From b5842db21928814bd20f7820fc2bc5cb17545b6f Mon Sep 17 00:00:00 2001 From: martinascholger Date: Thu, 30 Mar 2023 13:35:16 +0200 Subject: [PATCH 001/127] changed content model for content, #2381 --- P5/Source/Specs/content.xml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/P5/Source/Specs/content.xml b/P5/Source/Specs/content.xml index 2dc84c84a3..554fec4656 100644 --- a/P5/Source/Specs/content.xml +++ b/P5/Source/Specs/content.xml @@ -30,8 +30,8 @@ $Id$ - - + + @@ -149,6 +149,9 @@ $Id$ + +

It is required that the content element has only one child element. If several RELAX NG elements are desired, they must be wrapped in a rng:div.

+ From da60e4bc11afdc837200d221313d841f9ac0526c Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Sat, 14 Oct 2023 16:26:34 -0400 Subject: [PATCH 002/127] Added and att.gaijiProp to att.datable (back on 2023-08-12 16:00 ET). --- P5/Source/Specs/att.gaijiProp.xml | 189 +++++++++++++++++++----------- P5/Source/Specs/mapping.xml | 1 + 2 files changed, 119 insertions(+), 71 deletions(-) diff --git a/P5/Source/Specs/att.gaijiProp.xml b/P5/Source/Specs/att.gaijiProp.xml index bccac95f5d..439d582e75 100644 --- a/P5/Source/Specs/att.gaijiProp.xml +++ b/P5/Source/Specs/att.gaijiProp.xml @@ -8,75 +8,122 @@ $Id$ --> - provides attributes for defining the properties of - non-standard characters or glyphs. - liefert Attribute zur Definition der Eigenschaften - von nicht standardisierten Zeichen und Glyphen. - fornisce attributi per definire le proprietà di caratteri o glifi non standard - - - provides the name of the character or glyph - property being defined. - - - - - - provides the value of the character or - glyph property being defined. - - - - - - specifies the version number of the Unicode - Standard in which this property name is defined. - gibt die Versionsnummer eines externen - Standards an, in dem dieser Eigenschaftsname definiert ist. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

In this example a definition for the Unicode property Decomposition Mapping - is provided.

- - - -

All name-only attributes need an xs:boolean attribute value inside value.

- - - - + provides attributes for defining the properties of + non-standard characters or glyphs. + liefert Attribute zur Definition der Eigenschaften + von nicht standardisierten Zeichen und Glyphen. + fornisce attributi per definire le proprietà di caratteri o glifi non standard + + + + + + provides the name of the character or glyph + property being defined. + + + + + + provides the value of the character or + glyph property being defined. + + + + + + specifies the version number of the Unicode + Standard in which this property name is defined. + gibt die Versionsnummer eines externen + Standards an, in dem dieser Eigenschaftsname definiert ist. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + supplies the name + of the character set system from which this property is drawn. + + Unicode + + + Unicode + ISO 10646 + + + E. Nelson Bridwell + + Original character set developed by E. Nelson Bridwell as + described by Al Turniansky, in use from the 1950s to 1985. + + + Georg Brewer + + Developed by Georg Brewer, with a look similar to the + Byrne glyphs. Like the Byrne set, this is not a true + character set, but rather a set of alternate glyphs. + + + + Darren Doyle + + Glyph set (in some cases associated with multiple + characters) developed by Darren Doyle as part of a + comprehensive version of the language created in part for + an invented language classs at UT Austin in 2006. + + + + Christine Schreyer + + Character set (without actual codepoints) of 153 + characters developed, along with pronunciation rules, + roughly 300 words, and a grammar, developed by Christine + Schreyer developed in 2012 for Warner Brothers. + + + + + + +

In this example a definition for the Unicode property Decomposition Mapping + is provided.

+ + + +

All name-only attributes need an xs:boolean attribute value inside value.

+ + + + diff --git a/P5/Source/Specs/mapping.xml b/P5/Source/Specs/mapping.xml index 6cc9808dc1..7f378dbcab 100644 --- a/P5/Source/Specs/mapping.xml +++ b/P5/Source/Specs/mapping.xml @@ -31,6 +31,7 @@ $Id$ + From 968222ceaca0f778382550dc2306b93b918803c5 Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Sun, 12 Nov 2023 21:28:21 -0500 Subject: [PATCH 003/127] First crack at improving prose of CC for #2445 --- .../Guidelines/en/CC-LanguageCorpora.xml | 411 +++++++++--------- 1 file changed, 204 insertions(+), 207 deletions(-) diff --git a/P5/Source/Guidelines/en/CC-LanguageCorpora.xml b/P5/Source/Guidelines/en/CC-LanguageCorpora.xml index ce65a7a203..32fa210980 100644 --- a/P5/Source/Guidelines/en/CC-LanguageCorpora.xml +++ b/P5/Source/Guidelines/en/CC-LanguageCorpora.xml @@ -8,103 +8,95 @@ $Id$ -->
Language Corpora -

The term language corpus is used to mean a number of -rather different things. It may refer simply to any collection of +rather different things. It may refer simply to any collection of linguistic data (for example, written, spoken, signed, or multimodal), although many practitioners prefer to reserve it for collections which have been organized or collected with a particular end in view, generally to characterize a particular state or variety of one or more languages. Because opinions as to the best method of achieving this goal differ, -various subcategories of corpora have also been identified. For our +various subcategories of corpora have also been identified. For our purposes however, the distinguishing characteristic of a corpus is that its components have been selected or structured according to some -conscious set of design criteria. -

+conscious set of design criteria.

These design criteria may be very simple and undemanding, or very -sophisticated. A corpus may be intended to represent (in the +sophisticated. A corpus may be intended to represent (in the statistical sense) a particular linguistic variety or sublanguage, or it may be intended to represent all aspects of some assumed -core language. A corpus may be made up of whole -texts or of fragments or text samples. It may be a +core language. A corpus may be made up of whole +texts or of fragments or text samples. It may be a closed corpus, or an open or monitor corpus, the composition of which may -change over time. However, since an open corpus is of necessity +change over time. However, since an open corpus is of necessity finite at any particular point in time, the only likely effect of its expansibility from the encoding point of view may be some increased difficulty in maintaining consistent encoding practices (see further section ). For simplicity, therefore, our discussion largely concerns ways of encoding closed corpora, regarded -as single but composite texts. -

+as single but composite texts.

Language corpora are regarded by these Guidelines as composite texts rather than unitary texts -(on this distinction, see chapter ). This is +(on this distinction, see chapter ). This is because although each discrete sample of language in a corpus clearly has a claim to be considered as a text in its own right, it is also regarded as a subdivision of some larger object, if only for -convenience of analysis. Corpora share a number of characteristics +convenience of analysis. Corpora share a number of characteristics with other types of composite texts, including anthologies and -collections. Most notably, different components of composite texts +collections. Most notably, different components of composite texts may exhibit different structural properties (for example, some may be composed of verse, and others of prose), thus potentially requiring -elements from different TEI modules. -

+elements from different TEI modules.

Aside from these high-level structural differences, and possibly differences of scale, the encoding of language corpora and the -encoding of individual texts present identical sets of problems. Any +encoding of individual texts present identical sets of problems. Any of the encoding techniques and elements presented in other chapters of these Guidelines may therefore prove relevant to some aspect of corpus -encoding and may be used in corpora. Therefore, we do not repeat here +encoding and may be used in corpora. Therefore, we do not repeat here the discussion of such fundamental matters as the representation of multiple character sets (see chapter ); nor do we attempt to summarize the variety of elements provided for encoding basic structural features such as quoted or highlighted phrases, cross-references, lists, notes, editorial changes and reference systems (see -chapter ). In addition to these general purpose +chapter ). In addition to these general purpose elements, these Guidelines offer a range of more specialized sets of tags which may be of use in certain specialized corpora, for example those consisting primarily of verse (chapter ), drama (chapter ), transcriptions of spoken text -(chapter ), etc. Chapter +(chapter ), etc. Chapter should be reviewed for details of how these and other components of these Guidelines should be tailored to create a TEI customization -appropriate to a given application. In sum, it should not be assumed +appropriate to a given application. In sum, it should not be assumed that only the matters specifically addressed in this chapter are of -importance for corpus creators. -

+importance for corpus creators.

This chapter does however include some other material relevant to corpora and corpus-building, for which no other location -appeared suitable. It begins with a review of the distinction between +appeared suitable. It begins with a review of the distinction between unitary and composite texts, and of the different methods provided by these Guidelines for representing composite texts of different kinds -(section ). Section describes a +(section ). Section describes a set of additional header elements provided for the documentation of contextual information, of importance largely though not exclusively to -language corpora. This is the additional module for language corpora -proper. Section discusses a mechanism by which +language corpora. This is the additional module for language corpora +proper. Section discusses a mechanism by which individual parts of the TEI header may be associated with different -parts of a TEI-conformant text. Section reviews +parts of a TEI-conformant text. Section reviews various methods of providing linguistic annotation in corpora, with some specific examples of relevance to current practice in corpus -linguistics. Finally, section provides some general +linguistics. Finally, section provides some general recommendations about the use of these Guidelines in the building of -large corpora. -

+large corpora.

Varieties of Composite Text -

Both unitary and composite texts may be encoded using these Guidelines; composite texts, including corpora, will typically make use of the following tags for their top-level organization. Full descriptions of these may be found in chapter (for teiHeader), and chapter (for teiCorpus, TEI, text, and group); this section discusses their application to composite -texts in particular. -

+texts in particular.

In these Guidelines, the word text refers to any stretch of discourse, whether complete or incomplete, unitary or composite, which the encoder chooses (perhaps merely for purposes of analytic -convenience) to regard as a unit. The term composite text +convenience) to regard as a unit. The term composite text refers to texts within which other texts appear; the following common cases may be distinguished: @@ -115,15 +107,13 @@ in the form of collections or series of letters) otherwise unitary texts, within which one or more subordinate texts are embedded The elements listed above may be combined to encode each of these -varieties of composite text in different ways. -

+varieties of composite text in different ways.

In corpora, the component samples are clearly distinct texts, but the systematic collection, standardized preparation, and common markup of the corpus often make it useful to treat the entire corpus as a unit, -too. Some corpora may become so well established as to be regarded as +too. Some corpora may become so well established as to be regarded as texts in their own right; the Brown and LOB corpora are now close to -achieving this status. -

+achieving this status.

The teiCorpus element is intended for the encoding of language corpora, though it may also be useful in encoding newspapers, electronic anthologies, and other disparate collections of material. @@ -138,109 +128,142 @@ comprising a teiHeader followed by one or more members of the has a corpus-level teiHeader element, in which the corpus as a whole, and encoding practices common to multiple samples may be described. The overall structure of a TEI-conformant corpus is thus: - - - + - - + + - - + + Or, alternatively: - - + - - + + - - + +

Header information which relates to the whole corpus rather than to individual components of it should be factored out and included in the -teiHeader element prefixed to the whole. This two-level +teiHeader element prefixed to the whole. This two-level structure allows for contextual information to be specified at the -corpus level, at the individual text level, or at both. Discussion of +corpus level, at the individual text level, or at both. Discussion of the kinds of information which may thus be specified is provided -below, in section , as well as in chapter . Information of this type should in general be +below, in section , as well as in chapter . Information of this type should in general be specified only once: a variety of methods are provided for associating it with individual components of a corpus, as further described in -section . -

+section .

In some cases, the design of a corpus is reflected in its internal -structure. For example, a corpus of newspaper extracts might be +structure. For example, a corpus of newspaper extracts might be arranged to combine all stories of one type (reportage, editorial, reviews, etc.) into some higher-level grouping, possibly with sub-groups -for date, region, etc. The teiCorpus element provides no +for date, region, etc. A teiCorpus element may occur +directly inside a teiCorpus specifically to allow direct support for reflecting such internal corpus structure in the -markup: it treats the corpus as an undifferentiated series of -components, each tagged TEI.

-

If it is essential to reflect a single permanent organization of a -corpus into sub- and sub-sub-corpora, then the corpus or the high-level -subcorpora may be encoded as composite texts, using the group -element described below and in section . The -mechanisms for corpus characterization described in this chapter, -however, are designed to reduce the need to do this. Useful groupings +markup. For example: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

+

Furthermore, useful groupings of components may easily be expressed using the text classification and identification elements described in section , and those for associating declarations with corpus components described -in section . These methods also allow several +in section . These methods also allow several different methods of text grouping to co-exist, each to be used as -needed at different times. This helps minimize the danger of +needed at different times. This helps minimize the danger of cross-classification and misclassification of samples, and helps improve the flexibility with which parts of a corpus may be -characterized for different applications. -

+characterized for different applications.

Anthologies and collections are often treated as texts in their own -right, if only for historical reasons. In conventional publishing, at +right, if only for historical reasons. In conventional publishing, at least, anthologies are published as units, with single editorial responsibility and common front and back matter which may need to be -included in their electronic encodings. The texts collected in the +included in their electronic encodings. The texts collected in the anthology, of course, may also need to be identifiable as distinct -individual objects for study. -

+individual objects for study.

Poem cycles, epistolary novels, and epistolary essays differ from anthologies in that they are often written as single works, by single authors, for single occasions; nevertheless, it can be useful to treat their constituent parts as individual texts, as well as the cycle -itself. Structurally, therefore, they may be treated in the same way +itself. Structurally, therefore, they may be treated in the same way as anthologies: in both cases, the body of the text is composed -largely of other texts. -

+largely of other texts.

The group element is provided to simplify the encoding of -collections, anthologies, and cyclic works; as noted above, the -group element can also be used to record the potentially -complex internal structure of language corpora. For a full description, -see chapter . -

+collections, anthologies, and cyclic works; the group element +may also be used to record the potentially complex internal structure +of language corpora. (For a full description, see chapter .) The choice between using group or nested +teiCorpus elements is up to individual encoders, but in +general when it is useful to associate a significant quantity of +metadata with such a unit of text it is easier to use +teiCorpus.

Some composite texts, finally, are neither corpora, nor anthologies, -nor cyclic works: they are otherwise unitary texts within which other -texts are embedded. In general, they may be treated in the same way as +nor cyclic works: they are otherwise unitary texts within which other +texts are embedded. In general, they may be treated in the same way as unitary texts, using the normal TEI and -body elements. The embedded text itself may be encoded using -the text element. For further discussion, see chapter . -

+body elements. The embedded text itself may be encoded using +the text element. For further discussion, see chapter .

All composite texts share the characteristic that their different -component texts may be of structurally similar or dissimilar types. If -all component texts may all be encoded using the same module, +component texts may be of structurally similar or dissimilar types. If +all component texts may all be encoded using the same module, then no problem arises. If however they require different modules, then these must be included in the TEI customization. This -process is described in more detail in section . -

+process is described in more detail in section .

+
Contextual Information

Contextual information is of particular importance for collections or corpora composed of samples from a variety of different kinds of -text. Examples of such contextual information include: the age, sex, +text. Examples of such contextual information include: the age, sex, and geographical origins of participants in a language interaction, or their socio-economic status; the cost and publication data of a newspaper; the topic, register or factuality of an extract from a @@ -254,12 +277,12 @@ vector of social characteristics).

Such contextual information is potentially of equal importance for unitary texts, and these Guidelines accordingly make no particular distinction between the kinds of information which should be gathered -for unitary and for composite texts. In either case, the information +for unitary and for composite texts. In either case, the information should be recorded in the appropriate section of a TEI header, as -described in chapter . In the case of language corpora, +described in chapter . In the case of language corpora, such information may be gathered together in the overall corpus header, or split across all the component texts of a corpus, in their individual -headers, or divided between the two. The association between an +headers, or divided between the two. The association between an individual corpus text and the contextual information applicable to it may be made in a number of ways, as further discussed in section below.

Chapter , which should be read in conjunction with @@ -269,17 +292,17 @@ for example its bibliographic description and those of the source or sources from which it was derived (see section ); information about the encoding practices followed with the corpus, for example its design principles, editorial practices, reference system, -etc. (see section ); more detailed descriptive +etc. (see section ); more detailed descriptive information about the creation and content of the corpus, such as the languages used within it and any descriptive classification system used (see section ); and version information documenting any changes made in the electronic text (see section ).

In addition to the elements defined by chapter , several other elements can be used in the TEI header if the additional -module defined by this chapter is invoked. These additional tags make +module defined by this chapter is invoked. These additional tags make it possible to characterize the social or other situation within which a language interaction takes place or is experienced, the physical setting -of a language interaction, and the participants in it. Though this +of a language interaction, and the participants in it. Though this information may be relevant to, and provided for, unitary texts as well as for collections or corpora, it is more often recorded for the components of systematically developed corpora than for isolated texts, @@ -289,7 +312,7 @@ corpora.

When the module defined in this chapter is included in a schema, a number of additional elements become available within the profileDesc element of the TEI header (discussed in section -). These +). These elements, members of the model.profileDescPart, are discussed in the remainder of the chapter. @@ -343,9 +366,9 @@ remainder of the chapter.

The textDesc element provides a full description of the situation within which a text was produced or experienced, and thus characterizes it in a way relatively independent of any a -priori theory of text-types. It is provided as an alternative +priori theory of text-types. It is provided as an alternative or a supplement to the common use of descriptive taxonomies used to -categorize texts, which is fully described in section , and section . The description is +categorize texts, which is fully described in section , and section . The description is organized as a set of values and optional prose descriptions for the following eight situational parameters, each represented by one of the following eight elements: @@ -358,19 +381,18 @@ described in .

elements, supplied in the order specified. Except for the purpose element, which may be repeated to indicate multiple purposes, no element should appear more than once within a single text -description. Each element may be empty, or may contain a brief +description. Each element may be empty, or may contain a brief qualification or more detailed description of the value expressed by -its attributes. It should be noted that some texts, in particular +its attributes. It should be noted that some texts, in particular literary ones, may resist unambiguous classification in some of these dimensions; in such cases, the situational parameter in question should be given the content not applicable or an equivalent -phrase. -

+phrase.

Texts may be described along many dimensions, according to many -different taxonomies. No generally accepted consensus as to how such +different taxonomies. No generally accepted consensus as to how such taxonomies should be defined has yet emerged, despite the best efforts of many corpus linguists, text linguists, sociolinguists, -rhetoricians, and literary theorists over the years. Rather than +rhetoricians, and literary theorists over the years. Rather than attempting the task of proposing a single taxonomy of text-types (or the equally impossible one of enumerating all those which have been proposed previously), the closed set of @@ -380,7 +402,7 @@ individual texts, without insisting on a system of discrete high-level text-types. Such text-types may however be used in combination with the parameters proposed here, with the advantage that the internal structure of each such text-type can be specified in terms of the -parameters proposed. This approach has the following analytical +parameters proposed. This approach has the following analytical advantages:Schemes similar to that proposed here were developed in the 1960s and 1970s by researchers such as Hymes, Halliday, and Crystal and Davy, but have rarely been implemented; one notable @@ -394,30 +416,28 @@ contrast to discrete categories based on type or topic) based on the particular parameters of interest to them it is equally applicable to spoken, written, or signed texts

Two alternative approaches to the use of these parameters are -supported by these Guidelines. One is to use pre-existing taxonomies +supported by these Guidelines. One is to use pre-existing taxonomies such as those used in subject classification or other types of text categorization. Such taxonomies may also be appropriate for the description of the -topics addressed by particular texts. Elements for this purpose are +topics addressed by particular texts. Elements for this purpose are described in section , and elements for defining or -declaring such classification schemes in section . A +declaring such classification schemes in section . A second approach is to develop an application-specific set of feature structures and an associated feature system declaration, as described in -chapters and . -

+chapters and .

Where the organizing principles of a corpus or collection so permit, it may be convenient to regard a particular set of values for the situational parameters listed in this section as forming a text-type in its own right; this may also be useful where -the same set of values applies to several texts within a corpus. In +the same set of values applies to several texts within a corpus. In such a case, the set of text-types so defined should be regarded as a -taxonomy. The mechanisms described in section may be used to define hierarchic taxonomies of such +taxonomy. The mechanisms described in section may be used to define hierarchic taxonomies of such text-types, provided that the catDesc component of the category element contains a textDesc element rather -than a prose description. Particular texts may then be associated with -such definitions using the mechanisms described in sections . -

+than a prose description. Particular texts may then be associated with +such definitions using the mechanisms described in sections .

Using these situational parameters, an informal domestic conversation might be characterized as follows: @@ -590,7 +610,7 @@ parameters might be used to characterize a novel:

The particDesc element in the profileDesc element provides additional information about the participants in a spoken text or, where this is judged appropriate, the persons named or -depicted in a written text. When the detailed elements provided by +depicted in a written text. When the detailed elements provided by the namesdates module described in are included in a schema, this element can contain detailed demographic or descriptive information about individual speakers or groups of speakers, such as their names or @@ -603,7 +623,7 @@ attribute.

participant are used throughout this section, it is intended that the same mechanisms may be used to characterize fictional personæ or voices within a written text, except -where otherwise stated. For the purposes of analysis of language usage, +where otherwise stated. For the purposes of analysis of language usage, the information specified here should be equally applicable to written, spoken, or signed texts.

The element particDesc contains a description of the @@ -612,9 +632,8 @@ straightforward prose, possibly containing a list of names, encoded using the usual list and name elements, or alternatively using the more specific and detailed listPerson element provided by the namesdates module -described in . -

-

For example, a participant in a recorded conversation might be +described in .

+

For example, a participant in a recorded conversation might be described informally as follows:

Female informant, well-educated, born in Shropshire UK, 12 Jan @@ -655,17 +674,16 @@ definitions for their speakers; see further section . Here, the characters are simply listed without the detailed -structure which use of the listPerson element permits. -

+structure which use of the listPerson element permits.

The Setting Description

The settingDesc element is used to describe the setting or -settings in which language interaction takes place. It may contain a +settings in which language interaction takes place. It may contain a prose description, analogous to a stage description at the start of a play, stating in broad terms the locale, or a more detailed -description of a series of such settings.

+description of a series of such settings.

Each distinct setting is described by means of a setting element. @@ -676,9 +694,9 @@ element. Individual settings may be associated with particular participants by means of the optional who attribute which this element inherits as a member of the att.ascribed -if, for example, participants are in different places. This attribute +if, for example, participants are in different places. This attribute identifies one or more individual participants or participant groups, -as discussed earlier in section . If this +as discussed earlier in section . If this attribute is not specified, the setting details provided are assumed to apply to all participants represented in the language interaction. Note however that it is not possible to encode different @@ -698,8 +716,7 @@ provide the following elements: Additional more specific naming elements such as orgName or persName may also be available if the -namesdates module is also included in the schema. -

+namesdates module is also included in the schema.

The following example demonstrates the kind of background information often required to support transcriptions of language interactions, first encoded as a simple prose narrative: @@ -733,7 +750,7 @@ way: radio performance

-

Again, a more detailed encoding for places is feasible if the +

Again, a more detailed encoding for places is feasible if the namesdates module is included in the schema. The above examples assume that only the general purpose name element supplied in the core module is @@ -778,53 +795,47 @@ available. - -

+

Associating Contextual Information with a Text

This section discusses the association of the contextual information held in the header with the individual elements making up a TEI text or -corpus. Contextual information is held in elements of various kinds +corpus. Contextual information is held in elements of various kinds within the TEI header, as discussed elsewhere in this section and in -chapter . Here we consider what happens when different +chapter . Here we consider what happens when different parts of a document need to be associated with different contextual information of the same type, for example when one part of a document uses a different encoding practice from another, or where one part -relates to a different setting from another. In such situations, there -will be more than one instance of a header element of the relevant type. -

+relates to a different setting from another. In such situations, there +will be more than one instance of a header element of the relevant type.

The TEI scheme allow for the following possibilities: A given element may appear in the corpus header only, in the header of one or more texts only, or in both places There may be multiple occurrences of certain elements in either -the corpus or a text header. -

+the corpus or a text header.

To simplify the exposition, we deal with these two possibilities separately in what follows; however, they may be combined as -desired. -

+desired.

Combining Corpus and Text Headers

A TEI-conformant document may have more than one header only in the case of a TEI corpus, which must have a header in its own right, as well -as the obligatory header for each text. Every element specified in a +as the obligatory header for each text. Every element specified in a corpus-header is understood as if it appeared within every text header -in the corpus. An element specified in a text header but not in the -corpus header supplements the specification for that text alone. If any +in the corpus. An element specified in a text header but not in the +corpus header supplements the specification for that text alone. If any element is specified in both corpus and text headers, the corpus header -element is over-ridden for that text alone. -

+element is over-ridden for that text alone.

The titleStmt for a corpus text is understood to be -prefixed by the titleStmt given in the corpus header. All +prefixed by the titleStmt given in the corpus header. All other optional elements of the fileDesc should be omitted from -an individual corpus text header unless they differ from those -specified in the corpus header. All other header elements behave +an individual corpus text header unless they differ from those +specified in the corpus header. All other header elements behave identically, in the manner documented below. This facility makes it possible to state once for all in the corpus header each piece of contextual information which is common to the whole of the corpus, while still allowing for individual texts to vary from -this common denominator. -

+this common denominator.

For example, the following schematic shows the structure of a corpus comprising three texts, the first and last of which share the same encoding description. The second one has its own encoding description. @@ -881,7 +892,7 @@ part of a text header or the corpus header by means of a decls attrib that element. This linkage is used to over-ride the default association between declarations in the header and a corpus or corpus text. The only header elements which may be associated in this way are -those which would not otherwise be meaningfully repeatable.

+those which would not otherwise be meaningfully repeatable.

Declarable elements are all members of the class att.declarable; the corresponding declaring elements are all members of the class att.declaring. @@ -932,7 +943,6 @@ elements are all members of the class att.declaring. - Each of the above elements is repeatable within a single header; that is, there may be more than one instance of any declarable element type at a given level. When this occurs, the following rules @@ -942,11 +952,10 @@ than once: each must bear a unique identifier when occurring within the same parent element, exactly one element must be specified as the default, by having a default attribute with the value "true". - -

+

In the following example, an editorial declaration contains two possible correction policies, one identified as -CorPol1 and the other as CorPol2. Since there +CorPol1 and the other as CorPol2. Since there are two, one of them (in this case CorPol1) should be specified as the default: @@ -961,7 +970,7 @@ specified as the default: For texts associated with the header in which this declaration appears, correction method CorPol1 will be -assumed, unless they explicitly state otherwise. Here is the +assumed, unless they explicitly state otherwise. Here is the structure of a text in which a division states otherwise: @@ -970,8 +979,7 @@ structure of a text in which a division states otherwise: @@ -988,8 +995,7 @@ attribute points must follow two further restrictions: elements of the same type, only the children elements with default set to "true" are considered referenced. Each element specified, explicitly or implicitly, by the list of -identifiers must be of a different kind. -

+identifiers must be of a different kind.

To demonstrate how these rules operate, we now expand our earlier example slightly: @@ -1013,24 +1019,22 @@ example slightly:

This encoding description now has two editorial declarations, -identified as ED1 (the default) and ED2. For texts not specifying -otherwise, ED1 will apply. If ED1 applies, correction method C1A and +identified as ED1 (the default) and ED2. For texts not specifying +otherwise, ED1 will apply. If ED1 applies, correction method C1A and normalization method N1 apply, since these are the specified defaults -within ED1. In the same way, for a text specifying decls as +within ED1. In the same way, for a text specifying decls as #ED2, correction C2A, and normalization N2B will -apply. -

-

A finer grained approach is also possible. A text might specify +apply.

+

A finer grained approach is also possible. A text might specify text decls='#C2B #N2A', to mix and match declarations as -required. A tag such as text decls='#ED1 #ED2' would +required. A tag such as text decls='#ED1 #ED2' would (obviously) be illegal, since it includes two elements of the same type; a tag such as text decls='#ED2 #C1A' is also illegal, since in this context #ED2 is synonymous with the defaults for that editorial declaration, namely #C2A #N2B, resulting in a list -that identifies two correction elements (C1A and C2A). -

+that identifies two correction elements (C1A and C2A).

Summary

The rules determining which of the declarable elements are applicable at any point may be summarized as follows: @@ -1055,16 +1059,15 @@ given declarable element is semantically equivalent to selecting only those contained elements which are specified as defaults. An association made by one element applies by default to all of its descendants. - -

+

Linguistic Annotation of Corpora

Language corpora often include analytic encodings or annotations, -designed to support a variety of different views of language. The +designed to support a variety of different views of language. The present Guidelines do not advocate any particular approach to linguistic annotation (or tagging); instead a number of general analytic facilities are provided which support the representation of most forms of annotation in a standard and -self-documenting manner. Analytic annotation is of importance in many +self-documenting manner. Analytic annotation is of importance in many fields, not only in corpus linguistics, and is therefore discussed in general terms elsewhere in the Guidelines.See in particular chapters @@ -1077,53 +1080,48 @@ determined by an analysis of linguistic features of the text, excluding as borderline cases both the formal structural properties of the text (e.g. its division into chapters or paragraphs) and descriptive information about its context (the circumstances of its production, its -genre, or medium). The structural properties of any TEI-conformant text +genre, or medium). The structural properties of any TEI-conformant text should be represented using the structural elements discussed elsewhere -in these Guidelines, for example in chapters and +in these Guidelines, for example in chapters and . The contextual properties of a TEI text are fully documented in the TEI header, which -is discussed in chapter , and in section of the present chapter. -

+is discussed in chapter , and in section of the present chapter.

Other forms of linguistic annotation may be applied at a number of -levels in a text. A code (such as a word-class or part-of-speech +levels in a text. A code (such as a word-class or part-of-speech code) may be associated with each word or token, or with groups of such -tokens, which may be continuous, discontinuous, or nested. A code may +tokens, which may be continuous, discontinuous, or nested. A code may also be associated with relationships (such as cohesion) perceived as -existing between distinct parts of a text. The codes themselves may +existing between distinct parts of a text. The codes themselves may stand for discrete non-decomposable categories, or they may represent -highly articulated bundles of textual features. Their function may be +highly articulated bundles of textual features. Their function may be to place the annotated part of the text somewhere within a narrowly linguistic or discoursal domain of analysis, or within a more general -semantic field, or any combination drawn from these and other domains. -

+semantic field, or any combination drawn from these and other domains.

The manner by which such annotations are generated and attached to -the text may be entirely automatic, entirely manual, or a mixture. The +the text may be entirely automatic, entirely manual, or a mixture. The ease and accuracy with which analysis may be automated may vary with the -level at which the annotation is attached. The method employed should +level at which the annotation is attached. The method employed should be documented in the interpretation element within the encoding -description of the TEI header, as described in section . Where different parts of a corpus have used different +description of the TEI header, as described in section . Where different parts of a corpus have used different annotation methods, the decls attribute should be used to -indicate the fact, as further discussed in section . -

+indicate the fact, as further discussed in section .

An extended example of one form of linguistic analysis commonly -practised in corpus linguistics is given in section . -

+practised in corpus linguistics is given in section .

Recommendations for the Encoding of Large Corpora

These Guidelines include proposals for the identification and encoding of a far greater variety of textual features and characteristics than is likely to be either feasible or desirable in -any one language corpus, however large and ambitious. The reasoning -behind this catholic approach is further discussed in chapter . For most large-scale corpus projects, it will therefore +any one language corpus, however large and ambitious. The reasoning +behind this catholic approach is further discussed in chapter . For most large-scale corpus projects, it will therefore be necessary to determine a subset of TEI recommended elements appropriate to the anticipated needs of the project, as further discussed in chapter ; these mechanisms include the ability to exclude selected element types, add new element types, -and change the names of existing elements. A discussion of the +and change the names of existing elements. A discussion of the implications of such changes for TEI conformance is provided in -chapter . -

+chapter .

Because of the high cost of identifying and encoding many textual features, and the difficulty in ensuring consistent practice across very large corpora, encoders may find it convenient to divide the set of @@ -1142,8 +1140,7 @@ text. textual features in this category are deliberately not encoded; they may be transcribed as unmarked up text, or represented as gap -elements, or silently omitted, as appropriate. -

+elements, or silently omitted, as appropriate.

Module for Language Corpora @@ -1164,4 +1161,4 @@ elements, or silently omitted, as appropriate. described in .

- \ No newline at end of file + From 42ea64e373c2cee45aa9755f7a80760d53565953 Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Mon, 13 Nov 2023 10:27:31 -0500 Subject: [PATCH 004/127] remove extraneous namespace decl --- P5/Source/Guidelines/en/CC-LanguageCorpora.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/P5/Source/Guidelines/en/CC-LanguageCorpora.xml b/P5/Source/Guidelines/en/CC-LanguageCorpora.xml index 32fa210980..c03d302a0f 100644 --- a/P5/Source/Guidelines/en/CC-LanguageCorpora.xml +++ b/P5/Source/Guidelines/en/CC-LanguageCorpora.xml @@ -169,7 +169,7 @@ for date, region, etc. A teiCorpus element may occur directly inside a teiCorpus specifically to allow direct support for reflecting such internal corpus structure in the markup. For example: - + From 7f52ad0fa693eefae45407fddf09fa59f876aa1e Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Mon, 13 Nov 2023 15:23:46 -0500 Subject: [PATCH 005/127] Tweak wording per suggestion @trishaoconnor and @raffazizzi --- P5/Source/Guidelines/en/CC-LanguageCorpora.xml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/P5/Source/Guidelines/en/CC-LanguageCorpora.xml b/P5/Source/Guidelines/en/CC-LanguageCorpora.xml index c03d302a0f..094f7eef13 100644 --- a/P5/Source/Guidelines/en/CC-LanguageCorpora.xml +++ b/P5/Source/Guidelines/en/CC-LanguageCorpora.xml @@ -1114,7 +1114,8 @@ practised in corpus linguistics is given in section .

encoding of a far greater variety of textual features and characteristics than is likely to be either feasible or desirable in any one language corpus, however large and ambitious. The reasoning -behind this catholic approach is further discussed in chapter . For most large-scale corpus projects, it will therefore +behind this universal approach is further discussed in chapter . +For most large-scale corpus projects, it will therefore be necessary to determine a subset of TEI recommended elements appropriate to the anticipated needs of the project, as further discussed in chapter ; these mechanisms include From d522c67af3852a87cfa5b688d1326abc0fc91b49 Mon Sep 17 00:00:00 2001 From: raffazizzi Date: Thu, 16 Nov 2023 16:29:06 -0500 Subject: [PATCH 006/127] upped version --- P5/VERSION | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/P5/VERSION b/P5/VERSION index f6cdf40983..90a8eb5ce3 100644 --- a/P5/VERSION +++ b/P5/VERSION @@ -1 +1 @@ -4.7.0 +4.8.0a From ed73010714e3b0981d9bd85b346dce97c5b5cd38 Mon Sep 17 00:00:00 2001 From: raffazizzi Date: Fri, 17 Nov 2023 13:45:46 -0500 Subject: [PATCH 007/127] fixed broken links in 4.7.0 release notes --- P5/ReleaseNotes/readme-4.7.0.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/P5/ReleaseNotes/readme-4.7.0.xml b/P5/ReleaseNotes/readme-4.7.0.xml index 7e4e7d717a..bbbefa8104 100644 --- a/P5/ReleaseNotes/readme-4.7.0.xml +++ b/P5/ReleaseNotes/readme-4.7.0.xml @@ -32,7 +32,7 @@ See the file COPYING.txt for details community. As always, the majority of these changes and corrections are a consequence of feature requests or bugs reported by the TEI community using the GitHub tracking system. A full list of the issues resolved in the course of this release cycle may be found under the - 4.7.0 milestone.

+ 4.7.0 milestone.

The following changes are particularly worth highlighting in this release: @@ -49,7 +49,7 @@ See the file COPYING.txt for details elements, but still allows older ways of labeling events. See PR #2483. The taxonomy and category elements are now added to att.datacat (att.datcat (#2419). @@ -149,7 +149,7 @@ See the file COPYING.txt for details conversions). The Stylesheets are maintained separately from the Guidelines at https://github.com/TEIC/Stylesheets. A full list of the issues resolved in the course of this release cycle may be found under the - 7.56.0 + 7.56.0 milestone.

Highlights of this release include: From 15e10e0275273d0b1bc6a36d58d34891da2826d5 Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Sun, 26 Nov 2023 08:28:39 -0500 Subject: [PATCH 008/127] add a missing Oxford comma --- P5/Source/Guidelines/en/TS-TranscriptionsofSpeech.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/P5/Source/Guidelines/en/TS-TranscriptionsofSpeech.xml b/P5/Source/Guidelines/en/TS-TranscriptionsofSpeech.xml index 4126156226..c6385f2a2e 100644 --- a/P5/Source/Guidelines/en/TS-TranscriptionsofSpeech.xml +++ b/P5/Source/Guidelines/en/TS-TranscriptionsofSpeech.xml @@ -500,7 +500,7 @@ section .

An utterance may contain either running text, or text within which other basic structural elements are nested. Where such nesting occurs, the who attribute is considered to be inherited for the -elements pause, vocal, shift and +elements pause, vocal, shift, and kinesic; that is, a pause or shift (etc.) within an utterance is regarded as being produced by that speaker only, while a pause between utterances applies to all speakers. @@ -1472,4 +1472,4 @@ to divide a transcribed text up into meaningful analytic sections. - \ No newline at end of file + From a1ed62ac03a681adc6971810cf5e89f8d05f712b Mon Sep 17 00:00:00 2001 From: sabine seifert Date: Wed, 29 Nov 2023 15:49:47 +0100 Subject: [PATCH 009/127] Update definition, closes #2476 --- P5/Source/Specs/surface.xml | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/P5/Source/Specs/surface.xml b/P5/Source/Specs/surface.xml index d07cce59b3..70ee7aa2f3 100644 --- a/P5/Source/Specs/surface.xml +++ b/P5/Source/Specs/surface.xml @@ -10,8 +10,7 @@ $Id$ defines a written surface as a two-dimensional coordinate space, optionally grouping one or more graphic representations of -that space, zones of interest within that space, and transcriptions of the - writing within them. +that space, zones of interest within that space, and, when using an embedded transcription approach, transcriptions of the writing within them. 직사각형의 좌표 공간과 그 내부에서 기록 표면부를 정의한다. 수의적으로 그 공간의 하나 이상의 그림 표상과 관심 있는 직사각형 공간을 모아놓는다. define una superficie escrita en coordinadas rectangulares, agrupando opcionalmente una o más representaciones gráficas de ese espacio, y las zonas rectangulares de interés dentro de él. 矩形の座標により、書記の表面を定義する。選択的に、空間や矩形範囲中のひ From 2abbebcf679166bdaac0d696822a9a38571067e0 Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Wed, 6 Dec 2023 19:27:36 -0500 Subject: [PATCH 010/127] Fix #2512 --- P5/Source/Specs/att.calendarSystem.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/P5/Source/Specs/att.calendarSystem.xml b/P5/Source/Specs/att.calendarSystem.xml index 36f102e80c..c34014f4d0 100644 --- a/P5/Source/Specs/att.calendarSystem.xml +++ b/P5/Source/Specs/att.calendarSystem.xml @@ -26,7 +26,7 @@ $Id$ - + @calendar indicates one or more From 21ba627db69d87b58f6c88cc28a89779109408c9 Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Fri, 15 Dec 2023 00:28:34 -0500 Subject: [PATCH 011/127] take a crack at issuing warning when ISO Schematron assertion is made without a context --- .../en/TD-DocumentationElements.xml | 76 +++++++------- P5/Source/Guidelines/en/USE.xml | 2 + P5/Source/Specs/ab.xml | 10 +- P5/Source/Specs/addSpan.xml | 22 ++--- P5/Source/Specs/alternate.xml | 10 +- P5/Source/Specs/att.repeatable.xml | 4 +- P5/Source/Specs/attDef.xml | 49 ++++++--- P5/Source/Specs/catchwords.xml | 16 ++- P5/Source/Specs/citeStructure.xml | 14 +-- P5/Source/Specs/constraint.xml | 11 ++- P5/Source/Specs/constraintSpec.xml | 36 ++++--- P5/Source/Specs/damageSpan.xml | 19 ++-- P5/Source/Specs/delSpan.xml | 18 ++-- P5/Source/Specs/dimensions.xml | 66 +++++-------- P5/Source/Specs/div.xml | 27 ++--- P5/Source/Specs/join.xml | 24 ++--- P5/Source/Specs/l.xml | 8 +- P5/Source/Specs/lg.xml | 31 +++--- P5/Source/Specs/link.xml | 6 +- P5/Source/Specs/modelSequence.xml | 26 +++-- P5/Source/Specs/moduleRef.xml | 35 +++---- P5/Source/Specs/msIdentifier.xml | 11 ++- P5/Source/Specs/p.xml | 33 +++++-- P5/Source/Specs/ptr.xml | 9 +- P5/Source/Specs/quotation.xml | 52 +++------- P5/Source/Specs/rdgGrp.xml | 13 ++- P5/Source/Specs/ref.xml | 28 +++--- P5/Source/Specs/relatedItem.xml | 41 +++----- P5/Source/Specs/relation.xml | 77 +++++++-------- P5/Source/Specs/rt.xml | 41 ++++---- P5/Source/Specs/s.xml | 16 +-- P5/Source/Specs/secFol.xml | 11 +-- P5/Source/Specs/sequence.xml | 6 +- P5/Source/Specs/shift.xml | 26 ++--- P5/Source/Specs/signatures.xml | 4 +- P5/Source/Specs/span.xml | 58 +++++------ P5/Source/Specs/standOff.xml | 99 +++++++++---------- P5/Source/Specs/subst.xml | 14 +-- P5/Test/detest.odd | 41 +++++--- .../detest_xml_schematron.log | 34 +++---- 40 files changed, 562 insertions(+), 562 deletions(-) diff --git a/P5/Source/Guidelines/en/TD-DocumentationElements.xml b/P5/Source/Guidelines/en/TD-DocumentationElements.xml index b610ee20ff..874ec510c1 100644 --- a/P5/Source/Guidelines/en/TD-DocumentationElements.xml +++ b/P5/Source/Guidelines/en/TD-DocumentationElements.xml @@ -9,6 +9,7 @@ $Id$

Documentation Elements @@ -840,22 +841,25 @@ to mark any technical term, thus: current version of the Guidelines, constraint specifications expressed as Schematron rules have been added, as follows: - + - One of the - attributes 'name', 'ref' or 'key' must be supplied + + One of the attributes @name, @ref or @key must be supplied + - + - Only one of the - attributes @active and @mutual may be supplied + + Only one of the attributes @active and @mutual may be supplied + - + - the - attribute 'passive' may be supplied only if the attribute 'active' is supplied + + the attribute @passive may be supplied only if the attribute @active is supplied + @@ -881,16 +885,16 @@ to mark any technical term, thus: - an introductory component - of the title is expected + + an introductory component of the title is expected + - a main title must be supplied - + + a main title must be supplied + @@ -1019,10 +1023,10 @@ to mark any technical term, thus: Note that restrictions are either expressed with restriction or dataFacet, never both.

-

A datatype may be used to constrain the textual content of - an element, rather than the value of an attribute. But because - they are intended for use in defining ranges of attribute - values, datatypes may not contain elements or attributes.

+

A datatype may be used to constrain the textual content of + an element, rather than the value of an attribute. But because + they are intended for use in defining ranges of attribute + values, datatypes may not contain elements or attributes.

The attributes minOccurs and maxOccurs are available for the case where an attribute may take more than one value of the type @@ -1030,21 +1034,21 @@ to mark any technical term, thus: the layout element can have one or two non-negative integers as its value: - - columns - specifies the number of columns per page - - - - -

If a single number is given, all pages referenced - have this number of columns. If two numbers are given, - the number of columns per page varies between the - values supplied. Where columns is omitted - the number is assumed to be 1.

- - - + + columns + specifies the number of columns per page + + + + +

If a single number is given, all pages referenced + have this number of columns. If two numbers are given, + the number of columns per page varies between the + values supplied. Where columns is omitted + the number is assumed to be 1.

+ + + indicating that the target attribute may take any number of values, each being of the same datatype, namely the TEI data specification teidata.pointer. As is usual in XML, multiple values for a single attribute are separated by one or more white space characters. Hence, @@ -1075,7 +1079,9 @@ to mark any technical term, thus: - age at death must be an integer less than 150 + + age at death must be an integer less than 150 + diff --git a/P5/Source/Guidelines/en/USE.xml b/P5/Source/Guidelines/en/USE.xml index acd43c1eb8..a4819a7c24 100644 --- a/P5/Source/Guidelines/en/USE.xml +++ b/P5/Source/Guidelines/en/USE.xml @@ -101,9 +101,11 @@ that practice. --> scheme="schematron" ident="no_outputs_nor_predicates_4_my_kids"> + The 'model' children of a 'modelSequence' element inherit the @output attribute of the parent 'modelSequence', and thus should not have their own + diff --git a/P5/Source/Specs/ab.xml b/P5/Source/Specs/ab.xml index 16bb2a91be..cfe3240a1a 100644 --- a/P5/Source/Specs/ab.xml +++ b/P5/Source/Specs/ab.xml @@ -35,9 +35,11 @@ - - Abstract model violation: Lines may not contain higher-level divisions such as p or ab, unless ab is a child of figure or note, or is a descendant of floatingText. - + + + Abstract model violation: Lines may not contain higher-level divisions such as p or ab, unless ab is a child of figure or note, or is a descendant of floatingText. + + @@ -67,4 +69,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/addSpan.xml b/P5/Source/Specs/addSpan.xml index 3053adcdc6..b6762a7249 100644 --- a/P5/Source/Specs/addSpan.xml +++ b/P5/Source/Specs/addSpan.xml @@ -15,17 +15,13 @@ $Id$ fragmento de texto añadido porzione di testo aggiunta 追加テキストの範囲 - marks the beginning of a longer sequence of text added by an - author, scribe, annotator or corrector (see also add). + marks the beginning of a longer sequence of text added by an author, scribe, annotator or corrector (see also add). 저자, 필기사, 주석자, 또는 교정자에 의해 추가된 긴 연쇄의 텍스트 시작부를 표시한다.(add 참조) 標記由作者、抄寫者、註解者或更正者所加入的較長連續文字之開端 (參照add) 。 - 著者、筆写者、注釈者、校正者の手による長めの追加テキストを挿入する始 - 点を示す(addも参照のこと)。 - marque le début d'une longue partie de texte ajoutée par un auteur, un copiste, un annotateur ou - un correcteur (voir aussi add). + 著者、筆写者、注釈者、校正者の手による長めの追加テキストを挿入する始 点を示す(addも参照のこと)。 + marque le début d'une longue partie de texte ajoutée par un auteur, un copiste, un annotateur ou un correcteur (voir aussi add). señala el inicio de un fragmento largo de texto añadido por un autor, un transcriptor, un comentarista o un corrector (ver también add). - segnala l'inizio di una porzione di testo più lunga aggiunta - da un autore, un trascrittore, un annotatore o un correttore (vedi anche add) + segnala l'inizio di una porzione di testo più lunga aggiunta da un autore, un trascrittore, un annotatore o un correttore (vedi anche add) @@ -38,12 +34,16 @@ $Id$ - The @spanTo attribute of is required. + + The @spanTo attribute of is required. + - L'attribut spanTo est requis. + + L'attribut spanTo est requis. + @@ -94,4 +94,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/alternate.xml b/P5/Source/Specs/alternate.xml index ebe3bb05ce..151546d204 100644 --- a/P5/Source/Specs/alternate.xml +++ b/P5/Source/Specs/alternate.xml @@ -23,14 +23,16 @@ $Id$ - The alternate element must have at least two child elements + + The alternate element must have at least two child elements + - - + + @@ -40,4 +42,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/att.repeatable.xml b/P5/Source/Specs/att.repeatable.xml index 02c9990305..d6e46be6b6 100644 --- a/P5/Source/Specs/att.repeatable.xml +++ b/P5/Source/Specs/att.repeatable.xml @@ -20,12 +20,12 @@ $Id$ maxOccurs is 1, when maxOccurs is not specified minOccurs must always be less than or equal to 1. --> - + @maxOccurs should be greater than or equal to @minOccurs - + When @maxOccurs is not specified, @minOccurs must be 0 or 1 diff --git a/P5/Source/Specs/attDef.xml b/P5/Source/Specs/attDef.xml index 6e90fdbd0f..9ea20a11ed 100644 --- a/P5/Source/Specs/attDef.xml +++ b/P5/Source/Specs/attDef.xml @@ -45,16 +45,26 @@ $Id$ - - Attribute: the definition of the @ attribute in the - - should have a closed valList or a datatype + + + + Attribute: the definition of the @ attribute in the + + + should + have a closed valList or a datatype + + - Since the @ attribute is required, it will always be specified. Thus the default value (of "") will never be used. Either change the definition of the attribute so it is not required ("rec" or "opt"), or remove the defaultVal element. + Since the @ attribute is required, it will always be specified. Thus the default value (of "") will never be used. Either change the definition of the attribute so it is not required ("rec" or "opt"), or remove the defaultVal element. @@ -65,9 +75,17 @@ $Id$ + - - In the defining + + In the defining the default value of the @ attribute is not among the closed list of possible values @@ -76,7 +94,13 @@ $Id$ - + In the defining the default value of the @ attribute is not among the closed list of possible @@ -90,12 +114,9 @@ $Id$ 속성 또는 요소의 수의성을 명시한다. 說明屬性或元素的必備性。 属性または要素の選択性を示す。 - précise qu'un attribut ou un élément sont - facultatifs. - especifica el caracter opcional de un atributo o un - elemento - indica il carattere facoltativo di un attributo o - elemento + précise qu'un attribut ou un élément sont facultatifs. + especifica el caracter opcional de un atributo o un elemento + indica il carattere facoltativo di un attributo o elemento opt diff --git a/P5/Source/Specs/catchwords.xml b/P5/Source/Specs/catchwords.xml index e9cbc1b77f..65fb8ca2fd 100644 --- a/P5/Source/Specs/catchwords.xml +++ b/P5/Source/Specs/catchwords.xml @@ -10,15 +10,11 @@ $Id$ catchwords réclames - describes the system used to ensure -correct ordering of the quires or similar making up a codex, incunable, or other object -typically by means of annotations at the foot of the page. + describes the system used to ensure correct ordering of the quires or similar making up a codex, incunable, or other object typically by means of annotations at the foot of the page. 일반적으로 페이지의 밑에 표시되며, 제본되지 않은 원고 또는 고판본의 정확한 순서를 보장하는 체계를 기술한다. 描述一疊書頁裝訂成手抄本或書冊時，確保書頁順序無誤的方法，通常是利用頁腳的註記。 古い冊子本や刊本にみられる、折丁の正しい順序を確認するためのシステムについて記述する。一般には、ページの脚に注記される。 - décrit le système utilisé pour s'assurer que les - cahiers formant un manuscrit ou un incunable sont dans le bon ordre, typiquement au moyen - d'annotations en bas de page. + décrit le système utilisé pour s'assurer que les cahiers formant un manuscrit ou un incunable sont dans le bon ordre, typiquement au moyen d'annotations en bas de page. describe el sistema utilizado para garantizar la ordenación correcta de los cuadernos que constituyen un códex o un incunable, obtenido normalmente por medio de anotaciones a pie de página. descrive il sistema utilizzato per garantire l'ordinamento corretto dei quaderni che costituiscono un codice o incunabolo, ottenuto solitamente tramite annotazioni a piè di pagina @@ -36,9 +32,11 @@ typically by means of annotations at the foot of the page. to test this the content of s have been extracted and put in the TEI namespace for testing. At least, that's what I think is going on. —Syd, 2018-10-01 - --> + --> - The element should not be used outside of msDesc. + + The element should not be used outside of msDesc. + @@ -50,4 +48,4 @@ the inner bounding line, reading from top to bottom. - \ No newline at end of file + diff --git a/P5/Source/Specs/citeStructure.xml b/P5/Source/Specs/citeStructure.xml index 9244d3cf24..61e41fe3cd 100644 --- a/P5/Source/Specs/citeStructure.xml +++ b/P5/Source/Specs/citeStructure.xml @@ -7,7 +7,7 @@ $Date$ $Id$ --> - + citation structure declares a structure and method for citing the current document. @@ -44,16 +44,16 @@ $Id$ - - An XPath in @match on the outer must start with '/'. - + + An XPath in @match on the outer must start with '/'. + - - An XPath in @match must not start with '/' except on the outer . - + + An XPath in @match must not start with '/' except on the outer . + diff --git a/P5/Source/Specs/constraint.xml b/P5/Source/Specs/constraint.xml index 0183768f58..0e68dd75af 100644 --- a/P5/Source/Specs/constraint.xml +++ b/P5/Source/Specs/constraint.xml @@ -7,7 +7,7 @@ $Date$ $Id$ --> - + constraint rules the formal rules of a constraint @@ -23,8 +23,9 @@ $Id$ - a main title must be supplied - + + a main title must be supplied + @@ -34,11 +35,11 @@ $Id$ (output = (ident(title) ident(author) "You must supply a title or an author")) - + - \ No newline at end of file + diff --git a/P5/Source/Specs/constraintSpec.xml b/P5/Source/Specs/constraintSpec.xml index ca2aad8f6f..8cdbc4bf2c 100644 --- a/P5/Source/Specs/constraintSpec.xml +++ b/P5/Source/Specs/constraintSpec.xml @@ -47,10 +47,12 @@ $Id$ Relationship between scheme attribute and contents: Schematron 1.x - Rules + + Rules in the Schematron 1.* language must be inside a constraintSpec with a value other than 'schematron' or 'isoschematron' on the scheme attribute + @@ -63,11 +65,19 @@ $Id$ - + + - - An ISO Schematron constraint specification for a macro should not - have an 'assert' or 'report' element without a parent 'rule' element + + + + The use of an <sch:assert> or <sch:report> that does not have a context (i.e., does not have an ancestor <sch:rule> with a @context attribute) in an ISO Schematron constraint specification is deprecated, and will become invalid after 2024-06-30. DEBUG: I am in . @@ -90,8 +100,7 @@ $Id$ Not sure, maybe @scheme should not be allowed when mode=change or mode=delete. Hmmm ... --> - supplies the name of the language in which the constraints - are defined + supplies the name of the language in which the constraints are defined @@ -143,8 +152,9 @@ $Id$ Enforce the presence of the spanTo attribute - The spanTo= attribute of - is required. + + The spanTo= attribute of is required. + @@ -155,9 +165,11 @@ $Id$ Implement an accessibility rule which says that pictures should have textual explanations - You should - provide information in a figure from which - we can construct an alt attribute in HTML + + You should + provide information in a figure from which + we can construct an alt attribute in HTML + diff --git a/P5/Source/Specs/damageSpan.xml b/P5/Source/Specs/damageSpan.xml index 8eece011b5..9c65b3d44e 100644 --- a/P5/Source/Specs/damageSpan.xml +++ b/P5/Source/Specs/damageSpan.xml @@ -13,14 +13,11 @@ $Id$ fragmento de texto dañado partie de texte endommagée porzione di testo danneggiata - marks the beginning of a longer sequence of text which is - damaged in some way but still legible. + marks the beginning of a longer sequence of text which is damaged in some way but still legible. 어떤 방식으로 손상되었지만 여전히 읽을 수 있는 긴 텍스트 연쇄 시작부를 표시한다. marca el inicio de una secuencia de texto larga dañada de alguna manera pero aún legible. - 読める程度の損傷がある、一連のテキストの始点を示す。 - - marque le début d'une longue partie de texte, -endommagée d'une manière quelconque mais toujours lisible. + 読める程度の損傷がある、一連のテキストの始点を示す。 + marque le début d'une longue partie de texte, endommagée d'une manière quelconque mais toujours lisible. segnala l'inizio di una sequenza più estesa di testo danneggiata ma ancora leggibile @@ -32,13 +29,17 @@ endommagée d'une manière quelconque mais toujours lisible. - The @spanTo attribute of is required. + + The @spanTo attribute of is required. + - L'attribut spanTo est requis. + + L'attribut spanTo est requis. + @@ -110,4 +111,4 @@ the start of the undamaged part of the text. ...

- \ No newline at end of file + diff --git a/P5/Source/Specs/delSpan.xml b/P5/Source/Specs/delSpan.xml index 9f1a06edb9..ead289145d 100644 --- a/P5/Source/Specs/delSpan.xml +++ b/P5/Source/Specs/delSpan.xml @@ -14,14 +14,10 @@ $Id$ partie de texte supprimée fragmento de texto omitido porzione di testo cancellata - marks the beginning of a longer sequence of text deleted, -marked as deleted, or otherwise signaled as superfluous or spurious by an -author, scribe, annotator, or corrector. + marks the beginning of a longer sequence of text deleted, marked as deleted, or otherwise signaled as superfluous or spurious by an author, scribe, annotator, or corrector. 작가, 필기사, 주석자 또는 교정자에 의해 삭제되었다고 표시되었거나, 잉여적으로 추가되거나 위조된 것으로 표시된 긴 연쇄의 텍스트 시작부를 표시한다. 標記一較長連續性文字之開端，該文字由作者、抄寫者、註解者、或更正者刪除、標上刪除記號、或者標明為多餘或偽造。 - 著者・筆写者・注釈者・校正者により、削除または削除として符号化または - 余分なものまたは間違いとして示されている、長めのテキスト部分の始点を - 示す。 + 著者・筆写者・注釈者・校正者により、削除または削除として符号化または 余分なものまたは間違いとして示されている、長めのテキスト部分の始点を 示す。 marque le début d'une longue partie de texte supprimée, signalée comme supprimée ou bien signalée comme superflue ou fausse par un auteur, un copiste, un annotateur ou un correcteur. señala el inicio de un fragmento largo de texto omitido, o marcado como cancelado o como supérfluo o espurio, por un autor, un transcriptor, un comentarista o un corrector. segnala l'inizio di una porzione di testo più lunga cancellata, indicata come cancellata, o indicata come superflua o spuria da un autore, un trascrittore, un annotatore o un correttore @@ -36,13 +32,17 @@ author, scribe, annotator, or corrector. - The @spanTo attribute of is required. + + The @spanTo attribute of is required. + - L'attribut spanTo est requis. + + L'attribut spanTo est requis. + @@ -131,4 +131,4 @@ the resumption of the text. ...

- \ No newline at end of file + diff --git a/P5/Source/Specs/dimensions.xml b/P5/Source/Specs/dimensions.xml index da74e64b90..c6f0057027 100644 --- a/P5/Source/Specs/dimensions.xml +++ b/P5/Source/Specs/dimensions.xml @@ -7,7 +7,7 @@ $Date$ $Id$ --> - + dimensions dimensions contains a dimensional specification. @@ -30,16 +30,22 @@ $Id$ + - - The element may appear once only - - - The element may appear once only - - - The element may appear once only - + + + The element may appear once only + + + The element may appear once only + + + The element may appear once only + + @@ -54,16 +60,12 @@ $Id$ - dimensions relate to one or more leaves (e.g. a single leaf, a -gathering, or a separately bound part) + dimensions relate to one or more leaves (e.g. a single leaf, a gathering, or a separately bound part) 하나 이상의 종이의 장과 관련된 차원(예, 한 장, 접지 모음, 또는 각각 분리되어 엮여진 부분) 一張或多張頁面的尺寸大小 (例如單一頁面、聚集頁面、或分開裝訂的部份) las dimensiones se relacionan con una o más hojas (p.ej. una sola hoja, un conjunto, o un intervalo) - 葉の状態を示す。例えば、一葉、葉の丁合(折丁)、独立した一枚を - まとめたもの、など。 - les dimensions concernent une ou -plusieurs feuilles (par exemple une feuille unique, un ensemble de -feuilles ou une partie reliée séparément). + 葉の状態を示す。例えば、一葉、葉の丁合(折丁)、独立した一枚を まとめたもの、など。 + les dimensions concernent une ou plusieurs feuilles (par exemple une feuille unique, un ensemble de feuilles ou une partie reliée séparément). le dimensioni si riferiscono a uno o più fogli (per esempio un foglio, una raccolta, o una parte rilegata separatamente) @@ -74,38 +76,26 @@ preparation for writing. las dimensiones se refieren al área de una hoja que se ha preparado para la escritura. 書記の準備として罫が引かれている領域を示す。 - les dimensions concernent la zone de -la réglure d'une feuille. + les dimensions concernent la zone de la réglure d'une feuille. le dimensioni si riferiscono alla porzione di un foglio sulla quale sono state disegnate delle righe al fine di scriverci - dimensions relate to the area of a leaf which has been pricked -out in preparation for ruling (used where this differs significantly -from the ruled area, or where the ruling is not measurable). + dimensions relate to the area of a leaf which has been pricked out in preparation for ruling (used where this differs significantly from the ruled area, or where the ruling is not measurable). (줄 그은 영역과 다르거나 영역 구분이 측정되지 않은 곳에서 사용되는) 줄을 긋기 위한 준비 과정에서 구멍 뚫은 영역과 관련된 차원 頁面上刺好記號以備劃線的範圍大小 (用在和畫線範圍不同的位置，或是畫線無法測量的位置) 。 las dimensiones se refieren al área de una hoja que ha sido agujereada en la preparación para la escritura (utilizado donde esto difiere significativamente del área lineada, o donde la lineación no es mensurable). - 罫を引く準備として開けられた穴がある領域を示す。これは、罫付 - き領域とも、罫が読み取れない領域とも異なる。 - les dimensions concernent la zone -d'une feuille qui a été piquée pour préparer la réglure (à utiliser -lorsqu'elle diffère significativement de la zone réglée ou lorsque la -réglure n'est pas mesurable). + 罫を引く準備として開けられた穴がある領域を示す。これは、罫付 き領域とも、罫が読み取れない領域とも異なる。 + les dimensions concernent la zone d'une feuille qui a été piquée pour préparer la réglure (à utiliser lorsqu'elle diffère significativement de la zone réglée ou lorsque la réglure n'est pas mesurable). le dimensioni si riferiscono alla porzione di un foglio sulla quale è stata indicata la posizione dei fori da praticare al fine di imprimervi delle righe (si usa quando la porzione da rigare è molto diversa da quella già rigata o quando la rigatura non è misurabile) - dimensions relate to the area of a leaf which has been written, -with the height measured from the top of the minims on the top line of -writing, to the bottom of the minims on the bottom line of writing. + dimensions relate to the area of a leaf which has been written, with the height measured from the top of the minims on the top line of writing, to the bottom of the minims on the bottom line of writing. 글의 첫 번째 줄 상단부터 마지막 줄 하단까지 측정된 높이를 통해 한 장의 글 쓴 영역과 관련된 차원 頁面上已書寫文字的範圍大小，高度由最頂行文字的頂端測量至最底行文字的底端。 las dimensiones se refiere al área de una hoja que ha sido escrita, con la altura medida desde la línea superior de escritura a la parte inferior de la última línea de la escritura. 書記領域を示す。先頭文字行から最終文字行までの高さ。 - les dimensions concernent la zone -écrite de la feuille, dont la hauteur est mesurée depuis le haut des -blancs sur la ligne d'écriture supérieure jusqu'au dernier des blancs -sur la dernière ligne écrite. + les dimensions concernent la zone écrite de la feuille, dont la hauteur est mesurée depuis le haut des blancs sur la ligne d'écriture supérieure jusqu'au dernier des blancs sur la dernière ligne écrite. le dimensioni si riferiscono ad un'area del foglio su cui è stato scritto e la cui altezza è misurata dalla cima degli uncini sulla prima riga scritta fino al fondo degli uncini sull'ultima riga scritta @@ -128,14 +118,12 @@ sur la dernière ligne écrite. le dimensioni si riferiscono alla rilegatura nella quale è contenuto il codice o manoscritto - dimensions relate to the box or other container in which the -manuscript is stored. + dimensions relate to the box or other container in which the manuscript is stored. 원고가 보관된 박스 또는 용기와 관련된 차원 手稿所儲存的箱子或其他容器的尺寸大小 las dimensiones se refieren a la caja o a cualquier otro contenedor en qué se conserva el manuscrito. 当該写本を入れるケースの大きさを示す。 - les dimensions concernent la boîte ou -autre conteneur dans lequel le manuscrit est conservé. + les dimensions concernent la boîte ou autre conteneur dans lequel le manuscrit est conservé. le dimensioni si riferiscono alla scatola o ad altro contenitore nel quale è custodito il manoscritto diff --git a/P5/Source/Specs/div.xml b/P5/Source/Specs/div.xml index 7422d13557..4df5f44a33 100644 --- a/P5/Source/Specs/div.xml +++ b/P5/Source/Specs/div.xml @@ -19,13 +19,10 @@ $Id$ 텍스트의 전면부, 본문, 후면부의 하위 구역을 포함한다. 文本的正文前資訊、正文、及正文後資訊的分段。 前付、本文、後付中のテキスト部分を示す。 - contient une subdivision dans le texte préliminaire, dans le - corps d’un texte ou dans le texte postliminaire. + contient une subdivision dans le texte préliminaire, dans le corps d’un texte ou dans le texte postliminaire. enthält einen Unterabschnitt in Vorspann (front), Textkörper oder Nachspann (back) eines Textes. - contiene una subdivisión del paratexto inicial, del - cuerpo del texto o del paratexto final. - contiene una suddivisione del peritesto iniziale, del - corpo del testo, o del peritesto finale + contiene una subdivisión del paratexto inicial, del cuerpo del texto o del paratexto final. + contiene una suddivisione del peritesto iniziale, del corpo del testo, o del peritesto finale @@ -76,16 +73,20 @@ $Id$ - - Abstract model violation: Lines may not contain higher-level structural elements such as div, unless div is a descendant of floatingText. - + + + Abstract model violation: Lines may not contain higher-level structural elements such as div, unless div is a descendant of floatingText. + + - - Abstract model violation: p and ab may not contain higher-level structural elements such as div, unless div is a descendant of floatingText. - + + + Abstract model violation: p and ab may not contain higher-level structural elements such as div, unless div is a descendant of floatingText. + + @@ -164,4 +165,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/join.xml b/P5/Source/Specs/join.xml index 3bb10bfcb7..5f17d3cc06 100644 --- a/P5/Source/Specs/join.xml +++ b/P5/Source/Specs/join.xml @@ -1,7 +1,7 @@ - + join jointure identifies a possibly fragmented segment of text, by pointing at the possibly discontiguous elements which compose it. @@ -17,19 +17,19 @@ - - - - - - - + + + + + - -You must supply at least two values for @target on - + + + You must supply at least two values for @target on + + @@ -199,4 +199,4 @@ You must supply at least two values for @target on - \ No newline at end of file + diff --git a/P5/Source/Specs/l.xml b/P5/Source/Specs/l.xml index 906375ab08..da11c15bd8 100644 --- a/P5/Source/Specs/l.xml +++ b/P5/Source/Specs/l.xml @@ -41,9 +41,9 @@ - - Abstract model violation: Lines may not contain lines or lg elements. - + + Abstract model violation: Lines may not contain lines or lg elements. + @@ -67,4 +67,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/lg.xml b/P5/Source/Specs/lg.xml index dabe40e72d..6687c6d983 100644 --- a/P5/Source/Specs/lg.xml +++ b/P5/Source/Specs/lg.xml @@ -15,17 +15,13 @@ grupo de versos un gruppo di versi Gruppe von Vers(zeil)en - contains one or more verse lines functioning as a formal unit, e.g. a stanza, refrain, - verse paragraph, etc. + contains one or more verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc. 예를 들어, 연, 후렴구, 운문 단락과 같이 형식적 단위로 기능하는 운문 행군을 포함한다. 包含形式上視為一組的詩行，例如詩節、疊句、韻文段落等。 形式単位としてある、ある韻文の行をまとまりを示す。例えば、連、リフレ イン、詩節など。 - contient un groupe de vers fonctionnant comme une unité - formelle, par exemple une strophe, un refrain, un paragraphe en vers, etc. - contiene un grupo de versos que funcionan como una - unidad formal, p.ej. una estrofa, un refrán, un estribillo, etc. - contiene un gruppo di versi che costituiscono un'unità - formale, per esempio una stanza, un refrain, un paragrafo in versi, ecc. + contient un groupe de vers fonctionnant comme une unité formelle, par exemple une strophe, un refrain, un paragraphe en vers, etc. + contiene un grupo de versos que funcionan como una unidad formal, p.ej. una estrofa, un refrán, un estribillo, etc. + contiene un gruppo di versi che costituiscono un'unità formale, per esempio una stanza, un refrain, un paragrafo in versi, ecc. enthält eine oder mehrere Verse bzw. Verszeilen, die zusammen eine formale Einheit (z. B. Strophe, Refrain) bilden. @@ -64,15 +60,16 @@ - An lg element - must contain at least one child l, lg, or gap element. + + An lg element must contain at least one child l, lg, or gap element. + - - Abstract model violation: Lines may not contain line groups. - + + Abstract model violation: Lines may not contain line groups. + @@ -133,12 +130,10 @@ -

contains verse lines or nested line groups only, possibly prefixed by a - heading.

+

contains verse lines or nested line groups only, possibly prefixed by a heading.

 -

ne contient que des vers ou des groupes de vers enchâssés, - éventuellement précédés d'un titre.

+

ne contient que des vers ou des groupes de vers enchâssés, éventuellement précédés d'un titre.

韻文の行または(普通は見出しが付く)入れ子化された行グループのみを示 す。

@@ -152,4 +147,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/link.xml b/P5/Source/Specs/link.xml index 520264faf1..65b7197042 100644 --- a/P5/Source/Specs/link.xml +++ b/P5/Source/Specs/link.xml @@ -20,7 +20,9 @@ - You must supply at least two values for @target or on + + You must supply at least two values for @target or on + @@ -51,4 +53,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/modelSequence.xml b/P5/Source/Specs/modelSequence.xml index cbd5e51ba6..6e6058ad05 100644 --- a/P5/Source/Specs/modelSequence.xml +++ b/P5/Source/Specs/modelSequence.xml @@ -8,8 +8,7 @@ --> - any sequence of model or modelSequence elements which - is to be processed as a single set of actions + any sequence of model or modelSequence elements which is to be processed as a single set of actions @@ -24,22 +23,22 @@ - The 'model' children - of a 'modelSequence' element inherit the @output attribute of the - parent 'modelSequence', and thus should not have their own + + The 'model' children + of a 'modelSequence' element inherit the @output attribute of the + parent 'modelSequence', and thus should not have their own + - the condition under which this model applies - given as an XPath Predicate Expression + the condition under which this model applies given as an XPath Predicate Expression - whether to obey any rendition attribute that is - present + whether to obey any rendition attribute that is present @@ -51,16 +50,13 @@ - the output is intended for presentation in a - web format + the output is intended for presentation in a web format - the output is intended for presentation in a - print format + the output is intended for presentation in a print format - the output is intended for presentation in a - plain text format + the output is intended for presentation in a plain text format diff --git a/P5/Source/Specs/moduleRef.xml b/P5/Source/Specs/moduleRef.xml index 2c1e52ba10..064ef701ee 100644 --- a/P5/Source/Specs/moduleRef.xml +++ b/P5/Source/Specs/moduleRef.xml @@ -7,7 +7,7 @@ $Date$ $Id$ --> - + module reference 모듈 참조 referencia de módulo @@ -17,8 +17,7 @@ $Id$ 하나의 스키마로 통합된 모듈을 참조한다. 參照一個被併入某一模型的模組。 スキーマに組み入れられるモジュールを参照する。 - référence un module qui doit être incorporé dans - un schéma. + référence un module qui doit être incorporé dans un schéma. indica un módulo que se ha de incluir al interno de un esquema. indica un modulo da includere all'interno di uno schema @@ -26,30 +25,27 @@ $Id$ - - - + - - -Child elements of are only allowed when an external module is being loaded - - + + + Child elements of are only allowed when an external module is being loaded + + - specifies a default prefix which will be - prepended to all patterns from the imported module + specifies a default prefix which will be prepended to all patterns from the imported module The prefix attribute - of should not match that of any other - element (it would defeat the purpose) + of should not match that of any other + element (it would defeat the purpose) @@ -75,8 +71,7 @@ specified module into the schema being defined. - supplies a list of the elements which are not to be copied from the -specified module into the schema being defined. + supplies a list of the elements which are not to be copied from the specified module into the schema being defined. @@ -95,8 +90,7 @@ specified module into the schema being defined. URL refers to a non-TEI module of RELAX NG code by external location se refiere a un módulo no-de-TEI del código de RELAX NG mediante una localización externa - fait référence à un module non TEI de code -RELAX NG par une localisation externe. + fait référence à un module non TEI de code RELAX NG par une localisation externe. indica la collocazione esterna di un modulo non TEI che utilizza il codice RELAX NG @@ -121,7 +115,6 @@ RELAX NG par une localisation externe.

This includes all elements available from the linking module except for the link and linkGrp elements.

 - @@ -173,4 +166,4 @@ processor should signal an error.

- \ No newline at end of file + diff --git a/P5/Source/Specs/msIdentifier.xml b/P5/Source/Specs/msIdentifier.xml index 6fa7e4a4d2..93886ac457 100644 --- a/P5/Source/Specs/msIdentifier.xml +++ b/P5/Source/Specs/msIdentifier.xml @@ -7,15 +7,14 @@ $Date$ $Id$ --> - + manuscript identifier 원고 확인소 identificador del manuscrito identifiant du manuscrit identificatore del manoscritto - contains the information required to identify -the manuscript or similar object being described. + contains the information required to identify the manuscript or similar object being described. 기술되고 있는 원고를 식별하기 위해 필요한 정보를 포함한다. 包含識別敘述中的手稿所需要的資訊。 解説されている手書き資料を特定するために必要な情報を示す。 @@ -44,7 +43,11 @@ the manuscript or similar object being described. - An msIdentifier must contain either a repository or location. + + An msIdentifier must contain either a repository or location. + diff --git a/P5/Source/Specs/p.xml b/P5/Source/Specs/p.xml index 1bf9c34e77..c5996253af 100644 --- a/P5/Source/Specs/p.xml +++ b/P5/Source/Specs/p.xml @@ -35,16 +35,35 @@ - - Abstract model violation: Paragraphs may not occur inside other paragraphs or ab elements. - + + + Abstract model violation: Paragraphs may not occur inside other paragraphs or ab elements. + + - - Abstract model violation: Lines may not contain higher-level structural elements such as div, p, or ab, unless p is a child of figure or note, or is a descendant of floatingText. - + + + Abstract model violation: Lines may not contain higher-level structural elements such as div, p, or ab, unless p is a child of figure or note, or is a descendant of floatingText. + + @@ -79,4 +98,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/ptr.xml b/P5/Source/Specs/ptr.xml index acebc97a7e..585677e5d4 100644 --- a/P5/Source/Specs/ptr.xml +++ b/P5/Source/Specs/ptr.xml @@ -7,7 +7,7 @@ $Id$ --> - + pointer 포인터 @@ -34,8 +34,9 @@ - Only one of the -attributes @target and @cRef may be supplied on . + + Only one of the attributes @target and @cRef may be supplied on . + @@ -49,4 +50,4 @@ attributes @target and @cRef may be supplied on . - \ No newline at end of file + diff --git a/P5/Source/Specs/quotation.xml b/P5/Source/Specs/quotation.xml index 92ad6dd141..931595670a 100644 --- a/P5/Source/Specs/quotation.xml +++ b/P5/Source/Specs/quotation.xml @@ -11,31 +11,28 @@ $Id$ quotation citation specifies editorial practice adopted with respect to quotation marks in the original. - décrit la pratique éditoriale adoptée par rapport aux - guillements dans l’original. + décrit la pratique éditoriale adoptée par rapport aux guillements dans l’original. 원본 인용 부호에 관해 채택한 편집 방식을 명시한다. 說明在編輯上是如何處理來源文件中的引文符號。 元資料にあった引用をどのように編集したのかを示す。 - beschreibt die editorische Praxis bezüglich der - Anführungszeichen im Originaltext. - indica las prácticas editoriales adoptadas respecto al - entrecomillado en el original. - specifica le pratiche editoriali rispetto all'uso delle - virgolette nell'originale + beschreibt die editorische Praxis bezüglich der Anführungszeichen im Originaltext. + indica las prácticas editoriales adoptadas respecto al entrecomillado en el original. + specifica le pratiche editoriali rispetto all'uso delle virgolette nell'originale - - - + - -On , either the @marks attribute should be used, or a paragraph of description provided + + + On , either the @marks attribute should be used, or a paragraph of description provided + + @@ -88,33 +85,6 @@ On , either the @marks attribute should be used, or a paragraph of descri - - @@ -171,4 +141,4 @@ On , either the @marks attribute should be used, or a paragraph of descri - \ No newline at end of file + diff --git a/P5/Source/Specs/rdgGrp.xml b/P5/Source/Specs/rdgGrp.xml index 72c65906b4..bede7986a7 100644 --- a/P5/Source/Specs/rdgGrp.xml +++ b/P5/Source/Specs/rdgGrp.xml @@ -14,15 +14,12 @@ $Id$ groupe de leçons grupo de lecturas gruppo di letture - within a textual variation, -groups two or more readings perceived to have a genetic -relationship or other affinity. + within a textual variation, groups two or more readings perceived to have a genetic relationship or other affinity. 텍스트 변이형 내에서 계통 관계 또는 유사 관계로 이해되는 둘 이상의 독법을 모아 놓는다. 原文變異中，匯集兩個或多個認為具有根源關係或於其他方面性質類似的對應本。 異なるテキストで、系統関係や類縁性があるとされる、二つ以上の読みをま とめる。 - regroupe deux leçons ou plus qui sont perçues - comme ayant une relation génétique ou une autre affinité. + regroupe deux leçons ou plus qui sont perçues comme ayant une relation génétique ou une autre affinité. agrupa al interno de una variante textual dos o más lecturas consideradas emparentadas o afines. all'interno di una variante testuale raggruppa due o più letture considerate imparentate o affini @@ -43,7 +40,9 @@ relationship or other affinity. - Only one <lem> element may appear within a <rdgGrp> + + Only one <lem> element may appear within a <rdgGrp> + @@ -103,4 +102,4 @@ relationship or other affinity. - \ No newline at end of file + diff --git a/P5/Source/Specs/ref.xml b/P5/Source/Specs/ref.xml index 1c6f9dd713..0458df4ff0 100644 --- a/P5/Source/Specs/ref.xml +++ b/P5/Source/Specs/ref.xml @@ -7,24 +7,22 @@ $Id$ --> - + reference 참조 referencia référence riferimento - Referenz + Referenz defines a reference to another location, possibly modified by additional text or comment. 부가적인 텍스트 또는 해설로 수정될 수 있는, 다른 위치로 참조를 정의한다. 標明與其他位置互相參照的符號，或許包含附加的文字或註解。 他の場所への参照を定義する。多くは、追加テキストまたはコメントを含む。 définit une référence vers un autre emplacement, la référence étant éventuellement modifiée ou complétée par un texte ou un commentaire. - define una referencia a otra localización, posiblemente - modificada por un texto o comentario adicional. - definisce un riferimento ad un'altra posizione, può - essere modificata da un commento o testo ulteriore - definiert einen externen oder internen Verweis, der auch durch einen zusätzlichen Text oder Kommentar ergänzt werden kann. + define una referencia a otra localización, posiblemente modificada por un texto o comentario adicional. + definisce un riferimento ad un'altra posizione, può essere modificata da un commento o testo ulteriore + definiert einen externen oder internen Verweis, der auch durch einen zusätzlichen Text oder Kommentar ergänzt werden kann. @@ -40,9 +38,9 @@ - Only one of the - attributes @target' and @cRef' may be supplied on - + + Only one of the attributes @target' and @cRef' may be supplied on + @@ -60,12 +58,12 @@ Cf. tout particulièrement le vers 234 du Livre I - + 關於第二行， 請參考 下列 - 慣用語 - . + 慣用語 + .

The target and cRef attributes are mutually exclusive.

@@ -77,10 +75,10 @@

属性targetとcRefは、排他的に使用される。

-

Die target und cRef-Attribute schließen sich gegenseitig aus.

+

Die target und cRef-Attribute schließen sich gegenseitig aus.

 - \ No newline at end of file + diff --git a/P5/Source/Specs/relatedItem.xml b/P5/Source/Specs/relatedItem.xml index 3cf81f3a14..1c88796164 100644 --- a/P5/Source/Specs/relatedItem.xml +++ b/P5/Source/Specs/relatedItem.xml @@ -8,42 +8,31 @@ --> - contains or references some other bibliographic item which is related to the present one in - some specified manner, for example as a constituent or alternative version of it. - 구성물이나 대체 버전과 같이 현 항목과 특정 방식으로 관련된 다른 서지 항목을 명시적 방식에 따라 - 포함하거나 지시한다. + contains or references some other bibliographic item which is related to the present one in some specified manner, for example as a constituent or alternative version of it. + 구성물이나 대체 버전과 같이 현 항목과 특정 방식으로 관련된 다른 서지 항목을 명시적 방식에 따라 포함하거나 지시한다. 包含或參照到其他書目項目，該些項目與目前的書目項目在某種程度上相關，例如作為其組成或者替代項目。 当該内容と関連する書誌情報項目を示す、または参照する。例えば、構成要 素または他の版など。 - contient ou référe à un autre élément bibliographique - ayant une relation quelconque avec l'objet décrit, par exemple comme faisant partie d'une version alternative de celui-ci, ou bien en étant une version alternative. - contiene o si riferisce ad altra entità bibliografica - legata alla presente tramite una relazione specificata quale, per esempio, versione costitutiva - o alternativa - contiene o refiere algún otro elemento bibliográfico que - se relaciona con el actual de alguna manera, por ejemplo como un versión complementaria o - alternativa de este. - enthält oder verweist auf ein anderes bibliografisches Objekt, welches zu dem aktuellen in einer - bestimmten Beziehung steht, z. B. als Bestandteil oder Alternativfassung. + contient ou référe à un autre élément bibliographique ayant une relation quelconque avec l'objet décrit, par exemple comme faisant partie d'une version alternative de celui-ci, ou bien en étant une version alternative. + contiene o si riferisce ad altra entità bibliografica legata alla presente tramite una relazione specificata quale, per esempio, versione costitutiva o alternativa + contiene o refiere algún otro elemento bibliográfico que se relaciona con el actual de alguna manera, por ejemplo como un versión complementaria o alternativa de este. + enthält oder verweist auf ein anderes bibliografisches Objekt, welches zu dem aktuellen in einer bestimmten Beziehung steht, z. B. als Bestandteil oder Alternativfassung. - - - - - - + + + + - -If the @target attribute on is used, the -relatedItem element must be empty - A relatedItem element should have either a 'target' attribute - or a child element to indicate the related bibliographic item + + If the @target attribute on is used, the relatedItem element must be empty + A relatedItem element should have either a @target attribute or a child element to indicate the related bibliographic item + @@ -101,4 +90,4 @@ relatedItem element must be empty - \ No newline at end of file + diff --git a/P5/Source/Specs/relation.xml b/P5/Source/Specs/relation.xml index 51c10ca188..ad9db4ebad 100644 --- a/P5/Source/Specs/relation.xml +++ b/P5/Source/Specs/relation.xml @@ -1,18 +1,20 @@ - +--> + + relationship 관련성 人際關係 relation relación relazione - describes any kind of relationship or linkage amongst a - specified group of places, events, persons, objects or other items. + describes any kind of relationship or linkage amongst a specified group of places, events, persons, objects or other items. 명시된 참여자군 사이에 관련성 또는 연결 종류를 기술한다. 描述在特定團體中，參與者彼此之間的關係或關聯。 指定された参加者グループ間の関連性の種類を示す。 @@ -30,12 +32,14 @@ $Id$ - + - One of the attributes 'name', 'ref' or 'key' must be supplied + + One of the attributes @name, @ref or @key must be supplied + - + - Only one of the attributes @active and @mutual may be supplied + + Only one of the attributes @active and @mutual may be supplied + - + - the attribute 'passive' may be supplied only if the attribute 'active' is supplied + + the attribute @passive may be supplied only if the attribute @active is supplied + @@ -62,32 +70,26 @@ $Id$ att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized. - indicates one or more systems or calendars to which the - date represented by the content of this element belongs. + indicates one or more systems or calendars to which the date represented by the content of this element belongs. 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. 指明該日期表示所使用的曆法計算系統。 この要素を含むコンテントにおける日付の暦やシステムを示す。 - indique le système ou le calendrier auquel - appartient la date exprimée dans le contenu de l'élément. - indica el sistema o calendario en que se muestra - una fecha. - indica il sistema o calendario al quale la data - appartiene. + indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. + indica el sistema o calendario en que se muestra una fecha. + indica il sistema o calendario al quale la data appartiene. - + - - - @calendar indicates one or more - systems or calendars to which the date represented by the content of this element belongs, - but this element has no textual content. - - + + + @calendar indicates one or more + systems or calendars to which the date represented by the content of this element belongs, + but this element has no textual content. + + - - - + supplies a name for the kind of relationship of which this is an instance. 이것이 실례인 관련성 종류에 대한 이름을 제공한다. @@ -100,20 +102,15 @@ $Id$ - identifies the active participants in a non-mutual relationship, or all the participants in a mutual - one. - identifica los participantes activos en una relación no-mutua, o todos los participantes de - una mutua. - identifie les participants actifs dans une relation à sens unique, ou tous les participants - dans une relation réciproque. - identifica i partecipanti attivi in una relazione di non reciprocità, oppure tutti i - partecipanti in una relazione di reciprocità + identifies the active participants in a non-mutual relationship, or all the participants in a mutual one. + identifica los participantes activos en una relación no-mutua, o todos los participantes de una mutua. + identifie les participants actifs dans une relation à sens unique, ou tous les participants dans une relation réciproque. + identifica i partecipanti attivi in una relazione di non reciprocità, oppure tutti i partecipanti in una relazione di reciprocità supplies a list of participants amongst all of whom the relationship holds equally. - proporciona una lista de participantes entre los cuales se establece una idéntica - relación + proporciona una lista de participantes entre los cuales se establece una idéntica relación fournit une liste de participants entre lesquels la relation est réciproque. fornisce una lista di partecipanti tra i quali c'è una relazione paritaria @@ -187,4 +184,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/rt.xml b/P5/Source/Specs/rt.xml index 69aa85d21b..2af924ae77 100644 --- a/P5/Source/Specs/rt.xml +++ b/P5/Source/Specs/rt.xml @@ -30,18 +30,19 @@ ルビテキストの対象へのポインタを示す。 - + Enforce that either target or both from and to (or none) are used, but not target in combination with either from or to. - When target= is - present, neither from= nor to= should be. + + When target= is present, neither from= nor to= should be. + @@ -59,15 +60,16 @@ - + Enforce the presence of to iff there is a from. - When from= is present, the to= - attribute of is required. + + When from= is present, the to= attribute of is required. + @@ -79,15 +81,16 @@ - + Enforce the presence of from iff there is a to. - When to= is present, the from= - attribute of is required. + + When to= is present, the from= attribute of is required. + @@ -115,4 +118,4 @@ - \ No newline at end of file + diff --git a/P5/Source/Specs/s.xml b/P5/Source/Specs/s.xml index 97094b2d4a..f763f3dcd1 100644 --- a/P5/Source/Specs/s.xml +++ b/P5/Source/Specs/s.xml @@ -7,7 +7,7 @@ $Date$ $Id$ --> - + s-unit s-단위 句子單元 @@ -31,15 +31,17 @@ $Id$ - + - You may not nest one s element within - another: use seg instead + + You may not nest one s element within another: use seg instead + @@ -93,4 +95,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/secFol.xml b/P5/Source/Specs/secFol.xml index 5abad24f53..7f7e962d31 100644 --- a/P5/Source/Specs/secFol.xml +++ b/P5/Source/Specs/secFol.xml @@ -14,15 +14,12 @@ $Id$ segundo folio deuxième folio secondo foglio - marks the word or words taken from a fixed point in a codex - (typically the beginning of the second leaf) in order to provide a unique identifier for it. + marks the word or words taken from a fixed point in a codex (typically the beginning of the second leaf) in order to provide a unique identifier for it. 고유한 확인소를 제공하기 위해 미제본 원고의 고정 위치(일반적으로 두 번째 장의 시작)에서 얻어진 단어 또는 단어군 從手抄本中固定位置所拿開的一個或多個字 (通常在第二張書頁的開頭) ，目的是提供一個專有的識別符號。 ユニークな識別子を示すために、冊子中の特定点にある単語を示す。 - le mot ou les mots repris d'un point précisément - connu d'un codex (comme le début du second feuillet) pour identifier celui-ci de façon - univoque. + le mot ou les mots repris d'un point précisément connu d'un codex (comme le début du second feuillet) pour identifier celui-ci de façon univoque. la palabra o palabras extraídas de un punto preciso de un códex (normalmente el inicio del segundo folio) con el fin de identificar lo mismo en modo unívoco. la parola o le parole estratte da un punto preciso di un codice (di solito l'inizio del secondo foglio) al fine di identificare lo stesso in modo univoco @@ -42,7 +39,9 @@ $Id$ At least, that's what I think is going on. —Syd, 2018-10-01 --> - The element should not be used outside of msDesc. + + The element should not be used outside of msDesc. + diff --git a/P5/Source/Specs/sequence.xml b/P5/Source/Specs/sequence.xml index c2c397c3e3..216a677fca 100644 --- a/P5/Source/Specs/sequence.xml +++ b/P5/Source/Specs/sequence.xml @@ -19,7 +19,9 @@ $Id$ - The sequence element must have at least two child elements + + The sequence element must have at least two child elements + @@ -48,4 +50,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Source/Specs/shift.xml b/P5/Source/Specs/shift.xml index 51f6dba6e8..d893fa23ac 100644 --- a/P5/Source/Specs/shift.xml +++ b/P5/Source/Specs/shift.xml @@ -7,7 +7,7 @@ $Date$ $Id$ --> - + shift changement marks the point at which some paralinguistic feature of a series of @@ -27,16 +27,18 @@ utterances by any one speaker changes. - -The @new attribute should always be supplied; use the special value -"normal" to indicate that the feature concerned ceases to be -remarkable at this point. + + + The @new attribute should always be supplied; use the special value + "normal" to indicate that the feature concerned ceases to be + remarkable at this point. + + - a -paralinguistic feature. + a paralinguistic feature. 준언어적 자질 附屬語言特性 発話(パラ言語)素性。 @@ -106,8 +108,7 @@ paralinguistic feature. 명시된 준언어적 자질의 새로운 상태를 명시한다. 說明改變後的附屬語言特性狀況。 発話(パラ言語)素性の、新しい状態を示す。 - précise le nouvel état de la - caractéristique paralinguistique en question. + précise le nouvel état de la caractéristique paralinguistique en question. especifica el nuevo estado del fenómeno paralingüístico especificado. specifica il nuovo stato del fenomeno paralinguistico specificato @@ -119,7 +120,7 @@ paralinguistic feature.

Si aucune valeur n'est spécifiée, on suppose que le trait concerné cesse - d'être remarquable. La valeur normal a le même effet.

+ d'être remarquable. La valeur normal a le même effet.

@@ -129,13 +130,12 @@ paralinguistic feature. - Elizabeth Yes Come and try this - come on + come on @@ -173,4 +173,4 @@ very loudly.

- \ No newline at end of file + diff --git a/P5/Source/Specs/signatures.xml b/P5/Source/Specs/signatures.xml index a85faf4f06..3217422039 100644 --- a/P5/Source/Specs/signatures.xml +++ b/P5/Source/Specs/signatures.xml @@ -34,7 +34,9 @@ $Id$ At least, that's what I think is going on. —Syd, 2018-10-01 --> - The element should not be used outside of msDesc. + + The element should not be used outside of msDesc. + diff --git a/P5/Source/Specs/span.xml b/P5/Source/Specs/span.xml index 60c8cda740..7f9528191f 100644 --- a/P5/Source/Specs/span.xml +++ b/P5/Source/Specs/span.xml @@ -7,17 +7,14 @@ $Date$ $Id$ --> - + associates an interpretative annotation directly with a span of text. 해석적 부호를 텍스트의 일정 부분과 직접적으로 연결시킨다. 將詮釋性註釋直接和一段文字段連結。 テキスト部分に解釈的注釈を関連づける。 - associe une interprétation sous forme d'annotation - directement à un passage donné dans un texte. - asocia una anotación interpretativa directamente con un - periodo de texto. - associa direttamente l'annotazione interpretativa ad una - prozione di testo + associe une interprétation sous forme d'annotation directement à un passage donné dans un texte. + asocia una anotación interpretativa directamente con un periodo de texto. + associa direttamente l'annotazione interpretativa ad una prozione di testo @@ -27,46 +24,51 @@ $Id$ - + - -Only one of the attributes @target and @from may be supplied on - + + + Only one of the attributes @target and @from may be supplied on + + - -Only one of the attributes @target and @to may be supplied on - + + + Only one of the attributes @target and @to may be supplied on + + - -If @to is supplied on , @from must be supplied as well + + + If @to is supplied on , @from must be supplied as well + + - -The attributes @to and @from on may each contain only a single value + + + The attributes @to and @from on may each contain only a single value + + gives the identifier of the node which is the starting point of the span of text being annotated; if not accompanied by a to attribute, gives the identifier of the node of the entire span of text being annotated. - 현재 부호를 붙이는 단락의 처음을 명시함; to 속성과 같이 쓰이지 않으면 - 전체 문단을 명시함. + 현재 부호를 붙이는 단락의 처음을 명시함; to 속성과 같이 쓰이지 않으면 전체 문단을 명시함. 指出被註解段落的起點；若沒有使用屬性to，則指出全部段落。 当該注釈対象の始点を示す。属性toがない場合は、対象全 体を示す。 - précise le début du passage sur lequel porte - l'annotation ; s'il n'est pas accompagné d'un attribut to, désigne alors - l'intégralité du passage - especifica el principio del pasaje que se anota; si - no aparece con el atributo to, especifica el pasaje entero. - indica l'inizio di un brano annotato; se non è - accompagnato dall'attributo to indica l'inero brano + précise le début du passage sur lequel porte l'annotation ; s'il n'est pas accompagné d'un attribut to, désigne alors l'intégralité du passage + especifica el principio del pasaje que se anota; si no aparece con el atributo to, especifica el pasaje entero. + indica l'inizio di un brano annotato; se non è accompagnato dall'attributo to indica l'inero brano @@ -109,4 +111,4 @@ The attributes @to and @from on may each contain only a single value - \ No newline at end of file + diff --git a/P5/Source/Specs/standOff.xml b/P5/Source/Specs/standOff.xml index 3436e774c9..cf860c89d0 100644 --- a/P5/Source/Specs/standOff.xml +++ b/P5/Source/Specs/standOff.xml @@ -4,15 +4,9 @@ Dual-licensed under CC-by and BSD2 licences See the file COPYING.txt for details --> - - Functions as a - container element for linked data, contextual information, and - stand-off annotations embedded in a TEI document. - - リンクト・データや文脈情報、TEI文書に埋め込まれたスタンドオフ・アノテーションをコンテナ化する要素として機能する。 - + + Functions as a container element for linked data, contextual information, and stand-off annotations embedded in a TEI document. + リンクト・データや文脈情報、TEI文書に埋め込まれたスタンドオフ・アノテーションをコンテナ化する要素として機能する。 @@ -24,16 +18,17 @@ See the file COPYING.txt for details - This - element must have a @type attribute, since it is - nested inside a + + This + element must have a @type attribute, since it is + nested inside a +

This example shows an encoding of morphosyntactic features similar to the encoding system used by ISO 24611 (MAF).

- + @@ -92,45 +87,45 @@ See the file COPYING.txt for details

This example shows an encoding of contextual information which is referred to from the main text.

+ xml:lang="en" source="#MLK01" valid="feasible"> - - - - - Atlanta - - Georgia - United States of America - 33.755 -84.39 - - - - - Birmingham - - Alabama - United States of America - 33.653333 -86.808889 - - - - - - - - -

Moreover, I am congnizantcognizant of the interrelatedness of all communities and - states. I cannot sit idly by in Atlanta and not be concerned about what happens - in Birmingham. Injustice anywhere is a threat to justice everywhere. We - are caught in an inescapable network of mutuality, tied in a single garment - of destiny. Whatever affects one directly affects all indirectly. Never - again can we afford to live with the narrow, provincial outside agitator - idea. Anyone who lives inside the United States can never be considered - an outsider anywhere in this country.

- - - + + + + + Atlanta + + Georgia + United States of America + 33.755 -84.39 + + + + + Birmingham + + Alabama + United States of America + 33.653333 -86.808889 + + + + + + + + +

Moreover, I am congnizantcognizant of the interrelatedness of all communities and + states. I cannot sit idly by in Atlanta and not be concerned about what happens + in Birmingham. Injustice anywhere is a threat to justice everywhere. We + are caught in an inescapable network of mutuality, tied in a single garment + of destiny. Whatever affects one directly affects all indirectly. Never + again can we afford to live with the narrow, provincial outside agitator + idea. Anyone who lives inside the United States can never be considered + an outsider anywhere in this country.

+ + + diff --git a/P5/Source/Specs/subst.xml b/P5/Source/Specs/subst.xml index e4ee36cd8c..c4272cae56 100644 --- a/P5/Source/Specs/subst.xml +++ b/P5/Source/Specs/subst.xml @@ -7,19 +7,17 @@ $Date$ $Id$ --> - + substitution 대체 substitución sostituzione substitution - groups one or more deletions (or surplus text) with one or more additions when - the combination is to be regarded as a single intervention in the text. + groups one or more deletions (or surplus text) with one or more additions when the combination is to be regarded as a single intervention in the text. 결합이 텍스트에서 단일 조작으로 간주될 때 하나 이상의 삭제를 하나 이상의 추가 사항으로 대체한다. regroupe une ou plusieurs parties de texte supprimées et une ou plusieurs parties de texte ajoutées, lorsque cette combinaison peut être considérée comme une intervention unique sur le texte. agrupa una o más cancelaciones con una o más adiciones cuando la combinación se considera una única intervención en el texto. - 追加と削除が一連の調整と考えられる場合、そのひとつ以上の追加部分や削 - 除部分をまとめる。 + 追加と削除が一連の調整と考えられる場合、そのひとつ以上の追加部分や削 除部分をまとめる。 raggruppa ona o più cancellazioni insieme a una o più aggiunte quando la combinazione va considerata come singolo intervento sul testo @@ -37,7 +35,9 @@ $Id$ - must have at least one child add and at least one child del or surplus + + must have at least one child add and at least one child del or surplus + @@ -72,4 +72,4 @@ $Id$ - \ No newline at end of file + diff --git a/P5/Test/detest.odd b/P5/Test/detest.odd index ed347586ac..308aa94ff2 100644 --- a/P5/Test/detest.odd +++ b/P5/Test/detest.odd @@ -77,8 +77,11 @@ - - lists inside paragraphs not supported + + + lists inside paragraphs not supported + + @@ -161,18 +164,20 @@ - - divs of type 'canon' may not be nested - - - divs of type 'canon' may not be nested within 'register' - - - divs of type 'canon' may contain only one 'canonText' - - - divs of type 'canonText' can only occur inside 'canon' - + + + divs of type 'canon' may not be nested + + + divs of type 'canon' may not be nested within 'register' + + + divs of type 'canon' may contain only one 'canonText' + + + divs of type 'canonText' can only occur inside 'canon' + + @@ -469,14 +474,18 @@ - + + + - + + + diff --git a/P5/Test/expected-results/detest_xml_schematron.log b/P5/Test/expected-results/detest_xml_schematron.log index a7f9a9332e..6ecfa77abc 100644 --- a/P5/Test/expected-results/detest_xml_schematron.log +++ b/P5/Test/expected-results/detest_xml_schematron.log @@ -12,8 +12,6 @@ The element indicated by @spanTo (notMeaningful) must follow the current element @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this date element has no textual content. (string-length( normalize-space(.) ) gt 0) - - lists inside paragraphs not supported (tei:list) @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this date element has no textual content. (string-length( normalize-space(.) ) gt 0) @@ -33,8 +31,7 @@ The content of a "gloss" list should include a sequence of one or more pairs of @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this date element has no textual content. (string-length( normalize-space(.) ) gt 0) -An lg element - must contain at least one child l, lg, or gap element. (count(descendant::tei:lg|descendant::tei:l|descendant::tei:gap) > 0) +An lg element must contain at least one child l, lg, or gap element. (count(descendant::tei:lg|descendant::tei:l|descendant::tei:gap) > 0) @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this date element has no textual content. (string-length( normalize-space(.) ) gt 0) @@ -51,7 +48,8 @@ An lg element systems or calendars to which the date represented by the content of this element belongs, but this date element has no textual content. (string-length( normalize-space(.) ) gt 0) -On quotation, either the @marks attribute should be used, or a paragraph of description provided (not(@marks) and not (tei:p)) + On quotation, either the @marks attribute should be used, or a paragraph of description provided + (not( @marks ) and not( tei:p )) @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this date element has no textual content. (string-length( normalize-space(.) ) gt 0) @@ -70,25 +68,16 @@ On quotation, either the @marks attribute should be used, or a paragraph of desc @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this date element has no textual content. (string-length( normalize-space(.) ) gt 0) +You may not nest one s element within another: use seg instead (tei:s) - divs of type 'canon' may contain only one 'canonText' - (@type='canon' and count (tei:div[@type='canonText']) >1) - - divs of type 'canon' may not be nested - (@type='canon' and parent::tei:div/@type='canon') - - divs of type 'canon' may not be nested within 'register' - (@type='canon' and parent::tei:div/@type='register') -You may not nest one s element within - another: use seg instead (tei:s) - -Only one of the attributes @target and @from may be supplied on span + Only one of the attributes @target and @from may be supplied on span (@from and @target) -Only one of the attributes @target and @to may be supplied on span + Only one of the attributes @target and @to may be supplied on span (@to and @target) -If @to is supplied on span, @from must be supplied as well (@to and not(@from)) + If @to is supplied on span, @from must be supplied as well + (@to and not(@from)) The @location value "external" is inconsistent with the parallel-segmentation method of apparatus markup. (@location eq 'external' and @method eq 'parallel-segmentation') @@ -172,6 +161,7 @@ In the context of tagset documentation, the listRef element must not self-nest. In the context of tagset documentation, each ptr or ref element inside a listRef must have a target attribute with only 1 pointer as its value. (@target and not( matches( @target,'\s') )) In the context of tagset documentation, each ptr or ref element inside a listRef must have a target attribute with only 1 pointer as its value. (@target and not( matches( @target,'\s') )) -The @new attribute should always be supplied; use the special value -"normal" to indicate that the feature concerned ceases to be -remarkable at this point. (@new / warning) + The @new attribute should always be supplied; use the special value + "normal" to indicate that the feature concerned ceases to be + remarkable at this point. + (@new / warning) From 5a517eff24e02fa41956605af0106e046508fdd2 Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Fri, 15 Dec 2023 08:33:22 -0500 Subject: [PATCH 012/127] Consistently use 'sch:' prefix rather than explicit namespace decl on Schematron, for no apparent reason other than it is mildly easier to read when consistent. --- .../en/TD-DocumentationElements.xml | 40 ++++++++-------- P5/Source/Specs/att.identified.xml | 47 +++++++------------ P5/Source/Specs/moduleRef.xml | 14 +++--- 3 files changed, 44 insertions(+), 57 deletions(-) diff --git a/P5/Source/Guidelines/en/TD-DocumentationElements.xml b/P5/Source/Guidelines/en/TD-DocumentationElements.xml index 874ec510c1..3449140788 100644 --- a/P5/Source/Guidelines/en/TD-DocumentationElements.xml +++ b/P5/Source/Guidelines/en/TD-DocumentationElements.xml @@ -872,11 +872,11 @@ to mark any technical term, thus: - - - if it contains any subdivisions, a - division must contain at least two of them - + + + if it contains any subdivisions, a + division must contain at least two of them + @@ -906,13 +906,13 @@ to mark any technical term, thus: - - - - You should provide information in a figure from - which we can construct an alt attribute in HTML - - + + + + You should provide information in a figure from + which we can construct an alt attribute in HTML + + @@ -921,14 +921,14 @@ to mark any technical term, thus: - - - - A <table> should have a caption, using a <head> - element - Do not use tables to lay out the document body - - + + + + A <table> should have a caption, using a <head> + element + Do not use tables to lay out the document body + + diff --git a/P5/Source/Specs/att.identified.xml b/P5/Source/Specs/att.identified.xml index b8fc55b42d..c6e0ae2616 100644 --- a/P5/Source/Specs/att.identified.xml +++ b/P5/Source/Specs/att.identified.xml @@ -7,35 +7,25 @@ $Date$ $Id$ --> - - provides identifying attributes for elements which can be - subsequently referenced by means of a key - attribute. - key 속성에 - 의해 참조될 수 있는 요소의 속성을 제시한다. - 可利用屬性 - key來參照的元素 + + provides identifying attributes for elements which can be subsequently referenced by means of a key attribute. + key 속성에 의해 참조될 수 있는 요소의 속성을 제시한다. + 可利用屬性 key來參照的元素 後でkey属性によって参照されうる要素を指定する属性を示す。 - fournit les attributs - pour des éléments référençables au moyen d'un attribut - key. - elementos a los que se - puede hacer referencia a través del atributo key. - elementi ai quali si - può fare riferimento tramite l'attributo key - + fournit les attributs pour des éléments référençables au moyen d'un attribut key. + elementos a los que se puede hacer referencia a través del atributo key. elementi ai quali si può fare riferimento tramite l'attributo key - - - - Specification : the value of the module attribute ("") + + + + Specification : the value of the module attribute ("") should correspond to an existing module, via a moduleSpec or - moduleRef - - + moduleRef + + @@ -43,8 +33,7 @@ should correspond to an existing module, via a moduleSpec or 이 요소가 참조된 확인소를 제공한다. 提供被參照的元素的識別符號。 当該要素を参照する識別子を示す。 - fournit l'identifiant qui référence cet - élément. + fournit l'identifiant qui référence cet élément. proporciona el identificador utilizado para indicar un elemento. specifica l'identificatore utilizzato per indicare l'elemento @@ -54,8 +43,7 @@ should correspond to an existing module, via a moduleSpec or tei infrastructure module. tei 하부구조 모듈에서 이 대상이 미리 선언되어야 하는지를 설명한다. 說明該元素集是否為全域元素集，並必須在核心中宣告。 - 当該オブジェクトが、TEI基盤モジュー - ルで事前に宣言されるべきかどうかを示す。 + 当該オブジェクトが、TEI基盤モジュー ルで事前に宣言されるべきかどうかを示す。 précise si cet objet nécessite une prédéfinition dans le module d'infrastructure tei. declara si la clase debe ser considerada global y por tanto definida en el módulo core dichiara se la classe debba essere considerata globale e quindi definita nel modulo core @@ -67,11 +55,10 @@ should correspond to an existing module, via a moduleSpec or 이 대상이 정의되어야 하는 모듈명을 제시한다. 提供定義該元素的模組名稱。 当該オブジェクトが定義されているモジュール名を示す。 - fournit le nom du module dans lequel doit - être défini cet objet. + fournit le nom du module dans lequel doit être défini cet objet. proporciona el nombre del módulo en que el objeto debe ser definido. indica il nome del modulo nel quale l'oggetto deve essere definito - \ No newline at end of file + diff --git a/P5/Source/Specs/moduleRef.xml b/P5/Source/Specs/moduleRef.xml index 064ef701ee..d13386f9e4 100644 --- a/P5/Source/Specs/moduleRef.xml +++ b/P5/Source/Specs/moduleRef.xml @@ -42,18 +42,18 @@ $Id$ - - The prefix attribute + + The prefix attribute of should not match that of any other - element (it would defeat the purpose) - + element (it would defeat the purpose) + - - It is an error to supply both the @include and @except attributes - + + It is an error to supply both the @include and @except attributes + From bc2ed11e8818988cefcb69851563ab52cd4fa46f Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Fri, 15 Dec 2023 08:40:58 -0500 Subject: [PATCH 013/127] =?UTF-8?q?Oops=20=E2=80=94=20correct=20slightly?= =?UTF-8?q?=20overzelous=20insertion=20of=20ns=20prefix.=20:-)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- P5/Source/Specs/att.identified.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/P5/Source/Specs/att.identified.xml b/P5/Source/Specs/att.identified.xml index c6e0ae2616..22086bf2a5 100644 --- a/P5/Source/Specs/att.identified.xml +++ b/P5/Source/Specs/att.identified.xml @@ -18,14 +18,14 @@ $Id$ - + Specification : the value of the module attribute ("") should correspond to an existing module, via a moduleSpec or moduleRef - + From 06ed939a5bfc8fab8e36413497921d7ce1830fe1 Mon Sep 17 00:00:00 2001 From: lb42 Date: Wed, 20 Dec 2023 13:03:31 +0100 Subject: [PATCH 014/127] tweak fr --- Documents/pureODD/howtoChain-fr.xml | 27 ++++++++++++++++----------- 1 file changed, 16 insertions(+), 11 deletions(-) diff --git a/Documents/pureODD/howtoChain-fr.xml b/Documents/pureODD/howtoChain-fr.xml index a202110427..ee985255b2 100644 --- a/Documents/pureODD/howtoChain-fr.xml +++ b/Documents/pureODD/howtoChain-fr.xml @@ -9,7 +9,7 @@ Lou Burnard -

Unpublished draft

+

Published at lb42.github.io

authored from scratch

@@ -40,15 +40,20 @@ Traitement d’un ODD

Regardons d’un peu plus près la manière dont la TEI définit un schéma très léger appelé TEI Bare. Son élément de spécification de schéma commence comme suit : - + xml:lang="en"> + + + + + + + + + + + + +

Aucune attribut source n’est spécifié, ainsi la les déclarations des éléments demandés seront prises dans le fichier courant p5subset.xml.

Notez que cet ODD contient à la fois des références et des spécifications : il continet des références à des modèles (qui peuvent être conçues comme des raccourcis pour des références à des éléments ou des classes, dès lors qu’un module n’est rien d’autre qu’une collection de spécifications d’éléments et de classes) et des spécifications pour deux classes (classSpec), plutôt que des références (classRef). La référence au module tei contenue dans cette spécification icnlue la plupart des classes de la TEI, y compris ces deux classes-là. Un processeur ODD devra alors résoudre les spécifications de classe dupliquées pour les classes att.global et att.fragmentable. La solution requise est indiquée par la valeur de l’attribut mode : si celle-ci est delete alors les deux déclarations seront ignorées, et la classe est supprimée ; si sa valeur est change alors les deux déclarations seront mélangées de sorte que les parties spécification présentes dans la seconde spécification écrasent les premières. Dans ce cas, l’effet sera de supprimer les trois attributs mentionnés.

@@ -135,4 +140,4 @@
- \ No newline at end of file + From 7fbd0db5efdbb0c6ee5e6a055af31337c8c0981e Mon Sep 17 00:00:00 2001 From: lb42 Date: Wed, 20 Dec 2023 13:08:31 +0100 Subject: [PATCH 015/127] fr doc tweak --- Documents/pureODD/howtoChain-fr.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documents/pureODD/howtoChain-fr.xml b/Documents/pureODD/howtoChain-fr.xml index ee985255b2..86df88b3ee 100644 --- a/Documents/pureODD/howtoChain-fr.xml +++ b/Documents/pureODD/howtoChain-fr.xml @@ -6,7 +6,7 @@ Chaînage ODD pour les débutants - Lou Burnard + Lou Burnard et Emmanuel Chateau-Dutier

Published at lb42.github.io

From 1275cdfc90843930abeb78986c928f5128fa07a9 Mon Sep 17 00:00:00 2001 From: Lou Date: Wed, 20 Dec 2023 13:18:12 +0100 Subject: [PATCH 016/127] Update howtoChain-fr.xml --- Documents/pureODD/howtoChain-fr.xml | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/Documents/pureODD/howtoChain-fr.xml b/Documents/pureODD/howtoChain-fr.xml index a202110427..5f7e57ff9e 100644 --- a/Documents/pureODD/howtoChain-fr.xml +++ b/Documents/pureODD/howtoChain-fr.xml @@ -6,10 +6,11 @@ Chaînage ODD pour les débutants - Lou Burnard + Lou Burnard et Emmanuel Château-Dutier + -

Unpublished draft

+

Published at lb42.github.io

authored from scratch

@@ -135,4 +136,4 @@ - \ No newline at end of file + From 0bb1c9ee14c8e296747a9b4bc3376dec61d3657a Mon Sep 17 00:00:00 2001 From: Lou Date: Wed, 20 Dec 2023 13:22:06 +0100 Subject: [PATCH 017/127] Update howtoChain-fr.xml --- Documents/pureODD/howtoChain-fr.xml | 26 ++++++++++++++++---------- 1 file changed, 16 insertions(+), 10 deletions(-) diff --git a/Documents/pureODD/howtoChain-fr.xml b/Documents/pureODD/howtoChain-fr.xml index 5f7e57ff9e..4b73552fd1 100644 --- a/Documents/pureODD/howtoChain-fr.xml +++ b/Documents/pureODD/howtoChain-fr.xml @@ -39,17 +39,23 @@
Traitement d’un ODD -

Regardons d’un peu plus près la manière dont la TEI définit un schéma très léger appelé TEI Bare. Son élément de spécification de schéma commence comme suit : Regardons d’un peu plus près la manière dont la TEI définit un schéma très léger appelé TEI Bare. + Son élément de spécification de schéma commence comme suit : - + xml:lang="en"> + + + + + + + + + + + + +

Aucune attribut source n’est spécifié, ainsi la les déclarations des éléments demandés seront prises dans le fichier courant p5subset.xml.

Notez que cet ODD contient à la fois des références et des spécifications : il continet des références à des modèles (qui peuvent être conçues comme des raccourcis pour des références à des éléments ou des classes, dès lors qu’un module n’est rien d’autre qu’une collection de spécifications d’éléments et de classes) et des spécifications pour deux classes (classSpec), plutôt que des références (classRef). La référence au module tei contenue dans cette spécification icnlue la plupart des classes de la TEI, y compris ces deux classes-là. Un processeur ODD devra alors résoudre les spécifications de classe dupliquées pour les classes att.global et att.fragmentable. La solution requise est indiquée par la valeur de l’attribut mode : si celle-ci est delete alors les deux déclarations seront ignorées, et la classe est supprimée ; si sa valeur est change alors les deux déclarations seront mélangées de sorte que les parties spécification présentes dans la seconde spécification écrasent les premières. Dans ce cas, l’effet sera de supprimer les trois attributs mentionnés.

From 465a7779b47e6f88b0e1077a1a454669480ffd0b Mon Sep 17 00:00:00 2001 From: Lou Date: Wed, 20 Dec 2023 16:48:56 +0000 Subject: [PATCH 018/127] Update howtoChain.xml --- Documents/pureODD/howtoChain.xml | 37 ++++++++++++++++---------------- 1 file changed, 19 insertions(+), 18 deletions(-) diff --git a/Documents/pureODD/howtoChain.xml b/Documents/pureODD/howtoChain.xml index 9e384e5a7d..c4f2bb0423 100644 --- a/Documents/pureODD/howtoChain.xml +++ b/Documents/pureODD/howtoChain.xml @@ -9,13 +9,14 @@ Lou Burnard -

Discussion draft

+

As published on lb42.github.io

authored from scratch

 + Minor changes for publication on lb42.github.io Expanded and announced on TEI-L Uploaded for Council review Drafted first part on train from Paris to La Souterraine; then lost @@ -73,22 +74,21 @@

Let's look more closely at the way the TEI defines a very light weight schema called TEI Bare. Its schema specification element begins like this: - - - - - - - - - - - - - - - + + + + + + + + + + + + + +

No source is specified, so declarations for the elements requested here will be taken from the current p5subset.xml.

@@ -251,7 +251,8 @@ the value for the source attribute on the schemaSpec defining our ODD. We could do the same thing (though I don't recommend it) even at the level of individual elements, by specifying a different version as source for an - elementSpec.

And just to make life a little simpler, there is an + elementSpec.

+

And just to make life a little simpler, there is an officially recognized short cut built into the current ODD processing stylesheets: instead of the lengthy URL above, we could simply say tei:3.0.0. For example, supposing that for some strange reason we don't want to add the current From 6b749a2bb6ed22b5e6a921d475040307a463ded8 Mon Sep 17 00:00:00 2001 From: Lou Date: Wed, 20 Dec 2023 17:14:22 +0000 Subject: [PATCH 019/127] Update howtoChain.xml --- Documents/pureODD/howtoChain.xml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/Documents/pureODD/howtoChain.xml b/Documents/pureODD/howtoChain.xml index c4f2bb0423..fb81c2c5f4 100644 --- a/Documents/pureODD/howtoChain.xml +++ b/Documents/pureODD/howtoChain.xml @@ -59,14 +59,14 @@ in the current source tree. And one with the value http://example.com/superODDs/anotherSubset.xml will go looking for it at the URL indicated.

-

It's important to understand that the resource indicated by the sources +

It's important to understand that the resource indicated by the source attribute must contain complete and explicit specification elements: elementSpec rather than elementRef, classSpec rather than classRef and so on. It may of course contain other TEI elements, but these will be ignored entirely in the construction of a schema. A file called p5subset.xml, provided as part of every TEI release, is an example of such a resource: it contains specifications for every - single TEI element, class, macro, and datatype, but nothing else much. If the - source parameter is not supplied, the most recently available version of this + single TEI element, class, macro, and datatype, but nothing else much. If a value for the + source attribute is not specified, the most recently available version of this file is what will be used during the processing of an ODD.

@@ -98,8 +98,8 @@ specifications for two classes (classSpec), rather than references (classRef). The reference to the module tei brings with it specifications for most TEI classes, including these two. An ODD processor will therefore - have to resolve duplicate class specifications for the classes att.global - and att.fragmentable. The required resolution is indicated by the value of + have to deal with duplicate class specifications for the classes att.global + and att.fragmentable. The resolution method required is indicated by the value of the mode attribute: if this is delete then both declarations are to be ignored, and the class is therefore suppressed; if it is change then the two declarations are to be merged, with any part of it present in the second specification @@ -107,7 +107,7 @@ attributes mentioned.

If you'd like to check that this ODD does what you expect, and you have oXygen installed with a recent version of the TEI Frameworks, just download the file - tei_bare.odd, and tell oXygen to apply the predefined transformation + tei_bare.odd (you can get it from the TEI github repo), and tell oXygen to apply the predefined transformation TEI ODD to HTML to it. This will produce a mini-manual for the TEI Bare customization in HTML format, near the beginning of which you should see a list of the elements the schema contains. From f4ba6a006e8ae969101cf3f6f02d7bf8c1d96ae3 Mon Sep 17 00:00:00 2001 From: lou burnard Date: Wed, 20 Dec 2023 18:14:57 +0000 Subject: [PATCH 020/127] add section missing from fr tuto --- Documents/pureODD/howtoChain-fr.xml | 157 +++++++++++++++------------- 1 file changed, 84 insertions(+), 73 deletions(-) diff --git a/Documents/pureODD/howtoChain-fr.xml b/Documents/pureODD/howtoChain-fr.xml index 0e8bf85eea..84352cf56d 100644 --- a/Documents/pureODD/howtoChain-fr.xml +++ b/Documents/pureODD/howtoChain-fr.xml @@ -6,7 +6,6 @@ Chaînage ODD pour les débutants - Lou Burnard et Emmanuel Chateau-Dutier @@ -18,6 +17,7 @@ + Added last section missing from earlier translation French translation by Emmanuel Château Uploaded for Council review Drafted first part on train from Paris to La Souterraine;l then lost half of it by shutting lid in a hurry without saving first : doh. @@ -28,10 +28,10 @@

À quoi ça sert ?

Ce court guide est destiné à expliquer le mécanisme du ODD chaining. Un fichier ODD spécifie une utilisation de la TEI en sélectionnant des éléments ou des attributs particuliers, etc. dans l’ensemble de la TEI. Mais il est également possible de rafiner encore plus cette spécification en faisant dériver votre ODD les uns des autres. En principe, vous pouvez chaîner des ODDs ensemble de cette manière autant que vous le souhaitez. Vous pouvez employer cette fonctionnalité de différentes manières : - vous pouvez ajouter des restrictions additionnelles à un ODD existant, par exemple pour modifier la liste des valeurs possibles d’un attribut - vous pouvez réduire le sous-ensemble d’éléments produits par un ODD existant - vous pouvez ajouter de nouveaux éléments ou des modules à un ODD existant -

+vous pouvez ajouter des restrictions additionnelles à un ODD existant, par exemple pour modifier la liste des valeurs possibles d’un attribut +vous pouvez réduire le sous-ensemble d’éléments produits par un ODD existant +vous pouvez ajouter de nouveaux éléments ou des modules à un ODD existant +

Comment ça marche ? @@ -40,27 +40,26 @@
Traitement d’un ODD -

Regardons d’un peu plus près la manière dont la TEI définit un schéma très léger appelé TEI Bare. - Son élément de spécification de schéma commence comme suit : - - - - - - - - - - - - - -

+

Regardons d’un peu plus près la manière dont la TEI définit un schéma très léger appelé TEI Bare. + Son élément de spécification de schéma commence comme suit : + + + + + + + + + + + + + +

Aucune attribut source n’est spécifié, ainsi la les déclarations des éléments demandés seront prises dans le fichier courant p5subset.xml.

-

Notez que cet ODD contient à la fois des références et des spécifications : il continet des références à des modèles (qui peuvent être conçues comme des raccourcis pour des références à des éléments ou des classes, dès lors qu’un module n’est rien d’autre qu’une collection de spécifications d’éléments et de classes) et des spécifications pour deux classes (classSpec), plutôt que des références (classRef). La référence au module tei contenue dans cette spécification icnlue la plupart des classes de la TEI, y compris ces deux classes-là. Un processeur ODD devra alors résoudre les spécifications de classe dupliquées pour les classes att.global et att.fragmentable. La solution requise est indiquée par la valeur de l’attribut mode : si celle-ci est delete alors les deux déclarations seront ignorées, et la classe est supprimée ; si sa valeur est change alors les deux déclarations seront mélangées de sorte que les parties spécification présentes dans la seconde spécification écrasent les premières. Dans ce cas, l’effet sera de supprimer les trois attributs mentionnés.

-

Vous pouvez vérifier que cet ODD fait bien ce que vous attendez, si vous avez une d’oXygen installée avec une version récente du TEI Frameworks, téléchargez simplement le fichier tei_bare.odd, et demandez à oXygen de lui appliquer la transformation prédéfinie TEI ODD to HTML. Cela va produire un mini-manuel pour la personnalisation TEI Bare au format HTML au début de laquelle vous pourrez consulter la liste des éléments que le schéma contient.

Vous pouvez alors vérifier que les modifications de la classe d’attribut att.global indiquées ci-dessus ont bien été exécutées en consultant cette documentation.

@@ -72,70 +71,82 @@ Chaînage : sous-ensemble

Supposez maintenant que nous avons une version compilée de TEI_bare dans un fichier nommé TEI_bare.compiled.xml. Le traitement de la spécification de schéma suivante produirait alors exactement le même résultat que nous aurions obtenu d’une version non compilée.

- - - - - - + + + + + +

Cela fonctionne car chaqu’une des éléments moduleRef ici réfèrent au module (i.e. ensemble d’éléments, etc.) disponible dans l’ODD compilé plutôt qu’aux modules définis dans l’ensemble de la TEI. Notez aussi que seulement fournir l’ODD compilé comme source d’un schema n’est pas suffisant : nous devons aussi spécifier laquelle des déclarations elle contient nous voulons utiliser : nihil ex nihilo fit...!

Cependant, la raison pour laquelle nous nous sommes engagés sur cette voie n’était pas de pouvoir faire d’une autre manière ce que nous pouvions déjà faire autrement. Produisons maintenant une version réduite de TEI Bare dans laquelle l’élément head serait manquant.

- - - - - - + + + + + +

Et juste pour la complétude, voici une autre manière d’arriver au même effet :

- - - - - - - -

Notez qu’on ne peut supprimer ou modifier que les choses qui sont déjà présentes dans l’ODD compilé spécifié par l’attribut source. Cette approche du chaînage est bien adaptée dans une situation où nous définissons d’æbrod un DODD qui combine tous les éléments (etc.) que nous envisageons d’utiliser et que nous dérivons ensuite un sous-ensemble particulier à partir d’eux. Par exemple, un pour les manuscrits, un pour les imprimés de la Renaissance, un pour les imprimés contemporains, etc. (Cette approche a, par exemple, été adoptée par la Deutsches Text Archive.)

Chaînage : super-ensemble -

Mais le chaînage ODD n’est pas restreint à la définition de sous-ensembles. Supposez que nous voulions prendre le schéma existant TEI Bare et ajouter des déclarations d’autres modules. Nous pourrions bien sûr laborieusement copier toutes les déclarations dont nous avons besoin dans notre schemaSpec, mais cela serait bien plus élégant d’avoir de ne pas avoir à faire ça. Supposez, par exemple, que nous voulions ajouter tout ce qui est founi par le module gaiji. Ce module n’était pas inclus lorsque nous avons défini notre version compilée de TEI Bare, toutefois il est évidemment disponible dans l’ensemble de la TEI. Voici une manière de faire :

+

Mais le chaînage ODD n’est pas restreint à la définition de sous-ensembles. Supposez que nous voulions prendre le schéma existant TEI Bare et ajouter des déclarations d’autres modules. Nous pourrions bien sûr laborieusement copier toutes les déclarations dont nous avons besoin dans notre schemaSpec, mais cela serait bien plus élégant d’avoir de ne pas avoir à faire ça. Supposez, par exemple, que nous voulions ajouter tout ce qui est fourni par le module gaiji. Ce module n’était pas inclus lorsque nous avons défini notre version compilée de TEI Bare, bien qu'il est évidemment disponible dans l’ensemble de la TEI. Voici une manière de faire :

- - - - - - -

Le moduleRef qui va cherche le module gaiji utilise son propre attribut source pour spécifier où aller cherche les déclarations de ce module. Cele ne ferait pas sens d’aller les chercher dans tei_bare.compiled.odd : ils n’y sont pas. Au lieu de cela, ici celles-ci sont collectées depuis une copie en ligne d’un ODD compilé qui fournit l’ensemble des Guidelines TEI. Bien sûr, nous aurions aussi pu également réaliser la définition d’un sous-ensemble. Par exemple :

+ + + + + + +

Le moduleRef qui va rechercher le module gaiji utilise son propre attribut source pour spécifier où trouver les déclarations de ce module. Cela ne ferait pas sens d’aller les chercher dans tei_bare.compiled.odd : elle n’y sont pas. Au lieu de cela, on va les retrouvées depuis une copie en ligne d’un ODD compilé qui fournit l’ensemble des Guidelines TEI. Bien sûr, nous aurions aussi pu en meme temps réaliser la définition d’un sous-ensemble. Par exemple :

- - - - - - + + + + + +

Cet ODD nous donnera tout ce qui est disponible dans tei_bare avec les g, char, et glyph tirés par défaut du module gaiji. Nous pourrions parvenir au même effet en nommant explicitement les élements dont nous avions besoin, de nouveau en spécifiant où ceux-ci devraient être trouvés :

- - - - - - - - + + + + + + + +

On peut employer cette technique pour ramener un élément qui a été effacé du schéma compilé. Par exemple, l’élément q n’est pas disponible avec TEI Bare, mais il peut facilement être rétabli. Nous pouvons même spécifier quelle version de l’élément q est souhaitée : dans ce cas, nous irons chercher la version définie dans la distribution 3.0.0 de la TEI P5 :

- - - - - - + + + + + + +

Il existe un tableau utile répertoriant les dates et les numéros de version de toutes les versions de TEI P5 au TEI website. +

Un cas d'usage +

Supposons que vous mettiez en place une application de crowdsourcing pour la transcription de documents d'archives de quelque nature que ce soit. Une fois les documents capturés et légèrement étiquetés, vous envisagez d'enrichir les archives avec des métadonnées détaillées décrivant les personnes et les lieux qui y sont mentionnés. Vous prévoyez donc d'avoir besoin de deux schémas : un (très simple et contraint) pour valider les fichiers de transcription, et un autre (également très contraint, mais différemment) pour valider les métadonnées. Mais bien sûr, vous devrez également valider les documents complétés, combinant les deux types de données. Et il y a certaines fonctionnalités (paragraphes, titres, etc.) communes aux deux, ce qui suggère que vous aurez également besoin d'un troisième schéma... Le chaînage ODD est la réponse !

+ (Avant de poursuivre votre lecture, je vous suggère de télécharger notre petit ensemble de fichiers d'exemple et de lancer votre processeur XML préféré. Veuillez noter que ces fichiers d'exemple sont simplement destinés à démontrer l'effet du chaînage : dans une application réelle, on personnalise son schéma beaucoup plus précisément, par exemple en supprimant les attributs inutiles, en simplifiant les modèles de contenu, en ajoutant différents exemples, etc.)

+ Il nous faudra définir le troisième schéma, qui contient tout ce qui est susceptible d'être utile à l'un ou l'autre des deux autres, plus tout ce qui est commun aux deux. Appelons celui-ci notre mère ODD. Ouvrez le fichier motherODD.xml et vous verrez un ODD typique, avec l'élément racine TEI, défini en référence aux directives TEI complètes. En plus du module d'infrastructure tei, il contient des éléments tels que pb, p, hi, div, et name du module core, ainsi que l'ensemble de métadonnées que nous prévoyons d'utiliser pour chaque document TEI valide, qui prend ses composants des modules header, namesdates, et corpus.

+ Nous définirons nos deux schémas plus spécialisés en référence à celui-ci. Nous devons donc compiler le motherODD, le transformant effectivement en une collection ou une bibliothèque de spécifications TEI complètes. Nous faisons cela en exécutant la transformation odd2odd mentionnée ci-dessus : les résultats de notre fichier exemple se trouvent dans le fichier motherODD.compiled. + Jetez maintenant un œil aux deux sous-ensembles ODD différents dans notre exemple : un (justTranscripts.xml) pour les transcriptions et un (justMetadata.xml) pour les métadonnées. Notez que chacun de ces fichiers ODD fait référence à motherODD.compiled au moyen de son attribut source. Notez également que chacun d'eux spécifie un élément racine différent : ceci afin que l'on puisse utiliser les schémas résultants pour valider une transcription sans en-tête, ou un en-tête sans transcription.

+ Essayez de traiter chacun de ces fichiers ODD pour générer de la documentation et un schéma, de la manière habituelle. Comparez ensuite les résultats. Nous avons inclus quelques exemples de fichiers de données pour vous permettre de vérifier que la validation fonctionne comme elle le devrait : le fichier transcription.xml doit être valide par rapport au schéma généré à partir de l'ODD justTranscription.xml et le fichier metadata.xml doit être valide par rapport au schéma généré à partir de l'ODD justMetadata.xml. Notre exemple suppose un flux de travail particulier dans lequel, par exemple, l'attribut ref est utilisé pour associer des éléments name a un élément person ou place dans l'en-tête ; votre kilométrage peut bien sûr varier. +

Enfin, jetez un œil au fichier driver.tei : il utilise xInclude pour combiner les deux fichiers en un document TEI complet, qui devrait être valide par rapport au schéma généré à partir du motherODD. Encore une fois, n'hésitez pas à modifier si nécessaire en fonction de vos propres pratiques de travail ! +

+ + - represents an annotation following the Web Annotation Data Model. diff --git a/P5/Source/Specs/att.entryLike.xml b/P5/Source/Specs/att.entryLike.xml index 34db8ea57b..71dfa9584b 100644 --- a/P5/Source/Specs/att.entryLike.xml +++ b/P5/Source/Specs/att.entryLike.xml @@ -25,7 +25,7 @@ $Id$ #370. Note that same problems is present in att.textCritical. --> - + indicates type of entry, in dictionaries with multiple types. 다중 유형을 포함하는 사전에서, 표제 항목 유형을 나타낸다. 指出複合類型字典中的辭條類型。 diff --git a/P5/Source/Specs/att.textCritical.xml b/P5/Source/Specs/att.textCritical.xml index 79f1e25fd9..518659e570 100644 --- a/P5/Source/Specs/att.textCritical.xml +++ b/P5/Source/Specs/att.textCritical.xml @@ -29,7 +29,7 @@ $Id$ Also see TEI ticket #1867. --> - + classifies the reading according to some useful typology. 유용한 유형에 따라 독법을 분류한다. 用合宜的分類法將對應本分類。 diff --git a/P5/Source/Specs/birth.xml b/P5/Source/Specs/birth.xml index 561103390f..7bd2cc19dd 100644 --- a/P5/Source/Specs/birth.xml +++ b/P5/Source/Specs/birth.xml @@ -67,7 +67,7 @@ - + caesarean section 帝王切開 diff --git a/P5/Source/Specs/castItem.xml b/P5/Source/Specs/castItem.xml index 0c0c7c527e..9e3a240a09 100644 --- a/P5/Source/Specs/castItem.xml +++ b/P5/Source/Specs/castItem.xml @@ -48,7 +48,7 @@ either a single role or a list of non-speaking roles. indica la voce della lista dei personaggi role - + the item describes a single role. 항목이 하나의 배역을 기술한다. diff --git a/P5/Source/Specs/certainty.xml b/P5/Source/Specs/certainty.xml index b8542ee9e1..8f27e128c0 100644 --- a/P5/Source/Specs/certainty.xml +++ b/P5/Source/Specs/certainty.xml @@ -34,7 +34,7 @@ $Id$ characterizes the element in some sense, using any convenient classification scheme or typology; sample categorization of annotations of uncertainty might use following values: - + diff --git a/P5/Source/Specs/classSpec.xml b/P5/Source/Specs/classSpec.xml index a9e64e6e77..e1dcd97806 100644 --- a/P5/Source/Specs/classSpec.xml +++ b/P5/Source/Specs/classSpec.xml @@ -58,7 +58,7 @@ that is a group of indica si se trata de una clase de modelos o de atributos. indica se si tratta di una classe di modelli o di attributi - + content model 내용 모델 diff --git a/P5/Source/Specs/constitution.xml b/P5/Source/Specs/constitution.xml index 25f8214d7e..d3d55c4c3e 100644 --- a/P5/Source/Specs/constitution.xml +++ b/P5/Source/Specs/constitution.xml @@ -38,7 +38,7 @@ as fragmentary, complete, etc. specifica come era costituito il testo. single - + a single complete text 단일 완전 텍스트 diff --git a/P5/Source/Specs/constraintSpec.xml b/P5/Source/Specs/constraintSpec.xml index ca2aad8f6f..6ebabade96 100644 --- a/P5/Source/Specs/constraintSpec.xml +++ b/P5/Source/Specs/constraintSpec.xml @@ -126,7 +126,7 @@ $Id$ when a constraintSpec warns about a deprecated construct. - + Indicates that this constraint specification warns that some other diff --git a/P5/Source/Specs/conversion.xml b/P5/Source/Specs/conversion.xml index 016a233242..dbc51d2ff0 100644 --- a/P5/Source/Specs/conversion.xml +++ b/P5/Source/Specs/conversion.xml @@ -47,13 +47,13 @@ $Id$ - + indicates a source unit of measure that is to be converted into another unit indicated in toUnit. - + the target unit of measurement for a conversion from a source unit referenced in fromUnit. diff --git a/P5/Source/Specs/correspAction.xml b/P5/Source/Specs/correspAction.xml index de1cfa7afc..5231cd5f57 100644 --- a/P5/Source/Specs/correspAction.xml +++ b/P5/Source/Specs/correspAction.xml @@ -36,7 +36,7 @@ - + information concerning the sending or dispatch of a message. メッセージの送信や発送に関する情報。 diff --git a/P5/Source/Specs/death.xml b/P5/Source/Specs/death.xml index e61e7384cb..d24250d3ed 100644 --- a/P5/Source/Specs/death.xml +++ b/P5/Source/Specs/death.xml @@ -64,7 +64,7 @@ - + diff --git a/P5/Source/Specs/derivation.xml b/P5/Source/Specs/derivation.xml index a237382430..2d23c625ee 100644 --- a/P5/Source/Specs/derivation.xml +++ b/P5/Source/Specs/derivation.xml @@ -36,7 +36,7 @@ $Id$ caracteriza la derivación del texto classifica la provenienza del testo. - + text is original 텍스트가 원본이다. diff --git a/P5/Source/Specs/desc.xml b/P5/Source/Specs/desc.xml index e5bdf55bf3..463485e6b4 100644 --- a/P5/Source/Specs/desc.xml +++ b/P5/Source/Specs/desc.xml @@ -63,7 +63,7 @@ - + deprecation information diff --git a/P5/Source/Specs/dimensions.xml b/P5/Source/Specs/dimensions.xml index da74e64b90..593b18cc3a 100644 --- a/P5/Source/Specs/dimensions.xml +++ b/P5/Source/Specs/dimensions.xml @@ -52,7 +52,7 @@ $Id$ indica que aspecto del objeto se mide. indica quale aspetto dell'oggetto viene misurato - + dimensions relate to one or more leaves (e.g. a single leaf, a gathering, or a separately bound part) diff --git a/P5/Source/Specs/divGen.xml b/P5/Source/Specs/divGen.xml index f563e704c6..20fe47f1b8 100644 --- a/P5/Source/Specs/divGen.xml +++ b/P5/Source/Specs/divGen.xml @@ -46,7 +46,7 @@ especifica que tipo de divisón de texto generada aparece (p.ej. índice, tabla de contenidos, etc.) specifica quale tipo di partizione testuale generata (ad esempio indice, sommario, ecc.) apparirà - + an index is to be generated and inserted at this point. 색인은 이 지점에서 생성되고 삽입된다. diff --git a/P5/Source/Specs/domain.xml b/P5/Source/Specs/domain.xml index 8e76214bbd..71a1d86fe6 100644 --- a/P5/Source/Specs/domain.xml +++ b/P5/Source/Specs/domain.xml @@ -44,7 +44,7 @@ education, religion, etc. clasifica el campo de uso. classifica l'ambito di uso. - + art and entertainment 예술과 연예 diff --git a/P5/Source/Specs/education.xml b/P5/Source/Specs/education.xml index 5867523916..7f33e3e6d6 100644 --- a/P5/Source/Specs/education.xml +++ b/P5/Source/Specs/education.xml @@ -63,7 +63,7 @@ - + diff --git a/P5/Source/Specs/factuality.xml b/P5/Source/Specs/factuality.xml index 4f423e3b39..526401d515 100644 --- a/P5/Source/Specs/factuality.xml +++ b/P5/Source/Specs/factuality.xml @@ -38,7 +38,7 @@ or a non-fictional world. clasifica la objetividad de un texto classifica la fattualità del testo. - + the text is to be regarded as entirely imaginative 텍스트가 전적으로 상상적이라 간주된다. diff --git a/P5/Source/Specs/faith.xml b/P5/Source/Specs/faith.xml index 681a7b4d3a..502fa7c630 100644 --- a/P5/Source/Specs/faith.xml +++ b/P5/Source/Specs/faith.xml @@ -63,7 +63,7 @@ - + diff --git a/P5/Source/Specs/form.xml b/P5/Source/Specs/form.xml index 53adf9b547..03d417cbf9 100644 --- a/P5/Source/Specs/form.xml +++ b/P5/Source/Specs/form.xml @@ -54,7 +54,7 @@ $Id$ clasifica la forma como simple, compuesta, etc. classifica la forma in simplice, composta, ecc. - + single free lexical item 단일 자립 어휘 항목 diff --git a/P5/Source/Specs/fw.xml b/P5/Source/Specs/fw.xml index 5b617dce51..5587342946 100644 --- a/P5/Source/Specs/fw.xml +++ b/P5/Source/Specs/fw.xml @@ -42,7 +42,7 @@ $Id$ clasifica las convenciones usadas según una tipología funcional. classifica le convenzioni usate secondo una tipologia funzionale - + a running title at the top of the page 페이지 상단의 현 제목 diff --git a/P5/Source/Specs/gram.xml b/P5/Source/Specs/gram.xml index 509c218607..26c94b6f39 100644 --- a/P5/Source/Specs/gram.xml +++ b/P5/Source/Specs/gram.xml @@ -62,7 +62,7 @@ $Id$ - + part of speech 품사 diff --git a/P5/Source/Specs/graph.xml b/P5/Source/Specs/graph.xml index a7be2a2f0c..1796150607 100644 --- a/P5/Source/Specs/graph.xml +++ b/P5/Source/Specs/graph.xml @@ -65,7 +65,7 @@ connect the nodes. describe el tipo de gráfico descrive il tipo di grafo - + undirected graph 무방향 그래프 diff --git a/P5/Source/Specs/iType.xml b/P5/Source/Specs/iType.xml index 56a7f59f04..25eb21c12e 100644 --- a/P5/Source/Specs/iType.xml +++ b/P5/Source/Specs/iType.xml @@ -57,7 +57,7 @@ $Id$ abbreviate solite (ad esempio inv)e altri tipi di indicatori, quali codici speciali per fare riferimento al tipo di coniugazione, ecc. - + abbreviated indicator 축약 지시자 diff --git a/P5/Source/Specs/idno.xml b/P5/Source/Specs/idno.xml index 6e78cc3fba..b378edb436 100644 --- a/P5/Source/Specs/idno.xml +++ b/P5/Source/Specs/idno.xml @@ -100,7 +100,7 @@ $Id$ - + International Standard Book Number: a 13- or (if assigned prior to 2007) 10-digit identifying number assigned by the publishing diff --git a/P5/Source/Specs/interaction.xml b/P5/Source/Specs/interaction.xml index 840dbd9b3b..2e6b53e5bc 100644 --- a/P5/Source/Specs/interaction.xml +++ b/P5/Source/Specs/interaction.xml @@ -43,7 +43,7 @@ form of response or interjection, commentary, etc. describe el grado de interacción entre los participantes activos y pasivos en un texto. specifica il grado di interazione tra partecipanti attivi e passivi all'interno del testo. - + no interaction of any kind, e.g. a monologue 종류의 상호작용이 없다. 예, 독백. diff --git a/P5/Source/Specs/langKnowledge.xml b/P5/Source/Specs/langKnowledge.xml index b3ca2bc8ec..71c1a14eaf 100644 --- a/P5/Source/Specs/langKnowledge.xml +++ b/P5/Source/Specs/langKnowledge.xml @@ -76,7 +76,7 @@ - + diff --git a/P5/Source/Specs/list.xml b/P5/Source/Specs/list.xml index 9991668cab..e3417c8952 100644 --- a/P5/Source/Specs/list.xml +++ b/P5/Source/Specs/list.xml @@ -108,7 +108,7 @@ describes the nature of the items in the list. beschreibt die Art der Listenpunkte. - + gloss Gloss diff --git a/P5/Source/Specs/listAnnotation.xml b/P5/Source/Specs/listAnnotation.xml index eed95be842..d8ee3aa31a 100644 --- a/P5/Source/Specs/listAnnotation.xml +++ b/P5/Source/Specs/listAnnotation.xml @@ -7,7 +7,7 @@ $Date$ $Id$ --> - contains a list of annotations, typically encoded as annotation, annotationBlock, or note, possibly organized with diff --git a/P5/Source/Specs/move.xml b/P5/Source/Specs/move.xml index ae6f03d189..3ea4db9a47 100644 --- a/P5/Source/Specs/move.xml +++ b/P5/Source/Specs/move.xml @@ -43,7 +43,7 @@ $Id$ indica il tipo di movimento, ad esempio come entrata o uscita. - + character is entering the stage. 등장인물이 무대에 등장하고 있다. diff --git a/P5/Source/Specs/nationality.xml b/P5/Source/Specs/nationality.xml index d588aed471..41a093ac89 100644 --- a/P5/Source/Specs/nationality.xml +++ b/P5/Source/Specs/nationality.xml @@ -66,7 +66,7 @@ $Id$ - + diff --git a/P5/Source/Specs/node.xml b/P5/Source/Specs/node.xml index 43861db564..b529b32160 100644 --- a/P5/Source/Specs/node.xml +++ b/P5/Source/Specs/node.xml @@ -48,7 +48,7 @@ other analytic element. define un tipo de nodo. definisce un tipo di nodo - + initial node in a transition network 전이망에서 시작 노드 diff --git a/P5/Source/Specs/num.xml b/P5/Source/Specs/num.xml index 20483d389a..8c81162640 100644 --- a/P5/Source/Specs/num.xml +++ b/P5/Source/Specs/num.xml @@ -43,7 +43,7 @@ indica il tipo di valore numerico bestimmt die Art des numerischen Wertes. - + absolute number, e.g. 21, 21.5 예를 들어, 21, 21.5와 같은 절대값 diff --git a/P5/Source/Specs/oRef.xml b/P5/Source/Specs/oRef.xml index 5e2572fc3d..616c7e37d8 100644 --- a/P5/Source/Specs/oRef.xml +++ b/P5/Source/Specs/oRef.xml @@ -52,7 +52,7 @@ $Id$ indica il tipo di modifica tipografica del lemma in un riferimento. - + capital 대문자 diff --git a/P5/Source/Specs/occupation.xml b/P5/Source/Specs/occupation.xml index 09501d3f59..daf711c415 100644 --- a/P5/Source/Specs/occupation.xml +++ b/P5/Source/Specs/occupation.xml @@ -64,7 +64,7 @@ $Id$ - + diff --git a/P5/Source/Specs/preparedness.xml b/P5/Source/Specs/preparedness.xml index b28d79149f..d966a82185 100644 --- a/P5/Source/Specs/preparedness.xml +++ b/P5/Source/Specs/preparedness.xml @@ -37,7 +37,7 @@ prepared or spontaneous. una palabra clave que caracteriza el tipo de preparación. una parola chiava che caratterizza il grado di spontaneità - + spontaneous or unprepared 자발적 또는 준비되지 않은 diff --git a/P5/Source/Specs/purpose.xml b/P5/Source/Specs/purpose.xml index 4675f2f3d0..d34d95fbcf 100644 --- a/P5/Source/Specs/purpose.xml +++ b/P5/Source/Specs/purpose.xml @@ -34,7 +34,7 @@ text. especifica un tipo particular de finalidad specifica un tipo particolare di scopo. - + didactic, advertising, propaganda, etc. 설교, 광고, 선전 등 diff --git a/P5/Source/Specs/recording.xml b/P5/Source/Specs/recording.xml index a5efb58380..ba11025fd5 100644 --- a/P5/Source/Specs/recording.xml +++ b/P5/Source/Specs/recording.xml @@ -55,7 +55,7 @@ a public broadcast. tipo di registrazione. audio - + audio recording enregistrement audio diff --git a/P5/Source/Specs/residence.xml b/P5/Source/Specs/residence.xml index a284f06693..9c013fe618 100644 --- a/P5/Source/Specs/residence.xml +++ b/P5/Source/Specs/residence.xml @@ -67,7 +67,7 @@ $Id$ - + diff --git a/P5/Source/Specs/rt.xml b/P5/Source/Specs/rt.xml index 69aa85d21b..33477776ec 100644 --- a/P5/Source/Specs/rt.xml +++ b/P5/Source/Specs/rt.xml @@ -51,7 +51,7 @@ to.

 - + points to the starting point of the span of text being glossed by this ruby text. ルビテキストの対象範囲の始点を示す。 @@ -71,7 +71,7 @@ - + points to the ending point of the span of text being glossed. ルビテキストの対象範囲の終点を示す。 diff --git a/P5/Source/Specs/socecStatus.xml b/P5/Source/Specs/socecStatus.xml index 51c75f12c1..79ea94c3a0 100644 --- a/P5/Source/Specs/socecStatus.xml +++ b/P5/Source/Specs/socecStatus.xml @@ -91,7 +91,7 @@ $Id$ - + diff --git a/P5/Source/Specs/standOff.xml b/P5/Source/Specs/standOff.xml index 3436e774c9..dfd60308f9 100644 --- a/P5/Source/Specs/standOff.xml +++ b/P5/Source/Specs/standOff.xml @@ -5,7 +5,7 @@ See the file COPYING.txt for details --> Functions as a container element for linked data, contextual information, and @@ -22,7 +22,7 @@ See the file COPYING.txt for details - + This element must have a @type attribute, since it is diff --git a/P5/Source/Specs/tag.xml b/P5/Source/Specs/tag.xml index 7ab9d5d2b3..3b79f291d8 100644 --- a/P5/Source/Specs/tag.xml +++ b/P5/Source/Specs/tag.xml @@ -40,7 +40,7 @@ $Id$ indique quel type de balise XML est prévu. indica di quale tipo di marcatore XML si tratta - + a start-tag, with delimiters < and > is intended une balise de début, délimitée par les signes diff --git a/P5/Source/Specs/tech.xml b/P5/Source/Specs/tech.xml index 44c3593e67..3a8920f4a2 100644 --- a/P5/Source/Specs/tech.xml +++ b/P5/Source/Specs/tech.xml @@ -42,7 +42,7 @@ meant for the actors. scène. classifica l'indicazione di scena tecnica. - + a lighting cue 조명 신호 diff --git a/P5/Source/Specs/title.xml b/P5/Source/Specs/title.xml index 2f0cc50578..ad9eda4e2f 100644 --- a/P5/Source/Specs/title.xml +++ b/P5/Source/Specs/title.xml @@ -284,7 +284,7 @@ doit pas être utilisé.

una tipologia conveniente. klassifiziert den Titel entsprechend einer geeigneten Typologie. - + main title (주)제목 diff --git a/P5/Source/Specs/titlePart.xml b/P5/Source/Specs/titlePart.xml index a4e9c60f69..521d72fc32 100644 --- a/P5/Source/Specs/titlePart.xml +++ b/P5/Source/Specs/titlePart.xml @@ -44,7 +44,7 @@ indicated on a title page. specifica il ruolo di tale sezione o partizione all'interno del titolo main - + main Haupttitel diff --git a/P5/Source/Specs/usg.xml b/P5/Source/Specs/usg.xml index b36d90ac4c..034131e3a8 100644 --- a/P5/Source/Specs/usg.xml +++ b/P5/Source/Specs/usg.xml @@ -44,7 +44,7 @@ $Id$ clasifica la información sobre el uso aplicando una tipología funcional. classifica le informazioni sull'uso secondo una tipologia funzionale. - + geographic 지리적 diff --git a/P5/Source/Specs/xr.xml b/P5/Source/Specs/xr.xml index 49947b3b1c..74fc97fed9 100644 --- a/P5/Source/Specs/xr.xml +++ b/P5/Source/Specs/xr.xml @@ -58,7 +58,7 @@ $Id$ indica il tipo di riferimento incrociato secondo una tipologia funzionale - + synonym 유의어 From 8018ca620e1fa4d9a4a1f69ada1634b84e019ed9 Mon Sep 17 00:00:00 2001 From: Patricia O Connor Date: Wed, 10 Jan 2024 18:38:17 +0100 Subject: [PATCH 022/127] Added deprecation information for \ element --- P5/Source/Specs/re.xml | 116 ++++++++++++++++++++++------------------- 1 file changed, 62 insertions(+), 54 deletions(-) diff --git a/P5/Source/Specs/re.xml b/P5/Source/Specs/re.xml index 064e19571f..d5eb5bf56a 100644 --- a/P5/Source/Specs/re.xml +++ b/P5/Source/Specs/re.xml @@ -7,26 +7,34 @@ $Date$ $Id$ --> - + + Because an entry can + now occur inside an entry, the re element is no longer needed. These + Guidelines recommend using an entry with a type attribute value of + related instead. related entry 관련 표제 항목 相關辭條 sous-entrée entrada relativa voce corregata - contains a dictionary entry for a lexical item related to the headword, such as a compound - phrase or derived form, embedded inside a larger entry. - 복합어, 또는 큰 표제 항목 내부에 포함된 파생 형태와 같이 표제 항목과 관련된 어휘 항목을 포함한다. + contains a dictionary entry for a lexical item + related to the headword, such as a compound phrase or derived form, embedded inside a larger + entry. + 복합어, 또는 큰 표제 항목 내부에 포함된 파생 형태와 같이 표제 항목과 관련된 어휘 항목을 + 포함한다. 和標題字相關聯的字典辭條，像是包括在一個更大辭條中的複合片語或衍生字。 - 見出し語と関連する語彙項目を表す辞書項目を示す。例えば、より上位の項 目を持つ複合句、派生形など。 + 見出し語と関連する語彙項目を表す辞書項目を示す。例えば、より上位の項 + 目を持つ複合句、派生形など。 contient une entrée relative à un item lexical lié au mot-vedette, tel qu'un composé ou un dérivé, inclus dans une entrée plus large. contiene una entrada de diccionario para un elemento léxico relativo al lema, como p.ej. un sintagma compuesto o una forma derivada, y que se incluye en un entrada mayor. - contiene una voce di dizionario per un'unità lessicale - collegata al lemma, quale un sintagma composto o una forma derivata, inclusa in una voce più - ampia. + contiene una voce di dizionario per un'unità + lessicale collegata al lemma, quale un sintagma composto o una forma derivata, inclusa in una + voce più ampia. @@ -35,22 +43,22 @@ $Id$ - - - - - - - - - - + + + + + + + + + +

The following example from Webster's New Collegiate Dictionary - (Springfield, Mass.: G. & C. Merriam Company, 1975) shows a single related - entry for which no definition is given, since its meaning is held to be readily derivable from - the root entry:

+ (Springfield, Mass.: G. & C. Merriam Company, 1975) shows a single related entry + for which no definition is given, since its meaning is held to be readily derivable from the + root entry:

@@ -114,14 +122,14 @@ $Id$ Art de conduire les affaires de l'Etat ; Ligne de conduite raisonnée ; - Habileté manifestée dans les rapports avec les autres et qui consiste - essentiellement à amener autrui à faire ce que l'on désire, sans pour autant dévoiler - ses propres intentions. + Habileté manifestée dans les rapports avec les autres et qui consiste essentiellement + à amener autrui à faire ce que l'on désire, sans pour autant dévoiler ses propres + intentions. politicisme : - théorie selon laquelle les événements et les transformations historiques sont dus - essentiellement à la politique et à ses évolutions ; + théorie selon laquelle les événements et les transformations historiques sont + dus essentiellement à la politique et à ses évolutions ;
politiciste :
@@ -148,32 +156,33 @@ $Id$ élém. formant entrant dans la constr. de subst. désignant des unités de mesure, dans tous les - domaines de la phys., valant mille fois l'unité de base ; v. - kilogramme, kilogrammètre, kilomètre, kilotonne, kilowatt et aussi : - - - + domaines de la phys., valant mille fois l'unité de base ; v. kilogramme, + kilogrammètre, kilomètre, kilotonne, kilowatt et aussi : + +
kilocalorie :
- unité de mesure de quantité de chaleur valant mille calories (symb. kcal) ; + unité de mesure de quantité de chaleur valant mille calories (symb. kcal) ;
kilohertz :
- Unité de mesure de fréquence valant mille hertz (kHz ) ; + Unité de mesure de fréquence valant mille hertz (kHz + ) ;
kilojoule :
unité de mesure de travail valant mille joules (kJ) - ; + ;
kiloparsec :
- unité de mesure de longueur astronomique valant mille parsecs ; - + unité de mesure de longueur astronomique valant mille parsecs ;
kilovolt :
- unité de mesure de différences de potentiel, valant mille volts (kv). + unité de mesure de différences de potentiel, valant mille volts (kv). @@ -246,9 +255,11 @@ $Id$ Inglés-Español y Español-Inglés / The University of Chicago Spanish Dictionary, Fourth Edition, compiled by Carlos Castillo and Otto F. Bond (Chicago: University of Chicago Press, 1987) shows a number of related entries embedded in the - main entry. The original entry resembles the following:abeja [a·bé·xa]f. bee;abejera [a·be·xé·ra]f. beehive;abejón [a·be·xóon]m. - drone; bumblebee;abejorro [a·be·xó·rro]m. bumble - bee. One encoding for this entry would be:

+ main entry. The original entry resembles the following:abeja [a·bé·xa]f. bee;abejera + [a·be·xé·ra]f. beehive;abejón [a·be·xóon]m. drone; bumblebee;abejorro [a·be·xó·rro]m. bumble bee. One encoding for this entry would be:

@@ -293,17 +304,14 @@ $Id$ -

In the much larger Simon & Schuster Spanish-English - dictionary (Tana de Gámez, ed., Simon and Schuster's - International Dictionary (New York: Simon and Schuster, - 1973).) these derived forms of abeja - are treated as separate main entries, but there are other embedded - phrases shown as res in its main entry for - abeja:abeja, - f. 1. (ento.) bee. 2. busy bee, hard worker. 3. (astron.) A., - Musca. — a. albanila, mason bee; a. carpintera, carpenter bee; a. - reina or maestra, queen bee; a. neutra or obrera, worker bee. - This entry may be encoded thus:

+

In the much larger Simon & Schuster Spanish-English dictionary (Tana de Gámez, ed., + Simon and Schuster's International Dictionary (New York: Simon and + Schuster, 1973).) these derived forms of abeja are treated as + separate main entries, but there are other embedded phrases shown as res in its main + entry for abeja:abeja, f. 1. (ento.) bee. 2. busy + bee, hard worker. 3. (astron.) A., Musca. — a. albanila, mason bee; a. carpintera, carpenter + bee; a. reina or maestra, queen bee; a. neutra or obrera, worker bee. This entry may be + encoded thus:

@@ -354,8 +362,8 @@ $Id$

Dans les sous-éléments, il est identique à un élémententry, et utilisé là où un dictionnaire a enchâssé dans une entrée des informations qui auraient pu donner lieu à une entrée séparée. Quelques-uns font une distinction entre les sous-entrées, les entrées en - continu et différents autres types d'entrées dérivées ; aucune de ces typologies n'a été utilisée - ici.

+ continu et différents autres types d'entrées dérivées ; aucune de ces typologies n'a été + utilisée ici.

辞書モジュールで定義されている他の要素と混合して、文字データをとる かもしれない。

@@ -365,4 +373,4 @@ $Id$ - \ No newline at end of file + From ec549a415bdcf766d3849ffdd7b5c744199bc45f Mon Sep 17 00:00:00 2001 From: Patricia O Connor Date: Wed, 10 Jan 2024 19:18:50 +0100 Subject: [PATCH 023/127] Updated the examples to match --- .../Guidelines/en/DI-PrintDictionaries.xml | 4 +- P5/Source/Specs/re.xml | 96 +++++++++---------- 2 files changed, 50 insertions(+), 50 deletions(-) diff --git a/P5/Source/Guidelines/en/DI-PrintDictionaries.xml b/P5/Source/Guidelines/en/DI-PrintDictionaries.xml index 22fb2907c6..0cbf7dba8c 100644 --- a/P5/Source/Guidelines/en/DI-PrintDictionaries.xml +++ b/P5/Source/Guidelines/en/DI-PrintDictionaries.xml @@ -2018,14 +2018,14 @@ the same elements as an entry element.

bevee, buvee drinking - + bevvied adj - +

diff --git a/P5/Source/Specs/re.xml b/P5/Source/Specs/re.xml index d5eb5bf56a..2d8d9be069 100644 --- a/P5/Source/Specs/re.xml +++ b/P5/Source/Specs/re.xml @@ -72,7 +72,7 @@ $Id$ of, relating to, or affecting a nerve or the nervous system ... - +
neurally -ə-lē @@ -80,7 +80,7 @@ $Id$ adv - + @@ -97,7 +97,7 @@ $Id$ Faire fonctionner un siphon, transvaser (un liquide) au moyen d'un siphon. - + siphonnage [as] @@ -105,7 +105,7 @@ $Id$ n. - + @@ -126,23 +126,23 @@ $Id$ à amener autrui à faire ce que l'on désire, sans pour autant dévoiler ses propres intentions. - + politicisme : théorie selon laquelle les événements et les transformations historiques sont dus essentiellement à la politique et à ses évolutions ; -
- + +
politiciste :
qui relève du politicisme ou lui est propre ; - - + +
politicomanie :
manie de la politique ; - - + +
politicaille :
politique envisagée sous un angle déprécié ou méprisable. - + @@ -160,30 +160,30 @@ $Id$ kilogrammètre, kilomètre, kilotonne, kilowatt et aussi : - +
kilocalorie :
unité de mesure de quantité de chaleur valant mille calories (symb. kcal) ; - - + +
kilohertz :
Unité de mesure de fréquence valant mille hertz (kHz ) ; - - + +
kilojoule :
unité de mesure de travail valant mille joules (kJ) ; - - + +
kiloparsec :
unité de mesure de longueur astronomique valant mille parsecs ; - - + +
kilovolt :
unité de mesure de différences de potentiel, valant mille volts (kv). - + @@ -201,7 +201,7 @@ $Id$ 不馴順；狡猾不易對付。 ... - +
調皮地 tiau2 pi2 de @@ -209,7 +209,7 @@ $Id$ 副詞 - + @@ -225,28 +225,28 @@ $Id$ 昆蟲學, 蜜蜂 . 忙碌的蜜蜂，工作狂 。 天文學 , 蒼蠅座 — - + abeja albanila , 石巢蜂 ; -
- + +
abeja carpintera ,
木匠蜂 ; - - + +
abeja reina abeja maestra
女王蜂; - - + +
abeja neutra abeja obrera
工蜂 。 - + @@ -271,28 +271,28 @@ $Id$ (ento.) bee . busy bee, hard worker . (astron.) , Musca — - +
abeja albanila ,
mason bee; - - + +
abeja carpintera ,
carpenter bee ; - - + +
abeja reina abeja maestra
queen bee ; - - + +
abeja neutra abeja obrera
worker bee. - + + diff --git a/P5/Source/Guidelines/en/AI-AnalyticMechanisms.xml b/P5/Source/Guidelines/en/AI-AnalyticMechanisms.xml index 52d61894b1..51916016ff 100644 --- a/P5/Source/Guidelines/en/AI-AnalyticMechanisms.xml +++ b/P5/Source/Guidelines/en/AI-AnalyticMechanisms.xml @@ -1,11 +1,4 @@ - - +
Simple Analytic Mechanisms diff --git a/P5/Source/Guidelines/en/BIB-Bibliography.xml b/P5/Source/Guidelines/en/BIB-Bibliography.xml index 14d10b349b..885cba0cea 100644 --- a/P5/Source/Guidelines/en/BIB-Bibliography.xml +++ b/P5/Source/Guidelines/en/BIB-Bibliography.xml @@ -1,10 +1,4 @@ - +
Bibliography
diff --git a/P5/Source/Guidelines/en/CC-LanguageCorpora.xml b/P5/Source/Guidelines/en/CC-LanguageCorpora.xml index 094f7eef13..f4ca35b1c3 100644 --- a/P5/Source/Guidelines/en/CC-LanguageCorpora.xml +++ b/P5/Source/Guidelines/en/CC-LanguageCorpora.xml @@ -1,11 +1,4 @@ - - +
Language Corpora

The term language corpus is used to mean a number of diff --git a/P5/Source/Guidelines/en/CE-CertaintyResponsibility.xml b/P5/Source/Guidelines/en/CE-CertaintyResponsibility.xml index 42b275d759..02675dd175 100644 --- a/P5/Source/Guidelines/en/CE-CertaintyResponsibility.xml +++ b/P5/Source/Guidelines/en/CE-CertaintyResponsibility.xml @@ -1,11 +1,4 @@ - - +

Certainty, Precision, and Responsibility

Encoders of text often find it useful to indicate that some aspects diff --git a/P5/Source/Guidelines/en/CH-LanguagesCharacterSets.xml b/P5/Source/Guidelines/en/CH-LanguagesCharacterSets.xml index e87690893b..ad367a5213 100644 --- a/P5/Source/Guidelines/en/CH-LanguagesCharacterSets.xml +++ b/P5/Source/Guidelines/en/CH-LanguagesCharacterSets.xml @@ -1,11 +1,4 @@ - - +

Languages and Character Sets diff --git a/P5/Source/Guidelines/en/CO-CoreElements.xml b/P5/Source/Guidelines/en/CO-CoreElements.xml index 8ee380d944..676c389f19 100644 --- a/P5/Source/Guidelines/en/CO-CoreElements.xml +++ b/P5/Source/Guidelines/en/CO-CoreElements.xml @@ -1,11 +1,4 @@ - - +
Elements Available in All TEI Documents diff --git a/P5/Source/Guidelines/en/COL-Colophon.xml b/P5/Source/Guidelines/en/COL-Colophon.xml index 359a9c35b6..23f593e6a0 100644 --- a/P5/Source/Guidelines/en/COL-Colophon.xml +++ b/P5/Source/Guidelines/en/COL-Colophon.xml @@ -1,11 +1,4 @@ - - + diff --git a/P5/Source/Guidelines/en/DEPRECATIONS.xml b/P5/Source/Guidelines/en/DEPRECATIONS.xml index 9e4f84cd10..5436fb1f7f 100644 --- a/P5/Source/Guidelines/en/DEPRECATIONS.xml +++ b/P5/Source/Guidelines/en/DEPRECATIONS.xml @@ -1,11 +1,4 @@ - - +
Deprecations diff --git a/P5/Source/Guidelines/en/DI-PrintDictionaries.xml b/P5/Source/Guidelines/en/DI-PrintDictionaries.xml index 0cbf7dba8c..bcefb264a3 100644 --- a/P5/Source/Guidelines/en/DI-PrintDictionaries.xml +++ b/P5/Source/Guidelines/en/DI-PrintDictionaries.xml @@ -1,11 +1,4 @@ - - +
Dictionaries diff --git a/P5/Source/Guidelines/en/DR-PerformanceTexts.xml b/P5/Source/Guidelines/en/DR-PerformanceTexts.xml index 31bab48b4b..bfcf74fdea 100644 --- a/P5/Source/Guidelines/en/DR-PerformanceTexts.xml +++ b/P5/Source/Guidelines/en/DR-PerformanceTexts.xml @@ -1,11 +1,4 @@ - - + diff --git a/P5/Source/Guidelines/en/DS-DefaultTextStructure.xml b/P5/Source/Guidelines/en/DS-DefaultTextStructure.xml index 025e17fe52..953c585d79 100644 --- a/P5/Source/Guidelines/en/DS-DefaultTextStructure.xml +++ b/P5/Source/Guidelines/en/DS-DefaultTextStructure.xml @@ -1,11 +1,4 @@ - - +
Default Text Structure diff --git a/P5/Source/Guidelines/en/Dedication.xml b/P5/Source/Guidelines/en/Dedication.xml index 7e994dc732..3f105ab8b9 100644 --- a/P5/Source/Guidelines/en/Dedication.xml +++ b/P5/Source/Guidelines/en/Dedication.xml @@ -1,11 +1,4 @@ - - +
Dedication diff --git a/P5/Source/Guidelines/en/FM1-IntroductoryNote.xml b/P5/Source/Guidelines/en/FM1-IntroductoryNote.xml index 07464a05bb..eb1ada5f01 100644 --- a/P5/Source/Guidelines/en/FM1-IntroductoryNote.xml +++ b/P5/Source/Guidelines/en/FM1-IntroductoryNote.xml @@ -1,11 +1,4 @@ - - +
diff --git a/P5/Source/Guidelines/en/FS-FeatureStructures.xml b/P5/Source/Guidelines/en/FS-FeatureStructures.xml index df7354bad9..1a4c2cf972 100644 --- a/P5/Source/Guidelines/en/FS-FeatureStructures.xml +++ b/P5/Source/Guidelines/en/FS-FeatureStructures.xml @@ -1,11 +1,4 @@ - - +
Feature Structures diff --git a/P5/Source/Guidelines/en/FT-TablesFormulaeGraphics.xml b/P5/Source/Guidelines/en/FT-TablesFormulaeGraphics.xml index 4d9341e3a2..4a66f2484c 100644 --- a/P5/Source/Guidelines/en/FT-TablesFormulaeGraphics.xml +++ b/P5/Source/Guidelines/en/FT-TablesFormulaeGraphics.xml @@ -1,11 +1,4 @@ - - +
Tables, Formulæ, Graphics, and Notated Music diff --git a/P5/Source/Guidelines/en/GD-GraphsNetworksTrees.xml b/P5/Source/Guidelines/en/GD-GraphsNetworksTrees.xml index f7e1642626..f4491bd8c6 100644 --- a/P5/Source/Guidelines/en/GD-GraphsNetworksTrees.xml +++ b/P5/Source/Guidelines/en/GD-GraphsNetworksTrees.xml @@ -1,11 +1,4 @@ - - +
Graphs, Networks, and Trees

Graphical representations are widely used for displaying relations diff --git a/P5/Source/Guidelines/en/HD-Header.xml b/P5/Source/Guidelines/en/HD-Header.xml index 0eebacb3ba..01ca4db0b6 100644 --- a/P5/Source/Guidelines/en/HD-Header.xml +++ b/P5/Source/Guidelines/en/HD-Header.xml @@ -1,11 +1,4 @@ - - +

The TEI Header diff --git a/P5/Source/Guidelines/en/MS-ManuscriptDescription.xml b/P5/Source/Guidelines/en/MS-ManuscriptDescription.xml index b0514d371e..707db494e2 100644 --- a/P5/Source/Guidelines/en/MS-ManuscriptDescription.xml +++ b/P5/Source/Guidelines/en/MS-ManuscriptDescription.xml @@ -1,11 +1,4 @@ - - +
Manuscript Description diff --git a/P5/Source/Guidelines/en/ND-NamesDates.xml b/P5/Source/Guidelines/en/ND-NamesDates.xml index 080753c925..c19d65555f 100644 --- a/P5/Source/Guidelines/en/ND-NamesDates.xml +++ b/P5/Source/Guidelines/en/ND-NamesDates.xml @@ -1,11 +1,4 @@ - - +
diff --git a/P5/Source/Guidelines/en/NH-Non-hierarchical.xml b/P5/Source/Guidelines/en/NH-Non-hierarchical.xml index 358ec7f756..a810a46b98 100644 --- a/P5/Source/Guidelines/en/NH-Non-hierarchical.xml +++ b/P5/Source/Guidelines/en/NH-Non-hierarchical.xml @@ -1,11 +1,4 @@ - - + diff --git a/P5/Source/Guidelines/en/PARTIND.xml b/P5/Source/Guidelines/en/PARTIND.xml index 44896cef9d..7efdd6160c 100644 --- a/P5/Source/Guidelines/en/PARTIND.xml +++ b/P5/Source/Guidelines/en/PARTIND.xml @@ -1,11 +1,4 @@ - - + diff --git a/P5/Source/Guidelines/en/PH-PrimarySources.xml b/P5/Source/Guidelines/en/PH-PrimarySources.xml index 532ea6cb2a..4ac22926a4 100644 --- a/P5/Source/Guidelines/en/PH-PrimarySources.xml +++ b/P5/Source/Guidelines/en/PH-PrimarySources.xml @@ -1,11 +1,4 @@ - - +
diff --git a/P5/Source/Guidelines/en/PrefatoryNote.xml b/P5/Source/Guidelines/en/PrefatoryNote.xml index c0c541c781..c7d97f67e1 100644 --- a/P5/Source/Guidelines/en/PrefatoryNote.xml +++ b/P5/Source/Guidelines/en/PrefatoryNote.xml @@ -1,11 +1,4 @@ - - + diff --git a/P5/Source/Guidelines/en/REF-ATTRIBUTES.xml b/P5/Source/Guidelines/en/REF-ATTRIBUTES.xml index e0d5582f47..160ec9182d 100644 --- a/P5/Source/Guidelines/en/REF-ATTRIBUTES.xml +++ b/P5/Source/Guidelines/en/REF-ATTRIBUTES.xml @@ -1,11 +1,4 @@ - - + diff --git a/P5/Source/Guidelines/en/REF-CLASSES-ATTS.xml b/P5/Source/Guidelines/en/REF-CLASSES-ATTS.xml index 9c1a06179d..f01fb8cecb 100644 --- a/P5/Source/Guidelines/en/REF-CLASSES-ATTS.xml +++ b/P5/Source/Guidelines/en/REF-CLASSES-ATTS.xml @@ -1,11 +1,4 @@ - - + diff --git a/P5/Source/Guidelines/en/REF-CLASSES-MODEL.xml b/P5/Source/Guidelines/en/REF-CLASSES-MODEL.xml index 1c7e849c4b..a22126f37f 100644 --- a/P5/Source/Guidelines/en/REF-CLASSES-MODEL.xml +++ b/P5/Source/Guidelines/en/REF-CLASSES-MODEL.xml @@ -1,11 +1,4 @@ - - + diff --git a/P5/Source/Guidelines/en/REF-ELEMENTS.xml b/P5/Source/Guidelines/en/REF-ELEMENTS.xml index 50c7266c48..7342f68b86 100644 --- a/P5/Source/Guidelines/en/REF-ELEMENTS.xml +++ b/P5/Source/Guidelines/en/REF-ELEMENTS.xml @@ -1,11 +1,4 @@ - - + diff --git a/P5/Source/Guidelines/en/REF-MACROS.xml b/P5/Source/Guidelines/en/REF-MACROS.xml index 16b991845c..d30784f2bf 100644 --- a/P5/Source/Guidelines/en/REF-MACROS.xml +++ b/P5/Source/Guidelines/en/REF-MACROS.xml @@ -1,11 +1,4 @@ - - + diff --git a/P5/Source/Guidelines/en/SA-LinkingSegmentationAlignment.xml b/P5/Source/Guidelines/en/SA-LinkingSegmentationAlignment.xml index 86f566266e..e20d6056b9 100644 --- a/P5/Source/Guidelines/en/SA-LinkingSegmentationAlignment.xml +++ b/P5/Source/Guidelines/en/SA-LinkingSegmentationAlignment.xml @@ -1,11 +1,4 @@ - - +
Linking, Segmentation, and Alignment diff --git a/P5/Source/Guidelines/en/SG-GentleIntroduction.xml b/P5/Source/Guidelines/en/SG-GentleIntroduction.xml index 1a10159351..90585c375c 100644 --- a/P5/Source/Guidelines/en/SG-GentleIntroduction.xml +++ b/P5/Source/Guidelines/en/SG-GentleIntroduction.xml @@ -1,11 +1,4 @@ - - +
diff --git a/P5/Source/Guidelines/en/ST-Infrastructure.xml b/P5/Source/Guidelines/en/ST-Infrastructure.xml index 7110750331..a474073f17 100644 --- a/P5/Source/Guidelines/en/ST-Infrastructure.xml +++ b/P5/Source/Guidelines/en/ST-Infrastructure.xml @@ -1,11 +1,4 @@ - - +
The TEI Infrastructure diff --git a/P5/Source/Guidelines/en/TC-CriticalApparatus.xml b/P5/Source/Guidelines/en/TC-CriticalApparatus.xml index 94d9059057..93fcb0d8f1 100644 --- a/P5/Source/Guidelines/en/TC-CriticalApparatus.xml +++ b/P5/Source/Guidelines/en/TC-CriticalApparatus.xml @@ -1,11 +1,4 @@ - - +
Critical Apparatus diff --git a/P5/Source/Guidelines/en/TD-DocumentationElements.xml b/P5/Source/Guidelines/en/TD-DocumentationElements.xml index b610ee20ff..0b2b595ebd 100644 --- a/P5/Source/Guidelines/en/TD-DocumentationElements.xml +++ b/P5/Source/Guidelines/en/TD-DocumentationElements.xml @@ -1,11 +1,4 @@ - - +
- +
Transcriptions of Speech diff --git a/P5/Source/Guidelines/en/TitlePageVerso.xml b/P5/Source/Guidelines/en/TitlePageVerso.xml index bdd294ef10..ea1b857235 100644 --- a/P5/Source/Guidelines/en/TitlePageVerso.xml +++ b/P5/Source/Guidelines/en/TitlePageVerso.xml @@ -1,11 +1,4 @@ - - + diff --git a/P5/Source/Guidelines/en/USE.xml b/P5/Source/Guidelines/en/USE.xml index acd43c1eb8..f6fd2cb557 100644 --- a/P5/Source/Guidelines/en/USE.xml +++ b/P5/Source/Guidelines/en/USE.xml @@ -1,11 +1,4 @@ - - +
Using the TEI diff --git a/P5/Source/Guidelines/en/VE-Verse.xml b/P5/Source/Guidelines/en/VE-Verse.xml index ede8b26788..0e46ad5d72 100644 --- a/P5/Source/Guidelines/en/VE-Verse.xml +++ b/P5/Source/Guidelines/en/VE-Verse.xml @@ -1,11 +1,4 @@ - - +
Verse diff --git a/P5/Source/Guidelines/en/WD-NonStandardCharacters.xml b/P5/Source/Guidelines/en/WD-NonStandardCharacters.xml index ba3c5ce0c0..46d74b6d20 100644 --- a/P5/Source/Guidelines/en/WD-NonStandardCharacters.xml +++ b/P5/Source/Guidelines/en/WD-NonStandardCharacters.xml @@ -1,11 +1,4 @@ - - +
Characters, Glyphs, and Writing Modes diff --git a/P5/Source/Guidelines/fr/HD-Header.xml b/P5/Source/Guidelines/fr/HD-Header.xml index e9b5e3d105..a260362732 100644 --- a/P5/Source/Guidelines/fr/HD-Header.xml +++ b/P5/Source/Guidelines/fr/HD-Header.xml @@ -1,8 +1,4 @@ - +
En-tête TEI diff --git a/P5/Source/Specs/TEI.xml b/P5/Source/Specs/TEI.xml index a0fe94201b..8f058f55d7 100644 --- a/P5/Source/Specs/TEI.xml +++ b/P5/Source/Specs/TEI.xml @@ -1,11 +1,4 @@ - - + TEI document diff --git a/P5/Source/Specs/ab.xml b/P5/Source/Specs/ab.xml index 16bb2a91be..94036c4042 100644 --- a/P5/Source/Specs/ab.xml +++ b/P5/Source/Specs/ab.xml @@ -1,11 +1,4 @@ - - + anonymous block diff --git a/P5/Source/Specs/abbr.xml b/P5/Source/Specs/abbr.xml index fdd4c54201..4c66655d09 100644 --- a/P5/Source/Specs/abbr.xml +++ b/P5/Source/Specs/abbr.xml @@ -1,11 +1,4 @@ - - + abbreviation diff --git a/P5/Source/Specs/abstract.xml b/P5/Source/Specs/abstract.xml index 7a1165a182..aed6ce706f 100644 --- a/P5/Source/Specs/abstract.xml +++ b/P5/Source/Specs/abstract.xml @@ -1,11 +1,4 @@ - - + contains a summary or formal diff --git a/P5/Source/Specs/accMat.xml b/P5/Source/Specs/accMat.xml index ec4f558128..e7b7d75de0 100644 --- a/P5/Source/Specs/accMat.xml +++ b/P5/Source/Specs/accMat.xml @@ -1,11 +1,4 @@ - - + accompanying material diff --git a/P5/Source/Specs/acquisition.xml b/P5/Source/Specs/acquisition.xml index 1a51d12679..ed909fd03d 100644 --- a/P5/Source/Specs/acquisition.xml +++ b/P5/Source/Specs/acquisition.xml @@ -1,10 +1,4 @@ - + acquisition adquisición acquisition diff --git a/P5/Source/Specs/activity.xml b/P5/Source/Specs/activity.xml index c0a3e3a5d4..bcd2a98aea 100644 --- a/P5/Source/Specs/activity.xml +++ b/P5/Source/Specs/activity.xml @@ -1,10 +1,4 @@ - + activity actividad activité diff --git a/P5/Source/Specs/actor.xml b/P5/Source/Specs/actor.xml index e18aaff61f..de765a29a4 100644 --- a/P5/Source/Specs/actor.xml +++ b/P5/Source/Specs/actor.xml @@ -1,11 +1,4 @@ - - + contains the name of an actor appearing within a cast list. diff --git a/P5/Source/Specs/add.xml b/P5/Source/Specs/add.xml index 46e8e60d50..f65ba3530b 100644 --- a/P5/Source/Specs/add.xml +++ b/P5/Source/Specs/add.xml @@ -1,11 +1,4 @@ - - + addition diff --git a/P5/Source/Specs/addName.xml b/P5/Source/Specs/addName.xml index b225c9b786..736b0b7967 100644 --- a/P5/Source/Specs/addName.xml +++ b/P5/Source/Specs/addName.xml @@ -1,11 +1,4 @@ - - + additional name diff --git a/P5/Source/Specs/addSpan.xml b/P5/Source/Specs/addSpan.xml index 3053adcdc6..acaeea22c4 100644 --- a/P5/Source/Specs/addSpan.xml +++ b/P5/Source/Specs/addSpan.xml @@ -1,11 +1,4 @@ - - + added span of text diff --git a/P5/Source/Specs/additional.xml b/P5/Source/Specs/additional.xml index f2bb30769c..bc044829e4 100644 --- a/P5/Source/Specs/additional.xml +++ b/P5/Source/Specs/additional.xml @@ -1,11 +1,4 @@ - - + additional diff --git a/P5/Source/Specs/additions.xml b/P5/Source/Specs/additions.xml index 7c911618a1..1eed0204c2 100644 --- a/P5/Source/Specs/additions.xml +++ b/P5/Source/Specs/additions.xml @@ -1,11 +1,4 @@ - - + additions diff --git a/P5/Source/Specs/addrLine.xml b/P5/Source/Specs/addrLine.xml index 43d72e9a37..3c6dacb5d5 100644 --- a/P5/Source/Specs/addrLine.xml +++ b/P5/Source/Specs/addrLine.xml @@ -1,11 +1,4 @@ - - + address line diff --git a/P5/Source/Specs/address.xml b/P5/Source/Specs/address.xml index c1c088b2ed..e9905c503b 100644 --- a/P5/Source/Specs/address.xml +++ b/P5/Source/Specs/address.xml @@ -1,11 +1,4 @@ - - + address diff --git a/P5/Source/Specs/adminInfo.xml b/P5/Source/Specs/adminInfo.xml index 29c7b2d1f6..dcf9e77604 100644 --- a/P5/Source/Specs/adminInfo.xml +++ b/P5/Source/Specs/adminInfo.xml @@ -1,11 +1,4 @@ - - + administrative information diff --git a/P5/Source/Specs/affiliation.xml b/P5/Source/Specs/affiliation.xml index 98eb63da44..72d8565e83 100644 --- a/P5/Source/Specs/affiliation.xml +++ b/P5/Source/Specs/affiliation.xml @@ -1,10 +1,4 @@ - + affiliation affiliation contains an informal description of a person's present or past affiliation with some diff --git a/P5/Source/Specs/age.xml b/P5/Source/Specs/age.xml index 9460db2631..1ee5fa574a 100644 --- a/P5/Source/Specs/age.xml +++ b/P5/Source/Specs/age.xml @@ -1,10 +1,4 @@ - + age âge specifies the age of a person. diff --git a/P5/Source/Specs/alt.xml b/P5/Source/Specs/alt.xml index e9535b5bb4..04693d7422 100644 --- a/P5/Source/Specs/alt.xml +++ b/P5/Source/Specs/alt.xml @@ -1,5 +1,4 @@ - - + alternation diff --git a/P5/Source/Specs/altGrp.xml b/P5/Source/Specs/altGrp.xml index a98c9ddd05..aa13ad11a0 100644 --- a/P5/Source/Specs/altGrp.xml +++ b/P5/Source/Specs/altGrp.xml @@ -1,5 +1,4 @@ - - + alternation group diff --git a/P5/Source/Specs/altIdent.xml b/P5/Source/Specs/altIdent.xml index cea06c3cac..5396cfb634 100644 --- a/P5/Source/Specs/altIdent.xml +++ b/P5/Source/Specs/altIdent.xml @@ -1,11 +1,4 @@ - - + alternate identifier diff --git a/P5/Source/Specs/altIdentifier.xml b/P5/Source/Specs/altIdentifier.xml index be5f44ec39..bec4171154 100644 --- a/P5/Source/Specs/altIdentifier.xml +++ b/P5/Source/Specs/altIdentifier.xml @@ -1,10 +1,4 @@ - + alternative identifier 대체 확인소 替換識別符碼 diff --git a/P5/Source/Specs/alternate.xml b/P5/Source/Specs/alternate.xml index ebe3bb05ce..74b743d2bf 100644 --- a/P5/Source/Specs/alternate.xml +++ b/P5/Source/Specs/alternate.xml @@ -1,11 +1,4 @@ - - + indicates that the constructs referenced by its children form an alternation diff --git a/P5/Source/Specs/am.xml b/P5/Source/Specs/am.xml index c1b8a5989b..cb310b015f 100644 --- a/P5/Source/Specs/am.xml +++ b/P5/Source/Specs/am.xml @@ -1,11 +1,4 @@ - - + abbreviation marker diff --git a/P5/Source/Specs/analytic.xml b/P5/Source/Specs/analytic.xml index 7009b87082..d16227469d 100644 --- a/P5/Source/Specs/analytic.xml +++ b/P5/Source/Specs/analytic.xml @@ -1,11 +1,4 @@ - - + analytic level diff --git a/P5/Source/Specs/anchor.xml b/P5/Source/Specs/anchor.xml index 11733a1c20..3716cd863e 100644 --- a/P5/Source/Specs/anchor.xml +++ b/P5/Source/Specs/anchor.xml @@ -1,5 +1,4 @@ - - + anchor point diff --git a/P5/Source/Specs/annotation.xml b/P5/Source/Specs/annotation.xml index d02a30e514..cf50df7357 100644 --- a/P5/Source/Specs/annotation.xml +++ b/P5/Source/Specs/annotation.xml @@ -1,11 +1,4 @@ - - + diff --git a/P5/Source/Specs/annotationBlock.xml b/P5/Source/Specs/annotationBlock.xml index ac877ca5bd..a6bebb6efa 100644 --- a/P5/Source/Specs/annotationBlock.xml +++ b/P5/Source/Specs/annotationBlock.xml @@ -1,9 +1,4 @@ - - + diff --git a/P5/Source/Specs/anyElement.xml b/P5/Source/Specs/anyElement.xml index dd469edd6f..1623b944db 100644 --- a/P5/Source/Specs/anyElement.xml +++ b/P5/Source/Specs/anyElement.xml @@ -1,11 +1,4 @@ - - + diff --git a/P5/Source/Specs/app.xml b/P5/Source/Specs/app.xml index a4e1356cdd..6d860edfed 100644 --- a/P5/Source/Specs/app.xml +++ b/P5/Source/Specs/app.xml @@ -1,11 +1,4 @@ - - + apparatus entry diff --git a/P5/Source/Specs/appInfo.xml b/P5/Source/Specs/appInfo.xml index b14ddfacf0..7f5136c182 100644 --- a/P5/Source/Specs/appInfo.xml +++ b/P5/Source/Specs/appInfo.xml @@ -1,11 +1,4 @@ - - + application information diff --git a/P5/Source/Specs/application.xml b/P5/Source/Specs/application.xml index 12606b8fab..835695be44 100644 --- a/P5/Source/Specs/application.xml +++ b/P5/Source/Specs/application.xml @@ -1,10 +1,4 @@ - + provides information about an application which has acted upon the document. 문서에 사용한 애플리케이션에 관한 정보를 제시한다. proporciona información sobre la aplicación que ha diff --git a/P5/Source/Specs/arc.xml b/P5/Source/Specs/arc.xml index f2cdf06259..af9d075df2 100644 --- a/P5/Source/Specs/arc.xml +++ b/P5/Source/Specs/arc.xml @@ -1,11 +1,4 @@ - - + arc diff --git a/P5/Source/Specs/argument.xml b/P5/Source/Specs/argument.xml index 88cf10e8b5..a7b3f4862c 100644 --- a/P5/Source/Specs/argument.xml +++ b/P5/Source/Specs/argument.xml @@ -1,11 +1,4 @@ - - + argument diff --git a/P5/Source/Specs/att.anchoring.xml b/P5/Source/Specs/att.anchoring.xml index 2981a19b9a..4dec26ca88 100644 --- a/P5/Source/Specs/att.anchoring.xml +++ b/P5/Source/Specs/att.anchoring.xml @@ -1,11 +1,4 @@ - - + anchoring diff --git a/P5/Source/Specs/att.ascribed.directed.xml b/P5/Source/Specs/att.ascribed.directed.xml index 41ded2db0a..e622a8fae3 100644 --- a/P5/Source/Specs/att.ascribed.directed.xml +++ b/P5/Source/Specs/att.ascribed.directed.xml @@ -1,11 +1,4 @@ - - + provides attributes for elements representing speech or action that can be directed at a diff --git a/P5/Source/Specs/att.ascribed.xml b/P5/Source/Specs/att.ascribed.xml index 086fc17c7b..35aeb401fd 100644 --- a/P5/Source/Specs/att.ascribed.xml +++ b/P5/Source/Specs/att.ascribed.xml @@ -1,11 +1,4 @@ - - + provides attributes for elements representing speech or action that can be ascribed to a diff --git a/P5/Source/Specs/att.breaking.xml b/P5/Source/Specs/att.breaking.xml index dd6de73bfb..75aa797a6f 100644 --- a/P5/Source/Specs/att.breaking.xml +++ b/P5/Source/Specs/att.breaking.xml @@ -1,11 +1,4 @@ - - + provides attributes to indicate whether or not the element diff --git a/P5/Source/Specs/att.cReferencing.xml b/P5/Source/Specs/att.cReferencing.xml index e090afd37a..4d93a69506 100644 --- a/P5/Source/Specs/att.cReferencing.xml +++ b/P5/Source/Specs/att.cReferencing.xml @@ -1,11 +1,4 @@ - - + provides attributes that may be used to supply a diff --git a/P5/Source/Specs/att.calendarSystem.xml b/P5/Source/Specs/att.calendarSystem.xml index c34014f4d0..735166ae98 100644 --- a/P5/Source/Specs/att.calendarSystem.xml +++ b/P5/Source/Specs/att.calendarSystem.xml @@ -1,11 +1,4 @@ - - + provides attributes for indicating calendar systems to which a date belongs. diff --git a/P5/Source/Specs/att.canonical.xml b/P5/Source/Specs/att.canonical.xml index f621566293..79d247f589 100644 --- a/P5/Source/Specs/att.canonical.xml +++ b/P5/Source/Specs/att.canonical.xml @@ -1,11 +1,4 @@ - - + provides attributes that can be used to associate a representation such as a name or title diff --git a/P5/Source/Specs/att.citeStructurePart.xml b/P5/Source/Specs/att.citeStructurePart.xml index e25cca8223..6602536ce4 100644 --- a/P5/Source/Specs/att.citeStructurePart.xml +++ b/P5/Source/Specs/att.citeStructurePart.xml @@ -1,11 +1,4 @@ - - + provides attributes for selecting particular elements diff --git a/P5/Source/Specs/att.citing.xml b/P5/Source/Specs/att.citing.xml index a41f2441a8..b641d071b1 100644 --- a/P5/Source/Specs/att.citing.xml +++ b/P5/Source/Specs/att.citing.xml @@ -1,11 +1,4 @@ - - + provides attributes for specifying the specific part of a bibliographic item being cited. diff --git a/P5/Source/Specs/att.combinable.xml b/P5/Source/Specs/att.combinable.xml index a636a74c5d..25e6a4b9b7 100644 --- a/P5/Source/Specs/att.combinable.xml +++ b/P5/Source/Specs/att.combinable.xml @@ -1,11 +1,4 @@ - - + provides attributes indicating how multiple diff --git a/P5/Source/Specs/att.coordinated.xml b/P5/Source/Specs/att.coordinated.xml index acafc0061e..a6b3e5de71 100644 --- a/P5/Source/Specs/att.coordinated.xml +++ b/P5/Source/Specs/att.coordinated.xml @@ -1,11 +1,4 @@ - - + provides attributes that can be used to position their parent diff --git a/P5/Source/Specs/att.damaged.xml b/P5/Source/Specs/att.damaged.xml index 1b45cc5be5..9402e33774 100644 --- a/P5/Source/Specs/att.damaged.xml +++ b/P5/Source/Specs/att.damaged.xml @@ -1,11 +1,4 @@ - - + provides attributes describing the nature of any physical damage affecting a reading. diff --git a/P5/Source/Specs/att.datable.custom.xml b/P5/Source/Specs/att.datable.custom.xml index 6cb24c7321..a0ef6b64e1 100644 --- a/P5/Source/Specs/att.datable.custom.xml +++ b/P5/Source/Specs/att.datable.custom.xml @@ -1,11 +1,4 @@ - - + provides attributes for normalization of elements that contain datable events to a custom dating system diff --git a/P5/Source/Specs/att.datable.iso.xml b/P5/Source/Specs/att.datable.iso.xml index 5b37e247cc..12b4dfdfcf 100644 --- a/P5/Source/Specs/att.datable.iso.xml +++ b/P5/Source/Specs/att.datable.iso.xml @@ -1,11 +1,4 @@ - - + provides attributes for normalization of elements that contain datable events using the ISO 8601:2004 standard. diff --git a/P5/Source/Specs/att.datable.w3c.xml b/P5/Source/Specs/att.datable.w3c.xml index 09567b7fa4..4245b2c142 100644 --- a/P5/Source/Specs/att.datable.w3c.xml +++ b/P5/Source/Specs/att.datable.w3c.xml @@ -1,11 +1,4 @@ - - + provides attributes for normalization of elements that contain diff --git a/P5/Source/Specs/att.datable.xml b/P5/Source/Specs/att.datable.xml index f2f6276aea..671fbc2406 100644 --- a/P5/Source/Specs/att.datable.xml +++ b/P5/Source/Specs/att.datable.xml @@ -1,11 +1,4 @@ - - + provides attributes for normalization of elements diff --git a/P5/Source/Specs/att.datcat.xml b/P5/Source/Specs/att.datcat.xml index b23fde6e4d..1081434b20 100644 --- a/P5/Source/Specs/att.datcat.xml +++ b/P5/Source/Specs/att.datcat.xml @@ -1,11 +1,4 @@ - - + diff --git a/P5/Source/Specs/att.declarable.xml b/P5/Source/Specs/att.declarable.xml index 950e726ef4..fabf0ed10b 100644 --- a/P5/Source/Specs/att.declarable.xml +++ b/P5/Source/Specs/att.declarable.xml @@ -1,11 +1,4 @@ - - + provides attributes for those elements in the TEI header which diff --git a/P5/Source/Specs/att.declaring.xml b/P5/Source/Specs/att.declaring.xml index d3e2c3489a..300f0708fc 100644 --- a/P5/Source/Specs/att.declaring.xml +++ b/P5/Source/Specs/att.declaring.xml @@ -1,11 +1,4 @@ - - + provides attributes for elements which may be independently associated with a particular declarable element within the header, thus overriding the inherited default for that element. diff --git a/P5/Source/Specs/att.deprecated.xml b/P5/Source/Specs/att.deprecated.xml index 652ed437fc..20253e6a30 100644 --- a/P5/Source/Specs/att.deprecated.xml +++ b/P5/Source/Specs/att.deprecated.xml @@ -1,11 +1,4 @@ - - + provides attributes indicating how a deprecated feature will be treated in future releases. diff --git a/P5/Source/Specs/att.dimensions.xml b/P5/Source/Specs/att.dimensions.xml index 32c642bdbe..d6508d4a3e 100644 --- a/P5/Source/Specs/att.dimensions.xml +++ b/P5/Source/Specs/att.dimensions.xml @@ -1,11 +1,4 @@ - - + provides attributes for describing the size of physical objects. diff --git a/P5/Source/Specs/att.divLike.xml b/P5/Source/Specs/att.divLike.xml index c48a02c6c4..e265fe802a 100644 --- a/P5/Source/Specs/att.divLike.xml +++ b/P5/Source/Specs/att.divLike.xml @@ -1,11 +1,4 @@ - - + provides attributes common to all elements which behave in the same way as divisions. diff --git a/P5/Source/Specs/att.docStatus.xml b/P5/Source/Specs/att.docStatus.xml index da32c21536..368efd4e62 100644 --- a/P5/Source/Specs/att.docStatus.xml +++ b/P5/Source/Specs/att.docStatus.xml @@ -1,11 +1,4 @@ - - + provides attributes for use on metadata elements diff --git a/P5/Source/Specs/att.duration.iso.xml b/P5/Source/Specs/att.duration.iso.xml index 82d1ebdcf2..16621af215 100644 --- a/P5/Source/Specs/att.duration.iso.xml +++ b/P5/Source/Specs/att.duration.iso.xml @@ -1,11 +1,4 @@ - - + provides attributes for recording normalized temporal durations. diff --git a/P5/Source/Specs/att.duration.w3c.xml b/P5/Source/Specs/att.duration.w3c.xml index cb8d9d531d..d4651a2362 100644 --- a/P5/Source/Specs/att.duration.w3c.xml +++ b/P5/Source/Specs/att.duration.w3c.xml @@ -1,11 +1,4 @@ - - + provides attributes for recording normalized temporal durations. diff --git a/P5/Source/Specs/att.duration.xml b/P5/Source/Specs/att.duration.xml index 9b4682e57b..6cc0e96f21 100644 --- a/P5/Source/Specs/att.duration.xml +++ b/P5/Source/Specs/att.duration.xml @@ -1,11 +1,4 @@ - - + diff --git a/P5/Source/Specs/att.editLike.xml b/P5/Source/Specs/att.editLike.xml index 92a0a4ab62..8640add267 100644 --- a/P5/Source/Specs/att.editLike.xml +++ b/P5/Source/Specs/att.editLike.xml @@ -1,11 +1,4 @@ - - + provides attributes describing the nature of an encoded scholarly intervention or diff --git a/P5/Source/Specs/att.edition.xml b/P5/Source/Specs/att.edition.xml index 39e2d8db4c..7b9d75a576 100644 --- a/P5/Source/Specs/att.edition.xml +++ b/P5/Source/Specs/att.edition.xml @@ -1,11 +1,4 @@ - - + provides attributes identifying the source edition from which diff --git a/P5/Source/Specs/att.enjamb.xml b/P5/Source/Specs/att.enjamb.xml index d502201125..18da1c2d3a 100644 --- a/P5/Source/Specs/att.enjamb.xml +++ b/P5/Source/Specs/att.enjamb.xml @@ -1,11 +1,4 @@ - - + enjambement diff --git a/P5/Source/Specs/att.entryLike.xml b/P5/Source/Specs/att.entryLike.xml index 71dfa9584b..2d7250e04d 100644 --- a/P5/Source/Specs/att.entryLike.xml +++ b/P5/Source/Specs/att.entryLike.xml @@ -1,11 +1,4 @@ - - + provides attributes used to distinguish diff --git a/P5/Source/Specs/att.formula.xml b/P5/Source/Specs/att.formula.xml index 64257e3b07..1c586dfc1e 100644 --- a/P5/Source/Specs/att.formula.xml +++ b/P5/Source/Specs/att.formula.xml @@ -1,11 +1,4 @@ - - + provides attributes for defining a mathematical formula. diff --git a/P5/Source/Specs/att.fragmentable.xml b/P5/Source/Specs/att.fragmentable.xml index 0be8deabec..f7dc410d45 100644 --- a/P5/Source/Specs/att.fragmentable.xml +++ b/P5/Source/Specs/att.fragmentable.xml @@ -1,11 +1,4 @@ - - + provides attributes for representing diff --git a/P5/Source/Specs/att.gaijiProp.xml b/P5/Source/Specs/att.gaijiProp.xml index bccac95f5d..c4c2f03a60 100644 --- a/P5/Source/Specs/att.gaijiProp.xml +++ b/P5/Source/Specs/att.gaijiProp.xml @@ -1,11 +1,4 @@ - - + provides attributes for defining the properties of diff --git a/P5/Source/Specs/att.global.analytic.xml b/P5/Source/Specs/att.global.analytic.xml index ae354ea3ff..eb1687301f 100644 --- a/P5/Source/Specs/att.global.analytic.xml +++ b/P5/Source/Specs/att.global.analytic.xml @@ -1,11 +1,4 @@ - - + provides additional global attributes for associating specific analyses or diff --git a/P5/Source/Specs/att.global.change.xml b/P5/Source/Specs/att.global.change.xml index ce241257d7..ef080b28b3 100644 --- a/P5/Source/Specs/att.global.change.xml +++ b/P5/Source/Specs/att.global.change.xml @@ -1,11 +1,4 @@ - - + provides attributes allowing its member diff --git a/P5/Source/Specs/att.global.facs.xml b/P5/Source/Specs/att.global.facs.xml index 1edcc4cdca..28007af28a 100644 --- a/P5/Source/Specs/att.global.facs.xml +++ b/P5/Source/Specs/att.global.facs.xml @@ -1,11 +1,4 @@ - - + provides attributes used to express correspondence between an element and all or part of a facsimile image or surface. diff --git a/P5/Source/Specs/att.global.linking.xml b/P5/Source/Specs/att.global.linking.xml index ccc1a64726..5ad6efa452 100644 --- a/P5/Source/Specs/att.global.linking.xml +++ b/P5/Source/Specs/att.global.linking.xml @@ -1,11 +1,4 @@ - - + provides a set of attributes for hypertextual linking. diff --git a/P5/Source/Specs/att.global.rendition.xml b/P5/Source/Specs/att.global.rendition.xml index 34340ef03f..9980cede90 100644 --- a/P5/Source/Specs/att.global.rendition.xml +++ b/P5/Source/Specs/att.global.rendition.xml @@ -1,11 +1,4 @@ - - + provides rendering attributes common to all elements in the TEI encoding scheme. diff --git a/P5/Source/Specs/att.global.responsibility.xml b/P5/Source/Specs/att.global.responsibility.xml index 9003a64b4d..aefec8b5db 100644 --- a/P5/Source/Specs/att.global.responsibility.xml +++ b/P5/Source/Specs/att.global.responsibility.xml @@ -1,11 +1,4 @@ - - + provides attributes indicating the agent diff --git a/P5/Source/Specs/att.global.source.xml b/P5/Source/Specs/att.global.source.xml index 82b38e3da8..97371be41d 100644 --- a/P5/Source/Specs/att.global.source.xml +++ b/P5/Source/Specs/att.global.source.xml @@ -1,11 +1,4 @@ - - + provides attributes used by elements to point to an diff --git a/P5/Source/Specs/att.global.xml b/P5/Source/Specs/att.global.xml index 5206c756f7..f1d22e983b 100644 --- a/P5/Source/Specs/att.global.xml +++ b/P5/Source/Specs/att.global.xml @@ -1,11 +1,4 @@ - - + provides attributes common to all elements in the TEI encoding scheme. diff --git a/P5/Source/Specs/att.handFeatures.xml b/P5/Source/Specs/att.handFeatures.xml index 4aad59eae2..e4ad0a6e81 100644 --- a/P5/Source/Specs/att.handFeatures.xml +++ b/P5/Source/Specs/att.handFeatures.xml @@ -1,11 +1,4 @@ - - + provides attributes describing aspects of the hand in which a diff --git a/P5/Source/Specs/att.identified.xml b/P5/Source/Specs/att.identified.xml index b8fc55b42d..dbb3a3afb2 100644 --- a/P5/Source/Specs/att.identified.xml +++ b/P5/Source/Specs/att.identified.xml @@ -1,11 +1,4 @@ - - + provides identifying attributes for elements which can be diff --git a/P5/Source/Specs/att.internetMedia.xml b/P5/Source/Specs/att.internetMedia.xml index e5835976e6..9aa4efe255 100644 --- a/P5/Source/Specs/att.internetMedia.xml +++ b/P5/Source/Specs/att.internetMedia.xml @@ -1,11 +1,4 @@ - - + provides attributes for specifying the type of a computer diff --git a/P5/Source/Specs/att.interpLike.xml b/P5/Source/Specs/att.interpLike.xml index d15f6740d6..98431f97c8 100644 --- a/P5/Source/Specs/att.interpLike.xml +++ b/P5/Source/Specs/att.interpLike.xml @@ -1,11 +1,4 @@ - - + provides attributes for elements which represent a formal analysis or interpretation. diff --git a/P5/Source/Specs/att.lexicographic.normalized.xml b/P5/Source/Specs/att.lexicographic.normalized.xml index 337300cddd..0008557043 100644 --- a/P5/Source/Specs/att.lexicographic.normalized.xml +++ b/P5/Source/Specs/att.lexicographic.normalized.xml @@ -1,10 +1,4 @@ - + provides attributes for usage within word-level elements in the analysis module and within lexicographic microstructure in the dictionaries module. diff --git a/P5/Source/Specs/att.lexicographic.xml b/P5/Source/Specs/att.lexicographic.xml index 464bcfe8ff..2679a2a94a 100644 --- a/P5/Source/Specs/att.lexicographic.xml +++ b/P5/Source/Specs/att.lexicographic.xml @@ -1,11 +1,4 @@ - - + provides a set of attributes for specifying standard and normalized values, grammatical functions, alternate or equivalent forms, and information about composite parts. diff --git a/P5/Source/Specs/att.linguistic.xml b/P5/Source/Specs/att.linguistic.xml index bd11bfbe4c..1994494e63 100644 --- a/P5/Source/Specs/att.linguistic.xml +++ b/P5/Source/Specs/att.linguistic.xml @@ -1,11 +1,4 @@ - - + provides a set of attributes concerning linguistic features of tokens, for usage within token-level elements, specifically w and pc in the analysis module. diff --git a/P5/Source/Specs/att.locatable.xml b/P5/Source/Specs/att.locatable.xml index df84373384..830ae5281b 100644 --- a/P5/Source/Specs/att.locatable.xml +++ b/P5/Source/Specs/att.locatable.xml @@ -1,11 +1,4 @@ - - + diff --git a/P5/Source/Specs/att.measurement.xml b/P5/Source/Specs/att.measurement.xml index ab96a55a59..8e2716e25e 100644 --- a/P5/Source/Specs/att.measurement.xml +++ b/P5/Source/Specs/att.measurement.xml @@ -1,11 +1,4 @@ - - + provides attributes to represent a regularized or normalized measurement. diff --git a/P5/Source/Specs/att.media.xml b/P5/Source/Specs/att.media.xml index 5e5a093c2d..baaec18dac 100644 --- a/P5/Source/Specs/att.media.xml +++ b/P5/Source/Specs/att.media.xml @@ -1,11 +1,4 @@ - - + provides attributes for specifying display and related properties of diff --git a/P5/Source/Specs/att.metrical.xml b/P5/Source/Specs/att.metrical.xml index b36786bb2e..e63bd07782 100644 --- a/P5/Source/Specs/att.metrical.xml +++ b/P5/Source/Specs/att.metrical.xml @@ -1,11 +1,4 @@ - - + defines a set of attributes that certain elements may use to diff --git a/P5/Source/Specs/att.milestoneUnit.xml b/P5/Source/Specs/att.milestoneUnit.xml index 827ef2d624..b722615eef 100644 --- a/P5/Source/Specs/att.milestoneUnit.xml +++ b/P5/Source/Specs/att.milestoneUnit.xml @@ -1,11 +1,4 @@ - - + diff --git a/P5/Source/Specs/att.msClass.xml b/P5/Source/Specs/att.msClass.xml index 4406c1adfd..b12b18edfd 100644 --- a/P5/Source/Specs/att.msClass.xml +++ b/P5/Source/Specs/att.msClass.xml @@ -1,11 +1,4 @@ - - + provides attributes to indicate text type or classification. diff --git a/P5/Source/Specs/att.msExcerpt.xml b/P5/Source/Specs/att.msExcerpt.xml index 76e0c64442..92bc6df421 100644 --- a/P5/Source/Specs/att.msExcerpt.xml +++ b/P5/Source/Specs/att.msExcerpt.xml @@ -1,11 +1,4 @@ - - + manuscript excerpt diff --git a/P5/Source/Specs/att.namespaceable.xml b/P5/Source/Specs/att.namespaceable.xml index bd074e6118..605fbe4f52 100644 --- a/P5/Source/Specs/att.namespaceable.xml +++ b/P5/Source/Specs/att.namespaceable.xml @@ -1,11 +1,4 @@ - - + provides attributes indicating the target namespace for an object being created. diff --git a/P5/Source/Specs/att.naming.xml b/P5/Source/Specs/att.naming.xml index 610b0cbebc..8fc1e7b118 100644 --- a/P5/Source/Specs/att.naming.xml +++ b/P5/Source/Specs/att.naming.xml @@ -1,11 +1,4 @@ - - + provides attributes common to elements which refer to named persons, places, organizations etc. diff --git a/P5/Source/Specs/att.notated.xml b/P5/Source/Specs/att.notated.xml index e26c68d9d4..07055a8055 100644 --- a/P5/Source/Specs/att.notated.xml +++ b/P5/Source/Specs/att.notated.xml @@ -1,11 +1,4 @@ - - + diff --git a/P5/Source/Specs/att.partials.xml b/P5/Source/Specs/att.partials.xml index c5f1d17576..ea22dbe46a 100644 --- a/P5/Source/Specs/att.partials.xml +++ b/P5/Source/Specs/att.partials.xml @@ -1,11 +1,4 @@ - - + provides attributes for describing the extent of lexical references for a dictionary term. diff --git a/P5/Source/Specs/att.patternReplacement.xml b/P5/Source/Specs/att.patternReplacement.xml index a085eace50..95bd7803b9 100644 --- a/P5/Source/Specs/att.patternReplacement.xml +++ b/P5/Source/Specs/att.patternReplacement.xml @@ -1,11 +1,4 @@ - - + provides attributes for regular-expression matching and replacement. diff --git a/P5/Source/Specs/att.personal.xml b/P5/Source/Specs/att.personal.xml index 9d9924a140..aedeb3f6a4 100644 --- a/P5/Source/Specs/att.personal.xml +++ b/P5/Source/Specs/att.personal.xml @@ -1,11 +1,4 @@ - - + attributes for components of names usually, but not necessarily, personal names diff --git a/P5/Source/Specs/att.placement.xml b/P5/Source/Specs/att.placement.xml index 78a8d466fe..e500b40c38 100644 --- a/P5/Source/Specs/att.placement.xml +++ b/P5/Source/Specs/att.placement.xml @@ -1,11 +1,4 @@ - - + provides attributes for describing where on the source page or diff --git a/P5/Source/Specs/att.pointing.group.xml b/P5/Source/Specs/att.pointing.group.xml index 2427493314..1d0b692f75 100644 --- a/P5/Source/Specs/att.pointing.group.xml +++ b/P5/Source/Specs/att.pointing.group.xml @@ -1,11 +1,4 @@ - - + provides a set of attributes common to all elements which diff --git a/P5/Source/Specs/att.pointing.xml b/P5/Source/Specs/att.pointing.xml index d30eeafca6..068af0dec9 100644 --- a/P5/Source/Specs/att.pointing.xml +++ b/P5/Source/Specs/att.pointing.xml @@ -1,11 +1,4 @@ - - + provides a set of attributes used by all elements which point diff --git a/P5/Source/Specs/att.predicate.xml b/P5/Source/Specs/att.predicate.xml index 9ee3e01f0c..35fe5f572b 100644 --- a/P5/Source/Specs/att.predicate.xml +++ b/P5/Source/Specs/att.predicate.xml @@ -1,9 +1,4 @@ - - + provides attributes for filtering diff --git a/P5/Source/Specs/att.ranging.xml b/P5/Source/Specs/att.ranging.xml index 247bc3fb4d..b56565c95e 100644 --- a/P5/Source/Specs/att.ranging.xml +++ b/P5/Source/Specs/att.ranging.xml @@ -1,11 +1,4 @@ - - + provides attributes for describing numerical ranges. diff --git a/P5/Source/Specs/att.rdgPart.xml b/P5/Source/Specs/att.rdgPart.xml index d2248d3bad..f67751789a 100644 --- a/P5/Source/Specs/att.rdgPart.xml +++ b/P5/Source/Specs/att.rdgPart.xml @@ -1,11 +1,4 @@ - - + provides attributes to mark the beginning or ending of a fragmentary diff --git a/P5/Source/Specs/att.repeatable.xml b/P5/Source/Specs/att.repeatable.xml index 02c9990305..47943bf7fb 100644 --- a/P5/Source/Specs/att.repeatable.xml +++ b/P5/Source/Specs/att.repeatable.xml @@ -1,11 +1,4 @@ - - + provides attributes for the elements which define diff --git a/P5/Source/Specs/att.resourced.xml b/P5/Source/Specs/att.resourced.xml index 3a418b8924..24775f1a3b 100644 --- a/P5/Source/Specs/att.resourced.xml +++ b/P5/Source/Specs/att.resourced.xml @@ -1,11 +1,4 @@ - - + provides attributes by which a resource (such as an externally diff --git a/P5/Source/Specs/att.scoping.xml b/P5/Source/Specs/att.scoping.xml index 0e842aab3f..c8fd3ca714 100644 --- a/P5/Source/Specs/att.scoping.xml +++ b/P5/Source/Specs/att.scoping.xml @@ -1,11 +1,4 @@ - - + provides attributes for selecting particular elements diff --git a/P5/Source/Specs/att.segLike.xml b/P5/Source/Specs/att.segLike.xml index 959fcd1228..15bb6a8e2a 100644 --- a/P5/Source/Specs/att.segLike.xml +++ b/P5/Source/Specs/att.segLike.xml @@ -1,11 +1,4 @@ - - + provides attributes for elements used for arbitrary segmentation. diff --git a/P5/Source/Specs/att.sortable.xml b/P5/Source/Specs/att.sortable.xml index 5715c4bec9..124c80d0d9 100644 --- a/P5/Source/Specs/att.sortable.xml +++ b/P5/Source/Specs/att.sortable.xml @@ -1,11 +1,4 @@ - - + provides attributes for elements in lists or groups that are sortable, but whose sorting key cannot be derived mechanically from the element content. diff --git a/P5/Source/Specs/att.spanning.xml b/P5/Source/Specs/att.spanning.xml index 303db259ed..6a95a334da 100644 --- a/P5/Source/Specs/att.spanning.xml +++ b/P5/Source/Specs/att.spanning.xml @@ -1,11 +1,4 @@ - - + provides attributes for elements which delimit a span of text by pointing mechanisms rather than by enclosing it. diff --git a/P5/Source/Specs/att.styleDef.xml b/P5/Source/Specs/att.styleDef.xml index 31f0d9aa66..940244f693 100644 --- a/P5/Source/Specs/att.styleDef.xml +++ b/P5/Source/Specs/att.styleDef.xml @@ -1,11 +1,4 @@ - - + provides attributes to specify the name of a formal definition diff --git a/P5/Source/Specs/att.tableDecoration.xml b/P5/Source/Specs/att.tableDecoration.xml index ddc4e5845c..8c070340f0 100644 --- a/P5/Source/Specs/att.tableDecoration.xml +++ b/P5/Source/Specs/att.tableDecoration.xml @@ -1,11 +1,4 @@ - - + provides attributes used to decorate rows or cells of a table. diff --git a/P5/Source/Specs/att.textCritical.xml b/P5/Source/Specs/att.textCritical.xml index 518659e570..47dc41845a 100644 --- a/P5/Source/Specs/att.textCritical.xml +++ b/P5/Source/Specs/att.textCritical.xml @@ -1,11 +1,4 @@ - - + defines a set of attributes common to all elements representing variant readings in text critical work. diff --git a/P5/Source/Specs/att.timed.xml b/P5/Source/Specs/att.timed.xml index c0b97b0a41..a9773626a0 100644 --- a/P5/Source/Specs/att.timed.xml +++ b/P5/Source/Specs/att.timed.xml @@ -1,11 +1,4 @@ - - + provides attributes common to those elements which diff --git a/P5/Source/Specs/att.transcriptional.xml b/P5/Source/Specs/att.transcriptional.xml index ef7fc0ab36..b3904c4cd2 100644 --- a/P5/Source/Specs/att.transcriptional.xml +++ b/P5/Source/Specs/att.transcriptional.xml @@ -1,11 +1,4 @@ - - + provides attributes specific to elements encoding authorial or diff --git a/P5/Source/Specs/att.translatable.xml b/P5/Source/Specs/att.translatable.xml index 468adf33c6..547d2185ce 100644 --- a/P5/Source/Specs/att.translatable.xml +++ b/P5/Source/Specs/att.translatable.xml @@ -1,11 +1,4 @@ - - + provides attributes used to indicate the status of a translatable diff --git a/P5/Source/Specs/att.typed.xml b/P5/Source/Specs/att.typed.xml index b935b8ac26..49cc5c4c0c 100644 --- a/P5/Source/Specs/att.typed.xml +++ b/P5/Source/Specs/att.typed.xml @@ -1,11 +1,4 @@ - - + provides attributes that can be used to classify or subclassify elements in any way. diff --git a/P5/Source/Specs/att.witnessed.xml b/P5/Source/Specs/att.witnessed.xml index 32d4fab08a..f094331a9c 100644 --- a/P5/Source/Specs/att.witnessed.xml +++ b/P5/Source/Specs/att.witnessed.xml @@ -1,11 +1,4 @@ - - + provides attributes used to identify the witnesses diff --git a/P5/Source/Specs/att.written.xml b/P5/Source/Specs/att.written.xml index 62885d9634..16b8ff40fc 100644 --- a/P5/Source/Specs/att.written.xml +++ b/P5/Source/Specs/att.written.xml @@ -1,11 +1,4 @@ - - + diff --git a/P5/Source/Specs/att.xml b/P5/Source/Specs/att.xml index 6843c304e1..a68bf3029e 100644 --- a/P5/Source/Specs/att.xml +++ b/P5/Source/Specs/att.xml @@ -1,11 +1,4 @@ - - + attribute diff --git a/P5/Source/Specs/attDef.xml b/P5/Source/Specs/attDef.xml index 6e90fdbd0f..4dc8ac0e27 100644 --- a/P5/Source/Specs/attDef.xml +++ b/P5/Source/Specs/attDef.xml @@ -1,11 +1,4 @@ - - + attribute definition diff --git a/P5/Source/Specs/attList.xml b/P5/Source/Specs/attList.xml index b6b93b2875..a2a7c7fbc6 100644 --- a/P5/Source/Specs/attList.xml +++ b/P5/Source/Specs/attList.xml @@ -1,11 +1,4 @@ - - + attribute list diff --git a/P5/Source/Specs/attRef.xml b/P5/Source/Specs/attRef.xml index 05d134b7d0..7fc2e4859b 100644 --- a/P5/Source/Specs/attRef.xml +++ b/P5/Source/Specs/attRef.xml @@ -1,11 +1,4 @@ - - + attribute pointer diff --git a/P5/Source/Specs/author.xml b/P5/Source/Specs/author.xml index 5850d43e8c..cb9631791c 100644 --- a/P5/Source/Specs/author.xml +++ b/P5/Source/Specs/author.xml @@ -1,10 +1,4 @@ - + author autor/a auteur diff --git a/P5/Source/Specs/authority.xml b/P5/Source/Specs/authority.xml index 297d962128..cf06e094f6 100644 --- a/P5/Source/Specs/authority.xml +++ b/P5/Source/Specs/authority.xml @@ -1,11 +1,4 @@ - - + release authority diff --git a/P5/Source/Specs/availability.xml b/P5/Source/Specs/availability.xml index 3bae1d644d..461e029701 100644 --- a/P5/Source/Specs/availability.xml +++ b/P5/Source/Specs/availability.xml @@ -1,11 +1,4 @@ - - + availability diff --git a/P5/Source/Specs/back.xml b/P5/Source/Specs/back.xml index 5176385ba4..aeca2168e9 100644 --- a/P5/Source/Specs/back.xml +++ b/P5/Source/Specs/back.xml @@ -1,11 +1,4 @@ - - + back matter diff --git a/P5/Source/Specs/bibl.xml b/P5/Source/Specs/bibl.xml index 4f44ebf955..3a6df7d3f7 100644 --- a/P5/Source/Specs/bibl.xml +++ b/P5/Source/Specs/bibl.xml @@ -1,11 +1,4 @@ - - + bibliographic citation diff --git a/P5/Source/Specs/biblFull.xml b/P5/Source/Specs/biblFull.xml index 462ec3aceb..0210fdb6a9 100644 --- a/P5/Source/Specs/biblFull.xml +++ b/P5/Source/Specs/biblFull.xml @@ -1,11 +1,4 @@ - - + fully-structured bibliographic citation diff --git a/P5/Source/Specs/biblScope.xml b/P5/Source/Specs/biblScope.xml index 2b085e6491..a4b425029d 100644 --- a/P5/Source/Specs/biblScope.xml +++ b/P5/Source/Specs/biblScope.xml @@ -1,11 +1,4 @@ - - + scope of bibliographic reference diff --git a/P5/Source/Specs/biblStruct.xml b/P5/Source/Specs/biblStruct.xml index b0c19ad88a..1d011834d7 100644 --- a/P5/Source/Specs/biblStruct.xml +++ b/P5/Source/Specs/biblStruct.xml @@ -1,11 +1,4 @@ - - + structured bibliographic citation diff --git a/P5/Source/Specs/bicond.xml b/P5/Source/Specs/bicond.xml index 10fd209d21..86d96ebb67 100644 --- a/P5/Source/Specs/bicond.xml +++ b/P5/Source/Specs/bicond.xml @@ -1,11 +1,4 @@ - - + bi-conditional feature-structure constraint diff --git a/P5/Source/Specs/binary.xml b/P5/Source/Specs/binary.xml index df6b3a0b8a..b9be6e9697 100644 --- a/P5/Source/Specs/binary.xml +++ b/P5/Source/Specs/binary.xml @@ -1,11 +1,4 @@ - - + binary value diff --git a/P5/Source/Specs/binaryObject.xml b/P5/Source/Specs/binaryObject.xml index f8de99bd6d..f205dc4dfb 100644 --- a/P5/Source/Specs/binaryObject.xml +++ b/P5/Source/Specs/binaryObject.xml @@ -1,11 +1,4 @@ - - + provides encoded binary data representing an inline graphic, diff --git a/P5/Source/Specs/binding.xml b/P5/Source/Specs/binding.xml index 110efc583a..a195459dcf 100644 --- a/P5/Source/Specs/binding.xml +++ b/P5/Source/Specs/binding.xml @@ -1,10 +1,4 @@ - + binding reliure contains a description of one binding, i.e. type of covering, boards, diff --git a/P5/Source/Specs/bindingDesc.xml b/P5/Source/Specs/bindingDesc.xml index 2fc39632d6..96fcfb40f3 100644 --- a/P5/Source/Specs/bindingDesc.xml +++ b/P5/Source/Specs/bindingDesc.xml @@ -1,11 +1,4 @@ - - + binding description diff --git a/P5/Source/Specs/birth.xml b/P5/Source/Specs/birth.xml index 7bd2cc19dd..897232af4b 100644 --- a/P5/Source/Specs/birth.xml +++ b/P5/Source/Specs/birth.xml @@ -1,10 +1,4 @@ - + birth naissance contains information about a person's birth, such as its date and place. diff --git a/P5/Source/Specs/bloc.xml b/P5/Source/Specs/bloc.xml index 8e187f0769..2746d5b0c8 100644 --- a/P5/Source/Specs/bloc.xml +++ b/P5/Source/Specs/bloc.xml @@ -1,10 +1,4 @@ - + bloc bloc contains the name of a geo-political unit consisting of two or more nation states or diff --git a/P5/Source/Specs/body.xml b/P5/Source/Specs/body.xml index c04dd1c4ce..8cd927de7d 100644 --- a/P5/Source/Specs/body.xml +++ b/P5/Source/Specs/body.xml @@ -1,11 +1,4 @@ - - + text body diff --git a/P5/Source/Specs/broadcast.xml b/P5/Source/Specs/broadcast.xml index 2221d187e3..d18684b500 100644 --- a/P5/Source/Specs/broadcast.xml +++ b/P5/Source/Specs/broadcast.xml @@ -1,11 +1,4 @@ - - + broadcast diff --git a/P5/Source/Specs/byline.xml b/P5/Source/Specs/byline.xml index 6f55cc74d2..7791edd8a2 100644 --- a/P5/Source/Specs/byline.xml +++ b/P5/Source/Specs/byline.xml @@ -1,11 +1,4 @@ - - + byline diff --git a/P5/Source/Specs/c.xml b/P5/Source/Specs/c.xml index cc9f79459b..f4c4d54a59 100644 --- a/P5/Source/Specs/c.xml +++ b/P5/Source/Specs/c.xml @@ -1,11 +1,4 @@ - - + character diff --git a/P5/Source/Specs/cRefPattern.xml b/P5/Source/Specs/cRefPattern.xml index f3bcffa580..dc58b6f9f9 100644 --- a/P5/Source/Specs/cRefPattern.xml +++ b/P5/Source/Specs/cRefPattern.xml @@ -1,11 +1,4 @@ - - + canonical reference pattern diff --git a/P5/Source/Specs/caesura.xml b/P5/Source/Specs/caesura.xml index aa5e553369..198a841591 100644 --- a/P5/Source/Specs/caesura.xml +++ b/P5/Source/Specs/caesura.xml @@ -1,11 +1,4 @@ - - + marks the point at which a metrical line may be divided. diff --git a/P5/Source/Specs/calendar.xml b/P5/Source/Specs/calendar.xml index 2fb79f36b3..1d27b8a48f 100644 --- a/P5/Source/Specs/calendar.xml +++ b/P5/Source/Specs/calendar.xml @@ -1,11 +1,4 @@ - - + calendar diff --git a/P5/Source/Specs/calendarDesc.xml b/P5/Source/Specs/calendarDesc.xml index c052006bc6..c7ed2b1e1a 100644 --- a/P5/Source/Specs/calendarDesc.xml +++ b/P5/Source/Specs/calendarDesc.xml @@ -1,11 +1,4 @@ - - + calendar description diff --git a/P5/Source/Specs/camera.xml b/P5/Source/Specs/camera.xml index 1f6c404934..1b9448cef2 100644 --- a/P5/Source/Specs/camera.xml +++ b/P5/Source/Specs/camera.xml @@ -1,11 +1,4 @@ - - + camera diff --git a/P5/Source/Specs/caption.xml b/P5/Source/Specs/caption.xml index b048bafabf..4be4953868 100644 --- a/P5/Source/Specs/caption.xml +++ b/P5/Source/Specs/caption.xml @@ -1,11 +1,4 @@ - - + caption diff --git a/P5/Source/Specs/case.xml b/P5/Source/Specs/case.xml index 7fee52299c..449e3c61fe 100644 --- a/P5/Source/Specs/case.xml +++ b/P5/Source/Specs/case.xml @@ -1,11 +1,4 @@ - - + case diff --git a/P5/Source/Specs/castGroup.xml b/P5/Source/Specs/castGroup.xml index 0f49b30933..104ff6e9ca 100644 --- a/P5/Source/Specs/castGroup.xml +++ b/P5/Source/Specs/castGroup.xml @@ -1,11 +1,4 @@ - - + cast list grouping diff --git a/P5/Source/Specs/castItem.xml b/P5/Source/Specs/castItem.xml index 9e3a240a09..9dcf03c2df 100644 --- a/P5/Source/Specs/castItem.xml +++ b/P5/Source/Specs/castItem.xml @@ -1,11 +1,4 @@ - - + cast list item diff --git a/P5/Source/Specs/castList.xml b/P5/Source/Specs/castList.xml index 6bf8c3db2c..30081fa397 100644 --- a/P5/Source/Specs/castList.xml +++ b/P5/Source/Specs/castList.xml @@ -1,11 +1,4 @@ - - + cast list diff --git a/P5/Source/Specs/catDesc.xml b/P5/Source/Specs/catDesc.xml index 7f80b20ac1..d94f20bf5c 100644 --- a/P5/Source/Specs/catDesc.xml +++ b/P5/Source/Specs/catDesc.xml @@ -1,11 +1,4 @@ - - + category description diff --git a/P5/Source/Specs/catRef.xml b/P5/Source/Specs/catRef.xml index dcfd95506b..dd50289688 100644 --- a/P5/Source/Specs/catRef.xml +++ b/P5/Source/Specs/catRef.xml @@ -1,11 +1,4 @@ - - + category reference diff --git a/P5/Source/Specs/catchwords.xml b/P5/Source/Specs/catchwords.xml index e9cbc1b77f..5db3ac3d98 100644 --- a/P5/Source/Specs/catchwords.xml +++ b/P5/Source/Specs/catchwords.xml @@ -1,11 +1,4 @@ - - + catchwords diff --git a/P5/Source/Specs/category.xml b/P5/Source/Specs/category.xml index f3ce5ea56f..add5e24715 100644 --- a/P5/Source/Specs/category.xml +++ b/P5/Source/Specs/category.xml @@ -1,11 +1,4 @@ - - + category diff --git a/P5/Source/Specs/cb.xml b/P5/Source/Specs/cb.xml index 9513db699e..8733f949aa 100644 --- a/P5/Source/Specs/cb.xml +++ b/P5/Source/Specs/cb.xml @@ -1,11 +1,4 @@ - - + column beginning diff --git a/P5/Source/Specs/cell.xml b/P5/Source/Specs/cell.xml index 2fa7642941..c5b8e783a5 100644 --- a/P5/Source/Specs/cell.xml +++ b/P5/Source/Specs/cell.xml @@ -1,11 +1,4 @@ - - + cell diff --git a/P5/Source/Specs/certainty.xml b/P5/Source/Specs/certainty.xml index 8f27e128c0..cc4245e8bf 100644 --- a/P5/Source/Specs/certainty.xml +++ b/P5/Source/Specs/certainty.xml @@ -1,11 +1,4 @@ - - + indicates the degree of certainty associated diff --git a/P5/Source/Specs/change.xml b/P5/Source/Specs/change.xml index 8038d8e5c9..41432e8858 100644 --- a/P5/Source/Specs/change.xml +++ b/P5/Source/Specs/change.xml @@ -1,10 +1,4 @@ - + change Änderung 変更 diff --git a/P5/Source/Specs/channel.xml b/P5/Source/Specs/channel.xml index 5a4a5a615e..cbc26f9f1e 100644 --- a/P5/Source/Specs/channel.xml +++ b/P5/Source/Specs/channel.xml @@ -1,11 +1,4 @@ - - + primary channel diff --git a/P5/Source/Specs/char.xml b/P5/Source/Specs/char.xml index f4c5d107c5..0ee8e4a39a 100644 --- a/P5/Source/Specs/char.xml +++ b/P5/Source/Specs/char.xml @@ -1,11 +1,4 @@ - - + character diff --git a/P5/Source/Specs/charDecl.xml b/P5/Source/Specs/charDecl.xml index 773cc98e34..cb28b4f15c 100644 --- a/P5/Source/Specs/charDecl.xml +++ b/P5/Source/Specs/charDecl.xml @@ -1,11 +1,4 @@ - - + character declarations diff --git a/P5/Source/Specs/choice.xml b/P5/Source/Specs/choice.xml index 481c3da878..5bd682b7b7 100644 --- a/P5/Source/Specs/choice.xml +++ b/P5/Source/Specs/choice.xml @@ -1,11 +1,4 @@ - - + choice diff --git a/P5/Source/Specs/cit.xml b/P5/Source/Specs/cit.xml index 452b3b4dee..a91da2eba5 100644 --- a/P5/Source/Specs/cit.xml +++ b/P5/Source/Specs/cit.xml @@ -1,11 +1,4 @@ - - + cited quotation diff --git a/P5/Source/Specs/citeData.xml b/P5/Source/Specs/citeData.xml index 806659b50c..765b2a6745 100644 --- a/P5/Source/Specs/citeData.xml +++ b/P5/Source/Specs/citeData.xml @@ -1,11 +1,4 @@ - - + citation data diff --git a/P5/Source/Specs/citeStructure.xml b/P5/Source/Specs/citeStructure.xml index 9244d3cf24..1267156072 100644 --- a/P5/Source/Specs/citeStructure.xml +++ b/P5/Source/Specs/citeStructure.xml @@ -1,11 +1,4 @@ - - + citation structure diff --git a/P5/Source/Specs/citedRange.xml b/P5/Source/Specs/citedRange.xml index deb0192e3d..96ab927cc7 100644 --- a/P5/Source/Specs/citedRange.xml +++ b/P5/Source/Specs/citedRange.xml @@ -1,11 +1,4 @@ - - + cited range diff --git a/P5/Source/Specs/cl.xml b/P5/Source/Specs/cl.xml index 93f9fa9fe5..ffb6558a25 100644 --- a/P5/Source/Specs/cl.xml +++ b/P5/Source/Specs/cl.xml @@ -1,11 +1,4 @@ - - + clause diff --git a/P5/Source/Specs/classCode.xml b/P5/Source/Specs/classCode.xml index 8037f787b2..99a61f1f23 100644 --- a/P5/Source/Specs/classCode.xml +++ b/P5/Source/Specs/classCode.xml @@ -1,11 +1,4 @@ - - + classification code diff --git a/P5/Source/Specs/classDecl.xml b/P5/Source/Specs/classDecl.xml index ebb75fedae..324705b85f 100644 --- a/P5/Source/Specs/classDecl.xml +++ b/P5/Source/Specs/classDecl.xml @@ -1,11 +1,4 @@ - - + classification declarations diff --git a/P5/Source/Specs/classRef.xml b/P5/Source/Specs/classRef.xml index f28b7afa08..2b4ed3ae86 100644 --- a/P5/Source/Specs/classRef.xml +++ b/P5/Source/Specs/classRef.xml @@ -1,11 +1,4 @@ - - + points to the specification for an attribute or model class which is to be included in a schema diff --git a/P5/Source/Specs/classSpec.xml b/P5/Source/Specs/classSpec.xml index e1dcd97806..35b92073eb 100644 --- a/P5/Source/Specs/classSpec.xml +++ b/P5/Source/Specs/classSpec.xml @@ -1,11 +1,4 @@ - - + class specification diff --git a/P5/Source/Specs/classes.xml b/P5/Source/Specs/classes.xml index 0b19b23249..5ae286a64a 100644 --- a/P5/Source/Specs/classes.xml +++ b/P5/Source/Specs/classes.xml @@ -1,11 +1,4 @@ - - + diff --git a/P5/Source/Specs/climate.xml b/P5/Source/Specs/climate.xml index a60a1b6573..1f8409cdb6 100644 --- a/P5/Source/Specs/climate.xml +++ b/P5/Source/Specs/climate.xml @@ -1,10 +1,4 @@ - + climate climat contains information about the physical climate of a place. diff --git a/P5/Source/Specs/closer.xml b/P5/Source/Specs/closer.xml index 8346d985d3..d62ca55468 100644 --- a/P5/Source/Specs/closer.xml +++ b/P5/Source/Specs/closer.xml @@ -1,11 +1,4 @@ - - + closer diff --git a/P5/Source/Specs/code.xml b/P5/Source/Specs/code.xml index 40e0259249..4d3a193ed8 100644 --- a/P5/Source/Specs/code.xml +++ b/P5/Source/Specs/code.xml @@ -1,11 +1,4 @@ - - + contains literal code from some formal language such as a diff --git a/P5/Source/Specs/collation.xml b/P5/Source/Specs/collation.xml index 2e33414be2..0763b55d71 100644 --- a/P5/Source/Specs/collation.xml +++ b/P5/Source/Specs/collation.xml @@ -1,11 +1,4 @@ - - + collation diff --git a/P5/Source/Specs/collection.xml b/P5/Source/Specs/collection.xml index d15255849a..1b2a33d3b9 100644 --- a/P5/Source/Specs/collection.xml +++ b/P5/Source/Specs/collection.xml @@ -1,11 +1,4 @@ - - + collection diff --git a/P5/Source/Specs/colloc.xml b/P5/Source/Specs/colloc.xml index 0de6099e7d..d6ff1f2402 100644 --- a/P5/Source/Specs/colloc.xml +++ b/P5/Source/Specs/colloc.xml @@ -1,11 +1,4 @@ - - + collocate diff --git a/P5/Source/Specs/colophon.xml b/P5/Source/Specs/colophon.xml index 0dc561b7e9..023ef2c58a 100644 --- a/P5/Source/Specs/colophon.xml +++ b/P5/Source/Specs/colophon.xml @@ -1,11 +1,4 @@ - - + colophon diff --git a/P5/Source/Specs/cond.xml b/P5/Source/Specs/cond.xml index 48d88ca063..075eb6604b 100644 --- a/P5/Source/Specs/cond.xml +++ b/P5/Source/Specs/cond.xml @@ -1,11 +1,4 @@ - - + conditional feature-structure constraint diff --git a/P5/Source/Specs/condition.xml b/P5/Source/Specs/condition.xml index daed2a0c98..b8557cf82f 100644 --- a/P5/Source/Specs/condition.xml +++ b/P5/Source/Specs/condition.xml @@ -1,11 +1,4 @@ - - + condition diff --git a/P5/Source/Specs/constitution.xml b/P5/Source/Specs/constitution.xml index d3d55c4c3e..1a93567456 100644 --- a/P5/Source/Specs/constitution.xml +++ b/P5/Source/Specs/constitution.xml @@ -1,11 +1,4 @@ - - + constitution diff --git a/P5/Source/Specs/constraint.xml b/P5/Source/Specs/constraint.xml index 0183768f58..0fed8d29f4 100644 --- a/P5/Source/Specs/constraint.xml +++ b/P5/Source/Specs/constraint.xml @@ -1,11 +1,4 @@ - - + constraint rules diff --git a/P5/Source/Specs/constraintSpec.xml b/P5/Source/Specs/constraintSpec.xml index 6ebabade96..730a21006f 100644 --- a/P5/Source/Specs/constraintSpec.xml +++ b/P5/Source/Specs/constraintSpec.xml @@ -1,11 +1,4 @@ - - + constraint on schema diff --git a/P5/Source/Specs/content.xml b/P5/Source/Specs/content.xml index a0b75ca295..a1bb138d7a 100644 --- a/P5/Source/Specs/content.xml +++ b/P5/Source/Specs/content.xml @@ -1,11 +1,4 @@ - - + content model diff --git a/P5/Source/Specs/conversion.xml b/P5/Source/Specs/conversion.xml index dbc51d2ff0..baa605de6c 100644 --- a/P5/Source/Specs/conversion.xml +++ b/P5/Source/Specs/conversion.xml @@ -1,10 +1,4 @@ - + defines how to calculate one unit of measure in terms of another. diff --git a/P5/Source/Specs/corr.xml b/P5/Source/Specs/corr.xml index 9bde810624..18a41fe203 100644 --- a/P5/Source/Specs/corr.xml +++ b/P5/Source/Specs/corr.xml @@ -1,11 +1,4 @@ - - + correction diff --git a/P5/Source/Specs/correction.xml b/P5/Source/Specs/correction.xml index 21683e3e93..986ff0c72f 100644 --- a/P5/Source/Specs/correction.xml +++ b/P5/Source/Specs/correction.xml @@ -1,11 +1,4 @@ - - + correction principles diff --git a/P5/Source/Specs/correspAction.xml b/P5/Source/Specs/correspAction.xml index 5231cd5f57..63b7665597 100644 --- a/P5/Source/Specs/correspAction.xml +++ b/P5/Source/Specs/correspAction.xml @@ -1,11 +1,4 @@ - - + correspondence action diff --git a/P5/Source/Specs/correspContext.xml b/P5/Source/Specs/correspContext.xml index 3f79fbeccc..95725f99c8 100644 --- a/P5/Source/Specs/correspContext.xml +++ b/P5/Source/Specs/correspContext.xml @@ -1,11 +1,4 @@ - - + correspondence context diff --git a/P5/Source/Specs/correspDesc.xml b/P5/Source/Specs/correspDesc.xml index eab25147a1..61185f249b 100644 --- a/P5/Source/Specs/correspDesc.xml +++ b/P5/Source/Specs/correspDesc.xml @@ -1,11 +1,4 @@ - - + correspondence description diff --git a/P5/Source/Specs/country.xml b/P5/Source/Specs/country.xml index 673cc04cc7..5261f47454 100644 --- a/P5/Source/Specs/country.xml +++ b/P5/Source/Specs/country.xml @@ -1,10 +1,4 @@ - + country pays contains the name of a geo-political unit, such as a nation, country, colony, or diff --git a/P5/Source/Specs/creation.xml b/P5/Source/Specs/creation.xml index d996fd6126..0d327c884c 100644 --- a/P5/Source/Specs/creation.xml +++ b/P5/Source/Specs/creation.xml @@ -1,10 +1,4 @@ - + creation création Entstehung diff --git a/P5/Source/Specs/custEvent.xml b/P5/Source/Specs/custEvent.xml index 52b3ab5565..24d4f5e63e 100644 --- a/P5/Source/Specs/custEvent.xml +++ b/P5/Source/Specs/custEvent.xml @@ -1,10 +1,4 @@ - + custodial event 보관 사건 diff --git a/P5/Source/Specs/custodialHist.xml b/P5/Source/Specs/custodialHist.xml index 230b2ecbae..63a149864d 100644 --- a/P5/Source/Specs/custodialHist.xml +++ b/P5/Source/Specs/custodialHist.xml @@ -1,11 +1,4 @@ - - + custodial history diff --git a/P5/Source/Specs/damage.xml b/P5/Source/Specs/damage.xml index 570c0f827e..9a55399d2f 100644 --- a/P5/Source/Specs/damage.xml +++ b/P5/Source/Specs/damage.xml @@ -1,10 +1,4 @@ - + damage 当該文献におけるテキストの損傷部分を示す。 dommage diff --git a/P5/Source/Specs/damageSpan.xml b/P5/Source/Specs/damageSpan.xml index 8eece011b5..39c84ff87b 100644 --- a/P5/Source/Specs/damageSpan.xml +++ b/P5/Source/Specs/damageSpan.xml @@ -1,11 +1,4 @@ - - + damaged span of text diff --git a/P5/Source/Specs/dataFacet.xml b/P5/Source/Specs/dataFacet.xml index e6625f0a15..6954775c24 100644 --- a/P5/Source/Specs/dataFacet.xml +++ b/P5/Source/Specs/dataFacet.xml @@ -1,11 +1,4 @@ - - + Restricts the value of the strings used to represent values of a datatype, diff --git a/P5/Source/Specs/dataRef.xml b/P5/Source/Specs/dataRef.xml index 0ec03f9ac7..44b85684e0 100644 --- a/P5/Source/Specs/dataRef.xml +++ b/P5/Source/Specs/dataRef.xml @@ -1,11 +1,4 @@ - - + identifies the datatype of an attribute value, either by referencing an item in an externally defined datatype library, or by diff --git a/P5/Source/Specs/dataSpec.xml b/P5/Source/Specs/dataSpec.xml index 45038fd7c8..4cbf602afc 100644 --- a/P5/Source/Specs/dataSpec.xml +++ b/P5/Source/Specs/dataSpec.xml @@ -1,11 +1,4 @@ - - + datatype specification diff --git a/P5/Source/Specs/datatype.xml b/P5/Source/Specs/datatype.xml index 08231604d8..5cda5dca0b 100644 --- a/P5/Source/Specs/datatype.xml +++ b/P5/Source/Specs/datatype.xml @@ -1,11 +1,4 @@ - - + datatype diff --git a/P5/Source/Specs/date.xml b/P5/Source/Specs/date.xml index 6df99c070a..ea67955764 100644 --- a/P5/Source/Specs/date.xml +++ b/P5/Source/Specs/date.xml @@ -1,11 +1,4 @@ - - + date diff --git a/P5/Source/Specs/dateline.xml b/P5/Source/Specs/dateline.xml index 4c6fe76e63..7024c733a2 100644 --- a/P5/Source/Specs/dateline.xml +++ b/P5/Source/Specs/dateline.xml @@ -1,11 +1,4 @@ - - + dateline diff --git a/P5/Source/Specs/death.xml b/P5/Source/Specs/death.xml index d24250d3ed..2eea349840 100644 --- a/P5/Source/Specs/death.xml +++ b/P5/Source/Specs/death.xml @@ -1,10 +1,4 @@ - + death décès contains information about a person's death, such as its date and place. diff --git a/P5/Source/Specs/decoDesc.xml b/P5/Source/Specs/decoDesc.xml index e2a52e9c07..ff67a4a0dd 100644 --- a/P5/Source/Specs/decoDesc.xml +++ b/P5/Source/Specs/decoDesc.xml @@ -1,11 +1,4 @@ - - + decoration description diff --git a/P5/Source/Specs/decoNote.xml b/P5/Source/Specs/decoNote.xml index 6c95ba57f4..0b1670c677 100644 --- a/P5/Source/Specs/decoNote.xml +++ b/P5/Source/Specs/decoNote.xml @@ -1,11 +1,4 @@ - - + note on decoration diff --git a/P5/Source/Specs/def.xml b/P5/Source/Specs/def.xml index f7151abe78..bc45f93afe 100644 --- a/P5/Source/Specs/def.xml +++ b/P5/Source/Specs/def.xml @@ -1,11 +1,4 @@ - - + definition diff --git a/P5/Source/Specs/default.xml b/P5/Source/Specs/default.xml index 1e149c388d..2abea157b0 100644 --- a/P5/Source/Specs/default.xml +++ b/P5/Source/Specs/default.xml @@ -1,11 +1,4 @@ - - + default feature value diff --git a/P5/Source/Specs/defaultVal.xml b/P5/Source/Specs/defaultVal.xml index aafe69f4b5..5d7aa6381b 100644 --- a/P5/Source/Specs/defaultVal.xml +++ b/P5/Source/Specs/defaultVal.xml @@ -1,11 +1,4 @@ - - + default value diff --git a/P5/Source/Specs/del.xml b/P5/Source/Specs/del.xml index 1f04fabb6a..921f09ece1 100644 --- a/P5/Source/Specs/del.xml +++ b/P5/Source/Specs/del.xml @@ -1,11 +1,4 @@ - - + deletion diff --git a/P5/Source/Specs/delSpan.xml b/P5/Source/Specs/delSpan.xml index 9f1a06edb9..bb11e0a97e 100644 --- a/P5/Source/Specs/delSpan.xml +++ b/P5/Source/Specs/delSpan.xml @@ -1,11 +1,4 @@ - - + deleted span of text diff --git a/P5/Source/Specs/depth.xml b/P5/Source/Specs/depth.xml index e4a8171c38..d127fc9cfb 100644 --- a/P5/Source/Specs/depth.xml +++ b/P5/Source/Specs/depth.xml @@ -1,11 +1,4 @@ - - + depth diff --git a/P5/Source/Specs/derivation.xml b/P5/Source/Specs/derivation.xml index 2d23c625ee..1f060134da 100644 --- a/P5/Source/Specs/derivation.xml +++ b/P5/Source/Specs/derivation.xml @@ -1,11 +1,4 @@ - - + derivation diff --git a/P5/Source/Specs/desc.xml b/P5/Source/Specs/desc.xml index 463485e6b4..b83b04119f 100644 --- a/P5/Source/Specs/desc.xml +++ b/P5/Source/Specs/desc.xml @@ -1,11 +1,4 @@ - - + description diff --git a/P5/Source/Specs/dictScrap.xml b/P5/Source/Specs/dictScrap.xml index c4174b6283..035e180c62 100644 --- a/P5/Source/Specs/dictScrap.xml +++ b/P5/Source/Specs/dictScrap.xml @@ -1,11 +1,4 @@ - - + dictionary scrap diff --git a/P5/Source/Specs/dim.xml b/P5/Source/Specs/dim.xml index e4238bc1af..3b7b15c68b 100644 --- a/P5/Source/Specs/dim.xml +++ b/P5/Source/Specs/dim.xml @@ -1,11 +1,4 @@ - - + contains any single measurement forming part of a dimensional diff --git a/P5/Source/Specs/dimensions.xml b/P5/Source/Specs/dimensions.xml index 593b18cc3a..af40664086 100644 --- a/P5/Source/Specs/dimensions.xml +++ b/P5/Source/Specs/dimensions.xml @@ -1,11 +1,4 @@ - - + dimensions diff --git a/P5/Source/Specs/distinct.xml b/P5/Source/Specs/distinct.xml index 92d02f8f3c..8b4a38ebac 100644 --- a/P5/Source/Specs/distinct.xml +++ b/P5/Source/Specs/distinct.xml @@ -1,11 +1,4 @@ - - + identifies any word or phrase which is regarded as linguistically distinct, for example as diff --git a/P5/Source/Specs/distributor.xml b/P5/Source/Specs/distributor.xml index 9b134e6914..0f6497090b 100644 --- a/P5/Source/Specs/distributor.xml +++ b/P5/Source/Specs/distributor.xml @@ -1,11 +1,4 @@ - - + distributor diff --git a/P5/Source/Specs/district.xml b/P5/Source/Specs/district.xml index cc2b2aa76d..d4a370db59 100644 --- a/P5/Source/Specs/district.xml +++ b/P5/Source/Specs/district.xml @@ -1,10 +1,4 @@ - + district district contains the name of any kind of subdivision of a settlement, such as a parish, ward, or other administrative or geographic unit. diff --git a/P5/Source/Specs/div.xml b/P5/Source/Specs/div.xml index 7422d13557..368d51c391 100644 --- a/P5/Source/Specs/div.xml +++ b/P5/Source/Specs/div.xml @@ -1,11 +1,4 @@ - - + text division diff --git a/P5/Source/Specs/div1.xml b/P5/Source/Specs/div1.xml index f5db865235..1ed1c0d817 100644 --- a/P5/Source/Specs/div1.xml +++ b/P5/Source/Specs/div1.xml @@ -1,11 +1,4 @@ - - + level-1 text division diff --git a/P5/Source/Specs/div2.xml b/P5/Source/Specs/div2.xml index e9b1bef023..b569201c71 100644 --- a/P5/Source/Specs/div2.xml +++ b/P5/Source/Specs/div2.xml @@ -1,11 +1,4 @@ - - + level-2 text division diff --git a/P5/Source/Specs/div3.xml b/P5/Source/Specs/div3.xml index 3d1dbf0fbc..38126a40fd 100644 --- a/P5/Source/Specs/div3.xml +++ b/P5/Source/Specs/div3.xml @@ -1,11 +1,4 @@ - - + level-3 text division diff --git a/P5/Source/Specs/div4.xml b/P5/Source/Specs/div4.xml index a36839d6b7..00e3a63e16 100644 --- a/P5/Source/Specs/div4.xml +++ b/P5/Source/Specs/div4.xml @@ -1,11 +1,4 @@ - - + level-4 text division diff --git a/P5/Source/Specs/div5.xml b/P5/Source/Specs/div5.xml index 578b7b5840..98ffb36330 100644 --- a/P5/Source/Specs/div5.xml +++ b/P5/Source/Specs/div5.xml @@ -1,11 +1,4 @@ - - + level-5 text division diff --git a/P5/Source/Specs/div6.xml b/P5/Source/Specs/div6.xml index c64d65ff3a..effa7143f1 100644 --- a/P5/Source/Specs/div6.xml +++ b/P5/Source/Specs/div6.xml @@ -1,11 +1,4 @@ - - + level-6 text division diff --git a/P5/Source/Specs/div7.xml b/P5/Source/Specs/div7.xml index b680a248b5..76cd431222 100644 --- a/P5/Source/Specs/div7.xml +++ b/P5/Source/Specs/div7.xml @@ -1,11 +1,4 @@ - - + level-7 text division diff --git a/P5/Source/Specs/divGen.xml b/P5/Source/Specs/divGen.xml index 20fe47f1b8..f0fc89a123 100644 --- a/P5/Source/Specs/divGen.xml +++ b/P5/Source/Specs/divGen.xml @@ -1,11 +1,4 @@ - - + automatically generated text division diff --git a/P5/Source/Specs/docAuthor.xml b/P5/Source/Specs/docAuthor.xml index a7572502c3..974f175a18 100644 --- a/P5/Source/Specs/docAuthor.xml +++ b/P5/Source/Specs/docAuthor.xml @@ -1,11 +1,4 @@ - - + document author diff --git a/P5/Source/Specs/docDate.xml b/P5/Source/Specs/docDate.xml index 4d1ac7b53f..a1762ddae6 100644 --- a/P5/Source/Specs/docDate.xml +++ b/P5/Source/Specs/docDate.xml @@ -1,11 +1,4 @@ - - + document date diff --git a/P5/Source/Specs/docEdition.xml b/P5/Source/Specs/docEdition.xml index c9fdbfed02..f7b516b48b 100644 --- a/P5/Source/Specs/docEdition.xml +++ b/P5/Source/Specs/docEdition.xml @@ -1,11 +1,4 @@ - - + document edition diff --git a/P5/Source/Specs/docImprint.xml b/P5/Source/Specs/docImprint.xml index 4bdb5a9da0..2a7e5ffbb6 100644 --- a/P5/Source/Specs/docImprint.xml +++ b/P5/Source/Specs/docImprint.xml @@ -1,11 +1,4 @@ - - + document imprint diff --git a/P5/Source/Specs/docTitle.xml b/P5/Source/Specs/docTitle.xml index 58420939ce..4ba9ff0707 100644 --- a/P5/Source/Specs/docTitle.xml +++ b/P5/Source/Specs/docTitle.xml @@ -1,11 +1,4 @@ - - + document title diff --git a/P5/Source/Specs/domain.xml b/P5/Source/Specs/domain.xml index 71a1d86fe6..36de7e0537 100644 --- a/P5/Source/Specs/domain.xml +++ b/P5/Source/Specs/domain.xml @@ -1,11 +1,4 @@ - - + domain of use diff --git a/P5/Source/Specs/eLeaf.xml b/P5/Source/Specs/eLeaf.xml index c2c5fbaf04..dd2ababbb9 100644 --- a/P5/Source/Specs/eLeaf.xml +++ b/P5/Source/Specs/eLeaf.xml @@ -1,11 +1,4 @@ - - + leaf or terminal node of an embedding tree diff --git a/P5/Source/Specs/eTree.xml b/P5/Source/Specs/eTree.xml index 1fdf34fe96..2db1826f14 100644 --- a/P5/Source/Specs/eTree.xml +++ b/P5/Source/Specs/eTree.xml @@ -1,11 +1,4 @@ - - + embedding tree diff --git a/P5/Source/Specs/edition.xml b/P5/Source/Specs/edition.xml index 7e8cbed118..ad9ef780be 100644 --- a/P5/Source/Specs/edition.xml +++ b/P5/Source/Specs/edition.xml @@ -1,11 +1,4 @@ - - + edition diff --git a/P5/Source/Specs/editionStmt.xml b/P5/Source/Specs/editionStmt.xml index 4620c6c305..e77529a1c5 100644 --- a/P5/Source/Specs/editionStmt.xml +++ b/P5/Source/Specs/editionStmt.xml @@ -1,11 +1,4 @@ - - + edition statement diff --git a/P5/Source/Specs/editor.xml b/P5/Source/Specs/editor.xml index d566c65068..a7b4b07ec9 100644 --- a/P5/Source/Specs/editor.xml +++ b/P5/Source/Specs/editor.xml @@ -1,10 +1,4 @@ - + contains a secondary statement of responsibility for a bibliographic item, for example the name of an individual, institution or organization, (or of several such) acting as editor, compiler, diff --git a/P5/Source/Specs/editorialDecl.xml b/P5/Source/Specs/editorialDecl.xml index 50f39b8eb9..ef6caf312b 100644 --- a/P5/Source/Specs/editorialDecl.xml +++ b/P5/Source/Specs/editorialDecl.xml @@ -1,11 +1,4 @@ - - + editorial practice declaration diff --git a/P5/Source/Specs/education.xml b/P5/Source/Specs/education.xml index 7f33e3e6d6..49f0f7bd33 100644 --- a/P5/Source/Specs/education.xml +++ b/P5/Source/Specs/education.xml @@ -1,10 +1,4 @@ - + education éducation contains a description of the educational experience of a person. diff --git a/P5/Source/Specs/eg.xml b/P5/Source/Specs/eg.xml index 18f8406df5..a866fb5d9d 100644 --- a/P5/Source/Specs/eg.xml +++ b/P5/Source/Specs/eg.xml @@ -1,11 +1,4 @@ - - + example diff --git a/P5/Source/Specs/egXML.xml b/P5/Source/Specs/egXML.xml index 4839ff6a0a..e0889cfd6c 100644 --- a/P5/Source/Specs/egXML.xml +++ b/P5/Source/Specs/egXML.xml @@ -1,11 +1,4 @@ - - + example of XML diff --git a/P5/Source/Specs/elementRef.xml b/P5/Source/Specs/elementRef.xml index 5dcc969eff..ee3077650b 100644 --- a/P5/Source/Specs/elementRef.xml +++ b/P5/Source/Specs/elementRef.xml @@ -1,11 +1,4 @@ - - + points to the specification for some element which is to be included in a schema diff --git a/P5/Source/Specs/elementSpec.xml b/P5/Source/Specs/elementSpec.xml index 5602119338..0c065a5d4f 100644 --- a/P5/Source/Specs/elementSpec.xml +++ b/P5/Source/Specs/elementSpec.xml @@ -1,11 +1,4 @@ - - + element specification diff --git a/P5/Source/Specs/ellipsis.xml b/P5/Source/Specs/ellipsis.xml index 41fd5f921d..f9e8e31dfb 100644 --- a/P5/Source/Specs/ellipsis.xml +++ b/P5/Source/Specs/ellipsis.xml @@ -1,11 +1,4 @@ - - + deliberately marked omission diff --git a/P5/Source/Specs/email.xml b/P5/Source/Specs/email.xml index d178f73fb2..75c9d9058d 100644 --- a/P5/Source/Specs/email.xml +++ b/P5/Source/Specs/email.xml @@ -1,11 +1,4 @@ - - + electronic mail address diff --git a/P5/Source/Specs/emph.xml b/P5/Source/Specs/emph.xml index 8eda527511..22a625864e 100644 --- a/P5/Source/Specs/emph.xml +++ b/P5/Source/Specs/emph.xml @@ -1,11 +1,4 @@ - - + emphasized diff --git a/P5/Source/Specs/empty.xml b/P5/Source/Specs/empty.xml index 466c44b5eb..daccd52c84 100644 --- a/P5/Source/Specs/empty.xml +++ b/P5/Source/Specs/empty.xml @@ -1,11 +1,4 @@ - - + indicates the presence of an empty node within a diff --git a/P5/Source/Specs/encodingDesc.xml b/P5/Source/Specs/encodingDesc.xml index 59e4007d1e..5f393b68a9 100644 --- a/P5/Source/Specs/encodingDesc.xml +++ b/P5/Source/Specs/encodingDesc.xml @@ -1,11 +1,4 @@ - - + encoding description diff --git a/P5/Source/Specs/entry.xml b/P5/Source/Specs/entry.xml index 6f664581a1..c93b53d4c6 100644 --- a/P5/Source/Specs/entry.xml +++ b/P5/Source/Specs/entry.xml @@ -1,11 +1,4 @@ - - + entry diff --git a/P5/Source/Specs/entryFree.xml b/P5/Source/Specs/entryFree.xml index e4350e10dd..93613ffa7c 100644 --- a/P5/Source/Specs/entryFree.xml +++ b/P5/Source/Specs/entryFree.xml @@ -1,11 +1,4 @@ - - + unstructured entry diff --git a/P5/Source/Specs/epigraph.xml b/P5/Source/Specs/epigraph.xml index 17e71d7bb8..0b9e75656f 100644 --- a/P5/Source/Specs/epigraph.xml +++ b/P5/Source/Specs/epigraph.xml @@ -1,11 +1,4 @@ - - + epigraph diff --git a/P5/Source/Specs/epilogue.xml b/P5/Source/Specs/epilogue.xml index d3b54436a4..6d8e6feeee 100644 --- a/P5/Source/Specs/epilogue.xml +++ b/P5/Source/Specs/epilogue.xml @@ -1,11 +1,4 @@ - - + epilogue diff --git a/P5/Source/Specs/equipment.xml b/P5/Source/Specs/equipment.xml index 297e6af725..dd63dbdd67 100644 --- a/P5/Source/Specs/equipment.xml +++ b/P5/Source/Specs/equipment.xml @@ -1,11 +1,4 @@ - - + equipment diff --git a/P5/Source/Specs/equiv.xml b/P5/Source/Specs/equiv.xml index dfebda007c..5109b7e769 100644 --- a/P5/Source/Specs/equiv.xml +++ b/P5/Source/Specs/equiv.xml @@ -1,11 +1,4 @@ - - + equivalent diff --git a/P5/Source/Specs/etym.xml b/P5/Source/Specs/etym.xml index b466558839..e4c5a9816b 100644 --- a/P5/Source/Specs/etym.xml +++ b/P5/Source/Specs/etym.xml @@ -1,11 +1,4 @@ - - + etymology diff --git a/P5/Source/Specs/event.xml b/P5/Source/Specs/event.xml index 1ba66f25c7..51979fb276 100644 --- a/P5/Source/Specs/event.xml +++ b/P5/Source/Specs/event.xml @@ -1,11 +1,4 @@ - - + event diff --git a/P5/Source/Specs/eventName.xml b/P5/Source/Specs/eventName.xml index ec724ecbc4..fd76bcc327 100644 --- a/P5/Source/Specs/eventName.xml +++ b/P5/Source/Specs/eventName.xml @@ -1,11 +1,4 @@ - - + name of an event diff --git a/P5/Source/Specs/ex.xml b/P5/Source/Specs/ex.xml index 7770328af1..fd9315b5d3 100644 --- a/P5/Source/Specs/ex.xml +++ b/P5/Source/Specs/ex.xml @@ -1,11 +1,4 @@ - - + editorial expansion diff --git a/P5/Source/Specs/exemplum.xml b/P5/Source/Specs/exemplum.xml index e731bac941..5bb19cb7d0 100644 --- a/P5/Source/Specs/exemplum.xml +++ b/P5/Source/Specs/exemplum.xml @@ -1,11 +1,4 @@ - - + exemplum diff --git a/P5/Source/Specs/expan.xml b/P5/Source/Specs/expan.xml index a577c7f5ba..4602e558e1 100644 --- a/P5/Source/Specs/expan.xml +++ b/P5/Source/Specs/expan.xml @@ -1,11 +1,4 @@ - - + expansion diff --git a/P5/Source/Specs/explicit.xml b/P5/Source/Specs/explicit.xml index 0ab2b0c78f..f04a365de5 100644 --- a/P5/Source/Specs/explicit.xml +++ b/P5/Source/Specs/explicit.xml @@ -1,11 +1,4 @@ - - + explicit diff --git a/P5/Source/Specs/extent.xml b/P5/Source/Specs/extent.xml index 5e6e23863b..af9ea8b811 100644 --- a/P5/Source/Specs/extent.xml +++ b/P5/Source/Specs/extent.xml @@ -1,11 +1,4 @@ - - + extent diff --git a/P5/Source/Specs/f.xml b/P5/Source/Specs/f.xml index dfa68ba832..fc21582245 100644 --- a/P5/Source/Specs/f.xml +++ b/P5/Source/Specs/f.xml @@ -1,11 +1,4 @@ - - + feature diff --git a/P5/Source/Specs/fDecl.xml b/P5/Source/Specs/fDecl.xml index 43fda19c43..d31d8ec638 100644 --- a/P5/Source/Specs/fDecl.xml +++ b/P5/Source/Specs/fDecl.xml @@ -1,11 +1,4 @@ - - + feature declaration diff --git a/P5/Source/Specs/fDescr.xml b/P5/Source/Specs/fDescr.xml index 4f63618dc6..0d24fff402 100644 --- a/P5/Source/Specs/fDescr.xml +++ b/P5/Source/Specs/fDescr.xml @@ -1,11 +1,4 @@ - - + feature description (in FSD) diff --git a/P5/Source/Specs/fLib.xml b/P5/Source/Specs/fLib.xml index 002bc93b9e..c2a9514f1f 100644 --- a/P5/Source/Specs/fLib.xml +++ b/P5/Source/Specs/fLib.xml @@ -1,11 +1,4 @@ - - + feature library diff --git a/P5/Source/Specs/facsimile.xml b/P5/Source/Specs/facsimile.xml index 9553f47c11..5adeacaa4e 100644 --- a/P5/Source/Specs/facsimile.xml +++ b/P5/Source/Specs/facsimile.xml @@ -1,11 +1,4 @@ - - + contains a representation of some written source in the form of diff --git a/P5/Source/Specs/factuality.xml b/P5/Source/Specs/factuality.xml index 526401d515..b505238511 100644 --- a/P5/Source/Specs/factuality.xml +++ b/P5/Source/Specs/factuality.xml @@ -1,11 +1,4 @@ - - + factuality diff --git a/P5/Source/Specs/faith.xml b/P5/Source/Specs/faith.xml index 502fa7c630..d6dc13905e 100644 --- a/P5/Source/Specs/faith.xml +++ b/P5/Source/Specs/faith.xml @@ -1,10 +1,4 @@ - + faith religion specifies the faith, religion, or belief set of a person. diff --git a/P5/Source/Specs/figDesc.xml b/P5/Source/Specs/figDesc.xml index 9b254f4eae..ff42825bc6 100644 --- a/P5/Source/Specs/figDesc.xml +++ b/P5/Source/Specs/figDesc.xml @@ -1,11 +1,4 @@ - - + description of figure diff --git a/P5/Source/Specs/figure.xml b/P5/Source/Specs/figure.xml index 611d941705..bba891c05e 100644 --- a/P5/Source/Specs/figure.xml +++ b/P5/Source/Specs/figure.xml @@ -1,11 +1,4 @@ - - + figure diff --git a/P5/Source/Specs/fileDesc.xml b/P5/Source/Specs/fileDesc.xml index 3ebf7bfb01..71817e08fa 100644 --- a/P5/Source/Specs/fileDesc.xml +++ b/P5/Source/Specs/fileDesc.xml @@ -1,11 +1,4 @@ - - + file description diff --git a/P5/Source/Specs/filiation.xml b/P5/Source/Specs/filiation.xml index a0bfe39e75..8d34706eac 100644 --- a/P5/Source/Specs/filiation.xml +++ b/P5/Source/Specs/filiation.xml @@ -1,11 +1,4 @@ - - + filiation diff --git a/P5/Source/Specs/finalRubric.xml b/P5/Source/Specs/finalRubric.xml index 92e7129406..4698e6e34e 100644 --- a/P5/Source/Specs/finalRubric.xml +++ b/P5/Source/Specs/finalRubric.xml @@ -1,11 +1,4 @@ - - + final rubric diff --git a/P5/Source/Specs/floatingText.xml b/P5/Source/Specs/floatingText.xml index 762aacc90d..b54546da6d 100644 --- a/P5/Source/Specs/floatingText.xml +++ b/P5/Source/Specs/floatingText.xml @@ -1,11 +1,4 @@ - - + floating text diff --git a/P5/Source/Specs/floruit.xml b/P5/Source/Specs/floruit.xml index a9da6728e2..5f01cb680d 100644 --- a/P5/Source/Specs/floruit.xml +++ b/P5/Source/Specs/floruit.xml @@ -1,10 +1,4 @@ - + floruit période d'activité contains information about a person's period of activity. diff --git a/P5/Source/Specs/foliation.xml b/P5/Source/Specs/foliation.xml index 1bc40b6a7e..f4ecf6e06e 100644 --- a/P5/Source/Specs/foliation.xml +++ b/P5/Source/Specs/foliation.xml @@ -1,11 +1,4 @@ - - + foliation diff --git a/P5/Source/Specs/foreign.xml b/P5/Source/Specs/foreign.xml index b8c03c75c9..9eeb2fd526 100644 --- a/P5/Source/Specs/foreign.xml +++ b/P5/Source/Specs/foreign.xml @@ -1,11 +1,4 @@ - - + foreign diff --git a/P5/Source/Specs/forename.xml b/P5/Source/Specs/forename.xml index 2f3890d79e..9b24e9ace0 100644 --- a/P5/Source/Specs/forename.xml +++ b/P5/Source/Specs/forename.xml @@ -1,11 +1,4 @@ - - + forename diff --git a/P5/Source/Specs/forest.xml b/P5/Source/Specs/forest.xml index 0e606446f7..8b2855b64c 100644 --- a/P5/Source/Specs/forest.xml +++ b/P5/Source/Specs/forest.xml @@ -1,11 +1,4 @@ - - + forest diff --git a/P5/Source/Specs/form.xml b/P5/Source/Specs/form.xml index 03d417cbf9..d52cb803ab 100644 --- a/P5/Source/Specs/form.xml +++ b/P5/Source/Specs/form.xml @@ -1,11 +1,4 @@ - - + form information group diff --git a/P5/Source/Specs/formula.xml b/P5/Source/Specs/formula.xml index 480b5b60cd..00c871f755 100644 --- a/P5/Source/Specs/formula.xml +++ b/P5/Source/Specs/formula.xml @@ -1,11 +1,4 @@ - - + formula diff --git a/P5/Source/Specs/front.xml b/P5/Source/Specs/front.xml index 99dd015b78..06bef4f50e 100644 --- a/P5/Source/Specs/front.xml +++ b/P5/Source/Specs/front.xml @@ -1,11 +1,4 @@ - - + front matter diff --git a/P5/Source/Specs/fs.xml b/P5/Source/Specs/fs.xml index c400ef40ca..c62b4e84fb 100644 --- a/P5/Source/Specs/fs.xml +++ b/P5/Source/Specs/fs.xml @@ -1,11 +1,4 @@ - - + feature structure diff --git a/P5/Source/Specs/fsConstraints.xml b/P5/Source/Specs/fsConstraints.xml index 7d59163590..1062e69845 100644 --- a/P5/Source/Specs/fsConstraints.xml +++ b/P5/Source/Specs/fsConstraints.xml @@ -1,11 +1,4 @@ - - + feature-structure constraints diff --git a/P5/Source/Specs/fsDecl.xml b/P5/Source/Specs/fsDecl.xml index 3122c8d764..13ce5aacb5 100644 --- a/P5/Source/Specs/fsDecl.xml +++ b/P5/Source/Specs/fsDecl.xml @@ -1,11 +1,4 @@ - - + feature structure declaration diff --git a/P5/Source/Specs/fsDescr.xml b/P5/Source/Specs/fsDescr.xml index 0b5ae895a7..3906c7054a 100644 --- a/P5/Source/Specs/fsDescr.xml +++ b/P5/Source/Specs/fsDescr.xml @@ -1,11 +1,4 @@ - - + feature system description (in FSD) diff --git a/P5/Source/Specs/fsdDecl.xml b/P5/Source/Specs/fsdDecl.xml index 6d4f0faf3f..96cd1f1bbd 100644 --- a/P5/Source/Specs/fsdDecl.xml +++ b/P5/Source/Specs/fsdDecl.xml @@ -1,11 +1,4 @@ - - + feature system declaration diff --git a/P5/Source/Specs/fsdLink.xml b/P5/Source/Specs/fsdLink.xml index dd41ca6b1b..0d13671f7f 100644 --- a/P5/Source/Specs/fsdLink.xml +++ b/P5/Source/Specs/fsdLink.xml @@ -1,11 +1,4 @@ - - + feature structure declaration link diff --git a/P5/Source/Specs/funder.xml b/P5/Source/Specs/funder.xml index bbeb4e49a1..ced649f52f 100644 --- a/P5/Source/Specs/funder.xml +++ b/P5/Source/Specs/funder.xml @@ -1,10 +1,4 @@ - + funding body financeur 재정 지원 조직체 diff --git a/P5/Source/Specs/fvLib.xml b/P5/Source/Specs/fvLib.xml index 71667c1ca2..3003d9959d 100644 --- a/P5/Source/Specs/fvLib.xml +++ b/P5/Source/Specs/fvLib.xml @@ -1,11 +1,4 @@ - - + feature-value library diff --git a/P5/Source/Specs/fw.xml b/P5/Source/Specs/fw.xml index 5587342946..e0689bf233 100644 --- a/P5/Source/Specs/fw.xml +++ b/P5/Source/Specs/fw.xml @@ -1,11 +1,4 @@ - - + forme work diff --git a/P5/Source/Specs/g.xml b/P5/Source/Specs/g.xml index c3f89ff89f..b7ee6383f2 100644 --- a/P5/Source/Specs/g.xml +++ b/P5/Source/Specs/g.xml @@ -1,11 +1,4 @@ - - + character or glyph diff --git a/P5/Source/Specs/gap.xml b/P5/Source/Specs/gap.xml index 0596868f14..ef715fd3c7 100644 --- a/P5/Source/Specs/gap.xml +++ b/P5/Source/Specs/gap.xml @@ -1,11 +1,4 @@ - - + diff --git a/P5/Source/Specs/gb.xml b/P5/Source/Specs/gb.xml index 28b2b2e15e..44b80bc33b 100644 --- a/P5/Source/Specs/gb.xml +++ b/P5/Source/Specs/gb.xml @@ -1,11 +1,4 @@ - - + gathering beginning diff --git a/P5/Source/Specs/gen.xml b/P5/Source/Specs/gen.xml index 51fd950c97..f3a197c8ae 100644 --- a/P5/Source/Specs/gen.xml +++ b/P5/Source/Specs/gen.xml @@ -1,11 +1,4 @@ - - + diff --git a/P5/Source/Specs/genName.xml b/P5/Source/Specs/genName.xml index a36482ec9b..84552c75ff 100644 --- a/P5/Source/Specs/genName.xml +++ b/P5/Source/Specs/genName.xml @@ -1,11 +1,4 @@ - - + generational name component diff --git a/P5/Source/Specs/gender.xml b/P5/Source/Specs/gender.xml index b7776cdc2f..a33ae2075a 100644 --- a/P5/Source/Specs/gender.xml +++ b/P5/Source/Specs/gender.xml @@ -1,10 +1,4 @@ - + gender specifies the gender identity of a person, persona, or character. especifica la identidad de género de una persona. diff --git a/P5/Source/Specs/geo.xml b/P5/Source/Specs/geo.xml index 020770a883..6b431e97aa 100644 --- a/P5/Source/Specs/geo.xml +++ b/P5/Source/Specs/geo.xml @@ -1,11 +1,4 @@ - - + geographical coordinates diff --git a/P5/Source/Specs/geoDecl.xml b/P5/Source/Specs/geoDecl.xml index 44c2d7271d..f15b783c8a 100644 --- a/P5/Source/Specs/geoDecl.xml +++ b/P5/Source/Specs/geoDecl.xml @@ -1,11 +1,4 @@ - - + geographic coordinates declaration diff --git a/P5/Source/Specs/geogFeat.xml b/P5/Source/Specs/geogFeat.xml index a5017b24c6..29be061dfa 100644 --- a/P5/Source/Specs/geogFeat.xml +++ b/P5/Source/Specs/geogFeat.xml @@ -1,10 +1,4 @@ - + geographical feature name 지리적 특성명 nom de caractéristique géographique diff --git a/P5/Source/Specs/geogName.xml b/P5/Source/Specs/geogName.xml index ad00164f35..91eaf46f7a 100644 --- a/P5/Source/Specs/geogName.xml +++ b/P5/Source/Specs/geogName.xml @@ -1,10 +1,4 @@ - + geographical name 지리명 地理名稱 diff --git a/P5/Source/Specs/gi.xml b/P5/Source/Specs/gi.xml index 6c5e1c6cc6..1d603e90a7 100644 --- a/P5/Source/Specs/gi.xml +++ b/P5/Source/Specs/gi.xml @@ -1,11 +1,4 @@ - - + element name diff --git a/P5/Source/Specs/gloss.xml b/P5/Source/Specs/gloss.xml index 3f3ed9ff04..1248276ca9 100644 --- a/P5/Source/Specs/gloss.xml +++ b/P5/Source/Specs/gloss.xml @@ -1,11 +1,4 @@ - - + gloss diff --git a/P5/Source/Specs/glyph.xml b/P5/Source/Specs/glyph.xml index 42d557e141..d18376ccb8 100644 --- a/P5/Source/Specs/glyph.xml +++ b/P5/Source/Specs/glyph.xml @@ -1,11 +1,4 @@ - - + character glyph diff --git a/P5/Source/Specs/gram.xml b/P5/Source/Specs/gram.xml index 26c94b6f39..7c8216fdd8 100644 --- a/P5/Source/Specs/gram.xml +++ b/P5/Source/Specs/gram.xml @@ -1,11 +1,4 @@ - - + grammatical information diff --git a/P5/Source/Specs/gramGrp.xml b/P5/Source/Specs/gramGrp.xml index 6cd4b2cfce..a32f855a22 100644 --- a/P5/Source/Specs/gramGrp.xml +++ b/P5/Source/Specs/gramGrp.xml @@ -1,11 +1,4 @@ - - + grammatical information group diff --git a/P5/Source/Specs/graph.xml b/P5/Source/Specs/graph.xml index 1796150607..ae8a2e5352 100644 --- a/P5/Source/Specs/graph.xml +++ b/P5/Source/Specs/graph.xml @@ -1,11 +1,4 @@ - - + graph diff --git a/P5/Source/Specs/graphic.xml b/P5/Source/Specs/graphic.xml index 60478ce72a..785dedf488 100644 --- a/P5/Source/Specs/graphic.xml +++ b/P5/Source/Specs/graphic.xml @@ -1,11 +1,4 @@ - - + graphic diff --git a/P5/Source/Specs/group.xml b/P5/Source/Specs/group.xml index 39460b164d..250606b879 100644 --- a/P5/Source/Specs/group.xml +++ b/P5/Source/Specs/group.xml @@ -1,11 +1,4 @@ - - + group diff --git a/P5/Source/Specs/handDesc.xml b/P5/Source/Specs/handDesc.xml index 43ba1a31d1..9c334f76ec 100644 --- a/P5/Source/Specs/handDesc.xml +++ b/P5/Source/Specs/handDesc.xml @@ -1,11 +1,4 @@ - - + description of hands diff --git a/P5/Source/Specs/handNote.xml b/P5/Source/Specs/handNote.xml index 9dcac2b1ef..fb50a57c50 100644 --- a/P5/Source/Specs/handNote.xml +++ b/P5/Source/Specs/handNote.xml @@ -1,11 +1,4 @@ - - + note on hand diff --git a/P5/Source/Specs/handNotes.xml b/P5/Source/Specs/handNotes.xml index 3e1472bdf2..0d9bb6fd17 100644 --- a/P5/Source/Specs/handNotes.xml +++ b/P5/Source/Specs/handNotes.xml @@ -1,11 +1,4 @@ - - + contains one or more handNote elements documenting the diff --git a/P5/Source/Specs/handShift.xml b/P5/Source/Specs/handShift.xml index 3823607363..d9db2cf54e 100644 --- a/P5/Source/Specs/handShift.xml +++ b/P5/Source/Specs/handShift.xml @@ -1,11 +1,4 @@ - - + handwriting shift diff --git a/P5/Source/Specs/head.xml b/P5/Source/Specs/head.xml index c998baf736..82593026ba 100644 --- a/P5/Source/Specs/head.xml +++ b/P5/Source/Specs/head.xml @@ -1,11 +1,4 @@ - - + heading diff --git a/P5/Source/Specs/headItem.xml b/P5/Source/Specs/headItem.xml index e71a4e3faa..ee23a7f20f 100644 --- a/P5/Source/Specs/headItem.xml +++ b/P5/Source/Specs/headItem.xml @@ -1,11 +1,4 @@ - - + heading for list items diff --git a/P5/Source/Specs/headLabel.xml b/P5/Source/Specs/headLabel.xml index 8f64d38f9c..2aab40ad81 100644 --- a/P5/Source/Specs/headLabel.xml +++ b/P5/Source/Specs/headLabel.xml @@ -1,11 +1,4 @@ - - + heading for list labels diff --git a/P5/Source/Specs/height.xml b/P5/Source/Specs/height.xml index 9157f1b300..7b0519755f 100644 --- a/P5/Source/Specs/height.xml +++ b/P5/Source/Specs/height.xml @@ -1,11 +1,4 @@ - - + height diff --git a/P5/Source/Specs/heraldry.xml b/P5/Source/Specs/heraldry.xml index 0a0bc60726..816133e3fe 100644 --- a/P5/Source/Specs/heraldry.xml +++ b/P5/Source/Specs/heraldry.xml @@ -1,11 +1,4 @@ - - + heraldry diff --git a/P5/Source/Specs/hi.xml b/P5/Source/Specs/hi.xml index fb7e610b77..27538b990a 100644 --- a/P5/Source/Specs/hi.xml +++ b/P5/Source/Specs/hi.xml @@ -1,11 +1,4 @@ - - + highlighted diff --git a/P5/Source/Specs/history.xml b/P5/Source/Specs/history.xml index 201e15ab9a..372b9160fe 100644 --- a/P5/Source/Specs/history.xml +++ b/P5/Source/Specs/history.xml @@ -1,11 +1,4 @@ - - + history diff --git a/P5/Source/Specs/hom.xml b/P5/Source/Specs/hom.xml index cf36c621d0..e0708cec05 100644 --- a/P5/Source/Specs/hom.xml +++ b/P5/Source/Specs/hom.xml @@ -1,11 +1,4 @@ - - + homograph diff --git a/P5/Source/Specs/hyph.xml b/P5/Source/Specs/hyph.xml index 1bb7a1271d..ac45dd7e88 100644 --- a/P5/Source/Specs/hyph.xml +++ b/P5/Source/Specs/hyph.xml @@ -1,11 +1,4 @@ - - + hyphenation diff --git a/P5/Source/Specs/hyphenation.xml b/P5/Source/Specs/hyphenation.xml index d8f60b32ed..02c8821df3 100644 --- a/P5/Source/Specs/hyphenation.xml +++ b/P5/Source/Specs/hyphenation.xml @@ -1,11 +1,4 @@ - - + hyphenation diff --git a/P5/Source/Specs/iNode.xml b/P5/Source/Specs/iNode.xml index 5ce7826716..0c1fdfa15d 100644 --- a/P5/Source/Specs/iNode.xml +++ b/P5/Source/Specs/iNode.xml @@ -1,11 +1,4 @@ - - + intermediate (or internal) node diff --git a/P5/Source/Specs/iType.xml b/P5/Source/Specs/iType.xml index 25eb21c12e..2c1491ea85 100644 --- a/P5/Source/Specs/iType.xml +++ b/P5/Source/Specs/iType.xml @@ -1,11 +1,4 @@ - - + inflectional class diff --git a/P5/Source/Specs/ident.xml b/P5/Source/Specs/ident.xml index c8142e1eb4..e619eb3e00 100644 --- a/P5/Source/Specs/ident.xml +++ b/P5/Source/Specs/ident.xml @@ -1,11 +1,4 @@ - - + identifier diff --git a/P5/Source/Specs/idno.xml b/P5/Source/Specs/idno.xml index b378edb436..3945300712 100644 --- a/P5/Source/Specs/idno.xml +++ b/P5/Source/Specs/idno.xml @@ -1,10 +1,4 @@ - + identifier identifiant 식별 숫자 diff --git a/P5/Source/Specs/if.xml b/P5/Source/Specs/if.xml index c5bf214b26..6e32083c09 100644 --- a/P5/Source/Specs/if.xml +++ b/P5/Source/Specs/if.xml @@ -1,11 +1,4 @@ - - + defines a conditional default value for a feature; the condition diff --git a/P5/Source/Specs/iff.xml b/P5/Source/Specs/iff.xml index bd4df70435..0a506718cc 100644 --- a/P5/Source/Specs/iff.xml +++ b/P5/Source/Specs/iff.xml @@ -1,11 +1,4 @@ - - + if and only if diff --git a/P5/Source/Specs/imprimatur.xml b/P5/Source/Specs/imprimatur.xml index a4ba223e22..5abd8d91eb 100644 --- a/P5/Source/Specs/imprimatur.xml +++ b/P5/Source/Specs/imprimatur.xml @@ -1,11 +1,4 @@ - - + imprimatur diff --git a/P5/Source/Specs/imprint.xml b/P5/Source/Specs/imprint.xml index aa538c8c53..a61b0d1fa8 100644 --- a/P5/Source/Specs/imprint.xml +++ b/P5/Source/Specs/imprint.xml @@ -1,11 +1,4 @@ - - + diff --git a/P5/Source/Specs/incident.xml b/P5/Source/Specs/incident.xml index b42f195967..c7c434419d 100644 --- a/P5/Source/Specs/incident.xml +++ b/P5/Source/Specs/incident.xml @@ -1,11 +1,4 @@ - - + incident diff --git a/P5/Source/Specs/incipit.xml b/P5/Source/Specs/incipit.xml index 7cf7ee5d59..24b7f3ac16 100644 --- a/P5/Source/Specs/incipit.xml +++ b/P5/Source/Specs/incipit.xml @@ -1,11 +1,4 @@ - - + contains the incipit of a manuscript or similar object item, that is the opening words of the text proper, exclusive of any rubric which might precede it, of sufficient length to identify the work uniquely; such incipits were, in former times, frequently used a means of reference to a work, in place of a title. diff --git a/P5/Source/Specs/index.xml b/P5/Source/Specs/index.xml index db994f01f5..34d581418e 100644 --- a/P5/Source/Specs/index.xml +++ b/P5/Source/Specs/index.xml @@ -1,11 +1,4 @@ - - + index entry diff --git a/P5/Source/Specs/institution.xml b/P5/Source/Specs/institution.xml index 03d07c38ab..b40c2ca634 100644 --- a/P5/Source/Specs/institution.xml +++ b/P5/Source/Specs/institution.xml @@ -1,11 +1,4 @@ - - + institution diff --git a/P5/Source/Specs/interaction.xml b/P5/Source/Specs/interaction.xml index 2e6b53e5bc..7754feb09a 100644 --- a/P5/Source/Specs/interaction.xml +++ b/P5/Source/Specs/interaction.xml @@ -1,11 +1,4 @@ - - + interaction diff --git a/P5/Source/Specs/interp.xml b/P5/Source/Specs/interp.xml index 2578c86534..f7e47b68fa 100644 --- a/P5/Source/Specs/interp.xml +++ b/P5/Source/Specs/interp.xml @@ -1,11 +1,4 @@ - - + interpretation diff --git a/P5/Source/Specs/interpGrp.xml b/P5/Source/Specs/interpGrp.xml index e747bb8a68..9b0b5cce97 100644 --- a/P5/Source/Specs/interpGrp.xml +++ b/P5/Source/Specs/interpGrp.xml @@ -1,11 +1,4 @@ - - + interpretation group diff --git a/P5/Source/Specs/interpretation.xml b/P5/Source/Specs/interpretation.xml index d9923ea2e1..76fb98af6e 100644 --- a/P5/Source/Specs/interpretation.xml +++ b/P5/Source/Specs/interpretation.xml @@ -1,11 +1,4 @@ - - + interpretation diff --git a/P5/Source/Specs/item.xml b/P5/Source/Specs/item.xml index a06d37d241..633fec8101 100644 --- a/P5/Source/Specs/item.xml +++ b/P5/Source/Specs/item.xml @@ -1,11 +1,4 @@ - - + item diff --git a/P5/Source/Specs/join.xml b/P5/Source/Specs/join.xml index 3bb10bfcb7..676e232121 100644 --- a/P5/Source/Specs/join.xml +++ b/P5/Source/Specs/join.xml @@ -1,5 +1,4 @@ - - + join diff --git a/P5/Source/Specs/joinGrp.xml b/P5/Source/Specs/joinGrp.xml index 56d0084095..78ec57a710 100644 --- a/P5/Source/Specs/joinGrp.xml +++ b/P5/Source/Specs/joinGrp.xml @@ -1,5 +1,4 @@ - - + join group diff --git a/P5/Source/Specs/keywords.xml b/P5/Source/Specs/keywords.xml index f3d9f61080..3f6b7a752e 100644 --- a/P5/Source/Specs/keywords.xml +++ b/P5/Source/Specs/keywords.xml @@ -1,11 +1,4 @@ - - + keywords diff --git a/P5/Source/Specs/kinesic.xml b/P5/Source/Specs/kinesic.xml index 15db325a14..ca3627b025 100644 --- a/P5/Source/Specs/kinesic.xml +++ b/P5/Source/Specs/kinesic.xml @@ -1,11 +1,4 @@ - - + kinesic diff --git a/P5/Source/Specs/l.xml b/P5/Source/Specs/l.xml index 906375ab08..c8658bb7ff 100644 --- a/P5/Source/Specs/l.xml +++ b/P5/Source/Specs/l.xml @@ -1,11 +1,4 @@ - - + verse line diff --git a/P5/Source/Specs/label.xml b/P5/Source/Specs/label.xml index 355552ca4c..46803c5e47 100644 --- a/P5/Source/Specs/label.xml +++ b/P5/Source/Specs/label.xml @@ -1,11 +1,4 @@ - - + label diff --git a/P5/Source/Specs/lacunaEnd.xml b/P5/Source/Specs/lacunaEnd.xml index eb0c6f250c..03e6b06fee 100644 --- a/P5/Source/Specs/lacunaEnd.xml +++ b/P5/Source/Specs/lacunaEnd.xml @@ -1,11 +1,4 @@ - - + lacuna end diff --git a/P5/Source/Specs/lacunaStart.xml b/P5/Source/Specs/lacunaStart.xml index ab2524033c..60c7eb588a 100644 --- a/P5/Source/Specs/lacunaStart.xml +++ b/P5/Source/Specs/lacunaStart.xml @@ -1,11 +1,4 @@ - - + lacuna start diff --git a/P5/Source/Specs/lang.xml b/P5/Source/Specs/lang.xml index a5825ef522..4bccd75d18 100644 --- a/P5/Source/Specs/lang.xml +++ b/P5/Source/Specs/lang.xml @@ -1,11 +1,4 @@ - - + language name diff --git a/P5/Source/Specs/langKnowledge.xml b/P5/Source/Specs/langKnowledge.xml index 71c1a14eaf..d4d6167587 100644 --- a/P5/Source/Specs/langKnowledge.xml +++ b/P5/Source/Specs/langKnowledge.xml @@ -1,10 +1,4 @@ - + language knowledge 언어 지식 conocimiento del lenguaje diff --git a/P5/Source/Specs/langKnown.xml b/P5/Source/Specs/langKnown.xml index a2bfb78124..ad8017b6c2 100644 --- a/P5/Source/Specs/langKnown.xml +++ b/P5/Source/Specs/langKnown.xml @@ -1,10 +1,4 @@ - + language known 언어 능력 語言能力 diff --git a/P5/Source/Specs/langUsage.xml b/P5/Source/Specs/langUsage.xml index 93481ceb62..877e6b75bf 100644 --- a/P5/Source/Specs/langUsage.xml +++ b/P5/Source/Specs/langUsage.xml @@ -1,11 +1,4 @@ - - + language usage diff --git a/P5/Source/Specs/language.xml b/P5/Source/Specs/language.xml index bda6f92ad7..2d3715148c 100644 --- a/P5/Source/Specs/language.xml +++ b/P5/Source/Specs/language.xml @@ -1,11 +1,4 @@ - - + language diff --git a/P5/Source/Specs/layout.xml b/P5/Source/Specs/layout.xml index 3fa64200ad..fd1697ebc1 100644 --- a/P5/Source/Specs/layout.xml +++ b/P5/Source/Specs/layout.xml @@ -1,11 +1,4 @@ - - + layout diff --git a/P5/Source/Specs/layoutDesc.xml b/P5/Source/Specs/layoutDesc.xml index 28c7b7468e..d0f0f79925 100644 --- a/P5/Source/Specs/layoutDesc.xml +++ b/P5/Source/Specs/layoutDesc.xml @@ -1,11 +1,4 @@ - - + layout description diff --git a/P5/Source/Specs/lb.xml b/P5/Source/Specs/lb.xml index 1d48306e51..729d8b207b 100644 --- a/P5/Source/Specs/lb.xml +++ b/P5/Source/Specs/lb.xml @@ -1,11 +1,4 @@ - - + line beginning diff --git a/P5/Source/Specs/lbl.xml b/P5/Source/Specs/lbl.xml index f63f590c44..00a5cbacc4 100644 --- a/P5/Source/Specs/lbl.xml +++ b/P5/Source/Specs/lbl.xml @@ -1,11 +1,4 @@ - - + label diff --git a/P5/Source/Specs/leaf.xml b/P5/Source/Specs/leaf.xml index f151cbe30d..0407e423af 100644 --- a/P5/Source/Specs/leaf.xml +++ b/P5/Source/Specs/leaf.xml @@ -1,11 +1,4 @@ - - + leaf diff --git a/P5/Source/Specs/lem.xml b/P5/Source/Specs/lem.xml index fda8a5a690..3ec658f386 100644 --- a/P5/Source/Specs/lem.xml +++ b/P5/Source/Specs/lem.xml @@ -1,10 +1,4 @@ - + lemma 레마 主題 diff --git a/P5/Source/Specs/lg.xml b/P5/Source/Specs/lg.xml index dabe40e72d..904310e6a7 100644 --- a/P5/Source/Specs/lg.xml +++ b/P5/Source/Specs/lg.xml @@ -1,11 +1,4 @@ - - + line group diff --git a/P5/Source/Specs/licence.xml b/P5/Source/Specs/licence.xml index 23392114ca..ec3a0b6db1 100644 --- a/P5/Source/Specs/licence.xml +++ b/P5/Source/Specs/licence.xml @@ -1,10 +1,4 @@ - + contains information about a licence or other legal agreement applicable to the text. contient des informations diff --git a/P5/Source/Specs/line.xml b/P5/Source/Specs/line.xml index 9e4f673189..fcc1831531 100644 --- a/P5/Source/Specs/line.xml +++ b/P5/Source/Specs/line.xml @@ -1,11 +1,4 @@ - - + contains the transcription of a topographic line in the source diff --git a/P5/Source/Specs/link.xml b/P5/Source/Specs/link.xml index 520264faf1..52f5fa6ffa 100644 --- a/P5/Source/Specs/link.xml +++ b/P5/Source/Specs/link.xml @@ -1,5 +1,4 @@ - - + link diff --git a/P5/Source/Specs/linkGrp.xml b/P5/Source/Specs/linkGrp.xml index d03a4d33bb..c9a3d8ea37 100644 --- a/P5/Source/Specs/linkGrp.xml +++ b/P5/Source/Specs/linkGrp.xml @@ -1,5 +1,4 @@ - - + link group diff --git a/P5/Source/Specs/list.xml b/P5/Source/Specs/list.xml index e3417c8952..0fc538af51 100644 --- a/P5/Source/Specs/list.xml +++ b/P5/Source/Specs/list.xml @@ -1,11 +1,4 @@ - - + list diff --git a/P5/Source/Specs/listAnnotation.xml b/P5/Source/Specs/listAnnotation.xml index d8ee3aa31a..4de68c2b20 100644 --- a/P5/Source/Specs/listAnnotation.xml +++ b/P5/Source/Specs/listAnnotation.xml @@ -1,11 +1,4 @@ - - + diff --git a/P5/Source/Specs/listApp.xml b/P5/Source/Specs/listApp.xml index 928010c452..7415b83444 100644 --- a/P5/Source/Specs/listApp.xml +++ b/P5/Source/Specs/listApp.xml @@ -1,11 +1,4 @@ - - + diff --git a/P5/Source/Specs/listBibl.xml b/P5/Source/Specs/listBibl.xml index 48213c3628..c409fbc504 100644 --- a/P5/Source/Specs/listBibl.xml +++ b/P5/Source/Specs/listBibl.xml @@ -1,11 +1,4 @@ - - + citation list diff --git a/P5/Source/Specs/listChange.xml b/P5/Source/Specs/listChange.xml index 941d7c5cd1..c9d3a0db37 100644 --- a/P5/Source/Specs/listChange.xml +++ b/P5/Source/Specs/listChange.xml @@ -1,11 +1,4 @@ - - + groups a number of change descriptions associated diff --git a/P5/Source/Specs/listEvent.xml b/P5/Source/Specs/listEvent.xml index 5cc313a292..2a9465b1ad 100644 --- a/P5/Source/Specs/listEvent.xml +++ b/P5/Source/Specs/listEvent.xml @@ -1,11 +1,4 @@ - - + list of events diff --git a/P5/Source/Specs/listForest.xml b/P5/Source/Specs/listForest.xml index ef16b48998..ba40ab4ba2 100644 --- a/P5/Source/Specs/listForest.xml +++ b/P5/Source/Specs/listForest.xml @@ -1,11 +1,4 @@ - - + provides for lists of forests. diff --git a/P5/Source/Specs/listNym.xml b/P5/Source/Specs/listNym.xml index 5de66e6487..3484bd324f 100644 --- a/P5/Source/Specs/listNym.xml +++ b/P5/Source/Specs/listNym.xml @@ -1,11 +1,4 @@ - - + list of canonical names diff --git a/P5/Source/Specs/listObject.xml b/P5/Source/Specs/listObject.xml index cdf5442ed3..d5ae2075b1 100644 --- a/P5/Source/Specs/listObject.xml +++ b/P5/Source/Specs/listObject.xml @@ -1,11 +1,4 @@ - - + list of objects diff --git a/P5/Source/Specs/listOrg.xml b/P5/Source/Specs/listOrg.xml index 0d3fc2105b..7cde9a8430 100644 --- a/P5/Source/Specs/listOrg.xml +++ b/P5/Source/Specs/listOrg.xml @@ -1,11 +1,4 @@ - - + list of organizations diff --git a/P5/Source/Specs/listPerson.xml b/P5/Source/Specs/listPerson.xml index 31963bd909..2901787068 100644 --- a/P5/Source/Specs/listPerson.xml +++ b/P5/Source/Specs/listPerson.xml @@ -1,11 +1,4 @@ - - + list of persons diff --git a/P5/Source/Specs/listPlace.xml b/P5/Source/Specs/listPlace.xml index 30b7fb9df2..4fd1e6d0a4 100644 --- a/P5/Source/Specs/listPlace.xml +++ b/P5/Source/Specs/listPlace.xml @@ -1,11 +1,4 @@ - - + list of places diff --git a/P5/Source/Specs/listPrefixDef.xml b/P5/Source/Specs/listPrefixDef.xml index 07d4ca6c7f..23b467cedb 100644 --- a/P5/Source/Specs/listPrefixDef.xml +++ b/P5/Source/Specs/listPrefixDef.xml @@ -1,11 +1,4 @@ - - + list of prefix definitions diff --git a/P5/Source/Specs/listRef.xml b/P5/Source/Specs/listRef.xml index 21f8d13d4b..753935ac94 100644 --- a/P5/Source/Specs/listRef.xml +++ b/P5/Source/Specs/listRef.xml @@ -1,11 +1,4 @@ - - + list of references diff --git a/P5/Source/Specs/listRelation.xml b/P5/Source/Specs/listRelation.xml index b8b4d6563d..81e321d2bd 100644 --- a/P5/Source/Specs/listRelation.xml +++ b/P5/Source/Specs/listRelation.xml @@ -1,11 +1,4 @@ - - + provides information about relationships identified amongst people, places, and diff --git a/P5/Source/Specs/listTranspose.xml b/P5/Source/Specs/listTranspose.xml index 841cd3a091..35758e0cfc 100644 --- a/P5/Source/Specs/listTranspose.xml +++ b/P5/Source/Specs/listTranspose.xml @@ -1,11 +1,4 @@ - - + supplies a list of transpositions, each of which is indicated at some point in diff --git a/P5/Source/Specs/listWit.xml b/P5/Source/Specs/listWit.xml index bfe9547086..71e25eedac 100644 --- a/P5/Source/Specs/listWit.xml +++ b/P5/Source/Specs/listWit.xml @@ -1,11 +1,4 @@ - - + witness list diff --git a/P5/Source/Specs/localProp.xml b/P5/Source/Specs/localProp.xml index dd12a5f824..797ff3f99d 100644 --- a/P5/Source/Specs/localProp.xml +++ b/P5/Source/Specs/localProp.xml @@ -1,4 +1,4 @@ - + diff --git a/P5/Source/Specs/locale.xml b/P5/Source/Specs/locale.xml index b9ec4e9f4e..1194ecec89 100644 --- a/P5/Source/Specs/locale.xml +++ b/P5/Source/Specs/locale.xml @@ -1,11 +1,4 @@ - - + diff --git a/P5/Source/Specs/location.xml b/P5/Source/Specs/location.xml index 2a2cd16bd2..bd84c76f3b 100644 --- a/P5/Source/Specs/location.xml +++ b/P5/Source/Specs/location.xml @@ -1,10 +1,4 @@ - + location localisation defines the location of a place as a set of geographical coordinates, in terms of other named geo-political entities, or as an diff --git a/P5/Source/Specs/locus.xml b/P5/Source/Specs/locus.xml index 5dabd4ee0b..05438e07cd 100644 --- a/P5/Source/Specs/locus.xml +++ b/P5/Source/Specs/locus.xml @@ -1,11 +1,4 @@ - - + locus diff --git a/P5/Source/Specs/locusGrp.xml b/P5/Source/Specs/locusGrp.xml index 366114db64..798aa873f1 100644 --- a/P5/Source/Specs/locusGrp.xml +++ b/P5/Source/Specs/locusGrp.xml @@ -1,11 +1,4 @@ - - + locus group diff --git a/P5/Source/Specs/m.xml b/P5/Source/Specs/m.xml index 4539961b5c..1cb3c310e4 100644 --- a/P5/Source/Specs/m.xml +++ b/P5/Source/Specs/m.xml @@ -1,11 +1,4 @@ - - + morpheme diff --git a/P5/Source/Specs/macro.abContent.xml b/P5/Source/Specs/macro.abContent.xml index 896739362e..bbfc8461d2 100644 --- a/P5/Source/Specs/macro.abContent.xml +++ b/P5/Source/Specs/macro.abContent.xml @@ -1,11 +1,4 @@ - - + anonymous block content diff --git a/P5/Source/Specs/macro.limitedContent.xml b/P5/Source/Specs/macro.limitedContent.xml index 9b21aa5493..204eb07cad 100644 --- a/P5/Source/Specs/macro.limitedContent.xml +++ b/P5/Source/Specs/macro.limitedContent.xml @@ -1,11 +1,4 @@ - - + paragraph content diff --git a/P5/Source/Specs/macro.paraContent.xml b/P5/Source/Specs/macro.paraContent.xml index 21112a4822..74a2771895 100644 --- a/P5/Source/Specs/macro.paraContent.xml +++ b/P5/Source/Specs/macro.paraContent.xml @@ -1,11 +1,4 @@ - - + paragraph content diff --git a/P5/Source/Specs/macro.phraseSeq.limited.xml b/P5/Source/Specs/macro.phraseSeq.limited.xml index b2fae86a03..dbb93623eb 100644 --- a/P5/Source/Specs/macro.phraseSeq.limited.xml +++ b/P5/Source/Specs/macro.phraseSeq.limited.xml @@ -1,11 +1,4 @@ - - + limited phrase sequence diff --git a/P5/Source/Specs/macro.phraseSeq.xml b/P5/Source/Specs/macro.phraseSeq.xml index aeff2e469e..39d2fe7767 100644 --- a/P5/Source/Specs/macro.phraseSeq.xml +++ b/P5/Source/Specs/macro.phraseSeq.xml @@ -1,11 +1,4 @@ - - + phrase sequence diff --git a/P5/Source/Specs/macro.specialPara.xml b/P5/Source/Specs/macro.specialPara.xml index a531a633e4..7c589d54b2 100644 --- a/P5/Source/Specs/macro.specialPara.xml +++ b/P5/Source/Specs/macro.specialPara.xml @@ -1,11 +1,4 @@ - - + 'special' paragraph content diff --git a/P5/Source/Specs/macro.xtext.xml b/P5/Source/Specs/macro.xtext.xml index 3c1a9d0bb8..70e2073584 100644 --- a/P5/Source/Specs/macro.xtext.xml +++ b/P5/Source/Specs/macro.xtext.xml @@ -1,11 +1,4 @@ - - + extended text diff --git a/P5/Source/Specs/macroRef.xml b/P5/Source/Specs/macroRef.xml index ba756f8d91..de5698dce3 100644 --- a/P5/Source/Specs/macroRef.xml +++ b/P5/Source/Specs/macroRef.xml @@ -1,11 +1,4 @@ - - + points to the specification for some pattern which is to be included in a schema diff --git a/P5/Source/Specs/macroSpec.xml b/P5/Source/Specs/macroSpec.xml index bda9b5aca2..5ec54e85be 100644 --- a/P5/Source/Specs/macroSpec.xml +++ b/P5/Source/Specs/macroSpec.xml @@ -1,11 +1,4 @@ - - + macro specification diff --git a/P5/Source/Specs/mapping.xml b/P5/Source/Specs/mapping.xml index 6cc9808dc1..ed766e8285 100644 --- a/P5/Source/Specs/mapping.xml +++ b/P5/Source/Specs/mapping.xml @@ -1,11 +1,4 @@ - - + character mapping diff --git a/P5/Source/Specs/material.xml b/P5/Source/Specs/material.xml index 403b4f0cf2..099a08c612 100644 --- a/P5/Source/Specs/material.xml +++ b/P5/Source/Specs/material.xml @@ -1,11 +1,4 @@ - - + material diff --git a/P5/Source/Specs/measure.xml b/P5/Source/Specs/measure.xml index 31c78873c9..c28e598124 100644 --- a/P5/Source/Specs/measure.xml +++ b/P5/Source/Specs/measure.xml @@ -1,11 +1,4 @@ - - + measure diff --git a/P5/Source/Specs/measureGrp.xml b/P5/Source/Specs/measureGrp.xml index 0d6c2a77ad..d5c9314e9a 100644 --- a/P5/Source/Specs/measureGrp.xml +++ b/P5/Source/Specs/measureGrp.xml @@ -1,11 +1,4 @@ - - + measure group diff --git a/P5/Source/Specs/media.xml b/P5/Source/Specs/media.xml index f4f76dde16..ea14edfa18 100644 --- a/P5/Source/Specs/media.xml +++ b/P5/Source/Specs/media.xml @@ -1,11 +1,4 @@ - - + indicates the location of any form of external media such as diff --git a/P5/Source/Specs/meeting.xml b/P5/Source/Specs/meeting.xml index dcde91d528..2662ca20b4 100644 --- a/P5/Source/Specs/meeting.xml +++ b/P5/Source/Specs/meeting.xml @@ -1,10 +1,4 @@ - + contains the formalized descriptive title for a meeting or conference, for use in a bibliographic description for an item derived from such a meeting, or as a heading or preamble to publications emanating from it. diff --git a/P5/Source/Specs/memberOf.xml b/P5/Source/Specs/memberOf.xml index 0ec6ae5d05..c10c9e3397 100644 --- a/P5/Source/Specs/memberOf.xml +++ b/P5/Source/Specs/memberOf.xml @@ -1,11 +1,4 @@ - - + specifies class membership of the documented element or class. diff --git a/P5/Source/Specs/mentioned.xml b/P5/Source/Specs/mentioned.xml index 1ac30b1f74..a665e7e67c 100644 --- a/P5/Source/Specs/mentioned.xml +++ b/P5/Source/Specs/mentioned.xml @@ -1,11 +1,4 @@ - - + diff --git a/P5/Source/Specs/metDecl.xml b/P5/Source/Specs/metDecl.xml index 16cb3e411e..a02918702c 100644 --- a/P5/Source/Specs/metDecl.xml +++ b/P5/Source/Specs/metDecl.xml @@ -1,11 +1,4 @@ - - + metrical notation declaration diff --git a/P5/Source/Specs/metSym.xml b/P5/Source/Specs/metSym.xml index a2a0abc6a4..b966ea0ece 100644 --- a/P5/Source/Specs/metSym.xml +++ b/P5/Source/Specs/metSym.xml @@ -1,11 +1,4 @@ - - + metrical notation symbol diff --git a/P5/Source/Specs/metamark.xml b/P5/Source/Specs/metamark.xml index 4844932e02..5f6f9935fa 100644 --- a/P5/Source/Specs/metamark.xml +++ b/P5/Source/Specs/metamark.xml @@ -1,11 +1,4 @@ - - + contains or describes any kind of graphic or written signal diff --git a/P5/Source/Specs/milestone.xml b/P5/Source/Specs/milestone.xml index d24366a5cf..d42a00d3be 100644 --- a/P5/Source/Specs/milestone.xml +++ b/P5/Source/Specs/milestone.xml @@ -1,11 +1,4 @@ - - + milestone diff --git a/P5/Source/Specs/mod.xml b/P5/Source/Specs/mod.xml index 315f67df7a..9d9a668621 100644 --- a/P5/Source/Specs/mod.xml +++ b/P5/Source/Specs/mod.xml @@ -1,11 +1,4 @@ - - + represents any kind of modification identified within a single document. diff --git a/P5/Source/Specs/model.addrPart.xml b/P5/Source/Specs/model.addrPart.xml index 6757003ae1..7ba411f4c1 100644 --- a/P5/Source/Specs/model.addrPart.xml +++ b/P5/Source/Specs/model.addrPart.xml @@ -1,11 +1,4 @@ - - + groups elements such as names or postal codes which may appear as part of a diff --git a/P5/Source/Specs/model.addressLike.xml b/P5/Source/Specs/model.addressLike.xml index f0910c30b5..b0cb56b841 100644 --- a/P5/Source/Specs/model.addressLike.xml +++ b/P5/Source/Specs/model.addressLike.xml @@ -1,11 +1,4 @@ - - + groups elements used to represent a postal or email address. diff --git a/P5/Source/Specs/model.annotationLike.xml b/P5/Source/Specs/model.annotationLike.xml index d3f62378ab..2f3b0648d6 100644 --- a/P5/Source/Specs/model.annotationLike.xml +++ b/P5/Source/Specs/model.annotationLike.xml @@ -1,11 +1,4 @@ - - + groups elements used to represent annotations. diff --git a/P5/Source/Specs/model.annotationPart.body.xml b/P5/Source/Specs/model.annotationPart.body.xml index e3d6448857..4ed5fe24b5 100644 --- a/P5/Source/Specs/model.annotationPart.body.xml +++ b/P5/Source/Specs/model.annotationPart.body.xml @@ -1,11 +1,4 @@ - - + groups elements which may be used as an annotation body. diff --git a/P5/Source/Specs/model.applicationLike.xml b/P5/Source/Specs/model.applicationLike.xml index a00d21edca..7ef827e172 100644 --- a/P5/Source/Specs/model.applicationLike.xml +++ b/P5/Source/Specs/model.applicationLike.xml @@ -1,11 +1,4 @@ - - + groups elements used to record application-specific information about a document in its diff --git a/P5/Source/Specs/model.attributable.xml b/P5/Source/Specs/model.attributable.xml index 646494fcc2..2c59ae16bb 100644 --- a/P5/Source/Specs/model.attributable.xml +++ b/P5/Source/Specs/model.attributable.xml @@ -1,10 +1,4 @@ - + groups elements that contain a word or phrase that can be attributed to a source. gruppiert Elemente, die ein Wort oder eine Phrase enthalten, welche einer Quelle zugeschrieben werden können. + groups elements such as licences and paragraphs of text which may appear as part of an diff --git a/P5/Source/Specs/model.biblLike.xml b/P5/Source/Specs/model.biblLike.xml index 19e72966ac..f153110052 100644 --- a/P5/Source/Specs/model.biblLike.xml +++ b/P5/Source/Specs/model.biblLike.xml @@ -1,11 +1,4 @@ - - + groups elements containing a bibliographic description. diff --git a/P5/Source/Specs/model.biblPart.xml b/P5/Source/Specs/model.biblPart.xml index 6c20cde833..fe071e78f6 100644 --- a/P5/Source/Specs/model.biblPart.xml +++ b/P5/Source/Specs/model.biblPart.xml @@ -1,11 +1,4 @@ - - + groups elements which represent components of a bibliographic description. diff --git a/P5/Source/Specs/model.castItemPart.xml b/P5/Source/Specs/model.castItemPart.xml index 747a62fa9c..4c12d14030 100644 --- a/P5/Source/Specs/model.castItemPart.xml +++ b/P5/Source/Specs/model.castItemPart.xml @@ -1,11 +1,4 @@ - - + groups component elements of an entry in a cast list, such as dramatic role or actor's name. diff --git a/P5/Source/Specs/model.catDescPart.xml b/P5/Source/Specs/model.catDescPart.xml index 17dd6e556d..3caed96273 100644 --- a/P5/Source/Specs/model.catDescPart.xml +++ b/P5/Source/Specs/model.catDescPart.xml @@ -1,11 +1,4 @@ - - + groups component elements of the TEI header Category Description. diff --git a/P5/Source/Specs/model.certLike.xml b/P5/Source/Specs/model.certLike.xml index 560582e476..7d3b910a1d 100644 --- a/P5/Source/Specs/model.certLike.xml +++ b/P5/Source/Specs/model.certLike.xml @@ -1,11 +1,4 @@ - - + groups elements which are used to indicate uncertainty or diff --git a/P5/Source/Specs/model.choicePart.xml b/P5/Source/Specs/model.choicePart.xml index b2eaf285af..e36a7706e4 100644 --- a/P5/Source/Specs/model.choicePart.xml +++ b/P5/Source/Specs/model.choicePart.xml @@ -1,11 +1,4 @@ - - + groups elements (other than choice itself) which can be used within a diff --git a/P5/Source/Specs/model.common.xml b/P5/Source/Specs/model.common.xml index 36bb880a66..3a8345c6a4 100644 --- a/P5/Source/Specs/model.common.xml +++ b/P5/Source/Specs/model.common.xml @@ -1,11 +1,4 @@ - - + groups common chunk- and inter-level elements. diff --git a/P5/Source/Specs/model.contentPart.xml b/P5/Source/Specs/model.contentPart.xml index 220a6b424b..6f6a58baa3 100644 --- a/P5/Source/Specs/model.contentPart.xml +++ b/P5/Source/Specs/model.contentPart.xml @@ -1,11 +1,4 @@ - - + groups elements which diff --git a/P5/Source/Specs/model.correspActionPart.xml b/P5/Source/Specs/model.correspActionPart.xml index 23493cafab..5fce18c220 100644 --- a/P5/Source/Specs/model.correspActionPart.xml +++ b/P5/Source/Specs/model.correspActionPart.xml @@ -1,11 +1,4 @@ - - + groups elements which define the diff --git a/P5/Source/Specs/model.correspContextPart.xml b/P5/Source/Specs/model.correspContextPart.xml index 07359944e9..c5aa85f88e 100644 --- a/P5/Source/Specs/model.correspContextPart.xml +++ b/P5/Source/Specs/model.correspContextPart.xml @@ -1,11 +1,4 @@ - - + groups elements which may diff --git a/P5/Source/Specs/model.correspDescPart.xml b/P5/Source/Specs/model.correspDescPart.xml index f8027993bf..d9fec20b59 100644 --- a/P5/Source/Specs/model.correspDescPart.xml +++ b/P5/Source/Specs/model.correspDescPart.xml @@ -1,11 +1,4 @@ - - + groups together metadata diff --git a/P5/Source/Specs/model.dateLike.xml b/P5/Source/Specs/model.dateLike.xml index 8d8bab23c2..6e90e0a624 100644 --- a/P5/Source/Specs/model.dateLike.xml +++ b/P5/Source/Specs/model.dateLike.xml @@ -1,11 +1,4 @@ - - + groups elements containing temporal expressions. diff --git a/P5/Source/Specs/model.descLike.xml b/P5/Source/Specs/model.descLike.xml index dca08fbb4a..bc0b30bc33 100644 --- a/P5/Source/Specs/model.descLike.xml +++ b/P5/Source/Specs/model.descLike.xml @@ -1,11 +1,4 @@ - - + groups elements which contain a description of their function. diff --git a/P5/Source/Specs/model.describedResource.xml b/P5/Source/Specs/model.describedResource.xml index dbb15bdd1f..cd32d9dd5a 100644 --- a/P5/Source/Specs/model.describedResource.xml +++ b/P5/Source/Specs/model.describedResource.xml @@ -1,11 +1,4 @@ - - + groups elements which diff --git a/P5/Source/Specs/model.dimLike.xml b/P5/Source/Specs/model.dimLike.xml index 046a0672fb..875460f33c 100644 --- a/P5/Source/Specs/model.dimLike.xml +++ b/P5/Source/Specs/model.dimLike.xml @@ -1,11 +1,4 @@ - - + groups elements which describe a measurement forming part of diff --git a/P5/Source/Specs/model.div1Like.xml b/P5/Source/Specs/model.div1Like.xml index 6a3a2f125e..8949d95c77 100644 --- a/P5/Source/Specs/model.div1Like.xml +++ b/P5/Source/Specs/model.div1Like.xml @@ -1,11 +1,4 @@ - - + groups top-level structural divisions. diff --git a/P5/Source/Specs/model.div2Like.xml b/P5/Source/Specs/model.div2Like.xml index eb543417ad..3305b2d5e5 100644 --- a/P5/Source/Specs/model.div2Like.xml +++ b/P5/Source/Specs/model.div2Like.xml @@ -1,11 +1,4 @@ - - + groups second-level structural divisions. diff --git a/P5/Source/Specs/model.div3Like.xml b/P5/Source/Specs/model.div3Like.xml index d4d29eb3ee..0a7d22ae4d 100644 --- a/P5/Source/Specs/model.div3Like.xml +++ b/P5/Source/Specs/model.div3Like.xml @@ -1,11 +1,4 @@ - - + groups third-level structural divisions. diff --git a/P5/Source/Specs/model.div4Like.xml b/P5/Source/Specs/model.div4Like.xml index a1d4e399c8..e1985e8b0e 100644 --- a/P5/Source/Specs/model.div4Like.xml +++ b/P5/Source/Specs/model.div4Like.xml @@ -1,11 +1,4 @@ - - + groups fourth-level structural divisions. diff --git a/P5/Source/Specs/model.div5Like.xml b/P5/Source/Specs/model.div5Like.xml index 7095fcd034..9200705136 100644 --- a/P5/Source/Specs/model.div5Like.xml +++ b/P5/Source/Specs/model.div5Like.xml @@ -1,11 +1,4 @@ - - + groups fifth-level structural divisions. diff --git a/P5/Source/Specs/model.div6Like.xml b/P5/Source/Specs/model.div6Like.xml index e15a8f7d91..5cae7f5656 100644 --- a/P5/Source/Specs/model.div6Like.xml +++ b/P5/Source/Specs/model.div6Like.xml @@ -1,11 +1,4 @@ - - + groups sixth-level structural divisions. diff --git a/P5/Source/Specs/model.div7Like.xml b/P5/Source/Specs/model.div7Like.xml index 6d019eab9d..819acfd4d5 100644 --- a/P5/Source/Specs/model.div7Like.xml +++ b/P5/Source/Specs/model.div7Like.xml @@ -1,11 +1,4 @@ - - + groups seventh-level structural divisions. diff --git a/P5/Source/Specs/model.divBottom.xml b/P5/Source/Specs/model.divBottom.xml index ca8ce87e11..1fd3bc39ee 100644 --- a/P5/Source/Specs/model.divBottom.xml +++ b/P5/Source/Specs/model.divBottom.xml @@ -1,11 +1,4 @@ - - + groups elements appearing at the end of a text diff --git a/P5/Source/Specs/model.divBottomPart.xml b/P5/Source/Specs/model.divBottomPart.xml index 4d34848811..6175322295 100644 --- a/P5/Source/Specs/model.divBottomPart.xml +++ b/P5/Source/Specs/model.divBottomPart.xml @@ -1,11 +1,4 @@ - - + groups elements which can occur only at the end of a text diff --git a/P5/Source/Specs/model.divGenLike.xml b/P5/Source/Specs/model.divGenLike.xml index efdb29702c..db05db0e83 100644 --- a/P5/Source/Specs/model.divGenLike.xml +++ b/P5/Source/Specs/model.divGenLike.xml @@ -1,11 +1,4 @@ - - + groups elements used to represent a structural division which is generated rather than diff --git a/P5/Source/Specs/model.divLike.xml b/P5/Source/Specs/model.divLike.xml index effe212310..5bb834f6f7 100644 --- a/P5/Source/Specs/model.divLike.xml +++ b/P5/Source/Specs/model.divLike.xml @@ -1,11 +1,4 @@ - - + groups elements used to represent un-numbered generic structural divisions. diff --git a/P5/Source/Specs/model.divPart.spoken.xml b/P5/Source/Specs/model.divPart.spoken.xml index 40919d95fd..6b19d4ec7d 100644 --- a/P5/Source/Specs/model.divPart.spoken.xml +++ b/P5/Source/Specs/model.divPart.spoken.xml @@ -1,11 +1,4 @@ - - + groups elements structurally analogous to paragraphs within spoken texts. diff --git a/P5/Source/Specs/model.divPart.xml b/P5/Source/Specs/model.divPart.xml index 4bdc6c87b4..85b74f98ec 100644 --- a/P5/Source/Specs/model.divPart.xml +++ b/P5/Source/Specs/model.divPart.xml @@ -1,11 +1,4 @@ - - + groups paragraph-level elements appearing directly within divisions. diff --git a/P5/Source/Specs/model.divTop.xml b/P5/Source/Specs/model.divTop.xml index 0403bd0558..336d6e3c96 100644 --- a/P5/Source/Specs/model.divTop.xml +++ b/P5/Source/Specs/model.divTop.xml @@ -1,11 +1,4 @@ - - + groups elements appearing at the beginning of a diff --git a/P5/Source/Specs/model.divTopPart.xml b/P5/Source/Specs/model.divTopPart.xml index 9ace91dd2a..5038063ad9 100644 --- a/P5/Source/Specs/model.divTopPart.xml +++ b/P5/Source/Specs/model.divTopPart.xml @@ -1,11 +1,4 @@ - - + groups elements which can occur only at the beginning of a text division. diff --git a/P5/Source/Specs/model.divWrapper.xml b/P5/Source/Specs/model.divWrapper.xml index 5ea3a94050..c8c0f0bbda 100644 --- a/P5/Source/Specs/model.divWrapper.xml +++ b/P5/Source/Specs/model.divWrapper.xml @@ -1,11 +1,4 @@ - - + groups elements which can appear at either top or bottom of a diff --git a/P5/Source/Specs/model.editorialDeclPart.xml b/P5/Source/Specs/model.editorialDeclPart.xml index 1fa7d8cbfe..14edb0c6ab 100644 --- a/P5/Source/Specs/model.editorialDeclPart.xml +++ b/P5/Source/Specs/model.editorialDeclPart.xml @@ -1,11 +1,4 @@ - - + groups elements which may be used inside editorialDecl and appear multiple times. diff --git a/P5/Source/Specs/model.egLike.xml b/P5/Source/Specs/model.egLike.xml index 71e612dc95..46fa32e6d9 100644 --- a/P5/Source/Specs/model.egLike.xml +++ b/P5/Source/Specs/model.egLike.xml @@ -1,11 +1,4 @@ - - + groups elements containing examples or illustrations. diff --git a/P5/Source/Specs/model.emphLike.xml b/P5/Source/Specs/model.emphLike.xml index d63c0f715a..78e6c32fc2 100644 --- a/P5/Source/Specs/model.emphLike.xml +++ b/P5/Source/Specs/model.emphLike.xml @@ -1,11 +1,4 @@ - - + groups phrase-level elements which are typographically diff --git a/P5/Source/Specs/model.encodingDescPart.xml b/P5/Source/Specs/model.encodingDescPart.xml index 35a4917274..3f639ac7a3 100644 --- a/P5/Source/Specs/model.encodingDescPart.xml +++ b/P5/Source/Specs/model.encodingDescPart.xml @@ -1,11 +1,4 @@ - - + groups elements which may be used inside encodingDesc and appear multiple times. diff --git a/P5/Source/Specs/model.entryLike.xml b/P5/Source/Specs/model.entryLike.xml index 9a34dc85a1..8f4c9e27a6 100644 --- a/P5/Source/Specs/model.entryLike.xml +++ b/P5/Source/Specs/model.entryLike.xml @@ -1,11 +1,4 @@ - - + groups elements structurally analogous to paragraphs within dictionaries. diff --git a/P5/Source/Specs/model.entryPart.top.xml b/P5/Source/Specs/model.entryPart.top.xml index 2d9463cec2..2e27558c91 100644 --- a/P5/Source/Specs/model.entryPart.top.xml +++ b/P5/Source/Specs/model.entryPart.top.xml @@ -1,11 +1,4 @@ - - + groups high level elements within a structured dictionary entry diff --git a/P5/Source/Specs/model.entryPart.xml b/P5/Source/Specs/model.entryPart.xml index 3e21a2fcdd..2f5d7a0022 100644 --- a/P5/Source/Specs/model.entryPart.xml +++ b/P5/Source/Specs/model.entryPart.xml @@ -1,11 +1,4 @@ - - + groups non-morphological elements appearing within a dictionary entry. diff --git a/P5/Source/Specs/model.eventLike.xml b/P5/Source/Specs/model.eventLike.xml index 18c62b330a..55feb20a45 100644 --- a/P5/Source/Specs/model.eventLike.xml +++ b/P5/Source/Specs/model.eventLike.xml @@ -1,11 +1,4 @@ - - + groups elements which describe events. diff --git a/P5/Source/Specs/model.featureVal.complex.xml b/P5/Source/Specs/model.featureVal.complex.xml index 05ee1f274f..19ec360806 100644 --- a/P5/Source/Specs/model.featureVal.complex.xml +++ b/P5/Source/Specs/model.featureVal.complex.xml @@ -1,11 +1,4 @@ - - + groups elements which express complex feature values in feature diff --git a/P5/Source/Specs/model.featureVal.single.xml b/P5/Source/Specs/model.featureVal.single.xml index 05e5a2df70..7c6db41df8 100644 --- a/P5/Source/Specs/model.featureVal.single.xml +++ b/P5/Source/Specs/model.featureVal.single.xml @@ -1,11 +1,4 @@ - - + group elements used to represent atomic feature values in feature structures. diff --git a/P5/Source/Specs/model.featureVal.xml b/P5/Source/Specs/model.featureVal.xml index c36cc9f01e..c5b5aa8292 100644 --- a/P5/Source/Specs/model.featureVal.xml +++ b/P5/Source/Specs/model.featureVal.xml @@ -1,11 +1,4 @@ - - + groups elements which represent feature values in feature structures. diff --git a/P5/Source/Specs/model.formPart.xml b/P5/Source/Specs/model.formPart.xml index eb3cda22af..9c1ceb3753 100644 --- a/P5/Source/Specs/model.formPart.xml +++ b/P5/Source/Specs/model.formPart.xml @@ -1,11 +1,4 @@ - - + groups elements allowed within a form element in a dictionary. diff --git a/P5/Source/Specs/model.frontPart.drama.xml b/P5/Source/Specs/model.frontPart.drama.xml index fa17334878..ebc9920e22 100644 --- a/P5/Source/Specs/model.frontPart.drama.xml +++ b/P5/Source/Specs/model.frontPart.drama.xml @@ -1,11 +1,4 @@ - - + groups elements which appear at the level of divisions within front or back matter of diff --git a/P5/Source/Specs/model.frontPart.xml b/P5/Source/Specs/model.frontPart.xml index dd0c66cae9..e6ac36c010 100644 --- a/P5/Source/Specs/model.frontPart.xml +++ b/P5/Source/Specs/model.frontPart.xml @@ -1,11 +1,4 @@ - - + groups elements which appear at the level of divisions within front or back matter. diff --git a/P5/Source/Specs/model.fsdDeclPart.xml b/P5/Source/Specs/model.fsdDeclPart.xml index a4d3e9224d..ca83d64783 100644 --- a/P5/Source/Specs/model.fsdDeclPart.xml +++ b/P5/Source/Specs/model.fsdDeclPart.xml @@ -1,9 +1,4 @@ - - + groups elements which can occur as direct children of fsdDecl. diff --git a/P5/Source/Specs/model.gLike.xml b/P5/Source/Specs/model.gLike.xml index 4f5b02e7a5..549c8e2f21 100644 --- a/P5/Source/Specs/model.gLike.xml +++ b/P5/Source/Specs/model.gLike.xml @@ -1,11 +1,4 @@ - - + groups elements used to represent individual non-Unicode characters or glyphs. diff --git a/P5/Source/Specs/model.global.edit.xml b/P5/Source/Specs/model.global.edit.xml index d2e8630a26..6a30b24222 100644 --- a/P5/Source/Specs/model.global.edit.xml +++ b/P5/Source/Specs/model.global.edit.xml @@ -1,11 +1,4 @@ - - + groups globally available elements which perform a specifically editorial function. diff --git a/P5/Source/Specs/model.global.meta.xml b/P5/Source/Specs/model.global.meta.xml index a6fcad2972..ed80bdb7d1 100644 --- a/P5/Source/Specs/model.global.meta.xml +++ b/P5/Source/Specs/model.global.meta.xml @@ -1,11 +1,4 @@ - - + groups globally available elements which describe the status of other elements. diff --git a/P5/Source/Specs/model.global.spoken.xml b/P5/Source/Specs/model.global.spoken.xml index 5cc7a505a3..25bb62990f 100644 --- a/P5/Source/Specs/model.global.spoken.xml +++ b/P5/Source/Specs/model.global.spoken.xml @@ -1,11 +1,4 @@ - - + groups elements diff --git a/P5/Source/Specs/model.global.xml b/P5/Source/Specs/model.global.xml index d172ad3b9d..5079a3498b 100644 --- a/P5/Source/Specs/model.global.xml +++ b/P5/Source/Specs/model.global.xml @@ -1,11 +1,4 @@ - - + groups elements which may appear at any point within a TEI text. diff --git a/P5/Source/Specs/model.gramPart.xml b/P5/Source/Specs/model.gramPart.xml index 889af593de..f3169f7f98 100644 --- a/P5/Source/Specs/model.gramPart.xml +++ b/P5/Source/Specs/model.gramPart.xml @@ -1,11 +1,4 @@ - - + groups elements allowed within a gramGrp element in a dictionary. diff --git a/P5/Source/Specs/model.graphicLike.xml b/P5/Source/Specs/model.graphicLike.xml index 8273497390..3d309f3344 100644 --- a/P5/Source/Specs/model.graphicLike.xml +++ b/P5/Source/Specs/model.graphicLike.xml @@ -1,11 +1,4 @@ - - + groups elements containing images, formulae, and diff --git a/P5/Source/Specs/model.headLike.xml b/P5/Source/Specs/model.headLike.xml index b9afd6f9ed..e5a218c1b0 100644 --- a/P5/Source/Specs/model.headLike.xml +++ b/P5/Source/Specs/model.headLike.xml @@ -1,11 +1,4 @@ - - + groups elements used to provide a title or heading at the start of a text diff --git a/P5/Source/Specs/model.hiLike.xml b/P5/Source/Specs/model.hiLike.xml index 67c6ee0cc5..f2e4281555 100644 --- a/P5/Source/Specs/model.hiLike.xml +++ b/P5/Source/Specs/model.hiLike.xml @@ -1,11 +1,4 @@ - - + groups phrase-level elements which are typographically distinct but to which no specific diff --git a/P5/Source/Specs/model.highlighted.xml b/P5/Source/Specs/model.highlighted.xml index 4b78cc5422..033508e9e1 100644 --- a/P5/Source/Specs/model.highlighted.xml +++ b/P5/Source/Specs/model.highlighted.xml @@ -1,11 +1,4 @@ - - + groups phrase-level elements which are typographically distinct. diff --git a/P5/Source/Specs/model.identEquiv.xml b/P5/Source/Specs/model.identEquiv.xml index ba4dcff36d..c8b44db1cb 100644 --- a/P5/Source/Specs/model.identEquiv.xml +++ b/P5/Source/Specs/model.identEquiv.xml @@ -1,11 +1,4 @@ - - + groups elements which provide an equivalent value to the identity of their parent element, either as a formal construct or in natural language. diff --git a/P5/Source/Specs/model.identSynonyms.xml b/P5/Source/Specs/model.identSynonyms.xml index c3b8d13d06..79187a0b83 100644 --- a/P5/Source/Specs/model.identSynonyms.xml +++ b/P5/Source/Specs/model.identSynonyms.xml @@ -1,11 +1,4 @@ - - + groups elements which provide an explanation, equivalency, or alternative name for a markup construct. diff --git a/P5/Source/Specs/model.imprintPart.xml b/P5/Source/Specs/model.imprintPart.xml index ad0df3eae6..4323c9bd0d 100644 --- a/P5/Source/Specs/model.imprintPart.xml +++ b/P5/Source/Specs/model.imprintPart.xml @@ -1,11 +1,4 @@ - - + groups the bibliographic elements which occur inside imprints. diff --git a/P5/Source/Specs/model.inter.xml b/P5/Source/Specs/model.inter.xml index 18aaa6b9a6..8c701142d7 100644 --- a/P5/Source/Specs/model.inter.xml +++ b/P5/Source/Specs/model.inter.xml @@ -1,11 +1,4 @@ - - + groups elements which can appear either within or between paragraph-like elements. diff --git a/P5/Source/Specs/model.lLike.xml b/P5/Source/Specs/model.lLike.xml index eedc50e6c8..e576766768 100644 --- a/P5/Source/Specs/model.lLike.xml +++ b/P5/Source/Specs/model.lLike.xml @@ -1,11 +1,4 @@ - - + groups elements representing metrical components such as verse lines. diff --git a/P5/Source/Specs/model.lPart.xml b/P5/Source/Specs/model.lPart.xml index 74209d799e..f07c52d2ab 100644 --- a/P5/Source/Specs/model.lPart.xml +++ b/P5/Source/Specs/model.lPart.xml @@ -1,11 +1,4 @@ - - + groups phrase-level elements which may appear within verse only. diff --git a/P5/Source/Specs/model.labelLike.xml b/P5/Source/Specs/model.labelLike.xml index 8405c94f18..d9a671bf18 100644 --- a/P5/Source/Specs/model.labelLike.xml +++ b/P5/Source/Specs/model.labelLike.xml @@ -1,11 +1,4 @@ - - + groups elements used to gloss or explain other parts of a document. diff --git a/P5/Source/Specs/model.lexicalRefinement.xml b/P5/Source/Specs/model.lexicalRefinement.xml index 73f14455e8..196cbedba9 100644 --- a/P5/Source/Specs/model.lexicalRefinement.xml +++ b/P5/Source/Specs/model.lexicalRefinement.xml @@ -1,11 +1,4 @@ - - + diff --git a/P5/Source/Specs/model.limitedPhrase.xml b/P5/Source/Specs/model.limitedPhrase.xml index c959b1eac7..2084f4fdc2 100644 --- a/P5/Source/Specs/model.limitedPhrase.xml +++ b/P5/Source/Specs/model.limitedPhrase.xml @@ -1,11 +1,4 @@ - - + groups phrase-level elements excluding those elements primarily intended for transcription diff --git a/P5/Source/Specs/model.linePart.xml b/P5/Source/Specs/model.linePart.xml index 7e0e2027c3..bf07c615c4 100644 --- a/P5/Source/Specs/model.linePart.xml +++ b/P5/Source/Specs/model.linePart.xml @@ -1,11 +1,4 @@ - - + groups transcriptional elements which appear within lines or diff --git a/P5/Source/Specs/model.listLike.xml b/P5/Source/Specs/model.listLike.xml index ce84746b4d..ca16d79da6 100644 --- a/P5/Source/Specs/model.listLike.xml +++ b/P5/Source/Specs/model.listLike.xml @@ -1,11 +1,4 @@ - - + groups list-like elements. diff --git a/P5/Source/Specs/model.measureLike.xml b/P5/Source/Specs/model.measureLike.xml index fdfcdd07a4..63be2d9015 100644 --- a/P5/Source/Specs/model.measureLike.xml +++ b/P5/Source/Specs/model.measureLike.xml @@ -1,11 +1,4 @@ - - + groups elements which denote a number, a quantity, a measurement, or similar piece of text diff --git a/P5/Source/Specs/model.milestoneLike.xml b/P5/Source/Specs/model.milestoneLike.xml index ed1fc5d87e..ef5da5015c 100644 --- a/P5/Source/Specs/model.milestoneLike.xml +++ b/P5/Source/Specs/model.milestoneLike.xml @@ -1,11 +1,4 @@ - - + groups milestone-style diff --git a/P5/Source/Specs/model.morphLike.xml b/P5/Source/Specs/model.morphLike.xml index 1d7b0a2377..b2f40ef7b2 100644 --- a/P5/Source/Specs/model.morphLike.xml +++ b/P5/Source/Specs/model.morphLike.xml @@ -1,11 +1,4 @@ - - + groups elements which provide morphological information within a dictionary entry. diff --git a/P5/Source/Specs/model.msItemPart.xml b/P5/Source/Specs/model.msItemPart.xml index 21afd6bf93..a4b3c71bac 100644 --- a/P5/Source/Specs/model.msItemPart.xml +++ b/P5/Source/Specs/model.msItemPart.xml @@ -1,11 +1,4 @@ - - + groups elements which can appear within a manuscript item description. diff --git a/P5/Source/Specs/model.msQuoteLike.xml b/P5/Source/Specs/model.msQuoteLike.xml index b3405d23b4..9bb52bbbb5 100644 --- a/P5/Source/Specs/model.msQuoteLike.xml +++ b/P5/Source/Specs/model.msQuoteLike.xml @@ -1,11 +1,4 @@ - - + groups elements which represent passages such as titles quoted from a manuscript as a part diff --git a/P5/Source/Specs/model.nameLike.agent.xml b/P5/Source/Specs/model.nameLike.agent.xml index 0a24434fc2..baa013cab5 100644 --- a/P5/Source/Specs/model.nameLike.agent.xml +++ b/P5/Source/Specs/model.nameLike.agent.xml @@ -1,11 +1,4 @@ - - + groups elements which contain names of individuals diff --git a/P5/Source/Specs/model.nameLike.xml b/P5/Source/Specs/model.nameLike.xml index 3682f1fc5c..9361febe84 100644 --- a/P5/Source/Specs/model.nameLike.xml +++ b/P5/Source/Specs/model.nameLike.xml @@ -1,11 +1,4 @@ - - + groups elements which name or refer to a person, place, or organization. diff --git a/P5/Source/Specs/model.noteLike.xml b/P5/Source/Specs/model.noteLike.xml index 3b04a4a961..5e0ae356bb 100644 --- a/P5/Source/Specs/model.noteLike.xml +++ b/P5/Source/Specs/model.noteLike.xml @@ -1,11 +1,4 @@ - - + groups globally-available note-like elements. diff --git a/P5/Source/Specs/model.objectLike.xml b/P5/Source/Specs/model.objectLike.xml index 170ba0f896..8be357e26b 100644 --- a/P5/Source/Specs/model.objectLike.xml +++ b/P5/Source/Specs/model.objectLike.xml @@ -1,10 +1,4 @@ - + groups elements which describe objects. diff --git a/P5/Source/Specs/model.oddDecl.xml b/P5/Source/Specs/model.oddDecl.xml index fcde75c52a..6f90f2c7b6 100644 --- a/P5/Source/Specs/model.oddDecl.xml +++ b/P5/Source/Specs/model.oddDecl.xml @@ -1,11 +1,4 @@ - - + groups elements which generate declarations in some markup language in ODD documents. diff --git a/P5/Source/Specs/model.oddRef.xml b/P5/Source/Specs/model.oddRef.xml index c495deef4b..5071985070 100644 --- a/P5/Source/Specs/model.oddRef.xml +++ b/P5/Source/Specs/model.oddRef.xml @@ -1,11 +1,4 @@ - - + groups elements which reference declarations in some markup language in ODD documents. diff --git a/P5/Source/Specs/model.offsetLike.xml b/P5/Source/Specs/model.offsetLike.xml index e669c6e819..a00aa1cfe9 100644 --- a/P5/Source/Specs/model.offsetLike.xml +++ b/P5/Source/Specs/model.offsetLike.xml @@ -1,11 +1,4 @@ - - + groups elements which can appear only as part of a place name. diff --git a/P5/Source/Specs/model.orgPart.xml b/P5/Source/Specs/model.orgPart.xml index 04bce9960c..0d97c3f0b5 100644 --- a/P5/Source/Specs/model.orgPart.xml +++ b/P5/Source/Specs/model.orgPart.xml @@ -1,11 +1,4 @@ - - + groups elements which form part of the description of an diff --git a/P5/Source/Specs/model.orgStateLike.xml b/P5/Source/Specs/model.orgStateLike.xml index 2c83dd4173..17cb8daf6c 100644 --- a/P5/Source/Specs/model.orgStateLike.xml +++ b/P5/Source/Specs/model.orgStateLike.xml @@ -1,11 +1,4 @@ - - + groups elements describing changeable characteristics of an organization which have a diff --git a/P5/Source/Specs/model.pLike.front.xml b/P5/Source/Specs/model.pLike.front.xml index 39dd6f603b..5ed337cc1a 100644 --- a/P5/Source/Specs/model.pLike.front.xml +++ b/P5/Source/Specs/model.pLike.front.xml @@ -1,11 +1,4 @@ - - + groups paragraph-like elements which can occur as direct constituents of front matter. diff --git a/P5/Source/Specs/model.pLike.xml b/P5/Source/Specs/model.pLike.xml index 75995b415c..acc1d35a36 100644 --- a/P5/Source/Specs/model.pLike.xml +++ b/P5/Source/Specs/model.pLike.xml @@ -1,11 +1,4 @@ - - + groups paragraph-like elements. diff --git a/P5/Source/Specs/model.pPart.data.xml b/P5/Source/Specs/model.pPart.data.xml index c85b685050..bdd8acf840 100644 --- a/P5/Source/Specs/model.pPart.data.xml +++ b/P5/Source/Specs/model.pPart.data.xml @@ -1,11 +1,4 @@ - - + groups phrase-level elements containing names, dates, numbers, measures, and similar data. diff --git a/P5/Source/Specs/model.pPart.edit.xml b/P5/Source/Specs/model.pPart.edit.xml index 0242090461..f1906e500a 100644 --- a/P5/Source/Specs/model.pPart.edit.xml +++ b/P5/Source/Specs/model.pPart.edit.xml @@ -1,11 +1,4 @@ - - + groups phrase-level elements for simple editorial correction and transcription. diff --git a/P5/Source/Specs/model.pPart.editorial.xml b/P5/Source/Specs/model.pPart.editorial.xml index a1d119dbe4..f01cdcb0de 100644 --- a/P5/Source/Specs/model.pPart.editorial.xml +++ b/P5/Source/Specs/model.pPart.editorial.xml @@ -1,11 +1,4 @@ - - + groups phrase-level elements for simple editorial interventions that may be useful both diff --git a/P5/Source/Specs/model.pPart.msdesc.xml b/P5/Source/Specs/model.pPart.msdesc.xml index 608aaa0f94..bf597ac580 100644 --- a/P5/Source/Specs/model.pPart.msdesc.xml +++ b/P5/Source/Specs/model.pPart.msdesc.xml @@ -1,11 +1,4 @@ - - + groups phrase-level elements used in manuscript description. diff --git a/P5/Source/Specs/model.pPart.transcriptional.xml b/P5/Source/Specs/model.pPart.transcriptional.xml index 2ae2eb9b2a..03ce7fbfe8 100644 --- a/P5/Source/Specs/model.pPart.transcriptional.xml +++ b/P5/Source/Specs/model.pPart.transcriptional.xml @@ -1,11 +1,4 @@ - - + groups phrase-level elements used for editorial transcription of pre-existing source diff --git a/P5/Source/Specs/model.paraPart.xml b/P5/Source/Specs/model.paraPart.xml index 7ea160c1d1..b593f26b43 100644 --- a/P5/Source/Specs/model.paraPart.xml +++ b/P5/Source/Specs/model.paraPart.xml @@ -1,11 +1,4 @@ - - + groups elements that may appear in paragraphs and similar elements diff --git a/P5/Source/Specs/model.persNamePart.xml b/P5/Source/Specs/model.persNamePart.xml index 58cea70614..d1c52cbda0 100644 --- a/P5/Source/Specs/model.persNamePart.xml +++ b/P5/Source/Specs/model.persNamePart.xml @@ -1,11 +1,4 @@ - - + groups elements which form part of a personal name. diff --git a/P5/Source/Specs/model.persStateLike.xml b/P5/Source/Specs/model.persStateLike.xml index 97814c8636..3749a55a8b 100644 --- a/P5/Source/Specs/model.persStateLike.xml +++ b/P5/Source/Specs/model.persStateLike.xml @@ -1,11 +1,4 @@ - - + groups elements describing changeable characteristics of a person which have a definite diff --git a/P5/Source/Specs/model.personLike.xml b/P5/Source/Specs/model.personLike.xml index e063f11388..c5e0d466dc 100644 --- a/P5/Source/Specs/model.personLike.xml +++ b/P5/Source/Specs/model.personLike.xml @@ -1,11 +1,4 @@ - - + groups elements which provide information about people and their relationships. diff --git a/P5/Source/Specs/model.personPart.xml b/P5/Source/Specs/model.personPart.xml index baad6b7d18..7a526ee0e0 100644 --- a/P5/Source/Specs/model.personPart.xml +++ b/P5/Source/Specs/model.personPart.xml @@ -1,11 +1,4 @@ - - + groups elements which form part of the description of a person. diff --git a/P5/Source/Specs/model.phrase.xml b/P5/Source/Specs/model.phrase.xml index baf3ba6770..26e5a5c08b 100644 --- a/P5/Source/Specs/model.phrase.xml +++ b/P5/Source/Specs/model.phrase.xml @@ -1,11 +1,4 @@ - - + groups elements which can occur at the level of individual words or phrases. diff --git a/P5/Source/Specs/model.phrase.xml.xml b/P5/Source/Specs/model.phrase.xml.xml index f290a08970..5ab4b83846 100644 --- a/P5/Source/Specs/model.phrase.xml.xml +++ b/P5/Source/Specs/model.phrase.xml.xml @@ -1,11 +1,4 @@ - - + groups phrase-level elements used to encode XML constructs such as element names, attribute diff --git a/P5/Source/Specs/model.physDescPart.xml b/P5/Source/Specs/model.physDescPart.xml index e180f81ee1..c349770cbf 100644 --- a/P5/Source/Specs/model.physDescPart.xml +++ b/P5/Source/Specs/model.physDescPart.xml @@ -1,11 +1,4 @@ - - + diff --git a/P5/Source/Specs/model.placeLike.xml b/P5/Source/Specs/model.placeLike.xml index 02f7ecfa49..3dc27043b9 100644 --- a/P5/Source/Specs/model.placeLike.xml +++ b/P5/Source/Specs/model.placeLike.xml @@ -1,11 +1,4 @@ - - + groups elements used to provide information about places and their relationships. diff --git a/P5/Source/Specs/model.placeNamePart.xml b/P5/Source/Specs/model.placeNamePart.xml index 1bc882fd3a..6580f89223 100644 --- a/P5/Source/Specs/model.placeNamePart.xml +++ b/P5/Source/Specs/model.placeNamePart.xml @@ -1,11 +1,4 @@ - - + groups elements which form part of a place name. diff --git a/P5/Source/Specs/model.placeStateLike.xml b/P5/Source/Specs/model.placeStateLike.xml index 364180593e..c5b08f4451 100644 --- a/P5/Source/Specs/model.placeStateLike.xml +++ b/P5/Source/Specs/model.placeStateLike.xml @@ -1,11 +1,4 @@ - - + groups elements which describe changing states of a place. diff --git a/P5/Source/Specs/model.profileDescPart.xml b/P5/Source/Specs/model.profileDescPart.xml index cba998ec0f..d744a63fb5 100644 --- a/P5/Source/Specs/model.profileDescPart.xml +++ b/P5/Source/Specs/model.profileDescPart.xml @@ -1,11 +1,4 @@ - - + groups elements which may be used inside profileDesc diff --git a/P5/Source/Specs/model.ptrLike.form.xml b/P5/Source/Specs/model.ptrLike.form.xml index 86a9143dc7..7b597902b3 100644 --- a/P5/Source/Specs/model.ptrLike.form.xml +++ b/P5/Source/Specs/model.ptrLike.form.xml @@ -1,11 +1,4 @@ - - + groups elements used for purposes of location of particular orthographic or pronunciation diff --git a/P5/Source/Specs/model.ptrLike.xml b/P5/Source/Specs/model.ptrLike.xml index e956afd057..7a4d193a66 100644 --- a/P5/Source/Specs/model.ptrLike.xml +++ b/P5/Source/Specs/model.ptrLike.xml @@ -1,11 +1,4 @@ - - + groups elements used for purposes of location and reference. diff --git a/P5/Source/Specs/model.publicationStmtPart.agency.xml b/P5/Source/Specs/model.publicationStmtPart.agency.xml index ba75c8a844..d955608d5c 100644 --- a/P5/Source/Specs/model.publicationStmtPart.agency.xml +++ b/P5/Source/Specs/model.publicationStmtPart.agency.xml @@ -1,11 +1,4 @@ - - + groups the child diff --git a/P5/Source/Specs/model.publicationStmtPart.detail.xml b/P5/Source/Specs/model.publicationStmtPart.detail.xml index 42565d0c80..7392139710 100644 --- a/P5/Source/Specs/model.publicationStmtPart.detail.xml +++ b/P5/Source/Specs/model.publicationStmtPart.detail.xml @@ -1,11 +1,4 @@ - - + groups the agency-specific child elements of the publicationStmt element of the TEI header. diff --git a/P5/Source/Specs/model.quoteLike.xml b/P5/Source/Specs/model.quoteLike.xml index ad3e6eef43..588084aa88 100644 --- a/P5/Source/Specs/model.quoteLike.xml +++ b/P5/Source/Specs/model.quoteLike.xml @@ -1,11 +1,4 @@ - - + groups elements used to directly contain quotations. diff --git a/P5/Source/Specs/model.rdgLike.xml b/P5/Source/Specs/model.rdgLike.xml index 560e6c2908..de9acb1da0 100644 --- a/P5/Source/Specs/model.rdgLike.xml +++ b/P5/Source/Specs/model.rdgLike.xml @@ -1,11 +1,4 @@ - - + groups elements which contain a single reading, other than the lemma, within a textual diff --git a/P5/Source/Specs/model.rdgPart.xml b/P5/Source/Specs/model.rdgPart.xml index aa74a30e71..8f1f3bca3d 100644 --- a/P5/Source/Specs/model.rdgPart.xml +++ b/P5/Source/Specs/model.rdgPart.xml @@ -1,11 +1,4 @@ - - + groups elements which mark the beginning or ending of a fragmentary manuscript or other diff --git a/P5/Source/Specs/model.recordingPart.xml b/P5/Source/Specs/model.recordingPart.xml index 7a38e29433..6d84cc11a5 100644 --- a/P5/Source/Specs/model.recordingPart.xml +++ b/P5/Source/Specs/model.recordingPart.xml @@ -1,11 +1,4 @@ - - + groups elements used to describe details of an audio or video recording. diff --git a/P5/Source/Specs/model.resource.xml b/P5/Source/Specs/model.resource.xml index 7fcfcf4030..d0b5370a6f 100644 --- a/P5/Source/Specs/model.resource.xml +++ b/P5/Source/Specs/model.resource.xml @@ -1,11 +1,4 @@ - - + groups separate elements diff --git a/P5/Source/Specs/model.respLike.xml b/P5/Source/Specs/model.respLike.xml index 9f265d8104..b4beb3d50c 100644 --- a/P5/Source/Specs/model.respLike.xml +++ b/P5/Source/Specs/model.respLike.xml @@ -1,11 +1,4 @@ - - + groups elements which are used to indicate intellectual or other significant responsibility, diff --git a/P5/Source/Specs/model.segLike.xml b/P5/Source/Specs/model.segLike.xml index 6509ebac88..d5601a7ef3 100644 --- a/P5/Source/Specs/model.segLike.xml +++ b/P5/Source/Specs/model.segLike.xml @@ -1,11 +1,4 @@ - - + groups elements used for arbitrary segmentation. diff --git a/P5/Source/Specs/model.settingPart.xml b/P5/Source/Specs/model.settingPart.xml index b937ea3e65..e1c86d8482 100644 --- a/P5/Source/Specs/model.settingPart.xml +++ b/P5/Source/Specs/model.settingPart.xml @@ -1,11 +1,4 @@ - - + groups elements used to describe the setting of a linguistic interaction. diff --git a/P5/Source/Specs/model.sourceDescPart.xml b/P5/Source/Specs/model.sourceDescPart.xml index 97bde75630..cd404efdf7 100644 --- a/P5/Source/Specs/model.sourceDescPart.xml +++ b/P5/Source/Specs/model.sourceDescPart.xml @@ -1,11 +1,4 @@ - - + groups elements which may be used inside sourceDesc and appear multiple times. diff --git a/P5/Source/Specs/model.specDescLike.xml b/P5/Source/Specs/model.specDescLike.xml index 8113e35251..b2d7d0f8b2 100644 --- a/P5/Source/Specs/model.specDescLike.xml +++ b/P5/Source/Specs/model.specDescLike.xml @@ -1,11 +1,4 @@ - - + groups elements for referring to specification elements. diff --git a/P5/Source/Specs/model.stageLike.xml b/P5/Source/Specs/model.stageLike.xml index 9d3e15a64f..900ada33b0 100644 --- a/P5/Source/Specs/model.stageLike.xml +++ b/P5/Source/Specs/model.stageLike.xml @@ -1,11 +1,4 @@ - - + groups elements containing stage directions or similar things defined by the module for diff --git a/P5/Source/Specs/model.standOffPart.xml b/P5/Source/Specs/model.standOffPart.xml index a13d76c2b5..11c0b46a9b 100644 --- a/P5/Source/Specs/model.standOffPart.xml +++ b/P5/Source/Specs/model.standOffPart.xml @@ -1,11 +1,4 @@ - - + groups elements which may be used as children of standOff. diff --git a/P5/Source/Specs/model.teiHeaderPart.xml b/P5/Source/Specs/model.teiHeaderPart.xml index 0d3d13eb0f..2991c623b8 100644 --- a/P5/Source/Specs/model.teiHeaderPart.xml +++ b/P5/Source/Specs/model.teiHeaderPart.xml @@ -1,11 +1,4 @@ - - + groups high level elements which may appear more than once in a TEI header. diff --git a/P5/Source/Specs/model.textDescPart.xml b/P5/Source/Specs/model.textDescPart.xml index aa17586653..78120f80d3 100644 --- a/P5/Source/Specs/model.textDescPart.xml +++ b/P5/Source/Specs/model.textDescPart.xml @@ -1,11 +1,4 @@ - - + diff --git a/P5/Source/Specs/model.titlepagePart.xml b/P5/Source/Specs/model.titlepagePart.xml index 47ed12300d..4534cbe3b5 100644 --- a/P5/Source/Specs/model.titlepagePart.xml +++ b/P5/Source/Specs/model.titlepagePart.xml @@ -1,11 +1,4 @@ - - + groups elements which can occur as direct constituents of a title page, such as diff --git a/P5/Source/Specs/model.xml b/P5/Source/Specs/model.xml index 636ebc63f1..31fe8a749d 100644 --- a/P5/Source/Specs/model.xml +++ b/P5/Source/Specs/model.xml @@ -1,11 +1,4 @@ - - + describes the processing intended for a specified diff --git a/P5/Source/Specs/modelGrp.xml b/P5/Source/Specs/modelGrp.xml index 15f897bb36..7267ad191c 100644 --- a/P5/Source/Specs/modelGrp.xml +++ b/P5/Source/Specs/modelGrp.xml @@ -1,11 +1,4 @@ - - + model group diff --git a/P5/Source/Specs/modelSequence.xml b/P5/Source/Specs/modelSequence.xml index cbd5e51ba6..b76bfdfa97 100644 --- a/P5/Source/Specs/modelSequence.xml +++ b/P5/Source/Specs/modelSequence.xml @@ -1,11 +1,4 @@ - - + any sequence of model or modelSequence elements which diff --git a/P5/Source/Specs/moduleRef.xml b/P5/Source/Specs/moduleRef.xml index 2c1e52ba10..65d7c7be4d 100644 --- a/P5/Source/Specs/moduleRef.xml +++ b/P5/Source/Specs/moduleRef.xml @@ -1,11 +1,4 @@ - - + module reference diff --git a/P5/Source/Specs/moduleSpec.xml b/P5/Source/Specs/moduleSpec.xml index 9d46eaa7f4..433fb78ebc 100644 --- a/P5/Source/Specs/moduleSpec.xml +++ b/P5/Source/Specs/moduleSpec.xml @@ -1,11 +1,4 @@ - - + module specification diff --git a/P5/Source/Specs/monogr.xml b/P5/Source/Specs/monogr.xml index c7ddd4f8bc..b14dc8c461 100644 --- a/P5/Source/Specs/monogr.xml +++ b/P5/Source/Specs/monogr.xml @@ -1,11 +1,4 @@ - - + monographic level diff --git a/P5/Source/Specs/mood.xml b/P5/Source/Specs/mood.xml index 304b0145a4..29b642a98e 100644 --- a/P5/Source/Specs/mood.xml +++ b/P5/Source/Specs/mood.xml @@ -1,11 +1,4 @@ - - + mood diff --git a/P5/Source/Specs/move.xml b/P5/Source/Specs/move.xml index 3ea4db9a47..56ba897744 100644 --- a/P5/Source/Specs/move.xml +++ b/P5/Source/Specs/move.xml @@ -1,11 +1,4 @@ - - + movement diff --git a/P5/Source/Specs/msContents.xml b/P5/Source/Specs/msContents.xml index 8dca42b0cf..73c08df756 100644 --- a/P5/Source/Specs/msContents.xml +++ b/P5/Source/Specs/msContents.xml @@ -1,11 +1,4 @@ - - + manuscript contents diff --git a/P5/Source/Specs/msDesc.xml b/P5/Source/Specs/msDesc.xml index f15468cf8c..da8621afd2 100644 --- a/P5/Source/Specs/msDesc.xml +++ b/P5/Source/Specs/msDesc.xml @@ -1,11 +1,4 @@ - - + manuscript description diff --git a/P5/Source/Specs/msFrag.xml b/P5/Source/Specs/msFrag.xml index 683ad8e813..ecf91cb7a6 100644 --- a/P5/Source/Specs/msFrag.xml +++ b/P5/Source/Specs/msFrag.xml @@ -1,11 +1,4 @@ - - + manuscript fragment diff --git a/P5/Source/Specs/msIdentifier.xml b/P5/Source/Specs/msIdentifier.xml index 6fa7e4a4d2..508a745707 100644 --- a/P5/Source/Specs/msIdentifier.xml +++ b/P5/Source/Specs/msIdentifier.xml @@ -1,11 +1,4 @@ - - + manuscript identifier diff --git a/P5/Source/Specs/msItem.xml b/P5/Source/Specs/msItem.xml index 6b18d25a95..a27ab89b98 100644 --- a/P5/Source/Specs/msItem.xml +++ b/P5/Source/Specs/msItem.xml @@ -1,11 +1,4 @@ - - + manuscript item diff --git a/P5/Source/Specs/msItemStruct.xml b/P5/Source/Specs/msItemStruct.xml index 33c554110c..98f6a26bb3 100644 --- a/P5/Source/Specs/msItemStruct.xml +++ b/P5/Source/Specs/msItemStruct.xml @@ -1,11 +1,4 @@ - - + structured manuscript item diff --git a/P5/Source/Specs/msName.xml b/P5/Source/Specs/msName.xml index bc60809960..eadcc467ee 100644 --- a/P5/Source/Specs/msName.xml +++ b/P5/Source/Specs/msName.xml @@ -1,11 +1,4 @@ - - + alternative name diff --git a/P5/Source/Specs/msPart.xml b/P5/Source/Specs/msPart.xml index 9399926215..26a51986f2 100644 --- a/P5/Source/Specs/msPart.xml +++ b/P5/Source/Specs/msPart.xml @@ -1,11 +1,4 @@ - - + manuscript part diff --git a/P5/Source/Specs/musicNotation.xml b/P5/Source/Specs/musicNotation.xml index 7a23aa5aed..ab05959f7c 100644 --- a/P5/Source/Specs/musicNotation.xml +++ b/P5/Source/Specs/musicNotation.xml @@ -1,11 +1,4 @@ - - + music notation diff --git a/P5/Source/Specs/name.xml b/P5/Source/Specs/name.xml index 13deaf9f82..6c70961cc5 100644 --- a/P5/Source/Specs/name.xml +++ b/P5/Source/Specs/name.xml @@ -1,10 +1,4 @@ - + name, proper noun 이름, 고유명사 名稱，特定名稱 diff --git a/P5/Source/Specs/nameLink.xml b/P5/Source/Specs/nameLink.xml index 56dc6a1276..e01796e8b1 100644 --- a/P5/Source/Specs/nameLink.xml +++ b/P5/Source/Specs/nameLink.xml @@ -1,11 +1,4 @@ - - + name link diff --git a/P5/Source/Specs/namespace.xml b/P5/Source/Specs/namespace.xml index b829366ced..910c90ea44 100644 --- a/P5/Source/Specs/namespace.xml +++ b/P5/Source/Specs/namespace.xml @@ -1,11 +1,4 @@ - - + namespace diff --git a/P5/Source/Specs/nationality.xml b/P5/Source/Specs/nationality.xml index 41a093ac89..a308adf8f4 100644 --- a/P5/Source/Specs/nationality.xml +++ b/P5/Source/Specs/nationality.xml @@ -1,10 +1,4 @@ - + nationality nationalité contains an informal description of a person's present or past nationality or citizenship. diff --git a/P5/Source/Specs/node.xml b/P5/Source/Specs/node.xml index b529b32160..9396e9c03b 100644 --- a/P5/Source/Specs/node.xml +++ b/P5/Source/Specs/node.xml @@ -1,11 +1,4 @@ - - + node diff --git a/P5/Source/Specs/normalization.xml b/P5/Source/Specs/normalization.xml index 42727bba0b..b97117e589 100644 --- a/P5/Source/Specs/normalization.xml +++ b/P5/Source/Specs/normalization.xml @@ -1,11 +1,4 @@ - - + normalization diff --git a/P5/Source/Specs/notatedMusic.xml b/P5/Source/Specs/notatedMusic.xml index 0a2be5e113..a9d62e1b9c 100644 --- a/P5/Source/Specs/notatedMusic.xml +++ b/P5/Source/Specs/notatedMusic.xml @@ -1,11 +1,4 @@ - - + encodes the presence of music notation in a text diff --git a/P5/Source/Specs/note.xml b/P5/Source/Specs/note.xml index 93a06cd96f..0798511e1a 100644 --- a/P5/Source/Specs/note.xml +++ b/P5/Source/Specs/note.xml @@ -1,11 +1,4 @@ - - + note diff --git a/P5/Source/Specs/noteGrp.xml b/P5/Source/Specs/noteGrp.xml index a8d179bc64..63489d1d0a 100644 --- a/P5/Source/Specs/noteGrp.xml +++ b/P5/Source/Specs/noteGrp.xml @@ -1,10 +1,4 @@ - + note group contains a group of notes diff --git a/P5/Source/Specs/notesStmt.xml b/P5/Source/Specs/notesStmt.xml index 33e32507d4..4bbcd6a711 100644 --- a/P5/Source/Specs/notesStmt.xml +++ b/P5/Source/Specs/notesStmt.xml @@ -1,11 +1,4 @@ - - + notes statement diff --git a/P5/Source/Specs/num.xml b/P5/Source/Specs/num.xml index 8c81162640..c0786c0062 100644 --- a/P5/Source/Specs/num.xml +++ b/P5/Source/Specs/num.xml @@ -1,11 +1,4 @@ - - + number diff --git a/P5/Source/Specs/number.xml b/P5/Source/Specs/number.xml index 1d6536c640..63446c5ead 100644 --- a/P5/Source/Specs/number.xml +++ b/P5/Source/Specs/number.xml @@ -1,11 +1,4 @@ - - + number diff --git a/P5/Source/Specs/numeric.xml b/P5/Source/Specs/numeric.xml index 46c26c179c..61dd6cedce 100644 --- a/P5/Source/Specs/numeric.xml +++ b/P5/Source/Specs/numeric.xml @@ -1,11 +1,4 @@ - - + numeric value diff --git a/P5/Source/Specs/nym.xml b/P5/Source/Specs/nym.xml index 13dc85b6a9..5e49136cad 100644 --- a/P5/Source/Specs/nym.xml +++ b/P5/Source/Specs/nym.xml @@ -1,11 +1,4 @@ - - + canonical name diff --git a/P5/Source/Specs/oRef.xml b/P5/Source/Specs/oRef.xml index 616c7e37d8..5a5608fcdb 100644 --- a/P5/Source/Specs/oRef.xml +++ b/P5/Source/Specs/oRef.xml @@ -1,11 +1,4 @@ - - + orthographic-form reference diff --git a/P5/Source/Specs/object.xml b/P5/Source/Specs/object.xml index ef1b06766a..1d49e2339c 100644 --- a/P5/Source/Specs/object.xml +++ b/P5/Source/Specs/object.xml @@ -1,10 +1,4 @@ - + contains a description of a single identifiable physical object. enthält die Beschreibung eines einzelnen identifizierbaren physischen Objekts. diff --git a/P5/Source/Specs/objectDesc.xml b/P5/Source/Specs/objectDesc.xml index 12814fd5bb..f3367b7fe6 100644 --- a/P5/Source/Specs/objectDesc.xml +++ b/P5/Source/Specs/objectDesc.xml @@ -1,11 +1,4 @@ - - + object description diff --git a/P5/Source/Specs/objectIdentifier.xml b/P5/Source/Specs/objectIdentifier.xml index 73ad199656..04a17e9922 100644 --- a/P5/Source/Specs/objectIdentifier.xml +++ b/P5/Source/Specs/objectIdentifier.xml @@ -1,10 +1,4 @@ - + object identifier Objektidentifikator diff --git a/P5/Source/Specs/objectName.xml b/P5/Source/Specs/objectName.xml index 4afb2ee24d..d53f53b8af 100644 --- a/P5/Source/Specs/objectName.xml +++ b/P5/Source/Specs/objectName.xml @@ -1,10 +1,4 @@ - + name of an object Name eines Objekts contains a proper noun or noun phrase used to refer to an object. diff --git a/P5/Source/Specs/objectType.xml b/P5/Source/Specs/objectType.xml index 87b6bdc7b4..e8db622519 100644 --- a/P5/Source/Specs/objectType.xml +++ b/P5/Source/Specs/objectType.xml @@ -1,11 +1,4 @@ - - + object type diff --git a/P5/Source/Specs/occupation.xml b/P5/Source/Specs/occupation.xml index daf711c415..59416ab32e 100644 --- a/P5/Source/Specs/occupation.xml +++ b/P5/Source/Specs/occupation.xml @@ -1,10 +1,4 @@ - + occupation activité contains an informal description of a person's trade, profession or occupation. diff --git a/P5/Source/Specs/offset.xml b/P5/Source/Specs/offset.xml index a4940b9d5f..4014780b5a 100644 --- a/P5/Source/Specs/offset.xml +++ b/P5/Source/Specs/offset.xml @@ -1,10 +1,4 @@ - + offset distance relative marks that part of a relative temporal or spatial expression which indicates the direction of the offset between the two place names, dates, or diff --git a/P5/Source/Specs/opener.xml b/P5/Source/Specs/opener.xml index 7b663ad345..ec89c7d444 100644 --- a/P5/Source/Specs/opener.xml +++ b/P5/Source/Specs/opener.xml @@ -1,11 +1,4 @@ - - + opener diff --git a/P5/Source/Specs/org.xml b/P5/Source/Specs/org.xml index e5423df3b8..cccb50a29c 100644 --- a/P5/Source/Specs/org.xml +++ b/P5/Source/Specs/org.xml @@ -1,11 +1,4 @@ - - + organization diff --git a/P5/Source/Specs/orgName.xml b/P5/Source/Specs/orgName.xml index d5dcca0617..0afffd8701 100644 --- a/P5/Source/Specs/orgName.xml +++ b/P5/Source/Specs/orgName.xml @@ -1,10 +1,4 @@ - + organization name 조직명 組織名稱 diff --git a/P5/Source/Specs/orig.xml b/P5/Source/Specs/orig.xml index d9caf97eb8..9c049b722f 100644 --- a/P5/Source/Specs/orig.xml +++ b/P5/Source/Specs/orig.xml @@ -1,11 +1,4 @@ - - + original form diff --git a/P5/Source/Specs/origDate.xml b/P5/Source/Specs/origDate.xml index d6ca446f25..b91153b077 100644 --- a/P5/Source/Specs/origDate.xml +++ b/P5/Source/Specs/origDate.xml @@ -1,11 +1,4 @@ - - + origin date diff --git a/P5/Source/Specs/origPlace.xml b/P5/Source/Specs/origPlace.xml index 286a02d69b..a112425a27 100644 --- a/P5/Source/Specs/origPlace.xml +++ b/P5/Source/Specs/origPlace.xml @@ -1,10 +1,4 @@ - + origin place 생산 장소 diff --git a/P5/Source/Specs/origin.xml b/P5/Source/Specs/origin.xml index 80ef7fcd00..cb7d9560e7 100644 --- a/P5/Source/Specs/origin.xml +++ b/P5/Source/Specs/origin.xml @@ -1,10 +1,4 @@ - + origin origine contains any descriptive or other information diff --git a/P5/Source/Specs/orth.xml b/P5/Source/Specs/orth.xml index 48b90b3984..eb9172b5b7 100644 --- a/P5/Source/Specs/orth.xml +++ b/P5/Source/Specs/orth.xml @@ -1,11 +1,4 @@ - - + orthographic form diff --git a/P5/Source/Specs/outputRendition.xml b/P5/Source/Specs/outputRendition.xml index 4d13201301..9bdaeffe86 100644 --- a/P5/Source/Specs/outputRendition.xml +++ b/P5/Source/Specs/outputRendition.xml @@ -1,11 +1,4 @@ - - + diff --git a/P5/Source/Specs/p.xml b/P5/Source/Specs/p.xml index 1bf9c34e77..e1b14d504b 100644 --- a/P5/Source/Specs/p.xml +++ b/P5/Source/Specs/p.xml @@ -1,11 +1,4 @@ - - + paragraph diff --git a/P5/Source/Specs/pRef.xml b/P5/Source/Specs/pRef.xml index b66f7ad71c..68ea99eb49 100644 --- a/P5/Source/Specs/pRef.xml +++ b/P5/Source/Specs/pRef.xml @@ -1,11 +1,4 @@ - - + pronunciation reference diff --git a/P5/Source/Specs/param.xml b/P5/Source/Specs/param.xml index 9a45e044f4..4eec04bfbd 100644 --- a/P5/Source/Specs/param.xml +++ b/P5/Source/Specs/param.xml @@ -1,11 +1,4 @@ - - + provides a parameter for a model behaviour by diff --git a/P5/Source/Specs/paramList.xml b/P5/Source/Specs/paramList.xml index 9d457462a7..1824691268 100644 --- a/P5/Source/Specs/paramList.xml +++ b/P5/Source/Specs/paramList.xml @@ -1,11 +1,4 @@ - - + list of parameter specifications diff --git a/P5/Source/Specs/paramSpec.xml b/P5/Source/Specs/paramSpec.xml index 14aabaa225..3e5f7daead 100644 --- a/P5/Source/Specs/paramSpec.xml +++ b/P5/Source/Specs/paramSpec.xml @@ -1,11 +1,4 @@ - - + supplies specification for one parameter of a model diff --git a/P5/Source/Specs/particDesc.xml b/P5/Source/Specs/particDesc.xml index a64f75e8be..0e2b6df990 100644 --- a/P5/Source/Specs/particDesc.xml +++ b/P5/Source/Specs/particDesc.xml @@ -1,11 +1,4 @@ - - + participation description diff --git a/P5/Source/Specs/path.xml b/P5/Source/Specs/path.xml index 8f9ec73136..bc6af60964 100644 --- a/P5/Source/Specs/path.xml +++ b/P5/Source/Specs/path.xml @@ -1,11 +1,4 @@ - - + path diff --git a/P5/Source/Specs/pause.xml b/P5/Source/Specs/pause.xml index 231b29aa00..263008f955 100644 --- a/P5/Source/Specs/pause.xml +++ b/P5/Source/Specs/pause.xml @@ -1,11 +1,4 @@ - - + pause diff --git a/P5/Source/Specs/pb.xml b/P5/Source/Specs/pb.xml index 0128120334..e4b83b5881 100644 --- a/P5/Source/Specs/pb.xml +++ b/P5/Source/Specs/pb.xml @@ -1,11 +1,4 @@ - - + page beginning diff --git a/P5/Source/Specs/pc.xml b/P5/Source/Specs/pc.xml index 2d5c970f89..84f5b40628 100644 --- a/P5/Source/Specs/pc.xml +++ b/P5/Source/Specs/pc.xml @@ -1,11 +1,4 @@ - - + punctuation character diff --git a/P5/Source/Specs/per.xml b/P5/Source/Specs/per.xml index 0016c2a374..b4d9299b45 100644 --- a/P5/Source/Specs/per.xml +++ b/P5/Source/Specs/per.xml @@ -1,11 +1,4 @@ - - + diff --git a/P5/Source/Specs/performance.xml b/P5/Source/Specs/performance.xml index 0e392fb01a..49bf2edd14 100644 --- a/P5/Source/Specs/performance.xml +++ b/P5/Source/Specs/performance.xml @@ -1,11 +1,4 @@ - - + performance diff --git a/P5/Source/Specs/persName.xml b/P5/Source/Specs/persName.xml index e670a2d5a9..25c76698ad 100644 --- a/P5/Source/Specs/persName.xml +++ b/P5/Source/Specs/persName.xml @@ -1,10 +1,4 @@ - + personal name 개인 이름 個人名稱 diff --git a/P5/Source/Specs/persPronouns.xml b/P5/Source/Specs/persPronouns.xml index 6f4b4f59f5..e2e65c67fe 100644 --- a/P5/Source/Specs/persPronouns.xml +++ b/P5/Source/Specs/persPronouns.xml @@ -1,10 +1,4 @@ - + personal pronouns indicates the personal pronouns used, or assumed to be used, by the individual being described. diff --git a/P5/Source/Specs/person.xml b/P5/Source/Specs/person.xml index 233e6cfd3d..64eef6dcd0 100644 --- a/P5/Source/Specs/person.xml +++ b/P5/Source/Specs/person.xml @@ -1,11 +1,4 @@ - - + person diff --git a/P5/Source/Specs/personGrp.xml b/P5/Source/Specs/personGrp.xml index defdf630e8..5e1ec78f8d 100644 --- a/P5/Source/Specs/personGrp.xml +++ b/P5/Source/Specs/personGrp.xml @@ -1,11 +1,4 @@ - - + personal group diff --git a/P5/Source/Specs/persona.xml b/P5/Source/Specs/persona.xml index f4ac55b3cd..91a38e340a 100644 --- a/P5/Source/Specs/persona.xml +++ b/P5/Source/Specs/persona.xml @@ -1,11 +1,4 @@ - - + provides information about one of the personalities identified for a given individual, where diff --git a/P5/Source/Specs/phr.xml b/P5/Source/Specs/phr.xml index 235afbe19e..83de82fd78 100644 --- a/P5/Source/Specs/phr.xml +++ b/P5/Source/Specs/phr.xml @@ -1,11 +1,4 @@ - - + phrase diff --git a/P5/Source/Specs/physDesc.xml b/P5/Source/Specs/physDesc.xml index d47e1c1a4a..94685466e1 100644 --- a/P5/Source/Specs/physDesc.xml +++ b/P5/Source/Specs/physDesc.xml @@ -1,11 +1,4 @@ - - + physical description diff --git a/P5/Source/Specs/place.xml b/P5/Source/Specs/place.xml index 26f8798cd5..ec9b883172 100644 --- a/P5/Source/Specs/place.xml +++ b/P5/Source/Specs/place.xml @@ -1,11 +1,4 @@ - - + place diff --git a/P5/Source/Specs/placeName.xml b/P5/Source/Specs/placeName.xml index 48ee8c47a9..8f1da61e5a 100644 --- a/P5/Source/Specs/placeName.xml +++ b/P5/Source/Specs/placeName.xml @@ -1,10 +1,4 @@ - + place name nom de lieu contains an absolute or relative place name. diff --git a/P5/Source/Specs/population.xml b/P5/Source/Specs/population.xml index 410b82b6bf..c7345cd428 100644 --- a/P5/Source/Specs/population.xml +++ b/P5/Source/Specs/population.xml @@ -1,10 +1,4 @@ - + population population contains information about the population of a place. diff --git a/P5/Source/Specs/pos.xml b/P5/Source/Specs/pos.xml index 8a381f7982..ac2037416d 100644 --- a/P5/Source/Specs/pos.xml +++ b/P5/Source/Specs/pos.xml @@ -1,11 +1,4 @@ - - + part of speech diff --git a/P5/Source/Specs/postBox.xml b/P5/Source/Specs/postBox.xml index 827ca90758..4eb7b47412 100644 --- a/P5/Source/Specs/postBox.xml +++ b/P5/Source/Specs/postBox.xml @@ -1,11 +1,4 @@ - - + postal box or post office box diff --git a/P5/Source/Specs/postCode.xml b/P5/Source/Specs/postCode.xml index 1e2e5016c3..8f6a3ec265 100644 --- a/P5/Source/Specs/postCode.xml +++ b/P5/Source/Specs/postCode.xml @@ -1,11 +1,4 @@ - - + postal code diff --git a/P5/Source/Specs/postscript.xml b/P5/Source/Specs/postscript.xml index b350289758..af2f6938f1 100644 --- a/P5/Source/Specs/postscript.xml +++ b/P5/Source/Specs/postscript.xml @@ -1,11 +1,4 @@ - - + contains a postscript, e.g. to a letter. diff --git a/P5/Source/Specs/precision.xml b/P5/Source/Specs/precision.xml index 8fecf29376..7d0f01dd2d 100644 --- a/P5/Source/Specs/precision.xml +++ b/P5/Source/Specs/precision.xml @@ -1,10 +1,4 @@ - + indicates the numerical accuracy or precision associated with some aspect of the text markup. diff --git a/P5/Source/Specs/prefixDef.xml b/P5/Source/Specs/prefixDef.xml index 53ae3aa73c..fce4879962 100644 --- a/P5/Source/Specs/prefixDef.xml +++ b/P5/Source/Specs/prefixDef.xml @@ -1,11 +1,4 @@ - - + prefix definition diff --git a/P5/Source/Specs/preparedness.xml b/P5/Source/Specs/preparedness.xml index d966a82185..0b2189fc40 100644 --- a/P5/Source/Specs/preparedness.xml +++ b/P5/Source/Specs/preparedness.xml @@ -1,11 +1,4 @@ - - + preparedness diff --git a/P5/Source/Specs/principal.xml b/P5/Source/Specs/principal.xml index edd5a71ba7..4c933f4431 100644 --- a/P5/Source/Specs/principal.xml +++ b/P5/Source/Specs/principal.xml @@ -1,10 +1,4 @@ - + principal researcher chercheur principal 책임 연구자 diff --git a/P5/Source/Specs/profileDesc.xml b/P5/Source/Specs/profileDesc.xml index af13139cee..fb11c233f7 100644 --- a/P5/Source/Specs/profileDesc.xml +++ b/P5/Source/Specs/profileDesc.xml @@ -1,11 +1,4 @@ - - + text-profile description diff --git a/P5/Source/Specs/projectDesc.xml b/P5/Source/Specs/projectDesc.xml index d40aecf0c9..c8e50f0b22 100644 --- a/P5/Source/Specs/projectDesc.xml +++ b/P5/Source/Specs/projectDesc.xml @@ -1,11 +1,4 @@ - - + project description diff --git a/P5/Source/Specs/prologue.xml b/P5/Source/Specs/prologue.xml index ef682277ab..947fdafd2d 100644 --- a/P5/Source/Specs/prologue.xml +++ b/P5/Source/Specs/prologue.xml @@ -1,11 +1,4 @@ - - + prologue diff --git a/P5/Source/Specs/pron.xml b/P5/Source/Specs/pron.xml index b37752e0f8..7a7d2424ea 100644 --- a/P5/Source/Specs/pron.xml +++ b/P5/Source/Specs/pron.xml @@ -1,11 +1,4 @@ - - + pronunciation diff --git a/P5/Source/Specs/provenance.xml b/P5/Source/Specs/provenance.xml index 90e6b89607..f201996069 100644 --- a/P5/Source/Specs/provenance.xml +++ b/P5/Source/Specs/provenance.xml @@ -1,10 +1,4 @@ - + provenance provenance contains any descriptive or other information diff --git a/P5/Source/Specs/ptr.xml b/P5/Source/Specs/ptr.xml index acebc97a7e..2fb1bf6c13 100644 --- a/P5/Source/Specs/ptr.xml +++ b/P5/Source/Specs/ptr.xml @@ -1,11 +1,4 @@ - - + pointer diff --git a/P5/Source/Specs/pubPlace.xml b/P5/Source/Specs/pubPlace.xml index 21ee7e1a29..ca26d0a9c2 100644 --- a/P5/Source/Specs/pubPlace.xml +++ b/P5/Source/Specs/pubPlace.xml @@ -1,11 +1,4 @@ - - + publication place diff --git a/P5/Source/Specs/publicationStmt.xml b/P5/Source/Specs/publicationStmt.xml index 5316a8b5de..37df6d2352 100644 --- a/P5/Source/Specs/publicationStmt.xml +++ b/P5/Source/Specs/publicationStmt.xml @@ -1,11 +1,4 @@ - - + publication statement diff --git a/P5/Source/Specs/publisher.xml b/P5/Source/Specs/publisher.xml index 7e850b1891..2037b6a70b 100644 --- a/P5/Source/Specs/publisher.xml +++ b/P5/Source/Specs/publisher.xml @@ -1,10 +1,4 @@ - + publisher editorial éditeur diff --git a/P5/Source/Specs/punctuation.xml b/P5/Source/Specs/punctuation.xml index c95640b945..93821375bc 100644 --- a/P5/Source/Specs/punctuation.xml +++ b/P5/Source/Specs/punctuation.xml @@ -1,11 +1,4 @@ - - + specifies editorial practice adopted with respect to punctuation marks in the original. diff --git a/P5/Source/Specs/purpose.xml b/P5/Source/Specs/purpose.xml index d34d95fbcf..9aee9bb848 100644 --- a/P5/Source/Specs/purpose.xml +++ b/P5/Source/Specs/purpose.xml @@ -1,11 +1,4 @@ - - + characterizes a single purpose or communicative function of the diff --git a/P5/Source/Specs/q.xml b/P5/Source/Specs/q.xml index 9b0e344e18..99fd3d39b6 100644 --- a/P5/Source/Specs/q.xml +++ b/P5/Source/Specs/q.xml @@ -1,11 +1,4 @@ - - + quoted diff --git a/P5/Source/Specs/quotation.xml b/P5/Source/Specs/quotation.xml index 92ad6dd141..1e124d2630 100644 --- a/P5/Source/Specs/quotation.xml +++ b/P5/Source/Specs/quotation.xml @@ -1,11 +1,4 @@ - - + quotation diff --git a/P5/Source/Specs/quote.xml b/P5/Source/Specs/quote.xml index ce7cf6b1df..36d43a000f 100644 --- a/P5/Source/Specs/quote.xml +++ b/P5/Source/Specs/quote.xml @@ -1,11 +1,4 @@ - - + quotation diff --git a/P5/Source/Specs/rb.xml b/P5/Source/Specs/rb.xml index d05c252eed..cffe1d7e11 100644 --- a/P5/Source/Specs/rb.xml +++ b/P5/Source/Specs/rb.xml @@ -1,11 +1,4 @@ - - + ruby base diff --git a/P5/Source/Specs/rdg.xml b/P5/Source/Specs/rdg.xml index 5dae28b179..519ed3a6a7 100644 --- a/P5/Source/Specs/rdg.xml +++ b/P5/Source/Specs/rdg.xml @@ -1,11 +1,4 @@ - - + reading diff --git a/P5/Source/Specs/rdgGrp.xml b/P5/Source/Specs/rdgGrp.xml index 72c65906b4..487da66324 100644 --- a/P5/Source/Specs/rdgGrp.xml +++ b/P5/Source/Specs/rdgGrp.xml @@ -1,11 +1,4 @@ - - + reading group diff --git a/P5/Source/Specs/re.xml b/P5/Source/Specs/re.xml index 7bd9b08160..2fbcd74061 100644 --- a/P5/Source/Specs/re.xml +++ b/P5/Source/Specs/re.xml @@ -1,11 +1,4 @@ - - + diff --git a/P5/Source/Specs/recordHist.xml b/P5/Source/Specs/recordHist.xml index bd66ec0811..a218041ad6 100644 --- a/P5/Source/Specs/recordHist.xml +++ b/P5/Source/Specs/recordHist.xml @@ -1,11 +1,4 @@ - - + recorded history diff --git a/P5/Source/Specs/recording.xml b/P5/Source/Specs/recording.xml index ba11025fd5..c312a4eec9 100644 --- a/P5/Source/Specs/recording.xml +++ b/P5/Source/Specs/recording.xml @@ -1,11 +1,4 @@ - - + recording event diff --git a/P5/Source/Specs/recordingStmt.xml b/P5/Source/Specs/recordingStmt.xml index d069238c92..3161ca2d7b 100644 --- a/P5/Source/Specs/recordingStmt.xml +++ b/P5/Source/Specs/recordingStmt.xml @@ -1,11 +1,4 @@ - - + recording statement diff --git a/P5/Source/Specs/redo.xml b/P5/Source/Specs/redo.xml index 0a8dad0d60..0da621df85 100644 --- a/P5/Source/Specs/redo.xml +++ b/P5/Source/Specs/redo.xml @@ -1,11 +1,4 @@ - - + indicates one or more cancelled interventions in a diff --git a/P5/Source/Specs/ref.xml b/P5/Source/Specs/ref.xml index 1c6f9dd713..d769a34f05 100644 --- a/P5/Source/Specs/ref.xml +++ b/P5/Source/Specs/ref.xml @@ -1,11 +1,4 @@ - - + reference diff --git a/P5/Source/Specs/refState.xml b/P5/Source/Specs/refState.xml index 1106b17904..b808c03b4b 100644 --- a/P5/Source/Specs/refState.xml +++ b/P5/Source/Specs/refState.xml @@ -1,11 +1,4 @@ - - + reference state diff --git a/P5/Source/Specs/refsDecl.xml b/P5/Source/Specs/refsDecl.xml index 7e5bc038d2..02befb6aa4 100644 --- a/P5/Source/Specs/refsDecl.xml +++ b/P5/Source/Specs/refsDecl.xml @@ -1,11 +1,4 @@ - - + references declaration diff --git a/P5/Source/Specs/reg.xml b/P5/Source/Specs/reg.xml index 234e9c4971..1429cc50c0 100644 --- a/P5/Source/Specs/reg.xml +++ b/P5/Source/Specs/reg.xml @@ -1,11 +1,4 @@ - - + regularization diff --git a/P5/Source/Specs/region.xml b/P5/Source/Specs/region.xml index 1dc01d63d3..ed2cf9dd95 100644 --- a/P5/Source/Specs/region.xml +++ b/P5/Source/Specs/region.xml @@ -1,10 +1,4 @@ - + region région contains the name of an administrative unit such as a state, province, or county, larger diff --git a/P5/Source/Specs/relatedItem.xml b/P5/Source/Specs/relatedItem.xml index 3cf81f3a14..7e1943e7cb 100644 --- a/P5/Source/Specs/relatedItem.xml +++ b/P5/Source/Specs/relatedItem.xml @@ -1,11 +1,4 @@ - - + contains or references some other bibliographic item which is related to the present one in diff --git a/P5/Source/Specs/relation.xml b/P5/Source/Specs/relation.xml index 51c10ca188..7813d5d2ac 100644 --- a/P5/Source/Specs/relation.xml +++ b/P5/Source/Specs/relation.xml @@ -1,10 +1,4 @@ - + relationship 관련성 人際關係 diff --git a/P5/Source/Specs/remarks.xml b/P5/Source/Specs/remarks.xml index 23da683e5e..eab9bc66a2 100644 --- a/P5/Source/Specs/remarks.xml +++ b/P5/Source/Specs/remarks.xml @@ -1,11 +1,4 @@ - - + remarks diff --git a/P5/Source/Specs/rendition.xml b/P5/Source/Specs/rendition.xml index 3b345f24fb..7cadc85f19 100644 --- a/P5/Source/Specs/rendition.xml +++ b/P5/Source/Specs/rendition.xml @@ -1,11 +1,4 @@ - - + rendition diff --git a/P5/Source/Specs/repository.xml b/P5/Source/Specs/repository.xml index 476584b959..be1df64396 100644 --- a/P5/Source/Specs/repository.xml +++ b/P5/Source/Specs/repository.xml @@ -1,11 +1,4 @@ - - + repository diff --git a/P5/Source/Specs/residence.xml b/P5/Source/Specs/residence.xml index 9c013fe618..c0e3cac801 100644 --- a/P5/Source/Specs/residence.xml +++ b/P5/Source/Specs/residence.xml @@ -1,10 +1,4 @@ - + residence 거주 住所 diff --git a/P5/Source/Specs/resp.xml b/P5/Source/Specs/resp.xml index 5db6d520a0..0fa4f7499a 100644 --- a/P5/Source/Specs/resp.xml +++ b/P5/Source/Specs/resp.xml @@ -1,10 +1,4 @@ - + responsibility 책임성 diff --git a/P5/Source/Specs/respStmt.xml b/P5/Source/Specs/respStmt.xml index 58349a0684..381e7fe5d0 100644 --- a/P5/Source/Specs/respStmt.xml +++ b/P5/Source/Specs/respStmt.xml @@ -1,11 +1,4 @@ - - + statement of responsibility diff --git a/P5/Source/Specs/respons.xml b/P5/Source/Specs/respons.xml index 73a5496334..673454b07c 100644 --- a/P5/Source/Specs/respons.xml +++ b/P5/Source/Specs/respons.xml @@ -1,11 +1,4 @@ - - + responsibility diff --git a/P5/Source/Specs/restore.xml b/P5/Source/Specs/restore.xml index c7e94547ab..97b0704019 100644 --- a/P5/Source/Specs/restore.xml +++ b/P5/Source/Specs/restore.xml @@ -1,11 +1,4 @@ - - + restore diff --git a/P5/Source/Specs/retrace.xml b/P5/Source/Specs/retrace.xml index dbd5275258..7fe3ce2c36 100644 --- a/P5/Source/Specs/retrace.xml +++ b/P5/Source/Specs/retrace.xml @@ -1,11 +1,4 @@ - - + contains a sequence of writing which has been retraced, for diff --git a/P5/Source/Specs/revisionDesc.xml b/P5/Source/Specs/revisionDesc.xml index ef4590e766..1f37dff596 100644 --- a/P5/Source/Specs/revisionDesc.xml +++ b/P5/Source/Specs/revisionDesc.xml @@ -1,11 +1,4 @@ - - + revision description diff --git a/P5/Source/Specs/rhyme.xml b/P5/Source/Specs/rhyme.xml index bfc72d8e28..a491783533 100644 --- a/P5/Source/Specs/rhyme.xml +++ b/P5/Source/Specs/rhyme.xml @@ -1,11 +1,4 @@ - - + marks the rhyming part of a metrical line. diff --git a/P5/Source/Specs/role.xml b/P5/Source/Specs/role.xml index 461b88d12d..a39524281a 100644 --- a/P5/Source/Specs/role.xml +++ b/P5/Source/Specs/role.xml @@ -1,11 +1,4 @@ - - + role diff --git a/P5/Source/Specs/roleDesc.xml b/P5/Source/Specs/roleDesc.xml index 2d737564fb..4192d1f359 100644 --- a/P5/Source/Specs/roleDesc.xml +++ b/P5/Source/Specs/roleDesc.xml @@ -1,11 +1,4 @@ - - + role description diff --git a/P5/Source/Specs/roleName.xml b/P5/Source/Specs/roleName.xml index 343dd5722a..9986b7c983 100644 --- a/P5/Source/Specs/roleName.xml +++ b/P5/Source/Specs/roleName.xml @@ -1,11 +1,4 @@ - - + role name diff --git a/P5/Source/Specs/root.xml b/P5/Source/Specs/root.xml index a3033d0869..4e704653b2 100644 --- a/P5/Source/Specs/root.xml +++ b/P5/Source/Specs/root.xml @@ -1,11 +1,4 @@ - - + root node diff --git a/P5/Source/Specs/row.xml b/P5/Source/Specs/row.xml index 4d08795cad..db4c1e60aa 100644 --- a/P5/Source/Specs/row.xml +++ b/P5/Source/Specs/row.xml @@ -1,11 +1,4 @@ - - + row diff --git a/P5/Source/Specs/rs.xml b/P5/Source/Specs/rs.xml index 31ec5ef3dc..8e49a17a7e 100644 --- a/P5/Source/Specs/rs.xml +++ b/P5/Source/Specs/rs.xml @@ -1,11 +1,4 @@ - - + referencing string diff --git a/P5/Source/Specs/rt.xml b/P5/Source/Specs/rt.xml index 33477776ec..71c2cd09c8 100644 --- a/P5/Source/Specs/rt.xml +++ b/P5/Source/Specs/rt.xml @@ -1,11 +1,4 @@ - - + ruby text diff --git a/P5/Source/Specs/rubric.xml b/P5/Source/Specs/rubric.xml index 903f2ebcac..584606f6ef 100644 --- a/P5/Source/Specs/rubric.xml +++ b/P5/Source/Specs/rubric.xml @@ -1,11 +1,4 @@ - - + rubric diff --git a/P5/Source/Specs/ruby.xml b/P5/Source/Specs/ruby.xml index 1097f0631b..db2f095b75 100644 --- a/P5/Source/Specs/ruby.xml +++ b/P5/Source/Specs/ruby.xml @@ -1,11 +1,4 @@ - - + ruby container diff --git a/P5/Source/Specs/s.xml b/P5/Source/Specs/s.xml index 97094b2d4a..2df1d961fc 100644 --- a/P5/Source/Specs/s.xml +++ b/P5/Source/Specs/s.xml @@ -1,11 +1,4 @@ - - + s-unit diff --git a/P5/Source/Specs/said.xml b/P5/Source/Specs/said.xml index 61a29696e2..28f5966631 100644 --- a/P5/Source/Specs/said.xml +++ b/P5/Source/Specs/said.xml @@ -1,11 +1,4 @@ - - + speech or thought diff --git a/P5/Source/Specs/salute.xml b/P5/Source/Specs/salute.xml index 586f534fc7..5dedecdf62 100644 --- a/P5/Source/Specs/salute.xml +++ b/P5/Source/Specs/salute.xml @@ -1,11 +1,4 @@ - - + salutation diff --git a/P5/Source/Specs/samplingDecl.xml b/P5/Source/Specs/samplingDecl.xml index edfe009fa1..005ece69e4 100644 --- a/P5/Source/Specs/samplingDecl.xml +++ b/P5/Source/Specs/samplingDecl.xml @@ -1,11 +1,4 @@ - - + sampling declaration diff --git a/P5/Source/Specs/schemaRef.xml b/P5/Source/Specs/schemaRef.xml index f93b1c609e..f5f622ddd2 100644 --- a/P5/Source/Specs/schemaRef.xml +++ b/P5/Source/Specs/schemaRef.xml @@ -1,11 +1,4 @@ - - + schema reference diff --git a/P5/Source/Specs/schemaSpec.xml b/P5/Source/Specs/schemaSpec.xml index 8b3b87ce18..8389f70a1d 100644 --- a/P5/Source/Specs/schemaSpec.xml +++ b/P5/Source/Specs/schemaSpec.xml @@ -1,11 +1,4 @@ - - + schema specification diff --git a/P5/Source/Specs/scriptDesc.xml b/P5/Source/Specs/scriptDesc.xml index 41e9ae1346..ead5c2de53 100644 --- a/P5/Source/Specs/scriptDesc.xml +++ b/P5/Source/Specs/scriptDesc.xml @@ -1,11 +1,4 @@ - - + script description diff --git a/P5/Source/Specs/scriptNote.xml b/P5/Source/Specs/scriptNote.xml index 758f6afd04..52d4803d81 100644 --- a/P5/Source/Specs/scriptNote.xml +++ b/P5/Source/Specs/scriptNote.xml @@ -1,11 +1,4 @@ - - + describes a particular script distinguished within diff --git a/P5/Source/Specs/scriptStmt.xml b/P5/Source/Specs/scriptStmt.xml index a5373939fa..4f97bc576e 100644 --- a/P5/Source/Specs/scriptStmt.xml +++ b/P5/Source/Specs/scriptStmt.xml @@ -1,11 +1,4 @@ - - + script statement diff --git a/P5/Source/Specs/seal.xml b/P5/Source/Specs/seal.xml index 7a86a8cff3..8d70bb1b56 100644 --- a/P5/Source/Specs/seal.xml +++ b/P5/Source/Specs/seal.xml @@ -1,10 +1,4 @@ - + seal sceau contains a description of one seal or similar applied to the object described diff --git a/P5/Source/Specs/sealDesc.xml b/P5/Source/Specs/sealDesc.xml index 92199795e8..bc6f609024 100644 --- a/P5/Source/Specs/sealDesc.xml +++ b/P5/Source/Specs/sealDesc.xml @@ -1,11 +1,4 @@ - - + seal description diff --git a/P5/Source/Specs/secFol.xml b/P5/Source/Specs/secFol.xml index 5abad24f53..1affd7b4cc 100644 --- a/P5/Source/Specs/secFol.xml +++ b/P5/Source/Specs/secFol.xml @@ -1,11 +1,4 @@ - - + second folio diff --git a/P5/Source/Specs/secl.xml b/P5/Source/Specs/secl.xml index ee6a262402..3518cb120c 100644 --- a/P5/Source/Specs/secl.xml +++ b/P5/Source/Specs/secl.xml @@ -1,11 +1,4 @@ - - + secluded text diff --git a/P5/Source/Specs/seg.xml b/P5/Source/Specs/seg.xml index 1154e5583d..a82d6d40fe 100644 --- a/P5/Source/Specs/seg.xml +++ b/P5/Source/Specs/seg.xml @@ -1,5 +1,4 @@ - - + arbitrary segment diff --git a/P5/Source/Specs/segmentation.xml b/P5/Source/Specs/segmentation.xml index c898527318..fe76c035cf 100644 --- a/P5/Source/Specs/segmentation.xml +++ b/P5/Source/Specs/segmentation.xml @@ -1,11 +1,4 @@ - - + segmentation diff --git a/P5/Source/Specs/sense.xml b/P5/Source/Specs/sense.xml index b5b714105b..2c0991d7f7 100644 --- a/P5/Source/Specs/sense.xml +++ b/P5/Source/Specs/sense.xml @@ -1,11 +1,4 @@ - - + groups together all information relating to one word sense in a dictionary entry, for diff --git a/P5/Source/Specs/sequence.xml b/P5/Source/Specs/sequence.xml index c2c397c3e3..bae4321128 100644 --- a/P5/Source/Specs/sequence.xml +++ b/P5/Source/Specs/sequence.xml @@ -1,11 +1,4 @@ - - + indicates that the constructs referenced by its children form a sequence diff --git a/P5/Source/Specs/series.xml b/P5/Source/Specs/series.xml index b4a41cc747..c2d2cda2f7 100644 --- a/P5/Source/Specs/series.xml +++ b/P5/Source/Specs/series.xml @@ -1,11 +1,4 @@ - - + series information diff --git a/P5/Source/Specs/seriesStmt.xml b/P5/Source/Specs/seriesStmt.xml index 3fed1411af..63698a8965 100644 --- a/P5/Source/Specs/seriesStmt.xml +++ b/P5/Source/Specs/seriesStmt.xml @@ -1,11 +1,4 @@ - - + series statement diff --git a/P5/Source/Specs/set.xml b/P5/Source/Specs/set.xml index 7c0414a352..47cfbfa483 100644 --- a/P5/Source/Specs/set.xml +++ b/P5/Source/Specs/set.xml @@ -1,11 +1,4 @@ - - + setting diff --git a/P5/Source/Specs/setting.xml b/P5/Source/Specs/setting.xml index 9de8088770..64c800e7b1 100644 --- a/P5/Source/Specs/setting.xml +++ b/P5/Source/Specs/setting.xml @@ -1,11 +1,4 @@ - - + describes one particular setting in which a language diff --git a/P5/Source/Specs/settingDesc.xml b/P5/Source/Specs/settingDesc.xml index 915dd6d807..ccf1394356 100644 --- a/P5/Source/Specs/settingDesc.xml +++ b/P5/Source/Specs/settingDesc.xml @@ -1,11 +1,4 @@ - - + setting description diff --git a/P5/Source/Specs/settlement.xml b/P5/Source/Specs/settlement.xml index dbe0208625..32beba5df6 100644 --- a/P5/Source/Specs/settlement.xml +++ b/P5/Source/Specs/settlement.xml @@ -1,10 +1,4 @@ - + settlement lieu de peuplement contains the name of a settlement such as a city, town, or village identified as a single geo-political or administrative unit. diff --git a/P5/Source/Specs/sex.xml b/P5/Source/Specs/sex.xml index ecf477a80b..7ee34128e7 100644 --- a/P5/Source/Specs/sex.xml +++ b/P5/Source/Specs/sex.xml @@ -1,10 +1,4 @@ - + sex sexe specifies the sex of an organism. diff --git a/P5/Source/Specs/shift.xml b/P5/Source/Specs/shift.xml index 51f6dba6e8..062aeb1ea7 100644 --- a/P5/Source/Specs/shift.xml +++ b/P5/Source/Specs/shift.xml @@ -1,11 +1,4 @@ - - + shift diff --git a/P5/Source/Specs/sic.xml b/P5/Source/Specs/sic.xml index 4b52220db7..8231191379 100644 --- a/P5/Source/Specs/sic.xml +++ b/P5/Source/Specs/sic.xml @@ -1,11 +1,4 @@ - - + Latin for thus or so diff --git a/P5/Source/Specs/signatures.xml b/P5/Source/Specs/signatures.xml index a85faf4f06..da4fb74723 100644 --- a/P5/Source/Specs/signatures.xml +++ b/P5/Source/Specs/signatures.xml @@ -1,11 +1,4 @@ - - + signatures diff --git a/P5/Source/Specs/signed.xml b/P5/Source/Specs/signed.xml index 32fc5b8cd6..c8a8f0cf93 100644 --- a/P5/Source/Specs/signed.xml +++ b/P5/Source/Specs/signed.xml @@ -1,11 +1,4 @@ - - + signature diff --git a/P5/Source/Specs/soCalled.xml b/P5/Source/Specs/soCalled.xml index 8b7341c2d3..2bbe980c98 100644 --- a/P5/Source/Specs/soCalled.xml +++ b/P5/Source/Specs/soCalled.xml @@ -1,11 +1,4 @@ - - + so called diff --git a/P5/Source/Specs/socecStatus.xml b/P5/Source/Specs/socecStatus.xml index 79ea94c3a0..5b91821cfa 100644 --- a/P5/Source/Specs/socecStatus.xml +++ b/P5/Source/Specs/socecStatus.xml @@ -1,10 +1,4 @@ - + socio-economic status statut socio-économique 사회-경제적 지위 diff --git a/P5/Source/Specs/sound.xml b/P5/Source/Specs/sound.xml index 3a943e8f3e..2c2ff455e8 100644 --- a/P5/Source/Specs/sound.xml +++ b/P5/Source/Specs/sound.xml @@ -1,11 +1,4 @@ - - + sound diff --git a/P5/Source/Specs/source.xml b/P5/Source/Specs/source.xml index 8aacb9e2d5..e947709180 100644 --- a/P5/Source/Specs/source.xml +++ b/P5/Source/Specs/source.xml @@ -1,11 +1,4 @@ - - + source diff --git a/P5/Source/Specs/sourceDesc.xml b/P5/Source/Specs/sourceDesc.xml index 165b4bf0ff..c6cd51625e 100644 --- a/P5/Source/Specs/sourceDesc.xml +++ b/P5/Source/Specs/sourceDesc.xml @@ -1,11 +1,4 @@ - - + source description diff --git a/P5/Source/Specs/sourceDoc.xml b/P5/Source/Specs/sourceDoc.xml index 1954c104ce..e1139403c7 100644 --- a/P5/Source/Specs/sourceDoc.xml +++ b/P5/Source/Specs/sourceDoc.xml @@ -1,11 +1,4 @@ - - + contains a transcription or other representation of a single diff --git a/P5/Source/Specs/sp.xml b/P5/Source/Specs/sp.xml index e99461b992..2ea0276125 100644 --- a/P5/Source/Specs/sp.xml +++ b/P5/Source/Specs/sp.xml @@ -1,11 +1,4 @@ - - + speech diff --git a/P5/Source/Specs/spGrp.xml b/P5/Source/Specs/spGrp.xml index 0376a3b5aa..e124a5f898 100644 --- a/P5/Source/Specs/spGrp.xml +++ b/P5/Source/Specs/spGrp.xml @@ -1,11 +1,4 @@ - - + speech group diff --git a/P5/Source/Specs/space.xml b/P5/Source/Specs/space.xml index 06930970fe..896094e328 100644 --- a/P5/Source/Specs/space.xml +++ b/P5/Source/Specs/space.xml @@ -1,11 +1,4 @@ - - + space diff --git a/P5/Source/Specs/span.xml b/P5/Source/Specs/span.xml index 60c8cda740..a0d2d2a16c 100644 --- a/P5/Source/Specs/span.xml +++ b/P5/Source/Specs/span.xml @@ -1,11 +1,4 @@ - - + associates an interpretative annotation directly with a span of text. diff --git a/P5/Source/Specs/spanGrp.xml b/P5/Source/Specs/spanGrp.xml index a028678bc1..3f86d96918 100644 --- a/P5/Source/Specs/spanGrp.xml +++ b/P5/Source/Specs/spanGrp.xml @@ -1,11 +1,4 @@ - - + span group diff --git a/P5/Source/Specs/speaker.xml b/P5/Source/Specs/speaker.xml index 929d53dfbc..46d6ded603 100644 --- a/P5/Source/Specs/speaker.xml +++ b/P5/Source/Specs/speaker.xml @@ -1,11 +1,4 @@ - - + diff --git a/P5/Source/Specs/specDesc.xml b/P5/Source/Specs/specDesc.xml index 67f15e8be5..35f3f5b1d6 100644 --- a/P5/Source/Specs/specDesc.xml +++ b/P5/Source/Specs/specDesc.xml @@ -1,11 +1,4 @@ - - + specification description diff --git a/P5/Source/Specs/specGrp.xml b/P5/Source/Specs/specGrp.xml index 61e2a04a15..961e3e511d 100644 --- a/P5/Source/Specs/specGrp.xml +++ b/P5/Source/Specs/specGrp.xml @@ -1,11 +1,4 @@ - - + specification group diff --git a/P5/Source/Specs/specGrpRef.xml b/P5/Source/Specs/specGrpRef.xml index 14adf6a8c1..3e914fd8ae 100644 --- a/P5/Source/Specs/specGrpRef.xml +++ b/P5/Source/Specs/specGrpRef.xml @@ -1,11 +1,4 @@ - - + reference to a specification group diff --git a/P5/Source/Specs/specList.xml b/P5/Source/Specs/specList.xml index 6c2be80d45..daf80dd6cd 100644 --- a/P5/Source/Specs/specList.xml +++ b/P5/Source/Specs/specList.xml @@ -1,11 +1,4 @@ - - + specification list diff --git a/P5/Source/Specs/sponsor.xml b/P5/Source/Specs/sponsor.xml index 8b637f6e59..95ef299da2 100644 --- a/P5/Source/Specs/sponsor.xml +++ b/P5/Source/Specs/sponsor.xml @@ -1,10 +1,4 @@ - + sponsor commanditaire Förderer diff --git a/P5/Source/Specs/stage.xml b/P5/Source/Specs/stage.xml index 544ee76cb1..decf7c7fdd 100644 --- a/P5/Source/Specs/stage.xml +++ b/P5/Source/Specs/stage.xml @@ -1,11 +1,4 @@ - - + stage direction diff --git a/P5/Source/Specs/stamp.xml b/P5/Source/Specs/stamp.xml index 4e993a006e..fbf1ad349a 100644 --- a/P5/Source/Specs/stamp.xml +++ b/P5/Source/Specs/stamp.xml @@ -1,10 +1,4 @@ - + stamp cachet contains a word or phrase describing a stamp or similar device. diff --git a/P5/Source/Specs/standOff.xml b/P5/Source/Specs/standOff.xml index dfd60308f9..2fd9814065 100644 --- a/P5/Source/Specs/standOff.xml +++ b/P5/Source/Specs/standOff.xml @@ -1,8 +1,4 @@ - + + state statut contains a description of some status or quality attributed to a person, place, or organization often at some specific time or for a specific date range. diff --git a/P5/Source/Specs/stdVals.xml b/P5/Source/Specs/stdVals.xml index 20b8e4a325..f74bb60d36 100644 --- a/P5/Source/Specs/stdVals.xml +++ b/P5/Source/Specs/stdVals.xml @@ -1,11 +1,4 @@ - - + standard values diff --git a/P5/Source/Specs/street.xml b/P5/Source/Specs/street.xml index 13472c54d1..b5d8888ae2 100644 --- a/P5/Source/Specs/street.xml +++ b/P5/Source/Specs/street.xml @@ -1,11 +1,4 @@ - - + contains a full street address including any name or number identifying a diff --git a/P5/Source/Specs/stress.xml b/P5/Source/Specs/stress.xml index 59a9f9713f..2d59a1b40f 100644 --- a/P5/Source/Specs/stress.xml +++ b/P5/Source/Specs/stress.xml @@ -1,11 +1,4 @@ - - + stress diff --git a/P5/Source/Specs/string.xml b/P5/Source/Specs/string.xml index 93aad81c84..e2cfb527f6 100644 --- a/P5/Source/Specs/string.xml +++ b/P5/Source/Specs/string.xml @@ -1,11 +1,4 @@ - - + string value diff --git a/P5/Source/Specs/styleDefDecl.xml b/P5/Source/Specs/styleDefDecl.xml index cb5a058be8..62809d322c 100644 --- a/P5/Source/Specs/styleDefDecl.xml +++ b/P5/Source/Specs/styleDefDecl.xml @@ -1,11 +1,4 @@ - - + style definition language declaration diff --git a/P5/Source/Specs/subc.xml b/P5/Source/Specs/subc.xml index 23939e7f55..08a1897755 100644 --- a/P5/Source/Specs/subc.xml +++ b/P5/Source/Specs/subc.xml @@ -1,11 +1,4 @@ - - + subcategorization diff --git a/P5/Source/Specs/subst.xml b/P5/Source/Specs/subst.xml index e4ee36cd8c..5ae7359022 100644 --- a/P5/Source/Specs/subst.xml +++ b/P5/Source/Specs/subst.xml @@ -1,11 +1,4 @@ - - + substitution diff --git a/P5/Source/Specs/substJoin.xml b/P5/Source/Specs/substJoin.xml index 47eab419d9..cc6101fd28 100644 --- a/P5/Source/Specs/substJoin.xml +++ b/P5/Source/Specs/substJoin.xml @@ -1,5 +1,4 @@ - - + substitution join diff --git a/P5/Source/Specs/summary.xml b/P5/Source/Specs/summary.xml index b72f02df49..658ee76957 100644 --- a/P5/Source/Specs/summary.xml +++ b/P5/Source/Specs/summary.xml @@ -1,11 +1,4 @@ - - + contains an overview of the available diff --git a/P5/Source/Specs/superEntry.xml b/P5/Source/Specs/superEntry.xml index d414afabf3..cab6f06146 100644 --- a/P5/Source/Specs/superEntry.xml +++ b/P5/Source/Specs/superEntry.xml @@ -1,11 +1,4 @@ - - + super entry diff --git a/P5/Source/Specs/supplied.xml b/P5/Source/Specs/supplied.xml index cf10b33aa8..8ca8261e1b 100644 --- a/P5/Source/Specs/supplied.xml +++ b/P5/Source/Specs/supplied.xml @@ -1,11 +1,4 @@ - - + supplied diff --git a/P5/Source/Specs/support.xml b/P5/Source/Specs/support.xml index b03ddb462b..93018995bd 100644 --- a/P5/Source/Specs/support.xml +++ b/P5/Source/Specs/support.xml @@ -1,11 +1,4 @@ - - + support diff --git a/P5/Source/Specs/supportDesc.xml b/P5/Source/Specs/supportDesc.xml index 60e6e55ce5..6e7aa4bbdc 100644 --- a/P5/Source/Specs/supportDesc.xml +++ b/P5/Source/Specs/supportDesc.xml @@ -1,11 +1,4 @@ - - + support description diff --git a/P5/Source/Specs/surface.xml b/P5/Source/Specs/surface.xml index 70ee7aa2f3..e6c82216d8 100644 --- a/P5/Source/Specs/surface.xml +++ b/P5/Source/Specs/surface.xml @@ -1,11 +1,4 @@ - - + defines a written surface as a two-dimensional diff --git a/P5/Source/Specs/surfaceGrp.xml b/P5/Source/Specs/surfaceGrp.xml index 5962f5aa49..a519536497 100644 --- a/P5/Source/Specs/surfaceGrp.xml +++ b/P5/Source/Specs/surfaceGrp.xml @@ -1,11 +1,4 @@ - - + surface group diff --git a/P5/Source/Specs/surname.xml b/P5/Source/Specs/surname.xml index eb308b00a0..77c00ff363 100644 --- a/P5/Source/Specs/surname.xml +++ b/P5/Source/Specs/surname.xml @@ -1,11 +1,4 @@ - - + surname diff --git a/P5/Source/Specs/surplus.xml b/P5/Source/Specs/surplus.xml index b9e7f521e1..0403081c34 100644 --- a/P5/Source/Specs/surplus.xml +++ b/P5/Source/Specs/surplus.xml @@ -1,11 +1,4 @@ - - + surplus diff --git a/P5/Source/Specs/surrogates.xml b/P5/Source/Specs/surrogates.xml index b6a26eadff..569de8ced0 100644 --- a/P5/Source/Specs/surrogates.xml +++ b/P5/Source/Specs/surrogates.xml @@ -1,11 +1,4 @@ - - + surrogates diff --git a/P5/Source/Specs/syll.xml b/P5/Source/Specs/syll.xml index 61f673b947..c9901c316c 100644 --- a/P5/Source/Specs/syll.xml +++ b/P5/Source/Specs/syll.xml @@ -1,11 +1,4 @@ - - + syllabification diff --git a/P5/Source/Specs/symbol.xml b/P5/Source/Specs/symbol.xml index 5b281f3657..2b0e10a514 100644 --- a/P5/Source/Specs/symbol.xml +++ b/P5/Source/Specs/symbol.xml @@ -1,11 +1,4 @@ - - + symbolic value diff --git a/P5/Source/Specs/table.xml b/P5/Source/Specs/table.xml index ab11d7c54b..006341f9e3 100644 --- a/P5/Source/Specs/table.xml +++ b/P5/Source/Specs/table.xml @@ -1,11 +1,4 @@ - - + table diff --git a/P5/Source/Specs/tag.xml b/P5/Source/Specs/tag.xml index 3b79f291d8..340052f631 100644 --- a/P5/Source/Specs/tag.xml +++ b/P5/Source/Specs/tag.xml @@ -1,11 +1,4 @@ - - + tag diff --git a/P5/Source/Specs/tagUsage.xml b/P5/Source/Specs/tagUsage.xml index 6289a27d35..8d30ff80e6 100644 --- a/P5/Source/Specs/tagUsage.xml +++ b/P5/Source/Specs/tagUsage.xml @@ -1,11 +1,4 @@ - - + element usage diff --git a/P5/Source/Specs/tagsDecl.xml b/P5/Source/Specs/tagsDecl.xml index 0b8997623a..49c2afd87b 100644 --- a/P5/Source/Specs/tagsDecl.xml +++ b/P5/Source/Specs/tagsDecl.xml @@ -1,11 +1,4 @@ - - + tagging declaration diff --git a/P5/Source/Specs/taxonomy.xml b/P5/Source/Specs/taxonomy.xml index 3badf02763..d27bc30c31 100644 --- a/P5/Source/Specs/taxonomy.xml +++ b/P5/Source/Specs/taxonomy.xml @@ -1,11 +1,4 @@ - - + taxonomy diff --git a/P5/Source/Specs/tech.xml b/P5/Source/Specs/tech.xml index 3a8920f4a2..01a8038611 100644 --- a/P5/Source/Specs/tech.xml +++ b/P5/Source/Specs/tech.xml @@ -1,11 +1,4 @@ - - + technical stage direction diff --git a/P5/Source/Specs/teiCorpus.xml b/P5/Source/Specs/teiCorpus.xml index be5c7dc1b4..1977aac53f 100644 --- a/P5/Source/Specs/teiCorpus.xml +++ b/P5/Source/Specs/teiCorpus.xml @@ -1,11 +1,4 @@ - - + TEI corpus diff --git a/P5/Source/Specs/teiHeader.xml b/P5/Source/Specs/teiHeader.xml index c6de7fdce7..14b9998179 100644 --- a/P5/Source/Specs/teiHeader.xml +++ b/P5/Source/Specs/teiHeader.xml @@ -1,11 +1,4 @@ - - + TEI header diff --git a/P5/Source/Specs/teidata.authority.xml b/P5/Source/Specs/teidata.authority.xml index 6720a61dbc..7c77d19c3a 100644 --- a/P5/Source/Specs/teidata.authority.xml +++ b/P5/Source/Specs/teidata.authority.xml @@ -1,9 +1,4 @@ - - + diff --git a/P5/Source/Specs/teidata.certainty.xml b/P5/Source/Specs/teidata.certainty.xml index 2797de8577..c54477346e 100644 --- a/P5/Source/Specs/teidata.certainty.xml +++ b/P5/Source/Specs/teidata.certainty.xml @@ -1,9 +1,4 @@ - - + defines the range of attribute values expressing a degree of certainty. diff --git a/P5/Source/Specs/teidata.count.xml b/P5/Source/Specs/teidata.count.xml index 7b428db4c4..5a96402b2b 100644 --- a/P5/Source/Specs/teidata.count.xml +++ b/P5/Source/Specs/teidata.count.xml @@ -1,9 +1,4 @@ - - + defines the range of attribute values used for a non-negative diff --git a/P5/Source/Specs/teidata.duration.iso.xml b/P5/Source/Specs/teidata.duration.iso.xml index 49127a8f98..e7d0cf2d6b 100644 --- a/P5/Source/Specs/teidata.duration.iso.xml +++ b/P5/Source/Specs/teidata.duration.iso.xml @@ -1,9 +1,4 @@ - - + defines the range of attribute values available for representation of a duration in time diff --git a/P5/Source/Specs/teidata.duration.w3c.xml b/P5/Source/Specs/teidata.duration.w3c.xml index 368724d72c..35848a2f69 100644 --- a/P5/Source/Specs/teidata.duration.w3c.xml +++ b/P5/Source/Specs/teidata.duration.w3c.xml @@ -1,9 +1,4 @@ - - + defines the range of attribute values available for representation of a duration in time using W3C datatypes. diff --git a/P5/Source/Specs/teidata.enumerated.xml b/P5/Source/Specs/teidata.enumerated.xml index 8a951c8229..f500c6736a 100644 --- a/P5/Source/Specs/teidata.enumerated.xml +++ b/P5/Source/Specs/teidata.enumerated.xml @@ -1,9 +1,4 @@ - - + defines the range of attribute values expressed as a single XML name taken from a list of diff --git a/P5/Source/Specs/teidata.gender.xml b/P5/Source/Specs/teidata.gender.xml index 9207d6cf87..dd5a6bcdb6 100644 --- a/P5/Source/Specs/teidata.gender.xml +++ b/P5/Source/Specs/teidata.gender.xml @@ -1,8 +1,4 @@ - + diff --git a/P5/Source/Specs/teidata.interval.xml b/P5/Source/Specs/teidata.interval.xml index f6b7eaf5d9..d17560fd73 100644 --- a/P5/Source/Specs/teidata.interval.xml +++ b/P5/Source/Specs/teidata.interval.xml @@ -1,9 +1,4 @@ - - + defines attribute values used to express an interval value. diff --git a/P5/Source/Specs/teidata.key.xml b/P5/Source/Specs/teidata.key.xml index a6dd428ed5..4a70da6877 100644 --- a/P5/Source/Specs/teidata.key.xml +++ b/P5/Source/Specs/teidata.key.xml @@ -1,8 +1,4 @@ - + - + defines the range of attribute values used to identify a particular combination of human diff --git a/P5/Source/Specs/teidata.name.xml b/P5/Source/Specs/teidata.name.xml index 4d1547a933..c64411dd72 100644 --- a/P5/Source/Specs/teidata.name.xml +++ b/P5/Source/Specs/teidata.name.xml @@ -1,9 +1,4 @@ - - + defines the range of attribute values expressed as an XML Name. diff --git a/P5/Source/Specs/teidata.namespace.xml b/P5/Source/Specs/teidata.namespace.xml index be9efb9202..f2b0189151 100644 --- a/P5/Source/Specs/teidata.namespace.xml +++ b/P5/Source/Specs/teidata.namespace.xml @@ -1,9 +1,4 @@ - - + defines the range of attribute values used to indicate XML namespaces as defined by the W3C diff --git a/P5/Source/Specs/teidata.namespaceOrName.xml b/P5/Source/Specs/teidata.namespaceOrName.xml index 98db1a8eca..849d049f95 100644 --- a/P5/Source/Specs/teidata.namespaceOrName.xml +++ b/P5/Source/Specs/teidata.namespaceOrName.xml @@ -1,9 +1,4 @@ - - + + - + defines the range of attribute values used for numeric values. diff --git a/P5/Source/Specs/teidata.outputMeasurement.xml b/P5/Source/Specs/teidata.outputMeasurement.xml index d155d5ba5c..6cdd30f469 100644 --- a/P5/Source/Specs/teidata.outputMeasurement.xml +++ b/P5/Source/Specs/teidata.outputMeasurement.xml @@ -1,9 +1,4 @@ - - + defines a range of values for use in specifying the size of an object that is intended for diff --git a/P5/Source/Specs/teidata.pattern.xml b/P5/Source/Specs/teidata.pattern.xml index 452be97e57..2ed5381daf 100644 --- a/P5/Source/Specs/teidata.pattern.xml +++ b/P5/Source/Specs/teidata.pattern.xml @@ -1,9 +1,4 @@ - - + + defines the data type used to express a point in cartesian space. diff --git a/P5/Source/Specs/teidata.pointer.xml b/P5/Source/Specs/teidata.pointer.xml index e4caa5e874..f8f79e4b44 100644 --- a/P5/Source/Specs/teidata.pointer.xml +++ b/P5/Source/Specs/teidata.pointer.xml @@ -1,9 +1,4 @@ - - + defines the range of attribute values used to provide a single diff --git a/P5/Source/Specs/teidata.prefix.xml b/P5/Source/Specs/teidata.prefix.xml index 9b65e7770d..92ea08f87f 100644 --- a/P5/Source/Specs/teidata.prefix.xml +++ b/P5/Source/Specs/teidata.prefix.xml @@ -1,8 +1,4 @@ - + diff --git a/P5/Source/Specs/teidata.probCert.xml b/P5/Source/Specs/teidata.probCert.xml index 86ca7d96d1..426c73ad56 100644 --- a/P5/Source/Specs/teidata.probCert.xml +++ b/P5/Source/Specs/teidata.probCert.xml @@ -1,8 +1,4 @@ - + - + defines the range of attribute values expressing a probability. diff --git a/P5/Source/Specs/teidata.replacement.xml b/P5/Source/Specs/teidata.replacement.xml index b1631c6fbc..22288dbbc2 100644 --- a/P5/Source/Specs/teidata.replacement.xml +++ b/P5/Source/Specs/teidata.replacement.xml @@ -1,9 +1,4 @@ - - + defines attribute values which contain a replacement template. diff --git a/P5/Source/Specs/teidata.sex.xml b/P5/Source/Specs/teidata.sex.xml index 8ee18792d3..15f2001b54 100644 --- a/P5/Source/Specs/teidata.sex.xml +++ b/P5/Source/Specs/teidata.sex.xml @@ -1,8 +1,4 @@ - + diff --git a/P5/Source/Specs/teidata.temporal.iso.xml b/P5/Source/Specs/teidata.temporal.iso.xml index adacbd23ff..8fcfd1574c 100644 --- a/P5/Source/Specs/teidata.temporal.iso.xml +++ b/P5/Source/Specs/teidata.temporal.iso.xml @@ -1,9 +1,4 @@ - - + defines the range of attribute values expressing a temporal expression such as a date, a diff --git a/P5/Source/Specs/teidata.temporal.w3c.xml b/P5/Source/Specs/teidata.temporal.w3c.xml index c79a6bc9a6..cb20e59f7d 100644 --- a/P5/Source/Specs/teidata.temporal.w3c.xml +++ b/P5/Source/Specs/teidata.temporal.w3c.xml @@ -1,9 +1,4 @@ - - + defines the range of attribute values expressing a temporal diff --git a/P5/Source/Specs/teidata.temporal.working.xml b/P5/Source/Specs/teidata.temporal.working.xml index 494dc701de..8c98b6630c 100644 --- a/P5/Source/Specs/teidata.temporal.working.xml +++ b/P5/Source/Specs/teidata.temporal.working.xml @@ -1,8 +1,4 @@ - + - + defines the range of attribute values used to express some diff --git a/P5/Source/Specs/teidata.truthValue.xml b/P5/Source/Specs/teidata.truthValue.xml index 50300365eb..a9c04ff713 100644 --- a/P5/Source/Specs/teidata.truthValue.xml +++ b/P5/Source/Specs/teidata.truthValue.xml @@ -1,9 +1,4 @@ - - + defines the range of attribute values used to express a truth diff --git a/P5/Source/Specs/teidata.unboundedCount.xml b/P5/Source/Specs/teidata.unboundedCount.xml index eacf8d4252..13bc913069 100644 --- a/P5/Source/Specs/teidata.unboundedCount.xml +++ b/P5/Source/Specs/teidata.unboundedCount.xml @@ -1,9 +1,4 @@ - - + defines the range of values used for a counting number or the string unbounded for infinity. diff --git a/P5/Source/Specs/teidata.version.xml b/P5/Source/Specs/teidata.version.xml index 2addc9bf52..963574335c 100644 --- a/P5/Source/Specs/teidata.version.xml +++ b/P5/Source/Specs/teidata.version.xml @@ -1,9 +1,4 @@ - - + defines the range of attribute values which may be used to diff --git a/P5/Source/Specs/teidata.versionNumber.xml b/P5/Source/Specs/teidata.versionNumber.xml index 95246f4f14..ddb0c00c6d 100644 --- a/P5/Source/Specs/teidata.versionNumber.xml +++ b/P5/Source/Specs/teidata.versionNumber.xml @@ -1,9 +1,4 @@ - - + defines the range of attribute values used for version numbers. diff --git a/P5/Source/Specs/teidata.word.xml b/P5/Source/Specs/teidata.word.xml index edd11ce673..80190cfec3 100644 --- a/P5/Source/Specs/teidata.word.xml +++ b/P5/Source/Specs/teidata.word.xml @@ -1,9 +1,4 @@ - - + defines the range of attribute values expressed as a single diff --git a/P5/Source/Specs/teidata.xTruthValue.xml b/P5/Source/Specs/teidata.xTruthValue.xml index b63a6ec2bb..9df6c0fef6 100644 --- a/P5/Source/Specs/teidata.xTruthValue.xml +++ b/P5/Source/Specs/teidata.xTruthValue.xml @@ -1,9 +1,4 @@ - - + extended truth value diff --git a/P5/Source/Specs/teidata.xmlName.xml b/P5/Source/Specs/teidata.xmlName.xml index 303bd567c7..73578fb750 100644 --- a/P5/Source/Specs/teidata.xmlName.xml +++ b/P5/Source/Specs/teidata.xmlName.xml @@ -1,9 +1,4 @@ - - + defines attribute values which contain an XML name. diff --git a/P5/Source/Specs/teidata.xpath.xml b/P5/Source/Specs/teidata.xpath.xml index 8ace6486cd..aaaaba9905 100644 --- a/P5/Source/Specs/teidata.xpath.xml +++ b/P5/Source/Specs/teidata.xpath.xml @@ -1,9 +1,4 @@ - - + defines attribute values diff --git a/P5/Source/Specs/term.xml b/P5/Source/Specs/term.xml index 9103e5d9f1..8b205ffcbb 100644 --- a/P5/Source/Specs/term.xml +++ b/P5/Source/Specs/term.xml @@ -1,11 +1,4 @@ - - + term diff --git a/P5/Source/Specs/terrain.xml b/P5/Source/Specs/terrain.xml index 8b1718c18c..7a2c69461c 100644 --- a/P5/Source/Specs/terrain.xml +++ b/P5/Source/Specs/terrain.xml @@ -1,10 +1,4 @@ - + terrain terrain contains information about the physical terrain of a place. diff --git a/P5/Source/Specs/text.xml b/P5/Source/Specs/text.xml index 28a761284d..45927be403 100644 --- a/P5/Source/Specs/text.xml +++ b/P5/Source/Specs/text.xml @@ -1,11 +1,4 @@ - - + text diff --git a/P5/Source/Specs/textClass.xml b/P5/Source/Specs/textClass.xml index 4cfe3b7e5a..30b7879dbd 100644 --- a/P5/Source/Specs/textClass.xml +++ b/P5/Source/Specs/textClass.xml @@ -1,11 +1,4 @@ - - + text classification diff --git a/P5/Source/Specs/textDesc.xml b/P5/Source/Specs/textDesc.xml index f70abebee7..c9ebd1c9e3 100644 --- a/P5/Source/Specs/textDesc.xml +++ b/P5/Source/Specs/textDesc.xml @@ -1,11 +1,4 @@ - - + text description diff --git a/P5/Source/Specs/textLang.xml b/P5/Source/Specs/textLang.xml index 61e0b15ceb..2a5db7d142 100644 --- a/P5/Source/Specs/textLang.xml +++ b/P5/Source/Specs/textLang.xml @@ -1,11 +1,4 @@ - - + text language diff --git a/P5/Source/Specs/textNode.xml b/P5/Source/Specs/textNode.xml index 6e246b0eef..b1880ce002 100644 --- a/P5/Source/Specs/textNode.xml +++ b/P5/Source/Specs/textNode.xml @@ -1,11 +1,4 @@ - - + indicates the presence diff --git a/P5/Source/Specs/then.xml b/P5/Source/Specs/then.xml index 6ffd948f9b..ca933db3dd 100644 --- a/P5/Source/Specs/then.xml +++ b/P5/Source/Specs/then.xml @@ -1,11 +1,4 @@ - - + separates the condition from the default in an if, or diff --git a/P5/Source/Specs/time.xml b/P5/Source/Specs/time.xml index 9431aba531..57f9fc9630 100644 --- a/P5/Source/Specs/time.xml +++ b/P5/Source/Specs/time.xml @@ -1,11 +1,4 @@ - - + time diff --git a/P5/Source/Specs/timeline.xml b/P5/Source/Specs/timeline.xml index 01102307de..b707d5350e 100644 --- a/P5/Source/Specs/timeline.xml +++ b/P5/Source/Specs/timeline.xml @@ -1,5 +1,4 @@ - - + timeline diff --git a/P5/Source/Specs/title.xml b/P5/Source/Specs/title.xml index ad9eda4e2f..671ce855e5 100644 --- a/P5/Source/Specs/title.xml +++ b/P5/Source/Specs/title.xml @@ -1,10 +1,4 @@ - + title titre Titel diff --git a/P5/Source/Specs/titlePage.xml b/P5/Source/Specs/titlePage.xml index 2e76307eb1..88e8be433d 100644 --- a/P5/Source/Specs/titlePage.xml +++ b/P5/Source/Specs/titlePage.xml @@ -1,11 +1,4 @@ - - + title page diff --git a/P5/Source/Specs/titlePart.xml b/P5/Source/Specs/titlePart.xml index 521d72fc32..0e97fa4922 100644 --- a/P5/Source/Specs/titlePart.xml +++ b/P5/Source/Specs/titlePart.xml @@ -1,11 +1,4 @@ - - + title part diff --git a/P5/Source/Specs/titleStmt.xml b/P5/Source/Specs/titleStmt.xml index d7afe5f04a..783e8749e9 100644 --- a/P5/Source/Specs/titleStmt.xml +++ b/P5/Source/Specs/titleStmt.xml @@ -1,11 +1,4 @@ - - + title statement diff --git a/P5/Source/Specs/tns.xml b/P5/Source/Specs/tns.xml index 0d26a92827..8d292fd826 100644 --- a/P5/Source/Specs/tns.xml +++ b/P5/Source/Specs/tns.xml @@ -1,11 +1,4 @@ - - + diff --git a/P5/Source/Specs/trailer.xml b/P5/Source/Specs/trailer.xml index 40f438bf60..7253cb814f 100644 --- a/P5/Source/Specs/trailer.xml +++ b/P5/Source/Specs/trailer.xml @@ -1,11 +1,4 @@ - - + contains a closing title or footer appearing at the end of a division of a text. diff --git a/P5/Source/Specs/trait.xml b/P5/Source/Specs/trait.xml index 66504a0a6c..dc29afb298 100644 --- a/P5/Source/Specs/trait.xml +++ b/P5/Source/Specs/trait.xml @@ -1,10 +1,4 @@ - + trait trait distinctif contains a description of some status or quality attributed to a person, place, or organization typically, but not necessarily, diff --git a/P5/Source/Specs/transcriptionDesc.xml b/P5/Source/Specs/transcriptionDesc.xml index 963d3c1322..618c60aff7 100644 --- a/P5/Source/Specs/transcriptionDesc.xml +++ b/P5/Source/Specs/transcriptionDesc.xml @@ -1,9 +1,4 @@ - - + transcription description diff --git a/P5/Source/Specs/transpose.xml b/P5/Source/Specs/transpose.xml index eccfcdf492..1329f0e8b2 100644 --- a/P5/Source/Specs/transpose.xml +++ b/P5/Source/Specs/transpose.xml @@ -1,11 +1,4 @@ - - + describes a single textual transposition as an ordered list diff --git a/P5/Source/Specs/tree.xml b/P5/Source/Specs/tree.xml index 40b2592cc2..a73125c013 100644 --- a/P5/Source/Specs/tree.xml +++ b/P5/Source/Specs/tree.xml @@ -1,11 +1,4 @@ - - + tree diff --git a/P5/Source/Specs/triangle.xml b/P5/Source/Specs/triangle.xml index 3d2379cb77..4b746544c5 100644 --- a/P5/Source/Specs/triangle.xml +++ b/P5/Source/Specs/triangle.xml @@ -1,11 +1,4 @@ - - + underspecified embedding tree, so called because of its diff --git a/P5/Source/Specs/typeDesc.xml b/P5/Source/Specs/typeDesc.xml index 1f08d51997..49d5692505 100644 --- a/P5/Source/Specs/typeDesc.xml +++ b/P5/Source/Specs/typeDesc.xml @@ -1,11 +1,4 @@ - - + typeface description diff --git a/P5/Source/Specs/typeNote.xml b/P5/Source/Specs/typeNote.xml index 7d9e6910be..e5aea87904 100644 --- a/P5/Source/Specs/typeNote.xml +++ b/P5/Source/Specs/typeNote.xml @@ -1,11 +1,4 @@ - - + typographic note diff --git a/P5/Source/Specs/u.xml b/P5/Source/Specs/u.xml index 85cab0b1f2..886455ea40 100644 --- a/P5/Source/Specs/u.xml +++ b/P5/Source/Specs/u.xml @@ -1,11 +1,4 @@ - - + utterance diff --git a/P5/Source/Specs/unclear.xml b/P5/Source/Specs/unclear.xml index 9c6a936f18..55d644b6b8 100644 --- a/P5/Source/Specs/unclear.xml +++ b/P5/Source/Specs/unclear.xml @@ -1,11 +1,4 @@ - - + unclear diff --git a/P5/Source/Specs/undo.xml b/P5/Source/Specs/undo.xml index 6c5ac0c1fc..4b91a953e1 100644 --- a/P5/Source/Specs/undo.xml +++ b/P5/Source/Specs/undo.xml @@ -1,11 +1,4 @@ - - + indicates one or more marked-up interventions in a document diff --git a/P5/Source/Specs/unicodeProp.xml b/P5/Source/Specs/unicodeProp.xml index bd101b5109..f759a5680e 100644 --- a/P5/Source/Specs/unicodeProp.xml +++ b/P5/Source/Specs/unicodeProp.xml @@ -1,4 +1,4 @@ - + + - + contains a symbol, a word or a phrase referring to a unit of measurement in any kind of formal or informal system. diff --git a/P5/Source/Specs/unitDecl.xml b/P5/Source/Specs/unitDecl.xml index 3e979a9c6a..605de2d176 100644 --- a/P5/Source/Specs/unitDecl.xml +++ b/P5/Source/Specs/unitDecl.xml @@ -1,10 +1,4 @@ - + unit declarations provides information about units of measurement that are not members of the International System of Units. diff --git a/P5/Source/Specs/unitDef.xml b/P5/Source/Specs/unitDef.xml index ae46a30382..6710cd2cdf 100644 --- a/P5/Source/Specs/unitDef.xml +++ b/P5/Source/Specs/unitDef.xml @@ -1,10 +1,4 @@ - + unit definition contains descriptive information related to a specific unit of measurement. diff --git a/P5/Source/Specs/usg.xml b/P5/Source/Specs/usg.xml index 034131e3a8..e36a7412b3 100644 --- a/P5/Source/Specs/usg.xml +++ b/P5/Source/Specs/usg.xml @@ -1,11 +1,4 @@ - - + usage diff --git a/P5/Source/Specs/vAlt.xml b/P5/Source/Specs/vAlt.xml index d836d0410c..c16caa0f54 100644 --- a/P5/Source/Specs/vAlt.xml +++ b/P5/Source/Specs/vAlt.xml @@ -1,11 +1,4 @@ - - + value alternation diff --git a/P5/Source/Specs/vColl.xml b/P5/Source/Specs/vColl.xml index 6f2bb26e5c..14ad51e4fd 100644 --- a/P5/Source/Specs/vColl.xml +++ b/P5/Source/Specs/vColl.xml @@ -1,11 +1,4 @@ - - + collection of values diff --git a/P5/Source/Specs/vDefault.xml b/P5/Source/Specs/vDefault.xml index 4ec3347a7e..c09ac7b8ba 100644 --- a/P5/Source/Specs/vDefault.xml +++ b/P5/Source/Specs/vDefault.xml @@ -1,11 +1,4 @@ - - + value default diff --git a/P5/Source/Specs/vLabel.xml b/P5/Source/Specs/vLabel.xml index 531daeecc2..9a3afe2e03 100644 --- a/P5/Source/Specs/vLabel.xml +++ b/P5/Source/Specs/vLabel.xml @@ -1,11 +1,4 @@ - - + value label diff --git a/P5/Source/Specs/vMerge.xml b/P5/Source/Specs/vMerge.xml index e4f998ff28..fe135a153e 100644 --- a/P5/Source/Specs/vMerge.xml +++ b/P5/Source/Specs/vMerge.xml @@ -1,11 +1,4 @@ - - + merged collection of values diff --git a/P5/Source/Specs/vNot.xml b/P5/Source/Specs/vNot.xml index 53bd40e940..5eb473360a 100644 --- a/P5/Source/Specs/vNot.xml +++ b/P5/Source/Specs/vNot.xml @@ -1,11 +1,4 @@ - - + value negation diff --git a/P5/Source/Specs/vRange.xml b/P5/Source/Specs/vRange.xml index 8487f76541..1e01198ad0 100644 --- a/P5/Source/Specs/vRange.xml +++ b/P5/Source/Specs/vRange.xml @@ -1,11 +1,4 @@ - - + value range diff --git a/P5/Source/Specs/val.xml b/P5/Source/Specs/val.xml index 9b1819e57d..adc9675a45 100644 --- a/P5/Source/Specs/val.xml +++ b/P5/Source/Specs/val.xml @@ -1,11 +1,4 @@ - - + value diff --git a/P5/Source/Specs/valDesc.xml b/P5/Source/Specs/valDesc.xml index 972416ed92..65d03f1a79 100644 --- a/P5/Source/Specs/valDesc.xml +++ b/P5/Source/Specs/valDesc.xml @@ -1,11 +1,4 @@ - - + value description diff --git a/P5/Source/Specs/valItem.xml b/P5/Source/Specs/valItem.xml index c4e228718c..fab5338e0e 100644 --- a/P5/Source/Specs/valItem.xml +++ b/P5/Source/Specs/valItem.xml @@ -1,11 +1,4 @@ - - + documents a single value in a predefined list of values. diff --git a/P5/Source/Specs/valList.xml b/P5/Source/Specs/valList.xml index 270a0d05f5..5272421a27 100644 --- a/P5/Source/Specs/valList.xml +++ b/P5/Source/Specs/valList.xml @@ -1,11 +1,4 @@ - - + value list diff --git a/P5/Source/Specs/variantEncoding.xml b/P5/Source/Specs/variantEncoding.xml index 6c8c8fc94e..3648eedb2a 100644 --- a/P5/Source/Specs/variantEncoding.xml +++ b/P5/Source/Specs/variantEncoding.xml @@ -1,11 +1,4 @@ - - + variant encoding diff --git a/P5/Source/Specs/view.xml b/P5/Source/Specs/view.xml index aebc363a62..51ddf993cf 100644 --- a/P5/Source/Specs/view.xml +++ b/P5/Source/Specs/view.xml @@ -1,11 +1,4 @@ - - + view diff --git a/P5/Source/Specs/vocal.xml b/P5/Source/Specs/vocal.xml index fb278b2858..fc4d99cba3 100644 --- a/P5/Source/Specs/vocal.xml +++ b/P5/Source/Specs/vocal.xml @@ -1,11 +1,4 @@ - - + vocal diff --git a/P5/Source/Specs/w.xml b/P5/Source/Specs/w.xml index 606d7f8867..20e59131ae 100644 --- a/P5/Source/Specs/w.xml +++ b/P5/Source/Specs/w.xml @@ -1,11 +1,4 @@ - - + word diff --git a/P5/Source/Specs/watermark.xml b/P5/Source/Specs/watermark.xml index 8e4dec88ee..3c97949666 100644 --- a/P5/Source/Specs/watermark.xml +++ b/P5/Source/Specs/watermark.xml @@ -1,11 +1,4 @@ - - + watermark diff --git a/P5/Source/Specs/when.xml b/P5/Source/Specs/when.xml index 3f21a63129..859bc110cc 100644 --- a/P5/Source/Specs/when.xml +++ b/P5/Source/Specs/when.xml @@ -1,5 +1,4 @@ - - + indicates a point in time either relative to other elements in the same timeline tag, or absolutely. diff --git a/P5/Source/Specs/width.xml b/P5/Source/Specs/width.xml index 62855f778f..3613d9952e 100644 --- a/P5/Source/Specs/width.xml +++ b/P5/Source/Specs/width.xml @@ -1,11 +1,4 @@ - - + width diff --git a/P5/Source/Specs/wit.xml b/P5/Source/Specs/wit.xml index f153529f5f..084fa3989d 100644 --- a/P5/Source/Specs/wit.xml +++ b/P5/Source/Specs/wit.xml @@ -1,11 +1,4 @@ - - + wit diff --git a/P5/Source/Specs/witDetail.xml b/P5/Source/Specs/witDetail.xml index f9b40b0762..c7687ab897 100644 --- a/P5/Source/Specs/witDetail.xml +++ b/P5/Source/Specs/witDetail.xml @@ -1,11 +1,4 @@ - - + witness detail diff --git a/P5/Source/Specs/witEnd.xml b/P5/Source/Specs/witEnd.xml index 3a163c4ffa..011b9967bc 100644 --- a/P5/Source/Specs/witEnd.xml +++ b/P5/Source/Specs/witEnd.xml @@ -1,11 +1,4 @@ - - + fragmented witness end diff --git a/P5/Source/Specs/witStart.xml b/P5/Source/Specs/witStart.xml index 2c0569f149..37ef1986a6 100644 --- a/P5/Source/Specs/witStart.xml +++ b/P5/Source/Specs/witStart.xml @@ -1,11 +1,4 @@ - - + fragmented witness start diff --git a/P5/Source/Specs/witness.xml b/P5/Source/Specs/witness.xml index fc5c9f4550..9d77bcea17 100644 --- a/P5/Source/Specs/witness.xml +++ b/P5/Source/Specs/witness.xml @@ -1,11 +1,4 @@ - - + witness diff --git a/P5/Source/Specs/writing.xml b/P5/Source/Specs/writing.xml index d028c67a71..6f526b0324 100644 --- a/P5/Source/Specs/writing.xml +++ b/P5/Source/Specs/writing.xml @@ -1,11 +1,4 @@ - - + writing diff --git a/P5/Source/Specs/xenoData.xml b/P5/Source/Specs/xenoData.xml index 7448af8d57..dbb1df763b 100644 --- a/P5/Source/Specs/xenoData.xml +++ b/P5/Source/Specs/xenoData.xml @@ -1,11 +1,4 @@ - - + non-TEI metadata diff --git a/P5/Source/Specs/xr.xml b/P5/Source/Specs/xr.xml index 74fc97fed9..27fbc63be8 100644 --- a/P5/Source/Specs/xr.xml +++ b/P5/Source/Specs/xr.xml @@ -1,11 +1,4 @@ - - + cross-reference phrase diff --git a/P5/Source/Specs/zone.xml b/P5/Source/Specs/zone.xml index f7487b0ac8..7adee8a624 100644 --- a/P5/Source/Specs/zone.xml +++ b/P5/Source/Specs/zone.xml @@ -1,11 +1,4 @@ - - + defines any two-dimensional area within a surface From 9dff0770f0d06b70d116a34b2768ce13181707c1 Mon Sep 17 00:00:00 2001 From: Kiyonori Nagasaki Date: Wed, 14 Feb 2024 10:57:31 +0900 Subject: [PATCH 028/127] Update reg.xml --- P5/Source/Specs/reg.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/P5/Source/Specs/reg.xml b/P5/Source/Specs/reg.xml index 234e9c4971..891b63bbdc 100644 --- a/P5/Source/Specs/reg.xml +++ b/P5/Source/Specs/reg.xml @@ -11,7 +11,7 @@ regularization 정규화 一般化 - + 規則化 régularisation regularización regolarizzazione @@ -19,7 +19,7 @@ contains a reading which has been regularized or normalized in some sense. 어떤 면에서 정규화 또는 표준화된 해석을 포함한다. 標誌一般化或規格化處理過的文字。 - 正規化された読みを示す。 + 規則化された読みを示す。 contient une partie qui a été régularisée ou normalisée de façon quelconque contiene una lectura que ha sido regularizada o From 0b916f2bcd1bdb55fda4e5d01d44a1189538fe3c Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Sun, 18 Feb 2024 22:17:55 -0500 Subject: [PATCH 029/127] The actual work: remove deprecation constraint, limit to only 1 child in PureODD content model. --- P5/Source/Specs/content.xml | 42 +++---------------------------------- 1 file changed, 3 insertions(+), 39 deletions(-) diff --git a/P5/Source/Specs/content.xml b/P5/Source/Specs/content.xml index c6992d6bf6..313f866f49 100644 --- a/P5/Source/Specs/content.xml +++ b/P5/Source/Specs/content.xml @@ -18,12 +18,9 @@ $Id$ 기록된 스키마에 대한 선언 텍스트를 포함한다. 包含所記錄之模型的宣告文字。 当該スキーマの宣言を示す。 - contient la déclaration - d'un modèle de contenu pour le schéma documenté. - contiene el texto de la - declaración del esquema utilizado. - contiene il testo di - una dichiarazione dello schema utilizzato + contient la déclaration d'un modèle de contenu pour le schéma documenté. + contiene el texto de la declaración del esquema utilizado. + contiene il testo di una dichiarazione dello schema utilizzato @@ -34,39 +31,6 @@ $Id$ - - A temporary constraint to give users a warning that in the - future the content of content will be restricted to 1 and - only 1 child element. - - - - - - - - - - - - - - - - - - which could be wrapped in a <sequence> element. - - - which could be wrapped in an <rng:div> element. - - - but those children are neither all TEI elements nor - all RELAX NG elements, and thus this <content> is invalid and can not be easily rectified. - - - - controls whether or From e927c76e1d1ae516f8161ce2595995066c77f7d7 Mon Sep 17 00:00:00 2001 From: Klaus Rettinghaus Date: Sat, 24 Feb 2024 17:55:16 +0100 Subject: [PATCH 030/127] Remove superfluous namespace declarations (#2522) * remove unneeded extra declaration of tei namespace * remove unneeded schematron namespace --- P5/Source/Specs/teidata.authority.xml | 3 +-- P5/Source/Specs/teidata.certainty.xml | 2 +- P5/Source/Specs/teidata.count.xml | 2 +- P5/Source/Specs/teidata.duration.iso.xml | 2 +- P5/Source/Specs/teidata.duration.w3c.xml | 2 +- P5/Source/Specs/teidata.enumerated.xml | 2 +- P5/Source/Specs/teidata.gender.xml | 3 +-- P5/Source/Specs/teidata.interval.xml | 2 +- P5/Source/Specs/teidata.key.xml | 6 ++---- P5/Source/Specs/teidata.language.xml | 2 +- P5/Source/Specs/teidata.name.xml | 2 +- P5/Source/Specs/teidata.namespace.xml | 2 +- P5/Source/Specs/teidata.namespaceOrName.xml | 6 ++---- P5/Source/Specs/teidata.nullOrName.xml | 17 +++++++---------- P5/Source/Specs/teidata.numeric.xml | 2 +- P5/Source/Specs/teidata.outputMeasurement.xml | 2 +- P5/Source/Specs/teidata.point.xml | 2 +- P5/Source/Specs/teidata.pointer.xml | 2 +- P5/Source/Specs/teidata.prefix.xml | 5 +---- P5/Source/Specs/teidata.probCert.xml | 19 +++++++++---------- P5/Source/Specs/teidata.probability.xml | 2 +- P5/Source/Specs/teidata.replacement.xml | 2 +- P5/Source/Specs/teidata.sex.xml | 3 +-- P5/Source/Specs/teidata.temporal.iso.xml | 2 +- P5/Source/Specs/teidata.temporal.w3c.xml | 2 +- P5/Source/Specs/teidata.temporal.working.xml | 4 +--- P5/Source/Specs/teidata.text.xml | 2 +- P5/Source/Specs/teidata.truthValue.xml | 2 +- P5/Source/Specs/teidata.version.xml | 2 +- P5/Source/Specs/teidata.versionNumber.xml | 2 +- P5/Source/Specs/teidata.word.xml | 2 +- P5/Source/Specs/teidata.xTruthValue.xml | 2 +- P5/Source/Specs/teidata.xmlName.xml | 2 +- P5/Source/Specs/teidata.xpath.xml | 2 +- 34 files changed, 50 insertions(+), 66 deletions(-) diff --git a/P5/Source/Specs/teidata.authority.xml b/P5/Source/Specs/teidata.authority.xml index 6720a61dbc..321c63bb11 100644 --- a/P5/Source/Specs/teidata.authority.xml +++ b/P5/Source/Specs/teidata.authority.xml @@ -5,8 +5,7 @@ Dual-licensed under CC-by and BSD2 licences See the file COPYING.txt for details --> - + defines attribute values which derive from an authority list, which may be an enumerated list defined in the document's schema, a list or taxonomy elsewhere in the document, or an online taxonomy, gazetteer, or other authority. diff --git a/P5/Source/Specs/teidata.certainty.xml b/P5/Source/Specs/teidata.certainty.xml index 2797de8577..4588ae4666 100644 --- a/P5/Source/Specs/teidata.certainty.xml +++ b/P5/Source/Specs/teidata.certainty.xml @@ -5,7 +5,7 @@ Dual-licensed under CC-by and BSD2 licences See the file COPYING.txt for details --> - + defines the range of attribute values expressing a degree of certainty. 확실성 정도를 표현하는 속성 값의 범위를 정의한다. 定義表示正確度的屬性值範圍 diff --git a/P5/Source/Specs/teidata.count.xml b/P5/Source/Specs/teidata.count.xml index 7b428db4c4..a0ea1201a8 100644 --- a/P5/Source/Specs/teidata.count.xml +++ b/P5/Source/Specs/teidata.count.xml @@ -5,7 +5,7 @@ Dual-licensed under CC-by and BSD2 licences See the file COPYING.txt for details --> - + defines the range of attribute values used for a non-negative integer value used as a count. 계산으로 사용된 음이 아닌 정수 값의 속성 값 범위를 정의한다. diff --git a/P5/Source/Specs/teidata.duration.iso.xml b/P5/Source/Specs/teidata.duration.iso.xml index 49127a8f98..6b166b4d8c 100644 --- a/P5/Source/Specs/teidata.duration.iso.xml +++ b/P5/Source/Specs/teidata.duration.iso.xml @@ -5,7 +5,7 @@ Dual-licensed under CC-by and BSD2 licences See the file COPYING.txt for details --> - + defines the range of attribute values available for representation of a duration in time using ISO 8601 standard formats ISO 8601 표준 형식을 사용하여 시간의 지속을 나타내는 속성 값 범위를 정의한다. diff --git a/P5/Source/Specs/teidata.duration.w3c.xml b/P5/Source/Specs/teidata.duration.w3c.xml index 368724d72c..2f81b598a8 100644 --- a/P5/Source/Specs/teidata.duration.w3c.xml +++ b/P5/Source/Specs/teidata.duration.w3c.xml @@ -5,7 +5,7 @@ Dual-licensed under CC-by and BSD2 licences See the file COPYING.txt for details --> - + defines the range of attribute values available for representation of a duration in time using W3C datatypes. W3C 데이터 유형을 사용해서 시간 지속을 나타내는 속성 값 범위를 정의한다. 以W3C datatypes標準格式來定義表示一段持續性時間的屬性值範圍 diff --git a/P5/Source/Specs/teidata.enumerated.xml b/P5/Source/Specs/teidata.enumerated.xml index 8a951c8229..a87d86bc62 100644 --- a/P5/Source/Specs/teidata.enumerated.xml +++ b/P5/Source/Specs/teidata.enumerated.xml @@ -5,7 +5,7 @@ Dual-licensed under CC-by and BSD2 licences See the file COPYING.txt for details --> - + defines the range of attribute values expressed as a single XML name taken from a list of documented possibilities. 기록된 확률의 목록으로부터 얻어진 단일 XML 이름으로 표현된 속성 값 범위를 정의한다. diff --git a/P5/Source/Specs/teidata.gender.xml b/P5/Source/Specs/teidata.gender.xml index 9207d6cf87..cd30ed7c93 100644 --- a/P5/Source/Specs/teidata.gender.xml +++ b/P5/Source/Specs/teidata.gender.xml @@ -4,8 +4,7 @@ Dual-licensed under CC-by and BSD2 licences See the file COPYING.txt for details --> - + defines the range of attribute values used to represent the gender of a person, persona, or character. diff --git a/P5/Source/Specs/teidata.interval.xml b/P5/Source/Specs/teidata.interval.xml index f6b7eaf5d9..a5d52e8fa4 100644 --- a/P5/Source/Specs/teidata.interval.xml +++ b/P5/Source/Specs/teidata.interval.xml @@ -5,7 +5,7 @@ Dual-licensed under CC-by and BSD2 licences See the file COPYING.txt for details --> - + defines attribute values used to express an interval value. diff --git a/P5/Source/Specs/teidata.key.xml b/P5/Source/Specs/teidata.key.xml index a6dd428ed5..3750cf828b 100644 --- a/P5/Source/Specs/teidata.key.xml +++ b/P5/Source/Specs/teidata.key.xml @@ -3,10 +3,8 @@ Copyright TEI Consortium. Dual-licensed under CC-by and BSD2 licences See the file COPYING.txt for details --> - + + defines the range of attribute values expressing a coded value by means of an arbitrary identifier, typically taken from a set of externally-defined possibilities. diff --git a/P5/Source/Specs/teidata.language.xml b/P5/Source/Specs/teidata.language.xml index 260e1d749b..cbca7bbc29 100644 --- a/P5/Source/Specs/teidata.language.xml +++ b/P5/Source/Specs/teidata.language.xml @@ -5,7 +5,7 @@ Dual-licensed under CC-by and BSD2 licences See the file COPYING.txt for details --> - + defines the range of attribute values used to identify a particular combination of human language and writing system. 인간의 언어와 문자 체계의 특별한 조합을 식별하는 속성 값 범위를 정의한다. diff --git a/P5/Source/Specs/teidata.name.xml b/P5/Source/Specs/teidata.name.xml index 4d1547a933..7eae21c601 100644 --- a/P5/Source/Specs/teidata.name.xml +++ b/P5/Source/Specs/teidata.name.xml @@ -5,7 +5,7 @@ Dual-licensed under CC-by and BSD2 licences See the file COPYING.txt for details --> - + defines the range of attribute values expressed as an XML Name. XML 이름으로 표현되는 속성 값 범위를 정의한다. 定義的屬性值範圍以XML名稱或識別符碼表示 diff --git a/P5/Source/Specs/teidata.namespace.xml b/P5/Source/Specs/teidata.namespace.xml index be9efb9202..cbbf49d97b 100644 --- a/P5/Source/Specs/teidata.namespace.xml +++ b/P5/Source/Specs/teidata.namespace.xml @@ -5,7 +5,7 @@ Dual-licensed under CC-by and BSD2 licences See the file COPYING.txt for details --> - + defines the range of attribute values used to indicate XML namespaces as defined by the W3C Namespaces in XML Technical Recommendation. diff --git a/P5/Source/Specs/teidata.namespaceOrName.xml b/P5/Source/Specs/teidata.namespaceOrName.xml index 98db1a8eca..5eb9121216 100644 --- a/P5/Source/Specs/teidata.namespaceOrName.xml +++ b/P5/Source/Specs/teidata.namespaceOrName.xml @@ -4,10 +4,8 @@ Copyright TEI Consortium. Dual-licensed under CC-by and BSD2 licences See the file COPYING.txt for details --> - + + defines attribute values which contain either an absolute namespace URI or a qualified XML name. diff --git a/P5/Source/Specs/teidata.nullOrName.xml b/P5/Source/Specs/teidata.nullOrName.xml index 535adea412..4ce729a8fc 100644 --- a/P5/Source/Specs/teidata.nullOrName.xml +++ b/P5/Source/Specs/teidata.nullOrName.xml @@ -3,20 +3,17 @@ Copyright TEI Consortium. Dual-licensed under CC-by and BSD2 licences See the file COPYING.txt for details --> - + + defines attribute values which contain either the null string or an XML name. - - - - + + + + - +

The rules defining an XML name form a part of the XML Specification.

 diff --git a/P5/Source/Specs/teidata.numeric.xml b/P5/Source/Specs/teidata.numeric.xml index 4e5e249e71..dbca4b4836 100644 --- a/P5/Source/Specs/teidata.numeric.xml +++ b/P5/Source/Specs/teidata.numeric.xml @@ -5,7 +5,7 @@ Dual-licensed under CC-by and BSD2 licences See the file COPYING.txt for details --> - + defines the range of attribute values used for numeric values. 수치에 사용되는 속성 값의 범위를 정의한다. 定義用於數值的屬性值範圍 diff --git a/P5/Source/Specs/teidata.outputMeasurement.xml b/P5/Source/Specs/teidata.outputMeasurement.xml index d155d5ba5c..3d22c24dfc 100644 --- a/P5/Source/Specs/teidata.outputMeasurement.xml +++ b/P5/Source/Specs/teidata.outputMeasurement.xml @@ -5,7 +5,7 @@ Dual-licensed under CC-by and BSD2 licences See the file COPYING.txt for details --> - + defines a range of values for use in specifying the size of an object that is intended for display. 웹에서 디스플레이 목적의 대상 크기를 명시하는 값의 범위를 정의한다. diff --git a/P5/Source/Specs/teidata.point.xml b/P5/Source/Specs/teidata.point.xml index d4a688b1e2..719040c7d1 100644 --- a/P5/Source/Specs/teidata.point.xml +++ b/P5/Source/Specs/teidata.point.xml @@ -5,7 +5,7 @@ Dual-licensed under CC-by and BSD2 licences See the file COPYING.txt for details --> - + defines the data type used to express a point in cartesian space. diff --git a/P5/Source/Specs/teidata.pointer.xml b/P5/Source/Specs/teidata.pointer.xml index e4caa5e874..e3dbbb23da 100644 --- a/P5/Source/Specs/teidata.pointer.xml +++ b/P5/Source/Specs/teidata.pointer.xml @@ -5,7 +5,7 @@ Dual-licensed under CC-by and BSD2 licences See the file COPYING.txt for details --> - + defines the range of attribute values used to provide a single URI, absolute or relative, pointing to some other resource, either within the current document or elsewhere. diff --git a/P5/Source/Specs/teidata.prefix.xml b/P5/Source/Specs/teidata.prefix.xml index 9b65e7770d..874fc5bc9d 100644 --- a/P5/Source/Specs/teidata.prefix.xml +++ b/P5/Source/Specs/teidata.prefix.xml @@ -6,10 +6,7 @@ See the file COPYING.txt for details - + defines a range of values that may function as a URI scheme name. diff --git a/P5/Source/Specs/teidata.probCert.xml b/P5/Source/Specs/teidata.probCert.xml index 86ca7d96d1..fdd2e82c80 100644 --- a/P5/Source/Specs/teidata.probCert.xml +++ b/P5/Source/Specs/teidata.probCert.xml @@ -3,16 +3,15 @@ Copyright TEI Consortium. Dual-licensed under CC-by and BSD2 licences See the file COPYING.txt for details --> - + + defines a range of attribute values which can be expressed either as a numeric probability or as a coded certainty value. - - - - + xml:lang="en">defines a range of attribute values which can be expressed either as a numeric + probability or as a coded certainty value. + + + + + - diff --git a/P5/Source/Specs/teidata.probability.xml b/P5/Source/Specs/teidata.probability.xml index 8ca88a9656..a3974fea69 100644 --- a/P5/Source/Specs/teidata.probability.xml +++ b/P5/Source/Specs/teidata.probability.xml @@ -5,7 +5,7 @@ Dual-licensed under CC-by and BSD2 licences See the file COPYING.txt for details --> - + defines the range of attribute values expressing a probability. 확률을 표현하는 속성 값의 범위를 정의한다. 定義表示可能性的屬性值範圍 diff --git a/P5/Source/Specs/teidata.replacement.xml b/P5/Source/Specs/teidata.replacement.xml index b1631c6fbc..c00fd6751d 100644 --- a/P5/Source/Specs/teidata.replacement.xml +++ b/P5/Source/Specs/teidata.replacement.xml @@ -5,7 +5,7 @@ Dual-licensed under CC-by and BSD2 licences See the file COPYING.txt for details --> - + defines attribute values which contain a replacement template. diff --git a/P5/Source/Specs/teidata.sex.xml b/P5/Source/Specs/teidata.sex.xml index 8ee18792d3..e454d1d96a 100644 --- a/P5/Source/Specs/teidata.sex.xml +++ b/P5/Source/Specs/teidata.sex.xml @@ -4,8 +4,7 @@ Dual-licensed under CC-by and BSD2 licences See the file COPYING.txt for details --> - + defines the range of attribute values used to identify the sex of an organism. 인간 또는 동물의 성을 식별하는 속성 값 범위를 정의한다. diff --git a/P5/Source/Specs/teidata.temporal.iso.xml b/P5/Source/Specs/teidata.temporal.iso.xml index adacbd23ff..1d558db181 100644 --- a/P5/Source/Specs/teidata.temporal.iso.xml +++ b/P5/Source/Specs/teidata.temporal.iso.xml @@ -5,7 +5,7 @@ Dual-licensed under CC-by and BSD2 licences See the file COPYING.txt for details --> - + defines the range of attribute values expressing a temporal expression such as a date, a time, or a combination of them, that conform to the international standard Data elements and interchange formats – Information interchange – Representation of dates and times. diff --git a/P5/Source/Specs/teidata.temporal.w3c.xml b/P5/Source/Specs/teidata.temporal.w3c.xml index c79a6bc9a6..45f260e5d7 100644 --- a/P5/Source/Specs/teidata.temporal.w3c.xml +++ b/P5/Source/Specs/teidata.temporal.w3c.xml @@ -5,7 +5,7 @@ Dual-licensed under CC-by and BSD2 licences See the file COPYING.txt for details --> - + defines the range of attribute values expressing a temporal expression such as a date, a time, or a combination of them, that conform to the W3C XML Schema Part 2: Datatypes Second Edition diff --git a/P5/Source/Specs/teidata.temporal.working.xml b/P5/Source/Specs/teidata.temporal.working.xml index 494dc701de..df7ea2d256 100644 --- a/P5/Source/Specs/teidata.temporal.working.xml +++ b/P5/Source/Specs/teidata.temporal.working.xml @@ -4,9 +4,7 @@ Dual-licensed under CC-by and BSD2 licences See the file COPYING.txt for details --> - + defines the range of values, conforming to the W3C XML Schema Part 2: Datatypes Second Edition specification, expressing a date or diff --git a/P5/Source/Specs/teidata.text.xml b/P5/Source/Specs/teidata.text.xml index f7caf8ccc6..9c154bfe0f 100644 --- a/P5/Source/Specs/teidata.text.xml +++ b/P5/Source/Specs/teidata.text.xml @@ -5,7 +5,7 @@ Dual-licensed under CC-by and BSD2 licences See the file COPYING.txt for details --> - + defines the range of attribute values used to express some kind of identifying string as a single sequence of Unicode characters possibly including whitespace. diff --git a/P5/Source/Specs/teidata.truthValue.xml b/P5/Source/Specs/teidata.truthValue.xml index 50300365eb..0d5c1318d0 100644 --- a/P5/Source/Specs/teidata.truthValue.xml +++ b/P5/Source/Specs/teidata.truthValue.xml @@ -5,7 +5,7 @@ Dual-licensed under CC-by and BSD2 licences See the file COPYING.txt for details --> - + defines the range of attribute values used to express a truth value. 진리값을 표현하는 속성 값 범위를 정의한다. diff --git a/P5/Source/Specs/teidata.version.xml b/P5/Source/Specs/teidata.version.xml index 2addc9bf52..c07a477aca 100644 --- a/P5/Source/Specs/teidata.version.xml +++ b/P5/Source/Specs/teidata.version.xml @@ -5,7 +5,7 @@ Dual-licensed under CC-by and BSD2 licences See the file COPYING.txt for details --> - + defines the range of attribute values which may be used to specify a TEI or Unicode version number. définit la gamme des valeurs d'attribut diff --git a/P5/Source/Specs/teidata.versionNumber.xml b/P5/Source/Specs/teidata.versionNumber.xml index 95246f4f14..fc634c6d75 100644 --- a/P5/Source/Specs/teidata.versionNumber.xml +++ b/P5/Source/Specs/teidata.versionNumber.xml @@ -5,7 +5,7 @@ Dual-licensed under CC-by and BSD2 licences See the file COPYING.txt for details --> - + defines the range of attribute values used for version numbers. diff --git a/P5/Source/Specs/teidata.word.xml b/P5/Source/Specs/teidata.word.xml index edd11ce673..e99c5a8493 100644 --- a/P5/Source/Specs/teidata.word.xml +++ b/P5/Source/Specs/teidata.word.xml @@ -5,7 +5,7 @@ Dual-licensed under CC-by and BSD2 licences See the file COPYING.txt for details --> - + defines the range of attribute values expressed as a single word or token. 단일 단어 또는 토큰으로 표현된 속성 값 범위를 정의한다. diff --git a/P5/Source/Specs/teidata.xTruthValue.xml b/P5/Source/Specs/teidata.xTruthValue.xml index b63a6ec2bb..79baaf2e99 100644 --- a/P5/Source/Specs/teidata.xTruthValue.xml +++ b/P5/Source/Specs/teidata.xTruthValue.xml @@ -5,7 +5,7 @@ Dual-licensed under CC-by and BSD2 licences See the file COPYING.txt for details --> - + extended truth value 확장 진리값 diff --git a/P5/Source/Specs/teidata.xmlName.xml b/P5/Source/Specs/teidata.xmlName.xml index 303bd567c7..63451806ac 100644 --- a/P5/Source/Specs/teidata.xmlName.xml +++ b/P5/Source/Specs/teidata.xmlName.xml @@ -5,7 +5,7 @@ Dual-licensed under CC-by and BSD2 licences See the file COPYING.txt for details --> - + defines attribute values which contain an XML name. diff --git a/P5/Source/Specs/teidata.xpath.xml b/P5/Source/Specs/teidata.xpath.xml index 8ace6486cd..e93b41378a 100644 --- a/P5/Source/Specs/teidata.xpath.xml +++ b/P5/Source/Specs/teidata.xpath.xml @@ -5,7 +5,7 @@ See the file COPYING.txt for details --> - + defines attribute values which contain an XPath expression. From 5c9112111df403d0621864c7cea1e8fece9762bc Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Sat, 24 Feb 2024 16:36:51 -0500 Subject: [PATCH 031/127] =?UTF-8?q?Oops=20=E2=80=94=20forgot=20XML=20decls?= =?UTF-8?q?.=20Thanks=20to=20@joeytakeda=20for=20noticing?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- P5/Source/Guidelines/en/AB-About.xml | 1 + .../Guidelines/en/AI-AnalyticMechanisms.xml | 1 + .../Guidelines/en/CC-LanguageCorpora.xml | 1 + .../en/CE-CertaintyResponsibility.xml | 1 + .../en/CH-LanguagesCharacterSets.xml | 1 + P5/Source/Guidelines/en/CO-CoreElements.xml | 1 + P5/Source/Guidelines/en/COL-Colophon.xml | 1 + P5/Source/Guidelines/en/DEPRECATIONS.xml | 1 + .../Guidelines/en/DI-PrintDictionaries.xml | 1 + .../Guidelines/en/DR-PerformanceTexts.xml | 1 + .../Guidelines/en/DS-DefaultTextStructure.xml | 1 + P5/Source/Guidelines/en/Dedication.xml | 1 + .../Guidelines/en/FM1-IntroductoryNote.xml | 1 + .../Guidelines/en/FS-FeatureStructures.xml | 1 + .../en/FT-TablesFormulaeGraphics.xml | 1 + .../Guidelines/en/GD-GraphsNetworksTrees.xml | 1 + P5/Source/Guidelines/en/HD-Header.xml | 1 + .../en/MS-ManuscriptDescription.xml | 1 + P5/Source/Guidelines/en/ND-NamesDates.xml | 1 + .../Guidelines/en/NH-Non-hierarchical.xml | 1 + P5/Source/Guidelines/en/PARTIND.xml | 1 + P5/Source/Guidelines/en/PH-PrimarySources.xml | 1 + P5/Source/Guidelines/en/PrefatoryNote.xml | 1 + P5/Source/Guidelines/en/REF-ATTRIBUTES.xml | 1 + P5/Source/Guidelines/en/REF-CLASSES-ATTS.xml | 1 + P5/Source/Guidelines/en/REF-CLASSES-MODEL.xml | 1 + P5/Source/Guidelines/en/REF-ELEMENTS.xml | 1 + P5/Source/Guidelines/en/REF-MACROS.xml | 1 + .../en/SA-LinkingSegmentationAlignment.xml | 1 + .../Guidelines/en/SG-GentleIntroduction.xml | 1 + P5/Source/Guidelines/en/ST-Infrastructure.xml | 1 + .../Guidelines/en/TC-CriticalApparatus.xml | 1 + .../en/TD-DocumentationElements.xml | 1 + .../en/TS-TranscriptionsofSpeech.xml | 1 + P5/Source/Guidelines/en/TitlePageVerso.xml | 1 + P5/Source/Guidelines/en/USE.xml | 1 + P5/Source/Guidelines/en/VE-Verse.xml | 1 + .../en/WD-NonStandardCharacters.xml | 1 + P5/Source/Guidelines/fr/AB-About.xml | 839 ++- .../Guidelines/fr/AI-AnalyticMechanisms.xml | 1236 +++- P5/Source/Guidelines/fr/BIB-Bibliography.xml | 6370 ++++++++++++++++- .../Guidelines/fr/CC-LanguageCorpora.xml | 1161 ++- .../fr/CE-CertaintyResponsibility.xml | 612 +- .../fr/CH-LanguagesCharacterSets.xml | 716 +- P5/Source/Guidelines/fr/CO-CoreElements.xml | 6014 +++++++++++++++- P5/Source/Guidelines/fr/COL-Colophon.xml | 39 +- .../Guidelines/fr/DI-PrintDictionaries.xml | 3107 +++++++- .../Guidelines/fr/DR-PerformanceTexts.xml | 1457 +++- .../Guidelines/fr/DS-DefaultTextStructure.xml | 1835 ++++- P5/Source/Guidelines/fr/Dedication.xml | 25 +- .../Guidelines/fr/FM1-IntroductoryNote.xml | 302 +- .../Guidelines/fr/FS-FeatureStructures.xml | 2026 +++++- .../fr/FT-TablesFormulaeGraphics.xml | 1106 ++- .../Guidelines/fr/GD-GraphsNetworksTrees.xml | 1500 +++- P5/Source/Guidelines/fr/HD-Header.xml | 1 + .../fr/MS-ManuscriptDescription.xml | 2572 ++++++- P5/Source/Guidelines/fr/ND-NamesDates.xml | 3060 +++++++- .../Guidelines/fr/NH-Non-hierarchical.xml | 825 ++- P5/Source/Guidelines/fr/PARTIND.xml | 11 +- P5/Source/Guidelines/fr/PH-PrimarySources.xml | 3060 +++++++- P5/Source/Guidelines/fr/PrefatoryNote.xml | 675 +- P5/Source/Guidelines/fr/REF-ATTRIBUTES.xml | 16 +- P5/Source/Guidelines/fr/REF-CLASSES-ATTS.xml | 17 +- P5/Source/Guidelines/fr/REF-CLASSES-MODEL.xml | 16 +- P5/Source/Guidelines/fr/REF-ELEMENTS.xml | 23 +- P5/Source/Guidelines/fr/REF-MACROS.xml | 16 +- .../fr/SA-LinkingSegmentationAlignment.xml | 3506 ++++++++- .../Guidelines/fr/SG-GentleIntroduction.xml | 1474 +++- P5/Source/Guidelines/fr/ST-Infrastructure.xml | 1426 +++- .../Guidelines/fr/TC-CriticalApparatus.xml | 1240 +++- .../fr/TD-DocumentationElements.xml | 2165 +++++- .../fr/TS-TranscriptionsofSpeech.xml | 1471 +++- P5/Source/Guidelines/fr/TitlePageVerso.xml | 23 +- P5/Source/Guidelines/fr/USE.xml | 2316 +++++- P5/Source/Guidelines/fr/VE-Verse.xml | 917 ++- .../fr/WD-NonStandardCharacters.xml | 1330 +++- P5/Source/Specs/TEI.xml | 1 + P5/Source/Specs/ab.xml | 1 + P5/Source/Specs/abbr.xml | 1 + P5/Source/Specs/abstract.xml | 1 + P5/Source/Specs/accMat.xml | 1 + P5/Source/Specs/actor.xml | 1 + P5/Source/Specs/add.xml | 1 + P5/Source/Specs/addName.xml | 1 + P5/Source/Specs/addSpan.xml | 1 + P5/Source/Specs/additional.xml | 1 + P5/Source/Specs/additions.xml | 1 + P5/Source/Specs/addrLine.xml | 1 + P5/Source/Specs/address.xml | 1 + P5/Source/Specs/adminInfo.xml | 1 + P5/Source/Specs/alt.xml | 1 + P5/Source/Specs/altGrp.xml | 1 + P5/Source/Specs/altIdent.xml | 1 + P5/Source/Specs/alternate.xml | 1 + P5/Source/Specs/am.xml | 1 + P5/Source/Specs/analytic.xml | 1 + P5/Source/Specs/anchor.xml | 1 + P5/Source/Specs/annotation.xml | 1 + P5/Source/Specs/annotationBlock.xml | 1 + P5/Source/Specs/anyElement.xml | 1 + P5/Source/Specs/app.xml | 1 + P5/Source/Specs/appInfo.xml | 1 + P5/Source/Specs/arc.xml | 1 + P5/Source/Specs/argument.xml | 1 + P5/Source/Specs/att.anchoring.xml | 1 + P5/Source/Specs/att.ascribed.directed.xml | 1 + P5/Source/Specs/att.ascribed.xml | 1 + P5/Source/Specs/att.breaking.xml | 1 + P5/Source/Specs/att.cReferencing.xml | 1 + P5/Source/Specs/att.calendarSystem.xml | 1 + P5/Source/Specs/att.canonical.xml | 1 + P5/Source/Specs/att.citeStructurePart.xml | 1 + P5/Source/Specs/att.citing.xml | 1 + P5/Source/Specs/att.combinable.xml | 1 + P5/Source/Specs/att.coordinated.xml | 1 + P5/Source/Specs/att.damaged.xml | 1 + P5/Source/Specs/att.datable.custom.xml | 1 + P5/Source/Specs/att.datable.iso.xml | 1 + P5/Source/Specs/att.datable.w3c.xml | 1 + P5/Source/Specs/att.datable.xml | 1 + P5/Source/Specs/att.datcat.xml | 1 + P5/Source/Specs/att.declarable.xml | 1 + P5/Source/Specs/att.declaring.xml | 1 + P5/Source/Specs/att.deprecated.xml | 1 + P5/Source/Specs/att.dimensions.xml | 1 + P5/Source/Specs/att.divLike.xml | 1 + P5/Source/Specs/att.docStatus.xml | 1 + P5/Source/Specs/att.duration.iso.xml | 1 + P5/Source/Specs/att.duration.w3c.xml | 1 + P5/Source/Specs/att.duration.xml | 1 + P5/Source/Specs/att.editLike.xml | 1 + P5/Source/Specs/att.edition.xml | 1 + P5/Source/Specs/att.enjamb.xml | 1 + P5/Source/Specs/att.entryLike.xml | 1 + P5/Source/Specs/att.formula.xml | 1 + P5/Source/Specs/att.fragmentable.xml | 1 + P5/Source/Specs/att.gaijiProp.xml | 1 + P5/Source/Specs/att.global.analytic.xml | 1 + P5/Source/Specs/att.global.change.xml | 1 + P5/Source/Specs/att.global.facs.xml | 1 + P5/Source/Specs/att.global.linking.xml | 1 + P5/Source/Specs/att.global.rendition.xml | 1 + P5/Source/Specs/att.global.responsibility.xml | 1 + P5/Source/Specs/att.global.source.xml | 1 + P5/Source/Specs/att.global.xml | 1 + P5/Source/Specs/att.handFeatures.xml | 1 + P5/Source/Specs/att.identified.xml | 1 + P5/Source/Specs/att.internetMedia.xml | 1 + P5/Source/Specs/att.interpLike.xml | 1 + P5/Source/Specs/att.lexicographic.xml | 1 + P5/Source/Specs/att.linguistic.xml | 1 + P5/Source/Specs/att.locatable.xml | 1 + P5/Source/Specs/att.measurement.xml | 1 + P5/Source/Specs/att.media.xml | 1 + P5/Source/Specs/att.metrical.xml | 1 + P5/Source/Specs/att.milestoneUnit.xml | 1 + P5/Source/Specs/att.msClass.xml | 1 + P5/Source/Specs/att.msExcerpt.xml | 1 + P5/Source/Specs/att.namespaceable.xml | 1 + P5/Source/Specs/att.naming.xml | 1 + P5/Source/Specs/att.notated.xml | 1 + P5/Source/Specs/att.partials.xml | 1 + P5/Source/Specs/att.patternReplacement.xml | 1 + P5/Source/Specs/att.personal.xml | 1 + P5/Source/Specs/att.placement.xml | 1 + P5/Source/Specs/att.pointing.group.xml | 1 + P5/Source/Specs/att.pointing.xml | 1 + P5/Source/Specs/att.predicate.xml | 1 + P5/Source/Specs/att.ranging.xml | 1 + P5/Source/Specs/att.rdgPart.xml | 1 + P5/Source/Specs/att.repeatable.xml | 1 + P5/Source/Specs/att.resourced.xml | 1 + P5/Source/Specs/att.scoping.xml | 1 + P5/Source/Specs/att.segLike.xml | 1 + P5/Source/Specs/att.sortable.xml | 1 + P5/Source/Specs/att.spanning.xml | 1 + P5/Source/Specs/att.styleDef.xml | 1 + P5/Source/Specs/att.tableDecoration.xml | 1 + P5/Source/Specs/att.textCritical.xml | 1 + P5/Source/Specs/att.timed.xml | 1 + P5/Source/Specs/att.transcriptional.xml | 1 + P5/Source/Specs/att.translatable.xml | 1 + P5/Source/Specs/att.typed.xml | 1 + P5/Source/Specs/att.witnessed.xml | 1 + P5/Source/Specs/att.written.xml | 1 + P5/Source/Specs/att.xml | 1 + P5/Source/Specs/attDef.xml | 1 + P5/Source/Specs/attList.xml | 1 + P5/Source/Specs/attRef.xml | 1 + P5/Source/Specs/authority.xml | 1 + P5/Source/Specs/availability.xml | 1 + P5/Source/Specs/back.xml | 1 + P5/Source/Specs/bibl.xml | 1 + P5/Source/Specs/biblFull.xml | 1 + P5/Source/Specs/biblScope.xml | 1 + P5/Source/Specs/biblStruct.xml | 1 + P5/Source/Specs/bicond.xml | 1 + P5/Source/Specs/binary.xml | 1 + P5/Source/Specs/binaryObject.xml | 1 + P5/Source/Specs/bindingDesc.xml | 1 + P5/Source/Specs/body.xml | 1 + P5/Source/Specs/broadcast.xml | 1 + P5/Source/Specs/byline.xml | 1 + P5/Source/Specs/c.xml | 1 + P5/Source/Specs/cRefPattern.xml | 1 + P5/Source/Specs/caesura.xml | 1 + P5/Source/Specs/calendar.xml | 1 + P5/Source/Specs/calendarDesc.xml | 1 + P5/Source/Specs/camera.xml | 1 + P5/Source/Specs/caption.xml | 1 + P5/Source/Specs/case.xml | 1 + P5/Source/Specs/castGroup.xml | 1 + P5/Source/Specs/castItem.xml | 1 + P5/Source/Specs/castList.xml | 1 + P5/Source/Specs/catDesc.xml | 1 + P5/Source/Specs/catRef.xml | 1 + P5/Source/Specs/catchwords.xml | 1 + P5/Source/Specs/category.xml | 1 + P5/Source/Specs/cb.xml | 1 + P5/Source/Specs/cell.xml | 1 + P5/Source/Specs/certainty.xml | 1 + P5/Source/Specs/channel.xml | 1 + P5/Source/Specs/char.xml | 1 + P5/Source/Specs/charDecl.xml | 1 + P5/Source/Specs/choice.xml | 1 + P5/Source/Specs/cit.xml | 1 + P5/Source/Specs/citeData.xml | 1 + P5/Source/Specs/citeStructure.xml | 1 + P5/Source/Specs/citedRange.xml | 1 + P5/Source/Specs/cl.xml | 1 + P5/Source/Specs/classCode.xml | 1 + P5/Source/Specs/classDecl.xml | 1 + P5/Source/Specs/classRef.xml | 1 + P5/Source/Specs/classSpec.xml | 1 + P5/Source/Specs/classes.xml | 1 + P5/Source/Specs/closer.xml | 1 + P5/Source/Specs/code.xml | 1 + P5/Source/Specs/collation.xml | 1 + P5/Source/Specs/collection.xml | 1 + P5/Source/Specs/colloc.xml | 1 + P5/Source/Specs/colophon.xml | 1 + P5/Source/Specs/cond.xml | 1 + P5/Source/Specs/condition.xml | 1 + P5/Source/Specs/constitution.xml | 1 + P5/Source/Specs/constraint.xml | 1 + P5/Source/Specs/constraintSpec.xml | 1 + P5/Source/Specs/content.xml | 1 + P5/Source/Specs/corr.xml | 1 + P5/Source/Specs/correction.xml | 1 + P5/Source/Specs/correspAction.xml | 1 + P5/Source/Specs/correspContext.xml | 1 + P5/Source/Specs/correspDesc.xml | 1 + P5/Source/Specs/custodialHist.xml | 1 + P5/Source/Specs/damageSpan.xml | 1 + P5/Source/Specs/dataFacet.xml | 1 + P5/Source/Specs/dataRef.xml | 1 + P5/Source/Specs/dataSpec.xml | 1 + P5/Source/Specs/datatype.xml | 1 + P5/Source/Specs/date.xml | 1 + P5/Source/Specs/dateline.xml | 1 + P5/Source/Specs/decoDesc.xml | 1 + P5/Source/Specs/decoNote.xml | 1 + P5/Source/Specs/def.xml | 1 + P5/Source/Specs/default.xml | 1 + P5/Source/Specs/defaultVal.xml | 1 + P5/Source/Specs/del.xml | 1 + P5/Source/Specs/delSpan.xml | 1 + P5/Source/Specs/depth.xml | 1 + P5/Source/Specs/derivation.xml | 1 + P5/Source/Specs/desc.xml | 1 + P5/Source/Specs/dictScrap.xml | 1 + P5/Source/Specs/dim.xml | 1 + P5/Source/Specs/dimensions.xml | 1 + P5/Source/Specs/distinct.xml | 1 + P5/Source/Specs/distributor.xml | 1 + P5/Source/Specs/div.xml | 1 + P5/Source/Specs/div1.xml | 1 + P5/Source/Specs/div2.xml | 1 + P5/Source/Specs/div3.xml | 1 + P5/Source/Specs/div4.xml | 1 + P5/Source/Specs/div5.xml | 1 + P5/Source/Specs/div6.xml | 1 + P5/Source/Specs/div7.xml | 1 + P5/Source/Specs/divGen.xml | 1 + P5/Source/Specs/docAuthor.xml | 1 + P5/Source/Specs/docDate.xml | 1 + P5/Source/Specs/docEdition.xml | 1 + P5/Source/Specs/docImprint.xml | 1 + P5/Source/Specs/docTitle.xml | 1 + P5/Source/Specs/domain.xml | 1 + P5/Source/Specs/eLeaf.xml | 1 + P5/Source/Specs/eTree.xml | 1 + P5/Source/Specs/edition.xml | 1 + P5/Source/Specs/editionStmt.xml | 1 + P5/Source/Specs/editorialDecl.xml | 1 + P5/Source/Specs/eg.xml | 1 + P5/Source/Specs/egXML.xml | 1 + P5/Source/Specs/elementRef.xml | 1 + P5/Source/Specs/elementSpec.xml | 1 + P5/Source/Specs/ellipsis.xml | 1 + P5/Source/Specs/email.xml | 1 + P5/Source/Specs/emph.xml | 1 + P5/Source/Specs/empty.xml | 1 + P5/Source/Specs/encodingDesc.xml | 1 + P5/Source/Specs/entry.xml | 1 + P5/Source/Specs/entryFree.xml | 1 + P5/Source/Specs/epigraph.xml | 1 + P5/Source/Specs/epilogue.xml | 1 + P5/Source/Specs/equipment.xml | 1 + P5/Source/Specs/equiv.xml | 1 + P5/Source/Specs/etym.xml | 1 + P5/Source/Specs/event.xml | 1 + P5/Source/Specs/eventName.xml | 1 + P5/Source/Specs/ex.xml | 1 + P5/Source/Specs/exemplum.xml | 1 + P5/Source/Specs/expan.xml | 1 + P5/Source/Specs/explicit.xml | 1 + P5/Source/Specs/extent.xml | 1 + P5/Source/Specs/f.xml | 1 + P5/Source/Specs/fDecl.xml | 1 + P5/Source/Specs/fDescr.xml | 1 + P5/Source/Specs/fLib.xml | 1 + P5/Source/Specs/facsimile.xml | 1 + P5/Source/Specs/factuality.xml | 1 + P5/Source/Specs/figDesc.xml | 1 + P5/Source/Specs/figure.xml | 1 + P5/Source/Specs/fileDesc.xml | 1 + P5/Source/Specs/filiation.xml | 1 + P5/Source/Specs/finalRubric.xml | 1 + P5/Source/Specs/floatingText.xml | 1 + P5/Source/Specs/foliation.xml | 1 + P5/Source/Specs/foreign.xml | 1 + P5/Source/Specs/forename.xml | 1 + P5/Source/Specs/forest.xml | 1 + P5/Source/Specs/form.xml | 1 + P5/Source/Specs/formula.xml | 1 + P5/Source/Specs/front.xml | 1 + P5/Source/Specs/fs.xml | 1 + P5/Source/Specs/fsConstraints.xml | 1 + P5/Source/Specs/fsDecl.xml | 1 + P5/Source/Specs/fsDescr.xml | 1 + P5/Source/Specs/fsdDecl.xml | 1 + P5/Source/Specs/fsdLink.xml | 1 + P5/Source/Specs/fvLib.xml | 1 + P5/Source/Specs/fw.xml | 1 + P5/Source/Specs/g.xml | 1 + P5/Source/Specs/gap.xml | 1 + P5/Source/Specs/gb.xml | 1 + P5/Source/Specs/gen.xml | 1 + P5/Source/Specs/genName.xml | 1 + P5/Source/Specs/geo.xml | 1 + P5/Source/Specs/geoDecl.xml | 1 + P5/Source/Specs/gi.xml | 1 + P5/Source/Specs/gloss.xml | 1 + P5/Source/Specs/glyph.xml | 1 + P5/Source/Specs/gram.xml | 1 + P5/Source/Specs/gramGrp.xml | 1 + P5/Source/Specs/graph.xml | 1 + P5/Source/Specs/graphic.xml | 1 + P5/Source/Specs/group.xml | 1 + P5/Source/Specs/handDesc.xml | 1 + P5/Source/Specs/handNote.xml | 1 + P5/Source/Specs/handNotes.xml | 1 + P5/Source/Specs/handShift.xml | 1 + P5/Source/Specs/head.xml | 1 + P5/Source/Specs/headItem.xml | 1 + P5/Source/Specs/headLabel.xml | 1 + P5/Source/Specs/height.xml | 1 + P5/Source/Specs/heraldry.xml | 1 + P5/Source/Specs/hi.xml | 1 + P5/Source/Specs/history.xml | 1 + P5/Source/Specs/hom.xml | 1 + P5/Source/Specs/hyph.xml | 1 + P5/Source/Specs/hyphenation.xml | 1 + P5/Source/Specs/iNode.xml | 1 + P5/Source/Specs/iType.xml | 1 + P5/Source/Specs/ident.xml | 1 + P5/Source/Specs/if.xml | 1 + P5/Source/Specs/iff.xml | 1 + P5/Source/Specs/imprimatur.xml | 1 + P5/Source/Specs/imprint.xml | 1 + P5/Source/Specs/incident.xml | 1 + P5/Source/Specs/incipit.xml | 1 + P5/Source/Specs/index.xml | 1 + P5/Source/Specs/institution.xml | 1 + P5/Source/Specs/interaction.xml | 1 + P5/Source/Specs/interp.xml | 1 + P5/Source/Specs/interpGrp.xml | 1 + P5/Source/Specs/interpretation.xml | 1 + P5/Source/Specs/item.xml | 1 + P5/Source/Specs/join.xml | 1 + P5/Source/Specs/joinGrp.xml | 1 + P5/Source/Specs/keywords.xml | 1 + P5/Source/Specs/kinesic.xml | 1 + P5/Source/Specs/l.xml | 1 + P5/Source/Specs/label.xml | 1 + P5/Source/Specs/lacunaEnd.xml | 1 + P5/Source/Specs/lacunaStart.xml | 1 + P5/Source/Specs/lang.xml | 1 + P5/Source/Specs/langUsage.xml | 1 + P5/Source/Specs/language.xml | 1 + P5/Source/Specs/layout.xml | 1 + P5/Source/Specs/layoutDesc.xml | 1 + P5/Source/Specs/lb.xml | 1 + P5/Source/Specs/lbl.xml | 1 + P5/Source/Specs/leaf.xml | 1 + P5/Source/Specs/lg.xml | 1 + P5/Source/Specs/line.xml | 1 + P5/Source/Specs/link.xml | 1 + P5/Source/Specs/linkGrp.xml | 1 + P5/Source/Specs/list.xml | 1 + P5/Source/Specs/listAnnotation.xml | 1 + P5/Source/Specs/listApp.xml | 1 + P5/Source/Specs/listBibl.xml | 1 + P5/Source/Specs/listChange.xml | 1 + P5/Source/Specs/listEvent.xml | 1 + P5/Source/Specs/listForest.xml | 1 + P5/Source/Specs/listNym.xml | 1 + P5/Source/Specs/listObject.xml | 1 + P5/Source/Specs/listOrg.xml | 1 + P5/Source/Specs/listPerson.xml | 1 + P5/Source/Specs/listPlace.xml | 1 + P5/Source/Specs/listPrefixDef.xml | 1 + P5/Source/Specs/listRef.xml | 1 + P5/Source/Specs/listRelation.xml | 1 + P5/Source/Specs/listTranspose.xml | 1 + P5/Source/Specs/listWit.xml | 1 + P5/Source/Specs/localProp.xml | 1 + P5/Source/Specs/locale.xml | 1 + P5/Source/Specs/locus.xml | 1 + P5/Source/Specs/locusGrp.xml | 1 + P5/Source/Specs/m.xml | 1 + P5/Source/Specs/macro.abContent.xml | 1 + P5/Source/Specs/macro.limitedContent.xml | 1 + P5/Source/Specs/macro.paraContent.xml | 1 + P5/Source/Specs/macro.phraseSeq.limited.xml | 1 + P5/Source/Specs/macro.phraseSeq.xml | 1 + P5/Source/Specs/macro.specialPara.xml | 1 + P5/Source/Specs/macro.xtext.xml | 1 + P5/Source/Specs/macroRef.xml | 1 + P5/Source/Specs/macroSpec.xml | 1 + P5/Source/Specs/mapping.xml | 1 + P5/Source/Specs/material.xml | 1 + P5/Source/Specs/measure.xml | 1 + P5/Source/Specs/measureGrp.xml | 1 + P5/Source/Specs/media.xml | 1 + P5/Source/Specs/memberOf.xml | 1 + P5/Source/Specs/mentioned.xml | 1 + P5/Source/Specs/metDecl.xml | 1 + P5/Source/Specs/metSym.xml | 1 + P5/Source/Specs/metamark.xml | 1 + P5/Source/Specs/milestone.xml | 1 + P5/Source/Specs/mod.xml | 1 + P5/Source/Specs/model.addrPart.xml | 1 + P5/Source/Specs/model.addressLike.xml | 1 + P5/Source/Specs/model.annotationLike.xml | 1 + P5/Source/Specs/model.annotationPart.body.xml | 1 + P5/Source/Specs/model.applicationLike.xml | 1 + P5/Source/Specs/model.availabilityPart.xml | 1 + P5/Source/Specs/model.biblLike.xml | 1 + P5/Source/Specs/model.biblPart.xml | 1 + P5/Source/Specs/model.castItemPart.xml | 1 + P5/Source/Specs/model.catDescPart.xml | 1 + P5/Source/Specs/model.certLike.xml | 1 + P5/Source/Specs/model.choicePart.xml | 1 + P5/Source/Specs/model.common.xml | 1 + P5/Source/Specs/model.contentPart.xml | 1 + P5/Source/Specs/model.correspActionPart.xml | 1 + P5/Source/Specs/model.correspContextPart.xml | 1 + P5/Source/Specs/model.correspDescPart.xml | 1 + P5/Source/Specs/model.dateLike.xml | 1 + P5/Source/Specs/model.descLike.xml | 1 + P5/Source/Specs/model.describedResource.xml | 1 + P5/Source/Specs/model.dimLike.xml | 1 + P5/Source/Specs/model.div1Like.xml | 1 + P5/Source/Specs/model.div2Like.xml | 1 + P5/Source/Specs/model.div3Like.xml | 1 + P5/Source/Specs/model.div4Like.xml | 1 + P5/Source/Specs/model.div5Like.xml | 1 + P5/Source/Specs/model.div6Like.xml | 1 + P5/Source/Specs/model.div7Like.xml | 1 + P5/Source/Specs/model.divBottom.xml | 1 + P5/Source/Specs/model.divBottomPart.xml | 1 + P5/Source/Specs/model.divGenLike.xml | 1 + P5/Source/Specs/model.divLike.xml | 1 + P5/Source/Specs/model.divPart.spoken.xml | 1 + P5/Source/Specs/model.divPart.xml | 1 + P5/Source/Specs/model.divTop.xml | 1 + P5/Source/Specs/model.divTopPart.xml | 1 + P5/Source/Specs/model.divWrapper.xml | 1 + P5/Source/Specs/model.editorialDeclPart.xml | 1 + P5/Source/Specs/model.egLike.xml | 1 + P5/Source/Specs/model.emphLike.xml | 1 + P5/Source/Specs/model.encodingDescPart.xml | 1 + P5/Source/Specs/model.entryLike.xml | 1 + P5/Source/Specs/model.entryPart.top.xml | 1 + P5/Source/Specs/model.entryPart.xml | 1 + P5/Source/Specs/model.eventLike.xml | 1 + P5/Source/Specs/model.featureVal.complex.xml | 1 + P5/Source/Specs/model.featureVal.single.xml | 1 + P5/Source/Specs/model.featureVal.xml | 1 + P5/Source/Specs/model.formPart.xml | 1 + P5/Source/Specs/model.frontPart.drama.xml | 1 + P5/Source/Specs/model.frontPart.xml | 1 + P5/Source/Specs/model.fsdDeclPart.xml | 1 + P5/Source/Specs/model.gLike.xml | 1 + P5/Source/Specs/model.global.edit.xml | 1 + P5/Source/Specs/model.global.meta.xml | 1 + P5/Source/Specs/model.global.spoken.xml | 1 + P5/Source/Specs/model.global.xml | 1 + P5/Source/Specs/model.gramPart.xml | 1 + P5/Source/Specs/model.graphicLike.xml | 1 + P5/Source/Specs/model.headLike.xml | 1 + P5/Source/Specs/model.hiLike.xml | 1 + P5/Source/Specs/model.highlighted.xml | 1 + P5/Source/Specs/model.identEquiv.xml | 1 + P5/Source/Specs/model.identSynonyms.xml | 1 + P5/Source/Specs/model.imprintPart.xml | 1 + P5/Source/Specs/model.inter.xml | 1 + P5/Source/Specs/model.lLike.xml | 1 + P5/Source/Specs/model.lPart.xml | 1 + P5/Source/Specs/model.labelLike.xml | 1 + P5/Source/Specs/model.lexicalRefinement.xml | 1 + P5/Source/Specs/model.limitedPhrase.xml | 1 + P5/Source/Specs/model.linePart.xml | 1 + P5/Source/Specs/model.listLike.xml | 1 + P5/Source/Specs/model.measureLike.xml | 1 + P5/Source/Specs/model.milestoneLike.xml | 1 + P5/Source/Specs/model.morphLike.xml | 1 + P5/Source/Specs/model.msItemPart.xml | 1 + P5/Source/Specs/model.msQuoteLike.xml | 1 + P5/Source/Specs/model.nameLike.agent.xml | 1 + P5/Source/Specs/model.nameLike.xml | 1 + P5/Source/Specs/model.noteLike.xml | 1 + P5/Source/Specs/model.oddDecl.xml | 1 + P5/Source/Specs/model.oddRef.xml | 1 + P5/Source/Specs/model.offsetLike.xml | 1 + P5/Source/Specs/model.orgPart.xml | 1 + P5/Source/Specs/model.orgStateLike.xml | 1 + P5/Source/Specs/model.pLike.front.xml | 1 + P5/Source/Specs/model.pLike.xml | 1 + P5/Source/Specs/model.pPart.data.xml | 1 + P5/Source/Specs/model.pPart.edit.xml | 1 + P5/Source/Specs/model.pPart.editorial.xml | 1 + P5/Source/Specs/model.pPart.msdesc.xml | 1 + .../Specs/model.pPart.transcriptional.xml | 1 + P5/Source/Specs/model.paraPart.xml | 1 + P5/Source/Specs/model.persNamePart.xml | 1 + P5/Source/Specs/model.persStateLike.xml | 1 + P5/Source/Specs/model.personLike.xml | 1 + P5/Source/Specs/model.personPart.xml | 1 + P5/Source/Specs/model.phrase.xml | 1 + P5/Source/Specs/model.phrase.xml.xml | 1 + P5/Source/Specs/model.physDescPart.xml | 1 + P5/Source/Specs/model.placeLike.xml | 1 + P5/Source/Specs/model.placeNamePart.xml | 1 + P5/Source/Specs/model.placeStateLike.xml | 1 + P5/Source/Specs/model.profileDescPart.xml | 1 + P5/Source/Specs/model.ptrLike.form.xml | 1 + P5/Source/Specs/model.ptrLike.xml | 1 + .../model.publicationStmtPart.agency.xml | 1 + .../model.publicationStmtPart.detail.xml | 1 + P5/Source/Specs/model.quoteLike.xml | 1 + P5/Source/Specs/model.rdgLike.xml | 1 + P5/Source/Specs/model.rdgPart.xml | 1 + P5/Source/Specs/model.recordingPart.xml | 1 + P5/Source/Specs/model.resource.xml | 1 + P5/Source/Specs/model.respLike.xml | 1 + P5/Source/Specs/model.segLike.xml | 1 + P5/Source/Specs/model.settingPart.xml | 1 + P5/Source/Specs/model.sourceDescPart.xml | 1 + P5/Source/Specs/model.specDescLike.xml | 1 + P5/Source/Specs/model.stageLike.xml | 1 + P5/Source/Specs/model.standOffPart.xml | 1 + P5/Source/Specs/model.teiHeaderPart.xml | 1 + P5/Source/Specs/model.textDescPart.xml | 1 + P5/Source/Specs/model.titlepagePart.xml | 1 + P5/Source/Specs/model.xml | 1 + P5/Source/Specs/modelGrp.xml | 1 + P5/Source/Specs/modelSequence.xml | 1 + P5/Source/Specs/moduleRef.xml | 1 + P5/Source/Specs/moduleSpec.xml | 1 + P5/Source/Specs/monogr.xml | 1 + P5/Source/Specs/mood.xml | 1 + P5/Source/Specs/move.xml | 1 + P5/Source/Specs/msContents.xml | 1 + P5/Source/Specs/msDesc.xml | 1 + P5/Source/Specs/msFrag.xml | 1 + P5/Source/Specs/msIdentifier.xml | 1 + P5/Source/Specs/msItem.xml | 1 + P5/Source/Specs/msItemStruct.xml | 1 + P5/Source/Specs/msName.xml | 1 + P5/Source/Specs/msPart.xml | 1 + P5/Source/Specs/musicNotation.xml | 1 + P5/Source/Specs/nameLink.xml | 1 + P5/Source/Specs/namespace.xml | 1 + P5/Source/Specs/node.xml | 1 + P5/Source/Specs/normalization.xml | 1 + P5/Source/Specs/notatedMusic.xml | 1 + P5/Source/Specs/note.xml | 1 + P5/Source/Specs/notesStmt.xml | 1 + P5/Source/Specs/num.xml | 1 + P5/Source/Specs/number.xml | 1 + P5/Source/Specs/numeric.xml | 1 + P5/Source/Specs/nym.xml | 1 + P5/Source/Specs/oRef.xml | 1 + P5/Source/Specs/objectDesc.xml | 1 + P5/Source/Specs/objectType.xml | 1 + P5/Source/Specs/opener.xml | 1 + P5/Source/Specs/org.xml | 1 + P5/Source/Specs/orig.xml | 1 + P5/Source/Specs/origDate.xml | 1 + P5/Source/Specs/orth.xml | 1 + P5/Source/Specs/outputRendition.xml | 1 + P5/Source/Specs/p.xml | 1 + P5/Source/Specs/pRef.xml | 1 + P5/Source/Specs/param.xml | 1 + P5/Source/Specs/paramList.xml | 1 + P5/Source/Specs/paramSpec.xml | 1 + P5/Source/Specs/particDesc.xml | 1 + P5/Source/Specs/path.xml | 1 + P5/Source/Specs/pause.xml | 1 + P5/Source/Specs/pb.xml | 1 + P5/Source/Specs/pc.xml | 1 + P5/Source/Specs/per.xml | 1 + P5/Source/Specs/performance.xml | 1 + P5/Source/Specs/person.xml | 1 + P5/Source/Specs/personGrp.xml | 1 + P5/Source/Specs/persona.xml | 1 + P5/Source/Specs/phr.xml | 1 + P5/Source/Specs/physDesc.xml | 1 + P5/Source/Specs/place.xml | 1 + P5/Source/Specs/pos.xml | 1 + P5/Source/Specs/postBox.xml | 1 + P5/Source/Specs/postCode.xml | 1 + P5/Source/Specs/postscript.xml | 1 + P5/Source/Specs/prefixDef.xml | 1 + P5/Source/Specs/preparedness.xml | 1 + P5/Source/Specs/profileDesc.xml | 1 + P5/Source/Specs/projectDesc.xml | 1 + P5/Source/Specs/prologue.xml | 1 + P5/Source/Specs/pron.xml | 1 + P5/Source/Specs/ptr.xml | 1 + P5/Source/Specs/pubPlace.xml | 1 + P5/Source/Specs/publicationStmt.xml | 1 + P5/Source/Specs/punctuation.xml | 1 + P5/Source/Specs/purpose.xml | 1 + P5/Source/Specs/q.xml | 1 + P5/Source/Specs/quotation.xml | 1 + P5/Source/Specs/quote.xml | 1 + P5/Source/Specs/rb.xml | 1 + P5/Source/Specs/rdg.xml | 1 + P5/Source/Specs/rdgGrp.xml | 1 + P5/Source/Specs/re.xml | 1 + P5/Source/Specs/recordHist.xml | 1 + P5/Source/Specs/recording.xml | 1 + P5/Source/Specs/recordingStmt.xml | 1 + P5/Source/Specs/redo.xml | 1 + P5/Source/Specs/ref.xml | 1 + P5/Source/Specs/refState.xml | 1 + P5/Source/Specs/refsDecl.xml | 1 + P5/Source/Specs/reg.xml | 1 + P5/Source/Specs/relatedItem.xml | 1 + P5/Source/Specs/remarks.xml | 1 + P5/Source/Specs/rendition.xml | 1 + P5/Source/Specs/repository.xml | 1 + P5/Source/Specs/respStmt.xml | 1 + P5/Source/Specs/respons.xml | 1 + P5/Source/Specs/restore.xml | 1 + P5/Source/Specs/retrace.xml | 1 + P5/Source/Specs/revisionDesc.xml | 1 + P5/Source/Specs/rhyme.xml | 1 + P5/Source/Specs/role.xml | 1 + P5/Source/Specs/roleDesc.xml | 1 + P5/Source/Specs/roleName.xml | 1 + P5/Source/Specs/root.xml | 1 + P5/Source/Specs/row.xml | 1 + P5/Source/Specs/rs.xml | 1 + P5/Source/Specs/rt.xml | 1 + P5/Source/Specs/rubric.xml | 1 + P5/Source/Specs/ruby.xml | 1 + P5/Source/Specs/s.xml | 1 + P5/Source/Specs/said.xml | 1 + P5/Source/Specs/salute.xml | 1 + P5/Source/Specs/samplingDecl.xml | 1 + P5/Source/Specs/schemaRef.xml | 1 + P5/Source/Specs/schemaSpec.xml | 1 + P5/Source/Specs/scriptDesc.xml | 1 + P5/Source/Specs/scriptNote.xml | 1 + P5/Source/Specs/scriptStmt.xml | 1 + P5/Source/Specs/sealDesc.xml | 1 + P5/Source/Specs/secFol.xml | 1 + P5/Source/Specs/secl.xml | 1 + P5/Source/Specs/seg.xml | 1 + P5/Source/Specs/segmentation.xml | 1 + P5/Source/Specs/sense.xml | 1 + P5/Source/Specs/sequence.xml | 1 + P5/Source/Specs/series.xml | 1 + P5/Source/Specs/seriesStmt.xml | 1 + P5/Source/Specs/set.xml | 1 + P5/Source/Specs/setting.xml | 1 + P5/Source/Specs/settingDesc.xml | 1 + P5/Source/Specs/shift.xml | 1 + P5/Source/Specs/sic.xml | 1 + P5/Source/Specs/signatures.xml | 1 + P5/Source/Specs/signed.xml | 1 + P5/Source/Specs/soCalled.xml | 1 + P5/Source/Specs/sound.xml | 1 + P5/Source/Specs/source.xml | 1 + P5/Source/Specs/sourceDesc.xml | 1 + P5/Source/Specs/sourceDoc.xml | 1 + P5/Source/Specs/sp.xml | 1 + P5/Source/Specs/spGrp.xml | 1 + P5/Source/Specs/space.xml | 1 + P5/Source/Specs/span.xml | 1 + P5/Source/Specs/spanGrp.xml | 1 + P5/Source/Specs/speaker.xml | 1 + P5/Source/Specs/specDesc.xml | 1 + P5/Source/Specs/specGrp.xml | 1 + P5/Source/Specs/specGrpRef.xml | 1 + P5/Source/Specs/specList.xml | 1 + P5/Source/Specs/stage.xml | 1 + P5/Source/Specs/standOff.xml | 1 + P5/Source/Specs/stdVals.xml | 1 + P5/Source/Specs/street.xml | 1 + P5/Source/Specs/stress.xml | 1 + P5/Source/Specs/string.xml | 1 + P5/Source/Specs/styleDefDecl.xml | 1 + P5/Source/Specs/subc.xml | 1 + P5/Source/Specs/subst.xml | 1 + P5/Source/Specs/substJoin.xml | 1 + P5/Source/Specs/summary.xml | 1 + P5/Source/Specs/superEntry.xml | 1 + P5/Source/Specs/supplied.xml | 1 + P5/Source/Specs/support.xml | 1 + P5/Source/Specs/supportDesc.xml | 1 + P5/Source/Specs/surface.xml | 1 + P5/Source/Specs/surfaceGrp.xml | 1 + P5/Source/Specs/surname.xml | 1 + P5/Source/Specs/surplus.xml | 1 + P5/Source/Specs/surrogates.xml | 1 + P5/Source/Specs/syll.xml | 1 + P5/Source/Specs/symbol.xml | 1 + P5/Source/Specs/table.xml | 1 + P5/Source/Specs/tag.xml | 1 + P5/Source/Specs/tagUsage.xml | 1 + P5/Source/Specs/tagsDecl.xml | 1 + P5/Source/Specs/taxonomy.xml | 1 + P5/Source/Specs/tech.xml | 1 + P5/Source/Specs/teiCorpus.xml | 1 + P5/Source/Specs/teiHeader.xml | 1 + P5/Source/Specs/teidata.authority.xml | 1 + P5/Source/Specs/teidata.certainty.xml | 1 + P5/Source/Specs/teidata.count.xml | 1 + P5/Source/Specs/teidata.duration.iso.xml | 1 + P5/Source/Specs/teidata.duration.w3c.xml | 1 + P5/Source/Specs/teidata.enumerated.xml | 1 + P5/Source/Specs/teidata.gender.xml | 1 + P5/Source/Specs/teidata.interval.xml | 1 + P5/Source/Specs/teidata.key.xml | 1 + P5/Source/Specs/teidata.language.xml | 1 + P5/Source/Specs/teidata.name.xml | 1 + P5/Source/Specs/teidata.namespace.xml | 1 + P5/Source/Specs/teidata.namespaceOrName.xml | 1 + P5/Source/Specs/teidata.nullOrName.xml | 1 + P5/Source/Specs/teidata.numeric.xml | 1 + P5/Source/Specs/teidata.outputMeasurement.xml | 1 + P5/Source/Specs/teidata.pattern.xml | 1 + P5/Source/Specs/teidata.point.xml | 1 + P5/Source/Specs/teidata.pointer.xml | 1 + P5/Source/Specs/teidata.prefix.xml | 1 + P5/Source/Specs/teidata.probCert.xml | 1 + P5/Source/Specs/teidata.probability.xml | 1 + P5/Source/Specs/teidata.replacement.xml | 1 + P5/Source/Specs/teidata.sex.xml | 1 + P5/Source/Specs/teidata.temporal.iso.xml | 1 + P5/Source/Specs/teidata.temporal.w3c.xml | 1 + P5/Source/Specs/teidata.temporal.working.xml | 1 + P5/Source/Specs/teidata.text.xml | 1 + P5/Source/Specs/teidata.truthValue.xml | 1 + P5/Source/Specs/teidata.unboundedCount.xml | 1 + P5/Source/Specs/teidata.version.xml | 1 + P5/Source/Specs/teidata.versionNumber.xml | 1 + P5/Source/Specs/teidata.word.xml | 1 + P5/Source/Specs/teidata.xTruthValue.xml | 1 + P5/Source/Specs/teidata.xmlName.xml | 1 + P5/Source/Specs/teidata.xpath.xml | 1 + P5/Source/Specs/term.xml | 1 + P5/Source/Specs/text.xml | 1 + P5/Source/Specs/textClass.xml | 1 + P5/Source/Specs/textDesc.xml | 1 + P5/Source/Specs/textLang.xml | 1 + P5/Source/Specs/textNode.xml | 1 + P5/Source/Specs/then.xml | 1 + P5/Source/Specs/time.xml | 1 + P5/Source/Specs/timeline.xml | 1 + P5/Source/Specs/titlePage.xml | 1 + P5/Source/Specs/titlePart.xml | 1 + P5/Source/Specs/titleStmt.xml | 1 + P5/Source/Specs/tns.xml | 1 + P5/Source/Specs/trailer.xml | 1 + P5/Source/Specs/transcriptionDesc.xml | 1 + P5/Source/Specs/transpose.xml | 1 + P5/Source/Specs/tree.xml | 1 + P5/Source/Specs/triangle.xml | 1 + P5/Source/Specs/typeDesc.xml | 1 + P5/Source/Specs/typeNote.xml | 1 + P5/Source/Specs/u.xml | 1 + P5/Source/Specs/unclear.xml | 1 + P5/Source/Specs/undo.xml | 1 + P5/Source/Specs/unicodeProp.xml | 1 + P5/Source/Specs/unihanProp.xml | 1 + P5/Source/Specs/unit.xml | 1 + P5/Source/Specs/usg.xml | 1 + P5/Source/Specs/vAlt.xml | 1 + P5/Source/Specs/vColl.xml | 1 + P5/Source/Specs/vDefault.xml | 1 + P5/Source/Specs/vLabel.xml | 1 + P5/Source/Specs/vMerge.xml | 1 + P5/Source/Specs/vNot.xml | 1 + P5/Source/Specs/vRange.xml | 1 + P5/Source/Specs/val.xml | 1 + P5/Source/Specs/valDesc.xml | 1 + P5/Source/Specs/valItem.xml | 1 + P5/Source/Specs/valList.xml | 1 + P5/Source/Specs/variantEncoding.xml | 1 + P5/Source/Specs/view.xml | 1 + P5/Source/Specs/vocal.xml | 1 + P5/Source/Specs/w.xml | 1 + P5/Source/Specs/watermark.xml | 1 + P5/Source/Specs/when.xml | 1 + P5/Source/Specs/width.xml | 1 + P5/Source/Specs/wit.xml | 1 + P5/Source/Specs/witDetail.xml | 1 + P5/Source/Specs/witEnd.xml | 1 + P5/Source/Specs/witStart.xml | 1 + P5/Source/Specs/witness.xml | 1 + P5/Source/Specs/writing.xml | 1 + P5/Source/Specs/xenoData.xml | 1 + P5/Source/Specs/xr.xml | 1 + P5/Source/Specs/zone.xml | 1 + 841 files changed, 55271 insertions(+), 37 deletions(-) mode change 120000 => 100644 P5/Source/Guidelines/fr/AB-About.xml mode change 120000 => 100644 P5/Source/Guidelines/fr/AI-AnalyticMechanisms.xml mode change 120000 => 100644 P5/Source/Guidelines/fr/BIB-Bibliography.xml mode change 120000 => 100644 P5/Source/Guidelines/fr/CC-LanguageCorpora.xml mode change 120000 => 100644 P5/Source/Guidelines/fr/CE-CertaintyResponsibility.xml mode change 120000 => 100644 P5/Source/Guidelines/fr/CH-LanguagesCharacterSets.xml mode change 120000 => 100644 P5/Source/Guidelines/fr/CO-CoreElements.xml mode change 120000 => 100644 P5/Source/Guidelines/fr/COL-Colophon.xml mode change 120000 => 100644 P5/Source/Guidelines/fr/DI-PrintDictionaries.xml mode change 120000 => 100644 P5/Source/Guidelines/fr/DR-PerformanceTexts.xml mode change 120000 => 100644 P5/Source/Guidelines/fr/DS-DefaultTextStructure.xml mode change 120000 => 100644 P5/Source/Guidelines/fr/Dedication.xml mode change 120000 => 100644 P5/Source/Guidelines/fr/FM1-IntroductoryNote.xml mode change 120000 => 100644 P5/Source/Guidelines/fr/FS-FeatureStructures.xml mode change 120000 => 100644 P5/Source/Guidelines/fr/FT-TablesFormulaeGraphics.xml mode change 120000 => 100644 P5/Source/Guidelines/fr/GD-GraphsNetworksTrees.xml mode change 120000 => 100644 P5/Source/Guidelines/fr/MS-ManuscriptDescription.xml mode change 120000 => 100644 P5/Source/Guidelines/fr/ND-NamesDates.xml mode change 120000 => 100644 P5/Source/Guidelines/fr/NH-Non-hierarchical.xml mode change 120000 => 100644 P5/Source/Guidelines/fr/PARTIND.xml mode change 120000 => 100644 P5/Source/Guidelines/fr/PH-PrimarySources.xml mode change 120000 => 100644 P5/Source/Guidelines/fr/PrefatoryNote.xml mode change 120000 => 100644 P5/Source/Guidelines/fr/REF-ATTRIBUTES.xml mode change 120000 => 100644 P5/Source/Guidelines/fr/REF-CLASSES-ATTS.xml mode change 120000 => 100644 P5/Source/Guidelines/fr/REF-CLASSES-MODEL.xml mode change 120000 => 100644 P5/Source/Guidelines/fr/REF-ELEMENTS.xml mode change 120000 => 100644 P5/Source/Guidelines/fr/REF-MACROS.xml mode change 120000 => 100644 P5/Source/Guidelines/fr/SA-LinkingSegmentationAlignment.xml mode change 120000 => 100644 P5/Source/Guidelines/fr/SG-GentleIntroduction.xml mode change 120000 => 100644 P5/Source/Guidelines/fr/ST-Infrastructure.xml mode change 120000 => 100644 P5/Source/Guidelines/fr/TC-CriticalApparatus.xml mode change 120000 => 100644 P5/Source/Guidelines/fr/TD-DocumentationElements.xml mode change 120000 => 100644 P5/Source/Guidelines/fr/TS-TranscriptionsofSpeech.xml mode change 120000 => 100644 P5/Source/Guidelines/fr/TitlePageVerso.xml mode change 120000 => 100644 P5/Source/Guidelines/fr/USE.xml mode change 120000 => 100644 P5/Source/Guidelines/fr/VE-Verse.xml mode change 120000 => 100644 P5/Source/Guidelines/fr/WD-NonStandardCharacters.xml diff --git a/P5/Source/Guidelines/en/AB-About.xml b/P5/Source/Guidelines/en/AB-About.xml index 42ba61a551..f5bea382ae 100644 --- a/P5/Source/Guidelines/en/AB-About.xml +++ b/P5/Source/Guidelines/en/AB-About.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Guidelines/en/AI-AnalyticMechanisms.xml b/P5/Source/Guidelines/en/AI-AnalyticMechanisms.xml index 51916016ff..d478467d37 100644 --- a/P5/Source/Guidelines/en/AI-AnalyticMechanisms.xml +++ b/P5/Source/Guidelines/en/AI-AnalyticMechanisms.xml @@ -1,3 +1,4 @@ +
Simple Analytic Mechanisms diff --git a/P5/Source/Guidelines/en/CC-LanguageCorpora.xml b/P5/Source/Guidelines/en/CC-LanguageCorpora.xml index f4ca35b1c3..eaadfd720b 100644 --- a/P5/Source/Guidelines/en/CC-LanguageCorpora.xml +++ b/P5/Source/Guidelines/en/CC-LanguageCorpora.xml @@ -1,3 +1,4 @@ +
Language Corpora diff --git a/P5/Source/Guidelines/en/CE-CertaintyResponsibility.xml b/P5/Source/Guidelines/en/CE-CertaintyResponsibility.xml index 02675dd175..a0c5b4f902 100644 --- a/P5/Source/Guidelines/en/CE-CertaintyResponsibility.xml +++ b/P5/Source/Guidelines/en/CE-CertaintyResponsibility.xml @@ -1,3 +1,4 @@ +
Certainty, Precision, and Responsibility diff --git a/P5/Source/Guidelines/en/CH-LanguagesCharacterSets.xml b/P5/Source/Guidelines/en/CH-LanguagesCharacterSets.xml index ad367a5213..dca8219668 100644 --- a/P5/Source/Guidelines/en/CH-LanguagesCharacterSets.xml +++ b/P5/Source/Guidelines/en/CH-LanguagesCharacterSets.xml @@ -1,3 +1,4 @@ +
diff --git a/P5/Source/Guidelines/en/CO-CoreElements.xml b/P5/Source/Guidelines/en/CO-CoreElements.xml index 676c389f19..0a15fa3776 100644 --- a/P5/Source/Guidelines/en/CO-CoreElements.xml +++ b/P5/Source/Guidelines/en/CO-CoreElements.xml @@ -1,3 +1,4 @@ +
diff --git a/P5/Source/Guidelines/en/COL-Colophon.xml b/P5/Source/Guidelines/en/COL-Colophon.xml index 23f593e6a0..7500dddd9d 100644 --- a/P5/Source/Guidelines/en/COL-Colophon.xml +++ b/P5/Source/Guidelines/en/COL-Colophon.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Guidelines/en/DEPRECATIONS.xml b/P5/Source/Guidelines/en/DEPRECATIONS.xml index 5436fb1f7f..7f139ec965 100644 --- a/P5/Source/Guidelines/en/DEPRECATIONS.xml +++ b/P5/Source/Guidelines/en/DEPRECATIONS.xml @@ -1,3 +1,4 @@ +
diff --git a/P5/Source/Guidelines/en/DI-PrintDictionaries.xml b/P5/Source/Guidelines/en/DI-PrintDictionaries.xml index bcefb264a3..e031829598 100644 --- a/P5/Source/Guidelines/en/DI-PrintDictionaries.xml +++ b/P5/Source/Guidelines/en/DI-PrintDictionaries.xml @@ -1,3 +1,4 @@ +
diff --git a/P5/Source/Guidelines/en/DR-PerformanceTexts.xml b/P5/Source/Guidelines/en/DR-PerformanceTexts.xml index bfcf74fdea..233e1dbc4b 100644 --- a/P5/Source/Guidelines/en/DR-PerformanceTexts.xml +++ b/P5/Source/Guidelines/en/DR-PerformanceTexts.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Guidelines/en/DS-DefaultTextStructure.xml b/P5/Source/Guidelines/en/DS-DefaultTextStructure.xml index 953c585d79..b160c7afdd 100644 --- a/P5/Source/Guidelines/en/DS-DefaultTextStructure.xml +++ b/P5/Source/Guidelines/en/DS-DefaultTextStructure.xml @@ -1,3 +1,4 @@ +
diff --git a/P5/Source/Guidelines/en/Dedication.xml b/P5/Source/Guidelines/en/Dedication.xml index 3f105ab8b9..766e7443d7 100644 --- a/P5/Source/Guidelines/en/Dedication.xml +++ b/P5/Source/Guidelines/en/Dedication.xml @@ -1,3 +1,4 @@ +
diff --git a/P5/Source/Guidelines/en/FM1-IntroductoryNote.xml b/P5/Source/Guidelines/en/FM1-IntroductoryNote.xml index eb1ada5f01..c3492bfca2 100644 --- a/P5/Source/Guidelines/en/FM1-IntroductoryNote.xml +++ b/P5/Source/Guidelines/en/FM1-IntroductoryNote.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Guidelines/en/FS-FeatureStructures.xml b/P5/Source/Guidelines/en/FS-FeatureStructures.xml index 1a4c2cf972..933e6a14b5 100644 --- a/P5/Source/Guidelines/en/FS-FeatureStructures.xml +++ b/P5/Source/Guidelines/en/FS-FeatureStructures.xml @@ -1,3 +1,4 @@ +
Feature Structures diff --git a/P5/Source/Guidelines/en/FT-TablesFormulaeGraphics.xml b/P5/Source/Guidelines/en/FT-TablesFormulaeGraphics.xml index 4a66f2484c..4c4102bb21 100644 --- a/P5/Source/Guidelines/en/FT-TablesFormulaeGraphics.xml +++ b/P5/Source/Guidelines/en/FT-TablesFormulaeGraphics.xml @@ -1,3 +1,4 @@ +
diff --git a/P5/Source/Guidelines/en/GD-GraphsNetworksTrees.xml b/P5/Source/Guidelines/en/GD-GraphsNetworksTrees.xml index f4491bd8c6..415d9f2e62 100644 --- a/P5/Source/Guidelines/en/GD-GraphsNetworksTrees.xml +++ b/P5/Source/Guidelines/en/GD-GraphsNetworksTrees.xml @@ -1,3 +1,4 @@ +
Graphs, Networks, and Trees diff --git a/P5/Source/Guidelines/en/HD-Header.xml b/P5/Source/Guidelines/en/HD-Header.xml index 01ca4db0b6..b03c51e5d7 100644 --- a/P5/Source/Guidelines/en/HD-Header.xml +++ b/P5/Source/Guidelines/en/HD-Header.xml @@ -1,3 +1,4 @@ +
diff --git a/P5/Source/Guidelines/en/MS-ManuscriptDescription.xml b/P5/Source/Guidelines/en/MS-ManuscriptDescription.xml index 707db494e2..e43d0b3bc6 100644 --- a/P5/Source/Guidelines/en/MS-ManuscriptDescription.xml +++ b/P5/Source/Guidelines/en/MS-ManuscriptDescription.xml @@ -1,3 +1,4 @@ +
diff --git a/P5/Source/Guidelines/en/ND-NamesDates.xml b/P5/Source/Guidelines/en/ND-NamesDates.xml index c19d65555f..eff14c5bed 100644 --- a/P5/Source/Guidelines/en/ND-NamesDates.xml +++ b/P5/Source/Guidelines/en/ND-NamesDates.xml @@ -1,3 +1,4 @@ +
diff --git a/P5/Source/Guidelines/en/NH-Non-hierarchical.xml b/P5/Source/Guidelines/en/NH-Non-hierarchical.xml index a810a46b98..9a2e0f15af 100644 --- a/P5/Source/Guidelines/en/NH-Non-hierarchical.xml +++ b/P5/Source/Guidelines/en/NH-Non-hierarchical.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Guidelines/en/PARTIND.xml b/P5/Source/Guidelines/en/PARTIND.xml index 7efdd6160c..48e76ceaae 100644 --- a/P5/Source/Guidelines/en/PARTIND.xml +++ b/P5/Source/Guidelines/en/PARTIND.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Guidelines/en/PH-PrimarySources.xml b/P5/Source/Guidelines/en/PH-PrimarySources.xml index 4ac22926a4..73fb70d1a4 100644 --- a/P5/Source/Guidelines/en/PH-PrimarySources.xml +++ b/P5/Source/Guidelines/en/PH-PrimarySources.xml @@ -1,3 +1,4 @@ +
diff --git a/P5/Source/Guidelines/en/REF-ATTRIBUTES.xml b/P5/Source/Guidelines/en/REF-ATTRIBUTES.xml index 160ec9182d..24d14cad0f 100644 --- a/P5/Source/Guidelines/en/REF-ATTRIBUTES.xml +++ b/P5/Source/Guidelines/en/REF-ATTRIBUTES.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Guidelines/en/REF-CLASSES-ATTS.xml b/P5/Source/Guidelines/en/REF-CLASSES-ATTS.xml index f01fb8cecb..b52965be87 100644 --- a/P5/Source/Guidelines/en/REF-CLASSES-ATTS.xml +++ b/P5/Source/Guidelines/en/REF-CLASSES-ATTS.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Guidelines/en/REF-CLASSES-MODEL.xml b/P5/Source/Guidelines/en/REF-CLASSES-MODEL.xml index a22126f37f..5c12bc541f 100644 --- a/P5/Source/Guidelines/en/REF-CLASSES-MODEL.xml +++ b/P5/Source/Guidelines/en/REF-CLASSES-MODEL.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Guidelines/en/REF-ELEMENTS.xml b/P5/Source/Guidelines/en/REF-ELEMENTS.xml index 7342f68b86..581769398c 100644 --- a/P5/Source/Guidelines/en/REF-ELEMENTS.xml +++ b/P5/Source/Guidelines/en/REF-ELEMENTS.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Guidelines/en/REF-MACROS.xml b/P5/Source/Guidelines/en/REF-MACROS.xml index d30784f2bf..eeb913d8b2 100644 --- a/P5/Source/Guidelines/en/REF-MACROS.xml +++ b/P5/Source/Guidelines/en/REF-MACROS.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Guidelines/en/SA-LinkingSegmentationAlignment.xml b/P5/Source/Guidelines/en/SA-LinkingSegmentationAlignment.xml index e20d6056b9..3d8e462b99 100644 --- a/P5/Source/Guidelines/en/SA-LinkingSegmentationAlignment.xml +++ b/P5/Source/Guidelines/en/SA-LinkingSegmentationAlignment.xml @@ -1,3 +1,4 @@ +
diff --git a/P5/Source/Guidelines/en/SG-GentleIntroduction.xml b/P5/Source/Guidelines/en/SG-GentleIntroduction.xml index 90585c375c..9a63cb7059 100644 --- a/P5/Source/Guidelines/en/SG-GentleIntroduction.xml +++ b/P5/Source/Guidelines/en/SG-GentleIntroduction.xml @@ -1,3 +1,4 @@ +
diff --git a/P5/Source/Guidelines/en/ST-Infrastructure.xml b/P5/Source/Guidelines/en/ST-Infrastructure.xml index a474073f17..b141ec6789 100644 --- a/P5/Source/Guidelines/en/ST-Infrastructure.xml +++ b/P5/Source/Guidelines/en/ST-Infrastructure.xml @@ -1,3 +1,4 @@ +
diff --git a/P5/Source/Guidelines/en/TC-CriticalApparatus.xml b/P5/Source/Guidelines/en/TC-CriticalApparatus.xml index 93fcb0d8f1..d9970210f6 100644 --- a/P5/Source/Guidelines/en/TC-CriticalApparatus.xml +++ b/P5/Source/Guidelines/en/TC-CriticalApparatus.xml @@ -1,3 +1,4 @@ +
diff --git a/P5/Source/Guidelines/en/TD-DocumentationElements.xml b/P5/Source/Guidelines/en/TD-DocumentationElements.xml index 0b2b595ebd..1c08f566e9 100644 --- a/P5/Source/Guidelines/en/TD-DocumentationElements.xml +++ b/P5/Source/Guidelines/en/TD-DocumentationElements.xml @@ -1,3 +1,4 @@ +
diff --git a/P5/Source/Guidelines/en/TitlePageVerso.xml b/P5/Source/Guidelines/en/TitlePageVerso.xml index ea1b857235..b822117af9 100644 --- a/P5/Source/Guidelines/en/TitlePageVerso.xml +++ b/P5/Source/Guidelines/en/TitlePageVerso.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Guidelines/en/USE.xml b/P5/Source/Guidelines/en/USE.xml index f6fd2cb557..d49abb5a03 100644 --- a/P5/Source/Guidelines/en/USE.xml +++ b/P5/Source/Guidelines/en/USE.xml @@ -1,3 +1,4 @@ +
diff --git a/P5/Source/Guidelines/en/VE-Verse.xml b/P5/Source/Guidelines/en/VE-Verse.xml index 0e46ad5d72..62f662afa2 100644 --- a/P5/Source/Guidelines/en/VE-Verse.xml +++ b/P5/Source/Guidelines/en/VE-Verse.xml @@ -1,3 +1,4 @@ +
diff --git a/P5/Source/Guidelines/en/WD-NonStandardCharacters.xml b/P5/Source/Guidelines/en/WD-NonStandardCharacters.xml index 46d74b6d20..70be97f315 100644 --- a/P5/Source/Guidelines/en/WD-NonStandardCharacters.xml +++ b/P5/Source/Guidelines/en/WD-NonStandardCharacters.xml @@ -1,3 +1,4 @@ +
diff --git a/P5/Source/Guidelines/fr/AB-About.xml b/P5/Source/Guidelines/fr/AB-About.xml deleted file mode 120000 index 2382495709..0000000000 --- a/P5/Source/Guidelines/fr/AB-About.xml +++ /dev/null @@ -1 +0,0 @@ -../en/./AB-About.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/AB-About.xml b/P5/Source/Guidelines/fr/AB-About.xml new file mode 100644 index 0000000000..9bae7a7755 --- /dev/null +++ b/P5/Source/Guidelines/fr/AB-About.xml @@ -0,0 +1,838 @@ + + + + + + + +
+About These Guidelines + +

These Guidelines have been developed and are maintained by the Text +Encoding Initiative Consortium (TEI); see . They +are addressed to anyone who works with any kind of textual resource in +digital form.

+ +

They make recommendations about suitable ways of representing those +features of textual resources which need to be identified explicitly +in order to facilitate processing by computer programs. In +particular, they specify a set of markers (or tags) which +may be inserted in the electronic representation of the text, in order +to mark the text structure and other features of interest. Many, or +most, computer programs depend on the presence of such explicit +markers for their functionality, since without them a digitized text +appears to be nothing but a sequence of undifferentiated bits. The +success of the World Wide Web, for example, is partly a consequence of +its use of such markup to indicate such features as headings and lists +on individual pages, and to indicate links between pages. The process +of inserting such explicit markers for implicit textual features is +often called markup, or equivalently within this +work encoding; the term +tagging is also used informally. We use the term +encoding scheme or markup language to denote +the complete set of rules associated with the use of markup in a given +context; we use the term markup vocabulary for the +specific set of markers or named distinctions employed by a given +encoding scheme. Thus, this work both describes the TEI encoding +scheme, and documents the TEI markup vocabulary.

+ +

The TEI encoding scheme is of particular usefulness in facilitating +the loss-free interchange of data amongst individuals and research +groups using different programs, computer systems, or application +software. Since they contain an inventory of the features most often +deployed for computer-based text processing, these Guidelines are also +useful as a starting point for those designing new systems and +creating new materials, even where interchange of information is not a +primary objective.

+ +

These Guidelines apply to texts in any natural language, of any +date, in any literary genre or text type, without restriction on form +or content. They treat both continuous materials (running +text) and discontinuous materials such as dictionaries and +linguistic corpora. Though principally directed to the needs of the +scholarly research community, these Guidelines are not restricted to +esoteric academic applications. They are also useful for librarians +maintaining and documenting electronic materials, and for publishers +and others creating or distributing electronic texts. Although they +focus on problems of representing in electronic form texts which +already exist in traditional media, these Guidelines are also +applicable to textual material which is born +digital. We believe them to be adequate to +the widest variety of currently existing practices in using +digital textual data, but by no means limited to them.

+ +

The rules and recommendations made in these Guidelines are +expressed in terms of what is currently the most widely-used markup +language for digital resources of all kinds: the Extensible Markup +Language (XML), as defined by the World Wide Web Consortium's XML +Recommendation. However, the TEI encoding scheme itself does not +depend on this language; it was originally formulated in terms of SGML +(the ISO Standard Generalized Markup Language), a +predecessor of XML, and +may in future years be re-expressed in other ways as the +field of markup develops and matures. For more information on markup +languages see chapter ; for more +information on the associated character encoding issues see chapter +. +

+ +

This document provides the authoritative and complete statement of +the requirements and usage of the TEI encoding scheme. As such, +although it includes numerous small examples, it must be stressed that +this work is intended to be a reference manual rather than a tutorial +guide.

+ +

The remainder of this chapter comprises three sections. The first +gives an overview of the structure and notational conventions used +throughout these Guidelines. The second enumerates the design principles +underlying the TEI scheme and the application environments in which it +may be found useful. Finally, the third section gives a brief account +of the origins and development of the Text Encoding Initiative itself.

+ +
Structure and Notational +Conventions of this Document + +

The remaining two sections of the front matter to these Guidelines +provide background tutorial material for those unfamiliar with basic +markup technologies. Following the present introductory section, we +present a detailed introduction to XML itself, intended to cover in a +relatively painless manner as much as the novice user of the TEI +scheme needs to know about markup languages in general and XML in +particular. This is followed by a discussion of the general principles +underlying current practice in the representation of different +languages and writing systems in digital form. This chapter is largely +intended for the user unfamiliar with the Unicode encoding systems, +though the expert may also find its historical overview of +interest.

+ +

The body of this edition of these Guidelines proper contains 23 +chapters arranged in increasing order of specialist interest. The +first five chapters discuss in depth matters likely to be of +importance to anyone intending to apply the TEI scheme to virtually +any kind of text. The next seven focus on particular kinds of text: +verse, drama, spoken text, dictionaries, and manuscript +materials. The next nine chapters deal with a wide range of topics, +one or more of which are likely to be of interest in specialist +applications of various kinds. The last two chapters deal with the XML +encoding used to represent the TEI scheme itself, and provide +technical information about its implementation. The last chapter also +defines the notion of TEI conformance and its implications for +interchange of materials produced according to these Guidelines.

+ +

As noted above, this is a reference work, and is not intended to be +read through from beginning to end. However, the reader wishing to +understand the full potential of the TEI scheme will need a thorough +grasp of the material covered by the first four chapters and the last +two. Beyond that, the reader is recommended to select according to +their specific interests: one of the strengths of the TEI architecture +is its modular nature.

+ +

As far as possible, extensive cross referencing is provided +wherever related topics are dealt with; these are particularly +effective in the online version of these Guidelines. In addition, a +series of technical appendixes provide detailed formal definitions for +every element, every class, and every macro discussed in the body of +the work; these are also cross linked as appropriate. Finally, a +detailed bibliography is provided, which identifies the source of many +examples cited in the text as well as documenting works referred to, +and listing other relevant publications.

+ + +

As an aid to the reader, most chapters of these Guidelines follow +the same basic organization. The chapter begins with an overview of +the subjects treated within it, linked to the following +subsections. Within each section where new elements are described, a +summary table is first given, which provides their names and a brief +description of their intended usage. This is then followed where +appropriate by further discussion of each element, including wherever +possible usage examples taken somewhat eclectically from a variety of +real sources. These examples are not intended to be exhaustive, but +rather to suggest typical ways in which the elements concerned may +usefully be applied. Where appropriate, a link to a statement of the +source for most examples is provided in the online version. Within the +examples, use of whitespace such as newlines or indentation is simply +intended to aid legibility, and is not prescriptive or normative.

+ +

Wherever TEI elements or classes are mentioned in the text, they +are linked in the online version to the relevant reference +specification for the element or class concerned. Element names are +always given in the form name, where name is the +generic identifier of the element; empty elements such as +pb or anchor include a closing slash to distinguish +them wherever they are discussed. References to attributes take the +form attname, where attname is the name of the +attribute. References to classes are also presented as links, for +example model.divLike for a model class, +and att.global for an attribute class. +

+ +
+ The use of modal verbs +

In general the TEI guidelines try to be careful when using modal verbs and phrases such as 'must', 'must not, + 'should', 'should not' and 'may'. In terms of the meanings, these generally follow in the different meanings of these words. + In particular: + + + This word, or the terms "REQUIRED" or "SHALL", means that this is an absolute requirement of the TEI Guidelines + for production of a TEI conformant file. + + This phrase, or the phrase "SHALL NOT", means that this is an absolute prohibition of the + TEI Guidelines for production of a TEI conformant file. + + This word, or the adjective "RECOMMENDED", means that there may exist valid reasons in + particular circumstances to ignore a particular recommendation, but the full implications + must be understood and carefully weighed before choosing a different course. + + This phrase, or the phrase "NOT RECOMMENDED" means that there may exist valid reasons in + particular circumstances when the particular behavior is acceptable or even useful, but the full implications + should be understood and the case carefully weighed before implementing any behavior so described. + + This word, or the adjective "OPTIONAL", means that a recommendation is truly optional. One user may + choose to follow the recommendation because a particular project requires it or feels that + it enhances their work while another project may choose to not follow this recommendation. + + However, the prose of the TEI Guidelines continually undergoes revision and all uses may not reflect this. Please report + any errors or unclear use of these words. +

+
+ +
+TEI Naming Conventions +

These Guidelines use a more or less consistent set of conventions +in the naming of XML elements and classes. This section summarizes +those conventions.

+
+Element and Attribute Names +

An unadorned name such as blort is the +name of a TEI element or attribute. During +generation of TEI RELAX NG schema fragments, the patterns corresponding +with these TEI names are given a prefix tei to allow them +to co-exist with names from other XML namespace. This prefix is not +visible to the end user, and is not used in TEI documentation. When +generating multi-namespace schemas, however, the user needs to be +aware of them. .

+

The following conventions apply to the choice of names: + +Elements are given generic identifiers as far as possible +consisting of one or more tokens, by which we mean whole +words or recognisable abbreviations of them, taken from the English +language. +Where an element name contains more than one token, the first +letter of the second +token, and of any subsequent ones, is capitalized, as in for example +biblStruct, listPerson. This +camelCasing is used also for attribute names and +symbolic values. +Module names also use whole words, for the most part, but are +always all lower case. +The specification for an element or attribute whose name +contains abbreviations generally also includes a gloss +element providing the expanded sense of the name. +An element specification may also contain approved translations +for element or attribute names in one or more other languages using +the altIdent element; this is not however generally done in +TEI P5. + +

+ +

Whole words are generally preferred for clarity. The following +abbreviations are however commonly used within generic identifiers: + + + +attribute + +bibliographic description or reference in a bibliography + +category, especially as used in text classification + +character, typically a Unicode character + +document: this usually refers to the original source document +which is being encoded, + +declaration: has a specific sense in the TEI +header, as discussed in + +description: has a specific sense in the TEI header, as +discussed in + +group. In TEI usage, a group is distinguished from a list in that +the former associates several objects which act as a single entity, +while the latter does not. For example, a linkGrp combines +several link elements which have certain properties in +common, whereas a listBibl simply lists a number of otherwise +unrelated bibl elements. + +interpretation or analysis +(natural) language +manuscript + +organization, that is, a named group of people or legal entity + +reading or version found in a specific witness +reference or link + +technical specification or definition + +statement: used in a specific sense in the TEI header, +as discussed in + +structured: that is, containing a specific set of +named elements rather than mixed content + +value, for example of a variable or an attribute + +witness: that is, a specific document which attests specific +readings in a textual tradition or apparatus + +

+

Some abbreviations are used inconsistently: for example, +add is an addition, and addSpan is a spanning +addition, but addName is an additional name, not the name of +an addition. Such inconsistencies are relatively few in number, and it +is hoped to remove them in subsequent revisions of these Guidelines.

+

Some elements have very short abbreviated names: these are for the +most part elements which are likely to be used very frequently in a +marked up text, for example p (paragraph), s +(segment) hi (highlighted phrase), ptr (pointer), +div (division) etc. We do not specifically list such elements +here: as noted above, an expansion of each such abbreviated name is +provided within the documentation using the gloss element +.

+
+
+
+Class, Macro, and Datatype Names + +

All named objects other than elements and attributes have one of +the following prefixes, which indicate whether the object is a module, +an attribute class, a model class, a datatype, or a macro: + +Component +Name +Example + +Attribute +Classesatt.*att.global +Model +Classesmodel.*model.biblPart +Macrosmacro.*macro.paraContent +Datatypesteidata.*teidata.pointer +
+

+

The concepts of model class, attribute class, etc. are defined in +. Here we simply note some conventions about their +naming.

+ +

The following rules apply to attribute class names: +Attribute class names take the form att.xxx, where +xxx is typically an adjective, or a series of adjectives +separated by dots, describing a property common to the attributes +which make up the class. +Attributes with the same name are considered to have the same +semantics, whether the attribute is inherited from a class, or locally +defined. + +

+ +

The following rules apply to model class names: +Model classes have names beginning model. followed +by a root name, and zero or more suffixes as described +below. +A root name may be the name of an element, generally the +prototypical parent or sibling for elements which are members of the +class. +The first suffix should be Part, if the class +members are all children of the element named rootname; or +Like, if the class members are all siblings of the +element named rootname. +The rootname global is used to indicate that class +members are permitted anywhere in a TEI document. +Additional suffixes may be added, prefixed by a dot, to +distinguish subclasses, semantic or structural. + +

+

For example, the class of elements which can form part of a +div is called model.divPart. This class +includes as a subclass the elements which can form part of a +div in a spoken text, which is named +model.divPart.spoken

+ + +
+ + + +
Design Principles + +

Because of its roots in the humanities research community, the TEI +scheme is driven by its original goal of serving the needs of research, +and is therefore committed to providing a maximum of comprehensibility, +flexibility, and extensibility. More specific design goals of the TEI +have been that these Guidelines should: + +provide a standard format for data interchange +provide guidance for the encoding of texts in this format +support the encoding of all kinds of features of all +kinds of texts studied by researchers +be application independent +This has led to a number of important design decisions, such as: + +the choice of XML and Unicode +the provision of a large predefined tag set +encodings for different views of text +alternative encodings for the same textual features +mechanisms for user-defined modification of the scheme +We discuss some of these goals in more detail below.

+ +

The goal of creating a common interchange format which is +application independent requires the definition of a specific markup +syntax as well as the definition of a large set of elements or +concepts. The syntax of the recommendations made in this document +conforms to the World Wide Web Consortium's XML Recommendation () +but their definition is as far +as possible independent of any particular schema language.

+

The goal of providing guidance for text encoding suggests that +recommendations be made as to what textual features should be recorded +in various situations. However, when selecting certain features for +encoding in preference to others, these Guidelines have tended to +prefer generic solutions to specific ones, and to avoid areas where no +consensus exists, while attempting to accommodate as many diverse views +as feasible. Consequently, the TEI Guidelines make (with relatively +rare exceptions) no suggestions or restrictions as to the relative +importance of textual features. The philosophy of these Guidelines is +if you want to encode this feature, do it this way—but very +few features are mandatory. In the same spirit, while these Guidelines +very rarely require you to encode any particular feature, they do +require you to be honest about which features you have encoded, that +is, to respect the meanings and usage rules they recommend for +specific elements and attributes proposed.

+

The requirement to support all kinds of materials likely to be of +interest in research has largely conditioned the development of the +TEI into a very flexible and modular system. The development of other +XML vocabularies or standards is typically motivated by the desire to +create a single fully specified encoding scheme for use in a +well-defined application domain. By contrast, the TEI is intended for +use in a large number of rather ill-defined and often overlapping +domains. It achieves its generality by means of the modular +architecture described in which enables each user +to create a schema appropriate to their needs without compromising the +interoperability of their data.

+

The Guidelines have been written largely with a focus on text capture +(i.e. the representation in electronic form of an already existing copy +text in another medium) rather than text creation (where no such copy +text exists). Hence the frequent use of terms like +transcription, original, +copy text, etc. However, these Guidelines are +equally applicable to text creation, although certain elements, such as sourceDesc, and certain attributes, such as the rendition indicators, will not be relevant in this case.

+

Concerning text capture the TEI Guidelines do not specify a +particular approach to the problem of fidelity to the source text and +recoverability of the original; such a choice is the responsibility of +the text encoder. The current version of these Guidelines, however, +provides a more fully elaborated set of tags for markup of rhetorical, +linguistic, and simple typographic characteristics of the text than for +detailed markup of page layout or for fine distinctions among type fonts +or manuscript hands. It should be noted also that, with the present +version of these Guidelines, it is no longer necessarily the case that +an unmediated version of the source text can be recovered from an +encoded text simply by removing the markup. +

+

In these Guidelines, no hard and fast distinction is drawn between +objective and subjective +information or between representation and +interpretation. These distinctions, though +widely made and often useful in narrow, well-defined contexts, are +perhaps best interpreted as distinctions between issues on which there +is a scholarly consensus and issues where no such consensus exists. +Such consensus has been, and no doubt will be, subject to change. The +TEI Guidelines do not make suggestions or restrictions as to which of +these features should be encoded. The use of the terms +descriptive and interpretive about different +types of encoding in these Guidelines is not intended to support any +particular view on these theoretical issues. Historically, it reflects +a purely practical division of responsibility amongst the original +working committees (see further ).

+

In general, the accuracy and the reliability of the encoding and the +appropriateness of the interpretation is for the individual user of the +text to determine. The Guidelines provide a means of documenting the +encoding in such a way that a user of the text can know the reasoning +behind that encoding, and the general interpretive decisions on which it +is based. The TEI header should be used to document and justify many +such aspects of the encoding, but the choice of TEI elements for a +particular feature is in itself a statement about the interpretation +reached by the encoder.

+ +

In many situations more than one view of a text is needed since no +absolute recommendation to embody one specific view of text can apply +to all texts and all approaches to them. Within limits, the syntax of +XML ensures that some encodings can be ignored for some purposes. To +enable encoding multiple views, these Guidelines not only treat a +variety of textual features, but sometimes provide several alternative +encodings for what appear to be identical textual phenomena. These +Guidelines offer the possibility of encoding many different +views of the text, simultaneously if necessary. Where different views +of the formal structure of a text are required, as opposed to +different annotations on a single structural view, however, the formal +syntax of XML (which requires a single hierarchical view of text +structure) poses some problems; recommendations concerning ways of +overcoming or circumventing that restriction are discussed in chapter +.

+ +

In brief, the TEI Guidelines define a general-purpose encoding +scheme which makes it possible to encode different views of text, +possibly intended for different applications, serving the majority of +scholarly purposes of text studies in the humanities. Because no +predefined encoding scheme can possibly serve all research purposes, +the TEI scheme is designed to facilitate both selection from a wide +range of predefined markup choices, and the addition of new (non-TEI) +markup options. By providing a formally verifiable means of extending +the TEI recommendations, the TEI makes it simple for such +user-identified modifications to be incorporated into future releases +of these Guidelines as they evolve. The underlying mechanisms which +support these aspects of the scheme are introduced in chapter , and detailed discussions of their use provided in +chapter .

+ +
Intended Use +

We envisage three primary functions for these Guidelines: + +guidance for individual or local practice in text +creation and data capture; +support of data interchange; +support of application-independent local processing. +These three functions are so thoroughly interwoven in practice that it +is hardly possible to address any one without addressing the others. +However, the distinction provides a useful framework for discussing the +possible role of these Guidelines in work with electronic texts.

+
Use in Text Capture and Text Creation +

The description of textual features found in the chapters which +follow should provide a useful checklist from which scholars planning to +create electronic texts should select the subset of features suitable +for their project.

+

Problems specific to text creation or text +capture have not been considered explicitly in +this document. These Guidelines are not concerned with the process by +which a digital text comes into being: it can be typed by hand, +scanned from a printed book or typescript, read from a typesetter's +tape, or acquired from another researcher who may have used another +markup scheme (or no explicit markup at all).

+

We include here only some general points which are often raised about +markup and the process of data capture.

+

XML can appear distressingly verbose, particularly when (as in these +Guidelines) the names of tags and attributes are chosen for clarity and +not for brevity. Editor macros and keyboard shortcuts can allow a +typist to enter frequently used tags with single keystrokes. +It is often possible to transform word-processed or +scanned text automatically. Markup-aware software can help with +maintaining the hierarchical structure of the document, and display the +document with visual formatting rather than raw tags.

+

The techniques described in chapter +may be used to develop simpler data capture TEI-conformant schemas, +for example with limited numbers of elements, or with shorter names +for the tags being used most often. Documents created with such +schemas may then be automatically converted to a more elaborated TEI +form.

+
+
Use for Interchange + +

The TEI format may simply be used as an interchange format, +permitting projects to share resources even when their local encoding +schemes differ. If there are n different encoding +formats, to provide mappings between each possible pair of formats +requires n×(n-1) translations; with an +interchange format, only 2×n such mappings +are needed. However, for such translations to be carried out without +loss of information, the interchange format chosen must be as +expressive (in a formal sense) as any of the target formats; this is a +further reason for the TEI's provision of both highly abstract or +generic encodings and highly specific ones.

+

To translate between any pair of encoding schemes implies: + +identifying the sets of textual features distinguished +by the two schemes; +determining where the two sets of features correspond; +creating a suitable set of mappings.

+

For example, to translate from encoding scheme X into the TEI +scheme: + +Make a list of all the textual features distinguished in +X. +Identify the corresponding feature in the TEI scheme. +There are three possibilities for each feature: + +the feature exists in both X and the TEI scheme; +X has a feature which is absent from the TEI scheme; +X has a feature which corresponds with more than one +feature in the TEI scheme. +The first case is a trivial renaming. The second will require an extension to +the TEI scheme, as described in chapter . The third +is more problematic, but not impossible, provided that a consistent +choice can be made (and documented) amongst the alternatives. +

+

The ease with which this translation can be defined will of +course depend on the clarity with which scheme X +represents the features it encodes.

+

Translating from the TEI into scheme X follows the same pattern, +except that if a TEI feature has no equivalent in X, and X cannot be +extended, information must be lost in translation.

+

The rules defining conformance to these Guidelines are +given in some detail in chapter . +The basic principles informing those rules may be summarized as +follows: + +The TEI abstract model (that is, the set of +categorical distinctions which it defines in the prose of the Guidelines) must be respected. The +correspondence between a tag X and the semantic function assigned to +it by these Guidelines may not be changed; such changes are known +as tag abuse and strongly discouraged. +A TEI document must be expressed as a valid XML-conformant +document which uses the TEI namespace appropriately. If, for example, +the document encodes features not provided by these Guidelines, such +extensions should not be associated with the TEI namespace. +It must be possible to validate a TEI document against a schema +derived from these Guidelines, possibly with extensions provided in +the recommended manner. + + +

+ + +
Use for Local Processing +

Machine-readable text can be manipulated in many ways; some users: + +edit texts (e.g. word processors, syntax-directed +editors) +edit, display, and link texts in hypertext systems +format and print texts using desktop publishing systems, +or batch-oriented formatting programs +load texts into free-text retrieval databases or +conventional databases +unload texts from databases as search results or for +export to other software +search texts for words or phrases +perform content analysis on texts +collate texts for critical editions +scan texts for automatic indexing or similar purposes +parse texts linguistically +analyze texts stylistically +scan verse texts metrically +link text and images

+

These applications cover a wide range of likely uses but are by no +means exhaustive. The aim has been to make the TEI Guidelines useful +for encoding the same texts for different purposes. We have avoided +anything which would restrict the use of the text for other +applications. We have also tried not to omit anything essential to any +single application.

+

Because the TEI format is expressed using XML, +almost any modern text processing system is able to process it, and +new TEI-aware software systems are able to build on a solid base +of existing software libraries.

+ +
Historical Background + +

The Text Encoding Initiative grew out of a planning conference +sponsored by the Association for Computers and the Humanities (ACH) and +funded by the U.S. National Endowment for the Humanities (NEH), which +was held at Vassar College in November 1987. At this conference some +thirty representatives of text archives, scholarly societies, and +research projects met to discuss the feasibility of a standard encoding +scheme and to make recommendations for its scope, structure, content, +and drafting. During the conference, the Association for Computational +Linguistics and the Association for Literary and Linguistic Computing +agreed to join ACH as sponsors of a project to develop these Guidelines. +The outcome of the conference was a set of principles (the +Poughkeepsie Principles, ), which +determined the further course of the project.

+ + +

The Text Encoding Initiative project began in June 1988 with funding +from the NEH, soon followed by further funding from the Commission of +the European Communities, the Andrew W. Mellon Foundation, and the +Social Science and Humanities Research Council of Canada. Four working +committees, composed of distinguished scholars and researchers from both +Europe and North America, were named to deal with problems of text +documentation, +text representation, text analysis and interpretation, and +metalanguage and syntax issues. Each committee was charged with the task of identifying +significant particularities in a range of texts, +and two editors appointed to harmonize the resulting recommendations.

+

A first draft version (P1, with the P here and subsequently +standing for Proposal) of the Guidelines was distributed in July +1990 under the title Guidelines for the Encoding and Interchange +of Machine-Readable Texts. +Extensive public comment and further work on areas not covered in +this version resulted in the drafting of a revised version, TEI P2, +distribution of which began in April 1992. This version included +substantial amounts of new material, resulting from work carried out by +several specialist working groups, set up in 1990 and 1991 to propose +extensions and revisions to the text of P1. The overall organization, +both of the draft itself and of the scheme it describes, was entirely +revised and reorganized in response to public comment on the first +draft.

+

In June 1993 an Advisory Board met to review the current state of +the TEI Guidelines, and recommended the formal publication of the work +done to that time. That version of the TEI Guidelines, TEI P3, +consolidated the work published as parts of TEI P2, along with some +additional new material and was finally published in May of 1994 +without the label draft, thus marking the +conclusion of the initial development work. +

+

In February of 1998 the World Wide Web Consortium issued a final +Recommendation for the Extensible Markup Language, XML.XML was originally developed as a way of publishing on +the World Wide Web richly encoded documents such as those for which +the TEI was designed. Several TEI participants contributed heavily to +the development of XML, most notably XML's senior co-editor +C. M. Sperberg-McQueen, who served as the North American editor for +the TEI Guidelines from their inception until 1999. +Following the rapid take-up of this new standard metalanguage, it +became evident that the TEI Guidelines (which had been published +originally as an SGML application) needed to be re-expressed in this +new formalism if they were to survive. The TEI editors, with +abundant assistance from others who had developed and used TEI, +developed an update plan, and made tentative decisions on relevant +syntactic issues.

+ +

In January of 1999, the University of Virginia and the University +of Bergen formally proposed the creation of an international +membership organization, to be known as the TEI Consortium, which +would maintain, develop, and promote the TEI. Shortly thereafter, two +further institutions with longstanding ties to the TEI (Brown +University and Oxford University) joined them in formulating an +Agreement to Establish a Consortium for the Maintenance of the Text +Encoding Initiative (), on which basis the TEI +Consortium was eventually established and incorporated as a +not-for-profit legal entity at the end of the year 2000. The first +members of the new TEI Board took office during January of 2001.

+ +

The TEI Consortium was established in order to maintain a permanent +home for the TEI as a democratically constituted, academically and +economically independent, self-sustaining, non-profit organization. In +addition, the TEI Consortium was intended to foster a broad-based user +community with sustained involvement in the future development and +widespread use of the TEI Guidelines ().

+ +

To oversee and manage the revision process in collaboration with +the TEI Editors, the TEI Board formed a Technical Council, with a +membership elected from the TEI user community. The Council met for +the first time in January 2002 at King's College London. Its first +task was to oversee production of an XML version +of the TEI Guidelines, updating P3 to enable users to +work with the emerging XML toolset. This, the P4 version of the Guidelines, +was published in June 2002. It was essentially an XML version of P3, +making no substantive changes to the constraints expressed in the +schemas apart from those necessitated by the shift to XML, and +changing only corrigible errors identified in the prose of the P3 +Guidelines. However, given that P3 had by this time been in steady use +since 1994, it was clear that a substantial revision of its content +was necessary, and work began immediately on the P5 version of the +Guidelines. This was planned as a thorough overhaul, involving a +public call for features and new development in a number of important +areas not previously addressed including character encoding, graphics, +manuscript description, biographical and geographical data, and the +encoding language in which the TEI Guidelines themselves are written.

+ +

The members of the TEI Council and its associated workgroups are +listed in . In preparing this edition, they have +been attentive to the requirements and practice of the widest possible +range of TEI users, who are now to be found in many different research +communities across the world, and have been largely instrumental in +transforming the TEI from a grant-supported international research +project into a self-sustaining community-based effort. One effect +of the incorporation of the TEI has been the legal requirement to hold +an annual meeting of the Consortium members; these meetings have +emerged as an invaluable opportunity to sustain and reinforce that +sense of community.

+

The present +work is therefore the result of a sustained period of consultation, +drafting, and revision, with input from many different +experts. Whatever merits it may have are to be attributed to them; the +Editors accept responsibility only for the errors remaining.

+ + +
+ +
Future Developments and Version Numbers + +

The encoding recommended by this document may be used without fear +that future versions of the TEI scheme will be inconsistent with it in +fundamental ways. The TEI will be sensitive, in revising these +Guidelines, to the possible problems which revision might pose for those +who are already using this version of these Guidelines. +

+

With TEI P5, a version numbering system is introduced following + the pattern specified by + the Unicode Consortium: the first digit identifies a major + version number, the second digit a minor version number, and the + third digit a sub-minor version number. The TEI undertakes that no + change will be made to the formal expression of these Guidelines + (that is, a TEI schema, as defined in ) such that + documents conformant to a +given major numbered release cease to be compatible with a subsequent +release of the same major number. Moreover, as far as possible, new +minor releases will be made only for the purpose of adding new +compatible features, or of correcting errors in existing features.

+ + +

The Guidelines are currently maintained as an open source project + on the Github site , from which released + and development versions may be freely downloaded. See Previous Releases of P5 for + information on how to find specific versions of TEI releases (Guidelines, + schemas etc.). Notice of errors detected and enhancements requested may + be submitted at .

+
diff --git a/P5/Source/Guidelines/fr/AI-AnalyticMechanisms.xml b/P5/Source/Guidelines/fr/AI-AnalyticMechanisms.xml deleted file mode 120000 index 98f2802ffd..0000000000 --- a/P5/Source/Guidelines/fr/AI-AnalyticMechanisms.xml +++ /dev/null @@ -1 +0,0 @@ -../en/./AI-AnalyticMechanisms.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/AI-AnalyticMechanisms.xml b/P5/Source/Guidelines/fr/AI-AnalyticMechanisms.xml new file mode 100644 index 0000000000..d398572221 --- /dev/null +++ b/P5/Source/Guidelines/fr/AI-AnalyticMechanisms.xml @@ -0,0 +1,1235 @@ + + + + +
Simple Analytic Mechanisms + +

This chapter describes a module for associating simple analyses and +interpretations with text elements. We use the term +analysis here to refer to any kind of semantic or +syntactic interpretation which an encoder wishes to attach to all or +part of a text. Examples discussed in this chapter include familiar +linguistic categorizations (such as clause, morpheme, +part-of-speech etc.) and characterizations of narrative +structure (such as theme, reconciliation etc.). The +mechanisms presented in this chapter are simpler but less powerful +than those described in chapter . +

+

Section introduces elements which can be used +to characterize +text segments according to the familiar linguistic categories of +sentence or s-unit, clause, +phrase, word, morpheme, +character, and punctuation mark. These elements represent special cases of the +generic seg element described in section .

+

Section introduces an additional global +attribute which allows passages of text to be associated with +specialized elements representing their interpretation. +These interpretative elements (span and +interp) are described in detail in section . +They allow the encoder to specify an analysis as a series of names and +associated values,Or, as they are widely known, +attribute-value pairs; this term should not be confused, +however, with XML attributes and their values, which are similar in +concept but distinct in their formal definitions. each such pair +being linked to one or more stretches of text, either directly, in the +case of spans, or indirectly, in the case of interpretations.

+

Finally section revisits the topic of linguistic +analysis, and illustrates how these interpretative mechanisms may be +used to associate simple linguistic analysis with text segments.

+ +
Linguistic Segment Categories +

In this section we introduce specialized linguistic segment +category elements which may be used to represent the segmentation of +a text into the traditional linguistic categories of +sentence, clause, phrase, +word, morpheme, +characters, and punctuation marks. +

+
Words and Above +

Although different languages have very different rules about what +constitutes a word or a +sentence, these remain generally useful concepts. +In this section we discuss elements provided for marking up linguistic +units down to the word level, however defined. + + +

+

As members of the att.segLike class, these +elements all share the following attribute: + +They also share attributes from att.typed: + +

+

These elements are also all members of the model.segLike class, which is a subclass of +model.phrase. They may thus appear anywhere +that text is permitted within a document, when the module defined by +this chapter is included in a schema.

+ +

The w and pc elements belong to the att.linguistic class, which supplies +attributes that may be used for lightweight linguistic annotation (see section below): +

+

Additionally, these elements also have access to the att.lexicographic.normalized class, +which supplies the attributes norm and orig: the former for handling +normalization/regularization at the word level, the latter providing the original form if the element +content is modernized or regularized. Note that these attributes are a local (word-level) alternative +to the robust mechanism that uses the choice, orig, and reg elements, +discussed in section and in chapter . The choice-based +mechanism is the default descriptive device, while the norm and orig attributes are used to +handle a subset of normalizations in linguistic contexts where a single sequence of tokens is a priority, for example +in historical corpora subject to linguistic analysis. It needs to be stressed that the simplified attribute-based +mechanism is not meant to be used for editorial interventions. +The att.lexicographic.normalized class is also used in dictionary +entries, as discussed in chapter .

+ +

The s element may be used simply to segment a text +end-to-end into a series of non-overlapping segments, referred to here +and elsewhere as s-units, or sentences. +

+ Nineteen fifty-four, when I was eighteen years old, + is held to be a crucial turning point in the history of + the Afro-American — for the U.S.A. as a whole — the + year segregation was outlawed by the U.S. Supreme Court. + It was also a crucial year for me because on June 18, + 1954, I began serving a sentence in state prison for + possession of marijuana. +

+ +The s element is more restricted both in its content and its +usage than the generic seg element. The seg unit may +contain anything which can appear within a paragraph: thus it may be +used to enclose members of the model.inter +class (such as bibl or list) as well as other phrase +elements; the s unit may only contain phrase-level elements +or text. Also, unlike seg elements, s elements +should not be nested within each other.Neither this +constraint, nor the requirement that the whole of the text be +segmented by s elements is required by the TEI +Guidelines. The seg element is intended for +use as a generic segmentation element, the specific function of which +may be indicated by its type attribute; the other members +of the class are more specialized. Thus, the s, cl, and +phr elements may be thought of as equivalent to seg +type="s-unit", seg +type="clause" and seg type="phrase", respectively, +but with the above-mentioned restrictions. +

+

The s element may be further subdivided into +clauses, marked with the cl element, +as in the following example: +

+ + It was about the beginning of September, 1664, + that I, among the rest of my neighbours, + heard in ordinary discourse + that the plague was returned again to Holland; + for it had been very violent there, and particularly at + Amsterdam and Rotterdam, in the year 1663, + whither, they say, it was brought, + some said from Italy, others from the Levant, among some goods + which were brought home by their Turkey fleet; + others said it was brought from Candia; + others from Cyprus. + + + It mattered not from whence it came; + but all agreed it was come into Holland again. + +

+

+

Clauses may be further divided into phr elements in the same +way. A text may be segmented directly into clauses, or into +phrases, with no need to include segmentation at a higher level as well. +

+

For verse texts, the overlapping of metrical and syntactic structure +requires that special care be given to representing both using an +element hierarchy. One simple approach is to split the syntactic phrases +into fragments when they cross verse boundaries, reuniting them +with the part attribute: +

+ Tweedledum and Tweedledee + Agreed to have a battle; + For Tweedledum said Tweedledee + Had spoiled his nice new rattle.
+
+ Just then flew down a monstrous crow, + As black as a tar barrel; + Which frightened both the heroes so, + They quite forgot their quarrel.
+ +Another approach is to use the next and prev +attributes defined in the additional module for linking (chapter ): +For Tweedledum said + Tweedledee + + Had spoiled his nice new rattle. +Other methods are also possible; for discussion, see chapter . +

+

The type attribute on linguistic segment categories can +be used to provide additional interpretative information about the +category. The function attribute on the cl and +phr elements can be used to provide additional information +about the function of the category. Legal values for these +two attributes are not defined by these Guidelines, but should be +documented in the segmentation element of the +encodingDesc element within the document's header. +A general approach to the encoding of linguistic categories for +parts of a text is discussed in section below. +

+

Using traditional terminology, these attributes provide a convenient +way of specifying, for example, that the clause from whence it +came is a relative clause modifying another, or that the +phrase by the U.S. Supreme Court is a prepositional +post-modifier: +It mattered not + from whence it came; + +the year segregation +was outlawed +by the U.S. Supreme Court. +

+

Segmentation into clauses and phrases can, of course, be combined. +Such detailed encodings as the following may require careful +formatting if they are to be easily readable however. +

+ + + Nineteen fifty-four, + + when I + was eighteen years old + , + + is held + + + to be + a crucial turning point + in + the history + of the Afro-American + + + — + for + the U.S.A. + as a whole + + + + — + the year + + segregation + + was outlawed + by the U.S. Supreme Court + . + + + It + + was + also + a crucial year for me + + because + on June 18, 1954, + I + + began serving + a sentence in state prison + for possession of marijuana +.

+

This style of markup may introduce spurious new lines and blanks +into the text. If the original layout is important, it should be +explicitly encoded, using such facilities as the lb element, +the global rend or rendition attributes, etc. +

+ +

The w, m, and c elements are identical +in meaning to the seg element with a type +attribute of w, m, or c respectively, and may +occur wherever seg is permitted to occur. However, their +content is more constrained than seg: for example, +the w element should only contain w, m, +c elements or pc elements, or plain text; the m element should +contain only c or pc elements or plain text; both +the c and pc elements +should contain only plain text, most often only a single character or +a sequence of graphemes to be treated as a single +character. Consequently, while these more specific elements can be +translated directly into typed seg elements, the reverse is +not necessarily the case. +

+

The restriction on the content of the w element in +particular requires that a certain care must be exercised when using it, +especially in relation to the use of other tags that one may think of as +word level, but which are in fact defined as phrase +level. Consider the problem of segmenting an occurrence of the +mentioned element as a word. +grandiloquent +The first of the following two encodings is legitimate; the second is +not, since the mentioned element is not part of the content +model of the w element: + +grandiloquent +grandiloquent

+

On the other hand, both of the following encodings are +legitimate: + + grandiloquent speech + + + grandiloquent speech + +The first encoding describes the citing of a phrase. The second +describes a phrase which consists of something mentioned. + +

+

The w element carries additional attributes +which may be of use in many indexing or analytic applications. The +lemma attribute may be used to specify the +lemma, that is the head- or uninflected form of an +inflected verb or noun, for example: + + timeo + Danaos + et + dona + ferentes + +

+

In some situations it may be more convenient to use the +lemmaRef pointer attribute than to supply an explicit +uninflected form. This attribute assumes the existence of a list of +uninflected forms, for example in an online lexicon, with which +individual w entries can be associated using the usual TEI +pointer mechanisms. Assuming that a +standardized lexicon for Latin is available at the location +http://lexicon.org/latin.xml, we might for example revise the above +example as: + + timeo + Danaos + +

+
+ +
Below the Word Level +

It is sometimes helpful to markup explicitly sub-word components +such as morphemes, characters, or punctuation. + + +

+ +

The m element is used to mark up morphologically +identified segmentation below the word level. Analogous to the +lemma attribute for w, there is a +baseForm attribute for the m element, +which may be used to indicate the base form of +an inflected morpheme; where appropriate, m elements may also +be organized hierarchically: + + + com + fort + + able + +

+

The distinction between m and w is provided as a +convenience only; it may not be appropriate for all linguistic +theories, nor is it meaningful in all languages. The intention is to +provide a means for those cases where it is considered helpful to distinguish +lexical from sub-lexical tokens, to complement the more general +mechanism already provided by the seg element, using which +the above example could alternatively be marked up as follows: + + + com + fort + + able + +See section for an alternative to using type in such contexts. +

+ +

There is a substantial +linguistic difference between characters like letters or diacritics +and punctuation marks. The former are used to +construct meaningful units like morphemes or words. The latter are +functionally independent units acting at the level of syntactic +units. A word may consist of a single letter (for example I in English), +but this does not mean that we should use c instead of w +to mark it up.

+ +

The c (character) element should be used to mark up any non-lexical +character, whether this appears within a word, or outside it. In the +following example, the encoder wishes to indicate that the letters are +not to be regarded as words: + + + + M + O + A + I + doth + sway + my + life + + +

+

The c element may be used for +individual characters occurring within a w or m +element which it is desired to distinguish for some reason, as in the +following examples: + + + n + ' + t + + +This encoding represents the constituents of a common abbreviation, +but does not indicate that it is in fact an abbreviation; the +am element () may be preferred for the +latter purpose. Generally speaking, the use of c use to mark +non-lexical punctuation marks is deprecated, since the pc +element is provided specifically to distinguish these. +

+ +

The pc (punctuation character) element should be used to mark up +characters which are specifically regarded as providing punctuation, +rather than constituting parts of a word. It may be particularly +useful when transcribing older written materials, in which an encoding +of the original punctuation may be useful for interpretive or analytic +purposes, in much the same way as an encoding of the original +orthography may be. For example, in the following extract from +a Bodleian Library musical manuscript +

+ +
+two different punctuation marks are used to distinguish kinds of pause +in the text. The punctus elevatus (which resembles an inverted +semicolon) is not a Unicode character, but may still be encoded using +the g element. As further described in chapter , this element points to a definition for the intended +character which may be stored either locally or elsewhere. + deus qui regis omnia +; natus est in bethlehem +.o . mira gratia... + + + + + +

+

The pc element carries special attributes to record +analyses of the functional behaviour or classification of the +punctuation mark it contains. The unit attribute may be +used, as on the milestone element to name the kind of unit +which the punctuation mark delimits, for example a paragraph or +section. The pre attribute may be used to indicate whether +the punctuation precedes or follows the unit it delimits. The +force attribute indicates the strength of the association +between the punctuation mark and its adjacent word.

+

In the following example, the paragraph marker (¶) has been tagged +as a strong punctuation mark, preceding the unit it marks, which is +named para: + +

Incipit...

+ +

+ +

A similar encoding can be used for hyphenation: + +A fire-proof vest is recom- +mended. + + + Refer to for a discussion of the motivations for + explicitely recording the presence of hyphens.

+ + +

The w, m, c, and pc elements can be used +together to give a fairly detailed low-level grammatical analysis of +text. For example, consider the following segmentation of the English +S-unit I didn't do it. +I + + did + n't + +do +it +. + +

+

This segmentation, crude as it is, succeeds in representing the idea +that did occurring as a morphological +component of the word +didn't has something in common with the word do. A further advantage of segmenting the text down +to this level is that it becomes relatively simple to associate each +such segment with a more detailed formal analysis, for example by +providing a baseform, or morphological analysis at whichever level is appropriate. +This matter is taken up in detail in section . +

+ + + + + + + + + + + + + + + +
+
+
Global Attributes for Simple Analyses +

When the module described by this chapter is selected, an +additional attribute is defined for all elements: + +The ana attribute may be specified for any element. +Its effect is to associate the element with one or more others +representing an analysis or interpretation of it. Its target should be +one of the elements described in the section below, +or some other interpretative element such as note, on which +see section or fs, +on which see chapter . If a hierarchical form of classification +is desired then it may point to category element at a suitable level in a +taxonomy see .

+ + + +
+
Spans and Interpretations +

The simplest mechanisms for attaching analytic notes in some +structured vocabulary to particular passages of text are provided by the +span and interp elements, and their associated +grouping elements spanGrp and interpGrp. +

+ +

These elements are all members of the class att.interpLike, and thus share the following attribute: + + They also inherit the following attributes from att.global.responsibility: + + +

+

The type attribute of the +span and interp elements may be used to indicate +that the annotations are of specific types, for example thematic or +structural. The annotation itself is supplied as the content of the +span or interp element. +In the case of the span element, the span of text being +annotated is indicated by values of the from, +to or target attributes, used in combination as +follows. If only the from attribute is supplied, then the +span is coterminous with the element indicated by its value; if both +from and to are supplied, the span runs from the +start of the element indicated by the from attribute up to +the end of the element indicated by the to attribute; if +the target attribute is used, the span is defined by +aggregating the contents of the (possibly non-contiguous) elements pointed to by its values. It +is an error to supply only the to attribute; to supply more +than one pointer value for either to or from +attributes; or to supply either of these in conjunction with the +target attribute. +In the case of interp (see below), the span is indicated by a +pointer from a link element or some similar mechanism. The +resp attribute indicates the annotator responsible for this annotation. +

+

The span element provides a simple way of indicating such +features as phrasal verbs in a linguistic analysis, as in this +example: + +Whatdidyoumakeup +phrasal verb "make up" + +Here the two components of the span follow each other, so the +to and from attributes may be used. The +same effect could however be achieved by using the target +attribute: + +Whatdidyoumakeup +phrasal verb "make up" + +This second approach might be cumbersome if the number of components +to be combined is very large. It is however essential if the +components do not follow each other, as in this example: + +Didyoumakeitup +phrasal verb "make up" + +

+

The span element can be used for any kind of +annotation. In this example it is used in a narratological analysis: +

+There was certainly a definite point at which the + thing began. +It was not; then it was suddenly inescapable, + and nothing could have frightened it away. +There was a slow integration, during which she, + and the little animals, and the moving grasses, and the sun-warmed + trees, and the slopes of shivering silvery mealies, and the great + dome of blue light overhead, and the stones of earth under her feet, + became one, shuddering together in a dissolution of dancing + atoms. +She felt the rivers under the ground forcing + themselves painfully along her veins, swelling them out in an + unbearable pressure; her flesh was the earth, and suffered growth + like a ferment; and her eyes stared, fixed like the eye of the + sun. +Not for one second longer (if the terms for time + apply) could she have borne it; but then, with a sudden movement + forwards and out, the whole process stopped; and that was the + moment which it was impossible to remember + afterwards. +the moment +For during that space of time (which was + timeless) she understood quite finally her smallness, the + unimportance of humanity. +

+

+

The span element may, as in this example, be placed in the +text near the textual span it is associated with. Alternatively, it may be placed +elsewhere in the same or a different document. Where several +span or interp elements share the same attributes, +for example having the same responsibility or type, it may be +convenient to group them within a spanGrp or interpGrp element as follows: + + the moment + + +

+

Spans may also be used to represent structural divisions within +a narrative, particularly when these do not coincide with the +structure implied by the element structure. Consider the following narrative: + +

Sigmund, the son of Volsung, was a king in Frankish country. +Sinfiotli was the eldest of his sons, the second was Helgi, the +third Hamund. +Borghild, Sigmund's wife, had a brother named — +But Sinfiotli, her stepson, and — both wooed the same woman +and Sinfiotli killed him over it.The rule marks spaces +left for the missing name in the manuscript. +And when he came home, Borghild asked him to go away, +but Sigmund offered her weregild, and she was obliged to accept it. +At the funeral feast Borghild was serving beer. She took poison, a big +drinking horn full, and brought it to Sinfiotli. When Sinfiotli looked +into the horn, he saw that poison was in it, and said to Sigmund This +drink is cloudy, old man. Sigmund took the horn and drank it off. +It is said that Sigmund was hardy and that poison did him no harm, +inside or out. And all his sons could tolerate poison on their skin. +Borghild brought another horn to Sinfiotli, and asked him to drink, and +everything happened as before. And a third time she brought him a horn, +and reproachful words as well, if he didn't drink from it. He spoke +again to Sigmund as before. He said Filter it through your mustache, +son! Sinfiotli drank it off and at once fell dead. +

+

Sigmund carried him a long way in his arms and came to a long, +narrow fjord, and there was a small boat there and a man in it. He +offered to ferry Sigmund over the fjord. But when Sigmund carried the +body out to the boat, it was fully laden. The man said Sigmund should +go around the fjord inland. The man pushed the boat out and then +suddenly vanished. +

+

King Sigmund lived a long time in Denmark in the kingdom of +Borghild, after he married her. Then he went south to Frankish lands, +to the kingdom he had there. Then he married Hiordis, the daughter of +King Eylimi. Their son was Sigurd. King Sigmund fell in a battle with +the sons of Hunding. And then Hiordis married Alf, the son of King +Hialprec. Sigurd grew up there as a boy. +

+

Sigmund and all his sons were tall and outstanding in their +strength, their growth, their intelligence, and their accomplishments. +But Sigurd was the most outstanding of all, and everyone who knows about +the old days says he was the most outstanding of men and the noblest of +all the warrior kings.

+

+

A structural analysis of this text, dividing it into narrative units +in a pattern shared with other texts from the same literature, might +look like this: +

+Sigmund ... was a king in Frankish country. +Sinfiotli was the eldest of his sons. +Borghild, Sigmund's wife, had a brother ... +But Sinfiotli ... wooed the same woman +and Sinfiotli killed him over it. +And when he came home, ... she was obliged to accept it. +At the funeral feast Borghild was serving beer. +She took poison ... and brought it to Sinfiotli. +Sinfiotli drank it off and at once fell dead. + +

+

Sigmund carried him a long way in his arms ...

+

King Sigmund lived a long time in Denmark ...

+

Sigmund and all his sons were tall ...

+ + introduction + conflict + climax + revenge + reconciliation + aftermath + +

+

Note the use of an empty anchor element to provide a target for +the reconciliation unit which is normally part of +the narrative pattern but which is not realized in the text shown. +

+ +

The same analysis may be expressed with the interp element +instead of the span element; this element provides attributes +for recording an interpretive category and its value, as well as the +identity of the interpreter, but does not itself indicate which passage +of text is being interpreted; the same interpretive structures can thus +be associated with many passages of the text. The association between +text passages and interp elements should be made either by +pointing from the text to the interp element with the +ana attribute defined in section , or by +pointing at both text and interpretation from a link element, + +as described in chapter . +

+

To encode the first example above using interp, it is +necessary to create a text element which contains—or corresponds to—the third, fourth, and fifth orthographic sentences (S-units) in +the paragraph. This can be done either with the seg element, +described in , or the join +element, described in . The resulting +element can then be associated with the interp element using the +ana attribute described in section . We illustrate using the seg element. +

+There was certainly a definite point ... +It was not; then it was suddenly inescapable ... + +There was a slow integration ... +She felt the rivers under the ground ... +Not for one second longer ... + +For during that space of time ... +

+the moment +

+

The second example above can be recoded using interp and +interpGrp tags in a similar manner. The interpretation +itself can be expressed in an interpGrp element, which would +replace the spanGrp in the example shown above: + + introduction + conflict + climax + revenge + reconciliation + aftermath + +

+

Any of these interp elements may be linked to the text either +by means of the ana attribute, or by means of link +elements. Using the ana attribute (on seg elements +introduced specifically for this purpose), the text would be encoded as +follows: +

+ +Sigmund ... was a king in Frankish country. +Sinfiotli was the eldest of his sons. +Borghild, Sigmund's wife, had a brother ... + +But Sinfiotli ... wooed the same woman +and Sinfiotli killed him over it. + +And when he came home, ... she was obliged to accept it. +At the funeral feast Borghild was serving beer. +Sinfiotli drank it off and at once fell dead. +

+ +

Sigmund carried him a long way in his arms ...

+

King Sigmund lived a long time in Denmark ...

+

Sigmund and all his sons were tall ...

+ +

+

The linkage may also be accomplished using a linkGrp element, +whose content is a set of link elements which point to each +interpretive element and its corresponding text unit. This method does +not require the use of the ana attribute on the text +units. + + + + + + + + +

+

One obvious advantage of using interp rather than +span elements for the Sigmund text is that the interp +elements can be reused for marking up other texts in the same document, +whereas the span elements cannot. On +the other hand, the use of interp elements may require the +creation of special text elements not otherwise needed (e.g. the +seg and the join in the revised encoding of the text), +whereas the use of span elements does not. +

+ + + + + + +
+
Linguistic Annotation +

By linguistic annotation we mean here any annotation +determined by an analysis of linguistic features of the text, excluding +as borderline cases both the formal structural properties of the text +(e.g. its division into chapters or paragraphs) and descriptive +information about its context (the circumstances of its production, its +genre or medium). The structural properties of any TEI-conformant text +should be represented using the structural elements discussed elsewhere +in this chapter and in chapters , , +, , , , +and . The contextual +properties of a TEI text are fully documented in the TEI header, which +is discussed in chapter , and in section . +

+

Other forms of linguistic annotation may be applied at a number of +levels in a text. A code (such as a word-class or part-of-speech +code) may be associated with each word or token, or with groups of such +tokens, which may be continuous, discontinuous, or nested. A code may +also be associated with relationships (such as cohesion) perceived as +existing between distinct parts of a text. The codes themselves may +stand for discrete and non-decomposable categories, or they may represent +highly articulated bundles of textual features. Their function may be +to place the annotated part of the text somewhere within a narrowly +linguistic or discoursal domain of analysis, or within a more general +semantic field, or any combination drawn from these and other domains. +

+

The manner by which such annotations are generated and attached to +the text may be entirely automatic, entirely manual or a mixture. The +ease and accuracy with which analysis may be automated may vary with the +level at which the annotation is attached. The method employed should +be documented in the interpretation element within the encoding +description of the TEI header, as described in section . +Where different parts of a language corpus have used +different annotation methods, the decls +attribute may be used to indicate the fact, as further +discussed in section . +

+
Linguistic Annotation by Means of Generic TEI Devices +

As one example of such types of analysis, consider the following +sentence, taken from the Lancaster/IBM Treebank +Project (). + The victim's friends told police that Kruger drove +into the quarry and never surfaced.

Our discussion focuses +on the way that this sentence might be analysed using the CLAWS system +developed at the University of Lancaster but exactly the same +principles may be applied to a wide variety of other systems.For the word-class tagging method used by CLAWS see +; +For an overview of the system see . The example sentence was processed +using an online version of the CLAWS tagger at +Output from the system consists of a segmented and tokenized version +of the text, in which word class codes have been associated with each +token. CLAWS offers outputs in a variety of non-XML and XML formats: +for example, the simplest format for the sample sentence would be: +

+

This may be easily transformed into an equivalent TEI XML representation: + +The +victim's +friends told +police that +Kruger drove into +the quarry +and never +surfaced + +Although the names used for the attribute values here may have some +significance for the human reader (AT0 for +article, NN1 for singular noun, +NN2 for plural noun, etc.) they are +arbitrary codes, used in this case as pointers to other elements which +define their significance more precisely. If the codes are considered +to be atomic, then the interp element described +in section might be used to supply brief definitions +in the header: + + + Definite article + Adverb + Conjunction + Relative that + Noun singular + Noun plural + Proper noun + Genitive marker + Preposition + Verb past tense + + + +If the codes are considered to +be compositional (for example that NN1 and NN2 +have something in common, namely their noun-ness, which +they do not share with, say, VVD), then this +compositionality may be most clearly expressed using a mechanism based +on the fs element defined in chapter . +

+

This approach requires the text to be fully segmented, using the +linguistic segment elements described in section , so that the scope of the ana attribute +used to point to each interpretation is clearly defined. A further +analysis into phrase and clause elements can be superimposed on the +word and morpheme tagging in the preceding illustration. For example, +CLAWS provides the following constituent analysis of the sample +sentence (the word class codes have been deleted): +

+

Treating the labels on the brackets as phrase or clause +interpretations, this analysis of the structure of the example sentence +can be combined with the word class analysis and represented as follows +(the symbol V&"/> representing the first part of a coordinate +phrase, has been replaced by V1, and V+, representing the +second part, has been replaced by V2). + + + + The + victim + 's + + friends + + + told + + police + + + that + + Krueger + + + + drove + + into + + the + quarry + + + + and + + never + surfaced + + + + + . + +

+

This approach requires the definition of further interp +(or fs) elements to provide targets for the pointers used to +represent the constituent analysis: + + + coordinate continuation + verbal + nominal + genitive + finite clause + prepositional + coordinate start + +

+ +

Alternatively, a stand-off representation for +these analyses might be created using the linkGrp element. +In this case, each linguistic segment to be annotated must be supplied with its own +xml:id attribute: + + +The +victim +'s friends +told police +that Kruger +drove into +the quarry +and never +surfaced + +Each segment-interpretation pair may now be represented by means of a +link element inside an appropriate linkGrp element: + + + + + + + + + + +

+

Each linguistic segment so far discussed has been well-behaved with +respect to the basic document hierarchy, having only a single parent. +Moreover, the segmentation has been complete, in that each part of the +text is accounted for by some segment at each level of analysis, without +discontinuities or overlap. This state of affairs does not of +course apply in all types of analysis, and these Guidelines provide a +number of mechanisms to support the representation of discontinuities or +multiple analyses. A brief overview of these facilities is provided in +chapter ; also see . These mechanisms +all depend to a greater or lesser degree on the use of pointing +elements of various kinds. +

+
+
Lightweight Linguistic Annotation +

While these Guidelines offer a variety of means to add linguistic information to textual +units and much of that has been presented above, two kinds of use cases and two groups of +users call for a dedicated set of specialized attributes to carry linguistic +information. One relevant use case is where basic linguistic information gets added to an +existing resource, in which generic attributes such as type or ana +have already been used to encode other categorizations and analyses. The other group of +users and use cases involves corpus linguists and resources built from scratch as lightly +annotated language corpora. In the latter kind of projects, energy and person-hours are not +devoted to careful literary analysis and hand-encoding of the relevant phenomena, but rather +to the analysis of the completed resources, and therefore the phase of resource-building must be +quick and relatively effortless, requiring minimal structural markup, well-established +containers for grammatical information, and a standardized way of filling them in.

+ +

The aims defined above can be realized by means of lightweight linguistic annotation using +attributes that belong to the att.linguistic class: + +

+ +

The essence of lightweight linguistic annotation is that the basic grammatical information +is encapsulated at the word level, together with the orthographic shape of the word. This +has clear advantages for automatic processing but, on the other hand, this form of data +encapsulation also imposes restrictions on the extent of information that can be encoded, +essentially limiting it to a single tokenization and lemmatization schema, a single tagset, +and a subset of the possible analyses (out from potentially many guesses at the +part-of-speech or morphosyntactic descriptions, single values have to fit into the existing +attributes). Another important principle that this kind of annotation is sensitive to is the +need for (near) homomorphism between the assumed tokenization (division of the text stream +into minimal units) and the division into minimal syntactic units (word forms, +in the terminology of ISO Morpho-Syntactic Framework, ISO 24611All +definitions contained within ISO standards can be accessed at the ISO Online Browsing Platform. For ISO MAF, see +.), because it is the former that results +from the process of tokenization, but the latter that can be lemmatized and meaningfully +described by means of grammatical features. Where tokens are only minimally mismatched with +word forms, various repair strategies can be used (e.g., recursing w to capture +multi-token compounds or using att.fragmentable to point at +disjoint tokens). Beyond that, more robust TEI mechanisms, based on standoff principles and +feature structures, should replace lightweight annotation.

+ + +

The basic grammatical information encoded by means of +att.linguistic is sufficient for the purpose of enhancing queries or improving +the analysis of search results by, for example, making it possible to distinguish between +the noun cut and the identically spelled verb +cut in English, and further between e.g. the present-tense form of +cut and its past-tense or past-participial forms. For the former +contrast, the part-of-speech (pos) attribute should be used, whereas the latter +may use pos and/or msd attributes, depending on the annotation +vocabulary adopted for the project in question. The various grammatical realizations of a +single dictionary word can be captured by means of the attribute lemma, which +provides a common label for them. For example, English verbs are typically lemmatized as the +base form (also called bare infinitive), so the value of lemma for +the verbal forms write, writes, +wrote, written, and +writing is typically write.

+ +

Together with the span-delimiting elements mentioned in this section, such as s, +cl, or phr, lightweight grammatical annotation may be used to build +basic syntactic constituency structures, where hierarchical information is expressed through +span containment rather than by relations among tree nodes. This is however the limit of +this kind of annotation: for the purpose of describing true constituency or dependency +syntactic structures, one needs to turn to more robust mechanisms offered by the TEI, which +may involve graph description (see chapter ) or standoff techniques (see +section ), and where grammatical labels may need to be annotated by +means of feature structures (see chapter ).

+ +

Some of the above-mentioned robust methods will also prove handy in cases where more than one tagset +(label inventory) is used to label the words, or where automatic morphological analysis yields multiple +possibilities (for example, the form cutting is morphologically ambiguous between +verbal, adjectival, and nominal) and needs to be followed by (often also automatic) disambiguation in +morphosyntactic contexts, with varying probabilities that may also need to be recorded together with their +corresponding part-of-speech and morphosyntactic values.

+ +

It should be borne in mind that tokenization, lemmatization, part-of-speech identification, and +morphosyntactic labelling, especially when performed automatically, should in most cases be seen as +involving pragmatic decisions, dictated by concrete practical goals, economy of description, or the +demands of particular analytic and/or visualization tools. It comes therefore as no surprise that +numerous alternative (and often conflicting) lemmatization strategies and tagsets exist, in use by +various communities and various tools, and that they change with time (a case in point is the CLAWS +tagset for English, with several versions that merge the part-of-speech and morphosyntactic information +to various degrees). +Given that the English language has relatively poor inflectional +morphology, the decision to merge part-of-speech symbols with morphosyntactic features (as +in, e.g., CLAWS-7, where the value PPHO1 signals the 3rd person singular objective personal +pronoun) is fully justified as the most economical approach. For languages with more +robust inflection, the pos and msd attributes will either be used +separately, or the part-of-speech information will be merged into the morphosyntactic +description. The nature and description of these systems is outside the scope of these +Guidelines, but it has to be stressed that all the strategies adopted for linguistic annotation, +even at the lightweight level of complexity, must be documented in the header of the +given electronic resource, not only for the purpose of guaranteeing successful data interpretation and exchange, but +also for the sake of sustainability of the results of the given project.

+ +

The last of the att.linguistic attributes, join, has the most text-technological +flavour. It can be used to amend the loss of whitespace-related information in non-inline +markup.

+

Compare the following two listings. The first difference between them is in the +tagset used (CLAWS-5 vs. CLAWS-7) and only serves to exemplify the need to document the +choice of descriptive vocabulary in the header, lest the encoded information is unreadable or +confusing. The second difference is the difference in the treatment of inter-token +whitespace, and it is here that the join attribute proves indispensable.

+ +

The first example listing uses CLAWS-5 and inline annotation, where whitespace serves as +part of the markup: + +The victim's friends + told police that Kruger + drove into the quarry + and never surfaced. +

+ +

In the second example, the attribute join is the only way to encode whether two +tokens are adjacent or not: + +The +victim +'s +friends +told +police +that +Kruger +drove +into +the +quarry +and +never +surfaced +.

+

Note that projects will need to decide whether they want to redundantly encode full +information on the adjacency of each token (in which case, the above listing should also +have join with the value right on the tokens +victim and surfaced, or whether information +on a single direction of adjacency is enough. Strategies vary, and it is important to +document them in the TEI header.

+

The following example shows a German sentence Wir fahren in den +Urlaub (We're going on vacation) annotated with all the attributes discussed +above.The annotation values have been adapted from the CLARIN Weblicht service, +where e.g. the full morphosyntactic description of the first item reads: [cat pronoun, +personal true, substituting true, person 1, case nominative, number plural], and has been +mapped from a sequence of attribute-value pairs suitable for feature structure notation, into a +compressed form that fits inside a single attribute value. + +Wir +fahren +in +den +Urlaub +. + + +

+

The final examples lay out a strategy for dealing with e.g. historical corpora where it is on +the one hand important to maintain a steady stream of token-level elements (w and +pc) for efficient processing, but, on the other hand, it is also important to +either record the original spelling (when the corpus text is normalized) or to record the +normalized variants (when the element content of the corpus preserves the original +spelling). The attribute class att.lexicographic.normalized can be used for that purpose: +

+

The first fragment below comes from "Gottfried, Newe Welt Vnd Americanische Historien. Frankfurt/M., 1631" +encoded in the Deutsches Textarchiv and records normalized forms in the norm attribute. + + vnuermuthete + Freundſchafft + angebotten +

+

The following example comes from the EarlyPrint project and uses the attribute orig to +record the original spelling (note that the xml:id attributes have been removed for the +sake of readability). + + he + hath + brought + forth +

+
+
Spoken Text +

The mechanisms proposed in this chapter may also be used to encode +analyses of an entirely different kind, for example discourse function. +Here is an application of the span technique to record details of a sales +transaction in a spoken text. +Can I have ten oranges and a kilo of bananas please? +Yes, anything else? +No thanks. +That'll be dollar forty. +Two dollars +Sixty, eighty, two dollars. Thank you. + + sale request + sale compliance + sale + purchase + purchase closure + +For further discussion of the u (utterance) element and other +elements recommended for transcriptions of spoken language, +see chapter . +

+
+
+ Module for Analysis and Interpretation +

The module described in this chapter makes available the + following components: + + Analysis and Interpretation + Simple analytic mechanisms + Mécanismes analytiques simples + 簡易分析機制 + Semplici meccanismi di analisi + Mecanismos simples de análise + 分析モジュール + + The selection and combination of modules to form a TEI schema is + described in . + + + +

+
+
diff --git a/P5/Source/Guidelines/fr/BIB-Bibliography.xml b/P5/Source/Guidelines/fr/BIB-Bibliography.xml deleted file mode 120000 index 084ad41329..0000000000 --- a/P5/Source/Guidelines/fr/BIB-Bibliography.xml +++ /dev/null @@ -1 +0,0 @@ -../en/./BIB-Bibliography.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/BIB-Bibliography.xml b/P5/Source/Guidelines/fr/BIB-Bibliography.xml new file mode 100644 index 0000000000..885cba0cea --- /dev/null +++ b/P5/Source/Guidelines/fr/BIB-Bibliography.xml @@ -0,0 +1,6369 @@ + +
+ Bibliography +
+ Works Cited in Examples in these Guidelines + + + 阿城，《棋王》。 + Académie française, + Rectifications de l'orthographe - J.O. du 06-12-1990, En ligne, + consulté le 05-03-2010. + + Adams, Douglas. The Hitchhiker's Guide to the + Galaxy, New York: Pocket Books, 1979, + chapter 31. + Agence bibliographique de l'enseignement + supérieur, ABES:Site internet + par l'ABES,consulté le 05-03-2010. + 阿拉伯短劍，國史館：嚴家淦總統文物。 + Alighieri, Dante. Doglia mi + reca ne lo core ardire, Rime, XLIX. + Allinson, E.P. and B. Penrose. + Philadelphia 1681-1887 (1887), p. 138. + American National Standard for Bibliographic + References, ANSI Z39.29-1977, New York: American + National Standards Institute (1977). + + + + Andersson, Theodore M.. A Preface to the Nibelungenlied, + Stanford University Press (1987). + + Andrews, Mr.. Song, Chambers's + Edinburgh Journal Series 1 + 9:463 (12 + December 1840), 376. + + Anouilh, Jean, + Antigone, 1842. + + [As in Visions of] Single leaf of Notes for a poem about night "visions," + possibly related to the untitled 1855 poem that Whitman eventually titled "The Sleepers." + Fragments of an unidentified newspaper clipping about the Puget Sound area have been pasted + to the leaf. The Trent Collection of Walt Whitman Manuscripts, Duke University Rare Book, + Manuscript, and Special Collections Library. + + + Atkins et al. + Collins Robert French-English English-French Dictionary. + London: Collins (1978). + + Atkinson, J. Maxwell and John Heritage. Structures of social action: Studies in conversation analysis, + Cambridge and Paris: Cambridge + University Press, Editions de la Maison des Sciences de + l'Homme (1984), ix-xvi. + Austen, Jane. Pride and + Prejudice. (1813), chapter + 1. + + + + 白先勇，〈金大班的最後一夜〉，《台北人》。 + 白先勇，《孽子》。 + 白居易，《憶江南》。 + + Amheida I: Ostraka from Trimithis Volume 1: Texts from the 2004–2007 Seasons, + Bagnall, R. S. and G. R. Ruffini, with contributions by R. Cribiore and G. Vittmann + (2012). + + + Baker, James K.. Night in Tarras. In Hilltop: A Literary Paper, vol 1 no 2. Wellington: Victoria University College + Literary Society. (1949). + Balzac, Honoré de, + Les Chouans, 1845. + Balzac, Honoré de, + Le Père Goriot, 1843. + Balzac, Honoré de, Petites misères de la + vie conjugale, 1850. + Barbauld, Lucy Aikin. The Works of Anna + Laetitia Barbauld (1826). + + Barker, Jane. The Lining to the Patch-Work Screen + (1726). + + Base de datos paleográfica da lírica galego-portuguesa (PalMed). Versión 1.2. + Santiago de Compostela: Centro Ramón Piñeiro para a + Investigación en Humanidades. . + f. B126r, column a, l. 21-32. + + Bataille, Michel , + L'Arbre de Noël, 1967. + + Les Chats, in : Baudelaire, Charles, Les Fleurs du mal, 1861. + + La Vie antérieure, in : Baudelaire, Charles, + Les Fleurs du mal, 1861. + 電影《霸王別姬》，1993年。 + Beck, Béatrice, Léon + Morin, prêtre, 1952. + Beckett, Samuel. Waiting for + Godot, London: Faber and Faber + (1956). + Beckett, Samuel. Murphy + (1963), chap 2. + Becque, Henry, La + Parisienne. Edition + électronique par l'ATILF et le CNRTL, d'après + l'édition de Fasquelle (Paris, 1922). + + Bowers, Jack + Mixtepec-Mixtec Project Personography + + + + + Beerbohm, Max. Autograph manuscript of The Golden Drugget, + Pierpont Morgan MA 3391. in 123. + Behn, Aphra. The Rover, + (1697). + + Beeton, Isabella. The book of Household Management, + London: S.O. Beeton + (1861). + Belloc, Denis , + Képas, 1989. + + Belloc, Denis , Néons, 1987. + Bentham, Jeremy. The Book of + Fallacies. (1824). + + Beowulf and The fight at Finnsburg; edited, with introduction, bibliography, + notes, glossary, and appendices, by Fr. Klaeber. Boston, New York + [etc.] + D.C. Heath & Co. (1922). + + Bibliographie dans le cadre de la semaine italienne du 11 au 18 mars 2006, , + document électronique. + Bibliothèque nationale de + France, Projet de description des reliures remarquables de la Réserve des + livres rares selon le modèle de la TEI manuscrits. + Billetdoux, Marie, Un + peu de désir sinon je meurs, 2006. + + Blake, William. London, in Songs + of Experience (1791). + + Blake, William. The Sick Rose, in Songs of Experience (1794). + + Blake, William. The Tyger, in Songs of Experience (1794). + Bloomfield, Leonard. Literate and + Illiterate Speech, American Speech, 2, (1927), pp. + 432-441. + Borges, Jorge Luis, tr. R. + Simms. The Analytical Language of John Wilkins. In + Emir Rodriguez Monegal and Alistair Reid, eds. Borges: A reader, Dutton Adult + (1981), p.141. + Borges, Jorge Luis. Avatars of + the Tortoise In James E. Irby tr. Labyrinths: Selected Stories and Other Writings, New York: + New Directions, (1962), pp.202-203. + Bouillier, Grégoire, + Rapport sur moi, 2002. + Bresson, Robert, Mouchette : script, l'Avant-scène cinéma, + n° 80, avril 1968. + Extract from British National Corpus () Text KB7, sentence 13730. + + Brontë, Charlotte. Jane Eyre: An Autobiography, + Third edition; reprintLondon + Service & Paton, 1897; + Project Gutenberg, 1 December 2020. + chapter XII. + + + + Browning, Robert. Letter to George Moulton-Barrett, Pierpont + Morgan MA 310, ( 23). + Buirette de Belloy, Pierre Laurent, + Gabrielle de Vergy, 1777. + + Bunyan, John. The Pilgrim's Progress from this world to that which + is to come..., London (1678). + Burgess, Anthony. A Clockwork + Orange. (1962), opening. + Burnard, Lou. Principles of + Database Design in S. Rahtz. ed. Information + Technology in the Humanities: tools, techniques and applications, Ellis + Horwood Ltd, Ellis Horwood Series in Computers and Their + Applications, (1987), p. 54. + Burnard, Lou, + Sperberg-McQueen, C. M., + <ref target="http://www.gutenberg.eu.org/publications/autres/TEILITE/">La TEI simplifiée, + une introduction au codage des textes électroniques en vue de leur échange -- version de + travail </ref> + , 1996. + + Burton, Robert. Anatomy of Melancholy + (1621), 16th ed. reprinted 1846, p. 743. + Butler, Samuel. The Way of All + Flesh (1903), chapter 37. + Byron, George Gordon. Don Juan + (1819), I.xxii. + Byron, George Gordon. Vision of + Judgment In E.H. Coleridge ed. The Poetical + Works of Lord Byron, viii, 1922. + + + + C 60/16 Fine Roll 6 HENRY III (28 October 1221-27 + October 1222), membrane 5, entry 154. + CBETA + Cædmon's Hymn in Bede's Historia Ecclesiastica (MS Kk. + 5. 16, Cambridge, University Library). + + Cabaret. A musical play, with book by Joe Masteroff, lyrics by Fred Ebb, and + music by John Kaner. Based on the play by John van Druten and stories by Christopher + Isherwood. 1966 + Edward Barkley, describing how Essex drove the Irish from the + plains into the woods to freeze or famish in winter; quoted by Canny, Nicholas + P. + The Ideology of English Colonization: From Ireland to America. In + Stanley N. Katz and John M. Murrin eds. Colonial America: Essays in Politics and Social Development, 3d + ed + New York: Knopf, (1983), p.53. + + + Carroll, Lewis. Through the Looking Glass, and what Alice + found there. (1871). + Catéchisme de l'Eglise + catholique, 1968. + + Cavendish, Margaret. Nature's Pictures. + London, 1656. Women Writers Online. Women + Writers Project, Northeastern University. 29 Mar. + 2015. + Centre national de la recherche scientifique + (France). UMR 7118 ATILF, <ref target="http://atilf.atilf.fr/tlf.htm">Le + Trésor de la Langue Française Informatisé (TLFI)</ref>, + 2004. + Example recoded from Chafe, W. + Adequacy, user-friendliness, and practicality in transcribing In + Leech, G., G. Myers, J. Thomas eds. + Spoken English on Computer: Transcription, Markup and + Applications. Harlow: Longman, + 1995. + + Chandler, Lloyd. + Conversation with Death (also known as Oh, + Death). In Journal of Folklore Research, 41.2/3, (2004), pp. + 125-126. + Chapman, Graham, Cleese, John, + Gilliam, Terry, Idle, Eric, Jones, + Terry. The complete Monty Pythons Flying Circus. + Chapman, Graham, Cleese, John, + Gilliam, Terry, Idle, Eric, Jones, + Terry. Monty Python's Life of Brian (1979). + + + Chaucer, Geoffrey. Canterbury Tales, f52r, in Holkham MS. + + Chaucer, Geoffrey. The Tale of Sir Topas, The Canterbury Tales, In F. N. Robinson ed. The Works of Geoffrey Chaucer, 2nd edition + Boston: Houghton Mifflin Co., + 1957. + 陳政彥，〈戰後臺灣現代詩論戰史研究〉，2007。 + + Cholières, Nicolas de, La Forest Nuptiale + (1600). + + Chomsky, Noam and Morris Halle. The Sound Pattern + of English. New York: Harper & Row (1968), p. 415. + Claude Simon + Le jardin des plantes, 1997, p 284 + + Cleaver, Eldridge. Soul on Ice. New + York (1968). + + Cloud of Unknowing In Hodgson, Phyllis ed. The Cloud of Unknowing and The Book of Privy Counselling, + London: Oxford University Press, Early + English Text Society, 218, (1944). + Clover, Carol J.The Medieval + Saga, Ithaca: Cornell University Press + (1982). + + Cocteau, Jean. La Machine Infernale. + Coleridge, Samuel Taylor. The + Rime of the Ancient Mariner. In Wordsworth, William and + Samuel Taylor Coleridge. Lyrical Ballads + (1798). + Coleridge, Samuel Taylor. Frost at + Midnight In E.H. Coleridge ed. Poetical + Works, Oxford: Oxford University + Press, (1967), p.240. + Colette, Colette à + l'école, 1900. + + Collins English Dictionary, 12th edition + Glasgow: Collins + (2014). + + Collins Pocket Dictionary of the English language. + London: Collins. + + Collins, Wilkie. The Moonstone, + Penguin, 6th narrative. + + Comenius, John Amos. Orbis Pictus: a facsimile of the + first English edition of 1659 (ed. John + E. + Sadler + ) Oxford University Press (1968). + Cope, Thomas Pym. Philadelphia + merchant: the diary of Thomas P. Cope, 1800-1851, Eliza Cope + Harrison ed. + Corneille, Pierre, + La Place Royale ou L'Amoureux extravagant, 1637. + Corneille, Pierre, + Théodore, vierge et martyre : tragédie chrétienne, + 1646. + + Cowley, Hannah. The Runaway (1813). + + Crashaw, Richard, ed. J.R. Tutin. The + Poems of Richard Crashaw. Muses Library Edition: + (1900). + + Creeley, Robert + A counterpoint in For Love: Poems 1950-1960 + (1962). + 崔西．雪佛蘭。《戴珍珠耳環的少女》。台北：皇冠，2003。 + + + + Dallas, George Mifflin. Unpublished + letter cited in Russell F. Weigley, Nicholas B. + Wainwright, Edwin Wolf eds. Philadelphia: A 300 + Year History, New York and London: + W. W. Norton & Company, 1982, p. 349. + Danhauser, Adolphe-Leopold, + Théorie de la musique, 1872. + + Darwin, Charles. Narrative of the Surveying Voyages of His Majesty's + ships Adventure and Beagle... volume 3 : Journal and Remarks (The Voyage of the + Beagle), chap 3. 1839. + Daudet, Alphonse, Les + contes du lundi, 1873. + + Davenant, William. The vvitts. A comedie, presented at the + private house in Blacke Fryers, by his Majesties servants. The author VVilliam D'avenant, + servant to Her Majestie. + London, 1636. [STC S109311] + + De Nutrimento et Nutribili, Tractatus 1, fol 217r col b of Merton College + Oxford MS O.2.1; in pl. 16. + + Dean of Sarum Churchwardens' presentments, 1731, Hurst; Wiltshire Record + Office; transcribed by Donald A. Spaeth. + Defoe, Daniel. The Fortunes and + Misfortunes of the Famous Moll Flanders (1722). + Defoe, Daniel. Robinson + Crusoe (1719). + + Defoe, Daniel. Journal of the Plague Year. + London (1722). + + Dekker, Thomas and Thomas Middleton. The Honest + Whore, Part One (1604). + Deloney, Thomas. Thomas of Reading or the + Sixe Worthie Yeomen of the West (1612). + Dennery, Annie. Du mélos à la note : Les notations musicales au Moyen Age, Médiévales, n° 3 + 1983. + Dickens, Charles. A Christmas + Carol in Prose, Being a Ghost Story of Christmas, Chapman and + Hall, (1843), p. 5, p. + 12. + Dickens, Charles. Little + Dorrit, (1857). + Dickinson, Emily. 1755 In + Arthur Eastman et al. eds. The Norton Anthology of + Poetry, New York: W.W. Norton, + 1970, p.859. + Diderot, Denis, + Lettres à Sophie Volland, 26 sept. 1762. + 〈第三屆第一次大會第一次會議記錄〉，臺灣省諮議會。 + Disraeli, Benjamin. Coningsby (1844), preface. + Doyle, Arthur Conan. The + Red-headed league. In The Adventures of Sherlock Holmes + (1892). + + Doyle, Arthur Conan. The Original Illustrated Sherlock + Holmes, Castle Books, 1989. + Drawing of a leaden plaque bearing an inquiry by Hermon from the + oracular precinct at Dodona. Catalogue no 725; LSAG 230.13. Image from + Dubois, Jacques, Nyssen, + Hubert (dir. de collection), Babel, Actes + sud,1989-.... + Dubois, Jean, + Dictionnaire de linguistique, 1974. + + Dudo of St Quentin. De moribus et actis primorum Normannie + ducum, fol 4v of British Library MS Harley 3742; in pl + 6(i). + Dufournaud, Nicole, + Numérisation des Titres de famille, édition électronique, 2002. + Duhamel, Georges, + Chronique des Pasquier, 1933-1945. + + Dutt, Toru. Lakshman In Ancient + Ballads and Legends of Hindustan, Kegan Paul, Trench & + Co., (1882) + Dylan, Bob. All Along the + Watchtower In John Wesley Harding + (1967). + Dylan, Bob. Positively 4th + Street In Highway 61 Revisited + (1965). + + + + + Eddic poems, in Reykjavík, Landsbókasafn Íslands, Lbs 1562 4to. + Editorial, .EXE + magazine, 6.11 (1992), + p. 2. + Eliot, George. Middlemarch (1871), I.1. + + Eliot, George. Middlemarch (1871), + I.XXI. + + Eliot, George. Daniel Deronda (1876), + III.1. + Eliot, Thomas Stearns. The + waste land: a facsimile and transcript of the original drafts including the annotations of + Ezra Pound, Eliot, Valerie ed. Faber and Faber + Ltd. (1971), p. 37. + + Scalable Vector Graphics (SVG) 1.1 (Second Edition). Editors + Erik Dahlström, Jon Ferraiolo, 藤沢 淳, Anthony Grasso, Dean + Jackson, Chris Lilley, Cameron McCormack + Doug Schepers, Jonathan Watt and Patrick + Dengler. World Wide Web Consortium (W3C) (22 June + 2010). Available from . + Ernaux, Annie, Se + perdre, 1988. + Ernaux, Annie, L'usage + de la photo, 2005. + + + <ref target="http://www.etudes-litteraires.com/figures-de-style/deictique.php">Études + littéraires</ref> + , consulté le 07-05-2010. + + + + Fallet , René, Le + Triporteur, 1951. + Field, Syd + Screenplay: the Foundations of Screenwriting (1998). + Fielding, Henry. The History of + the Adventures of Joseph Andrews and his Friend, Mr. Abraham Abrams + (1742). + + Fielding, Henry. Tragedy of Tragedies, + (1737). + + Fish, Stanley. Is there a text in this class? The authority of + interpretive communities. Harvard University Press + (1980). + Fisher, M. F. K. I Was Really Very + Hungry In As They Were, Knopf + (1982), p. 43. + + + FitzGerald, Edward. The Rubáiyát of Omar Khayyám, translated into + English Verse (1859), stanza 25. + Flaubert, Gustave, + Salammbô, 1862. + Flaubert, Gustave, + La Tentation de saint Antoine, 1874. + Foley James D., Andries van Dam, + Steven K. Feiner and John F. Hughes. Computer Graphics: Principles and Practice, 2nd edition + Reading: Addison-Wesley, p.259. + Forster, E.M., Howards + End. Edward Arnold. (1910). + + + <ref target="http://sites.radiofrance.fr/franceinter/em/labassijysuis">France inter, + Là-bas si j'y suis</ref> + , consulté le 07-05-2010. + + + <ref target="http://sites.radiofrance.fr/franceinter/em/letelephonesonne/contact.php" + >France inter, Le téléphone sonne</ref> + , consulté le 07-05-2010. + + + <ref target="http://franglais.ini.hu/">Franglais et franricain</ref> + , consulté le 07-05-2010. + Fry, Christopher, The firstborn + (1948). + 福春嫁女 + + Fussell, Paul. The Norton Book of Travel. W. W. + Norton (1987). + + + + Galilei, Galileo, Sidereus + Nuncius, Venetiis: Apud Thomam + Baglionum, 1610, quoted by Tufte, Edward R., + Envisioning Information, Cheshire: + Graphics Press (1990), p. + 97. + Galland, Antoine, Les + Mille et une nuits, 1704. + Galsworthy, John, Strife. In + Plays, vol 1. (1909). + Gaskell, Elizabeth Cleghorn. The Grey Woman, MS. + Gavioli, Laura and Gillian + Mansfield. The PIXI corpora: bookshop encounters in English and + Italian, Bologna: Cooperativa Libraria + Universitaria Editrice (1990), p.74. + Gay, John. The Beggar's Opera + (1728). + Gazdar, Gerald and Mellish, + Christopher. Natural language processing in Prolog. + Addison-Wesley (1989), p.5. + + Gazdar, Gerald, Ewan Klein, Geoffrey Pullum, and Ivan Sag: + Generalized Phrase Structure Grammar, Harvard + University Press (1985). + + Gershwin, Ira + By Strauss (from An American in Paris, 1953). + Gianfraco Contini, Poeti del + Duecento, Milano-Napoli:Ricciardi I, (1960). pp 155-64. + Gibbon, Edward, The History of the + Decline and Fall of the Roman Empire, (1789), chapter 58. + Gide, André, Le + Journal des Faux-Monnayeurs, 1927. + Gide, André, Journal : + 1889-1939, 1939. + + Gilbert, William Schwenck and Sullivan, Arthur. HMS Pinafore (1878), I. + Gilbert, William Schwenck and Sullivan, + Arthur. The Mikado (1885). + Ginsberg, Allen. My alba, + Reality Sandwiches, San Francisco: + City Lights, (1963). + Giono, Jean, + Regain, 1930. + Giraudoux, Jean, La + guerre de Troie n'aura pas lieu, 1935. + + Godefroy, Frédéric, Dictionnaire de l'ancienne langue française et + de tous ses dialectes du IXe au XVe siècle, 1881. + Goethe, Johann Wolfgang von, tr. Philip Wayne. Faust, Part + 1, London: Penguin. (1949). + + Goethe, Johann Wolfgang von. Auf dem See + (1775). + + [Goldsmith, Oliver], The History of Little GOODY TWO-SHOES; + Otherwise called, Mrs. MARGERY TWO-SHOES... (Printed for J. Newbery, + 1766). + + Grallert, Till, Tools for the Computational Normalisation and + Analysis of Food Prices and Food Riots in the Eastern Mediterranean (Bilād al-Shām) in the + 19th and 20th Centuries. Zenodo, 2021. . + + Graves, Robert. Rough draft of letter to Desmond Flower. + 17 Dec 1938. (from Diary of Robert Graves 1935-39 and + ancillary materials, compiled by Beryl Graves, C.G. Petter, L.R. Roberts, + University of Victoria Libraries). + + Greene, Robert. Groatsworth of Wit Bought with a Million + of Repentance (1592). + + Gregory of Tours. Ecclesiastical History of the + Franks (translated by Lewis Thorpe). + Greimas, Algirdas Julien + et Courtés, Joseph, Sémiotique : dictionnaire raisonné de la théorie + du langage, 1979. + Grune, Dick and Ceriel J. H. + Jacobs. Parsing Techniques: A Practical Guide, + New York and London: Ellis + Horwood, 1990, p. 24. + + Guerard, Françoise. Le Dictionnaire de Notre Temps, ed. + Paris: Hachette, 1990 + + + + + Hall, Radclyffe. The well of + loneliness. (1928). + Halliday, M.A.K. and R. + Hassan. Language, Context and Text: Aspects of Language in a + Social-Semiotic Perspective, Oxford: Oxford + University Press, 1990, p. + 104. + Hanks, Patrick. Definitions and + Explanations. In J. M. Sinclair ed. Looking Up. + Collins, 1987, p. 121 + . + Hannam's last farewell to the world:: being a full and true + relation of the notorious life and shamfull death of Mr. Richard Hannam... + (1656). + + Hansberry, Lorraine. A raisin in the sun. + (1959). + Harvey, Gabriel. Four letters and certain + sonnets specially touching Robert Greene... (1592). + Harvey, William. Exercitatio Anatomica De Motu Cordis Et Sanguinis In Animalibus, 1949 (Third edition, second printing), p. 74. + Hobbes, Thomas. Leviathan + (1681). + 《紅樓夢》第六回：賈寶玉初試云雨情 劉姥姥一進榮國府 + 〈紅頭嶼踏查報告〉，國立台灣大學圖書館：田代文庫。 + Hoola Van Nooten, + BertheFleurs, fruits et feuillages choisis de l'île de Java peints d'après + nature, troisième édition par C. Muquardt, Bruxelles, + 1880. + + Hornby, A.S. et al. Oxford Advanced Learner's Dictionary of Current + English. Oxford University Press (1974). + 黃晨淳編著，《希臘羅馬神話故事》，p76。 + Hugo, Victor, + Notre-Dame de Paris, 1845. + + Souvenir de la nuit du 4, in : Hugo, Victor, + Les Contemplations, 1853. + Hugo, Victor, Les + Misérables, 1862. + + A la fenêtre pendant la nuit, in : Hugo, Victor , + Les Contemplations, 1856. + Huizinga, Johan, + L'Automne du Moyen-Âge, 1919. + + + + ISO 690:1987: Information and documentation – + Bibliographic references – Content, form and structure + clause 4.1, p.2. + ISO 24611:2012 Language resource management — Morpho-syntactic annotation framework (MAF). + International Organization for Standardization. 2012. + + Ibsen, Henrik, tr. William and Charles Archer. + Peer Gynt (1875). + + Ibsen, Henrik + Den episke Brand KBK Collin 2869, 4º I, fol. 11v. + + Ibsen, Henrik + Digte NBO Ms.4º 1110a, p. 36. + + Ibsen, Henrik + Brand, The Royal Library, Denmark. KBK Collin 262, 4°, I.1.1, fol. + [4]v + Ibsen, Henrik, tr. R. + Farquharson Sharp and Eleanor Marx-Aveling. + A Doll's House In A Doll's House; and Two Other + Plays by Henrik Ibsen, Everyman's library: the drama 494 + , London: J. M. Dent & Sons, + 1910. + Idle, Eric, Michael Palin, + Graham Chapman, John Cleese, Terry + Gilliam. The Complete Monty Python's Flying Circus: All the + Words, Pantheon Books, (1989), 2, p.230. + Imbs, Paul, Martin, + Robert, Straka, Georges, Mélanges de linguistique + française et de philologie et littérature médiévales offerts à Monsieur Paul + Imbs, 1973 . + Institut de Littérature Française Moderne de + l’Université de Neuchâtel, Présentation du projet Cyrus, En ligne, consulté le + 05-03-2010. + Ionesco, Eugène, La + cantatrice chauve, 1950. + 羅貫中，《三國演義》。 + + + + + Jakacki, Diane. Schema question: further constraining + @subtype based on @type. January 18, + 2021. TEI (Text Encoding Initiative) public discussion + list, . + Jarry, Alfred, tr. Simon Watson + Taylor and Cyril Connolly. The Ubu + plays, London: Methuen, + 1968. + Jean-Jacques Rousseau + Les confessions vol 6 + Jerome, Jerome K. + Three men in a boat (1889), chapter 6. + Joachim Heinrich + CampeWörterbuch der Deutschen Sprache. Erster Theil. A - bis - E., + 1807. + John, Lord Sheffield, The + Auto-biography of Edward Gibbon esq., (1846), 222. + Jonson, Ben. Bartholomew + Fair. + Jonson, Ben. Volpone, + J. B. Bamborough ed. Macmillan, 1963, + p.14. + Jonson, Ben. The Alchemist + , Douglas Brown ed. London: + Benn, 1966, I.1, + p.9. + Joyce, James. Ulysses: + The Bodley Head, 1960. p. + 933. + + Judith Patt, Michiko Warkentyne and Barry + Till. Haiku: Japanese Art and Poetry. 2010. + Pomegranate Communications, Inc. San Francisco. . + + + + + Karlstadt, Andreas + Bodenstein. Distinctiones Thomistarum. + Wittenberg + 1507. In Harald Bollbuck ed. Kritische Gesamtausgabe + Karlstadt + I, available: + + Kersey, John. Dictionarium + Anglo-Brittannicum: Or, a General English Dictionary. London: + J. Wilde, 1715. 2nd ed. + Kilian, Wilfrid, <ref + target="http://jubil.upmc.fr/sdx/pl/toc.xsp?id=GH_000484_001&fmt=upmc&idtoc=GH_000484_001-pleadetoc&base=fa" + >Neige et glaciers ; notes prises au cours de géologie de la Faculté des Sciences de + Grenoble par M. Alamelle</ref>, 1891-1895. + King, Martin Luther. Letter from Birmingham City + Jail. Philadelphia, PA: American Friends Service + Committee (1963). + Kipling, Rudyard. The mother + hive. In Actions and Reactions, + London: Macmillan, (1909). + + Kipling, Rudyard. Stalky & Co., + London: Macmillan (1899). + Kipling, Rudyard. Kim, + Macmillan, (1901), p. + 9. + Knuth, Donald Ervin. The Potrzebie + System of Weights and Measures, Mad Magazine33June 1957. + Koltès, + Bernard-Marie, Quai ouest, 1985. + Krummrey, Hans, Panciera, Silvio + Criteri di edizione e segni diacritici, Tituli 2 (1980), + 205-215. + Kyd, Thomas. Spanish Tragedy + (1592). + + + + La Fayette, Marie-Madeleine Pioche + de La Vergne, comtesse de, La Princesse de Clèves, + 1678. + La Fontaine, Jean de. L'Astrologue + qui se laisse tomber dans un puits In Fables Choisies, + Classiques Larousse, Paris: Librairie + Larousse, 1, 1940. + La Fontaine, Jean de. Le corbeau + et le renard In Fables Choisies, Classiques + Larousse, Paris: Librairie Larousse, + 1, 1940. + Laboratoire ATILF + + <ref target="http://www.atilf.fr/">Analyse et traitement informatique de la langue + française (ATILF)</ref> + , consulté le 07-05-2010. + + Laclos, Pierre Choderlos de. Les Liaisons + dangereuses (1772), 1963, p. + 13. + Ladurie, Emmanuel Le Roy. Montaillou, Middlesex: Penguin Books, + 1980, p. 3. + Lamartine, Alphonse de, + Méditations poétiques, 1820. + Lamothe, Alexandre + de + Principaux manuscrits latins et français conservés dans la Bibliothèque + impériale et dans celle de l'Ermitage à Saint-Pétersbourg, édition numérique, Bibliothèque de l'école nationale des + chartes, 1864. + Langendoen, D. Terence and Paul M. + Postal. Vastness of Natural Languages, + Oxford: Basil Blackwell, 1984, p. + 24, note 12. + Langendoen, D. Terence and Paul Postal. The + vastness of natural languages, Blackwell, , 1, 1984. + + Langland, William. The Vision of Piers Plowman. In + A.V.C. Schmidt ed. Langland: Vision of Piers Plowman: + "B" Text, opening. + Latin liturgical manuscript: Bod MS. Lat liturg. b. + 19, folio 4r. Taken from the digitized image described at . + Lavrentev, Alexei, + <ref target="http://ccfm.ens-lsh.fr/IMG/pdf/BFM-Mss_Encodage-XML.pdf">Manuel + d’encodage XML-TEI étendu des transcriptions de manuscrits dans le projet + BFM-Manuscrits</ref>, dernier enregistrement le 26 juin + 2008. + + Lawrence, David Herbert. Autograph manuscript of Eloi, Eloi, lama + sabachthani, Pierpont Morgan MA 1892; in p.129. + + Layamon. Brut, fol 65v of Bodleian MS. Rawlinson Poetry 32; + in 12(ii). + Le Grand Robert de la langue + française, 2004. + LeTourneau, Mark S. + English Grammar, 2001, New York: + Harcourt + p. 89. + + Leech, G., G. Myers, J. Thomas eds. + Spoken English on Computer: Transcription, Markup and + Applications. Harlow: Longman, + 1995. + Leech, Geoffrey and Mick Short. + Style in Fiction, London: + Longman, 1981, p.272. + + Lennon, John and McCartney, Paul. She + Loves You. The Beatles Anthology 1. + Capitol, 1995. + Léry, Jean de, Histoire faict + en la terre de Brésil, 1580. + + Lessing, Doris. Martha Quest. 1952, + pp. 52-53. + Letter of Mikołaj Orlik to Mikołaj Serafin, Gródek, January 13 + [1438]. Edited by Skolimowska et al. Available from + Lewis, Leopold Davis. The + Bells, (1871), translated from Erckmann-Chatrian, + Le Juif Polonais. + + Lewis, Wyndham. Tarr (1928), + Jupiter, 1968, p. 17. + 李白，《黃鶴樓送孟浩然之廣陵》。 + 李白，《靜夜思》。 + 《梁山伯與祝英台》 + 電影《梁山伯與祝英台》，舊版。 + 〈歷代漢文大藏經概述〉，李圓淨，原載《南行》第六期（南行學社編印）。 + Lillo, George. The London + Merchant (1731), epilogue. + 林覺民，《與妻訣別書》。 + Lincoln, Abraham. Second Inaugural + Address, 4 March 1865. In H. S. Commager, ed., + Documents of American History, 5th ed + Crofts American history series. New York: + Appleton-Century-Crofts, 1949, p.442. + 劉康，《對話的喧囂：巴赫汀文化理論評述》，台北：麥田，2005，二版。 + 劉康，《對話的喧聲：巴赫汀文化理論述評》，台北：麥田，2005，頁20-23。 + + Longman Dictionary of Contemporary English. Harlow, + Essex: Longman (1978). + Lorris, Guillaume de et + Meun, Jean deLe Roman de la Rose, 1230, + 1270-1285. + Lowe, David. Lost + Chicago, Boston: Houghton Mifflin, + (1978), p.30. + + Lowell, Amy. Autumn + haze.(1919). + Lucie Lichtig, M. + Klein de Joseph Losey : script, . l'Avant-scène cinéma, + n° 175, nov. 1976. + Luther, Martin [tr]. Die gantze + Heilige Schrifft Deudsch, Wittenberg 1545. Letzte zu Luthers Lebzeiten erchienene Ausgabe, + hsg. Hans Volz unter Mitarbeit von Heinz Blanke. Textredaktion Friedrich Kur, + München: Rogner & Bernhard, + 1972. + 《論語》卷七：憲問第十四。 + 羅貫中，《三國演義》。 + 魯迅，《狂人日記 》。 + 魯迅，《狂人日記》。 + 魯迅，《狂人日記》。 + + + + MacNeice, Louis. The Sunlight on + the Garden In E.R. Dodds, + The collected poems of Louis MacNeice, London: + Faber, 1966. + Examples from MacWhinney, Brian, 88, 87, cited by Johansson, S. + The approach of the Text Encoding Initiative to the encoding of spoken + discourse In Leech, G., G. Myers, J. + Thomas eds. Spoken English on Computer: Transcription, Markup + and Applications. Harlow: Longman, + 1995. + + Madan, Falconer, et al, A summary catalogue of western manuscripts + in the Bodleian Library at Oxford which have not hitherto been catalogued ... + Oxford, 1895-1953. 5: 515. + Cited in Driscoll, M.J. P5-MS: A general purpose tagset for + manuscript description in Digital Medievalist: + 2.1, (2006) + + Maingeneau, Dominique, + Analyser les textes de communication, 2007. + Any issue of the Malawi Daily Times. + + Malle, Louis, Zazie + dans le métro : script, l'Avant-scène cinéma, n° + 104, juin 1970. + + Manuélian, Hélène, Schang, Emmanuel, XML, DTD et + TEI pour un dictionnaire étymologique des créoles, édition électronique, + 12 Octobre 2007. + + The Manere of Good Lyuynge: fol. 126v of Bodleian MS Laud Misc 517; + in , p.8. + Marbury v. Madison, 1 Cranch, + 137 (1803), rpt. In H. S. Commager, ed., Documents of American History, 5th ed + Crofts American history series. New York: + Appleton-Century-Crofts, 1949, + p.192. + Marvell, Andrew. An Horatian + Ode, Bod. MS Eng. Poet d.49. + Mauriac, Claude, + La Marquise sortit à cinq heures, 1961. + Mauss, Marcel, + Sociologie et anthropologie, 1950. + McCarthy, Niall, No + Parachute: The Highest Falls People Survived, Statista, + November 18, 2020. . + McCarty, Willard. Introduction in Collaborative Research in the Digital + Humanities: A volume in honour of Harold Short on the occasion of his 65th + birthday, September 2010, ed. Marilyn Deegan and Willard + McCarty. London: Ashgate + (2012). + Melville, Herman, Moby + Dick. (1851). + Mendès-France, Pierre, + Œuvres complètes, 1984-1985. + 《孟子》〈三十三〉。 + + Miller, Henry. Death of a Salesman in + Atkinson, Brooks, + New Voices in the American Theatre, New York: + Modern Library, 1955, p.113. + + Milne, A. A. + The House at Pooh Corner. London: + Methuen & Co., 1928, p. + 83. + + Milton, John. Paradise Lost: A poem in X books + (1667), I, 1-10. + Milton, John. Poems of Mr John Milton, both + English and Latin... (1645). + Molière, L'École des + femmes, 1663. + Molière, Le Médecin + malgré lui, 1667. + Molière, Le Médecin + volant, 1673. + Montaigne, Michel de, + Essais, 1592. + Montesquieu, Charles-Louis de Secondat, + baron de la Brède et de, Lettres persanes, + 1721. + Montherlant, Henry de , + Pitié pour les femmes, 1936. + + Moore, George. Autograph manuscript of Memoirs of my dead + life, Pierpont Morgan MA 3421; in + + Moore, Thomas. Autograph manuscript of the second version of Lalla + Rookh, Pierpont Morgan MA 310; in 23. + + Moreland, Floyd L. and Rita M. Fleischer. Latin: An + Intensive Course, (1977) p.53. + + Des Minnesangs Frühling, Moser, Hugo, Helmut + Tervooren eds. 36., neugestaltete und erweiterte Auflage + I Texte, Stuttgart: S. + Hirzel Verlag, 1977. + Mošin, Vladimir A. Anchor Watermarks. + Amsterdam: Paper Publications Society (Labarre Foundation), 1973. + Monumenta Chartæ Papyraceæ Historiam Illustrantia; v. 13. + Mréjen, Valérie, Eau + sauvage, 2004. + + Zuigan calls himself "Master". Mumon Ekai. (In + The Gateless Gate, Case 12.) + Mustafa Siddik Altinakar, + René Walther (éds.), Hydraulique fluviale. Tome 16, Écoulement et + phénomènes de transport dans les canaux à géométrie simple , + 2008. + Mégnin, Michel (éd.), Tunis + 1900 Lehnert & Landrock photographes,2005. + + Nabokov, Vladimir + Pnin (1953) , p.14 + + + The New Penguin English Dictionary. London: + Penguin Books (1986). + + Derived from + New Zealand Parliament, Legislative Council. Nga Korero Paramete: 1881-1885 + (New Zealand Electronic Text Collection). 2008 + Wellington, New Zealand. + . + + + Njal's saga. tr. Magnus Magnusson and Hermann + Palsson. Penguin. (1960), chapter + 12, p.60. + + O'Casey, Sean. Time to go (1951). + Ollagnier, Jeanne, + Main, 2008. + Herodotus. On Libya, from the + Histories. + + [Letter of Capt. E. Hopkins. Providence, 10 Sep 1764] + + "[I am a curse]" in Original Manuscript Drafts for the Song of + Myself, Collection MSS3829, part of the Papers of Walt Whitman, Clifton Waller + Barrett Library of American Literature, Albert and Shirley Small Special Collections + Library, University of Virginia. + Ormesson, Jean d', La Douane de mer, 1993. + + Orwell, George. Nineteen-Eighty-Four. + London: Gollancz (1949). + + 大隅亜希子. 1996. 律令制下における権衡普及の実態: + 海産物の貢納単位を中心として. 史論 + 49. pp. 22–44. . + + Owen, Wilfred. Dulce et decorum est, from autograph + manuscript in the English Faculty Library, Oxford University. + + Owenson, Sydney. The Wild Irish Girl. Ed. + Kathryn Kirkpatrick. Oxford: Oxford + University Press, 1999, p. 17. + + + + 擺夷文經，中央研究院歷史語言研究所 。 + Pascal, Blaise, Le Mémorial, in Pensées,1670. + + Payne, J. + Report on the compatibility of J P French's spoken corpus transcription + conventions with the TEI guidelines for transcription of spoken texts, Working Paper, Dec 1992, NERC WP8/WP4 122. + + Peacock, Thomas Love. Gryll Grange + (1861), chapter 1. + Pennac, Daniel , + La Petite marchande de prose, 1978. + Perec, Georges, Espèces + d'espaces, 1974. + Perec, Georges, La Vie + mode d'emploi : romans, 1978. + Perec, Georges , Les + Choses, 1965. + Partial family tree for Bertrand Russell + based on an example in Pereira, Fernando C.N. and Stuart M. + Shieber, Prolog and Natural Language Analysis, + Stanford: Center for the Study of Language and + Information. (1987), p.22. + Pernoud, Régine, La + Femme au temps des Cathédrales, 1982. + Perreault, Simon, vCard Format Specification + Internet Engineering Task Force (IETF) (2011). + . + + Petit Larousse en Couleurs. Paris: + Larousse, (1990). + + Philipott, Thomas + Poems. (1646). + + Pinsky, Robert. Essays on Psychiatrists in Sadness and Happiness (1975). + Pix, Mary. The False Friend + (1699). + Plautus, Titus Macchius. Asinaria, or the + Comedy of Asses. Edited and translated by Wolfgang de Melo. Loeb + Classical Library 60. Cambridge, MA: Harvard University + Press (2011). + Plautus, Titus Macchius. Menaechmi. + Polac, Michel, Un + fils unique : script, l'Avant-scène cinéma, n° + 99, janvier. 1970. + + Pope, Alexander. The Rape of the Lock + (1714) III.7. + Pope, Alexander. An Essay on + Criticism (1711). + Pope, Alexander. Dunciad Variorum + (1729), III.284. + From letter 'JK' found in Poulson's Daily + Advertiser, + 8 Oct 1835. + Proust, Marcel, A la + recherche du temps perdu : Du côté de chez Swann, 1913. + Queneau, Raymond. Exercices de + style. Paris: Gallimard, + (1947), p. 192. + + + + 瓊瑤，《還珠格格》。 + Queneau, Raymond , + Journaux, 1914-1965. + + + + Rabelais, François. + Gargantua Lyon, 1542 + Rabelais, François + Tiers livre des faictz et dictz Heroïques du noble Pantagruel... + (1546), adapted from the website at + Renard, Jules, + Journal : 1887-1910, 1910. + Reference from the bibliography in Reps, Thomas + William and Teitelbaum, Tim eds. The + Synthesizer Generator: A system for constructing language-based editors, + New York and Berlin: + Springer-Verlag, 1989, p.304. + 日本法隆寺貝葉心經 (Wikipedia Sept 2008). + Richardson, Samuel. Clarissa; + or the History of a Young Lady (1748), 2 Letter XIV. + + Robert, Paul. Le Petit Robert. Paris: + Dictionnaires Le Robert (1967). + Rohmer, Eric, Ma nuit chez Maud : script, l'Avant-scène cinéma, + n°98, 2001. + Romains, Jules, + Knock, 1923. + Rostand, Edmond, Cyrano de + Bergerac, 1898. + Roubaud, Jacques, La + Boucle, 1993. + Rowling, J. K. + The Sorting Hat. In Harry Potter and the + Sorcerer's Stone, New York: Scholastic, Inc. (1999), chapter + 7, p. 121. + + + + + The Saga of the Volsungs: the Norse epic of Sigurd the Dragon + Slayer. trans. Jesse L. Byock. University of + California Press (1990). + Le Sanctoral du lectionnaire de + l'office dominicain (ms. Rome, Sainte-Sabine XIV L 1, f.142r et 189r-230v, Ecclesiasticum + officium secundum ordinem fratrum praedicatorum), édition électronique par + l'Ecole nationale des chartes, d'après l'édition d'Anne-Élisabeth + Urfels-Capot (Paris : Ecole nationale des chartes, 2007). + + 崎山理. 1985 + インドネシア語. 講座日本語学 + 11. 外国語との対照II. + 東京:明治書院 + 61-80 + + 三毛，〈沙漠中的飯店〉，《撒哈拉的故事》。 + 《三家詩鈔》，華培昌，藏於國家圖書館。 + Sapir, Edward. Language: an + introduction to the study of speech, New York: + Harcourt, Brace and World, 1921, p.79. + Shakespeare William, + Richard III, 1597. + Shakespeare, William. Henry V + In Mr. William Shakespeares Comedies, Histories, & Tragedies, + London: Jaggard and Blount, + 1623. + Shakespeare, William. Henry V + In The Works of Shakespeare in seven volumes, ed. Lewis + Theobald, London: Bettesworth, Hitch, Tonson et + al, (1733). + Shakespeare, William. Antony and + Cleopatra, IV.4, 14-21. + Shakespeare, William. Merchant of + Venice, I.ii, speech 5 (Portia). + Shakespeare, William. Macbeth, Act V, Scene 1. + Shakespeare, William. Antony + and Cleopatra (1623), V. + ii. + Shakespeare, William. Hamlet In Stanley Wells and Gary Taylor eds. + The Complete Works, Oxford: Clarendon + Press, 1986, I.i. + Shakespeare, William. Hamlet, London: Valentine Simmes. + (1603), I.i. + Shakespeare, William. The Tempest + In Mr. William Shakespeares Comedies, Histories, & + Tragedies, London: Jaggard and Blount, + (1623). + Shakespeare, William. Twelfth Night, or + What you Will In Mr. William Shakespeares Comedies, Histories, + & Tragedies, London: Jaggard and + Blount, (1623). + Shakespeare, William, The + Sonnets (1609), 18. + Shakespeare, William, The + Sonnets (1609), 130. + 莎士比亞，《終成眷屬 》。 + 莎士比亞，《馬克白》。 + Sharing Ancient Wisdoms, 2013, + available: . + Shaw, George Bernard. Heartbreak + House: a fantasia in the Russian manner on English themes (1919). + Shaw, George Bernard. Pygmalion, 1913. + Shields, David. Dead + Languages, HarperCollins Canada/Perennial + Rack, rpt. 1990, p.10. + Sinclair, John ed. Collins + COBUILD English Language Dictionary. London and + Glasgow: Collins, (1987), + p. 337 s.v. croissant. + 京劇《四郎探母》，1947年梅蘭芳演出。 + Smith, Adam. An Inquiry into the + Nature and Causes of the Wealth of Nations, London. + (1776), index to vol. 1. + + Smith, Sydney. Autograph letter. In Pierpont Morgan library; + 11. + + Smith, William. A New Classical Dictionary of Greek and + Roman Biography, Mythology, and Geography, Partly Based Upon the Dictionary of Greek and + Roman Biography and Mythology, New York: Harper + & Brothers, Publishers, 1860, 1026. + + Southey, Robert. Autograph manuscript of The Life of Cowper. + In Pierpont Morgan MA 412 ( 15). + Soyinka, Akinwande Oluwole Wole. Madmen and Specialists, London: + Methuen (1971). + + Spenser, Edmund. The Faerie Queene: Disposed into twelue + bookes, Fashioning XII. Morall vertues. (1596). + + Sterne, Laurence. The Life and Opinions of Tristram + Shandy, Gentleman. (1760). + + Stow, John A survey of the cities of London and Westminster: + containing the original, antiquity, increase, modern estate and government of those + cities. Written at first in the year MDXCVIII. By John Stow, citizen and native of London. + ... Now lastly, corrected, improved, and very much enlarged: ... by John Strype, ... In + six books. ... (London c.1525 - London 1605). + Sudetic, Chuck Serbs Tighten Grip On Eastern + Bosnia. New York Times, + April 20, 1992. + + SUEtheTrex, Twitter biography. . Accessed March 25th, + 2020. + Sutherland, L.S. and L.G. + Mitchell eds. The Eighteenth century, The + History of the University of Oxford V + , p.178. + 蘇童，《妻妾成群》。 + 蘇軾，《定風波》。 + + Swift, Jonathan. Travels into Several Remote Nations of + the World, in Four Parts. By Lemuel Gulliver... (1735). + Swift, Jonathan. Law is a bottomless pit, or + the history of John Bull (1712). + + Swinburne, Algernon Charles. Poems and Ballads (First + Series). London: Chatto & Windus. + (1904). + Swinnerton, Frank Arthur. The + Georgian Literary Scene 1910-1935, 1938, London: + J. M. Dent, p. 195. + + + + + 台灣，《結婚入盟誓》，1997年5月。 + 台灣區三碼與三加二碼郵遞區號 + 《台灣叢書》，伊能嘉矩著，藏於國立台灣大學圖書館。(http://catalog.ndap.org.tw/?URN=2155366 (Aug 2008)). + 唐．白居易．琵琶行 + + Taylor, John + The Cold Tearme or, The Frozen age, Or, The Metamorphosis of the Riuer of + Thames. London, 1621. [STC (2nd ed.) 23910]. + + TEI Consortium + Call for Papers - TEI 2022 Newcastle, 2022. + + The Castle of the Fly, in Russian Fairy Tales, + translated by Norbert Guterman from the collections of Aleksandr Afanas'ev, illustrations by + Alexander Alexeieff, folkloristic commentary by Roman Jakobson (New York: Pantheon Books, + 1947, rpt. [n.d.]), p. 25. + The Daily Telegraph, 21 Dec + 1992. + The Guardian, + 26 Oct 1992, p. 2 + The Guardian, + 21 Dec 1992, p. 2. + The Holy Bible, conteyning the Old Testament and the new... + appointed to be read in Churches. (1611), Genesis + 1:1. + The Independent, + 26 Oct 1775, headline. + Thurber, James. The 13 + Clocks (1950). + Tolkien, J. R. R. + The Monsters and the Critics. London: + George Allen & Unwin (1983). + + Townsend, Sue. The growing pains of Adrian Mole + (1984), p.43. + + Trollope, Anthony. An Autobiography + (1883). + + Trollope, Anthony. North America + (1862). + Truffaut, François et + Gruault, Jean, Les deux Anglaises et le continent : + script, l'Avant-scène cinéma, n° 121, + nov. 1971. + Tufte, Edward R., Envisioning + Information, Cheshire: Graphics Press. + (1990). + + + Ukraine Relief Fund + UBS + . + + United States Code Title 17, Section 107, found at . + + United States District Court for the Middle District of Pennsylvania. + Kitzmiller v. Dover Area School District et al.: 2005. + 04cv2688, p. 33. Available from and transcribed at . + + + + Valéry, Paul, Monsieur + Teste, 1929. + + Vergil (Publius Vergilius Naso). Aeneid, + I.1. + Verne, Jules, Cinq + semaines en ballon, 1863. + Verne, Jules, La + Chasse au météore, 1908. + Verne, Jules, Vingt + mille lieues sous les mers, 1870. + + Vinge, Vernor + Across realtime + ch 10 (1986). + Viton de Saint-Allais, Nicolas + , Dictionnaire encyclopédique de la noblesse de France, + 1816. + + Vóluspá recto of folio 5 of the unique manuscript of the Elder Edda. Codex + Regius, ed. L. F. A. Wimmer and F. Jónsson (Copenhagen 1891). + + + + + Wanklyn, M.D.G. et al. Gloucester Port Books, 1575-1765. + Available from . + + Wanton, Joseph. Unpublished letter to Nicholas Brown and Co, + 1761 + Brown University Steering Committee on Slavery and Justice: Repository of + Historical Documents. (). + + Warriner, John E. + English Composition and Grammar (1988), p.280. + + Webster's Seventh Collegiate Dictionary. Springfield, Mass. + G. & C. Merriam Co. (1975). + 魏飴，《小說鑑賞入門》，台北：萬卷樓，1999。 + Weil, Simone, Lettres à Antonio Atarès, in Oeuvres + complètes1988-. + + Williams, Nigel. The Wimbledon Poisoner + (1990), p. 204. + Winock, Michel, + Jeanne et les siens : récit, 2003. + + Wölfflin, Heinrich, trans. Hottinger, Marie + Donald Mackie (1932). Principles of art history: the problem + of the development of style in later art.. Originally published as Kunstgeschichtliche Grundbegriffe (1915). + + Woolf, Virginia. Mrs Dalloway (1925), + p.64, p.65. + + Wordsworth, William. Scorn not the sonnet in + Poetical Works (1827). + + Wordsworth, William. The Prelude (1850). + + Wrenn C. L. ed. Beowulf: with the Finnesburg + fragment, London: Harrap + (1953). + + 吳承恩，《西遊記》。 + + + Wycherley, William. The Country Wife + (1675). + + + 夏宇，〈甜蜜的復仇〉，《備忘錄》。 + 蕭紅，《呼蘭河傳》。 + + + + 幼莘貢俚賀曉濤之新婚賀詞 + 余秋雨 + 元曲。馬致遠，《天淨沙：秋思》。 + + + + 張錯， 《西洋文學術與手冊》，台北：書林，2005。頁201。 + + 珍．奧斯丁，《傲慢與偏見》。 + + 中國青年守則 + 中國學位論文全文數據庫 + 周慧玲，《表演中國：女明星表演文化視覺政治1910-1945》，2004。 + 朱自清， 《憶》跋。 + + Zimman, Lal. Lal Zimman + , accessed February 1, + 2021. + + Zupko, Ronald Edward + British Weights & Measures: A History from Antiquity to the Seventeenth + Century. Madison: University of Wisconsin + Press, 141-151. + + + + No source, made up for these Guidelines. + Example is copied from the source of these + Guidelines. + Undetermined. + + + +
+
+ Works Cited Elsewhere in the Text of these Guidelines + + + + + Knuth + Donald E. + + Literate Programming + CSLI Lecture Notes 27 + 0-937073-80-6 + + Stanford, California + Center for the Study of Language and Information + 1992 + + + + + + + Mazzolini + Renato + G. + + Colonialism and the Emergence of Racial Theories + + + + Reproduction: Antiquity to the Present Day + + Nick + Hopwood + + + Rebecca + Flemming + + + Lauren + Kassell + + + Cambridge + Cambridge University Press + 2018 + + 361-374 + + + + + + Rubin + Gayle + + The Traffic in Women: Notes on the <q>Political Economy</q> of Sex + + + + Toward an Anthropology of Women + + Rayna + R. + Reiter + + + New York + Monthly Review Press + 1975 + + 157–210, 165 + + + + + + + A. G. + Petty + + English literary hands from Chaucer to Dryden + + London + Edward Arnold + 1977 + + 22–25 + + + + + + Lou + Burnard + + Report of Workshop on Text Encoding Guidelines + + + Literary & Linguistic Computing + + 3 + 1988 + + + + + + + Lou + Burnard + + + C. + Michael + Sperberg-McQueen + + The Design of the TEI Encoding Scheme + 10.1007/BF01830314 + + + Computers and the Humanities + + 29 + 1 + 1995 + 17–39 + + + Reprinted in , pp. 17-40 + + + + + Lou + Burnard + + + Sebastian + Rahtz + + RelaxNG with Son of ODD + + + + Proceedings of Extreme Markup Languages 2004 + + 2004 + + + + + + + M. + B. + Parkes + + English Cursive Book Hands 1250–1500 + + Oxford + Clarendon Press + 1969 + + + + + + British Literary Manuscripts. Series 2: from 1800 to 1914 + + Klinkenborg + Verlyn + + + Cahoon + Herbert + + + New York + Pierpont Morgan Library + 1981 + + + + + + + Paul + Grosso + + + Eve + Maler + + + Jonathan + Marsh + + + Norman + Walsh + + XPointer Framework + + + W3C + 25 March 2003 + + + + + + + Paul + Grosso + + + Eve + Maler + + + Jonathan + Marsh + + + Norman + Walsh + + XPointer element() Scheme + + + W3C + 25 March 2003 + + + + + + XHTML™ 1.0 The Extensible HyperText Markup Language (Second + Edition) + + + W3C + 26 January 2000 + + + + + + + Dave + Ragget + + + Arnaud + Le Hors + + + Ian + Jacobs + + HTML 4.01 Specification + + + W3C + 24 December 1999 + + + + + + + David + Carlisle + + + Patrick + Ion + + + Robert + Miner + + + Nico + Poppelier + + Mathematical Markup Language (MathML) Version 2.0 (Second + edition) + + + W3C + 21 October 2003 + + + + + + + Paul V. + Biron + + + Ashok + Malhotra + + XML Schema Part 2: Datatypes Second Edition + + + W3C + 28 October 2004 + + + + + + + Anders + Berglund + + Extensible Stylesheet Language (XSL) Version 1.1 + + + W3C + 5 December 2006 + + + + + + + James + Clark + + XSL Transformations (XSLT) Version 1.0 + + + W3C + 16 November 1999 + + + + + + + Michael + Kay + + XSL Transformations (XSLT) Version 2.0 + + + W3C + 23 January 2007 + + + + + + + Michael + Kay + + XSL Transformations (XSLT) Version 3.0 + + + W3C + 8 June 2017 + + + + + + + Tim + Bray + + + Jean + Paoli + + + C. M. + Sperberg-McQueen + + + Eve + Maler + + + François + Yergau + + Extensible Markup Language (XML) Version 1.0 (Fourth edition) + + + W3C + 16 August 2006 + + + + + + + Bert + Bos + + + Tantek + Çelik + + + Ian + Hickson + + + Håkon Wium + Lie + + Cascading Style Sheets Level 2 Revision 1 + + + W3C + 7 June 2011 + + + + + + + Håkon Wium + Lie + + + Bert + Bos + + Cascading Style Sheets, Level 1 + + + W3C + 11 January 1999 + + + + + + + fantasai + + + Koji + Ishi + + CSS Writing Modes Level 3 (W3C Candidate Recommendation) + + + W3C + 15 December 2015 + + + + + + + Simon + Fraser + + + Dean + Jackson + + + Edward + O'Connor + + + Dirk + Schulze + + CSS Transforms Module Level 1 (W3C Working Draft) + + + W3C + 26 November 2013 + + + + + + + Frank + Manola + + + Eric + Miller + + + Brian + McBride + + RDF 1.1 Primer + + + W3C + 24 June 2014 + + + + + + + Jonathan + Marsh + + + Richard + Tobin + + XML Base (Second Edition) + + + W3C + 28 January 2009 + + + + + + + James + Clark + + + Steve + DeRose + + XML Path Language (XPath) Version 1.0 + + + W3C + 16 November 1999 + + + + + + + Anders + Berglund + + + Scot + Boag + + + Mary F. + Fernández + + + Michael + Kay + + + Jonathan + Robie + + + Jérôme + Siméon + + XML Path Language (XPath) 2.0 + + + W3C + 23 January 2007 + + + + + + + Jonathan + Robie + + + Don + Chamberlin + + + Michael + Dyck + + + Jon + Snelson + + XML Path Language (XPath) 3.0 + + + W3C + 8 April 2014 + + + + + + + Jonathan + Robie + + + Michael + Dyck + + + Josh + Spiegel + + XML Path Language (XPath) 3.1 + + + W3C + 21 March 2017 + + + + + + + Tim + Bray + + + Dave + Hollander + + + Andrew + Laymon + + + Richard + Tobin + + Namespaces in XML 1.0 (second edition) + + + W3C + 16 August 2006 + + + + + + + Eric + van der Vlist + + RELAX NG + + + O'Reilly + 2004 + + + + + + + Renear + A. + + + Mylonas + E. + + + Durand + D. + + Refining our notion of what text really is: the problem of overlapping + hierarchies + + + + Nancy + Ide + + + Susan + Hockey + + Research in Humanities Computing + + Oxford University Press + 1996 + + + + + + + Robert + Sanderson + + + Paolo + Ciccarese + + + Benjamin + Young + + Web Annotation Data Model + + + W3C + 23 February 2017 + + + + + + + Robert + Sanderson + + + Paolo + Ciccarese + + + Benjamin + Young + + Web Annotation Vocabulary + + + W3C + 23 February 2017 + + + + + + The Unicode Standard, Version 5.0 + + Unicode Consortium + + Addison-Wesley Professional + 2006 + + + + + + + Addison + Phillips + + + Mark + Davis + + Tags for Identifying Languages + RFC 4646 + + 2006 + IETF + + + + + + + Addison + Phillips + + + Mark + Davis + + Matching of Language Tags + RFC 4647 + + 2006 + IETF + + + + + + + Mark + Davis + + + Ken + Whistler + + + Asmus + Freytag + + Unicode Character Database + + + Unicode Consortium + 2006 + + + + + + + + Fernando + C. + N. + Pereira + + Grammars and logics of partial information + + Menlo Park, CA + SRI International + 1987 + + + + SRI International Technical Note + 420 + + + + + + Bob + Carpenter + + The logic of typed feature structures + + Cambridge + Cambridge University Press + 1992 + + + + Cambridge Tracts in Theoretical Computer Science + 32 + + + + + + Stuart + Shieber + + An Introduction to Unification-based Approaches to Grammar + CSLI Lecture Notes 4 + + Center for the Study of Language and Information + Palo Alto, CA + 1986 + + + + + + Anglo-American Cataloguing Rules + Second Edition, 2002 revision, 2005 update + + Chicago + American Library Association + Ottawa + Canadian Library Association + 2002–2005 + + + + + + + + John + Burrows + + Computation into Criticism: A Study of Jane Austen's Novel and an + Experiment in Method + + Oxford + Clarendon Press + 1987 + + + + + + + + Klaus + Mattheier + + + Ulrich + Ammon + + + Peter + Trudgill + + Sociolinguistics + Soziolinguistik + An international handbook of the science of + language and society + Ein internationales Handbuch zur Wissenschaft + von Sprache und Gesellschaft + + Berlin + New York + De Gruyter + 1988 + I + 271 and 274 + + + + + + + J. + A. + Edwards + + + M. + D. + Lampert + + Talking Language: Transcription and Coding of Spoken Discourse + + Hillsdale, N.J. + Lawrence Erlbaum Associates + 1993 + + + + + + + Asmus + Freytag + + The Unicode Character Property Model + Unicode Technical Report #23 + + + 2006 + + + + + + + Mark + Davis + + + Aharon + Lanin + + + Andrew + Glass + + Unicode Bidirectional Algorithm + Unicode Standard Annex #9 + + + 2017-05-04 + + r. 37 + + + + + + + Stig + Johansson + + Encoding a Corpus in Machine-Readable Form + + + + + Sue + Atkins + + + Antonio + Zampolli + + Computational Approaches to the Lexicon: An Overview + + Oxford + Oxford University Press + 1994 + + + + + + + + Stig + Johansson + + + Lou + Burnard + + + Jane + Edwards + + + And + Rosta + + Working Paper on Spoken Texts + TEI document TEI AI2 W1 + + 1991 + + + + + + + + Brian + MacWhinney + + CHAT Manual + + Pittsburgh + Dept of Psychology, Carnegie-Mellon University + 1988 + 87ff + + + + + + + Bengt + Loman + + + Nils + Jørgensen + + Manual for analys och beskrivning av makrosyntagmer + + Lund + Studentlitteratur + 1971 + + + + + + + Robert + A. + Amsler + + + Frank + W. + Tompa + + An SGML-Based Standard for English Monolingual Dictionaries + + + Information in Text + Fourth Annual Conference of the U[niversity of] W[aterloo] + Centre for the New Oxford English Dictionary + Fourth Annual Conference of the U[niversity of] W[aterloo] Centre for the New + Oxford English Dictionary, October 26-28, 1988, Waterloo, Canada + + Waterloo, Canada + October 1988 + 61-79 + + + + + + + + N. + Calzolari + + + C. + Peters + + + A. + Roventini + + Computational Model of the Dictionary Entry: Preliminary + Report + Acquilex: Esprit Basic Research Action No. 3030, Six-Month + Deliverable + + Pisa + April 1990 + + + + + + + + John + Fought + + + Carol + Van Ess-Dykema + + Toward an SGML Document Type Definition for Bilingual + Dictionaries + TEI working paper TEI AIW20 + + available from the TEI. + + + + + + + + Nancy + Ide + + + Jean + Veronis + + Encoding Print Dictionaries + + + Computers and the Humanities + + 29 + 1995 + 167-195 + + + + + + + Nancy + Ide + + + Jacques + Le Maitre + + + Jean + Veronis + + Outline of a Model for Lexical Databases + + + Information Processing and Management + + 29 + 2 + 1993 + 159-186 + + + + + + + Nancy + Ide + + + Jean + Veronis + + + Susan + Warwick-Amstrong + + + Nicoletta + Calzolari + + Principles for Encoding machine readable dictionaries + + + Proceedings of the Fifth EURALEX International Congress, + EURALEX'92 + Fifth EURALEX International Congress, EURALEX'92, University of Tampere, + Finland + + 1992 + + + + + + + + The + DANLEX Group + + Descriptive tools for electronic processing of dictionary data + + + Lexicographica, Series Maior + + Tübingen + Niemeyer + 1987 + + + + + + + + Agnès + Tutin + + + Jean + Veronis + + Electronic dictionary encoding: customizing the TEI Guidelines + + + Proceedings of the Eighth Euralex International Congress + Eighth Euralex International Congress + + 1998 + + + + + + + N. + Ide + + + A. + Kilgarriff + + + L. + Romary + + A Formal Model of Dictionary Structure and Content + + + Proceedings of Euralex 2000 + Euralex 2000 + + Stuttgart + 2000 + 113-126 + + + + + + + William + A. + Gale + + + Kenneth + W. + Church + + Program for aligning sentences in bilingual corpora + + + Computational Linguistics + + 19 + 1993 + 75-102 + + + + + + + G. + N. + Leech + + + R. + G. + Garside + + Running a Grammar Factory + + + + S. + Johansson + + + A.-B. + Stenstrøm + + English Computer Corpora: Selected Papers and Research Guide + + Berlin + de Gruyter + New York + Mouton + 1991 + pp. 15-32. + + + + + + + + I. + Marshall + + Choice of Grammatical Word Class without Global Syntactic Analysis: + Tagging Words in the LOB Corpus + + + Computers and the Humanities + + 17 + 1983 + 139-50 + + + + + + + + R. + G. + Garside + + + G. + N. + Leech + + + G. + R. + Sampson + + The Computational Analysis of English: a Corpus-Based Approach + + Oxford + Oxford University Press + 1991 + + + + + + + + Gary + Chartrand + + + Linda + Lesniak + + Graphs and Digraphs + + Menlo Park, CA + Wadsworth + 1986 + + + + + + + + R. + Jackendoff + + X-Bar Syntax: A study of phrase structure + + + Linguistic Inquiry Monograph + + 2 + 1977 + + + + + + + + M. + Kytö + + + M. + Rissanen + + The Helsinki Corpus of English Texts + + + + M. + Kytö + + + O. + Ihalainen + + + M. + Rissanen + + Corpus Linguistics: hard and soft + + Amsterdam + Rodopi + 1988 + + + + + + + + Steven + DeRose + + Markup overlap: a review and a horse + + + + Proceedings of Extreme Markup Languages 2004 + + 2004 + + + + + + + Andreas + Witt + + Multiple Informationsstrukturierung mit + Auszeichnungssprachen. XML-basierte Methoden und deren Nutzen für die + Sprachtechnologie + + 2002 + + + Ph D thesis, Bielefeld University + See also + + + + + + + Mirco + Hilbert + + + Oliver + Schonefeld + + + Andreas + Witt + + Making CONCUR work + + + + Proceedings of Extreme Markup Languages 2005 + + 2005 + + + + + + + + Alex + Dekhtyar + + + Ionut + E. + Iacob + + A framework for management of concurrent XML markup + + + + + 2005 + + + + + + + + H. + V. + Jagadish + + + Laks + V. + S. + Lakshmanan + + + Monica + Scannapieco + + + Divesh + Srivastava + + + Nuwee + Wiwatwattana + + Colorful XML: one hierarchy isn't enough + + + + + + + 2004 + + + + + + + + Noureddine + Chatti + + + Suha + Kaouk + + + Sylvie + Calabretto + + + Jean + Marie + Pinon + + MultiX: an XML based formalism to encode multistructured + documents + + + + + + Proceedings of Extreme Markup Languages 2007 + + 2007 + + + + + + + + Patrick + Durusau + + + Matthew + Brook + O'Donnell + + Coming down from the trees: next step in the evolution of markup? + + + Proceedings of Extreme Markup Languages 2002 + + 2002 + + + + + + + + Jeni + Tennison + + + Wendell + Piez + + The layered markup and annotation language + + + Proceedings of Extreme Markup Languages Conference + + 2002 + + + + + + + + Claus + Huitfeldt + + + C. + Michael + Sperberg-McQueen + + TexMECS: An experimental markup meta-language for complex + documents + + + 2001 + + + + + + + D. Terence + Langendoen + + + Gary F. + Simons + + A rationale for the TEI recommendations for feature-structure + markup, + + + Computers and the Humanities + + 29 + 1995 + 167-195 + + + + + + British Standards Institute + BS 5605:1990: Recommendations for Citing and Referencing Published + Material + + 1990 + + + + + + British Standards Institute + BS 6371:1983: Recommendations for Citation of Unpublished + Documents + + 1983 + + + + + + Deutsches Institut für Normung + DIN 1505-2: Titelangaben von Dokumenten; Zitierregeln + + 1984 + + + + + + Die Deutsche Bibliothek + Regeln für die alphabetische Katalogisierung in wissenschaftlichen + Bibliotheken RAK-WB + + 2006 + + + + + + International Organization for Standardization + ISO 690:1987: Information and documentation – Bibliographic references – Content, + form and structure + + 1987 + + + + + + International Organization for Standardization + ISO 8601:2004: Data elements and interchange formats — Information interchange — + Representation of dates and times + + 2004 + + + + + + International Organization for Standardization + ISO 12620:2009: Terminology and other language and content resources – + Specification of data categories and management of a Data Category Registry for language + resources + + + 2009 + + + + + + International Organization for Standardization + ISO 19136:2007: Geographic information — Geography Markup Language (GML) + + 2006 + + + + + + International Organization for Standardization + ISO/IEC 19757-3:2006: Information technology — Document Schema Definition Languages + (DSDL) – Part 3: Rule-based validation – Schematron + + 2006 + + + + + + Istituto Centrale per il Catalogo Unico + Regole italiane di catalogazione per autori + + 1979 + + + + + + National Information Standards Organization + ANSI/NISO Z39.29 – 2005 (R2010) Bibliographic References + + 2010 + + + + + + ISBD: International Standard Bibliographic Description + + Berlin, München + De Gruyter Saur + 2011 + + + + IFLA Series on Bibliographic Control + 44 + + + + + Федеральное агентство по техническому регулированию и метрологии + (РОССТАНДАРТ) + ГОСТ Р 7.0.5-2008: Система стандартов по информации, библиотечному и + издательскому делу. Библиографическая ссылка. Общие требования и правила + составления + + 2008 + + + + + + Федеральное агентство по техническому регулированию и метрологии + (РОССТАНДАРТ) + ГОСТ 7.1—2003. Система стандартов по информации, библиотечному и + издательскому делу. Библиографическая запись. Библоиграфическое описание. Общие + требования и правила составления + + 2003 + + + + + + DCMI Usage Board + Dublin Core™ Metadata Element Set, Version 1.1: Reference Description + + + 2012-06-14 + + + + +
+
+ Reading List +

The following lists of readings in markup theory and the TEI derive from work + originally prepared by Susan Schreibman and Kevin Hawkins for the TEI Education Special + Interest Group, recoded in TEI P5 by Sabine Krott and Eva Radermacher. They should be regarded + only as a snapshot of work in progress, to which further contributions and corrections are + welcomed (see further ).

+
+ Theory of Markup and XML + + + + + C. + Michael + Sperberg-McQueen + + + Claus + Huitfeld + + Concurrent Document Hierarchies in MECS and SGML + + + Literary and Linguistic Computing + + 14 + 1 + 1999 + 29-42 + + + + + + + C. + Michael + Sperberg-McQueen + + Rabbit/duck grammars: a validation method for overlapping + structures + + + + Proceedings of Extreme Markup Languages 2006 + + 2006 + + + + + + + David + T. + Barnard + + + Lou + Burnard + + + Jean-Pierre + Gaspart + + + Lynne + A. + Price + + + C. + Michael + Sperberg-McQueen + + + Giovanni + Battista + Varile + + Hierarchical Encoding of Text: Technical Problems and SGML + Solutions + 10.1007/BF01830617 + + + + Computers and the Humanities + + 29 + 3 + 1995 + 211–231 + + + + + + + David + T. + Barnard + + + Lou + Burnard + + + C. + Michael + Sperberg-McQueen + + Lessons learned from using SGML in the Text Encoding Initiative + 10.1016/0920-5489(95)00035-6 + + + Computer Standards & Interfaces + + 18 + 1 + 1996 + 3–10 + + + + + + + Lou + Burnard + + What is SGML and how does it help? + + + + + Daniel + Greenstein + + Modelling Historical Data: Towards a Standard for Encoding and + Exchanging Machine-readable Texts + + St Katherinen + Max-Planck-Institut für Geschichte In Kommission bei Scripta Mercaturae + Verlag + 1991 + 81–91 + + + + Halbgraue Reihe zur Historischen Fachinformatik + + Herausg. von + + Manfred + Thaller + + + serie A + 11 + + + Revised version published as + + + + + Lou + Burnard + + SGML on the Web: Too Little Too Soon or Too Much Too Late? + + + + Computers & Texts + + 15 + 1995 + 12–15 + + + + + + + + Lou + Burnard + + What is SGML and How Does It Help? + 10.1007/BF01830315 + + + + Computers and the Humanities + + 29 + 1 + 1995 + 41–50 + + + Reprinted in , pp. 41-50 + + + + + Nancy + Ide + + + Jean + Veronis + + The Text Encoding Initiative: Background and Contexts + + Dordrecht + Boston + Kluwer Academic Publisher + 1995 + + + + + + + Lou + Burnard + + Is Humanities Computing an Academic Discipline? or, Why Humanities + Computing Matters + + + + 1999 + + + + Presented at an interdisciplinary seminar at the Institute for Advanced Technology + in the Humanities, University of Virginia, November 1999. + + + + + Lou + Burnard + + Using SGML for Linguistic Analysis: The Case of the BNC + + + + Markup Languages Theory and Practice + + 2 + 1999 + Cambridge, Massachusettes + MIT Press + 31–51 + + + Also published in , pp. 53–72 + + + + + Stephan + Moser + + + Peter + Stahl + + + Werner + Wegstein + + + Norbert + Richard + Wolf + + Maschinelle Verarbeitung Altdeutscher Texte V (Beiträge zum Fünften + Internationalen Symposion, Würzburg, 4–6 März 1997) + + Tübingen + Niemeyer + 2001 + + + + + + + Lou + Burnard + + + Elizabeth + Lalou + + + Peter + Robinson + + Vers un Standard Européen de Description des Manuscrits: Le Projet + Master + + + Documents Numeriques + Les Documents Anciens + + 3 + 1–2 + 1999 + Paris + Hermes Science Publications + 151-169 + + + + + + + Lou + Burnard + + XML: The Dream and the Reality + + + 1999 + + + Closing plenary address at the XML Europe Conference, Granada, May 1999 + + + + + Lou + Burnard + + + Claudia + Claridge + + + Josef + Schmied + + + Rainer + Siemund + + Encoding the Lampeter Corpus + + + + DRH98: Selected Papers from Digital Resources for the + Humanities + + London + Office for Humanities Communication + 2000 + + + + + + + + Lou + Burnard + + From Two Cultures to Digital Culture: The Rise of the Digital + Demotic + + + 2000 + + + Presented at CLIP, Alicante + + Published in Italian as + + + + + + Lou + Burnard + + Dalle «Due Culture» Alla Cultura Digitale: La Nascita del Demotico + Digitale + + Translated by + + Federico + Pellizi + + + + + Il Verri + Nella Rete + + 16 + 2001 + Milano + Monogramma + 9–22 + + + + + + + Lou + Burnard + + On the Hermeneutic Implications of Text Encoding + + + + + Domenico + Fiormonte + + + Jonathan + Usher + + New Media and the Humanities: Research and Applications + + Oxford + Humanities Computing Unit + 2001 + 31–38 + + + + + + + + Lou + Burnard + + Encoding Standards for the Electronic Edition + + + + + Matija + Ogrin + + Znanstvene Izdaje in Elektronski + Medij + Scholarly Editions and the Digital + Medium + + Ljubljana + Studia Litteraria ZRC ZAZU + 2005 + 12–67 + + + + + + + + Lou + Burnard + + Metadata for corpus work + + + + + Martin + Wynne + + Developing Linguistic Corpora: A Guide to Good Practice + + Oxford + Oxbow Books + 2005 + 30–46 + + + + + + + + Lou + Burnard + + + Katherine + O'Brien + O'Keefe + + + John + Unsworth + + Electronic Textual Editing + + + New York + Modern Languages Association + 2006 + + + + + + + Dino + Buzzetti + + Digital Representation and the Text Model + + + + New Literary History + + 33 + 1 + 2002 + 61–88 + + + + + + + + Paul + Caton + + Markup's Current Imbalance + + + Markup Languages: Theory and Practice + + 3 + 1 + 2001 + 1–13 + + + This paper was proceeded by reports at the Joint Annual Conference of the + Association for Computers and the Humanities and the Association for Literary and + Linguistic Computing in 1999 (Charlottesville, Virginia) and Extreme Markup Languages + 2000 (Montreal, Canada) + + + + + Ruey-Shun + Chen + + + Shien-Chiang + Yu + + Developing an XML Framework for Metadata System + + + + Proceedings of the 1st International Symposium on Information and + Communication Technologies + + Dublin + 2003 + 267–272 + + + + ACM International Conference Proceeding Series + 49 + + + This paper was presented in a session entitled "Electronic Document + Technology." + + + + + James + H. + Coombs + + Information Management System for Scholars + Technical Memorandum TM 69–2 + + Providence + Brown Computer Center + 1986 + + + + + + + James + H. + Coombs + + + Allen + Renear + + + Steven + J. + DeRose + + Markup Systems and The Future of Scholarly Text Processing + 10.1145/32206.32209 + + + + + Communications of the ACM + + 30 + 11 + 1987 + 933–947 + + + Reprinted with new commentary in , pp 85–118 + + + + + George + P. + Landow + + + Paul + Delany + + The Digital Word: Text-based Computing in the Humanities + + Cambridge, MA + MIT Press + 1993 + + + + + + + Robin + Cover + + Markup Languages and (Non-) Hierarchies + + + 2005 + + + Technology report from the Cover Pages + + + + + + Steven + J. + DeRose + + Structured Information: Navigation, Access, and Control + + + 1995 + + + Paper presented at the Berkeley Finding Aid Conference, April 4–6, 1995 + + + + + + Steven + J. + DeRose + + + David + G. + Durand + + + Elli + Mylonas + + + Allen + H. + Renear + + What is Text, Really? + + + Journal of Computing in Higher Education + + 1 + 2 + 1990 + 3–26 + + + Republished () as a "classic reprint" with invited + commentary and authors' replies in the ACM/SIGDOC + + + + + Steven + J. + DeRose + + + David + G. + Durand + + + Elli + Mylonas + + + Allen + H. + Renear + + What is Text, Really? + 10.1145/264842.264843 + + + Journal of Computer Documentation + + 21 + 3 + 1997 + 1–24 + + + + + + + Charles + F. + Goldfarb + + A Generalized Approach to Document Markup + + + + Proceedings of the ACM SIGPLAN SIGOA Symposium on Text + Manipulation + + New York + ACM + 1981 + 68–73 + + + Adapted as "Annex A. Introduction to Generalized Markup" in ISO 8879 + + + + + + Tony + Graham + + Unicode: What Is It and How Do I Use It? + + + Markup Languages: Theory & Practice + + 1 + 4 + 1999 + 75 + + + + + + + Susan + Hockey + + Creating and Using Electronic Editions + + + + Richard + J. + Finneran + + The Literary Text in the Digital Age + + Ann Arbor, MI + University of Michigan Press + 1996 + 1–22 + + + + + + + Susan + Hockey + + + Allen + Renear + + + Jerome + J. + McGann + + What is Text? A Debate on the Philosophical and Epistemological Nature + of Text in the Light of Humanities Computing Research + + + 1999 + + + Panel presented at ACH/ALLC 1999 + + + + + + Susan + Hockey + + Electronic Texts in the Humanities + + New York, NY + Oxford University Press + 2000 + + + + + + + Claus + Huitfeldt + + Multi-dimensional Texts in a One-dimensional Medium + 10.1007/BF01830270 + + + Computers and the Humanities + + 28 + 4/5 + 1994 + 235–241 + + + + + + + Claus + Huitfeldt + + Toward a Machine-Readable Version of Wittgenstein's Nachlaß: Some + Editorial Problems + + + + Hans + Gerhard + Senger + + Philosophische Editionen. Erwartungen an sie — Wirkungen durch + sie + + Tübingen + Max Niemeyer Verlag + 1994 + 37–43 + + + + Beihefte zu editio + 6 + + + + + + Leslie + Lamport + + Document Production: Visual or Logical? + + + + Notices of the American Mathematical Society + + 34 + 1987 + 621–624 + + + + Republished as + + + + + Leslie + Lamport + + Document Production: Visual or Logical? + + + + TUGboat + + 9 + 1 + 1988 + 8-10 + + + + + + + + + + John + Lavagnino + + Completeness and Adequacy in Text Encoding + + + + Richard + J. + Finneran + + The Literary Text in the Digital Age + + Ann Arbor, MI + University of Michigan Press + 1996 + 63–76 + + + + + + + Charles + Lightfoot + + Generic Textual Element Identification—A Primer + + Arlington + Graphic Communications Computer Association + 1979 + + + + + + + Joshua + Lubell + + Structured Markup on the Web: A Tale of Two Sites + + + + Markup Languages: Theory & Practice + + 1 + 3 + 1999 + 7–22 + + + + + + + + Tony + McEnery + + + Lou + Burnard + + + Andrew + Wilson + + + Paul + Baker + + Validation of Linguistic Corpora + + + 1998 + + + + Report commissioned by ELRA + + + + + Jerome + McGann + + The Rationale of Hypertext + + + + Kathryn + Sutherland + + Electronic Text: Investigations in Method and Theory + + New York, NY + Clarendon Press Oxford + 1997 + 19–46 + + + + + + + Jerome + McGann + + Radiant Textuality: Literature After the World Wide Web + + New York, NY + Palgrave Macmillian + 2001 + + + + + + + Jerome + McGann + + Marking Texts of Many Dimensions + + + + + Susan + Schreibman + + + Ray + Siemens + + + John + Unsworth + + A Companion to Digital Humanities + + Oxford + Blackwell + 2004 + 198–217 + + + + + + + + Alan + Morrison + + + Michael + Popham + + + Karen + Wikander + + Creating and Documenting Electronic Texts: A Guide to Good + Practice + + + (no date) + + + + + + + + Alois + Pichler + + Advantages of a Machine-Readable Version of Wittgenstein's + Nachlaß + + + + + Kjell + S. + Johannessen + + + Tore + Nordenstam + + Culture and Value: Philosophy and the Cultural Sciences. Beiträge des + 18. Internationalen Wittgenstein Symposiums 13–20. August 1995 Kirchberg am + Wechsel + + Kirchberg am Wechsel + Die Österreichische Ludwig Wittgenstein Gesellschaft + 1995 + 770–776 + + + + + + + + + Wendell + Piez + + Beyond the 'Descriptive vs. Procedural' Distinction + + + + + B. + Tommie + Usdin + + + Steven + R. + Newcomb + + Proceedings of Extreme Markup Languages 2001: Montreal, Canada + + 2001 + + + + + + + + + Michael + Popham + + What Is Markup and Why Does It Matter + + + + Michael + Popham + + + Lorna + Hughes + + Computers and Teaching in the Humanities: Selected Papers from the + CATH94 Conference held in Glasgow University September 9th-12th 1994 + + Oxford + CTI Centre for Textual Studies + 1996 + + + + + + + Liam + Quin + + Suggestive Markup: Explicit Relationships in Descriptive and + Prescriptive DTDs + + + + + B. + Tommie + Usdin + + + Deborah + A. + Lapeyre + + SGML'96 Conference Proceedings + + Alexandria, VA + Graphic Communications Association + 1996 + 405–418 + + + + + + + + Darrell + Raymond + + + Frank + Tompa + + + Derick + Wood + + From Data Representation to Data Model: Meta-Semantic Issues in the + Evolution of SGML + + + + Computer Standards & Interfaces + + 18 + 1 + 1996 + 25–36 + + + + + + + Allen + Renear + + + David + Durand + + + Elli + Mylonas + + Refining our Notion of What Text Really Is: The Problem of Overlapping + Hierarchies + + + + + Susan + Hockey + + + Nancy + Ide + + Research in Humanities Computing 4: Selected Papers from the 1992 + ALLC/ACH Conference + + Oxford + Oxford University Press + 1996 + 263–280 + + + + + + + + Allen + Renear + + Out of Praxis: Three (Meta)Theories of Textuality + + + + Kathryn + Sutherland + + Electronic Text: Investigations in Method and Theory + + New York, NY + Clarendon Press Oxford + 1997 + 107–126 + + + + + + + Allen + Renear + + The Descriptive/Procedural Distinction is Flawed + + + Markup Languages: Theory and Practice + + 2 + 4 + 2000 + 411–420 + + + + + + + + Allen + H. + Renear + + + David + Dubin + + + C. + Michael + Sperberg-McQueen + + Towards a Semantics for XML Markup + 10.1145/585058.585081 + + + + Richard + Furuta + + + Jonathan + I. + Maletic + + + Ethan + V. + Munson + + Proceedings of the 2002 ACM Symposium on Document Engineering + + McLean, VA + Association for Computing Machinery + 2002 + 119–126 + + + + + + + Allen + H. + Renear + + + Christopher + Phillippe + + + Pat + Lawton + + + David + Dubin + + An XML Document Corresponds to Which FRBR Group 1 Entity? + + + + + + B. + Tommie + Usdin + + + Steven + R. + Newcomb + + Proceedings of Extreme Markup Languages 2003: Montreal, Canada + + 2003 + + + + + + + + + Allen + H. + Renear + + + David + Dubin + + + C. + Michael + Sperberg-McQueen + + + Claus + Huitfeldt + + XML Semantics and Digital Libraries + + + + Proceedings of the 3rd ACM/IEEE–CS Joint Conference on Digital + Libraries + + Los Alamitos, CA + IEEE Computer Society + 2003 + 303–305 + + + + + + + + Allen + H. + Renear + + Text Encoding + + + + + Susan + Schreibman + + + Ray + Siemans + + + John + Unsworth + + A Companion to Digital Humanities + + Oxford + Blackwell + 2004 + 218–239 + + + + + + + + Susanne + Salmon-Alt + + Data Structures for Etymology: Towards an Etymological Lexical + Network + + + + BULAG: revue internationale annuelle + Numéro Etymologie + + 31 + 2006 + Besançon + Presses Universitaires de Franche-Comté + + + + + + + + Susan + Schreibman + + Computer-mediated Texts and Textuality: Theory and Practice + 10.1023/A:1016178200469 + + + Computers and the Humanities + + 36 + 3 + 2002 + 283–293 + + + + + + + Susan + Schreibman + + The Text Ported + 10.1093/llc/17.1.77 + + + Literary and Linguistic Computing + + 17 + 1 + 2002 + 77–87 + + + + + + + SGML Users' Group + + A Brief History of the Development of SGML + + + 1990 + + + + + + + + Frank + M. + Shipman + III + + + Catherine + C. + Marshall + + Formality Considered Harmful: Experiences, Emerging Themes, and + Directions on the Use of Formal Representations in Interactive Systems + 10.1023/A:1008716330212 + + + + Computer-Supported Cooperative Work + + 8 + 4 + 1999 + 333–352 + + + + + + + C. + Michael + Sperberg-McQueen + + + Claus + Huitfeldt + + Concurrent document hierarchies in MECS and SGML + 10.1093/llc/14.1.29 + + + Literary and Linguistic Computing + + 14 + 1 + 1999 + 29–42 + + + + + + + C. + Michael + Sperberg-McQueen + + + Claus + Huitfeldt + + + Allen + H. + Renear + + Meaning and Interpretation in Markup + + + Markup Languages: Theory and Practice + + 2 + 3 + 2000 + 215–234 + + + + + + + C. + Michael + Sperberg-McQueen + + + David + Dubin + + + Claus + Huitfeldt + + + Allen + Renear + + Drawing Inferences on the Basis of Markup + + + + + + B. + Tommie + Usdin + + + Steven + R. + Newcomb + + Proceedings of Extreme Markup Languages 2002: Montreal, Canada + + 2002 + + + + + + + + + Suzana + Sukovic + + Beyond the Scriptorium: The Role of the Library in Text + Encoding + + + + D-Lib + + 8 + 1 + 2002 + + + + + + + + University of Nebraska — Lincoln Libraries + + A Basic Guide to Text Encoding + + + + + + 2003 + + + + + + + + John + Unsworth + + Knowledge Representation in Humanities Computing + + + 2001 + + + Lecture I in the eHumanities NEH Lecture Series on Technology & the Humanities, + Washington, DC, April 3, 2001 + + + + + + John + Unsworth + + Scholarly Primitives: What Methods Do Humanities Researchers Have in + Common, How Might Our Tools Reflect This? + + + 2000 + + + Part of a Symposium on "Humanities Computing: Formal Methods, Experimental + Practice" sponsored by King's College, London + + + + + + Fabio + Vitali + + + Luca + Bompani + + + Paolo + Ciancarini + + Hypertext Functionalities with XML + + + Markup Languages: Theory & Practice + + 2 + 4 + 2000 + 389 + + + + + + + Dennis + G. + Watson + + Brief History of Document Markup + + + 1992 + + + Circular 1086. Florida Cooperative Extension Service, Institute of Food and + Agricultural Sciences, University of Florida + + + + + + Adriaan + van der + Weel + + The Concept of Markup + + + + Digital Text and the Gutenberg Heritage + + (no date) + 3 + + + in preparation; draft only + + + + + + Christopher + Welty + + + Nancy + Ide + + Using the Right Tools: Enhancing Retrieval from Marked-up + Documents + 10.1023/A:1001800717376 + + + + Computers and the Humanities + + 33 + 1–2 + 1999 + 59–84 + + + + +
+
+ TEI + + + + + Syd + Bauman + + Keying NAMEs: the WWP Approach + + + + Brown University Women Writers Project Newsletter + + 2 + 3 + 1996 + 3–6 + 10–11 + + + + + + + Syd + Bauman + + + Julia + Flanders + + Odd Customizations + + + + Proceedings of Extreme Markup Languages 2004 + + 2004 + + + + + + + Syd + Bauman + + Tables of Contents TEI-style + + + + Lou + Burnard + + TEXT Technology: The Journal of Computer Text + Processing + Electronic Texts and the Text Encoding Initiative. A Special + Issue of TEXT Technology + + 5 + 3 + 1995 + Madison, SD + College of Liberal Arts, Dakota State University + 235–247 + + + + + + + Syd + Bauman + + + Terry + Catapano + + TEI and the Encoding of the Physical Structure of Books + 10.1023/A:1001769103586 + + + Computers and the Humanities + + 33 + 1–2 + 1999 + 113–127 + + + + + + + Syd + Bauman + + TEI HORSEing Around + + + + Proceedings of the Extreme Markup Languages 2005 + + 2005 + + + + + + + Malcolm + B. + Brown + + What is the TEI? + + + Information Technology and Libraries + + 13 + 1 + 1994 + 8 + + + + + + + Lou + Burnard + + The Text Encoding Initiative: A Progress Report + + + + Gerhard + Leitner + + New Directions in Corpus Linguistics + + Berlin + Mouton de Gruyter + 1992 + + + + + + + Lou + Burnard + + Rolling your own with the TEI + + + Information Services and Use + + 13 + 2 + 1993 + Amsterdam + IOS Press + 141–154 + + + + + + + Lou + Burnard + + The TEI: Towards an Extensible Standard for the Encoding of + Texts + + + + Seamus + Ross + + + Edward + Higgs + + Electronic Information Resources and Historians + + London + British Academy + 1994 + + + + + + + Lou + Burnard + + The Text Encoding Initiative: An Overview + + + + Geoffrey + Leech + + + Greg + Myers + + + Jenny + Thomas + + Spoken English on Computer: Transcription, Mark-up and + Application + + London + Longman + 1995 + + + + + + + Lou + Burnard + + The Text Encoding Initiative's Recommendations for the Encoding of + Language Corpora: Theory and Practice + + + 1997 + + + Prepared for a seminar on Etiquetación y extracción de información de grandes corpus + textuales within the Curso Industrias de la Lengua (14–18 de Julio de 1997). Sponsored + by the Fundacion Duques de Soria. + + + + + Lou + Burnard + + + Michael + Popham + + Putting Our Headers Together: A Report on the TEI Header Meeting 12 + September 1997 + 10.1023/A:1001710828622 + + + Computers and the Humanities + + 33 + 1-2 + 1999 + Dordrecht, Boston + Kluwer Academic Publishers + 39–47 + + + + + + An Agreement to Establish a Consortium for the Maintenance of the Text Encoding + Initiative + + + March 1999 + + + + + + + Lou + Burnard + + Text Encoding for Interchange: A New Consortium + + + 2000 + + + + + + + Fabio + Ciotti + + Il Manuale TEI Lite: Introduzione Alla Codifica Elettronica Dei Testi + Letterari + + Milano + Sylvestre Bonnard + 2005 + + + + + + + Sheau-Hwang + Chang + + The Implications of TEI + + + OCLC Systems and Services + + 17 + 3 + 2001 + 101–103 + + + + + + + Mavis + Cournane + + The Application of SGML/TEI to the Processing of Complex, Multi-lingual + Text + PhD Dissertation + + Cork, Ireland + University College Cork + 1997 + + + + + + + Digital Library Federation + + TEI and XML in Digital Libraries: Meeting June 30 and July 1, 1998, + Library of Congress, Summary/Proceedings + + + + 1998 + + + + + + + + Digital Library Federation + + TEI Text Encoding in Libraries: Guidelines for Best + Encoding Practices + Version 3.0 (October 2011) + + + 2011 + + + + + + + Timothy + J. + Finney + + Manuscript Markup + + + + Larry + W. + Hurtado + + The Freer Biblical Manuscripts: Fresh Studies of an American Treasure + Trove + + Atlanta, GA + Society of Biblical Literature + 2006 + 263-288 + + + + Text-critical studies + 6 + + + + + + Matthew + Gibson + + + Christine + Ruotolo + + Beyond the Web: TEI, the Digital Library, and the Ebook + Revolution + 10.1023/A:1021895322291 + + + Computers and the Humanities + + 37 + 1 + 2003 + 57–63 + + + + + + + Sylvain + Loiseau + + Les standards : autour d'XML et de la TEI + + + 2002 + + + + + + + + Lynn + Marko + + + Christina + Kelleher Powell + + Descriptive Metadata Strategy for TEI Headers: A University of Michigan + Library Case Study + 10.1108/10650750110402585 + + + OCLC Systems & Services + + 17 + 3 + 2001 + 117-20 + + + + + + + David + Mertz + + XML Matters: TEI — the Text Encoding Initiative + An XML Dialect for Archival and Complex Documents + + + 2003 + + + + + + + Alan + Morrison + + Delivering Electronic Texts Over the Web: The Current and Planned + Practices of the Oxford Text Archive + 10.1023/A:1001726011322 + + + Computers and the Humanities + + 33 + 1-2 + 1999 + 193-198 + + + + + + + Elli + Mylonas + + + Allen + Renear + + The Text Encoding Initiative at 10: Not Just an Interchange Format + Anymore — But a New Research Community + 10.1023/A:1001832310939 + + + Computers and the Humanities + + 33 + 1-2 + 1999 + 1-9 + + + + + + + Tobin + Nellhaus + + XML, TEI, Digital Libraries in the Humanities + + + + Portal: Libraries and the Academy + + 1 + 3 + 2001 + 267-277 + + + + + + + + Sebastian + Rahtz + + Building TEI DTDs and Schemas on demand + + + + 2003 + + + Paper presented at XML Europe 2003, London, March 2003 + + + + + Sebastian + Rahtz + + + Norman + Walsh + + + Lou + Burnard + + A unified model for text markup: TEI, Docbook, and beyond + + + 2004 + + + Paper presented at XML Europe 2004, Amsterdam, April 2004 + + + + + Allen + Renear + + Theory and Metatheory in the Development of Text Encoding + + + + + Michael + A. + R. + Biggs + + + Claus + Huitfeldt + + Philosophy and Electronic Publishing + + 1995 + + + Interactive seminar for the Monist + + + + + + Peter + Robinson + + Making a Digital Edition with TEI and Anastasia + + + (no date) + + + + + + + + David + Seaman + + The Electronic Text Center Introduction to TEI and Guide to Document + Preparation + + + 1995 + + + + + + + Gary + F. + Simons + + Using Architectural Forms to Map TEI Data into an Object-Oriented + Database + 10.1023/A:1001765030032 + + + Computers and the Humanities + + 33 + 1-2 + 1999 + 85-101 + + + + + + + David + Smith + + Textual Variation and Version Control in the TEI + 10.1023/A:1001795210724 + + + Computers and the Humanities + + 33 + 1-2 + 1999 + 103-112 + + + + + + + C. + Michael + Sperberg-McQueen + + Text in the Electronic Age: Textual Study and Text Encoding, with + Examples from Medieval Texts + 10.1093/llc/6.1.34 + + + Literary & Linguistic Computing + + 6 + 1 + 1991 + 34-46 + + + + + + + C. + Michael + Sperberg-McQueen + + The Text Encoding Initiative: Electronic Text Markup for + Research + + + + Brett + Sutton + + Literary Texts in an Electronic Age + + Urbana-Champaign, IL + University of Illinois at Urbana-Champaign, Graduate School of Library and + Information Science + 1994 + 35–55 + + + + + + + C. + Michael + Sperberg-McQueen + + Textual Criticism and the Text Encoding Initiative + + + + Richard + J. + Finneran + + The Literary Text in the Digital Age + + Ann Arbor, MI + University of Michigan Press + 1996 + 37–62 + + + + + + + Edward + Vanhoutte + + An Introduction to the TEI and the TEI Consortium + 10.1093/llc/19.1.9 + + + Literary & Linguistic Computing + + 19 + 1 + 2004 + 9 + + + + + + + T. + Kindberg + + + S. + Hawke + + The 'tag' URI Scheme + + RFC 4151 + + 2005 + IETF + + + + + +
+
+
diff --git a/P5/Source/Guidelines/fr/CC-LanguageCorpora.xml b/P5/Source/Guidelines/fr/CC-LanguageCorpora.xml deleted file mode 120000 index 355a055774..0000000000 --- a/P5/Source/Guidelines/fr/CC-LanguageCorpora.xml +++ /dev/null @@ -1 +0,0 @@ -../en/./CC-LanguageCorpora.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/CC-LanguageCorpora.xml b/P5/Source/Guidelines/fr/CC-LanguageCorpora.xml new file mode 100644 index 0000000000..5d5422140e --- /dev/null +++ b/P5/Source/Guidelines/fr/CC-LanguageCorpora.xml @@ -0,0 +1,1160 @@ + + + + +
Language Corpora +

The term language corpus is used to mean a number of +rather different things. It may refer simply to any collection of +linguistic data (for example, written, spoken, signed, or multimodal), although +many practitioners prefer to reserve it for collections which have +been organized or collected with a particular end in view, generally to +characterize a particular state or variety of one or more languages. +Because opinions as to the best method of achieving this goal differ, +various subcategories of corpora have also been identified. For our +purposes however, the distinguishing characteristic of a corpus is that +its components have been selected or structured according to some +conscious set of design criteria.

+

These design criteria may be very simple and undemanding, or very +sophisticated. A corpus may be intended to represent (in the +statistical sense) a particular linguistic variety or sublanguage, or +it may be intended to represent all aspects of some assumed +core language. A corpus may be made up of whole +texts or of fragments or text samples. It may be a +closed corpus, or an open or +monitor corpus, the composition of which may +change over time. However, since an open corpus is of necessity +finite at any particular point in time, the only likely effect of its +expansibility from the encoding point of view may be some increased +difficulty in maintaining consistent encoding practices (see further +section ). For simplicity, therefore, our +discussion largely concerns ways of encoding closed corpora, regarded +as single but composite texts.

+

Language corpora are regarded by these Guidelines as +composite texts rather than unitary texts +(on this distinction, see chapter ). This is +because although each discrete sample of language in a corpus clearly +has a claim to be considered as a text in its own right, it is also +regarded as a subdivision of some larger object, if only for +convenience of analysis. Corpora share a number of characteristics +with other types of composite texts, including anthologies and +collections. Most notably, different components of composite texts +may exhibit different structural properties (for example, some may be +composed of verse, and others of prose), thus potentially requiring +elements from different TEI modules.

+

Aside from these high-level structural differences, and possibly +differences of scale, the encoding of language corpora and the +encoding of individual texts present identical sets of problems. Any +of the encoding techniques and elements presented in other chapters of +these Guidelines may therefore prove relevant to some aspect of corpus +encoding and may be used in corpora. Therefore, we do not repeat here +the discussion of such fundamental matters as the representation of +multiple character sets (see chapter ); nor do we +attempt to summarize the variety of elements provided for encoding +basic structural features such as quoted or highlighted phrases, +cross-references, lists, notes, editorial changes and reference systems (see +chapter ). In addition to these general purpose +elements, these Guidelines offer a range of more specialized sets of +tags which may be of use in certain specialized corpora, for example +those consisting primarily of verse (chapter ), +drama (chapter ), transcriptions of spoken text +(chapter ), etc. Chapter +should be reviewed for details of how these and other components of +these Guidelines should be tailored to create a TEI customization +appropriate to a given application. In sum, it should not be assumed +that only the matters specifically addressed in this chapter are of +importance for corpus creators.

+

This chapter does however include some other material +relevant to corpora and corpus-building, for which no other location +appeared suitable. It begins with a review of the distinction between +unitary and composite texts, and of the different methods provided by +these Guidelines for representing composite texts of different kinds +(section ). Section describes a +set of additional header elements provided for the documentation of +contextual information, of importance largely though not exclusively to +language corpora. This is the additional module for language corpora +proper. Section discusses a mechanism by which +individual parts of the TEI header may be associated with different +parts of a TEI-conformant text. Section reviews +various methods of providing linguistic annotation in corpora, with some +specific examples of relevance to current practice in corpus +linguistics. Finally, section provides some general +recommendations about the use of these Guidelines in the building of +large corpora.

+
Varieties of Composite Text +

Both unitary and composite texts may be encoded using these +Guidelines; composite texts, including corpora, will typically make +use of the following tags for their top-level organization. + Full descriptions of these may be found in +chapter (for teiHeader), and chapter (for teiCorpus, TEI, text, and +group); this section discusses their application to composite +texts in particular.

+

In these Guidelines, the word text refers to any stretch +of discourse, whether complete or incomplete, unitary or composite, +which the encoder chooses (perhaps merely for purposes of analytic +convenience) to regard as a unit. The term composite text +refers to texts within which other texts appear; the following common +cases may be distinguished: + +language corpora +collections or anthologies +poem cycles and epistolary works (novels or essays written +in the form of collections or series of letters) +otherwise unitary texts, within which one or more subordinate +texts are embedded +The elements listed above may be combined to encode each of these +varieties of composite text in different ways.

+

In corpora, the component samples are clearly distinct texts, but the +systematic collection, standardized preparation, and common markup of +the corpus often make it useful to treat the entire corpus as a unit, +too. Some corpora may become so well established as to be regarded as +texts in their own right; the Brown and LOB corpora are now close to +achieving this status.

+

The teiCorpus element is intended for the encoding of +language corpora, though it may also be useful in encoding newspapers, +electronic anthologies, and other disparate collections of material. +The TEI element may be used in the same manner itself; the +teiCorpus element, however, makes explicit the multiplicity +of the collection, whatever it may be. The individual samples in the +corpus are encoded as separate TEI elements, and the entire +corpus is enclosed in a TEI or teiCorpus element. +Each sample has the usual structure for a TEI document, +comprising a teiHeader followed by one or more members of the +model.resource class. The corpus, too, +has a corpus-level teiHeader element, in which the corpus as +a whole, and encoding practices common to multiple samples may be +described. The overall structure of a TEI-conformant corpus is thus: + + + + + + + + + + + +Or, alternatively: + + + + + + + + + + +

+

Header information which relates to the whole corpus rather than to +individual components of it should be factored out and included in the +teiHeader element prefixed to the whole. This two-level +structure allows for contextual information to be specified at the +corpus level, at the individual text level, or at both. Discussion of +the kinds of information which may thus be specified is provided +below, in section , as well as in chapter . Information of this type should in general be +specified only once: a variety of methods are provided for associating +it with individual components of a corpus, as further described in +section .

+

In some cases, the design of a corpus is reflected in its internal +structure. For example, a corpus of newspaper extracts might be +arranged to combine all stories of one type (reportage, editorial, +reviews, etc.) into some higher-level grouping, possibly with sub-groups +for date, region, etc. A teiCorpus element may occur +directly inside a teiCorpus specifically to allow +direct support for reflecting such internal corpus structure in the +markup. For example: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

+

Furthermore, useful groupings +of components may easily be expressed using the text classification and +identification elements described in section , +and those for associating declarations with corpus components described +in section . These methods also allow several +different methods of text grouping to co-exist, each to be used as +needed at different times. This helps minimize the danger of +cross-classification and misclassification of samples, and helps +improve the flexibility with which parts of a corpus may be +characterized for different applications.

+

Anthologies and collections are often treated as texts in their own +right, if only for historical reasons. In conventional publishing, at +least, anthologies are published as units, with single editorial +responsibility and common front and back matter which may need to be +included in their electronic encodings. The texts collected in the +anthology, of course, may also need to be identifiable as distinct +individual objects for study.

+

Poem cycles, epistolary novels, and epistolary essays differ from +anthologies in that they are often written as single works, by single +authors, for single occasions; nevertheless, it can be useful to treat +their constituent parts as individual texts, as well as the cycle +itself. Structurally, therefore, they may be treated in the same way +as anthologies: in both cases, the body of the text is composed +largely of other texts.

+

The group element is provided to simplify the encoding of +collections, anthologies, and cyclic works; the group element +may also be used to record the potentially complex internal structure +of language corpora. (For a full description, see chapter .) The choice between using group or nested +teiCorpus elements is up to individual encoders, but in +general when it is useful to associate a significant quantity of +metadata with such a unit of text it is easier to use +teiCorpus.

+

Some composite texts, finally, are neither corpora, nor anthologies, +nor cyclic works: they are otherwise unitary texts within which other +texts are embedded. In general, they may be treated in the same way as +unitary texts, using the normal TEI and +body elements. The embedded text itself may be encoded using +the text element. For further discussion, see chapter .

+

All composite texts share the characteristic that their different +component texts may be of structurally similar or dissimilar types. If +all component texts may all be encoded using the same module, +then no problem arises. If however they require +different modules, then these must be included in the TEI customization. This +process is described in more detail in section .

+ +
Contextual Information +

Contextual information is of particular importance for collections +or corpora composed of samples from a variety of different kinds of +text. Examples of such contextual information include: the age, sex, +and geographical origins of participants in a language interaction, or +their socio-economic status; the cost and publication data of a +newspaper; the topic, register or factuality of an extract from a +textbook. Such information may be of the first importance, whether as +an organizing principle in creating a corpus (for example, to ensure +that the range of values in such a parameter is evenly represented +throughout the corpus, or represented proportionately to the population +being sampled), or as a selection criterion in analysing the corpus +(for example, to investigate the language usage of some particular +vector of social characteristics).

+

Such contextual information is potentially of equal importance for +unitary texts, and these Guidelines accordingly make no particular +distinction between the kinds of information which should be gathered +for unitary and for composite texts. In either case, the information +should be recorded in the appropriate section of a TEI header, as +described in chapter . In the case of language corpora, +such information may be gathered together in the overall corpus header, +or split across all the component texts of a corpus, in their individual +headers, or divided between the two. The association between an +individual corpus text and the contextual information applicable to it +may be made in a number of ways, as further discussed in section below.

+

Chapter , which should be read in conjunction with +the present section, describes in full the range of elements available +for the encoding of information relating to the electronic file itself, +for example its bibliographic description and those of the source or +sources from which it was derived (see section ); +information about the encoding practices followed with the corpus, for +example its design principles, editorial practices, reference system, +etc. (see section ); more detailed descriptive +information about the creation and content of the corpus, such as the +languages used within it and any descriptive classification system used +(see section ); and version information documenting any +changes made in the electronic text (see section ).

+

In addition to the elements defined by chapter , +several other elements can be used in the TEI header if the additional +module defined by this chapter is invoked. These additional tags make +it possible to characterize the social or other situation within which a +language interaction takes place or is experienced, the physical setting +of a language interaction, and the participants in it. Though this +information may be relevant to, and provided for, unitary texts as well +as for collections or corpora, it is more often recorded for the +components of systematically developed corpora than for isolated texts, +and thus this module is referred to as being for language +corpora.

+ +

When the module defined in this chapter is included in a schema, a +number of additional elements become available within the +profileDesc element of the TEI header (discussed in section +). These +elements, members of the model.profileDescPart, are discussed in the +remainder of the chapter. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

+ +
The Text Description +

The textDesc element provides a full description of the +situation within which a text was produced or experienced, and thus +characterizes it in a way relatively independent of any a +priori theory of text-types. It is provided as an alternative +or a supplement to the common use of descriptive taxonomies used to +categorize texts, which is fully described in section , and section . The description is +organized as a set of values and optional prose descriptions for the +following eight situational parameters, each represented by +one of the following eight elements: +

+

These elements constitute a model class called model.textDescPart; new parameters may be defined +by defining new elements and adding them to that class, as further +described in .

+ +

By default, a text description will contain each of the above +elements, supplied in the order specified. Except for the +purpose element, which may be repeated to indicate multiple +purposes, no element should appear more than once within a single text +description. Each element may be empty, or may contain a brief +qualification or more detailed description of the value expressed by +its attributes. It should be noted that some texts, in particular +literary ones, may resist unambiguous classification in some of these +dimensions; in such cases, the situational parameter in question +should be given the content not applicable or an equivalent +phrase.

+

Texts may be described along many dimensions, according to many +different taxonomies. No generally accepted consensus as to how such +taxonomies should be defined has yet emerged, despite the best efforts +of many corpus linguists, text linguists, sociolinguists, +rhetoricians, and literary theorists over the years. Rather than +attempting the task of proposing a single taxonomy of +text-types (or the equally impossible one of enumerating +all those which have been proposed previously), the closed set of +situational parameters described above can be used in +combination to supply useful distinguishing descriptive features of +individual texts, without insisting on a system of discrete high-level +text-types. Such text-types may however be used in combination with +the parameters proposed here, with the advantage that the internal +structure of each such text-type can be specified in terms of the +parameters proposed. This approach has the following analytical +advantages:Schemes similar to that proposed here were developed +in the 1960s and 1970s by researchers such as Hymes, Halliday, and +Crystal and Davy, but have rarely been implemented; one notable +exception being the pioneering work on the Helsinki Diachronic Corpus +of English, on which see + + it enables a relatively continuous characterization of texts (in +contrast to discrete categories based on type or topic) +it enables meaningful comparisons across corpora +it allows analysts to build and compare their own text-types +based on the particular parameters of interest to them +it is equally applicable to spoken, written, or signed texts

+

Two alternative approaches to the use of these parameters are +supported by these Guidelines. One is to use pre-existing taxonomies +such as those used in subject classification or other types of text +categorization. +Such taxonomies may also be appropriate for the description of the +topics addressed by particular texts. Elements for this purpose are +described in section , and elements for defining or +declaring such classification schemes in section . A +second approach is to develop an application-specific set of +feature structures and an associated feature system +declaration, as described in +chapters and .

+

Where the organizing principles of a corpus or collection so permit, +it may be convenient to regard a particular set of values for the +situational parameters listed in this section as forming a +text-type in its own right; this may also be useful where +the same set of values applies to several texts within a corpus. In +such a case, the set of text-types so defined should be regarded as a +taxonomy. The mechanisms described in section may be used to define hierarchic taxonomies of such +text-types, provided that the catDesc component of the +category element contains a textDesc element rather +than a prose description. Particular texts may then be associated with +such definitions using the mechanisms described in sections .

+ +

Using these situational parameters, an informal domestic +conversation might be characterized as follows: + + informal face-to-face conversation + each text represents a continuously + recorded interaction among the specified participants + + + plans for coming week, local affairs + mostly factual, some jokes + + + + + +

+

The following example demonstrates how the same situational +parameters might be used to characterize a novel: + + print; part issues + + + + + + + + + + +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+
The Participant Description + +

The particDesc element in the profileDesc element +provides additional information about the participants in a spoken +text or, where this is judged appropriate, the persons named or +depicted in a written text. When the detailed elements provided by +the namesdates module described in are included in a schema, this element can +contain detailed demographic or descriptive information about +individual speakers or groups of speakers, such as their names or +other personal characteristics. Individually identified persons may +also identified by a code which can then be used elsewhere within the +encoded text, for example as the value of a who +attribute.

+ +

It should be noted that although the terms speaker or +participant are used throughout this section, it is +intended that the same mechanisms may be used to characterize fictional +personæ or voices within a written text, except +where otherwise stated. For the purposes of analysis of language usage, +the information specified here should be equally applicable to +written, spoken, or signed texts.

+

The element particDesc contains a description of the +participants in an interaction, which may be supplied as +straightforward prose, possibly containing a list of names, encoded +using the usual list and name elements, or +alternatively using the more specific and detailed listPerson +element provided by the namesdates module +described in .

+

For example, a participant in a recorded conversation might be +described informally as follows: + +

Female informant, well-educated, born in Shropshire UK, 12 Jan + 1950, of unknown occupation. Speaks French fluently. + Socio-Economic status B2 in the PEP classification scheme.

+

+ +

Alternatively, when the namesdates module +is included in a schema, information about the same participant +described above might be provided in a more structured way as follows: + + + 12 Jan 1950 + Shropshire, UK + + + English + French + + Long term resident of Hull + University postgraduate + Unknown + +

+

An identified character in a drama or a novel may also be regarded +as a participant in this sense, and encoded using +the same techniques:It is particularly useful to +define participants in a dramatic text in this way, since it enables the +who attribute to be used to link sp elements to +definitions for their speakers; see further section . + +

The chief speaking characters in this novel are + + Emma Woodhouse + Mr Darcy + + +

+ +Here, the characters are simply listed without the detailed +structure which use of the listPerson element permits.

+ +
+
+The Setting Description +

The settingDesc element is used to describe the setting or +settings in which language interaction takes place. It may contain a +prose description, analogous to a stage description at the start of a +play, stating in broad terms the locale, or a more detailed +description of a series of such settings.

+

Each distinct setting is described by means of a setting +element. + + + + + +Individual settings may be associated with particular participants by +means of the optional who attribute which this element +inherits as a member of the att.ascribed +if, for example, participants are in different places. This attribute +identifies one or more individual participants or participant groups, +as discussed earlier in section . If this +attribute is not specified, the setting details provided are assumed +to apply to all participants represented in the language +interaction. Note however that it is not possible to encode different +settings for the same participant: a participant is deemed to be a +person within a specific setting.

+

The setting element may contain either a prose description +or a selection of elements from the classes model.nameLike.agent, model.dateLike, or +model.settingPart. By default, when the +module defined by this chapter is included in a schema, these classes thus +provide the following elements: + + + + + + + +Additional more specific naming elements such as orgName or +persName may also be available if the +namesdates module is also included in the schema.

+

The following example demonstrates the kind of background information +often required to support transcriptions of language interactions, first +encoded as a simple prose narrative: + +

The time is early spring, 1989. P1 and P2 are playing on the rug + of a suburban home in Bedford. P3 is doing the washing up at the + sink. P4 (a radio announcer) is in a broadcasting studio in + London.

+ +The same information might be represented more formally in the following +way: + + + Bedford + UK: South East + early spring, 1989 + rug of a suburban home + playing + + + Bedford + UK: South East + early spring, 1989 + at the sink + washing-up + + + London, UK + + broadcasting studio + radio performance + +

+

Again, a more detailed encoding for places is feasible if the +namesdates module is included in the +schema. The above examples assume that only the +general purpose name element supplied in the core module is +available. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

+
Associating Contextual +Information with a Text +

This section discusses the association of the contextual information +held in the header with the individual elements making up a TEI text or +corpus. Contextual information is held in elements of various kinds +within the TEI header, as discussed elsewhere in this section and in +chapter . Here we consider what happens when different +parts of a document need to be associated with different contextual +information of the same type, for example when one part of a document +uses a different encoding practice from another, or where one part +relates to a different setting from another. In such situations, there +will be more than one instance of a header element of the relevant type.

+

The TEI scheme allow for the following possibilities: + +A given element may appear in the corpus header only, in the +header of one or more texts only, or in both places +There may be multiple occurrences of certain elements in either +the corpus or a text header.

+

To simplify the exposition, we deal with these two possibilities +separately in what follows; however, they may be combined as +desired.

+
Combining Corpus and Text Headers +

A TEI-conformant document may have more than one header only in the +case of a TEI corpus, which must have a header in its own right, as well +as the obligatory header for each text. Every element specified in a +corpus-header is understood as if it appeared within every text header +in the corpus. An element specified in a text header but not in the +corpus header supplements the specification for that text alone. If any +element is specified in both corpus and text headers, the corpus header +element is over-ridden for that text alone.

+

The titleStmt for a corpus text is understood to be +prefixed by the titleStmt given in the corpus header. All +other optional elements of the fileDesc should be omitted from +an individual corpus text header unless they differ from those +specified in the corpus header. All other header elements behave +identically, in the manner documented below. +This facility makes it possible to state once for all in the corpus +header each piece of contextual information which is common to the whole +of the corpus, while still allowing for individual texts to vary from +this common denominator.

+

For example, the following schematic shows the structure of a corpus +comprising three texts, the first and last of which share the same +encoding description. The second one has its own encoding description. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

+
Declarable Elements + +

Certain of the elements which can appear within a TEI header are +known as declarable elements. These elements have in +common the fact that they may be linked explicitly with a particular +part of a text header or the corpus header by means of a decls attribute on +that element. This linkage is used to over-ride the default +association between declarations in the header and a corpus or corpus +text. The only header elements which may be associated in this way are +those which would not otherwise be meaningfully repeatable.

+

Declarable elements are all members of the class att.declarable; the corresponding declaring +elements are all members of the class att.declaring. + + + +

+ +

An alphabetically ordered list of declarable elements follows: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +Each of the above elements is repeatable within a single +header; that is, there may be more than one instance of any declarable +element type at a given level. When this occurs, the following rules +apply. For each different type of declarable element which occurs more +than once: + +each must bear a unique identifier +when occurring within the same parent element, exactly one element must be +specified as the default, by having a default attribute with the value "true". +

+

In the following example, an editorial declaration contains two +possible correction policies, one identified as +CorPol1 and the other as CorPol2. Since there +are two, one of them (in this case CorPol1) should be +specified as the default: + +

...

+ + +

...

+ + +

...

+

...

+ + For texts associated with the header in which +this declaration appears, correction method CorPol1 will be +assumed, unless they explicitly state otherwise. Here is the +structure of a text in which a division states otherwise: + + + + + + In this case, the contents of the divisions D1 and D3 +will both use correction policy CorPol1, and those of +division D2 will use correction policy CorPol2.

+

The decls attribute is defined for any element which is a +member of the class declaring. This includes the major +structural elements text, group, and div, as +well as smaller structural units, down to the level of paragraphs in +prose, individual utterances in spoken texts, and entries in +dictionaries. However, TEI recommended practice is to limit the number +of multiple declarable elements used by a document as far as possible, +for simplicity and ease of processing.

+

The identifier or identifiers to which the decls +attribute points must follow two further restrictions: + +When decl references an element that itself contains multiple +elements of the same type, only the children elements with default +set to "true" are considered referenced. +Each element specified, explicitly or implicitly, by the list of +identifiers must be of a different kind.

+

To demonstrate how these rules operate, we now expand our earlier +example slightly: + + + + +

...

+ +

...

+ +

...

+

...

+ + + +

...

+

...

+

...

+

...

+ + +

+

This encoding description now has two editorial declarations, +identified as ED1 (the default) and ED2. For texts not specifying +otherwise, ED1 will apply. If ED1 applies, correction method C1A and +normalization method N1 apply, since these are the specified defaults +within ED1. In the same way, for a text specifying decls as +#ED2, correction C2A, + and normalization N2B will +apply.

+

A finer grained approach is also possible. A text might specify +text decls='#C2B #N2A', + to mix and match declarations as +required. A tag such as text decls='#ED1 #ED2' would +(obviously) be illegal, since it includes two elements of the same type; +a tag such as text decls='#ED2 #C1A' is also illegal, since in +this context #ED2 is synonymous with the defaults for that +editorial declaration, namely #C2A #N2B, resulting in a list +that identifies two correction elements (C1A and C2A).

+
Summary +

The rules determining which of the declarable elements are applicable +at any point may be summarized as follows: + +If there is a single occurrence of a given declarable +element in a corpus header, then it applies by default to all elements +within the corpus. +If there is a single occurrence of a given declarable +element in the text header, then it applies by default to all elements +of that text irrespective of the contents of the corpus header. +Where there are multiple occurrences of declarable elements + within a text’s header or its corpus header, + +each must have a unique value specified as the value +of its xml:id attribute; +one and only one must bear a default attribute with + the value true (or 1). +It is a semantic error for an element to be associated +with more than one occurrence of any declarable element. +Selecting an element which contains multiple occurrences of a +given declarable element is semantically equivalent to selecting only +those contained elements which are specified as defaults. +An association made by one element applies by default +to all of its descendants. +

+
Linguistic Annotation of Corpora +

Language corpora often include analytic encodings or annotations, +designed to support a variety of different views of language. The +present Guidelines do not advocate any particular approach to linguistic +annotation (or tagging); instead a number of +general analytic facilities are provided which support the +representation of most forms of annotation in a standard and +self-documenting manner. Analytic annotation is of importance in many +fields, not only in corpus linguistics, and is therefore discussed in +general terms elsewhere in the +Guidelines.See in particular chapters +, , and . +The present section presents informally some particular applications of +these general mechanisms to the specific practice of corpus linguistics.

+
Levels of Analysis +

By linguistic annotation we mean here any annotation +determined by an analysis of linguistic features of the text, excluding +as borderline cases both the formal structural properties of the text +(e.g. its division into chapters or paragraphs) and descriptive +information about its context (the circumstances of its production, its +genre, or medium). The structural properties of any TEI-conformant text +should be represented using the structural elements discussed elsewhere +in these Guidelines, for example in chapters and +. +The contextual +properties of a TEI text are fully documented in the TEI header, which +is discussed in chapter , and in section of the present chapter.

+

Other forms of linguistic annotation may be applied at a number of +levels in a text. A code (such as a word-class or part-of-speech +code) may be associated with each word or token, or with groups of such +tokens, which may be continuous, discontinuous, or nested. A code may +also be associated with relationships (such as cohesion) perceived as +existing between distinct parts of a text. The codes themselves may +stand for discrete non-decomposable categories, or they may represent +highly articulated bundles of textual features. Their function may be +to place the annotated part of the text somewhere within a narrowly +linguistic or discoursal domain of analysis, or within a more general +semantic field, or any combination drawn from these and other domains.

+

The manner by which such annotations are generated and attached to +the text may be entirely automatic, entirely manual, or a mixture. The +ease and accuracy with which analysis may be automated may vary with the +level at which the annotation is attached. The method employed should +be documented in the interpretation element within the encoding +description of the TEI header, as described in section . Where different parts of a corpus have used different +annotation methods, the decls attribute should be used to +indicate the fact, as further discussed in section .

+

An extended example of one form of linguistic analysis commonly +practised in corpus linguistics is given in section .

+
+
Recommendations for the Encoding of Large Corpora +

These Guidelines include proposals for the identification and +encoding of a far greater variety of textual features and +characteristics than is likely to be either feasible or desirable in +any one language corpus, however large and ambitious. The reasoning +behind this universal approach is further discussed in chapter . +For most large-scale corpus projects, it will therefore +be necessary to determine a subset of TEI recommended elements +appropriate to the anticipated needs of the project, as further +discussed in chapter ; these mechanisms include +the ability to exclude selected element types, add new element types, +and change the names of existing elements. A discussion of the +implications of such changes for TEI conformance is provided in +chapter .

+

Because of the high cost of identifying and encoding many textual +features, and the difficulty in ensuring consistent practice across very +large corpora, encoders may find it convenient to divide the set of +elements to be encoded into the following four categories: + +texts included within the corpus will always +encode textual features in this category, should they exist in the +text +textual features in this category will be +encoded wherever economically and practically feasible; where present +but not encoded, a note in the header should be made. +textual features in this category may or may not +be encoded; no conclusion about the absence of such features can be +inferred from the absence of the corresponding element in a given +text. + +textual features in this category are deliberately not encoded; they may be +transcribed as unmarked up text, or represented as gap +elements, or silently omitted, as appropriate.

+
+
+ Module for Language Corpora +

The module described in this chapter makes available the + following components: + + Metadata for Language Corpora + Corpus texts + Corpus linguistiques + 文集文本 + Corpus di testi + Textos do corpora + コーパスモジュール + + + + The selection and combination of modules to form a TEI schema is + described in .

+
+ +
diff --git a/P5/Source/Guidelines/fr/CE-CertaintyResponsibility.xml b/P5/Source/Guidelines/fr/CE-CertaintyResponsibility.xml deleted file mode 120000 index 564f456474..0000000000 --- a/P5/Source/Guidelines/fr/CE-CertaintyResponsibility.xml +++ /dev/null @@ -1 +0,0 @@ -../en/./CE-CertaintyResponsibility.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/CE-CertaintyResponsibility.xml b/P5/Source/Guidelines/fr/CE-CertaintyResponsibility.xml new file mode 100644 index 0000000000..424088a4c3 --- /dev/null +++ b/P5/Source/Guidelines/fr/CE-CertaintyResponsibility.xml @@ -0,0 +1,611 @@ + + + + +
Certainty, Precision, and Responsibility +

Encoders of text often find it useful to indicate that some aspects +of the encoded text are problematic or uncertain, and to indicate who is +responsible for various aspects of the markup of the electronic text. +These Guidelines provide several methods of recording uncertainty about the +text or its markup: + +the note element defined in section may +be used with a value of certainty for its type +attribute. +the certainty element defined in this chapter may be used +to record the nature and degree of the uncertainty in a more structured +way. +the precision element defined in this chapter may be +used to record the accuracy with which some numerical value (such as a +date or quantity) is provided by some other element or attribute. +the alt element defined in the module for +linking and segmentation may be used to provide alternative encodings +for parts of a text, as described in section . +There are three methods of indicating responsibility for different +aspects of the electronic text: + +the TEI header records who is responsible for an electronic text +by means of the respStmt element and other more specific elements +(author, sponsor, funder, principal, +etc.) used within the titleStmt, editionStmt, and +revisionDesc elements. +the note element may be used with a value of resp +or responsibility in its type attribute. +the respons element defined in this chapter may be used +to record fine-grained structured information about responsibility for +individual tags in the text. +No special steps are needed to use the note and respStmt elements, since they are defined in the core module and header +respectively. The alt element is only available when the +module for linking has been selected, as described in +chapter . To use the certainty, precision or +respons elements, the module for certainty and +responsibility should be selected. +

+ +

These three elements are all members of an attribute class called +att.scoping from which they inherit the +following attributes: + + + + +

+

These attributes enable statements about certainty, precision, or +responsibility to be made with respect to the whole of a document, or +any part or parts of it which can be identified using standard XML +location methods. Several examples are given in the discussion of the +certainty element below; the same mechanisms are available +for all three elements discussed in this chapter. +

+
Levels of Certainty +

Many types of uncertainty may be distinguished. The +certainty element is designed to encode the following sorts: + +a given tag may or may not correctly apply (e.g. a given word may +be a personal name, or perhaps not) +the precise point at which an element begins or ends is +uncertain +the value given for an attribute is uncertain +the content given for an element is unreliable for any reason.

+

The following types of uncertainty are not indicated +with the certainty element: + +the numerical precision associated with a number or date (for +this use the precision element discussed in ) + +the content of the document being transcribed is identifiable, +but may be read or understood in different ways +(for this use the transcriptional elements such as unclear, +discussed in chapter ) +a transcriber, editor, or author wishes to indicate a level of +confidence in a factual assertion made in the text (for this use the +interpretative mechanisms discussed in and ) + +

+
Using Notes to Record Uncertainty +

The simplest way of recording uncertainty about markup is to attach a +note to the element or location about which one is unsure. In the +following (invented) paragraph, for example, an encoder might be +uncertain whether to mark Essex as a place name or a personal +name, since both might be plausible in the given context: +Elizabeth went to Essex. She had always liked Essex. +Using note, the uncertainty here may be recorded quite simply: +Elizabeth went to Essex. She had always liked Essex.It is not +clear here whether Essex +refers to the place or to the nobleman. -MSM

+

Using the normal mechanisms, the note may be associated +unambiguously with specific elements of the text, thus: +Elizabeth went to Essex. +She had always liked Essex.It +is not clear here whether Essex +refers to the place or to the nobleman. If the latter, +it should be tagged as a personal name. -Michael

+

The advantage of this technique is its relative simplicity. Its +disadvantage is that the nature and degree of uncertainty are not +conveyed in any systematic way and thus are not susceptible to any sort +of automatic processing.

+
Structured Indications of Uncertainty +

To record uncertainty in a more structured way, susceptible of at +least simple automatic processing, the certainty element may be +used: +

+

Returning to the example, the certainty element may be used to record doubts about +the proper encoding of Essex in several ways of varying +precision. To record merely that we are not certain that Essex +is in fact a place name, as it is tagged, we use the target +attribute to identify the element in question, and the locus +attribute to indicate which aspect of the markup we are uncertain about +(in this case, whether we have used the correct name for the +element used to mark it): +Elizabeth went to +Essex. + +possibly not a placename +There are no particular constraints as to where the +certainty element is placed in a document; it may be placed adjacent to the target +element, or elsewhere in the same or another document. Its position +is however significant when the target attribute is not specified +as further discussed below. +

+

We may wish to record the probability, assessed in some subjective +way, that Essex really is a place name here. The +degree attribute is used to indicate the degree of +confidence associated with the certainty element, expressed as a +number between 0 and 1: + + + +This expresses the point of view that there is a 60 percent chance of Essex +being a place name here, and hence a 40 percent chance of its being a +personal name. We can use two certainty elements to indicate the +two probabilities independently. Both elements indicate the same location in the +text, but the second provides an alternative choice of name +identifier (in this case persName), which is given as the +value of the assertedValue attribute: + + + + probably a placename, but possibly not + + may refer to the Earl of Essex

+ +

In the simplest case, it is also possible to place the +certainty element within the element concerned: + +Elizabeth went to +Essex +. +When no target is specified, by default the proposed +certainty applies to its parent element, in this case the +placeName element. The match attribute discussed +below may be used to further vary this behaviour.

+ +
Contingent Conditions + +

Finally, we may wish to make our probability estimates contingent +on some condition. In the passage Elizabeth went to Essex; she had +always liked Essex, for example, we may feel there is a 60 percent chance +that the county is meant, and a 40 percent chance that the earl is meant. But +the two occurrences of the word are not independent: there is (we may +feel) no chance at all that the first occurrence refers to the county +and the second +to the earl. We can express this by using the given +attribute to list the identifiers of certainty elements. +Elizabeth went to Essex. +She had always liked Essex. + + + + probably a placename, but possibly not" + + may refer to the Earl of Essex" + + + if CE-PL1 is a placename, CE-PL2 certainly is" + + if CE-PL1 is a personal name, then so is CE-PL2 +When given conditions are listed, the certainty +element is interpreted as claiming a given degree of confidence in a +particular markup given the assertional content of the +certainty elements indicated. That is, a conjectural +assertion is being made solely on the assumption that the +interpretation indicated by the element named by the given +attribute is actually correct.

+ +

Conditional confidence may be less than 100 percent: given the sentence +Ernest went to old Saybrook, we may interpret Saybrook as +a personal name or a place name, assigning a 60 percent probability to the +former. If it is a place name, there may be a 50 percent chance that the +place name actually in question is Old Saybrook rather than +Saybrook, while if it is correctly tagged as a personal name, it +is much more likely (say, 90 percent certain) that the name is Saybrook. +Hence there is uncertainty about the correct location for the markup +as well as about which markup to use. This state of affairs can be expressed using the certainty element thus: +Ernest went to old Saybrook. + + + + + + + +Note the use of the assertedValue on certainty +elements cert3 and cert4 to reference +the anchor element placed at the alternative starting +point for the element.

+ +

Multiplying the numeric values out, this markup may be interpreted as +assigning specific probabilities to three different ways of +marking up the sentence: +Ernest went to old Saybrook. (0.6 * 0.9, or 0.54) +Ernest went to old Saybrook. (0.4 * 0.5, or 0.20) +Ernest went to old Saybrook. (0.4 * 0.5, or 0.20) +The probabilities do not add up to 1.00 because the markup indicates +that if Saybrook is (part of) a personal name, there is a +10 percent likelihood that the element should start somewhere other than the +place indicated, without however giving an alternative location; there +is thus a 6 percent chance (0.1 × 0.6) that none of the alternatives given is +correct.

+
+
Pervasive Conditions +

We may also wish to indicate confidence in some aspect +of the tagging throughout a document, rather than (as discussed so far) in one +particular instance. The match attribute may be used to +supply a pattern identifying the portion of a document +concerning which certainty is being expressed. The value of the +match attribute is an XSLT selection pattern +using the syntax defined in . In the following +example, we wish to indicate a low degree of confidence +that the persName elements used throughout the whole document +have been correctly applied: + + + + + +No target has been supplied here, and so by default the +certainty expressed would therefore apply to the parent +element. However, in this case the XPath supplied as the value for +match returns a set of all the persName elements +in the document, independent of the current context. By contrast, in +the following example + +

[...]

+
+ +
+ +only the persName elements within the second div +element are in question. +Similarly, we may indicate that we have more +confidence in the persName tagging within those div +elements which have a type value of checked: + + + + + +If an element in a document is matched by more than one match +expression, then the most specific pattern applies. Specificity of +pattern matching is defined further in the XSLT3 reference cited above +(see ) As a +simple case, if both the preceding certainty elements were +present in the same document, a persName occurring within a +div type="checked" element would potentially match both +pattern expressions. However because the second pattern is more +specific than the former, in fact this is the only one that would +apply. If multiple patterns match and have the same priority, then the +first one (in document order) is applied. Only those statements of certainty +which have matched in this sense are available for conditional +application using the given attribute mentioned above. +

+

When the match attribute is processed, the namespace bindings in +force are those in effect at that point in the document. +For example, + +

+ + +
+ +might be used to indicate a high degree of certainty about the content +of any elements taken the namespace associated with the prefix +my. This namespace prefix must be associated with an +appropriate namespace definition, either on the certainty +element itself, or on one of its ancestor elements.

+
+ +
Content Uncertainty + +

Doubts about whether the content of an element is correct may also be expressed +by assigning to locus the value +value. For example, if the source is +hard to read and so the transcription is uncertain: +I have a bun. +

+

Degrees of confidence in the proper expansion of abbreviations may +also be expressed, as in the following example:You will want to use +Standard +Generalized Markup Language +Some Grandiose Methodology for Losers +SGML ... + + +

+

The assertedValue attribute should be used to provide an +alternative value for whatever aspect of the markup is in doubt: an +alternative name, or the identifier of an alternative starting or +ending point, as already shown, an alternative attribute value, or +alternative element content, as in this example: +I have a bun. + + a gun makes more sense in a holdup + Since attribute values have no internal substructure, the + assertedValue attribute is not generally useful for + specifying alternative transcriptions; it cannot for example be used + if the alternative reading contains markup of any kind. More robust + methods of handling uncertainties of transcription are the + unclear element and the app and rdg + elements described in chapter . The + certainty element allows for indications of uncertainty to + be structured with at least as much detail and clarity as appears to + be currently required in most ongoing text projects.

+
+ + +
Target or Match? + +

As noted in , the target attribute +may take any general teidata.pointer as values and may thus +also contain an XPath expression of arbitrary complexity. Because full +support for XPath is not provided by current processors, it is not +generally recommended TEI practice. There are however some simple +cases in which XPath syntax is to be preferred, notably those in which +the xml:id attribute is used to identify a single element +occurrence. The usage #A (to indicate the element whose +xml:id attribute has the value A) is +syntactically much simpler than the equivalent xpath2 expression +//*[@xml:id='A'] and is hence preferred throughout these +guidelines. +

+

For similar reasons, the certainty element may specify +both a target value (expressed as an URI) and a +match value (expressed as an XPath). The former defines +the context within which the latter is to be evaluated. As previously +noted, if no value is supplied for target, the context +within which the value of match should be evaluated is the +parent element of the certainty element itself.

+ +

A typical case where it may be convenient to specify both +target and match is that where we wish to +indicate that the value of an attribute on some specific element is +uncertain. In this case, the locus attribute +takes the value value. For example, supposing there is only a 50 percent chance that the question was spoken by +participant A: +Have you heard the election results? + or, equivalently and without the +need to define a target, +Have you heard the election results? + + +

+ +

The match and target attributes together +provide a powerful mechanism which can be used to indicate precision for a +large number of assertions throughout an encoded document in an +economical way. Some further +examples follow: + + + +This encoding indicates that there is only a 0.2 certainty that the +boundaries of all p elements in the document have been correctly +identified.

+

+ + + +This encoding indicates that there is only a 0.2 certainty that the +boundaries of the p elements contained by the element with +xml:id value a101 have been correctly +identified.

+

+ + +Essex + + +This encoding indicates that there is only a 0.2 certainty that the +value for the resp attribute on the given persName +element +is correct.

+

+ + + +This encoding indicates that there is only a 0.2 certainty that any +value for the resp attribute is correct, wherever it +appears in the document.

+ +

+ + +This encoding indicates that there is only a 0.2 certainty that the +value for the resp attribute of the element indicated by +the pointer #dd001 is correct

+ +

+ + +This encoding indicates that there is only a 0.2 certainty that the +content of any element the resp attribute of which has the +value #LB is correct, wherever it +appears in the document.

+ +

The certainty element and the other TEI mechanisms for +indicating uncertainty provide a range of methods of graduated +complexity. Simple expressions of uncertainty may be made by using +the note element. This is simple and convenient, and can +accommodate either a discursive and unstructured indication of +uncertainty, or a complex and structured but probably project-specific +expression of uncertainty. In general, however, unless special steps +are taken, the note element does not provide as much +expressive power as the certainty element, and in cases where +highly structured certainty information are needed, it is +recommended that the certainty element be preferred.

+ + + + + +
+
+ +
+ +
Indications of Precision +

As noted above, certainty about the accuracy of an encoding or its +content is not the same thing as the precision with which +a value is specified. In the case of a date or a quantity, for example, we might be +certain that the value given is imprecise, or uncertain +about whether or not the value given is correct. The latter +possibility would be represented by the certainty element +discussed in the previous section; the former by the +precision element discussed in this section.

+

The elements concerning which statements of precision are to be +made are identified using the same target and +match attributes inherited from the +att.scoping class discussed in the +previous section and in the same way. Other aspects are provided by +other attributes as further discussed below. + + + +

+

In several ways of indicating ranges of +values were introduced. For example, if we know that a date falls between +1930 and 1935, without being certain exactly where, this fact may be +encoded using attributes notBefore and +notAfter, as in the following example: + +Early in the 1930s... +Equally, if we know that every page of a +manuscript has a width of at least 10 cm but no more than 30, we can +use the attributes atLeast and atMost, as in the +following examples: + + +

+

Suppose however that the precision with which the value +of such an attribute can be specified is variable. For example, +suppose an event is dated about fifty years after the death of +Augustus. In this case, the precision of one end of the range (the +death of Augustus) is higher than the other, assuming we know when +Augustus died. We can say that the latest possible date is probably 50 +years after that, but with less confidence than we can attach to the +earliest possible date.

+

The precision element allows us to indicate the two +attributes concerned and attach different levels of precision to them, +using a similar mechanism as that provided for the certainty +element: + +About 50 +years after the death of Augustus + + +

+

In much the same way, we may wish to indicate different levels of +precision about the dating of either end of a historical period. For example, + the elements defined for encoding personal data all bear a similar + set of attributes to indicate normalized values for earliest or + latest dates, etc. (see section + ); the precision of these attribute values + may be indicated in exactly the same way. For example, + +From the 1st of March to +some time in April of 1857. + + +

+

It may also be useful to indicate that the precisions given for +minimum and maximum quanta differ. For example, to indicate that all +pages measure at least 10 cm wide, and at most about 30: + + + + +

+

The +stdDeviation attribute may be used to indicate the +standard deviation for a range of values. The generic dim +element introduced in might be used to record the average +number of characters per line in a typescript. If in addition we wish +to record the standard deviation for the values summarized by that +average, this would require an additional precision element, +as in the following example: + + + + +

+
+ +
Attribution of Responsibility +

In general, attribution of responsibility for the transcription and +markup of an electronic text is made by respStmt elements +within the header: specifically, within the title statement, the +edition statement(s), and the revision history.

+

In some cases, however, more detailed element-by-element information +may be desired. For example, an encoder may wish to distinguish between the +individuals responsible for transcribing the content and those +responsible for determining that a given word or phrase constitutes a +proper noun. Where such fine-grained attribution of responsibility is +required, the respons element can be used. +

+

This element allows one or more aspects of the markup to be +attributed to a given individual. This element inherits the +target and match attributes from the +att.scoping class, in the same way as the +certainty and precision elements. Its +locus attribute functions in the same way as that on the +certainty element (see ). It inherits the resp and cert +attributes from the att.global.responsibility class. +

+

For example, the following encoding +indicates that RC is responsible for transcribing an +illegible word, and that PMWR is responsible for identifying that word +as a proper noun, i.e. deciding to mark it with the persName +element at the location indicated: +Ernest went to old +Saybrook. + + + + + + +

+

Similarly, in the following example, we indicate that RC is +responsible for proposing the value of the rend attribute: + + + +

+ + +
+ +
The Certainty Module +

The module described in this chapter makes available the following +additional elements: + + + Certainty and Uncertainty + Certainty, Precision, and Responsibility + Degré de certitude et responsabilité + 確定程度與不確定程度 + Certezza e incertezza + Certeza e incerteza + 確信度モジュール + + + +The selection and combination of modules to form a TEI schema is described in +. + +

+
\ No newline at end of file diff --git a/P5/Source/Guidelines/fr/CH-LanguagesCharacterSets.xml b/P5/Source/Guidelines/fr/CH-LanguagesCharacterSets.xml deleted file mode 120000 index 4be9500eba..0000000000 --- a/P5/Source/Guidelines/fr/CH-LanguagesCharacterSets.xml +++ /dev/null @@ -1 +0,0 @@ -../en/CH-LanguagesCharacterSets.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/CH-LanguagesCharacterSets.xml b/P5/Source/Guidelines/fr/CH-LanguagesCharacterSets.xml new file mode 100644 index 0000000000..9292be69c7 --- /dev/null +++ b/P5/Source/Guidelines/fr/CH-LanguagesCharacterSets.xml @@ -0,0 +1,715 @@ + + + + +
+Languages and Character Sets +

The documents which users of these Guidelines may wish to encode +encompass all kinds of material, potentially expressed in the full +range of written and spoken human languages, including the extinct, +the non-existent, and the conjectural. Because of this wide scope, +special attention has been paid to two particular aspects of the +representation of linguistic information often taken for granted: +language identification and character encoding.

+

Even within a single document, material in many different languages +may be encountered. Human culture, and the texts which embody it, is +intrinsically multilingual, and shows no sign of ceasing to be so. +Traditional philologists and modern computational linguists alike work +in a polyglot world, in which code-switching (in the linguistic sense) +and accurate representation of differing language systems constitute +the norm, not the exception. The current increased interest in studies +of linguistic diversity, most notably in the recording and +documentation of endangered languages, is one aspect of this long +standing tradition. Because of their historical importance, the needs +of endangered and even extinct languages must be taken into account +when formulating Guidelines and recommendations such as these.

+

Beyond the sheer number and diversity of human languages, it should +be remembered that in their written forms they may deploy a huge +variety of scripts or writing systems. These scripts are in turn +composed of smaller units, which for simplicity we term here +characters. A primary goal when encoding a text should be to capture +enough information for subsequent users to correctly identify +not only the constituent characters, but also the language and script. In this chapter we +address this requirement, and propose recommended mechanisms to +indicate the languages, scripts and characters used in a document or a +part thereof.

+

Identification of language is dealt with in . In summary, it recommends the use of pre-defined +identifiers for a language where these are available, as they +increasingly are, in part as a result of the twin pressures of an +increasing demand for language-specific software and an increased +interest in language documentation. Where such identifiers are not +available or not standardized, these Guidelines recommend a method for +documenting language identifiers and their significance, in the same +way as other metadata is documented in the TEI header.

+

Standardization of the means available to represent characters and +scripts has moved on considerably since the publication of the first +version of these Guidelines. At that time, it was essential to +explicitly document the characters and encoded character sets used by +almost any digital resource if it was to have any chance of being +usable across different computer platforms or environments, but this +is no longer the case. With the availability of the Unicode standard, +more than 128,000 different characters representing almost all of the world's +current writing systems are available and usable in any XML processing +environment without formality. Nevertheless, however large the number +of standardized characters, there will always be a need to encode +documents which use non-standard characters and glyphs, particularly +but not exclusively in historical material. The second part of +this chapter discusses in some detail the concepts and +practice underlying this standard, and also introduces the methods +available for extending beyond it, which are more fully discussed in +.

+ +
Language Identification + +

Identification of the language a document or part thereof is +written in is a crucial requirement for many envisioned usages of +an electronic document. The TEI therefore accommodates this need in the +following way: + A global attribute xml:lang is defined for all TEI + elements. Its value identifies the language and writing system + used. + The TEI header has a section set aside for the information + about the languages used in a document: see further . +

+

The value of the attribute xml:lang identifies the +language (and, optionally, script) using a coded value. For maximal compatibility with existing +processes, the identifier for the language must be constructed as in +Best Current Practice 47Currently +BCP 47 comprises two Internet Engineering Task Force documents, +referred to separately as RFC 5646 and RFC 4647; over time, other IETF +documents may succeed these as the best current practice.. This +same identifier has to be used to identify +the corresponding language element in the TEI header, if one +is present.

+

The first part of BCP 47 is called Tags for Identifying +Languages, and proposes the following mechanism for +constructing an identifier (tag) for languages as administered by the +Internet Assigned Numbers Authority (IANA). The tag is assembled from +a sequence of subtags separated by the hyphen (-, U+002D) character. +It gives the language (possibly further identified with a +sublanguage), a script, and a region for the language, each possibly +followed by a variant subtag.

+

The authoritative list of registered subtags is maintained by IANA +and is available at . +For a good general overview of the construction of language tags, see +, +and for a practical step-by-step guide, see .

+

In addition to the list of registered subtags, BCP 47 provides +extensions that can be employed by private convention. The constructs +provided can thus be used to generate identifiers for any language, +past and present, in any usage in any area of the world. If such +private extensions are used within the context of the TEI, they should +be documented within the language element of the TEI header, +which might also provide a prose description of the language described +by the language tag.

+ +

While language, region, and script can be adequately identified +using this mechanism, there is only very rough provision to express a +dimension of time for the language of a document; those codes provided +(e.g. grc for Greek, Ancient (to 1453)) might not +reflect the segments appropriate for a text at hand. Text encoders +might express the time window of the language used in the document by +means of the extension mechanism defined in BCP 47 and relate that +to a date element in the corresponding language +section of the TEI header.

+

Equivalences to language identifiers by other authorities can be +given in the language section as well, but no formal +mechanism for doing so has been defined.

+

The scope of the language identification extends to the whole +subtree of the document anchored at the element that carries the +xml:lang attribute, including all elements and those +attributes, if any, where a language might apply.This excludes all attributes where a non-textual +datatype has been specified, for example tokens, boolean values, +dates, and predefined value lists.

+ +
+ Characters and Character Sets +

All document encoding has to do with representing one thing by + another in an agreed and systematic way. Applied to the smallest + distinctive units in any given writing system, which for the + moment we may loosely call characters, such representation + raises surprisingly complex and troublesome issues. The reasons + are partly historical and partly to do with conceptual + unclarities about what is involved in identifying, encoding, + processing and rendering the characters of a natural + language.

+
+ Historical Considerations +

When the first methods of representing text for storage or + transmission by machines were devised, long before the + development of computers, the overriding aim was to identify the + smallest set of symbols needed to convey the essential semantic + content, and to encode that symbol set in the most economical + way that the storage or transmission media allowed. The initial + outcome were systems that encoded only such content as could be + expressed in uppercase letters in the Latin script, plus a few + punctuation marks and some control characters needed to + regulate the storage and transmission devices. Such encodings, + originally developed for telegraphy, strongly influenced the way + the pioneers of computing conceived of and implemented the + handling of text, with consequences that are with us still.

+

For many years after the invention of computers, the way they + represented text continued to be constrained by the imperative + to use expensive resources with maximal efficiency. Even when + storage and processing costs began their dramatic fall, the + Anglo-centric outlook of most hardware designers and software + engineers hampered initiatives to devise a more generous and + flexible model for text representation. The wish to retain + compatibility with legacy data was an additional disincentive. + Eventually, tension in East Asia between commitment to + technological progress and the inability of existing computers + to cope with local writing systems led to decisive developments. + Japanese, Korean, and Chinese standards bodies, who long before + the advent of computers had been engaged in the specification of + character sets, joined with computer manufacturers and software + houses to devise ways of mapping those character sets to numeric + encodings and processing the resulting text data.

+

Unfortunately, in the early years there was little or no + co-ordination among either the national standards bodies or the + manufacturers concerned, so that although commercial necessity + dictated that these various local standards were all compatible + with the representation of US-American English, they were not + straightforwardly compatible with one another. Even within Japan + itself there emerged a number of mutually incompatible systems, + thanks to a mixture of commercial rivalry, disagreements about + how best to manage certain intractable problems, and the fact + that such pioneering work inevitably involved some false starts, + leading to incompatibilities even between successive products of + the same bodies. Roughly at the same time, and for similar + reasons, multiple and incompatible ways of representing + languages that use Cyrillic scripts were devised, along with + methods of encoding ancient writing systems which inevitably + could not aim for compatibility with other writing systems apart + from basic Latin script. Many of the earliest projects that fed + into the TEI were shaped in this developmental phase of the + computerized representation of texts, and it was also the + context in which SGML was devised and finalized.

+

SGML had of necessity to offer ways of coping with multiple + writing systems in multiple representations; or rather, it + provided a framework within which SGML-compliant applications + capable of handling such multiple representations might be + developed by those with sufficient financial and personnel + resources (such as are seldom found in academia). Earlier + editions of these Guidelines offered advice on character set and + writing system issues addressed to the condition of those for + whom SGML was the only feasible option. That advice is here + substantially altered because of two closely-related + developments: the availability of the ISO/Unicode character set + as an international standard, and the emergence of XML and + related technologies which are committed to the theory and + practice of character representation which Unicode embodies. +

+
Terminology and Key + Concepts

Before the significance of Unicode and the + implications of the association between XML and Unicode can be + adequately explained, it is necessary to clarify some key + concepts and attempt to establish an adequately precise + terminology for them.

+

+ + Examples of the latin a, in both lower and upper case, rendered with different fonts. + Examples of the latin a, in both lower and upper case, rendered with different fonts. +

+

+ The word character will not of itself take us + very far towards greater terminological precision. It tends to be + used to refer indiscriminately both to the visible symbol on a + page and to the letter or ideograph which that symbol represents, + two things that it is essential to keep conceptually distinct. The + visible symbol obviously has some aspects by which we interpret it + as representing one character rather than another; but its + appearance may also be significantly determined by features that + have no effect on our notion of which character in a writing + system it represents. A familiar instance is the lowercase + a, which in printed texts may be + represented either by a single storey symbol + (cf. figure 1 in the examples from + URW Gothic L on the bottom row) or by a two + storey version (as in figure + 1 in the examples from Umpush, or URW Bookman L Demi Bold). + We say that the single and double-storey symbols both represent + one and the same the same abstract + character a using two different + glyphs. Similarly, an uppercase + A in a serif typeface has additional + strokes that are absent from the same letter when printed using a + sans-serif typeface, so that once again we have differing glyphs + standing for the same abstract character. The distinction + between abstract characters and glyphs is fundamental to all + machine processing of documents.

+

In most scholarly encoding projects, the accurate recording of + the abstract characters which make up the text is of prime + importance, because it is the essential prerequisite of + digitizing and processing the document without semantic loss. In + many cases (though there are important exceptions, to be touched + on shortly) it may not be necessary to encode the specific + glyphs used to render those abstract characters in the original + document. An encoding that faithfully registers the abstract + characters of a document allows us to search and analyse our + document's content, language, and structure, and to access its full + semantics. That same encoding, however, may not contain + sufficient information to allow an exact visual representation + of the glyphs in the source text or manuscript to be recreated. +

+

The importance of this distinction between information content + and its visual representation is not always immediately apparent + to people unused to the specific complexities of text handling + by machine. Such users tend to ask first what (in order of + conceptual priority) should actually be their very last + question: how do I get a physical image that looks like + character x in my source document to appear on to the screen or + the output page? Their first question should in fact be: how can + I get an abstract representation of character x into my encoded + document in a way that will be universally and unambiguously + identifiable, no matter what it happens to look like in printout + or on any particular display? And occasionally the response they + receive as a result of their misguided initial question is a + custom solution that satisfies their + immediate rendering wishes at the price of making their + underlying document unintelligible to other users (or even to + the original user in other times and places) because it encodes + the abstract character in an idiosyncratic way.

+

That said, there will certainly be documents or projects where + it is a matter of scholarly significance that the compositor or + scribe chose to represent a given abstract character using one + particular glyph or set of strokes rather than a + semantically-equivalent but visually distinct alternative, and + in that case the specific appearance of the form will have to be + encoded in one way or another. But that encoding need not (and + in most cases will not) involve a notation that visually + resembles the original, any more than italicized text in an + original document will be represented by the use of italic + characters in the encoded version.

+

A collection of the abstract characters needed to represent + documents in a given writing system is known as a +character set, and the character set or + character repertoire of a processing or + rendering device is the set of abstract characters that it is + equipped to recognize and handle appropriately. There is, + however, a subtle distinction between these two parallel uses of + the same term, involving one more key concept which it is + essential to grasp. The character set of a document (or the + writing system in which it is recorded) is purely a collection + of abstract characters. But the character set of a computing + device is a set of abstract characters which have been mapped in + a well-defined way to a set of numbers or code points + by which the device represents + those abstract characters internally. It can therefore be + referred to as a coded character set, + meaning a set of abstract characters each of which has been + assigned a numerical code point (or in some instances a sequence + of code points) which unambiguously identifies the character + concerned.

+

It is now possible to use this terminology to + say what Unicode is: it is a coded character set, devised and + actively maintained by an international public body, where each + abstract character is identified by a unique name and assigned a + distinctive code point.Although only Unicode + is mentioned here explicitly, it should be noted that the + character repertoire and assigned code points of Unicode and + the ISO standard 10646 are identical and maintained in a way + that ensures this continues to be the case. Unicode is + distinguished from other coded character sets by its + (current and potential) size and scope; its built-in provision + for (in practical terms) limitless expansion; the range and + quality of linguistic and computational expertise on which it + draws; the stability, authority, and accessibility it derives + from its status as an international public standard; and, + perhaps most importantly, the fact that today it is implemented + by almost every provider of hardware and software platforms + worldwide.

+
+ Abstract Characters, Glyphs, and Encoding Scheme + Design +

The distinction between abstract characters and glyphs can be + crucial when devising an encoding scheme. When performing + searches, text retrieval, or creating concordances, users of + electronic text will expect the system to recognize and treat + different glyphs as instances of the same character; but when + perusing the text itself they may well expect to see glyph variants + preserved and rendered. When encoding a pre-existing text, the + encoder should determine whether a particular + letter or symbol is a character or a glyphic variant. The Unicode + Consortium and an ISO work group (ISO/IEC JTC1 + SC2/WG2) have developed a detailed model of the relationship + between characters and glyphs. This model, presented in Unicode Technical + Report 17: Character Encoding Model, is the underpinning + of much standards work since, including the current chapter.

+

The model makes explicit the distinction between two different + properties of the components of written language: + + their content, i.e. its meaning and phonetic value + (represented by characters) their graphical + appearance (represented by glyphs). + +

+

When searching for information, a system generally operates + on the content aspects of characters, with little or no + attention to their appearance. A layout or formatting process, + on the other hand, must of necessity be concerned with the exact + appearance of characters. Of course, some operations + (hyphenation for example) require attention to both kinds of + feature, but in general the kind of text encoding described in + these Guidelines tends to focus on content rather than + appearance (see further ).

+

An encoder wishing to record information about which glyphs + are present in a given document may do so at either or both of + two levels: + + the level of character encoding, using an appropriate + Unicode code point to represent the glyph concerned + the markup level, with the glyph indicated via + appropriate elements or attributes +

+

The encoding practice adopted may be guided by, among other + things, an assessment of the most frequent uses to which the + encoded text will be put. For example, if recognition of + identical characters represented by a variety of glyphs is the + main priority, it may be advisable to represent the glyph + variations at markup level, so that the character value can be + immediately exposed to the indexing and retrieval software. + Plainly, an encoding project will need to consider such issues + carefully and document the outcome of their + deliberations in their TEI customization file (or other local + encoding documentation) to ensure encoding consistency. Using + Unicode code points to represent glyph information requires that + such choices be documented in the TEI header. Such documentation + cannot of itself guarantee proper display of the desired + glyph but at least makes the intention of the encoder + discoverable.

+

At present the Unicode Standard does not offer detailed + specifications for the encoding of glyph variations. These + Guidelines do give some recommendations; some discussion of + related matters is given in , + and offers some features for the definition of variant + glyphs.

+
+
+ Entry of Characters +

The entry of characters was much more complicated before the near-universal + adoption of Unicode, for which there are Input Method Editors + (IMEs) available in most languages and fonts that provide glyphs for the full + range of the Unicode specification. In those rare situations where there is + difficulty entering the specific character you want, or some problem representing + it on the system you are working in, Numeric Character References + (NCRs) should be used. These take the general form &#D; where + D is an integer representing the code point of the character in + base 10, or &#xH;, where H is the code point in + hexadecimal notation. Every XML processor is capable of recognising NCRs and + replacing them with the required code point value without needing access to + any additional data. The disadvantage of NCRs as a means of entering, + representing and proofing character data is that most human beings find them + anything but readable and it is all too easy + for the wrong character to be entered in error and retained undetected. + Where characters are not defined in Unicode, these Guidelines provide advice + on the strategies available for handling their representation in Chapter 25 Representation of non-standard Characters and + Glyphs.

+
+
+ Output of Characters +

The rendering of the encoded text is a complicated process that + depends largely on the purpose, external requirements, local + equipment and so forth, it is thus outside the scope of coverage + for these Guidelines.

+

It might however nevertheless be helpful to put some of the + terminology used for the rendering process in the context of the + discussion of this chapter. As was mentioned above, Unicode + encodes abstract characters, not specific glyphs. For any + process that makes characters visible, however, concrete, + specifically designed glyph shapes have to be used. For a printing + process, for example, these shapes + describe exactly at which point ink has to be put on the paper + and which areas have to be left blank. If we want to print a character + from the Latin script, besides the selection of + the overall glyph shape, this process also requires that a + specific weight of the font has been selected, a specific size + and to what degree the shape should be slanted. Beyond + individual characters, the overall typesetting process also + follows specific rules of how to calculate the distance between + characters, how much whitespace occurs between words, at which + points line breaks might occur and so forth.

+

If we concern ourselves only with the rendering process of the + characters themselves, leaving out all these other parameters, we + will realize that of all the information required for this process, only a small + amount will be drawn from the encoded text itself. This + information is the code point used to encode the character in the + document. With this information, the font selected for printing + will be queried to provide a glyph shape for this character. + Some modern font formats (e.g. OpenType) implement a + sophisticated mapping from a code point to the glyph selected, + which might take into account surrounding characters (to create + ligatures where necessary) and the language or even area this character is + printed for to accommodate different typesetting traditions and + differences in the usage of glyphs.

+

A TEI document might provide some of the information that is + required for this process, for example by identifying the + linguistic context with the xml:lang attribute. The + selection of fonts and sizes is usually done in a stylesheet, + while the actual layout of a page is determined by the + typesetting system used. Similarly, if a document is rendered + for publication on the Web, information of this kind can be + shipped with the document in a stylesheet.The World Wide + Web Consortium provides recommendations for two standard + stylesheet languages: either CSS or + XSL could be used for this purpose.

+
+
Unicode and + XML +

XML was designed with Unicode in mind as its means of representing + abstract characters. It is possible to use other character encoding + schemes, but in general they are best avoided, as you run the risk + of encountering compatibility issues with different XML processors, + as well as potential difficulties with rendering their output. We + recommend using the UTF-8 encoding, which for the Basic + Latin range is identical to ASCII, and which uses a variable-length + set of bytes to represent characters. It should be noted that it is + not sufficient simply to declare in the XML Declaration that a document + is in UTF-8 format. Doing so merely means that processors will treat the + content therein as if it were UTF-8, and may fail to process the + document if it is not. For further discussion of UTF-8, see the + section below on .

+
+
+ Special Aspects of Unicode Character Definitions +
+ Compatibility Characters +

The principles of Unicode are judiciously tempered with + pragmatism. This means, among other things, that the actual + repertoire of characters which the standard encodes, especially + those parts dating from its earlier days, include a number of + items which on a strict interpretation of the Unicode + Consortium's theoretical approach should not have been regarded + as abstract characters in their own right. Some of these + characters are grouped together into a + code-point regions assigned to compatibility characters. + Ligatures are a case in point. Ligatures (e.g. the joining of + adjacent lowercase letters s and t or f and i in Latin + scripts, whether produced by a scribal practice of not lifting + the pen between strokes or dictated by the aesthetics of a type + design) are representational features with no added semantic + value beyond that of the two letters they unite (though for + historians of typography their presence and form in a given + edition may be of scholarly significance). However, by the time + the Unicode standard was first being debated, it had become + common practice to include single glyphs representing the more + common ligatures in the repertoires of some typesetting devices + and high-end printers, and for the coded character sets built + into those devices to use a single code point for such glyphs, + even though they represent two distinct abstract characters. So + as to increase the acceptance of Unicode among the makers and + users of such devices, it was agreed that some such + pseudo-characters should be incorporated into the standard as compatibility characters. + Nevertheless, if a project requires the presence of such + ligatured forms to be encoded, this should normally be done via + markup, not by the use of a compatibility character. That way, + the presence of the ligature can still be identified (and, if + desired, rendered visually) where appropriate, but indexing and + retrieval software will treat the code points in the document as + a simple sequential occurrence of the two constituent characters + concerned and so correctly align their semantics with + non-ligatured equivalents. Such ligatures should not be confused + with digraphs (usually) indicating diphthongs, as in the French + word "cœur". A digraph is an atomic orthographic unit + representing an abstract character in its own right, not purely an amalgamation + of glyphs, and indexing and retrieval software will need to + treat it as such. Where a digraph occurs in a source text, it + should normally be encoded using the appropriate code point for + the single abstract character which it represents.

+
+ Precomposed and Combining Characters and + Normalization +

The treatment of characters with + diacritical marks within Unicode shows a similar combination of + rigour and pragmatism. It is obvious enough that it would be + feasible to represent many characters with diacritical marks in + Latin and some other scripts by a sequence of code points, where + one code point designated the base character and the remainder + represented one or more diacritical marks that were to be + combined with the base character to produce an appropriate + glyphic rendering of the abstract character concerned. From its + earliest phase, the Unicode Consortium espoused this view in + theory but was prepared in practice to compromise by assigning + single code points to precomposed characters which were + already commonly assigned a single distinctive code point in + existing encoding schemes. This means, however, that for quite a + large number of commonly-occurring abstract characters, Unicode + has two different, but logically and semantically equivalent + encodings: a precomposed single code point, and a code point + sequence of a base character plus one or more combining + diacritics. Scripts more recently added to Unicode no longer + exhibit this code-point duplication (in current practice no new + precomposed characters are defined where the use of combining + characters is possible) but this does nothing to remove the + problem caused by the duplications from older character sets that + have been permanently embodied in Unicode. Together with essentially analogous + issues arising from the encoding of certain East Asian + ideographs. This duplication gives rise to the need to practice + normalization of Unicode documents. Normalization is + the process of ensuring that a given abstract character is represented in one + way only in a given Unicode document or document collection. + The Unicode Consortium provides four standard normalization + forms, of which the Normalization Form C (NFC) + seems to be most appropriate for text encoding projects. The NFC, as + far as possible, defines conversions for all base characters followed + by one or more combining characters into the corresponding precomposed + characters. The World Wide Web Consortium has produced a document entitled + Character Model for the World Wide Web 1.0Available at + ., which among other things + discusses normalization issues and outlines some relevant + principles. An authoritative reference is Unicode Standard Annex + #15 Unicode Normalization Formsavailable at + .

+

It is important that every Unicode-based project should agree + on, consistently implement, and fully document a comprehensive and + coherent normalization practice. As well as ensuring data integrity + within a given project, a consistently implemented and properly + documented normalization policy is essential for successful + document interchange. While different input methods may themselves differ + in what normalization form they use, any programming language that implements Unicode + will provide mechanisms for converting between normalization forms, so it + is easy in practice to ensure that all documents in a project are in a consistent form, + even if different methods are used to enter data.

+
+
+ Character Semantics +

In addition to the Universal Character Set itself, the + Unicode Consortium maintains a database of additional character + semantics. This + includes names for each character code point and normative + properties for it. Character properties, as given in this + database, determine the semantics and thus the intended use of a + code point or character. The database also contains information that might be + needed for correctly processing this character for different + purposes. It is an important reference in determining which Unicode + code point to use to encode a certain character.

+

In addition to the printed documentation and lists made + available by the Unicode consortium, the information it contains + may also be accessed by a number of search systems over the Web + (e.g. ). Examples of + character properties included in the database include case, numeric + value, directionality, and, (where applicable) status as a + compatibility characterFor + further details, see The Unicode Character Property + Model (Unicode Technical Report #23), at .. Where a + project undertakes local definition of characters with code points + in the PUA, it is desirable that any relevant additional + information about the characters concerned should be recorded in an + analogous way, as further discussed under .

+
+
+
+ Issues Arising from the Internal Representations of + Unicode +

In theory it should not be necessary for encoders to have any + knowledge of the various ways in which Unicode code points can + be represented internally within a document or in the memory of + a processing system, but experience shows that problems + frequently arise in this area because of mistaken practice or + defective software, and in order to recognize the resulting + symptoms and correct their causes an outline knowledge of + certain aspects of Unicode internal representation is desirable. + There are three encodings of Unicode available for use: UTF-8, which + uses 1–4 bytes per character, UTF-16, which uses 2–4, and UTF-32, + which uses 4 bytes per character. Current practice for documents to + be transmitted via the Web recommends only UTF-8.See the W3C + Internationalization document, Choosing & applying a + character encoding at + +

+
+ Encoding Errors Related to UTF-8 +

The code points assigned by Unicode 3.0 and later are + notionally 32-bit integers, and the most straightforward way to + represent each such integer in computer storage would be to use + 4 eight-bit bytes. However, many of the code points for + characters most commonly used in Latin scripts can be + represented in one byte only and the vast majority of the + remainder which are in common use (including those assigned + from the most frequently used PUA range) can be expressed in + two bytes alone. This accounts for the use of UTF-8 and UTF-16 + and their special place in the XML standard. UTF-8 and UTF-16 + are ways of representing 32-bit code points in an economical + way.

UTF-8 is a variable length encoding: the more + significant bits there are in the underlying code point (or in + everyday terminology the bigger the number used to represent + the character), the more bytes UTF-8 uses to encode it. What + makes UTF-8 particularly attractive for representing Latin + scripts, explaining its status as the default encoding in XML + documents, is that all code points that can be expressed in + seven or fewer bits (the 127 values in the original ASCII + character set) are also encoded as the same seven or fewer bits + (and therefore in a single byte) in UTF-8. That is why a + document which is actually encoded in pure 7-bit ASCII can be + fed to an XML processor without alteration and without its + encoding being explicitly declared: the processor will regard + it as being in the UTF-8 representation of Unicode and be able + to handle it correctly on that basis.

+

However, even within the domain of Latin-based scripts, some + projects have documents which use characters from 8 bit + extensions to ASCII, e.g. those in the ISO-8859-n series of + encodings, and the way characters which under ISO-8859-n use + all eight bits are encoded in UTF-8 is significantly different, + giving rise to puzzling errors. Abstract characters that have a + single byte code point where the + highest bit is set (that is, they have a decimal numeric + representation between 129 and 255) are encoded in ISO-8859-n + as a single byte with the same value + as the code point. But in UTF-8 code-point values inside that + range are expressed as a two byte + sequence. That is to say, the abstract character in question is + no longer represented in the file or in memory by the same number + as its code-point value: it is transformed (hence the T in + UTF) into a sequence of two different numbers. Now as a + side-effect of the way such UTF-8 sequences are derived from + the underlying code-point value, many of the single-byte + eight-bit values employed in ISO-8859-n encodings are illegal + in UTF-8.

+

This complicated situation has a simple consequence which can + cause great bewilderment. XML processors will effortlessly + handle character data in pure 7-bit ASCII without that encoding + needing to be declared to the parser, and will similarly accept + documents encoded in an undeclared ISO-8859-n encoding if they + happen to use no characters outside the strict ASCII subset of + the ISO character sets; but the parse will immediately fail if + an eight-bit character from an ISO-8859-n set is encountered in + the input stream, unless the document's encoding has been + explicitly and correctly declared. Explicitly declaring the + encoding ought to solve the problem, and if the file is + correctly encoded throughout, it will do so. But projects dealing + with documents of sufficient age may find that they have to deal with some files encoded + in UTF-8 along with others in, say, ISO-8859-1. Such encoding + differences may go unnoticed, especially if the proportion of + characters where the internal encodings are distinguishable is + relatively small (for example in a long English text with a + smattering of French words). These types of error may or may not + manifest in actual processing errors, and may only become visible + as garbage characters in the eventual display of documents.

+

In projects that routinely handle documents in non-Latin + scripts, everyone is well aware of the need to ensure correct + and consistent encoding, so in such places mixed encoding + problems seldom arise, and when they do are readily identified + and remedied. Real confusion tends to arise, however, in + projects which have a low awareness of the issues because they + employ predominantly unaccented Latin characters, with only + thinly-distributed instances of accented letters, or other + special characters where the internal representation under + ISO-8859-n and UTF-8 are different (such as the copyright + symbol, or, a frequent troublemaker where eventual HTML output + is envisaged, the non-breaking space). Even, or especially, + if such projects view themselves as concerned only with + English documents, the close relationship between XML and + Unicode means they will need to acquire an understanding of + these encoding issues and develop procedures which assure + consistency and integrity of encoding and its correct + declaration, including the use of appropriate software for + transcoding and verification.

+
+
+
diff --git a/P5/Source/Guidelines/fr/CO-CoreElements.xml b/P5/Source/Guidelines/fr/CO-CoreElements.xml deleted file mode 120000 index 5c5b56dfe0..0000000000 --- a/P5/Source/Guidelines/fr/CO-CoreElements.xml +++ /dev/null @@ -1 +0,0 @@ -../en/./CO-CoreElements.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/CO-CoreElements.xml b/P5/Source/Guidelines/fr/CO-CoreElements.xml new file mode 100644 index 0000000000..b4a7aebc95 --- /dev/null +++ b/P5/Source/Guidelines/fr/CO-CoreElements.xml @@ -0,0 +1,6013 @@ + + + + +
+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 , 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 ) 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 ) and features commonly marked by quotation marks +(section ) as well as such features as terms, +cited words, and glosses (section ).

+ +

Section 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 ), +which should be adequate to most commonly encountered situations.

+ +

The next section (section ) 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 ), numbers and measures (section ), dates and times (section ), abbreviations (section ), and addresses (section ).

+ +

In the same way, the following section (section ) 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 ; the tags presented here +are intended to be usable for a wide variety of simple +applications.

+ +

Sections , and , 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 ) is discussed.

+

Section 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 and .

+

Next, section , 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 , 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 .

+

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 , describing the structure of +the TEI document type definition.

+
Paragraphs +

Paragraphs in modern printed or online text are typically visually + offset with whitespace or an indented first line. But paragraphs are + not simply blocks of text. The paragraph may be thought of as a mid-level + unit of sense, a coherent grouping of sentences. Paragraphs may, in turn, + be grouped into larger divisions, such as chapters. Because it is a unit + of sense rather than simply a block of text, the p element in TEI + may contain other structures displayed as blocks, such as lists or quotes. + This distinguishes it from the p + element in HTML, which is primarily a block of text, and from the ab + (anonymous block) element described in which may be used + as an alternative to the paragraph in cases that require a chunk-level container + which is not necessarily a sense unit and which may have different structural properties.

+

The paragraph can be understood in the context of the distinct forms of textual + division discussed in : chunk, + phrase, and inter-level. + Chunk-level elements are paragraphs and other elements which have similar + structural properties. Phrase-level elements must be entirely contained within a + paragraph or other chunk-level structure. This type includes emphasized or quoted + phrases, names, dates, etc. Inter-level elements can appear either within a + paragraph or between paragraphs, and include bibliographic citations, notes, and + lists. The ab (anonymous block) element is an alternative to + p which is useful in cases where paragraphs are not present, but chunk-level + organization is still needed. ab may contain other abs, + may use the type attribute, and does not necessarily represent a coherent set of + statements.

+

Paragraphs can contain many of the other elements described within this chapter, + as well as other elements which are specific to individual text types. Because + paragraphs may appear in different customizations, their possible + contents may vary in different kinds of documents. In particular, additional + elements not listed in this chapter may appear in paragraphs. However, + the elements described in this chapter are available + in all kinds of text unless they are excluded by a customization.

+

The paragraph is marked using the p element: +

+

If a consistent internal subdivision of paragraphs is desired, the +s or seg (segment) elements may +be used, as discussed in chapters and +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.

+

The following example demonstrates a basic application of the p tag for an indented passage in a printed book: + +

It is in vain to say human beings ought to be satisfied with tranquillity: + they must have action; and they will make it if they cannot find it. Millions are + condemned to a stiller doom than mine, and millions are in silent revolt against + their lot. Nobody knows how many rebellions besides political rebellions ferment + in the masses of life which people earth. Women are supposed to be very calm + generally: but women feel just as men feel; they need exercise for their faculties, + and a field for their efforts, as much as their brothers do; they suffer from + too rigid a restraint, too absolute a stagnation, precisely as men would suffer; and + it is narrow-minded in their more privileged fellow-creatures to say that they ought to + confine themselves to making puddings and knitting stockings, to playing on the piano + and embroidering bags. It is thoughtless to condemn them, or laugh at them, if they + seek to do more or learn more than custom has pronounced necessary for their sex.

+ +

+

This news story shows typically short journalistic paragraphs: +SARAJEVO, Bosnia and Herzegovina, April 19

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.

+

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.

+

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.

+

...

+

+

The following extract from a Russian fairy tale demonstrates +how other phrase level elements (in this case q elements +representing direct speech; see section ) +may be nested within, but not across, paragraphs: +

A fly built a castle, a tall and mighty castle. +There came to the castle the Crawling Louse. Who, +who's in the castle? Who, who's in your house? +said the Crawling Louse. I, I, the Languishing Fly. +And who art thou?I'm the Crawling Louse. +

+

Then came to the castle the Leaping Flea. Who, +who's in the castle? said the Leaping Flea. I, +I, the Languishing Fly, and I, the Crawling Louse. And +who art thou?I'm the Leaping Flea. +

+

Then came to the castle the Mischievous Mosquito. +Who, who's in the castle? said the Mischievous +Mosquito. I, I, the Languishing Fly, and I, the +Crawling Louse, and I, the Leaping Flea. And who art +thou?I'm the Mischievous Mosquito. +

+

+ + + + + +
+
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 +. Where the character used for a punctuation mark +is not available in Unicode, the g element and other facilities described in +chapter may also be used to mark its presence.

+ +
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 , , +and 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 . +

+

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 , and section , + 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 .

+ +

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 . +

+

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. +

+ +
+ +
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: 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 ). + tea-pot + + +A similar range of possibilities applies equally to the representation of +other common punctuation marks, notably quotation marks, as discussed +in .

+ +

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 , or the more sophisticated mechanisms for +linguistic analysis discussed in chapter . +

+
+
+ + +
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. +

+
What Is Highlighting? +

By highlighting we mean the use of any +combination ofhighlighting typographic +features (font, size, hue, etc.) in a printed or written text in order +to distinguish some passage of a text from its surroundings.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 +. 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 ). 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. + + + +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 (). 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 . +

+ +

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 ) and name (discussed +in section ). +

+
Emphasis, Foreign Words, and Unusual Language +

This subsection discusses the following elements: + +These elements are all members of the model.emphLike class.

+
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 and 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. +Aren't you confusing post hoc with propter +hoc? said the Bee Master. Wax-moth only succeed when +weak bees let them in. +

+ +

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 below. Compare the +following example sentences: +John eats a croissant every morning. +Croissant is difficult to +pronounce with your mouth full. +A croissant 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

+ + + + +
+
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: Sex, sir, is purely a question +of appetite! 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: What it all comes to is this, he said. +What does Christopher Robin do in the morning +nowadays? 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: What it all comes to is this, he said. +What does Christopher Robin do in +the morning nowadays? +

+

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: +Here Thou, great Anna! + whom three Realms obey, +Doth sometimes Counsel take — + and sometimes Tea. + +font-style: italic + +Further information on the use of the rendition element is +provided at .

+ + +

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: +And this Indenture further witnesseth +that the said Walter Shandy, 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 came down handsomely, and Scrooge never +did. In this example, the phrase came +down uses inverted commas to indicate a play on +words.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. + +In a second pass, the element soCalled might be preferred as +a means of indicating that the narrator is distancing himself from +this usage. +

+ + + + +
+
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,diachronic information +for example as archaic, old-fashioned, contemporary, futuristic, etc.; +the space attribute places a word or phrase +diatopically,diatopic information +that is, with respect to a geographical classification, for example as +national, regional, international, etc.; the social attribute +places a word or phrase diastratically,diastratic information +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 ). +

+

Examples: +Next morning a boy in that dormitory confided to his +bosom friend, a fag of +Macrea's, that there was trouble in their midst which +King would fain keep +secret. + +Next morning a boy in that dormitory confided to his +bosom friend, a +fag +of Macrea's, that there was trouble in their midst which +King would fain 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 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 , or the +span element described in section . +

+ + + +
+
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: + + + + + + + + + +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 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 ). 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 : + — Alors, Albert, quoi de neuf? + — Pas grand-chose. + — Il fait beau, 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 : + Alors, + Albert, quoi de neuf ? + Pas grand-chose. + Il fait beau, + dit Robert. + +content: '— ' + + +

+ +

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 ) 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: + + Who-e debel + you? — he at last said — + you no speak-e, + damme, I kill-e. 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 . 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: + + +Who-e debel + you? — he at last said — + you no speak-e, + damme, I kill-e. And so saying, + the lighted tomahawk began flourishing + about me in the dark. + + + content:"‘"; + content:"’"; + + +

+ + + +

As members of the att.ascribed.directed class, + elements said and q share the following attributes: + +These may be used to make explicit who is speaking and who is being spoken to: + Adolphe se tourna vers lui : + — Alors, Albert, quoi de neuf? + — Pas grand-chose. + — Il fait beau, dit Robert. + + + + Adolphe + Albert + Robert + + + + + 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 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: + Oh yes, said Henry, I mean + Gordon Macrae, for example… Jungian + Analyst with Winebox! That's what you called him, you callous bastard, + didn't you? Eh? Eh? +

+

Quoted matter may be embedded within quoted matter, as when one + speaker reports the speech of another: + Spaulding, he came down into the office just this day + eight weeks with this very paper in his hand, and he says:— + I wish to the Lord, Mr. Wilson, that I was a + red-headed man. + + + Wilson + Spaulding reported by Wilson + + +

+

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: +

The Lord! The Lord! It is Sakya Muni himself, the lama half + sobbed; and under his breath began the wonderful Buddhist + invocation:- + + To Him the Way — the Law — Apart — + Whom Maya held beneath her heart + Ananda's Lord — the Bodhisat + + And He is here! The Most Excellent Law is here also. My + pilgrimage is well begun. And what work! What work! +

+

+

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 , as in the following example. +

+ Chapter 1 + + + Since I can do no good because a woman + Reach constantly at something that is near it. + + + The Maid's Tragedy + Beaumont and Fletcher + + +

Miss Brooke had that kind of beauty which seems to be thrown into + relief by poor dress...

+
+ 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, + You shall know a word by the company it keeps. + (Firth, 1957) + + + 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: + + Tolkien (1936) tells us that +Beowulf is in fact so interesting as +poetry, in places poetry so powerful, that this quite +overshadows the historical content. + + 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 .

+

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: + PM dodges election threat in interview +

+

The same element should be used to mark a variety of special ironic + usages. Some further examples follow: + He hated good books. + Croissants 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 + social justification. It was commonly assumed in + works on logic until fairly recently that the notion + language is necessarily restricted to finite + strings. +

+ + + + + + + + +
+ +
+
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.

+ +
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 (formentionvs. useusevs. mention + example, as examples) rather than used may + mark them either with italics or with quotation marks, and will gloss + them less regularly. + + + + 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 discoursal point of view + as the relationship, expressed through discourse + structure, between the implied author or some other addresser, + and the fiction. + + A computational device that infers + structure from grammatical strings of words is known as a + parser, 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 discoursal point of view 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 .

+

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 eluthemen + we were released, accented on the + second syllable of the word, and its participial derivative + lutheis released, 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 below are available on the + term element for this purpose. +

+ + + + + + +
Some Further Examples +

As a simple example of the elements discussed here and in + , 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 Nibelungenlied is + associated with the new rise of romance of twelfth-century France, + the romans d'antiquité, + 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 Nibelungenlied + is associated with the new rise of romance of twelfth-century France, + the romans d'antiquité, 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 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. + + + + + + + +

+
+ + +
+ 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. +
+ +

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 (). 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: + + + + + + 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: + + + + 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: + +

+ + + 大学 + だいがく + + +

+ + + 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: + +

+ + + 大 + だい + + + 学 + がく + + +

+ + + Here is a similar example from Taiwan using bopomofo (pinyin + píngzi = bottle)Taken from Wikipedia.: + +

+ + + 瓶 + ㄆㄧㄥˊ + + + 子 + ˙ㄗ + + +

+ + + + 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 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. + +

+ + Billiard hall 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: + + +

+ + + + + 打 + ダ + + + 球 + キウ + + 場 + + ビリヤード + + +

+ + + We could also use a standoff approach with anchor elements and + pointers: + + +

+ + + + 打 + 球 + 場 + + + ビリヤード + ダ + キウ + + +

+ + + Alternatively, if the encoding itself already includes segmentation below + the word level, we can use the existing elements instead of adding anchors: + + +

+ + + 打球場 + ビリヤード + ダ + キウ + + +

+ + + Multiple ruby annotations can appear in the same alignment relative to the main text. For example, there might be two annotations on the right. We use this + instance to exemplify two ways of encoding this phenomenon, dependent on the interpretation of the text. + We could use a parallel approach where a sequence of two rt elements, both with the same value for the place attribute, are + assumed to appear in their document sequence. The first of the two rt elements would appear to the right of the ruby base (rb), while the second would appear to the right of the first rt element + Taken from Wikipedia.: + + +

+ + + ㄅ + B + 博 + + +

+ + + Alternatively, a nested approach can be used. With nested ruby elements, the structure suggests that the second rt element is glossing both the rb and the rt element: + + +

+ + + + + ㄅ + B + + + 博 + + +

+ + +

+ + + +

The rt element is a member of att.written: + + + + + so the hand attribute can be used where the ruby + text constitutes an annotation in a + different hand from the ruby base: + +

+ + Base text with a ruby gloss in a different hand. + リクシ ソウモク チョウジュウ チュウギョ ソ ズカイ。 東京大学総合図書館 (General Library in the University of Tokyo, JAPAN). +
+ + +

+ + + 蘝蔓 + ヤブカラシ + + 于野 + +

+ + +

+ +

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. While ruby is included for use with East Asian languages, + encoders may find other contexts in which these elements are useful.

+ + + + + + +
+ +
+ 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. + + + + + + Along with the gloss element mentioned above, these elements + constitute the model.identSynonyms class. + They are described in more detail in .

+
+ +
+ +
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 . +Systematic interpretive annotation is also possible using the various +methods described in chapter . 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 should be used. To encode multiple +witnesses of a particular text, a similar mechanism designed +specifically for critical editions is described in chapter .

+ +

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: + + + + + +

+ +

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: + + + +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 .

+
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. + + + + +

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 dates +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 date's +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 + + dates + date's + 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 + + dates + date's + mentioned in the main body of the text are + incorrect. + + +editor +C.M. Sperberg-McQueen + +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 ; 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 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 AutumnAntony it was, +That grew the more by reaping +See further the discussion in section .

+

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 +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 . +

+ + + + + +
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.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.

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: + + + + +

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: +

...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

Alternatively, the encoder may simply indicate that certain words +have been modernized by using the reg element with no +attributes specified, as follows:

...how godly a +deed it is to overthrow so wicked a race the +world may judge: for my part I think +there cannot be a greater +sacrifice to God.

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: +

...how godly a dededeed it is to +overthroweoverthrow so wicked a race the +world may judge: for my part I thinkethink +there canotcannot be a greater +sacryficesacrifice to God.

+

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

+ + + + +
+
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: + + + + + + +

+

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 ). In these situations — where copy text +is not transcribed due to editorial policy or because it is impossible +to do so — the gap element may be used to indicate the +omission. Attributes on the gap element optionally provide +further information about the reason for the omission, its extent, and +the person or agency responsible for it, as in the following examples: + + +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 .

+

The desc element may be used to supply a description of +the material omitted, where that is considered useful: + irrelevant commentary +… Their arrangement with respect to Jupiter and to each other was as follows: +astrological figure +That is, there were two stars on the easterly side and one to the +west; … + + + + +

+ +

The ellipsis element provides a means to encode the + deliberate, marked omission of content in a source document. Within + ellipsis, a required metamark is used to represent + the characters or markings in the source that indicate the presence + of omitted material. Encoders may optionally provide a desc + element to describe the omission, as well as a supplied + element to record the content omitted from the source at this point. + The ellipsis element could be applied to ditto marks + when they indicate repetition of the same content, as in this + example: + + + + Tent supplies + + + nylon tent + + + 1 + + + + + steel stakes + + + 6 + + + + + fiberglass poles + + + + " + 6 + + + +
+ +

+ +

The ellipsis element may also apply to literary passages + that omit the full names of places or people, leaving their + identities to the imagination of the reader, as in the next example. + +

I leave Dublin to-morrow for M—— house. It is situated in the county of ——, on the north-west coast of Connaught, which I am told is the classic ground of Ireland.

+ +

+

A manuscript of song lyrics provides a more complex example of ellipsis to encode a marked omission that begins in the middle of a verse line. +

+ + A manuscript from Cancioneiro da Biblioteca Nacional + [1525-1526] in Biblioteca Nacional de Portugal, representing + song lyrics and the beginning of a chorus. On the last line + visible in this image, a marking of three dots and a line, + ·:—, indicates that the rest of the chorus should follow + after this point. +
+ Our encoding of the passage shows the use of ellipsis with supplied to contain the omitted content. + + + Amıgas sey eu ben dunha molher + Que se trabalha de uosco buscar + Mal a uossamigo polo matar + Mays todaquestamiga ela quer + ꜒ + Por que nunca con el pode poer + Queo podesse por amigauer + + + E buscalhi con uosco quanto mal + Ela mays pode aquesto sei eu + E todaquestela faz polo seu + E poreste pẏte non por al + ꜒ + Por que nunca + + ·:— + + con el pode poer + Queo podesse por amigauer + + + + +

+

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 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),additionssupralinearinsertionssupralinearsupralinear insertions 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 of +these facts 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 , and in section +, 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: +And where the sandy mountain Fenwick scald +The sea between +yet hence his pray'r prevail'd +or from a spoken text: +

... and then marbled queen...

+

+

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: +One day I will sojourn to your shores +I live in the middle of England +But! +Norway! My soul resides in your watery +fiords fyords fiiords +Inlets. +

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: +Mein Frisch +schwebt weht der Wind

+

Deletion in manuscript or typescript is often associated with +addition: +Inviolable + Inexplicable +splendour of Corinthian white and gold +The subst element discussed in 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 ) rather than add and +del. These two sets of elements allow the encoder to +distinguish editorial changes from those visible in the source text. +

+ + + + + + + + + +
+
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 ); more detailed +treatment of abbreviations is provided by the transcription module +(see section ).

+ +
Referring Strings +

A referring string is a phrase which refers to some +person, place, object, etc. Two elements are provided to mark such +strings: + + + + +Both the name and rs elements are members of the +att.typed class, from which they inherit +the following attributes: which may be used to further +categorize the kind of object referred to.

+ +

Examples include: + +

My dear +Mr. Bennet, said his lady to +him one day, have you heard that +Netherfield Park is let at last?

+

Collectors of water-rents were appointed by the +Watering Committee. +They were paid a commission not exceeding four per +cent, and gave bond.

 +

It being one of the principles of the +Circumlocution Office never, on any +account whatsoever, to give a straightforward answer, +Mr Barnacle said, Possibly.

 +

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. +

My dear Mr. Bennet, said +his lady to him one day ...

+

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: +

My dear Mr. Bennet, said his lady to him one day, +have you heard that Netherfield Park is let at last?

+As the following example shows, a proper name may be nested within a +referring string: +His Excellency the Life President, Ngwazi Dr H. Kamuzu Banda +

+

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 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: +

+ +

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: + + My dear + Mr. Bennet, said + his lady to him one day, + have you heard that + Netherfield Park is let at +last? + + +

Mme. de Volanges + marie sa fille: + c'est encore un secret; +mais elle m'en a fait part hier.

+

+ +

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. + + +

Heathrow

+

+ +

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. + + +

Heathrow

+

+

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:

My personal life during +the administration of Col. Polk +(Polk, James K.) has but poorly compensated me for the +suspended enjoyments and pursuits of private and professional +spheres

+

+ +

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: + +

Mme. de Volanges marie sa fille: c'est encore un secret; +mais elle m'en a fait part hier.

+ +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 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: + +

+Walter de la Mare +de la Mare, Walter + +was born at Charlton, in +Kent, in 1873.

+

The index element discussed in may be +more appropriate if the function of the regularization is to provide a +consistent index: +

Montaillou is not a large parish. +At the time of the events which led to +FournierBenedict XII, Pope of Avignon (Jacques Fournier)'s +investigations, the local population consisted of between 200 and 250 inhabitants.

+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 or the +analytical tools described in chapter should be +used. +

+ + + + + +
+
Addresses + +

These Guidelines propose the following elements to distinguish +postal and electronic addresses: + + + + +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. + + +info@tei-c.org + +

+ +

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: + +Here is an example of a postal address encoded using this approach: +

+ 110 Southmoor Road, + Oxford OX2 6RB, + UK +
+

+

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: + + + + 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: + +

+ 110 Southmoor Road + Oxford + OX2 6RB + United Kingdom +
+

+ +

The order of elements within an address is highly culture-specific, +and is therefore unconstrained: +

+ Università di Bologna + Italy + 40126 + Bologna + via Marsala 24 +
+

+ +

A telephone number (normally outside of the address + element) might be tagged with an addrLine and ref + that points to the phone number using the tel URI + scheme: + + (201) 555 0123 +

+ +

For further discussion of ways of regularizing the names of places, +see section . 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 , 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: +

+ 110 Southmoor Road + Oxford + OX2 6RB + United Kingdom +
+

+ + + + + + + +
+
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: + +

+ +

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: + xxxiii +twenty-one +ten percent +10% +5th + one half +1/2 +

+ +

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: + + + +

+ +

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: + +

+Unimportant +Small and round +Green +White +yellow +Mobile +13¾" +11" + + + +
+ +In the same way, it may be convenient to mark +representations of currency which might otherwise be misinterpreted as +lexical: + +

...the sum of +12s 6d...

 +

+

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: + + + +With these attributes, the measurement of Celia's neck may be +specified in a normalized form: + +13¾" + +Such techniques are particularly useful when representing historical +data such as inventories: + + + ii bags hops + + six trusses Woolen and linen goods + + 5 tonnes coale + + +

+

In addition to normalization, the attributes of the att.ranging class may be used to supply the mininum or maximum values + of a range, or of an approximate measurement: + + + +

In a cadaver I have found it + holding more than three ounces. + [...] Then + we may suppose in man that a single heart beat + would force out either + a half ounce, three drams, + or even one dram of blood, which because of the + valvular block could not flow back that way into + the heart.

+ +

+

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: + + +xiv +v +x + + + +

+

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. + + + + + + +A measure element may contain a combination of num and unit elements: + + 1, 2, 5, 7 + millimètres + +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: + +

Light travels at 3×10^10 + + cm per second + .

+ +

+ + + + + + +
+
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: + + + + +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: + + + + +

+

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 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 . 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: + 12/2/1980 + Given on the 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. +

+

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.The datatypes are taken from the W3C Recommendation XML Schema Part 2: Datatypes Second Edition. +The permitted datatypes are: + +date +gYear +gMonth +gDay +gYearMonth +gMonthDay +time +dateTime + +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. +Some typical examples follow: + +The year 2001 +September 2001 +11 Sep 01 +9/11 +September +Eleventh of the month + +Sept 11th, 12 minutes before 9 am +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:

Those five years — +1918 to 1923 +— had been, he suspected, +somehow very important.

+ +

The Eddic poems are preserved in a unique +manuscript (Codex Regius 2365) from +the second half of the +thirteenth century, and Hervarar +saga dates from around 1300.

 +

+

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.

+ + + + + + +
+
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: + + + + +

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 CC is defined by that calibration of values which +motivates the elements of its GSP; ... +Every manufacturer of 3GL or 4GL +languages is currently nailing on OOP extensions. +

The type attribute may be used to distinguish types + of abbreviation by their function:Dr. M. Deegan is +the Director of the CTI Centre for Textual Studies. +

+

Abbreviations such as Dr. M. above may be + treated as two abbreviations, as above, or as one: Dr. M. Deegan is +the Director of the CTI 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 +World Wide Web Consortium +W3C +Nested abbreviations may also be handled in this way: + RELAX NGregular +language for XMLextensible markup +language, next +generation

+ +

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 , which includes +additional elements made available for the purpose by the transcr module.

+ + + + + +
+
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: + + + +Linkages of several other kinds are also provided for in these +guidelines; see further chapter . +

+

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: +

... +The complete XPointer specification is managed by the W3C, +, +, and +; +for a discussion of TEI schemes for XPointer, see +.

+ +
+ +
+ +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 . The complete XPointer specification is managed by the W3C, , , and ; for a discussion of +TEI schemes for XPointer, see .

+

+ +

+

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: + + + + +

+

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 section 12 on page 34. +

+

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 + + +then the same cross-reference might more exactly be encoded as + See especially section 12 on page 34. +

+

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 . +

+

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 (); 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: + + Saints aid rejected in mel. + Sallets censured + Sanguine mel. signs + Scilla or sea onyon, a purger of mel. + +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: + + +... + +... + +... + +... + +... + +

+

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 ⁵¹ + +text of annotation + +

+

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 +rewriting systems, have a long history +among mathematicians, but the specific form of +was first studied extensively by Chomsky . + +

+ + + +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 , , and , 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: + +

The current version of the TEI Guidelines source code + is available in the TEI GitHub Repository; guidelines-en.xml + is the root document used to create the English version + of these Guidelines.

+ +

+ + + + +
+
Lists +

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

+

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. + + + My first rough manuscript, without any +intermediate copy, has been sent to the press. + + 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. + +I will add two facts, which have seldom occurred in +the composition of six, or even five quartos. + + My first rough manuscript, without any +intermediate copy, has been sent to the press. + 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. + +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 + those that belong to the Emperor, + embalmed ones, + those that are trained, + suckling pigs, + mermaids, + fabulous ones, + stray dogs, + those that are included in this classification, + those that tremble as if they were mad, + innumerable ones, + those drawn with a very fine camel's-hair brush, + others, + those that have just broken a flower vase, + those that resemble flies from a distance. + +

+

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: + + Report of the conduct and progress of Ernest Pontifex. + Upper Vth form — half term ending Midsummer 1851 + Idle listless and unimproving + ditto + ditto + Orderly + + Not satisfactory, on account of his great + unpunctuality and inattention to duties + +

+

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, +tablesand +lists on which see chapter . 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: + + Unit Three — Vocabulary + bitter, harsh + field + hear, listen (to) + war + good + +Additionally, the term and gloss elements discussed +in section might be used to make explicit the role +that each column in the glossary list has, as follows: + + Unit Three — Vocabulary + + bitter, harsh + + field + + hear, listen (to) + + war + + good + +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 , and +section . 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 . +

+

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. + + TRITE + SIMPLE, STRAIGHTFORWARD + stop fighting, make peace + disorganized + friendly + completely honest + near death + +

+

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: + + + + + I am cast upon a horrible desolate island, void + of all hope of recovery. + I am singled out and separated as it were from + all the world to be miserable. + I am divided from mankind — a solitaire; one + banished from human society. + + + + + + But I am alive; and not drowned, as all my + ship's company were. + But I am singled out, too, from all the ship's + crew, to be spared from death... + But I am not starved, and perishing on a barren place, + affording no sustenances.... + + + +

+

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

+ + + + + + + + +
+
Notes, Annotation, and Indexing +
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: + +

+

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 .

+

In the following example, the type attribute is used to +categorise the note as a gloss: +The self-same moment I could pray +And from my neck so free +The albatross fell off, and sank +Like lead into the sea. +The spell begins to break + +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: +The self-same moment I could pray +And from my neck so free +The albatross fell off, and sank +Like lead into the sea. +The spell begins to break + +

+

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: +The self-same moment I could pray +And from my neck so free +The albatross fell off, and sank +Like lead into the sea. + +

+

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.We +explain below why we use the uncommon term +collection instead of the expected +set. Our usage corresponds to the +aggregate of many mathematical writings and to +the sense of class found in older logical +writings. 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: + + +The self-same moment I could pray; + +The spell begins to break +The turning point of the poem... + + +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 ; thus in this +case, the TEI header for this text might contain a +title statement like the following: + + +The Rime of the Ancient Mariner: an annotated edition +Samuel Taylor Coleridge +John Livingston Lowes + +

+ +

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 +). +

+ +
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. + +

... reuerendos dominos archiepiscopum et canonicos Leopolienses + in duplicibus Quatuortemporibus + + Quatuor Tempora, so called dry fast days. + 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). + + + totaliter expediui. +

+ +

+
+
+
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. +

+
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: +

+ + +Women, how cause of mel. 193; their vanity in +apparell taxed, 527; their counterfeit tears +547; their vices 601, commended, +624. +Wormwood, good against mel. 443 +World taxed, 181 +Writers of the cure of mel. 295 + + +
+

+

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: +Women, + how cause of mel. 193; + their vanity in apparell taxed, 527; + their counterfeit tears 547; + their vices + 601, + commended, 624. + + + +

+

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 pb element: + + + +624 + + +For further discussion of this and alternative ways of encoding such +links see the discussion in section . Note that +similar methods may also be used to encode a table of contents, as +further exemplified in section . +

+
+
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: + + + +

+

Like the interp element described in +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): +]]> +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: +

The students understand procedures for Arabic lemmatisation + + Lemmatization, Arabic +and are beginning to build parsers.

+

+

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 +) at the appropriate point and pointing to it from +the index element by means of its spanTo +attribute, as +in this example: +

We now turn to the +topic of Arabic lemmatisation + + Lemmatization, Arabic + concerning which it is important to note [...] + +and now we can build our parser.

+

+

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: +

The @ operator +@ precedes an +attribute name

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 . In +the following example, we assume that somewhere a definition for this +glyph has been provided using the elements described in chapter , and given the code PrinceGlyph: + + + + + +

The Artist formerly known as Prince ...

 +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: +

Sir John Ashford +Ashford, John was, +coincidentally, born in +Ashford +(Kent)Ashford...

+ +

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: +

The students understand procedures for Arabic lemmatisation + + lemmatization + + arabic + + +...

+

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 + + + Women + + how cause of mel. + + +. Similarly, page 601 of the body text would include +an index element like the following: + + Women + + their vices + + +while the index element at page 624 would have a structure +like the following: + + Women + + their vices + + commended + + + +

+

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. + + +

+ Bibliography + + ... + +
+ + + +

+

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. + + + + An Index of Names + + + +

+

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.

+ + + + + +
+
+
+
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: + + + + + + +

+

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 + 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: + + + +

+ +

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: +

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: + +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 +...

+ + +

+

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: + +.

+

The figure element discussed in +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.

+ + + + + + + +
+
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 . + +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 . + +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 +. + +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 . + +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 and in section . +

+

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.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.

+
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 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: + + + + + + + + ... + ... + + ... + + + + + +

+

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: + + + + + + + + ... + + + + + + +

+

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: + + + + + + ... + + + + + + +

+

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 . +

+

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 . +

+
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 + . +

+ +

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

+ +
+ 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. + + +

+

...

+
+ + ... + +
+

...

+
+ + +

...

+

...

+
+ ... +

...

+

...

+
+
+ ... +

...

+

...

+
+ + + 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 . +

+
+ +
+ 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: + + 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. + 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. + 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. + 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.

+
+ +
+
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 ), 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: +

+

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: + + +

+ + +

+ + +

+ +

+ + + +An encoding of the same work in which parts are regarded as more +important than chapters might begin as follows: + + + + +

+ +

+ +

+ + +

+ +

+ + + +

+

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: + + Oh what is this I cannot see + With icy hands gets a hold on me + Oh I am Death, none can excel + I open the doors of heaven and hell + +

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: + + + + + + + + + +

+

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: + + + + + +or + + + + + +

+

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 + may be used, for example to specify that the +attribute must specify one of a predefined set of values. +

+

See below, section , 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 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 imperator 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 imperator 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 .

+ + + + + + + +
+
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 +. 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 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: + + + +

A canonical reference is assembled with + + the name of the : the + n of a div1, + a space, + the number of the : the + n of a child div2, + a full stop + the number of the : the + n of a child div3, + the line number: the n value of a + child l + +

+ + +

Same as above, but without the last component (full + stop followed by the l's n.

+ + +

Same as above, but without the poem component (full + stop followed by the div3's n.

+ + + + +

+

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: + + +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: + + + + +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: + + + +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: + + + + + + + + + + +

+

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: + + + + + + + + + + + + + + + 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 . + +

Standard references to work, book, poem, and line may be + constructed from the milestone tags in the text.

+ +Or in this way, using a formal declaration for this reference scheme +derived from edition E1. + + + + + + +

+
+
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 ; 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. + + + +Lists of such elements may also be encoded using the following element: + + +

+ +

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,For example, to distinguish +London as an author's name from +London as a place of publication or as a +component of a title. 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.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 . The features distinguished and +described below (in section ) 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 ; for a brief mention of related library +standards see section . +

+ +

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. +

+ + + +
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 +; for the biblFull element, the +sub-elements concerned are fully described in section . +

+

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: +

A book which had a great influence on him +was Tufte's Envisioning +Information, although he may +never have actually read it.

+Indeed, some encoders may find it unnecessary to mark the bibliographic +reference at all: +

A book which had a great influence on him +was Tufte's Envisioning Information, +although he may never have actually read it.

 +

+

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 Baxter, 1983. +In general, however, normal modern bibliographic practice, and these +Guidelines, distinguish between a bibliographic reference,referencesbibliographicbibliographic references +which is a self-sufficient description of a bibliographic item, and a +bibliographic pointer,bibliographic pointerspointersbibliographic +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 +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. + + + + + Edward + R. + Tufte + + 6506403994 + https://id.loc.gov/authorities/names/n50012763.html + + Envisioning Information + + Cheshire, Conn. + Graphics Press + + + + +

+

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 +); 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: + + + Envisioning Information + Tufte, Edward R[olf] + + 126 pp. + + Graphics Press + Cheshire, Conn. USA + 1990 + + +

+

A list of bibliographic items, of whatever kind, may be treated in +the same way as any other list (see section ). +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: + + + Bibliography + + + + + Nelson + Theodore + Holm + + + Replacing the printed word: + a complete literary system + + + Information Processing '80: Proceedings of the IFIPS + Congress, October 1980 + + + Simon + H. + Lavington + + + + North-Holland + Amsterdam + + + 1013–23 + + Apparently a draft of section 4 of + Literary Machines. + + + Ted +Nelson: +Literary Machines (privately published, +1987). + + Baxter, +Glen: +Glen Baxter His Life: the years of struggle +London: Thames and Hudson, +1988. + + + 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: + + + + Bibliography + + + Nelson, T. H. + Replacing the printed word: + a complete literary system. + Information Processing '80: + Proceedings of the IFIPS Congress, October 1980. + Simon H. Lavington + North-Holland: + Amsterdam, + 1980. + pp 1013–23 + + Apparently a draft of section 4 of + Literary Machines. + + + + Ted Nelson: Literary Machines + (privately published, 1987) + + + + Baxter, Glen + Glen Baxter His Life: the years of struggle + London: Thames and Hudson, 1988. + + + +

+
+
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 ). +

+
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: + +the analytic level, giving the title, author, etc., of the article; + +the monographic +level, giving the title, editor, etc., of the collection; + +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: + + + Beaupaire + (Edmond), + A propos de la rue de la Femme-sans-Tête, + + La Cité, + janvier 1911, pp. 5-17. + + + +

+ +

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

+ +

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: + + +Albert Schachter +Iolaos + + +Herakles to Poseidon +1986 +64-70 + + +Cults of Boiotia +London +4 vols. +2 + + +Bulletin of the Institute of Classical Studies +Supplements +38 + + + +

+ +

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. + + + + Thaller + Manfred + A Draft Proposal for a Standard for the + Coding of Machine Readable Sources + + + + Historical Social Research + + October 1986 + + 40 + 3-46 + + Modelling Historical Data: + Towards a Standard for Encoding and + Exchanging Machine-Readable Texts + DanielI. + Greenstein + + St. Katharinen + Max-Planck-Institut für Geschichte + In Kommission bei + Scripta Mercaturae Verlag + + + + + Halbgraue Reihe + zur Historischen Fachinformatik + + Herausgegeben von + Manfred Thaller + Max-Planck-Institut für Geschichte + + Serie A: Historische Quellenkunden + 11 + + +

+ + +

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 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.

+ + + + + +James +H. +Coombs + + +Allen +Renear + + +Steven +J. +DeRose + +Markup Systems and The Future of Scholarly Text +Processing +10.1145/32206.32209 +http://xml.coverpages.org/coombs.html + + +Communications of the ACM +1987 +30 +11 +933–947 + + + +

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. + + + + + Nelson, + T. + H. + + + 1980. + Replacing the printed word: a complete literary + system. In Information Processing '80: Proceedings of the + IFIPS Congress, October 1980, + ed. + + + Simon + H. + Lavington + + , + 1013-23. + Amsterdam: North- + Holland. (Apparently a draft of section 4 of + Literary + Machines.) + +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.

+ + + + + + +
+
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: + + + + + + + + + + + + +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: + + + + + Lucy + Allen + Paton + + + Notes on Manuscripts of the + <title level="m" xml:lang="fr">Prophécies de Merlin + + + + PMLA + 1913 + 8 + 122 + +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). +Saarikoski, Pirkko-Liisa, and Paavo Suomalainen, + Studies on the physiology of + the hibernating hedgehog, 15 + Effects of seasonal + and temperature changes on the in vitro glycerol release from + brown adipose tissue + Ann. Acad. Sci. Fenn., Ser. A4 + 1972 + 187 + 1-4 + + +

+

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).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. 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. +Tchaikovsky, Peter Ilich. +The swan lake ballet += Le lac des cygnes +: grand ballet en 4 actes +: op. 20 +[Score]. +New York: Broude Brothers; [1951] (B.B. 59). vi, 685 p. + +

+ +

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 .

+ + John Warrack. „Es waren seine letzten Töne!“ + In Joachim Veit + and Frank Ziegler eds. Weber-Studien Bd. 3, Mainz (1996), pp.300–317 + +

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 , and ; 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: + + + Lominandze, DG. + Cyclotron waves in plasma. + + Translated by + AN. Dellis + ; + + edited by + SM. Hamberger + . + 1st ed. + Oxford: + Pergamon Press, + 1981. + 206 p. + International series in natural philosophy. + Translation of: + Ciklotronnye volny v + plazme. + 0-08-021680-3. + + + + +

+

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. + + + Des Minnesangs Frühling + Mit 1 Faksimile + 36., neugestaltete und erweiterte Auflage + + Unter Benutzung der Ausgaben von Karl + Lachmann und Moriz Haupt, Friedrich + Vogt und Carl von Kraus bearbeitet von + Hugo Moser + Helmut Tervooren + + + Stuttgart + S. Hirzel Verlag + 1977 + + I Texte + + + + + +

+

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. + + proofreading + Ashley Cross + Loren Noveck + +The following example records the fact that one individual had two +distinctly different intellectual responsibilities at different times. + + Erica Dillon + annotated uncredited citations + encoded named entities + +

+

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: + + + Proceedings of a workshop on corpus resources + + Programme Organizer + Geoffrey Leech + + DTI Speech and Language Technology Club meeting, 3-4 + January 1990, Wadham College, Oxford + Oxford + + + + +

+ + + + + + + + + +
+
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: + + + + + John + Downame + + Foure treatises tending to disswade all Christians from foure no lesse hainous then common sinnes + 7141 + + At London + 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 + 1609 + + + + +

+

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: + + + + + + +

+

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: + + + + + US + + 6885550 + + B1 + April 26, 2005 + + + + +

+
+
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: + + + + + + + + + +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. + + + + +

+

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 . Alternatively, +if desired, the rs or name elements described in +section 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: + + + Nicholas, Charles K. + Welsch, Lawrence A. + On the interchangeability of SGML and ODA + NISTIR 4681 + + Gaithersburg, MD + + National Institute of Standards and Technology + + January 1992 + + 19 pp. + + +and with dissertations: + + + Hansen, W. + Creation of hierarchic text + with a computer display + ANL-7818 + Ph.D. dissertation + + Dept. of Computer Science, Stanford Univ. + Stanford, CA + June 1971 + + + +

+

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. + + + Shirley, James + The gentlemen of Venice + a tragi-comedie presented at the private + house in Salisbury Court by Her Majesties servants + [Microform] + + London + H. Moseley + 1655 + + 78 p. + + + + New York + Readex Microprint + 1953 + + 1 microprint card, 23 x 15 cm. + + + Three centuries of drama: English, 1642–1700 + + + +

+

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: + + + + + EP + + 1558513 + + A1 + + + + + + B1 + + + + + +

+

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 below.

+
+
+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: + + + + + Wrigley + E. + A. + + + Parish registers and the historian + + + + + Steel + D. + J. + + + + + Steel + A. + E. + F. + + + General sources of births, marriages and deaths before 1837 + + London + Society of Genealogists + + + 155–167 + + + National index of parish registers + 1 + + +

+

The unit attribute on biblScope is optional: +both the following are legal examples: + + + Boguraev, Branimir + Neff, Mary + Text Representation, Dictionary Structure, + and Lexical Knowledge + + + Literary & Linguistic Computing + + 1992 + + 7 + 2 + 110-112 + + + + + Chesnutt, David + Historical Editions in the States + + + Computers and the Humanities + + (December, 1991): + + 25.6 + 377–380 + + + + + +

+

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: + + + Chesnutt, David + Historical Editions in the States + + + Computers and the Humanities + + (December, 1991): + + 25.6 + 377–380 + + 378 + +

+ + + + + + + +
+
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 ) may be tagged +editor or respStmt. Any identifier associated with +the series itself should be marked using the idno element. +

+
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: + + +

+ +

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. + + + + Swinburne, Algernon Charles + Swinburne's <title level="m">Atalanta in Calydon: A Facsimile of the + First Edition + Georges Lafourcade + + London + Oxford UP + 1930 + + + + + + + + + + Swinburne, Algernon Charles + Atalanta in Calydon + + London + Edward Moxon + 1865 + + + + + +

+ +

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: + + + + Shirley, James + The gentlemen of Venice + + New York + Readex Microprint + 1953 + + 1 microprint card, 23 x 15 cm. + + + Three centuries of drama: English, 1642–1700 + + + + Shirley, James + The gentlemen of Venice + a tragi-comedie presented at the private + house in Salisbury Court by Her Majesties servants + + London + H. Moseley + 1655 + + 78 p. + + +

+

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: + + + Tolkien, J.R.R. + Den hobbit + aus dem Engleschen iwwersat + Henry Wickens + + Esch-sur-Sûre + Op der Lay S. àr. L + 2002 + + + + + Tolkien, J.R.R. +The Hobbit. + Collins + 1997 + + + +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: + + + +

+ + + + + + + + + +
+
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. + +

+

For example: + + Coombs, James H., Allen H. Renear, + and Steven J. DeRose. + Markup Systems and the Future of Scholarly +Text Processing. + Communications of the ACM + 30.11 (November 1987): 933–947. + Classic polemic supporting descriptive over procedural + markup in scholarly work. + +

+

+The textLang element may be used to record information about the languages used within a bibliographic item. + +This element can take the form of a simple note such as: + +Latin, with some glosses in Anglo-Saxon and French + +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: + +Latin, with some glosses in Anglo-Saxon and French + +

+

The mainLang and otherLangs attributes should both provide language identifiers +in the same form as used for xml:lang as described at . 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 .

+

A description, in French, of a work predominantly in German, but also with some Latin might +have a textLang like the following: + +allemand et latin + For more information about the use of textLang in manuscript descriptions +see: .

+ +
+
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: + +notes on the publication (and meeting elements +describing the conference, in the case of a proceedings volume) +edition elements, each followed by any related +editor or respStmt elements +imprint +biblScope +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 . +

+
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 ). 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 () ... +

+

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 (ibid, passim) ... 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 (Nelson [1980] 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 (Nelson [1980] pages 13–37) ... +

+

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: + + + + +Suzana +Sukovic + +Beyond the Scriptorium: The Role of the Library in Text +Encoding +https://www.dlib.org/dlib/january02/sukovic/01sukovic.html + + +D-Lib + +8 +1 +2002 + + + + +

+

The ptr element may be used as a child element of biblStruct to refer to the online catalog record of this bibliographic item: + + + + + + Germain + Brice + + + 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 + + 1717 + Paris + F. Fournier + + In-12 + + + + +

+
+ +
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.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. Elements and structures available in the module defined here which +have no analogues in Scribe and BibTeX are not noted. + + + tag as placeName or address + + tag as note + + tag as author + + tag as title level="m" or title within + monogr + + tag as biblScope unit="chap" + + used only to record date entry was made in the bibliographic database; + not supported + + tag as edition + + tag as editor or respStmt + + tag as multiple editor or respStmt elements + + use the reg element, possibly inside a choice element, inside either an author or name + + use the reg element, possibly inside a choice element, inside a name type="org" + + tag as note, possibly using the form note + place="inline" + + used only for issuer of technical reports; tag as publisher + + tag as title level="j" or title within + monogr + + used to specify an alternate sort key for the bibliographic item, for + use instead of author's or editor's name; not supported + + tag as meeting or as note + + 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 + + tag as note + + tag as biblScope unit="issue" or biblScope + unit="number"; for technical report numbers, use idno + type="docno" + + used only for sponsor of conference; use name type="org" + within respStmt within meeting element + + tag as biblScope unit="pp" + + tag as publisher + + used only for institutions at which thesis work is done; tag as + publisher + + tag as title level="s" or title within + series + + tag as title in appropriate context or with appropriate + level value + + tag as biblScope unit="volume" + + tag as date; if the date is not in a trivially parseable form, + use the when attribute to provide an ISO-format + equivalent + +

+ +
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. + +

+

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 ; for performance texts, see the +drama base described in chapter ). 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. +

+ +
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 and . 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 . 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: + + +Of Mans First Disobedience, and the Fruit +Of that Forbidden Tree, whose mortal tast +Brought Death into the World, and all our woe, +With loss of Eden, till one greater Man +Restore us, and regain the blissful Seat... + + +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 .

+

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 . 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: + +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. + + + Come fill up the Glass, + Round, round let it pass, + 'Till our Reason be lost in our Wine: + Leave Conscience's Rules + To Women and Fools, + This only can make us divine. + + + Then a Mohock, a Mohock I'll be, + No Laws shall restrain + Our Libertine Reign, + We'll riot, drink on, and be free. + +

+

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 . For example: + + + Thus speaks the Muse, and bends her brow severe:— + “Did I, Lætitia, lend my choicest lays, + And crown thy youthful head with freshest bays, + That all the' expectance of thy full-grown year + Should lie inert and fruitless? O revere + Those sacred gifts whose meed is deathless praise, + Whose potent charms the' enraptured soul can raise + Far from the vapours of this earthly sphere! + + + Seize, seize the lyre! resume the lofty strain! + 'T is time, 't is time! hark how the nations round + With jocund notes of liberty resound,— + And thy own Corsica has burst her chain! + O let the song to Britain's shores rebound, + Where Freedom's once-loved voice is heard, + alas! in vain.” + + +

+

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: +Thou fumblest Eros, and my Queenes a Squire +More tight at this, then thou: Dispatch. O Loue, +That thou couldst see my Warres to day, and knew'st +The Royall Occupation, thou should'st see +A Workeman in't. +Enter an Armed Soldier. +Good morrow to thee, welcome. +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: + + + +Unprofitably travelling toward the grave, +Like a false steward who hath much received +And renders nothing back. + +Was it for this +That one, the fairest of all rivers, loved +To blend his murmurs with my nurse's song, + + + +

+

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: + + First Voice + + But why drives on that ship so fast + Withouten wave or wind? + + + + Second Voice + + The air is cut away before, + And closes from behind. + + + +

+

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 . For discussion of +other elements and attributes specific to the encoding of verse, see +chapter . +

+ + + + + +
+
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 and . 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: + + Scene 2. + Peachum, Filch. + + FILCH. +

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.

+ + + PEACHUM. +

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.

+ + + FILCH. +

Tom Gagg, sir, is found guilty.

+ + + +

+

In the following example, each speech consists of a sequence of verse +lines, some of them being marked as metrically incomplete: + + ACT I + + SCENE I + Enter Barnardo and Francisco, + two Sentinels, at several doors + Barn + Who's there? + + Fran + Nay, answer me. Stand and unfold yourself. + + Barn + Long live the King! + + Fran + Barnardo? + + Barn + He. + + Fran + You come most carefully upon your hour. + + Barn + 'Tis now struck twelve. Get thee to bed, Francisco. + + Fran + For this relief much thanks. 'Tis bitter cold, + And I am sick at heart. + + + + +

+

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: +Enter two Centinels. +Now call'd Bernardo & +Francesco. + 1. + Stand: who is that? + + 2. + Tis I. + + 1. + O you come most carefully vpon your watch, + + 2. + And if you meete Marcellus and Horatio, + The partners of my watch, bid them make haste. + + 1. + I will: See who goes there. + +Enter Horatio and Marcellus. + + +

+

By contrast with the preceding examples, the following encodes an +early printed edition without making any assumption about which parts +are prose or verse: + + + Actus primus, Scena prima. + A tempestuous + noise of Thunder and Lightning heard: Enter + a Ship-master, and a Boteswaine. + + Master.

Bote-swaine.

+ + + Botes.

Heere Master: What cheere?

+ + + Mast. +

Good: Speake to th' Mariners: fall + too't, yarely, or we run our selues a ground, + bestirre, bestirre. Exit. +

+ + Enter Mariners. + + Botes. +

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.

+ + + + +

+

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: +The reverend Doctor Opimian +

I do not think I have named a single unpresentable fish.

+ +Mr Gryll +

Bream, Doctor: there is not much to be said for bream.

+ +The Reverend Doctor Opimian +

On the contrary, sir, I think there is much to be said for him. + In the first place ...

+

Fish, Miss Gryll — I could discourse to you on fish by the + hour: but for the present I will forbear ...

+ + + + Lord Curryfin + (after a pause). +

Mass as the second grave-digger says + in Hamlet, I cannot tell.

+ +

A chorus of laughter dissolved the sitting.

 + +

+ + + + + + +
+
+ Overview of the Core Module +

All the elements described in this chapter are provided by the + core module. + + Common Core + Elements common to all TEI documents + Éléments disponibles pour tous les documents TEI + 所有TEI文件所通用的元素 + Elementi comuni a tutti i documenti TEI + Elementos comuns a todos os documentos TEI + コアモジュール + + The selection and combination of modules to form a TEI schema is + described in .

+ + + + + + + + + + + + + + + + + + +
+
diff --git a/P5/Source/Guidelines/fr/COL-Colophon.xml b/P5/Source/Guidelines/fr/COL-Colophon.xml deleted file mode 120000 index 49c7b82206..0000000000 --- a/P5/Source/Guidelines/fr/COL-Colophon.xml +++ /dev/null @@ -1 +0,0 @@ -../en/./COL-Colophon.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/COL-Colophon.xml b/P5/Source/Guidelines/fr/COL-Colophon.xml new file mode 100644 index 0000000000..dcdd313fb0 --- /dev/null +++ b/P5/Source/Guidelines/fr/COL-Colophon.xml @@ -0,0 +1,38 @@ + + + + + + + +
+ Colophon +

The text of this manual was prepared electronically on a variety of + systems. Most sections were originally drafted by members of the work + groups and working committees of the TEI; all have been revised by the + editors to achieve greater uniformity of style and greater consistency + in the tag set.

+ +

The web release of the Guidelines was created using a library of + XSLT stylesheets to convert to XHTML; the PDF version for printing was + produced by conversion to LaTeX markup, processed using XeLaTeX. + The XSLT libraries were written by Sebastian Rahtz.

+ + +

Almost every available SGML and XML editor or processing program + has been used at one time or another by the TEI; but + without the open source implementations of XML parsers, editors and + XSLT engines by James Clark, Richard Stallman, Michael Kay, and Daniel + Veillard, the TEI could not survive, and we thank these + individuals. We would also like to thank the staff at SyncRO Soft SRL, + creators of the oXygen editor, for their support for the TEI during + the creation on P5.

+ +

Many volunteers contributed to the preparation of this release of + the Guidelines; we particularly note the work of Sabine Krott, Eva + Radermacher and Arianna Ciula for their work in structuring the + bibliographies.

+ +

The production and release process for TEI P5 was originally developed by + Sebastian Rahtz for the TEI Technical Council.

+
diff --git a/P5/Source/Guidelines/fr/DI-PrintDictionaries.xml b/P5/Source/Guidelines/fr/DI-PrintDictionaries.xml deleted file mode 120000 index 62b981ca5b..0000000000 --- a/P5/Source/Guidelines/fr/DI-PrintDictionaries.xml +++ /dev/null @@ -1 +0,0 @@ -../en/./DI-PrintDictionaries.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/DI-PrintDictionaries.xml b/P5/Source/Guidelines/fr/DI-PrintDictionaries.xml new file mode 100644 index 0000000000..40060bcdce --- /dev/null +++ b/P5/Source/Guidelines/fr/DI-PrintDictionaries.xml @@ -0,0 +1,3106 @@ + + + + +
+ Dictionaries + +

This chapter defines a module for encoding lexical resources of all +kinds, in particular human-oriented +monolingual and multilingual dictionaries, glossaries, and similar +documents. The elements described here may also be useful in the +encoding of computational lexica and similar resources intended for +use by language-processing software; they may also be used to provide +a rich encoding for wordlists, lexica, glossaries, etc. included +within other documents. Dictionaries are most familiar in +their printed form; however, increasing numbers of dictionaries exist +also in electronic forms which are independent of any particular +printed form, but from which various displays can be produced.

+ +

Both typographically and structurally, print dictionaries are +extremely complex. Such lexical resources are moreover of interest to +many communities with different and sometimes conflicting goals. As a +result, many general problems of text encoding are particularly +pronounced here, and more compromises and alternatives within the +encoding scheme may be required in the future.We +refer the reader to previous and current discussions of a common +format for encoding lexical resources. For example, ; ; ; ; ; ; ; and ; . Two problems are particularly +prominent.

+ +

First, because the structure of dictionary entries varies widely +both among and within dictionaries, the simplest way for an encoding +scheme to accommodate the entire range of structures actually +encountered is to allow virtually any element to appear virtually +anywhere in a dictionary entry. It is clear, however, that strong and +consistent structural principles do govern the vast majority of +conventional dictionaries, as well as many or most entries even in +more exotic dictionaries; +encoding guidelines should include these structural principles. We +therefore define two distinct elements for dictionary entries, one +(entry) which captures the regularities of many conventional +dictionary entries, and a second (entryFree) which uses the +same elements, but allows them to combine much more freely. It is +however recommended that entry be used in preference to +entryFree wherever possible. +These elements and their contents are described in sections , , and .

+ +

Second, since so much of the information in printed dictionaries is +implicit or highly compressed, their encoding requires clear thought +about whether it is to capture the precise typographic form of the +source text or the underlying structure of the information it +presents. Since both of these views of the dictionary may be of +interest, it proves necessary to develop methods of recording both, +and of recording the interrelationship between them as well. Users +interested mainly in the printed format of the dictionary will require +an encoding to be faithful to an original printed version. However, +other users will be interested primarily in capturing the lexical +information in a dictionary in a form suitable for further processing, +which may demand the expansion or rearrangement of the information +contained in the printed form. Further, some users wish to encode +both of these views of the data, and retain the links +between related elements of the two encodings. Problems of recording +these two different views of dictionary data are discussed in section +, together with mechanisms for retaining both +views when this is desired.

+ +

To deal with this complexity, and in particular to account for the +wide variety of linguistic contexts within which a dictionary may be +designed, it can be necessary to customize or change the schema by +providing more restriction or possibly alternate content models for +the elements defined in this chapter. Section +illustrates this with the provision of a closed set of values for +grammatical descriptors.

+ +

This chapter contains a large number of examples taken from +existing print dictionaries; in each case, the original source is +identified. In presenting such examples, we have tried to retain the +original typographic appearance of the example as well as presenting a +suggested encoding for it. Where this has not been possible (for +example in the display of pronunciation) we have adopted the +transliteration found in the electronic edition of the Oxford +Advanced Learner's Dictionary. Also, the middle dot in quoted +entries is rendered with a full stop, while within the sample +transcriptions hyphenation and syllabification points are indicated by +a vertical bar |, regardless of their appearance in the source +text.

+ +
+Dictionary Body and Overall Structure + +

Overall, dictionaries have the same structure of front matter, +body, and back matter familiar from other texts. In addition, +this module defines entry, entryFree, +and superEntry as component-level elements which can occur +directly within a text division or the text body.

+ +

The following tags can therefore be used to mark the gross structure of a +printed dictionary; the dictionary-specific tags are discussed further +in the following section. + + + + + + + + +

+ +

As members of the classes att.entryLike and + att.sortable, +entry and entryFree share the following +attributes: + + + +

+ +

The front and back matter of a dictionary may well contain +specialized material such as lists of common and proper nouns, +grammatical tables, gazetteers, a guide to the use of the +dictionary, etc. These should be tagged using elements +defined elsewhere in these Guidelines, chiefly in the core module +(chapter ) together with the specialized dictionary +elements defined in this chapter.

+ +

The body element consists of a set of +entries, optionally grouped into one or several +div elements. These text divisions might, for example, correspond to +sections for different letters of the alphabet, or to sections for +different languages in a bilingual dictionary, as in the following +example: + + + +

English-French +
cat
 +
dog
 +
horse
 +
+
+French-English +
chat
 +
chien
 +
cheval
 +
+ + +

+ +

In a +print dictionary, the entries are typically typographically distinct +entities, each headed by some morphological form of the lexical item +described (the headword), and sorted in alphabetical +order or (especially for non-alphabetic scripts) in some other +conventional sequence. Dictionary entries should be encoded as +distinct successive items, each marked as an entry or +entryFree element. The type attribute may be used +to distinguish different types of entries, for example main entries, +related entries, run-on entries, or entries for cross-references, +etc.

+ +

Some dictionaries provide distinct entries for homographs, on the +basis of etymology, part-of-speech, or both, and typically provide a +numeric superscript on the headword identifying the homograph +number. In these cases each homograph should be encoded as a separate +entry; the superEntry element may optionally be used to group +such successive homograph entries. In addition to a series of +entry elements, the superEntry may contain a +preliminary form group (see section ) +when information about hyphenation, pronunciation, etc., is given only +once for two or more homograph entries. If the homograph number is to +be recorded, the global attribute n may be used for this +purpose. In some dictionaries, homographs are treated in distinct +parts of the same entry; in these cases, they may be separated by use +of the hom element, for which see section .

+ +

A sort key, given in the sortKey attribute, is often +required for superentries and entries, especially in cases where the +order of entries does not follow the local character-set collating +sequence (as, for example, when an entry for 3D appears at the +place where three-D would appear).

+ + + +

A dictionary with no internal divisions might thus have a structure like +the following; a superEntry is shown grouping two homograph +entries. + + +

+ manifestation +
+ + +
+ émeute +
 + + +
+ grève +
+ + +
+ grève +
+ + + + +

+ + + + + + + + + + + + + + + + + + + + + +
+
+The Structure of Dictionary Entries + +

A simple dictionary entry may contain information about the form of +the word treated, its grammatical characterization, its definition, +synonyms, or translation equivalents, its etymology, cross-references +to other entries, usage information, and examples. These we refer to +as the constituent parts or constituents of +the entry; some dictionary constituents possess no internal structure, +while others are most naturally viewed as groups of smaller elements, +which may be marked in their own right. In some styles of markup, +tags will be applied only to the low-level items, leaving the +constituent groups which contain them untagged. We distinguish the +class of top-level constituents of dictionary entries, +which can occur directly within the entry element, from the class of +phrase-level constituents, which can normally occur only +within top-level constituents. The top-level constituents of +dictionary entries are described in section , +and documented more fully, together with their phrase-level +sub-constituents, in section .

+ +

In addition, however, dictionary entries often have a complex +hierarchical structure. For example, an entry may consist of two or +more sub-parts, each corresponding to information for a different +part-of-speech homograph of the headword. The entry (or part-of-speech +homographs, if the entry is split this way) may also consist of +senses, each of which may in turn be composed of two or more +sub-senses, etc. Each sub-part, homograph entry, sense, or sub-sense +we call a level; at any level in an entry, any or all of +the constituent parts of dictionary entries may appear. The +hierarchical levels of dictionary entries are documented in section +.

+ +
+Hierarchical Levels + +

The outermost structural level of an entry is marked with the +elements entry or entryFree. The hom +element marks the subdivision of entries into homographs differing in +their part-of-speech. The sense element marks the subdivision +of entries and part-of-speech homographs into senses; this element +nests recursively in order to provide for a hierarchy of sub-senses of +any depth. It is recommended to use the sense element even +for an entry that has only one sense to group together all parts of +the definition relating to the word sense since this leads to more +consistent encoding across entries. +All of these levels may each contain any of the +constituent parts of an entry. A special case of hierarchical +structure is represented by the re (related entry) element, +which is discussed in section . Finally, the +element dictScrap may be used at any point in the hierarchy +to delimit parts of the dictionary entry which are structurally +anomalous, as further discussed in section . + + + + + + +

+

For example, an entry with two senses will have the following structure: + + + + + +

+

An entry with two homographs, the first with two senses and the second with three + (one of which has two sub-senses), may have a structure like this: + + + + + + + + + + + + + + + In some dictionaries, homographs have separate entries; in +such a case, as noted in section , the two homographs may be + treated as entries, optionally grouped in a superEntry: + + + + + + + + + + + + + + + +

+

The hierarchic structure of a dictionary entry is enforced by the +structures defined in this module. The content model for +entry specifies that entries do not nest, that homographs +nest within entries, and that senses nest within entries, homographs, +or senses, and may be nested to any depth to reflect the embedding of +sub-senses. Any of the top-level constituents (def, +usg, form, etc.) can appear at any level (i.e., +within entries, homographs, or senses). + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

+
+
+Groups and Constituents + +

As noted above, dictionary entries, and subordinate levels within dictionary entries, +may comprise several constituent parts, each providing a different type of +information about the word treated. The top-level constituents of +dictionary entries are: +information about the form of the word treated (orthography, +pronunciation, hyphenation, etc.) +grammatical information (part of speech, grammatical sub-categorization, +etc.) +definitions or translations into another language +etymology +examples +usage information +cross-references to other entries +notes +entries (often of reduced form) for related words, typically called +related entries + + Any of the hierarchical levels (entry, entryFree, +hom, and sense) may contain any of these top-level constituents, since +information about word form, particular grammatical information, special +pronunciation, usage information, etc., may apply to an entire entry, or to only one +homograph, or only to a particular sense. The examples below illustrate this point.

+

The following elements are used to encode these top-level constituents: + + + + + + + + + + +

+

In a simple entry with no internal hierarchy, all top-level constituents can appear +as children of entry. + +com.peti.tor +/k@m"petit@(r)/ n person who competes. OALD + + +

+competitor +com|peti|tor +k@m"petit@(r) +
+ +n + +person who competes. + + +For the elements which appear within the form and gramGrp +elements of this and other examples, see below, section , and section .

+

Any top-level constituent can appear at any level when the +hierarchical structure of the entry is more complex. The most obvious examples are +def and cit, which appear at the sense level when +several senses or translations exist: +disproof + (dɪsˈpru:f) n 1 facts that disprove something 2 the +act of disproving. CED + + +

+disproof +dɪsˈpru:f +
+ +n + + +facts that disprove something + + +the act of disproving + + + +

+

For ease of processing of such entries containing multiple senses along with those containing +only a single sense, it is recommended to use sense in all entries to wrap those elements +relating to a particular word sense.

+

In the following example, gramGrp is used to distinguish two homographs: +bray +/breI/ n cry of an ass; sound of a trumpet. ∙ vt [VP2A] +make a cry or sound of this kind. OALD + + +

+bray +breI +
+ + +n + + +cry of an ass; sound of a trumpet. + + + + +vt +VP2A + + +make a cry or sound of this kind. + + + + + +

+

Information of the same kind can appear at different levels within the same entry; +here, grammatical information occurs both at entry and homograph level. +ca.reen +/k@"ri:n/ vt,vi 1 [VP6A] turn (a ship) on one side for +cleaning, repairing, etc. 2 [VP6A, 2A] (cause to) tilt, lean over to one side. +OALD + + +

+careen +ca|reen +k@"ri:n +
+ +vt +vi + + + +VP6A + +turn (a ship) on one side for cleaning, repairing, etc. + + + +VP6A +VP2A + +(cause to) tilt, lean over to one side. + + + + +

+

Alone among the constituent groups, form can appear at the +superEntry level as well as at the entry, hom, and +sense levels: +a.ban.don 1/@"band@n/ +v [T1] 1 to leave completely and for ever; desert: The sailors abandoned the +burning ship. 2 …abandon 2 n [U] the state when one's +feelings and actions are uncontrolled; freedom from control...LDOCE + + +

+abandon +a|ban|don +@"band@n +
+ + +v +T1 + + +to leave completely and for ever … + + + + + +n +U + + +the state when one's feelings and actions are uncontrolled; freedom +from control… + + + + +

+
+
+
+Top-level Constituents of Entries +

This section describes the top-level constituents of dictionary entries, together with +the phrase-level constituents peculiar to each. +the form element, which groups orthographic information and +pronunciations, is described in section + +the gramGrp element, which groups elements for the grammatical +characterization of the headword, is described in section + +the def element, which describes the meaning of the headword, is +described in section + +the etym element and its special phrase-level elements are documented +in section + +the cit element and its specific applications are described in +section and section + +the usg, lbl, xr, and note elements are +described in section + +the re element, which marks nested entries for related words, is +described in section + + +

+
+Information on Written and Spoken Forms +

Dictionary entries most often begin with information about the form of the word to +which the entry applies. Typically, the orthographic form of the word, sometimes +marked for syllabification or hyphenation, is the first item in an entry. Other +information about the word, including variant or alternate forms, inflected forms, +pronunciation, etc., is also often given.

+

The following elements should be used to encode this information: the form +element groups one or more occurrences of any of them; it can also be +recursively nested to reflect more complex sub-grouping of information about word +form(s), as shown in the examples. + + + + + + + + +

+

In addition to those listed above, the following elements, which encode morphological +details of the form, may also occur within form elements: + + + + + + + + + + + + Of these, the gram element is most general, and all of the +others are synonymous with a gram element with appropriate values (gen, +number, case, etc.) for the type attribute.

+

The use of these elements as children of form is deprecated; instead, they +should always be children of a gramGrp within form when describing +that particular form of the word.

+

Different dictionaries use different means to mark hyphenation, +syllabification, and stress, and they often use some unusual glyphs +(e.g., the middle dot for hyphenation). All of +these glyphs are in the Unicode character set, as discussed in . When transcribing representations of pronunciation +the International Phonetic Alphabet should be used. It may be +convenient (as has been done in the text of this chapter) to use a +simple transliteration scheme for this; such a scheme should however be +properly documented in the header.

+

In the simplest case, nothing is given but the orthography: +

+doom-laden +
+ +

+

Often, however, pronunciation is given. +soucoupe [sukup] … DNT + +

+soucoupe +sukup +
+ +

+

For a variety of reasons including ease of processing, it may be desired to split +into separate elements information which is collapsed into a single element in the +source text; orthography and hyphenation may for example be transcribed as separate +elements, although given together in the source text. For a discussion of the issues +involved, and of methods for retaining both the presentation form and the +interpreted form, see section .

+

This example splits orthography and hyphenation, and adds syllabification because it +differs from hyphenation: +ar.ea … W7 + +

+area +ar|ea +ar|e|a +
+ + +

+

Multiple orthographic forms may be given, e.g. to illustrate a word's inflectional +pattern: +brag … vb brags, bragging, bragged … CED + +

+brag +
+ +vb + +
+brags +bragging +bragged +
+ Or the inflectional pattern may be indicated by reference to a table of +paradigms, as here: +horrifier +[ORifje] (7) vt … [C/R] + +
+horrifier +ORifje + +7 + + +
+ + +

+ +

Explanatory labels may be attached to alternate forms: +MTBF +abbreviation for mean time between failures CED + + +

+MTBF +
+
+abbreviation for +mean time between failures +
+ + +

+

When multiple orthographic forms are given, a pronunciation may be associated with +all of them, as here: +biryani or biriani + (ˌbɪrɪˈa:nɪ) … CED + +

+biryani +biriani +ˌbɪrɪˈa:nɪ +
+ +

+

In other cases, different pronunciations are provided for different orthographic +forms; here, the form element is repeated to associate the first +orthographic form explicitly with the first pronunciation, and the second +orthographic form with the second pronunciation: +mackle + (ˈmækᵊl) or macule (ˈmækju:l) … CED + +

+mackle +ˈmækᵊl +
+
+macule +ˈmækju:l +
+ +

+

Recursive nesting of the form element can preserve relations among elements +that are implicit in the text. For example, in the CED entry for hospitaller, +it is clear that U.S. is associated only with hospitaler, but that the +pronunciation applies to both forms. The following encoding preserves these +relations: + hospitaller or US hospitaler (ˈhɒspɪtələ) … CED + +

+hospitaller + +US +hospitaler +
+ˈhɒspɪtələ + + + +

+ + + + + + + + + + + + + + + + + + + + + + + + + +
+
+Grammatical Information +

The gramGrp element groups grammatical information, such as part of speech, +subcategorization information (e.g., syntactic patterns for verbs, count/mass +distinctions for nouns), etc. It can contain any of the morphological elements defined +in section for form and can appear as a child of entry, +form, sense, cit, or any other element containing content about which +there is grammatical information. For example, in the entry + pinna (ˈpɪnə) n, + pl -nae (-ni:) or -nas CED, the +word defined can be either singular or plural; the pl. specification applies +only to the inflected forms provided. Compare this with pants (paents) pl. +n., where pl. applies to the headword itself.

+

As noted above in section , the elements for morphological +information are simply shorthand for the general purpose gram element. +Consider this entry for the French word médire: + +médire v.t. ind. (de) … PLC This entry can be +tagged using specialized grammatical elements: +

+médire +
+ +v +t ind +de + + Or using the gram element: +
+médire +
+ +v +t ind +de + + +

+

Like form, gramGrp can be repeated, recursively nested, or used at +the sense level to show relations among elements. +isotope adj. et n. m. … DNT + +

+isotope +
+ +adj + + +n +m + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + wits (wɪts) pl n 1 + (sometimes singular) the ability to +reason and act, esp quickly … CED + + +
+wits +wɪts +
+ +pl +n + + + +sometimes singular + +the ability to reason and act, esp quickly … + + + +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+
+Sense Information +

Dictionaries may describe the meanings of words in a wide variety of different + ways—by means of synonyms, paraphrases, translations into other languages, formal +definitions in various highly stylized forms, etc. No attempt is made here to +distinguish all the different forms which sense information may take; +all of them may +be tagged using the def element described in section .

+

As a special case it is frequently desirable to distinguish +the provision of translation equivalents in other languages from other +forms of sense information; the use of cit +type="translation" (which groups a translation equivalent with +related information such as its grammatical description) +for this purpose is described +in section .

+ +
+Definitions +

Dictionary definitions are those pieces of prose in a dictionary entry that +describe the meaning of some lexical item. Most often, definitions describe the +headword of the entry; in some cases, they describe translated texts, examples, +etc.; see cit type="translation", section , and +cit type="example", section . The +def element directly contains the text of the definition; unlike +form and gramGrp, it does not serve solely to +group a set of smaller elements. The close analysis of definition text, such as +the tagging of hypernyms, typical objects, etc., is not covered by these +Guidelines.

+

Definitions may occur directly within an entry; when multiple +definitions are given, they are typically identified as belonging to +distinct senses, as here: demigod (…) n. 1.a. a being who is part mortal, part +god. b. a lesser deity. 2. a godlike person. CP + + +

+demigod + … +
+ +n + + + +a being who is part mortal, part god. + + +a lesser deity. + + + +a godlike person. + + + +

+

In multilingual dictionaries, it is sometimes possible to distinguish translation +equivalents from definitions proper; here a def element is +distinguished from the translation information within which it appears. +rémoulade +[Remulad] nf remoulade, rémoulade (dressing containing mustard and herbs). CR + + +

+rémoulade +Remulad +
+ +n +f + + +remoulade +rémoulade +dressing containing mustard and herbs + + + +

+ + + + + + + + + + + + + + +
+
+Translation Equivalents +

Multilingual dictionaries contain information about translations of a given word +in some source language for one or more target languages. Minimally, the +dictionary provides the corresponding translation in the target language; other +material, such as morphological information (gender, case), various kinds of +usage restrictions, etc., may also be given. If translation equivalents are to +be distinguished from other kinds of sense information, they may be encoded +using cit type="translation". The global xml:lang attribute +should be used to specify the target language.

+

As in monolingual dictionaries, the sense element is used in +multilingual dictionaries to group information (forms, grammatical information, +usage, translation(s), etc.) about a given sense of a word where necessary. +Information about the individual translation equivalents within a sense is +grouped using cit type="translation". This information may include the +translation text (tagged q or quote), morphological +information (gen, case, etc.), usage notes (usg), +translation labels (lbl), and definitions (def).When +bibliographic data is provided, the quote element should be used. + + + +

+

Note how in the following example, different translation +equivalents are grouped into the same or different senses, following +the punctuation of the source and the usage labels: +dresser … (a) (Theat) habilleur m, -euse f; +(Comm: window ~) étalagiste mf. she's a stylish ~ elle s'habille avec +chic; V hair. (b) (tool) (for wood) raboteuse f; (for stone) rabotin +m. CR + + + + + +

+dresser +
+ + +Theat + +habilleur + +m + + + +-euse + +f + + + + +Comm +
+window + +
+ +étalagiste + +mf + + + + +she's a stylish + + +elle s'habille avec chic + + +V. hair + + + +tool + +for wood + +raboteuse + +f + + + + +for stone + +rabotin + +m + + + + + + + + + + +

+

In the following example, a distinction is made between the +translation equivalent (OAS) and a descriptive phrase providing +further information for the user of the dictionary. +O.A.S. ... nf (abrév de Organisation de l'Armée secrète) OAS (illegal military organization supporting French rule of +Algeria). CR + + + + +OAS +illegal military organization supporting French rule of +Algeria + + + +

+

Note that cit type="translation" may also be used in monolingual +dictionaries when a translation is given for a foreign word: + +havdalah or havdoloh Hebrew + (havdaˈla; Yiddish havˈdɔlə) + n Judaism the ceremony marking the end of the +sabbath or of a festival, including the blessings over wine, candles and +spices [literally: separation] CED + + +

+havdalah +havdoloh + +n + +
+ +Judaism +the ceremony marking the end of the sabbath or of a festival, +including the blessings over wine, candles and spices + + +literally +separation + + + +

+
+
+
+Etymological Information +

The element etym marks a block of etymological information. Etymologies may +contain highly structured lists of words in an order indicating their descent from +each other, but often also include related words and forms outside the direct line +of descent, for comparison. Not infrequently, etymologies include commentary of +various sorts, and can grow into short (or long!) essays with prose-like structure. +This variation in structure makes it impracticable to define tags which capture the +entire intellectual structure of the etymology or record the precise interrelation +of all the words mentioned. It is, however, feasible to mark some of the more +obvious phrase-level elements frequently found in etymologies, using tags defined in +the core module or elsewhere in this chapter. Of particular relevance for the +markup of etymologies are: + + + + + + + + + +

+

As in other prose, individual word forms mentioned in an etymological description are +tagged with mentioned elements. Pronunciations, usage labels, and glosses +can be tagged using the pron, usg, and gloss elements +defined elsewhere in these Guidelines. In addition, the lang element may be +used to identify a particular language name where it appears, in addition to using +the xml:lang attribute of the mentioned element.

+

Examples: +abismo m. (del gr. a priv. y byssos, fondo). Sima, gran +profundidad. … + + +

+abismo +
+del gr. +a priv. y byssos, +fondo + + + + + +neume +\'n(y)üm\ n [F, fr. ML pneuma, neuma, fr. Gk pneuma +breath — more at pneumatic]: any of various symbols used in +the notation of Gregorian chant … [WNC] + + + + +F fr. ML +pneuma +neuma fr. Gk +pneuma +breath +more at + + + +any of various symbols used in the notation of Gregorian chant + + + + + + + +

+ + + + + +
+
+Other Information +
+Examples +

Dictionaries typically include examples of word use, usually accompanying +definitions or translations. In some cases, the examples are quotations from +another source, and are occasionally followed by a citation to the author.

+

The cit type="example" element contains usage examples and associated +information; the example text itself should be enclosed in a q or +quote element. The cit element associates a quotation with +a bibliographic reference to its source. + + + + +

+

Examples frequently abbreviate the headword, and so their transcription will +frequently make use of the oRef element described +below in section .

+

Examples: +multiplex +/…/ adj tech having many parts: the multiplex eye +of the fly. LDOCE + + +the multiplex eye of the fly. + Or when one wants a more comprehensive representation of +examples: + +the multiplex eye of the fly. + + As the following example shows, cit can also contain elements +such as pron, def, etc. +some … 4. (S~ and any are used with more): Give me ~ more/s@'mO:(r)/ OALD + + + + + and any are used with +more + + +Give me more +s@'mO:(r) + + + In multilingual dictionaries, examples may also be accompanied by +translations: +horrifier … vt to horrify. elle était +horrifiée par la dépense she was horrified at the expense. CR + + + + + +to horrify + + +elle était horrifiée par la dépense + +she was horrified at the expense. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + When a source is indicated, the example should be marked +with a bibl element: +valeur … n. f. … 2. Vx. Vaillance, bravoure +(spécial., au combat). La valeur n'attend pas le nombre des années +(Corneille). … DNT + + +Vx. +Vaillance, bravoure (spécial., au combat) + +La valeur n'attend pas le nombre des années + +Corneille + + + + +

+
+
+Usage Information and Other Labels + +

Most dictionaries provide restrictive labels and phrases indicating +the usage of given words or particular senses. Other phrases, not +necessarily related to usage, may also be attached to forms, translations, +cross-references, and examples. The following elements are provided +to mark up such labels: + + + As indicated in the following section (), the +lbl element may be used for any kind of significative phrase +or label within the text. The usg element is a specialization +of this to mark usage labels in particular. Usage labels typically +indicate +temporal use (archaic, obsolete, etc.) +register (slang, formal, taboo, ironic, facetious, etc.) +style (literal, figurative, etc.) +connotative effect (e.g. derogatory, offensive) +subject field (Astronomy, Philosophy, etc.) +national or regional use (Australian, U.S., Midland dialect, +etc.) + Many dictionaries provide an explanation and/or a list of such usage +labels in a preface or appendix. The type of the usage information may be +indicated in the type attribute on the usg element. Some +typical values are: + +geographic area + +temporal, historical era (archaic, old, etc.) + +domain + +register + +style (figurative, literal, etc.) + +preference level (chiefly, usually, etc.) + +acceptability + +language for foreign words, spellings pronunciations, etc. + +grammatical usage + In addition to this kind of information, multilingual dictionaries often +provide semantic cues to help the user determine the right +sense of a word in the source language (and hence the correct translation). +These include synonyms, concept subdivisions, typical subjects and objects, +typical verb complements, etc. These labels may also be marked with the +usg element; sample values for the type attribute in these +cases include: + +synonym given to show use + +hypernym given to show usage + +collocation given to show usage + +typical complement + +typical object + +typical subject + +typical verb + +unclassifiable piece of information to guide sense choice + +

+

In this entry, one spelling is marked as geographically restricted: +colour or US color … CED + +

+colour + +US +color +
+ + +

+

In the next example, usage labels are used to indicate domains, register, and +synonyms associated with different senses: +palette +[palEt] nf (a) (Peinture: lit, fig) palette. (b) +(Boucherie) shoulder. (c) (aube de roue) paddle; (battoir à linge) beetle; +(Manutention, Constr) pallet. CR + + +Peinture +lit +fig + +palette + + + +Boucherie + +shoulder + + + + +aube de roue + +paddle + + + +battoir à linge + +beetle + + + +Manutention +Constr + +pallet + + + + + + + + + + + + + + + + + + + + + + + + +

+

When the usage label is hard to classify, it may be described as a hint: +rempaillage […] nm reseating, rebottoming (with straw). CR + + + + +reseating +rebottoming +with straw + + + +

+ + + + + +
+
+Cross-References to Other Entries +

Dictionary entries frequently refer to information in other entries, often using +extremely dense notations to convey the headword of the entry to be sought, the +particular part of the entry being referred to, and the nature of the +information to be sought there (synonyms, antonyms, usage notes, etymology, an +illustration, etc.)

+

Cross-references may be tagged in dictionaries using the ref and +ptr elements defined in the core module (section ). In addition, the xr element may be used to group all the +information relating to a cross-reference. + + + + + + +

+

As in other types of text, the actual pointing element (e.g. ref or +ptr) is used to tag the cross-reference target proper (in +dictionaries, usually the headword, possibly accompanied by a homograph number, +a sense number, or other further restriction specifying what portion of the +target entry is being referred to). +The xr element +is used to group the target with any accompanying phrases or symbols used to +label the cross-reference; the cross-reference label itself may be encoded with +lbl or may remain untagged. Both of the following are thus +legitimate: +glee … Compare madrigal (1) +CED + + +

+glee +
+Compare + + + +
+ + + +hostellerie Syn. de hôtellerie (sens 1). DNT + + +Syn. de +hôtellerie (sens 1). + In addition to using, or not using, lbl to mark the +cross-reference label, the two examples differ in another way. The former +assumes that the first sense of madrigal has the +identifier madrigal.1, and that the specific form of the reference in the +source volume can be reconstructed, if needed, from that information. The latter +does not require the first sense of hôtellerie to have an identifier, and +retains the print form of the cross-reference; by omitting the target +attribute of the ref element, however, the second example does assume +implicitly either that some software could usefully parse the phrase tagged as a +ref and find the location referred to, or else that such processing +will not be necessary.

+

The type attribute on the pointing element or on the xr +element may be used to indicate what kind of cross-reference is being made, +using any convenient typology. Since different dictionaries may label the same +kind of cross-reference in different ways, it may be useful to give normalized +indications in the type attribute, enabling the encoder to distinguish +irregular forms of cross-reference more reliably: +rose2 … vb the past tense of rise CED + + +

+rose +
+ +the past tense of +rise + + + + +
+rise +
+ + + from cross-references for synonyms and the like: +antagonist … syn see adverse +W7 + + +syn see +adverse + + + +
+adverse +
+ + +Strictly speaking, the reference above is not to the entry for +adverse, but to the list of synonyms found +within that entry. + + In some cases, the cross-reference is to a particular subset of the +meanings of the entry in question: +globe …V. armillaire (sphère) +PR + +V. armillaire +sphère + + +

+ +

Cross-references occasionally occur in definition texts, example +texts, etc., or may be free-standing within an entry. These may +typically be encoded using ref or ptr, without an +enclosing xr. For example: + +entacher … Acte entaché de +nullité, contenant un vice de forme ou passé par un incapable*. DNT + The asterisk signals a reference to the entry for +incapable. +contenant un vice de forme ou passé par un . + + In +some cases, the form in the definition is inflected, and thus ref must +be used to indicate more exactly the intended target, as here: +justifier …4. IMPRIM Donner a (une ligne) une longeur +convenable au moyen de blancs (2, sens 1, 3). DNT + + +imprim +Donner a (une ligne) une longeur convenable au moyen de +blancs (2, sens 1, 3) + + + + + + + +... + + + + + + + +

+ + + + + + + + + + + + + + +
+
+Notes within Entries +

Dictionaries may include extensive explanatory notes about usage, grammar, +context, etc. within entries. Very often, such notes appear as a separate +section at the end of an entry. The standard note element should be used for +such material. + + +

+

For example: +neither + (ˈnaɪðə, ˈni:ðə) +determiner 1a not one nor the other (of two); + not either: neither foot is swollen … + usage A verb following a compound subject that uses neither… should be + in the singular if both subjects are in the singular: neither Jack nor John has done the work + CED + + +

+neither +ˈnaɪðə, +ˈni:ðə +
+ + +neither foot is swollen + +A verb following a compound subject + that uses neither… should be + in the singular if both subjects are in the singular: + neither Jack nor John has done the work + + + +

+

The formal declaration for note is given in section .

+
+
+
+Related Entries +

The re element encloses a degenerate entry which appears in the body of +another entry for some purpose. Many dictionaries include related entries for direct +derivatives or inflected forms of the entry word, or for compound words, phrases, +collocations, and idioms containing the entry word.

+

Related entries can be complex, and may in fact include any of the information to be +found in a regular entry. Therefore, the re element is defined to contain +the same elements as an entry element.

+

Examples: +bevvy + (ˈbɛvɪ) informal n, pl -vies 1 a drink, esp an + alcoholic one: we had a few bevvies last night 2 a session of drinking. ▷ vb + -vies, -vying, -vied (intr) + 3 to drink alcohol [probably from Old French bevee, +buvee, drinking] > 'bevvied adj CED + + +

+bevvy +ˈbɛvɪ +
+informal + + +n + + +a drink, esp. an alcoholic one: we had a few bevvies last night. + + + + + +vb + + +to drink alcohol + + +probably from Old French +bevee, buvee +drinking + + +
+bevvied +
+ +adj + + + + +

+ + + + + + + + + + + + + + + + + + +
+
+
+Headword and Pronunciation References +

Examples, definitions, etymologies, and occasionally other elements such as +cross-references, orthographic forms, etc., often contain a shortened or iconic reference to +the headword, rather than repeating the headword itself. The references may be to the +orthographic form or to the pronunciation, to the form given or to a variant of that +form. The following elements are used to encode such iconic references to a headword: + + + +

+

These elements all inherit the following attributes from the class att.pointing +which may optionally be used to resolve any +ambiguity about the headword form being referred to. + +

+

Headword references come in a variety of formats: + +indicates a reference to the full form of the headword + +gives a prefix to be affixed to the headword + +gives a suffix to be affixed to the headword + +gives the first letter in uppercase, indicating that the headword is +capitalized + +gives a prefix and a suffix to be affixed to the headword + +gives the initial of the word followed by a full stop, to indicate reference +to the full form of the headword + +refers to a capitalized form of the headword + +

+

The oRef element should be used for iconic or shortened references to the +orthographic form(s) of the headword itself. It is an empty element and replaces, rather +than enclosing, the reference. Note that the reference to a headword is not necessarily +a simple string replacement. In the example +colour1, (US = color) …~ films; ~ TV; Red, blue and yellow +are ~s. OALD, the tilde stands for either headword form +(colour, color).

+

Examples: +colonel … army officer above a lieutenant-~. OALD + +army officer above a lieutenant- + + + + + + + + + + + + +academy … The Royal A~ of Arts OALD + +The Royal of Arts + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

+

The following example demonstrates the use of the target attribute to refer to +a specific form of the headword: +vag- or vago- comb form … : vagus nerve +< vagal > < vagotomy +> W7 + + +

+vag- +vago- +
+vagus nerve + + +al + +tomy + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

+

In many cases the reference is not to the orthographic form of the headword, but rather +to another form of the headword—usually to an inflected form. In these cases, the +element oRef should be used; this element may take as its content the string as it +appears in the text. +take … < Mr Burton took us for +French > NPEG + + +Mr Burton took us for French + + + +take … < was quite ~n with him +> NPEG + + +was quite n with him + + +

+

The next example shows a discontinuous reference, using the +attributes +next and +prev, which are defined in the additional module for linking, +segmentation, and alignment (see chapter ) and therefore require that +that module be selected in addition to that for dictionaries. +mix up… < it's easy to mix her up with her sister > NPEG + + +it's easy to mix +her up with her sister + + +

+

In addition, some dictionaries make reference to the pronunciation of the headword in the +pronunciation of related entries, variants, or examples. The pRef +element should be used for such references. +hors d'oeuvre +/,aw'duhv (Fr O:r dœvr)/ n, pl hors d'oeuvres also hors +d'oeuvre /'duhv(z) (Fr ~)/ NPEG + +

+hors d'oeuvre +,aw'duhv + +Fr +O:r dœvr +
+ +
+pl +hors d'oeuvres +hors d'oeuvre +'duhv(z) + +Fr + + + +
+ + +

+

Because headword and pronunciation references can occur virtually anywhere in an entry, +the oRef and pRef elements may appear +within any other element defined for dictionary entries.

+

Since existing printed dictionaries use different conventions for headword references +(swung dash, first letter abbreviated form, capitalization, or italicization of the word, +etc.) the exact method used should be documented in the header.

+ + + + + + + + + + +
+
+Typographic and Lexical Information in Dictionary Data +

Among the many possible views of dictionaries, it is useful to distinguish at least the +following three, which help to clarify some issues raised with particular urgency by +dictionaries, on account of the complexity of both their typography and their +information structure. +(a) the typographic view—the +two-dimensional printed page, including information about line and page breaks +and other features of layout +(b) the editorial view—the one-dimensional sequence of tokens +which can be seen as the input to the typesetting process; the wording and +punctuation of the text and the sequencing of items are visible in this view, +but specifics of the typographic realization are not +(c) the lexical view—this view includes the underlying +information represented in a dictionary, without concern for its exact textual +form + +

+

For example, a domain indication in a dictionary entry might be broken over a line and +therefore hyphenated (naut- +ical); the typographic view of the dictionary preserves this information. In a +purely editorial view, the particular form in which the domain name is given in the +particular dictionary (as nautical, rather than naut., Naut., etc.) +would be preserved, but the fact of the line break would not. Font shifts might +plausibly be included in either a strictly typographic or an editorial view. In the +lexical view, the only information preserved concerning domain would be some standard +symbol or string representing the nautical domain (e.g. naut.) regardless of the +form in which it appears in the printed dictionary.

+

In practice, publishers begin with the lexical view—i.e., lexical data as it might +appear in a database—and generate first the editorial view, which reflects editorial +choices for a particular dictionary (such as the use of the abbreviation Naut. +for nautical, the fonts in which different types of information are to be +rendered, etc.), and then the typographic view, which is tied to a specific printed +rendering. Computational linguists and philologists often begin with the typographic +view and analyse it to obtain the editorial and/or lexical views. Some users may +ultimately be concerned with retaining only the lexical view, or they may wish to +preserve the typographic or editorial views as a reference text, perhaps as a guard +against the loss or misinterpretation of information in the translation process. Some +researchers may wish to retain all three views, and study their interrelations, since +research questions may well span all three views.

+

In general, an electronic encoding of a text will allow the recovery of at least one view +of that text (the one which guided the encoding); if editorial and typographic practices +are consistently applied in the production of a printed dictionary, or if exceptions to +the rules are consistently recorded in the electronic encoding, then it is in +principle possible to recover the editorial view from an encoding of the +lexical view, and the typographic view from an encoding of the editorial view. In +practice, of course, the severe compression of information in dictionaries, the variety +of methods by which this compression is achieved, the complexity of formulating +completely explicit rules for editorial and typographic practice, and the relative +rarity of complete consistency in the application of such rules, all make the mechanical +transformation of information from one view into another something of a vexed question.

+

This section describes some principles which may be useful in capturing one or the other +of these views as consistently and completely as possible, and describes some methods of +attempting to capture more than one view in a single encoding. Only the editorial and +lexical views are explicitly treated here; for methods of recording the physical or +typographic details of a text, see chapter . Other approaches to +these problems, such as the use of repetitive encoding and links to show their +correspondences, or the use of feature structures to capture the information structure, +and of the ana and inst attributes to link feature structures to a +transcription of the editorial view of a dictionary, are not discussed here (for +feature structures, see chapter . For linkage of textual form and +underlying information, see chapter ).

+
+Editorial View +

Common practice in encoding texts of all sorts relies on principles such as the +following, which can be used successfully to capture the editorial view when +encoding a dictionary: +All characters of the source text should be retained, with the possible +exception of rendition text (for which see further below). +Characters appearing in the source text should typically be given as +character data content in the document, rather than as the value of an +attribute; again, rendition text may optionally be excepted from this rule. +Apart from the characters or graphics in the source text, nothing else +should appear as content in the document, although it may be given in +attribute values. +The material in the source text should appear in the encoding in the same +order. Complications of the character sequence by footnotes, marginal notes, +etc., text wrapping around illustrations, etc., may be dealt with by the +usual means (for notes, see section ).Complications of sequence caused by marginal or interlinear +insertions and deletions, which are frequent in manuscripts, or by +unconventional page layouts, as in concrete poetry, magazines with +imaginative graphic designers, and texts about the nature of typography +as a medium, typically do not occur in dictionaries, and so are not +discussed here. + + +

+

In a very conservative transcription of the editorial view of a text, rendition +characters (e.g. the commas, parentheses, etc., used in dictionary +entries to signal boundaries among parts of the entry) and rendition +text (for example, conjunctions joining alternate headwords, etc.) are +typically retained. Removing the tags from such a transcription will leave all and +only the characters of the source text, in their original sequence.This is a slight oversimplification. Even in conservative +transcriptions, it is common to omit page numbers, signatures of gatherings, +running titles and the like. The simple description above also elides, for the +sake of simplicity, the difficulties of assigning a meaning to the phrase +original sequence when it is applied to the printed characters of a +source text; the original sequence retained or recovered from a +conservative transcription of the editorial view is, of course, the one +established during the transcription by the encoder. +

+

Consider, for example, the following entry: + pinna (ˈpɪnə) n, pl -nae (-ni:) or +-nas 1 any leaflet of a pinnate compound leaf 2 zoology +a feather, wing, fin, or similarly shaped part 3 another name for auricle (2). [C18: via New Latin from Latin: wing, +feather, fin] CED A conservative encoding of the editorial view of this +entry, which retains all rendition text, might resemble the following: + +

+pinna +ˈpɪnə +
+ +n, +
+pl + +-nae +(-ni:) +
or -nas + +1 any leaflet of a pinnate compound leaf + +2 zoology +a feather, wing, fin, or similarly shaped part + +3 +another name for +auricle (2) + + +[C18: via New Latin from Latin: +wing, feather, +fin] + + +
+ + +

+

A somewhat simplified encoding of the editorial view of this entry might exploit the +fact that rendition text is often systematically recoverable. For example, +parentheses consistently appear around pronunciation in this dictionary, and thus +are effectively implied by the start- and end-tags for pron.The omission of rendition text is particularly common in systems +for document production; it is considered good practice there, since automatic +generation of rendition text is more reliable and more consistent than +attempting to maintain it manually in the electronic text. In such an +encoding, removing the tags should exactly reproduce the sequence of characters in +the source, minus rendition text. The original character sequence can be recovered +fully by replacing tags with any rendition text they imply.

+

Encoding in this way, the example given above might resemble the following. The +tagUsage element in the header would be used to record the following +patterns of rendition text: +parentheses appear around pron elements +commas appear before inflected forms +the word or appears before alternate forms +brackets appear around the etymology +full stops appear after pos, inflection information, and sense +numbers +senses are numbered in sequence unless otherwise specified using the +global n attribute + + + +

+pinna +"pIn@ +
+ +n + +
+pl + +-nae +-ni: +
+-nas + + +any leaflet of a pinnate compound leaf. + + +Zoology +a feather, wing, fin, or similarly shaped part. + + + +another name for +auricle (sense 2). + + + +C18: via New Latin from Latin: +wing, feather, fin + + + +

+

When rendition text is omitted, it is recommended that the means to regenerate it be +fully documented, using the tagUsage element of the TEI header.

+

If rendition text is used systematically in a dictionary, with only a few mistakes or +exceptions, the global attribute rend may be used on any tag to flag +exceptions to the normal treatment. The values of the rend attribute are +not prescribed, but it can be used with values such as no-comma, +no-left-paren, etc. Specific values can be documented using the +rendition element in the TEI header.

+

In the following (imaginary) example, no left parenthesis precedes the +pronunciation: +biryani or biriani %bIrI"A:nI) any of a +variety of Indian dishes … [from Urdu] This irregularity can be recorded +thus: + +

+biryani +biriani +%bIrI"A:nI +
+any of a variety of Indian dishes … +from Urdu + + + +

+
+
+Lexical View +

If the text to be interchanged retains only the lexical view of the text, there may +be no concern for the recoverability of the editorial (not to speak of the +typographic) view of the text. However, it is strongly recommended that the TEI +header be used to document fully the nature of all alterations to the original data, +such as normalization of domain names, expansion of inflected forms, etc.

+

In an encoding of the lexical view of a text, there are degrees of departure from the +original data: normalizing inconsistent forms like nautical, naut., +Naut., etc., to nautical is a relatively slight alteration; +expansion of delay -ed -ing to delay, delayed, delaying is a more +substantial departure. Still more severe is the rearranging of the order of +information in entries; for example: +reorganizing the order of elements in an entry to show their +relationship, as in clem (klɛm) +or clam vb clems, clemming, clemmed + or clams, clamming, clammed CED where in a strictly lexical view one +might wish to group clem and clam with their respective +inflected forms. +splitting an entry into two separate entries, as in +celi.bacy /"selIb@sI/ n [U] state of living +unmarried, esp as a religious obligation. celi.bate /"selIb@t/ n [C] +unmarried person (esp a priest who has taken a vow not to marry). +OALD For some purposes, this entry might usefully be split into an +entry for celibacy and a separate entry for celibate. + +

+

An encoding which captures the lexical view of the example given in the previous +section might look something like the following. In this encoding: +abbreviated forms have been silently expanded +some forms have been moved to allow related forms to be grouped together +the part of speech information has been moved to allow all forms to be +given together +the cross-reference to auricle has been simplified + + + +

+pinna +"pIn@ + +pl + +pinnae +'pIni: +
+pinnas + + + +n + + +any leaflet of a pinnate compound leaf. + + +Zoology +a feather, wing, fin, or similarly shaped part. + + + + + + + +C18: via New Latin from Latin: +wing, feather, fin + + + +

+

Whether the given dictionary encoding focusses on the lexical view and thus approaches the status of +lexical databases, or uses the typographic/editorial view approach and needs to communicate the +sometimes informally stated values for the particular descriptive features, the issue of interoperability +of the content and of the container objects becomes relevant, in view of the growing +tendency to interlink pieces of information across Internet resources. In such +cases, it becomes crucial to be able to encode the fact that whether the information on, +for instance, the value of the grammatical category of Number is provided as sg., sing., Singular, or +equivalently poj. in Polish, or Ez. in German, etc., what is actually referred to is always the same +grammatical value that can be rendered with a plethora of markers, depending on the publisher, language, or lexicographic tradition. +In order to signal that this variety of surface markers in fact indicate the same +underlying value, it is possible to align them with an external inventory of standardized +values. The TEI provides the att.datcat attribute class for the purpose of aligning grammatical (or indeed any sort of) categories as well as their values +with a reference taxonomy of shared data categories.

+

In the example below, a fragment of the entry for isotope cited +in section is adorned by references to standardized definitions for part +of speech (datcat) and adjective (valueDatcat). Depending +on the status and extent of the dictionary, various strategies may be used to reduce the +redundancy of references. + + +

+isotope +
+ +adj + + + + +In the above example, alignment is performed against the CLARIN Concept Registry.

+
+
+Retaining Both Views +

It is sometimes desirable to retain both the lexical and the editorial view, in which +case a potential conflict exists between the two. When there is a conflict between +the encodings for the lexical and editorial views, the principles described in the +following sections may be applied.

+
+Using Attribute Values to Capture Alternate Views +

If the order of the data is the same in both views, then both views may be +captured by encoding one dominant view in the character +data content of the document, and encoding the other using attribute values on +the appropriate elements. If all tags were to be removed, the remaining +characters would be those of the dominant view of the text.

+

The attribute class att.lexicographic (which +includes the attributes norm and org from class att.lexicographic.normalized) +is used to provide attributes for use in encoding multiple views of the same dictionary +entry. These attributes are available for use on all elements defined in this +chapter when the base module for dictionaries is selected.

+

When the editorial view is dominant, the following attributes may be used to +capture the lexical view: + + +

+

When the lexical view is dominant, the following attributes may be used to record +the editorial view: + + + +

+

One attribute is useful in either view: + + +

+

For example, if the source text had the domain label naut., it might be +encoded as follows. With the editorial view dominant: +naut. + The lexical view of the same label would transcribe the normalized form +as content of the usg element, the typographic form as an attribute +value: +nautical + +

+

If the source text gives inflectional information for the verb +delay as delay, -ed, -ing, it might usefully be +expanded to delayed, delayed, delaying. An encoding of the editorial view +might take this form: +

+delay + +-ed + + +
+-ing + + + + Note the use of the tns tag with null content, to enable the +representation of implicit information even though it has no print realization.

+

The lexical view might be encoded thus: +

+delay + +delayed +pst +pstp +
+
+delaying +prsp +
+ + +

+ + + +

A particular problem may be posed by the common practice of presenting two +alternate forms of a word in a single string, by marking some parts of the word +as optional in some forms. The following entry is for a word which can be +spelled either thyrostimuline or thyréostimuline: +thyr(é)ostimuline [tiR(e)ostimylin] … With the +editorial view dominant, this entry might begin thus: +

+thyr(é)ostimuline +tiR(e)ostimylin +
+ + +With the lexical view dominant, however, two orth and +two pron elements would be encoded, in order to disentangle the two +forms; the orig attribute would be used to record the typographic +presentation of the information in the source. +
+thyrostimuline +tiRostimylin +
+
+thyréostimuline +tiReostimylin +
+ + +

+ +

This example might also be encoded using the opt attribute combined +with the attributes next and prev defined in chapter . +

+thyr +é +ostimuline +tiR +e +ostimylin +
+ +

+

Note that this transcription preserves both the lexical and +editorial views in a single encoding. However, it has the disadvantage +that the strings corresponding to entire words do not appear in the +encoding uninterrupted, and therefore complex processing is required +to retrieve them from the encoded text. The use of the opt +attribute is recommended, however, when long spans of text are +involved, or when the optional part contains embedded tags.

+ +

For example, the following gives two definitions in one text: +picture drawn with coloured chalk made into crayons, and +coloured chalk made into crayons: + pas.tel /"pastl US: pa"stel/ n +1 (picture drawn with) coloured chalk made into crayons. 2… OALD

A simple encoding solution +would be to leave the definition text unanalysed, but this might be +felt inadequate since it does not show that there are two +definitions. A possible alternative encoding would be: coloured +chalk made into crayons picture drawn with coloured chalk +made into crayons

This transcribes +some characters of the source text twice, however, which deviates from +the usual practice. The following encoding records both the editorial +and lexical views: + picture drawn +with coloured chalk made into +crayons

+ +
+
+Recording Original Locations of Transposed Elements +

The attributes described in the previous section are useful only when the order +of material is the same in both the editorial and the lexical view. When the two +views impose different orders on the data, the standard linking mechanisms may be used to +show the original location of material transposed in an encoding of the lexical +view.

+

If the original is only slightly modified, the anchor element may be +used to mark the original location of the material, and the location +attribute may be used on the lexical encoding of that material to indicate its +original location(s). Like those in the preceding section, this attribute is +defined for the attribute class att.lexicographic: + + +

+

For example: +pinna + (ˈpɪnə) n, pl + -nae (-ni:) or -nas CED + +

+pinna +ˈpɪnə + + +pl + +-nae +-ni: + +-nas + + + +n + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

+
+
+ +
+
+Unstructured Entries + +

The content model for the entry element provides an entry +structure suitable for many average dictionaries, as well as many +regular entries in more exotic dictionaries. However, the structure +of some dictionaries does not allow the restrictions imposed by the +content model for entry. To handle these cases, the +entryFree and dictScrap elements are provided to +support much wider variation in entry structure. The +dictScrap element offers less freedom, in that it can only +contain phrase level elements, but it can itself appear at any point +within a dictionary entry where any of the structural components of a +dictionary entry are permitted. As such, it acts as a container for +otherwise anomalous parts of an entry.

+ +

The entryFree element places no constraints at all upon +the entry: any element defined in this chapter, as well as all the +normal phrase-level and inter-level elements, can +appear anywhere within it. With the entryFree element, the +encoder is free to use any element anywhere, as well as to use or omit +grouping elements such as form, gramGrp, etc.

+ +

The entryFree element allows the encoding of entries which +violate the structure specified for the entry element. For +example, in the following entry from a dictionary already in +electronic form, it is necessary to include a pron element +within a def. This is not permitted in the content model for +entry, but it poses no problem in the entryFree +element. demi|god "demIgQd one who is partly divine and partly human +(in Gk myth, etc) the son of a god and a mortal woman, +egHercules "h3:kjUli:z + ]]> + + +

+demigod +demi|god +"demIgQd +
+ +n + +one who is partly divine and partly human +(in Gk myth, etc) the son of a god and a mortal woman, eg +Hercules +"h3:kjUli:z + + +

+

The entryFree element also makes it possible to transcribe a dictionary using +only phrase-level (atomic) elements—that is, using no grouping +elements at all. This can be desirable if the encoder wants a completely +flat view, with no indication of or commitment to the association +of one element with another. The following encoding uses no grouping elements, and keeps +all rendition text: + biryani or biriani + (ˌbɪrɪˈa:nɪ) n any of a variety of Indian dishes … [from +Urdu] CED + + +biryani or biriani +(ˌbɪrɪˈa:nɪ) +any of a variety of Indian dishes … +[from Urdu] + + +

+

Here is an alternative way of representing the same structure, this time using +dictScrap: + + +biryani or biriani +(ˌbɪrɪˈa:nɪ) +any of a variety of Indian dishes … +[from Urdu] + + + +

+
+
+ The Dictionary Module +

The module defined in this chapter makes available the following + components: + + Dictionaries + Dictionaries + Dictionnaires + 紙本字典 + Dizionari a stampa + Dicionários impressos + 辞書モジュール + + + The selection and combination of modules to form a TEI schema is + described in .

+
+
diff --git a/P5/Source/Guidelines/fr/DR-PerformanceTexts.xml b/P5/Source/Guidelines/fr/DR-PerformanceTexts.xml deleted file mode 120000 index 496d5b8806..0000000000 --- a/P5/Source/Guidelines/fr/DR-PerformanceTexts.xml +++ /dev/null @@ -1 +0,0 @@ -../en/./DR-PerformanceTexts.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/DR-PerformanceTexts.xml b/P5/Source/Guidelines/fr/DR-PerformanceTexts.xml new file mode 100644 index 0000000000..88741a884c --- /dev/null +++ b/P5/Source/Guidelines/fr/DR-PerformanceTexts.xml @@ -0,0 +1,1456 @@ + + + + + + + +
Performance Texts +

This module is intended for use when encoding printed dramatic +texts, screen plays or radio scripts, and written transcriptions of any +other form of performance. +

+

Section discusses elements such as cast lists, +which can appear only in the front or back matter of printed dramatic +texts. Section discusses the structural +components of performance texts: these include major structural +divisions such as acts and scenes (section ); +individual speeches (section ); groups of +speeches (section ); stage directions +(section ); and the elements making up individual +speeches (section ). Section +discusses ways of encoding units which cross the simple hierarchic +structure so far defined, such as embedded songs or masques. +Finally, section discusses a small number of +additional elements characteristic of screen plays and radio or +television scripts, as well as some elements for representing +technical stage directions such as lighting or blocking.

+ +

The default structure for dramatic texts is similar to that +defined by chapter , as further discussed in +section .

+ +

Two element classes are used by this module. +The model.frontPart.drama class supplies +specialized elements which can appear only in the front or back matter +of performance texts. The model.stageLike +class supplies a set of elements for stage directions and similar +items such as camera movements, which can occur between or within +speeches.

+ + + + + +
Front and Back Matter + +

In dramatic texts, as in all TEI-conformant documents, the header +element is followed by a text element, which contains optional +front and back matter, and either a body or else a +group of nested text elements. For more information +on these, see chapter . +

+

The front and back elements are most likely to be +of use when encoding preliminary materials in published performance +texts. When the module defined by this chapter is included in a +schema, the following additional elements not generally +found in other forms of text become available as part of the front or +back matter: + +

+ +

Elements for encoding each of these specific kinds of front matter +are discussed in the remainder of this section, in the order given +above. In addition, the front matter of dramatic texts may include +the same elements as that of any other kind of text, notably title +pages and various kinds of text division, as discussed in section . The encoder may choose to ignore the specialized +elements discussed in this section and instead use constructions of +the type div type="performance" or div1 +type="set". +

+ +

Most other material in the front matter of a performance text will be +marked with the default text structure elements described in chapter +. For example, the title +page, dedication, other commendatory material, preface, etc., in a +printed text should be encoded using div or div1 +elements, containing headings, paragraphs, and other core tags. +

+ + + + + + + +
The Set Element +

A special form of note describing the setting of a dramatic text +(that is, the time and place of its action) is sometimes found in the +front matter. + +Descriptions of the setting may also appear as initial stage directions +in the body of the play, but such descriptions should be marked as stage +directions, not set. The set element should be used +only where the description forms part of the front matter, as in the +following examples: + + + ... + +

The action of the play is set in Chicago's + Southside, sometime between World War II and the + present.

+ + + + Peer Gynt + +
+
+
+
+ Note on the Translation +

...

+
+
+ Characters + +
+

The action, which opens in the beginning of the nineteenth + century, and ends around the 1860s, takes place partly in + Gudbrandsdalen, and on the mountains around it, partly on the coast + of Morocco, in the desert of Sahara, in a madhouse at Cairo, at sea, + etc.

 +

+ + +

+ + + + + +
+
Prologues and Epilogues +

Many plays in the Western tradition include in their front matter a +prologue, spoken by an actor, generally not in character. Similar +speeches often also occur at the end of the play, as epilogues. The +elements prologue and epilogue are provided for the +encoding of such features within the front or back matter, where +appropriate. + +A prologue may be encoded just like a distinct poem, as in the following +example: + + + Prologue, spoken by Mr. Hart + Poets like Cudgel'd Bullys, never do + At first, or second blow, submit to you; + But will provoke you still, and ne're have done, + Till you are weary first, with laying on: + We patiently you see, give up to you, + Our Poets, Virgins, nay our Matrons too. + + + The Persons + ... + + The SCENE +

London

+ + + + +

+

A prologue or epilogue may also be encoded as a speech, using the +sp element described in section . This is +particularly appropriate where stage directions, etc., are involved, as +in the following example: + + Written by Colley Cibber, Esq + and spoken by Mrs. Cibber + + + Since Fate has robb'd me of the hapless Youth, + For whom my heart had hoarded up its truth; + By all the Laws of Love and Honour, now, + I'm free again to chuse, — and one of you + + + Suppose I search the sober Gallery; — No, + There's none but Prentices — & Cuckolds all a row: + And these, I doubt, are those that make 'em so. + + Pointing to the Boxes. + + 'Tis very well, enjoy the jest: + + + + +

+

In cases where the prologue or epilogue is clearly a significant part +of the dramatic action, it may be preferable to include it in the body +of a text, rather than in the front or back matter. In such cases, the +encoder (and theatrical tradition) will determine whether or not to +regard it as a new scene or division, or simply the final speech in the +play. In the First Folio version of Shakespeare's +Tempest, for example, Prospero's final speech is clearly +marked off as a distinct textual unit by the headings and layout of the +page, and might therefore be encoded as back matter: + + + + + I'le deliver all, + And promise you calme Seas, auspicious gales, + Be free and fare thou well: please you, draw neere. + Exeunt omnes. + + + + + + Epilogue, spoken by Prospero. + + Now my Charmes are all ore-throwne, + And what strength I have's mine owne + As you from crimes would pardon'd be, + Let your Indulgence set me free. + Exit + + +

The Scene, an un-inhabited Island.

+ + + Names of the Actors. + Alonso, K. of Naples + Sebastian, his Brother. + Prospero, the right Duke of Millaine. + + FINIS + + + +

+

In many modern editions, the editors have chosen to regard +Prospero's speech as a part of the preceding scene: + + Prospero + I'll deliver all, + And promise you calm seas, auspicious gales, + Be free and fare thou well. Exit Ariel + Please you, draw near. Exeunt all but Prospero + Epilogue + Now my charms are all o'erthrown, + And what strength I have's mine own + As you from crimes would pardoned be, + Let your indulgence set me free. + +He awaits applause, then exit. + + +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+
Records of Performances +

Performance texts are not only printed in books to be read, they are +also performed. It is common practice therefore to include within the +front matter of a printed dramatic text some brief account of particular +performances, using the following element: + +The performance element may be used to group any and all +information relating to the actual performance of a play or screenplay, +whether it specifies how the play should be performed in general or how +it was performed in practice on some occasion. +

+

Performance information may include complex structures such as cast +lists, or paragraphs describing the date and location of a performance, +details about the setting portrayed in the performance and so forth. +(See the discussion of these specialized structures in section above.) If +information for more than one performance is being recorded, then more +than one performance element should be used, wherever possible. +

+

Names of persons, places, and dates of particular significance within +the performance record may be explicitly marked using the general +purpose name, rs type="place" and date +elements described in section . +No particular elements for such features as stagehouses, +directors, etc., are proposed at this time. +

+

For example: + + Death of a Salesman +

A New Play by Arthur Miller

+

Staged by Elia Kazan

+ + Cast + (in order of appearance) + + Willy Loman + Lee J. Cobb + + + Linda + Mildred Dunnock + + + Biff + Arthur Kennedy + + + Happy + Cameron Mitchell + + + +

The setting and lighting were designed by + Jo Mielziner.

+

The incidental music was composed by Alex North.

+

The costumes were designed by Julia Sze.

+

Presented by Kermit Bloomgarden + and Walter Fried at the + Morosco Theatre in New York on + February 10, 1949.

+ + + + + + +Or: + +

La Machine Infernale a été + représentée pour la première fois au + théâtre Louis-Jouvet + (Comédie des + Champs-élysées) le 10 avril 1934, + avec les décors et les costumes de + Christian Bérard. ...

+ + +

+ + + + + + + + + + + + + + + +
+
Cast Lists +

A cast list is a specialized form of list, +conventionally found at the start or end of a play, usually listing all +the speaking and non-speaking roles in the play, often with additional +description (Cataplasma, a maker of Periwigges and Attires) or +the name of an actor or actress (Old Lady Squeamish. Mrs +Rutter). Cast lists may be encoded with the general purpose +list element described in section , but for +more detailed work the following specialized elements are provided: + +

A castItem element may contain any mixture of elements +taken from the model.castItemPart class, +members of which (when this module is included) are: + + +Cast lists often have an internal structure of their own; it is quite +usual to find, for example, nobility and commoners, or male and female +roles, presented in different groups or sublists. Roles are also often +grouped together by their function, for example: + +Sons of Cato: + +Portius +Marcus +

+

A cast list relating to a specific performance may be accompanied by +notes about the time or place of that performance, indicating (for +example) the name of the theatre where the play was first presented, the +name of the producer or director, and so forth. When the cast list +relates to a specific performance, it should be embedded within a +performance element (see section ), as in +the following example: + +

The first performance in Great Britain of Waiting for + Godot was given at the Arts Theatre, London, on + 3rd August 1955. It was directed by + Peter Hall, and the décor was by Peter + Snow. The cast was as follows:

+ + Estragon: Peter Woodthorpe + Vladimir: Paul Daneman + ... + + + +

+

In this example, the castItem elements have no substructure. +If desired, however, their components may be more finely distinguished +using the elements role, roleDesc, and actor. +For example, the second cast item above might be encoded as follows: + + Vladimir: + Paul Daneman + +

+

The ref attribute on actor may be used to associate the name +with information about the real-world person identified, as further discussed in section ND. In the previous example, +we might associate the name of Paul Daneman with his entry in a widely used bibliography as follows : + + Paul Daneman +

+

The global xml:id attribute may be used to specify a unique +identifier for the role element, where it is desired to link +speeches within the text explicitly to the role, using the +who attribute, as further discussed in section below. +

+

The occasionally lengthy descriptions of a role sometimes found in +written play scripts may be marked using the roleDesc element, +as in the following example: + + Tom Thumb the Great + a little hero with a great soul, something violent in his + temper, which is a little abated by his love for Huncamunca + Young Verhuyk + + +For non-speaking or un-named roles, a castItem may contain a +roleDesc without an accompanying role, for example + + Costermonger + +

+

When a list of such minor roles is given together, the +type attribute of the castItem should indicate that +it contains more than one role, by taking a value such as list. The encoder may or may not elect to +encode each separate constituent within such a composite +castItem. Thus, either of the following is acceptable: +Constables, Drawer, Turnkey, etc. + + Constables, + Drawer, + Turnkey, + etc. + +

+

A group of cast items forming a distinct subdivision of a cast list +may be marked as such by using the special purpose castGroup +element. The rend attribute may be used to indicate +whether this grouping is indicated in the text by layout alone (i.e. the +use of whitespace), by long braces or by some other means. A +castGroup may contain an optional heading (represented as +usual by a head element) followed by a series of +castItem elements: + + friends of Mathias + + Walter + Mr Frank Hall + + + Hans + Mr F.W. Irish + + + +

+

Alternatively, the encoder may prefer to regard the phrase +friends of Mathias as a role description, and encode the above +example as follows: + + friends of Mathias + + Walter + Mr Frank Hall + + + Hans + Mr F.W. Irish + + +

+

This version has the advantage that all role descriptions are treated +alike, rather than in some cases being treated as headings. On the +other hand there are also cases, such as the following, where the +role description does function more like a heading: + + + + Mendicants + Aafaa Femi Johnson + Blindman Femi Osofisan + Goyi Wale Ogunyemi + Cripple Tunji Oyelana + + Si Bero + Sister to Dr Bero + Deolo Adedoyin + + Two old women + Iya Agba Nguba Agolia + Iya Mate Bopo George + + Dr Bero + Specialist + Nat Okoro + Priest Gbenga Sonuga + The old man + Bero's father + Dapo Adelugba + + +

+ + + + + + + + +
+
+
The Body of a Performance Text +

The body of a performance text may be divided into structural +units, variously called acts, scenes, stasima, entr'actes, etc. All +such formal divisions should be encoded using an appropriate +text-division element (div, div1, div2, +etc.), as further discussed in section . +Whether divided up into such units or not, all performance texts +consist of sequences of speeches (see ) and stage +directions (see ). In musical performances, it +is also common to identify groups of speeches which act as a single +unit, sometimes called a number; such units typically +float within the structural hierarchy at the same level as speeches +preceding or following them and cannot therefore be treated as +text-divisions. (see ). Speeches will generally +consist of a sequence of chunk-level items: paragraphs, +verse lines, stanzas, or (in case of uncertainty as to whether +something is verse or prose) ab elements (see ).

+

The boundaries of formal units such as verse lines or paragraphs do +not always coincide with speech boundaries. Units such as songs may be +discontinuous or shared among several speakers. As described below in +section , such fragmentation may be encoded in a +relatively simple fashion using the linkage and aggregation mechanisms +defined in chapter .

+
Major Structural Divisions +

Large divisions in drama such as acts, scenes, stasima, or entr'actes +are indicated by numbered or unnumbered div elements, as +described in section . The type and +n attributes may be used to define the type of division being +marked, and to provide a name or number for it, as in the following +example: + + + Night—Faust's Study (i) + + + Outside the City Gate + + +

+

Where the largest divisions of a performance text are themselves +subdivided, most obviously in the case of plays traditionally divided +into acts and scenes, further nested text-division elements may be used, +as in this example: + + + Act One + + Pa Ubu, Ma Ubu + Pa Ubu

Pschitt!

+ + + A room in Pa Ubu's house, where a magnificent + collation is set out + + + + Act Two + + Scene One + + + Scene Two + + + +

+

In the example above, the div2 element has been used to +represent the French scene convention, (where the +entrance of each new set of characters is marked as a distinct unit in +the text) and the div1 element to represent the acts into which +the play is divided. The elements chosen are determined only by the +hierarchic position of these units in the text as a whole. If the text +had no acts, but only scenes, then the scenes might be represented by +div1 elements. Equally, if a play is divided only into +acts, with no smaller subdivisions, then the div1 +element might be used to represent acts. The type should be +used, as above, to make explicit the name associated +with a particular category of subdivision.

+

As an alternative to the use of numbered +divisions, the encoder may represent all subdivisions with the same +element, the unnumbered div. The second +act in the above example would then be represented as follows: +

+ Act Two +
+ Scene One +
+
+ Scene Two +
+

+

For further discussion of the use of numbered and unnumbered +divisions, see section .

+
Speeches and Speakers +

The following elements are used to identify speeches and speakers in +a performance text: +

+

As noted above, the structure of many performance texts may be +analysed as multiply hierarchic: a scene of a verse play, for example, +may be divided into speeches and, at the same time, into verse lines. +The end of a line may or may not coincide with the end of a speech, and +vice versa. Other structures, such as songs, may be discontinuous or +split up over several speeches. For some purposes it will be +appropriate to regard the verse-structure as the fundamental organizing +principle of the text, and for others the speech structure; in some +cases, the choice between the two may be arbitrary. The discussion in +the remainder of this chapter assumes that it is the speech-based +hierarchy which most prominently determines the structure of performance +texts, but the same mechanisms could be employed to encode a view of a +performance text in which individual speeches were entirely subordinate +to the formal units of prose and verse. For more detailed discussion and +examples of various treatments of this fundamental issue, refer to +chapter .

+

The who attribute and the speaker element are +both used to indicate the speaker or speakers of a speech, but in +rather different ways. The speaker element is used to encode +the word or phrase actually used within the source text to indicate +the speaker: it may contain any string or prefix, and may be thought +of as a highly specialized form of stage direction. The +who attribute however contains one or more pointer values, +each of which indicates one or more other XML elements documenting the +character to whom the speech is assigned. Typically, this attribute +might point to a person element in the TEI header , to a role element in the cast list , or even to some external source such as an online +handbook of dramatic roles. The most usual case is that the pointer +value supplied (prefixed by a sharp sign) corresponds with the value +of an xml:id attribute, +used elsewhere in the document to identify a particular element, as in the following examples: + + + Menaechmus + Peniculus + + Menaechmus + Responde, adulescens, quaeso, quid nomen tibist? + Peniculus + Etiam derides, quasi nomen non noveris? + Menaechmus + Non edepol ego te, quot sciam, umquam ante hunc diem + Vidi neque novi; ... +

+

If present, a speaker element may only appear as the first +part of an sp element. The distinction between the +speaker element and the who attribute makes it +possible to encode uniformly characters whose names are not indicated in +a uniform fashion throughout the play, or characters who appear in +disguise, as in the following examples: + + Henry Higgins + + + The Notetaker +

...

+ +

+

If the speaker attributions are completely regular (and may thus be +reconstructed mechanically from the values given for the who +attribute), or are of no interest for the encoder of the text (as might +be the case with editorially supplied attributions in older texts), then +the speaker element need not be used; the former example above +then might look like this: + + Menaechmus + Peniculus + +Responde, adulescens, quaeso, quid nomen tibist? +Etiam derides, quasi nomen non noveris? +Non edepol ego te, quot sciam, umquam ante hunc diem + Vidi neque novi; ... +

+

More than one identifier may be listed as value for the who +attribute if the speech is spoken by more than one person, as in the +following example: + + + Nano + Castrone + + Nano and Castrone sing + + Fools, they are the only nation + Worth men's envy or admiration + + +

+

In the event there is a speech that is assigned to a +character that is not listed in the source cast list, a +castList may be encoded inside the standOff +element to provide an element to which the who of +sp may point.

+

The sp and speaker elements are both declared +within the core module (see section ).

+ +
Grouped Speeches +

This module makes available the following additional element for +handling groups of speeches:

+

The spGrp element is intended for cases where +the characters in a performance launch into something which might be +regarded almost as a kind of separate structural division, typically +associated with its own heading or numbering system, but which +floats in the text, at the same hierarchic level +as speeches preceding or following it. Such units are often numbered, +titled, and visually presented as distinct objects within the +text. Here is a typical example from a well-known American musical comedy: + +By Strauss : performed by Georges Guetary, Gene Kelly, and Oscar +Levant +HENRI BAUREL +The waltzes of Mittel Europa +They charm you and warm you within +While each day discloses +What Broadway composes +Is emptiness pounding on tin. + + +JERRY MULLIGAN: ADAM COOK: +Mein Herr! +Mein Herr! +Bitte, bitte! +Denke, danke! +Aufwiedersehen! Aufwiedersehen! + +HENRI BAUREL: +How can I be civil +When hearing this drivel? +It's only for night-clubbing souses. +Oh give me the free 'n easy +Waltz that is Viennes-y +And go tell the band +If they want a hand +The waltz must be Strauss's + +ALL +Ya ya ya +Give me oom pah pah... + + + +

+
+
Stage Directions +

Both between and within the speeches of a written performance text, +it is normal practice to include a wide variety of descriptive +directions to indicate non-verbal action. The following elements are +provided to represent these: + + + +

+

A satisfactory typology of stage directions is difficult to define. +Certain basic types such as entrance, exit, +setting, delivery, are easily identified. But the list is +not a closed one, and it is not uncommon to mix types within a single +direction. No closed set of values for the type attribute is +therefore proposed at the present time, though some suggested values are +indicated in the list below, which also indicates the range of +possibilities. +The throne descends. +Music +Enter Husband as being thrown off his horse. +Exit pursued by a bear. +He quickly takes the stone out. +To Lussurioso. +Aside. +Not knowing what to say. +Disguised as Ansaldo. +At a window. +Having had enough, and embarrassed + for the family.

+

The meaning of the values used for the type attribute on +stage elements may be defined within the tagUsage +element of the TEI header (described in section ). +For example: +This element is used for all stage directions, + editorial or authorial. The type attribute on this element takes + one or more of the following values: + + + describes the set + + describes movement across stage, position, etc. + + describes movement other than blocking + + describes how the line is said + + describes character's emotional state or through line + +

+

This approach is purely documentary; in a real project it would generally be more effective to define the range of +permitted values explicitly within the project's schema specification, +using the techniques described in chapter . For +example, a specification like the following might be used to produce a +schema in which the type attribute of the +stage element is permitted to take only the values listed +above: + + + + + + + + + + + +describes the set +describes movement across stage, position, etc. +describes movement other than blocking +describes how the line is said +describes character's emotional state or through line + + + +

+

The stage element may appear both between and within +sp elements. It may contain a mixture of phrase level +elements, possibly combined into paragraphs, as in the following +example: + + +

Scene. — A room furnished comfortably and +tastefully but not extravagantly ... +The floor is carpeted and a fire burns in the stove. +It is winter.

+

A bell rings in the hall; shortly afterwards the +door is heard to open. Enter NORA humming a tune ...

+ +Nora +

Hide the Christmas Tree carefully, Helen. Be sure the +children do not see it till this evening, when it is +dressed. To the PORTER taking +out her purse How much?

+ + +

+

The stage element may also be used in non-theatrical +texts, to mark sound effects or musical effects, etc., as further +discussed in section .

+

The move element is intended to help overcome the fact that +the stage directions of a printed text may often not provide full +information about either the intended or the actual movement of actors +on stage. It may be used to keep track of entrances and exits in +detail, so as to know which characters are on stage at which time. Its +attributes permit a relatively formal specification for movements of +characters, using user-defined codes to identify the characters involved +(the who attribute), the direction of the movement +(type attribute), and optionally which part of the stage is +involved (where attribute). For stage-historical purposes, a +perf attribute is also provided; this allows the recording of +different move elements +as taken in different performances of the same text.

+

The move element should be located at the position in the +text where the move is presumed to take place. This will often coincide +with a stage direction, as in the following simple example: + +Bellafront + + + Enter Bellafront mad.

+

The move element can however appear independently of a stage +direction, as in the following example: + +Lady Macbeth +First Gentleman + + Gent. +

Neither to you, nor any one; having no witness +to confirm my speech. +Lo you! here she comes. This is her very guise; and, +upon my life, fast asleep.

+

+ + + + +
+
Speech Contents +

The actual speeches of a dramatic text may be composed of running +text, which must be formally organized into paragraphs, in the case of +prose (see section ), verse lines or line groups in +that of verse (see section ), or seg +elements, in case of doubt as to whether the material should be treated +as verse or prose. The following elements, all of which are defined in +the core, are particularly useful when marking units of prose or verse within +speeches: +

+

Like other milestone elements, the element lb additionally bears the attributes +ed and edRef, from its membership in the class +att.edition: + + + +

+

As a member of the classes att.typed +and att.divLike, the +lg element +also bears the following attributes: + + + + +

+ +

When the verse module is included in a +schema, the elements l +and lg also gain additional attributes through their +membership of the class att.metrical: + +

+ + +

In many texts, prose and verse may be inextricably mingled; +particularly in earlier printed texts, prose may be printed as verse or +verse as prose, or it may be impossible to distinguish the two. In +cases of doubt, an encoder may prefer to tag the dubious material +consistently as verse, to tag it all as prose, to follow the typography +of the source text, or to use the neutral ab +element to contain the speech itself. When this question arises, the +tagUsage element in the encodingDesc element of the +header may be used to record explicitly what policy has been adopted.

+

Even where they can reliably be distinguished, a single speech may frequently +contain a mixture of prose (marked as p) and verse (marked as +l or—if stanzaic—lg).

+ +

The part attribute which both l and lg +elements inherit from the att.fragmentable class provides one simple way of indicating where the boundaries of a +speech and of a verse line or line group do not coincide. The encoder +may simply indicate that a line or line group is metrically incomplete by +specifying the value Y or N, as in the following example: +FaceYou most +notorious whelp, you insolent slave +Dare you do this? +SubtleYes faith, yes faith. +FaceWhy! Who +Am I, my mongrel? Who am I? +SubtleI'll tell you, + +

+

Alternatively, where the fragments of the line or line group are +consecutive in the text (though possibly interrupted by stage +directions), the values I (initial), M (medial), and F (final) +may be used to indicate how metrical lines are constituted: + FaceYou most +notorious whelp, you insolent slave +Dare you do this? +SubtleYes faith, yes faith. +FaceWhy! Who +Am I, my mongrel? Who am I? +SubtleI'll tell you, + + +

+

In dramatic texts, the lg or line group element is most +often of use for the encoding of songs and other stanzaic material. Line groups may be fragmented +across speakers in the same way as individual lines, and the same set of +attributes may be used to record this fact. The element +spGrp is provided in order to simplify the situation, very +common in performances, where performance of a single entity, such as +a song, is shared amongst several performers, as in the following +example: + +Song — Sir Joseph + + I am the monarch of the sea, + The ruler of the Queen's Navee. + Whose praise Great Britain loudly chants. + + + Cousin Hebe + And we are his sisters and his cousins and his aunts! + + + Rel. + And we are his sisters and his cousins and his aunts! + + + + +

+

This encoding however does not indicate that the three lines of +Sir Joseph's song and the two lines following it together constitute a +single verse stanza. This can be indicated by using the part +attribute, as follows: + +Song — Sir Joseph + + I am the monarch of the sea, + The ruler of the Queen's Navee. + Whose praise Great Britain loudly chants. + + + Cousin Hebe + And we are his sisters and his cousins and his aunts! + + + Rel. + And we are his sisters and his cousins and his aunts! + + + + +

+
+
Embedded Structures +

Although primarily composed of speeches, performance texts often +contain other structural units such as songs or strophes which are +shared among different speakers. More generally, complex nested +structures of plays within plays, interpolated masques, or interludes +are far from uncommon. In more modern material, comparably complex +structural devices such as flashback or nested playback are equally +frequent. In all kinds of performance material, it may be necessary to +indicate several actions which are happening simultaneously.

+

A number of different devices are available within the TEI scheme to +support these complexities in the general case. Texts may be composite +or self-nesting (see section ) and multiple +hierarchies may be defined (see chapter ). The TEI +encoding scheme provides a variety of linking mechanisms, which may be +used to indicate temporal alignment and aggregation of fragmented +structures. In this section we provide a few specific examples of the +application of these techniques to performance texts: + +the use of the floatingText element +the use of the part attribute on fragmentary +lg elements +the use of the next and prev attributes on +fragments of embedded structures to join them into a larger whole +the use of the join element to define a +virtual element composed of the fragments +indicated +

+

When the whole of a song appears within a single speech, it may +require no special treatment if it is considered to form a part +of the speech: Kelly + (calmly). +

Aha, so you've bad minds along with th' love of gain. + You thry to pin on others th' dirty decorations that + may be hangin' on your own coats.

+ (He points, one after the other at Conroy, Bull, + and Flagonson. Lilting) + + Who were you with last night? + Who were you with last night? + Will you tell your missus when you go home + Who you were with last night? + +Flagonson + (in anguished indignation). +

This is more than a hurt to us: this hits at the + decency of the whole nation!

+ +If however, the song is to be regarded as forming a distinct item, +perhaps with its own front and back matter, it may be better to regard +it as a floating text: +Kelly + (calmly). +

Aha, so you've bad minds along with ...

 + (He points, one after the other at Conroy, Bull, + and Flagonson. Lilting): + + + Kelly's Song + + + Who were you with last night? + Who were you with last night? + Will you tell your missus when you go home + Who you were with last night? + + +

+

When an embedded structure extends across more than one sp +element, each of its constituent parts must be regarded as a distinct +fragment; the problem then facing the encoder is to reconstitute the +interrupted whole in some way.

+

As already noted above, the spGrp element may be used to +group together consecutive speeches which are grouped together in some +way, for example constituting a single song. Alternatively the +part attribute, typically used to +indicate that an l element contains a partial, not a complete, +verse line, may also be used on the lg element, +to indicate that the line group is partial rather than complete, thus: +Kelly + (wheeling quietly in his semi-dance, + as he goes out): + + Goodbye to holy souls left here, + Goodbye to man an' fairy; + + +Widda Machree + (wheeling quietly in her semi-dance, + as she goes out): + + Goodbye to all of Leicester Square, + An' the long way to Tipperary. + +

+

When the fragments of a song are separated by other intervening +dialogue, or even when not, they may be linked together with the +next and prev attributes defined in section +. +For example, the line groups making up Ophelia's song +might be encoded as follows: + + + Elsinore. A room in the Castle. + Enter Ophelia, distracted. + Ophelia +

Where is the beauteous Majesty of Denmark?

+ + Queen +

How now, Ophelia?

+ + Ophelia + Singing + + How should I your true-love know + From another one? + By his cockle hat and staff + And his sandal shoon. + + + Queen +

Alas, sweet lady, what imports this song?

+ + Ophelia +

Say you? Nay, pray you mark.

+ Sings + + He is dead and gone, lady, + He is dead and gone; + At his head a grass-green turf, + At his heels a stone. + +

O, ho!

+ + +

+

The next and prev attributes are discussed in +section : they form part of the module +for alignment and linking; this module must therefore be included in a +schema if they are to be used, as further discussed in section .

+

The fragments of Ophelia's song might also be linked together using +the join mechanism described in section . +The join element is specifically intended to encode the fact +that several discontiguous elements of the text together form one +virtual element. Using this mechanism, the example +might be encoded as follows: + + + + + Elsinore. A room in the Castle. + Queen +

How now, Ophelia?

+ + Ophelia + Singing + + How should I your true-love know + From another one? + By his cockle hat and staff + And his sandal shoon. + + + Queen +

Alas, sweet lady, what imports this song?

+ + Ophelia +

Say you? Nay, pray you mark.

+ Sings + + He is dead and gone, lady, + He is dead and gone; + At his head a grass-green turf, + At his heels a stone. + +

O, ho!

+ + + + + + +The location of the join element is not significant; here it +has been placed shortly after the conclusion of the song, in order to +have it close to the fragments it unifies.

+

Like the next and prev attributes, the +join element requires the additional module for linking, which +is selected as shown above.

+
Simultaneous Action +

In printed or written versions of performance texts, a variety of +techniques may be used to indicate the temporal alignment of speeches or +actions. Speeches may be printed vertically aligned on the page, or +braced together; stage directions (e.g. Speaking at the same +time) are also often used. In operatic or musical works in +particular, the need to indicate timing and alignment of individual +parts of a song may lead to very complex layout.

+

One simple method of indicating the temporal alignment of speeches or +actions is to use the spGrp element discussed in +section , with a type attribute to specify the +reason for grouping, as in the following example: + Mangan + wildly +

Look here: I'm going to take off all my clothes.

+ he begins tearing off his coat. + + + Lady Utterword +

Mr Mangan!

+ + Captain Shotover +

Whats that?

+ + Hector +

Ha! ha! Do. Do.

+ + Ellie +

Please dont.

+ +in consternation + + Mrs. Hushabye + catching his arm and stopping him +

Alfred: for shame! Are you mad?

+

+ + + + +

In the original, the stage direction in consternation is +printed opposite a brace grouping all four speeches, indicating that all +four characters speak at once, and that the stage direction applies to +all of them. Rather than attempting to represent the appearance of the +source, this example encoding represents its presumed meaning: the +stage element is placed arbitrarily after the last relevant +speech, and the four speeches with which it is to be associated are +grouped by means of the spGrp element. The rend +attribute is used to specify the fact that the three speeches were +grouped by the brace in the copy text. Producing a readable version +of the text which simulates the original printed effect may however +require more complex markup and processing. +

+

More powerful and more precise mechanisms for temporal alignment are +defined in chapter . These would be appropriate for +encodings the focus of which is on the actual performance of a text +rather than its structure or formal properties. The module described +in that chapter includes a large number of other detailed proposals for +the encoding of such features as voice quality, prosody, etc., which +might be relevant to such a treatment of performance texts. +

+
Other Types of Performance Text +

Most of the elements and structures identified thus far are derived +from traditional theatrical texts. Although other performance texts, +such as screenplays or radio scripts, have not been discussed +specifically, they can be encoded using the elements and structures +listed above. Encoders may however find it convenient to use, as well, +the additional specialized elements discussed in this section. For +scripts containing very detailed technical information, the +tech element discussed in section may also +be useful. +

+

Like other texts, screenplays and television or radio scripts may +be divided into text divisions marked with div or +div1, etc. Within units corresponding with the traditional +act and scene, further subdivisions or sequences may be +identified, composed of individual shots, each associated with +a single camera angle and setting. Shots and sequences should be +encoded using an appropriate text-division element (i.e., a +div3 element if numbered division elements are in use and the +next largest unit is a div2, or a div element if +un-numbered divisions are in use) specifying sequence or +shot as the value of the type attribute, as +appropriate. +

+

It is normal practice in screenplays and radio scripts to distinguish +directions concerning camera angles, sound effects, etc., from other +forms of stage direction. Such texts also generally include far more +detailed specifications of what the audience actually sees: +descriptions of actions and background, etc. Scripts derived from +cinema and television productions may also include texts displayed as +captions superimposed on the action. All of these may be encoded using +the general purpose stage element discussed in section , and distinguished by means of its type +attribute. Alternatively, or in addition, the following more specific +elements may be used, where clear distinctions can be made: + +

+

Some examples of the use of these elements follow: +Angle on Olivia. +Ryan's wife, standing nervously alone on the sidelines, +biting her lip. She's scared and she shows it. +

+

Where particular words or phrases within a direction are emphasized +(by change of typeface or use of capital letters), an appropriate +phrase-level element may be used to indicate the fact, as in the +following examples, where certain words in the original are given in +small capitals: + George glances at the window--and freezes. +New angle--shock cut Out the window +the body of a dead man suddenly slams into +frame. He dangles grotesquely, +held up by his coat caught on a protruding bolt. +George gasps. The train whistle screams. + + Ext. TV control van—Early morning. +The T.V. announcer from the Ryan interview +stands near the Control Van, the lake in b.g. + T.V. Announcer +

Several years ago, Jack Ryan was a highly +successful hydroplane racer ...

+ + +

+

All of these elements, like other stage directions, can appear both +within and between speeches. + + TV Announcer VO +

Working with Ryan are his two coworkers— +Strut Bowman, the mechanical engineer— +Angle on Strut +standing in the tow boat, walkie-talkie in hand, +watching Ryan carefully. +—and Roger Dalton, a rocket +systems analyst, and one of the scientists +from the Jet Propulsion Lab ...

+ + Benjy +

Now to business.

+ + Ford and Zaphod +

To business.

 +Glasses clink. + Benjy +

I beg your pardon?

 + Ford +

I'm sorry, I thought you were proposing a toast.

 + +Zoom in to overlay showing some stock film + of hansom cabs galloping past. +London, 1895. +The residence of Mr Oscar Wilde. +Suitably classy music starts. +Mix through to Wilde's drawing room. A crowd of suitably + dressed folk are engaged in typically brilliant conversation, + laughing affectedly and drinking champagne. + + Prince of Wales +

My congratulations, Wilde. Your latest play is a great success.

+ + +

+
Technical Information +

Traditional stage scripts may contain additional technical +information about such production-related factors as lighting, +blocking (that is, detailed notes on actors' +movements), or props required at particular points. More technical +information about intended production effects may also appear in +published versions of screenplays or movie scripts. Where these are +presented simply as marginal notes, they may be encoded using the +general-purpose note element defined in section . +Alternatively, they may be formally distinguished from +other stage directions by using the specialized tech element: + +

+

Like stage directions, tech elements can appear anywhere +within a speech or between speeches. +

+ + + + + + + + +
+
+ Module for Performance Texts +

The module described in this chapter makes available the + following components: + + Performance Texts + Performance texts + Théâtre + 劇本 + Testi per performance + Textos de actuação + 舞台芸術モジュール + + + The selection and combination of modules to form a TEI schema is described in + .

+
+
diff --git a/P5/Source/Guidelines/fr/DS-DefaultTextStructure.xml b/P5/Source/Guidelines/fr/DS-DefaultTextStructure.xml deleted file mode 120000 index a6f5a1ffd8..0000000000 --- a/P5/Source/Guidelines/fr/DS-DefaultTextStructure.xml +++ /dev/null @@ -1 +0,0 @@ -../en/./DS-DefaultTextStructure.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/DS-DefaultTextStructure.xml b/P5/Source/Guidelines/fr/DS-DefaultTextStructure.xml new file mode 100644 index 0000000000..8d033a464e --- /dev/null +++ b/P5/Source/Guidelines/fr/DS-DefaultTextStructure.xml @@ -0,0 +1,1834 @@ + + + + +
+ Default Text Structure + +

This chapter describes the default high-level structure for TEI + documents. A full TEI document combines metadata describing it, + represented by a teiHeader element, with the document + itself, represented by one or more text elements or other + elements taken from the model.resource class. That + is, the TEI element is used to group together metadata + about an encoded resource (in teiHeader, specified by the header module, which is fully described in + chapter ) with an encoded + resource. Possible encoded resources are + + a logical transcription of a source document in a + text element; the text element is specified + along with its high-level constituents in the textstructure module and described in the + remainder of the current chapter + a diplomatic transcription of a source document in a + sourceDoc element, which is specified in the transcr module and described in + chapter + an encoded representation of a text-bearing object as images + in a facsimile element, which is also specified in the + transcr module and described in + chapter + a collection of contextual information or annotations that + provides more detail about another encoded resource (whether in + the same or a different TEI document) in a standOff + element, which is specified in the linking module and described in section + a feature system declaration which can be used + to declare the use of fs elements in the rest of the + document, which is specified in the iso-fs module and described in section +

+

In a case in which more than one resource related to the same + source document share the same metadata, they may be grouped + together in a TEI element following a single + teiHeader.

+

Because the TEI can be a child of itself, a set or collection of +documents may be represented by an outermost TEI element that +contains a teiHeader with metadata that is applicable to the +entire set or collection of transcriptions, and then a complete +TEI element for each document in the collection or set; each +of these TEI elements contains a teiHeader with +metadata that is applicable to the individual document, and one or +more text or other elements taken from the +model.resource class.

+ +

A variant on this basic form, the teiCorpus, is also +defined for the representation of language corpora, or other +collections of encoded texts. A teiCorpus consists of its own +metadata in a teiHeader, followed by one or more complete +TEI elements, each combining a teiHeader with one or +more elements from the model.resource class. This +permits the encoder to distinguish metadata applicable to the whole +collection of encoded texts, which is represented by the outermost +teiHeader, from that applicable to each of the individual +TEI elements within the corpus. Further information about the +organization and encoding of language corpora is given in chapter .

+ +

Alternatively, the corpus may be represented with a TEI +element (perhaps with a type of corpus) in the +same manner as a teiCorpus.

+ +

In summary, when the default structure module is included in a +schema, the following elements are available for the +representation of the outermost structure of a TEI document: + + + + + + + +As noted above, the teiHeader element is formally declared in +the header module (see chapter ). A TEI document may also contain elements from the +model.resource class (such as a +collection of facsimile images, or a feature system declaration) if +the appropriate module is included in a schema (see further and respectively). By default, +however, this class is not populated and hence only the elements +TEI, text, and teiCorpus are available +as major parts of a TEI document. These three elements are +provided by the textstructure module +described by the present chapter. + + + + + + +

+ +

TEI texts may be regarded either as unitary, that is, +forming an organic whole, or as composite, that is, +consisting of several components which are in some important sense +independent of each other. The distinction is not always entirely +obvious: for example a collection of essays might be regarded as a +single item in some circumstances, or as a number of distinct items in +others. In such borderline cases, the encoder must choose whether to +treat the text as unitary or composite; each may have advantages and +disadvantages in a given situation.

+ +

Whether unitary or composite, the text is marked with the +text tag and may contain front matter, a text body, and back +matter. In unitary texts, the text body is tagged body; in +composite texts, where the text body consists of a series of subordinate +texts or groups, it is tagged group. The overall structure of +any text, unitary or composite, is thus defined by the following +elements: + +

+

The overall structure of a unitary text is: + + + + + + + + + + + + + +

+

The overall structure of a composite text made up of two unitary +texts is: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

+

Finally, a floatingText element is provided for the case +where one text is embedded within another, but does not contribute to +its hierarchical organization, for example because it interrupts it, +or simply quoted within it. This is useful in such common literary contexts as +the play within a play or the narrative interrupted by other (often +deeply nested) multiple narratives. + + + + + + + +

+

Each of these elements is further described in the remainder of +this chapter. Elements front and back are further +discussed in sections and . The group and floatingText +elements, used for more complex or composite text structures, are +further discussed in section . Other textual +elements, such as paragraphs, lists or phrases, which nest within +these major structural elements, are discussed in chapter , in the case of elements which can appear in any kind +of document, or elsewhere in the case of elements specific to +particular kinds of document. +

+
Divisions of the Body + +

In some texts, the body consists simply of a sequence of low-level +structural items, referred to here as components or +component-level elements (see section ). Examples in prose texts include paragraphs or +lists; in dramatic texts, speeches and stage directions; in +dictionaries, dictionary entries. In other cases sequences of such +elements will be grouped together hierarchically into textual +divisions and subdivisions, such as chapters or sections. The names +used for these structural subdivisions of texts vary with the genre +and period of the text, or even at the whim of the author, editor, or +publisher. For example, a major subdivision of an epic or of the Bible +is generally called a book, that of a report is +usually called a part or +section, that of a novel a +chapter—unless it is an epistolary novel, in +which case it may be called a letter. Even texts +which are not organized as linear prose narratives, or not as +narratives at all, will frequently be subdivided in a similar way: a +drama into acts and scenes; +a reference book into sections; a diary or day +book into entries; a newspaper into +issues and sections, and so +forth. +

+ +

Because of this variety, these Guidelines propose that all such +textual divisions be regarded as occurrences of the same neutrally named +elements, with an attribute type used to categorize elements +independently of their hierarchic level. Two alternative styles are +provided for the marking of these neutral divisions: +numbered and un-numbered. Numbered divisions +are named div1, div2, etc., where the +number indicates the depth of this particular division within the +hierarchy, the largest such division being div1, any subdivision +within it being div2, any further sub-sub-division being +div3 and so on. Un-numbered divisions are simply named +div, and allowed to nest recursively to indicate their +hierarchic depth. The two styles must not be combined +within a single front, body, or back element. +

+
Un-numbered Divisions +

The following element is used to identify textual subdivisions in +the un-numbered style: As a +member of the class att.typed, this +element has the following additional attributes: +

+

Using this style, the body of a text containing two parts, each +composed of two chapters, might be represented as follows: + +

+
+ +
+
+ +
+
+
+
+ +
+
+ +
+
+ +

+ + + + + + +
+
Numbered Divisions +

The following elements are used to identify textual subdivisions +in the numbered style: + + + + + + + + + +As members of the class att.typed these +elements all bear the following additional attributes: + +

+

The largest possible subdivision of the body is div1 +element and the smallest possible div7. If numbered +divisions are in use, a division at any one level (say, +div3), may contain only numbered divisions at the next lowest +level (in this case, div4).

+

Using this style, the body of a text containing two parts, each +composed of two chapters, might be represented as follows: + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

+ + + + + + + + + + + + + + +
+
Numbered or Un-numbered? +

Within the same front, body, or back +element, all hierarchic subdivisions must be marked using either +nested div elements, or div1, div2 etc. +elements nested as appropriate; the two styles must not +be mixed. +

+

The choice between numbered and un-numbered divisions will depend +to some extent on the complexity of the material: un-numbered +divisions allow for an arbitrary depth of nesting, while numbered +divisions limit the depth of the tree which can be constructed. Where +divisions at different levels should be processed differently (for +example to ensure that chapters, but not sections, begin on a new +page), numbered divisions slightly simplify the task of defining the +desired processing for each level, though this distinction could also +be made by supplying this information on the type attribute +of an un-numbered div. Some software may find numbered +divisions easier to process, as there is no need to maintain knowledge +of the whole document structure in order to know the level at which a +division occurs; such software may, however, find it difficult to cope +with some other aspects of the TEI scheme. On the other hand, in a +collection of many works it may prove difficult or impossible to +ensure that the same numbered division always corresponds with the +same type of textual feature: a chapter may be at +level 1 in one work and level 3 in another. +

+

Whichever style is used, the global n and xml:id +attributes (section ) may be used to provide +reference strings or labels for each division of a text, where +appropriate. Such labels should be provided for each section +which is regarded as significant for referencing purposes (on +reference systems, see further section ). +

+ +

As indicated above, the type and subtype +attributes provided by the att.typed class +may be used to provide a name or description for the division. +Typical values might be book, +chapter, section, +part, or (for verse texts) +book, canto, +stanza, or (for dramatic texts) +act, scene. The following +extended example uses numbered divisions to indicate the structure of +a novel, and illustrates the use of the attributes discussed above. +It also uses some elements discussed in section +and the p element discussed in section . + + + Book I. + + Of writing lives in general, and particularly of Pamela, with a word + by the bye of Colley Cibber and others. +

It is a trite but true observation, that examples work more forcibly on + the mind than precepts: ...

+ + + + Of Mr. Joseph Andrews, his birth, parentage, education, and great + endowments; with a word or two concerning ancestors. +

Mr. Joseph Andrews, the hero of our ensuing history, was esteemed to + be the only son of Gaffar and Gammar Andrews, and brother to the + illustrious Pamela, whose virtue is at present so famous ...

+ + + + The end of the first Book + + + Book II + + Of divisions in authors +

There are certain mysteries or secrets in all trades, from the highest + to the lowest, from that of prime-ministering, to this of + authoring, which are seldom discovered unless to members of + the same calling ...

+

I will dismiss this chapter with the following observation: that it + becomes an author generally to divide a book, as it does a butcher to + joint his meat, for such assistance is of great help to both the reader + and the carver. And now having indulged myself a little I will endeavour + to indulge the curiosity of my reader, who is no doubt impatient to know + what he will find in the subsequent chapters of this book.

+ + + A surprising instance of Mr. Adams's short memory, with the + unfortunate consequences which it brought on Joseph. + +

Mr. Adams and Joseph were now ready to depart different ways ...

+ + + +

+ +

As an alternative (or complement) to this use of the +type attribute to characterize neutrally named division +elements, the modification mechanisms discussed in section may be used to define new elements such as +chapter, part, etc. To make this simpler, a single +member model class is defined for each of the neutrally named division +elements: model.divLike (containing +div), model.div1Like (containing +div1), model.div2Like (containing +div2), etc. For example, suppose that the body of a text +consists of a series of diary entries, each of which is potentially +divided into entries for the morning and the afternoon. This might be +represented in any of the following ways. First, using the un-numbered +style: +

+

[...]

+

[...]

+
+
+

[...]

+

[...]

+
+ + +Equivalently, using the numbered style: + + +

[...]

 +

[...]

 + + +

[...]

 +

[...]

 + + + + +Now, assuming a customization in which a new element +diaryEntry has been added to the model.divLike class: + +

[...]

 +

[...]

 + + +

[...]

 +

[...]

 + + + + +And finally, assuming a customization in which three new elements have +been added: diaryEntry to the model.div1Like class, and amEntry and +pmEntry both to the model.div2Like class: +

+ +

[...]

 +

[...]

 + + +

[...]

 +

[...]

 + + + +

+

More information about the customization techniques exemplified +here is provided in . +

+ + +
+
Partial and Composite Divisions +

In most situations, the textual subdivisions marked by div +or div1 (etc.) elements will be both complete and identically +organized with reference to the original source. For some purposes +however, in particular where dealing with unusually large or unusually +small texts, encoders may find it convenient to present as textual +divisions sequences of text which are incomplete with reference to the +original text, or which are in fact an ad hoc agglomeration of tiny +texts. Moreover, in some kinds of texts it is difficult or impossible +to determine the order in which individual subdivisions should be +combined to form the next higher level of subdivision, as noted below. +

+

To overcome these problems, the following additional attributes are +defined for all elements in the att.divLike class: + + + +

+

For example, an encoder might choose to transcribe only the first two +thousand words of each chapter from a novel. In such a case, each +chapter might conveniently be regarded as a partial division, and tagged +with a div element in the following form: +

+

...

+
+where xx represents a number for the chapter, and the +part attribute takes the value Y to indicate +that this division is incomplete in some respect. Other possible +values for this attribute indicate whether material has been omitted +initially (I), finally +(F), or in the middle (M) of the division, while the gap +element () may be used to indicate exactly +where material has been omitted: +
+

...

+ +

...

+
 +The +samplingDecl element in the TEI header should also be used to +record the principles underlying the selection of incomplete samples, as +further described in section . +

+

The following example demonstrates how a newspaper column composed of +very short unrelated snippets may be encoded using these attributes: + +News in brief + +Police deny losing bomb +

Scotland Yard yesterday denied claims in the Sunday +Express that anti-terrorist officers trailing an IRA van +loaded with explosives in north London had lost track of +it 10 days ago.

+ + +Hotel blaze +

Nearly 200 guests were evacuated before dawn +yesterday after fire broke out at the Scandic +Crown hotel in the Royal Mile, Edinburgh.

+ + +Test match split +

Test Match Special next summer will be split +between Radio 5 and Radio 3, after protests this +year that it disrupted Radio 3's music schedule.

+ + + +

+

The org attribute on the div1 element is used +here to indicate that individual stories in this group, marked here as +div2, are really quite independent of each other, although they +are all marked as subdivisions of the whole group. They can be read in +any order without affecting the sense of the piece; indeed, in some +cases, divisions of this nature are printed in such a way as to make it +impossible to determine the order in which they are intended to be read. +Individual stories can be added or removed without affecting the +existing components. +

+

This method of encoding composite texts as composite divisions has +some limitations compared with the more general and powerful mechanisms +discussed in section . However, it may be preferable +in some circumstances, notably where the individual texts are very +small. +

+
Elements Common to All Divisions +

The divisions of any kind of text may sometimes begin with a brief +heading or descriptive title, with or without a byline, an epigraph or +brief quotation, or a salutation such as one finds at the start of a +letter. They may also conclude with a brief trailer, byline, +postscript, or signature. Many of these (e.g. a byline) may appear +either at the start or at the end of a text division proper.

+

To support this heterogeneity, the TEI architecture defines five +classes, all of which are populated by this module: + + + + + + +

+ +
Headings and Trailers + +

The head element is used to identify a heading prefixed to +the start of any textual division, at any level. A given division may +contain more than one such element, as in the following example: + +Etymology +(Supplied by a late consumptive usher to a +grammar school) +

The pale Usher — threadbare in coat, heart, +body and brain; I see him now. He was ever +dusting his old lexicons and grammars, ...

+ +

+

Unlike some other markup schemes, the TEI scheme does +not require that headings attached to textual +subdivisions at different hierarchic levels have different +identifiers. All kinds of heading are marked identically using the +head tag; the type or level of heading intended is implied by +the immediate parent of the head element, which may for +example be a div1, div2, etc., an un-numbered +div, or any member of the model.listLike class. However, as with +div elements, the encoder may choose to extend the model.headLike class of which head is +the sole member to include other such elements if required.

+

In certain kinds of text (notably newspapers), there may be a need +to categorize individual headings within the sequence at the start of +a division, for example as main headings, or +detail headings: this may readily be done using the +type or subtype attribute. Specific elements are provided +for certain kinds of heading-like features, (notably byline, +dateline, and salute; see further section ), but the type or subtype +attributes must be used to discriminate among other forms of +heading. These attributes are provided, as elsewhere, by the att.typed attribute class of which the +head element is a member. +

+

In the following example, taken from a British newspaper, the lead +story and its associated headlines have been encoded as a div +element, with appropriate model.divTop elements attached: +

+ +President pledges safeguards for 2,400 British +troops in Bosnia + +Major agrees to enforced no-fly zone +By George Jones, Political Editor, in Washington +

Greater Western intervention in the conflict in +former Yugoslavia was pledged by President Bush ...

+ +

+

In older writings, the headings or incipits may be +longer than in modern works. +When heading-like material appears in the middle of a text, the encoder +must decide whether or not to treat it as the start of a new division. +If the phrase in question appears to be more closely connected with what +follows than with what precedes it, then it may be regarded as a +heading and tagged as the head of a new div element. +If it appears to be simply inserted or superimposed—as for example +the kind of pull quotes often found in newspapers +or magazines, then the quote, q, or cit +element may be more appropriate. +

+

The trailer element, which can appear at the end of a +division only, is used to mark any heading-like feature appearing in +this position, as in this example: +

In the name of Christ here begins the + first book of the ecclesiastical history of Georgius Florentinus, + known as Gregory, Bishop of Tours. +
Chapter Headings + + + + +
+
In the name of Christ here begins Book I of the history. +

Proposing as I do ...

+

From the Passion of our Lord until the death of Saint Martin four + hundred and twelve years passed.

+ Here ends the first Book, which covers five thousand, five + hundred and ninety-six years from the beginning of the world down + to the death of Saint Martin. +
+
+

+ + +
+
Openers and Closers +

In addition to headings of various kinds, divisions sometimes include +more or less formulaic opening or closing passages, typically conveying +such information as the name and address of the person to whom the +division is addressed, the place or time of its production, a salutation +or exhortation to the reader, and so on. Divisions in epistolary form +are particularly liable to include such features. +Additional elements for the detailed encoding of personal names, dates, +and places are provided in chapter . +For simple cases, the following elements should be adequate: + + + + + + +

+

The byline and dateline elements are used to encode +headings which identify the authorship and provenance of a division. +Although the terminology derives from newspaper usage, there is no +implication that dateline or byline elements apply +only to newspaper texts. The following example illustrates use of the +dateline and signed elements at the end of the +preface to a novel: +

+To Henry Hope. +

It is not because this volume was conceived and partly +executed amid the glades and galleries of the Deepdene, +that I have inscribed it with your name. ... I shall find a +reflex to their efforts in your own generous spirit and +enlightened mind. +

+ +D. +Grosvenor Gate, May-Day, 1844 + +
+ + +

+

Where a sequence of such elements appear together, either at the +beginning or end of an element, it may be convenient to group them +together using one of the following elements: + + + +The following examples demonstrate the use of the opener and +closer grouping elements: +

+ Sixth Narrative + contributed by Sergeant Cuff +
+ + + Dorking, Surrey, + July 30th, 1849 + + To Franklin Blake, Esq. Sir, — + +

I beg to apologize for the delay that has occurred in the + production of the Report, with which I engaged to furnish you. + I have waited to make it a complete Report ...

+ + I have the honour to remain, dear sir, your + obedient servant + RICHARD CUFF (late sergeant in the + Detective Force, Scotland Yard, London). + +
+
+ +
+Letter XIV: Miss Clarissa Harlowe to Miss Howe + Thursday evening, March 2. +

On Hannah's depositing my long letter ...

+

An interruption obliges me to conclude myself +in some hurry, as well as fright, what I must ever be,

+ +Yours more than my own, +Clarissa Harlowe + +
 + +

+

For further discussion of the encoding of dates and of names of persons and places, see section and chapter . +

+
Arguments, Epigraphs, and Postscripts +

The argument element may be used to encode the prefatory +list of topics sometimes found at the start of a chapter or +other division. It is most conveniently encoded as a list, since this +allows each item to be distinguished, but may also simply be presented +as a paragraph. The following are thus both equally valid ways of +encoding the same argument: +

+ +

Kingston — Instructive remarks on early English history + — Instructive observations on carved oak and life in general + — Sad case of Stivvings, junior — Musings on antiquity + — I forget that I am steering — Interesting result + — Hampton Court Maze — Harris as a guide.

+ +

It was a glorious morning, late spring or early summer, as you + care to take it ...

+
+ +
+ + + Kingston + Instructive remarks on early English history + Instructive observations on carved oak and life in + general + Sad case of Stivvings, junior + Musings on antiquity + I forget that I am steering + Interesting result + Hampton Court Maze + Harris as a guide. + + +

It was a glorious morning, late spring or early summer, as you + care to take it ...

+
 + +

+

An epigraph is a quotation from some other work, a +saying, or a motto, appearing on a title page, or at the start of a +division. It may be encoded using the special-purpose +epigraph element, as in the following example: + + +E. M. Forster +Howards End +Only connect... + + +When an epigraph contains a quotation, this may often be associated +with a bibliographic reference. In such cases, it is recommended +additionally to group the quotation and its source together using the +cit element, as in the following example:

Chapter 19 + + I pity the man who can travel + from Dan to Beersheba, and say 'Tis all + barren; and so is all the world to him + who will not cultivate the fruits it offers. + + Sterne: Sentimental Journey. + +

To say that Deronda was romantic would be to + misrepresent him: but under his calm and somewhat + self-repressed exterior ...

+
+ +

+

For discussion of quotations appearing other than as epigraphs refer +to section . +

A postscript is a passage added after the signature of +a letter or, less frequently, the main portion of the body of a book, +article, or essay. In English a postscript is often abbreviated as +P.S. or PS, and +postscripts are often introduced by labels with one of these +abbreviations, as in the following example. + +

+ + + Newport + May ye 27th 1761 + + Gentlemen + +

Capt Stoddard's Business + calling him to Providence, have + got him to look at Hopkins brigantine + & if can agree to Purchase her, shall + be much oblig'd for your further + assistance herein, & will acquiesce with + whatever you & he shall Contract + for — I Thank you for your + Line respecting the brigantine & Beg + leave to Recommend the Bearer + to you for your advice & Friendship + in this matter

+ + I am your most humble servant + Joseph Wanton Jr + + + +

I have Mollases, Sugar, + Coffee & Rum, which + will Exchange with you + for Candles or Oyl

+ +
+ + +

+
+
Content of Textual Divisions +

Other than elements from the model.divWrapper, model.divTop, or model.divBottom classes, every textual division +(numbered or un-numbered) consists of a sequence of ungrouped model.common elements (see ). The actual elements available will depend on the +modules in use; in all cases, at least the component-level structural +elements defined in the core will be available (paragraphs, lists, +dramatic speeches, verse lines and line groups etc.). If the drama +module has been selected, then other component- or phrase- level items +specialized for performance texts (for example, cast lists or camera +angles) will be available, as defined in +chapter ) will be available. If the dictionary +module is in use, then dictionary entries, related entries, etc. (as +defined in chapter ) will also be available; if the +module for transcribed speech is in use, then utterances, pauses, +vocals, kinesics, etc., as defined in chapter +will be available; and so on.

+

Where a text contains low-level elements from more than one +module these may appear at any point; there is no requirement that +elements from the same module be kept together.

+ + + + + + + + + + + + + + + +
+
+
Grouped and Floating Texts +

The group element discussed in +should be used to represent a collection of independent texts which is +to be regarded as a single unit for processing or other purposes. The +floatingText element discussed in +should be used to represent an independent text which interrupts the +text containing it at any point but after which the surrounding text +resumes. +

+
Grouped Texts +

+Examples of composite texts which should be represented using the +group element include +anthologies and other collections. The presence of common front matter +referring to the whole collection, possibly in addition to front matter +relating to each individual text, is a good indication that a given text +might usefully be encoded in this way; this structure may be found +useful in other circumstances too. +

+

For example, the overall structure of a collection of +short stories might be encoded as follows: + + + + + The Adventures of Sherlock Holmes + + First published in The Strand + between July 1891 and December 1892 + + + + + + Adventures of Sherlock + Holmes + Adventure I. — + A Scandal in Bohemia + By A. Conan Doyle. + + +

To Sherlock Holmes she is always + the woman. ...

+ + + + + + Adventures of Sherlock Holmes + Adventure II. — + The Red-Headed League + By A. Conan Doyle. + + +

I had called upon my friend, Mr. Sherlock Holmes, one day + in the autumn of last year and found him in deep conversation + with a very stout, florid-faced, elderly gentleman with fiery red hair … +

+ + + + + + Adventures of Sherlock Holmes + Adventure XII. — + The Adventure of the Copper Beeches + + By A. Conan Doyle. + + +

To the man who loves art for its + own sake, remarked Sherlock Holmes ... + + + + ... she is now the head of a private school + at Walsall, where I believe that she has + met with considerable success.

+ + + + + + +

+

A text which is a member of a group may itself contain groups. This +is quite common in collections of verse, but may happen in any kind of +text. As an example, consider the overall structure of a typical +collection, such as the Muses Library edition of +Crashaw's poetry. Following a critical +introduction and table of contents, this work contains the following +major sections: + +Steps to the Temple (a collection of +verse as published in 1648) +Carmen deo Nostro (a second collection, +published in 1652) +The Delights of the Muses (a third +collection, published in 1648) +Posthumous Poems, I (a collection of +fragments all taken from a single manuscript) +Posthumous Poems, II (a further collection +of fragments, taken from a different manuscript) +

+

The first three of these collections each has a +reasonable claim to be considered as a text in its own right, and may +therefore be encoded as such. It is rather more arbitrary as to +whether the two posthumous collections should be treated as two +groups, following the practice of the Muses Library +edition. An encoder might elect to combine the two into a single +group or simply to treat each fragment as an ungrouped unitary text. +

+

The Muses Library edition reprints the whole of each +of the three original collections, including their original front +matter (title pages, dedications etc.). These should be encoded using +the front element and its constituents (on which see further +section ), while the body of each collection +should be encoded as a single group element. Each individual +poem within the collections should be encoded as a distinct +text element. The beginning of the whole collection would +thus appear as follows (for further discussion of the use of the +elements div and lg for textual subdivision of +verse, see section and chapter ): + + + The poems of Richard Crashaw + Edited by J.R. Tutin + +

Editor's Note +

A few words are necessary ...

+
+ + + + + + + Steps to the Temple, Sacred Poems + + +
The Preface to the Reader +

Learned Reader, The Author's friend will not usurp much + upon thy eye ...

+
+ + + + + Sospetto D'Herode + + + + Libro Primo + + Casting the times with their strong signs + + + Muse! now the servant of soft loves no more + Hate is thy theme and Herod whose unblest + Hand (O, what dares not jealous greatness?) tore + A thousand sweet babes from their mothers' breast, + The blooms of martyrdom ... + + + The Tear + + + What bright soft thing is this + Sweet Mary, thy fair eyes' expense? + + + + + + + + + + + + + + + + + + + + + + + + +

+

The group element may be used in this way to encode any kind +of collection of which the constituents are regarded by the encoder as +texts in their own right. Examples include anthologies or collections +of verse or +prose by multiple authors, florilegia, or commonplace books, +journals, day books, etc. As a fairly typical example, we consider +The Norton Book of Travel, an anthology edited by Paul +Fussell and published in 1987 by W. W. Norton. This work comprises +the following major sections: + +Front matter (title page, acknowledgments, introductory essay) +The Beginnings +The Eighteenth Century and the Grand Tour +The Heyday +Touristic Tendencies +Post Tourism +Back matter (permissions list, index) +Each titled section listed above comprises a group of extracts or +complete texts from writers of a given historical period, preceded by an +introductory essay. For example, the second group listed above +contains, inter alia, the following: + +Prefatory essay +Five letters by Lady Mary Wortley Montagu +An extract from Swift's Gulliver's Travels +Two poems by Alexander Pope +Two extracts from Boswell's Journal +A poem by William Blake +Each group of writings by a single author is preceded by a brief +biographical notice. Some of the extracts are quite lengthy, containing +several chapters or other divisions; others are quite short. As the +above list indicates, the texts included range across all kinds of +material: verse, prose, journals and letters. +

+

The easiest way of encoding such an anthology is to treat each +individual extract as a text in its own right. A sequence of texts by a +single author, together with the biographical note preceding it, can +then be treated as a single group element within the larger +group formed by the section. The sequence of single or +composite texts making up a single section of the work is likewise +treated, together with its prefatory essay, as a single group +within the work. Schematically: + + + + + + + The Beginnings + + + + + + + + + + + + + + + + + + + + + + The Heyday + + + + + + +

+

Note that the editor's introductory essays on each author may be +treated as texts in their own right (as the essays on Lady Mary +Wortley Montagu and Alexander Pope have been treated above), or as +front matter to the embedded text, as the essay on Swift has been. +The treatment in the example is intentionally inconsistent, to allow +comparison of the two approaches. Consistency can be imposed either +by treating the Swift section as a group containing one text +by Swift and one by the editor, or by treating the Montagu and Pope +sections as text elements containing the editor's essays as +front matter. Marked in the second way, the Pope section of the book +would look like this: + + + + + + + +

+

The essays on The Eighteenth Century and the Grand Tour and +other larger sections could also be tagged as front +matter in the same way, by treating the larger sections as text +elements rather than group elements. +

+

Where, as in this case, an anthology contains different kinds of +text (for example, mixtures of prose and drama, or transcribed speech +and dictionary entries, or letters and verse), the elements to be +encoded will of course be drawn from more than one module. +The elements provided by the core module +described in chapter should however prove adequate +for most simple purposes, where prose, drama, and verse are combined +in a single collection. +

+

For anthologies of short extracts such as commonplace books, it may +often be preferable to regard each extract not as a text in its own +right but simply as a quotation or cit element. The following +component-level elements may be used to encode quotations of this kind: + +For example, the chapter of extracts which appears +in the front matter of Melville's Moby Dick might be +encoded as follows: +

+ Extracts + (Supplied by a sub-sub-Librarian) +

It will be seen that this mere painstaking burrower and + grubworm of a poor devil of a Sub-Sub appears to have gone + through the long Vaticans and street-stalls of the earth, + picking up whatever random allusions to whales he could + anyways find ... + Here ye strike but splintered hearts together — there, + ye shall strike unsplinterable glasses!

+

+ + And God created great whales. + Genesis + + + + Leviathan maketh a path to shine after him; + One would think the deep to be hoary. + + Job + + + By art is created that great Leviathan, + called a Commonwealth or State — (in Latin, + civitas), which + is but an artificial man. + Opening sentence of Hobbes's Leviathan + +

+
+For more information on the use of the quote and bibl +elements, see sections and +respectively. +

+ +
+
Floating Texts +

An important characteristic of the unitary or composite text +structures discussed so far is that they can be regarded as forming what is +mathematically known as a tesselation covering the whole +of the available text (or text division) at each hierarchic +level. Just as an XML document has a single root element containing +a single tree, each node of which forms a properly nested sub-tree, so +it seems natural to think of the internal structure of a text as +decomposable hierarchically into subparts, each of which is a +properly nested subtree. While this is undoubtedly true of a large +number of documents, it is not true of all. In particular, it is not +true of texts which are only partly tesselated at a given level. For +example, if a text A is contained by text B in such a way that part of +B precedes A and part follows it, we cannot tesselate the whole of B. +In such a case, we say that text A is a floating text.

+ +

The floatingText element is a member of the +model.divPart class, and can thus appear within +any division level element in the same way as a paragraph. For +example, texts such as the Decameron or the +Arabian Nights might be regarded as containing many +floating texts embedded within another single text, the framing +narrative, rather than as groups of discrete texts in which the +fragments of framing narrative are regarded as front or back matter. +

+ +

As an example, we consider an 18th century text The Lining to +the <hi>Patch-Work Screen</hi>, by Jane Barker (1726). This +lengthy narrative contains nearly a hundred distinct tales +embedded (as the title suggests) in a single patchwork. The work +begins by introducing the central character, Galecia, but within a few pages +launches into a distinct narrative, the story of Captain Manly: + + +

Galecia one Evening setting alone in her Chamber by a clear Fire, +and a clean Hearth [...] reflected on the Providence of our +All-wise and Gracious Creator [...]

+

She was thus ruminating, when a Gentleman enter'd the Room, the +Door being a jar [...] calling for a Candle, she beg'd a thousand +Pardons, engaged him to sit down, and let her know, what had so long +conceal'd him from her Correspondence. +

+ +The Story of Captain Manly +

Dear Galecia, said he, though you partly know the loose, or rather +lewd Life that I led in my Youth; yet I can't forbear relating part of +it to you by way of Abhorrence... + +I had lost and spent all I had in the World; in which I verified the +Old Proverb, That a Rolling Stone never gathers Moss, +

 + + +

+

Following the conclusion of Captain Manly's tale, we are +returned to Galecia, and almost immediately after that into two further +stories. +However, the Galecia narrative returns between each of the texts, +which is why we choose to represent them as floatingTexts: + + +

The Gentleman having finish'd his Story, Galecia waited on him to +the Stairs-head; and at her return, casting her Eyes on the Table, she +saw lying there an old dirty rumpled Book, and found in it the +following story:

+

IN the time of the Holy War when +Christians from all parts went into the Holy Land to oppose the Turks; +Amongst these there was a certain English Knight...

+ +

The King graciously pardoned the Knight; Richard was kindly receiv'd +into his Convent, and all things went on in good order: But from hence +came the Proverb, We must not strike Robert for +Richard.

 + +

By this time Galecia's Maid brought up her Supper; after which she +cast her Eyes again on the foresaid little Book, where she found the +following Story, which she read through before she went to bed. +

+The Cause of the Moors Overrunning +Spain +

King ———— of Spain at his Death, committed the Government of his +Kingdom to his Brother Don ——— till his little Son should come of +Age ...

+

Thus the little Story ended, without telling what Misery +befel the King and Kingdom, by the Moors, who over ran the Country for +many Years after. To which, we may well apply the Proverb, + + Who drives the Devil's Stages, + Deserves the Devil's Wages +

+ +

The reading this Trifle of a Story detained Galecia from her Rest +beyond her usual Hour; for she slept so sound the next Morning, that +she did not rise, till a Lady's Footman came to tell her, that his +Lady and another or two were coming to breakfast with her... +

+ +

+

In other multi-narrative texts, the individual nested tales may +have greater significance than the framing narratives, and it may +therefore be preferable to treat the fragments of framing narrative as +front or back matter associated with each nested tale. This is +commonly done, for example, in texts such as Chaucer's Canterbury +Tales, where each tale is typically presented with front matter in +which the teller of the tale is introduced, and back matter in which +the pilgrims comment on it.

+ +

It is important to distinguish between the uses of floatingText and quote. Whereas the semantics of quote suggest that its content derives from a source external to the current text, floatingText carries no such implication and is simply used whenever the richer content model that it provides is required to support the markup of a part of a text that is presented as a discrete inclusion. In some cases, such inclusions could be considered external (e.g., enclosures, attachments, etc.); often however, as in the examples above, the included text bears no signs of emanating from outside.

+ +

floatingText and quote may be used in combination. For a text with rich internal structure that is quoted at length, floatingText might be used within quote. Also, like a unitary text, floatingText may include one or more quoted sections, each marked with a quote element.

+ +
+ +
Virtual Divisions +

Where the whole of a division can be automatically generated, for +example because it is derived from +another part of this or another document, an encoder may prefer not to represent it +explicitly but instead simply mark its location by means of a +processing instruction, or by using the special purpose +divGen element: + +

+

This element is made available by the model.divGenLike class of which it is the sole +element. The divGen element is a member of the +att.typed class, from which it inherits the +type and subtype attributes. It may appear +wherever a div or div1 (div2, etc.) element may appear.

+ + + +

For example, if the table of contents (toc) for a given work is simply +derived by copying the first head element from each +div element in a text, it might be more easily encoded as +follows: + +Similarly, in a digital edition combining a transcribed version +of some text with a translated version of it, it may be desired to +represent the transcript, the translation, and an aligned version of +the two as three distinct divisions. This could be achieved by an +encoding like the following: +

+
+
The processing to be carried out when a +divGen element is rendered will be determined by the +application program or stylesheet in use: the function of the TEI +markup is simply to identify the location at which the virtual +division is to be generated, and also to provide some information +about the kind of division to be generated. As such it may be regarded +as a special kind of processing instruction, and could equally well be +represented by one.

+ +
+ + +
Front Matter +

By front matter we mean distinct sections of a text +(usually, but not necessarily, a printed one), prefixed to it by way of +introduction or identification as a part of its production. Features +such as title pages or prefaces are clear examples; a less definite +case might be the prologue attached to a play. The front matter of an +encoded text should not be confused with the TEI header described in +chapter , which serves as a kind of front matter for +the computer file itself, not the text it encodes. +

+

An encoder may choose simply to ignore the front matter in a text, +if the original presentation of the work is of no interest, or for +other reasons; alternatively some or all components of the front matter +may be thought worth including with the text as components of the +front element.This decision should be recorded in the +samplingDecl element of the header. With the exception of +the title page, (on which see section ), front +matter should be encoded using the same elements as the rest of a text. +As with the divisions of the text body, no other specific tags are +proposed here for the various kinds of subdivision which may appear +within front matter: instead either numbered or un-numbered +div elements may be used. The following suggested +valuesAs with all lists of suggested +values for attributes, it is recommended that software +written to handle TEI-conformant texts be prepared to recognize and +handle these values when they occur, without limiting the user to the +values in this list. +for the type attribute may be used to distinguish various +kinds of division characteristic of front matter: + +A foreword or preface addressed to + the reader in which the author or publisher explains the + content, purpose, or origin of the text. +A formal declaration of + acknowledgment by the author in which persons and institutions + are thanked for their part in the creation of a text. +A formal offering or dedication of + a text to one or more persons or institutions by the author. +A summary of the content of a text as + continuous prose. +A table of contents, specifying the + structure of a work and listing its constituents. + The list + element should be used to mark its structure. +A pictorial frontispiece, + possibly including some text. +

+

The following extended example demonstrates how various parts of the +front matter of a text may be encoded. The front part begins with a +title page, which is presented in section below. +This is followed by a dedication and a preface, each of which is encoded +as a distinct div: +

+

To my parents, Ida and Max Fish

+
+
Preface +

The answer this book gives to its title question is there is + and there isn't.

+

Chapters 1–12 have been previously published in the + following journals and collections: + + chapters 1 and 3 in New literary History + chapter 10 in Boundary II (1980) + . + I am grateful for permission to reprint.

+ S.F. +
+

+

The front matter concludes with another div element, shown +in the next example, this time containing a table of contents, which +contains a list element (as described in section +). Note the use of the ptr element to provide +page-references: the implication here is that the target identifiers +supplied (fish1, fish2, etc.) will correspond with identifiers used for +the div elements containing chapters of the text itself. (For the +ptr element, see .) +

+ Contents + + Introduction, or How I stopped Worrying and Learned to Love + Interpretation + + + Part One: Literature in the Reader + Literature in the Reader: Affective Stylistics + + What is Stylistics and Why Are They Saying Such + Terrible Things About It? + +
+
Introduction + +
+
Literature in the Reader + +
+
What is stylistics? + +
+ +Alternatively, the pointers in the index might link to the page breaks +at which a chapter begins, assuming that these have been included in +the markup: + + Literature in the Reader: Affective Stylistics + 24 + +
Literature in the Reader + + +
+ + +

+

The following example uses numbered divisions to mark up the front +matter of a medieval text. +Note that in this case no title page in the modern +sense occurs; the title is simply given as a heading at the start of the +front matter. Note also the use of the type attribute on the +div elements to indicate document elements comparatively +unusual in modern books such as the initial prayer: + + +

Here bygynniþ a book of contemplacyon, þe whiche + is clepyd þE CLOWDE OF VNKNOWYNG, + in þe whiche a soule is onyd wiþ GOD.

+ + + Here biginneþ þe preyer on þe prologe. +

God, unto whom alle hertes ben open, & unto whome alle wille + spekiþ, & unto whom no priue þing is hid: I beseche + þee so for to clense þe entent of myn hert wiþ þe + unspekable 3ift of þi grace, þat I may parfiteliche + loue þee & worþilich preise þee. Amen.

+ + + Here biginneþ þe prolog. +

In þe name of þe Fader & of þe Sone & + of þe Holy Goost.

+

I charge þee & I beseeche þee, wiþ as moche + power & vertewe as þe bonde of charite is sufficient + to suffre, what-so-euer þou be þat þis book schalt + haue in possession ...

+ + + Here biginneþ a table of þe chapitres. + + + Of foure degrees of Cristen mens leuing; & of þe + cours of his cleping þat þis book was maad vnto. + + A schort stering to meeknes & to þe werk of þis + book + + Of somme certein tokenes bi þe whiche a man may proue + wheþer he be clepid of God to worche in þis werk. + + & here eendeþ þe table of þe chapitres. + + + +

+

If, however, the table of contents can be automatically generated +from the remainder of the text, it may be preferable simply to mark +its presence, either by means of an empty divGen element or +by using an appropriate processing instruction.

+
+
Title Pages +

Detailed analysis of the title page and other +preliminaries of older printed books and manuscripts is of +major importance in descriptive bibliography and the cataloguing of +printed books; such analysis may require a rather more detailed module +than that proposed here. The following elements are +suggested as a means of encoding the major features of most title pages: + + + + + + + + + + + + + + +

+

These elements constitute the model.titlepagePart class. Together with the figure + element described in chapter , any number of elements +from this class can appear within a titlePage element. The figure element is included so +as to enable encoders to record the presence of complex non-textual +material on a title page. For simple cases such as printers' +ornaments or illustrations the graphic element discussed +in section should be adequate.

+

The elements listed above, together with the head element, +also constitute the class model.pLike.front. The elements in this class can +appear within a minimal front element without any need to +group them together and encode a complete title page.

+

Encoders wishing to add new elements to either class may do so +using the methods described in section . Two +examples of the use of these elements follow. First, the title page of +the work discussed earlier in this section: + + + Is There a Text in This Class? + The Authority of Interpretive Communities + + Stanley Fish + + Harvard University Press + Cambridge, Massachusetts + London, England + +

+

Second, a characteristically verbose 17th century example. Note the +use of the lb tag to mark the line breaks of the original +where necessary: + + + THE + Pilgrim's Progress + FROM + THIS WORLD, + TO + That which is to come: + Delivered under the Similitude of a + DREAM + Wherein is Discovered, + The manner of his setting out, + His Dangerous Journey; And safe + Arrival at the Desired Countrey. + + + I have used Similitudes,Hos. 12.10 + + By John Bunyan. + Licensed and Entred according to Order. + + LONDON, + Printed for Nath. Ponder + at the Peacock in the Poultrey + near Cornhil, 1678. +

+

Where, as here, it is considered important to encode salient +features of the way a title page was originally rendered, +the techniques exemplified in may also be +useful.

+ + + + +

Where title pages are encoded, their physical rendition is +often of considerable importance. One approach to this requirement +would be to use the seg tag, described in chapter , to segment the typographic content of each part of the +title page, and then use the global rend attribute to specify +its rendition. Another would be to use a module specialized for the +description of typographic entities such as pages, lines, rules, etc., +bearing special-purpose attributes to describe line-height, leading, +degree of kerning, font, etc. Further discussion of these problems is +provided in chapter . +

+ + + + + + + +
+
Back Matter +

Conventions vary as to which elements are grouped as back matter and +which as front. For example, some books place the table of contents at +the front, and others at the back. Even title pages may appear at the +back of a book as well as at the front. The content model for +back and front elements are therefore identical. +

+

The following suggested values may be used for the type +attribute on all division elements, in order to distinguish various +kinds of division characteristic of back matter: + +An ancillary self-contained section of +a work, often providing additional but in some sense extra-canonical +text. +A list of terms associated with definition texts +(glosses): this should be encoded as a list type="gloss" +(see section ). +A section in which textual or +other kinds of notes are gathered together. +A list of bibliographic citations: this should be encoded +as a listBibl (see section ). +Any form of index to the work. +A statement appearing at the end of a book describing the +conditions of its physical production. +

+

No additional elements are proposed for the encoding of back matter +at present. Some characteristic examples follow; first, an index (for +the case in which a printed index is of sufficient interest to merit +transcription): + +

+ Index + + Actors, public, paid for the contempt attending + their profession, 263 + Africa, cause assigned for the barbarous state of + the interior parts of that continent, 125 + Agriculture + + ancient policy of Europe unfavourable to, 371 + artificers necessary to carry it on, 481 + cattle and tillage mutually improve each other, 325 + wealth arising from more solid than that which proceeds + from commerce 520 + + Alehouses, the number of, not the efficient cause of drunkenness, 461 + +
+ + +Note that if the page breaks in the original source have also been +explicitly encoded, and given identifiers, the references to them in the +above index can more usefully be recorded as links. For example, +assuming that the encoding of page 461 of the original source starts +like this: + +then the last item above might be encoded more usefully in either +of the following forms: + Alehouses, the number of, not +the efficient cause of drunkenness, 461 + Alehouses, the number of, not the efficient cause of drunkenness, +

+

Next, a back-matter division in epistolary form: + +

+ A letter written to his wife, founde with this booke + after his death. +

The remembrance of the many wrongs offred thee, and thy + unreproued vertues, adde greater sorrow to my miserable state, + than I can utter or thou conceiue. ... + ... yet trust I in the world to come to find mercie, by the + merites of my Saiuour to whom I commend thee, and commit + my soule.

+ Thy repentant husband for his disloyaltie, + Robert Greene. +

Faelicem fuisse infaustum

 + FINIS +
+ +

+

And finally, a list of corrigenda and addenda with pseudo-epistolary +features: + +

+ Addenda + M. Scriblerus Lectori +

Once more, gentle reader I appeal unto thee, from the shameful +ignorance of the Editor, by whom Our own Specimen of +Virgil hath been mangled in such miserable manner, that +scarce without tears can we behold it. At the very entrance, Instead +of προλεγομενα, lo! +προλεγωμενα with an Omega! +and in the same line consulâs with a circumflex! +In the next page thou findest leviter perlabere, +which his ignorance took to be the infinitive mood of +perlabor but ought to be +perlabi ... Wipe away all these +monsters, Reader, with thy quill.

+
+ + + +

+ + + + + +
+
+ Module for Default Text Structure +

The module described by the present chapter has the following + components: + + Default Text Structure + Default text structure + Structure textuelle par défaut + 預設文件結構 + Struttura standard del testo + Estrutura do texto por defeito + テキスト構造モジュール + + + + + + + + The selection and combination of modules to form a TEI schema is + described in .

+
+
diff --git a/P5/Source/Guidelines/fr/Dedication.xml b/P5/Source/Guidelines/fr/Dedication.xml deleted file mode 120000 index e4cfe6538e..0000000000 --- a/P5/Source/Guidelines/fr/Dedication.xml +++ /dev/null @@ -1 +0,0 @@ -../en/./Dedication.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/Dedication.xml b/P5/Source/Guidelines/fr/Dedication.xml new file mode 100644 index 0000000000..fe156db83a --- /dev/null +++ b/P5/Source/Guidelines/fr/Dedication.xml @@ -0,0 +1,24 @@ + + + + +
+ Dedication +

+ + In memoriam + + Donald E. Walker + 22 November 1928 – 26 November 1993 + + + Antonio Zampolli + 1937 – 22 August 2003 + + + Sebastian Rahtz + 13 February 1955 – 15 March 2016 + + +

+
diff --git a/P5/Source/Guidelines/fr/FM1-IntroductoryNote.xml b/P5/Source/Guidelines/fr/FM1-IntroductoryNote.xml deleted file mode 120000 index cbe82c47b8..0000000000 --- a/P5/Source/Guidelines/fr/FM1-IntroductoryNote.xml +++ /dev/null @@ -1 +0,0 @@ -../en/./FM1-IntroductoryNote.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/FM1-IntroductoryNote.xml b/P5/Source/Guidelines/fr/FM1-IntroductoryNote.xml new file mode 100644 index 0000000000..1ab7864174 --- /dev/null +++ b/P5/Source/Guidelines/fr/FM1-IntroductoryNote.xml @@ -0,0 +1,301 @@ + + + + + +
+ Preface and Acknowledgments + +

This publication constitutes the fifth distinct version of the + Guidelines for Electronic Text Encoding and + Interchange, and the first complete revision since the + appearance of P3 in 1994. It includes substantial amounts of new + material and a major revision of the underlying technical + infrastructure. With this version, these Guidelines enter a new stage in + their development as a community-maintained open source project. This + edition is the first version to have benefitted from the close + overview and oversight of an elected TEI Technical Council. The + editors are therefore particularly pleased to acknowledge with + gratitude the hard work and dedication put into this project by the + Council over the last five years.

+ +

The Chair of the TEI Board sits on the Technical Council, and the + Board appoints the Chair of the Technical Council and one other + member of the Council. Other Council members are all elected by the + Consortium membership, and serve periods of up to two years at a + time. The names and affiliations of all Council members who served + during the production of this edition of the Guidelines are listed + below. + + + Board Chair + 2004–2005: Julia Flanders (Brown University) + 2006: Matthew Zimmerman (New York University) + 2007–2011: Daniel O'Donnell (University of Lethbridge) + 2011: Martin Mueller (Northwestern University) + 2011–2012: John Unsworth (University of Illinois at Urbana-Champaign / Brandeis University) + 2012–2015: Elena Pierazzo (King's College London / Université Stendhal-Grenoble 3) + 2016–2017: Michelle Dalmau (Indiana University) + 2018–2021: Kathryn Tomasek (Wheaton College) + 2022-2023: Diane K. Jakacki (Bucknell University) + + + + Technical Council Chair + 2002–2003: John Unsworth (University of Virginia) + 2003–2007: Christian Wittern (Kyoto University) + 2008–2011: Laurent Romary (Max Planck Digital Library / Inria & Humboldt-Universität zu Berlin) + 2012–2014: James Cummings (University of Oxford) + 2015–2017: Hugh Cayless (Duke University) + 2018–2022: Martina Scholger (University of Graz) + 2023: Elisa Beshero-Bondar (Penn State Erie, The Behrend College) + + + + Members of the Technical Council Appointed by the TEI Board + 2001–2009: Sebastian Rahtz (University of Oxford) + 2010–2014: Lou Burnard (University of Oxford / TGE Adonis / Independent Consultant) + + + + Appointed Editors + 2001–2007: Syd Bauman (Brown Univesity) + 2001–2007: Lou Burnard (University of Oxford) + + + + Elected Members of the Technical Council + 2011–2012: Piotr Bański (University of Warsaw) + 2010–2013: Brett Barney (University of Nebraska) + 2013–2023: Syd Bauman (Brown University / Northeastern University) + 2021–2025: Helena Bermúdez Sabel (Université de Neuchâtel / JinnTec) + 2016–2024: Elisa Beshero-Bondar (University of Pittsburgh at Greensburg / Penn State Erie, The Behrend College) + 2022: Elli Bleeker (Huygens Institute for the History of the Netherlands) + 2019–2020: Vanessa Bigot Juloux (Ecole Pratique des Hautes Etudes / Paris Sciences et Lettres / Andrews University, Michigan) + 2003–2006, 2017–2018: Alejandro Bia (University of Alicante) + 2004–2007: David Birnbaum (University of Pittsburgh) + 2008–2013: Gabriel Bodard (King's College London) + 2008–2009: Peter Boot (Huygens Institute for Netherlands History) + 2020–2021: Meaghan Brown (Papers of the Bibliographical Society of America) + 2007–2008: Tone Merete Bruvik (University of Bergen) + 2015–2016: Lou Burnard (Independent Consultant) + 2013–2023: Hugh Cayless (New York University / Duke University) + 2014–2015: Fabio Ciotti (University of Rome “Tor Vergata”) + 2007–2009: Arianna Ciula (King's College London / European Science Foundation) + 2005–2019: James Cummings (University of Oxford / Newcastle University) + 2020: Nicholas Cole (Pembroke College Oxford) + 2002–2007, 2010: Matthew Driscoll (University of Copenhagen) + 2002–2004: David Durand (Ingenta plc) + 2002–2004: Tomas Erjavec (Jozef Stefan Institute, Ljubljana) + 2014–2015: Stefanie Gehrke (Biblissima) + 2010–2013: Kevin Hawkins (University of Michigan) + 2010–2015: Martin Holmes (University of Victoria) + 2002: Fotis Jannidis (University of Munich) + 2021–2023: Janelle Jenstad (University of Victoria) + 2006: Amit Kumar (University of Illinois at Urbana-Champaign) + 2020–2021: Jessica H. Lu (University of Maryland) + 2015–2016: Stefan Majewski (Austrian National Library) + 2002: Martin Mueller (Northwestern University) + 2013–2014, 2016–2019: Elli Mylonas (Brown University) + 2010–2011: Julianne Nyhan (University of Trier / University College London) + 2023-2025: Patricia O Connor (Independent Researcher) + 2008–2011: Elena Pierazzo (King's College London) + 2006–2007, 2009–2010: Dot Porter (University of Kentucky / Digital Humanities Observatory / Indiana University) + 2002–2003: Merillee Proffitt (Research Libraries Group) + 2002: Peter Robinson (De Montfort University) + 2009–2014: Sebastian Rahtz (University of Oxford) + 2002: Geoffrey Rockwell (Macmaster University) + 2002–2007: Laurent Romary (Inria / CNRS / Max Planck Digital Library) + 2008–2009, 2012–2015: Paul Schaffner (University of Michigan) + 2016–2024: Martina Scholger (University of Graz) + 2003–2007: Susan Schreibman (University of Maryland) + 2022-2024: Sabine Seifert (University of Potsdam) + 2008–2009: David Sewell (University of Virginia) + 2004–2005: Natasha Smith (University of North Carolina at Chapel Hill) + 2014–2022: Peter Stadler (Carl-Maria-von-Weber-Gesamtausgabe / University of Paderborn) + 2017–2019: Sarah Stanley (Florida State University) + 2023: Joey Takeda (Digital Humanities Innovation Lab, Simon Fraser University) + 2008–2009: Manfred Thaller (University of Cologne) + 2006–2007: Conal Tuohy (Victoria University of Wellington) + 2016–2024: Magdalena Turska (eXist Solutions / University of Oxford) + 2004–2005: Edward Vanhoutte (Royal Academy of Dutch Language and Literature) + 2015–2023: Raffaele Viglianti (University of Maryland) + 2005–2008: John Walsh (Indiana University) + 2012–2013: Rebecca Welzenbach (University of Michigan) + 2002–2005: Perry Willett (Indiana University / University of Michigan) + 2011–2012: Stuart Yeates (New Zealand Electronic Text Centre) + +

+ +

The bulk of the Council's work has been carried out by email and by +regular telephone conference. In addition, the Council has held many +two-day face-to-face meetings. During production of P5, +these meetings were generously hosted by the following institutions: + + King's College, London (2002) + Oxford University Computing Services (2003) + Royal Academy of Dutch Language and Literature, Ghent (2004) + AFNOR: Association française de normalisation, Paris (2005) + Institute for Research in Humanities, Kyoto University (2006) + Berlin-Brandenburgische Akademie der Wissenschaften, Berlin (2007) + National University of Ireland, Galway (2008) + Ecole Normale Supérieure, Lyon (2009) + Royal Irish Academy, Dublin (2010) + Big Ten Center, Chicago (2011) + Inria, Paris (2011) + University of Michigan, Ann Arbor (2012) + University of Oxford (2012) + Brown University (2013) + University of Oxford (2013) + University of Oxford (2014) + Duke University (2014) + University of Michigan, Ann Arbor (2015) + Lyon (2015) + Brown University (2016) + Austrian Academy of Sciences (2016) + Prague (2017) + Victoria (2017) + CCEH, Cologne University (2018) + University of Tokyo (2018) + Folger Shakespeare Library, Washington, D.C. (2019) + ZIM-ACDH, University of Graz (2019) + Virtual meeting (May 2020) + Virtual meeting (October 2020) + Short virtual meeting (January 2021) + Short virtual meeting (May 2021) + Short virtual meeting (October 2021) + Short virtual (April 2022) + Newcastle University (September 2022) + University of Guelph (May 2023) + Paderborn University (September 2023) +

+ +

During the production of TEI P5, the Council chartered a number +of smaller workgroups and similar activities, each of which +made significant contribution to the intellectual content of the +work. Active members of these are listed below: + + + +

Active between July 2001 and January 2005, this group revised and +developed the recommendations now forming chapters +and . It was chaired by Christian Wittern, and its +membership included: Deborah Anderson (Berkeley); Michael Beddow +(independent scholar); David Birnbaum (University of Pittsburgh); +Martin Duerst (W3C/Keio University); +Patrick Durusau (Society of Biblical Literature); +Tomohiko Morioka (Kyoto University); + and Espen Ore (National Library of Norway).

+ + + + +

Active between February 2003 and February 2005, this group developed the +material now forming . It was chaired by Sebastian +Rahtz, and its membership included: +Alejandro Bia; +David G. Durand; +Laurent Romary; +Norman Walsh (Sun Microsystems); +and Christian Wittern.

+ + + + +

Active between February 2002 and January 2006, this +group reviewed and expanded the +material now largely forming part of . It was +chaired by David G. Durand, and its membership included: +Jean Carletta (Edinburgh University); +Chris Caton (University of Oxford); +Jessica P. Hekman (Ingenta plc); +Nancy M. Ide (Vassar College); +and +Fabio Vitali (University of Bologna).

 + + + +

Active between February 2003 and December 2005, this group reviewed +and finalised the material now forming . It was +chaired by Matthew Driscoll and comprised David Birnbaum and Merrilee +Proffitt, in addition to the TEI Editors.

+ + + +

Active between January 2006 and May 2007, this group formulated the +new material now forming part of . It was chaired +by Matthew Driscoll. and its membership included +Gabriel Bodard (King's College London); +Arianna Ciula; +James Cummings; +Tom Elliott (University of North Carolina at Chapel Hill); +Øyvind Eide (University of Oslo); +Leif Isaksen (Oxford Archaeology plc); +Richard Light (private consultant); +Tadeusz Piotrowski (Opole University); +Sebastian Rahtz; +and +Tatiana Timcenko (Vilnius University). +

+ + + + +

Active between January 2003 and August 2007, this group reviewed the +material now presented in and revised it for +inclusion in ISO Standard 24610. It was chaired by Kiyong Lee (Korea +University), and its active membership included the following: +Harry Bunt (Tilburg); +Lionel Clément (INRIA); +Eric de la Clergerie (INRIA); +Thierry Declerck (Saarbrücken); +Patrick Drouin (University of Montréal); +Lee Gillam (Surrey University); +and +Kōiti Hasida (ICOT). +

+

+ +

From 2000 to 2008 the TEI had two appointed Editors, Lou Burnard + (University of Oxford) and Syd Bauman (Brown University), who served + ex officio on the Council and, as far as possible, + on all Council workgroups.

+ + +

The Council also oversees an Internationalization and Localization +project, led by Sebastian Rahtz and with funding from the ALLC. This +activity, ongoing since October 2005, is engaged in translating key +parts of the P5 source into a variety of languages.

+ +

Production of the translations currently included in P5 has been +coordinated by the following: + + Marcus Bingenheimer (Chung-hwa Institute +of Buddhist Studies, Taipei / Temple University) and Weining Hwang (Würzburg University) +Pierre-Yves Duchemin (ENSSIB); Jean-Luc +Benoit (ATILF); Anila Angjeli (BnF); Joëlle Bellec Martini (BnF); +Marie-France Claerebout (Aldine); Magali Le Coënt (BIUSJ); Florence +Clavaud (EnC); Cécile Pierre (BIUSJ). + + Werner Wegstein (Würzburg University), Franz Fischer (Cologne University), Martina Scholger (University of Graz) and Peter Stadler (Paderborn University) +Marco Venuti (University of Venice) and Letizia Cirillo +(University of Bologna) + Ohya Kazushi (Tsurumi University), Kiyonori Nagasaki (University of Tokyo) and Martin Holmes (University of Victoria) +Beom-mo Kang and Jungha Hong (Korea University) + Carmen Arronis Llopis (University of + Alicante), Alejandro Bia (Miguel Hernández University), Gimena del Rio Riande (Consejo Nacional de Investigaciones Científicas y Técnicas) and Susanna Allés-Torrent (University of Miami) + +

+ +

Any one who works closely with the TEI Guidelines, whether as +translator, editor, or reader is constantly reminded of the +ambitious scope and exceptionally high editorial standards set by the original +project, now approaching twenty years ago. It is appropriate therefore to retain +a sense of the history of this document, as it has evolved since its +first appearance in 1990, and to acknowledge with gratitude the +contributions made to that evolution by very many individuals and +institutions around the world. The original prefatory notes to each +major edition of the Guidelines recording these names are therefore +preserved in an appendix to the current edition (see ).

+
diff --git a/P5/Source/Guidelines/fr/FS-FeatureStructures.xml b/P5/Source/Guidelines/fr/FS-FeatureStructures.xml deleted file mode 120000 index 67724271eb..0000000000 --- a/P5/Source/Guidelines/fr/FS-FeatureStructures.xml +++ /dev/null @@ -1 +0,0 @@ -../en/./FS-FeatureStructures.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/FS-FeatureStructures.xml b/P5/Source/Guidelines/fr/FS-FeatureStructures.xml new file mode 100644 index 0000000000..989a676e90 --- /dev/null +++ b/P5/Source/Guidelines/fr/FS-FeatureStructures.xml @@ -0,0 +1,2025 @@ + + + + +
Feature Structures + +

A feature structure is a general purpose data +structure which identifies and groups together individual +features, each of which associates a name with one or +more values. Because of the generality of feature structures, they +can be used to represent many different kinds of information, but they +are of particular usefulness in the representation of linguistic +analyses, especially where such analyses are partial, or +underspecified. Feature structures represent the +interrelations among various pieces of information, and their +instantiation in markup provides a metalanguage for the +generic representation of analyses and interpretations. Moreover, +this instantiation allows feature values to be of specific +types, and for restrictions to be placed on the values +for particular features, by means of feature system +declarations.The recommendations of this chapter have +been adopted as ISO Standard 24610-1 Language Resource +Management — Feature Structures — Part One: Feature Structure Representation +

+
Organization of this Chapter +

This chapter is organized as +follows. Following this introduction, section +introduces the elements fs and f, used to represent +feature structures and features respectively, together with the +elementary binary feature value. Section introduces elements for representing other kinds of +atomic feature values such as symbolic, +numeric, and string values. Section introduces the notion of predefined +libraries or groups of features or feature values along +with methods for referencing their components. Section introduces complex values, in particular +feature-structures as values, thus enabling feature structures to be +recursively defined. Section discusses other +complex values, in particular values which are collections, organized +as sets, bags, and +lists. Section discusses how the +operations of alternation, negation, and collection of feature values +may be represented. Section discusses ways of +representing underspecified, default, or uncertain values. Section + discusses how analyses may be linked to other +parts of an encoded text. Section describes the +feature system declaration, a construct which provides +for the validation of typed feature structures. + +Formal definitions for +all the elements introduced in this chapter are provided in section +.

+ + +
+ +
Elementary Feature Structures and the Binary +Feature Value +

The fundamental elements used to represent a feature structure +analysis are f (for feature), which represents a +feature-value pair, and fs (for feature +structure), which represents a structure made up of such +feature-value pairs. The fs element has an optional +type attribute which may be used to represent typed feature +structures, and may contain any number of f elements. An +f element has a required name attribute and an +associated value. The value may be simple: that is, a +single binary, numeric, symbolic (i.e. taken from a restricted set of +legal values), or string value, or a collection of such values, +organized in various ways, for example, as a list; or it may be +complex, that is, it may itself be a feature structure, thus providing +a degree of recursion. Values may be under-specified or defaulted in +various ways. These possibilities are all described in more detail in +this and the following sections. +

+

Feature and feature-value representations (including feature +structure representations) may be embedded directly at any point in an +XML document, or they may be collected together in special-purpose +feature or feature-value libraries. The components of +such libraries may then be referenced from other feature or +feature-value representations, using the feats or +fVal attribute as appropriate.

+

We begin by considering the simple case of a feature structure +which contains binary-valued features only. The following three XML elements are +needed to represent such a feature structure: + + + + + +The attributes feats and the fVal are not +discussed in this section: they provide an alternative way of +indicating the content of an element, as further discussed in section +. +

+

An fs element containing f elements with binary +values can be straightforwardly used to encode the matrices +of feature-value specifications for phonetic segments, such as the +following for the English segment [s]. + +--- ---+ +| consonantal + | +| vocalic - | +| voiced - | +| anterior + | +| coronal + | +| continuant + | +| strident + | ++--- ---+ +

+

This representation may be encoded in XML as follows: + + + + + + + + + +Note that fs elements may have an optional type +attribute to indicate the kind of feature structure in question, +whereas f elements must have a name attribute to +indicate the name of the feature. Feature structures need not be +typed, but features must be named. + + +Similarly, the fs element +may be empty, but the f element must specify its value either +directly as content, by means of the fVal attribute, or +implicitly by reference to a feature system declaration.

+

The restriction of specific features to specific types of values +(e.g. the restriction of the feature strident +to a binary value) requires additional validation, as does any +restriction on the features available within a feature structure of a +particular type (e.g. whether a feature structure of type +phonological segment necessarily contains a +feature voiced). Such validation may be carried +out at the document level, using special purpose processing, at the +schema level using additional validation rules, or at the declarative +level, using an additional mechanism such as the feature-system +declaration discussed in .

+

Although we have used the term binary for this kind +of value, and its representation in XML uses values such as +true and false (or, equivalently, +1 and 0), it should be noted that such +values are not restricted to propositional assertions. As this example +shows, this kind of value is intended for use with any binary-valued +feature.

+ +
+
Other Atomic Feature Values +

Features may take other kinds of atomic value. In this section, we +define elements which may be used to represent: symbolic +values, numeric values, and string +values. The module defined by this chapter allows for the +specification of additional datatypes if necessary, by extending the +underlying class model.featureVal.single. If this is done, it +is recommended that only the basic W3C datatypes should be used; more +complex datatyping should be represented as feature structures. + + + + +

+

The symbol element is used for the value of a feature when +that feature can have any of a small, finite set of possible values, +representable as character strings. For example, the following might +be used to represent the claim that the Latin noun form +mensas +(tables) has accusative case, feminine gender, and +plural number: + + + + +

+

More formally, this representation shows a structure in which three +features (case, gender, and +number) are used to define morpho-syntactic properties of +a word. Each of these features can take one of a small number of +values (for example, case can be nominative, +genitive, dative, accusative, +etc.) and it is therefore appropriate to represent the values taken +in this instance as symbol elements. Note that, instead of +using a symbolic value for grammatical number, one could have named +the feature singular or plural and given it +an appropriate binary value, as in the following example: + + + + +Whether one uses a binary or symbolic value in situations like this is +largely a matter of taste.

+

The string element is used for the value of a +feature when that value is a string drawn from a very large or potentially +unbounded set of possible strings of characters, so that it would be +impractical or impossible to use the symbol element. The string +value is expressed as the content of the string element, +rather than as an attribute value. For example, one might encode a +street address as follows: + + 3418 East Third Street +

+

The numeric element is used when the value of a feature is a +numeric value, or a range of such values. For example, one might wish +to regard the house number and the street +name as different features, using an encoding like the following: + + + East Third Street +

+

If the numeric value to be represented falls within a specific +range (for example an address that spans several numbers), the +max attribute may be used to supply an upper limit: + + + East Third Street +

+

It is also possible to specify that the numeric value (or values) +represented should (or should not) be truncated. For example, assuming +that the daily rainfall in mm is a feature of interest for some +address, one might represent this by an encoding like the following: + + + This represents any of the infinite +number of numeric values falling between 0 and 1.3; by contrast + + + represents only two possible values: 0 and 1. +

+

Some communities of practice, notably those with a strong computer-science +bias, prefer to dissociate the information on the value of the given +feature from the specification of the data type that this value represents. +In such cases, feature values can be provided directly as textual content +of f, with the assumption that the data type is specified by the +schema. The following is an example taken from ISO 24612, presenting the +symbolic values for Active Voice and Simple Present Tense in the untyped +form:active +SimPre

+

As noted above, additional processing is necessary to ensure that +appropriate values are supplied for particular features, for example +to ensure that the feature singular is not given a value +such as symbol value="feminine"/. There are two +ways of attempting to ensure that only certain combinations of feature +names and values are used. First, if the total number of legal +combinations is relatively small, one can predefine all of them in a +construct known as a feature library, and then reference +the combination required using the feats attribute in the +enclosing fs element, rather than give it explicitly. This +method is suitable in the situation described above, since it requires +specifying a total of only ten (5 + 3 + 2) combinations of features +and values. Similarly, to ensure that only feature structures +containing valid combinations of feature values are used, one can put +definitions for all valid feature structures inside a feature +value library (so called, since a feature structure may be the +value of a feature). A total of 30 feature structures (5 × 3 +× 2) is required to enumerate all the possible combinations of +individual case, gender and number values in the preceding +illustration. We discuss the use of such libraries and their +representation in XML further in section below. +

+

However, the most general method of attempting to ensure that only legal +combinations of feature names and values are used is to provide a +feature-system declaration discussed in .

+

Whether at the level of feature-system declarations, feature- and +feature-value libraries, or individual features, it is possible to +align both feature names and their values with standardized external +data category repositories. See +section for more discussion of the need and +rationale for aligning the content of grammatical (and other) descriptions with +standardized external taxonomies. In the following example, both +the feature part_of_speech and its value +NN (standing for common noun) are aligned with the respective definitions +provided by the CLARIN Concept Registry (CCR). + + + + + + + +

+

Since the above representation takes up a lot of space and quickly becomes redundant and +error-prone, it is possible to delegate the task of aligning with external repositories to +elements such as fLib, fvLib, fDecl, or fsDecl to reduce the feature +representation at hand and to increase its readability at the same time, as shown in the example below. + + + + + + +

+

The value common_noun should best be listed (as an xml:id) either in a +library of feature values (fvLib, see the following section) or in a +taxonomy element.

+
+
Feature Libraries and Feature-Value Libraries +

As the examples in the preceding section suggest, the direct +encoding of feature structures can be verbose. Moreover, it is often +the case that particular feature-value combinations, or feature +structures composed of them, are re-used in different analyses. To reduce +the size and complexity of the task of encoding feature structures, one +may use the feats attribute of the fs element to point +to one or more of the feature-value specifications for that element. This indirect method of +encoding feature structures presumes that the f elements are +assigned unique xml:id values, and are collected together in +fLib elements (feature libraries). In the same way, feature +values of whatever type can be collected together in fvLib elements +(feature-value libraries). If a feature has as its +value a feature structure or other value which is predefined in this way, the +fVal attribute may be used to point to it, as discussed in +the next section. The following elements are used for representing feature libraries and feature-value libraries: + + + +

+

For example, suppose a feature library for phonological feature +specifications is set up as follows. + + + + + + + + + + + + + + + + + +

+

Then the feature structures that represent the analysis of the +phonological segments (phonemes) /t/, /d/, +/s/, and /z/ may be defined as follows. + + + + +

+

The preceding are but four of the 128 logically possible fully +specified phonological segments using the seven binary features listed in +the feature library. Presumably not all combinations of features +correspond to phonological segments (there are no strident vowels, for +example). The legal combinations, however, can be collected together, +each one represented as an identifiable fs element within a +feature-value library, as in the following example: + + + + + + + + +

+

Once defined, these feature structure values can also be reused. +Other f elements may invoke them by reference, using the +fVal attribute; for example, one might use them in a +feature value pair such as: rather than expanding the hierarchy of the +component phonological features explicitly.

+

The feature structure that concludes section above, identifying the +value of some part of speech to be a common noun, may be used in tandem with a +feature-value library, which offers a way to encode a grammatical tagset, in this case +containing labels for parts of speech: + + + + + + + +Such a feature-value library combines the standard short symbolic label for a part of speech (e.g., NN) with a +mnemonic identifier that can be referenced by means of fVal, and with a persistent identifier, maintained +in a public reference taxonomy repository together with the basic definition of the given concept.

+

Feature structures stored in the way presented in this section may also be associated with +the text which they are intended to annotate, either by a link from the text +(for example, using the TEI global ana attribute), or +by means of stand-off annotation techniques (for example, using the TEI +link element): see further section +below. +

+

Note that when features or feature structures are linked to in this +way, the result is effectively a copy of the item linked to into the +place from which it is linked. This form of linking should be distinguished from +the phenomenon of structure-sharing, where it is desired +to indicate that some part of an annotation structure appears +simultaneously in two or more places within the structure. This kind +of annotation should be represented using the vLabel element, as +discussed in below.

+
+
Feature Structures as Complex Feature Values +

Features may have complex values as well as atomic ones; the +simplest such complex value is represented by supplying an fs +element as the content of an f element, or (equivalently) by +supplying the identifier of an fs element as the value for +the fVal attribute on the f +element. Structures may be nested as deeply as appropriate, using this +mechanism. For example, an fs element may contain or point +to an f element, which may contain or point to an fs +element, which may contain or point to an f element, and so +on.

+

To illustrate the use of complex values, consider the following +simple model of a word, as a structure combining surface form +information, a syntactic category, and semantic information. Each word +analysis is represented as a fs type='word' element, +containing three features named surface, +syntax, and semantics. The first of these +has an atomic string value, but the other two have complex values, +represented as nested feature structures of types +category and act respectively: + + love + + + + + + + + + + + +

+

This analysis does not tell us much about the meaning of the +symbols verb or transitive. It might be +preferable to replace these atomic feature values by feature +structures. Suppose therefore that we maintain a feature-value +library for each of the major syntactic categories (N, V, ADJ, PREP): + + + + + + + + + + +

+

This library allows us to use shortcut codes (N, +V, etc.) to reference a complete definition for the +corresponding feature structure. Each definition may be explicitly +contained within the fs element, as a number of f +elements. Alternatively, the relevant features may be referenced by +their identifiers, supplied as the value of the feats +attribute, as in these examples: +<!-- ... --> +<fs xml:id="ADJ" type="adjective" feats="#F1 #F2"/> +<fs xml:id="PREP" type="preposition" feats="#F1 #F3"/> +<!-- ... --> + +

+

This ability to re-use feature definitions within multiple feature +structure definitions is an essential simplification in any realistic +example. In this case, we assume the existence of a feature library +containing specifications for the basic feature categories like the following: + + + + + + + + +

+

With such libraries in place, and assuming the availability of +similarly predefined feature structures for transitivity and +semantics, the preceding example could be considerably simplified: + +love + + + + + + + + + + + + +

+

Although in principle the fVal attribute could point to +any kind of feature value, its use is not recommended for simple +atomic values.

+
+
Re-entrant Feature Structures +

Sometimes the same feature value is required at multiple places +within a feature structure, in particular where the value is only +partially specified at one or more places. The vLabel element is +provided as a means of labelling each such re-entrancy point: + + + +

+

For example, suppose one wishes to represent noun-verb agreement as +a single feature structure. Within the representation, the feature +indicating (say) number appears more than once. To represent the fact +that each occurrence is another appearance of the same feature (rather +than a copy) one could use an encoding like the following: + + + + + + + + + + + + + + + + + + + + +

+

In the above encoding, the features named vb-num and +nm-num exhibit structure sharing. Their values, given as +vLabel elements, are understood to be references to the same +point in the feature structure, which is labelled by their +name attribute.

+

The scope of the names used to label re-entrancy points is that of the +outermost fs element in which they appear. When a feature +structure is imported from a feature value library, or referenced from +elsewhere (for example by using the fVal attribute) the +names of any +sharing points it may contain are implicitly prefixed by the identifier used +for the imported feature structure, to avoid name clashes. Thus, if +some other feature structure were to reference the fs element + given in the example above, for example in this way: then +the labelled points in the example would be interpreted as if they had the +name NVAL1.

+
+
Collections as Complex Feature Values +

Complex feature values need not always be represented as feature +structures. Multiple values may also be organized as sets, bags or +multisets, or lists of atomic values of any type. The vColl +element is provided to represent such cases: + + + +

+

A feature whose value is regarded as a set, bag, or list may have +any positive number of values as its content, or none at +all, (thus allowing for representation of the empty set, bag, or list). +The items in a list are ordered, and need not be distinct. The items +in a set are not ordered, and must be distinct. The items in a bag are +neither ordered nor distinct. Sets and bags are thus distinguished +from lists in that the order in which the values are specified does +not matter for the former, but does matter for the latter, while sets +are distinguished from bags and lists in that repetitions of values do +not count for the former but do count for the latter. +

+

If no value is specified for the org attribute, the +assumption is that the vColl defines a list of values. If the +vColl element is empty, the assumption is that it represents +the null list, set, or bag.

+

To illustrate the use of the org attribute, suppose that +a feature structure analysis is used to represent a genealogical tree, +with the information about each individual treated as a single feature +structure, like this: + + + + Daniel + Edouard + + + + + + + + + + + + + + + +

+

In this example, the vColl element is first used to supply +a list of name feature values, which together +constitute the forenames feature. Other features +are defined by reference to values which we assume are held in some +external feature value library (not shown here). For example, the +vColl element is used a second time to indicate that the +persons's siblings should be regarded as constituting a set rather +than a list. Each sibling is represented by a feature structure: in +this example, each feature structure is a copy of one specified in the +feature value library.

+

If a specific feature contains only a single feature structure as +its value, the component features of which are organized as a set, bag, +or list, it may be more convenient to represent the value as a +vColl rather than as an fs. For example, consider the +following encoding of the English verb form +sinks, which contains an +agreement feature whose value is a feature +structure which contains person and +number features with symbolic values. + + + + + + + + + + +

+

If the names of the features contained within +the agreement feature structure are +of no particular significance, the following simpler representation +may be used: + + + + + + + + + + +

+

The vColl element is also useful in cases where an analysis +has several components. In the following example, the French +word auxquels has a two-part analysis, +represented as a list of two values. The first specifies that the word contains a +preposition; the second that it contains a masculine plural relative +pronoun: + + + + + + + + + + + + + + + + + + +

+

The set, bag, or list which has no members is known as the null (or +empty) set, bag, or list. A vColl element with no content and +with no value for its feats attribute is interpreted as +referring to the null set, bag, or list, depending on the value of its +org attribute.

+

If, for example, the individual described by the +feature structure with identifier p027 (above) had no siblings, we might specify the +siblings feature as follows. + +

+

A vColl element may also collect together one or more other +vColl elements, if, for example one of the members of a set is +itself a set, or if two lists are concatenated together. Note that +such collections pay no attention to the contents of the nested +vColl elements: if it is desired to produce the union of two +sets, the vMerge element discussed below should be used to +make a new collection from the two sets.

+
+
Feature Value Expressions +

It is sometimes desirable to express the value of a feature as the +result of an operation over some other value (for example, as +not green, or as male or +female, or as the concatenation of two collections). Three +special purpose elements are provided to represent disjunctive +alternation, negation, and collection of values: + + + + + +

+
Alternation +

The vAlt element can be used wherever a feature value can +appear. It contains two or more feature values, any one of which is to +be understood as the value required. Suppose, for example, that we are +using a feature system to describe residential property, using such +features as number.of.bathrooms. In a +particular case, we might wish to represent uncertainty as to whether +a house has two or three bathrooms. As we have already shown, one +simple way to represent this would be with a numeric maximum: + +

+

A more general way would be to represent the +alternation explicitly, in this way: + +

+

The vAlt element represents alternation over feature +values, not feature-value pairs. If therefore the uncertainty relates +to two or more feature value specifications, each must be represented +as a feature structure, since a feature structure can always appear +where a value is required. For example, suppose that it is uncertain +as to whether the house being described has two bathrooms or two +bedrooms, a structure like the following may be used: + + + + + + +

+

Note that alternation is always regarded as exclusive: +in the case above, the implication is that having two bathrooms +excludes the possibility of having two bedrooms and vice versa. If +inclusive alternation is required, a vColl element may be +included in the alternation as follows: + + + + + + + + + +This analysis indicates that the property may have two bathrooms, two +bedrooms, or both two bathrooms and two bedrooms. +

+

As the previous example shows, the vAlt element can also +be used to indicate alternations among values of features organized as +sets, bags or lists. Suppose we use a feature +selling.points to describe items that are mentioned to +enhance a property's sales value, such as whether it has a pool or a +good view. Now suppose for a particular listing, the selling points include +an alarm system and a good view, and either a pool or a jacuzzi (but +not both). This situation could be represented, using the +vAlt element, as follows. + + + + alarm system + good view + + pool + jacuzzi + + + + +

+

Now suppose the situation is like the preceding except that one is +also uncertain whether the property has an alarm system or a good +view. This can be represented as follows. + + + + + alarm system + good view + + + pool + jacuzzi + + + + +

+

If a large number of ambiguities or uncertainties need to be +represented, involving a relatively small number of features and +values, it is recommended that a stand-off technique, for example +using the general-purpose alt element discussed in +section be used, rather than the +special-purpose vAlt element. +

+
+
Negation +

The vNot element can be used wherever a feature value can +appear. It contains any feature value and returns the complement of +its contents. For example, the feature +number.of.bathrooms in the following example +has any whole numeric value other than 2: + +

+

Strictly speaking, the effect of the vNot element is to +provide the complement of the feature values it contains, rather than +their negation. If a feature system declaration is available which defines the +possible values for the associated feature, then it is possible to say +more about the negated value. For example, suppose that the +available values for the feature case are declared to be +nominative, genitive, dative, or accusative, whether in a TEI feature +system declaration or +by some other means. Then the following two specifications are equivalent: + (i) + +(ii) + + + + + + +

+

If however no such system declaration is available, all that one +can say about a feature specified via negation is that its value is +something other than the negated value.

+

Negation is always applied to a feature value, rather than to a +feature-value pair. The negation of an atomic value is the set of all +other values which are possible for the feature.

+

Any kind of value can be negated, including collections +(represented by a vColl elements) or feature structures +(represented by fs elements). The negation of any complex +value is understood to be the set of values which +cannot be unified with it. Thus, for example, the negation of the +feature structure F is understood to be the set of feature structures +which are not unifiable with F. In the absence of a constraint +mechanism such as the Feature System Declaration, the negation of a +collection is anything that is not unifiable with it, including +collections of different types and atomic values. It will generally be +more useful to require that the organization of the negated value be +the same as that of the original value, for example that a negated set +is understood to mean the set which is a complement of the set, but +such a requirement cannot be enforced in the absence of a constraint +mechanism.

+
+
Collection of Values +

The vMerge element can be used wherever a feature value can +appear. It contains two or more feature values, all of which are to be +collected together. The organization of the resulting collection is +specified by the value of the org attribute, which need +not necessarily be the same as that of its constituent values if these +are collections. For example, one can change a list to a set, or vice versa.

+

As an example, suppose that we wish to represent the range of +possible values for a feature genders used to +describe some language. It would be natural to represent the possible +values as a set, using the vColl element as in the following +example: + + + + + + + + + +

+

Suppose however that we discover for some language it is necessary +to add a new possible value, and to treat the value of the +feature as a list rather than as a set. The vMerge element can +be used to achieve this: + + + + + + + + + + + + +

+ +
+
+
Default Values +

The value of a feature may be underspecified in a number of +different ways. It may be null, unknown, or uncertain with respect to +a range of known possibilities, as well as being defined as a negation +or an alternation. As previously noted, the specification of the range +of known possibilities for a given feature is not part of the current +specification: in the TEI scheme, this information is conveyed by the +feature system declaration. Using this, or some other +system, we might specify (for example) that the range of values +for an element includes symbols for masculine, feminine, and neuter, +and that the default value is neuter. With such definitions available +to us, it becomes possible to say that some feature takes the default +value, or some unspecified value from the list. The following special +element is provided for this purpose: + + + +

+

The value of an empty f element which also lacks an fVal +attribute is understood to be the most general +case, i.e. any of the available values. Thus, assuming the feature +system defined above, the following two representations are equivalent. + + + + + + + + +

+

If, however, the value is explicitly stated to be the default one, +using the default element, then the following two representations +are equivalent: + + +

+

Similarly, if the value is stated to be the negation of the +default, then the following two representations are equivalent: + + + + + +

+
+ + +
Linking Text and Analysis +

Text elements can be linked with feature structures using any of +the linking methods discussed elsewhere in these Guidelines (see for +example sections and ). +In the simplest case, the ana attribute may be used +to point from any element to an annotation of it, as in the following +example: + + The + closest + he + came + to + exercise + was + to + open + one + eye + + every + so + often + + , + if + someone + entered + the + room + + +

+

The values specified for the ana attribute reference +components of a feature-structure library, which represents all of the +grammatical structures used by this encoding scheme. (For illustrative +purposes, we cite here only the structures needed for the first six +words of the sample sentence): + + + + + + + + + + +The components of each feature structure in the library are +referenced in much the same way, using the +feats attribute to identify one or more f +elements in the following feature library (again, only a few of the +available features are quoted here): + + + + + + + + + + + + + + + + + +

+

Alternatively, a stand-off technique may be used, as in the following +example, where a linkGrp element is used to link selected +characters in the text Caesar seized control with +their phonological representations. + + + Caesar + seized + control. + + + + + + + + + + + + +

+

As this example shows, a stand-off solution requires that every +component to be linked to must be addressable in some way, by means of +an XPointer. To handle the +POS tagging example above, for example, each annotated element might be +given an identifier of some sort, as follows: + + The + closest + he + came + to + exercise + +It would then be possible to link each word to its intended +annotation in the feature library quoted above, as follows: + + + + + + + + +

+
+ + +
+Feature System Declaration +

The Feature System Declaration (FSD) is intended for use in conjunction with a + TEI-conforming text that makes use of fs (that is, feature structure) elements. + The FSD serves three purposes: + the encoder can list all of the feature names and feature values and give a prose + description as to what each represents. + the encoder can define what it means to be a well-formed feature structure, and + define constraints which may be used to determine whether a particular feature + structure is valid relative to a given theory stated in typed feature + logic. These may involve constraints on the range of a feature value, + constraints on what features are valid within certain types of feature structures, or + constraints that prevent the co-occurrence of certain feature-value pairs. + the encoder can define the intended interpretation of underspecified feature + structures. This involves defining default values (whether literal or computed) for + missing features.

+

The scheme described in this chapter may be used to document any +feature structure system, but is primarily intended for use with the +feature structure representation defined by the ISO 24610-1:2006 +standard, which corresponds with the recommendations presented in +these Guidelines, . This chapter relies upon, but +does not reproduce, formal definitions and descriptions presented more +thoroughly in the ISO standard, which should be consulted in case of +ambiguity or uncertainty.

+ +

The FSD serves an important function in documenting precisely what +the encoder intended by the system of feature structure markup used in +an XML-encoded text. The FSD is also an important resource which +standardizes the rules of inference used by software to validate the +feature structure markup in a text, and to infer the full +interpretation of underspecified feature structures.

+ +

The reader should be aware the terminology used in this document +does not always closely follow conventional practice in formal logic, +and may also diverge from practice in some linguistic applications of +typed feature structures. In particular, the term +interpretation when applied to a feature +structure is not an interpretation in the model-theoretic sense, but +is instead a minimally informative (or equivalently, most general) +extension of that feature +structure that is consistent with a set of constraints declared by an +FSD. In linguistic application, such a system of constraints is the +principal means by which the grammar of some natural language is +expressed. There is a great deal of disagreement as to what, if any, +model-theoretic interpretation feature structures have in such +applications, but the status of this formal kind of interpretation is +not germane to the present document. Similarly, the term +valid is used here as elsewhere in these +Guidelines to identify the syntactic state of well-formedness in the +sense defined by the logic of typed feature structures itself, as +distinct from and in addition to the +well-formedness that pertains at the level of +this encoding standard. No appeal to any notion from formal semantics +should be inferred.

+ +

We begin by describing how an encoded text is associated with one +or more feature system declarations. The second, third, and fourth +sections describe the overall structure of a feature system +declaration and give details of how to encode its components. The final +section offers a full example; fuller discussion +of the reasoning behind FSDs and another complete example are provided +in .

+
+Linking a TEI Text to Feature System Declarations +

In order for application software to use feature system +declarations to aid in the automatic interpretation of encoded texts, +or even for human readers to find the appropriate declarations which +document the feature system used in markup, there must be a formal +link from the encoded texts to the declarations. However, the +schema which declares the syntax of the Feature System itself +should be kept distinct from the feature structure schema, which is an +application of that system.

+ +

A document containing typed feature structures may simply include a +feature system declaration documenting those feature structures. A +more usual scenario, however, is that the same feature system +declaration (or parts of it) will be shared by many documents. In +either case, an fsDecl element for each distinct type of +feature structure used must be provided and associated with the type, +which is the value used within each feature structure for its +type attribute.

+ +

When the module defined in this chapter is included in an XML +schema, the following elements become available via the +model.fsdDeclPart class: + + + + + + +The fsdDecl element serves as a wrapper for declaring feature +systems and may be supplied either within the header +of a standard TEI document, or as a standalone document in its own +right. It contains one or more fsdLink or fsDecl +elements and may hold several fLib or fvLib as well.

+ + + +

For example, suppose that a document doc.xml +contains feature structures of two types: gpsg and +lex. We might simply embed an fsDecl element for +each within the header attached to the document as follows: + + + + + + + + + + + + + + + + + + + + + + + + + + +

+

In this case there is an implicit link between the fs +element and the corresponding fsDecl element because they +share the same value for their type attribute and appear +within the same document. This is a short cut for the more general +case which requires a more explicit link provided by means of the +fsdLink element, as demonstrated below.

+ +

Now suppose that we wish to create a second document which includes +feature structures of the same type. Rather than duplicate the +corresponding declarations, we will need to provide a means of +pointing to them from this second document. The easiestWays of pointing to components of a TEI document without +using an XML identifier are discussed in +way of accomplishing this is to add an XML identifier to each +fsDecl element in example.xml: + + + + + + + + + + +(Although in this case the XML identifier is simply an uppercase +version of the type name, there is no necessary connection between the +two names. The only requirement is that the XML identifier conform to +the standards required for identifiers, and that it be unique within +the document containing it.)

+

In the fsdDecl for the second document, we can now include +pointers to the fsDecl elements in the first: + + + + + + + + + + + + + + + + + + + + + +Note that in doc2.xml there is no requirement for the local +name for a given type of feature structures to be the same as that +used by example.xml. We assume in this encoding that the type +called lexx in doc2.xml is declared as +having identical constraints and other properties to those declared +for the type called lex in example.xml.

+ +

An fsdDecl may be given, as above, within the encoding +description of the teiHeader element of a TEI document +containing typed feature structures. Alternatively, it may appear +independently of any feature structures, as a document in its own +right with its own teiHeader. These options are both possible +because the element is a member of both the model.encodingDescPart class and the model.resource class.

+ +

The current recommendations provide no way of enforcing uniqueness +of the type values among fsdDecl elements, nor of +requiring that every type value specified on an fs +element be also declared on an fsdDecl element. Encoders +requiring such constraints (which might have some obvious utility in +assisting the consistency and accuracy of tagging) are recommended to +develop tools to enforce them, using such mechanisms as Schematron +assertions.

+ +
+
The Overall Structure of a Feature System Declaration +

A feature system declaration contains one or more feature +structure declarations, each of which has up to three parts: an optional description +(which gives a prose comment on what that type of feature structure +encodes), an obligatory set of feature declarations (which specify +range constraints and default values for the features in that type of +structure), and optional feature structure constraints (which specify +co-occurrence restrictions on feature values). + + + +

+

Feature declarations and feature structure constraints are +described in the next two sections. Note that the specification of +similar fsDecl elements can be simplified by devising an +inheritance hierarchy for the feature structure types. Each +fsDecl element may name one or more +basetypes from which it inherits feature +declarations and constraints (these are often called +supertypes). For instance, suppose that +fsDecl type="Basic" contains fDecl name="One" +and fDecl name="Two", and that fsDecl type="Derived" +baseTypes="Basic" contains just fDecl name="Three". +Then any instance of fs type="Derived" must include all +three features. This is because fsDecl type="Derived" +inherits the two feature declarations from fsDecl +type="Basic" when it specifies a base type of +Basic.

+

The following sample shows the overall structure of a complete +feature structure declaration: + + + Describes what this type of fs represents + + + + + + + + + + +

+ +

The attribute baseTypes gives the name of one or more +types from which this type inherits feature specifications and +constraints; if this type includes a feature specification with the +same name as one inherited from any of the types specified by this +attribute, or if more than one specification of the same name is +inherited, then the possible values of that feature is determined by +unification. Similarly, the set of constraints applicable is derived +by conjoining those specified explicitly within this element with +those implied by the baseTypes attribute. When no base type +is specified, no feature specification or constraint is inherited.

+

Although the present standard does provide for default feature values, +feature inheritance is defined to be monotonic. +

+The process of combining constraints may result in a contradiction, +for example if two specifications for the same feature specify +disjoint ranges of values, and at least one such specification is +mandatory. In such a case, there is no valid feature structure of the +type being defined.

+

+Every type specified by baseTypes must be a single word which +is a legal XML name; for example, they cannot include whitespace or +begin with digits. Multiple base types are separated with spaces, +e.g. fsDecl type="Sub" baseTypes="Super1 Super2".

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+
Feature Declarations +

Each feature is declared in an fDecl element whose +name attribute identifies the feature being declared; this +matches the name attribute of the f elements it +declares. + + +An fDecl has three parts: an optional +prose description (which should explain what the feature and its +values represent), an obligatory range specification (which declares +what values the feature is allowed to have), and an optional default +specification (which declares what default value should be supplied +when the named feature does not appear in an fs). +If, in a feature +structure, a feature: + is not optional (i.e., is obligatory), + has no value provided, or the value default is +provided (see ISO 24610-1, Subclause 5.10, Default Values, and + either has no default specified, or has conditional defaults, +none of the conditions on which is met, + +then the value of this feature in the feature structure's most +general valid extension is the most general value provided in its +vRange, in the case of a unit organization, or the +singleton set, bag, or list containing that element, in the case of a +complex organization. If the feature: + is optional, + has no value provided, or the value default is +provided, and + either has a default specified, or has conditional defaults, +one of the conditions on which is met, + +then this feature does have a value in the feature structure's most +general valid extension when it exists, namely the default value that +pertains. +

+

It is possible that a feature structure will not have a valid +extension because the default value that pertains to a feature is not +consistent with that feature's declared range. Additional tools +are required for the enforcement of such criteria. +

+ +

The following elements are used in feature system declarations: + + + + + + +

+

The logic for validating feature values and for matching the +conditions for supplying default values is based on the operation of +subsumption. Subsumption is a standard operation in +feature-structure-based formalisms. Informally, a feature structure +FS subsumes all feature structures that are at least as +informative as itself; that is, all feature structures that +specify all of the feature values that FS does with values that are +subsumed by the values that FS has, and that have all of the +re-entrancies (see ) that FS does. (; +see also and ) +A more formal definition is provided in ISO 24610-1:2006 .

+ + +

Following the spirit of the informal definition above, we can extend +subsumption in a straightforward way to cover alternation, negation, +special primitive values, and the use of attributes in the markup. +For instance, a vAlt containing the value v subsumes v. The negation +of a value v (represented by means of the +vNot element discussed in section ) +subsumes any value that is not v; for +example <vNot><numeric value='0'/></vNot> subsumes any +numeric value other than zero. + The value fs +type="X"/ subsumes any feature structure of type X, +even if it is not valid. +

+ +

As an example of feature declarations, consider the following extract +from Gazdar et al.'s Generalized Phrase Structure + Grammar. In the appendix to their book, they +propose a feature system for English of which this is just a sampling: +feature value range +INV {+, -} +CONJ {and, both, but, either, neither, nor, or, NIL} +COMP {for, that, whether, if, NIL} +AGR CAT +PFORM {to, by, for, ...} +Feature specification defaults +FSD 1: [-INV] +FSD 2: ~[CONJ] +FSD 9: [INF, +SUBJ] --> [COMP for]

+

The INV feature, which encodes whether or not a sentence is inverted, +allows only the values plus (+) and minus (-). If the feature is not +specified, then the default rule (FSD 1 above) says that a value of +minus is always assumed. The feature declaration for this feature would +be encoded as follows: + + inverted sentence + + + + + +

+

The value range is specified as an alternation (more precisely, an +exclusive disjunction), which can be represented by the +binary feature value. That is, +the value must be either true or false, but cannot be both or neither.

+

The CONJ feature indicates the surface form of the conjunction used +in a construction. The ~ in the default rule (see FSD 2 above) +represents negation. This means that by default the feature is not +applicable, in other words, no conjunction is taking place. Note that +CONJ not being present is distinct from CONJ being present but having the NIL value allowed in +the value range. In their analysis, NIL means that the phenomenon of +conjunction is taking place but there is no explicit conjunction in the +surface form of the sentence. The feature declaration for this feature +would be encoded as follows: + + surface form of the conjunction + + + + + + + + + + + + + + + +Note that the vDefault is not strictly necessary in this case, +since the binary value of false only serves to convey the +information that the feature has no other legitimate value. +

+ +

The COMP feature indicates the surface form of the complementizer +used in a construction. In value range, it is analogous to CONJ. +However, its default rule (see FSD 9 above) is conditional. It says +that if the verb form is infinitival (the VFORM feature is not +mentioned in the rule since it is the only feature that can take INF +as a value), and the construction has a subject, then a +for complement must be used. For instance, to +make John the subject of the infinitive in It is necessary +to go, a for complement must be +used; that is, It is necessary for John to go. +The feature declaration for this feature would be encoded as follows: + + + surface form of the complementizer + + + + + + + + + + + + + +

+

The AGR feature stores the features relevant to subject-verb +agreement. Gazdar et al. specify the range of this feature as CAT. +This means that the value is a category, which +is their term for a feature structure. This is actually too weak a +statement. Not just any feature structure is allowable here; it must be +a feature structure for agreement (which is defined in the complete +example at the end of the chapter to contain the features of person and +number). The following feature declaration encodes this constraint on +the value range: + + agreement for person and number + + +That is, the value must be a feature structure of type Agreement. The complete example at the end of this +chapter includes the fsDecl type="Agreement" which includes +fDecl name="PERS" and fDecl name="NUM".

+

The PFORM feature indicates the surface form of the preposition used +in a construction. Since PFORM is specified above as an open set, +string is used in the range specification below rather than +symbol. + + word form of a preposition + + +This example makes use of a negated value: <vNot><string/></vNot> +subsumes any string that is not the empty +string.

+

For the reduced feature structure that concludes section above and +identifies the value of some part of speech to be a common noun, it is possible to align +the concept of part of speech with its definition and persistent +identifier using the targetDatcat attribute, which connects the modeled XML object +with the appropriate locus in a reference taxonomy, as shown below: + + +part of speech (morphosyntactic category) + + + + + + + + + +The above example declares the feature POS as instantiating the corresponding concept defined in a reference +taxonomy or ontology, and defines the range of values of the feature at hand by listing the appropriate +alternatives, together with their external persistent identifiers.

+

Note that +the class model.featureVal includes all possible +single feature values, including feature structures, alternations +(vAlt) and complex collections (vColl).

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+
Feature Structure Constraints +

Ensuring the validity of feature structures may require much more +than simply specifying the range of allowed values for each feature. +There may be constraints on the co-occurrence of one feature value with +the value of another feature in the same feature structure or in an +embedded feature structure.

+

Such constraints on valid feature structures are expressed as a +series of conditional and biconditional tests in the +fsConstraints part of an fsDecl. A particular feature +structure is valid only if it meets all the constraints. The +cond element encodes the conventional if-then conditional of +boolean logic which succeeds when both the antecedent and consequent are +true, or whenever the antecedent is false. The bicond element +encodes the biconditional (if and only if) operation of boolean logic. +It succeeds only when the corresponding +if-then conditionals in both directions are true. In feature structure constraints the antecedent and +consequent are expressed as feature structures; they are considered true +if they subsume +(see section ) the feature structure in question, but in the +case of consequents, this truth is asserted rather than simply +tested. That is to say, a conditional is enforced by determining that +the antecedent does not (and will never) subsume the given feature +structure, or by determining that the antecedent does subsume the +given feature structure, and then unifying the consequent with it (the +result of which, if successful, will be subsumed by the consequent). +In practice, the enforcement of such constraints can result in +periods in which the truth of a constraint with respect to a given +feature structure is simply not known; in this case, the constraint +must be persistently monitored as the feature structure becomes more +informative until either its truth value is determined or computation +fails for some other reason.

+

The +following elements make up the fsConstraints part of an FSD: +

+

For an example of feature structure constraints, consider the +following feature co-occurrence restrictions +extracted from the feature system for English proposed by Gazdar, et al. (1985:246–247): +[FCR 1: [+INV] → [+AUX, FIN] +FCR 7: [BAR 0] ≡ [N] & [V] & [SUBCAT] +FCR 8: [BAR 1] → ~[SUBCAT]]

+

The first constraint says that if a construction is inverted, it must +also have an auxiliary and a finite verb form. That is, + + + + + + +

+

The second constraint says that if a construction has a BAR value of +zero (i.e., it is a sentence), then it must have a value for the +features N, V, and SUBCAT. By the same token, because it is a +biconditional, if it has values for N, V, and SUBCAT, it must have +BAR='0'. That is, + + + + + + + + +

+ +

The final constraint says that if a construction has a BAR value of 1 +(i.e., it is a phrase), then the SUBCAT feature should be absent (~). +This is not biconditional, since there are other instances under which +the SUBCAT feature is inappropriate. That is, + + + + +

+ +

+Note that cond and bicond use the empty tags +then and iff, respectively, to separate the antecedent +and consequent. These are primarily for the sake of enhancing human +readability.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+
A Complete Example +

To summarize this chapter, the complete FSD for the example that has +run through the chapter is reproduced below: + + + + + A sample FSD based on an extract from Gazdar + et al.'s GPSG feature system for English + + encoded by + Gary F. Simons + + + +

This sample was first encoded by Gary F. Simons (Summer +Institute of Linguistics, Dallas, TX) on January 28, 1991. +Revised April 8, 1993 to match the specification of FSDs +in version P2 of the TEI Guidelines. Revised again December 2004 to +be consistent with the feature structure representation standard +jointly developed with ISO TC37/SC4. +

+ +

This sample FSD does not describe a complete feature +system. It is based on extracts from the feature system +for English presented in the appendix (pages 245–247) of +Generalized Phrase Structure Grammar, by Gazdar, Klein, +Pullum, and Sag (Harvard University Press, 1985).

+ + + + + + Encodes a feature structure for the GPSG analysis + of English (after Gazdar, Klein, Pullum, and Sag) + + inverted sentence + + + + + + + + + + surface form of the conjunction + + + + + + + + + surface form of the complementizer + + + + + + + + + + + + agreement for person and number + + + + word form of a preposition + + + + + + + + + + + + + + + + + + + + + + + This type of feature structure encodes the features + for subject-verb agreement in English + + person (first, second, or third) + + + + + + number (singular or plural) + + + + +

+ +
+ + + +
+ Formal Definition and Implementation +

This elements discussed in this chapter constitute a module of the + TEI scheme which is formally defined as follows: + + Feature Structures + Feature structures + Structures de traits + 功能結構 (Feature Structures) + Strutture di configurazione (feature structures) + Estrutura das características + 素性構造モジュール + + + + The selection and combination of modules to form a TEI schema is + described in . + + + + + + + + + + + + + + + + + +

+
+
diff --git a/P5/Source/Guidelines/fr/FT-TablesFormulaeGraphics.xml b/P5/Source/Guidelines/fr/FT-TablesFormulaeGraphics.xml deleted file mode 120000 index 190989855a..0000000000 --- a/P5/Source/Guidelines/fr/FT-TablesFormulaeGraphics.xml +++ /dev/null @@ -1 +0,0 @@ -../en/./FT-TablesFormulaeGraphics.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/FT-TablesFormulaeGraphics.xml b/P5/Source/Guidelines/fr/FT-TablesFormulaeGraphics.xml new file mode 100644 index 0000000000..95d9bffe45 --- /dev/null +++ b/P5/Source/Guidelines/fr/FT-TablesFormulaeGraphics.xml @@ -0,0 +1,1105 @@ + + + + +
+ Tables, Formulæ, Graphics, and Notated Music +

Many documents, both historical and contemporary, include not only text, + but also graphics, artwork, and other images. Although some types of images + can be represented directly with markup, it is more common practice to + include such information by using a reference to an external entity + (typically a URL) encoded in a suitable graphical notation.

+

In addition to graphic images, documents often contain material presented + in graphical or tabular format. In such materials, details of layout and + presentation may also be of comparatively greater significance or complexity + than they are for running text. Indeed, it may often be difficult to make a + clear distinction between details relating purely to the rendition of + information and those relating to the information itself.

+

Documents may also contain mathematical formulæ or expressions in other + formulaic notations, for which no notation is defined in these + Guidelines.

+

Finally, documents may contain musical notation, embedded in a manner + similar to tables, graphs, and formulæ.

+

These areas (graphics, tabular material, and mathematical or other formulæ, + and music) have in common that they have received considerable attention + from many other standards bodies or similar professional groups. In part + because of this, they may frequently be most conveniently encoded and + processed using some notation not defined by these Guidelines. For these + reasons, and others, we consider tables, formulæ, graphics, and notated music + together in this chapter.

+

As with text markup in general, many incompatible formats have been + proposed for the representation of graphics, formulæ, and tables in + electronic form. Unfortunately, no single format as effective as XML in the + domain of text has yet emerged for their interchange, to some extent because + of the difficulty of representing the information these data formats convey + independently of the way it is rendered.

+

The module defined by this chapter defines special purpose + container elements that can be used to encapsulate + occurrences of such data within a TEI-conformant document in a portable way. + Specific recommendations for the encoding of tables are provided in section + , recommendations for mathematical or other formulæ + in section , and for the encoding of musical notation + in section . Specific recommendations for the encoding + of graphic figures may be found in section . The rest + of the chapter is devoted to general problems of encoding graphic + information.

+

There is at the time of writing no consensus on formats for graphical + images, and such formats vary in many ways. We therefore provide (in section + ) a brief discussion of the ways in which images + may be represented, and (in section ) a list of + formal names for those representations most popular at this time. Each one + includes a very brief description. These Guidelines recommend a few + particular representations as being the most widely supported and + understood.

+
+ Tables +

A table is the least graphic of the elements + discussed in this chapter. Almost any text structure can be presented as a + series of rows and columns: one might, for example, choose to show a + glossary or other form of list in tabular form, without necessarily + regarding it as a table. In such cases, the global rend + attribute is an appropriate way of indicating that some element is being + presented in tabular format; similarly, the global style attribute coud be used + to provide an appropriate display property in CSS. When tabular presentation is regarded as of less + intrinsic importance, it is correspondingly simpler to encode descriptive + or functional information about the contents of the table, for example to + identify one cell as containing a name and another as containing a date, + though the two methods may be combined.

+

When, however, particular elements are required to encode the tabular + arrangement itself, then one or other of the various table + schemas now available may be preferable. The schemas in + common use generally view a table as a special text element, made up of + row elements, themselves composed of + cells. + Table cells generally appear in row-major order, with the first row from + left to right, then the second row, and so on. Details of appearance such + as column widths, border lines, and alignment are generally encoded by + numerous attributes. Beyond this, however, such schemas differ greatly. + This section begins by describing a table schema of this kind; a brief + summary of some other widely available table schemas is also provided in + section .

+
+ TEI Tables +

For encoding tables of low to moderate complexity, these Guidelines + provide the following special purpose elements: + + + + +

+

The table element is defined as a member of the class model.inter; it may therefore appear both within + other components (such as paragraphs), or between them, provided that + the module defined in this chapter has been enabled, as described at the + beginning of this chapter.

+

It is to a large extent arbitrary whether a table should be regarded as + a series of rows or as a series of columns. For compatibility with + currently available systems, however, these Guidelines require a + row-by-row description of a table. It is also possible to describe a + table simply as a series of cells; this may be useful for tabular + material which is not presented as a simple matrix.

+

The attributes rows and cols may be used to + indicate the size of a table, or to indicate that a particular cell or + row of a table spans more than one row or column. For both tables and + cells, rows and columns are always given in top-to-bottom, left-to-right + order, although formatting properties such as those provided by CSS may + be used to specify that they should be displayed differently. These + Guidelines do not require that the size of a table be specified; for + most formatting and many other applications, it will be necessary to + process the whole table in two passes in any case.

+

Where cells span more than one column or row, the encoder must + determine whether this is a purely presentational effect (in which case + the rend attribute may be more appropriate), whether the part + of the table affected would be better treated as a nested table, or + whether to use the spanning attributes listed above.

+

The role attribute may be used to categorize a single cell, + or set a default for all the cells in a given row. The present + Guidelines distinguish the roles of label and + data only, but the encoder may define other roles, such + as derived, numeric, etc., as appropriate.

+

These three attributes are provided by the attribute class + att.tableDecoration of which both + cell and row are members; see further .

+

The following simple example demonstrates how the data presented as a + labelled list in section might be represented by + an encoder wishing to preserve its original appearance as a table: + + Report of the conduct and progress of Ernest + Pontifex. Upper Vth form — half term ending Midsummer 1851 + + Classics + Idle listless and unimproving + + + Mathematics + ditto + + + Divinity + ditto + + + Conduct in house + Orderly + + + General conduct + Not satisfactory, on account of his great unpunctuality and + inattention to duties + +
+ +

+

Note that this encoding makes no attempt to represent the full + significance of the ditto cells above; these might be regarded as + simple links between the cells containing them and that to which they + refer, or as virtual copies of it. For ways of representing either + interpretation, see chapter .

+

The following example demonstrates how a simple statistical table may + be represented using this scheme: + + Poor Man's Lodgings in Norfolk (Mayhew, 1843) + + + Dossing Cribs or Lodging Houses + Beds + Needys or Nightly Lodgers + + + Bury St Edmund's + 5 + 8 + 128 + + + Thetford + 3 + 6 + 36 + + + Attleboro' + 3 + 5 + 20 + + + Wymondham + 1 + 11 + 22 + +
+

+

Note the use of a blank cell in the first row to ensure that the column + labels are correctly aligned with the data. Again, this encoding does + not explicitly represent the alignment between column and row labels and + the data to which they apply. Where the primary emphasis of an encoding + is on the semantic content of a table, a more explicit mechanism for the + representation of structured information such as that provided by the + feature structure mechanism described in chapter may + be preferred. Alternatively, the general purpose linkage and alignment + mechanisms described in chapter may also be applied + to individual cells of a table.

+

The content of a table cell need not be simply character data. It may + also contain any sequence of the phrase-level elements described in + chapter , thus allowing for the encoding of + potentially more useful semantic information, as in the following + example, where the fact that one cell contains a number and the other + contains a place name has been explicitly recorded: + + US State populations, 1990 + + Wyoming + + + 453,588 + + + Alaska + + + 550,043 + + + Montana + + + 799,065 + + + Rhode Island + + + 1,003,464 + +
+

+

The use of semantically marked elements within a cell enables + the encoder to convey something about the nature and significance of the + information, rather than merely suggesting how to display it in rows and + columns.

+

Alternatively, the role attribute might be used to convey + such information: + + US State populations, 1990 + Wyoming + 453,588 + Alaska + 550,043 + Montana + 799,065 + Rhode Island + 1,003,464 +
+

+

The content of table elements is not limited to head and + row. Milestone elements such as cb and lb + allow breaks to be signalled inside tables; figure provides an + option for including data which is not amenable to normal row and cell + analysis; and other elements such as epigraph and + trailer provide options for including text which is clearly + part of the table, but outside the actual tabular layout. This example + shows the use of trailer: + + The Table of Battallions, reduced out of the grand square of + men. + + 1 + 2 + 3 + 4 + + + + 841 + 3 + 289 289 256 + 7 + + The end of the Table of Battallions reduced out of the + battels of g. and squares of men: vpon the right side of euery + leafe. +
+

+ + + + + +
+
+ Other Table Schemas +

Many authoring systems include built-in support for their own or for + public table schemas. These provide an enhanced user interface and good + formatting capabilities, but are often product-specific, despite their + use of a XML markup language.

+

The DTD developed by the Association of American Publishers (AAP) and + standardized in ANSI Z39.59 provided a very simple encoding for + correspondingly simple tables. This has been further developed, together + with the table DTD documented in ISO Technical Report 9537, and now + forms part of ISO 12083. The TEI table model described above has + functionality very similar to that defined by ISO 12083.

+

For more complex tables, the most effective publicly-available DTD is + probably that developed by the US Department of Defense CALS project. + This supports vertical and horizontal spanning and various kinds of text + rotation and justification within cells and is also directly supported + by a number of existing XML software systems.

+

The CALS table model is much too complex to describe fully here; for + historical background see ; for + more recent simplifications of it and current implementations see . As with + any other XML vocabulary, the XML version of the CALS model may readily + be included in a TEI schema, using the techniques described in .

+ + +

The XHTML table model () is based on the HTML + table model (). Both models support arrangement of + arbitrary data into rows and columns of cells. Table rows and columns + may be grouped to convey additional structural information and may be + rendered by user agents in ways that emphasize this structure. Support + for incremental rendering of tables and for rendering on + non-visual user agents + + is also available. Special elements and attributes are provided to + associate metadata with tables. They indicate the table's purpose, or + are for the benefit of people using speech or Braille-based user agents. + Tables are not recommended for use purely as a means to lay out document + content, as this leads to many accessibility problems (see further ). + Stylesheets provide a far more effective means of controlling layout and + other visual characteristics in both HTML and XML documents.

+
+
+
+ Formulæ and Mathematical Expressions +

Mathematical and chemical formulæ pose problems similar to those posed by + tables in that rendition may be of great significance and hard to + disentangle from content. They also require access to a wide range of + special characters, for most of which standard entity names already exist + in the documented ISO entity sets (see further chapters and ).

+

Formulæ and tables are also similar in that well-researched and detailed + DTD fragments have already been developed for them independently of the + TEI. They differ in that (for mathematics at least) there also exists a + richly detailed text-based but non-XML notation which is very widely used: + this is the TeX system, and the sets of descriptive macros developed for + it such as LaTeX, AMS-TeX, and AMS-LaTeX.

+

The AAP and ISO standards mentioned in section + above both provide DTDs for equations as well as for tables, which now + form part of ISO 12083. The European Mathematical Trust, an organization + set up specifically to enhance research support for European + mathematicians, has also defined a general purpose mathematical DTD known + as EuroMath (), for which it provides both software and services.

+

Most if not all of the functionality provided by these DTDs can now be + found in the OpenMath and MathML XML-based systems briefly described + below.

+

As with tables, in all the XML solutions a tension exists between the + need to encode the way a formula is written (its appearance) and the need + to represent its semantics. If the object of the encoding is purely to act + as an interchange format among different formatting programs, then there + is no need to represent the mathematical meaning of an expression. If + however the object is to use the encoding as input to an algebraic + manipulation system (such as Mathematica or Maple) or a database system, + clearly simply representing superscripts and subscripts will be + inadequate.

+

The formula element provided by these Guidelines makes no + attempt to represent the internal structure of formulæ. + + +

+

By default, a formula is assumed to contain character data which + is not validated in any way. The notation used may however be named, using + the notation attribute provided by the + att.notated class. + $e=mc^2$ + The character data must still be well-formed, of course, which means that + < and & must be + escaped with entity references or numeric character references, e.g. + $\matrix{0 &amp; + 1\cr&lt;0&amp;>1}$ +

+

Alternatively, if more detailed markup is desired, the content of the formula element may be redefined + to include elements defined by some other XML vocabulary, such as that of ISO + 12083, or to use elements from the OpenMath or + MathML + schemas. +

+

When the content of a formula element is not expressed in XML + the notation used should always be specified using the notation + attribute as above, and in the following longer example: +

Achilles runs ten times faster than the tortoise and gives the + animal a headstart of ten meters. Achilles runs those ten meters, the + tortoise one; Achilles runs that meter, the tortoise runs a decimeter; + Achilles runs that decimeter, the tortoise runs a centimeter; Achilles + runs that centimeter, the tortoise, a millimeter; Fleet-footed + Achilles, the millimeter, the tortoise, a tenth of a millimeter, and + so on to infinity, without the tortoise ever being overtaken. . . Such + is the customary version. The problem does not change, as + you can see; but I would like to know the name of the poet who + provided it with a hero and a tortoise. To those magical competitors + and to the series $$ {1 \over 10} + {1 \over + 100} + {1 \over 1000} + {1 \over 10,\!000} + \dots $$ the + argument owes its fame.

+ The notation attribute supplies the name of a notation + (TeX), which is expected to be identified somewhere in document + metadata.

+

Mathematical Markup Language (MathML) () is a + vocabulary for describing mathematical notation, capturing both its + structure and content. + + It provides two types of markup: Presentation Markup, which captures the + notational structure of an expression and could be seen as the + TeX for the Web and Content Markup, which captures + the mathematical structure of an expression. Most of its content + elements correspond with the range of operators, relations, and named + functions typically found at the high-school level of mathematics. The + tortoise example given above in TeX can be re-expressed in MathML as + + + + 1 + + + 10 + + + + + + + 1 + + + 100 + + + + + + + 1 + + + 1000 + + + + + + + 1 + + + 10000 + + + + + … + +

+

MathML 2.0 provides support for a Semantic Math-Web, + XML namespaces, and other current XML standards, such as XML DOM, OMG IDL, + ECMAScript, and Java. It also provides a modularized version of the MathML + DTD so that MathML fragments embedded in XHTML 1.1 + documents can be correctly validated.

+

The OpenMath () project is coordinated by the OpenMath Society () and funded by the European + Commission under the Esprit Multimedia Standards Initiative that commenced + in September 1997. It is likely to become a key standard for communicating + semantically rich representations of mathematical objects both on and off + the Web in a platform-independent manner.

+

The OpenMath Standard () consists + of specifications for + OpenMath objects, representing the structure of formulæ (); + Content Dictionaries, providing semantic context (); + Encodings, both binary () and XML (). +

+

OpenMath and MathML have certain common aspects. They both use prefix + operators, both are XML-based and they both construct their objects by + applying certain rules recursively. Such similarities facilitate mapping + between the two standards. There are also some key differences between + MathML and OpenMath. OpenMath does not provide support for presentation of + mathematical objects and its scope of semantically-oriented elements is + much broader that of MathML, with the expressive power to cover virtually + all areas of computational mathematics. In fact, a particular set of + Content Dictionaries, the MathML CD Group, covers the + same areas of mathematics as the Content Markup elements of MathML + 2.0.

+

Finally, OMDoc () is an extension of the + OpenMath standard that supplies markup for structures such as axioms, + theorems, proofs, definitions, texts (mixing formal content with + mathematical text).

+

In-line versus block placement for an equation can be distinguished if + desired, via the global rend attribute. The global n + and xml:id attributes may also be used to label or identify the + formula, as in the following example: +

The volume of a sphere + is given by the formula: + + V + = + + + 4 + + + 3 + + + π + + + r + + + 3 + + + + which is readily calculated.

+

As we have seen in equation , ...

+

+ + + +
+
+ Notated Music in Written Text +

Music, like many other art forms, is often mentioned, discussed and + described in writings of various kinds. This applies to both historical + and contemporary documents, even though methods of notating music have + changed considerably in western history. In most cases, music notation + enters the text flow in a way similar to figures, images, or graphs. On + other occasions, elements of music notation are treated as inline + characters in running text.

+

notatedMusic provides a way to signal the presence of music + notation in text, but defer to other representations, which are not + covered by the TEI guidelines, to describe the music notation itself. In + fact several commercial, academic, and standard bodies have developed + digital representations of music notation. Given the topic's + complexity, these representations often focus on different aspects and + adopt different methodologies. Therefore, notatedMusic only + defines a container element to encode the occurrence of music notation and + allows linking to the data format preferred by the encoder. (Note: + notatedMusic is not the same as musicNotation, a + metadata element, which is used to describe musical notation that appears + in a manuscript. See .)

+

The following elements can be used for encoding music notation in text: + + + + + + +

+ + + groups elements representing or + containing music notation. + + can be used to indicate the location of a + representation of the music notation. + mimeType supplies the MIME type of the data format, + when available. + + + + can be used to give a prose description of + the notated music. + + can be used to indicate the location of + a graphical representation of the music notation. + + provides encoded binary data which + constitutes another representation of the music notation (e.g. + audio). + +

The notatedMusic element may contain a textual description and + pointers to various representations of the music notation in different + media. An external representation of the notated music is specified using + the ptr element, whose target attribute provides its + electronically-accessible location. The attribute mimeType + supplies the MIME type of the data format when available. For example:

+ + + +

A textual description of the notation can be provided within the + desc element; alternatively, a label may be supplied. + For example:

+ + + First bar of Chopin's Scherzo No.3 Op.39 + +

It is possible to link to any kind of music notation data format. + However, when a MIME type is not available, it is recommended that the + format be specified in the description. See the following examples.

+

MIME type available:

+ + + First bar of Chopin's Scherzo No.3 Op.39. Encoded in + MusicXML. + +

MIME type not available:

+ + + First bar of Chopin's Scherzo No.3 Op.39. Encoded in + Lilypond. + +

Application format:

+ + + First bar of Chopin's Scherzo No.3 Op.39. MuseScore Notation + Software format. + +

It is possible to specify the location of digital objects representing + the notated music in other media such as images or audio-visual files. The + interpretation of the correspondence between the notated music and these + digital objects is not encoded explicitly. We recommend the use of + graphic and binaryObject mainly as a fallback + mechanism when the notated music format is not displayable by the + application using the encoding. The alignment of encoded notated music, + images carrying the notation, and audio files is a complex matter for + which we refer the reader to other formats and specifications such as MPEG-SMR.

+ + + + First bar of Chopin's Scherzo No.3 Op.39 + + +

It is also recommended, when useful, to embed XML-based music notation + formats, such as the Music Encoding Initiative + format as content of notatedMusic. This must be done by means of customization.

+ +

In modern printing, music notation positioned between blocks of text for + illustrative purposes is usually referred to as a figure or + example. In this cases, we recommend the inclusion of + notatedMusic in figure in order to encode possible + captions and headers. For example:

+
+ Example from: + Prout, E. (1899). The + orchestra. + + +
+
+

We now give some examples, from the works of the great masters, of + some of the most frequently used bowings.

+
+ SCHUBERT: Symphony in B minor. + + + +
+
+ + + + +
+
+ Specific Elements for Graphic Images +

The following special purpose elements are used to indicate the presence + of graphic images within a document: + + + + + +

+

The graphic and binaryObject elements form part of the + common core module, and are discussed in section .

+

The figure element is used to contain images, captions, and + textual descriptions of the pictures. The images themselves are specified + using the graphic element, whose url attribute + provides the location of an image. For example: +

+ +
+

+

Three kinds of content may be supplied inside a figure element: + the element head may be used to transcribe (or supply) a + descriptive heading or title for the graphic itself as in this example: +

+ + The View from the Bridge +
+

+

Figures are often accompanied not only by a title or heading (a caption), + but by a paragraph or so of commentary (a legend) following the caption. + One or more p or ab elements + may be used to transcribe any + commentary on the figure in the source: +

+ + Above: +

The drawing room of the Pullman house, the white and gold saloon + where the magnate delighted in giving receptions for several hundred + people.

+ The figure shows an elaborately decorated room, at least + twenty-five feet side to side and fifty feet long, with ornate + mouldings and Corinthian columns on the walls, overstuffed armchairs + and loveseats arranged in several conversational groupings, and two + large chandeliers. +
+ + Here, + the figure contains a heading Above which is complemented by a + paragraph of description The drawing room ... several hundred + people. Both of these are transcribed from the source, while the + description is provided by the encoder, for use by applications which + cannot display the graphic directly. In documents created in electronic + form with the needs of print-handicapped readers in mind, the + figDesc element may be provided by the author rather than a + subsequent encoder. +
+ + Figure One: The View from the Bridge + A Whistleresque view showing four or five sailing boats in + the foreground, and a series of buoys strung out between + them. +
+

+

Where the graphic itself contains large amounts of text, perhaps with a + complex structure, and perhaps difficult to distinguish from the graphic, + the encoder should choose whether to regard the graphic as containing the + text (in which case, a nested floatingText element may be + included within the figure element) or to regard the enclosed + text as being a separate division of the text element in which + the graphic appears. In this latter case, an appropriate div or + div1 (etc.) element may be used for the text represented within + the graphic, and the figure element embedded within it. The + choice will depend to a large degree on the encoder's understanding of the + relationship between the graphic and the surrounding text.

+

A figure which is internally divided, or contains sub-figures, may be + encoded with nested figure elements, as in the following example. + +

+
+ + Parallel +
+
+ + Perspective +
+ The two canonical view volumes, for the (a) + parallel and (b) perspective projections. Note that -z is to the + right. +
+ + +

+

Like any other element in the TEI scheme, figures may be given + identifiers so that they can be aligned with other elements, and linked to + or from them, as described in chapter . Some common + examples are discussed briefly here; full information is provided in that + chapter.

+

It is often desirable to maintain two versions of an image in an + electronic file: one a low resolution or thumbnail + version which, when selected by the user, causes the other, high + resolution, version to be accessed. In TEI terms, the thumbnail image acts + as a reference to the other. Supposing that a thumbnail + version of the figure discussed above is available as fig1th.png, we might embed a reference to the image using the + simple ref element discussed in section : + Click + here for enlightenment +

+ +
+ +

+

Another common requirement is to associate part or the whole of an image + with a textual element not necessarily contiguous to it in the text; this + is sometimes known as a callout. When the module for + transcription is included in a schema, specific attributes for parts of a + text and parts (or all) of a digital image are available; these are + discussed in . In addition, chapter may be consulted for other mechanisms available for this + purpose.

+

The following example assumes that we wish to associate one portion of + the image held as fig1 with chapter two of some text, and another + portion of it with chapter three. The application may be thought of as a + hypertext browser in which the user selects from a graphic image which + part of a text to read next, but the mechanism is independent of this + particular application.

+

The first requirement is some way of identifying and hence pointing to + sub-parts of a graphic image. This may be done by pointing into an XML + graphic representation, for example an SVG file. Thus + + +

+

These ptr elements identify two areas within the image + Fig1 by pointing at elements inside the XML file Fig1.svg, which contains the following. + + + + + + + + + + +

+

The next requirement is some way of identifying the parts of the document + to which a link is to be made. The most obvious way of doing this is to + use the global xml:id attribute: + + + + + + +

+

Now, all that is needed to linking these areas to the relevant chapters + is a linkGrp element, as described in section : + + + + +

+

In this example, the SVG representation of the graphic is stored + externally to the TEI document and linked by means of a pointer. It is + also possible to embed the SVG representation directly within the TEI by + extending the content model of the figure element to permit an + element svg from the SVG namespace. Like other + customizations of the TEI scheme, this is carried out using the techniques + documented in section ; further examples are provided + in chapter .

+ + + + + +
+
+ Overview of Basic Graphics Concepts +

The first major distinction in graphic representation is that between + raster graphics and vector graphics. A raster image is a list + of points, or dots. Scanners, fax machines, and other simple devices easily + produce digital raster images, and such images are therefore quite common. + A vector image, in contrast, is a list of geometrical + objects, such as lines, circles, arcs, or even cubes. These are much more + difficult to produce, and so are mainly encountered as the output of + sophisticated systems such as architectural and engineering CAD + programs.

+

Raster images are difficult to modify because by definition they only + encode single points: a line, for example, cannot grow or shrink as such, + since it is not identified as such. Only its component parts are + identified, and only they can be manipulated. Therefore the resolution or + dot-size of a raster image is important, which is not the case with vector + images. It is also far more difficult to convert raster images to vector + images than to perform the opposite conversion. Raster images generally + require more storage space than vector images, and a wide variety of + methods exists for compressing them; the variation in these methods leads + to corresponding variations in representations for storage and + transmission of raster images.

+

Motion video usually consists of a long series of raster images. Data + compression is even more effective on video than on single raster images + (mainly owing to redundancy which arises from the usual similarity of + adjacent frames). Notations for representing full-motion video are hotly + debated at this time, and any user of these Guidelines would do well to + obtain up-to-date expert advice before undertaking a project using + them.

+

The compression methods used with any of these image types may be + lossy or lossless. Methods for + lossy compression save space by discarding a small portion + of the image's detail, such as fine distinctions of shading. When + decompressed, therefore, such an image will be only a close approximation + of the original. In contrast, lossless compression guarantees + that the exact uncompressed image will be reproducible from the compressed + form: only truly redundant information is removed. In general, therefore, + lossless compression does not save quite so much space as lossy + compression, though it does guarantee fidelity to the original + uncompressed image.

+

Raster images may be characterized by their resolution, + which is the number of dots per inch used to represent the image. Doubling + the resolution will give a more precise image, but also quadruple the + storage requirement (before compression), and affect processing time for + any operations to be performed, such as displaying an image for a reader. + Motion video also has resolution in time: the number of frames to be shown + per second. Encoders should consider carefully what resolution(s) and + frame rate(s) to use for particular applications; these Guidelines express + no recommendation in this matter, save the universal ones of consistency + and documentation.

+

Within any image, it is typical to refer to locations via Cartesian + coordinate axes: values for x, y, and sometimes z and/or time. However, + graphic notations vary in whether coordinates count from left-to-right and + top-to-bottom, or another way. They also vary in whether coordinates are + considered real (inches, millimeters, and so on), or virtual (dots). These + Guidelines do not recommend any of these methods over another, but all + decisions made should be applied consistently, and documented in the + encodingDesc section of the TEI header.Since no special purpose element is provided for this purpose by the + current version of these Guidelines, such information should be provided + as one or more distinct paragraphs at the end of the + encodingDesc element described in section .

+

Methods of aligning images and text are discussed in .

+

The chromatic values of an image may be rendered in many different ways. + In monochrome images every displayed point is either black or white. In + grayscale images, each point is rendered in some shade of + gray, the number of shades varying from system to system. In true + polychrome images, points are rendered in different hues, again with + varying limitations affecting the number of distinct shades and the means + by which they are displayed.

+
+
+ Graphic Image Formats +

As noted above, there exists a wide variety of different graphics + formats, and the following list is in no way exhaustive. Moreover, + inclusion of any format in this list should not be taken as indicating + endorsement by the TEI of this format or any products associated with it. + Some of the formats listed here are proprietary to a greater or lesser + extent and cannot therefore be regarded as standards in any meaningful + sense. They are however widely used by many different vendors.

+

The following formats are widely used at the present time, and likely to + remain supported by more than one vendor's software: + BMP: Microsoft bitmap format + CGM: Computer Graphics Metafile + GIF: Graphics Interchange Format + JPEG: Joint Photographic Expert Group + PBM: Portable Bit Map + PCX: IBM PC raster format + PICT: Macintosh drawing format + PNG: Portable Network Graphics format + Photo-CD: Kodak Photo Compact Disk format + QuickTime: Apple real-time image system + SMIL: Synchronized Multimedia Integration Language format + SVG: Scalable Vector Graphics format + TIFF: Tagged Image File Format +

+

Brief descriptions of all the above are given below. Where possible, + current addresses or other contact information are shown for the + originator of each format. Many formal standards, especially those + promulgated by ISO and many related national organizations (ANSI, DIN, + BSI, and many more), are available from those national organizations. + Addresses may be found in any standard organizational directory for the + country in question.

+
+ Vector Graphic Formats + + + This vector graphics format is specified by an ISO standard, ISO + 8632:1987, amended in 1990. It defines binary, character, and + plain-text encodings; the non-binary forms are safer for blind + interchange, especially over networks. Documentation on CGM is + available from ISO and from its member national bodies such as AFNOR, + ANSI, BSI, DIN, JIS, etc. + + SVG is a language for describing two-dimensional vector and mixed + vector or raster graphics in XML. It is defined by the Scalable Vector + Graphics (SVG) 1.0 Specification, W3C Recommendation, 04 September + 2001, and is available at . + + This format is universally supported on Macintosh™ systems, + and readable by a limited range of software for other systems. + Documentation is available from Apple Computer Company, Cupertino, + California USA. + +
+
+ Raster Graphic Formats + + + PNG is a non-proprietary raster format currently widely available. + It provides an extensible file format for the lossless, portable, + well-compressed storage of raster images. Indexed-color, grayscale, + and truecolor images are supported, plus an optional alpha channel. + Sample depths range from 1 to 16 bits. It is defined by IETF RFC 2083, + March 1997. + + Currently the most widely supported raster image format, + especially for black and white images, TIFF is also one of the few + formats commonly supported on more than one operating system. The + drawback to TIFF is that it actually is a wrapper for several formats, + and some TIFF-supporting software does not support all variants. TIFF + files may use LZW, CCITT Group 4, or PackBits compression methods, or + may use no compression at all. Also, TIFF files may be monochrome, + grayscale, or polychromatic. All such options should be specified in + prose at the end of the encodingDesc section of the TEI + header for any document including TIFF images. TIFF is owned by Aldus + Corporation. Documentation on TIFF is available from them at Craigcook + Castle, Craigcook Road, Edinburgh EH4 3UH, Scotland, or 411 First + Avenue South, Seattle, Washington 98104 USA. + + Raster images are widely available in this form, which was created + by CompuServe Information Services, but has by now been implemented + for many other systems as well. Documentation on GIF is copyright by, + and is available from, CompuServe Incorporated, Graphics Technology + Department, 5000 Arlington Center Boulevard, Columbus, Ohio 43220 USA. + + PBM files are easy to process, eschewing all compression in favor + of transparency of file format. PBM files can, of course, be + compressed by generic file-compression tools for storage and transfer. + Public domain software exists which will convert many other formats to + and from PBM. Documentation on PBM is copyright by Jeff Poskanzer, and + is available widely on the Internet. + + This format is used by most IBM PC paint programs, and supports + both monochrome and polychromatic images. Documentation is available + from ZSoft Corporation, Technical Support Department, ATTN: Technical + Reference Manual, 450 Franklin Rd. Suite 100, Marietta, GA 30067 USA. + + This format is the standard raster format for computer using + Microsoft Windows™ or Presentation Manager™. Documentation is + available from Microsoft Corporation. + +
+
+ Photographic and Motion Video Formats + + + This standard is sponsored by CCITT and by ISO. It is ISO/IEC + Draft International Standard 10918-1, and CCITT T.81. It handles + monochrome and polychromatic images with a variety of compression + techniques. JPEG per se, like CCITT Group IV, must be encapsulated + before transmission; this can be done via TIFF, or via the JPEG File + Interchange Format (JFIF), as commonly done for Internet delivery. + + QuickTime is a proprietary method introduced by Apple Computer + Company to synchronize the display of various data. The data can + include frames of video, sound, lighting control mechanisms, and other + things. Viewers for QuickTime productions are available for Apple and + other computers. Further information is available from Apple Computer + Incorporated, 10201 North de Anza Boulevard MS 23AQ, Cupertino, + California 95014 USA. + + This format was introduced by Kodak for rasterizing photographs + and storing them on CD-ROMs (about one hundred 35mm file images fit on + one disk), for display on televisions or CD-I systems. Information on + Photo-CD is available from Kodak Limited, Research and Development, + Headstone Drive, Harrow, Middlesex HA1 4TY, UK. + + SMIL is a W3C Recommendation which supports the integration of + independent multimedia objects into a synchronized multimedia + presentation. It provides multimedia authors with easily-defined basic + timing relationships, fine-tuned synchronization, spatial layout, + direct inclusion of non-text and non-image media objects, hyperlink + support for time-based media, and adaptiveness to varying user and + system characteristics. SMIL 1.0 () became a W3C + Recommendation on June 15, 1998, and was further developed in SMIL + 2.0. SMIL 2.0 adds native support for transitions, animation, + event-based interaction, extended layout facilities, and more + sophisticated timing and synchronization primitives to the SMIL 1.0 + language. It also allows reuse of SMIL syntax and semantics in other + XML-based languages, in particular those who need to represent timing + and synchronization. For example, SMIL 2.0 components are used for + integrating timing into XHTML Document Types and into SVG. SMIL 2.0 + also provides recommendations for Document Types based on SMIL 2.0 + Modules (). One such Document Type is the SMIL 2.0 Language Profile (). It contains support for all of the major SMIL 2.0 features + including animation, content control, layout, linking, media object, + meta-information, structure, timing, and transition effects and is + designed for Web clients that support direct playback from SMIL 2.0 + markup. SMIL 2.0 () became a + W3C Recommendation on August 7, 2001, becoming the first vocabulary to + provide XML Schema support and to have reached such status. + +

As noted above, the reader will encounter many, many other graphics + formats.

+
+
+
+ Module for Tables, Formulæ, Notated Music, and Graphics +

The module described in this chapter provides the following features: + + Tables, Formulæ, Notated Music, Figures + Tables, formulæ, notated music, and figures + Tableaux, formules et graphiques + 表格、方程式與圖表 + Tabelle, formule e figure + Tabelas, fórmulas, e figuras + 図表式モジュール + + The selection and combination of modules to form a TEI + schema is described in . + + + + +

+
+
\ No newline at end of file diff --git a/P5/Source/Guidelines/fr/GD-GraphsNetworksTrees.xml b/P5/Source/Guidelines/fr/GD-GraphsNetworksTrees.xml deleted file mode 120000 index e57b3b09fc..0000000000 --- a/P5/Source/Guidelines/fr/GD-GraphsNetworksTrees.xml +++ /dev/null @@ -1 +0,0 @@ -../en/./GD-GraphsNetworksTrees.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/GD-GraphsNetworksTrees.xml b/P5/Source/Guidelines/fr/GD-GraphsNetworksTrees.xml new file mode 100644 index 0000000000..b7d952b394 --- /dev/null +++ b/P5/Source/Guidelines/fr/GD-GraphsNetworksTrees.xml @@ -0,0 +1,1499 @@ + + + + +
Graphs, Networks, and Trees +

Graphical representations are widely used for displaying relations +among informational units because they help readers to visualize those +relations and hence to understand them better. Two general types of +graphical representations may be distinguished. + + Graphs, in the strictly mathematical sense, consist +of points, often called nodes or +vertices, and connections among them, called +arcs, or under certain conditions, +edges. Among the various types of graphs are +networks and trees. Graphs +generally and networks in particular are dealt with +directly below. Trees are dealt with separately in +sections and +.The treatment here is largely based on the +characterizations of graph types in +Charts, which typically plot data in two or more +dimensions, including plots with orthogonal or radial axes, bar charts, +pie charts, and the like. These can be described using the elements +defined in the module for figures and graphics; see +chapter . +

+ +

Among the types of qualitative relations often represented by graphs +are organizational hierarchies, flow charts, genealogies, semantic +networks, transition networks, grammatical relations, tournament +schedules, seating plans, and directions to people's houses. In +developing recommendations for the encoding of graphs of various types, +we have relied on their formal mathematical definitions and on the most +common conventions for representing them visually. However, it must be +emphasized that these recommendations do not provide for the full range +of possible graphical representations, and deal only partially with +questions of design, layout, and placement.

+
Graphs and Digraphs +

Broadly speaking, graphs can be divided into two types: +undirected and directed. An undirected graph +is a set of nodes (or vertices) together with +a set of pairs of those vertices, called arcs or +edges. Each node in an arc of an undirected graph is said +to be incident with that arc, and the two vertices (nodes) which +make up an arc are said to be adjacent. An directed graph +is like an undirected graph except that the arcs are ordered +pairs of nodes. In the case of directed graphs, the term +edge is not used; moreover, each arc in a directed graph +is said to be adjacent from the node from which the arc +emanates, and adjacent to the node to which the arc is +directed. We use the element graph to encode graphs as a +whole, node to encode nodes or vertices, and arc to +encode arcs or edges; arcs can also be encoded by attributes on the +node element. These elements have the following descriptions +and attributes: + + + +

+

Before proceeding, some additional terminology may be helpful. We +define a path in a graph as a sequence of nodes n1, ..., nk +such that there is an arc from each ni to ni+1 in the sequence. A +cyclic path, or cycle is a path leading from a +particular node back to itself. A graph that contains at least one +cycle is said to be cyclic; otherwise it is +acyclic. We say, finally, that a graph is +connected if there is a path from some node to every other +node in the graph; any graph that is not connected is said to be +disconnected.

+

Here is an example of an undirected, cyclic disconnected graph, in +which the nodes are annotated with three-letter codes for airports, and +the arcs connecting the nodes are represented by horizontal and vertical +lines, with 90 degree bends used simply to avoid having to draw diagonal +lines.

+ + + + + +

+ +

Next is a markup of the graph, using arc elements to encode +the arcs. + + + + + + + + + + + + + + + + + + + + + +

+

+The first child element of graph may be a label to record a +label for the graph; similarly, the label child of each +node element records the labels of that node. The +order and size attributes on the graph +element record the number of nodes and number of arcs in the graph +respectively; these values are optional (since they can be computed +from the rest of the graph), but if they are supplied, they must be +consistent with the rest of the encoding. They can thus be used to +help check that the graph has been encoded and transmitted correctly. +The degree attribute on the node elements record +the number of arcs that are incident with that node. It is optional +(because redundant), but can be used to help in validity checking: if +a value is given, it must be consistent with the rest of the +information in the graph. Finally, the from and +to attributes on the arc elements provide pointers +to the nodes connected by those arcs. Since the graph is undirected, +no directionality is implied by the use of the from and +to attributes; the values of these attributes could be +interchanged in each arc without changing the graph.

+

The adj, adjFrom, and adjTo +attributes of the node element provide an alternative method of +representing unlabeled arcs, their values being pointers to the nodes +which are adjacent to or from that node. The adj attribute +is to be used for undirected graphs, and the adjFrom and +adjTo attributes for directed graphs. It is a semantic error +for the directed adjacency attributes to be used in an undirected graph, +and vice versa. Here is a markup of the preceding graph, using the +adj attribute to represent the arcs. + + + + + + + + + + + + + + + + + +

+

Note that each arc is represented twice in this encoding of the +graph. For example, the existence of the arc from LAX to LVG can be +inferred from each of the first two node elements in the graph. +This redundancy, however, is not required: it suffices to describe an +arc in any one of the three places it can be described (either adjacent +node, or in a separate arc element). Here is a less redundant +representation of the same graph. + + + + + + + + + + + + + + + + + +

+

Although in many cases the arc element is redundant (since +arcs can be described using the adjacency attributes of their adjacent +nodes), it has nevertheless been included in this module, in order to +allow the convenient specification of identifiers, display or +rendition information, and labels for each arc (using the attributes +xml:id, rend, and a child label element).

+

Next, let us modify the preceding graph by adding directionality to +the arcs. Specifically, we now think of the arcs as specifying selected +routes from one airport to another, as indicated by the direction of the +arrowheads in the following diagram.

+

+

Here is an encoding of this graph, using the arc element to +designate the arcs. + + + + + + + + + + + + + + + + + + + + + + + +The attributes inDegree and outDegree indicate +the number of nodes which are adjacent to and from the node concerned +respectively.

+ +

Here is another encoding of the graph, using the adjTo and +adjFrom attributes on nodes to designate the arcs. + + + + + + + + + + + + + + + + + +

+

If we wish to label the arcs, say with flight numbers, then +arc elements must be used to hold the label +elements, as in the following example. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Transition Networks +

For encoding transition networks and other kinds of directed graphs +in which distinctions among types of nodes must be made, the +type attribute is provided for node elements. In +the following example, the initial and final +nodes (or states) of the network are distinguished. It can +be understood as accepting the set of strings obtained by traversing it +from its initial node to its final node, and concatenating the labels. +

+

+ + + + + + + + + + + + + + + + + + + + + + + + + + +

+

A finite state transducer has two labels on each arc, and can be +thought of as representing a mapping from one sequence of labels to +the other. The following example represents a transducer for +translating the English strings accepted by the network in the +preceding example into French. The nodes have been annotated with +numbers, for convenience.

+

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

+
Family Trees +

The next example provides an encoding a portion of a +family treeThe family tree is that of the +mathematician and philosopher Bertrand Russell, whose third wife was +commonly known as Peter. The information presented here is taken from +Pereira and Shieber (1987). in which nodes are used to represent +individuals and parents of individuals, and arcs are used to +represent common parentage and descent links. Let us suppose, +further, that information about individuals is contained in feature +structures, which are contained in feature-structure libraries +elsewhere (see ). We can use the +value attribute on node elements to point to those +feature structures. In this particular representation of +the graph, nodes representing females are framed by ovals, nodes +representing males are framed by boxes, and nodes representing parents +are framed by diamonds. +

+

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

+
Historical Interpretation +

For our final example, we represent graphically the relationships +among various geographic areas mentioned in a +seventeenth-century Scottish document. The document itself is +a sasine, which records a grant of land +from the earl of Argyll to one Donald McNeill, and reads in part +as follows (abbreviations have been expanded silently, +and [...] marks illegible passages): + +

Item instrument of Sasine given the said Hector +Mcneil confirmed and dated 28 May 1632 +[...] at Edinburgh upon the 15 June 1632

+

Item ane charter granted by Archibald late earl +of Argyle and Donald McNeill of Gallachalzie wh +makes mention that ... +the said late Earl yields and grants +to the said Donald MacNeill ...

+

All and hail the two merk land of old extent +of Gallachalzie with the pertinents by and in +the lordship of Knapdale within the sherrifdome +of Argyll

+

[description of other lands granted follows ...]

+

This Charter is dated at Inverary the 15th May 1669

+

In this example, we are concerned with the land and pertinents (i.e. +accompanying sources of revenue) described as the two merk land of +old extent of Gallachalzie with the pertinents by and in the lordship of +Knapdale within the sherrifdom of Argyll.

+

The passage concerns the following pieces of land: + +the Earl of Argyll's land (i.e. the lands granted by this clause +of the sasine) +two mark of land in Gallachalzie +the pertinents for this land +the Lordship of Knapdale +the sherrifdom of Argyll +We will represent these geographic entities as nodes in a graph. +Arcs in the graph will represent the following relationships among +them: + +containment (INCLUDE) +location within (IN) +contiguity (BY) +constituency (PART OF) +Note that these relationships are logically related: include +and in, for example, are inverses of each other: the Earl of +Argyll's land includes the parcel in Gallachalzie, and the parcel is +therefore in the Earl of Argyll's land. Given an explicit set of +inference rules, an appropriate application could use the graph we are +constructing to infer the logical consequences of the relationships we +identify.

+

Let us assume that feature-structure analyses are available which +describe Gallachalzie, Knapdale, and Argyll. We will link to those +feature structures using the value attribute on the nodes +representing those places. However, there may be some uncertainty as to +which noun phrase is modified by the phrase within the sheriffdome of +Argyll: perhaps the entire lands (land and pertinents) are in +Argyll, perhaps just the pertinents are, or perhaps only Knapdale is +(together with the portion of the pertinents which is in Knapdale). We +will represent all three of these interpretations in the graph; they +are, however, mutually exclusive, which we represent using the +exclude attribute defined in +chapter .That is, the three syntactic +interpretations of the clause are mutually exclusive. The notion that +the pertinents are in Argyll is clearly not inconsistent with the notion +that both the land in Gallachalzie and the pertinents are in Argyll. +The graph given here describes the possible interpretations of the +clause itself, not the sets of inferences derivable from each syntactic +interpretation, for which it would be convenient to use the facilities +described in chapter .

+

We represent the graph and its encoding as follows, where +the dotted lines in the graph indicate the mutually exclusive arcs; in +the encoding, we use the exclude attribute to indicate those +arcs. +

+

+

The graph formalizes the following relationships: + +the Earl of Argyll's land includes (the parcel of +land in) Gallachalzie +the Earl of Argyll's land includes the pertinents of that parcel +the pertinents are (in part) by the Lordship of Knapdale +the pertinents are (in part) part of the Lordship of Knapdale +the Earl of Argyll's land, or the pertinents, or +the Lordship of Knapdale, is in the Sherrifdom of Argyll +We encode the graph thus: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

+
Trees +

A tree is a connected acyclic graph. That is, it is +possible in a tree graph to follow a path from any vertex to any other +vertex, but there are no paths that lead from any vertex to itself. A +rooted tree is a directed graph based on a tree; that is, the arcs in +the graph correspond to the arcs of a tree such that there is exactly +one node, called the root, for which there is a path from +that node to all other nodes in the graph. For our purposes, we may +ignore all trees except for rooted trees, and hence we shall use the +tree element for rooted trees, and the root element +for its root. The nodes adjacent to a given node are called its +children, and the node adjacent from a given node is called +its parent. Nodes with both a parent and children are +called internal nodes, for which we use the iNode +element. A node with no children is tagged as a leaf. If the +children of a node are ordered from left to right, then we say that that +node is ordered. If all the nodes of a tree are ordered, +then we say that the tree is an ordered tree. If some of +the nodes of a tree are ordered and others are not, then the tree is a +partially ordered tree. The ordering of nodes and trees +may be specified by an attribute; we take the default ordering for trees +to be ordered, that roots inherit their ordering from the trees in which +they occur, and internal nodes inherit their ordering from their +parents. Finally, we permit a node to be specified as following other +nodes, which (when its parent is ordered) it would be assumed to +precede, giving rise to crossing arcs. +The elements used for the +encoding of trees have the following descriptions and attributes. + + + + +

+

Here is an example of a tree. It represents the order in which the +operators of addition (symbolized by +), exponentiation +(symbolized by **) and division (symbolized by /) are +applied in evaluating the arithmetic formula +((a**2)+(b**2))/((a+b)**2). +In drawing the graph, the root is placed on the far right, and +directionality is presumed to be to the left. +

+

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

+

In this encoding, the arity attribute represents the +arity of the tree, which is the greatest value of the +outDegree attribute for any of the nodes in the tree. If, as +in this case, arity is 2, we say that the tree is a +binary tree.

+

Since the left-to-right (or top-to-bottom!) order of the children of +the two + nodes does not affect the arithmetic result in this +case, we could represent in this tree all of the arithmetically +equivalent formulas involving its leaves, by specifying the attribute +ord as false on those two iNode elements, the attribute +ord as true on the root and other iNode +elements, and the attribute ord as partial on the tree +element, as follows. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

+

This encoding represents all of the following: + + ((a**2)+(b**2))/((a+b)**2) + ((b**2)+(a**2))/((a+b)**2) + ((a**2)+(b**2))/((b+a)**2) + ((b**2)+(a**2))/((a+b)**2) + +

+

Linguistic phrase structure is very commonly represented by trees. +Here is an example of phrase structure represented by an ordered tree +with its root at the top, and a possible encoding. +

+

+ + + + + + + + + + + + + + + + + + + + + + + + + + +

+

Finally, here is an example of an ordered tree, in which a particular +node which ordinarily would precede another is specified as following +it. In the drawing, the xxx symbol indicates that the arc from +VB to PT crosses the arc from VP to PN. +

+

+ + + + + + + + + + + + + + + + + + + + + + + + + +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+
Another Tree Notation +

In this section, we present an alternative to the method of +representing the structure of ordered rooted trees given in +section , which is based on the observation +that any node of such a tree can be thought of as the root of the +subtree that it dominates. Thus subtrees can be thought of as the same +type as the trees they are embedded in, hence the designation +eTree, for embedding tree. Whereas in a +tree the relationship among the parts is indicated by the +children attribute, and by the names of the elements +root, iNode, and leaf, the relationship among +the parts of an eTree is indicated simply by the arrangement of +their content. However, we have chosen to enable encoders to +distinguish the terminal elements of an eTree by means of the +empty eLeaf element, though its use is not required; the +eTree element can also be used to identify the terminal nodes +of eTree elements. We also provide a triangle +element, which can be thought of as an underspecified +eTree, i.e. an eTree in which certain information +has been left out. In addition, we provide a forest element, +which consists of one or more tree, eTree, or +triangle elements, and a listForest element, which +consists of one or more forest elements. The elements used for +the encoding of embedding trees and the units containing them have the +following descriptions and attributes. + + + + + + +

+

Like the root, iNode, and leaf of a +tree, the eTree, triangle and +eLeaf elements may also have +value attributes and label children.

+

To illustrate the use of the eTree and eLeaf +elements, here is an encoding of the second example in section , repeated here for convenience. +

+

+ + + + + + + + + + + + + + + + + + + + + + + +

+

Next, we provide an encoding, using the triangle element, in +which the internal structure of the eTree labeled NP is +omitted. +

+

+ + + + + + + + + + + + + + + +

+

Ambiguity involving alternative tree structures associated with the +same terminal sequence can be encoded relatively conveniently using a +combination of the exclude and copyOf attributes +described in sections and . In +the simplest case, an eTree may be part of the content of +exactly one of two different eTree elements. To mark it up, +the embedded eTree may be fully specified within one of the +embedding eTree elements to which it may belong, and a +virtual copy, specified by the copyOf attribute, may appear +on the other. In addition, each of the embedded elements in question +is specified as excluding the other, using the exclude +attribute. To illustrate, consider the English phrase see the +vessel with the periscope, which may be considered to be +structurally ambiguous, depending on whether the phrase with +the periscope is a modifier of the phrase the +vessel or a modifier of the phrase see the +vessel. This ambiguity is indicated in the sketch of the +ambiguous tree by means of the dotted-line arcs. The markup using the +copyOf and exclude attributes follows the +sketch. +

+

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

+

To indicate that one of the alternatives is selected, one may specify +the select attribute on the highest eTree as +either #GD-PPA or #GD-PPB; see section +.

+

Depending on the grammar one uses to associate structures with +examples like see the man with the periscope, the +representations may be more complicated than this. For example, +adopting a version of the X-bar theory of phrase structure +originated by Jackendoff, the +attachment of a modifier may require the creation of an intermediate +node which is not required when the attachment is not made, as shown in +the following diagram. A possible encoding of this ambiguous structure +immediately follows the diagram. +

+

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

+ +

A derivation in a generative grammar is often thought +of as a set of trees. To encode such a derivation, one may use the +forest element, in which the trees may be marked up using the +tree, the eTree, or the triangle element. +The type attribute may be used to specify what kind of +derivation it is. Here is an example of a two-tree forest, involving +application of the wh-movement transformation in +the derivation of what you do (as in this is +what you do) from the underlying you do +what.The symbols +e and t denote +special theoretical constructs (empty category and +trace respectively), which need not concern us here. +

+

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

+

In this markup, we have used copyOf attributes to provide +virtual copies of elements in the tree representing the second stage of +the derivation that also occur in the first stage, and the +corresp attribute (see section ) to link +those elements in the second stage with corresponding elements in the +first stage that are not copies of them.

+

If a group of forests (e.g. a full grammatical derivation including +syntactic, semantic, and phonological subderivations) is to be +articulated, the grouping element listForest may be used.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ +
Representing Textual Transmission + +

A stemma codicum (sometimes called just +stemma) is a tree-like graphic structure that has become +traditional in manuscript studies for representing textual +transmission. Consider the following hypothetical stemma: +

Example stemma +
+

+ +

The nodes in this stemma represent manuscripts; each has a label (a +letter) which identifies it and also distinguishes whether the +manuscript is extant, lost, or hypothetical. Extant manuscripts are +identified by uppercase Latin letters or words beginning with +uppercase Latin letters, e.g., L, shown as aqua in this example; +manuscripts no longer existing, but providing readings which are +attested e.g. by note or copy made before their disappearance, are +identified by lowercase Latin letters, e.g., t, shown as magenta in +this example; hypothetical stages in the textual transmission, which +do not necessarily correspond to real manuscripts, are given +lowercase Greek letters, e.g., α and shown as gold in this example. +The stemma shown above thus suggests that (on the basis of +similarities in the readings of the extant and lost manuscripts) L +and t share textual material that is not shared with other +manuscripts (represented in this case by δ) even though no physical +manuscript attesting this stage in the textual transmission has ever +been identified.

+ +

Manuscripts are copied from other manuscripts. The preceding +stemma represents the hypothesis that all manuscripts go back to a common +ancestor (α), that the tradition split after that stage into two +(β and γ), etc. Descent by copying is indicated with a solid line. +According to this model, α is the earliest common hypothetical stage +that can be reconstructed, and all nodes below α have a single +parent, that is, were copied from a single other stage in the +tradition.

+ +

This familiar tree model is complicated because manuscripts +sometimes show the influence of more than one ancestor. They may have +been produced by a scribe who checked the text in one +manuscript of the same work whilst copying from another, or perhaps +made changes from his memory of a slightly different version of the +text that he had read elsewhere. Alternatively, perhaps scribe A +copied a manuscript from one source, scribe B made changes in it in +the margins or between the lines (either by consulting another source +directly or from memory), and another scribe then copied that +manuscript, incorporating the changes into the body. Whatever the +specific scenario, it is not uncommon for a +manuscript to be based primarily on one source, but to incorporate +features of another branch of the tradition. This mixed result is +called contamination, and it is reflected in a stemma by a +dotted line. Thus, the example above asserts that A is copied within +the ε tradition, but is also contaminated from the γ +tradition.

+ +

The utility of a stemma as a visualization tool is inversely +proportional to the degree of contamination in the manuscript +tradition. A tradition completely without contamination (called a +closed tradition) yields a classic tree, easily +represented graphically by a stemma. An open tradition, with +substantial contamination, yields a spaghetti-like stemma +characterized by crossing dotted lines, which is both difficult to +read and not very informative.

+ +

The eTree element introduced in this chapter can be used +to represent a closed tradition in a straightforward manner. Each +non-terminal node is represented by a typed eTree element and +each terminal node by an eLeaf. A label element +provides a way of identifying each node, complementary to the global +attributes n and xml:id attributes. For example, +the closed part of the tradition headed by the label δ may be encoded +as follows: + + + + + + + + + + + +To complete this representation, we need to show that the node +labelled A is not derived solely from its parent node (labelled ε) +but also demonstrates contamination from the node labelled γ. The +easiest way to accomplish this is to include an appropriately-typed +ptr element within the node in question, the +target of which points to the node labelled γ. This +requires that this latter node be supplied with a value for its +xml:id attribute. The complete representation is thus: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

+

In any substantial codicological project, it is likely that +significantly more data will be required about the individual +witnesses than indicated in the simple structures above. These +Guidelines provide a rich variety of additional elements for +representing such information: see in particular chapters , , and .

+ +
+ +
+ Module for Graphs, Networks, and Trees +

The module described in this chapter makes available the + following components: + + Graphs, networks, and trees + Graphs, networks, and trees + Graphes, réseaux et arbres + 圖形、網絡與樹狀結構 + Grafici, reti e alberi + Grafos, redes, e árvores + グラフモジュール + + + The selection and combination of modules to form a TEI schema is + described in . + + + +

+
+
\ No newline at end of file diff --git a/P5/Source/Guidelines/fr/HD-Header.xml b/P5/Source/Guidelines/fr/HD-Header.xml index a260362732..1b41c58497 100644 --- a/P5/Source/Guidelines/fr/HD-Header.xml +++ b/P5/Source/Guidelines/fr/HD-Header.xml @@ -1,3 +1,4 @@ +
diff --git a/P5/Source/Guidelines/fr/MS-ManuscriptDescription.xml b/P5/Source/Guidelines/fr/MS-ManuscriptDescription.xml deleted file mode 120000 index ad777996bd..0000000000 --- a/P5/Source/Guidelines/fr/MS-ManuscriptDescription.xml +++ /dev/null @@ -1 +0,0 @@ -../en/./MS-ManuscriptDescription.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/MS-ManuscriptDescription.xml b/P5/Source/Guidelines/fr/MS-ManuscriptDescription.xml new file mode 100644 index 0000000000..cbe3f34f5f --- /dev/null +++ b/P5/Source/Guidelines/fr/MS-ManuscriptDescription.xml @@ -0,0 +1,2571 @@ + + + + +
+Manuscript Description +
+Overview +

The msdescription module + This chapter is based on the work of the European MASTER (Manuscript Access +through Standards for Electronic Records) project, funded by the European Union +from January 1999 to June 2001, and led by Peter Robinson, then at the Centre +for Technology and the Arts at De Montfort University, Leicester (UK). +Significant input also came from a TEI Workgroup headed by Consuelo W. Dutschke +of the Rare Book and Manuscript Library, Columbia University (USA) and Ambrogio +Piazzoni of the Biblioteca Apostolica Vaticana (IT) during 1998-2000. +defines a special purpose element which can be used to provide detailed +descriptive information about handwritten primary sources and other text-bearing objects. +Although originally developed to meet the needs of cataloguers and scholars working with medieval +manuscripts in the European tradition, the scheme presented here is general +enough that it can also be extended to other traditions and materials, and is +potentially useful for any kind of text-bearing artefact. Where the textuality of +an object is not the primary concern, encoders may wish to use the object +element which provides a very similar system of description (see .

+

The scheme described here is also intended to accommodate the needs of many +different classes of encoders. On the one hand, encoders may be engaged in +retrospective conversion of existing detailed descriptions and +catalogues into machine tractable form; on the other, they may be engaged in +cataloguing ex nihilo, that is, creating new detailed +descriptions for materials never before catalogued. Some may be primarily +concerned to represent accurately the description itself, as opposed to the +ideas and interpretations the description represents; others may have entirely +opposite priorities. At one extreme, a project may simply wish to capture an +existing catalogue in a form that can be displayed on the Web, and which can be +searched for literal strings, or for such features such as titles, authors and +dates; at the other, a project may wish to create, in highly structured and +encoded form, a detailed database of information about the physical +characteristics, history, interpretation, etc. of the material, able to support +practitioners of quantitative codicology as well as librarians.

+

To cater for this diversity, here as elsewhere, these Guidelines propose a +flexible strategy, in which encoders must choose for themselves the approach +appropriate to their needs, and are provided with a choice of encoding +mechanisms to support those differing degrees.

+
+
+The Manuscript Description Element +

The msDesc element will normally appear within the +sourceDesc element of the header of a TEI-conformant document, where +the document being encoded is a digital representation of some manuscript +original, whether as an encoded transcription, as a collection of digital images +(as described in ), or as some combination of the two. +However, in cases where the document being encoded is essentially a collection +of manuscript descriptions, the msDesc element may be used in the same +way as the bibliographic elements (bibl, biblFull, and +biblStruct) making up the TEI element class model.biblLike. +These typically appear within the listBibl +element. + +

+

The msDesc element has the following components, which provide more +detailed information under a number of headings. Each of these component +elements is further described in the remainder of this chapter. + + + + + + + + +

+

The first of these components, msIdentifier, is the only one which +is mandatory; it is described in more detail in below. It +is followed optionally by one or more head elements, each holding a +brief heading (see ), and then either one or more +paragraphs, marked up as a series of p elements, or at most +one of each of the specialized elements msContents (), +physDesc (), history (), +and additional (). These elements are all +optional, and if used they may appear at most once in a given +msDesc, in any order. Finally, +in the case of a composite manuscript (a manuscript composed of several +codicological units) or a fragmented manuscript (a manuscript whose parts are now +dispersed and kept at different places), a full description may also contain one or more +msPart () elements and msFrag () +elements, respectively.

+

To demonstrate the use of this module, consider the following sample +manuscript description, chosen more or less at random from the Bodleian +Library's Summary catalogue ()

+ +Entry for Bodleian MS. Add. A. 61 in Madan et al. 1895-1953 +
+

+

The simplest way of digitizing this catalogue entry would simply be to key in +the text, tagging the relevant parts of it which make up the mandatory +msIdentifier element, as follows: + + + +Oxford +Bodleian Library +MS. Add. A. 61 +28843 + +

In Latin, on parchment: written in more than one hand of the 13th cent. in +England: 7¼ x 5⅜ in., i + 55 leaves, in double columns: with a few coloured +capitals.

+

'Hic incipit Bruitus Anglie,' the De origine et gestis Regum Angliae of +Geoffrey of Monmouth (Galfridus Monumetensis: beg. 'Cum mecum multa & de +multis.'

+

On fol. 54v very faint is 'Iste liber est fratris guillelmi de buria de ... +Roberti ordinis fratrum Pred[icatorum],' 14th cent. (?): 'hanauilla' is written +at the foot of the page (15th cent.). Bought from the rev. W. D. Macray on March +17, 1863, for £1 10s.

+ + With a suitable stylesheet, this encoding would be as readable as the original; +it would not, however, be very useful for search purposes since only shelfmarks +and other identifiers are distinguished. To improve on this, one might wrap the +paragraphs in the appropriate special-purpose first-child-level elements of +msDesc and add some of the additional phrase-level elements available +when this module is in use: + + + +Oxford +Bodleian Library +MS. Add. A. 61 + +28843 + + + +

Hic incipit Bruitus Anglie, the De origine et gestis +Regum Angliae of Geoffrey of Monmouth (Galfridus Monumetensis): beg. +Cum mecum multa & de multis. In Latin.

+ + +

Parchment: written in +more than one hand: 7¼ x 5⅜ in., i + 55 leaves, in double columns: +with a few coloured capitals.

+ + +

Written in England in the 13th +cent. On fol. 54v very faint is Iste liber est fratris +guillelmi de buria de ... Roberti ordinis fratrum Pred[icatorum], 14th +cent. (?): hanauilla is written at the foot of the page (15th +cent.). Bought from the rev. W. D. Macray on March 17, 1863, for £1 10s.

+ + + + Note that in this version the text has been slightly reorganized, but no actual +rewriting has been necessary. The encoding now allows the user to search for +such features as title, material, and date and place of origin; it is also +possible to distinguish quoted material from descriptive passages and to search +within descriptions relating to a particular topic (for example, history as +distinct from material).

+

This process could be continued further, restructuring the whole entry so as +to take full advantage of many more of the encoding possibilities provided by +the module described in this chapter: + + + +Oxford +Bodleian Library +MS. Add. A. 61 + +28843 + + + + +Geoffrey of Monmouth +Galfridus Monumetensis +De origine et gestis Regum Angliae +Hic incipit Bruitus Anglie +Cum mecum multa & de multis +Latin + + + + + + +

Parchment.

+ +i + 55 leaves +7¼ +5⅜ + + + + + +

In double columns.

+ + + + +

Written in more than one hand.

+ + +

With a few coloured capitals.

+ + + + +

Written in England in the 13th cent.

+ + +

On fol. 54v very faint is Iste liber est fratris +guillelmi de buria de Roberti ordinis fratrum +Predicatorum, 14th cent. (?): hanauilla is +written at the foot of the page (15th cent.).

+ + +

Bought from the rev. W. D. Macray on March 17, 1863, for £1 10s.

+ + + + + In the remainder of this chapter we discuss all of the encoding features +demonstrated above, together with many other related matters.

+ + + +
+
+Phrase-level Elements +

When the msdescription module is in use, several +extra elements are added to the phrase level class, and thus become available +within paragraphs and elsewhere in the document. These elements are listed below +in alphabetical order: + + + + + + + + + + + + +

+

Within a manuscript description, many other standard TEI phrase level +elements are available, notably those described in the Core module (). Additional elements of particular relevance to manuscript +description, such as those for names and dates, may also be made available by +including the relevant module in one's schema.

+
+Origination +

The following elements may be used to provide information about the origins +of any aspect of a manuscript: + + +

+

The origDate and origPlace elements are specialized forms +of the existing date and name elements respectively, used to +indicate specifically the date and place of origin of a manuscript or manuscript +part. Such information would normally be encoded within the history +element, discussed in section . origDate and +origPlace can also be used to identify the place or date of origin of +any aspect of the manuscript, such as its decoration or binding, when these are +not of the same date or from the same location as rest of the manuscript. Both +these elements are members of the att.editLike +class, from which they inherit many attributes. +

+

The origDate element is a member of the att.datable class, and may thus also carry additional attributes giving +normalized values for the associated dating. +

+
+
+Material and Object Type +

The material element can be used to tag any specific term used for +the physical material of which a manuscript (or binding, seal, etc.) is +composed. The objectType element may be used to tag any term specifying +the type of object or manuscript upon with the text is written. + + +

+

These elements may appear wherever a term regarded as significant by the +encoder occurs, as in the following examples: + + +

Brown calfskin, previously with two clasps.

+ + + + +

Parchment +codex with half goat-leather +binding.

+ + +

+
+
+Watermarks and Stamps +

Two further elements are provided to mark up other decorative features +characteristic of manuscript leaves and bindings: + + +

+

These elements may appear wherever a term regarded as significant by the +encoder occurs. The watermark element is most likely to be of use +within the support element discussed in +below. We give a simple example here: +Rag +paper with anchor watermark +

+

The stamp element will typically appear when text from the source is +being transcribed, for example within a rubric in the following case: + +Apologyticu TTVLLIANI AC IGNORATIA IN XPO IHV +SI NON LICET +NOBIS RO +manii imperii Bodleian stamp + +

+

It may also appear as part of the detailed description of a binding: + +

Modern calf recasing with original armorial stamp with legend +Ex Bibliotheca J. Richard +D.M.

+ +

+

If, as here, any text contained by a stamp is included in its description it +should be clearly distinguished from that description. The element +mentioned may be used for this purpose, as shown above.

+
+
+Dimensions +

The dimensions element can be used to specify the size of some +aspect of the manuscript, and thus may be thought of as a specialized form of +the existing TEI measure element. + +

+

The dimensions element will normally occur within the element +describing the particular feature or aspect of a manuscript whose dimensions are +being given; thus the size of the leaves would be specified within the +support or extent element (part of the physDesc +element discussed in ), while the dimensions of other +specific parts of a manuscript, such as accompanying materials, binding, etc., +would be given in other parts of the description, as appropriate.

+

The following elements are available within the dimensions element: + + + + + +

+

These elements, as well as dimensions itself, are all members of the +att.dimensions class, which also inherits attributes +from the att.ranging class. They all thus carry the +following attributes: + + +

+

Attributes scope, min, and max are used only +when the measurement applies to several items, for example the size of all +leaves in a manuscript; attributes atLeast and atMost are +used when the measurement applies to a single item, for example the size of a +specific codex, but has had to be estimated. Attribute quantity is +used when the measurement can be given exactly, and applies to a single item; +this is the usual situation. In this case, the units in which dimensions are +measured may be specified using the unit attribute, the value of +which will normally be taken from a closed set of values appropriate to the +project, using standard units of measurement wherever possible, such as +cm, mm, in, line, char. +If however the only data available for the measurement uses some other unit, or +it is preferred to normalize it in some other way, then it may be supplied as a +string value by means of the extent attribute.

+

In the simplest case, only the extent attribute may be supplied: +six +cubits + More usually, the measurement will be normalized into a value and an +appropriate SI unit: +six cubits + Where the exact value is uncertain, the attributes atLeast and +atMost may be used to indicate the upper and lower bounds of an +estimated value: +six cubits +

+

It is often convenient to supply a measurement which applies to a number of +discrete observations: for example, the number of ruled lines on the pages of a +manuscript (which may not all be the same), or the diameter of an object like a +bell, which will differ depending where it is measured. In such cases, the +scope attribute may be used to specify the observations for which +this measurement is applicable: + + + This indicates that most pages have at least 20 lines. The attributes +min and max can also be used to specify the possible range +of values: for example, to show that all pages have between 12 and 30 lines: + + +

+

The dimensions element may be repeated as often as necessary, with +appropriate attribute values to indicate the nature and scope of the measurement +concerned. For example, in the following case the leaf size and ruled space of +the leaves of the manuscript are specified: + + + + + + + + + + + This indicates that for most leaves of the manuscript being described the ruled +space is 90 mm high and 48 mm wide, while the leaves throughout are between 157 +and 160 mm in height and 105 mm in width.

+

The dim element is provided for cases where some measurement other +than height, width, or depth is required. Its type attribute is used +to indicate the type of measurement involved: + + + + + + +

+

The order in which components of the dimensions element may be +supplied is not constrained. +

+
+
+References to Locations within a Manuscript +

The locus and its grouping element locusGrp element are +specialized forms of the ref element, used to indicate a location, or +sequence of locations, within a manuscript. + + +

+

The locus element is used to reference a single location within a +manuscript, typically to specify the location occupied by the element within +which it appears. If, for example, it is used as the first component of an +msItem or msItemStruct element, or of any of the more specific +elements appearing within one (see further section below) +then it is understood to specify the location (or locations) of that item within +the manuscript being described.

+
+Identifying a Location +

A locus element can be used to identify any reference to one or more +folios within a manuscript, wherever such a reference is appropriate. Locations +are conventionally specified as a sequence of folio or page numbers, but may +also be a discontinuous list, or a combination of the two. This specification +should be given as the content of the locus element, using the +conventions appropriate to the individual scholar or holding institution, as in +the following example: + +ff. 1-24r +Apocalypsis beati Ioannis Apostoli + + +

+

A normalized form of the location can also be supplied, using special purpose +attributes on the locus element, as in the following revision of the +above example: + +ff. 1-24r +Apocalypsis beati Ioannis Apostoli + + +

+

When the item concerned occupies a discontinuous sequence of pages, this may +simply be indicated in the body of the locus element: + +ff. 1-12v, 18-24r +Apocalypsis beati Ioannis Apostoli + + + Alternatively, if it is desired to indicate normalized values for each part of +the sequence, a sequence of locus elements can be supplied, grouped +within the locusGrp element: + + +ff. 1-12v +ff. 18-24r + +Apocalypsis beati Ioannis Apostoli + + + +If an existing catalogue is being transcribed and it is desirable to retain formatting of the reference (e.g. superscript or italic text) then the hi element may be used. If encoding multiple semantic divisions in a single location reference then a nested locus may be used to separate or annotate these. +

+

Finally, the content of the locus element may be omitted if a +formatting application can construct it automatically from the values of the +from and to attributes: + + + + + +Apocalypsis beati Ioannis Apostoli + + +

+
+
+Linking a Location to a Transcription or an Image +

The locus attribute can also be used to associate a location within +a manuscript with facsimile images of that location, using the facs +attribute, or with a transcription of the text occurring at that location. The +former association is effected by means of the facs attribute; the +latter by means of the target attribute.

+

The facs is available only when the transcr module described in chapter is included in +a schema. It associates a locus element with one or more digitized +images, as in the following example: + + +fols. 8v-10v +Birds Praise of Love + +IMEV +1506 + + + + Here, the facs attribute uses a URI reference to point directly to +images of the relevant pages. This method may be found cumbersome when many +images are to be associated with a single location. It is of most use when +specific pages are referenced within a description, as in the following example: + + +

Several of the miniatures in this section have been damaged and overpainted +at a later date (e.g. the figure of Christ on fol. 33r; the face of the +Shepherdess on fol. +59v, etc.).

+ + + For further discussion of the facs attribute, see section .

+

Where a transcription of the relevant pages is available, this may be +associated with the locus element using its target +attribute, as in the following example: + + +ff. 1r-2r +Ben Jonson +Ode to himself + + An Ode + to him selfe. +Com leaue the loathed stage +And see his chariot triumph ore his wayne. +Beal, Index 1450-1625, JnB 380 + + + + + + + + + +

+

When (as in this example) a sequence of elements is to be supplied as target +value, it may be given explicitly as above, or using the xPointer range() syntax +defined at . Note however that support for this pointer +mechanism is not widespread in current XML processing systems.

+

The target attribute should only be used to point to elements that +contain or indicate a transcription of the locus being described. To associate a +locus element with a page image or other comparable representation, the +global facs attribute should be used instead.

+
+
+Using Multiple Location Schemes +

Where a manuscript contains more than one foliation, the scheme +attribute may be used to distinguish them. For example, MS 65 Corpus Christi +College, Cambridge contains two fly leaves bearing music. These leaves have +modern foliation 135 and 136 respectively, but are also marked with an older +foliation. This may be preserved in an encoding such as the following: + +XCIII +135 + + Here the scheme attribute points to a foliation element +providing more details about the scheme used, as further discussed in below.

+

Where discontinuous sequences are identified within two different foliations, +the scheme attribute should be supplied on the locusGrp +element in preference, as in the following: + + +XCIII +CC-CCII + + +135 +197-204 + + +

+
+
+
+Names of Persons, Places, and Organizations +

The standard TEI element name may be used to identify names of any +kind occurring within a description: + + As further discussed in , this element is a +member of the class att.canonical, from which it +inherits the following attributes: + + +

+

Here are some examples of the use of the name element: + +Thomas Hoccleve +Villingaholt +Vetus Latina Institut +Occleve + +

+

Note that the name element is defined as providing information about +a name, not the person, place, or organization to which that name +refers. In the last example above, the ref attribute is used to +associate the name with a more detailed description of the person named. This is +provided by means of the person element, which becomes available when +the namesdates module described in chapter is included in a schema. An element such as the following might +then be used to provide detailed information about the person indicated by the +name: + + +Hoccleve +Thomas + + +poet + + + Note that an instance of +the person element must be provided for each distinct ref +value specified. For example, in the case above, the value HOC001 +must be found as the xml:id attribute of some person +element; the same value will be used as the ref attribute of every +reference to Hoccleve in the document (however spelled), but there will only be +one person element with this identifier.

+

Alternatively, the key attribute may be used to supply a unique +identifying code for the person referenced by the name independently of both the +existence of a person element and the use of the standard URI reference +mechanism. If, for example, a project maintains as its authority file some +non-digital resource, or uses a database which cannot readily be integrated with +other digital resources for this purpose, the unique codes used by such +offline resources may be used as values for the +key attribute. Although such practices clearly reduce the +interchangeability of the resulting encoded texts, they may be judged more +convenient or practical in certain situations. As explained in , interchange is improved by use of tag URIs in ref +instead of key.

+

All the person elements referenced by a particular +document set should be collected together within a listPerson + element, located in a standOff element. +This functions as a kind of prosopography for all the people +referenced by the set of manuscripts being described, in much the same +way as a listBibl element may be used to hold bibliographic +information for all the works referenced.

+

When the namesdates module described in chapter + is included in a schema, similar mechanisms are used to +maintain and reference canonical lists of places or organizations, as further +discussed in sections and +respectively.

+
+
+Catchwords, Signatures, Secundo Folio +

The catchwords element is used to describe one method by which +correct ordering of the quires of a codex is ensured. Typically, this takes the +form of a word or phrase written in the lower margin of the last leaf verso of a +gathering, which provides a preview of the first recto leaf of the successive +gathering. This may be a simple phrase such as the following: +Quires signed on the +last leaf verso in roman numerals. + + Alternatively, it may contain more details: + +Vertical catchwords in the hand of the scribe placed along the inner +bounding line, reading from top to bottom. + +

+

The Signatures element is used, in a similar way, to +describe a similar system in which quires or leaves are marked progressively in +order to facilitate arrangement during binding. For example: +At the bottom of the +first four leaves of quires 1-14 are the remains of a series of quire signatures +a-o plus roman figures in a cursive hand of the fourteenth century. + +

+

The signatures element can be used for either leaf signatures, or a +combination of quire and leaf signatures, whether the marking is alphabetic, +alphanumeric, or some ad hoc system, as in the following more complex example: +Quire and leaf +signatures in letters, [b]-v, and roman numerals; those in quires 10 (1) and 17 +(s) in red ink and different from others; every third quire also signed with red +crayon in arabic numerals in the centre lower margin of the first leaf recto: +"2" for quire 4 (f. 19), "3" for quire 7 (f. 43); "4", barely visible, for quire +10 (f. 65), "5", in a later hand, for quire 13 (f. 89), "6", in a later hand, +for quire 16 (f. 113). + +

+

The secFol element (for secundo folio) is used +to record an identifying phrase (also called dictio +probatoria) taken from a specific known point in a codex (for example +the first few words on the second leaf). Since these words will differ from one +copy of a text to another, the practice originated in the middle ages of using +them when cataloguing a manuscript in order to distinguish individual copies of +a work in a way which its opening words could not. + +(ando-)ssene in una villa + +

+
+
+Heraldry + +

Descriptions of heraldic arms, supporters, devices, and mottos may appear at +various points in the description of a manuscript, usually in the context of +ownership information, binding descriptions, or detailed accounts of +illustrations. A full description may also contain a detailed account of the +heraldic components of a manuscript independently considered. Frequently, +however, heraldic descriptions will be cited as short phrases within other parts +of the record. The phrase level element heraldry is provided to allow +such phrases to be marked for further analysis, as in the following examples: + +

Ownership stamp (xvii cent.) on i recto with the arms A bull +passant within a bordure bezanty, in chief a crescent for difference +[Cole], crest, and the legend Cole Deum.

+ +

A c. 8r fregio su due lati, stemma e imprese medicee +racchiudono l'inizio dell'epistolario di Paolino.

+ +

+ + + + + + + + + + + + + + + + + + + + +
+
+
+The Manuscript Identifier +

The msIdentifier element is intended to provide an unambiguous means +of uniquely identifying a particular manuscript. This may be done in a +structured way, by providing information about the holding institution and the +call number, shelfmark, or other identifier used to indicate its location within +that institution. Alternatively, or in addition, a manuscript may be identified +simply by a commonly used name. + +

+

A manuscript's actual physical location may occasionally be different from +its place of ownership; at Cambridge University, for example, manuscripts owned +by various colleges are kept in the central University Library. Normally, it is +the ownership of the manuscript which should be specified in the manuscript +identifier, while additional or more precise information on the physical +location of the manuscript can be given within the adminInfo element, +discussed in section below.

+

The following elements are available within msIdentifier to identify +the holding institution: + + + + + +

+

These elements are all structurally equivalent to the standard TEI +name element with an appropriate value for its type +attribute; however the use of this syntactic sugar enables +the model for msIdentifier to be constrained rather more tightly than +would otherwise be possible. Specifically, only one of each of the elements +listed above may appear within the msIdentifier and they must, if +present, appear in the order given.

+

Like name, these elements are all also members of the attribute +class att.canonical, and thus can use the attributes +key or ref to reference a single standardized source of +information about the entity named.

+

The following elements are used within msIdentifier to provide +different ways of identifying the manuscript within its holding institution: + + + + +

+

Major manuscript repositories will usually have a preferred form of citation +for manuscript shelfmarks, including rules about punctuation, spacing, +abbreviation, etc., which should be adhered to. Where such a format also +contains information which might additionally be supplied as a distinct +subcomponent of the msIdentifier, for example a collection name, a +decision must be taken as to whether to use the more specific element, or to +include such information within the idno element. For example, the +manuscript formally identified as El 26 C 9 forms a part of the Ellesmere +(El) collection. Either of the following encodings is therefore feasible: + + +USA +California +San Marino +Huntington Library +El +26 C 9 +The Ellesmere Chaucer + + + + +USA +California +San Marino +Huntington Library +El 26 C 9 +The Ellesmere Chaucer + + +

+

In the former example, the preferred form of the identifier can be retrieved +by prefixing the content of the idno element with that of the +collection element, while in the latter it is given explicitly. The +advantage of the former is that it simplifies accurate retrieval of all +manuscripts from a given collection; the disadvantage is that encoded +abbreviations of this kind may not be as immediately comprehensible. Care should +be taken to avoid redundancy: for example + +El +El 26 C 9 + + would clearly be inappropriate. Equally clearly, + +Ellesmere +El 26 C 9 + + might be considered helpful in some circumstances (if, for example, some of the +items in the Ellesmere collection had shelfmarks which did not begin El).

+

In some cases the shelfmark may contain no information about the collection; +in other cases, the item may be regarded as belonging to more than one +collection. The collection element may be added, and repeated as often +as necessary to cater for such situations: + + +Hungary +Budapest + Bibliothèque de l'Académie des Sciences de Hongrie +Oriental Collection +Sandor Kégl Bequest +MS 1265 + + +

+

+ + +USA +New Jersey +Princeton +Princeton University Library +Scheide Library +MS 71 +Blickling Homiliary + + +

+

Note in the latter case the use of the msName element to provide a +common name other than the shelfmark by which a manuscript is known. Where a +manuscript has several such names, more than one of these elements may be used, +as in the following example: + + +Danmark +København +Det Arnamagnæanske Institut +AM 45 fol. +Codex Frisianus +Fríssbók + + + Here the globally available xml:lang attribute has been used to +specify the language of the alternative names. +

+

In very rare cases a repository may have only one manuscript (or only one of +any significance), which will have no shelfmark as such but will be known by a +particular name or names. In such circumstances, the idno element may +be omitted, and the manuscript identified by the name or names used for it, +using one or more msName elements, as in the following example: + + +Rossano +Biblioteca arcivescovile +Codex Rossanensis +Codex purpureus +The Rossano Gospels + + +If a manuscript name contains a name or referencing string that it is useful to +annotate (e.g. by referring to an authority list) then name or rs +may be used for this purpose. +

+

Where manuscripts have moved from one institution to another, or even within +the same institution, they may have identifiers additional to the ones currently +used, such as former shelfmarks, which are sometimes retained even after they +have been officially superseded. In such cases it may be useful to supply an +alternative identifier, with a detailed structure similar to that of the +msIdentifier itself. The following example shows a manuscript which had +shelfmark II-M-5 in the collection of the Duque de Osuna, but which +now has the shelfmark MS 10237 in the National Library in Madrid: + + +Madrid +Biblioteca Nacional +MS 10237 + +Andalucia +Osuna +Duque de Osuna +II-M-5 + + + + Normally, such information would be dealt with under history, except +in cases where a manuscript is likely still to be referred to or known by its +former identifier. For example, an institution may have changed its call number +system but still wish to retain a record of the earlier number, perhaps because +the manuscript concerned is frequently cited in print under its previous number: + + +Berkeley +University of California +Bancroft Library +UCB 16 +2MS BS1145 I8 + + + Where (as in this example) no repository is specified for the +altIdentifier, it is assumed to be the same as that of the parent +msIdentifier. Where the holding institution has only one preferred form +of citation but wishes to retain the other for internal administrative purposes, +the secondary could be given within altIdentifier with an appropriate +value on the type attribute: + + +Oxford +Bodleian Library +MS. Bodley 406 +2297 + + + It might, however, be preferable to include such information within the +adminInfo element discussed in section +below.

+

Cases of such changed or alternative identifiers should be clearly +distinguished from cases of fragmented () manuscripts, that is to say manuscripts which although physically disjoint +are nevertheless generally treated as single units.

+

As mentioned above, the smallest possible description is one that contains +only the element msIdentifier; good practice in all but exceptional +circumstances requires the presence within it of the three sub-elements +settlement, repository, and idno, since they provide +what is, by common consent, the minimum amount of information necessary to +identify a manuscript.

+ + + + + + + + +
+
+The Manuscript Heading +

Historically, the briefest possible meaningful description of a manuscript +consists of no more than a title, e.g. Polychronicon. +This will often have been enough to identify a manuscript in a small collection +because the identity of the author is implicit. Where a title does not imply the +author, and is thus insufficient to identify the main text of a manuscript, the +author should be stated explicitly (e.g. Augustinus, +Sermones or Cicero, Letters). Many +inventories of manuscripts consist of no more than an author and title, with +some form of copy-specific identifier, such as a shelfmark or secundo +folio reference (e.g. Arch. B. 3. 2: Evangelium Matthei +cum glossa, 126. Isidori Originum libri octo, +Biblia Hieronimi, 2o fo. opus est); information on date +and place of writing will sometimes also be included. The standard TEI element +head element can be used to provide a brief description of this kind. + + In this way the cataloguer or scholar can supply in one place a +minimum of essential information, such as might be displayed or printed as the +heading of a full description. For example: + +Marsilius de Inghen, Abbreviata phisicorum Aristotelis; Italy, +1463. + + Any phrase-level elements, such as title, name, +date, or the specialized elements origPlace and +origDate, can also be used within a head element, but it +should be remembered that the head element is intended principally to +contain a heading. More structured information concerning the contents, physical +form, or history of the manuscript should be given within the specialized +elements described below, msContents, physDesc, +history, etc. However, in simple cases, the p element may also +be used to supply an unstructured collection of such information, as in the +example given above ().

+
+
+Intellectual Content +

The msContents element is used to describe the intellectual content +of a manuscript or manuscript part. It comprises either a series of +informal prose paragraphs or a series of msItem or +msItemStruct elements, each of which provides a more detailed +description of a single item contained within the manuscript. These may be +prefaced, if desired, by a summary element, which is especially useful +where one wishes to provide an overview of a manuscript's contents and describe +only some of the items in detail. + + + + + + +

+

In the simplest case, only a brief description may be provided, as in the +following examples: + + +

A collection of Lollard sermons

+ + + + +

Atlas of the world from Western Europe and Africa to Indochina, containing 27 + maps and 26 tables

+ + + + +

Biblia sacra: Antiguo y Nuevo Testamento, con prefacios, prólogos y + argumentos de san Jerónimo y de otros. Interpretaciones de los nombres + hebreos.

+ + +

+

This description may of course be expanded to include any of the TEI elements +generally available within a p element, such as title, +bibl, or list. More usually, however, each individual work +within a manuscript will be given its own description, using the msItem +or msItemStruct element described in the next section, as in the +following example: + + +fols. 5r -7v +An ABC +IMEV +239 +fols. 7v -8v +Lenvoy de Chaucer a Scogan +IMEV +3747 +fol. 8vTruth +IMEV +809 +fols. 8v-10v +Birds Praise of Love +IMEV +1506 +fols. 10v -11v +De amico ad amicam +Responcio +IMEV +16 & 19 +fols. 14r-126v +Troilus and Criseyde +Bk. 1:71-Bk. 5:1701, with additional losses due to mutilation +throughout + + + +

+

The summary element may be used in conjunction with one or more +msItem elements if it is desired to provide both a general summary of +the contents of a manuscript and more detail about some or all of the individual +items within it. It may not however be used within an individual msItem +element.

+ + +A collection of Lollard sermons +fol. 4r-8r +3rd Sunday Before Lent +fol. 9r-16v +Sexagesima + + + +
+The msItem and msItemStruct Elements +

Each discrete item in a manuscript or manuscript part can be described within +a distinct msItem or msItemStruct element, and may be +classified using the class attribute.

+

These are the possible component elements of msItem and +msItemStruct. + + + + + + + + + + + + + + + + +

+

In addition, an msItemStruct may contain nested msItemStruct +elements, just as an msItem may contain nested msItem +elements.

+

The main difference between msItem and msItemStruct is that +in the former, the order and number of child elements is not constrained; any +element, in other words, may be given in any order, and repeated as often as is +judged necessary. In the latter, however, the sub-elements, if used, must be +given in the order specified above and only some of them may be repeated; +specifically, rubric, finalRubric. incipit, +textLang and explicit can appear only once.

+

While neither msItem nor msItemStruct may contain untagged +running text, both permit an unstructured description to be provided in the form +of one or more paragraphs of text. They differ in this respect also: if +paragraphs are supplied as the content of an msItem, then none of the +other component elements listed above is permitted; in the msItemStruct +case, however, paragraphs may appear anywhere as an alternative to any of the +component elements listed above.

+

As noted above, both msItem and msItemStruct elements may +also nest, where a number of separate items in a manuscript are grouped under a +single title or rubric, as is the case, for example, with a work like The +Canterbury Tales.

+

The elements msContents, msItem, msItemStruct, +incipit, and explicit are all members of the class att.msExcerpt from which they inherit the +defective attribute. + + This attribute can be used for example with collections of +fragments, where each fragment is given as a separate msItem and the +first and last words of each fragment are transcribed as defective incipits and +explicits, as in the following example, a manuscript containing four fragments +of a single work: + + +1r-9v +Knýtlinga saga +1r:1-2v:30 +danna a englandi +en meðan haraldr hein hafði +konungr vit +yfir danmork + + + + + +

+

The elements ex, am, and expan used in the above +example are further discussed in section ; they are +available only when the transcr module defined by +that chapter is selected. Similarly, the g element used in this example +to represent the abbreviation mark is defined by the gaiji module documented in chapter .

+
+
+Authors and Titles +

When used within a manuscript description, the title element should +be used to supply a regularized form of the item's title, as distinct from any +rubric quoted from the manuscript. If the item concerned has a standardized +distinctive title, e.g. Roman de la Rose, then this +should be the form given as content of the title element, with the +value of the type attribute given as uniform. If no +uniform title exists for an item, or none has been yet identified, or if one +wishes to provide a general designation of the contents, then a +supplied title can be given, e.g. +missal, in which case the type attribute on +the title should be given the value supplied.

+

Similarly, if used within a manuscript description, the author +element should always contain the normalized form of an author's name, +irrespective of how (or whether) this form of the name is cited in the +manuscript. If it is desired to retain the form of the author's name as given in +the manuscript, this may be tagged as a distinct name element, within +the text at the point where it occurs.

+ +

Note that the key attribute can also be used, as on names in +general, to specify the identifier of a person element carrying full +details of the person concerned (see further ).

+

The respStmt element can be used to supply the name and role of a +person other than the author who is responsible for some aspect of the +intellectual content of the manuscript: + +Diogenes Laertius + +in the translation of +Ambrogio Traversari + + +

+

The respStmt element can also be used where there is a discrepancy +between the author of an item as given in the manuscript and the accepted +scholarly view, as in the following example: + +Sermons on the Epistles and the Gospels + +here erroneously attributed to +St. Bonaventura + + + Note that such attributions of authorship, both correct and incorrect, are +frequently found in the rubric or final rubric (and occasionally also elsewhere +in the text), and can therefore be transcribed and included in the description, +if desired, using the rubric, finalRubric, or quote +elements, as appropriate.

+
+
+Rubrics, Incipits, Explicits, and Other Quotations from the Text +

It is customary in a manuscript description to record the opening and closing +words of a text as well as any headings or colophons it might have, and the +specialized elements rubric, incipit, explicit, +finalRubric, and colophon are available within msItem +for doing so, along with the more general quote, for recording other +bits of the text not covered by these elements. Each of these elements has the +same substructure, containing a mixture of phrase-level elements and plain text. +A locus element can be included within each, in order to specify the +location of the component, as in the following example: + + +f. 1-223 +Radulphus Flaviacensis +Expositio super Leviticum +f. 1r Forte Hervei monachi +f. 223v Benedictio salis et aquae + + + +

+

In the following example, standard TEI elements for the transcription of +primary sources have been used to mark the expansion of abbreviations and other +features present in the original: + + +ff. 1r-24v +Ágrip af Noregs konunga sǫgum + +regi oc hann seti ho +sc heim sem þio +hon hever +oc þa buit hesta .ij. +annan viþ fé en honom annan til +reiþar + + + Note here also the use of the defective attribute on +incipit and explicit to indicate that the text begins and ends +defectively.

+

The xml:lang attribute for colophon, explicit, +incipit, quote, and rubric may always be used to +identify the language of the text quoted, if this is different from the default +language specified by the mainLang attribute on +textLang.

+
+ +
+Filiation +

The filiation element can be used to provide information on the +relationship between the manuscript and other surviving manuscripts of the same +text, either specifically or in a general way, as in the following example: + + +118rb +Ecce morior cum nichil horum ... [Dn 13, 43]. Verba ista +dixit Susanna de illis +ut bonum comune conservatur. +Schneyer 3, 436 (Johannes Contractus OFM) +weitere Überl. Uppsala C 181, 35r. + + +

+
+
+Text Classification +

One or more text classification or text-type codes may be specified, either +for the whole of the msContents element, or for one or more of its +constituent msItem elements, using the class attribute as +specified above: + + + +1v-71v +Jónsbók +Magnus med guds miskun Noregs konungur +enn uirda þo til fullra aura + + + The value used for the class attribute in this example points to a +category element with the identifier law, which defines +the classification concerned. Such category elements will typically +appear within a taxonomy element, within the classDecl element +of the TEI header () as in the following example: + + + + +Legislation + + +Military topics + + + + + More than one classification may apply to a single item. Another text, +concerned with legislation about military topics might thus be specified as +follows: + + +

A treatise on Clausewitz

+ + + +

+
+
+Languages and Writing Systems +

The textLang element should be used to provide information about the +languages used within a manuscript item. It may take the form of a simple note, +as in the following example: + +Old Church Slavonic, written in Cyrillic script. + +

+

Where, for validation and indexing purposes, it is thought convenient to add +keywords identifying the particular languages used, the mainLang +attribute may be used. This attribute takes the same range of values as the +global xml:lang attribute, on which see further . In the following example a manuscript written chiefly in Old Church Slavonic +is described: + +Old Church Slavonic + +

+ +

A manuscript item will sometimes contain material in more than one language. +The mainLang attribute should be used only for the chief language. +Other languages used may be specified using the otherLangs attribute +as in the following example: + +Mostly Old Church Slavonic, with +some Russian and Greek material + +

+

Since Old Church Slavonic may be written in either Cyrillic or Glagolitic +scripts, and even occasionally in both within the same manuscript, it might be +preferable to use a more explicit identifier: + +Old Church Slavonic in Cyrillic script + +

+

The form and scope of language identifiers recommended by these Guidelines is +based on the IANA standard described at and should be +followed throughout. 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 .

+

Note that the language element defines a particular combination of +human language and writing system. Only one language element may be +supplied for each such combination. Standard TEI practice also allows this +element to be referenced by any element using the global xml:lang +attribute in order to specify the language applicable to the content of that +element. For example, assuming that language elements have been defined +with the identifiers fr (for French), la (for +Latin), and de (for German), a manuscript description written in +French which specifies that a particular manuscript contains predominantly +German but also some Latin material, might have a textLang element like +the following: + +allemand et +latin + +

+ + + + + + + + + + + + + + + + + +
+
+
+Physical Description +

Under the general heading physical description we +subsume a large number of different aspects generally regarded as useful in the +description of a given manuscript. These include: +aspects of the form, support, extent, and quire structure of the +manuscript object and of the way in which the text is laid out on the page (); +the styles of writing, such as the way it is laid out on the page, the +styles of writing, decorative features, any musical notation employed and any +annotations or marginalia (); + and discussion of its binding, seals, and any accompanying material (). +

+

Most manuscript descriptions touch on several of these categories of +information though few include them all, and not all distinguish them as clearly +as we propose here. In particular, it is often the case that an existing +description will include information for which we propose distinct elements +within a single paragraph, or even sentence. The encoder must then decide +whether to rewrite the description using the structure proposed here, or to +retain the existing prose, marked up simply as a series of p elements, +directly within the physDesc element.

+

The physDesc element may thus be used in either of two distinct +ways. It may contain a series of paragraphs addressing topics listed above and +similar ones. Alternatively, it may act as a container for any choice of the +more specialized elements described in the remainder of this section, each of +which itself contains a series of paragraphs, and may also have more specific +attributes. +

+

In general, it is not recommended to combine unstructured prose description +with usage of the more specialized elements, as such an approach complicates +processing, and may lead to inconsistency within a single manuscript +description. A single physDesc element will normally contain either a +series of model.pLike elements, or a sequence of +specialized elements from the model.physDescPart +class. There are however circumstances in which this is not feasible, for +example: +the description already exists in a prose form where some of the +specialized topics are treated together in paragraphs of prose, but others are +treated distinctly; +although all parts of the description are clearly distinguished, some of +them cannot be mapped to a pre-existing specialized element. +

+

In such situations, both specialized and generic (model.pLike) elements may be combined in a single physDesc. +Note however that all generic elements given must precede the first specialized +element in the description. Thus the following is valid: + + +

Generic descriptive prose...

+ + + + + + + but neither of the following is valid: + + + + +

Generic descriptive prose...

+]]> + + + + +

Generic descriptive prose...

+ +]]> + The order in which specific elements may appear is also constrained by the +content model; again this is for simplicity of processing. They may of course be +processed or displayed in any desired order, but for ease of validation, they +must be given in the order specified below.

+
+Object Description +

The objectDesc element is used to group together those parts of the +physical description which relate specifically to the text-bearing object, its +format, constitution, layout, etc. The objectDesc element is used for grouping + elements relating to the physicality of a text-bearing object as part of a manuscript + description. If a full description of an object (text-bearing or not) is desired, the + more general object element may be preferred. +

+

The form attribute is used to +indicate the specific type of writing vehicle being described, for example, as a +codex, roll, tablet, etc. If used it must appear first in the sequence of +specialized elements. The objectDesc element has two parts: a +description of the support, i.e. the physical carrier on which the +text is inscribed; and a description of the layout, i.e. the way +text is organized on the carrier. +

+

Taking these in turn, the description of the support is tagged using the +following elements, each of which is discussed in more detail below: + + + + + + +

+

Each of these elements contains paragraphs relating to the topic concerned. +Within these paragraphs, phrase-level elements (in particular those discussed +above at ), may be used to tag specific terms of +interest if so desired. + + + +

Mostly paper, with watermarks +unicorn (Briquet 9993) and +ox (close to Briquet 2785). The first and last +leaf of each quire, with the exception of quires xvi and xviii, are constituted +by bifolia of parchment, and all seven miniatures have been painted on inserted +singletons of parchment.

+ + + +

+

This example combines information which might alternatively be more precisely +tagged using the more specific elements described in the following +subsections.

+
+Support +

The support element groups together information about the physical +carrier. Typically, for western manuscripts, this will entail discussion of the +material (parchment, paper, or a combination of the two) written on. For paper, +a discussion of any watermarks present may also be useful. If this discussion +makes reference to standard catalogues of such items, these may be tagged using +the standard ref element as in the following example: + +

+Paper with watermark: anchor in a circle with +star on top, countermark B-B with trefoil + similar to Mošin, Anchor N 1680 +1570-1585.

+ +

+
+
+Extent +

The extent element, defined in the TEI header, may also be used in a +manuscript description to specify the number of leaves a manuscript contains, as +in the following example: + +ii + 97 + ii + + Information regarding the size of the leaves may be specifically marked using +the phrase level dimensions element, as in the following example, or +left as plain prose. + +ii + 321 leaves +35 +27 + + + +

+

Alternatively, the generic measure element might be used within +extent, as in the following example: + + +10 Bl. +37 x 29 cm + +

+
+
+Collation +

The collation element should be used to provide a description of a +book's current and original structure, that is, the arrangement of its leaves +and quires. This information may be conveyed using informal prose, or any +appropriate notational convention. Although no specific notation is defined +here, an appropriate element to enclose such an expression would be the +formula element, which is provided when the figures module is included in a schema. Here are some examples of +different ways of treating collation: + +

1-3:8, 4:6, 5-13:8

+ +

There are now four gatherings, the first, second and fourth originally +consisting of eight leaves, the third of seven. A fifth gathering thought to +have followed has left no trace. +Gathering I consists of 7 leaves, a first leaf, originally conjoint with +fol. 7, having been cut away leaving only a narrow strip along +the gutter; the others, fols 1 and 6, +2 and 5, and 3 and +4, are bifolia. +Gathering II consists of 8 leaves, 4 bifolia. +Gathering III consists of 7 leaves; fols 16 and +22 are conjoint, the others singletons. +Gathering IV consists of 2 leaves, a bifolium. +

+ +

I (1, 2+9, 3+8, 4+7, 5+6, 10); II (11, 12+17, 13, 14, 15, 16, 18, +19).

 + +

1-5.8 6.6 (catchword, f. 46, does not match following text) 7-8.8 +9.10, 11.2 (through f. 82) 12-14.8 15.8(-7) +

+ + +

+
+
+Foliation +

The foliation element may be used to indicate the scheme, medium or +location of folio, page, column, or line numbers written in the manuscript, +frequently including a statement about when and, if known, by whom, the +numbering was done. + +

Neuere Foliierung, die auch das Vorsatzblatt mitgezählt +hat.

+

Folio numbers were added in brown ink by Árni Magnússon ca. +1720-1730 in the upper right corner of all recto-pages.

 + +

+

Where a manuscript contains traces of more than one foliation, each should be +recorded as a distinct foliation element and optionally given a +distinct value for its xml:id attribute. The locus element +discussed in can then indicate which foliation scheme is +being cited by means of its scheme attribute, which points to this +identifier: + +

Original foliation in red roman numerals in the +middle of the outer margin of each recto

+

Foliated in pencil in the top right corner of each +recto page.

 + +ff 1-20 + +

+
+
+Condition +

The condition element is used to summarize the overall physical +state of a manuscript, in particular where such information is not recorded +elsewhere in the description. It should not, however, be used to describe +changes or repairs to a manuscript, as these are more appropriately described as +a part of its custodial history (see ). It should be +supplied within the supportDesc element, if it discusses the condition +of the physical support of the manuscript; within the bindingDesc or +binding elements () if it discusses only the +condition of the binding or bindings concerned; or within the sealDesc +element if it discusses the condition of any seal attached to the +manuscript.

+ + +

The manuscript shows signs of damage from water and mould on its +outermost leaves.

 + + + +

Despite tears on many of the leaves the codex is reasonably well +preserved. The top and the bottom of f. 1 is damaged, and only a thin slip is +left of the original second leaf (now foliated as 1bis). The lower margin of f. +92 has been cut away. There is a lacuna of one leaf between ff. 193 and 194. The +manuscript ends defectively (there are approximately six leaves +missing).

 + + +
+
+Layout Description +

The second part of the objectDesc element is the layoutDesc +element, which is used to describe and document the +mise-en-page of the manuscript, that is the way in which text +and illumination are arranged on the page, specifying for example the number of +written, ruled, or pricked lines and columns per page, size of margins, distinct +textual streams such as glosses, commentaries, etc. This may be given as a simple series +of paragraphs. Alternatively, one or more different layouts may be identified +within a single manuscript, each described by its own layout element. + + +

+

Where the layout element is used, the layout will often be +sufficiently regular for the attributes on this element to convey all that is +necessary; more usually however a more detailed treatment will be required. The +attributes are provided as a convenient shorthand for commonly occurring cases, +and should not be used except where the layout is regular. The value +NA (not-applicable) should be used for cases where the layout is +either very irregular, or where it cannot be characterized simply in terms of +lines and columns, for example, where blocks of commentary and text are arranged +in a regular but complex pattern on each page

+

The following examples indicate the range of possibilities: + + +

Most pages have between 25 and 32 long lines ruled in lead.

+ + +

Written in one column throughout; 24 lines per page.

+ +

Written in 3 columns, with 8 lines of text and interlinear glosses in +the centre, and up to 26 lines of gloss in the outer two columns. Double +vertical bounding lines ruled in hard point on hair side. Text lines ruled +faintly in lead. Remains of prickings in upper, lower, and outer (for 8 lines of +text only) margins.

 + +

+

Where multiple layout elements are supplied, the scope for each +specification can be indicated by means of locus elements within the +content of the element, as in the following example: + + + +

On fols 1r-200v and fols 210r-212v there are between 25 and 32 ruled lines.

+ + +

On fols 203r-209v there are between 34 +and 50 ruled lines.

+ + +

+
+
+
+Writing, Decoration, and Other Notations +

The second group of elements within a structured physical description +concerns aspects of the writing, illumination, or other notation (notably, +music) found in a manuscript, including additions made in later hands—the +text, as it were, as opposed to the carrier. + + + + + + + + + + +

+
+Writing +

The handDesc element can contain a short description of the general +characteristics of the writing observed in a manuscript, as in the following +example: + + +

Written in a late Caroline minuscule; versals in a form of +rustic capitals; although the marginal and interlinear gloss is +written in varying shades of ink that are not those of the main text, text and +gloss appear to have been copied during approximately the same time span.

+ + +

+

Note the use of the term element to mark specific technical terms +within the context of the handDesc element.

+

Where several distinct hands have been identified, this fact can be +registered by using the hands attribute, as in the following example: + + +

The manuscript is written in two contemporary hands, otherwise unknown, but +clearly those of practised scribes. Hand I writes ff. 1r-22v and hand II ff. 23 +and 24. Some scholars, notably Verner Dahlerup and Hreinn Benediktsson, have +argued for a third hand on f. 24, but the evidence for this is +insubstantial.

+ + +

+

Alternatively, or in addition, where more specific information about one or +more of the hands identified is to be recorded, the handNote element +should be used, as in the following example: + + + +

The first part of the manuscript, fols +1v-72v:4, is written in a practised Icelandic Gothic bookhand. This hand +is not found elsewhere.

+ +

The second part of the manuscript, fols +72v:4-194, is written in a hand contemporary with the first; it can also +be found in a fragment of Knýtlinga saga, AM 20b II +fol..

 + +

The third hand has written the majority of the chapter headings. This hand +has been identified as the one also found in AM 221 +fol..

 + + + Note here the use of the locus element, discussed in section , to specify exactly which parts of a manuscript are written by +a given hand.

+

When a full or partial transcription of a manuscript is available in addition +to the manuscript description, the handShift element described in can be used to link the relevant parts of the transcription to +the appropriate handNote element in the description: for example, at +the point in the transcript where the second hand listed above starts (i.e. at +folio 72v:4), we might insert handShift new="#Eirsp-2"/.

+

Additions, notes, drawings etc. (e.g. add, note and figure) made by other hands + in the text, can be linked to the corresponding handNote element using the hand attribute.

+

The elements typeDesc, and typeNote are used to provide +information about the printing of a source, in exactly the same way as the +handDesc or handNote elements provide information about its +writing. They are provided for the convenience of those using this module to +provide information about early printed sources and incunables. The +typeDesc element can simply provide a summary description: + +

Uses a mixture of Roman and Black Letter types.

+ +

+

Where detailed information about individual typefaces is to be recorded, this +may be done using the typeNote element: + +

Uses a mixture of Roman and Black Letter types. +Antiqua typeface, showing influence of Jenson's Venetian +fonts. +The black letter face is a variant of Schwabacher. + + +

+

Where information is required about both typography and written script, for +example where a printed book contains extensive handwritten annotation, both +handDesc and typeDesc elements should be supplied. Similarly, +in the following example, the source text is a typescript with extensive +handwritten annotation: + + +Authorial typescript, probably produced on Eliot's own +Remington. + + +Ezra Pound's annotations. +Commentary in Eliot's hand. + + +

+

The elements scriptNote and scriptDesc may be used in +exactly the same way to document a script used in this and other manuscripts, +for example to record that this script was used mainly for the production of +books or for charters; or that it is characteristic of some geographical area or +scriptorium or date. Such information as the letter forms characteristic of this +script may also be recorded. By contrast, the handNote element would be +used to document the way that a particular scribe uses a script, for example +with long or short descenders, or using a pen which is cut in a different way, +or an ink of a given colour, and so forth.

+

As with typeNote, the scriptNote element can be used in +combination with handNote.

+
+
+Decoration +

It can be difficult to draw a clear distinction between aspects of a +manuscript which are purely physical and those which form part of its +intellectual content. This is particularly true of illuminations and other forms +of decoration in a manuscript. We propose the following elements for the purpose +of delimiting discussion of these aspects within a manuscript description, and +for convenience locate them all within the physical description, despite the +fact that the illustrative features of a manuscript will in many cases also be +seen as constituting part of its intellectual content.

+

The decoDesc element may contain simply one or more paragraphs +summarizing the overall nature of the decorative features of the manuscript, as +in the following example: + + +

The decoration comprises two full page miniatures, perhaps added by the +original owner, or slightly later; the original major decoration consists of +twenty-three large miniatures, illustrating the divisions of the Passion +narrative and the start of the major texts, and the major divisions of the +Hours; seventeen smaller miniatures, illustrating the suffrages to saints; and +seven historiated initials, illustrating the pericopes and major prayers.

+ + + Alternatively, it may contain a series of more specific typed decoNote +elements, each summarizing a particular aspect or individual instance of the +decoration present, for example the use of miniatures, initials (historiated or +otherwise), borders, diagrams, etc., as in the following example: + + + +

One full-page miniature, facing the beginning of the first Penitential +Psalm.

+ + +

One seven-line historiated initial, commencing the first Penitential +Psalm.

+ + +

Six four-line decorated initials, commencing the second through the seventh +Penitential Psalm.

+ + +

Some three hundred two-line versal initials with pen-flourishes, commencing +the psalm verses.

+ + +

Four-sided border decoration surrounding the miniatures and three-sided +border decoration accompanying the historiated and decorated initials.

+ + + +

+

Where more exact indexing of the decorative content of a manuscript is +required, the standard TEI elements term or index may be used +within the prose description to supply or delimit appropriate iconographic +terms, as in the following example: + + + +

Fourteen large miniatures with arched tops, above five lines of text: +fol. 14rPericopes. St. John writing on Patmos, +with the Eagle holding his ink-pot and pen-case; some flaking of pigment, +especially in the sky +fol. 26rHours of the Virgin, Matins. +Annunciation; Gabriel and the Dove to the right +fol. 60rPrime. Nativity; the Virgin and +Joseph adoring the Child +fol. 66rTerce. Annunciation to the Shepherds, +one with bagpipes + +

+ + + +

+
+
+Musical Notation +

Where a manuscript contains music, the musicNotation element may be +used to describe the form of notation employed, as in the following examples: + + +

Square notation on 4-line red staves.

+ + + +

Neumes in campo aperto of the St. Gall type.

+ + +

If a manuscript employs more than one notation, they must both be described within the +same musicNotation element, for example as different list items.

+
+
+Additions and Marginalia +

The additions element can be used to list or describe any additions +to the manuscript, such as marginalia, scribblings, doodles, etc., which are +considered to be of interest or importance. Such topics may also be discussed or +referenced elsewhere in a description, for example in the history +element, in cases where the marginalia provide evidence of ownership. Note that +this element may not be repeated within a single manuscript description. If +several different kinds of additional matter are discussed, the content may be +structured as a labelled list or a series of paragraphs. Some examples follow: + +

Doodles on most leaves, possibly by children, and often quite +amusing.

+ +

Quelques annotations marginales des XVIe et XVIIe s.

 + + +

The text of this manuscript is not interpolated with sentences from Royal +decrees promulgated in 1294, 1305 and 1314. In the margins, however, another +somewhat later scribe has added the relevant paragraphs of these decrees, see +pp. 8, 24, 44, 47 etc.

+

As a humorous gesture the scribe in one opening of the manuscript, pp. 36 and +37, has prolonged the lower stems of one letter f and five letters þ and has +them drizzle down the margin.

+ + + +

Spaces for initials and chapter headings were left by the scribe but not +filled in. A later, probably fifteenth-century, hand has added initials and +chapter headings in greenish-coloured ink on fols 8r, +8v, 9r, 10r and 11r. +Although a few of these chapter headings are now rather difficult to read, most +can be made out, e.g. fol. 8rb +floti astridar; fol. +9rb +vm olaf conung, and fol. +10ra +Gipting olafs +konungs.

+

The manuscript contains the following marginalia: +Fol. 4v, left margin: hialmadr +ok +brynjadr, in a fifteenth-century hand, imitating an addition made +to the text by the scribe at this point. +Fol. 5r, lower margin: þetta +þiki mer vera gott blek ennda kann ek icki +betr sia, in a fifteenth-century hand, probably the same as that on the +previous page. +Fol. 9v, bottom margin: þessa bok +uilda eg gæt lært med +an Gud gefe myer Gott ad +læra; seventeenth-century hand. +

+

There are in addition a number of illegible scribbles in a later hand (or +hands) on fols 2r, 3r, 5v and +19r.

+ + +

+
+
+
+Bindings, Seals, and Additional Material +

The third major component of the physical description relates to supporting +but distinct physical components, such as bindings, seals and accompanying +material. These may be described using the following specialist elements: + + + + + +

+
+Binding Descriptions +

The bindingDesc element contains a description of the state of the +present and former bindings of a manuscript, including information about its +material, any distinctive marks, and provenance information. This may be given +as a series of paragraphs if only one binding is being described, or as a series +of distinct binding elements, each describing a distinct binding where +these are separately described. For example: + + +

Sewing not visible; tightly rebound over 19th-century pasteboards, reusing +panels of 16th-century brown leather with gilt tooling à la fanfare, Paris c. +1580-90, the centre of each cover inlaid with a 17th-century oval medallion of +red morocco tooled in gilt (perhaps replacing the identifying mark of a previous +owner); the spine similarly tooled, without raised bands or title-piece; +coloured endbands; the edges of the leaves and boards gilt. Boxed.

+ + +

+

Within a binding description, the elements decoNote and +condition are available, as alternatives to p, for paragraphs +dealing exclusively with information about decorative features of a binding, or +about its condition, respectively. + +

Bound, s. XVIII (?), in diced russia leather +retaining most of the original 15th century metal ornaments (but with some +replacements) as well as the heavy wooden boards.

+

On each cover: alternating circular stamps of the Holy Monogram, a +sunburst, and a flower.

 +

On the cornerpieces, one of which is missing, a rectangular stamp +of the Agnus Dei.

 +Front and back leather inlaid panels very badly worn. +

Rebacked during the 19th century.

+ + +

+

As noted above, () the element condition may +also be used as an alternative to p for paragraphs concerned +exclusively with the condition of a binding, where this has not been supplied as +part of the physical description.

+
+
+Seals +

The sealDesc element supplies information about the seal(s) attached +to documents to guarantee their integrity, or to show authentication of the +issuer or consent of the participants. It may contain one or more paragraphs +summarizing the overall nature of the seals, or may contain one or more +seal elements. + + + +

Round seal of Anders Olufsen in black wax: DAS +930. Parchment tag, on which is written: pertinere nos +predictorum placiti nostri iusticarii precessorum dif.

+ +

The seal of Jens Olufsen in black wax: DAS +1061. Legend: S IOHANNES OLAVI. Parchment tag on +which is written: Woldorp Iohanne G.

+ + + +

+
+
+Accompanying Material +

The circumstance may arise where material not originally part of a manuscript +is bound into or otherwise kept with a manuscript. In some cases this material +would best be treated in a separate msPart element (see below). There are, however, cases where the additional matter +is not self-evidently a distinct manuscript: it might, for example, be a set of +notes by a later scholar, or a file of correspondence relating to the +manuscript. The accMat element is provided as a holder for this kind of +information. + +

+

Here is an example of the use of this element, describing a note by the +Icelandic manuscript collector Árni Magnússon which has been bound with the +manuscript: + + +

A slip in Árni Magnússon's hand has been stuck to the pastedown on the inside +front cover; the text reads: Þidreks Søgu þessa hefi eg +feiged af Sekreterer Wielandt Anno 1715 i Kaupmanna høfn. Hun er, sem eg sie, +Copia af Austfirda bókinni (Eidagás) enn ecki progenies Brædratungu +bokarinnar. Og er þar fyrer eigi i allann máta samhlioda +þeirre er Sr Jon Erlendz son hefer ritad fyrer Mag. Bryniolf. Þesse +Þidreks Saga mun vera komin fra Sr Vigfuse á Helgafelle.

+ + +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+History +

The following elements are used to record information about the history of a +manuscript: + + + + +

+

The three components of the history element all have the same +substructure, consisting of one or more paragraphs marked as p +elements. Each of these three elements is also a member of the att.datable attribute class, itself a member of the att.datable.w3c class, and thus also carries the following +optional attributes: + +

+

Information about the origins of the manuscript, its place and date of +writing, should be given as one or more paragraphs contained by a single +origin element; following this, any available information on distinct +stages in the history of the manuscript before its acquisition by its current +holding institution should be included as paragraphs within one or more +provenance elements. Finally, any information specific to the means by +which the manuscript was acquired by its present owners should be given as +paragraphs within the acquisition element.

+

Here is a fairly simple example of the use of this element: + + +

Written in Durham during the mid-twelfth +century.

+

Recorded in two medieval catalogues of the books belonging to +Durham Priory, made in 1391 and +1405.

 +

Given to W. Olleyf by William Ebchester, Prior (1446-56) and later belonged to +Henry Dalton, Prior of Holy Island (Lindisfarne) according to inscriptions on ff. 4v and 5.

+ +

Presented to Trinity College in +1738 by Thomas Gale and his son Roger.

 + + +

+

Here is a fuller example, demonstrating the use of multiple +provenance elements where distinct periods of ownership for the +manuscript have been identified: + + + Written in Spain or Portugal in the +middle of the 13th century (the date 1042, given in a marginal note on f. 97v, +cannot be correct.) +The Spanish scholar Benito Arias Montano +(1527-1598) has written his name on f. 97r, and may be presumed to have owned +the manuscript. +It came somehow into the possession of etatsråd +Holger Parsberg (1636-1692), who has written his name +twice, once on the front pastedown and once on f. 1r, the former dated +1680 and the latter 1682. +Following Parsberg's death the manuscript was bought by +etatsråd +Jens Rosenkrantz (1640-1695) when Parsberg's library +was auctioned off (23 October 1693). +The manuscript was acquired by +Árni Magnússon from the estate of Jens Rosenkrantz, presumably at auction (the +auction lot number 468 is written in red chalk on the flyleaf), either in 1696 +or 97. + + +

+ + + + + + +
+
+ Additional Information +

Three categories of additional information are provided for by + the scheme described here, grouped together within the + additional element described in this section. + + + + + +

+

None of these specialized constituent elements of +additional is required. If any is supplied, it may appear +once only; furthermore, the order in which elements are supplied +should be as specified above. Alternatively, additional information may be +provided as either one or more paragraphs or anonymous blocks, marked up as +a series of p or ab elements.

+ + + +
+Administrative Information +

The adminInfo element is used to hold information relating to the +curation and management of a manuscript. This may be supplied as a note using +the global note element. Alternatively, different aspects of this +information may be presented grouped within one of the following +specialized elements: + + + +

+
+Record History +

The recordHist element may contain simply a series of paragraphs. +Alternatively it may contain a source element, followed by an optional +series of change elements. + + +

+

The source element is used to document the primary source of +information for the record containing it, in a similar way to the standard TEI +sourceDesc element within a TEI Header. If the record is a new one, +made without reference to anything other than the manuscript itself, then it may +simply contain a p element, as in the following example: + +

Directly catalogued from the original manuscript.

+ +

+

Frequently, however, the record will be derived from some previously existing +description, which may be specified using the standard TEI bibl +element, as in the following example: + + +

Information transcribed from The index of Middle English +verse123.

+ + +

+

If, as is likely, a full bibliographic description of the source from which +cataloguing information was taken is included within the listBibl +element contained by the current additional element, or elsewhere in +the current document, then it need not be repeated here. Instead, it should be +referenced using the standard TEI ref element, as in the following +example: + + + + +

Information transcribed from IMEV +123.

+ + + + + +Carleton Brown and Rossell Hope Robbins +The index of Middle English verse +New York +1943 + + + + + +

+

The change element may also appear within the revisionDesc +element of the standard TEI header; its use here is intended to signal the +similarity of function between the two container elements. Where the TEI header +should be used to document the revision history of the whole electronic file to +which it is prefixed, the recordHist element may be used to document +changes at a lower level, relating to the individual description, as in the +following example: + +On 10 March 2005 MJD added provenance +information + +

+
+
+Availability and Custodial History +

The availability element is another element also available in the +TEI header, which should be used here to supply any information concerning +access to the current manuscript, such as its physical location (where this is +not implicit in its identifier), any restrictions on access, information about +copyright, etc. + + +

Viewed by appointment only, to be arranged with curator.

+ + +

In conservation, Jan. - Mar., 2002. On loan to the Bayerische +Staatsbibliothek, April - July, 2002.

+ + +

The manuscript is in poor condition, due to many of the leaves being brittle +and fragile and the poor quality of a number of earlier repairs; it should +therefore not be used or lent out until it has been conserved.

+ + +

+

The custodialHist record is used to describe the custodial history +of a manuscript, recording any significant events noted during the period that +it has been located within its holding institution. It may contain either a +series of p elements, or a series of custEvent elements, each +describing a distinct incident or event, further specified by a type +attribute, and carrying dating information by virtue of its membership in the +att.datable class, as noted above. + +

+

Here is an example of the use of this element: + + + +

Conserved between March 1961 and February 1963 at Birgitte Dalls +Konserveringsværksted.

+ +

Photographed in May 1988 by AMI/FA.

 + +

Dispatched to Iceland 13 November 1989.

 + + +

+ + + + + + + + +
+
+
+Surrogates +

The surrogates element is used to provide information about +representations such as photographs or other representations of the manuscript +which may exist within the holding institution or elsewhere. + +

+

The surrogates element should not be used to repeat information +about representations of the manuscript available within published works; this +should normally be documented within the listBibl element within the +additional element. However, it is often also convenient to record +information such as negative numbers or digital identifiers for unpublished +collections of manuscript images maintained within the holding institution, as +well as to provide more detailed descriptive information about the surrogate +itself. Such information may be provided as prose paragraphs, within which +identifying information about particular surrogates may be presented using the +standard TEI bibl element, as in the following example: + + +microfilm (master)G.neg. 160 +n.d. +microfilm (archive)G.pos. 186 +n.d. +b/w printsAM 795 4to +27 January 1999copy of G.pos. +186 +b/w printsreg.nr. 75 +25 January 1999 +photographs of the spine, outside covers, stitching etc. + + + + Note the use of the specialized form of title (general material +designation) to specify the kind of surrogate being documented.

+

At a later revision, the content of the surrogates element is likely +to be expanded to include elements more specifically intended to provide +detailed information such as technical details of the process by which a digital +or photographic image was made. For information about the inclusion of digital +facsimile images within a TEI document, refer also to .

+ + + +
+
+
+Manuscript Parts +

The msPart element may be used in cases where manuscripts or parts +of manuscripts that were originally physically separate have been bound together +and/or share the same call number. + +

+

Since each component of such a composite manuscript will in all likelihood +have its own content, physical description, history, and so on, the structure of +msPart is in the main identical to that of msDesc, allowing +one to retain the top level of identity (msIdentifier), but to branch +out thereafter into as many parts, or even subparts, as necessary. + + + + + + + + +Brussels +Koninklijke Bibliotheek van België / Bibliothèque royale de +Belgique +ms. 10066-77 + +

Miscellany of various texts; Prudentius, +Psychomachia; Physiologus de natura animantium +Latin + + + + + +ms. 10066-77 ff. 140r-156v + +Physiologus +Latin + + + +ms. 10066-77 ff. 112r-139r + + +Prudentius, Psychomachia +Latin + + + + +

+ + + +
+
+Manuscript Fragments +

The msFrag element may be used inside msDesc when encoding +one or more fragments of a scattered or fragmented manuscript. The fragment(s) +described in a single msDesc element may be held either at several +institutions or at a single institution, so different call numbers may be +attached to the fragments. Inside the msFrag element, information about +the single fragment or each dispersed part is provided: e.g. the current +shelfmark or call number, the labels of the range of folios concerned if the +fragment currently forms part of a larger manuscript, dimensions, extent, title, +author, annotations, illuminations and so on. + +

+

One well-known example of fragmentation is the Old Church Slavonic manuscript +known as Codex Suprasliensis, substantial parts of which are to +be found in three separate repositories, in Ljubljana, Warsaw, and St. +Petersburg. This manuscript should be represented using one single +msDesc element in which msName is used to identify the +fragmented manuscript, along with three distinct msFrag elements, each +of which contains the current identifier of one of the fragments, a physical +description, and other related information: + + + +Codex Suprasliensis + + + +Ljubljana +Narodna in univerzitetna knjiznica +MS Kopitar 2 + + +

Contains ff. 10 to 42 only + + + + +Warszawa +Biblioteka Narodowa +BO 3.201 + + + + +Sankt-Peterburg +Rossiiskaia natsional'naia biblioteka +Q.p.I.72 + + + + +

+ + + +
+
+ Module for Manuscript Description +

The module described in this chapter makes available the following + components: + + Manuscript Description + Manuscript Description + Description de manuscrits + 寫本描述 + Descrizione di manoscritti + Descrição do manuscrito + 手書きモジュール + + The selection and combination of modules to form a TEI schema is + described in .

+ + + + + + + + + + + + + +
+
diff --git a/P5/Source/Guidelines/fr/ND-NamesDates.xml b/P5/Source/Guidelines/fr/ND-NamesDates.xml deleted file mode 120000 index 17a3993d16..0000000000 --- a/P5/Source/Guidelines/fr/ND-NamesDates.xml +++ /dev/null @@ -1 +0,0 @@ -../en/./ND-NamesDates.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/ND-NamesDates.xml b/P5/Source/Guidelines/fr/ND-NamesDates.xml new file mode 100644 index 0000000000..7f4fd5c4b0 --- /dev/null +++ b/P5/Source/Guidelines/fr/ND-NamesDates.xml @@ -0,0 +1,3059 @@ + + + + +
+ + Names, Dates, People, and Places + +

This chapter describes a module which may be used for the encoding of names and other phrases descriptive of persons, places, + or organizations, in a manner more detailed than that possible using the elements already provided for these purposes in the + Core module. In section it was noted that the elements provided in the core module allow an encoder to + specify that a given text segment is a proper noun, or a referring string, and to specify the kind of object + named or referred to only by supplying a value for the type attribute. The elements provided by the present module + allow the encoder to supply a detailed sub-structure for such referring strings, and to distinguish explicitly between names + of persons, places, and organizations.

+ +

This module also provides elements for the representation of information about the person, place, or organization to which a + given name is understood to refer and to represent the name itself, independently of its application. In simple terms, where + the core module allows one simply to represent that a given piece of text is a name, this module allows one + further to represent a personal name, to represent the person being named, and to represent the + canonical name being used. A similar range is provided for names of places and organizations. The main intended + applications for this module are in biographical, historical, or geographical data systems such as gazetteers and biographical + databases, where these are to be integrated with encoded texts.

+ +

The chapter begins by discussing attributes common to many of the elements discussed in the remaining parts of the chapter + () before discussing specifically the elements provided for the encoding of component parts of + personal names (section ), place names (section ) and organizational names + (section ). Elements for encoding personal and organizational data are discussed in section . Elements for the encoding of geographical data are discussed in section . + Finally, elements for encoding onomastic data are discussed in , and the detailed encoding of dates and + times is described in section .

+ + + +
+ Attribute Classes Defined by This Module +

Most of the elements made available by this chapter share some important characteristics which are expressed by their + membership in specific attribute classes. Members of the class att.naming have specialized + attributes which support linkage of a naming element with the entity (person, place, organization) being named; members of + the class att.datable have specialized attributes which support a number of ways of normalizing + the date or time of the data encoded by the element concerned.

+ +
+ Linking Names and Their Referents + +

The class att.naming is a subclass of the class att.canonical, + from which it inherits the following attributes: + + As discussed in , these attributes provide two different ways of associating any sort + of name with its referent. For cases where all that is required is to provide some minimal information about the person + name, for example their occupation or status, the att.naming class also provides a simple + role attribute. It also provides an additional attribute, which allows the name itself to be associated with + a base or canonical form: + + The encoder may use these attributes in combination as appropriate. For example: That silly man David Paul Brown + has suffered ... The ref attribute should be used wherever it is possible to supply a direct link + such as a URI to indicate the location of canonical information about the referent. That silly man David Paul Brown has + suffered ... This encoding requires that there exist somewhere a person element with the identifier + DPB1, which will contain canonical information about this particular person, marked up using the elements + discussed in below. The same element might alternatively be provided by some other document, of + course, which the same attribute could refer to by means of a URI, as explained in : That silly man David Paul Brown has suffered ...More than one URI may be supplied if the name refers to + more than one person. For example, assuming the existence of another person element for Mrs Brown, with + identifier EBB1, a reference to the Browns might be encoded That wretched pair the Browns came + to dine ... +

+ +

The key attribute is provided for cases where no such direct link is required: for example because resolution + of the reference is carried out by some local convention, or because the encoder judges that no such resolution is + necessary. As an example of the first case, a project might maintain its own local database system containing canonical + information about persons and places, each entry in which is accessed by means of some system-specific identifier + constructed in a project-specific way from the value supplied for the key attribute.In the + module described by chapter a similar method is used to link element descriptions to the modules or + classes to which they belong, for example. As an example of the second case, consider the use of well-established + codifications such as country or airport codes, which it is probably unnecessary for an encoder to expand further: I never fly from Heathrow Airport to France +

+ +

However, as explained in , interchange is improved by use of tag URIs in ref instead of + key.

+ +

The nymRef attribute has a more specialized use, where it is the name itself which is of interest rather than + the person, place, or organization being named. See section for further discussion.

+ +

All members of the att.naming class inherit the following attributes from the att.global.responsibility class: + + This enables an encoder to record the agency responsible for a given assertion (for example, the name) and the + confidence placed in that assertion by the encoder. Examples are given below.

+
+ +
+ Dating Attributes + +

Members of the att.datable class share the following attributes: + + + +

+

The when attribute is used to specify a normalized form for any temporal expression, independently of how it + is represented in the text, as in the following example: June 9th The period is approaching which will terminate my present + copartnership. On the 1st Jany. next, it expires by its own limitation. +

+

The period attribute provides a convenient way of associating an event or date with a named period. Its value + is a pointer which should indicate some other element where the period concerned is more precisely defined. A convenient + location for such definitions is the taxonomy element in the classDecl (classification declaration) in + the encodingDesc of a TEI header. A taxonomy may contain simply a bibliographic reference to an external + definition for it. More usefully, it may also contain a series of category elements, each with an identifier and + a description. The identifier can then be used as the target for a period attribute. For example, a taxonomy of + named periods might be defined as follows: + + + Before 510 BC + + Between 510 and 323 BC + + + Hellenistic. Commonly treated as from the death of Alexander to the Roman conquest. + + + + + Roman + + + + The Christian period technically starts at the birth of Jesus, but in practice is considered to date from + the conversion of Constantine in 312 AD. + + + +

+

With these definitions in place, any datable element may be associated with a specific period: + Stauropolis

+

The other dating attributes provided by this class support a wide range of methods of specifying temporal information in + a normalized form. The from and to attributes may be used to express the begining and ending of a + period of time, for example: + + + A political and social protest campaign against the policy of racial segregation on the public transit system of + the city of Montgomery. + +

+

The notBefore and notAfter attributes may be used to express a range of possibilities for a + particular date (or time). For example the following element, extracted from an imaginary prosopographic entry for Anne + Calthorpe, indicates that although the exact date of her death is not known, it can be narrowed down to a particular + range: from 22 August 1579 to 28 March 1582, inclusive. Ostensibly the encoder has evidence that Anne Calthorpe was alive + on the 22nd of August 1579 and evidence that she was already dead on the 28th of March 1582. + +

+

Since when is used for a particular date or time, from and to for a duration, and + notBefore and notAfter for a date or time within a range, it makes no sense to use when + in combination with one or more of the others. Thus these Guidelines at present recommend against the use of + when in combination with any of from, to, notBefore, or + notAfter.

+

The from or to attributes imply that the temporal expression to which they are attached signifies a + duration, so the use of either with notBefore or notAfter means a duration is indicated. + + + notBefore + from + + + notAfter + range of possibilities, inclusive + duration from from to sometime before + notAfter, inclusive + + + to + duration from sometime after notBefore to + to, inclusive + duration from from to to, inclusive + +
+

+ + +

Some further self-explanatory examples follow: + 15 March 1857. + + + Some time in March or April of 1857. + + + Lived in Amsterdam during March and April of 1857. + + + From the 1st of March to some time later in March or April of 1857. + + + From the 1st of March or sometime later to the end of April, + 1857. + + + From sometime in March of 1856 to sometime in April of 1858. + +

+

Normalization of date and time values permits the efficient processing of data (for example, to determine whether one + event precedes or follows another). These examples all use the W3C standard format for representation of dates and times. + Further examples, and discussion of some alternative approaches to normalization are given in section below.

+ +
+ +
+ +
+ Names + +
+ Personal Names + +

The core rs and name elements can distinguish names in a text but are insufficiently powerful to mark + their internal components or structure. To conduct nominal record linkage or even to create an alphabetically sorted list + of personal names, it is important to distinguish between a family name, a forename and an honorary title. Similarly, when + confronted with a string such as John, by the grace of God, king of England, lord of Ireland, duke of Normandy and + Aquitaine, and count of Anjou, the analyst will often wish to distinguish amongst the various constituent elements + present, since they provide additional information about the status, occupation, or residence of the person to whom the + name belongs. The following elements are provided for these and related purposes: + + + + + + + + +

+ +

In addition to the att.naming attributes mentioned above, all of the above elements are + members of the class att.personal, and thus share the following attributes: + + +

+

The persName element may be used in preference to the general name element irrespective of whether or + not the components of the personal name are also to be marked. + The + element persName is synonymous with the element name type="person", except that its type + attribute allows for further subcategorization of the personal name itself, for example as a married, + birth, pen, pseudo, or religious name. Consequently the following examples + are equivalent: That silly man David Paul Brown has suffered the furniture of his office to be seized the third time for + rent. + That silly man + David Paul Brown + has suffered ... + That silly man David Paul Brown has suffered ... + That silly man David Paul + Brown has suffered ... +

+

The persName element is more powerful than the rs and name elements because distinctive name + components occurring within it can be marked as such.

+

Many cultures distinguish between a family or inherited surname and additional personal names, often known + as given names. These should be tagged using the surname and forename elements respectively + and may occur in any order: + Roosevelt, Franklin + Delano + + + Franklin + Delano + Roosevelt + +

+

The type attribute may be used with both forename and surname elements to provide further + culture- or project-specific detail about the name component, for example: + Franklin + Delano + Roosevelt + + + Margaret + Hilda + Roberts + Thatcher + + Muhammad Ali + + Norman + St John Stevas + + Values for the type attribute are not constrained, and may be chosen as appropriate to the encoding + needs of the project. They may be used to distinguish different kinds of forename or surname, as well as to indicate the + function a name component fills within the whole. In this example, we indicate that a surname is toponymic, and also point + to the specific place name from which it is derived: + + Johan + Dystvold + + + Dystvold + +

+ +

The value complex was suggested above for the not uncommon case where the whole of a surname is composed of + several other surname elements. These nested surnames may be individually tagged as well, together with appropriate type + values: + Kara + + Hattersley- Smith + + +

+

The full attribute may be used to indicate whether a name is an abbreviation, initials, or given in full: + + Maggie + Thatcher + +

+ +

These elements may be applied as the encoder considers appropriate, including cases where phrases or expressions are used + to stand for surnames or forenames, as in the following: + Peter + son of Herbert gives the king 40 m. for having custody of the land and heir of + John + son of Hugh... +

+ +

Similarly, patronymics may be treated as forenames, thus: ... but it remained for + Snorri + Sturluson + to combine the two traditions in cyclic form. When a patronymic is used as a surname, however (e.g. + by an individual who otherwise would have no surname, but lives in a culture which requires surnames), it may be tagged as + such: Even Finnur + Jonsson acknowledged the artificiality of the procedure... Alternatively, it may + be felt more appropriate to mark a patronymic as a distinct kind of name, neither a forename nor a surname, using the + addName element: + + Egill + Skallagrmsson + + In the following example, the type attribute is used to distinguish a patronymic from other forenames: + + Sergei + Mikhailovic + Uspensky + +

+ + +

This example also demonstrates the use of the sort attribute common to all members of the model.persNamePart class; its effect is to state the sequence in which forename and surname + elements should be combined when constructing a sort key for the name.

+

Some names include generational or dynastic information, such as a number, or phrases such as Junior, or the + Elder; these qualifications may also be used to distinguish similarly named but unrelated people. In either case, + the genName element may be used to distinguish such labels from other parts of the name, as in the following + examples: + Marques + Junior, Henrique + + + Charles + II + + + Rudolf + II + von Habsburg + + + Smith + Minor + +

+

It is also often convenient to distinguish phrases (historically similar to the generational labels mentioned above) used + to link parts of a name together, such as von, of, de etc. It is often a matter of arbitrary choice + whether such components are regarded as part of the surname or not; the nameLink element is provided as a means + of making clear what the correct usage should be in a given case, as in the following examples: + Mme + de la + Rochefoucault + + + Walter + de la Mare + +

+

Finally, the addName and roleName elements are used to mark all name components other than those + already listed. The distinction between them is that a roleName encloses an associated name component such as an + aristocratic or official title which exists in some sense independently of its bearer. The distinction is not always a + clear one. As elsewhere, the type attribute may be used with either element to supply culture- or application- + specific distinctions. Some typical values for this attribute for names in the Western European tradition follow: + + An inherited or life-time title of nobility such as Lord, Viscount, + Baron, etc. + + An academic or other honorific prefixed to a name e.g. Doctor, + Professor, Mrs., etc. + + Membership of some elected or appointed organization such as President, + Governor, etc. + + Military rank such as Colonel. + + A traditional descriptive phrase or nick-name such as The Hammer, The + Great, etc. + Note, however, that the role a person has in a given context (such as witness, + defendant, etc. in a legal document) should not be encoded using the roleName element, + since this is intended to mark roles which function as part of a person's name, not the role of the person bearing the + name in general. Information about roles, occupations, etc. of a person are encoded within the person element + discussed below in .

+

Here are some further examples of the usage of these elements: + Princess + Grace + + + Grandma + Moses + + + President + Bill + Clinton + + + Colonel + Gaddafi + + + Frederick + the Great + +

+

A name may have any combination of the above elements: + Governor + Edmund + G. + Jerry + Moonbeam + Brown + Jr. +

+

Although highly flexible, these mechanisms for marking personal name components will not cater for every personal name, + nor for every processing need. Where the internal structure of personal names is highly complex or where name components + are particularly ambiguous, feature structures are recommended as the most appropriate mechanism to mark and analyze them, + as further discussed in chapter .

+ +

White space is allowed and therefore significant between elements within name, persName, + orgName, and placeName. Therefore + Mary + Ann + DeMint + ]]> encodes Mary Ann DeMint and + MaryAnn + De + Mint + ]]> encodes MaryAnn De Mint. See for more information on whitespace in XML.

+
+ +
+ Organizational Names +

In these Guidelines, we use the term organization for any named collection of people regarded as a single unit. + Typical examples include institutions such as Harvard College or the BBC and + businesses such as Apple or Google but also racial or ethnic groupings or + political factions where these are regarded as forming a single agency such as the Scythians or + the Militant Tendency. Giving a loosely-defined group of individuals a name often serves a + particular political or social agenda and an analysis of the way such phrases are constructed and used may therefore be of + considerable importance to the social historian, even where the objective existence of an organization in this + sense is harder to demonstrate than that of (say) a named person. In the case of businesses or other formally constituted + institutions, the component parts of an organizational name may help to characterize the organization in terms of its + perceived geographical location, ownership, likely number of employees, management structure, etc.

+ +

Like names of persons or places, organizational names can be marked up as referring strings or as proper names with the + rs or name elements respectively. The element orgName is provided for use where it is desired + to distinguish organizational names more explicitly. + + This element is a member of the same attribute classes as persName, as discussed above in .

+

The orgName element may be used to mark up any form of organizational name: About a year back, a question of considerable interest + was agitated in the Pennsyla. Abolition + Society This encoding is equivalent to, but more specific than, either of the following + representations: About a year back, a question of considerable interest + was agitated in the + Pennsyla. Abolition Society. + About a year back, a question of considerable interest was agitated in the + Pennsyla. Abolition Society. As shown above, like + the rs and name elements, the orgName element has a key attribute with which an + external identifier such as a database key can be assigned to the organization name, and also a ref attribute + which can be used to point directly to an org element containing information about the organization itself (see + further ). Its type attribute should be used to characterize the name (rather than the + organization), for example as an acronym: Mr Frost will be able to earn an + extra fee from BSkyB rather than the BBC + as a phrase: The feeling in + Canada is one of strong aversion to the United States Government, + and of predilection for self-government under the English Crown + + The Justified Ancients of Mu Mu + or as a composite of other kinds of name: + + Ernst & Young + +

+

The components of an organization's name may include place names as well as personal names: A spokesman from + IBM + UK + said ... or role names: THE TICKET which you will + receive herewith has been formed by the Democratic Whig party + after the most careful deliberation, with a reference to all the great objects of NATIONAL, STATE, COUNTY and + CITY concern, and with a single eye to the Welfare and Best Interests of the Community. +

+

As indicated above, organizational names may also be specified hierarchically particularly where the named organization + is itself a department or a branch of a larger organizational entity. The Department of Modern History, Glasgow + University is an example: + Department of Modern History + Glasgow + University + + +

+ +

+ + + + + + + + + + +

+
+ +
+ Place Names +

Like other proper nouns or noun phrases used as names, place names can simply be marked up with the rs element, + or with the name element. For cartographers and historical geographers, however, the component parts of a place + name provide important information about the relation between the name and some spot in space and time. They also provide + important evidence in historical linguistics.

+

These Guidelines distinguish three ways of referring to places. A place name (represented using the placeName + element) may consist of one or more names for hierarchically-organized geo-political or administrative units (see section + ). A place named simply in terms of geographical features such as mountains or rivers is + represented using the geogName element (see section ). Finally, an expression consisting + of phrases expressing spatial or other kinds of relationship between other kinds of named place may itself be regarded as + a way of referring to a place, and hence as a kind of named place (see section ). + + + +

+

As members of the att.naming class, all of these elements bear the attributes key, + ref, and nymRef mentioned above. These attributes are primarily useful as a means of linking a + place name with information about a specific place. Recommendations for the encoding of information about a place, as + distinct from its name, are provided in below.

+ +

Like the persName element discussed in section , the placeName element may be + regarded simply as an abbreviation for the elements name type="place" or rs type="place". The + following encodings are thus equivalent:Strictly, a suitable value such as figurative + should be added to the two place names which are presented periphrastically in the second version of this example. This + would preserve the distinction indicated by the choice of rs rather than name to encode them in the + first version of this example. + After spending some time in our modern Babylon, New York, I have proceeded to the City of Brotherly Love. + After spending some time in our modern Babylon, New York, I have proceeded + to the City of Brotherly Love. +

+
+ Geo-political Place Names +

A place name may contain text with no indication of its internal structure: Rochester, NY More usually + however, a place name of this kind will be further analysed in terms of its constitutive geo-political or administrative + units. These may be arranged in ascending sequence according to their size or administrative importance, for example: + Rochester, New York, or as a single such unit, for example Belgium. These Guidelines provide a hierarchy + of generic element names, each of which may be more exactly specified by means of a type attribute: + + + + + +

+

These elements are all members of the model.placeNamePart class, members of which may be + used anywhere that text is permitted, including within each other as in the following examples: + Rochester, New York + + + Laos, Southeast Asia + + + 6ème + Paris, + France + + +

+
+
+ Geographic Names +

Places may also be named in terms of geographic features such as mountains, lakes, or rivers, independently of + geo-political units. The geogName is provided to mark up such names, as an alternative to the + placeName element discussed above. For example: Mississippi River +

+

In addition to the usual phrase level elements, the geogName element may contain the following specialized + element: + + +

+

Where the geogFeat element is used to characterize the kind of geographic feature being named, the + name element will generally also be used to mark the associated proper noun or noun phrase: + Mississippi + River + A more complex example, showing a variety of practices, follows: The isolated ridge separates two great corridors which run from Glencoe into + Glen + Etive + , the + Lairig + Gartain + and the + Lairig + Eilde +

+

The Gaelic word lairig may be glossed as sloping hill face. The most efficient + way of including this information in the above encoding would be to create a separate nym element for this + component of the name and then point to it using the nymRef attribute, as further discussed in .

+
+
+ Relative Place Names + +

All the place name specifications so far discussed are absolute, in the sense that they + define only one place. A place may however be specified in terms of its relationship to another place, for example 10 + miles northeast of Paris or near the top of Mount Sinai. These relative place names will + contain a place name which acts as a referent (e.g. Paris and Mount Sinai). They will also contain a word + or phrase indicating the position of the place being named in relation to the referent (e.g. the top of, north + of). A distance, possibly only vaguely specified, between the referent place and the place being indicated may + also be present (e.g. 10 miles, near).

+

Relative place names may be encoded using the following elements in combination with either a placeName or a + geogName element. + + + Some examples of relative place names are: + near the top of + + Mount + Sinai + + + + 20 km + north of + Paris + If desired, the distance specified may be normalized using the unit and + quantity attributes of measure: + 11 miles + Northwest of + Providence, RI + +

+

The internal structure of place names is like that of personal names—complex and subject to an enormous amount of + variation across time and different cultures. The recommendations in this section should however be adequate for a + majority of users and applications; they may be extended using the mechanisms described in chapter + to add new elements to the existing classes. When the focus of interest is on the name components themselves, as in + place name studies for example, the elements discussed in may also be of use. Alternatively, the + meaning structure itself may be represented using feature structures ().

+

+ + + + + + + + + + + +

+
+ + +
+ +
+ Event Names + +

The eventName element is provided in parallel to + other naming mechanisms; it is intended especially for + canonical names that are used in texts to + mention specific named events, whether real or fictional. + +

On Monday, she was writing about the + 1618 Defenestration of Prague which initiated the + long war.

+ +

+

+

There are two major applications of eventName: + + to indicate names of events mentioned in transcribed text, such as in the above example; and + to indicate the names of events for which details are being provided in an event element. + +

+

For the first application, as with most other naming + elements, the eventName element is a member of the + att.canonical class, and thus the + ref (or key) attribute may be used to + refer to a an event element (about which see ) or some other data item that contains + further information about the event.

+

When used as a direct child of event, an + eventName provides one of the names of the event about + which details are being provided in its parent event. A + single event may be known by many names. All, only one, or + indeed none of these might be provided in the event used + to provide information about such an event. If more than one + eventName is used they may be differentiated by use of + type, where, or dating attributes. In cases + where multiple event elements describe events that have + the same name, the xml:id attribute of the + event or an idno, head, or + label sibling of the eventName may be used for + disambiguation and identification. Typically xml:id + or idno would be used for machine-processable + disambiguation, and either head or label for + human readers.

+

+ + + +

+
+ +
+ Object Names + +

+ +

+ +

As with other proper nouns or noun phrases used as names, the names of objects may be marked up simply with the + name element. For those working with a variety of named objects the objectName element provides more + flexibility. +

The Minster Lovell Jewel is probably the most similar to the + Alfred Jewel and was found in Minster + Lovell in Oxfordshire and is kept at the Ashmolean Museum.

+ +

+

The objectName element may be used to encode any named object whether or not this is a text-bearing object. The + use of objectName by itself does not categorize the object referenced, but this may be done further with the + type and subtype attributes or through reference to a taxonomy. Additionally, the use of + the objectName element says nothing about the physical reality of the object – that is whether it is real, + fictional, purported, or missing – and this may be one aspect that some may wish to record through the type + attribute. Where more detailed information is available for a named object the ref attribute should be used to + point to an object element or other source of information about this object. The objectName element is + intended for named objects; where an object is mentioned through a descriptive phrase but not named explicitly the + rs element should be used.

+
+ +
+ +
+ Biographical and Prosopographical Data +

This module defines a number of special purpose elements which can be used to markup biographical, historical, and + prosopographical data. We envisage a number of users and uses for these elements. For example, an encoder may be interested + in creating or converting a set of biographical records of the type found in a Dictionary of National + Biography. Another use is the creation or conversion of a database-like collection of information about a group of people, + such as the people referenced in a marked-up collection of documents, or persons who have served as informants in the + creation of spoken corpora. It is also appropriate to use these elements to register information relating to those who have + taken part in the creation of a TEI document.

+ +

To cater for this diversity, these Guidelines propose a flexible strategy, in which encoders may choose for themselves the + approach appropriate to their needs. If one were interested, for example, in converting existing DNB-type records, and + wanted to preserve the text as is, the person element (see ) could simply contain the text + of an article, placed within p elements, possibly using elements such as name or date to mark up + features of that text. For a more structured entry, however, one would extract the data and place information contained in + the text, and encode it directly using the more specific elements described in this section.

+
+ Basic Principles +

Information about people, places, organizations, and events, of whatever type, essentially comprises a series of statements or + assertions relating to: + characteristics or traits which do not, by and large, change over time + characteristics or states which hold true only at a specific time + events or incidents which may lead to a change of state or, less frequently, trait, + external resources where other information on the subject can be found. + +

+ +

Characteristics or traits are typically independent of an individual's volition + or action and can be either physical, such as hair and eye colour; or cultural, such as ethnicity and caste. + The distinction is not entirely straightforward: gender and sex can be regarded as culturally determined with physical manifestations, + interpreted based on the social hierarchies of a time and place. Also the division of humanity into different races, + formalized in the nineteenth century to organize a hierarchy of humanity on the basis of physical characteristics such as skin colour, hair type, + and skull measurements, is now recognized as a colonialist social construct.For example, see Renato G. Mazzolini's historical survey + of European empires and their unstable constructions of race. + When such a construct defined individuals' identities beyond their volition, the markup and documentation should reflect + this as a culturally-determined characteristic.

+ +

States include, for example, marital status, place of residence, and position or occupation. Such + states have a definite duration, that is, they have a beginning and an end and are typically a consequence of the + individual's own action or that of others.

+ +

Changes in state refer to life-changing or identity-changing events such as birth, marriage, or appointment + to office; such events will normally be associated with a specific date or a fairly narrow date-range. Changes in states + can also cause or be caused by changes in characteristics. Any statement or assertion about these aspects of a + person's life will be based on some source, possibly multiple sources, possibly contradictory. Taking all this into + account it follows that each such statement or assertion needs to be documentable, put into a time frame, and be + relatable to other statements or assertions.

+ +

The elements defined by the module described in this chapter may, for the most part, all be regarded as specializations + of one or other of the above three classes. Generic elements for state, trait, and event are also defined: + + + + + + + +

+ +

When developing a prosopography record of a named entity it is a common practice to refer explicitly to other resources, for example the Library of Congress Name Authority File, Virtual Internationl Authority File (VIAF), a gazetteer of places like Pleiades, or a printed book. + + + +

+

Here is a simple example: + + Rome + + 41.891775, 12.486137 + + 423025 + capital of the Roman Empire + +

+
+
+ The Person Element +

Information about a person, as distinct from references to a person, for example by name, is grouped together within a + person element. Information about a group of people regarded as a single entity (for example the + audience of a performance) may be encoded using the personGrp element. Note however that information + about a group of people with a distinct identity (for example a named theatrical troupe) should be recorded using the + org element described in section below.

+

These elements may appear only within a listPerson element, which groups such descriptions together, and + optionally also describes relationships amongst the people listed. + + + +

+ +

One or more listPerson elements may be supplied + within the standOff element (see ) or, when used to list the participants in + a linguistic interaction, within the particDesc + (participant description) element in the profileDesc + element of a TEI header. Like other forms of list, however, + listPerson can also appear within the body of a text + when the module defined by this chapter is included in a + schema.

+ +

The type attribute may be used to distinguish lists of people of different kinds where this is considered + convenient: + + + + + Adam Schiff + District Attorney for Manhattan in + seasons 1 to 10 of Law and Order. + + + Mike Logan + NYPDNew York Police + Department Detective regularly appearing in + seasons 1 to 5 of Law and Order and seasons 5 to 7 + of Law and Order: Criminal Intent. + + + Benjamin Stone + Executive Assistant District Attorney for + Manhattan in seasons 1 to 4 of Law + and Order + + + Jack McCoy + An Executive Assistant District Attorney then District + Attorney for Manhattan in seasons 5 to 10 + of Law and Order, in seasons 1, 9, 11, and 19 of + Law and Order: Special Victims Unit, and in + season 1 of Law and Order: Trial by Jury. + + + Jamie Ross + An Assistant District Attorney for + Manhattan in seasons 7 & 8 of + Law and Order, and a defense attorney in seasons + 10 & 11, and then a judge in Law and Order: Trial by + Jury. + + + Joe Fontana + NYPDNew York Police + Department Detective regularly appearing + in seasons 15 & 16 of Law and Order. + + + + + + Adam Schiff + U.S. Representative from California since 2013. + + + Mike Logan + Gridiron football player for the Pittsburgh Steelers from + 2001 to 2006. + + + Benjamin Stone + Michigan State Senator from 1968 to 1979. + + + Jack McCoy + Iowa State Representative from 1955 to 1959. + + + Jamie Ross + Broadway actor, with occasional forays into television, + from 1971 to roughly 2007. + + + Joe Fontana + A member of Canada’s House of Commons from 1987 to 2006, + and mayor of London, Ontario from 2010 to 2014. + + + + +

+ +

The person element carries several attributes. As a member of the classes att.global.responsibility, att.editLike, and att.global.source class, it carries the usual attributes for providing details about the information recorded + for that person, such as its reliability or source: + + + + In addition, a small number of very commonly used personal properties may be recorded using attributes + specific to person and personGrp: + + +

+ +

These attributes are intended for use where only a small amount of data is to be encoded in a more or less normalized + form, possibly for many person elements, for example when encoding basic facts about respondents to a questionnaire. When + however a more detailed encoding is required for all kinds of information about a person, for example in a historical + gazetteer, then it will be more appropriate to use the elements age, sex and others described elsewhere + in this chapter.

+ +

Note that the age attribute is not intended to record the person's age expressed in years, months, or other + temporal unit. Rather it is intended to record into which age bracket, for the purposes of some analysis, the person + falls. A simple (perhaps too simple to be useful) binary classification of age brackets would be child and + adult. The actual age brackets useful to various projects are likely to be varied and idiosyncratic, and thus + these Guidelines make no particular recommendation as to possible values. Instead, individual projects are recommended to + define the values they use in their own customization file, using a declaration like the following: + + + + + + + + + less than 18 years of age + + + 18 to 65 years of age + + + over 65 years of age + + + + + + The above declaration, were it properly placed in a customization file, establishes that the age + attribute of person has only three possible values, child, adult, and retired. + For more information on customization see .

+ +

The person element may contain many sub-elements, each specifying a different property of the person being + described. The remainder of this section describes these more specific elements. For convenience, these elements are + grouped into three classes, corresponding with the tripartite division outlined above: one for traits, one for states and + one for events. Each class may contain specific elements for common types of biographical information, and contains a + generic element for other, user-defined, types of information.

+

All the elements in these three classes belong to the attribute class att.datable, which + provides the following attributes: + + as discussed in above.

+ +
+ Personal Characteristics +

The model.persStateLike class contains elements describing physical or socially-constructed + characteristics, traits, or states of a person. Members of the class comprise the following specific elements: + + + + + + + + + + + + + + + + + + + All, apart from langKnowledge and persona, allow content of ordinary prose containing + phrase-level elements. + Status AB1 in the RG Classification scheme + + +

+

Encoders should take particular care to be explicit about culturally determined concepts such as nationality, ethnicity, age, + or sex/gender system that influence their markup.Following Gayle Rubin’s influential theory, + Every society also has a sex/gender system—a set of arrangements by which the biological raw material + of human sex and procreation is shaped by human, social intervention and satisfied in a conventional manner, + no matter how bizarre some of the conventions may be.. For example, when recording + personal age in different cultures, there may be different assumptions about the point from which age is reckoned. + Scholars face similar issues when marking sex and gender according to cultural systems from times and places not their own. + A statement of the practice adopted in a given encoding may usefully be provided in the editorialDecl element + discussed in .

+ +

The langKnowledge element contains either paragraphs or a number of langKnown elements; it may take a + tags attribute, which provides one or more standard codes or tags for the languages. + The langKnown element must have a tag attribute, which indicates the language with the same kind of + language tag. These language tags are discussed in detail in .

+

Furthermore, the langKnown element also has a level attribute to indicate the level of the person's + competence in the language. It is thus possible either to say: +

Speaks fluent Fulani, Wolof, and French. Some knowledge of + English.

+ or + + Fulani + Wolof + French + English + + +

+

The persona element may contain the same component elements as a person element. Its function is to + document a distinct persona assumed by the person element containing it. A person, not necessarily fictional, + may take on different personas at different times or in different situations, each persona having different personal + characteristics, such as name, age, sex, gender etc. We distinguish a persona, which is a set of characteristics associated with + one specific individual, from a role, which is a set of characteristics that many different people can assume. An actor + does not change their persona when adopting a different role, but none of the personas associated with one person can + properly be associated with another.

+ +

The persPronouns element may be used to indicate + the personal pronouns used, or assumed to be used, by the + individual being described. It is common practice in email + signatures and biographies, for people to include their + preferred personal pronouns along with their name or handle. + This allows transgender and gender variant people to express + how they wish to be identified, without having to share + their gender identity (though some do). Cisgender people + have also adopted the practice, which normalizes the idea + that a person's personal pronouns should not be inferred by + their name, sex, gender, or gender presentation. The + persPronouns element may be used either in + transcribed content to encode a phrase used to indicate + preferred personal pronouns, or may be used inside a + person or persona element to indicate + the associated pronouns.

+ +

For example, the following entry from a hypothetical + prosopography lists only the nominative case of the + preferred pronouns as identified by Miss Major + Griffin-Gracy, a historical figure. + + + + + + Miss Major + Griffin-Gracy + + + trans woman + + +

Veteran of the Stonewall Riots. Founder of the + Griffin-Gracy Educational Retreat and Historical + Center (the House of GG). Activist and advocate for + transgender and gender-nonconforming people of + color.

+ + + +

+

Personal pronouns often occur as part of the closer of an + email, post, or other electronic communication. + + +

+ Dear all, +

With apologies for length. I'm expanding a schema …

+ + + Diane Jakacki, Ph.D. + Digital Scholarship Coordinator + Affiliate Faculty in Comparative & Digital Humanities + Bucknell University + d…@….edu + (she/her/hers) + + Principal Investigator, + LAB Cooperative and REED London Online + Chair, ADHO Conference Coordinating Committee + +
+

+

The sex and gender elements each carry a value attribute to give values from a project-internal taxonomy, or an + external standard. + female + woman + As elsewhere, these coded values may be used as an alternative to or normalization of the actual descriptive + text contained in the element. The previous example might equally well be given as + + + +

+

The generic trait and state elements are also members of this class, + + + These elements can be used to extend the range of information supplied about an individual's personal + characteristics. Either may contain an optional label element, used to provide a human-readable specification + for the characteristic concerned and a description of the feature itself supplied within a desc element. These + may be followed by or one or more p elements supplying more detailed information about the trait. In either + case, these may be followed by one or more notes or bibliographical references. The type, ref, and + key attributes may be used to indicate a fuller definition of the combination of feature and value. + + + Ethnic Albanian. + + +

+ + + +

These elements are provided as a simple means of extending the set of descriptive features available in a standardized + way. For example, there are no predefined elements for such features as eye or hair colour. If these are to be recorded, + they may simply be added as new types of trait: + + + blue + + + + brown + + +

+ +

If none of the more specialized elements listed above is appropriate, then a choice must be made between the two + generic elements trait and state. If you wish to distinguish between characteristics that are + generally perceived to be transient and those which are generally considered unchanging, use state for the + former, and trait for the latter. It may also be helpful to note that traits are typically, but not + necessarily, independent of the volition or action of the holder. If the distinction between state and trait is not + considered relevant or useful, use state.

+ +

The persName element is repeatable and can, like all TEI elements, take the attribute xml:lang to + indicate the language of the content of the element, as well as a type attribute to indicate the type of + name, whether a nickname, maiden or birth name, alternative form, etc. This is useful in cases where, for example, a + person is known by a Latin name and also by any number of vernacular names, many or all of which may have claims to + authenticity. In order to ensure uniformity, the method generally employed in the library world + has been to accept the form found in some authority file, for example that of the American Library of Congress, as the + base or neutral form. Feelings can run high on this matter, however, and + people are often reluctant to accept as neutral an overtly foreign form of the name of their local + saint or hero. Within the person element any number of variant forms of a name can be given, with no + prioritization, and hence less likelihood of offence. The Icelandic scholar and manuscript collector Árni Magnússon, to + give his name in standard modern Icelandic spelling, is known in Danish as Arne Magnusson, the form which he himself, as + a long term resident of Denmark, generally used; there is also a Latinized form, Arnas Magnæus, which he used in his + scholarly writings. All three forms can be given, and in any order: + + Árni Magnússon + Arne Magnusson + Arnas Magnæus + + +

+

At the other extreme, a person may be named periphrastically as in the following example: + + Simon, son of Richard + Essex + 1219-1223 + + +

+ +

Alternatively, the generic name element may be used for all of the naming components in a description. For + example, a description of the first living held by the Icelandic clergyman and poet Jón Oddsson Hjaltalín might be + tagged as follows: +

Jón's first living — which he apparently accepted rather reluctantly — was at Háls í + Hamarsfirði, Múlasýsla, to which he was presented on 7 April 1777. He was + ordained the following month and spent three years at Háls, but was never happy there, due largely to the general + penury in which he was forced to live — a recurrent theme throughout the early part of his life. In June of 1780 + the bishop recommended that Jón should promoveres til andet bedre kald, end det hand hidindtil + har havt, and on 12 July it was agreed that he should exchange livings with sr. Þórður Jónsson at Kálfafell á Síðu, + Skaftafellssýsla.

ÞÍ, Stms I.15, p. 733. ÞÍ, Stms I.17, p. + 102. + +

+ +

Similarly, the generic state or trait element may be used in preference to the more specific elements + listed above: + + + American citizen from 15 January 2002. + + is the same as: + American citizen from 15 January 2002. + or even: + + +

+ +
+
+ Personal Events +

This section describes events that relate to one or more persons, while the section on + Events below describes the use of event in more general terms.

+

Events in a person's history are not characteristics of an individual, but often cause an individual to gain such + characteristics, or to enter a new state. Most such events, for example marriage, appointment, promotion, or a journey + may be recorded using the generic element event, which may be grouped with listEvent, and has a + content model similar to that of state and trait. The chief difference is that event can + include a placeName element to identify the name of the place where the event occurred.

+

Two particular events in a person's life, namely birth and death, are both ubiquitous and usually considered + particularly important, and thus may be represented by specialized elements for the purpose: + + + +

+

In the following example, we give a brief summary of the wedding of Jane Burden to the English writer, designer, and + socialist William Morris, encoded as an event element embedded within the person element used to + record data about Morris, though we could equally well have embedded the event element within the + person element for Burden, or have encoded it independently of either person element: + + + + + William Morris and Jane Burden were married at St + Michael's Church, Ship Street, Oxford on 26 April 1859. The wedding was + conducted by Morris's friend R. W. Dixon with Charles Faulkner as the best man. The bride was given away by her father, Robert Burden. According to the account that Burne-Jones gave Mackail + M. said to Dixon beforehand Mind you don't call her Mary but he did. The entry in + the Register reads: William Morris, 25, Bachelor Gentleman, 13 George Street, son of William Morris decd. + Gentleman. Jane Burden, minor, spinster, 65 Holywell Street, d. of Robert Burden, Groom. The witnesses + were Jane's parents and Faulkner. None of Morris's family attended the ceremony. Morris presented Jane with a + plain gold ring bearing the London hallmark for 1858. She gave her husband a double-handled antique silver + cup. + J. W. Mackail, The Life of William Morris, 1899. + + + + Robert Burden + + + R.W. Dixon + + + Charles Faulkner + + + + Edward + Burne-Jones + + + + J.W. Mackail + + In this example the ref attributes on the various name elements point either to an external + source or to a person element within which other information about the person named may be found. As further + discussed below (), a relation element may then be used to link them in a more + meaningful way: + + + + +

+

As mentioned above, all these elements, both the specific and the generic, are members of the att.datable attribute class, which means they can be limited in terms of time. The following encoding, for + example, demonstrates that the person named David Jones changed his name in 1966 to David Bowie: + + David Jones + David Bowie + + +

+

All the generic elements are also members of the att.global.responsibility and att.editLike classes. These classes make available the attributes cert, to indicate + the degree of certainty, resp, the agency responsible, evidence, the nature of the evidence used, + and source, a pointer to a resource from which the information derives. In this way it is possible, in the + case of multiple and conflicting sources, to provide more than one view of what happened, as in the following example: + +

Born in Brixton on 8 January + 1947.

+

Born in Berkhamsted on 9 January + 1947.

 + +

+
+
+ Personal Relationships + +

When the module defined by this chapter is included in a schema, the following two elements may be used to document + relationships amongst the persons, places, or organizations identified: + + + These elements are both members of the att.typed class, from which they inherit + the type and subtype attributes in the usual way. The value specified for either attribute on a + listRelation element is implicitly applicable to all of its child relation elements, unless + overridden.

+

A relationship, as defined here, may be any kind of describable link between specified participants. A + participant (in this sense) might be a person, a place, or an organization. In the case of persons, therefore, a + relationship might be a social relationship (such as employer/employee), a personal relationship (such as sibling, + spouse, etc.) or something less precise such as possessing shared knowledge. A relationship may be + mutual, in that all the participants engage in it on an equal footing (for example the sibling + relationship); or it may not be if participants are not identical with respect to their role in the relationship (for + example, the employer relationship). For non-mutual relationships, only two kinds of role are currently + supported; they are named active and passive. These names are chosen to reflect the fact that + non-mutual relations are directed, in the sense that they are most readily described by a transitive verb, + or a verb phrase of the form is X of or is X to. The subject of the verb + is classed as active; the direct object of the verb, or the object of the concluding preposition, as + passive. Thus parents are active and children passive in the relationship parent + (interpreted as is parent of); the employer is active, the employee passive, in the + relationship employs. These relationships can be inverted: parents are passive and + children active in the relationship is child of; similarly works for inverts the + active and passive roles of employs.

+

For example: + + + + This example defines the relationships amongst a number of people not further described here; + we assume however that each person has been allocated an identifier such as P1, P2, etc. which can + be linked to using references such as #P1, #P2, etc. Then the above set of relation + elements describe the following three relationships amongst the people referenced: + P1 and P2 are parents of P3 and P4. + P1 and P2 are linked in a mutual relationship called spouse—that is, P2 is the spouse of P1, and P1 is + the spouse of P2. + P1 has the social relationship employer with respect to P3 and P4. +

+

Relationships within places and organizations are further discussed in the relevant sections below. Relationships + between for example organizations and places, or places and persons, may be handled in exactly the same way. + +

+
+
+ +
+ Organizational Data +

The org and listOrg elements are used to store data about an organization such as its preferred name, + its locations, or key persons within it. + + + These elements are intended to be used in a way analogous to the place and person elements + discussed elsewhere in this chapter, that is to provide a unique wrapper element for information about an entity, distinct + from references to that entity which are typically encoded using a naming element such as name type="org" or + orgName. The content of a naming element will represent the way an organization is named in a given context; + the content of an org represents the information known to the encoder about that organization, gathered together + in a single place, and independent of its textual realization.

+

An organization is not the same thing as a list or group of people because it has an identity of its own. That identity + may be expressed solely in the existence of a name (for example The Scythians), but is likely to consist in the + combination of that name with a number of events, traits, or states which are considered to apply to the organization + itself, rather than any of its members. For example, a sports team might be described in terms of its membership (a + listPerson), its fixtures (a listPlace), its geographical affiliation (a placeName), or any + combination of these. It will also have properties which may be used to categorize it in some way such as the kind of + sport played, whether the team is amateur or professional, and so on: these are probably best dealt with by means of the + type attribute. However, it is the name of the sports team alone which identifies it.

+

The content model for org permits any mixture of generic state, trait, or event + elements: the presence of the orgName element described in is however strongly + recommended.

+

In other respects, the org element is used in much the same way as place or person. An + organization may have different names at different times: + The Silver Beetles + The Beatles + +

+

The names of the people making up an organization can also change over time, (if they are known at all). For example: + + The Silver Beetles + The Beatles + + + John Lennon + Paul McCartney + George Harrison + Stuart Sutcliffe + Pete Best + + + + + John Lennon + Paul McCartney + George Harrison + Ringo Starr + + + +

+

An org may contain subordinate orgs: + Oxford University Computing Services + + Information and Support Group + + + Infrastructure Group + + Networking Team + + + System Development Team + + + + Learning Technologies Group + + + +

+

The following example demonstrates the use of the listOrg element to group together a number of org + elements, each of which is defined solely by means of an informal description, itself containing other names. +

The TEI institutional hosts are: + + Brown University + The host contribution is made jointly by the Brown University Women Writers + Project and the Brown University Library's Center for Digital Initiatives. + + + Nancy + Hosting is provided by a group of institutions located in Nancy, France, coordinated by + Loria and also including ATILF and INIST. + + + Oxford University + Hosting is provided by the Research Technologies Service at Oxford University + Computing Services. + + + University of Virginia + Virginia's host support comes jointly from the Institute for Advanced Technology in the + Humanities and the University of Virginia Library. + + +

In a more elaborated version of this example, the organizational names tagged using orgName might + be linked using the key or ref attribute to a unique org element elsewhere.

+
+ +
+ Places + +

In we discuss various ways of naming places such as towns, countries, etc. In much the same way + as these Guidelines distinguish between the encoding of names for people and the encoding of other data about people, so + they also distinguish between the encoding of names for places and the encoding of other data about places. In this + section we present elements which may be used to record in a structured way data about places of any kind which might be + named or referenced within a text. Such data may be useful as a way of normalizing or standardizing references to + particular places, as the raw material for a gazetteer or similar reference document associated with a particular text or + set of texts, or in conjunction with any form of geographical information system.

+

The following elements are provided for this purpose: + + + +

+ +

The model.placeStateLike class contains elements describing characteristics of a place which + have a definite duration, such as its name. Any member of the model.placeNamePart may be used + for this purpose, since a place element will usually contain at least one, and possibly several, + placeName-like elements indicating the names associated with it, by different people, in different languages, + or at different times.

+ +

For example, the modern city of Lyon in France was in Roman times known as Lugdunum. Although the modern and the Roman + city are not physically co-extensive, they have significant areas which overlap, and we may therefore wish to regard them + as the same place, while supplying both names with an indication of the time period during which each was current.

+ +

Places usually have physical locations in addition to names. As with the example of Lyon, the precise + geographic location and extent of a place may change over time, and so locations like names may need to be + qualified with indications of the time period to which they apply. Locations may be + specified in a number of ways: as a set of coordinates defining a point or an area on the + surface of the earth, or by providing a description of how the place may be found, usually + in terms of other place names. For example, we can identify the location of the Canadian + city of London, either by specifying its latitude and longitude, or by specifying that we + mean the city called London located in the province called Ontario within the country called + Canada.

+ +

In addition we may wish to supply a brief characterization of the place identified, for example to state that it is a + city, an administrative area such as a country, or a landmark of some kind such as a monument or a battlefield. If our + typology of places is simple, the open ended type attribute is the easiest way to represent it: so we might say + place type="city", place type="battlefield" etc.

+ + +

Within the place element, the following elements may be used to provide more information about specific aspects + of the place in a structured form: + + + +

+
+ Varieties of Location +

A location may be specified in one or more of the following ways: + by supplying a string representing its coordinates in some standardized way within a geo element, as + shown below + by supplying one or more place name component elements (e.g. country, settlement etc.) to + place it within a geo-political context + by supplying a postal address, e.g. using the address element + by supplying a brief textual description, e.g. using the desc element + by using a non-TEI XML vocabulary such as the Geography Markup Language + We give examples of all of these methods in the remainder of this section.

+ +

The simplest method of specifying a location is by means of its geographic coordinates, supplied within the + geo element. This may be used to supply any kind of positional information, using one of the many different + geodetic systems available. Such systems vary in their format, in their scope or coverage, and more fundamentally in the + reference frame (the datum) used for the coordinate system itself. The default recommended by these + Guidelines is to supply a string containing two real numbers separated by whitespace, of which the first indicates + latitude and the second longitude according to the 1984 World Geodetic System (WGS84); this is the system currently used + by most GPS applications which TEI users are likely to encounter.See . The most recent revision of this standard is known as + the Earth Gravity Model 1996.We might therefore record the information about the place known as + Lyon as follows: + + Lyon + Lugdunum + 45.769559 4.834843 + + +

+ +

Identifying Lyon by its geo-political status as a settlement within a country forming part of a larger political + entity, we might represent the same place as follows: + + Lyon + Lugdunum + + EU + France + + + Elements such as bloc are specialized forms of placeName, as discussed in .

+

We may use the same procedure to represent the location of smaller places, such as a street or even an individual + building: + Brasserie Georges + + + Lyon + IIème + Perrache + 30, Cours de Verdun + + Note the use of the type attribute to categorize more precisely both the kind of place + concerned (a building) and the kind of name used to locate it, for example by characterizing the generic + district as an arrondissement, or a quartier.

+ +

We may also treat imaginary places in the same way: + Atlantis + + beyond + The Pillars of Hercules + +

+ +

A location sometimes resembles a set of instructions for finding a place: + Yasgur's Farm + Woodstock Festival Site + + one mile + north west of + Bethel + New York + + +

+

The element address may also be used to identify a location in terms of its postal or other address: + Protestant Cemetery + Cimitero Acattolico + + Italy + Rome + Testaccio + + +

+ Via Caio Cestio, 6 + 00153 Roma +
+ + When, as here, the same place is given multiple locations, the type attribute should be + used to characterize the kind of location, as a means of indicating that these are alternative ways of identifying the + same place, rather than that the place is spread across several locations.

+ +

The location element may thus identify a place to a greater or lesser degree of precision, using a variety of + means: a name, a set of names, or a set of coordinates. The geo element introduced earlier is by default + understood to supply a value expressed in a specific (and widely used) notation. If a location contains more + than one geo, this is interpreted as being really the same place in the universe, but with different systems + used to refer to it. If there is a lack of consensus about the location (of, for example, Camelot), more than one + location should be used, each with its own geo.

+ +

By default, the content of geo is interpreted as following the standard known as the World Geodetic System + (WGS). This may be modified, however, in two ways.

+

Firstly, the content of the geo element can be expressed some other way, that is, according to some different + geodetic system. The decls attribute is used point to a geoDecl element defined in the document + header, which describes a different datum.

+

Secondly, the element geo may be redefined to contain markup from a different XML vocabulary which is + specifically designed to represent this kind of information. This technique is used throughout these Guidelines where + specialized markup is required, for example to embed mathematical expressions or vector graphics, and is further + described and exemplified in . For geographic information, suitable non-TEI vocabularies include: + + the OpenGIS Geography Markup Language (GML) being defined by the OGCThe OGC is an + international voluntary consensus standards organization whose members maintain the Geography Markup Language + standard. The OGC coordinates with the ISO TC 211 standards organization to maintain consistency between OGC and + ISO standards work. GML is also an ISO standard (ISO 19136:2007). + + the Keyhole Markup Language (KML) used by Google MapsSee + + +

+

In the following example, we have defined the location of the place Lyon using GML and indicated + the two names associated with it at different times: + + Lyon + Lugdunum + + + + + 45.256 -110.45 46.46 -109.48 43.84 -109.86 45.8 -109.2 45.256 -110.45 + + + + + +

+ +

A bibl element may be used within location to indicate the source of the location information.

+ + + 53.226658 -0.541254 + Roman Inscriptions of Britain, 262 + + + +
+
+ Multiple Places +

A place may contain other places. This containment relation can be directly modelled in XML: thus we can say that the + towns of Vilnius and Kaunas are both in a place called Lithuania (or Lietuva) as follows: + Lithuania + Lietuva + + Vilnius + + + Kaunas + + +

+

This does not, of course, imply that Vilnius and Kaunas are the only places constituting Lithuania; only that they are + within it. A separate place element may indicate that it is a part of Lithuania by supplying a + relation element, as discussed below ().

+ +

As a further example, the islands of Mauritius, Réunion, and Rodrigues are collectively known as the Mascarene Islands. + Grouped together with Mauritius there are also several smaller offshore islands, with rather picturesque French names. + These offshore islands do not however constitute an identifiable place as a whole. One way of representing this is as + follows: + Mascarene Islands + Mascarenhas Archipelago + + Mauritius + + + La roche qui pleure + + + Île aux cerfs + + + + + Rodrigues + + + Réunion + + +

+

Here is a more complex example, showing the variety of names associated at different times and in different languages + with a set of hierarchically grouped places—the settlement of Carmarthen Castle, within the town of Carmarthen, within + the administrative county of Carmarthenshire, Wales. + + Cymru + Wales + Wallie + Wallia + Le Waleis + + Carmarthenshire + + Carmarthen + Kaermerdin + Caerfyrddin + + castle of Carmarthen + + + + + +

+

As noted previously, country, region, and settlement are all specializations of the generic + placeName element; they are not specializations of the place element. If it is desired to + distinguish amongst kinds of place this can only be done by means of the type attribute as in + the above example.

+ +

This use of multiple place elements should be distinguished from the (possibly simpler) case where a number of + places with some property in common are being grouped together for convenience, for example, in a gazetteer. The + listPlace element is provided as a means of grouping places together where there is no implication that the + grouped elements constitute a distinct place. For example: + Herefordshire + + + Abbey Dore + + 51.969604 -2.893146 + + + + Acton Beauchamp + + + + + + Hereford + + + Leominster + + + + +

+
+
+ States, Traits, and Events + +

There are many different kinds of information which it might be considered useful to record for a place in addition to + its name and location, and the categories selected are likely to be very project-specific. As with persons therefore + these Guidelines make no claim to comprehensiveness in this context. Instead, the generic state, + trait, and event elements defined by this module should be used. Each of these may be customized for + particular needs by means of their type attribute. These are complemented by a small number of predefined + elements of general utility: + + + + +

+ +

These are all specializations of the generic trait element. This element may be used for almost any kind of + event in the life of a place; no specialized version of this element is proposed, nor do we attempt to enumerate the + possible values which might be appropriate for the type attribute on any of these generic elements.

+

Here is an example, showing how the specific and generic elements may be combined: + + Iceland + Ísland + 65.00 -18.00 + + Area: 103,000 sq km + + +

Constitutional republic

+ + +

Part of the kingdom of Denmark

+ + + Iceland became independent on 17 June 1944. + + +

An independent republic since June 1944

+ + +

+ +

In the following example, the climate example is used to provided a detailed discussion of this particular + aspect of the information available about a particular place: + + Greece + + Greece's climate is divided into three well defined classes: + + + It features mild, wet winters and hot, dry summers. Temperatures rarely reach extremes, although snowfalls + do occur occasionally even in Athens, Cyclades or + Crete during the winter. + + + + It is found primarily in Western Greece + (Epirus, Central Greece, + Thessaly, Western Macedonia as well as + central parts of Peloponnesus like Achaea, + Arcadia and parts of Laconia where the Alpine range pass + by) + + + + It is found in Central and Eastern Macedonia as + well as in Thrace at places like Komotini, + Xanthi and northern Evros. It features cold, + damp winters and hot, dry summers. + + + + + +

+

As the above example shows, state and trait elements, and others of the same class, can be nested + hierarchically within each other. When this is done, values for the type attribute are to be understood as + cumulatively inherited, as elsewhere in the TEI scheme (for example on category or linkGrp). In the + following example, the outermost population element concerns the squirrel population between the dates given. + This is then broken down into red and gray squirrel populations, and within that into male and female: + + + 12 + 15 + + + 23 + 45 + + + The dating and responsibility attributes here behave slightly differently from the type attribute: + responsibility is not an additive property, and therefore an element either states it explicitly, or inherits it from + its nearest ancestor. Dating is slightly different again, in that a child element may specify a date more precisely than + its parent, as in the example above.

+ +

An event may be related to other named entities, and thus may appear within + an org, person, personGrp, persona, or place + element as well as within a listEvent or another event.

+ +
+ +
+ Relations Between Places + +

The relation element may also be used to express relationships of various kinds between places, or between + places and persons, in much the same way as it is used to express relationships between persons alone. Returning to the + Mascarene Islands example cited above, we might define the island group and its constituents separately, but indicate + the relationship by means of a relation element: + + + Mascarene islands + Mascarenhas Archipelago + + + Mauritius + + + + Rodrigues + + + Réunion + + + + +

+ +

This stand-off style of representation has the advantage that we can now also represent the fact + that a place may be a part of more than one other place; for example, Réunion is part of France, as well as part + of the Mascarenes. If we add a declaration for France to the list above: + + France + + we can now model this dual allegiance by means of a relation element: + + +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+
+ +
+ Events +

+ + + + + An event is a change of state whether real, planned, fictional, or purported about which more + information is known. The eventName element may be used to encode the proper name of an event, if known. The head or label element may also appear in event, either in lieu of or in addition to the eventName element, to provide a human-readable heading or editorially supplied label for the event.

+

These guidelines do not prescribe what encoders count as events, nor their granularity, + nesting, or amount of other information to record in relation to each event. Yet most events can be identified by their time, location, or agents involved (be they organizations, persons, or objects).

+

An event element may be used to record information about a place, person, or organization related to the described event; for this reason the element + may appear as content of a place, person, or org. However, it is also possible to describe events + independently of either a place, person, or organization. This may be useful not only for encoding texts which describe named events and + their eventNames, but also in applications as chronologies or lists of significant events (e.g., important battles, legislative milestones, or the stages of construction of a large building, etc.).

+ +

The listEvent element is a member of the model.listLike class, and may therefore + appear inside standOff, or wherever else lists are + permitted, in the same way as the listPerson, + listPlace, listOrg etc. elements described elsewhere in this + chapter.

+ + + + + + + France ceded to Great Britain its claims to the Hudson's Bay Company territories in + Rupert's Land, Newfoundland, and Acadia and + recognized British suzerainty over the Iroquois but retained its other pre-war + North American possessions, including + Île-Saint-Jean + (now Prince Edward Island)... + + + + This act of the British Parliament guaranteed free practice of the Catholic faith and restored use of the + French Civil Code for private matters throughout the Province of Quebec, which had been expanded in territory + following the Treaty of Paris. + + + + Also known as the Treaty with the Delawares, this was the first written treaty + between the newly formed United States and any Native American people, in this case, the + Lenape or Delawares. + + + + +

The next example demonstrates the use of the + where attribute with event, coordinated + with location information stored in listPlace.

+ + + + + + Luftwaffe shoots down Ilyushin Il-4 + DB-3F + + Іван Чиссов + + + Snap, Crackle, Pop is shot down by German flak + B-17 + + Alan Magee + + + Avro Lancaster shot down by Junkers Ju 88 + Lancaster + + Nicholas Alkemade + + + LANSA 508 struck by lightning + Amazon rainforest + + Juliane Diller (née Koepcke) + + + Bombing of Yugoslav Airlines Flight 367 + JAT 367 + + Весна Вуловић + + + + SAS parachute failure + Bear Grylls + + + + + Johannesburg parachute failure + Christine McKenzie + + Christine McKenzie + + + Cameraman fails to open chute + Sport videographer + + + + + + + + Gare de Saint-Nazaire + + 47.28657,-2.21171 + + + + Johannesburg + + South Africa + Gauteng + + + + Камчатке + + Russia + Kamchatka Krai + + + + Kenya + + + Oberkirchen + + Deutschland + Nordrhein-Westfalen + Arnsberg + Hochsauerlandkreis + Schmallenberg + 51.154,8.357 + + + + Puerto Inca + + Peru + Huánuco + Puerto Inca + + + + Schmallenberg + Smalmereg + + + + + Sebnitz + + 50.966667,14.283333 + + + + Eastern Front + + + + Zambia + + + + + + Весна Вуловић + Vesna Vulović + + + + + + Іван Михайлович Чиссов + Иван Михайлович Чисов + Ivan Mikhailovich Chisov + + + + + + Alan Eugene Magee + + + + + + Nicholas Stephen Alkemade + + + + + + Edward Michael Grylls + + + + + Juliane Koepcke + + + + + James Boole + 1978, give or take a year + + + + + + + + + +

The where attribute on event can point to multiple canonical place descriptions, which indicates that an event took place in multiple locations. For example, the November 2015 + Paris Attacks took place at six different locations in Paris; this + might be encoded as an event with a where + attribute with six space-separated values, or using a listPlace (nested into the event or standalone).

+ +

Events may also be modeled as hierarchies of nested events. For example, a two part meeting might be represented as follows: + + + All day meeting to resolve content models + + first part + + + second part + + + +

+ +

For event as a child element of person, note the Section .

+
+ +
+ Objects +

+ + + + + An object is any material thing whether real, in existence, fictional, missing, or purported about which more + information is known. Where objects have proper names the objectName element may be used to encode these. + However, many objects are not named but the object element may still be used to provide a description of them. + The object element is a more general descriptive form of the msDesc element. The latter should be used + for describing manuscripts and similar text-bearing objects but can be viewed as a more specific form of the + object element.

+

+ Please note: The object element is a recent addition to TEI P5 Guidelines as of version 3.5.0 and as such might + be more prone to further revision in the next few releases as its use develops. This may be particularly evident where its + contents have been borrowed from msDesc and have yet to be generalized from their use in the context of manuscript descriptions. +

+

The object element usually appears inside the + listObject element which is used to group + descriptions of identifiable objects. The listObject + element is a member of model.listLike and so may appear inside + standOff, or anywhere else that list is + allowed. This enables the flexibility of using + listObject to contain a set of metadata descriptions + stored in the TEI header, or as a list of objects transcribed from + a source document. The equivalent list for manuscript + descriptions is listBibl.

+

+ + + + + + + + Overall, the basic structure of an object element is akin to that of msDesc in that it is providing a + structured description of an object. After a group of + identifying information, it has the option of paragraphs or, if the msdescription module is + loaded, msContents, physDesc, history, and additional elements for descriptive + metadata about this object. Although these elements originate from manuscript description the object element may + be used for all forms of object (whether text-bearing or not). + + + Where descendents of object still have the hallmarks + of their use in manuscript description, the descriptions as relating to manuscripts should be interpreted as applying to all + forms of object (text-bearing) or not.

+

The objectIdentifier element is a general-purpose + grouping element for location or identification information relating to a single object or resource. It is very similar to + an msIdentifier element with less contraints on the order of its contents. The objectIdentifier may be more + or less detailed dependent on the needs of the encoder. In some cases an object may be used mostly as a common + reference point for multiple objectName elements to refer back to. In situations, one might provide more detailed + information in the objectIdentifier where it is available or desirable. Compare + + + Excalibur + +

Excalibur is the name for the legendary sword of King Arthur.

+ + where only a single objectName is provided and below where multiple versions are provided. + + + Excalibur + Caliburn + Caledfwlch + Calesvol + Kaledvoulc'h + Caliburnus + Wales + +

Excalibur is the main English name for the legendary + sword of King Arthur. In Welsh it is called + Caledfwlch, in Cornish it is called + Calesvol, in Breton it is called + Kaledvoulc'h, and in Latin it is + called Caliburnus. In some versions + of the legend, Excalibur’s blade was engraved with phrases on opposite + sides: Take me up and Cast me away (or similar).

+ + +

+

Moreover, the objectIdentifier may include an address element to provide the address at which the object + currently resides. The use of location within this enables the provision of geographical coordinates when + describing objects not housed in traditional repositories or institutions. This may also be used to supplement more + traditional repository location information if available and, for example, to enable providing outputs such as maps + showing the location of encoded objects. + + Mask of Tutankhamun + 256a + 60672 + 220 + Museum of Egyptian Antiquities +

+ 15 Meret Basha + Ismailia + Cairo + Egypt + + 30.047778, 31.233333 + +
+ + +

+

The msContents element is currently used to provide a description of the intellectual contents of any text on an object + and, being optional, is not necessary if there are no intellectual contents to describe. (Such contents, especially in the + case of artistic objects, may not always be textual.) The physDesc element may be used to give a physical + description of the object either in prose or using more structured elements as and where they apply to that kind of + object. The history element provides the option to describe the history of the object as paragraphs or with more + structure using the origin element, as many provenance stages as are appropriate, and + acquisition to describe its current ownership. The additional element may be used to provide + information about surrogates for the object (such as digital facsimiles) as well as administrative and curatorial + information. A full description of an object can provide more or less detail at any level to represent the state of + knowledge about the object. + + + + + Mask of Tutankhamun + 256a + 60672 + 220 + Museum of Egyptian Antiquities +
+ 15 Meret Basha + Ismailia + Cairo + Egypt + + 30.047778, 31.233333 + +
+ + +

The back and shoulders of the mask is inscribed with a protective spell in Egyptian hieroglyphs formed of ten + vertical and horizontal lines. This spell first appeared on masks in the Middle Kingdom at least 500 years + before Tutankhamun, and comes from chapter 151 of the Book of the Dead.

+ + +

The mask of Tutankhamun is 54cm x 39.3cm x 49cm. It is constructed from two layers of high-karat gold that + varies in thickness from 1.5-3mm. It weighs approximately 10.23kg and x-ray crystallography shows that it is + composed of two alloys of gold with a lighter 18.4 karat shade being used for the face and neck while a heavier + 22.5 karat gold was used for the rest of the mask.

+

In the mask Tutankhamun wears a nemes headcloth which has the royal insignia of a cobra (Wadjet) and vulture + (Nekhbet) on it. These are thought respectively to symbolize Tutankhamun's rule of both Lower Egypt and Upper + Egypt. His ears are pierced for earrings. The mask has rich inlays of coloured glass and gemstones, including + lapis lazuli surrounding the eye and eyebrows, quartz for the eyes, obsidian for the pupils. The broad collar is + made up of carnelian, feldspar, turquoise, amazonite, faience and other stones.

+ + + +

The mask of Tutankhamun was created in Egypt around 1323 BC. It is a death mask of the 18th-dynasty ancient Egyptian Pharaoh Tutankhamun + who reigned 1332–1323 BC.

+ + +

The mask of Tutankhamun was found in his burial chamber at Theban Necropolis in the Valley of the Kings in + 1922. On 28 October 1925 the excavation team led by English archaeologist Howard Carter opened the heavy + sarcophagus and three coffins and were the first people in around 3,250 years to see the mask of Tutankhamun. + Carter wrote in his diary: The pins removed, the lid was raised. The penultimate scene was disclosed – + a very neatly wrapped mummy of the young king, with golden mask of sad but tranquil expression, symbolizing + Osiris … the mask bears that god's attributes, but the likeness is that of Tut.Ankh.Amen – placid and + beautiful, with the same features as we find upon his statues and coffins. The mask has fallen slightly + back, thus its gaze is straight up to the heavens. +

+ + In December 1925, the mask was removed from the tomb, placed in a crate and transported 635 + kilometres (395 mi) to the Egyptian Museum in Cairo, where it remains on public display. + + + + + When it was discovered in 1925, the 2.5kg narrow gold beard was no longer attached to + the mask and was reattached to the chin by use of a wooden dowel in 1944. + In August 2014 when the mask was removed from its display case for cleaning, the + beard fell off again. Those working in the museum unadvisedly used a quick-drying epoxy to attempt to fix + it, but left the beard off-centre. + The damage was noticed and repaired in January 2015 by a German-Egyptian team who + used beeswax, a material known to be used as adhesives by the ancient Egyptians. + + + + + + +

+ + +

If the object is being referenced from elsewhere in the document, this is usually done with an objectName. For + example here the Alfred-Jewel xml:id is referenced from a paragraph elsewhere in the document using the ref + attribute on the objectName element. + + + + + + + United Kingdom + Oxfordshire + Oxford + University of Oxford + Ashmolean Museum + English Treasures + AN1836p.135.371 + https://en.wikipedia.org/wiki/Alfred_Jewel + Alfred Jewel + + +

The Alfred Jewel is about 6.4 cm in length and is made of combination of filigreed gold + surrounding a polished teardrop shaped piece of transparent quartz. Underneath the rock + crystal is a cloisonné enamel image of a man with ecclesiastical symbols. The sides of the jewel holding the + crystal in place contain an openwork inscription saying "AELFRED MEC HEHT GEWYRCAN", meaning 'Alfred ordered me + made'.

+ + + It is generally accepted that the Alfred Jewel dates from the late 9th Century and + was most likely made in England. + The jewel was discovered in 1693 at Petherton Park, North Petherton in the English county + of Somerset, on land owned by Sir Thomas Wroth. North Petherton is about 8 miles away from Athelney, where King + Alfred founded a monastery. + A description of the Alfred Jewel was first published in 1698, in the Philosophical + Transactions of the Royal Society. + It was bequeathed to Oxford University by Colonel Nathaniel Palmer (c. 1661-1718) and today is in + the Ashmolean Museum in Oxford. + + + + + +

+ The Minster Lovell Jewel is probably the most similar to the + Alfred Jewel and was found in Minster + Lovell in Oxfordshire and is kept at the Ashmolean Museum. +

+ +

+ +

+There is no restriction on the form, size, or type of object that may be described by an object element, however, some objects may be more adequately described by a place element depending on context. Where a description of an object is being provided in terms of identification, physical characteristics, or history, then an object element may be preferred. Where metadata is being recorded about the geo-political location, population, or similar traits, then the place element may be better suited. A corresponding relation between an object description and place may be recorded through the use of the corresp attribute. An example of a large object that might be described with the object element could be a building such as the Central Library of the National Autonomous University of Mexico. +

+ + +

+ + + + The Central Library of UNAM + The Central Library of the National Autonomous University of Mexico + La Biblioteca Central de la Universidad Nacional Autónoma de México + Mexico City + Coyoacán + Mexico + + + +

The Central Library encompasses an area of 16 thousand square + meters and is built on a three meter platform. The base contains two basalt + fountains and decorative reliefs inspired by + pre-Hispanic art.

+

The library has ten windowless floors for book storage, each having enough space for 120 thousand volumes. + These storage areas have the necessary lighting, temperature and humidty conditions for book conservation. + In the reading room, flanked by a garden on each side, the diffuse and matte light is filtered through + thin tecali stone slabs. The semi-basement of the building contains the service + and administrative offices of the library.

+

The building facades are covered with one of the largest murals in the world and is made from naturally + colored stone tiles. It is entitled Historical Representation of Culture and is by + Juan O'Gorman.

+ + + + At the base of the building there are two basalt fountains and decorative reliefs + around the outside that are inspired by pre-Hispanic art. The color of the stone in these elements is left + exposed to take advantage of the stone's texture as an aesthetic and expressive element, and to give a + sense of continuity to the external pavement. + + +

The outside windowless portion of the building contains one of the largest murals in the world. This is + called Historical Representation of the Culture and is a stone polychromatic + mosaic based on the combination of 12 basic colors. The mural is created in an + impressionist style where the coloured tiles when seen from a distance form specific figures. The 12 + colors where chosen from 150 samples of original stones with the criteria including the stone's + resistance to degredation by weather. According to the artist, Juan + O'Gorman, in the mosaic he represented three fundamental historical facets of the Mexican + culture: the pre-Hispanic era, the Spanish colonial era, and the modern age. For example with the North + Wall, this represents the pre-Hispanic era and is dominated by mythical elements relating to the + life-death duality. The left side of the main axis there are + deities and scenes pertaining to the creation of life. The right hand side of the mural contains figures + relating to death. For a more detailed description see https://en.wikipedia.org/wiki/Central_Library_(UNAM)#Murals.

+ + + + + In 1948 the architect and artist Juan O'Gorman, in + collaboration with architects Gustavo Saavedra and Juan Martinez de Velasco designed the building with a + functionalist approach, as part of the greater project of the construction of the University City on the + grounds of the Pedregal de San Angel in Mexico City. Originally the building was planned to host the National + Library and National Newspaper Library of Mexico. The library finally opened its doors for the first time on + 5 April 1956. In July 2007 it was declared a UNESCO + world heritage site. + + + + + + The library was significantly remodelled from 1981 - 1983 with the + purpose of changing from closed shelving to open stacks, providing users more direct access to the + collections. + + + + + + + +

+ + + + + + + + + + + + +
+ + + +
+ Names and Nyms +

So far we have discussed ways in which a name or referring string encountered in running text may be resolved by + considering the object that the name refers to: in the case of a personal name, the name refers to a person; in the case + of a place name, to a place, for example. The resolution of this reference is effected by means of the key or + ref attributes available to all elements which are members of the att.naming + class, such as persName or placeName and their more specialized variants such as forename or + country. However, names can also be regarded as objects in their own right, irrespective of the + objects to which they are attached, notably in onomastic studies. From this point of view, the names + John in English, Jean in French, and Ivan in + Russian might all be regarded as existing independently of any person to which they are attached, and also independently + of any variant forms that might be attested in different sources (such as Jon or Johnny in English, or Jehan or Jojo in + French). We use the term nym to refer to the canonical or normalized form of a name regarded in such a way, + and provide the following elements to encode it: + + + +

+

Any element which is a member of the att.naming class may use the attribute nymRef + to indicate the nym with which it corresponds. Thus, given the following nym for the name + Antony: + + +

Antony
+ + + an occurrence of this name in running text might be encoded as follows: + Tony Blair Note that this association (between "Tony" and "Antony") has + nothing to do with any individual who might use the name.

+

The person identified by this particular Tony may however be indicated independently using the ref attribute, + either on the forename or on the whole name component: + Tony + + + Tony Blair + politician + +

+

The nym element may be thought of as providing a specialized kind of dictionary entry. Like a dictionary entry, + it may contain any element from the model.entryPart class, such as form, + etym, etc. For example, we may show that the canonical form for a given nym has two orthographic variants in + this way: + +

+ Ian + Iain +
+ + +

+

Because a schema intending to make use of the nym or listNym element must include the dictionaries module as well as the namesdates module, many other + elements are available in addition to form. For example, to provide a more complex etymological decomposition of + a name, we might use the existing etym element, as follows: +

Bogomil
+ Means favoured by God from the Slavic elements bog + God and mil + favour + +

+

Where it is necessary to mark the substructure of nyms, this may be done by seg elements within the + form: + +

+ + Bogomil + Bogomil + +
+ + The seg element used here is provided by the TEI + linking module, which would therefore also need to be included in a schema built to + validate such markup. Other possibilities for more detailed linguistic analysis are provided by elements included in that + and the analysis (see ) or iso-fs modules + (see ).

+

Alternatively, each of the constituents of Bogomil might be regarded as a nym in its own right: + + +

bog
+ + +
mil
+ + Within running text, a name can specify all the nyms associated with it: ...Bogomil... Similarly, + within a nym, the attribute parts is used to indicate its constituent parts, where these have been identified + as distinct nyms: + +
Bogomil
+ + +

+

The nym element may also combine a number of other nym elements together, where it is intended to show + that they are all regarded as variations on the same root. Thus the different forms of the name John, all being derived + from the same root, may be represented as a hierarchic structure like this: +

Iohannes
+ +
John
+ +
Johnny
+ + +
Jon
+ + + +
Ivan
+ + +
Jean
+ + +

+

The nym element may be used for components of geographical or organizational names as well. For example: + + Lairig + Eilde + ... +

lairig
+ sloping hill face + ... +

+ +

+ + + + As noted above, use of these elements implies that both the dictionaries and the + namesdates modules are included in a schema.

+
+
+ +
+ Dates +

The following elements for the encoding of dates and times were introduced in section : + + + +

+

The current module namesdates provides a mechanism for more detailed encoding of relative + dates and times. A relative temporal expression describes a date or time with reference to some other + (absolute) temporal expression, and thus may contain an offset element in addition to one or more date + or time elements: + + +

+

As members of the att.datable and att.duration classes, which in + turn are members of att.datable.w3c and att.duration.w3c + respectively, the date and time elements share the following attributes: + + + +

+
+ Relative Dates and Times +

As noted above, relative dates and times such as in the Two Hundredth and First Year of the Republic, twenty + minutes before noon, and, more ambiguously, after the lamented death of the Doctor or an hour after the + game have two distinct components. As well as the absolute temporal expression or event to which reference is made + (e.g. noon, the game, the death of the Doctor, [the foundation of] the Republic), they also + contain a description of the distance between the time or date which is indicated and the referent + expression (e.g. the Two Hundredth and First Year, twenty minutes, an hour); and (optionally) an + offset describing the direction of the distance between the time or date indicated and the + referent expression (e.g. of implying after, before, after).

+

The distance component of a relative temporal expression may be encoded as a temporal element in + its own right using either date or time, or with the more generic measure element. A special + element, offset, is provided by this module for encoding the offset component of a + relative temporal expression. The absolute temporal expression contained within the relative expression may be encoded + with a date or time element; in turn, those elements may of course be relative, and thus contain + date or time elements within themselves. This allows for deeply nested structures such as the + third Sunday after the first Monday before Lammastide in the fifth year of the King's second marriage ... but so + does natural language.

+

In the following examples, the when and dur attributes have been used to simplify processing of + variant forms of expression: + A fortnight + before + Christmas 1786 + + I reached the station

+

In the following example, a nested date element is used to show that my birthday and the cited date are + parts of the same temporal expression, and hence to disambiguate the phrase A week before my birthday on 9th + December: + A week + before + + my birthday on 9th December + + The alternative reading of this phrase could be encoded as follows: + A week + before + my birthday on 9th December + +

+

Where more complex or ambiguous expressions are involved, and where it is desirable to make more explicit the + interpretive processes required, the feature structure notation described in chapter may be used. + Consider, for example, the following temporal expression which occurs in the Scottish Temperance Review + of August 1850, referring to the summer holiday known in Glasgow simply as the Fair: Not only is the city, during the Fair, a horrible + nucleus of immorality and wickedness; it sends our multitudes to pollute and demoralize the country. +

+

For the definition of the ana attribute, see chapter (in particular ). It is used here to link the temporal phrase with an interpretation of it. Like most traditional + fairs and market days, the Glasgow Fair was established by local custom and could vary from year to year. Consequently, + in order to provide such an interpretation, it is necessary to draw upon additional information which may or may not be + located in the particular text in question. In this case, it is necessary at least to know the spatial and temporal + context (year and place) of the fair referred to. These and other features required for the analysis of this particular + temporal expression may be combined together as one feature structure of type date-analysis: + the Fair + Glasgow + + 1850-08-08 + 1850-09-19 + For further discussion of feature structure representation see chapter .

+
+ +
+ Absolute Dates and Times + +

The following are examples of absolute temporal expressions.

+

+ The university's view of American affairs + produced a stinging attack by Edmund Burke in the Commons debate of 26 October + 1775 + + Friday, 14 May 1993 + +

+

It may be useful to categorize a temporal expression which is given in terms of a named event, such as a public + holiday, or a named time such as tea time or matins: In + New York, New Year's Day is the quietest of holidays, Independence Day the most turbulent. +

+ + + + + + + + + +

Absolute temporal expressions denoting times which are given in terms of seconds, minutes, hours, or of well-defined + events (e.g. noon, sunset) may similarly be represented using the time element. The train leaves for Boston at + At we walked to the beach. + The train leaves for Boston at +

+
+
+ More Expressive Normalizations +

The attributes for normalization of dates and times so far described use a standard format defined by XML Schema Part 2: Datatypes Second Edition. This format is widely accepted and has significant + software support. It is essentially a profile of ISO 8601 Data elements and interchange formats — Information + interchange — Representation of dates and times. The full ISO standard provides formats not available in the + W3C recommendation, for example, the capability to refer to a date by its ordinal date or week date, or to refer to a + century. It also provides ways of indicating duration and range.

+ +

When this module is included in a schema, the following additional attributes are provided: + + + These attributes may be used in preference to their W3C equivalent when it is necessary to provide a + normalized value in some form not supported by the W3C attributes. For example, a century date in the W3C format must be + expressed as a range, using the from attribute together with either the to attribute or the + dur (duration) attribute: fourteenth century + fourteenth century + With the attribute when-iso, however, it is possible to express the same normalized value in any of + the following additional ways: fourteenth + century + fourteenth century + fourteenth century + +

+ + + + + + + + + + + + + + + + +
+ +
+ Using Non-Gregorian Calendars +

All date-related encoding described above makes use of the Gregorian calendar, on which both the ISO and W3C datetime + formats are based. However, historical texts often pre-date the invention of the Gregorian calendar in the 16th century, + or its adoption in Europe over the following centuries, and many other calendars are used in texts from other cultures + and contexts. Non-Gregorian dates can be encoded using methods described below.

+ +

First, a Calendar Description element needs to be supplied in the teiHeader as described in :

+ + + +

The Julian calendar, as used in England until 1752.

 + + + +

The following attributes can now be used to encode dates using this calendar: + + + + +

The Poole by S. Giles Churchyarde was a large water in the yeare 1244.

+ Here, the calendar attribute points to the calendar element in the header which defines and + describes the calendar used.

+ +

The calendar attribute is used to specify the calendar used in the text content of the dating + element which bears it. For reasons of consistency and computability, it is often useful to complement the content of an + element with attributes such as when, notBefore, notAfter, etc. For dates expressed in a non-Gregorian calendar, + such normalizations may also be expressed in terms of the non-Gregorian calendar specified by the datingMethod attribute. + The attributes when-custom, notBefore-custom, from-custom, etc. are provided for this purpose; the datingMethod attribute + is used to identify the calendar used in the value of these attributes: + The Tryumphs of Peace. That Celebrated the Solemnity of the right Honorable Sr Francis Iones Knight, at + his Inauguration into the Maioraltie of London, on Monday being the 30. of October, 1620. + + Here, the calendar attribute specifies the calendar used in the text content of the date + element, as before, whereas the datingMethod attribute signifies that the calendar used in the + when-custom attribute is also Julian. The schema could be customized in order to constrain the content of + custom attributes in a manner similar to the constraints provided on regular Gregorian dating attributes such as + when, to enforce consistency in the use of non-Gregorian dates.

+ +

Custom dating attributes can be combined with any of the standard dating attributes in order to provide a standardized + Gregorian version of a non-Gregorian date. We might enhance the preceding example with the addition of when, + providing the Gregorian calendar equivalent of the Julian date: + 30. of + October, 1620. + +

+
+
+ + +
+ Module for Names and Dates +

The module described in this chapter makes available the following components: + Names, dates, persons and places + Names and dates + Noms, dates, personnes et lieux + 名稱與日期 + Nomi e date + Nomes e datas + 名前モジュール + The selection and combination of modules to form a TEI schema is described in .

+
+ +
diff --git a/P5/Source/Guidelines/fr/NH-Non-hierarchical.xml b/P5/Source/Guidelines/fr/NH-Non-hierarchical.xml deleted file mode 120000 index d58074a0a7..0000000000 --- a/P5/Source/Guidelines/fr/NH-Non-hierarchical.xml +++ /dev/null @@ -1 +0,0 @@ -../en/NH-Non-hierarchical.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/NH-Non-hierarchical.xml b/P5/Source/Guidelines/fr/NH-Non-hierarchical.xml new file mode 100644 index 0000000000..652eaf1b20 --- /dev/null +++ b/P5/Source/Guidelines/fr/NH-Non-hierarchical.xml @@ -0,0 +1,824 @@ + + + + + + + +
+ Non-hierarchical Structures +

XML employs a strongly hierarchical document model. At various + points, these Guidelines discuss problems that arise when using + XML to encode textual features that either do not naturally lend + themselves to representation in a strictly hierarchical form or + conflict with other hierarchies represented in the + markup. Examples of such situations include: + +

Conflict between the hierarchy established by the + physical structure of a document (e.g., volume, page, + column, line) and its rhetorical or linguistic + structure (e.g., chapters, paragraphs, sentences, + acts, scenes, etc.)

+ + +

Conflict between a verse text's metrical structure + (e.g., its arrangement in stanzas and metrical lines) + and its rhetorical or linguistic structure (e.g., + phrases, sentences, and, for plays, acts, scenes, and + speeches).

+ + +

Conflict between metrical, rhetorical, or + linguistic structure and the representation of direct + speech, especially if the quoted speech is interrupted + by other elements (e.g., What, she asked, + was that all about) or crosses metrical, + rhetorical, or linguistic boundaries.

+ + +

Conflict between different analytical views or + descriptions of a text or document, e.g., markup + intended to encode diplomatic information about a + word's appearance in a manuscript with markup intended + to describe its morphology or pronunciation.

+ + +

+

Non-nesting information poses fundamental problems for any + XML-based encoding scheme, and it must be stated at the outset + that no current solution combines all the desirable attributes of + formal simplicity, capacity to represent all occurring or + imaginable kinds of structures, suitability for formal or + mechanical validation. The representation of non-hierarchical + information is thus necessarily a matter of trade-offs among + various sets of advantages and disadvantages.

+

These Guidelines support several methods for handling + non-hierarchical information: + +

redundant encoding of information in multiple forms + (discussed in )

+ + +

the use of empty elements to delimit the boundaries + of a non-nesting structure (discussed in )

+ + +

the division of a logically single non-nesting + element into segments that nest properly in their + immediate hierarchical context but can also be + reconstituted virtually across these hierarchical + boundaries (discussed )

+ + +

stand-off markup: the annotation of information by + pointing at it, rather than by placing XML tags within + it (discussed in )

+ + Some of these methods can be used in TEI-conformant documents. Others + require extension.

+

In the sections which follow these techniques are described and their advantages and + disadvantages are briefly discussed. The various solutions to the problem will be + exemplified using extracts from two poems. The first is the opening quatrain from William + Wordsworth's Scorn not the sonnet: + Scorn not the sonnet; critic, you have frowned, + Mindless of its just honours; with this key + Shakespeare unlocked his heart; the melody + Of this small lute gave ease to Petrarch's wound. + The second example is the third stanza from the fourth section of Robert Pinsky's + Essay on Psychiatrists: + + Catholic woman of twenty-seven with five children + And a first-rate body—pointed her finger + at the back of one certain man and asked me, + "Is that guy a psychiatrist?" and by god he was! "Yes," + She said, "He looks like a psychiatrist." + Grown quiet, I looked at his pink back, and thought. + + These two texts can be analysed in various ways. The first, which we might describe + as the Metrical View, encodes the text according to its metrical + features: line divisions (as here), stanzas or cantos in larger poems, and perhaps prosodic + features like stress or syllable patterns, alliteration, or rhyme. A second view, which we + might describe as the Grammatical, encodes linguistic and rhetorical + features: phonemes, morphemes, words, phrases, clauses, and sentences. A third view, the + Dialogic, might concentrate on narrative voice: distinguishing + between the narrator and their interlocutors and identifying individual segments as direct + quotations. In our examples, we will restrict ourselves to relatively simple conflicts: for + the Metrical View we will encode only metrical lines and line groups; for the + Grammatical View we will restrict ourselves to encoding sentences; and for + the Dialogic View, we only will distinguish direct quotation from other + narration.

+
+ Multiple Encodings of the Same Information +

Conceptually, the simplest method of disentangling two (or + more) conflicting hierarchical views of the same information + is to encode it twice (or more), each time capturing a single + view.

+

Thus, for example, the Metrical View of Scorn not the + sonnet might be encoded as follows, using the l element to encode + each metrical line: + Scorn not the sonnet; critic, you have frowned, + Mindless of its just honours; with this key + Shakespeare unlocked his heart; the melody + Of this small lute gave ease to Petrarch's wound. +

+

The Grammatical View would be encoded by + taking the same text and replacing the metrical markup with + information about its sentence structure: +

+ Scorn not the sonnet; + critic, you have frowned, Mindless of its just honours; + with this key Shakespeare unlocked his heart; + the melody Of this small lute gave ease to Petrarch's wound. +

+

+

Likewise, the more complex passage from Pinsky could be + encoded in three different ways to reflect the different + metrical, grammatical, and dialogic views of its text: + + Catholic woman of twenty-seven with five children + And a first-rate body—pointed her finger + at the back of one certain man and asked me, + "Is that guy a psychiatrist?" and by god he was! "Yes," + She said, "He looks like a psychiatrist." + Grown quiet, I looked at his pink back, and thought. + + + + +

+Catholic woman of twenty-seven with five children And a +first-rate body—pointed her finger at the back of one certain man and +asked me, "Is that guy a psychiatrist?" and by god he was! +

+

+"Yes," She said, "He looks like a +psychiatrist." +

+

+ Grown quiet, I looked at his pink back, and thought. +

+ + + +Catholic woman of twenty-seven with five children And a first-rate +body—pointed her finger at the back of one certain man and asked me, +Is that guy a psychiatrist? and by god he was! +Yes, She said, He looks like a +psychiatrist. Grown quiet, I looked at his pink back, and +thought. + + +

+

This method is TEI-conformant. Its advantages are that each + way of looking at the information is explicitly represented in + the data and that the individual views are simple to + process. The disadvantages are that the method requires the + maintenance of multiple copies of identical textual content + (an invitation to inconsistency) and that there is no explicit + indication that the various views, which might be in separate + files, are related to each other: it might prove difficult to + combine the views or access information from one view while + processing the file that contains the encoding of + another.It has been shown, however, that it + is possible to relate the different annotations in an indirect + way: if the textual content of the annotations is identical, + the very text can serve as a means for linking the different + annotations, as described in .

+
+
+ Boundary Marking with Empty Elements +

A second method for accommodating non-hierarchical objects + in an XML document involves marking the start and end points + of the non-nesting material. This prevents textual features + that fall outside the privileged hierarchy from invalidating + the document while identifying their beginnings and ends for + further processing. The disadvantage of this method is that no + single XML element represents the non-nesting material and, as + a result, processing with XML technologies is significantly + more difficult.

+

The empty elements used at each end are called + segment-boundary elements or + segment-boundary delimiters. There are several + variations on this method of encoding.

+ +

For some common structural features, the TEI provides + milestone elements that can be used to mark the beginning of a + textual feature. These include lb, pb, + cb, handShift, and the generic + milestone. Using lb, for example, it is + possible to indicate both the physical lineation of a poem on + the page and its grammatical division into sentences: + +

+Scorn not the sonnet;; critic, you have +frowned, Mindless of its just honours; with this +key Shakespeare unlocked his heart; the melody +Of this small lute gave ease to Petrarch's +wound.

+

+

The use of these elements is by definition TEI-conformant. + Care should be taken, however, that the meaning of + the milestone elements is preserved: semantically, for + example, lb is used to mark the start of a new + (typographical) line. While in much modern poetry, + typographical and metrical line divisions correspond, + lb does not itself make a metrical claim: in encoding + verse from sources, such as Old English manuscripts, where + physical line breaks are not used to indicate metrical + lineation, the correspondence would break down entirely.

+ + +

The segment boundaries also may be delimited by the generic + anchor element. Attributes can then be used to + indicate the type of feature being delimited and whether a + given instance opens or closes the feature. + + + Scorn not the sonnet; + + critic, you have frowned, + Mindless of its just honours; + with this key + Shakespeare unlocked his heart; + the melody + Of this small lute gave ease to Petrarch's wound. + +

+

This method is TEI-conformant.

+ + +

Another approach is to design custom elements that provide + richer information about the feature being delimited or its + boundaries. This information can be included as attribute + values or as part of the element name itself: e.g., + boundaryStart + element="sentence"/... boundaryEnd + element="sentence"/, sentenceBoundary + position="start"/... sentenceBoundary + position="end"/, or sentenceBoundaryStart/... + sentenceBoundaryEnd/: + + + +Scorn not the sonnet; + +critic, you have frowned, +Mindless of its just honours; +with this key +Shakespeare unlocked his heart; +the melody +Of this small lute gave ease to Petrarch's wound. + +

+

If the custom elements can be replaced by TEI elements and + attributes without loss of information, this method is TEI-conformant + (see ); if the custom elements + introduce information or distinctions that cannot be captured + using standard TEI elements, the method is an extension.

+ + +

Finally, elements that are normally used to encode nesting + textual features (e.g., said, seg, + l, etc.) can be adapted so that they serve as empty + segment boundary delimiters when the features they encode + cross-hierarchical boundaries. Additional attributes (sID and eID in + the example below) are added to these elements in order to + allow the unambiguous correlation of start and end + points. This method has been introduced in the markup + literature under various names, including Trojan milestones, + HORSE markup, CLIX, and COLT. It is described in detail by + ): + + + Scorn not the sonnet;critic, you have frowned, + Mindless of its just honours; + with this key + Shakespeare unlocked his heart; + the melody + Of this small lute gave ease to Petrarch's wound. + + + Depending on how the modifications are carried out, + this method may be TEI-conformant, may represent an extension of the + TEI, or may produce a non-conformant document. + The method is TEI-conformant if the modified + elements and attributes can be mapped without loss of + information to existing TEI markup structures such as + milestone or anchor elements automatically (see ). + The method represents an Extension if the + modified elements are placed in a distinct, non-TEI + namespace (see ). + The method is non-conformant—and indeed strongly + deprecated—if the modified elements and attributes are + not placed in a distinct, non-TEI namespace (see ). +

+ + + +

In each of the above examples (except the last), the relationship between the start and + end delimiters (where these exist) of a given feature is implicit: it is assumed that + "end" delimiters close the nearest preceding "start" delimiter, or, in the case of + milestones, that the milestone marks both the end of the preceding example and the + beginning of the next. Complications arise, however, when the non-nesting text overlaps + with other non-nesting text of the same type, as, for example, in a grammatical analysis + of the various possible interpretations of the noun phrase + fast trains and planes. In this case, the adjective fast + can be understood as either modifying trains and planes or just + trains:

+ Two interpretations of the phrase + Fast trains and planes + + Graphic representation of two interpretations of the phrase Fast + trains and planes. +

+

In order to encode the possible analyses of this phrase, an + unambiguous method of associating opening and closing segment + boundary delimiters is required: + + + Fast + + trains + + and + planes + + + +

+

In this encoding, the first interpretation, in which + fast modifies the NP trains + and planes, the NP trains and + planes is opened using an anchor tag with + the xml:id value + NPInterpretationA and closed with an + anchor with the same value on corresp; in + the second interpretation, in which + fast forms a NP with + trains, the NP fast + cars is opened using an anchor tag with + the xml:id value + NPInterpretationB and closed with an + anchor tag that has the same value on + corresp.

+

Despite their advantages, segment boundary delimiters incur + the disadvantage of cumbersome processing: since the elements + of the analysis (e.g., the sentences in the poems, or phrases + in the above example) are not uniformly represented by nodes + in the document tree, they must be reconstituted by software + in an ad hoc fashion, which is likely to be difficult and may + be error prone.

+

Most important for some encoders, the method also disguises + the relationship between the beginning and the ending of each + logical element. This makes it impossible for standard + validation software to provide the same kind of validation + possible elsewhere in the encoding. When using grammar-based + schema languages it is not possible to define a content model + for the range limited by empty elements.Grammar based schema languages (e.g., DTD, W3C + Schema, and RELAX NG) are used to define markup languages + (e.g., XHTML or TEI). Rule-based schema languages (e.g., + Schematron) can be used to define further constraints. Such a + rule-based schema language permits a sequence of certain + elements between empty elements to be legitimized or + prohibited.

+
+
+ Fragmentation and Reconstitution of Virtual Elements +

A third method involves breaking what might be considered a + single logical (but non-nesting) element into multiple smaller + structural elements that fit within the dominant hierarchy but + can be reconstituted virtually. For example, if a passage of + direct discourse begins in the middle of one paragraph and + continues for several more paragraphs, one could encode the + passage as a series of said elements, each fitting + within a p element. The resulting encoding is valid + XML, but the text in each said element represents + only a portion of the complete passage of direct + discourse. For this reason these elements are sometimes called + partial elements.

+

In the case of our selection from Pinsky's poem, for + example, the second passage of direct quotation, which crosses + a line boundary and is broken up by a She + said in the narrator's voice, can be made to fit + within the hierarchy established by the metrical lineation by + using two said elements: + + + + Catholic woman of twenty-seven with five children + And a first-rate body—pointed her finger + at the back of one certain man and asked me, + Is that guy a psychiatrist? and by god he was! + Yes, + She said, He looks like a +psychiatrist. + Grown quiet, I looked at his pink back, and thought. + + +

+

Similarly, the sentences in our example from Wordsworth + could be encoded: + + + Scorn not the sonnet; + critic, you have frowned, + + + Mindless of its just honours; + with this key + + + Shakespeare unlocked his heart; + the melody + + + Of this small lute gave ease to Petrarch's wound. + +

+

There are two main problems with this type of encoding. The + first is that it invariably means that the encoding will have + more elements claiming to represent a feature than there are + actual instances of that feature in the text. Thus, for + example, the passage from Scorn not the + sonnet marks seven spans of text using seg, + even though there are only four linguistic sentences in the + passage.

+

The second problem is that it can be semantically + misleading. Although they are tagged using the element for + sentence, for example, very few of the textual + features encoded using seg in this example represent + actual linguistic sentences: with this + key, for example, is a prepositional phrase, not a + sentence; Of this small lute gave ease to + Petrarch's wound is a string corresponding to no + single grammatical category.

+

Taken together, these problems can make automatic analysis + of the fragmented features difficult. An analysis that + intended to count the number of sentences in Wordsworth's + poem, for example, would arrive at an inflated figure if it + understood the seg elements to represent complete + rhetorical sentences; if it wanted to do an analysis of his + syntax, it would not be able to assume that seg + delimited linguistic sentences.

+

The technique of fragmentation is often complemented by the + technique of virtual joins. Virtual joins may be used to + combine objects in the text to a new hierarchy. Here is Scorn not the sonnet again; this time the + relationship between the parts of the fragmented sentences is + indicated explicitly using the next and + prev attributes described in . + + + + Scorn not the sonnet; + critic, you have frowned, + + + Mindless of its just honours; + with this key + + + Shakespeare unlocked his heart; + the melody + + + Of this small lute gave ease to Petrarch's wound. + + This method of virtually joining partial elements is sometimes called + chaining.

+

For fragments encoded using ab, l, + lg, div, or elements that belong to the + att.segLike class, an even simpler + mechanism for virtually joining fragments exists: the use of + the part attribute with the value + I (Initial), M + (Medial), or F (Final) as described in + . Here is the above example recoded to + reflect this method: + + Scorn not the sonnet; + critic, you have frowned, + + + Mindless of its just honours; + with this key + + + Shakespeare unlocked his heart; + the melody + + + Of this small lute gave ease to Petrarch's wound. + +

+

This method is TEI-conformant and simple to use. Its + disadvantage is that it does not work well for cases of + self-overlap, or if there are nested occurrences of the same + element type, as it can become difficult to ascertain which + initial, medial, or final partial element should be combined + with which others or in which order. This problem becomes + evident if we attempt to combine a detailed Grammatical view + of the Pinsky example with its metrical encoding: + + + + Catholic woman of twenty-seven with five children + + + And a first-rate body—pointed her finger + + + at the back of one certain man and asked me, + + + "Is that guy a psychiatrist?" and by god he was! + "Yes," + + + She said, "He looks like a psychiatrist." + + + Grown quiet, I looked at his pink back, and thought. + + +

+ +

A third method for aggregating fragmented partial elements + involves using markup that is not directly part of the + encoding, e.g., the join element. In this method, a + join element is used elsewhere in the document to + indicate explicitly the members of the virtual element: + + + + Scorn + not + the + sonnet; critic, you + have + frowned, + + Mindless + of + its + just + honours; with + this + key + + + Shakespeare + unlocked + his + heart; the + melody + + + Of + this + small + lute + gave + ease + to + Petrarch's + wound. + + + +

+ + + + +

+ +

+

This use of join is TEI-conformant.

+

The major advantage of fragmentation and virtual joins is + that it allows all the hierarchies in the text to be handled + explicitly: both the privileged one directly represented and + the alternate hierarchy that has been split up and + rejoined. The major disadvantages are that (like most of the + other methods described here) it privileges one hierarchy over + the others, requires special processing to reconstitute the + elements of the other hierarchies, and, except in the case of + join, can be semantically misleading.

+
+
+ Stand-off Markup +

Most markup is characterized by the embedding of elements + in the text. An alternative approach separates the text and + the elements used to describe it. This approach is known as + stand-off markup (see section ). It + establishes a new hierarchy by building a new tree whose nodes + are XML elements that do not contain textual content, but + rather links to another layer: a node in + another XML document or a span of text. This approach + can be subdivided according to different criteria. A first + distinction concerns the link base, i.e. the content to which + annotations are to be applied. Sometimes the link target + contains markup that can be referred to explicitly, as in the + following example where the offset markup uses the + xml:id values on w to provide targets for + xi:includeA fake namespace is + given for XInclude here, to avoid the markup being interpreted + literally during processing.: + + Scorn + not + the + sonnet; critic, you + have + frowned, + + Mindless + of + its + just + honours; with + this + key + + + Shakespeare + unlocked + his + heart; the + melody + + + Of + this + small + lute + gave + ease + to + Petrarch's + wound. + + + + + + + + + + + + + + + + +

+]]> + + + Note that the layer that uses XInclude to build another hierarchy + might well be in another document, in which case the value of href of xi:xinclude would need to be + the URL of the document that contains the base layer, in this case + the w elements. +

+ +

This is very similar to the use of join discussed + above. The main advantages of the stand-off method are that it + is possible to specify attributes on the aggregate + seg elements, and that there exists off-the-shelf + software that will perform appropriate processing. Stand-off + markup may be used even when the base text being annotated is + plain text, i.e. does not have any XML encoding. In this case, + the range of text to be marked up is indicated by character + offsets (see , in particular ). Another distinction concerns the number + of files which can serve as link targets. Often, one + (dedicated) annotation is used as the link target of all the + other annotations. It is also possible to freely interlink + several layers.

+

It has been noted that stand-off markup has several + advantages over embedded annotations. In particular, it is + possible to produce annotations of a text even when the source + document is read-only. Furthermore, annotation files can be + distributed without distributing the source text. Further + advantages mentioned in the literature are that discontinuous + segments of text can be combined in a single annotation, that + independent parallel coders can produce independent + annotations, and that different annotation files can contain + different layers of information. Lastly, it has also been + noted that this approach is elegant.

+

But there are also several drawbacks. First, new stand-off + annotated layers require a separate interpretation, and the + layers—although separate—depend on each other. Moreover, + although all of the information of the multiple hierarchies is + included, the information may be difficult to access using + generic methods.

+

Inasmuch as it uses elements not included in the TEI + namespace, stand-off markup involves an extension of the + TEI.

+
+
+ Non-XML-based Approaches +

There exist many non-XML methods of encoding a text that + either solve or do not suffer the problem of the inability to + encode overlapping hierarchies. These include, but are not + limited to, the following proposals.

+ + Applying the notion of concurrent markup to XML + (). This reintroduces + the CONCUR feature of SGML, which was omitted from the XML + specification. + Designing a form of document representation in which + several trees share all or part of the same frontier, and + in which each individual view of the document has the form + of a tree (see ). + The colored XML proposal (), which stores a body of + information as a set of intertwined XML trees. This + approach eliminates unnecessary redundancy and makes the + database readily updatable, while allowing the user to + exploit different hierarchical access paths. + The MultiX proposal () , which represents documents as directed + graphs. Because XML is used to represent the graph, the + document is, at least in principle, manipulable with + standard XML tools. + The Just-In-Time-Trees proposal (), which stores documents + using XML, but processes the XML representation in + non-standard ways and allows it to be mapped onto data + structures that are different from those known from + XML. + The + Layered Markup and Annotation + Language LMNL + proposal. This offers alternatives to the basic + XML linear form as well as its data and processing + models. It uses an alternative notation to XML and + a data structure based on Core Range Algebra (). + + Markup Languages for Complex Documents + MLCD . This provides a + notation (TexMECS) and a data structure (Goddag) + as well as a draft constraint language for the + representation of non-hierarchical structures; see + . + +

These approaches are based either on non-standard XML + processing or data models, or not based on XML at all. Since + TEI is currently based on XML they are not described any + further in these Guidelines. Use of these methods with the TEI + will certainly involve extensions; in most cases the documents + will also be non-conformant.

+
+ + +
diff --git a/P5/Source/Guidelines/fr/PARTIND.xml b/P5/Source/Guidelines/fr/PARTIND.xml deleted file mode 120000 index 20a0f60c0e..0000000000 --- a/P5/Source/Guidelines/fr/PARTIND.xml +++ /dev/null @@ -1 +0,0 @@ -../en/./PARTIND.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/PARTIND.xml b/P5/Source/Guidelines/fr/PARTIND.xml new file mode 100644 index 0000000000..1ac7a6e99c --- /dev/null +++ b/P5/Source/Guidelines/fr/PARTIND.xml @@ -0,0 +1,10 @@ + + + + + + + +
Index + +
diff --git a/P5/Source/Guidelines/fr/PH-PrimarySources.xml b/P5/Source/Guidelines/fr/PH-PrimarySources.xml deleted file mode 120000 index 766b2496bb..0000000000 --- a/P5/Source/Guidelines/fr/PH-PrimarySources.xml +++ /dev/null @@ -1 +0,0 @@ -../en/./PH-PrimarySources.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/PH-PrimarySources.xml b/P5/Source/Guidelines/fr/PH-PrimarySources.xml new file mode 100644 index 0000000000..d5512f2e23 --- /dev/null +++ b/P5/Source/Guidelines/fr/PH-PrimarySources.xml @@ -0,0 +1,3059 @@ + + + + +
+ Representation of Primary Sources + +

This chapter describes elements that may be used to represent primary source materials, + such as manuscripts, printed books, ephemera, or other textual documents. Some of these specialized elements, + particularly at phrase-level, add to the other elements available within text + to deal with textual phenomena more specific to primary source transcription. + Other structural and block-level elements described here can be used to represent primary + source materials by prioritizing the encoding of their spatial features over their logical + textual structure (that is, the elements described in chapter ). + These elements, facsimile, sourceDoc, and their children, may be used in + parallel and in combination with an encoding of logical text structures with text, + or as standalone representations. The element sourceDoc in particular provides a way + of combining facsimile and transcriptions by embedding transcribed text. This approach focuses + on physical and textual features that can be primarily described spatially, such as the sequence + of pages in a manuscript, or the layout of a printed page. This is not meant to be the only way + of transcribing primary sources in TEI, or even a preferred way; which approach is more appropriate + will depend on the specific needs of your project.

+ +

Although this chapter discusses manuscript materials more frequently than other forms of written text, + most of the recommendations presented are equally applicable to facsimiles of a wide variety of media, + including printed matter, monumental inscriptions, and art. Each medium has its own vocabulary of agents. + In the following examples, terms such as scribe, author, editor, + annotator or corrector may be re-interpreted in terms + more appropriate to the medium being transcribed. In printed material, for example, the compositor plays a role analogous to the scribe, while in an authorial manuscript, the author and the scribe are the same person.

+ +

This module may be used in conjunction with other modules. These recommendations are not intended to meet every transcriptional circumstance likely to be faced by any scholar. They are intended rather as a base to enable encoding of the most common phenomena found in the course of scholarly transcription of primary source materials. These guidelines do not address the encoding of physical description of textual witnesses: the materials of the carrier, the medium of the inscribing implement, the organisation of the carrier materials themselves (such as quiring, collation), authorial instructions or scribal markup, etc., except insofar as these are involved in the broader question of manuscript description, as addressed by the msdescription module described in chapter .

+ +

This chapter begins by describing elements for handling digitally-encoded images of primary source materials for the purpose of creating digital facsimiles using the facsimile element ().

+

The next section () describes two ways of combining a facsimile images with a transcription; either by referencing a parallel transcription in text, or by providing an embedded transcription that prioritizes the encoding of a resource’s spatial features via the sourceDoc element and a number of transcriptional elements.

+

Section documents elements that support scholars in recording information about specific features of the text written on its physical carrier, such as and

+

Section describes how complex page layouts may be represented.

+

Section introduces the element fw (forme work) for encoding material repeated from page to page that falls outside the stream of the text.

+

Section describes how to document changes made during the production or revision of a primary source.

+

The chapter concludes with a technical overview of the structure and organization of the module described here. Some elements from other chapters are recontexualized for situations involving the transcription of primary source materials, whether within text or sourceDoc. Therefore, this overview should be read in conjunction with chapters and .

+ +
+ + Digital Facsimiles + +

A common approach in the TEI to representing pre-existing sources involves transcribing or otherwise converting sources into character form before marking them up. However, it is also a common practice to make a different form of + digital text that is instead composed of digital images of the + original source, typically one per page, or other written surface. We call such a resource + a digital facsimile. A digital facsimile may, in the simplest case, just + consist of a collection of images, with some metadata to identify them and the source + materials portrayed. It may sometimes contain a variety of images of the same source pages, + perhaps of different resolutions, or of different kinds. Such a collection may form part of + any kind of document, for example a commentary of a codicological or paleographic nature, + where there is a need to align explanatory text with image data. It may also be + complemented by a transcribed or encoded version of the original source, which may be + linked to the page images or embedded as discussed in . + In this section we present elements designed to support these + various possibilities and discuss the associated mechanisms provided by these + Guidelines.

+ + +

When this module is included in a schema, the class att.global + is extended to include two new pointer attributes, facs and change: + + + The change attribute is discussed further below in section . The facs attribute is used to associate any element + in a transcription with an image of the corresponding part of the source, by means of the + usual URI pointing mechanism. +

+ +

In the simple case where a digital text is composed of page images, the facs + attribute on the pb element may be used to associate each image with an + appropriate point in the text: + + + + + + + + + + + By convention, this encoding indicates that the image indicated by the + facs attribute represents the whole of the text following the pb + (page beginning) element, up to the next pb element. Any convenient milestone element + (see further ) could be used in the same way; for example if the + images represent individual columns, the cb element might be used. Though simple, + this method has some drawbacks. It does not scale well to more complex cases where, for + example, the images do not correspond exactly with transcribed pages, or where the + intention is to align specific marked up elements with detailed images, or parts of images. + The management of information about the images may become more difficult if references to + them are scattered through many files rather than being concentrated in a single + identifiable location. Nevertheless, this solution may be adequate for many straightforward + digital library applications.

+ +

The recommended approach to encoding facsimiles is instead to use the facs + attribute in conjunction with the elements facsimile or sourceDoc, and + the elements surface, surfaceGrp, and zone, which are also + provided by this module. These elements make it possible to accommodate multiple images of + each page, as well as to record the position and relative size of elements identified on + any kind of written surface and to link such elements with digital facsimile images of + them. Typical applications include the provision of full text search in digital + facsimile editions, and ways of annotating graphics, for example so as to + identify individuals appearing in group portraits and link them to data about the people + represented.

+ +

The following elements are available to represent components of a digital facsimile: + + + + + + + +

+ +

Either of the facsimile or sourceDoc elements may be used to represent a + digital facsimile. Either may appear within a TEI document along with, or instead of, the + text element introduced in section . The sourceDoc element + is used when a digital facsimile contains a transcription that prioritizes the encoding of the spatial features and layout of a text document over the text’s logical textual structure; the text element + should be used when it contains a textual transcription focused on its logical features. + When the digital facsimile contains only images, + however, only facsimile elements should be used. In this section, we first discuss the + simpler case, returning to the use of the sourceDoc element in section below. When this module is selected therefore, a legal TEI + document may thus comprise any of the following: + a TEI header and a text element + a TEI header and a facsimile element + a TEI header and a sourceDoc element + a TEI header, a facsimile element, and a text element + a TEI header, one or more sourceDoc or facsimile elements, and a text + element + +

+

Like the text element, a facsimile element may also contain an optional + front or back element, used in the same way as described in sections + and .

+ +

In the simplest case, a facsimile just contains a series of graphic elements, each + of which identifies an image file: + + + + + + + If desired, the binaryObject element described in + (or any other element from the model.graphicLike class) can be + used instead of a graphic.

+ +

In this simple case, the four page images are understood to represent the complete + facsimile, and are to be read in the sequence given. Suppose, however, that the second page + of this particular work is available both as an ordinary photograph and as an infra-red + image, or in two different resolutions. The surface element may be used to group + the two image files, since these correspond with the same area of the work: + + + + + + + + + + +

+ +

The surface element provides a way of indicating that the two images of page2 + represent the same surface within the source material. A surface might be one + side of a piece of paper or parchment, an opening in a codex treated as a single surface by + the writer, a face of a monument, a billboard, a membrane of a scroll, or indeed any + two-dimensional surface, of any size.

+ +

The surfaceGrp element may be used to indicate that two (or more) surfaces are + associated in some way, for example because they represent the recto and verso of the same + leaf, as in this example: + + + + + + + + + + + + The surfaceGrp element may also be useful as a means of identifying other + groups of written surfaces, such as adjacent faces of a monument, or gatherings of leaves.

+ +

Simply grouping related graphics is not however the main purpose of the surface + element: rather it is to help identify the location and size of the various two-dimensional + spaces constituting the digital facsimile. Note that the actual dimensions of the object + represented are not provided by the surface element ; rather, the surface + element defines an abstract coordinate space which may be used to address parts of the + image. Four attributes supplied by the att.coordinated class + are used to define this space. + + + +

+

By default, the same coordinate space is used for a surface and for all of its + child elements.The coordinate space may be thought of as a grid + superimposed on a rectangular space. Rectangular areas of the grid are defined as four + numbers a b c d: the first two identify the grid point which is at + the upper left corner of the rectangle; the second two give the grid point located at + the lower right corner of the rectangle. The grid point a b is + understood to be the point which is located a points from the + origin along the x (horizontal) axis, and b + points from the origin along the y (vertical) axis. It may + be most convenient to derive a coordinate space from a digital image of the surface in + question such that each pixel in the image corresponds with a whole number of units + (typically 1) in the coordinate space. In other cases it may be more convenient to use + units such as millimetres. Neither practice implies any specific mapping between the + coordinate system used and the actual dimensions of the physical object represented.

+ +

A surface element can contain one or more zone elements, each of which + represents a region or bounding box defined in terms of the same coordinate + space as that of its parent surface element. A zone may be rectangular or + non-rectangular: a rectangular zone is defined by a sequence of four coordinates in the + same way as a surface; a non-rectangular zone is defined using the attribute + points, which provides a sequence of coordinates, each of which specifies a + point on the perimeter of the zone.The points attribute + supplies a points specification in the same form as that required + by the polyline or polygon elements in the SVG standard. See +

+

A zone may be used to define any region of interest, such as a detail or illustration, or + some part of the surface which is to be aligned with a particular text element, or + otherwise distinguished from the rest of the surface. A surface establishes a coordinate + system which may be used to address parts or the whole of some digital representation of a + written surface. A zone, by contrast, defines any arbitrary area of interest relative to + that surface, using the same coordinate system. It might be bigger or smaller than its + parent surface, or might overlap its boundaries. The only constraint is that it must be + defined using the same coordinate system.

+ +

When an image of some kind is supplied within either a zone or a surface, the implication + is that the image represents the whole of the zone or surface concerned. In the simple case + therefore, we might imagine a surface defining a page, within which there is a graphic + representing the whole of that page, and a number of zones defining parts of the page, each + with its own graphic, each representing a part of the page. If however one of those + graphics actually represents an area larger than the page (for example to include a binding + or the surface of a desk on which the page rests), then it will be enclosed by a zone with + coordinates larger than those of the parent surface.

+ + +

For example, consider the following figure:

+ + + Badische Landesbibliothek, Manuscript Durlach 1, Fols. 95v-96r +
This is an image of a two page spread from a manuscript in the Badische + Landesbibliothek, Karlsruhe. We have no information as to the dimensions of the original + object, but the low resolution image displayed here contains 500 pixels horizontally and + 321 pixels vertically. For convenience, we might map each pixel to one cell of the + coordinate space.The coordinate space used here is based on pixels, + but the mapping between pixels and units in the coordinate space need not be one-to-one; + it might be convenient to define a more delicate grid, to enable us to address much + smaller parts of the image. This can be done simply by supplying appropriate values for + the attributes which define the coordinate space; for example doubling them all would + map each pixel to two grid points in the coordinate space. +

+ +

We therefore define a surface element corresponding with the area of the image + which represents the whole of the two page spread and embed the graphic within it: + + + +

+ + + +

If desired, the binaryObject element described in (or any + other element from the model.graphicLike class) may be used + instead of a graphic element.

+ +

Since the image in this example is of a two page opening, we will probably wish to define + at least two nested zones, one for each page: + + + + + + + + + + + + + + +

+

As this example shows, in addition to acting as a container for graphic elements, + zone elements may be used to identify parts of a surface for analytical + purposes.

+

The relationship between zone and surface can be quite complex: for example, it may be + appropriate to treat the whole of a two page spread as a single written surface, perhaps + because particular written zones span both pages. A zone may contain a nested surface, if + for example a page has an additional scrap of paper attached to it. A zone may be of any + shape, not simply rectangular. Discussion of these and other cases are provided in section + below.

+ + +

In the following extended example, we discuss a hypothetical digital edition of an early + 16th century French work, Charles de Bovelles' Géometrie Pratique.The image is taken from the collection at , and was digitized from a copy in the + Bibliothèque Municipale de Lyon, by whose kind permission it is included here. In + this edition, each page has been digitized as a separate file: for example, recto page 49 + is stored in a file called Bovelles-49r.png. In the + facsimile element used to contain the whole set of pages, we define a + surface element for this page, which we situate within a coordinate scale + running from 0 to 200 in the x (horizontal) axis, and 0 to 300 in the y (vertical) axis. + The surface element contains a graphic element which represents the whole + of this surface: + + + + We can now identify distinct zones within the page image using the + coordinate scale defined for the surface. In the following figure we show the upper part of the page, with boxes indicating four such zones. Each of these + will be represented by a zone element, given within the surface element + already defined, and specified in terms of the same coordinate system. Some zones of + interest are indicated by red lines in the following image.

+ + Detail of p 49r from Bovelles Géometrie Pratique +
The following encoding defines each of the four zones identified in the figure + above. + + + + + + + + + + + + + Note that the location of each zone is defined independently but + using the same coordinate system.

+ +

A non rectangular-zone, for example that containing the word cloche. + at bottom left of the page, could also be defined, using the points attribute: + + + + + + +

+ + +

In the examples above a single graphic element has been associated directly with the + surface of the page rather than nesting it within a zone. However, it is also possible to + include multiple zone elements which contain a graphic element, if for + example a detailed image is available. Since all zone elements use the same + coordinate system (that defined by their parent surface), there is no need to + demonstrate enclosure of one zone within another by means of nesting. To continue the + current example, supposing that we have an additional image called + Bovelles49r-detail.png containing an additional image of the figure in the + third zone above, we might encode that zone as follows: + + + + +

+ + +

Within a surface or zone, individual lines can be identified using the + path element, which also carries the points + attribute: +

+ + Smaller detail of p 49r from Bovelles highlighting two specific lines +
+ + + + + + + + This is useful for linking an annotation or explanation to a specific line on + an object surface. Any number of coordinates can be included to specify lines + which are not straight; this example shows how the first of the famous + story lines appearing at the beginning of chapter 40 of + Tristram Shandy might be encoded: + +
+ + Page 152 of Tristram Shandy +
+ + + + + + +

+ +
+
+ Combining Transcription with Facsimile + +

A digitized source document may contain nothing more than page images and a small amount of + metadata. It may also contain an encoded transcription of the pages represented, which may + either be embedded within a sourceDoc element, or supplied in parallel with + a facsimile as defined above.

+

If the transcription is regarded as a text in its own right, organized and structured + independently of its physical realization in the document or documents represented by the + facsimile, then the recommended practice is to use the text element to contain + such a structured representation, and to present it in parallel. The text element + is a sibling of the facsimile and sourceDoc elements. This approach is + illustrated in section below. Alternatively, if the transcription + is intended not to prioritize representation of the final text so much as the process by + which the document came to take its present form, or the physical disposition of its + component parts, it can be presented as an embedded transcription, as further described + in section below.

+
+ Parallel Transcription + +

Suppose now that we wish to align a transcription of the page discussed in the preceding + section with particular zones. We begin by giving each relevant part of the facsimile an + identifier: + + + + + + + + + + + + + + + + + The alignment between transcription and image is made, as usual, + by means of the facs attribute: + + De Geometrie 49 + DU SON ET ACCORD DES CLOCHES ET des alleures des + chevaulx, chariotz & charges, des fontaines:& encyclie du monde, + & de la dimension du corps humain. Chapitre septiesme +

+

Le son & accord des cloches pendans en ung mesme axe, est faict en + contraires parties.

+

LEs cloches ont quasi figures de rondes + pyramides imperfaictes & irregulieres: & leur accord se + fait par reigle geometrique. Comme si les deux cloches C & D + sont pendans à ung mesme axe ou essieu A B: + je dis que leur accord se fera en contraires parties + comme voyez icy figuré. Car quand lune sera en + hault, laultre declinera embas. Aultrement si elles declinent toutes deux + ensembles en une mesme partie, elles seront discord, & sera leur + sonnerie mal plaisante à oyr.

+ +

+
+ +

+ +

It is also possible to point in the other direction, from a surface or + zone to the corresponding text. This is the function of the start + attribute, which supplies the identifier of the element containing at least the start of + the transcribed text found within the surface or zone concerned. Thus, another way of + linking this page with its transcription would be simply + + + + + + +

+ + + De Geometrie 49 + +
+ + +

+ + + + + + + + + + + + + + + +
+ +
+ Embedded Transcription +

An embedded transcription is one in which words and other written traces + are encoded as subcomponents of elements representing the physical surfaces carrying + them rather than independently of them.

+

The following elements are available for this purpose: + + + + + + + +

+ +

The elements surface, surfaceGrp, and zone were introduced + above in section . When supplied within a sourceDoc + element, these elements may contain transcriptions of the written content of a source in + addition to or as an alternative to digital images of them. Such transcription may be + placed directly within the zone element, or within one or more line + elements, for cases where the writing is linear, in the sense that it is composed of + discrete tokens organized physically into groups, typically organized in a sequence + corresponding with the way they are intended to be read. Depending on the directionality + of the writing system used, this might be any combination of top-down and left to right, + or vice versa. The element line may be used to hold a complete group of such + tokens. Where, however, the lineation is not considered significant, any group of tokens + may be indicated using the zone element. The seg element described in + section may also be used to indicate smaller sequences of tokens + within zone, or line as appropriate.

+ +

Returning to the preceding example, we might transcribe the content of the zone to which + we gave the identifier B49rPara2 within a sourceDoc element as + follows:

+ + + + + + + + LEs cloches ont quasi + figures de rondes pyramides imperfaictes & + irregulieres: & leur accord se + fait par reigle geometrique. Comme si les deux cloches C + & D sont pendans à ung mesme axe ou essieu A B: je dis que + leur accord se fera en cõtraires parties cõme + voyez icy figuré. Car quãd lune sera en hault, laultre + declinera embas. Aultrement si elles declinent toutes deux ensembles en une + mesme partie, elles seront discord, & sera leur sonnerie + mal plaisante à oyr. + + + + +

As mentioned above, some or all of the written surfaces being transcribed may be + composed of physically distinct scraps. In the following example, taken from the Walt + Whitman Archive, two pieces of newsprint have been glued to a piece of blue paper on + which a poem is being drafted:

+ + Single leaf of notes possibly related to the poem eventually titled + Sleepers. From the Walt Whitman Archive (Duke 258). +
The two pieces of newsprint might simply be regarded as special kinds of zone, + but they are also new surfaces, since they might contain additional written zones + themselves (such as the numbers in this case).

+ +

Using these elements, the Whitman draft above might be encoded as follows: + + + Poem + As in Visions of — at + night — + All sorts of fancies running through + the head + + + + Spring has just set in here, and the weather[...] a steamer + 2 + + + + + "The shores on either side of the Sound are... The In- + 3 + + + + +

+ +

The metamark element used in this example is further discussed below ()

+ +

Note that in this example we have not included any graphic element + corresponding with the zone or surface elements identified in the + transcription. The encoder may choose to complement a transcription with graphic + representations of its source at whatever level is considered effective, or not at all. + Equally, the encoder may choose to provide only graphics without any transcription, to + provide only a structured (non-embedded) transcription, or to provide any combination of + the three.

+

This example also lacks any coordinate information to specify either the size of the two + newspaper fragments or whereabouts on the parent surface element they are to be + found, other than the reading order implicit in their sequence. Such information could + be added if desired by specifying a coordinate system on the outermost surface + element, and then indicating values within that system for each of the two fragments, as + was discussed above. We discuss this in further detail in section below.

+ +
+ Advanced Uses of surface and zone + +

As a child of sourceDoc, the surface element both identifies a specific area + containing writing and provides a two dimensional set of coordinates which can be used to position + and define dimensions for sub-parts of it. Furthermore, surfaces may nest within other + surfaces, as in the case of patches or other written materials attached to the main + writing surface. In the general case, the position and dimensions of such nested surfaces + will be defined using the same coordinate system as that supplied by the parent + surface element. It is also possible, however, that a different coordinate + system is required for such a nested surface, perhaps because it requires a more complex + granularity. We consider both possibilities.

+ +

In the earlier examples showing nested examples we did not provide any coordinate + information, for simplicity of presentation. Suppose however, that we wish to indicate the + position and sizes of the newspaper scraps in above, relative to + the whole page. As previously noted, the four attributes ulx, uly, + lrx and lry when given on the surface element define the + coordinate scheme, rather than specifying the location of that surface. We must therefore + introduce an additional zone element, as in the following revised encoding for + this example + + + Poem + As in Visions of — at + night — + All sorts of fancies running through + the head + + + + Spring has just set in here, and the weather[...] a steamer + 2 + + + In this version of the encoding, the inner surface, corresponding + with the first piece of newsprint, inherits locational information from the zone + element that contains it. This zone, and the preceding one, which contains a sequence of + line elements, are both positioned in terms of the coordinates specified on the + outermost surface element, which defines a scale running from 0 to 50 in either + direction. On that scale, the line elements occupy a rectangle with coordinates + (1,1,10,10), while the nested surface occupies a rectangle with coordinates + (4,4,20,20).

+

Now suppose that we wish to define a finer scale grid for the newspaper patch, perhaps + because we wish to localize zones within it with greater accuracy. To do this we will need + to specify the position of the nested surface as in the previous example, but also to + define the new coordinate system. We accomplish this as follows: + + + Poem + + the head + + + + Spring has just set in here, and the + weather [...] a steamer + + + As before, the second zone defines the position and size of the + newspaper patch itself in terms of a coordinate system running from 0 to 50 on both X and Y + axes. The nested surface element however defines a new scale for all of its + components, running from 0 to 100 on both X and Y axes. The position of the nested zone + containing the text Spring ... steamer is now given in terms of this + scale.

+ +

All of the examples so far given have involved rectangular zones, for clarity of + exposition. As noted above, the points attribute may be used to define + non-rectangular zones as a series of points. For example, in the last of the Whitman + examples discussed in section above, we might wish to record the + exact shape of the zone containing the metamark Entered. Since this + is not a rectangular zone, we use the points attribute to indicate the points + defining a polygon which contains it. The values used are expressed in terms of a + coordinate space running from 0 to 229 in the X dimension, and 0 to 160 in the Y dimension.

+ + + + + + + + +

In exactly the same way, we may wish to identify the curved zone in the following image + containing the word Northamptonshire:

+ + Gravestone of Private Moulds +
This curved zone might be encoded in the following way: + + + + + +

+

Finally, it should be noted that a zone does not need to be entirely contained + within the two-dimensional space defined by its parent surface. For example, we might wish + to encode the example in above not as a surface representing the + whole of the two page spread, but as a surface representing only the written part of this + opening. The written part appears 50 units from the left of the image and 20 units from the + top, while the bottom right corner of the written part appears 400 units from the left of + the image, and 280 units from the top. We therefore define the written surface within this + image as follows: + + + + To describe the whole image, we will now need to define a zone of + interest which represents an area larger than this surface. Using the same coordinate + system as that defined for the surface, its coordinates are 0,0,500,321. This + zone of interest can be defined by a zone element, within which we can place the + uncropped graphic: + + + + + +

+ +
+
+ +
+ +
+ Scope of Transcriptions + +

When transcribing a primary source, whether using text or sourceDoc, + scholars may wish to record information concerning + individual readings of letters, words, or larger units.They + may also wish to include other editorial material, such as comments on the status or + possible origin of particular readings, corrections, or text supplied to fill lacunae.

+ +

Such elements may also be used for digital transcriptions in which the object is not to + represent a finished text, but rather to represent the creative process, as evidenced by + different layers or traces of writing in one or more documents. + Transcriptions of this kind are closely focussed on the physical appearance of specific + documents, needing to distinguish the traces of different writing activities on them, such + as additions and deletions but also other indications of how the writing is to be read, + such as indications of transposition, re-affirmation of writing which has been deleted, and + so on. Such distinctions are considered of particular importance when dealing with + authorial manuscripts, but are also relevant in the case of historical sources such as + charters or other legal documents.

+ +

In either case, it is customary in transcriptions to register certain features of the + source, such as ornamentation, underlining, deletion, areas of damage and lacunae. This + chapter provides ways of encoding such information: + methods of recording editorial or other alterations to the text, such as expansion + of abbreviations, corrections, conjectures, etc. (section ) + methods of describing important extra-linguistic phenomena in the source: unusual + spaces, lines, page and line breaks, changes of manuscript hand, etc. (section ) + methods of representing aspects of layout such as spacing or lines + + methods of representing material such as running heads, catch-words, and the like + (section ) +

+ + +

The remainder of this chapter describes a model for encoding such transcriptions, in which + elements such as mod, del, etc. are used to mark writing traces and their + functions within the document. Each such element can be assigned to one or more + editorially-defined modification groups, termed a change, by means of a global + change attribute, which references a definition for the modification group + concerned, typically provided within the TEI header creation element; see further + . The transcription itself may be embedded within the + elements surface and zone described in section , or + provided in parallel within a text element. Within a zone, the + transcription may be organized topographically in terms of lines of writing, using the + line element, or in terms of further nested zones, or as a combination of the + two ().

+ + + +

These recommendations are not intended to meet every transcriptional circumstance likely to + be faced by any scholar. Rather, they should be regarded as a base which can be elaborated + if necessary by different scholars in different disciplines

+ + +

As a rule, all elements which may be used in the course of a transcription of a single + witness may also be used in a critical apparatus, i.e. within the elements proposed in + chapter . This can generally be achieved by nesting a particular reading + containing tagged elements from a particular witness within the rdg element in an + app structure.

+

Just as a critical apparatus may contain transcriptional elements within its record of + variant readings in various witnesses, one may record variant readings in an individual + witness by use of the apparatus mechanisms app and rdg. This is discussed + in section .

+ +
+ Altered, Corrected, and Erroneous Texts + +

In the detailed transcription of any source, it may prove necessary to record various + types of actual or potential alteration of the text: expansion of abbreviations, + correction of the text (either by author, scribe, or later hand, or by previous or + current editors or scholars), addition, deletion, or substitution of material, and + similar matters. The sections below describe how such phenomena may be encoded using + either elements defined in the core module (defined in chapter ) or + specialized elements available only when the module described in this chapter is + available.

+ +
+ Core Elements for Transcriptional Work +

In transcribing individual sources of any type, encoders may record corrections, + normalizations, additions, and omissions using the elements described in section . Representation of abbreviations and their expansions may also + involve use of elements described in section . Elements + particularly relevant to this chapter include: + + + + + + + + + +

+

All of these elements bear additional attributes for specifying who is responsible + for the interpretation represented by the markup, and the associated certainty. In + addition, some of them bear an attribute allowing the markup to be categorized by + type and source. + + + + + The specific aspect of the markup described by these attributes differs + on different elements; for further discussion, see the relevant sections below, + especially section .

+

The following sections describe how the core elements just named may be used in the + transcription of primary source materials.

+
+ +
+ Abbreviation and Expansion + +

The writing of manuscripts by hand lends itself to the use of abbreviation to shorten + scribal labour. Commonly occurring letters, groups of letters, words, or even whole + phrases, may be represented by significant marks. This phenomenon of manuscript + abbreviation is so widespread and so various that no taxonomy of it is here + attempted. Instead, methods are shown which allow abbreviations to be encoded using + the core elements mentioned above.

+

A manuscript abbreviation may be viewed in two ways. One may transcribe it as a + particular sequence of letters or marks upon the page: thus, a p with a bar + through the descender, a superscript hook, a macron. One may + also interpret the abbreviation in terms of the letter or letters it is seen as + standing for: thus, per, re, n. Both of these views are + supported by these Guidelines.

+ +

In many cases the glyph found in the manuscript source also exists in the Unicode + character set: for example the common Latin brevigraph ⁊, standing for + et and often known as the Tironian et + can be directly represented in any XML document as the Unicode character with code + point U+204A (see further and ). In cases where it does not, these Guidelines recommend use of the g + element provided by the gaiji module described in + chapter . This module allows the encoder great flexibility both in + processing and in documenting non-standard characters or glyphs, including the + ability to provide detailed documentation and images for them.

+ +

These two methods of coding abbreviation may also be combined. An encoder may record, + for any abbreviation, both the sequence of letters or marks which constitutes it, and + its sense, that is, the letter or letters for which it is believed to stand. For + example, in the following fragment the phrase euery persone is + represented by a sequence of abbreviated characters:

+ + Detail from fol. 126v of Bodleian MS Laud Misc 517 +
These lines may be transcribed directly, using the g element to + indicate the two brevigraphs as follows: euery persone that loketh after heuen hath a place in + this ladder + + + + + + + + Note that in each case the g element may contain a + suggested replacement for the referenced brevigraph; this is purely advisory however, + and may not be appropriate in all cases. The referenced character definitions may be + located elsewhere in this or some other document, typically forming part of a + charDecl element, as described in .

+ +

The transcriber may also wish to indicate that, because of the presence of these + particular characters, the two words are actually abbreviations, by using the + abbr element: euery + persone ... Alternatively, the + transcriber may choose silently to expand these abbreviations, using the + expan element: euery + persone ... And, of course, the choice element + can be used to show that one encoding is an alternative for the other: eueryeuery +

+

When abbreviated forms such as these are expanded, two processes are carried out: + some characters not present in the abbreviation are added (always), and some + characters or glyphs present in the abbreviation are omitted or replaced (often). For + example, when the abbreviation Dr. is expanded to + Doctor, the dot in the abbreviation is removed, and the + letters octo are added. Where detailed markup of abbreviated + words is required, these two aspects may be marked up explicitly, using the following + elements: + + + Using these elements, a transcriber may indicate the status of the + individual letters or signs within both the abbreviation and the expansion. The + am element surrounds characters or signs such as tittles or tildes, used + to indicate the presence of an abbreviation, which are typically removed or replaced + by other characters in the expanded form of the abbreviation: euy + sone ... while the ex + element may be used to indicate those characters within the expansion which are not + present in the abbreviated form. euery + persone ... The content of the abbr + element should usually include the whole of the abbreviated word, while the + expan element should include the whole of its expansion. If this is not + considered necessary, the am and ex elements may be used within a + choice element, as in this example: euery persone ... +

+

As implied in the preceding discussion, making decisions about which of these various + methods of representing abbreviation to use will form an important part of an + encoder's practice. As a rule, the abbr and am elements should be + preferred where it is wished to signify that the content of the element is an + abbreviation, without necessarily indicating what the abbreviation may stand for. The + ex and expan elements should be used where it is wished to + signify that the content of the element is not present in the source but has been + supplied by the transcriber, without necessarily indicating the abbreviation used in + the original. The decision as to which course of action is appropriate may vary from + abbreviation to abbreviation; there is no requirement that the same system be used + throughout a transcription, although doing so will generally simplify processing. The + choice is likely to be a matter of editorial policy. If the highest priority is to + transcribe the text literatim (letter by letter), while indicating + the presence of abbreviations, the choice will be to use abbr or am + throughout. If the highest priority is to present a reading transcription, while + indicating that some letters or words are not actually present in the original, the + choice will be to use ex or expan throughout.

+

Further information may be attached to instances of these elements by the + note element, on which see section , and by use of + the resp and cert attributes. In this instance from the English + Brut, a note is attached to an editorial expansion of the tail on + the final d of good to goode: For alle the while + that I had goode I was welbeloued + Then the note: The stroke added to + the final d could signify the plural ending (-es, -is, -ys>) but the + singular goode was used with the meaning property, + wealth, at this time (v. examples quoted in OED, sb. Good, C. 7, b, + c, d and 8 spec.) The editor might declare a degree of certainty + for this expansion, based on the OED examples, and state the responsibility for the + expansion: For alle the while that I + had goode I was welbeloued The value + supplied for the resp attribute should point to the name of the editor + responsible for this and possibly other interventions; an appropriate element + therefore might be a respStmt element in the header like the following: + + + Editorial emendations + Malcom Parkes + Observe that the cert and resp + attributes are used with the ex element only to indicate confidence in the + content of the element (i.e. the expansion), and responsibility for suggesting this + expansion respectively.

+

The choice element may be used to indicate that the proposed expansion is + one way of encoding what might equally well be represented as an abbreviation, + represented by the hooked D, as follows: For alle the while that I had + gooɗ + goode I was + welbeloued If it is desired to express aspects of certainty and + responsibility for some other aspect of the use of these elements, then the + mechanisms discussed in chapter should be used. See also for discussion of the issues of certainty and responsibility in + the context of transcription.

+ +

If more than one expansion for the same abbreviation is to be recorded, multiple + notes may be supplied. It may also be appropriate to use the markup for critical + apparatus; an example is given in section .

+
+ + +
+ Correction and Conjecture + +

The sic, corr, and choice elements, defined in the core module should be used to indicate passages deemed in + need of correction, or actually corrected, during the transcription of a source. For + example, in the manuscript of William James's A Pluralistic Universe + as edited by Fredson Bowers (Cambridge: Harvard University Press, 1977), a sentence + first written One must have lived longer with this system, to + appreciate its advantages. has been modified by James to begin But One must + ..., without the initial capital O having been reduced to lowercase. This + non-standard orthography could be recorded thus: But One must have lived + ... or corrected: But + one must have lived ... or the two possibilities might be + represented as a choice: But + Oneone must have lived + ...

+

Similarly, in this example from Albertus Magnus, both a manuscript error + angues and its correction augens are + registered within a choice element: Nos autem iam + ostendimus quod nutrimentum et + anguesaugens. +

+

Note that the corr element is used to provide a corrected form which is + not present in the source; in the case of a correction made in the + source itself, whether scribal, authorial, or by some other hand, the add, + del, and subst elements described in + should be used.

+

The sic element is used to mark passages considered by the transcriber to be + erroneous; in such cases, the corr element indicates the transcriber's + correction of them. Where the transcriber considers that one or more words have been + erroneously omitted in the original source and corrects this omission, the + supplied element discussed in should be used in + preference to corr. Thus, in the following example, from George Moore's + draft of additional materials for Memoirs of My Dead Life, the + transcriber supplies the word we omitted by the author: You see that I avoid + the word create for we create nothing we develope. +

+

As with expan and abbr, the choice as to whether to record simply + that there is an apparent error, or simply that a correction has been applied, or to + record both possible readings within a choice element is left to the + encoder. The decision is likely to be a matter of editorial policy, which might be + applied consistently throughout or decided case by case. If the highest priority is + to present an uncorrected transcription while noting perceived errors in the + original, the choice will typically be to use only sic throughout. If the + highest priority is to present a reading transcription, while indicating that + perceived errors in the original have been corrected, the choice will be to use only + corr throughout.

+ +

Further information may be attached to instances of these elements by the + note element and resp and cert attributes. + Instances of these elements may also be classified according to any convenient + typology using the type attribute.

+

For example, consider the following encoding of an emendation in the Hengwrt + manuscript proposed by E. Talbot Donaldson: Telle me also, to what conclusioun Were + membres maad, of generacioun And of so parfit wis a wightwright ywroght? + This emendation of the Hengwrt copy text, based on a Latin + source and on the reading of three late and usually unauthoritative + manuscripts, was proposed by E. Talbot Donaldson in + Speculum 40 (1965) 626–33. + The note element discussed in may be used to + give a more detailed discussion of the motivation for or scope of a correction. If + linked by means of a pointer (as in this example) it may be located anywhere + convenient within the transcription; typically all detailed notes will be collected + together in a separate div element in the back. Alternatively, the + pointer may be omitted, and the note placed immediately adjacent to the + element being annotated. The advantage of the former solution is that it permits the + same annotation to refer to several corrections, by supplying more than one pointer + in the target attribute of the note, as shown in the example + below.

+

The attribute cert may be used to indicate the degree of confidence + ascribed by the encoder to the proposed emendation on a broad scale: high, medium, or + low. The attribute resp is used to indicate who is responsible for the + proposed emendation. Its value is a pointer, which will typically indicate a + respStmt or name element in the header of the transcribed + document, but can point anywhere, for example to some online authority file. Using + these two attributes, the corr element presented above might usefully be + enhanced as follows: + + E Talbot Donaldson + And of so parfit wis a wightwright ywroght?

+ +

As remarked above, where the same annotation applies to several corrections, this may + be represented by supplying multiple pointers on the note. Consider for example such + corrections as the following, in Dudo of S. Quentin. Parkes cites two cases in this + manuscript of the same phenomenon: quamuis mensiners que nutu dei gesta + sunt ... unde esset uiriliter uegetatanegata which may be + described as follows: Substitution of a more familiar word which resembles + graphically what the scribe should be copying but which does not make sense in + the context. +

+

The target attribute on the note element indicates the + choice elements which exemplify this kind of scribal error. This + necessitates the addition of an identifier to each choice element. However, + if the number of corrections is large and the number of notes is small, it may well + be both more practical and more appropriate to regard the collection of annotations + as constituting a typology and then use the type attribute. Suppose that + the note given above is one of half a dozen possible kinds of corrected phenomena + identified in a given text; others might include, say, repetition of a word from + the preceding line, etc. The type attribute on the corr + element can be used to specify an arbitrary code for the particular kind of + correction (or other editorial intervention) identified within it. This code can be + chosen freely and is not treated as a pointer. quamuis mensiners que nutu dei gesta sunt ... unde + esset uiriliter uegetatanegata Note that this encoding + might be extended to include a range of possible corrections: quamuis mensinersinres que + nutu dei gesta sunt ... In addition, the conscientious encoder will + provide documentation explaining the circumstances in which particular codes are + judged appropriate. A suitable location for this might be within the + correction element of the encodingDesc of the header, which + might include a list such as the following: + +

The following codes are used to categorize corrections identified in this + transcription: + + Substitution of a more familiar word which resembles graphically + what the scribe should be copying but which does not make sense in the + context. + +

A subtype attribute may be used + in conjunction with the type for subclassification purposes: the above + examples might thus be represented as choice type="substitution" + subtype="graphicResemblance" for example.

+

For a given project, it may well be desirable to limit the possible values for the + type or subtype attributes automatically. This is easily + done but requires customization of the TEI system using techniques described in , in particular , which should be consulted + for further information on this topic.

+

When making a correction in a source which forms part of a textual tradition attested + by many witnesses, a textual editor will sometimes use a reading from one witness to + correct the reading of the source text. In the general case, such encoding is best + achieved with the mechanisms provided by the module for textual criticism described + in chapter . However, for simple cases, the source + attribute of the corr element may suffice. In the passage from Chaucer's + Wife of Bath's Tale mentioned above, Parkes proposes to emend the + problematic word wight to wyf which is + the reading found in the Cambridge manuscript Gg.1. 27. This may be simply + represented as follows: And of so + parfit wis a wightwyf ywroght? The value of the source + attribute here is, like the value of the resp attribute, a pointer, in + this case indicating the manuscript used as a witness. Elsewhere in the transcribed + text, a list of witnesses used in this text will be given, one of which has an + identifier Gg. Each witness will be represented either by a + witness element (see ) or more fully by an + msDesc element (see ): + + + Cambridge + University Library + Gg.1. 27 + + + +

+ +

The app element described in chapter provides a more + powerful way of representing all three possible readings in parallel: And of so parfit wis a + wight + wright + wyf +

+

This encoding simply records the three readings found in the various traditions, and + gives (by means of the wit attribute) an indication of the witnesses + supporting each. If the resp attribute were supplied on the rdg + element, it would indicate the person responsible for asserting that the manuscript + indicated has this reading, who is not necessarily the same as the person responsible + for asserting that this reading should be used to correct the others. Editorial + intervention elements such as corr can however be nested within a + rdg to provide this additional information: And of so parfit wis a + wight + wright + wyf + This encoding asserts that the reading wyf + found in Gg is regarded as a correction by Parkes.

+ +

Like the resp attribute, the cert attribute may be used with + both corr and rdg elements. When used on the rdg element, + these attributes indicate confidence in and responsibility for identifying the + reading within the sources specified; when used on the corr element they + indicate confidence in and responsibility for the use of the reading to correct the + base text. If no other source is indicated (either by the source + attribute, or by the wit attribute of a parent rdg), the reading + supplied within a corr has been provided by the person indicated by the + resp attribute.

+ +

If it is desired to express certainty of or responsibility for some other aspect of + the use of these elements, then the mechanisms discussed in chapter may be found useful. See also for further discussion of the + issues of certainty and responsibility in the context of transcription.

+
+ +
+ Additions and Deletions + +

Additions and deletions observed in a source text may be described using the + following elements: + + + + + Of these, add and del are included in the core module, + while addSpan and delSpan are available only when using the module + defined in this chapter. These particular elements are members of the att.spanning class, from which they inherit the following + attribute: + + +

+ +

Further characteristics of each addition and deletion, such as the hand used, its + effect (complete or incomplete, for example), or its position in a sequence of such + operations may conveniently be recorded as attributes of these elements, all of which + are members of the att.transcriptional class: + + +

+ + +

As described in section , the add element is used to + record any manuscript addition observed in the text, whether it is considered to be + authorial or scribal. In the autograph manuscript of Max Beerbohm's The Golden + Drugget, the author's addition of do ever may be + recorded as follows, with the hand attribute indicating that the addition + was Beerbohm's by referencing a handNote element defined elsewhere in the + document (see further ): Some things are best + at first sight. Others — and here is one of them — do ever + improve by recognition [...] Max Beerbohm + holograph + +

+ +

The del element is used to record manuscript deletions in a similar way. In + the autograph manuscript of D. H. Lawrence's Eloi, Eloi, lama + sabachthani the author's deletion of my may be + recorded as follows. In this case, the hand attribute indicating that the + deletion was Lawrence's is complemented by a rend attribute indicating + that the deletion was by strike-through: For I hate this my body, which is so dear to me ... + D H Lawrence holograph +

+ + +

If deletions are classified systematically, the type attribute may be + useful to indicate the classification; when they are classified by the manner in + which they were effected, or by their appearance, however, this will lead to a + certain arbitrariness in deciding whether to use the type or the + rend attribute to hold the information. In general, it is recommended + that the rend attribute be used for description of the appearance or + method of deletion, and that the type attribute be reserved for higher + level or more abstract classifications.

+ +

The place attribute is also available to indicate the location of an + addition. For example, consider the following passage from a draft letter by Robert + Graves:

+ + Draft letter from Robert Graves to Desmond Flower, 17 Dec 1938 (detail). + +
At the end of this extract, the writer inserts the word cant, above + the line, with a stroke to indicate insertion. Assuming that we have previously + defined the identifier RG somewhere: + + + + + + , this extract might now be encoded as follows: The O.E.D. is not a + dictionary so much as a corpus of precedents in the: + current, obsolete, cant, cataphretic and + nonce-words are all included. A little earlier in the same extract, + Graves writes for an abridgement above the line, and then deletes it. This may + be encoded similarly: As for 'significant artist.' You quote the O.E.D for an abridgement in explanation... + Similarly, in the margin, the word Norton has been added and then + deleted: You + quote the Norton O.E.D... + The word O.E.D. in this first sentence has also clearly been the result of + some redrafting: it may be that Graves started to write Oxford, and then + changed it; it may be that he inserted other punctuation marks between the letters + before replacing them with the centre dots used elsewhere to represent this acronym. + We do not deal with these possibilities here, and mention them only to indicate that + any encoding of manuscript material of this complexity will need to make decisions + about what is and is not worth mentioning.

+ + + + + +

An encoder may also wish to indicate that an addition replaces a specific deletion, + that is to encode a substitution as a single intervention in the text. This may be + achieved by grouping the addition and deletion together within a subst + element. At the end of the passage illustrated above, Graves first writes It is + the expressed..., then deletes It is, and substitutes an uppercase T at + the start of the. ... are all included. It is + Tthe expressed The use of this + element and of the seq attribute to indicate the order in which + interventions such as deletions are believed to have occurred are further discussed + in section below.

+ +

The add and del elements defined in the core module suffice only + for the description of additions and deletions which fit within the structure of the + text being transcribed, that is, which each deletion or addition is completely + contained by the structural element (paragraph, line, division) within which it + occurs. Where this is not the case, for example because an individual addition or + deletion involves several distinct structural subdivisions, such as poems or prose + items, or otherwise crosses a structural boundary in the text being encoded, special + treatment is needed. The addSpan and delSpan elements are provided + by this module for that purpose. (For a general discussion of the issue see further + ).

+ +

In this example of the use of addSpan, the insertion by Helgi Ólafsson of a + gathering containing four neo-Eddic poems into Lbs 1562 4to is + recorded as follows. A handNote + element is first declared, within the header of the document, to associate the + identifier heol with Helgi. Each of the added poems is encoded as a + distinct div element. In the body of the text, an addSpan element + is placed to mark the beginning of the span of added text, and an anchor is + used to mark its end. The hand attribute on the addSpan element + ascribes responsibility for the addition to the manuscript to Helgi, and the + spanTo attribute points to the end of the added text: + + +

+ +
+
+
+
+ +
+

+

The delSpan element is used in the same way. An authorial manuscript will + often contain + several + occasions where sequences of whole lines are marked for deletion, either by boxes or + by being struck out. If the encoder is marking up individual verse lines with the + l element, such deletions are problematic: deletion of two consecutive + lines should be regarded as a single deletion, but the del element must be + properly nested within a single l element. The delSpan element + solves this problem: + Flowed up the hill and down King William Street, + + To where Saint Mary Woolnoth kept the time, + With a dead sound on the final stroke of nine. + + There I saw one I knew, and stopped him, crying "Stetson!... +

+

It is also often the case that deletions and additions may themselves contain other + deletions and additions. For example, in Thomas Moore's autograph of the second + version of Lalla Rookh two lines are marked for omission by vertical + strike-through. Within the first of the two lines, the word + upon has also been struck out, and the word + over has been added: + Tis moonlight + upon + over Oman's sky + Her isles of pearl look lovelily In this + case the anchor and delSpan have been placed within the structural + elements (the ls) rather than between, as in the previous example. This is + to indicate that placement of these empty elements is arbitrary.

+

The text deleted must be at least partially legible, in order for the encoder to be + able to transcribe it. If all of part of it is not legible, the gap element + should be used to indicate where text has not been transcribed, because it could not + be. The unclear element described in section may be + used to indicate areas of text which cannot be read with confidence. See further + section and section .

+
+ +
+ Substitutions + +

Substitution of one word or phrase for another is perhaps the most common of all + phenomena requiring special treatment in transcription of primary textual sources. It + may be simply one word written over the top of another, or deletion of one word and + its replacement by another written above it by the same hand on the same occasion; + the deletion and replacement may be done by different hands at different times; there + may be a long chain of substitutions on the same stretch of text, with uncertainty as + to the order of substitution and as to which of many possible readings should be + preferred.

+

As we have shown, the simplest method of recording a substitution is simply to record + both the addition and the deletion. However, when the module defined by this chapter + is in use, additional elements are available to indicate that the encoder believes + the addition and the deletion to be part of the same intervention: a substitution. + + + Using the subst element, the example at the end of the last + section might be encoded as follows: + Tis moonlight + uponover Oman's sky + Her isles of pearl look lovelily Since + the purpose of this element is solely to group its child elements together, the order + in which they are presented is not significant. When both deletion and addition are + present, it may not always be clear which occurs first: using the seq + attribute is a simple way of resolving any such ambiguities.

+ +

For example, returning to the example from William James, in a passage first written + out by James as One must have lived longer with this system, to appreciate its + advantages, the word this is first replaced by + such a and this is then replaced by + a.The manuscript contains several + other substitutions, ignored here for the sake of clarity. This may be + encoded as follows, representing the two changes as a sequence of additions and + deletions: One must have lived longer + with this + such a + a system, to appreciate its advantages. Note + the nesting of an add element within a del to record text first + added, then deleted in the source. The numbers assigned by the seq + attribute may be used to identify the order in which the various additions and + deletions are believed by the encoder to have been carried out, and thus provide a + simple method of supporting the kind of genetic textual + criticism typified by (for example) Hans Walter Gabler's work on the reconstruction + of the overlay levels implicit in the manuscripts of James + Joyce's Ulysses. A fuller and more complex way of supporting such an + approach is discussed in .

+ +

A special case of a substitution may consist of a superfluous word + or phrase that is silently replaced by some addition. E.g. a scribe + abandons a word (without indicating it should be deleted), and then + writes a replacement word immediately after. Here the encoder may + interpret this as an unmarked deletion which can + then be combined with a corresponding addition to a substitution.

+ +

The case of a single substitution or scribal correction that involves non-contiguous + addition and deletion can be handled by using the substJoin element to make + an explicit connection between one or more add and del elements. In + the following example from Thomas Moore's Lalla Rookh, the deletion and addition are + not contiguous: they are separated by the word thus, which is not part of the + scribal intervention being marked. Because of this intervening text, it would be + inappropriate to use subst to group this add and del. + substJoin allows the encoder to indicate that additions and deletions + separated in this way are part of a single scribal intervention: While pondering thus she mus'd, her pinions + fann'd + Note that, unlike subst, the placement of the substJoin is + arbitrary. It may occur before or after the relevant add and del + elements.

+ +

As a more complex example, consider the following passage: +

+ + Detail from Dulce et decorum est autograph manuscript in the + English Faculty Library, Oxford University. +
This passage might be encoded as follows: + And towards our distant rest began to trudge, + Helping the worst amongst usDragging the worst amongt + us, who'd no boots + But limped on, blood-shod. All went lame; half-all blind; + Drunk with fatigue ; deaf even to the hoots + Of tired, outstripped fif five-nines that dropped + behind. In this representation, + the authorial slip (amongt for + amongst) is retained without comment. + the other two authorial corrections are marked as substitutions, each + combining a deletion and an addition. + the false start fif in the last line is simply marked + as a deletion; + +

+

The app element presented in chapter provides similar + facilities, by treating each state of the text as a distinct reading. The + rdg element has a varSeq attribute which may be used in the + same way as the seq attribute to indicate the preferred sequence. The + James example above might thus be represented as follows: One must have lived longer with + this + such a + a + system, to appreciate its advantages. +

+
+ +
+ Cancellation of Deletions and Other Markings +

An author or scribe may mark a word or phrase in some way, and then on reflection + decide to cancel the marking. For example, text may be marked for deletion and the + deletion then cancelled, thus restoring the deleted text. Such cancellation may be + indicated by the restore element: + +

+

This element bears the same attributes as the other transcriptional elements. These + may be used to supply further information such as the hand in which the restoration + is carried out, the type of restoration, and the person responsible for identifying + the restoration as such, in the same way as elsewhere.

+

Presume that Lawrence decided to restore my to the phrase of + Eloi, Eloi, lama sabachthani first written For I hate this my + body, with the my first deleted then restored by + writing stet in the margin. This may be encoded: For I hate this my body

+

Another feature commonly encountered in manuscripts is the use of circles, lines, or + arrows to indicate transposition of material from one point in the text to another. + No specific markup for this phenomenon is proposed at this time. Such cases are most + simply encoded as additions at the point of insertion and deletions at the point of + encirclement or other marking.

+
+ +
+ Text Omitted from or Supplied in the Transcription +

Where text is not transcribed, whether because of damage to the original, or because + it is illegible, or for some other reason such as editorial policy, the gap + core element may be used to register the omission; where such text is transcribed, + but the editor wishes to indicate that they consider it to be superfluous, for + example because it is an inadvertent scribal repetition or an interpolation from + another source, the surplus element may be used in preference. Where the + editor believes text to be interpolated but genuine, the secl element may be + used instead. Where text not present in the source is supplied (whether conjecturally + or from other witnesses) to fill an apparent gap in the text, the supplied + element may be used. + + + + +

+

By its nature, the gap element has no content. It marks a point in the text + where nothing at all can be read, whether because of authorial or scribal erasure, + physical damage, or any other form of illegibility. Its attributes allow the encoder + to specify the amount of text which is illegible in this way at this point, using any + convenient units, where this can be determined. For example, in the Beerbohm + manuscript of The Golden Drugget cited above, the author has erased a + passage amounting about 10 cm in length by inking over it completely: Others —and here is one of + them...

+

In an autograph letter of Sydney Smith now in the Pierpont Morgan library three words + in the signature are quite illegible: I am dr Sr yr Sydney Smith The degree of precision attempted when measuring the size + of a gap will vary with the purpose of the encoding and the nature of the material: + no particular recommendation is made here.

+ +

As noted above, the gap element should only be used where text has not been + transcribed. If partially legible text has been transcribed, one of the elements + damage and unclear should be used instead (these elements are + described in section ); if the text is legible and has been + transcribed, but the editor wishes to indicate that they regard it is superfluous or + redundant, then the element surplus may be used in preference to the core + element sic used to indicate text regarded as erroneous.

+ +

Amongst the many examples cited in Hans Krummrey & Silvio Panciera's classic text + on the editing of epigraphic inscriptions is the following. In a late classical + inscription, the form dedikararunt is encountered. The editor + may choose any of the following three possibilities:

+ + mark this as an erroneous form + dedikararunt + + additionally supply a corrected form + dedikararunt + dedikarunt + + + indicate that the erroneous form contains surplus characters which the editor + wishes to suppress dedikararunt + + +

The surplus element may also be used to mark up interpolations, as in the + following example taken from a 13th century Italian source: + a darmi morte, poi m'avete preso a + tradimento + sì com' l'uccellator prende l'uccello + + e lettere dintorno che diriano in questa + guisa + Più v'amo, dëa, che non faccio Deo + The words marked as surplus here are metrically inconsistent with + the rest and have been marked by the editor as such.

+ +

In the case of an interpolation which the editor regards as genuine (i.e. written by + the author in question), but out of its original place, the secl element + should be used instead of surplus. For example: + + + + Great praise and thanks be to Perfidy as she + deserves, since by our swindles, tricks, and clever moves, relying + on the daring of our shoulder blades and the excellence of our + forearms who went against cattle-prods, hot iron-blades, + crosses and shackles, neck-irons, chains, prisons, collars, fetters, + and yokes, the fiercest painters fully acquainted with our backs + who have often before put scars on our shoulder blades + ... + + + + The final line is bracketed in the Loeb edition, with a note: versum secl. + Bothe, meaning Bothe regarded this line as Plautine, but probably + interpolated. It is easy to see how the line might have crept in as a gloss on the + metaphor in the previous line.

+ +

If some part of the source text is completely illegible or missing, an encoder may + sometimes wish to supply new (conjectural) material to replace it. This conjectural + reading is analogous to a correction in that it contains text provided by the encoder + and not attested in the source. This is not however a correction, since no error is + necessarily present in the original; for that reason a different element + supplied should be used. If another (imaginary) copy of the letter above + preserved the signature as reading I am dear Sir your very humble Servt Sydney + Smith, the text illegible in the autograph might be supplied in the + transcription: I am dr Sr yr + very humble + Servt Sydney Smith Here the source and + resp attributes are used, as elsewhere, to indicate respectively the + sigil of a manuscript from which the supplied reading has been taken, and the + identifier of the person responsible for deciding to supply the text. If the + source attribute is not supplied, the implication is that the encoder + (or whoever is indicated by the value of the resp attribute) has supplied + the missing reading. Both gap and supplied may be used in + combination with unclear, damage, and other elements; for + discussion, see section .

+
+
+ +
+ Hands and Responsibility +

This section discusses in more detail the representation of aspects of responsibility + perceived or to be recorded for the writing of a primary source. These include points at + which one scribe takes over from another, or at which ink, pen, or other characteristics + of the writing change. A discussion of the usage of the hand, + resp, and cert attributes is also included.

+
+ Document Hands + +

For many text-critical purposes it is important to signal the person responsible (the + hand) for the writing of a whole document, a stretch of text within a + document, or a particular feature within the document. A hand, as the name suggests, + need not necessarily be identified with a particular known (or unknown) scribe or + author; it may simply indicate a particular combination of writing features + recognized within one or more documents. The examples given above of the use of the + hand attribute with coding of additions and deletions illustrate this.

+ +

The handNote element is used to provide information about each hand + distinguished within the encoded document. + + +

+ +

A handNote element, with an identifier given by its xml:id + attribute, may appear in either of two places in the TEI header, depending on which + modules are included in a schema. When the transcr + module defined by the present chapter is used, the element handNotes is + available, within the profileDesc element of the TEI header, to hold one or + more handNote elements. When the msdescription + module defined in chapter is included, the handDesc + element described in also becomes available as part of a + structured manuscript description. The encoder may choose to place handNote + elements identifying individual hands in either location without affecting their + accessibility since the element is always addressed by means of its xml:id + attribute. The handDesc element may be more appropriate when a full + cataloguing of each manuscript is required; the handNotes element if only a + brief characterization of each hand is needed. It is also possible to use the two + elements together if, for example, the handDesc element contains a single + summary describing all the hands discursively, while the handNotes element + gives specific details of each. The choice will depend on individual encoders' + priorities.

+ +

As shown above, the hand attribute is available on several elements to + indicate the hand in which the content of the element (usually a deletion or + addition) is carried out. The handShift element may also be used within the + body of a transcription to indicate where a change of hand is detected for whatever + reason. + + +

+

A handShift element can be used to + indicate a change of hand even within an element with a hand attribute. The text following the handShift + must be considered to be in the new hand. +

+

Both handShift and handNote are members of the att.handFeatures class, and thus share the following attributes: + + +

+ +

A single hand may employ different writing styles and inks within a document, or may + change character. For example, the writing style might shift from anglicana to + secretary, or the ink from blue to brown, or the character of the hand may + change. Simple changes of this kind may be indicated by assigning a new value to the + appropriate attribute within the handShift element. It is for the encoder to + decide whether a change in these properties of the writing style is so marked as to + require treatment as a distinct hand.

+

Where such a change is to be identified, the new attribute indicates the + hand applicable to the material following the handShift. The sequence of + such handShift elements will often, but not necessarily, correspond with the + order in which the material was originally written. Where this is not the case, the + facilities described in section may be found helpful.

+ +

As might be expected, a single hand may also vary renditions within the same writing + style, for example medieval scribes often indicate a structural division by + emboldening all the words within a line. Such changes should be indicated by use of + the rend attribute, in the same manner as underlining, emboldening, font + shifts, etc. are represented in transcription of a printed text, rather than by + introducing a new handShift element.

+ +

In the following example there is a change of ink within a single hand. This is + simply indicated by a new value for the medium attribute on the + handShift element: When wolde the cat dwelle in his ynne + + And if the cattes skynne be slyk and + gaye

+ +

In the following example, the encoder has identified two distinct hands within the + document and given them identifiers h1 and h2, by means of the + following declarations included in the document's TEI header: + + Carefully written + with regular descenders + Unschooled + scrawl + + +

+

Then the change of hand is indicated in the text: ... and that good Order Decency and regular worship may be once + more introduced and Established in this Parish according to the Rules and + Ceremonies of the Church of England and as under a good Consciencious and sober + Curate there would and ought to be and for that + purpose the parishioners pray

+ +

When a more precise or nuanced discussion of the writing in a manuscript is required, + the handNote and scriptNote elements discussed in should be used. Either element may serve as the target for a + handShift.

+ +
+ +
+ Hand, Responsibility, and Certainty Attributes + +

The hand and resp attributes have similar, but not identical, + meanings. Observe their distinctive uses in the following encoding of the William + James passage mentioned above in section . In this example, the + But inserted by James is tagged as an add, and the + consequent editorial correction of One to + one treated separately: But + Oneone must have lived ... + + editorial changes + Fredson Bowers + + + authorial changes + William James + + As in this example, hand should be reserved for indicating the + hand of any form of marking—here, addition but also deletion, correction, annotation, + underlining, etc.—within the primary text being transcribed. The scribal or authorial + responsibility for this marking may be inferred from the value of the hand + attribute. The value of the hand attribute should be a pointer to a hand + identifiers typically declared in the document header but potentially in another + document or repository (see section ).

+

The resp attribute, by contrast, indicates the person responsible for + deciding to mark up this part of the text with this particular element. In the case + of the add element, for example, the resp attribute will indicate + the responsibility for identifying that the addition is indeed an addition, and also + (if the hand attribute is supplied) to which hand it should be attributed. + In this case, Bowers is credited with identifying the hand as that of William James. + In the case of the corr element, the resp attribute indicates who + is responsible for supplying the intellectual content of the correction reported in + the transcription: here, Bowers' correction of One to one. In the case + of a deletion, the resp attribute will similarly indicate who bears + responsibility for identifying or categorizing the deletion itself, while other + attributes (hand most obviously) attribute responsibility for the deletion + itself. It should be noted that the source attribute may be used in a simiilar + fashion to indicate, for example, when an encoding decision is based on the work of a + previous editor or on an article. In that case, the source would point to + a bibl in the bibliography.

+

+ In cases where both the resp and cert attributes are defined + for a particular element, the two attributes refer to the same aspect of the markup. + The one indicates who is intellectually responsible for some item of information, the + other indicates the degree of confidence in the information. Thus, for a correction, + the resp attribute signifies the person responsible for supplying the + correction, while the cert attribute signifies the degree of editorial + confidence felt in that correction. For the expansion of an abbreviation, the + resp attribute signifies the person responsible for supplying the + expansion and the cert attribute signifies the degree of editorial + confidence felt in the expansion.

+

This close definition of the use of the resp and cert + attributes with each element is intended to provide for the most frequent + circumstances in which encoders might wish to make unambiguous statements regarding + the responsibility for and certainty of aspects of their encoding. The + resp and cert attributes, as so defined, give a convenient + mechanism for this. However, there will be cases where it is desirable to state + responsibility for and certainty concerning other aspects of the encoding. For + example, one may wish in the case of an apparent addition to state the responsibility + for the use of the add element, rather than the responsibility for + identifying the hand of the addition. It may also be that one editor may make an + electronic transcription of another editor's printed transcription of a manuscript + text—here, one will wish to assign layers of responsibility, so as to allow the + reader to determine exactly what in the final transcription was the responsibility of + each editor. In these complex cases of divided editorial responsibility for and + certainty concerning the content, attributes, and application of a particular + element, the more general mechanisms for representing certainty and responsibility + described in chapter should be used.

+ +

It should be noted that the certainty and responsibility mechanisms described in + chapter replicate all the functions of the resp and + cert attributes on particular elements. For example, the encoding of + Donaldson's conjectured emendation of wight to + wright in line 117 of Chaucer's Wife of Bath's + Prologue (see ) may be encoded as follows using the + resp and cert attributes on the corr element: + + wightwright Exactly the same information could be conveyed + using the certainty and responsibility mechanisms, as follows: + wrightwight + + The choice of which + mechanism to use is left to the encoder. In transcriptions where only such statements + of responsibility and certainty are made as can be accommodated within the + resp and cert attributes of particular elements, it will be + economical to use the resp and cert attributes of those + elements. Where many statements of responsibility and certainty are made which cannot + be so accommodated, it may be economical to use the respons and + certainty elements throughout.

+

The above discussion supposes that in each case an encoder is able to specify exactly + what it is that one wishes to state responsibility for and certainty about. + Situations may arise when an encoder wishes to make a statement concerning certainty + or responsibility but is unable or unwilling to specify so precisely the domain of + the certainty or responsibility. In these cases, the note element may be + used with the type attribute set to cert or resp and the + content of the note giving a prose description of the state of affairs.

+
+
+ +
+ Damage and Conjecture +

The carrier medium of a primary source may often sustain physical damage which makes + parts of it hard or impossible to read. In this section we discuss elements which may be + used to represent such situations and give recommendations about how these should be + used in conjunction with the other related elements introduced previously in this + chapter.

+ + +
+ Damage, Illegibility, and Supplied Text +

The gap and supplied elements described above (section ) should be used with appropriate attributes where the degree of + damage or illegibility in a text is such that nothing can be read and the text must + be either omitted or supplied conjecturally or from one or more other sources. In + many cases, however, despite damage or illegibility, the text may yet be read with + reasonable confidence. In these cases, the following elements should be used: + + + As members of the class att.damaged, these + elements bear the following attributes: + + The class att.damaged is a subclass of the + class att.dimensions, itself a subclass of the class + att.ranging. Consequently these elements also + therefore bear at least the following attributes: + + + From the att.spanning class, + damageSpan inherits the following additional attribute: + + +

+

The following examples all refer to the recto of folio 5 of the unique manuscript of + the Elder Edda. Here, the manuscript of Vóluspá has been damaged + through irregular rubbing so that letters in various places are obscured and in some + cases cannot be read at all.

+

In the first line of this leaf, the transcriber may believe that the last three + letters of daga can be read clearly despite the damage: um aldr + daga yndisniota +

+

If, as is often the case, the damage crosses structural divisions, so that the + damage element cannot be nested properly within the containing + div elements, the damageSpan element may be used, in the same + way as the delSpan and addSpan elements discussed in section .

+ + + +

+

[...]

+

[...] +

Note that in this example the spanTo element points to the + next pb element rather than to an inserted anchor element, since it + is the whole of the leaf (the text between the two pb elements) which has + sustained damage. For other techniques of handling non-nesting information, see + chapter .

+

If, as is also likely, the damage affects several disjoint parts of the text, each + such part must be marked with a separate damage or damageSpan + element. To indicate that each of these is to be regarded as forming part of the same + damaged area, the group attribute may be used as in the following example. + In this (imaginary) text of Fitzgerald's translation from Omar Khayam, water damage + has affected an area covering parts of several lines: The Moving Finger wries; and having writ, + Moves on: nor all your Piety nor + Wit + Shall lure it back to + cancel half a Line, + Nor all your Tears wash out a Word of it + +

+

A more general solution to this problem is provided by the join element + discussed in which may be used to link together arbitrary + elements of any kind in the transcription. Here, several phenomena of illegibility + and conjecture all result from a single cause: an area of damage to the text caused + by rubbing at various points. The damage is not continuous, and affects the text at + irregular points. In cases such as this, the join element may be used to indicate + which tagged features are part of the same physical phenomenon.

+ +

If the damage has been so severe as to render parts of the text only imperfectly + legible, the unclear element should be used to mark the fact. Returning to + the Eddic example above, an encoder less confident in the daga + reading might indicate this as follows: um aldr daga yndisniota

+

If it is desired to supply more information about the kind of damage, it is also + possible to nest an unclear element within the damage element: + um aldr daga yndisniota

+

Alternatively, the transcriber may not feel able to read the last three letters of + daga but may wish to supply them by conjecture. Note the + use of the resp attribute to assign the conjecture to Finnur Jónsson: + um aldr daga + yndisniota The supplied element may if desired be enclosed within + a damage element: um aldr daga + yndisniota The transcriber may also provide alternative conjectures by + enclosing multiple supplied elements within a choice element.

+

Contrast the use of gap in the next line, where the transcriber believes + that four letters cannot be read at all because of the damage: þar komr inn dimmi + dreki fliugandi naþr frann neþan As with supplied, this + gap might be enclosed by a damage element.

+

Where elements are nested in this way, information about agency, etc. is by default + inherited. In the following imaginary example, there is a smoke-damaged part within + which two stretches can be read with some difficulty, and a third stretch which + cannot be read at all: + and the proof of this is + + margin + + +

+

The above examples record imperfect legibility due to damage. When imperfect + legibility is due to some other reason (typically because the handwriting is + ill-formed), the unclear element should be used without any enclosing + damage element. In Robert Southey's autograph of The Life of + Cowper the final six letters of attention are + difficult to read because of the haste of the writing, though reasonably certain from + the context. and + from time to time invited in like manner his attention + The cert attribute on the unclear element may be used to indicate + the level of editorial confidence in the reading contained within it.

+
+
+ Use of the gap, del, damage, unclear, and + supplied Elements in Combination +

The gap, damage, unclear, supplied, and + del elements may be closely allied in their use. For example, an area of + damage in a primary source might be encoded with any one of the first four of these + elements, depending on how far the damage has affected the readability of the text. + Further, certain of the elements may nest within one another. The examples given in + the last sections illustrate something of how these elements are to be distinguished + in use. This may be formulated as follows: + where the text has been rendered completely illegible by deletion or damage + and no text is supplied by the editor in place of what is lost: place an empty + gap element at the point of deletion or damage. Note that the gap + could be wrapped in a del or damage element. Use the + reason attribute to state the cause (damage, deletion, etc.) of + the loss of text. + where the text has been rendered completely illegible by deletion or damage + and text is supplied by the editor in place of what is lost: surround the text + supplied at the point of deletion or damage with the supplied element. + Use the reason attribute to state the cause (damage, deletion, etc.) + of the loss of text leading to the need to supply the text. + where the text has been rendered partly illegible by deletion or damage so + that the text can be read but without perfect confidence: transcribe the text + and surround it with the unclear element. Use the reason + attribute to state the cause (damage, deletion, etc.) of the uncertainty in + transcription and the cert attribute to indicate the confidence in + the transcription. + where there is deletion or damage but at least some of the text can be read + with perfect confidence: transcribe the text and surround it with the + del element (for deletion) or the damage element (for + damage). Use appropriate attribute values to indicate the cause and type of + deletion or damage. Observe that the degree attribute on the + damage element permits the encoding to show that a letter, word, or + phrase is not perfectly preserved, though it may be read with + confidence. + where there is an area of deletion or damage and parts of the text within + that area can be read with perfect confidence, other parts with less + confidence, other parts not at all: in transcription, surround the whole area + with the del element (for deletion; or the delSpan element + where it crosses a structural boundary); or the damage element (for + damage). Text within the damaged area which can be read with perfect confidence + needs no further tagging. Text within the damaged area which cannot be read + with perfect confidence may be surrounded with the unclear element. + Places within the damaged area where the text has been rendered completely + illegible and no text is supplied by the editor may be marked with the + gap element. For each element, one may use appropriate attribute + values to indicate the cause and type of deletion or damage and the certainty + of the reading. +

+

The rules for combinations of the add and del elements, and for the + interpretation of such combinations, are similar:

+ + if one add element (with identifier ADD1) contains + another (with identifier ADD2), then the addition + ADD1 was first made to the text, and later a second addition + (ADD2) was made within that added text: This is the text with some added (interlinear!) material as + written. + if one del element contains another, and the seq attribute + does not indicate otherwise, it should be assumed that the inner deletion was made + before the enclosing one. In the following example, the word + redundant was deleted before a second deletion removed + the entire passage: This + sentence contains some redundant unnecessary + verbiage. + if a del element contains an add element, the normal + interpretation will be that an addition was made within a passage which was later + deleted in its entirety: This + sentence was deleted originally from the + text. + if an add element contains a del element, the normal + interpretation will be that a deletion was made from a passage which had earlier + been added: This sentence was + added eventually to the text. + When some text has been blackened out so thoroughly that can no longer be read, + the encoding should be: runs out the door in shirt + For consistency, one might prefer to encode the deletion as such, using del, + and containing a gap, as in the following example: + runs out the door in shirt + This is something that would be necessary if one wanted to encode a subst including an illegible deletion: + summons + If some parts of the deleted text are readable, and other parts unreadable, it should be encoded as in the following example: + Billy in The ng Silver Dollar.. + +
+
+ + +
+ Marking up the Writing Process +

Modifications of various kinds (correction, addition, deletion, etc.) are frequently + found within a single document, and may also be inferred when different documents are + compared, although it may be an open question as to whether inter-document discrepancies + should be regarded in the same way as intra-document + alterations. When two witnesses are collated, we may observe that a word present in one + is missing from the other: this does not necessarily imply that the word was added to + the first witness, nor that it was deleted from the other.

+ +

In this section we discuss a number of elements which may be useful when attempting to + record traces of the writing process within a document.

+ +
+ Generic Modification + + + +

Most, if not all, transcriptional elements imply a certain level of semantic + interpretation. For instance, using the add element to encode a word or + phrase that occupies interlinear space involves a decision that it has been + deliberately inserted as an addition rather than an alternative, and indeed a + judgment that it was written after, rather than before, the other lines. Where it is + felt desirable to keep the recording of what is on the page + entirely separate from what is the editor’s interpretation, the + generic mod element may be preferred. + + This element simply indicates any kind of modification that has been + identified in the document, without prejudice as to its function. Occurrences of the + mod element may be categorized by means of their type + attribute, and visual aspects of their appearance can be described by means of the + rend attribute, but they provide no further interpretation of the + function or intention of the passage so marked up. The spanTo attribute + may be used to indicate the end of a modified passage if this extends across the + boundaries of some other XML element, for example from the middle of one line tagged + as a line to the middle of another line some distance further on in + the document.

+ + words words words words with wavy + underline <!-- more lines here --> wavy underlining finishes + here more words + + + + +

The distinction between an example such as that above and the simple use of + hi to mark the visual salience of the underlining (apart from the use of + the spanTo attribute) is that hi does not imply that the visual + effect being recorded is understood to represent some kind of modification.

+
+ +
+ Metamarks + +

By metamark we mean marks such as numbers, arrows, crosses, or other + symbols introduced by the writer into a document expressly for the purpose of + indicating how the text is to be read. Such marks thus constitute a kind of markup of + the document, rather than forming part of the text. + + +

+ +

Unlike marginal notes or other additions to the text, metamarks are used by the + writer to indicate a deliberate alteration of the writing itself, such as move + this passage over there. An addition or annotation by contrast would typically + concern some property of the passage other than its intended location or status + within the text flow. A metamark may contain text, or some other graphic which the + encoder wishes to represent, or it may simply consist of arrows, dots, lines etc. + which the encoder simply describes.

+ + + +

The metamark element carries a function attribute which specifies + the function of the metamark, using values such as reorder, + flag, delete, insert or used. The + passage to which the metamark applies may be indicated in either of two ways: the + target attribute may be used to point to the element or elements + containing the passage concerned, or the spanTo element may be used to + point to a position in the document at which the passage concerned finishes. In the + latter case, the metamark itself must be supplied at the position in the + document where the passage concerned begins; in the former case it may be supplied at + any convenient point. Both attributes should not be supplied.

+ +

The following example is taken from an 15th century legal book from the city of + Göttingen, containing regulations of everyday life issued by the city council

+ + Kundige bok 2, fol 1v. +
+

+ + +

In the second paragraph, the word lege ("read") + was written in the left hand margin, next to the sentence beginning Ock en + schullen de bruwere.... It is thought to function as a metamark, indicating + that this sentence forms part of the regulations. A further sentence was then added, + while at some later stage the text and also the metamark were deleted. We might + encode this as follows as an embedded transcription (keeping in mind that the elements described here can also be used within text): + + lege + Ock en schullen de bruwere des hilgen dages + nicht over setten noch uppe den stillen fridach bruwen. + + Noch nymande over setten, se en sehin denne erst, dat uppe den bonen neyn + stro noch, huw noch flaß ligghe, by pine eyner halven roden, deme bruwere so + wol alse dem bruwheren to murende. + + +

+

The change attribute used here to indicate the sequencing of these various + interventions is discussed below, in section . The + elements addSpan and delSpan are discussed in section .

+ +

The metamark element may also be used to encode the symbols etc. often found + in marked-up proofs such as the following, taken from the Walt Whitman archive:

+ + From a corrected proof of Miracles (Walt Whitman + Archive) +

+ +

In this example, the whole of what was originally the 14th section of the poem has + been marked for deletion, both by horizontal and vertical lines, and by the proofreading mark + resembling the deleatur or dele deletion symbol to left and right of the section. The + deletion itself might be encoded by using the normal del or delSpan + element, and the metamarks by the metamark element. This is quite a + different case from that of the next example, in which the writer does not intend to + suppress the content, but only to mark that it has been copied to another manuscript + or reused.

+

+

+ + From "I am that halfgrown angry boy" (MS q 25), David M. Rubenstein Rare + Book & Manuscript Library, Duke University. +
+

+

This page contains internal deletions, additions, and retracings but these are + semantically quite different from the apparent deletion + signalled by the larger of the two single vertical lines, which shows that the + written material has been transferred or re-used, not deleted.

+ + + + + I am that halfgrown angry boy, fallen asleep + The tears of foolish passion yet undried + upon my cheeks. + + I pass through the travels and fortunes of + thirty + years and become old, + Each in its due order comes and goes, + And thus a message for me comes. + The + + Entered - Yes + + +

In this embedded transcription example, we class as metamarks both the long vertical line and the annotation + Entered - yes. + + Both metamarks are assumed to indicate that the whole of the written zone with + identifier X2 is marked as having been used. metamark can be similarly used within text to encode the same phenomenon as part of a transcription that privileges logical over physical and layout structures.

+ +
+ +
+ Fixation and Clarification + +

A writer may sometimes rewrite material a second time without significant change and + in the same place. We consider this a distinct activity from addition as usually + defined because no new textual material results; instead the status of existing + material is reaffirmed. We may distinguish two variants of this: + fixation where the first version was a tentative draft which is + subsequently reaffirmed, for example by inking it over; and + clarification, where the first version was badly written and has been + rewritten for clarity. The element retrace is provided for both cases; its + cause attribute may be used to distinguish these or other cases. + + +

+ +

In this simple example, taken from the papers of Henrik Ibsen, the writer wrote the + word skuldren hastily, and then returned to it to make the + letter l larger and clearer:

+ + From autograph ms of Peer Gynt, Collin 2869, 4°, + I.1.1, the Royal Library of Copenhagen +
We might transcribe this word as follows: + Skuldren + +

+ +

A single rewrite may not be sufficient, and it may be that the document becomes + almost unreadable as a result of repeated clarification. In the following example, we + can distinguish at least three attempts to write the letters + er in the word bægerklang:

+ + Detail from autograph ms Brand in The Royal + Library, Denmark (KBK Collin 262) + +
We might encode this by nesting the retrace element as follows: + + ved Bæg + er + ... + The change attribute used here is discussed further below ().

+ +

The retrace element is used only for cases where text has been written + multiple times. When metamarks and other markup-like strokes have been rewritten + multiple times, the redo element described in the next section should be + used in preference.

+
+ +
+ Confirmation, Cancellation, and Reinstatement of Modifications + +

+ A writer may indicate that an alteration is itself to be altered: for + example, a struck-through passage may be restored via a dotted underlining, or the + underlining of a passage may be deleted by a wavy line.

+ +

The following elements are provided to represent these situations: + + + +

+ + + + + +

The element restore () is provided for the + comparatively simple case where a simple deletion is marked as having been + subsequently cancelled. The undo element discussed here is more widely + applicable and may be used for any kind of cancellation. It points to the element or + elements which are being cancelled. These components need not be contiguous, provided + that the cancellation is clearly a single act; each distinct act of cancellation + requires a distinct undo element, however. Either of the attributes + target or spanTo may be used to indicate the passages + concerned.

+ +

Consider the following imaginary example:

+ + Imaginary example demonstrating restoring and undoing +
We hypothesize that the text has gone through three states or changes, as + follows: + This is just some sample text, we need a real example. + This is not a real example. + This is just some text, not a real example. + +

+ +

This sequence of events might be encoded as follows: + This is + just some sample text, we need + not a real example. + using two undo elements, each with a spanTo attribute, + to delimit the two parts of the deletion which were reverted at change s3. Note that + in this case, since target is not supplied, it is the effect of the parent + element (the del) which is assumed to be undone.

+ +

Alternatively, we might more economically use the generic seg element to delimit the two sequences whose deletion is being reverted, and + then use the target attribute on a single undo element: + This is + just some sample text, we + need + not a real example. + + + +

+
+ +
+ Transpositions + +

A transposition occurs when metamarks are found in a document indicating + that passages should be moved to a different position. Typically this may be done + using arrows, asterisks or numbers, or other means. By definition the result of a + transposition is not present in the document, and should not therefore be encoded, if + the intention is to represent the actual appearance of the document. Instead, the + following elements may be used to indicate the intended reordering: + + +

+

Consider for example, the following extract from an Ibsen manuscript

+ + Extract from autograph Digte (Poems) NBO Ms. 4º 1110a +
The underlined numbers 1 and 2 here indicate that, although the word + bör precedes the word hör in the + text, the order of the two words should be reversed. We may encode this as follows: + + bör2. og hör1. + + + + + + + + +

+ +

Note the use of the generic seg element to identify the sections of text + being transposed. The following example uses an embedded transcription approach, which typically identifies lines of writing with the line element. This makes it trivial to refer to the transposed line, but when encoding transposition within text the encoder will need to find a way to identify the line with another element, such as seg.

+ + Detail from autograph ms of Den episke Brand (KBK Collin + 2869) +
+ + 2.) thi da er du med Himmelen i Pagt; — + + 1.) da kan du + Folkets Jøkelhjerter tine; + + + + + + + + When transposition is made, the whole element indicated is understood to be + moved, not just its contents. In the above example, the metamarks are thus understood + to be moved along with the lines to which they apply.

+ + + +

One or more listTranspose elements may be + supplied either embedded within the text, in the + profileDesc of the header, or in a + standOff depending on local preference. Each + listTranspose can contain one or more + transpose elements, each of which defines a + single transposition.

+
+ +
+ Alternative Readings +

+ + Detail from autograph manuscript of the second version of Lalla + Rookh, Pierpont Morgan MA 310 +
In this example two alternative readings are provided, but no preference is + indicated. While the author apparently first composed the line Alone before his + native river -, at some later point, he entertained the possibility of using + the word beside instead of before. The + manuscript supplies no indication of which word Moore favours at this point, although + in fact, in the first printed edition of Lalla Rookh the word + beside was chosen.

+

The element alt provided by the linking module + gives a simple way of encoding the state of this manuscript, as follows: Alone before + beside his native river ­— + + +

+

The mode attribute here indicates that the two possible readings indicated + by the target attribute are mutually exclusive. The weights + attribute indicates the relative importance or preference to be attached to the two + readings on a scale running from zero (most improbable) to one (most probable). In + this case, we have a very strong preference for the second reading because this is + the one that appears in the published version of the poem. The alt element + is further discussed in section .

+
+ + + +
+ Instant Corrections +

The use of elements such as del and add necessarily implies that + the modifications they indicate were made at some time after the original writing. An + exception to this is where a false start or instant correction + has been identified: the author starts to write, and then immediately corrects what + has been written.

+

The instant attribute defined by this module may be used on any element + which is a member of the att.editLike class to modify + this default assumption. When the value of instant is set to + true, the addition or deletion is considered to belong to the same + change as its parent element, while false means some change later than + that of its parent.

+

An example of false start or instant correction can be seen in the following line: +

+ + Detail fron [I am a curse], one of the drafts for Whitman's + Song of Myself +
in which we can detect the following sequence of events: + The letter T is written and then immediately deleted + The word The is written, deleted, and replaced by the word + His + The added word His is then deleted + The initial letter i of the words iron + necklace is overwritten with a capital I + To indicate that the first of these acts must have taken place during the + main act of writing, before the other deletion and additions, we might encode this + revision campaign as follows: + T + + The + + His + + + + i + I + ron necklace + +

+
+
+
+ +
+ Aspects of Layout +

The following methods are available to capture general aspects of the layout of material on + a page where this is considered important. Within the sourceDoc element, as + already indicated, the element surface and surfaceGrp enable the encoder + to represent directly the structure of a codex as gatherings or quires, leaves, and + surfaces, as in the following example: + + + + + + + + + + + + + + + + + + + + +

+

In some cases, it may be preferable to define surfaces corresponding with each two + page opening, for example where it is clear that the writer regarded each such opening as a + single writing surface, with written zones or other features crossing the page divide. An + example is shown here:

+ + Opening from autograph ms of Proust's A la recherche du temps perdu + (f 42v-43r) +
+

+

The coloured lines added to this image indicate a number of zones of writing, colour coded + to indicate the order in which they were written (purple, then green, then red). For + example, the zone marked in red on the left contains a note referring to the purple zone on + the right.

+ +

This approach assumes that the transcription will primarily be organized in the same way as + the physical layout of the source, using embedded transcription elements. Alternatively, + where the a non-embedded transcription has been provided, using the text element, + it is still possible to record gathering breaks, page breaks, column breaks, line breaks + etc in the source, using the elements described in section . Detailed + metadata about the physical make-up of a source will usually be summarized by the + physDesc component of an msDesc element discussed in .

+ +
+ Space +

The author or scribe may have left space for a word, or for an initial capital, and for + some reason the word or capital was never supplied and the space left empty. The + presence of significant space in the text being transcribed may be indicated by the + space element. + + Note that this element should not be used to mark normal inter-word space or + the like.

+

In line 694 of Chaucer's Wife of Bath's Prologue in the Holkham + manuscript the scribe has left a space for a word where other manuscripts read + preestes: By + god if wommen had writen storyes As han within her + oratoryes The supplied element discussed in the previous section may + be used to supply the text presumed missing: By god if wommen had writen storyes As + preestes han within + her oratoryes Here, the fact of the space within the manuscript is indicated + by the value of the reason attribute. The source of the supplied text is + shown by the value of the source attribute as the Hengwrt manuscript; the + transcriber responsible for supplying the text is ES.

+
+
+ Lines +

One of the more common forms of modification encountered in written documents of any + kind is the presence of lines written under, beside, or through the text. Such lines may + be of various types: they may be solid, dashed or dotted, doubled or tripled, wavy or + straight, or a combination of these and other renderings. The line may be used for + emphasis, or to mark a foreign or technical term, or to signal a quotation or a title, + etc.: the elements emph, foreign, term, mentioned, + or title may be used for these. Where the line has a clear paratextual function + the metamark element may be considered more appropriate. Frequently, a scholar + may judge that a line is used to delete text: the del element is available to + indicate this. In all these cases, the rend attribute may be used to supply + further details concerning the style of the line. Thus, Lawrence's deletion by + strike-through of my in the autograph of Eloi, Eloi, lama + sabachthani may be encoded: For I hate this my body, which is so + dear to me

+

There will be instances, however, where a scholar wishes only to register the occurrence + of lines in the text, without making any judgement as to what the lines signify. In + these cases the hi element may be used, with the rend attribute to + mark the style of line. In the manuscript of a letter by Robert Browning to George + Moulton-Barrett the underlining of the phrase had obtained all the letters to + Mr Boyd may be marked-up as follows: I have once — by + declaring I would prosecute by law — hindered a man's proceedings who had obtained all the letters to Mr Boyd

+

The above examples presume the common case where a single word or phrase is marked by a + line, with no doubt as to where the marking begins or ends and with no overlapping of + the area of text with other marked areas of text. Where there is doubt, the + certainty element may be used to record the doubt. In the Browning example + cited above the underlining actually begins half-way under who, + and this uncertainty could be remarked as follows: I have once — by declaring I would prosecute + by law — hindered a man's proceedings who had + obtained all the letters to Mr Boyd + + + may begin with previous word +

+

Where the area of text marked overlaps other areas of text, for example crossing a + structural division, one of the spanning mechanisms mentioned above must be used; for + example where the line is thought to mark a deletion, the delSpan element may + be used. Where it is desired simply to record the marking of a span of text in + circumstances where it is not possible to surround the text with a hi element, + the span element may be used with the rend or type + attribute indicating the style of line-marking.

+

More work needs to be done on clarifying the treatment of other textual features marked + by lines which might so overlap or nest. For example, in many Middle English manuscripts + (e.g. the Jesus and Digby verse collections), marginal sidebars may indicate metrical + structure: couplets may be linked in pairs, with the pairs themselves linked into + stanzas. Or, marginal sidebars may indicate emphasis, or may point out a region of text + on which there is some annotation: in many manuscripts of Chaucer's Wife of + Bath's Prologue lines 655–8 are marked with nesting parentheses against which + the scribe has written nota.

+

Such features could be captured by use of the note element, containing a prose + description of the manuscript at this point, enhanced by a link to a visual + representation (or facsimile) of the feature in question. For example, in the Chaucer + example just cited, one may wish to record that the nota is + written in the Hengwrt manuscript in the right margin against a single large left + parenthesis bracketing the four lines, with two right parentheses in the right margin + bracketing two overlapping pairs of lines: the first and third, the second and fourth. + The note element allows us to record that the scribe wrote + nota, but is not well-adapted to show that the + nota points both at all four lines and at two pairs of lines + within the four lines. The metamark element discussed in section above provides better facilities for this kind of complex + annotation.

+
+
+ + +
+ Transcription and Ruby + +

These Guidelines also provide special elements to support the + encoding of ruby annotations, which are common in East Asian textual + traditions. These elements provide a method of capturing a specific + type of annotation, in addition to the generic methods like the + note or interp elements. Both the specific and + general methods should integrate well with the transcriptional + elements described above, allowing authorial and scribal features to + be captured in conjunction with ruby base text and annotations. See + for more information about these + elements.

+
+ +
+ Headers, Footers, and Similar Matter + +

Such information as page numbers, signatures, or catchwords may be recorded in a + specialized fw element provided for that purpose. Although the name derives from + the term forme work, used in description of early printed documents (the + forme being the block used to hold movable type), the fw element may be + used for such features of any document, written or printed. Note that the purpose of this + element is to record page numbers etc. actually present in the document being + encoded, not necessarily to provide a complete or accurate pagination of it.

+

Information about pagination etc. may also be provided using the n attribute of + the pb or gb elements, or by other appropriate milestone + elements, as further discussed in section : since this information is + usually provided by the encoder, it is not subject to the constraint that it should be + present only if textually present in the source being encoded. In text-critical situations + it may be useful to provide both a normalized version of the pagination and a + representation of the catch-word or numbering, especially when the latter presents a + variant reading, or is significant for compositor identification. + + The fw element may be used to encode any of the unchanging portions of + a page forme, such as: + running heads (whether repeated or changing on every page, or alternating + pages) + running footers + page numbers + catch-words + other material repeated from page to page, which falls outside the stream of the + text + It should not be used for marginal glosses, annotations, or textual variants, which + should be tagged using gloss, note, or the text-critical tags described + in chapter , respectively.

+

For example: Poëms. + 29 + E3 + TEMPLE + + +

+
+ + + +
+ Identifying Changes and Revisions +

A major purpose of genetic editing is the identification of revision + campaigns or, more generally, changes. An editor may wish to + regard a particular set of alterations (deletions, additions, substitutions, transpositions, etc.) or + any other act of writing as a single object for which we use the general term change, to indicate both that one or more of such + phenomena preceded or followed another and also to indicate that they are related in some + way, for example that one is a consequence of the other. They might also wish to group + together certain revisions, regardless of when they might have occurred, based on a variety + of other shared characteristics (e.g., corrections of factual errors or revisions that + incorporate suggestions made by a given reader). To document this we need: + a system to assign phenomena to a particular change as defined above + a way to characterize each such change, in itself and in relation to others. +

+ +

The element creation (within the TEI header profile description) contains all + information relating to the genesis or production of a text. It may contain a + listChange element which contains a number of change elements, one for + each set of alterations identified: + + + +

+ +

In the following example an editor has identified four distinct sets of alterations:

+ + + + + First stage, written in ink + Second stage, with revisions written in the author's hand + using pencil + Fixation of the pencilled revisions together with further + revisions in the author's hand using ink + Additions in a different hand, probably at a later + stage + + + + +

The listChange element carries an attribute ordered, which can take the + values true or false (the default). The attribute specifies + whether the order of child elements signifies a temporal order for the revision campaigns + which they document. In the example above, the editor has asserted that the four sets + distinguished are ordered chronologically according to the order of the change + elements. + + If necessary, listChange elements can be nested hierarchically. This may be + helpful in two cases. Firstly one can build up hypotheses about related revisions + step-by-step, starting with change elements of smaller coverage, whose members are certainly + related, and then in a subsequent pass grouping these in turn, thereby extending + their reach.

+ + + + + + An unrelated change note + + Alterations on one manuscript page, certainly + related + Alterations on another manuscript page, certainly + related + + Another unrelated change note + + + + +

A nested listChange element is also useful to indicate a partial + ordering of change elements.

+ + + The first stage + + + A revision of the first stage + Another revision of the first stage + + The last stage + + +

In addition to the possibility of being ordered by their sequence within + a listChange element, + change elements may carry a number of attributes from the att.datable class (period, when, notBefore, + notAfter, from, and to) which allow each element to be + dated as exactly or inexactly as necessary, in the same way as is currently possible for + the TEI date element.

+ + + + + + + The first draft of + Persuasion, completed by the date July 16 1816 + which is written after the word Finis at page + 30. + After the 16th of July + Austen starts revision of the two final chapters, by rewriting the end and + adding a new zone (pages 32-35) to be inserted at + page 19. This stage is documented by the + deletion of the date (July 16 1816) at page + 30, and the addition of more text and of a new date (July 18. + 1816) at page 31 + Before publication, after July 18th, + 1816 chapters 10-11 were broken into three chapters, 10, 11, 12, as + witnessed by the print. + + + + +

Each change element, apart from declaring a distinct moment or phase in the creation of the + document, may also contain references to other annotations contained within the + teiHeader or in the document (as shown in the previous example). Such + references, along with the textual content, are purely documentary. The association between a textual + component and a change element + is always made explicitly, either by using the target + attribute on the change element to point to one or more textual elements, or by pointing + from the element or elements concerned to the change element by means of their + change attribute. If a change element is associated with some + element, it is also associated with all of that element's children, unless otherwise + indicated, for example by a new value for the change attribute.

+

In the following simple example, the text at one stage read This is a mouse, and at + the next This is a house mouse: + This is a house + mouse. + +

+

In this example, however, the text originally read This is a house, and subsequently + This is a mouse: + This is a + house + mouse + . + Note that in this case both the deletion and the addition are associated with the + second change element. The word house, because its deletion forms part of + this second set of alterations, must have + been present originally, whereas the word mouse must have been added during + the second set of alterations.

+ +

Elements such as add and del and the like carry an implied semantics + concerning the order in which events in the writing of a document was carried out: + something which is deleted must have been written before it was deleted; something which is + added must have been added at a later stage of the writing. Even when a combination of such + elements is used, the chronology can usually be inferred (see further ). Explicit indication of the set of alterations to which some modification belongs is mostly useful + in situations where all the alterations identified in a document are to be grouped, for + example chronologically.

+ + +

The interpretation of change elements with respect to a particular text passage is based on a number + of implicit assumptions and constraints which have the effect of minimizing the amount of + tagging necessary. The system is also flexible enough to support an explicit distinction + between acts of writing and textual alterations, since either of these can be associated + with changes described in the encoding. The following example shows an encoding in which + the same passage is transcribed twice, once from a documentary perspective, and once from a + textual one: + + + + First stage, written in ink by a + scribe + Revised by Goethe using pencil + Fixation of the revised passages and further revisions by Goethe using + ink + + + + + + + + + Nun + + Ihr wanſtige Schuften mit den Feuerbacken + + + feiſt + + Ihr glüht ſo recht vom Höllen Schwefel ſatt. [...] + + + + + + + Ihr + Nun + wanſtige Schuften mit den Feuerbacken + Ihr glüht ſo recht vom Höllen Schwefel + ſatt + feiſt + . + + + +

+ +

The documentary transcription stresses the writing process, while the textual transcription + emphasizes textual alterations. In either case, the change of writing activity associated + with a particular feature in the transcript is explicitly indicated. From the documentary + perspective, by assigning particular modifications to a specific change element, we describe the + writing process, in that they specify which segment has been written when + . From the textual perspective, the markup concentrates simply on the + existence of textual alterations and makes no explicit claims about the order of writing. + +

+
+ + + +
+ Other Primary Source Features not Covered in these Guidelines +

We repeat the advice given at the beginning of this chapter, that these recommendations are + not intended to meet every transcriptional circumstance ever likely to be faced by any + scholar. They are intended rather as a base to enable encoding of the most common phenomena + found in the course of scholarly transcription of primary source materials. These + guidelines particularly do not address the encoding of physical description of textual + witnesses: the materials of the carrier, the medium of the inscribing implement, the + organisation of the carrier materials themselves (as quiring, collation, etc.), and authorial + instructions or scribal markup, except insofar as these are involved in the broader + question of manuscript description, as addressed by the msdescription module described in chapter .

+
+ +
+ Module for Transcription of Primary Sources +

The module described in this chapter makes available the following components: + + Transcription of Primary Sources + Transcription of primary sources + 原文轉錄 + Représentation de sources primaires + Trascrizione di fonti primarie + Transcrição de fontes primárias + 転記モジュール + + + The selection and combination of modules to form a TEI schema + is described in .

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+
diff --git a/P5/Source/Guidelines/fr/PrefatoryNote.xml b/P5/Source/Guidelines/fr/PrefatoryNote.xml deleted file mode 120000 index be1a998c63..0000000000 --- a/P5/Source/Guidelines/fr/PrefatoryNote.xml +++ /dev/null @@ -1 +0,0 @@ -../en/./PrefatoryNote.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/PrefatoryNote.xml b/P5/Source/Guidelines/fr/PrefatoryNote.xml new file mode 100644 index 0000000000..f4369cae25 --- /dev/null +++ b/P5/Source/Guidelines/fr/PrefatoryNote.xml @@ -0,0 +1,674 @@ + + + + + + + +
Prefatory Notes +

This Appendix contains (in reverse chronological +order) the Introductory Notes prefixed to each +revision of the TEI Guidelines since its first publication in 1994. +

+ +
Prefatory Note (March 2002) +

The primary goal of this revision has been to make available a new +and corrected version of the TEI Guidelines which: + +is expressed in XML and conforms to a TEI-conformant XML + DTD; +generates a set of DTD fragments that can be combined + together to form either SGML or XML document type + definitions; + corrects blatant errors, typographical mishaps, and other + egregious editorial oversights; +can be processed and maintained using readily available XML + tools instead of the special-purpose ad hoc software originally + used for TEI P3. + +

+

A second major design goal of this revision has been to ensure that the + DTD fragments generated would not break existing documents: in + other words, that any document conforming to the original TEI P3 + SGML DTD would also conform to the new XML version of + it. Although full backwards compatibility cannot be guaranteed, + we believe our implementation is consistent with that goal. +

+

In most respects, the TEI Guidelines have stood the test of time remarkably +well. The present edition makes no substantial attempt to rewrite those few parts +of them which have now been rendered obsolete by changes since their +first publication, though an indication is given in the text of where such rewriting is +now considered necessary. Neither does the present version attempt to +address any of the many possible new areas of digital activity in which +the TEI approach to standardization may have something to offer. Both +these tasks require the existence of an informed and active TEI +Council to direct and validate such extension and maintenance work, +in response to the changing needs and priorities of the TEI user community. +

+

Two exceptions to the above principles may be cited: firstly, the +chapter which originally provided a Gentle +Introduction to SGML has been completely rewritten to +provide a similarly gentle introduction to XML; secondly the chapter +on character sets has been completely revised in light of the +close connexion between Unicode and XML. The editors gratefully +acknowledge the assistance of the ad hoc workgroup chaired by Christian +Wittern, which undertook to provide expert advice and correction at +very short notice, in the latter task.

+

The preparation of this new version relied extensively on +preliminary work carried out by the former North American editor of +the TEI Guidelines, C.M. Sperberg-McQueen. In a TEI working paper +written in 1999TEI ED W69, available +from the TEI web site at . he sketched +out a precise blueprint for the conversion of the TEI from SGML to +XML, which we have implemented, with only slight modification.

+

The Editors would also like to express thanks to the +team of volunteers from the TEI community who helped us with the task +of proofreading the first draft during the summer of 2001; and to + Sebastian Rahtz of Oxford University Computing Services, without + whose skill and enthusiasm this new edition would not have been + possible. +

+

A substantial proportion of the work of preparing this new edition was +funded with the assistance of a grant from the US National +Endowment for the Humanities, whose continued support of the TEI has +also been crucial to the effort of setting up the TEI Consortium. +

+

Finally, we would like to thank all our colleagues on the interim +management board of the TEI Consortium, in particular its Chairman +John Unsworth, for their continued support of +the TEI's work, and their willingness to devote effort to the +difficult task of overseeing its transition to a new organizational +infrastructure.

+

Summary details of the changes made in the present and previous +editions are given in their Prefatory Notes, all of which are now +reproduced in an Appendix to the present edition: see . +

+Lou Burnard and Syd Bauman (TEI Editors) +Oxford and Providence, March 2002. +
+ + + +
Introductory Note (November 2001) +

To complete the work started in June of this year, the TEI Editors +asked for volunteers from the TEI community to proofread the preliminary XML +version. 24 volunteers responded to this call during August, and gave invaluable help both by identifying +a number of previously un-noticed errors, and by suggesting areas in +which more substantial revision should be undertaken in the +future. The Editors gratefully acknowledge the assistance of the following +individuals during this exercise: +

+

+Jimmy Adair, +Syd Bauman, +Michael Beddow, +Steven Bird, +Lisa Charlong, +Matthew Driscoll, +Patrick Durusau, +Tomaz Erjavec, +Nick Finke, +Tim Finney, +Julia Flanders, +Mike Fraser, +Pankaj Kamthan, +François Lachance, +Terry Langendoen, +Anne Mahoney, +Gregory Murphy, +Daniel Pitti, +Rafal Prinke, +Laurent Romary, +Stewart Russell, +Gary Simons, +Elisabeth Solopova, +Christian Wittern, +Martin Wynne. +

+

In addition to error correction, and clear delineation of those sections in +which substantial revision is yet to be undertaken for TEI P5, the +present draft differs from earlier ones in the following respects: + +Formal Public Identifiers have been introduced as a means of +constructing TEI DTDs and an SGML Open Catalog is now included with the +standard release; +Some systematic errors and omissions in the reference section +have been removed; the format of this section has been substantially changed, we +hope for the better; +The chapters on obtaining the TEI DTDs and WSDs have been +brought up to date; the chapter on modification has been expanded to +include a discussion of the TEI Lite customization; +All examples and cited markup has been checked for XML validity +against the published DTDs, and corrected where faulty; examples have +been formatted in a (more or less) consistent style. + +

+Lou Burnard and Syd Bauman (Editors) +Oxford and Providence, November 2001. +
+
Introductory Note (June 2001) +

This is a preliminary version of a revised and fully XML-compliant +edition of the TEI Guidelines. Although work on revising and +correcting the text of the document is incomplete, by making +available this preliminary version we hope to facilitate testing of +the XML document type declarations which it describes by as wide a +range of TEI users as possible.

+

The primary goal of this revision is to make available the +corrected (May 1999) edition of the Guidelines in a new version which: + +is expressed in XML and itself conforms to a TEI-conformant XML + DTD; +generates a set of XML DTD fragments that can be combined + together in the same way as the existing TEI (P3) SGML DTD + fragments to form true TEI XML DTD fragments without loss of functionality; +can be processed and maintained using readily available XML + tools instead of the special-purpose ad hoc software originally + used for TEI P3. + +As noted elsewhere, a number of errors were corrected in +the May 1999 edition. A (much) smaller number of errors have also been +corrected in this edition, but no new material has been added. We +expect the expansion and modification of the Guidelines to become +a real possibility in the context of the newly formed TEI Consortium, +which has funded the preparation of this present edition.

+

A major design goal of both this and the previous revision has been + to ensure that the DTD fragments generated would not break + existing documents: in other words, that any document conforming + to the original TEI P3 SGML DTD would also conform to the new + XML version of it. Although full backwards compatibility cannot + be guaranteed, we believe our implementation is consistent with + that goal.

+

In making this new version, we relied extensively on preliminary + work carried out by the outgoing North American editor of the + TEI Guidelines, Michael Sperberg-McQueen. In a TEI working paper + written in 1999, TEI ED + W69, Michael sketched out a precise blueprint for the + conversion of the TEI from SGML to XML, which we have + implemented, with only slight modification. The current TEI + editors wish to express here our admiration for the detailed + care put into that paper, without which our task would have been + forbiddingly difficult, if not impossible. We would also like to + express our thanks to Sebastian Rahtz of Oxford University + Computing Services, for his invaluable assistance in preparing + this new edition.

+

We list here in summary form all the changes made in the present +edition. Full technical details are provided in documents TEI EDW69 +and TEI EDW70, available from the TEI web site. + +A new keyword TEI.XML has been added. By setting +its value to INCLUDE, rather than the default IGNORE, +the user can request generation of an XML rather than an SGML DTD; +The content models of all elements have been checked, and, where +necessary, changed so that they are equally valid as SGML or as +XML; +The declared value for all attributes has been changed to a form +which is equally valid as SGML or as XML; +All the examples have been checked for conformance and converted to +use XML syntax, where possible. (This process is currently incomplete.) +Some errors and duplications in the class +membership of elements from the names and dates tagsets have been corrected.

+

To implement the first of these, we have parameterized the +tag omissibility indicators - o and - - +used within element declarations in the DTD. When XML is to be +generated, the parameter entities concerned are redeclared with the null +string as their value.

+

The second change was achieved by removing SGML-specific features +(ampersand connectors, inclusion and exclusion exceptions, various +types of attribute content) from the DTD and revising the syntax of +the DTD to conform to XML requirements (specifically in the +representation of mixed-content models, and by removing redundant +parentheses). In making these changes, we took care to ensure that the +resulting content model would continue to accept existing valid +documents, though in the nature of things it could not be guaranteed +to reject the same set of documents. As further discussed in EDW69 and +EDW70, some constraints (exclusion exceptions, for example) which +could be carried out by a generic SGML parser using TEI P3 will have +to be implemented by a special purpose TEI validator using TEI +P4.

+

Much work remains to be done, firstly in testing the new DTD +fragments against as wide a range of TEI materials as possible, +secondly in revising the discussion of markup theory and practice +within the text to reflect current thinking. A few sections of the +current text (the Gentle Introduction to SGML and the discussion of +Extended Pointer syntax are two examples) will need substantial +rewriting. For the most part, however, we think the Guidelines have +stood the test of time well and can be recommended to a new generation of +text encoders scarcely born at the time they were first formulated. +

+

Lou Burnard and Steve De Rose (Editors)

+

Oxford and Providence, May 2001.

+
+
+Introductory Note (May 1999) +

No work of the size and complexity of the TEI +Guidelines could reasonably be expected to be error-free on +publication, nor to remain long uncorrected. It has however taken rather longer +than might have been anticipated to complete production of the present +corrected reprint of the first edition, for which we present our apologies, +both to the many individuals and institutions whose enthusiastic adoption and +promotion of the TEI encoding scheme have ensured its continued survival in the +rapidly changing world of digital scholarship, and also to the many helpfully +critical users whose assiduous uncovering and reporting of our errors have made +possible the present revision.

+

At its first meeting in Bergen, in June 1996, the TEI Technical Review +Committee (TRC) approved the setting up of a small working committee to oversee the +production of a revised edition of the TEI +Guidelines, to include corrections of as many as possible of the +`corrigible errors' notified to the editors since publication +of the first edition in May 1994, the bulk of which are summarized in a TEI +working paper (TEI EDW67, available from the TEI web site).

+

During the spring of 1997, this TRC Core Subcommittee reviewed nearly 200 +comments and proposals which the editors had collected from public debate and +discussion over the preceding two years, and provided invaluable technical +guidance in disposition of them. We are glad to take this opportunity of +expressing our thanks to this subcommittee, whose members were Elli Mylonas, +Dominic Dunlop, and David T. Barnard.

+

The work of making the corrections and regenerating the text proceeded + rather fitfully during 1998 and 1999, largely because of increasing demands on + the editors' time from their other responsibilities. With the + establishment of the new TEI Consortium, it is be hoped that maintenance of the + Guidelines will be placed on a more secure footing. Some specific areas in which we + anticipate future revisions being carried out are listed below.

+
+Typographic Corrections Made + + examples of TEI markup throughout the text were all checked against the + relevant DTD fragment and an embarassingly large number of tagging errors + corrected; + various minor typographic and spelling errors were corrected; + the corrigible errors listed in working paper TEI EDW67 were all + corrected: some of these required specific changes to the DTD which are listed + in the next section. + +
+
+Specific Changes in the DTD +

A major goal of this revision was to avoid changes which might invalidate + existing data, even where existing constructs seemed erroneous in retrospect. + To that end, wherever changes have been made in content models for existing + elements, they have as far as possible been made so that the DTD will now + accept a superset of what was previously legal. Only one new element + (ab) has been added.

+

Where possible, a few content models have been changed in such a way as to + facilitate conversion to XML, but XML compatibility is + not a goal + of this revision.

+

Brief details of all changes made in the DTD follow: + + Several changes were made in class membership, in order to correct + unreachability problems. Specifically: + + elements geogName, persName, + placeName were added to the m.data class; + geogName and placeName were removed from the + m.placepart class; + the elements addSpan, delSpan, gap, were + added to the m.Edit class; + a new class m.editIncl was defined, with members + addSpan, delSpan, and gap; this class was then added + to the global inclusion class +m.globIncl along with + anchor (erroneously a member of the +m.Seg class, from + which it is now removed), m.metadata and m.refsys; + + + added name element to m.addrPart class; + added dateline to m.divtop and + m.divbot classes; + added epilogue and castList to + m.dramafront class; + added divGen to m.front class; + added dateline to m.divtop and + m.divtop classes; + added u element to a.declaring class; + defined new class m.fmchunk (front matter chunk), + comprising argument, byline, docAuthor, + docDate, docEdition, docImprint, docTitle, + epigraph, head, and titlePart for use in + simplification of the content model for front element; + defined new element ab (anonymous block), and added it to the + m.chunk class; + corrected an error whereby global attributes were not properly defined + for elements specifying a non-default value for any of the + a.global attributes: elements affected include: foreign, + hi, del, pb, lb, cb, + language, anchor, and when; + changed content models to permit empty list and empty + availability elements; + changed content model for series element to permit #PCDATA; + + changed content model for setting element to permit + date element as a direct child; + added a key attribute to the distance element, + for consistency with other elements in its class; + changed content model for orgName element to make it more + consistent with e.g. persName; + changed content model for opener element to include + argument, byline, and epigraph; + changed content models for app, rdgGrp, and + wit elements; + revised attributes on hand element.

+

A number of content models were changed with a view to +easing the creation of an XML compatible version of the +Guidelines. Specifically: + removed ampersand connectors from cit, +respStmt, publicationStmt, and graph; +changed the mixed content models for sense, re, persName, +placeName, geogName, dateStruct, timeStruct, and dateline +to make them XML-conformant. +

+
+
+Outstanding Errors +

A small number of other known problems remain uncorrected in this version + and are briefly listed below. Please watch the TEI mailing list for + announcements of their correction.

+ +elements of class model.inter don't always behave + as they should (e.g. one cannot insert a table before + anything else in a div); + + some mixed-content problems consequent on the definition of + macro.specialPara need to be addressed systematically; + in particular, the treatment of list items or notes which contain + several paragraphs continues to surprise many users: no + whitespace is allowed between the paragraphs; + the resp attributes on editorial elements are not + consistently defined; + the discussions of DTD invocation, and the DTD itself, all use + system identifiers instead of formal public identifiers. + +

Our next priority however will be the production of a fully XML-compliant version + of the TEI DTD, work on which is already well advanced.

+C.M. Sperberg-McQueen and Lou Burnard, May 1999 +
+
+
Preface (April 1994) +

These Guidelines are the result of over five years' effort by +members of the research and academic community within the +framework of an international cooperative project called the Text +Encoding Initiative (TEI), established in 1987 under the joint +sponsorship of the Association for Computers and the Humanities, +the Association for Computational Linguistics, and the Association +for Literary and Linguistic Computing. +

+

The impetus for the project came from the humanities computing +community, which sought a common encoding scheme for complex textual +structures in order to reduce the diversity of existing encoding +practices, simplify processing by machine, and encourage the sharing of +electronic texts. It soon became apparent that a sufficiently flexible +scheme could provide solutions for text encoding problems generally. The +scope of the TEI was therefore broadened to meet the varied encoding +requirements of any discipline or application. Thus, the TEI became the +only systematized attempt to develop a fully general text encoding model +and set of encoding conventions based upon it, suitable for processing +and analysis of any type of text, in any language, and intended to serve +the increasing range of existing (and potential) applications and use. +

+

What is published here is a major milestone in this effort. It +provides a single, coherent framework for all kinds of text encoding +which is hardware-, software- and application-independent. Within this +framework, it specifies encoding conventions for a number of key text +types and features. The ongoing work of the TEI is to extend the +scheme presented here to cover additional text types and features, as +well as to continue to refine its encoding recommendations on the +basis of extensive experience with their actual application and use. +

+

We therefore offer these Guidelines to the user community for use in +the same spirit of active collaboration and cooperation with which +they have so far been developed. The TEI is committed to actively +supporting the wide-spread and large-scale use of the Guidelines +which, with the publication of this volume, is now for the first time +possible. In addition, we anticipate that users of the TEI Guidelines +will in some instances adapt and extend them as necessary to suit +particular needs; we invite such users to engage in the further +development of these Guidelines by working with us as they do so. +

+

Like any standard which is actually used, these Guidelines do not +represent a static finished work, but rather one which will evolve +over time with the active involvement of its community of users. We +invite and encourage the participation of the user community in +this process, in order to ensure that the TEI Guidelines become and +remain useful in all sorts of work with machine-readable texts. +

+

This document was made possible in part by financial support from +the U.S. National Endowment for the Humanities, an independent federal +agency; Directorate General XIII of the Commission of the European +Communities; the Andrew W. Mellon Foundation; and the Social Science +and Humanities Research Council of Canada. Direct and indirect +support has also been received from the University of Illinois at +Chicago, the Oxford University Computing Services, the University of +Arizona, the University of Oslo and Queen's University (Kingston, +Ont.), Bellcore (Bell Communications Research), the Istituto di +Linguistica Computazionale (C.N.R.) Pisa, the British Academy, and +Ohio State University, as well as the employers and host institutions +of the members of the TEI working committees and work groups listed in +the acknowledgments. +

+

The production of this document has been greatly facilitated by the +willingness of many software vendors to provide us with evaluation +versions of their products. Most parts of this text have been processed +at some time by almost every currently available SGML-aware software +system. In particular, we gratefully acknowledge the +assistance of the following vendors: + +Berger-Levrault AIS s.a. (for Balise); +E2S n.v. (for E2S Advanced SGML Editor); +Electronic Book Technology (for DynaText); +SEMA Group and Yard Software (for Mark-It and Write-It); +Software Exoterica (for CheckMark and Xtran); +SoftQuad, Inc., (for Author/Editor and RulesBuilder); +Xerox Corporation (for Ventura Publisher). +

+

Details of the software actually used to produce the current document +are given in the colophon at the end of the work.

+
+
Acknowledgments +

Many people have given of their time, energy, expertise, and support +in the creation of this document; it is unfortunately not possible to +thank them all adequately. Below are listed those who have served as +formal members of the TEI's Work Groups and Working Committees during +its six-year history; others not so officially enfranchised also +contributed much to the quality of the result.

+

The editors take this opportunity to acknowledge our debt to those +who have patiently endured and corrected our misunderstandings of their +work; we hope that they will feel the wait has not been in vain. For +any errors and inconsistencies remaining, we must accept responsibility; +any virtue in what is here presented, we gladly ascribe to the energies +of the keen intellects listed below.

+

C. M. Sperberg-McQueen and Lou Burnard

+
TEI Working Committees (1990-1993)Not all members listed were able to serve throughout the development +of the Guidelines. + + +

Chair: Dominik Wujastyk (Wellcome Institute for the History of +Medicine)

+

Members 1990–1992: J. D. Byrum (Library of Congress); +Marianne Gaunt (Rutgers University); +Richard Giordano (Manchester University); +Barbara Ann Kipfer (Independent Consultant); +Hans Jørgen Marker (Danish Data Archive, Odense); +Marcia Taylor (University of Essex);

 + +

Chair: Stig Johansson (University of Oslo)

+

Members 1990–1992: Roberto Cencioni (Commission of the European +Communities); +David R. Chesnutt (University of South Carolina); +Robin C. Cover (Dallas Theological Seminary); +Steven J. DeRose (Electronic Book Technology Inc); +David G. Durand (Boston University); +Susan M. Hockey (Oxford University Computing Service); +Claus Huitfeldt (University of Bergen); +Francisco Marcos-Marin (University Madrid); +Elli Mylonas (Harvard University); +Wilhelm Ott (University of Tübingen); +Allen H. Renear (Brown University); +Manfred Thaller (Max-Planck-Institut für Geschichte, +Göttingen)

 + +

Chair: D. Terence Langendoen (University of Arizona)

+

Members 1990–1992: +Robert Amsler (Bell Communications Research); +Stephen Anderson (Johns Hopkins University); +Branimir Boguraev (IBM T. J. Watson Research Center); +Nicoletta Calzolari (University of Pisa); +Robert Ingria (Bolt Beranek Newman Inc); +Winfried Lenders (University of Bonn); +Mitch Marcus (University of Pennsylvania); +Nelleke Oostdijk (University of Nijmegen); +William Poser (Stanford University); +Beatrice Santorini (University of Pennsylvania); +Gary Simons (Summer Institute of Linguistics); +Antonio Zampolli, University of Pisa.

 + +

Chair: David T. Barnard (Queen's University)

+

Members 1990–1994: David G. Durand (Boston University); +Jean-Pierre Gaspart (Associated Consultants and +Software Engineers sa/nv); +Nancy M. Ide (Vassar College); +Lynne A. Price (Software Exoterica / Xerox PARC); +Frank Tompa (University of Waterloo); +Giovanni Battista Varile (Commission of the European Communities).

 +

In addition, the two TEI editors served ex officio on each +committee.

+

Following publication of the first draft of the TEI Guidelines (P1) +in November 1990, a number of specialist work groups were charged with +responsibility for drafting revisions and extensions, which, together +with material already presented in P1, constitute the basis of the +present work.

+

In addition, many members of the work groups listed below met on +three occasions to review the emerging proposals in detail at +technical review meetings convened by the TEI Steering Committee. +These meetings, held in Myrdal, Norway (November 1991), Chicago (May +1992) and Oxford (May 1993), were largely responsible for the +technical content and organization of the present work. Attendants at +these meetings are starred in the list below. + +Chair: Harry Gaylord* (University of Groningen); +Syun Tutiya* (Chiba University). +Chair: Peter Robinson* (Oxford University); +David Chesnutt* (University of South Carolina); +Robin Cover* (Dallas Theological Seminary); +Robert Kraft (University of Pennsylvania); +Peter Shillingsburg (Mississippi State University). +Chair: Steven J. DeRose* (Electronic Book Technologies Inc); +David Durand (Boston University); +Edward A. Fox (Virginia State University); Eve Wilson (University of +Kent). +Chair: Paul Ellison* (University of Exeter); +Anders Berglund (Independent Consultant); Dale Waldt (Thompson +Professional Publishing). +Chair: Douglas Biber* (University of Northern Arizona); +Jeremy Clear (Birmingham University); +Gunnel Engwall (University of Stockholm). +Chair: Claus Huitfeldt* (University of Bergen); +Dino Buzzetti (University of Bologna); +Jacqueline Hamesse (University of Louvain); +Mary Keeler (Georgetown University); +Christian Kloesel (Indiana University); +Allen Renear* (Brown University); +Donald Spaeth (Glasgow University). +Chair: David Robey* (University of Manchester); +Elaine Brennan* (Brown University); +David Chisholm (University of Arizona); +Willard McCarty (University of Toronto). +Chair: Elli Mylonas* (Harvard University); +John Lavagnino* (Brandeis University); +Rosanne Potter (University of Iowa). +Chair Thomas N. Corns* (University of Wales); +Christian Delcourt (University of Liège). + +Chair: D. Terence Langendoen* (University of Arizona); +Stephen R. Anderson (Johns Hopkins University); +Nicoletta Calzolari (University of Pisa); +Geoffrey Sampson* (University of Sussex); +Gary Simons* (Summer Institute of Linguistics). +Chair: Stig Johansson* (University of Oslo); +Jane Edwards (University of California at Berkeley); +Andrew Rosta (University College London). +Chair: Paul Fortier* (University of Manitoba); +Christian Delcourt (University of Liège;); +Ian Lancashire (University of Toronto); +Rosanne Potter (University of Iowa); +David Robey* (University of Manchester). + +Chair: Daniel Greenstein* (University of Glasgow); +Peter Denley (Queen Mary Westfield College, London); +Ingo Kropac (University of Graz); +Hans Jørgen Marker (Danish Data Archive, Odense); +Jan Oldervoll (University of Tromsø); +Kevin Schurer (University of Cambridge); +Donald Spaeth (Glasgow University); +Manfred Thaller (Max-Planck-Institut für Geschichte, +Göttingen).This Workgroup was jointly +sponsored by the Association for History and Computing. + +Chairs: Robert Amsler* (Bell Communications Research) and +Nicoletta Calzolari (University of Pisa); +Susan Armstrong-Warwick (University of Geneva); +John Fought (University of Pennsylvania); +Louise Guthrie (University of New Mexico); +Nancy M. Ide* (Vassar College); +Frank Tompa (University of Waterloo); +Carol Van Ess-Dykema (US Department of Defense); +Jean Veronis (University of Aix-en-Provence). +Chair: Robert Ingria* (Bolt Beranek Newman Inc); +Susan Armstrong-Warwick (University of Geneva); +Nicoletta Calzolari (University of Pisa). +Chair: Alan Melby* (Brigham Young University) +Gerhard Budin (University of Vienna); +Gregory Shreve (Kent State University); +Richard Strehlow (Oak Ridge National Laboratory); +Sue Ellen Wright (Kent State University).

+
Advisory Board +

Members of the TEI Advisory Board during the lifetime of the +project are listed below, grouped under the name of the organization +represented. + +Chad McDaniel (University of Maryland). +Elizabeth A. R. Brown (Brooklyn College, CUNY). +Jocelyn Penny Small (Rutgers University). +Allen Renear (Brown University). +Clifford A. Lynch (University of California). +1989–93: Scott Deerwester (University of Chicago); 1993- : +Martha Evens (Illinois Institute of Technology). +David Chesnutt (University of South Carolina). +1989–91: Manfred Thaller, Max-Planck-Institut für +Geschichte, Göttingen; 1991- : Daniel Greenstein (Glasgow +University). +1989–93: Wilhelm Ott (University of Tübingen); 1993- : +Winfried Bader (University of Tübingen). +Anne-Maria di Sciullo (Université du Québec +à Montréal) +Barbara Ann Kipfer (Independent Consultant). +1989–92: Betsy Kiser (OCLC); 1992- : +Deborah Bendig and Andrea Keyhani (OCLC). +J. D. Byrum Jr. (The Library of Congress). +Stephen Anderson (The Johns Hopkins University) +Randall Jones (Brigham Young University) and +Ian Lancashire (University of Toronto).

+
Steering Committee Membership +

Members of the Steering Committee of the TEI during the preparation +of this work were: + + + +1987–1993: Robert A. Amsler (Bell Communications Research); +1987–1993: Donald E. Walker (Bell Communications Research); +1993–1994: Susan Armstrong-Warwick (University of Geneva); +1994–1999: Judith Klavans (Columbia University). + + +1987–1999: Nancy M. Ide (Vassar College); +1987–1994: C. M. Sperberg-McQueen (University of Illinois at +Chicago); +1994–1999: David Barnard (Queen's University). + + +1987–1999: Susan M. Hockey (Center for Electronic Texts in the +Humanities); +1987–1999: Antonio Zampolli (University of Pisa).

+
diff --git a/P5/Source/Guidelines/fr/REF-ATTRIBUTES.xml b/P5/Source/Guidelines/fr/REF-ATTRIBUTES.xml deleted file mode 120000 index d3fc379a64..0000000000 --- a/P5/Source/Guidelines/fr/REF-ATTRIBUTES.xml +++ /dev/null @@ -1 +0,0 @@ -../en/REF-ATTRIBUTES.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/REF-ATTRIBUTES.xml b/P5/Source/Guidelines/fr/REF-ATTRIBUTES.xml new file mode 100644 index 0000000000..fdb0773d90 --- /dev/null +++ b/P5/Source/Guidelines/fr/REF-ATTRIBUTES.xml @@ -0,0 +1,15 @@ + + + + + + + +
+ Attributes +
+ About the Attributes Appendix +

This appendix gives you a list of attributes and links to the reference pages for the elements on which they appear. There are distinctly-named attributes in revision of TEI P5 of the TEI Guidelines.

+ + +
diff --git a/P5/Source/Guidelines/fr/REF-CLASSES-ATTS.xml b/P5/Source/Guidelines/fr/REF-CLASSES-ATTS.xml deleted file mode 120000 index 8762489a7f..0000000000 --- a/P5/Source/Guidelines/fr/REF-CLASSES-ATTS.xml +++ /dev/null @@ -1 +0,0 @@ -../en/REF-CLASSES-ATTS.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/REF-CLASSES-ATTS.xml b/P5/Source/Guidelines/fr/REF-CLASSES-ATTS.xml new file mode 100644 index 0000000000..0f003ed34c --- /dev/null +++ b/P5/Source/Guidelines/fr/REF-CLASSES-ATTS.xml @@ -0,0 +1,16 @@ + + + + + + + +
+ Attribute Classes +
+ About the Attribute Classes Appendix +

This appendix gives you a list of attribute classes and links to the reference pages for them. There are distinctly-named attribute classes in revision of TEI P5 of the TEI Guidelines.

+ + + +
diff --git a/P5/Source/Guidelines/fr/REF-CLASSES-MODEL.xml b/P5/Source/Guidelines/fr/REF-CLASSES-MODEL.xml deleted file mode 120000 index bfc16102dc..0000000000 --- a/P5/Source/Guidelines/fr/REF-CLASSES-MODEL.xml +++ /dev/null @@ -1 +0,0 @@ -../en/REF-CLASSES-MODEL.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/REF-CLASSES-MODEL.xml b/P5/Source/Guidelines/fr/REF-CLASSES-MODEL.xml new file mode 100644 index 0000000000..4a8511a445 --- /dev/null +++ b/P5/Source/Guidelines/fr/REF-CLASSES-MODEL.xml @@ -0,0 +1,15 @@ + + + + + + + +
+ Model Classes +
+ About the Model Classes Appendix +

This appendix gives you a list of model classes and links to the reference pages for them. There are distinctly-named model classes in revision of TEI P5 of the TEI Guidelines.

+ + +
diff --git a/P5/Source/Guidelines/fr/REF-ELEMENTS.xml b/P5/Source/Guidelines/fr/REF-ELEMENTS.xml deleted file mode 120000 index 187574ad0a..0000000000 --- a/P5/Source/Guidelines/fr/REF-ELEMENTS.xml +++ /dev/null @@ -1 +0,0 @@ -../en/REF-ELEMENTS.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/REF-ELEMENTS.xml b/P5/Source/Guidelines/fr/REF-ELEMENTS.xml new file mode 100644 index 0000000000..8db9fdcad3 --- /dev/null +++ b/P5/Source/Guidelines/fr/REF-ELEMENTS.xml @@ -0,0 +1,22 @@ + + + + + + + +
+ Elements +
+ About the Elements Appendix +

This appendix gives you links to reference pages for all elements in the TEI Guidelines. + There are TEI elements in revision of + TEI P5 of the TEI Guidelines.

+

The elements listed here are in the TEI Namespace: + http://www.tei-c.org/ns/1.0 + unless otherwise noted on that element's reference page. +

+ +
+ +
diff --git a/P5/Source/Guidelines/fr/REF-MACROS.xml b/P5/Source/Guidelines/fr/REF-MACROS.xml deleted file mode 120000 index 05ba029c5b..0000000000 --- a/P5/Source/Guidelines/fr/REF-MACROS.xml +++ /dev/null @@ -1 +0,0 @@ -../en/REF-MACROS.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/REF-MACROS.xml b/P5/Source/Guidelines/fr/REF-MACROS.xml new file mode 100644 index 0000000000..27437ab765 --- /dev/null +++ b/P5/Source/Guidelines/fr/REF-MACROS.xml @@ -0,0 +1,15 @@ + + + + + + + +
+ Datatypes and Other Macros +
+ About the Datatypes and Macros Appendix +

This appendix gives you a list of datypes and links to the reference pages for them. There are distinctly-named data specifications in revision of TEI P5 of the TEI Guidelines.

+ + +
diff --git a/P5/Source/Guidelines/fr/SA-LinkingSegmentationAlignment.xml b/P5/Source/Guidelines/fr/SA-LinkingSegmentationAlignment.xml deleted file mode 120000 index d863f9f68b..0000000000 --- a/P5/Source/Guidelines/fr/SA-LinkingSegmentationAlignment.xml +++ /dev/null @@ -1 +0,0 @@ -../en/./SA-LinkingSegmentationAlignment.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/SA-LinkingSegmentationAlignment.xml b/P5/Source/Guidelines/fr/SA-LinkingSegmentationAlignment.xml new file mode 100644 index 0000000000..48d6e5827d --- /dev/null +++ b/P5/Source/Guidelines/fr/SA-LinkingSegmentationAlignment.xml @@ -0,0 +1,3505 @@ + + + + +
+ Linking, Segmentation, and Alignment + +

This chapter discusses a number of ways in which encoders may +represent analyses of the structure of a text which are not +necessarily linear or hierarchic. The module defined by this chapter +provides for the following common requirements: + + to link disparate elements + using the xml:id attribute (section ); + to link disparate elements without using the + xml:id attribute (sections and ); + to segment text into elements convenient for + the encoder and to mark arbitrary points within documents (section + ); + to represent correspondence or + alignment among groups of text elements, both those + with content and those which are empty (section );We use the term alignment as a + special case for the more general notion of correspondence. Using A + as a short form for an element with its attribute xml:id + set to the value A, and suppose elements A1, A2, + and A3 occur in that order and form one group, while elements B1, + B2, and B3 occur in that order and form another group. Then a + relation in which A1 corresponds to B1, A2 corresponds to B2, and + A3 corresponds to B3 is an alignment. On the other hand, a + relation in which A1 corresponds to B2, B1 to C2, and C1 to A2 is + not an alignment. + to synchronize elements of a + text, that is to represent temporal correspondences and alignments + among text elements (section ) and also to + align them with specific points in time (section ); + to specify that one text element is identical + to or a copy of another (section ); + to aggregate possibly noncontiguous elements + (section ); + to specify that different elements are + alternatives to one another and to express + preferences among the alternatives (section ); + to store markup separately from the data it describes + or is related to (section ); + to associate segments of a text + with interpretations or analyses of their significance (section + ); + to group together elements used to provide stand-off + annotation, including contextual information (section ). +

+

These facilities all use the same set of techniques based on the +W3C XPointer framework () This provides a +variety of schemes; the most convenient of +which, and that recommended by these Guidelines, makes use of the +global xml:id attribute, as defined in section , and introduced in the section of +titled . When the linking module is included in a schema, the +attribute class att.global is extended to +include eight additional attributes to support the various kinds of +linking listed above. Each of these attributes is introduced in the +appropriate section below. In addition, for many of the topics +discussed, a choice of methods of encoding is offered, ranging from +simple but less general ones, which use attribute values only, to more +elaborate and more general ones, which use specialized elements.

+
+ Links +

We say that one element points to + others if the first has an attribute whose value is a reference to + the others: such an element is called a pointer + element, or simply a pointer. Among the + pointers that have been introduced up to this point in these + Guidelines are note, ref, and ptr. + These elements all indicate an association between one place in + the document (the location of the pointer itself) and one or more + others (the elements whose identifiers are specified by the + pointer's target attribute). The module described in + this chapter introduces a + variation on this basic kind of pointer, known as a + link, which specifies both ends + of an association. In addition, we define a syntax for + representing locations in a document by a variety of means not + dependent on the use of xml:id attributes.

+
+Pointers and Links +

In section we introduced the simplest +pointer elements, ptr and ref. Here we +introduce additionally the link element, which +represents an association between two (or more) locations by +specifying each location explicitly. Its own location is +irrelevant to the intended linkage. All three elements use the +attribute target, provided by the att.pointing class as a means of indicating the +location or locations referenced or pointed to. + + + + +The ptr element may be called a pure +pointer, because its primary function is simply to point. A +pointer sets up a connection between an +element (which, in the case of a pure pointer, is +simply a location in a document), and one or more others, known +collectively as its target. The ptr and +ref elements point, conceptually, at a single target, even +if that target may be discontinuous in the document. The link +element specifies at least two targets and represents an association +between them, independent of its own location.

+

These three elements also share a common set of attributes, derived +from the att.pointing and att.typed classes: + + + +

+

Double connection among elements could also be expressed by a +combination of pointer elements, for example, two ptr +elements, or one ptr element and one note +element. All that is required is that the value of the +target (or other pointing) attribute of the one be +the value of the xml:id attribute of the other. What +the link element accomplishes is the handling of double +connection by means of a single element. Thus, in the following +encoding: + +sa-p1 points to sa-p2, and sa-p2 +points to sa-p1. This is logically +equivalent to the more compact encoding: +

+

As noted elsewhere, the target attribute may take as value one or +more URI reference. In the simplest case, each such reference will +indicate an element in the current document (or in some other +document), for example by supplying the value used for its global +xml:id attribute. It may however carry as value any form of +URI, such as a URL pointing to some other document or location on the +Internet. Pointing or linking to external documents and pointing and +linking where identifiers are not available is described below in +section .

+
+
+Using Pointers and Links +

As an example of the use of mechanisms which establish +connections among elements, consider the practice (common in +18th century English verse and elsewhere) of providing footnotes +citing parallel passages from classical authors.

+The +figure shows the original page of Pope's Dunciad +which is discussed in the text.
Such +footnotes can of course simply be encoded using the +note element (see section ) without +a target attribute, placed adjacent to the passage to +which the note refers:The type +attribute on the note is used to classify the notes using the +typology established in the Advertisement to the work: The +Imitations of the Ancients are +added, to gratify those who either never read, or may have +forgotten them; together with some of the Parodies, and +Allusions to the most excellent of the Moderns. In the +source text, the text of the poem shares the page with two sets +of notes, one headed Remarks and the other +Imitations. +(Diff'rent our parties, but with equal grace +The Goddess smiles on Whig and Tory race, + + Virg. Æn. 10. + +Tros Rutulusve fuat; nullo discrimine habebo. +—— Rex Jupiter omnibus idem. + + 'Tis the same rope at sev'ral ends they twist, +To Dulness, Ridpath is as dear as Mist) +

+

This use of the note element can be called +implicit pointing (or implicit +linking). It relies on the juxtaposition of the note to +the text being commented on for the connection to be understood. +If it is felt that the mere juxtaposition of the note to the +text does not make it sufficiently clear exactly what text +segment is being commented on (for example, is it the +immediately preceding line, or the immediately preceding two +lines, or what?), or if it is decided to place the note at some +distance from the text, then the pointing or the linking must be +made explicit. We now consider various methods for doing +that.

+

Firstly, a ptr element might be placed at an +appropriate point within the text to link it with the +annotation: +(Diff'rent our parties, but with equal grace +The Goddess smiles on Whig and Tory race, + +'Tis the same rope at sev'ral ends they twist, +To Dulness, Ridpath is as dear as Mist) + + Virg. Æn. 10. + +Tros Rutulusve fuat; nullo discrimine habebo. +—— Rex Jupiter omnibus idem. + + + +The note element has been given an arbitrary identifier +(note3.284) to enable it to be specified +as the target of the pointer element. Because there is nothing +in the text to signal the existence of the annotation, the +rend attribute has been given the value unmarked.

+

Secondly, the target attribute of the +note element can be used to point at its associated +text, provided that an xml:id attribute has been +supplied for the associated text: +(Diff'rent our parties, but with equal grace +The Goddess smiles on Whig and Tory race, +'Tis the same rope at sev'ral ends they twist, +To Dulness, Ridpath is as dear as Mist) + + +Given this encoding of the text itself, we can now link the various +notes to it. In this case, the note +itself contains a pointer to the place in the text which it is +annotating; this could be encoded using a ref +element, which bears a target attribute of its own +and contains a (slightly misquoted) extract from the text marked +as a quote element: + + Verse 283–84. + + ——. With equal grace + Our Goddess smiles on Whig and Tory race. + + + Virg. Æn. 10. + +Tros Rutulusve fuat; nullo discrimine habebo. +—— Rex Jupiter omnibus idem. + + +

+

Combining these two approaches gives us the following +associations: + + a pointer within one line indicates the note + the note indicates the line + a pointer within the note indicates the line + +Note that we do not have any way of pointing from the line itself to +the note: the association is implied by containment of the pointer. We +do not as yet have a true double link between text and note. To +achieve that we will need to supply identifiers for the annotations as +well as for the verse lines, and use a link element to +associate the two. Note that the ptr element and the +target attribute on the note may now be dispensed +with: + + + Verse 283–84. + + ——. With equal grace + Our Goddess smiles on Whig and Tory race. + + Virg. Æn. 10. + +Tros Rutulusve fuat; nullo discrimine habebo. +—— Rex Jupiter omnibus idem. + + + +

+

The target attribute of the link element +here bears the identifier of the note followed by that of the +verse line. We could also allocate an +identifier to the reference within the note and encode the +association between it and the verse line in the same way: + + Verse 283–84. + + ——. With equal grace + Our Goddess smiles on Whig and Tory race. + + + + + + +Indeed, the two links could be combined into one, as +follows: +

+
+
+Groups of Links +

Clearly, there are many reasons for which an encoder might +wish to represent a link or association between different +elements. For some of them, specific elements are provided in +these Guidelines; some of these are discussed elsewhere in the +present chapter. The link element is a general purpose +element which may be used for any kind of association. The +element linkGrp may be used to group links of a +particular type together in a single part of the document; such +a collection may be used to represent what is sometimes referred +to in the literature of Hypertext as a web, a term +introduced by the Brown University FRESS project in 1969, and not to +be confused with the World Wide Web. + +As a member of the class att.pointing.group, this element shares the +following attributes with other members of that class: + +It is also a member of the att.pointing +and att.typed classes, and therefore also carries the attributes specified in +section above, in particular the +type attribute.

+

The linkGrp element provides a convenient way of +establishing a default for the type attribute on a +group of links of the same type: by default, the type +attribute on a link element has the same value as that +given for type on the enclosing linkGrp.

+

Typical software might hide a web entirely from the user, but +use it as a source of information about links, which are +displayed independently at their referenced locations. +Alternatively, software might provide a direct view of the link +collection, along with added functions for manipulating the +collection, as by filtering, sorting, and so on. +To continue our previous example, this text contains many other +notes of a kind similar to the one shown above. Here are a few +more of the lines to which annotations have to be attached, +followed by the annotations themselves: +A place there is, betwixt earth, air and seas +Where from Ambrosia, Jove retires for ease. + +Sign'd with that Ichor which from Gods distills. + + + Ovid Met. 12. + +Orbe locus media est, inter terrasq; fretumq; +Cœlestesq; plagas — + + + + Alludes to Homer, Iliad 5 ... + +To avoid having +to repeat the specification of type as imitation on each note, +we may specify it once for all on a linkGrp element +containing all links of this type. + + + + + +

+

Additional information for applications that use +linkGrp elements can be provided by means of special +attributes. First, the domains attribute can be used +to identify the text elements within which the individual +targets of the links are to be found. Suppose that the text +under discussion is organized into a body element, +containing the text of the poem, and a back element +containing the notes. Then the domains attribute can +have as its value the identifiers of the body and the +back, to enable an application to verify that the link +targets are in fact contained by appropriate elements, or to +limit its search space: + + + + + + + + + +

+

Note that there must be a single parent element for each +domain; if some notes are contained by a +section with identifier dunnotes, and +others by a section with identifier dunimits, +an intermediate pointer must be +provided (as described in section ) within +the linkGrp and its identifier used instead.

+

Next, the targFunc attribute can be used to +provide further information about the role or function of the +various targets specified for each link in the group. The value +of the targFunc attribute is a list of names +(formally, name tokens), one for each of the targets in the +link; these names can be chosen freely by the encoder, but their +significance should be documented in the encoding description in +the header.Since no special element is +provided for this purpose in the present version of these +Guidelines, the information should be supplied as a series of +paragraphs at the end of the encodingDesc element +described in section . In the current +example, we might think of the note as containing the source of the imitation and the verse line +as containing the goal of the +imitation. Accordingly, we can specify the linkGrp in +the preceding example thus: + + + + + + +

+ + + + +
+
+Intermediate Pointers +

In the preceding examples, we have shown various ways of +linking an annotation and a single verse line. However, the +example cited in fact requires us to encode an association +between the note and a pair of verse lines (lines +284 and 285); we call these two lines a span.

+

There are a number of possible ways of correcting this error: one +could use the target attribute to indicate one end of the +span and the special purpose targetEnd attribute on the +note element to point to the other. Another possibility might +be to create an element which represents the whole span itself and +assign that an xml:id attribute, which can then be linked +to the note and ref elements. This could be done +using for example the lg element defined in section or the virtual join +element discussed in section .

+

A third possibility would be to use an +intermediate pointer as follows: + + +When the target attribute of a ptr or +ref element specifies more than one element, the +indicated elements are intended to be combined or aggregated in +some way to produce the object of the pointer. (Such aggregation +is however the task of a processing application, and cannot be +defined simply by the markup). The xml:id attribute +of the ptr then provides an identifier which can be linked to the +note and ref elements: + +

+

The all value of evaluate is used on the +link element to specify that any pointer encountered as +a target of that element is itself evaluated. If +evaluate had the value none, the link target would be the pointer +itself, rather than the objects it points to.

+

Where a linkGrp element is used to group a +collection of link elements, any intermediate pointer +elements used by those link elements should be included +within the linkGrp.

+
+
+
+ Pointing Mechanisms +

This section introduces more formally the pointing mechanisms + available in the TEI. In addition to those + discussed so far, the TEI provides methods of pointing: + +into documents other than the current document; +to a particular element in a document other than the +current document using its xml:id; +to a particular element whether in the current document or +not, using its position in the XML element tree; +at arbitrary content in any XML document using TEI-defined +XPointer schemes. + +

+

All TEI attributes used to point at something else are declared as +having the datatype teidata.pointer, which +is defined as a URI referenceThe URI (Universal +Resource Indicator) is defined in RFC 3986; the +cases so far discussed are all simple examples of a URI +reference. Another familiar example is the mechanism used in XHTML to +create represent hypertext links by means of the XHTML href attribute. A URI reference can reference the +whole of an +XML resource such as a document or an XML element, or a +sub-portion of such a resource, identified by means of an appropriate fragment +identifier. Technically speaking, the fragment +identifier is that portion of a URI reference following the +first unescaped # character; in practice, it provides a means +of accessing some part of the resource described by the URI which is +less than the whole.

+

The first three of the following subsections provide only a + brief overview and some examples of the W3C mechanisms + recommended. More detailed information on the use of these + mechanisms is readily available elsewhere.

+
+Pointing Elsewhere +

Like the ubiquitous if misnamed XHTML pointing attribute href, the TEI pointing attributes can point to a +document that is not the current document (the one that contains the +pointing element) whether it is in the same local filesystem as the +current document, or on a different system entirely. In either case, +the pointing can be accomplished absolutely (using the entire address +of the target document) or relatively (using an address relative to +the current base URI in force). The current base +URI is defined according to Marsh +and Tobin 2009. If there is none, the base URI is that of the current +document. In common practice the current base URI in force is likely +to be the value of the xml:base attribute of the closest +ancestor that has one. However this may not be the case, since +xml:base attributes are accumulated through the hierarchy +by concatenation of path segments, beginning at the top of the +hierarchy and proceeding down to the context node.

+

The following example demonstrates an absolute URI reference +that points to a remote document: +The current base URI in force is as defined in the + W3C XML + Base recommendation.

+

This example points explicitly to a location on the Web, +accessible via HTTP. Suppose however that we wish +to access a document stored locally in a file. Again we will +supply an absolute URI reference, but this time using a +different protocol: +This Debian package is distributed under the terms + of the GNU General Public License.

+

In the following example, we use a relative URI reference +to point to a local document: +

+ + The figure shows the page from the Orbis + pictus of Comenius which is discussed in the text. +
+ +Since no xml:base is specified here, the location of the resource + Images/compic.png is determined relative to the +resource indicated by the current base URI, which is the current +document. +

+ + +

In the following example, however, we first change the current base +URI by setting a new value for xml:base. The resource +required is then identified by means of a relative URI: + +

+ On Ancient Persian Manners +

In the very first story of The Gulistan of + Sa'di, + Sa'di relates moral advice worthy of Miss Minners ...

+ +

+

As noted above, the current base URI is found on the nearest +ancestor. It is technically possible to use xml:base as a means to shorten URIs, but +this usage is not recommended. Abbreviated pointers provide a more +flexible and consistent method for creating shorthand links. +

+ + +
+
+Pointing Locally +

A shorthand pointer, in which the URI consists only of +# followed by the value of an xml:id acts as a +pointer to the element in the current document with that xml:id, +as in the following example.

+
+ Limitations on exclusive rights: Fair use +

Notwithstanding the provisions of + section 106, the fair use of a + copyrighted work, including such use by reproduction in copies + or phonorecords or by any other means specified by that section, + for purposes such as criticism, comment, news reporting, + teaching (including multiple copies for classroom use), + scholarship, or research, is not an infringement of copyright. + In determining whether the use made of a work in any particular + case is a fair use the factors to be considered shall + include —  + + the purpose and character of the use, including + whether such use is of a commercial nature or is for nonprofit + educational purposes; + the nature of the copyrighted work; + the amount and substantiality of the portion + used in relation to the copyrighted work as a whole; + and + the effect of the use upon the potential market + for or value of the copyrighted work. + + The fact that a work is unpublished shall not itself bar a + finding of fair use if such finding is made upon consideration + of all the above factors.

+
+This method of pointing, by referring to the xml:id of the +target element as a bare name only (e.g., #sect106) is +the simplest and often the best approach where it can be applied, i.e. where +both the source element and target element are in the same XML +document, and where the target element carries an identifier. It +is the method used extensively in previous sections of this +chapter and elsewhere in these Guidelines.

+
+ +
+ Using Abbreviated Pointers + +

Even in the case of relative links on the local file system, ref or target attributes may become quite lengthy and make XML code difficult to read. To deal with this problem, the TEI provides a useful method of using abbreviated pointers and documenting a way to dereference them automatically.

+ +

Imagine a project which has a large collection of XML documents organized like this:

+ + + anthology + + poetry + + poem.xml + + + prose + + novel.xml + + + + + references + + people + + personography.xml + + + + + + + +

If you want to link a name in the novel.xml file to a person in the personography.xml file, the link will look like this: + + + Fred + + + If there are many names to tag in a single paragraph, the XML encoding will be congested, and such lengthy links are prone to typographical error. In addition, if the project organization is changed, every relative link will have to be found and altered.

+ +

One way to deal with this is to use what is often referred to as a "magic token". You could make such links using the key attribute: + + Fred + + + and document the meaning of the key using (for instance) a taxonomy element in the TEI header, as described in . However, such a link cannot be mechanically processed by an external system that does not know how to interpret it; a human will have to read the header explanation and write code explicitly to reconstruct the intended link.

+ +

A more robust alternative is to use a private URI scheme. This is a method of constructing a simple, key-like token which functions as a teidata.pointer, and can therefore be used as the value of any attribute which has that datatype, such as ref and target. Such a scheme consists of a prefix with a colon, and then a value. You might, for example, use the prefix psn (for "person"), and structure your name tags like this: + + + Fred + + + How is this different from a magic token? Essentially, it isn't, except that TEI provides a structured method of dereferencing it (turning it into a computable path, such as ../../references/people/personography.xml#fred) by means of a declaration inside encodingDesc in the TEI header, using the elements and attributes for prefix declaration: + + + + + + + +

+ + +

This is how you might document a private URI scheme using the psn: prefix: + + + + +

+ In the context of this project, private URIs with the prefix + "psn" point to person elements in the project's + personography.xml file. +

+ + + + + This specifies that where a teidata.pointer value is constructed with a psn: prefix, a regular-expression replace operation can be performed on it to construct the full or relative URI to the target document or fragment. listPrefixDef is a child of encodingDesc, and it contains any number of prefixDef elements. Each prefixDef element provides a method of dereferencing or expanding an abbreviated pointer, based on a regular expression. The ident attribute specifies the prefix to which the expansion applies (without the colon). The matchPattern attribute contains a regular expression which is matched against the component of the pointer following the first colon, and the replacementPattern provides the string which will be used as a replacement. In this example, using psn:fred, the value fred would be matched by the matchPattern, and also captured (through the parentheses in the regular expression); it would then be replaced by the value ../../references/people/personography.xml#fred (with the the $1 in the replacementPattern being replaced by the captured value). The p element inside the prefixDef can be used to provide a human-readable explanation of the usage of this prefix.

+ +

Through this mechanism, any processor which encounters a teidata.pointer with a protocol unknown to it can check the listPrefixDef in the header to see if there is an available expansion for it, and if there is, it can automatically provide the expansion and generate a full or relative URI.

+ +

For any given prefix, it may be useful to supply more than one expansion. For instance, in addition to pointing at the person element in the personography file, it might also be useful to point to an external source which is available on the network, representing the same information in a different way. So there might be a second prefixDef like this: + + + +

+ Private URIs with the prefix "psn" can be converted to point + to a fragment on the Personography page of the project Website. +

+ + + + Any number of prefixDef elements may be provided for the same prefix. A processor may decide to process one or all of them; if it processes only one, it should choose the first one with the correct ident value, so the primary or most important prefixDef for any given prefix should appear first in its parent listPrefixDef.

+ +

When creating private URI schemes, it is recommended that you avoid using any existing registered prefix. A list of registered prefixes is maintained by IANA at .

+ +

Note that this mechanism can also be used to dereference other abbreviated pointing systems which are based on prefixes, such as Tag URIs.

+ +

The matchPattern and replacementPattern attributes are also used in dereferencing canonical reference patterns, and further examples of the use of regular expressions are shown in .

+ +
+ +
+TEI XPointer Schemes + +

The pointing schemes described in this chapter are part of a number of +such schemes envisaged by the W3C, which together constitute a +framework for addressing data within XML documents, known as the +XPointer Framework (Grosso et al +2003). This framework permits the definition of many other named +addressing methods, each of which is known as an XPointer +Scheme. The W3C has predefined a set of such schemes, and +maintains a register for their expansion.

+ +

One important scheme, also defined by the W3C, and recommended +by these Guidelines is the xpath() pointer +scheme, which allows for any part of an XML structure to be selected +using the syntax defined by the XPath specification. This is further +discussed below, . These Guidelines also define +six other pointer schemes, which provide access to parts of an XML +document such as points within data content or stretches of data +content. These additional TEI pointer schemes are defined in sections + to below.

+ +
Introduction to TEI Pointers + +

Before discussing the TEI pointer schemes, we introduce slightly +more formally the terminology used to define them. So far, we have +discussed only ways of pointing at components of the XML information +set node such as elements and attributes. However, there is often a +need in text analysis to address additional types of location such as +the point locations between +nodes, and sequences that +may arbitrarily cross the boundaries of nodes in a document. The +content of an XML document is organized sequentially as well as +hierarchically, and it makes sense to consider ranges of characters +within a document independently of the nodes to which they belong. +From the perspective of most of the pointer schemes discussed below, +a TEI document is a tree structure superimposed upon a character stream. +Nodes are entities available only in the tree, while points are available +only in the stream. For this reason, the schemes below that rely upon +character positions (string-index(), +string-range(), and match()) cannot take nodes +into account. Conversely, XPath (disregarding functions that return atomic values) is a method for locating nodes in the +tree and treats those nodes as indivisible units, meaning it is unable to address parts of nodes +in their document context.

+ +

The TEI pointer scheme thus distinguishes the following +kinds of object: + + + +A node is an instance of one of the node kinds defined in +the XQuery and XPath Data Model 3.1. It represents +a single item in the XML information set for a document. For pointing +purposes, the only nodes that are of interest are Text Nodes, +Element Nodes, and Attribute Nodes. + +A Sequence follows the definition in the XPath 3.1 Data +Model, with one alteration. A Sequence is an ordered collection +of zero or more items, where an item is either a node or a partial +text node. + + +A Text Stream is the concatenation of the text nodes in a document +and behaves as though all tags had been removed. A text stream begins +at a reference node and encompasses all of the text inside that node (if any) +and all the text following it in document order. In XPath terms, this would +encompass all of the text nodes beginning at a particular node, and following +it on the following axis. + + +A Point represents a dimensionless point between nodes or characters in +a document. Every point is adjacent to either characters or elements, and +never to another point. Points can only be referenced in relation to an +element or text node in the document (i.e. something addressable by either +an XPath or a fragment identifier). Points occur either immediately before +or after an element, or at a numbered position inside a text stream. +Position zero in the stream would be immediately before the first character. +Note that points within attribute values cannot mark the beginning or end of +a range extending beyond the attribute value, because points indicate a +position within a document. Since attribute nodes are by definition un-ordered, +they cannot be said to have a fixed position. + + +

+ +

The TEI recommends the following seven pointer schemes: + + +Addresses a node or node sequence using the XPath syntax. () + +addresses the point before (left) or after (right) a node or node +sequence ( and ) + +addresses a point inside a text node ( + +addresses the range between two points () + +addresses a range of a specified length starting from a +specified point () + +addresses a range which matches a specified string within a node +() + +

+

The xpath() scheme refers to the +existing XPath specification which is adopted with one modification: +the default namespace for any XPath used as a parameter to this +scheme is assumed to be the TEI namespace http://www.tei-c.org/ns/1.0. +

+

The other six schemes overlap in functionality with a W3C draft +specification known as the XPointer +scheme draft, but are individually much simpler. At the time of +this writing, there is no current or scheduled activity at the W3C +towards revising this draft or issuing it as a recommendation.

+ +

A note on namespaces: The W3C defines an +xmlns() scheme (see +XPointer xmlns() Scheme) +which when prepended to a resolvable pointer allows for the definition of +namespace prefixes to be used in XPaths in subsequent pointers. TEI Pointer +schemes assume that un-prefixed element names in TEI Pointer XPaths are in the +TEI namespace, http://www.tei-c.org/ns/1.0. The use of +xmlns() is thus optional, +provided no new prefixes need to be defined. If the schemes described here +are used to address non-TEI elements, then any new prefixes to be used in +pointer XPaths may be defined using the xmlns() +scheme.

+
+ +
+xpath() +

Sequence xpath(XPATH)

+

The xpath() scheme locates zero or more nodes within an XML + Information Set. The single argument XPATH is an XPath selection pattern, as + defined in XSLT + 3.0, that returns a node or sequence of nodes. XPaths returning atomic values + (e.g. substring()) are illegal in the xpath() + scheme because they represent extracted values rather than locations in the source + document. Because the schemes below involve starting at a node and navigating from there, + and because attribute nodes have no intrinsic order, XPath expressions that address + attribute nodes should be avoided in schemes other than xpath().

+

The example below, and all subsequent examples in this section refer +to the following TEI fragment: + + +

+si non habuiabui quidquam vaco +sib + cohorte mi rescribas +semper in mentementem + habeabe supra res +scriptas +auge et opto ut bene valeas
+ +

+

A TEI Pointer that referenced the reg element in the +choice in line 1 of the example might look like: +#xpath(//lb[@n='1']/following-sibling::choice[1]/reg). + Note that XPath values must be assumed to start from the document root. They cannot be relative + to the element bearing the attribute that uses the pointer because TEI Pointers are URIs. Care + should be taken to ensure that XPaths used in TEI Pointers match only a single node, unless + multiple matches are desired. The examples that follow are relatively simple because the + document they refer to is short and does not contain many elements.

+

When an XPath is interpreted by a TEI processor, the +information set of the referenced document is interpreted +without any additional information supplied by any schema +processing that may or may not be present. In particular this +means that no whitespace normalization is applied to a +document before the XPath is interpreted. +

+

This pointer scheme allows easy, direct use of the most +widely-implemented XML query method. It is probably the most +robust pointing mechanism for the common situation of +selecting an XML element or its contents where an +xml:id is not present. The ability to use element +names and attribute names and +values makes xpath() pointers more +robust than the other mechanisms discussed in this section +even if the designated document changes. For durability in the +presence of editing, use of xml:id is always +recommended when possible.

+
+ +
+left() +

Point left( IDREF | XPATH )

+

The left() scheme locates the +point immediately preceding the node addressed by its argument, +which is either an XPATH as defined above or an +IDREF, the value of an xml:id +occurring in the document addressed by the base URI in effect +for the pointer.

+

Example: the pointer #left(//supplied[1]) +indicates the point between the first lb and the first +supplied in the example above.

+

Example: #left(//gap[1]) indicates the point immediately before +the first gap element in line two and the string si.

+

Example: #left(line1) indicates the point immediately before +the lb n="1" element.

+ +
+right() +

Point right( IDREF | XPATH )

+

The right() scheme locates the +point immediately following the node addressed by its argument.

+

Example: the pointer #right(//lb[@n='3']) +indicates the point between the third lb and the +s]]> element +in the example.

+
+ +
+string-index() +

Point string-index( IDREF | XPATH, OFFSET )

+

The string-index() scheme locates a + point based on character positions in a text stream relative + to the node identified by the IDREF or XPATH parameter. The OFFSET +parameter is a positive, negative, or zero integer which determines +the position of the point. An offset of 0 represents the +position immediately before the first character in either the first +text node descendant of the node addressed in the first parameter or the +first following text node, if the addressed element contains +no text node descendants.

+

Example: #string-index(//lb[@n='2'],1) indicates the point +between the s and the i in the word si in line 2.

+

Note: The OFFSET parameter (and similarly the +LENGTH parameter found below in the string-range() +scheme) are measured in characters. What is considered a single character will +depend on the Normalization Form in use (see +UNICODE NORMALIZATION +FORMS). A letter followed by a combining diacritic counts as two +characters, but the same diacritic precombined with a letter would count +as a single character. Compare, for example, é (U+0060 +followed by U+0301) and é (>U+00E9). These are +equivalent, and a conversion between Normalization Forms C and D will +transform one into the other. This specification does not mandate a +particular Normalization Form (see ), but +users and implementers should be aware that it affects the character count +and therefore the result of evaluating pointers that rely on character +counting.

+
+ +
+range() +

Sequence range( POINTER, POINTER[, POINTER, POINTER ...])

+

The range() scheme takes as parameters one +or more pairs of POINTERs, which are each members of the set IDREF, +XPATH, left(), +right(), or +string-index(). A +range() locates a (possibly non-contiguous) +sequence beginning at the first POINTER parameter and ending at the +last. If a POINTER locates a node (i.e. is an XPATH or IDREF), then +that node is a member of the addressed sequence. If a sequence addressed +by a range pointer overlaps, but does not wholly contain, an element +(i.e. it contains only the start but not the end tag or vice-versa), +then that element is not part of the sequence.

+

Range()s may address sequences of +non-contiguous nodes. For example, a range() might select text beginning +before an app, encompassing the content of a single rdg +and continuing after the app.

+

Example: #range(left(//lb[@n='3']),left(//lb[@n='4'])) indicates +the whole of line 3 from the +]]> to the point right before the +following ]]>.

+

Example: #range(right(//lb[@n='3']),string-index(//lb[@n='3'],15)) + indicates the sequence semper in mente]]> (an element, a text node, another element, and a partial text node).

+

Example: #range(string-index(//lb[@n='3'],7),string-index(//lb[@n='3'],10),string-index(//lb[@n='3'],15),string-index(//lb[@n='3'],21)) indicates +the non-contiguous sequence in mentem.

+
+ +
+string-range() +

Sequence string-range(IDREF | XPATH, OFFSET, LENGTH[, OFFSET, LENGTH ...])

+

The string-range() scheme +locates a sequence based on character positions in a text stream relative +to the node identified by the first parameter. The location of the +beginning of the addressed sequence is determined precisely +as for string-index(). The OFFSET +parameter is defined as above in string-index(). +The LENGTH parameter is a positive integer that denotes +the length of the text stream captured by the sequence. As with +range(), the addressed sequence may +contain text nodes and elements. The +string-range() scheme can accept multiple +OFFSET, LENGTH pairs to address a non-contiguous sequence in much the +same way that range() can accept multiple pairs of pointers.

+

Because string-range() addresses points in the text stream, tags are +invisible to it. For example, if an empty tag like lb is +encountered while processing a string-range(), it will be included in +the resulting sequence, but the LENGTH count will not increment when +it is captured.

+

Example: #string-range(//lb[@n='5'],0,27) indicates +the whole of line 5 from the text immediately +following the lb to the point right before the closing +ab tag.

+

Example: #string-range(//lb[@n='3'],7,8) +indicates the sequence in mente.

+

Example: #string-range(//lb[@n='3'],7,3,15,6) indicates +the non-contiguous sequence in mentem.

+
+ +
+match() +

Sequence match(IDREF | XPATH, 'REGEX' [, INDEX])

+

The match scheme locates a sequence based on matching the REGEX parameter +against a text stream relative to the reference node identified by the first +parameter. REGEX is a regular expression as defined by +XQuery +1.0 and XPath 2.0 Functions and Operators (Second Edition), with some +modifications: + + Because the regular expression is delimited by apostrophe + characters, any such characters (' or U+0027) + occurring inside the expression must be escaped using the URI + percent-encoding scheme %27. + Regular expressions in match() are assumed to + operate in single-line mode. The end of the string to be matched + against is either the end of the text contained by the element in the + first parameter or the end of the document, if that parameter + indicates an empty element. The meta-character ^ + therefore matches the beginning of the text stream inside or following + the reference node, and the meta-character $ matches the + end of that stream. + + +The optional INDEX parameter is an integer greater than 0 which specifies which +match should be chosen when there is more than one possibility. If omitted, the +first match in the text stream will be used to resolve the match().

+

Like string-range(), match() may capture elements +in the indicated sequence, even though they are ignored for purposes of evaluating +the match.

+

Example: #match(//lb[@n='5'],'opto.*valeas') indicates the sequence +t bene valeas]]> in +line 5.

+

Example: #match(//lb[@n='3'],'semper') would indicate the +word semper, but would not capture the unclear elements +in semper]]>, just +their text children.

+
+
+
+Canonical References + +

By canonical reference we mean any means +of pointing into documents, specific to a community or +corpus. For example, biblical scholars might understand Matt +5:7 to mean the book called Matthew, chapter +5, verse 7. They might then wish to translate the string +Matt 5:7 into a pointer into a TEI-encoded document, +selecting the element which corresponds to the seventh +div element within the fifth div element +within the div element with the n attribute +valued Matt.

+

Several elements in the TEI scheme (gloss, +ptr, ref, and term) bear a special +attribute, cRef, just for this purpose. Using the +system described in this section, an encoder may specify +references to canonical works in a discipline-familiar format, +and expect software to derive a complete URI from it. The value +of the cRef attribute is processed as described in +this section, and the resulting URI reference is treated as if +it were the value of the target attribute. The +cRef and target attributes are mutually +exclusive: only one or the other may be specified on any given +occurrence of an element.

+

For the cRef attribute to function as required, a mechanism is needed to define the +mapping between (for example) the book called +Matt and the part of the XML structure which +corresponds with it. This is provided by the refsDecl element in the TEI header, +which contains an algorithm for translating a canonical reference string +(like Matt 5:7) into a URI such as #xpath(//div[@n='Matt']/div[5]/div[7]). The +refsDecl element is described in section ; the following example is discussed in more + detail below in section . An alternative and less verbose method is described in section . + + +

This pointer pattern extracts and references the book, +chapter, and verse parts of a biblical reference.

+ + +

This pointer pattern extracts and references the book and +chapter parts of a biblical reference.

+ + +

This pointer pattern extracts and references just the book +part of a biblical reference.

+ + +

+

When an application encounters a canonical reference as the +value of cRef attribute, it might follow this sequence of +specific steps to transform it into a URI reference: + + Ascertain the correct refsDecl + following the rules summarized in section . + For each cRefPattern element encountered in + the appropriate refsDecl, in the order encountered: + + match the value of the cRef attribute to the regular + expression found as the value of the matchPattern + attribute + if the value of the cRef attribute matches: + + take the value of the replacementPattern + attribute and substitute the back references ($1, $2, + etc.) with the corresponding matched substrings + the result is taken as if it were a relative or + absolute URI reference specified on the target + attribute; i.e., it should be used as is or combined with + the current xml:base attribute value as usual + no further processing of this value of the cRef + attribute against the refsDecl should take place + + + if, however, the value of the cRef attribute does not match + the regular expression specified in the value of the matchPattern attribute, + proceed to the next cRefPattern + + + If all the cRefPattern elements are + examined in turn and none matches, the pointer fails. +

+

The regular expression language used as the value of the +matchPattern attribute is that used for the +pattern facet of the World Wide Web Consortium's +XML Schema Language in an Appendix to +XML Schema Part 2.As always +seems to be the case, no two regular expression languages are +precisely the same. For those used to Perl regular expressions, +be warned that while in Perl the pattern tei +matches any string that contains tei, in +the W3C language it only matches the string tei. +The value of the replacementPattern attribute is simply a string, +except that occurrences of $1 through $9 are +replaced by the corresponding substring match. Note that since a +maximum of nine substring matches are permitted, the string +$18 means the value of the first matched substring +followed by the character 8 as opposed to the +eighteenth matched substring. If there is a need for an +actual string including a dollar sign followed by a digit that is +not supposed to be replaced, the dollar sign should be written +as $$. Implementations must convert $$ +to $ during processing.

+
+ Worked Example +

Let us presume that with the example refsDecl + above, an application comes across a cRef value of + Matt 5:7. The + application would first apply the regular expression + (.+) (.+):(.+) to Matt 5:7. This regular + expression would successfully match. The first matched + substring would be Matt, the second 5, and the + third 7. The application would then apply these + substrings to the pattern + #xpath(//div[@n='$1']/div[$2]/div[$3]), producing + #xpath(//div[@n='Matt']/div[5]/div[7]). +

+

If, however, the input string had been Matt 5, the + first regular expression would not have matched. The + application would have then tried the second, (.+) + (.+), producing a successful match, and the matched + substrings Matt and 5. It would then have + substituted those matched substrings into the pattern + #xpath(//div[@n='$1']/div[$2]) to produce a + fragment identifier indicating the referenced element.

+

If the input string had been Matt, neither the first + nor the second regular expressions would have successfully + matched. The application would have then tried the third, + (.+), producing the matched substring Matt, + and the URI Reference + #xpath(//div[@n='Matt']).

+

a cRefPattern should not reference more matched substrings. For example: + + is faulty, since only three matched + substrings would have been produced, but a fourth ($4) was + referenced.

+
+
+ Complete and Partial URI Examples +

In the above example, the value of cRef was used + to generate a Fragment Identifier. An absolute URI could be generated + directly, as in the following example. + + + +

Matches most standard references to particular + chapters of the United States Code, e.g. + 11USCC7, 17 U.S.C. Chapter 3, or + 14 USC Ch. 5. Note that a leading zero is + required for the title (must be two digits), but is not + permitted for the chapter number.

+ + +

Matches references to the preliminary material for a + given title, e.g. 11USCP, 17 U.S.C. + Prelim Mat, or 14 USC pm.

+ + +

Matches references to the appendix of a given tile, + e.g. 05USCA, 11 U.S.C. Appendix, + or 18 USC Append.

+ + + +

The example in section 10 is taken + from Subject Matter and Scope of + Copyright.

+ +

+

See for another related use of the matchPattern and replacementPattern attributes.

+
+
Miscellaneous Usages +

Canonical reference pointers are intended for use by TEI + encoders. However, this specification might be useful to the + development of a process for recognizing canonical + references in non-TEI documents (such as plain text + documents), possibly as part of their conversion to TEI.

+
+
+ Citation Structures +

Citation structures provide a more thorough and concise mechanism for describing canonical references + and the ways those references map on to parts of a TEI document. A citeStructure element + describes a single step in a reference, such as Matt, and may nest to handle multi-part references. +

+

The equivalent structure to the set of cRefPatterns in would be: + + + + + + + + + +

+

An application wishing to resolve a canonical reference such as Matt 5:7 might follow this procedure: + + Ascertain the correct refsDecl + following the rules summarized in section . + Begin with the outer citeStructure. If it has a delim attribute + and the reference begins with the value of delim then take the portion of + the reference after the value of delim as input for the next child citeStructure. + For each nested citeStructure, if the input reference string contains the value + of the delim, then split the string on the value of the delim attribute. + If the input string does not contain delim, then stop. Take the portion of the input + string after the value of delim and use it as the input string for the child citeStructure. + After processing the outer citeStructure, the output will be ('Matt 5:7'), after + the second, ('Matt', '5:7'). The end result will be a + sequence like ('Matt','5','7'). + For each item in the resulting sequence, resolve the matching node by evaluating + the XPath in match with the predicate found in use, using the + context of the previously matched node, if any. Start with the outer citeStructure + and move to the next child citeStructure for each step in the sequence. For + example, for the first citeStructure, we could construct an XPath + //div[@n='Matt']. The full XPath after the reference Matt 5:7 is resolved will be + //div[@n='Matt']/div[@n='5']/div[@n='7']. + + One advantage citeStructure has is that it can be used to generate canonical + references, using the declared citation structure to query the text structure. This means it is + possible to automatically produce a list of resolvable citations for a TEI document. It also + enables the automatic breaking of documents into smaller chunks for presentation and automated + generation of tables of contents.

+

Citation structures may in addition specify how informational properties are to be extracted from the + document sections they identify, using the citeData element. For example, if a TEI document + is divided into chapters with a div per chapter and those chapters have titles, contained in + head elements, then we might declare a citation structure for the document thus: + + + + + +

+

This specifies that chapter references are given in the form ch. n, where n + is the position of the div in the body of the document, and that we may obtain + the title of the chapter (identified by the Dublin Core property title) from the chapter + heading. This would, for example, enable the automated generation of a chapter listing for the document.

+
+
+
+
+ Blocks, Segments, and Anchors + +

In this section, we discuss three general purposes elements which +may be used to mark and categorize both a span of text and a point +within one. These elements have several uses, most notably to provide +elements which can be given identifiers for use when aligning or +linking to parts of a document, as discussed elsewhere in this +chapter. They also provide a convenient way of extending the semantics +of the TEI markup scheme in a theory-neutral manner, by providing for +two neutral or anonymous elements to which the +encoder can add any meaning not supplied by other TEI defined +elements. + + + + + + The elements anchor, ab, and seg are members of + the class att.typed, from which they + inherit the following attributes: + + + +The elements ab, and seg are members of + the class att.fragmentable, from which they + inherit the following attribute: + + + + The seg element is also a member of the class att.segLike from which it inherits the + following attribute: + + + +

+

The anchor element may be thought of as an empty + seg, or as an artifice enabling an identifier to be + attached to any position in a text. Like the milestone + element discussed in section , it is useful + where multiple views of a document are to be combined, for + example, when a logical view based on paragraphs or verse lines is + to be mapped on to a physical view based on manuscript lines. Like + those elements, it is a member of the class model.global and can therefore appear + anywhere within a document when the module defined by this chapter + is included in a schema. Unlike the other elements in its class, + the anchor element is primarily intended to mark + an arbitrary point used for alignment, or as the target of a + spanning element such as those discussed in section , rather than as a means of marking segment + boundaries for some arbitrary segmentation of a text.

+

For example, suppose that we wish to mark the end of the fifth + word following each occurrence of some term in a particular text, + perhaps to assist with some collocational analysis. This can most + easily be done with the help of the anchor element, as + follows: + + English language. Except for not very +English at all at the time +English was still full of flaws +English. This was revised by young + In section we discuss ways in which these + anchor points might be used to represent an alignment + such as one might get in a keyword-in-context concordance.

+

The seg element may be used at the encoder's + discretion to mark almost any segment of the text of interest for + processing. One use of the element is to mark text features for + which no appropriate markup is otherwise defined, i.e. as a simple + extension mechanism. Another use is to provide an identifier for + some segment which is to be pointed at by some other element, i.e. + to provide a target, or a part of a target, for a ptr or + other similar element.

+

Several examples of uses for the seg element are + provided elsewhere in these Guidelines. For example: + +as a means of marking segments significant in a metrical +or rhyming analysis (see section ) +as a means of marking typographic lines in drama (see +section ) or title pages (see section ) +as a means of marking prosody- or pause-defined units in +transcribed speech (see section ) +as a means of marking linguistic or other analyses in a +theory-neutral manner (see chapter +passim)

+ +

In the following simple example, the seg element simply +delimits the extent of a stutter, a textual feature for which no +element is provided in these Guidelines. Don't say I-I-I'm afraid, Melvin, just say I'm +afraid. + +The seg element is particularly useful for the markup +of linguistically significant constituents such as the phrases +that may be the output of an automatic parsing system. This +example also demonstrates the use of the xml:id +attribute to carry an identifier which other parts of a document +may use to point to, or align with: + + Literate and illiterate speech + in a language like English + are plainly different. + +

+

As the above example shows, seg elements may be +nested directly within one another, to any degree of analysis +considered appropriate. This is taken a little further in the +following example, where the type and +subtype attributes have been used to further +categorize each word of the sentence (the xml:id +attributes have been removed to reduce the complexity of the +example): + + +Literate +and +illiterate +speech + + +in +a +language +like +English + + +are +plainly +different + + . +

+

(The example values shown are chosen for simplicity of +comprehension, rather than verisimilitude). It should also be +noted that specialized segment elements are defined in section + to facilitate this particular kind of +analysis. These allow for the explicit markup of units called +s-units, clauses, +phrases, words, morphemes, +and characters, which may be felt preferable to the +more generic approach typified by use of the seg +element. Using these, the first phrase above might be encoded +simply as + + Literate + and + illiterate + speech + +Note the way in which the type attribute of these +specialized elements now carries the value carried by the +subtype attribute of the more general seg +element. For an analysis not using these traditional linguistic +categories however, the seg element provides a simple +but powerful mechanism.

+

In language corpora and similar material, the seg +element may be used to provide an end-to-end segmentation as an +alternative to the more specific s element proposed in +chapter for the markup of orthographic +sentences, or s-units. However, it may be more +useful to use the s element for this purpose, since +this means that the seg element can then be used to +mark both features within s-units and segments composed of +s-units, as in the following example:See +section , where the text from which this +fragment is taken is analyzed. + + Sigmund, the son of Volsung, + was a king in Frankish country. + Sinfiotli was the eldest of his sons. + ... +

+

Like other elements, the seg tag must be properly +enclosed within other elements. Thus, a single seg +element can be used to group together words in different +sentences only if the sentences are not themselves tagged. The +first of the following two encodings is legal, but the second is +not. + +Give me a dozen. Or two or three. + +Give me a dozen. +Or two or three.]]>

+

The part attribute may be used as one simple +method of overcoming this restriction: +Give me a dozen. +Or two or three. +Another solution is to use the join element discussed +in section ; this requires that each of the +seg elements be given an identifier. For further +discussion of this generic encoding problem, see also chapter +.

+

The seg element has the same content as a paragraph +in prose: it can therefore be used to group together consecutive +sequences of model.inter class elements, +such as lists, quotations, notes, stage directions, etc. as well +as to contain sequences of phrase-level elements. It cannot +however be used to group together sequences of paragraphs or +similar text units such as verse lines; for this purpose, the +encoder should use intermediate pointers, as described in +section or the methods described in +section . It is particularly important that +the encoder provide a clear description of the principles by +which a text has been segmented, and the way in which that +segmentation is represented. This should include a description +of the method used and the significance of any categorization +codes. The description should be provided as a series of +paragraphs within the segmentation element of the +encoding description in the TEI header, as described in section +.

+

The seg element may also be used to encode +simultaneous or mutually exclusive variants of a text when the +more special purpose elements for simple editorial changes, +abbreviation and expansion, addition and deletion, or for a +critical apparatus are not appropriate. In these circumstances, +one seg is encoded for each possible variant, and the +set of them is enclosed in a choice element.

+

For example, if one were writing dual-platform instructions for +installation of software, it might be useful to use seg +to record platform-specific pieces of mutually exclusive text. +…pressing option +alt-f will …

+

Elsewhere in this chapter we provide a number of examples +where the seg element is used simply to provide an +element to which an identifier may be attached, for example so +that another segment may be linked or related to it in some +way.

+

The ab (anonymous block) element functions like the + seg element, but is used for portions + of the text which occur at the chunk level + (See ). It is therefore a member of the + model.pLike class. Like seg, + but unlike p, ab may nest within other ab + elements. So it may be used to represent texts with irregular + chunk-level structures.

+

Probably the most common use for ab is as a container for +text that does not naturally belong in a paragraph. The text of an +epitaph, for example, may not be paragraph-like, but still requires +a container: + + + SACRED + to the memory of + Mrs. ALICE HUTTON + born at Chesterfield in + Great Britain, + Jany. 25th. 1722: + and died in Carolina + Septr. 26th. 1777. + This stone + is placed by her only Child + ANN BOOTH POLLOK + +Encoders may also prefer to treat other types of short documents, such as receipts, in this way.

+

The ab element may also be used, for +example, to tag the canonical verse divisions of Biblical texts: + + The First Book of Moses, Called + Genesis + + In the beginning God created the heaven and the +earth. + And the earth was without form, and void; and darkness +was upon the face of the deep. And the Spirit of God +moved upon the face of the waters. + And God said, Let there be light: and there was +light. + + +

+

In other cases, where the text clearly indicates paragraph +divisions containing one or more verses, the p element +may be used to tag the paragraphs, and the seg element +used to subdivide them. The ab element is provided as +an alternative to the p element; it may +not be used within paragraphs. The seg +element, by contrast, may appear only within and not between +paragraphs (or anonymous block elements). + + Das Erste Buch Mose. + +

+Am Anfang schuff Gott Himel vnd Erden. +Vnd die Erde war wüst vnd leer / vnd es war + finster auff der Tieffe / Vnd der Geist Gottes schwebet auff + dem Wasser.

+

+Vnd Gott sprach / Es werde Liecht / Vnd es ward + Liecht.

+ + +

+

The ab element is also useful for marking dramatic +speeches when it is not clear whether the speech is to be +regarded as prose or verse. If, for example, an encoder does not +wish to express an opinion as to whether the opening lines of +Shakespeare's The Tempest are to be regarded as +prose or as verse, they might be tagged as follows: + + Actus primus, Scena prima. + A tempestuous noise of +Thunder and Lightning heard: +Enter a Ship-master, and a Boteswaine. + Master. + Bote-swaine. + Botes. + Heere Master: What cheere? + Mast. + Good: Speake to th' Mariners: fall too't, yarely, + or we run our selues a ground, bestirre, bestirre. + Exit. + + Enter Mariners. + Botes. + 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. + + +See further and .

+ + + + + +
+
+Synchronization +

In the previous section we discussed two particular kinds of +alignment: alignment of parallel texts in different languages; and +alignment of texts and portions of an image. In this section we address +another specialized form of alignment: synchronization. The need to +mark the relative positions of text components with respect to time +arises most naturally and frequently in transcribed spoken texts, but it +may arise in any text in which quoted speech occurs, or events are +described within a time frame. The methods described here are also +generalizable for other kinds of alignment (for example, alignment of +text elements with respect to space).

+
+Aligning Synchronous Events + +

Provided that explicit elements are available to represent the +parts or places to be synchronized, then the global linking attribute +synch may be used to encode such synchronization, once it +has been identified. + + + + This is another of the attributes made globally available by + the mechanism described in the introduction to this chapter. + Alternatively, the link and linkGrp elements + may be used to make explicit the fact that the synchronous + elements are aligned.

+

To illustrate the use of these mechanisms for marking synchrony, +consider the following representation of a spoken text: + +

+

This representation uses numbers in brackets to mark the points at +which speakers overlap each other. For example, the [1] +in A's first speech is to be understood as coinciding with the +[1] in B's second speech.This sample is taken from +a conversation collected and transcribed for the British National +Corpus.

+

To encode this we use the spoken texts module, described +in chapter , together with the module +described in the present chapter. First, we transcribe this text, +marking the synchronous points with anchor elements, and +providing a synch attribute on one of each of the pairs of +synchronous anchors. As noted in the example given above (section ), correspondence, and hence synchrony, is a +symmetric relation; therefore the attribute need only be specified on +one of the pairs of synchronous anchors. +

+ + The first time in twenty five years, + we've cooked Christmas for a blooming great + load of people. +So you're + + +It will be + nice in a way, but, + be strange. +Yeah + , yeah, cos it, its + the + +not +

+

We can encode this same example using link and +linkGrp elements to make the temporal alignment explicit. A back +element has been used to enclose the linkGrp element, but the links +may be located anywhere the encoder finds convenient: + + + + + + + + + + +The +xml:id attributes are provided for the link and +linkGrp elements here for reasons discussed in the next +section, . +

+

As with other forms of alignment, synchronization may be expressed +between stretches of speech as well as between points. When complete +utterances are synchronous, for example, if one person says +What? and another No! at the same time, +that can be represented without anchor elements as follows. +What? +No!

+

A simple way of expressing overlap (where one speaker +starts speaking before another has finished) is thus to use the +seg element to encode the overlapping portions of speech. For +example, + So you're + It will be nice in a way, but, + be strange. + Yeah , yeah, cos it, + its the + not +Note in this encoding how synchronization has been effected between an +empty unclear element and the content of a seg element, and between the +content of a +u element and that of another seg, using the synch +attribute. Alternatively, a linkGrp could be used in the same +way as above.

+
+Placing Synchronous Events in Time +

A synchronous alignment specifies which points in a spoken text occur +at the same time, and the order in which they occur, but does not say at +what time those points actually occur. If that information is available +to the encoder it can be represented by means of the when and +timeline elements, whose description and attributes are the +following: +

+

Each when element indicates a point in time, either directly +by means of the absolute attribute, whose value is a string +which specifies a particular time, or indirectly by means of the +since attribute, which points to another when. If +the since is used, then the interval and +unit attributes should also be used to indicate the amount of +time that has elapsed since the time specified by the element pointed to +by the since attribute; the value -1 +can be given to indicate that the interval is unknown.

+

If the when elements are uniformly spaced in time, then the +interval and unit values need be given once in the +timeline, and not repeated in any of the when +elements. If the intervals vary, but the units are all the same, then +the unit attribute alone can be given in the +timeline element, and the interval attribute given +in the when element.

+

The origin attribute in the timeline element +points to a when element which specifies the reference or +origin for the timings within the timeline; this must, of +course, specify its position in time absolutely. If the origin of a +timeline is unknown, then this attribute may be omitted.

+

The following timeline might be used to accompany the marked +up conversation shown in the preceding section: + + + + + + + + + +The information in this timeline could now be linked to the +information in the linkGrp which provides the temporal +alignment (synchronization) for the text, as follows: + + + + + + + +

+

To avoid the need for two distinct link groups (one marking the +synchronization of anchors with each other, and the other marking their +alignment with points on the time line) it would be better to link the +when elements with the synchronous points directly: + + + + + + + +

+ + +

Finally, suppose that a digitized audio recording is also +available, and an XML file that assigns identifiers to the various +temporal spans of sound is available. For example, the following +Synchronized Multimedia Integration Language (SMIL, pronounced +"smile") fragment: + + +URIs pointing to the audio elements could also +be included as a fourth component in each of the above link +elements, thus providing a synchronized audio track to complement the +transcribed text.

+

For further discussion of this and related aspects of encoding +transcribed speech, refer to chapter .

+ + + +
+
+ +Correspondence and Alignment +

In this section we introduce the notions of +correspondence, expressed by the corresp +attribute, and of alignment, which is a special +kind of correspondence involving an ordered set of +correspondences. Both cases may be represented using the +link and linkGrp elements introduced in +section . We also discuss the special case +of alignment in time or synchronization, for which +special purpose elements are proposed in section .

+
+ Correspondence +

A common requirement in text analysis is to represent + correspondences between two or more parts of a single + document, or between places in different documents. Provided + that explicit elements are available to represent the parts or + places to be linked, then the global linking attribute + corresp may be used to encode such correspondence, + once it has been identified. + + + + This is one of the attributes made available by the mechanism + described in the introduction to this chapter (). Correspondence can also be expressed by means + of the link element introduced in section .

+

Where the correspondence is between spans, the + seg element should be used, if no other element is + available. Where the correspondence is between + points, the anchor element should be + used, if no other element is available.

+

The use of the corresp attribute with spans of + content is illustrated by the following example: +Shirley, which made +its Friday night debut only a month ago, was +not listed on NBC's new schedule, +although the network +says the show +still is being considered. + + + + Here the anaphoric phrases the network + and the show have been associated + directly with the elements to which they refer by means of + corresp attributes. This mechanism is simple to + apply, but has the drawback that it is not possible to specify + more exactly what kind of correspondence is intended. Where + this attribute is used, therefore, encoders are encouraged to + specify their intent in the associated encoding description + in the TEI header.

+

Essentially, what the corresp attribute does is + to specify that elements bearing this attribute and those +to which the attribute points are doubly linked. In the example above, +the use of the corresp attribute indicates that the seg element containing the show and the +title element containing Shirley correspond to each +other: the correspondence relationship is not from +one to the other, but between the two +objects. It is thus different from the target attribute, +and provides functionality more similar to that of the link and linkGrp elements defined in + section , although it lacks the ability to + indicate more precisely what kind of correspondence is + intended as in the following retagging of the preceding + example. +Shirley, which made +its Friday night debut only a month ago, was not +listed on NBC's new schedule, +although the network says +the show still is being considered. + + + +

+

In the following example, we use the same mechanism to +express a correspondence amongst the anchors introduced following the +fifth word after English in a text: + +English language. Except for not very + +English at all at the time + +English was still full of flaws + +English. This was revised by young + + + + + +

+
+ Alignment of Parallel Texts +

One very important application area for the alignment of + parallel texts is multilingual corpora. Consider, for + example, the need to align translation + pairs of sentences drawn from a corpus such as + the Canadian Hansard, in which each sentence is given in + both English and French. Concerning this problem, Gale and + Church write: Most English sentences match + exactly one French sentence, but it is possible for an + English sentence to match two or more French sentences. The + first two English sentences [in the example below] + illustrate a particularly hard case where two English + sentences align to two French sentences. No smaller + alignments are possible because the clause + ...sales...were higher... in the first English + sentence corresponds to (part of) the second French + sentence. The next two alignments ... illustrate the more + typical case where one English sentence aligns with exactly + one French sentence. The final alignment matches two English + sentences to a single French sentence. These alignments + [which were produced by a computer program] agreed with the + results produced by a human judge.See + , from which the example in the + text is taken.

+

The alignment produced by Gale and Church's program can + be expressed in four different ways. The encoder must first + decide whether to represent the alignment in terms of points + within each text (using the anchor element) or in + terms of whole stretches of text, using the seg + element. To some extent the choice will depend on the + process by which the software works out where alignment + occurs, and the intention of the encoder. Secondly, the + encoder may elect to represent the actual encoding using + either corresp attributes attached to the + individual anchor or seg elements, or + using a free-standing linkGrp element.

+

We present first a solution using anchor + elements bearing only corresp attributes: +

+

According to our survey, 1988 +sales of mineral water and soft drinks were much higher than in 1987, +reflecting the growing popularity of these products. Cola drink +manufacturers in particular achieved above-average growth rates. +The higher turnover was largely +due to an increase in the sales volume. +Employment and investment levels also climbed. +Following a two-year transitional period, +the new Foodstuffs Ordinance for Mineral Water came into effect on +April 1, 1988. Specifically, it contains more stringent requirements +regarding quality consistency and purity guarantees.

+
+
+

Quant aux eaux minérales +et aux limonades, elles rencontrent toujours plus d'adeptes. En effet, +notre sondage fait ressortir des ventes nettement supérieures +à celles de 1987, pour les boissons à base de cola +notamment. La progression des +chiffres d'affaires résulte en grande partie de l'accroissement +du volume des ventes. L'emploi et +les investissements ont également augmenté. +La nouvelle ordonnance fédérale +sur les denrées alimentaires concernant entre autres les eaux +minérales, entrée en vigueur le 1er avril 1988 après +une période transitoire de deux ans, exige surtout une plus +grande constance dans la qualité et une garantie de la +pureté.

+

+

There is no requirement that the corresp + attribute be specified in both English and French texts, since + (as noted above) this attribute is defined as representing a + mutual association. However, it may simplify processing to do + so, and also avoids giving the impression that the English is + translating the French, or vice versa. More seriously, this + encoding does not make explicit that it is in fact + the entire stretch of text between the anchors which is being + aligned, not simply the points themselves. If for example one + text contained material omitted from the other, this approach + would not be appropriate.

+

We now present the same passage using the alternative + linkGrp mechanism and marking explicitly the segments + which have been aligned: +

+

+ According to our survey, 1988 sales of mineral +water and soft drinks were much higher than in 1987, +reflecting the growing popularity of these products. Cola +drink manufacturers in particular achieved above-average +growth rates. + The higher turnover was largely due to an +increase in the sales volume. + Employment and investment levels also climbed. + Following a two-year transitional period, the new +Foodstuffs Ordinance for Mineral Water came into effect on +April 1, 1988. Specifically, it contains more stringent +requirements regarding quality consistency and purity +guarantees.

+
+
+

+ Quant aux eaux minérales et aux limonades, +elles rencontrent toujours plus d'adeptes. En effet, notre +sondage fait ressortir des ventes nettement +supérieures à celles de 1987, pour les +boissons à base de cola notamment. + La progression des chiffres d'affaires +résulte en grande partie de l'accroissement du volume +des ventes. + L'emploi et les investissements ont +également augmenté. + La nouvelle ordonnance fédérale sur +les denrées alimentaires concernant entre autres les +eaux minérales, entrée en vigueur le 1er avril +1988 après une période transitoire de deux +ans, exige surtout une plus grande constance dans la +qualité et une garantie de la pureté.

+
+ + + + + +

+

Note that use of the ab element allows us to mark up the +orthographic sentences in both languages independently of the alignment: +the first translation pair in this example might be marked up as +follows: +

+ + According to our survey, 1988 sales of mineral water and soft +drinks were much higher than in 1987, reflecting the growing popularity +of these products. + Cola drink manufacturers in particular achieved above-average +growth rates. + +
+
+ + Quant aux eaux minérales et aux limonades, elles +rencontrent toujours plus d'adeptes. + En effet, notre sondage fait ressortir des ventes nettement +supérieures à celles de 1987, pour les boissons à +base de cola notamment. + +
+

+
+A Three-way Alignment +

The preceding encoding of the alignment of parallel passages from +two texts requires that those texts and the alignment all be part of +the same document. If the texts are in separate documents, then +complete URIs, whether absolute or relative (section ), will be required. These external pointers may appear +anywhere within the document, but if they are created solely for use +in encoding links, they may for convenience be grouped within the +linkGrp (or other grouping element that uses them for +linking).

+

To demonstrate this facility, we consider how we might encode the +alignments in an extract from Comenius' Orbis Sensualium +Pictus, in the +English translation of Charles Hoole (1659). + +

+ +
+Each topic covered in this work has three parts: a +picture, a prose text in Latin describing the topic, and a +carefully-aligned translation of the Latin into English, German, or some +other vernacular. Key terms in the two texts are typographically +distinct, and are linked to the picture by numbers, which appear in the +two texts and within the picture as well.

+

First, we consider the text portions. The English and Latin portions +have been encoded as distinct div elements. Identifiers have +been attached to each typographic line, but no other encoding added, to +simplify the example. + +

+ The Study +

+The Study +is a place +where a Student, +a part from men, +sitteth alone, +addicted to his Studies, +whilst he readeth +Books,

+
+
+ Muséum +

+Museum +est locus +ubi Studiosus, +secretus ab hominibus, +solus sedet, +Studiis deditus, +dum lectitat +Libros,

+

+ +

Next we consider the non-textual parts of the page. Encoding this +requires providing two distinct components: firstly a digitized rendering of the +page itself, and secondly a representation of the areas within that image +which are to be aligned. In section we present a +simple way of doing this using the TEI-defined markup for alignment of +facsimiles. In the present chapter we demonstrate a more powerful +means of aligning arbitrary polygons and points, which uses the XML notation SVG (see SVG). This provides appropriate facilities for both these +requirements: + + + + + + + +This example of SVG defines two rectangles +at the locations with the specified x and y coordinates. A view is +defined on these, enabling them to be +mapped by an SVG processor to the image found at the URL specified +(p1764.png). It also defines unique identifiers for +the whole image, and the two views of it, which we will use within our +alignment, as shown next (for further discussion of the handling of + images and graphics, see section ; for further + discussion of using non-TEI XML vocabularies such as SVG within a TEI + document, see section ). +

+

As printed, the Comenius text exhibits three kinds of alignment. + + The English and Latin portions are printed in two + parallel columns, with corresponding phrases, (represented above by + seg elements), more or less next to each other. + Particular words or phrases are marked as terms in the + two languages by a change of rendition: the English text, which + otherwise uses black letter type throughout, has the words + The Study, a Student, + Studies, and Books in + a roman font; in the Latin text, which is printed in roman, the + corresponding words (Museum, + Studiosus, Studiis, + and Libros) are all in italic. + Numbered labels appear within the text portions, + linking keywords to each other and to sections of the picture. + These labels, which have been left out of the above encoding, are + attached to the first, third, and last segments in each language + quoted below, and also appear (rather indistinctly) within the + picture itself. Thus, the images of the study, the student, and his + books are each aligned with the correct term for them in the two + languages. +

+

The first kind of alignment might be represented by using the +corresp attribute on the seg element. The second +kind might be represented by using the gloss and term +mechanism described in section . The third kind of +alignment might be represented using pointers embedded within the +texts, for example: + + +where a Student, +ubi Studiosus, + + + +We choose however to use +the link element, since this provides a more efficient way of +representing the three-way alignment between English, Latin, and picture +without redundancy. + + + + + + + + + +

+

This map, of course, only aligns whole segments and image portions, +since these are the only parts of our encoding which bear identifiers +and can therefore be pointed to. To add to it the alignment between +the typographically distinct words mentioned above, new elements must +be defined, either within the text itself or externally by using stand +off techniques. Encoding these word pairs as term +and gloss, although intuitively obvious, requires a +non-trivial decision as to whether the Latin text is glossing the +English, or vice versa. Tagging all the marked words as term +avoids the difficult decision, but might be thought by some encoders +to convey the wrong information about the words in question. Simply +tagging them as additional embedded seg elements with +identifiers that can be aligned like the others is also a possibility. +

+

These solutions all require the addition of further markup to the text. This +may pose no problems, or it may be infeasible, for example because the text is +held on a read-only medium. If it is not feasible to add more markup +to the original text, some form of stand-off markup will be +needed. Any item within the text that can be pointed to using the +various pointer schemes discussed in this chapter may be used, not +simply those which rely on the existence of an xml:id +attribute. Suppose our example had been +more lightly tagged, as follows: + +

+ The Study + The Study + is a place + where a Student, +
+
+ Muséum + Museum + est locus + ubi Studiosus, +
+

+

To express the same alignment mentioned above, we could use an +XPath expression to identify the required ab elements: + + + + + +In the absence of any markup around individual substrings of +the element content, the string-range pointer scheme discussed in may also be helpful: for example, to indicate that the words +Studies and Studiis +correspond, we might express the link between them as follows: + +

+ +
+
+Identical Elements and Virtual Copies +

This section introduces the notion of a virtual element, +that is, an element which is not explicitly present in a text, but the +presence of which an application can infer from the encoding supplied. +In this section, we are concerned with virtual elements made by simply +cloning existing elements. In the next section (), we +discuss virtual elements made by aggregating existing elements.

+

Provided + that explicit elements are available to represent the parts or + places to be linked, then the global linking attributes + sameAs and copyOf may be used to encode +this kind of equivalence: + + + +

+

It is useful to be able to represent the fact that one element of +text is identical to others, for analytical purposes, or (especially if +the elements have lengthy content) to obviate the need to repeat the +content. For example, consider the repetition of the date +element in the following material: +

In small clumsy letters he wrote: +April 4th, +1984.

+

He sat back. A sense of complete helplessness had +descended upon him. ...

+

His small but childish handwriting straggled up +and down the page, shedding first its capital letters +and finally even its full stops: +April 4th, 1984. +Last night to the flicks. ...

+Suppose now that we wish to encode the fact that the second +date element above has identical content to the first. The +sameAs attribute is provided for this purpose. Using it, we +could recode the last line of the above example as follows: +April 4th, +1984 +Last night to the flicks ...

+

The sameAs attribute may be used to document the fact +that two elements have identical content. It may be regarded as a +special kind of link. It should only be attached to an element with +identical content to that which it targets, or to one the content of which +clearly designates it as a repetition, such as the word +repeat or bis in the +representation of the chorus of a song, the second time it is to be +sung. The relation specified by the sameAs attribute is +symmetric: if a chorus is repeated three times and each repetition +bears a sameAs attribute indicating the first occurrence of +the element concerned, it is implied that each chorus is identical, +and there is no need for the first occurrence to specify any of its +copies.

+

The copyOf attribute is used in a similar way to +indicate that the content of the element bearing it is identical to +that of another. The difference is that the content is not itself +repeated. The effect of this attribute is thus to create a +virtual copy of the element indicated. Using this +attribute, the repeated date in the first example above could be +recoded as follows: +

+

An application program should replace whatever is the actual content +of an element bearing a copyOf attribute with the content of +the element specified by it. If the content of the element specified +includes other elements, these will become embedded within the element +bearing the attribute. Care must be taken to ensure that the document +is valid both before and after this embedding takes +place. If, for example, the element bearing a copyOf +attribute requires a mandatory sub-component, then this component must +be present (though possibly empty), even though it will be replaced by +the content of the targetted element.

+

The following example demonstrates how the copyOf +attribute may be used in conjunction with the seg element to +highlight the differences between almost identical repetitions: + +Mikado + My object all sublime + I shall achieve in time— + To let the punishment fit the crime, + ; + And make each pris'ner pent + Unwillingly represent + A source of innocent merriment, + ! + +Chorus + His + He will + + + + + + + +

+

For further examples of the use of this attribute, see and .

+
+Aggregation +

Because of the strict hierarchical organization of elements, or for +other reasons, it may not always be possible or desirable to include +all the parts of a possibly fragmented text segment within a single +element. In section we introduced the notion of +an intermediate pointer as a way of pointing to discontinuous segments +of this kind. In this section we first describe another way of linking +the parts of a discontinuous whole, using a set of linking attributes, +which are made available for any tag by following the procedure +described at the beginning of this chapter. We then describe how the +link element may be used to aggregate such segments, and +finally introduce the join element, which is a +special-purpose linking element specifically for representing the +aggregation of parts, and the joinGrp for grouping +join elements.

+

The linking attributes for aggregation are next and +prev; each of these attributes has a single identifier as its +value: +

+

It is recommended that the elements indicated by these attributes be of the same type as the element bearing them.

+ +

The join element is also a member of the class of att.pointing elements, and so may carry any of the +attributes of that class; for the list, see section .

+

Here is the material on which we base our first illustration of the +use of these mechanisms. Our problem is to represent the s-units +identified below as qs3 and qs4 as a single (but discontinuous) whole: +Monsieur Paul, after he has taken equal +parts of goose breast and the finest pork, and +broken a certain number of egg yolks into them, +and ground them very, very fine, +cooks all with seasoning for some three hours. + +But, +she pushed her face nearer, and looked with + ferocious gloating at the pâté + inside me, her eyes like X rays, + + he never stops stirring it! + Figure to yourself the work of it — + stir, stir, never stopping! + + +

+

Using the prev and next attributes, we can +link the s-units with identifiers qs3 and qs4, either singly or doubly as follows: +But, + he never stops stirring it!]]> +But, + he never stops stirring it!]]> +But, + he never stops stirring it!]]> +Double linking of the two s-units, as illustrated by the last of these +encodings, is equivalent to specifying a link element: +

+

Such a link element must carry a type +attribute with a value of join to specify that the link is +to be understood as joining its targets into a single aggregate.

+

The join element is equivalent to a link element of +type join. + +Unlike the link element, the join element can +additionally specify information about the virtual element which it +represents, by means of its result attribute. And finally, +unlike the link element, the position of a join +element within a text is significant: it must be supplied at a position +where the element indicated by its result attribute would be +contextually legal. + +To conclude the above example, we now use a join element to +represent the virtual sentence formed by the aggregation of s1 and s2: + +As a further example, consider the following list of authors' names. +The object of the join element here is to provide another +list, composed of those authors from the larger list who happen to +come from Heidelberg: + +Authors + Figge, Udo + Heibach, Christiane + Heyer, Gerhard + Philipp, Bettina + Samiec, Monika + Schierholz, Stefan + + +Authors from Heidelberg

+

The following example shows how join can be used to +reconstruct a text cited in fragments presented out of order. The poem +being remembered (an unusual translation of a well-known poem by Basho) +runs When the old pond / gets a new frog, / it's a new pond.

+ +Hughie +

How does it go? + + da-da-da + gets a new frog + ... + +

+ +Louie +

+ +When the old pond +... + +

+ +Dewey +

+ ... + It's a new pond. + +

+ + + +

As with other forms of link, a grouping element joinGrp +is available for use when a number of join elements of the +same kind co-occur. This avoids the need to specify the +result attribute for each join if they are all of +the same type, and also allows us to restrict the domain within which +their target elements are to be found, in the same way as for +linkGrp elements (see ). Like a +join, a joinGrp may appear only where the elements +represented by its contents are legal. Thus if we had created many +join tags of the sort just described, we could group them +together, and require that their components are all contained by an +element with the identifier MFKFhungry as +follows: + + + + + +

+

The join element is useful as a means of representing +non-hierarchic structures (as further discussed in chapter ). It may also be used as a convenient way of representing a +variety of analytic units, like the span and interp +elements discussed in chapter . As an example, consider +the following famous Zen koan: + +

Zui-Gan called out to himself every day, Master.

+

Then he answered himself, Yes, sir.

+

And then he added, Become sober.

+

Again he answered, Yes, sir.

+

And after that, he continued, do not be deceived by +others.

+

Yes, sir; yes, sir, he replied.

+

Suppose now that we wish to represent an interpretation of the above +passage in which we distinguish between the various +voices adopted by Zui-Gan. In the +following encoding, the who attribute has been used for this +purpose; its value on each occasion supplies a pointer to the +voice to which each speech is attributed. (For convenience in +this example, we use simply the first occurrence of the names used for +each voice as the target for these pointers.) Note also that we add +xml:id attributes to each distinct speech fragment, which +we can then use to link the material +spoken by each voice: + + +

Zui-Gan called out to himself every day, + Master.

+

Then he answered himself, + Yes, sir.

+

And then he added, + Become sober.

+

Again he answered, + Yes, sir.

+

And after that, + he continued, + do not be deceived by others.

+

Yes, sir; yes, sir, + he replied.

+ +

+

However, by using the join element, we can directly +represent the complete speech attributed to each voice: + + + what Zui-Gan said + + what Master said +

+

Note the use of the desc child element within the two +joins making up the q element here. These enable us +to document the speakers of the two virtual q elements +represented by the join elements; this is necessary because the +there is no way of specifying the attributes +to be associated with a virtual element, in particular there is no way +to specify a +who value for them.

+

Suppose now that xml:id attributes, for whatever +reasons, are not available. Then ptr elements may be created +using any of the methods described in section . +The xml:id attributes of +these elements may now be specified by the +target attribute on the join elements. + + + + +

Zui-Gan called out to himself every day, Master.

+

Then he answered himself, Yes, sir.

+

And then he added, Become sober.

+

Again he answered, Yes, sir.

+

And after that, he continued, do not be deceived by others.

+

Yes, sir; yes, sir, he replied.

+ + + + + + + + + + + what Zui-Gan said + + what Master said + + + +

+

The extended pointer with identifier +rzuiq2, for example, may be read as the first +q in the first p, within the sixth div1 +element of the current document.

+ + + + +
+
+Alternation +

This section proposes elements for the representation of alternation. +We say that two or more elements are in exclusive +alternation if any of those elements could be present in a text, +but one and only one of them is; in addition, we say that those elements +are mutually exclusive. We say that the elements are in +inclusive alternation if at least one (and possibly more) +of them is present. The elements that are in alternation may also be +called alternants.

+

The need to mark exclusive alternation arises frequently in text +encoding. A common situation is one in which it can be determined that +exactly one of several different words appears in a given location, but +it cannot be determined which one. One way to mark such an exclusive +alternation is to use the linking attribute exclude. Having +marked an exclusive alternation, it can sometimes later be determined +which of the alternants actually appears in the given location. To +preserve the fact that an alternation was posited, one can add the +linking attribute select to a tag which hierarchically +encompasses the alternants, which points to the one which actually +appears. To assign responsibility and degree of certainty to the +choice, one can use the certainty tag described in +chapter . Also see that chapter for further discussion of +certainty in general.

+

The exclude and select attributes may be used +with any element assuming that they have been declared following the +procedure discussed in the introduction to this chapter. + + +

+

A more general way to mark alternation, encompassing both exclusive +and inclusive alternation, is to use the linking element alt. +The description and attributes of this tag and of the associated +grouping tag altGrp are as follows. These elements are also +members of the att.pointing class and therefore +have all the attributes associated with that class. +

+

To take a simple hypothetical example, suppose in transcribing a +spoken text, we encounter an utterance that we can understand either as +We had fun at the beach today. or as We had sun at +the beach today. We can represent the exclusive alternation of +these two possibilities by means of the exclude attribute as +follows. +

+ We had fun at the beach today. + We had sun at the beach today. +

+

If it is then determined that the speaker said fun, +not sun, the encoder could amend the text by deleting the +alternant containing sun and the exclude +attribute on the remaining alternant. Alternatively, the encoder could +preserve the fact that there was uncertainty in the original +transcription by retaining the alternants, and assigning the +we.fun value to the select attribute value on the div element that +encompasses the alternants, as in: +

+ We had fun at the beach + today. + We had sun at the beach today. +

+

The above alternation (including the select attribute) +could be recoded by assigning the exclude attributes to tags +that enclose just the words or even the characters that are mutually +exclusive, as in:See section for discussion of the +w and c tags that can be used in the following +examples instead of the seg type="word" and seg +type="character" tags. +

+ We had + fun + sun + at the beach today. +
+
+ We had + +f +s +un + at the beach today. +

+

Now suppose that the transcriber is uncertain whether the first word +in the utterance is We or Lee, but is +certain that if it is Lee, then the other uncertain word +is definitely fun and not sun. The three +utterances that are in mutual exclusion can be encoded as follows. +

+ + We had fun at the beach today. + We had sun at the beach today. + Lee had fun at the beach today. + +

+

The preceding example can also be encoded with exclude +attributes on the word segments We, Lee, +fun, and sun: + + We + Lee + had + fun + sun + at the beach today.

+

The value of the select attribute is defined as a list of +identifiers; hence it can also be used to +narrow down the range of alternants, as in: +

+ We had fun at the beach today. + We had sun at the beach today. + Lee had fun at the beach today. +
+This is interpreted to mean that either the first or the third +u element tag appears, and is thus equivalent to just the alternation +of those two tags: +
+ We had fun at the beach + today. + Lee had fun at the beach today. +

+

The exclude attribute can also be used in case there is +uncertainty about the tag that appears in a certain position. For +example, the occurrence of the word May in the s-unit +Let's go to May can be interpreted, in the absence of +other information, either as a person's name or as a date. The +uncertainty can be rendered as follows, using the exclude +attribute. +Let's go to +May + .

+

Note the use of the copyOf attribute discussed in +section ; this avoids having to repeat the content of the +element whose correct tagging is in doubt.

+

The copyOf and the exclude attributes also +provide for a simple way of indicating uncertainty about exactly where a +particular element occurs in a document.An alternative way of +representing this problem is discussed in chapter . + +For example suppose that a particular div2 +element appears either as the third and last of the div2 +elements within the first div1 element in the body of a +document, or as the first div2 of the second div1. +One solution would be to record the div2 in its entirety in the +first of these positions, and a virtual copy of it in the second, and +mark them as excluding each other as follows: + + + + + + + + + +In this case, the select attribute, if used, would appear on +the body element.

+

Mutual exclusion can also be expressed using a link; the +first example in this section can be recoded by removing the +exclude attributes from the u elements, and adding a +link element as follows:In this example, we have +placed the link next to the elements that represent the +alternants. It could also have been placed elsewhere in the document, +perhaps within a linkGrp. +

+ We had fun at the beach today. + We had sun at the beach today. + +

+

Now we define the specialized linking element alt, making +it a member of the class att.pointing, and +assigning it a mode attribute, which can have either of the +values excl (for exclusive) or incl (for +inclusive). Then the following equivalence holds: + = +

+

The preceding link element may therefore be recoded as the + following alt element.

+

Another attribute that is defined specifically for the alt +element is weights, which is to be used if one wishes to assign +probabilistic weights to the targets (alternants). Its +value is a list of numbers, corresponding to the targets, expressing the +probability that each target appears. If the alternants are mutually exclusive, then +the weights must sum to 1.0.

+

Suppose in the preceding example that it is equiprobable whether +fun or sun appears. Then +the alt element that represents the alternation may be stated +as follows:

+

The assignment of a weight of 1.0 to one target (and weights of 0 +to all the others) is equivalent to selecting that target. Thus the +following encoding is equivalent to the second example at the beginning +of this section. +We had fun at the beach today. +We had sun at the beach today. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +The sum of the weights for alt mode="incl" tags ranges from 0% to +(100 × k)%, where k is the number of targets. If the sum is 0%, then +the alternation is equivalent to exclusive alternation; if the sum is +(100 x k)%, then all of the alternants must appear, and the situation is +better encoded without an alt tag.

+ +

If it is desired, alt elements may be grouped together in +an altGrp element, and attribute values shared by the +individual alt elements may be identified on the +altGrp element. The targFunc attribute defaults to +the value first.alternant next.alternant.

+ +

To illustrate, consider again the example of a transcribed +utterance, in which it is uncertain whether the first word is +We or Lee, whether the +third word is fun or +sun, but that if the first word is +Lee, then the third word is +fun. Now suppose we have the following +additional information: if we occurs, then the +probability that fun occurs is 50% and that +sun occurs is 50%; if +fun occurs, then the probability that +we occurs is 40% and that +Lee occurs is 60%. This situation can be +encoded as follows. + + + We + Lee + had + fun + sun + at the beach today. + + + + + + +As noted above, when the mode attribute on an +alt has the value incl, then each weight states +the probability that the corresponding alternative occurs, given that at least one of the other alternatives occurs. +

+

From the information in this encoding, we can determine that the +probability is about 28.5% that the utterance is We had fun at the +beach today, 28.5% that it is We had sun at the beach +today, and 43% that it is Lee had fun at the beach +today.

+

Another very similar example is the following regarding the text of a +Broadway song. In three different versions of the song, the same line +reads Her skin is tender as a leather glove, Her skin is +tender as a baseball glove, and Her skin is tender as Dimaggio's +glove.The variant readings are found in the commercial sheet +music, the performance score, and the Broadway cast recording.

+

If we wish to express this textual variation using the alt +element, we can record our relative confidence in the readings +Dimaggio's (with probability 50%), a +leather (25%), and a baseball (25%).

+

Let us extend the example with a further (imaginary) variation, +supposing for the sake of the argument that the next line is variously +given as and she bats from right to left (with +probability 50%) or now ain't that too damn bad (with +probability 50%). Using the alt element, we can express the +conviction that if the first choice for the second line is correct, then +the probability that the first line contains Dimaggio's +is 90%, and each of the others 5%; whereas if the second choice for the +second line is correct, then the probability that the first line +contains Dimaggio's is 10%, and each of the others is +45%. This can be encoded, with an altGrp element containing a +combination of exclusive and inclusive alt elements, as follows. + +

+ Her skin is tender as + Dimaggio's + a leather + a baseball + glove, + and she bats from right to left. + now ain't that too damn bad. +
+ + + + + + + + + + + +

+ + + +
+ +
+Stand-off Markup +
+ Introduction + +

Most of the mechanisms defined in this chapter rely to a + greater or lesser extent on the fact that tags in a marked-up + document can both assert a property for a span of text which they + enclose, and assert the existence of an association between + themselves and some other span of text elsewhere. In stand-off + markup, there is a clear separation of these two behaviours: the + markup does not directly contain any part of the text, but + instead includes it by reference. One specific mechanism + recommended by these Guidelines for this purpose is the standard + XInclude mechanism defined by the W3C; another is to use pointers + as demonstrated elsewhere in this chapter.

+ +

There are many reasons for using stand-off markup: the source + text might be read-only so that additional markup cannot be added, + or a single text may need to be marked up + according to several hierarchically incompatible schemes, or a single + scheme may need to accommodate multiple hierarchical ambiguities, so that + a single markup tree is not the most faithful representation of the + source material.

+

This section describes a generic mechanism for expressing + all kinds of markup externally as stand-off tags, + for use whenever it is appropriate; and a place in the TEI + structure (standOff) to contain certain common kinds + of stand-off markup.

+ +

Throughout this section the following terms will be systematically used in + specific senses. + + + a document to which the stand-off markup refers (a source document can be either XML or + plain text); there may be more than one source document. + + markup that is already present in an XML source document + + markup that is either outside of the source document + and points in to it to the data it describes, or is pointed + at by the data that refers to it; or alternatively is in + another part of the source document and points elsewhere + within the document to the data it describes, or is pointed + at by data elsewhere that refers to it. + + a document that contains stand-off markup that points to a different, source document + + the action of creating a new XML document with external markup and data integrated with the + source document data, and possibly some source document markup as well + + a process applied to markup from a pre-existing XML + document, which splits it into two documents, an XML + (external) document containing some of the markup of the + original document, and another (source) XML document + containing whatever text content and markup has not been + extracted into the stand-off document; if all markup has been + externalized from a document, the new source may be a plain + text document + +

+

The three major requirements satisfied by this scheme for stand-off markup are: + + any valid TEI markup can be either internal or + external, + external markup can be internalized by + applying it to the document content by either + substituting the existing markup or adding to it, + to form a valid TEI document, and + the external markup itself specifies whether + an internalized document is to be created by substituting + the existing internal markup or by adding to + it. +

+ + + +
+ +
+ Overview of XInclude +

Stand-off markup which relies on the inclusion of virtual + content is adequately supported by the W3C XInclude recommendation, + which is also recommended for use by these Guidelines.The version on which this text is based is the W3C + Recommendation dated 20 December + 2004.. XInclude defines a namespace + (http://www.w3.org/2001/XInclude), which in + these Guidelines will be associated with the prefix + xi:, and exactly two elements, + xi:include and xi:fallback. XInclude relies on + the XPointer + framework discussed elsewhere in this chapter to point to the + actual fragments of text to be internalized. Although XInclude only + requires support for the element() + scheme of XPointer, these Guidelines permit the use of any of the + pointing schemes discussed in section .

+ +

XInclude is a W3C recommendation which specifies a syntax for the + inclusion within an XML document of data fragments placed in + different resources. Included resources can be either plain + text or XML. XInclude instructions within an XML document + are meant to be replaced by a resource targetted by a + URI, possibly augmented by an XPointer that identifies the + exact subresource to be included.

+ +

The xi:include element uses the href attribute to specify the location of + the resource to be included; its value is an URI containing, + if necessary, an XPointer. Additionally, it uses the parse attribute (whose only valid values + are text and xml) to specify whether + the included content is plain text or an XML fragment, and + the encoding attribute to provide a hint, when + the included fragment is text, of the character encoding of + the fragment. An optional xi:fallback element is + also permitted within an xi:include; it specifies + alternative content to be used when the external resource + cannot be fetched for some reason. Its use is not however + recommended for stand-off markup.

+ +
+
+ + Stand-off Markup in TEI + +

The operations of internalizing and externalizing markup are + very useful and practically important. XInclude processing as + defined by the W3C is internalization of one or more + source documents' content into a stand-off document. TEI use of + XInclude for stand-off markup enables use of XInclude-conformant + software to perform this useful operation. However, + internalization is not clearly defined for all stand-off files, + because the structure of the internal and external markup trees + may overlap. In particular, when an external markup document + selects a range that overlaps partial elements in the source + document, it is not clear how the semantics of internalization + (inclusion) should work, since partial elements are not XML + objects.This corresponds to the observation + that overlapping XML tags reflecting a textual version of such an + inclusion would not even be well-formed XML. This kind of overlap + in textual phenomena of interest is in fact the major reason that + stand-off markup is needed. XInclude defines a semantics + for this case that involves only complete elements.

+ +

When a range selection partially overlaps a number of elements in a +source document, XInclude specifies that the partially overlapping +elements should be included as well as all completely overlapping +elements and characters (partially overlapping characters are not +possible). The effect of this is that elements that straddle the start +or end of a selected range will be included as wrappers for those of +their children that are completely or partially selected by the +range. For example, given the following source document: + + + +

home, home on Brokeback Mountain.

+

That was the song that I sang

+ + + and the following external document: + +
+
+ ]]> + the resulting document after XInclude processing of this external document + would be: + +
+

home, home on Brokeback Mountain.

+

That was the song that I sang

+
+ ]]> + The result of the inclusion is two paragraph elements, while + the original range designated in the source document + overlapped two paragraph fragments. + + +The semantics of XInclude require the creation of well-formed XML results even though + the pointing mechanisms it uses do not necessarily + respect the hierarchical structure of XML documents, as in + this case. While + this is a good way to ensure that internalization is always + possible, it has implications for the use of XInclude as a + notation for the description of overlapping + markup structures. +

+ +

When overlapping hierarchies need to be represented + for a single document, each hierarchy must be represented by a + separate set of XInclude tags pointing to a common source + document. This sort of structure corresponds to common + practice in work with linguistic text corpora. In such corpora, each + potentially overlapping hierarchy of elements for the text is + represented as a separate stream of stand-off + markup. Generally the source text contains markup for + the smallest significant units of analysis in the corpus, + such as words or morphemes, this information and its markup + representing a layer of common information that is shared by + all the various hierarchies. As a way of organizing the + representation of complex data, this technique generally + allows a large number of xml:id attributes to be + attached to the shared elements, providing robust anchors for + links and facilitating adjustments to the source document + without breaking external documents that reference it. +

+ + +

Any tag can be externalized by + + removing its content and replacing it with an + xi:include element that contains an XPointer + pointing to the desired content.

+

For instance the following portion of a TEI document: + + +1755 +To make a prairie it takes a clover and one bee, +One clover, and a bee, +And revery. +The revery alone will do, +If bees are few. + + + can be externalized by placing the actual text in a separate + document, and providing exactly the same markup with the + xi:include elements: + + + To make a prairie it takes a clover and one bee,\n +One clover, and a bee,\n +And revery.\n +The revery alone will do,\n +If bees are few.\n +]]> + + + + + 1755 + + + + + + + + + + + + + + + + +]]>

+ + + +

Please note that this specification requires that the + XInclude namespace declaration is present in all cases. The + xi:fallback element contains text or XML fragments to + be placed in the document if the inclusion fails for any + reason (for instance due to inaccessibility of an external + resource). The xi:fallback element is optional; if it + is not present an XInclude processor must signal a fatal error + when a resource is not found. This is the preferred behaviour + for use with stand-off markup. These Guidelines recommend + against the use of xi:fallback for stand-off + markup.

+
+
+ Well-formedness and Validity of Stand-off Markup +

The whole source fragment + identified by an XInclude element, as well as any markup + therein contained is inserted in the position specified, and + an XInclude processor is required to ensure that the resulting + internalized document is + well-formed. This has obvious implications when the external + document contains XML markup. A plain text source document + will always create a well-formed + internalized document.

+

While a TEI customization may permit + xi:include elements in various places in a TEI document + instance, in general these Guidelines suggest that validity be + verified after the resolution of all the xi:include + elements.

+
+
+ Including Text or XML Fragments +

When the source text is plain text the overall form of the + XPointer pointing to it is of minimal importance. The form + of the XPointer matters considerably, on the other hand, + when the source document is XML.

+

In this case, it is rather important to distinguish whether + we intend to substitute the source XML with the new one, or + just to add new markup to it. The XPointers used in the + references can express both cases.

+

A simple way is to make sure to select only textual data in + the XPointer. For instance, given the following + document: + + + + + +

To make a prairie it takes a clover + and one bee,
+
One clover, and + a bee,
+
And revery.
+
The revery alone will do,
+
If bees are few.
+ + + +the expression +range(element(/1/2/1.0),element(/1/2/11.1)) will select +the whole poem, text content and div elements +and hypertext links (NB: in XPointer whitespace-only text +nodes count).

+

On the contrary, the expressions +xpointer(//text()/range-to(.)) and +xpointer(string-range(//text(),"To")/range-to(//text(),"few.") +will only select the text of the poem, with no markup inside.

+

Thus, the following could be a valid stand-off document for + the Source.xhtml document: + + + + + 1755 + + + + + + + + + + + + + + + + +]]>

+
+
+ +
+ + The standOff Container +

The standOff element is intended to hold content that does not fit well in the + text (e.g. because it is not transcribed from the source), nor in the + teiHeader (e.g. because it is not metadata about the source or transcription). + Examples include contextual information about named entities (typically encoded using + listBibl, listOrg, listNym, listPerson, or + listPlace), annotations indicating the morphosyntactic features of a text, and + annotations commenting on or associating parts of a text with additional information. + + +

+ +

As a member of model.resource, standOff may occur as a + child of TEI (or teiCorpus). If the metadata that describes the + standOff is largely the same as the metadata that describes the associated resource + (e.g., the transcribed text in text), then the standOff and the encoded + associated resource may appear as children of the same TEI element. The example below + has a transcription with placename elements in the text linked to a list of place elements in the + standOff section. + + + + + + + + + + Cilicia + https://pleiades.stoa.org/places/658440 + + + Creta + Crete + https://pleiades.stoa.org/places/589748 + + + + Rhodus + Rhodes + https://pleiades.stoa.org/places/590031 + + + Syria + https://pleiades.stoa.org/places/1306 + + + + + + +

+
+ Bellum Alexandrinum +

+ Bello Alexandrino conflato Caesar + + Rhodo + Ordo + atque ex Syria + Ciliciaque omnem classem arcessit; + Creta + certa + sagittarios, equites ab rege Nabataeorum + Malcho euocat; tormenta undique conquiri et + frumentum mitti, auxilia adduci iubet. + +

+ +
+ +
+ + + + +

+
+
+ Annotations +

The annotation element's structure is based on the Web + Annotation Data Model (WADM). A Web Annotation may have one or more targets, which are + URIs, and zero or more bodies, which may be either URIs or embedded text. A Web Annotation may + also contain metadata about the annotation, such as the creator, creation and modification + dates, and license information. The annotation element implements a subset of WADM, + using TEI elements and attributes to encode the same information, with a focus on annotating + TEI documents. Targets are represented using the target attribute on + annotation. URI bodies are represented using ref or ptr and + embedded text bodies using note. Lifecycle and license information may be given using + respStmt, revisionDesc, and licence. + + +

+ +

TEI annotations are, in general, intended to capture the output of processes that annotate + TEI texts without altering the text and markup in the text. They allow this kind of + output to be represented directly in TEI, and thus to be processed using the same toolchains + as the texts they annotate. A named entity recognition workflow might use annotation, + for example to associate names in the text with person elements instead of attempting + to rewrite the TEI text using inline persName. Projects may wish to use this + mechanism to layer information onto a TEI text in case where using inline elements might + result in complicated markup.

+ +

The example below illustrates how stand-off annotations can be used to connect words in a + text with place elements in a list. The words Gallia and Galliae in the + edition are connected by an annotation in the standOff section which points to them + using string-range() pointers and references the definition of the place (also in + the standOff section). If the set of annotations were created in a process separate + from the creation of the transcription and then imported into the transcription document, then + wrapping them in a TEI element with its own teiHeader providing metadata for + the annotations might be advisable. + + + + + De Bello Gallico + + + + + + +

+
+

+ Gallia est omnis divisa in partes tres, quarum unam + incolunt Belgae, aliam Aquitani, tertiam qui ipsorum lingua Celtae, nostra + Galli appellantur. + + Belgae ab extremis Galliae finibus oriuntur, + pertinent ad inferiorem partem fluminis Rheni, spectant in septentrionem et + orientem solem. + Aquitania a Garumna flumine ad Pyrenaeos montes et + eam partem Oceani quae est ad Hispaniam pertinet; spectat inter occasum solis + et septentriones.] + +

+ +
+ +
+ + + + + + Gallia + Gaul + https://pleiades.stoa.org/places/993 + + + + + + + + + + + + + creator + Fred Editor + + + + + + + + + + + + + + + + + +

+ + + + +
+ +
+Connecting Analytic and Textual Markup +

In chapters and and elsewhere, +provision is made for analytic and interpretive markup to be represented +outside of textual markup, either in the same document or in a different +document. The elements in these separate domains can be connected, +either with the pointing attributes ana (for +analysis) and inst (for +instance), or by means of link and +linkGrp elements. Numerous examples are given in these +chapters.

+

Another more specific form of annotation is available through the TEI ruby element and its + children, described in detail in .

+ +
+
+ Module for Linking, Segmentation, and Alignment +

The module described in this chapter makes available the + following components: + + Linking, Segmentation, and Alignment + Linking, segmentation, and alignment + Liens, segmentation et alignement + 連結、分割與隊列 + Collegamento, segmentazione e allineamento + Ligação, segmentação e alinhamento + リンクモジュール + + The selection and combination of modules to form a TEI schema is + described in . + + + + + + + + +

+
+
diff --git a/P5/Source/Guidelines/fr/SG-GentleIntroduction.xml b/P5/Source/Guidelines/fr/SG-GentleIntroduction.xml deleted file mode 120000 index 7d37fad42f..0000000000 --- a/P5/Source/Guidelines/fr/SG-GentleIntroduction.xml +++ /dev/null @@ -1 +0,0 @@ -../en/./SG-GentleIntroduction.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/SG-GentleIntroduction.xml b/P5/Source/Guidelines/fr/SG-GentleIntroduction.xml new file mode 100644 index 0000000000..a8b298c76e --- /dev/null +++ b/P5/Source/Guidelines/fr/SG-GentleIntroduction.xml @@ -0,0 +1,1473 @@ + + + + +
+ +A Gentle Introduction to XML + +

The encoding scheme defined by these Guidelines is formulated as an +application of the Extensible Markup Language (XML) (). XML is widely used for +the definition of device-independent, system-independent methods of +storing and processing texts in electronic form. It is now also the +interchange and communication format used by many applications on the +World Wide Web. In the present chapter we informally introduce some of +its basic concepts and attempt to explain to the reader encountering +them for the first time how and why they are used in the TEI +scheme. More detailed technical accounts of TEI practice in this +respect are provided in chapters , , and of these Guidelines.

+ +

Strictly speaking, XML is a metalanguage, that is, a +language used to describe other languages, in this case, +markup languages. Historically, the word +markup has been used to describe annotation or other +marks within a text intended to instruct a compositor or typist how a +particular passage should be printed or laid out. Examples include +wavy underlining to indicate boldface, special symbols for passages to +be omitted or printed in a particular font, and so forth. As the +formatting and printing of texts was automated, the term was extended +to cover all sorts of special codes inserted into electronic texts to +govern formatting, printing, or other processing.

+

Generalizing from that sense, we define markup, or +(synonymously) encoding, as any means of making explicit +an interpretation of a text. Of course, all printed texts are +implicitly encoded (or marked up) in this sense: punctuation marks, +capitalization, disposition of letters around the page, even +the spaces between words all might be regarded as a kind of markup, the +purpose of which is to help the human reader determine where one word +ends and another begins, or how to identify gross structural features +such as headings or simple syntactic units such as dependent clauses +or sentences. Encoding a text for computer processing is, in +principle, like transcribing a manuscript from scriptio continuaIn the +continuous writing characteristic of manuscripts from the early +classical period, words are written continuously with no intervening +spaces or punctuation.; it is a process of making explicit what is +conjectural or implicit, a process of directing the user as to how the +content of the text should be (or has been) interpreted.

+ +

By markup language we mean a set of markup conventions +used together for encoding texts. A markup language must specify how +markup is to be distinguished from text, what markup is allowed, what +markup is required, and what the markup means. XML provides the means +for doing the first three; documentation such as these Guidelines is +required for the last.

+ +

The present chapter attempts to give an informal introduction to +those parts of XML of which a proper understanding is necessary to +make best use of these Guidelines. The interested reader should also +consult one or more of the many excellent introductory textbooks and +web sites now available on the subject.New +textbooks and websites about XML appear at regular intervals and to +select any one of them would be invidious. +some recommended online courses include and .

+ +
What's Special about XML? + +

XML has three highly distinctive advantages: + +it places emphasis on descriptive rather than +procedural markup; +it distinguishes the concepts of syntactic correctness and of +validity with respect to a document type definition; +it is independent of any one hardware or software +system. These three aspects are discussed briefly below, +and then in more depth in the remainder of this chapter.

+ +

XML is frequently compared with HTML, the language in which web +pages have generally been written, which +shares some of the above characteristics. Compared with HTML, however, +XML has some other important features: + +XML is extensible: it does not consist of a fixed set of +tags; +XML documents must be well-formed according to a defined +syntax; +an XML document can be formally validated against a set of schema rules for consistent application; +XML is more interested in the meaning of data than in its +presentation.

+ +
Descriptive Markup + +

In a descriptive markup system, the markup codes used do little +more than categorize parts of a document. Markup codes such as +para or \end{list} simply identify a portion +of a document and assert of it that the following item is a +paragraph, or this is the end of the most recently begun +list, etc. By contrast, a procedural markup system defines what +processing is to be carried out at particular points in a document: +call procedure PARA with parameters 42, b, and x here or move +the left margin 2 quads left, move the right margin 2 quads right, +skip down one line, and go to the new left margin, etc. In XML, +the instructions needed to process a document for some particular +purpose (for example, to format it) are sharply distinguished from the +markup used to describe it.

+ +

Usually, the markup or other information needed to process a +document will be maintained separately from the document itself, +typically in a distinct document called a stylesheet, +though it may do much more than simply define the rendition or visual +appearance of a document.We do not here discuss in +any detail the ways that a stylesheet can be used or defined, nor do +we discuss the popular W3C Stylesheet Languages XSLT and CSS. See +further , , and +.

+ +

When descriptive markup is used, the same document can +readily be processed in many different ways, using only those parts of +it which are considered relevant. For example, a content analysis +program might disregard entirely the footnotes embedded in an +annotated text, while a formatting program might extract and collect +them all together for printing at the end of each chapter. Different +kinds of processing can be carried out with the same part of a file. +For example, one program might extract names of persons and places +from a document to create an index or database, while another, +operating on the same text, but using a different stylesheet, might +print names of persons and places in a distinctive typeface.

+
+ +
Types of Document + +

A second key aspect of XML is its notion of a document +type: documents are regarded as having types, just as other +objects processed by computers do. The type of a document is formally +defined by its constituent parts and their structure. The definition +of a report, for example, might be that it +consisted of a title and possibly an +author, followed by an +abstract and a sequence of one or more +paragraphs. Anything lacking a title, according +to this formal definition, would not formally be a report, and neither +would a sequence of paragraphs followed by an abstract, whatever other +report-like characteristics these might have for the human reader.

+ +

If documents are of known types, a special-purpose program (called +a parser), once provided with an unambiguous definition +of a document type, can check that any document claiming to be of +that type does in fact conform to the specification. A parser +can check that all elements specified for a particular +document type are present and no others, that they are combined in appropriate ways, +correctly ordered, and so forth. More significantly, different +documents of the same type can be processed in a uniform way. Programs +can be written which take advantage of the knowledge encapsulated in +the document type information, and which can thus behave in a +more intelligent fashion.

+
+ +
Data Independence + +

A basic design goal of XML is to ensure that documents encoded +according to its provisions can move from one hardware and software +environment to another without loss of information. The two features +discussed so far both address this requirement at an abstract level; +the third feature addresses it at the level of the strings of data +characters that make up a document. All XML documents, +whatever languages or writing systems they employ, use the same +underlying character encoding (that is, the same method of +representing as binary data those graphic forms making up a particular +writing system).See Extensible Markup +Language (XML) 1.0, available from , Section 2.2 +Characters. This encoding is defined by an international +standard,ISO/IEC 10646-1993 Information +Technology — Universal Multiple-Octet Coded Character Set +(UCS) which is implemented by a universal character set +maintained by an industry group called the Unicode Consortium, and +known as Unicode.See Unicode +provides a standardized way of representing any of the many thousands of +discrete symbols making up the world's writing systems, past and +present.

+ + +

Most modern computing systems now support Unicode directly; for +those which do not, XML provides a mechanism for the indirect +representation of single characters by means of +their character number, known as character references; see further +.

+
+
+
Textual Structures +

A text is not an undifferentiated sequence of words, much less of +bytes. For different purposes, it may be divided into many different +units, of different types or sizes. A prose text such as this one +might be divided into sections, chapters, paragraphs, and sentences. A +verse text might be divided into cantos, stanzas, and lines. Once +printed, sequences of prose and verse might be divided into volumes, +gatherings, and pages.

+ +

Structural units of this kind are most often used to identify +specific locations or refer to points within a text (the third +sentence of the second paragraph in chapter ten; canto 10, line +1234; page 412, etc.) but they may also be used to +subdivide a text into meaningful fragments for analytic purposes +(is the average sentence length of section 2 different from that of +section 5? how many paragraphs separate each occurrence of the +word nature? how many pages?). +Other structural units are more clearly analytic, in that they +characterize a section of a text. A dramatic text might regard each +speech by a different character as a unit of one kind, and stage +directions or pieces of action as units of another kind. Such an +analysis is less useful for locating parts of the text (the 93rd +speech by Horatio in Act 2) than for facilitating comparisons +between the words used by one character and those of another, or those +used by the same character at different points of the play.

+ +

In a prose text one might similarly wish to regard as units of +different types passages in direct or indirect speech, passages +employing different stylistic registers (narrative, polemic, +commentary, argument, etc.), passages of different authorship and so +forth. And for certain types of analysis (most notably textual +criticism) the physical appearance of one particular printed or +manuscript source may be of importance: paradoxically, one may wish to +use descriptive markup to describe presentational features such as +typeface, line breaks, use of whitespace and so forth.

+ +

These textual structures overlap with one another in complex and +unpredictable ways. Particularly when dealing with texts as +instantiated by paper technology, the reader needs to be aware of both +the physical organization of the book and the logical structure of the +work it contains. Many great works (Sterne's Tristram +Shandy for example) cannot be fully appreciated without an +awareness of the interplay between narrative units (such as chapters +or paragraphs) and presentational ones (such as page divisions). For +many types of research, the interplay among different levels +of analysis is crucial: the extent to which syntactic structure +and narrative structure mesh, or fail to mesh, for example, or the +extent to which phonological structures reflect morphology.

+ +
XML Structures + +

This section describes the simple and consistent mechanism for the +markup or identification of textual structure provided by XML. It +also describes the methods XML provides for the expression of rules +defining how units of textual structure can meaningfully be combined +in a text.

+ +
Elements + +

The technical term used in XML for a textual unit, viewed as a +structural component, is element. Different types of +elements are given different names, but XML provides no way of +expressing the meaning of a particular type of element, other than its +relationship to other element types. That is, all one can say about +an element called (say) blort is that instances of +it may (or may not) occur within elements of type farble, and +that it may (or may not) be decomposed into elements of type +blortette. It should be stressed that XML is entirely +unconcerned with the semantics of textual elements, +because these are considered to be application dependent. It is up to +the creators of XML vocabularies (such as these Guidelines) to choose +intelligible element names and to define their +intended use in text markup. That is the chief purpose of documents +such as the TEI Guidelines. From the need to choose element names +indicative of function comes the technical term for the name of an +element type, which is generic identifier, or GI.

+

Within a marked-up text (a document instance), each +element must be explicitly marked or tagged in some way. This is done +by inserting a tag at the beginning of the element (a +start-tag) and another at its end (an +end-tag). The start- and end-tag pair are used to bracket +off element occurrences within the running text, in rather the +same way as different types of parentheses or quotation marks are used +in conventional punctuation. For example, a quotation element in a +text might be tagged as follows: +... Rosalind's +remarks This is the silliest stuff that ere I heard +of! clearly indicate ... + +As this example shows, a start-tag takes the form quote, +where the opening angle bracket indicates the start of the start-tag, +quote is the generic identifier of the element that is being +delimited, and the closing angle bracket indicates the end of the start-tag. +An end-tag takes an identical form, except that the opening angle +bracket is followed by a solidus (slash) character, so that the +corresponding end-tag is /quote.Because +the opening angle bracket has this special function in an XML +document, special steps must be taken to use that character for other +purposes (for example, as the mathematical less-than operator); see +further section . The material between +the start-tag and the end-tag (the string of words This is the +silliest stuff that ere I heard of in the example above) is known +as the content of the element. Sometimes there may be +nothing between the start and the end-tag; in this case the two may +optionally be merged together into a single composite tag with the +solidus at the end, like this: quote/.

+ +
Content Models: an Example + +

An element may be empty, that is, it may have no +content at all, or it may contain just a sequence of characters with +no other elements. Often, however, elements of one type will +be embedded (contained entirely) within elements of a +different type.

+ +

To illustrate this, we will consider a very simple structural +model. Let us assume that we wish to identify within an anthology +only poems, their headings, and the stanzas and lines of which they are +composed. In XML terms, our document type is the +anthology, and it consists of a series of +poems. Each poem has embedded within it one element, a +heading, and several occurrences of another, a +stanza, each stanza having embedded within it a number of +line elements. Fully marked up, a text conforming to +this model might appear as follows: + + + + The SICK ROSE + + O Rose thou art sick. + The invisible worm, + That flies in the night + In the howling storm: + + + Has found out thy bed + Of crimson joy: + And his dark secret love + Does thy life destroy. + + + +

+

It should be stressed that this example does not use +the names proposed for corresponding elements elsewhere +in these Guidelines: the above is thus not a valid TEI +document.The element names here have been chosen for +clarity of exposition; there is, however, a TEI element corresponding to +each. It will, however, serve as an introduction to the basic notions of XML. +Whitespace and line breaks have been added to the example for the +sake of visual clarity only; they have no particular significance in the +XML encoding itself. Also, the line +]]> +is an XML comment and is not treated as part of the text.

+

As it stands, the above example is what is known as a +well-formed XML document because it obeys the following simple rules: + +there is a single element +enclosing the whole document: this is known as the root +element (anthology in our case); +each element is completely contained by the root element, +or by an element that is so contained; elements do not partially +overlap one another; +a tag explicitly marks the start and end of each element. + +

+

A well-formed XML document can be processed in a number of useful +ways. A simple indexing program could extract only the relevant text +elements in order to make a list of headings, first lines, or words +used in the poem text; a simple formatting program could insert blank +lines between stanzas, perhaps indenting the first line of each, or +inserting a stanza number. Different parts of each poem could be +typeset in different ways. A more ambitious analytic program could +relate the use of punctuation marks to stanzaic and metrical +divisions.Note that this simple example has not +addressed the problem of marking elements such as sentences +explicitly; the implications of this are discussed in section . Scholars wishing to see the implications of +changing the stanza or line divisions chosen by the editor of this +poem can do so simply by altering the position of the tags. And of +course, the text as presented above can be transported from one +computer to another and processed by any program (or person) capable +of making sense of the tags embedded within it with no need for the +sort of transformations and translations needed for files which have +been saved in one or other of the proprietary formats preferred by +most word-processing programs.

+ +

As we noted above, one of the attractions of XML is that it enables +us to apply our own names for the elements rather than requiring us +always to use names predefined by other agencies. Clearly, however, if +we wish to exchange our poems with others, or to include poems others +have marked up in our anthology, we will need to know a bit more about +the names used for the tags. The means that XML provides for this is +called a namespace. In our simple example, the tags just +contain a simple name. As we shall see, it is also possible to use +tags that include a qualified name, that is, a name with +an optional prefix identifying the set of names to which it +belongs. For example, we have defined an element line for the purpose of marking lines of +verse. Another person might, however, define an element called line for the purpose of marking typographic +lines, or drawn lines. Because of these different meanings, if we wish +to share data it will be necessary to distinguish the two line +components in our marked-up texts. This is achieved by including a +namespace prefix within the markup, for example like +this: This is one of my lines + +This is one of your lines]]> + +This feature is particularly important if we have different +definitions of what a line is, of course, but +there are many occasions when it is useful to distinguish groups of +tags belonging to different markup vocabularies; +we discuss this further below (). One +particularly useful namespace prefix is predefined for XML: it is +xml and we will see examples of its use below.

+ +

Namespaces allow us to represent the fact that a name belongs to a +group of names, but don't allow us to do much more by way of checking +the integrity or accuracy of our tagging. Simple well-formedness alone +is not enough for the full range of what might be useful in marking up +a document. It might well be useful if, in the process of preparing +our digital anthology, a computer system could check some basic rules +about how stanzas, lines, and headings can sensibly co-occur in a +document. It would be even more useful if the system could check that +stanzas are always tagged stanza and not occasionally +canto or Stanza. An XML document in which such +rules have been checked is technically known as a valid +document, and the ability to perform such validation is one of the key +advantages of using XML. To carry this out, some way of formally +stating the criteria for successful validation is necessary: in XML +this formal statement is provided by an additional document known +as a schema.The older terms +Document Type Declaration and Document Type +Definition, both abbreviated as DTD, may also be +encountered. Throughout these Guidelines we use the term +schema for any kind of formal document grammar. +

+
+
+ +
Validating a Document's Structure + +

The design of a schema may be as lax or as restrictive as the +occasion warrants. A balance must be struck between the convenience +of following simple rules and the complexity of handling real +texts. This is particularly the case when the rules being defined +relate to texts that already exist: the designer may have only the +haziest of notions as to an ancient text's original purpose or meaning +and hence find it very difficult to specify consistent rules about its +structure. On the other hand, where a new text is being prepared to +an exact specification, for entry into a textual database +of some kind for example, the more precisely stated the rules, the better they can +be enforced. Even in marking up an existing text, a restrictive set of schema rules may be beneficial, especially when applied to test a particular view or hypothesis about the text. A schema +designed for use by a small project or team is likely to take a +different position on such issues than one intended for use by a large +and possibly fragmented community. It is +important to remember that every schema results +from an interpretation of a text. There is no single schema +encompassing the absolute truth about any text, although it may +be convenient to privilege some schemas above others for particular +types of analysis.

+ +

XML is widely used in environments where uniformity of document +structure is a major desideratum. In the production of technical +documentation, for example, it is of major importance that sections +and subsections should be properly nested, that cross-references +should be properly resolved and so forth. In such situations, +documents are seen as raw material to match against predefined sets +of rules. As discussed above, however, the use of simple rules can +also greatly simplify the task of tagging accurately elements of less +rigidly constrained texts. By making these schema rules explicit, scholars reduce their own burdens with consistently marking up and verifying the +electronic text. By defining and sharing their schema rules, scholars openly express a project-specific interpretation of the structure and significant particularities of the +text being encoded.

+

Schema validation for XML is usually written in the RELAX NG language () originally + developed within the OASIS Technical Committee and now an + ISO standardISO/IEC FDIS 19757-2 Document + Schema Definition Language (DSDL) — Part 2: Regular-grammar-based + validation — RELAX NG, though other older methods include the Document Type Definition + (DTD) language which XML inherited from SGML and the XML Schema language () defined by the W3C.Schema validation languages co-evolved with early markup language specifications, as summarized in Rick Jelliffe's Family Tree of Schema Languages for Markup Languages. In this chapter, and throughout these + Guidelines, we give examples using the compact + syntax of RELAX NG for ease of reading. The specifications for the TEI Guidelines are first expressed in the TEI language itself and a RELAX NG schema is generated from them for processing convenience. Details about schema customization using the TEI ODD language are addressed in , and . +

+ +
An Example Schema +

For the purposes of illustrating how a schema works to restrict how XML may be written, we use the RELAX NG compact syntax in what follows. The following schema can be used to validate our example poem: + +

+ +

Note that this is not the only way in which a RELAX NG schema might +be written; we have adopted this idiom, however, because it +matches that used throughout the rest of these Guidelines.

+ +

A RELAX NG schema expresses rules about the possible structure of a +document in terms of patterns; that is, it defines a +number of named patterns, each of which acts as a kind of template +against which an input document can be matched. The meaning of a +pattern is expressed in a schema either by reference to other patterns, or to +a small number of fundamental built-in concepts, as we shall see. In +the example above, the word to the left of the equals sign is the +pattern's name, and the material following it declares a meaning for +the pattern. Patterns may also be of particular types; the ones that +interest us here are called element patterns and +attribute patterns. In this example we see definitions +for five element patterns. Note that we have used similar names for +the pattern and the element which the pattern describes: so, for +example, the line anthology_p = element anthology {poem_p+} defines an element pattern called anthology_p, +the value of which defines an element called +anthology. These naming conventions are +arbitrary; we could use the same name for the pattern as +for the element, but we want to make clear that the two are syntactically quite distinct. The +name, or generic identifier, of the element follows the +word element, and the content model for the +element is given within the curly braces following that. Each of +these parts is discussed further below. +

+

The last line of the schema above tells a RELAX NG validator which +element (or elements) in a document can be used as the root element: +in our case only anthology. This enables +the validator to detect whether a particular document is well-formed +but incomplete; it also simplifies the processing task by providing an +entry point.

+
Generic Identifier +

Following the word element each pattern declaration gives +the generic identifier (often abbreviated to GI) of the element being +defined, for example poem, +heading, etc. A GI may contain letters, +digits, hyphens, underscore characters, or full stops, but must begin +with a letter and may not contain a space.In XML, a single colon may also +appear in a GI, where it has a special significance related to the use +of namespaces, as further discussed in section . The characters defined by Unicode as +combining characters and as extenders are +also permitted, as are logograms such as Chinese characters. Uppercase and lowercase letters are quite +distinct: an element with the GI foo is +not the same as an element with the GI Foo; the root element of a TEI-conformant +document is TEI, not tei.

+
Content Model +

The second part of each declaration, enclosed in curly braces, is +called the content model of the element being defined, because it +specifies what may legitimately be contained within it. In RELAX NG, +the content model is defined in terms of other patterns, either by +embedding them, or (as in our examples above) by naming or referring +to them. The RELAX NG compact syntax also uses a small number of +reserved words to identify other possible contents for an element, of which by +far the most commonly encountered is text, as in this +example: it means that the element being defined may contain any valid +character data, but no elements. If an XML document is thought of as a structure +like a family tree, with a single ancestor at the top (in our case, +this would be anthology), then almost always, following the +branches of the tree downwards (for example, from anthology +to poem to stanza to line and +heading) will lead eventually to text. In our example, +heading and line are so defined, since their content +models say text only and name no embedded elements.

+ +
Occurrence Indicators + +

The declaration for stanza in the example above states +that a stanza consists of one or more lines. It uses an +occurrence indicator (the plus sign) to indicate how many +times something matching the pattern line_p may be +repeated. There are three occurrence indicators: the plus sign, the +question mark, and the asterisk or star. The plus sign means that +the pattern can match one or more times; the +question mark means that it may match at most once but is not +mandatory; the star means that the pattern concerned is not +mandatory, but may match more than once. Thus, if the content model for +stanza were {line_p*}, stanzas with no lines +would be possible as well as those with more than one line. If it +were {line_p?}, again empty stanzas would be +permitted, but no stanza could have more than a single line. The +declaration for poem in the example above thus states that a +poem cannot have more than one heading, but may have none, +and that it must have at least one stanza and may have +several.

+ +
Connectors +

The content model {heading_p?, stanza_p+} contains more than +one component, and thus needs additionally to specify the order in +which these patterns (heading_p and stanza_p) may appear. +This ordering is determined by the connector (the comma) +used between its components. The +comma connector indicates that the patterns concerned must appear in +the sequence given. Another commonly encountered connector is the +vertical bar, representing alternation. If the comma in this example were replaced by a vertical +bar, then a poem would consist of either a heading or just +stanzas—but not both!

+
Groups +

In our example so far, the components of each content model have +been either single patterns or text. We often need to define content models in more complicated ways, in which the components +are lists of patterns, combined by connectors. Such lists may also be +modified by occurrence indicators and themselves combined by +connectors. To demonstrate these facilities, let us expand our +example so that it may include non-stanzaic types of verse. For the sake of +demonstration, we will categorize poems as one of the following: +stanzaic, couplets, or blank +(or stichic). A blank-verse poem consists simply of +lines (we ignore the possibility of verse paragraphs for the +moment), so no additional elements need be defined +for it. We could define a couplet as a firstLine followed by a + secondLine, which distinction might be useful in a study of rhyme schemes.This example is probably not a good practice for most XML projects, since XPath provides ways of distinguishing elements in an XML structure by their position, or the order in which they appear in relation to one another, without the need to give them distinct names. + + + +

+

The patterns firstLine_p and secondLine_p define elements +firstLine and secondLine; these will have exactly +the same content model as the existing line element. We will +therefore add the following two lines to our example schema: +Next, we can change the declaration for the poem element to +include all three possibilities: That is, a poem +consists of an optional heading, followed by one or several stanzas, +or one or several couplets, or one or several lines. Note the +difference between this declaration and the following: The second version, +by applying the occurrence indicator to the group rather than to each +element within it, would allow a single poem to contain a mixture +of stanzas, couplets, and lines.

+

A group of this kind can contain text as well as named +elements: this combination, known as mixed content, +allows for elements in which the sub-components appear with +intervening stretches of character data. For example, if we wished to +mark place names wherever they appear inside our verse lines, then, +assuming we have also added a pattern for the +name element, we could change the definition for +line to +

+ +

Some XML schema languages place no constraints on the way that +mixed content models may be defined, but in the XML DTD language, when +text appears with other elements in a content model, it +must always appear as the first option in an alternation; it may +appear once only, and in the outermost model group; and if the group +containing it is repeated, the star operator must be used. Although +these constraints are not strictly necessary in RELAX NG schemas, all TEI content models currently obey them.

+ +

Quite complex models can be built in this way, to match +the structural complexity of many types of text. For example, consider the case of stanzaic verse in which a refrain or +chorus appears. Like a stanza, a refrain consists of repetitions of +the line element. A refrain can appear at the start of a poem only, +or as an optional addition following each stanza. This could be +expressed by a pattern such as the following: + + +That is, a poem consists of an optional heading, followed by either a +sequence of lines or an unnamed group, which starts with an optional +refrain and is followed by one or more occurrences of another group, each +member of which is composed of a stanza followed by an optional +refrain. A sequence such as refrain - stanza - stanza - +refrain follows this pattern, as does the sequence +stanza - refrain - stanza - refrain. The +sequence refrain - refrain - stanza - stanza +does not, however, and neither does the sequence stanza - +refrain - refrain - stanza. Among other conditions made +explicit by this content model are the requirements that at least one +stanza must appear in a poem, if it is not composed simply of lines, +and that if there is both a heading and a stanza they must appear in +that order.

+

Note that the apparent complexity of this model derives from the +constraints expressed informally above. A simpler model, such as + would not enforce any of them, and would therefore permit +such anomalies as a poem consisting only of refrains, or an arbitrary mixture of +lines and refrains.

+ + + +

It is beyond the scope of this "Gentle Introduction to XML" to provide a complete orientation to schema writing with Relax NG, but interested readers may wish to consult more thorough tutorials on the subject.For a complete tutorial introduction to RELAX NG, see . The examples and explanation provided here may be helpful to consult when reading the schema declarations posted for groupings of TEI elements that share the same content model, such as macro.phraseSeq, whose declaration features an example of mixed text and element content. Due to the complexity of the TEI schema as expressed in Relax NG, it is best to customize its content model in TEI itself by writing an ODD, as discussed in .

+
+
+
+
Complicating the Issue +

In the simple cases described so far, we have assumed that one +can identify the immediate constituents of every element in a +textual structure. A poem consists of stanzas, and an anthology +consists of poems. Stanzas do not float around unattached to poems or +combined into some other unrelated element; a poem cannot contain an +anthology. All the elements of a given document type may be arranged +into a hierarchic structure like a family tree, with a single +ancestor at one end and many children (mostly the elements containing +simple text) at the other. For example, we could represent an anthology +containing two poems, the first of which contains two four-line +stanzas and the second a single stanza, by a tree structure like the following figure:

+
+ + + +

This graphic represents the hierarchical structure of an XML document, +resembling a family tree. Most XML processing systems now use a standardized way of accessing +parts of an XML document called XPath.The official specification is at ; many +introductory tutorials are available in the XML references cited above +and elsewhere on the Web: good beginners' tutorials include , and , the latter being +available in several languages. XPath gives us a +non-graphical way of referring to any part of an XML document: for +example, we might refer to the last line of Blake's poem as +/anthology/poem[1]/stanza[2]/line[4]. The square brackets +here indicate a numerical selection: we are talking about the fourth +line in the second stanza of the first poem in the anthology. If we +left out all the square-bracketted selections, the corresponding XPath +expression would refer to all lines contained by stanzas contained by +poems contained by anthologies. An XPath expression can refer to any +collection of elements: for example, the expression +/anthology/poem refers to all poems in an anthology and +the expression /anthology/poem/heading refers to all their headings.

+

The forward slash (‘/’, U+002F SOLIDUS) within an XPath expression behaves in much the same way +as a forward slash or backslash does in a filename specification. +To use a family tree analogy, a single slash indicates that the item to the +immediate left is a parent of the item(s) to the right of it. For example, +in the XPath expression /anthology/poem, the single slash +between anthology and poem indicates that anthology is a parent of the +poem children elements. (The first forward slash in the XPath expression +indicates the document node.) In XPath, it is also possible to refer to +children, grandchildren, and other descendants of the family tree using two +forward slashes together. For example, the XPath expression /anthology/poem//line +will refer to all of the lines of all of the stanzas of all the poems, without +having to represent the stanza element in the XPath.

+ +

Clearly, there are many such trees that might be drawn to describe +the structure of this or other anthologies. Some of them might be +representable as further subdivisions of this tree: for example, we +might subdivide the lines into individual words, since in our simple +example no word crosses a line boundary. Surprisingly perhaps, this +grossly simplified view of what text is (memorably termed an +ordered hierarchy of content objects (OHCO) view of text +by Renear et al.See +.) turns out to +be very effective for a large number of purposes. It is not, however, +adequate for the full complexity of real textual structures, for which +more complex mechanisms need to be employed. There are many other +trees that might be drawn which do not fit within the +anthology model which we have presented so far. We might, for +example, be interested in syntactic structures or other linguistic +constructs, which rarely respect the formal boundaries of verse. Or, +to take a simpler example, we might want to represent the pagination +of different editions of the same text.

+ +

In the OHCO model of text, representation of cases where different +elements overlap so that several different trees may be identified in +the same document is generally problematic. All the elements marked +up in a document, no matter what namespace they belong to, must fit +within a single hierarchy. To represent overlapping structures, +therefore, a single hierarchy must be chosen, and the points at which +other hierarchies intersect with it marked. For example, +we might choose the verse structure as our primary hierarchy, and then +mark the pagination by means of empty elements inserted at the boundary +points between one page and the next. Or we could represent alternative +hierarchies by means of the pointing and linking mechanisms described +in chapter of these Guidelines. These mechanisms all +depend on the use of attributes, which may be used both to +identify particular elements within a document and to point to, link, +or align them into arbitrary structures.

+ + +
+
Attributes +

In the XML context, the word attribute, like +some other words, has a specific technical sense. It is used to +describe information that is in some sense descriptive of a specific +element occurrence but not regarded as part of its content. For +example, you might wish to add a status attribute to +occurrences of some elements in a document to indicate their degree of +reliability, or to add an identifier attribute so that you +could refer to particular element occurrences from elsewhere within a +document. Attributes are useful in precisely such circumstances.

+

Although different elements may have attributes with the same name +(for example, in the TEI scheme, every element is defined as having an +attribute named n), they are always regarded as +different, and may have different values assigned to them. If an +element has been defined as having attributes, the attribute values +are supplied in the document instance as attribute-value +pairs inside the start-tag for the element occurrence. An +end-tag cannot contain an attribute-value specification, since it +would be redundant.

+

The order in which attribute-value pairs are supplied inside a tag +has no significance; they must, however, be separated by at least one +whitespace (blank, newline, or tab) character. The value part +must always be given inside matching quotation marks, either single or +doubleIn the unlikely event that both kinds of quotation marks are needed within the +quoted string, either or both can also be presented in escaped form, using the +predefined character entities &apos; or &quot;.

+

For example: + + ... + +Here attribute values are being specified for two attributes +previously declared for the poem element: xml:id +and status. For the instance of a poem in this +example, represented here by ellipsis points, the xml:id +attribute has the value P1 and the status +attribute has the value draft. An XML processor can use the +values of the attributes in any way it chooses; for example, a +poem in which the status attribute has the value +draft might be formatted differently from one in which the same +attribute has the value revised; another processor might use the +same attribute to determine whether or not poem elements are to be +processed at all. The xml:id attribute is a slightly +special case in that, by convention, it is always used to supply a +unique value to identify a particular element occurrence, which may be +used for cross-reference purposes, as discussed further below ().

+ +
Declaring Attributes + +

Attributes are declared in a schema in the same way as elements. +As well as specifying an attribute's name and the element to which it is to be +attached, it is possible to specify (within limits) what kind of value +is acceptable for an attribute.

+ +

In the compact syntax of RELAX NG, an attribute is defined by means +of an attribute pattern, like the following: + + + +This defines a new pattern, called att.status, whose +value is an attribute pattern defining an attribute named +status. Attribute names are subject to the same +restrictions as other names in XML; they need not be unique across the +whole schema, however, but only within the list of attributes for a +given element.

+ +

A pattern defining the possible values for this attribute is given +within the curly braces, in just the same way as a content model is +given for an element pattern. In this case, the attribute's value must +be one of the strings presented explicitly above.

+ +

The attribute pattern definition must be included or referenced +within the definition for every element to which the attribute is +attached. We therefore modify the definition for the +poem_p pattern given above as follows: + + + +In RELAX NG, an element pattern simply includes any attribute patterns +applicable to it along with its other constituents, as shown +above. Attribute patterns can also be grouped and alternated in the +same way as element patterns, though this particular feature is not +widely used in the TEI scheme, since it is not available to the same +extent in all schema languages. Because a question mark follows the +reference to the att.status pattern in our example, a +document in which the status attribute is not specified +will still be valid; without this occurrence indicator the +status attribute would be required. + +

+ +

Instead of supplying a list of explicit values, an attribute +pattern can specify that the attribute must have a value of a +particular type, for example a text string, a numeric value, a +normalized date, etc. This is accomplished by supplying a pattern +that refers to a datatype. In the example above, +because a list of acceptable values is predefined, a parser can check +that no poem is defined for which the status +attribute does not have one of draft, revised, +or published as its value. By contrast, with a definition +such as a parser would accept almost any +unbroken string of characters (status="awful", +status="awe-ful", or status="12345678") as +valid for this attribute. Sometimes, of course, the set of possible +values cannot be predefined. Where it can, as in this case, it is +generally better to do so.

+ +

Schema languages vary widely in the extent to which they support +validation of attribute values. Some languages predefine a small set +of possibilities. Others allow the schema designer to use values from +a predefined library of possible datatypes, or to +add their own definitions, possibly of great complexity. A +datatype might be something fairly general (any +positive integer), something very specific or idiosyncratic (any +four-character string ending with "T"), or somewhere between the +two. In the RELAX NG schemas used by the TEI, general patterns have +been defined for about half a dozen datatypes (using the W3C Schema +Datatype Library, +and discussed further in ). In addition to the two +possibilities already mentioned—plain text or an explicit list of +possible strings—other datatypes likely to be encountered include +the following: + + +values must be either true or false + +values must represent a numeric quantity of some +kind + +values must represent a possible date and time in some calendar +

+

Two further datatypes of particular usefulness in managing XML documents +are commonly known as ID—for identifier—and +URI—for Universal Resource Indicator, or pointer for +short. These are discussed in the next section.

+
+
Identifiers and Indicators +

It is often necessary to refer to an occurrence of one textual +element from within another, an obvious example being phrases such as +see note 6 or as discussed in chapter 5. When a text is +being produced the actual numbers associated with the notes or +chapters may not be certain. If we are using descriptive markup, such +things as page or chapter numbers, being entirely matters of +presentation, will not in any case be present in the marked-up text: +they will be assigned by whatever processor is operating on the text +(and may indeed differ in different applications). XML therefore +predefines an attribute that may be used to provide any element +occurrence with a special identifier, a kind of label, which may be +used to refer to it from anywhere else: since it is defined in the XML +namespace, the name of this attribute is xml:id and it is +used throughout the TEI schema. Because it is intended to act as an +identifier, its values must be unique within a given document. The +cross-reference itself will be supplied by an element bearing an +attribute of a specific kind, which must also be declared in the +schema.

+

Suppose, for example, we wish to include a reference within +the notes on one poem that refers to another poem. We will +first need to provide some way of attaching a label to each +poem: this is easily done using the xml:id attribute. +Note that not every poem need carry an xml:id attribute and +the parser may safely ignore the lack of one in those that do not. +Only poems to which we intend to refer need use this attribute; for +each such poem we should now include in its start-tag some unique +identifier, for example: + + ... + + ... + + ... + +

+

Next we need to define a new element for the cross-reference +itself. This will not have any content—it is only a +pointer—but it has an attribute, the value of which will be +the identifier of the element pointed at. This is achieved by +the following definition: + +

+ +

The poemRef element has no content, but a single attribute +called target. The value of this attribute must be a +pointer or web reference of type anyURI;The word anyURI is a predefined name, used in +schema languages to mean that any Uniform Resource +Identifier (URI) may be supplied here. The accepted syntax for +URIs is an Internet Standard, defined in . anyURI +is one of the datatypes defined by the W3C +Schema datatype library. +furthermore, because there is no indication of optionality on the +attribute pattern, it must be supplied on each occurrence—a +poemRef with no referent is an impossibility.

+ +

With these declarations in force, we can now encode a reference to +the poem whose xml:id attribute specifies that its +identifier is Rose as follows: + +Blake's poem on the sick rose + ... + +

+

A processor may take any number of actions when it encounters a +link encoded in this way: a formatter might construct an exact page +and line reference for the location of the poem in the current +document and insert it, or just quote the poem's title or first lines. +A hypertext style processor might use this element as a signal to +activate a link to the poem being referred to, for example by +displaying it in a new window. Note, however, that the purpose of the +XML markup is simply to indicate that a cross-reference exists: it +does not necessarily determine what the processor is to do with it.

+ +

The target of a URI can be located anywhere: it may not necessarily +be part of the same document, nor even located on the same computer +system. Equally, it can be a resource of any kind, not necessarily an +XML document or document fragment. It is thus a very convenient way of +including references to non-XML data such as image files within a +document. If, for example, we wished to include an illustration +containing a reproduction of Blake's original in our anthology, the +most appropriate method would probably be to define a new element +called (for the sake of argument) graphic +with a target attribute of datatype URI: + With these additions to the schema, we +can now represent the location of the illustration within our text +like this: + By providing a location from which a reproduction of +the required image can be downloaded, this encoding makes it possible +for appropriate software able to display the image as well as record +its existence.

+

Attributes form part of the structure of an XML document in the +same way as elements, and can therefore be accessed using XPath. For +example, to refer to all the poems in our anthology whose +status attribute has the value draft, we might +use an XPath such as /anthology/poem[@status='draft']. To +find the headings of all such poems, we would use the XPath +/anthology/poem[@status='draft']/heading.

+
+
+ +
Other Components of an XML Document + +

In addition to the elements and attributes so far discussed, an XML +document can contain a few other formally distinct things. An XML +document may contain references to predefined strings of data that a +validator must resolve before attempting to validate the document's +structure; these are called entity references. They may +be useful as a means of providing boilerplate text or +representing character data which cannot easily be keyboarded. As +noted earlier, an XML document may also contain instances of elements +taken from some other namespace. And an XML +document may also contain arbitrary signals or flags for use when the +document is processed in a particular way by some class of processor +(a common example in document production is the need to force a +formatter to start a new page at some specific point in a document); +such flags are called processing instructions. We discuss each of these +three cases in the rest of this section.

+ +

The XML declaration should be supplied at the very +beginning of every XML file; while it looks like a processing +instruction, it is not, and may not occur anywhere other than at the +very beginning of an XML file. For example: ]]> The XML declaration specifies +the version number of the XML Recommendation applicable to the +document it introduces (in this case, version 1.0), and optionally +also the character encoding used to represent the Unicode characters +within it. By default an XML document uses the character encoding +UTF-8 or UTF-16; other commonly-encountered encodings include ISO +8859-1. If any character present in the document is not available in +the specified character encoding, it must be represented as a +character reference (). The XML declaration is +documentary, but should normally be supplied at the start of any XML +file. If it is missing many XML-aware processors will be unable to +process the associated text correctly.

+ +
Character References + +

As mentioned above, all XML documents use the same internal +character encoding. Since not all computer systems currently support +this encoding directly, a special syntax is defined +that can be used to represent individual characters from the Unicode +character set in a portable way by providing their numeric value, in +decimal or hexadecimal notation.

+ +

For example, the character é is represented +within an XML document as the Unicode character with hexadecimal value +00E9. If such a document is being prepared on (or +exported to) a system using a different character set in which this +character is not available, it may instead be represented by the +character reference &#x00E9; (the x indicating +that what follows is a hexadecimal value) or +&#0233; (its decimal equivalent). References of this type do not need +to be predefined, since the underlying character encoding for XML is +always the same.

+ +

To aid legibility, however, it is also possible to use a mnemonic +name (such as eacute) for such character references, +provided that each such name is mapped to the required Unicode value +by means of a construct known as an entity +declaration. A reference to a named character entity always +takes the form of an ampersand, followed by the name, followed by a +semicolon. For example an XML document containing the string +T&C might be encoded as T&amp;C.

+ +

There is a small set of such character +entity references that do not have to be declared because they form +part of the definition of XML. These include the names used for +characters such as the ampersand (amp) and the open angle +bracket or less-than sign (lt), which could not easily +otherwise be included in an XML document without ambiguity. Other +predeclared entity names are those for quotation marks (quot +and apos for double and single respectively), and for +completeness the closing angle bracket or greater-than sign +(gt).

+ +

For all other named character entities, a set of entity declarations +must be provided to an XML processor before the document referring to +them can be validated. The declaration itself uses a non-XML syntax +inherited from SGML; for example, to define an entity named +eacute with the replacement value é, the declaration +could have any of the following forms: ]]> or, using hexadecimal notation: ]]> or, using decimal notation: +]]> +

+ +

Entities of this kind are useful also for string +substitution purposes, where the same text needs to be repeated +uniformly throughout a text. For example, if a declaration such as +]]> is included with a document, +then references such as &TEI; may be used within it, +each of which will be expanded in the same way and replaced by the +string Text Encoding Initiative before the text is validated.

+ + +
+
Namespaces + +

A valid XML document necessarily specifies the schema in which its +constituent elements are defined. However, a well-formed XML document +is not required to specify its schema (indeed, it may not even have a +schema). It would still be useful to indicate that the element names used +in it have some defined provenance. Furthermore, it might be desirable +to include in a document elements that are defined (possibly +differently) in different schemas. A cabinet-maker's schema might well +define an element called table with very different +characteristics from those of a documentalist's.

+

The concept of namespace was introduced into the XML +language as a means of addressing these and related problems. If the +markup of an XML document is thought of as an expression in some +language, then a namespace may be thought of as analogous to the +lexicon of that language. Just as a document can contain words taken +from different languages, so a well-formed XML document can include +elements taken from different namespaces. A namespace resembles a +schema in that we may say that a given +set of elements belongs to a given namespace, or +are defined by a given schema. However, a schema +is a set of element definitions, whereas a namespace is really only a +property of a collection of elements: the only tangible form it takes +in an XML document is its distinctive prefix and the +identifying name associated with it.

+ +

Suppose for example that we wish to extend our anthology to include +a complex diagram. We might start by considering whether or +not to extend our simple schema to include XML markup for such +features as arcs, polygons, and other graphical elements. XML can be +used to represent any kind of structure, not simply text, and there +are clear advantages to having our text and our diagrams all expressed +in the same way.

+

Fortunately we do not need to invent a schema for the +representation of graphical components such as diagrams; it already +exists in the shape of the Scalable Vector Graphics (SVG) language +defined by the W3C.The W3C Recommendation is +defined at . SVG +is a widely used and rich XML vocabulary for representing all kinds of +two-dimensional graphics; it is also well supported by existing +software. Using an SVG-aware drawing package, we can easily draw our +diagram and save it in XML format for inclusion within our +anthology. When we do so, we need to indicate that this part of +the document contains elements taken from the SVG namespace, if only +to ensure that processing software does not confuse our line +element with the SVG line, which means something quite +different.

+

An XML document need not specify any namespace: it is then said to +use the null namespace. Alternatively, the root element of a +document may supply a default namespace, understood to apply to all elements which have no namespace prefix. This is the function of the +xmlns attribute which provides a +unique name for the default namespace, in the form of a URI: + + + + + +In exactly the same way, on the root element for each part of our +document which uses the SVG language, we might introduce the SVG +namespace name: + + + + + + + + + +Although a namespace name usually uses the URI (Uniform Resource +Identifier) syntax, it is not treated as an online address +and an XML processor regards it just as a string, providing a longer name for the +namespace.

+

The xmlns attribute can also be used to associate a short prefix +name with the namespace it defines. This is very useful if we want to +mingle elements from different namespaces within the same document, +since the prefix can be attached to any element, overriding the +implicit namespace for itself (but not its children): + + + + + + + + + +

+

There is no limit on the number of namespaces that a document can +use. Provided that each is uniquely identified, an XML processor can +identify those that are relevant, and validate them appropriately. To +extend our example further, we might decide to add a linguistic +analysis to each of the poems, using a set of elements such as aux, adj, etc., +derived from some pre-existing XML vocabulary for linguistic analysis. + + + + + + + + O + Rose + thou + art + sick + + + +

+ +
Marked Sections +

We mentioned above that the syntax of XML requires the encoder to +take special action if characters with a syntactic meaning in XML +(such as the left angle bracket or ampersand) are to be used in a +document to stand for themselves, rather than to signal the start of a +tag or an entity reference respectively. The predefined entities +&amp;, &lt;, and +&gt; provide one method of dealing with this problem, +if the number of occurrences of such things is small. Other methods +may be considered when the number is large, as in an XML document like +the present Guidelines, which contains hundreds of examples of XML +markup. One is to label the XML examples as belonging to a different +namespace from that of the document itself, which is the approach +taken in the present Guidelines. Another and simpler approach is +provided by one of the features inherited by XML from its parent SGML: +the marked section.

+

A marked section is a block of text within an XML document +introduced by the characters <![CDATA[ and terminated +by the characters ]]>. Between these rather strange +brackets, markup recognition is turned off, and any tags or entity +references encountered are therefore treated as if they were plain +text. For example, when we come to write the users' manual for our +anthology, we may find ourselves often producing text like the +following: +line element: +[...]]]]]>]]>

+ +
+
+ +
Processing Instructions + +

Although one of the aims of using XML is to remove any information +specific to the processing of a document from the document itself, it +is occasionally very convenient to be able to include such information—if +only so that it can be clearly distinguished from the +structure of the document. As suggested above, one common example is +the need, when processing an XML document for printed output, to +include a suggestion that the formatting processor might use to +determine where to begin a new page of output. Page-breaking decisions +are usually best made by the formatting engine alone, but there will +always be occasions when it may be necessary to override these. An XML +processing instruction inserted into the document is one very simple +and effective way of doing this without interfering with other aspects +of the markup.

+

Here is an example XML processing instruction: ]]> It begins with <? and ends with +?>. In between are two strings separated by a space: +the first is the name of some processor (tex in the above +example) and the second is some data intended for the use of that +processor (in this case, the instruction to start a new page). The +only constraint placed by XML on the strings is that the first one +must be a valid XML name other than XML, +Xml, or xml, etc. The second string can be +any arbitrary sequence of characters, not including the closing +character-sequence ?>.

+
+
+ +
Putting It All Together + +

In this chapter we have discussed most of the components of an XML +document and its associated schema. We have described informally +how an XML document is represented, and also introduced one +way of representing the rules a RELAX NG validator might use to +validate it. In a working system, the following issues will also need +to be addressed: + +how does a processor determine the schema (or schemas) that +should be used to validate a given XML document instance? +if a document contains entity references that must be processed before the +document can be validated, where are those entities defined? +an XML document instance may be stored in a number of different +operating system files; how should they be assembled together? +how does a processor determine which stylesheets it should use +when processing an XML document, or how to interpret any processing +instructions it contains? +how does a processor enforce more exact validation than simple +datatypes permit (for example of element content)? + +

+ +

Different schema languages and different XML processing systems +take very different positions on all of these topics, since none of +them is explicitly addressed in the XML specification itself. Consequently, +the best answer is likely to be specific to a particular software +environment and schema language. Since this chapter is concerned with +XML considered independently of its processing environment, we only +address them in summary detail here.

+ +
Associating Entity Definitions with a Document +Instance +

In we introduced the syntax used for the +definition of named character entities such as eacute, +which XML inherited from SGML. Different schema languages vary in the +ways they make a collection of such definitions available +to an XML processor, but fortunately there is one method that all +current schema languages support.

+

As well as, and following, the XML declaration (), an XML document instance may be prefixed with a +special DOCTYPE statement. This declarative statement has +been inherited by XML from SGML; in its full form it provides a large +number of facilities, but we are here concerned only with the small +subset of those facilities recognized by all schema languages.

+

Here is an example DOCTYPE statement which we might consider +prefixing to the final version of our anthology: + + +]>]]> +Any XML processor encountering this statement will use it to add the +two named entities it defines to those already predefined for +XML. Before the document instance itself is validated, any references +to these entities will be expanded to the character string +given. Thus, wherever in the document instance the string +&legalese; appears, it will be replaced by the +formulation above. This makes life a little easier for those +keyboarding our anthology.And, indeed, for those +responsible for deciding the licensing conditions if they change their +minds later. The word anthology following the string +DOCTYPE in this example is, of course, the name of the root element of +the document to which this declaration is prefixed; however, only an XML +DTD processor will take note of this fact.

+ +
Associating a Document Instance with Its Schema + +

In the past, different schema languages adopted entirely different attitudes to +this question, leading to a variety of different methods of associating schemas with +document instances. However, a W3C Working Group Note, + Associating Schemas with XML documents, +() now provides a +standardized method of doing this through the use of a processing instruction: + + ]]> + +The href pseudo-attribute points to the location of the schema. This is the only mandatory + pseudo-attribute, but others can be added to give more information about the schema: + + ]]> + +See the XML Model WG Note for more information on the pseudo-attributes available and +how to use them.

+ +

A document instance may be valid according to many +different schemas, each appropriate to a different processing task. All of these may be expressed in the same way: + + +]]> + +This example includes a standard schema in XML Schema format, along with a Schematron schema which might be +used for checking the format and linking of names.

+ +

Any modern XML processing software tool will provide +convenient methods of validating documents which are appropriate to the particular +schema language chosen. In the interests of maximizing portability of +document instances, they should contain as little processing-specific +information as possible.

+ +
+
Assembling Multiple Resources into a Single Document +

As we have already indicated, a single XML document may be made up +of several different operating system files that need to be pulled +together by a processor before the whole document can be +validated. The XML DTD language defines a special kind of entity (a +system entity) that can be used to embed references to +whole files into a document for this purpose, in much the same way as +the character or string entities discussed in . Neither RELAX NG nor W3C Schema directly supports +this mechanism, however, and we do not +discuss it further here.

+

An alternative way of achieving the same effect is to use a special +kind of pointer element to refer to the resources that need to be +assembled, in exactly the same way as we proposed for the illustration +in our anthology. The W3C Recommendation XML Inclusions + (XInclude). defines a generic mechanism +for this purpose, which is supported by an increasing number of XML +processors.

+ +
Stylesheet Association and Processing +

As mentioned above, the processing of an XML document will usually +involve the use of one or more stylesheets, often but not exclusively +to provide specific details of how the document should be displayed or +rendered. In general, there is no reason to associate a document +instance with any specific stylesheet and the schema languages we have +discussed so far do not therefore make any special provision for such +association. The association is made when the stylesheet processor is +invoked, and is thus entirely application-specific.

+

However, since one very common application for XML documents is to +serve them as browsable documents over the Web, the W3C has defined a +procedure and a syntax for associating a document instance with its +stylesheet (see ). This Recommendation +allows a document to supply a link to a default stylesheet and also to +categorize the stylesheet according to its MIME type, +for example to indicate whether the stylesheet is written in CSS or +XSLT, using a specialized form of processing instruction.

+

Assuming therefore that we have made a CSS-conformant stylesheet +for our anthology and stored it in a file called +anthology.css which is available from the same location +as the anthology itself, we could make it available over the Web simply +by adding a processing instruction like the following to the anthology: +]]>

+

Multiple stylesheets can be defined for the same document, and +options are available to specify how a web browser should select +amongst them. For example, if the document also contained a directive: +]]>a different stylesheet +called anthology_m.css could be used when rendering the +document on a handheld device such as a mobile phone.

+

Most modern web browsers support CSS (although the extent +of their implementation varies), and some of them +support XSLT.

+ +
Content Validation + +

As we noted above, most schema languages provide some degree of +datatype validation for attribute values (). They vary greatly in the validation facilities +they offer for the content of elements, other than the syntactic +constraints already discussed. Thus, while we may very easily check +that our stanza elements contain only line elements, we cannot easily check that line elements contain between five and 500 +correctly-spelled English words, should we wish to constrain our +poetry in such a way. Also, because attributes and elements are +treated differently, it is difficult or impossible to express +co-occurrence constraints: for example, if the status of a poem is draft we might +wish to permit elements such as editorialQuery within its content, but not +otherwise.

+ +

The XML DTD language offers very little beyond syntactic checking +of element content. By contrast, a major impetus behind the design and +development of the W3C schema language was the addition of a much more +general and powerful constraint language to the existing structural +constraints of XML DTDs. In RELAX NG the opposite approach was taken, +in that all datatype validation, whether of attributes or element +content, is regarded as external to the schema language. For +attributes, as we have seen, RELAX NG makes use of the W3C Schema +Datatype Library (but permits use of others). Because RELAX NG treats +both elements and attributes as special cases of patterns, the same +datatype validation facilities are available for element content as +for attribute values; it is unlike other schema languages in +this respect. In addition, for content validation, +a different component of DSDL known as Schematron can be used. Schematron +is a pattern matching (rather than a grammar-based) language, which +allows us to test the components of a document against +templates that express constraints such as those mentioned above.

+ +

Like other XML processors, Schematron uses XPath to identify parts +of an XML document; in addition, it provides elements that describe +assertions to be tested and conditions which must be validated, as +well as elements to report the results of the test.

+
+
diff --git a/P5/Source/Guidelines/fr/ST-Infrastructure.xml b/P5/Source/Guidelines/fr/ST-Infrastructure.xml deleted file mode 120000 index 52b6a1da6f..0000000000 --- a/P5/Source/Guidelines/fr/ST-Infrastructure.xml +++ /dev/null @@ -1 +0,0 @@ -../en/./ST-Infrastructure.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/ST-Infrastructure.xml b/P5/Source/Guidelines/fr/ST-Infrastructure.xml new file mode 100644 index 0000000000..9a981eb043 --- /dev/null +++ b/P5/Source/Guidelines/fr/ST-Infrastructure.xml @@ -0,0 +1,1425 @@ + + + + +
+ The TEI Infrastructure +

This chapter describes the infrastructure for the encoding scheme defined by these Guidelines. + It introduces the conceptual framework within which the following chapters are to be understood, + and the means by which that conceptual framework is implemented. It assumes some familiarity + with XML and XML schemas (see chapter ) but is intended to be accessible to + any user of these Guidelines. Other chapters supply further technical details, in particular + chapter which describes the XML schema used to express these Guidelines + themselves, and chapter which combines a discussion of modification and + conformance issues with a description of the intended behaviour of an ODD processor; these + chapters should be read by anyone intending to implement a new TEI-based system.

+

The TEI encoding scheme consists of a number of modules, each of which declares + particular XML elements and their attributes. Part of an element's declaration includes its + assignment to one or more element classes. Another part defines its possible + content and attributes with reference to these classes. This indirection gives the TEI system + much of its strength and its flexibility. Elements may be combined more or less freely to form a + schema appropriate to a particular set of requirements. It is also easy to add + new elements which reference existing classes or elements to a schema, as it is to exclude some + of the elements provided by any module included in a schema.

+

In principle, a TEI schema may be constructed using any combination of modules. However, + certain TEI modules are of particular importance, and should always be included in all but + exceptional circumstances: the module tei described in the present + chapter is of this kind because it defines classes, macros, and datatypes which are used by all + other modules. The core module, defined in chapter contains declarations for elements and attributes which are likely to be needed + in almost any kind of document, and is therefore recommended for global use. The header module defined in chapter provides + declarations for the metadata elements and attributes constituting the TEI header, a component + which is required for TEI conformance, while the textstructure + module defined in chapter declares basic structural elements needed for the + encoding of most book-like objects. Most schemas will therefore need to include these four + modules.

+

The specification for a TEI schema is itself a TEI document, using elements from the module + described in chapter : we refer to such a document informally as an + ODD document, from the design goal originally formulated for the system: One + Document Does it all. Stylesheets for maintaining and processing ODD documents are + maintained by the TEI, and these Guidelines are also maintained as such a document. As further + discussed in , an ODD document can be processed to generate a schema + expressed using any of the three schema languages currently in wide use: the XML DTD language, + the ISO RELAX NG language, or the W3C Schema language, as well as to generate documentation such + as the Guidelines and their associated web site.

+

The bulk of this chapter describes the TEI infrastructure module itself. Although it may be + skipped at a first reading, an understanding of the topics addressed here is essential for + anyone planning to take full advantage of the TEI customization techniques described in chapter + .

+

The chapter begins by briefly characterizing each of the modules available in the TEI scheme. + Section describes in general terms the method of constructing a TEI schema + in a specific schema language such as XML DTD language, RELAX NG, or W3C Schema.

+

The next and largest part of the chapter introduces the attribute and element classes used to + define groups of elements and their characteristics (section ).

+

Finally, section introduces the concept of macros, which + are used to express some commonly used content models, and lists the datatypes used + to constrain the range of legal values for TEI attributes (section ).

+
+ TEI Modules +

These Guidelines define several hundred elements and attributes for marking up documents of + any kind. Each definition has the following components: + a prose description + a formal declaration, expressed using a special-purpose XML vocabulary defined by + these Guidelines in combination with elements taken from the ISO schema language RELAX + NG + usage examples +

+

Each chapter of these Guidelines presents a group of related elements, and also defines a + corresponding set of declarations, which we call a module. All the definitions + are collected together in the reference sections provided as an appendix. Formal declarations + for a given chapter are collected together within the corresponding module. For convenience, + each element is assigned to a single module, typically for use in some specific application + area, or to support a particular kind of usage. A module is thus simply a convenient way of + grouping together a number of associated element declarations. In the simple case, a TEI + schema is made by combining together a small number of modules, as further described in + section below.

+

The following table lists the modules defined by the current release of these Guidelines: + + + + Module name + Formal public identifier + Where defined + + + analysis + Analysis and Interpretation + + + + certainty + Certainty and Uncertainty + + + + core + Common Core + + + + corpus + Metadata for Language Corpora + + + + + dictionaries + Print Dictionaries + + + + drama + Performance Texts + + + + figures + Tables, Formulae, Figures + + + + gaiji + Character and Glyph Documentation + + + + header + Common Metadata + + + + iso-fs + Feature Structures + + + + linking + Linking, Segmentation, and Alignment + + + + msdescription + Manuscript Description + + + + namesdates + Names, Dates, People, and Places + + + + nets + Graphs, Networks, and Trees + + + + spoken + Transcribed Speech + + + + tagdocs + Documentation Elements + + + + tei + TEI Infrastructure + + + + + textcrit + Text Criticism + + + + textstructure + Default Text Structure + + + + transcr + Transcription of Primary Sources + + + + verse + Verse + + +
+

+

For each module listed above, the corresponding chapter gives a full description of the + classes, elements, and macros which it makes available when it is included in a schema. Other + chapters of these Guidelines explore other aspects of using the TEI scheme.

+
+
+ Defining a TEI Schema +

To determine that an XML document is valid (as opposed to merely well-formed), its structure + must be checked against a schema, as discussed in chapter . For a valid TEI + document, this schema must be a conformant TEI schema, as further defined in chapter . Local systems may allow their schema to be implicit, but for interchange + purposes the schema associated with a document must be made explicit. The method + of doing this recommended by these Guidelines is to provide explicitly or by reference a TEI + schema specification against which the document may be validated.

+

A TEI-conformant schema is a specific combination of TEI modules, possibly also including + additional declarations that modify the element and attribute declarations contained by each + module, for example to suppress or rename some elements. The TEI provides an + application-independent way of specifying a TEI schema by means of the schemaSpec + element defined in chapter . The same system may also be used to specify a + schema which extends the TEI by adding new elements explicitly, or by reference to other XML + vocabularies. In either case, the specification may be processed to generate a formal schema, + expressed in a variety of specific schema languages, such as XML DTD language, RELAX NG, or + W3C Schema. These output schemas can then be used by an XML processor such as a validator or + editor to validate or otherwise process documents. Further information about the processing of + a TEI formal specification is given in chapter .

+
+ A Simple Customization +

The simplest customization of the TEI scheme combines just the four recommended modules + mentioned above. In ODD format, this schema specification takes this form: + + + + + + +

+

This schema specification contains references to each of four modules, identified by the + key attribute on the moduleRef element. The schema specification + itself is also given an identifier (TEI-minimal). An ODD processor will + generate an appropriate schema from this set of declarations, expressed using the XML DTD + language, the ISO RELAX NG language, the W3C Schema language, or in principle any other + adequately powerful schema language. The resulting schema may then be associated with the + document instance by one of a number of different mechanisms, as further described in + chapter . The start point (or root element) of document instances to be + validated against the schema is specified by means of the start attribute. + Further information about the processing of an ODD specification is given in .

+
+
+ A Larger Customization +

These Guidelines introduce each of the modules making up the TEI scheme one by one, and + therefore, for clarity of exposition, each chapter focusses on elements drawn from a single + module. In reality, of course, the markup of a text will draw on elements taken from many + different modules, partly because texts are heterogeneous objects, and partly because + encoders have different goals. Some examples of this heterogeneity include: + a text may be a collection of other texts of different types: for example, an + anthology of prose, verse, and drama; + a text may contain other smaller, embedded texts: for example, a poem or song + included in a prose narrative; + some sections of a text may be written in one form, and others in a different form: + for example, a novel where some chapters are in prose, others take the form of + dictionary entries, and still others the form of scenes in a play; + an encoded text may include detailed analytic annotation, for example of rhetorical + or linguistic features; + an encoded text may combine a literal transcription with a diplomatic edition of the + same or different sources; + the description of a text may require additional specialized metadata elements, for + example when describing manuscript material in detail. +

+

The TEI provides mechanisms to support all of these and many other use cases. The + architecture permits elements and attributes from any combination of modules to co-exist + within a single schema. Within particular modules, elements and attributes are provided to + support differing views of the granularity of a text, for example: + + a definition of a corpus or collection as a series of TEI documents, + sharing a common TEI header (see chapter ) + a definition of composite texts which combine optional front- and back-matter with a + group of collected texts, themselves possibly composite (see section ) + an element for the representation of embedded texts, where one + narrative appears to float within another (see section ) +

+

Subsequent chapters of these Guidelines describe in detail markup constructs appropriate + for these and many other possible features of interest. The markup constructs can be + combined as needed for any given set of applications or project.

+

For example, a project aiming to produce an ambitious digital edition of a collection of + manuscript materials, to include detailed metadata about each source, digital images of the + content, along with a detailed transcription of each source, and a supporting biographical + and geographical database might need a schema combining several modules, as follows: + + + + + + + + + + + + +

+

Alternatively, a simpler schema might be used for a part of such a project: those preparing + the transcriptions, for example, might need only elements from the core, textstructure, and transcr modules, and might therefore prefer to use a simpler schema such as that + generated by the following: + + + + + +

+

The TEI architecture also supports more detailed customization beyond the simple selection + of modules. A schema may suppress elements from a module, suppress some of their attributes, + change their names, or even add new elements and attributes. Detailed discussion of the kind + of modification possible in this way is provided in and conformance + rules relating to their application are discussed in . These facilities + are available for any schema language (though some features may not be available in all + languages). The ODD language also makes it possible to combine TEI and non-TEI modules into + a single schema, provided that the non-TEI module is expressed using the RELAX NG schema + language (see further ).

+
+
+
+ The TEI Class System +

The TEI scheme distinguishes about five hundred different elements. To aid comprehension, + modularity, and modification, the majority of these elements are formally classified in some + way. Classes are used to express two distinct kinds of commonality among elements. The + elements of a class may share some set of attributes, or they may appear in the same locations + in a content model. A class is known as an attribute class if its members share + attributes, and as a model class if its members appear in the same locations. In + either case, an element is said to inherit properties from any classes of which + it is a member.

+

Classes (and therefore elements which are members of those classes) may also inherit + properties from other classes. For example, supposing that class A is a member (or a + subclass) of class B, any element which is a member of class A will inherit not + only the properties defined by class A, but also those defined by class B. In such a + situation, we also say that class B is a superclass of class A. The properties of + a superclass are inherited by all members of its subclasses.

+

A basic understanding of the classes into which the TEI scheme is organized is strongly + recommended and is essential for any successful customization of the system.

+
+ Attribute Classes +

An attribute class groups together elements which share some set of common attributes. + Attribute classes are given names composed of the prefix att., often followed + by an adjective. For example, the members of the class att.canonical have in common a key and a ref attribute, + both of which are inherited from their membership in the class rather than individually + defined for each element. These attributes are said to be defined by (or inherited from) the + att.canonical class. If another element were to be added to + the TEI scheme for which these attributes were considered useful, the simplest way to + provide them would be to make the new element a member of the att.canonical class. Note also that this method ensures that the attributes in + question are always defined in the same way, taking the same default values etc., no matter + which element they are attached to.

+

Some attribute classes are defined within the tei + infrastructural module and are thus globally available. Other attribute classes are specific + to particular modules and thus defined in other chapters. Attributes defined by such classes + will not be available unless the module concerned is included in a schema.

+

The attributes provided by an attribute class are those specified by the class itself, + either directly, or by inheritance from another class. For example, the attribute class + att.pointing.group provides attributes domains and + targFunc to all of its members. This class is however a subclass of the att.pointing class, from which its members also inherit the + attributes target, targetLang and evaluate. Members of the + class att.pointing will thus have these three attributes, while + members of the class att.pointing.group will have all five.

+

Note that some modules define superclasses of an existing infrastructural class. For + example, the global attribute class att.divLike makes attributes + org and sample available, while the att.metrical class, which is specific to the verse + module, provides attributes met, real, and rhyme. Because + att.metrical is defined as a superclass of att.divLike, all five of these attributes are available to elements; the + declaration for att.metrical adds its three attributes to the + three already defined by att.divLike when the verse module is included in a schema. If, however, this module is + not included in a schema, then the att.divLike class supplies + only the two attributes first mentioned.

+

Attributes specific to particular modules are documented along with the relevant module + rather than in the present chapter. One particular attribute class, known as att.global, is common to all modules, and is therefore described in + some detail in the next section. A full list of all attribute classes is given in below.

+
+ Global Attributes +

The following attributes are defined in the infrastructure module for every TEI element. + + +

+

Some of these attributes (specifically xml:id, n, xml:lang, + xml:base and xml:space) are provided by the att.global attribute class itself. + The others are provided by one its subclasses att.global.rendition, + att.global.responsibility, or att.global.source. + Their usage is discussed in the following subsections.

Several other globally-available + attributes are defined by other subclasses of the att.global class. These + are provided by other modules, and are therefore discussed in the chapter discussing that module. + A brief summary table is provided in section below.

+
+ Element Identifiers and Labels +

The value supplied for the xml:id attribute must be a legal + name, as defined in the World Wide Web Consortium's XML Recommendation. This means that it + must begin with a letter, or the underscore character (_), and contain no + characters other than letters, digits, hyphens, underscores, full stops, and certain + combining and extension characters.The colon is also by default a + valid name character; however, it has a specific purpose in XML (to indicate namespace + prefixes), and may not therefore be used in any other way within a name.

+

In XML names (and thus the values of xml:id in an XML TEI document) + uppercase and lowercase letters are distinguished, and thus + partTime and parttime are two distinctly + different names, and could (though perhaps unwisely) be used to denote two different + element occurrences.

+

If two elements are given the same identifier, a validating XML parser will signal a + syntax error. The following example, therefore, is not valid: +<p xml:id="PAGE1"><q>What's it going to be then, eh?</q></p> +<p xml:id="PAGE1">There was me, that is Alex, and my three droogs, that is Pete, +Georgie, and Dim, ... </p> +

+

For a discussion of methods of providing unique identifiers for elements, see section + .

+

The n attribute also provides an identifying name or number for an element, + but in this case the information need not be a legal xml:id value. Its value + may be any string of characters; typically it is a number or other similar enumerator or + label. For example, the numbers given to the items of a numbered list may be recorded + with the n attribute; this would make it possible to record errors in the + numeration of the original, as in this list of chapters, transcribed from a faulty + original in which the number 10 is used twice, and 11 is omitted: + About These Guidelines + A Gentle Introduction to XML + Verse + Drama + Spoken Materials + Dictionaries + The n attribute may also be used to record non-unique names + associated with elements in a text, possibly together with a unique identifier as in the + following example:

+ +
+ +
+
+

+

As noted above there is no requirement to record a value for either the + xml:id or the n attribute. Any XML processor can identify the + sequential position of one element within another in an XML document without any + additional tagging. An encoding in which each line of a long poem is explicitly labelled + with its numerical sequence such as the following + + + + + is therefore probably redundant.

+
+
+ Language Indicators +

The xml:lang attribute indicates the natural language and writing system + applicable to the content of a given element. If it is not specified, the value is + inherited from that of the immediately enclosing element. As a rule, therefore, it is + simplest to specify the base language of the text on the TEI element, and allow + most elements to take the default value for xml:lang; the language of an + element then need be explicitly specified only for elements in languages other than the + base language. For this reason, it is recommended practice to supply a default value for + the xml:lang attribute, either on the TEI root element, or on both + the teiHeader and the text element. The latter is appropriate in the + not uncommon case where the text element in a TEI document uses a different default + language from that of the TEI header attached to it. Other language shifts in the source + should be explicitly identified by use of the xml:lang attribute on an + element at an appropriate level wherever possible.

+

In the following example schematic, an English language TEI header is attached to an + English language text: + + + + + + + + +

+

The same effect would be obtained by specifying the default language for both header + and text: + + + + + + + + +

+

The latter approach is necessary in the case where the two differ: for example, where + an English language header is applied to a French text: + + + + + + + + +

+

The same principle applies at any hierarchic level. In the following example, the + default language of the text is French, but one section of it is in German: + + + + + + +

+ +
+
+ +
+
+ +
+ + + + +

+

Similarly, in the following example the xml:lang attribute on the + term element allows us to record the fact that the technical terms used are + Latin rather than English; no xml:lang attribute is needed on the q + element, by contrast, because it is in the same language as its parent.

The + constitution declares that no bill of attainder or ex post + facto law shall be passed. ...

+

+

Note that in cases where it is advisable or necessary to identify the language of the + text that is pointed at, the (non-global) attribute targetLang should be + used, for example in the pointer references text written in French.

+

The values used for the xml:lang and targetLang attributes must + be constructed in a particular way, using values from standard lists. See further .

+

Additional information about a particular language may be supplied in the + language element within the header (see section ).

+
+
+ Rendition Indicators +

The rend, rendition, and style attributes are all used + to give information about the physical presentation of the text in the source. In the + following example, rend is used to indicate that both the emphasized word and + the proper name are printed in italics:

... Their motives might be pure + and pious; but he was equally alarmed by his knowledge of the ambitious Bohemond, and his ignorance of the Transalpine chiefs: + ...

The same effect might be achieved using the style + attribute, as follows:

... Their motives might be pure and pious; but he was equally alarmed by his knowledge of + the ambitious Bohemond, and his ignorance of + the Transalpine chiefs: ...

 If all or most emph and + name elements are rendered in the text by italics, it will be more convenient + to register that fact in the TEI header once and for all (using the rendition + element discussed below) and specify a rend or style value only + for any elements which deviate from the stated rendition.

+

The main difference between rend attribute and style is that the + value used for the former may contain one or more tokens from any vocabulary devised by + the encoder, separated by space characters, whereas the value used for the latter must + be a single string taken from a formally-defined style definition language such as CSS. + The rend attribute values are sequence-indeterminate set of + whitespace-separated tokens, whereas style values allow whitespace and + sequence relationships as part of the formally-defined style definition language.

+

The rendition element defined in may be used to hold + repeatedly-used format descriptions. A rendition element can then be associated + with any element, either by default, or by means of the global rendition + attribute. For example: + + + font-style: italic; + + font-family: serif; + + + + +

+

+ +

+

+ +

+
+ + + +

+

The rendition attribute always points to one or more rendition + elements, each of which defines some aspect of the rendering or appearance of the text + in its original form. These details may most conveniently be described using a formal + style definition language, such as CSS () or XSL-FO (); in some other formal language developed for a specific project; or + even informally in running prose. Although languages such as CSS and XSL-FO are + generally used to describe document output to screen or print, they nonetheless provide + formal and precise mechanisms for describing the appearance of source documents, + especially print documents, but also many aspects of manuscript documents. For example, + both CSS and XSL-FO provide mechanisms for describing typefaces, weight, and styles; + character and line spacing; and so on.

+

As noted above, the style attribute is provided for encoders wishing to + describe the appearance of individual source elements using a language such as CSS + directly rather than by reference to a rendition element. Its value may be any + expression in the chosen formal style definition language.

+

Formal definition languages such as CSS typically identity a series of + properties (such as font-style or margin-left) for which + values are specified. A sequence of such property-value pairs makes up a + stylesheet. The TEI uses such languages simply to describe the appearance of a source + document, rather than to control how it should be formatted.

+

In the TEI scheme, it is possible to supply information about the appearance of + elements within a source document in the following distinct ways: + One or more properties may be specified as the + default for a set of elements (based on an external + scheme, by default CSS), using rendition elements + and their selector attributes; + One or more properties may be specified for individual element occurrences, + using the rend attribute with any convenient set of one or more + sequence-indeterminate tokens; + One or more properties may be specified for individual element occurrences, + using the rendition attribute to point to rendition elements; + One or more properties may be supplied explicitly for individual element + occurrences, using the style attribute. + +

+

If the same property is specified in more than one of the above ways, the one with the + highest number in the list above is understood to be applicable. The resulting + properties from each way are then combined to provide the full set of property-value + pairs applicable to the given element, and (by default) to all of its children.

+

For simplicity of processing, the same formal style definition should be used + throughout; however, the architecture does permit this to be varied, by using the + scheme attribute to indicate a different language for one or more + rendition elements. Care should be taken to ensure that such values can be + meaningfully combined. Similar considerations apply to the use of the rend + attribute, if this is used in combination with either rendition or + style.

+

Note that these TEI attributes always describe the rendition or appearance of the + source document, not intended output renditions, although often the two may + be closely related.

+
+ + +
+ Sources, certainty, and responsibility +

The source attribute is used to indicate the source of an element and its content, for example + by pointing to a bibliographic citation for a quotation to indicate the source from which it derives. The target of the + pointer may be an entry in a bibliographic list of some kind, or a pointer to a digital version of the source itself.

+ +

As with other TEI pointers, the value of this attribute + is expressed as any form of URI, for example an absolute + URL, a relative URL, or a private scheme URI that is + expanded to a relative or absolute URL as documented in a + prefixDef. In the following typical example a + relative bare name URL value is used + to point to a bibl elsewhere in the bibliography + of the document which contains a bibliographic source for + the quotation itself: + +

+ + Grammatical theories + are in flux, and the more we learn, the less we + seem to know. + +

+ + The Chicago Manual of Style, + 15th edition. + Chicago: + University of Chicago Press + (2003), + p.147. + +

+ Alternatively, the quotation might be directly linked to the online edition of this source using a full URI : + +

+ + Grammatical theories + are in flux, and the more we learn, the less we + seem to know. + +

+ +

+

The source attribute is + also used on schema documentation elements such as schemaSpec or elementRef to indicate + the location from which declarations for the components being defined may + be obtained by an ODD processor. For example, a customization wishing to include the p element specifically as it was in version 2.0.1 of TEI P5 would indicate the source for this on an elementRef element like + the following: + + + + Here the value of the source attribute is provided using + private URI syntax, using a short cut predefined for the TEI Guidelines. More generally, an ODD customization can + point to a URI from which a compiled version of any ODD can be downloaded. The above shortcut is equivalent to + + + + Elements such as moduleRef or elementRef can use the source attribute in this way to + point to any previously compiled set of TEI ODD specifications which are to be included in a schema, as further + discussed in section

+ +

The cert attribute provides a method of indicating the encoder's certainty + concerning an intervention or interpretation represented by the markup. It is typically used where + the encoder wishes to supply one or more possible corrections to a text, indicating the + certainty they wish to attach to each, as in the following example: + + + Blessed are the cheesemakerspeacemakersplacemakers: +for they shall be called the children of God. + The cert attribute will usually, as here, characterize the degree of certainty simply as high, medium or low. + In situations where a more detailed or nuanced indication is required, it can instead supply a probability value between 0 (minimal + probability) and 1 (maximal probability). Other more sophisticated mechanisms are discussed in chapter . +

+

The resp attribute is used to indicate the person or organization considered responsible for some aspects + of the information encoded by an element. For example, the preceding example might be revised as follows to indicate the editors responsible + for the two corrections: + + ... peacemakers + placemakers... + When a more detailed or nuanced representation of responsibility is required, it is recommended that the element + indicated by the resp attribute should not be a generic agent (for example a person or org) + but a more precise element such as respStmt, author, or editor which can document the + exact role played by the agent. In the following example, we indicate that the correction of n to u + was made by a particular named transcriber: + + + + + Punkes, Panders, baſe extortionizing + slanues, + + + + + + Transcriber + Janelle Jenstad + + + Pointing to multiple respStmts allows the encoder to specify clearly each of the roles played in part of a TEI file (creating, transcribing, encoding, editing, proofing etc.). + If appropriate, the name element inside a respStmt may also be associated with a more detailed person + or org element using methods discussed in chapter .

+
+ +
+ Evaluation of Links +

Several TEI elements carry attributes whose values are defined as anyURI, + meaning that such attributes supply a link or pointer, typically expressed as a URL. + Like other XML applications, the TEI allows use of a special attribute to set the + context within which relative URLs are to be evaluated. The global attribute + xml:base is defined as part of the XML specification and belongs to the XML + namespace rather than the TEI namespace. We do not describe it in detail here: reference + information about xml:base is provided by +

+

In essence xml:base is used to set a context for all relative URLs within + the scope of the element on which it is specified. For example: + +

+

+ + +

+
+
+

+ + +

+
+ The first ptr element here is within the scope of a + div which supplies a value for xml:base; its target is therefore + to be found at http://www.example.org/elsewhere.xml. The second + ptr, however, is within the scope of a div which does not change the + default context, and its target is therefore a document in the same directory as the current + document.

+

The xml:base attribute is intended to enable the stable resolution of + relative URIs in a document after that document's context may have changed (for example as a + result of being embedded in another document via XInclude). Setting the xml:base + simply as a way to allow encoders to write shorter URIs is not recommended. In + particular, xml:base may cause ambiguity as to the referent of same-document + references in the form #id (where id is an xml:id). + RFC 3986 states that + URIs of this type should not result in the loading of a different document. The RFC + therefore assumes that such references are internal to the document in which they are located. + Using xml:base to denote arbitrary external bases while also using same-document + references may mean that software agents deal with these links in unexpected and + inconsistent ways. Further discussion of this attribute and its effect on TEI linking methods + is provided in chapter .

+
+
+ XML Whitespace +

The global attribute xml:space provides a mechanism for indicating to + systems processing an XML file how they should treat whitespace, that is, any sequences + of consecutive tab (#x09), space (#x20), carriage return (#x0D) or linefeed (#x0A) + characters. Like xml:id this attribute is defined as part of the XML + specification and belongs to the XML namespace rather than the TEI namespace. Complete + information about this attribute is provided by section 2.10 of the XML + Specification; here we provide a summary of how its use affects users of the TEI + scheme.

+

The xml:space attribute has only two permitted values: preserve + and default. The first indicates that whitespace in a text node—every + carriage return, every tab, etc.—should be maintained as is when the document is + processed. The second (which is implied when the attribute is not supplied), indicates + that whitespace should be handled as appropriate. Exactly what is + deemed appropriate is left unspecified by the XML Recommendation.

+

These Guidelines assume one of two different ways of processing whitespace will apply + in a given case, depending on an element's content model. For an element that can + contain only other elements with no intervening non-whitespace characters, whitespace is + considered to have no semantic significance, and should therefore be discarded by a + processor. For example, in a choice element, such as + + 1724 + 1728 + + since non-whitespace text is not permitted between the choice + start-tag and the sic tags or between the sic and corr tags, + any whitespace found there has no significance and can be ignored completely by a + processor.

+

Similarly, the address element has a content model containing only elements: + any punctuation or whitespace required between the lines of an address must therefore be + supplied by the processor, as any whitespace present in the input document will be + ignored.

+

Elements with content models of this type are comparatively unusual in the TEI: a list + of them is provided in the TEI release file stripspace.xsl.model, formatted there for use as an xsl:strip-space + command for XSL stylesheets.

+

Most TEI elements permit what is known as mixed-content: that is, they can contain both + text and other elements. Here the assumption of these Guidelines is that whitespace will + be normalized. This means that all space, carriage return, linefeed, and tab characters + are converted into spaces, all consecutive spaces are then deleted and replaced by one + space, and then space immediately after a start-tag or immediately before an end-tag is + deleted. The result is that this encoding, + + Edward + George + Bulwer-Lytton, Baron Lytton of + Knebworth + + + would be rendered as Edward George Bulwer-Lytton, Baron Lytton of + Knebworth. The space before his name has been removed, a space is included between + his forenames, the comma is preserved, and the newlines within his name have all been + removed.

+ +

If the default treatment described above is not appropriate for a mixed content + element, the processing required may be described in the encodingDesc element + of the TEI header, but generic XML processing tools may not take note of this.

+

Alternatively, the xml:space attribute may be supplied with a value of + preserve in order to indicate that every space, tab, carriage return and + linefeed character found within that element in the document being processed is + significant. Typically, the result of that processing will be to retain the whitespace + characters in the output. Thus if the above example began persName + xml:space="preserve", the resulting text would most likely be rendered over five + lines, indented, and with a blank line following.

+

The xml:space="preserve" attribute is rarely used in TEI documents because + such layout features are generally captured with less risk and more precision by using + native TEI elements such as lb or space, or by using the renditional + attributes described in section .

+
Other Globally Available Attributes +

The following table lists for convenience other potentially available global attributes. + The table specifies the name of the attribute class providing the attributes concerned, the module which must + be included in a schema if the attributes are to be made available, and the section of these Guidelines + where the class is discussed. + + class namemodule namesee further + att.global.linkinglinking + att.global.analyticanalysis + att.global.facstranscr + att.global.changetranscr +
+

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ Model Classes +

As noted above, the members of a given TEI model class share the property that they can all + appear in the same location within a document. Wherever possible, the content model of a TEI + element is expressed not directly in terms of specific elements, but indirectly in terms of + particular model classes. This makes content models simpler and more consistent; it also + makes them much easier to understand and to modify.

+

Like attribute classes, model classes may have subclasses or superclasses. Just as elements + inherit from a class the ability to appear in certain locations of a document (wherever the + class can appear), so all members of a subclass inherit the ability to appear wherever any + superclass can appear. To some extent, the class system thus provides a way of reducing the + whole TEI galaxy of elements into a tidy hierarchy. This is however not entirely the + case.

+

In fact, the nature of a given class of elements can be considered along two dimensions: as + noted, it defines a set of places where the class members are permitted within the document + hierarchy; it also implies a semantic grouping of some kind. For example, the very large + class of elements which can appear within a paragraph comprises a number of other classes, + all of which have the same structural property, but which differ in their field of + application. Some are related to highlighting, while others relate to names or places, and + so on. In some cases, the set of places where class members are + permitted is very constrained: it may just be within one specific element, or + one class of element, for example. In other cases, elements may be permitted to appear in + very many places, or in more than one such set of places.

+

These factors are reflected in the way that model classes are named. If a model class has a + name containing part, such as model.divPart or model.biblPart then it is primarily defined in terms of its + structural location. For example, those elements (or classes of element) which appear as + content of a div constitute the model.divPart class; + those which appear as content of a bibl constitute the model.biblPart class. If, however, a model class has a name containing + like, such as model.biblLike or model.nameLike, the implication is that its members all have some additional + semantic property in common, for example containing a bibliographic description, or + containing some form of name, respectively. These semantically-motivated classes often + provide a useful way of dividing up large structurally-motivated classes: for example, the + very general structural class model.pPart.data (data + elements that form part of a paragraph) has four semantically-motivated member + classes (model.addressLike, model.dateLike, model.measureLike, and model.nameLike), the last of these being itself a superclass with + several members.

+

Although most classes are defined by the tei infrastructure + module, a class cannot be populated unless some other specific module is included in a + schema, since element declarations are contained by modules. Classes are not declared + top down, but instead gain their members as a consequence of + individual elements' declaration of their membership. The same class may therefore contain + different members, depending on which modules are active. Consequently, the content model of + a given element (being expressed in terms of model classes) may differ depending on which + modules are active.

+

Some classes contain only a single member, even when all modules are loaded. One reason for + declaring such a class is to make it easier for a customization to add new member elements + in a specific place, particularly in areas where the TEI does not make fully elaborated + proposals. For example, the TEI class model.rdgLike, initially + empty, is expanded by the textcrit module to include just the + TEI rdg element. A project wishing to add an alternative way of structuring + text-critical information could do so by defining their own elements and adding it to this + class.

+

Another reason for declaring single-member classes is where the class members are not + needed in all documents, but appear in the same place as elements which are very frequently + required. For example, the specialized element g used to represent a non-Unicode + character or glyph is provided as the only member of the model.gLike class when the gaiji module is added to + a schema. References to this class are included in almost every content model, since if it + is used at all the g must be available wherever text is available; however these + references have no effect unless the gaiji module is loaded.

+

At the other end of the scale, a few of the classes predefined by the tei module are + subsequently populated with very many members. For example, the class model.pPart.edit groups all the classes of element for simple editorial + correction and transcription which can appear within a p or paragraph element. The + core module alone adds more than fifty elements to this + class; the namesdates module adds another twenty, as does the + tagdocs module. Since the p element is one of the + basic building blocks of a TEI document it is not surprising that each module will need to + add elements to it. The class system here provides a very convenient way of controlling the + resulting complexity. Typically, elements are not added directly to these very general + classes, but via some intermediate semantically-motivated class.

+

Just as there are a few classes which have a single member, so there are some classes which + are used only once in the TEI architecture. These classes, which have no superclass and + therefore do not fit into the class hierarchy defined here, are a convenient way of + maintaining elements which are highly structured internally, but which appear from the + outside to be uniform objects like others at the same level.In former + editions of these Guidelines, such elements were known metaphorically as + crystals. Members of such classes can only ever appear + within one element, or one class of elements. For example, the class model.addrPart is used only to express the content model for the element + address; it references some other classes of elements, which can appear + elsewhere, and also some elements which can only appear inside an address.

+
+ Informal Element Classifications +

Most TEI elements may also be informally classified as belonging to one of the following + groupings: + + high level, possibly self-nesting, major divisions of texts. These elements + populate such classes as model.divLike or model.div1Like, and typically form the largest component units + of a text. + + elements such as paragraphs and other paragraph-level elements, which can appear + directly within texts or within divisions of them, but not (usually) within other + chunks. These elements populate the class model.divPart, + either directly or by means of other classes such as model.pLike (paragraph-like elements), model.entryLike, etc. + + elements such as highlighted phrases, book titles, or editorial corrections which + can occur only within chunks, but not between them (and thus cannot appear directly + within a division). These elements populate the class model.phrase.Note that in this context, + phrase means any string of characters, and can apply to individual + words, parts of words, and groups of words indifferently; it does not refer only to + linguistically-motivated phrasal units. This may cause confusion for readers + accustomed to applying the word in a more restrictive sense. + +

+

The TEI also identifies two further groupings derived from these three: + + elements such as lists, notes, quotations, etc. which can appear either between + chunks (as children of a div) or within them; these elements populate the + class model.inter. Note that this class is not a superset + of the model.phrase and model.divPart classes but rather a distinct grouping of elements which are + both chunk-like and phrase-like. However, the classes model.phrase, model.pLike, and model.inter are all disjoint. + + elements which can appear directly within texts or text divisions; this is a + combination of the inter- and chunk- level elements defined above. These elements + populate the class model.common, which is defined as a + superset of the classes model.divPart, model.inter, and (when the dictionary module is included in a schema) + model.entryLike. + Broadly speaking, the front, body, and back of a text each comprises a series of + components, optionally grouped into divisions.

+

As noted above, some elements do not belong to any model class, and some model classes + are not readily associated with any of the above informal groupings. However, over + two-thirds of the elements defined in the present edition of + these Guidelines are classified in this way, and future editions of these recommendations + will extend and develop this classification scheme.

+

A complete alphabetical list of all model classes is provided in .

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ Macros +

The infrastructure module defined by this chapter also declares a number of + macros, or shortcut names for frequently occurring parts of other declarations. + Macros are used in two ways in the TEI scheme: to stand for frequently-encountered content + models, or parts of content models (); and to stand for attribute + datatypes ().

+
+ Standard Content Models +

As far as possible, the TEI schemas use the following set of frequently-encountered content + models to help achieve consistency among different elements. + + + + + + + +

+ + +

The present version of the TEI Guidelines includes some different + elements. shows, in descending order of frequency, the + seven most commonly used content models.

+ + + + + + + + + +
+
+ Datatype Specifications +

The values which attributes may take in a TEI schema are defined, for the most part, by + reference to a TEI datatype specification. Each such specification is defined + in terms of other primitive datatypes, derived mostly from W3C Schema + Datatypes, literal values, or other datatypes. This indirection makes it possible + for a TEI application to set constraints either globally or in individual cases, by + redefining the datatype definition or the reference to it respectively. In some cases, the + TEI datatype includes additional usage constraints which cannot be enforced by existing + schema languages, although a TEI-compliant processor should attempt to validate them (see + further discussion in chapter ).

+

The following element is used to define a TEI datatype: + + +

+

TEI-defined datatypes may be grouped into those which define normalized values for numeric + quantities, probabilities, or temporal expressions, those which define various kinds of + shorthand codes or keys, and those which define pointers or links.

+

The following datatypes are used for attributes which are intended to hold normalized + values of various kinds. First, expressions of quantity or probability: + + + + + + +

+

Examples of attributes using the teidata.probability + datatype include degree on damage or certainty; examples of + teidata.numeric include quantity on members of + the att.measurement class or value on + numeric; examples of teidata.count include + cols on cell and table.

+ + + + + + + +

Next, the datatypes used for attributes which are intended to hold normalized dates or + times, durations, truth values, and language identifiers: + + + + + + + + + + +

+

Note that in each of these cases the values used are those + recommended by existing international standards: ISO 8601 as + profiled by XML Schema Part 2: Datatypes + Second Edition in the case of durations, times, and + date; W3C Schema datatypes in the case of truth values; and BCP + 47 in the case of language.

+ + + + + + + + + + +

The following datatypes have more specialized uses: + + + + + + + + + + + + +

+ + + + + + + + + + + + + +

By far the largest number of TEI attributes take values which are coded values or names of + some kind. These values may be constrained or defined in a number of different ways, each of + which is given a different name, as follows: + + + + + + + + + +

+

Attributes of type teidata.word, such as age on + person, are used to supply an identifier expressed as any kind of single token or + word. The TEI places a few constraints on the characters which may be used for this purpose: + only Unicode characters classified as letters, digits, punctuation characters, or symbols + can appear in an attribute value of this kind. Note in particular that such values cannot + include whitespace characters. Legal values include cholmondeley, été, + 1234, e_content, or xml:id, but not grand + wazoo. Attributes of this kind are sometimes used to associate (by co-reference) + elements of different types.

+

Where identifiers are defined externally, for example as part of a database or file system, + the inability to include whitespace or other special characters in a value may be + problematic. In other cases, it may also be simply more convenient to supply a short + sequence of natural language words including spaces as a single value. For these reasons, we + also provide a datatype teidata.text which does permit whitespace and indeed + any other Unicode character. Legal values include cholmondeley, été, + 1234, e-content, xml:id, and grand wazoo. This + datatype should be used with care since XML will not normalize whitespace characters within + it: for example the values n="a  b" (two spaces) and n="a   b" (three + spaces) would be considered distinct. This case should be distinguished from that of an + attribute permitting multiple values, each of which may be separated by whitespace which + will be normalized (see further ).

+

Attributes of type teidata.name are similar to those of type + teidata.word, but with the additional constraint that they + must be legal XML identifiers, as defined by the XML 1.0 specification, or successors. + Hence, they may not begin with digits or punctuation characters. Legal identifiers include + cholmondeley, été, e_content, or xml:id, but + not grand wazoo or 1234. Attributes of this kind are typically used to + represent XML element or attribute names.

+

Attributes of type teidata.xmlName are similar to those of + type teidata.name, but with the + additional constraint that they must not contain a colon + character (:, U+003A). Thus attributes of + this kind are used to represent XML element or attribute names + that do not have a namespace prefix.

+

Attributes of type teidata.prefix, such as ident + of prefixDef, are restricted to strings that form legal + URI prefixes.Technically the + specification permits the 26 uppercase letters + A-Z; however, since the canonical + form is lowercase and documents that specify schemes must do so + with lowercase letters, the TEI teidata.prefix datatype does not permit + uppercase letters. Examples of valid values are + http, https, tn3270, + xmlrpc.beep, and view-source.

+

Attributes of type teidata.enumerated, such as + new on shift or evidence supplied by att.editLike, have the same definition as teidata.word above, with the added constraint that the word supplied is taken + from a specific list of possibilities. In each case, the element or class specification + which includes the definition for the attribute will also contain a list of possible values, + together with a prose description of their intended significance. This list may be open (in + which case the list is advisory), or closed (in which case it determines the range of legal + values). In this latter case, the datatype will not be teidata.enumerated, but an explicit list of the possible values.

+ + + + + + + + + + +

An attribute may, of course, take more than one value of a given type, for example a list + of pointer values, or a list of words. In the TEI scheme, this information is regarded as a + property of the datatype element used to document the attribute in question rather + than as a distinct datatype, and is provided by the + minOccurs or maxOccurs attribute. See further .

+

In a small number of cases, an attribute may take a value of either one datatype or + another. These cases are considered as distinct datatypes: + + + + +

+ + + + + +
+
+
+ The TEI Infrastructure Module +

The tei module defined by this chapter is a required component + of any TEI schema. It provides declarations for all datatypes, and initial declarations for + the attribute classes, model classes, and macros used by other modules in the TEI scheme. Its + components are listed below in alphabetical order: + + TEI Infrastructure + Declarations for classes, datatypes, and macros available to all TEI modules + Infrastructure de la TEI + 所有TEI模組可用的元素集、資料類型、巨集指令之宣告 + Dichiarazione di classi, tipi di dati (datatype)e macro disponibili in tutti i moduli TEI + Declaraçoes de classes, tipos de dados, e macros disponíveis em todos os módulos TEI + 全TEIモジュールで使用可能なデータ型，クラス，マクロ。 + +

+

The order in which declarations are made within the infrastructure module is critical, since + several class declarations refer to others, which must therefore precede them. Other + constraints on the order of declarations derive from the way in which the modularity of the + TEI scheme is implemented in different schema languages. The XML DTD fragment implementing + this TEI module makes extensive use of parameter entities and marked + sections to effect a kind of conditional construction; the RELAX NG schema fragment + similarly predeclares a number of patterns with null (notAllowed) values. + These issues are further discussed in chapter .

+
+
diff --git a/P5/Source/Guidelines/fr/TC-CriticalApparatus.xml b/P5/Source/Guidelines/fr/TC-CriticalApparatus.xml deleted file mode 120000 index 2d8c114e35..0000000000 --- a/P5/Source/Guidelines/fr/TC-CriticalApparatus.xml +++ /dev/null @@ -1 +0,0 @@ -../en/./TC-CriticalApparatus.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/TC-CriticalApparatus.xml b/P5/Source/Guidelines/fr/TC-CriticalApparatus.xml new file mode 100644 index 0000000000..d803b421f1 --- /dev/null +++ b/P5/Source/Guidelines/fr/TC-CriticalApparatus.xml @@ -0,0 +1,1239 @@ + + + + +
+ Critical Apparatus +

Scholarly editions of texts, especially texts of great antiquity or importance, often record + some or all of the known variations among different witnesses to the text. + Witnesses to a text may include authorial or other manuscripts, printed editions of the work, + early translations, or quotations of a work in other texts. Information concerning variant + readings of a text may be accumulated in highly structured form in a critical apparatus of + variants. This chapter defines a module for use in encoding such an apparatus of variants, which + may be used in conjunction with any of the modules defined in these Guidelines. It also defines + an element class which provides extra attributes for some elements of the core tag set when this + module is selected. In printed critical editions, the apparatus takes the form of highly-compressed + notes at the bottom of each page. TEI’s critical apparatus module allows variation to be encoded + so that such notes may be generated, but it also models the variation so that, for example, + interactive editions in which readers can choose which witness readings to display are possible.

+ +

Information about variant readings (whether or not represented by a critical apparatus in the + source text) may be recorded in a series of apparatus entries, each entry + documenting one variation, or set of readings, in the text. Elements for the + apparatus entry and readings, and for the documentation of the witnesses whose readings are + included in the apparatus, are described in section . Special tags for + fragmentary witnesses are described in section . The available methods + for embedding the apparatus in the rest of the text, or for linking an external apparatus to the + text of the edition, are described in section . Finally, several extra + attributes for some tags of the core tag set, made available when the additional tag set for + text criticism is selected, are documented in section .

+ +

Scholarly practice in representing critical editions differs widely across disciplines, time + periods, and languages. The TEI does not make any recommendations as to which text-critical + methods are best suited to any given text. Editors will wish to consider questions such as: + + What source documents will be used? Are there many witnesses, few, or one? Are the + sources relatively close copies or not? + Will there be a single base text? Or will witnesses be separately + transcribed? + If a single base text will be used, will it be that of a particular witness, or will the + editor attempt to reconstruct an ideal or original text? + Will each reading in an apparatus entry record every attestation (a positive + apparatus), or merely witnesses that deviate from the base text (a negative + apparatus)? + Will the readings of most or all witnesses be represented in the apparatus, or only a + selection the editor deems relevant? + What level of variation will require distinguishing one witness reading from another? + For example, will the editor consider an abbreviated word in a witness as agreeing with the + base text, or not? + Will conjectures (variant readings suggested by an editor) be treated differently than + readings found in witnesses? + Will there be a need to distinguish different types of variation, for example + orthographic vs. morphological or lexical variants? +

+ +

Different editorial methodologies will produce different answers to these questions, and those + answers may influence choices of markup used in the edition. For example, if there will be + multiple witness transcriptions and a single apparatus, then the double + end-point attachment method may be the best choice of apparatus linking style. The parallel segmentation method may present several advantages to editors + producing an edition with a single base text. Editors of single-source editions may care to note + material aspects of the text (such as damage or unclear text). On the other + hand, editors attempting to synthesize an ideal or original text from many witnesses may feel + little need to represent the material aspects of individual witnesses. Editors wishing to + distinguish witness readings from conjectures by modern editors may wish to use wit + to indicate the former and source for the latter. Differences in types of variation + might be marked using type or ana on the rdg element.

+ +

Many examples given in this chapter refer to the following texts of the opening (usually just + line 1) of Chaucer's Wife of Bath's Prologue, as it appears in each of the four + different manuscripts + Ellesmere, Huntingdon Library 26.C.9 () + + Hengwrt, National Library of Wales, Aberystwyth, Peniarth 392D () + + British Library Lansdowne 851 () + + Bodleian Library Rawlinson Poetic 149 () + + +

+ +
+ The Apparatus Entry, Readings, and Witnesses +

This section introduces the fundamental markup methods used to encode textual variations: + + the app element for entries in the critical apparatus: see section . + elements for identifying individual readings: see section . + ways of grouping readings together: see section . + methods of identifying which witnesses support a particular reading, and for + describing the witnesses included in the apparatus: see section . + elements for indicating which portions of a text are covered by fragmentary witnesses: + see section . +

+

The app element is in one sense a more sophisticated and complex version of the + choice element introduced in as a way of marking points + where the encoding of a passage in a single source may be carried out in more than one way. + Unlike choice, however, the app element allows for the representation of + many different versions of the same passage taken from different sources.

+ +
+ The Apparatus Entry +

Individual textual variations are encoded using the app element, which groups + together all the readings constituting the variation. The identification of discrete textual + variations or apparatus entries is not a purely mechanical process; different editors will + group readings differently. No rules are given here as to how to collect readings into + apparatus entries.

+

The individual apparatus entry is encoded with the app element: + +

+

The attributes loc, from, and to, are used to link the + apparatus entry to the base text, if present. In such cases, several methods may be used for + such linkage, each involving a slightly different usage for these attributes. Linkage + between text and apparatus is described below in section . For the + use of the app element without a base text, see .

+

Each app element usually comprises one or more readings, which in turn are encoded using + the rdg or other elements, as described in the next section. A very simple partial + apparatus for the first line of the Wife of Bath's Prologue might take a form + something like this: + + Experience though noon Auctoritee + Experiment thouh noon Auctoritee + Eryment though none auctorite + + Of course, in practice the apparatus will be somewhat more complex. Specifically, it may be + desired to record more obviously that manuscripts El and La agree on the words noon + Auctoritee, to indicate a preference for one reading, etc. The following sections on + readings, subvariation, and witness information describe some of the more important + complications which can arise.

+ +
+
+ Readings +

Individual readings are the crucial elements in any critical apparatus of variants. The + following elements should be used to tag individual readings within an apparatus entry: + + + N.B. the term lemma is used here in the text-critical sense of + the reading accepted as that of the original or of the base text. This sense + differs from that in which the word is used elsewhere in the Guidelines, for example as in + the attribute lemma where the intended sense is the root form of an inflected + word, or the heading of an entry in a reference book, especially a dictionary. +

+

In recording readings within an apparatus entry, the rdg element should always be + used; each app usually contains at least one rdg, though it may contain only + notes.

+

The lem element may also be used to record the base text of the source edition, + to mark the readings of a base witness, to indicate the preference of an editor or encoder + for a particular reading, or (e.g. in the case of an external apparatus) to indicate + precisely to which portion of the main text the variation applies. Those who prefer to work + without the notion of a base text or who are not using the parallel segmentation method + may prefer not to use it at all. How it is used depends in part on the method chosen for + linking the apparatus to the text; for more information, see section .

+

Readings may be encoded individually, or grouped for clarity using the rdgGrp + element described in section .

+

As members of the attribute class att.textCritical, both of these elements + inherit the following attributes: . + rdg (but not rdgGrp) is also a member of att.witnessed: + These elements also inherit the following attributes from the + att.global.responsibility class: + + As elsewhere, these attributes may be used to indicate the person responsible + for the editorial decision being recorded, and also the degree of certainty associated with + that decision by the person carrying out the encoding.

+

The wit attribute identifies the witnesses which have the reading in question. + It is required if the apparatus gathers together readings from different witnesses, but may + be omitted in an apparatus recording the readings of only one witness, e.g. substitutions, + divergent opinions on what is in the witness or on how to expand abbreviations, etc. Even in + such a one-witness apparatus, however, the wit attribute may still be useful when + it is desired to record the occurrence of a particular reading in some other witness. For + other methods of identifying the witnesses to a reading, see section .

+

The type attribute allows the encoder to classify readings in any convenient + way, for example as substantive variants of the lemma: + + Experience + Experiment + Eryment + + or as orthographic variants: + + though + thouh +

+

The varSeq and cause attributes may be used to convey information on + the sequence and cause of variation. In the following apparatus fragment, the reading + Eryment is tagged as sequential to (derived from) the reading + Experiment, and the cause is given as loss of the abbreviation for + per. + + Experiment + Eryment +

+

If a manuscript is written in several hands, and it is desired to report which hand wrote a + particular reading, the hand attribute should be used. For example, in the Munich + manuscript containing the Carmina Burana, the word + alle has been changed to allen: Swaz hi gât umbe +daz sint alle megede, +die wellent ân man + + + alle + allen + +disen sumer gân. + + + +

+

Similarly, if a witness is hard to decipher, it may be desired to indicate responsibility + for the claim that a particular reading is supported by a particular witness. In line 2212a + of Beowulf, for example, the manuscript is read in different ways by + different scholars; the editor Klaeber prints one text, using parentheses to indicate his + expansion, and records in the apparatus two different accounts of the manuscript reading, by + Zupitza and Chambers:For the sake of legibility in the example, long + marks over vowels are omitted. + se ðe on + + hea(um) h(æþ)e + heaðo hlæwe + heaum hope + +hord beweotode, +

+

Because the hand attribute indicates a particular manuscript hand, it is intelligible + only on a reading from a single witness. If an encoder wishes to indicate that a particular + reading from a list in wit is in a particular hand, the witDetail element + should be used; see section .

+

Where there is a greater weight of editorial discussion and interpretation than can + conveniently be expressed through the attributes provided on these elements (for example + where the editor wishes to discuss how a section of text might be punctuated) this information + can be attached to the apparatus in a note.

+

The note element may also be used to record the specific wording of notes in the + apparatus of the source edition, as here in a transcription of Friedrich Klaeber's note on + Beowulf 2207a: syððan Beowulfe +Fol. 179a beowulfe. + Folio 179, with the last page (Fol. 198b), is the worst part of the + entire MS. It has been freshened up by a later hand, but not always + correctly. Information on doubtful readings is in the notes of + Zupitza and Chambers. +brade rice + + Notes providing details of + the reading of one particular witness should be encoded using the specialized + witDetail element described in section .

+

Encoders should be aware of the distinct fields of use of the attribute values + wit, hand, and source. Broadly, wit identifies + the physical entity in which the reading is found (manuscript, clay tablet, papyrus, printed + edition); hand refers to the agent responsible for inscribing that reading in + that physical entity (scribe, author, inscriber, hand 1, hand 2); source indicates + the scholar responsible for asserting the existence of that reading in that physical entity. + In some cases, the categories may blur: a scholar may produce an edition introducing + readings for which he or she is responsible; that edition may itself become a witness in a + later critical apparatus. Thus, readings introduced as corrections in the earlier edition + will be seen in the later apparatus as witnessed by the earlier edition. As observed in the + discussion concerning the discrimination of hand and resp in + transcription of primary sources in section , the division of layers of + responsibility through various scholars for particular aspects of a particular reading may + require the more complex mechanisms for assigning responsibility described in chapter .

+ +
+
+ Indicating Subvariation in Apparatus Entries +

The rdgGrp element may be used to group readings, either because they have + identical values on one or more attributes, or because they are seen as forming a + self-contained variant sequence, or for some other reason. This grouping of readings is + entirely optional: no such grouping of readings is required. + +

+

The rdgGrp element is a member of class att.textCritical and therefore can carry the type, + cause, varSeq, hand, and resp attributes + described in the preceding section. When values for any of these attributes are given on a + rdgGrp element, the values given are inherited by the rdg or + lem elements nested within the reading group, unless overridden by a new + specification on the individual reading element.

+

To indicate that both Hg and La vary only orthographically from the lemma, one might tag + both readings rdg type='orthographic', as shown in the preceding section. This + fact can be expressed more perspicuously, however, by grouping their readings into a + rdgGrp, thus: + + though + + thogh + thouh + +

+

Similarly, rdgGrp may be used to organize the substantive variants of an apparatus + entry. Editors may need to indicate that each of a group of witnesses may be taken as all + supporting a particular reading, even though there may be variation concerning the exact + form of that reading in, or the degree of support offered by, those witnesses. For example: + one may identify three substantive variants on the first word of Chaucer's Wife of + Bath's Prologue in the manuscripts: these might be expressed in regularized + spelling as Experience, Experiment, and + Eriment. In fact, the manuscripts display many different spellings + of these words, and a scholar may wish both to show that the manuscripts have all these + variant spellings and that these variant spellings actually support only the three + regularized spelling forms. One may term these variant spellings as + subvariants of the regularized spelling forms.

+

This subvariation can be expressed within an app element by gathering the readings + into three groups according to the normalized form of their reading. All the readings within + each group may be accounted subvariants of the main reading for the group, which may be + indicated by tagging it as a lem element or as rdg type='groupBase'.

+

In this example, the different subvariants on Experience, + Experiment, and Eriment are held within + three rdgGrp elements nested within the enclosing app element: + + + Experience + Experiens + + + Experiment + Eximent + + + Eriment + Eryment + + + From this, one may deduce that the regularized reading Experience is + supported by all three manuscripts El Hg Ha4, although the spelling differs in Ha4, and that + the regularized reading Eriment is supported by Ra2, even though the + form differs in that manuscript. Accordingly, an application which recognizes that these + apparatus entries show subvariation may then assign all the witnesses instanced as attesting + the sub-variants on that lemma as actually supporting the reading of the lemma itself at a + higher level of classification. Thus, Ha4 here supports the reading + Experience found in El and Hg, even though it is spelt slightly + differently in Ha4.

+

Reading groups may nest recursively, so that variants can be classified to any desired + depth. Because apparatus entries may also nest, the app element might also be used + to group readings in the same way. The example above is substantially identical to the + following, which uses app instead of rdgGrp: + + + + Experience + Experiens + + + + + Experiment + Eximent + + + + + Eriment + Eryment + + + + This expresses even more clearly than the previous encoding of this material that at the + highest level of classification (apparatus entry A1), this variation has three normalized + readings, and that the first of these is supported by manuscripts El, Hg, and Ha4; the + second by Cp, Ld1, and La; and the third by Ra2. Some encoders may find the use of nested + apparatus entries less intuitive than the use of reading groups, however, so both methods of + classifying the readings of a variation are allowed.

+

Reading groups may also be used to bring together variants which form an apparent + developmental sequence, and to make clear that other readings are not part of that sequence, + as in the following example, which makes clear that the variant sequence + experiment to eriment says nothing about the + relative priority of experiment and + experience: + + + Experience + Experiens + + + + Experiment + Eximent + + + Eriment + Eryment + + +

+ +
+
+ Witness Information +

A given reading is associated with the set of witnesses attesting it by listing the + witnesses in the wit attribute on the rdg or lem element. Special + mechanisms, described in the following sections, are needed to associate annotation on a reading + with one specific witness among several (section ), to transcribe + witness information verbatim from a source edition (section ), and to + identify the formal lists of witnesses typically provided in the front matter of critical + editions (section ).

+
+ Witness Detail Information +

When it is desired to give additional information about the reading of a particular witness + or witnesses, such as noting that it appears in the margin or was corrected + for the reading, that information may be given in a witDetail element. This is a + specialized note, which can be linked to both a reading and to one or more of the + witnesses for that reading. The link to the reading may be inferred from witDetail's + position or made explicit by the target attribute which witDetail inherits + from the attribute class + att.pointing; the link to the witness, by the wit attribute. + + +

+

Because it annotates an attribute value, witDetail cannot be included in the text at the point of + attachment; without a target attribute, it refers to the closest preceding lem or rdg. + But if there is any ambiguity or if the witDetail refers to multiple readings, target must be + used to point to the reading(s) being annotated. To indicate that the + Ellesmere manuscript has an ornamental capital in the word + Experience, for example, one might write: + + Experience + Ornamental capital. + Experiens + + + This encoding makes clear that the ornamental capital mentioned is in the Ellesmere + manuscript, and not in Hengwrt or Ha4.

+

Like note, witDetail may be used to record the specific wording of + information in the source text, even when the information itself is captured in some more + formal way elsewhere. The example from the Carmina Burana above (section + ), for example, might be extended thus, to record the wording of + the note explaining that the variant reading adds n to the original + in a second hand: Swaz hi gât umbe +daz sint alle megede, +die wellent ân man + + + alle + allen + + n nachgetragen. + + +disen sumer gân. + + + +

+

Feature structures containing information about the text in a witness (whether retroversion, + regularization, or other) can also be linked to specific lem and rdg + instances. See chapter .

+ +
+
+ Witness Information in the Source +

Although witDetail provides a good way to annotate witness references in wit, lists + of sigla The Latin word siglum (sign), pl. + sigla denotes the abbreviation used in a critical apparatus to indicate a + particular witness. may be complex enough that it is impractical to use the combination of + wit and witDetail. + Moreover, in the transcription of printed critical editions, it may be desirable to retain for + future reference the exact form in which the source edition records the witnesses to a + particular reading; this is particularly important in cases of ambiguity in the + information, or uncertainty as to the correct interpretation. The wit element may + be used to transcribe such lists of witnesses to a particular reading. + + The wit list may appear following a rdg, rdgGrp, or + lem element in any apparatus entry. wit may be used in a way functionally equivalent + to wit if the sigla therein are wrapped in refs with target attributes + pointing to a predefined witness. For example + + Nondum + nundum + corr. G1 + + + which indicates that the reading nundum for nondum is to be found in MSS G (although it is + corrected to nondum in the primary hand) and P, might be written: + + Nondum + nundum + G(corr. G1)P + + + This is somewhat more verbose, but accomplishes the same goal. Because wit is more succinct, and because it makes + the automated verification of correct witness references easier, using wit (with witDetail when + needed) is almost always to be preferred. +

+ +
+
+ The Witness List +

A list of all identified witnesses should normally be supplied in the front matter of the + edition, or in the sourceDesc element of its header. This may be given either as + a simple bibliographic list, using the listBibl element described in + , or as a listWit element, which contains a series of + witness elements. Each witness element may contain a brief + characterization of the witness, given as one or more prose paragraphs. If more detailed + information about a manuscript witness is available, it should be represented using the + msDesc element provided by the msdescription + module; an msDesc may appear within a listBibl.

+

Whether information about a particular witness is supplied by means of a bibl, + msDesc, or witness element, a unique siglum for this source should + always be supplied, using the global xml:id attribute. This identifier can then + be used elsewhere to refer to this particular witness. + + + + + +

+

The minimal information provided by a witness list is thus the set of sigla for all the + witnesses named in the apparatus. For example, the witnesses referenced by the examples of + this chapter might simply be listed thus: + + + + + + + + + + + + + + + +

+

It is more helpful, however, for witness lists to be somewhat more informative: each + witness element should contain at least a brief prose description of the + witness, perhaps including a bibliographic citation, as in the following examples: + + Ellesmere, Huntingdon Library 26.C.9 + Hengwrt, National Library of Wales, + Aberystwyth, Peniarth 392D + Bodleian Library Rawlinson Poetic 149 +(see further ) + + As the last example shows, the witness description here may be complemented by a reference + to a full description of the manuscript supplied elsewhere, typically as the content of an + msDesc or bibl element. Alternatively, it may contain a whole + paragraph of commentary for each witness: + die sog. Kleine (oder alte) + Heidelberger Liederhandschrift. + Universitätsbibliothek Heidelberg col. pal. + germ. 357. Pergament, 45 Fll. 18,5 × 13,5 cm. + Wahrscheinlich die älteste der drei großen Hss. Sie + datiert aus dem 13. Jahrhundert, etwa um 1275. Ihre Sprache + weist ins Elsaß, evtl. nach Straßburg. Man geht wohl nicht + fehl, in ihr eine Sammlung aus dem Stadtpatriziat zu sehen + (Blank, [vgl. Lit. z. Hss. Bd. 2, + S. 39] S. 14). Sie enthält 34 namentlich + genannte Dichter. Zu den Vorzügen von A gehört, daß + sie kaum je bewußt geändert hat, so daß sie für + manche Dichter ... oft den besten Text liefert (so wohl mit + Recht v. Kraus). + Bezeichnung Lachmann + s für die von einer 2. Hand auf bl. 40–43 + geschriebenen Strophen der Hs. A. + die Weingartner (Stuttgarter) + Liederhandschrift. Württembergische + Landesbibliothek Stuttgart, HB XIII poetae germanici 1. + Pergament, 156 Bll. 15 × 11,5 cm; 25 teils ganzseitig, + teils halbseitige Miniaturen. Kaum vor 1306 in Konstanz + geschrieben. Sie enthält Lieder von 25 namentlich genannten + Dichtern. (Dazu kommen Gedichte von einigen ungenannten + bzw. unbekannten Dichtern, ein Marienlobpreis und eine + Minnelehre.) + + +

+

It would however generally be preferable to represent such detailed information using an + appropriately structured msDesc element, as discussed in chapter . Note also that if the witnesses being recorded are not manuscripts but + printed works, it may be preferable to document them using the standard bibl or + biblStruct elements described in , as in this example: + + +T. Kempis, De la imitació de Jesuchrist e del +menyspreu del món (trad. Miquel Peres); Barcelona, 1482, Pere +Posa. Editio princeps. +T. Kempis, Del menyspreu del món (trad. Miquel +Peres); València, 1491. +T. Kempis, Libre del menysprey del món e de la +imitació de nostre senyor Déu Jesucrist, (trad. Miquel Peres); +Barcelona, 1518, Carles Amorós. + + +

+

In text-critical work it is customary to refer to frequently occurring groups of + witnesses by means of a single common siglum. Such sigla may be documented as + pseudo-witnesses in their own right by including a nested witness list within the witness + list, which uses the siglum for the group as its identifier, and supplies a fuller name for + the group in its optional child head element, before listing the other witnesses + contained by the group. + For example, the Constant Group C of manuscripts comprising witnesses Cp, La, and S12, + might be represented as follows: + +Ellesmere, Huntingdon Library 26.C.9 + + + Constant Group C + Corpus Christi Oxford MS 198 + British Library Lansdowne 851 + British Library Sloane MS 1686 + + + That the reading Experiment occurs in all three manuscripts can now be + indicated simply as follows: Experiment

+

The more elaborate example below shows both multiple levels of nesting and a strategy for mapping + the the xml:id of the witness to the siglum which will be displayed to the reader of a derived visualisation: + Servius (Σ) = ΔΓ + + Δ + J = Metens. Bibl. mun. 292, s. IX + L = Leid. Bibl. der Rijksuniv. B.P.L. 52, s. VIII / IX + + Γ + θ + A = Caroliruh. Bad. Landesbibl. Aug. CXVI, s. IX2 (Reichenau); de codice A derivati: + + S = Sangall. Stiftsbibl. 861 + 862, s. IX / X + Guelf. = Guelf. HAB 2546 (44.23 Aug. fol.), s. XV + + + O = Oxon. Bodl. Laud lat. 117, s. XI2 + + τ + + Pa = Paris. BnF lat. 7959, s. IX (Tours) + Pc = Paris. BnF lat. 7961, s. X / XI + Q Flor. BML Plut. 45.14, s. IX + Lb = corrector cod. L (sup.) + + + γ + E = Escorial. Bibl. S. Lorenzo T.II.17, s. IX2 (Ital. septentrion.) + Pb Paris. BnF lat. 16236, s. X / XI + Y = Trident. Bib. com. 3388 (olim Vind. 72), s. + IX2 + M = Monac. Bay. Staatsbibl. Clm 6394, s. XI + + + σ + W = Guelf. HAB 2091, s. XIIIex. + N = Neap. Bibl. naz. lat. 5 (olim Vind. 27), s. + X1 + U = Berolin. Staatsbibl. lat. quart. 219, s. XII + + º classis codicum de Γ defluentium quibus lectiones faciliores in contextum contaminatione inferre valde placuit (= PaPcγσ in A. 9.1-10.190, 10.397-12.162; PaPcγU in A. 12.162-320; PaPcγ in A. 12.320-522); cf. praef. n. 30. + + + + Here we have a summary of the witnesses, with their sigla, used in an edition, as is generally + found in the conspectus siglorum in the front matter of a critical edition. + Families are indicated with Greek letters and manuscript witnesses with Latin letters. The siglum for + display is always contained in the abbr with type siglum child of each + witness, so it is always easy to retrieve the display siglum for a given identifier reference. +

+ + +

Situations commonly arise where there are many more or less fragmentary witnesses, such + that there may be quite distinct groups of witnesses for different parts of a text or + collection of texts. One may treat this with distinct listWit elements for each + different part. Alternatively, one may have a single listWit element at the + beginning of the file or in its header listing all the witnesses, partial and complete, + for the text, with the attestation of fragmentary witnesses indicated within the apparatus + by use of the witStart and witEnd elements described in section .

+

If a witness list is provided, it may be unnecessary to give, in each apparatus entry, an + exhaustive list of the witnesses which agree with the base text. An application program + can—in principle—compare the witnesses given for each variant found with those given in + the full list of witnesses, subtracting from this list all the witnesses not active at + this point (perhaps because of lacuna, or because they contain a variation on a different, + overlapping lemma) and thence calculate all the manuscripts agreeing with the base text. + In practice, encoders may find it less error-prone to list all witnesses explicitly in + each apparatus entry.

+ +
+
+
+ Fragmentary Witnesses +

If a witness is incomplete (whether a single fragment, a series of fragments, or a + relatively complete text with one or more lacunae), it is usually desirable to record + explicitly where its preserved portions begin and end. The following empty tags, which may + occur within any lem or rdg element, indicate the beginning or end of a + fragmentary witness or of a lacuna within a witness: + + + + + These elements constitute the class model.rdgPart, + members of which are permitted within the elements lem and rdg when the + module defined by this chapter is included in a schema.

+

Suppose a fragment of a manuscript X of the Wife of Bath's Prologue has a + physical lacuna, and the text of the manuscript begins with + auctorite. In an apparatus this might appear thus, distinguished from + the reading of other manuscripts by the presence of the lacunaEnd element: + + Auctoritee + auctorite + auctorite + + Alternatively, it may be clearer to record this as + + Auctoritee + auctorite + + since this shows more clearly that the lacuna and the reading of auctorite both + appear in witness X. In some cases, the apparatus in the source may commence recording the + readings for a particular witness without its being clear whether the previous absence of + readings for this witness is due to a lacuna, or to some other reason. The witStart + element may be used in this circumstance: + + Auctoritee + auctorite + auctorite +

+ + +
+
+
+ Linking the Apparatus to the Text +

Three different methods may be used to link a critical apparatus to the text: + the location-referenced method, + the double-end-point-attached method, and + the parallel segmentation method. +

+

Both the location-referenced and the double end-point methods may be used with either + in-line or external apparatus, the former dispersed within the + base text, the latter held in some separate location, within or outside the document containing the + base text. The parallel segmentation method may only be used for in-line apparatus.

+ + + +

Where an external apparatus is used, the listApp element + provides a useful means of grouping together a series of app elements of a specific type, + or from a particular source: + + + + + + listApp elements would normally appear in the back of + a document, but they may also be placed in any other convenient location.

+ +

Any document containing app elements requires a variantEncoding declaration + in the encodingDesc element of its TEI header, thus: + +

+ +
+ The Location-referenced Method +

The location-referenced method of encoding apparatus provides a convenient method for + encoding printed apparatus; in this method as in most printed editions, the apparatus is + linked to the base text by indicating explicitly only the block of text on which there is a + variant (noted usually by a canonical reference scheme, or by line number in the edition, + such as A 137 or Page 15 line 1).

+

If the location-referenced method is used for an apparatus stored externally to the base + text, the TEI header must have the declaration: +

+

In the body of the document, the base text (here El) will appear: + + +

+ The Prologe of the Wyves Tale of Bathe + Experience though noon Auctoritee + Were in this world ... +
+ +

+

Elsewhere in the document, or in a separate file, the apparatus will appear. On each + app element, the loc attribute should be specified to indicate where + the variant occurs in the base text. + + Experiment + Eryment +

+

If the same text is encoded using in-line storage, the apparatus is dispersed through the + base text block to which it refers. In this case, the location of the variant can be read + from the line in which it occurs. + + +Experience + + Experiment + Eryment + + though noon Auctoritee +Were in this world ...

+

Since the location is not required to be exact, the apparatus for a line might also appear + at the end of the line: + Experience though noon Auctoritee + + Experiment + Eryment + +Were in this world ...

+

When the apparatus is linked to the text by means of location references, as shown here, it + is not possible to find automatically the precise portion of text varied by the readings. In + order to show explicitly what portion of the base text is replaced by the variant readings, + the lem element may be used: + Experience though noon Auctoritee + + Experience + Experiment + Eryment + +Were in this world ... + Often the lemma will have no attributes, being simply the base text + reading and requiring no qualification, but it may optionally carry the normal + attributes, as shown here. Some text critics prefer to abbreviate or elide the lemma, in + order to save space or trouble; such practice is not forbidden by these Guidelines, but no + recommendations are made for conventions of abbreviating the lemma, whether abbreviation of + each word, or suppression of all but the first and last word, etc.

+

Where it is intended that the apparatus be complete enough to allow the reconstruction of + the witnesses (or at least of their non-orthographic variations), simple location-reference + methods are unlikely to be as successful as the other two methods, which allow the + unambiguous reconstruction of the lemma from the encoding.

+
+
+ The Double End-Point Attachment Method +

In the double end-point attachment method, the beginning and end of the lemma in the base + text are both explicitly indicated. It thus differs from the location-referenced method, in + which only the larger span of text containing the lemma is indicated. Double end-point + attachment permits unambiguous matching of each variant reading against its lemma. It or the + parallel-segmentation method should be used in all cases where this is desired, for example + where the apparatus is intended to enable full reconstruction of the text, or of the + substantives, of every witness.

+

When the double end-point attachment method is used, the from and to + attributes of the app element are used to indicate the beginning and ending points + of the reading in the base text: their values are identifiers which occur at the locations + in question. If no other markup is present there, the beginning and ending points should be + marked using the anchor element defined in chapter . In cases + where it is not possible to insert anchors within the base text (e.g. where the text is on a + read-only medium) the beginning and end of the lemma may be indicated by using the + indirect pointing mechanisms discussed in chapter . Explicit anchors are more likely to be reliable, and are therefore to be preferred.

+

The double end-point attachment method may be used with in-line or external apparatus. In + the latter case, the base text (here El) will appear with anchor elements inserted + at every place where a variant begins or ends (unless some element with an identifier + already begins or ends at that point): + + + +

The Prologe ... + Experience though noon Auctoritee + Were in this world ... +
+ + The apparatus will be separately encoded: + + Experiment + Eryment + + No anchor element is needed at the beginning of the line, since the from + attribute can use the identifier for the line as a whole; the lemma is assumed to run from + the beginning of the element indicated by the from attribute, to the end of that + indicated by the to attribute. If no value is given for to, the lemma + runs from the beginning to the end of the element indicated by the from + attribute.

+

When the apparatus is encoded in-line, it is dispersed through the base text. Only the + beginning of the lemma need be marked with an anchor, since the app is + inserted at the end of the lemma, and itself therefore marks the end of the lemma. + + +Experience + + Experiment + Eryment + + though noon Auctoritee +Were in this world ...

+

The lemma need not be repeated within the app element in this method, as it may be + extracted reliably from the base text. If an exhaustive list of witnesses is available, it + will also not be necessary to specify just which manuscripts agree with the base text to + enable reconstruction of witnesses. An application will be able to determine the manuscripts + that witness the base reading, by noting which witnesses are attested as having a variant + reading, and inferring the base text reading for all others after adjusting for fragmentary + witnesses and for witnesses carrying overlapping variant readings.

+

Alternatively, if it is desired to make an explicit record of the attestation of the base + text, the lem element may be embedded within app, carrying the witnesses + to the base. Thus + + Experience + Experiment + Eryment +

+

This method is designed to cope with overlapping lemmata. For example, + at line 117 of the Wife of Bath's Prologue, the manuscripts Hg (Hengwrt), El (Ellesmere), + and Ha4 (British Library Harleian 7334) read: + + And of so parfit wys a wight ywroght + + And for what profit was a wight ywroght + + And in what wise was a wight ywroght +

+

In this case, one might wish to record in what wise was in Ha4 as a + single variant for of so parfit wys in Hg, and was a + wight in El and Ha4 as a variant on wys a wight in Hg. + This method can readily cope with such difficult situations, typically found in large and + complex traditions: + And + of so parfit + wys + a wight + ywroght + + of so parfit wys + in what wise was + + + wys a wight + was a wight + + The parallel segmentation method, to be discussed next, cannot handle overlaps among + variants, and would require the individual variants to be split into pieces.

+

Because creation and interpretation of double end-point attachment apparatus will be + lengthy and difficult it is likely that they will usually be created and examined by + scholars only with mechanical assistance.

+
+
+ The Parallel Segmentation Method +

This method differs from the double end-point attachment method in that all variants at any + point of the text are expressed as variants on one another. In this method, no two + variations can overlap, although they may nest. The texts compared are divided into matching + segments all synchronized with one another. This permits direct comparison of any span of + text in any witness with that in any other witness. With a positive apparatus, it is + straightforward for an application to extract the full text of any one witness from the + apparatus.Some care must be taken with this approach, as a derived + view of a witness may not be a complete and accurate transcription of that witness. It is + more likely to be the base text with all readings from that witness applied.

+

This method will (by definition) always be satisfactory when there are just two texts for + comparison (assuming they are in the same language and script). It will however be less + convenient for textual traditions where establishing a base text with variations from + it is not a satisfactory goal for the edition, or in some cases where every detail of + variation needs to be modeled.

+

In the parallel segmentation method, each segment of text on which there is variation is + marked by an app element. If there is a preferred (or base) reading it is tagged + with lem; each reading is given in a rdg element: + + + Experience + Experiment + Eryment though noon Auctoritee + Were in this world ...

+

This method cannot be used with external apparatus: it must be used in-line. Note that + apparatus encoded with this method may be translated into the double end-point attachment + method and back without loss of information. Where double-end-point-attachment encodings + have no overlapping lemmata, translation of these to the parallel segmentation encoding and + back will also be possible without loss of information.

+ +

As noted, apparatus entries may nest in this method: if an imaginary fifth manuscript of + the text read Auctoritee, though none experience, the variation on + the individual words of the line would nest within that for the line as a whole: + + Auctoritee, though none experience + + + Experience + Experiment + Eryment + + + though + thogh + thouh + + + noon Auctorite + none auctorite + + + +

+

Parallel segmentation cannot, however, deal very gracefully with variants which overlap + without nesting: such variants must be broken up into pieces in order to keep all witnesses + synchronized.

+
+ + + +
+ Other Linking Methods +

When an apparatus is provided it does not need to be given at the location in the + transcription where the variation, emendation, attribution, or other apparatus observation + occurs. Instead it may be stored in a separate place in the same file, or indeed in another + file, and point to the location at which it is meant to be used. Storing apparatus entries + separately can be beneficial when encoding multiple competing, potentially overlapping, + interpretations of the same point in the source texts.

+

The location-referenced method can be used to point a position in a text using the + loc attribute and a canonical reference that is understood and documented in + the context of the file where it is used. Where possible it is recommended that other + methods use the from attribute to point to an xml:id attribute on an + anchor or other element at the location where the apparatus observation takes + place. The contents of an element pointed to are understood to be equivalent to a + lem if none exists in the app, and if a lem does exist this + should replace any content.

+

The from attribute is a teidata.pointer datatype and + thus contains a URI as a value. This means that it can point directly to an + xml:id, an xml:id in another local file, or indeed a file identified + by any URL or URN. + + Experience though noon Auctoritee + + + + + Experiment + Eryment + + + This could also be encoded as: + + though noon Auctoritee + + + + + Experience + Experiment + Eryment + + + However, this should be considered more fragile since a full reading of the lem is + not provided in the source file.

+

In addition, URLs can contain XPointer schemes including xpath(), range(), and + string-range() which can be used in providing the location of an app that is stored + separately from the text to which it applies. Both from and to can be + used, as in the double end-point attachment method, to identify the starting and ending + location for an apparatus using XPointer schemes described in section + to more precisely identify this location where beneficial. + + Experience though noon Auctoritee + + + + + Experience + Experiment + Eryment + + +

+

If only the from attribute is provided then it should be understood that this + supplies the location of the textual variance that the apparatus documents. If the + from attribute contains an XPointer scheme that identifies a range of text (or + elements) then this is understood to record the starting and ending of the range as in the + double end-point attachment method. In such a case a @to attribute is unnecessary.

+
+ +
+ + + + +
+ Using Apparatus Elements in Transcriptions +

It is often desirable to record different transcriptions of one stretch of text. These + variant transcriptions may be grouped within a single app element. An application may + then construct different views of the transcription by extraction of the + appropriate variant readings from the apparatus elements embedded in the transcription.

+

For example, alternative expansions can be recorded in several different expan + elements, all grouped within an app element. Consider, for example, the three + different transcriptions given below of line 105 of the Hengwrt manuscript of Chaucer's + The Wife of Bath's Prologue. The last word of the line Virginite + is grete perfection is written perfectio followed by two + minims over which a bar has been drawn, which has been read in different ways by different + scholars. The first transcription, by Elizabeth Solopova, represents the two minims with bar + above as a special composite character using the g element. This transcription notes + this as a mark of abbreviation but gives no expansion for it. A second transcriber, F. J. + Furnivall, regards the bar as an abbreviation of u, and therefore reads + the two minims as an n. A third transcriber, P. G. Ruggiers, regards + the bar as an abbreviation of n, reading the minims as + u. This information may be held within an app structure, as + follows: + Virginite is grete + + perfectio + perfectioun + perfectioun + + This example uses special purpose elements am and ex used to represent + abbreviation marks and editorial expansion respectively; these elements are provided by the + transcr module documented in chapter , which + should be consulted for further discussion of methods of representing multiple readings of a + source. +

+

Editorial notes may also be attached to app structures within transcriptions. Here, + editorial preference for Ruggiers' expansion and an explanation of that preference is given: + Virginite is grete + + perfecti + perfectioun + perfectioun + + +Furnivall's expansion implies that the bar + is an abbreviation for 'u'. There are no certain instances of + this mark as an abbreviation for 'u' in these manuscripts and it is + widely used as an abbreviation for 'n'. Ruggiers' expansion is to + be accepted. +

+

In most cases, elements used to indicate features of a primary textual source may be + represented within an app structure simply by nesting them within its readings, just + as the am and ex elements are nested within the rdg elements in the + example just given. However, in cases where the tagged feature extends across a span of text + which might itself contain variant readings which it is desired to represent by app + structures, some adaptation of the tagging may be necessary. For example, a span of text may + be marked in the transcription of the primary source as a single deletion but it may be + desirable to represent just a few words from this source as individual deletions within the + context of a critical apparatus drawing together readings from this and several other + witnesses. In this case, the tagging of the span of words as one deletion may need to be + decomposed into a series of one-word deletions for encoding within the apparatus. If it is + important to record the fact that all were deleted by the same act, the markup may use the + join element or the next and prev attributes defined by + chapter .

+
+ +
+ Strategies for Encoding Variation +

Textual variation may manifest itself in many ways. Variation most frequently occurs at the phrase level, + but is also common at higher structural levels, such as the verse line, paragraph, or chapter. When + these structures are involved, some care must be taken in their encoding to ensure that TEI's + Abstract Model is not being broken. It would be an error, for example, to have a div in + the lem, but a p in a rdg inside the same apparatus entry, because these + structures cannot occur at the same level. Similarly, it is an error if the contents of an + apparatus entry place a p inside another p or an l inside an l.

+

Phenomena such as omissions and transpositions in witnesses will require some encoding strategies + that differ from those in the examples above. An editor wishing to signal an omission in one witness + should encode the omission using an empty rdg, thus: + + Hypsipyle uacuo constitit in thalamo: + + + Notice that in this example, the variation occurs at the unit of the verse line. The scribe of MS J has + skipped line 18 (probably by mistake) because, like line 19, it begins with the name "Hypsipyle." If a witness + contains an interpolation that the editor does not wish to show in the base text, an empty + lem should be used, in the same fashion. +

+

Transpositions are harder to encode, because they involve variation that occurs in different + locations. A single app will therefore not be sufficient, and the variants must be linked. + For example, in his edition of Propertius 1.16, Housman printed lines 25-6 after line 32, Heyworth prints + them in place. We might encode Heyworth's edition, which records Housman's conjecture despite disagreeing + with it, as follows: + + + desine iam reuocare tuis periuria verbis, + Cynthia, et oblitos parce movere deos; + + and then, after line 32: + + + + + + Housman put these lines after 32. + + Note that both apps are linked via the exclude attribute, because they are mutually + exclusive: if one reading is chosen for display in a reading interface, for example, the other must + disappear and vice versa. To avoid repetition, the second pair of lines can make use of the copyOf + attribute. If they were both transposed and somewhat different, then both sets should be written in full. +

+

Apparatus entries may nest when there is variation at both higher and lower structural levels, e.g.: + + + utetac perhapsquam formosa nouo quae parat ire uiro. + atet non sic, Ithaci digressu motaimmota, Calypso + desertis olim fleuerat aequoribus: + multos illa dies incomptis maesta capillis + + omits lines 8-11 because of homoeoteleuton. + + Here, MS C omits lines 8-11, but there are variations the editor wishes to record in the other witnesses + which do have these lines. Therefore, an outer app gives the lines in the lem and the + omission in a rdg. Further variation is encoded for lines 8 and 9 using nested apps. +

+
+ +
+ Module for Critical Apparatus +

The module described in this chapter makes available the following components: + + Text Criticism + Critical Apparatus + Apparat critique + 學術編輯註解 + Apparato critico + Critical Apparatus + 校勘モジュール + + + The selection and combination of modules to form a TEI schema is + described in .

+ + + + + + + + + + + + + + + +
+ +
diff --git a/P5/Source/Guidelines/fr/TD-DocumentationElements.xml b/P5/Source/Guidelines/fr/TD-DocumentationElements.xml deleted file mode 120000 index 301d781642..0000000000 --- a/P5/Source/Guidelines/fr/TD-DocumentationElements.xml +++ /dev/null @@ -1 +0,0 @@ -../en/./TD-DocumentationElements.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/TD-DocumentationElements.xml b/P5/Source/Guidelines/fr/TD-DocumentationElements.xml new file mode 100644 index 0000000000..36910d7800 --- /dev/null +++ b/P5/Source/Guidelines/fr/TD-DocumentationElements.xml @@ -0,0 +1,2164 @@ + + + + +
+ Documentation Elements +

This chapter describes a module which may be used for the documentation of the XML elements and element + classes which make up any markup scheme, in particular that described by the TEI Guidelines, and also for + the automatic generation of schemas or DTDs conforming to that documentation. It should be used also by + those wishing to customize or modify these Guidelines in a conformant manner, as further described in + chapters and and may also be useful in the documentation of any + other comparable encoding scheme, even though it contains some aspects which are specific to the TEI and + may not be generally applicable.

+

An overview of the kind of processing environment envisaged for the module described by this chapter may + be helpful. In the remainder of this chapter we refer to software which provides such a processing + environment as an ODD processor.ODD is short for One Document Does it + all, and was the name invented by the original TEI Editors for the predecessor of the system + currently used for this purpose. See further and . Like any other piece of XML software, an ODD processor may be instantiated in many ways: the + current system uses a number of XSLT stylesheets which are freely available from the TEI, but this + specification makes no particular assumptions about the tools which will be used to provide an ODD + processing environment.

+

As the name suggests, an ODD processor uses a single XML document to generate multiple outputs. These + outputs will include: + formal reference documentation for elements, attributes, element classes, patterns, etc. such as + those provided in below; + detailed descriptive documentation, embedding some parts of the formal reference documentation, + such as the tag description lists provided in this and other chapters of these Guidelines; + declarative code for one or more XML schema languages, such as RELAX NG, W3C Schema, ISO + Schematron, or DTD. + + +

+

The input required to generate these outputs consists of running prose, and special purpose elements + documenting the components (elements, classes, etc.) which are to be declared in the chosen schema + language. All of this input is encoded in XML using elements defined in this chapter. In order to support + more than one schema language, these elements constitute a comparatively high-level model which can then + be mapped by an ODD processor to the specific constructs appropriate for the schema language in use. + Although some modern schema languages such as RELAX NG or W3C Schema natively support self-documentary + features of this kind, we have chosen to retain the ODD model, if only for reasons of compatibility with + earlier versions of these Guidelines. For reasons of backwards compatibility, the ISO standard XML schema + language RELAX NG () may be used as a means of declaring content + models and datatypes, but it is also possible to express content models using native TEI XML constructs. + We also use the ISO Schematron language to define additional constraints beyond those expressed in the + content model, as further discussed in below.

+

In the TEI system, a schema is built by combining element and attribute declarations, more + or less as required. Each element is documented by an appropriate specification element and + has an identifier unique across the whole TEI scheme. For convenience, these specifications are grouped + into a number of discrete modules, which can also be combined more or less as required. Each + major chapter of these Guidelines defines a distinct module. Each module declares a number of + elements specific to that module, and may also populate particular classes. + All classes are available globally, irrespective of the module in which they are declared; particular + modules extend the meaning of a class by adding elements or attributes to it. Wherever possible, element + content models are defined in terms of classes rather than in terms of specific elements. Modules can also + declare particular patterns, which act as short-cuts for commonly used content models or + class references.

+

In the present chapter, we discuss the components needed to support this system. In addition, section + discusses some general purpose elements which may be useful in any kind of + technical documentation, wherever there is need to talk about technical features of an XML encoding such + as element names and attributes. Section discusses the elements which are used + to document XML modules and their high-level components. Section + discusses the elements which document XML elements and their attributes, element classes, and generic + patterns or macros. Finally, section provides a summary overview of the elements + provided by this module.

+
+ Phrase Level Documentary Elements +
+ Phrase Level Terms +

In any kind of technical documentation, the following phrase-level elements may be found useful for + marking up strings of text which need to be distinguished from the running text because they come from + some formal language: + + + Like other phrase-level elements used to indicate the semantics of a typographically + distinct string, these are members of the model.emphLike class. They are + available anywhere that running prose is permitted when the module defined by this chapter is included + in a schema.

+

The code and ident elements are intended for use when citing brief passages in some + formal language such as a programming language, as in the following example: + +

If the variable z has a value of zero, a statement such as x=y/z will + usually cause a fatal error.

+ +

+

If the cited phrase is a mathematical or chemical formula, the more specific formula element + defined by the figures module () may be more + appropriate.

+

A further group of similar phrase-level elements is also defined for the special case of representing + parts of an XML document: + + + + + These elements constitute the model.phrase.xml class, which is + also a subclass of model.phrase. They are also available anywhere that + running prose is permitted when the module defined by this chapter is included in a schema.

+

As an example of the recommended use of these elements, we quote from an imaginary TEI working paper: +

The gi element is used to tag element + names when they appear in the text; the tag element however is used to show how a tag as + such might appear. So one might talk of an occurrence of the blort element which had been + tagged blort type='runcible'. The type attribute may take any name token as + value; the default value is spqr, in memory of its creator.

+

+

Within technical documentation, it is also often necessary to provide more extended examples of usage + or to present passages of markup for discussion. The following special elements are provided for these + purposes: + + + +

+

Like the code element, the egXML element is used to mark strings of formal code, or + passages of XML markup. The eg element may be used to enclose any kind of example, which will + typically be rendered as a distinct block, possibly using particular formatting conventions, when the + document is processed. It is a specialized form of the more general q element provided by the + TEI core module. In documents containing examples of XML markup, the egXML element should be + used for preference, as further discussed below in , since the content of this + element can be checked for well-formedness.

+

These elements are added to the class model.egLike when this module is + included in a schema. That class is a part of the general model.inter + class, thus permitting eg or egXML elements to appear either within or between + paragraph-like elements.

+
+
+ Element and Attribute Descriptions +

Within the body of a document using this module, the following elements may be used to reference + parts of the specification elements discussed in section , in particular + the brief prose descriptions these provide for elements and attributes. + + + +

+

TEI practice recommends that a specList listing the elements under discussion introduce each + subsection of a module's documentation. The source for the present section, for example, begins as + follows: + +

+ Element and Attribute Descriptions +

Within the body of a document using this module, the … the brief prose descriptions these provide for elements and attributes. + + + +

+

TEI practice recommends that a specList listing the elements under …

+ +
+ +

+

When formatting the ptr element in this example, an ODD processor might simply generate the + section number and title of the section referred to, perhaps additionally inserting a link to the + section. In a similar way, when processing the specDesc elements, an ODD processor may + recover relevant details of the elements being specified (specList and specDesc in + this case) from their associated declaration elements: typically, the details recovered will include a + brief description of the element and its attributes. These, and other data, will be stored in a + specification element elsewhere within the current document, or they may be supplied by the ODD + processor in some other way, for example from a database. For this reason, the link to the required + specification element is always made using a TEI-defined key rather than an XML IDREF value. The ODD + processor uses this key as a means of accessing the specification element required. There is no + requirement that this be performed using the XML ID/IDREF mechanism, but there is an assumption that + the identifier be unique.

+

A specDesc generates in the documentation the identifier, and also the contents of the + desc child of whatever specification element is indicated by its key attribute, + as in the example above. Documentation for any attributes specified by the atts attribute + will also be generated as an associated attribute list.

+ + + + + + + + + + + + +
+
+
+ Modules and Schemas +

As mentioned above, the primary purpose of this module is to facilitate the documentation and creation + of an XML schema derived from the TEI Guidelines. The following elements are provided for this purpose: + + + + + + + + + A module is a convenient way of grouping together element and + other declarations, and of associating an externally-visible name with the resulting group. A + specification group performs essentially the same function, but the resulting group is + not accessible outside the scope of the ODD document in which it is defined, whereas a module can be + accessed by name from any TEI schema specification. Elements, and their attributes, element classes, and + patterns are all individually documented using further elements described in section below; part of that specification includes the name of the module to which the + component belongs.

+

An ODD processor generating XML DTD or schema fragments from a document marked up according to the + recommendations of this chapter will generate such fragments for each moduleSpec element found. + For example, the chapter documenting the TEI module for names and dates contains a module specification + like the following: + + + Names and Dates + Additional elements for names and dates + + + together with specifications for all the elements, classes, and patterns which make up that module, + expressed using elementSpec, classSpec, or macroSpec elements as appropriate. + (These elements are discussed in section below.) Each of those + specifications carries a module attribute, the value of which is namesdates. An + ODD processor encountering the moduleSpec element above can thus generate a schema fragment for + the TEI namesdates module that includes declarations for all the elements + (etc.) which reference it.

+

In most realistic applications, it will be desirable to combine more than one module together to form a + complete schema. A schema consists of references to one or more modules or specification + groups, and may also contain explicit declarations or redeclarations of elements (see further ). Any combination of modules can be used to create a schema The distinction between base and additional tagsets in earlier versions of the TEI scheme has not + been carried forward into P5. +

+

A schema can combine references to TEI modules with references to other (non-TEI) modules using + different namespaces, for example to include mathematical markup expressed using MathML in a TEI + document. By default, the effect of combining modules is to allow all of the components declared by the + constituent modules to coexist (where this is syntactically possible: where it is not—for example, + because of name clashes—a schema cannot be generated). It is also possible to over-ride declarations + contained by a module, as further discussed in section

+

It is often convenient to describe and operate on sets of declarations smaller than the whole, and to + document them in a specific order: such collections are called specGrps (specification + groups). Individual specGrp elements are identified using the global xml:id + attribute, and may then be referenced from any point in an ODD document using the specGrpRef + element. This is useful if, for example, it is desired to describe particular groups of elements in a + specific sequence. Note however that the order in which element declarations appear within the schema + code generated from an ODD file element is not in general affected by the order of declarations within a + specGrp.

+

An ODD processor will generate a piece of schema code corresponding with the declarations contained by + a specGrp element in the documentation being output, and a cross-reference to such a piece of + schema code when processing a specGrpRef. For example, if the input text reads +

This module contains three red elements: + + + + and two blue ones: + + +

+ + then the output documentation will replace the two specGrp elements above with a + representation of the schema code declaring the elements beetroot, east, and rose and that declaring the elements sky and bayou respectively. Similarly, if the + input text contains elsewhere a passage such as +
+ An overview of the imaginary module +

The imaginary module contains declarations for coloured things: + +

+
+ then the specGrpRef elements may be replaced by an appropriate piece of reference text such as + The RED elements were declared in section 4.2 above, or even by a copy of the relevant + declarations. As stated above, the order of declarations within the imaginary module described above + will not be affected in any way. Indeed, it is possible that the imaginary module will contain + declarations not present in any specification group, or that the specification groups will refer to + elements that come from different modules. Specification groups are always local to the document in + which they are defined, and cannot be referenced externally (unlike modules).

+ + + + + + + + + + + +
+
+ Specification Elements +

The following elements are used to specify elements, classes, patterns, and datatypes: + + + + + +

+

Unlike most elements in the TEI scheme, each of these specification elements has a + fairly rigid internal structure consisting of a large number of child elements which are always + presented in the same + order. + Furthermore, since these elements all describe markup objects in broadly similar ways, they have several + child elements in common. In the remainder of this chapter, we discuss first the elements which are + common to all the specification elements, and then those which are specific to a particular type.

+

Specification elements may appear at any point in an ODD document, both between and within paragraphs + as well as inside a specGrp element, but the specification element for any particular component + may only appear once (except in the case where a modification is being defined; see further ). The order in which they appear will not affect the order in which they are + presented within any schema module generated from the document. In documentation mode, however, an ODD + processor will output the schema declarations corresponding with a specification element at the point in + the text where they are encountered, provided that they are contained by a specGrp element, + + as discussed in the previous section. An ODD processor will also associate all declarations found with + the nominated module, thus including them within the schema code generated for that module, and it will + also generate a full reference description for the object concerned in a catalogue of markup objects. + These latter two actions always occur irrespective of whether or not the declaration is included in a + specGrp.

+ + + + + + +
+
+ Common Elements +

This section discusses the child elements common to all of the specification elements; some of these + are defined in the core module (). These child elements are used to specify the + naming, description, exemplification, and classification of the specification elements.

+
+ Description of Components +

+ + + + + + + + +

+

The gloss element may be used to provide a brief explanation for the name of the object if + this is not self-explanatory. For example, the specification for the element ab used to mark + arbitrary blocks of text begins as follows: + + anonymous block + + + A gloss may also be supplied for an attribute name or an attribute value in similar + circumstances: + + + suspension + the abbreviation provides the first letter(s) of the word or phrase, omitting the + remainder. + + + contraction + the abbreviation omits some letter(s) in the middle. + + + +

+

Note that the gloss element is needed to explain the significance of the identifier for an + item only when this is not apparent, for example because it is abbreviated, as in the above example. + It should not be used to provide a full description of the intended meaning (this is the function of + the desc element), nor to comment on equivalent values in other schemes (this is the purpose + of the equiv element), nor to provide alternative versions of the ident attribute + value in other languages (this is the purpose of the altIdent element).

+

The contents of the desc element provide a brief characterization of the intended function + of the object being documented in a form that permits its quotation out of context, as in the + following example: + + + identifies a word or phrase as belonging to some + language other than that of the surrounding text. + + + By convention, a desc element begins with a verb such as contains, + indicates, specifies, etc. and contains a single + clause.

+

Both the gloss and desc elements (in + addition to exemplum, remarks, and + valDesc) are members of att.translatable, and thus carry the + versionDate attributre. Where specifications are + supplied in multiple languages, these elements may be repeated + as often as needed. Each such element should carry both an + xml:lang and a versionDate attribute to + indicate the language used and the date on which the + translated text was last checked against its source.

+ +

The equiv element is used to document equivalencies between the concept represented by this + object and the same concept as described in other schemes or ontologies. The uri attribute + is used to supply a pointer to some location where such external concepts are defined. For example, to + indicate that the TEI death element corresponds to the concept defined by the CIDOC CRM + category E69, the declaration for the former might begin as follows: + + + + + + +

+

The equiv element may also be used to map newly-defined elements onto existing constructs in + the TEI, using the filter and name attributes to point to an implementation of + the mapping. This is useful when a TEI customization (see ) defines + shortcuts for convenience of data entry or markup readability. For example, + suppose that in some TEI customization an element bo has been defined + which is conceptually equivalent to the standard markup construct hi rend='bold'. The + following declarations would additionally indicate that instances of the bo element can be converted to canonical TEI by obtaining a filter from the URI specified, and + running the procedure with the name bold. The mimeType attribute specifies + the language (in this case XSL) in which the filter is written: + + + + bold + contains a sequence of characters rendered in a bold face. + + + +

+

The altIdent element is used to provide an alternative name for an object, for example using + a different natural language. Thus, the following might be used to indicate that the abbr + element should be identified using the German word Abkürzung: + + Abkürzung + + In the same way, the following specification for the graphic element indicates that the + attribute url may also be referred to using the alternate identifier href: + + + + href + + + + + +

+

By default, the altIdent of a component is identical to the value of its ident + attribute.

+

The remarks element contains any additional commentary about how the item concerned may be + used, details of implementation-related issues, suggestions for other ways of treating related + information etc., as in the following example: + + + +

This element is intended for use only where no other element is available to mark the phrase + or words concerned. The global xml:lang attribute should be used in preference to + this element where it is intended to mark the language of the whole of some text element.

+

The distinct element may be used to identify phrases belonging to sublanguages or + registers not generally regarded as true languages.

+ + + +

+

A specification element will usually conclude with a list of references, each tagged using the + standard ptr element, and grouped together into a listRef element: in the case of + the foreign element discussed above, the list is as follows: + + + + + + where the value COHQF is the identifier of the section in these Guidelines where this + element is fully documented.

+
+
+ Exemplification of Components +

+ + + + + +

+

The exemplum element is used to combine a single illustrative example with an optional + paragraph of commentary following or preceding it. The illustrative example itself may be marked up + using either the eg or the egXML element.

+

The source attribute may be used on either element to indicate the source from which an + example is taken, typically by means of a pointer to an entry in an associated bibliography, as in the + following example: + +

L'element foreign s'applique également aux termes considerés étrangers.

+ +

Pendant ce temps-là, dans le bureau du rez- de-chaussée, les secrétaires faisaient du + hulla-hoop.

+ + +]]> +

+

When, as here, an example contains valid XML markup, the egXML element should be used. In + such a case, it will clearly be necessary to distinguish the markup within the example from the markup + of the document itself. In an XML environment, this is easily done by using a different name space for + the content of the egXML element. For example: + The term element may be used +to mark any technical term, thus: + + This recursion is + giving me a headache.

]]>

+

Alternatively, the XML tagging within an example may be escaped, either by using + entity references to represent the opening angle bracket, or by wrapping the whole example in a CDATA + marked section: The term element may be used +to mark any technical term, thus: + + This <term>recursion</term> is + giving me a headache.

]]> or, equivalently: + The term element may be used +to mark any technical term, thus: +recursion is + giving me a headache.]]]]>

]]> + However, escaping the markup in this way will make it impossible to validate, and should therefore + generally be avoided.

+

If the XML contained in an example is not well-formed then it must either be enclosed in a CDATA + marked section, or escaped as above: this applies whether the eg or + egXML is used. The valid attribute on egXML may be used to indicate the + XML validity of the example with respect to some schema, as being valid, invalid, or feasibly valid.

+

The egXML element should not be used to tag non-XML examples: the general purpose + eg or q elements should be used for such purposes.

+
+
+ Classification of Components +

In the TEI scheme elements are assigned to one or more classes, which may themselves + have subclasses. The following elements are used to indicate class membership: + + + +

+

The classes element appears within either the elementSpec or classSpec + element. It specifies the classes of which the element or class concerned is a member by means of one + or more memberOf child elements. Each such element references a class by means of its + key attribute. Classes themselves are defined by the classSpec element described + in section below.

+

For example, to show that the element gi is a member of the class model.phrase.xml, the elementSpec which documents this element contains the + following classes element: + + + + +

+ + + + + + + + + +
+
+
+ Element Specifications +

The elementSpec element is used to document an element + type, together with its associated attributes. In addition to the + elements listed above, it may contain the following subcomponents: + + + + + + +

+

These subcomponents are discussed in the following sections.

+
+ Defining Content Models +

As described in and , the content of the element being + defined — that is, what elements are allowed inside it, and in + what order they are permitted — is described by its + content model. The content model is defined by the + content child of elementSpec. There are three + distinctly different ways of specifying a content model: + + The content model can be described using TEI elements + defined by this chapter, as discussed in immediately below. Two such TEI elements + that may be used to define a content model are + dataRef and valList. But because these are + most often used to define attribute values, they are discussed + separately near the beginning and towards the end of , respectively. + Alternatively, and primarily for backwards + compatibility, the content model may be expressed using a + RELAX NG pattern. This is discussed in , below. + Lastly, content models may be expressed using a schema + language other than TEI or RELAX NG, but no further + recommendations on doing so are provided by these + Guidelines. +

+
+ Defining Content Models: TEI +

In the simplest case, the content model of an element may + be expressed using a single empty element as the only + child of content. This describes the element being + defined as empty, meaning a valid instance of + said element can not have any content.It + would still be allowed to contain comments or processing + instructions, as these are not considered part of the content + model. + + + +

+

More commonly, one or more of the following elements are used + to define a content model: + + + + + + +

+

An elementRef provides the name of an element which + may appear at a certain point in a content model. An + anyElement also asserts that an element may appear at a + certain point in a content model, but rather than providing the + name of a particular element type that may appear, any element + regardless of its name may appear (and may have any attributes). + A classRef provides the name of a model class, members + of which may appear at a certain point in content model.The classRef element may be used to + refer to attribute classes, but this should not be done within a + content. A macroRef provides the name + of a predefined macro, the expansion of which is to be inserted + at a certain point in a content model.

+

These three elements are all members of an attribute class + which provides attributes that further modify their significance + as follows: + + + +

+

Additionally, two wrapper elements are provided to indicate + whether the components listed as their children form a sequence + or an alternation: + + + + + These two wrapper elements are also members of att.repeatable. References listed as + children of sequence must appear in the order and + cardinality specified. Only one of the references listed as + children of alternate may appear, although the + cardinality of the alternate itself applies. Thus the + following fanciful content model permits either any number of + ptr elements (except zero) or any number of + ref elements (except zero); at least one element must + be present, but having both a ptr and a ref would be + invalid. + + + + + + + + + However, the following content model permits any number of + either ptr or ref elements (except zero); one + element must be present, and having both ptr elements + and ref elements (even intermixed) would be valid. + + + + + + + + +

+

The sequence and alternate elements may be + used in combination with great expressive power. For example, in + the following example, which might be imagined as a clean + replacement for the content of the choice element, one + and only one of the element pairs sic and + corr, orig and reg, or + abbr and expan is allowed. + + + + + + + + + + + + + + + + + + + In the following example, which might be imagined as a clean + replacement for the content of the address element, the + encoder is given a choice of either: + + a single street followed by a single + placeName followed by a single postCode + followed by an optional country, or + 2, 3, or 4 + addrLine elements. + + + + + + + + + + + + + + +

+

In addition to expressing where certain elements, members of + a class of elements, or constructs matching a predefined macro + may occur inside an element, a content model may permit a string + of zero or more Unicode characters to occur at a certain point + in the content model. This is indicated by supplying the element + textNode within the content element. + + + + If nothing but a textNode element is present inside a + content element, valid instances of the element being + defined may contain a sequence of zero or more Unicode + characters, but may not contain any elements.This content model is not used very often in the + TEI scheme. Because only Unicode characters are permitted, there + is no way to record characters that are not (yet) represented in + Unicode. Thus in TEI instead of textNode we often use a + reference to macro.xtext which + permits both Unicode characters and the g + element.

+
+
+ Defining Content Models: RELAX NG +

Element content models may also be defined using RELAX NG + patterns. Here is a very simple example + + + + + The element within whose specification element this + content element appears will have a content model which + is expressed in RELAX NG as text, using the RELAX + NG namespace. This model will be copied unchanged to the output + when RELAX NG schemas are being generated. When an XML DTD is + being generated, an equivalent declaration (in this case + (#PCDATA)) will be output.

+

Here is a more complex example: + + + + + + + + + + + + + This is the content model for the teiHeader element, expressed in the RELAX NG syntax, which + again is copied unchanged to the output during schema generation. The equivalent DTD notation + generated from this is (fileDesc, (%model.teiHeaderPart;)*, revisionDesc?).

+

The RELAX NG language does not formally distinguish element names, attribute names, class names, or + macro names: all names are patterns which are handled in the same way, as the above example shows. + Within the TEI scheme, however, different naming conventions are used to distinguish amongst the + objects being named. Unqualified names (fileDesc, revisionDesc) are always + element names. Names prefixed with model. or att. (e.g. model.teiHeaderPart and att.typed) are always class names. In + DTD language, classes are represented by parameter entities (%model.teiHeaderPart; in the + above example); see further .

+

The RELAX NG pattern names generated by an ODD processor by default include a special prefix, the + default value for which is set using the prefix attribute on schemaSpec. + The purpose of this is to ensure that the pattern name + generated is uniquely identified as belonging to a particular schema, and thus avoid name clashes. For + example, in a RELAX NG schema combining the TEI element ident with another element called + ident from some other vocabulary, the former will be defined by a pattern called + TEI_ident rather than simply ident. Most of the time, this behaviour is + entirely transparent to the user; the one occasion when it is not will be where a content model + (expressed using RELAX NG syntax) needs explicitly to reference either the TEI ident or the + other one. In such a situation, the autoPrefix attribute on content may be used. + For example, suppose that we wish to define a content model for term which permits either a + TEI ident or the ident defined by some other vocabulary. A suitable content model + would be generated from the following content element: + + + + + + +

+
+
+
+ Additional Constraints +

In addition to the content element, a set of general constraintSpec elements can be + used to express rules about the validity of an element. Like some other specification elements, they + are identifiable (using the ident attribute) in order that a TEI customization may + override, delete, or change them individually. Each constraintSpec can be expressed in any + notation which is found useful; the notation used must be recorded using the scheme + attribute.

+

Schematron is an ISO standard (ISO/IEC 19757-3:2006) that defines a + simple XML vocabulary for an assertion language which provides a powerful way of + expressing constraints on the content of any XML document in addition to those provided by other + schema languages. Such constraints can be embedded within a TEI schema specification — including + a TEI customization specification — using the methods exemplified in this chapter.Indeed, these Guidelines themselves include many additional constraints + which are expressed in the ISO Schematron language using this mechanism. A conformant TEI document + should respect these constraints, although automatic validation of them may not be possible for all + processors. + An ODD processor will typically process any constraintSpec elements in a TEI + specification whose scheme attribute indicates that they are expressed in Schematron to + create an ISO Schematron schema which may be used to validate document instances. The ISO Schematron + schema may be a free-standing document, or may be embedded in the RELAX NG schema output of the ODD + processor.

+

Constraints are generally used to model local rules which may be outside the scope of the target + schema language. For example, in earlier versions of these Guidelines several constraints on the usage + of the attributes of the TEI element relation were expressed informally as follows: only + one of the attributes active and mutual may be supplied; the attribute + passive may be supplied only if the attribute active is supplied.. In the + current version of the Guidelines, constraint specifications expressed as Schematron rules have been + added, as follows: + + + + One of the + attributes 'name', 'ref' or 'key' must be supplied + + + + + Only one of the + attributes @active and @mutual may be supplied + + + + + the + attribute 'passive' may be supplied only if the attribute 'active' is supplied + + + +

+

The constraints in the preceding example all related to attributes in the empty namespace, and the + Schematron rules did not therefore need to define a TEI namespace prefix. The Schematron language ns element should be used to do this when a constraint needs to refer to a + TEI element, as in the following example, which models the constraint that a TEI div must + contain either no subdivisions or at least two of them: + + + + + + if it contains any subdivisions, a + division must contain at least two of them + + + + + Schematron rules are also useful where an application needs to enforce rules on attribute values, as + in the following examples which check that various types of title are provided: + + + + an introductory component + of the title is expected + + + + + a main title must be supplied + + + + +

+

As a further example, Schematron may be used to enforce rules applicable to a TEI document which is + going to be rendered into accessible HTML, for example to check that some sort of content is available + from which the alt attribute of an HTML img can be + created: + + + + + + + You should provide information in a figure from + which we can construct an alt attribute in HTML + + + + + + Schematron rules can also be used to enforce other HTML accessibility rules about tables; note here + the use of a report and an assertion within one pattern: + + + + + + + A <table> should have a caption, using a <head> + element + Do not use tables to lay out the document body + + + + + +

+

Constraints can be expressed using any convenient language. + The following example uses a pattern matching language called + SPITBOL to express the requirement that title and author should + be different. + + + (output = leq(title,author) "title and author cannot be the same") + + + Note that the value of scheme is + SPITBOL. In order to properly constrain and + document the values of scheme used in their + customization file, a project may wish to create a + customization that (among other things) adds and explains this + value for use in validating their customization file. Thus + using schemes other than those provided for by the TEI + (currently schematron and isoschematron) + may require somewhat more effort when creating a customization + file. Such private schemes will generally be even more + problematic on implementation of the constraints themselves, + as it may require siginficant programming work. The TEI only + provides this capability for the suggested values.

+
+
+ Attribute List Specification +

The attList element is used to document information about a collection of attributes, either + within an elementSpec, or within a classSpec. An attribute list can be organized + either as a group of attribute definitions, all of which are understood to be available, or as a + choice of attribute definitions, of which only one is understood to be available. An attribute list + may thus contain nested attribute lists.

+

The attribute org is used to indicate whether its child attDef elements are all + to be made available, or whether only one of them may be used. For example, the attribute list for the + element moduleRef contains a nested attribute list to indicate that either the + include or the except attribute may be supplied, but not both: + + + + + + + + + + + + +

+

The attDef element is used to document a single attribute, using an appropriate selection + from the common elements already mentioned and the following : + + + + + + + + +

+

The attList within an elementSpec is used to specify only the attributes which are + specific to that particular element. Instances of the element may carry other attributes which are + declared by the classes of which the element is a member. These extra attributes, which are shared by + other elements, or by all elements, are specified by an attList contained within a + classSpec element, as described in section below.

+
+ Datatypes +

The datatype (i.e. the kind of value) for an attribute may be specified using + the elements datatype and dataRef. A datatype may be defined in any of the + following three ways: + by reference to an existing TEI datatype definition, itself defined by a dataSpec; + by use of its name in XML Schema + Part 2: Datatypes Second Edition, the widely used + datatype library maintained by the W3C as part of + the definition of its schema language; + by referencing its URI within some other datatype library. + The TEI defines a number of datatypes, each with an identifier beginning + teidata., which are used in preference to the datatypes available natively from a + target schema such as RELAX NG or W3C Schema since the facilities provided by different schema + languages vary so widely. The TEI datatypes available are described in section above. Note that each is, of necessity, mapped eventually to an externally defined datatype such + as W3C Schema's text or name, possibly combined to give more + expressivity, or constrained to a particular defined usage.

+

It is possible to reference a W3C schema datatype directly using name. In this case, + the child dataFacet can be used instead of restriction to set W3C schema compliant + restrictions on the datatype. A dataFacet is particularly useful for restrictions that can be difficult to impose and to read as a + regular expression pattern. + + + + + Note that restrictions are either expressed with restriction or dataFacet, never both.

+

A datatype may be used to constrain the textual content of + an element, rather than the value of an attribute. But because + they are intended for use in defining ranges of attribute + values, datatypes may not contain elements or attributes.

+

The attributes minOccurs and + maxOccurs are available for the case where an + attribute may take more than one value of the type + specified. For example, the columns attribute of + the layout element can have one or two non-negative + integers as its value: + + + columns + specifies the number of columns per page + + + + +

If a single number is given, all pages referenced + have this number of columns. If two numbers are given, + the number of columns per page varies between the + values supplied. Where columns is omitted + the number is assumed to be 1.

+ + + + indicating that the target attribute may take any number of values, each being of the + same datatype, namely the TEI data specification teidata.pointer. As is usual in XML, + multiple values for a single attribute are separated by one or more white space characters. Hence, + values such as #a #b #c or http://example.org + http://www.tei-c.org/index.xml may be supplied. + +

+
+
+ Value Specification +

The valDesc element may be used to describe constraints on data content in an informal + way: for example + must point to another align + element logically preceding this one. + Values should be Library of Congress + subject headings. + A bookseller's surname, taken from the list + in Pollard and Redgrave +

+

Constraints expressed in this way are purely documentary; to enforce them, the + constraintSpec element described in section must be used. For + example, to specify that an imaginary attribute ageAtDeath must take + positive integer values less than 150, the datatype teidata.numeric + might be used in combination with a constraintSpec such as the following: + + + age in years at death + + + + age at death must be an integer less than 150 + + + + +

+

The elements altIdent, equiv, gloss and desc may all be used in + the same way as they are elsewhere to describe fully the meaning of a coded value, as in the + following example: + + + dou + + dubious + used when the application of this element is doubtful or uncertain + + +

+

Where all the possible values for an attribute can be enumerated, the datatype + teidata.enumerated should be used, together with a valList element + specifying the values and their significance, as in the following example: + + required + recommended + optional + + + Note the use of the gloss element here to explain the otherwise less than obvious meaning + of the codes used for these values. Since this value list specifies that it is of type + closed, only the values enumerated are legal, and an ODD processor will typically + enforce these constraints in the schema fragment generated.

+

The valList element can also be used to provide illustrative examples of the kinds of + values expected without listing all of them. In such cases the type attribute will have + the value open, as in the following example: + + characterizes the movement, for example as an + entrance or exit. + 예를 들어 입장 또는 퇴장과 같은, 이동의 특성을 기술한다. + + + + + + character is entering the stage. + 등장인물이 무대에 등장하고 있다. + + + character is exiting the stage. + 등장인물이 무대에서 퇴장하고 있다. + + + character moves on stage + 등장인물이 무대에서 이동한다. + + + + The datatype will be teidata.enumerated in either case.

+

The valList or dataRef elements may also be used (as a child of the + content element) to put constraints on the permitted content of an element, as noted at + . This use is not however supported by all schema languages, and is + therefore not recommended if support for non-RELAX NG systems is a consideration.

+
+ + +
+
+ Processing Models +

As far as possible, the TEI defines elements and their attributes in a way which is entirely + independent of their subsequent processing, since its intention is to maximize the reusability of + encoded documents and their use in multiple contexts. Nevertheless, it can be very useful to specify + one or more possible models for such processing, both to clarify the intentions of the encoder, and to + provide default behaviours for a software engineer to implement when documents conforming to a + particular TEI customization are processed. To that end, the following elements may be used to + document one or more processing models for a given element. + + + + +

+

One or more of these elements may appear directly within an element specification to define the + processing anticipated for that element, more specifically how it should be processed to produce the + kind of output indicated by the output attribute. Where multiple such elements appear + directly within an elementSpec, they are understood to document mutually exclusive processing + models, possibly for different outputs or applicable in different contexts. Alternatively, the + modelGrp element may be used to group alternative model elements intended for a + single kind of output. The modelSequence element is provided for the case where a sequence of + models is to be processed, functioning as a single unit.

+

A processing model suggests how a given element may be transformed to produce one or more outputs. + The model is expressed in terms of behaviours and parameters, using + high-level formatting concepts familiar to software engineers and web designers, such as + block or inline. As such, it has a different purpose from + existing TEI mechanisms for documenting the appearance of source materials, such as the global + attributes rend, rendition and style, described in sections and . It does not necessarily describe anything present in + the original source, nor does it necessarily represent its original structure or semantics. A + processing model is a template description, which may be used to simplify the task of producing or + customizing the stylesheets needed by a formatting engine or any other form of processor.

+
+ The TEI processing model +

The model element is used to document the processing model intended for a particular + element in an abstract manner, independently of its implementation in whatever processing language + is chosen. This is achieved by means of the following attributes and elements: + + + The mandatory behaviour attribute defines in broad terms how an element + should be processed, for example as a block or as an inline element. The optional + predicate attribute may be used to specify a subset of contexts in which this model + should be applicable: for example, an element might be treated as a block element in some contexts, + but not in others. The output attribute supplies a name for the output for which this + model is intended, for example for screen display, for a printed reading copy, for a scholarly + publication, etc. The way in which an element should be rendered is declared independently of its + behaviour, using either the attribute useSourceRendition or the element + outputRendition. These Guidelines recommend that outputRendition be expressed + using the W3C Cascading Stylesheet Language (CSS), but other possibilities are not excluded. The + particular language used may be documented by means of the styleDefDecl element described + in . +

+
+
+ Output Rendition +

Here is a simple example of a processing model which might be included in the specification for an + element such as hi or foreign. The intent is that these elements should be + presented inline using an italic font. + + + font-style: italic; + + + If the rendition element, or the attributes style, rend, or + rendition have already been used in the source document to indicate elements that were + originally rendered in italic, and we wish simply to follow this in our processing, then there is no + need to include an outputRendition element, and the attribute useSourceRendition + could be used as follows: + + + + Any rendition information present in the source document will be ignored unless the + useSourceRendition attribute has the value true. If that is the case, then + such information will be combined with any rendition information supplied by the + outputRendition element. For example, using CSS, an element which appears in the source + as follows + + this is in bold + + would appear in bold and italic if processed by the following model + + + font-style: italic; + + +

+
+
+ CSS Class +

In a typical workflow processing TEI documents for display on the web, a system designer will often + wish to use an externally defined CSS stylesheet. The cssClass attribute simplifies the + task of maintaining compatibility amongst the possibly many applications using such a stylesheet and + also enables a TEI application to specify the names of classes to be used for particular processing + models. For example, supposing that the associated CSS stylesheet includes a CSS class called + labeled-list, the following processing model might be used to request it be used + for list elements containing a child label element: + + + + + + + +

+

In the following example, a table will be formatted using renditional information provided in the + source if that is available, or by an external stylesheet, using one of the CSS classes specified, + if it is not: + + + + + + + + +

+

As discussed further below, the input data available to a processing model is by default the + content of the element being processed, together with its child nodes.

+ + + +
+
+ Model Contexts and Outputs +

Sometimes different processing models are required for the same element in different contexts. For + example, we may wish to process the quote element as an inline italic element when it + appears inside a p element, but as an indented block when it appears elsewhere. To achieve + this, we need to change the specification for the quote element to include two + model elements as follows: + + + font-style: italic; + + + left-margin: 2em; + + + As noted above, these two models are mutually exclusive. The first processing model will be used + only for quote elements which match the XPath expression given as value for the + predicate attribute. All other element occurrences will use the second processing + model.

+

When, as here, multiple behaviours are required for the same element, it will often be the case + that the appropriate processing will depend on the context. It may however be the case that the + choice of an appropriate model will be made on the basis of the intended output. For example, we + might wish to define quite different behaviours when a document is to be displayed on a mobile + device and when it is to be displayed on a desktop screen. Different behaviours again might be + specified for a print version intended for the general reader, and for a print version aimed at the + technical specialist.

+

The modelGrp element can be used to group together all the processing models which have in + common a particular intended output, as in the following example: + + + + font-size: 7pt; + + + text-color: red; + + + + + font-size: 12pt; + + + text-align: center; + + + +

+
+
+ Behaviours and their parameters +

In the examples above we have used without explanation or definition two simple + behaviours: inline and block, but many other behaviours + are possible. A list of recommended behaviour names forms part of the specification for the element + model. A processing model can specify any named behaviour, some of which have additional + parameters. The parameters of a behaviour resemble the + arguments of a function in many programming languages: they provide names which can be used to + distinguish particular parts of the input data available to the process used to implement the + behaviour in question.

+

The following elements are used to represent and to define parameters: + + + +

+

By default, a processor implementing the TEI processing model for a particular element has + available to it as input data the content of the element itself, and all of its children. One or + more param elements may be supplied within a model element to specify + parameters which modify this, either by selecting particular parts of the default + input data, or by selecting data which would not otherwise be available. In either case, the value + supplied for the parameter is given as an XPath expression, evaluated with respect to the element + node being processed. An arbitrary name (defined in the corresponding paramSpec) is also + supplied to a processor to identify each parameter.

+

For example, an element such as the TEI ref element will probably be associated with a + processing model which treats it as a hyperlink. But a hyperlink (in most implementations) often has + two associated pieces of information: the address indicated, and some textual content serving to + label the link . In HTML, the former is provided as value of the href + element, and the latter by the content of an a element. In the following + processing model we define a behaviour called link, which will use whatever is + indicated by the parameter called uri + + to provide the former, while the latter is provided by the content of the ref element itself: + + + + + + + + The value attribute of a param element supplies an XPath expression that + indicates where the required value may be found. The context for this XPath is the element which is + being processed; hence in this example, the uri parameter takes the value of the + target attribute on the ref element being processed. The content + parameter indicates that the content of that ref element should be provided as its value. (This parameter is not + strictly necessary, since by default the whole content of the element being processed is always available to a processor, but + supplying it in this way makes the procedure more explicit). +

+

All the parameters available for a given behaviour are defined as a part of the definition of the + behaviour itself, as further discussed in section below.

+

As a further example, the TEI choice element requires a different behaviour for which the + name alternate is proposed as in the following example: + + + + + + + + The processing model shown here will be selected for processing a choice element which has both sic and corr child elements. + The names default and alternate here are provided for convenience. + The default parameter provides the value of the child corr element, and the alternate + parameter will provide that of the child sic elements. If neither param element was supplied, both elements would + still be available to an application, but the application would need to distinguish them for itself. +

+

A choice element might contain multiple corrections, each with differing values for their + cert attribute. In the following processing model, we will accept as value of the default attribute only + those child corr elements which have a value high for that attribute: + + + + + + + +

+

A choice element might contain several different pairs of alternate elements (abbr + and expan, orig and reg, etc.) We might wish to group together a set of + processing models for these, for example to determine which of the possible alternatives is + displayed by default whenever a choice element is processed for output to the web: + + + + + + + + + + + + + + + + + +

+

If nothing matches the XPath defining the value of a particular parameter (e.g. if in the above + example there is no correction with cert=high) then the default + parameter has no value. It is left to implementors to determine how null-valued parameters should be + processed.

+
+
+ Outputs +

As noted above, the output attribute is used to associate particular processing models + with a specific type of output. The following example documents a range of processing intentions for + the date element, intended to cope with at least the following three situations:

+ + there is text inside the element, and the output is print; + there is no text inside the element but there is a when attribute, and the output + is print; + there is a when attribute, there is text inside the element, and the output is + web + + + + + + + + + + + + + + + +

For output to print we supply two processing models, one for the simplest case where the content of + the date is to be treated as an inline element, and the other for the case where there is + no content and the value of the when attribute is to be used in its place. This is + specified by a parameter, called content in this example. For output to web, we use + the alternate behaviour discussed in the previous section to indicate that by default + the content of the element will be used, while retaining access to the value of the when + attribute, this time via a parameter called alternate.

+
+
+ Model sequence +

As well as being combined to form model groups, several models may be combined to form a + model sequence. All of the individual components of a model sequence are understood + to be applied, rather than considered to be mutually exclusive alternatives. For example, we might + wish to define two different behaviours for a note element: the inline behaviour should be + used to display the value of the note number (given by its n attribute), while a + different behaviour (here called footnote) should be used to display the content of + the element at a specified place, given by the parameter place. Because both of these + actions are required, the two models are grouped by a modelSequence element: + + + + + + + + + + + + +

+

The value of the parameter called place above is an XPath expression supplying an + arbitrary string (foot), which is therefore quoted. It is left to implementors to validate or + constrain the possible values for such expressions.

+
+ +
+ Defining a processing model +

The processing model for an element is defined using some combination of model, + modelSequence, or modelGrp elements within the elementSpec element containing its specification. + The processing to be carried out is defined by means of the behaviour specified for each + model element, possibly supplying specified values for a number of named parameters. The + parameters available for a given behaviour are specified using a number of param elements + grouped together in a paramList element. This paramList is supplied within the + valItem used to document and name the behaviour. Here for example is the valItem + which defines the link behaviour presented above: + + + create a hyperlink + + + supplies the location of some content describing the link + + + supplies the location of the intended hyperlink + + + + +

+

Similarly the valItem which defines the behaviour named alternate includes specifications for two + parameters: one also called alternate and the other called default + + + support display of alternative visualisations, for + example by displaying the preferred content, by displaying both in parallel, or by toggling + between the two. + + + supplies the location of the preferred + content + + + supplies the location of the alternative + content + + + + +

+

The suggested behaviours provided by the model element are informally defined using + commonly understood terminology, but specific details of how they should be implemented are left to + the implementor. Such decisions may vary greatly depending on the kind of processing environment, + the kind of output envisaged, etc. The intention is to reduce as far as possible any requirement for + the implementor to be aware of TEI-specific rules, and to maximize the ability of the ODD to express + processing intentions without fully specifying an implementation.

+
+
+ Implementation of Processing Models +

As elsewhere in these Guidelines, the recommendations of this section are intended to be + implementation-agnostic, not favouring any particular implementation method or technology. An + implementor may choose, for example, whether to pre-process processing model specifications into a + free standing pipeline, or to extract and process them dynamically during + document processing. However, although implementors are generally free to interpret the processing + model documentation according to their own requirements, some general assumptions underlie the + recommendations made here: + If a model element has no child param elements, the action specified by + its behaviour should be applied to the whole element node concerned, including its child nodes + of whatever type. If that behaviour requires distinguishing particular parts of the input, an + implementation may choose either to make those distinctions itself, or to raise an error. + If a model element has no predicate or output attribute then + it is assumed to apply to all instances of the element defined in its parent + elementSpec for all outputs. Otherwise its applicability depends on these + attributes. + Only one of the models is to be applied for a particular instance of the element, except when they appear + within a modelSequence + + A matching model is one where the element to be processed satisfies the XPath in the + predicate attribute of the model or modelSequence and the current + output method matches the method specified in the output attribute of the model, + modelSequence, or a containing modelGrp. A model or modelSequence + without a predicate always matches the element to be processed. A model, + modelGrp, or modelSequence without an output attribute matches any output method. + Processing Model implementations must execute only the first matching model or + modelSequence in document order. + If there are two or more model elements provided for an elementSpec but + they have different output attributes then the implementation should choose the + model appropriate to the desired output. + If there are two or more model elements provided for an elementSpec but + they have different predicate attributes then the implementation should choose the + model whose predicate provides the most specific context (where + specific is understood in the same way as in XSLT) + + In the following example, which shows part of the element specification for the head + element, there are two model elements, one with and one without a predicate + attribute: + + + Model for list headings + + + + Default model for all headings. + + + + In this example, an implementation should use the first processing model only for head + elements with a list element as parent; for all other head elements, the second + processing model should be used.

+ + + + + + + + + + + + +
+
+
+
+ Class Specifications +

The element classSpec is used to document either an attribute class or a + model class, as defined in section . A corresponding + classRef element may be used to select a specific named class from those available. + + + + +

+

A model class specification does not list all of its members. Instead, its members declare that they + belong to it by means of a classes element contained within the relevant elementSpec. + This will contain a memberOf element for each class of which the relevant element is a member, + supplying the name of the relevant class. For example, the elementSpec for the element + hi contains the following: + + + + + This indicates that the hi element is a member of the class with identifier model.hiLike. The classSpec element that documents this class contains + the following declarations: + + groups phrase-level elements related to highlighting that have no specific semantics + + + + + + which indicate that the class model.hiLike is actually a member (or + subclass) of the class model.highlighted.

+

The function of a model class declaration is to provide another way of referring to a group of + elements. It does not confer any other properties on the elements which constitute its membership.

+

The attribute type is used to distinguish between model and + attribute classes. In the case of attribute classes, the attributes provided by + membership in the class are documented by an attList element contained within the + classSpec. In the case of model classes, no further information is needed to define the class + beyond its description, its identifier, and optionally any classes of which it is a member.

+

When a model class is referenced in the content model of an element (i.e. by means of a + classRef element within the content of an elementSpec), its meaning will + depend on the value of its expand attribute.

+

If this attribute is not specified, the classRef is interpreted to mean an alternated list of + all the current members of the class named. For example, suppose that the members of the class model.hiLike are elements hi, it, and bo. Then a content model such as + + + + would be equivalent to the explicit content model: + + + + + + + + (or, to use RELAX NG compact syntax, + ( hi | it | bo )). + However, a content model of <classRef + expand="sequence"/> would be equivalent to the + following explicit content model: + + + + + + + (or, in RELAX NG compact syntax, + ( hi, it, bo )).

+ +

An attribute class (a classSpec of type + atts) contains an attList element which lists the attributes that all the members of + that class inherit from it. For example, the class att.interpLike defines a + small set of attributes common to all elements which are members of that class: those attributes are + listed by the attList element contained by the classSpec for att.interpLike. When processing the documentation elements for elements which are members of + that class, an ODD processor is required to extend the attList (or equivalent) for such + elements to include any attributes defined by the classSpec elements concerned. There is a + single global attribute class, att.global, to which some modules contribute + additional attributes when they are included in a schema.

+ + + + + + + + + + + + + + + + + + + + + + +
+
+ Macro Specifications +

The macroSpec element is used to declare and document predefined strings or patterns not + otherwise documented by the elements described in this section. A corresponding macroRef + element may be used to select a specific named pattern from those available. Patterns are used as a + shorthand chiefly to describe common content models and datatypes, but may be used for any purpose. The + following elements are used to represent patterns: + + + +

+
+
+ Building a TEI Schema + +

The specification elements, and some of their children, are all members of the att.identified class, from which they inherit the following attributes: + + This attribute class is a subclass of the att.combinable class + from which it (and some other elements) inherits the following attribute: + + This attribute class, in turn, is a subclass of the att.deprecated class, from which it inherits the following attribute: + + The validUntil attribute may be used to signal an intent to remove a construct + from future versions of the schema being specified.

+ + + +

The elementSpec, attDef and schemaSpec specification elements also have an + attribute which determines which namespace to which the object being created will belong. In the case of + schemaSpec, this namespace is inherited by all the elements created in the schema, unless + they have their own ns. + + +

+ +

These attributes are used by an ODD processor to determine how declarations are to be combined to form + a schema or DTD, as further discussed in this section.

+ +
+ TEI customizations +

As noted above, a TEI schema is defined by a schemaSpec element containing an arbitrary + mixture of explicit declarations for objects (i.e. elements, classes, patterns, or macro + specifications) and references to other objects containing such declarations (i.e. references to + specification groups, or to modules). A major purpose of this mechanism is to simplify the process of + defining user customizations, by providing a formal method for the user to combine new declarations + with existing ones, or to modify particular parts of existing declarations.

+

In the simplest case, a user-defined schema might just combine all the declarations from two + nominated modules: + + + + + An ODD processor, given such a document, should combine the declarations which belong to the named + modules, and deliver the result as a schema of the requested type. It may also generate documentation + for the elements declared by those modules. No source is specified for the modules, and the schema + will therefore combine the declarations found in the most recent release version of the TEI Guidelines + known to the ODD processor in use.

+

The value specified for the source attribute, when it is supplied as a URL, specifies any + convenient location from which the relevant ODD files may be obtained. For the current release of the + TEI Guidelines, a URL in the form + http://www.tei-c.org/Vault/P5/x.y.z/xml/tei/odd/p5subset.xml may be used, where + x.y.z represents the P5 version number, e.g. 1.3.0. Alternatively, if the + ODD files are locally installed, it may be more convenient to supply a value such as + ../ODDs/p5subset.xml". +

+

The value for the source attribute may be any form of URI. A set of TEI-conformant + specifications in a form directly usable by an ODD processor must be available at the location + indicated. When no source value is supplied, an ODD processor may either raise an error or + assume that the location of the current release of the TEI Guidelines is intended.

+

If the source is specified in the form of a private URI, the form recommended is + aaa:x.y.z, where aaa is a prefix indicating the markup language in use, + and x.y.z indicates the version number. For example, tei:1.2.1 should be + used to reference release 1.2.1 of the current TEI Guidelines. When such a URI is used, it will + usually be necessary to translate it before such a file can be used in blind interchange.

+

The effect of a moduleRef element is to include in the schema all declarations provided by + that module. This may be modified by means of the attributes include and except + which allow the encoder to supply an explicit lists of elements from the stated module which are to be + included or excluded respectively. For example: + + + + + The schema specified here will include all the elements supplied by the core module except for + add, del, orig, and reg. It will also include only the + linkGrp and link elements from the linking module.

+

Alternatively, the element elementRef may be used to indicate explicitly which elements are + to be included in a schema. The same effect as the preceding example might thus be achieved by the + following: + + + + + + Note that in this last case, there is no need to specify the name of the module from which the two + element declarations are to be found; in the TEI scheme, element names are unique across all modules. + The module is simply a convenient way of grouping together a number of related declarations.

+

In the same way, a schema may select a subset of the attributes available in a specific class, + using the classRef element to point to an attribute class: + + + + + + + Here, only the corresp attribute is included; the other attributes in the class + are not available. The same effect can be achieved using except: + + + + + + +

+

A schema may also include declarations for new elements, as in the following example: + + + + + + + + A declaration for the element soundClip, which is not defined in the TEI + scheme, will be added to the output schema. This element will also be added to the existing TEI class + model.pPart.data, and will thus be available in TEI conformant + documents. Attributes from existing TEI classes could be added to the new element using attRef: + + + + + + + + + + + This will provide the source attribute from the att.global.source class on the new + soundClip element. +

+

A schema might also include re-declarations of existing elements, as in the following example: + + + + + + + + + The effect of this is to redefine the content model for the element head as plain text, by + over-riding the content child of the selected elementSpec. The attribute + specification mode="change" has the effect of over-riding only those children elements of + the elementSpec which appear both in the original specification and in the new specification + supplied above: content in this example. Note that if the value for mode were + replace, the effect would be to replace all children elements of the original + specification with the the children elements of the new specification, and thus (in this example) to + delete all of them except content.

+

A schema may not contain more than two declarations for any given component. The value of the + mode attribute is used to determine exactly how the second declaration (and its + constituents) should be combined with the first. The following table summarizes how a processor should + resolve duplicate declarations; the term identifiable refers to those elements which can + have a mode attribute: + + mode value + existing declaration + effect + + + add + no + add new declaration to schema; process its children in add mode + + + add + yes + raise error + + + replace + no + raise error + + + replace + yes + retain existing declaration; process new children in replace mode; ignore existing + children + + + change + no + raise error + + + change + yes + process identifiable children according to their modes; process unidentifiable children in + replace mode; retain existing children where no replacement or change is provided + + + delete + no + raise error + + + delete + yes + ignore existing declaration and its children + +
+

+
+
+ Combining TEI and Non-TEI Modules +

In the simplest case, all that is needed to include a non-TEI module in a schema is to reference its + RELAX NG source using the url attribute on moduleRef. The following specification, + for example, creates a schema in which declarations from the non-TEI module svg11.rng (defining Standard Vector Graphics) are included. To avoid any risk of name + clashes, the schema specifies that all TEI patterns generated should be prefixed by the string "TEI_". + + + + + + + + +

+

This specification generates a single schema which might be used to validate either a TEI document + (with the root element TEI), or an SVG document (with a root element svg:svg), but + would not validate a TEI document containing svg:svg or other elements from the + SVG language. For that to be possible, the svg:svg element must become a member of a TEI + model class (), so that it may be referenced by other TEI elements. To achieve + this, we modify the last moduleRef in the above example as follows: + + + + + + + + + +

+

This states that when the declarations from the svg11.rng module are + combined with those from the other modules, the declaration for the model class model.graphicLike in the TEI module should be extended to include the element + svg:svg as an alternative. This has the effect that elements in the TEI scheme which define + their content model in terms of that element class (notably figure) can now include it. A + RELAX NG schema generated from such a specification can be used to validate documents in which the TEI + figure element contains any valid SVG representation of a graphic, embedded within an + svg:svg element.

+ +
+
+ Linking Schemas to XML Documents +

Schemas can be linked to XML documents by means of the ?xml-model? processing + instruction described in the W3C Working Group Note Associating Schemas with XML + documents (). ?xml-model? can be used for any type of schema, and may be used for multiple schemas: + +]]> + This example includes a standard RELAX NG schema, a Schematron schema which might be used for checking + that all pointing attributes point at existing targets, and also a link to the TEI ODD file from which + the RELAX NG schema was generated. See also for details of another method + of linking an ODD specification into your file by including a schemaSpec element in + encodingDesc.

+
+
+
+ Module for Documentation Elements +

The module described in this chapter makes available the following components: + + Documentation Elements + Documentation of TEI and other XML markup languages + Éléments de déclaration d’un modèle + TEI模組說明 + Documentazione dei moduli TEI + Documentação dos módulos TEI + タグ定義モジュール + + The selection and combination of modules to form a TEI schema is + described in .

The elements described + in this chapter are all members of one of three classes: model.oddDecl, model.oddRef, or model.phrase.xml, with the exceptions of + schemaSpec (a member of model.divPart) and both eg and egXML + (members of model.common and model.egLike). All of these classes are + declared along with the other general TEI classes, in the basic + structure module documented in .

+

In addition, some elements are members of the att.identified class, which is documented in + above.

+ + + + + + + +
+
diff --git a/P5/Source/Guidelines/fr/TS-TranscriptionsofSpeech.xml b/P5/Source/Guidelines/fr/TS-TranscriptionsofSpeech.xml deleted file mode 120000 index c2ac9637a1..0000000000 --- a/P5/Source/Guidelines/fr/TS-TranscriptionsofSpeech.xml +++ /dev/null @@ -1 +0,0 @@ -../en/./TS-TranscriptionsofSpeech.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/TS-TranscriptionsofSpeech.xml b/P5/Source/Guidelines/fr/TS-TranscriptionsofSpeech.xml new file mode 100644 index 0000000000..282af7921b --- /dev/null +++ b/P5/Source/Guidelines/fr/TS-TranscriptionsofSpeech.xml @@ -0,0 +1,1470 @@ + + + + +
+Transcriptions of Speech + +

The module described in this chapter is intended for use with a +wide variety of transcribed spoken material. It should be stressed, +however, that the present proposals are not intended to support +unmodified every variety of research undertaken upon spoken material +now or in the future; some discourse analysts, some phonologists, and +doubtless others may wish to extend the scheme presented here to +express more precisely the set of distinctions they wish to draw in +their transcriptions. Speech regarded as a purely acoustic phenomenon +may well require different methods from those outlined here, as may +speech regarded solely as a process of social interaction. +

+

This chapter begins with a discussion of some of the problems +commonly encountered in transcribing spoken language (section ). Section documents some +additional TEI header elements which may be used to document the +recording or other source from which transcribed text is taken. +Section describes the basic structural elements +provided by this module. Finally, section of this +chapter reviews further problems specific to the encoding of spoken +language, demonstrating how mechanisms and elements discussed +elsewhere in these Guidelines may be applied to them.

+ + +
General Considerations and Overview +

There is great variation in the ways different researchers have +chosen to represent speech using the written medium.For a +discussion of several of these see ; ; and +. This +reflects the special difficulties which apply to the encoding or transcription of speech. Speech varies according to +a large number of dimensions, many of which have no counterpart in +writing (for example, tempo, loudness, pitch, etc.). The audibility of +speech recorded in natural communication situations is often less than +perfect, affecting the accuracy of the transcription. Spoken material +may be transcribed in the course of linguistic, acoustic, +anthropological, psychological, ethnographic, journalistic, or many +other types of research. Even in the same field, the interests and +theoretical perspectives of different transcribers may lead them to +prefer different levels of detail in the transcript and different styles +of visual display. The production and comprehension of speech are +intimately bound up with the situation in which speech occurs, far more +so than is the case for written texts. A speech transcript must +therefore include some contextual features; determining which are +relevant is not always simple. Moreover, the ethical problems in +recording and making public what was produced in a private setting and +intended for a limited audience are more frequently encountered in +dealing with spoken texts than with written ones. +

+

Speech also poses difficult structural problems. Unlike a written +text, a speech event takes place in time. Its beginning and end may be +hard to determine and its internal composition difficult to define. +Most researchers agree that the utterances or turns of +individual speakers form an important structural component in most kinds +of speech, but these are rarely as well-behaved (in the structural +sense) as paragraphs or other analogous units in written texts: +speakers frequently interrupt each other, use gestures as well as words, +leave remarks unfinished and so on. Speech itself, though it may be +represented as words, frequently contains items such as vocalized pauses +which, although only semi-lexical, have immense importance in the +analysis of spoken text. Even non-vocal elements such as gestures may +be regarded as forming a component of spoken text for some analytic +purposes. +Below the level of the individual utterance, speech may be segmented +into units defined by phonological, prosodic, or syntactic phenomena; +no clear agreement exists, however, even as to appropriate names for +such segments. +

+ +

Spoken texts transcribed according to the guidelines presented here +are organized as follows. The overall structure of a TEI spoken text +is identical to that of any other TEI text: the TEI element +for a spoken text contains a teiHeader element, followed by a +text element. Even texts primarily composed of transcribed +speech may also include conventional front and back matter, and may +even be organized into divisions like printed texts.

+

We may say, therefore, that these Guidelines regard transcribed +speech as being composed of arbitrary high-level units called texts.textsas +organizing unit for spoken material A spoken +text might typically be a conversation between a small number +of people, a lecture, a broadcast TV item, or a similar event. Each +such unit has associated with it a teiHeader providing +detailed contextual information such as the source of the transcript, +the identity of the participants, whether the speech is scripted or +spontaneous, the physical and social setting in which the discourse +takes place and a range of other aspects. Details of the header +in general are provided in chapter ; the +particular elements it provides for use with spoken texts are +described below (). Details concerning +additional elements which may be used for the documentation of participant and +contextual information are given in . +

+ +

Defining the bounds of a spoken text is frequently a matter of +arbitrary convention or convenience. In public or semi-public contexts, +a text may be regarded as synonymous with, for example, a lecture, a broadcast item, +a meeting, etc. In informal or private +contexts, a text may be simply a conversation involving a specific group +of participants. Alternatively, researchers may elect to define spoken +texts solely in terms of their duration in time or length in words. By +default, these Guidelines assume of a text only that: + +it is internally cohesive, +it is describable by a single header, and +it represents a single stretch of time with no significant +discontinuities. +

+ +

Within a text it may be necessary to identify subdivisions +of various kinds, if only for convenience of handling. The neutral +div element discussed in section is +recommended for this purpose. It may be found useful also for +representing subdivisions relating to discourse structure, speech act +theory, transactional analysis, etc., provided only that these divisions +are hierarchically well-behaved. Where they are not, as is often the +case, the mechanisms discussed in chapters and + may be used. +

+ +

A spoken text may contain any of the following components: + +utterances +pauses +vocalized but non-lexical phenomena such as coughs +kinesic (non-verbal, non-lexical) phenomena such as gestures +entirely non-linguistic incidents occurring during and possibly +influencing the course of speech +writing, regarded as a special class of incident in that it can +be transcribed, for example captions or overheads displayed during +a lecture +shifts or changes in vocal quality +

+

Elements to represent all of these features of spoken language are +discussed in section below. +

+

An utterance (tagged u) may contain lexical items +interspersed with pauses and non-lexical vocal sounds; during an +utterance, non-linguistic incidents may occur and written materials may be +presented. The u element can thus contain any of the other +elements listed, interspersed with a transcription of the lexical items +of the utterance; the other elements may all appear between utterances +or next to each other, but except for writing they do not +contain any other elements nor any data. +

+ +

A spoken text itself may be without substructure, that is, it may +consist simply of units such as utterances or pauses, not grouped +together in any way, or it may be subdivided. If the notion of what +constitutes a text in spoken discourse is +inevitably rather an arbitrary one, the notion of formal subdivisions +within such a text may appear even more debatable. +Nevertheless, such divisions may be useful for such types of discourse +as debates, broadcasts, etc., where structural subdivisions can easily +be identified, or more generally wherever it is desired to aggregate +utterances or other parts of a transcript into units smaller than a +complete text. Examples might include +conversations or discourse fragments, or more narrowly, +that part of the conversation where topic x was discussed, +provided only that the set of all such divisions is coextensive with +the text. +

+

Each such division of a spoken text should be represented by the +numbered or unnumbered div elements defined in chapter . For some detailed kinds of analysis a hierarchy of +such divisions may be found useful; nested div elements may +be used for this purpose, as in the following example showing how a +collection made up of transcribed sound bites +taken from speeches given by a politician on different occasions +might be encoded. Each extract is regarded as a distinct +div, nested within a single composite div as +follows:

+
+
+
+
+
+
+
+

+

As a member of the class att.declaring, the +div element may also carry a decls attribute, for +use where the divisions of a text do not all share the same set of the +contextual declarations specified in the TEI header. (See further +section ). +

+ +
+ +
Documenting the Source of Transcribed Speech +

Where a computer file is derived from a spoken text rather than a +written one, it will usually be desirable to record additional +information about the recording or broadcast which constitutes its +source. Several additional elements are provided for this purpose +within the source description component of the TEI header: + + + + + + +As a member of the att.duration class, +the recording element inherits the following attribute: + + + +

+

Note that detailed information about the participants or setting of +an interview or other transcript of spoken language should be recorded +in the appropriate division of the profile description, discussed in +chapter , rather than as part of the source +description. The source description is used to hold information only +about the source from which the transcribed speech was taken, for +example, any script being read and any technical details of how the +recording was produced. If the source was a previously-created +transcript, it should be treated in the same way as any other source +text. +

+

The scriptStmt element should be used where it is known that +one or more of the participants in a spoken text is speaking from a +previously prepared script. The script itself should be documented in +the same way as any other written text, using one of the three citation +tags mentioned above. Utterances or groups of utterances may be linked +to the script concerned by means of the decls attribute, +described in section . + + + + CNN Network News + News headlines + 12 Jun 91 + + + +

+

The recordingStmt is used to group together information +relating to the recordings from which the spoken text was transcribed. +The element may contain either a prose description or, more helpfully, +one or more recording elements, each corresponding with a +particular recording. The linkage between utterances or groups of +utterances and the relevant recording statement is made by means of the +decls attribute, described in section . +

+

The recording element should be used to provide a +description of how and by whom a recording was made. This information +may be provided in the form of a prose description, within which such items as statements of +responsibility, names, places, and dates may be identified using the +appropriate phrase-level tags. Alternatively, a selection of elements +from the model.recordingPart class may be +provided. This element class makes available the following elements: + + + + + + + +

+

Specialized +collections may wish to add further sub-elements to these major +components. These elements should be used only for +information relating to the recording process itself; information about +the setting or participants (for example) is recorded elsewhere: see +sections and . + + +

U-matic recording made by college audio-visual department staff, + available as PAL-standard VHS transfer or sound-only cassette

+ + + + + Location recording by + Sound Services Ltd. + + +

Multiple close microphones mixed down to stereo Digital + Audio Tape, standard play, 44.1 KHz sampling frequency

+ + 12 Jan 1987 + + + + +14 Feb 2001 + + +17 Feb 2001 + + +22 Feb 2001 + + +

+

When a recording has been made from a public broadcast, details of +the broadcast itself should be supplied within the recording +element, as a nested broadcast element. A broadcast is closely +analogous to a publication and the broadcast element should +therefore contain one or the other of the bibliographic citation +elements bibl, biblStruct, or biblFull. The +broadcasting agency responsible for a broadcast is regarded as its +author, while other participants (for example interviewers, +interviewees, script writers, directors, producers, etc.) should be specified using the +respStmt or editor element with an appropriate +resp (see further section ). + +

Recorded from FM Radio to digital tape

+ + + Interview on foreign policy BBC Radio 5 + interviewerRobin Day + intervieweeMargaret Thatcher + The World Tonight + First broadcast on 27 Nov 1989 + + +

+

When a broadcast contains several distinct recordings (for example a +compilation), additional recording elements may be further +nested within the broadcast element. + + + + + + + + +

+

The transcriptionDesc element can be used to document the particular transcription conventions (use of space, +punctuation, special characters etc.) used in making the transcription. A number of sets of such conventions have been defined +within particular research communities, or by users of particular transcription tools. The attributes ident +and version may be used to refer to such conventions in a machine tractable way, where this is appropriate. + + + + + +

+ + + + + + + + + +
+ +
Elements Unique to Spoken Texts +

The following elements characterize spoken texts, transcribed +according to these Guidelines: + +

+

The u element may appear directly within a spoken text, +and may contain any of the others; the others may also appear directly +(for example, a vocal may appear between two utterances) but cannot +contain a u element. In terms of the basic TEI model, +therefore, we regard the u element as analogous to a +paragraph, and the others as analogous to phrase +elements, but with the important difference that they can exist either +as siblings or as children of utterances. The class model.divPart.spoken provides the u +element; the class model.global.spoken +provides the six other elements listed above.

+ +

As members of the att.ascribed class, +all of these elements share the following attributes: + +As members of the att.typed, att.timed and att.duration classes, +all of these elements except shift share the following attribute: + + + + + +

+

Each of these elements is further discussed and specified in +sections to . +

+

We can show the relationship between four of these constituents of +speech using the features eventive, communicative, anthropophonic (for sounds produced by the human +vocal apparatus), and lexical: + + eventivecommunicativeanthropophoniclexical +incident+--- +kinesic++-- +vocal+++- +utterance++++ +
+The differences are not always clear-cut. Among incidents might be included actions like slamming +the door, which can certainly be communicative. Vocals include coughing and sneezing, which +arevocal eventsin +transcription of speech usually +involuntary noises. Equally, the distinction between utterances and +vocals is not always clear, although for many analytic purposes it +will be convenient to regard them as distinct. Individual scholars +may differ in the way borderlines are drawn and should declare their +definitions in the editorialDecl element of the header (see +). +

+

The following short extract exemplifies several of these elements. It +is recoded from a text originally transcribed in the CHILDES +format.The original is a conversation between two children and +their parents, recorded in 1987, and discussed in + +Each utterance is encoded using a u element (see section ). The speakers are defined using the +listPerson element discussed in and each is +given a unique identifier also used to identify their speech. Pauses marked by the transcriber are indicated +using the pause element (see section ). +Non-verbal vocal effects such as the child's meowing are indicated +either with orthographic transcriptions or with the vocal +element, and entirely non-linguistic but significant incidents such as +the sound of the toy cat are represented by the incident +elements (see section ). + + + + + + + + +you +never take this cat for show and tell + meow meow +yeah well I dont want to +toy cat has bell in tail which continues to make a tinkling sound +meows +because it is so old +how boutabout + your cat yours is new + shows Father the cat +thats darling +no mine isnt old +mine is just um a little dirty + +

+

This example also uses some elements common to all TEI texts, +notably the reg tag for editorial regularization. Unusually +stressed syllables have been encoded with the emph +element. The seg element has also been used to segment the +last utterance. Further discussion of all of such options is provided +in section . +

+

Contextual information is of particular importance in spoken texts, +and should be provided by the TEI header of a text. In general, all of +the information in a header is understood to be relevant to the whole +of the associated text. The element u as a member of the +att.declaring class, may however specify a +different context by means of the decls attribute (see +further section ). +

+
Utterances +

Each distinct utterance in a spoken text is represented +by a u element, described as follows: + + +

+

Use of the who attribute to associate the utterance with a +particular speaker is recommended but not required. Its use implies as +a further requirement that all speakers be identified by a +person or personGrp element, typically in the TEI +header (see section ), but it may also point to another +external source of information about the speaker. Where utterances or +other parts of the transcription cannot be +attributed with confidence to any particular participant or group of +participants, the encoder may choose to create personGrp elements +with xml:id attributes such as various or unknown, +and perhaps give the root listPerson element an xml:id value of +all, then point to those as appropriate using who.

+ +

The trans attribute is provided as a means of +characterizing the transition from one utterance to the next at a +simpler level of detail than that provided by the temporal alignment +mechanism discussed in section . The value specified +applies to the transition from the preceding utterance into the +utterance bearing the attribute. For example:For +the most part, the examples in this chapter use no sentence punctuation +except to mark the rising intonation often found in interrogative +statements; for further discussion, see section . +Have you heard the +the election results? yes +it's a disaster +it's a miracle +In this example, utterance ts_b1 latches on to utterance +ts_a1, while there is a marked pause between +ts_b1 and ts_a2. ts_b2 and +ts_a2 overlap, but by an unspecified amount. For ways of +providing a more precise indication of the degree of overlap, see +section . +

+

An utterance may contain either running text, or text within which +other basic structural elements are nested. Where such nesting occurs, +the who attribute is considered to be inherited for the +elements pause, vocal, shift, and +kinesic; that is, a pause or shift (etc.) within an utterance +is regarded as being produced by that speaker only, while a pause +between utterances applies to all speakers. +

+

Occasionally, an utterance may seem to contain other utterances, +for example where one speaker interrupts himself, or +when another speaker produces a back-channel +while they are still speaking. The present version of these +Guidelines does not support nesting of one u element within +another. The transcriber must therefore decide whether such +interruptions constitute a change of utterance, or whether other +elements may be used. In the case of self-interruption, the +shift element may be used to show that the speaker has +changed the quality of their speech: +Listen to this The government is +confident, he said, that the current economic problems will be +completely overcome by June what nonsense +Alternatively the incident element described in section might be used, without transcribing the read material: Listen to this +reads aloud from newspaper what +nonsense +

+

Often, back-channelling is only semi-lexicalized and may therefore be +represented using the vocal element: +So what could I have done tut-tutting about it anyway? +Where this is not possible, it is simplest to regard the back-channel +as a distinct utterance.

+
+
Pausing +

Speakers differ very much in their rhythm and in particular in the +amount of time they leave between words. The following element is +provided to mark occasions where the transcriber judges that +speech has been paused, irrespective of the actual amount of silence: + +A pause contained by an utterance applies to the speaker of that +utterance. A pause between utterances applies to all speakers. The +type attribute may be used to categorize the pause, for +example as short, medium, or long; alternatively the attribute +dur may be used to indicate its length more exactly, as in +the following example: +Okay U-mthe scene opens up + with um you see +a tree okay? + +If detailed synchronization of pausing with other vocal phenomena is +required, the alignment mechanism defined at section +and discussed informally below should be used. Note that the +trans attribute mentioned in the previous section may also be +used to characterize the degree of pausing between (but not within) +utterances. +

+
Vocal, Kinesic, Incident +

The presence of +non-transcribed semi-lexical or non-lexical phenomena either between or +within utterances may be indicated with the following three elements. + +

+

The who attribute should be used to specify the person or +group responsible for a vocal, kinesic, or incident which is contained +within an utterance, if this differs from that of the enclosing +utterance. The attribute must be supplied for a vocal, kinesic, or incident +which is not contained within an utterance. +

+

The iterated attribute may be used to indicate that the +vocal, kinesic, or incident is repeated, for example laughter as opposed to laugh. +These should both be distinguished from laughing, +where what is being encoded is a shift in voice quality. For this last +case, the shift element discussed in section should be used. +

+

A child desc element may be used to supply a conventional +representation for the phenomenon, for example: + +burp, click, cough, exhale, giggle, gulp, + inhale, laugh, sneeze, sniff, snort, sob, swallow, throat, yawn + +ah, aha, aw, eh, ehm, er, erm, hmm, huh, + mm, mmhm, oh, ooh, oops, phew, tsk, uh, uh-huh, uh-uh, um, urgh, + yup +Researchers may prefer to regard some semi-lexical phenomena as +words within the bounds of the u element. +See further the discussion at section below. As +for all basic categories, the definition should be made clear in the +encodingDesc element of the TEI header. +

+

Some typical examples follow: +This is just delicious +telephone rings +I'll get it +I used to cough smoke a lot +sniffsHe thinks he's tough +snorts + + + + + + + + + + +Note that Ann's snorting could equally well be encoded as follows: + + snorts + +

+

The extent to which encoding of incidents or kinesics is included in a +transcription will depend entirely on the purpose for which the +transcription was made. As elsewhere, this will depend on the +particular research agenda and the extent to which their presence is +felt to be significant for the interpretation of spoken interactions. +

+
Writing +

Written text may also be encountered when speech is transcribed, for +example in a television broadcast or cinema performance, or where one +participant shows written text to another. The writing element +may be used to distinguish such written elements from the spoken text in +which they are embedded. + + +For example, if speaker A in the breakfast table conversation in section + above had simply shown the newspaper passage to her +interlocutor instead of reading it, the interaction might have been +encoded as follows: +look at this + +Government claims economic problems +over by June what nonsense! +

+

If the source of the writing being displayed is known, +bibliographic information +about it may be stored in a listBibl within the +sourceDesc element of the TEI header, and then pointed to +using the source attribute. For example, in the following +imaginary example, a lecturer displays two different versions of the same +passage of text: + + + +Shakespeare First Folio text +Shakespeare Second Folio text + + + +[...] now compare the punctuation of lines 12 and 14 in these two +versions of page 42... +[...] +[...] + +

+
+
Temporal Information +

As noted above, utterances, vocals, pauses, kinesics, incidents, +and writing elements all inherit attributes providing information +about their position in time from the classes att.timed and att.duration. These attributes can be used to +link parts of the transcription very exactly with points on a +timeline, or simply to indicate their duration. Note that if +start and end point to when elements +whose temporal distance from each other is specified in a timeline, +then dur is ignored. +

+

The anchor element (see ) may be used as +an alternative means of aligning the start and end of timed elements, +and is required when the temporal alignment involves points within an +element. +

+

For further discussion of temporal alignment and synchronization +see below.

+
+
Shifts +

A common requirement in transcribing spoken language is to mark +positions at which a variety of prosodic features change. Many +paralinguistic features (pitch, prominence, loudness, etc.) characterize +stretches of speech which are not co-extensive with utterances or any of +the other units discussed so far. One simple method of encoding such +units is simply to mark their boundaries. An empty element called +shift is provided for this purpose. + +A shift element may appear within an utterance or a segment to +mark a significant change in the particular feature defined by its +attributes, which is then understood to apply to all subsequent +utterances for the same speaker, unless changed by a new shift for the +same feature in the same speaker. Intervening utterances by other +speakers do not normally carry the same feature. +For example: +Elizabeth +Yes +Come and try this + come on +In this example, the word Elizabeth is spoken loudly, the +words Yes and Come and try this with +normal volume, and the words come on very loudly. +

+

The values proposed here for the feature attribute are +based on those used by the Survey of English Usage (see further +Boase 1990); this list may be revised or supplemented using +the methods outlined in section .

+

The new attribute specifies the new state of the feature +following the shift. If this attribute has the special value normal, the +implication is that the feature concerned ceases to be remarkable at this point.

+

A list of suggested values for each of the features proposed follows: + +tempo + + +allegro (fast) + +very fast +accelerando (getting faster) +lento (slow) +very slow +rallentando (getting slower) +loud (for loudness): + +forte (loud) +very loud +crescendo (getting louder) +piano (soft) +very soft +diminuendo (getting softer) +pitch (for pitch range): + +high pitch-range +low pitch-range +wide pitch-range +narrow pitch-range +ascending +descending +monotonous +scandent, each succeeding syllable higher than + the last, generally ending in a falling tone +tension: + +slurred +lax, a little slurred +tense +very precise +staccato, every stressed syllable being doubly + stressed +legato, every syllable receiving more or less equal + stress +rhythm: + +beatable rhythm +arrhythmic, particularly halting +spiky rising, with markedly higher unstressed + syllables +spiky falling, with markedly lower unstressed + syllables +glissando rising, like spiky rising but the + unstressed syllables, usually several, also rise + in pitch relative to each other +glissando falling, like spiky falling but with the + unstressed syllables also falling in pitch relative + to each other +voice (for voice quality): + +whisper +breathy +husky +creaky +falsetto +resonant +unvoiced laugh or giggle +voiced laugh +tremulous +sobbing +yawning + sighing +

+

A full definition of the sense of the values provided for each +feature may be provided either in the encoding description section of the +text header (see section ) or as part of a TEI customization, + as described in section . + +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+
+
Elements Defined Elsewhere +

This section describes the following features characteristic of +spoken texts for which elements are defined elsewhere in these +Guidelines: + +segmentation below the utterance level +synchronization and overlap +regularization of orthography The elements +discussed here are not provided by the module for spoken texts. Some +of them are included in the core module and others are contained in +the modules for linking and for analysis respectively. The selection +of modules and their combination to define a TEI schema is discussed +in section . + + +

+
Segmentation +

For some analytic purposes it may be desirable to subdivide the +divisions of a spoken text into units smaller than the individual +utterance or turn. Segmentation may be performed for a number of +different purposes and in terms of a variety of speech phenomena. +Common examples include units defined both prosodically (by intonation, +pausing, etc.) and syntactically (clauses, phrases, etc.) The term +macrosyntagm has been used by a number of researchers to +define units peculiar to speech transcripts.The term was +apparently first proposed by , +where it is defined as follows: A text can be analysed as a sequence +of segments which are internally connected by a network of syntactic +relations and externally delimited by the absence of such relations with +respect to neighbouring segments. Such a segment is a syntactic unit +called a macrosyntagm (trans. S. Johansson).

+

These Guidelines propose that such analyses be performed in terms of +neutrally-named segments, represented by the seg +element, which is discussed more fully in section . +This element may take a type attribute to specify the kind of +segmentation applicable to a particular segment, if more than one is +possible in a text. A full definition of the segmentation scheme or +schemes used should be provided in the segmentation element of +the editorialDecl element in the TEI header (see ).

+

In the first example below, an utterance has been segmented according +to a notion of syntactic completeness not necessarily marked by the +speech, although in this case a pause has been recorded between the two +sentence-like units. In the second, the segments are defined +prosodically (an acute accent +has been used to mark the position immediately following the syllable +bearing the primary accent or stress), and may be thought of as +tone units. + + we went to the pub yesterday + + there was no one there + + + although its an old ide´a + it hasnt been on the mar´ket very long + + +In either case, the segmentation element in the header of the +text should specify the principles adopted to define the segments marked +in this way.

+

When utterances are segmented end-to-end in the same way as the +s-units in written texts, the s element discussed in chapter + may be used, either as an alternative or in addition to +the more general purpose seg element. The s element +is available without formality in all texts, but does not allow segments +to nest within each other. +

+

Where segments of different kinds are to be distinguished within the +same stretch of speech, the type attribute may be used, as in +the following example: + +I think +this chap was writing +and he said hello said +hello +and he said +I'm going to a gate + at twenty past seven +he said +ok +right away +and so on they went +and they were + writing there + + +In this example, recoded from a corpus of language-impaired speech +prepared by Fletcher and Garman, the speaker's utterance has been fully +segmented into clausal (type="C") +or minor (type="M") units.

+ +

For some features, it may be +more appropriate or convenient to introduce a new element in a custom namespace: + + +and he said +I'm going to a +gate +at twenty past seven + + + +Here, ext:paraphasia has been used to define a particular +characteristic of this corpus for which no element exists in the TEI scheme. +See further chapter for a discussion of the way in +which this kind of user-defined extension of the TEI scheme may be +performed and chapter for the mechanisms on which it +depends.

+

This example also uses the core elements gap and +del to mark editorial decisions concerning matter completely +omitted from the transcript (because of inaudibility), and words which +have been transcribed but which the transcriber wishes to exclude from +the segment because they are repeated, respectively. See +section for a discussion of these and related +elements.

+

It is often the case that the desired segmentation does not respect +utterance boundaries; for example, syntactic units may cross utterance +boundaries. For a detailed discussion of this problem, and the various +methods proposed by these Guidelines for handling it, see chapter +. Methods discussed there include these: + +milestone tags may be used; +the special-purpose shift tag discussed +in section is an extension of this method +where several discontinuous segments are to be grouped +together to form a syntactic unit (e.g. a phrasal verb with interposed +complement), the join element may be used +

+
Synchronization and Overlap +

A major difference between spoken and written texts is the importance +of the temporal dimension to the former. As a very simple example, +consider the following, first as it might be represented in a +playscript: + Jane: Have you read Vanity Fair? +Stig: Yes +Lou: (nods vigorously) +To encode this, we first define the participants: + + + + + +Let us assume that Stig and Lou respond to Jane's question before she +has finished asking it—a fairly normal situation in spontaneous +speech. The simplest way of representing this overlap +would be to use the trans attribute previously discussed: +have you read Vanity Fair +yes + +However, this does not allow us to indicate either the extent to which +Stig's utterance is overlapped, nor does it show that there are in +fact three things which are synchronous: the end of Jane's utterance, +Stig's whole utterance, and Lou's kinesic. To overcome these problems, +more sophisticated techniques, employing the mechanisms for pointing and +alignment discussed in detail in section , are needed. +If the module for linking has been enabled (as described in +section above), one way to represent the simple +example above would be as follows: +have you read Vanity Fair +yes +nods head vertically

+

For a full discussion of this and related mechanisms, section should be consulted. The rest of the present +section, which should be read in conjunction with that more detailed +discussion, presents a number of ways in which these mechanisms may be +applied to the specific problem of representing temporal alignment, +synchrony, or overlap in transcribing spoken texts.

+

In the simple example above, the first utterance (that with +identifier utt1) contains an anchor element, the function of +which is simply to mark a point within it. The synch +attribute associated with this anchor point specifies the identifiers of +the other two elements which are to be synchronized with it: +specifically, the second utterance (utt2) and the kinesic (k1). Note that +one of these elements has content and the other is empty.

+

This example demonstrates only a way of indicating a point within one +utterance at which it can be synchronized with another utterance and a +kinesic. For more complex kinds of alignment, involving possibly +multiple synchronization points, an additional element is provided, +known as a timeline. This consists of a series of +when elements, each representing a point in time, and bearing +attributes which indicate its exact temporal position relative to other +elements in the same timeline, in addition to the sequencing implied by +its position within it.

+

For example: + + + + + + +This timeline represents four points in time, named TS-P1, TS-P2, TS-P6, and TS-P3 +(as with all attributes named xml:id in the TEI scheme, the +names must be unique within the document but have no other +significance). TS-P1 is located absolutely, at 12:20:01:01 BST. TS-P2 is 4.5 +seconds later than TS-P2 (i.e. at 12:20:46). TS-P6 is +at some unspecified time later than TS-P2 and previous to TS-P3 (this is +implied by its position within the timeline, as no attribute values have +been specified for it). The fourth point, TS-P3, is 1.5 seconds +later than TS-P6.

+

One or more such timelines may be specified within a spoken text, to +suit the encoder's convenience. If more than one is supplied, the +origin attribute may be used on each to specify which other +timeline element it follows. The unit attribute +indicates the units used for timings given on when elements +contained by the alignment map. Alternatively, to avoid the need to +specify times explicitly, the interval attribute may be used +to indicate that all the when elements in a time line are a +fixed distance apart.

+

Three methods are available for aligning points or elements within a +spoken text with the points in time defined by the timeline: + +The elements to be synchronized may specify the identifier +of a when element as the value of one of the start, +end, or synch attributes +The when +element may specify the identifiers of all the elements to be +synchronized with it using the synch attribute +A +free-standing link element may be used to associate the +when element and the elements synchronized with it by +specifying their identifiers as values for its target +attribute.

+

For example, using the timeline given above: This is my turn The start of utterance +TS-U1 is aligned with TS-P2 and its end with +TS-P3. The transition between the words +my and turn occurs at +point TS-P6A, which is synchronous with point +TS-P6 on the timeline.

+

The synchronization represented by the preceding examples could +equally well be represented as follows: + + + + + + +This is my turn +Here, the whole of the object with identifier ts-u1 (the +utterance) has been aligned with two different points, +ts-p2 and ts-p3. This is interpreted to mean +that the utterance spans at least those two points.

+

Finally, a linkGrp may be used as an alternative to the +synch attribute: + + + + + + + + + This is my turn + + + + + + +

+

As a further example of the three possibilities, consider the +following dialogue, represented first as it might appear in a +conventional playscript: +Tom: I used to smoke - - +Bob: (interrupting) You used to smoke? +Tom: (at the same time) a lot more than this. But I never + inhaled the smoke + +A commonly used convention might be to transcribe such a passage as +follows: + (1) I used to smoke [ a lot more than this ] +(2)                 [ you used to smoke ] +(1) but I never inhaled the smoke +Such conventions have the drawback that they are hard to generalize or +to extend beyond the very simple case presented here. Their reliance on +the accidentals of physical layout may also make them difficult to +transport and to process computationally. These Guidelines recommend +the following mechanisms to encode this.

+

Where the whole of one or another utterance is to be synchronized, +the start and end attributes may be used: +I used to smoke a lot more than this +but I never inhaled the smoke +You used to smoke +Note that the second utterance above could equally well be encoded as +follows with exactly the same effect: +You used to smoke

+

If synchronization with specific timing information is required, a +timeline must be included: + + + + +I used to smoke + a lot more than this + but I never inhaled the smoke + + You used to smoke + +(Note that If only the ordering or sequencing of utterances is needed, +then specific timing information shown here in unit, absolute +and interval does not need to be provided.) +

+

As above, since the whole of Bob's utterance is to be aligned, the +start and end attributes may be used as an +alternative to the second pair of anchor elements: +You used to smoke

+

An alternative approach is to mark the synchronization by pointing +from the timeline to the text: + + + + +I used to smoke + a lot more than this + but I never inhaled the smoke +You used to smoke +To avoid deciding whether to point from the timeline to the text or vice +versa, a linkGrp may be used: + + + + + + I used to smoke + a lot more than this + but I never inhaled the smoke + You used to smoke + + + + +

+

Note that in each case, although Bob's utterance follows Tom's +sequentially in the text, it is aligned temporally with its middle, +without any need to disrupt the normal syntax of the text.

+

As a final example, consider the following exchange, first as it +might be represented using a musical-score-like notation, in which +points of synchronization are represented by vertical alignment of the +text: + Stig: This is |my  |turn +Jane:         |Balderdash +Lou :         |No, |it's mine +All three speakers are simultaneous at the words my, +Balderdash, and No; speakers Stig and Lou are +simultaneous at the words turn and it's. +This could be encoded as follows, using pointers from the alignment map +into the text: + + + + + +this is my turn +balderdash + no it's mine +

+
Regularization of Word Forms +

When speech is transcribed using ordinary orthographic notation, as +is customary, some compromise must be made between the sounds produced +and conventional orthography. Particularly when dealing with informal, +dialectal, or other varieties of language, the transcriber will +frequently have to decide whether a particular sound is to be treated as +a distinct vocabulary item or not. For example, while in a given +project kinda may not be worth distinguishing as a +vocabulary item from kind of, isn't may +clearly be worth distinguishing from is not; for some +purposes, the regional variant isnae might also be worth +distinguishing in the same way.

+

One rule of thumb might be to allow such variation only where a +generally accepted orthographic form exists, for example, in published +dictionaries of the language register being encoded; this has the +disadvantage that such dictionaries may not exist. Another is to +maintain a controlled (but extensible) set of normalized forms for all +such words; this has the advantage of enforcing some degree of +consistency among different transcribers. Occasionally, as for example +when transcribing abbreviations or acronyms, it may be felt necessary to +depart from conventional spelling to distinguish between cases where the +abbreviation is spelled out letter by letter (e.g. B B C +or V A T) and where it is pronounced as a single word +(VAT or RADA). Similar considerations +might apply to pronunciation of foreign words +(e.g. Monsewer vs. Monsieur).

+

In general, use of punctuation, capitalization, etc., in spoken +transcripts should be carefully controlled. It is important to +distinguish the transcriber's intuition as to what the punctuation +should be from the marking of prosodic features such as pausing, +intonation, etc.

+

Whatever practice is adopted, it is essential that it be clearly and +fully documented in the editorial declarations section of the header. +It may also be found helpful to include normalized forms of +non-conventional spellings within the text, using the elements for +simple editorial changes described in section (see +further section ).

+
Prosody +

In the absence of conventional punctuation, the marking of prosodic +features assumes paramount importance, since these structure and +organize the spoken message. Indeed, such prosodic features as points +of primary or secondary stress may be represented by specialized +punctuation marks, or other characters such as those provided by the +Unicode Spacing Modifier Letters block. Pauses have already been dealt with in section +; while tone units (or intonational phrases) +can be indicated by the segmentation tag discussed in section +. The shift element discussed in section +may also be used to encode some prosodic features, for example where all +that is required is the ability to record shifts in voice quality.

+ +

In a more detailed phonological transcript, it is common practice +to include a number of conventional signs to mark prosodic features of +the surrounding or (more usually) preceding speech. Such signs may be +used to record, for example, particular intonation patterns, +truncation, vowel quality (long or short) etc. These signs may be +preserved in a transcript either by using conventional punctuation or +by marking their presence by g +elements. Where a transcript +includes many phonetic or phonemic aspects, it will generally be +more convenient to use the appropriate Unicode characters (see +further chapters and ). For +representation of phonemic information, the use of the International +Phonetic Alphabet, which can be represented in Unicode characters, is +recommended.

+

In the following example, special characters have been defined as +follows within the encodingDesc of the TEI header + + low fall intonation + low rise intonation + fall rise intonation + rise fall intonation + lengthened syllable + shortened syllable + + +These declarations might additionally provide information about +how the characters concerned should be rendered, their equivalent +IPA form, etc. In the transcript itself references to them can then +be included as follows: + + + +

Customer WN

+

Assistant K

 + + +
+ C is with a friend + + Excuse me You dont have some + aesthetic specially on early + aesthetics terminology + + No No I'm + afraid + + No Well thanks Oh + you couldnt can we kind of + I mean ask you to order it for us + + Yes if you know the title Yeah + + + + Yes thats fine. just as soon as it comes in we'll send + you a postcard +
+

+

This example, which is taken from a corpus of bookshop service +encounters, +also demonstrates the use of the unclear and gap +elements discussed in section . Where words are so +unclear that only their extent can be recorded, the empty gap +element may be used; where the encoder can identify the words but wishes +to record a degree of uncertainty about their accuracy, the +unclear element may be used. More flexible and detailed +methods of indicating uncertainty are discussed in chapter .

+ + +

For more detailed work, involving a detailed phonological transcript +including representation of stress and pitch patterns, it is probably +best to maintain the prosodic description in parallel with the +conventional written transcript, rather than attempt to embed detailed +prosodic information within it. The two parallel streams may be aligned +with each other and with other streams, for example an acoustic +encoding, using the general alignment mechanisms discussed in section +.

+ + +
+
Speech Management +

Phenomena of speech management include disfluencies such +as filled and unfilled pauses, interrupted or repeated words, +corrections, and reformulations as well as interactional devices asking +for or providing feedback. Depending on the importance attached to such +features, transcribers may choose to adopt conventionalized +representations for them (as discussed in section +above), or to transcribe them using IPA or some other transcription +system. To simplify analysis of the lexical features of a speech +transcript, it may be felt useful to tidy away many +of these disfluencies. Where this policy has been adopted, these +Guidelines recommend the use of the tags for simple editorial +intervention discussed in section , to make explicit +the extent of regularization or normalization performed by the +transcriber.

+

For example, false starts, repetition, and truncated words might all +be included within a transcript, but marked as editorially deleted, in +the following way: +ssee +you you you know +it's he's crazy

+

As previously noted, the gap element may be used to mark +points within a transcript where words have been omitted, for example +because they are inaudible, as in the following example in which 5 seconds of +speech is drowned out by an external event: +

+

The unclear element may be used to mark words which have +been included although the transcriber is unsure of their accuracy: +...and then marbled queen

+

Where a transcriber is believed to have incorrectly identified a +word, the elements corr or sic embedded within a +choice element may be used to indicate +both the original and a corrected form of it: + +SCSIskuzzy + +These elements are further discussed in section . +

+

Finally phenomena such as code-switching, where a +speaker switches from one language to another, may easily be +represented in a transcript by using the foreign element +provided by the core tagset: + +I proposed that wir können + vielleicht go to warsaw +and vienna + + + +

+
+
Analytic Coding +

The recommendations made here only concern the establishment of a +basic text. Where a more sophisticated analysis is needed, more +sophisticated methods of markup will also be appropriate, for example, +using stand-off markup to indicate multiple segmentation of the +stream of discourse, or complex alignment of several segments within it. +Where additional annotations (sometimes called +codes or tags) are used to +represent such features as linguistic word class (noun, verb, etc.), +type of speech act (imperative, concessive, etc.), or information status +(theme/rheme, given/new, active/semi-active/new), etc., a selection from +the general purpose analytic tools discussed in chapters , , and may be used to +advantage. +

+

The general-purpose annotationBlock element may be used to group together a transcription and multiple layers of annotation. It also serves +to divide a transcribed text up into meaningful analytic sections. + + + +

+ +
+
+ +
+ Module for Transcribed Speech +

The module described in this chapter makes available the following components: + + Transcribed Speech + Transcribed Speech + Transcriptions de la parole + 轉錄的言詞 + Trascrizione del parlato + Transcrição do discurso + 発話モジュール + + The selection and combination of modules to form a TEI schema is + described in .

+ + + + + +
+
diff --git a/P5/Source/Guidelines/fr/TitlePageVerso.xml b/P5/Source/Guidelines/fr/TitlePageVerso.xml deleted file mode 120000 index 6cf093865c..0000000000 --- a/P5/Source/Guidelines/fr/TitlePageVerso.xml +++ /dev/null @@ -1 +0,0 @@ -../en/TitlePageVerso.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/TitlePageVerso.xml b/P5/Source/Guidelines/fr/TitlePageVerso.xml new file mode 100644 index 0000000000..5d98709f3a --- /dev/null +++ b/P5/Source/Guidelines/fr/TitlePageVerso.xml @@ -0,0 +1,22 @@ + + + + + + + +
+ Releases of the TEI Guidelines + + + 1990, C.M. Sperberg-McQueen and Lou Burnard + + 1992, C.M. Sperberg-McQueen and Lou Burnard + + 1994, C.M. Sperberg-McQueen and Lou Burnard + + 2001, Lou Burnard, Syd Bauman, and Steven DeRose + + 2007, Lou Burnard and Syd Bauman + +
diff --git a/P5/Source/Guidelines/fr/USE.xml b/P5/Source/Guidelines/fr/USE.xml deleted file mode 120000 index 51bee9af4d..0000000000 --- a/P5/Source/Guidelines/fr/USE.xml +++ /dev/null @@ -1 +0,0 @@ -../en/USE.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/USE.xml b/P5/Source/Guidelines/fr/USE.xml new file mode 100644 index 0000000000..9ae95e93a7 --- /dev/null +++ b/P5/Source/Guidelines/fr/USE.xml @@ -0,0 +1,2315 @@ + + + + +
+ Using the TEI + + +

This section discusses some technical topics concerning the deployment of the TEI markup schema + documented elsewhere in these Guidelines. + + In section we discuss the scope and variety of the TEI customization + mechanisms. + In we define the notions of TEI Conformance and + TEI + Extension. Since the ODD markup description language defined in chapter is fundamental to the way conformance and customization are handled in the TEI + system, these two definitional sections are followed by a section () which + describes the intended behaviour of an ODD processor.

+ + + +
+ Serving TEI files with the TEI Media Type +

In February 2011, the media type application/tei+xml was registered with IANA + for markup languages defined in accordance with the Text Encoding and Interchange + guidelines (RFC 6129). We + recommend that any XML file whose root element is in the TEI namespace be served with the + media type application/tei+xml to enable and encourage automated recognition and + processing of TEI files by external applications.

+
+ +
+ Obtaining the TEI +

As discussed in chapter , all components of the TEI schema are generated + from a single set of TEI XML source files. Schemas can be generated in each of XML DTD + language, W3C schema language, and RELAX NG schema language. Documentation can be generated in + a variety of commonly-used document formats, including HTML, DOCX, or PDF. +

+

TEI components are freely available over the Internet and elsewhere. The canonical home for + the TEI source, the schema fragments generated from it, and example modifications, is the TEI + repository at ; versions are also available in + other formats, along with copies of these Guidelines and related materials, from the TEI web + site at .

+ +
+ + + +
+ + Customization + +

These Guidelines provide an encoding schema suitable for encoding a very wide range of texts, + and capable of supporting a wide variety of applications. For this reason, the TEI schema + supports a variety of different approaches to solving similar problems, and also defines a + much richer set of elements than is likely to be necessary in any given project. Furthermore, + the TEI schema may be extended in well-defined and documented ways for texts that cannot be + conveniently or appropriately encoded using what is provided. For these reasons, it is almost + impossible to use the TEI schema without customizing it in some way.

+ +

This section describes how the TEI encoding schema may be customized, and should be read in + conjunction with chapter , which describes how a specific application of + the TEI encoding schema should be documented. The documentation system described in that + chapter is, like the rest of the TEI schema, independent of any particular schema or document + type definition language.

+ +

Formally speaking, these Guidelines provide both syntactic rules about how elements and + attributes may be used in valid documents and semantic recommendations about what + interpretation should be attached to a given syntactic construct. In this sense, they provide + both a document type definition and a document type declaration. + More exactly, we may distinguish between the TEI Abstract Model, which defines a + set of related concepts, and the TEI schema which defines a set of syntactic + rules and constraints. Many (though not all) of the semantic recommendations are provided + solely as informal descriptive prose, though some of them are also enforced by means of such + constructs as datatypes (see ), or by schema constraints expressed + using the Schematron language. Schematron constraints provide information about special kinds + of validation errors dependent on conditional relationships, such as the invalidity of an + attribute name or value on one element when another is present, or when, given a pair of + attributes such as minOccurs and maxOccurs, the minimum value exceeds + the maximum value. Schematron constraints also provide warnings when a particular element, + attribute, or combination is to be deprecated in future releases of the TEI scheme, to alert + users that the feature in question is no longer to be used after a certain date. Very rarely, + TEI Schematron constraints offer warnings that do not explicitly break with the TEI but + suggest a more efficient or less ambiguous encoding. + + Although the descriptions, validation errors, and warnings have been written with care, there + will inevitably be cases where the intention of the contributors has not been conveyed with + sufficient clarity to prevent users of these Guidelines from extending + them in the sense of attaching slightly variant semantics to them.

+ +

Beyond this unintentional semantic extension, some of the elements described can + intentionally be used in a variety of ways; for example, the element note has an + attribute type which can take on arbitrary string values, depending on how it is + used in a document. A new type of note, therefore, requires no change in the existing + model. On the other hand, for many applications, it may be desirable to constrain the possible + values for the type attribute to a small set of possibilities. A schema modified in + this way would no longer necessarily regard as valid the same set of documents as the + corresponding unmodified TEI schema, but would remain faithful to the same conceptual + model.

+ + +

This section explains how the TEI schema can be customized by suppressing elements, modifying + classes of elements, or adding elements. Documents which + validate against an application of the TEI schema which has been customized in this way may or + may not be considered TEI-conformant, as further discussed in section + .

+ +

The TEI system is designed to support modification and customization in a documented way that + can be validated by an XML processor. This is achieved by writing a small TEI-conformant + document, known informally as an ODD (One Document Does it all), from which an appropriate + processor can generate both human-readable documentation, and a schema expressed in a language + such as RELAX NG or DTD. The mechanisms used to instantiate a TEI schema differ for different + schema languages, and are therefore not defined here. In XML DTDs, for example, extensive use + is made of parameter entities, while in RELAX NG schemas, extensive use is made of patterns. + In either case, the names of elements and, wherever possible, their attributes and content + models are defined indirectly. The syntax used to implement this indirection also varies with + the schema language used, but the underlying constructs in the TEI Abstract Model are given + the same names. + + This indirection makes it simpler to implement customization of the TEI system in an + accessible and human-readable way.

+ +

As further discussed in section , the TEI encoding schema comprises a set + of class and macro declarations, and a number of modules. Each module is made up + of element and attribute declarations, and a schema is made by combining a particular set of + modules together. In the absence of any other kind of customization, when modules are combined + together: + all the elements defined by the module (and described in the corresponding section of + these Guidelines) are included in the schema; + each such element is identified by the canonical name given it in these + Guidelines; + the content model of each such element is as defined by these Guidelines; + the names, datatypes, and permitted values declared for each attribute associated with + each such element are as given in these Guidelines; + the elements comprising element classes and the meaning of macro declarations + expressed in terms of element classes is determined by the particular combination of + modules selected. + The TEI customization mechanisms allow the user to control this behaviour as follows: + + particular elements may be suppressed, removing them from any classes in which they + are members, and also from any generated schema; + new elements may be added to an existing class, thus making them available in macros + or content models defined in terms of those classes; + additional attributes, or attribute values, may be specified for an individual element + or for classes of elements; + within certain limits, attributes, or attribute values, may also be removed either + from an individual element or for classes of elements; + the characteristics inherited by one class from another class may be modified by + modifying its class membership: all members of the class then inherit the changed + characteristics; + the set of values legal for an attribute or attribute class may be constrained or + relaxed by supplying or modifying a value list, or by modifying its datatype. + within certain limits, the name (generic identifier) associated with an element may be + changed, without changing the semantic or syntactic properties of the element; + + The modification mechanisms presented in this section are quite general, and may be + used to make all the types of changes just listed.

+ +

The recommended way of implementing and documenting all such modifications is by means of the + ODD system described in chapter ; in the remainder of this section we give + specific examples to illustrate how that system may be applied. An ODD processor, such as the + Roma application supported by the TEI, or any other comparable set of stylesheets will use the + declarations provided by an ODD to generate appropriate sets of declarations in a specific + schema language such as RELAX NG or the XML DTD language. We do not discuss in detail here how + this should be done, since the details are schema language-specific; some background + information about the methods used for XML DTD and RELAX NG schema generation is however + provided in section . Several example ODD files are also provided as part + of the standard TEI release: see further section below.

+ +
+ Kinds of Modification +

For ease of discussion, we distinguish the following different kinds of modification: + deletion of elements; + modification of content models; + modification of attribute and attribute-value lists; + modification of class membership; + addition of new elements. + renaming of elements; + + Each of these is described in the following sections.

+ +

Each kind of modification changes the set of documents that will be considered valid + according to the resulting schema. A schema derived from any combination of unmodified TEI + declarations (an "unmodified schema") may be thought of as defining a certain set of + documents. A schema deriving from a combination of modified TEI declarations (a "modified + schema") will define a different set of documents. The set of documents valid according to + the modified schema may or may not be properly contained by the set of documents considered + to be valid according to the unmodified schema. The schema TEI-All is the + special case of the unmodified schema which includes all currently available TEI modules. We + use the term clean modification for cases where the set of documents defined by a + modified schema is a proper subset of the set of documents defined by TEI-All. Where this is + not the case, that is, where the modified schema considers valid some documents which + TEI-All does not, we use the term unclean modification. Despite this + terminology, unclean modifications are not particularly deprecated, and their use may often + be vital to the success of a project. The concept is introduced solely to distinguish the + effects of different kinds of modification.

+ + + +
+ Deletion of Elements + +

The simplest way to modify the supplied modules is to suppress one or more of the + supplied elements. This is simply done by setting the mode attribute to + delete on an elementSpec for the element concerned.

+ +

For example, if the note element is not to be used in a particular application, + but has been included via one of the supplied modules, then the schema specification + concerned will contain a declaration like the following: The ident attribute here supplies the + canonical name of the element to be deleted and the mode attribute specifies + what is to be done with it. There is no need to specify the module concerned, since + element names are unique across all TEI modules. The full specification for a schema in + which this modification is applied would thus be something like the following: + + + + +

+ +

In most cases, deletion is a clean modification, since most elements are optional. + Documents that are valid with respect to the modified schema are also valid according to + TEI-All. To say this another way, the set of documents matching the new schema is + contained by the set of documents matching the original schema.

+ +

There are however some elements in the TEI schema which have mandatory children; for + example, the element listPerson must contain at least one element from the + model.personLike class. If that class has no members because all of its + member elements have been removed, then the content model cannot be satisfied. A + modification which keeps listPerson but removes all of its possible children + would therefore be regarded as unclean. So long as at least one member of the class + remains available, however, deleting other members would not have this effect, and would + therefore be regarded as a clean modification.

+ +

In general, whenever the element deleted by a modification is mandatory within the + content model of some other (undeleted) element, the result is an unclean modification, + and may also break the TEI Abstract Model (). However, the parent of + a mandatory child can be safely removed if it is itself optional.

+ +

To determine whether or not an element is mandatory in a given context, the user must + inspect the content model of the element concerned. In most cases, content models are + expressed in terms of model classes rather than elements; hence, removing an element will + generally be a clean modification, since there will generally be other members of the + class available. If a class is completely depopulated by a modification, then the + cleanliness of the modification will depend upon whether or not the class reference is + mandatory or optional, in the same way as for an individual element.

+ +
+ + +
+ Modification of Content Models + +

The content model for an element in the TEI schema is defined by means of a + content element within the elementSpec which specifies it. For + example, the specification for the element term provided by these Guidelines + contains a content element like the following: + + + + This content model consists of a reference to a macro called macro.phraseSeq. Further examination shows that this macro in turn expands to + an optional repeatable alternation of text (textNode) with references to three + other classes (model.gLike, model.phrase, or model.global). For some particular + application it might be preferable to insist that term elements should only + contain plain text, excluding these other possibilities.Excluding + model.gLike is generally inadvisable however, since + without it the resulting schema has no way of referencing non-Unicode characters. + This could be achieved simply by supplying a specification for term like the + following: + + + + +

+ +

This is a clean modification which does not change the meaning of a TEI element; there is + therefore no need to assign the element to some other namespace than that of the TEI, + though it may be considered good practice; see further below.

+

A change of this kind, which simplifies the possible content of an element by reducing + its model to one of its existing components, is always clean, because the set of documents + matched by the resulting schema is a subset of the set of documents which would have been + matched by TEI-All.

+ +

Note that content models are generally defined (as far as possible) in terms of + references to model classes, rather than to explicit elements. This means that the need to + modify content models is greatly reduced: if an element is deleted or modified, for + example, then the deletion or modification will be available for every content model which + references that element via its class, as well as those which reference it explicitly. For + this reason it is not (in general) good practice to replace class references by explicit + element references, since this may have unintended side effects.

+ +

An unqualified reference to an element class within a content model generates a content + model which is equivalent to an alternation of all the members of the class referenced. + Thus, a content model which refers to the model class model.phrase will generate a content model in which any one of the members of + that class is equally acceptable. The classRef element used to reference a class + has an expand attribute which may be used to vary this behaviour, for example + to require an optional repeatable alternation of all members of a class, a + sequence containing no more than one of each member of the class, etc. as described + further in .

+ +

Content model changes which are not simple restrictions on an existing model should be + undertaken with caution. The set of documents matching the schema which results from such + changes is unlikely to be contained by the set of documents matching TEI-All, and such + changes are therefore regarded as unclean. When content models are changed or extended, + care should be taken to respect the existing semantics of the element concerned as stated + in these Guidelines. For example, the element l is defined as containing a line + of verse. It would not therefore make sense to redefine its content model so that it could + also include members of the class model.pLike such as + p or ab. Although syntactically feasible, such a modification would + not be regarded as TEI-conformant because it breaks the TEI Abstract Model.

+ +
+ + +
+ Modification of Attribute and Attribute Value Lists + +

The attributes applicable to a given element may be specified in two ways: they may be + given explicitly, by means of an attList element within the corresponding + elementSpec, or they may be inherited from an attribute class, as specified in + the classes element. To add a new attribute to an element, the designer should + therefore first check to see whether this attribute is already available from some + existing attribute class. If it is, then the simplest method of adding it will be to make + the element in question a member of that class, as further discussed below. If this is not + possible, then a new attDef element must be added to the existing + attList for the element in question.

+ +

Whichever method is adopted, the modification capabilities are the same as those + available for elements. Attributes may be added or deleted from the list, using the + mode attribute on attDef in the same way as on elementSpec. + The content of an attribute is defined by means of the datatype, + valList, or valDesc elements within the attDef element. Any + of these elements may be changed.

+ +

Suppose, for example, that we wish to add two attributes to the eg element (used + to indicate examples in a text), type to characterize the example in some way, + and valid to indicate whether the example is considered valid or not. A quick + glance through the Guidelines indicates that the attribute class att.typed could be used to provide the type attribute, but there is + no comparable class which will provide a valid attribute. The existing + eg element in fact has no local attributes defined for it at all: we will + therefore need to add not only an attDef element to define the new attribute, but + also an attList to hold it.

+

We begin by adding the new valid attribute: + + + indicates whether or not the example is considered to be valid + + + + + + +

+

The value supplied for the mode attribute on the attDef element is + add; if this attribute already existed on the element we are modifying this + should generate an error, since a specification cannot have more than one attribute of the + same name. If the attribute is already present, we can replace the whole of the existing + declaration by supplying replace as the value for mode; + alternatively, we can change some parts of an existing declaration only by supplying just + the new parts, and setting change as the value for mode.

+ +

Because the new attribute is not defined by the TEI, it is good practice to specify a + namespace for it on the attDef; see further .

+ + +

As noted above, adding the new type attribute involves changing this element's + class membership; we therefore discuss that in the next section ().

+ +

The canonical name for the new attribute is valid, and is supplied on the + ident attribute of the attDef element. In this simple example, we + supply only a description and datatype for the new attribute; the former is given by the + desc element, and the latter by the datatype element. (There are of + course many other pieces of information which could be supplied, as documented in ). The content of the datatype + element + is a dataRef element which references an existing TEI data specification.

+ +

It is often desirable to constrain the possible values for an attribute to a greater + extent than is possible by simply supplying a TEI datatype for it. This facility is + provided by the valList element, which can also appear as a child of the + attDef element. Suppose for example that, rather than simply indicating whether + or not the example is considered valid by means of the values true and + false we wish to provide a more nuanced indication, using encoded values such + as A, B, and C. A declaration like the following might be appropriate: + + + + indicates the validity of the example by supplying one of three predefined + codes for it. + + + + + + validity is of the highest class + + + validity is of the second highest class + + + validity is of the lowest class + + + + + +

+ +

The same technique may be used to replace or extend the valList supplied as part + of any attribute in the TEI schema.

+ + +
+
+ Class Modification + +

The concept of element classes was introduced in ; an + understanding of it is fundamental to successful use of the TEI system. As noted there, we + distinguish model classes, the members of which all have structural + similarity, from attribute classes, the members of which simply share a set + of attributes.

+

The part of an element specification which determines its class membership is an element + called classes. All classes to which the element belongs must be specified within + this, using a memberOf element for each.

+

To add an element to a class in which it is not already a member, all that is needed is + to supply a new memberOf element within the classes element for the + element concerned. For example, to add an element to the att.typed class, we include a declaration like the following: + + + + Any existing class memberships for the element being changed are + not affected because the mode attribute of the classes element is set + to change (rather than its default value of replace). Consequently, + in this case, the eg element retains its membership of the two classes (model.common and model.graphicLike) to + which it already belongs.

+

Equally, to remove the attributes which an element inherits from its membership in some + class, all that is needed is to remove the relevant memberOf element. For + example, the element term defined in the core module is a member of two attribute + classes, att.typed and att.declaring. It inherits the attributes type and + subtype from the former, and the attribute decls from the latter. + To remove the last of these attributes from this element, we need to remove it from that + class: + + + + +

+

If the intention is to change the class membership of an element completely, rather than + simply add or remove it to or from one or more classes, the value of the mode + attribute of classes can be set to replace (which is the default if no + value is specified), indicating that the memberships indicated by its child + memberOf elements are the only ones applicable. Thus the following declaration: + + + + + would have the effect of removing the element term from + both its existing attribute classes, and adding it to the att.interpLike class.

+

If however the mode attribute is set to change, the implication is + that the memberships indicated by its child memberOf elements are to be combined + with the existing memberships for the element.

+ +

To change or remove attributes inherited from an attribute class for all members of the + class (as opposed to specific members of that class), it is also possible to modify the + class specification itself. For example, the class att.global.rendition defines several attributes which are available for all + elements, namely rend, style, and rendition. If we decide + that we never wish to use the rend attribute, the simplest way of removing it + is to supply a modified class specification for att.global.rendition as follows: + + + + + Because the mode attribute on the classSpec defining the + attributes inherited through membership of this class has the value change, any + of its existing identifiable components not specified in the modification above will + remain unchanged. The only effect will therefore be to delete the rend + attribute from the class, and hence from all elements which are members of the class.

+ +

The classes used in the TEI schema are further discussed in chapter . + Note in particular that classes are themselves classified: the attributes inherited by a + member of attribute class A may come to it directly from that class, or from another class + of which A is itself a member. For example, the class att.global is itself a member of the classes att.global.linking and att.global.analytic. By + default, these two classes are predefined as empty. However, if (for example) the linking module is included in a schema, a number of attributes + (corresp, sameAs, etc.) are defined as members of the att.global.linking class. All elements which are members of att.global will then inherit these new attributes (see further + section ). A new attribute may thus be added to the global class in + two ways: either by adding it to the attList defined within the class + specification for att.global; or by defining a new attribute + class, and changing the class membership of the att.global + class to reference it.

+ + +

Such global changes should be undertaken with caution: in general removing existing + non-mandatory attributes from a class will always be a clean modification, in the same way + as removing non-mandatory elements. Adding a new attribute to a class however can be a + clean modification only if the new attribute is labelled as belonging to some namespace + other than the TEI.

+ +

The same mechanisms are available for modification of model classes. Care should be taken + when modifying the model class membership of existing elements since model class + membership is what determines the content model of most elements in the TEI schema, and a + small change may have unintended consequences.

+ + +
+ + +
+ Addition of New Elements + +

To add a completely new element into a schema involves providing a complete element + specification for it. It is recommended that the classes element of this new + declaration should include a reference to at least one TEI model class. Without such a + reference, the new element would not otherwise be referenced by the content model of any + other TEI element, and would therefore be inaccessible within a TEI document. It is also + possible to modify the content models of one or more existing elements to refer to the new + element explicitly, as discussed in + but this will generally be less convenient.

+ +

For example, the three elements bibl, biblFull, and biblStruct + are all defined as members of the class model.biblLike. To add + a fourth member (say myBibl) to this class, we need to include + in the elementSpec defining our new element a memberOf element which + nominates the intended class: + + + + + The other parts of this declaration will typically include a + description for the new element and information about its content model, its attributes, + etc., as further described in .

+
+ +
+ Renaming of Elements + +

Every element and other named markup construct in the TEI schema has a canonical + name, usually composed of English language words or syllables: this name is supplied as the value of the + ident attribute on the elementSpec, attDef, + classSpec, or macroSpec used to define it. In some circumstances, it may be + convenient for the element or attribute + declaration used within a schema generated from that specification to take a different form, for example, permitting schemas to use generic identifiers + from a different language, or in an abbreviated form. There may be many alternative + identifiers for the same markup construct, and an ODD processor may choose which of them + to use for a given purpose. Each such alternative name is supplied by means of an + altIdent element within the specification element concerned.

+

For example, the following declaration converts note to nt: + nt + Note that the mode attribute on the + elementSpec now takes the value change to indicate that those parts + of the element specification not supplied are to be inherited from the standard + definition. The content of the altIdent element is now available for use in place of the + canonical ident value in the schema generated.

+ +

Renaming in this way is is an + inherently unclean modification (because the set of documents matched by the resulting + schema is not contained by the set matched by TEI-All), even though the process of + converting any document in which elements have been renamed into an exactly equivalent + document using canonical names is completely deterministic. Documents using such a schema should not claim to be + in the TEI namespace, but either use a null namespace or some user-defined + namespace, as further discussed in ; this is necessary to + avoid the risk of name collision between the new name and all existing TEI names as well as for reasons + of conformance + (see further ).

+ +
+ +
+ +
+ Modification and Namespaces + + +

All the elements defined by the TEI schema are labelled as belonging to a single + namespace, maintained by the TEI and with the URI + http://www.tei-c.org/ns/1.0.This is not strictly the case, + since the element egXML used to represent TEI examples has its own namespace, + http://www.tei-c.org/ns/Examples; this is the only exception however. + Only elements which are unmodified or which have undergone a clean modification may use this + namespace. Note however that TEI-defined attributes are not associated with any namespace. +

+ +

This implies that any other modification + must either specify a different + namespace or, equivalently, specify no namespace at all. The ns attribute is + provided on elements schemaSpec, elementSpec, and attDef for this + purpose.

+

Suppose, for example, that we wish to add a new attribute topic to the existing TEI element p. In the absence of namespace + considerations, this would be an unclean modification, since p does not currently + have such an attribute. The most appropriate action is to explicitly attach the new + attribute to a new namespace by a declaration such as the following: + + + + indicates the topic of a TEI paragraph + + + + +

+

Document instances using a schema derived from this ODD can now indicate clearly the status + of this attribute: +

+ +

Flopsy, Mopsy, Cottontail, and Peter...

+

+ +

Since topic is explicitly labelled as belonging to something + other than the TEI namespace, we regard the modification which introduced it as clean. A + namespace-aware processor will be able to validate those elements in the TEI namespace + against the unmodified schema.Full namespace support does not exist in + the DTD language, and therefore these techniques are available only to users of more + modern schema languages such as RELAX NG or W3C Schema.

+ +

Similar considerations apply when modification is made to the content model or some other + aspect of an element, or when a new element is declared. + All such changes should be explicitly + labelled as belonging to some non-TEI namespace or to no namespace at all.

+

If the ns attribute is supplied on a schemaSpec element, it identifies + the namespace applicable to all components of the schema being specified. Even if such a + schema includes unmodified modules from the TEI namespace, the elements contained by such + modules will now be regarded as belonging to the namespace specified on the + schemaSpec. This can be useful if it is desired simply to avoid namespace + processing. For example, the following schema specification results in a schema called + noName which has no namespace, even though it comprises declarations from + the TEI header module: + + + +

+

In addition to the TEI canonical namespace mentioned above, the TEI may also define + namespaces for approved translations of the TEI schema into other languages. + + The namespace for such translations is the same as that for the canonical namespace, + suffixed by the appropriate ISO language identifier (). A schema + specification using the Chinese translation, for example, would use the namespace http://www.tei-c.org/ns/1.0/zh +

+
+ +
+ Documenting the Modification + +

The elements used to define a TEI customization (schemaSpec, moduleRef, + elementSpec, etc.) will typically be used within a TEI document which supplies + further information about the intended use of the new schema, the meaning and application of + any new or modified elements within it, and so on. This document will typically conform to a + schema which includes components from the module described in + chapter .This module can be used to document any XML + schema, and has indeed been used to document several non-TEI schemas.

+

Where the customization to be documented simply consists in a selection of TEI modules, + perhaps with some deletion of unwanted elements or attributes, the documentation need not + specify anything further. Even here however it may be considered worthwhile to replace some + of the semantic information provided by the unmodified TEI specification. For example, the + desc element of an unmodified TEI elementSpec may describe an element in + terms more general than appropriate to a particular project, or the exemplum + elements within it may not illustrate the project's actual intended usage of the element, or + the remarks element may contain discussions of matters irrelevant to the project. + These elements may therefore be replaced or deleted within an elementSpec as + necessary.

+ + + +

Radical revision is also possible. It is feasible to produce a modification in which the + teiHeader or text elements are not required, or in which any other rule + stated in these Guidelines is either not enforced or not enforceable. In fact, the + mechanism, if used in an extreme way, permits replacement of all that the TEI has to say + about every component of its schema. Such revisions would result in documents that are not + TEI-conformant in even the broadest sense, and it is not intended that encoders use the + mechanism in this way. We discuss exactly what is meant by the concept of TEI + conformance in the next section, .

+
+ + + +
+ Examples of Modification + +

Several examples of customizations of the TEI are provided as part of the standard release. + They include the following: + + The schema generated from this customization is the minimum needed for TEI + Conformance. It provides only a handful of elements. + + The schema generated from this customization combines all available TEI modules, + providing elements. + + The schema generated from this customization combines all available TEI modules with + three other non-TEI vocabularies, specifically MathML, SVG, and XInclude. + +

+

It is unlikely that any project would wish to use any of these extremes unchanged. However, + they form a useful starting point for customization, whether by removing modules from + tei_all or tei_allPlus, or by replacing elements deleted from tei_bare. They also + demonstrate how an ODD document may be constructed to provide a basic reference manual to + accompany schemas generated from it.

+ +

Shortly after publication of the first edition of these Guidelines, as a demonstration of + how the TEI encoding schema might be adopted to meet 90% of the needs of 90% of the TEI user + community, the TEI editors produced a brief tutorial defining one specific + clean modification of the TEI schema, which they called TEI Lite. + This tutorial and its associated DTD became very popular and are still available from the + TEI web site at . The + tutorial and associated schema specification is also included as one of the exemplars + provided with TEI P5.

+

An updated and expanded version of this schema known as TEI simplePrint was + added to the Exemplars at release 3.1.0. The elements it defines have been modified to take + advantage of the processing model features (see further ) introduced to the Guidelines at release 3.0.0.

+

The exemplars provided with TEI P5 also include a customization file from which a schema + for the validation of other customization files may be generated. This ODD, called tei_odds, + combines the four basic modules with the tagdocs, dictionaries, gaiji, linking, and figures + modules and also provides facilities for including RELAX NG or Schematron code within a + document. +

+
+ + + + +
+ + + +
+ + Conformance + +

The notion of TEI Conformance is intended to assist in the description of the + format and contents of a particular XML document instance or set of documents. It may be found + useful in such situations as: + interchange or integration of documents amongst different researchers or users; + software specifications for TEI-aware processing tools; + agreements for the deposit of texts in, and distribution of texts from, archives; + specifying the form of documents to be produced by or for a given project. + It is not intended to provide any other evaluation, for example of scholarly merit, + intellectual integrity, or value for money. A document may be of major intellectual importance + and yet not be TEI-conformant; a TEI-conformant document may be of no scholarly value + whatsoever.

+ +

In this section we explore several aspects of conformance, and in particular attempt to + define how the term TEI-conformant should be used. The terminology defined here + should be considered normative: users and implementors of the TEI Guidelines should use the + phrases TEI-conformant and + TEI Extension only in the senses given and with the usages described.

+ +

A document is TEI-conformant if it: + is a well-formed XML document () + can be validated against a TEI Schema, that is, a schema derived from the + TEI Guidelines () + conforms to the TEI Abstract Model () + uses the TEI namespace (and other namespaces where relevant) correctly + () + is documented by means of a TEI-conformant ODD file () which refers to the TEI Guidelines + Each of these criteria is discussed in more detail below.

+ + + +

A document is said to use a TEI Extension if it is a well-formed XML document + which is valid against a TEI Schema which contains additional distinctions, representing + concepts not present in the TEI Abstract Model, and therefore not documented in these + Guidelines. Such a document + cannot necessarily be transformed automatically to a TEI-conformant document without loss of + information. However, since one of the goals of the TEI is to support extensions and + modifications, it should not be assumed that no TEI document can include extensions: an + extension which is expressed by means of the recommended mechanisms is also a TEI-conformant + document provided that those parts of it which are not extensions are + TEI-conformant.

+ +

A TEI-conformant document is said to follow TEI Recommended + Practice if, wherever these Guidelines prefer one encoding practice to another, the + preferred practice is used.

+ +
+ + Well-formedness Criterion + +

These Guidelines mandate the use of well-formed XML as representation format. Documents + must conform to the World Wide Web Consortium recommendation of the Extensible Markup + Language (XML) 1.0 (Fourth Edition) or successor editions found at . Other ways of + representing the concepts of the TEI Abstract Model are possible, and other representations + may be considered appropriate for use in particular situations (for example, for data + capture, or project-internal processing). But such alternative representations + should not be + considered in any way TEI-conformant.

+ +

Previous versions of these Guidelines used SGML as a representation format. With the + release of P5, the only representation format supported by these Guidelines became valid + XML; legacy documents in SGML format should therefore be converted using appropriate + software.

+

A TEI-conformant document must use the TEI namespace, and therefore must also include an + XML-conformant namespace declaration, as defined below ().

+

The use of XML greatly reduces the need to consider hardware or software differences + between processing environments when exchanging data. No special packing or interchange + format is required for an XML document, beyond that defined by the W3C recommendations, and + no special interchange format is therefore proposed by these + Guidelines. For discussion of encoding issues that may arise in the processing of special + character sets or non-standard writing systems, see further chapter .

+ +

In addition to the well-formedness criterion, the W3C defines the notion of a + valid document, as being a well-formed document which matches a specific set + of rules or syntactic constraints, defined by a schema. As noted above, TEI + conformance implies that the schema used to determine validity of a given document should be + derived from the present Guidelines, by means of an ODD which references and documents + components which these Guidelines define.

+
+ +
+ Validation Constraint + +

All TEI-conformant documents must validate against a schema file that has been + derived from the published TEI Guidelines, combined and documented in the manner described + in section . We call the formal output of this process a TEI + Schema.

+ +

The TEI does not mandate use of any particular schema language, only that this schemaHere and elsewhere we use the word schema to refer + to any formal document grammar language, irrespective of the formalism used to represent + it. should have been generated from a TEI ODD file that references the + TEI Guidelines. Currently available tools permit the expression of schemas in any or all of + the XML DTD language, W3C XML Schema, and RELAX NG (both compact and XML formats). Some of + what is syntactically possible using the ODD formalism cannot be represented by all schema + languages; and there are some features of some schema languages which have no counterpart in + ODD. No single schema language fully captures all the constraints implied by conformance to + the TEI Abstract Model. A document which is valid according to a TEI schema represented + using one schema language may not be valid against the same schema expressed in other + languages; for example, the DTD language does not support namespaces. +

+ +

As noted in section , many varieties of TEI schema are possible and not + all of them are necessarily TEI-conformant; derivation from an ODD is a + necessary but not a sufficient condition for TEI Conformance.

+ + +
+ +
+ + Conformance to the TEI Abstract Model + +

The TEI Abstract Model is the conceptual schema instantiated by the TEI + Guidelines. These Guidelines define, both formally and informally, a set of abstract + concepts such as paragraph or heading, and their structural relationships, for + example stating that paragraphs do not contain + headings. These Guidelines also define classes of elements, which + have both semantic and structural properties in common. Those semantic and structural + properties are also a part of the TEI Abstract Model; the class membership of an existing + TEI element cannot therefore be changed without changing the model. Elements can however be + removed from a class by deletion, and new non-TEI elements within their own namespaces can + be added to existing TEI classes.

+ + +
+ Semantic Constraints + +

It is an important condition of TEI conformance that elements defined in the TEI + Guidelines as having one specific meaning should not be used with another. For example, + the element l is defined in the TEI Guidelines as containing a line of verse. A + schema in which it is redefined to mean a typographic line, or an ordered queue of objects + of some kind, cannot therefore be TEI-conformant, whatever its other properties.

+ +

The semantics of elements defined in the TEI Guidelines are conveyed in a number of ways, + ranging from formally verifiable datatypes to informal descriptive prose. In addition, a + mapping between TEI elements and concepts in other conceptual models may be provided by + the equiv element where this is available.

+ +

A schema which shares equivalent concepts to those of the TEI conceptual model may be + mappable to the TEI Schema by means of such a mechanism. For example, the concept of + paragraph expressed in the TEI schema by the p element is probably the same + concept as that expressed in the DocBook schema by the para element. + Such + areas of overlap facilitate + interchange + because elements from one namespace may be readily integrated with those from another, but + do not affect the definition of conformance.

+ +

A document is said to conform to the TEI Abstract Model if features for + which an encoding is proposed by the TEI Guidelines are encoded within it using the markup + and other syntactic properties defined by means of a valid TEI-conformant + schema. Hence, even though the names of elements or attributes may vary, a TEI-conformant + document must respect the TEI Semantic Model, and be valid with respect to a + TEI-conformant Schema. Although it may be possible to transform a document which follows + the TEI Abstract Model into a TEI-conformant document, such a + document is not itself conformant.

+

As noted above, the notion of semantic conformance cannot be completely enforced in a + formal way. The TEI conceptual model is expressed by means of formal specification in a + customization file, by means of descriptive prose in the body of these Guidelines, and + implicitly by examples of usage. Any inconsistency between, for example, the text of these + Guidelines and a part of a specification should be considered an error and reported to the + TEI Council for correction.

+ +
+ +
+ Mandatory Components of a TEI Document + +

It is a long-standing requirement for any TEI-conformant document that it + should contain a teiHeader element. To be more specific a + TEI-conformant document must contain + a single teiHeader element followed by one or more elements from the + model.resource class; or + in the case of a corpus or collection, a single overall teiHeader + element followed by a series of TEI elements each with its own + teiHeader + All teiHeader elements in a TEI-conformant document must + include elements for: + + This should include the title of the TEI document expressed using a + titleStmt element. + + This should include the place and date of publication or distribution of the TEI + document, expressed using the publicationStmt element. + + For a document derived from some previously existing document, this must include a + bibliographic description of that source. For a document not so derived, this must + include a brief statement that the document has no pre-existing source. In either + case, this will be expressed using the sourceDesc element. +

+ +
+ +
+ + +
+ Use of the TEI Namespace + +

The Namespaces Recommendation of the W3C () provides a way for + an XML document to combine markup from different vocabularies without risking name collision + and consequent processing difficulties. While the scope of the TEI is large, there are many + areas in which it makes no particular recommendation, or where it recommends that other + defined markup schemas should be adopted, such as graphics or mathematics. It is also + considered desirable that users of other markup schemas should be able to integrate + documents using TEI markup with their own system. To meet these objectives without + compromising the reliability of its encoding, a TEI-conformant document is required to make + appropriate use of the TEI namespace.

+ +

Essentially all elements in a TEI Schema which represents concepts from the TEI Abstract + Model belong to the TEI namespace, http://www.tei-c.org/ns/1.0, + maintained by the TEI. A TEI-conformant document is required to declare the namespace for + all the elements it contains whether these come from the TEI namespace or from other + schemas.

+ +

A TEI Schema may be created which assigns TEI elements to some other namespace, or to no + namespace at all. A document using such a schema cannot be considered + TEI-conformant. A document which places non-TEI + elements or attributes within the TEI namespace cannot be considered TEI-conformant; such + practices are strongly deprecated as they may lead to serious difficulties for processing or + interchange.

+ +
+ +
+ Documentation Constraint + +

As noted in above, a TEI Schema can only be generated from a TEI ODD, + which also serves to document the semantics of the elements defined by it. A TEI-conformant + document should therefore always be accompanied by (or refer to) a valid TEI ODD + file specifying which modules, elements, classes, etc. are in use together with any + modifications applied, and from which a TEI Schema can be generated to + validate the document. The TEI supplies a number of predefined TEI Customization + exemplar ODD files and the schemas already generated from them (see ), but most projects will typically need to customize the TEI beyond + what these examples provide. It is assumed, for example, that most projects will customize + the TEI schema by removing those elements that are not needed for the texts they are + encoding, and by providing further constraints on the attribute values and element content + models the TEI provides. All such customizations must be specified by means of a valid + TEI ODD file.

+ +

As different sorts of customization have different implications for the interchange and + interoperability of TEI documents, it cannot be assumed that every customization will + necessarily result in a schema that validates only TEI-conformant documents. The ODD + language permits modifications which conflict with the TEI Abstract Model, even though + observing this model is a requirement for TEI Conformance. The ODD language can in fact be + used to describe many kinds of markup schema, including schemas which have nothing to do + with the TEI at all.

+ +

Equally, it is possible to construct a TEI Schema which is identical to that derived from a + given TEI ODD file without using the ODD schema. A schema can constructed simply by + combining the predefined schema language fragments corresponding with the required set of + TEI modules and other statements in the relevant schema language. However, the status of + such a schema with respect to the tei_all schema cannot in + general be easily determined; it may therefore be impractical to determine whether such a + schema represents a clean modification or an extension. This is one reason for making the + presence of a TEI ODD file a requirement for conformance.

+ +
+ + + + +
+ Varieties of TEI Conformance + +

The conformance status of a given document may be assessed by answering the following + questions, in the order indicated: + Is it a valid XML document, for which a TEI Schema exists? If not, then the document + cannot be considered TEI-conformant in any sense. + Is the document accompanied by a TEI-conformant ODD specification describing its + markup schema and intended semantics? If not, then the document can only be considered + TEI-conformant if it validates against a predefined TEI Schema and conforms to the TEI + abstract model. + Does the markup in the document correctly represent the TEI abstract model? Though + difficult to assess, this is essential to TEI conformance. + Does the document claim that all of its elements come from some namespace other than + the TEI (or no namespace)? If so, the document cannot be TEI-conformant. + If the document claims to use the TEI namespace, in part or wholly, do the elements + associated with that namespace in fact belong to it? If not, the document cannot be + TEI-conformant; if so, and if all non-TEI elements and attributes are correctly + associated with other namespaces, then the document may be TEI-conformant. + Is the document valid according to a schema made by combining all TEI modules as + well as valid according to the schema derived from its associated ODD specification? If + so, the document is TEI-conformant. + Is the document valid according to the schema derived from its associated ODD + specification, but not according to tei_all? If so, the + document uses a TEI extension. + Is it possible automatically to transform the document into a document which is + valid according to tei_all, using only information supplied + in the accompanying ODD and without loss of information? If so, the document is + TEI-conformant. + +

+ +

In the following table, we examine more closely some specific, though imaginary, cases: + + + + A + B + C + D + E + F + G + H + + + Conforms to TEI Abstract Model + Y + N + Y + Y + ? + Y + N + ? + + + Valid ODD present + Y + Y + Y + Y + Y + Y + Y + N + + + Uses only non-TEI namespace(s) or none + N + N + N + N + Y + N + Y + N + + + Uses TEI and other namespaces correctly + Y + Y + N + Y + N + Y + N + Y + + + Document is valid as a subset of tei_all + Y + N + Y + N + N + Y + N + Y + + + Document can be converted automatically to a form which is valid as a subset of + tei_all + Y + N + Y + N + N + Y + N + ? + +
+

+

We assume firstly that each sample document assessed here is a well-formed XML document, + and that it is valid against some schema.

+

The document in column A is TEI-conformant. Its tagging follows the TEI Abstract Model, + both as regards syntactic constraints (its l elements appear within div + elements and not the reverse) and semantic constraints (its l elements appear to + contain verse lines rather than typographic ones). It is accompanied by a valid ODD which + documents exactly how it uses the TEI. All the TEI-defined elements and attributes in the + document are placed in the TEI namespace. The schema against which it is valid is a + clean subset of the tei_all schema.

+ +

The document in column B is not a TEI document. Although it is accompanied by a valid TEI + ODD, the resulting schema includes some unclean modifications, and + represents some concepts from the TEI Abstract Model using non-TEI elements; for example, it + re-defines the content model of p to permit div within it, and it includes + an element pageTrimming which appears to have the same meaning + as the existing TEI fw element, but the equivalence is not made explicit in the + ODD. It uses the TEI namespace correctly to identify the TEI elements it contains, but the + ODD does not contain enough information automatically to convert its non-TEI elements into + TEI equivalents.

+ +

The document in column C is TEI conformant. It is almost the same as + the document in column A, except that the names of the elements used are not those specified + for the TEI namespace. Because the ODD accompanying it contains an exact mapping for each + element name (using the altIdent element) and there are no name conflicts, it is + possible to make an automatic conversion of this document.

+ +

The document in column D is a TEI Extension. It combines elements from its own namespace + with unmodified TEI elements in the TEI namespace. Its usage of TEI elements conforms to the + TEI Abstract Model. Its ODD defines a new blort element which + has no exact TEI equivalent, but which is assigned to an existing TEI class; consequently + its schema is not a clean subset of tei_all. If the associated + ODD provided a way of mapping this element to an existing TEI element, then this would be + TEI-conformant.

+ +

The document in column E is superficially similar to document D, but because it does not + use any namespace declarations (or, equivalently, it assigns unmodified TEI elements to its + own namespace), it may contain name collisions; there is no way of knowing whether a + p within it is the same as the TEI's p or has some other meaning. The + accompanying ODD file may be used to provide the human reader with information about + equivalently named elements in the TEI namespace, and hence to determine whether the + document is valid with respect to the TEI Abstract Model but this is not an automatable + process. In particular, cases of apparent conflict (for example use of an element p + to represent a concept not in the TEI Abstract Model but in the abstract model of some other + system, whose namespace has been removed as well) cannot be reliably resolved. By our + current definition therefore, this is not a TEI document.

+ +

The document in column F is TEI-conformant. The difference between it and that in + column D is that the new element blort which is used in this + document is a specialization of an existing TEI element, and the ODD in which it is defined + specifies the mapping (a my:blort may be automatically converted + to a tei:seg type="blort", for example). For this to work, however, the blort must observe the same syntactic constraints as the + seg; if it does not, this would also be a case of TEI Extension.

+ +

The document in column G is not a TEI document. Its structure is fully documented by a + valid TEI ODD, but it does not claim to represent the TEI Abstract Model, does not use the + TEI namespace, and is not intended to validate against any TEI schema.

+ +

The document in column H is very like that in column A, but it lacks an accompanying ODD. + Instead, the schema used to validate it is produced simply by combining TEI schema fragments + in the same way as an ODD processor would, given the ODD. If the resulting schema is a clean + subset of tei_all, such a document is indistinguishable from a + TEI-conformant one, but there is no way of determining (without inspection) whether this is + the case if any modification or extension has been applied. Its status is therefore, like + that of Text E, impossible to determine.

+ +
+ + +
+ + + + + +
+ Implementation of an ODD System +

This section specifies how a processing system may take advantage of the markup specification + elements documented in chapter of these Guidelines in order to produce + project specific user documentation, schemas in one or more schema languages, and validation + tools for other processors.

+ +

The specifications in this section are illustrative but not normative. Its function is to + further illustrate the intended scope and application of the elements documented in chapter + , since it is believed that these may have application beyond the areas + directly addressed by the TEI.

+ +

An ODD processing system has to accomplish two main tasks. A set of selections, deletions, + changes, and additions supplied by an ODD customization (as described in ) + must first be merged with the published TEI P5 ODD specifications. Next, the resulting unified + ODD must be processed to produce the desired outputs.

+ +

An ODD processor is not required to do these two stages in sequence, but that may well be the + simplest approach; the ODD processing tools currently provided by the TEI Consortium, which + are also used to process the source of these Guidelines, adopt this approach.

+ +
+ Making a Unified ODD +

An ODD customization must contain a single schemaSpec element, which defines the + schema to be constructed. + + Amongst other attributes inherited from the att.identified class, this element also carries a required ident + attribute. This provides a name for the generated schema, which other components of the + processing system may use to refer to the schema being generated, e.g. in issuing error + messages or as part of the generated output schema file or files. The ns + attribute may be used to specify the default namespace within which elements valid against + the resulting schema belong, as discussed in .

+

The schemaSpec element contains an unordered series of specialized elements, each + of which is of one of the following four types: + + elements from the class model.oddDecl (by default + elementSpec, classSpec, moduleSpec, and + macroSpec); these must have a mode attribute which determines how + they will be processed.An ODD processor should recognize as + erroneous such obvious inconsistencies as an attempt to include an + elementSpec in add mode for an element which is already present + in an imported module. If the value of mode is add, then + the object is simply copied to the output, but if it is change, + delete, or replace, then it will be looked at by other parts of + the process. + + specGrpRef elements refer to specGrp elements that occur elsewhere + in this, or another, document. A specGrp element, in turn, groups together a + set of ODD specifications (among other things, including further specGrpRef + elements). The use of specGrp and specGrpRef permits the ODD markup to + occur at the points in documentation where they are discussed, rather than all inside + schemaSpec. The target attribute of any specGrpRef should + be followed, and the elementSpec, classSpec, and macroSpec, + elements in the corresponding specGrp should be processed as described in the + previous item; specGrpRef elements should be processed as described + here. + + moduleRef elements with key attributes refer to components of + the TEI. The value of the key attribute matches the ident + attribute of the moduleSpec element defining a TEI module. The key + must be dereferenced by some means, such as reading an XML file with the TEI ODD + specification (either from the local hard drive or off the Web), or looking up the + reference in an XML database (again, locally or remotely); whatever means is used, it + should return a stream of XML containing the element, class, and macro specifications + collected together in the specified module. These specification elements are then + processed in the same way as if they had been supplied directly within the + schemaSpec being processed. + + + a moduleRef element may also refer to a compatible external module by means + of its url attribute; the content of such modules, which must be available in + the RELAX NG XML syntax, are passed directly and without modification to the output + schema when that is created. + +

+ +

Each object obtained from the TEI ODD specification using moduleRef by means of + the key attribute must be checked against objects in the customization + schemaSpec according to the following rules: + if there is an object in the ODD customization with the same value for the + ident attribute, and a mode value of delete, then the + object from the module is ignored; + if there is an object in the ODD customization with the same value for the + ident attribute, and a mode value of replace, then + the object from the module is ignored, and the one from the ODD customization is used in + its place; + if there is an object in the ODD customization with the same value for the + ident attribute, and a mode value of change, then the + two objects must be merged, as described below; + if there is an object in the ODD customization with the same value for the + ident attribute, and a mode value of add, then an + error condition should be raised; + + otherwise, the object from the module is copied to the result. + +

+ +

To merge two objects with the same ident, their component attributes and child + elements must be looked at recursively. Each component may fall into one of the following + four categories: + + Some components may occur only once within the merged object (for example + attributes, and altIdent, content, or classes elements). If + such a component is found in the ODD customization, it will be copied to the output; if + it is not found there, but is present in the TEI ODD specification, then that will be + copied to the output. + + Some components are grouping objects (attList, valList, for + example); these are always copied to the output, and their children are then processed + following the rules given in this list. + + Some components are identifiable: this means that they are + members of the att.identified class from which they inherit + the ident attribute; examples include attDef and valItem. A + component of this type will be processed according to its mode attribute, + following the rules given above. + + Some components may occur multiple times, but are neither grouped nor identifiable. + Examples include the desc, exemplum, remarks, listRef, + datatype and defaultVal elements, and the members of + model.identSynonyms, i.e., the equiv, + altIdent, and gloss, elements. These should be copied from both the TEI + ODD specification and the ODD customization, and all occurrences included in the output. + +

+ +

A special problem arises with elements which are members of attribute classes, as they are + permitted to override attributes inherited from a class. For example, consider this simple + modification: + + + + + + + The effect of its membership in the att.typed class is + to provide p with a type attribute and a subtype attribute. + If we wish p to not have subtype, we could extend the + customization in our schema as follows: + + + + + + + + + + This means that when memberOf key="att.typed"/ is processed, that class + is looked up, each attribute which it defines is examined in turn, and the customization is + searched for an override. If the modification is of the attribute class itself, work + proceeds as usual; if, however, the modification is at the element level, the class + reference is deleted and a series of attRef elements is added to the element, one + for each attribute inherited from the class. Since attribute classes can themselves be + members of other attribute classes, membership must be followed recursively.

+ +

The effect of the concatenation of unidentifiable components should be considered + carefully. An original may have + + marks paragraphs in prose. + + + which would usefully be extended with this: + + marca párrafos en prosa. + + + to provide an alternate description in another language. Nothing prevents the user + from supplying desc several times in the same language, and subsequent applications + will have to decide what that may mean.

+ +

Similar considerations apply to multiple example elements, though these are less likely to + cause problems in documentation. Note that existing examples can only be deleted by + supplying a completely new elementSpec in replace mode, since the + exemplum element is not identifiable.

+ +

In the processing of the content models of elements and the content of macros, deleted + elements may require special attention.The carthago program behind the + Pizza Chef application, written by Michael Sperberg-McQueen for TEI P3 and P4, went to + very great efforts to get this right. The XSLT transformations used by the P5 Roma + application are not as sophisticated, partly because the RELAX NG language is more + forgiving than DTDs. A content model like this: + + + + + + + + + + + + + + + requires no special treatment because everything is expressed in terms of model + classes; if the class model.personPart is deleted explicitly, or + removed because all of its members have been deleted, then model.global is left as the only child of the inner alternate. An ODD + processor may or may not elect to simplify the resulting choice between nothing and model.global by removing the wrapper alternate element. + However, such simplification may be considerably more complex in the general case + and + an ODD processor is therefore likely to be more successful in carrying out such + simplification as a distinct stage during processing of ODD sources.

+

If an element refers directly to an element child, like this: + + + + + + + + + + + + + + + and figDesc has been deleted,Note that deletion of + required elements will cause the schema specification to accept as valid documents which + cannot be TEI-conformant, since they no longer conform to the TEI Abstract Model; + conformance topics are addressed in more detail in . it will be + necessary to remove that reference, or the resulting schema will be + invalid.

+ +

The result of the work carried out should be a new schemaSpec which contains a + complete and internally consistent set of element, class, and macro specifications, possibly + also including moduleRef elements with url attributes identifying + external modules.

+ +
+ +
+ Generating Schemas +

Assuming that any modifications have been resolved, as outlined in the previous section, + making a schema is now a four stage process: + all datatype and other macro specifications must be collected together and declared + at the start of the output schema; + all classes must be declared in the right order (order is significant because since + some classes reference others); + all elements are declared; + any moduleRef elements with a url attribute identifying an + external schema must be processed. + Working in this order gives the best chance of successfully supporting all the + schema languages. However, there are a number of obstacles to overcome along the way.

+ +

An ODD processor may choose to use any desired schema language or languages for its schema + output, since ODD specifications are expressed as far as possible in a form independent of + any schema language. + + The current TEI ODD processing system produces schema output in the three main schema + languages as follows: + A RELAX NG (XML) schema is generated by converting content models, datatypes, and + macro specifications provided within the ODD specification; a version re-expressed in + the RELAX NG compact syntax is generated using James Clark's trang + application. + + A DTD schema is generated by converting the RELAX NG content models to DTD language, + often simplifying it to allow for the less-sophisticated output language. + + A W3C Schema schema is created by generating a RELAX NG schema and then using James + Clark's trang application. + Note that the method used to generate W3C Schema means that a processor must ensure + that the RELAX NG it generates follows the subset which trang is able to + translate properly (see further below)—this may involve simple trial and error.

+ +

Other projects may decide to follow a different route, perhaps implementing a direct ODD to + W3C Schema translator.

+ +

Secondly, it is possible to create two rather different styles of schema. On the one hand, + the schema can try to maintain all the flexibility of ODD by using the facilities of the + schema language for parameterization; on the other, it can remove all customization features + and produce a flat result which is not suitable for further manipulation. The TEI project + currently generates both styles of schema; the first as a set of schema fragments in DTD and + RELAX NG languages, which can be included as modules in other schemas, and customized + further; the second as the output from a processor such as Roma, in which many of the + parameterization features have been removed.

+ +

The difference between the schema styles may be illustrated by considering this ODD + specification: + + + + + + + + + + + + + + + + + + + + + + + + A simple rendering to RELAX NG produces this: + In the above, a subsequent redefinition of the attribute class (such as att.global) would have no effect, since references to such classes have been + expanded to reference their constituent attributes.

+

The equivalent parameterized version might look like this: + Here, the attribute class att.global is provided via an + explicit reference (att.global.attributes), and can therefore be redefined. + Moreover, the attributes are separated from the content model, allowing either to be + overridden.

+

In the remainder of these section, the terms simple schema and + parameterized schema are used to distinguish the two schema types. An ODD + processor is not required to support both, though the simple schema output is generally + preferable for most applications.

+ +

Thirdly, the problem of missing components must be resolved. For example, consider this + (fictitious) model for sp: + + + + + + + + + + + + + + This proposes anything from the class model.global, + followed optionally by a speaker element followed by anything from the model.global class. What happens if speaker is removed from + the schema? The following would result: + + + + + + + + + + + which is illegal in DTD and W3C schema languages, since for a given member of + model.global it is impossible to be sure which rule is being + used. This situation is not detected when RELAX NG is used, since the language is able to + cope with non-deterministic content models of this kind and does not require that only a + single rule be used.

+ + +

Finally, an application will need to have some method of associating the schema with + document instances that use it. The TEI does not mandate any particular method of doing + this, since different schema languages and processors vary considerably in their + requirements. ODD processors may wish to build in support for some of the methods for + associating a document instance with a schema. The TEI does not mandate any particular + method, but does suggest that those which are already part of XML (the DOCTYPE declaration + for DTDs) and W3C Schema (the xsi:schemaLocation attribute) be supported where + possible.

+ +

In order for the xsi:schemaLocation attribute to be valid when a document is + validated against either a DTD or a RELAX NG schema, ODD processors may wish to add + declarations for this attribute and its namespace to the root element, even though these are + not part of the TEI per se. For DTDs this means adding to the list of attributes on the root element, + which permits the non-namespace-aware DTD language to recognize the + xsi:schemaLocation notation. For RELAX NG, the namespace and attribute would + be declared in the usual way: and inside the root element + declaration.

+ +

Note that declaration of the xsi:schemaLocation attribute in a W3C Schema schema + is not permitted. Therefore, if W3C Schemas are being generated by converting the RELAX NG + schema (for example, with trang), it may be necessary to perform that + conversion prior to adding the xsi:schemaLocation declaration to the RELAX + NG.

+ +

It is recognized that this is an unsatisfactory solution, but it permits users to take + advantage of the W3C Schema facility for indicating a schema, while still permitting + documents to be validated using DTD and RELAX NG processors without any conflict.

+ +
+ +
+ Names and Documentation in Generated Schemas +

When processing class, element, or macro specifications, there are three general rules: + + If a RELAX NG pattern or DTD parameter entity is being created, its name is the + value of the corresponding ident attribute, prefixed by the value of any + prefix attribute on schemaSpec. This allows for elements from an + external schema to be mixed in without risk of name clashes, since all TEI elements can + be given a distinctive prefix such as tei_. Thus + + + + + + may generate a RELAX NG (compact syntax) pattern like this: + References to these patterns (or, in DTDs, parameter entities) also need to be prefixed + with the same value. + + If an element or attribute is being created, its default name is the value of the + ident attribute, but if there is an altIdent child, its content is + used instead. + + Where appropriate, the documentation strings in gloss and desc + should be copied into the generated schema. If there is only one occurrence of either of + these elements, it should be used regardless, but if there are several, local processing + rules will need to be applied. For example, if there are several with different values + of xml:lang, a locale indication in the processing environment might be used + to decide which to use. For example, + + + heading + en-tête + encabezamiento + titolo + + + might generate a RELAX NG schema fragment like the following, if the locale is + determined to be French: + + Alternatively, a selection might be made on the basis of the value of the + version attribute which these elements carry as members of the att.translatable class.

+

In addition, there are three conventions about naming patterns relating to classes; ODD + processors need not follow them, but those reading the schemas generated by the TEI project + will find it necessary to understand them: + when a pattern for an attribute class is created, it is named after the attribute + class identifier (as above) suffixed by .attributes (e.g. + att.editLike.attributes); + when a pattern for an attribute is created, it is named after the attribute class + identifier (as above) suffixed by .attribute. and then the identifier of + the attribute (e.g. att.editLike.attribute.resp); + + + when a parameterized schema is created, each element generates patterns for its + attributes and its contents separately, suffixing respectively .attributes + and .contents to the element name. + +

+
+ +
+ Making a RELAX NG Schema + +

To create a RELAX NG schema, the processor processes every macroSpec, + classSpec, and elementSpec in turn, creating a RELAX NG pattern for + each, using the naming conventions listed above. The order of declaration is not important, + and a processor may well sort them into alphabetical order of identifier.

+ +

A complete RELAX NG schema must have an rng:start element defining which elements + can occur as the root of a document. The ODD schemaSpec has an optional + start attribute, containing one or more patterns, which can be used to + construct the rng:start. A pattern normally corresponds to an element name, but if + a prefix (see above, ) is supplied for an element, the pattern + consists of the prefix name with the element name.

+ +
+ Macros +

An ODD macro generates a corresponding RELAX NG pattern by processing the body of the + content element in the same way as elsewhere. Thus + + + + + + + + + + + produces the following + + + + + + + + + + + +

+
+ +
+ Classes +

An ODD model class always generates a RELAX NG pattern definition listing all the members + of the class in alternation. For example + + + + will produce something like the following: + + + + + + + + assuming that the elements num, measure, and + measureGrp are all defined in the schema concerned as members of that class. A + model declaration may also generate a number of other patterns corresponding with + sequences or alternations of the class members: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + where the pattern name is created by appending an underscore and the name of the + generation type to the class name.

+

When classes are referenced using the classRef element, it is possible to + indicate which of the available patterns is required by means of the expand + attribute.

+

Attribute classes work by producing a pattern containing definitions of the appropriate + attributes. So + + + + + indicates whether the end of a verse line is marked by enjambement. + + + + + + + the line is end-stopped + + + + the line in question runs on into the next + + + + the line is weakly enjambed + + + + the line is strongly enjambed + + + + + + produces + + + + + + + + (enjambement) indicates whether the end of a verse line is marked by + enjambement. Sample values include: 1] no; 2] yes; 3] weak; 4] + strong + + + + + Since the processor may have expanded the attribute classes already, separate + patterns are generated for each attribute in the class as well as one for the class + itself. This allows an element to refer directly to a member of a class. Notice that the + desc element is used to add an a:documentation element to the schema, + which some editors use to provide help during composition. The desc elements in + the valList are used to create the human-readable sentence Sample values + include: 1] no; 2] yes; 3] weak; 4] strong Naturally, this behaviour is not + mandatory; and other ODD processors may create documentation in other ways, or ignore + those parts of the ODD specifications when creating schemas.

+ +

An individual attribute consists of an rng:attribute with a name + attribute derived according to the naming rules described above (). In addition, the ODD model supports a defaultVal, which is transformed to a + defaultValue attribute in the namespace http://relaxng.org/ns/compatibility/annotations/1.0 on the + rng:attribute. The body of the attribute is taken from the datatype + child, unless there is a supporting valList with a type value of + closed. In that case an rng:choice is created, listing the allowed + values. Thus the following attribute definition + + yes + + + the name component is spelled out in full. + + + abbreviated + the name component is given in an abbreviated form. + + + initial letter + the name component is indicated only by one initial. + + + + may generate this RELAX NG code: + + + + + yes + the name component is spelled out in full. + abb + the name component is given in an abbreviated form. + init + the name component is indicated only by one initial. + + + + + + Note the use of the http://relaxng.org/ns/compatibility/annotations/1.0 namespace to provide + default values and documentation.

+
+ +
+ Elements +

An elementSpec produces a RELAX NG specification in two parts; firstly, it must + generate an rng:define pattern by which other elements can refer to it, and then + it must generate an rng:element with the content model and attributes. It may be + convenient to make two separate patterns, one for the element's attributes and one for its + content model.

+

The content model is created by processing the TEI declarations found within the + content element; ; the attributes are processed in the same way as those from + attribute classes, described above.

+
+ +
+ + +
+ Making a DTD +

Generation of DTDs largely follows the same pattern as RELAX NG generation, with one + important exception—the order of declaration matters. A DTD may not refer to an + entity which has not yet been declared. Since both macros and classes generate DTD parameter + entities, the TEI Guidelines are constructed so that they can be declared in the right + order. A processor must therefore work in the following order: + declare all model classes which have a predeclare value of + true + declare all macros which have a predeclare value of + true + declare all other classes + declare the modules (if DTD fragments are being constructed) + declare any remaining macros + declare the elements and their attributes + +

+

Let us consider a complete example, a simple element with no attributes of its own: + + specifies the faith, religion, or belief set of a person. + + + + + + + + + + If DTD fragments are being generated (for use as described in ), this will result in the following: + + + + + +]]]]>]]> Here the whole stanza is contained in a marked section (for use as described in ), the element name is parameterized (see ), and + the class attributes are entity references derived from the memberOf records in + classes. Note the additional attribute which provides a default xmlns declaration for the element; the effect of this is that if the document is + processed by a DTD-aware XML processor, the namespace declaration will be present + automatically without the document author even being aware of it.

+ +

A simpler rendition for a flattened DTD generated from a customization will result in the + following, with no containing marked section, and no parameterized name: + + +]]> Here the attributes from classes have been expanded into individual entity references.

+ + + +
+ +
+ Generating Documentation +

In Donald Knuth's literate programming terminology (), the previous + sections have dealt with the tangle process; to generate documentation, we now + turn to the weave process.

+ +

An ODD customization may consist largely of general documentation and examples, requiring + no ODD-specific processing. It will normally however also contain a schemaSpec + element and possibly some specGrp fragments.

+ +

The generated documentation may be of two forms. On the one hand, we may document the + customization itself, that is, only those elements (etc.) which differ in their + specification from that provided by the TEI reference documentation. Alternatively, we may + generate reference documentation for the complete subset of the TEI which results from + applying the customization. The TEI Roma tools take the latter approach, and operate on the + result of the first stage processing described in .

+ +

Generating reference documentation for elementSpec, classSpec, and + macroSpec elements is largely dependent on the design of the preferred output. + Some applications may, for example, want to turn all names of objects into hyperlinks, show + lists of class members, or present lists of attributes as tables, lists, or inline prose. + Another technique implemented in these Guidelines is to show lists of potential + parents for each element, by tracing which other elements have them + as possible members of their content models.

+

One model of display on a web page is shown in , corresponding to + the faith element shown in section .

+
+ + Example reference documentation for faith +
+ +
+ + + + + +
+ Using TEI Parameterized Schema Fragments +

The TEI parameterized DTD and RELAX NG fragments make use of parameter entities and + patterns for several purposes. In this section we describe their interface for the user. In + general we recommend use of ODD instead of this technique, which has been retained only for + compatability reasons.

+ +
+ Selection of Modules + +

Special-purpose parameter entities are used to specify which modules are to be combined + into a TEI DTD. They take the form TEI.xxxxx where xxxx is the + name of the module as given in table in . + For example, the parameter entity TEI.linking is used to define + whether or not to include the module linking. All such + parameter entities are declared by default with the value IGNORE: to select a + module, therefore, the encoder declares the appropriate parameter entities with the value + INCLUDE.

+ +

For XML DTD fragments, note that some modules generate two DTD fragments: for example the + analysis module generates fragments called analysis-decl and analysis. This is + because the declarations they contain are needed at different points in the creation of an + XML DTD.

+ +

The parameter entity named for the module is used as the keyword controlling a + conditional marked section in the DTD fragment generated by the tei module. The declarations for each DTD fragment constituting the module are + contained within such marked sections. For example, the parameter entity TEI.linking appears twice in tei.dtd, once for the + linking-decl schema fragment: + + +%file.linking-decl; +]] >]]> and once for the linking schema fragment: + +%file.linking;]] >]]> If TEI.linking has its default value of IGNORE, neither declaration has any effect. If + however it has the value INCLUDE, then the content of each marked section is acted upon: + the parameter entities file.linking and file.linking-decl are referenced, which has the effect of embedding the content + of the files they represent at the appropriate point in the DTD.

+ +

The RELAX NG schema fragments can be combined in a wrapper schema using the standard + mechanism of rng:include in that language.

+ +
+ + +
+ Inclusion and Exclusion of Elements + +

The TEI DTD fragments also use marked sections and parameter entity references to allow + users to exclude the definitions of individual elements, in order either to make the + elements illegal in a document or to allow the element to be redefined. The parameter + entities used for this purpose have exactly the same name as the generic identifier of the + element concerned. The default definition for these parameter entities is + INCLUDE but they may be changed to IGNORE in order to exclude the + standard element and attribute definition list declarations from the DTD.

+ +

The declarations for the element p, for example, are preceded by a definition + for a parameter entity with the name p and + contained within a marked section whose keyword is given as %p;: + +]]]]>

+

These parameter entities are defined immediately preceding the element whose declarations + they control; because their names are completely regular, they are not documented further.

+

To define a DTD in which the element p is excluded therefore, the entity p needs to be redefined as IGNORE by + ensuring that a declaration such as + ]]> is added earlier in the + DTD than the default (see further ).

+ +

Similarly, in the parameterized RELAX NG schemas, every element is defined by a pattern + named after the element. To undefine an element therefore all that is necessary is to add + a declaration like the following: + +

+
+ +
+ Changing the Names of Generic Identifiers + +

In the TEI DTD fragments, elements are not referred to directly by their generic + identifiers; instead, the DTD fragments refer to parameter entities which expand to the + standard generic identifiers. This allows users to rename elements by redefining the + appropriate parameter entity. Parameter entities used for this purpose are formed by + taking the standard generic identifier of the element and attaching the string + n. as a prefix. Thus the standard generic identifiers for paragraphs, notes, + and quotations, p, note, and persName are defined by + declarations of the following form: + +]]> Note that since all names are case-sensitive, the specific + mix of uppercase and lowercase letters in the standard generic identifier must be + preserved in the entity name.

+ +

These declarations are generated by an ODD processor when TEI DTD fragments are created.

+ +

In the RELAX NG schemas, all elements are normally defined using a pattern with the same + name as the element (as described in ): for example + The easiest way of renaming the element is thus simply to rewrite the pattern with a + different element name; any references use the pattern, not the element, name. + More complex revisions, such as redefining the content of the element (defined by the + pattern abbr.content) or its attributes (defined by the pattern + abbr.attributes) can be accomplished in a similar way, using + the features of the RELAX NG language. The recommended method of carrying out such + modifications is however to use the ODD language as further described in section .

+
+ + +
+ Embedding Local Modifications (DTD only) + +

Any local modifications to a DTD (i.e. changes to a schema other than simple inclusion or + exclusion of modules) are made by declarations stored in one of two local extension files, + one containing modifications to the TEI parameter entities, and the other new or changed + declarations of elements and their attributes. Entity declarations must be made which + associate the names of these two files with the appropriate parameter entity so that the + declarations they contain can be embedded within the TEI DTD at an appropriate point.

+ +

The following entities are referred to by the main tei.dtd + file to embed portions of the TEI DTD fragments or locally developed extensions. + + identifies a local file containing extensions to the TEI parameter entities + + identifies a local file containing extensions to the TEI module +

+

For example, if the relevant files are called project.ent and project.dtd, then + declarations like the following would be appropriate: +]]>

+ +

When an entity is declared more than once, the first declaration is binding and the + others are ignored. The local modifications to parameter entities should therefore be + handled before the standard parameter entities themselves are declared in tei.dtd. The entity TEI.extensions.ent is + referred to before any TEI declarations are handled, to allow the user's declarations to + take priority. If the user does not provide a TEI.extensions.ent + entity, the entity will be expanded to the empty string.

+

For example the encoder might wish to add two phrase-level elements it and bd, perhaps as synonyms for + hi rend='italics' and hi rend='bold'. As described in chapter , this involves two distinct steps: one to define the new elements, and + the other to ensure that they are placed into the TEI document structure at the right + place.

+

Creating the new declarations is done in the same way for user-defined elements as for + any other; the same parameter entities need to be defined so that they may be referenced + by other elements. The content models of these new elements may also reference other + parameter entities, which is why they need to be declared after other declarations.

+

The second step involves modifying the element class to which the new elements should be + attached. This requires that the parameter entity macro.phraseSeq + should be modified to include the generic identifiers for the new elements we wish to + create. The declaration for each modifiable parameter entity in the DTD includes a + reference to an additional parameter entity with the same name prefixed by an + x.; these entities are declared by default as the null string. However, in + the file containing local declarations they may be redeclared to include references to the + new class members: ]]> and this declaration will take precedence over the default when the declaration for + macro.phraseSeq is evaluated.

+
+ +
+ +
+ +
diff --git a/P5/Source/Guidelines/fr/VE-Verse.xml b/P5/Source/Guidelines/fr/VE-Verse.xml deleted file mode 120000 index 50ee373466..0000000000 --- a/P5/Source/Guidelines/fr/VE-Verse.xml +++ /dev/null @@ -1 +0,0 @@ -../en/./VE-Verse.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/VE-Verse.xml b/P5/Source/Guidelines/fr/VE-Verse.xml new file mode 100644 index 0000000000..a1b8cb35f4 --- /dev/null +++ b/P5/Source/Guidelines/fr/VE-Verse.xml @@ -0,0 +1,916 @@ + + + + +
+ Verse +

This module is intended for use when encoding texts which are entirely or predominantly in + verse, and for which the elements for encoding verse structure already provided by the core + module are inadequate.

+

The tags described in section include elements for the encoding of verse + lines and line groups such as stanzas: these are available for any TEI document, irrespective + of the module it uses. Like the modules for prose and for drama, the module for verse + additionally makes use of the module defined in chapter to define the + basic formal structure of a text, in terms of front, body and back + elements and the text-division elements into which these may be subdivided.

+

The module for verse extends the facilities provided by these modules in the following ways: + + a special purpose caesura element is provided, to allow for segmentation of + the verse line (see section ) + a set of attributes is provided for the encoding of rhyme scheme and metrical + information (see sections and ) + a special purpose rhyme element is provided to support simple analysis of + rhyming words (see section ) +

+ + +
+ Structural Divisions of Verse Texts +

Like other kinds of text, texts written in verse may be of widely differing lengths and + structures. A complete poem, no matter how short, may be treated as a free-standing text, + and encoded in the same way as a distinct prose text. A group of poems functioning as a + single unit may be encoded either as a group or as a text, depending on + the encoder's view of the text. For further discussion, including an example encoding for a + verse anthology, see chapter .

+

Many poems consist only of ungrouped lines. + + + + + + + + + + + + + + + + + + + + + + + This short poem by Emily + Dickinson is a simple case: + + 1755 + + + To make a prairie it takes a clover and one bee, + One clover, and a bee, + And revery. + The revery alone will do, + If bees are few. + + + + + +

+

Often, however, lines are grouped, formally or informally, into stanzas, verse paragraphs, + etc. The lg element defined in the core tag set (in section ) + may be used for all such groupings. It may thus serve for informal groupings of lines such + as those of the following example from Allen Ginsberg: + + My Alba + + Now that I've wasted + five years in Manhattan + life decaying + talent a blank + + + talking disconnected + patient and mental + sliderule and number + machine on a desk + + + + + + +

+

It may also be used to mark the verse paragraphs into which longer poems are often divided, + as in the following example from Samuel Taylor Coleridge's Frost at + Midnight: + The Frost performs its secret ministry, + Unhelped by any wind. ... + Whose puny flaps and freaks the idling Spirit + By its own moods interprets, every where + Echo or mirror seeking of itself, + And makes a toy of Thought. + + + But O! how oft, + How oft, at school, with most believing mind + Presageful, have I gazed upon the bars, + To watch that fluttering stranger! ... + + + Dear Babe, that sleepest cradled by my side, + + Note, in the above example, + the use of the part attribute on the l element, where a verse line is + broken between two line groups, as discussed in section .

+

Most typically, however, the lg element is used to mark the highly regular line + groups which characterize stanzaic and similar verse forms, as in the following example + from Chaucer: + Sire Thopas was a doghty swayn; + White was his face as payndemayn, + His lippes rede as rose; + His rode is lyk scarlet in grayn, + And I yow telle in good certayn, + He hadde a semely nose. + + + His heer, his ber was lyk saffroun, + That to his girdel raughte adoun; + + +

+

Like other text-division elements, lg elements may be nested hierarchically. For + example, one particularly common English stanzaic form consists of a quatrain or sestet + followed by a couplet. The lg element may be used to encode both the stanza and + its components, as in the following example from Byron: + + In the first year of Freedom's second dawn + Died George the Third; although no tyrant, one + Who shielded tyrants, till each sense withdrawn + Left him nor mental nor external sun: + A better farmer ne'er brushed dew from lawn, + A worse king never left a realm undone! + + + He died — but left his subjects still behind, + One half as mad — and t'other no less blind. + + + +

+

Note the use of the type attribute to name the type of unit encoded by the + lg element; this attribute is common to all members of the att.divLike class (see section ).For discussion of other attributes of this class, see . + When used on lg, the type attribute is intended solely for conventional + names of different classes of text block. For systematic analysis of metrical and rhyme + schemes, use the met and rhyme attributes, for which see below, + section .

+

As a further example, consider the Shakespearean sonnet. This may be divided into two + parts: a concluding couplet, and a body of twelve lines, itself subdivided into three quatrains: + + + + + + + + My Mistres eyes are nothing like the Sunne, + Currall is farre more red, then her lips red + If snow be white, why then her brests are dun: + If haires be wiers, black wiers grown on her head: + + + I have seene Roses damaskt, red and white, + But no such Roses see I in her cheekes, + And in some perfumes is there more delight, + Then in the breath that from my Mistres reekes. + + + I love to heare her speake, yet well I know, + That Musicke hath a farre more pleasing sound: + I graunt I never saw a goddesse goe, + My Mistres when shee walkes treads on the ground. + + + + And yet by heaven I think my love as rare, + As any she beli'd with false compare. + + + + +

+

Particularly lengthy poetic texts are often subdivided into units larger than stanzas or + paragraphs, which may themselves be subdivided. Spenser's Faery Queene, for + example, consists of twelve books each of which contains a prologue + followed by twelve cantos. Each prologue and each canto consists of + nine-line stanzas, each of which follows the same regular pattern. + Other examples in the same tradition are easy to find.

+ +

Large structures of this kind are most conveniently represented by div or + div1 elements, as described in section . Thus the start + of the Faerie Queene might be encoded as follows: +

+
+ + A Gentle Knight was pricking on the plain + Y cladd in mightie armes and silver shielde, + +
+
+ The encoder must choose at which point in the hierarchy of structural + units to introduce lg elements rather than a yet smaller div element: it + would (for example) also be possible to encode the above example as follows: +
+
+
+ A gentle knight was pricking on the plain + Ycladd in mightie armes and silver shielde, +
+
+
+

+ +

One reason for using div rather than lg elements is that the former may + contain non-metrical elements, such as epigraphs or dedications and other members of the + model.divTop class, whereas lg elements may contain + only headings or metrical lines.

+
+
+ Components of the Verse Line +

It is often convenient for various kinds of analysis to encode subdivisions of verse lines. + The general purpose seg element defined in the tag set for segmentation and + alignment (section ) is provided for this purpose: + +

+

To use this element together with the module for verse, the module for segmentation and + alignment must also be enabled as further described in section .

+

In Old and Middle English alliterative verse, individual verse lines are typically split + into half lines. The seg element may be used to mark these explicitly, as in the + following example from Langland's Piers Plowman: In a somer + seson, + whan softe was the sonne, + I shoop me into shroudes + as I a sheep were, + In habite as an heremite + unholy of werkes, + Went wide in this world + wondres to here. + +

+

The seg element can be nested hierarchically, in the same way as the lg + element, down to whatever level of detailed structure is required. In the following + example, the line has been divided into feet, each of which has been further + subdivided into syllables.As elsewhere in these Guidelines, this + example has been formatted for clarity of exposition rather than correct display. Note + in particular that whether an XML processor retains whitespace within the seg + element or not (this can be configured by means of the xml:space attribute) + this example will still require additional processing, since whitespace should be + retained for the lower level seg elements (those of type syll) but + not for the higher level one (those of type foot). + + Arma vi + rumque ca + no Tro + iae qui + primus ab + oris + +

+

The seg element may be used to identify any subcomponent of a line which has + content; its type attribute may characterize such units in any way appropriate to the needs + of the encoder. For the specific case of labeling each foot with its formal type + (dactyl, spondee, etc.), and each syllable with its metrical or prosodic + status (syllables bearing primary or secondary stress, long syllables, short syllables), + however, the specialized attributes met and real are defined, which + provide a more systematic framework than the type attribute; see section below.

+

In classical verse, a hexameter like that above may also be formally divided into two + cola or hemistiches. This example provides a typical + case, in that the boundary of the first colon falls in the middle of one of the feet + (between the syllables no and Tro). If both kinds of segmentation are + required, the part attribute might be used to mark the overlapping structure as + follows. + + + Ar + ma + vi + + + rum + que + ca + + + no + + + + + Tro + + + iae + qui + + + +

+

Instead of using the part attribute on the seg element, it might be + simpler just to mark the point at which the caesura occurs. An additional element is + provided for analyses of this kind, in which what is to be marked are points between the + words, which have some significance within a verse line: + + In classical prosody, the caesura, which occurs within a foot, is + distinguished from a diaeresis, which occurs on a foot boundary (not to be + confused with the division of a diphthong into two syllables, or the diacritic symbol used + to indicate such division, each of which is also termed diaeresis). This + distinction is rarely made nowadays, the term caesura being used for + any division irrespective of foot boundaries. No special-purpose diaeresis element is therefore provided.

+

As an example of the caesura element, we refer again to the example from Langland. + An encoder might choose simply to record the location of the caesura within each line, + rather than encoding each half-line as a segment in its own right, as follows: In a somer seson, + whan softe was the sonne, + I shoop me into shroudes as I a sheep were, + In habite as an heremite unholy of werkes, + Went wide in this world wondres to here. +

+

Logically, the opposite of caesura might be considered to be enjambement. When + the verse module is included in a schema, an additional class + called att.enjamb is defined as follows: + + The following lines demonstrate the use of the enjamb attribute to + mark places where there is a discrepancy between the boundaries of the l elements + and the syntactic structure of the verse (a discrepancy of some significance in some + schools of verse): Un astrologue, un jour, se laissa choir + Au fond d'un puits. + + + + + +

+
+
+ Encoding Textual Structures Across Verses +

It is possible that certain textual structures may span multiple lines of verse, either by + incorporating more than one, or by crossing line hierarchy. This is common, + for example, when lines contain reported thought or speech (i.e. said), + or other forms of quotation (i.e. q). For these cases, it is recommended practice + to fragment and reconstruct the elements representing the textual structures. +

+

The following example from Margaret Cavendish's Nature's Pictures shows speech + encoded across two lines reconstructed by chaining elements with prev and + next attributes: + + Our lives, ſaid he, + wee'll give before we yield, + + + Wee'll win your battles, or dye in the field. + + +

+

Alternatively, the elements may be reconstructed with stand-off markup using the element join: + + + Our lives, ſaid he, + wee'll give before we yield, + + + Wee'll win your battles, or dye in the field. + + + +

+ +

+ +

+

+ A more general discussion of these and other strategies to deal with fragmentation and reconstruction + appears in section . +

+
+
+ Rhyme and Metrical Analysis +

When the module for verse is in use, the following additional attributes are available to + record information about rhyme and metrical form: + + +

+

These attributes may be attached to the lg element, or to the higher-level + text-division elements div, div1, etc. In general, the attributes should + be specified at the highest level possible; they may not however be specifiable at the + highest level if some of the subdivisions of a text are in prose and others in verse. All + these attributes may also be attached to the l and seg elements, but the + default notation for the rhyme attribute has no defined meaning when specified + on l or seg. The value for these attributes may take any form desired by + the encoder, but the nature of the notation used will determine how well the attribute + values can be processed by automatic means.

+

The primary function of the metrical attributes is to encode the conventional metrical or + rhyming structure within which the poet is working, rather than the actual prosodic + realization of each line; the latter can be recorded using the real attribute, + as further discussed below. A simple mechanism is also provided for recording the actual + realization of a rhyme pattern; see .

+
+ Sample Metrical Analyses +

As a simple example of the use of these attributes, consider the following lines from + Pope's Essay on Criticism:

+ + 'Tis hard to say, if greater Want of Skill + Appear in Writing or in Judging ill; + But, of the two, less dang'rous is th'Offence, + To tire our Patience, than mis-lead our Sense: + +
+ +

+

This text is written entirely in heroic couplets; each line is an iambic + pentameter (which, using a common notation, can be described with the formula + -+|-+|-+|-+|-+/, each - denoting a metrically unstressed + syllable, each + a metrically stressed one, each | a foot + boundary, and the / a line-end), and the couplets rhyme (which can be + represented with the conventional formula aa).

+

Because both rhyme pattern and metrical form are consistent throughout the poem, they + may be conveniently specified on the div element; the values given for the + attributes will be inherited by any metrical unit contained within the div + elements of this poem, and must be interpreted in the appropriate way.

+

Since the notation used in the met, real, and rhyme + attributes is user-defined, no binding description can be given of its details or of how + its interpretation must proceed. (A default notation is provided for the + rhyme attribute, which however the encoder can replace with another; see + section .) It is expected, however, that software should be able to + support these attributes in useful ways; the more intelligent the software is, and the + more knowledge of metrics is built into it, the better it will be able to support these + attributes. In the extract given above, for example, the met and + rhyme attribute values specified on the div element are inherited + directly by the lg elements nested within it. Since the met value + specifies the metrical form of a single verse line, the structure of the lg as + a whole is understood to involve as many repetitions of the pattern as there are lines + in the verse paragraph. The same attribute value, when inherited in turn by the + l element, must be understood not to repeat. With sufficiently + sophisticated software, segments within the line might even be understood as inheriting + precisely that portion of the formula which applies to the segment in question; this + will, however, be easier to accomplish for some languages than for others.

+

The rhyme attribute in this example uses the default notation to specify a + rhyme scheme applicable only to pairs of lines. As elsewhere, the default notation for + the rhyme attribute has no meaning for metrical units at the line level or + below. In verse forms where line-internal rhyme is structurally significant, e.g. in + some skaldic poetry, the default notation is incapable of expressing the required + information, since the rhyme pattern may need to be specified for units smaller than the + line. In such cases, a user-specified rhyme notation must be substituted for the default + notation, or else the rhyme pattern must be described using some alternative method + (e.g. by using the link mechanism described below).

+

The precise semantics of the met attribute and the inferences which software + is expected or able to draw from it, are implementation-dependent; so are the semantics + and processing of the rhyme attribute, when user-specified notations are + used.

+

A formal definition of the significance of each component of the pattern given as the + value of the met attribute may be provided in the metDecl element + within the encodingDesc element in the TEI header (see section ). The encoder is free to invent any notation appropriate to his or + her analytic needs, provided that it is adequately documented in this element. The + notation may define metrical components using invented or traditional names (such as + iamb or hexameter) or in terms of basic units such as codes for + stressed or unstressed syllables, or a combination of the two.

+

The real (for realization) attribute may optionally be specified to + indicate any deviation from the pattern defined by the met attribute which + the encoder wishes to record. By default, the real attribute has the same + value as the met attribute on the same element; it is only necessary to + provide an explicit value when the realization differs in some way from the abstract + metrical pattern. The tension between conventional metrical pattern and its realization + may thus be recorded explicitly. For example, many readers of the above passage would + stress the word But at the beginning of the third line rather than the word + of following it, as the metrical pattern would normally require. This + variation might be encoded as follows: + + But, of the two, ... + +

+

Where the real attribute is used to over-ride the default or conventional + metrical pattern, it applies only to the element on which it is specified. The default + pattern for any subsequent lines is unaffected.

+

As it happens, this particular kind of variation is very common in the English iambic + pentameter—it even has a name: trochaic substitution—an encoder might + therefore + + choose to regard this not as an + instance of a variant realization, but as an instance of a variant metrical form: + + But, of the two, ... + Alternatively, a different metrical notation might be defined, in + which this kind of variation was permitted throughout the text.

+

In choosing whether to over-ride a metrical specification in this way or by using the + real attribute, the encoder is required to determine whether the change is + a systematic or conventional one (as in this example) or an occasional variation, + perhaps for local effect. In the following example, from Goethe's Auf + dem See, the variation is a matter of local realization: + + + + Und frische Nahrung, neues Blut + Saug' ich aus freier Welt; + Wie ist Natur so hold und gut, + Die mich am Busen hält! + Die Welle wieget unsern Kahn + Im Rudertakt hinauf, + Und Berge, wolkig himmelan, + Begegnen unserm Lauf. + On the other hand, the famous inserted alexandrine in Pope's Essay + on Criticism, might be encoded as follows: A + needless alexandrine ends the song, + That, like a wounded + snake, drags its slow length along. + + Here the + met attribute indicates that a different metrical convention (the + alexandrine) is in force, while the real attribute indicates that there is a + variation from that convention. As with many other aspects of metrical analysis, + however, this is of necessity an entirely interpretive judgment.

+
+
+ Segment-Level versus Line-level Tagging +

The examples given so far have encoded information about the realization of metrical + conventions at the level of the whole verse-line. This has obvious advantages of + simplicity, but the disadvantage that any deviation from metrical convention is not + marked at its precise point of occurrence in the text. Greater precision may be + achieved, but only at the cost of marking deviant metrical units explicitly. This may be + done with the seg element, giving the variant realization as the value of the + real attribute on that element. Using this method, the example given + immediately above might be encoded as follows: A needless alexandrine ends the song, + + That, like a wounded snake, + drags its + slow length along. The marking of the + foot boundaries with the symbol | in the met attribute value of + the l element allows the human reader, or a sufficiently intelligent software + program, to isolate the correct portion of that attribute value as the default value for + the same attribute on the seg elements for feet, namely -+. It is of + course up to the encoder to decide whether or not to include the n attribute + of seg here, and whether or not also to tag the feet in the line in which there + is no deviation from the metrical convention. The ability of software to infer which + foot is being marked, if not all are tagged, will depend heavily on the language of the + text and the knowledge of prosody built into the software; the fuller and more explicit + the markup, the easier it will be for software to handle it. It may prove useful, + however, to mark metrical deviations in the manner shown, even if the available software + is not sufficiently intelligent to scan lines without aid from the markup. Human readers + who are interested in prosody may well be able to exploit the markup in useful ways even + with less sophisticated software.

+

There are circumstances where it may also be useful to use the met attribute + of seg. If we wish to identify the exact location of the different types of + foot in the first line of Virgil's Aeneid, the text could be encoded as + follows (for simplicity's sake the caesura has been omitted): Arma vi + rumque ca + no Tro + iae qui + primus ab + oris + An appropriate value of the met attribute might also be + supplied on the enclosing div element, to indicate that each foot may be made + up of a dactyl or a spondee, so that the values given here for met at the + level of the foot may be considered a series of local variations on this fundamental + pattern; in cases like this, of course, the local variations may also be considered + aspects of realization rather than of convention, in which case the real + attribute may be used instead of met, if desired.

+
+
+ Metrical Analysis of Stanzaic Verse +

The method described above may be used to encode quite complex verse forms, for instance + various kinds of fixed-form stanzas. Let us take one of Dante's canzoni, in which each + stanza except the last has the same combination of eleven-syllable and seven-syllable + lines, and the same rhyme scheme:

+ + Doglia mi reca nello core ardire + +
+

+

Here the met attribute specifies a metrical pattern for each of the + twenty-one lines making up a stanza of the canzone. Each stanza inherits + this definition from the parent div element. The rhyme attribute + specifies a rhyme scheme for each stanza, in the same way.

+

In the metrical notation used here, the letter E represents a line containing + nine syllables which may or may not be metrically prominent, a tenth which is prominent + and an optional non-prominent eleventh syllable. The letter S is used to + represent a line containing five syllables which may or may not be metrically prominent, + a sixth which is prominent and an optional non-prominent seventh syllable. A suitable + definition for this notation might be given by a metDecl element like the + following: + + + xxxxxxxxx+o + xxxxx+o + metrically prominent or non-prominent + metrically prominent + optional non prominent + line division + + +

+

As noted above, the metrical pattern specified on the div applies to each + lg (stanza) element contained within the div. In fact however, + after seven stanzas of this type, there is a final stanza, known as a + commiato or envoi, which follows a different metrical and rhyming + scheme. The solution to this problem is simply to specify a new met attribute + on the eighth stanza itself, which will override the default value inherited from parent + div, as follows:

+ + ... + + + Canzone, presso di qui è une donna + +

+

Note that, in the same way as for the real attribute, over-riding of this + kind does not affect subsequent elements at the same hierarchic level. Any lg + element following the commiato above would be assumed to use the same + metrical and rhyming scheme as the one preceding the commiato. Moreover, + although it is quite regular (in the sense that the last stanza of each + canzone is a commiato), the over-riding must be specified + for each case.

+
+
+
+ Rhyme + +

The rhyme attribute is used to specify the rhyme pattern of a verse form. It + should not be confused with the rhyme element, which is used to mark the actual + rhyming word or words: + +

+ +

Like the met attribute, the rhyme attribute can be used with a + user-specified notation documented by the metDecl element in the TEI header. + Unlike met, however, the rhyme attribute has a default notation; if + this default notation is used, no metDecl element need be given.

+

The default notation for rhyme offers the ability to record patterns of rhyming lines, + using the traditional notation in which distinct letters stand for rhyming lines. For a + work in rhyming couplets, like the Pope example above, the rhyme attribute + simply specifies aa, indicating that pairs of adjacent lines rhyme with each + other. For a slightly more complex scheme, applicable to groups of four lines, in which + lines 1 and 3 rhyme, as do lines 2 and 4, this attribute would have the value + abab. The traditional Spenserian stanza has the pattern ababbcbcc, + indicating that within each nine line stanza, lines 1 and 3 rhyme with each other, as do + lines 2, 4, 5 and 7, and lines 6, 8 and 9.

+

Non-rhyming lines within such a group may be represented using a hyphen or an x, as in the + following example: + + Why, all the Saints and Sages who discuss'd + Of the Two Worlds so learnedly, are thrust + Like foolish Prophets forth; their Words to Scorn + Are scatter'd, and their Mouths are stopt with Dust. + +

+

The rhyme element may be used to mark the words (or parts of words) which rhyme + according to a predefined pattern: + Outside in the distance a wildcat did growl + Two riders were approaching and the wind began to howl + + +

+

The label attribute is used to specify which parts of a rhyme scheme a given set + of rhyming words represent: + I wander thro' each charter'd street, + Near where the charter'd Thames does flow, + And mark in every face I meet + Marks of weakness, marks of woe. + + In every cry of every Man + In every Infant's cry of fear, + In every voice, in every ban, + The mind-forg'd manacles I hear. + +

+

Within a given scope, all rhyme elements with the same value for their + label attribute are assumed to rhyme with each other: thus, in the above + example, the two rhymes labelled a in the first stanza rhyme with each other, + but not necessarily with those labelled a in the second stanza. The scope is + defined by the nearest ancestor element for which the rhyme attribute has been + supplied.

+ +

The rhyme element can appear anywhere within a verse line, and not necessarily + around a single word. It can thus be used to mark quite complex internal rhyming schemes, + as in the following example: + The sunlight on the garden + Hardens and grows cold, + We cannot cage the minute + Within its nets of gold + When all is told + We cannot beg for pardon. + + +

+

This mechanism, although reasonably simple for simple cases, may not be appropriate for + more complex applications. In general, rhyme may be considered as a special form of + correspondence, and hence encoded using the mechanisms defined for + that purpose in section . Similar considerations apply to other + metrical features such as alliteration or assonance.

+

To use the correspondence mechanisms to represent the complex rhyming pattern of the above + example, each rhyme element must be given a unique identifier, as follows: + The sunlight on the garden + Hardens and grows cold, + We cannot cage the minute + Within its nets of gold + When all is told + We cannot beg for pardon. + + Now that each rhyming word, or part-word, has been tagged and allocated an + arbitrary identifier, the general purpose link element may be used to indicate + which of the rhyme elements share the same rhyme, as follows: + + + + + +

+

For further discussion of the link and linkGrp element, see section .

+

The rhyme and caesura phrase level elements are made available by the + model.lPart class when the module defined by this chapter is + included in a schema.

+
+ +
+ Metrical Notation Declaration +

When the module defined in this chapter is included in a schema, a specialized element is + optionally available in the encodingDesc element of the TEI header to document the + metrical notation used in marking up a text. + + +

+

As with other components of the header, metrical notation may be specified either formally + or informally. In a formal specification, every symbol used in the metrical notation must + be documented by a corresponding metSym element; in an informal one, only a brief + prose description of the way in which the notation is used need be given. In either case, + the optional pattern attribute may be used to supply a regular expression which + a processor can use to validate expressions in the intended notation. The following + constraints apply: + if pattern is supplied, any notation used which does not conform to it + should be regarded as invalid + if any metSym is defined, then any notation using undefined symbols + should be regarded as invalid + if both pattern and symbol are defined, then every symbol appearing explicitly + within pattern must be defined + symbols which are not matched by pattern may be defined within a + metDecl element +

+

As a simple example, consider the case of the notation in + which metrical prominence, metrical feet, and line boundaries + are all to be encoded. Legal specifications in this notation may + be written for any sequence of metrically prominent or + non-prominent features, optionally separated by foot or metrical + line boundaries at arbitrary points. Assuming that the symbol + 1 is used for metrical prominence, + 0 for non-prominence, + | for foot boundary and + / for line boundary, then the following + declaration achieves this objective: + + + metrical prominence + metrical non-prominence + foot boundary + metrical line boundary + + +

+

The same notation might also be specified less formally, as follows: + + +

Metrically prominent syllables are marked '1' and other + syllables '0'. Foot divisions are marked by a vertical bar, + and line divisions with a solidus.

+

This notation may be applied to any metrical unit, of any + size (including, for example, individual feet as well as + groups of lines).

+ + + Note that in this case, because the pattern attribute has + not been supplied, no processor can validate met attribute values within the + text which use this metrical notation.

+

For more complex cases, it will often be more convenient to + define a notation incrementally. The terminal + attribute should be used to indicate for a given symbol whether + or not it may be re-defined in terms of other symbols used + within the same notation. For example, here is a notation for + encoding classical metres, in which symbols are provided for the + most common types of foot. These symbols are themselves + documented within the same notation, in terms of more primitive + long and short syllables: + + + -oo + -o + o- + -- + ooo + oo- + short syllable + long syllable + + + Note here the use of the global n attribute to supply + an additional name for the symbols being documented.

+ +

Where an encoder wishes to use more than one different + pattern for metrical notation, multiple metDecl + elements may be included in the encodingDesc, each + supplied with an xml:id. The decls + attribute may be used in the text of the document to specify + which metDecl is in force at a particular point in the + text. In this example, two metDecls are defined in the + header, one with an English verse pattern and one with a French + pattern. In the body of the document, there are two div + elements, one declaring the English pattern and one the + French: + + + + + stressed syllable + unstressed syllable + metrical line boundary + + + syllabe tonique + syllabe atone + pause métrique + + + + + +

+ + + + +
+
+ + + + +
+ + +

+ + + + +
+ +
+ Encoding Procedures for Other Verse Features +

A number of procedures that may be of particular concern to encoders of verse texts are + dealt with elsewhere in these guidelines. Some aspects of layout and physical appearance, + especially important in the case of free verse, are dealt with in chapter . Some initial recommendations for the encoding of phonetic or prosodic transcripts, + which may be helpful in the analysis of sound structures in poetry, are to be found in + chapter ; it may also be found convenient to use standard entity names + (those proposed for the International Phonetic Alphabet suggest themselves) to mark + positions of suprasegmentals such as primary and secondary stress, or other aspects of + accentual structure.

+ +

As already indicated, chapter contains much which will be found useful + for the aligning of multiple levels of commentary and structure within verse analysis. + Encoders of verse (as of other types of literary text) will frequently wish to attach + identifying labels to portions of text that are not part of a system of hierarchical + divisions, may overlap with one another, and/or may be discontinuous; for instance passages + associated with particular characters, themes, images, allusions, topoi, styles, or modes + of narration. Much of the computerized analysis of verse seems likely to require dividing + texts up into blocks in this way. The span element discussed in provides the means for doing this. Finally, the procedures for the + tagging of feature structures, described in chapter , provide a powerful + means of encoding a wide variety of aspects of verse literature, including not only the + metrical structures discussed above, but also such stylistic and rhetorical features as + metaphor.

+

For other features it must for the time being be left to encoders to devise their own + terminology. Elements such as metaphor tenor="..." vehicle="..." ... + /metaphor might well suggest themselves; but given the problems of definition + involved, and the great richness of modern metaphor theory, it is clear that any such + format, if predefined by these Guidelines, would have seemed objectionable to some and + excessively restrictive to many. Leaving the choice of tagging terminology to individual + encoders carries with it one vital corollary, however: the encoder must be utterly + explicit, in the TEI header, about the methods of tagging used and the criteria and + definitions on which they rest. Where no formal elements are currently proposed, such + information may readily be given as simple prose description within the + encodingDesc element defined in section .

+
+ +
+ Module for Verse +

The module described in this chapter makes available the + following components: + + Verse + Verse structures + Poésie + 韻文結構 + Strutture poetiche + Estrutura dos versos + 韻文モジュール + + + The selection and combination of modules to form a TEI schema + is described in .

+ + + + + + +
+
\ No newline at end of file diff --git a/P5/Source/Guidelines/fr/WD-NonStandardCharacters.xml b/P5/Source/Guidelines/fr/WD-NonStandardCharacters.xml deleted file mode 120000 index 58533a1b20..0000000000 --- a/P5/Source/Guidelines/fr/WD-NonStandardCharacters.xml +++ /dev/null @@ -1 +0,0 @@ -../en/./WD-NonStandardCharacters.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/WD-NonStandardCharacters.xml b/P5/Source/Guidelines/fr/WD-NonStandardCharacters.xml new file mode 100644 index 0000000000..ed1ec4eb83 --- /dev/null +++ b/P5/Source/Guidelines/fr/WD-NonStandardCharacters.xml @@ -0,0 +1,1329 @@ + + + + +
+Characters, Glyphs, and Writing Modes + + +

Chapter introduced the fundamental notions of +language identification and character representation in an encoded TEI +document. In this chapter we discuss some additional issues relating +to the way that written language is represented in a TEI document. In +sections and we +introduce markup which may be used to represent and document +non-standard characters, that is, written symbols for which no +codepoint exists in Unicode. The same markup may be used to annotate +existing characters according to their visual or other properties, and +thus process them as distinct glyphs (see section ), or to define new characters or glyphs (section +). We also provide recommendations concerning +the Unicode Private Use Area (. Finally, in +section we +discuss ways of documenting the writing mode used in a source text, +that is, the directionality of the script, the orientation of +individual characters, and related questions.

+ + + +
Is Your Journey Really Necessary? +

Despite the availability of Unicode, text encoders still +sometimes find that the published repertoire of available +characters is inadequate to their needs. This is particularly the +case when dealing with ancient languages, for which encoding +standards do not yet exist, or where an encoder wishes to +represent variant forms of a character or glyphs. +The module defined by this chapter provides a mechanism to satisfy +that need, while retaining compatibility with standards. +

+

When encoders encounter some graphical unit in a document which is +to be represented electronically, the first issue to be resolved +should be Is this really a different character? To determine +whether a particular graphical unit is a character or +not, see .

+

If the unit is indeed determined to be a character, the next +question should be Has this character been encoded already? +In order to determine whether a character has been encoded, +encoders should follow the following steps: + +

Check the Unicode + web site at , in particular the page "Where is my + Character?", and the associated character code charts. + Alternatively, users can check the latest published version of + The Unicode Standard (Unicode Consortium (2006)), though the web site is + often more up to date than the printed version, and should be + checked for preference.

+

The pictures (glyphs) in the Unicode code +charts are only meant to be representative, not definitive. If a +specific form of an already encoded character is required for a +project, refer to the guidelines contained below under Annotating Characters. Remember that your +encoded document may be rendered on a system which has different fonts +from yours: if the specific form of a character is important to you, +then you should document it.

+ Check the Proposed New Characters web page () to see whether + the character is in line for approval. + +Ask on the Unicode email list () to +see whether a proposal is pending, or to determine whether this +character is considered eligible for addition +to the Unicode Standard. + +

+

Since there are now over 130,000 characters in Unicode, +chances are good that what you need is already there, but it might +not be easy to find, since it might have a different name in +Unicode. Editors working with East Asian writing systems should consult +the Unihan Database. +Look again, this time at other sites, preferably ones which also provide searches based on scripts and languages. For example (for CJK characters) or (for non-CJK characters) . +Take care, however, that all the +properties of what seems to be a relevant character are consistent +with those of the character you are looking for. For example, if +your character is definitely a digit, but the properties of the +best match you can find for it say that it is a letter, you may +have a character not yet defined in Unicode.

+

In general, it is advisable to avoid Unicode characters generally +described as presentation forms.Specifically, +characters in the Unicode blocks Alphabetic Presentation Forms, Arabic Presentation Forms-A, Arabic Presentation Forms-B, Letterlike Symbols,and Number Forms. However, if the character you are looking for is being used in a notation (rather than as part of the orthography of a language) then it is quite acceptable to select characters from the Mathematical Operators block, provided that they have the appropriate properties (i.e. So: Symbol, Other; or Sm: +Symbol, Math).

+

An encoded character may be precomposed or it may be formed +from base characters and combining diacritical marks. Either will +suffice for a character to be "found" as an encoded character. If there are several possible Unicode characters to choose amongst, +it is good practice to consult other colleagues and practitioners to +see whether a consensus has emerged in favour of one or other of +them.

+

If, however, no suitable form of your character seems to exist, the +next question will be: Does the graphical unit in question +represent a variant form of a known character, or does it represent a +completely unencoded character? If the character is determined to +be missing from the Unicode Standard, it would be helpful to submit +the new character for inclusion (see ). For assistance +on writing or submitting a proposal, potential proposers can contact +the UC Berkeley Script Encoding Initiative ().

+

These guidelines will help you proceed once you have + identified a given graphical unit as either a variant or an + unencoded character. Determining this will require knowledge of + the contents of the document that you have. The first case will + be called annotation of a character, while the + second case will be called adding of a new + character. How to handle graphical units that represent variants + will be discussed below () + while the problem of representing new characters will be dealt + with in section .

+

While there is some overlap between these requirements, +distinct specialized markup constructs have been created for each +of these cases. These constructs are presented in section +below.

+
+
+ +Markup Constructs for Representation of Characters and Glyphs +

An XML document can, in principle, contain any defined Unicode +character. The standard allows these characters to be represented +either directly, using an appropriate encoding (UTF-8 by default), or +indirectly by means of a numeric character reference (NCR), such as +&#196; (A-umlaut). The encoder can also restrict the +range of characters which are represented directly in a document (or +part of it) by adding a suitable encoding declaration. For example, if +a document begins with the declaration <?xml +encoding="iso-8859-1"?> any Unicode characters which are not +in the ISO-8859-1 character set must be represented by NCRs.

+

The gaiji module defined by this + chapter adds a further way of representing specific characters + and glyphs in a document. (Gaiji is from Japanese 外字, meaning external + characters.) This allows the encoder to distinguish + characters and glyphs which Unicode regards as identical, to add + new nonstandard characters or glyphs, and to represent Unicode + characters not available in the document encoding by an + alternative means.

+

The mechanism provided here consists functionally of two parts: + + an element g, which serves as a proxy for new + characters or glyphs + elements char and glyph, providing information about such characters or glyphs; these elements are stored in the + charDecl element in the header. + +

+

When the gaiji module is included in a schema, the +charDecl element is added to the model.encodingDescPart +class, and the g element is added to the phrase class. These +elements and their components are documented in the rest of this +section.

+

The Unicode standard defines properties for all the characters it +defines in the Unicode Character Database , knowledge of which is usually built into text processing systems. If the +character represented by the g element does not exist in Unicode at +all, its properties are not available. If the character represented is +an existing Unicode character, but is not available in the document +character set recognized by a given text processing system, it may +also be convenient to have access to its properties in the same way. +The char element makes it possible to store properties +for use by such applications in a standard way.

+

The list of attributes (properties) for characters is modelled on +those in the Unicode Character Database, which distinguishes +normative and informative character +properties. The Unicode Consortium also maintains a separate set of character properties specific to East Asian characters in the Unihan database which TEI fully supports. Lastly, non-Unicode properties may also be supplied. +Since the list of properties will vary with different versions of the +Unicode Standard, there may not be an exact correspondence between +them and the list of properties defined in these Guidelines.

+ +

Usage examples for these elements are given below at and . The gaiji module +itself is formally defined in section +below. It declares the following additional elements: + + + + +The charDecl element is a member of the class model.encodingDescPart, and thus becomes +available within encodingDesc when this module is included in +a schema. The g element is the only member of the class +model.gLike: this class is referenced as +an alternative to plain text in almost every element which contains +plain text, thus permitting the g element also to appear at +such places when this module is included in a schema. +

+

The following elements may appear within a charDecl + element: + + + + + +

+

The char and glyph elements have similar contents +and are used in similar ways, but their functions are different. The +char element is provided to define a character which is not +available in the current document character set, for whatever reason, +as stated above. The glyph element is used to annotate a +character that has already been defined somewhere (either in the +document character set, or through a char element) by +providing a specific glyph that shows how a character appeared in the +original document. This is necessary since Unicode code points refer +not to a single, specific glyph shape of a character, but rather to a +set of glyphs, any of which may be used to render the code point in +question; in some cases they can differ considerably.

+

The glyph element is provided for cases where the encoder +wants to specify a specific glyph (or family of glyphs) out of all +possible glyphs. Unfortunately, due to the way Unicode has been +defined, there are cases where several glyphs that logically belong +together have been given separate code points, especially in the blocks +defining East Asian characters. In such cases, glyph elements +can also be used to express the view that these apparently distinct +characters are to be regarded as instances of the same character (see +further ).

+

The Unicode Standard recommends naming conventions which should be +followed strictly where the intention is to annotate an existing +Unicode character, and which may also be used as a model when +creating new names for characters or glyphsIt should be noted, however, that this naming convention cannot meaningfully be applied to East Asian characters; the typical Unicode descriptions for these characters take the form CJK Unified Ideograph U+4E00, where U+4E00 is simply the Unicode code point value of the character in question. In cases where no Unicode code point exists, there is little hope of finding a name that helps to identify the character. Names should therefore be constructed in a way meaningful to local practice, for example by using a reference number from a well-known character dictionary or a project-specific serial number.:

+

Within both char and glyph, the following elements are available: + + + + + + + + + + +

+ +

Four of these elements (gloss, desc, +figure, and note) are defined by other TEI +modules, and their usage here is no different from their usage +elsewhere. The figure element, however, is used here only to +link to an image of the character or glyph under discussion, or to +contain a representation of it in SVG. The figure element may +contain more than one graphic +element, for example to provide images with different +resolution, or in different formats, or may itself be repeated. As +elsewhere, the mimeType attribute +of graphic should be used to specify +the format of the image.

+

The mapping element is similar to the standard TEI +equiv element. While the latter is used to express +correspondence relationships between TEI concepts or elements and +those in other systems or ontologies, the former is used to express +any kind of relationship between the character or glyph under +discussion and characters or glyphs defined elsewhere. It may contain +any Unicode character, or a g element linked to some other +char or glyph element, if, for example, the +intention is to express an association between two non-standard +characters. The type of association is indicated by the +type attribute, which may take such values as +exact for exact equivalences, uppercase for +uppercase equivalences, lowercase for lowercase +equivalences, standard for standardized forms, and +simplified for simplified characters, etc., as in the +following example: + + + +a + + + +

+

The mapping element may also be used to represent a mapping of the +character or (more likely) glyph under discussion onto a character +from the private use area as in this example: + + + +Z +U+E304 + + + +

+

A more precise documentation of the properties of any character or +glyph may be supplied using one of the three property elements: localProp, unicodeProp, or unihanProp; these are described in the next section.

+
Character Properties +

The Unicode Standard documents ideal +characters, defined by reference to a number of +properties (or attribute-value pairs) which they are said +to possess. For example, a lowercase letter is said to have the value +Ll for the property General_Category. The +Standard distinguishes between normative properties +(i.e. properties which form part of the definition of a given +character), and informative or additional +properties which are not normative. It also allows for the addition of +new properties, and (in some circumstances) alteration of the values +currently assigned to certain properties. When making such +modifications, great care should be taken not to override standard +informative properties for characters which already exist in the Unicode +Standard, as documented in Freytag (2006).

+ +

The unicodeProp, unihanProp, and +localProp elements allow a TEI encoder to record information +about a character or glyph: + + + + + +

+

Where the information concerned relates to a property which has +already been identified in the Unicode Standard, use of the +appropriate Unicode property name with unicodeProp is +strongly encouraged. The use of available Unihan property names with +unihanProp is similarly encouraged. Validation rules for +property names according to Unicode conventions +are incorporated into the TEI schemas. Where neither of these +standards suffices use localProp.

+ +

The three elements for recording Unicode or locally defined properties belong to the att.gaijiProp class. This class defines two required attributes for record key-value pairs for character properties: + + + + +For each property, the encoder must supply both a +name and a value. In cases of boolean properties TEI requires an explict true or false value attribute: + + + +

+

For convenience, we list here some of the normative character +properties and their values. For full information, refer to chapter 4 of The Unicode Standard, or the online documentation of the Unicode Character Database. + + The general + category (described in the Unicode Standard chapter 4 section 5) is an assignment to some + major classes and subclasses of characters. Suggested + values for this property are listed here: + +LuLetter, uppercase +LlLetter, lowercase +LtLetter, titlecase +Lm Letter, modifier +LoLetter, other +MnMark, nonspacing +McMark, spacing combining +MeMark, enclosing +NdNumber, decimal digit +NlNumber, letter +NoNumber, other +PcPunctuation, connector +PdPunctuation, dash +PsPunctuation, open +PePunctuation, close +PiPunctuation, initial quote +PfPunctuation, final quote +PoPunctuation, other +SmSymbol, math +ScSymbol, currency +SkSymbol, modifier +SoSymbol, other +ZsSeparator, space +ZlSeparator, line +ZpSeparator, paragraph +CcOther, control +CfOther, format +CsOther, surrogate +CoOther, private use +CnOther, not assigned +
+ + +This property applies to all Unicode characters. It governs the +application of the algorithm for bi-directional behaviour, as further +specified in Unicode Annex 9, The Bidirectional +Algorithm. The following 21 different values are currently +defined for this property: + +LLeft-to-Right +RRight-to-Left +ALRight-to-Left Arabic +ENEuropean Number +ESEuropean Number Separator +ETEuropean Number Terminator +ANArabic Number +CSCommon Number Separator +NSMNonspacing Mark +BNBoundary Neutral +BParagraph Separator +SSegment Separator +WSWhitespace +ONOther Neutrals +LRELeft-to-Right Embedding +LROLeft-to-Right Override +RLERight-to-Left Embedding +RLORight-to-Left Override +PDFPop Directional Format +LRILeft-to-Right Isolate +RLIRight-to-Left Isolate +FSIFirst Strong Isolate +PDIPop Directional Isolate +
 + This + property exists for characters that are not used + independently, but in combination with other characters, for + example the strokes making up CJK (Chinese, Japanese, and Korean) characters. It + records a class for these characters, which is used to + determine how they interact typographically. The following + values are defined in the Unicode Standard: (see Unicode +Character Database: Canonical Combining Class Values); these were taken from version 12.1: + +0Spacing, split, enclosing, reordrant, and Tibetan subjoined +1Overlays and interior +7Nuktas +8Hiragana/Katakana voicing marks +9Viramas +10Start of fixed position classes +199End of fixed position classes +200Below left attached +202Below attached +204Below right attached +208Left attached (reordrant around single base character) +210Right attached +212Above left attached +214Above attached +216Above right attached +218Below left +220Below +222Below right +224Left (reordrant around single base character) +226Right +228Above left +230Above +232Above right +233Double below +234Double above +240Below (iota subscript) +
 + + This property is defined for characters, + which may be decomposed, for example to a canonical form + plus a typographic variation of some kind. For such characters the Unicode standard specifies both + a decomposition type and a decomposition mapping + (i.e. another Unicode character to which this one may be + mapped in the way specified by the decomposition type). The + following types of mapping are defined in the Unicode Standard: + +fontA font variant (e.g. a blackletter form) +noBreakA no-break version of a space or hyphen +initialAn initial presentation form (Arabic) +medialA medial presentation form (Arabic) +finalA final presentation form (Arabic) +isolatedAn isolated presentation form (Arabic) +circleAn encircled form +superA superscript form +subA subscript form +verticalA vertical layout presentation form +wideA wide (or zenkaku) compatibility character +narrowA narrow (or hankaku) compatibility character +smallA small variant form (CNS compatibility) +squareA CJK squared font variant +fractionA vulgar fraction form +compatOtherwise-unspecified compatibility character +
+ + This property applies for + any character which expresses any kind of numeric value. Its + value is the intended value in decimal notation. + The mirrored + character property is used to properly render characters such + as U+0028, OPENING PARENTHESIS independent of + the text direction: it has the value Y +(character is mirrored) or N (code is not mirrored). +

+

The Unicode Standard also defines a set of informative (but non-normative) properties for Unicode characters. If encoders wish to provide such properties, they should be included using the Unicode name. If a Unicode name exists for a given character this should always be used, however encoders may also supply locally defined names. To tag a Unicode name, use unicodeProp name="Name" (or unihanProp name="Name"). For names specified elsewhere or specified locally use localProp.

+
+
+
+Annotating Characters +

Annotation of a character becomes necessary when it is desired +to distinguish it on the basis of certain aspects (typically, its +graphical appearance) only. In a manuscript, for example, where +distinctly different forms of the letter r can be recognized, it +might be useful to distinguish them for analytic purposes, quite +distinct from the need to provide an accurate representation of the +page. A digital facsimile, particularly one linked to a +transcribed and encoded version of the text, will always provide a +superior visual representation (for information on how to link a +digital facsimile to a transcribed text see ), but cannot be used to support arguments based +on the distribution of such different forms. Character annotation +as described here provides a solution to this problem. It should be kept in mind that any kind of text +encoding is an abstraction and an interpretation of the text at +hand, which will not necessarily be useful in reproducing an exact +facsimile of the appearance of a manuscript.

+ +

Assuming that we wish to distinguish the variant glyphs from the +standard representation for the character concerned, we will need to +define distinct glyph elements, one for each of the forms of +the letter we wish to distinguish: + + + +

+ + + + +
+ + + With these definitions in place, occurrences of these two special + rs in the text can be represented using the element g: + +

Words in this + manuscript are sometimes + written in a funny way.

+

+ As can be seen in this example, the glyph element pointed + to from the g element will be interpreted as an + annotation on the content of the element g. This mechanism + can be used to represent common manuscript abbreviations or ligatures, as in the + following examples: +

... Filthy riches...

+ + + +
+ + +

... per ardua

+ + + +
+ + + +(In fact the Unicode Standard does provide a character to represent the + Fi ligature; the encoder may however prefer not to + use it in order to simplify other text processing operations, + such as indexing).

+

With this + markup in place, it will be possible to write programs to analyze + the distribution of the different letters r as well as produce + more faithful renderings of the original. It + will also be possible to produce normalized versions by simply ignoring + the annotation pointed to by the element g. +

+

For brevity of encoding, it may be preferred to predefine +internal entities such as the following: + r' > +r' >]]> +which would enable the same material to be encoded as follows: + Wo&r1;ds in this manusc&r2;ipt are + sometimes written in a funny way.

]]> +

+

The same technique may be used to represent particular +abbreviation marks as well as to represent other characters or +glyphs. For example, if we believe that the r-with-one-funny-stroke is +being used as an abbreviation for receipt, this might be +represented as follows:&r1;]]>

+

Note however that this technique employs markup objects to +provide a link between a character in the document and some +annotation on that character. Therefore, it cannot be used in +places where such markup constructs are not allowed, notably in +attribute values. +

+ +

Since the need to use these constructs to annotate or define +characters occurs frequently in Chinese, Korean, and Japanese +documents, here are some issues that are specific to these +documents. There are two slightly different versions of the +problem. In the first case, due to the way Unicode is defined, +there are occasions when more than one glyph is defined for a +character. In such an occasion, one might want to retain the +character as used, but add information in a way so that a +normalizer (for search or indexing operations) could take +advantage of this information. To achieve this, we simply define +within a charDecl element a glyph that has two +mapping elements, as shown here: + + + + 說 + 説 + + + +The first of these mappings, of type Unicode, +simply maps our glyph to the code point where Unicode defined it. +The other one, of type standard, encodes the fact that +in our view, this glyph is a variation of the standard character +given in the content of the element. We could then use this +glyph element's unique identifier u8aaa to +refer to it from within a text as follows. + + 說 + +

+

A slightly different, but related problem occurs when we have +multiple variants, none of which has been defined in Unicode. In +this case, we need to define one as a new character using +char, and the others as glyphs using glyph. + + + + + + + + + + + +The char defines a new character, while the +glyph element then defines a variant glyph of this newly +defined character. Additional properties should be specified in +order to make these both identifiable.

+
+ +
+Adding New Characters +

The creation of additional characters for use in text encoding +is quite similar to the annotation of existing characters. The +same element g is used to provide a link from the +character instance in the text to a character definition provided +within the charDecl element. This character definition +takes the form of a char element. The element g +itself will usually be empty, but could contain a code point from +the Private Use Area (PUA) of the Unicode Standard, which is an +area set aside for the very purpose of privately adding new +characters to a document. Recommendations on how to use such PUA +characters are given in the following section.

+

In some circumstances, it may be desirable to provide a single +precomposed form of a character that is encoded in Unicode only as a +sequence of code points. For example, in Medieval +Nordic material, a character looking like a lowercase letter Y with a +dot and an acute-accent above it may be encountered so frequently that +the encoder wishes to treat it as a single precomposed character with +one single coded value. In the +transcription concerned, the encoder enters this letter as +&ydotacute;, which when the +transcription is processed can then be expanded in one of three ways, +depending on the mapping in force. The entity reference might be +translated into the sequence of corresponding Unicode code points +or into some locally-defined PUA character +(say &#xE0A4;) for local +processing only. Both these options have disadvantages; the former +loses the fact that the sequence of composed characters is regarded as +a single object; the second is not reliably portable. +Therefore, the recommended +representation is to use the g element defined by +the module defined in this chapter: . This makes it possible for the encoder to +provide useful documentation for the particular character or glyph so referenced: + + + + &#x0079;&#x0307;&#x0301; + U+E0A4 This + definition specifies the mapping between this composed character + and the individual Unicode-defined code points which make it + up. It also supplies a single locally-defined property + (entity) for the character concerned, the + purpose of which is to supply a recommended character entity name + for the character. +

+

The composition rules for ideographic characters typically require more complex rules than the &ydotacute; above. For these cases Unicode provides dedicated symbols to capture the composition in Ideographic Description Sequences (IDS). Encoders are strongly encouraged to provide IDS for each variant ideograph in the header component of the gaiji module to faciliated greater human and machine readability of rare or unencoded characters, as in the following example: + + + + ⿻人為 + 偽 + + +The composition rules and further examples appear in Chapter 18.2: Ideographic Description Characters of the Unicode Standard. Editors should be aware that different sequences can accurately describe the same character. In the example, the character "人" (U+4EBA) could have been substituted with "亻" (U+4EBB). Local preferences about how sequences are constructed should be documented in the encodingDesc of the corresponding TEI header (see ). Additionally, a number of online services, such as CHISE, offer querying and retrieving characters via IDS, which facilitates a greater degree of stability across different applications.

+

Under certain circumstances, Chinese Han characters can be written +within a circle. Rather than considering this as simply an aspect of the rendering, an encoder may wish to treat such circled characters as entirely distinct derived characters. For a given character +(say that represented by the numeric-character reference &#x4EBA;) +the circled variant might conveniently be represented as + , which references a +definition such as the following: + + + + + + &#x4EBA; + + + &#xE000; + +

+

In this example, the circled ideograph +character has been defined with two mappings, and with two +properties. The two properties are the Unicode-defined +character-decomposition which specifies that this is a circled +character, using the appropriate terminology (see above) and a locally defined property known as +daikanwa. The two mappings indicate firstly that the standard form of this character is the character &#x4EBA;, and secondly that the character used to represent this character locally is the PUA character &#xE000;. For convenience of local processing this PUA character may in fact appear as content of the g element. In general, however, the g element +will be empty.

+
+
+How to Use Code Points from the Private Use Area +

The developers of the Unicode Standard have set aside an +area of the codespace for the private use of software vendors, +user groups, or individuals. As of this writing (Unicode 12.1), +there are around 137,000 code points available in this area, which +should be enough for most needs. No code point assignments will be made +to this area by standard bodies and only some very basic default +properties have been assigned (which may be overridden where +necessary by the mechanism outlined in this chapter). Therefore, +unlike all other code points defined by the Unicode Standard, PUA code points should +not be used directly in documents intended for blind interchange. +

+

In the two previous examples, we mentioned that the variant +characters concerned might well be assigned specific code points from +the PUA. This might, for example, facilitate the use of a particular +font which displays the desired character at this code point in the +local processing environment. Since however this assignment would be +valid only on the local site, documents containing such code points are +unsuitable for blind interchange. During the process of preparing +such documents for interchange, any PUA code points should be replaced by an appropriate use of the g element, such as g ref="#xxxx", thus associating the character required +with the documentation of it provided by the referenced char element. The PUA character +used during the preparation of the document might be recorded in the +char element, as shown in the example in , or retained as content of the g element. However, since there is no requirement that the same PUA +character be used to represent it at the receiving site, and since it +may well be the case that this other site has already made an +assignment of some other character to the original PUA code point, it is best practice to remove the locally-defined PUA character. It is to be expected that a further translation into the +local processing environment at the receiving site will be necessary +to handle such characters, during which variant letters can be +converted to hitherto unused code points on the basis of the +information provided in the char element.

+

This mechanism is rather weak in cases where DOM trees or +parsed XML fragments are exchanged, which may increasingly be the +case. The best an application can do here is to treat any +occurrence of a PUA character only in the context of the local +document and use the properties provided through the char +element as a handle to the character in other contexts.

+

In the fullness of time, a character may become standardized, and +thus assigned a specific code point outside the PUA. Documents which +have been encoded using the mechanism must at the least ensure that +this changed code point is recorded within the relevant char +element; it will however normally be simpler to remove the +char element and replace all occurrences of g +elements which reference it by occurrences of the newly coded +character.

+
+ + +
+ + Writing Modes + +

The scripts used for writing human languages vary not only in the +glyphs they use, but also in the way (or ways) that those glyphs are +arranged on the writing surface. For the majority of modern languages, +writing is arranged as a series of lines which are to be read from top +to bottom. Within each line, individual characters are frequently +presented from left to right (English, Russian, Greek), but there are +also several widely-used scripts which run right-to-left (Arabic, +Hebrew). Writing in which the lines of glyphs are presented vertically +and read from right to left is also often encountered, notably in +East Asian scripts (Sinitic characters, Japanese Kana, Korean +Hangul, Vietnamese chữ nôm). In many cases, a language normally uses +the same writing mode (we use this term to +refer to the orientation of individual glyphs within a line and the +order in which glyphs and lines should be read), but there are exceptions in which +the same language may appear in different modes, for example either +vertically or horizontally. Many East Asian scripts were traditionally +written from top to bottom within the line, with their lines sequenced +from right to left. Although modern Japanese, Chinese, and Korean are +often written horizontally, the traditional vertical writing mode is +still widely used. There are also comparatively rare cases of ancient +scripts written with lines running left to right, each line being read +top to bottom (Ancient Uighur, classical Mongolian and Manchu), or +scripts such as Ogham where the writing direction may start from the +bottom left and run around the edge of an inscribed object.

+ +

When different languages are combined, it is possible that +different writing modes will be needed: for example, in Hebrew text, +running right to left, sequences of Latin digits still run left to +right. When different writing modes are available for the same +language, it may be that different glyphs will be preferred when the +script is used in different modes. For example, when Japanese is +written horizontally, the Unicode character U+3001, the +ideographic comma, is used in preference to +Unicode character U+FE11, the vertical mode comma. This ensures that +the comma appears in the correct position relative to the surrounding +glyphs. Even for scripts which are usually written in exactly the same +way, different writing modes may be encountered in particular +contexts; for example when a language using Roman script is embedded +within vertically-organized Chinese text, it may sometimes be +displayed vertically and sometimes horizontally. The writing mode may +also vary in response to layout constraints such as those imposed by a +complex table, where column or row labels may be written vertically or +diagonally to make the most effective use of available space, just as +it may vary in response to the size and shape of the carrier in the +case of a monumental inscription.

+ +

For many, perhaps most, TEI documents there may be no need to +encode the writing mode explicitly, even in so-called "mixed mode" +texts containing passages written in languages which use different +writing modes. Modern printed texts in most European languages, for +instance, may be expected to use left-to-right/top-to-bottom +directionality; while Arabic or Hebrew texts are expected to run +right-to-left/top-to-bottom. In a TEI document, language and script +are explicitly stated in the markup using the attribute +xml:lang; this indication will usually imply a particular +default writing mode. Even where this attribute is not used, passages +in different scripts will use different Unicode characters, and will +thus imply a particular default writing mode.

+ +

Consider the case of an English text containing a few Arabic words: + The Arabic term قلم رصاص means "pencil". +A correct TEI encoding might read as follows: + + The Arabic term + قلم رصاص means "pencil". + +We might assume that it is the presence of the xml:lang +attribute with value ar that causes processing software to +display the Arabic from right to left, but in fact, this is not the +case. The order in which the Arabic characters appear when rendered +would be the same, even if the markup were not present: + + The Arabic term قلم رصاص means "pencil". + +This is because Arabic glyphs are always displayed right to left, +even when they appear within a left-to-right English sentence. Like +most other codepoints in the Unicode standard, they have a specific +directionality setting which helps any rendering software determine +how they should be ordered. The Latin glyph "a" has a strong +left-to-right bidirectionality setting, as do the digits 0 to 9; the +Hebrew א (alef) is strongly right-to-left. Of course, some glyphs +(common punctuation marks such as the period or comma for example) +have weak or neutral settings because they may appear in several +contexts.

+ +

The Unicode Bidirectional Algorithm (Unicode +Consortium, 2017) + defines a number of +rules enabling software to render sequences of characters which have +differing directionality properties in a predictable and reliable way, +using only those properties. Because this +algorithm may not always give the desired result, Unicode also +provides a set of "directional formatting characters" (). These +additional codepoints can be used to signal to rendering software that +a specific directionality setting should be turned on or off. However, +in the case of documents encoded in XML, there is generally no need to use such +characters, and the W3C advises against it unless markup is unavailable. (). It +should be remembered however that individual sequences of characters +are always stored in a file in the order in which they should be read, +irrespective of the order in which the characters making up a sequence +should be displayed or rendered. For example, in a RTL language such +as Hebrew, the first character in a file will be that which is +displayed at the rightmost end of the first line of text.

+ +

An encoder wishing to document or to control the order in which +sequences of characters in a TEI document are displayed will usually +do so by segmenting the text into sequences presented in the desired +order and specifying an appropriate language code for each. In +situations where this approach may result in ambiguity or lack of +precision, or if the encoder wishes to record directional information +explicitly in their encoding, we recommend using the global @style +attribute to supply detail about the writing mode applicable to the +content of any element. The style attribute (discussed in +) permits use of any formatting language; for +these purposes however, we recommend use of CSS, which includes a +Writing Modes module At the time of writing, this +W3C module has the status of a candidate recommendation: see further + + which permits direct specification of a number of useful properties +associated with writing modes, notably direction (ltr +or rtl); writing-mode +(horizontal-tb, vertical-rl, or vertical-lr); +and text-orientation (mixed, upright, +sideways ...) + +as well as properties affecting the behaviour of the unicode-bidi (bidirectional) algorithm. +We discuss and exemplify how these properties may be used below.

+ +

The global TEI style attribute applies to the element on +which it is specified (and in most cases, its descendants). Rather +than specify it on every element, it will often be more efficient to +express sets of commonly-used styling rules as rendition +elements in the teiHeader and then point to them using the +global rendition attribute, as further discussed in . Although the CSS specifications are mainly used to +provide instructions for software when rendering a digital text, they +also provide a useful means of describing the visual properties of a +pre-existing document in a formal and standardized way.

+ +

The next section presents some examples of how CSS can be used to +describe a variety of writing modes. A full description of the appearance +of a document will probably include many other properties of course.

+
+ +
+ Examples of Different Writing Modes +

The CSS recommendations provides several properties which can be used to encode aspects of the "writing mode". The most useful of these is the property "writing-mode" which may be used to specify a reading-order for both characters within a single line and lines within a single block of text. The property "text-orientation" may also used to indicate the orientation of individual characters with respect to the line, and the property "direction" to determine the reading order of characters within a line only. We give some examples of each below.

+
+ Vertical Writing Modes +

The writing-mode property is particularly useful for languages + which can be written in different writing modes, such as Chinese + and Japanese. Its possible values include horizontal-tb, + vertical-rl and vertical-lr. Each value has + two components: horizontal or vertical specifies the inline + writing direction, while the second component specifies the + direction in which lines in a block, and blocks in a sequence are + arranged: from top to bottom (as in most European languages, in + which lines and paragraphs are arranged from top to bottom on a + page), from right to left (as in the case of Japanese written vertically), or + left-to-right (as in the case of Mongolian).

+

The following example shows three versions of the same poem: first in + Japanese, written top to bottom; next in romaji (Japanese in + Latin script); and finally in an English translation.

+

+

+ + Taken from p.42 of Haiku: Japanese Art and Poetry. Judith Patt, Michiko Warkentyne (calligraphy) and Barry Till. 2010. +
+

+

+

We might encode this as follows:

+
+ + 古池や + 蛙 + 飛び込む + 水の音 + + + furu ike ya + kawazu tobikomu + mizu no oto + + + Old pond, + and a frog dives in— + "Splash"! + +
 +

For the sake of simplicity, we have not attempted to capture in + this encoding such aspects as the indenting of lines in the first + Japanese version, or the central alignment of the other two + versions, nor any other renditional features such as font weight or + size etc. The Japanese transcription has writing-mode: + vertical-rl, which is required because Japanese may be + written either in this mode or horizontally. The transcription in + romaji uses the attribute xml:lang to supply a value of + ja-Latn, indicating Japanese written in Latin + script. Its style attribute specifies a horizontal + writing mode; this may seem superfluous, but vertically-written + romaji is not unknown.

+
+
+ Vertical Text with Embedded Horizontal Text + +

When Japanese is written vertically, the glyph orientation + remains the same as when it is written horizontally. In other + words, glyphs are not rotated (although as noted above some + different glyphs may be used for some characters, in particular for + punctuation which needs to be positioned differently in vertical + and in horizontal text). However, it is very common for languages + written vertically to have embedded runs of text from languages + which are normally written horizontally. This raises the issue of + the orientation of the glyphs from the horizontal language. Are + they written upright, as they would normally appear in horizontal + text runs, or are they rotated? Consider this fragment from a + Japanese article about the Indonesian language, which takes the + form of a glossary list:

+

+

+ +Detail from p.62 of インドネシア語". 崎山理. 1985. 外国語との対照 II. 講座日本語学 11. +
+

+ +

The text-orientation property allows us to indicate whether or + not glyphs are rotated. In the following example, we have indicated + that the list uses a vertical-rl writing mode, but that the orientation + of individual glyphs may vary:

+ + + + 「近い、ほとんど」 + + 「新しい、ばかい」 + + +

The rule text-orientation: mixed specifies that + characters from horizontal-only scripts are set sideways, + i.e. 90° clockwise from their standard orientation in horizontal + text. Characters from vertical scripts are set with their intrinsic + orientation (fantasai + 2014). Since the default value for + text-orientation is mixed, this rule is + not strictly required. However, if the Indonesian glyphs (which are + roman characters) had been set vertically, like this:

+

+

+ + Fragment of previous image with Indonesian glyphs upright. +
+

+

then an encoding like the following could be used to make this explicit:

+ + + + 「近い、ほとんど」 + + 「新しい、ばかい」 + + + +

The rule text-orientation: upright specifies that + characters from horizontal-only scripts are rendered + upright, i.e. in their standard horizontal orientation. Characters + from vertical scripts are set with their intrinsic orientation and + shaped normally (fantasai + 2014).

+
+
+ Vertical Orientation in Horizontal Scripts +

It is not unusual to see text from horizontal languages + written vertically even where no vertically-written script is + involved. This example is a fragment from a table of information + about agricultural development on Vancouver Island, written in + 1855:

+

+

+ + Enclosure with Despatch to London 10048, CO + 305/6, p. 131v from +
+

+

Four of the subheading cells in this fragment contain English text written vertically, + bottom-to-top, to conserve space on the page. To describe this sort of phenomenon, + we can use the text-orientation property again:

+ +

text-orientation: mixed | upright | sideways-right | sideways-left | sideways | use-glyph-orientation

+ +

For full details on this property, we refer the reader to the CSS Writing Modes specification. + For the present example, we will make use only of the sideways-left value, + which causes text to be set as if in a horizontal layout, but rotated 90° counter-clockwise. + We might encode the third of the four cells containing vertical text like this:

+ + + Cash Value + of + Farms + + +

The writing-mode property captures the fact that the script is written vertically, and + its lines are to be read from left to right (so the line containing of + is to the right of that containing Cash value), while the text-orientation + value encodes the orientation (rotated 90° counter-clockwise). We might also add + text-align: center to the style, to express the fact that the text is centrally-aligned.

+
+
+ Bottom-to-top Writing +

Of the rather small number of scripts which appear to be written + bottom-to-top, perhaps the best-known is Ogham, an alphabet used + mainly to write Archaic Irish. Ogham is typically found inscribed + along the edge of a standing stone, starting at its base. The CSS Writing + Modes specification does not explicitly distinguish between + vertical scripts which are written top-to-bottom and those which + are written bottom-to-top. Instead, such bottom-to-top scripts are best treated + as left-to-right horizontal scripts, oriented vertically because of + the constraints of the medium on which they are inscribed. Such + scripts are analogous to the vertical English text-runs in the + table cells in the example above, and can be handled in exactly the + same manner (writing-mode: vertical-lr; text-orientation: + sideways-left). In cases where writing follows a curved path + (such as Ogham running around the edge of a stone), a meticulous + encoder might resort to the use of SVG to describe the path, rather + than treating the phenomenon as a writing mode.

+
+
+ Mixed Horizontal Directionality + +

Returning to our previous simple example

+ The Arabic term قلم رصاص means "pencil". +

we could use the direction property to make directionality explicit:

+

direction: ltr | rtl

+ + The Arabic term + قلم رصاص means "pencil". + +

The use of the direction property to record the observed directionality + of the text is unambiguous, even though it is (as we noted above) superfluous. + The use of the unicode-bidi property here may require some explanation. + By default this property has the value normal, the effect of which in this + context would be to ignore any value supplied for the direction property. The CSS Writing + Modes specification stipulates that the direction property has no effect on bidi + reordering when specified on inline boxes whose unicode-bidi property’s + value is normal, because the element does not open an additional + level of embedding with respect to the bidirectional algorithm. +

+ +

Mixed horizontal directionality is very common in languages such as Arabic + and Hebrew, particularly when numbers (which are always given LTR) + or phrases from LTR languages are embedded. It is not + impossible, though quite unusual, for ambiguities +to arise in such situations, which may give rise to the +parts of a document being displayed in unexpected ways that do +not correspond to the natural reading order. A more detailed + discussion of this issue from an HTML perspective is provided by a + W3C Internationalization Working Group report Inline + markup and bidirectional text in HTML.

+ + + + + +
+
+ + Summary +

For most texts, information about text directionality need not be explicitly + encoded in a TEI text, either because it follows unambiguously from + xml:lang values, or because it can be expected to be handled + unequivocally by the Unicode Bidi Algorithm. Where it is considered important + to encode such information, properties and values taken from the CSS Writing + Modes module may be used by means of the global TEI style attribute + (or using the TEI rendition element, linked with the rendition + attribute). Most phenomena can be well described in this way; of those which + cannot, other approaches based on the CSS Transforms module are presented + in the next section.

+
+
+
+ + Text Rotation +

In what follows, we examine a range of textual phenomena which + in some ways appear very similar to those examined above, and even + overlap with them. We can categorize these as text transformation + features, and suggest some strategies for encoding them based on + the properties detailed in the CSS Transforms (Fraser et al 2013) specification. + This CSS module provides a complex array of properties, values and + functions which can be used to rotate, skew, translate and otherwise + transform textual and graphical objects. We can borrow this vocabulary + in order to describe textual phenomena in a precise manner.

+ +

We begin with a simple example of a rotational transform:

+

+

+ +
+

+

Here a block of text has been rotated around its z-axis. This is clearly + not a writing mode; the writing mode for this text + is horizontal, left to right. Furthermore, even if we wished to treat this + as a writing mode, we could not do so, because there is no way to use + writing modes properties to describe an text orientation which is angled + at 45 degrees; no human languages are consistently written in this + orientation. It is more appropriate to treat this as a rotational transformation. + We can do this using two properties: transform and + transform-origin. (Both of these properties have quite complex + value sets, and we will not look at all of them here. See the + specification for full details.)

+ +

The transform property takes as its value one or more of the transform functions, + one of which is the function rotateZ():

+ + TEI-C.ORG + +

Any rotation must take place clockwise around an axis positioned relative + to the element being rotated, and the transform-origin property + can be used to specify the pivot point. By default, the value of transform-origin + is 50% 50%, the point at the centre of the element, but these + values can be changed to reflect rotation around a different origin point. + (The TEI zone element also bears an attribute rotate which can + specify rotation in degrees around the z-axis, but it is not available for any other + element.)

+ +

A block of text may also be rotated about either of its other axes. For example, + this shows rotation around the Y (vertical) axis:

+

+

+ +
+

+ TEI-C.ORG + +

These are obviously trivial examples, but similar features do appear in historical texts. + George Herbert's The Temple includes two stanzas headed + Easter Wings which are both normally printed in a rotated form + so that they represent a pair of wings:

+

+

+ + Page 35 of George Herbert's The Temple + (1633), from a copy in the Folger Library. +
+

+ +

This could be encoded thus:

+ + + My tender age in ſorrow did beginne: + And ſtill with ſickneſſes and ſhame + + +

We might also argue that this is in fact a vertical writing + mode by supplying writing-mode: vertical-rl; + text-orientation: sideways-right as the value for the + style attribute in the preceding example.

+ +

Rotation is also useful as a method of handling a true writing + mode which is not covered by the CSS Writing Modes: + boustrophedon. This is a writing mode common in + inscriptions in Latin, Greek and other languages, in which + alternate lines run from left to right and from right to leftThe name is taken from the Greek βουστροφηδόν, meaning + ox-turning from βοῦς (an ox) and στροφή (turn); that is, + turning as an ox does when pulling a plough.. Right-to-left + lines in boustrophedon have another unexpected feature: their + glyphs are reversed, so that these lines appear as mirror + writing, as in the following ancient Greek inscription: +

+ +Leaden plaque bearing an inquiry by Hermon from the oracular +precinct at Dodona. (L.H. Jeffery Archive) +
+

+

This might be transcribed as follows (ignoring word boundaries for the moment):

+ + ΗΕΡΜΟΝΤΙΝA + ΚΑΘΕΟΝΠΟΤΘΕΜ + ΕΝΟΣΥΕΝΕΑϜ + ΟΙΥΕΝΟΙΤΙΕΚΚ + ΡΕΤΑΙΑΣΟΝΑ + ΣΙΜΟΣΟΤΤΑΙΕ + ΑΣΣΑΙ + +

The 180-degree rotation around the Y (vertical) axis here + describes what is happening in the RTL line in boustrophedon; the order of glyphs + is reversed, and so is their individual orientation (in fact, we see them + from the back, as it were). seg elements + have been used here because these are clearly not lines + in the sense of poetic lines; the text is continuous prose, and linebreaks + are incidental.

+ +

There are obviously some unsatisfactory aspects of this manner of encoding + boustrophedon. In the inscription above, some words run across linebreaks, + so if we wished to tag both words and the right-to-left phenomena, one + hierarchy would have to be privileged over the other. By using a transform + function rather than a writing mode property, we are apparently suggesting + that boustrophedon is not in fact a writing mode, whereas it clearly is. But + the CSS Writing Modes specification does not provide support for boustrophedon, + because it is a rather obscure historical phenomenon; using a rotational transform + is one practical alternative.

+ +
+
+ Caveat + +

As with other parts of the CSS specification, the intended + effect of CSS Transforms properties and values is defined with + reference to a specific Visual formatting + model; the language is designed to describe how an HTML + document should be formatted. This is not, of course, the case for + the TEI, which lacks any explicit processing or formatting model, + and attempts to define objects as far as possible without + consideration of their visual appearance. As long as the properties + and values from the CSS Transforms module are used as a convenient, + well-specified descriptive language to capture features of a text, + without any expectation of using them directly and reliably for + rendering, this is not particularly problematic. CSS provides a + useful and well-defined vocabulary to describe many aspects of the + appearance of source texts, benefitting particularly from the + clarity of definition provided by the specification. However, if + there is any expectation of using this information to render a text + in a predictable and accurate way, it will be essential to provide + enough styling information throughout the document hierarchy to + resolve all ambiguities with regard to size, positioning, block + status, etc. before any element undergoes a transform + operation.

+
+ + +
Formal Definition +

The gaiji module described in this chapter makes available the following +components: + + Character and Glyph Documentation + Character and glyph documentation + Représentation des caractères et des glyphes non standard + 文字與字體說明 + Documentazione di caratteri non standard e glifi + Documentação dos carateres + 外字モジュール + + +The selection and combination of modules to form a TEI schema is described in +. +

+ + + + + + + + + + + + +
+
diff --git a/P5/Source/Specs/TEI.xml b/P5/Source/Specs/TEI.xml index 8f058f55d7..f9e779ce03 100644 --- a/P5/Source/Specs/TEI.xml +++ b/P5/Source/Specs/TEI.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/ab.xml b/P5/Source/Specs/ab.xml index 94036c4042..8718461882 100644 --- a/P5/Source/Specs/ab.xml +++ b/P5/Source/Specs/ab.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/abbr.xml b/P5/Source/Specs/abbr.xml index 4c66655d09..e6cd6f0f6e 100644 --- a/P5/Source/Specs/abbr.xml +++ b/P5/Source/Specs/abbr.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/abstract.xml b/P5/Source/Specs/abstract.xml index aed6ce706f..fc53a09f63 100644 --- a/P5/Source/Specs/abstract.xml +++ b/P5/Source/Specs/abstract.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/accMat.xml b/P5/Source/Specs/accMat.xml index e7b7d75de0..10aa249263 100644 --- a/P5/Source/Specs/accMat.xml +++ b/P5/Source/Specs/accMat.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/actor.xml b/P5/Source/Specs/actor.xml index de765a29a4..3c2e9db59a 100644 --- a/P5/Source/Specs/actor.xml +++ b/P5/Source/Specs/actor.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/add.xml b/P5/Source/Specs/add.xml index f65ba3530b..8f55105eed 100644 --- a/P5/Source/Specs/add.xml +++ b/P5/Source/Specs/add.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/addName.xml b/P5/Source/Specs/addName.xml index 736b0b7967..ec28e8c578 100644 --- a/P5/Source/Specs/addName.xml +++ b/P5/Source/Specs/addName.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/addSpan.xml b/P5/Source/Specs/addSpan.xml index acaeea22c4..ffbfc6622a 100644 --- a/P5/Source/Specs/addSpan.xml +++ b/P5/Source/Specs/addSpan.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/additional.xml b/P5/Source/Specs/additional.xml index bc044829e4..aefeac5d47 100644 --- a/P5/Source/Specs/additional.xml +++ b/P5/Source/Specs/additional.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/additions.xml b/P5/Source/Specs/additions.xml index 1eed0204c2..072f726d3c 100644 --- a/P5/Source/Specs/additions.xml +++ b/P5/Source/Specs/additions.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/addrLine.xml b/P5/Source/Specs/addrLine.xml index 3c6dacb5d5..0a3a27ba6d 100644 --- a/P5/Source/Specs/addrLine.xml +++ b/P5/Source/Specs/addrLine.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/address.xml b/P5/Source/Specs/address.xml index e9905c503b..3fc9b7f3f7 100644 --- a/P5/Source/Specs/address.xml +++ b/P5/Source/Specs/address.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/adminInfo.xml b/P5/Source/Specs/adminInfo.xml index dcf9e77604..187093982e 100644 --- a/P5/Source/Specs/adminInfo.xml +++ b/P5/Source/Specs/adminInfo.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/alt.xml b/P5/Source/Specs/alt.xml index 04693d7422..02ba2c3b87 100644 --- a/P5/Source/Specs/alt.xml +++ b/P5/Source/Specs/alt.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/altGrp.xml b/P5/Source/Specs/altGrp.xml index aa13ad11a0..df42c046d2 100644 --- a/P5/Source/Specs/altGrp.xml +++ b/P5/Source/Specs/altGrp.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/altIdent.xml b/P5/Source/Specs/altIdent.xml index 5396cfb634..1e4f07e909 100644 --- a/P5/Source/Specs/altIdent.xml +++ b/P5/Source/Specs/altIdent.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/alternate.xml b/P5/Source/Specs/alternate.xml index 74b743d2bf..d9f194a44e 100644 --- a/P5/Source/Specs/alternate.xml +++ b/P5/Source/Specs/alternate.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/am.xml b/P5/Source/Specs/am.xml index cb310b015f..89487bf824 100644 --- a/P5/Source/Specs/am.xml +++ b/P5/Source/Specs/am.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/analytic.xml b/P5/Source/Specs/analytic.xml index d16227469d..3ac57fee55 100644 --- a/P5/Source/Specs/analytic.xml +++ b/P5/Source/Specs/analytic.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/anchor.xml b/P5/Source/Specs/anchor.xml index 3716cd863e..bd66b33b79 100644 --- a/P5/Source/Specs/anchor.xml +++ b/P5/Source/Specs/anchor.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/annotation.xml b/P5/Source/Specs/annotation.xml index cf50df7357..4d0191b677 100644 --- a/P5/Source/Specs/annotation.xml +++ b/P5/Source/Specs/annotation.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/anyElement.xml b/P5/Source/Specs/anyElement.xml index 1623b944db..0a6034270d 100644 --- a/P5/Source/Specs/anyElement.xml +++ b/P5/Source/Specs/anyElement.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/app.xml b/P5/Source/Specs/app.xml index 6d860edfed..ee3da7cdfc 100644 --- a/P5/Source/Specs/app.xml +++ b/P5/Source/Specs/app.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/appInfo.xml b/P5/Source/Specs/appInfo.xml index 7f5136c182..45c7f9dbb8 100644 --- a/P5/Source/Specs/appInfo.xml +++ b/P5/Source/Specs/appInfo.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/arc.xml b/P5/Source/Specs/arc.xml index af9d075df2..c4e920af76 100644 --- a/P5/Source/Specs/arc.xml +++ b/P5/Source/Specs/arc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/argument.xml b/P5/Source/Specs/argument.xml index a7b3f4862c..13b4adb462 100644 --- a/P5/Source/Specs/argument.xml +++ b/P5/Source/Specs/argument.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.anchoring.xml b/P5/Source/Specs/att.anchoring.xml index 4dec26ca88..8841f61c63 100644 --- a/P5/Source/Specs/att.anchoring.xml +++ b/P5/Source/Specs/att.anchoring.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.ascribed.directed.xml b/P5/Source/Specs/att.ascribed.directed.xml index e622a8fae3..8eb1e80143 100644 --- a/P5/Source/Specs/att.ascribed.directed.xml +++ b/P5/Source/Specs/att.ascribed.directed.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.ascribed.xml b/P5/Source/Specs/att.ascribed.xml index 35aeb401fd..7aeb0f4421 100644 --- a/P5/Source/Specs/att.ascribed.xml +++ b/P5/Source/Specs/att.ascribed.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.breaking.xml b/P5/Source/Specs/att.breaking.xml index 75aa797a6f..1a92710321 100644 --- a/P5/Source/Specs/att.breaking.xml +++ b/P5/Source/Specs/att.breaking.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.cReferencing.xml b/P5/Source/Specs/att.cReferencing.xml index 4d93a69506..a450cd5516 100644 --- a/P5/Source/Specs/att.cReferencing.xml +++ b/P5/Source/Specs/att.cReferencing.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.calendarSystem.xml b/P5/Source/Specs/att.calendarSystem.xml index 735166ae98..abdfc796ea 100644 --- a/P5/Source/Specs/att.calendarSystem.xml +++ b/P5/Source/Specs/att.calendarSystem.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.canonical.xml b/P5/Source/Specs/att.canonical.xml index 79d247f589..cb1d8afe9b 100644 --- a/P5/Source/Specs/att.canonical.xml +++ b/P5/Source/Specs/att.canonical.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.citeStructurePart.xml b/P5/Source/Specs/att.citeStructurePart.xml index 6602536ce4..7c15aeabbe 100644 --- a/P5/Source/Specs/att.citeStructurePart.xml +++ b/P5/Source/Specs/att.citeStructurePart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.citing.xml b/P5/Source/Specs/att.citing.xml index b641d071b1..ee841a807b 100644 --- a/P5/Source/Specs/att.citing.xml +++ b/P5/Source/Specs/att.citing.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.combinable.xml b/P5/Source/Specs/att.combinable.xml index 25e6a4b9b7..5b05f5735b 100644 --- a/P5/Source/Specs/att.combinable.xml +++ b/P5/Source/Specs/att.combinable.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.coordinated.xml b/P5/Source/Specs/att.coordinated.xml index a6b3e5de71..aa9c818d63 100644 --- a/P5/Source/Specs/att.coordinated.xml +++ b/P5/Source/Specs/att.coordinated.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.damaged.xml b/P5/Source/Specs/att.damaged.xml index 9402e33774..ffbf926c28 100644 --- a/P5/Source/Specs/att.damaged.xml +++ b/P5/Source/Specs/att.damaged.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.datable.custom.xml b/P5/Source/Specs/att.datable.custom.xml index a0ef6b64e1..298ff2d19d 100644 --- a/P5/Source/Specs/att.datable.custom.xml +++ b/P5/Source/Specs/att.datable.custom.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.datable.iso.xml b/P5/Source/Specs/att.datable.iso.xml index 12b4dfdfcf..a222fbb8a3 100644 --- a/P5/Source/Specs/att.datable.iso.xml +++ b/P5/Source/Specs/att.datable.iso.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.datable.w3c.xml b/P5/Source/Specs/att.datable.w3c.xml index 4245b2c142..8563ab0a09 100644 --- a/P5/Source/Specs/att.datable.w3c.xml +++ b/P5/Source/Specs/att.datable.w3c.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.datable.xml b/P5/Source/Specs/att.datable.xml index 671fbc2406..cf817927a5 100644 --- a/P5/Source/Specs/att.datable.xml +++ b/P5/Source/Specs/att.datable.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.datcat.xml b/P5/Source/Specs/att.datcat.xml index 1081434b20..89f1611e30 100644 --- a/P5/Source/Specs/att.datcat.xml +++ b/P5/Source/Specs/att.datcat.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.declaring.xml b/P5/Source/Specs/att.declaring.xml index 300f0708fc..ffebd1514c 100644 --- a/P5/Source/Specs/att.declaring.xml +++ b/P5/Source/Specs/att.declaring.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.deprecated.xml b/P5/Source/Specs/att.deprecated.xml index 20253e6a30..2e39248858 100644 --- a/P5/Source/Specs/att.deprecated.xml +++ b/P5/Source/Specs/att.deprecated.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.dimensions.xml b/P5/Source/Specs/att.dimensions.xml index d6508d4a3e..2d79c3b0f9 100644 --- a/P5/Source/Specs/att.dimensions.xml +++ b/P5/Source/Specs/att.dimensions.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.divLike.xml b/P5/Source/Specs/att.divLike.xml index e265fe802a..25b4efbb9c 100644 --- a/P5/Source/Specs/att.divLike.xml +++ b/P5/Source/Specs/att.divLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.docStatus.xml b/P5/Source/Specs/att.docStatus.xml index 368efd4e62..47866c32af 100644 --- a/P5/Source/Specs/att.docStatus.xml +++ b/P5/Source/Specs/att.docStatus.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.duration.iso.xml b/P5/Source/Specs/att.duration.iso.xml index 16621af215..737d550651 100644 --- a/P5/Source/Specs/att.duration.iso.xml +++ b/P5/Source/Specs/att.duration.iso.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.duration.w3c.xml b/P5/Source/Specs/att.duration.w3c.xml index d4651a2362..9f0b36e673 100644 --- a/P5/Source/Specs/att.duration.w3c.xml +++ b/P5/Source/Specs/att.duration.w3c.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.duration.xml b/P5/Source/Specs/att.duration.xml index 6cc0e96f21..5cc32e857f 100644 --- a/P5/Source/Specs/att.duration.xml +++ b/P5/Source/Specs/att.duration.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.editLike.xml b/P5/Source/Specs/att.editLike.xml index 8640add267..49a594ecde 100644 --- a/P5/Source/Specs/att.editLike.xml +++ b/P5/Source/Specs/att.editLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.edition.xml b/P5/Source/Specs/att.edition.xml index 7b9d75a576..6b2d9f968f 100644 --- a/P5/Source/Specs/att.edition.xml +++ b/P5/Source/Specs/att.edition.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.enjamb.xml b/P5/Source/Specs/att.enjamb.xml index 18da1c2d3a..073c2b1104 100644 --- a/P5/Source/Specs/att.enjamb.xml +++ b/P5/Source/Specs/att.enjamb.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.entryLike.xml b/P5/Source/Specs/att.entryLike.xml index 2d7250e04d..4b11831056 100644 --- a/P5/Source/Specs/att.entryLike.xml +++ b/P5/Source/Specs/att.entryLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.formula.xml b/P5/Source/Specs/att.formula.xml index 1c586dfc1e..e3f8ba5cfb 100644 --- a/P5/Source/Specs/att.formula.xml +++ b/P5/Source/Specs/att.formula.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.fragmentable.xml b/P5/Source/Specs/att.fragmentable.xml index f7dc410d45..c9e3a9b4a9 100644 --- a/P5/Source/Specs/att.fragmentable.xml +++ b/P5/Source/Specs/att.fragmentable.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.gaijiProp.xml b/P5/Source/Specs/att.gaijiProp.xml index c4c2f03a60..bce2f4a029 100644 --- a/P5/Source/Specs/att.gaijiProp.xml +++ b/P5/Source/Specs/att.gaijiProp.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.global.analytic.xml b/P5/Source/Specs/att.global.analytic.xml index eb1687301f..2dd56940c4 100644 --- a/P5/Source/Specs/att.global.analytic.xml +++ b/P5/Source/Specs/att.global.analytic.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.global.change.xml b/P5/Source/Specs/att.global.change.xml index ef080b28b3..3b08692d6a 100644 --- a/P5/Source/Specs/att.global.change.xml +++ b/P5/Source/Specs/att.global.change.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.global.facs.xml b/P5/Source/Specs/att.global.facs.xml index 28007af28a..484fc218a3 100644 --- a/P5/Source/Specs/att.global.facs.xml +++ b/P5/Source/Specs/att.global.facs.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.global.linking.xml b/P5/Source/Specs/att.global.linking.xml index 5ad6efa452..4dbf7b053c 100644 --- a/P5/Source/Specs/att.global.linking.xml +++ b/P5/Source/Specs/att.global.linking.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.global.rendition.xml b/P5/Source/Specs/att.global.rendition.xml index 9980cede90..b28d1524be 100644 --- a/P5/Source/Specs/att.global.rendition.xml +++ b/P5/Source/Specs/att.global.rendition.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.global.responsibility.xml b/P5/Source/Specs/att.global.responsibility.xml index aefec8b5db..b3a09b3cc5 100644 --- a/P5/Source/Specs/att.global.responsibility.xml +++ b/P5/Source/Specs/att.global.responsibility.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.global.source.xml b/P5/Source/Specs/att.global.source.xml index 97371be41d..1ff09275c0 100644 --- a/P5/Source/Specs/att.global.source.xml +++ b/P5/Source/Specs/att.global.source.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.global.xml b/P5/Source/Specs/att.global.xml index f1d22e983b..f3d180c526 100644 --- a/P5/Source/Specs/att.global.xml +++ b/P5/Source/Specs/att.global.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.handFeatures.xml b/P5/Source/Specs/att.handFeatures.xml index e4ad0a6e81..c7a7c63184 100644 --- a/P5/Source/Specs/att.handFeatures.xml +++ b/P5/Source/Specs/att.handFeatures.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.identified.xml b/P5/Source/Specs/att.identified.xml index dbb3a3afb2..def3639b3c 100644 --- a/P5/Source/Specs/att.identified.xml +++ b/P5/Source/Specs/att.identified.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.internetMedia.xml b/P5/Source/Specs/att.internetMedia.xml index 9aa4efe255..b0ae3c6564 100644 --- a/P5/Source/Specs/att.internetMedia.xml +++ b/P5/Source/Specs/att.internetMedia.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.interpLike.xml b/P5/Source/Specs/att.interpLike.xml index 98431f97c8..17debf1f49 100644 --- a/P5/Source/Specs/att.interpLike.xml +++ b/P5/Source/Specs/att.interpLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.lexicographic.xml b/P5/Source/Specs/att.lexicographic.xml index 2679a2a94a..2edad5524a 100644 --- a/P5/Source/Specs/att.lexicographic.xml +++ b/P5/Source/Specs/att.lexicographic.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.linguistic.xml b/P5/Source/Specs/att.linguistic.xml index 1994494e63..ba3f7b3a8f 100644 --- a/P5/Source/Specs/att.linguistic.xml +++ b/P5/Source/Specs/att.linguistic.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.locatable.xml b/P5/Source/Specs/att.locatable.xml index 830ae5281b..173f78b874 100644 --- a/P5/Source/Specs/att.locatable.xml +++ b/P5/Source/Specs/att.locatable.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.media.xml b/P5/Source/Specs/att.media.xml index baaec18dac..b8047e105b 100644 --- a/P5/Source/Specs/att.media.xml +++ b/P5/Source/Specs/att.media.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.metrical.xml b/P5/Source/Specs/att.metrical.xml index e63bd07782..26ec9bbd6d 100644 --- a/P5/Source/Specs/att.metrical.xml +++ b/P5/Source/Specs/att.metrical.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.milestoneUnit.xml b/P5/Source/Specs/att.milestoneUnit.xml index b722615eef..c8b41afa3b 100644 --- a/P5/Source/Specs/att.milestoneUnit.xml +++ b/P5/Source/Specs/att.milestoneUnit.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.msExcerpt.xml b/P5/Source/Specs/att.msExcerpt.xml index 92bc6df421..2c08f8654e 100644 --- a/P5/Source/Specs/att.msExcerpt.xml +++ b/P5/Source/Specs/att.msExcerpt.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.namespaceable.xml b/P5/Source/Specs/att.namespaceable.xml index 605fbe4f52..f330c1d0be 100644 --- a/P5/Source/Specs/att.namespaceable.xml +++ b/P5/Source/Specs/att.namespaceable.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.naming.xml b/P5/Source/Specs/att.naming.xml index 8fc1e7b118..02661b59ef 100644 --- a/P5/Source/Specs/att.naming.xml +++ b/P5/Source/Specs/att.naming.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.notated.xml b/P5/Source/Specs/att.notated.xml index 07055a8055..4d32a7d9a8 100644 --- a/P5/Source/Specs/att.notated.xml +++ b/P5/Source/Specs/att.notated.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.partials.xml b/P5/Source/Specs/att.partials.xml index ea22dbe46a..e0a596e52b 100644 --- a/P5/Source/Specs/att.partials.xml +++ b/P5/Source/Specs/att.partials.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.patternReplacement.xml b/P5/Source/Specs/att.patternReplacement.xml index 95bd7803b9..2d4120e515 100644 --- a/P5/Source/Specs/att.patternReplacement.xml +++ b/P5/Source/Specs/att.patternReplacement.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.personal.xml b/P5/Source/Specs/att.personal.xml index aedeb3f6a4..b9de4ef0da 100644 --- a/P5/Source/Specs/att.personal.xml +++ b/P5/Source/Specs/att.personal.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.placement.xml b/P5/Source/Specs/att.placement.xml index e500b40c38..ea39dd853e 100644 --- a/P5/Source/Specs/att.placement.xml +++ b/P5/Source/Specs/att.placement.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.pointing.group.xml b/P5/Source/Specs/att.pointing.group.xml index 1d0b692f75..608afc689e 100644 --- a/P5/Source/Specs/att.pointing.group.xml +++ b/P5/Source/Specs/att.pointing.group.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.pointing.xml b/P5/Source/Specs/att.pointing.xml index 068af0dec9..be6706a871 100644 --- a/P5/Source/Specs/att.pointing.xml +++ b/P5/Source/Specs/att.pointing.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.predicate.xml b/P5/Source/Specs/att.predicate.xml index 35fe5f572b..c59aa6d56b 100644 --- a/P5/Source/Specs/att.predicate.xml +++ b/P5/Source/Specs/att.predicate.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.ranging.xml b/P5/Source/Specs/att.ranging.xml index b56565c95e..de53817f95 100644 --- a/P5/Source/Specs/att.ranging.xml +++ b/P5/Source/Specs/att.ranging.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.rdgPart.xml b/P5/Source/Specs/att.rdgPart.xml index f67751789a..e8beac7127 100644 --- a/P5/Source/Specs/att.rdgPart.xml +++ b/P5/Source/Specs/att.rdgPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.repeatable.xml b/P5/Source/Specs/att.repeatable.xml index 47943bf7fb..d998311c9c 100644 --- a/P5/Source/Specs/att.repeatable.xml +++ b/P5/Source/Specs/att.repeatable.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.resourced.xml b/P5/Source/Specs/att.resourced.xml index 24775f1a3b..063cfa695d 100644 --- a/P5/Source/Specs/att.resourced.xml +++ b/P5/Source/Specs/att.resourced.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.scoping.xml b/P5/Source/Specs/att.scoping.xml index c8fd3ca714..564e87fac2 100644 --- a/P5/Source/Specs/att.scoping.xml +++ b/P5/Source/Specs/att.scoping.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.segLike.xml b/P5/Source/Specs/att.segLike.xml index 15bb6a8e2a..ec569cd46b 100644 --- a/P5/Source/Specs/att.segLike.xml +++ b/P5/Source/Specs/att.segLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.sortable.xml b/P5/Source/Specs/att.sortable.xml index 124c80d0d9..1b66543ebb 100644 --- a/P5/Source/Specs/att.sortable.xml +++ b/P5/Source/Specs/att.sortable.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.spanning.xml b/P5/Source/Specs/att.spanning.xml index 6a95a334da..71b1611f64 100644 --- a/P5/Source/Specs/att.spanning.xml +++ b/P5/Source/Specs/att.spanning.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.styleDef.xml b/P5/Source/Specs/att.styleDef.xml index 940244f693..c51ad1314c 100644 --- a/P5/Source/Specs/att.styleDef.xml +++ b/P5/Source/Specs/att.styleDef.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.tableDecoration.xml b/P5/Source/Specs/att.tableDecoration.xml index 8c070340f0..32616a0f09 100644 --- a/P5/Source/Specs/att.tableDecoration.xml +++ b/P5/Source/Specs/att.tableDecoration.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.textCritical.xml b/P5/Source/Specs/att.textCritical.xml index 47dc41845a..0a615ba848 100644 --- a/P5/Source/Specs/att.textCritical.xml +++ b/P5/Source/Specs/att.textCritical.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.timed.xml b/P5/Source/Specs/att.timed.xml index a9773626a0..3212075348 100644 --- a/P5/Source/Specs/att.timed.xml +++ b/P5/Source/Specs/att.timed.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.transcriptional.xml b/P5/Source/Specs/att.transcriptional.xml index b3904c4cd2..af34c63c6c 100644 --- a/P5/Source/Specs/att.transcriptional.xml +++ b/P5/Source/Specs/att.transcriptional.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.translatable.xml b/P5/Source/Specs/att.translatable.xml index 547d2185ce..4565876756 100644 --- a/P5/Source/Specs/att.translatable.xml +++ b/P5/Source/Specs/att.translatable.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.typed.xml b/P5/Source/Specs/att.typed.xml index 49cc5c4c0c..f9adf9696c 100644 --- a/P5/Source/Specs/att.typed.xml +++ b/P5/Source/Specs/att.typed.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.witnessed.xml b/P5/Source/Specs/att.witnessed.xml index f094331a9c..c08ec0f2cb 100644 --- a/P5/Source/Specs/att.witnessed.xml +++ b/P5/Source/Specs/att.witnessed.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.written.xml b/P5/Source/Specs/att.written.xml index 16b8ff40fc..ccde47fe80 100644 --- a/P5/Source/Specs/att.written.xml +++ b/P5/Source/Specs/att.written.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.xml b/P5/Source/Specs/att.xml index a68bf3029e..46f891d634 100644 --- a/P5/Source/Specs/att.xml +++ b/P5/Source/Specs/att.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/attDef.xml b/P5/Source/Specs/attDef.xml index 4dc8ac0e27..c4a55b11f7 100644 --- a/P5/Source/Specs/attDef.xml +++ b/P5/Source/Specs/attDef.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/attList.xml b/P5/Source/Specs/attList.xml index a2a7c7fbc6..06f0db90cf 100644 --- a/P5/Source/Specs/attList.xml +++ b/P5/Source/Specs/attList.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/attRef.xml b/P5/Source/Specs/attRef.xml index 7fc2e4859b..9c7dc32e87 100644 --- a/P5/Source/Specs/attRef.xml +++ b/P5/Source/Specs/attRef.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/authority.xml b/P5/Source/Specs/authority.xml index cf06e094f6..4f269ce281 100644 --- a/P5/Source/Specs/authority.xml +++ b/P5/Source/Specs/authority.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/availability.xml b/P5/Source/Specs/availability.xml index 461e029701..f6fa6a0b0d 100644 --- a/P5/Source/Specs/availability.xml +++ b/P5/Source/Specs/availability.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/back.xml b/P5/Source/Specs/back.xml index aeca2168e9..9453ec0cc2 100644 --- a/P5/Source/Specs/back.xml +++ b/P5/Source/Specs/back.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/bibl.xml b/P5/Source/Specs/bibl.xml index 3a6df7d3f7..89eb998995 100644 --- a/P5/Source/Specs/bibl.xml +++ b/P5/Source/Specs/bibl.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/biblFull.xml b/P5/Source/Specs/biblFull.xml index 0210fdb6a9..de359d2876 100644 --- a/P5/Source/Specs/biblFull.xml +++ b/P5/Source/Specs/biblFull.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/biblScope.xml b/P5/Source/Specs/biblScope.xml index a4b425029d..3682ffd5b1 100644 --- a/P5/Source/Specs/biblScope.xml +++ b/P5/Source/Specs/biblScope.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/biblStruct.xml b/P5/Source/Specs/biblStruct.xml index 1d011834d7..36ec4f8b7a 100644 --- a/P5/Source/Specs/biblStruct.xml +++ b/P5/Source/Specs/biblStruct.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/bicond.xml b/P5/Source/Specs/bicond.xml index 86d96ebb67..5059a0a142 100644 --- a/P5/Source/Specs/bicond.xml +++ b/P5/Source/Specs/bicond.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/binary.xml b/P5/Source/Specs/binary.xml index b9be6e9697..919333114f 100644 --- a/P5/Source/Specs/binary.xml +++ b/P5/Source/Specs/binary.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/binaryObject.xml b/P5/Source/Specs/binaryObject.xml index f205dc4dfb..88ce086b59 100644 --- a/P5/Source/Specs/binaryObject.xml +++ b/P5/Source/Specs/binaryObject.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/bindingDesc.xml b/P5/Source/Specs/bindingDesc.xml index 96fcfb40f3..5af5063ac9 100644 --- a/P5/Source/Specs/bindingDesc.xml +++ b/P5/Source/Specs/bindingDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/body.xml b/P5/Source/Specs/body.xml index 8cd927de7d..d997b57c2a 100644 --- a/P5/Source/Specs/body.xml +++ b/P5/Source/Specs/body.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/broadcast.xml b/P5/Source/Specs/broadcast.xml index d18684b500..0c0d7d2f26 100644 --- a/P5/Source/Specs/broadcast.xml +++ b/P5/Source/Specs/broadcast.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/byline.xml b/P5/Source/Specs/byline.xml index 7791edd8a2..7a3caf9f0e 100644 --- a/P5/Source/Specs/byline.xml +++ b/P5/Source/Specs/byline.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/c.xml b/P5/Source/Specs/c.xml index f4c4d54a59..5151bf6108 100644 --- a/P5/Source/Specs/c.xml +++ b/P5/Source/Specs/c.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/cRefPattern.xml b/P5/Source/Specs/cRefPattern.xml index dc58b6f9f9..32cbe8280c 100644 --- a/P5/Source/Specs/cRefPattern.xml +++ b/P5/Source/Specs/cRefPattern.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/caesura.xml b/P5/Source/Specs/caesura.xml index 198a841591..2e4769ff90 100644 --- a/P5/Source/Specs/caesura.xml +++ b/P5/Source/Specs/caesura.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/calendar.xml b/P5/Source/Specs/calendar.xml index 1d27b8a48f..1795e00f7e 100644 --- a/P5/Source/Specs/calendar.xml +++ b/P5/Source/Specs/calendar.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/calendarDesc.xml b/P5/Source/Specs/calendarDesc.xml index c7ed2b1e1a..5b43b3eab7 100644 --- a/P5/Source/Specs/calendarDesc.xml +++ b/P5/Source/Specs/calendarDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/camera.xml b/P5/Source/Specs/camera.xml index 1b9448cef2..362ee40d6d 100644 --- a/P5/Source/Specs/camera.xml +++ b/P5/Source/Specs/camera.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/caption.xml b/P5/Source/Specs/caption.xml index 4be4953868..a4cf82f135 100644 --- a/P5/Source/Specs/caption.xml +++ b/P5/Source/Specs/caption.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/case.xml b/P5/Source/Specs/case.xml index 449e3c61fe..1e84cdb86a 100644 --- a/P5/Source/Specs/case.xml +++ b/P5/Source/Specs/case.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/castGroup.xml b/P5/Source/Specs/castGroup.xml index 104ff6e9ca..420fad30d0 100644 --- a/P5/Source/Specs/castGroup.xml +++ b/P5/Source/Specs/castGroup.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/castItem.xml b/P5/Source/Specs/castItem.xml index 9dcf03c2df..cb38befe7b 100644 --- a/P5/Source/Specs/castItem.xml +++ b/P5/Source/Specs/castItem.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/castList.xml b/P5/Source/Specs/castList.xml index 30081fa397..0c6db4b5d7 100644 --- a/P5/Source/Specs/castList.xml +++ b/P5/Source/Specs/castList.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/catDesc.xml b/P5/Source/Specs/catDesc.xml index d94f20bf5c..7c5eee627d 100644 --- a/P5/Source/Specs/catDesc.xml +++ b/P5/Source/Specs/catDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/catRef.xml b/P5/Source/Specs/catRef.xml index dd50289688..dc1d662095 100644 --- a/P5/Source/Specs/catRef.xml +++ b/P5/Source/Specs/catRef.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/catchwords.xml b/P5/Source/Specs/catchwords.xml index 5db3ac3d98..0dea6a3fc2 100644 --- a/P5/Source/Specs/catchwords.xml +++ b/P5/Source/Specs/catchwords.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/category.xml b/P5/Source/Specs/category.xml index add5e24715..c65549e62f 100644 --- a/P5/Source/Specs/category.xml +++ b/P5/Source/Specs/category.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/cb.xml b/P5/Source/Specs/cb.xml index 8733f949aa..ad01b8ce5c 100644 --- a/P5/Source/Specs/cb.xml +++ b/P5/Source/Specs/cb.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/cell.xml b/P5/Source/Specs/cell.xml index c5b8e783a5..194b1fdcbc 100644 --- a/P5/Source/Specs/cell.xml +++ b/P5/Source/Specs/cell.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/certainty.xml b/P5/Source/Specs/certainty.xml index cc4245e8bf..dbab1a7661 100644 --- a/P5/Source/Specs/certainty.xml +++ b/P5/Source/Specs/certainty.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/channel.xml b/P5/Source/Specs/channel.xml index cbc26f9f1e..420031e21e 100644 --- a/P5/Source/Specs/channel.xml +++ b/P5/Source/Specs/channel.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/char.xml b/P5/Source/Specs/char.xml index 0ee8e4a39a..b0af7995d8 100644 --- a/P5/Source/Specs/char.xml +++ b/P5/Source/Specs/char.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/charDecl.xml b/P5/Source/Specs/charDecl.xml index cb28b4f15c..03f34fab08 100644 --- a/P5/Source/Specs/charDecl.xml +++ b/P5/Source/Specs/charDecl.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/choice.xml b/P5/Source/Specs/choice.xml index 5bd682b7b7..9cd79835c8 100644 --- a/P5/Source/Specs/choice.xml +++ b/P5/Source/Specs/choice.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/cit.xml b/P5/Source/Specs/cit.xml index a91da2eba5..7c846a1267 100644 --- a/P5/Source/Specs/cit.xml +++ b/P5/Source/Specs/cit.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/citeData.xml b/P5/Source/Specs/citeData.xml index 765b2a6745..1a526b59d5 100644 --- a/P5/Source/Specs/citeData.xml +++ b/P5/Source/Specs/citeData.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/citeStructure.xml b/P5/Source/Specs/citeStructure.xml index 1267156072..2992cab228 100644 --- a/P5/Source/Specs/citeStructure.xml +++ b/P5/Source/Specs/citeStructure.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/citedRange.xml b/P5/Source/Specs/citedRange.xml index 96ab927cc7..658a506ce0 100644 --- a/P5/Source/Specs/citedRange.xml +++ b/P5/Source/Specs/citedRange.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/cl.xml b/P5/Source/Specs/cl.xml index ffb6558a25..2b5d42838a 100644 --- a/P5/Source/Specs/cl.xml +++ b/P5/Source/Specs/cl.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/classCode.xml b/P5/Source/Specs/classCode.xml index 99a61f1f23..0159b376af 100644 --- a/P5/Source/Specs/classCode.xml +++ b/P5/Source/Specs/classCode.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/classDecl.xml b/P5/Source/Specs/classDecl.xml index 324705b85f..fedc67a79b 100644 --- a/P5/Source/Specs/classDecl.xml +++ b/P5/Source/Specs/classDecl.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/classRef.xml b/P5/Source/Specs/classRef.xml index 2b4ed3ae86..c54c02cd8b 100644 --- a/P5/Source/Specs/classRef.xml +++ b/P5/Source/Specs/classRef.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/classSpec.xml b/P5/Source/Specs/classSpec.xml index 35b92073eb..bd2ba92970 100644 --- a/P5/Source/Specs/classSpec.xml +++ b/P5/Source/Specs/classSpec.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/classes.xml b/P5/Source/Specs/classes.xml index 5ae286a64a..600a936395 100644 --- a/P5/Source/Specs/classes.xml +++ b/P5/Source/Specs/classes.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/closer.xml b/P5/Source/Specs/closer.xml index d62ca55468..7cf7854dc8 100644 --- a/P5/Source/Specs/closer.xml +++ b/P5/Source/Specs/closer.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/code.xml b/P5/Source/Specs/code.xml index 4d3a193ed8..c522f2d104 100644 --- a/P5/Source/Specs/code.xml +++ b/P5/Source/Specs/code.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/collation.xml b/P5/Source/Specs/collation.xml index 0763b55d71..9078d3d630 100644 --- a/P5/Source/Specs/collation.xml +++ b/P5/Source/Specs/collation.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/collection.xml b/P5/Source/Specs/collection.xml index 1b2a33d3b9..7787d7a429 100644 --- a/P5/Source/Specs/collection.xml +++ b/P5/Source/Specs/collection.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/colloc.xml b/P5/Source/Specs/colloc.xml index d6ff1f2402..f08d542912 100644 --- a/P5/Source/Specs/colloc.xml +++ b/P5/Source/Specs/colloc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/colophon.xml b/P5/Source/Specs/colophon.xml index 023ef2c58a..e595695616 100644 --- a/P5/Source/Specs/colophon.xml +++ b/P5/Source/Specs/colophon.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/cond.xml b/P5/Source/Specs/cond.xml index 075eb6604b..651c00877b 100644 --- a/P5/Source/Specs/cond.xml +++ b/P5/Source/Specs/cond.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/condition.xml b/P5/Source/Specs/condition.xml index b8557cf82f..062ff74942 100644 --- a/P5/Source/Specs/condition.xml +++ b/P5/Source/Specs/condition.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/constitution.xml b/P5/Source/Specs/constitution.xml index 1a93567456..7db2fdf463 100644 --- a/P5/Source/Specs/constitution.xml +++ b/P5/Source/Specs/constitution.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/constraint.xml b/P5/Source/Specs/constraint.xml index 0fed8d29f4..a174228e3e 100644 --- a/P5/Source/Specs/constraint.xml +++ b/P5/Source/Specs/constraint.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/constraintSpec.xml b/P5/Source/Specs/constraintSpec.xml index 730a21006f..d4372507c7 100644 --- a/P5/Source/Specs/constraintSpec.xml +++ b/P5/Source/Specs/constraintSpec.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/content.xml b/P5/Source/Specs/content.xml index 0a16393c33..3fa014b639 100644 --- a/P5/Source/Specs/content.xml +++ b/P5/Source/Specs/content.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/corr.xml b/P5/Source/Specs/corr.xml index 18a41fe203..6625d423f2 100644 --- a/P5/Source/Specs/corr.xml +++ b/P5/Source/Specs/corr.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/correction.xml b/P5/Source/Specs/correction.xml index 986ff0c72f..7544d27ae4 100644 --- a/P5/Source/Specs/correction.xml +++ b/P5/Source/Specs/correction.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/correspAction.xml b/P5/Source/Specs/correspAction.xml index 63b7665597..e984573497 100644 --- a/P5/Source/Specs/correspAction.xml +++ b/P5/Source/Specs/correspAction.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/correspContext.xml b/P5/Source/Specs/correspContext.xml index 95725f99c8..3dbdfa6896 100644 --- a/P5/Source/Specs/correspContext.xml +++ b/P5/Source/Specs/correspContext.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/correspDesc.xml b/P5/Source/Specs/correspDesc.xml index 61185f249b..f34d1f8252 100644 --- a/P5/Source/Specs/correspDesc.xml +++ b/P5/Source/Specs/correspDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/custodialHist.xml b/P5/Source/Specs/custodialHist.xml index 63a149864d..8c45b16d06 100644 --- a/P5/Source/Specs/custodialHist.xml +++ b/P5/Source/Specs/custodialHist.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/damageSpan.xml b/P5/Source/Specs/damageSpan.xml index 39c84ff87b..78adc5279b 100644 --- a/P5/Source/Specs/damageSpan.xml +++ b/P5/Source/Specs/damageSpan.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/dataFacet.xml b/P5/Source/Specs/dataFacet.xml index 6954775c24..44799e9694 100644 --- a/P5/Source/Specs/dataFacet.xml +++ b/P5/Source/Specs/dataFacet.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/dataRef.xml b/P5/Source/Specs/dataRef.xml index 44b85684e0..5de6997ea0 100644 --- a/P5/Source/Specs/dataRef.xml +++ b/P5/Source/Specs/dataRef.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/dataSpec.xml b/P5/Source/Specs/dataSpec.xml index 4cbf602afc..d8c90e46c1 100644 --- a/P5/Source/Specs/dataSpec.xml +++ b/P5/Source/Specs/dataSpec.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/datatype.xml b/P5/Source/Specs/datatype.xml index 5cda5dca0b..2277562fd1 100644 --- a/P5/Source/Specs/datatype.xml +++ b/P5/Source/Specs/datatype.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/date.xml b/P5/Source/Specs/date.xml index ea67955764..709566274b 100644 --- a/P5/Source/Specs/date.xml +++ b/P5/Source/Specs/date.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/dateline.xml b/P5/Source/Specs/dateline.xml index 7024c733a2..40f6626e0e 100644 --- a/P5/Source/Specs/dateline.xml +++ b/P5/Source/Specs/dateline.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/decoDesc.xml b/P5/Source/Specs/decoDesc.xml index ff67a4a0dd..13a9317457 100644 --- a/P5/Source/Specs/decoDesc.xml +++ b/P5/Source/Specs/decoDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/decoNote.xml b/P5/Source/Specs/decoNote.xml index 0b1670c677..5883c93015 100644 --- a/P5/Source/Specs/decoNote.xml +++ b/P5/Source/Specs/decoNote.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/def.xml b/P5/Source/Specs/def.xml index bc45f93afe..606675b53a 100644 --- a/P5/Source/Specs/def.xml +++ b/P5/Source/Specs/def.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/default.xml b/P5/Source/Specs/default.xml index 2abea157b0..feaa206473 100644 --- a/P5/Source/Specs/default.xml +++ b/P5/Source/Specs/default.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/defaultVal.xml b/P5/Source/Specs/defaultVal.xml index 5d7aa6381b..d45c68a302 100644 --- a/P5/Source/Specs/defaultVal.xml +++ b/P5/Source/Specs/defaultVal.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/del.xml b/P5/Source/Specs/del.xml index 921f09ece1..0cafd9eeae 100644 --- a/P5/Source/Specs/del.xml +++ b/P5/Source/Specs/del.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/delSpan.xml b/P5/Source/Specs/delSpan.xml index bb11e0a97e..fbeea67ab8 100644 --- a/P5/Source/Specs/delSpan.xml +++ b/P5/Source/Specs/delSpan.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/depth.xml b/P5/Source/Specs/depth.xml index d127fc9cfb..d422b8a927 100644 --- a/P5/Source/Specs/depth.xml +++ b/P5/Source/Specs/depth.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/derivation.xml b/P5/Source/Specs/derivation.xml index 1f060134da..2bd0f6439e 100644 --- a/P5/Source/Specs/derivation.xml +++ b/P5/Source/Specs/derivation.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/desc.xml b/P5/Source/Specs/desc.xml index b83b04119f..456113e9ab 100644 --- a/P5/Source/Specs/desc.xml +++ b/P5/Source/Specs/desc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/dictScrap.xml b/P5/Source/Specs/dictScrap.xml index 035e180c62..19840ec46c 100644 --- a/P5/Source/Specs/dictScrap.xml +++ b/P5/Source/Specs/dictScrap.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/dim.xml b/P5/Source/Specs/dim.xml index 3b7b15c68b..a9454860f7 100644 --- a/P5/Source/Specs/dim.xml +++ b/P5/Source/Specs/dim.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/dimensions.xml b/P5/Source/Specs/dimensions.xml index af40664086..52b4d0dfd5 100644 --- a/P5/Source/Specs/dimensions.xml +++ b/P5/Source/Specs/dimensions.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/distinct.xml b/P5/Source/Specs/distinct.xml index 8b4a38ebac..1072eb9b40 100644 --- a/P5/Source/Specs/distinct.xml +++ b/P5/Source/Specs/distinct.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/distributor.xml b/P5/Source/Specs/distributor.xml index 0f6497090b..1cb8a7bbb7 100644 --- a/P5/Source/Specs/distributor.xml +++ b/P5/Source/Specs/distributor.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/div.xml b/P5/Source/Specs/div.xml index 368d51c391..39e8c989b9 100644 --- a/P5/Source/Specs/div.xml +++ b/P5/Source/Specs/div.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/div1.xml b/P5/Source/Specs/div1.xml index 1ed1c0d817..7200b5b6e5 100644 --- a/P5/Source/Specs/div1.xml +++ b/P5/Source/Specs/div1.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/div2.xml b/P5/Source/Specs/div2.xml index b569201c71..00fc2e827d 100644 --- a/P5/Source/Specs/div2.xml +++ b/P5/Source/Specs/div2.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/div3.xml b/P5/Source/Specs/div3.xml index 38126a40fd..0ef90c0416 100644 --- a/P5/Source/Specs/div3.xml +++ b/P5/Source/Specs/div3.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/div4.xml b/P5/Source/Specs/div4.xml index 00e3a63e16..77098e55f3 100644 --- a/P5/Source/Specs/div4.xml +++ b/P5/Source/Specs/div4.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/div5.xml b/P5/Source/Specs/div5.xml index 98ffb36330..8de091464d 100644 --- a/P5/Source/Specs/div5.xml +++ b/P5/Source/Specs/div5.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/div6.xml b/P5/Source/Specs/div6.xml index effa7143f1..8a106356c2 100644 --- a/P5/Source/Specs/div6.xml +++ b/P5/Source/Specs/div6.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/div7.xml b/P5/Source/Specs/div7.xml index 76cd431222..7c12ef44ff 100644 --- a/P5/Source/Specs/div7.xml +++ b/P5/Source/Specs/div7.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/divGen.xml b/P5/Source/Specs/divGen.xml index f0fc89a123..b07284e1ea 100644 --- a/P5/Source/Specs/divGen.xml +++ b/P5/Source/Specs/divGen.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/docAuthor.xml b/P5/Source/Specs/docAuthor.xml index 974f175a18..ebcb1fa30b 100644 --- a/P5/Source/Specs/docAuthor.xml +++ b/P5/Source/Specs/docAuthor.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/docDate.xml b/P5/Source/Specs/docDate.xml index a1762ddae6..84d3bc7db5 100644 --- a/P5/Source/Specs/docDate.xml +++ b/P5/Source/Specs/docDate.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/docEdition.xml b/P5/Source/Specs/docEdition.xml index f7b516b48b..ca9b1a3a18 100644 --- a/P5/Source/Specs/docEdition.xml +++ b/P5/Source/Specs/docEdition.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/docImprint.xml b/P5/Source/Specs/docImprint.xml index 2a7e5ffbb6..04680f550a 100644 --- a/P5/Source/Specs/docImprint.xml +++ b/P5/Source/Specs/docImprint.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/docTitle.xml b/P5/Source/Specs/docTitle.xml index 4ba9ff0707..6d6e15bdac 100644 --- a/P5/Source/Specs/docTitle.xml +++ b/P5/Source/Specs/docTitle.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/domain.xml b/P5/Source/Specs/domain.xml index 36de7e0537..75b7a63b1c 100644 --- a/P5/Source/Specs/domain.xml +++ b/P5/Source/Specs/domain.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/eLeaf.xml b/P5/Source/Specs/eLeaf.xml index dd2ababbb9..3824945b89 100644 --- a/P5/Source/Specs/eLeaf.xml +++ b/P5/Source/Specs/eLeaf.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/eTree.xml b/P5/Source/Specs/eTree.xml index 2db1826f14..c5ed6fc3d7 100644 --- a/P5/Source/Specs/eTree.xml +++ b/P5/Source/Specs/eTree.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/edition.xml b/P5/Source/Specs/edition.xml index ad9ef780be..e97f543484 100644 --- a/P5/Source/Specs/edition.xml +++ b/P5/Source/Specs/edition.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/editionStmt.xml b/P5/Source/Specs/editionStmt.xml index e77529a1c5..0361735562 100644 --- a/P5/Source/Specs/editionStmt.xml +++ b/P5/Source/Specs/editionStmt.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/editorialDecl.xml b/P5/Source/Specs/editorialDecl.xml index ef6caf312b..99fadb634a 100644 --- a/P5/Source/Specs/editorialDecl.xml +++ b/P5/Source/Specs/editorialDecl.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/eg.xml b/P5/Source/Specs/eg.xml index a866fb5d9d..ff6fc2ccc4 100644 --- a/P5/Source/Specs/eg.xml +++ b/P5/Source/Specs/eg.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/egXML.xml b/P5/Source/Specs/egXML.xml index e0889cfd6c..a29290d82e 100644 --- a/P5/Source/Specs/egXML.xml +++ b/P5/Source/Specs/egXML.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/elementRef.xml b/P5/Source/Specs/elementRef.xml index ee3077650b..95babaa2a4 100644 --- a/P5/Source/Specs/elementRef.xml +++ b/P5/Source/Specs/elementRef.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/elementSpec.xml b/P5/Source/Specs/elementSpec.xml index 0c065a5d4f..ca33f9e5e6 100644 --- a/P5/Source/Specs/elementSpec.xml +++ b/P5/Source/Specs/elementSpec.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/ellipsis.xml b/P5/Source/Specs/ellipsis.xml index f9e8e31dfb..6299c4932a 100644 --- a/P5/Source/Specs/ellipsis.xml +++ b/P5/Source/Specs/ellipsis.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/email.xml b/P5/Source/Specs/email.xml index 75c9d9058d..c39c4ea84e 100644 --- a/P5/Source/Specs/email.xml +++ b/P5/Source/Specs/email.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/emph.xml b/P5/Source/Specs/emph.xml index 22a625864e..d918421d13 100644 --- a/P5/Source/Specs/emph.xml +++ b/P5/Source/Specs/emph.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/empty.xml b/P5/Source/Specs/empty.xml index daccd52c84..663ba5de5b 100644 --- a/P5/Source/Specs/empty.xml +++ b/P5/Source/Specs/empty.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/encodingDesc.xml b/P5/Source/Specs/encodingDesc.xml index 5f393b68a9..52a8b2eb94 100644 --- a/P5/Source/Specs/encodingDesc.xml +++ b/P5/Source/Specs/encodingDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/entry.xml b/P5/Source/Specs/entry.xml index c93b53d4c6..d2a6cb13b6 100644 --- a/P5/Source/Specs/entry.xml +++ b/P5/Source/Specs/entry.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/entryFree.xml b/P5/Source/Specs/entryFree.xml index 93613ffa7c..a88b644654 100644 --- a/P5/Source/Specs/entryFree.xml +++ b/P5/Source/Specs/entryFree.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/epigraph.xml b/P5/Source/Specs/epigraph.xml index 0b9e75656f..0bf803b7fa 100644 --- a/P5/Source/Specs/epigraph.xml +++ b/P5/Source/Specs/epigraph.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/epilogue.xml b/P5/Source/Specs/epilogue.xml index 6d8e6feeee..7575f42858 100644 --- a/P5/Source/Specs/epilogue.xml +++ b/P5/Source/Specs/epilogue.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/equipment.xml b/P5/Source/Specs/equipment.xml index dd63dbdd67..8aacead70f 100644 --- a/P5/Source/Specs/equipment.xml +++ b/P5/Source/Specs/equipment.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/equiv.xml b/P5/Source/Specs/equiv.xml index 5109b7e769..f52b301199 100644 --- a/P5/Source/Specs/equiv.xml +++ b/P5/Source/Specs/equiv.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/etym.xml b/P5/Source/Specs/etym.xml index e4c5a9816b..df05226923 100644 --- a/P5/Source/Specs/etym.xml +++ b/P5/Source/Specs/etym.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/event.xml b/P5/Source/Specs/event.xml index 51979fb276..1902d9df0d 100644 --- a/P5/Source/Specs/event.xml +++ b/P5/Source/Specs/event.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/eventName.xml b/P5/Source/Specs/eventName.xml index fd76bcc327..16a33b74f2 100644 --- a/P5/Source/Specs/eventName.xml +++ b/P5/Source/Specs/eventName.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/ex.xml b/P5/Source/Specs/ex.xml index fd9315b5d3..2eea604d73 100644 --- a/P5/Source/Specs/ex.xml +++ b/P5/Source/Specs/ex.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/exemplum.xml b/P5/Source/Specs/exemplum.xml index 5bb19cb7d0..84bd2bbdda 100644 --- a/P5/Source/Specs/exemplum.xml +++ b/P5/Source/Specs/exemplum.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/expan.xml b/P5/Source/Specs/expan.xml index 4602e558e1..f892e1b14f 100644 --- a/P5/Source/Specs/expan.xml +++ b/P5/Source/Specs/expan.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/explicit.xml b/P5/Source/Specs/explicit.xml index f04a365de5..dce7ce320d 100644 --- a/P5/Source/Specs/explicit.xml +++ b/P5/Source/Specs/explicit.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/extent.xml b/P5/Source/Specs/extent.xml index af9ea8b811..c702bf7ba8 100644 --- a/P5/Source/Specs/extent.xml +++ b/P5/Source/Specs/extent.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/f.xml b/P5/Source/Specs/f.xml index fc21582245..18ca1fba66 100644 --- a/P5/Source/Specs/f.xml +++ b/P5/Source/Specs/f.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/fDecl.xml b/P5/Source/Specs/fDecl.xml index d31d8ec638..5e94d789f9 100644 --- a/P5/Source/Specs/fDecl.xml +++ b/P5/Source/Specs/fDecl.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/fDescr.xml b/P5/Source/Specs/fDescr.xml index 0d24fff402..bffcee4ac8 100644 --- a/P5/Source/Specs/fDescr.xml +++ b/P5/Source/Specs/fDescr.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/fLib.xml b/P5/Source/Specs/fLib.xml index c2a9514f1f..b7645f61c3 100644 --- a/P5/Source/Specs/fLib.xml +++ b/P5/Source/Specs/fLib.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/facsimile.xml b/P5/Source/Specs/facsimile.xml index 5adeacaa4e..a97e0a346b 100644 --- a/P5/Source/Specs/facsimile.xml +++ b/P5/Source/Specs/facsimile.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/factuality.xml b/P5/Source/Specs/factuality.xml index b505238511..8a664c5fa2 100644 --- a/P5/Source/Specs/factuality.xml +++ b/P5/Source/Specs/factuality.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/figDesc.xml b/P5/Source/Specs/figDesc.xml index ff42825bc6..d6c79130db 100644 --- a/P5/Source/Specs/figDesc.xml +++ b/P5/Source/Specs/figDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/figure.xml b/P5/Source/Specs/figure.xml index bba891c05e..f61c5c06d7 100644 --- a/P5/Source/Specs/figure.xml +++ b/P5/Source/Specs/figure.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/fileDesc.xml b/P5/Source/Specs/fileDesc.xml index 71817e08fa..c32b869120 100644 --- a/P5/Source/Specs/fileDesc.xml +++ b/P5/Source/Specs/fileDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/filiation.xml b/P5/Source/Specs/filiation.xml index 8d34706eac..213c38dbb1 100644 --- a/P5/Source/Specs/filiation.xml +++ b/P5/Source/Specs/filiation.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/finalRubric.xml b/P5/Source/Specs/finalRubric.xml index 4698e6e34e..d36766bfe3 100644 --- a/P5/Source/Specs/finalRubric.xml +++ b/P5/Source/Specs/finalRubric.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/floatingText.xml b/P5/Source/Specs/floatingText.xml index b54546da6d..f97cec2d38 100644 --- a/P5/Source/Specs/floatingText.xml +++ b/P5/Source/Specs/floatingText.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/foliation.xml b/P5/Source/Specs/foliation.xml index f4ecf6e06e..235e69008a 100644 --- a/P5/Source/Specs/foliation.xml +++ b/P5/Source/Specs/foliation.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/foreign.xml b/P5/Source/Specs/foreign.xml index 9eeb2fd526..fc9247d40a 100644 --- a/P5/Source/Specs/foreign.xml +++ b/P5/Source/Specs/foreign.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/forename.xml b/P5/Source/Specs/forename.xml index 9b24e9ace0..1877c1f7cf 100644 --- a/P5/Source/Specs/forename.xml +++ b/P5/Source/Specs/forename.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/forest.xml b/P5/Source/Specs/forest.xml index 8b2855b64c..124df837a2 100644 --- a/P5/Source/Specs/forest.xml +++ b/P5/Source/Specs/forest.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/form.xml b/P5/Source/Specs/form.xml index d52cb803ab..7745d6b013 100644 --- a/P5/Source/Specs/form.xml +++ b/P5/Source/Specs/form.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/formula.xml b/P5/Source/Specs/formula.xml index 00c871f755..d1f3b6e0ee 100644 --- a/P5/Source/Specs/formula.xml +++ b/P5/Source/Specs/formula.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/front.xml b/P5/Source/Specs/front.xml index 06bef4f50e..f2b5eea61e 100644 --- a/P5/Source/Specs/front.xml +++ b/P5/Source/Specs/front.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/fs.xml b/P5/Source/Specs/fs.xml index c62b4e84fb..6298a58894 100644 --- a/P5/Source/Specs/fs.xml +++ b/P5/Source/Specs/fs.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/fsConstraints.xml b/P5/Source/Specs/fsConstraints.xml index 1062e69845..fdb36a3d17 100644 --- a/P5/Source/Specs/fsConstraints.xml +++ b/P5/Source/Specs/fsConstraints.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/fsDecl.xml b/P5/Source/Specs/fsDecl.xml index 13ce5aacb5..80824faec2 100644 --- a/P5/Source/Specs/fsDecl.xml +++ b/P5/Source/Specs/fsDecl.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/fsDescr.xml b/P5/Source/Specs/fsDescr.xml index 3906c7054a..8412c4cc63 100644 --- a/P5/Source/Specs/fsDescr.xml +++ b/P5/Source/Specs/fsDescr.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/fsdDecl.xml b/P5/Source/Specs/fsdDecl.xml index 96cd1f1bbd..f925669f9f 100644 --- a/P5/Source/Specs/fsdDecl.xml +++ b/P5/Source/Specs/fsdDecl.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/fsdLink.xml b/P5/Source/Specs/fsdLink.xml index 0d13671f7f..beba71bcd0 100644 --- a/P5/Source/Specs/fsdLink.xml +++ b/P5/Source/Specs/fsdLink.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/fvLib.xml b/P5/Source/Specs/fvLib.xml index 3003d9959d..928faec915 100644 --- a/P5/Source/Specs/fvLib.xml +++ b/P5/Source/Specs/fvLib.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/fw.xml b/P5/Source/Specs/fw.xml index e0689bf233..37927f3111 100644 --- a/P5/Source/Specs/fw.xml +++ b/P5/Source/Specs/fw.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/g.xml b/P5/Source/Specs/g.xml index b7ee6383f2..96528f1c51 100644 --- a/P5/Source/Specs/g.xml +++ b/P5/Source/Specs/g.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/gap.xml b/P5/Source/Specs/gap.xml index ef715fd3c7..216734fe88 100644 --- a/P5/Source/Specs/gap.xml +++ b/P5/Source/Specs/gap.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/gb.xml b/P5/Source/Specs/gb.xml index 44b80bc33b..fb2d89919a 100644 --- a/P5/Source/Specs/gb.xml +++ b/P5/Source/Specs/gb.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/gen.xml b/P5/Source/Specs/gen.xml index f3a197c8ae..9c3d63e449 100644 --- a/P5/Source/Specs/gen.xml +++ b/P5/Source/Specs/gen.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/genName.xml b/P5/Source/Specs/genName.xml index 84552c75ff..b2cbfa4e34 100644 --- a/P5/Source/Specs/genName.xml +++ b/P5/Source/Specs/genName.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/geo.xml b/P5/Source/Specs/geo.xml index 6b431e97aa..75cb35e44f 100644 --- a/P5/Source/Specs/geo.xml +++ b/P5/Source/Specs/geo.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/geoDecl.xml b/P5/Source/Specs/geoDecl.xml index f15b783c8a..461e6d109d 100644 --- a/P5/Source/Specs/geoDecl.xml +++ b/P5/Source/Specs/geoDecl.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/gi.xml b/P5/Source/Specs/gi.xml index 1d603e90a7..57e953156d 100644 --- a/P5/Source/Specs/gi.xml +++ b/P5/Source/Specs/gi.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/gloss.xml b/P5/Source/Specs/gloss.xml index 1248276ca9..78e3a546ee 100644 --- a/P5/Source/Specs/gloss.xml +++ b/P5/Source/Specs/gloss.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/glyph.xml b/P5/Source/Specs/glyph.xml index d18376ccb8..f93c75c354 100644 --- a/P5/Source/Specs/glyph.xml +++ b/P5/Source/Specs/glyph.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/gram.xml b/P5/Source/Specs/gram.xml index 7c8216fdd8..1e71133303 100644 --- a/P5/Source/Specs/gram.xml +++ b/P5/Source/Specs/gram.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/gramGrp.xml b/P5/Source/Specs/gramGrp.xml index a32f855a22..11684c3d89 100644 --- a/P5/Source/Specs/gramGrp.xml +++ b/P5/Source/Specs/gramGrp.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/graph.xml b/P5/Source/Specs/graph.xml index ae8a2e5352..4a6ed4df6b 100644 --- a/P5/Source/Specs/graph.xml +++ b/P5/Source/Specs/graph.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/graphic.xml b/P5/Source/Specs/graphic.xml index 785dedf488..484b498b96 100644 --- a/P5/Source/Specs/graphic.xml +++ b/P5/Source/Specs/graphic.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/group.xml b/P5/Source/Specs/group.xml index 250606b879..3c1e70c7ef 100644 --- a/P5/Source/Specs/group.xml +++ b/P5/Source/Specs/group.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/handDesc.xml b/P5/Source/Specs/handDesc.xml index 9c334f76ec..5502f8cf3b 100644 --- a/P5/Source/Specs/handDesc.xml +++ b/P5/Source/Specs/handDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/handNote.xml b/P5/Source/Specs/handNote.xml index fb50a57c50..a3f276004f 100644 --- a/P5/Source/Specs/handNote.xml +++ b/P5/Source/Specs/handNote.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/handNotes.xml b/P5/Source/Specs/handNotes.xml index 0d9bb6fd17..0bda313232 100644 --- a/P5/Source/Specs/handNotes.xml +++ b/P5/Source/Specs/handNotes.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/handShift.xml b/P5/Source/Specs/handShift.xml index d9db2cf54e..c1b125314c 100644 --- a/P5/Source/Specs/handShift.xml +++ b/P5/Source/Specs/handShift.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/head.xml b/P5/Source/Specs/head.xml index 82593026ba..044a79606a 100644 --- a/P5/Source/Specs/head.xml +++ b/P5/Source/Specs/head.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/headItem.xml b/P5/Source/Specs/headItem.xml index ee23a7f20f..d56ac58f59 100644 --- a/P5/Source/Specs/headItem.xml +++ b/P5/Source/Specs/headItem.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/headLabel.xml b/P5/Source/Specs/headLabel.xml index 2aab40ad81..5654aa3589 100644 --- a/P5/Source/Specs/headLabel.xml +++ b/P5/Source/Specs/headLabel.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/height.xml b/P5/Source/Specs/height.xml index 7b0519755f..6955af7abc 100644 --- a/P5/Source/Specs/height.xml +++ b/P5/Source/Specs/height.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/heraldry.xml b/P5/Source/Specs/heraldry.xml index 816133e3fe..157d67fe9f 100644 --- a/P5/Source/Specs/heraldry.xml +++ b/P5/Source/Specs/heraldry.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/hi.xml b/P5/Source/Specs/hi.xml index 27538b990a..38d552d7d7 100644 --- a/P5/Source/Specs/hi.xml +++ b/P5/Source/Specs/hi.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/history.xml b/P5/Source/Specs/history.xml index 372b9160fe..33acee2629 100644 --- a/P5/Source/Specs/history.xml +++ b/P5/Source/Specs/history.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/hom.xml b/P5/Source/Specs/hom.xml index e0708cec05..de6f25101c 100644 --- a/P5/Source/Specs/hom.xml +++ b/P5/Source/Specs/hom.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/hyph.xml b/P5/Source/Specs/hyph.xml index ac45dd7e88..de8cb05498 100644 --- a/P5/Source/Specs/hyph.xml +++ b/P5/Source/Specs/hyph.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/hyphenation.xml b/P5/Source/Specs/hyphenation.xml index 02c8821df3..8788509470 100644 --- a/P5/Source/Specs/hyphenation.xml +++ b/P5/Source/Specs/hyphenation.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/iNode.xml b/P5/Source/Specs/iNode.xml index 0c1fdfa15d..3f504ce3a1 100644 --- a/P5/Source/Specs/iNode.xml +++ b/P5/Source/Specs/iNode.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/iType.xml b/P5/Source/Specs/iType.xml index 2c1491ea85..5d17618783 100644 --- a/P5/Source/Specs/iType.xml +++ b/P5/Source/Specs/iType.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/ident.xml b/P5/Source/Specs/ident.xml index e619eb3e00..8f6e42e8fe 100644 --- a/P5/Source/Specs/ident.xml +++ b/P5/Source/Specs/ident.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/if.xml b/P5/Source/Specs/if.xml index 6e32083c09..ec21615270 100644 --- a/P5/Source/Specs/if.xml +++ b/P5/Source/Specs/if.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/iff.xml b/P5/Source/Specs/iff.xml index 0a506718cc..2ea5058680 100644 --- a/P5/Source/Specs/iff.xml +++ b/P5/Source/Specs/iff.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/imprimatur.xml b/P5/Source/Specs/imprimatur.xml index 5abd8d91eb..dfe6eb7348 100644 --- a/P5/Source/Specs/imprimatur.xml +++ b/P5/Source/Specs/imprimatur.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/imprint.xml b/P5/Source/Specs/imprint.xml index a61b0d1fa8..4de2c11dca 100644 --- a/P5/Source/Specs/imprint.xml +++ b/P5/Source/Specs/imprint.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/incident.xml b/P5/Source/Specs/incident.xml index c7c434419d..897b8ab58e 100644 --- a/P5/Source/Specs/incident.xml +++ b/P5/Source/Specs/incident.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/incipit.xml b/P5/Source/Specs/incipit.xml index 24b7f3ac16..a3db06c937 100644 --- a/P5/Source/Specs/incipit.xml +++ b/P5/Source/Specs/incipit.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/index.xml b/P5/Source/Specs/index.xml index 34d581418e..99f022c5bf 100644 --- a/P5/Source/Specs/index.xml +++ b/P5/Source/Specs/index.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/institution.xml b/P5/Source/Specs/institution.xml index b40c2ca634..9e5fb18b2a 100644 --- a/P5/Source/Specs/institution.xml +++ b/P5/Source/Specs/institution.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/interaction.xml b/P5/Source/Specs/interaction.xml index 7754feb09a..34ec2d8803 100644 --- a/P5/Source/Specs/interaction.xml +++ b/P5/Source/Specs/interaction.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/interp.xml b/P5/Source/Specs/interp.xml index f7e47b68fa..207f4324c5 100644 --- a/P5/Source/Specs/interp.xml +++ b/P5/Source/Specs/interp.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/interpGrp.xml b/P5/Source/Specs/interpGrp.xml index 9b0b5cce97..754f723f6e 100644 --- a/P5/Source/Specs/interpGrp.xml +++ b/P5/Source/Specs/interpGrp.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/interpretation.xml b/P5/Source/Specs/interpretation.xml index 76fb98af6e..52aa24ada9 100644 --- a/P5/Source/Specs/interpretation.xml +++ b/P5/Source/Specs/interpretation.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/item.xml b/P5/Source/Specs/item.xml index 633fec8101..ee76e6984f 100644 --- a/P5/Source/Specs/item.xml +++ b/P5/Source/Specs/item.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/join.xml b/P5/Source/Specs/join.xml index 676e232121..3ea81278ff 100644 --- a/P5/Source/Specs/join.xml +++ b/P5/Source/Specs/join.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/joinGrp.xml b/P5/Source/Specs/joinGrp.xml index 78ec57a710..2473c6af84 100644 --- a/P5/Source/Specs/joinGrp.xml +++ b/P5/Source/Specs/joinGrp.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/keywords.xml b/P5/Source/Specs/keywords.xml index 3f6b7a752e..0aa4daec7b 100644 --- a/P5/Source/Specs/keywords.xml +++ b/P5/Source/Specs/keywords.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/kinesic.xml b/P5/Source/Specs/kinesic.xml index ca3627b025..b2ce01a9bc 100644 --- a/P5/Source/Specs/kinesic.xml +++ b/P5/Source/Specs/kinesic.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/l.xml b/P5/Source/Specs/l.xml index c8658bb7ff..6ce96e2937 100644 --- a/P5/Source/Specs/l.xml +++ b/P5/Source/Specs/l.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/label.xml b/P5/Source/Specs/label.xml index 46803c5e47..8fcffea4b6 100644 --- a/P5/Source/Specs/label.xml +++ b/P5/Source/Specs/label.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/lacunaEnd.xml b/P5/Source/Specs/lacunaEnd.xml index 03e6b06fee..c202f074a3 100644 --- a/P5/Source/Specs/lacunaEnd.xml +++ b/P5/Source/Specs/lacunaEnd.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/lacunaStart.xml b/P5/Source/Specs/lacunaStart.xml index 60c7eb588a..470c2eeda1 100644 --- a/P5/Source/Specs/lacunaStart.xml +++ b/P5/Source/Specs/lacunaStart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/lang.xml b/P5/Source/Specs/lang.xml index 4bccd75d18..fadc375705 100644 --- a/P5/Source/Specs/lang.xml +++ b/P5/Source/Specs/lang.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/langUsage.xml b/P5/Source/Specs/langUsage.xml index 877e6b75bf..c98816d9b6 100644 --- a/P5/Source/Specs/langUsage.xml +++ b/P5/Source/Specs/langUsage.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/language.xml b/P5/Source/Specs/language.xml index 2d3715148c..2f0b0a198a 100644 --- a/P5/Source/Specs/language.xml +++ b/P5/Source/Specs/language.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/layout.xml b/P5/Source/Specs/layout.xml index fd1697ebc1..10d211629b 100644 --- a/P5/Source/Specs/layout.xml +++ b/P5/Source/Specs/layout.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/layoutDesc.xml b/P5/Source/Specs/layoutDesc.xml index d0f0f79925..12404fd0ae 100644 --- a/P5/Source/Specs/layoutDesc.xml +++ b/P5/Source/Specs/layoutDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/lb.xml b/P5/Source/Specs/lb.xml index 729d8b207b..20d1d12c0b 100644 --- a/P5/Source/Specs/lb.xml +++ b/P5/Source/Specs/lb.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/lbl.xml b/P5/Source/Specs/lbl.xml index 00a5cbacc4..be29884354 100644 --- a/P5/Source/Specs/lbl.xml +++ b/P5/Source/Specs/lbl.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/leaf.xml b/P5/Source/Specs/leaf.xml index 0407e423af..ff5bc06eb4 100644 --- a/P5/Source/Specs/leaf.xml +++ b/P5/Source/Specs/leaf.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/lg.xml b/P5/Source/Specs/lg.xml index 904310e6a7..236f42407e 100644 --- a/P5/Source/Specs/lg.xml +++ b/P5/Source/Specs/lg.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/line.xml b/P5/Source/Specs/line.xml index fcc1831531..c964955051 100644 --- a/P5/Source/Specs/line.xml +++ b/P5/Source/Specs/line.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/link.xml b/P5/Source/Specs/link.xml index 52f5fa6ffa..53d6a029cb 100644 --- a/P5/Source/Specs/link.xml +++ b/P5/Source/Specs/link.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/linkGrp.xml b/P5/Source/Specs/linkGrp.xml index c9a3d8ea37..c69cba235e 100644 --- a/P5/Source/Specs/linkGrp.xml +++ b/P5/Source/Specs/linkGrp.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/list.xml b/P5/Source/Specs/list.xml index 0fc538af51..5f965639ae 100644 --- a/P5/Source/Specs/list.xml +++ b/P5/Source/Specs/list.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/listAnnotation.xml b/P5/Source/Specs/listAnnotation.xml index 4de68c2b20..4d0c6c9af4 100644 --- a/P5/Source/Specs/listAnnotation.xml +++ b/P5/Source/Specs/listAnnotation.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/listChange.xml b/P5/Source/Specs/listChange.xml index c9d3a0db37..f18dcc2f6a 100644 --- a/P5/Source/Specs/listChange.xml +++ b/P5/Source/Specs/listChange.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/listEvent.xml b/P5/Source/Specs/listEvent.xml index 2a9465b1ad..9b82a6b07d 100644 --- a/P5/Source/Specs/listEvent.xml +++ b/P5/Source/Specs/listEvent.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/listForest.xml b/P5/Source/Specs/listForest.xml index ba40ab4ba2..6aaafc3d48 100644 --- a/P5/Source/Specs/listForest.xml +++ b/P5/Source/Specs/listForest.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/listNym.xml b/P5/Source/Specs/listNym.xml index 3484bd324f..d4d5b53c20 100644 --- a/P5/Source/Specs/listNym.xml +++ b/P5/Source/Specs/listNym.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/listObject.xml b/P5/Source/Specs/listObject.xml index d5ae2075b1..3fba9dd5e0 100644 --- a/P5/Source/Specs/listObject.xml +++ b/P5/Source/Specs/listObject.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/listOrg.xml b/P5/Source/Specs/listOrg.xml index 7cde9a8430..35d0dc7d76 100644 --- a/P5/Source/Specs/listOrg.xml +++ b/P5/Source/Specs/listOrg.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/listPerson.xml b/P5/Source/Specs/listPerson.xml index 2901787068..fa5d589253 100644 --- a/P5/Source/Specs/listPerson.xml +++ b/P5/Source/Specs/listPerson.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/listPlace.xml b/P5/Source/Specs/listPlace.xml index 4fd1e6d0a4..67e5dca76a 100644 --- a/P5/Source/Specs/listPlace.xml +++ b/P5/Source/Specs/listPlace.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/listPrefixDef.xml b/P5/Source/Specs/listPrefixDef.xml index 23b467cedb..d62136ef0c 100644 --- a/P5/Source/Specs/listPrefixDef.xml +++ b/P5/Source/Specs/listPrefixDef.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/listRef.xml b/P5/Source/Specs/listRef.xml index 753935ac94..d4d888cee7 100644 --- a/P5/Source/Specs/listRef.xml +++ b/P5/Source/Specs/listRef.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/listRelation.xml b/P5/Source/Specs/listRelation.xml index 81e321d2bd..d1510dbe9f 100644 --- a/P5/Source/Specs/listRelation.xml +++ b/P5/Source/Specs/listRelation.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/listTranspose.xml b/P5/Source/Specs/listTranspose.xml index 35758e0cfc..53507ffd4f 100644 --- a/P5/Source/Specs/listTranspose.xml +++ b/P5/Source/Specs/listTranspose.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/listWit.xml b/P5/Source/Specs/listWit.xml index 71e25eedac..76bb5f9dcc 100644 --- a/P5/Source/Specs/listWit.xml +++ b/P5/Source/Specs/listWit.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/localProp.xml b/P5/Source/Specs/localProp.xml index 797ff3f99d..4bd08517ad 100644 --- a/P5/Source/Specs/localProp.xml +++ b/P5/Source/Specs/localProp.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/locus.xml b/P5/Source/Specs/locus.xml index 05438e07cd..811bb7a855 100644 --- a/P5/Source/Specs/locus.xml +++ b/P5/Source/Specs/locus.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/locusGrp.xml b/P5/Source/Specs/locusGrp.xml index 798aa873f1..7ddc2b7b61 100644 --- a/P5/Source/Specs/locusGrp.xml +++ b/P5/Source/Specs/locusGrp.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/m.xml b/P5/Source/Specs/m.xml index 1cb3c310e4..acf7cf9e38 100644 --- a/P5/Source/Specs/m.xml +++ b/P5/Source/Specs/m.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/macro.abContent.xml b/P5/Source/Specs/macro.abContent.xml index bbfc8461d2..334fcc3b12 100644 --- a/P5/Source/Specs/macro.abContent.xml +++ b/P5/Source/Specs/macro.abContent.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/macro.limitedContent.xml b/P5/Source/Specs/macro.limitedContent.xml index 204eb07cad..01874ed5ff 100644 --- a/P5/Source/Specs/macro.limitedContent.xml +++ b/P5/Source/Specs/macro.limitedContent.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/macro.paraContent.xml b/P5/Source/Specs/macro.paraContent.xml index 74a2771895..69a2a4f275 100644 --- a/P5/Source/Specs/macro.paraContent.xml +++ b/P5/Source/Specs/macro.paraContent.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/macro.phraseSeq.limited.xml b/P5/Source/Specs/macro.phraseSeq.limited.xml index dbb93623eb..efc9dc1dc8 100644 --- a/P5/Source/Specs/macro.phraseSeq.limited.xml +++ b/P5/Source/Specs/macro.phraseSeq.limited.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/macro.phraseSeq.xml b/P5/Source/Specs/macro.phraseSeq.xml index 39d2fe7767..ffb6fd08cb 100644 --- a/P5/Source/Specs/macro.phraseSeq.xml +++ b/P5/Source/Specs/macro.phraseSeq.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/macro.specialPara.xml b/P5/Source/Specs/macro.specialPara.xml index 7c589d54b2..931b331a37 100644 --- a/P5/Source/Specs/macro.specialPara.xml +++ b/P5/Source/Specs/macro.specialPara.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/macro.xtext.xml b/P5/Source/Specs/macro.xtext.xml index 70e2073584..e6eaeafc40 100644 --- a/P5/Source/Specs/macro.xtext.xml +++ b/P5/Source/Specs/macro.xtext.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/macroRef.xml b/P5/Source/Specs/macroRef.xml index de5698dce3..76eb78bb86 100644 --- a/P5/Source/Specs/macroRef.xml +++ b/P5/Source/Specs/macroRef.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/macroSpec.xml b/P5/Source/Specs/macroSpec.xml index 5ec54e85be..039a67c863 100644 --- a/P5/Source/Specs/macroSpec.xml +++ b/P5/Source/Specs/macroSpec.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/mapping.xml b/P5/Source/Specs/mapping.xml index ed766e8285..35c2b5c2a0 100644 --- a/P5/Source/Specs/mapping.xml +++ b/P5/Source/Specs/mapping.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/material.xml b/P5/Source/Specs/material.xml index 099a08c612..b874df85cb 100644 --- a/P5/Source/Specs/material.xml +++ b/P5/Source/Specs/material.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/measure.xml b/P5/Source/Specs/measure.xml index c28e598124..78f8d26b9a 100644 --- a/P5/Source/Specs/measure.xml +++ b/P5/Source/Specs/measure.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/measureGrp.xml b/P5/Source/Specs/measureGrp.xml index d5c9314e9a..764e9feb13 100644 --- a/P5/Source/Specs/measureGrp.xml +++ b/P5/Source/Specs/measureGrp.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/media.xml b/P5/Source/Specs/media.xml index ea14edfa18..79b94f79a9 100644 --- a/P5/Source/Specs/media.xml +++ b/P5/Source/Specs/media.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/memberOf.xml b/P5/Source/Specs/memberOf.xml index c10c9e3397..d65b7cc231 100644 --- a/P5/Source/Specs/memberOf.xml +++ b/P5/Source/Specs/memberOf.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/mentioned.xml b/P5/Source/Specs/mentioned.xml index a665e7e67c..102bff58cb 100644 --- a/P5/Source/Specs/mentioned.xml +++ b/P5/Source/Specs/mentioned.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/metDecl.xml b/P5/Source/Specs/metDecl.xml index a02918702c..67e137bd56 100644 --- a/P5/Source/Specs/metDecl.xml +++ b/P5/Source/Specs/metDecl.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/metSym.xml b/P5/Source/Specs/metSym.xml index b966ea0ece..deb5f32d8c 100644 --- a/P5/Source/Specs/metSym.xml +++ b/P5/Source/Specs/metSym.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/metamark.xml b/P5/Source/Specs/metamark.xml index 5f6f9935fa..69855f11a2 100644 --- a/P5/Source/Specs/metamark.xml +++ b/P5/Source/Specs/metamark.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/milestone.xml b/P5/Source/Specs/milestone.xml index d42a00d3be..1a70a9ee47 100644 --- a/P5/Source/Specs/milestone.xml +++ b/P5/Source/Specs/milestone.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/mod.xml b/P5/Source/Specs/mod.xml index 9d9a668621..98e3f4b768 100644 --- a/P5/Source/Specs/mod.xml +++ b/P5/Source/Specs/mod.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.addrPart.xml b/P5/Source/Specs/model.addrPart.xml index 7ba411f4c1..847584ab25 100644 --- a/P5/Source/Specs/model.addrPart.xml +++ b/P5/Source/Specs/model.addrPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.addressLike.xml b/P5/Source/Specs/model.addressLike.xml index b0cb56b841..f8634bf901 100644 --- a/P5/Source/Specs/model.addressLike.xml +++ b/P5/Source/Specs/model.addressLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.annotationLike.xml b/P5/Source/Specs/model.annotationLike.xml index 2f3b0648d6..ef3037faa7 100644 --- a/P5/Source/Specs/model.annotationLike.xml +++ b/P5/Source/Specs/model.annotationLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.annotationPart.body.xml b/P5/Source/Specs/model.annotationPart.body.xml index 4ed5fe24b5..da785f57b1 100644 --- a/P5/Source/Specs/model.annotationPart.body.xml +++ b/P5/Source/Specs/model.annotationPart.body.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.applicationLike.xml b/P5/Source/Specs/model.applicationLike.xml index 7ef827e172..5dd5316e47 100644 --- a/P5/Source/Specs/model.applicationLike.xml +++ b/P5/Source/Specs/model.applicationLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.availabilityPart.xml b/P5/Source/Specs/model.availabilityPart.xml index 6203ff3fe5..4075da2b94 100644 --- a/P5/Source/Specs/model.availabilityPart.xml +++ b/P5/Source/Specs/model.availabilityPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.biblLike.xml b/P5/Source/Specs/model.biblLike.xml index f153110052..0ef6a0ef2d 100644 --- a/P5/Source/Specs/model.biblLike.xml +++ b/P5/Source/Specs/model.biblLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.biblPart.xml b/P5/Source/Specs/model.biblPart.xml index fe071e78f6..8be9a7204b 100644 --- a/P5/Source/Specs/model.biblPart.xml +++ b/P5/Source/Specs/model.biblPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.castItemPart.xml b/P5/Source/Specs/model.castItemPart.xml index 4c12d14030..cd34fa265f 100644 --- a/P5/Source/Specs/model.castItemPart.xml +++ b/P5/Source/Specs/model.castItemPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.catDescPart.xml b/P5/Source/Specs/model.catDescPart.xml index 3caed96273..1fb3154064 100644 --- a/P5/Source/Specs/model.catDescPart.xml +++ b/P5/Source/Specs/model.catDescPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.certLike.xml b/P5/Source/Specs/model.certLike.xml index 7d3b910a1d..36cc33bc97 100644 --- a/P5/Source/Specs/model.certLike.xml +++ b/P5/Source/Specs/model.certLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.choicePart.xml b/P5/Source/Specs/model.choicePart.xml index e36a7706e4..e5751b9830 100644 --- a/P5/Source/Specs/model.choicePart.xml +++ b/P5/Source/Specs/model.choicePart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.common.xml b/P5/Source/Specs/model.common.xml index 3a8345c6a4..a280903eb3 100644 --- a/P5/Source/Specs/model.common.xml +++ b/P5/Source/Specs/model.common.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.contentPart.xml b/P5/Source/Specs/model.contentPart.xml index 6f6a58baa3..4f632739e1 100644 --- a/P5/Source/Specs/model.contentPart.xml +++ b/P5/Source/Specs/model.contentPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.correspActionPart.xml b/P5/Source/Specs/model.correspActionPart.xml index 5fce18c220..d21ce9fae8 100644 --- a/P5/Source/Specs/model.correspActionPart.xml +++ b/P5/Source/Specs/model.correspActionPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.correspContextPart.xml b/P5/Source/Specs/model.correspContextPart.xml index c5aa85f88e..571b58d3ec 100644 --- a/P5/Source/Specs/model.correspContextPart.xml +++ b/P5/Source/Specs/model.correspContextPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.correspDescPart.xml b/P5/Source/Specs/model.correspDescPart.xml index d9fec20b59..bc7361c439 100644 --- a/P5/Source/Specs/model.correspDescPart.xml +++ b/P5/Source/Specs/model.correspDescPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.dateLike.xml b/P5/Source/Specs/model.dateLike.xml index 6e90e0a624..cc5e64f093 100644 --- a/P5/Source/Specs/model.dateLike.xml +++ b/P5/Source/Specs/model.dateLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.descLike.xml b/P5/Source/Specs/model.descLike.xml index bc0b30bc33..2156d0fe50 100644 --- a/P5/Source/Specs/model.descLike.xml +++ b/P5/Source/Specs/model.descLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.describedResource.xml b/P5/Source/Specs/model.describedResource.xml index cd32d9dd5a..d23feec3a8 100644 --- a/P5/Source/Specs/model.describedResource.xml +++ b/P5/Source/Specs/model.describedResource.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.dimLike.xml b/P5/Source/Specs/model.dimLike.xml index 875460f33c..582c736f6e 100644 --- a/P5/Source/Specs/model.dimLike.xml +++ b/P5/Source/Specs/model.dimLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.div1Like.xml b/P5/Source/Specs/model.div1Like.xml index 8949d95c77..75ed9ca237 100644 --- a/P5/Source/Specs/model.div1Like.xml +++ b/P5/Source/Specs/model.div1Like.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.div2Like.xml b/P5/Source/Specs/model.div2Like.xml index 3305b2d5e5..f641e7d38a 100644 --- a/P5/Source/Specs/model.div2Like.xml +++ b/P5/Source/Specs/model.div2Like.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.div3Like.xml b/P5/Source/Specs/model.div3Like.xml index 0a7d22ae4d..170fe3dafe 100644 --- a/P5/Source/Specs/model.div3Like.xml +++ b/P5/Source/Specs/model.div3Like.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.div4Like.xml b/P5/Source/Specs/model.div4Like.xml index e1985e8b0e..21403a6383 100644 --- a/P5/Source/Specs/model.div4Like.xml +++ b/P5/Source/Specs/model.div4Like.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.div5Like.xml b/P5/Source/Specs/model.div5Like.xml index 9200705136..d1fbe5b62a 100644 --- a/P5/Source/Specs/model.div5Like.xml +++ b/P5/Source/Specs/model.div5Like.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.div6Like.xml b/P5/Source/Specs/model.div6Like.xml index 5cae7f5656..69c74d0dcd 100644 --- a/P5/Source/Specs/model.div6Like.xml +++ b/P5/Source/Specs/model.div6Like.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.div7Like.xml b/P5/Source/Specs/model.div7Like.xml index 819acfd4d5..0f3bb314bb 100644 --- a/P5/Source/Specs/model.div7Like.xml +++ b/P5/Source/Specs/model.div7Like.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.divBottom.xml b/P5/Source/Specs/model.divBottom.xml index 1fd3bc39ee..45ccdefce6 100644 --- a/P5/Source/Specs/model.divBottom.xml +++ b/P5/Source/Specs/model.divBottom.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.divBottomPart.xml b/P5/Source/Specs/model.divBottomPart.xml index 6175322295..be152a9006 100644 --- a/P5/Source/Specs/model.divBottomPart.xml +++ b/P5/Source/Specs/model.divBottomPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.divGenLike.xml b/P5/Source/Specs/model.divGenLike.xml index db05db0e83..a9374d82a2 100644 --- a/P5/Source/Specs/model.divGenLike.xml +++ b/P5/Source/Specs/model.divGenLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.divLike.xml b/P5/Source/Specs/model.divLike.xml index 5bb834f6f7..9b16663607 100644 --- a/P5/Source/Specs/model.divLike.xml +++ b/P5/Source/Specs/model.divLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.divPart.spoken.xml b/P5/Source/Specs/model.divPart.spoken.xml index 6b19d4ec7d..d27191ad49 100644 --- a/P5/Source/Specs/model.divPart.spoken.xml +++ b/P5/Source/Specs/model.divPart.spoken.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.divPart.xml b/P5/Source/Specs/model.divPart.xml index 85b74f98ec..a322a9803f 100644 --- a/P5/Source/Specs/model.divPart.xml +++ b/P5/Source/Specs/model.divPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.divTop.xml b/P5/Source/Specs/model.divTop.xml index 336d6e3c96..83ab4ca3e8 100644 --- a/P5/Source/Specs/model.divTop.xml +++ b/P5/Source/Specs/model.divTop.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.divTopPart.xml b/P5/Source/Specs/model.divTopPart.xml index 5038063ad9..30314ebd9c 100644 --- a/P5/Source/Specs/model.divTopPart.xml +++ b/P5/Source/Specs/model.divTopPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.divWrapper.xml b/P5/Source/Specs/model.divWrapper.xml index c8c0f0bbda..2844c3759e 100644 --- a/P5/Source/Specs/model.divWrapper.xml +++ b/P5/Source/Specs/model.divWrapper.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.editorialDeclPart.xml b/P5/Source/Specs/model.editorialDeclPart.xml index 14edb0c6ab..0d647afe9c 100644 --- a/P5/Source/Specs/model.editorialDeclPart.xml +++ b/P5/Source/Specs/model.editorialDeclPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.egLike.xml b/P5/Source/Specs/model.egLike.xml index 46fa32e6d9..de9279727e 100644 --- a/P5/Source/Specs/model.egLike.xml +++ b/P5/Source/Specs/model.egLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.emphLike.xml b/P5/Source/Specs/model.emphLike.xml index 78e6c32fc2..5f3d8d23ce 100644 --- a/P5/Source/Specs/model.emphLike.xml +++ b/P5/Source/Specs/model.emphLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.encodingDescPart.xml b/P5/Source/Specs/model.encodingDescPart.xml index 3f639ac7a3..4e81fb7352 100644 --- a/P5/Source/Specs/model.encodingDescPart.xml +++ b/P5/Source/Specs/model.encodingDescPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.entryLike.xml b/P5/Source/Specs/model.entryLike.xml index 8f4c9e27a6..f353dae501 100644 --- a/P5/Source/Specs/model.entryLike.xml +++ b/P5/Source/Specs/model.entryLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.entryPart.top.xml b/P5/Source/Specs/model.entryPart.top.xml index 2e27558c91..a876bd47d2 100644 --- a/P5/Source/Specs/model.entryPart.top.xml +++ b/P5/Source/Specs/model.entryPart.top.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.entryPart.xml b/P5/Source/Specs/model.entryPart.xml index 2f5d7a0022..175ba2e294 100644 --- a/P5/Source/Specs/model.entryPart.xml +++ b/P5/Source/Specs/model.entryPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.eventLike.xml b/P5/Source/Specs/model.eventLike.xml index 55feb20a45..e962a0cdae 100644 --- a/P5/Source/Specs/model.eventLike.xml +++ b/P5/Source/Specs/model.eventLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.featureVal.complex.xml b/P5/Source/Specs/model.featureVal.complex.xml index 19ec360806..c43ff4e8f6 100644 --- a/P5/Source/Specs/model.featureVal.complex.xml +++ b/P5/Source/Specs/model.featureVal.complex.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.featureVal.single.xml b/P5/Source/Specs/model.featureVal.single.xml index 7c6db41df8..a23dc83436 100644 --- a/P5/Source/Specs/model.featureVal.single.xml +++ b/P5/Source/Specs/model.featureVal.single.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.featureVal.xml b/P5/Source/Specs/model.featureVal.xml index c5b5aa8292..1c530fb21f 100644 --- a/P5/Source/Specs/model.featureVal.xml +++ b/P5/Source/Specs/model.featureVal.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.formPart.xml b/P5/Source/Specs/model.formPart.xml index 9c1ceb3753..f0c8385f9c 100644 --- a/P5/Source/Specs/model.formPart.xml +++ b/P5/Source/Specs/model.formPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.frontPart.drama.xml b/P5/Source/Specs/model.frontPart.drama.xml index ebc9920e22..6fb75c05d1 100644 --- a/P5/Source/Specs/model.frontPart.drama.xml +++ b/P5/Source/Specs/model.frontPart.drama.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.frontPart.xml b/P5/Source/Specs/model.frontPart.xml index e6ac36c010..350fd52d0d 100644 --- a/P5/Source/Specs/model.frontPart.xml +++ b/P5/Source/Specs/model.frontPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.fsdDeclPart.xml b/P5/Source/Specs/model.fsdDeclPart.xml index ca83d64783..57a8bbbed5 100644 --- a/P5/Source/Specs/model.fsdDeclPart.xml +++ b/P5/Source/Specs/model.fsdDeclPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.gLike.xml b/P5/Source/Specs/model.gLike.xml index 549c8e2f21..aae54d3233 100644 --- a/P5/Source/Specs/model.gLike.xml +++ b/P5/Source/Specs/model.gLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.global.edit.xml b/P5/Source/Specs/model.global.edit.xml index 6a30b24222..c17467604b 100644 --- a/P5/Source/Specs/model.global.edit.xml +++ b/P5/Source/Specs/model.global.edit.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.global.meta.xml b/P5/Source/Specs/model.global.meta.xml index ed80bdb7d1..8d4c514ac4 100644 --- a/P5/Source/Specs/model.global.meta.xml +++ b/P5/Source/Specs/model.global.meta.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.global.spoken.xml b/P5/Source/Specs/model.global.spoken.xml index 25bb62990f..e8046e67a1 100644 --- a/P5/Source/Specs/model.global.spoken.xml +++ b/P5/Source/Specs/model.global.spoken.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.global.xml b/P5/Source/Specs/model.global.xml index 5079a3498b..e6da0f33f7 100644 --- a/P5/Source/Specs/model.global.xml +++ b/P5/Source/Specs/model.global.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.gramPart.xml b/P5/Source/Specs/model.gramPart.xml index f3169f7f98..69878ff4c4 100644 --- a/P5/Source/Specs/model.gramPart.xml +++ b/P5/Source/Specs/model.gramPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.graphicLike.xml b/P5/Source/Specs/model.graphicLike.xml index 3d309f3344..3a75a3df6c 100644 --- a/P5/Source/Specs/model.graphicLike.xml +++ b/P5/Source/Specs/model.graphicLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.headLike.xml b/P5/Source/Specs/model.headLike.xml index e5a218c1b0..6d5eb489e4 100644 --- a/P5/Source/Specs/model.headLike.xml +++ b/P5/Source/Specs/model.headLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.hiLike.xml b/P5/Source/Specs/model.hiLike.xml index f2e4281555..c05ff7bc6e 100644 --- a/P5/Source/Specs/model.hiLike.xml +++ b/P5/Source/Specs/model.hiLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.highlighted.xml b/P5/Source/Specs/model.highlighted.xml index 033508e9e1..96664c4dc3 100644 --- a/P5/Source/Specs/model.highlighted.xml +++ b/P5/Source/Specs/model.highlighted.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.identEquiv.xml b/P5/Source/Specs/model.identEquiv.xml index c8b44db1cb..b455592949 100644 --- a/P5/Source/Specs/model.identEquiv.xml +++ b/P5/Source/Specs/model.identEquiv.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.identSynonyms.xml b/P5/Source/Specs/model.identSynonyms.xml index 79187a0b83..b5729c6eef 100644 --- a/P5/Source/Specs/model.identSynonyms.xml +++ b/P5/Source/Specs/model.identSynonyms.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.imprintPart.xml b/P5/Source/Specs/model.imprintPart.xml index 4323c9bd0d..ea2e52ba0a 100644 --- a/P5/Source/Specs/model.imprintPart.xml +++ b/P5/Source/Specs/model.imprintPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.inter.xml b/P5/Source/Specs/model.inter.xml index 8c701142d7..ce5d9d92af 100644 --- a/P5/Source/Specs/model.inter.xml +++ b/P5/Source/Specs/model.inter.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.lLike.xml b/P5/Source/Specs/model.lLike.xml index e576766768..89815c76a0 100644 --- a/P5/Source/Specs/model.lLike.xml +++ b/P5/Source/Specs/model.lLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.lPart.xml b/P5/Source/Specs/model.lPart.xml index f07c52d2ab..374a2e2cad 100644 --- a/P5/Source/Specs/model.lPart.xml +++ b/P5/Source/Specs/model.lPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.labelLike.xml b/P5/Source/Specs/model.labelLike.xml index d9a671bf18..940ae3ed7a 100644 --- a/P5/Source/Specs/model.labelLike.xml +++ b/P5/Source/Specs/model.labelLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.lexicalRefinement.xml b/P5/Source/Specs/model.lexicalRefinement.xml index 196cbedba9..64a5b5bbf3 100644 --- a/P5/Source/Specs/model.lexicalRefinement.xml +++ b/P5/Source/Specs/model.lexicalRefinement.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.limitedPhrase.xml b/P5/Source/Specs/model.limitedPhrase.xml index 2084f4fdc2..5b6c2ea0d5 100644 --- a/P5/Source/Specs/model.limitedPhrase.xml +++ b/P5/Source/Specs/model.limitedPhrase.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.linePart.xml b/P5/Source/Specs/model.linePart.xml index bf07c615c4..6595c90937 100644 --- a/P5/Source/Specs/model.linePart.xml +++ b/P5/Source/Specs/model.linePart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.listLike.xml b/P5/Source/Specs/model.listLike.xml index ca16d79da6..933ca683a1 100644 --- a/P5/Source/Specs/model.listLike.xml +++ b/P5/Source/Specs/model.listLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.measureLike.xml b/P5/Source/Specs/model.measureLike.xml index 63be2d9015..240dfd3398 100644 --- a/P5/Source/Specs/model.measureLike.xml +++ b/P5/Source/Specs/model.measureLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.milestoneLike.xml b/P5/Source/Specs/model.milestoneLike.xml index ef5da5015c..86aa7ea019 100644 --- a/P5/Source/Specs/model.milestoneLike.xml +++ b/P5/Source/Specs/model.milestoneLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.morphLike.xml b/P5/Source/Specs/model.morphLike.xml index b2f40ef7b2..01178cb65d 100644 --- a/P5/Source/Specs/model.morphLike.xml +++ b/P5/Source/Specs/model.morphLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.msItemPart.xml b/P5/Source/Specs/model.msItemPart.xml index a4b3c71bac..8252284491 100644 --- a/P5/Source/Specs/model.msItemPart.xml +++ b/P5/Source/Specs/model.msItemPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.msQuoteLike.xml b/P5/Source/Specs/model.msQuoteLike.xml index 9bb52bbbb5..ab9d6cc53a 100644 --- a/P5/Source/Specs/model.msQuoteLike.xml +++ b/P5/Source/Specs/model.msQuoteLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.nameLike.agent.xml b/P5/Source/Specs/model.nameLike.agent.xml index baa013cab5..31d40a42f8 100644 --- a/P5/Source/Specs/model.nameLike.agent.xml +++ b/P5/Source/Specs/model.nameLike.agent.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.nameLike.xml b/P5/Source/Specs/model.nameLike.xml index 9361febe84..794fef0801 100644 --- a/P5/Source/Specs/model.nameLike.xml +++ b/P5/Source/Specs/model.nameLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.noteLike.xml b/P5/Source/Specs/model.noteLike.xml index 5e0ae356bb..dc030037ae 100644 --- a/P5/Source/Specs/model.noteLike.xml +++ b/P5/Source/Specs/model.noteLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.oddDecl.xml b/P5/Source/Specs/model.oddDecl.xml index 6f90f2c7b6..4cfcea94d9 100644 --- a/P5/Source/Specs/model.oddDecl.xml +++ b/P5/Source/Specs/model.oddDecl.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.oddRef.xml b/P5/Source/Specs/model.oddRef.xml index 5071985070..b68930eb85 100644 --- a/P5/Source/Specs/model.oddRef.xml +++ b/P5/Source/Specs/model.oddRef.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.offsetLike.xml b/P5/Source/Specs/model.offsetLike.xml index a00aa1cfe9..9990330de2 100644 --- a/P5/Source/Specs/model.offsetLike.xml +++ b/P5/Source/Specs/model.offsetLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.orgPart.xml b/P5/Source/Specs/model.orgPart.xml index 0d97c3f0b5..27aa48a4dc 100644 --- a/P5/Source/Specs/model.orgPart.xml +++ b/P5/Source/Specs/model.orgPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.orgStateLike.xml b/P5/Source/Specs/model.orgStateLike.xml index 17cb8daf6c..0495ebe712 100644 --- a/P5/Source/Specs/model.orgStateLike.xml +++ b/P5/Source/Specs/model.orgStateLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.pLike.front.xml b/P5/Source/Specs/model.pLike.front.xml index 5ed337cc1a..58a2a3f4ab 100644 --- a/P5/Source/Specs/model.pLike.front.xml +++ b/P5/Source/Specs/model.pLike.front.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.pLike.xml b/P5/Source/Specs/model.pLike.xml index acc1d35a36..109954fa1b 100644 --- a/P5/Source/Specs/model.pLike.xml +++ b/P5/Source/Specs/model.pLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.pPart.data.xml b/P5/Source/Specs/model.pPart.data.xml index bdd8acf840..fee3950155 100644 --- a/P5/Source/Specs/model.pPart.data.xml +++ b/P5/Source/Specs/model.pPart.data.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.pPart.edit.xml b/P5/Source/Specs/model.pPart.edit.xml index f1906e500a..da05b24dc0 100644 --- a/P5/Source/Specs/model.pPart.edit.xml +++ b/P5/Source/Specs/model.pPart.edit.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.pPart.editorial.xml b/P5/Source/Specs/model.pPart.editorial.xml index f01cdcb0de..0cf401ddf3 100644 --- a/P5/Source/Specs/model.pPart.editorial.xml +++ b/P5/Source/Specs/model.pPart.editorial.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.pPart.msdesc.xml b/P5/Source/Specs/model.pPart.msdesc.xml index bf597ac580..ab4625ae0c 100644 --- a/P5/Source/Specs/model.pPart.msdesc.xml +++ b/P5/Source/Specs/model.pPart.msdesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.pPart.transcriptional.xml b/P5/Source/Specs/model.pPart.transcriptional.xml index 03ce7fbfe8..37389adddf 100644 --- a/P5/Source/Specs/model.pPart.transcriptional.xml +++ b/P5/Source/Specs/model.pPart.transcriptional.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.paraPart.xml b/P5/Source/Specs/model.paraPart.xml index b593f26b43..7242f4a202 100644 --- a/P5/Source/Specs/model.paraPart.xml +++ b/P5/Source/Specs/model.paraPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.persNamePart.xml b/P5/Source/Specs/model.persNamePart.xml index d1c52cbda0..4dcc7c8a7a 100644 --- a/P5/Source/Specs/model.persNamePart.xml +++ b/P5/Source/Specs/model.persNamePart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.persStateLike.xml b/P5/Source/Specs/model.persStateLike.xml index 3749a55a8b..7391695f01 100644 --- a/P5/Source/Specs/model.persStateLike.xml +++ b/P5/Source/Specs/model.persStateLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.personLike.xml b/P5/Source/Specs/model.personLike.xml index c5e0d466dc..0066b0c904 100644 --- a/P5/Source/Specs/model.personLike.xml +++ b/P5/Source/Specs/model.personLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.personPart.xml b/P5/Source/Specs/model.personPart.xml index 7a526ee0e0..6cbf0040e0 100644 --- a/P5/Source/Specs/model.personPart.xml +++ b/P5/Source/Specs/model.personPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.phrase.xml b/P5/Source/Specs/model.phrase.xml index 26e5a5c08b..8f370d52cd 100644 --- a/P5/Source/Specs/model.phrase.xml +++ b/P5/Source/Specs/model.phrase.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.phrase.xml.xml b/P5/Source/Specs/model.phrase.xml.xml index 5ab4b83846..01b2d63cd1 100644 --- a/P5/Source/Specs/model.phrase.xml.xml +++ b/P5/Source/Specs/model.phrase.xml.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.physDescPart.xml b/P5/Source/Specs/model.physDescPart.xml index c349770cbf..46328bbd62 100644 --- a/P5/Source/Specs/model.physDescPart.xml +++ b/P5/Source/Specs/model.physDescPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.placeLike.xml b/P5/Source/Specs/model.placeLike.xml index 3dc27043b9..833179ea38 100644 --- a/P5/Source/Specs/model.placeLike.xml +++ b/P5/Source/Specs/model.placeLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.placeNamePart.xml b/P5/Source/Specs/model.placeNamePart.xml index 6580f89223..19b1a60558 100644 --- a/P5/Source/Specs/model.placeNamePart.xml +++ b/P5/Source/Specs/model.placeNamePart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.placeStateLike.xml b/P5/Source/Specs/model.placeStateLike.xml index c5b08f4451..8929e9833b 100644 --- a/P5/Source/Specs/model.placeStateLike.xml +++ b/P5/Source/Specs/model.placeStateLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.profileDescPart.xml b/P5/Source/Specs/model.profileDescPart.xml index d744a63fb5..4cb0466848 100644 --- a/P5/Source/Specs/model.profileDescPart.xml +++ b/P5/Source/Specs/model.profileDescPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.ptrLike.form.xml b/P5/Source/Specs/model.ptrLike.form.xml index 7b597902b3..65d7347683 100644 --- a/P5/Source/Specs/model.ptrLike.form.xml +++ b/P5/Source/Specs/model.ptrLike.form.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.ptrLike.xml b/P5/Source/Specs/model.ptrLike.xml index 7a4d193a66..6e3281bb2f 100644 --- a/P5/Source/Specs/model.ptrLike.xml +++ b/P5/Source/Specs/model.ptrLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.publicationStmtPart.agency.xml b/P5/Source/Specs/model.publicationStmtPart.agency.xml index d955608d5c..babb6af6df 100644 --- a/P5/Source/Specs/model.publicationStmtPart.agency.xml +++ b/P5/Source/Specs/model.publicationStmtPart.agency.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.publicationStmtPart.detail.xml b/P5/Source/Specs/model.publicationStmtPart.detail.xml index 7392139710..795e20a135 100644 --- a/P5/Source/Specs/model.publicationStmtPart.detail.xml +++ b/P5/Source/Specs/model.publicationStmtPart.detail.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.quoteLike.xml b/P5/Source/Specs/model.quoteLike.xml index 588084aa88..26ee6d9b55 100644 --- a/P5/Source/Specs/model.quoteLike.xml +++ b/P5/Source/Specs/model.quoteLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.rdgLike.xml b/P5/Source/Specs/model.rdgLike.xml index de9acb1da0..980447303c 100644 --- a/P5/Source/Specs/model.rdgLike.xml +++ b/P5/Source/Specs/model.rdgLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.rdgPart.xml b/P5/Source/Specs/model.rdgPart.xml index 8f1f3bca3d..8fd44c5ee5 100644 --- a/P5/Source/Specs/model.rdgPart.xml +++ b/P5/Source/Specs/model.rdgPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.recordingPart.xml b/P5/Source/Specs/model.recordingPart.xml index 6d84cc11a5..e5c23ad431 100644 --- a/P5/Source/Specs/model.recordingPart.xml +++ b/P5/Source/Specs/model.recordingPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.resource.xml b/P5/Source/Specs/model.resource.xml index d0b5370a6f..8065ea297d 100644 --- a/P5/Source/Specs/model.resource.xml +++ b/P5/Source/Specs/model.resource.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.respLike.xml b/P5/Source/Specs/model.respLike.xml index b4beb3d50c..dd94ae118b 100644 --- a/P5/Source/Specs/model.respLike.xml +++ b/P5/Source/Specs/model.respLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.segLike.xml b/P5/Source/Specs/model.segLike.xml index d5601a7ef3..ab419a58db 100644 --- a/P5/Source/Specs/model.segLike.xml +++ b/P5/Source/Specs/model.segLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.settingPart.xml b/P5/Source/Specs/model.settingPart.xml index e1c86d8482..e9e477ab6e 100644 --- a/P5/Source/Specs/model.settingPart.xml +++ b/P5/Source/Specs/model.settingPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.sourceDescPart.xml b/P5/Source/Specs/model.sourceDescPart.xml index cd404efdf7..61ad43bb34 100644 --- a/P5/Source/Specs/model.sourceDescPart.xml +++ b/P5/Source/Specs/model.sourceDescPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.specDescLike.xml b/P5/Source/Specs/model.specDescLike.xml index b2d7d0f8b2..88f2ca4594 100644 --- a/P5/Source/Specs/model.specDescLike.xml +++ b/P5/Source/Specs/model.specDescLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.stageLike.xml b/P5/Source/Specs/model.stageLike.xml index 900ada33b0..3a81f417aa 100644 --- a/P5/Source/Specs/model.stageLike.xml +++ b/P5/Source/Specs/model.stageLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.standOffPart.xml b/P5/Source/Specs/model.standOffPart.xml index 11c0b46a9b..0a22ae432b 100644 --- a/P5/Source/Specs/model.standOffPart.xml +++ b/P5/Source/Specs/model.standOffPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.teiHeaderPart.xml b/P5/Source/Specs/model.teiHeaderPart.xml index 2991c623b8..f60280913e 100644 --- a/P5/Source/Specs/model.teiHeaderPart.xml +++ b/P5/Source/Specs/model.teiHeaderPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.textDescPart.xml b/P5/Source/Specs/model.textDescPart.xml index 78120f80d3..8b7162bdc1 100644 --- a/P5/Source/Specs/model.textDescPart.xml +++ b/P5/Source/Specs/model.textDescPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.titlepagePart.xml b/P5/Source/Specs/model.titlepagePart.xml index 4534cbe3b5..7ce67bed5c 100644 --- a/P5/Source/Specs/model.titlepagePart.xml +++ b/P5/Source/Specs/model.titlepagePart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.xml b/P5/Source/Specs/model.xml index 31fe8a749d..d09274f70f 100644 --- a/P5/Source/Specs/model.xml +++ b/P5/Source/Specs/model.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/modelGrp.xml b/P5/Source/Specs/modelGrp.xml index 7267ad191c..ca4e11a00d 100644 --- a/P5/Source/Specs/modelGrp.xml +++ b/P5/Source/Specs/modelGrp.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/modelSequence.xml b/P5/Source/Specs/modelSequence.xml index b76bfdfa97..51f31ed829 100644 --- a/P5/Source/Specs/modelSequence.xml +++ b/P5/Source/Specs/modelSequence.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/moduleRef.xml b/P5/Source/Specs/moduleRef.xml index 65d7c7be4d..80563bf2e3 100644 --- a/P5/Source/Specs/moduleRef.xml +++ b/P5/Source/Specs/moduleRef.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/moduleSpec.xml b/P5/Source/Specs/moduleSpec.xml index 433fb78ebc..49f5e2123d 100644 --- a/P5/Source/Specs/moduleSpec.xml +++ b/P5/Source/Specs/moduleSpec.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/monogr.xml b/P5/Source/Specs/monogr.xml index b14dc8c461..1e4599a9af 100644 --- a/P5/Source/Specs/monogr.xml +++ b/P5/Source/Specs/monogr.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/mood.xml b/P5/Source/Specs/mood.xml index 29b642a98e..628538c53c 100644 --- a/P5/Source/Specs/mood.xml +++ b/P5/Source/Specs/mood.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/move.xml b/P5/Source/Specs/move.xml index 56ba897744..41358c33cb 100644 --- a/P5/Source/Specs/move.xml +++ b/P5/Source/Specs/move.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/msContents.xml b/P5/Source/Specs/msContents.xml index 73c08df756..5ec0587876 100644 --- a/P5/Source/Specs/msContents.xml +++ b/P5/Source/Specs/msContents.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/msDesc.xml b/P5/Source/Specs/msDesc.xml index da8621afd2..fc7440d97b 100644 --- a/P5/Source/Specs/msDesc.xml +++ b/P5/Source/Specs/msDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/msFrag.xml b/P5/Source/Specs/msFrag.xml index ecf91cb7a6..b8a51b5106 100644 --- a/P5/Source/Specs/msFrag.xml +++ b/P5/Source/Specs/msFrag.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/msIdentifier.xml b/P5/Source/Specs/msIdentifier.xml index 508a745707..07414f1311 100644 --- a/P5/Source/Specs/msIdentifier.xml +++ b/P5/Source/Specs/msIdentifier.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/msItem.xml b/P5/Source/Specs/msItem.xml index a27ab89b98..431746ea67 100644 --- a/P5/Source/Specs/msItem.xml +++ b/P5/Source/Specs/msItem.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/msItemStruct.xml b/P5/Source/Specs/msItemStruct.xml index 98f6a26bb3..dfae4ef9ab 100644 --- a/P5/Source/Specs/msItemStruct.xml +++ b/P5/Source/Specs/msItemStruct.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/msName.xml b/P5/Source/Specs/msName.xml index eadcc467ee..38f6294ca4 100644 --- a/P5/Source/Specs/msName.xml +++ b/P5/Source/Specs/msName.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/msPart.xml b/P5/Source/Specs/msPart.xml index 26a51986f2..23492df635 100644 --- a/P5/Source/Specs/msPart.xml +++ b/P5/Source/Specs/msPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/musicNotation.xml b/P5/Source/Specs/musicNotation.xml index ab05959f7c..147bfda3c9 100644 --- a/P5/Source/Specs/musicNotation.xml +++ b/P5/Source/Specs/musicNotation.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/nameLink.xml b/P5/Source/Specs/nameLink.xml index e01796e8b1..8e1ddc0eba 100644 --- a/P5/Source/Specs/nameLink.xml +++ b/P5/Source/Specs/nameLink.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/namespace.xml b/P5/Source/Specs/namespace.xml index 910c90ea44..083902310e 100644 --- a/P5/Source/Specs/namespace.xml +++ b/P5/Source/Specs/namespace.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/node.xml b/P5/Source/Specs/node.xml index 9396e9c03b..838cecea70 100644 --- a/P5/Source/Specs/node.xml +++ b/P5/Source/Specs/node.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/normalization.xml b/P5/Source/Specs/normalization.xml index b97117e589..2d456d9ab9 100644 --- a/P5/Source/Specs/normalization.xml +++ b/P5/Source/Specs/normalization.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/notatedMusic.xml b/P5/Source/Specs/notatedMusic.xml index a9d62e1b9c..a3f3851d1a 100644 --- a/P5/Source/Specs/notatedMusic.xml +++ b/P5/Source/Specs/notatedMusic.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/note.xml b/P5/Source/Specs/note.xml index 0798511e1a..a880eafaae 100644 --- a/P5/Source/Specs/note.xml +++ b/P5/Source/Specs/note.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/notesStmt.xml b/P5/Source/Specs/notesStmt.xml index 4bbcd6a711..6b13620a81 100644 --- a/P5/Source/Specs/notesStmt.xml +++ b/P5/Source/Specs/notesStmt.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/num.xml b/P5/Source/Specs/num.xml index c0786c0062..06c2701efe 100644 --- a/P5/Source/Specs/num.xml +++ b/P5/Source/Specs/num.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/number.xml b/P5/Source/Specs/number.xml index 63446c5ead..cb387e9f25 100644 --- a/P5/Source/Specs/number.xml +++ b/P5/Source/Specs/number.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/numeric.xml b/P5/Source/Specs/numeric.xml index 61dd6cedce..fc94f495b9 100644 --- a/P5/Source/Specs/numeric.xml +++ b/P5/Source/Specs/numeric.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/nym.xml b/P5/Source/Specs/nym.xml index 5e49136cad..412bd2f4fa 100644 --- a/P5/Source/Specs/nym.xml +++ b/P5/Source/Specs/nym.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/oRef.xml b/P5/Source/Specs/oRef.xml index 5a5608fcdb..a386b7aeed 100644 --- a/P5/Source/Specs/oRef.xml +++ b/P5/Source/Specs/oRef.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/objectDesc.xml b/P5/Source/Specs/objectDesc.xml index f3367b7fe6..49058f9b60 100644 --- a/P5/Source/Specs/objectDesc.xml +++ b/P5/Source/Specs/objectDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/objectType.xml b/P5/Source/Specs/objectType.xml index e8db622519..6502e4177c 100644 --- a/P5/Source/Specs/objectType.xml +++ b/P5/Source/Specs/objectType.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/opener.xml b/P5/Source/Specs/opener.xml index ec89c7d444..ff5e5039da 100644 --- a/P5/Source/Specs/opener.xml +++ b/P5/Source/Specs/opener.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/org.xml b/P5/Source/Specs/org.xml index cccb50a29c..8c888d73c2 100644 --- a/P5/Source/Specs/org.xml +++ b/P5/Source/Specs/org.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/orig.xml b/P5/Source/Specs/orig.xml index 9c049b722f..d418ce08bd 100644 --- a/P5/Source/Specs/orig.xml +++ b/P5/Source/Specs/orig.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/origDate.xml b/P5/Source/Specs/origDate.xml index b91153b077..fe9da4b27f 100644 --- a/P5/Source/Specs/origDate.xml +++ b/P5/Source/Specs/origDate.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/orth.xml b/P5/Source/Specs/orth.xml index eb9172b5b7..8b9152649e 100644 --- a/P5/Source/Specs/orth.xml +++ b/P5/Source/Specs/orth.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/outputRendition.xml b/P5/Source/Specs/outputRendition.xml index 9bdaeffe86..d486a403ef 100644 --- a/P5/Source/Specs/outputRendition.xml +++ b/P5/Source/Specs/outputRendition.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/p.xml b/P5/Source/Specs/p.xml index e1b14d504b..fec443c9b3 100644 --- a/P5/Source/Specs/p.xml +++ b/P5/Source/Specs/p.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/pRef.xml b/P5/Source/Specs/pRef.xml index 68ea99eb49..2d35095af1 100644 --- a/P5/Source/Specs/pRef.xml +++ b/P5/Source/Specs/pRef.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/param.xml b/P5/Source/Specs/param.xml index 4eec04bfbd..6fed3ad2aa 100644 --- a/P5/Source/Specs/param.xml +++ b/P5/Source/Specs/param.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/paramList.xml b/P5/Source/Specs/paramList.xml index 1824691268..50ba643cc6 100644 --- a/P5/Source/Specs/paramList.xml +++ b/P5/Source/Specs/paramList.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/paramSpec.xml b/P5/Source/Specs/paramSpec.xml index 3e5f7daead..b32bb2ec4b 100644 --- a/P5/Source/Specs/paramSpec.xml +++ b/P5/Source/Specs/paramSpec.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/particDesc.xml b/P5/Source/Specs/particDesc.xml index 0e2b6df990..1cf432ee1a 100644 --- a/P5/Source/Specs/particDesc.xml +++ b/P5/Source/Specs/particDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/path.xml b/P5/Source/Specs/path.xml index bc6af60964..fd203e73b6 100644 --- a/P5/Source/Specs/path.xml +++ b/P5/Source/Specs/path.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/pause.xml b/P5/Source/Specs/pause.xml index 263008f955..541ed408b0 100644 --- a/P5/Source/Specs/pause.xml +++ b/P5/Source/Specs/pause.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/pb.xml b/P5/Source/Specs/pb.xml index e4b83b5881..c8dd57831c 100644 --- a/P5/Source/Specs/pb.xml +++ b/P5/Source/Specs/pb.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/pc.xml b/P5/Source/Specs/pc.xml index 84f5b40628..a1d5d8d54a 100644 --- a/P5/Source/Specs/pc.xml +++ b/P5/Source/Specs/pc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/per.xml b/P5/Source/Specs/per.xml index b4d9299b45..e56026742e 100644 --- a/P5/Source/Specs/per.xml +++ b/P5/Source/Specs/per.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/performance.xml b/P5/Source/Specs/performance.xml index 49bf2edd14..b35e13e3e3 100644 --- a/P5/Source/Specs/performance.xml +++ b/P5/Source/Specs/performance.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/person.xml b/P5/Source/Specs/person.xml index 64eef6dcd0..68f6af3ec5 100644 --- a/P5/Source/Specs/person.xml +++ b/P5/Source/Specs/person.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/personGrp.xml b/P5/Source/Specs/personGrp.xml index 5e1ec78f8d..5542cddf31 100644 --- a/P5/Source/Specs/personGrp.xml +++ b/P5/Source/Specs/personGrp.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/persona.xml b/P5/Source/Specs/persona.xml index 91a38e340a..39ee662a6a 100644 --- a/P5/Source/Specs/persona.xml +++ b/P5/Source/Specs/persona.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/phr.xml b/P5/Source/Specs/phr.xml index 83de82fd78..552ef58b2e 100644 --- a/P5/Source/Specs/phr.xml +++ b/P5/Source/Specs/phr.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/physDesc.xml b/P5/Source/Specs/physDesc.xml index 94685466e1..284df79517 100644 --- a/P5/Source/Specs/physDesc.xml +++ b/P5/Source/Specs/physDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/place.xml b/P5/Source/Specs/place.xml index ec9b883172..1ee05ebe3d 100644 --- a/P5/Source/Specs/place.xml +++ b/P5/Source/Specs/place.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/pos.xml b/P5/Source/Specs/pos.xml index ac2037416d..087aad96b1 100644 --- a/P5/Source/Specs/pos.xml +++ b/P5/Source/Specs/pos.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/postBox.xml b/P5/Source/Specs/postBox.xml index 4eb7b47412..e889aec6a3 100644 --- a/P5/Source/Specs/postBox.xml +++ b/P5/Source/Specs/postBox.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/postCode.xml b/P5/Source/Specs/postCode.xml index 8f6a3ec265..ec1382a9f7 100644 --- a/P5/Source/Specs/postCode.xml +++ b/P5/Source/Specs/postCode.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/postscript.xml b/P5/Source/Specs/postscript.xml index af2f6938f1..5ff28a29a5 100644 --- a/P5/Source/Specs/postscript.xml +++ b/P5/Source/Specs/postscript.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/prefixDef.xml b/P5/Source/Specs/prefixDef.xml index fce4879962..8291193a01 100644 --- a/P5/Source/Specs/prefixDef.xml +++ b/P5/Source/Specs/prefixDef.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/preparedness.xml b/P5/Source/Specs/preparedness.xml index 0b2189fc40..55741f0bf9 100644 --- a/P5/Source/Specs/preparedness.xml +++ b/P5/Source/Specs/preparedness.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/profileDesc.xml b/P5/Source/Specs/profileDesc.xml index fb11c233f7..171410364b 100644 --- a/P5/Source/Specs/profileDesc.xml +++ b/P5/Source/Specs/profileDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/projectDesc.xml b/P5/Source/Specs/projectDesc.xml index c8e50f0b22..56441a21dc 100644 --- a/P5/Source/Specs/projectDesc.xml +++ b/P5/Source/Specs/projectDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/prologue.xml b/P5/Source/Specs/prologue.xml index 947fdafd2d..abdfb7e041 100644 --- a/P5/Source/Specs/prologue.xml +++ b/P5/Source/Specs/prologue.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/pron.xml b/P5/Source/Specs/pron.xml index 7a7d2424ea..d5158e0914 100644 --- a/P5/Source/Specs/pron.xml +++ b/P5/Source/Specs/pron.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/ptr.xml b/P5/Source/Specs/ptr.xml index 2fb1bf6c13..d04b16f53b 100644 --- a/P5/Source/Specs/ptr.xml +++ b/P5/Source/Specs/ptr.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/pubPlace.xml b/P5/Source/Specs/pubPlace.xml index ca26d0a9c2..628111b22d 100644 --- a/P5/Source/Specs/pubPlace.xml +++ b/P5/Source/Specs/pubPlace.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/publicationStmt.xml b/P5/Source/Specs/publicationStmt.xml index 37df6d2352..d436a01003 100644 --- a/P5/Source/Specs/publicationStmt.xml +++ b/P5/Source/Specs/publicationStmt.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/punctuation.xml b/P5/Source/Specs/punctuation.xml index 93821375bc..bd3bd1012c 100644 --- a/P5/Source/Specs/punctuation.xml +++ b/P5/Source/Specs/punctuation.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/purpose.xml b/P5/Source/Specs/purpose.xml index 9aee9bb848..857fee64f9 100644 --- a/P5/Source/Specs/purpose.xml +++ b/P5/Source/Specs/purpose.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/q.xml b/P5/Source/Specs/q.xml index 99fd3d39b6..5e930fc498 100644 --- a/P5/Source/Specs/q.xml +++ b/P5/Source/Specs/q.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/quotation.xml b/P5/Source/Specs/quotation.xml index 1e124d2630..53241f45dc 100644 --- a/P5/Source/Specs/quotation.xml +++ b/P5/Source/Specs/quotation.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/quote.xml b/P5/Source/Specs/quote.xml index 36d43a000f..4efc5359d8 100644 --- a/P5/Source/Specs/quote.xml +++ b/P5/Source/Specs/quote.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/rb.xml b/P5/Source/Specs/rb.xml index cffe1d7e11..9a3b993fa2 100644 --- a/P5/Source/Specs/rb.xml +++ b/P5/Source/Specs/rb.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/rdg.xml b/P5/Source/Specs/rdg.xml index 519ed3a6a7..acdfe07712 100644 --- a/P5/Source/Specs/rdg.xml +++ b/P5/Source/Specs/rdg.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/rdgGrp.xml b/P5/Source/Specs/rdgGrp.xml index 487da66324..957e83f3a3 100644 --- a/P5/Source/Specs/rdgGrp.xml +++ b/P5/Source/Specs/rdgGrp.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/re.xml b/P5/Source/Specs/re.xml index 2fbcd74061..13dd822119 100644 --- a/P5/Source/Specs/re.xml +++ b/P5/Source/Specs/re.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/recording.xml b/P5/Source/Specs/recording.xml index c312a4eec9..7131f9ebc3 100644 --- a/P5/Source/Specs/recording.xml +++ b/P5/Source/Specs/recording.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/recordingStmt.xml b/P5/Source/Specs/recordingStmt.xml index 3161ca2d7b..01e0e456be 100644 --- a/P5/Source/Specs/recordingStmt.xml +++ b/P5/Source/Specs/recordingStmt.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/redo.xml b/P5/Source/Specs/redo.xml index 0da621df85..786a606ad2 100644 --- a/P5/Source/Specs/redo.xml +++ b/P5/Source/Specs/redo.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/ref.xml b/P5/Source/Specs/ref.xml index d769a34f05..736e9099d5 100644 --- a/P5/Source/Specs/ref.xml +++ b/P5/Source/Specs/ref.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/refState.xml b/P5/Source/Specs/refState.xml index b808c03b4b..b31c07a137 100644 --- a/P5/Source/Specs/refState.xml +++ b/P5/Source/Specs/refState.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/refsDecl.xml b/P5/Source/Specs/refsDecl.xml index 02befb6aa4..39a83d06d1 100644 --- a/P5/Source/Specs/refsDecl.xml +++ b/P5/Source/Specs/refsDecl.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/reg.xml b/P5/Source/Specs/reg.xml index 1429cc50c0..a9d7df25cb 100644 --- a/P5/Source/Specs/reg.xml +++ b/P5/Source/Specs/reg.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/relatedItem.xml b/P5/Source/Specs/relatedItem.xml index 7e1943e7cb..ef12cb724d 100644 --- a/P5/Source/Specs/relatedItem.xml +++ b/P5/Source/Specs/relatedItem.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/remarks.xml b/P5/Source/Specs/remarks.xml index eab9bc66a2..2fbbcb8413 100644 --- a/P5/Source/Specs/remarks.xml +++ b/P5/Source/Specs/remarks.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/rendition.xml b/P5/Source/Specs/rendition.xml index 7cadc85f19..b732b40468 100644 --- a/P5/Source/Specs/rendition.xml +++ b/P5/Source/Specs/rendition.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/repository.xml b/P5/Source/Specs/repository.xml index be1df64396..aa9dc49ac1 100644 --- a/P5/Source/Specs/repository.xml +++ b/P5/Source/Specs/repository.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/respStmt.xml b/P5/Source/Specs/respStmt.xml index 381e7fe5d0..7393d5c125 100644 --- a/P5/Source/Specs/respStmt.xml +++ b/P5/Source/Specs/respStmt.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/respons.xml b/P5/Source/Specs/respons.xml index 673454b07c..50a01c8c01 100644 --- a/P5/Source/Specs/respons.xml +++ b/P5/Source/Specs/respons.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/restore.xml b/P5/Source/Specs/restore.xml index 97b0704019..5856c337e1 100644 --- a/P5/Source/Specs/restore.xml +++ b/P5/Source/Specs/restore.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/retrace.xml b/P5/Source/Specs/retrace.xml index 7fe3ce2c36..88ff77aa5c 100644 --- a/P5/Source/Specs/retrace.xml +++ b/P5/Source/Specs/retrace.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/revisionDesc.xml b/P5/Source/Specs/revisionDesc.xml index 1f37dff596..811f8d6e56 100644 --- a/P5/Source/Specs/revisionDesc.xml +++ b/P5/Source/Specs/revisionDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/rhyme.xml b/P5/Source/Specs/rhyme.xml index a491783533..44c9cc969f 100644 --- a/P5/Source/Specs/rhyme.xml +++ b/P5/Source/Specs/rhyme.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/role.xml b/P5/Source/Specs/role.xml index a39524281a..672e332b30 100644 --- a/P5/Source/Specs/role.xml +++ b/P5/Source/Specs/role.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/roleDesc.xml b/P5/Source/Specs/roleDesc.xml index 4192d1f359..b91187f0c4 100644 --- a/P5/Source/Specs/roleDesc.xml +++ b/P5/Source/Specs/roleDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/roleName.xml b/P5/Source/Specs/roleName.xml index 9986b7c983..592f62728f 100644 --- a/P5/Source/Specs/roleName.xml +++ b/P5/Source/Specs/roleName.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/root.xml b/P5/Source/Specs/root.xml index 4e704653b2..d16d8672fd 100644 --- a/P5/Source/Specs/root.xml +++ b/P5/Source/Specs/root.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/row.xml b/P5/Source/Specs/row.xml index db4c1e60aa..33e81bc137 100644 --- a/P5/Source/Specs/row.xml +++ b/P5/Source/Specs/row.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/rs.xml b/P5/Source/Specs/rs.xml index 8e49a17a7e..7110efa93c 100644 --- a/P5/Source/Specs/rs.xml +++ b/P5/Source/Specs/rs.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/rt.xml b/P5/Source/Specs/rt.xml index 71c2cd09c8..c0b562a740 100644 --- a/P5/Source/Specs/rt.xml +++ b/P5/Source/Specs/rt.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/rubric.xml b/P5/Source/Specs/rubric.xml index 584606f6ef..f1bfae2e68 100644 --- a/P5/Source/Specs/rubric.xml +++ b/P5/Source/Specs/rubric.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/ruby.xml b/P5/Source/Specs/ruby.xml index db2f095b75..ed9ed1a697 100644 --- a/P5/Source/Specs/ruby.xml +++ b/P5/Source/Specs/ruby.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/s.xml b/P5/Source/Specs/s.xml index 2df1d961fc..9d434e3a6d 100644 --- a/P5/Source/Specs/s.xml +++ b/P5/Source/Specs/s.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/said.xml b/P5/Source/Specs/said.xml index 28f5966631..7424cb5186 100644 --- a/P5/Source/Specs/said.xml +++ b/P5/Source/Specs/said.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/salute.xml b/P5/Source/Specs/salute.xml index 5dedecdf62..eaef9619b3 100644 --- a/P5/Source/Specs/salute.xml +++ b/P5/Source/Specs/salute.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/samplingDecl.xml b/P5/Source/Specs/samplingDecl.xml index 005ece69e4..2ea1365ea5 100644 --- a/P5/Source/Specs/samplingDecl.xml +++ b/P5/Source/Specs/samplingDecl.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/schemaRef.xml b/P5/Source/Specs/schemaRef.xml index f5f622ddd2..94115574da 100644 --- a/P5/Source/Specs/schemaRef.xml +++ b/P5/Source/Specs/schemaRef.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/schemaSpec.xml b/P5/Source/Specs/schemaSpec.xml index 8389f70a1d..02ef7756cf 100644 --- a/P5/Source/Specs/schemaSpec.xml +++ b/P5/Source/Specs/schemaSpec.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/scriptDesc.xml b/P5/Source/Specs/scriptDesc.xml index ead5c2de53..1fe086068a 100644 --- a/P5/Source/Specs/scriptDesc.xml +++ b/P5/Source/Specs/scriptDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/scriptNote.xml b/P5/Source/Specs/scriptNote.xml index 52d4803d81..0fbbb277ed 100644 --- a/P5/Source/Specs/scriptNote.xml +++ b/P5/Source/Specs/scriptNote.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/scriptStmt.xml b/P5/Source/Specs/scriptStmt.xml index 4f97bc576e..44b57d0246 100644 --- a/P5/Source/Specs/scriptStmt.xml +++ b/P5/Source/Specs/scriptStmt.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/sealDesc.xml b/P5/Source/Specs/sealDesc.xml index bc6f609024..54905c1d4f 100644 --- a/P5/Source/Specs/sealDesc.xml +++ b/P5/Source/Specs/sealDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/secFol.xml b/P5/Source/Specs/secFol.xml index 1affd7b4cc..ca5f89e229 100644 --- a/P5/Source/Specs/secFol.xml +++ b/P5/Source/Specs/secFol.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/secl.xml b/P5/Source/Specs/secl.xml index 3518cb120c..f83a261942 100644 --- a/P5/Source/Specs/secl.xml +++ b/P5/Source/Specs/secl.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/seg.xml b/P5/Source/Specs/seg.xml index a82d6d40fe..4fc42aca7d 100644 --- a/P5/Source/Specs/seg.xml +++ b/P5/Source/Specs/seg.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/segmentation.xml b/P5/Source/Specs/segmentation.xml index fe76c035cf..148322e2d3 100644 --- a/P5/Source/Specs/segmentation.xml +++ b/P5/Source/Specs/segmentation.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/sense.xml b/P5/Source/Specs/sense.xml index 2c0991d7f7..dc7f3cbc5f 100644 --- a/P5/Source/Specs/sense.xml +++ b/P5/Source/Specs/sense.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/sequence.xml b/P5/Source/Specs/sequence.xml index bae4321128..6af5939002 100644 --- a/P5/Source/Specs/sequence.xml +++ b/P5/Source/Specs/sequence.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/series.xml b/P5/Source/Specs/series.xml index c2d2cda2f7..254b30b4a0 100644 --- a/P5/Source/Specs/series.xml +++ b/P5/Source/Specs/series.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/seriesStmt.xml b/P5/Source/Specs/seriesStmt.xml index 63698a8965..29e503c1ac 100644 --- a/P5/Source/Specs/seriesStmt.xml +++ b/P5/Source/Specs/seriesStmt.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/set.xml b/P5/Source/Specs/set.xml index 47cfbfa483..1b5d08b0d4 100644 --- a/P5/Source/Specs/set.xml +++ b/P5/Source/Specs/set.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/setting.xml b/P5/Source/Specs/setting.xml index 64c800e7b1..69a5956412 100644 --- a/P5/Source/Specs/setting.xml +++ b/P5/Source/Specs/setting.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/settingDesc.xml b/P5/Source/Specs/settingDesc.xml index ccf1394356..b02d9e58bc 100644 --- a/P5/Source/Specs/settingDesc.xml +++ b/P5/Source/Specs/settingDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/shift.xml b/P5/Source/Specs/shift.xml index 062aeb1ea7..b73d1fd52e 100644 --- a/P5/Source/Specs/shift.xml +++ b/P5/Source/Specs/shift.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/sic.xml b/P5/Source/Specs/sic.xml index 8231191379..83b7b9ace4 100644 --- a/P5/Source/Specs/sic.xml +++ b/P5/Source/Specs/sic.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/signatures.xml b/P5/Source/Specs/signatures.xml index da4fb74723..fbf77d5463 100644 --- a/P5/Source/Specs/signatures.xml +++ b/P5/Source/Specs/signatures.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/signed.xml b/P5/Source/Specs/signed.xml index c8a8f0cf93..f49316e0e0 100644 --- a/P5/Source/Specs/signed.xml +++ b/P5/Source/Specs/signed.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/soCalled.xml b/P5/Source/Specs/soCalled.xml index 2bbe980c98..0557283655 100644 --- a/P5/Source/Specs/soCalled.xml +++ b/P5/Source/Specs/soCalled.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/sound.xml b/P5/Source/Specs/sound.xml index 2c2ff455e8..44400d7a3b 100644 --- a/P5/Source/Specs/sound.xml +++ b/P5/Source/Specs/sound.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/source.xml b/P5/Source/Specs/source.xml index e947709180..07aab737f2 100644 --- a/P5/Source/Specs/source.xml +++ b/P5/Source/Specs/source.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/sourceDesc.xml b/P5/Source/Specs/sourceDesc.xml index c6cd51625e..cbf92ec831 100644 --- a/P5/Source/Specs/sourceDesc.xml +++ b/P5/Source/Specs/sourceDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/sourceDoc.xml b/P5/Source/Specs/sourceDoc.xml index e1139403c7..745cfaa0ab 100644 --- a/P5/Source/Specs/sourceDoc.xml +++ b/P5/Source/Specs/sourceDoc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/sp.xml b/P5/Source/Specs/sp.xml index 2ea0276125..304e05c17b 100644 --- a/P5/Source/Specs/sp.xml +++ b/P5/Source/Specs/sp.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/spGrp.xml b/P5/Source/Specs/spGrp.xml index e124a5f898..74189f9318 100644 --- a/P5/Source/Specs/spGrp.xml +++ b/P5/Source/Specs/spGrp.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/space.xml b/P5/Source/Specs/space.xml index 896094e328..0ccf08fe91 100644 --- a/P5/Source/Specs/space.xml +++ b/P5/Source/Specs/space.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/span.xml b/P5/Source/Specs/span.xml index a0d2d2a16c..e4db80bedc 100644 --- a/P5/Source/Specs/span.xml +++ b/P5/Source/Specs/span.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/spanGrp.xml b/P5/Source/Specs/spanGrp.xml index 3f86d96918..3aa3efa293 100644 --- a/P5/Source/Specs/spanGrp.xml +++ b/P5/Source/Specs/spanGrp.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/speaker.xml b/P5/Source/Specs/speaker.xml index 46d6ded603..97f236f2b0 100644 --- a/P5/Source/Specs/speaker.xml +++ b/P5/Source/Specs/speaker.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/specDesc.xml b/P5/Source/Specs/specDesc.xml index 35f3f5b1d6..1d56a95780 100644 --- a/P5/Source/Specs/specDesc.xml +++ b/P5/Source/Specs/specDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/specGrp.xml b/P5/Source/Specs/specGrp.xml index 961e3e511d..3759c4c82b 100644 --- a/P5/Source/Specs/specGrp.xml +++ b/P5/Source/Specs/specGrp.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/specGrpRef.xml b/P5/Source/Specs/specGrpRef.xml index 3e914fd8ae..3362ea72d9 100644 --- a/P5/Source/Specs/specGrpRef.xml +++ b/P5/Source/Specs/specGrpRef.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/specList.xml b/P5/Source/Specs/specList.xml index daf80dd6cd..c45e6dee1e 100644 --- a/P5/Source/Specs/specList.xml +++ b/P5/Source/Specs/specList.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/stage.xml b/P5/Source/Specs/stage.xml index decf7c7fdd..40b592d57c 100644 --- a/P5/Source/Specs/stage.xml +++ b/P5/Source/Specs/stage.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/standOff.xml b/P5/Source/Specs/standOff.xml index 2fd9814065..679102b394 100644 --- a/P5/Source/Specs/standOff.xml +++ b/P5/Source/Specs/standOff.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/street.xml b/P5/Source/Specs/street.xml index b5d8888ae2..7ad04f1d0f 100644 --- a/P5/Source/Specs/street.xml +++ b/P5/Source/Specs/street.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/stress.xml b/P5/Source/Specs/stress.xml index 2d59a1b40f..e00c87c03b 100644 --- a/P5/Source/Specs/stress.xml +++ b/P5/Source/Specs/stress.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/string.xml b/P5/Source/Specs/string.xml index e2cfb527f6..7706028626 100644 --- a/P5/Source/Specs/string.xml +++ b/P5/Source/Specs/string.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/styleDefDecl.xml b/P5/Source/Specs/styleDefDecl.xml index 62809d322c..6809677d58 100644 --- a/P5/Source/Specs/styleDefDecl.xml +++ b/P5/Source/Specs/styleDefDecl.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/subc.xml b/P5/Source/Specs/subc.xml index 08a1897755..5cc296352c 100644 --- a/P5/Source/Specs/subc.xml +++ b/P5/Source/Specs/subc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/subst.xml b/P5/Source/Specs/subst.xml index 5ae7359022..3e7b2cc575 100644 --- a/P5/Source/Specs/subst.xml +++ b/P5/Source/Specs/subst.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/substJoin.xml b/P5/Source/Specs/substJoin.xml index cc6101fd28..70c91a8138 100644 --- a/P5/Source/Specs/substJoin.xml +++ b/P5/Source/Specs/substJoin.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/summary.xml b/P5/Source/Specs/summary.xml index 658ee76957..6e4e6db0c7 100644 --- a/P5/Source/Specs/summary.xml +++ b/P5/Source/Specs/summary.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/superEntry.xml b/P5/Source/Specs/superEntry.xml index cab6f06146..65220fab2b 100644 --- a/P5/Source/Specs/superEntry.xml +++ b/P5/Source/Specs/superEntry.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/supplied.xml b/P5/Source/Specs/supplied.xml index 8ca8261e1b..029f9d2972 100644 --- a/P5/Source/Specs/supplied.xml +++ b/P5/Source/Specs/supplied.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/support.xml b/P5/Source/Specs/support.xml index 93018995bd..ac90f6d69a 100644 --- a/P5/Source/Specs/support.xml +++ b/P5/Source/Specs/support.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/supportDesc.xml b/P5/Source/Specs/supportDesc.xml index 6e7aa4bbdc..093c210637 100644 --- a/P5/Source/Specs/supportDesc.xml +++ b/P5/Source/Specs/supportDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/surface.xml b/P5/Source/Specs/surface.xml index e6c82216d8..1583ed2125 100644 --- a/P5/Source/Specs/surface.xml +++ b/P5/Source/Specs/surface.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/surfaceGrp.xml b/P5/Source/Specs/surfaceGrp.xml index a519536497..8ac125249e 100644 --- a/P5/Source/Specs/surfaceGrp.xml +++ b/P5/Source/Specs/surfaceGrp.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/surname.xml b/P5/Source/Specs/surname.xml index 77c00ff363..85d72fc318 100644 --- a/P5/Source/Specs/surname.xml +++ b/P5/Source/Specs/surname.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/surplus.xml b/P5/Source/Specs/surplus.xml index 0403081c34..dbbda6824d 100644 --- a/P5/Source/Specs/surplus.xml +++ b/P5/Source/Specs/surplus.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/surrogates.xml b/P5/Source/Specs/surrogates.xml index 569de8ced0..6623e368d4 100644 --- a/P5/Source/Specs/surrogates.xml +++ b/P5/Source/Specs/surrogates.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/syll.xml b/P5/Source/Specs/syll.xml index c9901c316c..0a1749ef40 100644 --- a/P5/Source/Specs/syll.xml +++ b/P5/Source/Specs/syll.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/symbol.xml b/P5/Source/Specs/symbol.xml index 2b0e10a514..43152cafe3 100644 --- a/P5/Source/Specs/symbol.xml +++ b/P5/Source/Specs/symbol.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/table.xml b/P5/Source/Specs/table.xml index 006341f9e3..9c14ffb87c 100644 --- a/P5/Source/Specs/table.xml +++ b/P5/Source/Specs/table.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/tag.xml b/P5/Source/Specs/tag.xml index 340052f631..2201b0c96f 100644 --- a/P5/Source/Specs/tag.xml +++ b/P5/Source/Specs/tag.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/tagUsage.xml b/P5/Source/Specs/tagUsage.xml index 8d30ff80e6..4997fe03ff 100644 --- a/P5/Source/Specs/tagUsage.xml +++ b/P5/Source/Specs/tagUsage.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/tagsDecl.xml b/P5/Source/Specs/tagsDecl.xml index 49c2afd87b..728167e24b 100644 --- a/P5/Source/Specs/tagsDecl.xml +++ b/P5/Source/Specs/tagsDecl.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/taxonomy.xml b/P5/Source/Specs/taxonomy.xml index d27bc30c31..089d2aaea4 100644 --- a/P5/Source/Specs/taxonomy.xml +++ b/P5/Source/Specs/taxonomy.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/tech.xml b/P5/Source/Specs/tech.xml index 01a8038611..da4991e0d0 100644 --- a/P5/Source/Specs/tech.xml +++ b/P5/Source/Specs/tech.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teiCorpus.xml b/P5/Source/Specs/teiCorpus.xml index 1977aac53f..20e651a103 100644 --- a/P5/Source/Specs/teiCorpus.xml +++ b/P5/Source/Specs/teiCorpus.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teiHeader.xml b/P5/Source/Specs/teiHeader.xml index 14b9998179..8c42224c5b 100644 --- a/P5/Source/Specs/teiHeader.xml +++ b/P5/Source/Specs/teiHeader.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.authority.xml b/P5/Source/Specs/teidata.authority.xml index 694dfb2c67..8a0d3456cc 100644 --- a/P5/Source/Specs/teidata.authority.xml +++ b/P5/Source/Specs/teidata.authority.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.certainty.xml b/P5/Source/Specs/teidata.certainty.xml index ad8777a528..6324feddb3 100644 --- a/P5/Source/Specs/teidata.certainty.xml +++ b/P5/Source/Specs/teidata.certainty.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.count.xml b/P5/Source/Specs/teidata.count.xml index 583ae1667d..2c9ac37563 100644 --- a/P5/Source/Specs/teidata.count.xml +++ b/P5/Source/Specs/teidata.count.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.duration.iso.xml b/P5/Source/Specs/teidata.duration.iso.xml index ff803c7ffa..84bd548c1a 100644 --- a/P5/Source/Specs/teidata.duration.iso.xml +++ b/P5/Source/Specs/teidata.duration.iso.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.duration.w3c.xml b/P5/Source/Specs/teidata.duration.w3c.xml index c712ae001e..ec001f8c1b 100644 --- a/P5/Source/Specs/teidata.duration.w3c.xml +++ b/P5/Source/Specs/teidata.duration.w3c.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.enumerated.xml b/P5/Source/Specs/teidata.enumerated.xml index 16c7fb66f3..9777ea1301 100644 --- a/P5/Source/Specs/teidata.enumerated.xml +++ b/P5/Source/Specs/teidata.enumerated.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.gender.xml b/P5/Source/Specs/teidata.gender.xml index fe83c77288..40ec63b81b 100644 --- a/P5/Source/Specs/teidata.gender.xml +++ b/P5/Source/Specs/teidata.gender.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.interval.xml b/P5/Source/Specs/teidata.interval.xml index ef3feb4eb6..8bb14ea458 100644 --- a/P5/Source/Specs/teidata.interval.xml +++ b/P5/Source/Specs/teidata.interval.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.key.xml b/P5/Source/Specs/teidata.key.xml index 1003467073..e82339f174 100644 --- a/P5/Source/Specs/teidata.key.xml +++ b/P5/Source/Specs/teidata.key.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.language.xml b/P5/Source/Specs/teidata.language.xml index ab68557d7a..e97a3fc5db 100644 --- a/P5/Source/Specs/teidata.language.xml +++ b/P5/Source/Specs/teidata.language.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.name.xml b/P5/Source/Specs/teidata.name.xml index 75c58adab1..38f7544005 100644 --- a/P5/Source/Specs/teidata.name.xml +++ b/P5/Source/Specs/teidata.name.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.namespace.xml b/P5/Source/Specs/teidata.namespace.xml index 6d0613bae5..14580b7d5c 100644 --- a/P5/Source/Specs/teidata.namespace.xml +++ b/P5/Source/Specs/teidata.namespace.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.namespaceOrName.xml b/P5/Source/Specs/teidata.namespaceOrName.xml index be04283789..5c597b5a5c 100644 --- a/P5/Source/Specs/teidata.namespaceOrName.xml +++ b/P5/Source/Specs/teidata.namespaceOrName.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.nullOrName.xml b/P5/Source/Specs/teidata.nullOrName.xml index 8b944dd974..d8165b539a 100644 --- a/P5/Source/Specs/teidata.nullOrName.xml +++ b/P5/Source/Specs/teidata.nullOrName.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.numeric.xml b/P5/Source/Specs/teidata.numeric.xml index 9015adcaa7..4649dd6f81 100644 --- a/P5/Source/Specs/teidata.numeric.xml +++ b/P5/Source/Specs/teidata.numeric.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.outputMeasurement.xml b/P5/Source/Specs/teidata.outputMeasurement.xml index 77679f1c10..a3bb6c9b45 100644 --- a/P5/Source/Specs/teidata.outputMeasurement.xml +++ b/P5/Source/Specs/teidata.outputMeasurement.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.pattern.xml b/P5/Source/Specs/teidata.pattern.xml index 2ed5381daf..d9c41dd206 100644 --- a/P5/Source/Specs/teidata.pattern.xml +++ b/P5/Source/Specs/teidata.pattern.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.point.xml b/P5/Source/Specs/teidata.point.xml index db8aec7bb0..34db58485b 100644 --- a/P5/Source/Specs/teidata.point.xml +++ b/P5/Source/Specs/teidata.point.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.pointer.xml b/P5/Source/Specs/teidata.pointer.xml index efb7aac0c7..9bb29db87f 100644 --- a/P5/Source/Specs/teidata.pointer.xml +++ b/P5/Source/Specs/teidata.pointer.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.prefix.xml b/P5/Source/Specs/teidata.prefix.xml index ff2f82d0ef..562c4ef6c3 100644 --- a/P5/Source/Specs/teidata.prefix.xml +++ b/P5/Source/Specs/teidata.prefix.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.probability.xml b/P5/Source/Specs/teidata.probability.xml index 55c99415a4..5267be894d 100644 --- a/P5/Source/Specs/teidata.probability.xml +++ b/P5/Source/Specs/teidata.probability.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.replacement.xml b/P5/Source/Specs/teidata.replacement.xml index d1f7ea7d08..a7b7e7ae38 100644 --- a/P5/Source/Specs/teidata.replacement.xml +++ b/P5/Source/Specs/teidata.replacement.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.sex.xml b/P5/Source/Specs/teidata.sex.xml index be3b96f47f..b57a7f5892 100644 --- a/P5/Source/Specs/teidata.sex.xml +++ b/P5/Source/Specs/teidata.sex.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.temporal.iso.xml b/P5/Source/Specs/teidata.temporal.iso.xml index 75964bf230..d395a42d73 100644 --- a/P5/Source/Specs/teidata.temporal.iso.xml +++ b/P5/Source/Specs/teidata.temporal.iso.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.temporal.w3c.xml b/P5/Source/Specs/teidata.temporal.w3c.xml index bcee15e3e6..dbd4117f63 100644 --- a/P5/Source/Specs/teidata.temporal.w3c.xml +++ b/P5/Source/Specs/teidata.temporal.w3c.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.temporal.working.xml b/P5/Source/Specs/teidata.temporal.working.xml index cf91487174..c154784dc2 100644 --- a/P5/Source/Specs/teidata.temporal.working.xml +++ b/P5/Source/Specs/teidata.temporal.working.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.text.xml b/P5/Source/Specs/teidata.text.xml index 6ba64e7103..49773b8e81 100644 --- a/P5/Source/Specs/teidata.text.xml +++ b/P5/Source/Specs/teidata.text.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.truthValue.xml b/P5/Source/Specs/teidata.truthValue.xml index f18af99ec4..55f8efcf02 100644 --- a/P5/Source/Specs/teidata.truthValue.xml +++ b/P5/Source/Specs/teidata.truthValue.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.unboundedCount.xml b/P5/Source/Specs/teidata.unboundedCount.xml index 13bc913069..cf07468081 100644 --- a/P5/Source/Specs/teidata.unboundedCount.xml +++ b/P5/Source/Specs/teidata.unboundedCount.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.version.xml b/P5/Source/Specs/teidata.version.xml index f5637c06ff..43519979cd 100644 --- a/P5/Source/Specs/teidata.version.xml +++ b/P5/Source/Specs/teidata.version.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.versionNumber.xml b/P5/Source/Specs/teidata.versionNumber.xml index 23227e843c..a4599773fd 100644 --- a/P5/Source/Specs/teidata.versionNumber.xml +++ b/P5/Source/Specs/teidata.versionNumber.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.word.xml b/P5/Source/Specs/teidata.word.xml index 9dd5f9390f..5c140b765d 100644 --- a/P5/Source/Specs/teidata.word.xml +++ b/P5/Source/Specs/teidata.word.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.xTruthValue.xml b/P5/Source/Specs/teidata.xTruthValue.xml index 70d229382d..7e5a6939a5 100644 --- a/P5/Source/Specs/teidata.xTruthValue.xml +++ b/P5/Source/Specs/teidata.xTruthValue.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.xmlName.xml b/P5/Source/Specs/teidata.xmlName.xml index dfb525e396..6f9df6ff7e 100644 --- a/P5/Source/Specs/teidata.xmlName.xml +++ b/P5/Source/Specs/teidata.xmlName.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.xpath.xml b/P5/Source/Specs/teidata.xpath.xml index 88fa12e371..8f83f1e816 100644 --- a/P5/Source/Specs/teidata.xpath.xml +++ b/P5/Source/Specs/teidata.xpath.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/term.xml b/P5/Source/Specs/term.xml index 8b205ffcbb..951ef269c0 100644 --- a/P5/Source/Specs/term.xml +++ b/P5/Source/Specs/term.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/text.xml b/P5/Source/Specs/text.xml index 45927be403..af7211b633 100644 --- a/P5/Source/Specs/text.xml +++ b/P5/Source/Specs/text.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/textClass.xml b/P5/Source/Specs/textClass.xml index 30b7879dbd..dd488c822e 100644 --- a/P5/Source/Specs/textClass.xml +++ b/P5/Source/Specs/textClass.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/textDesc.xml b/P5/Source/Specs/textDesc.xml index c9ebd1c9e3..0f2fc18b21 100644 --- a/P5/Source/Specs/textDesc.xml +++ b/P5/Source/Specs/textDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/textLang.xml b/P5/Source/Specs/textLang.xml index 2a5db7d142..479142edea 100644 --- a/P5/Source/Specs/textLang.xml +++ b/P5/Source/Specs/textLang.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/textNode.xml b/P5/Source/Specs/textNode.xml index b1880ce002..26a6f80f09 100644 --- a/P5/Source/Specs/textNode.xml +++ b/P5/Source/Specs/textNode.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/then.xml b/P5/Source/Specs/then.xml index ca933db3dd..d9eec07272 100644 --- a/P5/Source/Specs/then.xml +++ b/P5/Source/Specs/then.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/time.xml b/P5/Source/Specs/time.xml index 57f9fc9630..ad92fe1a22 100644 --- a/P5/Source/Specs/time.xml +++ b/P5/Source/Specs/time.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/timeline.xml b/P5/Source/Specs/timeline.xml index b707d5350e..f4e0f564c4 100644 --- a/P5/Source/Specs/timeline.xml +++ b/P5/Source/Specs/timeline.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/titlePage.xml b/P5/Source/Specs/titlePage.xml index 88e8be433d..c60811e765 100644 --- a/P5/Source/Specs/titlePage.xml +++ b/P5/Source/Specs/titlePage.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/titlePart.xml b/P5/Source/Specs/titlePart.xml index 0e97fa4922..1030d9c704 100644 --- a/P5/Source/Specs/titlePart.xml +++ b/P5/Source/Specs/titlePart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/titleStmt.xml b/P5/Source/Specs/titleStmt.xml index 783e8749e9..0455cf0e2b 100644 --- a/P5/Source/Specs/titleStmt.xml +++ b/P5/Source/Specs/titleStmt.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/tns.xml b/P5/Source/Specs/tns.xml index 8d292fd826..c616e4ad2f 100644 --- a/P5/Source/Specs/tns.xml +++ b/P5/Source/Specs/tns.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/trailer.xml b/P5/Source/Specs/trailer.xml index 7253cb814f..051734a859 100644 --- a/P5/Source/Specs/trailer.xml +++ b/P5/Source/Specs/trailer.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/transcriptionDesc.xml b/P5/Source/Specs/transcriptionDesc.xml index 618c60aff7..ea2b4a1bd2 100644 --- a/P5/Source/Specs/transcriptionDesc.xml +++ b/P5/Source/Specs/transcriptionDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/transpose.xml b/P5/Source/Specs/transpose.xml index 1329f0e8b2..2a00899d61 100644 --- a/P5/Source/Specs/transpose.xml +++ b/P5/Source/Specs/transpose.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/tree.xml b/P5/Source/Specs/tree.xml index a73125c013..fb60d50287 100644 --- a/P5/Source/Specs/tree.xml +++ b/P5/Source/Specs/tree.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/triangle.xml b/P5/Source/Specs/triangle.xml index 4b746544c5..0eeceaa997 100644 --- a/P5/Source/Specs/triangle.xml +++ b/P5/Source/Specs/triangle.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/typeDesc.xml b/P5/Source/Specs/typeDesc.xml index 49d5692505..d289209798 100644 --- a/P5/Source/Specs/typeDesc.xml +++ b/P5/Source/Specs/typeDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/typeNote.xml b/P5/Source/Specs/typeNote.xml index e5aea87904..311207cb6b 100644 --- a/P5/Source/Specs/typeNote.xml +++ b/P5/Source/Specs/typeNote.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/u.xml b/P5/Source/Specs/u.xml index 886455ea40..7996e27497 100644 --- a/P5/Source/Specs/u.xml +++ b/P5/Source/Specs/u.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/unclear.xml b/P5/Source/Specs/unclear.xml index 55d644b6b8..4fcf4d47bb 100644 --- a/P5/Source/Specs/unclear.xml +++ b/P5/Source/Specs/unclear.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/undo.xml b/P5/Source/Specs/undo.xml index 4b91a953e1..74fc3329f8 100644 --- a/P5/Source/Specs/undo.xml +++ b/P5/Source/Specs/undo.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/unicodeProp.xml b/P5/Source/Specs/unicodeProp.xml index f759a5680e..accd341a78 100644 --- a/P5/Source/Specs/unicodeProp.xml +++ b/P5/Source/Specs/unicodeProp.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/usg.xml b/P5/Source/Specs/usg.xml index e36a7412b3..6425b822f2 100644 --- a/P5/Source/Specs/usg.xml +++ b/P5/Source/Specs/usg.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/vAlt.xml b/P5/Source/Specs/vAlt.xml index c16caa0f54..76b8696dc2 100644 --- a/P5/Source/Specs/vAlt.xml +++ b/P5/Source/Specs/vAlt.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/vColl.xml b/P5/Source/Specs/vColl.xml index 14ad51e4fd..15aa41de5b 100644 --- a/P5/Source/Specs/vColl.xml +++ b/P5/Source/Specs/vColl.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/vDefault.xml b/P5/Source/Specs/vDefault.xml index c09ac7b8ba..9c23ea6d5a 100644 --- a/P5/Source/Specs/vDefault.xml +++ b/P5/Source/Specs/vDefault.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/vLabel.xml b/P5/Source/Specs/vLabel.xml index 9a3afe2e03..e36049018c 100644 --- a/P5/Source/Specs/vLabel.xml +++ b/P5/Source/Specs/vLabel.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/vMerge.xml b/P5/Source/Specs/vMerge.xml index fe135a153e..e262c194d8 100644 --- a/P5/Source/Specs/vMerge.xml +++ b/P5/Source/Specs/vMerge.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/vNot.xml b/P5/Source/Specs/vNot.xml index 5eb473360a..02e5ac4b1e 100644 --- a/P5/Source/Specs/vNot.xml +++ b/P5/Source/Specs/vNot.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/vRange.xml b/P5/Source/Specs/vRange.xml index 1e01198ad0..e2c29bad4a 100644 --- a/P5/Source/Specs/vRange.xml +++ b/P5/Source/Specs/vRange.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/val.xml b/P5/Source/Specs/val.xml index adc9675a45..983e06b0a8 100644 --- a/P5/Source/Specs/val.xml +++ b/P5/Source/Specs/val.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/valDesc.xml b/P5/Source/Specs/valDesc.xml index 65d03f1a79..a490d925fc 100644 --- a/P5/Source/Specs/valDesc.xml +++ b/P5/Source/Specs/valDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/valItem.xml b/P5/Source/Specs/valItem.xml index fab5338e0e..a2f0c381cd 100644 --- a/P5/Source/Specs/valItem.xml +++ b/P5/Source/Specs/valItem.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/valList.xml b/P5/Source/Specs/valList.xml index 5272421a27..bc3ab4a215 100644 --- a/P5/Source/Specs/valList.xml +++ b/P5/Source/Specs/valList.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/variantEncoding.xml b/P5/Source/Specs/variantEncoding.xml index 3648eedb2a..51d2616312 100644 --- a/P5/Source/Specs/variantEncoding.xml +++ b/P5/Source/Specs/variantEncoding.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/view.xml b/P5/Source/Specs/view.xml index 51ddf993cf..66a71671dd 100644 --- a/P5/Source/Specs/view.xml +++ b/P5/Source/Specs/view.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/vocal.xml b/P5/Source/Specs/vocal.xml index fc4d99cba3..6c2f8d053f 100644 --- a/P5/Source/Specs/vocal.xml +++ b/P5/Source/Specs/vocal.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/w.xml b/P5/Source/Specs/w.xml index 20e59131ae..b5ff2b7b1d 100644 --- a/P5/Source/Specs/w.xml +++ b/P5/Source/Specs/w.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/watermark.xml b/P5/Source/Specs/watermark.xml index 3c97949666..f2b8f6f3ce 100644 --- a/P5/Source/Specs/watermark.xml +++ b/P5/Source/Specs/watermark.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/when.xml b/P5/Source/Specs/when.xml index 859bc110cc..f109777b30 100644 --- a/P5/Source/Specs/when.xml +++ b/P5/Source/Specs/when.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/width.xml b/P5/Source/Specs/width.xml index 3613d9952e..610d9418c8 100644 --- a/P5/Source/Specs/width.xml +++ b/P5/Source/Specs/width.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/wit.xml b/P5/Source/Specs/wit.xml index 084fa3989d..9779c7992b 100644 --- a/P5/Source/Specs/wit.xml +++ b/P5/Source/Specs/wit.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/witDetail.xml b/P5/Source/Specs/witDetail.xml index c7687ab897..08983d6465 100644 --- a/P5/Source/Specs/witDetail.xml +++ b/P5/Source/Specs/witDetail.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/witEnd.xml b/P5/Source/Specs/witEnd.xml index 011b9967bc..19fce91bd6 100644 --- a/P5/Source/Specs/witEnd.xml +++ b/P5/Source/Specs/witEnd.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/witStart.xml b/P5/Source/Specs/witStart.xml index 37ef1986a6..8c42075373 100644 --- a/P5/Source/Specs/witStart.xml +++ b/P5/Source/Specs/witStart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/witness.xml b/P5/Source/Specs/witness.xml index 9d77bcea17..3e17e4ef15 100644 --- a/P5/Source/Specs/witness.xml +++ b/P5/Source/Specs/witness.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/writing.xml b/P5/Source/Specs/writing.xml index 6f526b0324..7bad204353 100644 --- a/P5/Source/Specs/writing.xml +++ b/P5/Source/Specs/writing.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/xenoData.xml b/P5/Source/Specs/xenoData.xml index dbb1df763b..3cb07cc48a 100644 --- a/P5/Source/Specs/xenoData.xml +++ b/P5/Source/Specs/xenoData.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/xr.xml b/P5/Source/Specs/xr.xml index 27fbc63be8..90be25df53 100644 --- a/P5/Source/Specs/xr.xml +++ b/P5/Source/Specs/xr.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/zone.xml b/P5/Source/Specs/zone.xml index 7adee8a624..cfa9bff22c 100644 --- a/P5/Source/Specs/zone.xml +++ b/P5/Source/Specs/zone.xml @@ -1,3 +1,4 @@ + From b27e85b63f3e2741d8813f7c55b6640e0c35eb8e Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Sat, 24 Feb 2024 16:46:48 -0500 Subject: [PATCH 032/127] Revert previous erroneous commit --- P5/Source/Guidelines/en/AB-About.xml | 1 - .../Guidelines/en/AI-AnalyticMechanisms.xml | 1 - .../Guidelines/en/CC-LanguageCorpora.xml | 1 - .../en/CE-CertaintyResponsibility.xml | 1 - .../en/CH-LanguagesCharacterSets.xml | 1 - P5/Source/Guidelines/en/CO-CoreElements.xml | 1 - P5/Source/Guidelines/en/COL-Colophon.xml | 1 - P5/Source/Guidelines/en/DEPRECATIONS.xml | 1 - .../Guidelines/en/DI-PrintDictionaries.xml | 1 - .../Guidelines/en/DR-PerformanceTexts.xml | 1 - .../Guidelines/en/DS-DefaultTextStructure.xml | 1 - P5/Source/Guidelines/en/Dedication.xml | 1 - .../Guidelines/en/FM1-IntroductoryNote.xml | 1 - .../Guidelines/en/FS-FeatureStructures.xml | 1 - .../en/FT-TablesFormulaeGraphics.xml | 1 - .../Guidelines/en/GD-GraphsNetworksTrees.xml | 1 - P5/Source/Guidelines/en/HD-Header.xml | 1 - .../en/MS-ManuscriptDescription.xml | 1 - P5/Source/Guidelines/en/ND-NamesDates.xml | 1 - .../Guidelines/en/NH-Non-hierarchical.xml | 1 - P5/Source/Guidelines/en/PARTIND.xml | 1 - P5/Source/Guidelines/en/PH-PrimarySources.xml | 1 - P5/Source/Guidelines/en/PrefatoryNote.xml | 1 - P5/Source/Guidelines/en/REF-ATTRIBUTES.xml | 1 - P5/Source/Guidelines/en/REF-CLASSES-ATTS.xml | 1 - P5/Source/Guidelines/en/REF-CLASSES-MODEL.xml | 1 - P5/Source/Guidelines/en/REF-ELEMENTS.xml | 1 - P5/Source/Guidelines/en/REF-MACROS.xml | 1 - .../en/SA-LinkingSegmentationAlignment.xml | 1 - .../Guidelines/en/SG-GentleIntroduction.xml | 1 - P5/Source/Guidelines/en/ST-Infrastructure.xml | 1 - .../Guidelines/en/TC-CriticalApparatus.xml | 1 - .../en/TD-DocumentationElements.xml | 1 - .../en/TS-TranscriptionsofSpeech.xml | 1 - P5/Source/Guidelines/en/TitlePageVerso.xml | 1 - P5/Source/Guidelines/en/USE.xml | 1 - P5/Source/Guidelines/en/VE-Verse.xml | 1 - .../en/WD-NonStandardCharacters.xml | 1 - P5/Source/Guidelines/fr/AB-About.xml | 839 +-- .../Guidelines/fr/AI-AnalyticMechanisms.xml | 1236 +--- P5/Source/Guidelines/fr/BIB-Bibliography.xml | 6370 +---------------- .../Guidelines/fr/CC-LanguageCorpora.xml | 1161 +-- .../fr/CE-CertaintyResponsibility.xml | 612 +- .../fr/CH-LanguagesCharacterSets.xml | 716 +- P5/Source/Guidelines/fr/CO-CoreElements.xml | 6014 +--------------- P5/Source/Guidelines/fr/COL-Colophon.xml | 39 +- .../Guidelines/fr/DI-PrintDictionaries.xml | 3107 +------- .../Guidelines/fr/DR-PerformanceTexts.xml | 1457 +--- .../Guidelines/fr/DS-DefaultTextStructure.xml | 1835 +---- P5/Source/Guidelines/fr/Dedication.xml | 25 +- .../Guidelines/fr/FM1-IntroductoryNote.xml | 302 +- .../Guidelines/fr/FS-FeatureStructures.xml | 2026 +----- .../fr/FT-TablesFormulaeGraphics.xml | 1106 +-- .../Guidelines/fr/GD-GraphsNetworksTrees.xml | 1500 +--- P5/Source/Guidelines/fr/HD-Header.xml | 1 - .../fr/MS-ManuscriptDescription.xml | 2572 +------ P5/Source/Guidelines/fr/ND-NamesDates.xml | 3060 +------- .../Guidelines/fr/NH-Non-hierarchical.xml | 825 +-- P5/Source/Guidelines/fr/PARTIND.xml | 11 +- P5/Source/Guidelines/fr/PH-PrimarySources.xml | 3060 +------- P5/Source/Guidelines/fr/PrefatoryNote.xml | 675 +- P5/Source/Guidelines/fr/REF-ATTRIBUTES.xml | 16 +- P5/Source/Guidelines/fr/REF-CLASSES-ATTS.xml | 17 +- P5/Source/Guidelines/fr/REF-CLASSES-MODEL.xml | 16 +- P5/Source/Guidelines/fr/REF-ELEMENTS.xml | 23 +- P5/Source/Guidelines/fr/REF-MACROS.xml | 16 +- .../fr/SA-LinkingSegmentationAlignment.xml | 3506 +-------- .../Guidelines/fr/SG-GentleIntroduction.xml | 1474 +--- P5/Source/Guidelines/fr/ST-Infrastructure.xml | 1426 +--- .../Guidelines/fr/TC-CriticalApparatus.xml | 1240 +--- .../fr/TD-DocumentationElements.xml | 2165 +----- .../fr/TS-TranscriptionsofSpeech.xml | 1471 +--- P5/Source/Guidelines/fr/TitlePageVerso.xml | 23 +- P5/Source/Guidelines/fr/USE.xml | 2316 +----- P5/Source/Guidelines/fr/VE-Verse.xml | 917 +-- .../fr/WD-NonStandardCharacters.xml | 1330 +--- P5/Source/Specs/TEI.xml | 1 - P5/Source/Specs/ab.xml | 1 - P5/Source/Specs/abbr.xml | 1 - P5/Source/Specs/abstract.xml | 1 - P5/Source/Specs/accMat.xml | 1 - P5/Source/Specs/actor.xml | 1 - P5/Source/Specs/add.xml | 1 - P5/Source/Specs/addName.xml | 1 - P5/Source/Specs/addSpan.xml | 1 - P5/Source/Specs/additional.xml | 1 - P5/Source/Specs/additions.xml | 1 - P5/Source/Specs/addrLine.xml | 1 - P5/Source/Specs/address.xml | 1 - P5/Source/Specs/adminInfo.xml | 1 - P5/Source/Specs/alt.xml | 1 - P5/Source/Specs/altGrp.xml | 1 - P5/Source/Specs/altIdent.xml | 1 - P5/Source/Specs/alternate.xml | 1 - P5/Source/Specs/am.xml | 1 - P5/Source/Specs/analytic.xml | 1 - P5/Source/Specs/anchor.xml | 1 - P5/Source/Specs/annotation.xml | 1 - P5/Source/Specs/annotationBlock.xml | 1 - P5/Source/Specs/anyElement.xml | 1 - P5/Source/Specs/app.xml | 1 - P5/Source/Specs/appInfo.xml | 1 - P5/Source/Specs/arc.xml | 1 - P5/Source/Specs/argument.xml | 1 - P5/Source/Specs/att.anchoring.xml | 1 - P5/Source/Specs/att.ascribed.directed.xml | 1 - P5/Source/Specs/att.ascribed.xml | 1 - P5/Source/Specs/att.breaking.xml | 1 - P5/Source/Specs/att.cReferencing.xml | 1 - P5/Source/Specs/att.calendarSystem.xml | 1 - P5/Source/Specs/att.canonical.xml | 1 - P5/Source/Specs/att.citeStructurePart.xml | 1 - P5/Source/Specs/att.citing.xml | 1 - P5/Source/Specs/att.combinable.xml | 1 - P5/Source/Specs/att.coordinated.xml | 1 - P5/Source/Specs/att.damaged.xml | 1 - P5/Source/Specs/att.datable.custom.xml | 1 - P5/Source/Specs/att.datable.iso.xml | 1 - P5/Source/Specs/att.datable.w3c.xml | 1 - P5/Source/Specs/att.datable.xml | 1 - P5/Source/Specs/att.datcat.xml | 1 - P5/Source/Specs/att.declarable.xml | 1 - P5/Source/Specs/att.declaring.xml | 1 - P5/Source/Specs/att.deprecated.xml | 1 - P5/Source/Specs/att.dimensions.xml | 1 - P5/Source/Specs/att.divLike.xml | 1 - P5/Source/Specs/att.docStatus.xml | 1 - P5/Source/Specs/att.duration.iso.xml | 1 - P5/Source/Specs/att.duration.w3c.xml | 1 - P5/Source/Specs/att.duration.xml | 1 - P5/Source/Specs/att.editLike.xml | 1 - P5/Source/Specs/att.edition.xml | 1 - P5/Source/Specs/att.enjamb.xml | 1 - P5/Source/Specs/att.entryLike.xml | 1 - P5/Source/Specs/att.formula.xml | 1 - P5/Source/Specs/att.fragmentable.xml | 1 - P5/Source/Specs/att.gaijiProp.xml | 1 - P5/Source/Specs/att.global.analytic.xml | 1 - P5/Source/Specs/att.global.change.xml | 1 - P5/Source/Specs/att.global.facs.xml | 1 - P5/Source/Specs/att.global.linking.xml | 1 - P5/Source/Specs/att.global.rendition.xml | 1 - P5/Source/Specs/att.global.responsibility.xml | 1 - P5/Source/Specs/att.global.source.xml | 1 - P5/Source/Specs/att.global.xml | 1 - P5/Source/Specs/att.handFeatures.xml | 1 - P5/Source/Specs/att.identified.xml | 1 - P5/Source/Specs/att.internetMedia.xml | 1 - P5/Source/Specs/att.interpLike.xml | 1 - P5/Source/Specs/att.lexicographic.xml | 1 - P5/Source/Specs/att.linguistic.xml | 1 - P5/Source/Specs/att.locatable.xml | 1 - P5/Source/Specs/att.measurement.xml | 1 - P5/Source/Specs/att.media.xml | 1 - P5/Source/Specs/att.metrical.xml | 1 - P5/Source/Specs/att.milestoneUnit.xml | 1 - P5/Source/Specs/att.msClass.xml | 1 - P5/Source/Specs/att.msExcerpt.xml | 1 - P5/Source/Specs/att.namespaceable.xml | 1 - P5/Source/Specs/att.naming.xml | 1 - P5/Source/Specs/att.notated.xml | 1 - P5/Source/Specs/att.partials.xml | 1 - P5/Source/Specs/att.patternReplacement.xml | 1 - P5/Source/Specs/att.personal.xml | 1 - P5/Source/Specs/att.placement.xml | 1 - P5/Source/Specs/att.pointing.group.xml | 1 - P5/Source/Specs/att.pointing.xml | 1 - P5/Source/Specs/att.predicate.xml | 1 - P5/Source/Specs/att.ranging.xml | 1 - P5/Source/Specs/att.rdgPart.xml | 1 - P5/Source/Specs/att.repeatable.xml | 1 - P5/Source/Specs/att.resourced.xml | 1 - P5/Source/Specs/att.scoping.xml | 1 - P5/Source/Specs/att.segLike.xml | 1 - P5/Source/Specs/att.sortable.xml | 1 - P5/Source/Specs/att.spanning.xml | 1 - P5/Source/Specs/att.styleDef.xml | 1 - P5/Source/Specs/att.tableDecoration.xml | 1 - P5/Source/Specs/att.textCritical.xml | 1 - P5/Source/Specs/att.timed.xml | 1 - P5/Source/Specs/att.transcriptional.xml | 1 - P5/Source/Specs/att.translatable.xml | 1 - P5/Source/Specs/att.typed.xml | 1 - P5/Source/Specs/att.witnessed.xml | 1 - P5/Source/Specs/att.written.xml | 1 - P5/Source/Specs/att.xml | 1 - P5/Source/Specs/attDef.xml | 1 - P5/Source/Specs/attList.xml | 1 - P5/Source/Specs/attRef.xml | 1 - P5/Source/Specs/authority.xml | 1 - P5/Source/Specs/availability.xml | 1 - P5/Source/Specs/back.xml | 1 - P5/Source/Specs/bibl.xml | 1 - P5/Source/Specs/biblFull.xml | 1 - P5/Source/Specs/biblScope.xml | 1 - P5/Source/Specs/biblStruct.xml | 1 - P5/Source/Specs/bicond.xml | 1 - P5/Source/Specs/binary.xml | 1 - P5/Source/Specs/binaryObject.xml | 1 - P5/Source/Specs/bindingDesc.xml | 1 - P5/Source/Specs/body.xml | 1 - P5/Source/Specs/broadcast.xml | 1 - P5/Source/Specs/byline.xml | 1 - P5/Source/Specs/c.xml | 1 - P5/Source/Specs/cRefPattern.xml | 1 - P5/Source/Specs/caesura.xml | 1 - P5/Source/Specs/calendar.xml | 1 - P5/Source/Specs/calendarDesc.xml | 1 - P5/Source/Specs/camera.xml | 1 - P5/Source/Specs/caption.xml | 1 - P5/Source/Specs/case.xml | 1 - P5/Source/Specs/castGroup.xml | 1 - P5/Source/Specs/castItem.xml | 1 - P5/Source/Specs/castList.xml | 1 - P5/Source/Specs/catDesc.xml | 1 - P5/Source/Specs/catRef.xml | 1 - P5/Source/Specs/catchwords.xml | 1 - P5/Source/Specs/category.xml | 1 - P5/Source/Specs/cb.xml | 1 - P5/Source/Specs/cell.xml | 1 - P5/Source/Specs/certainty.xml | 1 - P5/Source/Specs/channel.xml | 1 - P5/Source/Specs/char.xml | 1 - P5/Source/Specs/charDecl.xml | 1 - P5/Source/Specs/choice.xml | 1 - P5/Source/Specs/cit.xml | 1 - P5/Source/Specs/citeData.xml | 1 - P5/Source/Specs/citeStructure.xml | 1 - P5/Source/Specs/citedRange.xml | 1 - P5/Source/Specs/cl.xml | 1 - P5/Source/Specs/classCode.xml | 1 - P5/Source/Specs/classDecl.xml | 1 - P5/Source/Specs/classRef.xml | 1 - P5/Source/Specs/classSpec.xml | 1 - P5/Source/Specs/classes.xml | 1 - P5/Source/Specs/closer.xml | 1 - P5/Source/Specs/code.xml | 1 - P5/Source/Specs/collation.xml | 1 - P5/Source/Specs/collection.xml | 1 - P5/Source/Specs/colloc.xml | 1 - P5/Source/Specs/colophon.xml | 1 - P5/Source/Specs/cond.xml | 1 - P5/Source/Specs/condition.xml | 1 - P5/Source/Specs/constitution.xml | 1 - P5/Source/Specs/constraint.xml | 1 - P5/Source/Specs/constraintSpec.xml | 1 - P5/Source/Specs/content.xml | 1 - P5/Source/Specs/corr.xml | 1 - P5/Source/Specs/correction.xml | 1 - P5/Source/Specs/correspAction.xml | 1 - P5/Source/Specs/correspContext.xml | 1 - P5/Source/Specs/correspDesc.xml | 1 - P5/Source/Specs/custodialHist.xml | 1 - P5/Source/Specs/damageSpan.xml | 1 - P5/Source/Specs/dataFacet.xml | 1 - P5/Source/Specs/dataRef.xml | 1 - P5/Source/Specs/dataSpec.xml | 1 - P5/Source/Specs/datatype.xml | 1 - P5/Source/Specs/date.xml | 1 - P5/Source/Specs/dateline.xml | 1 - P5/Source/Specs/decoDesc.xml | 1 - P5/Source/Specs/decoNote.xml | 1 - P5/Source/Specs/def.xml | 1 - P5/Source/Specs/default.xml | 1 - P5/Source/Specs/defaultVal.xml | 1 - P5/Source/Specs/del.xml | 1 - P5/Source/Specs/delSpan.xml | 1 - P5/Source/Specs/depth.xml | 1 - P5/Source/Specs/derivation.xml | 1 - P5/Source/Specs/desc.xml | 1 - P5/Source/Specs/dictScrap.xml | 1 - P5/Source/Specs/dim.xml | 1 - P5/Source/Specs/dimensions.xml | 1 - P5/Source/Specs/distinct.xml | 1 - P5/Source/Specs/distributor.xml | 1 - P5/Source/Specs/div.xml | 1 - P5/Source/Specs/div1.xml | 1 - P5/Source/Specs/div2.xml | 1 - P5/Source/Specs/div3.xml | 1 - P5/Source/Specs/div4.xml | 1 - P5/Source/Specs/div5.xml | 1 - P5/Source/Specs/div6.xml | 1 - P5/Source/Specs/div7.xml | 1 - P5/Source/Specs/divGen.xml | 1 - P5/Source/Specs/docAuthor.xml | 1 - P5/Source/Specs/docDate.xml | 1 - P5/Source/Specs/docEdition.xml | 1 - P5/Source/Specs/docImprint.xml | 1 - P5/Source/Specs/docTitle.xml | 1 - P5/Source/Specs/domain.xml | 1 - P5/Source/Specs/eLeaf.xml | 1 - P5/Source/Specs/eTree.xml | 1 - P5/Source/Specs/edition.xml | 1 - P5/Source/Specs/editionStmt.xml | 1 - P5/Source/Specs/editorialDecl.xml | 1 - P5/Source/Specs/eg.xml | 1 - P5/Source/Specs/egXML.xml | 1 - P5/Source/Specs/elementRef.xml | 1 - P5/Source/Specs/elementSpec.xml | 1 - P5/Source/Specs/ellipsis.xml | 1 - P5/Source/Specs/email.xml | 1 - P5/Source/Specs/emph.xml | 1 - P5/Source/Specs/empty.xml | 1 - P5/Source/Specs/encodingDesc.xml | 1 - P5/Source/Specs/entry.xml | 1 - P5/Source/Specs/entryFree.xml | 1 - P5/Source/Specs/epigraph.xml | 1 - P5/Source/Specs/epilogue.xml | 1 - P5/Source/Specs/equipment.xml | 1 - P5/Source/Specs/equiv.xml | 1 - P5/Source/Specs/etym.xml | 1 - P5/Source/Specs/event.xml | 1 - P5/Source/Specs/eventName.xml | 1 - P5/Source/Specs/ex.xml | 1 - P5/Source/Specs/exemplum.xml | 1 - P5/Source/Specs/expan.xml | 1 - P5/Source/Specs/explicit.xml | 1 - P5/Source/Specs/extent.xml | 1 - P5/Source/Specs/f.xml | 1 - P5/Source/Specs/fDecl.xml | 1 - P5/Source/Specs/fDescr.xml | 1 - P5/Source/Specs/fLib.xml | 1 - P5/Source/Specs/facsimile.xml | 1 - P5/Source/Specs/factuality.xml | 1 - P5/Source/Specs/figDesc.xml | 1 - P5/Source/Specs/figure.xml | 1 - P5/Source/Specs/fileDesc.xml | 1 - P5/Source/Specs/filiation.xml | 1 - P5/Source/Specs/finalRubric.xml | 1 - P5/Source/Specs/floatingText.xml | 1 - P5/Source/Specs/foliation.xml | 1 - P5/Source/Specs/foreign.xml | 1 - P5/Source/Specs/forename.xml | 1 - P5/Source/Specs/forest.xml | 1 - P5/Source/Specs/form.xml | 1 - P5/Source/Specs/formula.xml | 1 - P5/Source/Specs/front.xml | 1 - P5/Source/Specs/fs.xml | 1 - P5/Source/Specs/fsConstraints.xml | 1 - P5/Source/Specs/fsDecl.xml | 1 - P5/Source/Specs/fsDescr.xml | 1 - P5/Source/Specs/fsdDecl.xml | 1 - P5/Source/Specs/fsdLink.xml | 1 - P5/Source/Specs/fvLib.xml | 1 - P5/Source/Specs/fw.xml | 1 - P5/Source/Specs/g.xml | 1 - P5/Source/Specs/gap.xml | 1 - P5/Source/Specs/gb.xml | 1 - P5/Source/Specs/gen.xml | 1 - P5/Source/Specs/genName.xml | 1 - P5/Source/Specs/geo.xml | 1 - P5/Source/Specs/geoDecl.xml | 1 - P5/Source/Specs/gi.xml | 1 - P5/Source/Specs/gloss.xml | 1 - P5/Source/Specs/glyph.xml | 1 - P5/Source/Specs/gram.xml | 1 - P5/Source/Specs/gramGrp.xml | 1 - P5/Source/Specs/graph.xml | 1 - P5/Source/Specs/graphic.xml | 1 - P5/Source/Specs/group.xml | 1 - P5/Source/Specs/handDesc.xml | 1 - P5/Source/Specs/handNote.xml | 1 - P5/Source/Specs/handNotes.xml | 1 - P5/Source/Specs/handShift.xml | 1 - P5/Source/Specs/head.xml | 1 - P5/Source/Specs/headItem.xml | 1 - P5/Source/Specs/headLabel.xml | 1 - P5/Source/Specs/height.xml | 1 - P5/Source/Specs/heraldry.xml | 1 - P5/Source/Specs/hi.xml | 1 - P5/Source/Specs/history.xml | 1 - P5/Source/Specs/hom.xml | 1 - P5/Source/Specs/hyph.xml | 1 - P5/Source/Specs/hyphenation.xml | 1 - P5/Source/Specs/iNode.xml | 1 - P5/Source/Specs/iType.xml | 1 - P5/Source/Specs/ident.xml | 1 - P5/Source/Specs/if.xml | 1 - P5/Source/Specs/iff.xml | 1 - P5/Source/Specs/imprimatur.xml | 1 - P5/Source/Specs/imprint.xml | 1 - P5/Source/Specs/incident.xml | 1 - P5/Source/Specs/incipit.xml | 1 - P5/Source/Specs/index.xml | 1 - P5/Source/Specs/institution.xml | 1 - P5/Source/Specs/interaction.xml | 1 - P5/Source/Specs/interp.xml | 1 - P5/Source/Specs/interpGrp.xml | 1 - P5/Source/Specs/interpretation.xml | 1 - P5/Source/Specs/item.xml | 1 - P5/Source/Specs/join.xml | 1 - P5/Source/Specs/joinGrp.xml | 1 - P5/Source/Specs/keywords.xml | 1 - P5/Source/Specs/kinesic.xml | 1 - P5/Source/Specs/l.xml | 1 - P5/Source/Specs/label.xml | 1 - P5/Source/Specs/lacunaEnd.xml | 1 - P5/Source/Specs/lacunaStart.xml | 1 - P5/Source/Specs/lang.xml | 1 - P5/Source/Specs/langUsage.xml | 1 - P5/Source/Specs/language.xml | 1 - P5/Source/Specs/layout.xml | 1 - P5/Source/Specs/layoutDesc.xml | 1 - P5/Source/Specs/lb.xml | 1 - P5/Source/Specs/lbl.xml | 1 - P5/Source/Specs/leaf.xml | 1 - P5/Source/Specs/lg.xml | 1 - P5/Source/Specs/line.xml | 1 - P5/Source/Specs/link.xml | 1 - P5/Source/Specs/linkGrp.xml | 1 - P5/Source/Specs/list.xml | 1 - P5/Source/Specs/listAnnotation.xml | 1 - P5/Source/Specs/listApp.xml | 1 - P5/Source/Specs/listBibl.xml | 1 - P5/Source/Specs/listChange.xml | 1 - P5/Source/Specs/listEvent.xml | 1 - P5/Source/Specs/listForest.xml | 1 - P5/Source/Specs/listNym.xml | 1 - P5/Source/Specs/listObject.xml | 1 - P5/Source/Specs/listOrg.xml | 1 - P5/Source/Specs/listPerson.xml | 1 - P5/Source/Specs/listPlace.xml | 1 - P5/Source/Specs/listPrefixDef.xml | 1 - P5/Source/Specs/listRef.xml | 1 - P5/Source/Specs/listRelation.xml | 1 - P5/Source/Specs/listTranspose.xml | 1 - P5/Source/Specs/listWit.xml | 1 - P5/Source/Specs/localProp.xml | 1 - P5/Source/Specs/locale.xml | 1 - P5/Source/Specs/locus.xml | 1 - P5/Source/Specs/locusGrp.xml | 1 - P5/Source/Specs/m.xml | 1 - P5/Source/Specs/macro.abContent.xml | 1 - P5/Source/Specs/macro.limitedContent.xml | 1 - P5/Source/Specs/macro.paraContent.xml | 1 - P5/Source/Specs/macro.phraseSeq.limited.xml | 1 - P5/Source/Specs/macro.phraseSeq.xml | 1 - P5/Source/Specs/macro.specialPara.xml | 1 - P5/Source/Specs/macro.xtext.xml | 1 - P5/Source/Specs/macroRef.xml | 1 - P5/Source/Specs/macroSpec.xml | 1 - P5/Source/Specs/mapping.xml | 1 - P5/Source/Specs/material.xml | 1 - P5/Source/Specs/measure.xml | 1 - P5/Source/Specs/measureGrp.xml | 1 - P5/Source/Specs/media.xml | 1 - P5/Source/Specs/memberOf.xml | 1 - P5/Source/Specs/mentioned.xml | 1 - P5/Source/Specs/metDecl.xml | 1 - P5/Source/Specs/metSym.xml | 1 - P5/Source/Specs/metamark.xml | 1 - P5/Source/Specs/milestone.xml | 1 - P5/Source/Specs/mod.xml | 1 - P5/Source/Specs/model.addrPart.xml | 1 - P5/Source/Specs/model.addressLike.xml | 1 - P5/Source/Specs/model.annotationLike.xml | 1 - P5/Source/Specs/model.annotationPart.body.xml | 1 - P5/Source/Specs/model.applicationLike.xml | 1 - P5/Source/Specs/model.availabilityPart.xml | 1 - P5/Source/Specs/model.biblLike.xml | 1 - P5/Source/Specs/model.biblPart.xml | 1 - P5/Source/Specs/model.castItemPart.xml | 1 - P5/Source/Specs/model.catDescPart.xml | 1 - P5/Source/Specs/model.certLike.xml | 1 - P5/Source/Specs/model.choicePart.xml | 1 - P5/Source/Specs/model.common.xml | 1 - P5/Source/Specs/model.contentPart.xml | 1 - P5/Source/Specs/model.correspActionPart.xml | 1 - P5/Source/Specs/model.correspContextPart.xml | 1 - P5/Source/Specs/model.correspDescPart.xml | 1 - P5/Source/Specs/model.dateLike.xml | 1 - P5/Source/Specs/model.descLike.xml | 1 - P5/Source/Specs/model.describedResource.xml | 1 - P5/Source/Specs/model.dimLike.xml | 1 - P5/Source/Specs/model.div1Like.xml | 1 - P5/Source/Specs/model.div2Like.xml | 1 - P5/Source/Specs/model.div3Like.xml | 1 - P5/Source/Specs/model.div4Like.xml | 1 - P5/Source/Specs/model.div5Like.xml | 1 - P5/Source/Specs/model.div6Like.xml | 1 - P5/Source/Specs/model.div7Like.xml | 1 - P5/Source/Specs/model.divBottom.xml | 1 - P5/Source/Specs/model.divBottomPart.xml | 1 - P5/Source/Specs/model.divGenLike.xml | 1 - P5/Source/Specs/model.divLike.xml | 1 - P5/Source/Specs/model.divPart.spoken.xml | 1 - P5/Source/Specs/model.divPart.xml | 1 - P5/Source/Specs/model.divTop.xml | 1 - P5/Source/Specs/model.divTopPart.xml | 1 - P5/Source/Specs/model.divWrapper.xml | 1 - P5/Source/Specs/model.editorialDeclPart.xml | 1 - P5/Source/Specs/model.egLike.xml | 1 - P5/Source/Specs/model.emphLike.xml | 1 - P5/Source/Specs/model.encodingDescPart.xml | 1 - P5/Source/Specs/model.entryLike.xml | 1 - P5/Source/Specs/model.entryPart.top.xml | 1 - P5/Source/Specs/model.entryPart.xml | 1 - P5/Source/Specs/model.eventLike.xml | 1 - P5/Source/Specs/model.featureVal.complex.xml | 1 - P5/Source/Specs/model.featureVal.single.xml | 1 - P5/Source/Specs/model.featureVal.xml | 1 - P5/Source/Specs/model.formPart.xml | 1 - P5/Source/Specs/model.frontPart.drama.xml | 1 - P5/Source/Specs/model.frontPart.xml | 1 - P5/Source/Specs/model.fsdDeclPart.xml | 1 - P5/Source/Specs/model.gLike.xml | 1 - P5/Source/Specs/model.global.edit.xml | 1 - P5/Source/Specs/model.global.meta.xml | 1 - P5/Source/Specs/model.global.spoken.xml | 1 - P5/Source/Specs/model.global.xml | 1 - P5/Source/Specs/model.gramPart.xml | 1 - P5/Source/Specs/model.graphicLike.xml | 1 - P5/Source/Specs/model.headLike.xml | 1 - P5/Source/Specs/model.hiLike.xml | 1 - P5/Source/Specs/model.highlighted.xml | 1 - P5/Source/Specs/model.identEquiv.xml | 1 - P5/Source/Specs/model.identSynonyms.xml | 1 - P5/Source/Specs/model.imprintPart.xml | 1 - P5/Source/Specs/model.inter.xml | 1 - P5/Source/Specs/model.lLike.xml | 1 - P5/Source/Specs/model.lPart.xml | 1 - P5/Source/Specs/model.labelLike.xml | 1 - P5/Source/Specs/model.lexicalRefinement.xml | 1 - P5/Source/Specs/model.limitedPhrase.xml | 1 - P5/Source/Specs/model.linePart.xml | 1 - P5/Source/Specs/model.listLike.xml | 1 - P5/Source/Specs/model.measureLike.xml | 1 - P5/Source/Specs/model.milestoneLike.xml | 1 - P5/Source/Specs/model.morphLike.xml | 1 - P5/Source/Specs/model.msItemPart.xml | 1 - P5/Source/Specs/model.msQuoteLike.xml | 1 - P5/Source/Specs/model.nameLike.agent.xml | 1 - P5/Source/Specs/model.nameLike.xml | 1 - P5/Source/Specs/model.noteLike.xml | 1 - P5/Source/Specs/model.oddDecl.xml | 1 - P5/Source/Specs/model.oddRef.xml | 1 - P5/Source/Specs/model.offsetLike.xml | 1 - P5/Source/Specs/model.orgPart.xml | 1 - P5/Source/Specs/model.orgStateLike.xml | 1 - P5/Source/Specs/model.pLike.front.xml | 1 - P5/Source/Specs/model.pLike.xml | 1 - P5/Source/Specs/model.pPart.data.xml | 1 - P5/Source/Specs/model.pPart.edit.xml | 1 - P5/Source/Specs/model.pPart.editorial.xml | 1 - P5/Source/Specs/model.pPart.msdesc.xml | 1 - .../Specs/model.pPart.transcriptional.xml | 1 - P5/Source/Specs/model.paraPart.xml | 1 - P5/Source/Specs/model.persNamePart.xml | 1 - P5/Source/Specs/model.persStateLike.xml | 1 - P5/Source/Specs/model.personLike.xml | 1 - P5/Source/Specs/model.personPart.xml | 1 - P5/Source/Specs/model.phrase.xml | 1 - P5/Source/Specs/model.phrase.xml.xml | 1 - P5/Source/Specs/model.physDescPart.xml | 1 - P5/Source/Specs/model.placeLike.xml | 1 - P5/Source/Specs/model.placeNamePart.xml | 1 - P5/Source/Specs/model.placeStateLike.xml | 1 - P5/Source/Specs/model.profileDescPart.xml | 1 - P5/Source/Specs/model.ptrLike.form.xml | 1 - P5/Source/Specs/model.ptrLike.xml | 1 - .../model.publicationStmtPart.agency.xml | 1 - .../model.publicationStmtPart.detail.xml | 1 - P5/Source/Specs/model.quoteLike.xml | 1 - P5/Source/Specs/model.rdgLike.xml | 1 - P5/Source/Specs/model.rdgPart.xml | 1 - P5/Source/Specs/model.recordingPart.xml | 1 - P5/Source/Specs/model.resource.xml | 1 - P5/Source/Specs/model.respLike.xml | 1 - P5/Source/Specs/model.segLike.xml | 1 - P5/Source/Specs/model.settingPart.xml | 1 - P5/Source/Specs/model.sourceDescPart.xml | 1 - P5/Source/Specs/model.specDescLike.xml | 1 - P5/Source/Specs/model.stageLike.xml | 1 - P5/Source/Specs/model.standOffPart.xml | 1 - P5/Source/Specs/model.teiHeaderPart.xml | 1 - P5/Source/Specs/model.textDescPart.xml | 1 - P5/Source/Specs/model.titlepagePart.xml | 1 - P5/Source/Specs/model.xml | 1 - P5/Source/Specs/modelGrp.xml | 1 - P5/Source/Specs/modelSequence.xml | 1 - P5/Source/Specs/moduleRef.xml | 1 - P5/Source/Specs/moduleSpec.xml | 1 - P5/Source/Specs/monogr.xml | 1 - P5/Source/Specs/mood.xml | 1 - P5/Source/Specs/move.xml | 1 - P5/Source/Specs/msContents.xml | 1 - P5/Source/Specs/msDesc.xml | 1 - P5/Source/Specs/msFrag.xml | 1 - P5/Source/Specs/msIdentifier.xml | 1 - P5/Source/Specs/msItem.xml | 1 - P5/Source/Specs/msItemStruct.xml | 1 - P5/Source/Specs/msName.xml | 1 - P5/Source/Specs/msPart.xml | 1 - P5/Source/Specs/musicNotation.xml | 1 - P5/Source/Specs/nameLink.xml | 1 - P5/Source/Specs/namespace.xml | 1 - P5/Source/Specs/node.xml | 1 - P5/Source/Specs/normalization.xml | 1 - P5/Source/Specs/notatedMusic.xml | 1 - P5/Source/Specs/note.xml | 1 - P5/Source/Specs/notesStmt.xml | 1 - P5/Source/Specs/num.xml | 1 - P5/Source/Specs/number.xml | 1 - P5/Source/Specs/numeric.xml | 1 - P5/Source/Specs/nym.xml | 1 - P5/Source/Specs/oRef.xml | 1 - P5/Source/Specs/objectDesc.xml | 1 - P5/Source/Specs/objectType.xml | 1 - P5/Source/Specs/opener.xml | 1 - P5/Source/Specs/org.xml | 1 - P5/Source/Specs/orig.xml | 1 - P5/Source/Specs/origDate.xml | 1 - P5/Source/Specs/orth.xml | 1 - P5/Source/Specs/outputRendition.xml | 1 - P5/Source/Specs/p.xml | 1 - P5/Source/Specs/pRef.xml | 1 - P5/Source/Specs/param.xml | 1 - P5/Source/Specs/paramList.xml | 1 - P5/Source/Specs/paramSpec.xml | 1 - P5/Source/Specs/particDesc.xml | 1 - P5/Source/Specs/path.xml | 1 - P5/Source/Specs/pause.xml | 1 - P5/Source/Specs/pb.xml | 1 - P5/Source/Specs/pc.xml | 1 - P5/Source/Specs/per.xml | 1 - P5/Source/Specs/performance.xml | 1 - P5/Source/Specs/person.xml | 1 - P5/Source/Specs/personGrp.xml | 1 - P5/Source/Specs/persona.xml | 1 - P5/Source/Specs/phr.xml | 1 - P5/Source/Specs/physDesc.xml | 1 - P5/Source/Specs/place.xml | 1 - P5/Source/Specs/pos.xml | 1 - P5/Source/Specs/postBox.xml | 1 - P5/Source/Specs/postCode.xml | 1 - P5/Source/Specs/postscript.xml | 1 - P5/Source/Specs/prefixDef.xml | 1 - P5/Source/Specs/preparedness.xml | 1 - P5/Source/Specs/profileDesc.xml | 1 - P5/Source/Specs/projectDesc.xml | 1 - P5/Source/Specs/prologue.xml | 1 - P5/Source/Specs/pron.xml | 1 - P5/Source/Specs/ptr.xml | 1 - P5/Source/Specs/pubPlace.xml | 1 - P5/Source/Specs/publicationStmt.xml | 1 - P5/Source/Specs/punctuation.xml | 1 - P5/Source/Specs/purpose.xml | 1 - P5/Source/Specs/q.xml | 1 - P5/Source/Specs/quotation.xml | 1 - P5/Source/Specs/quote.xml | 1 - P5/Source/Specs/rb.xml | 1 - P5/Source/Specs/rdg.xml | 1 - P5/Source/Specs/rdgGrp.xml | 1 - P5/Source/Specs/re.xml | 1 - P5/Source/Specs/recordHist.xml | 1 - P5/Source/Specs/recording.xml | 1 - P5/Source/Specs/recordingStmt.xml | 1 - P5/Source/Specs/redo.xml | 1 - P5/Source/Specs/ref.xml | 1 - P5/Source/Specs/refState.xml | 1 - P5/Source/Specs/refsDecl.xml | 1 - P5/Source/Specs/reg.xml | 1 - P5/Source/Specs/relatedItem.xml | 1 - P5/Source/Specs/remarks.xml | 1 - P5/Source/Specs/rendition.xml | 1 - P5/Source/Specs/repository.xml | 1 - P5/Source/Specs/respStmt.xml | 1 - P5/Source/Specs/respons.xml | 1 - P5/Source/Specs/restore.xml | 1 - P5/Source/Specs/retrace.xml | 1 - P5/Source/Specs/revisionDesc.xml | 1 - P5/Source/Specs/rhyme.xml | 1 - P5/Source/Specs/role.xml | 1 - P5/Source/Specs/roleDesc.xml | 1 - P5/Source/Specs/roleName.xml | 1 - P5/Source/Specs/root.xml | 1 - P5/Source/Specs/row.xml | 1 - P5/Source/Specs/rs.xml | 1 - P5/Source/Specs/rt.xml | 1 - P5/Source/Specs/rubric.xml | 1 - P5/Source/Specs/ruby.xml | 1 - P5/Source/Specs/s.xml | 1 - P5/Source/Specs/said.xml | 1 - P5/Source/Specs/salute.xml | 1 - P5/Source/Specs/samplingDecl.xml | 1 - P5/Source/Specs/schemaRef.xml | 1 - P5/Source/Specs/schemaSpec.xml | 1 - P5/Source/Specs/scriptDesc.xml | 1 - P5/Source/Specs/scriptNote.xml | 1 - P5/Source/Specs/scriptStmt.xml | 1 - P5/Source/Specs/sealDesc.xml | 1 - P5/Source/Specs/secFol.xml | 1 - P5/Source/Specs/secl.xml | 1 - P5/Source/Specs/seg.xml | 1 - P5/Source/Specs/segmentation.xml | 1 - P5/Source/Specs/sense.xml | 1 - P5/Source/Specs/sequence.xml | 1 - P5/Source/Specs/series.xml | 1 - P5/Source/Specs/seriesStmt.xml | 1 - P5/Source/Specs/set.xml | 1 - P5/Source/Specs/setting.xml | 1 - P5/Source/Specs/settingDesc.xml | 1 - P5/Source/Specs/shift.xml | 1 - P5/Source/Specs/sic.xml | 1 - P5/Source/Specs/signatures.xml | 1 - P5/Source/Specs/signed.xml | 1 - P5/Source/Specs/soCalled.xml | 1 - P5/Source/Specs/sound.xml | 1 - P5/Source/Specs/source.xml | 1 - P5/Source/Specs/sourceDesc.xml | 1 - P5/Source/Specs/sourceDoc.xml | 1 - P5/Source/Specs/sp.xml | 1 - P5/Source/Specs/spGrp.xml | 1 - P5/Source/Specs/space.xml | 1 - P5/Source/Specs/span.xml | 1 - P5/Source/Specs/spanGrp.xml | 1 - P5/Source/Specs/speaker.xml | 1 - P5/Source/Specs/specDesc.xml | 1 - P5/Source/Specs/specGrp.xml | 1 - P5/Source/Specs/specGrpRef.xml | 1 - P5/Source/Specs/specList.xml | 1 - P5/Source/Specs/stage.xml | 1 - P5/Source/Specs/standOff.xml | 1 - P5/Source/Specs/stdVals.xml | 1 - P5/Source/Specs/street.xml | 1 - P5/Source/Specs/stress.xml | 1 - P5/Source/Specs/string.xml | 1 - P5/Source/Specs/styleDefDecl.xml | 1 - P5/Source/Specs/subc.xml | 1 - P5/Source/Specs/subst.xml | 1 - P5/Source/Specs/substJoin.xml | 1 - P5/Source/Specs/summary.xml | 1 - P5/Source/Specs/superEntry.xml | 1 - P5/Source/Specs/supplied.xml | 1 - P5/Source/Specs/support.xml | 1 - P5/Source/Specs/supportDesc.xml | 1 - P5/Source/Specs/surface.xml | 1 - P5/Source/Specs/surfaceGrp.xml | 1 - P5/Source/Specs/surname.xml | 1 - P5/Source/Specs/surplus.xml | 1 - P5/Source/Specs/surrogates.xml | 1 - P5/Source/Specs/syll.xml | 1 - P5/Source/Specs/symbol.xml | 1 - P5/Source/Specs/table.xml | 1 - P5/Source/Specs/tag.xml | 1 - P5/Source/Specs/tagUsage.xml | 1 - P5/Source/Specs/tagsDecl.xml | 1 - P5/Source/Specs/taxonomy.xml | 1 - P5/Source/Specs/tech.xml | 1 - P5/Source/Specs/teiCorpus.xml | 1 - P5/Source/Specs/teiHeader.xml | 1 - P5/Source/Specs/teidata.authority.xml | 1 - P5/Source/Specs/teidata.certainty.xml | 1 - P5/Source/Specs/teidata.count.xml | 1 - P5/Source/Specs/teidata.duration.iso.xml | 1 - P5/Source/Specs/teidata.duration.w3c.xml | 1 - P5/Source/Specs/teidata.enumerated.xml | 1 - P5/Source/Specs/teidata.gender.xml | 1 - P5/Source/Specs/teidata.interval.xml | 1 - P5/Source/Specs/teidata.key.xml | 1 - P5/Source/Specs/teidata.language.xml | 1 - P5/Source/Specs/teidata.name.xml | 1 - P5/Source/Specs/teidata.namespace.xml | 1 - P5/Source/Specs/teidata.namespaceOrName.xml | 1 - P5/Source/Specs/teidata.nullOrName.xml | 1 - P5/Source/Specs/teidata.numeric.xml | 1 - P5/Source/Specs/teidata.outputMeasurement.xml | 1 - P5/Source/Specs/teidata.pattern.xml | 1 - P5/Source/Specs/teidata.point.xml | 1 - P5/Source/Specs/teidata.pointer.xml | 1 - P5/Source/Specs/teidata.prefix.xml | 1 - P5/Source/Specs/teidata.probCert.xml | 1 - P5/Source/Specs/teidata.probability.xml | 1 - P5/Source/Specs/teidata.replacement.xml | 1 - P5/Source/Specs/teidata.sex.xml | 1 - P5/Source/Specs/teidata.temporal.iso.xml | 1 - P5/Source/Specs/teidata.temporal.w3c.xml | 1 - P5/Source/Specs/teidata.temporal.working.xml | 1 - P5/Source/Specs/teidata.text.xml | 1 - P5/Source/Specs/teidata.truthValue.xml | 1 - P5/Source/Specs/teidata.unboundedCount.xml | 1 - P5/Source/Specs/teidata.version.xml | 1 - P5/Source/Specs/teidata.versionNumber.xml | 1 - P5/Source/Specs/teidata.word.xml | 1 - P5/Source/Specs/teidata.xTruthValue.xml | 1 - P5/Source/Specs/teidata.xmlName.xml | 1 - P5/Source/Specs/teidata.xpath.xml | 1 - P5/Source/Specs/term.xml | 1 - P5/Source/Specs/text.xml | 1 - P5/Source/Specs/textClass.xml | 1 - P5/Source/Specs/textDesc.xml | 1 - P5/Source/Specs/textLang.xml | 1 - P5/Source/Specs/textNode.xml | 1 - P5/Source/Specs/then.xml | 1 - P5/Source/Specs/time.xml | 1 - P5/Source/Specs/timeline.xml | 1 - P5/Source/Specs/titlePage.xml | 1 - P5/Source/Specs/titlePart.xml | 1 - P5/Source/Specs/titleStmt.xml | 1 - P5/Source/Specs/tns.xml | 1 - P5/Source/Specs/trailer.xml | 1 - P5/Source/Specs/transcriptionDesc.xml | 1 - P5/Source/Specs/transpose.xml | 1 - P5/Source/Specs/tree.xml | 1 - P5/Source/Specs/triangle.xml | 1 - P5/Source/Specs/typeDesc.xml | 1 - P5/Source/Specs/typeNote.xml | 1 - P5/Source/Specs/u.xml | 1 - P5/Source/Specs/unclear.xml | 1 - P5/Source/Specs/undo.xml | 1 - P5/Source/Specs/unicodeProp.xml | 1 - P5/Source/Specs/unihanProp.xml | 1 - P5/Source/Specs/unit.xml | 1 - P5/Source/Specs/usg.xml | 1 - P5/Source/Specs/vAlt.xml | 1 - P5/Source/Specs/vColl.xml | 1 - P5/Source/Specs/vDefault.xml | 1 - P5/Source/Specs/vLabel.xml | 1 - P5/Source/Specs/vMerge.xml | 1 - P5/Source/Specs/vNot.xml | 1 - P5/Source/Specs/vRange.xml | 1 - P5/Source/Specs/val.xml | 1 - P5/Source/Specs/valDesc.xml | 1 - P5/Source/Specs/valItem.xml | 1 - P5/Source/Specs/valList.xml | 1 - P5/Source/Specs/variantEncoding.xml | 1 - P5/Source/Specs/view.xml | 1 - P5/Source/Specs/vocal.xml | 1 - P5/Source/Specs/w.xml | 1 - P5/Source/Specs/watermark.xml | 1 - P5/Source/Specs/when.xml | 1 - P5/Source/Specs/width.xml | 1 - P5/Source/Specs/wit.xml | 1 - P5/Source/Specs/witDetail.xml | 1 - P5/Source/Specs/witEnd.xml | 1 - P5/Source/Specs/witStart.xml | 1 - P5/Source/Specs/witness.xml | 1 - P5/Source/Specs/writing.xml | 1 - P5/Source/Specs/xenoData.xml | 1 - P5/Source/Specs/xr.xml | 1 - P5/Source/Specs/zone.xml | 1 - 841 files changed, 37 insertions(+), 55271 deletions(-) mode change 100644 => 120000 P5/Source/Guidelines/fr/AB-About.xml mode change 100644 => 120000 P5/Source/Guidelines/fr/AI-AnalyticMechanisms.xml mode change 100644 => 120000 P5/Source/Guidelines/fr/BIB-Bibliography.xml mode change 100644 => 120000 P5/Source/Guidelines/fr/CC-LanguageCorpora.xml mode change 100644 => 120000 P5/Source/Guidelines/fr/CE-CertaintyResponsibility.xml mode change 100644 => 120000 P5/Source/Guidelines/fr/CH-LanguagesCharacterSets.xml mode change 100644 => 120000 P5/Source/Guidelines/fr/CO-CoreElements.xml mode change 100644 => 120000 P5/Source/Guidelines/fr/COL-Colophon.xml mode change 100644 => 120000 P5/Source/Guidelines/fr/DI-PrintDictionaries.xml mode change 100644 => 120000 P5/Source/Guidelines/fr/DR-PerformanceTexts.xml mode change 100644 => 120000 P5/Source/Guidelines/fr/DS-DefaultTextStructure.xml mode change 100644 => 120000 P5/Source/Guidelines/fr/Dedication.xml mode change 100644 => 120000 P5/Source/Guidelines/fr/FM1-IntroductoryNote.xml mode change 100644 => 120000 P5/Source/Guidelines/fr/FS-FeatureStructures.xml mode change 100644 => 120000 P5/Source/Guidelines/fr/FT-TablesFormulaeGraphics.xml mode change 100644 => 120000 P5/Source/Guidelines/fr/GD-GraphsNetworksTrees.xml mode change 100644 => 120000 P5/Source/Guidelines/fr/MS-ManuscriptDescription.xml mode change 100644 => 120000 P5/Source/Guidelines/fr/ND-NamesDates.xml mode change 100644 => 120000 P5/Source/Guidelines/fr/NH-Non-hierarchical.xml mode change 100644 => 120000 P5/Source/Guidelines/fr/PARTIND.xml mode change 100644 => 120000 P5/Source/Guidelines/fr/PH-PrimarySources.xml mode change 100644 => 120000 P5/Source/Guidelines/fr/PrefatoryNote.xml mode change 100644 => 120000 P5/Source/Guidelines/fr/REF-ATTRIBUTES.xml mode change 100644 => 120000 P5/Source/Guidelines/fr/REF-CLASSES-ATTS.xml mode change 100644 => 120000 P5/Source/Guidelines/fr/REF-CLASSES-MODEL.xml mode change 100644 => 120000 P5/Source/Guidelines/fr/REF-ELEMENTS.xml mode change 100644 => 120000 P5/Source/Guidelines/fr/REF-MACROS.xml mode change 100644 => 120000 P5/Source/Guidelines/fr/SA-LinkingSegmentationAlignment.xml mode change 100644 => 120000 P5/Source/Guidelines/fr/SG-GentleIntroduction.xml mode change 100644 => 120000 P5/Source/Guidelines/fr/ST-Infrastructure.xml mode change 100644 => 120000 P5/Source/Guidelines/fr/TC-CriticalApparatus.xml mode change 100644 => 120000 P5/Source/Guidelines/fr/TD-DocumentationElements.xml mode change 100644 => 120000 P5/Source/Guidelines/fr/TS-TranscriptionsofSpeech.xml mode change 100644 => 120000 P5/Source/Guidelines/fr/TitlePageVerso.xml mode change 100644 => 120000 P5/Source/Guidelines/fr/USE.xml mode change 100644 => 120000 P5/Source/Guidelines/fr/VE-Verse.xml mode change 100644 => 120000 P5/Source/Guidelines/fr/WD-NonStandardCharacters.xml diff --git a/P5/Source/Guidelines/en/AB-About.xml b/P5/Source/Guidelines/en/AB-About.xml index f5bea382ae..42ba61a551 100644 --- a/P5/Source/Guidelines/en/AB-About.xml +++ b/P5/Source/Guidelines/en/AB-About.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Guidelines/en/AI-AnalyticMechanisms.xml b/P5/Source/Guidelines/en/AI-AnalyticMechanisms.xml index d478467d37..51916016ff 100644 --- a/P5/Source/Guidelines/en/AI-AnalyticMechanisms.xml +++ b/P5/Source/Guidelines/en/AI-AnalyticMechanisms.xml @@ -1,4 +1,3 @@ -
Simple Analytic Mechanisms diff --git a/P5/Source/Guidelines/en/CC-LanguageCorpora.xml b/P5/Source/Guidelines/en/CC-LanguageCorpora.xml index eaadfd720b..f4ca35b1c3 100644 --- a/P5/Source/Guidelines/en/CC-LanguageCorpora.xml +++ b/P5/Source/Guidelines/en/CC-LanguageCorpora.xml @@ -1,4 +1,3 @@ -
Language Corpora diff --git a/P5/Source/Guidelines/en/CE-CertaintyResponsibility.xml b/P5/Source/Guidelines/en/CE-CertaintyResponsibility.xml index a0c5b4f902..02675dd175 100644 --- a/P5/Source/Guidelines/en/CE-CertaintyResponsibility.xml +++ b/P5/Source/Guidelines/en/CE-CertaintyResponsibility.xml @@ -1,4 +1,3 @@ -
Certainty, Precision, and Responsibility diff --git a/P5/Source/Guidelines/en/CH-LanguagesCharacterSets.xml b/P5/Source/Guidelines/en/CH-LanguagesCharacterSets.xml index dca8219668..ad367a5213 100644 --- a/P5/Source/Guidelines/en/CH-LanguagesCharacterSets.xml +++ b/P5/Source/Guidelines/en/CH-LanguagesCharacterSets.xml @@ -1,4 +1,3 @@ -
diff --git a/P5/Source/Guidelines/en/CO-CoreElements.xml b/P5/Source/Guidelines/en/CO-CoreElements.xml index 0a15fa3776..676c389f19 100644 --- a/P5/Source/Guidelines/en/CO-CoreElements.xml +++ b/P5/Source/Guidelines/en/CO-CoreElements.xml @@ -1,4 +1,3 @@ -
diff --git a/P5/Source/Guidelines/en/COL-Colophon.xml b/P5/Source/Guidelines/en/COL-Colophon.xml index 7500dddd9d..23f593e6a0 100644 --- a/P5/Source/Guidelines/en/COL-Colophon.xml +++ b/P5/Source/Guidelines/en/COL-Colophon.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Guidelines/en/DEPRECATIONS.xml b/P5/Source/Guidelines/en/DEPRECATIONS.xml index 7f139ec965..5436fb1f7f 100644 --- a/P5/Source/Guidelines/en/DEPRECATIONS.xml +++ b/P5/Source/Guidelines/en/DEPRECATIONS.xml @@ -1,4 +1,3 @@ -
diff --git a/P5/Source/Guidelines/en/DI-PrintDictionaries.xml b/P5/Source/Guidelines/en/DI-PrintDictionaries.xml index e031829598..bcefb264a3 100644 --- a/P5/Source/Guidelines/en/DI-PrintDictionaries.xml +++ b/P5/Source/Guidelines/en/DI-PrintDictionaries.xml @@ -1,4 +1,3 @@ -
diff --git a/P5/Source/Guidelines/en/DR-PerformanceTexts.xml b/P5/Source/Guidelines/en/DR-PerformanceTexts.xml index 233e1dbc4b..bfcf74fdea 100644 --- a/P5/Source/Guidelines/en/DR-PerformanceTexts.xml +++ b/P5/Source/Guidelines/en/DR-PerformanceTexts.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Guidelines/en/DS-DefaultTextStructure.xml b/P5/Source/Guidelines/en/DS-DefaultTextStructure.xml index b160c7afdd..953c585d79 100644 --- a/P5/Source/Guidelines/en/DS-DefaultTextStructure.xml +++ b/P5/Source/Guidelines/en/DS-DefaultTextStructure.xml @@ -1,4 +1,3 @@ -
diff --git a/P5/Source/Guidelines/en/Dedication.xml b/P5/Source/Guidelines/en/Dedication.xml index 766e7443d7..3f105ab8b9 100644 --- a/P5/Source/Guidelines/en/Dedication.xml +++ b/P5/Source/Guidelines/en/Dedication.xml @@ -1,4 +1,3 @@ -
diff --git a/P5/Source/Guidelines/en/FM1-IntroductoryNote.xml b/P5/Source/Guidelines/en/FM1-IntroductoryNote.xml index c3492bfca2..eb1ada5f01 100644 --- a/P5/Source/Guidelines/en/FM1-IntroductoryNote.xml +++ b/P5/Source/Guidelines/en/FM1-IntroductoryNote.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Guidelines/en/FS-FeatureStructures.xml b/P5/Source/Guidelines/en/FS-FeatureStructures.xml index 933e6a14b5..1a4c2cf972 100644 --- a/P5/Source/Guidelines/en/FS-FeatureStructures.xml +++ b/P5/Source/Guidelines/en/FS-FeatureStructures.xml @@ -1,4 +1,3 @@ -
Feature Structures diff --git a/P5/Source/Guidelines/en/FT-TablesFormulaeGraphics.xml b/P5/Source/Guidelines/en/FT-TablesFormulaeGraphics.xml index 4c4102bb21..4a66f2484c 100644 --- a/P5/Source/Guidelines/en/FT-TablesFormulaeGraphics.xml +++ b/P5/Source/Guidelines/en/FT-TablesFormulaeGraphics.xml @@ -1,4 +1,3 @@ -
diff --git a/P5/Source/Guidelines/en/GD-GraphsNetworksTrees.xml b/P5/Source/Guidelines/en/GD-GraphsNetworksTrees.xml index 415d9f2e62..f4491bd8c6 100644 --- a/P5/Source/Guidelines/en/GD-GraphsNetworksTrees.xml +++ b/P5/Source/Guidelines/en/GD-GraphsNetworksTrees.xml @@ -1,4 +1,3 @@ -
Graphs, Networks, and Trees diff --git a/P5/Source/Guidelines/en/HD-Header.xml b/P5/Source/Guidelines/en/HD-Header.xml index b03c51e5d7..01ca4db0b6 100644 --- a/P5/Source/Guidelines/en/HD-Header.xml +++ b/P5/Source/Guidelines/en/HD-Header.xml @@ -1,4 +1,3 @@ -
diff --git a/P5/Source/Guidelines/en/MS-ManuscriptDescription.xml b/P5/Source/Guidelines/en/MS-ManuscriptDescription.xml index e43d0b3bc6..707db494e2 100644 --- a/P5/Source/Guidelines/en/MS-ManuscriptDescription.xml +++ b/P5/Source/Guidelines/en/MS-ManuscriptDescription.xml @@ -1,4 +1,3 @@ -
diff --git a/P5/Source/Guidelines/en/ND-NamesDates.xml b/P5/Source/Guidelines/en/ND-NamesDates.xml index eff14c5bed..c19d65555f 100644 --- a/P5/Source/Guidelines/en/ND-NamesDates.xml +++ b/P5/Source/Guidelines/en/ND-NamesDates.xml @@ -1,4 +1,3 @@ -
diff --git a/P5/Source/Guidelines/en/NH-Non-hierarchical.xml b/P5/Source/Guidelines/en/NH-Non-hierarchical.xml index 9a2e0f15af..a810a46b98 100644 --- a/P5/Source/Guidelines/en/NH-Non-hierarchical.xml +++ b/P5/Source/Guidelines/en/NH-Non-hierarchical.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Guidelines/en/PARTIND.xml b/P5/Source/Guidelines/en/PARTIND.xml index 48e76ceaae..7efdd6160c 100644 --- a/P5/Source/Guidelines/en/PARTIND.xml +++ b/P5/Source/Guidelines/en/PARTIND.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Guidelines/en/PH-PrimarySources.xml b/P5/Source/Guidelines/en/PH-PrimarySources.xml index 73fb70d1a4..4ac22926a4 100644 --- a/P5/Source/Guidelines/en/PH-PrimarySources.xml +++ b/P5/Source/Guidelines/en/PH-PrimarySources.xml @@ -1,4 +1,3 @@ -
diff --git a/P5/Source/Guidelines/en/REF-ATTRIBUTES.xml b/P5/Source/Guidelines/en/REF-ATTRIBUTES.xml index 24d14cad0f..160ec9182d 100644 --- a/P5/Source/Guidelines/en/REF-ATTRIBUTES.xml +++ b/P5/Source/Guidelines/en/REF-ATTRIBUTES.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Guidelines/en/REF-CLASSES-ATTS.xml b/P5/Source/Guidelines/en/REF-CLASSES-ATTS.xml index b52965be87..f01fb8cecb 100644 --- a/P5/Source/Guidelines/en/REF-CLASSES-ATTS.xml +++ b/P5/Source/Guidelines/en/REF-CLASSES-ATTS.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Guidelines/en/REF-CLASSES-MODEL.xml b/P5/Source/Guidelines/en/REF-CLASSES-MODEL.xml index 5c12bc541f..a22126f37f 100644 --- a/P5/Source/Guidelines/en/REF-CLASSES-MODEL.xml +++ b/P5/Source/Guidelines/en/REF-CLASSES-MODEL.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Guidelines/en/REF-ELEMENTS.xml b/P5/Source/Guidelines/en/REF-ELEMENTS.xml index 581769398c..7342f68b86 100644 --- a/P5/Source/Guidelines/en/REF-ELEMENTS.xml +++ b/P5/Source/Guidelines/en/REF-ELEMENTS.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Guidelines/en/REF-MACROS.xml b/P5/Source/Guidelines/en/REF-MACROS.xml index eeb913d8b2..d30784f2bf 100644 --- a/P5/Source/Guidelines/en/REF-MACROS.xml +++ b/P5/Source/Guidelines/en/REF-MACROS.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Guidelines/en/SA-LinkingSegmentationAlignment.xml b/P5/Source/Guidelines/en/SA-LinkingSegmentationAlignment.xml index 3d8e462b99..e20d6056b9 100644 --- a/P5/Source/Guidelines/en/SA-LinkingSegmentationAlignment.xml +++ b/P5/Source/Guidelines/en/SA-LinkingSegmentationAlignment.xml @@ -1,4 +1,3 @@ -
diff --git a/P5/Source/Guidelines/en/SG-GentleIntroduction.xml b/P5/Source/Guidelines/en/SG-GentleIntroduction.xml index 9a63cb7059..90585c375c 100644 --- a/P5/Source/Guidelines/en/SG-GentleIntroduction.xml +++ b/P5/Source/Guidelines/en/SG-GentleIntroduction.xml @@ -1,4 +1,3 @@ -
diff --git a/P5/Source/Guidelines/en/ST-Infrastructure.xml b/P5/Source/Guidelines/en/ST-Infrastructure.xml index b141ec6789..a474073f17 100644 --- a/P5/Source/Guidelines/en/ST-Infrastructure.xml +++ b/P5/Source/Guidelines/en/ST-Infrastructure.xml @@ -1,4 +1,3 @@ -
diff --git a/P5/Source/Guidelines/en/TC-CriticalApparatus.xml b/P5/Source/Guidelines/en/TC-CriticalApparatus.xml index d9970210f6..93fcb0d8f1 100644 --- a/P5/Source/Guidelines/en/TC-CriticalApparatus.xml +++ b/P5/Source/Guidelines/en/TC-CriticalApparatus.xml @@ -1,4 +1,3 @@ -
diff --git a/P5/Source/Guidelines/en/TD-DocumentationElements.xml b/P5/Source/Guidelines/en/TD-DocumentationElements.xml index 1c08f566e9..0b2b595ebd 100644 --- a/P5/Source/Guidelines/en/TD-DocumentationElements.xml +++ b/P5/Source/Guidelines/en/TD-DocumentationElements.xml @@ -1,4 +1,3 @@ -
diff --git a/P5/Source/Guidelines/en/TitlePageVerso.xml b/P5/Source/Guidelines/en/TitlePageVerso.xml index b822117af9..ea1b857235 100644 --- a/P5/Source/Guidelines/en/TitlePageVerso.xml +++ b/P5/Source/Guidelines/en/TitlePageVerso.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Guidelines/en/USE.xml b/P5/Source/Guidelines/en/USE.xml index d49abb5a03..f6fd2cb557 100644 --- a/P5/Source/Guidelines/en/USE.xml +++ b/P5/Source/Guidelines/en/USE.xml @@ -1,4 +1,3 @@ -
diff --git a/P5/Source/Guidelines/en/VE-Verse.xml b/P5/Source/Guidelines/en/VE-Verse.xml index 62f662afa2..0e46ad5d72 100644 --- a/P5/Source/Guidelines/en/VE-Verse.xml +++ b/P5/Source/Guidelines/en/VE-Verse.xml @@ -1,4 +1,3 @@ -
diff --git a/P5/Source/Guidelines/en/WD-NonStandardCharacters.xml b/P5/Source/Guidelines/en/WD-NonStandardCharacters.xml index 70be97f315..46d74b6d20 100644 --- a/P5/Source/Guidelines/en/WD-NonStandardCharacters.xml +++ b/P5/Source/Guidelines/en/WD-NonStandardCharacters.xml @@ -1,4 +1,3 @@ -
diff --git a/P5/Source/Guidelines/fr/AB-About.xml b/P5/Source/Guidelines/fr/AB-About.xml deleted file mode 100644 index 9bae7a7755..0000000000 --- a/P5/Source/Guidelines/fr/AB-About.xml +++ /dev/null @@ -1,838 +0,0 @@ - - - - - - - -
-About These Guidelines - -

These Guidelines have been developed and are maintained by the Text -Encoding Initiative Consortium (TEI); see . They -are addressed to anyone who works with any kind of textual resource in -digital form.

- -

They make recommendations about suitable ways of representing those -features of textual resources which need to be identified explicitly -in order to facilitate processing by computer programs. In -particular, they specify a set of markers (or tags) which -may be inserted in the electronic representation of the text, in order -to mark the text structure and other features of interest. Many, or -most, computer programs depend on the presence of such explicit -markers for their functionality, since without them a digitized text -appears to be nothing but a sequence of undifferentiated bits. The -success of the World Wide Web, for example, is partly a consequence of -its use of such markup to indicate such features as headings and lists -on individual pages, and to indicate links between pages. The process -of inserting such explicit markers for implicit textual features is -often called markup, or equivalently within this -work encoding; the term -tagging is also used informally. We use the term -encoding scheme or markup language to denote -the complete set of rules associated with the use of markup in a given -context; we use the term markup vocabulary for the -specific set of markers or named distinctions employed by a given -encoding scheme. Thus, this work both describes the TEI encoding -scheme, and documents the TEI markup vocabulary.

- -

The TEI encoding scheme is of particular usefulness in facilitating -the loss-free interchange of data amongst individuals and research -groups using different programs, computer systems, or application -software. Since they contain an inventory of the features most often -deployed for computer-based text processing, these Guidelines are also -useful as a starting point for those designing new systems and -creating new materials, even where interchange of information is not a -primary objective.

- -

These Guidelines apply to texts in any natural language, of any -date, in any literary genre or text type, without restriction on form -or content. They treat both continuous materials (running -text) and discontinuous materials such as dictionaries and -linguistic corpora. Though principally directed to the needs of the -scholarly research community, these Guidelines are not restricted to -esoteric academic applications. They are also useful for librarians -maintaining and documenting electronic materials, and for publishers -and others creating or distributing electronic texts. Although they -focus on problems of representing in electronic form texts which -already exist in traditional media, these Guidelines are also -applicable to textual material which is born -digital. We believe them to be adequate to -the widest variety of currently existing practices in using -digital textual data, but by no means limited to them.

- -

The rules and recommendations made in these Guidelines are -expressed in terms of what is currently the most widely-used markup -language for digital resources of all kinds: the Extensible Markup -Language (XML), as defined by the World Wide Web Consortium's XML -Recommendation. However, the TEI encoding scheme itself does not -depend on this language; it was originally formulated in terms of SGML -(the ISO Standard Generalized Markup Language), a -predecessor of XML, and -may in future years be re-expressed in other ways as the -field of markup develops and matures. For more information on markup -languages see chapter ; for more -information on the associated character encoding issues see chapter -. -

- -

This document provides the authoritative and complete statement of -the requirements and usage of the TEI encoding scheme. As such, -although it includes numerous small examples, it must be stressed that -this work is intended to be a reference manual rather than a tutorial -guide.

- -

The remainder of this chapter comprises three sections. The first -gives an overview of the structure and notational conventions used -throughout these Guidelines. The second enumerates the design principles -underlying the TEI scheme and the application environments in which it -may be found useful. Finally, the third section gives a brief account -of the origins and development of the Text Encoding Initiative itself.

- -
Structure and Notational -Conventions of this Document - -

The remaining two sections of the front matter to these Guidelines -provide background tutorial material for those unfamiliar with basic -markup technologies. Following the present introductory section, we -present a detailed introduction to XML itself, intended to cover in a -relatively painless manner as much as the novice user of the TEI -scheme needs to know about markup languages in general and XML in -particular. This is followed by a discussion of the general principles -underlying current practice in the representation of different -languages and writing systems in digital form. This chapter is largely -intended for the user unfamiliar with the Unicode encoding systems, -though the expert may also find its historical overview of -interest.

- -

The body of this edition of these Guidelines proper contains 23 -chapters arranged in increasing order of specialist interest. The -first five chapters discuss in depth matters likely to be of -importance to anyone intending to apply the TEI scheme to virtually -any kind of text. The next seven focus on particular kinds of text: -verse, drama, spoken text, dictionaries, and manuscript -materials. The next nine chapters deal with a wide range of topics, -one or more of which are likely to be of interest in specialist -applications of various kinds. The last two chapters deal with the XML -encoding used to represent the TEI scheme itself, and provide -technical information about its implementation. The last chapter also -defines the notion of TEI conformance and its implications for -interchange of materials produced according to these Guidelines.

- -

As noted above, this is a reference work, and is not intended to be -read through from beginning to end. However, the reader wishing to -understand the full potential of the TEI scheme will need a thorough -grasp of the material covered by the first four chapters and the last -two. Beyond that, the reader is recommended to select according to -their specific interests: one of the strengths of the TEI architecture -is its modular nature.

- -

As far as possible, extensive cross referencing is provided -wherever related topics are dealt with; these are particularly -effective in the online version of these Guidelines. In addition, a -series of technical appendixes provide detailed formal definitions for -every element, every class, and every macro discussed in the body of -the work; these are also cross linked as appropriate. Finally, a -detailed bibliography is provided, which identifies the source of many -examples cited in the text as well as documenting works referred to, -and listing other relevant publications.

- - -

As an aid to the reader, most chapters of these Guidelines follow -the same basic organization. The chapter begins with an overview of -the subjects treated within it, linked to the following -subsections. Within each section where new elements are described, a -summary table is first given, which provides their names and a brief -description of their intended usage. This is then followed where -appropriate by further discussion of each element, including wherever -possible usage examples taken somewhat eclectically from a variety of -real sources. These examples are not intended to be exhaustive, but -rather to suggest typical ways in which the elements concerned may -usefully be applied. Where appropriate, a link to a statement of the -source for most examples is provided in the online version. Within the -examples, use of whitespace such as newlines or indentation is simply -intended to aid legibility, and is not prescriptive or normative.

- -

Wherever TEI elements or classes are mentioned in the text, they -are linked in the online version to the relevant reference -specification for the element or class concerned. Element names are -always given in the form name, where name is the -generic identifier of the element; empty elements such as -pb or anchor include a closing slash to distinguish -them wherever they are discussed. References to attributes take the -form attname, where attname is the name of the -attribute. References to classes are also presented as links, for -example model.divLike for a model class, -and att.global for an attribute class. -

- -
- The use of modal verbs -

In general the TEI guidelines try to be careful when using modal verbs and phrases such as 'must', 'must not, - 'should', 'should not' and 'may'. In terms of the meanings, these generally follow in the different meanings of these words. - In particular: - - - This word, or the terms "REQUIRED" or "SHALL", means that this is an absolute requirement of the TEI Guidelines - for production of a TEI conformant file. - - This phrase, or the phrase "SHALL NOT", means that this is an absolute prohibition of the - TEI Guidelines for production of a TEI conformant file. - - This word, or the adjective "RECOMMENDED", means that there may exist valid reasons in - particular circumstances to ignore a particular recommendation, but the full implications - must be understood and carefully weighed before choosing a different course. - - This phrase, or the phrase "NOT RECOMMENDED" means that there may exist valid reasons in - particular circumstances when the particular behavior is acceptable or even useful, but the full implications - should be understood and the case carefully weighed before implementing any behavior so described. - - This word, or the adjective "OPTIONAL", means that a recommendation is truly optional. One user may - choose to follow the recommendation because a particular project requires it or feels that - it enhances their work while another project may choose to not follow this recommendation. - - However, the prose of the TEI Guidelines continually undergoes revision and all uses may not reflect this. Please report - any errors or unclear use of these words. -

-
- -
-TEI Naming Conventions -

These Guidelines use a more or less consistent set of conventions -in the naming of XML elements and classes. This section summarizes -those conventions.

-
-Element and Attribute Names -

An unadorned name such as blort is the -name of a TEI element or attribute. During -generation of TEI RELAX NG schema fragments, the patterns corresponding -with these TEI names are given a prefix tei to allow them -to co-exist with names from other XML namespace. This prefix is not -visible to the end user, and is not used in TEI documentation. When -generating multi-namespace schemas, however, the user needs to be -aware of them. .

-

The following conventions apply to the choice of names: - -Elements are given generic identifiers as far as possible -consisting of one or more tokens, by which we mean whole -words or recognisable abbreviations of them, taken from the English -language. -Where an element name contains more than one token, the first -letter of the second -token, and of any subsequent ones, is capitalized, as in for example -biblStruct, listPerson. This -camelCasing is used also for attribute names and -symbolic values. -Module names also use whole words, for the most part, but are -always all lower case. -The specification for an element or attribute whose name -contains abbreviations generally also includes a gloss -element providing the expanded sense of the name. -An element specification may also contain approved translations -for element or attribute names in one or more other languages using -the altIdent element; this is not however generally done in -TEI P5. - -

- -

Whole words are generally preferred for clarity. The following -abbreviations are however commonly used within generic identifiers: - - - -attribute - -bibliographic description or reference in a bibliography - -category, especially as used in text classification - -character, typically a Unicode character - -document: this usually refers to the original source document -which is being encoded, - -declaration: has a specific sense in the TEI -header, as discussed in - -description: has a specific sense in the TEI header, as -discussed in - -group. In TEI usage, a group is distinguished from a list in that -the former associates several objects which act as a single entity, -while the latter does not. For example, a linkGrp combines -several link elements which have certain properties in -common, whereas a listBibl simply lists a number of otherwise -unrelated bibl elements. - -interpretation or analysis -(natural) language -manuscript - -organization, that is, a named group of people or legal entity - -reading or version found in a specific witness -reference or link - -technical specification or definition - -statement: used in a specific sense in the TEI header, -as discussed in - -structured: that is, containing a specific set of -named elements rather than mixed content - -value, for example of a variable or an attribute - -witness: that is, a specific document which attests specific -readings in a textual tradition or apparatus - -

-

Some abbreviations are used inconsistently: for example, -add is an addition, and addSpan is a spanning -addition, but addName is an additional name, not the name of -an addition. Such inconsistencies are relatively few in number, and it -is hoped to remove them in subsequent revisions of these Guidelines.

-

Some elements have very short abbreviated names: these are for the -most part elements which are likely to be used very frequently in a -marked up text, for example p (paragraph), s -(segment) hi (highlighted phrase), ptr (pointer), -div (division) etc. We do not specifically list such elements -here: as noted above, an expansion of each such abbreviated name is -provided within the documentation using the gloss element -.

-
-
-
-Class, Macro, and Datatype Names - -

All named objects other than elements and attributes have one of -the following prefixes, which indicate whether the object is a module, -an attribute class, a model class, a datatype, or a macro: - -Component -Name -Example - -Attribute -Classesatt.*att.global -Model -Classesmodel.*model.biblPart -Macrosmacro.*macro.paraContent -Datatypesteidata.*teidata.pointer -
-

-

The concepts of model class, attribute class, etc. are defined in -. Here we simply note some conventions about their -naming.

- -

The following rules apply to attribute class names: -Attribute class names take the form att.xxx, where -xxx is typically an adjective, or a series of adjectives -separated by dots, describing a property common to the attributes -which make up the class. -Attributes with the same name are considered to have the same -semantics, whether the attribute is inherited from a class, or locally -defined. - -

- -

The following rules apply to model class names: -Model classes have names beginning model. followed -by a root name, and zero or more suffixes as described -below. -A root name may be the name of an element, generally the -prototypical parent or sibling for elements which are members of the -class. -The first suffix should be Part, if the class -members are all children of the element named rootname; or -Like, if the class members are all siblings of the -element named rootname. -The rootname global is used to indicate that class -members are permitted anywhere in a TEI document. -Additional suffixes may be added, prefixed by a dot, to -distinguish subclasses, semantic or structural. - -

-

For example, the class of elements which can form part of a -div is called model.divPart. This class -includes as a subclass the elements which can form part of a -div in a spoken text, which is named -model.divPart.spoken

- - -
- - - -
Design Principles - -

Because of its roots in the humanities research community, the TEI -scheme is driven by its original goal of serving the needs of research, -and is therefore committed to providing a maximum of comprehensibility, -flexibility, and extensibility. More specific design goals of the TEI -have been that these Guidelines should: - -provide a standard format for data interchange -provide guidance for the encoding of texts in this format -support the encoding of all kinds of features of all -kinds of texts studied by researchers -be application independent -This has led to a number of important design decisions, such as: - -the choice of XML and Unicode -the provision of a large predefined tag set -encodings for different views of text -alternative encodings for the same textual features -mechanisms for user-defined modification of the scheme -We discuss some of these goals in more detail below.

- -

The goal of creating a common interchange format which is -application independent requires the definition of a specific markup -syntax as well as the definition of a large set of elements or -concepts. The syntax of the recommendations made in this document -conforms to the World Wide Web Consortium's XML Recommendation () -but their definition is as far -as possible independent of any particular schema language.

-

The goal of providing guidance for text encoding suggests that -recommendations be made as to what textual features should be recorded -in various situations. However, when selecting certain features for -encoding in preference to others, these Guidelines have tended to -prefer generic solutions to specific ones, and to avoid areas where no -consensus exists, while attempting to accommodate as many diverse views -as feasible. Consequently, the TEI Guidelines make (with relatively -rare exceptions) no suggestions or restrictions as to the relative -importance of textual features. The philosophy of these Guidelines is -if you want to encode this feature, do it this way—but very -few features are mandatory. In the same spirit, while these Guidelines -very rarely require you to encode any particular feature, they do -require you to be honest about which features you have encoded, that -is, to respect the meanings and usage rules they recommend for -specific elements and attributes proposed.

-

The requirement to support all kinds of materials likely to be of -interest in research has largely conditioned the development of the -TEI into a very flexible and modular system. The development of other -XML vocabularies or standards is typically motivated by the desire to -create a single fully specified encoding scheme for use in a -well-defined application domain. By contrast, the TEI is intended for -use in a large number of rather ill-defined and often overlapping -domains. It achieves its generality by means of the modular -architecture described in which enables each user -to create a schema appropriate to their needs without compromising the -interoperability of their data.

-

The Guidelines have been written largely with a focus on text capture -(i.e. the representation in electronic form of an already existing copy -text in another medium) rather than text creation (where no such copy -text exists). Hence the frequent use of terms like -transcription, original, -copy text, etc. However, these Guidelines are -equally applicable to text creation, although certain elements, such as sourceDesc, and certain attributes, such as the rendition indicators, will not be relevant in this case.

-

Concerning text capture the TEI Guidelines do not specify a -particular approach to the problem of fidelity to the source text and -recoverability of the original; such a choice is the responsibility of -the text encoder. The current version of these Guidelines, however, -provides a more fully elaborated set of tags for markup of rhetorical, -linguistic, and simple typographic characteristics of the text than for -detailed markup of page layout or for fine distinctions among type fonts -or manuscript hands. It should be noted also that, with the present -version of these Guidelines, it is no longer necessarily the case that -an unmediated version of the source text can be recovered from an -encoded text simply by removing the markup. -

-

In these Guidelines, no hard and fast distinction is drawn between -objective and subjective -information or between representation and -interpretation. These distinctions, though -widely made and often useful in narrow, well-defined contexts, are -perhaps best interpreted as distinctions between issues on which there -is a scholarly consensus and issues where no such consensus exists. -Such consensus has been, and no doubt will be, subject to change. The -TEI Guidelines do not make suggestions or restrictions as to which of -these features should be encoded. The use of the terms -descriptive and interpretive about different -types of encoding in these Guidelines is not intended to support any -particular view on these theoretical issues. Historically, it reflects -a purely practical division of responsibility amongst the original -working committees (see further ).

-

In general, the accuracy and the reliability of the encoding and the -appropriateness of the interpretation is for the individual user of the -text to determine. The Guidelines provide a means of documenting the -encoding in such a way that a user of the text can know the reasoning -behind that encoding, and the general interpretive decisions on which it -is based. The TEI header should be used to document and justify many -such aspects of the encoding, but the choice of TEI elements for a -particular feature is in itself a statement about the interpretation -reached by the encoder.

- -

In many situations more than one view of a text is needed since no -absolute recommendation to embody one specific view of text can apply -to all texts and all approaches to them. Within limits, the syntax of -XML ensures that some encodings can be ignored for some purposes. To -enable encoding multiple views, these Guidelines not only treat a -variety of textual features, but sometimes provide several alternative -encodings for what appear to be identical textual phenomena. These -Guidelines offer the possibility of encoding many different -views of the text, simultaneously if necessary. Where different views -of the formal structure of a text are required, as opposed to -different annotations on a single structural view, however, the formal -syntax of XML (which requires a single hierarchical view of text -structure) poses some problems; recommendations concerning ways of -overcoming or circumventing that restriction are discussed in chapter -.

- -

In brief, the TEI Guidelines define a general-purpose encoding -scheme which makes it possible to encode different views of text, -possibly intended for different applications, serving the majority of -scholarly purposes of text studies in the humanities. Because no -predefined encoding scheme can possibly serve all research purposes, -the TEI scheme is designed to facilitate both selection from a wide -range of predefined markup choices, and the addition of new (non-TEI) -markup options. By providing a formally verifiable means of extending -the TEI recommendations, the TEI makes it simple for such -user-identified modifications to be incorporated into future releases -of these Guidelines as they evolve. The underlying mechanisms which -support these aspects of the scheme are introduced in chapter , and detailed discussions of their use provided in -chapter .

- -
Intended Use -

We envisage three primary functions for these Guidelines: - -guidance for individual or local practice in text -creation and data capture; -support of data interchange; -support of application-independent local processing. -These three functions are so thoroughly interwoven in practice that it -is hardly possible to address any one without addressing the others. -However, the distinction provides a useful framework for discussing the -possible role of these Guidelines in work with electronic texts.

-
Use in Text Capture and Text Creation -

The description of textual features found in the chapters which -follow should provide a useful checklist from which scholars planning to -create electronic texts should select the subset of features suitable -for their project.

-

Problems specific to text creation or text -capture have not been considered explicitly in -this document. These Guidelines are not concerned with the process by -which a digital text comes into being: it can be typed by hand, -scanned from a printed book or typescript, read from a typesetter's -tape, or acquired from another researcher who may have used another -markup scheme (or no explicit markup at all).

-

We include here only some general points which are often raised about -markup and the process of data capture.

-

XML can appear distressingly verbose, particularly when (as in these -Guidelines) the names of tags and attributes are chosen for clarity and -not for brevity. Editor macros and keyboard shortcuts can allow a -typist to enter frequently used tags with single keystrokes. -It is often possible to transform word-processed or -scanned text automatically. Markup-aware software can help with -maintaining the hierarchical structure of the document, and display the -document with visual formatting rather than raw tags.

-

The techniques described in chapter -may be used to develop simpler data capture TEI-conformant schemas, -for example with limited numbers of elements, or with shorter names -for the tags being used most often. Documents created with such -schemas may then be automatically converted to a more elaborated TEI -form.

-
-
Use for Interchange - -

The TEI format may simply be used as an interchange format, -permitting projects to share resources even when their local encoding -schemes differ. If there are n different encoding -formats, to provide mappings between each possible pair of formats -requires n×(n-1) translations; with an -interchange format, only 2×n such mappings -are needed. However, for such translations to be carried out without -loss of information, the interchange format chosen must be as -expressive (in a formal sense) as any of the target formats; this is a -further reason for the TEI's provision of both highly abstract or -generic encodings and highly specific ones.

-

To translate between any pair of encoding schemes implies: - -identifying the sets of textual features distinguished -by the two schemes; -determining where the two sets of features correspond; -creating a suitable set of mappings.

-

For example, to translate from encoding scheme X into the TEI -scheme: - -Make a list of all the textual features distinguished in -X. -Identify the corresponding feature in the TEI scheme. -There are three possibilities for each feature: - -the feature exists in both X and the TEI scheme; -X has a feature which is absent from the TEI scheme; -X has a feature which corresponds with more than one -feature in the TEI scheme. -The first case is a trivial renaming. The second will require an extension to -the TEI scheme, as described in chapter . The third -is more problematic, but not impossible, provided that a consistent -choice can be made (and documented) amongst the alternatives. -

-

The ease with which this translation can be defined will of -course depend on the clarity with which scheme X -represents the features it encodes.

-

Translating from the TEI into scheme X follows the same pattern, -except that if a TEI feature has no equivalent in X, and X cannot be -extended, information must be lost in translation.

-

The rules defining conformance to these Guidelines are -given in some detail in chapter . -The basic principles informing those rules may be summarized as -follows: - -The TEI abstract model (that is, the set of -categorical distinctions which it defines in the prose of the Guidelines) must be respected. The -correspondence between a tag X and the semantic function assigned to -it by these Guidelines may not be changed; such changes are known -as tag abuse and strongly discouraged. -A TEI document must be expressed as a valid XML-conformant -document which uses the TEI namespace appropriately. If, for example, -the document encodes features not provided by these Guidelines, such -extensions should not be associated with the TEI namespace. -It must be possible to validate a TEI document against a schema -derived from these Guidelines, possibly with extensions provided in -the recommended manner. - - -

- - -
Use for Local Processing -

Machine-readable text can be manipulated in many ways; some users: - -edit texts (e.g. word processors, syntax-directed -editors) -edit, display, and link texts in hypertext systems -format and print texts using desktop publishing systems, -or batch-oriented formatting programs -load texts into free-text retrieval databases or -conventional databases -unload texts from databases as search results or for -export to other software -search texts for words or phrases -perform content analysis on texts -collate texts for critical editions -scan texts for automatic indexing or similar purposes -parse texts linguistically -analyze texts stylistically -scan verse texts metrically -link text and images

-

These applications cover a wide range of likely uses but are by no -means exhaustive. The aim has been to make the TEI Guidelines useful -for encoding the same texts for different purposes. We have avoided -anything which would restrict the use of the text for other -applications. We have also tried not to omit anything essential to any -single application.

-

Because the TEI format is expressed using XML, -almost any modern text processing system is able to process it, and -new TEI-aware software systems are able to build on a solid base -of existing software libraries.

- -
Historical Background - -

The Text Encoding Initiative grew out of a planning conference -sponsored by the Association for Computers and the Humanities (ACH) and -funded by the U.S. National Endowment for the Humanities (NEH), which -was held at Vassar College in November 1987. At this conference some -thirty representatives of text archives, scholarly societies, and -research projects met to discuss the feasibility of a standard encoding -scheme and to make recommendations for its scope, structure, content, -and drafting. During the conference, the Association for Computational -Linguistics and the Association for Literary and Linguistic Computing -agreed to join ACH as sponsors of a project to develop these Guidelines. -The outcome of the conference was a set of principles (the -Poughkeepsie Principles, ), which -determined the further course of the project.

- - -

The Text Encoding Initiative project began in June 1988 with funding -from the NEH, soon followed by further funding from the Commission of -the European Communities, the Andrew W. Mellon Foundation, and the -Social Science and Humanities Research Council of Canada. Four working -committees, composed of distinguished scholars and researchers from both -Europe and North America, were named to deal with problems of text -documentation, -text representation, text analysis and interpretation, and -metalanguage and syntax issues. Each committee was charged with the task of identifying -significant particularities in a range of texts, -and two editors appointed to harmonize the resulting recommendations.

-

A first draft version (P1, with the P here and subsequently -standing for Proposal) of the Guidelines was distributed in July -1990 under the title Guidelines for the Encoding and Interchange -of Machine-Readable Texts. -Extensive public comment and further work on areas not covered in -this version resulted in the drafting of a revised version, TEI P2, -distribution of which began in April 1992. This version included -substantial amounts of new material, resulting from work carried out by -several specialist working groups, set up in 1990 and 1991 to propose -extensions and revisions to the text of P1. The overall organization, -both of the draft itself and of the scheme it describes, was entirely -revised and reorganized in response to public comment on the first -draft.

-

In June 1993 an Advisory Board met to review the current state of -the TEI Guidelines, and recommended the formal publication of the work -done to that time. That version of the TEI Guidelines, TEI P3, -consolidated the work published as parts of TEI P2, along with some -additional new material and was finally published in May of 1994 -without the label draft, thus marking the -conclusion of the initial development work. -

-

In February of 1998 the World Wide Web Consortium issued a final -Recommendation for the Extensible Markup Language, XML.XML was originally developed as a way of publishing on -the World Wide Web richly encoded documents such as those for which -the TEI was designed. Several TEI participants contributed heavily to -the development of XML, most notably XML's senior co-editor -C. M. Sperberg-McQueen, who served as the North American editor for -the TEI Guidelines from their inception until 1999. -Following the rapid take-up of this new standard metalanguage, it -became evident that the TEI Guidelines (which had been published -originally as an SGML application) needed to be re-expressed in this -new formalism if they were to survive. The TEI editors, with -abundant assistance from others who had developed and used TEI, -developed an update plan, and made tentative decisions on relevant -syntactic issues.

- -

In January of 1999, the University of Virginia and the University -of Bergen formally proposed the creation of an international -membership organization, to be known as the TEI Consortium, which -would maintain, develop, and promote the TEI. Shortly thereafter, two -further institutions with longstanding ties to the TEI (Brown -University and Oxford University) joined them in formulating an -Agreement to Establish a Consortium for the Maintenance of the Text -Encoding Initiative (), on which basis the TEI -Consortium was eventually established and incorporated as a -not-for-profit legal entity at the end of the year 2000. The first -members of the new TEI Board took office during January of 2001.

- -

The TEI Consortium was established in order to maintain a permanent -home for the TEI as a democratically constituted, academically and -economically independent, self-sustaining, non-profit organization. In -addition, the TEI Consortium was intended to foster a broad-based user -community with sustained involvement in the future development and -widespread use of the TEI Guidelines ().

- -

To oversee and manage the revision process in collaboration with -the TEI Editors, the TEI Board formed a Technical Council, with a -membership elected from the TEI user community. The Council met for -the first time in January 2002 at King's College London. Its first -task was to oversee production of an XML version -of the TEI Guidelines, updating P3 to enable users to -work with the emerging XML toolset. This, the P4 version of the Guidelines, -was published in June 2002. It was essentially an XML version of P3, -making no substantive changes to the constraints expressed in the -schemas apart from those necessitated by the shift to XML, and -changing only corrigible errors identified in the prose of the P3 -Guidelines. However, given that P3 had by this time been in steady use -since 1994, it was clear that a substantial revision of its content -was necessary, and work began immediately on the P5 version of the -Guidelines. This was planned as a thorough overhaul, involving a -public call for features and new development in a number of important -areas not previously addressed including character encoding, graphics, -manuscript description, biographical and geographical data, and the -encoding language in which the TEI Guidelines themselves are written.

- -

The members of the TEI Council and its associated workgroups are -listed in . In preparing this edition, they have -been attentive to the requirements and practice of the widest possible -range of TEI users, who are now to be found in many different research -communities across the world, and have been largely instrumental in -transforming the TEI from a grant-supported international research -project into a self-sustaining community-based effort. One effect -of the incorporation of the TEI has been the legal requirement to hold -an annual meeting of the Consortium members; these meetings have -emerged as an invaluable opportunity to sustain and reinforce that -sense of community.

-

The present -work is therefore the result of a sustained period of consultation, -drafting, and revision, with input from many different -experts. Whatever merits it may have are to be attributed to them; the -Editors accept responsibility only for the errors remaining.

- - -
- -
Future Developments and Version Numbers - -

The encoding recommended by this document may be used without fear -that future versions of the TEI scheme will be inconsistent with it in -fundamental ways. The TEI will be sensitive, in revising these -Guidelines, to the possible problems which revision might pose for those -who are already using this version of these Guidelines. -

-

With TEI P5, a version numbering system is introduced following - the pattern specified by - the Unicode Consortium: the first digit identifies a major - version number, the second digit a minor version number, and the - third digit a sub-minor version number. The TEI undertakes that no - change will be made to the formal expression of these Guidelines - (that is, a TEI schema, as defined in ) such that - documents conformant to a -given major numbered release cease to be compatible with a subsequent -release of the same major number. Moreover, as far as possible, new -minor releases will be made only for the purpose of adding new -compatible features, or of correcting errors in existing features.

- - -

The Guidelines are currently maintained as an open source project - on the Github site , from which released - and development versions may be freely downloaded. See Previous Releases of P5 for - information on how to find specific versions of TEI releases (Guidelines, - schemas etc.). Notice of errors detected and enhancements requested may - be submitted at .

-
diff --git a/P5/Source/Guidelines/fr/AB-About.xml b/P5/Source/Guidelines/fr/AB-About.xml new file mode 120000 index 0000000000..2382495709 --- /dev/null +++ b/P5/Source/Guidelines/fr/AB-About.xml @@ -0,0 +1 @@ +../en/./AB-About.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/AI-AnalyticMechanisms.xml b/P5/Source/Guidelines/fr/AI-AnalyticMechanisms.xml deleted file mode 100644 index d398572221..0000000000 --- a/P5/Source/Guidelines/fr/AI-AnalyticMechanisms.xml +++ /dev/null @@ -1,1235 +0,0 @@ - - - - -
Simple Analytic Mechanisms - -

This chapter describes a module for associating simple analyses and -interpretations with text elements. We use the term -analysis here to refer to any kind of semantic or -syntactic interpretation which an encoder wishes to attach to all or -part of a text. Examples discussed in this chapter include familiar -linguistic categorizations (such as clause, morpheme, -part-of-speech etc.) and characterizations of narrative -structure (such as theme, reconciliation etc.). The -mechanisms presented in this chapter are simpler but less powerful -than those described in chapter . -

-

Section introduces elements which can be used -to characterize -text segments according to the familiar linguistic categories of -sentence or s-unit, clause, -phrase, word, morpheme, -character, and punctuation mark. These elements represent special cases of the -generic seg element described in section .

-

Section introduces an additional global -attribute which allows passages of text to be associated with -specialized elements representing their interpretation. -These interpretative elements (span and -interp) are described in detail in section . -They allow the encoder to specify an analysis as a series of names and -associated values,Or, as they are widely known, -attribute-value pairs; this term should not be confused, -however, with XML attributes and their values, which are similar in -concept but distinct in their formal definitions. each such pair -being linked to one or more stretches of text, either directly, in the -case of spans, or indirectly, in the case of interpretations.

-

Finally section revisits the topic of linguistic -analysis, and illustrates how these interpretative mechanisms may be -used to associate simple linguistic analysis with text segments.

- -
Linguistic Segment Categories -

In this section we introduce specialized linguistic segment -category elements which may be used to represent the segmentation of -a text into the traditional linguistic categories of -sentence, clause, phrase, -word, morpheme, -characters, and punctuation marks. -

-
Words and Above -

Although different languages have very different rules about what -constitutes a word or a -sentence, these remain generally useful concepts. -In this section we discuss elements provided for marking up linguistic -units down to the word level, however defined. - - -

-

As members of the att.segLike class, these -elements all share the following attribute: - -They also share attributes from att.typed: - -

-

These elements are also all members of the model.segLike class, which is a subclass of -model.phrase. They may thus appear anywhere -that text is permitted within a document, when the module defined by -this chapter is included in a schema.

- -

The w and pc elements belong to the att.linguistic class, which supplies -attributes that may be used for lightweight linguistic annotation (see section below): -

-

Additionally, these elements also have access to the att.lexicographic.normalized class, -which supplies the attributes norm and orig: the former for handling -normalization/regularization at the word level, the latter providing the original form if the element -content is modernized or regularized. Note that these attributes are a local (word-level) alternative -to the robust mechanism that uses the choice, orig, and reg elements, -discussed in section and in chapter . The choice-based -mechanism is the default descriptive device, while the norm and orig attributes are used to -handle a subset of normalizations in linguistic contexts where a single sequence of tokens is a priority, for example -in historical corpora subject to linguistic analysis. It needs to be stressed that the simplified attribute-based -mechanism is not meant to be used for editorial interventions. -The att.lexicographic.normalized class is also used in dictionary -entries, as discussed in chapter .

- -

The s element may be used simply to segment a text -end-to-end into a series of non-overlapping segments, referred to here -and elsewhere as s-units, or sentences. -

- Nineteen fifty-four, when I was eighteen years old, - is held to be a crucial turning point in the history of - the Afro-American — for the U.S.A. as a whole — the - year segregation was outlawed by the U.S. Supreme Court. - It was also a crucial year for me because on June 18, - 1954, I began serving a sentence in state prison for - possession of marijuana. -

- -The s element is more restricted both in its content and its -usage than the generic seg element. The seg unit may -contain anything which can appear within a paragraph: thus it may be -used to enclose members of the model.inter -class (such as bibl or list) as well as other phrase -elements; the s unit may only contain phrase-level elements -or text. Also, unlike seg elements, s elements -should not be nested within each other.Neither this -constraint, nor the requirement that the whole of the text be -segmented by s elements is required by the TEI -Guidelines. The seg element is intended for -use as a generic segmentation element, the specific function of which -may be indicated by its type attribute; the other members -of the class are more specialized. Thus, the s, cl, and -phr elements may be thought of as equivalent to seg -type="s-unit", seg -type="clause" and seg type="phrase", respectively, -but with the above-mentioned restrictions. -

-

The s element may be further subdivided into -clauses, marked with the cl element, -as in the following example: -

- - It was about the beginning of September, 1664, - that I, among the rest of my neighbours, - heard in ordinary discourse - that the plague was returned again to Holland; - for it had been very violent there, and particularly at - Amsterdam and Rotterdam, in the year 1663, - whither, they say, it was brought, - some said from Italy, others from the Levant, among some goods - which were brought home by their Turkey fleet; - others said it was brought from Candia; - others from Cyprus. - - - It mattered not from whence it came; - but all agreed it was come into Holland again. - -

-

-

Clauses may be further divided into phr elements in the same -way. A text may be segmented directly into clauses, or into -phrases, with no need to include segmentation at a higher level as well. -

-

For verse texts, the overlapping of metrical and syntactic structure -requires that special care be given to representing both using an -element hierarchy. One simple approach is to split the syntactic phrases -into fragments when they cross verse boundaries, reuniting them -with the part attribute: -

- Tweedledum and Tweedledee - Agreed to have a battle; - For Tweedledum said Tweedledee - Had spoiled his nice new rattle.
-
- Just then flew down a monstrous crow, - As black as a tar barrel; - Which frightened both the heroes so, - They quite forgot their quarrel.
- -Another approach is to use the next and prev -attributes defined in the additional module for linking (chapter ): -For Tweedledum said - Tweedledee - - Had spoiled his nice new rattle. -Other methods are also possible; for discussion, see chapter . -

-

The type attribute on linguistic segment categories can -be used to provide additional interpretative information about the -category. The function attribute on the cl and -phr elements can be used to provide additional information -about the function of the category. Legal values for these -two attributes are not defined by these Guidelines, but should be -documented in the segmentation element of the -encodingDesc element within the document's header. -A general approach to the encoding of linguistic categories for -parts of a text is discussed in section below. -

-

Using traditional terminology, these attributes provide a convenient -way of specifying, for example, that the clause from whence it -came is a relative clause modifying another, or that the -phrase by the U.S. Supreme Court is a prepositional -post-modifier: -It mattered not - from whence it came; - -the year segregation -was outlawed -by the U.S. Supreme Court. -

-

Segmentation into clauses and phrases can, of course, be combined. -Such detailed encodings as the following may require careful -formatting if they are to be easily readable however. -

- - - Nineteen fifty-four, - - when I - was eighteen years old - , - - is held - - - to be - a crucial turning point - in - the history - of the Afro-American - - - — - for - the U.S.A. - as a whole - - - - — - the year - - segregation - - was outlawed - by the U.S. Supreme Court - . - - - It - - was - also - a crucial year for me - - because - on June 18, 1954, - I - - began serving - a sentence in state prison - for possession of marijuana -.

-

This style of markup may introduce spurious new lines and blanks -into the text. If the original layout is important, it should be -explicitly encoded, using such facilities as the lb element, -the global rend or rendition attributes, etc. -

- -

The w, m, and c elements are identical -in meaning to the seg element with a type -attribute of w, m, or c respectively, and may -occur wherever seg is permitted to occur. However, their -content is more constrained than seg: for example, -the w element should only contain w, m, -c elements or pc elements, or plain text; the m element should -contain only c or pc elements or plain text; both -the c and pc elements -should contain only plain text, most often only a single character or -a sequence of graphemes to be treated as a single -character. Consequently, while these more specific elements can be -translated directly into typed seg elements, the reverse is -not necessarily the case. -

-

The restriction on the content of the w element in -particular requires that a certain care must be exercised when using it, -especially in relation to the use of other tags that one may think of as -word level, but which are in fact defined as phrase -level. Consider the problem of segmenting an occurrence of the -mentioned element as a word. -grandiloquent -The first of the following two encodings is legitimate; the second is -not, since the mentioned element is not part of the content -model of the w element: - -grandiloquent -grandiloquent

-

On the other hand, both of the following encodings are -legitimate: - - grandiloquent speech - - - grandiloquent speech - -The first encoding describes the citing of a phrase. The second -describes a phrase which consists of something mentioned. - -

-

The w element carries additional attributes -which may be of use in many indexing or analytic applications. The -lemma attribute may be used to specify the -lemma, that is the head- or uninflected form of an -inflected verb or noun, for example: - - timeo - Danaos - et - dona - ferentes - -

-

In some situations it may be more convenient to use the -lemmaRef pointer attribute than to supply an explicit -uninflected form. This attribute assumes the existence of a list of -uninflected forms, for example in an online lexicon, with which -individual w entries can be associated using the usual TEI -pointer mechanisms. Assuming that a -standardized lexicon for Latin is available at the location -http://lexicon.org/latin.xml, we might for example revise the above -example as: - - timeo - Danaos - -

-
- -
Below the Word Level -

It is sometimes helpful to markup explicitly sub-word components -such as morphemes, characters, or punctuation. - - -

- -

The m element is used to mark up morphologically -identified segmentation below the word level. Analogous to the -lemma attribute for w, there is a -baseForm attribute for the m element, -which may be used to indicate the base form of -an inflected morpheme; where appropriate, m elements may also -be organized hierarchically: - - - com - fort - - able - -

-

The distinction between m and w is provided as a -convenience only; it may not be appropriate for all linguistic -theories, nor is it meaningful in all languages. The intention is to -provide a means for those cases where it is considered helpful to distinguish -lexical from sub-lexical tokens, to complement the more general -mechanism already provided by the seg element, using which -the above example could alternatively be marked up as follows: - - - com - fort - - able - -See section for an alternative to using type in such contexts. -

- -

There is a substantial -linguistic difference between characters like letters or diacritics -and punctuation marks. The former are used to -construct meaningful units like morphemes or words. The latter are -functionally independent units acting at the level of syntactic -units. A word may consist of a single letter (for example I in English), -but this does not mean that we should use c instead of w -to mark it up.

- -

The c (character) element should be used to mark up any non-lexical -character, whether this appears within a word, or outside it. In the -following example, the encoder wishes to indicate that the letters are -not to be regarded as words: - - - - M - O - A - I - doth - sway - my - life - - -

-

The c element may be used for -individual characters occurring within a w or m -element which it is desired to distinguish for some reason, as in the -following examples: - - - n - ' - t - - -This encoding represents the constituents of a common abbreviation, -but does not indicate that it is in fact an abbreviation; the -am element () may be preferred for the -latter purpose. Generally speaking, the use of c use to mark -non-lexical punctuation marks is deprecated, since the pc -element is provided specifically to distinguish these. -

- -

The pc (punctuation character) element should be used to mark up -characters which are specifically regarded as providing punctuation, -rather than constituting parts of a word. It may be particularly -useful when transcribing older written materials, in which an encoding -of the original punctuation may be useful for interpretive or analytic -purposes, in much the same way as an encoding of the original -orthography may be. For example, in the following extract from -a Bodleian Library musical manuscript -

- -
-two different punctuation marks are used to distinguish kinds of pause -in the text. The punctus elevatus (which resembles an inverted -semicolon) is not a Unicode character, but may still be encoded using -the g element. As further described in chapter , this element points to a definition for the intended -character which may be stored either locally or elsewhere. - deus qui regis omnia -; natus est in bethlehem -.o . mira gratia... - - - - - -

-

The pc element carries special attributes to record -analyses of the functional behaviour or classification of the -punctuation mark it contains. The unit attribute may be -used, as on the milestone element to name the kind of unit -which the punctuation mark delimits, for example a paragraph or -section. The pre attribute may be used to indicate whether -the punctuation precedes or follows the unit it delimits. The -force attribute indicates the strength of the association -between the punctuation mark and its adjacent word.

-

In the following example, the paragraph marker (¶) has been tagged -as a strong punctuation mark, preceding the unit it marks, which is -named para: - -

Incipit...

- -

- -

A similar encoding can be used for hyphenation: - -A fire-proof vest is recom- -mended. - - - Refer to for a discussion of the motivations for - explicitely recording the presence of hyphens.

- - -

The w, m, c, and pc elements can be used -together to give a fairly detailed low-level grammatical analysis of -text. For example, consider the following segmentation of the English -S-unit I didn't do it. -I - - did - n't - -do -it -. - -

-

This segmentation, crude as it is, succeeds in representing the idea -that did occurring as a morphological -component of the word -didn't has something in common with the word do. A further advantage of segmenting the text down -to this level is that it becomes relatively simple to associate each -such segment with a more detailed formal analysis, for example by -providing a baseform, or morphological analysis at whichever level is appropriate. -This matter is taken up in detail in section . -

- - - - - - - - - - - - - - - -
-
-
Global Attributes for Simple Analyses -

When the module described by this chapter is selected, an -additional attribute is defined for all elements: - -The ana attribute may be specified for any element. -Its effect is to associate the element with one or more others -representing an analysis or interpretation of it. Its target should be -one of the elements described in the section below, -or some other interpretative element such as note, on which -see section or fs, -on which see chapter . If a hierarchical form of classification -is desired then it may point to category element at a suitable level in a -taxonomy see .

- - - -
-
Spans and Interpretations -

The simplest mechanisms for attaching analytic notes in some -structured vocabulary to particular passages of text are provided by the -span and interp elements, and their associated -grouping elements spanGrp and interpGrp. -

- -

These elements are all members of the class att.interpLike, and thus share the following attribute: - - They also inherit the following attributes from att.global.responsibility: - - -

-

The type attribute of the -span and interp elements may be used to indicate -that the annotations are of specific types, for example thematic or -structural. The annotation itself is supplied as the content of the -span or interp element. -In the case of the span element, the span of text being -annotated is indicated by values of the from, -to or target attributes, used in combination as -follows. If only the from attribute is supplied, then the -span is coterminous with the element indicated by its value; if both -from and to are supplied, the span runs from the -start of the element indicated by the from attribute up to -the end of the element indicated by the to attribute; if -the target attribute is used, the span is defined by -aggregating the contents of the (possibly non-contiguous) elements pointed to by its values. It -is an error to supply only the to attribute; to supply more -than one pointer value for either to or from -attributes; or to supply either of these in conjunction with the -target attribute. -In the case of interp (see below), the span is indicated by a -pointer from a link element or some similar mechanism. The -resp attribute indicates the annotator responsible for this annotation. -

-

The span element provides a simple way of indicating such -features as phrasal verbs in a linguistic analysis, as in this -example: - -Whatdidyoumakeup -phrasal verb "make up" - -Here the two components of the span follow each other, so the -to and from attributes may be used. The -same effect could however be achieved by using the target -attribute: - -Whatdidyoumakeup -phrasal verb "make up" - -This second approach might be cumbersome if the number of components -to be combined is very large. It is however essential if the -components do not follow each other, as in this example: - -Didyoumakeitup -phrasal verb "make up" - -

-

The span element can be used for any kind of -annotation. In this example it is used in a narratological analysis: -

-There was certainly a definite point at which the - thing began. -It was not; then it was suddenly inescapable, - and nothing could have frightened it away. -There was a slow integration, during which she, - and the little animals, and the moving grasses, and the sun-warmed - trees, and the slopes of shivering silvery mealies, and the great - dome of blue light overhead, and the stones of earth under her feet, - became one, shuddering together in a dissolution of dancing - atoms. -She felt the rivers under the ground forcing - themselves painfully along her veins, swelling them out in an - unbearable pressure; her flesh was the earth, and suffered growth - like a ferment; and her eyes stared, fixed like the eye of the - sun. -Not for one second longer (if the terms for time - apply) could she have borne it; but then, with a sudden movement - forwards and out, the whole process stopped; and that was the - moment which it was impossible to remember - afterwards. -the moment -For during that space of time (which was - timeless) she understood quite finally her smallness, the - unimportance of humanity. -

-

-

The span element may, as in this example, be placed in the -text near the textual span it is associated with. Alternatively, it may be placed -elsewhere in the same or a different document. Where several -span or interp elements share the same attributes, -for example having the same responsibility or type, it may be -convenient to group them within a spanGrp or interpGrp element as follows: - - the moment - - -

-

Spans may also be used to represent structural divisions within -a narrative, particularly when these do not coincide with the -structure implied by the element structure. Consider the following narrative: - -

Sigmund, the son of Volsung, was a king in Frankish country. -Sinfiotli was the eldest of his sons, the second was Helgi, the -third Hamund. -Borghild, Sigmund's wife, had a brother named — -But Sinfiotli, her stepson, and — both wooed the same woman -and Sinfiotli killed him over it.The rule marks spaces -left for the missing name in the manuscript. -And when he came home, Borghild asked him to go away, -but Sigmund offered her weregild, and she was obliged to accept it. -At the funeral feast Borghild was serving beer. She took poison, a big -drinking horn full, and brought it to Sinfiotli. When Sinfiotli looked -into the horn, he saw that poison was in it, and said to Sigmund This -drink is cloudy, old man. Sigmund took the horn and drank it off. -It is said that Sigmund was hardy and that poison did him no harm, -inside or out. And all his sons could tolerate poison on their skin. -Borghild brought another horn to Sinfiotli, and asked him to drink, and -everything happened as before. And a third time she brought him a horn, -and reproachful words as well, if he didn't drink from it. He spoke -again to Sigmund as before. He said Filter it through your mustache, -son! Sinfiotli drank it off and at once fell dead. -

-

Sigmund carried him a long way in his arms and came to a long, -narrow fjord, and there was a small boat there and a man in it. He -offered to ferry Sigmund over the fjord. But when Sigmund carried the -body out to the boat, it was fully laden. The man said Sigmund should -go around the fjord inland. The man pushed the boat out and then -suddenly vanished. -

-

King Sigmund lived a long time in Denmark in the kingdom of -Borghild, after he married her. Then he went south to Frankish lands, -to the kingdom he had there. Then he married Hiordis, the daughter of -King Eylimi. Their son was Sigurd. King Sigmund fell in a battle with -the sons of Hunding. And then Hiordis married Alf, the son of King -Hialprec. Sigurd grew up there as a boy. -

-

Sigmund and all his sons were tall and outstanding in their -strength, their growth, their intelligence, and their accomplishments. -But Sigurd was the most outstanding of all, and everyone who knows about -the old days says he was the most outstanding of men and the noblest of -all the warrior kings.

-

-

A structural analysis of this text, dividing it into narrative units -in a pattern shared with other texts from the same literature, might -look like this: -

-Sigmund ... was a king in Frankish country. -Sinfiotli was the eldest of his sons. -Borghild, Sigmund's wife, had a brother ... -But Sinfiotli ... wooed the same woman -and Sinfiotli killed him over it. -And when he came home, ... she was obliged to accept it. -At the funeral feast Borghild was serving beer. -She took poison ... and brought it to Sinfiotli. -Sinfiotli drank it off and at once fell dead. - -

-

Sigmund carried him a long way in his arms ...

-

King Sigmund lived a long time in Denmark ...

-

Sigmund and all his sons were tall ...

- - introduction - conflict - climax - revenge - reconciliation - aftermath - -

-

Note the use of an empty anchor element to provide a target for -the reconciliation unit which is normally part of -the narrative pattern but which is not realized in the text shown. -

- -

The same analysis may be expressed with the interp element -instead of the span element; this element provides attributes -for recording an interpretive category and its value, as well as the -identity of the interpreter, but does not itself indicate which passage -of text is being interpreted; the same interpretive structures can thus -be associated with many passages of the text. The association between -text passages and interp elements should be made either by -pointing from the text to the interp element with the -ana attribute defined in section , or by -pointing at both text and interpretation from a link element, - -as described in chapter . -

-

To encode the first example above using interp, it is -necessary to create a text element which contains—or corresponds to—the third, fourth, and fifth orthographic sentences (S-units) in -the paragraph. This can be done either with the seg element, -described in , or the join -element, described in . The resulting -element can then be associated with the interp element using the -ana attribute described in section . We illustrate using the seg element. -

-There was certainly a definite point ... -It was not; then it was suddenly inescapable ... - -There was a slow integration ... -She felt the rivers under the ground ... -Not for one second longer ... - -For during that space of time ... -

-the moment -

-

The second example above can be recoded using interp and -interpGrp tags in a similar manner. The interpretation -itself can be expressed in an interpGrp element, which would -replace the spanGrp in the example shown above: - - introduction - conflict - climax - revenge - reconciliation - aftermath - -

-

Any of these interp elements may be linked to the text either -by means of the ana attribute, or by means of link -elements. Using the ana attribute (on seg elements -introduced specifically for this purpose), the text would be encoded as -follows: -

- -Sigmund ... was a king in Frankish country. -Sinfiotli was the eldest of his sons. -Borghild, Sigmund's wife, had a brother ... - -But Sinfiotli ... wooed the same woman -and Sinfiotli killed him over it. - -And when he came home, ... she was obliged to accept it. -At the funeral feast Borghild was serving beer. -Sinfiotli drank it off and at once fell dead. -

- -

Sigmund carried him a long way in his arms ...

-

King Sigmund lived a long time in Denmark ...

-

Sigmund and all his sons were tall ...

- -

-

The linkage may also be accomplished using a linkGrp element, -whose content is a set of link elements which point to each -interpretive element and its corresponding text unit. This method does -not require the use of the ana attribute on the text -units. - - - - - - - - -

-

One obvious advantage of using interp rather than -span elements for the Sigmund text is that the interp -elements can be reused for marking up other texts in the same document, -whereas the span elements cannot. On -the other hand, the use of interp elements may require the -creation of special text elements not otherwise needed (e.g. the -seg and the join in the revised encoding of the text), -whereas the use of span elements does not. -

- - - - - - -
-
Linguistic Annotation -

By linguistic annotation we mean here any annotation -determined by an analysis of linguistic features of the text, excluding -as borderline cases both the formal structural properties of the text -(e.g. its division into chapters or paragraphs) and descriptive -information about its context (the circumstances of its production, its -genre or medium). The structural properties of any TEI-conformant text -should be represented using the structural elements discussed elsewhere -in this chapter and in chapters , , -, , , , -and . The contextual -properties of a TEI text are fully documented in the TEI header, which -is discussed in chapter , and in section . -

-

Other forms of linguistic annotation may be applied at a number of -levels in a text. A code (such as a word-class or part-of-speech -code) may be associated with each word or token, or with groups of such -tokens, which may be continuous, discontinuous, or nested. A code may -also be associated with relationships (such as cohesion) perceived as -existing between distinct parts of a text. The codes themselves may -stand for discrete and non-decomposable categories, or they may represent -highly articulated bundles of textual features. Their function may be -to place the annotated part of the text somewhere within a narrowly -linguistic or discoursal domain of analysis, or within a more general -semantic field, or any combination drawn from these and other domains. -

-

The manner by which such annotations are generated and attached to -the text may be entirely automatic, entirely manual or a mixture. The -ease and accuracy with which analysis may be automated may vary with the -level at which the annotation is attached. The method employed should -be documented in the interpretation element within the encoding -description of the TEI header, as described in section . -Where different parts of a language corpus have used -different annotation methods, the decls -attribute may be used to indicate the fact, as further -discussed in section . -

-
Linguistic Annotation by Means of Generic TEI Devices -

As one example of such types of analysis, consider the following -sentence, taken from the Lancaster/IBM Treebank -Project (). - The victim's friends told police that Kruger drove -into the quarry and never surfaced.

Our discussion focuses -on the way that this sentence might be analysed using the CLAWS system -developed at the University of Lancaster but exactly the same -principles may be applied to a wide variety of other systems.For the word-class tagging method used by CLAWS see -; -For an overview of the system see . The example sentence was processed -using an online version of the CLAWS tagger at -Output from the system consists of a segmented and tokenized version -of the text, in which word class codes have been associated with each -token. CLAWS offers outputs in a variety of non-XML and XML formats: -for example, the simplest format for the sample sentence would be: -

-

This may be easily transformed into an equivalent TEI XML representation: - -The -victim's -friends told -police that -Kruger drove into -the quarry -and never -surfaced - -Although the names used for the attribute values here may have some -significance for the human reader (AT0 for -article, NN1 for singular noun, -NN2 for plural noun, etc.) they are -arbitrary codes, used in this case as pointers to other elements which -define their significance more precisely. If the codes are considered -to be atomic, then the interp element described -in section might be used to supply brief definitions -in the header: - - - Definite article - Adverb - Conjunction - Relative that - Noun singular - Noun plural - Proper noun - Genitive marker - Preposition - Verb past tense - - - -If the codes are considered to -be compositional (for example that NN1 and NN2 -have something in common, namely their noun-ness, which -they do not share with, say, VVD), then this -compositionality may be most clearly expressed using a mechanism based -on the fs element defined in chapter . -

-

This approach requires the text to be fully segmented, using the -linguistic segment elements described in section , so that the scope of the ana attribute -used to point to each interpretation is clearly defined. A further -analysis into phrase and clause elements can be superimposed on the -word and morpheme tagging in the preceding illustration. For example, -CLAWS provides the following constituent analysis of the sample -sentence (the word class codes have been deleted): -

-

Treating the labels on the brackets as phrase or clause -interpretations, this analysis of the structure of the example sentence -can be combined with the word class analysis and represented as follows -(the symbol V&"/> representing the first part of a coordinate -phrase, has been replaced by V1, and V+, representing the -second part, has been replaced by V2). - - - - The - victim - 's - - friends - - - told - - police - - - that - - Krueger - - - - drove - - into - - the - quarry - - - - and - - never - surfaced - - - - - . - -

-

This approach requires the definition of further interp -(or fs) elements to provide targets for the pointers used to -represent the constituent analysis: - - - coordinate continuation - verbal - nominal - genitive - finite clause - prepositional - coordinate start - -

- -

Alternatively, a stand-off representation for -these analyses might be created using the linkGrp element. -In this case, each linguistic segment to be annotated must be supplied with its own -xml:id attribute: - - -The -victim -'s friends -told police -that Kruger -drove into -the quarry -and never -surfaced - -Each segment-interpretation pair may now be represented by means of a -link element inside an appropriate linkGrp element: - - - - - - - - - - -

-

Each linguistic segment so far discussed has been well-behaved with -respect to the basic document hierarchy, having only a single parent. -Moreover, the segmentation has been complete, in that each part of the -text is accounted for by some segment at each level of analysis, without -discontinuities or overlap. This state of affairs does not of -course apply in all types of analysis, and these Guidelines provide a -number of mechanisms to support the representation of discontinuities or -multiple analyses. A brief overview of these facilities is provided in -chapter ; also see . These mechanisms -all depend to a greater or lesser degree on the use of pointing -elements of various kinds. -

-
-
Lightweight Linguistic Annotation -

While these Guidelines offer a variety of means to add linguistic information to textual -units and much of that has been presented above, two kinds of use cases and two groups of -users call for a dedicated set of specialized attributes to carry linguistic -information. One relevant use case is where basic linguistic information gets added to an -existing resource, in which generic attributes such as type or ana -have already been used to encode other categorizations and analyses. The other group of -users and use cases involves corpus linguists and resources built from scratch as lightly -annotated language corpora. In the latter kind of projects, energy and person-hours are not -devoted to careful literary analysis and hand-encoding of the relevant phenomena, but rather -to the analysis of the completed resources, and therefore the phase of resource-building must be -quick and relatively effortless, requiring minimal structural markup, well-established -containers for grammatical information, and a standardized way of filling them in.

- -

The aims defined above can be realized by means of lightweight linguistic annotation using -attributes that belong to the att.linguistic class: - -

- -

The essence of lightweight linguistic annotation is that the basic grammatical information -is encapsulated at the word level, together with the orthographic shape of the word. This -has clear advantages for automatic processing but, on the other hand, this form of data -encapsulation also imposes restrictions on the extent of information that can be encoded, -essentially limiting it to a single tokenization and lemmatization schema, a single tagset, -and a subset of the possible analyses (out from potentially many guesses at the -part-of-speech or morphosyntactic descriptions, single values have to fit into the existing -attributes). Another important principle that this kind of annotation is sensitive to is the -need for (near) homomorphism between the assumed tokenization (division of the text stream -into minimal units) and the division into minimal syntactic units (word forms, -in the terminology of ISO Morpho-Syntactic Framework, ISO 24611All -definitions contained within ISO standards can be accessed at the ISO Online Browsing Platform. For ISO MAF, see -.), because it is the former that results -from the process of tokenization, but the latter that can be lemmatized and meaningfully -described by means of grammatical features. Where tokens are only minimally mismatched with -word forms, various repair strategies can be used (e.g., recursing w to capture -multi-token compounds or using att.fragmentable to point at -disjoint tokens). Beyond that, more robust TEI mechanisms, based on standoff principles and -feature structures, should replace lightweight annotation.

- - -

The basic grammatical information encoded by means of -att.linguistic is sufficient for the purpose of enhancing queries or improving -the analysis of search results by, for example, making it possible to distinguish between -the noun cut and the identically spelled verb -cut in English, and further between e.g. the present-tense form of -cut and its past-tense or past-participial forms. For the former -contrast, the part-of-speech (pos) attribute should be used, whereas the latter -may use pos and/or msd attributes, depending on the annotation -vocabulary adopted for the project in question. The various grammatical realizations of a -single dictionary word can be captured by means of the attribute lemma, which -provides a common label for them. For example, English verbs are typically lemmatized as the -base form (also called bare infinitive), so the value of lemma for -the verbal forms write, writes, -wrote, written, and -writing is typically write.

- -

Together with the span-delimiting elements mentioned in this section, such as s, -cl, or phr, lightweight grammatical annotation may be used to build -basic syntactic constituency structures, where hierarchical information is expressed through -span containment rather than by relations among tree nodes. This is however the limit of -this kind of annotation: for the purpose of describing true constituency or dependency -syntactic structures, one needs to turn to more robust mechanisms offered by the TEI, which -may involve graph description (see chapter ) or standoff techniques (see -section ), and where grammatical labels may need to be annotated by -means of feature structures (see chapter ).

- -

Some of the above-mentioned robust methods will also prove handy in cases where more than one tagset -(label inventory) is used to label the words, or where automatic morphological analysis yields multiple -possibilities (for example, the form cutting is morphologically ambiguous between -verbal, adjectival, and nominal) and needs to be followed by (often also automatic) disambiguation in -morphosyntactic contexts, with varying probabilities that may also need to be recorded together with their -corresponding part-of-speech and morphosyntactic values.

- -

It should be borne in mind that tokenization, lemmatization, part-of-speech identification, and -morphosyntactic labelling, especially when performed automatically, should in most cases be seen as -involving pragmatic decisions, dictated by concrete practical goals, economy of description, or the -demands of particular analytic and/or visualization tools. It comes therefore as no surprise that -numerous alternative (and often conflicting) lemmatization strategies and tagsets exist, in use by -various communities and various tools, and that they change with time (a case in point is the CLAWS -tagset for English, with several versions that merge the part-of-speech and morphosyntactic information -to various degrees). -Given that the English language has relatively poor inflectional -morphology, the decision to merge part-of-speech symbols with morphosyntactic features (as -in, e.g., CLAWS-7, where the value PPHO1 signals the 3rd person singular objective personal -pronoun) is fully justified as the most economical approach. For languages with more -robust inflection, the pos and msd attributes will either be used -separately, or the part-of-speech information will be merged into the morphosyntactic -description. The nature and description of these systems is outside the scope of these -Guidelines, but it has to be stressed that all the strategies adopted for linguistic annotation, -even at the lightweight level of complexity, must be documented in the header of the -given electronic resource, not only for the purpose of guaranteeing successful data interpretation and exchange, but -also for the sake of sustainability of the results of the given project.

- -

The last of the att.linguistic attributes, join, has the most text-technological -flavour. It can be used to amend the loss of whitespace-related information in non-inline -markup.

-

Compare the following two listings. The first difference between them is in the -tagset used (CLAWS-5 vs. CLAWS-7) and only serves to exemplify the need to document the -choice of descriptive vocabulary in the header, lest the encoded information is unreadable or -confusing. The second difference is the difference in the treatment of inter-token -whitespace, and it is here that the join attribute proves indispensable.

- -

The first example listing uses CLAWS-5 and inline annotation, where whitespace serves as -part of the markup: - -The victim's friends - told police that Kruger - drove into the quarry - and never surfaced. -

- -

In the second example, the attribute join is the only way to encode whether two -tokens are adjacent or not: - -The -victim -'s -friends -told -police -that -Kruger -drove -into -the -quarry -and -never -surfaced -.

-

Note that projects will need to decide whether they want to redundantly encode full -information on the adjacency of each token (in which case, the above listing should also -have join with the value right on the tokens -victim and surfaced, or whether information -on a single direction of adjacency is enough. Strategies vary, and it is important to -document them in the TEI header.

-

The following example shows a German sentence Wir fahren in den -Urlaub (We're going on vacation) annotated with all the attributes discussed -above.The annotation values have been adapted from the CLARIN Weblicht service, -where e.g. the full morphosyntactic description of the first item reads: [cat pronoun, -personal true, substituting true, person 1, case nominative, number plural], and has been -mapped from a sequence of attribute-value pairs suitable for feature structure notation, into a -compressed form that fits inside a single attribute value. - -Wir -fahren -in -den -Urlaub -. - - -

-

The final examples lay out a strategy for dealing with e.g. historical corpora where it is on -the one hand important to maintain a steady stream of token-level elements (w and -pc) for efficient processing, but, on the other hand, it is also important to -either record the original spelling (when the corpus text is normalized) or to record the -normalized variants (when the element content of the corpus preserves the original -spelling). The attribute class att.lexicographic.normalized can be used for that purpose: -

-

The first fragment below comes from "Gottfried, Newe Welt Vnd Americanische Historien. Frankfurt/M., 1631" -encoded in the Deutsches Textarchiv and records normalized forms in the norm attribute. - - vnuermuthete - Freundſchafft - angebotten -

-

The following example comes from the EarlyPrint project and uses the attribute orig to -record the original spelling (note that the xml:id attributes have been removed for the -sake of readability). - - he - hath - brought - forth -

-
-
Spoken Text -

The mechanisms proposed in this chapter may also be used to encode -analyses of an entirely different kind, for example discourse function. -Here is an application of the span technique to record details of a sales -transaction in a spoken text. -Can I have ten oranges and a kilo of bananas please? -Yes, anything else? -No thanks. -That'll be dollar forty. -Two dollars -Sixty, eighty, two dollars. Thank you. - - sale request - sale compliance - sale - purchase - purchase closure - -For further discussion of the u (utterance) element and other -elements recommended for transcriptions of spoken language, -see chapter . -

-
-
- Module for Analysis and Interpretation -

The module described in this chapter makes available the - following components: - - Analysis and Interpretation - Simple analytic mechanisms - Mécanismes analytiques simples - 簡易分析機制 - Semplici meccanismi di analisi - Mecanismos simples de análise - 分析モジュール - - The selection and combination of modules to form a TEI schema is - described in . - - - -

-
-
diff --git a/P5/Source/Guidelines/fr/AI-AnalyticMechanisms.xml b/P5/Source/Guidelines/fr/AI-AnalyticMechanisms.xml new file mode 120000 index 0000000000..98f2802ffd --- /dev/null +++ b/P5/Source/Guidelines/fr/AI-AnalyticMechanisms.xml @@ -0,0 +1 @@ +../en/./AI-AnalyticMechanisms.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/BIB-Bibliography.xml b/P5/Source/Guidelines/fr/BIB-Bibliography.xml deleted file mode 100644 index 885cba0cea..0000000000 --- a/P5/Source/Guidelines/fr/BIB-Bibliography.xml +++ /dev/null @@ -1,6369 +0,0 @@ - -
- Bibliography -
- Works Cited in Examples in these Guidelines - - - 阿城，《棋王》。 - Académie française, - Rectifications de l'orthographe - J.O. du 06-12-1990, En ligne, - consulté le 05-03-2010. - - Adams, Douglas. The Hitchhiker's Guide to the - Galaxy, New York: Pocket Books, 1979, - chapter 31. - Agence bibliographique de l'enseignement - supérieur, ABES:Site internet - par l'ABES,consulté le 05-03-2010. - 阿拉伯短劍，國史館：嚴家淦總統文物。 - Alighieri, Dante. Doglia mi - reca ne lo core ardire, Rime, XLIX. - Allinson, E.P. and B. Penrose. - Philadelphia 1681-1887 (1887), p. 138. - American National Standard for Bibliographic - References, ANSI Z39.29-1977, New York: American - National Standards Institute (1977). - - - - Andersson, Theodore M.. A Preface to the Nibelungenlied, - Stanford University Press (1987). - - Andrews, Mr.. Song, Chambers's - Edinburgh Journal Series 1 - 9:463 (12 - December 1840), 376. - - Anouilh, Jean, - Antigone, 1842. - - [As in Visions of] Single leaf of Notes for a poem about night "visions," - possibly related to the untitled 1855 poem that Whitman eventually titled "The Sleepers." - Fragments of an unidentified newspaper clipping about the Puget Sound area have been pasted - to the leaf. The Trent Collection of Walt Whitman Manuscripts, Duke University Rare Book, - Manuscript, and Special Collections Library. - - - Atkins et al. - Collins Robert French-English English-French Dictionary. - London: Collins (1978). - - Atkinson, J. Maxwell and John Heritage. Structures of social action: Studies in conversation analysis, - Cambridge and Paris: Cambridge - University Press, Editions de la Maison des Sciences de - l'Homme (1984), ix-xvi. - Austen, Jane. Pride and - Prejudice. (1813), chapter - 1. - - - - 白先勇，〈金大班的最後一夜〉，《台北人》。 - 白先勇，《孽子》。 - 白居易，《憶江南》。 - - Amheida I: Ostraka from Trimithis Volume 1: Texts from the 2004–2007 Seasons, - Bagnall, R. S. and G. R. Ruffini, with contributions by R. Cribiore and G. Vittmann - (2012). - - - Baker, James K.. Night in Tarras. In Hilltop: A Literary Paper, vol 1 no 2. Wellington: Victoria University College - Literary Society. (1949). - Balzac, Honoré de, - Les Chouans, 1845. - Balzac, Honoré de, - Le Père Goriot, 1843. - Balzac, Honoré de, Petites misères de la - vie conjugale, 1850. - Barbauld, Lucy Aikin. The Works of Anna - Laetitia Barbauld (1826). - - Barker, Jane. The Lining to the Patch-Work Screen - (1726). - - Base de datos paleográfica da lírica galego-portuguesa (PalMed). Versión 1.2. - Santiago de Compostela: Centro Ramón Piñeiro para a - Investigación en Humanidades. . - f. B126r, column a, l. 21-32. - - Bataille, Michel , - L'Arbre de Noël, 1967. - - Les Chats, in : Baudelaire, Charles, Les Fleurs du mal, 1861. - - La Vie antérieure, in : Baudelaire, Charles, - Les Fleurs du mal, 1861. - 電影《霸王別姬》，1993年。 - Beck, Béatrice, Léon - Morin, prêtre, 1952. - Beckett, Samuel. Waiting for - Godot, London: Faber and Faber - (1956). - Beckett, Samuel. Murphy - (1963), chap 2. - Becque, Henry, La - Parisienne. Edition - électronique par l'ATILF et le CNRTL, d'après - l'édition de Fasquelle (Paris, 1922). - - Bowers, Jack - Mixtepec-Mixtec Project Personography - - - - - Beerbohm, Max. Autograph manuscript of The Golden Drugget, - Pierpont Morgan MA 3391. in 123. - Behn, Aphra. The Rover, - (1697). - - Beeton, Isabella. The book of Household Management, - London: S.O. Beeton - (1861). - Belloc, Denis , - Képas, 1989. - - Belloc, Denis , Néons, 1987. - Bentham, Jeremy. The Book of - Fallacies. (1824). - - Beowulf and The fight at Finnsburg; edited, with introduction, bibliography, - notes, glossary, and appendices, by Fr. Klaeber. Boston, New York - [etc.] - D.C. Heath & Co. (1922). - - Bibliographie dans le cadre de la semaine italienne du 11 au 18 mars 2006, , - document électronique. - Bibliothèque nationale de - France, Projet de description des reliures remarquables de la Réserve des - livres rares selon le modèle de la TEI manuscrits. - Billetdoux, Marie, Un - peu de désir sinon je meurs, 2006. - - Blake, William. London, in Songs - of Experience (1791). - - Blake, William. The Sick Rose, in Songs of Experience (1794). - - Blake, William. The Tyger, in Songs of Experience (1794). - Bloomfield, Leonard. Literate and - Illiterate Speech, American Speech, 2, (1927), pp. - 432-441. - Borges, Jorge Luis, tr. R. - Simms. The Analytical Language of John Wilkins. In - Emir Rodriguez Monegal and Alistair Reid, eds. Borges: A reader, Dutton Adult - (1981), p.141. - Borges, Jorge Luis. Avatars of - the Tortoise In James E. Irby tr. Labyrinths: Selected Stories and Other Writings, New York: - New Directions, (1962), pp.202-203. - Bouillier, Grégoire, - Rapport sur moi, 2002. - Bresson, Robert, Mouchette : script, l'Avant-scène cinéma, - n° 80, avril 1968. - Extract from British National Corpus () Text KB7, sentence 13730. - - Brontë, Charlotte. Jane Eyre: An Autobiography, - Third edition; reprintLondon - Service & Paton, 1897; - Project Gutenberg, 1 December 2020. - chapter XII. - - - - Browning, Robert. Letter to George Moulton-Barrett, Pierpont - Morgan MA 310, ( 23). - Buirette de Belloy, Pierre Laurent, - Gabrielle de Vergy, 1777. - - Bunyan, John. The Pilgrim's Progress from this world to that which - is to come..., London (1678). - Burgess, Anthony. A Clockwork - Orange. (1962), opening. - Burnard, Lou. Principles of - Database Design in S. Rahtz. ed. Information - Technology in the Humanities: tools, techniques and applications, Ellis - Horwood Ltd, Ellis Horwood Series in Computers and Their - Applications, (1987), p. 54. - Burnard, Lou, - Sperberg-McQueen, C. M., - <ref target="http://www.gutenberg.eu.org/publications/autres/TEILITE/">La TEI simplifiée, - une introduction au codage des textes électroniques en vue de leur échange -- version de - travail </ref> - , 1996. - - Burton, Robert. Anatomy of Melancholy - (1621), 16th ed. reprinted 1846, p. 743. - Butler, Samuel. The Way of All - Flesh (1903), chapter 37. - Byron, George Gordon. Don Juan - (1819), I.xxii. - Byron, George Gordon. Vision of - Judgment In E.H. Coleridge ed. The Poetical - Works of Lord Byron, viii, 1922. - - - - C 60/16 Fine Roll 6 HENRY III (28 October 1221-27 - October 1222), membrane 5, entry 154. - CBETA - Cædmon's Hymn in Bede's Historia Ecclesiastica (MS Kk. - 5. 16, Cambridge, University Library). - - Cabaret. A musical play, with book by Joe Masteroff, lyrics by Fred Ebb, and - music by John Kaner. Based on the play by John van Druten and stories by Christopher - Isherwood. 1966 - Edward Barkley, describing how Essex drove the Irish from the - plains into the woods to freeze or famish in winter; quoted by Canny, Nicholas - P. - The Ideology of English Colonization: From Ireland to America. In - Stanley N. Katz and John M. Murrin eds. Colonial America: Essays in Politics and Social Development, 3d - ed - New York: Knopf, (1983), p.53. - - - Carroll, Lewis. Through the Looking Glass, and what Alice - found there. (1871). - Catéchisme de l'Eglise - catholique, 1968. - - Cavendish, Margaret. Nature's Pictures. - London, 1656. Women Writers Online. Women - Writers Project, Northeastern University. 29 Mar. - 2015. - Centre national de la recherche scientifique - (France). UMR 7118 ATILF, <ref target="http://atilf.atilf.fr/tlf.htm">Le - Trésor de la Langue Française Informatisé (TLFI)</ref>, - 2004. - Example recoded from Chafe, W. - Adequacy, user-friendliness, and practicality in transcribing In - Leech, G., G. Myers, J. Thomas eds. - Spoken English on Computer: Transcription, Markup and - Applications. Harlow: Longman, - 1995. - - Chandler, Lloyd. - Conversation with Death (also known as Oh, - Death). In Journal of Folklore Research, 41.2/3, (2004), pp. - 125-126. - Chapman, Graham, Cleese, John, - Gilliam, Terry, Idle, Eric, Jones, - Terry. The complete Monty Pythons Flying Circus. - Chapman, Graham, Cleese, John, - Gilliam, Terry, Idle, Eric, Jones, - Terry. Monty Python's Life of Brian (1979). - - - Chaucer, Geoffrey. Canterbury Tales, f52r, in Holkham MS. - - Chaucer, Geoffrey. The Tale of Sir Topas, The Canterbury Tales, In F. N. Robinson ed. The Works of Geoffrey Chaucer, 2nd edition - Boston: Houghton Mifflin Co., - 1957. - 陳政彥，〈戰後臺灣現代詩論戰史研究〉，2007。 - - Cholières, Nicolas de, La Forest Nuptiale - (1600). - - Chomsky, Noam and Morris Halle. The Sound Pattern - of English. New York: Harper & Row (1968), p. 415. - Claude Simon - Le jardin des plantes, 1997, p 284 - - Cleaver, Eldridge. Soul on Ice. New - York (1968). - - Cloud of Unknowing In Hodgson, Phyllis ed. The Cloud of Unknowing and The Book of Privy Counselling, - London: Oxford University Press, Early - English Text Society, 218, (1944). - Clover, Carol J.The Medieval - Saga, Ithaca: Cornell University Press - (1982). - - Cocteau, Jean. La Machine Infernale. - Coleridge, Samuel Taylor. The - Rime of the Ancient Mariner. In Wordsworth, William and - Samuel Taylor Coleridge. Lyrical Ballads - (1798). - Coleridge, Samuel Taylor. Frost at - Midnight In E.H. Coleridge ed. Poetical - Works, Oxford: Oxford University - Press, (1967), p.240. - Colette, Colette à - l'école, 1900. - - Collins English Dictionary, 12th edition - Glasgow: Collins - (2014). - - Collins Pocket Dictionary of the English language. - London: Collins. - - Collins, Wilkie. The Moonstone, - Penguin, 6th narrative. - - Comenius, John Amos. Orbis Pictus: a facsimile of the - first English edition of 1659 (ed. John - E. - Sadler - ) Oxford University Press (1968). - Cope, Thomas Pym. Philadelphia - merchant: the diary of Thomas P. Cope, 1800-1851, Eliza Cope - Harrison ed. - Corneille, Pierre, - La Place Royale ou L'Amoureux extravagant, 1637. - Corneille, Pierre, - Théodore, vierge et martyre : tragédie chrétienne, - 1646. - - Cowley, Hannah. The Runaway (1813). - - Crashaw, Richard, ed. J.R. Tutin. The - Poems of Richard Crashaw. Muses Library Edition: - (1900). - - Creeley, Robert - A counterpoint in For Love: Poems 1950-1960 - (1962). - 崔西．雪佛蘭。《戴珍珠耳環的少女》。台北：皇冠，2003。 - - - - Dallas, George Mifflin. Unpublished - letter cited in Russell F. Weigley, Nicholas B. - Wainwright, Edwin Wolf eds. Philadelphia: A 300 - Year History, New York and London: - W. W. Norton & Company, 1982, p. 349. - Danhauser, Adolphe-Leopold, - Théorie de la musique, 1872. - - Darwin, Charles. Narrative of the Surveying Voyages of His Majesty's - ships Adventure and Beagle... volume 3 : Journal and Remarks (The Voyage of the - Beagle), chap 3. 1839. - Daudet, Alphonse, Les - contes du lundi, 1873. - - Davenant, William. The vvitts. A comedie, presented at the - private house in Blacke Fryers, by his Majesties servants. The author VVilliam D'avenant, - servant to Her Majestie. - London, 1636. [STC S109311] - - De Nutrimento et Nutribili, Tractatus 1, fol 217r col b of Merton College - Oxford MS O.2.1; in pl. 16. - - Dean of Sarum Churchwardens' presentments, 1731, Hurst; Wiltshire Record - Office; transcribed by Donald A. Spaeth. - Defoe, Daniel. The Fortunes and - Misfortunes of the Famous Moll Flanders (1722). - Defoe, Daniel. Robinson - Crusoe (1719). - - Defoe, Daniel. Journal of the Plague Year. - London (1722). - - Dekker, Thomas and Thomas Middleton. The Honest - Whore, Part One (1604). - Deloney, Thomas. Thomas of Reading or the - Sixe Worthie Yeomen of the West (1612). - Dennery, Annie. Du mélos à la note : Les notations musicales au Moyen Age, Médiévales, n° 3 - 1983. - Dickens, Charles. A Christmas - Carol in Prose, Being a Ghost Story of Christmas, Chapman and - Hall, (1843), p. 5, p. - 12. - Dickens, Charles. Little - Dorrit, (1857). - Dickinson, Emily. 1755 In - Arthur Eastman et al. eds. The Norton Anthology of - Poetry, New York: W.W. Norton, - 1970, p.859. - Diderot, Denis, - Lettres à Sophie Volland, 26 sept. 1762. - 〈第三屆第一次大會第一次會議記錄〉，臺灣省諮議會。 - Disraeli, Benjamin. Coningsby (1844), preface. - Doyle, Arthur Conan. The - Red-headed league. In The Adventures of Sherlock Holmes - (1892). - - Doyle, Arthur Conan. The Original Illustrated Sherlock - Holmes, Castle Books, 1989. - Drawing of a leaden plaque bearing an inquiry by Hermon from the - oracular precinct at Dodona. Catalogue no 725; LSAG 230.13. Image from - Dubois, Jacques, Nyssen, - Hubert (dir. de collection), Babel, Actes - sud,1989-.... - Dubois, Jean, - Dictionnaire de linguistique, 1974. - - Dudo of St Quentin. De moribus et actis primorum Normannie - ducum, fol 4v of British Library MS Harley 3742; in pl - 6(i). - Dufournaud, Nicole, - Numérisation des Titres de famille, édition électronique, 2002. - Duhamel, Georges, - Chronique des Pasquier, 1933-1945. - - Dutt, Toru. Lakshman In Ancient - Ballads and Legends of Hindustan, Kegan Paul, Trench & - Co., (1882) - Dylan, Bob. All Along the - Watchtower In John Wesley Harding - (1967). - Dylan, Bob. Positively 4th - Street In Highway 61 Revisited - (1965). - - - - - Eddic poems, in Reykjavík, Landsbókasafn Íslands, Lbs 1562 4to. - Editorial, .EXE - magazine, 6.11 (1992), - p. 2. - Eliot, George. Middlemarch (1871), I.1. - - Eliot, George. Middlemarch (1871), - I.XXI. - - Eliot, George. Daniel Deronda (1876), - III.1. - Eliot, Thomas Stearns. The - waste land: a facsimile and transcript of the original drafts including the annotations of - Ezra Pound, Eliot, Valerie ed. Faber and Faber - Ltd. (1971), p. 37. - - Scalable Vector Graphics (SVG) 1.1 (Second Edition). Editors - Erik Dahlström, Jon Ferraiolo, 藤沢 淳, Anthony Grasso, Dean - Jackson, Chris Lilley, Cameron McCormack - Doug Schepers, Jonathan Watt and Patrick - Dengler. World Wide Web Consortium (W3C) (22 June - 2010). Available from . - Ernaux, Annie, Se - perdre, 1988. - Ernaux, Annie, L'usage - de la photo, 2005. - - - <ref target="http://www.etudes-litteraires.com/figures-de-style/deictique.php">Études - littéraires</ref> - , consulté le 07-05-2010. - - - - Fallet , René, Le - Triporteur, 1951. - Field, Syd - Screenplay: the Foundations of Screenwriting (1998). - Fielding, Henry. The History of - the Adventures of Joseph Andrews and his Friend, Mr. Abraham Abrams - (1742). - - Fielding, Henry. Tragedy of Tragedies, - (1737). - - Fish, Stanley. Is there a text in this class? The authority of - interpretive communities. Harvard University Press - (1980). - Fisher, M. F. K. I Was Really Very - Hungry In As They Were, Knopf - (1982), p. 43. - - - FitzGerald, Edward. The Rubáiyát of Omar Khayyám, translated into - English Verse (1859), stanza 25. - Flaubert, Gustave, - Salammbô, 1862. - Flaubert, Gustave, - La Tentation de saint Antoine, 1874. - Foley James D., Andries van Dam, - Steven K. Feiner and John F. Hughes. Computer Graphics: Principles and Practice, 2nd edition - Reading: Addison-Wesley, p.259. - Forster, E.M., Howards - End. Edward Arnold. (1910). - - - <ref target="http://sites.radiofrance.fr/franceinter/em/labassijysuis">France inter, - Là-bas si j'y suis</ref> - , consulté le 07-05-2010. - - - <ref target="http://sites.radiofrance.fr/franceinter/em/letelephonesonne/contact.php" - >France inter, Le téléphone sonne</ref> - , consulté le 07-05-2010. - - - <ref target="http://franglais.ini.hu/">Franglais et franricain</ref> - , consulté le 07-05-2010. - Fry, Christopher, The firstborn - (1948). - 福春嫁女 - - Fussell, Paul. The Norton Book of Travel. W. W. - Norton (1987). - - - - Galilei, Galileo, Sidereus - Nuncius, Venetiis: Apud Thomam - Baglionum, 1610, quoted by Tufte, Edward R., - Envisioning Information, Cheshire: - Graphics Press (1990), p. - 97. - Galland, Antoine, Les - Mille et une nuits, 1704. - Galsworthy, John, Strife. In - Plays, vol 1. (1909). - Gaskell, Elizabeth Cleghorn. The Grey Woman, MS. - Gavioli, Laura and Gillian - Mansfield. The PIXI corpora: bookshop encounters in English and - Italian, Bologna: Cooperativa Libraria - Universitaria Editrice (1990), p.74. - Gay, John. The Beggar's Opera - (1728). - Gazdar, Gerald and Mellish, - Christopher. Natural language processing in Prolog. - Addison-Wesley (1989), p.5. - - Gazdar, Gerald, Ewan Klein, Geoffrey Pullum, and Ivan Sag: - Generalized Phrase Structure Grammar, Harvard - University Press (1985). - - Gershwin, Ira - By Strauss (from An American in Paris, 1953). - Gianfraco Contini, Poeti del - Duecento, Milano-Napoli:Ricciardi I, (1960). pp 155-64. - Gibbon, Edward, The History of the - Decline and Fall of the Roman Empire, (1789), chapter 58. - Gide, André, Le - Journal des Faux-Monnayeurs, 1927. - Gide, André, Journal : - 1889-1939, 1939. - - Gilbert, William Schwenck and Sullivan, Arthur. HMS Pinafore (1878), I. - Gilbert, William Schwenck and Sullivan, - Arthur. The Mikado (1885). - Ginsberg, Allen. My alba, - Reality Sandwiches, San Francisco: - City Lights, (1963). - Giono, Jean, - Regain, 1930. - Giraudoux, Jean, La - guerre de Troie n'aura pas lieu, 1935. - - Godefroy, Frédéric, Dictionnaire de l'ancienne langue française et - de tous ses dialectes du IXe au XVe siècle, 1881. - Goethe, Johann Wolfgang von, tr. Philip Wayne. Faust, Part - 1, London: Penguin. (1949). - - Goethe, Johann Wolfgang von. Auf dem See - (1775). - - [Goldsmith, Oliver], The History of Little GOODY TWO-SHOES; - Otherwise called, Mrs. MARGERY TWO-SHOES... (Printed for J. Newbery, - 1766). - - Grallert, Till, Tools for the Computational Normalisation and - Analysis of Food Prices and Food Riots in the Eastern Mediterranean (Bilād al-Shām) in the - 19th and 20th Centuries. Zenodo, 2021. . - - Graves, Robert. Rough draft of letter to Desmond Flower. - 17 Dec 1938. (from Diary of Robert Graves 1935-39 and - ancillary materials, compiled by Beryl Graves, C.G. Petter, L.R. Roberts, - University of Victoria Libraries). - - Greene, Robert. Groatsworth of Wit Bought with a Million - of Repentance (1592). - - Gregory of Tours. Ecclesiastical History of the - Franks (translated by Lewis Thorpe). - Greimas, Algirdas Julien - et Courtés, Joseph, Sémiotique : dictionnaire raisonné de la théorie - du langage, 1979. - Grune, Dick and Ceriel J. H. - Jacobs. Parsing Techniques: A Practical Guide, - New York and London: Ellis - Horwood, 1990, p. 24. - - Guerard, Françoise. Le Dictionnaire de Notre Temps, ed. - Paris: Hachette, 1990 - - - - - Hall, Radclyffe. The well of - loneliness. (1928). - Halliday, M.A.K. and R. - Hassan. Language, Context and Text: Aspects of Language in a - Social-Semiotic Perspective, Oxford: Oxford - University Press, 1990, p. - 104. - Hanks, Patrick. Definitions and - Explanations. In J. M. Sinclair ed. Looking Up. - Collins, 1987, p. 121 - . - Hannam's last farewell to the world:: being a full and true - relation of the notorious life and shamfull death of Mr. Richard Hannam... - (1656). - - Hansberry, Lorraine. A raisin in the sun. - (1959). - Harvey, Gabriel. Four letters and certain - sonnets specially touching Robert Greene... (1592). - Harvey, William. Exercitatio Anatomica De Motu Cordis Et Sanguinis In Animalibus, 1949 (Third edition, second printing), p. 74. - Hobbes, Thomas. Leviathan - (1681). - 《紅樓夢》第六回：賈寶玉初試云雨情 劉姥姥一進榮國府 - 〈紅頭嶼踏查報告〉，國立台灣大學圖書館：田代文庫。 - Hoola Van Nooten, - BertheFleurs, fruits et feuillages choisis de l'île de Java peints d'après - nature, troisième édition par C. Muquardt, Bruxelles, - 1880. - - Hornby, A.S. et al. Oxford Advanced Learner's Dictionary of Current - English. Oxford University Press (1974). - 黃晨淳編著，《希臘羅馬神話故事》，p76。 - Hugo, Victor, - Notre-Dame de Paris, 1845. - - Souvenir de la nuit du 4, in : Hugo, Victor, - Les Contemplations, 1853. - Hugo, Victor, Les - Misérables, 1862. - - A la fenêtre pendant la nuit, in : Hugo, Victor , - Les Contemplations, 1856. - Huizinga, Johan, - L'Automne du Moyen-Âge, 1919. - - - - ISO 690:1987: Information and documentation – - Bibliographic references – Content, form and structure - clause 4.1, p.2. - ISO 24611:2012 Language resource management — Morpho-syntactic annotation framework (MAF). - International Organization for Standardization. 2012. - - Ibsen, Henrik, tr. William and Charles Archer. - Peer Gynt (1875). - - Ibsen, Henrik - Den episke Brand KBK Collin 2869, 4º I, fol. 11v. - - Ibsen, Henrik - Digte NBO Ms.4º 1110a, p. 36. - - Ibsen, Henrik - Brand, The Royal Library, Denmark. KBK Collin 262, 4°, I.1.1, fol. - [4]v - Ibsen, Henrik, tr. R. - Farquharson Sharp and Eleanor Marx-Aveling. - A Doll's House In A Doll's House; and Two Other - Plays by Henrik Ibsen, Everyman's library: the drama 494 - , London: J. M. Dent & Sons, - 1910. - Idle, Eric, Michael Palin, - Graham Chapman, John Cleese, Terry - Gilliam. The Complete Monty Python's Flying Circus: All the - Words, Pantheon Books, (1989), 2, p.230. - Imbs, Paul, Martin, - Robert, Straka, Georges, Mélanges de linguistique - française et de philologie et littérature médiévales offerts à Monsieur Paul - Imbs, 1973 . - Institut de Littérature Française Moderne de - l’Université de Neuchâtel, Présentation du projet Cyrus, En ligne, consulté le - 05-03-2010. - Ionesco, Eugène, La - cantatrice chauve, 1950. - 羅貫中，《三國演義》。 - - - - - Jakacki, Diane. Schema question: further constraining - @subtype based on @type. January 18, - 2021. TEI (Text Encoding Initiative) public discussion - list, . - Jarry, Alfred, tr. Simon Watson - Taylor and Cyril Connolly. The Ubu - plays, London: Methuen, - 1968. - Jean-Jacques Rousseau - Les confessions vol 6 - Jerome, Jerome K. - Three men in a boat (1889), chapter 6. - Joachim Heinrich - CampeWörterbuch der Deutschen Sprache. Erster Theil. A - bis - E., - 1807. - John, Lord Sheffield, The - Auto-biography of Edward Gibbon esq., (1846), 222. - Jonson, Ben. Bartholomew - Fair. - Jonson, Ben. Volpone, - J. B. Bamborough ed. Macmillan, 1963, - p.14. - Jonson, Ben. The Alchemist - , Douglas Brown ed. London: - Benn, 1966, I.1, - p.9. - Joyce, James. Ulysses: - The Bodley Head, 1960. p. - 933. - - Judith Patt, Michiko Warkentyne and Barry - Till. Haiku: Japanese Art and Poetry. 2010. - Pomegranate Communications, Inc. San Francisco. . - - - - - Karlstadt, Andreas - Bodenstein. Distinctiones Thomistarum. - Wittenberg - 1507. In Harald Bollbuck ed. Kritische Gesamtausgabe - Karlstadt - I, available: - - Kersey, John. Dictionarium - Anglo-Brittannicum: Or, a General English Dictionary. London: - J. Wilde, 1715. 2nd ed. - Kilian, Wilfrid, <ref - target="http://jubil.upmc.fr/sdx/pl/toc.xsp?id=GH_000484_001&fmt=upmc&idtoc=GH_000484_001-pleadetoc&base=fa" - >Neige et glaciers ; notes prises au cours de géologie de la Faculté des Sciences de - Grenoble par M. Alamelle</ref>, 1891-1895. - King, Martin Luther. Letter from Birmingham City - Jail. Philadelphia, PA: American Friends Service - Committee (1963). - Kipling, Rudyard. The mother - hive. In Actions and Reactions, - London: Macmillan, (1909). - - Kipling, Rudyard. Stalky & Co., - London: Macmillan (1899). - Kipling, Rudyard. Kim, - Macmillan, (1901), p. - 9. - Knuth, Donald Ervin. The Potrzebie - System of Weights and Measures, Mad Magazine33June 1957. - Koltès, - Bernard-Marie, Quai ouest, 1985. - Krummrey, Hans, Panciera, Silvio - Criteri di edizione e segni diacritici, Tituli 2 (1980), - 205-215. - Kyd, Thomas. Spanish Tragedy - (1592). - - - - La Fayette, Marie-Madeleine Pioche - de La Vergne, comtesse de, La Princesse de Clèves, - 1678. - La Fontaine, Jean de. L'Astrologue - qui se laisse tomber dans un puits In Fables Choisies, - Classiques Larousse, Paris: Librairie - Larousse, 1, 1940. - La Fontaine, Jean de. Le corbeau - et le renard In Fables Choisies, Classiques - Larousse, Paris: Librairie Larousse, - 1, 1940. - Laboratoire ATILF - - <ref target="http://www.atilf.fr/">Analyse et traitement informatique de la langue - française (ATILF)</ref> - , consulté le 07-05-2010. - - Laclos, Pierre Choderlos de. Les Liaisons - dangereuses (1772), 1963, p. - 13. - Ladurie, Emmanuel Le Roy. Montaillou, Middlesex: Penguin Books, - 1980, p. 3. - Lamartine, Alphonse de, - Méditations poétiques, 1820. - Lamothe, Alexandre - de - Principaux manuscrits latins et français conservés dans la Bibliothèque - impériale et dans celle de l'Ermitage à Saint-Pétersbourg, édition numérique, Bibliothèque de l'école nationale des - chartes, 1864. - Langendoen, D. Terence and Paul M. - Postal. Vastness of Natural Languages, - Oxford: Basil Blackwell, 1984, p. - 24, note 12. - Langendoen, D. Terence and Paul Postal. The - vastness of natural languages, Blackwell, , 1, 1984. - - Langland, William. The Vision of Piers Plowman. In - A.V.C. Schmidt ed. Langland: Vision of Piers Plowman: - "B" Text, opening. - Latin liturgical manuscript: Bod MS. Lat liturg. b. - 19, folio 4r. Taken from the digitized image described at . - Lavrentev, Alexei, - <ref target="http://ccfm.ens-lsh.fr/IMG/pdf/BFM-Mss_Encodage-XML.pdf">Manuel - d’encodage XML-TEI étendu des transcriptions de manuscrits dans le projet - BFM-Manuscrits</ref>, dernier enregistrement le 26 juin - 2008. - - Lawrence, David Herbert. Autograph manuscript of Eloi, Eloi, lama - sabachthani, Pierpont Morgan MA 1892; in p.129. - - Layamon. Brut, fol 65v of Bodleian MS. Rawlinson Poetry 32; - in 12(ii). - Le Grand Robert de la langue - française, 2004. - LeTourneau, Mark S. - English Grammar, 2001, New York: - Harcourt - p. 89. - - Leech, G., G. Myers, J. Thomas eds. - Spoken English on Computer: Transcription, Markup and - Applications. Harlow: Longman, - 1995. - Leech, Geoffrey and Mick Short. - Style in Fiction, London: - Longman, 1981, p.272. - - Lennon, John and McCartney, Paul. She - Loves You. The Beatles Anthology 1. - Capitol, 1995. - Léry, Jean de, Histoire faict - en la terre de Brésil, 1580. - - Lessing, Doris. Martha Quest. 1952, - pp. 52-53. - Letter of Mikołaj Orlik to Mikołaj Serafin, Gródek, January 13 - [1438]. Edited by Skolimowska et al. Available from - Lewis, Leopold Davis. The - Bells, (1871), translated from Erckmann-Chatrian, - Le Juif Polonais. - - Lewis, Wyndham. Tarr (1928), - Jupiter, 1968, p. 17. - 李白，《黃鶴樓送孟浩然之廣陵》。 - 李白，《靜夜思》。 - 《梁山伯與祝英台》 - 電影《梁山伯與祝英台》，舊版。 - 〈歷代漢文大藏經概述〉，李圓淨，原載《南行》第六期（南行學社編印）。 - Lillo, George. The London - Merchant (1731), epilogue. - 林覺民，《與妻訣別書》。 - Lincoln, Abraham. Second Inaugural - Address, 4 March 1865. In H. S. Commager, ed., - Documents of American History, 5th ed - Crofts American history series. New York: - Appleton-Century-Crofts, 1949, p.442. - 劉康，《對話的喧囂：巴赫汀文化理論評述》，台北：麥田，2005，二版。 - 劉康，《對話的喧聲：巴赫汀文化理論述評》，台北：麥田，2005，頁20-23。 - - Longman Dictionary of Contemporary English. Harlow, - Essex: Longman (1978). - Lorris, Guillaume de et - Meun, Jean deLe Roman de la Rose, 1230, - 1270-1285. - Lowe, David. Lost - Chicago, Boston: Houghton Mifflin, - (1978), p.30. - - Lowell, Amy. Autumn - haze.(1919). - Lucie Lichtig, M. - Klein de Joseph Losey : script, . l'Avant-scène cinéma, - n° 175, nov. 1976. - Luther, Martin [tr]. Die gantze - Heilige Schrifft Deudsch, Wittenberg 1545. Letzte zu Luthers Lebzeiten erchienene Ausgabe, - hsg. Hans Volz unter Mitarbeit von Heinz Blanke. Textredaktion Friedrich Kur, - München: Rogner & Bernhard, - 1972. - 《論語》卷七：憲問第十四。 - 羅貫中，《三國演義》。 - 魯迅，《狂人日記 》。 - 魯迅，《狂人日記》。 - 魯迅，《狂人日記》。 - - - - MacNeice, Louis. The Sunlight on - the Garden In E.R. Dodds, - The collected poems of Louis MacNeice, London: - Faber, 1966. - Examples from MacWhinney, Brian, 88, 87, cited by Johansson, S. - The approach of the Text Encoding Initiative to the encoding of spoken - discourse In Leech, G., G. Myers, J. - Thomas eds. Spoken English on Computer: Transcription, Markup - and Applications. Harlow: Longman, - 1995. - - Madan, Falconer, et al, A summary catalogue of western manuscripts - in the Bodleian Library at Oxford which have not hitherto been catalogued ... - Oxford, 1895-1953. 5: 515. - Cited in Driscoll, M.J. P5-MS: A general purpose tagset for - manuscript description in Digital Medievalist: - 2.1, (2006) - - Maingeneau, Dominique, - Analyser les textes de communication, 2007. - Any issue of the Malawi Daily Times. - - Malle, Louis, Zazie - dans le métro : script, l'Avant-scène cinéma, n° - 104, juin 1970. - - Manuélian, Hélène, Schang, Emmanuel, XML, DTD et - TEI pour un dictionnaire étymologique des créoles, édition électronique, - 12 Octobre 2007. - - The Manere of Good Lyuynge: fol. 126v of Bodleian MS Laud Misc 517; - in , p.8. - Marbury v. Madison, 1 Cranch, - 137 (1803), rpt. In H. S. Commager, ed., Documents of American History, 5th ed - Crofts American history series. New York: - Appleton-Century-Crofts, 1949, - p.192. - Marvell, Andrew. An Horatian - Ode, Bod. MS Eng. Poet d.49. - Mauriac, Claude, - La Marquise sortit à cinq heures, 1961. - Mauss, Marcel, - Sociologie et anthropologie, 1950. - McCarthy, Niall, No - Parachute: The Highest Falls People Survived, Statista, - November 18, 2020. . - McCarty, Willard. Introduction in Collaborative Research in the Digital - Humanities: A volume in honour of Harold Short on the occasion of his 65th - birthday, September 2010, ed. Marilyn Deegan and Willard - McCarty. London: Ashgate - (2012). - Melville, Herman, Moby - Dick. (1851). - Mendès-France, Pierre, - Œuvres complètes, 1984-1985. - 《孟子》〈三十三〉。 - - Miller, Henry. Death of a Salesman in - Atkinson, Brooks, - New Voices in the American Theatre, New York: - Modern Library, 1955, p.113. - - Milne, A. A. - The House at Pooh Corner. London: - Methuen & Co., 1928, p. - 83. - - Milton, John. Paradise Lost: A poem in X books - (1667), I, 1-10. - Milton, John. Poems of Mr John Milton, both - English and Latin... (1645). - Molière, L'École des - femmes, 1663. - Molière, Le Médecin - malgré lui, 1667. - Molière, Le Médecin - volant, 1673. - Montaigne, Michel de, - Essais, 1592. - Montesquieu, Charles-Louis de Secondat, - baron de la Brède et de, Lettres persanes, - 1721. - Montherlant, Henry de , - Pitié pour les femmes, 1936. - - Moore, George. Autograph manuscript of Memoirs of my dead - life, Pierpont Morgan MA 3421; in - - Moore, Thomas. Autograph manuscript of the second version of Lalla - Rookh, Pierpont Morgan MA 310; in 23. - - Moreland, Floyd L. and Rita M. Fleischer. Latin: An - Intensive Course, (1977) p.53. - - Des Minnesangs Frühling, Moser, Hugo, Helmut - Tervooren eds. 36., neugestaltete und erweiterte Auflage - I Texte, Stuttgart: S. - Hirzel Verlag, 1977. - Mošin, Vladimir A. Anchor Watermarks. - Amsterdam: Paper Publications Society (Labarre Foundation), 1973. - Monumenta Chartæ Papyraceæ Historiam Illustrantia; v. 13. - Mréjen, Valérie, Eau - sauvage, 2004. - - Zuigan calls himself "Master". Mumon Ekai. (In - The Gateless Gate, Case 12.) - Mustafa Siddik Altinakar, - René Walther (éds.), Hydraulique fluviale. Tome 16, Écoulement et - phénomènes de transport dans les canaux à géométrie simple , - 2008. - Mégnin, Michel (éd.), Tunis - 1900 Lehnert & Landrock photographes,2005. - - Nabokov, Vladimir - Pnin (1953) , p.14 - - - The New Penguin English Dictionary. London: - Penguin Books (1986). - - Derived from - New Zealand Parliament, Legislative Council. Nga Korero Paramete: 1881-1885 - (New Zealand Electronic Text Collection). 2008 - Wellington, New Zealand. - . - - - Njal's saga. tr. Magnus Magnusson and Hermann - Palsson. Penguin. (1960), chapter - 12, p.60. - - O'Casey, Sean. Time to go (1951). - Ollagnier, Jeanne, - Main, 2008. - Herodotus. On Libya, from the - Histories. - - [Letter of Capt. E. Hopkins. Providence, 10 Sep 1764] - - "[I am a curse]" in Original Manuscript Drafts for the Song of - Myself, Collection MSS3829, part of the Papers of Walt Whitman, Clifton Waller - Barrett Library of American Literature, Albert and Shirley Small Special Collections - Library, University of Virginia. - Ormesson, Jean d', La Douane de mer, 1993. - - Orwell, George. Nineteen-Eighty-Four. - London: Gollancz (1949). - - 大隅亜希子. 1996. 律令制下における権衡普及の実態: - 海産物の貢納単位を中心として. 史論 - 49. pp. 22–44. . - - Owen, Wilfred. Dulce et decorum est, from autograph - manuscript in the English Faculty Library, Oxford University. - - Owenson, Sydney. The Wild Irish Girl. Ed. - Kathryn Kirkpatrick. Oxford: Oxford - University Press, 1999, p. 17. - - - - 擺夷文經，中央研究院歷史語言研究所 。 - Pascal, Blaise, Le Mémorial, in Pensées,1670. - - Payne, J. - Report on the compatibility of J P French's spoken corpus transcription - conventions with the TEI guidelines for transcription of spoken texts, Working Paper, Dec 1992, NERC WP8/WP4 122. - - Peacock, Thomas Love. Gryll Grange - (1861), chapter 1. - Pennac, Daniel , - La Petite marchande de prose, 1978. - Perec, Georges, Espèces - d'espaces, 1974. - Perec, Georges, La Vie - mode d'emploi : romans, 1978. - Perec, Georges , Les - Choses, 1965. - Partial family tree for Bertrand Russell - based on an example in Pereira, Fernando C.N. and Stuart M. - Shieber, Prolog and Natural Language Analysis, - Stanford: Center for the Study of Language and - Information. (1987), p.22. - Pernoud, Régine, La - Femme au temps des Cathédrales, 1982. - Perreault, Simon, vCard Format Specification - Internet Engineering Task Force (IETF) (2011). - . - - Petit Larousse en Couleurs. Paris: - Larousse, (1990). - - Philipott, Thomas - Poems. (1646). - - Pinsky, Robert. Essays on Psychiatrists in Sadness and Happiness (1975). - Pix, Mary. The False Friend - (1699). - Plautus, Titus Macchius. Asinaria, or the - Comedy of Asses. Edited and translated by Wolfgang de Melo. Loeb - Classical Library 60. Cambridge, MA: Harvard University - Press (2011). - Plautus, Titus Macchius. Menaechmi. - Polac, Michel, Un - fils unique : script, l'Avant-scène cinéma, n° - 99, janvier. 1970. - - Pope, Alexander. The Rape of the Lock - (1714) III.7. - Pope, Alexander. An Essay on - Criticism (1711). - Pope, Alexander. Dunciad Variorum - (1729), III.284. - From letter 'JK' found in Poulson's Daily - Advertiser, - 8 Oct 1835. - Proust, Marcel, A la - recherche du temps perdu : Du côté de chez Swann, 1913. - Queneau, Raymond. Exercices de - style. Paris: Gallimard, - (1947), p. 192. - - - - 瓊瑤，《還珠格格》。 - Queneau, Raymond , - Journaux, 1914-1965. - - - - Rabelais, François. - Gargantua Lyon, 1542 - Rabelais, François - Tiers livre des faictz et dictz Heroïques du noble Pantagruel... - (1546), adapted from the website at - Renard, Jules, - Journal : 1887-1910, 1910. - Reference from the bibliography in Reps, Thomas - William and Teitelbaum, Tim eds. The - Synthesizer Generator: A system for constructing language-based editors, - New York and Berlin: - Springer-Verlag, 1989, p.304. - 日本法隆寺貝葉心經 (Wikipedia Sept 2008). - Richardson, Samuel. Clarissa; - or the History of a Young Lady (1748), 2 Letter XIV. - - Robert, Paul. Le Petit Robert. Paris: - Dictionnaires Le Robert (1967). - Rohmer, Eric, Ma nuit chez Maud : script, l'Avant-scène cinéma, - n°98, 2001. - Romains, Jules, - Knock, 1923. - Rostand, Edmond, Cyrano de - Bergerac, 1898. - Roubaud, Jacques, La - Boucle, 1993. - Rowling, J. K. - The Sorting Hat. In Harry Potter and the - Sorcerer's Stone, New York: Scholastic, Inc. (1999), chapter - 7, p. 121. - - - - - The Saga of the Volsungs: the Norse epic of Sigurd the Dragon - Slayer. trans. Jesse L. Byock. University of - California Press (1990). - Le Sanctoral du lectionnaire de - l'office dominicain (ms. Rome, Sainte-Sabine XIV L 1, f.142r et 189r-230v, Ecclesiasticum - officium secundum ordinem fratrum praedicatorum), édition électronique par - l'Ecole nationale des chartes, d'après l'édition d'Anne-Élisabeth - Urfels-Capot (Paris : Ecole nationale des chartes, 2007). - - 崎山理. 1985 - インドネシア語. 講座日本語学 - 11. 外国語との対照II. - 東京:明治書院 - 61-80 - - 三毛，〈沙漠中的飯店〉，《撒哈拉的故事》。 - 《三家詩鈔》，華培昌，藏於國家圖書館。 - Sapir, Edward. Language: an - introduction to the study of speech, New York: - Harcourt, Brace and World, 1921, p.79. - Shakespeare William, - Richard III, 1597. - Shakespeare, William. Henry V - In Mr. William Shakespeares Comedies, Histories, & Tragedies, - London: Jaggard and Blount, - 1623. - Shakespeare, William. Henry V - In The Works of Shakespeare in seven volumes, ed. Lewis - Theobald, London: Bettesworth, Hitch, Tonson et - al, (1733). - Shakespeare, William. Antony and - Cleopatra, IV.4, 14-21. - Shakespeare, William. Merchant of - Venice, I.ii, speech 5 (Portia). - Shakespeare, William. Macbeth, Act V, Scene 1. - Shakespeare, William. Antony - and Cleopatra (1623), V. - ii. - Shakespeare, William. Hamlet In Stanley Wells and Gary Taylor eds. - The Complete Works, Oxford: Clarendon - Press, 1986, I.i. - Shakespeare, William. Hamlet, London: Valentine Simmes. - (1603), I.i. - Shakespeare, William. The Tempest - In Mr. William Shakespeares Comedies, Histories, & - Tragedies, London: Jaggard and Blount, - (1623). - Shakespeare, William. Twelfth Night, or - What you Will In Mr. William Shakespeares Comedies, Histories, - & Tragedies, London: Jaggard and - Blount, (1623). - Shakespeare, William, The - Sonnets (1609), 18. - Shakespeare, William, The - Sonnets (1609), 130. - 莎士比亞，《終成眷屬 》。 - 莎士比亞，《馬克白》。 - Sharing Ancient Wisdoms, 2013, - available: . - Shaw, George Bernard. Heartbreak - House: a fantasia in the Russian manner on English themes (1919). - Shaw, George Bernard. Pygmalion, 1913. - Shields, David. Dead - Languages, HarperCollins Canada/Perennial - Rack, rpt. 1990, p.10. - Sinclair, John ed. Collins - COBUILD English Language Dictionary. London and - Glasgow: Collins, (1987), - p. 337 s.v. croissant. - 京劇《四郎探母》，1947年梅蘭芳演出。 - Smith, Adam. An Inquiry into the - Nature and Causes of the Wealth of Nations, London. - (1776), index to vol. 1. - - Smith, Sydney. Autograph letter. In Pierpont Morgan library; - 11. - - Smith, William. A New Classical Dictionary of Greek and - Roman Biography, Mythology, and Geography, Partly Based Upon the Dictionary of Greek and - Roman Biography and Mythology, New York: Harper - & Brothers, Publishers, 1860, 1026. - - Southey, Robert. Autograph manuscript of The Life of Cowper. - In Pierpont Morgan MA 412 ( 15). - Soyinka, Akinwande Oluwole Wole. Madmen and Specialists, London: - Methuen (1971). - - Spenser, Edmund. The Faerie Queene: Disposed into twelue - bookes, Fashioning XII. Morall vertues. (1596). - - Sterne, Laurence. The Life and Opinions of Tristram - Shandy, Gentleman. (1760). - - Stow, John A survey of the cities of London and Westminster: - containing the original, antiquity, increase, modern estate and government of those - cities. Written at first in the year MDXCVIII. By John Stow, citizen and native of London. - ... Now lastly, corrected, improved, and very much enlarged: ... by John Strype, ... In - six books. ... (London c.1525 - London 1605). - Sudetic, Chuck Serbs Tighten Grip On Eastern - Bosnia. New York Times, - April 20, 1992. - - SUEtheTrex, Twitter biography. . Accessed March 25th, - 2020. - Sutherland, L.S. and L.G. - Mitchell eds. The Eighteenth century, The - History of the University of Oxford V - , p.178. - 蘇童，《妻妾成群》。 - 蘇軾，《定風波》。 - - Swift, Jonathan. Travels into Several Remote Nations of - the World, in Four Parts. By Lemuel Gulliver... (1735). - Swift, Jonathan. Law is a bottomless pit, or - the history of John Bull (1712). - - Swinburne, Algernon Charles. Poems and Ballads (First - Series). London: Chatto & Windus. - (1904). - Swinnerton, Frank Arthur. The - Georgian Literary Scene 1910-1935, 1938, London: - J. M. Dent, p. 195. - - - - - 台灣，《結婚入盟誓》，1997年5月。 - 台灣區三碼與三加二碼郵遞區號 - 《台灣叢書》，伊能嘉矩著，藏於國立台灣大學圖書館。(http://catalog.ndap.org.tw/?URN=2155366 (Aug 2008)). - 唐．白居易．琵琶行 - - Taylor, John - The Cold Tearme or, The Frozen age, Or, The Metamorphosis of the Riuer of - Thames. London, 1621. [STC (2nd ed.) 23910]. - - TEI Consortium - Call for Papers - TEI 2022 Newcastle, 2022. - - The Castle of the Fly, in Russian Fairy Tales, - translated by Norbert Guterman from the collections of Aleksandr Afanas'ev, illustrations by - Alexander Alexeieff, folkloristic commentary by Roman Jakobson (New York: Pantheon Books, - 1947, rpt. [n.d.]), p. 25. - The Daily Telegraph, 21 Dec - 1992. - The Guardian, - 26 Oct 1992, p. 2 - The Guardian, - 21 Dec 1992, p. 2. - The Holy Bible, conteyning the Old Testament and the new... - appointed to be read in Churches. (1611), Genesis - 1:1. - The Independent, - 26 Oct 1775, headline. - Thurber, James. The 13 - Clocks (1950). - Tolkien, J. R. R. - The Monsters and the Critics. London: - George Allen & Unwin (1983). - - Townsend, Sue. The growing pains of Adrian Mole - (1984), p.43. - - Trollope, Anthony. An Autobiography - (1883). - - Trollope, Anthony. North America - (1862). - Truffaut, François et - Gruault, Jean, Les deux Anglaises et le continent : - script, l'Avant-scène cinéma, n° 121, - nov. 1971. - Tufte, Edward R., Envisioning - Information, Cheshire: Graphics Press. - (1990). - - - Ukraine Relief Fund - UBS - . - - United States Code Title 17, Section 107, found at . - - United States District Court for the Middle District of Pennsylvania. - Kitzmiller v. Dover Area School District et al.: 2005. - 04cv2688, p. 33. Available from and transcribed at . - - - - Valéry, Paul, Monsieur - Teste, 1929. - - Vergil (Publius Vergilius Naso). Aeneid, - I.1. - Verne, Jules, Cinq - semaines en ballon, 1863. - Verne, Jules, La - Chasse au météore, 1908. - Verne, Jules, Vingt - mille lieues sous les mers, 1870. - - Vinge, Vernor - Across realtime - ch 10 (1986). - Viton de Saint-Allais, Nicolas - , Dictionnaire encyclopédique de la noblesse de France, - 1816. - - Vóluspá recto of folio 5 of the unique manuscript of the Elder Edda. Codex - Regius, ed. L. F. A. Wimmer and F. Jónsson (Copenhagen 1891). - - - - - Wanklyn, M.D.G. et al. Gloucester Port Books, 1575-1765. - Available from . - - Wanton, Joseph. Unpublished letter to Nicholas Brown and Co, - 1761 - Brown University Steering Committee on Slavery and Justice: Repository of - Historical Documents. (). - - Warriner, John E. - English Composition and Grammar (1988), p.280. - - Webster's Seventh Collegiate Dictionary. Springfield, Mass. - G. & C. Merriam Co. (1975). - 魏飴，《小說鑑賞入門》，台北：萬卷樓，1999。 - Weil, Simone, Lettres à Antonio Atarès, in Oeuvres - complètes1988-. - - Williams, Nigel. The Wimbledon Poisoner - (1990), p. 204. - Winock, Michel, - Jeanne et les siens : récit, 2003. - - Wölfflin, Heinrich, trans. Hottinger, Marie - Donald Mackie (1932). Principles of art history: the problem - of the development of style in later art.. Originally published as Kunstgeschichtliche Grundbegriffe (1915). - - Woolf, Virginia. Mrs Dalloway (1925), - p.64, p.65. - - Wordsworth, William. Scorn not the sonnet in - Poetical Works (1827). - - Wordsworth, William. The Prelude (1850). - - Wrenn C. L. ed. Beowulf: with the Finnesburg - fragment, London: Harrap - (1953). - - 吳承恩，《西遊記》。 - - - Wycherley, William. The Country Wife - (1675). - - - 夏宇，〈甜蜜的復仇〉，《備忘錄》。 - 蕭紅，《呼蘭河傳》。 - - - - 幼莘貢俚賀曉濤之新婚賀詞 - 余秋雨 - 元曲。馬致遠，《天淨沙：秋思》。 - - - - 張錯， 《西洋文學術與手冊》，台北：書林，2005。頁201。 - - 珍．奧斯丁，《傲慢與偏見》。 - - 中國青年守則 - 中國學位論文全文數據庫 - 周慧玲，《表演中國：女明星表演文化視覺政治1910-1945》，2004。 - 朱自清， 《憶》跋。 - - Zimman, Lal. Lal Zimman - , accessed February 1, - 2021. - - Zupko, Ronald Edward - British Weights & Measures: A History from Antiquity to the Seventeenth - Century. Madison: University of Wisconsin - Press, 141-151. - - - - No source, made up for these Guidelines. - Example is copied from the source of these - Guidelines. - Undetermined. - - - -
-
- Works Cited Elsewhere in the Text of these Guidelines - - - - - Knuth - Donald E. - - Literate Programming - CSLI Lecture Notes 27 - 0-937073-80-6 - - Stanford, California - Center for the Study of Language and Information - 1992 - - - - - - - Mazzolini - Renato - G. - - Colonialism and the Emergence of Racial Theories - - - - Reproduction: Antiquity to the Present Day - - Nick - Hopwood - - - Rebecca - Flemming - - - Lauren - Kassell - - - Cambridge - Cambridge University Press - 2018 - - 361-374 - - - - - - Rubin - Gayle - - The Traffic in Women: Notes on the <q>Political Economy</q> of Sex - - - - Toward an Anthropology of Women - - Rayna - R. - Reiter - - - New York - Monthly Review Press - 1975 - - 157–210, 165 - - - - - - - A. G. - Petty - - English literary hands from Chaucer to Dryden - - London - Edward Arnold - 1977 - - 22–25 - - - - - - Lou - Burnard - - Report of Workshop on Text Encoding Guidelines - - - Literary & Linguistic Computing - - 3 - 1988 - - - - - - - Lou - Burnard - - - C. - Michael - Sperberg-McQueen - - The Design of the TEI Encoding Scheme - 10.1007/BF01830314 - - - Computers and the Humanities - - 29 - 1 - 1995 - 17–39 - - - Reprinted in , pp. 17-40 - - - - - Lou - Burnard - - - Sebastian - Rahtz - - RelaxNG with Son of ODD - - - - Proceedings of Extreme Markup Languages 2004 - - 2004 - - - - - - - M. - B. - Parkes - - English Cursive Book Hands 1250–1500 - - Oxford - Clarendon Press - 1969 - - - - - - British Literary Manuscripts. Series 2: from 1800 to 1914 - - Klinkenborg - Verlyn - - - Cahoon - Herbert - - - New York - Pierpont Morgan Library - 1981 - - - - - - - Paul - Grosso - - - Eve - Maler - - - Jonathan - Marsh - - - Norman - Walsh - - XPointer Framework - - - W3C - 25 March 2003 - - - - - - - Paul - Grosso - - - Eve - Maler - - - Jonathan - Marsh - - - Norman - Walsh - - XPointer element() Scheme - - - W3C - 25 March 2003 - - - - - - XHTML™ 1.0 The Extensible HyperText Markup Language (Second - Edition) - - - W3C - 26 January 2000 - - - - - - - Dave - Ragget - - - Arnaud - Le Hors - - - Ian - Jacobs - - HTML 4.01 Specification - - - W3C - 24 December 1999 - - - - - - - David - Carlisle - - - Patrick - Ion - - - Robert - Miner - - - Nico - Poppelier - - Mathematical Markup Language (MathML) Version 2.0 (Second - edition) - - - W3C - 21 October 2003 - - - - - - - Paul V. - Biron - - - Ashok - Malhotra - - XML Schema Part 2: Datatypes Second Edition - - - W3C - 28 October 2004 - - - - - - - Anders - Berglund - - Extensible Stylesheet Language (XSL) Version 1.1 - - - W3C - 5 December 2006 - - - - - - - James - Clark - - XSL Transformations (XSLT) Version 1.0 - - - W3C - 16 November 1999 - - - - - - - Michael - Kay - - XSL Transformations (XSLT) Version 2.0 - - - W3C - 23 January 2007 - - - - - - - Michael - Kay - - XSL Transformations (XSLT) Version 3.0 - - - W3C - 8 June 2017 - - - - - - - Tim - Bray - - - Jean - Paoli - - - C. M. - Sperberg-McQueen - - - Eve - Maler - - - François - Yergau - - Extensible Markup Language (XML) Version 1.0 (Fourth edition) - - - W3C - 16 August 2006 - - - - - - - Bert - Bos - - - Tantek - Çelik - - - Ian - Hickson - - - Håkon Wium - Lie - - Cascading Style Sheets Level 2 Revision 1 - - - W3C - 7 June 2011 - - - - - - - Håkon Wium - Lie - - - Bert - Bos - - Cascading Style Sheets, Level 1 - - - W3C - 11 January 1999 - - - - - - - fantasai - - - Koji - Ishi - - CSS Writing Modes Level 3 (W3C Candidate Recommendation) - - - W3C - 15 December 2015 - - - - - - - Simon - Fraser - - - Dean - Jackson - - - Edward - O'Connor - - - Dirk - Schulze - - CSS Transforms Module Level 1 (W3C Working Draft) - - - W3C - 26 November 2013 - - - - - - - Frank - Manola - - - Eric - Miller - - - Brian - McBride - - RDF 1.1 Primer - - - W3C - 24 June 2014 - - - - - - - Jonathan - Marsh - - - Richard - Tobin - - XML Base (Second Edition) - - - W3C - 28 January 2009 - - - - - - - James - Clark - - - Steve - DeRose - - XML Path Language (XPath) Version 1.0 - - - W3C - 16 November 1999 - - - - - - - Anders - Berglund - - - Scot - Boag - - - Mary F. - Fernández - - - Michael - Kay - - - Jonathan - Robie - - - Jérôme - Siméon - - XML Path Language (XPath) 2.0 - - - W3C - 23 January 2007 - - - - - - - Jonathan - Robie - - - Don - Chamberlin - - - Michael - Dyck - - - Jon - Snelson - - XML Path Language (XPath) 3.0 - - - W3C - 8 April 2014 - - - - - - - Jonathan - Robie - - - Michael - Dyck - - - Josh - Spiegel - - XML Path Language (XPath) 3.1 - - - W3C - 21 March 2017 - - - - - - - Tim - Bray - - - Dave - Hollander - - - Andrew - Laymon - - - Richard - Tobin - - Namespaces in XML 1.0 (second edition) - - - W3C - 16 August 2006 - - - - - - - Eric - van der Vlist - - RELAX NG - - - O'Reilly - 2004 - - - - - - - Renear - A. - - - Mylonas - E. - - - Durand - D. - - Refining our notion of what text really is: the problem of overlapping - hierarchies - - - - Nancy - Ide - - - Susan - Hockey - - Research in Humanities Computing - - Oxford University Press - 1996 - - - - - - - Robert - Sanderson - - - Paolo - Ciccarese - - - Benjamin - Young - - Web Annotation Data Model - - - W3C - 23 February 2017 - - - - - - - Robert - Sanderson - - - Paolo - Ciccarese - - - Benjamin - Young - - Web Annotation Vocabulary - - - W3C - 23 February 2017 - - - - - - The Unicode Standard, Version 5.0 - - Unicode Consortium - - Addison-Wesley Professional - 2006 - - - - - - - Addison - Phillips - - - Mark - Davis - - Tags for Identifying Languages - RFC 4646 - - 2006 - IETF - - - - - - - Addison - Phillips - - - Mark - Davis - - Matching of Language Tags - RFC 4647 - - 2006 - IETF - - - - - - - Mark - Davis - - - Ken - Whistler - - - Asmus - Freytag - - Unicode Character Database - - - Unicode Consortium - 2006 - - - - - - - - Fernando - C. - N. - Pereira - - Grammars and logics of partial information - - Menlo Park, CA - SRI International - 1987 - - - - SRI International Technical Note - 420 - - - - - - Bob - Carpenter - - The logic of typed feature structures - - Cambridge - Cambridge University Press - 1992 - - - - Cambridge Tracts in Theoretical Computer Science - 32 - - - - - - Stuart - Shieber - - An Introduction to Unification-based Approaches to Grammar - CSLI Lecture Notes 4 - - Center for the Study of Language and Information - Palo Alto, CA - 1986 - - - - - - Anglo-American Cataloguing Rules - Second Edition, 2002 revision, 2005 update - - Chicago - American Library Association - Ottawa - Canadian Library Association - 2002–2005 - - - - - - - - John - Burrows - - Computation into Criticism: A Study of Jane Austen's Novel and an - Experiment in Method - - Oxford - Clarendon Press - 1987 - - - - - - - - Klaus - Mattheier - - - Ulrich - Ammon - - - Peter - Trudgill - - Sociolinguistics - Soziolinguistik - An international handbook of the science of - language and society - Ein internationales Handbuch zur Wissenschaft - von Sprache und Gesellschaft - - Berlin - New York - De Gruyter - 1988 - I - 271 and 274 - - - - - - - J. - A. - Edwards - - - M. - D. - Lampert - - Talking Language: Transcription and Coding of Spoken Discourse - - Hillsdale, N.J. - Lawrence Erlbaum Associates - 1993 - - - - - - - Asmus - Freytag - - The Unicode Character Property Model - Unicode Technical Report #23 - - - 2006 - - - - - - - Mark - Davis - - - Aharon - Lanin - - - Andrew - Glass - - Unicode Bidirectional Algorithm - Unicode Standard Annex #9 - - - 2017-05-04 - - r. 37 - - - - - - - Stig - Johansson - - Encoding a Corpus in Machine-Readable Form - - - - - Sue - Atkins - - - Antonio - Zampolli - - Computational Approaches to the Lexicon: An Overview - - Oxford - Oxford University Press - 1994 - - - - - - - - Stig - Johansson - - - Lou - Burnard - - - Jane - Edwards - - - And - Rosta - - Working Paper on Spoken Texts - TEI document TEI AI2 W1 - - 1991 - - - - - - - - Brian - MacWhinney - - CHAT Manual - - Pittsburgh - Dept of Psychology, Carnegie-Mellon University - 1988 - 87ff - - - - - - - Bengt - Loman - - - Nils - Jørgensen - - Manual for analys och beskrivning av makrosyntagmer - - Lund - Studentlitteratur - 1971 - - - - - - - Robert - A. - Amsler - - - Frank - W. - Tompa - - An SGML-Based Standard for English Monolingual Dictionaries - - - Information in Text - Fourth Annual Conference of the U[niversity of] W[aterloo] - Centre for the New Oxford English Dictionary - Fourth Annual Conference of the U[niversity of] W[aterloo] Centre for the New - Oxford English Dictionary, October 26-28, 1988, Waterloo, Canada - - Waterloo, Canada - October 1988 - 61-79 - - - - - - - - N. - Calzolari - - - C. - Peters - - - A. - Roventini - - Computational Model of the Dictionary Entry: Preliminary - Report - Acquilex: Esprit Basic Research Action No. 3030, Six-Month - Deliverable - - Pisa - April 1990 - - - - - - - - John - Fought - - - Carol - Van Ess-Dykema - - Toward an SGML Document Type Definition for Bilingual - Dictionaries - TEI working paper TEI AIW20 - - available from the TEI. - - - - - - - - Nancy - Ide - - - Jean - Veronis - - Encoding Print Dictionaries - - - Computers and the Humanities - - 29 - 1995 - 167-195 - - - - - - - Nancy - Ide - - - Jacques - Le Maitre - - - Jean - Veronis - - Outline of a Model for Lexical Databases - - - Information Processing and Management - - 29 - 2 - 1993 - 159-186 - - - - - - - Nancy - Ide - - - Jean - Veronis - - - Susan - Warwick-Amstrong - - - Nicoletta - Calzolari - - Principles for Encoding machine readable dictionaries - - - Proceedings of the Fifth EURALEX International Congress, - EURALEX'92 - Fifth EURALEX International Congress, EURALEX'92, University of Tampere, - Finland - - 1992 - - - - - - - - The - DANLEX Group - - Descriptive tools for electronic processing of dictionary data - - - Lexicographica, Series Maior - - Tübingen - Niemeyer - 1987 - - - - - - - - Agnès - Tutin - - - Jean - Veronis - - Electronic dictionary encoding: customizing the TEI Guidelines - - - Proceedings of the Eighth Euralex International Congress - Eighth Euralex International Congress - - 1998 - - - - - - - N. - Ide - - - A. - Kilgarriff - - - L. - Romary - - A Formal Model of Dictionary Structure and Content - - - Proceedings of Euralex 2000 - Euralex 2000 - - Stuttgart - 2000 - 113-126 - - - - - - - William - A. - Gale - - - Kenneth - W. - Church - - Program for aligning sentences in bilingual corpora - - - Computational Linguistics - - 19 - 1993 - 75-102 - - - - - - - G. - N. - Leech - - - R. - G. - Garside - - Running a Grammar Factory - - - - S. - Johansson - - - A.-B. - Stenstrøm - - English Computer Corpora: Selected Papers and Research Guide - - Berlin - de Gruyter - New York - Mouton - 1991 - pp. 15-32. - - - - - - - - I. - Marshall - - Choice of Grammatical Word Class without Global Syntactic Analysis: - Tagging Words in the LOB Corpus - - - Computers and the Humanities - - 17 - 1983 - 139-50 - - - - - - - - R. - G. - Garside - - - G. - N. - Leech - - - G. - R. - Sampson - - The Computational Analysis of English: a Corpus-Based Approach - - Oxford - Oxford University Press - 1991 - - - - - - - - Gary - Chartrand - - - Linda - Lesniak - - Graphs and Digraphs - - Menlo Park, CA - Wadsworth - 1986 - - - - - - - - R. - Jackendoff - - X-Bar Syntax: A study of phrase structure - - - Linguistic Inquiry Monograph - - 2 - 1977 - - - - - - - - M. - Kytö - - - M. - Rissanen - - The Helsinki Corpus of English Texts - - - - M. - Kytö - - - O. - Ihalainen - - - M. - Rissanen - - Corpus Linguistics: hard and soft - - Amsterdam - Rodopi - 1988 - - - - - - - - Steven - DeRose - - Markup overlap: a review and a horse - - - - Proceedings of Extreme Markup Languages 2004 - - 2004 - - - - - - - Andreas - Witt - - Multiple Informationsstrukturierung mit - Auszeichnungssprachen. XML-basierte Methoden und deren Nutzen für die - Sprachtechnologie - - 2002 - - - Ph D thesis, Bielefeld University - See also - - - - - - - Mirco - Hilbert - - - Oliver - Schonefeld - - - Andreas - Witt - - Making CONCUR work - - - - Proceedings of Extreme Markup Languages 2005 - - 2005 - - - - - - - - Alex - Dekhtyar - - - Ionut - E. - Iacob - - A framework for management of concurrent XML markup - - - - - 2005 - - - - - - - - H. - V. - Jagadish - - - Laks - V. - S. - Lakshmanan - - - Monica - Scannapieco - - - Divesh - Srivastava - - - Nuwee - Wiwatwattana - - Colorful XML: one hierarchy isn't enough - - - - - - - 2004 - - - - - - - - Noureddine - Chatti - - - Suha - Kaouk - - - Sylvie - Calabretto - - - Jean - Marie - Pinon - - MultiX: an XML based formalism to encode multistructured - documents - - - - - - Proceedings of Extreme Markup Languages 2007 - - 2007 - - - - - - - - Patrick - Durusau - - - Matthew - Brook - O'Donnell - - Coming down from the trees: next step in the evolution of markup? - - - Proceedings of Extreme Markup Languages 2002 - - 2002 - - - - - - - - Jeni - Tennison - - - Wendell - Piez - - The layered markup and annotation language - - - Proceedings of Extreme Markup Languages Conference - - 2002 - - - - - - - - Claus - Huitfeldt - - - C. - Michael - Sperberg-McQueen - - TexMECS: An experimental markup meta-language for complex - documents - - - 2001 - - - - - - - D. Terence - Langendoen - - - Gary F. - Simons - - A rationale for the TEI recommendations for feature-structure - markup, - - - Computers and the Humanities - - 29 - 1995 - 167-195 - - - - - - British Standards Institute - BS 5605:1990: Recommendations for Citing and Referencing Published - Material - - 1990 - - - - - - British Standards Institute - BS 6371:1983: Recommendations for Citation of Unpublished - Documents - - 1983 - - - - - - Deutsches Institut für Normung - DIN 1505-2: Titelangaben von Dokumenten; Zitierregeln - - 1984 - - - - - - Die Deutsche Bibliothek - Regeln für die alphabetische Katalogisierung in wissenschaftlichen - Bibliotheken RAK-WB - - 2006 - - - - - - International Organization for Standardization - ISO 690:1987: Information and documentation – Bibliographic references – Content, - form and structure - - 1987 - - - - - - International Organization for Standardization - ISO 8601:2004: Data elements and interchange formats — Information interchange — - Representation of dates and times - - 2004 - - - - - - International Organization for Standardization - ISO 12620:2009: Terminology and other language and content resources – - Specification of data categories and management of a Data Category Registry for language - resources - - - 2009 - - - - - - International Organization for Standardization - ISO 19136:2007: Geographic information — Geography Markup Language (GML) - - 2006 - - - - - - International Organization for Standardization - ISO/IEC 19757-3:2006: Information technology — Document Schema Definition Languages - (DSDL) – Part 3: Rule-based validation – Schematron - - 2006 - - - - - - Istituto Centrale per il Catalogo Unico - Regole italiane di catalogazione per autori - - 1979 - - - - - - National Information Standards Organization - ANSI/NISO Z39.29 – 2005 (R2010) Bibliographic References - - 2010 - - - - - - ISBD: International Standard Bibliographic Description - - Berlin, München - De Gruyter Saur - 2011 - - - - IFLA Series on Bibliographic Control - 44 - - - - - Федеральное агентство по техническому регулированию и метрологии - (РОССТАНДАРТ) - ГОСТ Р 7.0.5-2008: Система стандартов по информации, библиотечному и - издательскому делу. Библиографическая ссылка. Общие требования и правила - составления - - 2008 - - - - - - Федеральное агентство по техническому регулированию и метрологии - (РОССТАНДАРТ) - ГОСТ 7.1—2003. Система стандартов по информации, библиотечному и - издательскому делу. Библиографическая запись. Библоиграфическое описание. Общие - требования и правила составления - - 2003 - - - - - - DCMI Usage Board - Dublin Core™ Metadata Element Set, Version 1.1: Reference Description - - - 2012-06-14 - - - - -
-
- Reading List -

The following lists of readings in markup theory and the TEI derive from work - originally prepared by Susan Schreibman and Kevin Hawkins for the TEI Education Special - Interest Group, recoded in TEI P5 by Sabine Krott and Eva Radermacher. They should be regarded - only as a snapshot of work in progress, to which further contributions and corrections are - welcomed (see further ).

-
- Theory of Markup and XML - - - - - C. - Michael - Sperberg-McQueen - - - Claus - Huitfeld - - Concurrent Document Hierarchies in MECS and SGML - - - Literary and Linguistic Computing - - 14 - 1 - 1999 - 29-42 - - - - - - - C. - Michael - Sperberg-McQueen - - Rabbit/duck grammars: a validation method for overlapping - structures - - - - Proceedings of Extreme Markup Languages 2006 - - 2006 - - - - - - - David - T. - Barnard - - - Lou - Burnard - - - Jean-Pierre - Gaspart - - - Lynne - A. - Price - - - C. - Michael - Sperberg-McQueen - - - Giovanni - Battista - Varile - - Hierarchical Encoding of Text: Technical Problems and SGML - Solutions - 10.1007/BF01830617 - - - - Computers and the Humanities - - 29 - 3 - 1995 - 211–231 - - - - - - - David - T. - Barnard - - - Lou - Burnard - - - C. - Michael - Sperberg-McQueen - - Lessons learned from using SGML in the Text Encoding Initiative - 10.1016/0920-5489(95)00035-6 - - - Computer Standards & Interfaces - - 18 - 1 - 1996 - 3–10 - - - - - - - Lou - Burnard - - What is SGML and how does it help? - - - - - Daniel - Greenstein - - Modelling Historical Data: Towards a Standard for Encoding and - Exchanging Machine-readable Texts - - St Katherinen - Max-Planck-Institut für Geschichte In Kommission bei Scripta Mercaturae - Verlag - 1991 - 81–91 - - - - Halbgraue Reihe zur Historischen Fachinformatik - - Herausg. von - - Manfred - Thaller - - - serie A - 11 - - - Revised version published as - - - - - Lou - Burnard - - SGML on the Web: Too Little Too Soon or Too Much Too Late? - - - - Computers & Texts - - 15 - 1995 - 12–15 - - - - - - - - Lou - Burnard - - What is SGML and How Does It Help? - 10.1007/BF01830315 - - - - Computers and the Humanities - - 29 - 1 - 1995 - 41–50 - - - Reprinted in , pp. 41-50 - - - - - Nancy - Ide - - - Jean - Veronis - - The Text Encoding Initiative: Background and Contexts - - Dordrecht - Boston - Kluwer Academic Publisher - 1995 - - - - - - - Lou - Burnard - - Is Humanities Computing an Academic Discipline? or, Why Humanities - Computing Matters - - - - 1999 - - - - Presented at an interdisciplinary seminar at the Institute for Advanced Technology - in the Humanities, University of Virginia, November 1999. - - - - - Lou - Burnard - - Using SGML for Linguistic Analysis: The Case of the BNC - - - - Markup Languages Theory and Practice - - 2 - 1999 - Cambridge, Massachusettes - MIT Press - 31–51 - - - Also published in , pp. 53–72 - - - - - Stephan - Moser - - - Peter - Stahl - - - Werner - Wegstein - - - Norbert - Richard - Wolf - - Maschinelle Verarbeitung Altdeutscher Texte V (Beiträge zum Fünften - Internationalen Symposion, Würzburg, 4–6 März 1997) - - Tübingen - Niemeyer - 2001 - - - - - - - Lou - Burnard - - - Elizabeth - Lalou - - - Peter - Robinson - - Vers un Standard Européen de Description des Manuscrits: Le Projet - Master - - - Documents Numeriques - Les Documents Anciens - - 3 - 1–2 - 1999 - Paris - Hermes Science Publications - 151-169 - - - - - - - Lou - Burnard - - XML: The Dream and the Reality - - - 1999 - - - Closing plenary address at the XML Europe Conference, Granada, May 1999 - - - - - Lou - Burnard - - - Claudia - Claridge - - - Josef - Schmied - - - Rainer - Siemund - - Encoding the Lampeter Corpus - - - - DRH98: Selected Papers from Digital Resources for the - Humanities - - London - Office for Humanities Communication - 2000 - - - - - - - - Lou - Burnard - - From Two Cultures to Digital Culture: The Rise of the Digital - Demotic - - - 2000 - - - Presented at CLIP, Alicante - - Published in Italian as - - - - - - Lou - Burnard - - Dalle «Due Culture» Alla Cultura Digitale: La Nascita del Demotico - Digitale - - Translated by - - Federico - Pellizi - - - - - Il Verri - Nella Rete - - 16 - 2001 - Milano - Monogramma - 9–22 - - - - - - - Lou - Burnard - - On the Hermeneutic Implications of Text Encoding - - - - - Domenico - Fiormonte - - - Jonathan - Usher - - New Media and the Humanities: Research and Applications - - Oxford - Humanities Computing Unit - 2001 - 31–38 - - - - - - - - Lou - Burnard - - Encoding Standards for the Electronic Edition - - - - - Matija - Ogrin - - Znanstvene Izdaje in Elektronski - Medij - Scholarly Editions and the Digital - Medium - - Ljubljana - Studia Litteraria ZRC ZAZU - 2005 - 12–67 - - - - - - - - Lou - Burnard - - Metadata for corpus work - - - - - Martin - Wynne - - Developing Linguistic Corpora: A Guide to Good Practice - - Oxford - Oxbow Books - 2005 - 30–46 - - - - - - - - Lou - Burnard - - - Katherine - O'Brien - O'Keefe - - - John - Unsworth - - Electronic Textual Editing - - - New York - Modern Languages Association - 2006 - - - - - - - Dino - Buzzetti - - Digital Representation and the Text Model - - - - New Literary History - - 33 - 1 - 2002 - 61–88 - - - - - - - - Paul - Caton - - Markup's Current Imbalance - - - Markup Languages: Theory and Practice - - 3 - 1 - 2001 - 1–13 - - - This paper was proceeded by reports at the Joint Annual Conference of the - Association for Computers and the Humanities and the Association for Literary and - Linguistic Computing in 1999 (Charlottesville, Virginia) and Extreme Markup Languages - 2000 (Montreal, Canada) - - - - - Ruey-Shun - Chen - - - Shien-Chiang - Yu - - Developing an XML Framework for Metadata System - - - - Proceedings of the 1st International Symposium on Information and - Communication Technologies - - Dublin - 2003 - 267–272 - - - - ACM International Conference Proceeding Series - 49 - - - This paper was presented in a session entitled "Electronic Document - Technology." - - - - - James - H. - Coombs - - Information Management System for Scholars - Technical Memorandum TM 69–2 - - Providence - Brown Computer Center - 1986 - - - - - - - James - H. - Coombs - - - Allen - Renear - - - Steven - J. - DeRose - - Markup Systems and The Future of Scholarly Text Processing - 10.1145/32206.32209 - - - - - Communications of the ACM - - 30 - 11 - 1987 - 933–947 - - - Reprinted with new commentary in , pp 85–118 - - - - - George - P. - Landow - - - Paul - Delany - - The Digital Word: Text-based Computing in the Humanities - - Cambridge, MA - MIT Press - 1993 - - - - - - - Robin - Cover - - Markup Languages and (Non-) Hierarchies - - - 2005 - - - Technology report from the Cover Pages - - - - - - Steven - J. - DeRose - - Structured Information: Navigation, Access, and Control - - - 1995 - - - Paper presented at the Berkeley Finding Aid Conference, April 4–6, 1995 - - - - - - Steven - J. - DeRose - - - David - G. - Durand - - - Elli - Mylonas - - - Allen - H. - Renear - - What is Text, Really? - - - Journal of Computing in Higher Education - - 1 - 2 - 1990 - 3–26 - - - Republished () as a "classic reprint" with invited - commentary and authors' replies in the ACM/SIGDOC - - - - - Steven - J. - DeRose - - - David - G. - Durand - - - Elli - Mylonas - - - Allen - H. - Renear - - What is Text, Really? - 10.1145/264842.264843 - - - Journal of Computer Documentation - - 21 - 3 - 1997 - 1–24 - - - - - - - Charles - F. - Goldfarb - - A Generalized Approach to Document Markup - - - - Proceedings of the ACM SIGPLAN SIGOA Symposium on Text - Manipulation - - New York - ACM - 1981 - 68–73 - - - Adapted as "Annex A. Introduction to Generalized Markup" in ISO 8879 - - - - - - Tony - Graham - - Unicode: What Is It and How Do I Use It? - - - Markup Languages: Theory & Practice - - 1 - 4 - 1999 - 75 - - - - - - - Susan - Hockey - - Creating and Using Electronic Editions - - - - Richard - J. - Finneran - - The Literary Text in the Digital Age - - Ann Arbor, MI - University of Michigan Press - 1996 - 1–22 - - - - - - - Susan - Hockey - - - Allen - Renear - - - Jerome - J. - McGann - - What is Text? A Debate on the Philosophical and Epistemological Nature - of Text in the Light of Humanities Computing Research - - - 1999 - - - Panel presented at ACH/ALLC 1999 - - - - - - Susan - Hockey - - Electronic Texts in the Humanities - - New York, NY - Oxford University Press - 2000 - - - - - - - Claus - Huitfeldt - - Multi-dimensional Texts in a One-dimensional Medium - 10.1007/BF01830270 - - - Computers and the Humanities - - 28 - 4/5 - 1994 - 235–241 - - - - - - - Claus - Huitfeldt - - Toward a Machine-Readable Version of Wittgenstein's Nachlaß: Some - Editorial Problems - - - - Hans - Gerhard - Senger - - Philosophische Editionen. Erwartungen an sie — Wirkungen durch - sie - - Tübingen - Max Niemeyer Verlag - 1994 - 37–43 - - - - Beihefte zu editio - 6 - - - - - - Leslie - Lamport - - Document Production: Visual or Logical? - - - - Notices of the American Mathematical Society - - 34 - 1987 - 621–624 - - - - Republished as - - - - - Leslie - Lamport - - Document Production: Visual or Logical? - - - - TUGboat - - 9 - 1 - 1988 - 8-10 - - - - - - - - - - John - Lavagnino - - Completeness and Adequacy in Text Encoding - - - - Richard - J. - Finneran - - The Literary Text in the Digital Age - - Ann Arbor, MI - University of Michigan Press - 1996 - 63–76 - - - - - - - Charles - Lightfoot - - Generic Textual Element Identification—A Primer - - Arlington - Graphic Communications Computer Association - 1979 - - - - - - - Joshua - Lubell - - Structured Markup on the Web: A Tale of Two Sites - - - - Markup Languages: Theory & Practice - - 1 - 3 - 1999 - 7–22 - - - - - - - - Tony - McEnery - - - Lou - Burnard - - - Andrew - Wilson - - - Paul - Baker - - Validation of Linguistic Corpora - - - 1998 - - - - Report commissioned by ELRA - - - - - Jerome - McGann - - The Rationale of Hypertext - - - - Kathryn - Sutherland - - Electronic Text: Investigations in Method and Theory - - New York, NY - Clarendon Press Oxford - 1997 - 19–46 - - - - - - - Jerome - McGann - - Radiant Textuality: Literature After the World Wide Web - - New York, NY - Palgrave Macmillian - 2001 - - - - - - - Jerome - McGann - - Marking Texts of Many Dimensions - - - - - Susan - Schreibman - - - Ray - Siemens - - - John - Unsworth - - A Companion to Digital Humanities - - Oxford - Blackwell - 2004 - 198–217 - - - - - - - - Alan - Morrison - - - Michael - Popham - - - Karen - Wikander - - Creating and Documenting Electronic Texts: A Guide to Good - Practice - - - (no date) - - - - - - - - Alois - Pichler - - Advantages of a Machine-Readable Version of Wittgenstein's - Nachlaß - - - - - Kjell - S. - Johannessen - - - Tore - Nordenstam - - Culture and Value: Philosophy and the Cultural Sciences. Beiträge des - 18. Internationalen Wittgenstein Symposiums 13–20. August 1995 Kirchberg am - Wechsel - - Kirchberg am Wechsel - Die Österreichische Ludwig Wittgenstein Gesellschaft - 1995 - 770–776 - - - - - - - - - Wendell - Piez - - Beyond the 'Descriptive vs. Procedural' Distinction - - - - - B. - Tommie - Usdin - - - Steven - R. - Newcomb - - Proceedings of Extreme Markup Languages 2001: Montreal, Canada - - 2001 - - - - - - - - - Michael - Popham - - What Is Markup and Why Does It Matter - - - - Michael - Popham - - - Lorna - Hughes - - Computers and Teaching in the Humanities: Selected Papers from the - CATH94 Conference held in Glasgow University September 9th-12th 1994 - - Oxford - CTI Centre for Textual Studies - 1996 - - - - - - - Liam - Quin - - Suggestive Markup: Explicit Relationships in Descriptive and - Prescriptive DTDs - - - - - B. - Tommie - Usdin - - - Deborah - A. - Lapeyre - - SGML'96 Conference Proceedings - - Alexandria, VA - Graphic Communications Association - 1996 - 405–418 - - - - - - - - Darrell - Raymond - - - Frank - Tompa - - - Derick - Wood - - From Data Representation to Data Model: Meta-Semantic Issues in the - Evolution of SGML - - - - Computer Standards & Interfaces - - 18 - 1 - 1996 - 25–36 - - - - - - - Allen - Renear - - - David - Durand - - - Elli - Mylonas - - Refining our Notion of What Text Really Is: The Problem of Overlapping - Hierarchies - - - - - Susan - Hockey - - - Nancy - Ide - - Research in Humanities Computing 4: Selected Papers from the 1992 - ALLC/ACH Conference - - Oxford - Oxford University Press - 1996 - 263–280 - - - - - - - - Allen - Renear - - Out of Praxis: Three (Meta)Theories of Textuality - - - - Kathryn - Sutherland - - Electronic Text: Investigations in Method and Theory - - New York, NY - Clarendon Press Oxford - 1997 - 107–126 - - - - - - - Allen - Renear - - The Descriptive/Procedural Distinction is Flawed - - - Markup Languages: Theory and Practice - - 2 - 4 - 2000 - 411–420 - - - - - - - - Allen - H. - Renear - - - David - Dubin - - - C. - Michael - Sperberg-McQueen - - Towards a Semantics for XML Markup - 10.1145/585058.585081 - - - - Richard - Furuta - - - Jonathan - I. - Maletic - - - Ethan - V. - Munson - - Proceedings of the 2002 ACM Symposium on Document Engineering - - McLean, VA - Association for Computing Machinery - 2002 - 119–126 - - - - - - - Allen - H. - Renear - - - Christopher - Phillippe - - - Pat - Lawton - - - David - Dubin - - An XML Document Corresponds to Which FRBR Group 1 Entity? - - - - - - B. - Tommie - Usdin - - - Steven - R. - Newcomb - - Proceedings of Extreme Markup Languages 2003: Montreal, Canada - - 2003 - - - - - - - - - Allen - H. - Renear - - - David - Dubin - - - C. - Michael - Sperberg-McQueen - - - Claus - Huitfeldt - - XML Semantics and Digital Libraries - - - - Proceedings of the 3rd ACM/IEEE–CS Joint Conference on Digital - Libraries - - Los Alamitos, CA - IEEE Computer Society - 2003 - 303–305 - - - - - - - - Allen - H. - Renear - - Text Encoding - - - - - Susan - Schreibman - - - Ray - Siemans - - - John - Unsworth - - A Companion to Digital Humanities - - Oxford - Blackwell - 2004 - 218–239 - - - - - - - - Susanne - Salmon-Alt - - Data Structures for Etymology: Towards an Etymological Lexical - Network - - - - BULAG: revue internationale annuelle - Numéro Etymologie - - 31 - 2006 - Besançon - Presses Universitaires de Franche-Comté - - - - - - - - Susan - Schreibman - - Computer-mediated Texts and Textuality: Theory and Practice - 10.1023/A:1016178200469 - - - Computers and the Humanities - - 36 - 3 - 2002 - 283–293 - - - - - - - Susan - Schreibman - - The Text Ported - 10.1093/llc/17.1.77 - - - Literary and Linguistic Computing - - 17 - 1 - 2002 - 77–87 - - - - - - - SGML Users' Group - - A Brief History of the Development of SGML - - - 1990 - - - - - - - - Frank - M. - Shipman - III - - - Catherine - C. - Marshall - - Formality Considered Harmful: Experiences, Emerging Themes, and - Directions on the Use of Formal Representations in Interactive Systems - 10.1023/A:1008716330212 - - - - Computer-Supported Cooperative Work - - 8 - 4 - 1999 - 333–352 - - - - - - - C. - Michael - Sperberg-McQueen - - - Claus - Huitfeldt - - Concurrent document hierarchies in MECS and SGML - 10.1093/llc/14.1.29 - - - Literary and Linguistic Computing - - 14 - 1 - 1999 - 29–42 - - - - - - - C. - Michael - Sperberg-McQueen - - - Claus - Huitfeldt - - - Allen - H. - Renear - - Meaning and Interpretation in Markup - - - Markup Languages: Theory and Practice - - 2 - 3 - 2000 - 215–234 - - - - - - - C. - Michael - Sperberg-McQueen - - - David - Dubin - - - Claus - Huitfeldt - - - Allen - Renear - - Drawing Inferences on the Basis of Markup - - - - - - B. - Tommie - Usdin - - - Steven - R. - Newcomb - - Proceedings of Extreme Markup Languages 2002: Montreal, Canada - - 2002 - - - - - - - - - Suzana - Sukovic - - Beyond the Scriptorium: The Role of the Library in Text - Encoding - - - - D-Lib - - 8 - 1 - 2002 - - - - - - - - University of Nebraska — Lincoln Libraries - - A Basic Guide to Text Encoding - - - - - - 2003 - - - - - - - - John - Unsworth - - Knowledge Representation in Humanities Computing - - - 2001 - - - Lecture I in the eHumanities NEH Lecture Series on Technology & the Humanities, - Washington, DC, April 3, 2001 - - - - - - John - Unsworth - - Scholarly Primitives: What Methods Do Humanities Researchers Have in - Common, How Might Our Tools Reflect This? - - - 2000 - - - Part of a Symposium on "Humanities Computing: Formal Methods, Experimental - Practice" sponsored by King's College, London - - - - - - Fabio - Vitali - - - Luca - Bompani - - - Paolo - Ciancarini - - Hypertext Functionalities with XML - - - Markup Languages: Theory & Practice - - 2 - 4 - 2000 - 389 - - - - - - - Dennis - G. - Watson - - Brief History of Document Markup - - - 1992 - - - Circular 1086. Florida Cooperative Extension Service, Institute of Food and - Agricultural Sciences, University of Florida - - - - - - Adriaan - van der - Weel - - The Concept of Markup - - - - Digital Text and the Gutenberg Heritage - - (no date) - 3 - - - in preparation; draft only - - - - - - Christopher - Welty - - - Nancy - Ide - - Using the Right Tools: Enhancing Retrieval from Marked-up - Documents - 10.1023/A:1001800717376 - - - - Computers and the Humanities - - 33 - 1–2 - 1999 - 59–84 - - - - -
-
- TEI - - - - - Syd - Bauman - - Keying NAMEs: the WWP Approach - - - - Brown University Women Writers Project Newsletter - - 2 - 3 - 1996 - 3–6 - 10–11 - - - - - - - Syd - Bauman - - - Julia - Flanders - - Odd Customizations - - - - Proceedings of Extreme Markup Languages 2004 - - 2004 - - - - - - - Syd - Bauman - - Tables of Contents TEI-style - - - - Lou - Burnard - - TEXT Technology: The Journal of Computer Text - Processing - Electronic Texts and the Text Encoding Initiative. A Special - Issue of TEXT Technology - - 5 - 3 - 1995 - Madison, SD - College of Liberal Arts, Dakota State University - 235–247 - - - - - - - Syd - Bauman - - - Terry - Catapano - - TEI and the Encoding of the Physical Structure of Books - 10.1023/A:1001769103586 - - - Computers and the Humanities - - 33 - 1–2 - 1999 - 113–127 - - - - - - - Syd - Bauman - - TEI HORSEing Around - - - - Proceedings of the Extreme Markup Languages 2005 - - 2005 - - - - - - - Malcolm - B. - Brown - - What is the TEI? - - - Information Technology and Libraries - - 13 - 1 - 1994 - 8 - - - - - - - Lou - Burnard - - The Text Encoding Initiative: A Progress Report - - - - Gerhard - Leitner - - New Directions in Corpus Linguistics - - Berlin - Mouton de Gruyter - 1992 - - - - - - - Lou - Burnard - - Rolling your own with the TEI - - - Information Services and Use - - 13 - 2 - 1993 - Amsterdam - IOS Press - 141–154 - - - - - - - Lou - Burnard - - The TEI: Towards an Extensible Standard for the Encoding of - Texts - - - - Seamus - Ross - - - Edward - Higgs - - Electronic Information Resources and Historians - - London - British Academy - 1994 - - - - - - - Lou - Burnard - - The Text Encoding Initiative: An Overview - - - - Geoffrey - Leech - - - Greg - Myers - - - Jenny - Thomas - - Spoken English on Computer: Transcription, Mark-up and - Application - - London - Longman - 1995 - - - - - - - Lou - Burnard - - The Text Encoding Initiative's Recommendations for the Encoding of - Language Corpora: Theory and Practice - - - 1997 - - - Prepared for a seminar on Etiquetación y extracción de información de grandes corpus - textuales within the Curso Industrias de la Lengua (14–18 de Julio de 1997). Sponsored - by the Fundacion Duques de Soria. - - - - - Lou - Burnard - - - Michael - Popham - - Putting Our Headers Together: A Report on the TEI Header Meeting 12 - September 1997 - 10.1023/A:1001710828622 - - - Computers and the Humanities - - 33 - 1-2 - 1999 - Dordrecht, Boston - Kluwer Academic Publishers - 39–47 - - - - - - An Agreement to Establish a Consortium for the Maintenance of the Text Encoding - Initiative - - - March 1999 - - - - - - - Lou - Burnard - - Text Encoding for Interchange: A New Consortium - - - 2000 - - - - - - - Fabio - Ciotti - - Il Manuale TEI Lite: Introduzione Alla Codifica Elettronica Dei Testi - Letterari - - Milano - Sylvestre Bonnard - 2005 - - - - - - - Sheau-Hwang - Chang - - The Implications of TEI - - - OCLC Systems and Services - - 17 - 3 - 2001 - 101–103 - - - - - - - Mavis - Cournane - - The Application of SGML/TEI to the Processing of Complex, Multi-lingual - Text - PhD Dissertation - - Cork, Ireland - University College Cork - 1997 - - - - - - - Digital Library Federation - - TEI and XML in Digital Libraries: Meeting June 30 and July 1, 1998, - Library of Congress, Summary/Proceedings - - - - 1998 - - - - - - - - Digital Library Federation - - TEI Text Encoding in Libraries: Guidelines for Best - Encoding Practices - Version 3.0 (October 2011) - - - 2011 - - - - - - - Timothy - J. - Finney - - Manuscript Markup - - - - Larry - W. - Hurtado - - The Freer Biblical Manuscripts: Fresh Studies of an American Treasure - Trove - - Atlanta, GA - Society of Biblical Literature - 2006 - 263-288 - - - - Text-critical studies - 6 - - - - - - Matthew - Gibson - - - Christine - Ruotolo - - Beyond the Web: TEI, the Digital Library, and the Ebook - Revolution - 10.1023/A:1021895322291 - - - Computers and the Humanities - - 37 - 1 - 2003 - 57–63 - - - - - - - Sylvain - Loiseau - - Les standards : autour d'XML et de la TEI - - - 2002 - - - - - - - - Lynn - Marko - - - Christina - Kelleher Powell - - Descriptive Metadata Strategy for TEI Headers: A University of Michigan - Library Case Study - 10.1108/10650750110402585 - - - OCLC Systems & Services - - 17 - 3 - 2001 - 117-20 - - - - - - - David - Mertz - - XML Matters: TEI — the Text Encoding Initiative - An XML Dialect for Archival and Complex Documents - - - 2003 - - - - - - - Alan - Morrison - - Delivering Electronic Texts Over the Web: The Current and Planned - Practices of the Oxford Text Archive - 10.1023/A:1001726011322 - - - Computers and the Humanities - - 33 - 1-2 - 1999 - 193-198 - - - - - - - Elli - Mylonas - - - Allen - Renear - - The Text Encoding Initiative at 10: Not Just an Interchange Format - Anymore — But a New Research Community - 10.1023/A:1001832310939 - - - Computers and the Humanities - - 33 - 1-2 - 1999 - 1-9 - - - - - - - Tobin - Nellhaus - - XML, TEI, Digital Libraries in the Humanities - - - - Portal: Libraries and the Academy - - 1 - 3 - 2001 - 267-277 - - - - - - - - Sebastian - Rahtz - - Building TEI DTDs and Schemas on demand - - - - 2003 - - - Paper presented at XML Europe 2003, London, March 2003 - - - - - Sebastian - Rahtz - - - Norman - Walsh - - - Lou - Burnard - - A unified model for text markup: TEI, Docbook, and beyond - - - 2004 - - - Paper presented at XML Europe 2004, Amsterdam, April 2004 - - - - - Allen - Renear - - Theory and Metatheory in the Development of Text Encoding - - - - - Michael - A. - R. - Biggs - - - Claus - Huitfeldt - - Philosophy and Electronic Publishing - - 1995 - - - Interactive seminar for the Monist - - - - - - Peter - Robinson - - Making a Digital Edition with TEI and Anastasia - - - (no date) - - - - - - - - David - Seaman - - The Electronic Text Center Introduction to TEI and Guide to Document - Preparation - - - 1995 - - - - - - - Gary - F. - Simons - - Using Architectural Forms to Map TEI Data into an Object-Oriented - Database - 10.1023/A:1001765030032 - - - Computers and the Humanities - - 33 - 1-2 - 1999 - 85-101 - - - - - - - David - Smith - - Textual Variation and Version Control in the TEI - 10.1023/A:1001795210724 - - - Computers and the Humanities - - 33 - 1-2 - 1999 - 103-112 - - - - - - - C. - Michael - Sperberg-McQueen - - Text in the Electronic Age: Textual Study and Text Encoding, with - Examples from Medieval Texts - 10.1093/llc/6.1.34 - - - Literary & Linguistic Computing - - 6 - 1 - 1991 - 34-46 - - - - - - - C. - Michael - Sperberg-McQueen - - The Text Encoding Initiative: Electronic Text Markup for - Research - - - - Brett - Sutton - - Literary Texts in an Electronic Age - - Urbana-Champaign, IL - University of Illinois at Urbana-Champaign, Graduate School of Library and - Information Science - 1994 - 35–55 - - - - - - - C. - Michael - Sperberg-McQueen - - Textual Criticism and the Text Encoding Initiative - - - - Richard - J. - Finneran - - The Literary Text in the Digital Age - - Ann Arbor, MI - University of Michigan Press - 1996 - 37–62 - - - - - - - Edward - Vanhoutte - - An Introduction to the TEI and the TEI Consortium - 10.1093/llc/19.1.9 - - - Literary & Linguistic Computing - - 19 - 1 - 2004 - 9 - - - - - - - T. - Kindberg - - - S. - Hawke - - The 'tag' URI Scheme - - RFC 4151 - - 2005 - IETF - - - - - -
-
-
diff --git a/P5/Source/Guidelines/fr/BIB-Bibliography.xml b/P5/Source/Guidelines/fr/BIB-Bibliography.xml new file mode 120000 index 0000000000..084ad41329 --- /dev/null +++ b/P5/Source/Guidelines/fr/BIB-Bibliography.xml @@ -0,0 +1 @@ +../en/./BIB-Bibliography.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/CC-LanguageCorpora.xml b/P5/Source/Guidelines/fr/CC-LanguageCorpora.xml deleted file mode 100644 index 5d5422140e..0000000000 --- a/P5/Source/Guidelines/fr/CC-LanguageCorpora.xml +++ /dev/null @@ -1,1160 +0,0 @@ - - - - -
Language Corpora -

The term language corpus is used to mean a number of -rather different things. It may refer simply to any collection of -linguistic data (for example, written, spoken, signed, or multimodal), although -many practitioners prefer to reserve it for collections which have -been organized or collected with a particular end in view, generally to -characterize a particular state or variety of one or more languages. -Because opinions as to the best method of achieving this goal differ, -various subcategories of corpora have also been identified. For our -purposes however, the distinguishing characteristic of a corpus is that -its components have been selected or structured according to some -conscious set of design criteria.

-

These design criteria may be very simple and undemanding, or very -sophisticated. A corpus may be intended to represent (in the -statistical sense) a particular linguistic variety or sublanguage, or -it may be intended to represent all aspects of some assumed -core language. A corpus may be made up of whole -texts or of fragments or text samples. It may be a -closed corpus, or an open or -monitor corpus, the composition of which may -change over time. However, since an open corpus is of necessity -finite at any particular point in time, the only likely effect of its -expansibility from the encoding point of view may be some increased -difficulty in maintaining consistent encoding practices (see further -section ). For simplicity, therefore, our -discussion largely concerns ways of encoding closed corpora, regarded -as single but composite texts.

-

Language corpora are regarded by these Guidelines as -composite texts rather than unitary texts -(on this distinction, see chapter ). This is -because although each discrete sample of language in a corpus clearly -has a claim to be considered as a text in its own right, it is also -regarded as a subdivision of some larger object, if only for -convenience of analysis. Corpora share a number of characteristics -with other types of composite texts, including anthologies and -collections. Most notably, different components of composite texts -may exhibit different structural properties (for example, some may be -composed of verse, and others of prose), thus potentially requiring -elements from different TEI modules.

-

Aside from these high-level structural differences, and possibly -differences of scale, the encoding of language corpora and the -encoding of individual texts present identical sets of problems. Any -of the encoding techniques and elements presented in other chapters of -these Guidelines may therefore prove relevant to some aspect of corpus -encoding and may be used in corpora. Therefore, we do not repeat here -the discussion of such fundamental matters as the representation of -multiple character sets (see chapter ); nor do we -attempt to summarize the variety of elements provided for encoding -basic structural features such as quoted or highlighted phrases, -cross-references, lists, notes, editorial changes and reference systems (see -chapter ). In addition to these general purpose -elements, these Guidelines offer a range of more specialized sets of -tags which may be of use in certain specialized corpora, for example -those consisting primarily of verse (chapter ), -drama (chapter ), transcriptions of spoken text -(chapter ), etc. Chapter -should be reviewed for details of how these and other components of -these Guidelines should be tailored to create a TEI customization -appropriate to a given application. In sum, it should not be assumed -that only the matters specifically addressed in this chapter are of -importance for corpus creators.

-

This chapter does however include some other material -relevant to corpora and corpus-building, for which no other location -appeared suitable. It begins with a review of the distinction between -unitary and composite texts, and of the different methods provided by -these Guidelines for representing composite texts of different kinds -(section ). Section describes a -set of additional header elements provided for the documentation of -contextual information, of importance largely though not exclusively to -language corpora. This is the additional module for language corpora -proper. Section discusses a mechanism by which -individual parts of the TEI header may be associated with different -parts of a TEI-conformant text. Section reviews -various methods of providing linguistic annotation in corpora, with some -specific examples of relevance to current practice in corpus -linguistics. Finally, section provides some general -recommendations about the use of these Guidelines in the building of -large corpora.

-
Varieties of Composite Text -

Both unitary and composite texts may be encoded using these -Guidelines; composite texts, including corpora, will typically make -use of the following tags for their top-level organization. - Full descriptions of these may be found in -chapter (for teiHeader), and chapter (for teiCorpus, TEI, text, and -group); this section discusses their application to composite -texts in particular.

-

In these Guidelines, the word text refers to any stretch -of discourse, whether complete or incomplete, unitary or composite, -which the encoder chooses (perhaps merely for purposes of analytic -convenience) to regard as a unit. The term composite text -refers to texts within which other texts appear; the following common -cases may be distinguished: - -language corpora -collections or anthologies -poem cycles and epistolary works (novels or essays written -in the form of collections or series of letters) -otherwise unitary texts, within which one or more subordinate -texts are embedded -The elements listed above may be combined to encode each of these -varieties of composite text in different ways.

-

In corpora, the component samples are clearly distinct texts, but the -systematic collection, standardized preparation, and common markup of -the corpus often make it useful to treat the entire corpus as a unit, -too. Some corpora may become so well established as to be regarded as -texts in their own right; the Brown and LOB corpora are now close to -achieving this status.

-

The teiCorpus element is intended for the encoding of -language corpora, though it may also be useful in encoding newspapers, -electronic anthologies, and other disparate collections of material. -The TEI element may be used in the same manner itself; the -teiCorpus element, however, makes explicit the multiplicity -of the collection, whatever it may be. The individual samples in the -corpus are encoded as separate TEI elements, and the entire -corpus is enclosed in a TEI or teiCorpus element. -Each sample has the usual structure for a TEI document, -comprising a teiHeader followed by one or more members of the -model.resource class. The corpus, too, -has a corpus-level teiHeader element, in which the corpus as -a whole, and encoding practices common to multiple samples may be -described. The overall structure of a TEI-conformant corpus is thus: - - - - - - - - - - - -Or, alternatively: - - - - - - - - - - -

-

Header information which relates to the whole corpus rather than to -individual components of it should be factored out and included in the -teiHeader element prefixed to the whole. This two-level -structure allows for contextual information to be specified at the -corpus level, at the individual text level, or at both. Discussion of -the kinds of information which may thus be specified is provided -below, in section , as well as in chapter . Information of this type should in general be -specified only once: a variety of methods are provided for associating -it with individual components of a corpus, as further described in -section .

-

In some cases, the design of a corpus is reflected in its internal -structure. For example, a corpus of newspaper extracts might be -arranged to combine all stories of one type (reportage, editorial, -reviews, etc.) into some higher-level grouping, possibly with sub-groups -for date, region, etc. A teiCorpus element may occur -directly inside a teiCorpus specifically to allow -direct support for reflecting such internal corpus structure in the -markup. For example: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

-

Furthermore, useful groupings -of components may easily be expressed using the text classification and -identification elements described in section , -and those for associating declarations with corpus components described -in section . These methods also allow several -different methods of text grouping to co-exist, each to be used as -needed at different times. This helps minimize the danger of -cross-classification and misclassification of samples, and helps -improve the flexibility with which parts of a corpus may be -characterized for different applications.

-

Anthologies and collections are often treated as texts in their own -right, if only for historical reasons. In conventional publishing, at -least, anthologies are published as units, with single editorial -responsibility and common front and back matter which may need to be -included in their electronic encodings. The texts collected in the -anthology, of course, may also need to be identifiable as distinct -individual objects for study.

-

Poem cycles, epistolary novels, and epistolary essays differ from -anthologies in that they are often written as single works, by single -authors, for single occasions; nevertheless, it can be useful to treat -their constituent parts as individual texts, as well as the cycle -itself. Structurally, therefore, they may be treated in the same way -as anthologies: in both cases, the body of the text is composed -largely of other texts.

-

The group element is provided to simplify the encoding of -collections, anthologies, and cyclic works; the group element -may also be used to record the potentially complex internal structure -of language corpora. (For a full description, see chapter .) The choice between using group or nested -teiCorpus elements is up to individual encoders, but in -general when it is useful to associate a significant quantity of -metadata with such a unit of text it is easier to use -teiCorpus.

-

Some composite texts, finally, are neither corpora, nor anthologies, -nor cyclic works: they are otherwise unitary texts within which other -texts are embedded. In general, they may be treated in the same way as -unitary texts, using the normal TEI and -body elements. The embedded text itself may be encoded using -the text element. For further discussion, see chapter .

-

All composite texts share the characteristic that their different -component texts may be of structurally similar or dissimilar types. If -all component texts may all be encoded using the same module, -then no problem arises. If however they require -different modules, then these must be included in the TEI customization. This -process is described in more detail in section .

- -
Contextual Information -

Contextual information is of particular importance for collections -or corpora composed of samples from a variety of different kinds of -text. Examples of such contextual information include: the age, sex, -and geographical origins of participants in a language interaction, or -their socio-economic status; the cost and publication data of a -newspaper; the topic, register or factuality of an extract from a -textbook. Such information may be of the first importance, whether as -an organizing principle in creating a corpus (for example, to ensure -that the range of values in such a parameter is evenly represented -throughout the corpus, or represented proportionately to the population -being sampled), or as a selection criterion in analysing the corpus -(for example, to investigate the language usage of some particular -vector of social characteristics).

-

Such contextual information is potentially of equal importance for -unitary texts, and these Guidelines accordingly make no particular -distinction between the kinds of information which should be gathered -for unitary and for composite texts. In either case, the information -should be recorded in the appropriate section of a TEI header, as -described in chapter . In the case of language corpora, -such information may be gathered together in the overall corpus header, -or split across all the component texts of a corpus, in their individual -headers, or divided between the two. The association between an -individual corpus text and the contextual information applicable to it -may be made in a number of ways, as further discussed in section below.

-

Chapter , which should be read in conjunction with -the present section, describes in full the range of elements available -for the encoding of information relating to the electronic file itself, -for example its bibliographic description and those of the source or -sources from which it was derived (see section ); -information about the encoding practices followed with the corpus, for -example its design principles, editorial practices, reference system, -etc. (see section ); more detailed descriptive -information about the creation and content of the corpus, such as the -languages used within it and any descriptive classification system used -(see section ); and version information documenting any -changes made in the electronic text (see section ).

-

In addition to the elements defined by chapter , -several other elements can be used in the TEI header if the additional -module defined by this chapter is invoked. These additional tags make -it possible to characterize the social or other situation within which a -language interaction takes place or is experienced, the physical setting -of a language interaction, and the participants in it. Though this -information may be relevant to, and provided for, unitary texts as well -as for collections or corpora, it is more often recorded for the -components of systematically developed corpora than for isolated texts, -and thus this module is referred to as being for language -corpora.

- -

When the module defined in this chapter is included in a schema, a -number of additional elements become available within the -profileDesc element of the TEI header (discussed in section -). These -elements, members of the model.profileDescPart, are discussed in the -remainder of the chapter. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

- -
The Text Description -

The textDesc element provides a full description of the -situation within which a text was produced or experienced, and thus -characterizes it in a way relatively independent of any a -priori theory of text-types. It is provided as an alternative -or a supplement to the common use of descriptive taxonomies used to -categorize texts, which is fully described in section , and section . The description is -organized as a set of values and optional prose descriptions for the -following eight situational parameters, each represented by -one of the following eight elements: -

-

These elements constitute a model class called model.textDescPart; new parameters may be defined -by defining new elements and adding them to that class, as further -described in .

- -

By default, a text description will contain each of the above -elements, supplied in the order specified. Except for the -purpose element, which may be repeated to indicate multiple -purposes, no element should appear more than once within a single text -description. Each element may be empty, or may contain a brief -qualification or more detailed description of the value expressed by -its attributes. It should be noted that some texts, in particular -literary ones, may resist unambiguous classification in some of these -dimensions; in such cases, the situational parameter in question -should be given the content not applicable or an equivalent -phrase.

-

Texts may be described along many dimensions, according to many -different taxonomies. No generally accepted consensus as to how such -taxonomies should be defined has yet emerged, despite the best efforts -of many corpus linguists, text linguists, sociolinguists, -rhetoricians, and literary theorists over the years. Rather than -attempting the task of proposing a single taxonomy of -text-types (or the equally impossible one of enumerating -all those which have been proposed previously), the closed set of -situational parameters described above can be used in -combination to supply useful distinguishing descriptive features of -individual texts, without insisting on a system of discrete high-level -text-types. Such text-types may however be used in combination with -the parameters proposed here, with the advantage that the internal -structure of each such text-type can be specified in terms of the -parameters proposed. This approach has the following analytical -advantages:Schemes similar to that proposed here were developed -in the 1960s and 1970s by researchers such as Hymes, Halliday, and -Crystal and Davy, but have rarely been implemented; one notable -exception being the pioneering work on the Helsinki Diachronic Corpus -of English, on which see - - it enables a relatively continuous characterization of texts (in -contrast to discrete categories based on type or topic) -it enables meaningful comparisons across corpora -it allows analysts to build and compare their own text-types -based on the particular parameters of interest to them -it is equally applicable to spoken, written, or signed texts

-

Two alternative approaches to the use of these parameters are -supported by these Guidelines. One is to use pre-existing taxonomies -such as those used in subject classification or other types of text -categorization. -Such taxonomies may also be appropriate for the description of the -topics addressed by particular texts. Elements for this purpose are -described in section , and elements for defining or -declaring such classification schemes in section . A -second approach is to develop an application-specific set of -feature structures and an associated feature system -declaration, as described in -chapters and .

-

Where the organizing principles of a corpus or collection so permit, -it may be convenient to regard a particular set of values for the -situational parameters listed in this section as forming a -text-type in its own right; this may also be useful where -the same set of values applies to several texts within a corpus. In -such a case, the set of text-types so defined should be regarded as a -taxonomy. The mechanisms described in section may be used to define hierarchic taxonomies of such -text-types, provided that the catDesc component of the -category element contains a textDesc element rather -than a prose description. Particular texts may then be associated with -such definitions using the mechanisms described in sections .

- -

Using these situational parameters, an informal domestic -conversation might be characterized as follows: - - informal face-to-face conversation - each text represents a continuously - recorded interaction among the specified participants - - - plans for coming week, local affairs - mostly factual, some jokes - - - - - -

-

The following example demonstrates how the same situational -parameters might be used to characterize a novel: - - print; part issues - - - - - - - - - - -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-
The Participant Description - -

The particDesc element in the profileDesc element -provides additional information about the participants in a spoken -text or, where this is judged appropriate, the persons named or -depicted in a written text. When the detailed elements provided by -the namesdates module described in are included in a schema, this element can -contain detailed demographic or descriptive information about -individual speakers or groups of speakers, such as their names or -other personal characteristics. Individually identified persons may -also identified by a code which can then be used elsewhere within the -encoded text, for example as the value of a who -attribute.

- -

It should be noted that although the terms speaker or -participant are used throughout this section, it is -intended that the same mechanisms may be used to characterize fictional -personæ or voices within a written text, except -where otherwise stated. For the purposes of analysis of language usage, -the information specified here should be equally applicable to -written, spoken, or signed texts.

-

The element particDesc contains a description of the -participants in an interaction, which may be supplied as -straightforward prose, possibly containing a list of names, encoded -using the usual list and name elements, or -alternatively using the more specific and detailed listPerson -element provided by the namesdates module -described in .

-

For example, a participant in a recorded conversation might be -described informally as follows: - -

Female informant, well-educated, born in Shropshire UK, 12 Jan - 1950, of unknown occupation. Speaks French fluently. - Socio-Economic status B2 in the PEP classification scheme.

-

- -

Alternatively, when the namesdates module -is included in a schema, information about the same participant -described above might be provided in a more structured way as follows: - - - 12 Jan 1950 - Shropshire, UK - - - English - French - - Long term resident of Hull - University postgraduate - Unknown - -

-

An identified character in a drama or a novel may also be regarded -as a participant in this sense, and encoded using -the same techniques:It is particularly useful to -define participants in a dramatic text in this way, since it enables the -who attribute to be used to link sp elements to -definitions for their speakers; see further section . - -

The chief speaking characters in this novel are - - Emma Woodhouse - Mr Darcy - - -

- -Here, the characters are simply listed without the detailed -structure which use of the listPerson element permits.

- -
-
-The Setting Description -

The settingDesc element is used to describe the setting or -settings in which language interaction takes place. It may contain a -prose description, analogous to a stage description at the start of a -play, stating in broad terms the locale, or a more detailed -description of a series of such settings.

-

Each distinct setting is described by means of a setting -element. - - - - - -Individual settings may be associated with particular participants by -means of the optional who attribute which this element -inherits as a member of the att.ascribed -if, for example, participants are in different places. This attribute -identifies one or more individual participants or participant groups, -as discussed earlier in section . If this -attribute is not specified, the setting details provided are assumed -to apply to all participants represented in the language -interaction. Note however that it is not possible to encode different -settings for the same participant: a participant is deemed to be a -person within a specific setting.

-

The setting element may contain either a prose description -or a selection of elements from the classes model.nameLike.agent, model.dateLike, or -model.settingPart. By default, when the -module defined by this chapter is included in a schema, these classes thus -provide the following elements: - - - - - - - -Additional more specific naming elements such as orgName or -persName may also be available if the -namesdates module is also included in the schema.

-

The following example demonstrates the kind of background information -often required to support transcriptions of language interactions, first -encoded as a simple prose narrative: - -

The time is early spring, 1989. P1 and P2 are playing on the rug - of a suburban home in Bedford. P3 is doing the washing up at the - sink. P4 (a radio announcer) is in a broadcasting studio in - London.

- -The same information might be represented more formally in the following -way: - - - Bedford - UK: South East - early spring, 1989 - rug of a suburban home - playing - - - Bedford - UK: South East - early spring, 1989 - at the sink - washing-up - - - London, UK - - broadcasting studio - radio performance - -

-

Again, a more detailed encoding for places is feasible if the -namesdates module is included in the -schema. The above examples assume that only the -general purpose name element supplied in the core module is -available. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

-
Associating Contextual -Information with a Text -

This section discusses the association of the contextual information -held in the header with the individual elements making up a TEI text or -corpus. Contextual information is held in elements of various kinds -within the TEI header, as discussed elsewhere in this section and in -chapter . Here we consider what happens when different -parts of a document need to be associated with different contextual -information of the same type, for example when one part of a document -uses a different encoding practice from another, or where one part -relates to a different setting from another. In such situations, there -will be more than one instance of a header element of the relevant type.

-

The TEI scheme allow for the following possibilities: - -A given element may appear in the corpus header only, in the -header of one or more texts only, or in both places -There may be multiple occurrences of certain elements in either -the corpus or a text header.

-

To simplify the exposition, we deal with these two possibilities -separately in what follows; however, they may be combined as -desired.

-
Combining Corpus and Text Headers -

A TEI-conformant document may have more than one header only in the -case of a TEI corpus, which must have a header in its own right, as well -as the obligatory header for each text. Every element specified in a -corpus-header is understood as if it appeared within every text header -in the corpus. An element specified in a text header but not in the -corpus header supplements the specification for that text alone. If any -element is specified in both corpus and text headers, the corpus header -element is over-ridden for that text alone.

-

The titleStmt for a corpus text is understood to be -prefixed by the titleStmt given in the corpus header. All -other optional elements of the fileDesc should be omitted from -an individual corpus text header unless they differ from those -specified in the corpus header. All other header elements behave -identically, in the manner documented below. -This facility makes it possible to state once for all in the corpus -header each piece of contextual information which is common to the whole -of the corpus, while still allowing for individual texts to vary from -this common denominator.

-

For example, the following schematic shows the structure of a corpus -comprising three texts, the first and last of which share the same -encoding description. The second one has its own encoding description. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

-
Declarable Elements - -

Certain of the elements which can appear within a TEI header are -known as declarable elements. These elements have in -common the fact that they may be linked explicitly with a particular -part of a text header or the corpus header by means of a decls attribute on -that element. This linkage is used to over-ride the default -association between declarations in the header and a corpus or corpus -text. The only header elements which may be associated in this way are -those which would not otherwise be meaningfully repeatable.

-

Declarable elements are all members of the class att.declarable; the corresponding declaring -elements are all members of the class att.declaring. - - - -

- -

An alphabetically ordered list of declarable elements follows: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -Each of the above elements is repeatable within a single -header; that is, there may be more than one instance of any declarable -element type at a given level. When this occurs, the following rules -apply. For each different type of declarable element which occurs more -than once: - -each must bear a unique identifier -when occurring within the same parent element, exactly one element must be -specified as the default, by having a default attribute with the value "true". -

-

In the following example, an editorial declaration contains two -possible correction policies, one identified as -CorPol1 and the other as CorPol2. Since there -are two, one of them (in this case CorPol1) should be -specified as the default: - -

...

- - -

...

- - -

...

-

...

- - For texts associated with the header in which -this declaration appears, correction method CorPol1 will be -assumed, unless they explicitly state otherwise. Here is the -structure of a text in which a division states otherwise: - - - - - - In this case, the contents of the divisions D1 and D3 -will both use correction policy CorPol1, and those of -division D2 will use correction policy CorPol2.

-

The decls attribute is defined for any element which is a -member of the class declaring. This includes the major -structural elements text, group, and div, as -well as smaller structural units, down to the level of paragraphs in -prose, individual utterances in spoken texts, and entries in -dictionaries. However, TEI recommended practice is to limit the number -of multiple declarable elements used by a document as far as possible, -for simplicity and ease of processing.

-

The identifier or identifiers to which the decls -attribute points must follow two further restrictions: - -When decl references an element that itself contains multiple -elements of the same type, only the children elements with default -set to "true" are considered referenced. -Each element specified, explicitly or implicitly, by the list of -identifiers must be of a different kind.

-

To demonstrate how these rules operate, we now expand our earlier -example slightly: - - - - -

...

- -

...

- -

...

-

...

- - - -

...

-

...

-

...

-

...

- - -

-

This encoding description now has two editorial declarations, -identified as ED1 (the default) and ED2. For texts not specifying -otherwise, ED1 will apply. If ED1 applies, correction method C1A and -normalization method N1 apply, since these are the specified defaults -within ED1. In the same way, for a text specifying decls as -#ED2, correction C2A, - and normalization N2B will -apply.

-

A finer grained approach is also possible. A text might specify -text decls='#C2B #N2A', - to mix and match declarations as -required. A tag such as text decls='#ED1 #ED2' would -(obviously) be illegal, since it includes two elements of the same type; -a tag such as text decls='#ED2 #C1A' is also illegal, since in -this context #ED2 is synonymous with the defaults for that -editorial declaration, namely #C2A #N2B, resulting in a list -that identifies two correction elements (C1A and C2A).

-
Summary -

The rules determining which of the declarable elements are applicable -at any point may be summarized as follows: - -If there is a single occurrence of a given declarable -element in a corpus header, then it applies by default to all elements -within the corpus. -If there is a single occurrence of a given declarable -element in the text header, then it applies by default to all elements -of that text irrespective of the contents of the corpus header. -Where there are multiple occurrences of declarable elements - within a text’s header or its corpus header, - -each must have a unique value specified as the value -of its xml:id attribute; -one and only one must bear a default attribute with - the value true (or 1). -It is a semantic error for an element to be associated -with more than one occurrence of any declarable element. -Selecting an element which contains multiple occurrences of a -given declarable element is semantically equivalent to selecting only -those contained elements which are specified as defaults. -An association made by one element applies by default -to all of its descendants. -

-
Linguistic Annotation of Corpora -

Language corpora often include analytic encodings or annotations, -designed to support a variety of different views of language. The -present Guidelines do not advocate any particular approach to linguistic -annotation (or tagging); instead a number of -general analytic facilities are provided which support the -representation of most forms of annotation in a standard and -self-documenting manner. Analytic annotation is of importance in many -fields, not only in corpus linguistics, and is therefore discussed in -general terms elsewhere in the -Guidelines.See in particular chapters -, , and . -The present section presents informally some particular applications of -these general mechanisms to the specific practice of corpus linguistics.

-
Levels of Analysis -

By linguistic annotation we mean here any annotation -determined by an analysis of linguistic features of the text, excluding -as borderline cases both the formal structural properties of the text -(e.g. its division into chapters or paragraphs) and descriptive -information about its context (the circumstances of its production, its -genre, or medium). The structural properties of any TEI-conformant text -should be represented using the structural elements discussed elsewhere -in these Guidelines, for example in chapters and -. -The contextual -properties of a TEI text are fully documented in the TEI header, which -is discussed in chapter , and in section of the present chapter.

-

Other forms of linguistic annotation may be applied at a number of -levels in a text. A code (such as a word-class or part-of-speech -code) may be associated with each word or token, or with groups of such -tokens, which may be continuous, discontinuous, or nested. A code may -also be associated with relationships (such as cohesion) perceived as -existing between distinct parts of a text. The codes themselves may -stand for discrete non-decomposable categories, or they may represent -highly articulated bundles of textual features. Their function may be -to place the annotated part of the text somewhere within a narrowly -linguistic or discoursal domain of analysis, or within a more general -semantic field, or any combination drawn from these and other domains.

-

The manner by which such annotations are generated and attached to -the text may be entirely automatic, entirely manual, or a mixture. The -ease and accuracy with which analysis may be automated may vary with the -level at which the annotation is attached. The method employed should -be documented in the interpretation element within the encoding -description of the TEI header, as described in section . Where different parts of a corpus have used different -annotation methods, the decls attribute should be used to -indicate the fact, as further discussed in section .

-

An extended example of one form of linguistic analysis commonly -practised in corpus linguistics is given in section .

-
-
Recommendations for the Encoding of Large Corpora -

These Guidelines include proposals for the identification and -encoding of a far greater variety of textual features and -characteristics than is likely to be either feasible or desirable in -any one language corpus, however large and ambitious. The reasoning -behind this universal approach is further discussed in chapter . -For most large-scale corpus projects, it will therefore -be necessary to determine a subset of TEI recommended elements -appropriate to the anticipated needs of the project, as further -discussed in chapter ; these mechanisms include -the ability to exclude selected element types, add new element types, -and change the names of existing elements. A discussion of the -implications of such changes for TEI conformance is provided in -chapter .

-

Because of the high cost of identifying and encoding many textual -features, and the difficulty in ensuring consistent practice across very -large corpora, encoders may find it convenient to divide the set of -elements to be encoded into the following four categories: - -texts included within the corpus will always -encode textual features in this category, should they exist in the -text -textual features in this category will be -encoded wherever economically and practically feasible; where present -but not encoded, a note in the header should be made. -textual features in this category may or may not -be encoded; no conclusion about the absence of such features can be -inferred from the absence of the corresponding element in a given -text. - -textual features in this category are deliberately not encoded; they may be -transcribed as unmarked up text, or represented as gap -elements, or silently omitted, as appropriate.

-
-
- Module for Language Corpora -

The module described in this chapter makes available the - following components: - - Metadata for Language Corpora - Corpus texts - Corpus linguistiques - 文集文本 - Corpus di testi - Textos do corpora - コーパスモジュール - - - - The selection and combination of modules to form a TEI schema is - described in .

-
- -
diff --git a/P5/Source/Guidelines/fr/CC-LanguageCorpora.xml b/P5/Source/Guidelines/fr/CC-LanguageCorpora.xml new file mode 120000 index 0000000000..355a055774 --- /dev/null +++ b/P5/Source/Guidelines/fr/CC-LanguageCorpora.xml @@ -0,0 +1 @@ +../en/./CC-LanguageCorpora.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/CE-CertaintyResponsibility.xml b/P5/Source/Guidelines/fr/CE-CertaintyResponsibility.xml deleted file mode 100644 index 424088a4c3..0000000000 --- a/P5/Source/Guidelines/fr/CE-CertaintyResponsibility.xml +++ /dev/null @@ -1,611 +0,0 @@ - - - - -
Certainty, Precision, and Responsibility -

Encoders of text often find it useful to indicate that some aspects -of the encoded text are problematic or uncertain, and to indicate who is -responsible for various aspects of the markup of the electronic text. -These Guidelines provide several methods of recording uncertainty about the -text or its markup: - -the note element defined in section may -be used with a value of certainty for its type -attribute. -the certainty element defined in this chapter may be used -to record the nature and degree of the uncertainty in a more structured -way. -the precision element defined in this chapter may be -used to record the accuracy with which some numerical value (such as a -date or quantity) is provided by some other element or attribute. -the alt element defined in the module for -linking and segmentation may be used to provide alternative encodings -for parts of a text, as described in section . -There are three methods of indicating responsibility for different -aspects of the electronic text: - -the TEI header records who is responsible for an electronic text -by means of the respStmt element and other more specific elements -(author, sponsor, funder, principal, -etc.) used within the titleStmt, editionStmt, and -revisionDesc elements. -the note element may be used with a value of resp -or responsibility in its type attribute. -the respons element defined in this chapter may be used -to record fine-grained structured information about responsibility for -individual tags in the text. -No special steps are needed to use the note and respStmt elements, since they are defined in the core module and header -respectively. The alt element is only available when the -module for linking has been selected, as described in -chapter . To use the certainty, precision or -respons elements, the module for certainty and -responsibility should be selected. -

- -

These three elements are all members of an attribute class called -att.scoping from which they inherit the -following attributes: - - - - -

-

These attributes enable statements about certainty, precision, or -responsibility to be made with respect to the whole of a document, or -any part or parts of it which can be identified using standard XML -location methods. Several examples are given in the discussion of the -certainty element below; the same mechanisms are available -for all three elements discussed in this chapter. -

-
Levels of Certainty -

Many types of uncertainty may be distinguished. The -certainty element is designed to encode the following sorts: - -a given tag may or may not correctly apply (e.g. a given word may -be a personal name, or perhaps not) -the precise point at which an element begins or ends is -uncertain -the value given for an attribute is uncertain -the content given for an element is unreliable for any reason.

-

The following types of uncertainty are not indicated -with the certainty element: - -the numerical precision associated with a number or date (for -this use the precision element discussed in ) - -the content of the document being transcribed is identifiable, -but may be read or understood in different ways -(for this use the transcriptional elements such as unclear, -discussed in chapter ) -a transcriber, editor, or author wishes to indicate a level of -confidence in a factual assertion made in the text (for this use the -interpretative mechanisms discussed in and ) - -

-
Using Notes to Record Uncertainty -

The simplest way of recording uncertainty about markup is to attach a -note to the element or location about which one is unsure. In the -following (invented) paragraph, for example, an encoder might be -uncertain whether to mark Essex as a place name or a personal -name, since both might be plausible in the given context: -Elizabeth went to Essex. She had always liked Essex. -Using note, the uncertainty here may be recorded quite simply: -Elizabeth went to Essex. She had always liked Essex.It is not -clear here whether Essex -refers to the place or to the nobleman. -MSM

-

Using the normal mechanisms, the note may be associated -unambiguously with specific elements of the text, thus: -Elizabeth went to Essex. -She had always liked Essex.It -is not clear here whether Essex -refers to the place or to the nobleman. If the latter, -it should be tagged as a personal name. -Michael

-

The advantage of this technique is its relative simplicity. Its -disadvantage is that the nature and degree of uncertainty are not -conveyed in any systematic way and thus are not susceptible to any sort -of automatic processing.

-
Structured Indications of Uncertainty -

To record uncertainty in a more structured way, susceptible of at -least simple automatic processing, the certainty element may be -used: -

-

Returning to the example, the certainty element may be used to record doubts about -the proper encoding of Essex in several ways of varying -precision. To record merely that we are not certain that Essex -is in fact a place name, as it is tagged, we use the target -attribute to identify the element in question, and the locus -attribute to indicate which aspect of the markup we are uncertain about -(in this case, whether we have used the correct name for the -element used to mark it): -Elizabeth went to -Essex. - -possibly not a placename -There are no particular constraints as to where the -certainty element is placed in a document; it may be placed adjacent to the target -element, or elsewhere in the same or another document. Its position -is however significant when the target attribute is not specified -as further discussed below. -

-

We may wish to record the probability, assessed in some subjective -way, that Essex really is a place name here. The -degree attribute is used to indicate the degree of -confidence associated with the certainty element, expressed as a -number between 0 and 1: - - - -This expresses the point of view that there is a 60 percent chance of Essex -being a place name here, and hence a 40 percent chance of its being a -personal name. We can use two certainty elements to indicate the -two probabilities independently. Both elements indicate the same location in the -text, but the second provides an alternative choice of name -identifier (in this case persName), which is given as the -value of the assertedValue attribute: - - - - probably a placename, but possibly not - - may refer to the Earl of Essex

- -

In the simplest case, it is also possible to place the -certainty element within the element concerned: - -Elizabeth went to -Essex -. -When no target is specified, by default the proposed -certainty applies to its parent element, in this case the -placeName element. The match attribute discussed -below may be used to further vary this behaviour.

- -
Contingent Conditions - -

Finally, we may wish to make our probability estimates contingent -on some condition. In the passage Elizabeth went to Essex; she had -always liked Essex, for example, we may feel there is a 60 percent chance -that the county is meant, and a 40 percent chance that the earl is meant. But -the two occurrences of the word are not independent: there is (we may -feel) no chance at all that the first occurrence refers to the county -and the second -to the earl. We can express this by using the given -attribute to list the identifiers of certainty elements. -Elizabeth went to Essex. -She had always liked Essex. - - - - probably a placename, but possibly not" - - may refer to the Earl of Essex" - - - if CE-PL1 is a placename, CE-PL2 certainly is" - - if CE-PL1 is a personal name, then so is CE-PL2 -When given conditions are listed, the certainty -element is interpreted as claiming a given degree of confidence in a -particular markup given the assertional content of the -certainty elements indicated. That is, a conjectural -assertion is being made solely on the assumption that the -interpretation indicated by the element named by the given -attribute is actually correct.

- -

Conditional confidence may be less than 100 percent: given the sentence -Ernest went to old Saybrook, we may interpret Saybrook as -a personal name or a place name, assigning a 60 percent probability to the -former. If it is a place name, there may be a 50 percent chance that the -place name actually in question is Old Saybrook rather than -Saybrook, while if it is correctly tagged as a personal name, it -is much more likely (say, 90 percent certain) that the name is Saybrook. -Hence there is uncertainty about the correct location for the markup -as well as about which markup to use. This state of affairs can be expressed using the certainty element thus: -Ernest went to old Saybrook. - - - - - - - -Note the use of the assertedValue on certainty -elements cert3 and cert4 to reference -the anchor element placed at the alternative starting -point for the element.

- -

Multiplying the numeric values out, this markup may be interpreted as -assigning specific probabilities to three different ways of -marking up the sentence: -Ernest went to old Saybrook. (0.6 * 0.9, or 0.54) -Ernest went to old Saybrook. (0.4 * 0.5, or 0.20) -Ernest went to old Saybrook. (0.4 * 0.5, or 0.20) -The probabilities do not add up to 1.00 because the markup indicates -that if Saybrook is (part of) a personal name, there is a -10 percent likelihood that the element should start somewhere other than the -place indicated, without however giving an alternative location; there -is thus a 6 percent chance (0.1 × 0.6) that none of the alternatives given is -correct.

-
-
Pervasive Conditions -

We may also wish to indicate confidence in some aspect -of the tagging throughout a document, rather than (as discussed so far) in one -particular instance. The match attribute may be used to -supply a pattern identifying the portion of a document -concerning which certainty is being expressed. The value of the -match attribute is an XSLT selection pattern -using the syntax defined in . In the following -example, we wish to indicate a low degree of confidence -that the persName elements used throughout the whole document -have been correctly applied: - - - - - -No target has been supplied here, and so by default the -certainty expressed would therefore apply to the parent -element. However, in this case the XPath supplied as the value for -match returns a set of all the persName elements -in the document, independent of the current context. By contrast, in -the following example - -

[...]

-
- -
- -only the persName elements within the second div -element are in question. -Similarly, we may indicate that we have more -confidence in the persName tagging within those div -elements which have a type value of checked: - - - - - -If an element in a document is matched by more than one match -expression, then the most specific pattern applies. Specificity of -pattern matching is defined further in the XSLT3 reference cited above -(see ) As a -simple case, if both the preceding certainty elements were -present in the same document, a persName occurring within a -div type="checked" element would potentially match both -pattern expressions. However because the second pattern is more -specific than the former, in fact this is the only one that would -apply. If multiple patterns match and have the same priority, then the -first one (in document order) is applied. Only those statements of certainty -which have matched in this sense are available for conditional -application using the given attribute mentioned above. -

-

When the match attribute is processed, the namespace bindings in -force are those in effect at that point in the document. -For example, - -

- - -
- -might be used to indicate a high degree of certainty about the content -of any elements taken the namespace associated with the prefix -my. This namespace prefix must be associated with an -appropriate namespace definition, either on the certainty -element itself, or on one of its ancestor elements.

-
- -
Content Uncertainty - -

Doubts about whether the content of an element is correct may also be expressed -by assigning to locus the value -value. For example, if the source is -hard to read and so the transcription is uncertain: -I have a bun. -

-

Degrees of confidence in the proper expansion of abbreviations may -also be expressed, as in the following example:You will want to use -Standard -Generalized Markup Language -Some Grandiose Methodology for Losers -SGML ... - - -

-

The assertedValue attribute should be used to provide an -alternative value for whatever aspect of the markup is in doubt: an -alternative name, or the identifier of an alternative starting or -ending point, as already shown, an alternative attribute value, or -alternative element content, as in this example: -I have a bun. - - a gun makes more sense in a holdup - Since attribute values have no internal substructure, the - assertedValue attribute is not generally useful for - specifying alternative transcriptions; it cannot for example be used - if the alternative reading contains markup of any kind. More robust - methods of handling uncertainties of transcription are the - unclear element and the app and rdg - elements described in chapter . The - certainty element allows for indications of uncertainty to - be structured with at least as much detail and clarity as appears to - be currently required in most ongoing text projects.

-
- - -
Target or Match? - -

As noted in , the target attribute -may take any general teidata.pointer as values and may thus -also contain an XPath expression of arbitrary complexity. Because full -support for XPath is not provided by current processors, it is not -generally recommended TEI practice. There are however some simple -cases in which XPath syntax is to be preferred, notably those in which -the xml:id attribute is used to identify a single element -occurrence. The usage #A (to indicate the element whose -xml:id attribute has the value A) is -syntactically much simpler than the equivalent xpath2 expression -//*[@xml:id='A'] and is hence preferred throughout these -guidelines. -

-

For similar reasons, the certainty element may specify -both a target value (expressed as an URI) and a -match value (expressed as an XPath). The former defines -the context within which the latter is to be evaluated. As previously -noted, if no value is supplied for target, the context -within which the value of match should be evaluated is the -parent element of the certainty element itself.

- -

A typical case where it may be convenient to specify both -target and match is that where we wish to -indicate that the value of an attribute on some specific element is -uncertain. In this case, the locus attribute -takes the value value. For example, supposing there is only a 50 percent chance that the question was spoken by -participant A: -Have you heard the election results? - or, equivalently and without the -need to define a target, -Have you heard the election results? - - -

- -

The match and target attributes together -provide a powerful mechanism which can be used to indicate precision for a -large number of assertions throughout an encoded document in an -economical way. Some further -examples follow: - - - -This encoding indicates that there is only a 0.2 certainty that the -boundaries of all p elements in the document have been correctly -identified.

-

- - - -This encoding indicates that there is only a 0.2 certainty that the -boundaries of the p elements contained by the element with -xml:id value a101 have been correctly -identified.

-

- - -Essex - - -This encoding indicates that there is only a 0.2 certainty that the -value for the resp attribute on the given persName -element -is correct.

-

- - - -This encoding indicates that there is only a 0.2 certainty that any -value for the resp attribute is correct, wherever it -appears in the document.

- -

- - -This encoding indicates that there is only a 0.2 certainty that the -value for the resp attribute of the element indicated by -the pointer #dd001 is correct

- -

- - -This encoding indicates that there is only a 0.2 certainty that the -content of any element the resp attribute of which has the -value #LB is correct, wherever it -appears in the document.

- -

The certainty element and the other TEI mechanisms for -indicating uncertainty provide a range of methods of graduated -complexity. Simple expressions of uncertainty may be made by using -the note element. This is simple and convenient, and can -accommodate either a discursive and unstructured indication of -uncertainty, or a complex and structured but probably project-specific -expression of uncertainty. In general, however, unless special steps -are taken, the note element does not provide as much -expressive power as the certainty element, and in cases where -highly structured certainty information are needed, it is -recommended that the certainty element be preferred.

- - - - - -
-
- -
- -
Indications of Precision -

As noted above, certainty about the accuracy of an encoding or its -content is not the same thing as the precision with which -a value is specified. In the case of a date or a quantity, for example, we might be -certain that the value given is imprecise, or uncertain -about whether or not the value given is correct. The latter -possibility would be represented by the certainty element -discussed in the previous section; the former by the -precision element discussed in this section.

-

The elements concerning which statements of precision are to be -made are identified using the same target and -match attributes inherited from the -att.scoping class discussed in the -previous section and in the same way. Other aspects are provided by -other attributes as further discussed below. - - - -

-

In several ways of indicating ranges of -values were introduced. For example, if we know that a date falls between -1930 and 1935, without being certain exactly where, this fact may be -encoded using attributes notBefore and -notAfter, as in the following example: - -Early in the 1930s... -Equally, if we know that every page of a -manuscript has a width of at least 10 cm but no more than 30, we can -use the attributes atLeast and atMost, as in the -following examples: - - -

-

Suppose however that the precision with which the value -of such an attribute can be specified is variable. For example, -suppose an event is dated about fifty years after the death of -Augustus. In this case, the precision of one end of the range (the -death of Augustus) is higher than the other, assuming we know when -Augustus died. We can say that the latest possible date is probably 50 -years after that, but with less confidence than we can attach to the -earliest possible date.

-

The precision element allows us to indicate the two -attributes concerned and attach different levels of precision to them, -using a similar mechanism as that provided for the certainty -element: - -About 50 -years after the death of Augustus - - -

-

In much the same way, we may wish to indicate different levels of -precision about the dating of either end of a historical period. For example, - the elements defined for encoding personal data all bear a similar - set of attributes to indicate normalized values for earliest or - latest dates, etc. (see section - ); the precision of these attribute values - may be indicated in exactly the same way. For example, - -From the 1st of March to -some time in April of 1857. - - -

-

It may also be useful to indicate that the precisions given for -minimum and maximum quanta differ. For example, to indicate that all -pages measure at least 10 cm wide, and at most about 30: - - - - -

-

The -stdDeviation attribute may be used to indicate the -standard deviation for a range of values. The generic dim -element introduced in might be used to record the average -number of characters per line in a typescript. If in addition we wish -to record the standard deviation for the values summarized by that -average, this would require an additional precision element, -as in the following example: - - - - -

-
- -
Attribution of Responsibility -

In general, attribution of responsibility for the transcription and -markup of an electronic text is made by respStmt elements -within the header: specifically, within the title statement, the -edition statement(s), and the revision history.

-

In some cases, however, more detailed element-by-element information -may be desired. For example, an encoder may wish to distinguish between the -individuals responsible for transcribing the content and those -responsible for determining that a given word or phrase constitutes a -proper noun. Where such fine-grained attribution of responsibility is -required, the respons element can be used. -

-

This element allows one or more aspects of the markup to be -attributed to a given individual. This element inherits the -target and match attributes from the -att.scoping class, in the same way as the -certainty and precision elements. Its -locus attribute functions in the same way as that on the -certainty element (see ). It inherits the resp and cert -attributes from the att.global.responsibility class. -

-

For example, the following encoding -indicates that RC is responsible for transcribing an -illegible word, and that PMWR is responsible for identifying that word -as a proper noun, i.e. deciding to mark it with the persName -element at the location indicated: -Ernest went to old -Saybrook. - - - - - - -

-

Similarly, in the following example, we indicate that RC is -responsible for proposing the value of the rend attribute: - - - -

- - -
- -
The Certainty Module -

The module described in this chapter makes available the following -additional elements: - - - Certainty and Uncertainty - Certainty, Precision, and Responsibility - Degré de certitude et responsabilité - 確定程度與不確定程度 - Certezza e incertezza - Certeza e incerteza - 確信度モジュール - - - -The selection and combination of modules to form a TEI schema is described in -. - -

-
\ No newline at end of file diff --git a/P5/Source/Guidelines/fr/CE-CertaintyResponsibility.xml b/P5/Source/Guidelines/fr/CE-CertaintyResponsibility.xml new file mode 120000 index 0000000000..564f456474 --- /dev/null +++ b/P5/Source/Guidelines/fr/CE-CertaintyResponsibility.xml @@ -0,0 +1 @@ +../en/./CE-CertaintyResponsibility.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/CH-LanguagesCharacterSets.xml b/P5/Source/Guidelines/fr/CH-LanguagesCharacterSets.xml deleted file mode 100644 index 9292be69c7..0000000000 --- a/P5/Source/Guidelines/fr/CH-LanguagesCharacterSets.xml +++ /dev/null @@ -1,715 +0,0 @@ - - - - -
-Languages and Character Sets -

The documents which users of these Guidelines may wish to encode -encompass all kinds of material, potentially expressed in the full -range of written and spoken human languages, including the extinct, -the non-existent, and the conjectural. Because of this wide scope, -special attention has been paid to two particular aspects of the -representation of linguistic information often taken for granted: -language identification and character encoding.

-

Even within a single document, material in many different languages -may be encountered. Human culture, and the texts which embody it, is -intrinsically multilingual, and shows no sign of ceasing to be so. -Traditional philologists and modern computational linguists alike work -in a polyglot world, in which code-switching (in the linguistic sense) -and accurate representation of differing language systems constitute -the norm, not the exception. The current increased interest in studies -of linguistic diversity, most notably in the recording and -documentation of endangered languages, is one aspect of this long -standing tradition. Because of their historical importance, the needs -of endangered and even extinct languages must be taken into account -when formulating Guidelines and recommendations such as these.

-

Beyond the sheer number and diversity of human languages, it should -be remembered that in their written forms they may deploy a huge -variety of scripts or writing systems. These scripts are in turn -composed of smaller units, which for simplicity we term here -characters. A primary goal when encoding a text should be to capture -enough information for subsequent users to correctly identify -not only the constituent characters, but also the language and script. In this chapter we -address this requirement, and propose recommended mechanisms to -indicate the languages, scripts and characters used in a document or a -part thereof.

-

Identification of language is dealt with in . In summary, it recommends the use of pre-defined -identifiers for a language where these are available, as they -increasingly are, in part as a result of the twin pressures of an -increasing demand for language-specific software and an increased -interest in language documentation. Where such identifiers are not -available or not standardized, these Guidelines recommend a method for -documenting language identifiers and their significance, in the same -way as other metadata is documented in the TEI header.

-

Standardization of the means available to represent characters and -scripts has moved on considerably since the publication of the first -version of these Guidelines. At that time, it was essential to -explicitly document the characters and encoded character sets used by -almost any digital resource if it was to have any chance of being -usable across different computer platforms or environments, but this -is no longer the case. With the availability of the Unicode standard, -more than 128,000 different characters representing almost all of the world's -current writing systems are available and usable in any XML processing -environment without formality. Nevertheless, however large the number -of standardized characters, there will always be a need to encode -documents which use non-standard characters and glyphs, particularly -but not exclusively in historical material. The second part of -this chapter discusses in some detail the concepts and -practice underlying this standard, and also introduces the methods -available for extending beyond it, which are more fully discussed in -.

- -
Language Identification - -

Identification of the language a document or part thereof is -written in is a crucial requirement for many envisioned usages of -an electronic document. The TEI therefore accommodates this need in the -following way: - A global attribute xml:lang is defined for all TEI - elements. Its value identifies the language and writing system - used. - The TEI header has a section set aside for the information - about the languages used in a document: see further . -

-

The value of the attribute xml:lang identifies the -language (and, optionally, script) using a coded value. For maximal compatibility with existing -processes, the identifier for the language must be constructed as in -Best Current Practice 47Currently -BCP 47 comprises two Internet Engineering Task Force documents, -referred to separately as RFC 5646 and RFC 4647; over time, other IETF -documents may succeed these as the best current practice.. This -same identifier has to be used to identify -the corresponding language element in the TEI header, if one -is present.

-

The first part of BCP 47 is called Tags for Identifying -Languages, and proposes the following mechanism for -constructing an identifier (tag) for languages as administered by the -Internet Assigned Numbers Authority (IANA). The tag is assembled from -a sequence of subtags separated by the hyphen (-, U+002D) character. -It gives the language (possibly further identified with a -sublanguage), a script, and a region for the language, each possibly -followed by a variant subtag.

-

The authoritative list of registered subtags is maintained by IANA -and is available at . -For a good general overview of the construction of language tags, see -, -and for a practical step-by-step guide, see .

-

In addition to the list of registered subtags, BCP 47 provides -extensions that can be employed by private convention. The constructs -provided can thus be used to generate identifiers for any language, -past and present, in any usage in any area of the world. If such -private extensions are used within the context of the TEI, they should -be documented within the language element of the TEI header, -which might also provide a prose description of the language described -by the language tag.

- -

While language, region, and script can be adequately identified -using this mechanism, there is only very rough provision to express a -dimension of time for the language of a document; those codes provided -(e.g. grc for Greek, Ancient (to 1453)) might not -reflect the segments appropriate for a text at hand. Text encoders -might express the time window of the language used in the document by -means of the extension mechanism defined in BCP 47 and relate that -to a date element in the corresponding language -section of the TEI header.

-

Equivalences to language identifiers by other authorities can be -given in the language section as well, but no formal -mechanism for doing so has been defined.

-

The scope of the language identification extends to the whole -subtree of the document anchored at the element that carries the -xml:lang attribute, including all elements and those -attributes, if any, where a language might apply.This excludes all attributes where a non-textual -datatype has been specified, for example tokens, boolean values, -dates, and predefined value lists.

- -
- Characters and Character Sets -

All document encoding has to do with representing one thing by - another in an agreed and systematic way. Applied to the smallest - distinctive units in any given writing system, which for the - moment we may loosely call characters, such representation - raises surprisingly complex and troublesome issues. The reasons - are partly historical and partly to do with conceptual - unclarities about what is involved in identifying, encoding, - processing and rendering the characters of a natural - language.

-
- Historical Considerations -

When the first methods of representing text for storage or - transmission by machines were devised, long before the - development of computers, the overriding aim was to identify the - smallest set of symbols needed to convey the essential semantic - content, and to encode that symbol set in the most economical - way that the storage or transmission media allowed. The initial - outcome were systems that encoded only such content as could be - expressed in uppercase letters in the Latin script, plus a few - punctuation marks and some control characters needed to - regulate the storage and transmission devices. Such encodings, - originally developed for telegraphy, strongly influenced the way - the pioneers of computing conceived of and implemented the - handling of text, with consequences that are with us still.

-

For many years after the invention of computers, the way they - represented text continued to be constrained by the imperative - to use expensive resources with maximal efficiency. Even when - storage and processing costs began their dramatic fall, the - Anglo-centric outlook of most hardware designers and software - engineers hampered initiatives to devise a more generous and - flexible model for text representation. The wish to retain - compatibility with legacy data was an additional disincentive. - Eventually, tension in East Asia between commitment to - technological progress and the inability of existing computers - to cope with local writing systems led to decisive developments. - Japanese, Korean, and Chinese standards bodies, who long before - the advent of computers had been engaged in the specification of - character sets, joined with computer manufacturers and software - houses to devise ways of mapping those character sets to numeric - encodings and processing the resulting text data.

-

Unfortunately, in the early years there was little or no - co-ordination among either the national standards bodies or the - manufacturers concerned, so that although commercial necessity - dictated that these various local standards were all compatible - with the representation of US-American English, they were not - straightforwardly compatible with one another. Even within Japan - itself there emerged a number of mutually incompatible systems, - thanks to a mixture of commercial rivalry, disagreements about - how best to manage certain intractable problems, and the fact - that such pioneering work inevitably involved some false starts, - leading to incompatibilities even between successive products of - the same bodies. Roughly at the same time, and for similar - reasons, multiple and incompatible ways of representing - languages that use Cyrillic scripts were devised, along with - methods of encoding ancient writing systems which inevitably - could not aim for compatibility with other writing systems apart - from basic Latin script. Many of the earliest projects that fed - into the TEI were shaped in this developmental phase of the - computerized representation of texts, and it was also the - context in which SGML was devised and finalized.

-

SGML had of necessity to offer ways of coping with multiple - writing systems in multiple representations; or rather, it - provided a framework within which SGML-compliant applications - capable of handling such multiple representations might be - developed by those with sufficient financial and personnel - resources (such as are seldom found in academia). Earlier - editions of these Guidelines offered advice on character set and - writing system issues addressed to the condition of those for - whom SGML was the only feasible option. That advice is here - substantially altered because of two closely-related - developments: the availability of the ISO/Unicode character set - as an international standard, and the emergence of XML and - related technologies which are committed to the theory and - practice of character representation which Unicode embodies. -

-
Terminology and Key - Concepts

Before the significance of Unicode and the - implications of the association between XML and Unicode can be - adequately explained, it is necessary to clarify some key - concepts and attempt to establish an adequately precise - terminology for them.

-

- - Examples of the latin a, in both lower and upper case, rendered with different fonts. - Examples of the latin a, in both lower and upper case, rendered with different fonts. -

-

- The word character will not of itself take us - very far towards greater terminological precision. It tends to be - used to refer indiscriminately both to the visible symbol on a - page and to the letter or ideograph which that symbol represents, - two things that it is essential to keep conceptually distinct. The - visible symbol obviously has some aspects by which we interpret it - as representing one character rather than another; but its - appearance may also be significantly determined by features that - have no effect on our notion of which character in a writing - system it represents. A familiar instance is the lowercase - a, which in printed texts may be - represented either by a single storey symbol - (cf. figure 1 in the examples from - URW Gothic L on the bottom row) or by a two - storey version (as in figure - 1 in the examples from Umpush, or URW Bookman L Demi Bold). - We say that the single and double-storey symbols both represent - one and the same the same abstract - character a using two different - glyphs. Similarly, an uppercase - A in a serif typeface has additional - strokes that are absent from the same letter when printed using a - sans-serif typeface, so that once again we have differing glyphs - standing for the same abstract character. The distinction - between abstract characters and glyphs is fundamental to all - machine processing of documents.

-

In most scholarly encoding projects, the accurate recording of - the abstract characters which make up the text is of prime - importance, because it is the essential prerequisite of - digitizing and processing the document without semantic loss. In - many cases (though there are important exceptions, to be touched - on shortly) it may not be necessary to encode the specific - glyphs used to render those abstract characters in the original - document. An encoding that faithfully registers the abstract - characters of a document allows us to search and analyse our - document's content, language, and structure, and to access its full - semantics. That same encoding, however, may not contain - sufficient information to allow an exact visual representation - of the glyphs in the source text or manuscript to be recreated. -

-

The importance of this distinction between information content - and its visual representation is not always immediately apparent - to people unused to the specific complexities of text handling - by machine. Such users tend to ask first what (in order of - conceptual priority) should actually be their very last - question: how do I get a physical image that looks like - character x in my source document to appear on to the screen or - the output page? Their first question should in fact be: how can - I get an abstract representation of character x into my encoded - document in a way that will be universally and unambiguously - identifiable, no matter what it happens to look like in printout - or on any particular display? And occasionally the response they - receive as a result of their misguided initial question is a - custom solution that satisfies their - immediate rendering wishes at the price of making their - underlying document unintelligible to other users (or even to - the original user in other times and places) because it encodes - the abstract character in an idiosyncratic way.

-

That said, there will certainly be documents or projects where - it is a matter of scholarly significance that the compositor or - scribe chose to represent a given abstract character using one - particular glyph or set of strokes rather than a - semantically-equivalent but visually distinct alternative, and - in that case the specific appearance of the form will have to be - encoded in one way or another. But that encoding need not (and - in most cases will not) involve a notation that visually - resembles the original, any more than italicized text in an - original document will be represented by the use of italic - characters in the encoded version.

-

A collection of the abstract characters needed to represent - documents in a given writing system is known as a -character set, and the character set or - character repertoire of a processing or - rendering device is the set of abstract characters that it is - equipped to recognize and handle appropriately. There is, - however, a subtle distinction between these two parallel uses of - the same term, involving one more key concept which it is - essential to grasp. The character set of a document (or the - writing system in which it is recorded) is purely a collection - of abstract characters. But the character set of a computing - device is a set of abstract characters which have been mapped in - a well-defined way to a set of numbers or code points - by which the device represents - those abstract characters internally. It can therefore be - referred to as a coded character set, - meaning a set of abstract characters each of which has been - assigned a numerical code point (or in some instances a sequence - of code points) which unambiguously identifies the character - concerned.

-

It is now possible to use this terminology to - say what Unicode is: it is a coded character set, devised and - actively maintained by an international public body, where each - abstract character is identified by a unique name and assigned a - distinctive code point.Although only Unicode - is mentioned here explicitly, it should be noted that the - character repertoire and assigned code points of Unicode and - the ISO standard 10646 are identical and maintained in a way - that ensures this continues to be the case. Unicode is - distinguished from other coded character sets by its - (current and potential) size and scope; its built-in provision - for (in practical terms) limitless expansion; the range and - quality of linguistic and computational expertise on which it - draws; the stability, authority, and accessibility it derives - from its status as an international public standard; and, - perhaps most importantly, the fact that today it is implemented - by almost every provider of hardware and software platforms - worldwide.

-
- Abstract Characters, Glyphs, and Encoding Scheme - Design -

The distinction between abstract characters and glyphs can be - crucial when devising an encoding scheme. When performing - searches, text retrieval, or creating concordances, users of - electronic text will expect the system to recognize and treat - different glyphs as instances of the same character; but when - perusing the text itself they may well expect to see glyph variants - preserved and rendered. When encoding a pre-existing text, the - encoder should determine whether a particular - letter or symbol is a character or a glyphic variant. The Unicode - Consortium and an ISO work group (ISO/IEC JTC1 - SC2/WG2) have developed a detailed model of the relationship - between characters and glyphs. This model, presented in Unicode Technical - Report 17: Character Encoding Model, is the underpinning - of much standards work since, including the current chapter.

-

The model makes explicit the distinction between two different - properties of the components of written language: - - their content, i.e. its meaning and phonetic value - (represented by characters) their graphical - appearance (represented by glyphs). - -

-

When searching for information, a system generally operates - on the content aspects of characters, with little or no - attention to their appearance. A layout or formatting process, - on the other hand, must of necessity be concerned with the exact - appearance of characters. Of course, some operations - (hyphenation for example) require attention to both kinds of - feature, but in general the kind of text encoding described in - these Guidelines tends to focus on content rather than - appearance (see further ).

-

An encoder wishing to record information about which glyphs - are present in a given document may do so at either or both of - two levels: - - the level of character encoding, using an appropriate - Unicode code point to represent the glyph concerned - the markup level, with the glyph indicated via - appropriate elements or attributes -

-

The encoding practice adopted may be guided by, among other - things, an assessment of the most frequent uses to which the - encoded text will be put. For example, if recognition of - identical characters represented by a variety of glyphs is the - main priority, it may be advisable to represent the glyph - variations at markup level, so that the character value can be - immediately exposed to the indexing and retrieval software. - Plainly, an encoding project will need to consider such issues - carefully and document the outcome of their - deliberations in their TEI customization file (or other local - encoding documentation) to ensure encoding consistency. Using - Unicode code points to represent glyph information requires that - such choices be documented in the TEI header. Such documentation - cannot of itself guarantee proper display of the desired - glyph but at least makes the intention of the encoder - discoverable.

-

At present the Unicode Standard does not offer detailed - specifications for the encoding of glyph variations. These - Guidelines do give some recommendations; some discussion of - related matters is given in , - and offers some features for the definition of variant - glyphs.

-
-
- Entry of Characters -

The entry of characters was much more complicated before the near-universal - adoption of Unicode, for which there are Input Method Editors - (IMEs) available in most languages and fonts that provide glyphs for the full - range of the Unicode specification. In those rare situations where there is - difficulty entering the specific character you want, or some problem representing - it on the system you are working in, Numeric Character References - (NCRs) should be used. These take the general form &#D; where - D is an integer representing the code point of the character in - base 10, or &#xH;, where H is the code point in - hexadecimal notation. Every XML processor is capable of recognising NCRs and - replacing them with the required code point value without needing access to - any additional data. The disadvantage of NCRs as a means of entering, - representing and proofing character data is that most human beings find them - anything but readable and it is all too easy - for the wrong character to be entered in error and retained undetected. - Where characters are not defined in Unicode, these Guidelines provide advice - on the strategies available for handling their representation in Chapter 25 Representation of non-standard Characters and - Glyphs.

-
-
- Output of Characters -

The rendering of the encoded text is a complicated process that - depends largely on the purpose, external requirements, local - equipment and so forth, it is thus outside the scope of coverage - for these Guidelines.

-

It might however nevertheless be helpful to put some of the - terminology used for the rendering process in the context of the - discussion of this chapter. As was mentioned above, Unicode - encodes abstract characters, not specific glyphs. For any - process that makes characters visible, however, concrete, - specifically designed glyph shapes have to be used. For a printing - process, for example, these shapes - describe exactly at which point ink has to be put on the paper - and which areas have to be left blank. If we want to print a character - from the Latin script, besides the selection of - the overall glyph shape, this process also requires that a - specific weight of the font has been selected, a specific size - and to what degree the shape should be slanted. Beyond - individual characters, the overall typesetting process also - follows specific rules of how to calculate the distance between - characters, how much whitespace occurs between words, at which - points line breaks might occur and so forth.

-

If we concern ourselves only with the rendering process of the - characters themselves, leaving out all these other parameters, we - will realize that of all the information required for this process, only a small - amount will be drawn from the encoded text itself. This - information is the code point used to encode the character in the - document. With this information, the font selected for printing - will be queried to provide a glyph shape for this character. - Some modern font formats (e.g. OpenType) implement a - sophisticated mapping from a code point to the glyph selected, - which might take into account surrounding characters (to create - ligatures where necessary) and the language or even area this character is - printed for to accommodate different typesetting traditions and - differences in the usage of glyphs.

-

A TEI document might provide some of the information that is - required for this process, for example by identifying the - linguistic context with the xml:lang attribute. The - selection of fonts and sizes is usually done in a stylesheet, - while the actual layout of a page is determined by the - typesetting system used. Similarly, if a document is rendered - for publication on the Web, information of this kind can be - shipped with the document in a stylesheet.The World Wide - Web Consortium provides recommendations for two standard - stylesheet languages: either CSS or - XSL could be used for this purpose.

-
-
Unicode and - XML -

XML was designed with Unicode in mind as its means of representing - abstract characters. It is possible to use other character encoding - schemes, but in general they are best avoided, as you run the risk - of encountering compatibility issues with different XML processors, - as well as potential difficulties with rendering their output. We - recommend using the UTF-8 encoding, which for the Basic - Latin range is identical to ASCII, and which uses a variable-length - set of bytes to represent characters. It should be noted that it is - not sufficient simply to declare in the XML Declaration that a document - is in UTF-8 format. Doing so merely means that processors will treat the - content therein as if it were UTF-8, and may fail to process the - document if it is not. For further discussion of UTF-8, see the - section below on .

-
-
- Special Aspects of Unicode Character Definitions -
- Compatibility Characters -

The principles of Unicode are judiciously tempered with - pragmatism. This means, among other things, that the actual - repertoire of characters which the standard encodes, especially - those parts dating from its earlier days, include a number of - items which on a strict interpretation of the Unicode - Consortium's theoretical approach should not have been regarded - as abstract characters in their own right. Some of these - characters are grouped together into a - code-point regions assigned to compatibility characters. - Ligatures are a case in point. Ligatures (e.g. the joining of - adjacent lowercase letters s and t or f and i in Latin - scripts, whether produced by a scribal practice of not lifting - the pen between strokes or dictated by the aesthetics of a type - design) are representational features with no added semantic - value beyond that of the two letters they unite (though for - historians of typography their presence and form in a given - edition may be of scholarly significance). However, by the time - the Unicode standard was first being debated, it had become - common practice to include single glyphs representing the more - common ligatures in the repertoires of some typesetting devices - and high-end printers, and for the coded character sets built - into those devices to use a single code point for such glyphs, - even though they represent two distinct abstract characters. So - as to increase the acceptance of Unicode among the makers and - users of such devices, it was agreed that some such - pseudo-characters should be incorporated into the standard as compatibility characters. - Nevertheless, if a project requires the presence of such - ligatured forms to be encoded, this should normally be done via - markup, not by the use of a compatibility character. That way, - the presence of the ligature can still be identified (and, if - desired, rendered visually) where appropriate, but indexing and - retrieval software will treat the code points in the document as - a simple sequential occurrence of the two constituent characters - concerned and so correctly align their semantics with - non-ligatured equivalents. Such ligatures should not be confused - with digraphs (usually) indicating diphthongs, as in the French - word "cœur". A digraph is an atomic orthographic unit - representing an abstract character in its own right, not purely an amalgamation - of glyphs, and indexing and retrieval software will need to - treat it as such. Where a digraph occurs in a source text, it - should normally be encoded using the appropriate code point for - the single abstract character which it represents.

-
- Precomposed and Combining Characters and - Normalization -

The treatment of characters with - diacritical marks within Unicode shows a similar combination of - rigour and pragmatism. It is obvious enough that it would be - feasible to represent many characters with diacritical marks in - Latin and some other scripts by a sequence of code points, where - one code point designated the base character and the remainder - represented one or more diacritical marks that were to be - combined with the base character to produce an appropriate - glyphic rendering of the abstract character concerned. From its - earliest phase, the Unicode Consortium espoused this view in - theory but was prepared in practice to compromise by assigning - single code points to precomposed characters which were - already commonly assigned a single distinctive code point in - existing encoding schemes. This means, however, that for quite a - large number of commonly-occurring abstract characters, Unicode - has two different, but logically and semantically equivalent - encodings: a precomposed single code point, and a code point - sequence of a base character plus one or more combining - diacritics. Scripts more recently added to Unicode no longer - exhibit this code-point duplication (in current practice no new - precomposed characters are defined where the use of combining - characters is possible) but this does nothing to remove the - problem caused by the duplications from older character sets that - have been permanently embodied in Unicode. Together with essentially analogous - issues arising from the encoding of certain East Asian - ideographs. This duplication gives rise to the need to practice - normalization of Unicode documents. Normalization is - the process of ensuring that a given abstract character is represented in one - way only in a given Unicode document or document collection. - The Unicode Consortium provides four standard normalization - forms, of which the Normalization Form C (NFC) - seems to be most appropriate for text encoding projects. The NFC, as - far as possible, defines conversions for all base characters followed - by one or more combining characters into the corresponding precomposed - characters. The World Wide Web Consortium has produced a document entitled - Character Model for the World Wide Web 1.0Available at - ., which among other things - discusses normalization issues and outlines some relevant - principles. An authoritative reference is Unicode Standard Annex - #15 Unicode Normalization Formsavailable at - .

-

It is important that every Unicode-based project should agree - on, consistently implement, and fully document a comprehensive and - coherent normalization practice. As well as ensuring data integrity - within a given project, a consistently implemented and properly - documented normalization policy is essential for successful - document interchange. While different input methods may themselves differ - in what normalization form they use, any programming language that implements Unicode - will provide mechanisms for converting between normalization forms, so it - is easy in practice to ensure that all documents in a project are in a consistent form, - even if different methods are used to enter data.

-
-
- Character Semantics -

In addition to the Universal Character Set itself, the - Unicode Consortium maintains a database of additional character - semantics. This - includes names for each character code point and normative - properties for it. Character properties, as given in this - database, determine the semantics and thus the intended use of a - code point or character. The database also contains information that might be - needed for correctly processing this character for different - purposes. It is an important reference in determining which Unicode - code point to use to encode a certain character.

-

In addition to the printed documentation and lists made - available by the Unicode consortium, the information it contains - may also be accessed by a number of search systems over the Web - (e.g. ). Examples of - character properties included in the database include case, numeric - value, directionality, and, (where applicable) status as a - compatibility characterFor - further details, see The Unicode Character Property - Model (Unicode Technical Report #23), at .. Where a - project undertakes local definition of characters with code points - in the PUA, it is desirable that any relevant additional - information about the characters concerned should be recorded in an - analogous way, as further discussed under .

-
-
-
- Issues Arising from the Internal Representations of - Unicode -

In theory it should not be necessary for encoders to have any - knowledge of the various ways in which Unicode code points can - be represented internally within a document or in the memory of - a processing system, but experience shows that problems - frequently arise in this area because of mistaken practice or - defective software, and in order to recognize the resulting - symptoms and correct their causes an outline knowledge of - certain aspects of Unicode internal representation is desirable. - There are three encodings of Unicode available for use: UTF-8, which - uses 1–4 bytes per character, UTF-16, which uses 2–4, and UTF-32, - which uses 4 bytes per character. Current practice for documents to - be transmitted via the Web recommends only UTF-8.See the W3C - Internationalization document, Choosing & applying a - character encoding at - -

-
- Encoding Errors Related to UTF-8 -

The code points assigned by Unicode 3.0 and later are - notionally 32-bit integers, and the most straightforward way to - represent each such integer in computer storage would be to use - 4 eight-bit bytes. However, many of the code points for - characters most commonly used in Latin scripts can be - represented in one byte only and the vast majority of the - remainder which are in common use (including those assigned - from the most frequently used PUA range) can be expressed in - two bytes alone. This accounts for the use of UTF-8 and UTF-16 - and their special place in the XML standard. UTF-8 and UTF-16 - are ways of representing 32-bit code points in an economical - way.

UTF-8 is a variable length encoding: the more - significant bits there are in the underlying code point (or in - everyday terminology the bigger the number used to represent - the character), the more bytes UTF-8 uses to encode it. What - makes UTF-8 particularly attractive for representing Latin - scripts, explaining its status as the default encoding in XML - documents, is that all code points that can be expressed in - seven or fewer bits (the 127 values in the original ASCII - character set) are also encoded as the same seven or fewer bits - (and therefore in a single byte) in UTF-8. That is why a - document which is actually encoded in pure 7-bit ASCII can be - fed to an XML processor without alteration and without its - encoding being explicitly declared: the processor will regard - it as being in the UTF-8 representation of Unicode and be able - to handle it correctly on that basis.

-

However, even within the domain of Latin-based scripts, some - projects have documents which use characters from 8 bit - extensions to ASCII, e.g. those in the ISO-8859-n series of - encodings, and the way characters which under ISO-8859-n use - all eight bits are encoded in UTF-8 is significantly different, - giving rise to puzzling errors. Abstract characters that have a - single byte code point where the - highest bit is set (that is, they have a decimal numeric - representation between 129 and 255) are encoded in ISO-8859-n - as a single byte with the same value - as the code point. But in UTF-8 code-point values inside that - range are expressed as a two byte - sequence. That is to say, the abstract character in question is - no longer represented in the file or in memory by the same number - as its code-point value: it is transformed (hence the T in - UTF) into a sequence of two different numbers. Now as a - side-effect of the way such UTF-8 sequences are derived from - the underlying code-point value, many of the single-byte - eight-bit values employed in ISO-8859-n encodings are illegal - in UTF-8.

-

This complicated situation has a simple consequence which can - cause great bewilderment. XML processors will effortlessly - handle character data in pure 7-bit ASCII without that encoding - needing to be declared to the parser, and will similarly accept - documents encoded in an undeclared ISO-8859-n encoding if they - happen to use no characters outside the strict ASCII subset of - the ISO character sets; but the parse will immediately fail if - an eight-bit character from an ISO-8859-n set is encountered in - the input stream, unless the document's encoding has been - explicitly and correctly declared. Explicitly declaring the - encoding ought to solve the problem, and if the file is - correctly encoded throughout, it will do so. But projects dealing - with documents of sufficient age may find that they have to deal with some files encoded - in UTF-8 along with others in, say, ISO-8859-1. Such encoding - differences may go unnoticed, especially if the proportion of - characters where the internal encodings are distinguishable is - relatively small (for example in a long English text with a - smattering of French words). These types of error may or may not - manifest in actual processing errors, and may only become visible - as garbage characters in the eventual display of documents.

-

In projects that routinely handle documents in non-Latin - scripts, everyone is well aware of the need to ensure correct - and consistent encoding, so in such places mixed encoding - problems seldom arise, and when they do are readily identified - and remedied. Real confusion tends to arise, however, in - projects which have a low awareness of the issues because they - employ predominantly unaccented Latin characters, with only - thinly-distributed instances of accented letters, or other - special characters where the internal representation under - ISO-8859-n and UTF-8 are different (such as the copyright - symbol, or, a frequent troublemaker where eventual HTML output - is envisaged, the non-breaking space). Even, or especially, - if such projects view themselves as concerned only with - English documents, the close relationship between XML and - Unicode means they will need to acquire an understanding of - these encoding issues and develop procedures which assure - consistency and integrity of encoding and its correct - declaration, including the use of appropriate software for - transcoding and verification.

-
-
-
diff --git a/P5/Source/Guidelines/fr/CH-LanguagesCharacterSets.xml b/P5/Source/Guidelines/fr/CH-LanguagesCharacterSets.xml new file mode 120000 index 0000000000..4be9500eba --- /dev/null +++ b/P5/Source/Guidelines/fr/CH-LanguagesCharacterSets.xml @@ -0,0 +1 @@ +../en/CH-LanguagesCharacterSets.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/CO-CoreElements.xml b/P5/Source/Guidelines/fr/CO-CoreElements.xml deleted file mode 100644 index b4a7aebc95..0000000000 --- a/P5/Source/Guidelines/fr/CO-CoreElements.xml +++ /dev/null @@ -1,6013 +0,0 @@ - - - - -
-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 , 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 ) 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 ) and features commonly marked by quotation marks -(section ) as well as such features as terms, -cited words, and glosses (section ).

- -

Section 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 ), -which should be adequate to most commonly encountered situations.

- -

The next section (section ) 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 ), numbers and measures (section ), dates and times (section ), abbreviations (section ), and addresses (section ).

- -

In the same way, the following section (section ) 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 ; the tags presented here -are intended to be usable for a wide variety of simple -applications.

- -

Sections , and , 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 ) is discussed.

-

Section 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 and .

-

Next, section , 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 , 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 .

-

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 , describing the structure of -the TEI document type definition.

-
Paragraphs -

Paragraphs in modern printed or online text are typically visually - offset with whitespace or an indented first line. But paragraphs are - not simply blocks of text. The paragraph may be thought of as a mid-level - unit of sense, a coherent grouping of sentences. Paragraphs may, in turn, - be grouped into larger divisions, such as chapters. Because it is a unit - of sense rather than simply a block of text, the p element in TEI - may contain other structures displayed as blocks, such as lists or quotes. - This distinguishes it from the p - element in HTML, which is primarily a block of text, and from the ab - (anonymous block) element described in which may be used - as an alternative to the paragraph in cases that require a chunk-level container - which is not necessarily a sense unit and which may have different structural properties.

-

The paragraph can be understood in the context of the distinct forms of textual - division discussed in : chunk, - phrase, and inter-level. - Chunk-level elements are paragraphs and other elements which have similar - structural properties. Phrase-level elements must be entirely contained within a - paragraph or other chunk-level structure. This type includes emphasized or quoted - phrases, names, dates, etc. Inter-level elements can appear either within a - paragraph or between paragraphs, and include bibliographic citations, notes, and - lists. The ab (anonymous block) element is an alternative to - p which is useful in cases where paragraphs are not present, but chunk-level - organization is still needed. ab may contain other abs, - may use the type attribute, and does not necessarily represent a coherent set of - statements.

-

Paragraphs can contain many of the other elements described within this chapter, - as well as other elements which are specific to individual text types. Because - paragraphs may appear in different customizations, their possible - contents may vary in different kinds of documents. In particular, additional - elements not listed in this chapter may appear in paragraphs. However, - the elements described in this chapter are available - in all kinds of text unless they are excluded by a customization.

-

The paragraph is marked using the p element: -

-

If a consistent internal subdivision of paragraphs is desired, the -s or seg (segment) elements may -be used, as discussed in chapters and -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.

-

The following example demonstrates a basic application of the p tag for an indented passage in a printed book: - -

It is in vain to say human beings ought to be satisfied with tranquillity: - they must have action; and they will make it if they cannot find it. Millions are - condemned to a stiller doom than mine, and millions are in silent revolt against - their lot. Nobody knows how many rebellions besides political rebellions ferment - in the masses of life which people earth. Women are supposed to be very calm - generally: but women feel just as men feel; they need exercise for their faculties, - and a field for their efforts, as much as their brothers do; they suffer from - too rigid a restraint, too absolute a stagnation, precisely as men would suffer; and - it is narrow-minded in their more privileged fellow-creatures to say that they ought to - confine themselves to making puddings and knitting stockings, to playing on the piano - and embroidering bags. It is thoughtless to condemn them, or laugh at them, if they - seek to do more or learn more than custom has pronounced necessary for their sex.

- -

-

This news story shows typically short journalistic paragraphs: -SARAJEVO, Bosnia and Herzegovina, April 19

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.

-

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.

-

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.

-

...

-

-

The following extract from a Russian fairy tale demonstrates -how other phrase level elements (in this case q elements -representing direct speech; see section ) -may be nested within, but not across, paragraphs: -

A fly built a castle, a tall and mighty castle. -There came to the castle the Crawling Louse. Who, -who's in the castle? Who, who's in your house? -said the Crawling Louse. I, I, the Languishing Fly. -And who art thou?I'm the Crawling Louse. -

-

Then came to the castle the Leaping Flea. Who, -who's in the castle? said the Leaping Flea. I, -I, the Languishing Fly, and I, the Crawling Louse. And -who art thou?I'm the Leaping Flea. -

-

Then came to the castle the Mischievous Mosquito. -Who, who's in the castle? said the Mischievous -Mosquito. I, I, the Languishing Fly, and I, the -Crawling Louse, and I, the Leaping Flea. And who art -thou?I'm the Mischievous Mosquito. -

-

- - - - - -
-
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 -. Where the character used for a punctuation mark -is not available in Unicode, the g element and other facilities described in -chapter may also be used to mark its presence.

- -
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 , , -and 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 . -

-

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 , and section , - 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 .

- -

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 . -

-

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. -

- -
- -
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: 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 ). - tea-pot - - -A similar range of possibilities applies equally to the representation of -other common punctuation marks, notably quotation marks, as discussed -in .

- -

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 , or the more sophisticated mechanisms for -linguistic analysis discussed in chapter . -

-
-
- - -
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. -

-
What Is Highlighting? -

By highlighting we mean the use of any -combination ofhighlighting typographic -features (font, size, hue, etc.) in a printed or written text in order -to distinguish some passage of a text from its surroundings.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 -. 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 ). 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. - - - -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 (). 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 . -

- -

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 ) and name (discussed -in section ). -

-
Emphasis, Foreign Words, and Unusual Language -

This subsection discusses the following elements: - -These elements are all members of the model.emphLike class.

-
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 and 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. -Aren't you confusing post hoc with propter -hoc? said the Bee Master. Wax-moth only succeed when -weak bees let them in. -

- -

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 below. Compare the -following example sentences: -John eats a croissant every morning. -Croissant is difficult to -pronounce with your mouth full. -A croissant 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

- - - - -
-
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: Sex, sir, is purely a question -of appetite! 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: What it all comes to is this, he said. -What does Christopher Robin do in the morning -nowadays? 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: What it all comes to is this, he said. -What does Christopher Robin do in -the morning nowadays? -

-

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: -Here Thou, great Anna! - whom three Realms obey, -Doth sometimes Counsel take — - and sometimes Tea. - -font-style: italic - -Further information on the use of the rendition element is -provided at .

- - -

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: -And this Indenture further witnesseth -that the said Walter Shandy, 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 came down handsomely, and Scrooge never -did. In this example, the phrase came -down uses inverted commas to indicate a play on -words.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. - -In a second pass, the element soCalled might be preferred as -a means of indicating that the narrator is distancing himself from -this usage. -

- - - - -
-
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,diachronic information -for example as archaic, old-fashioned, contemporary, futuristic, etc.; -the space attribute places a word or phrase -diatopically,diatopic information -that is, with respect to a geographical classification, for example as -national, regional, international, etc.; the social attribute -places a word or phrase diastratically,diastratic information -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 ). -

-

Examples: -Next morning a boy in that dormitory confided to his -bosom friend, a fag of -Macrea's, that there was trouble in their midst which -King would fain keep -secret. - -Next morning a boy in that dormitory confided to his -bosom friend, a -fag -of Macrea's, that there was trouble in their midst which -King would fain 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 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 , or the -span element described in section . -

- - - -
-
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: - - - - - - - - - -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 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 ). 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 : - — Alors, Albert, quoi de neuf? - — Pas grand-chose. - — Il fait beau, 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 : - Alors, - Albert, quoi de neuf ? - Pas grand-chose. - Il fait beau, - dit Robert. - -content: '— ' - - -

- -

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 ) 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: - - Who-e debel - you? — he at last said — - you no speak-e, - damme, I kill-e. 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 . 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: - - -Who-e debel - you? — he at last said — - you no speak-e, - damme, I kill-e. And so saying, - the lighted tomahawk began flourishing - about me in the dark. - - - content:"‘"; - content:"’"; - - -

- - - -

As members of the att.ascribed.directed class, - elements said and q share the following attributes: - -These may be used to make explicit who is speaking and who is being spoken to: - Adolphe se tourna vers lui : - — Alors, Albert, quoi de neuf? - — Pas grand-chose. - — Il fait beau, dit Robert. - - - - Adolphe - Albert - Robert - - - - - 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 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: - Oh yes, said Henry, I mean - Gordon Macrae, for example… Jungian - Analyst with Winebox! That's what you called him, you callous bastard, - didn't you? Eh? Eh? -

-

Quoted matter may be embedded within quoted matter, as when one - speaker reports the speech of another: - Spaulding, he came down into the office just this day - eight weeks with this very paper in his hand, and he says:— - I wish to the Lord, Mr. Wilson, that I was a - red-headed man. - - - Wilson - Spaulding reported by Wilson - - -

-

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: -

The Lord! The Lord! It is Sakya Muni himself, the lama half - sobbed; and under his breath began the wonderful Buddhist - invocation:- - - To Him the Way — the Law — Apart — - Whom Maya held beneath her heart - Ananda's Lord — the Bodhisat - - And He is here! The Most Excellent Law is here also. My - pilgrimage is well begun. And what work! What work! -

-

-

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 , as in the following example. -

- Chapter 1 - - - Since I can do no good because a woman - Reach constantly at something that is near it. - - - The Maid's Tragedy - Beaumont and Fletcher - - -

Miss Brooke had that kind of beauty which seems to be thrown into - relief by poor dress...

-
- 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, - You shall know a word by the company it keeps. - (Firth, 1957) - - - 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: - - Tolkien (1936) tells us that -Beowulf is in fact so interesting as -poetry, in places poetry so powerful, that this quite -overshadows the historical content. - - 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 .

-

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: - PM dodges election threat in interview -

-

The same element should be used to mark a variety of special ironic - usages. Some further examples follow: - He hated good books. - Croissants 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 - social justification. It was commonly assumed in - works on logic until fairly recently that the notion - language is necessarily restricted to finite - strings. -

- - - - - - - - -
- -
-
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.

- -
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 (formentionvs. useusevs. mention - example, as examples) rather than used may - mark them either with italics or with quotation marks, and will gloss - them less regularly. - - - - 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 discoursal point of view - as the relationship, expressed through discourse - structure, between the implied author or some other addresser, - and the fiction. - - A computational device that infers - structure from grammatical strings of words is known as a - parser, 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 discoursal point of view 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 .

-

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 eluthemen - we were released, accented on the - second syllable of the word, and its participial derivative - lutheis released, 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 below are available on the - term element for this purpose. -

- - - - - - -
Some Further Examples -

As a simple example of the elements discussed here and in - , 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 Nibelungenlied is - associated with the new rise of romance of twelfth-century France, - the romans d'antiquité, - 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 Nibelungenlied - is associated with the new rise of romance of twelfth-century France, - the romans d'antiquité, 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 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. - - - - - - - -

-
- - -
- 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. -
- -

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 (). 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: - - - - - - 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: - - - - 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: - -

- - - 大学 - だいがく - - -

- - - 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: - -

- - - 大 - だい - - - 学 - がく - - -

- - - Here is a similar example from Taiwan using bopomofo (pinyin - píngzi = bottle)Taken from Wikipedia.: - -

- - - 瓶 - ㄆㄧㄥˊ - - - 子 - ˙ㄗ - - -

- - - - 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 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. - -

- - Billiard hall 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: - - -

- - - - - 打 - ダ - - - 球 - キウ - - 場 - - ビリヤード - - -

- - - We could also use a standoff approach with anchor elements and - pointers: - - -

- - - - 打 - 球 - 場 - - - ビリヤード - ダ - キウ - - -

- - - Alternatively, if the encoding itself already includes segmentation below - the word level, we can use the existing elements instead of adding anchors: - - -

- - - 打球場 - ビリヤード - ダ - キウ - - -

- - - Multiple ruby annotations can appear in the same alignment relative to the main text. For example, there might be two annotations on the right. We use this - instance to exemplify two ways of encoding this phenomenon, dependent on the interpretation of the text. - We could use a parallel approach where a sequence of two rt elements, both with the same value for the place attribute, are - assumed to appear in their document sequence. The first of the two rt elements would appear to the right of the ruby base (rb), while the second would appear to the right of the first rt element - Taken from Wikipedia.: - - -

- - - ㄅ - B - 博 - - -

- - - Alternatively, a nested approach can be used. With nested ruby elements, the structure suggests that the second rt element is glossing both the rb and the rt element: - - -

- - - - - ㄅ - B - - - 博 - - -

- - -

- - - -

The rt element is a member of att.written: - - - - - so the hand attribute can be used where the ruby - text constitutes an annotation in a - different hand from the ruby base: - -

- - Base text with a ruby gloss in a different hand. - リクシ ソウモク チョウジュウ チュウギョ ソ ズカイ。 東京大学総合図書館 (General Library in the University of Tokyo, JAPAN). -
- - -

- - - 蘝蔓 - ヤブカラシ - - 于野 - -

- - -

- -

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. While ruby is included for use with East Asian languages, - encoders may find other contexts in which these elements are useful.

- - - - - - -
- -
- 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. - - - - - - Along with the gloss element mentioned above, these elements - constitute the model.identSynonyms class. - They are described in more detail in .

-
- -
- -
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 . -Systematic interpretive annotation is also possible using the various -methods described in chapter . 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 should be used. To encode multiple -witnesses of a particular text, a similar mechanism designed -specifically for critical editions is described in chapter .

- -

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: - - - - - -

- -

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: - - - -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 .

-
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. - - - - -

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 dates -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 date's -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 - - dates - date's - 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 - - dates - date's - mentioned in the main body of the text are - incorrect. - - -editor -C.M. Sperberg-McQueen - -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 ; 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 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 AutumnAntony it was, -That grew the more by reaping -See further the discussion in section .

-

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 -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 . -

- - - - - -
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.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.

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: - - - - -

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: -

...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

Alternatively, the encoder may simply indicate that certain words -have been modernized by using the reg element with no -attributes specified, as follows:

...how godly a -deed it is to overthrow so wicked a race the -world may judge: for my part I think -there cannot be a greater -sacrifice to God.

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: -

...how godly a dededeed it is to -overthroweoverthrow so wicked a race the -world may judge: for my part I thinkethink -there canotcannot be a greater -sacryficesacrifice to God.

-

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

- - - - -
-
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: - - - - - - -

-

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 ). In these situations — where copy text -is not transcribed due to editorial policy or because it is impossible -to do so — the gap element may be used to indicate the -omission. Attributes on the gap element optionally provide -further information about the reason for the omission, its extent, and -the person or agency responsible for it, as in the following examples: - - -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 .

-

The desc element may be used to supply a description of -the material omitted, where that is considered useful: - irrelevant commentary -… Their arrangement with respect to Jupiter and to each other was as follows: -astrological figure -That is, there were two stars on the easterly side and one to the -west; … - - - - -

- -

The ellipsis element provides a means to encode the - deliberate, marked omission of content in a source document. Within - ellipsis, a required metamark is used to represent - the characters or markings in the source that indicate the presence - of omitted material. Encoders may optionally provide a desc - element to describe the omission, as well as a supplied - element to record the content omitted from the source at this point. - The ellipsis element could be applied to ditto marks - when they indicate repetition of the same content, as in this - example: - - - - Tent supplies - - - nylon tent - - - 1 - - - - - steel stakes - - - 6 - - - - - fiberglass poles - - - - " - 6 - - - -
- -

- -

The ellipsis element may also apply to literary passages - that omit the full names of places or people, leaving their - identities to the imagination of the reader, as in the next example. - -

I leave Dublin to-morrow for M—— house. It is situated in the county of ——, on the north-west coast of Connaught, which I am told is the classic ground of Ireland.

- -

-

A manuscript of song lyrics provides a more complex example of ellipsis to encode a marked omission that begins in the middle of a verse line. -

- - A manuscript from Cancioneiro da Biblioteca Nacional - [1525-1526] in Biblioteca Nacional de Portugal, representing - song lyrics and the beginning of a chorus. On the last line - visible in this image, a marking of three dots and a line, - ·:—, indicates that the rest of the chorus should follow - after this point. -
- Our encoding of the passage shows the use of ellipsis with supplied to contain the omitted content. - - - Amıgas sey eu ben dunha molher - Que se trabalha de uosco buscar - Mal a uossamigo polo matar - Mays todaquestamiga ela quer - ꜒ - Por que nunca con el pode poer - Queo podesse por amigauer - - - E buscalhi con uosco quanto mal - Ela mays pode aquesto sei eu - E todaquestela faz polo seu - E poreste pẏte non por al - ꜒ - Por que nunca - - ·:— - - con el pode poer - Queo podesse por amigauer - - - - -

-

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 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),additionssupralinearinsertionssupralinearsupralinear insertions 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 of -these facts 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 , and in section -, 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: -And where the sandy mountain Fenwick scald -The sea between -yet hence his pray'r prevail'd -or from a spoken text: -

... and then marbled queen...

-

-

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: -One day I will sojourn to your shores -I live in the middle of England -But! -Norway! My soul resides in your watery -fiords fyords fiiords -Inlets. -

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: -Mein Frisch -schwebt weht der Wind

-

Deletion in manuscript or typescript is often associated with -addition: -Inviolable - Inexplicable -splendour of Corinthian white and gold -The subst element discussed in 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 ) rather than add and -del. These two sets of elements allow the encoder to -distinguish editorial changes from those visible in the source text. -

- - - - - - - - - -
-
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 ); more detailed -treatment of abbreviations is provided by the transcription module -(see section ).

- -
Referring Strings -

A referring string is a phrase which refers to some -person, place, object, etc. Two elements are provided to mark such -strings: - - - - -Both the name and rs elements are members of the -att.typed class, from which they inherit -the following attributes: which may be used to further -categorize the kind of object referred to.

- -

Examples include: - -

My dear -Mr. Bennet, said his lady to -him one day, have you heard that -Netherfield Park is let at last?

-

Collectors of water-rents were appointed by the -Watering Committee. -They were paid a commission not exceeding four per -cent, and gave bond.

 -

It being one of the principles of the -Circumlocution Office never, on any -account whatsoever, to give a straightforward answer, -Mr Barnacle said, Possibly.

 -

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. -

My dear Mr. Bennet, said -his lady to him one day ...

-

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: -

My dear Mr. Bennet, said his lady to him one day, -have you heard that Netherfield Park is let at last?

-As the following example shows, a proper name may be nested within a -referring string: -His Excellency the Life President, Ngwazi Dr H. Kamuzu Banda -

-

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 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: -

- -

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: - - My dear - Mr. Bennet, said - his lady to him one day, - have you heard that - Netherfield Park is let at -last? - - -

Mme. de Volanges - marie sa fille: - c'est encore un secret; -mais elle m'en a fait part hier.

-

- -

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. - - -

Heathrow

-

- -

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. - - -

Heathrow

-

-

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:

My personal life during -the administration of Col. Polk -(Polk, James K.) has but poorly compensated me for the -suspended enjoyments and pursuits of private and professional -spheres

-

- -

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: - -

Mme. de Volanges marie sa fille: c'est encore un secret; -mais elle m'en a fait part hier.

- -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 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: - -

-Walter de la Mare -de la Mare, Walter - -was born at Charlton, in -Kent, in 1873.

-

The index element discussed in may be -more appropriate if the function of the regularization is to provide a -consistent index: -

Montaillou is not a large parish. -At the time of the events which led to -FournierBenedict XII, Pope of Avignon (Jacques Fournier)'s -investigations, the local population consisted of between 200 and 250 inhabitants.

-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 or the -analytical tools described in chapter should be -used. -

- - - - - -
-
Addresses - -

These Guidelines propose the following elements to distinguish -postal and electronic addresses: - - - - -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. - - -info@tei-c.org - -

- -

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: - -Here is an example of a postal address encoded using this approach: -

- 110 Southmoor Road, - Oxford OX2 6RB, - UK -
-

-

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: - - - - 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: - -

- 110 Southmoor Road - Oxford - OX2 6RB - United Kingdom -
-

- -

The order of elements within an address is highly culture-specific, -and is therefore unconstrained: -

- Università di Bologna - Italy - 40126 - Bologna - via Marsala 24 -
-

- -

A telephone number (normally outside of the address - element) might be tagged with an addrLine and ref - that points to the phone number using the tel URI - scheme: - - (201) 555 0123 -

- -

For further discussion of ways of regularizing the names of places, -see section . 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 , 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: -

- 110 Southmoor Road - Oxford - OX2 6RB - United Kingdom -
-

- - - - - - - -
-
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: - -

- -

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: - xxxiii -twenty-one -ten percent -10% -5th - one half -1/2 -

- -

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: - - - -

- -

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: - -

-Unimportant -Small and round -Green -White -yellow -Mobile -13¾" -11" - - - -
- -In the same way, it may be convenient to mark -representations of currency which might otherwise be misinterpreted as -lexical: - -

...the sum of -12s 6d...

 -

-

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: - - - -With these attributes, the measurement of Celia's neck may be -specified in a normalized form: - -13¾" - -Such techniques are particularly useful when representing historical -data such as inventories: - - - ii bags hops - - six trusses Woolen and linen goods - - 5 tonnes coale - - -

-

In addition to normalization, the attributes of the att.ranging class may be used to supply the mininum or maximum values - of a range, or of an approximate measurement: - - - -

In a cadaver I have found it - holding more than three ounces. - [...] Then - we may suppose in man that a single heart beat - would force out either - a half ounce, three drams, - or even one dram of blood, which because of the - valvular block could not flow back that way into - the heart.

- -

-

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: - - -xiv -v -x - - - -

-

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. - - - - - - -A measure element may contain a combination of num and unit elements: - - 1, 2, 5, 7 - millimètres - -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: - -

Light travels at 3×10^10 - - cm per second - .

- -

- - - - - - -
-
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: - - - - -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: - - - - -

-

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 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 . 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: - 12/2/1980 - Given on the 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. -

-

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.The datatypes are taken from the W3C Recommendation XML Schema Part 2: Datatypes Second Edition. -The permitted datatypes are: - -date -gYear -gMonth -gDay -gYearMonth -gMonthDay -time -dateTime - -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. -Some typical examples follow: - -The year 2001 -September 2001 -11 Sep 01 -9/11 -September -Eleventh of the month - -Sept 11th, 12 minutes before 9 am -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:

Those five years — -1918 to 1923 -— had been, he suspected, -somehow very important.

- -

The Eddic poems are preserved in a unique -manuscript (Codex Regius 2365) from -the second half of the -thirteenth century, and Hervarar -saga dates from around 1300.

 -

-

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.

- - - - - - -
-
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: - - - - -

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 CC is defined by that calibration of values which -motivates the elements of its GSP; ... -Every manufacturer of 3GL or 4GL -languages is currently nailing on OOP extensions. -

The type attribute may be used to distinguish types - of abbreviation by their function:Dr. M. Deegan is -the Director of the CTI Centre for Textual Studies. -

-

Abbreviations such as Dr. M. above may be - treated as two abbreviations, as above, or as one: Dr. M. Deegan is -the Director of the CTI 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 -World Wide Web Consortium -W3C -Nested abbreviations may also be handled in this way: - RELAX NGregular -language for XMLextensible markup -language, next -generation

- -

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 , which includes -additional elements made available for the purpose by the transcr module.

- - - - - -
-
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: - - - -Linkages of several other kinds are also provided for in these -guidelines; see further chapter . -

-

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: -

... -The complete XPointer specification is managed by the W3C, -, -, and -; -for a discussion of TEI schemes for XPointer, see -.

- -
- -
- -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 . The complete XPointer specification is managed by the W3C, , , and ; for a discussion of -TEI schemes for XPointer, see .

-

- -

-

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: - - - - -

-

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 section 12 on page 34. -

-

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 - - -then the same cross-reference might more exactly be encoded as - See especially section 12 on page 34. -

-

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 . -

-

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 (); 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: - - Saints aid rejected in mel. - Sallets censured - Sanguine mel. signs - Scilla or sea onyon, a purger of mel. - -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: - - -... - -... - -... - -... - -... - -

-

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 ⁵¹ - -text of annotation - -

-

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 -rewriting systems, have a long history -among mathematicians, but the specific form of -was first studied extensively by Chomsky . - -

- - - -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 , , and , 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: - -

The current version of the TEI Guidelines source code - is available in the TEI GitHub Repository; guidelines-en.xml - is the root document used to create the English version - of these Guidelines.

- -

- - - - -
-
Lists -

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

-

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. - - - My first rough manuscript, without any -intermediate copy, has been sent to the press. - - 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. - -I will add two facts, which have seldom occurred in -the composition of six, or even five quartos. - - My first rough manuscript, without any -intermediate copy, has been sent to the press. - 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. - -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 - those that belong to the Emperor, - embalmed ones, - those that are trained, - suckling pigs, - mermaids, - fabulous ones, - stray dogs, - those that are included in this classification, - those that tremble as if they were mad, - innumerable ones, - those drawn with a very fine camel's-hair brush, - others, - those that have just broken a flower vase, - those that resemble flies from a distance. - -

-

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: - - Report of the conduct and progress of Ernest Pontifex. - Upper Vth form — half term ending Midsummer 1851 - Idle listless and unimproving - ditto - ditto - Orderly - - Not satisfactory, on account of his great - unpunctuality and inattention to duties - -

-

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, -tablesand -lists on which see chapter . 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: - - Unit Three — Vocabulary - bitter, harsh - field - hear, listen (to) - war - good - -Additionally, the term and gloss elements discussed -in section might be used to make explicit the role -that each column in the glossary list has, as follows: - - Unit Three — Vocabulary - - bitter, harsh - - field - - hear, listen (to) - - war - - good - -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 , and -section . 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 . -

-

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. - - TRITE - SIMPLE, STRAIGHTFORWARD - stop fighting, make peace - disorganized - friendly - completely honest - near death - -

-

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: - - - - - I am cast upon a horrible desolate island, void - of all hope of recovery. - I am singled out and separated as it were from - all the world to be miserable. - I am divided from mankind — a solitaire; one - banished from human society. - - - - - - But I am alive; and not drowned, as all my - ship's company were. - But I am singled out, too, from all the ship's - crew, to be spared from death... - But I am not starved, and perishing on a barren place, - affording no sustenances.... - - - -

-

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

- - - - - - - - -
-
Notes, Annotation, and Indexing -
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: - -

-

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 .

-

In the following example, the type attribute is used to -categorise the note as a gloss: -The self-same moment I could pray -And from my neck so free -The albatross fell off, and sank -Like lead into the sea. -The spell begins to break - -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: -The self-same moment I could pray -And from my neck so free -The albatross fell off, and sank -Like lead into the sea. -The spell begins to break - -

-

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: -The self-same moment I could pray -And from my neck so free -The albatross fell off, and sank -Like lead into the sea. - -

-

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.We -explain below why we use the uncommon term -collection instead of the expected -set. Our usage corresponds to the -aggregate of many mathematical writings and to -the sense of class found in older logical -writings. 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: - - -The self-same moment I could pray; - -The spell begins to break -The turning point of the poem... - - -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 ; thus in this -case, the TEI header for this text might contain a -title statement like the following: - - -The Rime of the Ancient Mariner: an annotated edition -Samuel Taylor Coleridge -John Livingston Lowes - -

- -

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 -). -

- -
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. - -

... reuerendos dominos archiepiscopum et canonicos Leopolienses - in duplicibus Quatuortemporibus - - Quatuor Tempora, so called dry fast days. - 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). - - - totaliter expediui. -

- -

-
-
-
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. -

-
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: -

- - -Women, how cause of mel. 193; their vanity in -apparell taxed, 527; their counterfeit tears -547; their vices 601, commended, -624. -Wormwood, good against mel. 443 -World taxed, 181 -Writers of the cure of mel. 295 - - -
-

-

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: -Women, - how cause of mel. 193; - their vanity in apparell taxed, 527; - their counterfeit tears 547; - their vices - 601, - commended, 624. - - - -

-

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 pb element: - - - -624 - - -For further discussion of this and alternative ways of encoding such -links see the discussion in section . Note that -similar methods may also be used to encode a table of contents, as -further exemplified in section . -

-
-
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: - - - -

-

Like the interp element described in -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): -]]> -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: -

The students understand procedures for Arabic lemmatisation - - Lemmatization, Arabic -and are beginning to build parsers.

-

-

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 -) at the appropriate point and pointing to it from -the index element by means of its spanTo -attribute, as -in this example: -

We now turn to the -topic of Arabic lemmatisation - - Lemmatization, Arabic - concerning which it is important to note [...] - -and now we can build our parser.

-

-

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: -

The @ operator -@ precedes an -attribute name

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 . In -the following example, we assume that somewhere a definition for this -glyph has been provided using the elements described in chapter , and given the code PrinceGlyph: - - - - - -

The Artist formerly known as Prince ...

 -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: -

Sir John Ashford -Ashford, John was, -coincidentally, born in -Ashford -(Kent)Ashford...

- -

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: -

The students understand procedures for Arabic lemmatisation - - lemmatization - - arabic - - -...

-

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 - - - Women - - how cause of mel. - - -. Similarly, page 601 of the body text would include -an index element like the following: - - Women - - their vices - - -while the index element at page 624 would have a structure -like the following: - - Women - - their vices - - commended - - - -

-

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. - - -

- Bibliography - - ... - -
- - - -

-

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. - - - - An Index of Names - - - -

-

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.

- - - - - -
-
-
-
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: - - - - - - -

-

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 - 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: - - - -

- -

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: -

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: - -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 -...

- - -

-

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: - -.

-

The figure element discussed in -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.

- - - - - - - -
-
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 . - -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 . - -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 -. - -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 . - -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 and in section . -

-

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.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.

-
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 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: - - - - - - - - ... - ... - - ... - - - - - -

-

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: - - - - - - - - ... - - - - - - -

-

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: - - - - - - ... - - - - - - -

-

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 . -

-

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 . -

-
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 - . -

- -

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

- -
- 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. - - -

-

...

-
- - ... - -
-

...

-
- - -

...

-

...

-
- ... -

...

-

...

-
-
- ... -

...

-

...

-
- - - 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 . -

-
- -
- 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: - - 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. - 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. - 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. - 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.

-
- -
-
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 ), 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: -

-

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: - - -

- - -

- - -

- -

- - - -An encoding of the same work in which parts are regarded as more -important than chapters might begin as follows: - - - - -

- -

- -

- - -

- -

- - - -

-

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: - - Oh what is this I cannot see - With icy hands gets a hold on me - Oh I am Death, none can excel - I open the doors of heaven and hell - -

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: - - - - - - - - - -

-

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: - - - - - -or - - - - - -

-

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 - may be used, for example to specify that the -attribute must specify one of a predefined set of values. -

-

See below, section , 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 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 imperator 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 imperator 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 .

- - - - - - - -
-
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 -. 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 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: - - - -

A canonical reference is assembled with - - the name of the : the - n of a div1, - a space, - the number of the : the - n of a child div2, - a full stop - the number of the : the - n of a child div3, - the line number: the n value of a - child l - -

- - -

Same as above, but without the last component (full - stop followed by the l's n.

- - -

Same as above, but without the poem component (full - stop followed by the div3's n.

- - - - -

-

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: - - -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: - - - - -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: - - - -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: - - - - - - - - - - -

-

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: - - - - - - - - - - - - - - - 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 . - -

Standard references to work, book, poem, and line may be - constructed from the milestone tags in the text.

- -Or in this way, using a formal declaration for this reference scheme -derived from edition E1. - - - - - - -

-
-
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 ; 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. - - - -Lists of such elements may also be encoded using the following element: - - -

- -

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,For example, to distinguish -London as an author's name from -London as a place of publication or as a -component of a title. 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.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 . The features distinguished and -described below (in section ) 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 ; for a brief mention of related library -standards see section . -

- -

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. -

- - - -
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 -; for the biblFull element, the -sub-elements concerned are fully described in section . -

-

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: -

A book which had a great influence on him -was Tufte's Envisioning -Information, although he may -never have actually read it.

-Indeed, some encoders may find it unnecessary to mark the bibliographic -reference at all: -

A book which had a great influence on him -was Tufte's Envisioning Information, -although he may never have actually read it.

 -

-

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 Baxter, 1983. -In general, however, normal modern bibliographic practice, and these -Guidelines, distinguish between a bibliographic reference,referencesbibliographicbibliographic references -which is a self-sufficient description of a bibliographic item, and a -bibliographic pointer,bibliographic pointerspointersbibliographic -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 -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. - - - - - Edward - R. - Tufte - - 6506403994 - https://id.loc.gov/authorities/names/n50012763.html - - Envisioning Information - - Cheshire, Conn. - Graphics Press - - - - -

-

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 -); 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: - - - Envisioning Information - Tufte, Edward R[olf] - - 126 pp. - - Graphics Press - Cheshire, Conn. USA - 1990 - - -

-

A list of bibliographic items, of whatever kind, may be treated in -the same way as any other list (see section ). -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: - - - Bibliography - - - - - Nelson - Theodore - Holm - - - Replacing the printed word: - a complete literary system - - - Information Processing '80: Proceedings of the IFIPS - Congress, October 1980 - - - Simon - H. - Lavington - - - - North-Holland - Amsterdam - - - 1013–23 - - Apparently a draft of section 4 of - Literary Machines. - - - Ted -Nelson: -Literary Machines (privately published, -1987). - - Baxter, -Glen: -Glen Baxter His Life: the years of struggle -London: Thames and Hudson, -1988. - - - 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: - - - - Bibliography - - - Nelson, T. H. - Replacing the printed word: - a complete literary system. - Information Processing '80: - Proceedings of the IFIPS Congress, October 1980. - Simon H. Lavington - North-Holland: - Amsterdam, - 1980. - pp 1013–23 - - Apparently a draft of section 4 of - Literary Machines. - - - - Ted Nelson: Literary Machines - (privately published, 1987) - - - - Baxter, Glen - Glen Baxter His Life: the years of struggle - London: Thames and Hudson, 1988. - - - -

-
-
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 ). -

-
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: - -the analytic level, giving the title, author, etc., of the article; - -the monographic -level, giving the title, editor, etc., of the collection; - -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: - - - Beaupaire - (Edmond), - A propos de la rue de la Femme-sans-Tête, - - La Cité, - janvier 1911, pp. 5-17. - - - -

- -

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

- -

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: - - -Albert Schachter -Iolaos - - -Herakles to Poseidon -1986 -64-70 - - -Cults of Boiotia -London -4 vols. -2 - - -Bulletin of the Institute of Classical Studies -Supplements -38 - - - -

- -

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. - - - - Thaller - Manfred - A Draft Proposal for a Standard for the - Coding of Machine Readable Sources - - - - Historical Social Research - - October 1986 - - 40 - 3-46 - - Modelling Historical Data: - Towards a Standard for Encoding and - Exchanging Machine-Readable Texts - DanielI. - Greenstein - - St. Katharinen - Max-Planck-Institut für Geschichte - In Kommission bei - Scripta Mercaturae Verlag - - - - - Halbgraue Reihe - zur Historischen Fachinformatik - - Herausgegeben von - Manfred Thaller - Max-Planck-Institut für Geschichte - - Serie A: Historische Quellenkunden - 11 - - -

- - -

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 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.

- - - - - -James -H. -Coombs - - -Allen -Renear - - -Steven -J. -DeRose - -Markup Systems and The Future of Scholarly Text -Processing -10.1145/32206.32209 -http://xml.coverpages.org/coombs.html - - -Communications of the ACM -1987 -30 -11 -933–947 - - - -

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. - - - - - Nelson, - T. - H. - - - 1980. - Replacing the printed word: a complete literary - system. In Information Processing '80: Proceedings of the - IFIPS Congress, October 1980, - ed. - - - Simon - H. - Lavington - - , - 1013-23. - Amsterdam: North- - Holland. (Apparently a draft of section 4 of - Literary - Machines.) - -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.

- - - - - - -
-
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: - - - - - - - - - - - - -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: - - - - - Lucy - Allen - Paton - - - Notes on Manuscripts of the - <title level="m" xml:lang="fr">Prophécies de Merlin - - - - PMLA - 1913 - 8 - 122 - -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). -Saarikoski, Pirkko-Liisa, and Paavo Suomalainen, - Studies on the physiology of - the hibernating hedgehog, 15 - Effects of seasonal - and temperature changes on the in vitro glycerol release from - brown adipose tissue - Ann. Acad. Sci. Fenn., Ser. A4 - 1972 - 187 - 1-4 - - -

-

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).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. 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. -Tchaikovsky, Peter Ilich. -The swan lake ballet -= Le lac des cygnes -: grand ballet en 4 actes -: op. 20 -[Score]. -New York: Broude Brothers; [1951] (B.B. 59). vi, 685 p. - -

- -

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 .

- - John Warrack. „Es waren seine letzten Töne!“ - In Joachim Veit - and Frank Ziegler eds. Weber-Studien Bd. 3, Mainz (1996), pp.300–317 - -

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 , and ; 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: - - - Lominandze, DG. - Cyclotron waves in plasma. - - Translated by - AN. Dellis - ; - - edited by - SM. Hamberger - . - 1st ed. - Oxford: - Pergamon Press, - 1981. - 206 p. - International series in natural philosophy. - Translation of: - Ciklotronnye volny v - plazme. - 0-08-021680-3. - - - - -

-

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. - - - Des Minnesangs Frühling - Mit 1 Faksimile - 36., neugestaltete und erweiterte Auflage - - Unter Benutzung der Ausgaben von Karl - Lachmann und Moriz Haupt, Friedrich - Vogt und Carl von Kraus bearbeitet von - Hugo Moser - Helmut Tervooren - - - Stuttgart - S. Hirzel Verlag - 1977 - - I Texte - - - - - -

-

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. - - proofreading - Ashley Cross - Loren Noveck - -The following example records the fact that one individual had two -distinctly different intellectual responsibilities at different times. - - Erica Dillon - annotated uncredited citations - encoded named entities - -

-

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: - - - Proceedings of a workshop on corpus resources - - Programme Organizer - Geoffrey Leech - - DTI Speech and Language Technology Club meeting, 3-4 - January 1990, Wadham College, Oxford - Oxford - - - - -

- - - - - - - - - -
-
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: - - - - - John - Downame - - Foure treatises tending to disswade all Christians from foure no lesse hainous then common sinnes - 7141 - - At London - 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 - 1609 - - - - -

-

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: - - - - - - -

-

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: - - - - - US - - 6885550 - - B1 - April 26, 2005 - - - - -

-
-
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: - - - - - - - - - -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. - - - - -

-

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 . Alternatively, -if desired, the rs or name elements described in -section 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: - - - Nicholas, Charles K. - Welsch, Lawrence A. - On the interchangeability of SGML and ODA - NISTIR 4681 - - Gaithersburg, MD - - National Institute of Standards and Technology - - January 1992 - - 19 pp. - - -and with dissertations: - - - Hansen, W. - Creation of hierarchic text - with a computer display - ANL-7818 - Ph.D. dissertation - - Dept. of Computer Science, Stanford Univ. - Stanford, CA - June 1971 - - - -

-

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. - - - Shirley, James - The gentlemen of Venice - a tragi-comedie presented at the private - house in Salisbury Court by Her Majesties servants - [Microform] - - London - H. Moseley - 1655 - - 78 p. - - - - New York - Readex Microprint - 1953 - - 1 microprint card, 23 x 15 cm. - - - Three centuries of drama: English, 1642–1700 - - - -

-

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: - - - - - EP - - 1558513 - - A1 - - - - - - B1 - - - - - -

-

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 below.

-
-
-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: - - - - - Wrigley - E. - A. - - - Parish registers and the historian - - - - - Steel - D. - J. - - - - - Steel - A. - E. - F. - - - General sources of births, marriages and deaths before 1837 - - London - Society of Genealogists - - - 155–167 - - - National index of parish registers - 1 - - -

-

The unit attribute on biblScope is optional: -both the following are legal examples: - - - Boguraev, Branimir - Neff, Mary - Text Representation, Dictionary Structure, - and Lexical Knowledge - - - Literary & Linguistic Computing - - 1992 - - 7 - 2 - 110-112 - - - - - Chesnutt, David - Historical Editions in the States - - - Computers and the Humanities - - (December, 1991): - - 25.6 - 377–380 - - - - - -

-

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: - - - Chesnutt, David - Historical Editions in the States - - - Computers and the Humanities - - (December, 1991): - - 25.6 - 377–380 - - 378 - -

- - - - - - - -
-
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 ) may be tagged -editor or respStmt. Any identifier associated with -the series itself should be marked using the idno element. -

-
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: - - -

- -

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. - - - - Swinburne, Algernon Charles - Swinburne's <title level="m">Atalanta in Calydon: A Facsimile of the - First Edition - Georges Lafourcade - - London - Oxford UP - 1930 - - - - - - - - - - Swinburne, Algernon Charles - Atalanta in Calydon - - London - Edward Moxon - 1865 - - - - - -

- -

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: - - - - Shirley, James - The gentlemen of Venice - - New York - Readex Microprint - 1953 - - 1 microprint card, 23 x 15 cm. - - - Three centuries of drama: English, 1642–1700 - - - - Shirley, James - The gentlemen of Venice - a tragi-comedie presented at the private - house in Salisbury Court by Her Majesties servants - - London - H. Moseley - 1655 - - 78 p. - - -

-

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: - - - Tolkien, J.R.R. - Den hobbit - aus dem Engleschen iwwersat - Henry Wickens - - Esch-sur-Sûre - Op der Lay S. àr. L - 2002 - - - - - Tolkien, J.R.R. -The Hobbit. - Collins - 1997 - - - -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: - - - -

- - - - - - - - - -
-
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. - -

-

For example: - - Coombs, James H., Allen H. Renear, - and Steven J. DeRose. - Markup Systems and the Future of Scholarly -Text Processing. - Communications of the ACM - 30.11 (November 1987): 933–947. - Classic polemic supporting descriptive over procedural - markup in scholarly work. - -

-

-The textLang element may be used to record information about the languages used within a bibliographic item. - -This element can take the form of a simple note such as: - -Latin, with some glosses in Anglo-Saxon and French - -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: - -Latin, with some glosses in Anglo-Saxon and French - -

-

The mainLang and otherLangs attributes should both provide language identifiers -in the same form as used for xml:lang as described at . 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 .

-

A description, in French, of a work predominantly in German, but also with some Latin might -have a textLang like the following: - -allemand et latin - For more information about the use of textLang in manuscript descriptions -see: .

- -
-
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: - -notes on the publication (and meeting elements -describing the conference, in the case of a proceedings volume) -edition elements, each followed by any related -editor or respStmt elements -imprint -biblScope -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 . -

-
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 ). 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 () ... -

-

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 (ibid, passim) ... 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 (Nelson [1980] 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 (Nelson [1980] pages 13–37) ... -

-

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: - - - - -Suzana -Sukovic - -Beyond the Scriptorium: The Role of the Library in Text -Encoding -https://www.dlib.org/dlib/january02/sukovic/01sukovic.html - - -D-Lib - -8 -1 -2002 - - - - -

-

The ptr element may be used as a child element of biblStruct to refer to the online catalog record of this bibliographic item: - - - - - - Germain - Brice - - - 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 - - 1717 - Paris - F. Fournier - - In-12 - - - - -

-
- -
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.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. Elements and structures available in the module defined here which -have no analogues in Scribe and BibTeX are not noted. - - - tag as placeName or address - - tag as note - - tag as author - - tag as title level="m" or title within - monogr - - tag as biblScope unit="chap" - - used only to record date entry was made in the bibliographic database; - not supported - - tag as edition - - tag as editor or respStmt - - tag as multiple editor or respStmt elements - - use the reg element, possibly inside a choice element, inside either an author or name - - use the reg element, possibly inside a choice element, inside a name type="org" - - tag as note, possibly using the form note - place="inline" - - used only for issuer of technical reports; tag as publisher - - tag as title level="j" or title within - monogr - - used to specify an alternate sort key for the bibliographic item, for - use instead of author's or editor's name; not supported - - tag as meeting or as note - - 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 - - tag as note - - tag as biblScope unit="issue" or biblScope - unit="number"; for technical report numbers, use idno - type="docno" - - used only for sponsor of conference; use name type="org" - within respStmt within meeting element - - tag as biblScope unit="pp" - - tag as publisher - - used only for institutions at which thesis work is done; tag as - publisher - - tag as title level="s" or title within - series - - tag as title in appropriate context or with appropriate - level value - - tag as biblScope unit="volume" - - tag as date; if the date is not in a trivially parseable form, - use the when attribute to provide an ISO-format - equivalent - -

- -
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. - -

-

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 ; for performance texts, see the -drama base described in chapter ). 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. -

- -
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 and . 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 . 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: - - -Of Mans First Disobedience, and the Fruit -Of that Forbidden Tree, whose mortal tast -Brought Death into the World, and all our woe, -With loss of Eden, till one greater Man -Restore us, and regain the blissful Seat... - - -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 .

-

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 . 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: - -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. - - - Come fill up the Glass, - Round, round let it pass, - 'Till our Reason be lost in our Wine: - Leave Conscience's Rules - To Women and Fools, - This only can make us divine. - - - Then a Mohock, a Mohock I'll be, - No Laws shall restrain - Our Libertine Reign, - We'll riot, drink on, and be free. - -

-

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 . For example: - - - Thus speaks the Muse, and bends her brow severe:— - “Did I, Lætitia, lend my choicest lays, - And crown thy youthful head with freshest bays, - That all the' expectance of thy full-grown year - Should lie inert and fruitless? O revere - Those sacred gifts whose meed is deathless praise, - Whose potent charms the' enraptured soul can raise - Far from the vapours of this earthly sphere! - - - Seize, seize the lyre! resume the lofty strain! - 'T is time, 't is time! hark how the nations round - With jocund notes of liberty resound,— - And thy own Corsica has burst her chain! - O let the song to Britain's shores rebound, - Where Freedom's once-loved voice is heard, - alas! in vain.” - - -

-

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: -Thou fumblest Eros, and my Queenes a Squire -More tight at this, then thou: Dispatch. O Loue, -That thou couldst see my Warres to day, and knew'st -The Royall Occupation, thou should'st see -A Workeman in't. -Enter an Armed Soldier. -Good morrow to thee, welcome. -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: - - - -Unprofitably travelling toward the grave, -Like a false steward who hath much received -And renders nothing back. - -Was it for this -That one, the fairest of all rivers, loved -To blend his murmurs with my nurse's song, - - - -

-

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: - - First Voice - - But why drives on that ship so fast - Withouten wave or wind? - - - - Second Voice - - The air is cut away before, - And closes from behind. - - - -

-

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 . For discussion of -other elements and attributes specific to the encoding of verse, see -chapter . -

- - - - - -
-
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 and . 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: - - Scene 2. - Peachum, Filch. - - FILCH. -

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.

- - - PEACHUM. -

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.

- - - FILCH. -

Tom Gagg, sir, is found guilty.

- - - -

-

In the following example, each speech consists of a sequence of verse -lines, some of them being marked as metrically incomplete: - - ACT I - - SCENE I - Enter Barnardo and Francisco, - two Sentinels, at several doors - Barn - Who's there? - - Fran - Nay, answer me. Stand and unfold yourself. - - Barn - Long live the King! - - Fran - Barnardo? - - Barn - He. - - Fran - You come most carefully upon your hour. - - Barn - 'Tis now struck twelve. Get thee to bed, Francisco. - - Fran - For this relief much thanks. 'Tis bitter cold, - And I am sick at heart. - - - - -

-

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: -Enter two Centinels. -Now call'd Bernardo & -Francesco. - 1. - Stand: who is that? - - 2. - Tis I. - - 1. - O you come most carefully vpon your watch, - - 2. - And if you meete Marcellus and Horatio, - The partners of my watch, bid them make haste. - - 1. - I will: See who goes there. - -Enter Horatio and Marcellus. - - -

-

By contrast with the preceding examples, the following encodes an -early printed edition without making any assumption about which parts -are prose or verse: - - - Actus primus, Scena prima. - A tempestuous - noise of Thunder and Lightning heard: Enter - a Ship-master, and a Boteswaine. - - Master.

Bote-swaine.

- - - Botes.

Heere Master: What cheere?

- - - Mast. -

Good: Speake to th' Mariners: fall - too't, yarely, or we run our selues a ground, - bestirre, bestirre. Exit. -

- - Enter Mariners. - - Botes. -

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.

- - - - -

-

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: -The reverend Doctor Opimian -

I do not think I have named a single unpresentable fish.

- -Mr Gryll -

Bream, Doctor: there is not much to be said for bream.

- -The Reverend Doctor Opimian -

On the contrary, sir, I think there is much to be said for him. - In the first place ...

-

Fish, Miss Gryll — I could discourse to you on fish by the - hour: but for the present I will forbear ...

- - - - Lord Curryfin - (after a pause). -

Mass as the second grave-digger says - in Hamlet, I cannot tell.

- -

A chorus of laughter dissolved the sitting.

 - -

- - - - - - -
-
- Overview of the Core Module -

All the elements described in this chapter are provided by the - core module. - - Common Core - Elements common to all TEI documents - Éléments disponibles pour tous les documents TEI - 所有TEI文件所通用的元素 - Elementi comuni a tutti i documenti TEI - Elementos comuns a todos os documentos TEI - コアモジュール - - The selection and combination of modules to form a TEI schema is - described in .

- - - - - - - - - - - - - - - - - - -
-
diff --git a/P5/Source/Guidelines/fr/CO-CoreElements.xml b/P5/Source/Guidelines/fr/CO-CoreElements.xml new file mode 120000 index 0000000000..5c5b56dfe0 --- /dev/null +++ b/P5/Source/Guidelines/fr/CO-CoreElements.xml @@ -0,0 +1 @@ +../en/./CO-CoreElements.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/COL-Colophon.xml b/P5/Source/Guidelines/fr/COL-Colophon.xml deleted file mode 100644 index dcdd313fb0..0000000000 --- a/P5/Source/Guidelines/fr/COL-Colophon.xml +++ /dev/null @@ -1,38 +0,0 @@ - - - - - - - -
- Colophon -

The text of this manual was prepared electronically on a variety of - systems. Most sections were originally drafted by members of the work - groups and working committees of the TEI; all have been revised by the - editors to achieve greater uniformity of style and greater consistency - in the tag set.

- -

The web release of the Guidelines was created using a library of - XSLT stylesheets to convert to XHTML; the PDF version for printing was - produced by conversion to LaTeX markup, processed using XeLaTeX. - The XSLT libraries were written by Sebastian Rahtz.

- - -

Almost every available SGML and XML editor or processing program - has been used at one time or another by the TEI; but - without the open source implementations of XML parsers, editors and - XSLT engines by James Clark, Richard Stallman, Michael Kay, and Daniel - Veillard, the TEI could not survive, and we thank these - individuals. We would also like to thank the staff at SyncRO Soft SRL, - creators of the oXygen editor, for their support for the TEI during - the creation on P5.

- -

Many volunteers contributed to the preparation of this release of - the Guidelines; we particularly note the work of Sabine Krott, Eva - Radermacher and Arianna Ciula for their work in structuring the - bibliographies.

- -

The production and release process for TEI P5 was originally developed by - Sebastian Rahtz for the TEI Technical Council.

-
diff --git a/P5/Source/Guidelines/fr/COL-Colophon.xml b/P5/Source/Guidelines/fr/COL-Colophon.xml new file mode 120000 index 0000000000..49c7b82206 --- /dev/null +++ b/P5/Source/Guidelines/fr/COL-Colophon.xml @@ -0,0 +1 @@ +../en/./COL-Colophon.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/DI-PrintDictionaries.xml b/P5/Source/Guidelines/fr/DI-PrintDictionaries.xml deleted file mode 100644 index 40060bcdce..0000000000 --- a/P5/Source/Guidelines/fr/DI-PrintDictionaries.xml +++ /dev/null @@ -1,3106 +0,0 @@ - - - - -
- Dictionaries - -

This chapter defines a module for encoding lexical resources of all -kinds, in particular human-oriented -monolingual and multilingual dictionaries, glossaries, and similar -documents. The elements described here may also be useful in the -encoding of computational lexica and similar resources intended for -use by language-processing software; they may also be used to provide -a rich encoding for wordlists, lexica, glossaries, etc. included -within other documents. Dictionaries are most familiar in -their printed form; however, increasing numbers of dictionaries exist -also in electronic forms which are independent of any particular -printed form, but from which various displays can be produced.

- -

Both typographically and structurally, print dictionaries are -extremely complex. Such lexical resources are moreover of interest to -many communities with different and sometimes conflicting goals. As a -result, many general problems of text encoding are particularly -pronounced here, and more compromises and alternatives within the -encoding scheme may be required in the future.We -refer the reader to previous and current discussions of a common -format for encoding lexical resources. For example, ; ; ; ; ; ; ; and ; . Two problems are particularly -prominent.

- -

First, because the structure of dictionary entries varies widely -both among and within dictionaries, the simplest way for an encoding -scheme to accommodate the entire range of structures actually -encountered is to allow virtually any element to appear virtually -anywhere in a dictionary entry. It is clear, however, that strong and -consistent structural principles do govern the vast majority of -conventional dictionaries, as well as many or most entries even in -more exotic dictionaries; -encoding guidelines should include these structural principles. We -therefore define two distinct elements for dictionary entries, one -(entry) which captures the regularities of many conventional -dictionary entries, and a second (entryFree) which uses the -same elements, but allows them to combine much more freely. It is -however recommended that entry be used in preference to -entryFree wherever possible. -These elements and their contents are described in sections , , and .

- -

Second, since so much of the information in printed dictionaries is -implicit or highly compressed, their encoding requires clear thought -about whether it is to capture the precise typographic form of the -source text or the underlying structure of the information it -presents. Since both of these views of the dictionary may be of -interest, it proves necessary to develop methods of recording both, -and of recording the interrelationship between them as well. Users -interested mainly in the printed format of the dictionary will require -an encoding to be faithful to an original printed version. However, -other users will be interested primarily in capturing the lexical -information in a dictionary in a form suitable for further processing, -which may demand the expansion or rearrangement of the information -contained in the printed form. Further, some users wish to encode -both of these views of the data, and retain the links -between related elements of the two encodings. Problems of recording -these two different views of dictionary data are discussed in section -, together with mechanisms for retaining both -views when this is desired.

- -

To deal with this complexity, and in particular to account for the -wide variety of linguistic contexts within which a dictionary may be -designed, it can be necessary to customize or change the schema by -providing more restriction or possibly alternate content models for -the elements defined in this chapter. Section -illustrates this with the provision of a closed set of values for -grammatical descriptors.

- -

This chapter contains a large number of examples taken from -existing print dictionaries; in each case, the original source is -identified. In presenting such examples, we have tried to retain the -original typographic appearance of the example as well as presenting a -suggested encoding for it. Where this has not been possible (for -example in the display of pronunciation) we have adopted the -transliteration found in the electronic edition of the Oxford -Advanced Learner's Dictionary. Also, the middle dot in quoted -entries is rendered with a full stop, while within the sample -transcriptions hyphenation and syllabification points are indicated by -a vertical bar |, regardless of their appearance in the source -text.

- -
-Dictionary Body and Overall Structure - -

Overall, dictionaries have the same structure of front matter, -body, and back matter familiar from other texts. In addition, -this module defines entry, entryFree, -and superEntry as component-level elements which can occur -directly within a text division or the text body.

- -

The following tags can therefore be used to mark the gross structure of a -printed dictionary; the dictionary-specific tags are discussed further -in the following section. - - - - - - - - -

- -

As members of the classes att.entryLike and - att.sortable, -entry and entryFree share the following -attributes: - - - -

- -

The front and back matter of a dictionary may well contain -specialized material such as lists of common and proper nouns, -grammatical tables, gazetteers, a guide to the use of the -dictionary, etc. These should be tagged using elements -defined elsewhere in these Guidelines, chiefly in the core module -(chapter ) together with the specialized dictionary -elements defined in this chapter.

- -

The body element consists of a set of -entries, optionally grouped into one or several -div elements. These text divisions might, for example, correspond to -sections for different letters of the alphabet, or to sections for -different languages in a bilingual dictionary, as in the following -example: - - - -

English-French -
cat
 -
dog
 -
horse
 -
-
-French-English -
chat
 -
chien
 -
cheval
 -
- - -

- -

In a -print dictionary, the entries are typically typographically distinct -entities, each headed by some morphological form of the lexical item -described (the headword), and sorted in alphabetical -order or (especially for non-alphabetic scripts) in some other -conventional sequence. Dictionary entries should be encoded as -distinct successive items, each marked as an entry or -entryFree element. The type attribute may be used -to distinguish different types of entries, for example main entries, -related entries, run-on entries, or entries for cross-references, -etc.

- -

Some dictionaries provide distinct entries for homographs, on the -basis of etymology, part-of-speech, or both, and typically provide a -numeric superscript on the headword identifying the homograph -number. In these cases each homograph should be encoded as a separate -entry; the superEntry element may optionally be used to group -such successive homograph entries. In addition to a series of -entry elements, the superEntry may contain a -preliminary form group (see section ) -when information about hyphenation, pronunciation, etc., is given only -once for two or more homograph entries. If the homograph number is to -be recorded, the global attribute n may be used for this -purpose. In some dictionaries, homographs are treated in distinct -parts of the same entry; in these cases, they may be separated by use -of the hom element, for which see section .

- -

A sort key, given in the sortKey attribute, is often -required for superentries and entries, especially in cases where the -order of entries does not follow the local character-set collating -sequence (as, for example, when an entry for 3D appears at the -place where three-D would appear).

- - - -

A dictionary with no internal divisions might thus have a structure like -the following; a superEntry is shown grouping two homograph -entries. - - -

- manifestation -
- - -
- émeute -
 - - -
- grève -
- - -
- grève -
- - - - -

- - - - - - - - - - - - - - - - - - - - - -
-
-The Structure of Dictionary Entries - -

A simple dictionary entry may contain information about the form of -the word treated, its grammatical characterization, its definition, -synonyms, or translation equivalents, its etymology, cross-references -to other entries, usage information, and examples. These we refer to -as the constituent parts or constituents of -the entry; some dictionary constituents possess no internal structure, -while others are most naturally viewed as groups of smaller elements, -which may be marked in their own right. In some styles of markup, -tags will be applied only to the low-level items, leaving the -constituent groups which contain them untagged. We distinguish the -class of top-level constituents of dictionary entries, -which can occur directly within the entry element, from the class of -phrase-level constituents, which can normally occur only -within top-level constituents. The top-level constituents of -dictionary entries are described in section , -and documented more fully, together with their phrase-level -sub-constituents, in section .

- -

In addition, however, dictionary entries often have a complex -hierarchical structure. For example, an entry may consist of two or -more sub-parts, each corresponding to information for a different -part-of-speech homograph of the headword. The entry (or part-of-speech -homographs, if the entry is split this way) may also consist of -senses, each of which may in turn be composed of two or more -sub-senses, etc. Each sub-part, homograph entry, sense, or sub-sense -we call a level; at any level in an entry, any or all of -the constituent parts of dictionary entries may appear. The -hierarchical levels of dictionary entries are documented in section -.

- -
-Hierarchical Levels - -

The outermost structural level of an entry is marked with the -elements entry or entryFree. The hom -element marks the subdivision of entries into homographs differing in -their part-of-speech. The sense element marks the subdivision -of entries and part-of-speech homographs into senses; this element -nests recursively in order to provide for a hierarchy of sub-senses of -any depth. It is recommended to use the sense element even -for an entry that has only one sense to group together all parts of -the definition relating to the word sense since this leads to more -consistent encoding across entries. -All of these levels may each contain any of the -constituent parts of an entry. A special case of hierarchical -structure is represented by the re (related entry) element, -which is discussed in section . Finally, the -element dictScrap may be used at any point in the hierarchy -to delimit parts of the dictionary entry which are structurally -anomalous, as further discussed in section . - - - - - - -

-

For example, an entry with two senses will have the following structure: - - - - - -

-

An entry with two homographs, the first with two senses and the second with three - (one of which has two sub-senses), may have a structure like this: - - - - - - - - - - - - - - - In some dictionaries, homographs have separate entries; in -such a case, as noted in section , the two homographs may be - treated as entries, optionally grouped in a superEntry: - - - - - - - - - - - - - - - -

-

The hierarchic structure of a dictionary entry is enforced by the -structures defined in this module. The content model for -entry specifies that entries do not nest, that homographs -nest within entries, and that senses nest within entries, homographs, -or senses, and may be nested to any depth to reflect the embedding of -sub-senses. Any of the top-level constituents (def, -usg, form, etc.) can appear at any level (i.e., -within entries, homographs, or senses). - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

-
-
-Groups and Constituents - -

As noted above, dictionary entries, and subordinate levels within dictionary entries, -may comprise several constituent parts, each providing a different type of -information about the word treated. The top-level constituents of -dictionary entries are: -information about the form of the word treated (orthography, -pronunciation, hyphenation, etc.) -grammatical information (part of speech, grammatical sub-categorization, -etc.) -definitions or translations into another language -etymology -examples -usage information -cross-references to other entries -notes -entries (often of reduced form) for related words, typically called -related entries - - Any of the hierarchical levels (entry, entryFree, -hom, and sense) may contain any of these top-level constituents, since -information about word form, particular grammatical information, special -pronunciation, usage information, etc., may apply to an entire entry, or to only one -homograph, or only to a particular sense. The examples below illustrate this point.

-

The following elements are used to encode these top-level constituents: - - - - - - - - - - -

-

In a simple entry with no internal hierarchy, all top-level constituents can appear -as children of entry. - -com.peti.tor -/k@m"petit@(r)/ n person who competes. OALD - - -

-competitor -com|peti|tor -k@m"petit@(r) -
- -n - -person who competes. - - -For the elements which appear within the form and gramGrp -elements of this and other examples, see below, section , and section .

-

Any top-level constituent can appear at any level when the -hierarchical structure of the entry is more complex. The most obvious examples are -def and cit, which appear at the sense level when -several senses or translations exist: -disproof - (dɪsˈpru:f) n 1 facts that disprove something 2 the -act of disproving. CED - - -

-disproof -dɪsˈpru:f -
- -n - - -facts that disprove something - - -the act of disproving - - - -

-

For ease of processing of such entries containing multiple senses along with those containing -only a single sense, it is recommended to use sense in all entries to wrap those elements -relating to a particular word sense.

-

In the following example, gramGrp is used to distinguish two homographs: -bray -/breI/ n cry of an ass; sound of a trumpet. ∙ vt [VP2A] -make a cry or sound of this kind. OALD - - -

-bray -breI -
- - -n - - -cry of an ass; sound of a trumpet. - - - - -vt -VP2A - - -make a cry or sound of this kind. - - - - - -

-

Information of the same kind can appear at different levels within the same entry; -here, grammatical information occurs both at entry and homograph level. -ca.reen -/k@"ri:n/ vt,vi 1 [VP6A] turn (a ship) on one side for -cleaning, repairing, etc. 2 [VP6A, 2A] (cause to) tilt, lean over to one side. -OALD - - -

-careen -ca|reen -k@"ri:n -
- -vt -vi - - - -VP6A - -turn (a ship) on one side for cleaning, repairing, etc. - - - -VP6A -VP2A - -(cause to) tilt, lean over to one side. - - - - -

-

Alone among the constituent groups, form can appear at the -superEntry level as well as at the entry, hom, and -sense levels: -a.ban.don 1/@"band@n/ -v [T1] 1 to leave completely and for ever; desert: The sailors abandoned the -burning ship. 2 …abandon 2 n [U] the state when one's -feelings and actions are uncontrolled; freedom from control...LDOCE - - -

-abandon -a|ban|don -@"band@n -
- - -v -T1 - - -to leave completely and for ever … - - - - - -n -U - - -the state when one's feelings and actions are uncontrolled; freedom -from control… - - - - -

-
-
-
-Top-level Constituents of Entries -

This section describes the top-level constituents of dictionary entries, together with -the phrase-level constituents peculiar to each. -the form element, which groups orthographic information and -pronunciations, is described in section - -the gramGrp element, which groups elements for the grammatical -characterization of the headword, is described in section - -the def element, which describes the meaning of the headword, is -described in section - -the etym element and its special phrase-level elements are documented -in section - -the cit element and its specific applications are described in -section and section - -the usg, lbl, xr, and note elements are -described in section - -the re element, which marks nested entries for related words, is -described in section - - -

-
-Information on Written and Spoken Forms -

Dictionary entries most often begin with information about the form of the word to -which the entry applies. Typically, the orthographic form of the word, sometimes -marked for syllabification or hyphenation, is the first item in an entry. Other -information about the word, including variant or alternate forms, inflected forms, -pronunciation, etc., is also often given.

-

The following elements should be used to encode this information: the form -element groups one or more occurrences of any of them; it can also be -recursively nested to reflect more complex sub-grouping of information about word -form(s), as shown in the examples. - - - - - - - - -

-

In addition to those listed above, the following elements, which encode morphological -details of the form, may also occur within form elements: - - - - - - - - - - - - Of these, the gram element is most general, and all of the -others are synonymous with a gram element with appropriate values (gen, -number, case, etc.) for the type attribute.

-

The use of these elements as children of form is deprecated; instead, they -should always be children of a gramGrp within form when describing -that particular form of the word.

-

Different dictionaries use different means to mark hyphenation, -syllabification, and stress, and they often use some unusual glyphs -(e.g., the middle dot for hyphenation). All of -these glyphs are in the Unicode character set, as discussed in . When transcribing representations of pronunciation -the International Phonetic Alphabet should be used. It may be -convenient (as has been done in the text of this chapter) to use a -simple transliteration scheme for this; such a scheme should however be -properly documented in the header.

-

In the simplest case, nothing is given but the orthography: -

-doom-laden -
- -

-

Often, however, pronunciation is given. -soucoupe [sukup] … DNT - -

-soucoupe -sukup -
- -

-

For a variety of reasons including ease of processing, it may be desired to split -into separate elements information which is collapsed into a single element in the -source text; orthography and hyphenation may for example be transcribed as separate -elements, although given together in the source text. For a discussion of the issues -involved, and of methods for retaining both the presentation form and the -interpreted form, see section .

-

This example splits orthography and hyphenation, and adds syllabification because it -differs from hyphenation: -ar.ea … W7 - -

-area -ar|ea -ar|e|a -
- - -

-

Multiple orthographic forms may be given, e.g. to illustrate a word's inflectional -pattern: -brag … vb brags, bragging, bragged … CED - -

-brag -
- -vb - -
-brags -bragging -bragged -
- Or the inflectional pattern may be indicated by reference to a table of -paradigms, as here: -horrifier -[ORifje] (7) vt … [C/R] - -
-horrifier -ORifje - -7 - - -
- - -

- -

Explanatory labels may be attached to alternate forms: -MTBF -abbreviation for mean time between failures CED - - -

-MTBF -
-
-abbreviation for -mean time between failures -
- - -

-

When multiple orthographic forms are given, a pronunciation may be associated with -all of them, as here: -biryani or biriani - (ˌbɪrɪˈa:nɪ) … CED - -

-biryani -biriani -ˌbɪrɪˈa:nɪ -
- -

-

In other cases, different pronunciations are provided for different orthographic -forms; here, the form element is repeated to associate the first -orthographic form explicitly with the first pronunciation, and the second -orthographic form with the second pronunciation: -mackle - (ˈmækᵊl) or macule (ˈmækju:l) … CED - -

-mackle -ˈmækᵊl -
-
-macule -ˈmækju:l -
- -

-

Recursive nesting of the form element can preserve relations among elements -that are implicit in the text. For example, in the CED entry for hospitaller, -it is clear that U.S. is associated only with hospitaler, but that the -pronunciation applies to both forms. The following encoding preserves these -relations: - hospitaller or US hospitaler (ˈhɒspɪtələ) … CED - -

-hospitaller - -US -hospitaler -
-ˈhɒspɪtələ - - - -

- - - - - - - - - - - - - - - - - - - - - - - - - -
-
-Grammatical Information -

The gramGrp element groups grammatical information, such as part of speech, -subcategorization information (e.g., syntactic patterns for verbs, count/mass -distinctions for nouns), etc. It can contain any of the morphological elements defined -in section for form and can appear as a child of entry, -form, sense, cit, or any other element containing content about which -there is grammatical information. For example, in the entry - pinna (ˈpɪnə) n, - pl -nae (-ni:) or -nas CED, the -word defined can be either singular or plural; the pl. specification applies -only to the inflected forms provided. Compare this with pants (paents) pl. -n., where pl. applies to the headword itself.

-

As noted above in section , the elements for morphological -information are simply shorthand for the general purpose gram element. -Consider this entry for the French word médire: - -médire v.t. ind. (de) … PLC This entry can be -tagged using specialized grammatical elements: -

-médire -
- -v -t ind -de - - Or using the gram element: -
-médire -
- -v -t ind -de - - -

-

Like form, gramGrp can be repeated, recursively nested, or used at -the sense level to show relations among elements. -isotope adj. et n. m. … DNT - -

-isotope -
- -adj - - -n -m - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - wits (wɪts) pl n 1 - (sometimes singular) the ability to -reason and act, esp quickly … CED - - -
-wits -wɪts -
- -pl -n - - - -sometimes singular - -the ability to reason and act, esp quickly … - - - -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-
-Sense Information -

Dictionaries may describe the meanings of words in a wide variety of different - ways—by means of synonyms, paraphrases, translations into other languages, formal -definitions in various highly stylized forms, etc. No attempt is made here to -distinguish all the different forms which sense information may take; -all of them may -be tagged using the def element described in section .

-

As a special case it is frequently desirable to distinguish -the provision of translation equivalents in other languages from other -forms of sense information; the use of cit -type="translation" (which groups a translation equivalent with -related information such as its grammatical description) -for this purpose is described -in section .

- -
-Definitions -

Dictionary definitions are those pieces of prose in a dictionary entry that -describe the meaning of some lexical item. Most often, definitions describe the -headword of the entry; in some cases, they describe translated texts, examples, -etc.; see cit type="translation", section , and -cit type="example", section . The -def element directly contains the text of the definition; unlike -form and gramGrp, it does not serve solely to -group a set of smaller elements. The close analysis of definition text, such as -the tagging of hypernyms, typical objects, etc., is not covered by these -Guidelines.

-

Definitions may occur directly within an entry; when multiple -definitions are given, they are typically identified as belonging to -distinct senses, as here: demigod (…) n. 1.a. a being who is part mortal, part -god. b. a lesser deity. 2. a godlike person. CP - - -

-demigod - … -
- -n - - - -a being who is part mortal, part god. - - -a lesser deity. - - - -a godlike person. - - - -

-

In multilingual dictionaries, it is sometimes possible to distinguish translation -equivalents from definitions proper; here a def element is -distinguished from the translation information within which it appears. -rémoulade -[Remulad] nf remoulade, rémoulade (dressing containing mustard and herbs). CR - - -

-rémoulade -Remulad -
- -n -f - - -remoulade -rémoulade -dressing containing mustard and herbs - - - -

- - - - - - - - - - - - - - -
-
-Translation Equivalents -

Multilingual dictionaries contain information about translations of a given word -in some source language for one or more target languages. Minimally, the -dictionary provides the corresponding translation in the target language; other -material, such as morphological information (gender, case), various kinds of -usage restrictions, etc., may also be given. If translation equivalents are to -be distinguished from other kinds of sense information, they may be encoded -using cit type="translation". The global xml:lang attribute -should be used to specify the target language.

-

As in monolingual dictionaries, the sense element is used in -multilingual dictionaries to group information (forms, grammatical information, -usage, translation(s), etc.) about a given sense of a word where necessary. -Information about the individual translation equivalents within a sense is -grouped using cit type="translation". This information may include the -translation text (tagged q or quote), morphological -information (gen, case, etc.), usage notes (usg), -translation labels (lbl), and definitions (def).When -bibliographic data is provided, the quote element should be used. - - - -

-

Note how in the following example, different translation -equivalents are grouped into the same or different senses, following -the punctuation of the source and the usage labels: -dresser … (a) (Theat) habilleur m, -euse f; -(Comm: window ~) étalagiste mf. she's a stylish ~ elle s'habille avec -chic; V hair. (b) (tool) (for wood) raboteuse f; (for stone) rabotin -m. CR - - - - - -

-dresser -
- - -Theat - -habilleur - -m - - - --euse - -f - - - - -Comm -
-window - -
- -étalagiste - -mf - - - - -she's a stylish - - -elle s'habille avec chic - - -V. hair - - - -tool - -for wood - -raboteuse - -f - - - - -for stone - -rabotin - -m - - - - - - - - - - -

-

In the following example, a distinction is made between the -translation equivalent (OAS) and a descriptive phrase providing -further information for the user of the dictionary. -O.A.S. ... nf (abrév de Organisation de l'Armée secrète) OAS (illegal military organization supporting French rule of -Algeria). CR - - - - -OAS -illegal military organization supporting French rule of -Algeria - - - -

-

Note that cit type="translation" may also be used in monolingual -dictionaries when a translation is given for a foreign word: - -havdalah or havdoloh Hebrew - (havdaˈla; Yiddish havˈdɔlə) - n Judaism the ceremony marking the end of the -sabbath or of a festival, including the blessings over wine, candles and -spices [literally: separation] CED - - -

-havdalah -havdoloh - -n - -
- -Judaism -the ceremony marking the end of the sabbath or of a festival, -including the blessings over wine, candles and spices - - -literally -separation - - - -

-
-
-
-Etymological Information -

The element etym marks a block of etymological information. Etymologies may -contain highly structured lists of words in an order indicating their descent from -each other, but often also include related words and forms outside the direct line -of descent, for comparison. Not infrequently, etymologies include commentary of -various sorts, and can grow into short (or long!) essays with prose-like structure. -This variation in structure makes it impracticable to define tags which capture the -entire intellectual structure of the etymology or record the precise interrelation -of all the words mentioned. It is, however, feasible to mark some of the more -obvious phrase-level elements frequently found in etymologies, using tags defined in -the core module or elsewhere in this chapter. Of particular relevance for the -markup of etymologies are: - - - - - - - - - -

-

As in other prose, individual word forms mentioned in an etymological description are -tagged with mentioned elements. Pronunciations, usage labels, and glosses -can be tagged using the pron, usg, and gloss elements -defined elsewhere in these Guidelines. In addition, the lang element may be -used to identify a particular language name where it appears, in addition to using -the xml:lang attribute of the mentioned element.

-

Examples: -abismo m. (del gr. a priv. y byssos, fondo). Sima, gran -profundidad. … - - -

-abismo -
-del gr. -a priv. y byssos, -fondo - - - - - -neume -\'n(y)üm\ n [F, fr. ML pneuma, neuma, fr. Gk pneuma -breath — more at pneumatic]: any of various symbols used in -the notation of Gregorian chant … [WNC] - - - - -F fr. ML -pneuma -neuma fr. Gk -pneuma -breath -more at - - - -any of various symbols used in the notation of Gregorian chant - - - - - - - -

- - - - - -
-
-Other Information -
-Examples -

Dictionaries typically include examples of word use, usually accompanying -definitions or translations. In some cases, the examples are quotations from -another source, and are occasionally followed by a citation to the author.

-

The cit type="example" element contains usage examples and associated -information; the example text itself should be enclosed in a q or -quote element. The cit element associates a quotation with -a bibliographic reference to its source. - - - - -

-

Examples frequently abbreviate the headword, and so their transcription will -frequently make use of the oRef element described -below in section .

-

Examples: -multiplex -/…/ adj tech having many parts: the multiplex eye -of the fly. LDOCE - - -the multiplex eye of the fly. - Or when one wants a more comprehensive representation of -examples: - -the multiplex eye of the fly. - - As the following example shows, cit can also contain elements -such as pron, def, etc. -some … 4. (S~ and any are used with more): Give me ~ more/s@'mO:(r)/ OALD - - - - - and any are used with -more - - -Give me more -s@'mO:(r) - - - In multilingual dictionaries, examples may also be accompanied by -translations: -horrifier … vt to horrify. elle était -horrifiée par la dépense she was horrified at the expense. CR - - - - - -to horrify - - -elle était horrifiée par la dépense - -she was horrified at the expense. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - When a source is indicated, the example should be marked -with a bibl element: -valeur … n. f. … 2. Vx. Vaillance, bravoure -(spécial., au combat). La valeur n'attend pas le nombre des années -(Corneille). … DNT - - -Vx. -Vaillance, bravoure (spécial., au combat) - -La valeur n'attend pas le nombre des années - -Corneille - - - - -

-
-
-Usage Information and Other Labels - -

Most dictionaries provide restrictive labels and phrases indicating -the usage of given words or particular senses. Other phrases, not -necessarily related to usage, may also be attached to forms, translations, -cross-references, and examples. The following elements are provided -to mark up such labels: - - - As indicated in the following section (), the -lbl element may be used for any kind of significative phrase -or label within the text. The usg element is a specialization -of this to mark usage labels in particular. Usage labels typically -indicate -temporal use (archaic, obsolete, etc.) -register (slang, formal, taboo, ironic, facetious, etc.) -style (literal, figurative, etc.) -connotative effect (e.g. derogatory, offensive) -subject field (Astronomy, Philosophy, etc.) -national or regional use (Australian, U.S., Midland dialect, -etc.) - Many dictionaries provide an explanation and/or a list of such usage -labels in a preface or appendix. The type of the usage information may be -indicated in the type attribute on the usg element. Some -typical values are: - -geographic area - -temporal, historical era (archaic, old, etc.) - -domain - -register - -style (figurative, literal, etc.) - -preference level (chiefly, usually, etc.) - -acceptability - -language for foreign words, spellings pronunciations, etc. - -grammatical usage - In addition to this kind of information, multilingual dictionaries often -provide semantic cues to help the user determine the right -sense of a word in the source language (and hence the correct translation). -These include synonyms, concept subdivisions, typical subjects and objects, -typical verb complements, etc. These labels may also be marked with the -usg element; sample values for the type attribute in these -cases include: - -synonym given to show use - -hypernym given to show usage - -collocation given to show usage - -typical complement - -typical object - -typical subject - -typical verb - -unclassifiable piece of information to guide sense choice - -

-

In this entry, one spelling is marked as geographically restricted: -colour or US color … CED - -

-colour - -US -color -
- - -

-

In the next example, usage labels are used to indicate domains, register, and -synonyms associated with different senses: -palette -[palEt] nf (a) (Peinture: lit, fig) palette. (b) -(Boucherie) shoulder. (c) (aube de roue) paddle; (battoir à linge) beetle; -(Manutention, Constr) pallet. CR - - -Peinture -lit -fig - -palette - - - -Boucherie - -shoulder - - - - -aube de roue - -paddle - - - -battoir à linge - -beetle - - - -Manutention -Constr - -pallet - - - - - - - - - - - - - - - - - - - - - - - - -

-

When the usage label is hard to classify, it may be described as a hint: -rempaillage […] nm reseating, rebottoming (with straw). CR - - - - -reseating -rebottoming -with straw - - - -

- - - - - -
-
-Cross-References to Other Entries -

Dictionary entries frequently refer to information in other entries, often using -extremely dense notations to convey the headword of the entry to be sought, the -particular part of the entry being referred to, and the nature of the -information to be sought there (synonyms, antonyms, usage notes, etymology, an -illustration, etc.)

-

Cross-references may be tagged in dictionaries using the ref and -ptr elements defined in the core module (section ). In addition, the xr element may be used to group all the -information relating to a cross-reference. - - - - - - -

-

As in other types of text, the actual pointing element (e.g. ref or -ptr) is used to tag the cross-reference target proper (in -dictionaries, usually the headword, possibly accompanied by a homograph number, -a sense number, or other further restriction specifying what portion of the -target entry is being referred to). -The xr element -is used to group the target with any accompanying phrases or symbols used to -label the cross-reference; the cross-reference label itself may be encoded with -lbl or may remain untagged. Both of the following are thus -legitimate: -glee … Compare madrigal (1) -CED - - -

-glee -
-Compare - - - -
- - - -hostellerie Syn. de hôtellerie (sens 1). DNT - - -Syn. de -hôtellerie (sens 1). - In addition to using, or not using, lbl to mark the -cross-reference label, the two examples differ in another way. The former -assumes that the first sense of madrigal has the -identifier madrigal.1, and that the specific form of the reference in the -source volume can be reconstructed, if needed, from that information. The latter -does not require the first sense of hôtellerie to have an identifier, and -retains the print form of the cross-reference; by omitting the target -attribute of the ref element, however, the second example does assume -implicitly either that some software could usefully parse the phrase tagged as a -ref and find the location referred to, or else that such processing -will not be necessary.

-

The type attribute on the pointing element or on the xr -element may be used to indicate what kind of cross-reference is being made, -using any convenient typology. Since different dictionaries may label the same -kind of cross-reference in different ways, it may be useful to give normalized -indications in the type attribute, enabling the encoder to distinguish -irregular forms of cross-reference more reliably: -rose2 … vb the past tense of rise CED - - -

-rose -
- -the past tense of -rise - - - - -
-rise -
- - - from cross-references for synonyms and the like: -antagonist … syn see adverse -W7 - - -syn see -adverse - - - -
-adverse -
- - -Strictly speaking, the reference above is not to the entry for -adverse, but to the list of synonyms found -within that entry. - - In some cases, the cross-reference is to a particular subset of the -meanings of the entry in question: -globe …V. armillaire (sphère) -PR - -V. armillaire -sphère - - -

- -

Cross-references occasionally occur in definition texts, example -texts, etc., or may be free-standing within an entry. These may -typically be encoded using ref or ptr, without an -enclosing xr. For example: - -entacher … Acte entaché de -nullité, contenant un vice de forme ou passé par un incapable*. DNT - The asterisk signals a reference to the entry for -incapable. -contenant un vice de forme ou passé par un . - - In -some cases, the form in the definition is inflected, and thus ref must -be used to indicate more exactly the intended target, as here: -justifier …4. IMPRIM Donner a (une ligne) une longeur -convenable au moyen de blancs (2, sens 1, 3). DNT - - -imprim -Donner a (une ligne) une longeur convenable au moyen de -blancs (2, sens 1, 3) - - - - - - - -... - - - - - - - -

- - - - - - - - - - - - - - -
-
-Notes within Entries -

Dictionaries may include extensive explanatory notes about usage, grammar, -context, etc. within entries. Very often, such notes appear as a separate -section at the end of an entry. The standard note element should be used for -such material. - - -

-

For example: -neither - (ˈnaɪðə, ˈni:ðə) -determiner 1a not one nor the other (of two); - not either: neither foot is swollen … - usage A verb following a compound subject that uses neither… should be - in the singular if both subjects are in the singular: neither Jack nor John has done the work - CED - - -

-neither -ˈnaɪðə, -ˈni:ðə -
- - -neither foot is swollen - -A verb following a compound subject - that uses neither… should be - in the singular if both subjects are in the singular: - neither Jack nor John has done the work - - - -

-

The formal declaration for note is given in section .

-
-
-
-Related Entries -

The re element encloses a degenerate entry which appears in the body of -another entry for some purpose. Many dictionaries include related entries for direct -derivatives or inflected forms of the entry word, or for compound words, phrases, -collocations, and idioms containing the entry word.

-

Related entries can be complex, and may in fact include any of the information to be -found in a regular entry. Therefore, the re element is defined to contain -the same elements as an entry element.

-

Examples: -bevvy - (ˈbɛvɪ) informal n, pl -vies 1 a drink, esp an - alcoholic one: we had a few bevvies last night 2 a session of drinking. ▷ vb - -vies, -vying, -vied (intr) - 3 to drink alcohol [probably from Old French bevee, -buvee, drinking] > 'bevvied adj CED - - -

-bevvy -ˈbɛvɪ -
-informal - - -n - - -a drink, esp. an alcoholic one: we had a few bevvies last night. - - - - - -vb - - -to drink alcohol - - -probably from Old French -bevee, buvee -drinking - - -
-bevvied -
- -adj - - - - -

- - - - - - - - - - - - - - - - - - -
-
-
-Headword and Pronunciation References -

Examples, definitions, etymologies, and occasionally other elements such as -cross-references, orthographic forms, etc., often contain a shortened or iconic reference to -the headword, rather than repeating the headword itself. The references may be to the -orthographic form or to the pronunciation, to the form given or to a variant of that -form. The following elements are used to encode such iconic references to a headword: - - - -

-

These elements all inherit the following attributes from the class att.pointing -which may optionally be used to resolve any -ambiguity about the headword form being referred to. - -

-

Headword references come in a variety of formats: - -indicates a reference to the full form of the headword - -gives a prefix to be affixed to the headword - -gives a suffix to be affixed to the headword - -gives the first letter in uppercase, indicating that the headword is -capitalized - -gives a prefix and a suffix to be affixed to the headword - -gives the initial of the word followed by a full stop, to indicate reference -to the full form of the headword - -refers to a capitalized form of the headword - -

-

The oRef element should be used for iconic or shortened references to the -orthographic form(s) of the headword itself. It is an empty element and replaces, rather -than enclosing, the reference. Note that the reference to a headword is not necessarily -a simple string replacement. In the example -colour1, (US = color) …~ films; ~ TV; Red, blue and yellow -are ~s. OALD, the tilde stands for either headword form -(colour, color).

-

Examples: -colonel … army officer above a lieutenant-~. OALD - -army officer above a lieutenant- - - - - - - - - - - - - -academy … The Royal A~ of Arts OALD - -The Royal of Arts - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

-

The following example demonstrates the use of the target attribute to refer to -a specific form of the headword: -vag- or vago- comb form … : vagus nerve -< vagal > < vagotomy -> W7 - - -

-vag- -vago- -
-vagus nerve - - -al - -tomy - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

-

In many cases the reference is not to the orthographic form of the headword, but rather -to another form of the headword—usually to an inflected form. In these cases, the -element oRef should be used; this element may take as its content the string as it -appears in the text. -take … < Mr Burton took us for -French > NPEG - - -Mr Burton took us for French - - - -take … < was quite ~n with him -> NPEG - - -was quite n with him - - -

-

The next example shows a discontinuous reference, using the -attributes -next and -prev, which are defined in the additional module for linking, -segmentation, and alignment (see chapter ) and therefore require that -that module be selected in addition to that for dictionaries. -mix up… < it's easy to mix her up with her sister > NPEG - - -it's easy to mix -her up with her sister - - -

-

In addition, some dictionaries make reference to the pronunciation of the headword in the -pronunciation of related entries, variants, or examples. The pRef -element should be used for such references. -hors d'oeuvre -/,aw'duhv (Fr O:r dœvr)/ n, pl hors d'oeuvres also hors -d'oeuvre /'duhv(z) (Fr ~)/ NPEG - -

-hors d'oeuvre -,aw'duhv - -Fr -O:r dœvr -
- -
-pl -hors d'oeuvres -hors d'oeuvre -'duhv(z) - -Fr - - - -
- - -

-

Because headword and pronunciation references can occur virtually anywhere in an entry, -the oRef and pRef elements may appear -within any other element defined for dictionary entries.

-

Since existing printed dictionaries use different conventions for headword references -(swung dash, first letter abbreviated form, capitalization, or italicization of the word, -etc.) the exact method used should be documented in the header.

- - - - - - - - - - -
-
-Typographic and Lexical Information in Dictionary Data -

Among the many possible views of dictionaries, it is useful to distinguish at least the -following three, which help to clarify some issues raised with particular urgency by -dictionaries, on account of the complexity of both their typography and their -information structure. -(a) the typographic view—the -two-dimensional printed page, including information about line and page breaks -and other features of layout -(b) the editorial view—the one-dimensional sequence of tokens -which can be seen as the input to the typesetting process; the wording and -punctuation of the text and the sequencing of items are visible in this view, -but specifics of the typographic realization are not -(c) the lexical view—this view includes the underlying -information represented in a dictionary, without concern for its exact textual -form - -

-

For example, a domain indication in a dictionary entry might be broken over a line and -therefore hyphenated (naut- -ical); the typographic view of the dictionary preserves this information. In a -purely editorial view, the particular form in which the domain name is given in the -particular dictionary (as nautical, rather than naut., Naut., etc.) -would be preserved, but the fact of the line break would not. Font shifts might -plausibly be included in either a strictly typographic or an editorial view. In the -lexical view, the only information preserved concerning domain would be some standard -symbol or string representing the nautical domain (e.g. naut.) regardless of the -form in which it appears in the printed dictionary.

-

In practice, publishers begin with the lexical view—i.e., lexical data as it might -appear in a database—and generate first the editorial view, which reflects editorial -choices for a particular dictionary (such as the use of the abbreviation Naut. -for nautical, the fonts in which different types of information are to be -rendered, etc.), and then the typographic view, which is tied to a specific printed -rendering. Computational linguists and philologists often begin with the typographic -view and analyse it to obtain the editorial and/or lexical views. Some users may -ultimately be concerned with retaining only the lexical view, or they may wish to -preserve the typographic or editorial views as a reference text, perhaps as a guard -against the loss or misinterpretation of information in the translation process. Some -researchers may wish to retain all three views, and study their interrelations, since -research questions may well span all three views.

-

In general, an electronic encoding of a text will allow the recovery of at least one view -of that text (the one which guided the encoding); if editorial and typographic practices -are consistently applied in the production of a printed dictionary, or if exceptions to -the rules are consistently recorded in the electronic encoding, then it is in -principle possible to recover the editorial view from an encoding of the -lexical view, and the typographic view from an encoding of the editorial view. In -practice, of course, the severe compression of information in dictionaries, the variety -of methods by which this compression is achieved, the complexity of formulating -completely explicit rules for editorial and typographic practice, and the relative -rarity of complete consistency in the application of such rules, all make the mechanical -transformation of information from one view into another something of a vexed question.

-

This section describes some principles which may be useful in capturing one or the other -of these views as consistently and completely as possible, and describes some methods of -attempting to capture more than one view in a single encoding. Only the editorial and -lexical views are explicitly treated here; for methods of recording the physical or -typographic details of a text, see chapter . Other approaches to -these problems, such as the use of repetitive encoding and links to show their -correspondences, or the use of feature structures to capture the information structure, -and of the ana and inst attributes to link feature structures to a -transcription of the editorial view of a dictionary, are not discussed here (for -feature structures, see chapter . For linkage of textual form and -underlying information, see chapter ).

-
-Editorial View -

Common practice in encoding texts of all sorts relies on principles such as the -following, which can be used successfully to capture the editorial view when -encoding a dictionary: -All characters of the source text should be retained, with the possible -exception of rendition text (for which see further below). -Characters appearing in the source text should typically be given as -character data content in the document, rather than as the value of an -attribute; again, rendition text may optionally be excepted from this rule. -Apart from the characters or graphics in the source text, nothing else -should appear as content in the document, although it may be given in -attribute values. -The material in the source text should appear in the encoding in the same -order. Complications of the character sequence by footnotes, marginal notes, -etc., text wrapping around illustrations, etc., may be dealt with by the -usual means (for notes, see section ).Complications of sequence caused by marginal or interlinear -insertions and deletions, which are frequent in manuscripts, or by -unconventional page layouts, as in concrete poetry, magazines with -imaginative graphic designers, and texts about the nature of typography -as a medium, typically do not occur in dictionaries, and so are not -discussed here. - - -

-

In a very conservative transcription of the editorial view of a text, rendition -characters (e.g. the commas, parentheses, etc., used in dictionary -entries to signal boundaries among parts of the entry) and rendition -text (for example, conjunctions joining alternate headwords, etc.) are -typically retained. Removing the tags from such a transcription will leave all and -only the characters of the source text, in their original sequence.This is a slight oversimplification. Even in conservative -transcriptions, it is common to omit page numbers, signatures of gatherings, -running titles and the like. The simple description above also elides, for the -sake of simplicity, the difficulties of assigning a meaning to the phrase -original sequence when it is applied to the printed characters of a -source text; the original sequence retained or recovered from a -conservative transcription of the editorial view is, of course, the one -established during the transcription by the encoder. -

-

Consider, for example, the following entry: - pinna (ˈpɪnə) n, pl -nae (-ni:) or --nas 1 any leaflet of a pinnate compound leaf 2 zoology -a feather, wing, fin, or similarly shaped part 3 another name for auricle (2). [C18: via New Latin from Latin: wing, -feather, fin] CED A conservative encoding of the editorial view of this -entry, which retains all rendition text, might resemble the following: - -

-pinna -ˈpɪnə -
- -n, -
-pl - --nae -(-ni:) -
or -nas - -1 any leaflet of a pinnate compound leaf - -2 zoology -a feather, wing, fin, or similarly shaped part - -3 -another name for -auricle (2) - - -[C18: via New Latin from Latin: -wing, feather, -fin] - - -
- - -

-

A somewhat simplified encoding of the editorial view of this entry might exploit the -fact that rendition text is often systematically recoverable. For example, -parentheses consistently appear around pronunciation in this dictionary, and thus -are effectively implied by the start- and end-tags for pron.The omission of rendition text is particularly common in systems -for document production; it is considered good practice there, since automatic -generation of rendition text is more reliable and more consistent than -attempting to maintain it manually in the electronic text. In such an -encoding, removing the tags should exactly reproduce the sequence of characters in -the source, minus rendition text. The original character sequence can be recovered -fully by replacing tags with any rendition text they imply.

-

Encoding in this way, the example given above might resemble the following. The -tagUsage element in the header would be used to record the following -patterns of rendition text: -parentheses appear around pron elements -commas appear before inflected forms -the word or appears before alternate forms -brackets appear around the etymology -full stops appear after pos, inflection information, and sense -numbers -senses are numbered in sequence unless otherwise specified using the -global n attribute - - - -

-pinna -"pIn@ -
- -n - -
-pl - --nae --ni: -
--nas - - -any leaflet of a pinnate compound leaf. - - -Zoology -a feather, wing, fin, or similarly shaped part. - - - -another name for -auricle (sense 2). - - - -C18: via New Latin from Latin: -wing, feather, fin - - - -

-

When rendition text is omitted, it is recommended that the means to regenerate it be -fully documented, using the tagUsage element of the TEI header.

-

If rendition text is used systematically in a dictionary, with only a few mistakes or -exceptions, the global attribute rend may be used on any tag to flag -exceptions to the normal treatment. The values of the rend attribute are -not prescribed, but it can be used with values such as no-comma, -no-left-paren, etc. Specific values can be documented using the -rendition element in the TEI header.

-

In the following (imaginary) example, no left parenthesis precedes the -pronunciation: -biryani or biriani %bIrI"A:nI) any of a -variety of Indian dishes … [from Urdu] This irregularity can be recorded -thus: - -

-biryani -biriani -%bIrI"A:nI -
-any of a variety of Indian dishes … -from Urdu - - - -

-
-
-Lexical View -

If the text to be interchanged retains only the lexical view of the text, there may -be no concern for the recoverability of the editorial (not to speak of the -typographic) view of the text. However, it is strongly recommended that the TEI -header be used to document fully the nature of all alterations to the original data, -such as normalization of domain names, expansion of inflected forms, etc.

-

In an encoding of the lexical view of a text, there are degrees of departure from the -original data: normalizing inconsistent forms like nautical, naut., -Naut., etc., to nautical is a relatively slight alteration; -expansion of delay -ed -ing to delay, delayed, delaying is a more -substantial departure. Still more severe is the rearranging of the order of -information in entries; for example: -reorganizing the order of elements in an entry to show their -relationship, as in clem (klɛm) -or clam vb clems, clemming, clemmed - or clams, clamming, clammed CED where in a strictly lexical view one -might wish to group clem and clam with their respective -inflected forms. -splitting an entry into two separate entries, as in -celi.bacy /"selIb@sI/ n [U] state of living -unmarried, esp as a religious obligation. celi.bate /"selIb@t/ n [C] -unmarried person (esp a priest who has taken a vow not to marry). -OALD For some purposes, this entry might usefully be split into an -entry for celibacy and a separate entry for celibate. - -

-

An encoding which captures the lexical view of the example given in the previous -section might look something like the following. In this encoding: -abbreviated forms have been silently expanded -some forms have been moved to allow related forms to be grouped together -the part of speech information has been moved to allow all forms to be -given together -the cross-reference to auricle has been simplified - - - -

-pinna -"pIn@ - -pl - -pinnae -'pIni: -
-pinnas - - - -n - - -any leaflet of a pinnate compound leaf. - - -Zoology -a feather, wing, fin, or similarly shaped part. - - - - - - - -C18: via New Latin from Latin: -wing, feather, fin - - - -

-

Whether the given dictionary encoding focusses on the lexical view and thus approaches the status of -lexical databases, or uses the typographic/editorial view approach and needs to communicate the -sometimes informally stated values for the particular descriptive features, the issue of interoperability -of the content and of the container objects becomes relevant, in view of the growing -tendency to interlink pieces of information across Internet resources. In such -cases, it becomes crucial to be able to encode the fact that whether the information on, -for instance, the value of the grammatical category of Number is provided as sg., sing., Singular, or -equivalently poj. in Polish, or Ez. in German, etc., what is actually referred to is always the same -grammatical value that can be rendered with a plethora of markers, depending on the publisher, language, or lexicographic tradition. -In order to signal that this variety of surface markers in fact indicate the same -underlying value, it is possible to align them with an external inventory of standardized -values. The TEI provides the att.datcat attribute class for the purpose of aligning grammatical (or indeed any sort of) categories as well as their values -with a reference taxonomy of shared data categories.

-

In the example below, a fragment of the entry for isotope cited -in section is adorned by references to standardized definitions for part -of speech (datcat) and adjective (valueDatcat). Depending -on the status and extent of the dictionary, various strategies may be used to reduce the -redundancy of references. - - -

-isotope -
- -adj - - - - -In the above example, alignment is performed against the CLARIN Concept Registry.

-
-
-Retaining Both Views -

It is sometimes desirable to retain both the lexical and the editorial view, in which -case a potential conflict exists between the two. When there is a conflict between -the encodings for the lexical and editorial views, the principles described in the -following sections may be applied.

-
-Using Attribute Values to Capture Alternate Views -

If the order of the data is the same in both views, then both views may be -captured by encoding one dominant view in the character -data content of the document, and encoding the other using attribute values on -the appropriate elements. If all tags were to be removed, the remaining -characters would be those of the dominant view of the text.

-

The attribute class att.lexicographic (which -includes the attributes norm and org from class att.lexicographic.normalized) -is used to provide attributes for use in encoding multiple views of the same dictionary -entry. These attributes are available for use on all elements defined in this -chapter when the base module for dictionaries is selected.

-

When the editorial view is dominant, the following attributes may be used to -capture the lexical view: - - -

-

When the lexical view is dominant, the following attributes may be used to record -the editorial view: - - - -

-

One attribute is useful in either view: - - -

-

For example, if the source text had the domain label naut., it might be -encoded as follows. With the editorial view dominant: -naut. - The lexical view of the same label would transcribe the normalized form -as content of the usg element, the typographic form as an attribute -value: -nautical - -

-

If the source text gives inflectional information for the verb -delay as delay, -ed, -ing, it might usefully be -expanded to delayed, delayed, delaying. An encoding of the editorial view -might take this form: -

-delay - --ed - - -
--ing - - - - Note the use of the tns tag with null content, to enable the -representation of implicit information even though it has no print realization.

-

The lexical view might be encoded thus: -

-delay - -delayed -pst -pstp -
-
-delaying -prsp -
- - -

- - - -

A particular problem may be posed by the common practice of presenting two -alternate forms of a word in a single string, by marking some parts of the word -as optional in some forms. The following entry is for a word which can be -spelled either thyrostimuline or thyréostimuline: -thyr(é)ostimuline [tiR(e)ostimylin] … With the -editorial view dominant, this entry might begin thus: -

-thyr(é)ostimuline -tiR(e)ostimylin -
- - -With the lexical view dominant, however, two orth and -two pron elements would be encoded, in order to disentangle the two -forms; the orig attribute would be used to record the typographic -presentation of the information in the source. -
-thyrostimuline -tiRostimylin -
-
-thyréostimuline -tiReostimylin -
- - -

- -

This example might also be encoded using the opt attribute combined -with the attributes next and prev defined in chapter . -

-thyr -é -ostimuline -tiR -e -ostimylin -
- -

-

Note that this transcription preserves both the lexical and -editorial views in a single encoding. However, it has the disadvantage -that the strings corresponding to entire words do not appear in the -encoding uninterrupted, and therefore complex processing is required -to retrieve them from the encoded text. The use of the opt -attribute is recommended, however, when long spans of text are -involved, or when the optional part contains embedded tags.

- -

For example, the following gives two definitions in one text: -picture drawn with coloured chalk made into crayons, and -coloured chalk made into crayons: - pas.tel /"pastl US: pa"stel/ n -1 (picture drawn with) coloured chalk made into crayons. 2… OALD

A simple encoding solution -would be to leave the definition text unanalysed, but this might be -felt inadequate since it does not show that there are two -definitions. A possible alternative encoding would be: coloured -chalk made into crayons picture drawn with coloured chalk -made into crayons

This transcribes -some characters of the source text twice, however, which deviates from -the usual practice. The following encoding records both the editorial -and lexical views: - picture drawn -with coloured chalk made into -crayons

- -
-
-Recording Original Locations of Transposed Elements -

The attributes described in the previous section are useful only when the order -of material is the same in both the editorial and the lexical view. When the two -views impose different orders on the data, the standard linking mechanisms may be used to -show the original location of material transposed in an encoding of the lexical -view.

-

If the original is only slightly modified, the anchor element may be -used to mark the original location of the material, and the location -attribute may be used on the lexical encoding of that material to indicate its -original location(s). Like those in the preceding section, this attribute is -defined for the attribute class att.lexicographic: - - -

-

For example: -pinna - (ˈpɪnə) n, pl - -nae (-ni:) or -nas CED - -

-pinna -ˈpɪnə - - -pl - --nae --ni: - --nas - - - -n - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

-
-
- -
-
-Unstructured Entries - -

The content model for the entry element provides an entry -structure suitable for many average dictionaries, as well as many -regular entries in more exotic dictionaries. However, the structure -of some dictionaries does not allow the restrictions imposed by the -content model for entry. To handle these cases, the -entryFree and dictScrap elements are provided to -support much wider variation in entry structure. The -dictScrap element offers less freedom, in that it can only -contain phrase level elements, but it can itself appear at any point -within a dictionary entry where any of the structural components of a -dictionary entry are permitted. As such, it acts as a container for -otherwise anomalous parts of an entry.

- -

The entryFree element places no constraints at all upon -the entry: any element defined in this chapter, as well as all the -normal phrase-level and inter-level elements, can -appear anywhere within it. With the entryFree element, the -encoder is free to use any element anywhere, as well as to use or omit -grouping elements such as form, gramGrp, etc.

- -

The entryFree element allows the encoding of entries which -violate the structure specified for the entry element. For -example, in the following entry from a dictionary already in -electronic form, it is necessary to include a pron element -within a def. This is not permitted in the content model for -entry, but it poses no problem in the entryFree -element. demi|god "demIgQd one who is partly divine and partly human -(in Gk myth, etc) the son of a god and a mortal woman, -egHercules "h3:kjUli:z - ]]> - - -

-demigod -demi|god -"demIgQd -
- -n - -one who is partly divine and partly human -(in Gk myth, etc) the son of a god and a mortal woman, eg -Hercules -"h3:kjUli:z - - -

-

The entryFree element also makes it possible to transcribe a dictionary using -only phrase-level (atomic) elements—that is, using no grouping -elements at all. This can be desirable if the encoder wants a completely -flat view, with no indication of or commitment to the association -of one element with another. The following encoding uses no grouping elements, and keeps -all rendition text: - biryani or biriani - (ˌbɪrɪˈa:nɪ) n any of a variety of Indian dishes … [from -Urdu] CED - - -biryani or biriani -(ˌbɪrɪˈa:nɪ) -any of a variety of Indian dishes … -[from Urdu] - - -

-

Here is an alternative way of representing the same structure, this time using -dictScrap: - - -biryani or biriani -(ˌbɪrɪˈa:nɪ) -any of a variety of Indian dishes … -[from Urdu] - - - -

-
-
- The Dictionary Module -

The module defined in this chapter makes available the following - components: - - Dictionaries - Dictionaries - Dictionnaires - 紙本字典 - Dizionari a stampa - Dicionários impressos - 辞書モジュール - - - The selection and combination of modules to form a TEI schema is - described in .

-
-
diff --git a/P5/Source/Guidelines/fr/DI-PrintDictionaries.xml b/P5/Source/Guidelines/fr/DI-PrintDictionaries.xml new file mode 120000 index 0000000000..62b981ca5b --- /dev/null +++ b/P5/Source/Guidelines/fr/DI-PrintDictionaries.xml @@ -0,0 +1 @@ +../en/./DI-PrintDictionaries.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/DR-PerformanceTexts.xml b/P5/Source/Guidelines/fr/DR-PerformanceTexts.xml deleted file mode 100644 index 88741a884c..0000000000 --- a/P5/Source/Guidelines/fr/DR-PerformanceTexts.xml +++ /dev/null @@ -1,1456 +0,0 @@ - - - - - - - -
Performance Texts -

This module is intended for use when encoding printed dramatic -texts, screen plays or radio scripts, and written transcriptions of any -other form of performance. -

-

Section discusses elements such as cast lists, -which can appear only in the front or back matter of printed dramatic -texts. Section discusses the structural -components of performance texts: these include major structural -divisions such as acts and scenes (section ); -individual speeches (section ); groups of -speeches (section ); stage directions -(section ); and the elements making up individual -speeches (section ). Section -discusses ways of encoding units which cross the simple hierarchic -structure so far defined, such as embedded songs or masques. -Finally, section discusses a small number of -additional elements characteristic of screen plays and radio or -television scripts, as well as some elements for representing -technical stage directions such as lighting or blocking.

- -

The default structure for dramatic texts is similar to that -defined by chapter , as further discussed in -section .

- -

Two element classes are used by this module. -The model.frontPart.drama class supplies -specialized elements which can appear only in the front or back matter -of performance texts. The model.stageLike -class supplies a set of elements for stage directions and similar -items such as camera movements, which can occur between or within -speeches.

- - - - - -
Front and Back Matter - -

In dramatic texts, as in all TEI-conformant documents, the header -element is followed by a text element, which contains optional -front and back matter, and either a body or else a -group of nested text elements. For more information -on these, see chapter . -

-

The front and back elements are most likely to be -of use when encoding preliminary materials in published performance -texts. When the module defined by this chapter is included in a -schema, the following additional elements not generally -found in other forms of text become available as part of the front or -back matter: - -

- -

Elements for encoding each of these specific kinds of front matter -are discussed in the remainder of this section, in the order given -above. In addition, the front matter of dramatic texts may include -the same elements as that of any other kind of text, notably title -pages and various kinds of text division, as discussed in section . The encoder may choose to ignore the specialized -elements discussed in this section and instead use constructions of -the type div type="performance" or div1 -type="set". -

- -

Most other material in the front matter of a performance text will be -marked with the default text structure elements described in chapter -. For example, the title -page, dedication, other commendatory material, preface, etc., in a -printed text should be encoded using div or div1 -elements, containing headings, paragraphs, and other core tags. -

- - - - - - - -
The Set Element -

A special form of note describing the setting of a dramatic text -(that is, the time and place of its action) is sometimes found in the -front matter. - -Descriptions of the setting may also appear as initial stage directions -in the body of the play, but such descriptions should be marked as stage -directions, not set. The set element should be used -only where the description forms part of the front matter, as in the -following examples: - - - ... - -

The action of the play is set in Chicago's - Southside, sometime between World War II and the - present.

- - - - Peer Gynt - -
-
-
-
- Note on the Translation -

...

-
-
- Characters - -
-

The action, which opens in the beginning of the nineteenth - century, and ends around the 1860s, takes place partly in - Gudbrandsdalen, and on the mountains around it, partly on the coast - of Morocco, in the desert of Sahara, in a madhouse at Cairo, at sea, - etc.

 -

- - -

- - - - - -
-
Prologues and Epilogues -

Many plays in the Western tradition include in their front matter a -prologue, spoken by an actor, generally not in character. Similar -speeches often also occur at the end of the play, as epilogues. The -elements prologue and epilogue are provided for the -encoding of such features within the front or back matter, where -appropriate. - -A prologue may be encoded just like a distinct poem, as in the following -example: - - - Prologue, spoken by Mr. Hart - Poets like Cudgel'd Bullys, never do - At first, or second blow, submit to you; - But will provoke you still, and ne're have done, - Till you are weary first, with laying on: - We patiently you see, give up to you, - Our Poets, Virgins, nay our Matrons too. - - - The Persons - ... - - The SCENE -

London

- - - - -

-

A prologue or epilogue may also be encoded as a speech, using the -sp element described in section . This is -particularly appropriate where stage directions, etc., are involved, as -in the following example: - - Written by Colley Cibber, Esq - and spoken by Mrs. Cibber - - - Since Fate has robb'd me of the hapless Youth, - For whom my heart had hoarded up its truth; - By all the Laws of Love and Honour, now, - I'm free again to chuse, — and one of you - - - Suppose I search the sober Gallery; — No, - There's none but Prentices — & Cuckolds all a row: - And these, I doubt, are those that make 'em so. - - Pointing to the Boxes. - - 'Tis very well, enjoy the jest: - - - - -

-

In cases where the prologue or epilogue is clearly a significant part -of the dramatic action, it may be preferable to include it in the body -of a text, rather than in the front or back matter. In such cases, the -encoder (and theatrical tradition) will determine whether or not to -regard it as a new scene or division, or simply the final speech in the -play. In the First Folio version of Shakespeare's -Tempest, for example, Prospero's final speech is clearly -marked off as a distinct textual unit by the headings and layout of the -page, and might therefore be encoded as back matter: - - - - - I'le deliver all, - And promise you calme Seas, auspicious gales, - Be free and fare thou well: please you, draw neere. - Exeunt omnes. - - - - - - Epilogue, spoken by Prospero. - - Now my Charmes are all ore-throwne, - And what strength I have's mine owne - As you from crimes would pardon'd be, - Let your Indulgence set me free. - Exit - - -

The Scene, an un-inhabited Island.

- - - Names of the Actors. - Alonso, K. of Naples - Sebastian, his Brother. - Prospero, the right Duke of Millaine. - - FINIS - - - -

-

In many modern editions, the editors have chosen to regard -Prospero's speech as a part of the preceding scene: - - Prospero - I'll deliver all, - And promise you calm seas, auspicious gales, - Be free and fare thou well. Exit Ariel - Please you, draw near. Exeunt all but Prospero - Epilogue - Now my charms are all o'erthrown, - And what strength I have's mine own - As you from crimes would pardoned be, - Let your indulgence set me free. - -He awaits applause, then exit. - - -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-
Records of Performances -

Performance texts are not only printed in books to be read, they are -also performed. It is common practice therefore to include within the -front matter of a printed dramatic text some brief account of particular -performances, using the following element: - -The performance element may be used to group any and all -information relating to the actual performance of a play or screenplay, -whether it specifies how the play should be performed in general or how -it was performed in practice on some occasion. -

-

Performance information may include complex structures such as cast -lists, or paragraphs describing the date and location of a performance, -details about the setting portrayed in the performance and so forth. -(See the discussion of these specialized structures in section above.) If -information for more than one performance is being recorded, then more -than one performance element should be used, wherever possible. -

-

Names of persons, places, and dates of particular significance within -the performance record may be explicitly marked using the general -purpose name, rs type="place" and date -elements described in section . -No particular elements for such features as stagehouses, -directors, etc., are proposed at this time. -

-

For example: - - Death of a Salesman -

A New Play by Arthur Miller

-

Staged by Elia Kazan

- - Cast - (in order of appearance) - - Willy Loman - Lee J. Cobb - - - Linda - Mildred Dunnock - - - Biff - Arthur Kennedy - - - Happy - Cameron Mitchell - - - -

The setting and lighting were designed by - Jo Mielziner.

-

The incidental music was composed by Alex North.

-

The costumes were designed by Julia Sze.

-

Presented by Kermit Bloomgarden - and Walter Fried at the - Morosco Theatre in New York on - February 10, 1949.

- - - - - - -Or: - -

La Machine Infernale a été - représentée pour la première fois au - théâtre Louis-Jouvet - (Comédie des - Champs-élysées) le 10 avril 1934, - avec les décors et les costumes de - Christian Bérard. ...

- - -

- - - - - - - - - - - - - - - -
-
Cast Lists -

A cast list is a specialized form of list, -conventionally found at the start or end of a play, usually listing all -the speaking and non-speaking roles in the play, often with additional -description (Cataplasma, a maker of Periwigges and Attires) or -the name of an actor or actress (Old Lady Squeamish. Mrs -Rutter). Cast lists may be encoded with the general purpose -list element described in section , but for -more detailed work the following specialized elements are provided: - -

A castItem element may contain any mixture of elements -taken from the model.castItemPart class, -members of which (when this module is included) are: - - -Cast lists often have an internal structure of their own; it is quite -usual to find, for example, nobility and commoners, or male and female -roles, presented in different groups or sublists. Roles are also often -grouped together by their function, for example: - -Sons of Cato: - -Portius -Marcus -

-

A cast list relating to a specific performance may be accompanied by -notes about the time or place of that performance, indicating (for -example) the name of the theatre where the play was first presented, the -name of the producer or director, and so forth. When the cast list -relates to a specific performance, it should be embedded within a -performance element (see section ), as in -the following example: - -

The first performance in Great Britain of Waiting for - Godot was given at the Arts Theatre, London, on - 3rd August 1955. It was directed by - Peter Hall, and the décor was by Peter - Snow. The cast was as follows:

- - Estragon: Peter Woodthorpe - Vladimir: Paul Daneman - ... - - - -

-

In this example, the castItem elements have no substructure. -If desired, however, their components may be more finely distinguished -using the elements role, roleDesc, and actor. -For example, the second cast item above might be encoded as follows: - - Vladimir: - Paul Daneman - -

-

The ref attribute on actor may be used to associate the name -with information about the real-world person identified, as further discussed in section ND. In the previous example, -we might associate the name of Paul Daneman with his entry in a widely used bibliography as follows : - - Paul Daneman -

-

The global xml:id attribute may be used to specify a unique -identifier for the role element, where it is desired to link -speeches within the text explicitly to the role, using the -who attribute, as further discussed in section below. -

-

The occasionally lengthy descriptions of a role sometimes found in -written play scripts may be marked using the roleDesc element, -as in the following example: - - Tom Thumb the Great - a little hero with a great soul, something violent in his - temper, which is a little abated by his love for Huncamunca - Young Verhuyk - - -For non-speaking or un-named roles, a castItem may contain a -roleDesc without an accompanying role, for example - - Costermonger - -

-

When a list of such minor roles is given together, the -type attribute of the castItem should indicate that -it contains more than one role, by taking a value such as list. The encoder may or may not elect to -encode each separate constituent within such a composite -castItem. Thus, either of the following is acceptable: -Constables, Drawer, Turnkey, etc. - - Constables, - Drawer, - Turnkey, - etc. - -

-

A group of cast items forming a distinct subdivision of a cast list -may be marked as such by using the special purpose castGroup -element. The rend attribute may be used to indicate -whether this grouping is indicated in the text by layout alone (i.e. the -use of whitespace), by long braces or by some other means. A -castGroup may contain an optional heading (represented as -usual by a head element) followed by a series of -castItem elements: - - friends of Mathias - - Walter - Mr Frank Hall - - - Hans - Mr F.W. Irish - - - -

-

Alternatively, the encoder may prefer to regard the phrase -friends of Mathias as a role description, and encode the above -example as follows: - - friends of Mathias - - Walter - Mr Frank Hall - - - Hans - Mr F.W. Irish - - -

-

This version has the advantage that all role descriptions are treated -alike, rather than in some cases being treated as headings. On the -other hand there are also cases, such as the following, where the -role description does function more like a heading: - - - - Mendicants - Aafaa Femi Johnson - Blindman Femi Osofisan - Goyi Wale Ogunyemi - Cripple Tunji Oyelana - - Si Bero - Sister to Dr Bero - Deolo Adedoyin - - Two old women - Iya Agba Nguba Agolia - Iya Mate Bopo George - - Dr Bero - Specialist - Nat Okoro - Priest Gbenga Sonuga - The old man - Bero's father - Dapo Adelugba - - -

- - - - - - - - -
-
-
The Body of a Performance Text -

The body of a performance text may be divided into structural -units, variously called acts, scenes, stasima, entr'actes, etc. All -such formal divisions should be encoded using an appropriate -text-division element (div, div1, div2, -etc.), as further discussed in section . -Whether divided up into such units or not, all performance texts -consist of sequences of speeches (see ) and stage -directions (see ). In musical performances, it -is also common to identify groups of speeches which act as a single -unit, sometimes called a number; such units typically -float within the structural hierarchy at the same level as speeches -preceding or following them and cannot therefore be treated as -text-divisions. (see ). Speeches will generally -consist of a sequence of chunk-level items: paragraphs, -verse lines, stanzas, or (in case of uncertainty as to whether -something is verse or prose) ab elements (see ).

-

The boundaries of formal units such as verse lines or paragraphs do -not always coincide with speech boundaries. Units such as songs may be -discontinuous or shared among several speakers. As described below in -section , such fragmentation may be encoded in a -relatively simple fashion using the linkage and aggregation mechanisms -defined in chapter .

-
Major Structural Divisions -

Large divisions in drama such as acts, scenes, stasima, or entr'actes -are indicated by numbered or unnumbered div elements, as -described in section . The type and -n attributes may be used to define the type of division being -marked, and to provide a name or number for it, as in the following -example: - - - Night—Faust's Study (i) - - - Outside the City Gate - - -

-

Where the largest divisions of a performance text are themselves -subdivided, most obviously in the case of plays traditionally divided -into acts and scenes, further nested text-division elements may be used, -as in this example: - - - Act One - - Pa Ubu, Ma Ubu - Pa Ubu

Pschitt!

- - - A room in Pa Ubu's house, where a magnificent - collation is set out - - - - Act Two - - Scene One - - - Scene Two - - - -

-

In the example above, the div2 element has been used to -represent the French scene convention, (where the -entrance of each new set of characters is marked as a distinct unit in -the text) and the div1 element to represent the acts into which -the play is divided. The elements chosen are determined only by the -hierarchic position of these units in the text as a whole. If the text -had no acts, but only scenes, then the scenes might be represented by -div1 elements. Equally, if a play is divided only into -acts, with no smaller subdivisions, then the div1 -element might be used to represent acts. The type should be -used, as above, to make explicit the name associated -with a particular category of subdivision.

-

As an alternative to the use of numbered -divisions, the encoder may represent all subdivisions with the same -element, the unnumbered div. The second -act in the above example would then be represented as follows: -

- Act Two -
- Scene One -
-
- Scene Two -
-

-

For further discussion of the use of numbered and unnumbered -divisions, see section .

-
Speeches and Speakers -

The following elements are used to identify speeches and speakers in -a performance text: -

-

As noted above, the structure of many performance texts may be -analysed as multiply hierarchic: a scene of a verse play, for example, -may be divided into speeches and, at the same time, into verse lines. -The end of a line may or may not coincide with the end of a speech, and -vice versa. Other structures, such as songs, may be discontinuous or -split up over several speeches. For some purposes it will be -appropriate to regard the verse-structure as the fundamental organizing -principle of the text, and for others the speech structure; in some -cases, the choice between the two may be arbitrary. The discussion in -the remainder of this chapter assumes that it is the speech-based -hierarchy which most prominently determines the structure of performance -texts, but the same mechanisms could be employed to encode a view of a -performance text in which individual speeches were entirely subordinate -to the formal units of prose and verse. For more detailed discussion and -examples of various treatments of this fundamental issue, refer to -chapter .

-

The who attribute and the speaker element are -both used to indicate the speaker or speakers of a speech, but in -rather different ways. The speaker element is used to encode -the word or phrase actually used within the source text to indicate -the speaker: it may contain any string or prefix, and may be thought -of as a highly specialized form of stage direction. The -who attribute however contains one or more pointer values, -each of which indicates one or more other XML elements documenting the -character to whom the speech is assigned. Typically, this attribute -might point to a person element in the TEI header , to a role element in the cast list , or even to some external source such as an online -handbook of dramatic roles. The most usual case is that the pointer -value supplied (prefixed by a sharp sign) corresponds with the value -of an xml:id attribute, -used elsewhere in the document to identify a particular element, as in the following examples: - - - Menaechmus - Peniculus - - Menaechmus - Responde, adulescens, quaeso, quid nomen tibist? - Peniculus - Etiam derides, quasi nomen non noveris? - Menaechmus - Non edepol ego te, quot sciam, umquam ante hunc diem - Vidi neque novi; ... -

-

If present, a speaker element may only appear as the first -part of an sp element. The distinction between the -speaker element and the who attribute makes it -possible to encode uniformly characters whose names are not indicated in -a uniform fashion throughout the play, or characters who appear in -disguise, as in the following examples: - - Henry Higgins - - - The Notetaker -

...

- -

-

If the speaker attributions are completely regular (and may thus be -reconstructed mechanically from the values given for the who -attribute), or are of no interest for the encoder of the text (as might -be the case with editorially supplied attributions in older texts), then -the speaker element need not be used; the former example above -then might look like this: - - Menaechmus - Peniculus - -Responde, adulescens, quaeso, quid nomen tibist? -Etiam derides, quasi nomen non noveris? -Non edepol ego te, quot sciam, umquam ante hunc diem - Vidi neque novi; ... -

-

More than one identifier may be listed as value for the who -attribute if the speech is spoken by more than one person, as in the -following example: - - - Nano - Castrone - - Nano and Castrone sing - - Fools, they are the only nation - Worth men's envy or admiration - - -

-

In the event there is a speech that is assigned to a -character that is not listed in the source cast list, a -castList may be encoded inside the standOff -element to provide an element to which the who of -sp may point.

-

The sp and speaker elements are both declared -within the core module (see section ).

- -
Grouped Speeches -

This module makes available the following additional element for -handling groups of speeches:

-

The spGrp element is intended for cases where -the characters in a performance launch into something which might be -regarded almost as a kind of separate structural division, typically -associated with its own heading or numbering system, but which -floats in the text, at the same hierarchic level -as speeches preceding or following it. Such units are often numbered, -titled, and visually presented as distinct objects within the -text. Here is a typical example from a well-known American musical comedy: - -By Strauss : performed by Georges Guetary, Gene Kelly, and Oscar -Levant -HENRI BAUREL -The waltzes of Mittel Europa -They charm you and warm you within -While each day discloses -What Broadway composes -Is emptiness pounding on tin. - - -JERRY MULLIGAN: ADAM COOK: -Mein Herr! -Mein Herr! -Bitte, bitte! -Denke, danke! -Aufwiedersehen! Aufwiedersehen! - -HENRI BAUREL: -How can I be civil -When hearing this drivel? -It's only for night-clubbing souses. -Oh give me the free 'n easy -Waltz that is Viennes-y -And go tell the band -If they want a hand -The waltz must be Strauss's - -ALL -Ya ya ya -Give me oom pah pah... - - - -

-
-
Stage Directions -

Both between and within the speeches of a written performance text, -it is normal practice to include a wide variety of descriptive -directions to indicate non-verbal action. The following elements are -provided to represent these: - - - -

-

A satisfactory typology of stage directions is difficult to define. -Certain basic types such as entrance, exit, -setting, delivery, are easily identified. But the list is -not a closed one, and it is not uncommon to mix types within a single -direction. No closed set of values for the type attribute is -therefore proposed at the present time, though some suggested values are -indicated in the list below, which also indicates the range of -possibilities. -The throne descends. -Music -Enter Husband as being thrown off his horse. -Exit pursued by a bear. -He quickly takes the stone out. -To Lussurioso. -Aside. -Not knowing what to say. -Disguised as Ansaldo. -At a window. -Having had enough, and embarrassed - for the family.

-

The meaning of the values used for the type attribute on -stage elements may be defined within the tagUsage -element of the TEI header (described in section ). -For example: -This element is used for all stage directions, - editorial or authorial. The type attribute on this element takes - one or more of the following values: - - - describes the set - - describes movement across stage, position, etc. - - describes movement other than blocking - - describes how the line is said - - describes character's emotional state or through line - -

-

This approach is purely documentary; in a real project it would generally be more effective to define the range of -permitted values explicitly within the project's schema specification, -using the techniques described in chapter . For -example, a specification like the following might be used to produce a -schema in which the type attribute of the -stage element is permitted to take only the values listed -above: - - - - - - - - - - - -describes the set -describes movement across stage, position, etc. -describes movement other than blocking -describes how the line is said -describes character's emotional state or through line - - - -

-

The stage element may appear both between and within -sp elements. It may contain a mixture of phrase level -elements, possibly combined into paragraphs, as in the following -example: - - -

Scene. — A room furnished comfortably and -tastefully but not extravagantly ... -The floor is carpeted and a fire burns in the stove. -It is winter.

-

A bell rings in the hall; shortly afterwards the -door is heard to open. Enter NORA humming a tune ...

- -Nora -

Hide the Christmas Tree carefully, Helen. Be sure the -children do not see it till this evening, when it is -dressed. To the PORTER taking -out her purse How much?

- - -

-

The stage element may also be used in non-theatrical -texts, to mark sound effects or musical effects, etc., as further -discussed in section .

-

The move element is intended to help overcome the fact that -the stage directions of a printed text may often not provide full -information about either the intended or the actual movement of actors -on stage. It may be used to keep track of entrances and exits in -detail, so as to know which characters are on stage at which time. Its -attributes permit a relatively formal specification for movements of -characters, using user-defined codes to identify the characters involved -(the who attribute), the direction of the movement -(type attribute), and optionally which part of the stage is -involved (where attribute). For stage-historical purposes, a -perf attribute is also provided; this allows the recording of -different move elements -as taken in different performances of the same text.

-

The move element should be located at the position in the -text where the move is presumed to take place. This will often coincide -with a stage direction, as in the following simple example: - -Bellafront - - - Enter Bellafront mad.

-

The move element can however appear independently of a stage -direction, as in the following example: - -Lady Macbeth -First Gentleman - - Gent. -

Neither to you, nor any one; having no witness -to confirm my speech. -Lo you! here she comes. This is her very guise; and, -upon my life, fast asleep.

-

- - - - -
-
Speech Contents -

The actual speeches of a dramatic text may be composed of running -text, which must be formally organized into paragraphs, in the case of -prose (see section ), verse lines or line groups in -that of verse (see section ), or seg -elements, in case of doubt as to whether the material should be treated -as verse or prose. The following elements, all of which are defined in -the core, are particularly useful when marking units of prose or verse within -speeches: -

-

Like other milestone elements, the element lb additionally bears the attributes -ed and edRef, from its membership in the class -att.edition: - - - -

-

As a member of the classes att.typed -and att.divLike, the -lg element -also bears the following attributes: - - - - -

- -

When the verse module is included in a -schema, the elements l -and lg also gain additional attributes through their -membership of the class att.metrical: - -

- - -

In many texts, prose and verse may be inextricably mingled; -particularly in earlier printed texts, prose may be printed as verse or -verse as prose, or it may be impossible to distinguish the two. In -cases of doubt, an encoder may prefer to tag the dubious material -consistently as verse, to tag it all as prose, to follow the typography -of the source text, or to use the neutral ab -element to contain the speech itself. When this question arises, the -tagUsage element in the encodingDesc element of the -header may be used to record explicitly what policy has been adopted.

-

Even where they can reliably be distinguished, a single speech may frequently -contain a mixture of prose (marked as p) and verse (marked as -l or—if stanzaic—lg).

- -

The part attribute which both l and lg -elements inherit from the att.fragmentable class provides one simple way of indicating where the boundaries of a -speech and of a verse line or line group do not coincide. The encoder -may simply indicate that a line or line group is metrically incomplete by -specifying the value Y or N, as in the following example: -FaceYou most -notorious whelp, you insolent slave -Dare you do this? -SubtleYes faith, yes faith. -FaceWhy! Who -Am I, my mongrel? Who am I? -SubtleI'll tell you, - -

-

Alternatively, where the fragments of the line or line group are -consecutive in the text (though possibly interrupted by stage -directions), the values I (initial), M (medial), and F (final) -may be used to indicate how metrical lines are constituted: - FaceYou most -notorious whelp, you insolent slave -Dare you do this? -SubtleYes faith, yes faith. -FaceWhy! Who -Am I, my mongrel? Who am I? -SubtleI'll tell you, - - -

-

In dramatic texts, the lg or line group element is most -often of use for the encoding of songs and other stanzaic material. Line groups may be fragmented -across speakers in the same way as individual lines, and the same set of -attributes may be used to record this fact. The element -spGrp is provided in order to simplify the situation, very -common in performances, where performance of a single entity, such as -a song, is shared amongst several performers, as in the following -example: - -Song — Sir Joseph - - I am the monarch of the sea, - The ruler of the Queen's Navee. - Whose praise Great Britain loudly chants. - - - Cousin Hebe - And we are his sisters and his cousins and his aunts! - - - Rel. - And we are his sisters and his cousins and his aunts! - - - - -

-

This encoding however does not indicate that the three lines of -Sir Joseph's song and the two lines following it together constitute a -single verse stanza. This can be indicated by using the part -attribute, as follows: - -Song — Sir Joseph - - I am the monarch of the sea, - The ruler of the Queen's Navee. - Whose praise Great Britain loudly chants. - - - Cousin Hebe - And we are his sisters and his cousins and his aunts! - - - Rel. - And we are his sisters and his cousins and his aunts! - - - - -

-
-
Embedded Structures -

Although primarily composed of speeches, performance texts often -contain other structural units such as songs or strophes which are -shared among different speakers. More generally, complex nested -structures of plays within plays, interpolated masques, or interludes -are far from uncommon. In more modern material, comparably complex -structural devices such as flashback or nested playback are equally -frequent. In all kinds of performance material, it may be necessary to -indicate several actions which are happening simultaneously.

-

A number of different devices are available within the TEI scheme to -support these complexities in the general case. Texts may be composite -or self-nesting (see section ) and multiple -hierarchies may be defined (see chapter ). The TEI -encoding scheme provides a variety of linking mechanisms, which may be -used to indicate temporal alignment and aggregation of fragmented -structures. In this section we provide a few specific examples of the -application of these techniques to performance texts: - -the use of the floatingText element -the use of the part attribute on fragmentary -lg elements -the use of the next and prev attributes on -fragments of embedded structures to join them into a larger whole -the use of the join element to define a -virtual element composed of the fragments -indicated -

-

When the whole of a song appears within a single speech, it may -require no special treatment if it is considered to form a part -of the speech: Kelly - (calmly). -

Aha, so you've bad minds along with th' love of gain. - You thry to pin on others th' dirty decorations that - may be hangin' on your own coats.

- (He points, one after the other at Conroy, Bull, - and Flagonson. Lilting) - - Who were you with last night? - Who were you with last night? - Will you tell your missus when you go home - Who you were with last night? - -Flagonson - (in anguished indignation). -

This is more than a hurt to us: this hits at the - decency of the whole nation!

- -If however, the song is to be regarded as forming a distinct item, -perhaps with its own front and back matter, it may be better to regard -it as a floating text: -Kelly - (calmly). -

Aha, so you've bad minds along with ...

 - (He points, one after the other at Conroy, Bull, - and Flagonson. Lilting): - - - Kelly's Song - - - Who were you with last night? - Who were you with last night? - Will you tell your missus when you go home - Who you were with last night? - - -

-

When an embedded structure extends across more than one sp -element, each of its constituent parts must be regarded as a distinct -fragment; the problem then facing the encoder is to reconstitute the -interrupted whole in some way.

-

As already noted above, the spGrp element may be used to -group together consecutive speeches which are grouped together in some -way, for example constituting a single song. Alternatively the -part attribute, typically used to -indicate that an l element contains a partial, not a complete, -verse line, may also be used on the lg element, -to indicate that the line group is partial rather than complete, thus: -Kelly - (wheeling quietly in his semi-dance, - as he goes out): - - Goodbye to holy souls left here, - Goodbye to man an' fairy; - - -Widda Machree - (wheeling quietly in her semi-dance, - as she goes out): - - Goodbye to all of Leicester Square, - An' the long way to Tipperary. - -

-

When the fragments of a song are separated by other intervening -dialogue, or even when not, they may be linked together with the -next and prev attributes defined in section -. -For example, the line groups making up Ophelia's song -might be encoded as follows: - - - Elsinore. A room in the Castle. - Enter Ophelia, distracted. - Ophelia -

Where is the beauteous Majesty of Denmark?

- - Queen -

How now, Ophelia?

- - Ophelia - Singing - - How should I your true-love know - From another one? - By his cockle hat and staff - And his sandal shoon. - - - Queen -

Alas, sweet lady, what imports this song?

- - Ophelia -

Say you? Nay, pray you mark.

- Sings - - He is dead and gone, lady, - He is dead and gone; - At his head a grass-green turf, - At his heels a stone. - -

O, ho!

- - -

-

The next and prev attributes are discussed in -section : they form part of the module -for alignment and linking; this module must therefore be included in a -schema if they are to be used, as further discussed in section .

-

The fragments of Ophelia's song might also be linked together using -the join mechanism described in section . -The join element is specifically intended to encode the fact -that several discontiguous elements of the text together form one -virtual element. Using this mechanism, the example -might be encoded as follows: - - - - - Elsinore. A room in the Castle. - Queen -

How now, Ophelia?

- - Ophelia - Singing - - How should I your true-love know - From another one? - By his cockle hat and staff - And his sandal shoon. - - - Queen -

Alas, sweet lady, what imports this song?

- - Ophelia -

Say you? Nay, pray you mark.

- Sings - - He is dead and gone, lady, - He is dead and gone; - At his head a grass-green turf, - At his heels a stone. - -

O, ho!

- - - - - - -The location of the join element is not significant; here it -has been placed shortly after the conclusion of the song, in order to -have it close to the fragments it unifies.

-

Like the next and prev attributes, the -join element requires the additional module for linking, which -is selected as shown above.

-
Simultaneous Action -

In printed or written versions of performance texts, a variety of -techniques may be used to indicate the temporal alignment of speeches or -actions. Speeches may be printed vertically aligned on the page, or -braced together; stage directions (e.g. Speaking at the same -time) are also often used. In operatic or musical works in -particular, the need to indicate timing and alignment of individual -parts of a song may lead to very complex layout.

-

One simple method of indicating the temporal alignment of speeches or -actions is to use the spGrp element discussed in -section , with a type attribute to specify the -reason for grouping, as in the following example: - Mangan - wildly -

Look here: I'm going to take off all my clothes.

- he begins tearing off his coat. - - - Lady Utterword -

Mr Mangan!

- - Captain Shotover -

Whats that?

- - Hector -

Ha! ha! Do. Do.

- - Ellie -

Please dont.

- -in consternation - - Mrs. Hushabye - catching his arm and stopping him -

Alfred: for shame! Are you mad?

-

- - - - -

In the original, the stage direction in consternation is -printed opposite a brace grouping all four speeches, indicating that all -four characters speak at once, and that the stage direction applies to -all of them. Rather than attempting to represent the appearance of the -source, this example encoding represents its presumed meaning: the -stage element is placed arbitrarily after the last relevant -speech, and the four speeches with which it is to be associated are -grouped by means of the spGrp element. The rend -attribute is used to specify the fact that the three speeches were -grouped by the brace in the copy text. Producing a readable version -of the text which simulates the original printed effect may however -require more complex markup and processing. -

-

More powerful and more precise mechanisms for temporal alignment are -defined in chapter . These would be appropriate for -encodings the focus of which is on the actual performance of a text -rather than its structure or formal properties. The module described -in that chapter includes a large number of other detailed proposals for -the encoding of such features as voice quality, prosody, etc., which -might be relevant to such a treatment of performance texts. -

-
Other Types of Performance Text -

Most of the elements and structures identified thus far are derived -from traditional theatrical texts. Although other performance texts, -such as screenplays or radio scripts, have not been discussed -specifically, they can be encoded using the elements and structures -listed above. Encoders may however find it convenient to use, as well, -the additional specialized elements discussed in this section. For -scripts containing very detailed technical information, the -tech element discussed in section may also -be useful. -

-

Like other texts, screenplays and television or radio scripts may -be divided into text divisions marked with div or -div1, etc. Within units corresponding with the traditional -act and scene, further subdivisions or sequences may be -identified, composed of individual shots, each associated with -a single camera angle and setting. Shots and sequences should be -encoded using an appropriate text-division element (i.e., a -div3 element if numbered division elements are in use and the -next largest unit is a div2, or a div element if -un-numbered divisions are in use) specifying sequence or -shot as the value of the type attribute, as -appropriate. -

-

It is normal practice in screenplays and radio scripts to distinguish -directions concerning camera angles, sound effects, etc., from other -forms of stage direction. Such texts also generally include far more -detailed specifications of what the audience actually sees: -descriptions of actions and background, etc. Scripts derived from -cinema and television productions may also include texts displayed as -captions superimposed on the action. All of these may be encoded using -the general purpose stage element discussed in section , and distinguished by means of its type -attribute. Alternatively, or in addition, the following more specific -elements may be used, where clear distinctions can be made: - -

-

Some examples of the use of these elements follow: -Angle on Olivia. -Ryan's wife, standing nervously alone on the sidelines, -biting her lip. She's scared and she shows it. -

-

Where particular words or phrases within a direction are emphasized -(by change of typeface or use of capital letters), an appropriate -phrase-level element may be used to indicate the fact, as in the -following examples, where certain words in the original are given in -small capitals: - George glances at the window--and freezes. -New angle--shock cut Out the window -the body of a dead man suddenly slams into -frame. He dangles grotesquely, -held up by his coat caught on a protruding bolt. -George gasps. The train whistle screams. - - Ext. TV control van—Early morning. -The T.V. announcer from the Ryan interview -stands near the Control Van, the lake in b.g. - T.V. Announcer -

Several years ago, Jack Ryan was a highly -successful hydroplane racer ...

- - -

-

All of these elements, like other stage directions, can appear both -within and between speeches. - - TV Announcer VO -

Working with Ryan are his two coworkers— -Strut Bowman, the mechanical engineer— -Angle on Strut -standing in the tow boat, walkie-talkie in hand, -watching Ryan carefully. -—and Roger Dalton, a rocket -systems analyst, and one of the scientists -from the Jet Propulsion Lab ...

- - Benjy -

Now to business.

- - Ford and Zaphod -

To business.

 -Glasses clink. - Benjy -

I beg your pardon?

 - Ford -

I'm sorry, I thought you were proposing a toast.

 - -Zoom in to overlay showing some stock film - of hansom cabs galloping past. -London, 1895. -The residence of Mr Oscar Wilde. -Suitably classy music starts. -Mix through to Wilde's drawing room. A crowd of suitably - dressed folk are engaged in typically brilliant conversation, - laughing affectedly and drinking champagne. - - Prince of Wales -

My congratulations, Wilde. Your latest play is a great success.

- - -

-
Technical Information -

Traditional stage scripts may contain additional technical -information about such production-related factors as lighting, -blocking (that is, detailed notes on actors' -movements), or props required at particular points. More technical -information about intended production effects may also appear in -published versions of screenplays or movie scripts. Where these are -presented simply as marginal notes, they may be encoded using the -general-purpose note element defined in section . -Alternatively, they may be formally distinguished from -other stage directions by using the specialized tech element: - -

-

Like stage directions, tech elements can appear anywhere -within a speech or between speeches. -

- - - - - - - - -
-
- Module for Performance Texts -

The module described in this chapter makes available the - following components: - - Performance Texts - Performance texts - Théâtre - 劇本 - Testi per performance - Textos de actuação - 舞台芸術モジュール - - - The selection and combination of modules to form a TEI schema is described in - .

-
-
diff --git a/P5/Source/Guidelines/fr/DR-PerformanceTexts.xml b/P5/Source/Guidelines/fr/DR-PerformanceTexts.xml new file mode 120000 index 0000000000..496d5b8806 --- /dev/null +++ b/P5/Source/Guidelines/fr/DR-PerformanceTexts.xml @@ -0,0 +1 @@ +../en/./DR-PerformanceTexts.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/DS-DefaultTextStructure.xml b/P5/Source/Guidelines/fr/DS-DefaultTextStructure.xml deleted file mode 100644 index 8d033a464e..0000000000 --- a/P5/Source/Guidelines/fr/DS-DefaultTextStructure.xml +++ /dev/null @@ -1,1834 +0,0 @@ - - - - -
- Default Text Structure - -

This chapter describes the default high-level structure for TEI - documents. A full TEI document combines metadata describing it, - represented by a teiHeader element, with the document - itself, represented by one or more text elements or other - elements taken from the model.resource class. That - is, the TEI element is used to group together metadata - about an encoded resource (in teiHeader, specified by the header module, which is fully described in - chapter ) with an encoded - resource. Possible encoded resources are - - a logical transcription of a source document in a - text element; the text element is specified - along with its high-level constituents in the textstructure module and described in the - remainder of the current chapter - a diplomatic transcription of a source document in a - sourceDoc element, which is specified in the transcr module and described in - chapter - an encoded representation of a text-bearing object as images - in a facsimile element, which is also specified in the - transcr module and described in - chapter - a collection of contextual information or annotations that - provides more detail about another encoded resource (whether in - the same or a different TEI document) in a standOff - element, which is specified in the linking module and described in section - a feature system declaration which can be used - to declare the use of fs elements in the rest of the - document, which is specified in the iso-fs module and described in section -

-

In a case in which more than one resource related to the same - source document share the same metadata, they may be grouped - together in a TEI element following a single - teiHeader.

-

Because the TEI can be a child of itself, a set or collection of -documents may be represented by an outermost TEI element that -contains a teiHeader with metadata that is applicable to the -entire set or collection of transcriptions, and then a complete -TEI element for each document in the collection or set; each -of these TEI elements contains a teiHeader with -metadata that is applicable to the individual document, and one or -more text or other elements taken from the -model.resource class.

- -

A variant on this basic form, the teiCorpus, is also -defined for the representation of language corpora, or other -collections of encoded texts. A teiCorpus consists of its own -metadata in a teiHeader, followed by one or more complete -TEI elements, each combining a teiHeader with one or -more elements from the model.resource class. This -permits the encoder to distinguish metadata applicable to the whole -collection of encoded texts, which is represented by the outermost -teiHeader, from that applicable to each of the individual -TEI elements within the corpus. Further information about the -organization and encoding of language corpora is given in chapter .

- -

Alternatively, the corpus may be represented with a TEI -element (perhaps with a type of corpus) in the -same manner as a teiCorpus.

- -

In summary, when the default structure module is included in a -schema, the following elements are available for the -representation of the outermost structure of a TEI document: - - - - - - - -As noted above, the teiHeader element is formally declared in -the header module (see chapter ). A TEI document may also contain elements from the -model.resource class (such as a -collection of facsimile images, or a feature system declaration) if -the appropriate module is included in a schema (see further and respectively). By default, -however, this class is not populated and hence only the elements -TEI, text, and teiCorpus are available -as major parts of a TEI document. These three elements are -provided by the textstructure module -described by the present chapter. - - - - - - -

- -

TEI texts may be regarded either as unitary, that is, -forming an organic whole, or as composite, that is, -consisting of several components which are in some important sense -independent of each other. The distinction is not always entirely -obvious: for example a collection of essays might be regarded as a -single item in some circumstances, or as a number of distinct items in -others. In such borderline cases, the encoder must choose whether to -treat the text as unitary or composite; each may have advantages and -disadvantages in a given situation.

- -

Whether unitary or composite, the text is marked with the -text tag and may contain front matter, a text body, and back -matter. In unitary texts, the text body is tagged body; in -composite texts, where the text body consists of a series of subordinate -texts or groups, it is tagged group. The overall structure of -any text, unitary or composite, is thus defined by the following -elements: - -

-

The overall structure of a unitary text is: - - - - - - - - - - - - - -

-

The overall structure of a composite text made up of two unitary -texts is: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

-

Finally, a floatingText element is provided for the case -where one text is embedded within another, but does not contribute to -its hierarchical organization, for example because it interrupts it, -or simply quoted within it. This is useful in such common literary contexts as -the play within a play or the narrative interrupted by other (often -deeply nested) multiple narratives. - - - - - - - -

-

Each of these elements is further described in the remainder of -this chapter. Elements front and back are further -discussed in sections and . The group and floatingText -elements, used for more complex or composite text structures, are -further discussed in section . Other textual -elements, such as paragraphs, lists or phrases, which nest within -these major structural elements, are discussed in chapter , in the case of elements which can appear in any kind -of document, or elsewhere in the case of elements specific to -particular kinds of document. -

-
Divisions of the Body - -

In some texts, the body consists simply of a sequence of low-level -structural items, referred to here as components or -component-level elements (see section ). Examples in prose texts include paragraphs or -lists; in dramatic texts, speeches and stage directions; in -dictionaries, dictionary entries. In other cases sequences of such -elements will be grouped together hierarchically into textual -divisions and subdivisions, such as chapters or sections. The names -used for these structural subdivisions of texts vary with the genre -and period of the text, or even at the whim of the author, editor, or -publisher. For example, a major subdivision of an epic or of the Bible -is generally called a book, that of a report is -usually called a part or -section, that of a novel a -chapter—unless it is an epistolary novel, in -which case it may be called a letter. Even texts -which are not organized as linear prose narratives, or not as -narratives at all, will frequently be subdivided in a similar way: a -drama into acts and scenes; -a reference book into sections; a diary or day -book into entries; a newspaper into -issues and sections, and so -forth. -

- -

Because of this variety, these Guidelines propose that all such -textual divisions be regarded as occurrences of the same neutrally named -elements, with an attribute type used to categorize elements -independently of their hierarchic level. Two alternative styles are -provided for the marking of these neutral divisions: -numbered and un-numbered. Numbered divisions -are named div1, div2, etc., where the -number indicates the depth of this particular division within the -hierarchy, the largest such division being div1, any subdivision -within it being div2, any further sub-sub-division being -div3 and so on. Un-numbered divisions are simply named -div, and allowed to nest recursively to indicate their -hierarchic depth. The two styles must not be combined -within a single front, body, or back element. -

-
Un-numbered Divisions -

The following element is used to identify textual subdivisions in -the un-numbered style: As a -member of the class att.typed, this -element has the following additional attributes: -

-

Using this style, the body of a text containing two parts, each -composed of two chapters, might be represented as follows: - -

-
- -
-
- -
-
-
-
- -
-
- -
-
- -

- - - - - - -
-
Numbered Divisions -

The following elements are used to identify textual subdivisions -in the numbered style: - - - - - - - - - -As members of the class att.typed these -elements all bear the following additional attributes: - -

-

The largest possible subdivision of the body is div1 -element and the smallest possible div7. If numbered -divisions are in use, a division at any one level (say, -div3), may contain only numbered divisions at the next lowest -level (in this case, div4).

-

Using this style, the body of a text containing two parts, each -composed of two chapters, might be represented as follows: - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

- - - - - - - - - - - - - - -
-
Numbered or Un-numbered? -

Within the same front, body, or back -element, all hierarchic subdivisions must be marked using either -nested div elements, or div1, div2 etc. -elements nested as appropriate; the two styles must not -be mixed. -

-

The choice between numbered and un-numbered divisions will depend -to some extent on the complexity of the material: un-numbered -divisions allow for an arbitrary depth of nesting, while numbered -divisions limit the depth of the tree which can be constructed. Where -divisions at different levels should be processed differently (for -example to ensure that chapters, but not sections, begin on a new -page), numbered divisions slightly simplify the task of defining the -desired processing for each level, though this distinction could also -be made by supplying this information on the type attribute -of an un-numbered div. Some software may find numbered -divisions easier to process, as there is no need to maintain knowledge -of the whole document structure in order to know the level at which a -division occurs; such software may, however, find it difficult to cope -with some other aspects of the TEI scheme. On the other hand, in a -collection of many works it may prove difficult or impossible to -ensure that the same numbered division always corresponds with the -same type of textual feature: a chapter may be at -level 1 in one work and level 3 in another. -

-

Whichever style is used, the global n and xml:id -attributes (section ) may be used to provide -reference strings or labels for each division of a text, where -appropriate. Such labels should be provided for each section -which is regarded as significant for referencing purposes (on -reference systems, see further section ). -

- -

As indicated above, the type and subtype -attributes provided by the att.typed class -may be used to provide a name or description for the division. -Typical values might be book, -chapter, section, -part, or (for verse texts) -book, canto, -stanza, or (for dramatic texts) -act, scene. The following -extended example uses numbered divisions to indicate the structure of -a novel, and illustrates the use of the attributes discussed above. -It also uses some elements discussed in section -and the p element discussed in section . - - - Book I. - - Of writing lives in general, and particularly of Pamela, with a word - by the bye of Colley Cibber and others. -

It is a trite but true observation, that examples work more forcibly on - the mind than precepts: ...

- - - - Of Mr. Joseph Andrews, his birth, parentage, education, and great - endowments; with a word or two concerning ancestors. -

Mr. Joseph Andrews, the hero of our ensuing history, was esteemed to - be the only son of Gaffar and Gammar Andrews, and brother to the - illustrious Pamela, whose virtue is at present so famous ...

- - - - The end of the first Book - - - Book II - - Of divisions in authors -

There are certain mysteries or secrets in all trades, from the highest - to the lowest, from that of prime-ministering, to this of - authoring, which are seldom discovered unless to members of - the same calling ...

-

I will dismiss this chapter with the following observation: that it - becomes an author generally to divide a book, as it does a butcher to - joint his meat, for such assistance is of great help to both the reader - and the carver. And now having indulged myself a little I will endeavour - to indulge the curiosity of my reader, who is no doubt impatient to know - what he will find in the subsequent chapters of this book.

- - - A surprising instance of Mr. Adams's short memory, with the - unfortunate consequences which it brought on Joseph. - -

Mr. Adams and Joseph were now ready to depart different ways ...

- - - -

- -

As an alternative (or complement) to this use of the -type attribute to characterize neutrally named division -elements, the modification mechanisms discussed in section may be used to define new elements such as -chapter, part, etc. To make this simpler, a single -member model class is defined for each of the neutrally named division -elements: model.divLike (containing -div), model.div1Like (containing -div1), model.div2Like (containing -div2), etc. For example, suppose that the body of a text -consists of a series of diary entries, each of which is potentially -divided into entries for the morning and the afternoon. This might be -represented in any of the following ways. First, using the un-numbered -style: -

-

[...]

-

[...]

-
-
-

[...]

-

[...]

-
- - -Equivalently, using the numbered style: - - -

[...]

 -

[...]

 - - -

[...]

 -

[...]

 - - - - -Now, assuming a customization in which a new element -diaryEntry has been added to the model.divLike class: - -

[...]

 -

[...]

 - - -

[...]

 -

[...]

 - - - - -And finally, assuming a customization in which three new elements have -been added: diaryEntry to the model.div1Like class, and amEntry and -pmEntry both to the model.div2Like class: -

- -

[...]

 -

[...]

 - - -

[...]

 -

[...]

 - - - -

-

More information about the customization techniques exemplified -here is provided in . -

- - -
-
Partial and Composite Divisions -

In most situations, the textual subdivisions marked by div -or div1 (etc.) elements will be both complete and identically -organized with reference to the original source. For some purposes -however, in particular where dealing with unusually large or unusually -small texts, encoders may find it convenient to present as textual -divisions sequences of text which are incomplete with reference to the -original text, or which are in fact an ad hoc agglomeration of tiny -texts. Moreover, in some kinds of texts it is difficult or impossible -to determine the order in which individual subdivisions should be -combined to form the next higher level of subdivision, as noted below. -

-

To overcome these problems, the following additional attributes are -defined for all elements in the att.divLike class: - - - -

-

For example, an encoder might choose to transcribe only the first two -thousand words of each chapter from a novel. In such a case, each -chapter might conveniently be regarded as a partial division, and tagged -with a div element in the following form: -

-

...

-
-where xx represents a number for the chapter, and the -part attribute takes the value Y to indicate -that this division is incomplete in some respect. Other possible -values for this attribute indicate whether material has been omitted -initially (I), finally -(F), or in the middle (M) of the division, while the gap -element () may be used to indicate exactly -where material has been omitted: -
-

...

- -

...

-
 -The -samplingDecl element in the TEI header should also be used to -record the principles underlying the selection of incomplete samples, as -further described in section . -

-

The following example demonstrates how a newspaper column composed of -very short unrelated snippets may be encoded using these attributes: - -News in brief - -Police deny losing bomb -

Scotland Yard yesterday denied claims in the Sunday -Express that anti-terrorist officers trailing an IRA van -loaded with explosives in north London had lost track of -it 10 days ago.

- - -Hotel blaze -

Nearly 200 guests were evacuated before dawn -yesterday after fire broke out at the Scandic -Crown hotel in the Royal Mile, Edinburgh.

- - -Test match split -

Test Match Special next summer will be split -between Radio 5 and Radio 3, after protests this -year that it disrupted Radio 3's music schedule.

- - - -

-

The org attribute on the div1 element is used -here to indicate that individual stories in this group, marked here as -div2, are really quite independent of each other, although they -are all marked as subdivisions of the whole group. They can be read in -any order without affecting the sense of the piece; indeed, in some -cases, divisions of this nature are printed in such a way as to make it -impossible to determine the order in which they are intended to be read. -Individual stories can be added or removed without affecting the -existing components. -

-

This method of encoding composite texts as composite divisions has -some limitations compared with the more general and powerful mechanisms -discussed in section . However, it may be preferable -in some circumstances, notably where the individual texts are very -small. -

-
Elements Common to All Divisions -

The divisions of any kind of text may sometimes begin with a brief -heading or descriptive title, with or without a byline, an epigraph or -brief quotation, or a salutation such as one finds at the start of a -letter. They may also conclude with a brief trailer, byline, -postscript, or signature. Many of these (e.g. a byline) may appear -either at the start or at the end of a text division proper.

-

To support this heterogeneity, the TEI architecture defines five -classes, all of which are populated by this module: - - - - - - -

- -
Headings and Trailers - -

The head element is used to identify a heading prefixed to -the start of any textual division, at any level. A given division may -contain more than one such element, as in the following example: - -Etymology -(Supplied by a late consumptive usher to a -grammar school) -

The pale Usher — threadbare in coat, heart, -body and brain; I see him now. He was ever -dusting his old lexicons and grammars, ...

- -

-

Unlike some other markup schemes, the TEI scheme does -not require that headings attached to textual -subdivisions at different hierarchic levels have different -identifiers. All kinds of heading are marked identically using the -head tag; the type or level of heading intended is implied by -the immediate parent of the head element, which may for -example be a div1, div2, etc., an un-numbered -div, or any member of the model.listLike class. However, as with -div elements, the encoder may choose to extend the model.headLike class of which head is -the sole member to include other such elements if required.

-

In certain kinds of text (notably newspapers), there may be a need -to categorize individual headings within the sequence at the start of -a division, for example as main headings, or -detail headings: this may readily be done using the -type or subtype attribute. Specific elements are provided -for certain kinds of heading-like features, (notably byline, -dateline, and salute; see further section ), but the type or subtype -attributes must be used to discriminate among other forms of -heading. These attributes are provided, as elsewhere, by the att.typed attribute class of which the -head element is a member. -

-

In the following example, taken from a British newspaper, the lead -story and its associated headlines have been encoded as a div -element, with appropriate model.divTop elements attached: -

- -President pledges safeguards for 2,400 British -troops in Bosnia - -Major agrees to enforced no-fly zone -By George Jones, Political Editor, in Washington -

Greater Western intervention in the conflict in -former Yugoslavia was pledged by President Bush ...

- -

-

In older writings, the headings or incipits may be -longer than in modern works. -When heading-like material appears in the middle of a text, the encoder -must decide whether or not to treat it as the start of a new division. -If the phrase in question appears to be more closely connected with what -follows than with what precedes it, then it may be regarded as a -heading and tagged as the head of a new div element. -If it appears to be simply inserted or superimposed—as for example -the kind of pull quotes often found in newspapers -or magazines, then the quote, q, or cit -element may be more appropriate. -

-

The trailer element, which can appear at the end of a -division only, is used to mark any heading-like feature appearing in -this position, as in this example: -

In the name of Christ here begins the - first book of the ecclesiastical history of Georgius Florentinus, - known as Gregory, Bishop of Tours. -
Chapter Headings - - - - -
-
In the name of Christ here begins Book I of the history. -

Proposing as I do ...

-

From the Passion of our Lord until the death of Saint Martin four - hundred and twelve years passed.

- Here ends the first Book, which covers five thousand, five - hundred and ninety-six years from the beginning of the world down - to the death of Saint Martin. -
-
-

- - -
-
Openers and Closers -

In addition to headings of various kinds, divisions sometimes include -more or less formulaic opening or closing passages, typically conveying -such information as the name and address of the person to whom the -division is addressed, the place or time of its production, a salutation -or exhortation to the reader, and so on. Divisions in epistolary form -are particularly liable to include such features. -Additional elements for the detailed encoding of personal names, dates, -and places are provided in chapter . -For simple cases, the following elements should be adequate: - - - - - - -

-

The byline and dateline elements are used to encode -headings which identify the authorship and provenance of a division. -Although the terminology derives from newspaper usage, there is no -implication that dateline or byline elements apply -only to newspaper texts. The following example illustrates use of the -dateline and signed elements at the end of the -preface to a novel: -

-To Henry Hope. -

It is not because this volume was conceived and partly -executed amid the glades and galleries of the Deepdene, -that I have inscribed it with your name. ... I shall find a -reflex to their efforts in your own generous spirit and -enlightened mind. -

- -D. -Grosvenor Gate, May-Day, 1844 - -
- - -

-

Where a sequence of such elements appear together, either at the -beginning or end of an element, it may be convenient to group them -together using one of the following elements: - - - -The following examples demonstrate the use of the opener and -closer grouping elements: -

- Sixth Narrative - contributed by Sergeant Cuff -
- - - Dorking, Surrey, - July 30th, 1849 - - To Franklin Blake, Esq. Sir, — - -

I beg to apologize for the delay that has occurred in the - production of the Report, with which I engaged to furnish you. - I have waited to make it a complete Report ...

- - I have the honour to remain, dear sir, your - obedient servant - RICHARD CUFF (late sergeant in the - Detective Force, Scotland Yard, London). - -
-
- -
-Letter XIV: Miss Clarissa Harlowe to Miss Howe - Thursday evening, March 2. -

On Hannah's depositing my long letter ...

-

An interruption obliges me to conclude myself -in some hurry, as well as fright, what I must ever be,

- -Yours more than my own, -Clarissa Harlowe - -
 - -

-

For further discussion of the encoding of dates and of names of persons and places, see section and chapter . -

-
Arguments, Epigraphs, and Postscripts -

The argument element may be used to encode the prefatory -list of topics sometimes found at the start of a chapter or -other division. It is most conveniently encoded as a list, since this -allows each item to be distinguished, but may also simply be presented -as a paragraph. The following are thus both equally valid ways of -encoding the same argument: -

- -

Kingston — Instructive remarks on early English history - — Instructive observations on carved oak and life in general - — Sad case of Stivvings, junior — Musings on antiquity - — I forget that I am steering — Interesting result - — Hampton Court Maze — Harris as a guide.

- -

It was a glorious morning, late spring or early summer, as you - care to take it ...

-
- -
- - - Kingston - Instructive remarks on early English history - Instructive observations on carved oak and life in - general - Sad case of Stivvings, junior - Musings on antiquity - I forget that I am steering - Interesting result - Hampton Court Maze - Harris as a guide. - - -

It was a glorious morning, late spring or early summer, as you - care to take it ...

-
 - -

-

An epigraph is a quotation from some other work, a -saying, or a motto, appearing on a title page, or at the start of a -division. It may be encoded using the special-purpose -epigraph element, as in the following example: - - -E. M. Forster -Howards End -Only connect... - - -When an epigraph contains a quotation, this may often be associated -with a bibliographic reference. In such cases, it is recommended -additionally to group the quotation and its source together using the -cit element, as in the following example:

Chapter 19 - - I pity the man who can travel - from Dan to Beersheba, and say 'Tis all - barren; and so is all the world to him - who will not cultivate the fruits it offers. - - Sterne: Sentimental Journey. - -

To say that Deronda was romantic would be to - misrepresent him: but under his calm and somewhat - self-repressed exterior ...

-
- -

-

For discussion of quotations appearing other than as epigraphs refer -to section . -

A postscript is a passage added after the signature of -a letter or, less frequently, the main portion of the body of a book, -article, or essay. In English a postscript is often abbreviated as -P.S. or PS, and -postscripts are often introduced by labels with one of these -abbreviations, as in the following example. - -

- - - Newport - May ye 27th 1761 - - Gentlemen - -

Capt Stoddard's Business - calling him to Providence, have - got him to look at Hopkins brigantine - & if can agree to Purchase her, shall - be much oblig'd for your further - assistance herein, & will acquiesce with - whatever you & he shall Contract - for — I Thank you for your - Line respecting the brigantine & Beg - leave to Recommend the Bearer - to you for your advice & Friendship - in this matter

- - I am your most humble servant - Joseph Wanton Jr - - - -

I have Mollases, Sugar, - Coffee & Rum, which - will Exchange with you - for Candles or Oyl

- -
- - -

-
-
Content of Textual Divisions -

Other than elements from the model.divWrapper, model.divTop, or model.divBottom classes, every textual division -(numbered or un-numbered) consists of a sequence of ungrouped model.common elements (see ). The actual elements available will depend on the -modules in use; in all cases, at least the component-level structural -elements defined in the core will be available (paragraphs, lists, -dramatic speeches, verse lines and line groups etc.). If the drama -module has been selected, then other component- or phrase- level items -specialized for performance texts (for example, cast lists or camera -angles) will be available, as defined in -chapter ) will be available. If the dictionary -module is in use, then dictionary entries, related entries, etc. (as -defined in chapter ) will also be available; if the -module for transcribed speech is in use, then utterances, pauses, -vocals, kinesics, etc., as defined in chapter -will be available; and so on.

-

Where a text contains low-level elements from more than one -module these may appear at any point; there is no requirement that -elements from the same module be kept together.

- - - - - - - - - - - - - - - -
-
-
Grouped and Floating Texts -

The group element discussed in -should be used to represent a collection of independent texts which is -to be regarded as a single unit for processing or other purposes. The -floatingText element discussed in -should be used to represent an independent text which interrupts the -text containing it at any point but after which the surrounding text -resumes. -

-
Grouped Texts -

-Examples of composite texts which should be represented using the -group element include -anthologies and other collections. The presence of common front matter -referring to the whole collection, possibly in addition to front matter -relating to each individual text, is a good indication that a given text -might usefully be encoded in this way; this structure may be found -useful in other circumstances too. -

-

For example, the overall structure of a collection of -short stories might be encoded as follows: - - - - - The Adventures of Sherlock Holmes - - First published in The Strand - between July 1891 and December 1892 - - - - - - Adventures of Sherlock - Holmes - Adventure I. — - A Scandal in Bohemia - By A. Conan Doyle. - - -

To Sherlock Holmes she is always - the woman. ...

- - - - - - Adventures of Sherlock Holmes - Adventure II. — - The Red-Headed League - By A. Conan Doyle. - - -

I had called upon my friend, Mr. Sherlock Holmes, one day - in the autumn of last year and found him in deep conversation - with a very stout, florid-faced, elderly gentleman with fiery red hair … -

- - - - - - Adventures of Sherlock Holmes - Adventure XII. — - The Adventure of the Copper Beeches - - By A. Conan Doyle. - - -

To the man who loves art for its - own sake, remarked Sherlock Holmes ... - - - - ... she is now the head of a private school - at Walsall, where I believe that she has - met with considerable success.

- - - - - - -

-

A text which is a member of a group may itself contain groups. This -is quite common in collections of verse, but may happen in any kind of -text. As an example, consider the overall structure of a typical -collection, such as the Muses Library edition of -Crashaw's poetry. Following a critical -introduction and table of contents, this work contains the following -major sections: - -Steps to the Temple (a collection of -verse as published in 1648) -Carmen deo Nostro (a second collection, -published in 1652) -The Delights of the Muses (a third -collection, published in 1648) -Posthumous Poems, I (a collection of -fragments all taken from a single manuscript) -Posthumous Poems, II (a further collection -of fragments, taken from a different manuscript) -

-

The first three of these collections each has a -reasonable claim to be considered as a text in its own right, and may -therefore be encoded as such. It is rather more arbitrary as to -whether the two posthumous collections should be treated as two -groups, following the practice of the Muses Library -edition. An encoder might elect to combine the two into a single -group or simply to treat each fragment as an ungrouped unitary text. -

-

The Muses Library edition reprints the whole of each -of the three original collections, including their original front -matter (title pages, dedications etc.). These should be encoded using -the front element and its constituents (on which see further -section ), while the body of each collection -should be encoded as a single group element. Each individual -poem within the collections should be encoded as a distinct -text element. The beginning of the whole collection would -thus appear as follows (for further discussion of the use of the -elements div and lg for textual subdivision of -verse, see section and chapter ): - - - The poems of Richard Crashaw - Edited by J.R. Tutin - -

Editor's Note -

A few words are necessary ...

-
- - - - - - - Steps to the Temple, Sacred Poems - - -
The Preface to the Reader -

Learned Reader, The Author's friend will not usurp much - upon thy eye ...

-
- - - - - Sospetto D'Herode - - - - Libro Primo - - Casting the times with their strong signs - - - Muse! now the servant of soft loves no more - Hate is thy theme and Herod whose unblest - Hand (O, what dares not jealous greatness?) tore - A thousand sweet babes from their mothers' breast, - The blooms of martyrdom ... - - - The Tear - - - What bright soft thing is this - Sweet Mary, thy fair eyes' expense? - - - - - - - - - - - - - - - - - - - - - - - - -

-

The group element may be used in this way to encode any kind -of collection of which the constituents are regarded by the encoder as -texts in their own right. Examples include anthologies or collections -of verse or -prose by multiple authors, florilegia, or commonplace books, -journals, day books, etc. As a fairly typical example, we consider -The Norton Book of Travel, an anthology edited by Paul -Fussell and published in 1987 by W. W. Norton. This work comprises -the following major sections: - -Front matter (title page, acknowledgments, introductory essay) -The Beginnings -The Eighteenth Century and the Grand Tour -The Heyday -Touristic Tendencies -Post Tourism -Back matter (permissions list, index) -Each titled section listed above comprises a group of extracts or -complete texts from writers of a given historical period, preceded by an -introductory essay. For example, the second group listed above -contains, inter alia, the following: - -Prefatory essay -Five letters by Lady Mary Wortley Montagu -An extract from Swift's Gulliver's Travels -Two poems by Alexander Pope -Two extracts from Boswell's Journal -A poem by William Blake -Each group of writings by a single author is preceded by a brief -biographical notice. Some of the extracts are quite lengthy, containing -several chapters or other divisions; others are quite short. As the -above list indicates, the texts included range across all kinds of -material: verse, prose, journals and letters. -

-

The easiest way of encoding such an anthology is to treat each -individual extract as a text in its own right. A sequence of texts by a -single author, together with the biographical note preceding it, can -then be treated as a single group element within the larger -group formed by the section. The sequence of single or -composite texts making up a single section of the work is likewise -treated, together with its prefatory essay, as a single group -within the work. Schematically: - - - - - - - The Beginnings - - - - - - - - - - - - - - - - - - - - - - The Heyday - - - - - - -

-

Note that the editor's introductory essays on each author may be -treated as texts in their own right (as the essays on Lady Mary -Wortley Montagu and Alexander Pope have been treated above), or as -front matter to the embedded text, as the essay on Swift has been. -The treatment in the example is intentionally inconsistent, to allow -comparison of the two approaches. Consistency can be imposed either -by treating the Swift section as a group containing one text -by Swift and one by the editor, or by treating the Montagu and Pope -sections as text elements containing the editor's essays as -front matter. Marked in the second way, the Pope section of the book -would look like this: - - - - - - - -

-

The essays on The Eighteenth Century and the Grand Tour and -other larger sections could also be tagged as front -matter in the same way, by treating the larger sections as text -elements rather than group elements. -

-

Where, as in this case, an anthology contains different kinds of -text (for example, mixtures of prose and drama, or transcribed speech -and dictionary entries, or letters and verse), the elements to be -encoded will of course be drawn from more than one module. -The elements provided by the core module -described in chapter should however prove adequate -for most simple purposes, where prose, drama, and verse are combined -in a single collection. -

-

For anthologies of short extracts such as commonplace books, it may -often be preferable to regard each extract not as a text in its own -right but simply as a quotation or cit element. The following -component-level elements may be used to encode quotations of this kind: - -For example, the chapter of extracts which appears -in the front matter of Melville's Moby Dick might be -encoded as follows: -

- Extracts - (Supplied by a sub-sub-Librarian) -

It will be seen that this mere painstaking burrower and - grubworm of a poor devil of a Sub-Sub appears to have gone - through the long Vaticans and street-stalls of the earth, - picking up whatever random allusions to whales he could - anyways find ... - Here ye strike but splintered hearts together — there, - ye shall strike unsplinterable glasses!

-

- - And God created great whales. - Genesis - - - - Leviathan maketh a path to shine after him; - One would think the deep to be hoary. - - Job - - - By art is created that great Leviathan, - called a Commonwealth or State — (in Latin, - civitas), which - is but an artificial man. - Opening sentence of Hobbes's Leviathan - -

-
-For more information on the use of the quote and bibl -elements, see sections and -respectively. -

- -
-
Floating Texts -

An important characteristic of the unitary or composite text -structures discussed so far is that they can be regarded as forming what is -mathematically known as a tesselation covering the whole -of the available text (or text division) at each hierarchic -level. Just as an XML document has a single root element containing -a single tree, each node of which forms a properly nested sub-tree, so -it seems natural to think of the internal structure of a text as -decomposable hierarchically into subparts, each of which is a -properly nested subtree. While this is undoubtedly true of a large -number of documents, it is not true of all. In particular, it is not -true of texts which are only partly tesselated at a given level. For -example, if a text A is contained by text B in such a way that part of -B precedes A and part follows it, we cannot tesselate the whole of B. -In such a case, we say that text A is a floating text.

- -

The floatingText element is a member of the -model.divPart class, and can thus appear within -any division level element in the same way as a paragraph. For -example, texts such as the Decameron or the -Arabian Nights might be regarded as containing many -floating texts embedded within another single text, the framing -narrative, rather than as groups of discrete texts in which the -fragments of framing narrative are regarded as front or back matter. -

- -

As an example, we consider an 18th century text The Lining to -the <hi>Patch-Work Screen</hi>, by Jane Barker (1726). This -lengthy narrative contains nearly a hundred distinct tales -embedded (as the title suggests) in a single patchwork. The work -begins by introducing the central character, Galecia, but within a few pages -launches into a distinct narrative, the story of Captain Manly: - - -

Galecia one Evening setting alone in her Chamber by a clear Fire, -and a clean Hearth [...] reflected on the Providence of our -All-wise and Gracious Creator [...]

-

She was thus ruminating, when a Gentleman enter'd the Room, the -Door being a jar [...] calling for a Candle, she beg'd a thousand -Pardons, engaged him to sit down, and let her know, what had so long -conceal'd him from her Correspondence. -

- -The Story of Captain Manly -

Dear Galecia, said he, though you partly know the loose, or rather -lewd Life that I led in my Youth; yet I can't forbear relating part of -it to you by way of Abhorrence... - -I had lost and spent all I had in the World; in which I verified the -Old Proverb, That a Rolling Stone never gathers Moss, -

 - - -

-

Following the conclusion of Captain Manly's tale, we are -returned to Galecia, and almost immediately after that into two further -stories. -However, the Galecia narrative returns between each of the texts, -which is why we choose to represent them as floatingTexts: - - -

The Gentleman having finish'd his Story, Galecia waited on him to -the Stairs-head; and at her return, casting her Eyes on the Table, she -saw lying there an old dirty rumpled Book, and found in it the -following story:

-

IN the time of the Holy War when -Christians from all parts went into the Holy Land to oppose the Turks; -Amongst these there was a certain English Knight...

- -

The King graciously pardoned the Knight; Richard was kindly receiv'd -into his Convent, and all things went on in good order: But from hence -came the Proverb, We must not strike Robert for -Richard.

 - -

By this time Galecia's Maid brought up her Supper; after which she -cast her Eyes again on the foresaid little Book, where she found the -following Story, which she read through before she went to bed. -

-The Cause of the Moors Overrunning -Spain -

King ———— of Spain at his Death, committed the Government of his -Kingdom to his Brother Don ——— till his little Son should come of -Age ...

-

Thus the little Story ended, without telling what Misery -befel the King and Kingdom, by the Moors, who over ran the Country for -many Years after. To which, we may well apply the Proverb, - - Who drives the Devil's Stages, - Deserves the Devil's Wages -

- -

The reading this Trifle of a Story detained Galecia from her Rest -beyond her usual Hour; for she slept so sound the next Morning, that -she did not rise, till a Lady's Footman came to tell her, that his -Lady and another or two were coming to breakfast with her... -

- -

-

In other multi-narrative texts, the individual nested tales may -have greater significance than the framing narratives, and it may -therefore be preferable to treat the fragments of framing narrative as -front or back matter associated with each nested tale. This is -commonly done, for example, in texts such as Chaucer's Canterbury -Tales, where each tale is typically presented with front matter in -which the teller of the tale is introduced, and back matter in which -the pilgrims comment on it.

- -

It is important to distinguish between the uses of floatingText and quote. Whereas the semantics of quote suggest that its content derives from a source external to the current text, floatingText carries no such implication and is simply used whenever the richer content model that it provides is required to support the markup of a part of a text that is presented as a discrete inclusion. In some cases, such inclusions could be considered external (e.g., enclosures, attachments, etc.); often however, as in the examples above, the included text bears no signs of emanating from outside.

- -

floatingText and quote may be used in combination. For a text with rich internal structure that is quoted at length, floatingText might be used within quote. Also, like a unitary text, floatingText may include one or more quoted sections, each marked with a quote element.

- -
- -
Virtual Divisions -

Where the whole of a division can be automatically generated, for -example because it is derived from -another part of this or another document, an encoder may prefer not to represent it -explicitly but instead simply mark its location by means of a -processing instruction, or by using the special purpose -divGen element: - -

-

This element is made available by the model.divGenLike class of which it is the sole -element. The divGen element is a member of the -att.typed class, from which it inherits the -type and subtype attributes. It may appear -wherever a div or div1 (div2, etc.) element may appear.

- - - -

For example, if the table of contents (toc) for a given work is simply -derived by copying the first head element from each -div element in a text, it might be more easily encoded as -follows: - -Similarly, in a digital edition combining a transcribed version -of some text with a translated version of it, it may be desired to -represent the transcript, the translation, and an aligned version of -the two as three distinct divisions. This could be achieved by an -encoding like the following: -

-
-
The processing to be carried out when a -divGen element is rendered will be determined by the -application program or stylesheet in use: the function of the TEI -markup is simply to identify the location at which the virtual -division is to be generated, and also to provide some information -about the kind of division to be generated. As such it may be regarded -as a special kind of processing instruction, and could equally well be -represented by one.

- -
- - -
Front Matter -

By front matter we mean distinct sections of a text -(usually, but not necessarily, a printed one), prefixed to it by way of -introduction or identification as a part of its production. Features -such as title pages or prefaces are clear examples; a less definite -case might be the prologue attached to a play. The front matter of an -encoded text should not be confused with the TEI header described in -chapter , which serves as a kind of front matter for -the computer file itself, not the text it encodes. -

-

An encoder may choose simply to ignore the front matter in a text, -if the original presentation of the work is of no interest, or for -other reasons; alternatively some or all components of the front matter -may be thought worth including with the text as components of the -front element.This decision should be recorded in the -samplingDecl element of the header. With the exception of -the title page, (on which see section ), front -matter should be encoded using the same elements as the rest of a text. -As with the divisions of the text body, no other specific tags are -proposed here for the various kinds of subdivision which may appear -within front matter: instead either numbered or un-numbered -div elements may be used. The following suggested -valuesAs with all lists of suggested -values for attributes, it is recommended that software -written to handle TEI-conformant texts be prepared to recognize and -handle these values when they occur, without limiting the user to the -values in this list. -for the type attribute may be used to distinguish various -kinds of division characteristic of front matter: - -A foreword or preface addressed to - the reader in which the author or publisher explains the - content, purpose, or origin of the text. -A formal declaration of - acknowledgment by the author in which persons and institutions - are thanked for their part in the creation of a text. -A formal offering or dedication of - a text to one or more persons or institutions by the author. -A summary of the content of a text as - continuous prose. -A table of contents, specifying the - structure of a work and listing its constituents. - The list - element should be used to mark its structure. -A pictorial frontispiece, - possibly including some text. -

-

The following extended example demonstrates how various parts of the -front matter of a text may be encoded. The front part begins with a -title page, which is presented in section below. -This is followed by a dedication and a preface, each of which is encoded -as a distinct div: -

-

To my parents, Ida and Max Fish

-
-
Preface -

The answer this book gives to its title question is there is - and there isn't.

-

Chapters 1–12 have been previously published in the - following journals and collections: - - chapters 1 and 3 in New literary History - chapter 10 in Boundary II (1980) - . - I am grateful for permission to reprint.

- S.F. -
-

-

The front matter concludes with another div element, shown -in the next example, this time containing a table of contents, which -contains a list element (as described in section -). Note the use of the ptr element to provide -page-references: the implication here is that the target identifiers -supplied (fish1, fish2, etc.) will correspond with identifiers used for -the div elements containing chapters of the text itself. (For the -ptr element, see .) -

- Contents - - Introduction, or How I stopped Worrying and Learned to Love - Interpretation - - - Part One: Literature in the Reader - Literature in the Reader: Affective Stylistics - - What is Stylistics and Why Are They Saying Such - Terrible Things About It? - -
-
Introduction - -
-
Literature in the Reader - -
-
What is stylistics? - -
- -Alternatively, the pointers in the index might link to the page breaks -at which a chapter begins, assuming that these have been included in -the markup: - - Literature in the Reader: Affective Stylistics - 24 - -
Literature in the Reader - - -
- - -

-

The following example uses numbered divisions to mark up the front -matter of a medieval text. -Note that in this case no title page in the modern -sense occurs; the title is simply given as a heading at the start of the -front matter. Note also the use of the type attribute on the -div elements to indicate document elements comparatively -unusual in modern books such as the initial prayer: - - -

Here bygynniþ a book of contemplacyon, þe whiche - is clepyd þE CLOWDE OF VNKNOWYNG, - in þe whiche a soule is onyd wiþ GOD.

- - - Here biginneþ þe preyer on þe prologe. -

God, unto whom alle hertes ben open, & unto whome alle wille - spekiþ, & unto whom no priue þing is hid: I beseche - þee so for to clense þe entent of myn hert wiþ þe - unspekable 3ift of þi grace, þat I may parfiteliche - loue þee & worþilich preise þee. Amen.

- - - Here biginneþ þe prolog. -

In þe name of þe Fader & of þe Sone & - of þe Holy Goost.

-

I charge þee & I beseeche þee, wiþ as moche - power & vertewe as þe bonde of charite is sufficient - to suffre, what-so-euer þou be þat þis book schalt - haue in possession ...

- - - Here biginneþ a table of þe chapitres. - - - Of foure degrees of Cristen mens leuing; & of þe - cours of his cleping þat þis book was maad vnto. - - A schort stering to meeknes & to þe werk of þis - book - - Of somme certein tokenes bi þe whiche a man may proue - wheþer he be clepid of God to worche in þis werk. - - & here eendeþ þe table of þe chapitres. - - - -

-

If, however, the table of contents can be automatically generated -from the remainder of the text, it may be preferable simply to mark -its presence, either by means of an empty divGen element or -by using an appropriate processing instruction.

-
-
Title Pages -

Detailed analysis of the title page and other -preliminaries of older printed books and manuscripts is of -major importance in descriptive bibliography and the cataloguing of -printed books; such analysis may require a rather more detailed module -than that proposed here. The following elements are -suggested as a means of encoding the major features of most title pages: - - - - - - - - - - - - - - -

-

These elements constitute the model.titlepagePart class. Together with the figure - element described in chapter , any number of elements -from this class can appear within a titlePage element. The figure element is included so -as to enable encoders to record the presence of complex non-textual -material on a title page. For simple cases such as printers' -ornaments or illustrations the graphic element discussed -in section should be adequate.

-

The elements listed above, together with the head element, -also constitute the class model.pLike.front. The elements in this class can -appear within a minimal front element without any need to -group them together and encode a complete title page.

-

Encoders wishing to add new elements to either class may do so -using the methods described in section . Two -examples of the use of these elements follow. First, the title page of -the work discussed earlier in this section: - - - Is There a Text in This Class? - The Authority of Interpretive Communities - - Stanley Fish - - Harvard University Press - Cambridge, Massachusetts - London, England - -

-

Second, a characteristically verbose 17th century example. Note the -use of the lb tag to mark the line breaks of the original -where necessary: - - - THE - Pilgrim's Progress - FROM - THIS WORLD, - TO - That which is to come: - Delivered under the Similitude of a - DREAM - Wherein is Discovered, - The manner of his setting out, - His Dangerous Journey; And safe - Arrival at the Desired Countrey. - - - I have used Similitudes,Hos. 12.10 - - By John Bunyan. - Licensed and Entred according to Order. - - LONDON, - Printed for Nath. Ponder - at the Peacock in the Poultrey - near Cornhil, 1678. -

-

Where, as here, it is considered important to encode salient -features of the way a title page was originally rendered, -the techniques exemplified in may also be -useful.

- - - - -

Where title pages are encoded, their physical rendition is -often of considerable importance. One approach to this requirement -would be to use the seg tag, described in chapter , to segment the typographic content of each part of the -title page, and then use the global rend attribute to specify -its rendition. Another would be to use a module specialized for the -description of typographic entities such as pages, lines, rules, etc., -bearing special-purpose attributes to describe line-height, leading, -degree of kerning, font, etc. Further discussion of these problems is -provided in chapter . -

- - - - - - - -
-
Back Matter -

Conventions vary as to which elements are grouped as back matter and -which as front. For example, some books place the table of contents at -the front, and others at the back. Even title pages may appear at the -back of a book as well as at the front. The content model for -back and front elements are therefore identical. -

-

The following suggested values may be used for the type -attribute on all division elements, in order to distinguish various -kinds of division characteristic of back matter: - -An ancillary self-contained section of -a work, often providing additional but in some sense extra-canonical -text. -A list of terms associated with definition texts -(glosses): this should be encoded as a list type="gloss" -(see section ). -A section in which textual or -other kinds of notes are gathered together. -A list of bibliographic citations: this should be encoded -as a listBibl (see section ). -Any form of index to the work. -A statement appearing at the end of a book describing the -conditions of its physical production. -

-

No additional elements are proposed for the encoding of back matter -at present. Some characteristic examples follow; first, an index (for -the case in which a printed index is of sufficient interest to merit -transcription): - -

- Index - - Actors, public, paid for the contempt attending - their profession, 263 - Africa, cause assigned for the barbarous state of - the interior parts of that continent, 125 - Agriculture - - ancient policy of Europe unfavourable to, 371 - artificers necessary to carry it on, 481 - cattle and tillage mutually improve each other, 325 - wealth arising from more solid than that which proceeds - from commerce 520 - - Alehouses, the number of, not the efficient cause of drunkenness, 461 - -
- - -Note that if the page breaks in the original source have also been -explicitly encoded, and given identifiers, the references to them in the -above index can more usefully be recorded as links. For example, -assuming that the encoding of page 461 of the original source starts -like this: - -then the last item above might be encoded more usefully in either -of the following forms: - Alehouses, the number of, not -the efficient cause of drunkenness, 461 - Alehouses, the number of, not the efficient cause of drunkenness, -

-

Next, a back-matter division in epistolary form: - -

- A letter written to his wife, founde with this booke - after his death. -

The remembrance of the many wrongs offred thee, and thy - unreproued vertues, adde greater sorrow to my miserable state, - than I can utter or thou conceiue. ... - ... yet trust I in the world to come to find mercie, by the - merites of my Saiuour to whom I commend thee, and commit - my soule.

- Thy repentant husband for his disloyaltie, - Robert Greene. -

Faelicem fuisse infaustum

 - FINIS -
- -

-

And finally, a list of corrigenda and addenda with pseudo-epistolary -features: - -

- Addenda - M. Scriblerus Lectori -

Once more, gentle reader I appeal unto thee, from the shameful -ignorance of the Editor, by whom Our own Specimen of -Virgil hath been mangled in such miserable manner, that -scarce without tears can we behold it. At the very entrance, Instead -of προλεγομενα, lo! -προλεγωμενα with an Omega! -and in the same line consulâs with a circumflex! -In the next page thou findest leviter perlabere, -which his ignorance took to be the infinitive mood of -perlabor but ought to be -perlabi ... Wipe away all these -monsters, Reader, with thy quill.

-
- - - -

- - - - - -
-
- Module for Default Text Structure -

The module described by the present chapter has the following - components: - - Default Text Structure - Default text structure - Structure textuelle par défaut - 預設文件結構 - Struttura standard del testo - Estrutura do texto por defeito - テキスト構造モジュール - - - - - - - - The selection and combination of modules to form a TEI schema is - described in .

-
-
diff --git a/P5/Source/Guidelines/fr/DS-DefaultTextStructure.xml b/P5/Source/Guidelines/fr/DS-DefaultTextStructure.xml new file mode 120000 index 0000000000..a6f5a1ffd8 --- /dev/null +++ b/P5/Source/Guidelines/fr/DS-DefaultTextStructure.xml @@ -0,0 +1 @@ +../en/./DS-DefaultTextStructure.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/Dedication.xml b/P5/Source/Guidelines/fr/Dedication.xml deleted file mode 100644 index fe156db83a..0000000000 --- a/P5/Source/Guidelines/fr/Dedication.xml +++ /dev/null @@ -1,24 +0,0 @@ - - - - -
- Dedication -

- - In memoriam - - Donald E. Walker - 22 November 1928 – 26 November 1993 - - - Antonio Zampolli - 1937 – 22 August 2003 - - - Sebastian Rahtz - 13 February 1955 – 15 March 2016 - - -

-
diff --git a/P5/Source/Guidelines/fr/Dedication.xml b/P5/Source/Guidelines/fr/Dedication.xml new file mode 120000 index 0000000000..e4cfe6538e --- /dev/null +++ b/P5/Source/Guidelines/fr/Dedication.xml @@ -0,0 +1 @@ +../en/./Dedication.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/FM1-IntroductoryNote.xml b/P5/Source/Guidelines/fr/FM1-IntroductoryNote.xml deleted file mode 100644 index 1ab7864174..0000000000 --- a/P5/Source/Guidelines/fr/FM1-IntroductoryNote.xml +++ /dev/null @@ -1,301 +0,0 @@ - - - - - -
- Preface and Acknowledgments - -

This publication constitutes the fifth distinct version of the - Guidelines for Electronic Text Encoding and - Interchange, and the first complete revision since the - appearance of P3 in 1994. It includes substantial amounts of new - material and a major revision of the underlying technical - infrastructure. With this version, these Guidelines enter a new stage in - their development as a community-maintained open source project. This - edition is the first version to have benefitted from the close - overview and oversight of an elected TEI Technical Council. The - editors are therefore particularly pleased to acknowledge with - gratitude the hard work and dedication put into this project by the - Council over the last five years.

- -

The Chair of the TEI Board sits on the Technical Council, and the - Board appoints the Chair of the Technical Council and one other - member of the Council. Other Council members are all elected by the - Consortium membership, and serve periods of up to two years at a - time. The names and affiliations of all Council members who served - during the production of this edition of the Guidelines are listed - below. - - - Board Chair - 2004–2005: Julia Flanders (Brown University) - 2006: Matthew Zimmerman (New York University) - 2007–2011: Daniel O'Donnell (University of Lethbridge) - 2011: Martin Mueller (Northwestern University) - 2011–2012: John Unsworth (University of Illinois at Urbana-Champaign / Brandeis University) - 2012–2015: Elena Pierazzo (King's College London / Université Stendhal-Grenoble 3) - 2016–2017: Michelle Dalmau (Indiana University) - 2018–2021: Kathryn Tomasek (Wheaton College) - 2022-2023: Diane K. Jakacki (Bucknell University) - - - - Technical Council Chair - 2002–2003: John Unsworth (University of Virginia) - 2003–2007: Christian Wittern (Kyoto University) - 2008–2011: Laurent Romary (Max Planck Digital Library / Inria & Humboldt-Universität zu Berlin) - 2012–2014: James Cummings (University of Oxford) - 2015–2017: Hugh Cayless (Duke University) - 2018–2022: Martina Scholger (University of Graz) - 2023: Elisa Beshero-Bondar (Penn State Erie, The Behrend College) - - - - Members of the Technical Council Appointed by the TEI Board - 2001–2009: Sebastian Rahtz (University of Oxford) - 2010–2014: Lou Burnard (University of Oxford / TGE Adonis / Independent Consultant) - - - - Appointed Editors - 2001–2007: Syd Bauman (Brown Univesity) - 2001–2007: Lou Burnard (University of Oxford) - - - - Elected Members of the Technical Council - 2011–2012: Piotr Bański (University of Warsaw) - 2010–2013: Brett Barney (University of Nebraska) - 2013–2023: Syd Bauman (Brown University / Northeastern University) - 2021–2025: Helena Bermúdez Sabel (Université de Neuchâtel / JinnTec) - 2016–2024: Elisa Beshero-Bondar (University of Pittsburgh at Greensburg / Penn State Erie, The Behrend College) - 2022: Elli Bleeker (Huygens Institute for the History of the Netherlands) - 2019–2020: Vanessa Bigot Juloux (Ecole Pratique des Hautes Etudes / Paris Sciences et Lettres / Andrews University, Michigan) - 2003–2006, 2017–2018: Alejandro Bia (University of Alicante) - 2004–2007: David Birnbaum (University of Pittsburgh) - 2008–2013: Gabriel Bodard (King's College London) - 2008–2009: Peter Boot (Huygens Institute for Netherlands History) - 2020–2021: Meaghan Brown (Papers of the Bibliographical Society of America) - 2007–2008: Tone Merete Bruvik (University of Bergen) - 2015–2016: Lou Burnard (Independent Consultant) - 2013–2023: Hugh Cayless (New York University / Duke University) - 2014–2015: Fabio Ciotti (University of Rome “Tor Vergata”) - 2007–2009: Arianna Ciula (King's College London / European Science Foundation) - 2005–2019: James Cummings (University of Oxford / Newcastle University) - 2020: Nicholas Cole (Pembroke College Oxford) - 2002–2007, 2010: Matthew Driscoll (University of Copenhagen) - 2002–2004: David Durand (Ingenta plc) - 2002–2004: Tomas Erjavec (Jozef Stefan Institute, Ljubljana) - 2014–2015: Stefanie Gehrke (Biblissima) - 2010–2013: Kevin Hawkins (University of Michigan) - 2010–2015: Martin Holmes (University of Victoria) - 2002: Fotis Jannidis (University of Munich) - 2021–2023: Janelle Jenstad (University of Victoria) - 2006: Amit Kumar (University of Illinois at Urbana-Champaign) - 2020–2021: Jessica H. Lu (University of Maryland) - 2015–2016: Stefan Majewski (Austrian National Library) - 2002: Martin Mueller (Northwestern University) - 2013–2014, 2016–2019: Elli Mylonas (Brown University) - 2010–2011: Julianne Nyhan (University of Trier / University College London) - 2023-2025: Patricia O Connor (Independent Researcher) - 2008–2011: Elena Pierazzo (King's College London) - 2006–2007, 2009–2010: Dot Porter (University of Kentucky / Digital Humanities Observatory / Indiana University) - 2002–2003: Merillee Proffitt (Research Libraries Group) - 2002: Peter Robinson (De Montfort University) - 2009–2014: Sebastian Rahtz (University of Oxford) - 2002: Geoffrey Rockwell (Macmaster University) - 2002–2007: Laurent Romary (Inria / CNRS / Max Planck Digital Library) - 2008–2009, 2012–2015: Paul Schaffner (University of Michigan) - 2016–2024: Martina Scholger (University of Graz) - 2003–2007: Susan Schreibman (University of Maryland) - 2022-2024: Sabine Seifert (University of Potsdam) - 2008–2009: David Sewell (University of Virginia) - 2004–2005: Natasha Smith (University of North Carolina at Chapel Hill) - 2014–2022: Peter Stadler (Carl-Maria-von-Weber-Gesamtausgabe / University of Paderborn) - 2017–2019: Sarah Stanley (Florida State University) - 2023: Joey Takeda (Digital Humanities Innovation Lab, Simon Fraser University) - 2008–2009: Manfred Thaller (University of Cologne) - 2006–2007: Conal Tuohy (Victoria University of Wellington) - 2016–2024: Magdalena Turska (eXist Solutions / University of Oxford) - 2004–2005: Edward Vanhoutte (Royal Academy of Dutch Language and Literature) - 2015–2023: Raffaele Viglianti (University of Maryland) - 2005–2008: John Walsh (Indiana University) - 2012–2013: Rebecca Welzenbach (University of Michigan) - 2002–2005: Perry Willett (Indiana University / University of Michigan) - 2011–2012: Stuart Yeates (New Zealand Electronic Text Centre) - -

- -

The bulk of the Council's work has been carried out by email and by -regular telephone conference. In addition, the Council has held many -two-day face-to-face meetings. During production of P5, -these meetings were generously hosted by the following institutions: - - King's College, London (2002) - Oxford University Computing Services (2003) - Royal Academy of Dutch Language and Literature, Ghent (2004) - AFNOR: Association française de normalisation, Paris (2005) - Institute for Research in Humanities, Kyoto University (2006) - Berlin-Brandenburgische Akademie der Wissenschaften, Berlin (2007) - National University of Ireland, Galway (2008) - Ecole Normale Supérieure, Lyon (2009) - Royal Irish Academy, Dublin (2010) - Big Ten Center, Chicago (2011) - Inria, Paris (2011) - University of Michigan, Ann Arbor (2012) - University of Oxford (2012) - Brown University (2013) - University of Oxford (2013) - University of Oxford (2014) - Duke University (2014) - University of Michigan, Ann Arbor (2015) - Lyon (2015) - Brown University (2016) - Austrian Academy of Sciences (2016) - Prague (2017) - Victoria (2017) - CCEH, Cologne University (2018) - University of Tokyo (2018) - Folger Shakespeare Library, Washington, D.C. (2019) - ZIM-ACDH, University of Graz (2019) - Virtual meeting (May 2020) - Virtual meeting (October 2020) - Short virtual meeting (January 2021) - Short virtual meeting (May 2021) - Short virtual meeting (October 2021) - Short virtual (April 2022) - Newcastle University (September 2022) - University of Guelph (May 2023) - Paderborn University (September 2023) -

- -

During the production of TEI P5, the Council chartered a number -of smaller workgroups and similar activities, each of which -made significant contribution to the intellectual content of the -work. Active members of these are listed below: - - - -

Active between July 2001 and January 2005, this group revised and -developed the recommendations now forming chapters -and . It was chaired by Christian Wittern, and its -membership included: Deborah Anderson (Berkeley); Michael Beddow -(independent scholar); David Birnbaum (University of Pittsburgh); -Martin Duerst (W3C/Keio University); -Patrick Durusau (Society of Biblical Literature); -Tomohiko Morioka (Kyoto University); - and Espen Ore (National Library of Norway).

- - - - -

Active between February 2003 and February 2005, this group developed the -material now forming . It was chaired by Sebastian -Rahtz, and its membership included: -Alejandro Bia; -David G. Durand; -Laurent Romary; -Norman Walsh (Sun Microsystems); -and Christian Wittern.

- - - - -

Active between February 2002 and January 2006, this -group reviewed and expanded the -material now largely forming part of . It was -chaired by David G. Durand, and its membership included: -Jean Carletta (Edinburgh University); -Chris Caton (University of Oxford); -Jessica P. Hekman (Ingenta plc); -Nancy M. Ide (Vassar College); -and -Fabio Vitali (University of Bologna).

 - - - -

Active between February 2003 and December 2005, this group reviewed -and finalised the material now forming . It was -chaired by Matthew Driscoll and comprised David Birnbaum and Merrilee -Proffitt, in addition to the TEI Editors.

- - - -

Active between January 2006 and May 2007, this group formulated the -new material now forming part of . It was chaired -by Matthew Driscoll. and its membership included -Gabriel Bodard (King's College London); -Arianna Ciula; -James Cummings; -Tom Elliott (University of North Carolina at Chapel Hill); -Øyvind Eide (University of Oslo); -Leif Isaksen (Oxford Archaeology plc); -Richard Light (private consultant); -Tadeusz Piotrowski (Opole University); -Sebastian Rahtz; -and -Tatiana Timcenko (Vilnius University). -

- - - - -

Active between January 2003 and August 2007, this group reviewed the -material now presented in and revised it for -inclusion in ISO Standard 24610. It was chaired by Kiyong Lee (Korea -University), and its active membership included the following: -Harry Bunt (Tilburg); -Lionel Clément (INRIA); -Eric de la Clergerie (INRIA); -Thierry Declerck (Saarbrücken); -Patrick Drouin (University of Montréal); -Lee Gillam (Surrey University); -and -Kōiti Hasida (ICOT). -

-

- -

From 2000 to 2008 the TEI had two appointed Editors, Lou Burnard - (University of Oxford) and Syd Bauman (Brown University), who served - ex officio on the Council and, as far as possible, - on all Council workgroups.

- - -

The Council also oversees an Internationalization and Localization -project, led by Sebastian Rahtz and with funding from the ALLC. This -activity, ongoing since October 2005, is engaged in translating key -parts of the P5 source into a variety of languages.

- -

Production of the translations currently included in P5 has been -coordinated by the following: - - Marcus Bingenheimer (Chung-hwa Institute -of Buddhist Studies, Taipei / Temple University) and Weining Hwang (Würzburg University) -Pierre-Yves Duchemin (ENSSIB); Jean-Luc -Benoit (ATILF); Anila Angjeli (BnF); Joëlle Bellec Martini (BnF); -Marie-France Claerebout (Aldine); Magali Le Coënt (BIUSJ); Florence -Clavaud (EnC); Cécile Pierre (BIUSJ). - - Werner Wegstein (Würzburg University), Franz Fischer (Cologne University), Martina Scholger (University of Graz) and Peter Stadler (Paderborn University) -Marco Venuti (University of Venice) and Letizia Cirillo -(University of Bologna) - Ohya Kazushi (Tsurumi University), Kiyonori Nagasaki (University of Tokyo) and Martin Holmes (University of Victoria) -Beom-mo Kang and Jungha Hong (Korea University) - Carmen Arronis Llopis (University of - Alicante), Alejandro Bia (Miguel Hernández University), Gimena del Rio Riande (Consejo Nacional de Investigaciones Científicas y Técnicas) and Susanna Allés-Torrent (University of Miami) - -

- -

Any one who works closely with the TEI Guidelines, whether as -translator, editor, or reader is constantly reminded of the -ambitious scope and exceptionally high editorial standards set by the original -project, now approaching twenty years ago. It is appropriate therefore to retain -a sense of the history of this document, as it has evolved since its -first appearance in 1990, and to acknowledge with gratitude the -contributions made to that evolution by very many individuals and -institutions around the world. The original prefatory notes to each -major edition of the Guidelines recording these names are therefore -preserved in an appendix to the current edition (see ).

-
diff --git a/P5/Source/Guidelines/fr/FM1-IntroductoryNote.xml b/P5/Source/Guidelines/fr/FM1-IntroductoryNote.xml new file mode 120000 index 0000000000..cbe82c47b8 --- /dev/null +++ b/P5/Source/Guidelines/fr/FM1-IntroductoryNote.xml @@ -0,0 +1 @@ +../en/./FM1-IntroductoryNote.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/FS-FeatureStructures.xml b/P5/Source/Guidelines/fr/FS-FeatureStructures.xml deleted file mode 100644 index 989a676e90..0000000000 --- a/P5/Source/Guidelines/fr/FS-FeatureStructures.xml +++ /dev/null @@ -1,2025 +0,0 @@ - - - - -
Feature Structures - -

A feature structure is a general purpose data -structure which identifies and groups together individual -features, each of which associates a name with one or -more values. Because of the generality of feature structures, they -can be used to represent many different kinds of information, but they -are of particular usefulness in the representation of linguistic -analyses, especially where such analyses are partial, or -underspecified. Feature structures represent the -interrelations among various pieces of information, and their -instantiation in markup provides a metalanguage for the -generic representation of analyses and interpretations. Moreover, -this instantiation allows feature values to be of specific -types, and for restrictions to be placed on the values -for particular features, by means of feature system -declarations.The recommendations of this chapter have -been adopted as ISO Standard 24610-1 Language Resource -Management — Feature Structures — Part One: Feature Structure Representation -

-
Organization of this Chapter -

This chapter is organized as -follows. Following this introduction, section -introduces the elements fs and f, used to represent -feature structures and features respectively, together with the -elementary binary feature value. Section introduces elements for representing other kinds of -atomic feature values such as symbolic, -numeric, and string values. Section introduces the notion of predefined -libraries or groups of features or feature values along -with methods for referencing their components. Section introduces complex values, in particular -feature-structures as values, thus enabling feature structures to be -recursively defined. Section discusses other -complex values, in particular values which are collections, organized -as sets, bags, and -lists. Section discusses how the -operations of alternation, negation, and collection of feature values -may be represented. Section discusses ways of -representing underspecified, default, or uncertain values. Section - discusses how analyses may be linked to other -parts of an encoded text. Section describes the -feature system declaration, a construct which provides -for the validation of typed feature structures. - -Formal definitions for -all the elements introduced in this chapter are provided in section -.

- - -
- -
Elementary Feature Structures and the Binary -Feature Value -

The fundamental elements used to represent a feature structure -analysis are f (for feature), which represents a -feature-value pair, and fs (for feature -structure), which represents a structure made up of such -feature-value pairs. The fs element has an optional -type attribute which may be used to represent typed feature -structures, and may contain any number of f elements. An -f element has a required name attribute and an -associated value. The value may be simple: that is, a -single binary, numeric, symbolic (i.e. taken from a restricted set of -legal values), or string value, or a collection of such values, -organized in various ways, for example, as a list; or it may be -complex, that is, it may itself be a feature structure, thus providing -a degree of recursion. Values may be under-specified or defaulted in -various ways. These possibilities are all described in more detail in -this and the following sections. -

-

Feature and feature-value representations (including feature -structure representations) may be embedded directly at any point in an -XML document, or they may be collected together in special-purpose -feature or feature-value libraries. The components of -such libraries may then be referenced from other feature or -feature-value representations, using the feats or -fVal attribute as appropriate.

-

We begin by considering the simple case of a feature structure -which contains binary-valued features only. The following three XML elements are -needed to represent such a feature structure: - - - - - -The attributes feats and the fVal are not -discussed in this section: they provide an alternative way of -indicating the content of an element, as further discussed in section -. -

-

An fs element containing f elements with binary -values can be straightforwardly used to encode the matrices -of feature-value specifications for phonetic segments, such as the -following for the English segment [s]. - +--- ---+ -| consonantal + | -| vocalic - | -| voiced - | -| anterior + | -| coronal + | -| continuant + | -| strident + | -+--- ---+ -

-

This representation may be encoded in XML as follows: - - - - - - - - - -Note that fs elements may have an optional type -attribute to indicate the kind of feature structure in question, -whereas f elements must have a name attribute to -indicate the name of the feature. Feature structures need not be -typed, but features must be named. - - -Similarly, the fs element -may be empty, but the f element must specify its value either -directly as content, by means of the fVal attribute, or -implicitly by reference to a feature system declaration.

-

The restriction of specific features to specific types of values -(e.g. the restriction of the feature strident -to a binary value) requires additional validation, as does any -restriction on the features available within a feature structure of a -particular type (e.g. whether a feature structure of type -phonological segment necessarily contains a -feature voiced). Such validation may be carried -out at the document level, using special purpose processing, at the -schema level using additional validation rules, or at the declarative -level, using an additional mechanism such as the feature-system -declaration discussed in .

-

Although we have used the term binary for this kind -of value, and its representation in XML uses values such as -true and false (or, equivalently, -1 and 0), it should be noted that such -values are not restricted to propositional assertions. As this example -shows, this kind of value is intended for use with any binary-valued -feature.

- -
-
Other Atomic Feature Values -

Features may take other kinds of atomic value. In this section, we -define elements which may be used to represent: symbolic -values, numeric values, and string -values. The module defined by this chapter allows for the -specification of additional datatypes if necessary, by extending the -underlying class model.featureVal.single. If this is done, it -is recommended that only the basic W3C datatypes should be used; more -complex datatyping should be represented as feature structures. - - - - -

-

The symbol element is used for the value of a feature when -that feature can have any of a small, finite set of possible values, -representable as character strings. For example, the following might -be used to represent the claim that the Latin noun form -mensas -(tables) has accusative case, feminine gender, and -plural number: - - - - -

-

More formally, this representation shows a structure in which three -features (case, gender, and -number) are used to define morpho-syntactic properties of -a word. Each of these features can take one of a small number of -values (for example, case can be nominative, -genitive, dative, accusative, -etc.) and it is therefore appropriate to represent the values taken -in this instance as symbol elements. Note that, instead of -using a symbolic value for grammatical number, one could have named -the feature singular or plural and given it -an appropriate binary value, as in the following example: - - - - -Whether one uses a binary or symbolic value in situations like this is -largely a matter of taste.

-

The string element is used for the value of a -feature when that value is a string drawn from a very large or potentially -unbounded set of possible strings of characters, so that it would be -impractical or impossible to use the symbol element. The string -value is expressed as the content of the string element, -rather than as an attribute value. For example, one might encode a -street address as follows: - - 3418 East Third Street -

-

The numeric element is used when the value of a feature is a -numeric value, or a range of such values. For example, one might wish -to regard the house number and the street -name as different features, using an encoding like the following: - - - East Third Street -

-

If the numeric value to be represented falls within a specific -range (for example an address that spans several numbers), the -max attribute may be used to supply an upper limit: - - - East Third Street -

-

It is also possible to specify that the numeric value (or values) -represented should (or should not) be truncated. For example, assuming -that the daily rainfall in mm is a feature of interest for some -address, one might represent this by an encoding like the following: - - - This represents any of the infinite -number of numeric values falling between 0 and 1.3; by contrast - - - represents only two possible values: 0 and 1. -

-

Some communities of practice, notably those with a strong computer-science -bias, prefer to dissociate the information on the value of the given -feature from the specification of the data type that this value represents. -In such cases, feature values can be provided directly as textual content -of f, with the assumption that the data type is specified by the -schema. The following is an example taken from ISO 24612, presenting the -symbolic values for Active Voice and Simple Present Tense in the untyped -form:active -SimPre

-

As noted above, additional processing is necessary to ensure that -appropriate values are supplied for particular features, for example -to ensure that the feature singular is not given a value -such as symbol value="feminine"/. There are two -ways of attempting to ensure that only certain combinations of feature -names and values are used. First, if the total number of legal -combinations is relatively small, one can predefine all of them in a -construct known as a feature library, and then reference -the combination required using the feats attribute in the -enclosing fs element, rather than give it explicitly. This -method is suitable in the situation described above, since it requires -specifying a total of only ten (5 + 3 + 2) combinations of features -and values. Similarly, to ensure that only feature structures -containing valid combinations of feature values are used, one can put -definitions for all valid feature structures inside a feature -value library (so called, since a feature structure may be the -value of a feature). A total of 30 feature structures (5 × 3 -× 2) is required to enumerate all the possible combinations of -individual case, gender and number values in the preceding -illustration. We discuss the use of such libraries and their -representation in XML further in section below. -

-

However, the most general method of attempting to ensure that only legal -combinations of feature names and values are used is to provide a -feature-system declaration discussed in .

-

Whether at the level of feature-system declarations, feature- and -feature-value libraries, or individual features, it is possible to -align both feature names and their values with standardized external -data category repositories. See -section for more discussion of the need and -rationale for aligning the content of grammatical (and other) descriptions with -standardized external taxonomies. In the following example, both -the feature part_of_speech and its value -NN (standing for common noun) are aligned with the respective definitions -provided by the CLARIN Concept Registry (CCR). - - - - - - - -

-

Since the above representation takes up a lot of space and quickly becomes redundant and -error-prone, it is possible to delegate the task of aligning with external repositories to -elements such as fLib, fvLib, fDecl, or fsDecl to reduce the feature -representation at hand and to increase its readability at the same time, as shown in the example below. - - - - - - -

-

The value common_noun should best be listed (as an xml:id) either in a -library of feature values (fvLib, see the following section) or in a -taxonomy element.

-
-
Feature Libraries and Feature-Value Libraries -

As the examples in the preceding section suggest, the direct -encoding of feature structures can be verbose. Moreover, it is often -the case that particular feature-value combinations, or feature -structures composed of them, are re-used in different analyses. To reduce -the size and complexity of the task of encoding feature structures, one -may use the feats attribute of the fs element to point -to one or more of the feature-value specifications for that element. This indirect method of -encoding feature structures presumes that the f elements are -assigned unique xml:id values, and are collected together in -fLib elements (feature libraries). In the same way, feature -values of whatever type can be collected together in fvLib elements -(feature-value libraries). If a feature has as its -value a feature structure or other value which is predefined in this way, the -fVal attribute may be used to point to it, as discussed in -the next section. The following elements are used for representing feature libraries and feature-value libraries: - - - -

-

For example, suppose a feature library for phonological feature -specifications is set up as follows. - - - - - - - - - - - - - - - - - -

-

Then the feature structures that represent the analysis of the -phonological segments (phonemes) /t/, /d/, -/s/, and /z/ may be defined as follows. - - - - -

-

The preceding are but four of the 128 logically possible fully -specified phonological segments using the seven binary features listed in -the feature library. Presumably not all combinations of features -correspond to phonological segments (there are no strident vowels, for -example). The legal combinations, however, can be collected together, -each one represented as an identifiable fs element within a -feature-value library, as in the following example: - - - - - - - - -

-

Once defined, these feature structure values can also be reused. -Other f elements may invoke them by reference, using the -fVal attribute; for example, one might use them in a -feature value pair such as: rather than expanding the hierarchy of the -component phonological features explicitly.

-

The feature structure that concludes section above, identifying the -value of some part of speech to be a common noun, may be used in tandem with a -feature-value library, which offers a way to encode a grammatical tagset, in this case -containing labels for parts of speech: - - - - - - - -Such a feature-value library combines the standard short symbolic label for a part of speech (e.g., NN) with a -mnemonic identifier that can be referenced by means of fVal, and with a persistent identifier, maintained -in a public reference taxonomy repository together with the basic definition of the given concept.

-

Feature structures stored in the way presented in this section may also be associated with -the text which they are intended to annotate, either by a link from the text -(for example, using the TEI global ana attribute), or -by means of stand-off annotation techniques (for example, using the TEI -link element): see further section -below. -

-

Note that when features or feature structures are linked to in this -way, the result is effectively a copy of the item linked to into the -place from which it is linked. This form of linking should be distinguished from -the phenomenon of structure-sharing, where it is desired -to indicate that some part of an annotation structure appears -simultaneously in two or more places within the structure. This kind -of annotation should be represented using the vLabel element, as -discussed in below.

-
-
Feature Structures as Complex Feature Values -

Features may have complex values as well as atomic ones; the -simplest such complex value is represented by supplying an fs -element as the content of an f element, or (equivalently) by -supplying the identifier of an fs element as the value for -the fVal attribute on the f -element. Structures may be nested as deeply as appropriate, using this -mechanism. For example, an fs element may contain or point -to an f element, which may contain or point to an fs -element, which may contain or point to an f element, and so -on.

-

To illustrate the use of complex values, consider the following -simple model of a word, as a structure combining surface form -information, a syntactic category, and semantic information. Each word -analysis is represented as a fs type='word' element, -containing three features named surface, -syntax, and semantics. The first of these -has an atomic string value, but the other two have complex values, -represented as nested feature structures of types -category and act respectively: - - love - - - - - - - - - - - -

-

This analysis does not tell us much about the meaning of the -symbols verb or transitive. It might be -preferable to replace these atomic feature values by feature -structures. Suppose therefore that we maintain a feature-value -library for each of the major syntactic categories (N, V, ADJ, PREP): - - - - - - - - - - -

-

This library allows us to use shortcut codes (N, -V, etc.) to reference a complete definition for the -corresponding feature structure. Each definition may be explicitly -contained within the fs element, as a number of f -elements. Alternatively, the relevant features may be referenced by -their identifiers, supplied as the value of the feats -attribute, as in these examples: -<!-- ... --> -<fs xml:id="ADJ" type="adjective" feats="#F1 #F2"/> -<fs xml:id="PREP" type="preposition" feats="#F1 #F3"/> -<!-- ... --> - -

-

This ability to re-use feature definitions within multiple feature -structure definitions is an essential simplification in any realistic -example. In this case, we assume the existence of a feature library -containing specifications for the basic feature categories like the following: - - - - - - - - -

-

With such libraries in place, and assuming the availability of -similarly predefined feature structures for transitivity and -semantics, the preceding example could be considerably simplified: - -love - - - - - - - - - - - - -

-

Although in principle the fVal attribute could point to -any kind of feature value, its use is not recommended for simple -atomic values.

-
-
Re-entrant Feature Structures -

Sometimes the same feature value is required at multiple places -within a feature structure, in particular where the value is only -partially specified at one or more places. The vLabel element is -provided as a means of labelling each such re-entrancy point: - - - -

-

For example, suppose one wishes to represent noun-verb agreement as -a single feature structure. Within the representation, the feature -indicating (say) number appears more than once. To represent the fact -that each occurrence is another appearance of the same feature (rather -than a copy) one could use an encoding like the following: - - - - - - - - - - - - - - - - - - - - -

-

In the above encoding, the features named vb-num and -nm-num exhibit structure sharing. Their values, given as -vLabel elements, are understood to be references to the same -point in the feature structure, which is labelled by their -name attribute.

-

The scope of the names used to label re-entrancy points is that of the -outermost fs element in which they appear. When a feature -structure is imported from a feature value library, or referenced from -elsewhere (for example by using the fVal attribute) the -names of any -sharing points it may contain are implicitly prefixed by the identifier used -for the imported feature structure, to avoid name clashes. Thus, if -some other feature structure were to reference the fs element - given in the example above, for example in this way: then -the labelled points in the example would be interpreted as if they had the -name NVAL1.

-
-
Collections as Complex Feature Values -

Complex feature values need not always be represented as feature -structures. Multiple values may also be organized as sets, bags or -multisets, or lists of atomic values of any type. The vColl -element is provided to represent such cases: - - - -

-

A feature whose value is regarded as a set, bag, or list may have -any positive number of values as its content, or none at -all, (thus allowing for representation of the empty set, bag, or list). -The items in a list are ordered, and need not be distinct. The items -in a set are not ordered, and must be distinct. The items in a bag are -neither ordered nor distinct. Sets and bags are thus distinguished -from lists in that the order in which the values are specified does -not matter for the former, but does matter for the latter, while sets -are distinguished from bags and lists in that repetitions of values do -not count for the former but do count for the latter. -

-

If no value is specified for the org attribute, the -assumption is that the vColl defines a list of values. If the -vColl element is empty, the assumption is that it represents -the null list, set, or bag.

-

To illustrate the use of the org attribute, suppose that -a feature structure analysis is used to represent a genealogical tree, -with the information about each individual treated as a single feature -structure, like this: - - - - Daniel - Edouard - - - - - - - - - - - - - - - -

-

In this example, the vColl element is first used to supply -a list of name feature values, which together -constitute the forenames feature. Other features -are defined by reference to values which we assume are held in some -external feature value library (not shown here). For example, the -vColl element is used a second time to indicate that the -persons's siblings should be regarded as constituting a set rather -than a list. Each sibling is represented by a feature structure: in -this example, each feature structure is a copy of one specified in the -feature value library.

-

If a specific feature contains only a single feature structure as -its value, the component features of which are organized as a set, bag, -or list, it may be more convenient to represent the value as a -vColl rather than as an fs. For example, consider the -following encoding of the English verb form -sinks, which contains an -agreement feature whose value is a feature -structure which contains person and -number features with symbolic values. - - - - - - - - - - -

-

If the names of the features contained within -the agreement feature structure are -of no particular significance, the following simpler representation -may be used: - - - - - - - - - - -

-

The vColl element is also useful in cases where an analysis -has several components. In the following example, the French -word auxquels has a two-part analysis, -represented as a list of two values. The first specifies that the word contains a -preposition; the second that it contains a masculine plural relative -pronoun: - - - - - - - - - - - - - - - - - - -

-

The set, bag, or list which has no members is known as the null (or -empty) set, bag, or list. A vColl element with no content and -with no value for its feats attribute is interpreted as -referring to the null set, bag, or list, depending on the value of its -org attribute.

-

If, for example, the individual described by the -feature structure with identifier p027 (above) had no siblings, we might specify the -siblings feature as follows. - -

-

A vColl element may also collect together one or more other -vColl elements, if, for example one of the members of a set is -itself a set, or if two lists are concatenated together. Note that -such collections pay no attention to the contents of the nested -vColl elements: if it is desired to produce the union of two -sets, the vMerge element discussed below should be used to -make a new collection from the two sets.

-
-
Feature Value Expressions -

It is sometimes desirable to express the value of a feature as the -result of an operation over some other value (for example, as -not green, or as male or -female, or as the concatenation of two collections). Three -special purpose elements are provided to represent disjunctive -alternation, negation, and collection of values: - - - - - -

-
Alternation -

The vAlt element can be used wherever a feature value can -appear. It contains two or more feature values, any one of which is to -be understood as the value required. Suppose, for example, that we are -using a feature system to describe residential property, using such -features as number.of.bathrooms. In a -particular case, we might wish to represent uncertainty as to whether -a house has two or three bathrooms. As we have already shown, one -simple way to represent this would be with a numeric maximum: - -

-

A more general way would be to represent the -alternation explicitly, in this way: - -

-

The vAlt element represents alternation over feature -values, not feature-value pairs. If therefore the uncertainty relates -to two or more feature value specifications, each must be represented -as a feature structure, since a feature structure can always appear -where a value is required. For example, suppose that it is uncertain -as to whether the house being described has two bathrooms or two -bedrooms, a structure like the following may be used: - - - - - - -

-

Note that alternation is always regarded as exclusive: -in the case above, the implication is that having two bathrooms -excludes the possibility of having two bedrooms and vice versa. If -inclusive alternation is required, a vColl element may be -included in the alternation as follows: - - - - - - - - - -This analysis indicates that the property may have two bathrooms, two -bedrooms, or both two bathrooms and two bedrooms. -

-

As the previous example shows, the vAlt element can also -be used to indicate alternations among values of features organized as -sets, bags or lists. Suppose we use a feature -selling.points to describe items that are mentioned to -enhance a property's sales value, such as whether it has a pool or a -good view. Now suppose for a particular listing, the selling points include -an alarm system and a good view, and either a pool or a jacuzzi (but -not both). This situation could be represented, using the -vAlt element, as follows. - - - - alarm system - good view - - pool - jacuzzi - - - - -

-

Now suppose the situation is like the preceding except that one is -also uncertain whether the property has an alarm system or a good -view. This can be represented as follows. - - - - - alarm system - good view - - - pool - jacuzzi - - - - -

-

If a large number of ambiguities or uncertainties need to be -represented, involving a relatively small number of features and -values, it is recommended that a stand-off technique, for example -using the general-purpose alt element discussed in -section be used, rather than the -special-purpose vAlt element. -

-
-
Negation -

The vNot element can be used wherever a feature value can -appear. It contains any feature value and returns the complement of -its contents. For example, the feature -number.of.bathrooms in the following example -has any whole numeric value other than 2: - -

-

Strictly speaking, the effect of the vNot element is to -provide the complement of the feature values it contains, rather than -their negation. If a feature system declaration is available which defines the -possible values for the associated feature, then it is possible to say -more about the negated value. For example, suppose that the -available values for the feature case are declared to be -nominative, genitive, dative, or accusative, whether in a TEI feature -system declaration or -by some other means. Then the following two specifications are equivalent: - (i) - -(ii) - - - - - - -

-

If however no such system declaration is available, all that one -can say about a feature specified via negation is that its value is -something other than the negated value.

-

Negation is always applied to a feature value, rather than to a -feature-value pair. The negation of an atomic value is the set of all -other values which are possible for the feature.

-

Any kind of value can be negated, including collections -(represented by a vColl elements) or feature structures -(represented by fs elements). The negation of any complex -value is understood to be the set of values which -cannot be unified with it. Thus, for example, the negation of the -feature structure F is understood to be the set of feature structures -which are not unifiable with F. In the absence of a constraint -mechanism such as the Feature System Declaration, the negation of a -collection is anything that is not unifiable with it, including -collections of different types and atomic values. It will generally be -more useful to require that the organization of the negated value be -the same as that of the original value, for example that a negated set -is understood to mean the set which is a complement of the set, but -such a requirement cannot be enforced in the absence of a constraint -mechanism.

-
-
Collection of Values -

The vMerge element can be used wherever a feature value can -appear. It contains two or more feature values, all of which are to be -collected together. The organization of the resulting collection is -specified by the value of the org attribute, which need -not necessarily be the same as that of its constituent values if these -are collections. For example, one can change a list to a set, or vice versa.

-

As an example, suppose that we wish to represent the range of -possible values for a feature genders used to -describe some language. It would be natural to represent the possible -values as a set, using the vColl element as in the following -example: - - - - - - - - - -

-

Suppose however that we discover for some language it is necessary -to add a new possible value, and to treat the value of the -feature as a list rather than as a set. The vMerge element can -be used to achieve this: - - - - - - - - - - - - -

- -
-
-
Default Values -

The value of a feature may be underspecified in a number of -different ways. It may be null, unknown, or uncertain with respect to -a range of known possibilities, as well as being defined as a negation -or an alternation. As previously noted, the specification of the range -of known possibilities for a given feature is not part of the current -specification: in the TEI scheme, this information is conveyed by the -feature system declaration. Using this, or some other -system, we might specify (for example) that the range of values -for an element includes symbols for masculine, feminine, and neuter, -and that the default value is neuter. With such definitions available -to us, it becomes possible to say that some feature takes the default -value, or some unspecified value from the list. The following special -element is provided for this purpose: - - - -

-

The value of an empty f element which also lacks an fVal -attribute is understood to be the most general -case, i.e. any of the available values. Thus, assuming the feature -system defined above, the following two representations are equivalent. - - - - - - - - -

-

If, however, the value is explicitly stated to be the default one, -using the default element, then the following two representations -are equivalent: - - -

-

Similarly, if the value is stated to be the negation of the -default, then the following two representations are equivalent: - - - - - -

-
- - -
Linking Text and Analysis -

Text elements can be linked with feature structures using any of -the linking methods discussed elsewhere in these Guidelines (see for -example sections and ). -In the simplest case, the ana attribute may be used -to point from any element to an annotation of it, as in the following -example: - - The - closest - he - came - to - exercise - was - to - open - one - eye - - every - so - often - - , - if - someone - entered - the - room - - -

-

The values specified for the ana attribute reference -components of a feature-structure library, which represents all of the -grammatical structures used by this encoding scheme. (For illustrative -purposes, we cite here only the structures needed for the first six -words of the sample sentence): - - - - - - - - - - -The components of each feature structure in the library are -referenced in much the same way, using the -feats attribute to identify one or more f -elements in the following feature library (again, only a few of the -available features are quoted here): - - - - - - - - - - - - - - - - - -

-

Alternatively, a stand-off technique may be used, as in the following -example, where a linkGrp element is used to link selected -characters in the text Caesar seized control with -their phonological representations. - - - Caesar - seized - control. - - - - - - - - - - - - -

-

As this example shows, a stand-off solution requires that every -component to be linked to must be addressable in some way, by means of -an XPointer. To handle the -POS tagging example above, for example, each annotated element might be -given an identifier of some sort, as follows: - - The - closest - he - came - to - exercise - -It would then be possible to link each word to its intended -annotation in the feature library quoted above, as follows: - - - - - - - - -

-
- - -
-Feature System Declaration -

The Feature System Declaration (FSD) is intended for use in conjunction with a - TEI-conforming text that makes use of fs (that is, feature structure) elements. - The FSD serves three purposes: - the encoder can list all of the feature names and feature values and give a prose - description as to what each represents. - the encoder can define what it means to be a well-formed feature structure, and - define constraints which may be used to determine whether a particular feature - structure is valid relative to a given theory stated in typed feature - logic. These may involve constraints on the range of a feature value, - constraints on what features are valid within certain types of feature structures, or - constraints that prevent the co-occurrence of certain feature-value pairs. - the encoder can define the intended interpretation of underspecified feature - structures. This involves defining default values (whether literal or computed) for - missing features.

-

The scheme described in this chapter may be used to document any -feature structure system, but is primarily intended for use with the -feature structure representation defined by the ISO 24610-1:2006 -standard, which corresponds with the recommendations presented in -these Guidelines, . This chapter relies upon, but -does not reproduce, formal definitions and descriptions presented more -thoroughly in the ISO standard, which should be consulted in case of -ambiguity or uncertainty.

- -

The FSD serves an important function in documenting precisely what -the encoder intended by the system of feature structure markup used in -an XML-encoded text. The FSD is also an important resource which -standardizes the rules of inference used by software to validate the -feature structure markup in a text, and to infer the full -interpretation of underspecified feature structures.

- -

The reader should be aware the terminology used in this document -does not always closely follow conventional practice in formal logic, -and may also diverge from practice in some linguistic applications of -typed feature structures. In particular, the term -interpretation when applied to a feature -structure is not an interpretation in the model-theoretic sense, but -is instead a minimally informative (or equivalently, most general) -extension of that feature -structure that is consistent with a set of constraints declared by an -FSD. In linguistic application, such a system of constraints is the -principal means by which the grammar of some natural language is -expressed. There is a great deal of disagreement as to what, if any, -model-theoretic interpretation feature structures have in such -applications, but the status of this formal kind of interpretation is -not germane to the present document. Similarly, the term -valid is used here as elsewhere in these -Guidelines to identify the syntactic state of well-formedness in the -sense defined by the logic of typed feature structures itself, as -distinct from and in addition to the -well-formedness that pertains at the level of -this encoding standard. No appeal to any notion from formal semantics -should be inferred.

- -

We begin by describing how an encoded text is associated with one -or more feature system declarations. The second, third, and fourth -sections describe the overall structure of a feature system -declaration and give details of how to encode its components. The final -section offers a full example; fuller discussion -of the reasoning behind FSDs and another complete example are provided -in .

-
-Linking a TEI Text to Feature System Declarations -

In order for application software to use feature system -declarations to aid in the automatic interpretation of encoded texts, -or even for human readers to find the appropriate declarations which -document the feature system used in markup, there must be a formal -link from the encoded texts to the declarations. However, the -schema which declares the syntax of the Feature System itself -should be kept distinct from the feature structure schema, which is an -application of that system.

- -

A document containing typed feature structures may simply include a -feature system declaration documenting those feature structures. A -more usual scenario, however, is that the same feature system -declaration (or parts of it) will be shared by many documents. In -either case, an fsDecl element for each distinct type of -feature structure used must be provided and associated with the type, -which is the value used within each feature structure for its -type attribute.

- -

When the module defined in this chapter is included in an XML -schema, the following elements become available via the -model.fsdDeclPart class: - - - - - - -The fsdDecl element serves as a wrapper for declaring feature -systems and may be supplied either within the header -of a standard TEI document, or as a standalone document in its own -right. It contains one or more fsdLink or fsDecl -elements and may hold several fLib or fvLib as well.

- - - -

For example, suppose that a document doc.xml -contains feature structures of two types: gpsg and -lex. We might simply embed an fsDecl element for -each within the header attached to the document as follows: - - - - - - - - - - - - - - - - - - - - - - - - - - -

-

In this case there is an implicit link between the fs -element and the corresponding fsDecl element because they -share the same value for their type attribute and appear -within the same document. This is a short cut for the more general -case which requires a more explicit link provided by means of the -fsdLink element, as demonstrated below.

- -

Now suppose that we wish to create a second document which includes -feature structures of the same type. Rather than duplicate the -corresponding declarations, we will need to provide a means of -pointing to them from this second document. The easiestWays of pointing to components of a TEI document without -using an XML identifier are discussed in -way of accomplishing this is to add an XML identifier to each -fsDecl element in example.xml: - - - - - - - - - - -(Although in this case the XML identifier is simply an uppercase -version of the type name, there is no necessary connection between the -two names. The only requirement is that the XML identifier conform to -the standards required for identifiers, and that it be unique within -the document containing it.)

-

In the fsdDecl for the second document, we can now include -pointers to the fsDecl elements in the first: - - - - - - - - - - - - - - - - - - - - - -Note that in doc2.xml there is no requirement for the local -name for a given type of feature structures to be the same as that -used by example.xml. We assume in this encoding that the type -called lexx in doc2.xml is declared as -having identical constraints and other properties to those declared -for the type called lex in example.xml.

- -

An fsdDecl may be given, as above, within the encoding -description of the teiHeader element of a TEI document -containing typed feature structures. Alternatively, it may appear -independently of any feature structures, as a document in its own -right with its own teiHeader. These options are both possible -because the element is a member of both the model.encodingDescPart class and the model.resource class.

- -

The current recommendations provide no way of enforcing uniqueness -of the type values among fsdDecl elements, nor of -requiring that every type value specified on an fs -element be also declared on an fsdDecl element. Encoders -requiring such constraints (which might have some obvious utility in -assisting the consistency and accuracy of tagging) are recommended to -develop tools to enforce them, using such mechanisms as Schematron -assertions.

- -
-
The Overall Structure of a Feature System Declaration -

A feature system declaration contains one or more feature -structure declarations, each of which has up to three parts: an optional description -(which gives a prose comment on what that type of feature structure -encodes), an obligatory set of feature declarations (which specify -range constraints and default values for the features in that type of -structure), and optional feature structure constraints (which specify -co-occurrence restrictions on feature values). - - - -

-

Feature declarations and feature structure constraints are -described in the next two sections. Note that the specification of -similar fsDecl elements can be simplified by devising an -inheritance hierarchy for the feature structure types. Each -fsDecl element may name one or more -basetypes from which it inherits feature -declarations and constraints (these are often called -supertypes). For instance, suppose that -fsDecl type="Basic" contains fDecl name="One" -and fDecl name="Two", and that fsDecl type="Derived" -baseTypes="Basic" contains just fDecl name="Three". -Then any instance of fs type="Derived" must include all -three features. This is because fsDecl type="Derived" -inherits the two feature declarations from fsDecl -type="Basic" when it specifies a base type of -Basic.

-

The following sample shows the overall structure of a complete -feature structure declaration: - - - Describes what this type of fs represents - - - - - - - - - - -

- -

The attribute baseTypes gives the name of one or more -types from which this type inherits feature specifications and -constraints; if this type includes a feature specification with the -same name as one inherited from any of the types specified by this -attribute, or if more than one specification of the same name is -inherited, then the possible values of that feature is determined by -unification. Similarly, the set of constraints applicable is derived -by conjoining those specified explicitly within this element with -those implied by the baseTypes attribute. When no base type -is specified, no feature specification or constraint is inherited.

-

Although the present standard does provide for default feature values, -feature inheritance is defined to be monotonic. -

-The process of combining constraints may result in a contradiction, -for example if two specifications for the same feature specify -disjoint ranges of values, and at least one such specification is -mandatory. In such a case, there is no valid feature structure of the -type being defined.

-

-Every type specified by baseTypes must be a single word which -is a legal XML name; for example, they cannot include whitespace or -begin with digits. Multiple base types are separated with spaces, -e.g. fsDecl type="Sub" baseTypes="Super1 Super2".

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-
Feature Declarations -

Each feature is declared in an fDecl element whose -name attribute identifies the feature being declared; this -matches the name attribute of the f elements it -declares. - - -An fDecl has three parts: an optional -prose description (which should explain what the feature and its -values represent), an obligatory range specification (which declares -what values the feature is allowed to have), and an optional default -specification (which declares what default value should be supplied -when the named feature does not appear in an fs). -If, in a feature -structure, a feature: - is not optional (i.e., is obligatory), - has no value provided, or the value default is -provided (see ISO 24610-1, Subclause 5.10, Default Values, and - either has no default specified, or has conditional defaults, -none of the conditions on which is met, - -then the value of this feature in the feature structure's most -general valid extension is the most general value provided in its -vRange, in the case of a unit organization, or the -singleton set, bag, or list containing that element, in the case of a -complex organization. If the feature: - is optional, - has no value provided, or the value default is -provided, and - either has a default specified, or has conditional defaults, -one of the conditions on which is met, - -then this feature does have a value in the feature structure's most -general valid extension when it exists, namely the default value that -pertains. -

-

It is possible that a feature structure will not have a valid -extension because the default value that pertains to a feature is not -consistent with that feature's declared range. Additional tools -are required for the enforcement of such criteria. -

- -

The following elements are used in feature system declarations: - - - - - - -

-

The logic for validating feature values and for matching the -conditions for supplying default values is based on the operation of -subsumption. Subsumption is a standard operation in -feature-structure-based formalisms. Informally, a feature structure -FS subsumes all feature structures that are at least as -informative as itself; that is, all feature structures that -specify all of the feature values that FS does with values that are -subsumed by the values that FS has, and that have all of the -re-entrancies (see ) that FS does. (; -see also and ) -A more formal definition is provided in ISO 24610-1:2006 .

- - -

Following the spirit of the informal definition above, we can extend -subsumption in a straightforward way to cover alternation, negation, -special primitive values, and the use of attributes in the markup. -For instance, a vAlt containing the value v subsumes v. The negation -of a value v (represented by means of the -vNot element discussed in section ) -subsumes any value that is not v; for -example <vNot><numeric value='0'/></vNot> subsumes any -numeric value other than zero. - The value fs -type="X"/ subsumes any feature structure of type X, -even if it is not valid. -

- -

As an example of feature declarations, consider the following extract -from Gazdar et al.'s Generalized Phrase Structure - Grammar. In the appendix to their book, they -propose a feature system for English of which this is just a sampling: -feature value range -INV {+, -} -CONJ {and, both, but, either, neither, nor, or, NIL} -COMP {for, that, whether, if, NIL} -AGR CAT -PFORM {to, by, for, ...} -Feature specification defaults -FSD 1: [-INV] -FSD 2: ~[CONJ] -FSD 9: [INF, +SUBJ] --> [COMP for]

-

The INV feature, which encodes whether or not a sentence is inverted, -allows only the values plus (+) and minus (-). If the feature is not -specified, then the default rule (FSD 1 above) says that a value of -minus is always assumed. The feature declaration for this feature would -be encoded as follows: - - inverted sentence - - - - - -

-

The value range is specified as an alternation (more precisely, an -exclusive disjunction), which can be represented by the -binary feature value. That is, -the value must be either true or false, but cannot be both or neither.

-

The CONJ feature indicates the surface form of the conjunction used -in a construction. The ~ in the default rule (see FSD 2 above) -represents negation. This means that by default the feature is not -applicable, in other words, no conjunction is taking place. Note that -CONJ not being present is distinct from CONJ being present but having the NIL value allowed in -the value range. In their analysis, NIL means that the phenomenon of -conjunction is taking place but there is no explicit conjunction in the -surface form of the sentence. The feature declaration for this feature -would be encoded as follows: - - surface form of the conjunction - - - - - - - - - - - - - - - -Note that the vDefault is not strictly necessary in this case, -since the binary value of false only serves to convey the -information that the feature has no other legitimate value. -

- -

The COMP feature indicates the surface form of the complementizer -used in a construction. In value range, it is analogous to CONJ. -However, its default rule (see FSD 9 above) is conditional. It says -that if the verb form is infinitival (the VFORM feature is not -mentioned in the rule since it is the only feature that can take INF -as a value), and the construction has a subject, then a -for complement must be used. For instance, to -make John the subject of the infinitive in It is necessary -to go, a for complement must be -used; that is, It is necessary for John to go. -The feature declaration for this feature would be encoded as follows: - - - surface form of the complementizer - - - - - - - - - - - - - -

-

The AGR feature stores the features relevant to subject-verb -agreement. Gazdar et al. specify the range of this feature as CAT. -This means that the value is a category, which -is their term for a feature structure. This is actually too weak a -statement. Not just any feature structure is allowable here; it must be -a feature structure for agreement (which is defined in the complete -example at the end of the chapter to contain the features of person and -number). The following feature declaration encodes this constraint on -the value range: - - agreement for person and number - - -That is, the value must be a feature structure of type Agreement. The complete example at the end of this -chapter includes the fsDecl type="Agreement" which includes -fDecl name="PERS" and fDecl name="NUM".

-

The PFORM feature indicates the surface form of the preposition used -in a construction. Since PFORM is specified above as an open set, -string is used in the range specification below rather than -symbol. - - word form of a preposition - - -This example makes use of a negated value: <vNot><string/></vNot> -subsumes any string that is not the empty -string.

-

For the reduced feature structure that concludes section above and -identifies the value of some part of speech to be a common noun, it is possible to align -the concept of part of speech with its definition and persistent -identifier using the targetDatcat attribute, which connects the modeled XML object -with the appropriate locus in a reference taxonomy, as shown below: - - -part of speech (morphosyntactic category) - - - - - - - - - -The above example declares the feature POS as instantiating the corresponding concept defined in a reference -taxonomy or ontology, and defines the range of values of the feature at hand by listing the appropriate -alternatives, together with their external persistent identifiers.

-

Note that -the class model.featureVal includes all possible -single feature values, including feature structures, alternations -(vAlt) and complex collections (vColl).

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-
Feature Structure Constraints -

Ensuring the validity of feature structures may require much more -than simply specifying the range of allowed values for each feature. -There may be constraints on the co-occurrence of one feature value with -the value of another feature in the same feature structure or in an -embedded feature structure.

-

Such constraints on valid feature structures are expressed as a -series of conditional and biconditional tests in the -fsConstraints part of an fsDecl. A particular feature -structure is valid only if it meets all the constraints. The -cond element encodes the conventional if-then conditional of -boolean logic which succeeds when both the antecedent and consequent are -true, or whenever the antecedent is false. The bicond element -encodes the biconditional (if and only if) operation of boolean logic. -It succeeds only when the corresponding -if-then conditionals in both directions are true. In feature structure constraints the antecedent and -consequent are expressed as feature structures; they are considered true -if they subsume -(see section ) the feature structure in question, but in the -case of consequents, this truth is asserted rather than simply -tested. That is to say, a conditional is enforced by determining that -the antecedent does not (and will never) subsume the given feature -structure, or by determining that the antecedent does subsume the -given feature structure, and then unifying the consequent with it (the -result of which, if successful, will be subsumed by the consequent). -In practice, the enforcement of such constraints can result in -periods in which the truth of a constraint with respect to a given -feature structure is simply not known; in this case, the constraint -must be persistently monitored as the feature structure becomes more -informative until either its truth value is determined or computation -fails for some other reason.

-

The -following elements make up the fsConstraints part of an FSD: -

-

For an example of feature structure constraints, consider the -following feature co-occurrence restrictions -extracted from the feature system for English proposed by Gazdar, et al. (1985:246–247): -[FCR 1: [+INV] → [+AUX, FIN] -FCR 7: [BAR 0] ≡ [N] & [V] & [SUBCAT] -FCR 8: [BAR 1] → ~[SUBCAT]]

-

The first constraint says that if a construction is inverted, it must -also have an auxiliary and a finite verb form. That is, - - - - - - -

-

The second constraint says that if a construction has a BAR value of -zero (i.e., it is a sentence), then it must have a value for the -features N, V, and SUBCAT. By the same token, because it is a -biconditional, if it has values for N, V, and SUBCAT, it must have -BAR='0'. That is, - - - - - - - - -

- -

The final constraint says that if a construction has a BAR value of 1 -(i.e., it is a phrase), then the SUBCAT feature should be absent (~). -This is not biconditional, since there are other instances under which -the SUBCAT feature is inappropriate. That is, - - - - -

- -

-Note that cond and bicond use the empty tags -then and iff, respectively, to separate the antecedent -and consequent. These are primarily for the sake of enhancing human -readability.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-
A Complete Example -

To summarize this chapter, the complete FSD for the example that has -run through the chapter is reproduced below: - - - - - A sample FSD based on an extract from Gazdar - et al.'s GPSG feature system for English - - encoded by - Gary F. Simons - - - -

This sample was first encoded by Gary F. Simons (Summer -Institute of Linguistics, Dallas, TX) on January 28, 1991. -Revised April 8, 1993 to match the specification of FSDs -in version P2 of the TEI Guidelines. Revised again December 2004 to -be consistent with the feature structure representation standard -jointly developed with ISO TC37/SC4. -

- -

This sample FSD does not describe a complete feature -system. It is based on extracts from the feature system -for English presented in the appendix (pages 245–247) of -Generalized Phrase Structure Grammar, by Gazdar, Klein, -Pullum, and Sag (Harvard University Press, 1985).

- - - - - - Encodes a feature structure for the GPSG analysis - of English (after Gazdar, Klein, Pullum, and Sag) - - inverted sentence - - - - - - - - - - surface form of the conjunction - - - - - - - - - surface form of the complementizer - - - - - - - - - - - - agreement for person and number - - - - word form of a preposition - - - - - - - - - - - - - - - - - - - - - - - This type of feature structure encodes the features - for subject-verb agreement in English - - person (first, second, or third) - - - - - - number (singular or plural) - - - - -

- -
- - - -
- Formal Definition and Implementation -

This elements discussed in this chapter constitute a module of the - TEI scheme which is formally defined as follows: - - Feature Structures - Feature structures - Structures de traits - 功能結構 (Feature Structures) - Strutture di configurazione (feature structures) - Estrutura das características - 素性構造モジュール - - - - The selection and combination of modules to form a TEI schema is - described in . - - - - - - - - - - - - - - - - - -

-
-
diff --git a/P5/Source/Guidelines/fr/FS-FeatureStructures.xml b/P5/Source/Guidelines/fr/FS-FeatureStructures.xml new file mode 120000 index 0000000000..67724271eb --- /dev/null +++ b/P5/Source/Guidelines/fr/FS-FeatureStructures.xml @@ -0,0 +1 @@ +../en/./FS-FeatureStructures.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/FT-TablesFormulaeGraphics.xml b/P5/Source/Guidelines/fr/FT-TablesFormulaeGraphics.xml deleted file mode 100644 index 95d9bffe45..0000000000 --- a/P5/Source/Guidelines/fr/FT-TablesFormulaeGraphics.xml +++ /dev/null @@ -1,1105 +0,0 @@ - - - - -
- Tables, Formulæ, Graphics, and Notated Music -

Many documents, both historical and contemporary, include not only text, - but also graphics, artwork, and other images. Although some types of images - can be represented directly with markup, it is more common practice to - include such information by using a reference to an external entity - (typically a URL) encoded in a suitable graphical notation.

-

In addition to graphic images, documents often contain material presented - in graphical or tabular format. In such materials, details of layout and - presentation may also be of comparatively greater significance or complexity - than they are for running text. Indeed, it may often be difficult to make a - clear distinction between details relating purely to the rendition of - information and those relating to the information itself.

-

Documents may also contain mathematical formulæ or expressions in other - formulaic notations, for which no notation is defined in these - Guidelines.

-

Finally, documents may contain musical notation, embedded in a manner - similar to tables, graphs, and formulæ.

-

These areas (graphics, tabular material, and mathematical or other formulæ, - and music) have in common that they have received considerable attention - from many other standards bodies or similar professional groups. In part - because of this, they may frequently be most conveniently encoded and - processed using some notation not defined by these Guidelines. For these - reasons, and others, we consider tables, formulæ, graphics, and notated music - together in this chapter.

-

As with text markup in general, many incompatible formats have been - proposed for the representation of graphics, formulæ, and tables in - electronic form. Unfortunately, no single format as effective as XML in the - domain of text has yet emerged for their interchange, to some extent because - of the difficulty of representing the information these data formats convey - independently of the way it is rendered.

-

The module defined by this chapter defines special purpose - container elements that can be used to encapsulate - occurrences of such data within a TEI-conformant document in a portable way. - Specific recommendations for the encoding of tables are provided in section - , recommendations for mathematical or other formulæ - in section , and for the encoding of musical notation - in section . Specific recommendations for the encoding - of graphic figures may be found in section . The rest - of the chapter is devoted to general problems of encoding graphic - information.

-

There is at the time of writing no consensus on formats for graphical - images, and such formats vary in many ways. We therefore provide (in section - ) a brief discussion of the ways in which images - may be represented, and (in section ) a list of - formal names for those representations most popular at this time. Each one - includes a very brief description. These Guidelines recommend a few - particular representations as being the most widely supported and - understood.

-
- Tables -

A table is the least graphic of the elements - discussed in this chapter. Almost any text structure can be presented as a - series of rows and columns: one might, for example, choose to show a - glossary or other form of list in tabular form, without necessarily - regarding it as a table. In such cases, the global rend - attribute is an appropriate way of indicating that some element is being - presented in tabular format; similarly, the global style attribute coud be used - to provide an appropriate display property in CSS. When tabular presentation is regarded as of less - intrinsic importance, it is correspondingly simpler to encode descriptive - or functional information about the contents of the table, for example to - identify one cell as containing a name and another as containing a date, - though the two methods may be combined.

-

When, however, particular elements are required to encode the tabular - arrangement itself, then one or other of the various table - schemas now available may be preferable. The schemas in - common use generally view a table as a special text element, made up of - row elements, themselves composed of - cells. - Table cells generally appear in row-major order, with the first row from - left to right, then the second row, and so on. Details of appearance such - as column widths, border lines, and alignment are generally encoded by - numerous attributes. Beyond this, however, such schemas differ greatly. - This section begins by describing a table schema of this kind; a brief - summary of some other widely available table schemas is also provided in - section .

-
- TEI Tables -

For encoding tables of low to moderate complexity, these Guidelines - provide the following special purpose elements: - - - - -

-

The table element is defined as a member of the class model.inter; it may therefore appear both within - other components (such as paragraphs), or between them, provided that - the module defined in this chapter has been enabled, as described at the - beginning of this chapter.

-

It is to a large extent arbitrary whether a table should be regarded as - a series of rows or as a series of columns. For compatibility with - currently available systems, however, these Guidelines require a - row-by-row description of a table. It is also possible to describe a - table simply as a series of cells; this may be useful for tabular - material which is not presented as a simple matrix.

-

The attributes rows and cols may be used to - indicate the size of a table, or to indicate that a particular cell or - row of a table spans more than one row or column. For both tables and - cells, rows and columns are always given in top-to-bottom, left-to-right - order, although formatting properties such as those provided by CSS may - be used to specify that they should be displayed differently. These - Guidelines do not require that the size of a table be specified; for - most formatting and many other applications, it will be necessary to - process the whole table in two passes in any case.

-

Where cells span more than one column or row, the encoder must - determine whether this is a purely presentational effect (in which case - the rend attribute may be more appropriate), whether the part - of the table affected would be better treated as a nested table, or - whether to use the spanning attributes listed above.

-

The role attribute may be used to categorize a single cell, - or set a default for all the cells in a given row. The present - Guidelines distinguish the roles of label and - data only, but the encoder may define other roles, such - as derived, numeric, etc., as appropriate.

-

These three attributes are provided by the attribute class - att.tableDecoration of which both - cell and row are members; see further .

-

The following simple example demonstrates how the data presented as a - labelled list in section might be represented by - an encoder wishing to preserve its original appearance as a table: - - Report of the conduct and progress of Ernest - Pontifex. Upper Vth form — half term ending Midsummer 1851 - - Classics - Idle listless and unimproving - - - Mathematics - ditto - - - Divinity - ditto - - - Conduct in house - Orderly - - - General conduct - Not satisfactory, on account of his great unpunctuality and - inattention to duties - -
- -

-

Note that this encoding makes no attempt to represent the full - significance of the ditto cells above; these might be regarded as - simple links between the cells containing them and that to which they - refer, or as virtual copies of it. For ways of representing either - interpretation, see chapter .

-

The following example demonstrates how a simple statistical table may - be represented using this scheme: - - Poor Man's Lodgings in Norfolk (Mayhew, 1843) - - - Dossing Cribs or Lodging Houses - Beds - Needys or Nightly Lodgers - - - Bury St Edmund's - 5 - 8 - 128 - - - Thetford - 3 - 6 - 36 - - - Attleboro' - 3 - 5 - 20 - - - Wymondham - 1 - 11 - 22 - -
-

-

Note the use of a blank cell in the first row to ensure that the column - labels are correctly aligned with the data. Again, this encoding does - not explicitly represent the alignment between column and row labels and - the data to which they apply. Where the primary emphasis of an encoding - is on the semantic content of a table, a more explicit mechanism for the - representation of structured information such as that provided by the - feature structure mechanism described in chapter may - be preferred. Alternatively, the general purpose linkage and alignment - mechanisms described in chapter may also be applied - to individual cells of a table.

-

The content of a table cell need not be simply character data. It may - also contain any sequence of the phrase-level elements described in - chapter , thus allowing for the encoding of - potentially more useful semantic information, as in the following - example, where the fact that one cell contains a number and the other - contains a place name has been explicitly recorded: - - US State populations, 1990 - - Wyoming - - - 453,588 - - - Alaska - - - 550,043 - - - Montana - - - 799,065 - - - Rhode Island - - - 1,003,464 - -
-

-

The use of semantically marked elements within a cell enables - the encoder to convey something about the nature and significance of the - information, rather than merely suggesting how to display it in rows and - columns.

-

Alternatively, the role attribute might be used to convey - such information: - - US State populations, 1990 - Wyoming - 453,588 - Alaska - 550,043 - Montana - 799,065 - Rhode Island - 1,003,464 -
-

-

The content of table elements is not limited to head and - row. Milestone elements such as cb and lb - allow breaks to be signalled inside tables; figure provides an - option for including data which is not amenable to normal row and cell - analysis; and other elements such as epigraph and - trailer provide options for including text which is clearly - part of the table, but outside the actual tabular layout. This example - shows the use of trailer: - - The Table of Battallions, reduced out of the grand square of - men. - - 1 - 2 - 3 - 4 - - - - 841 - 3 - 289 289 256 - 7 - - The end of the Table of Battallions reduced out of the - battels of g. and squares of men: vpon the right side of euery - leafe. -
-

- - - - - -
-
- Other Table Schemas -

Many authoring systems include built-in support for their own or for - public table schemas. These provide an enhanced user interface and good - formatting capabilities, but are often product-specific, despite their - use of a XML markup language.

-

The DTD developed by the Association of American Publishers (AAP) and - standardized in ANSI Z39.59 provided a very simple encoding for - correspondingly simple tables. This has been further developed, together - with the table DTD documented in ISO Technical Report 9537, and now - forms part of ISO 12083. The TEI table model described above has - functionality very similar to that defined by ISO 12083.

-

For more complex tables, the most effective publicly-available DTD is - probably that developed by the US Department of Defense CALS project. - This supports vertical and horizontal spanning and various kinds of text - rotation and justification within cells and is also directly supported - by a number of existing XML software systems.

-

The CALS table model is much too complex to describe fully here; for - historical background see ; for - more recent simplifications of it and current implementations see . As with - any other XML vocabulary, the XML version of the CALS model may readily - be included in a TEI schema, using the techniques described in .

- - -

The XHTML table model () is based on the HTML - table model (). Both models support arrangement of - arbitrary data into rows and columns of cells. Table rows and columns - may be grouped to convey additional structural information and may be - rendered by user agents in ways that emphasize this structure. Support - for incremental rendering of tables and for rendering on - non-visual user agents - - is also available. Special elements and attributes are provided to - associate metadata with tables. They indicate the table's purpose, or - are for the benefit of people using speech or Braille-based user agents. - Tables are not recommended for use purely as a means to lay out document - content, as this leads to many accessibility problems (see further ). - Stylesheets provide a far more effective means of controlling layout and - other visual characteristics in both HTML and XML documents.

-
-
-
- Formulæ and Mathematical Expressions -

Mathematical and chemical formulæ pose problems similar to those posed by - tables in that rendition may be of great significance and hard to - disentangle from content. They also require access to a wide range of - special characters, for most of which standard entity names already exist - in the documented ISO entity sets (see further chapters and ).

-

Formulæ and tables are also similar in that well-researched and detailed - DTD fragments have already been developed for them independently of the - TEI. They differ in that (for mathematics at least) there also exists a - richly detailed text-based but non-XML notation which is very widely used: - this is the TeX system, and the sets of descriptive macros developed for - it such as LaTeX, AMS-TeX, and AMS-LaTeX.

-

The AAP and ISO standards mentioned in section - above both provide DTDs for equations as well as for tables, which now - form part of ISO 12083. The European Mathematical Trust, an organization - set up specifically to enhance research support for European - mathematicians, has also defined a general purpose mathematical DTD known - as EuroMath (), for which it provides both software and services.

-

Most if not all of the functionality provided by these DTDs can now be - found in the OpenMath and MathML XML-based systems briefly described - below.

-

As with tables, in all the XML solutions a tension exists between the - need to encode the way a formula is written (its appearance) and the need - to represent its semantics. If the object of the encoding is purely to act - as an interchange format among different formatting programs, then there - is no need to represent the mathematical meaning of an expression. If - however the object is to use the encoding as input to an algebraic - manipulation system (such as Mathematica or Maple) or a database system, - clearly simply representing superscripts and subscripts will be - inadequate.

-

The formula element provided by these Guidelines makes no - attempt to represent the internal structure of formulæ. - - -

-

By default, a formula is assumed to contain character data which - is not validated in any way. The notation used may however be named, using - the notation attribute provided by the - att.notated class. - $e=mc^2$ - The character data must still be well-formed, of course, which means that - < and & must be - escaped with entity references or numeric character references, e.g. - $\matrix{0 &amp; - 1\cr&lt;0&amp;>1}$ -

-

Alternatively, if more detailed markup is desired, the content of the formula element may be redefined - to include elements defined by some other XML vocabulary, such as that of ISO - 12083, or to use elements from the OpenMath or - MathML - schemas. -

-

When the content of a formula element is not expressed in XML - the notation used should always be specified using the notation - attribute as above, and in the following longer example: -

Achilles runs ten times faster than the tortoise and gives the - animal a headstart of ten meters. Achilles runs those ten meters, the - tortoise one; Achilles runs that meter, the tortoise runs a decimeter; - Achilles runs that decimeter, the tortoise runs a centimeter; Achilles - runs that centimeter, the tortoise, a millimeter; Fleet-footed - Achilles, the millimeter, the tortoise, a tenth of a millimeter, and - so on to infinity, without the tortoise ever being overtaken. . . Such - is the customary version. The problem does not change, as - you can see; but I would like to know the name of the poet who - provided it with a hero and a tortoise. To those magical competitors - and to the series $$ {1 \over 10} + {1 \over - 100} + {1 \over 1000} + {1 \over 10,\!000} + \dots $$ the - argument owes its fame.

- The notation attribute supplies the name of a notation - (TeX), which is expected to be identified somewhere in document - metadata.

-

Mathematical Markup Language (MathML) () is a - vocabulary for describing mathematical notation, capturing both its - structure and content. - - It provides two types of markup: Presentation Markup, which captures the - notational structure of an expression and could be seen as the - TeX for the Web and Content Markup, which captures - the mathematical structure of an expression. Most of its content - elements correspond with the range of operators, relations, and named - functions typically found at the high-school level of mathematics. The - tortoise example given above in TeX can be re-expressed in MathML as - - - - 1 - - - 10 - - - + - - - 1 - - - 100 - - - + - - - 1 - - - 1000 - - - + - - - 1 - - - 10000 - - - + - … - -

-

MathML 2.0 provides support for a Semantic Math-Web, - XML namespaces, and other current XML standards, such as XML DOM, OMG IDL, - ECMAScript, and Java. It also provides a modularized version of the MathML - DTD so that MathML fragments embedded in XHTML 1.1 - documents can be correctly validated.

-

The OpenMath () project is coordinated by the OpenMath Society () and funded by the European - Commission under the Esprit Multimedia Standards Initiative that commenced - in September 1997. It is likely to become a key standard for communicating - semantically rich representations of mathematical objects both on and off - the Web in a platform-independent manner.

-

The OpenMath Standard () consists - of specifications for - OpenMath objects, representing the structure of formulæ (); - Content Dictionaries, providing semantic context (); - Encodings, both binary () and XML (). -

-

OpenMath and MathML have certain common aspects. They both use prefix - operators, both are XML-based and they both construct their objects by - applying certain rules recursively. Such similarities facilitate mapping - between the two standards. There are also some key differences between - MathML and OpenMath. OpenMath does not provide support for presentation of - mathematical objects and its scope of semantically-oriented elements is - much broader that of MathML, with the expressive power to cover virtually - all areas of computational mathematics. In fact, a particular set of - Content Dictionaries, the MathML CD Group, covers the - same areas of mathematics as the Content Markup elements of MathML - 2.0.

-

Finally, OMDoc () is an extension of the - OpenMath standard that supplies markup for structures such as axioms, - theorems, proofs, definitions, texts (mixing formal content with - mathematical text).

-

In-line versus block placement for an equation can be distinguished if - desired, via the global rend attribute. The global n - and xml:id attributes may also be used to label or identify the - formula, as in the following example: -

The volume of a sphere - is given by the formula: - - V - = - - - 4 - - - 3 - - - π - - - r - - - 3 - - - - which is readily calculated.

-

As we have seen in equation , ...

-

- - - -
-
- Notated Music in Written Text -

Music, like many other art forms, is often mentioned, discussed and - described in writings of various kinds. This applies to both historical - and contemporary documents, even though methods of notating music have - changed considerably in western history. In most cases, music notation - enters the text flow in a way similar to figures, images, or graphs. On - other occasions, elements of music notation are treated as inline - characters in running text.

-

notatedMusic provides a way to signal the presence of music - notation in text, but defer to other representations, which are not - covered by the TEI guidelines, to describe the music notation itself. In - fact several commercial, academic, and standard bodies have developed - digital representations of music notation. Given the topic's - complexity, these representations often focus on different aspects and - adopt different methodologies. Therefore, notatedMusic only - defines a container element to encode the occurrence of music notation and - allows linking to the data format preferred by the encoder. (Note: - notatedMusic is not the same as musicNotation, a - metadata element, which is used to describe musical notation that appears - in a manuscript. See .)

-

The following elements can be used for encoding music notation in text: - - - - - - -

- - - groups elements representing or - containing music notation. - - can be used to indicate the location of a - representation of the music notation. - mimeType supplies the MIME type of the data format, - when available. - - - - can be used to give a prose description of - the notated music. - - can be used to indicate the location of - a graphical representation of the music notation. - - provides encoded binary data which - constitutes another representation of the music notation (e.g. - audio). - -

The notatedMusic element may contain a textual description and - pointers to various representations of the music notation in different - media. An external representation of the notated music is specified using - the ptr element, whose target attribute provides its - electronically-accessible location. The attribute mimeType - supplies the MIME type of the data format when available. For example:

- - - -

A textual description of the notation can be provided within the - desc element; alternatively, a label may be supplied. - For example:

- - - First bar of Chopin's Scherzo No.3 Op.39 - -

It is possible to link to any kind of music notation data format. - However, when a MIME type is not available, it is recommended that the - format be specified in the description. See the following examples.

-

MIME type available:

- - - First bar of Chopin's Scherzo No.3 Op.39. Encoded in - MusicXML. - -

MIME type not available:

- - - First bar of Chopin's Scherzo No.3 Op.39. Encoded in - Lilypond. - -

Application format:

- - - First bar of Chopin's Scherzo No.3 Op.39. MuseScore Notation - Software format. - -

It is possible to specify the location of digital objects representing - the notated music in other media such as images or audio-visual files. The - interpretation of the correspondence between the notated music and these - digital objects is not encoded explicitly. We recommend the use of - graphic and binaryObject mainly as a fallback - mechanism when the notated music format is not displayable by the - application using the encoding. The alignment of encoded notated music, - images carrying the notation, and audio files is a complex matter for - which we refer the reader to other formats and specifications such as MPEG-SMR.

- - - - First bar of Chopin's Scherzo No.3 Op.39 - - -

It is also recommended, when useful, to embed XML-based music notation - formats, such as the Music Encoding Initiative - format as content of notatedMusic. This must be done by means of customization.

- -

In modern printing, music notation positioned between blocks of text for - illustrative purposes is usually referred to as a figure or - example. In this cases, we recommend the inclusion of - notatedMusic in figure in order to encode possible - captions and headers. For example:

-
- Example from: - Prout, E. (1899). The - orchestra. - - -
-
-

We now give some examples, from the works of the great masters, of - some of the most frequently used bowings.

-
- SCHUBERT: Symphony in B minor. - - - -
-
- - - - -
-
- Specific Elements for Graphic Images -

The following special purpose elements are used to indicate the presence - of graphic images within a document: - - - - - -

-

The graphic and binaryObject elements form part of the - common core module, and are discussed in section .

-

The figure element is used to contain images, captions, and - textual descriptions of the pictures. The images themselves are specified - using the graphic element, whose url attribute - provides the location of an image. For example: -

- -
-

-

Three kinds of content may be supplied inside a figure element: - the element head may be used to transcribe (or supply) a - descriptive heading or title for the graphic itself as in this example: -

- - The View from the Bridge -
-

-

Figures are often accompanied not only by a title or heading (a caption), - but by a paragraph or so of commentary (a legend) following the caption. - One or more p or ab elements - may be used to transcribe any - commentary on the figure in the source: -

- - Above: -

The drawing room of the Pullman house, the white and gold saloon - where the magnate delighted in giving receptions for several hundred - people.

- The figure shows an elaborately decorated room, at least - twenty-five feet side to side and fifty feet long, with ornate - mouldings and Corinthian columns on the walls, overstuffed armchairs - and loveseats arranged in several conversational groupings, and two - large chandeliers. -
- - Here, - the figure contains a heading Above which is complemented by a - paragraph of description The drawing room ... several hundred - people. Both of these are transcribed from the source, while the - description is provided by the encoder, for use by applications which - cannot display the graphic directly. In documents created in electronic - form with the needs of print-handicapped readers in mind, the - figDesc element may be provided by the author rather than a - subsequent encoder. -
- - Figure One: The View from the Bridge - A Whistleresque view showing four or five sailing boats in - the foreground, and a series of buoys strung out between - them. -
-

-

Where the graphic itself contains large amounts of text, perhaps with a - complex structure, and perhaps difficult to distinguish from the graphic, - the encoder should choose whether to regard the graphic as containing the - text (in which case, a nested floatingText element may be - included within the figure element) or to regard the enclosed - text as being a separate division of the text element in which - the graphic appears. In this latter case, an appropriate div or - div1 (etc.) element may be used for the text represented within - the graphic, and the figure element embedded within it. The - choice will depend to a large degree on the encoder's understanding of the - relationship between the graphic and the surrounding text.

-

A figure which is internally divided, or contains sub-figures, may be - encoded with nested figure elements, as in the following example. - -

-
- - Parallel -
-
- - Perspective -
- The two canonical view volumes, for the (a) - parallel and (b) perspective projections. Note that -z is to the - right. -
- - -

-

Like any other element in the TEI scheme, figures may be given - identifiers so that they can be aligned with other elements, and linked to - or from them, as described in chapter . Some common - examples are discussed briefly here; full information is provided in that - chapter.

-

It is often desirable to maintain two versions of an image in an - electronic file: one a low resolution or thumbnail - version which, when selected by the user, causes the other, high - resolution, version to be accessed. In TEI terms, the thumbnail image acts - as a reference to the other. Supposing that a thumbnail - version of the figure discussed above is available as fig1th.png, we might embed a reference to the image using the - simple ref element discussed in section : - Click - here for enlightenment -

- -
- -

-

Another common requirement is to associate part or the whole of an image - with a textual element not necessarily contiguous to it in the text; this - is sometimes known as a callout. When the module for - transcription is included in a schema, specific attributes for parts of a - text and parts (or all) of a digital image are available; these are - discussed in . In addition, chapter may be consulted for other mechanisms available for this - purpose.

-

The following example assumes that we wish to associate one portion of - the image held as fig1 with chapter two of some text, and another - portion of it with chapter three. The application may be thought of as a - hypertext browser in which the user selects from a graphic image which - part of a text to read next, but the mechanism is independent of this - particular application.

-

The first requirement is some way of identifying and hence pointing to - sub-parts of a graphic image. This may be done by pointing into an XML - graphic representation, for example an SVG file. Thus - - -

-

These ptr elements identify two areas within the image - Fig1 by pointing at elements inside the XML file Fig1.svg, which contains the following. - - - - - - - - - - -

-

The next requirement is some way of identifying the parts of the document - to which a link is to be made. The most obvious way of doing this is to - use the global xml:id attribute: - - - - - - -

-

Now, all that is needed to linking these areas to the relevant chapters - is a linkGrp element, as described in section : - - - - -

-

In this example, the SVG representation of the graphic is stored - externally to the TEI document and linked by means of a pointer. It is - also possible to embed the SVG representation directly within the TEI by - extending the content model of the figure element to permit an - element svg from the SVG namespace. Like other - customizations of the TEI scheme, this is carried out using the techniques - documented in section ; further examples are provided - in chapter .

- - - - - -
-
- Overview of Basic Graphics Concepts -

The first major distinction in graphic representation is that between - raster graphics and vector graphics. A raster image is a list - of points, or dots. Scanners, fax machines, and other simple devices easily - produce digital raster images, and such images are therefore quite common. - A vector image, in contrast, is a list of geometrical - objects, such as lines, circles, arcs, or even cubes. These are much more - difficult to produce, and so are mainly encountered as the output of - sophisticated systems such as architectural and engineering CAD - programs.

-

Raster images are difficult to modify because by definition they only - encode single points: a line, for example, cannot grow or shrink as such, - since it is not identified as such. Only its component parts are - identified, and only they can be manipulated. Therefore the resolution or - dot-size of a raster image is important, which is not the case with vector - images. It is also far more difficult to convert raster images to vector - images than to perform the opposite conversion. Raster images generally - require more storage space than vector images, and a wide variety of - methods exists for compressing them; the variation in these methods leads - to corresponding variations in representations for storage and - transmission of raster images.

-

Motion video usually consists of a long series of raster images. Data - compression is even more effective on video than on single raster images - (mainly owing to redundancy which arises from the usual similarity of - adjacent frames). Notations for representing full-motion video are hotly - debated at this time, and any user of these Guidelines would do well to - obtain up-to-date expert advice before undertaking a project using - them.

-

The compression methods used with any of these image types may be - lossy or lossless. Methods for - lossy compression save space by discarding a small portion - of the image's detail, such as fine distinctions of shading. When - decompressed, therefore, such an image will be only a close approximation - of the original. In contrast, lossless compression guarantees - that the exact uncompressed image will be reproducible from the compressed - form: only truly redundant information is removed. In general, therefore, - lossless compression does not save quite so much space as lossy - compression, though it does guarantee fidelity to the original - uncompressed image.

-

Raster images may be characterized by their resolution, - which is the number of dots per inch used to represent the image. Doubling - the resolution will give a more precise image, but also quadruple the - storage requirement (before compression), and affect processing time for - any operations to be performed, such as displaying an image for a reader. - Motion video also has resolution in time: the number of frames to be shown - per second. Encoders should consider carefully what resolution(s) and - frame rate(s) to use for particular applications; these Guidelines express - no recommendation in this matter, save the universal ones of consistency - and documentation.

-

Within any image, it is typical to refer to locations via Cartesian - coordinate axes: values for x, y, and sometimes z and/or time. However, - graphic notations vary in whether coordinates count from left-to-right and - top-to-bottom, or another way. They also vary in whether coordinates are - considered real (inches, millimeters, and so on), or virtual (dots). These - Guidelines do not recommend any of these methods over another, but all - decisions made should be applied consistently, and documented in the - encodingDesc section of the TEI header.Since no special purpose element is provided for this purpose by the - current version of these Guidelines, such information should be provided - as one or more distinct paragraphs at the end of the - encodingDesc element described in section .

-

Methods of aligning images and text are discussed in .

-

The chromatic values of an image may be rendered in many different ways. - In monochrome images every displayed point is either black or white. In - grayscale images, each point is rendered in some shade of - gray, the number of shades varying from system to system. In true - polychrome images, points are rendered in different hues, again with - varying limitations affecting the number of distinct shades and the means - by which they are displayed.

-
-
- Graphic Image Formats -

As noted above, there exists a wide variety of different graphics - formats, and the following list is in no way exhaustive. Moreover, - inclusion of any format in this list should not be taken as indicating - endorsement by the TEI of this format or any products associated with it. - Some of the formats listed here are proprietary to a greater or lesser - extent and cannot therefore be regarded as standards in any meaningful - sense. They are however widely used by many different vendors.

-

The following formats are widely used at the present time, and likely to - remain supported by more than one vendor's software: - BMP: Microsoft bitmap format - CGM: Computer Graphics Metafile - GIF: Graphics Interchange Format - JPEG: Joint Photographic Expert Group - PBM: Portable Bit Map - PCX: IBM PC raster format - PICT: Macintosh drawing format - PNG: Portable Network Graphics format - Photo-CD: Kodak Photo Compact Disk format - QuickTime: Apple real-time image system - SMIL: Synchronized Multimedia Integration Language format - SVG: Scalable Vector Graphics format - TIFF: Tagged Image File Format -

-

Brief descriptions of all the above are given below. Where possible, - current addresses or other contact information are shown for the - originator of each format. Many formal standards, especially those - promulgated by ISO and many related national organizations (ANSI, DIN, - BSI, and many more), are available from those national organizations. - Addresses may be found in any standard organizational directory for the - country in question.

-
- Vector Graphic Formats - - - This vector graphics format is specified by an ISO standard, ISO - 8632:1987, amended in 1990. It defines binary, character, and - plain-text encodings; the non-binary forms are safer for blind - interchange, especially over networks. Documentation on CGM is - available from ISO and from its member national bodies such as AFNOR, - ANSI, BSI, DIN, JIS, etc. - - SVG is a language for describing two-dimensional vector and mixed - vector or raster graphics in XML. It is defined by the Scalable Vector - Graphics (SVG) 1.0 Specification, W3C Recommendation, 04 September - 2001, and is available at . - - This format is universally supported on Macintosh™ systems, - and readable by a limited range of software for other systems. - Documentation is available from Apple Computer Company, Cupertino, - California USA. - -
-
- Raster Graphic Formats - - - PNG is a non-proprietary raster format currently widely available. - It provides an extensible file format for the lossless, portable, - well-compressed storage of raster images. Indexed-color, grayscale, - and truecolor images are supported, plus an optional alpha channel. - Sample depths range from 1 to 16 bits. It is defined by IETF RFC 2083, - March 1997. - - Currently the most widely supported raster image format, - especially for black and white images, TIFF is also one of the few - formats commonly supported on more than one operating system. The - drawback to TIFF is that it actually is a wrapper for several formats, - and some TIFF-supporting software does not support all variants. TIFF - files may use LZW, CCITT Group 4, or PackBits compression methods, or - may use no compression at all. Also, TIFF files may be monochrome, - grayscale, or polychromatic. All such options should be specified in - prose at the end of the encodingDesc section of the TEI - header for any document including TIFF images. TIFF is owned by Aldus - Corporation. Documentation on TIFF is available from them at Craigcook - Castle, Craigcook Road, Edinburgh EH4 3UH, Scotland, or 411 First - Avenue South, Seattle, Washington 98104 USA. - - Raster images are widely available in this form, which was created - by CompuServe Information Services, but has by now been implemented - for many other systems as well. Documentation on GIF is copyright by, - and is available from, CompuServe Incorporated, Graphics Technology - Department, 5000 Arlington Center Boulevard, Columbus, Ohio 43220 USA. - - PBM files are easy to process, eschewing all compression in favor - of transparency of file format. PBM files can, of course, be - compressed by generic file-compression tools for storage and transfer. - Public domain software exists which will convert many other formats to - and from PBM. Documentation on PBM is copyright by Jeff Poskanzer, and - is available widely on the Internet. - - This format is used by most IBM PC paint programs, and supports - both monochrome and polychromatic images. Documentation is available - from ZSoft Corporation, Technical Support Department, ATTN: Technical - Reference Manual, 450 Franklin Rd. Suite 100, Marietta, GA 30067 USA. - - This format is the standard raster format for computer using - Microsoft Windows™ or Presentation Manager™. Documentation is - available from Microsoft Corporation. - -
-
- Photographic and Motion Video Formats - - - This standard is sponsored by CCITT and by ISO. It is ISO/IEC - Draft International Standard 10918-1, and CCITT T.81. It handles - monochrome and polychromatic images with a variety of compression - techniques. JPEG per se, like CCITT Group IV, must be encapsulated - before transmission; this can be done via TIFF, or via the JPEG File - Interchange Format (JFIF), as commonly done for Internet delivery. - - QuickTime is a proprietary method introduced by Apple Computer - Company to synchronize the display of various data. The data can - include frames of video, sound, lighting control mechanisms, and other - things. Viewers for QuickTime productions are available for Apple and - other computers. Further information is available from Apple Computer - Incorporated, 10201 North de Anza Boulevard MS 23AQ, Cupertino, - California 95014 USA. - - This format was introduced by Kodak for rasterizing photographs - and storing them on CD-ROMs (about one hundred 35mm file images fit on - one disk), for display on televisions or CD-I systems. Information on - Photo-CD is available from Kodak Limited, Research and Development, - Headstone Drive, Harrow, Middlesex HA1 4TY, UK. - - SMIL is a W3C Recommendation which supports the integration of - independent multimedia objects into a synchronized multimedia - presentation. It provides multimedia authors with easily-defined basic - timing relationships, fine-tuned synchronization, spatial layout, - direct inclusion of non-text and non-image media objects, hyperlink - support for time-based media, and adaptiveness to varying user and - system characteristics. SMIL 1.0 () became a W3C - Recommendation on June 15, 1998, and was further developed in SMIL - 2.0. SMIL 2.0 adds native support for transitions, animation, - event-based interaction, extended layout facilities, and more - sophisticated timing and synchronization primitives to the SMIL 1.0 - language. It also allows reuse of SMIL syntax and semantics in other - XML-based languages, in particular those who need to represent timing - and synchronization. For example, SMIL 2.0 components are used for - integrating timing into XHTML Document Types and into SVG. SMIL 2.0 - also provides recommendations for Document Types based on SMIL 2.0 - Modules (). One such Document Type is the SMIL 2.0 Language Profile (). It contains support for all of the major SMIL 2.0 features - including animation, content control, layout, linking, media object, - meta-information, structure, timing, and transition effects and is - designed for Web clients that support direct playback from SMIL 2.0 - markup. SMIL 2.0 () became a - W3C Recommendation on August 7, 2001, becoming the first vocabulary to - provide XML Schema support and to have reached such status. - -

As noted above, the reader will encounter many, many other graphics - formats.

-
-
-
- Module for Tables, Formulæ, Notated Music, and Graphics -

The module described in this chapter provides the following features: - - Tables, Formulæ, Notated Music, Figures - Tables, formulæ, notated music, and figures - Tableaux, formules et graphiques - 表格、方程式與圖表 - Tabelle, formule e figure - Tabelas, fórmulas, e figuras - 図表式モジュール - - The selection and combination of modules to form a TEI - schema is described in . - - - - -

-
-
\ No newline at end of file diff --git a/P5/Source/Guidelines/fr/FT-TablesFormulaeGraphics.xml b/P5/Source/Guidelines/fr/FT-TablesFormulaeGraphics.xml new file mode 120000 index 0000000000..190989855a --- /dev/null +++ b/P5/Source/Guidelines/fr/FT-TablesFormulaeGraphics.xml @@ -0,0 +1 @@ +../en/./FT-TablesFormulaeGraphics.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/GD-GraphsNetworksTrees.xml b/P5/Source/Guidelines/fr/GD-GraphsNetworksTrees.xml deleted file mode 100644 index b7d952b394..0000000000 --- a/P5/Source/Guidelines/fr/GD-GraphsNetworksTrees.xml +++ /dev/null @@ -1,1499 +0,0 @@ - - - - -
Graphs, Networks, and Trees -

Graphical representations are widely used for displaying relations -among informational units because they help readers to visualize those -relations and hence to understand them better. Two general types of -graphical representations may be distinguished. - - Graphs, in the strictly mathematical sense, consist -of points, often called nodes or -vertices, and connections among them, called -arcs, or under certain conditions, -edges. Among the various types of graphs are -networks and trees. Graphs -generally and networks in particular are dealt with -directly below. Trees are dealt with separately in -sections and -.The treatment here is largely based on the -characterizations of graph types in -Charts, which typically plot data in two or more -dimensions, including plots with orthogonal or radial axes, bar charts, -pie charts, and the like. These can be described using the elements -defined in the module for figures and graphics; see -chapter . -

- -

Among the types of qualitative relations often represented by graphs -are organizational hierarchies, flow charts, genealogies, semantic -networks, transition networks, grammatical relations, tournament -schedules, seating plans, and directions to people's houses. In -developing recommendations for the encoding of graphs of various types, -we have relied on their formal mathematical definitions and on the most -common conventions for representing them visually. However, it must be -emphasized that these recommendations do not provide for the full range -of possible graphical representations, and deal only partially with -questions of design, layout, and placement.

-
Graphs and Digraphs -

Broadly speaking, graphs can be divided into two types: -undirected and directed. An undirected graph -is a set of nodes (or vertices) together with -a set of pairs of those vertices, called arcs or -edges. Each node in an arc of an undirected graph is said -to be incident with that arc, and the two vertices (nodes) which -make up an arc are said to be adjacent. An directed graph -is like an undirected graph except that the arcs are ordered -pairs of nodes. In the case of directed graphs, the term -edge is not used; moreover, each arc in a directed graph -is said to be adjacent from the node from which the arc -emanates, and adjacent to the node to which the arc is -directed. We use the element graph to encode graphs as a -whole, node to encode nodes or vertices, and arc to -encode arcs or edges; arcs can also be encoded by attributes on the -node element. These elements have the following descriptions -and attributes: - - - -

-

Before proceeding, some additional terminology may be helpful. We -define a path in a graph as a sequence of nodes n1, ..., nk -such that there is an arc from each ni to ni+1 in the sequence. A -cyclic path, or cycle is a path leading from a -particular node back to itself. A graph that contains at least one -cycle is said to be cyclic; otherwise it is -acyclic. We say, finally, that a graph is -connected if there is a path from some node to every other -node in the graph; any graph that is not connected is said to be -disconnected.

-

Here is an example of an undirected, cyclic disconnected graph, in -which the nodes are annotated with three-letter codes for airports, and -the arcs connecting the nodes are represented by horizontal and vertical -lines, with 90 degree bends used simply to avoid having to draw diagonal -lines.

- - - - - -

- -

Next is a markup of the graph, using arc elements to encode -the arcs. - - - - - - - - - - - - - - - - - - - - - -

-

-The first child element of graph may be a label to record a -label for the graph; similarly, the label child of each -node element records the labels of that node. The -order and size attributes on the graph -element record the number of nodes and number of arcs in the graph -respectively; these values are optional (since they can be computed -from the rest of the graph), but if they are supplied, they must be -consistent with the rest of the encoding. They can thus be used to -help check that the graph has been encoded and transmitted correctly. -The degree attribute on the node elements record -the number of arcs that are incident with that node. It is optional -(because redundant), but can be used to help in validity checking: if -a value is given, it must be consistent with the rest of the -information in the graph. Finally, the from and -to attributes on the arc elements provide pointers -to the nodes connected by those arcs. Since the graph is undirected, -no directionality is implied by the use of the from and -to attributes; the values of these attributes could be -interchanged in each arc without changing the graph.

-

The adj, adjFrom, and adjTo -attributes of the node element provide an alternative method of -representing unlabeled arcs, their values being pointers to the nodes -which are adjacent to or from that node. The adj attribute -is to be used for undirected graphs, and the adjFrom and -adjTo attributes for directed graphs. It is a semantic error -for the directed adjacency attributes to be used in an undirected graph, -and vice versa. Here is a markup of the preceding graph, using the -adj attribute to represent the arcs. - - - - - - - - - - - - - - - - - -

-

Note that each arc is represented twice in this encoding of the -graph. For example, the existence of the arc from LAX to LVG can be -inferred from each of the first two node elements in the graph. -This redundancy, however, is not required: it suffices to describe an -arc in any one of the three places it can be described (either adjacent -node, or in a separate arc element). Here is a less redundant -representation of the same graph. - - - - - - - - - - - - - - - - - -

-

Although in many cases the arc element is redundant (since -arcs can be described using the adjacency attributes of their adjacent -nodes), it has nevertheless been included in this module, in order to -allow the convenient specification of identifiers, display or -rendition information, and labels for each arc (using the attributes -xml:id, rend, and a child label element).

-

Next, let us modify the preceding graph by adding directionality to -the arcs. Specifically, we now think of the arcs as specifying selected -routes from one airport to another, as indicated by the direction of the -arrowheads in the following diagram.

-

-

Here is an encoding of this graph, using the arc element to -designate the arcs. - - - - - - - - - - - - - - - - - - - - - - - -The attributes inDegree and outDegree indicate -the number of nodes which are adjacent to and from the node concerned -respectively.

- -

Here is another encoding of the graph, using the adjTo and -adjFrom attributes on nodes to designate the arcs. - - - - - - - - - - - - - - - - - -

-

If we wish to label the arcs, say with flight numbers, then -arc elements must be used to hold the label -elements, as in the following example. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Transition Networks -

For encoding transition networks and other kinds of directed graphs -in which distinctions among types of nodes must be made, the -type attribute is provided for node elements. In -the following example, the initial and final -nodes (or states) of the network are distinguished. It can -be understood as accepting the set of strings obtained by traversing it -from its initial node to its final node, and concatenating the labels. -

-

- - - - - - - - - - - - - - - - - - - - - - - - - - -

-

A finite state transducer has two labels on each arc, and can be -thought of as representing a mapping from one sequence of labels to -the other. The following example represents a transducer for -translating the English strings accepted by the network in the -preceding example into French. The nodes have been annotated with -numbers, for convenience.

-

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

-
Family Trees -

The next example provides an encoding a portion of a -family treeThe family tree is that of the -mathematician and philosopher Bertrand Russell, whose third wife was -commonly known as Peter. The information presented here is taken from -Pereira and Shieber (1987). in which nodes are used to represent -individuals and parents of individuals, and arcs are used to -represent common parentage and descent links. Let us suppose, -further, that information about individuals is contained in feature -structures, which are contained in feature-structure libraries -elsewhere (see ). We can use the -value attribute on node elements to point to those -feature structures. In this particular representation of -the graph, nodes representing females are framed by ovals, nodes -representing males are framed by boxes, and nodes representing parents -are framed by diamonds. -

-

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

-
Historical Interpretation -

For our final example, we represent graphically the relationships -among various geographic areas mentioned in a -seventeenth-century Scottish document. The document itself is -a sasine, which records a grant of land -from the earl of Argyll to one Donald McNeill, and reads in part -as follows (abbreviations have been expanded silently, -and [...] marks illegible passages): - -

Item instrument of Sasine given the said Hector -Mcneil confirmed and dated 28 May 1632 -[...] at Edinburgh upon the 15 June 1632

-

Item ane charter granted by Archibald late earl -of Argyle and Donald McNeill of Gallachalzie wh -makes mention that ... -the said late Earl yields and grants -to the said Donald MacNeill ...

-

All and hail the two merk land of old extent -of Gallachalzie with the pertinents by and in -the lordship of Knapdale within the sherrifdome -of Argyll

-

[description of other lands granted follows ...]

-

This Charter is dated at Inverary the 15th May 1669

-

In this example, we are concerned with the land and pertinents (i.e. -accompanying sources of revenue) described as the two merk land of -old extent of Gallachalzie with the pertinents by and in the lordship of -Knapdale within the sherrifdom of Argyll.

-

The passage concerns the following pieces of land: - -the Earl of Argyll's land (i.e. the lands granted by this clause -of the sasine) -two mark of land in Gallachalzie -the pertinents for this land -the Lordship of Knapdale -the sherrifdom of Argyll -We will represent these geographic entities as nodes in a graph. -Arcs in the graph will represent the following relationships among -them: - -containment (INCLUDE) -location within (IN) -contiguity (BY) -constituency (PART OF) -Note that these relationships are logically related: include -and in, for example, are inverses of each other: the Earl of -Argyll's land includes the parcel in Gallachalzie, and the parcel is -therefore in the Earl of Argyll's land. Given an explicit set of -inference rules, an appropriate application could use the graph we are -constructing to infer the logical consequences of the relationships we -identify.

-

Let us assume that feature-structure analyses are available which -describe Gallachalzie, Knapdale, and Argyll. We will link to those -feature structures using the value attribute on the nodes -representing those places. However, there may be some uncertainty as to -which noun phrase is modified by the phrase within the sheriffdome of -Argyll: perhaps the entire lands (land and pertinents) are in -Argyll, perhaps just the pertinents are, or perhaps only Knapdale is -(together with the portion of the pertinents which is in Knapdale). We -will represent all three of these interpretations in the graph; they -are, however, mutually exclusive, which we represent using the -exclude attribute defined in -chapter .That is, the three syntactic -interpretations of the clause are mutually exclusive. The notion that -the pertinents are in Argyll is clearly not inconsistent with the notion -that both the land in Gallachalzie and the pertinents are in Argyll. -The graph given here describes the possible interpretations of the -clause itself, not the sets of inferences derivable from each syntactic -interpretation, for which it would be convenient to use the facilities -described in chapter .

-

We represent the graph and its encoding as follows, where -the dotted lines in the graph indicate the mutually exclusive arcs; in -the encoding, we use the exclude attribute to indicate those -arcs. -

-

-

The graph formalizes the following relationships: - -the Earl of Argyll's land includes (the parcel of -land in) Gallachalzie -the Earl of Argyll's land includes the pertinents of that parcel -the pertinents are (in part) by the Lordship of Knapdale -the pertinents are (in part) part of the Lordship of Knapdale -the Earl of Argyll's land, or the pertinents, or -the Lordship of Knapdale, is in the Sherrifdom of Argyll -We encode the graph thus: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

-
Trees -

A tree is a connected acyclic graph. That is, it is -possible in a tree graph to follow a path from any vertex to any other -vertex, but there are no paths that lead from any vertex to itself. A -rooted tree is a directed graph based on a tree; that is, the arcs in -the graph correspond to the arcs of a tree such that there is exactly -one node, called the root, for which there is a path from -that node to all other nodes in the graph. For our purposes, we may -ignore all trees except for rooted trees, and hence we shall use the -tree element for rooted trees, and the root element -for its root. The nodes adjacent to a given node are called its -children, and the node adjacent from a given node is called -its parent. Nodes with both a parent and children are -called internal nodes, for which we use the iNode -element. A node with no children is tagged as a leaf. If the -children of a node are ordered from left to right, then we say that that -node is ordered. If all the nodes of a tree are ordered, -then we say that the tree is an ordered tree. If some of -the nodes of a tree are ordered and others are not, then the tree is a -partially ordered tree. The ordering of nodes and trees -may be specified by an attribute; we take the default ordering for trees -to be ordered, that roots inherit their ordering from the trees in which -they occur, and internal nodes inherit their ordering from their -parents. Finally, we permit a node to be specified as following other -nodes, which (when its parent is ordered) it would be assumed to -precede, giving rise to crossing arcs. -The elements used for the -encoding of trees have the following descriptions and attributes. - - - - -

-

Here is an example of a tree. It represents the order in which the -operators of addition (symbolized by +), exponentiation -(symbolized by **) and division (symbolized by /) are -applied in evaluating the arithmetic formula -((a**2)+(b**2))/((a+b)**2). -In drawing the graph, the root is placed on the far right, and -directionality is presumed to be to the left. -

-

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

-

In this encoding, the arity attribute represents the -arity of the tree, which is the greatest value of the -outDegree attribute for any of the nodes in the tree. If, as -in this case, arity is 2, we say that the tree is a -binary tree.

-

Since the left-to-right (or top-to-bottom!) order of the children of -the two + nodes does not affect the arithmetic result in this -case, we could represent in this tree all of the arithmetically -equivalent formulas involving its leaves, by specifying the attribute -ord as false on those two iNode elements, the attribute -ord as true on the root and other iNode -elements, and the attribute ord as partial on the tree -element, as follows. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

-

This encoding represents all of the following: - - ((a**2)+(b**2))/((a+b)**2) - ((b**2)+(a**2))/((a+b)**2) - ((a**2)+(b**2))/((b+a)**2) - ((b**2)+(a**2))/((a+b)**2) - -

-

Linguistic phrase structure is very commonly represented by trees. -Here is an example of phrase structure represented by an ordered tree -with its root at the top, and a possible encoding. -

-

- - - - - - - - - - - - - - - - - - - - - - - - - - -

-

Finally, here is an example of an ordered tree, in which a particular -node which ordinarily would precede another is specified as following -it. In the drawing, the xxx symbol indicates that the arc from -VB to PT crosses the arc from VP to PN. -

-

- - - - - - - - - - - - - - - - - - - - - - - - - -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-
Another Tree Notation -

In this section, we present an alternative to the method of -representing the structure of ordered rooted trees given in -section , which is based on the observation -that any node of such a tree can be thought of as the root of the -subtree that it dominates. Thus subtrees can be thought of as the same -type as the trees they are embedded in, hence the designation -eTree, for embedding tree. Whereas in a -tree the relationship among the parts is indicated by the -children attribute, and by the names of the elements -root, iNode, and leaf, the relationship among -the parts of an eTree is indicated simply by the arrangement of -their content. However, we have chosen to enable encoders to -distinguish the terminal elements of an eTree by means of the -empty eLeaf element, though its use is not required; the -eTree element can also be used to identify the terminal nodes -of eTree elements. We also provide a triangle -element, which can be thought of as an underspecified -eTree, i.e. an eTree in which certain information -has been left out. In addition, we provide a forest element, -which consists of one or more tree, eTree, or -triangle elements, and a listForest element, which -consists of one or more forest elements. The elements used for -the encoding of embedding trees and the units containing them have the -following descriptions and attributes. - - - - - - -

-

Like the root, iNode, and leaf of a -tree, the eTree, triangle and -eLeaf elements may also have -value attributes and label children.

-

To illustrate the use of the eTree and eLeaf -elements, here is an encoding of the second example in section , repeated here for convenience. -

-

- - - - - - - - - - - - - - - - - - - - - - - -

-

Next, we provide an encoding, using the triangle element, in -which the internal structure of the eTree labeled NP is -omitted. -

-

- - - - - - - - - - - - - - - -

-

Ambiguity involving alternative tree structures associated with the -same terminal sequence can be encoded relatively conveniently using a -combination of the exclude and copyOf attributes -described in sections and . In -the simplest case, an eTree may be part of the content of -exactly one of two different eTree elements. To mark it up, -the embedded eTree may be fully specified within one of the -embedding eTree elements to which it may belong, and a -virtual copy, specified by the copyOf attribute, may appear -on the other. In addition, each of the embedded elements in question -is specified as excluding the other, using the exclude -attribute. To illustrate, consider the English phrase see the -vessel with the periscope, which may be considered to be -structurally ambiguous, depending on whether the phrase with -the periscope is a modifier of the phrase the -vessel or a modifier of the phrase see the -vessel. This ambiguity is indicated in the sketch of the -ambiguous tree by means of the dotted-line arcs. The markup using the -copyOf and exclude attributes follows the -sketch. -

-

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

-

To indicate that one of the alternatives is selected, one may specify -the select attribute on the highest eTree as -either #GD-PPA or #GD-PPB; see section -.

-

Depending on the grammar one uses to associate structures with -examples like see the man with the periscope, the -representations may be more complicated than this. For example, -adopting a version of the X-bar theory of phrase structure -originated by Jackendoff, the -attachment of a modifier may require the creation of an intermediate -node which is not required when the attachment is not made, as shown in -the following diagram. A possible encoding of this ambiguous structure -immediately follows the diagram. -

-

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

- -

A derivation in a generative grammar is often thought -of as a set of trees. To encode such a derivation, one may use the -forest element, in which the trees may be marked up using the -tree, the eTree, or the triangle element. -The type attribute may be used to specify what kind of -derivation it is. Here is an example of a two-tree forest, involving -application of the wh-movement transformation in -the derivation of what you do (as in this is -what you do) from the underlying you do -what.The symbols -e and t denote -special theoretical constructs (empty category and -trace respectively), which need not concern us here. -

-

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

-

In this markup, we have used copyOf attributes to provide -virtual copies of elements in the tree representing the second stage of -the derivation that also occur in the first stage, and the -corresp attribute (see section ) to link -those elements in the second stage with corresponding elements in the -first stage that are not copies of them.

-

If a group of forests (e.g. a full grammatical derivation including -syntactic, semantic, and phonological subderivations) is to be -articulated, the grouping element listForest may be used.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
Representing Textual Transmission - -

A stemma codicum (sometimes called just -stemma) is a tree-like graphic structure that has become -traditional in manuscript studies for representing textual -transmission. Consider the following hypothetical stemma: -

Example stemma -
-

- -

The nodes in this stemma represent manuscripts; each has a label (a -letter) which identifies it and also distinguishes whether the -manuscript is extant, lost, or hypothetical. Extant manuscripts are -identified by uppercase Latin letters or words beginning with -uppercase Latin letters, e.g., L, shown as aqua in this example; -manuscripts no longer existing, but providing readings which are -attested e.g. by note or copy made before their disappearance, are -identified by lowercase Latin letters, e.g., t, shown as magenta in -this example; hypothetical stages in the textual transmission, which -do not necessarily correspond to real manuscripts, are given -lowercase Greek letters, e.g., α and shown as gold in this example. -The stemma shown above thus suggests that (on the basis of -similarities in the readings of the extant and lost manuscripts) L -and t share textual material that is not shared with other -manuscripts (represented in this case by δ) even though no physical -manuscript attesting this stage in the textual transmission has ever -been identified.

- -

Manuscripts are copied from other manuscripts. The preceding -stemma represents the hypothesis that all manuscripts go back to a common -ancestor (α), that the tradition split after that stage into two -(β and γ), etc. Descent by copying is indicated with a solid line. -According to this model, α is the earliest common hypothetical stage -that can be reconstructed, and all nodes below α have a single -parent, that is, were copied from a single other stage in the -tradition.

- -

This familiar tree model is complicated because manuscripts -sometimes show the influence of more than one ancestor. They may have -been produced by a scribe who checked the text in one -manuscript of the same work whilst copying from another, or perhaps -made changes from his memory of a slightly different version of the -text that he had read elsewhere. Alternatively, perhaps scribe A -copied a manuscript from one source, scribe B made changes in it in -the margins or between the lines (either by consulting another source -directly or from memory), and another scribe then copied that -manuscript, incorporating the changes into the body. Whatever the -specific scenario, it is not uncommon for a -manuscript to be based primarily on one source, but to incorporate -features of another branch of the tradition. This mixed result is -called contamination, and it is reflected in a stemma by a -dotted line. Thus, the example above asserts that A is copied within -the ε tradition, but is also contaminated from the γ -tradition.

- -

The utility of a stemma as a visualization tool is inversely -proportional to the degree of contamination in the manuscript -tradition. A tradition completely without contamination (called a -closed tradition) yields a classic tree, easily -represented graphically by a stemma. An open tradition, with -substantial contamination, yields a spaghetti-like stemma -characterized by crossing dotted lines, which is both difficult to -read and not very informative.

- -

The eTree element introduced in this chapter can be used -to represent a closed tradition in a straightforward manner. Each -non-terminal node is represented by a typed eTree element and -each terminal node by an eLeaf. A label element -provides a way of identifying each node, complementary to the global -attributes n and xml:id attributes. For example, -the closed part of the tradition headed by the label δ may be encoded -as follows: - - - - - - - - - - - -To complete this representation, we need to show that the node -labelled A is not derived solely from its parent node (labelled ε) -but also demonstrates contamination from the node labelled γ. The -easiest way to accomplish this is to include an appropriately-typed -ptr element within the node in question, the -target of which points to the node labelled γ. This -requires that this latter node be supplied with a value for its -xml:id attribute. The complete representation is thus: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

-

In any substantial codicological project, it is likely that -significantly more data will be required about the individual -witnesses than indicated in the simple structures above. These -Guidelines provide a rich variety of additional elements for -representing such information: see in particular chapters , , and .

- -
- -
- Module for Graphs, Networks, and Trees -

The module described in this chapter makes available the - following components: - - Graphs, networks, and trees - Graphs, networks, and trees - Graphes, réseaux et arbres - 圖形、網絡與樹狀結構 - Grafici, reti e alberi - Grafos, redes, e árvores - グラフモジュール - - - The selection and combination of modules to form a TEI schema is - described in . - - - -

-
-
\ No newline at end of file diff --git a/P5/Source/Guidelines/fr/GD-GraphsNetworksTrees.xml b/P5/Source/Guidelines/fr/GD-GraphsNetworksTrees.xml new file mode 120000 index 0000000000..e57b3b09fc --- /dev/null +++ b/P5/Source/Guidelines/fr/GD-GraphsNetworksTrees.xml @@ -0,0 +1 @@ +../en/./GD-GraphsNetworksTrees.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/HD-Header.xml b/P5/Source/Guidelines/fr/HD-Header.xml index 1b41c58497..a260362732 100644 --- a/P5/Source/Guidelines/fr/HD-Header.xml +++ b/P5/Source/Guidelines/fr/HD-Header.xml @@ -1,4 +1,3 @@ -
diff --git a/P5/Source/Guidelines/fr/MS-ManuscriptDescription.xml b/P5/Source/Guidelines/fr/MS-ManuscriptDescription.xml deleted file mode 100644 index cbe3f34f5f..0000000000 --- a/P5/Source/Guidelines/fr/MS-ManuscriptDescription.xml +++ /dev/null @@ -1,2571 +0,0 @@ - - - - -
-Manuscript Description -
-Overview -

The msdescription module - This chapter is based on the work of the European MASTER (Manuscript Access -through Standards for Electronic Records) project, funded by the European Union -from January 1999 to June 2001, and led by Peter Robinson, then at the Centre -for Technology and the Arts at De Montfort University, Leicester (UK). -Significant input also came from a TEI Workgroup headed by Consuelo W. Dutschke -of the Rare Book and Manuscript Library, Columbia University (USA) and Ambrogio -Piazzoni of the Biblioteca Apostolica Vaticana (IT) during 1998-2000. -defines a special purpose element which can be used to provide detailed -descriptive information about handwritten primary sources and other text-bearing objects. -Although originally developed to meet the needs of cataloguers and scholars working with medieval -manuscripts in the European tradition, the scheme presented here is general -enough that it can also be extended to other traditions and materials, and is -potentially useful for any kind of text-bearing artefact. Where the textuality of -an object is not the primary concern, encoders may wish to use the object -element which provides a very similar system of description (see .

-

The scheme described here is also intended to accommodate the needs of many -different classes of encoders. On the one hand, encoders may be engaged in -retrospective conversion of existing detailed descriptions and -catalogues into machine tractable form; on the other, they may be engaged in -cataloguing ex nihilo, that is, creating new detailed -descriptions for materials never before catalogued. Some may be primarily -concerned to represent accurately the description itself, as opposed to the -ideas and interpretations the description represents; others may have entirely -opposite priorities. At one extreme, a project may simply wish to capture an -existing catalogue in a form that can be displayed on the Web, and which can be -searched for literal strings, or for such features such as titles, authors and -dates; at the other, a project may wish to create, in highly structured and -encoded form, a detailed database of information about the physical -characteristics, history, interpretation, etc. of the material, able to support -practitioners of quantitative codicology as well as librarians.

-

To cater for this diversity, here as elsewhere, these Guidelines propose a -flexible strategy, in which encoders must choose for themselves the approach -appropriate to their needs, and are provided with a choice of encoding -mechanisms to support those differing degrees.

-
-
-The Manuscript Description Element -

The msDesc element will normally appear within the -sourceDesc element of the header of a TEI-conformant document, where -the document being encoded is a digital representation of some manuscript -original, whether as an encoded transcription, as a collection of digital images -(as described in ), or as some combination of the two. -However, in cases where the document being encoded is essentially a collection -of manuscript descriptions, the msDesc element may be used in the same -way as the bibliographic elements (bibl, biblFull, and -biblStruct) making up the TEI element class model.biblLike. -These typically appear within the listBibl -element. - -

-

The msDesc element has the following components, which provide more -detailed information under a number of headings. Each of these component -elements is further described in the remainder of this chapter. - - - - - - - - -

-

The first of these components, msIdentifier, is the only one which -is mandatory; it is described in more detail in below. It -is followed optionally by one or more head elements, each holding a -brief heading (see ), and then either one or more -paragraphs, marked up as a series of p elements, or at most -one of each of the specialized elements msContents (), -physDesc (), history (), -and additional (). These elements are all -optional, and if used they may appear at most once in a given -msDesc, in any order. Finally, -in the case of a composite manuscript (a manuscript composed of several -codicological units) or a fragmented manuscript (a manuscript whose parts are now -dispersed and kept at different places), a full description may also contain one or more -msPart () elements and msFrag () -elements, respectively.

-

To demonstrate the use of this module, consider the following sample -manuscript description, chosen more or less at random from the Bodleian -Library's Summary catalogue ()

- -Entry for Bodleian MS. Add. A. 61 in Madan et al. 1895-1953 -
-

-

The simplest way of digitizing this catalogue entry would simply be to key in -the text, tagging the relevant parts of it which make up the mandatory -msIdentifier element, as follows: - - - -Oxford -Bodleian Library -MS. Add. A. 61 -28843 - -

In Latin, on parchment: written in more than one hand of the 13th cent. in -England: 7¼ x 5⅜ in., i + 55 leaves, in double columns: with a few coloured -capitals.

-

'Hic incipit Bruitus Anglie,' the De origine et gestis Regum Angliae of -Geoffrey of Monmouth (Galfridus Monumetensis: beg. 'Cum mecum multa & de -multis.'

-

On fol. 54v very faint is 'Iste liber est fratris guillelmi de buria de ... -Roberti ordinis fratrum Pred[icatorum],' 14th cent. (?): 'hanauilla' is written -at the foot of the page (15th cent.). Bought from the rev. W. D. Macray on March -17, 1863, for £1 10s.

- - With a suitable stylesheet, this encoding would be as readable as the original; -it would not, however, be very useful for search purposes since only shelfmarks -and other identifiers are distinguished. To improve on this, one might wrap the -paragraphs in the appropriate special-purpose first-child-level elements of -msDesc and add some of the additional phrase-level elements available -when this module is in use: - - - -Oxford -Bodleian Library -MS. Add. A. 61 - -28843 - - - -

Hic incipit Bruitus Anglie, the De origine et gestis -Regum Angliae of Geoffrey of Monmouth (Galfridus Monumetensis): beg. -Cum mecum multa & de multis. In Latin.

- - -

Parchment: written in -more than one hand: 7¼ x 5⅜ in., i + 55 leaves, in double columns: -with a few coloured capitals.

- - -

Written in England in the 13th -cent. On fol. 54v very faint is Iste liber est fratris -guillelmi de buria de ... Roberti ordinis fratrum Pred[icatorum], 14th -cent. (?): hanauilla is written at the foot of the page (15th -cent.). Bought from the rev. W. D. Macray on March 17, 1863, for £1 10s.

- - - - Note that in this version the text has been slightly reorganized, but no actual -rewriting has been necessary. The encoding now allows the user to search for -such features as title, material, and date and place of origin; it is also -possible to distinguish quoted material from descriptive passages and to search -within descriptions relating to a particular topic (for example, history as -distinct from material).

-

This process could be continued further, restructuring the whole entry so as -to take full advantage of many more of the encoding possibilities provided by -the module described in this chapter: - - - -Oxford -Bodleian Library -MS. Add. A. 61 - -28843 - - - - -Geoffrey of Monmouth -Galfridus Monumetensis -De origine et gestis Regum Angliae -Hic incipit Bruitus Anglie -Cum mecum multa & de multis -Latin - - - - - - -

Parchment.

- -i + 55 leaves -7¼ -5⅜ - - - - - -

In double columns.

- - - - -

Written in more than one hand.

- - -

With a few coloured capitals.

- - - - -

Written in England in the 13th cent.

- - -

On fol. 54v very faint is Iste liber est fratris -guillelmi de buria de Roberti ordinis fratrum -Predicatorum, 14th cent. (?): hanauilla is -written at the foot of the page (15th cent.).

- - -

Bought from the rev. W. D. Macray on March 17, 1863, for £1 10s.

- - - - - In the remainder of this chapter we discuss all of the encoding features -demonstrated above, together with many other related matters.

- - - -
-
-Phrase-level Elements -

When the msdescription module is in use, several -extra elements are added to the phrase level class, and thus become available -within paragraphs and elsewhere in the document. These elements are listed below -in alphabetical order: - - - - - - - - - - - - -

-

Within a manuscript description, many other standard TEI phrase level -elements are available, notably those described in the Core module (). Additional elements of particular relevance to manuscript -description, such as those for names and dates, may also be made available by -including the relevant module in one's schema.

-
-Origination -

The following elements may be used to provide information about the origins -of any aspect of a manuscript: - - -

-

The origDate and origPlace elements are specialized forms -of the existing date and name elements respectively, used to -indicate specifically the date and place of origin of a manuscript or manuscript -part. Such information would normally be encoded within the history -element, discussed in section . origDate and -origPlace can also be used to identify the place or date of origin of -any aspect of the manuscript, such as its decoration or binding, when these are -not of the same date or from the same location as rest of the manuscript. Both -these elements are members of the att.editLike -class, from which they inherit many attributes. -

-

The origDate element is a member of the att.datable class, and may thus also carry additional attributes giving -normalized values for the associated dating. -

-
-
-Material and Object Type -

The material element can be used to tag any specific term used for -the physical material of which a manuscript (or binding, seal, etc.) is -composed. The objectType element may be used to tag any term specifying -the type of object or manuscript upon with the text is written. - - -

-

These elements may appear wherever a term regarded as significant by the -encoder occurs, as in the following examples: - - -

Brown calfskin, previously with two clasps.

- - - - -

Parchment -codex with half goat-leather -binding.

- - -

-
-
-Watermarks and Stamps -

Two further elements are provided to mark up other decorative features -characteristic of manuscript leaves and bindings: - - -

-

These elements may appear wherever a term regarded as significant by the -encoder occurs. The watermark element is most likely to be of use -within the support element discussed in -below. We give a simple example here: -Rag -paper with anchor watermark -

-

The stamp element will typically appear when text from the source is -being transcribed, for example within a rubric in the following case: - -Apologyticu TTVLLIANI AC IGNORATIA IN XPO IHV -SI NON LICET -NOBIS RO -manii imperii Bodleian stamp - -

-

It may also appear as part of the detailed description of a binding: - -

Modern calf recasing with original armorial stamp with legend -Ex Bibliotheca J. Richard -D.M.

- -

-

If, as here, any text contained by a stamp is included in its description it -should be clearly distinguished from that description. The element -mentioned may be used for this purpose, as shown above.

-
-
-Dimensions -

The dimensions element can be used to specify the size of some -aspect of the manuscript, and thus may be thought of as a specialized form of -the existing TEI measure element. - -

-

The dimensions element will normally occur within the element -describing the particular feature or aspect of a manuscript whose dimensions are -being given; thus the size of the leaves would be specified within the -support or extent element (part of the physDesc -element discussed in ), while the dimensions of other -specific parts of a manuscript, such as accompanying materials, binding, etc., -would be given in other parts of the description, as appropriate.

-

The following elements are available within the dimensions element: - - - - - -

-

These elements, as well as dimensions itself, are all members of the -att.dimensions class, which also inherits attributes -from the att.ranging class. They all thus carry the -following attributes: - - -

-

Attributes scope, min, and max are used only -when the measurement applies to several items, for example the size of all -leaves in a manuscript; attributes atLeast and atMost are -used when the measurement applies to a single item, for example the size of a -specific codex, but has had to be estimated. Attribute quantity is -used when the measurement can be given exactly, and applies to a single item; -this is the usual situation. In this case, the units in which dimensions are -measured may be specified using the unit attribute, the value of -which will normally be taken from a closed set of values appropriate to the -project, using standard units of measurement wherever possible, such as -cm, mm, in, line, char. -If however the only data available for the measurement uses some other unit, or -it is preferred to normalize it in some other way, then it may be supplied as a -string value by means of the extent attribute.

-

In the simplest case, only the extent attribute may be supplied: -six -cubits - More usually, the measurement will be normalized into a value and an -appropriate SI unit: -six cubits - Where the exact value is uncertain, the attributes atLeast and -atMost may be used to indicate the upper and lower bounds of an -estimated value: -six cubits -

-

It is often convenient to supply a measurement which applies to a number of -discrete observations: for example, the number of ruled lines on the pages of a -manuscript (which may not all be the same), or the diameter of an object like a -bell, which will differ depending where it is measured. In such cases, the -scope attribute may be used to specify the observations for which -this measurement is applicable: - - - This indicates that most pages have at least 20 lines. The attributes -min and max can also be used to specify the possible range -of values: for example, to show that all pages have between 12 and 30 lines: - - -

-

The dimensions element may be repeated as often as necessary, with -appropriate attribute values to indicate the nature and scope of the measurement -concerned. For example, in the following case the leaf size and ruled space of -the leaves of the manuscript are specified: - - - - - - - - - - - This indicates that for most leaves of the manuscript being described the ruled -space is 90 mm high and 48 mm wide, while the leaves throughout are between 157 -and 160 mm in height and 105 mm in width.

-

The dim element is provided for cases where some measurement other -than height, width, or depth is required. Its type attribute is used -to indicate the type of measurement involved: - - - - - - -

-

The order in which components of the dimensions element may be -supplied is not constrained. -

-
-
-References to Locations within a Manuscript -

The locus and its grouping element locusGrp element are -specialized forms of the ref element, used to indicate a location, or -sequence of locations, within a manuscript. - - -

-

The locus element is used to reference a single location within a -manuscript, typically to specify the location occupied by the element within -which it appears. If, for example, it is used as the first component of an -msItem or msItemStruct element, or of any of the more specific -elements appearing within one (see further section below) -then it is understood to specify the location (or locations) of that item within -the manuscript being described.

-
-Identifying a Location -

A locus element can be used to identify any reference to one or more -folios within a manuscript, wherever such a reference is appropriate. Locations -are conventionally specified as a sequence of folio or page numbers, but may -also be a discontinuous list, or a combination of the two. This specification -should be given as the content of the locus element, using the -conventions appropriate to the individual scholar or holding institution, as in -the following example: - -ff. 1-24r -Apocalypsis beati Ioannis Apostoli - - -

-

A normalized form of the location can also be supplied, using special purpose -attributes on the locus element, as in the following revision of the -above example: - -ff. 1-24r -Apocalypsis beati Ioannis Apostoli - - -

-

When the item concerned occupies a discontinuous sequence of pages, this may -simply be indicated in the body of the locus element: - -ff. 1-12v, 18-24r -Apocalypsis beati Ioannis Apostoli - - - Alternatively, if it is desired to indicate normalized values for each part of -the sequence, a sequence of locus elements can be supplied, grouped -within the locusGrp element: - - -ff. 1-12v -ff. 18-24r - -Apocalypsis beati Ioannis Apostoli - - - -If an existing catalogue is being transcribed and it is desirable to retain formatting of the reference (e.g. superscript or italic text) then the hi element may be used. If encoding multiple semantic divisions in a single location reference then a nested locus may be used to separate or annotate these. -

-

Finally, the content of the locus element may be omitted if a -formatting application can construct it automatically from the values of the -from and to attributes: - - - - - -Apocalypsis beati Ioannis Apostoli - - -

-
-
-Linking a Location to a Transcription or an Image -

The locus attribute can also be used to associate a location within -a manuscript with facsimile images of that location, using the facs -attribute, or with a transcription of the text occurring at that location. The -former association is effected by means of the facs attribute; the -latter by means of the target attribute.

-

The facs is available only when the transcr module described in chapter is included in -a schema. It associates a locus element with one or more digitized -images, as in the following example: - - -fols. 8v-10v -Birds Praise of Love - -IMEV -1506 - - - - Here, the facs attribute uses a URI reference to point directly to -images of the relevant pages. This method may be found cumbersome when many -images are to be associated with a single location. It is of most use when -specific pages are referenced within a description, as in the following example: - - -

Several of the miniatures in this section have been damaged and overpainted -at a later date (e.g. the figure of Christ on fol. 33r; the face of the -Shepherdess on fol. -59v, etc.).

- - - For further discussion of the facs attribute, see section .

-

Where a transcription of the relevant pages is available, this may be -associated with the locus element using its target -attribute, as in the following example: - - -ff. 1r-2r -Ben Jonson -Ode to himself - - An Ode - to him selfe. -Com leaue the loathed stage -And see his chariot triumph ore his wayne. -Beal, Index 1450-1625, JnB 380 - - - - - - - - - -

-

When (as in this example) a sequence of elements is to be supplied as target -value, it may be given explicitly as above, or using the xPointer range() syntax -defined at . Note however that support for this pointer -mechanism is not widespread in current XML processing systems.

-

The target attribute should only be used to point to elements that -contain or indicate a transcription of the locus being described. To associate a -locus element with a page image or other comparable representation, the -global facs attribute should be used instead.

-
-
-Using Multiple Location Schemes -

Where a manuscript contains more than one foliation, the scheme -attribute may be used to distinguish them. For example, MS 65 Corpus Christi -College, Cambridge contains two fly leaves bearing music. These leaves have -modern foliation 135 and 136 respectively, but are also marked with an older -foliation. This may be preserved in an encoding such as the following: - -XCIII -135 - - Here the scheme attribute points to a foliation element -providing more details about the scheme used, as further discussed in below.

-

Where discontinuous sequences are identified within two different foliations, -the scheme attribute should be supplied on the locusGrp -element in preference, as in the following: - - -XCIII -CC-CCII - - -135 -197-204 - - -

-
-
-
-Names of Persons, Places, and Organizations -

The standard TEI element name may be used to identify names of any -kind occurring within a description: - - As further discussed in , this element is a -member of the class att.canonical, from which it -inherits the following attributes: - - -

-

Here are some examples of the use of the name element: - -Thomas Hoccleve -Villingaholt -Vetus Latina Institut -Occleve - -

-

Note that the name element is defined as providing information about -a name, not the person, place, or organization to which that name -refers. In the last example above, the ref attribute is used to -associate the name with a more detailed description of the person named. This is -provided by means of the person element, which becomes available when -the namesdates module described in chapter is included in a schema. An element such as the following might -then be used to provide detailed information about the person indicated by the -name: - - -Hoccleve -Thomas - - -poet - - - Note that an instance of -the person element must be provided for each distinct ref -value specified. For example, in the case above, the value HOC001 -must be found as the xml:id attribute of some person -element; the same value will be used as the ref attribute of every -reference to Hoccleve in the document (however spelled), but there will only be -one person element with this identifier.

-

Alternatively, the key attribute may be used to supply a unique -identifying code for the person referenced by the name independently of both the -existence of a person element and the use of the standard URI reference -mechanism. If, for example, a project maintains as its authority file some -non-digital resource, or uses a database which cannot readily be integrated with -other digital resources for this purpose, the unique codes used by such -offline resources may be used as values for the -key attribute. Although such practices clearly reduce the -interchangeability of the resulting encoded texts, they may be judged more -convenient or practical in certain situations. As explained in , interchange is improved by use of tag URIs in ref -instead of key.

-

All the person elements referenced by a particular -document set should be collected together within a listPerson - element, located in a standOff element. -This functions as a kind of prosopography for all the people -referenced by the set of manuscripts being described, in much the same -way as a listBibl element may be used to hold bibliographic -information for all the works referenced.

-

When the namesdates module described in chapter - is included in a schema, similar mechanisms are used to -maintain and reference canonical lists of places or organizations, as further -discussed in sections and -respectively.

-
-
-Catchwords, Signatures, Secundo Folio -

The catchwords element is used to describe one method by which -correct ordering of the quires of a codex is ensured. Typically, this takes the -form of a word or phrase written in the lower margin of the last leaf verso of a -gathering, which provides a preview of the first recto leaf of the successive -gathering. This may be a simple phrase such as the following: -Quires signed on the -last leaf verso in roman numerals. - - Alternatively, it may contain more details: - -Vertical catchwords in the hand of the scribe placed along the inner -bounding line, reading from top to bottom. - -

-

The Signatures element is used, in a similar way, to -describe a similar system in which quires or leaves are marked progressively in -order to facilitate arrangement during binding. For example: -At the bottom of the -first four leaves of quires 1-14 are the remains of a series of quire signatures -a-o plus roman figures in a cursive hand of the fourteenth century. - -

-

The signatures element can be used for either leaf signatures, or a -combination of quire and leaf signatures, whether the marking is alphabetic, -alphanumeric, or some ad hoc system, as in the following more complex example: -Quire and leaf -signatures in letters, [b]-v, and roman numerals; those in quires 10 (1) and 17 -(s) in red ink and different from others; every third quire also signed with red -crayon in arabic numerals in the centre lower margin of the first leaf recto: -"2" for quire 4 (f. 19), "3" for quire 7 (f. 43); "4", barely visible, for quire -10 (f. 65), "5", in a later hand, for quire 13 (f. 89), "6", in a later hand, -for quire 16 (f. 113). - -

-

The secFol element (for secundo folio) is used -to record an identifying phrase (also called dictio -probatoria) taken from a specific known point in a codex (for example -the first few words on the second leaf). Since these words will differ from one -copy of a text to another, the practice originated in the middle ages of using -them when cataloguing a manuscript in order to distinguish individual copies of -a work in a way which its opening words could not. - -(ando-)ssene in una villa - -

-
-
-Heraldry - -

Descriptions of heraldic arms, supporters, devices, and mottos may appear at -various points in the description of a manuscript, usually in the context of -ownership information, binding descriptions, or detailed accounts of -illustrations. A full description may also contain a detailed account of the -heraldic components of a manuscript independently considered. Frequently, -however, heraldic descriptions will be cited as short phrases within other parts -of the record. The phrase level element heraldry is provided to allow -such phrases to be marked for further analysis, as in the following examples: - -

Ownership stamp (xvii cent.) on i recto with the arms A bull -passant within a bordure bezanty, in chief a crescent for difference -[Cole], crest, and the legend Cole Deum.

- -

A c. 8r fregio su due lati, stemma e imprese medicee -racchiudono l'inizio dell'epistolario di Paolino.

- -

- - - - - - - - - - - - - - - - - - - - -
-
-
-The Manuscript Identifier -

The msIdentifier element is intended to provide an unambiguous means -of uniquely identifying a particular manuscript. This may be done in a -structured way, by providing information about the holding institution and the -call number, shelfmark, or other identifier used to indicate its location within -that institution. Alternatively, or in addition, a manuscript may be identified -simply by a commonly used name. - -

-

A manuscript's actual physical location may occasionally be different from -its place of ownership; at Cambridge University, for example, manuscripts owned -by various colleges are kept in the central University Library. Normally, it is -the ownership of the manuscript which should be specified in the manuscript -identifier, while additional or more precise information on the physical -location of the manuscript can be given within the adminInfo element, -discussed in section below.

-

The following elements are available within msIdentifier to identify -the holding institution: - - - - - -

-

These elements are all structurally equivalent to the standard TEI -name element with an appropriate value for its type -attribute; however the use of this syntactic sugar enables -the model for msIdentifier to be constrained rather more tightly than -would otherwise be possible. Specifically, only one of each of the elements -listed above may appear within the msIdentifier and they must, if -present, appear in the order given.

-

Like name, these elements are all also members of the attribute -class att.canonical, and thus can use the attributes -key or ref to reference a single standardized source of -information about the entity named.

-

The following elements are used within msIdentifier to provide -different ways of identifying the manuscript within its holding institution: - - - - -

-

Major manuscript repositories will usually have a preferred form of citation -for manuscript shelfmarks, including rules about punctuation, spacing, -abbreviation, etc., which should be adhered to. Where such a format also -contains information which might additionally be supplied as a distinct -subcomponent of the msIdentifier, for example a collection name, a -decision must be taken as to whether to use the more specific element, or to -include such information within the idno element. For example, the -manuscript formally identified as El 26 C 9 forms a part of the Ellesmere -(El) collection. Either of the following encodings is therefore feasible: - - -USA -California -San Marino -Huntington Library -El -26 C 9 -The Ellesmere Chaucer - - - - -USA -California -San Marino -Huntington Library -El 26 C 9 -The Ellesmere Chaucer - - -

-

In the former example, the preferred form of the identifier can be retrieved -by prefixing the content of the idno element with that of the -collection element, while in the latter it is given explicitly. The -advantage of the former is that it simplifies accurate retrieval of all -manuscripts from a given collection; the disadvantage is that encoded -abbreviations of this kind may not be as immediately comprehensible. Care should -be taken to avoid redundancy: for example - -El -El 26 C 9 - - would clearly be inappropriate. Equally clearly, - -Ellesmere -El 26 C 9 - - might be considered helpful in some circumstances (if, for example, some of the -items in the Ellesmere collection had shelfmarks which did not begin El).

-

In some cases the shelfmark may contain no information about the collection; -in other cases, the item may be regarded as belonging to more than one -collection. The collection element may be added, and repeated as often -as necessary to cater for such situations: - - -Hungary -Budapest - Bibliothèque de l'Académie des Sciences de Hongrie -Oriental Collection -Sandor Kégl Bequest -MS 1265 - - -

-

- - -USA -New Jersey -Princeton -Princeton University Library -Scheide Library -MS 71 -Blickling Homiliary - - -

-

Note in the latter case the use of the msName element to provide a -common name other than the shelfmark by which a manuscript is known. Where a -manuscript has several such names, more than one of these elements may be used, -as in the following example: - - -Danmark -København -Det Arnamagnæanske Institut -AM 45 fol. -Codex Frisianus -Fríssbók - - - Here the globally available xml:lang attribute has been used to -specify the language of the alternative names. -

-

In very rare cases a repository may have only one manuscript (or only one of -any significance), which will have no shelfmark as such but will be known by a -particular name or names. In such circumstances, the idno element may -be omitted, and the manuscript identified by the name or names used for it, -using one or more msName elements, as in the following example: - - -Rossano -Biblioteca arcivescovile -Codex Rossanensis -Codex purpureus -The Rossano Gospels - - -If a manuscript name contains a name or referencing string that it is useful to -annotate (e.g. by referring to an authority list) then name or rs -may be used for this purpose. -

-

Where manuscripts have moved from one institution to another, or even within -the same institution, they may have identifiers additional to the ones currently -used, such as former shelfmarks, which are sometimes retained even after they -have been officially superseded. In such cases it may be useful to supply an -alternative identifier, with a detailed structure similar to that of the -msIdentifier itself. The following example shows a manuscript which had -shelfmark II-M-5 in the collection of the Duque de Osuna, but which -now has the shelfmark MS 10237 in the National Library in Madrid: - - -Madrid -Biblioteca Nacional -MS 10237 - -Andalucia -Osuna -Duque de Osuna -II-M-5 - - - - Normally, such information would be dealt with under history, except -in cases where a manuscript is likely still to be referred to or known by its -former identifier. For example, an institution may have changed its call number -system but still wish to retain a record of the earlier number, perhaps because -the manuscript concerned is frequently cited in print under its previous number: - - -Berkeley -University of California -Bancroft Library -UCB 16 -2MS BS1145 I8 - - - Where (as in this example) no repository is specified for the -altIdentifier, it is assumed to be the same as that of the parent -msIdentifier. Where the holding institution has only one preferred form -of citation but wishes to retain the other for internal administrative purposes, -the secondary could be given within altIdentifier with an appropriate -value on the type attribute: - - -Oxford -Bodleian Library -MS. Bodley 406 -2297 - - - It might, however, be preferable to include such information within the -adminInfo element discussed in section -below.

-

Cases of such changed or alternative identifiers should be clearly -distinguished from cases of fragmented () manuscripts, that is to say manuscripts which although physically disjoint -are nevertheless generally treated as single units.

-

As mentioned above, the smallest possible description is one that contains -only the element msIdentifier; good practice in all but exceptional -circumstances requires the presence within it of the three sub-elements -settlement, repository, and idno, since they provide -what is, by common consent, the minimum amount of information necessary to -identify a manuscript.

- - - - - - - - -
-
-The Manuscript Heading -

Historically, the briefest possible meaningful description of a manuscript -consists of no more than a title, e.g. Polychronicon. -This will often have been enough to identify a manuscript in a small collection -because the identity of the author is implicit. Where a title does not imply the -author, and is thus insufficient to identify the main text of a manuscript, the -author should be stated explicitly (e.g. Augustinus, -Sermones or Cicero, Letters). Many -inventories of manuscripts consist of no more than an author and title, with -some form of copy-specific identifier, such as a shelfmark or secundo -folio reference (e.g. Arch. B. 3. 2: Evangelium Matthei -cum glossa, 126. Isidori Originum libri octo, -Biblia Hieronimi, 2o fo. opus est); information on date -and place of writing will sometimes also be included. The standard TEI element -head element can be used to provide a brief description of this kind. - - In this way the cataloguer or scholar can supply in one place a -minimum of essential information, such as might be displayed or printed as the -heading of a full description. For example: - -Marsilius de Inghen, Abbreviata phisicorum Aristotelis; Italy, -1463. - - Any phrase-level elements, such as title, name, -date, or the specialized elements origPlace and -origDate, can also be used within a head element, but it -should be remembered that the head element is intended principally to -contain a heading. More structured information concerning the contents, physical -form, or history of the manuscript should be given within the specialized -elements described below, msContents, physDesc, -history, etc. However, in simple cases, the p element may also -be used to supply an unstructured collection of such information, as in the -example given above ().

-
-
-Intellectual Content -

The msContents element is used to describe the intellectual content -of a manuscript or manuscript part. It comprises either a series of -informal prose paragraphs or a series of msItem or -msItemStruct elements, each of which provides a more detailed -description of a single item contained within the manuscript. These may be -prefaced, if desired, by a summary element, which is especially useful -where one wishes to provide an overview of a manuscript's contents and describe -only some of the items in detail. - - - - - - -

-

In the simplest case, only a brief description may be provided, as in the -following examples: - - -

A collection of Lollard sermons

- - - - -

Atlas of the world from Western Europe and Africa to Indochina, containing 27 - maps and 26 tables

- - - - -

Biblia sacra: Antiguo y Nuevo Testamento, con prefacios, prólogos y - argumentos de san Jerónimo y de otros. Interpretaciones de los nombres - hebreos.

- - -

-

This description may of course be expanded to include any of the TEI elements -generally available within a p element, such as title, -bibl, or list. More usually, however, each individual work -within a manuscript will be given its own description, using the msItem -or msItemStruct element described in the next section, as in the -following example: - - -fols. 5r -7v -An ABC -IMEV -239 -fols. 7v -8v -Lenvoy de Chaucer a Scogan -IMEV -3747 -fol. 8vTruth -IMEV -809 -fols. 8v-10v -Birds Praise of Love -IMEV -1506 -fols. 10v -11v -De amico ad amicam -Responcio -IMEV -16 & 19 -fols. 14r-126v -Troilus and Criseyde -Bk. 1:71-Bk. 5:1701, with additional losses due to mutilation -throughout - - - -

-

The summary element may be used in conjunction with one or more -msItem elements if it is desired to provide both a general summary of -the contents of a manuscript and more detail about some or all of the individual -items within it. It may not however be used within an individual msItem -element.

- - -A collection of Lollard sermons -fol. 4r-8r -3rd Sunday Before Lent -fol. 9r-16v -Sexagesima - - - -
-The msItem and msItemStruct Elements -

Each discrete item in a manuscript or manuscript part can be described within -a distinct msItem or msItemStruct element, and may be -classified using the class attribute.

-

These are the possible component elements of msItem and -msItemStruct. - - - - - - - - - - - - - - - - -

-

In addition, an msItemStruct may contain nested msItemStruct -elements, just as an msItem may contain nested msItem -elements.

-

The main difference between msItem and msItemStruct is that -in the former, the order and number of child elements is not constrained; any -element, in other words, may be given in any order, and repeated as often as is -judged necessary. In the latter, however, the sub-elements, if used, must be -given in the order specified above and only some of them may be repeated; -specifically, rubric, finalRubric. incipit, -textLang and explicit can appear only once.

-

While neither msItem nor msItemStruct may contain untagged -running text, both permit an unstructured description to be provided in the form -of one or more paragraphs of text. They differ in this respect also: if -paragraphs are supplied as the content of an msItem, then none of the -other component elements listed above is permitted; in the msItemStruct -case, however, paragraphs may appear anywhere as an alternative to any of the -component elements listed above.

-

As noted above, both msItem and msItemStruct elements may -also nest, where a number of separate items in a manuscript are grouped under a -single title or rubric, as is the case, for example, with a work like The -Canterbury Tales.

-

The elements msContents, msItem, msItemStruct, -incipit, and explicit are all members of the class att.msExcerpt from which they inherit the -defective attribute. - - This attribute can be used for example with collections of -fragments, where each fragment is given as a separate msItem and the -first and last words of each fragment are transcribed as defective incipits and -explicits, as in the following example, a manuscript containing four fragments -of a single work: - - -1r-9v -Knýtlinga saga -1r:1-2v:30 -danna a englandi -en meðan haraldr hein hafði -konungr vit -yfir danmork - - - - - -

-

The elements ex, am, and expan used in the above -example are further discussed in section ; they are -available only when the transcr module defined by -that chapter is selected. Similarly, the g element used in this example -to represent the abbreviation mark is defined by the gaiji module documented in chapter .

-
-
-Authors and Titles -

When used within a manuscript description, the title element should -be used to supply a regularized form of the item's title, as distinct from any -rubric quoted from the manuscript. If the item concerned has a standardized -distinctive title, e.g. Roman de la Rose, then this -should be the form given as content of the title element, with the -value of the type attribute given as uniform. If no -uniform title exists for an item, or none has been yet identified, or if one -wishes to provide a general designation of the contents, then a -supplied title can be given, e.g. -missal, in which case the type attribute on -the title should be given the value supplied.

-

Similarly, if used within a manuscript description, the author -element should always contain the normalized form of an author's name, -irrespective of how (or whether) this form of the name is cited in the -manuscript. If it is desired to retain the form of the author's name as given in -the manuscript, this may be tagged as a distinct name element, within -the text at the point where it occurs.

- -

Note that the key attribute can also be used, as on names in -general, to specify the identifier of a person element carrying full -details of the person concerned (see further ).

-

The respStmt element can be used to supply the name and role of a -person other than the author who is responsible for some aspect of the -intellectual content of the manuscript: - -Diogenes Laertius - -in the translation of -Ambrogio Traversari - - -

-

The respStmt element can also be used where there is a discrepancy -between the author of an item as given in the manuscript and the accepted -scholarly view, as in the following example: - -Sermons on the Epistles and the Gospels - -here erroneously attributed to -St. Bonaventura - - - Note that such attributions of authorship, both correct and incorrect, are -frequently found in the rubric or final rubric (and occasionally also elsewhere -in the text), and can therefore be transcribed and included in the description, -if desired, using the rubric, finalRubric, or quote -elements, as appropriate.

-
-
-Rubrics, Incipits, Explicits, and Other Quotations from the Text -

It is customary in a manuscript description to record the opening and closing -words of a text as well as any headings or colophons it might have, and the -specialized elements rubric, incipit, explicit, -finalRubric, and colophon are available within msItem -for doing so, along with the more general quote, for recording other -bits of the text not covered by these elements. Each of these elements has the -same substructure, containing a mixture of phrase-level elements and plain text. -A locus element can be included within each, in order to specify the -location of the component, as in the following example: - - -f. 1-223 -Radulphus Flaviacensis -Expositio super Leviticum -f. 1r Forte Hervei monachi -f. 223v Benedictio salis et aquae - - - -

-

In the following example, standard TEI elements for the transcription of -primary sources have been used to mark the expansion of abbreviations and other -features present in the original: - - -ff. 1r-24v -Ágrip af Noregs konunga sǫgum - -regi oc hann seti ho -sc heim sem þio -hon hever -oc þa buit hesta .ij. -annan viþ fé en honom annan til -reiþar - - - Note here also the use of the defective attribute on -incipit and explicit to indicate that the text begins and ends -defectively.

-

The xml:lang attribute for colophon, explicit, -incipit, quote, and rubric may always be used to -identify the language of the text quoted, if this is different from the default -language specified by the mainLang attribute on -textLang.

-
- -
-Filiation -

The filiation element can be used to provide information on the -relationship between the manuscript and other surviving manuscripts of the same -text, either specifically or in a general way, as in the following example: - - -118rb -Ecce morior cum nichil horum ... [Dn 13, 43]. Verba ista -dixit Susanna de illis -ut bonum comune conservatur. -Schneyer 3, 436 (Johannes Contractus OFM) -weitere Überl. Uppsala C 181, 35r. - - -

-
-
-Text Classification -

One or more text classification or text-type codes may be specified, either -for the whole of the msContents element, or for one or more of its -constituent msItem elements, using the class attribute as -specified above: - - - -1v-71v -Jónsbók -Magnus med guds miskun Noregs konungur -enn uirda þo til fullra aura - - - The value used for the class attribute in this example points to a -category element with the identifier law, which defines -the classification concerned. Such category elements will typically -appear within a taxonomy element, within the classDecl element -of the TEI header () as in the following example: - - - - -Legislation - - -Military topics - - - - - More than one classification may apply to a single item. Another text, -concerned with legislation about military topics might thus be specified as -follows: - - -

A treatise on Clausewitz

- - - -

-
-
-Languages and Writing Systems -

The textLang element should be used to provide information about the -languages used within a manuscript item. It may take the form of a simple note, -as in the following example: - -Old Church Slavonic, written in Cyrillic script. - -

-

Where, for validation and indexing purposes, it is thought convenient to add -keywords identifying the particular languages used, the mainLang -attribute may be used. This attribute takes the same range of values as the -global xml:lang attribute, on which see further . In the following example a manuscript written chiefly in Old Church Slavonic -is described: - -Old Church Slavonic - -

- -

A manuscript item will sometimes contain material in more than one language. -The mainLang attribute should be used only for the chief language. -Other languages used may be specified using the otherLangs attribute -as in the following example: - -Mostly Old Church Slavonic, with -some Russian and Greek material - -

-

Since Old Church Slavonic may be written in either Cyrillic or Glagolitic -scripts, and even occasionally in both within the same manuscript, it might be -preferable to use a more explicit identifier: - -Old Church Slavonic in Cyrillic script - -

-

The form and scope of language identifiers recommended by these Guidelines is -based on the IANA standard described at and should be -followed throughout. 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 .

-

Note that the language element defines a particular combination of -human language and writing system. Only one language element may be -supplied for each such combination. Standard TEI practice also allows this -element to be referenced by any element using the global xml:lang -attribute in order to specify the language applicable to the content of that -element. For example, assuming that language elements have been defined -with the identifiers fr (for French), la (for -Latin), and de (for German), a manuscript description written in -French which specifies that a particular manuscript contains predominantly -German but also some Latin material, might have a textLang element like -the following: - -allemand et -latin - -

- - - - - - - - - - - - - - - - - -
-
-
-Physical Description -

Under the general heading physical description we -subsume a large number of different aspects generally regarded as useful in the -description of a given manuscript. These include: -aspects of the form, support, extent, and quire structure of the -manuscript object and of the way in which the text is laid out on the page (); -the styles of writing, such as the way it is laid out on the page, the -styles of writing, decorative features, any musical notation employed and any -annotations or marginalia (); - and discussion of its binding, seals, and any accompanying material (). -

-

Most manuscript descriptions touch on several of these categories of -information though few include them all, and not all distinguish them as clearly -as we propose here. In particular, it is often the case that an existing -description will include information for which we propose distinct elements -within a single paragraph, or even sentence. The encoder must then decide -whether to rewrite the description using the structure proposed here, or to -retain the existing prose, marked up simply as a series of p elements, -directly within the physDesc element.

-

The physDesc element may thus be used in either of two distinct -ways. It may contain a series of paragraphs addressing topics listed above and -similar ones. Alternatively, it may act as a container for any choice of the -more specialized elements described in the remainder of this section, each of -which itself contains a series of paragraphs, and may also have more specific -attributes. -

-

In general, it is not recommended to combine unstructured prose description -with usage of the more specialized elements, as such an approach complicates -processing, and may lead to inconsistency within a single manuscript -description. A single physDesc element will normally contain either a -series of model.pLike elements, or a sequence of -specialized elements from the model.physDescPart -class. There are however circumstances in which this is not feasible, for -example: -the description already exists in a prose form where some of the -specialized topics are treated together in paragraphs of prose, but others are -treated distinctly; -although all parts of the description are clearly distinguished, some of -them cannot be mapped to a pre-existing specialized element. -

-

In such situations, both specialized and generic (model.pLike) elements may be combined in a single physDesc. -Note however that all generic elements given must precede the first specialized -element in the description. Thus the following is valid: - - -

Generic descriptive prose...

- - - - - - - but neither of the following is valid: - - - - -

Generic descriptive prose...

-]]> - - - - -

Generic descriptive prose...

- -]]> - The order in which specific elements may appear is also constrained by the -content model; again this is for simplicity of processing. They may of course be -processed or displayed in any desired order, but for ease of validation, they -must be given in the order specified below.

-
-Object Description -

The objectDesc element is used to group together those parts of the -physical description which relate specifically to the text-bearing object, its -format, constitution, layout, etc. The objectDesc element is used for grouping - elements relating to the physicality of a text-bearing object as part of a manuscript - description. If a full description of an object (text-bearing or not) is desired, the - more general object element may be preferred. -

-

The form attribute is used to -indicate the specific type of writing vehicle being described, for example, as a -codex, roll, tablet, etc. If used it must appear first in the sequence of -specialized elements. The objectDesc element has two parts: a -description of the support, i.e. the physical carrier on which the -text is inscribed; and a description of the layout, i.e. the way -text is organized on the carrier. -

-

Taking these in turn, the description of the support is tagged using the -following elements, each of which is discussed in more detail below: - - - - - - -

-

Each of these elements contains paragraphs relating to the topic concerned. -Within these paragraphs, phrase-level elements (in particular those discussed -above at ), may be used to tag specific terms of -interest if so desired. - - - -

Mostly paper, with watermarks -unicorn (Briquet 9993) and -ox (close to Briquet 2785). The first and last -leaf of each quire, with the exception of quires xvi and xviii, are constituted -by bifolia of parchment, and all seven miniatures have been painted on inserted -singletons of parchment.

- - - -

-

This example combines information which might alternatively be more precisely -tagged using the more specific elements described in the following -subsections.

-
-Support -

The support element groups together information about the physical -carrier. Typically, for western manuscripts, this will entail discussion of the -material (parchment, paper, or a combination of the two) written on. For paper, -a discussion of any watermarks present may also be useful. If this discussion -makes reference to standard catalogues of such items, these may be tagged using -the standard ref element as in the following example: - -

-Paper with watermark: anchor in a circle with -star on top, countermark B-B with trefoil - similar to Mošin, Anchor N 1680 -1570-1585.

- -

-
-
-Extent -

The extent element, defined in the TEI header, may also be used in a -manuscript description to specify the number of leaves a manuscript contains, as -in the following example: - -ii + 97 + ii - - Information regarding the size of the leaves may be specifically marked using -the phrase level dimensions element, as in the following example, or -left as plain prose. - -ii + 321 leaves -35 -27 - - - -

-

Alternatively, the generic measure element might be used within -extent, as in the following example: - - -10 Bl. -37 x 29 cm - -

-
-
-Collation -

The collation element should be used to provide a description of a -book's current and original structure, that is, the arrangement of its leaves -and quires. This information may be conveyed using informal prose, or any -appropriate notational convention. Although no specific notation is defined -here, an appropriate element to enclose such an expression would be the -formula element, which is provided when the figures module is included in a schema. Here are some examples of -different ways of treating collation: - -

1-3:8, 4:6, 5-13:8

- -

There are now four gatherings, the first, second and fourth originally -consisting of eight leaves, the third of seven. A fifth gathering thought to -have followed has left no trace. -Gathering I consists of 7 leaves, a first leaf, originally conjoint with -fol. 7, having been cut away leaving only a narrow strip along -the gutter; the others, fols 1 and 6, -2 and 5, and 3 and -4, are bifolia. -Gathering II consists of 8 leaves, 4 bifolia. -Gathering III consists of 7 leaves; fols 16 and -22 are conjoint, the others singletons. -Gathering IV consists of 2 leaves, a bifolium. -

- -

I (1, 2+9, 3+8, 4+7, 5+6, 10); II (11, 12+17, 13, 14, 15, 16, 18, -19).

 - -

1-5.8 6.6 (catchword, f. 46, does not match following text) 7-8.8 -9.10, 11.2 (through f. 82) 12-14.8 15.8(-7) -

- - -

-
-
-Foliation -

The foliation element may be used to indicate the scheme, medium or -location of folio, page, column, or line numbers written in the manuscript, -frequently including a statement about when and, if known, by whom, the -numbering was done. - -

Neuere Foliierung, die auch das Vorsatzblatt mitgezählt -hat.

-

Folio numbers were added in brown ink by Árni Magnússon ca. -1720-1730 in the upper right corner of all recto-pages.

 - -

-

Where a manuscript contains traces of more than one foliation, each should be -recorded as a distinct foliation element and optionally given a -distinct value for its xml:id attribute. The locus element -discussed in can then indicate which foliation scheme is -being cited by means of its scheme attribute, which points to this -identifier: - -

Original foliation in red roman numerals in the -middle of the outer margin of each recto

-

Foliated in pencil in the top right corner of each -recto page.

 - -ff 1-20 - -

-
-
-Condition -

The condition element is used to summarize the overall physical -state of a manuscript, in particular where such information is not recorded -elsewhere in the description. It should not, however, be used to describe -changes or repairs to a manuscript, as these are more appropriately described as -a part of its custodial history (see ). It should be -supplied within the supportDesc element, if it discusses the condition -of the physical support of the manuscript; within the bindingDesc or -binding elements () if it discusses only the -condition of the binding or bindings concerned; or within the sealDesc -element if it discusses the condition of any seal attached to the -manuscript.

- - -

The manuscript shows signs of damage from water and mould on its -outermost leaves.

 - - - -

Despite tears on many of the leaves the codex is reasonably well -preserved. The top and the bottom of f. 1 is damaged, and only a thin slip is -left of the original second leaf (now foliated as 1bis). The lower margin of f. -92 has been cut away. There is a lacuna of one leaf between ff. 193 and 194. The -manuscript ends defectively (there are approximately six leaves -missing).

 - - -
-
-Layout Description -

The second part of the objectDesc element is the layoutDesc -element, which is used to describe and document the -mise-en-page of the manuscript, that is the way in which text -and illumination are arranged on the page, specifying for example the number of -written, ruled, or pricked lines and columns per page, size of margins, distinct -textual streams such as glosses, commentaries, etc. This may be given as a simple series -of paragraphs. Alternatively, one or more different layouts may be identified -within a single manuscript, each described by its own layout element. - - -

-

Where the layout element is used, the layout will often be -sufficiently regular for the attributes on this element to convey all that is -necessary; more usually however a more detailed treatment will be required. The -attributes are provided as a convenient shorthand for commonly occurring cases, -and should not be used except where the layout is regular. The value -NA (not-applicable) should be used for cases where the layout is -either very irregular, or where it cannot be characterized simply in terms of -lines and columns, for example, where blocks of commentary and text are arranged -in a regular but complex pattern on each page

-

The following examples indicate the range of possibilities: - - -

Most pages have between 25 and 32 long lines ruled in lead.

- - -

Written in one column throughout; 24 lines per page.

- -

Written in 3 columns, with 8 lines of text and interlinear glosses in -the centre, and up to 26 lines of gloss in the outer two columns. Double -vertical bounding lines ruled in hard point on hair side. Text lines ruled -faintly in lead. Remains of prickings in upper, lower, and outer (for 8 lines of -text only) margins.

 - -

-

Where multiple layout elements are supplied, the scope for each -specification can be indicated by means of locus elements within the -content of the element, as in the following example: - - - -

On fols 1r-200v and fols 210r-212v there are between 25 and 32 ruled lines.

- - -

On fols 203r-209v there are between 34 -and 50 ruled lines.

- - -

-
-
-
-Writing, Decoration, and Other Notations -

The second group of elements within a structured physical description -concerns aspects of the writing, illumination, or other notation (notably, -music) found in a manuscript, including additions made in later hands—the -text, as it were, as opposed to the carrier. - - - - - - - - - - -

-
-Writing -

The handDesc element can contain a short description of the general -characteristics of the writing observed in a manuscript, as in the following -example: - - -

Written in a late Caroline minuscule; versals in a form of -rustic capitals; although the marginal and interlinear gloss is -written in varying shades of ink that are not those of the main text, text and -gloss appear to have been copied during approximately the same time span.

- - -

-

Note the use of the term element to mark specific technical terms -within the context of the handDesc element.

-

Where several distinct hands have been identified, this fact can be -registered by using the hands attribute, as in the following example: - - -

The manuscript is written in two contemporary hands, otherwise unknown, but -clearly those of practised scribes. Hand I writes ff. 1r-22v and hand II ff. 23 -and 24. Some scholars, notably Verner Dahlerup and Hreinn Benediktsson, have -argued for a third hand on f. 24, but the evidence for this is -insubstantial.

- - -

-

Alternatively, or in addition, where more specific information about one or -more of the hands identified is to be recorded, the handNote element -should be used, as in the following example: - - - -

The first part of the manuscript, fols -1v-72v:4, is written in a practised Icelandic Gothic bookhand. This hand -is not found elsewhere.

- -

The second part of the manuscript, fols -72v:4-194, is written in a hand contemporary with the first; it can also -be found in a fragment of Knýtlinga saga, AM 20b II -fol..

 - -

The third hand has written the majority of the chapter headings. This hand -has been identified as the one also found in AM 221 -fol..

 - - - Note here the use of the locus element, discussed in section , to specify exactly which parts of a manuscript are written by -a given hand.

-

When a full or partial transcription of a manuscript is available in addition -to the manuscript description, the handShift element described in can be used to link the relevant parts of the transcription to -the appropriate handNote element in the description: for example, at -the point in the transcript where the second hand listed above starts (i.e. at -folio 72v:4), we might insert handShift new="#Eirsp-2"/.

-

Additions, notes, drawings etc. (e.g. add, note and figure) made by other hands - in the text, can be linked to the corresponding handNote element using the hand attribute.

-

The elements typeDesc, and typeNote are used to provide -information about the printing of a source, in exactly the same way as the -handDesc or handNote elements provide information about its -writing. They are provided for the convenience of those using this module to -provide information about early printed sources and incunables. The -typeDesc element can simply provide a summary description: - -

Uses a mixture of Roman and Black Letter types.

- -

-

Where detailed information about individual typefaces is to be recorded, this -may be done using the typeNote element: - -

Uses a mixture of Roman and Black Letter types. -Antiqua typeface, showing influence of Jenson's Venetian -fonts. -The black letter face is a variant of Schwabacher. - - -

-

Where information is required about both typography and written script, for -example where a printed book contains extensive handwritten annotation, both -handDesc and typeDesc elements should be supplied. Similarly, -in the following example, the source text is a typescript with extensive -handwritten annotation: - - -Authorial typescript, probably produced on Eliot's own -Remington. - - -Ezra Pound's annotations. -Commentary in Eliot's hand. - - -

-

The elements scriptNote and scriptDesc may be used in -exactly the same way to document a script used in this and other manuscripts, -for example to record that this script was used mainly for the production of -books or for charters; or that it is characteristic of some geographical area or -scriptorium or date. Such information as the letter forms characteristic of this -script may also be recorded. By contrast, the handNote element would be -used to document the way that a particular scribe uses a script, for example -with long or short descenders, or using a pen which is cut in a different way, -or an ink of a given colour, and so forth.

-

As with typeNote, the scriptNote element can be used in -combination with handNote.

-
-
-Decoration -

It can be difficult to draw a clear distinction between aspects of a -manuscript which are purely physical and those which form part of its -intellectual content. This is particularly true of illuminations and other forms -of decoration in a manuscript. We propose the following elements for the purpose -of delimiting discussion of these aspects within a manuscript description, and -for convenience locate them all within the physical description, despite the -fact that the illustrative features of a manuscript will in many cases also be -seen as constituting part of its intellectual content.

-

The decoDesc element may contain simply one or more paragraphs -summarizing the overall nature of the decorative features of the manuscript, as -in the following example: - - -

The decoration comprises two full page miniatures, perhaps added by the -original owner, or slightly later; the original major decoration consists of -twenty-three large miniatures, illustrating the divisions of the Passion -narrative and the start of the major texts, and the major divisions of the -Hours; seventeen smaller miniatures, illustrating the suffrages to saints; and -seven historiated initials, illustrating the pericopes and major prayers.

- - - Alternatively, it may contain a series of more specific typed decoNote -elements, each summarizing a particular aspect or individual instance of the -decoration present, for example the use of miniatures, initials (historiated or -otherwise), borders, diagrams, etc., as in the following example: - - - -

One full-page miniature, facing the beginning of the first Penitential -Psalm.

- - -

One seven-line historiated initial, commencing the first Penitential -Psalm.

- - -

Six four-line decorated initials, commencing the second through the seventh -Penitential Psalm.

- - -

Some three hundred two-line versal initials with pen-flourishes, commencing -the psalm verses.

- - -

Four-sided border decoration surrounding the miniatures and three-sided -border decoration accompanying the historiated and decorated initials.

- - - -

-

Where more exact indexing of the decorative content of a manuscript is -required, the standard TEI elements term or index may be used -within the prose description to supply or delimit appropriate iconographic -terms, as in the following example: - - - -

Fourteen large miniatures with arched tops, above five lines of text: -fol. 14rPericopes. St. John writing on Patmos, -with the Eagle holding his ink-pot and pen-case; some flaking of pigment, -especially in the sky -fol. 26rHours of the Virgin, Matins. -Annunciation; Gabriel and the Dove to the right -fol. 60rPrime. Nativity; the Virgin and -Joseph adoring the Child -fol. 66rTerce. Annunciation to the Shepherds, -one with bagpipes - -

- - - -

-
-
-Musical Notation -

Where a manuscript contains music, the musicNotation element may be -used to describe the form of notation employed, as in the following examples: - - -

Square notation on 4-line red staves.

- - - -

Neumes in campo aperto of the St. Gall type.

- - -

If a manuscript employs more than one notation, they must both be described within the -same musicNotation element, for example as different list items.

-
-
-Additions and Marginalia -

The additions element can be used to list or describe any additions -to the manuscript, such as marginalia, scribblings, doodles, etc., which are -considered to be of interest or importance. Such topics may also be discussed or -referenced elsewhere in a description, for example in the history -element, in cases where the marginalia provide evidence of ownership. Note that -this element may not be repeated within a single manuscript description. If -several different kinds of additional matter are discussed, the content may be -structured as a labelled list or a series of paragraphs. Some examples follow: - -

Doodles on most leaves, possibly by children, and often quite -amusing.

- -

Quelques annotations marginales des XVIe et XVIIe s.

 - - -

The text of this manuscript is not interpolated with sentences from Royal -decrees promulgated in 1294, 1305 and 1314. In the margins, however, another -somewhat later scribe has added the relevant paragraphs of these decrees, see -pp. 8, 24, 44, 47 etc.

-

As a humorous gesture the scribe in one opening of the manuscript, pp. 36 and -37, has prolonged the lower stems of one letter f and five letters þ and has -them drizzle down the margin.

- - - -

Spaces for initials and chapter headings were left by the scribe but not -filled in. A later, probably fifteenth-century, hand has added initials and -chapter headings in greenish-coloured ink on fols 8r, -8v, 9r, 10r and 11r. -Although a few of these chapter headings are now rather difficult to read, most -can be made out, e.g. fol. 8rb -floti astridar; fol. -9rb -vm olaf conung, and fol. -10ra -Gipting olafs -konungs.

-

The manuscript contains the following marginalia: -Fol. 4v, left margin: hialmadr -ok -brynjadr, in a fifteenth-century hand, imitating an addition made -to the text by the scribe at this point. -Fol. 5r, lower margin: þetta -þiki mer vera gott blek ennda kann ek icki -betr sia, in a fifteenth-century hand, probably the same as that on the -previous page. -Fol. 9v, bottom margin: þessa bok -uilda eg gæt lært med -an Gud gefe myer Gott ad -læra; seventeenth-century hand. -

-

There are in addition a number of illegible scribbles in a later hand (or -hands) on fols 2r, 3r, 5v and -19r.

- - -

-
-
-
-Bindings, Seals, and Additional Material -

The third major component of the physical description relates to supporting -but distinct physical components, such as bindings, seals and accompanying -material. These may be described using the following specialist elements: - - - - - -

-
-Binding Descriptions -

The bindingDesc element contains a description of the state of the -present and former bindings of a manuscript, including information about its -material, any distinctive marks, and provenance information. This may be given -as a series of paragraphs if only one binding is being described, or as a series -of distinct binding elements, each describing a distinct binding where -these are separately described. For example: - - -

Sewing not visible; tightly rebound over 19th-century pasteboards, reusing -panels of 16th-century brown leather with gilt tooling à la fanfare, Paris c. -1580-90, the centre of each cover inlaid with a 17th-century oval medallion of -red morocco tooled in gilt (perhaps replacing the identifying mark of a previous -owner); the spine similarly tooled, without raised bands or title-piece; -coloured endbands; the edges of the leaves and boards gilt. Boxed.

- - -

-

Within a binding description, the elements decoNote and -condition are available, as alternatives to p, for paragraphs -dealing exclusively with information about decorative features of a binding, or -about its condition, respectively. - -

Bound, s. XVIII (?), in diced russia leather -retaining most of the original 15th century metal ornaments (but with some -replacements) as well as the heavy wooden boards.

-

On each cover: alternating circular stamps of the Holy Monogram, a -sunburst, and a flower.

 -

On the cornerpieces, one of which is missing, a rectangular stamp -of the Agnus Dei.

 -Front and back leather inlaid panels very badly worn. -

Rebacked during the 19th century.

- - -

-

As noted above, () the element condition may -also be used as an alternative to p for paragraphs concerned -exclusively with the condition of a binding, where this has not been supplied as -part of the physical description.

-
-
-Seals -

The sealDesc element supplies information about the seal(s) attached -to documents to guarantee their integrity, or to show authentication of the -issuer or consent of the participants. It may contain one or more paragraphs -summarizing the overall nature of the seals, or may contain one or more -seal elements. - - - -

Round seal of Anders Olufsen in black wax: DAS -930. Parchment tag, on which is written: pertinere nos -predictorum placiti nostri iusticarii precessorum dif.

- -

The seal of Jens Olufsen in black wax: DAS -1061. Legend: S IOHANNES OLAVI. Parchment tag on -which is written: Woldorp Iohanne G.

- - - -

-
-
-Accompanying Material -

The circumstance may arise where material not originally part of a manuscript -is bound into or otherwise kept with a manuscript. In some cases this material -would best be treated in a separate msPart element (see below). There are, however, cases where the additional matter -is not self-evidently a distinct manuscript: it might, for example, be a set of -notes by a later scholar, or a file of correspondence relating to the -manuscript. The accMat element is provided as a holder for this kind of -information. - -

-

Here is an example of the use of this element, describing a note by the -Icelandic manuscript collector Árni Magnússon which has been bound with the -manuscript: - - -

A slip in Árni Magnússon's hand has been stuck to the pastedown on the inside -front cover; the text reads: Þidreks Søgu þessa hefi eg -feiged af Sekreterer Wielandt Anno 1715 i Kaupmanna høfn. Hun er, sem eg sie, -Copia af Austfirda bókinni (Eidagás) enn ecki progenies Brædratungu -bokarinnar. Og er þar fyrer eigi i allann máta samhlioda -þeirre er Sr Jon Erlendz son hefer ritad fyrer Mag. Bryniolf. Þesse -Þidreks Saga mun vera komin fra Sr Vigfuse á Helgafelle.

- - -

- - - - - - - - - - - - - - - - - - - - - - - - - - - -
-
-
-
-History -

The following elements are used to record information about the history of a -manuscript: - - - - -

-

The three components of the history element all have the same -substructure, consisting of one or more paragraphs marked as p -elements. Each of these three elements is also a member of the att.datable attribute class, itself a member of the att.datable.w3c class, and thus also carries the following -optional attributes: - -

-

Information about the origins of the manuscript, its place and date of -writing, should be given as one or more paragraphs contained by a single -origin element; following this, any available information on distinct -stages in the history of the manuscript before its acquisition by its current -holding institution should be included as paragraphs within one or more -provenance elements. Finally, any information specific to the means by -which the manuscript was acquired by its present owners should be given as -paragraphs within the acquisition element.

-

Here is a fairly simple example of the use of this element: - - -

Written in Durham during the mid-twelfth -century.

-

Recorded in two medieval catalogues of the books belonging to -Durham Priory, made in 1391 and -1405.

 -

Given to W. Olleyf by William Ebchester, Prior (1446-56) and later belonged to -Henry Dalton, Prior of Holy Island (Lindisfarne) according to inscriptions on ff. 4v and 5.

- -

Presented to Trinity College in -1738 by Thomas Gale and his son Roger.

 - - -

-

Here is a fuller example, demonstrating the use of multiple -provenance elements where distinct periods of ownership for the -manuscript have been identified: - - - Written in Spain or Portugal in the -middle of the 13th century (the date 1042, given in a marginal note on f. 97v, -cannot be correct.) -The Spanish scholar Benito Arias Montano -(1527-1598) has written his name on f. 97r, and may be presumed to have owned -the manuscript. -It came somehow into the possession of etatsråd -Holger Parsberg (1636-1692), who has written his name -twice, once on the front pastedown and once on f. 1r, the former dated -1680 and the latter 1682. -Following Parsberg's death the manuscript was bought by -etatsråd -Jens Rosenkrantz (1640-1695) when Parsberg's library -was auctioned off (23 October 1693). -The manuscript was acquired by -Árni Magnússon from the estate of Jens Rosenkrantz, presumably at auction (the -auction lot number 468 is written in red chalk on the flyleaf), either in 1696 -or 97. - - -

- - - - - - -
-
- Additional Information -

Three categories of additional information are provided for by - the scheme described here, grouped together within the - additional element described in this section. - - - - - -

-

None of these specialized constituent elements of -additional is required. If any is supplied, it may appear -once only; furthermore, the order in which elements are supplied -should be as specified above. Alternatively, additional information may be -provided as either one or more paragraphs or anonymous blocks, marked up as -a series of p or ab elements.

- - - -
-Administrative Information -

The adminInfo element is used to hold information relating to the -curation and management of a manuscript. This may be supplied as a note using -the global note element. Alternatively, different aspects of this -information may be presented grouped within one of the following -specialized elements: - - - -

-
-Record History -

The recordHist element may contain simply a series of paragraphs. -Alternatively it may contain a source element, followed by an optional -series of change elements. - - -

-

The source element is used to document the primary source of -information for the record containing it, in a similar way to the standard TEI -sourceDesc element within a TEI Header. If the record is a new one, -made without reference to anything other than the manuscript itself, then it may -simply contain a p element, as in the following example: - -

Directly catalogued from the original manuscript.

- -

-

Frequently, however, the record will be derived from some previously existing -description, which may be specified using the standard TEI bibl -element, as in the following example: - - -

Information transcribed from The index of Middle English -verse123.

- - -

-

If, as is likely, a full bibliographic description of the source from which -cataloguing information was taken is included within the listBibl -element contained by the current additional element, or elsewhere in -the current document, then it need not be repeated here. Instead, it should be -referenced using the standard TEI ref element, as in the following -example: - - - - -

Information transcribed from IMEV -123.

- - - - - -Carleton Brown and Rossell Hope Robbins -The index of Middle English verse -New York -1943 - - - - - -

-

The change element may also appear within the revisionDesc -element of the standard TEI header; its use here is intended to signal the -similarity of function between the two container elements. Where the TEI header -should be used to document the revision history of the whole electronic file to -which it is prefixed, the recordHist element may be used to document -changes at a lower level, relating to the individual description, as in the -following example: - -On 10 March 2005 MJD added provenance -information - -

-
-
-Availability and Custodial History -

The availability element is another element also available in the -TEI header, which should be used here to supply any information concerning -access to the current manuscript, such as its physical location (where this is -not implicit in its identifier), any restrictions on access, information about -copyright, etc. - - -

Viewed by appointment only, to be arranged with curator.

- - -

In conservation, Jan. - Mar., 2002. On loan to the Bayerische -Staatsbibliothek, April - July, 2002.

- - -

The manuscript is in poor condition, due to many of the leaves being brittle -and fragile and the poor quality of a number of earlier repairs; it should -therefore not be used or lent out until it has been conserved.

- - -

-

The custodialHist record is used to describe the custodial history -of a manuscript, recording any significant events noted during the period that -it has been located within its holding institution. It may contain either a -series of p elements, or a series of custEvent elements, each -describing a distinct incident or event, further specified by a type -attribute, and carrying dating information by virtue of its membership in the -att.datable class, as noted above. - -

-

Here is an example of the use of this element: - - - -

Conserved between March 1961 and February 1963 at Birgitte Dalls -Konserveringsværksted.

- -

Photographed in May 1988 by AMI/FA.

 - -

Dispatched to Iceland 13 November 1989.

 - - -

- - - - - - - - -
-
-
-Surrogates -

The surrogates element is used to provide information about -representations such as photographs or other representations of the manuscript -which may exist within the holding institution or elsewhere. - -

-

The surrogates element should not be used to repeat information -about representations of the manuscript available within published works; this -should normally be documented within the listBibl element within the -additional element. However, it is often also convenient to record -information such as negative numbers or digital identifiers for unpublished -collections of manuscript images maintained within the holding institution, as -well as to provide more detailed descriptive information about the surrogate -itself. Such information may be provided as prose paragraphs, within which -identifying information about particular surrogates may be presented using the -standard TEI bibl element, as in the following example: - - -microfilm (master)G.neg. 160 -n.d. -microfilm (archive)G.pos. 186 -n.d. -b/w printsAM 795 4to -27 January 1999copy of G.pos. -186 -b/w printsreg.nr. 75 -25 January 1999 -photographs of the spine, outside covers, stitching etc. - - - - Note the use of the specialized form of title (general material -designation) to specify the kind of surrogate being documented.

-

At a later revision, the content of the surrogates element is likely -to be expanded to include elements more specifically intended to provide -detailed information such as technical details of the process by which a digital -or photographic image was made. For information about the inclusion of digital -facsimile images within a TEI document, refer also to .

- - - -
-
-
-Manuscript Parts -

The msPart element may be used in cases where manuscripts or parts -of manuscripts that were originally physically separate have been bound together -and/or share the same call number. - -

-

Since each component of such a composite manuscript will in all likelihood -have its own content, physical description, history, and so on, the structure of -msPart is in the main identical to that of msDesc, allowing -one to retain the top level of identity (msIdentifier), but to branch -out thereafter into as many parts, or even subparts, as necessary. - - - - - - - - -Brussels -Koninklijke Bibliotheek van België / Bibliothèque royale de -Belgique -ms. 10066-77 - -

Miscellany of various texts; Prudentius, -Psychomachia; Physiologus de natura animantium -Latin - - - - - -ms. 10066-77 ff. 140r-156v - -Physiologus -Latin - - - -ms. 10066-77 ff. 112r-139r - - -Prudentius, Psychomachia -Latin - - - - -

- - - -
-
-Manuscript Fragments -

The msFrag element may be used inside msDesc when encoding -one or more fragments of a scattered or fragmented manuscript. The fragment(s) -described in a single msDesc element may be held either at several -institutions or at a single institution, so different call numbers may be -attached to the fragments. Inside the msFrag element, information about -the single fragment or each dispersed part is provided: e.g. the current -shelfmark or call number, the labels of the range of folios concerned if the -fragment currently forms part of a larger manuscript, dimensions, extent, title, -author, annotations, illuminations and so on. - -

-

One well-known example of fragmentation is the Old Church Slavonic manuscript -known as Codex Suprasliensis, substantial parts of which are to -be found in three separate repositories, in Ljubljana, Warsaw, and St. -Petersburg. This manuscript should be represented using one single -msDesc element in which msName is used to identify the -fragmented manuscript, along with three distinct msFrag elements, each -of which contains the current identifier of one of the fragments, a physical -description, and other related information: - - - -Codex Suprasliensis - - - -Ljubljana -Narodna in univerzitetna knjiznica -MS Kopitar 2 - - -

Contains ff. 10 to 42 only - - - - -Warszawa -Biblioteka Narodowa -BO 3.201 - - - - -Sankt-Peterburg -Rossiiskaia natsional'naia biblioteka -Q.p.I.72 - - - - -

- - - -
-
- Module for Manuscript Description -

The module described in this chapter makes available the following - components: - - Manuscript Description - Manuscript Description - Description de manuscrits - 寫本描述 - Descrizione di manoscritti - Descrição do manuscrito - 手書きモジュール - - The selection and combination of modules to form a TEI schema is - described in .

- - - - - - - - - - - - - -
-
diff --git a/P5/Source/Guidelines/fr/MS-ManuscriptDescription.xml b/P5/Source/Guidelines/fr/MS-ManuscriptDescription.xml new file mode 120000 index 0000000000..ad777996bd --- /dev/null +++ b/P5/Source/Guidelines/fr/MS-ManuscriptDescription.xml @@ -0,0 +1 @@ +../en/./MS-ManuscriptDescription.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/ND-NamesDates.xml b/P5/Source/Guidelines/fr/ND-NamesDates.xml deleted file mode 100644 index 7f4fd5c4b0..0000000000 --- a/P5/Source/Guidelines/fr/ND-NamesDates.xml +++ /dev/null @@ -1,3059 +0,0 @@ - - - - -
- - Names, Dates, People, and Places - -

This chapter describes a module which may be used for the encoding of names and other phrases descriptive of persons, places, - or organizations, in a manner more detailed than that possible using the elements already provided for these purposes in the - Core module. In section it was noted that the elements provided in the core module allow an encoder to - specify that a given text segment is a proper noun, or a referring string, and to specify the kind of object - named or referred to only by supplying a value for the type attribute. The elements provided by the present module - allow the encoder to supply a detailed sub-structure for such referring strings, and to distinguish explicitly between names - of persons, places, and organizations.

- -

This module also provides elements for the representation of information about the person, place, or organization to which a - given name is understood to refer and to represent the name itself, independently of its application. In simple terms, where - the core module allows one simply to represent that a given piece of text is a name, this module allows one - further to represent a personal name, to represent the person being named, and to represent the - canonical name being used. A similar range is provided for names of places and organizations. The main intended - applications for this module are in biographical, historical, or geographical data systems such as gazetteers and biographical - databases, where these are to be integrated with encoded texts.

- -

The chapter begins by discussing attributes common to many of the elements discussed in the remaining parts of the chapter - () before discussing specifically the elements provided for the encoding of component parts of - personal names (section ), place names (section ) and organizational names - (section ). Elements for encoding personal and organizational data are discussed in section . Elements for the encoding of geographical data are discussed in section . - Finally, elements for encoding onomastic data are discussed in , and the detailed encoding of dates and - times is described in section .

- - - -
- Attribute Classes Defined by This Module -

Most of the elements made available by this chapter share some important characteristics which are expressed by their - membership in specific attribute classes. Members of the class att.naming have specialized - attributes which support linkage of a naming element with the entity (person, place, organization) being named; members of - the class att.datable have specialized attributes which support a number of ways of normalizing - the date or time of the data encoded by the element concerned.

- -
- Linking Names and Their Referents - -

The class att.naming is a subclass of the class att.canonical, - from which it inherits the following attributes: - - As discussed in , these attributes provide two different ways of associating any sort - of name with its referent. For cases where all that is required is to provide some minimal information about the person - name, for example their occupation or status, the att.naming class also provides a simple - role attribute. It also provides an additional attribute, which allows the name itself to be associated with - a base or canonical form: - - The encoder may use these attributes in combination as appropriate. For example: That silly man David Paul Brown - has suffered ... The ref attribute should be used wherever it is possible to supply a direct link - such as a URI to indicate the location of canonical information about the referent. That silly man David Paul Brown has - suffered ... This encoding requires that there exist somewhere a person element with the identifier - DPB1, which will contain canonical information about this particular person, marked up using the elements - discussed in below. The same element might alternatively be provided by some other document, of - course, which the same attribute could refer to by means of a URI, as explained in : That silly man David Paul Brown has suffered ...More than one URI may be supplied if the name refers to - more than one person. For example, assuming the existence of another person element for Mrs Brown, with - identifier EBB1, a reference to the Browns might be encoded That wretched pair the Browns came - to dine ... -

- -

The key attribute is provided for cases where no such direct link is required: for example because resolution - of the reference is carried out by some local convention, or because the encoder judges that no such resolution is - necessary. As an example of the first case, a project might maintain its own local database system containing canonical - information about persons and places, each entry in which is accessed by means of some system-specific identifier - constructed in a project-specific way from the value supplied for the key attribute.In the - module described by chapter a similar method is used to link element descriptions to the modules or - classes to which they belong, for example. As an example of the second case, consider the use of well-established - codifications such as country or airport codes, which it is probably unnecessary for an encoder to expand further: I never fly from Heathrow Airport to France -

- -

However, as explained in , interchange is improved by use of tag URIs in ref instead of - key.

- -

The nymRef attribute has a more specialized use, where it is the name itself which is of interest rather than - the person, place, or organization being named. See section for further discussion.

- -

All members of the att.naming class inherit the following attributes from the att.global.responsibility class: - - This enables an encoder to record the agency responsible for a given assertion (for example, the name) and the - confidence placed in that assertion by the encoder. Examples are given below.

-
- -
- Dating Attributes - -

Members of the att.datable class share the following attributes: - - - -

-

The when attribute is used to specify a normalized form for any temporal expression, independently of how it - is represented in the text, as in the following example: June 9th The period is approaching which will terminate my present - copartnership. On the 1st Jany. next, it expires by its own limitation. -

-

The period attribute provides a convenient way of associating an event or date with a named period. Its value - is a pointer which should indicate some other element where the period concerned is more precisely defined. A convenient - location for such definitions is the taxonomy element in the classDecl (classification declaration) in - the encodingDesc of a TEI header. A taxonomy may contain simply a bibliographic reference to an external - definition for it. More usefully, it may also contain a series of category elements, each with an identifier and - a description. The identifier can then be used as the target for a period attribute. For example, a taxonomy of - named periods might be defined as follows: - - - Before 510 BC - - Between 510 and 323 BC - - - Hellenistic. Commonly treated as from the death of Alexander to the Roman conquest. - - - - - Roman - - - - The Christian period technically starts at the birth of Jesus, but in practice is considered to date from - the conversion of Constantine in 312 AD. - - - -

-

With these definitions in place, any datable element may be associated with a specific period: - Stauropolis

-

The other dating attributes provided by this class support a wide range of methods of specifying temporal information in - a normalized form. The from and to attributes may be used to express the begining and ending of a - period of time, for example: - - - A political and social protest campaign against the policy of racial segregation on the public transit system of - the city of Montgomery. - -

-

The notBefore and notAfter attributes may be used to express a range of possibilities for a - particular date (or time). For example the following element, extracted from an imaginary prosopographic entry for Anne - Calthorpe, indicates that although the exact date of her death is not known, it can be narrowed down to a particular - range: from 22 August 1579 to 28 March 1582, inclusive. Ostensibly the encoder has evidence that Anne Calthorpe was alive - on the 22nd of August 1579 and evidence that she was already dead on the 28th of March 1582. - -

-

Since when is used for a particular date or time, from and to for a duration, and - notBefore and notAfter for a date or time within a range, it makes no sense to use when - in combination with one or more of the others. Thus these Guidelines at present recommend against the use of - when in combination with any of from, to, notBefore, or - notAfter.

-

The from or to attributes imply that the temporal expression to which they are attached signifies a - duration, so the use of either with notBefore or notAfter means a duration is indicated. - - - notBefore - from - - - notAfter - range of possibilities, inclusive - duration from from to sometime before - notAfter, inclusive - - - to - duration from sometime after notBefore to - to, inclusive - duration from from to to, inclusive - -
-

- - -

Some further self-explanatory examples follow: - 15 March 1857. - - - Some time in March or April of 1857. - - - Lived in Amsterdam during March and April of 1857. - - - From the 1st of March to some time later in March or April of 1857. - - - From the 1st of March or sometime later to the end of April, - 1857. - - - From sometime in March of 1856 to sometime in April of 1858. - -

-

Normalization of date and time values permits the efficient processing of data (for example, to determine whether one - event precedes or follows another). These examples all use the W3C standard format for representation of dates and times. - Further examples, and discussion of some alternative approaches to normalization are given in section below.

- -
- -
- -
- Names - -
- Personal Names - -

The core rs and name elements can distinguish names in a text but are insufficiently powerful to mark - their internal components or structure. To conduct nominal record linkage or even to create an alphabetically sorted list - of personal names, it is important to distinguish between a family name, a forename and an honorary title. Similarly, when - confronted with a string such as John, by the grace of God, king of England, lord of Ireland, duke of Normandy and - Aquitaine, and count of Anjou, the analyst will often wish to distinguish amongst the various constituent elements - present, since they provide additional information about the status, occupation, or residence of the person to whom the - name belongs. The following elements are provided for these and related purposes: - - - - - - - - -

- -

In addition to the att.naming attributes mentioned above, all of the above elements are - members of the class att.personal, and thus share the following attributes: - - -

-

The persName element may be used in preference to the general name element irrespective of whether or - not the components of the personal name are also to be marked. - The - element persName is synonymous with the element name type="person", except that its type - attribute allows for further subcategorization of the personal name itself, for example as a married, - birth, pen, pseudo, or religious name. Consequently the following examples - are equivalent: That silly man David Paul Brown has suffered the furniture of his office to be seized the third time for - rent. - That silly man - David Paul Brown - has suffered ... - That silly man David Paul Brown has suffered ... - That silly man David Paul - Brown has suffered ... -

-

The persName element is more powerful than the rs and name elements because distinctive name - components occurring within it can be marked as such.

-

Many cultures distinguish between a family or inherited surname and additional personal names, often known - as given names. These should be tagged using the surname and forename elements respectively - and may occur in any order: - Roosevelt, Franklin - Delano - - - Franklin - Delano - Roosevelt - -

-

The type attribute may be used with both forename and surname elements to provide further - culture- or project-specific detail about the name component, for example: - Franklin - Delano - Roosevelt - - - Margaret - Hilda - Roberts - Thatcher - - Muhammad Ali - - Norman - St John Stevas - - Values for the type attribute are not constrained, and may be chosen as appropriate to the encoding - needs of the project. They may be used to distinguish different kinds of forename or surname, as well as to indicate the - function a name component fills within the whole. In this example, we indicate that a surname is toponymic, and also point - to the specific place name from which it is derived: - - Johan - Dystvold - - - Dystvold - -

- -

The value complex was suggested above for the not uncommon case where the whole of a surname is composed of - several other surname elements. These nested surnames may be individually tagged as well, together with appropriate type - values: - Kara - - Hattersley- Smith - - -

-

The full attribute may be used to indicate whether a name is an abbreviation, initials, or given in full: - - Maggie - Thatcher - -

- -

These elements may be applied as the encoder considers appropriate, including cases where phrases or expressions are used - to stand for surnames or forenames, as in the following: - Peter - son of Herbert gives the king 40 m. for having custody of the land and heir of - John - son of Hugh... -

- -

Similarly, patronymics may be treated as forenames, thus: ... but it remained for - Snorri - Sturluson - to combine the two traditions in cyclic form. When a patronymic is used as a surname, however (e.g. - by an individual who otherwise would have no surname, but lives in a culture which requires surnames), it may be tagged as - such: Even Finnur - Jonsson acknowledged the artificiality of the procedure... Alternatively, it may - be felt more appropriate to mark a patronymic as a distinct kind of name, neither a forename nor a surname, using the - addName element: - - Egill - Skallagrmsson - - In the following example, the type attribute is used to distinguish a patronymic from other forenames: - - Sergei - Mikhailovic - Uspensky - -

- - -

This example also demonstrates the use of the sort attribute common to all members of the model.persNamePart class; its effect is to state the sequence in which forename and surname - elements should be combined when constructing a sort key for the name.

-

Some names include generational or dynastic information, such as a number, or phrases such as Junior, or the - Elder; these qualifications may also be used to distinguish similarly named but unrelated people. In either case, - the genName element may be used to distinguish such labels from other parts of the name, as in the following - examples: - Marques - Junior, Henrique - - - Charles - II - - - Rudolf - II - von Habsburg - - - Smith - Minor - -

-

It is also often convenient to distinguish phrases (historically similar to the generational labels mentioned above) used - to link parts of a name together, such as von, of, de etc. It is often a matter of arbitrary choice - whether such components are regarded as part of the surname or not; the nameLink element is provided as a means - of making clear what the correct usage should be in a given case, as in the following examples: - Mme - de la - Rochefoucault - - - Walter - de la Mare - -

-

Finally, the addName and roleName elements are used to mark all name components other than those - already listed. The distinction between them is that a roleName encloses an associated name component such as an - aristocratic or official title which exists in some sense independently of its bearer. The distinction is not always a - clear one. As elsewhere, the type attribute may be used with either element to supply culture- or application- - specific distinctions. Some typical values for this attribute for names in the Western European tradition follow: - - An inherited or life-time title of nobility such as Lord, Viscount, - Baron, etc. - - An academic or other honorific prefixed to a name e.g. Doctor, - Professor, Mrs., etc. - - Membership of some elected or appointed organization such as President, - Governor, etc. - - Military rank such as Colonel. - - A traditional descriptive phrase or nick-name such as The Hammer, The - Great, etc. - Note, however, that the role a person has in a given context (such as witness, - defendant, etc. in a legal document) should not be encoded using the roleName element, - since this is intended to mark roles which function as part of a person's name, not the role of the person bearing the - name in general. Information about roles, occupations, etc. of a person are encoded within the person element - discussed below in .

-

Here are some further examples of the usage of these elements: - Princess - Grace - - - Grandma - Moses - - - President - Bill - Clinton - - - Colonel - Gaddafi - - - Frederick - the Great - -

-

A name may have any combination of the above elements: - Governor - Edmund - G. - Jerry - Moonbeam - Brown - Jr. -

-

Although highly flexible, these mechanisms for marking personal name components will not cater for every personal name, - nor for every processing need. Where the internal structure of personal names is highly complex or where name components - are particularly ambiguous, feature structures are recommended as the most appropriate mechanism to mark and analyze them, - as further discussed in chapter .

- -

White space is allowed and therefore significant between elements within name, persName, - orgName, and placeName. Therefore - Mary - Ann - DeMint - ]]> encodes Mary Ann DeMint and - MaryAnn - De - Mint - ]]> encodes MaryAnn De Mint. See for more information on whitespace in XML.

-
- -
- Organizational Names -

In these Guidelines, we use the term organization for any named collection of people regarded as a single unit. - Typical examples include institutions such as Harvard College or the BBC and - businesses such as Apple or Google but also racial or ethnic groupings or - political factions where these are regarded as forming a single agency such as the Scythians or - the Militant Tendency. Giving a loosely-defined group of individuals a name often serves a - particular political or social agenda and an analysis of the way such phrases are constructed and used may therefore be of - considerable importance to the social historian, even where the objective existence of an organization in this - sense is harder to demonstrate than that of (say) a named person. In the case of businesses or other formally constituted - institutions, the component parts of an organizational name may help to characterize the organization in terms of its - perceived geographical location, ownership, likely number of employees, management structure, etc.

- -

Like names of persons or places, organizational names can be marked up as referring strings or as proper names with the - rs or name elements respectively. The element orgName is provided for use where it is desired - to distinguish organizational names more explicitly. - - This element is a member of the same attribute classes as persName, as discussed above in .

-

The orgName element may be used to mark up any form of organizational name: About a year back, a question of considerable interest - was agitated in the Pennsyla. Abolition - Society This encoding is equivalent to, but more specific than, either of the following - representations: About a year back, a question of considerable interest - was agitated in the - Pennsyla. Abolition Society. - About a year back, a question of considerable interest was agitated in the - Pennsyla. Abolition Society. As shown above, like - the rs and name elements, the orgName element has a key attribute with which an - external identifier such as a database key can be assigned to the organization name, and also a ref attribute - which can be used to point directly to an org element containing information about the organization itself (see - further ). Its type attribute should be used to characterize the name (rather than the - organization), for example as an acronym: Mr Frost will be able to earn an - extra fee from BSkyB rather than the BBC - as a phrase: The feeling in - Canada is one of strong aversion to the United States Government, - and of predilection for self-government under the English Crown - - The Justified Ancients of Mu Mu - or as a composite of other kinds of name: - - Ernst & Young - -

-

The components of an organization's name may include place names as well as personal names: A spokesman from - IBM - UK - said ... or role names: THE TICKET which you will - receive herewith has been formed by the Democratic Whig party - after the most careful deliberation, with a reference to all the great objects of NATIONAL, STATE, COUNTY and - CITY concern, and with a single eye to the Welfare and Best Interests of the Community. -

-

As indicated above, organizational names may also be specified hierarchically particularly where the named organization - is itself a department or a branch of a larger organizational entity. The Department of Modern History, Glasgow - University is an example: - Department of Modern History - Glasgow - University - - -

- -

- - - - - - - - - - -

-
- -
- Place Names -

Like other proper nouns or noun phrases used as names, place names can simply be marked up with the rs element, - or with the name element. For cartographers and historical geographers, however, the component parts of a place - name provide important information about the relation between the name and some spot in space and time. They also provide - important evidence in historical linguistics.

-

These Guidelines distinguish three ways of referring to places. A place name (represented using the placeName - element) may consist of one or more names for hierarchically-organized geo-political or administrative units (see section - ). A place named simply in terms of geographical features such as mountains or rivers is - represented using the geogName element (see section ). Finally, an expression consisting - of phrases expressing spatial or other kinds of relationship between other kinds of named place may itself be regarded as - a way of referring to a place, and hence as a kind of named place (see section ). - - - -

-

As members of the att.naming class, all of these elements bear the attributes key, - ref, and nymRef mentioned above. These attributes are primarily useful as a means of linking a - place name with information about a specific place. Recommendations for the encoding of information about a place, as - distinct from its name, are provided in below.

- -

Like the persName element discussed in section , the placeName element may be - regarded simply as an abbreviation for the elements name type="place" or rs type="place". The - following encodings are thus equivalent:Strictly, a suitable value such as figurative - should be added to the two place names which are presented periphrastically in the second version of this example. This - would preserve the distinction indicated by the choice of rs rather than name to encode them in the - first version of this example. - After spending some time in our modern Babylon, New York, I have proceeded to the City of Brotherly Love. - After spending some time in our modern Babylon, New York, I have proceeded - to the City of Brotherly Love. -

-
- Geo-political Place Names -

A place name may contain text with no indication of its internal structure: Rochester, NY More usually - however, a place name of this kind will be further analysed in terms of its constitutive geo-political or administrative - units. These may be arranged in ascending sequence according to their size or administrative importance, for example: - Rochester, New York, or as a single such unit, for example Belgium. These Guidelines provide a hierarchy - of generic element names, each of which may be more exactly specified by means of a type attribute: - - - - - -

-

These elements are all members of the model.placeNamePart class, members of which may be - used anywhere that text is permitted, including within each other as in the following examples: - Rochester, New York - - - Laos, Southeast Asia - - - 6ème - Paris, - France - - -

-
-
- Geographic Names -

Places may also be named in terms of geographic features such as mountains, lakes, or rivers, independently of - geo-political units. The geogName is provided to mark up such names, as an alternative to the - placeName element discussed above. For example: Mississippi River -

-

In addition to the usual phrase level elements, the geogName element may contain the following specialized - element: - - -

-

Where the geogFeat element is used to characterize the kind of geographic feature being named, the - name element will generally also be used to mark the associated proper noun or noun phrase: - Mississippi - River - A more complex example, showing a variety of practices, follows: The isolated ridge separates two great corridors which run from Glencoe into - Glen - Etive - , the - Lairig - Gartain - and the - Lairig - Eilde -

-

The Gaelic word lairig may be glossed as sloping hill face. The most efficient - way of including this information in the above encoding would be to create a separate nym element for this - component of the name and then point to it using the nymRef attribute, as further discussed in .

-
-
- Relative Place Names - -

All the place name specifications so far discussed are absolute, in the sense that they - define only one place. A place may however be specified in terms of its relationship to another place, for example 10 - miles northeast of Paris or near the top of Mount Sinai. These relative place names will - contain a place name which acts as a referent (e.g. Paris and Mount Sinai). They will also contain a word - or phrase indicating the position of the place being named in relation to the referent (e.g. the top of, north - of). A distance, possibly only vaguely specified, between the referent place and the place being indicated may - also be present (e.g. 10 miles, near).

-

Relative place names may be encoded using the following elements in combination with either a placeName or a - geogName element. - - - Some examples of relative place names are: - near the top of - - Mount - Sinai - - - - 20 km - north of - Paris - If desired, the distance specified may be normalized using the unit and - quantity attributes of measure: - 11 miles - Northwest of - Providence, RI - -

-

The internal structure of place names is like that of personal names—complex and subject to an enormous amount of - variation across time and different cultures. The recommendations in this section should however be adequate for a - majority of users and applications; they may be extended using the mechanisms described in chapter - to add new elements to the existing classes. When the focus of interest is on the name components themselves, as in - place name studies for example, the elements discussed in may also be of use. Alternatively, the - meaning structure itself may be represented using feature structures ().

-

- - - - - - - - - - - -

-
- - -
- -
- Event Names - -

The eventName element is provided in parallel to - other naming mechanisms; it is intended especially for - canonical names that are used in texts to - mention specific named events, whether real or fictional. - -

On Monday, she was writing about the - 1618 Defenestration of Prague which initiated the - long war.

- -

-

-

There are two major applications of eventName: - - to indicate names of events mentioned in transcribed text, such as in the above example; and - to indicate the names of events for which details are being provided in an event element. - -

-

For the first application, as with most other naming - elements, the eventName element is a member of the - att.canonical class, and thus the - ref (or key) attribute may be used to - refer to a an event element (about which see ) or some other data item that contains - further information about the event.

-

When used as a direct child of event, an - eventName provides one of the names of the event about - which details are being provided in its parent event. A - single event may be known by many names. All, only one, or - indeed none of these might be provided in the event used - to provide information about such an event. If more than one - eventName is used they may be differentiated by use of - type, where, or dating attributes. In cases - where multiple event elements describe events that have - the same name, the xml:id attribute of the - event or an idno, head, or - label sibling of the eventName may be used for - disambiguation and identification. Typically xml:id - or idno would be used for machine-processable - disambiguation, and either head or label for - human readers.

-

- - - -

-
- -
- Object Names - -

- -

- -

As with other proper nouns or noun phrases used as names, the names of objects may be marked up simply with the - name element. For those working with a variety of named objects the objectName element provides more - flexibility. -

The Minster Lovell Jewel is probably the most similar to the - Alfred Jewel and was found in Minster - Lovell in Oxfordshire and is kept at the Ashmolean Museum.

- -

-

The objectName element may be used to encode any named object whether or not this is a text-bearing object. The - use of objectName by itself does not categorize the object referenced, but this may be done further with the - type and subtype attributes or through reference to a taxonomy. Additionally, the use of - the objectName element says nothing about the physical reality of the object – that is whether it is real, - fictional, purported, or missing – and this may be one aspect that some may wish to record through the type - attribute. Where more detailed information is available for a named object the ref attribute should be used to - point to an object element or other source of information about this object. The objectName element is - intended for named objects; where an object is mentioned through a descriptive phrase but not named explicitly the - rs element should be used.

-
- -
- -
- Biographical and Prosopographical Data -

This module defines a number of special purpose elements which can be used to markup biographical, historical, and - prosopographical data. We envisage a number of users and uses for these elements. For example, an encoder may be interested - in creating or converting a set of biographical records of the type found in a Dictionary of National - Biography. Another use is the creation or conversion of a database-like collection of information about a group of people, - such as the people referenced in a marked-up collection of documents, or persons who have served as informants in the - creation of spoken corpora. It is also appropriate to use these elements to register information relating to those who have - taken part in the creation of a TEI document.

- -

To cater for this diversity, these Guidelines propose a flexible strategy, in which encoders may choose for themselves the - approach appropriate to their needs. If one were interested, for example, in converting existing DNB-type records, and - wanted to preserve the text as is, the person element (see ) could simply contain the text - of an article, placed within p elements, possibly using elements such as name or date to mark up - features of that text. For a more structured entry, however, one would extract the data and place information contained in - the text, and encode it directly using the more specific elements described in this section.

-
- Basic Principles -

Information about people, places, organizations, and events, of whatever type, essentially comprises a series of statements or - assertions relating to: - characteristics or traits which do not, by and large, change over time - characteristics or states which hold true only at a specific time - events or incidents which may lead to a change of state or, less frequently, trait, - external resources where other information on the subject can be found. - -

- -

Characteristics or traits are typically independent of an individual's volition - or action and can be either physical, such as hair and eye colour; or cultural, such as ethnicity and caste. - The distinction is not entirely straightforward: gender and sex can be regarded as culturally determined with physical manifestations, - interpreted based on the social hierarchies of a time and place. Also the division of humanity into different races, - formalized in the nineteenth century to organize a hierarchy of humanity on the basis of physical characteristics such as skin colour, hair type, - and skull measurements, is now recognized as a colonialist social construct.For example, see Renato G. Mazzolini's historical survey - of European empires and their unstable constructions of race. - When such a construct defined individuals' identities beyond their volition, the markup and documentation should reflect - this as a culturally-determined characteristic.

- -

States include, for example, marital status, place of residence, and position or occupation. Such - states have a definite duration, that is, they have a beginning and an end and are typically a consequence of the - individual's own action or that of others.

- -

Changes in state refer to life-changing or identity-changing events such as birth, marriage, or appointment - to office; such events will normally be associated with a specific date or a fairly narrow date-range. Changes in states - can also cause or be caused by changes in characteristics. Any statement or assertion about these aspects of a - person's life will be based on some source, possibly multiple sources, possibly contradictory. Taking all this into - account it follows that each such statement or assertion needs to be documentable, put into a time frame, and be - relatable to other statements or assertions.

- -

The elements defined by the module described in this chapter may, for the most part, all be regarded as specializations - of one or other of the above three classes. Generic elements for state, trait, and event are also defined: - - - - - - - -

- -

When developing a prosopography record of a named entity it is a common practice to refer explicitly to other resources, for example the Library of Congress Name Authority File, Virtual Internationl Authority File (VIAF), a gazetteer of places like Pleiades, or a printed book. - - - -

-

Here is a simple example: - - Rome - - 41.891775, 12.486137 - - 423025 - capital of the Roman Empire - -

-
-
- The Person Element -

Information about a person, as distinct from references to a person, for example by name, is grouped together within a - person element. Information about a group of people regarded as a single entity (for example the - audience of a performance) may be encoded using the personGrp element. Note however that information - about a group of people with a distinct identity (for example a named theatrical troupe) should be recorded using the - org element described in section below.

-

These elements may appear only within a listPerson element, which groups such descriptions together, and - optionally also describes relationships amongst the people listed. - - - -

- -

One or more listPerson elements may be supplied - within the standOff element (see ) or, when used to list the participants in - a linguistic interaction, within the particDesc - (participant description) element in the profileDesc - element of a TEI header. Like other forms of list, however, - listPerson can also appear within the body of a text - when the module defined by this chapter is included in a - schema.

- -

The type attribute may be used to distinguish lists of people of different kinds where this is considered - convenient: - - - - - Adam Schiff - District Attorney for Manhattan in - seasons 1 to 10 of Law and Order. - - - Mike Logan - NYPDNew York Police - Department Detective regularly appearing in - seasons 1 to 5 of Law and Order and seasons 5 to 7 - of Law and Order: Criminal Intent. - - - Benjamin Stone - Executive Assistant District Attorney for - Manhattan in seasons 1 to 4 of Law - and Order - - - Jack McCoy - An Executive Assistant District Attorney then District - Attorney for Manhattan in seasons 5 to 10 - of Law and Order, in seasons 1, 9, 11, and 19 of - Law and Order: Special Victims Unit, and in - season 1 of Law and Order: Trial by Jury. - - - Jamie Ross - An Assistant District Attorney for - Manhattan in seasons 7 & 8 of - Law and Order, and a defense attorney in seasons - 10 & 11, and then a judge in Law and Order: Trial by - Jury. - - - Joe Fontana - NYPDNew York Police - Department Detective regularly appearing - in seasons 15 & 16 of Law and Order. - - - - - - Adam Schiff - U.S. Representative from California since 2013. - - - Mike Logan - Gridiron football player for the Pittsburgh Steelers from - 2001 to 2006. - - - Benjamin Stone - Michigan State Senator from 1968 to 1979. - - - Jack McCoy - Iowa State Representative from 1955 to 1959. - - - Jamie Ross - Broadway actor, with occasional forays into television, - from 1971 to roughly 2007. - - - Joe Fontana - A member of Canada’s House of Commons from 1987 to 2006, - and mayor of London, Ontario from 2010 to 2014. - - - - -

- -

The person element carries several attributes. As a member of the classes att.global.responsibility, att.editLike, and att.global.source class, it carries the usual attributes for providing details about the information recorded - for that person, such as its reliability or source: - - - - In addition, a small number of very commonly used personal properties may be recorded using attributes - specific to person and personGrp: - - -

- -

These attributes are intended for use where only a small amount of data is to be encoded in a more or less normalized - form, possibly for many person elements, for example when encoding basic facts about respondents to a questionnaire. When - however a more detailed encoding is required for all kinds of information about a person, for example in a historical - gazetteer, then it will be more appropriate to use the elements age, sex and others described elsewhere - in this chapter.

- -

Note that the age attribute is not intended to record the person's age expressed in years, months, or other - temporal unit. Rather it is intended to record into which age bracket, for the purposes of some analysis, the person - falls. A simple (perhaps too simple to be useful) binary classification of age brackets would be child and - adult. The actual age brackets useful to various projects are likely to be varied and idiosyncratic, and thus - these Guidelines make no particular recommendation as to possible values. Instead, individual projects are recommended to - define the values they use in their own customization file, using a declaration like the following: - - - - - - - - - less than 18 years of age - - - 18 to 65 years of age - - - over 65 years of age - - - - - - The above declaration, were it properly placed in a customization file, establishes that the age - attribute of person has only three possible values, child, adult, and retired. - For more information on customization see .

- -

The person element may contain many sub-elements, each specifying a different property of the person being - described. The remainder of this section describes these more specific elements. For convenience, these elements are - grouped into three classes, corresponding with the tripartite division outlined above: one for traits, one for states and - one for events. Each class may contain specific elements for common types of biographical information, and contains a - generic element for other, user-defined, types of information.

-

All the elements in these three classes belong to the attribute class att.datable, which - provides the following attributes: - - as discussed in above.

- -
- Personal Characteristics -

The model.persStateLike class contains elements describing physical or socially-constructed - characteristics, traits, or states of a person. Members of the class comprise the following specific elements: - - - - - - - - - - - - - - - - - - - All, apart from langKnowledge and persona, allow content of ordinary prose containing - phrase-level elements. - Status AB1 in the RG Classification scheme - - -

-

Encoders should take particular care to be explicit about culturally determined concepts such as nationality, ethnicity, age, - or sex/gender system that influence their markup.Following Gayle Rubin’s influential theory, - Every society also has a sex/gender system—a set of arrangements by which the biological raw material - of human sex and procreation is shaped by human, social intervention and satisfied in a conventional manner, - no matter how bizarre some of the conventions may be.. For example, when recording - personal age in different cultures, there may be different assumptions about the point from which age is reckoned. - Scholars face similar issues when marking sex and gender according to cultural systems from times and places not their own. - A statement of the practice adopted in a given encoding may usefully be provided in the editorialDecl element - discussed in .

- -

The langKnowledge element contains either paragraphs or a number of langKnown elements; it may take a - tags attribute, which provides one or more standard codes or tags for the languages. - The langKnown element must have a tag attribute, which indicates the language with the same kind of - language tag. These language tags are discussed in detail in .

-

Furthermore, the langKnown element also has a level attribute to indicate the level of the person's - competence in the language. It is thus possible either to say: -

Speaks fluent Fulani, Wolof, and French. Some knowledge of - English.

- or - - Fulani - Wolof - French - English - - -

-

The persona element may contain the same component elements as a person element. Its function is to - document a distinct persona assumed by the person element containing it. A person, not necessarily fictional, - may take on different personas at different times or in different situations, each persona having different personal - characteristics, such as name, age, sex, gender etc. We distinguish a persona, which is a set of characteristics associated with - one specific individual, from a role, which is a set of characteristics that many different people can assume. An actor - does not change their persona when adopting a different role, but none of the personas associated with one person can - properly be associated with another.

- -

The persPronouns element may be used to indicate - the personal pronouns used, or assumed to be used, by the - individual being described. It is common practice in email - signatures and biographies, for people to include their - preferred personal pronouns along with their name or handle. - This allows transgender and gender variant people to express - how they wish to be identified, without having to share - their gender identity (though some do). Cisgender people - have also adopted the practice, which normalizes the idea - that a person's personal pronouns should not be inferred by - their name, sex, gender, or gender presentation. The - persPronouns element may be used either in - transcribed content to encode a phrase used to indicate - preferred personal pronouns, or may be used inside a - person or persona element to indicate - the associated pronouns.

- -

For example, the following entry from a hypothetical - prosopography lists only the nominative case of the - preferred pronouns as identified by Miss Major - Griffin-Gracy, a historical figure. - - - - - - Miss Major - Griffin-Gracy - - - trans woman - - -

Veteran of the Stonewall Riots. Founder of the - Griffin-Gracy Educational Retreat and Historical - Center (the House of GG). Activist and advocate for - transgender and gender-nonconforming people of - color.

- - - -

-

Personal pronouns often occur as part of the closer of an - email, post, or other electronic communication. - - -

- Dear all, -

With apologies for length. I'm expanding a schema …

- - - Diane Jakacki, Ph.D. - Digital Scholarship Coordinator - Affiliate Faculty in Comparative & Digital Humanities - Bucknell University - d…@….edu - (she/her/hers) - - Principal Investigator, - LAB Cooperative and REED London Online - Chair, ADHO Conference Coordinating Committee - -
-

-

The sex and gender elements each carry a value attribute to give values from a project-internal taxonomy, or an - external standard. - female - woman - As elsewhere, these coded values may be used as an alternative to or normalization of the actual descriptive - text contained in the element. The previous example might equally well be given as - - - -

-

The generic trait and state elements are also members of this class, - - - These elements can be used to extend the range of information supplied about an individual's personal - characteristics. Either may contain an optional label element, used to provide a human-readable specification - for the characteristic concerned and a description of the feature itself supplied within a desc element. These - may be followed by or one or more p elements supplying more detailed information about the trait. In either - case, these may be followed by one or more notes or bibliographical references. The type, ref, and - key attributes may be used to indicate a fuller definition of the combination of feature and value. - - - Ethnic Albanian. - - -

- - - -

These elements are provided as a simple means of extending the set of descriptive features available in a standardized - way. For example, there are no predefined elements for such features as eye or hair colour. If these are to be recorded, - they may simply be added as new types of trait: - - - blue - - - - brown - - -

- -

If none of the more specialized elements listed above is appropriate, then a choice must be made between the two - generic elements trait and state. If you wish to distinguish between characteristics that are - generally perceived to be transient and those which are generally considered unchanging, use state for the - former, and trait for the latter. It may also be helpful to note that traits are typically, but not - necessarily, independent of the volition or action of the holder. If the distinction between state and trait is not - considered relevant or useful, use state.

- -

The persName element is repeatable and can, like all TEI elements, take the attribute xml:lang to - indicate the language of the content of the element, as well as a type attribute to indicate the type of - name, whether a nickname, maiden or birth name, alternative form, etc. This is useful in cases where, for example, a - person is known by a Latin name and also by any number of vernacular names, many or all of which may have claims to - authenticity. In order to ensure uniformity, the method generally employed in the library world - has been to accept the form found in some authority file, for example that of the American Library of Congress, as the - base or neutral form. Feelings can run high on this matter, however, and - people are often reluctant to accept as neutral an overtly foreign form of the name of their local - saint or hero. Within the person element any number of variant forms of a name can be given, with no - prioritization, and hence less likelihood of offence. The Icelandic scholar and manuscript collector Árni Magnússon, to - give his name in standard modern Icelandic spelling, is known in Danish as Arne Magnusson, the form which he himself, as - a long term resident of Denmark, generally used; there is also a Latinized form, Arnas Magnæus, which he used in his - scholarly writings. All three forms can be given, and in any order: - - Árni Magnússon - Arne Magnusson - Arnas Magnæus - - -

-

At the other extreme, a person may be named periphrastically as in the following example: - - Simon, son of Richard - Essex - 1219-1223 - - -

- -

Alternatively, the generic name element may be used for all of the naming components in a description. For - example, a description of the first living held by the Icelandic clergyman and poet Jón Oddsson Hjaltalín might be - tagged as follows: -

Jón's first living — which he apparently accepted rather reluctantly — was at Háls í - Hamarsfirði, Múlasýsla, to which he was presented on 7 April 1777. He was - ordained the following month and spent three years at Háls, but was never happy there, due largely to the general - penury in which he was forced to live — a recurrent theme throughout the early part of his life. In June of 1780 - the bishop recommended that Jón should promoveres til andet bedre kald, end det hand hidindtil - har havt, and on 12 July it was agreed that he should exchange livings with sr. Þórður Jónsson at Kálfafell á Síðu, - Skaftafellssýsla.

ÞÍ, Stms I.15, p. 733. ÞÍ, Stms I.17, p. - 102. - -

- -

Similarly, the generic state or trait element may be used in preference to the more specific elements - listed above: - - - American citizen from 15 January 2002. - - is the same as: - American citizen from 15 January 2002. - or even: - - -

- -
-
- Personal Events -

This section describes events that relate to one or more persons, while the section on - Events below describes the use of event in more general terms.

-

Events in a person's history are not characteristics of an individual, but often cause an individual to gain such - characteristics, or to enter a new state. Most such events, for example marriage, appointment, promotion, or a journey - may be recorded using the generic element event, which may be grouped with listEvent, and has a - content model similar to that of state and trait. The chief difference is that event can - include a placeName element to identify the name of the place where the event occurred.

-

Two particular events in a person's life, namely birth and death, are both ubiquitous and usually considered - particularly important, and thus may be represented by specialized elements for the purpose: - - - -

-

In the following example, we give a brief summary of the wedding of Jane Burden to the English writer, designer, and - socialist William Morris, encoded as an event element embedded within the person element used to - record data about Morris, though we could equally well have embedded the event element within the - person element for Burden, or have encoded it independently of either person element: - - - - - William Morris and Jane Burden were married at St - Michael's Church, Ship Street, Oxford on 26 April 1859. The wedding was - conducted by Morris's friend R. W. Dixon with Charles Faulkner as the best man. The bride was given away by her father, Robert Burden. According to the account that Burne-Jones gave Mackail - M. said to Dixon beforehand Mind you don't call her Mary but he did. The entry in - the Register reads: William Morris, 25, Bachelor Gentleman, 13 George Street, son of William Morris decd. - Gentleman. Jane Burden, minor, spinster, 65 Holywell Street, d. of Robert Burden, Groom. The witnesses - were Jane's parents and Faulkner. None of Morris's family attended the ceremony. Morris presented Jane with a - plain gold ring bearing the London hallmark for 1858. She gave her husband a double-handled antique silver - cup. - J. W. Mackail, The Life of William Morris, 1899. - - - - Robert Burden - - - R.W. Dixon - - - Charles Faulkner - - - - Edward - Burne-Jones - - - - J.W. Mackail - - In this example the ref attributes on the various name elements point either to an external - source or to a person element within which other information about the person named may be found. As further - discussed below (), a relation element may then be used to link them in a more - meaningful way: - - - - -

-

As mentioned above, all these elements, both the specific and the generic, are members of the att.datable attribute class, which means they can be limited in terms of time. The following encoding, for - example, demonstrates that the person named David Jones changed his name in 1966 to David Bowie: - - David Jones - David Bowie - - -

-

All the generic elements are also members of the att.global.responsibility and att.editLike classes. These classes make available the attributes cert, to indicate - the degree of certainty, resp, the agency responsible, evidence, the nature of the evidence used, - and source, a pointer to a resource from which the information derives. In this way it is possible, in the - case of multiple and conflicting sources, to provide more than one view of what happened, as in the following example: - -

Born in Brixton on 8 January - 1947.

-

Born in Berkhamsted on 9 January - 1947.

 - -

-
-
- Personal Relationships - -

When the module defined by this chapter is included in a schema, the following two elements may be used to document - relationships amongst the persons, places, or organizations identified: - - - These elements are both members of the att.typed class, from which they inherit - the type and subtype attributes in the usual way. The value specified for either attribute on a - listRelation element is implicitly applicable to all of its child relation elements, unless - overridden.

-

A relationship, as defined here, may be any kind of describable link between specified participants. A - participant (in this sense) might be a person, a place, or an organization. In the case of persons, therefore, a - relationship might be a social relationship (such as employer/employee), a personal relationship (such as sibling, - spouse, etc.) or something less precise such as possessing shared knowledge. A relationship may be - mutual, in that all the participants engage in it on an equal footing (for example the sibling - relationship); or it may not be if participants are not identical with respect to their role in the relationship (for - example, the employer relationship). For non-mutual relationships, only two kinds of role are currently - supported; they are named active and passive. These names are chosen to reflect the fact that - non-mutual relations are directed, in the sense that they are most readily described by a transitive verb, - or a verb phrase of the form is X of or is X to. The subject of the verb - is classed as active; the direct object of the verb, or the object of the concluding preposition, as - passive. Thus parents are active and children passive in the relationship parent - (interpreted as is parent of); the employer is active, the employee passive, in the - relationship employs. These relationships can be inverted: parents are passive and - children active in the relationship is child of; similarly works for inverts the - active and passive roles of employs.

-

For example: - - - - This example defines the relationships amongst a number of people not further described here; - we assume however that each person has been allocated an identifier such as P1, P2, etc. which can - be linked to using references such as #P1, #P2, etc. Then the above set of relation - elements describe the following three relationships amongst the people referenced: - P1 and P2 are parents of P3 and P4. - P1 and P2 are linked in a mutual relationship called spouse—that is, P2 is the spouse of P1, and P1 is - the spouse of P2. - P1 has the social relationship employer with respect to P3 and P4. -

-

Relationships within places and organizations are further discussed in the relevant sections below. Relationships - between for example organizations and places, or places and persons, may be handled in exactly the same way. - -

-
-
- -
- Organizational Data -

The org and listOrg elements are used to store data about an organization such as its preferred name, - its locations, or key persons within it. - - - These elements are intended to be used in a way analogous to the place and person elements - discussed elsewhere in this chapter, that is to provide a unique wrapper element for information about an entity, distinct - from references to that entity which are typically encoded using a naming element such as name type="org" or - orgName. The content of a naming element will represent the way an organization is named in a given context; - the content of an org represents the information known to the encoder about that organization, gathered together - in a single place, and independent of its textual realization.

-

An organization is not the same thing as a list or group of people because it has an identity of its own. That identity - may be expressed solely in the existence of a name (for example The Scythians), but is likely to consist in the - combination of that name with a number of events, traits, or states which are considered to apply to the organization - itself, rather than any of its members. For example, a sports team might be described in terms of its membership (a - listPerson), its fixtures (a listPlace), its geographical affiliation (a placeName), or any - combination of these. It will also have properties which may be used to categorize it in some way such as the kind of - sport played, whether the team is amateur or professional, and so on: these are probably best dealt with by means of the - type attribute. However, it is the name of the sports team alone which identifies it.

-

The content model for org permits any mixture of generic state, trait, or event - elements: the presence of the orgName element described in is however strongly - recommended.

-

In other respects, the org element is used in much the same way as place or person. An - organization may have different names at different times: - The Silver Beetles - The Beatles - -

-

The names of the people making up an organization can also change over time, (if they are known at all). For example: - - The Silver Beetles - The Beatles - - - John Lennon - Paul McCartney - George Harrison - Stuart Sutcliffe - Pete Best - - - - - John Lennon - Paul McCartney - George Harrison - Ringo Starr - - - -

-

An org may contain subordinate orgs: - Oxford University Computing Services - - Information and Support Group - - - Infrastructure Group - - Networking Team - - - System Development Team - - - - Learning Technologies Group - - - -

-

The following example demonstrates the use of the listOrg element to group together a number of org - elements, each of which is defined solely by means of an informal description, itself containing other names. -

The TEI institutional hosts are: - - Brown University - The host contribution is made jointly by the Brown University Women Writers - Project and the Brown University Library's Center for Digital Initiatives. - - - Nancy - Hosting is provided by a group of institutions located in Nancy, France, coordinated by - Loria and also including ATILF and INIST. - - - Oxford University - Hosting is provided by the Research Technologies Service at Oxford University - Computing Services. - - - University of Virginia - Virginia's host support comes jointly from the Institute for Advanced Technology in the - Humanities and the University of Virginia Library. - - -

In a more elaborated version of this example, the organizational names tagged using orgName might - be linked using the key or ref attribute to a unique org element elsewhere.

-
- -
- Places - -

In we discuss various ways of naming places such as towns, countries, etc. In much the same way - as these Guidelines distinguish between the encoding of names for people and the encoding of other data about people, so - they also distinguish between the encoding of names for places and the encoding of other data about places. In this - section we present elements which may be used to record in a structured way data about places of any kind which might be - named or referenced within a text. Such data may be useful as a way of normalizing or standardizing references to - particular places, as the raw material for a gazetteer or similar reference document associated with a particular text or - set of texts, or in conjunction with any form of geographical information system.

-

The following elements are provided for this purpose: - - - -

- -

The model.placeStateLike class contains elements describing characteristics of a place which - have a definite duration, such as its name. Any member of the model.placeNamePart may be used - for this purpose, since a place element will usually contain at least one, and possibly several, - placeName-like elements indicating the names associated with it, by different people, in different languages, - or at different times.

- -

For example, the modern city of Lyon in France was in Roman times known as Lugdunum. Although the modern and the Roman - city are not physically co-extensive, they have significant areas which overlap, and we may therefore wish to regard them - as the same place, while supplying both names with an indication of the time period during which each was current.

- -

Places usually have physical locations in addition to names. As with the example of Lyon, the precise - geographic location and extent of a place may change over time, and so locations like names may need to be - qualified with indications of the time period to which they apply. Locations may be - specified in a number of ways: as a set of coordinates defining a point or an area on the - surface of the earth, or by providing a description of how the place may be found, usually - in terms of other place names. For example, we can identify the location of the Canadian - city of London, either by specifying its latitude and longitude, or by specifying that we - mean the city called London located in the province called Ontario within the country called - Canada.

- -

In addition we may wish to supply a brief characterization of the place identified, for example to state that it is a - city, an administrative area such as a country, or a landmark of some kind such as a monument or a battlefield. If our - typology of places is simple, the open ended type attribute is the easiest way to represent it: so we might say - place type="city", place type="battlefield" etc.

- - -

Within the place element, the following elements may be used to provide more information about specific aspects - of the place in a structured form: - - - -

-
- Varieties of Location -

A location may be specified in one or more of the following ways: - by supplying a string representing its coordinates in some standardized way within a geo element, as - shown below - by supplying one or more place name component elements (e.g. country, settlement etc.) to - place it within a geo-political context - by supplying a postal address, e.g. using the address element - by supplying a brief textual description, e.g. using the desc element - by using a non-TEI XML vocabulary such as the Geography Markup Language - We give examples of all of these methods in the remainder of this section.

- -

The simplest method of specifying a location is by means of its geographic coordinates, supplied within the - geo element. This may be used to supply any kind of positional information, using one of the many different - geodetic systems available. Such systems vary in their format, in their scope or coverage, and more fundamentally in the - reference frame (the datum) used for the coordinate system itself. The default recommended by these - Guidelines is to supply a string containing two real numbers separated by whitespace, of which the first indicates - latitude and the second longitude according to the 1984 World Geodetic System (WGS84); this is the system currently used - by most GPS applications which TEI users are likely to encounter.See . The most recent revision of this standard is known as - the Earth Gravity Model 1996.We might therefore record the information about the place known as - Lyon as follows: - - Lyon - Lugdunum - 45.769559 4.834843 - - -

- -

Identifying Lyon by its geo-political status as a settlement within a country forming part of a larger political - entity, we might represent the same place as follows: - - Lyon - Lugdunum - - EU - France - - - Elements such as bloc are specialized forms of placeName, as discussed in .

-

We may use the same procedure to represent the location of smaller places, such as a street or even an individual - building: - Brasserie Georges - - - Lyon - IIème - Perrache - 30, Cours de Verdun - - Note the use of the type attribute to categorize more precisely both the kind of place - concerned (a building) and the kind of name used to locate it, for example by characterizing the generic - district as an arrondissement, or a quartier.

- -

We may also treat imaginary places in the same way: - Atlantis - - beyond - The Pillars of Hercules - -

- -

A location sometimes resembles a set of instructions for finding a place: - Yasgur's Farm - Woodstock Festival Site - - one mile - north west of - Bethel - New York - - -

-

The element address may also be used to identify a location in terms of its postal or other address: - Protestant Cemetery - Cimitero Acattolico - - Italy - Rome - Testaccio - - -

- Via Caio Cestio, 6 - 00153 Roma -
- - When, as here, the same place is given multiple locations, the type attribute should be - used to characterize the kind of location, as a means of indicating that these are alternative ways of identifying the - same place, rather than that the place is spread across several locations.

- -

The location element may thus identify a place to a greater or lesser degree of precision, using a variety of - means: a name, a set of names, or a set of coordinates. The geo element introduced earlier is by default - understood to supply a value expressed in a specific (and widely used) notation. If a location contains more - than one geo, this is interpreted as being really the same place in the universe, but with different systems - used to refer to it. If there is a lack of consensus about the location (of, for example, Camelot), more than one - location should be used, each with its own geo.

- -

By default, the content of geo is interpreted as following the standard known as the World Geodetic System - (WGS). This may be modified, however, in two ways.

-

Firstly, the content of the geo element can be expressed some other way, that is, according to some different - geodetic system. The decls attribute is used point to a geoDecl element defined in the document - header, which describes a different datum.

-

Secondly, the element geo may be redefined to contain markup from a different XML vocabulary which is - specifically designed to represent this kind of information. This technique is used throughout these Guidelines where - specialized markup is required, for example to embed mathematical expressions or vector graphics, and is further - described and exemplified in . For geographic information, suitable non-TEI vocabularies include: - - the OpenGIS Geography Markup Language (GML) being defined by the OGCThe OGC is an - international voluntary consensus standards organization whose members maintain the Geography Markup Language - standard. The OGC coordinates with the ISO TC 211 standards organization to maintain consistency between OGC and - ISO standards work. GML is also an ISO standard (ISO 19136:2007). - - the Keyhole Markup Language (KML) used by Google MapsSee - - -

-

In the following example, we have defined the location of the place Lyon using GML and indicated - the two names associated with it at different times: - - Lyon - Lugdunum - - - - - 45.256 -110.45 46.46 -109.48 43.84 -109.86 45.8 -109.2 45.256 -110.45 - - - - - -

- -

A bibl element may be used within location to indicate the source of the location information.

- - - 53.226658 -0.541254 - Roman Inscriptions of Britain, 262 - - - -
-
- Multiple Places -

A place may contain other places. This containment relation can be directly modelled in XML: thus we can say that the - towns of Vilnius and Kaunas are both in a place called Lithuania (or Lietuva) as follows: - Lithuania - Lietuva - - Vilnius - - - Kaunas - - -

-

This does not, of course, imply that Vilnius and Kaunas are the only places constituting Lithuania; only that they are - within it. A separate place element may indicate that it is a part of Lithuania by supplying a - relation element, as discussed below ().

- -

As a further example, the islands of Mauritius, Réunion, and Rodrigues are collectively known as the Mascarene Islands. - Grouped together with Mauritius there are also several smaller offshore islands, with rather picturesque French names. - These offshore islands do not however constitute an identifiable place as a whole. One way of representing this is as - follows: - Mascarene Islands - Mascarenhas Archipelago - - Mauritius - - - La roche qui pleure - - - Île aux cerfs - - - - - Rodrigues - - - Réunion - - -

-

Here is a more complex example, showing the variety of names associated at different times and in different languages - with a set of hierarchically grouped places—the settlement of Carmarthen Castle, within the town of Carmarthen, within - the administrative county of Carmarthenshire, Wales. - - Cymru - Wales - Wallie - Wallia - Le Waleis - - Carmarthenshire - - Carmarthen - Kaermerdin - Caerfyrddin - - castle of Carmarthen - - - - - -

-

As noted previously, country, region, and settlement are all specializations of the generic - placeName element; they are not specializations of the place element. If it is desired to - distinguish amongst kinds of place this can only be done by means of the type attribute as in - the above example.

- -

This use of multiple place elements should be distinguished from the (possibly simpler) case where a number of - places with some property in common are being grouped together for convenience, for example, in a gazetteer. The - listPlace element is provided as a means of grouping places together where there is no implication that the - grouped elements constitute a distinct place. For example: - Herefordshire - - - Abbey Dore - - 51.969604 -2.893146 - - - - Acton Beauchamp - - - - - - Hereford - - - Leominster - - - - -

-
-
- States, Traits, and Events - -

There are many different kinds of information which it might be considered useful to record for a place in addition to - its name and location, and the categories selected are likely to be very project-specific. As with persons therefore - these Guidelines make no claim to comprehensiveness in this context. Instead, the generic state, - trait, and event elements defined by this module should be used. Each of these may be customized for - particular needs by means of their type attribute. These are complemented by a small number of predefined - elements of general utility: - - - - -

- -

These are all specializations of the generic trait element. This element may be used for almost any kind of - event in the life of a place; no specialized version of this element is proposed, nor do we attempt to enumerate the - possible values which might be appropriate for the type attribute on any of these generic elements.

-

Here is an example, showing how the specific and generic elements may be combined: - - Iceland - Ísland - 65.00 -18.00 - - Area: 103,000 sq km - - -

Constitutional republic

- - -

Part of the kingdom of Denmark

- - - Iceland became independent on 17 June 1944. - - -

An independent republic since June 1944

- - -

- -

In the following example, the climate example is used to provided a detailed discussion of this particular - aspect of the information available about a particular place: - - Greece - - Greece's climate is divided into three well defined classes: - - - It features mild, wet winters and hot, dry summers. Temperatures rarely reach extremes, although snowfalls - do occur occasionally even in Athens, Cyclades or - Crete during the winter. - - - - It is found primarily in Western Greece - (Epirus, Central Greece, - Thessaly, Western Macedonia as well as - central parts of Peloponnesus like Achaea, - Arcadia and parts of Laconia where the Alpine range pass - by) - - - - It is found in Central and Eastern Macedonia as - well as in Thrace at places like Komotini, - Xanthi and northern Evros. It features cold, - damp winters and hot, dry summers. - - - - - -

-

As the above example shows, state and trait elements, and others of the same class, can be nested - hierarchically within each other. When this is done, values for the type attribute are to be understood as - cumulatively inherited, as elsewhere in the TEI scheme (for example on category or linkGrp). In the - following example, the outermost population element concerns the squirrel population between the dates given. - This is then broken down into red and gray squirrel populations, and within that into male and female: - - - 12 - 15 - - - 23 - 45 - - - The dating and responsibility attributes here behave slightly differently from the type attribute: - responsibility is not an additive property, and therefore an element either states it explicitly, or inherits it from - its nearest ancestor. Dating is slightly different again, in that a child element may specify a date more precisely than - its parent, as in the example above.

- -

An event may be related to other named entities, and thus may appear within - an org, person, personGrp, persona, or place - element as well as within a listEvent or another event.

- -
- -
- Relations Between Places - -

The relation element may also be used to express relationships of various kinds between places, or between - places and persons, in much the same way as it is used to express relationships between persons alone. Returning to the - Mascarene Islands example cited above, we might define the island group and its constituents separately, but indicate - the relationship by means of a relation element: - - - Mascarene islands - Mascarenhas Archipelago - - - Mauritius - - - - Rodrigues - - - Réunion - - - - -

- -

This stand-off style of representation has the advantage that we can now also represent the fact - that a place may be a part of more than one other place; for example, Réunion is part of France, as well as part - of the Mascarenes. If we add a declaration for France to the list above: - - France - - we can now model this dual allegiance by means of a relation element: - - -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-
- -
- Events -

- - - - - An event is a change of state whether real, planned, fictional, or purported about which more - information is known. The eventName element may be used to encode the proper name of an event, if known. The head or label element may also appear in event, either in lieu of or in addition to the eventName element, to provide a human-readable heading or editorially supplied label for the event.

-

These guidelines do not prescribe what encoders count as events, nor their granularity, - nesting, or amount of other information to record in relation to each event. Yet most events can be identified by their time, location, or agents involved (be they organizations, persons, or objects).

-

An event element may be used to record information about a place, person, or organization related to the described event; for this reason the element - may appear as content of a place, person, or org. However, it is also possible to describe events - independently of either a place, person, or organization. This may be useful not only for encoding texts which describe named events and - their eventNames, but also in applications as chronologies or lists of significant events (e.g., important battles, legislative milestones, or the stages of construction of a large building, etc.).

- -

The listEvent element is a member of the model.listLike class, and may therefore - appear inside standOff, or wherever else lists are - permitted, in the same way as the listPerson, - listPlace, listOrg etc. elements described elsewhere in this - chapter.

- - - - - - - France ceded to Great Britain its claims to the Hudson's Bay Company territories in - Rupert's Land, Newfoundland, and Acadia and - recognized British suzerainty over the Iroquois but retained its other pre-war - North American possessions, including - Île-Saint-Jean - (now Prince Edward Island)... - - - - This act of the British Parliament guaranteed free practice of the Catholic faith and restored use of the - French Civil Code for private matters throughout the Province of Quebec, which had been expanded in territory - following the Treaty of Paris. - - - - Also known as the Treaty with the Delawares, this was the first written treaty - between the newly formed United States and any Native American people, in this case, the - Lenape or Delawares. - - - - -

The next example demonstrates the use of the - where attribute with event, coordinated - with location information stored in listPlace.

- - - - - - Luftwaffe shoots down Ilyushin Il-4 - DB-3F - - Іван Чиссов - - - Snap, Crackle, Pop is shot down by German flak - B-17 - - Alan Magee - - - Avro Lancaster shot down by Junkers Ju 88 - Lancaster - - Nicholas Alkemade - - - LANSA 508 struck by lightning - Amazon rainforest - - Juliane Diller (née Koepcke) - - - Bombing of Yugoslav Airlines Flight 367 - JAT 367 - - Весна Вуловић - - - - SAS parachute failure - Bear Grylls - - - - - Johannesburg parachute failure - Christine McKenzie - - Christine McKenzie - - - Cameraman fails to open chute - Sport videographer - - - - - - - - Gare de Saint-Nazaire - - 47.28657,-2.21171 - - - - Johannesburg - - South Africa - Gauteng - - - - Камчатке - - Russia - Kamchatka Krai - - - - Kenya - - - Oberkirchen - - Deutschland - Nordrhein-Westfalen - Arnsberg - Hochsauerlandkreis - Schmallenberg - 51.154,8.357 - - - - Puerto Inca - - Peru - Huánuco - Puerto Inca - - - - Schmallenberg - Smalmereg - - - - - Sebnitz - - 50.966667,14.283333 - - - - Eastern Front - - - - Zambia - - - - - - Весна Вуловић - Vesna Vulović - - - - - - Іван Михайлович Чиссов - Иван Михайлович Чисов - Ivan Mikhailovich Chisov - - - - - - Alan Eugene Magee - - - - - - Nicholas Stephen Alkemade - - - - - - Edward Michael Grylls - - - - - Juliane Koepcke - - - - - James Boole - 1978, give or take a year - - - - - - - - - -

The where attribute on event can point to multiple canonical place descriptions, which indicates that an event took place in multiple locations. For example, the November 2015 - Paris Attacks took place at six different locations in Paris; this - might be encoded as an event with a where - attribute with six space-separated values, or using a listPlace (nested into the event or standalone).

- -

Events may also be modeled as hierarchies of nested events. For example, a two part meeting might be represented as follows: - - - All day meeting to resolve content models - - first part - - - second part - - - -

- -

For event as a child element of person, note the Section .

-
- -
- Objects -

- - - - - An object is any material thing whether real, in existence, fictional, missing, or purported about which more - information is known. Where objects have proper names the objectName element may be used to encode these. - However, many objects are not named but the object element may still be used to provide a description of them. - The object element is a more general descriptive form of the msDesc element. The latter should be used - for describing manuscripts and similar text-bearing objects but can be viewed as a more specific form of the - object element.

-

- Please note: The object element is a recent addition to TEI P5 Guidelines as of version 3.5.0 and as such might - be more prone to further revision in the next few releases as its use develops. This may be particularly evident where its - contents have been borrowed from msDesc and have yet to be generalized from their use in the context of manuscript descriptions. -

-

The object element usually appears inside the - listObject element which is used to group - descriptions of identifiable objects. The listObject - element is a member of model.listLike and so may appear inside - standOff, or anywhere else that list is - allowed. This enables the flexibility of using - listObject to contain a set of metadata descriptions - stored in the TEI header, or as a list of objects transcribed from - a source document. The equivalent list for manuscript - descriptions is listBibl.

-

- - - - - - - - Overall, the basic structure of an object element is akin to that of msDesc in that it is providing a - structured description of an object. After a group of - identifying information, it has the option of paragraphs or, if the msdescription module is - loaded, msContents, physDesc, history, and additional elements for descriptive - metadata about this object. Although these elements originate from manuscript description the object element may - be used for all forms of object (whether text-bearing or not). - - - Where descendents of object still have the hallmarks - of their use in manuscript description, the descriptions as relating to manuscripts should be interpreted as applying to all - forms of object (text-bearing) or not.

-

The objectIdentifier element is a general-purpose - grouping element for location or identification information relating to a single object or resource. It is very similar to - an msIdentifier element with less contraints on the order of its contents. The objectIdentifier may be more - or less detailed dependent on the needs of the encoder. In some cases an object may be used mostly as a common - reference point for multiple objectName elements to refer back to. In situations, one might provide more detailed - information in the objectIdentifier where it is available or desirable. Compare - - - Excalibur - -

Excalibur is the name for the legendary sword of King Arthur.

- - where only a single objectName is provided and below where multiple versions are provided. - - - Excalibur - Caliburn - Caledfwlch - Calesvol - Kaledvoulc'h - Caliburnus - Wales - -

Excalibur is the main English name for the legendary - sword of King Arthur. In Welsh it is called - Caledfwlch, in Cornish it is called - Calesvol, in Breton it is called - Kaledvoulc'h, and in Latin it is - called Caliburnus. In some versions - of the legend, Excalibur’s blade was engraved with phrases on opposite - sides: Take me up and Cast me away (or similar).

- - -

-

Moreover, the objectIdentifier may include an address element to provide the address at which the object - currently resides. The use of location within this enables the provision of geographical coordinates when - describing objects not housed in traditional repositories or institutions. This may also be used to supplement more - traditional repository location information if available and, for example, to enable providing outputs such as maps - showing the location of encoded objects. - - Mask of Tutankhamun - 256a - 60672 - 220 - Museum of Egyptian Antiquities -

- 15 Meret Basha - Ismailia - Cairo - Egypt - - 30.047778, 31.233333 - -
- - -

-

The msContents element is currently used to provide a description of the intellectual contents of any text on an object - and, being optional, is not necessary if there are no intellectual contents to describe. (Such contents, especially in the - case of artistic objects, may not always be textual.) The physDesc element may be used to give a physical - description of the object either in prose or using more structured elements as and where they apply to that kind of - object. The history element provides the option to describe the history of the object as paragraphs or with more - structure using the origin element, as many provenance stages as are appropriate, and - acquisition to describe its current ownership. The additional element may be used to provide - information about surrogates for the object (such as digital facsimiles) as well as administrative and curatorial - information. A full description of an object can provide more or less detail at any level to represent the state of - knowledge about the object. - - - - - Mask of Tutankhamun - 256a - 60672 - 220 - Museum of Egyptian Antiquities -
- 15 Meret Basha - Ismailia - Cairo - Egypt - - 30.047778, 31.233333 - -
- - -

The back and shoulders of the mask is inscribed with a protective spell in Egyptian hieroglyphs formed of ten - vertical and horizontal lines. This spell first appeared on masks in the Middle Kingdom at least 500 years - before Tutankhamun, and comes from chapter 151 of the Book of the Dead.

- - -

The mask of Tutankhamun is 54cm x 39.3cm x 49cm. It is constructed from two layers of high-karat gold that - varies in thickness from 1.5-3mm. It weighs approximately 10.23kg and x-ray crystallography shows that it is - composed of two alloys of gold with a lighter 18.4 karat shade being used for the face and neck while a heavier - 22.5 karat gold was used for the rest of the mask.

-

In the mask Tutankhamun wears a nemes headcloth which has the royal insignia of a cobra (Wadjet) and vulture - (Nekhbet) on it. These are thought respectively to symbolize Tutankhamun's rule of both Lower Egypt and Upper - Egypt. His ears are pierced for earrings. The mask has rich inlays of coloured glass and gemstones, including - lapis lazuli surrounding the eye and eyebrows, quartz for the eyes, obsidian for the pupils. The broad collar is - made up of carnelian, feldspar, turquoise, amazonite, faience and other stones.

- - - -

The mask of Tutankhamun was created in Egypt around 1323 BC. It is a death mask of the 18th-dynasty ancient Egyptian Pharaoh Tutankhamun - who reigned 1332–1323 BC.

- - -

The mask of Tutankhamun was found in his burial chamber at Theban Necropolis in the Valley of the Kings in - 1922. On 28 October 1925 the excavation team led by English archaeologist Howard Carter opened the heavy - sarcophagus and three coffins and were the first people in around 3,250 years to see the mask of Tutankhamun. - Carter wrote in his diary: The pins removed, the lid was raised. The penultimate scene was disclosed – - a very neatly wrapped mummy of the young king, with golden mask of sad but tranquil expression, symbolizing - Osiris … the mask bears that god's attributes, but the likeness is that of Tut.Ankh.Amen – placid and - beautiful, with the same features as we find upon his statues and coffins. The mask has fallen slightly - back, thus its gaze is straight up to the heavens. -

- - In December 1925, the mask was removed from the tomb, placed in a crate and transported 635 - kilometres (395 mi) to the Egyptian Museum in Cairo, where it remains on public display. - - - - - When it was discovered in 1925, the 2.5kg narrow gold beard was no longer attached to - the mask and was reattached to the chin by use of a wooden dowel in 1944. - In August 2014 when the mask was removed from its display case for cleaning, the - beard fell off again. Those working in the museum unadvisedly used a quick-drying epoxy to attempt to fix - it, but left the beard off-centre. - The damage was noticed and repaired in January 2015 by a German-Egyptian team who - used beeswax, a material known to be used as adhesives by the ancient Egyptians. - - - - - - -

- - -

If the object is being referenced from elsewhere in the document, this is usually done with an objectName. For - example here the Alfred-Jewel xml:id is referenced from a paragraph elsewhere in the document using the ref - attribute on the objectName element. - - - - - - - United Kingdom - Oxfordshire - Oxford - University of Oxford - Ashmolean Museum - English Treasures - AN1836p.135.371 - https://en.wikipedia.org/wiki/Alfred_Jewel - Alfred Jewel - - -

The Alfred Jewel is about 6.4 cm in length and is made of combination of filigreed gold - surrounding a polished teardrop shaped piece of transparent quartz. Underneath the rock - crystal is a cloisonné enamel image of a man with ecclesiastical symbols. The sides of the jewel holding the - crystal in place contain an openwork inscription saying "AELFRED MEC HEHT GEWYRCAN", meaning 'Alfred ordered me - made'.

- - - It is generally accepted that the Alfred Jewel dates from the late 9th Century and - was most likely made in England. - The jewel was discovered in 1693 at Petherton Park, North Petherton in the English county - of Somerset, on land owned by Sir Thomas Wroth. North Petherton is about 8 miles away from Athelney, where King - Alfred founded a monastery. - A description of the Alfred Jewel was first published in 1698, in the Philosophical - Transactions of the Royal Society. - It was bequeathed to Oxford University by Colonel Nathaniel Palmer (c. 1661-1718) and today is in - the Ashmolean Museum in Oxford. - - - - - -

- The Minster Lovell Jewel is probably the most similar to the - Alfred Jewel and was found in Minster - Lovell in Oxfordshire and is kept at the Ashmolean Museum. -

- -

- -

-There is no restriction on the form, size, or type of object that may be described by an object element, however, some objects may be more adequately described by a place element depending on context. Where a description of an object is being provided in terms of identification, physical characteristics, or history, then an object element may be preferred. Where metadata is being recorded about the geo-political location, population, or similar traits, then the place element may be better suited. A corresponding relation between an object description and place may be recorded through the use of the corresp attribute. An example of a large object that might be described with the object element could be a building such as the Central Library of the National Autonomous University of Mexico. -

- - -

- - - - The Central Library of UNAM - The Central Library of the National Autonomous University of Mexico - La Biblioteca Central de la Universidad Nacional Autónoma de México - Mexico City - Coyoacán - Mexico - - - -

The Central Library encompasses an area of 16 thousand square - meters and is built on a three meter platform. The base contains two basalt - fountains and decorative reliefs inspired by - pre-Hispanic art.

-

The library has ten windowless floors for book storage, each having enough space for 120 thousand volumes. - These storage areas have the necessary lighting, temperature and humidty conditions for book conservation. - In the reading room, flanked by a garden on each side, the diffuse and matte light is filtered through - thin tecali stone slabs. The semi-basement of the building contains the service - and administrative offices of the library.

-

The building facades are covered with one of the largest murals in the world and is made from naturally - colored stone tiles. It is entitled Historical Representation of Culture and is by - Juan O'Gorman.

- - - - At the base of the building there are two basalt fountains and decorative reliefs - around the outside that are inspired by pre-Hispanic art. The color of the stone in these elements is left - exposed to take advantage of the stone's texture as an aesthetic and expressive element, and to give a - sense of continuity to the external pavement. - - -

The outside windowless portion of the building contains one of the largest murals in the world. This is - called Historical Representation of the Culture and is a stone polychromatic - mosaic based on the combination of 12 basic colors. The mural is created in an - impressionist style where the coloured tiles when seen from a distance form specific figures. The 12 - colors where chosen from 150 samples of original stones with the criteria including the stone's - resistance to degredation by weather. According to the artist, Juan - O'Gorman, in the mosaic he represented three fundamental historical facets of the Mexican - culture: the pre-Hispanic era, the Spanish colonial era, and the modern age. For example with the North - Wall, this represents the pre-Hispanic era and is dominated by mythical elements relating to the - life-death duality. The left side of the main axis there are - deities and scenes pertaining to the creation of life. The right hand side of the mural contains figures - relating to death. For a more detailed description see https://en.wikipedia.org/wiki/Central_Library_(UNAM)#Murals.

- - - - - In 1948 the architect and artist Juan O'Gorman, in - collaboration with architects Gustavo Saavedra and Juan Martinez de Velasco designed the building with a - functionalist approach, as part of the greater project of the construction of the University City on the - grounds of the Pedregal de San Angel in Mexico City. Originally the building was planned to host the National - Library and National Newspaper Library of Mexico. The library finally opened its doors for the first time on - 5 April 1956. In July 2007 it was declared a UNESCO - world heritage site. - - - - - - The library was significantly remodelled from 1981 - 1983 with the - purpose of changing from closed shelving to open stacks, providing users more direct access to the - collections. - - - - - - - -

- - - - - - - - - - - - -
- - - -
- Names and Nyms -

So far we have discussed ways in which a name or referring string encountered in running text may be resolved by - considering the object that the name refers to: in the case of a personal name, the name refers to a person; in the case - of a place name, to a place, for example. The resolution of this reference is effected by means of the key or - ref attributes available to all elements which are members of the att.naming - class, such as persName or placeName and their more specialized variants such as forename or - country. However, names can also be regarded as objects in their own right, irrespective of the - objects to which they are attached, notably in onomastic studies. From this point of view, the names - John in English, Jean in French, and Ivan in - Russian might all be regarded as existing independently of any person to which they are attached, and also independently - of any variant forms that might be attested in different sources (such as Jon or Johnny in English, or Jehan or Jojo in - French). We use the term nym to refer to the canonical or normalized form of a name regarded in such a way, - and provide the following elements to encode it: - - - -

-

Any element which is a member of the att.naming class may use the attribute nymRef - to indicate the nym with which it corresponds. Thus, given the following nym for the name - Antony: - - -

Antony
- - - an occurrence of this name in running text might be encoded as follows: - Tony Blair Note that this association (between "Tony" and "Antony") has - nothing to do with any individual who might use the name.

-

The person identified by this particular Tony may however be indicated independently using the ref attribute, - either on the forename or on the whole name component: - Tony - - - Tony Blair - politician - -

-

The nym element may be thought of as providing a specialized kind of dictionary entry. Like a dictionary entry, - it may contain any element from the model.entryPart class, such as form, - etym, etc. For example, we may show that the canonical form for a given nym has two orthographic variants in - this way: - -

- Ian - Iain -
- - -

-

Because a schema intending to make use of the nym or listNym element must include the dictionaries module as well as the namesdates module, many other - elements are available in addition to form. For example, to provide a more complex etymological decomposition of - a name, we might use the existing etym element, as follows: -

Bogomil
- Means favoured by God from the Slavic elements bog - God and mil - favour - -

-

Where it is necessary to mark the substructure of nyms, this may be done by seg elements within the - form: - -

- - Bogomil - Bogomil - -
- - The seg element used here is provided by the TEI - linking module, which would therefore also need to be included in a schema built to - validate such markup. Other possibilities for more detailed linguistic analysis are provided by elements included in that - and the analysis (see ) or iso-fs modules - (see ).

-

Alternatively, each of the constituents of Bogomil might be regarded as a nym in its own right: - - -

bog
- - -
mil
- - Within running text, a name can specify all the nyms associated with it: ...Bogomil... Similarly, - within a nym, the attribute parts is used to indicate its constituent parts, where these have been identified - as distinct nyms: - -
Bogomil
- - -

-

The nym element may also combine a number of other nym elements together, where it is intended to show - that they are all regarded as variations on the same root. Thus the different forms of the name John, all being derived - from the same root, may be represented as a hierarchic structure like this: -

Iohannes
- -
John
- -
Johnny
- - -
Jon
- - - -
Ivan
- - -
Jean
- - -

-

The nym element may be used for components of geographical or organizational names as well. For example: - - Lairig - Eilde - ... -

lairig
- sloping hill face - ... -

- -

- - - - As noted above, use of these elements implies that both the dictionaries and the - namesdates modules are included in a schema.

-
-
- -
- Dates -

The following elements for the encoding of dates and times were introduced in section : - - - -

-

The current module namesdates provides a mechanism for more detailed encoding of relative - dates and times. A relative temporal expression describes a date or time with reference to some other - (absolute) temporal expression, and thus may contain an offset element in addition to one or more date - or time elements: - - -

-

As members of the att.datable and att.duration classes, which in - turn are members of att.datable.w3c and att.duration.w3c - respectively, the date and time elements share the following attributes: - - - -

-
- Relative Dates and Times -

As noted above, relative dates and times such as in the Two Hundredth and First Year of the Republic, twenty - minutes before noon, and, more ambiguously, after the lamented death of the Doctor or an hour after the - game have two distinct components. As well as the absolute temporal expression or event to which reference is made - (e.g. noon, the game, the death of the Doctor, [the foundation of] the Republic), they also - contain a description of the distance between the time or date which is indicated and the referent - expression (e.g. the Two Hundredth and First Year, twenty minutes, an hour); and (optionally) an - offset describing the direction of the distance between the time or date indicated and the - referent expression (e.g. of implying after, before, after).

-

The distance component of a relative temporal expression may be encoded as a temporal element in - its own right using either date or time, or with the more generic measure element. A special - element, offset, is provided by this module for encoding the offset component of a - relative temporal expression. The absolute temporal expression contained within the relative expression may be encoded - with a date or time element; in turn, those elements may of course be relative, and thus contain - date or time elements within themselves. This allows for deeply nested structures such as the - third Sunday after the first Monday before Lammastide in the fifth year of the King's second marriage ... but so - does natural language.

-

In the following examples, the when and dur attributes have been used to simplify processing of - variant forms of expression: - A fortnight - before - Christmas 1786 - - I reached the station

-

In the following example, a nested date element is used to show that my birthday and the cited date are - parts of the same temporal expression, and hence to disambiguate the phrase A week before my birthday on 9th - December: - A week - before - - my birthday on 9th December - - The alternative reading of this phrase could be encoded as follows: - A week - before - my birthday on 9th December - -

-

Where more complex or ambiguous expressions are involved, and where it is desirable to make more explicit the - interpretive processes required, the feature structure notation described in chapter may be used. - Consider, for example, the following temporal expression which occurs in the Scottish Temperance Review - of August 1850, referring to the summer holiday known in Glasgow simply as the Fair: Not only is the city, during the Fair, a horrible - nucleus of immorality and wickedness; it sends our multitudes to pollute and demoralize the country. -

-

For the definition of the ana attribute, see chapter (in particular ). It is used here to link the temporal phrase with an interpretation of it. Like most traditional - fairs and market days, the Glasgow Fair was established by local custom and could vary from year to year. Consequently, - in order to provide such an interpretation, it is necessary to draw upon additional information which may or may not be - located in the particular text in question. In this case, it is necessary at least to know the spatial and temporal - context (year and place) of the fair referred to. These and other features required for the analysis of this particular - temporal expression may be combined together as one feature structure of type date-analysis: - the Fair - Glasgow - - 1850-08-08 - 1850-09-19 - For further discussion of feature structure representation see chapter .

-
- -
- Absolute Dates and Times - -

The following are examples of absolute temporal expressions.

-

- The university's view of American affairs - produced a stinging attack by Edmund Burke in the Commons debate of 26 October - 1775 - - Friday, 14 May 1993 - -

-

It may be useful to categorize a temporal expression which is given in terms of a named event, such as a public - holiday, or a named time such as tea time or matins: In - New York, New Year's Day is the quietest of holidays, Independence Day the most turbulent. -

- - - - - - - - - -

Absolute temporal expressions denoting times which are given in terms of seconds, minutes, hours, or of well-defined - events (e.g. noon, sunset) may similarly be represented using the time element. The train leaves for Boston at - At we walked to the beach. - The train leaves for Boston at -

-
-
- More Expressive Normalizations -

The attributes for normalization of dates and times so far described use a standard format defined by XML Schema Part 2: Datatypes Second Edition. This format is widely accepted and has significant - software support. It is essentially a profile of ISO 8601 Data elements and interchange formats — Information - interchange — Representation of dates and times. The full ISO standard provides formats not available in the - W3C recommendation, for example, the capability to refer to a date by its ordinal date or week date, or to refer to a - century. It also provides ways of indicating duration and range.

- -

When this module is included in a schema, the following additional attributes are provided: - - - These attributes may be used in preference to their W3C equivalent when it is necessary to provide a - normalized value in some form not supported by the W3C attributes. For example, a century date in the W3C format must be - expressed as a range, using the from attribute together with either the to attribute or the - dur (duration) attribute: fourteenth century - fourteenth century - With the attribute when-iso, however, it is possible to express the same normalized value in any of - the following additional ways: fourteenth - century - fourteenth century - fourteenth century - -

- - - - - - - - - - - - - - - - -
- -
- Using Non-Gregorian Calendars -

All date-related encoding described above makes use of the Gregorian calendar, on which both the ISO and W3C datetime - formats are based. However, historical texts often pre-date the invention of the Gregorian calendar in the 16th century, - or its adoption in Europe over the following centuries, and many other calendars are used in texts from other cultures - and contexts. Non-Gregorian dates can be encoded using methods described below.

- -

First, a Calendar Description element needs to be supplied in the teiHeader as described in :

- - - -

The Julian calendar, as used in England until 1752.

 - - - -

The following attributes can now be used to encode dates using this calendar: - - - - -

The Poole by S. Giles Churchyarde was a large water in the yeare 1244.

- Here, the calendar attribute points to the calendar element in the header which defines and - describes the calendar used.

- -

The calendar attribute is used to specify the calendar used in the text content of the dating - element which bears it. For reasons of consistency and computability, it is often useful to complement the content of an - element with attributes such as when, notBefore, notAfter, etc. For dates expressed in a non-Gregorian calendar, - such normalizations may also be expressed in terms of the non-Gregorian calendar specified by the datingMethod attribute. - The attributes when-custom, notBefore-custom, from-custom, etc. are provided for this purpose; the datingMethod attribute - is used to identify the calendar used in the value of these attributes: - The Tryumphs of Peace. That Celebrated the Solemnity of the right Honorable Sr Francis Iones Knight, at - his Inauguration into the Maioraltie of London, on Monday being the 30. of October, 1620. - - Here, the calendar attribute specifies the calendar used in the text content of the date - element, as before, whereas the datingMethod attribute signifies that the calendar used in the - when-custom attribute is also Julian. The schema could be customized in order to constrain the content of - custom attributes in a manner similar to the constraints provided on regular Gregorian dating attributes such as - when, to enforce consistency in the use of non-Gregorian dates.

- -

Custom dating attributes can be combined with any of the standard dating attributes in order to provide a standardized - Gregorian version of a non-Gregorian date. We might enhance the preceding example with the addition of when, - providing the Gregorian calendar equivalent of the Julian date: - 30. of - October, 1620. - -

-
-
- - -
- Module for Names and Dates -

The module described in this chapter makes available the following components: - Names, dates, persons and places - Names and dates - Noms, dates, personnes et lieux - 名稱與日期 - Nomi e date - Nomes e datas - 名前モジュール - The selection and combination of modules to form a TEI schema is described in .

-
- -
diff --git a/P5/Source/Guidelines/fr/ND-NamesDates.xml b/P5/Source/Guidelines/fr/ND-NamesDates.xml new file mode 120000 index 0000000000..17a3993d16 --- /dev/null +++ b/P5/Source/Guidelines/fr/ND-NamesDates.xml @@ -0,0 +1 @@ +../en/./ND-NamesDates.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/NH-Non-hierarchical.xml b/P5/Source/Guidelines/fr/NH-Non-hierarchical.xml deleted file mode 100644 index 652eaf1b20..0000000000 --- a/P5/Source/Guidelines/fr/NH-Non-hierarchical.xml +++ /dev/null @@ -1,824 +0,0 @@ - - - - - - - -
- Non-hierarchical Structures -

XML employs a strongly hierarchical document model. At various - points, these Guidelines discuss problems that arise when using - XML to encode textual features that either do not naturally lend - themselves to representation in a strictly hierarchical form or - conflict with other hierarchies represented in the - markup. Examples of such situations include: - -

Conflict between the hierarchy established by the - physical structure of a document (e.g., volume, page, - column, line) and its rhetorical or linguistic - structure (e.g., chapters, paragraphs, sentences, - acts, scenes, etc.)

- - -

Conflict between a verse text's metrical structure - (e.g., its arrangement in stanzas and metrical lines) - and its rhetorical or linguistic structure (e.g., - phrases, sentences, and, for plays, acts, scenes, and - speeches).

- - -

Conflict between metrical, rhetorical, or - linguistic structure and the representation of direct - speech, especially if the quoted speech is interrupted - by other elements (e.g., What, she asked, - was that all about) or crosses metrical, - rhetorical, or linguistic boundaries.

- - -

Conflict between different analytical views or - descriptions of a text or document, e.g., markup - intended to encode diplomatic information about a - word's appearance in a manuscript with markup intended - to describe its morphology or pronunciation.

- - -

-

Non-nesting information poses fundamental problems for any - XML-based encoding scheme, and it must be stated at the outset - that no current solution combines all the desirable attributes of - formal simplicity, capacity to represent all occurring or - imaginable kinds of structures, suitability for formal or - mechanical validation. The representation of non-hierarchical - information is thus necessarily a matter of trade-offs among - various sets of advantages and disadvantages.

-

These Guidelines support several methods for handling - non-hierarchical information: - -

redundant encoding of information in multiple forms - (discussed in )

- - -

the use of empty elements to delimit the boundaries - of a non-nesting structure (discussed in )

- - -

the division of a logically single non-nesting - element into segments that nest properly in their - immediate hierarchical context but can also be - reconstituted virtually across these hierarchical - boundaries (discussed )

- - -

stand-off markup: the annotation of information by - pointing at it, rather than by placing XML tags within - it (discussed in )

- - Some of these methods can be used in TEI-conformant documents. Others - require extension.

-

In the sections which follow these techniques are described and their advantages and - disadvantages are briefly discussed. The various solutions to the problem will be - exemplified using extracts from two poems. The first is the opening quatrain from William - Wordsworth's Scorn not the sonnet: - Scorn not the sonnet; critic, you have frowned, - Mindless of its just honours; with this key - Shakespeare unlocked his heart; the melody - Of this small lute gave ease to Petrarch's wound. - The second example is the third stanza from the fourth section of Robert Pinsky's - Essay on Psychiatrists: - - Catholic woman of twenty-seven with five children - And a first-rate body—pointed her finger - at the back of one certain man and asked me, - "Is that guy a psychiatrist?" and by god he was! "Yes," - She said, "He looks like a psychiatrist." - Grown quiet, I looked at his pink back, and thought. - - These two texts can be analysed in various ways. The first, which we might describe - as the Metrical View, encodes the text according to its metrical - features: line divisions (as here), stanzas or cantos in larger poems, and perhaps prosodic - features like stress or syllable patterns, alliteration, or rhyme. A second view, which we - might describe as the Grammatical, encodes linguistic and rhetorical - features: phonemes, morphemes, words, phrases, clauses, and sentences. A third view, the - Dialogic, might concentrate on narrative voice: distinguishing - between the narrator and their interlocutors and identifying individual segments as direct - quotations. In our examples, we will restrict ourselves to relatively simple conflicts: for - the Metrical View we will encode only metrical lines and line groups; for the - Grammatical View we will restrict ourselves to encoding sentences; and for - the Dialogic View, we only will distinguish direct quotation from other - narration.

-
- Multiple Encodings of the Same Information -

Conceptually, the simplest method of disentangling two (or - more) conflicting hierarchical views of the same information - is to encode it twice (or more), each time capturing a single - view.

-

Thus, for example, the Metrical View of Scorn not the - sonnet might be encoded as follows, using the l element to encode - each metrical line: - Scorn not the sonnet; critic, you have frowned, - Mindless of its just honours; with this key - Shakespeare unlocked his heart; the melody - Of this small lute gave ease to Petrarch's wound. -

-

The Grammatical View would be encoded by - taking the same text and replacing the metrical markup with - information about its sentence structure: -

- Scorn not the sonnet; - critic, you have frowned, Mindless of its just honours; - with this key Shakespeare unlocked his heart; - the melody Of this small lute gave ease to Petrarch's wound. -

-

-

Likewise, the more complex passage from Pinsky could be - encoded in three different ways to reflect the different - metrical, grammatical, and dialogic views of its text: - - Catholic woman of twenty-seven with five children - And a first-rate body—pointed her finger - at the back of one certain man and asked me, - "Is that guy a psychiatrist?" and by god he was! "Yes," - She said, "He looks like a psychiatrist." - Grown quiet, I looked at his pink back, and thought. - - - - -

-Catholic woman of twenty-seven with five children And a -first-rate body—pointed her finger at the back of one certain man and -asked me, "Is that guy a psychiatrist?" and by god he was! -

-

-"Yes," She said, "He looks like a -psychiatrist." -

-

- Grown quiet, I looked at his pink back, and thought. -

- - - -Catholic woman of twenty-seven with five children And a first-rate -body—pointed her finger at the back of one certain man and asked me, -Is that guy a psychiatrist? and by god he was! -Yes, She said, He looks like a -psychiatrist. Grown quiet, I looked at his pink back, and -thought. - - -

-

This method is TEI-conformant. Its advantages are that each - way of looking at the information is explicitly represented in - the data and that the individual views are simple to - process. The disadvantages are that the method requires the - maintenance of multiple copies of identical textual content - (an invitation to inconsistency) and that there is no explicit - indication that the various views, which might be in separate - files, are related to each other: it might prove difficult to - combine the views or access information from one view while - processing the file that contains the encoding of - another.It has been shown, however, that it - is possible to relate the different annotations in an indirect - way: if the textual content of the annotations is identical, - the very text can serve as a means for linking the different - annotations, as described in .

-
-
- Boundary Marking with Empty Elements -

A second method for accommodating non-hierarchical objects - in an XML document involves marking the start and end points - of the non-nesting material. This prevents textual features - that fall outside the privileged hierarchy from invalidating - the document while identifying their beginnings and ends for - further processing. The disadvantage of this method is that no - single XML element represents the non-nesting material and, as - a result, processing with XML technologies is significantly - more difficult.

-

The empty elements used at each end are called - segment-boundary elements or - segment-boundary delimiters. There are several - variations on this method of encoding.

- -

For some common structural features, the TEI provides - milestone elements that can be used to mark the beginning of a - textual feature. These include lb, pb, - cb, handShift, and the generic - milestone. Using lb, for example, it is - possible to indicate both the physical lineation of a poem on - the page and its grammatical division into sentences: - -

-Scorn not the sonnet;; critic, you have -frowned, Mindless of its just honours; with this -key Shakespeare unlocked his heart; the melody -Of this small lute gave ease to Petrarch's -wound.

-

-

The use of these elements is by definition TEI-conformant. - Care should be taken, however, that the meaning of - the milestone elements is preserved: semantically, for - example, lb is used to mark the start of a new - (typographical) line. While in much modern poetry, - typographical and metrical line divisions correspond, - lb does not itself make a metrical claim: in encoding - verse from sources, such as Old English manuscripts, where - physical line breaks are not used to indicate metrical - lineation, the correspondence would break down entirely.

- - -

The segment boundaries also may be delimited by the generic - anchor element. Attributes can then be used to - indicate the type of feature being delimited and whether a - given instance opens or closes the feature. - - - Scorn not the sonnet; - - critic, you have frowned, - Mindless of its just honours; - with this key - Shakespeare unlocked his heart; - the melody - Of this small lute gave ease to Petrarch's wound. - -

-

This method is TEI-conformant.

- - -

Another approach is to design custom elements that provide - richer information about the feature being delimited or its - boundaries. This information can be included as attribute - values or as part of the element name itself: e.g., - boundaryStart - element="sentence"/... boundaryEnd - element="sentence"/, sentenceBoundary - position="start"/... sentenceBoundary - position="end"/, or sentenceBoundaryStart/... - sentenceBoundaryEnd/: - - - -Scorn not the sonnet; - -critic, you have frowned, -Mindless of its just honours; -with this key -Shakespeare unlocked his heart; -the melody -Of this small lute gave ease to Petrarch's wound. - -

-

If the custom elements can be replaced by TEI elements and - attributes without loss of information, this method is TEI-conformant - (see ); if the custom elements - introduce information or distinctions that cannot be captured - using standard TEI elements, the method is an extension.

- - -

Finally, elements that are normally used to encode nesting - textual features (e.g., said, seg, - l, etc.) can be adapted so that they serve as empty - segment boundary delimiters when the features they encode - cross-hierarchical boundaries. Additional attributes (sID and eID in - the example below) are added to these elements in order to - allow the unambiguous correlation of start and end - points. This method has been introduced in the markup - literature under various names, including Trojan milestones, - HORSE markup, CLIX, and COLT. It is described in detail by - ): - - - Scorn not the sonnet;critic, you have frowned, - Mindless of its just honours; - with this key - Shakespeare unlocked his heart; - the melody - Of this small lute gave ease to Petrarch's wound. - - - Depending on how the modifications are carried out, - this method may be TEI-conformant, may represent an extension of the - TEI, or may produce a non-conformant document. - The method is TEI-conformant if the modified - elements and attributes can be mapped without loss of - information to existing TEI markup structures such as - milestone or anchor elements automatically (see ). - The method represents an Extension if the - modified elements are placed in a distinct, non-TEI - namespace (see ). - The method is non-conformant—and indeed strongly - deprecated—if the modified elements and attributes are - not placed in a distinct, non-TEI namespace (see ). -

- - - -

In each of the above examples (except the last), the relationship between the start and - end delimiters (where these exist) of a given feature is implicit: it is assumed that - "end" delimiters close the nearest preceding "start" delimiter, or, in the case of - milestones, that the milestone marks both the end of the preceding example and the - beginning of the next. Complications arise, however, when the non-nesting text overlaps - with other non-nesting text of the same type, as, for example, in a grammatical analysis - of the various possible interpretations of the noun phrase - fast trains and planes. In this case, the adjective fast - can be understood as either modifying trains and planes or just - trains:

- Two interpretations of the phrase - Fast trains and planes - - Graphic representation of two interpretations of the phrase Fast - trains and planes. -

-

In order to encode the possible analyses of this phrase, an - unambiguous method of associating opening and closing segment - boundary delimiters is required: - - - Fast - - trains - - and - planes - - - -

-

In this encoding, the first interpretation, in which - fast modifies the NP trains - and planes, the NP trains and - planes is opened using an anchor tag with - the xml:id value - NPInterpretationA and closed with an - anchor with the same value on corresp; in - the second interpretation, in which - fast forms a NP with - trains, the NP fast - cars is opened using an anchor tag with - the xml:id value - NPInterpretationB and closed with an - anchor tag that has the same value on - corresp.

-

Despite their advantages, segment boundary delimiters incur - the disadvantage of cumbersome processing: since the elements - of the analysis (e.g., the sentences in the poems, or phrases - in the above example) are not uniformly represented by nodes - in the document tree, they must be reconstituted by software - in an ad hoc fashion, which is likely to be difficult and may - be error prone.

-

Most important for some encoders, the method also disguises - the relationship between the beginning and the ending of each - logical element. This makes it impossible for standard - validation software to provide the same kind of validation - possible elsewhere in the encoding. When using grammar-based - schema languages it is not possible to define a content model - for the range limited by empty elements.Grammar based schema languages (e.g., DTD, W3C - Schema, and RELAX NG) are used to define markup languages - (e.g., XHTML or TEI). Rule-based schema languages (e.g., - Schematron) can be used to define further constraints. Such a - rule-based schema language permits a sequence of certain - elements between empty elements to be legitimized or - prohibited.

-
-
- Fragmentation and Reconstitution of Virtual Elements -

A third method involves breaking what might be considered a - single logical (but non-nesting) element into multiple smaller - structural elements that fit within the dominant hierarchy but - can be reconstituted virtually. For example, if a passage of - direct discourse begins in the middle of one paragraph and - continues for several more paragraphs, one could encode the - passage as a series of said elements, each fitting - within a p element. The resulting encoding is valid - XML, but the text in each said element represents - only a portion of the complete passage of direct - discourse. For this reason these elements are sometimes called - partial elements.

-

In the case of our selection from Pinsky's poem, for - example, the second passage of direct quotation, which crosses - a line boundary and is broken up by a She - said in the narrator's voice, can be made to fit - within the hierarchy established by the metrical lineation by - using two said elements: - - - - Catholic woman of twenty-seven with five children - And a first-rate body—pointed her finger - at the back of one certain man and asked me, - Is that guy a psychiatrist? and by god he was! - Yes, - She said, He looks like a -psychiatrist. - Grown quiet, I looked at his pink back, and thought. - - -

-

Similarly, the sentences in our example from Wordsworth - could be encoded: - - - Scorn not the sonnet; - critic, you have frowned, - - - Mindless of its just honours; - with this key - - - Shakespeare unlocked his heart; - the melody - - - Of this small lute gave ease to Petrarch's wound. - -

-

There are two main problems with this type of encoding. The - first is that it invariably means that the encoding will have - more elements claiming to represent a feature than there are - actual instances of that feature in the text. Thus, for - example, the passage from Scorn not the - sonnet marks seven spans of text using seg, - even though there are only four linguistic sentences in the - passage.

-

The second problem is that it can be semantically - misleading. Although they are tagged using the element for - sentence, for example, very few of the textual - features encoded using seg in this example represent - actual linguistic sentences: with this - key, for example, is a prepositional phrase, not a - sentence; Of this small lute gave ease to - Petrarch's wound is a string corresponding to no - single grammatical category.

-

Taken together, these problems can make automatic analysis - of the fragmented features difficult. An analysis that - intended to count the number of sentences in Wordsworth's - poem, for example, would arrive at an inflated figure if it - understood the seg elements to represent complete - rhetorical sentences; if it wanted to do an analysis of his - syntax, it would not be able to assume that seg - delimited linguistic sentences.

-

The technique of fragmentation is often complemented by the - technique of virtual joins. Virtual joins may be used to - combine objects in the text to a new hierarchy. Here is Scorn not the sonnet again; this time the - relationship between the parts of the fragmented sentences is - indicated explicitly using the next and - prev attributes described in . - - - - Scorn not the sonnet; - critic, you have frowned, - - - Mindless of its just honours; - with this key - - - Shakespeare unlocked his heart; - the melody - - - Of this small lute gave ease to Petrarch's wound. - - This method of virtually joining partial elements is sometimes called - chaining.

-

For fragments encoded using ab, l, - lg, div, or elements that belong to the - att.segLike class, an even simpler - mechanism for virtually joining fragments exists: the use of - the part attribute with the value - I (Initial), M - (Medial), or F (Final) as described in - . Here is the above example recoded to - reflect this method: - - Scorn not the sonnet; - critic, you have frowned, - - - Mindless of its just honours; - with this key - - - Shakespeare unlocked his heart; - the melody - - - Of this small lute gave ease to Petrarch's wound. - -

-

This method is TEI-conformant and simple to use. Its - disadvantage is that it does not work well for cases of - self-overlap, or if there are nested occurrences of the same - element type, as it can become difficult to ascertain which - initial, medial, or final partial element should be combined - with which others or in which order. This problem becomes - evident if we attempt to combine a detailed Grammatical view - of the Pinsky example with its metrical encoding: - - - - Catholic woman of twenty-seven with five children - - - And a first-rate body—pointed her finger - - - at the back of one certain man and asked me, - - - "Is that guy a psychiatrist?" and by god he was! - "Yes," - - - She said, "He looks like a psychiatrist." - - - Grown quiet, I looked at his pink back, and thought. - - -

- -

A third method for aggregating fragmented partial elements - involves using markup that is not directly part of the - encoding, e.g., the join element. In this method, a - join element is used elsewhere in the document to - indicate explicitly the members of the virtual element: - - - - Scorn - not - the - sonnet; critic, you - have - frowned, - - Mindless - of - its - just - honours; with - this - key - - - Shakespeare - unlocked - his - heart; the - melody - - - Of - this - small - lute - gave - ease - to - Petrarch's - wound. - - - -

- - - - -

- -

-

This use of join is TEI-conformant.

-

The major advantage of fragmentation and virtual joins is - that it allows all the hierarchies in the text to be handled - explicitly: both the privileged one directly represented and - the alternate hierarchy that has been split up and - rejoined. The major disadvantages are that (like most of the - other methods described here) it privileges one hierarchy over - the others, requires special processing to reconstitute the - elements of the other hierarchies, and, except in the case of - join, can be semantically misleading.

-
-
- Stand-off Markup -

Most markup is characterized by the embedding of elements - in the text. An alternative approach separates the text and - the elements used to describe it. This approach is known as - stand-off markup (see section ). It - establishes a new hierarchy by building a new tree whose nodes - are XML elements that do not contain textual content, but - rather links to another layer: a node in - another XML document or a span of text. This approach - can be subdivided according to different criteria. A first - distinction concerns the link base, i.e. the content to which - annotations are to be applied. Sometimes the link target - contains markup that can be referred to explicitly, as in the - following example where the offset markup uses the - xml:id values on w to provide targets for - xi:includeA fake namespace is - given for XInclude here, to avoid the markup being interpreted - literally during processing.: - - Scorn - not - the - sonnet; critic, you - have - frowned, - - Mindless - of - its - just - honours; with - this - key - - - Shakespeare - unlocked - his - heart; the - melody - - - Of - this - small - lute - gave - ease - to - Petrarch's - wound. - - - - - - - - - - - - - - - - -

-]]> - - - Note that the layer that uses XInclude to build another hierarchy - might well be in another document, in which case the value of href of xi:xinclude would need to be - the URL of the document that contains the base layer, in this case - the w elements. -

- -

This is very similar to the use of join discussed - above. The main advantages of the stand-off method are that it - is possible to specify attributes on the aggregate - seg elements, and that there exists off-the-shelf - software that will perform appropriate processing. Stand-off - markup may be used even when the base text being annotated is - plain text, i.e. does not have any XML encoding. In this case, - the range of text to be marked up is indicated by character - offsets (see , in particular ). Another distinction concerns the number - of files which can serve as link targets. Often, one - (dedicated) annotation is used as the link target of all the - other annotations. It is also possible to freely interlink - several layers.

-

It has been noted that stand-off markup has several - advantages over embedded annotations. In particular, it is - possible to produce annotations of a text even when the source - document is read-only. Furthermore, annotation files can be - distributed without distributing the source text. Further - advantages mentioned in the literature are that discontinuous - segments of text can be combined in a single annotation, that - independent parallel coders can produce independent - annotations, and that different annotation files can contain - different layers of information. Lastly, it has also been - noted that this approach is elegant.

-

But there are also several drawbacks. First, new stand-off - annotated layers require a separate interpretation, and the - layers—although separate—depend on each other. Moreover, - although all of the information of the multiple hierarchies is - included, the information may be difficult to access using - generic methods.

-

Inasmuch as it uses elements not included in the TEI - namespace, stand-off markup involves an extension of the - TEI.

-
-
- Non-XML-based Approaches -

There exist many non-XML methods of encoding a text that - either solve or do not suffer the problem of the inability to - encode overlapping hierarchies. These include, but are not - limited to, the following proposals.

- - Applying the notion of concurrent markup to XML - (). This reintroduces - the CONCUR feature of SGML, which was omitted from the XML - specification. - Designing a form of document representation in which - several trees share all or part of the same frontier, and - in which each individual view of the document has the form - of a tree (see ). - The colored XML proposal (), which stores a body of - information as a set of intertwined XML trees. This - approach eliminates unnecessary redundancy and makes the - database readily updatable, while allowing the user to - exploit different hierarchical access paths. - The MultiX proposal () , which represents documents as directed - graphs. Because XML is used to represent the graph, the - document is, at least in principle, manipulable with - standard XML tools. - The Just-In-Time-Trees proposal (), which stores documents - using XML, but processes the XML representation in - non-standard ways and allows it to be mapped onto data - structures that are different from those known from - XML. - The - Layered Markup and Annotation - Language LMNL - proposal. This offers alternatives to the basic - XML linear form as well as its data and processing - models. It uses an alternative notation to XML and - a data structure based on Core Range Algebra (). - - Markup Languages for Complex Documents - MLCD . This provides a - notation (TexMECS) and a data structure (Goddag) - as well as a draft constraint language for the - representation of non-hierarchical structures; see - . - -

These approaches are based either on non-standard XML - processing or data models, or not based on XML at all. Since - TEI is currently based on XML they are not described any - further in these Guidelines. Use of these methods with the TEI - will certainly involve extensions; in most cases the documents - will also be non-conformant.

-
- - -
diff --git a/P5/Source/Guidelines/fr/NH-Non-hierarchical.xml b/P5/Source/Guidelines/fr/NH-Non-hierarchical.xml new file mode 120000 index 0000000000..d58074a0a7 --- /dev/null +++ b/P5/Source/Guidelines/fr/NH-Non-hierarchical.xml @@ -0,0 +1 @@ +../en/NH-Non-hierarchical.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/PARTIND.xml b/P5/Source/Guidelines/fr/PARTIND.xml deleted file mode 100644 index 1ac7a6e99c..0000000000 --- a/P5/Source/Guidelines/fr/PARTIND.xml +++ /dev/null @@ -1,10 +0,0 @@ - - - - - - - -
Index - -
diff --git a/P5/Source/Guidelines/fr/PARTIND.xml b/P5/Source/Guidelines/fr/PARTIND.xml new file mode 120000 index 0000000000..20a0f60c0e --- /dev/null +++ b/P5/Source/Guidelines/fr/PARTIND.xml @@ -0,0 +1 @@ +../en/./PARTIND.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/PH-PrimarySources.xml b/P5/Source/Guidelines/fr/PH-PrimarySources.xml deleted file mode 100644 index d5512f2e23..0000000000 --- a/P5/Source/Guidelines/fr/PH-PrimarySources.xml +++ /dev/null @@ -1,3059 +0,0 @@ - - - - -
- Representation of Primary Sources - -

This chapter describes elements that may be used to represent primary source materials, - such as manuscripts, printed books, ephemera, or other textual documents. Some of these specialized elements, - particularly at phrase-level, add to the other elements available within text - to deal with textual phenomena more specific to primary source transcription. - Other structural and block-level elements described here can be used to represent primary - source materials by prioritizing the encoding of their spatial features over their logical - textual structure (that is, the elements described in chapter ). - These elements, facsimile, sourceDoc, and their children, may be used in - parallel and in combination with an encoding of logical text structures with text, - or as standalone representations. The element sourceDoc in particular provides a way - of combining facsimile and transcriptions by embedding transcribed text. This approach focuses - on physical and textual features that can be primarily described spatially, such as the sequence - of pages in a manuscript, or the layout of a printed page. This is not meant to be the only way - of transcribing primary sources in TEI, or even a preferred way; which approach is more appropriate - will depend on the specific needs of your project.

- -

Although this chapter discusses manuscript materials more frequently than other forms of written text, - most of the recommendations presented are equally applicable to facsimiles of a wide variety of media, - including printed matter, monumental inscriptions, and art. Each medium has its own vocabulary of agents. - In the following examples, terms such as scribe, author, editor, - annotator or corrector may be re-interpreted in terms - more appropriate to the medium being transcribed. In printed material, for example, the compositor plays a role analogous to the scribe, while in an authorial manuscript, the author and the scribe are the same person.

- -

This module may be used in conjunction with other modules. These recommendations are not intended to meet every transcriptional circumstance likely to be faced by any scholar. They are intended rather as a base to enable encoding of the most common phenomena found in the course of scholarly transcription of primary source materials. These guidelines do not address the encoding of physical description of textual witnesses: the materials of the carrier, the medium of the inscribing implement, the organisation of the carrier materials themselves (such as quiring, collation), authorial instructions or scribal markup, etc., except insofar as these are involved in the broader question of manuscript description, as addressed by the msdescription module described in chapter .

- -

This chapter begins by describing elements for handling digitally-encoded images of primary source materials for the purpose of creating digital facsimiles using the facsimile element ().

-

The next section () describes two ways of combining a facsimile images with a transcription; either by referencing a parallel transcription in text, or by providing an embedded transcription that prioritizes the encoding of a resource’s spatial features via the sourceDoc element and a number of transcriptional elements.

-

Section documents elements that support scholars in recording information about specific features of the text written on its physical carrier, such as and

-

Section describes how complex page layouts may be represented.

-

Section introduces the element fw (forme work) for encoding material repeated from page to page that falls outside the stream of the text.

-

Section describes how to document changes made during the production or revision of a primary source.

-

The chapter concludes with a technical overview of the structure and organization of the module described here. Some elements from other chapters are recontexualized for situations involving the transcription of primary source materials, whether within text or sourceDoc. Therefore, this overview should be read in conjunction with chapters and .

- -
- - Digital Facsimiles - -

A common approach in the TEI to representing pre-existing sources involves transcribing or otherwise converting sources into character form before marking them up. However, it is also a common practice to make a different form of - digital text that is instead composed of digital images of the - original source, typically one per page, or other written surface. We call such a resource - a digital facsimile. A digital facsimile may, in the simplest case, just - consist of a collection of images, with some metadata to identify them and the source - materials portrayed. It may sometimes contain a variety of images of the same source pages, - perhaps of different resolutions, or of different kinds. Such a collection may form part of - any kind of document, for example a commentary of a codicological or paleographic nature, - where there is a need to align explanatory text with image data. It may also be - complemented by a transcribed or encoded version of the original source, which may be - linked to the page images or embedded as discussed in . - In this section we present elements designed to support these - various possibilities and discuss the associated mechanisms provided by these - Guidelines.

- - -

When this module is included in a schema, the class att.global - is extended to include two new pointer attributes, facs and change: - - - The change attribute is discussed further below in section . The facs attribute is used to associate any element - in a transcription with an image of the corresponding part of the source, by means of the - usual URI pointing mechanism. -

- -

In the simple case where a digital text is composed of page images, the facs - attribute on the pb element may be used to associate each image with an - appropriate point in the text: - - - - - - - - - - - By convention, this encoding indicates that the image indicated by the - facs attribute represents the whole of the text following the pb - (page beginning) element, up to the next pb element. Any convenient milestone element - (see further ) could be used in the same way; for example if the - images represent individual columns, the cb element might be used. Though simple, - this method has some drawbacks. It does not scale well to more complex cases where, for - example, the images do not correspond exactly with transcribed pages, or where the - intention is to align specific marked up elements with detailed images, or parts of images. - The management of information about the images may become more difficult if references to - them are scattered through many files rather than being concentrated in a single - identifiable location. Nevertheless, this solution may be adequate for many straightforward - digital library applications.

- -

The recommended approach to encoding facsimiles is instead to use the facs - attribute in conjunction with the elements facsimile or sourceDoc, and - the elements surface, surfaceGrp, and zone, which are also - provided by this module. These elements make it possible to accommodate multiple images of - each page, as well as to record the position and relative size of elements identified on - any kind of written surface and to link such elements with digital facsimile images of - them. Typical applications include the provision of full text search in digital - facsimile editions, and ways of annotating graphics, for example so as to - identify individuals appearing in group portraits and link them to data about the people - represented.

- -

The following elements are available to represent components of a digital facsimile: - - - - - - - -

- -

Either of the facsimile or sourceDoc elements may be used to represent a - digital facsimile. Either may appear within a TEI document along with, or instead of, the - text element introduced in section . The sourceDoc element - is used when a digital facsimile contains a transcription that prioritizes the encoding of the spatial features and layout of a text document over the text’s logical textual structure; the text element - should be used when it contains a textual transcription focused on its logical features. - When the digital facsimile contains only images, - however, only facsimile elements should be used. In this section, we first discuss the - simpler case, returning to the use of the sourceDoc element in section below. When this module is selected therefore, a legal TEI - document may thus comprise any of the following: - a TEI header and a text element - a TEI header and a facsimile element - a TEI header and a sourceDoc element - a TEI header, a facsimile element, and a text element - a TEI header, one or more sourceDoc or facsimile elements, and a text - element - -

-

Like the text element, a facsimile element may also contain an optional - front or back element, used in the same way as described in sections - and .

- -

In the simplest case, a facsimile just contains a series of graphic elements, each - of which identifies an image file: - - - - - - - If desired, the binaryObject element described in - (or any other element from the model.graphicLike class) can be - used instead of a graphic.

- -

In this simple case, the four page images are understood to represent the complete - facsimile, and are to be read in the sequence given. Suppose, however, that the second page - of this particular work is available both as an ordinary photograph and as an infra-red - image, or in two different resolutions. The surface element may be used to group - the two image files, since these correspond with the same area of the work: - - - - - - - - - - -

- -

The surface element provides a way of indicating that the two images of page2 - represent the same surface within the source material. A surface might be one - side of a piece of paper or parchment, an opening in a codex treated as a single surface by - the writer, a face of a monument, a billboard, a membrane of a scroll, or indeed any - two-dimensional surface, of any size.

- -

The surfaceGrp element may be used to indicate that two (or more) surfaces are - associated in some way, for example because they represent the recto and verso of the same - leaf, as in this example: - - - - - - - - - - - - The surfaceGrp element may also be useful as a means of identifying other - groups of written surfaces, such as adjacent faces of a monument, or gatherings of leaves.

- -

Simply grouping related graphics is not however the main purpose of the surface - element: rather it is to help identify the location and size of the various two-dimensional - spaces constituting the digital facsimile. Note that the actual dimensions of the object - represented are not provided by the surface element ; rather, the surface - element defines an abstract coordinate space which may be used to address parts of the - image. Four attributes supplied by the att.coordinated class - are used to define this space. - - - -

-

By default, the same coordinate space is used for a surface and for all of its - child elements.The coordinate space may be thought of as a grid - superimposed on a rectangular space. Rectangular areas of the grid are defined as four - numbers a b c d: the first two identify the grid point which is at - the upper left corner of the rectangle; the second two give the grid point located at - the lower right corner of the rectangle. The grid point a b is - understood to be the point which is located a points from the - origin along the x (horizontal) axis, and b - points from the origin along the y (vertical) axis. It may - be most convenient to derive a coordinate space from a digital image of the surface in - question such that each pixel in the image corresponds with a whole number of units - (typically 1) in the coordinate space. In other cases it may be more convenient to use - units such as millimetres. Neither practice implies any specific mapping between the - coordinate system used and the actual dimensions of the physical object represented.

- -

A surface element can contain one or more zone elements, each of which - represents a region or bounding box defined in terms of the same coordinate - space as that of its parent surface element. A zone may be rectangular or - non-rectangular: a rectangular zone is defined by a sequence of four coordinates in the - same way as a surface; a non-rectangular zone is defined using the attribute - points, which provides a sequence of coordinates, each of which specifies a - point on the perimeter of the zone.The points attribute - supplies a points specification in the same form as that required - by the polyline or polygon elements in the SVG standard. See -

-

A zone may be used to define any region of interest, such as a detail or illustration, or - some part of the surface which is to be aligned with a particular text element, or - otherwise distinguished from the rest of the surface. A surface establishes a coordinate - system which may be used to address parts or the whole of some digital representation of a - written surface. A zone, by contrast, defines any arbitrary area of interest relative to - that surface, using the same coordinate system. It might be bigger or smaller than its - parent surface, or might overlap its boundaries. The only constraint is that it must be - defined using the same coordinate system.

- -

When an image of some kind is supplied within either a zone or a surface, the implication - is that the image represents the whole of the zone or surface concerned. In the simple case - therefore, we might imagine a surface defining a page, within which there is a graphic - representing the whole of that page, and a number of zones defining parts of the page, each - with its own graphic, each representing a part of the page. If however one of those - graphics actually represents an area larger than the page (for example to include a binding - or the surface of a desk on which the page rests), then it will be enclosed by a zone with - coordinates larger than those of the parent surface.

- - -

For example, consider the following figure:

- - - Badische Landesbibliothek, Manuscript Durlach 1, Fols. 95v-96r -
This is an image of a two page spread from a manuscript in the Badische - Landesbibliothek, Karlsruhe. We have no information as to the dimensions of the original - object, but the low resolution image displayed here contains 500 pixels horizontally and - 321 pixels vertically. For convenience, we might map each pixel to one cell of the - coordinate space.The coordinate space used here is based on pixels, - but the mapping between pixels and units in the coordinate space need not be one-to-one; - it might be convenient to define a more delicate grid, to enable us to address much - smaller parts of the image. This can be done simply by supplying appropriate values for - the attributes which define the coordinate space; for example doubling them all would - map each pixel to two grid points in the coordinate space. -

- -

We therefore define a surface element corresponding with the area of the image - which represents the whole of the two page spread and embed the graphic within it: - - - -

- - - -

If desired, the binaryObject element described in (or any - other element from the model.graphicLike class) may be used - instead of a graphic element.

- -

Since the image in this example is of a two page opening, we will probably wish to define - at least two nested zones, one for each page: - - - - - - - - - - - - - - -

-

As this example shows, in addition to acting as a container for graphic elements, - zone elements may be used to identify parts of a surface for analytical - purposes.

-

The relationship between zone and surface can be quite complex: for example, it may be - appropriate to treat the whole of a two page spread as a single written surface, perhaps - because particular written zones span both pages. A zone may contain a nested surface, if - for example a page has an additional scrap of paper attached to it. A zone may be of any - shape, not simply rectangular. Discussion of these and other cases are provided in section - below.

- - -

In the following extended example, we discuss a hypothetical digital edition of an early - 16th century French work, Charles de Bovelles' Géometrie Pratique.The image is taken from the collection at , and was digitized from a copy in the - Bibliothèque Municipale de Lyon, by whose kind permission it is included here. In - this edition, each page has been digitized as a separate file: for example, recto page 49 - is stored in a file called Bovelles-49r.png. In the - facsimile element used to contain the whole set of pages, we define a - surface element for this page, which we situate within a coordinate scale - running from 0 to 200 in the x (horizontal) axis, and 0 to 300 in the y (vertical) axis. - The surface element contains a graphic element which represents the whole - of this surface: - - - - We can now identify distinct zones within the page image using the - coordinate scale defined for the surface. In the following figure we show the upper part of the page, with boxes indicating four such zones. Each of these - will be represented by a zone element, given within the surface element - already defined, and specified in terms of the same coordinate system. Some zones of - interest are indicated by red lines in the following image.

- - Detail of p 49r from Bovelles Géometrie Pratique -
The following encoding defines each of the four zones identified in the figure - above. - - - - - - - - - - - - - Note that the location of each zone is defined independently but - using the same coordinate system.

- -

A non rectangular-zone, for example that containing the word cloche. - at bottom left of the page, could also be defined, using the points attribute: - - - - - - -

- - -

In the examples above a single graphic element has been associated directly with the - surface of the page rather than nesting it within a zone. However, it is also possible to - include multiple zone elements which contain a graphic element, if for - example a detailed image is available. Since all zone elements use the same - coordinate system (that defined by their parent surface), there is no need to - demonstrate enclosure of one zone within another by means of nesting. To continue the - current example, supposing that we have an additional image called - Bovelles49r-detail.png containing an additional image of the figure in the - third zone above, we might encode that zone as follows: - - - - -

- - -

Within a surface or zone, individual lines can be identified using the - path element, which also carries the points - attribute: -

- - Smaller detail of p 49r from Bovelles highlighting two specific lines -
- - - - - - - - This is useful for linking an annotation or explanation to a specific line on - an object surface. Any number of coordinates can be included to specify lines - which are not straight; this example shows how the first of the famous - story lines appearing at the beginning of chapter 40 of - Tristram Shandy might be encoded: - -
- - Page 152 of Tristram Shandy -
- - - - - - -

- -
-
- Combining Transcription with Facsimile - -

A digitized source document may contain nothing more than page images and a small amount of - metadata. It may also contain an encoded transcription of the pages represented, which may - either be embedded within a sourceDoc element, or supplied in parallel with - a facsimile as defined above.

-

If the transcription is regarded as a text in its own right, organized and structured - independently of its physical realization in the document or documents represented by the - facsimile, then the recommended practice is to use the text element to contain - such a structured representation, and to present it in parallel. The text element - is a sibling of the facsimile and sourceDoc elements. This approach is - illustrated in section below. Alternatively, if the transcription - is intended not to prioritize representation of the final text so much as the process by - which the document came to take its present form, or the physical disposition of its - component parts, it can be presented as an embedded transcription, as further described - in section below.

-
- Parallel Transcription - -

Suppose now that we wish to align a transcription of the page discussed in the preceding - section with particular zones. We begin by giving each relevant part of the facsimile an - identifier: - - - - - - - - - - - - - - - - - The alignment between transcription and image is made, as usual, - by means of the facs attribute: - - De Geometrie 49 - DU SON ET ACCORD DES CLOCHES ET des alleures des - chevaulx, chariotz & charges, des fontaines:& encyclie du monde, - & de la dimension du corps humain. Chapitre septiesme -

-

Le son & accord des cloches pendans en ung mesme axe, est faict en - contraires parties.

-

LEs cloches ont quasi figures de rondes - pyramides imperfaictes & irregulieres: & leur accord se - fait par reigle geometrique. Comme si les deux cloches C & D - sont pendans à ung mesme axe ou essieu A B: - je dis que leur accord se fera en contraires parties - comme voyez icy figuré. Car quand lune sera en - hault, laultre declinera embas. Aultrement si elles declinent toutes deux - ensembles en une mesme partie, elles seront discord, & sera leur - sonnerie mal plaisante à oyr.

- -

-
- -

- -

It is also possible to point in the other direction, from a surface or - zone to the corresponding text. This is the function of the start - attribute, which supplies the identifier of the element containing at least the start of - the transcribed text found within the surface or zone concerned. Thus, another way of - linking this page with its transcription would be simply - - - - - - -

- - - De Geometrie 49 - -
- - -

- - - - - - - - - - - - - - - -
- -
- Embedded Transcription -

An embedded transcription is one in which words and other written traces - are encoded as subcomponents of elements representing the physical surfaces carrying - them rather than independently of them.

-

The following elements are available for this purpose: - - - - - - - -

- -

The elements surface, surfaceGrp, and zone were introduced - above in section . When supplied within a sourceDoc - element, these elements may contain transcriptions of the written content of a source in - addition to or as an alternative to digital images of them. Such transcription may be - placed directly within the zone element, or within one or more line - elements, for cases where the writing is linear, in the sense that it is composed of - discrete tokens organized physically into groups, typically organized in a sequence - corresponding with the way they are intended to be read. Depending on the directionality - of the writing system used, this might be any combination of top-down and left to right, - or vice versa. The element line may be used to hold a complete group of such - tokens. Where, however, the lineation is not considered significant, any group of tokens - may be indicated using the zone element. The seg element described in - section may also be used to indicate smaller sequences of tokens - within zone, or line as appropriate.

- -

Returning to the preceding example, we might transcribe the content of the zone to which - we gave the identifier B49rPara2 within a sourceDoc element as - follows:

- - - - - - - - LEs cloches ont quasi - figures de rondes pyramides imperfaictes & - irregulieres: & leur accord se - fait par reigle geometrique. Comme si les deux cloches C - & D sont pendans à ung mesme axe ou essieu A B: je dis que - leur accord se fera en cõtraires parties cõme - voyez icy figuré. Car quãd lune sera en hault, laultre - declinera embas. Aultrement si elles declinent toutes deux ensembles en une - mesme partie, elles seront discord, & sera leur sonnerie - mal plaisante à oyr. - - - - -

As mentioned above, some or all of the written surfaces being transcribed may be - composed of physically distinct scraps. In the following example, taken from the Walt - Whitman Archive, two pieces of newsprint have been glued to a piece of blue paper on - which a poem is being drafted:

- - Single leaf of notes possibly related to the poem eventually titled - Sleepers. From the Walt Whitman Archive (Duke 258). -
The two pieces of newsprint might simply be regarded as special kinds of zone, - but they are also new surfaces, since they might contain additional written zones - themselves (such as the numbers in this case).

- -

Using these elements, the Whitman draft above might be encoded as follows: - - - Poem - As in Visions of — at - night — - All sorts of fancies running through - the head - - - - Spring has just set in here, and the weather[...] a steamer - 2 - - - - - "The shores on either side of the Sound are... The In- - 3 - - - - -

- -

The metamark element used in this example is further discussed below ()

- -

Note that in this example we have not included any graphic element - corresponding with the zone or surface elements identified in the - transcription. The encoder may choose to complement a transcription with graphic - representations of its source at whatever level is considered effective, or not at all. - Equally, the encoder may choose to provide only graphics without any transcription, to - provide only a structured (non-embedded) transcription, or to provide any combination of - the three.

-

This example also lacks any coordinate information to specify either the size of the two - newspaper fragments or whereabouts on the parent surface element they are to be - found, other than the reading order implicit in their sequence. Such information could - be added if desired by specifying a coordinate system on the outermost surface - element, and then indicating values within that system for each of the two fragments, as - was discussed above. We discuss this in further detail in section below.

- -
- Advanced Uses of surface and zone - -

As a child of sourceDoc, the surface element both identifies a specific area - containing writing and provides a two dimensional set of coordinates which can be used to position - and define dimensions for sub-parts of it. Furthermore, surfaces may nest within other - surfaces, as in the case of patches or other written materials attached to the main - writing surface. In the general case, the position and dimensions of such nested surfaces - will be defined using the same coordinate system as that supplied by the parent - surface element. It is also possible, however, that a different coordinate - system is required for such a nested surface, perhaps because it requires a more complex - granularity. We consider both possibilities.

- -

In the earlier examples showing nested examples we did not provide any coordinate - information, for simplicity of presentation. Suppose however, that we wish to indicate the - position and sizes of the newspaper scraps in above, relative to - the whole page. As previously noted, the four attributes ulx, uly, - lrx and lry when given on the surface element define the - coordinate scheme, rather than specifying the location of that surface. We must therefore - introduce an additional zone element, as in the following revised encoding for - this example - - - Poem - As in Visions of — at - night — - All sorts of fancies running through - the head - - - - Spring has just set in here, and the weather[...] a steamer - 2 - - - In this version of the encoding, the inner surface, corresponding - with the first piece of newsprint, inherits locational information from the zone - element that contains it. This zone, and the preceding one, which contains a sequence of - line elements, are both positioned in terms of the coordinates specified on the - outermost surface element, which defines a scale running from 0 to 50 in either - direction. On that scale, the line elements occupy a rectangle with coordinates - (1,1,10,10), while the nested surface occupies a rectangle with coordinates - (4,4,20,20).

-

Now suppose that we wish to define a finer scale grid for the newspaper patch, perhaps - because we wish to localize zones within it with greater accuracy. To do this we will need - to specify the position of the nested surface as in the previous example, but also to - define the new coordinate system. We accomplish this as follows: - - - Poem - - the head - - - - Spring has just set in here, and the - weather [...] a steamer - - - As before, the second zone defines the position and size of the - newspaper patch itself in terms of a coordinate system running from 0 to 50 on both X and Y - axes. The nested surface element however defines a new scale for all of its - components, running from 0 to 100 on both X and Y axes. The position of the nested zone - containing the text Spring ... steamer is now given in terms of this - scale.

- -

All of the examples so far given have involved rectangular zones, for clarity of - exposition. As noted above, the points attribute may be used to define - non-rectangular zones as a series of points. For example, in the last of the Whitman - examples discussed in section above, we might wish to record the - exact shape of the zone containing the metamark Entered. Since this - is not a rectangular zone, we use the points attribute to indicate the points - defining a polygon which contains it. The values used are expressed in terms of a - coordinate space running from 0 to 229 in the X dimension, and 0 to 160 in the Y dimension.

- - - - - - - - -

In exactly the same way, we may wish to identify the curved zone in the following image - containing the word Northamptonshire:

- - Gravestone of Private Moulds -
This curved zone might be encoded in the following way: - - - - - -

-

Finally, it should be noted that a zone does not need to be entirely contained - within the two-dimensional space defined by its parent surface. For example, we might wish - to encode the example in above not as a surface representing the - whole of the two page spread, but as a surface representing only the written part of this - opening. The written part appears 50 units from the left of the image and 20 units from the - top, while the bottom right corner of the written part appears 400 units from the left of - the image, and 280 units from the top. We therefore define the written surface within this - image as follows: - - - - To describe the whole image, we will now need to define a zone of - interest which represents an area larger than this surface. Using the same coordinate - system as that defined for the surface, its coordinates are 0,0,500,321. This - zone of interest can be defined by a zone element, within which we can place the - uncropped graphic: - - - - - -

- -
-
- -
- -
- Scope of Transcriptions - -

When transcribing a primary source, whether using text or sourceDoc, - scholars may wish to record information concerning - individual readings of letters, words, or larger units.They - may also wish to include other editorial material, such as comments on the status or - possible origin of particular readings, corrections, or text supplied to fill lacunae.

- -

Such elements may also be used for digital transcriptions in which the object is not to - represent a finished text, but rather to represent the creative process, as evidenced by - different layers or traces of writing in one or more documents. - Transcriptions of this kind are closely focussed on the physical appearance of specific - documents, needing to distinguish the traces of different writing activities on them, such - as additions and deletions but also other indications of how the writing is to be read, - such as indications of transposition, re-affirmation of writing which has been deleted, and - so on. Such distinctions are considered of particular importance when dealing with - authorial manuscripts, but are also relevant in the case of historical sources such as - charters or other legal documents.

- -

In either case, it is customary in transcriptions to register certain features of the - source, such as ornamentation, underlining, deletion, areas of damage and lacunae. This - chapter provides ways of encoding such information: - methods of recording editorial or other alterations to the text, such as expansion - of abbreviations, corrections, conjectures, etc. (section ) - methods of describing important extra-linguistic phenomena in the source: unusual - spaces, lines, page and line breaks, changes of manuscript hand, etc. (section ) - methods of representing aspects of layout such as spacing or lines - - methods of representing material such as running heads, catch-words, and the like - (section ) -

- - -

The remainder of this chapter describes a model for encoding such transcriptions, in which - elements such as mod, del, etc. are used to mark writing traces and their - functions within the document. Each such element can be assigned to one or more - editorially-defined modification groups, termed a change, by means of a global - change attribute, which references a definition for the modification group - concerned, typically provided within the TEI header creation element; see further - . The transcription itself may be embedded within the - elements surface and zone described in section , or - provided in parallel within a text element. Within a zone, the - transcription may be organized topographically in terms of lines of writing, using the - line element, or in terms of further nested zones, or as a combination of the - two ().

- - - -

These recommendations are not intended to meet every transcriptional circumstance likely to - be faced by any scholar. Rather, they should be regarded as a base which can be elaborated - if necessary by different scholars in different disciplines

- - -

As a rule, all elements which may be used in the course of a transcription of a single - witness may also be used in a critical apparatus, i.e. within the elements proposed in - chapter . This can generally be achieved by nesting a particular reading - containing tagged elements from a particular witness within the rdg element in an - app structure.

-

Just as a critical apparatus may contain transcriptional elements within its record of - variant readings in various witnesses, one may record variant readings in an individual - witness by use of the apparatus mechanisms app and rdg. This is discussed - in section .

- -
- Altered, Corrected, and Erroneous Texts - -

In the detailed transcription of any source, it may prove necessary to record various - types of actual or potential alteration of the text: expansion of abbreviations, - correction of the text (either by author, scribe, or later hand, or by previous or - current editors or scholars), addition, deletion, or substitution of material, and - similar matters. The sections below describe how such phenomena may be encoded using - either elements defined in the core module (defined in chapter ) or - specialized elements available only when the module described in this chapter is - available.

- -
- Core Elements for Transcriptional Work -

In transcribing individual sources of any type, encoders may record corrections, - normalizations, additions, and omissions using the elements described in section . Representation of abbreviations and their expansions may also - involve use of elements described in section . Elements - particularly relevant to this chapter include: - - - - - - - - - -

-

All of these elements bear additional attributes for specifying who is responsible - for the interpretation represented by the markup, and the associated certainty. In - addition, some of them bear an attribute allowing the markup to be categorized by - type and source. - - - - - The specific aspect of the markup described by these attributes differs - on different elements; for further discussion, see the relevant sections below, - especially section .

-

The following sections describe how the core elements just named may be used in the - transcription of primary source materials.

-
- -
- Abbreviation and Expansion - -

The writing of manuscripts by hand lends itself to the use of abbreviation to shorten - scribal labour. Commonly occurring letters, groups of letters, words, or even whole - phrases, may be represented by significant marks. This phenomenon of manuscript - abbreviation is so widespread and so various that no taxonomy of it is here - attempted. Instead, methods are shown which allow abbreviations to be encoded using - the core elements mentioned above.

-

A manuscript abbreviation may be viewed in two ways. One may transcribe it as a - particular sequence of letters or marks upon the page: thus, a p with a bar - through the descender, a superscript hook, a macron. One may - also interpret the abbreviation in terms of the letter or letters it is seen as - standing for: thus, per, re, n. Both of these views are - supported by these Guidelines.

- -

In many cases the glyph found in the manuscript source also exists in the Unicode - character set: for example the common Latin brevigraph ⁊, standing for - et and often known as the Tironian et - can be directly represented in any XML document as the Unicode character with code - point U+204A (see further and ). In cases where it does not, these Guidelines recommend use of the g - element provided by the gaiji module described in - chapter . This module allows the encoder great flexibility both in - processing and in documenting non-standard characters or glyphs, including the - ability to provide detailed documentation and images for them.

- -

These two methods of coding abbreviation may also be combined. An encoder may record, - for any abbreviation, both the sequence of letters or marks which constitutes it, and - its sense, that is, the letter or letters for which it is believed to stand. For - example, in the following fragment the phrase euery persone is - represented by a sequence of abbreviated characters:

- - Detail from fol. 126v of Bodleian MS Laud Misc 517 -
These lines may be transcribed directly, using the g element to - indicate the two brevigraphs as follows: euery persone that loketh after heuen hath a place in - this ladder - - - - - - - - Note that in each case the g element may contain a - suggested replacement for the referenced brevigraph; this is purely advisory however, - and may not be appropriate in all cases. The referenced character definitions may be - located elsewhere in this or some other document, typically forming part of a - charDecl element, as described in .

- -

The transcriber may also wish to indicate that, because of the presence of these - particular characters, the two words are actually abbreviations, by using the - abbr element: euery - persone ... Alternatively, the - transcriber may choose silently to expand these abbreviations, using the - expan element: euery - persone ... And, of course, the choice element - can be used to show that one encoding is an alternative for the other: eueryeuery -

-

When abbreviated forms such as these are expanded, two processes are carried out: - some characters not present in the abbreviation are added (always), and some - characters or glyphs present in the abbreviation are omitted or replaced (often). For - example, when the abbreviation Dr. is expanded to - Doctor, the dot in the abbreviation is removed, and the - letters octo are added. Where detailed markup of abbreviated - words is required, these two aspects may be marked up explicitly, using the following - elements: - - - Using these elements, a transcriber may indicate the status of the - individual letters or signs within both the abbreviation and the expansion. The - am element surrounds characters or signs such as tittles or tildes, used - to indicate the presence of an abbreviation, which are typically removed or replaced - by other characters in the expanded form of the abbreviation: euy - sone ... while the ex - element may be used to indicate those characters within the expansion which are not - present in the abbreviated form. euery - persone ... The content of the abbr - element should usually include the whole of the abbreviated word, while the - expan element should include the whole of its expansion. If this is not - considered necessary, the am and ex elements may be used within a - choice element, as in this example: euery persone ... -

-

As implied in the preceding discussion, making decisions about which of these various - methods of representing abbreviation to use will form an important part of an - encoder's practice. As a rule, the abbr and am elements should be - preferred where it is wished to signify that the content of the element is an - abbreviation, without necessarily indicating what the abbreviation may stand for. The - ex and expan elements should be used where it is wished to - signify that the content of the element is not present in the source but has been - supplied by the transcriber, without necessarily indicating the abbreviation used in - the original. The decision as to which course of action is appropriate may vary from - abbreviation to abbreviation; there is no requirement that the same system be used - throughout a transcription, although doing so will generally simplify processing. The - choice is likely to be a matter of editorial policy. If the highest priority is to - transcribe the text literatim (letter by letter), while indicating - the presence of abbreviations, the choice will be to use abbr or am - throughout. If the highest priority is to present a reading transcription, while - indicating that some letters or words are not actually present in the original, the - choice will be to use ex or expan throughout.

-

Further information may be attached to instances of these elements by the - note element, on which see section , and by use of - the resp and cert attributes. In this instance from the English - Brut, a note is attached to an editorial expansion of the tail on - the final d of good to goode: For alle the while - that I had goode I was welbeloued - Then the note: The stroke added to - the final d could signify the plural ending (-es, -is, -ys>) but the - singular goode was used with the meaning property, - wealth, at this time (v. examples quoted in OED, sb. Good, C. 7, b, - c, d and 8 spec.) The editor might declare a degree of certainty - for this expansion, based on the OED examples, and state the responsibility for the - expansion: For alle the while that I - had goode I was welbeloued The value - supplied for the resp attribute should point to the name of the editor - responsible for this and possibly other interventions; an appropriate element - therefore might be a respStmt element in the header like the following: - - - Editorial emendations - Malcom Parkes - Observe that the cert and resp - attributes are used with the ex element only to indicate confidence in the - content of the element (i.e. the expansion), and responsibility for suggesting this - expansion respectively.

-

The choice element may be used to indicate that the proposed expansion is - one way of encoding what might equally well be represented as an abbreviation, - represented by the hooked D, as follows: For alle the while that I had - gooɗ - goode I was - welbeloued If it is desired to express aspects of certainty and - responsibility for some other aspect of the use of these elements, then the - mechanisms discussed in chapter should be used. See also for discussion of the issues of certainty and responsibility in - the context of transcription.

- -

If more than one expansion for the same abbreviation is to be recorded, multiple - notes may be supplied. It may also be appropriate to use the markup for critical - apparatus; an example is given in section .

-
- - -
- Correction and Conjecture - -

The sic, corr, and choice elements, defined in the core module should be used to indicate passages deemed in - need of correction, or actually corrected, during the transcription of a source. For - example, in the manuscript of William James's A Pluralistic Universe - as edited by Fredson Bowers (Cambridge: Harvard University Press, 1977), a sentence - first written One must have lived longer with this system, to - appreciate its advantages. has been modified by James to begin But One must - ..., without the initial capital O having been reduced to lowercase. This - non-standard orthography could be recorded thus: But One must have lived - ... or corrected: But - one must have lived ... or the two possibilities might be - represented as a choice: But - Oneone must have lived - ...

-

Similarly, in this example from Albertus Magnus, both a manuscript error - angues and its correction augens are - registered within a choice element: Nos autem iam - ostendimus quod nutrimentum et - anguesaugens. -

-

Note that the corr element is used to provide a corrected form which is - not present in the source; in the case of a correction made in the - source itself, whether scribal, authorial, or by some other hand, the add, - del, and subst elements described in - should be used.

-

The sic element is used to mark passages considered by the transcriber to be - erroneous; in such cases, the corr element indicates the transcriber's - correction of them. Where the transcriber considers that one or more words have been - erroneously omitted in the original source and corrects this omission, the - supplied element discussed in should be used in - preference to corr. Thus, in the following example, from George Moore's - draft of additional materials for Memoirs of My Dead Life, the - transcriber supplies the word we omitted by the author: You see that I avoid - the word create for we create nothing we develope. -

-

As with expan and abbr, the choice as to whether to record simply - that there is an apparent error, or simply that a correction has been applied, or to - record both possible readings within a choice element is left to the - encoder. The decision is likely to be a matter of editorial policy, which might be - applied consistently throughout or decided case by case. If the highest priority is - to present an uncorrected transcription while noting perceived errors in the - original, the choice will typically be to use only sic throughout. If the - highest priority is to present a reading transcription, while indicating that - perceived errors in the original have been corrected, the choice will be to use only - corr throughout.

- -

Further information may be attached to instances of these elements by the - note element and resp and cert attributes. - Instances of these elements may also be classified according to any convenient - typology using the type attribute.

-

For example, consider the following encoding of an emendation in the Hengwrt - manuscript proposed by E. Talbot Donaldson: Telle me also, to what conclusioun Were - membres maad, of generacioun And of so parfit wis a wightwright ywroght? - This emendation of the Hengwrt copy text, based on a Latin - source and on the reading of three late and usually unauthoritative - manuscripts, was proposed by E. Talbot Donaldson in - Speculum 40 (1965) 626–33. - The note element discussed in may be used to - give a more detailed discussion of the motivation for or scope of a correction. If - linked by means of a pointer (as in this example) it may be located anywhere - convenient within the transcription; typically all detailed notes will be collected - together in a separate div element in the back. Alternatively, the - pointer may be omitted, and the note placed immediately adjacent to the - element being annotated. The advantage of the former solution is that it permits the - same annotation to refer to several corrections, by supplying more than one pointer - in the target attribute of the note, as shown in the example - below.

-

The attribute cert may be used to indicate the degree of confidence - ascribed by the encoder to the proposed emendation on a broad scale: high, medium, or - low. The attribute resp is used to indicate who is responsible for the - proposed emendation. Its value is a pointer, which will typically indicate a - respStmt or name element in the header of the transcribed - document, but can point anywhere, for example to some online authority file. Using - these two attributes, the corr element presented above might usefully be - enhanced as follows: - - E Talbot Donaldson - And of so parfit wis a wightwright ywroght?

- -

As remarked above, where the same annotation applies to several corrections, this may - be represented by supplying multiple pointers on the note. Consider for example such - corrections as the following, in Dudo of S. Quentin. Parkes cites two cases in this - manuscript of the same phenomenon: quamuis mensiners que nutu dei gesta - sunt ... unde esset uiriliter uegetatanegata which may be - described as follows: Substitution of a more familiar word which resembles - graphically what the scribe should be copying but which does not make sense in - the context. -

-

The target attribute on the note element indicates the - choice elements which exemplify this kind of scribal error. This - necessitates the addition of an identifier to each choice element. However, - if the number of corrections is large and the number of notes is small, it may well - be both more practical and more appropriate to regard the collection of annotations - as constituting a typology and then use the type attribute. Suppose that - the note given above is one of half a dozen possible kinds of corrected phenomena - identified in a given text; others might include, say, repetition of a word from - the preceding line, etc. The type attribute on the corr - element can be used to specify an arbitrary code for the particular kind of - correction (or other editorial intervention) identified within it. This code can be - chosen freely and is not treated as a pointer. quamuis mensiners que nutu dei gesta sunt ... unde - esset uiriliter uegetatanegata Note that this encoding - might be extended to include a range of possible corrections: quamuis mensinersinres que - nutu dei gesta sunt ... In addition, the conscientious encoder will - provide documentation explaining the circumstances in which particular codes are - judged appropriate. A suitable location for this might be within the - correction element of the encodingDesc of the header, which - might include a list such as the following: - -

The following codes are used to categorize corrections identified in this - transcription: - - Substitution of a more familiar word which resembles graphically - what the scribe should be copying but which does not make sense in the - context. - -

A subtype attribute may be used - in conjunction with the type for subclassification purposes: the above - examples might thus be represented as choice type="substitution" - subtype="graphicResemblance" for example.

-

For a given project, it may well be desirable to limit the possible values for the - type or subtype attributes automatically. This is easily - done but requires customization of the TEI system using techniques described in , in particular , which should be consulted - for further information on this topic.

-

When making a correction in a source which forms part of a textual tradition attested - by many witnesses, a textual editor will sometimes use a reading from one witness to - correct the reading of the source text. In the general case, such encoding is best - achieved with the mechanisms provided by the module for textual criticism described - in chapter . However, for simple cases, the source - attribute of the corr element may suffice. In the passage from Chaucer's - Wife of Bath's Tale mentioned above, Parkes proposes to emend the - problematic word wight to wyf which is - the reading found in the Cambridge manuscript Gg.1. 27. This may be simply - represented as follows: And of so - parfit wis a wightwyf ywroght? The value of the source - attribute here is, like the value of the resp attribute, a pointer, in - this case indicating the manuscript used as a witness. Elsewhere in the transcribed - text, a list of witnesses used in this text will be given, one of which has an - identifier Gg. Each witness will be represented either by a - witness element (see ) or more fully by an - msDesc element (see ): - - - Cambridge - University Library - Gg.1. 27 - - - -

- -

The app element described in chapter provides a more - powerful way of representing all three possible readings in parallel: And of so parfit wis a - wight - wright - wyf -

-

This encoding simply records the three readings found in the various traditions, and - gives (by means of the wit attribute) an indication of the witnesses - supporting each. If the resp attribute were supplied on the rdg - element, it would indicate the person responsible for asserting that the manuscript - indicated has this reading, who is not necessarily the same as the person responsible - for asserting that this reading should be used to correct the others. Editorial - intervention elements such as corr can however be nested within a - rdg to provide this additional information: And of so parfit wis a - wight - wright - wyf - This encoding asserts that the reading wyf - found in Gg is regarded as a correction by Parkes.

- -

Like the resp attribute, the cert attribute may be used with - both corr and rdg elements. When used on the rdg element, - these attributes indicate confidence in and responsibility for identifying the - reading within the sources specified; when used on the corr element they - indicate confidence in and responsibility for the use of the reading to correct the - base text. If no other source is indicated (either by the source - attribute, or by the wit attribute of a parent rdg), the reading - supplied within a corr has been provided by the person indicated by the - resp attribute.

- -

If it is desired to express certainty of or responsibility for some other aspect of - the use of these elements, then the mechanisms discussed in chapter may be found useful. See also for further discussion of the - issues of certainty and responsibility in the context of transcription.

-
- -
- Additions and Deletions - -

Additions and deletions observed in a source text may be described using the - following elements: - - - - - Of these, add and del are included in the core module, - while addSpan and delSpan are available only when using the module - defined in this chapter. These particular elements are members of the att.spanning class, from which they inherit the following - attribute: - - -

- -

Further characteristics of each addition and deletion, such as the hand used, its - effect (complete or incomplete, for example), or its position in a sequence of such - operations may conveniently be recorded as attributes of these elements, all of which - are members of the att.transcriptional class: - - -

- - -

As described in section , the add element is used to - record any manuscript addition observed in the text, whether it is considered to be - authorial or scribal. In the autograph manuscript of Max Beerbohm's The Golden - Drugget, the author's addition of do ever may be - recorded as follows, with the hand attribute indicating that the addition - was Beerbohm's by referencing a handNote element defined elsewhere in the - document (see further ): Some things are best - at first sight. Others — and here is one of them — do ever - improve by recognition [...] Max Beerbohm - holograph - -

- -

The del element is used to record manuscript deletions in a similar way. In - the autograph manuscript of D. H. Lawrence's Eloi, Eloi, lama - sabachthani the author's deletion of my may be - recorded as follows. In this case, the hand attribute indicating that the - deletion was Lawrence's is complemented by a rend attribute indicating - that the deletion was by strike-through: For I hate this my body, which is so dear to me ... - D H Lawrence holograph -

- - -

If deletions are classified systematically, the type attribute may be - useful to indicate the classification; when they are classified by the manner in - which they were effected, or by their appearance, however, this will lead to a - certain arbitrariness in deciding whether to use the type or the - rend attribute to hold the information. In general, it is recommended - that the rend attribute be used for description of the appearance or - method of deletion, and that the type attribute be reserved for higher - level or more abstract classifications.

- -

The place attribute is also available to indicate the location of an - addition. For example, consider the following passage from a draft letter by Robert - Graves:

- - Draft letter from Robert Graves to Desmond Flower, 17 Dec 1938 (detail). - -
At the end of this extract, the writer inserts the word cant, above - the line, with a stroke to indicate insertion. Assuming that we have previously - defined the identifier RG somewhere: - - - - - - , this extract might now be encoded as follows: The O.E.D. is not a - dictionary so much as a corpus of precedents in the: - current, obsolete, cant, cataphretic and - nonce-words are all included. A little earlier in the same extract, - Graves writes for an abridgement above the line, and then deletes it. This may - be encoded similarly: As for 'significant artist.' You quote the O.E.D for an abridgement in explanation... - Similarly, in the margin, the word Norton has been added and then - deleted: You - quote the Norton O.E.D... - The word O.E.D. in this first sentence has also clearly been the result of - some redrafting: it may be that Graves started to write Oxford, and then - changed it; it may be that he inserted other punctuation marks between the letters - before replacing them with the centre dots used elsewhere to represent this acronym. - We do not deal with these possibilities here, and mention them only to indicate that - any encoding of manuscript material of this complexity will need to make decisions - about what is and is not worth mentioning.

- - - - - -

An encoder may also wish to indicate that an addition replaces a specific deletion, - that is to encode a substitution as a single intervention in the text. This may be - achieved by grouping the addition and deletion together within a subst - element. At the end of the passage illustrated above, Graves first writes It is - the expressed..., then deletes It is, and substitutes an uppercase T at - the start of the. ... are all included. It is - Tthe expressed The use of this - element and of the seq attribute to indicate the order in which - interventions such as deletions are believed to have occurred are further discussed - in section below.

- -

The add and del elements defined in the core module suffice only - for the description of additions and deletions which fit within the structure of the - text being transcribed, that is, which each deletion or addition is completely - contained by the structural element (paragraph, line, division) within which it - occurs. Where this is not the case, for example because an individual addition or - deletion involves several distinct structural subdivisions, such as poems or prose - items, or otherwise crosses a structural boundary in the text being encoded, special - treatment is needed. The addSpan and delSpan elements are provided - by this module for that purpose. (For a general discussion of the issue see further - ).

- -

In this example of the use of addSpan, the insertion by Helgi Ólafsson of a - gathering containing four neo-Eddic poems into Lbs 1562 4to is - recorded as follows. A handNote - element is first declared, within the header of the document, to associate the - identifier heol with Helgi. Each of the added poems is encoded as a - distinct div element. In the body of the text, an addSpan element - is placed to mark the beginning of the span of added text, and an anchor is - used to mark its end. The hand attribute on the addSpan element - ascribes responsibility for the addition to the manuscript to Helgi, and the - spanTo attribute points to the end of the added text: - - -

- -
-
-
-
- -
-

-

The delSpan element is used in the same way. An authorial manuscript will - often contain - several - occasions where sequences of whole lines are marked for deletion, either by boxes or - by being struck out. If the encoder is marking up individual verse lines with the - l element, such deletions are problematic: deletion of two consecutive - lines should be regarded as a single deletion, but the del element must be - properly nested within a single l element. The delSpan element - solves this problem: - Flowed up the hill and down King William Street, - - To where Saint Mary Woolnoth kept the time, - With a dead sound on the final stroke of nine. - - There I saw one I knew, and stopped him, crying "Stetson!... -

-

It is also often the case that deletions and additions may themselves contain other - deletions and additions. For example, in Thomas Moore's autograph of the second - version of Lalla Rookh two lines are marked for omission by vertical - strike-through. Within the first of the two lines, the word - upon has also been struck out, and the word - over has been added: - Tis moonlight - upon - over Oman's sky - Her isles of pearl look lovelily In this - case the anchor and delSpan have been placed within the structural - elements (the ls) rather than between, as in the previous example. This is - to indicate that placement of these empty elements is arbitrary.

-

The text deleted must be at least partially legible, in order for the encoder to be - able to transcribe it. If all of part of it is not legible, the gap element - should be used to indicate where text has not been transcribed, because it could not - be. The unclear element described in section may be - used to indicate areas of text which cannot be read with confidence. See further - section and section .

-
- -
- Substitutions - -

Substitution of one word or phrase for another is perhaps the most common of all - phenomena requiring special treatment in transcription of primary textual sources. It - may be simply one word written over the top of another, or deletion of one word and - its replacement by another written above it by the same hand on the same occasion; - the deletion and replacement may be done by different hands at different times; there - may be a long chain of substitutions on the same stretch of text, with uncertainty as - to the order of substitution and as to which of many possible readings should be - preferred.

-

As we have shown, the simplest method of recording a substitution is simply to record - both the addition and the deletion. However, when the module defined by this chapter - is in use, additional elements are available to indicate that the encoder believes - the addition and the deletion to be part of the same intervention: a substitution. - - - Using the subst element, the example at the end of the last - section might be encoded as follows: - Tis moonlight - uponover Oman's sky - Her isles of pearl look lovelily Since - the purpose of this element is solely to group its child elements together, the order - in which they are presented is not significant. When both deletion and addition are - present, it may not always be clear which occurs first: using the seq - attribute is a simple way of resolving any such ambiguities.

- -

For example, returning to the example from William James, in a passage first written - out by James as One must have lived longer with this system, to appreciate its - advantages, the word this is first replaced by - such a and this is then replaced by - a.The manuscript contains several - other substitutions, ignored here for the sake of clarity. This may be - encoded as follows, representing the two changes as a sequence of additions and - deletions: One must have lived longer - with this - such a - a system, to appreciate its advantages. Note - the nesting of an add element within a del to record text first - added, then deleted in the source. The numbers assigned by the seq - attribute may be used to identify the order in which the various additions and - deletions are believed by the encoder to have been carried out, and thus provide a - simple method of supporting the kind of genetic textual - criticism typified by (for example) Hans Walter Gabler's work on the reconstruction - of the overlay levels implicit in the manuscripts of James - Joyce's Ulysses. A fuller and more complex way of supporting such an - approach is discussed in .

- -

A special case of a substitution may consist of a superfluous word - or phrase that is silently replaced by some addition. E.g. a scribe - abandons a word (without indicating it should be deleted), and then - writes a replacement word immediately after. Here the encoder may - interpret this as an unmarked deletion which can - then be combined with a corresponding addition to a substitution.

- -

The case of a single substitution or scribal correction that involves non-contiguous - addition and deletion can be handled by using the substJoin element to make - an explicit connection between one or more add and del elements. In - the following example from Thomas Moore's Lalla Rookh, the deletion and addition are - not contiguous: they are separated by the word thus, which is not part of the - scribal intervention being marked. Because of this intervening text, it would be - inappropriate to use subst to group this add and del. - substJoin allows the encoder to indicate that additions and deletions - separated in this way are part of a single scribal intervention: While pondering thus she mus'd, her pinions - fann'd - Note that, unlike subst, the placement of the substJoin is - arbitrary. It may occur before or after the relevant add and del - elements.

- -

As a more complex example, consider the following passage: -

- - Detail from Dulce et decorum est autograph manuscript in the - English Faculty Library, Oxford University. -
This passage might be encoded as follows: - And towards our distant rest began to trudge, - Helping the worst amongst usDragging the worst amongt - us, who'd no boots - But limped on, blood-shod. All went lame; half-all blind; - Drunk with fatigue ; deaf even to the hoots - Of tired, outstripped fif five-nines that dropped - behind. In this representation, - the authorial slip (amongt for - amongst) is retained without comment. - the other two authorial corrections are marked as substitutions, each - combining a deletion and an addition. - the false start fif in the last line is simply marked - as a deletion; - -

-

The app element presented in chapter provides similar - facilities, by treating each state of the text as a distinct reading. The - rdg element has a varSeq attribute which may be used in the - same way as the seq attribute to indicate the preferred sequence. The - James example above might thus be represented as follows: One must have lived longer with - this - such a - a - system, to appreciate its advantages. -

-
- -
- Cancellation of Deletions and Other Markings -

An author or scribe may mark a word or phrase in some way, and then on reflection - decide to cancel the marking. For example, text may be marked for deletion and the - deletion then cancelled, thus restoring the deleted text. Such cancellation may be - indicated by the restore element: - -

-

This element bears the same attributes as the other transcriptional elements. These - may be used to supply further information such as the hand in which the restoration - is carried out, the type of restoration, and the person responsible for identifying - the restoration as such, in the same way as elsewhere.

-

Presume that Lawrence decided to restore my to the phrase of - Eloi, Eloi, lama sabachthani first written For I hate this my - body, with the my first deleted then restored by - writing stet in the margin. This may be encoded: For I hate this my body

-

Another feature commonly encountered in manuscripts is the use of circles, lines, or - arrows to indicate transposition of material from one point in the text to another. - No specific markup for this phenomenon is proposed at this time. Such cases are most - simply encoded as additions at the point of insertion and deletions at the point of - encirclement or other marking.

-
- -
- Text Omitted from or Supplied in the Transcription -

Where text is not transcribed, whether because of damage to the original, or because - it is illegible, or for some other reason such as editorial policy, the gap - core element may be used to register the omission; where such text is transcribed, - but the editor wishes to indicate that they consider it to be superfluous, for - example because it is an inadvertent scribal repetition or an interpolation from - another source, the surplus element may be used in preference. Where the - editor believes text to be interpolated but genuine, the secl element may be - used instead. Where text not present in the source is supplied (whether conjecturally - or from other witnesses) to fill an apparent gap in the text, the supplied - element may be used. - - - - -

-

By its nature, the gap element has no content. It marks a point in the text - where nothing at all can be read, whether because of authorial or scribal erasure, - physical damage, or any other form of illegibility. Its attributes allow the encoder - to specify the amount of text which is illegible in this way at this point, using any - convenient units, where this can be determined. For example, in the Beerbohm - manuscript of The Golden Drugget cited above, the author has erased a - passage amounting about 10 cm in length by inking over it completely: Others —and here is one of - them...

-

In an autograph letter of Sydney Smith now in the Pierpont Morgan library three words - in the signature are quite illegible: I am dr Sr yr Sydney Smith The degree of precision attempted when measuring the size - of a gap will vary with the purpose of the encoding and the nature of the material: - no particular recommendation is made here.

- -

As noted above, the gap element should only be used where text has not been - transcribed. If partially legible text has been transcribed, one of the elements - damage and unclear should be used instead (these elements are - described in section ); if the text is legible and has been - transcribed, but the editor wishes to indicate that they regard it is superfluous or - redundant, then the element surplus may be used in preference to the core - element sic used to indicate text regarded as erroneous.

- -

Amongst the many examples cited in Hans Krummrey & Silvio Panciera's classic text - on the editing of epigraphic inscriptions is the following. In a late classical - inscription, the form dedikararunt is encountered. The editor - may choose any of the following three possibilities:

- - mark this as an erroneous form - dedikararunt - - additionally supply a corrected form - dedikararunt - dedikarunt - - - indicate that the erroneous form contains surplus characters which the editor - wishes to suppress dedikararunt - - -

The surplus element may also be used to mark up interpolations, as in the - following example taken from a 13th century Italian source: - a darmi morte, poi m'avete preso a - tradimento - sì com' l'uccellator prende l'uccello - - e lettere dintorno che diriano in questa - guisa - Più v'amo, dëa, che non faccio Deo - The words marked as surplus here are metrically inconsistent with - the rest and have been marked by the editor as such.

- -

In the case of an interpolation which the editor regards as genuine (i.e. written by - the author in question), but out of its original place, the secl element - should be used instead of surplus. For example: - - - - Great praise and thanks be to Perfidy as she - deserves, since by our swindles, tricks, and clever moves, relying - on the daring of our shoulder blades and the excellence of our - forearms who went against cattle-prods, hot iron-blades, - crosses and shackles, neck-irons, chains, prisons, collars, fetters, - and yokes, the fiercest painters fully acquainted with our backs - who have often before put scars on our shoulder blades - ... - - - - The final line is bracketed in the Loeb edition, with a note: versum secl. - Bothe, meaning Bothe regarded this line as Plautine, but probably - interpolated. It is easy to see how the line might have crept in as a gloss on the - metaphor in the previous line.

- -

If some part of the source text is completely illegible or missing, an encoder may - sometimes wish to supply new (conjectural) material to replace it. This conjectural - reading is analogous to a correction in that it contains text provided by the encoder - and not attested in the source. This is not however a correction, since no error is - necessarily present in the original; for that reason a different element - supplied should be used. If another (imaginary) copy of the letter above - preserved the signature as reading I am dear Sir your very humble Servt Sydney - Smith, the text illegible in the autograph might be supplied in the - transcription: I am dr Sr yr - very humble - Servt Sydney Smith Here the source and - resp attributes are used, as elsewhere, to indicate respectively the - sigil of a manuscript from which the supplied reading has been taken, and the - identifier of the person responsible for deciding to supply the text. If the - source attribute is not supplied, the implication is that the encoder - (or whoever is indicated by the value of the resp attribute) has supplied - the missing reading. Both gap and supplied may be used in - combination with unclear, damage, and other elements; for - discussion, see section .

-
-
- -
- Hands and Responsibility -

This section discusses in more detail the representation of aspects of responsibility - perceived or to be recorded for the writing of a primary source. These include points at - which one scribe takes over from another, or at which ink, pen, or other characteristics - of the writing change. A discussion of the usage of the hand, - resp, and cert attributes is also included.

-
- Document Hands - -

For many text-critical purposes it is important to signal the person responsible (the - hand) for the writing of a whole document, a stretch of text within a - document, or a particular feature within the document. A hand, as the name suggests, - need not necessarily be identified with a particular known (or unknown) scribe or - author; it may simply indicate a particular combination of writing features - recognized within one or more documents. The examples given above of the use of the - hand attribute with coding of additions and deletions illustrate this.

- -

The handNote element is used to provide information about each hand - distinguished within the encoded document. - - -

- -

A handNote element, with an identifier given by its xml:id - attribute, may appear in either of two places in the TEI header, depending on which - modules are included in a schema. When the transcr - module defined by the present chapter is used, the element handNotes is - available, within the profileDesc element of the TEI header, to hold one or - more handNote elements. When the msdescription - module defined in chapter is included, the handDesc - element described in also becomes available as part of a - structured manuscript description. The encoder may choose to place handNote - elements identifying individual hands in either location without affecting their - accessibility since the element is always addressed by means of its xml:id - attribute. The handDesc element may be more appropriate when a full - cataloguing of each manuscript is required; the handNotes element if only a - brief characterization of each hand is needed. It is also possible to use the two - elements together if, for example, the handDesc element contains a single - summary describing all the hands discursively, while the handNotes element - gives specific details of each. The choice will depend on individual encoders' - priorities.

- -

As shown above, the hand attribute is available on several elements to - indicate the hand in which the content of the element (usually a deletion or - addition) is carried out. The handShift element may also be used within the - body of a transcription to indicate where a change of hand is detected for whatever - reason. - - -

-

A handShift element can be used to - indicate a change of hand even within an element with a hand attribute. The text following the handShift - must be considered to be in the new hand. -

-

Both handShift and handNote are members of the att.handFeatures class, and thus share the following attributes: - - -

- -

A single hand may employ different writing styles and inks within a document, or may - change character. For example, the writing style might shift from anglicana to - secretary, or the ink from blue to brown, or the character of the hand may - change. Simple changes of this kind may be indicated by assigning a new value to the - appropriate attribute within the handShift element. It is for the encoder to - decide whether a change in these properties of the writing style is so marked as to - require treatment as a distinct hand.

-

Where such a change is to be identified, the new attribute indicates the - hand applicable to the material following the handShift. The sequence of - such handShift elements will often, but not necessarily, correspond with the - order in which the material was originally written. Where this is not the case, the - facilities described in section may be found helpful.

- -

As might be expected, a single hand may also vary renditions within the same writing - style, for example medieval scribes often indicate a structural division by - emboldening all the words within a line. Such changes should be indicated by use of - the rend attribute, in the same manner as underlining, emboldening, font - shifts, etc. are represented in transcription of a printed text, rather than by - introducing a new handShift element.

- -

In the following example there is a change of ink within a single hand. This is - simply indicated by a new value for the medium attribute on the - handShift element: When wolde the cat dwelle in his ynne - - And if the cattes skynne be slyk and - gaye

- -

In the following example, the encoder has identified two distinct hands within the - document and given them identifiers h1 and h2, by means of the - following declarations included in the document's TEI header: - - Carefully written - with regular descenders - Unschooled - scrawl - - -

-

Then the change of hand is indicated in the text: ... and that good Order Decency and regular worship may be once - more introduced and Established in this Parish according to the Rules and - Ceremonies of the Church of England and as under a good Consciencious and sober - Curate there would and ought to be and for that - purpose the parishioners pray

- -

When a more precise or nuanced discussion of the writing in a manuscript is required, - the handNote and scriptNote elements discussed in should be used. Either element may serve as the target for a - handShift.

- -
- -
- Hand, Responsibility, and Certainty Attributes - -

The hand and resp attributes have similar, but not identical, - meanings. Observe their distinctive uses in the following encoding of the William - James passage mentioned above in section . In this example, the - But inserted by James is tagged as an add, and the - consequent editorial correction of One to - one treated separately: But - Oneone must have lived ... - - editorial changes - Fredson Bowers - - - authorial changes - William James - - As in this example, hand should be reserved for indicating the - hand of any form of marking—here, addition but also deletion, correction, annotation, - underlining, etc.—within the primary text being transcribed. The scribal or authorial - responsibility for this marking may be inferred from the value of the hand - attribute. The value of the hand attribute should be a pointer to a hand - identifiers typically declared in the document header but potentially in another - document or repository (see section ).

-

The resp attribute, by contrast, indicates the person responsible for - deciding to mark up this part of the text with this particular element. In the case - of the add element, for example, the resp attribute will indicate - the responsibility for identifying that the addition is indeed an addition, and also - (if the hand attribute is supplied) to which hand it should be attributed. - In this case, Bowers is credited with identifying the hand as that of William James. - In the case of the corr element, the resp attribute indicates who - is responsible for supplying the intellectual content of the correction reported in - the transcription: here, Bowers' correction of One to one. In the case - of a deletion, the resp attribute will similarly indicate who bears - responsibility for identifying or categorizing the deletion itself, while other - attributes (hand most obviously) attribute responsibility for the deletion - itself. It should be noted that the source attribute may be used in a simiilar - fashion to indicate, for example, when an encoding decision is based on the work of a - previous editor or on an article. In that case, the source would point to - a bibl in the bibliography.

-

- In cases where both the resp and cert attributes are defined - for a particular element, the two attributes refer to the same aspect of the markup. - The one indicates who is intellectually responsible for some item of information, the - other indicates the degree of confidence in the information. Thus, for a correction, - the resp attribute signifies the person responsible for supplying the - correction, while the cert attribute signifies the degree of editorial - confidence felt in that correction. For the expansion of an abbreviation, the - resp attribute signifies the person responsible for supplying the - expansion and the cert attribute signifies the degree of editorial - confidence felt in the expansion.

-

This close definition of the use of the resp and cert - attributes with each element is intended to provide for the most frequent - circumstances in which encoders might wish to make unambiguous statements regarding - the responsibility for and certainty of aspects of their encoding. The - resp and cert attributes, as so defined, give a convenient - mechanism for this. However, there will be cases where it is desirable to state - responsibility for and certainty concerning other aspects of the encoding. For - example, one may wish in the case of an apparent addition to state the responsibility - for the use of the add element, rather than the responsibility for - identifying the hand of the addition. It may also be that one editor may make an - electronic transcription of another editor's printed transcription of a manuscript - text—here, one will wish to assign layers of responsibility, so as to allow the - reader to determine exactly what in the final transcription was the responsibility of - each editor. In these complex cases of divided editorial responsibility for and - certainty concerning the content, attributes, and application of a particular - element, the more general mechanisms for representing certainty and responsibility - described in chapter should be used.

- -

It should be noted that the certainty and responsibility mechanisms described in - chapter replicate all the functions of the resp and - cert attributes on particular elements. For example, the encoding of - Donaldson's conjectured emendation of wight to - wright in line 117 of Chaucer's Wife of Bath's - Prologue (see ) may be encoded as follows using the - resp and cert attributes on the corr element: - - wightwright Exactly the same information could be conveyed - using the certainty and responsibility mechanisms, as follows: - wrightwight - - The choice of which - mechanism to use is left to the encoder. In transcriptions where only such statements - of responsibility and certainty are made as can be accommodated within the - resp and cert attributes of particular elements, it will be - economical to use the resp and cert attributes of those - elements. Where many statements of responsibility and certainty are made which cannot - be so accommodated, it may be economical to use the respons and - certainty elements throughout.

-

The above discussion supposes that in each case an encoder is able to specify exactly - what it is that one wishes to state responsibility for and certainty about. - Situations may arise when an encoder wishes to make a statement concerning certainty - or responsibility but is unable or unwilling to specify so precisely the domain of - the certainty or responsibility. In these cases, the note element may be - used with the type attribute set to cert or resp and the - content of the note giving a prose description of the state of affairs.

-
-
- -
- Damage and Conjecture -

The carrier medium of a primary source may often sustain physical damage which makes - parts of it hard or impossible to read. In this section we discuss elements which may be - used to represent such situations and give recommendations about how these should be - used in conjunction with the other related elements introduced previously in this - chapter.

- - -
- Damage, Illegibility, and Supplied Text -

The gap and supplied elements described above (section ) should be used with appropriate attributes where the degree of - damage or illegibility in a text is such that nothing can be read and the text must - be either omitted or supplied conjecturally or from one or more other sources. In - many cases, however, despite damage or illegibility, the text may yet be read with - reasonable confidence. In these cases, the following elements should be used: - - - As members of the class att.damaged, these - elements bear the following attributes: - - The class att.damaged is a subclass of the - class att.dimensions, itself a subclass of the class - att.ranging. Consequently these elements also - therefore bear at least the following attributes: - - - From the att.spanning class, - damageSpan inherits the following additional attribute: - - -

-

The following examples all refer to the recto of folio 5 of the unique manuscript of - the Elder Edda. Here, the manuscript of Vóluspá has been damaged - through irregular rubbing so that letters in various places are obscured and in some - cases cannot be read at all.

-

In the first line of this leaf, the transcriber may believe that the last three - letters of daga can be read clearly despite the damage: um aldr - daga yndisniota -

-

If, as is often the case, the damage crosses structural divisions, so that the - damage element cannot be nested properly within the containing - div elements, the damageSpan element may be used, in the same - way as the delSpan and addSpan elements discussed in section .

- - - -

-

[...]

-

[...] -

Note that in this example the spanTo element points to the - next pb element rather than to an inserted anchor element, since it - is the whole of the leaf (the text between the two pb elements) which has - sustained damage. For other techniques of handling non-nesting information, see - chapter .

-

If, as is also likely, the damage affects several disjoint parts of the text, each - such part must be marked with a separate damage or damageSpan - element. To indicate that each of these is to be regarded as forming part of the same - damaged area, the group attribute may be used as in the following example. - In this (imaginary) text of Fitzgerald's translation from Omar Khayam, water damage - has affected an area covering parts of several lines: The Moving Finger wries; and having writ, - Moves on: nor all your Piety nor - Wit - Shall lure it back to - cancel half a Line, - Nor all your Tears wash out a Word of it - -

-

A more general solution to this problem is provided by the join element - discussed in which may be used to link together arbitrary - elements of any kind in the transcription. Here, several phenomena of illegibility - and conjecture all result from a single cause: an area of damage to the text caused - by rubbing at various points. The damage is not continuous, and affects the text at - irregular points. In cases such as this, the join element may be used to indicate - which tagged features are part of the same physical phenomenon.

- -

If the damage has been so severe as to render parts of the text only imperfectly - legible, the unclear element should be used to mark the fact. Returning to - the Eddic example above, an encoder less confident in the daga - reading might indicate this as follows: um aldr daga yndisniota

-

If it is desired to supply more information about the kind of damage, it is also - possible to nest an unclear element within the damage element: - um aldr daga yndisniota

-

Alternatively, the transcriber may not feel able to read the last three letters of - daga but may wish to supply them by conjecture. Note the - use of the resp attribute to assign the conjecture to Finnur Jónsson: - um aldr daga - yndisniota The supplied element may if desired be enclosed within - a damage element: um aldr daga - yndisniota The transcriber may also provide alternative conjectures by - enclosing multiple supplied elements within a choice element.

-

Contrast the use of gap in the next line, where the transcriber believes - that four letters cannot be read at all because of the damage: þar komr inn dimmi - dreki fliugandi naþr frann neþan As with supplied, this - gap might be enclosed by a damage element.

-

Where elements are nested in this way, information about agency, etc. is by default - inherited. In the following imaginary example, there is a smoke-damaged part within - which two stretches can be read with some difficulty, and a third stretch which - cannot be read at all: - and the proof of this is - - margin - - -

-

The above examples record imperfect legibility due to damage. When imperfect - legibility is due to some other reason (typically because the handwriting is - ill-formed), the unclear element should be used without any enclosing - damage element. In Robert Southey's autograph of The Life of - Cowper the final six letters of attention are - difficult to read because of the haste of the writing, though reasonably certain from - the context. and - from time to time invited in like manner his attention - The cert attribute on the unclear element may be used to indicate - the level of editorial confidence in the reading contained within it.

-
-
- Use of the gap, del, damage, unclear, and - supplied Elements in Combination -

The gap, damage, unclear, supplied, and - del elements may be closely allied in their use. For example, an area of - damage in a primary source might be encoded with any one of the first four of these - elements, depending on how far the damage has affected the readability of the text. - Further, certain of the elements may nest within one another. The examples given in - the last sections illustrate something of how these elements are to be distinguished - in use. This may be formulated as follows: - where the text has been rendered completely illegible by deletion or damage - and no text is supplied by the editor in place of what is lost: place an empty - gap element at the point of deletion or damage. Note that the gap - could be wrapped in a del or damage element. Use the - reason attribute to state the cause (damage, deletion, etc.) of - the loss of text. - where the text has been rendered completely illegible by deletion or damage - and text is supplied by the editor in place of what is lost: surround the text - supplied at the point of deletion or damage with the supplied element. - Use the reason attribute to state the cause (damage, deletion, etc.) - of the loss of text leading to the need to supply the text. - where the text has been rendered partly illegible by deletion or damage so - that the text can be read but without perfect confidence: transcribe the text - and surround it with the unclear element. Use the reason - attribute to state the cause (damage, deletion, etc.) of the uncertainty in - transcription and the cert attribute to indicate the confidence in - the transcription. - where there is deletion or damage but at least some of the text can be read - with perfect confidence: transcribe the text and surround it with the - del element (for deletion) or the damage element (for - damage). Use appropriate attribute values to indicate the cause and type of - deletion or damage. Observe that the degree attribute on the - damage element permits the encoding to show that a letter, word, or - phrase is not perfectly preserved, though it may be read with - confidence. - where there is an area of deletion or damage and parts of the text within - that area can be read with perfect confidence, other parts with less - confidence, other parts not at all: in transcription, surround the whole area - with the del element (for deletion; or the delSpan element - where it crosses a structural boundary); or the damage element (for - damage). Text within the damaged area which can be read with perfect confidence - needs no further tagging. Text within the damaged area which cannot be read - with perfect confidence may be surrounded with the unclear element. - Places within the damaged area where the text has been rendered completely - illegible and no text is supplied by the editor may be marked with the - gap element. For each element, one may use appropriate attribute - values to indicate the cause and type of deletion or damage and the certainty - of the reading. -

-

The rules for combinations of the add and del elements, and for the - interpretation of such combinations, are similar:

- - if one add element (with identifier ADD1) contains - another (with identifier ADD2), then the addition - ADD1 was first made to the text, and later a second addition - (ADD2) was made within that added text: This is the text with some added (interlinear!) material as - written. - if one del element contains another, and the seq attribute - does not indicate otherwise, it should be assumed that the inner deletion was made - before the enclosing one. In the following example, the word - redundant was deleted before a second deletion removed - the entire passage: This - sentence contains some redundant unnecessary - verbiage. - if a del element contains an add element, the normal - interpretation will be that an addition was made within a passage which was later - deleted in its entirety: This - sentence was deleted originally from the - text. - if an add element contains a del element, the normal - interpretation will be that a deletion was made from a passage which had earlier - been added: This sentence was - added eventually to the text. - When some text has been blackened out so thoroughly that can no longer be read, - the encoding should be: runs out the door in shirt - For consistency, one might prefer to encode the deletion as such, using del, - and containing a gap, as in the following example: - runs out the door in shirt - This is something that would be necessary if one wanted to encode a subst including an illegible deletion: - summons - If some parts of the deleted text are readable, and other parts unreadable, it should be encoded as in the following example: - Billy in The ng Silver Dollar.. - -
-
- - -
- Marking up the Writing Process -

Modifications of various kinds (correction, addition, deletion, etc.) are frequently - found within a single document, and may also be inferred when different documents are - compared, although it may be an open question as to whether inter-document discrepancies - should be regarded in the same way as intra-document - alterations. When two witnesses are collated, we may observe that a word present in one - is missing from the other: this does not necessarily imply that the word was added to - the first witness, nor that it was deleted from the other.

- -

In this section we discuss a number of elements which may be useful when attempting to - record traces of the writing process within a document.

- -
- Generic Modification - - - -

Most, if not all, transcriptional elements imply a certain level of semantic - interpretation. For instance, using the add element to encode a word or - phrase that occupies interlinear space involves a decision that it has been - deliberately inserted as an addition rather than an alternative, and indeed a - judgment that it was written after, rather than before, the other lines. Where it is - felt desirable to keep the recording of what is on the page - entirely separate from what is the editor’s interpretation, the - generic mod element may be preferred. - - This element simply indicates any kind of modification that has been - identified in the document, without prejudice as to its function. Occurrences of the - mod element may be categorized by means of their type - attribute, and visual aspects of their appearance can be described by means of the - rend attribute, but they provide no further interpretation of the - function or intention of the passage so marked up. The spanTo attribute - may be used to indicate the end of a modified passage if this extends across the - boundaries of some other XML element, for example from the middle of one line tagged - as a line to the middle of another line some distance further on in - the document.

- - words words words words with wavy - underline <!-- more lines here --> wavy underlining finishes - here more words - - - - -

The distinction between an example such as that above and the simple use of - hi to mark the visual salience of the underlining (apart from the use of - the spanTo attribute) is that hi does not imply that the visual - effect being recorded is understood to represent some kind of modification.

-
- -
- Metamarks - -

By metamark we mean marks such as numbers, arrows, crosses, or other - symbols introduced by the writer into a document expressly for the purpose of - indicating how the text is to be read. Such marks thus constitute a kind of markup of - the document, rather than forming part of the text. - - -

- -

Unlike marginal notes or other additions to the text, metamarks are used by the - writer to indicate a deliberate alteration of the writing itself, such as move - this passage over there. An addition or annotation by contrast would typically - concern some property of the passage other than its intended location or status - within the text flow. A metamark may contain text, or some other graphic which the - encoder wishes to represent, or it may simply consist of arrows, dots, lines etc. - which the encoder simply describes.

- - - -

The metamark element carries a function attribute which specifies - the function of the metamark, using values such as reorder, - flag, delete, insert or used. The - passage to which the metamark applies may be indicated in either of two ways: the - target attribute may be used to point to the element or elements - containing the passage concerned, or the spanTo element may be used to - point to a position in the document at which the passage concerned finishes. In the - latter case, the metamark itself must be supplied at the position in the - document where the passage concerned begins; in the former case it may be supplied at - any convenient point. Both attributes should not be supplied.

- -

The following example is taken from an 15th century legal book from the city of - Göttingen, containing regulations of everyday life issued by the city council

- - Kundige bok 2, fol 1v. -
-

- - -

In the second paragraph, the word lege ("read") - was written in the left hand margin, next to the sentence beginning Ock en - schullen de bruwere.... It is thought to function as a metamark, indicating - that this sentence forms part of the regulations. A further sentence was then added, - while at some later stage the text and also the metamark were deleted. We might - encode this as follows as an embedded transcription (keeping in mind that the elements described here can also be used within text): - - lege - Ock en schullen de bruwere des hilgen dages - nicht over setten noch uppe den stillen fridach bruwen. - - Noch nymande over setten, se en sehin denne erst, dat uppe den bonen neyn - stro noch, huw noch flaß ligghe, by pine eyner halven roden, deme bruwere so - wol alse dem bruwheren to murende. - - -

-

The change attribute used here to indicate the sequencing of these various - interventions is discussed below, in section . The - elements addSpan and delSpan are discussed in section .

- -

The metamark element may also be used to encode the symbols etc. often found - in marked-up proofs such as the following, taken from the Walt Whitman archive:

- - From a corrected proof of Miracles (Walt Whitman - Archive) -

- -

In this example, the whole of what was originally the 14th section of the poem has - been marked for deletion, both by horizontal and vertical lines, and by the proofreading mark - resembling the deleatur or dele deletion symbol to left and right of the section. The - deletion itself might be encoded by using the normal del or delSpan - element, and the metamarks by the metamark element. This is quite a - different case from that of the next example, in which the writer does not intend to - suppress the content, but only to mark that it has been copied to another manuscript - or reused.

-

-

- - From "I am that halfgrown angry boy" (MS q 25), David M. Rubenstein Rare - Book & Manuscript Library, Duke University. -
-

-

This page contains internal deletions, additions, and retracings but these are - semantically quite different from the apparent deletion - signalled by the larger of the two single vertical lines, which shows that the - written material has been transferred or re-used, not deleted.

- - - - - I am that halfgrown angry boy, fallen asleep - The tears of foolish passion yet undried - upon my cheeks. - - I pass through the travels and fortunes of - thirty - years and become old, - Each in its due order comes and goes, - And thus a message for me comes. - The - - Entered - Yes - - -

In this embedded transcription example, we class as metamarks both the long vertical line and the annotation - Entered - yes. - - Both metamarks are assumed to indicate that the whole of the written zone with - identifier X2 is marked as having been used. metamark can be similarly used within text to encode the same phenomenon as part of a transcription that privileges logical over physical and layout structures.

- -
- -
- Fixation and Clarification - -

A writer may sometimes rewrite material a second time without significant change and - in the same place. We consider this a distinct activity from addition as usually - defined because no new textual material results; instead the status of existing - material is reaffirmed. We may distinguish two variants of this: - fixation where the first version was a tentative draft which is - subsequently reaffirmed, for example by inking it over; and - clarification, where the first version was badly written and has been - rewritten for clarity. The element retrace is provided for both cases; its - cause attribute may be used to distinguish these or other cases. - - -

- -

In this simple example, taken from the papers of Henrik Ibsen, the writer wrote the - word skuldren hastily, and then returned to it to make the - letter l larger and clearer:

- - From autograph ms of Peer Gynt, Collin 2869, 4°, - I.1.1, the Royal Library of Copenhagen -
We might transcribe this word as follows: - Skuldren - -

- -

A single rewrite may not be sufficient, and it may be that the document becomes - almost unreadable as a result of repeated clarification. In the following example, we - can distinguish at least three attempts to write the letters - er in the word bægerklang:

- - Detail from autograph ms Brand in The Royal - Library, Denmark (KBK Collin 262) - -
We might encode this by nesting the retrace element as follows: - - ved Bæg - er - ... - The change attribute used here is discussed further below ().

- -

The retrace element is used only for cases where text has been written - multiple times. When metamarks and other markup-like strokes have been rewritten - multiple times, the redo element described in the next section should be - used in preference.

-
- -
- Confirmation, Cancellation, and Reinstatement of Modifications - -

- A writer may indicate that an alteration is itself to be altered: for - example, a struck-through passage may be restored via a dotted underlining, or the - underlining of a passage may be deleted by a wavy line.

- -

The following elements are provided to represent these situations: - - - -

- - - - - -

The element restore () is provided for the - comparatively simple case where a simple deletion is marked as having been - subsequently cancelled. The undo element discussed here is more widely - applicable and may be used for any kind of cancellation. It points to the element or - elements which are being cancelled. These components need not be contiguous, provided - that the cancellation is clearly a single act; each distinct act of cancellation - requires a distinct undo element, however. Either of the attributes - target or spanTo may be used to indicate the passages - concerned.

- -

Consider the following imaginary example:

- - Imaginary example demonstrating restoring and undoing -
We hypothesize that the text has gone through three states or changes, as - follows: - This is just some sample text, we need a real example. - This is not a real example. - This is just some text, not a real example. - -

- -

This sequence of events might be encoded as follows: - This is - just some sample text, we need - not a real example. - using two undo elements, each with a spanTo attribute, - to delimit the two parts of the deletion which were reverted at change s3. Note that - in this case, since target is not supplied, it is the effect of the parent - element (the del) which is assumed to be undone.

- -

Alternatively, we might more economically use the generic seg element to delimit the two sequences whose deletion is being reverted, and - then use the target attribute on a single undo element: - This is - just some sample text, we - need - not a real example. - - - -

-
- -
- Transpositions - -

A transposition occurs when metamarks are found in a document indicating - that passages should be moved to a different position. Typically this may be done - using arrows, asterisks or numbers, or other means. By definition the result of a - transposition is not present in the document, and should not therefore be encoded, if - the intention is to represent the actual appearance of the document. Instead, the - following elements may be used to indicate the intended reordering: - - -

-

Consider for example, the following extract from an Ibsen manuscript

- - Extract from autograph Digte (Poems) NBO Ms. 4º 1110a -
The underlined numbers 1 and 2 here indicate that, although the word - bör precedes the word hör in the - text, the order of the two words should be reversed. We may encode this as follows: - - bör2. og hör1. - - - - - - - - -

- -

Note the use of the generic seg element to identify the sections of text - being transposed. The following example uses an embedded transcription approach, which typically identifies lines of writing with the line element. This makes it trivial to refer to the transposed line, but when encoding transposition within text the encoder will need to find a way to identify the line with another element, such as seg.

- - Detail from autograph ms of Den episke Brand (KBK Collin - 2869) -
- - 2.) thi da er du med Himmelen i Pagt; — - - 1.) da kan du - Folkets Jøkelhjerter tine; - - - - - - - - When transposition is made, the whole element indicated is understood to be - moved, not just its contents. In the above example, the metamarks are thus understood - to be moved along with the lines to which they apply.

- - - -

One or more listTranspose elements may be - supplied either embedded within the text, in the - profileDesc of the header, or in a - standOff depending on local preference. Each - listTranspose can contain one or more - transpose elements, each of which defines a - single transposition.

-
- -
- Alternative Readings -

- - Detail from autograph manuscript of the second version of Lalla - Rookh, Pierpont Morgan MA 310 -
In this example two alternative readings are provided, but no preference is - indicated. While the author apparently first composed the line Alone before his - native river -, at some later point, he entertained the possibility of using - the word beside instead of before. The - manuscript supplies no indication of which word Moore favours at this point, although - in fact, in the first printed edition of Lalla Rookh the word - beside was chosen.

-

The element alt provided by the linking module - gives a simple way of encoding the state of this manuscript, as follows: Alone before - beside his native river ­— - - -

-

The mode attribute here indicates that the two possible readings indicated - by the target attribute are mutually exclusive. The weights - attribute indicates the relative importance or preference to be attached to the two - readings on a scale running from zero (most improbable) to one (most probable). In - this case, we have a very strong preference for the second reading because this is - the one that appears in the published version of the poem. The alt element - is further discussed in section .

-
- - - -
- Instant Corrections -

The use of elements such as del and add necessarily implies that - the modifications they indicate were made at some time after the original writing. An - exception to this is where a false start or instant correction - has been identified: the author starts to write, and then immediately corrects what - has been written.

-

The instant attribute defined by this module may be used on any element - which is a member of the att.editLike class to modify - this default assumption. When the value of instant is set to - true, the addition or deletion is considered to belong to the same - change as its parent element, while false means some change later than - that of its parent.

-

An example of false start or instant correction can be seen in the following line: -

- - Detail fron [I am a curse], one of the drafts for Whitman's - Song of Myself -
in which we can detect the following sequence of events: - The letter T is written and then immediately deleted - The word The is written, deleted, and replaced by the word - His - The added word His is then deleted - The initial letter i of the words iron - necklace is overwritten with a capital I - To indicate that the first of these acts must have taken place during the - main act of writing, before the other deletion and additions, we might encode this - revision campaign as follows: - T - - The - - His - - - - i - I - ron necklace - -

-
-
-
- -
- Aspects of Layout -

The following methods are available to capture general aspects of the layout of material on - a page where this is considered important. Within the sourceDoc element, as - already indicated, the element surface and surfaceGrp enable the encoder - to represent directly the structure of a codex as gatherings or quires, leaves, and - surfaces, as in the following example: - - - - - - - - - - - - - - - - - - - - -

-

In some cases, it may be preferable to define surfaces corresponding with each two - page opening, for example where it is clear that the writer regarded each such opening as a - single writing surface, with written zones or other features crossing the page divide. An - example is shown here:

- - Opening from autograph ms of Proust's A la recherche du temps perdu - (f 42v-43r) -
-

-

The coloured lines added to this image indicate a number of zones of writing, colour coded - to indicate the order in which they were written (purple, then green, then red). For - example, the zone marked in red on the left contains a note referring to the purple zone on - the right.

- -

This approach assumes that the transcription will primarily be organized in the same way as - the physical layout of the source, using embedded transcription elements. Alternatively, - where the a non-embedded transcription has been provided, using the text element, - it is still possible to record gathering breaks, page breaks, column breaks, line breaks - etc in the source, using the elements described in section . Detailed - metadata about the physical make-up of a source will usually be summarized by the - physDesc component of an msDesc element discussed in .

- -
- Space -

The author or scribe may have left space for a word, or for an initial capital, and for - some reason the word or capital was never supplied and the space left empty. The - presence of significant space in the text being transcribed may be indicated by the - space element. - - Note that this element should not be used to mark normal inter-word space or - the like.

-

In line 694 of Chaucer's Wife of Bath's Prologue in the Holkham - manuscript the scribe has left a space for a word where other manuscripts read - preestes: By - god if wommen had writen storyes As han within her - oratoryes The supplied element discussed in the previous section may - be used to supply the text presumed missing: By god if wommen had writen storyes As - preestes han within - her oratoryes Here, the fact of the space within the manuscript is indicated - by the value of the reason attribute. The source of the supplied text is - shown by the value of the source attribute as the Hengwrt manuscript; the - transcriber responsible for supplying the text is ES.

-
-
- Lines -

One of the more common forms of modification encountered in written documents of any - kind is the presence of lines written under, beside, or through the text. Such lines may - be of various types: they may be solid, dashed or dotted, doubled or tripled, wavy or - straight, or a combination of these and other renderings. The line may be used for - emphasis, or to mark a foreign or technical term, or to signal a quotation or a title, - etc.: the elements emph, foreign, term, mentioned, - or title may be used for these. Where the line has a clear paratextual function - the metamark element may be considered more appropriate. Frequently, a scholar - may judge that a line is used to delete text: the del element is available to - indicate this. In all these cases, the rend attribute may be used to supply - further details concerning the style of the line. Thus, Lawrence's deletion by - strike-through of my in the autograph of Eloi, Eloi, lama - sabachthani may be encoded: For I hate this my body, which is so - dear to me

-

There will be instances, however, where a scholar wishes only to register the occurrence - of lines in the text, without making any judgement as to what the lines signify. In - these cases the hi element may be used, with the rend attribute to - mark the style of line. In the manuscript of a letter by Robert Browning to George - Moulton-Barrett the underlining of the phrase had obtained all the letters to - Mr Boyd may be marked-up as follows: I have once — by - declaring I would prosecute by law — hindered a man's proceedings who had obtained all the letters to Mr Boyd

-

The above examples presume the common case where a single word or phrase is marked by a - line, with no doubt as to where the marking begins or ends and with no overlapping of - the area of text with other marked areas of text. Where there is doubt, the - certainty element may be used to record the doubt. In the Browning example - cited above the underlining actually begins half-way under who, - and this uncertainty could be remarked as follows: I have once — by declaring I would prosecute - by law — hindered a man's proceedings who had - obtained all the letters to Mr Boyd - - - may begin with previous word -

-

Where the area of text marked overlaps other areas of text, for example crossing a - structural division, one of the spanning mechanisms mentioned above must be used; for - example where the line is thought to mark a deletion, the delSpan element may - be used. Where it is desired simply to record the marking of a span of text in - circumstances where it is not possible to surround the text with a hi element, - the span element may be used with the rend or type - attribute indicating the style of line-marking.

-

More work needs to be done on clarifying the treatment of other textual features marked - by lines which might so overlap or nest. For example, in many Middle English manuscripts - (e.g. the Jesus and Digby verse collections), marginal sidebars may indicate metrical - structure: couplets may be linked in pairs, with the pairs themselves linked into - stanzas. Or, marginal sidebars may indicate emphasis, or may point out a region of text - on which there is some annotation: in many manuscripts of Chaucer's Wife of - Bath's Prologue lines 655–8 are marked with nesting parentheses against which - the scribe has written nota.

-

Such features could be captured by use of the note element, containing a prose - description of the manuscript at this point, enhanced by a link to a visual - representation (or facsimile) of the feature in question. For example, in the Chaucer - example just cited, one may wish to record that the nota is - written in the Hengwrt manuscript in the right margin against a single large left - parenthesis bracketing the four lines, with two right parentheses in the right margin - bracketing two overlapping pairs of lines: the first and third, the second and fourth. - The note element allows us to record that the scribe wrote - nota, but is not well-adapted to show that the - nota points both at all four lines and at two pairs of lines - within the four lines. The metamark element discussed in section above provides better facilities for this kind of complex - annotation.

-
-
- - -
- Transcription and Ruby - -

These Guidelines also provide special elements to support the - encoding of ruby annotations, which are common in East Asian textual - traditions. These elements provide a method of capturing a specific - type of annotation, in addition to the generic methods like the - note or interp elements. Both the specific and - general methods should integrate well with the transcriptional - elements described above, allowing authorial and scribal features to - be captured in conjunction with ruby base text and annotations. See - for more information about these - elements.

-
- -
- Headers, Footers, and Similar Matter - -

Such information as page numbers, signatures, or catchwords may be recorded in a - specialized fw element provided for that purpose. Although the name derives from - the term forme work, used in description of early printed documents (the - forme being the block used to hold movable type), the fw element may be - used for such features of any document, written or printed. Note that the purpose of this - element is to record page numbers etc. actually present in the document being - encoded, not necessarily to provide a complete or accurate pagination of it.

-

Information about pagination etc. may also be provided using the n attribute of - the pb or gb elements, or by other appropriate milestone - elements, as further discussed in section : since this information is - usually provided by the encoder, it is not subject to the constraint that it should be - present only if textually present in the source being encoded. In text-critical situations - it may be useful to provide both a normalized version of the pagination and a - representation of the catch-word or numbering, especially when the latter presents a - variant reading, or is significant for compositor identification. - - The fw element may be used to encode any of the unchanging portions of - a page forme, such as: - running heads (whether repeated or changing on every page, or alternating - pages) - running footers - page numbers - catch-words - other material repeated from page to page, which falls outside the stream of the - text - It should not be used for marginal glosses, annotations, or textual variants, which - should be tagged using gloss, note, or the text-critical tags described - in chapter , respectively.

-

For example: Poëms. - 29 - E3 - TEMPLE - - -

-
- - - -
- Identifying Changes and Revisions -

A major purpose of genetic editing is the identification of revision - campaigns or, more generally, changes. An editor may wish to - regard a particular set of alterations (deletions, additions, substitutions, transpositions, etc.) or - any other act of writing as a single object for which we use the general term change, to indicate both that one or more of such - phenomena preceded or followed another and also to indicate that they are related in some - way, for example that one is a consequence of the other. They might also wish to group - together certain revisions, regardless of when they might have occurred, based on a variety - of other shared characteristics (e.g., corrections of factual errors or revisions that - incorporate suggestions made by a given reader). To document this we need: - a system to assign phenomena to a particular change as defined above - a way to characterize each such change, in itself and in relation to others. -

- -

The element creation (within the TEI header profile description) contains all - information relating to the genesis or production of a text. It may contain a - listChange element which contains a number of change elements, one for - each set of alterations identified: - - - -

- -

In the following example an editor has identified four distinct sets of alterations:

- - - - - First stage, written in ink - Second stage, with revisions written in the author's hand - using pencil - Fixation of the pencilled revisions together with further - revisions in the author's hand using ink - Additions in a different hand, probably at a later - stage - - - - -

The listChange element carries an attribute ordered, which can take the - values true or false (the default). The attribute specifies - whether the order of child elements signifies a temporal order for the revision campaigns - which they document. In the example above, the editor has asserted that the four sets - distinguished are ordered chronologically according to the order of the change - elements. - - If necessary, listChange elements can be nested hierarchically. This may be - helpful in two cases. Firstly one can build up hypotheses about related revisions - step-by-step, starting with change elements of smaller coverage, whose members are certainly - related, and then in a subsequent pass grouping these in turn, thereby extending - their reach.

- - - - - - An unrelated change note - - Alterations on one manuscript page, certainly - related - Alterations on another manuscript page, certainly - related - - Another unrelated change note - - - - -

A nested listChange element is also useful to indicate a partial - ordering of change elements.

- - - The first stage - - - A revision of the first stage - Another revision of the first stage - - The last stage - - -

In addition to the possibility of being ordered by their sequence within - a listChange element, - change elements may carry a number of attributes from the att.datable class (period, when, notBefore, - notAfter, from, and to) which allow each element to be - dated as exactly or inexactly as necessary, in the same way as is currently possible for - the TEI date element.

- - - - - - - The first draft of - Persuasion, completed by the date July 16 1816 - which is written after the word Finis at page - 30. - After the 16th of July - Austen starts revision of the two final chapters, by rewriting the end and - adding a new zone (pages 32-35) to be inserted at - page 19. This stage is documented by the - deletion of the date (July 16 1816) at page - 30, and the addition of more text and of a new date (July 18. - 1816) at page 31 - Before publication, after July 18th, - 1816 chapters 10-11 were broken into three chapters, 10, 11, 12, as - witnessed by the print. - - - - -

Each change element, apart from declaring a distinct moment or phase in the creation of the - document, may also contain references to other annotations contained within the - teiHeader or in the document (as shown in the previous example). Such - references, along with the textual content, are purely documentary. The association between a textual - component and a change element - is always made explicitly, either by using the target - attribute on the change element to point to one or more textual elements, or by pointing - from the element or elements concerned to the change element by means of their - change attribute. If a change element is associated with some - element, it is also associated with all of that element's children, unless otherwise - indicated, for example by a new value for the change attribute.

-

In the following simple example, the text at one stage read This is a mouse, and at - the next This is a house mouse: - This is a house - mouse. - -

-

In this example, however, the text originally read This is a house, and subsequently - This is a mouse: - This is a - house - mouse - . - Note that in this case both the deletion and the addition are associated with the - second change element. The word house, because its deletion forms part of - this second set of alterations, must have - been present originally, whereas the word mouse must have been added during - the second set of alterations.

- -

Elements such as add and del and the like carry an implied semantics - concerning the order in which events in the writing of a document was carried out: - something which is deleted must have been written before it was deleted; something which is - added must have been added at a later stage of the writing. Even when a combination of such - elements is used, the chronology can usually be inferred (see further ). Explicit indication of the set of alterations to which some modification belongs is mostly useful - in situations where all the alterations identified in a document are to be grouped, for - example chronologically.

- - -

The interpretation of change elements with respect to a particular text passage is based on a number - of implicit assumptions and constraints which have the effect of minimizing the amount of - tagging necessary. The system is also flexible enough to support an explicit distinction - between acts of writing and textual alterations, since either of these can be associated - with changes described in the encoding. The following example shows an encoding in which - the same passage is transcribed twice, once from a documentary perspective, and once from a - textual one: - - - - First stage, written in ink by a - scribe - Revised by Goethe using pencil - Fixation of the revised passages and further revisions by Goethe using - ink - - - - - - - - - Nun - - Ihr wanſtige Schuften mit den Feuerbacken - - - feiſt - - Ihr glüht ſo recht vom Höllen Schwefel ſatt. [...] - - - - - - - Ihr - Nun - wanſtige Schuften mit den Feuerbacken - Ihr glüht ſo recht vom Höllen Schwefel - ſatt - feiſt - . - - - -

- -

The documentary transcription stresses the writing process, while the textual transcription - emphasizes textual alterations. In either case, the change of writing activity associated - with a particular feature in the transcript is explicitly indicated. From the documentary - perspective, by assigning particular modifications to a specific change element, we describe the - writing process, in that they specify which segment has been written when - . From the textual perspective, the markup concentrates simply on the - existence of textual alterations and makes no explicit claims about the order of writing. - -

-
- - - -
- Other Primary Source Features not Covered in these Guidelines -

We repeat the advice given at the beginning of this chapter, that these recommendations are - not intended to meet every transcriptional circumstance ever likely to be faced by any - scholar. They are intended rather as a base to enable encoding of the most common phenomena - found in the course of scholarly transcription of primary source materials. These - guidelines particularly do not address the encoding of physical description of textual - witnesses: the materials of the carrier, the medium of the inscribing implement, the - organisation of the carrier materials themselves (as quiring, collation, etc.), and authorial - instructions or scribal markup, except insofar as these are involved in the broader - question of manuscript description, as addressed by the msdescription module described in chapter .

-
- -
- Module for Transcription of Primary Sources -

The module described in this chapter makes available the following components: - - Transcription of Primary Sources - Transcription of primary sources - 原文轉錄 - Représentation de sources primaires - Trascrizione di fonti primarie - Transcrição de fontes primárias - 転記モジュール - - - The selection and combination of modules to form a TEI schema - is described in .

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-
diff --git a/P5/Source/Guidelines/fr/PH-PrimarySources.xml b/P5/Source/Guidelines/fr/PH-PrimarySources.xml new file mode 120000 index 0000000000..766b2496bb --- /dev/null +++ b/P5/Source/Guidelines/fr/PH-PrimarySources.xml @@ -0,0 +1 @@ +../en/./PH-PrimarySources.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/PrefatoryNote.xml b/P5/Source/Guidelines/fr/PrefatoryNote.xml deleted file mode 100644 index f4369cae25..0000000000 --- a/P5/Source/Guidelines/fr/PrefatoryNote.xml +++ /dev/null @@ -1,674 +0,0 @@ - - - - - - - -
Prefatory Notes -

This Appendix contains (in reverse chronological -order) the Introductory Notes prefixed to each -revision of the TEI Guidelines since its first publication in 1994. -

- -
Prefatory Note (March 2002) -

The primary goal of this revision has been to make available a new -and corrected version of the TEI Guidelines which: - -is expressed in XML and conforms to a TEI-conformant XML - DTD; -generates a set of DTD fragments that can be combined - together to form either SGML or XML document type - definitions; - corrects blatant errors, typographical mishaps, and other - egregious editorial oversights; -can be processed and maintained using readily available XML - tools instead of the special-purpose ad hoc software originally - used for TEI P3. - -

-

A second major design goal of this revision has been to ensure that the - DTD fragments generated would not break existing documents: in - other words, that any document conforming to the original TEI P3 - SGML DTD would also conform to the new XML version of - it. Although full backwards compatibility cannot be guaranteed, - we believe our implementation is consistent with that goal. -

-

In most respects, the TEI Guidelines have stood the test of time remarkably -well. The present edition makes no substantial attempt to rewrite those few parts -of them which have now been rendered obsolete by changes since their -first publication, though an indication is given in the text of where such rewriting is -now considered necessary. Neither does the present version attempt to -address any of the many possible new areas of digital activity in which -the TEI approach to standardization may have something to offer. Both -these tasks require the existence of an informed and active TEI -Council to direct and validate such extension and maintenance work, -in response to the changing needs and priorities of the TEI user community. -

-

Two exceptions to the above principles may be cited: firstly, the -chapter which originally provided a Gentle -Introduction to SGML has been completely rewritten to -provide a similarly gentle introduction to XML; secondly the chapter -on character sets has been completely revised in light of the -close connexion between Unicode and XML. The editors gratefully -acknowledge the assistance of the ad hoc workgroup chaired by Christian -Wittern, which undertook to provide expert advice and correction at -very short notice, in the latter task.

-

The preparation of this new version relied extensively on -preliminary work carried out by the former North American editor of -the TEI Guidelines, C.M. Sperberg-McQueen. In a TEI working paper -written in 1999TEI ED W69, available -from the TEI web site at . he sketched -out a precise blueprint for the conversion of the TEI from SGML to -XML, which we have implemented, with only slight modification.

-

The Editors would also like to express thanks to the -team of volunteers from the TEI community who helped us with the task -of proofreading the first draft during the summer of 2001; and to - Sebastian Rahtz of Oxford University Computing Services, without - whose skill and enthusiasm this new edition would not have been - possible. -

-

A substantial proportion of the work of preparing this new edition was -funded with the assistance of a grant from the US National -Endowment for the Humanities, whose continued support of the TEI has -also been crucial to the effort of setting up the TEI Consortium. -

-

Finally, we would like to thank all our colleagues on the interim -management board of the TEI Consortium, in particular its Chairman -John Unsworth, for their continued support of -the TEI's work, and their willingness to devote effort to the -difficult task of overseeing its transition to a new organizational -infrastructure.

-

Summary details of the changes made in the present and previous -editions are given in their Prefatory Notes, all of which are now -reproduced in an Appendix to the present edition: see . -

-Lou Burnard and Syd Bauman (TEI Editors) -Oxford and Providence, March 2002. -
- - - -
Introductory Note (November 2001) -

To complete the work started in June of this year, the TEI Editors -asked for volunteers from the TEI community to proofread the preliminary XML -version. 24 volunteers responded to this call during August, and gave invaluable help both by identifying -a number of previously un-noticed errors, and by suggesting areas in -which more substantial revision should be undertaken in the -future. The Editors gratefully acknowledge the assistance of the following -individuals during this exercise: -

-

-Jimmy Adair, -Syd Bauman, -Michael Beddow, -Steven Bird, -Lisa Charlong, -Matthew Driscoll, -Patrick Durusau, -Tomaz Erjavec, -Nick Finke, -Tim Finney, -Julia Flanders, -Mike Fraser, -Pankaj Kamthan, -François Lachance, -Terry Langendoen, -Anne Mahoney, -Gregory Murphy, -Daniel Pitti, -Rafal Prinke, -Laurent Romary, -Stewart Russell, -Gary Simons, -Elisabeth Solopova, -Christian Wittern, -Martin Wynne. -

-

In addition to error correction, and clear delineation of those sections in -which substantial revision is yet to be undertaken for TEI P5, the -present draft differs from earlier ones in the following respects: - -Formal Public Identifiers have been introduced as a means of -constructing TEI DTDs and an SGML Open Catalog is now included with the -standard release; -Some systematic errors and omissions in the reference section -have been removed; the format of this section has been substantially changed, we -hope for the better; -The chapters on obtaining the TEI DTDs and WSDs have been -brought up to date; the chapter on modification has been expanded to -include a discussion of the TEI Lite customization; -All examples and cited markup has been checked for XML validity -against the published DTDs, and corrected where faulty; examples have -been formatted in a (more or less) consistent style. - -

-Lou Burnard and Syd Bauman (Editors) -Oxford and Providence, November 2001. -
-
Introductory Note (June 2001) -

This is a preliminary version of a revised and fully XML-compliant -edition of the TEI Guidelines. Although work on revising and -correcting the text of the document is incomplete, by making -available this preliminary version we hope to facilitate testing of -the XML document type declarations which it describes by as wide a -range of TEI users as possible.

-

The primary goal of this revision is to make available the -corrected (May 1999) edition of the Guidelines in a new version which: - -is expressed in XML and itself conforms to a TEI-conformant XML - DTD; -generates a set of XML DTD fragments that can be combined - together in the same way as the existing TEI (P3) SGML DTD - fragments to form true TEI XML DTD fragments without loss of functionality; -can be processed and maintained using readily available XML - tools instead of the special-purpose ad hoc software originally - used for TEI P3. - -As noted elsewhere, a number of errors were corrected in -the May 1999 edition. A (much) smaller number of errors have also been -corrected in this edition, but no new material has been added. We -expect the expansion and modification of the Guidelines to become -a real possibility in the context of the newly formed TEI Consortium, -which has funded the preparation of this present edition.

-

A major design goal of both this and the previous revision has been - to ensure that the DTD fragments generated would not break - existing documents: in other words, that any document conforming - to the original TEI P3 SGML DTD would also conform to the new - XML version of it. Although full backwards compatibility cannot - be guaranteed, we believe our implementation is consistent with - that goal.

-

In making this new version, we relied extensively on preliminary - work carried out by the outgoing North American editor of the - TEI Guidelines, Michael Sperberg-McQueen. In a TEI working paper - written in 1999, TEI ED - W69, Michael sketched out a precise blueprint for the - conversion of the TEI from SGML to XML, which we have - implemented, with only slight modification. The current TEI - editors wish to express here our admiration for the detailed - care put into that paper, without which our task would have been - forbiddingly difficult, if not impossible. We would also like to - express our thanks to Sebastian Rahtz of Oxford University - Computing Services, for his invaluable assistance in preparing - this new edition.

-

We list here in summary form all the changes made in the present -edition. Full technical details are provided in documents TEI EDW69 -and TEI EDW70, available from the TEI web site. - -A new keyword TEI.XML has been added. By setting -its value to INCLUDE, rather than the default IGNORE, -the user can request generation of an XML rather than an SGML DTD; -The content models of all elements have been checked, and, where -necessary, changed so that they are equally valid as SGML or as -XML; -The declared value for all attributes has been changed to a form -which is equally valid as SGML or as XML; -All the examples have been checked for conformance and converted to -use XML syntax, where possible. (This process is currently incomplete.) -Some errors and duplications in the class -membership of elements from the names and dates tagsets have been corrected.

-

To implement the first of these, we have parameterized the -tag omissibility indicators - o and - - -used within element declarations in the DTD. When XML is to be -generated, the parameter entities concerned are redeclared with the null -string as their value.

-

The second change was achieved by removing SGML-specific features -(ampersand connectors, inclusion and exclusion exceptions, various -types of attribute content) from the DTD and revising the syntax of -the DTD to conform to XML requirements (specifically in the -representation of mixed-content models, and by removing redundant -parentheses). In making these changes, we took care to ensure that the -resulting content model would continue to accept existing valid -documents, though in the nature of things it could not be guaranteed -to reject the same set of documents. As further discussed in EDW69 and -EDW70, some constraints (exclusion exceptions, for example) which -could be carried out by a generic SGML parser using TEI P3 will have -to be implemented by a special purpose TEI validator using TEI -P4.

-

Much work remains to be done, firstly in testing the new DTD -fragments against as wide a range of TEI materials as possible, -secondly in revising the discussion of markup theory and practice -within the text to reflect current thinking. A few sections of the -current text (the Gentle Introduction to SGML and the discussion of -Extended Pointer syntax are two examples) will need substantial -rewriting. For the most part, however, we think the Guidelines have -stood the test of time well and can be recommended to a new generation of -text encoders scarcely born at the time they were first formulated. -

-

Lou Burnard and Steve De Rose (Editors)

-

Oxford and Providence, May 2001.

-
-
-Introductory Note (May 1999) -

No work of the size and complexity of the TEI -Guidelines could reasonably be expected to be error-free on -publication, nor to remain long uncorrected. It has however taken rather longer -than might have been anticipated to complete production of the present -corrected reprint of the first edition, for which we present our apologies, -both to the many individuals and institutions whose enthusiastic adoption and -promotion of the TEI encoding scheme have ensured its continued survival in the -rapidly changing world of digital scholarship, and also to the many helpfully -critical users whose assiduous uncovering and reporting of our errors have made -possible the present revision.

-

At its first meeting in Bergen, in June 1996, the TEI Technical Review -Committee (TRC) approved the setting up of a small working committee to oversee the -production of a revised edition of the TEI -Guidelines, to include corrections of as many as possible of the -`corrigible errors' notified to the editors since publication -of the first edition in May 1994, the bulk of which are summarized in a TEI -working paper (TEI EDW67, available from the TEI web site).

-

During the spring of 1997, this TRC Core Subcommittee reviewed nearly 200 -comments and proposals which the editors had collected from public debate and -discussion over the preceding two years, and provided invaluable technical -guidance in disposition of them. We are glad to take this opportunity of -expressing our thanks to this subcommittee, whose members were Elli Mylonas, -Dominic Dunlop, and David T. Barnard.

-

The work of making the corrections and regenerating the text proceeded - rather fitfully during 1998 and 1999, largely because of increasing demands on - the editors' time from their other responsibilities. With the - establishment of the new TEI Consortium, it is be hoped that maintenance of the - Guidelines will be placed on a more secure footing. Some specific areas in which we - anticipate future revisions being carried out are listed below.

-
-Typographic Corrections Made - - examples of TEI markup throughout the text were all checked against the - relevant DTD fragment and an embarassingly large number of tagging errors - corrected; - various minor typographic and spelling errors were corrected; - the corrigible errors listed in working paper TEI EDW67 were all - corrected: some of these required specific changes to the DTD which are listed - in the next section. - -
-
-Specific Changes in the DTD -

A major goal of this revision was to avoid changes which might invalidate - existing data, even where existing constructs seemed erroneous in retrospect. - To that end, wherever changes have been made in content models for existing - elements, they have as far as possible been made so that the DTD will now - accept a superset of what was previously legal. Only one new element - (ab) has been added.

-

Where possible, a few content models have been changed in such a way as to - facilitate conversion to XML, but XML compatibility is - not a goal - of this revision.

-

Brief details of all changes made in the DTD follow: - - Several changes were made in class membership, in order to correct - unreachability problems. Specifically: - - elements geogName, persName, - placeName were added to the m.data class; - geogName and placeName were removed from the - m.placepart class; - the elements addSpan, delSpan, gap, were - added to the m.Edit class; - a new class m.editIncl was defined, with members - addSpan, delSpan, and gap; this class was then added - to the global inclusion class -m.globIncl along with - anchor (erroneously a member of the -m.Seg class, from - which it is now removed), m.metadata and m.refsys; - - - added name element to m.addrPart class; - added dateline to m.divtop and - m.divbot classes; - added epilogue and castList to - m.dramafront class; - added divGen to m.front class; - added dateline to m.divtop and - m.divtop classes; - added u element to a.declaring class; - defined new class m.fmchunk (front matter chunk), - comprising argument, byline, docAuthor, - docDate, docEdition, docImprint, docTitle, - epigraph, head, and titlePart for use in - simplification of the content model for front element; - defined new element ab (anonymous block), and added it to the - m.chunk class; - corrected an error whereby global attributes were not properly defined - for elements specifying a non-default value for any of the - a.global attributes: elements affected include: foreign, - hi, del, pb, lb, cb, - language, anchor, and when; - changed content models to permit empty list and empty - availability elements; - changed content model for series element to permit #PCDATA; - - changed content model for setting element to permit - date element as a direct child; - added a key attribute to the distance element, - for consistency with other elements in its class; - changed content model for orgName element to make it more - consistent with e.g. persName; - changed content model for opener element to include - argument, byline, and epigraph; - changed content models for app, rdgGrp, and - wit elements; - revised attributes on hand element.

-

A number of content models were changed with a view to -easing the creation of an XML compatible version of the -Guidelines. Specifically: - removed ampersand connectors from cit, -respStmt, publicationStmt, and graph; -changed the mixed content models for sense, re, persName, -placeName, geogName, dateStruct, timeStruct, and dateline -to make them XML-conformant. -

-
-
-Outstanding Errors -

A small number of other known problems remain uncorrected in this version - and are briefly listed below. Please watch the TEI mailing list for - announcements of their correction.

- -elements of class model.inter don't always behave - as they should (e.g. one cannot insert a table before - anything else in a div); - - some mixed-content problems consequent on the definition of - macro.specialPara need to be addressed systematically; - in particular, the treatment of list items or notes which contain - several paragraphs continues to surprise many users: no - whitespace is allowed between the paragraphs; - the resp attributes on editorial elements are not - consistently defined; - the discussions of DTD invocation, and the DTD itself, all use - system identifiers instead of formal public identifiers. - -

Our next priority however will be the production of a fully XML-compliant version - of the TEI DTD, work on which is already well advanced.

-C.M. Sperberg-McQueen and Lou Burnard, May 1999 -
-
-
Preface (April 1994) -

These Guidelines are the result of over five years' effort by -members of the research and academic community within the -framework of an international cooperative project called the Text -Encoding Initiative (TEI), established in 1987 under the joint -sponsorship of the Association for Computers and the Humanities, -the Association for Computational Linguistics, and the Association -for Literary and Linguistic Computing. -

-

The impetus for the project came from the humanities computing -community, which sought a common encoding scheme for complex textual -structures in order to reduce the diversity of existing encoding -practices, simplify processing by machine, and encourage the sharing of -electronic texts. It soon became apparent that a sufficiently flexible -scheme could provide solutions for text encoding problems generally. The -scope of the TEI was therefore broadened to meet the varied encoding -requirements of any discipline or application. Thus, the TEI became the -only systematized attempt to develop a fully general text encoding model -and set of encoding conventions based upon it, suitable for processing -and analysis of any type of text, in any language, and intended to serve -the increasing range of existing (and potential) applications and use. -

-

What is published here is a major milestone in this effort. It -provides a single, coherent framework for all kinds of text encoding -which is hardware-, software- and application-independent. Within this -framework, it specifies encoding conventions for a number of key text -types and features. The ongoing work of the TEI is to extend the -scheme presented here to cover additional text types and features, as -well as to continue to refine its encoding recommendations on the -basis of extensive experience with their actual application and use. -

-

We therefore offer these Guidelines to the user community for use in -the same spirit of active collaboration and cooperation with which -they have so far been developed. The TEI is committed to actively -supporting the wide-spread and large-scale use of the Guidelines -which, with the publication of this volume, is now for the first time -possible. In addition, we anticipate that users of the TEI Guidelines -will in some instances adapt and extend them as necessary to suit -particular needs; we invite such users to engage in the further -development of these Guidelines by working with us as they do so. -

-

Like any standard which is actually used, these Guidelines do not -represent a static finished work, but rather one which will evolve -over time with the active involvement of its community of users. We -invite and encourage the participation of the user community in -this process, in order to ensure that the TEI Guidelines become and -remain useful in all sorts of work with machine-readable texts. -

-

This document was made possible in part by financial support from -the U.S. National Endowment for the Humanities, an independent federal -agency; Directorate General XIII of the Commission of the European -Communities; the Andrew W. Mellon Foundation; and the Social Science -and Humanities Research Council of Canada. Direct and indirect -support has also been received from the University of Illinois at -Chicago, the Oxford University Computing Services, the University of -Arizona, the University of Oslo and Queen's University (Kingston, -Ont.), Bellcore (Bell Communications Research), the Istituto di -Linguistica Computazionale (C.N.R.) Pisa, the British Academy, and -Ohio State University, as well as the employers and host institutions -of the members of the TEI working committees and work groups listed in -the acknowledgments. -

-

The production of this document has been greatly facilitated by the -willingness of many software vendors to provide us with evaluation -versions of their products. Most parts of this text have been processed -at some time by almost every currently available SGML-aware software -system. In particular, we gratefully acknowledge the -assistance of the following vendors: - -Berger-Levrault AIS s.a. (for Balise); -E2S n.v. (for E2S Advanced SGML Editor); -Electronic Book Technology (for DynaText); -SEMA Group and Yard Software (for Mark-It and Write-It); -Software Exoterica (for CheckMark and Xtran); -SoftQuad, Inc., (for Author/Editor and RulesBuilder); -Xerox Corporation (for Ventura Publisher). -

-

Details of the software actually used to produce the current document -are given in the colophon at the end of the work.

-
-
Acknowledgments -

Many people have given of their time, energy, expertise, and support -in the creation of this document; it is unfortunately not possible to -thank them all adequately. Below are listed those who have served as -formal members of the TEI's Work Groups and Working Committees during -its six-year history; others not so officially enfranchised also -contributed much to the quality of the result.

-

The editors take this opportunity to acknowledge our debt to those -who have patiently endured and corrected our misunderstandings of their -work; we hope that they will feel the wait has not been in vain. For -any errors and inconsistencies remaining, we must accept responsibility; -any virtue in what is here presented, we gladly ascribe to the energies -of the keen intellects listed below.

-

C. M. Sperberg-McQueen and Lou Burnard

-
TEI Working Committees (1990-1993)Not all members listed were able to serve throughout the development -of the Guidelines. - - -

Chair: Dominik Wujastyk (Wellcome Institute for the History of -Medicine)

-

Members 1990–1992: J. D. Byrum (Library of Congress); -Marianne Gaunt (Rutgers University); -Richard Giordano (Manchester University); -Barbara Ann Kipfer (Independent Consultant); -Hans Jørgen Marker (Danish Data Archive, Odense); -Marcia Taylor (University of Essex);

 - -

Chair: Stig Johansson (University of Oslo)

-

Members 1990–1992: Roberto Cencioni (Commission of the European -Communities); -David R. Chesnutt (University of South Carolina); -Robin C. Cover (Dallas Theological Seminary); -Steven J. DeRose (Electronic Book Technology Inc); -David G. Durand (Boston University); -Susan M. Hockey (Oxford University Computing Service); -Claus Huitfeldt (University of Bergen); -Francisco Marcos-Marin (University Madrid); -Elli Mylonas (Harvard University); -Wilhelm Ott (University of Tübingen); -Allen H. Renear (Brown University); -Manfred Thaller (Max-Planck-Institut für Geschichte, -Göttingen)

 - -

Chair: D. Terence Langendoen (University of Arizona)

-

Members 1990–1992: -Robert Amsler (Bell Communications Research); -Stephen Anderson (Johns Hopkins University); -Branimir Boguraev (IBM T. J. Watson Research Center); -Nicoletta Calzolari (University of Pisa); -Robert Ingria (Bolt Beranek Newman Inc); -Winfried Lenders (University of Bonn); -Mitch Marcus (University of Pennsylvania); -Nelleke Oostdijk (University of Nijmegen); -William Poser (Stanford University); -Beatrice Santorini (University of Pennsylvania); -Gary Simons (Summer Institute of Linguistics); -Antonio Zampolli, University of Pisa.

 - -

Chair: David T. Barnard (Queen's University)

-

Members 1990–1994: David G. Durand (Boston University); -Jean-Pierre Gaspart (Associated Consultants and -Software Engineers sa/nv); -Nancy M. Ide (Vassar College); -Lynne A. Price (Software Exoterica / Xerox PARC); -Frank Tompa (University of Waterloo); -Giovanni Battista Varile (Commission of the European Communities).

 -

In addition, the two TEI editors served ex officio on each -committee.

-

Following publication of the first draft of the TEI Guidelines (P1) -in November 1990, a number of specialist work groups were charged with -responsibility for drafting revisions and extensions, which, together -with material already presented in P1, constitute the basis of the -present work.

-

In addition, many members of the work groups listed below met on -three occasions to review the emerging proposals in detail at -technical review meetings convened by the TEI Steering Committee. -These meetings, held in Myrdal, Norway (November 1991), Chicago (May -1992) and Oxford (May 1993), were largely responsible for the -technical content and organization of the present work. Attendants at -these meetings are starred in the list below. - -Chair: Harry Gaylord* (University of Groningen); -Syun Tutiya* (Chiba University). -Chair: Peter Robinson* (Oxford University); -David Chesnutt* (University of South Carolina); -Robin Cover* (Dallas Theological Seminary); -Robert Kraft (University of Pennsylvania); -Peter Shillingsburg (Mississippi State University). -Chair: Steven J. DeRose* (Electronic Book Technologies Inc); -David Durand (Boston University); -Edward A. Fox (Virginia State University); Eve Wilson (University of -Kent). -Chair: Paul Ellison* (University of Exeter); -Anders Berglund (Independent Consultant); Dale Waldt (Thompson -Professional Publishing). -Chair: Douglas Biber* (University of Northern Arizona); -Jeremy Clear (Birmingham University); -Gunnel Engwall (University of Stockholm). -Chair: Claus Huitfeldt* (University of Bergen); -Dino Buzzetti (University of Bologna); -Jacqueline Hamesse (University of Louvain); -Mary Keeler (Georgetown University); -Christian Kloesel (Indiana University); -Allen Renear* (Brown University); -Donald Spaeth (Glasgow University). -Chair: David Robey* (University of Manchester); -Elaine Brennan* (Brown University); -David Chisholm (University of Arizona); -Willard McCarty (University of Toronto). -Chair: Elli Mylonas* (Harvard University); -John Lavagnino* (Brandeis University); -Rosanne Potter (University of Iowa). -Chair Thomas N. Corns* (University of Wales); -Christian Delcourt (University of Liège). - -Chair: D. Terence Langendoen* (University of Arizona); -Stephen R. Anderson (Johns Hopkins University); -Nicoletta Calzolari (University of Pisa); -Geoffrey Sampson* (University of Sussex); -Gary Simons* (Summer Institute of Linguistics). -Chair: Stig Johansson* (University of Oslo); -Jane Edwards (University of California at Berkeley); -Andrew Rosta (University College London). -Chair: Paul Fortier* (University of Manitoba); -Christian Delcourt (University of Liège;); -Ian Lancashire (University of Toronto); -Rosanne Potter (University of Iowa); -David Robey* (University of Manchester). - -Chair: Daniel Greenstein* (University of Glasgow); -Peter Denley (Queen Mary Westfield College, London); -Ingo Kropac (University of Graz); -Hans Jørgen Marker (Danish Data Archive, Odense); -Jan Oldervoll (University of Tromsø); -Kevin Schurer (University of Cambridge); -Donald Spaeth (Glasgow University); -Manfred Thaller (Max-Planck-Institut für Geschichte, -Göttingen).This Workgroup was jointly -sponsored by the Association for History and Computing. - -Chairs: Robert Amsler* (Bell Communications Research) and -Nicoletta Calzolari (University of Pisa); -Susan Armstrong-Warwick (University of Geneva); -John Fought (University of Pennsylvania); -Louise Guthrie (University of New Mexico); -Nancy M. Ide* (Vassar College); -Frank Tompa (University of Waterloo); -Carol Van Ess-Dykema (US Department of Defense); -Jean Veronis (University of Aix-en-Provence). -Chair: Robert Ingria* (Bolt Beranek Newman Inc); -Susan Armstrong-Warwick (University of Geneva); -Nicoletta Calzolari (University of Pisa). -Chair: Alan Melby* (Brigham Young University) -Gerhard Budin (University of Vienna); -Gregory Shreve (Kent State University); -Richard Strehlow (Oak Ridge National Laboratory); -Sue Ellen Wright (Kent State University).

-
Advisory Board -

Members of the TEI Advisory Board during the lifetime of the -project are listed below, grouped under the name of the organization -represented. - -Chad McDaniel (University of Maryland). -Elizabeth A. R. Brown (Brooklyn College, CUNY). -Jocelyn Penny Small (Rutgers University). -Allen Renear (Brown University). -Clifford A. Lynch (University of California). -1989–93: Scott Deerwester (University of Chicago); 1993- : -Martha Evens (Illinois Institute of Technology). -David Chesnutt (University of South Carolina). -1989–91: Manfred Thaller, Max-Planck-Institut für -Geschichte, Göttingen; 1991- : Daniel Greenstein (Glasgow -University). -1989–93: Wilhelm Ott (University of Tübingen); 1993- : -Winfried Bader (University of Tübingen). -Anne-Maria di Sciullo (Université du Québec -à Montréal) -Barbara Ann Kipfer (Independent Consultant). -1989–92: Betsy Kiser (OCLC); 1992- : -Deborah Bendig and Andrea Keyhani (OCLC). -J. D. Byrum Jr. (The Library of Congress). -Stephen Anderson (The Johns Hopkins University) -Randall Jones (Brigham Young University) and -Ian Lancashire (University of Toronto).

-
Steering Committee Membership -

Members of the Steering Committee of the TEI during the preparation -of this work were: - - - -1987–1993: Robert A. Amsler (Bell Communications Research); -1987–1993: Donald E. Walker (Bell Communications Research); -1993–1994: Susan Armstrong-Warwick (University of Geneva); -1994–1999: Judith Klavans (Columbia University). - - -1987–1999: Nancy M. Ide (Vassar College); -1987–1994: C. M. Sperberg-McQueen (University of Illinois at -Chicago); -1994–1999: David Barnard (Queen's University). - - -1987–1999: Susan M. Hockey (Center for Electronic Texts in the -Humanities); -1987–1999: Antonio Zampolli (University of Pisa).

-
diff --git a/P5/Source/Guidelines/fr/PrefatoryNote.xml b/P5/Source/Guidelines/fr/PrefatoryNote.xml new file mode 120000 index 0000000000..be1a998c63 --- /dev/null +++ b/P5/Source/Guidelines/fr/PrefatoryNote.xml @@ -0,0 +1 @@ +../en/./PrefatoryNote.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/REF-ATTRIBUTES.xml b/P5/Source/Guidelines/fr/REF-ATTRIBUTES.xml deleted file mode 100644 index fdb0773d90..0000000000 --- a/P5/Source/Guidelines/fr/REF-ATTRIBUTES.xml +++ /dev/null @@ -1,15 +0,0 @@ - - - - - - - -
- Attributes -
- About the Attributes Appendix -

This appendix gives you a list of attributes and links to the reference pages for the elements on which they appear. There are distinctly-named attributes in revision of TEI P5 of the TEI Guidelines.

- - -
diff --git a/P5/Source/Guidelines/fr/REF-ATTRIBUTES.xml b/P5/Source/Guidelines/fr/REF-ATTRIBUTES.xml new file mode 120000 index 0000000000..d3fc379a64 --- /dev/null +++ b/P5/Source/Guidelines/fr/REF-ATTRIBUTES.xml @@ -0,0 +1 @@ +../en/REF-ATTRIBUTES.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/REF-CLASSES-ATTS.xml b/P5/Source/Guidelines/fr/REF-CLASSES-ATTS.xml deleted file mode 100644 index 0f003ed34c..0000000000 --- a/P5/Source/Guidelines/fr/REF-CLASSES-ATTS.xml +++ /dev/null @@ -1,16 +0,0 @@ - - - - - - - -
- Attribute Classes -
- About the Attribute Classes Appendix -

This appendix gives you a list of attribute classes and links to the reference pages for them. There are distinctly-named attribute classes in revision of TEI P5 of the TEI Guidelines.

- - - -
diff --git a/P5/Source/Guidelines/fr/REF-CLASSES-ATTS.xml b/P5/Source/Guidelines/fr/REF-CLASSES-ATTS.xml new file mode 120000 index 0000000000..8762489a7f --- /dev/null +++ b/P5/Source/Guidelines/fr/REF-CLASSES-ATTS.xml @@ -0,0 +1 @@ +../en/REF-CLASSES-ATTS.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/REF-CLASSES-MODEL.xml b/P5/Source/Guidelines/fr/REF-CLASSES-MODEL.xml deleted file mode 100644 index 4a8511a445..0000000000 --- a/P5/Source/Guidelines/fr/REF-CLASSES-MODEL.xml +++ /dev/null @@ -1,15 +0,0 @@ - - - - - - - -
- Model Classes -
- About the Model Classes Appendix -

This appendix gives you a list of model classes and links to the reference pages for them. There are distinctly-named model classes in revision of TEI P5 of the TEI Guidelines.

- - -
diff --git a/P5/Source/Guidelines/fr/REF-CLASSES-MODEL.xml b/P5/Source/Guidelines/fr/REF-CLASSES-MODEL.xml new file mode 120000 index 0000000000..bfc16102dc --- /dev/null +++ b/P5/Source/Guidelines/fr/REF-CLASSES-MODEL.xml @@ -0,0 +1 @@ +../en/REF-CLASSES-MODEL.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/REF-ELEMENTS.xml b/P5/Source/Guidelines/fr/REF-ELEMENTS.xml deleted file mode 100644 index 8db9fdcad3..0000000000 --- a/P5/Source/Guidelines/fr/REF-ELEMENTS.xml +++ /dev/null @@ -1,22 +0,0 @@ - - - - - - - -
- Elements -
- About the Elements Appendix -

This appendix gives you links to reference pages for all elements in the TEI Guidelines. - There are TEI elements in revision of - TEI P5 of the TEI Guidelines.

-

The elements listed here are in the TEI Namespace: - http://www.tei-c.org/ns/1.0 - unless otherwise noted on that element's reference page. -

- -
- -
diff --git a/P5/Source/Guidelines/fr/REF-ELEMENTS.xml b/P5/Source/Guidelines/fr/REF-ELEMENTS.xml new file mode 120000 index 0000000000..187574ad0a --- /dev/null +++ b/P5/Source/Guidelines/fr/REF-ELEMENTS.xml @@ -0,0 +1 @@ +../en/REF-ELEMENTS.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/REF-MACROS.xml b/P5/Source/Guidelines/fr/REF-MACROS.xml deleted file mode 100644 index 27437ab765..0000000000 --- a/P5/Source/Guidelines/fr/REF-MACROS.xml +++ /dev/null @@ -1,15 +0,0 @@ - - - - - - - -
- Datatypes and Other Macros -
- About the Datatypes and Macros Appendix -

This appendix gives you a list of datypes and links to the reference pages for them. There are distinctly-named data specifications in revision of TEI P5 of the TEI Guidelines.

- - -
diff --git a/P5/Source/Guidelines/fr/REF-MACROS.xml b/P5/Source/Guidelines/fr/REF-MACROS.xml new file mode 120000 index 0000000000..05ba029c5b --- /dev/null +++ b/P5/Source/Guidelines/fr/REF-MACROS.xml @@ -0,0 +1 @@ +../en/REF-MACROS.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/SA-LinkingSegmentationAlignment.xml b/P5/Source/Guidelines/fr/SA-LinkingSegmentationAlignment.xml deleted file mode 100644 index 48d6e5827d..0000000000 --- a/P5/Source/Guidelines/fr/SA-LinkingSegmentationAlignment.xml +++ /dev/null @@ -1,3505 +0,0 @@ - - - - -
- Linking, Segmentation, and Alignment - -

This chapter discusses a number of ways in which encoders may -represent analyses of the structure of a text which are not -necessarily linear or hierarchic. The module defined by this chapter -provides for the following common requirements: - - to link disparate elements - using the xml:id attribute (section ); - to link disparate elements without using the - xml:id attribute (sections and ); - to segment text into elements convenient for - the encoder and to mark arbitrary points within documents (section - ); - to represent correspondence or - alignment among groups of text elements, both those - with content and those which are empty (section );We use the term alignment as a - special case for the more general notion of correspondence. Using A - as a short form for an element with its attribute xml:id - set to the value A, and suppose elements A1, A2, - and A3 occur in that order and form one group, while elements B1, - B2, and B3 occur in that order and form another group. Then a - relation in which A1 corresponds to B1, A2 corresponds to B2, and - A3 corresponds to B3 is an alignment. On the other hand, a - relation in which A1 corresponds to B2, B1 to C2, and C1 to A2 is - not an alignment. - to synchronize elements of a - text, that is to represent temporal correspondences and alignments - among text elements (section ) and also to - align them with specific points in time (section ); - to specify that one text element is identical - to or a copy of another (section ); - to aggregate possibly noncontiguous elements - (section ); - to specify that different elements are - alternatives to one another and to express - preferences among the alternatives (section ); - to store markup separately from the data it describes - or is related to (section ); - to associate segments of a text - with interpretations or analyses of their significance (section - ); - to group together elements used to provide stand-off - annotation, including contextual information (section ). -

-

These facilities all use the same set of techniques based on the -W3C XPointer framework () This provides a -variety of schemes; the most convenient of -which, and that recommended by these Guidelines, makes use of the -global xml:id attribute, as defined in section , and introduced in the section of -titled . When the linking module is included in a schema, the -attribute class att.global is extended to -include eight additional attributes to support the various kinds of -linking listed above. Each of these attributes is introduced in the -appropriate section below. In addition, for many of the topics -discussed, a choice of methods of encoding is offered, ranging from -simple but less general ones, which use attribute values only, to more -elaborate and more general ones, which use specialized elements.

-
- Links -

We say that one element points to - others if the first has an attribute whose value is a reference to - the others: such an element is called a pointer - element, or simply a pointer. Among the - pointers that have been introduced up to this point in these - Guidelines are note, ref, and ptr. - These elements all indicate an association between one place in - the document (the location of the pointer itself) and one or more - others (the elements whose identifiers are specified by the - pointer's target attribute). The module described in - this chapter introduces a - variation on this basic kind of pointer, known as a - link, which specifies both ends - of an association. In addition, we define a syntax for - representing locations in a document by a variety of means not - dependent on the use of xml:id attributes.

-
-Pointers and Links -

In section we introduced the simplest -pointer elements, ptr and ref. Here we -introduce additionally the link element, which -represents an association between two (or more) locations by -specifying each location explicitly. Its own location is -irrelevant to the intended linkage. All three elements use the -attribute target, provided by the att.pointing class as a means of indicating the -location or locations referenced or pointed to. - - - - -The ptr element may be called a pure -pointer, because its primary function is simply to point. A -pointer sets up a connection between an -element (which, in the case of a pure pointer, is -simply a location in a document), and one or more others, known -collectively as its target. The ptr and -ref elements point, conceptually, at a single target, even -if that target may be discontinuous in the document. The link -element specifies at least two targets and represents an association -between them, independent of its own location.

-

These three elements also share a common set of attributes, derived -from the att.pointing and att.typed classes: - - - -

-

Double connection among elements could also be expressed by a -combination of pointer elements, for example, two ptr -elements, or one ptr element and one note -element. All that is required is that the value of the -target (or other pointing) attribute of the one be -the value of the xml:id attribute of the other. What -the link element accomplishes is the handling of double -connection by means of a single element. Thus, in the following -encoding: - -sa-p1 points to sa-p2, and sa-p2 -points to sa-p1. This is logically -equivalent to the more compact encoding: -

-

As noted elsewhere, the target attribute may take as value one or -more URI reference. In the simplest case, each such reference will -indicate an element in the current document (or in some other -document), for example by supplying the value used for its global -xml:id attribute. It may however carry as value any form of -URI, such as a URL pointing to some other document or location on the -Internet. Pointing or linking to external documents and pointing and -linking where identifiers are not available is described below in -section .

-
-
-Using Pointers and Links -

As an example of the use of mechanisms which establish -connections among elements, consider the practice (common in -18th century English verse and elsewhere) of providing footnotes -citing parallel passages from classical authors.

-The -figure shows the original page of Pope's Dunciad -which is discussed in the text.
Such -footnotes can of course simply be encoded using the -note element (see section ) without -a target attribute, placed adjacent to the passage to -which the note refers:The type -attribute on the note is used to classify the notes using the -typology established in the Advertisement to the work: The -Imitations of the Ancients are -added, to gratify those who either never read, or may have -forgotten them; together with some of the Parodies, and -Allusions to the most excellent of the Moderns. In the -source text, the text of the poem shares the page with two sets -of notes, one headed Remarks and the other -Imitations. -(Diff'rent our parties, but with equal grace -The Goddess smiles on Whig and Tory race, - - Virg. Æn. 10. - -Tros Rutulusve fuat; nullo discrimine habebo. -—— Rex Jupiter omnibus idem. - - 'Tis the same rope at sev'ral ends they twist, -To Dulness, Ridpath is as dear as Mist) -

-

This use of the note element can be called -implicit pointing (or implicit -linking). It relies on the juxtaposition of the note to -the text being commented on for the connection to be understood. -If it is felt that the mere juxtaposition of the note to the -text does not make it sufficiently clear exactly what text -segment is being commented on (for example, is it the -immediately preceding line, or the immediately preceding two -lines, or what?), or if it is decided to place the note at some -distance from the text, then the pointing or the linking must be -made explicit. We now consider various methods for doing -that.

-

Firstly, a ptr element might be placed at an -appropriate point within the text to link it with the -annotation: -(Diff'rent our parties, but with equal grace -The Goddess smiles on Whig and Tory race, - -'Tis the same rope at sev'ral ends they twist, -To Dulness, Ridpath is as dear as Mist) - - Virg. Æn. 10. - -Tros Rutulusve fuat; nullo discrimine habebo. -—— Rex Jupiter omnibus idem. - - - -The note element has been given an arbitrary identifier -(note3.284) to enable it to be specified -as the target of the pointer element. Because there is nothing -in the text to signal the existence of the annotation, the -rend attribute has been given the value unmarked.

-

Secondly, the target attribute of the -note element can be used to point at its associated -text, provided that an xml:id attribute has been -supplied for the associated text: -(Diff'rent our parties, but with equal grace -The Goddess smiles on Whig and Tory race, -'Tis the same rope at sev'ral ends they twist, -To Dulness, Ridpath is as dear as Mist) - - -Given this encoding of the text itself, we can now link the various -notes to it. In this case, the note -itself contains a pointer to the place in the text which it is -annotating; this could be encoded using a ref -element, which bears a target attribute of its own -and contains a (slightly misquoted) extract from the text marked -as a quote element: - - Verse 283–84. - - ——. With equal grace - Our Goddess smiles on Whig and Tory race. - - - Virg. Æn. 10. - -Tros Rutulusve fuat; nullo discrimine habebo. -—— Rex Jupiter omnibus idem. - - -

-

Combining these two approaches gives us the following -associations: - - a pointer within one line indicates the note - the note indicates the line - a pointer within the note indicates the line - -Note that we do not have any way of pointing from the line itself to -the note: the association is implied by containment of the pointer. We -do not as yet have a true double link between text and note. To -achieve that we will need to supply identifiers for the annotations as -well as for the verse lines, and use a link element to -associate the two. Note that the ptr element and the -target attribute on the note may now be dispensed -with: - - - Verse 283–84. - - ——. With equal grace - Our Goddess smiles on Whig and Tory race. - - Virg. Æn. 10. - -Tros Rutulusve fuat; nullo discrimine habebo. -—— Rex Jupiter omnibus idem. - - - -

-

The target attribute of the link element -here bears the identifier of the note followed by that of the -verse line. We could also allocate an -identifier to the reference within the note and encode the -association between it and the verse line in the same way: - - Verse 283–84. - - ——. With equal grace - Our Goddess smiles on Whig and Tory race. - - - - - - -Indeed, the two links could be combined into one, as -follows: -

-
-
-Groups of Links -

Clearly, there are many reasons for which an encoder might -wish to represent a link or association between different -elements. For some of them, specific elements are provided in -these Guidelines; some of these are discussed elsewhere in the -present chapter. The link element is a general purpose -element which may be used for any kind of association. The -element linkGrp may be used to group links of a -particular type together in a single part of the document; such -a collection may be used to represent what is sometimes referred -to in the literature of Hypertext as a web, a term -introduced by the Brown University FRESS project in 1969, and not to -be confused with the World Wide Web. - -As a member of the class att.pointing.group, this element shares the -following attributes with other members of that class: - -It is also a member of the att.pointing -and att.typed classes, and therefore also carries the attributes specified in -section above, in particular the -type attribute.

-

The linkGrp element provides a convenient way of -establishing a default for the type attribute on a -group of links of the same type: by default, the type -attribute on a link element has the same value as that -given for type on the enclosing linkGrp.

-

Typical software might hide a web entirely from the user, but -use it as a source of information about links, which are -displayed independently at their referenced locations. -Alternatively, software might provide a direct view of the link -collection, along with added functions for manipulating the -collection, as by filtering, sorting, and so on. -To continue our previous example, this text contains many other -notes of a kind similar to the one shown above. Here are a few -more of the lines to which annotations have to be attached, -followed by the annotations themselves: -A place there is, betwixt earth, air and seas -Where from Ambrosia, Jove retires for ease. - -Sign'd with that Ichor which from Gods distills. - - - Ovid Met. 12. - -Orbe locus media est, inter terrasq; fretumq; -Cœlestesq; plagas — - - - - Alludes to Homer, Iliad 5 ... - -To avoid having -to repeat the specification of type as imitation on each note, -we may specify it once for all on a linkGrp element -containing all links of this type. - - - - - -

-

Additional information for applications that use -linkGrp elements can be provided by means of special -attributes. First, the domains attribute can be used -to identify the text elements within which the individual -targets of the links are to be found. Suppose that the text -under discussion is organized into a body element, -containing the text of the poem, and a back element -containing the notes. Then the domains attribute can -have as its value the identifiers of the body and the -back, to enable an application to verify that the link -targets are in fact contained by appropriate elements, or to -limit its search space: - - - - - - - - - -

-

Note that there must be a single parent element for each -domain; if some notes are contained by a -section with identifier dunnotes, and -others by a section with identifier dunimits, -an intermediate pointer must be -provided (as described in section ) within -the linkGrp and its identifier used instead.

-

Next, the targFunc attribute can be used to -provide further information about the role or function of the -various targets specified for each link in the group. The value -of the targFunc attribute is a list of names -(formally, name tokens), one for each of the targets in the -link; these names can be chosen freely by the encoder, but their -significance should be documented in the encoding description in -the header.Since no special element is -provided for this purpose in the present version of these -Guidelines, the information should be supplied as a series of -paragraphs at the end of the encodingDesc element -described in section . In the current -example, we might think of the note as containing the source of the imitation and the verse line -as containing the goal of the -imitation. Accordingly, we can specify the linkGrp in -the preceding example thus: - - - - - - -

- - - - -
-
-Intermediate Pointers -

In the preceding examples, we have shown various ways of -linking an annotation and a single verse line. However, the -example cited in fact requires us to encode an association -between the note and a pair of verse lines (lines -284 and 285); we call these two lines a span.

-

There are a number of possible ways of correcting this error: one -could use the target attribute to indicate one end of the -span and the special purpose targetEnd attribute on the -note element to point to the other. Another possibility might -be to create an element which represents the whole span itself and -assign that an xml:id attribute, which can then be linked -to the note and ref elements. This could be done -using for example the lg element defined in section or the virtual join -element discussed in section .

-

A third possibility would be to use an -intermediate pointer as follows: - - -When the target attribute of a ptr or -ref element specifies more than one element, the -indicated elements are intended to be combined or aggregated in -some way to produce the object of the pointer. (Such aggregation -is however the task of a processing application, and cannot be -defined simply by the markup). The xml:id attribute -of the ptr then provides an identifier which can be linked to the -note and ref elements: - -

-

The all value of evaluate is used on the -link element to specify that any pointer encountered as -a target of that element is itself evaluated. If -evaluate had the value none, the link target would be the pointer -itself, rather than the objects it points to.

-

Where a linkGrp element is used to group a -collection of link elements, any intermediate pointer -elements used by those link elements should be included -within the linkGrp.

-
-
-
- Pointing Mechanisms -

This section introduces more formally the pointing mechanisms - available in the TEI. In addition to those - discussed so far, the TEI provides methods of pointing: - -into documents other than the current document; -to a particular element in a document other than the -current document using its xml:id; -to a particular element whether in the current document or -not, using its position in the XML element tree; -at arbitrary content in any XML document using TEI-defined -XPointer schemes. - -

-

All TEI attributes used to point at something else are declared as -having the datatype teidata.pointer, which -is defined as a URI referenceThe URI (Universal -Resource Indicator) is defined in RFC 3986; the -cases so far discussed are all simple examples of a URI -reference. Another familiar example is the mechanism used in XHTML to -create represent hypertext links by means of the XHTML href attribute. A URI reference can reference the -whole of an -XML resource such as a document or an XML element, or a -sub-portion of such a resource, identified by means of an appropriate fragment -identifier. Technically speaking, the fragment -identifier is that portion of a URI reference following the -first unescaped # character; in practice, it provides a means -of accessing some part of the resource described by the URI which is -less than the whole.

-

The first three of the following subsections provide only a - brief overview and some examples of the W3C mechanisms - recommended. More detailed information on the use of these - mechanisms is readily available elsewhere.

-
-Pointing Elsewhere -

Like the ubiquitous if misnamed XHTML pointing attribute href, the TEI pointing attributes can point to a -document that is not the current document (the one that contains the -pointing element) whether it is in the same local filesystem as the -current document, or on a different system entirely. In either case, -the pointing can be accomplished absolutely (using the entire address -of the target document) or relatively (using an address relative to -the current base URI in force). The current base -URI is defined according to Marsh -and Tobin 2009. If there is none, the base URI is that of the current -document. In common practice the current base URI in force is likely -to be the value of the xml:base attribute of the closest -ancestor that has one. However this may not be the case, since -xml:base attributes are accumulated through the hierarchy -by concatenation of path segments, beginning at the top of the -hierarchy and proceeding down to the context node.

-

The following example demonstrates an absolute URI reference -that points to a remote document: -The current base URI in force is as defined in the - W3C XML - Base recommendation.

-

This example points explicitly to a location on the Web, -accessible via HTTP. Suppose however that we wish -to access a document stored locally in a file. Again we will -supply an absolute URI reference, but this time using a -different protocol: -This Debian package is distributed under the terms - of the GNU General Public License.

-

In the following example, we use a relative URI reference -to point to a local document: -

- - The figure shows the page from the Orbis - pictus of Comenius which is discussed in the text. -
- -Since no xml:base is specified here, the location of the resource - Images/compic.png is determined relative to the -resource indicated by the current base URI, which is the current -document. -

- - -

In the following example, however, we first change the current base -URI by setting a new value for xml:base. The resource -required is then identified by means of a relative URI: - -

- On Ancient Persian Manners -

In the very first story of The Gulistan of - Sa'di, - Sa'di relates moral advice worthy of Miss Minners ...

- -

-

As noted above, the current base URI is found on the nearest -ancestor. It is technically possible to use xml:base as a means to shorten URIs, but -this usage is not recommended. Abbreviated pointers provide a more -flexible and consistent method for creating shorthand links. -

- - -
-
-Pointing Locally -

A shorthand pointer, in which the URI consists only of -# followed by the value of an xml:id acts as a -pointer to the element in the current document with that xml:id, -as in the following example.

-
- Limitations on exclusive rights: Fair use -

Notwithstanding the provisions of - section 106, the fair use of a - copyrighted work, including such use by reproduction in copies - or phonorecords or by any other means specified by that section, - for purposes such as criticism, comment, news reporting, - teaching (including multiple copies for classroom use), - scholarship, or research, is not an infringement of copyright. - In determining whether the use made of a work in any particular - case is a fair use the factors to be considered shall - include —  - - the purpose and character of the use, including - whether such use is of a commercial nature or is for nonprofit - educational purposes; - the nature of the copyrighted work; - the amount and substantiality of the portion - used in relation to the copyrighted work as a whole; - and - the effect of the use upon the potential market - for or value of the copyrighted work. - - The fact that a work is unpublished shall not itself bar a - finding of fair use if such finding is made upon consideration - of all the above factors.

-
-This method of pointing, by referring to the xml:id of the -target element as a bare name only (e.g., #sect106) is -the simplest and often the best approach where it can be applied, i.e. where -both the source element and target element are in the same XML -document, and where the target element carries an identifier. It -is the method used extensively in previous sections of this -chapter and elsewhere in these Guidelines.

-
- -
- Using Abbreviated Pointers - -

Even in the case of relative links on the local file system, ref or target attributes may become quite lengthy and make XML code difficult to read. To deal with this problem, the TEI provides a useful method of using abbreviated pointers and documenting a way to dereference them automatically.

- -

Imagine a project which has a large collection of XML documents organized like this:

- - - anthology - - poetry - - poem.xml - - - prose - - novel.xml - - - - - references - - people - - personography.xml - - - - - - - -

If you want to link a name in the novel.xml file to a person in the personography.xml file, the link will look like this: - - - Fred - - - If there are many names to tag in a single paragraph, the XML encoding will be congested, and such lengthy links are prone to typographical error. In addition, if the project organization is changed, every relative link will have to be found and altered.

- -

One way to deal with this is to use what is often referred to as a "magic token". You could make such links using the key attribute: - - Fred - - - and document the meaning of the key using (for instance) a taxonomy element in the TEI header, as described in . However, such a link cannot be mechanically processed by an external system that does not know how to interpret it; a human will have to read the header explanation and write code explicitly to reconstruct the intended link.

- -

A more robust alternative is to use a private URI scheme. This is a method of constructing a simple, key-like token which functions as a teidata.pointer, and can therefore be used as the value of any attribute which has that datatype, such as ref and target. Such a scheme consists of a prefix with a colon, and then a value. You might, for example, use the prefix psn (for "person"), and structure your name tags like this: - - - Fred - - - How is this different from a magic token? Essentially, it isn't, except that TEI provides a structured method of dereferencing it (turning it into a computable path, such as ../../references/people/personography.xml#fred) by means of a declaration inside encodingDesc in the TEI header, using the elements and attributes for prefix declaration: - - - - - - - -

- - -

This is how you might document a private URI scheme using the psn: prefix: - - - - -

- In the context of this project, private URIs with the prefix - "psn" point to person elements in the project's - personography.xml file. -

- - - - - This specifies that where a teidata.pointer value is constructed with a psn: prefix, a regular-expression replace operation can be performed on it to construct the full or relative URI to the target document or fragment. listPrefixDef is a child of encodingDesc, and it contains any number of prefixDef elements. Each prefixDef element provides a method of dereferencing or expanding an abbreviated pointer, based on a regular expression. The ident attribute specifies the prefix to which the expansion applies (without the colon). The matchPattern attribute contains a regular expression which is matched against the component of the pointer following the first colon, and the replacementPattern provides the string which will be used as a replacement. In this example, using psn:fred, the value fred would be matched by the matchPattern, and also captured (through the parentheses in the regular expression); it would then be replaced by the value ../../references/people/personography.xml#fred (with the the $1 in the replacementPattern being replaced by the captured value). The p element inside the prefixDef can be used to provide a human-readable explanation of the usage of this prefix.

- -

Through this mechanism, any processor which encounters a teidata.pointer with a protocol unknown to it can check the listPrefixDef in the header to see if there is an available expansion for it, and if there is, it can automatically provide the expansion and generate a full or relative URI.

- -

For any given prefix, it may be useful to supply more than one expansion. For instance, in addition to pointing at the person element in the personography file, it might also be useful to point to an external source which is available on the network, representing the same information in a different way. So there might be a second prefixDef like this: - - - -

- Private URIs with the prefix "psn" can be converted to point - to a fragment on the Personography page of the project Website. -

- - - - Any number of prefixDef elements may be provided for the same prefix. A processor may decide to process one or all of them; if it processes only one, it should choose the first one with the correct ident value, so the primary or most important prefixDef for any given prefix should appear first in its parent listPrefixDef.

- -

When creating private URI schemes, it is recommended that you avoid using any existing registered prefix. A list of registered prefixes is maintained by IANA at .

- -

Note that this mechanism can also be used to dereference other abbreviated pointing systems which are based on prefixes, such as Tag URIs.

- -

The matchPattern and replacementPattern attributes are also used in dereferencing canonical reference patterns, and further examples of the use of regular expressions are shown in .

- -
- -
-TEI XPointer Schemes - -

The pointing schemes described in this chapter are part of a number of -such schemes envisaged by the W3C, which together constitute a -framework for addressing data within XML documents, known as the -XPointer Framework (Grosso et al -2003). This framework permits the definition of many other named -addressing methods, each of which is known as an XPointer -Scheme. The W3C has predefined a set of such schemes, and -maintains a register for their expansion.

- -

One important scheme, also defined by the W3C, and recommended -by these Guidelines is the xpath() pointer -scheme, which allows for any part of an XML structure to be selected -using the syntax defined by the XPath specification. This is further -discussed below, . These Guidelines also define -six other pointer schemes, which provide access to parts of an XML -document such as points within data content or stretches of data -content. These additional TEI pointer schemes are defined in sections - to below.

- -
Introduction to TEI Pointers - -

Before discussing the TEI pointer schemes, we introduce slightly -more formally the terminology used to define them. So far, we have -discussed only ways of pointing at components of the XML information -set node such as elements and attributes. However, there is often a -need in text analysis to address additional types of location such as -the point locations between -nodes, and sequences that -may arbitrarily cross the boundaries of nodes in a document. The -content of an XML document is organized sequentially as well as -hierarchically, and it makes sense to consider ranges of characters -within a document independently of the nodes to which they belong. -From the perspective of most of the pointer schemes discussed below, -a TEI document is a tree structure superimposed upon a character stream. -Nodes are entities available only in the tree, while points are available -only in the stream. For this reason, the schemes below that rely upon -character positions (string-index(), -string-range(), and match()) cannot take nodes -into account. Conversely, XPath (disregarding functions that return atomic values) is a method for locating nodes in the -tree and treats those nodes as indivisible units, meaning it is unable to address parts of nodes -in their document context.

- -

The TEI pointer scheme thus distinguishes the following -kinds of object: - - - -A node is an instance of one of the node kinds defined in -the XQuery and XPath Data Model 3.1. It represents -a single item in the XML information set for a document. For pointing -purposes, the only nodes that are of interest are Text Nodes, -Element Nodes, and Attribute Nodes. - -A Sequence follows the definition in the XPath 3.1 Data -Model, with one alteration. A Sequence is an ordered collection -of zero or more items, where an item is either a node or a partial -text node. - - -A Text Stream is the concatenation of the text nodes in a document -and behaves as though all tags had been removed. A text stream begins -at a reference node and encompasses all of the text inside that node (if any) -and all the text following it in document order. In XPath terms, this would -encompass all of the text nodes beginning at a particular node, and following -it on the following axis. - - -A Point represents a dimensionless point between nodes or characters in -a document. Every point is adjacent to either characters or elements, and -never to another point. Points can only be referenced in relation to an -element or text node in the document (i.e. something addressable by either -an XPath or a fragment identifier). Points occur either immediately before -or after an element, or at a numbered position inside a text stream. -Position zero in the stream would be immediately before the first character. -Note that points within attribute values cannot mark the beginning or end of -a range extending beyond the attribute value, because points indicate a -position within a document. Since attribute nodes are by definition un-ordered, -they cannot be said to have a fixed position. - - -

- -

The TEI recommends the following seven pointer schemes: - - -Addresses a node or node sequence using the XPath syntax. () - -addresses the point before (left) or after (right) a node or node -sequence ( and ) - -addresses a point inside a text node ( - -addresses the range between two points () - -addresses a range of a specified length starting from a -specified point () - -addresses a range which matches a specified string within a node -() - -

-

The xpath() scheme refers to the -existing XPath specification which is adopted with one modification: -the default namespace for any XPath used as a parameter to this -scheme is assumed to be the TEI namespace http://www.tei-c.org/ns/1.0. -

-

The other six schemes overlap in functionality with a W3C draft -specification known as the XPointer -scheme draft, but are individually much simpler. At the time of -this writing, there is no current or scheduled activity at the W3C -towards revising this draft or issuing it as a recommendation.

- -

A note on namespaces: The W3C defines an -xmlns() scheme (see -XPointer xmlns() Scheme) -which when prepended to a resolvable pointer allows for the definition of -namespace prefixes to be used in XPaths in subsequent pointers. TEI Pointer -schemes assume that un-prefixed element names in TEI Pointer XPaths are in the -TEI namespace, http://www.tei-c.org/ns/1.0. The use of -xmlns() is thus optional, -provided no new prefixes need to be defined. If the schemes described here -are used to address non-TEI elements, then any new prefixes to be used in -pointer XPaths may be defined using the xmlns() -scheme.

-
- -
-xpath() -

Sequence xpath(XPATH)

-

The xpath() scheme locates zero or more nodes within an XML - Information Set. The single argument XPATH is an XPath selection pattern, as - defined in XSLT - 3.0, that returns a node or sequence of nodes. XPaths returning atomic values - (e.g. substring()) are illegal in the xpath() - scheme because they represent extracted values rather than locations in the source - document. Because the schemes below involve starting at a node and navigating from there, - and because attribute nodes have no intrinsic order, XPath expressions that address - attribute nodes should be avoided in schemes other than xpath().

-

The example below, and all subsequent examples in this section refer -to the following TEI fragment: - - -

-si non habuiabui quidquam vaco -sib - cohorte mi rescribas -semper in mentementem - habeabe supra res -scriptas -auge et opto ut bene valeas
- -

-

A TEI Pointer that referenced the reg element in the -choice in line 1 of the example might look like: -#xpath(//lb[@n='1']/following-sibling::choice[1]/reg). - Note that XPath values must be assumed to start from the document root. They cannot be relative - to the element bearing the attribute that uses the pointer because TEI Pointers are URIs. Care - should be taken to ensure that XPaths used in TEI Pointers match only a single node, unless - multiple matches are desired. The examples that follow are relatively simple because the - document they refer to is short and does not contain many elements.

-

When an XPath is interpreted by a TEI processor, the -information set of the referenced document is interpreted -without any additional information supplied by any schema -processing that may or may not be present. In particular this -means that no whitespace normalization is applied to a -document before the XPath is interpreted. -

-

This pointer scheme allows easy, direct use of the most -widely-implemented XML query method. It is probably the most -robust pointing mechanism for the common situation of -selecting an XML element or its contents where an -xml:id is not present. The ability to use element -names and attribute names and -values makes xpath() pointers more -robust than the other mechanisms discussed in this section -even if the designated document changes. For durability in the -presence of editing, use of xml:id is always -recommended when possible.

-
- -
-left() -

Point left( IDREF | XPATH )

-

The left() scheme locates the -point immediately preceding the node addressed by its argument, -which is either an XPATH as defined above or an -IDREF, the value of an xml:id -occurring in the document addressed by the base URI in effect -for the pointer.

-

Example: the pointer #left(//supplied[1]) -indicates the point between the first lb and the first -supplied in the example above.

-

Example: #left(//gap[1]) indicates the point immediately before -the first gap element in line two and the string si.

-

Example: #left(line1) indicates the point immediately before -the lb n="1" element.

- -
-right() -

Point right( IDREF | XPATH )

-

The right() scheme locates the -point immediately following the node addressed by its argument.

-

Example: the pointer #right(//lb[@n='3']) -indicates the point between the third lb and the -s]]> element -in the example.

-
- -
-string-index() -

Point string-index( IDREF | XPATH, OFFSET )

-

The string-index() scheme locates a - point based on character positions in a text stream relative - to the node identified by the IDREF or XPATH parameter. The OFFSET -parameter is a positive, negative, or zero integer which determines -the position of the point. An offset of 0 represents the -position immediately before the first character in either the first -text node descendant of the node addressed in the first parameter or the -first following text node, if the addressed element contains -no text node descendants.

-

Example: #string-index(//lb[@n='2'],1) indicates the point -between the s and the i in the word si in line 2.

-

Note: The OFFSET parameter (and similarly the -LENGTH parameter found below in the string-range() -scheme) are measured in characters. What is considered a single character will -depend on the Normalization Form in use (see -UNICODE NORMALIZATION -FORMS). A letter followed by a combining diacritic counts as two -characters, but the same diacritic precombined with a letter would count -as a single character. Compare, for example, é (U+0060 -followed by U+0301) and é (>U+00E9). These are -equivalent, and a conversion between Normalization Forms C and D will -transform one into the other. This specification does not mandate a -particular Normalization Form (see ), but -users and implementers should be aware that it affects the character count -and therefore the result of evaluating pointers that rely on character -counting.

-
- -
-range() -

Sequence range( POINTER, POINTER[, POINTER, POINTER ...])

-

The range() scheme takes as parameters one -or more pairs of POINTERs, which are each members of the set IDREF, -XPATH, left(), -right(), or -string-index(). A -range() locates a (possibly non-contiguous) -sequence beginning at the first POINTER parameter and ending at the -last. If a POINTER locates a node (i.e. is an XPATH or IDREF), then -that node is a member of the addressed sequence. If a sequence addressed -by a range pointer overlaps, but does not wholly contain, an element -(i.e. it contains only the start but not the end tag or vice-versa), -then that element is not part of the sequence.

-

Range()s may address sequences of -non-contiguous nodes. For example, a range() might select text beginning -before an app, encompassing the content of a single rdg -and continuing after the app.

-

Example: #range(left(//lb[@n='3']),left(//lb[@n='4'])) indicates -the whole of line 3 from the -]]> to the point right before the -following ]]>.

-

Example: #range(right(//lb[@n='3']),string-index(//lb[@n='3'],15)) - indicates the sequence semper in mente]]> (an element, a text node, another element, and a partial text node).

-

Example: #range(string-index(//lb[@n='3'],7),string-index(//lb[@n='3'],10),string-index(//lb[@n='3'],15),string-index(//lb[@n='3'],21)) indicates -the non-contiguous sequence in mentem.

-
- -
-string-range() -

Sequence string-range(IDREF | XPATH, OFFSET, LENGTH[, OFFSET, LENGTH ...])

-

The string-range() scheme -locates a sequence based on character positions in a text stream relative -to the node identified by the first parameter. The location of the -beginning of the addressed sequence is determined precisely -as for string-index(). The OFFSET -parameter is defined as above in string-index(). -The LENGTH parameter is a positive integer that denotes -the length of the text stream captured by the sequence. As with -range(), the addressed sequence may -contain text nodes and elements. The -string-range() scheme can accept multiple -OFFSET, LENGTH pairs to address a non-contiguous sequence in much the -same way that range() can accept multiple pairs of pointers.

-

Because string-range() addresses points in the text stream, tags are -invisible to it. For example, if an empty tag like lb is -encountered while processing a string-range(), it will be included in -the resulting sequence, but the LENGTH count will not increment when -it is captured.

-

Example: #string-range(//lb[@n='5'],0,27) indicates -the whole of line 5 from the text immediately -following the lb to the point right before the closing -ab tag.

-

Example: #string-range(//lb[@n='3'],7,8) -indicates the sequence in mente.

-

Example: #string-range(//lb[@n='3'],7,3,15,6) indicates -the non-contiguous sequence in mentem.

-
- -
-match() -

Sequence match(IDREF | XPATH, 'REGEX' [, INDEX])

-

The match scheme locates a sequence based on matching the REGEX parameter -against a text stream relative to the reference node identified by the first -parameter. REGEX is a regular expression as defined by -XQuery -1.0 and XPath 2.0 Functions and Operators (Second Edition), with some -modifications: - - Because the regular expression is delimited by apostrophe - characters, any such characters (' or U+0027) - occurring inside the expression must be escaped using the URI - percent-encoding scheme %27. - Regular expressions in match() are assumed to - operate in single-line mode. The end of the string to be matched - against is either the end of the text contained by the element in the - first parameter or the end of the document, if that parameter - indicates an empty element. The meta-character ^ - therefore matches the beginning of the text stream inside or following - the reference node, and the meta-character $ matches the - end of that stream. - - -The optional INDEX parameter is an integer greater than 0 which specifies which -match should be chosen when there is more than one possibility. If omitted, the -first match in the text stream will be used to resolve the match().

-

Like string-range(), match() may capture elements -in the indicated sequence, even though they are ignored for purposes of evaluating -the match.

-

Example: #match(//lb[@n='5'],'opto.*valeas') indicates the sequence -t bene valeas]]> in -line 5.

-

Example: #match(//lb[@n='3'],'semper') would indicate the -word semper, but would not capture the unclear elements -in semper]]>, just -their text children.

-
-
-
-Canonical References - -

By canonical reference we mean any means -of pointing into documents, specific to a community or -corpus. For example, biblical scholars might understand Matt -5:7 to mean the book called Matthew, chapter -5, verse 7. They might then wish to translate the string -Matt 5:7 into a pointer into a TEI-encoded document, -selecting the element which corresponds to the seventh -div element within the fifth div element -within the div element with the n attribute -valued Matt.

-

Several elements in the TEI scheme (gloss, -ptr, ref, and term) bear a special -attribute, cRef, just for this purpose. Using the -system described in this section, an encoder may specify -references to canonical works in a discipline-familiar format, -and expect software to derive a complete URI from it. The value -of the cRef attribute is processed as described in -this section, and the resulting URI reference is treated as if -it were the value of the target attribute. The -cRef and target attributes are mutually -exclusive: only one or the other may be specified on any given -occurrence of an element.

-

For the cRef attribute to function as required, a mechanism is needed to define the -mapping between (for example) the book called -Matt and the part of the XML structure which -corresponds with it. This is provided by the refsDecl element in the TEI header, -which contains an algorithm for translating a canonical reference string -(like Matt 5:7) into a URI such as #xpath(//div[@n='Matt']/div[5]/div[7]). The -refsDecl element is described in section ; the following example is discussed in more - detail below in section . An alternative and less verbose method is described in section . - - -

This pointer pattern extracts and references the book, -chapter, and verse parts of a biblical reference.

- - -

This pointer pattern extracts and references the book and -chapter parts of a biblical reference.

- - -

This pointer pattern extracts and references just the book -part of a biblical reference.

- - -

-

When an application encounters a canonical reference as the -value of cRef attribute, it might follow this sequence of -specific steps to transform it into a URI reference: - - Ascertain the correct refsDecl - following the rules summarized in section . - For each cRefPattern element encountered in - the appropriate refsDecl, in the order encountered: - - match the value of the cRef attribute to the regular - expression found as the value of the matchPattern - attribute - if the value of the cRef attribute matches: - - take the value of the replacementPattern - attribute and substitute the back references ($1, $2, - etc.) with the corresponding matched substrings - the result is taken as if it were a relative or - absolute URI reference specified on the target - attribute; i.e., it should be used as is or combined with - the current xml:base attribute value as usual - no further processing of this value of the cRef - attribute against the refsDecl should take place - - - if, however, the value of the cRef attribute does not match - the regular expression specified in the value of the matchPattern attribute, - proceed to the next cRefPattern - - - If all the cRefPattern elements are - examined in turn and none matches, the pointer fails. -

-

The regular expression language used as the value of the -matchPattern attribute is that used for the -pattern facet of the World Wide Web Consortium's -XML Schema Language in an Appendix to -XML Schema Part 2.As always -seems to be the case, no two regular expression languages are -precisely the same. For those used to Perl regular expressions, -be warned that while in Perl the pattern tei -matches any string that contains tei, in -the W3C language it only matches the string tei. -The value of the replacementPattern attribute is simply a string, -except that occurrences of $1 through $9 are -replaced by the corresponding substring match. Note that since a -maximum of nine substring matches are permitted, the string -$18 means the value of the first matched substring -followed by the character 8 as opposed to the -eighteenth matched substring. If there is a need for an -actual string including a dollar sign followed by a digit that is -not supposed to be replaced, the dollar sign should be written -as $$. Implementations must convert $$ -to $ during processing.

-
- Worked Example -

Let us presume that with the example refsDecl - above, an application comes across a cRef value of - Matt 5:7. The - application would first apply the regular expression - (.+) (.+):(.+) to Matt 5:7. This regular - expression would successfully match. The first matched - substring would be Matt, the second 5, and the - third 7. The application would then apply these - substrings to the pattern - #xpath(//div[@n='$1']/div[$2]/div[$3]), producing - #xpath(//div[@n='Matt']/div[5]/div[7]). -

-

If, however, the input string had been Matt 5, the - first regular expression would not have matched. The - application would have then tried the second, (.+) - (.+), producing a successful match, and the matched - substrings Matt and 5. It would then have - substituted those matched substrings into the pattern - #xpath(//div[@n='$1']/div[$2]) to produce a - fragment identifier indicating the referenced element.

-

If the input string had been Matt, neither the first - nor the second regular expressions would have successfully - matched. The application would have then tried the third, - (.+), producing the matched substring Matt, - and the URI Reference - #xpath(//div[@n='Matt']).

-

a cRefPattern should not reference more matched substrings. For example: - - is faulty, since only three matched - substrings would have been produced, but a fourth ($4) was - referenced.

-
-
- Complete and Partial URI Examples -

In the above example, the value of cRef was used - to generate a Fragment Identifier. An absolute URI could be generated - directly, as in the following example. - - - -

Matches most standard references to particular - chapters of the United States Code, e.g. - 11USCC7, 17 U.S.C. Chapter 3, or - 14 USC Ch. 5. Note that a leading zero is - required for the title (must be two digits), but is not - permitted for the chapter number.

- - -

Matches references to the preliminary material for a - given title, e.g. 11USCP, 17 U.S.C. - Prelim Mat, or 14 USC pm.

- - -

Matches references to the appendix of a given tile, - e.g. 05USCA, 11 U.S.C. Appendix, - or 18 USC Append.

- - - -

The example in section 10 is taken - from Subject Matter and Scope of - Copyright.

- -

-

See for another related use of the matchPattern and replacementPattern attributes.

-
-
Miscellaneous Usages -

Canonical reference pointers are intended for use by TEI - encoders. However, this specification might be useful to the - development of a process for recognizing canonical - references in non-TEI documents (such as plain text - documents), possibly as part of their conversion to TEI.

-
-
- Citation Structures -

Citation structures provide a more thorough and concise mechanism for describing canonical references - and the ways those references map on to parts of a TEI document. A citeStructure element - describes a single step in a reference, such as Matt, and may nest to handle multi-part references. -

-

The equivalent structure to the set of cRefPatterns in would be: - - - - - - - - - -

-

An application wishing to resolve a canonical reference such as Matt 5:7 might follow this procedure: - - Ascertain the correct refsDecl - following the rules summarized in section . - Begin with the outer citeStructure. If it has a delim attribute - and the reference begins with the value of delim then take the portion of - the reference after the value of delim as input for the next child citeStructure. - For each nested citeStructure, if the input reference string contains the value - of the delim, then split the string on the value of the delim attribute. - If the input string does not contain delim, then stop. Take the portion of the input - string after the value of delim and use it as the input string for the child citeStructure. - After processing the outer citeStructure, the output will be ('Matt 5:7'), after - the second, ('Matt', '5:7'). The end result will be a - sequence like ('Matt','5','7'). - For each item in the resulting sequence, resolve the matching node by evaluating - the XPath in match with the predicate found in use, using the - context of the previously matched node, if any. Start with the outer citeStructure - and move to the next child citeStructure for each step in the sequence. For - example, for the first citeStructure, we could construct an XPath - //div[@n='Matt']. The full XPath after the reference Matt 5:7 is resolved will be - //div[@n='Matt']/div[@n='5']/div[@n='7']. - - One advantage citeStructure has is that it can be used to generate canonical - references, using the declared citation structure to query the text structure. This means it is - possible to automatically produce a list of resolvable citations for a TEI document. It also - enables the automatic breaking of documents into smaller chunks for presentation and automated - generation of tables of contents.

-

Citation structures may in addition specify how informational properties are to be extracted from the - document sections they identify, using the citeData element. For example, if a TEI document - is divided into chapters with a div per chapter and those chapters have titles, contained in - head elements, then we might declare a citation structure for the document thus: - - - - - -

-

This specifies that chapter references are given in the form ch. n, where n - is the position of the div in the body of the document, and that we may obtain - the title of the chapter (identified by the Dublin Core property title) from the chapter - heading. This would, for example, enable the automated generation of a chapter listing for the document.

-
-
-
-
- Blocks, Segments, and Anchors - -

In this section, we discuss three general purposes elements which -may be used to mark and categorize both a span of text and a point -within one. These elements have several uses, most notably to provide -elements which can be given identifiers for use when aligning or -linking to parts of a document, as discussed elsewhere in this -chapter. They also provide a convenient way of extending the semantics -of the TEI markup scheme in a theory-neutral manner, by providing for -two neutral or anonymous elements to which the -encoder can add any meaning not supplied by other TEI defined -elements. - - - - - - The elements anchor, ab, and seg are members of - the class att.typed, from which they - inherit the following attributes: - - - -The elements ab, and seg are members of - the class att.fragmentable, from which they - inherit the following attribute: - - - - The seg element is also a member of the class att.segLike from which it inherits the - following attribute: - - - -

-

The anchor element may be thought of as an empty - seg, or as an artifice enabling an identifier to be - attached to any position in a text. Like the milestone - element discussed in section , it is useful - where multiple views of a document are to be combined, for - example, when a logical view based on paragraphs or verse lines is - to be mapped on to a physical view based on manuscript lines. Like - those elements, it is a member of the class model.global and can therefore appear - anywhere within a document when the module defined by this chapter - is included in a schema. Unlike the other elements in its class, - the anchor element is primarily intended to mark - an arbitrary point used for alignment, or as the target of a - spanning element such as those discussed in section , rather than as a means of marking segment - boundaries for some arbitrary segmentation of a text.

-

For example, suppose that we wish to mark the end of the fifth - word following each occurrence of some term in a particular text, - perhaps to assist with some collocational analysis. This can most - easily be done with the help of the anchor element, as - follows: - - English language. Except for not very -English at all at the time -English was still full of flaws -English. This was revised by young - In section we discuss ways in which these - anchor points might be used to represent an alignment - such as one might get in a keyword-in-context concordance.

-

The seg element may be used at the encoder's - discretion to mark almost any segment of the text of interest for - processing. One use of the element is to mark text features for - which no appropriate markup is otherwise defined, i.e. as a simple - extension mechanism. Another use is to provide an identifier for - some segment which is to be pointed at by some other element, i.e. - to provide a target, or a part of a target, for a ptr or - other similar element.

-

Several examples of uses for the seg element are - provided elsewhere in these Guidelines. For example: - -as a means of marking segments significant in a metrical -or rhyming analysis (see section ) -as a means of marking typographic lines in drama (see -section ) or title pages (see section ) -as a means of marking prosody- or pause-defined units in -transcribed speech (see section ) -as a means of marking linguistic or other analyses in a -theory-neutral manner (see chapter -passim)

- -

In the following simple example, the seg element simply -delimits the extent of a stutter, a textual feature for which no -element is provided in these Guidelines. Don't say I-I-I'm afraid, Melvin, just say I'm -afraid. - -The seg element is particularly useful for the markup -of linguistically significant constituents such as the phrases -that may be the output of an automatic parsing system. This -example also demonstrates the use of the xml:id -attribute to carry an identifier which other parts of a document -may use to point to, or align with: - - Literate and illiterate speech - in a language like English - are plainly different. - -

-

As the above example shows, seg elements may be -nested directly within one another, to any degree of analysis -considered appropriate. This is taken a little further in the -following example, where the type and -subtype attributes have been used to further -categorize each word of the sentence (the xml:id -attributes have been removed to reduce the complexity of the -example): - - -Literate -and -illiterate -speech - - -in -a -language -like -English - - -are -plainly -different - - . -

-

(The example values shown are chosen for simplicity of -comprehension, rather than verisimilitude). It should also be -noted that specialized segment elements are defined in section - to facilitate this particular kind of -analysis. These allow for the explicit markup of units called -s-units, clauses, -phrases, words, morphemes, -and characters, which may be felt preferable to the -more generic approach typified by use of the seg -element. Using these, the first phrase above might be encoded -simply as - - Literate - and - illiterate - speech - -Note the way in which the type attribute of these -specialized elements now carries the value carried by the -subtype attribute of the more general seg -element. For an analysis not using these traditional linguistic -categories however, the seg element provides a simple -but powerful mechanism.

-

In language corpora and similar material, the seg -element may be used to provide an end-to-end segmentation as an -alternative to the more specific s element proposed in -chapter for the markup of orthographic -sentences, or s-units. However, it may be more -useful to use the s element for this purpose, since -this means that the seg element can then be used to -mark both features within s-units and segments composed of -s-units, as in the following example:See -section , where the text from which this -fragment is taken is analyzed. - - Sigmund, the son of Volsung, - was a king in Frankish country. - Sinfiotli was the eldest of his sons. - ... -

-

Like other elements, the seg tag must be properly -enclosed within other elements. Thus, a single seg -element can be used to group together words in different -sentences only if the sentences are not themselves tagged. The -first of the following two encodings is legal, but the second is -not. - -Give me a dozen. Or two or three. - -Give me a dozen. -Or two or three.]]>

-

The part attribute may be used as one simple -method of overcoming this restriction: -Give me a dozen. -Or two or three. -Another solution is to use the join element discussed -in section ; this requires that each of the -seg elements be given an identifier. For further -discussion of this generic encoding problem, see also chapter -.

-

The seg element has the same content as a paragraph -in prose: it can therefore be used to group together consecutive -sequences of model.inter class elements, -such as lists, quotations, notes, stage directions, etc. as well -as to contain sequences of phrase-level elements. It cannot -however be used to group together sequences of paragraphs or -similar text units such as verse lines; for this purpose, the -encoder should use intermediate pointers, as described in -section or the methods described in -section . It is particularly important that -the encoder provide a clear description of the principles by -which a text has been segmented, and the way in which that -segmentation is represented. This should include a description -of the method used and the significance of any categorization -codes. The description should be provided as a series of -paragraphs within the segmentation element of the -encoding description in the TEI header, as described in section -.

-

The seg element may also be used to encode -simultaneous or mutually exclusive variants of a text when the -more special purpose elements for simple editorial changes, -abbreviation and expansion, addition and deletion, or for a -critical apparatus are not appropriate. In these circumstances, -one seg is encoded for each possible variant, and the -set of them is enclosed in a choice element.

-

For example, if one were writing dual-platform instructions for -installation of software, it might be useful to use seg -to record platform-specific pieces of mutually exclusive text. -…pressing option -alt-f will …

-

Elsewhere in this chapter we provide a number of examples -where the seg element is used simply to provide an -element to which an identifier may be attached, for example so -that another segment may be linked or related to it in some -way.

-

The ab (anonymous block) element functions like the - seg element, but is used for portions - of the text which occur at the chunk level - (See ). It is therefore a member of the - model.pLike class. Like seg, - but unlike p, ab may nest within other ab - elements. So it may be used to represent texts with irregular - chunk-level structures.

-

Probably the most common use for ab is as a container for -text that does not naturally belong in a paragraph. The text of an -epitaph, for example, may not be paragraph-like, but still requires -a container: - - - SACRED - to the memory of - Mrs. ALICE HUTTON - born at Chesterfield in - Great Britain, - Jany. 25th. 1722: - and died in Carolina - Septr. 26th. 1777. - This stone - is placed by her only Child - ANN BOOTH POLLOK - -Encoders may also prefer to treat other types of short documents, such as receipts, in this way.

-

The ab element may also be used, for -example, to tag the canonical verse divisions of Biblical texts: - - The First Book of Moses, Called - Genesis - - In the beginning God created the heaven and the -earth. - And the earth was without form, and void; and darkness -was upon the face of the deep. And the Spirit of God -moved upon the face of the waters. - And God said, Let there be light: and there was -light. - - -

-

In other cases, where the text clearly indicates paragraph -divisions containing one or more verses, the p element -may be used to tag the paragraphs, and the seg element -used to subdivide them. The ab element is provided as -an alternative to the p element; it may -not be used within paragraphs. The seg -element, by contrast, may appear only within and not between -paragraphs (or anonymous block elements). - - Das Erste Buch Mose. - -

-Am Anfang schuff Gott Himel vnd Erden. -Vnd die Erde war wüst vnd leer / vnd es war - finster auff der Tieffe / Vnd der Geist Gottes schwebet auff - dem Wasser.

-

-Vnd Gott sprach / Es werde Liecht / Vnd es ward - Liecht.

- - -

-

The ab element is also useful for marking dramatic -speeches when it is not clear whether the speech is to be -regarded as prose or verse. If, for example, an encoder does not -wish to express an opinion as to whether the opening lines of -Shakespeare's The Tempest are to be regarded as -prose or as verse, they might be tagged as follows: - - Actus primus, Scena prima. - A tempestuous noise of -Thunder and Lightning heard: -Enter a Ship-master, and a Boteswaine. - Master. - Bote-swaine. - Botes. - Heere Master: What cheere? - Mast. - Good: Speake to th' Mariners: fall too't, yarely, - or we run our selues a ground, bestirre, bestirre. - Exit. - - Enter Mariners. - Botes. - 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. - - -See further and .

- - - - - -
-
-Synchronization -

In the previous section we discussed two particular kinds of -alignment: alignment of parallel texts in different languages; and -alignment of texts and portions of an image. In this section we address -another specialized form of alignment: synchronization. The need to -mark the relative positions of text components with respect to time -arises most naturally and frequently in transcribed spoken texts, but it -may arise in any text in which quoted speech occurs, or events are -described within a time frame. The methods described here are also -generalizable for other kinds of alignment (for example, alignment of -text elements with respect to space).

-
-Aligning Synchronous Events - -

Provided that explicit elements are available to represent the -parts or places to be synchronized, then the global linking attribute -synch may be used to encode such synchronization, once it -has been identified. - - - - This is another of the attributes made globally available by - the mechanism described in the introduction to this chapter. - Alternatively, the link and linkGrp elements - may be used to make explicit the fact that the synchronous - elements are aligned.

-

To illustrate the use of these mechanisms for marking synchrony, -consider the following representation of a spoken text: - -

-

This representation uses numbers in brackets to mark the points at -which speakers overlap each other. For example, the [1] -in A's first speech is to be understood as coinciding with the -[1] in B's second speech.This sample is taken from -a conversation collected and transcribed for the British National -Corpus.

-

To encode this we use the spoken texts module, described -in chapter , together with the module -described in the present chapter. First, we transcribe this text, -marking the synchronous points with anchor elements, and -providing a synch attribute on one of each of the pairs of -synchronous anchors. As noted in the example given above (section ), correspondence, and hence synchrony, is a -symmetric relation; therefore the attribute need only be specified on -one of the pairs of synchronous anchors. -

- - The first time in twenty five years, - we've cooked Christmas for a blooming great - load of people. -So you're - - -It will be - nice in a way, but, - be strange. -Yeah - , yeah, cos it, its - the - -not -

-

We can encode this same example using link and -linkGrp elements to make the temporal alignment explicit. A back -element has been used to enclose the linkGrp element, but the links -may be located anywhere the encoder finds convenient: - - - - - - - - - - -The -xml:id attributes are provided for the link and -linkGrp elements here for reasons discussed in the next -section, . -

-

As with other forms of alignment, synchronization may be expressed -between stretches of speech as well as between points. When complete -utterances are synchronous, for example, if one person says -What? and another No! at the same time, -that can be represented without anchor elements as follows. -What? -No!

-

A simple way of expressing overlap (where one speaker -starts speaking before another has finished) is thus to use the -seg element to encode the overlapping portions of speech. For -example, - So you're - It will be nice in a way, but, - be strange. - Yeah , yeah, cos it, - its the - not -Note in this encoding how synchronization has been effected between an -empty unclear element and the content of a seg element, and between the -content of a -u element and that of another seg, using the synch -attribute. Alternatively, a linkGrp could be used in the same -way as above.

-
-Placing Synchronous Events in Time -

A synchronous alignment specifies which points in a spoken text occur -at the same time, and the order in which they occur, but does not say at -what time those points actually occur. If that information is available -to the encoder it can be represented by means of the when and -timeline elements, whose description and attributes are the -following: -

-

Each when element indicates a point in time, either directly -by means of the absolute attribute, whose value is a string -which specifies a particular time, or indirectly by means of the -since attribute, which points to another when. If -the since is used, then the interval and -unit attributes should also be used to indicate the amount of -time that has elapsed since the time specified by the element pointed to -by the since attribute; the value -1 -can be given to indicate that the interval is unknown.

-

If the when elements are uniformly spaced in time, then the -interval and unit values need be given once in the -timeline, and not repeated in any of the when -elements. If the intervals vary, but the units are all the same, then -the unit attribute alone can be given in the -timeline element, and the interval attribute given -in the when element.

-

The origin attribute in the timeline element -points to a when element which specifies the reference or -origin for the timings within the timeline; this must, of -course, specify its position in time absolutely. If the origin of a -timeline is unknown, then this attribute may be omitted.

-

The following timeline might be used to accompany the marked -up conversation shown in the preceding section: - - - - - - - - - -The information in this timeline could now be linked to the -information in the linkGrp which provides the temporal -alignment (synchronization) for the text, as follows: - - - - - - - -

-

To avoid the need for two distinct link groups (one marking the -synchronization of anchors with each other, and the other marking their -alignment with points on the time line) it would be better to link the -when elements with the synchronous points directly: - - - - - - - -

- - -

Finally, suppose that a digitized audio recording is also -available, and an XML file that assigns identifiers to the various -temporal spans of sound is available. For example, the following -Synchronized Multimedia Integration Language (SMIL, pronounced -"smile") fragment: - - -URIs pointing to the audio elements could also -be included as a fourth component in each of the above link -elements, thus providing a synchronized audio track to complement the -transcribed text.

-

For further discussion of this and related aspects of encoding -transcribed speech, refer to chapter .

- - - -
-
- -Correspondence and Alignment -

In this section we introduce the notions of -correspondence, expressed by the corresp -attribute, and of alignment, which is a special -kind of correspondence involving an ordered set of -correspondences. Both cases may be represented using the -link and linkGrp elements introduced in -section . We also discuss the special case -of alignment in time or synchronization, for which -special purpose elements are proposed in section .

-
- Correspondence -

A common requirement in text analysis is to represent - correspondences between two or more parts of a single - document, or between places in different documents. Provided - that explicit elements are available to represent the parts or - places to be linked, then the global linking attribute - corresp may be used to encode such correspondence, - once it has been identified. - - - - This is one of the attributes made available by the mechanism - described in the introduction to this chapter (). Correspondence can also be expressed by means - of the link element introduced in section .

-

Where the correspondence is between spans, the - seg element should be used, if no other element is - available. Where the correspondence is between - points, the anchor element should be - used, if no other element is available.

-

The use of the corresp attribute with spans of - content is illustrated by the following example: -Shirley, which made -its Friday night debut only a month ago, was -not listed on NBC's new schedule, -although the network -says the show -still is being considered. - - - - Here the anaphoric phrases the network - and the show have been associated - directly with the elements to which they refer by means of - corresp attributes. This mechanism is simple to - apply, but has the drawback that it is not possible to specify - more exactly what kind of correspondence is intended. Where - this attribute is used, therefore, encoders are encouraged to - specify their intent in the associated encoding description - in the TEI header.

-

Essentially, what the corresp attribute does is - to specify that elements bearing this attribute and those -to which the attribute points are doubly linked. In the example above, -the use of the corresp attribute indicates that the seg element containing the show and the -title element containing Shirley correspond to each -other: the correspondence relationship is not from -one to the other, but between the two -objects. It is thus different from the target attribute, -and provides functionality more similar to that of the link and linkGrp elements defined in - section , although it lacks the ability to - indicate more precisely what kind of correspondence is - intended as in the following retagging of the preceding - example. -Shirley, which made -its Friday night debut only a month ago, was not -listed on NBC's new schedule, -although the network says -the show still is being considered. - - - -

-

In the following example, we use the same mechanism to -express a correspondence amongst the anchors introduced following the -fifth word after English in a text: - -English language. Except for not very - -English at all at the time - -English was still full of flaws - -English. This was revised by young - - - - - -

-
- Alignment of Parallel Texts -

One very important application area for the alignment of - parallel texts is multilingual corpora. Consider, for - example, the need to align translation - pairs of sentences drawn from a corpus such as - the Canadian Hansard, in which each sentence is given in - both English and French. Concerning this problem, Gale and - Church write: Most English sentences match - exactly one French sentence, but it is possible for an - English sentence to match two or more French sentences. The - first two English sentences [in the example below] - illustrate a particularly hard case where two English - sentences align to two French sentences. No smaller - alignments are possible because the clause - ...sales...were higher... in the first English - sentence corresponds to (part of) the second French - sentence. The next two alignments ... illustrate the more - typical case where one English sentence aligns with exactly - one French sentence. The final alignment matches two English - sentences to a single French sentence. These alignments - [which were produced by a computer program] agreed with the - results produced by a human judge.See - , from which the example in the - text is taken.

-

The alignment produced by Gale and Church's program can - be expressed in four different ways. The encoder must first - decide whether to represent the alignment in terms of points - within each text (using the anchor element) or in - terms of whole stretches of text, using the seg - element. To some extent the choice will depend on the - process by which the software works out where alignment - occurs, and the intention of the encoder. Secondly, the - encoder may elect to represent the actual encoding using - either corresp attributes attached to the - individual anchor or seg elements, or - using a free-standing linkGrp element.

-

We present first a solution using anchor - elements bearing only corresp attributes: -

-

According to our survey, 1988 -sales of mineral water and soft drinks were much higher than in 1987, -reflecting the growing popularity of these products. Cola drink -manufacturers in particular achieved above-average growth rates. -The higher turnover was largely -due to an increase in the sales volume. -Employment and investment levels also climbed. -Following a two-year transitional period, -the new Foodstuffs Ordinance for Mineral Water came into effect on -April 1, 1988. Specifically, it contains more stringent requirements -regarding quality consistency and purity guarantees.

-
-
-

Quant aux eaux minérales -et aux limonades, elles rencontrent toujours plus d'adeptes. En effet, -notre sondage fait ressortir des ventes nettement supérieures -à celles de 1987, pour les boissons à base de cola -notamment. La progression des -chiffres d'affaires résulte en grande partie de l'accroissement -du volume des ventes. L'emploi et -les investissements ont également augmenté. -La nouvelle ordonnance fédérale -sur les denrées alimentaires concernant entre autres les eaux -minérales, entrée en vigueur le 1er avril 1988 après -une période transitoire de deux ans, exige surtout une plus -grande constance dans la qualité et une garantie de la -pureté.

-

-

There is no requirement that the corresp - attribute be specified in both English and French texts, since - (as noted above) this attribute is defined as representing a - mutual association. However, it may simplify processing to do - so, and also avoids giving the impression that the English is - translating the French, or vice versa. More seriously, this - encoding does not make explicit that it is in fact - the entire stretch of text between the anchors which is being - aligned, not simply the points themselves. If for example one - text contained material omitted from the other, this approach - would not be appropriate.

-

We now present the same passage using the alternative - linkGrp mechanism and marking explicitly the segments - which have been aligned: -

-

- According to our survey, 1988 sales of mineral -water and soft drinks were much higher than in 1987, -reflecting the growing popularity of these products. Cola -drink manufacturers in particular achieved above-average -growth rates. - The higher turnover was largely due to an -increase in the sales volume. - Employment and investment levels also climbed. - Following a two-year transitional period, the new -Foodstuffs Ordinance for Mineral Water came into effect on -April 1, 1988. Specifically, it contains more stringent -requirements regarding quality consistency and purity -guarantees.

-
-
-

- Quant aux eaux minérales et aux limonades, -elles rencontrent toujours plus d'adeptes. En effet, notre -sondage fait ressortir des ventes nettement -supérieures à celles de 1987, pour les -boissons à base de cola notamment. - La progression des chiffres d'affaires -résulte en grande partie de l'accroissement du volume -des ventes. - L'emploi et les investissements ont -également augmenté. - La nouvelle ordonnance fédérale sur -les denrées alimentaires concernant entre autres les -eaux minérales, entrée en vigueur le 1er avril -1988 après une période transitoire de deux -ans, exige surtout une plus grande constance dans la -qualité et une garantie de la pureté.

-
- - - - - -

-

Note that use of the ab element allows us to mark up the -orthographic sentences in both languages independently of the alignment: -the first translation pair in this example might be marked up as -follows: -

- - According to our survey, 1988 sales of mineral water and soft -drinks were much higher than in 1987, reflecting the growing popularity -of these products. - Cola drink manufacturers in particular achieved above-average -growth rates. - -
-
- - Quant aux eaux minérales et aux limonades, elles -rencontrent toujours plus d'adeptes. - En effet, notre sondage fait ressortir des ventes nettement -supérieures à celles de 1987, pour les boissons à -base de cola notamment. - -
-

-
-A Three-way Alignment -

The preceding encoding of the alignment of parallel passages from -two texts requires that those texts and the alignment all be part of -the same document. If the texts are in separate documents, then -complete URIs, whether absolute or relative (section ), will be required. These external pointers may appear -anywhere within the document, but if they are created solely for use -in encoding links, they may for convenience be grouped within the -linkGrp (or other grouping element that uses them for -linking).

-

To demonstrate this facility, we consider how we might encode the -alignments in an extract from Comenius' Orbis Sensualium -Pictus, in the -English translation of Charles Hoole (1659). - -

- -
-Each topic covered in this work has three parts: a -picture, a prose text in Latin describing the topic, and a -carefully-aligned translation of the Latin into English, German, or some -other vernacular. Key terms in the two texts are typographically -distinct, and are linked to the picture by numbers, which appear in the -two texts and within the picture as well.

-

First, we consider the text portions. The English and Latin portions -have been encoded as distinct div elements. Identifiers have -been attached to each typographic line, but no other encoding added, to -simplify the example. - -

- The Study -

-The Study -is a place -where a Student, -a part from men, -sitteth alone, -addicted to his Studies, -whilst he readeth -Books,

-
-
- Muséum -

-Museum -est locus -ubi Studiosus, -secretus ab hominibus, -solus sedet, -Studiis deditus, -dum lectitat -Libros,

-

- -

Next we consider the non-textual parts of the page. Encoding this -requires providing two distinct components: firstly a digitized rendering of the -page itself, and secondly a representation of the areas within that image -which are to be aligned. In section we present a -simple way of doing this using the TEI-defined markup for alignment of -facsimiles. In the present chapter we demonstrate a more powerful -means of aligning arbitrary polygons and points, which uses the XML notation SVG (see SVG). This provides appropriate facilities for both these -requirements: - - - - - - - -This example of SVG defines two rectangles -at the locations with the specified x and y coordinates. A view is -defined on these, enabling them to be -mapped by an SVG processor to the image found at the URL specified -(p1764.png). It also defines unique identifiers for -the whole image, and the two views of it, which we will use within our -alignment, as shown next (for further discussion of the handling of - images and graphics, see section ; for further - discussion of using non-TEI XML vocabularies such as SVG within a TEI - document, see section ). -

-

As printed, the Comenius text exhibits three kinds of alignment. - - The English and Latin portions are printed in two - parallel columns, with corresponding phrases, (represented above by - seg elements), more or less next to each other. - Particular words or phrases are marked as terms in the - two languages by a change of rendition: the English text, which - otherwise uses black letter type throughout, has the words - The Study, a Student, - Studies, and Books in - a roman font; in the Latin text, which is printed in roman, the - corresponding words (Museum, - Studiosus, Studiis, - and Libros) are all in italic. - Numbered labels appear within the text portions, - linking keywords to each other and to sections of the picture. - These labels, which have been left out of the above encoding, are - attached to the first, third, and last segments in each language - quoted below, and also appear (rather indistinctly) within the - picture itself. Thus, the images of the study, the student, and his - books are each aligned with the correct term for them in the two - languages. -

-

The first kind of alignment might be represented by using the -corresp attribute on the seg element. The second -kind might be represented by using the gloss and term -mechanism described in section . The third kind of -alignment might be represented using pointers embedded within the -texts, for example: - - -where a Student, -ubi Studiosus, - - - -We choose however to use -the link element, since this provides a more efficient way of -representing the three-way alignment between English, Latin, and picture -without redundancy. - - - - - - - - - -

-

This map, of course, only aligns whole segments and image portions, -since these are the only parts of our encoding which bear identifiers -and can therefore be pointed to. To add to it the alignment between -the typographically distinct words mentioned above, new elements must -be defined, either within the text itself or externally by using stand -off techniques. Encoding these word pairs as term -and gloss, although intuitively obvious, requires a -non-trivial decision as to whether the Latin text is glossing the -English, or vice versa. Tagging all the marked words as term -avoids the difficult decision, but might be thought by some encoders -to convey the wrong information about the words in question. Simply -tagging them as additional embedded seg elements with -identifiers that can be aligned like the others is also a possibility. -

-

These solutions all require the addition of further markup to the text. This -may pose no problems, or it may be infeasible, for example because the text is -held on a read-only medium. If it is not feasible to add more markup -to the original text, some form of stand-off markup will be -needed. Any item within the text that can be pointed to using the -various pointer schemes discussed in this chapter may be used, not -simply those which rely on the existence of an xml:id -attribute. Suppose our example had been -more lightly tagged, as follows: - -

- The Study - The Study - is a place - where a Student, -
-
- Muséum - Museum - est locus - ubi Studiosus, -
-

-

To express the same alignment mentioned above, we could use an -XPath expression to identify the required ab elements: - - - - - -In the absence of any markup around individual substrings of -the element content, the string-range pointer scheme discussed in may also be helpful: for example, to indicate that the words -Studies and Studiis -correspond, we might express the link between them as follows: - -

- -
-
-Identical Elements and Virtual Copies -

This section introduces the notion of a virtual element, -that is, an element which is not explicitly present in a text, but the -presence of which an application can infer from the encoding supplied. -In this section, we are concerned with virtual elements made by simply -cloning existing elements. In the next section (), we -discuss virtual elements made by aggregating existing elements.

-

Provided - that explicit elements are available to represent the parts or - places to be linked, then the global linking attributes - sameAs and copyOf may be used to encode -this kind of equivalence: - - - -

-

It is useful to be able to represent the fact that one element of -text is identical to others, for analytical purposes, or (especially if -the elements have lengthy content) to obviate the need to repeat the -content. For example, consider the repetition of the date -element in the following material: -

In small clumsy letters he wrote: -April 4th, -1984.

-

He sat back. A sense of complete helplessness had -descended upon him. ...

-

His small but childish handwriting straggled up -and down the page, shedding first its capital letters -and finally even its full stops: -April 4th, 1984. -Last night to the flicks. ...

-Suppose now that we wish to encode the fact that the second -date element above has identical content to the first. The -sameAs attribute is provided for this purpose. Using it, we -could recode the last line of the above example as follows: -April 4th, -1984 -Last night to the flicks ...

-

The sameAs attribute may be used to document the fact -that two elements have identical content. It may be regarded as a -special kind of link. It should only be attached to an element with -identical content to that which it targets, or to one the content of which -clearly designates it as a repetition, such as the word -repeat or bis in the -representation of the chorus of a song, the second time it is to be -sung. The relation specified by the sameAs attribute is -symmetric: if a chorus is repeated three times and each repetition -bears a sameAs attribute indicating the first occurrence of -the element concerned, it is implied that each chorus is identical, -and there is no need for the first occurrence to specify any of its -copies.

-

The copyOf attribute is used in a similar way to -indicate that the content of the element bearing it is identical to -that of another. The difference is that the content is not itself -repeated. The effect of this attribute is thus to create a -virtual copy of the element indicated. Using this -attribute, the repeated date in the first example above could be -recoded as follows: -

-

An application program should replace whatever is the actual content -of an element bearing a copyOf attribute with the content of -the element specified by it. If the content of the element specified -includes other elements, these will become embedded within the element -bearing the attribute. Care must be taken to ensure that the document -is valid both before and after this embedding takes -place. If, for example, the element bearing a copyOf -attribute requires a mandatory sub-component, then this component must -be present (though possibly empty), even though it will be replaced by -the content of the targetted element.

-

The following example demonstrates how the copyOf -attribute may be used in conjunction with the seg element to -highlight the differences between almost identical repetitions: - -Mikado - My object all sublime - I shall achieve in time— - To let the punishment fit the crime, - ; - And make each pris'ner pent - Unwillingly represent - A source of innocent merriment, - ! - -Chorus - His - He will - - - - - - - -

-

For further examples of the use of this attribute, see and .

-
-Aggregation -

Because of the strict hierarchical organization of elements, or for -other reasons, it may not always be possible or desirable to include -all the parts of a possibly fragmented text segment within a single -element. In section we introduced the notion of -an intermediate pointer as a way of pointing to discontinuous segments -of this kind. In this section we first describe another way of linking -the parts of a discontinuous whole, using a set of linking attributes, -which are made available for any tag by following the procedure -described at the beginning of this chapter. We then describe how the -link element may be used to aggregate such segments, and -finally introduce the join element, which is a -special-purpose linking element specifically for representing the -aggregation of parts, and the joinGrp for grouping -join elements.

-

The linking attributes for aggregation are next and -prev; each of these attributes has a single identifier as its -value: -

-

It is recommended that the elements indicated by these attributes be of the same type as the element bearing them.

- -

The join element is also a member of the class of att.pointing elements, and so may carry any of the -attributes of that class; for the list, see section .

-

Here is the material on which we base our first illustration of the -use of these mechanisms. Our problem is to represent the s-units -identified below as qs3 and qs4 as a single (but discontinuous) whole: -Monsieur Paul, after he has taken equal -parts of goose breast and the finest pork, and -broken a certain number of egg yolks into them, -and ground them very, very fine, -cooks all with seasoning for some three hours. - -But, -she pushed her face nearer, and looked with - ferocious gloating at the pâté - inside me, her eyes like X rays, - - he never stops stirring it! - Figure to yourself the work of it — - stir, stir, never stopping! - - -

-

Using the prev and next attributes, we can -link the s-units with identifiers qs3 and qs4, either singly or doubly as follows: -But, - he never stops stirring it!]]> -But, - he never stops stirring it!]]> -But, - he never stops stirring it!]]> -Double linking of the two s-units, as illustrated by the last of these -encodings, is equivalent to specifying a link element: -

-

Such a link element must carry a type -attribute with a value of join to specify that the link is -to be understood as joining its targets into a single aggregate.

-

The join element is equivalent to a link element of -type join. - -Unlike the link element, the join element can -additionally specify information about the virtual element which it -represents, by means of its result attribute. And finally, -unlike the link element, the position of a join -element within a text is significant: it must be supplied at a position -where the element indicated by its result attribute would be -contextually legal. - -To conclude the above example, we now use a join element to -represent the virtual sentence formed by the aggregation of s1 and s2: - -As a further example, consider the following list of authors' names. -The object of the join element here is to provide another -list, composed of those authors from the larger list who happen to -come from Heidelberg: - -Authors - Figge, Udo - Heibach, Christiane - Heyer, Gerhard - Philipp, Bettina - Samiec, Monika - Schierholz, Stefan - - -Authors from Heidelberg

-

The following example shows how join can be used to -reconstruct a text cited in fragments presented out of order. The poem -being remembered (an unusual translation of a well-known poem by Basho) -runs When the old pond / gets a new frog, / it's a new pond.

- -Hughie -

How does it go? - - da-da-da - gets a new frog - ... - -

- -Louie -

- -When the old pond -... - -

- -Dewey -

- ... - It's a new pond. - -

- - - -

As with other forms of link, a grouping element joinGrp -is available for use when a number of join elements of the -same kind co-occur. This avoids the need to specify the -result attribute for each join if they are all of -the same type, and also allows us to restrict the domain within which -their target elements are to be found, in the same way as for -linkGrp elements (see ). Like a -join, a joinGrp may appear only where the elements -represented by its contents are legal. Thus if we had created many -join tags of the sort just described, we could group them -together, and require that their components are all contained by an -element with the identifier MFKFhungry as -follows: - - - - - -

-

The join element is useful as a means of representing -non-hierarchic structures (as further discussed in chapter ). It may also be used as a convenient way of representing a -variety of analytic units, like the span and interp -elements discussed in chapter . As an example, consider -the following famous Zen koan: - -

Zui-Gan called out to himself every day, Master.

-

Then he answered himself, Yes, sir.

-

And then he added, Become sober.

-

Again he answered, Yes, sir.

-

And after that, he continued, do not be deceived by -others.

-

Yes, sir; yes, sir, he replied.

-

Suppose now that we wish to represent an interpretation of the above -passage in which we distinguish between the various -voices adopted by Zui-Gan. In the -following encoding, the who attribute has been used for this -purpose; its value on each occasion supplies a pointer to the -voice to which each speech is attributed. (For convenience in -this example, we use simply the first occurrence of the names used for -each voice as the target for these pointers.) Note also that we add -xml:id attributes to each distinct speech fragment, which -we can then use to link the material -spoken by each voice: - - -

Zui-Gan called out to himself every day, - Master.

-

Then he answered himself, - Yes, sir.

-

And then he added, - Become sober.

-

Again he answered, - Yes, sir.

-

And after that, - he continued, - do not be deceived by others.

-

Yes, sir; yes, sir, - he replied.

- -

-

However, by using the join element, we can directly -represent the complete speech attributed to each voice: - - - what Zui-Gan said - - what Master said -

-

Note the use of the desc child element within the two -joins making up the q element here. These enable us -to document the speakers of the two virtual q elements -represented by the join elements; this is necessary because the -there is no way of specifying the attributes -to be associated with a virtual element, in particular there is no way -to specify a -who value for them.

-

Suppose now that xml:id attributes, for whatever -reasons, are not available. Then ptr elements may be created -using any of the methods described in section . -The xml:id attributes of -these elements may now be specified by the -target attribute on the join elements. - - - - -

Zui-Gan called out to himself every day, Master.

-

Then he answered himself, Yes, sir.

-

And then he added, Become sober.

-

Again he answered, Yes, sir.

-

And after that, he continued, do not be deceived by others.

-

Yes, sir; yes, sir, he replied.

- - - - - - - - - - - what Zui-Gan said - - what Master said - - - -

-

The extended pointer with identifier -rzuiq2, for example, may be read as the first -q in the first p, within the sixth div1 -element of the current document.

- - - - -
-
-Alternation -

This section proposes elements for the representation of alternation. -We say that two or more elements are in exclusive -alternation if any of those elements could be present in a text, -but one and only one of them is; in addition, we say that those elements -are mutually exclusive. We say that the elements are in -inclusive alternation if at least one (and possibly more) -of them is present. The elements that are in alternation may also be -called alternants.

-

The need to mark exclusive alternation arises frequently in text -encoding. A common situation is one in which it can be determined that -exactly one of several different words appears in a given location, but -it cannot be determined which one. One way to mark such an exclusive -alternation is to use the linking attribute exclude. Having -marked an exclusive alternation, it can sometimes later be determined -which of the alternants actually appears in the given location. To -preserve the fact that an alternation was posited, one can add the -linking attribute select to a tag which hierarchically -encompasses the alternants, which points to the one which actually -appears. To assign responsibility and degree of certainty to the -choice, one can use the certainty tag described in -chapter . Also see that chapter for further discussion of -certainty in general.

-

The exclude and select attributes may be used -with any element assuming that they have been declared following the -procedure discussed in the introduction to this chapter. - - -

-

A more general way to mark alternation, encompassing both exclusive -and inclusive alternation, is to use the linking element alt. -The description and attributes of this tag and of the associated -grouping tag altGrp are as follows. These elements are also -members of the att.pointing class and therefore -have all the attributes associated with that class. -

-

To take a simple hypothetical example, suppose in transcribing a -spoken text, we encounter an utterance that we can understand either as -We had fun at the beach today. or as We had sun at -the beach today. We can represent the exclusive alternation of -these two possibilities by means of the exclude attribute as -follows. -

- We had fun at the beach today. - We had sun at the beach today. -

-

If it is then determined that the speaker said fun, -not sun, the encoder could amend the text by deleting the -alternant containing sun and the exclude -attribute on the remaining alternant. Alternatively, the encoder could -preserve the fact that there was uncertainty in the original -transcription by retaining the alternants, and assigning the -we.fun value to the select attribute value on the div element that -encompasses the alternants, as in: -

- We had fun at the beach - today. - We had sun at the beach today. -

-

The above alternation (including the select attribute) -could be recoded by assigning the exclude attributes to tags -that enclose just the words or even the characters that are mutually -exclusive, as in:See section for discussion of the -w and c tags that can be used in the following -examples instead of the seg type="word" and seg -type="character" tags. -

- We had - fun - sun - at the beach today. -
-
- We had - -f -s -un - at the beach today. -

-

Now suppose that the transcriber is uncertain whether the first word -in the utterance is We or Lee, but is -certain that if it is Lee, then the other uncertain word -is definitely fun and not sun. The three -utterances that are in mutual exclusion can be encoded as follows. -

- - We had fun at the beach today. - We had sun at the beach today. - Lee had fun at the beach today. - -

-

The preceding example can also be encoded with exclude -attributes on the word segments We, Lee, -fun, and sun: - - We - Lee - had - fun - sun - at the beach today.

-

The value of the select attribute is defined as a list of -identifiers; hence it can also be used to -narrow down the range of alternants, as in: -

- We had fun at the beach today. - We had sun at the beach today. - Lee had fun at the beach today. -
-This is interpreted to mean that either the first or the third -u element tag appears, and is thus equivalent to just the alternation -of those two tags: -
- We had fun at the beach - today. - Lee had fun at the beach today. -

-

The exclude attribute can also be used in case there is -uncertainty about the tag that appears in a certain position. For -example, the occurrence of the word May in the s-unit -Let's go to May can be interpreted, in the absence of -other information, either as a person's name or as a date. The -uncertainty can be rendered as follows, using the exclude -attribute. -Let's go to -May - .

-

Note the use of the copyOf attribute discussed in -section ; this avoids having to repeat the content of the -element whose correct tagging is in doubt.

-

The copyOf and the exclude attributes also -provide for a simple way of indicating uncertainty about exactly where a -particular element occurs in a document.An alternative way of -representing this problem is discussed in chapter . - -For example suppose that a particular div2 -element appears either as the third and last of the div2 -elements within the first div1 element in the body of a -document, or as the first div2 of the second div1. -One solution would be to record the div2 in its entirety in the -first of these positions, and a virtual copy of it in the second, and -mark them as excluding each other as follows: - - - - - - - - - -In this case, the select attribute, if used, would appear on -the body element.

-

Mutual exclusion can also be expressed using a link; the -first example in this section can be recoded by removing the -exclude attributes from the u elements, and adding a -link element as follows:In this example, we have -placed the link next to the elements that represent the -alternants. It could also have been placed elsewhere in the document, -perhaps within a linkGrp. -

- We had fun at the beach today. - We had sun at the beach today. - -

-

Now we define the specialized linking element alt, making -it a member of the class att.pointing, and -assigning it a mode attribute, which can have either of the -values excl (for exclusive) or incl (for -inclusive). Then the following equivalence holds: - = -

-

The preceding link element may therefore be recoded as the - following alt element.

-

Another attribute that is defined specifically for the alt -element is weights, which is to be used if one wishes to assign -probabilistic weights to the targets (alternants). Its -value is a list of numbers, corresponding to the targets, expressing the -probability that each target appears. If the alternants are mutually exclusive, then -the weights must sum to 1.0.

-

Suppose in the preceding example that it is equiprobable whether -fun or sun appears. Then -the alt element that represents the alternation may be stated -as follows:

-

The assignment of a weight of 1.0 to one target (and weights of 0 -to all the others) is equivalent to selecting that target. Thus the -following encoding is equivalent to the second example at the beginning -of this section. -We had fun at the beach today. -We had sun at the beach today. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -The sum of the weights for alt mode="incl" tags ranges from 0% to -(100 × k)%, where k is the number of targets. If the sum is 0%, then -the alternation is equivalent to exclusive alternation; if the sum is -(100 x k)%, then all of the alternants must appear, and the situation is -better encoded without an alt tag.

- -

If it is desired, alt elements may be grouped together in -an altGrp element, and attribute values shared by the -individual alt elements may be identified on the -altGrp element. The targFunc attribute defaults to -the value first.alternant next.alternant.

- -

To illustrate, consider again the example of a transcribed -utterance, in which it is uncertain whether the first word is -We or Lee, whether the -third word is fun or -sun, but that if the first word is -Lee, then the third word is -fun. Now suppose we have the following -additional information: if we occurs, then the -probability that fun occurs is 50% and that -sun occurs is 50%; if -fun occurs, then the probability that -we occurs is 40% and that -Lee occurs is 60%. This situation can be -encoded as follows. - - - We - Lee - had - fun - sun - at the beach today. - - - - - - -As noted above, when the mode attribute on an -alt has the value incl, then each weight states -the probability that the corresponding alternative occurs, given that at least one of the other alternatives occurs. -

-

From the information in this encoding, we can determine that the -probability is about 28.5% that the utterance is We had fun at the -beach today, 28.5% that it is We had sun at the beach -today, and 43% that it is Lee had fun at the beach -today.

-

Another very similar example is the following regarding the text of a -Broadway song. In three different versions of the song, the same line -reads Her skin is tender as a leather glove, Her skin is -tender as a baseball glove, and Her skin is tender as Dimaggio's -glove.The variant readings are found in the commercial sheet -music, the performance score, and the Broadway cast recording.

-

If we wish to express this textual variation using the alt -element, we can record our relative confidence in the readings -Dimaggio's (with probability 50%), a -leather (25%), and a baseball (25%).

-

Let us extend the example with a further (imaginary) variation, -supposing for the sake of the argument that the next line is variously -given as and she bats from right to left (with -probability 50%) or now ain't that too damn bad (with -probability 50%). Using the alt element, we can express the -conviction that if the first choice for the second line is correct, then -the probability that the first line contains Dimaggio's -is 90%, and each of the others 5%; whereas if the second choice for the -second line is correct, then the probability that the first line -contains Dimaggio's is 10%, and each of the others is -45%. This can be encoded, with an altGrp element containing a -combination of exclusive and inclusive alt elements, as follows. - -

- Her skin is tender as - Dimaggio's - a leather - a baseball - glove, - and she bats from right to left. - now ain't that too damn bad. -
- - - - - - - - - - - -

- - - -
- -
-Stand-off Markup -
- Introduction - -

Most of the mechanisms defined in this chapter rely to a - greater or lesser extent on the fact that tags in a marked-up - document can both assert a property for a span of text which they - enclose, and assert the existence of an association between - themselves and some other span of text elsewhere. In stand-off - markup, there is a clear separation of these two behaviours: the - markup does not directly contain any part of the text, but - instead includes it by reference. One specific mechanism - recommended by these Guidelines for this purpose is the standard - XInclude mechanism defined by the W3C; another is to use pointers - as demonstrated elsewhere in this chapter.

- -

There are many reasons for using stand-off markup: the source - text might be read-only so that additional markup cannot be added, - or a single text may need to be marked up - according to several hierarchically incompatible schemes, or a single - scheme may need to accommodate multiple hierarchical ambiguities, so that - a single markup tree is not the most faithful representation of the - source material.

-

This section describes a generic mechanism for expressing - all kinds of markup externally as stand-off tags, - for use whenever it is appropriate; and a place in the TEI - structure (standOff) to contain certain common kinds - of stand-off markup.

- -

Throughout this section the following terms will be systematically used in - specific senses. - - - a document to which the stand-off markup refers (a source document can be either XML or - plain text); there may be more than one source document. - - markup that is already present in an XML source document - - markup that is either outside of the source document - and points in to it to the data it describes, or is pointed - at by the data that refers to it; or alternatively is in - another part of the source document and points elsewhere - within the document to the data it describes, or is pointed - at by data elsewhere that refers to it. - - a document that contains stand-off markup that points to a different, source document - - the action of creating a new XML document with external markup and data integrated with the - source document data, and possibly some source document markup as well - - a process applied to markup from a pre-existing XML - document, which splits it into two documents, an XML - (external) document containing some of the markup of the - original document, and another (source) XML document - containing whatever text content and markup has not been - extracted into the stand-off document; if all markup has been - externalized from a document, the new source may be a plain - text document - -

-

The three major requirements satisfied by this scheme for stand-off markup are: - - any valid TEI markup can be either internal or - external, - external markup can be internalized by - applying it to the document content by either - substituting the existing markup or adding to it, - to form a valid TEI document, and - the external markup itself specifies whether - an internalized document is to be created by substituting - the existing internal markup or by adding to - it. -

- - - -
- -
- Overview of XInclude -

Stand-off markup which relies on the inclusion of virtual - content is adequately supported by the W3C XInclude recommendation, - which is also recommended for use by these Guidelines.The version on which this text is based is the W3C - Recommendation dated 20 December - 2004.. XInclude defines a namespace - (http://www.w3.org/2001/XInclude), which in - these Guidelines will be associated with the prefix - xi:, and exactly two elements, - xi:include and xi:fallback. XInclude relies on - the XPointer - framework discussed elsewhere in this chapter to point to the - actual fragments of text to be internalized. Although XInclude only - requires support for the element() - scheme of XPointer, these Guidelines permit the use of any of the - pointing schemes discussed in section .

- -

XInclude is a W3C recommendation which specifies a syntax for the - inclusion within an XML document of data fragments placed in - different resources. Included resources can be either plain - text or XML. XInclude instructions within an XML document - are meant to be replaced by a resource targetted by a - URI, possibly augmented by an XPointer that identifies the - exact subresource to be included.

- -

The xi:include element uses the href attribute to specify the location of - the resource to be included; its value is an URI containing, - if necessary, an XPointer. Additionally, it uses the parse attribute (whose only valid values - are text and xml) to specify whether - the included content is plain text or an XML fragment, and - the encoding attribute to provide a hint, when - the included fragment is text, of the character encoding of - the fragment. An optional xi:fallback element is - also permitted within an xi:include; it specifies - alternative content to be used when the external resource - cannot be fetched for some reason. Its use is not however - recommended for stand-off markup.

- -
-
- - Stand-off Markup in TEI - -

The operations of internalizing and externalizing markup are - very useful and practically important. XInclude processing as - defined by the W3C is internalization of one or more - source documents' content into a stand-off document. TEI use of - XInclude for stand-off markup enables use of XInclude-conformant - software to perform this useful operation. However, - internalization is not clearly defined for all stand-off files, - because the structure of the internal and external markup trees - may overlap. In particular, when an external markup document - selects a range that overlaps partial elements in the source - document, it is not clear how the semantics of internalization - (inclusion) should work, since partial elements are not XML - objects.This corresponds to the observation - that overlapping XML tags reflecting a textual version of such an - inclusion would not even be well-formed XML. This kind of overlap - in textual phenomena of interest is in fact the major reason that - stand-off markup is needed. XInclude defines a semantics - for this case that involves only complete elements.

- -

When a range selection partially overlaps a number of elements in a -source document, XInclude specifies that the partially overlapping -elements should be included as well as all completely overlapping -elements and characters (partially overlapping characters are not -possible). The effect of this is that elements that straddle the start -or end of a selected range will be included as wrappers for those of -their children that are completely or partially selected by the -range. For example, given the following source document: - - - -

home, home on Brokeback Mountain.

-

That was the song that I sang

- - - and the following external document: - -
-
- ]]> - the resulting document after XInclude processing of this external document - would be: - -
-

home, home on Brokeback Mountain.

-

That was the song that I sang

-
- ]]> - The result of the inclusion is two paragraph elements, while - the original range designated in the source document - overlapped two paragraph fragments. - - -The semantics of XInclude require the creation of well-formed XML results even though - the pointing mechanisms it uses do not necessarily - respect the hierarchical structure of XML documents, as in - this case. While - this is a good way to ensure that internalization is always - possible, it has implications for the use of XInclude as a - notation for the description of overlapping - markup structures. -

- -

When overlapping hierarchies need to be represented - for a single document, each hierarchy must be represented by a - separate set of XInclude tags pointing to a common source - document. This sort of structure corresponds to common - practice in work with linguistic text corpora. In such corpora, each - potentially overlapping hierarchy of elements for the text is - represented as a separate stream of stand-off - markup. Generally the source text contains markup for - the smallest significant units of analysis in the corpus, - such as words or morphemes, this information and its markup - representing a layer of common information that is shared by - all the various hierarchies. As a way of organizing the - representation of complex data, this technique generally - allows a large number of xml:id attributes to be - attached to the shared elements, providing robust anchors for - links and facilitating adjustments to the source document - without breaking external documents that reference it. -

- - -

Any tag can be externalized by - - removing its content and replacing it with an - xi:include element that contains an XPointer - pointing to the desired content.

-

For instance the following portion of a TEI document: - - -1755 -To make a prairie it takes a clover and one bee, -One clover, and a bee, -And revery. -The revery alone will do, -If bees are few. - - - can be externalized by placing the actual text in a separate - document, and providing exactly the same markup with the - xi:include elements: - - - To make a prairie it takes a clover and one bee,\n -One clover, and a bee,\n -And revery.\n -The revery alone will do,\n -If bees are few.\n -]]> - - - - - 1755 - - - - - - - - - - - - - - - - -]]>

- - - -

Please note that this specification requires that the - XInclude namespace declaration is present in all cases. The - xi:fallback element contains text or XML fragments to - be placed in the document if the inclusion fails for any - reason (for instance due to inaccessibility of an external - resource). The xi:fallback element is optional; if it - is not present an XInclude processor must signal a fatal error - when a resource is not found. This is the preferred behaviour - for use with stand-off markup. These Guidelines recommend - against the use of xi:fallback for stand-off - markup.

-
-
- Well-formedness and Validity of Stand-off Markup -

The whole source fragment - identified by an XInclude element, as well as any markup - therein contained is inserted in the position specified, and - an XInclude processor is required to ensure that the resulting - internalized document is - well-formed. This has obvious implications when the external - document contains XML markup. A plain text source document - will always create a well-formed - internalized document.

-

While a TEI customization may permit - xi:include elements in various places in a TEI document - instance, in general these Guidelines suggest that validity be - verified after the resolution of all the xi:include - elements.

-
-
- Including Text or XML Fragments -

When the source text is plain text the overall form of the - XPointer pointing to it is of minimal importance. The form - of the XPointer matters considerably, on the other hand, - when the source document is XML.

-

In this case, it is rather important to distinguish whether - we intend to substitute the source XML with the new one, or - just to add new markup to it. The XPointers used in the - references can express both cases.

-

A simple way is to make sure to select only textual data in - the XPointer. For instance, given the following - document: - - - - - -

To make a prairie it takes a clover - and one bee,
-
One clover, and - a bee,
-
And revery.
-
The revery alone will do,
-
If bees are few.
- - - -the expression -range(element(/1/2/1.0),element(/1/2/11.1)) will select -the whole poem, text content and div elements -and hypertext links (NB: in XPointer whitespace-only text -nodes count).

-

On the contrary, the expressions -xpointer(//text()/range-to(.)) and -xpointer(string-range(//text(),"To")/range-to(//text(),"few.") -will only select the text of the poem, with no markup inside.

-

Thus, the following could be a valid stand-off document for - the Source.xhtml document: - - - - - 1755 - - - - - - - - - - - - - - - - -]]>

-
-
- -
- - The standOff Container -

The standOff element is intended to hold content that does not fit well in the - text (e.g. because it is not transcribed from the source), nor in the - teiHeader (e.g. because it is not metadata about the source or transcription). - Examples include contextual information about named entities (typically encoded using - listBibl, listOrg, listNym, listPerson, or - listPlace), annotations indicating the morphosyntactic features of a text, and - annotations commenting on or associating parts of a text with additional information. - - -

- -

As a member of model.resource, standOff may occur as a - child of TEI (or teiCorpus). If the metadata that describes the - standOff is largely the same as the metadata that describes the associated resource - (e.g., the transcribed text in text), then the standOff and the encoded - associated resource may appear as children of the same TEI element. The example below - has a transcription with placename elements in the text linked to a list of place elements in the - standOff section. - - - - - - - - - - Cilicia - https://pleiades.stoa.org/places/658440 - - - Creta - Crete - https://pleiades.stoa.org/places/589748 - - - - Rhodus - Rhodes - https://pleiades.stoa.org/places/590031 - - - Syria - https://pleiades.stoa.org/places/1306 - - - - - - -

-
- Bellum Alexandrinum -

- Bello Alexandrino conflato Caesar - - Rhodo - Ordo - atque ex Syria - Ciliciaque omnem classem arcessit; - Creta - certa - sagittarios, equites ab rege Nabataeorum - Malcho euocat; tormenta undique conquiri et - frumentum mitti, auxilia adduci iubet. - -

- -
- -
- - - - -

-
-
- Annotations -

The annotation element's structure is based on the Web - Annotation Data Model (WADM). A Web Annotation may have one or more targets, which are - URIs, and zero or more bodies, which may be either URIs or embedded text. A Web Annotation may - also contain metadata about the annotation, such as the creator, creation and modification - dates, and license information. The annotation element implements a subset of WADM, - using TEI elements and attributes to encode the same information, with a focus on annotating - TEI documents. Targets are represented using the target attribute on - annotation. URI bodies are represented using ref or ptr and - embedded text bodies using note. Lifecycle and license information may be given using - respStmt, revisionDesc, and licence. - - -

- -

TEI annotations are, in general, intended to capture the output of processes that annotate - TEI texts without altering the text and markup in the text. They allow this kind of - output to be represented directly in TEI, and thus to be processed using the same toolchains - as the texts they annotate. A named entity recognition workflow might use annotation, - for example to associate names in the text with person elements instead of attempting - to rewrite the TEI text using inline persName. Projects may wish to use this - mechanism to layer information onto a TEI text in case where using inline elements might - result in complicated markup.

- -

The example below illustrates how stand-off annotations can be used to connect words in a - text with place elements in a list. The words Gallia and Galliae in the - edition are connected by an annotation in the standOff section which points to them - using string-range() pointers and references the definition of the place (also in - the standOff section). If the set of annotations were created in a process separate - from the creation of the transcription and then imported into the transcription document, then - wrapping them in a TEI element with its own teiHeader providing metadata for - the annotations might be advisable. - - - - - De Bello Gallico - - - - - - -

-
-

- Gallia est omnis divisa in partes tres, quarum unam - incolunt Belgae, aliam Aquitani, tertiam qui ipsorum lingua Celtae, nostra - Galli appellantur. - - Belgae ab extremis Galliae finibus oriuntur, - pertinent ad inferiorem partem fluminis Rheni, spectant in septentrionem et - orientem solem. - Aquitania a Garumna flumine ad Pyrenaeos montes et - eam partem Oceani quae est ad Hispaniam pertinet; spectat inter occasum solis - et septentriones.] - -

- -
- -
- - - - - - Gallia - Gaul - https://pleiades.stoa.org/places/993 - - - - - - - - - - - - - creator - Fred Editor - - - - - - - - - - - - - - - - - -

- - - - -
- -
-Connecting Analytic and Textual Markup -

In chapters and and elsewhere, -provision is made for analytic and interpretive markup to be represented -outside of textual markup, either in the same document or in a different -document. The elements in these separate domains can be connected, -either with the pointing attributes ana (for -analysis) and inst (for -instance), or by means of link and -linkGrp elements. Numerous examples are given in these -chapters.

-

Another more specific form of annotation is available through the TEI ruby element and its - children, described in detail in .

- -
-
- Module for Linking, Segmentation, and Alignment -

The module described in this chapter makes available the - following components: - - Linking, Segmentation, and Alignment - Linking, segmentation, and alignment - Liens, segmentation et alignement - 連結、分割與隊列 - Collegamento, segmentazione e allineamento - Ligação, segmentação e alinhamento - リンクモジュール - - The selection and combination of modules to form a TEI schema is - described in . - - - - - - - - -

-
-
diff --git a/P5/Source/Guidelines/fr/SA-LinkingSegmentationAlignment.xml b/P5/Source/Guidelines/fr/SA-LinkingSegmentationAlignment.xml new file mode 120000 index 0000000000..d863f9f68b --- /dev/null +++ b/P5/Source/Guidelines/fr/SA-LinkingSegmentationAlignment.xml @@ -0,0 +1 @@ +../en/./SA-LinkingSegmentationAlignment.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/SG-GentleIntroduction.xml b/P5/Source/Guidelines/fr/SG-GentleIntroduction.xml deleted file mode 100644 index a8b298c76e..0000000000 --- a/P5/Source/Guidelines/fr/SG-GentleIntroduction.xml +++ /dev/null @@ -1,1473 +0,0 @@ - - - - -
- -A Gentle Introduction to XML - -

The encoding scheme defined by these Guidelines is formulated as an -application of the Extensible Markup Language (XML) (). XML is widely used for -the definition of device-independent, system-independent methods of -storing and processing texts in electronic form. It is now also the -interchange and communication format used by many applications on the -World Wide Web. In the present chapter we informally introduce some of -its basic concepts and attempt to explain to the reader encountering -them for the first time how and why they are used in the TEI -scheme. More detailed technical accounts of TEI practice in this -respect are provided in chapters , , and of these Guidelines.

- -

Strictly speaking, XML is a metalanguage, that is, a -language used to describe other languages, in this case, -markup languages. Historically, the word -markup has been used to describe annotation or other -marks within a text intended to instruct a compositor or typist how a -particular passage should be printed or laid out. Examples include -wavy underlining to indicate boldface, special symbols for passages to -be omitted or printed in a particular font, and so forth. As the -formatting and printing of texts was automated, the term was extended -to cover all sorts of special codes inserted into electronic texts to -govern formatting, printing, or other processing.

-

Generalizing from that sense, we define markup, or -(synonymously) encoding, as any means of making explicit -an interpretation of a text. Of course, all printed texts are -implicitly encoded (or marked up) in this sense: punctuation marks, -capitalization, disposition of letters around the page, even -the spaces between words all might be regarded as a kind of markup, the -purpose of which is to help the human reader determine where one word -ends and another begins, or how to identify gross structural features -such as headings or simple syntactic units such as dependent clauses -or sentences. Encoding a text for computer processing is, in -principle, like transcribing a manuscript from scriptio continuaIn the -continuous writing characteristic of manuscripts from the early -classical period, words are written continuously with no intervening -spaces or punctuation.; it is a process of making explicit what is -conjectural or implicit, a process of directing the user as to how the -content of the text should be (or has been) interpreted.

- -

By markup language we mean a set of markup conventions -used together for encoding texts. A markup language must specify how -markup is to be distinguished from text, what markup is allowed, what -markup is required, and what the markup means. XML provides the means -for doing the first three; documentation such as these Guidelines is -required for the last.

- -

The present chapter attempts to give an informal introduction to -those parts of XML of which a proper understanding is necessary to -make best use of these Guidelines. The interested reader should also -consult one or more of the many excellent introductory textbooks and -web sites now available on the subject.New -textbooks and websites about XML appear at regular intervals and to -select any one of them would be invidious. -some recommended online courses include and .

- -
What's Special about XML? - -

XML has three highly distinctive advantages: - -it places emphasis on descriptive rather than -procedural markup; -it distinguishes the concepts of syntactic correctness and of -validity with respect to a document type definition; -it is independent of any one hardware or software -system. These three aspects are discussed briefly below, -and then in more depth in the remainder of this chapter.

- -

XML is frequently compared with HTML, the language in which web -pages have generally been written, which -shares some of the above characteristics. Compared with HTML, however, -XML has some other important features: - -XML is extensible: it does not consist of a fixed set of -tags; -XML documents must be well-formed according to a defined -syntax; -an XML document can be formally validated against a set of schema rules for consistent application; -XML is more interested in the meaning of data than in its -presentation.

- -
Descriptive Markup - -

In a descriptive markup system, the markup codes used do little -more than categorize parts of a document. Markup codes such as -para or \end{list} simply identify a portion -of a document and assert of it that the following item is a -paragraph, or this is the end of the most recently begun -list, etc. By contrast, a procedural markup system defines what -processing is to be carried out at particular points in a document: -call procedure PARA with parameters 42, b, and x here or move -the left margin 2 quads left, move the right margin 2 quads right, -skip down one line, and go to the new left margin, etc. In XML, -the instructions needed to process a document for some particular -purpose (for example, to format it) are sharply distinguished from the -markup used to describe it.

- -

Usually, the markup or other information needed to process a -document will be maintained separately from the document itself, -typically in a distinct document called a stylesheet, -though it may do much more than simply define the rendition or visual -appearance of a document.We do not here discuss in -any detail the ways that a stylesheet can be used or defined, nor do -we discuss the popular W3C Stylesheet Languages XSLT and CSS. See -further , , and -.

- -

When descriptive markup is used, the same document can -readily be processed in many different ways, using only those parts of -it which are considered relevant. For example, a content analysis -program might disregard entirely the footnotes embedded in an -annotated text, while a formatting program might extract and collect -them all together for printing at the end of each chapter. Different -kinds of processing can be carried out with the same part of a file. -For example, one program might extract names of persons and places -from a document to create an index or database, while another, -operating on the same text, but using a different stylesheet, might -print names of persons and places in a distinctive typeface.

-
- -
Types of Document - -

A second key aspect of XML is its notion of a document -type: documents are regarded as having types, just as other -objects processed by computers do. The type of a document is formally -defined by its constituent parts and their structure. The definition -of a report, for example, might be that it -consisted of a title and possibly an -author, followed by an -abstract and a sequence of one or more -paragraphs. Anything lacking a title, according -to this formal definition, would not formally be a report, and neither -would a sequence of paragraphs followed by an abstract, whatever other -report-like characteristics these might have for the human reader.

- -

If documents are of known types, a special-purpose program (called -a parser), once provided with an unambiguous definition -of a document type, can check that any document claiming to be of -that type does in fact conform to the specification. A parser -can check that all elements specified for a particular -document type are present and no others, that they are combined in appropriate ways, -correctly ordered, and so forth. More significantly, different -documents of the same type can be processed in a uniform way. Programs -can be written which take advantage of the knowledge encapsulated in -the document type information, and which can thus behave in a -more intelligent fashion.

-
- -
Data Independence - -

A basic design goal of XML is to ensure that documents encoded -according to its provisions can move from one hardware and software -environment to another without loss of information. The two features -discussed so far both address this requirement at an abstract level; -the third feature addresses it at the level of the strings of data -characters that make up a document. All XML documents, -whatever languages or writing systems they employ, use the same -underlying character encoding (that is, the same method of -representing as binary data those graphic forms making up a particular -writing system).See Extensible Markup -Language (XML) 1.0, available from , Section 2.2 -Characters. This encoding is defined by an international -standard,ISO/IEC 10646-1993 Information -Technology — Universal Multiple-Octet Coded Character Set -(UCS) which is implemented by a universal character set -maintained by an industry group called the Unicode Consortium, and -known as Unicode.See Unicode -provides a standardized way of representing any of the many thousands of -discrete symbols making up the world's writing systems, past and -present.

- - -

Most modern computing systems now support Unicode directly; for -those which do not, XML provides a mechanism for the indirect -representation of single characters by means of -their character number, known as character references; see further -.

-
-
-
Textual Structures -

A text is not an undifferentiated sequence of words, much less of -bytes. For different purposes, it may be divided into many different -units, of different types or sizes. A prose text such as this one -might be divided into sections, chapters, paragraphs, and sentences. A -verse text might be divided into cantos, stanzas, and lines. Once -printed, sequences of prose and verse might be divided into volumes, -gatherings, and pages.

- -

Structural units of this kind are most often used to identify -specific locations or refer to points within a text (the third -sentence of the second paragraph in chapter ten; canto 10, line -1234; page 412, etc.) but they may also be used to -subdivide a text into meaningful fragments for analytic purposes -(is the average sentence length of section 2 different from that of -section 5? how many paragraphs separate each occurrence of the -word nature? how many pages?). -Other structural units are more clearly analytic, in that they -characterize a section of a text. A dramatic text might regard each -speech by a different character as a unit of one kind, and stage -directions or pieces of action as units of another kind. Such an -analysis is less useful for locating parts of the text (the 93rd -speech by Horatio in Act 2) than for facilitating comparisons -between the words used by one character and those of another, or those -used by the same character at different points of the play.

- -

In a prose text one might similarly wish to regard as units of -different types passages in direct or indirect speech, passages -employing different stylistic registers (narrative, polemic, -commentary, argument, etc.), passages of different authorship and so -forth. And for certain types of analysis (most notably textual -criticism) the physical appearance of one particular printed or -manuscript source may be of importance: paradoxically, one may wish to -use descriptive markup to describe presentational features such as -typeface, line breaks, use of whitespace and so forth.

- -

These textual structures overlap with one another in complex and -unpredictable ways. Particularly when dealing with texts as -instantiated by paper technology, the reader needs to be aware of both -the physical organization of the book and the logical structure of the -work it contains. Many great works (Sterne's Tristram -Shandy for example) cannot be fully appreciated without an -awareness of the interplay between narrative units (such as chapters -or paragraphs) and presentational ones (such as page divisions). For -many types of research, the interplay among different levels -of analysis is crucial: the extent to which syntactic structure -and narrative structure mesh, or fail to mesh, for example, or the -extent to which phonological structures reflect morphology.

- -
XML Structures - -

This section describes the simple and consistent mechanism for the -markup or identification of textual structure provided by XML. It -also describes the methods XML provides for the expression of rules -defining how units of textual structure can meaningfully be combined -in a text.

- -
Elements - -

The technical term used in XML for a textual unit, viewed as a -structural component, is element. Different types of -elements are given different names, but XML provides no way of -expressing the meaning of a particular type of element, other than its -relationship to other element types. That is, all one can say about -an element called (say) blort is that instances of -it may (or may not) occur within elements of type farble, and -that it may (or may not) be decomposed into elements of type -blortette. It should be stressed that XML is entirely -unconcerned with the semantics of textual elements, -because these are considered to be application dependent. It is up to -the creators of XML vocabularies (such as these Guidelines) to choose -intelligible element names and to define their -intended use in text markup. That is the chief purpose of documents -such as the TEI Guidelines. From the need to choose element names -indicative of function comes the technical term for the name of an -element type, which is generic identifier, or GI.

-

Within a marked-up text (a document instance), each -element must be explicitly marked or tagged in some way. This is done -by inserting a tag at the beginning of the element (a -start-tag) and another at its end (an -end-tag). The start- and end-tag pair are used to bracket -off element occurrences within the running text, in rather the -same way as different types of parentheses or quotation marks are used -in conventional punctuation. For example, a quotation element in a -text might be tagged as follows: -... Rosalind's -remarks This is the silliest stuff that ere I heard -of! clearly indicate ... - -As this example shows, a start-tag takes the form quote, -where the opening angle bracket indicates the start of the start-tag, -quote is the generic identifier of the element that is being -delimited, and the closing angle bracket indicates the end of the start-tag. -An end-tag takes an identical form, except that the opening angle -bracket is followed by a solidus (slash) character, so that the -corresponding end-tag is /quote.Because -the opening angle bracket has this special function in an XML -document, special steps must be taken to use that character for other -purposes (for example, as the mathematical less-than operator); see -further section . The material between -the start-tag and the end-tag (the string of words This is the -silliest stuff that ere I heard of in the example above) is known -as the content of the element. Sometimes there may be -nothing between the start and the end-tag; in this case the two may -optionally be merged together into a single composite tag with the -solidus at the end, like this: quote/.

- -
Content Models: an Example - -

An element may be empty, that is, it may have no -content at all, or it may contain just a sequence of characters with -no other elements. Often, however, elements of one type will -be embedded (contained entirely) within elements of a -different type.

- -

To illustrate this, we will consider a very simple structural -model. Let us assume that we wish to identify within an anthology -only poems, their headings, and the stanzas and lines of which they are -composed. In XML terms, our document type is the -anthology, and it consists of a series of -poems. Each poem has embedded within it one element, a -heading, and several occurrences of another, a -stanza, each stanza having embedded within it a number of -line elements. Fully marked up, a text conforming to -this model might appear as follows: - - - - The SICK ROSE - - O Rose thou art sick. - The invisible worm, - That flies in the night - In the howling storm: - - - Has found out thy bed - Of crimson joy: - And his dark secret love - Does thy life destroy. - - - -

-

It should be stressed that this example does not use -the names proposed for corresponding elements elsewhere -in these Guidelines: the above is thus not a valid TEI -document.The element names here have been chosen for -clarity of exposition; there is, however, a TEI element corresponding to -each. It will, however, serve as an introduction to the basic notions of XML. -Whitespace and line breaks have been added to the example for the -sake of visual clarity only; they have no particular significance in the -XML encoding itself. Also, the line -]]> -is an XML comment and is not treated as part of the text.

-

As it stands, the above example is what is known as a -well-formed XML document because it obeys the following simple rules: - -there is a single element -enclosing the whole document: this is known as the root -element (anthology in our case); -each element is completely contained by the root element, -or by an element that is so contained; elements do not partially -overlap one another; -a tag explicitly marks the start and end of each element. - -

-

A well-formed XML document can be processed in a number of useful -ways. A simple indexing program could extract only the relevant text -elements in order to make a list of headings, first lines, or words -used in the poem text; a simple formatting program could insert blank -lines between stanzas, perhaps indenting the first line of each, or -inserting a stanza number. Different parts of each poem could be -typeset in different ways. A more ambitious analytic program could -relate the use of punctuation marks to stanzaic and metrical -divisions.Note that this simple example has not -addressed the problem of marking elements such as sentences -explicitly; the implications of this are discussed in section . Scholars wishing to see the implications of -changing the stanza or line divisions chosen by the editor of this -poem can do so simply by altering the position of the tags. And of -course, the text as presented above can be transported from one -computer to another and processed by any program (or person) capable -of making sense of the tags embedded within it with no need for the -sort of transformations and translations needed for files which have -been saved in one or other of the proprietary formats preferred by -most word-processing programs.

- -

As we noted above, one of the attractions of XML is that it enables -us to apply our own names for the elements rather than requiring us -always to use names predefined by other agencies. Clearly, however, if -we wish to exchange our poems with others, or to include poems others -have marked up in our anthology, we will need to know a bit more about -the names used for the tags. The means that XML provides for this is -called a namespace. In our simple example, the tags just -contain a simple name. As we shall see, it is also possible to use -tags that include a qualified name, that is, a name with -an optional prefix identifying the set of names to which it -belongs. For example, we have defined an element line for the purpose of marking lines of -verse. Another person might, however, define an element called line for the purpose of marking typographic -lines, or drawn lines. Because of these different meanings, if we wish -to share data it will be necessary to distinguish the two line -components in our marked-up texts. This is achieved by including a -namespace prefix within the markup, for example like -this: This is one of my lines - -This is one of your lines]]> - -This feature is particularly important if we have different -definitions of what a line is, of course, but -there are many occasions when it is useful to distinguish groups of -tags belonging to different markup vocabularies; -we discuss this further below (). One -particularly useful namespace prefix is predefined for XML: it is -xml and we will see examples of its use below.

- -

Namespaces allow us to represent the fact that a name belongs to a -group of names, but don't allow us to do much more by way of checking -the integrity or accuracy of our tagging. Simple well-formedness alone -is not enough for the full range of what might be useful in marking up -a document. It might well be useful if, in the process of preparing -our digital anthology, a computer system could check some basic rules -about how stanzas, lines, and headings can sensibly co-occur in a -document. It would be even more useful if the system could check that -stanzas are always tagged stanza and not occasionally -canto or Stanza. An XML document in which such -rules have been checked is technically known as a valid -document, and the ability to perform such validation is one of the key -advantages of using XML. To carry this out, some way of formally -stating the criteria for successful validation is necessary: in XML -this formal statement is provided by an additional document known -as a schema.The older terms -Document Type Declaration and Document Type -Definition, both abbreviated as DTD, may also be -encountered. Throughout these Guidelines we use the term -schema for any kind of formal document grammar. -

-
-
- -
Validating a Document's Structure - -

The design of a schema may be as lax or as restrictive as the -occasion warrants. A balance must be struck between the convenience -of following simple rules and the complexity of handling real -texts. This is particularly the case when the rules being defined -relate to texts that already exist: the designer may have only the -haziest of notions as to an ancient text's original purpose or meaning -and hence find it very difficult to specify consistent rules about its -structure. On the other hand, where a new text is being prepared to -an exact specification, for entry into a textual database -of some kind for example, the more precisely stated the rules, the better they can -be enforced. Even in marking up an existing text, a restrictive set of schema rules may be beneficial, especially when applied to test a particular view or hypothesis about the text. A schema -designed for use by a small project or team is likely to take a -different position on such issues than one intended for use by a large -and possibly fragmented community. It is -important to remember that every schema results -from an interpretation of a text. There is no single schema -encompassing the absolute truth about any text, although it may -be convenient to privilege some schemas above others for particular -types of analysis.

- -

XML is widely used in environments where uniformity of document -structure is a major desideratum. In the production of technical -documentation, for example, it is of major importance that sections -and subsections should be properly nested, that cross-references -should be properly resolved and so forth. In such situations, -documents are seen as raw material to match against predefined sets -of rules. As discussed above, however, the use of simple rules can -also greatly simplify the task of tagging accurately elements of less -rigidly constrained texts. By making these schema rules explicit, scholars reduce their own burdens with consistently marking up and verifying the -electronic text. By defining and sharing their schema rules, scholars openly express a project-specific interpretation of the structure and significant particularities of the -text being encoded.

-

Schema validation for XML is usually written in the RELAX NG language () originally - developed within the OASIS Technical Committee and now an - ISO standardISO/IEC FDIS 19757-2 Document - Schema Definition Language (DSDL) — Part 2: Regular-grammar-based - validation — RELAX NG, though other older methods include the Document Type Definition - (DTD) language which XML inherited from SGML and the XML Schema language () defined by the W3C.Schema validation languages co-evolved with early markup language specifications, as summarized in Rick Jelliffe's Family Tree of Schema Languages for Markup Languages. In this chapter, and throughout these - Guidelines, we give examples using the compact - syntax of RELAX NG for ease of reading. The specifications for the TEI Guidelines are first expressed in the TEI language itself and a RELAX NG schema is generated from them for processing convenience. Details about schema customization using the TEI ODD language are addressed in , and . -

- -
An Example Schema -

For the purposes of illustrating how a schema works to restrict how XML may be written, we use the RELAX NG compact syntax in what follows. The following schema can be used to validate our example poem: - -

- -

Note that this is not the only way in which a RELAX NG schema might -be written; we have adopted this idiom, however, because it -matches that used throughout the rest of these Guidelines.

- -

A RELAX NG schema expresses rules about the possible structure of a -document in terms of patterns; that is, it defines a -number of named patterns, each of which acts as a kind of template -against which an input document can be matched. The meaning of a -pattern is expressed in a schema either by reference to other patterns, or to -a small number of fundamental built-in concepts, as we shall see. In -the example above, the word to the left of the equals sign is the -pattern's name, and the material following it declares a meaning for -the pattern. Patterns may also be of particular types; the ones that -interest us here are called element patterns and -attribute patterns. In this example we see definitions -for five element patterns. Note that we have used similar names for -the pattern and the element which the pattern describes: so, for -example, the line anthology_p = element anthology {poem_p+} defines an element pattern called anthology_p, -the value of which defines an element called -anthology. These naming conventions are -arbitrary; we could use the same name for the pattern as -for the element, but we want to make clear that the two are syntactically quite distinct. The -name, or generic identifier, of the element follows the -word element, and the content model for the -element is given within the curly braces following that. Each of -these parts is discussed further below. -

-

The last line of the schema above tells a RELAX NG validator which -element (or elements) in a document can be used as the root element: -in our case only anthology. This enables -the validator to detect whether a particular document is well-formed -but incomplete; it also simplifies the processing task by providing an -entry point.

-
Generic Identifier -

Following the word element each pattern declaration gives -the generic identifier (often abbreviated to GI) of the element being -defined, for example poem, -heading, etc. A GI may contain letters, -digits, hyphens, underscore characters, or full stops, but must begin -with a letter and may not contain a space.In XML, a single colon may also -appear in a GI, where it has a special significance related to the use -of namespaces, as further discussed in section . The characters defined by Unicode as -combining characters and as extenders are -also permitted, as are logograms such as Chinese characters. Uppercase and lowercase letters are quite -distinct: an element with the GI foo is -not the same as an element with the GI Foo; the root element of a TEI-conformant -document is TEI, not tei.

-
Content Model -

The second part of each declaration, enclosed in curly braces, is -called the content model of the element being defined, because it -specifies what may legitimately be contained within it. In RELAX NG, -the content model is defined in terms of other patterns, either by -embedding them, or (as in our examples above) by naming or referring -to them. The RELAX NG compact syntax also uses a small number of -reserved words to identify other possible contents for an element, of which by -far the most commonly encountered is text, as in this -example: it means that the element being defined may contain any valid -character data, but no elements. If an XML document is thought of as a structure -like a family tree, with a single ancestor at the top (in our case, -this would be anthology), then almost always, following the -branches of the tree downwards (for example, from anthology -to poem to stanza to line and -heading) will lead eventually to text. In our example, -heading and line are so defined, since their content -models say text only and name no embedded elements.

- -
Occurrence Indicators - -

The declaration for stanza in the example above states -that a stanza consists of one or more lines. It uses an -occurrence indicator (the plus sign) to indicate how many -times something matching the pattern line_p may be -repeated. There are three occurrence indicators: the plus sign, the -question mark, and the asterisk or star. The plus sign means that -the pattern can match one or more times; the -question mark means that it may match at most once but is not -mandatory; the star means that the pattern concerned is not -mandatory, but may match more than once. Thus, if the content model for -stanza were {line_p*}, stanzas with no lines -would be possible as well as those with more than one line. If it -were {line_p?}, again empty stanzas would be -permitted, but no stanza could have more than a single line. The -declaration for poem in the example above thus states that a -poem cannot have more than one heading, but may have none, -and that it must have at least one stanza and may have -several.

- -
Connectors -

The content model {heading_p?, stanza_p+} contains more than -one component, and thus needs additionally to specify the order in -which these patterns (heading_p and stanza_p) may appear. -This ordering is determined by the connector (the comma) -used between its components. The -comma connector indicates that the patterns concerned must appear in -the sequence given. Another commonly encountered connector is the -vertical bar, representing alternation. If the comma in this example were replaced by a vertical -bar, then a poem would consist of either a heading or just -stanzas—but not both!

-
Groups -

In our example so far, the components of each content model have -been either single patterns or text. We often need to define content models in more complicated ways, in which the components -are lists of patterns, combined by connectors. Such lists may also be -modified by occurrence indicators and themselves combined by -connectors. To demonstrate these facilities, let us expand our -example so that it may include non-stanzaic types of verse. For the sake of -demonstration, we will categorize poems as one of the following: -stanzaic, couplets, or blank -(or stichic). A blank-verse poem consists simply of -lines (we ignore the possibility of verse paragraphs for the -moment), so no additional elements need be defined -for it. We could define a couplet as a firstLine followed by a - secondLine, which distinction might be useful in a study of rhyme schemes.This example is probably not a good practice for most XML projects, since XPath provides ways of distinguishing elements in an XML structure by their position, or the order in which they appear in relation to one another, without the need to give them distinct names. - - - -

-

The patterns firstLine_p and secondLine_p define elements -firstLine and secondLine; these will have exactly -the same content model as the existing line element. We will -therefore add the following two lines to our example schema: -Next, we can change the declaration for the poem element to -include all three possibilities: That is, a poem -consists of an optional heading, followed by one or several stanzas, -or one or several couplets, or one or several lines. Note the -difference between this declaration and the following: The second version, -by applying the occurrence indicator to the group rather than to each -element within it, would allow a single poem to contain a mixture -of stanzas, couplets, and lines.

-

A group of this kind can contain text as well as named -elements: this combination, known as mixed content, -allows for elements in which the sub-components appear with -intervening stretches of character data. For example, if we wished to -mark place names wherever they appear inside our verse lines, then, -assuming we have also added a pattern for the -name element, we could change the definition for -line to -

- -

Some XML schema languages place no constraints on the way that -mixed content models may be defined, but in the XML DTD language, when -text appears with other elements in a content model, it -must always appear as the first option in an alternation; it may -appear once only, and in the outermost model group; and if the group -containing it is repeated, the star operator must be used. Although -these constraints are not strictly necessary in RELAX NG schemas, all TEI content models currently obey them.

- -

Quite complex models can be built in this way, to match -the structural complexity of many types of text. For example, consider the case of stanzaic verse in which a refrain or -chorus appears. Like a stanza, a refrain consists of repetitions of -the line element. A refrain can appear at the start of a poem only, -or as an optional addition following each stanza. This could be -expressed by a pattern such as the following: - - -That is, a poem consists of an optional heading, followed by either a -sequence of lines or an unnamed group, which starts with an optional -refrain and is followed by one or more occurrences of another group, each -member of which is composed of a stanza followed by an optional -refrain. A sequence such as refrain - stanza - stanza - -refrain follows this pattern, as does the sequence -stanza - refrain - stanza - refrain. The -sequence refrain - refrain - stanza - stanza -does not, however, and neither does the sequence stanza - -refrain - refrain - stanza. Among other conditions made -explicit by this content model are the requirements that at least one -stanza must appear in a poem, if it is not composed simply of lines, -and that if there is both a heading and a stanza they must appear in -that order.

-

Note that the apparent complexity of this model derives from the -constraints expressed informally above. A simpler model, such as - would not enforce any of them, and would therefore permit -such anomalies as a poem consisting only of refrains, or an arbitrary mixture of -lines and refrains.

- - - -

It is beyond the scope of this "Gentle Introduction to XML" to provide a complete orientation to schema writing with Relax NG, but interested readers may wish to consult more thorough tutorials on the subject.For a complete tutorial introduction to RELAX NG, see . The examples and explanation provided here may be helpful to consult when reading the schema declarations posted for groupings of TEI elements that share the same content model, such as macro.phraseSeq, whose declaration features an example of mixed text and element content. Due to the complexity of the TEI schema as expressed in Relax NG, it is best to customize its content model in TEI itself by writing an ODD, as discussed in .

-
-
-
-
Complicating the Issue -

In the simple cases described so far, we have assumed that one -can identify the immediate constituents of every element in a -textual structure. A poem consists of stanzas, and an anthology -consists of poems. Stanzas do not float around unattached to poems or -combined into some other unrelated element; a poem cannot contain an -anthology. All the elements of a given document type may be arranged -into a hierarchic structure like a family tree, with a single -ancestor at one end and many children (mostly the elements containing -simple text) at the other. For example, we could represent an anthology -containing two poems, the first of which contains two four-line -stanzas and the second a single stanza, by a tree structure like the following figure:

-
- - - -

This graphic represents the hierarchical structure of an XML document, -resembling a family tree. Most XML processing systems now use a standardized way of accessing -parts of an XML document called XPath.The official specification is at ; many -introductory tutorials are available in the XML references cited above -and elsewhere on the Web: good beginners' tutorials include , and , the latter being -available in several languages. XPath gives us a -non-graphical way of referring to any part of an XML document: for -example, we might refer to the last line of Blake's poem as -/anthology/poem[1]/stanza[2]/line[4]. The square brackets -here indicate a numerical selection: we are talking about the fourth -line in the second stanza of the first poem in the anthology. If we -left out all the square-bracketted selections, the corresponding XPath -expression would refer to all lines contained by stanzas contained by -poems contained by anthologies. An XPath expression can refer to any -collection of elements: for example, the expression -/anthology/poem refers to all poems in an anthology and -the expression /anthology/poem/heading refers to all their headings.

-

The forward slash (‘/’, U+002F SOLIDUS) within an XPath expression behaves in much the same way -as a forward slash or backslash does in a filename specification. -To use a family tree analogy, a single slash indicates that the item to the -immediate left is a parent of the item(s) to the right of it. For example, -in the XPath expression /anthology/poem, the single slash -between anthology and poem indicates that anthology is a parent of the -poem children elements. (The first forward slash in the XPath expression -indicates the document node.) In XPath, it is also possible to refer to -children, grandchildren, and other descendants of the family tree using two -forward slashes together. For example, the XPath expression /anthology/poem//line -will refer to all of the lines of all of the stanzas of all the poems, without -having to represent the stanza element in the XPath.

- -

Clearly, there are many such trees that might be drawn to describe -the structure of this or other anthologies. Some of them might be -representable as further subdivisions of this tree: for example, we -might subdivide the lines into individual words, since in our simple -example no word crosses a line boundary. Surprisingly perhaps, this -grossly simplified view of what text is (memorably termed an -ordered hierarchy of content objects (OHCO) view of text -by Renear et al.See -.) turns out to -be very effective for a large number of purposes. It is not, however, -adequate for the full complexity of real textual structures, for which -more complex mechanisms need to be employed. There are many other -trees that might be drawn which do not fit within the -anthology model which we have presented so far. We might, for -example, be interested in syntactic structures or other linguistic -constructs, which rarely respect the formal boundaries of verse. Or, -to take a simpler example, we might want to represent the pagination -of different editions of the same text.

- -

In the OHCO model of text, representation of cases where different -elements overlap so that several different trees may be identified in -the same document is generally problematic. All the elements marked -up in a document, no matter what namespace they belong to, must fit -within a single hierarchy. To represent overlapping structures, -therefore, a single hierarchy must be chosen, and the points at which -other hierarchies intersect with it marked. For example, -we might choose the verse structure as our primary hierarchy, and then -mark the pagination by means of empty elements inserted at the boundary -points between one page and the next. Or we could represent alternative -hierarchies by means of the pointing and linking mechanisms described -in chapter of these Guidelines. These mechanisms all -depend on the use of attributes, which may be used both to -identify particular elements within a document and to point to, link, -or align them into arbitrary structures.

- - -
-
Attributes -

In the XML context, the word attribute, like -some other words, has a specific technical sense. It is used to -describe information that is in some sense descriptive of a specific -element occurrence but not regarded as part of its content. For -example, you might wish to add a status attribute to -occurrences of some elements in a document to indicate their degree of -reliability, or to add an identifier attribute so that you -could refer to particular element occurrences from elsewhere within a -document. Attributes are useful in precisely such circumstances.

-

Although different elements may have attributes with the same name -(for example, in the TEI scheme, every element is defined as having an -attribute named n), they are always regarded as -different, and may have different values assigned to them. If an -element has been defined as having attributes, the attribute values -are supplied in the document instance as attribute-value -pairs inside the start-tag for the element occurrence. An -end-tag cannot contain an attribute-value specification, since it -would be redundant.

-

The order in which attribute-value pairs are supplied inside a tag -has no significance; they must, however, be separated by at least one -whitespace (blank, newline, or tab) character. The value part -must always be given inside matching quotation marks, either single or -doubleIn the unlikely event that both kinds of quotation marks are needed within the -quoted string, either or both can also be presented in escaped form, using the -predefined character entities &apos; or &quot;.

-

For example: - - ... - -Here attribute values are being specified for two attributes -previously declared for the poem element: xml:id -and status. For the instance of a poem in this -example, represented here by ellipsis points, the xml:id -attribute has the value P1 and the status -attribute has the value draft. An XML processor can use the -values of the attributes in any way it chooses; for example, a -poem in which the status attribute has the value -draft might be formatted differently from one in which the same -attribute has the value revised; another processor might use the -same attribute to determine whether or not poem elements are to be -processed at all. The xml:id attribute is a slightly -special case in that, by convention, it is always used to supply a -unique value to identify a particular element occurrence, which may be -used for cross-reference purposes, as discussed further below ().

- -
Declaring Attributes - -

Attributes are declared in a schema in the same way as elements. -As well as specifying an attribute's name and the element to which it is to be -attached, it is possible to specify (within limits) what kind of value -is acceptable for an attribute.

- -

In the compact syntax of RELAX NG, an attribute is defined by means -of an attribute pattern, like the following: - - - -This defines a new pattern, called att.status, whose -value is an attribute pattern defining an attribute named -status. Attribute names are subject to the same -restrictions as other names in XML; they need not be unique across the -whole schema, however, but only within the list of attributes for a -given element.

- -

A pattern defining the possible values for this attribute is given -within the curly braces, in just the same way as a content model is -given for an element pattern. In this case, the attribute's value must -be one of the strings presented explicitly above.

- -

The attribute pattern definition must be included or referenced -within the definition for every element to which the attribute is -attached. We therefore modify the definition for the -poem_p pattern given above as follows: - - - -In RELAX NG, an element pattern simply includes any attribute patterns -applicable to it along with its other constituents, as shown -above. Attribute patterns can also be grouped and alternated in the -same way as element patterns, though this particular feature is not -widely used in the TEI scheme, since it is not available to the same -extent in all schema languages. Because a question mark follows the -reference to the att.status pattern in our example, a -document in which the status attribute is not specified -will still be valid; without this occurrence indicator the -status attribute would be required. - -

- -

Instead of supplying a list of explicit values, an attribute -pattern can specify that the attribute must have a value of a -particular type, for example a text string, a numeric value, a -normalized date, etc. This is accomplished by supplying a pattern -that refers to a datatype. In the example above, -because a list of acceptable values is predefined, a parser can check -that no poem is defined for which the status -attribute does not have one of draft, revised, -or published as its value. By contrast, with a definition -such as a parser would accept almost any -unbroken string of characters (status="awful", -status="awe-ful", or status="12345678") as -valid for this attribute. Sometimes, of course, the set of possible -values cannot be predefined. Where it can, as in this case, it is -generally better to do so.

- -

Schema languages vary widely in the extent to which they support -validation of attribute values. Some languages predefine a small set -of possibilities. Others allow the schema designer to use values from -a predefined library of possible datatypes, or to -add their own definitions, possibly of great complexity. A -datatype might be something fairly general (any -positive integer), something very specific or idiosyncratic (any -four-character string ending with "T"), or somewhere between the -two. In the RELAX NG schemas used by the TEI, general patterns have -been defined for about half a dozen datatypes (using the W3C Schema -Datatype Library, -and discussed further in ). In addition to the two -possibilities already mentioned—plain text or an explicit list of -possible strings—other datatypes likely to be encountered include -the following: - - -values must be either true or false - -values must represent a numeric quantity of some -kind - -values must represent a possible date and time in some calendar -

-

Two further datatypes of particular usefulness in managing XML documents -are commonly known as ID—for identifier—and -URI—for Universal Resource Indicator, or pointer for -short. These are discussed in the next section.

-
-
Identifiers and Indicators -

It is often necessary to refer to an occurrence of one textual -element from within another, an obvious example being phrases such as -see note 6 or as discussed in chapter 5. When a text is -being produced the actual numbers associated with the notes or -chapters may not be certain. If we are using descriptive markup, such -things as page or chapter numbers, being entirely matters of -presentation, will not in any case be present in the marked-up text: -they will be assigned by whatever processor is operating on the text -(and may indeed differ in different applications). XML therefore -predefines an attribute that may be used to provide any element -occurrence with a special identifier, a kind of label, which may be -used to refer to it from anywhere else: since it is defined in the XML -namespace, the name of this attribute is xml:id and it is -used throughout the TEI schema. Because it is intended to act as an -identifier, its values must be unique within a given document. The -cross-reference itself will be supplied by an element bearing an -attribute of a specific kind, which must also be declared in the -schema.

-

Suppose, for example, we wish to include a reference within -the notes on one poem that refers to another poem. We will -first need to provide some way of attaching a label to each -poem: this is easily done using the xml:id attribute. -Note that not every poem need carry an xml:id attribute and -the parser may safely ignore the lack of one in those that do not. -Only poems to which we intend to refer need use this attribute; for -each such poem we should now include in its start-tag some unique -identifier, for example: - - ... - - ... - - ... - -

-

Next we need to define a new element for the cross-reference -itself. This will not have any content—it is only a -pointer—but it has an attribute, the value of which will be -the identifier of the element pointed at. This is achieved by -the following definition: - -

- -

The poemRef element has no content, but a single attribute -called target. The value of this attribute must be a -pointer or web reference of type anyURI;The word anyURI is a predefined name, used in -schema languages to mean that any Uniform Resource -Identifier (URI) may be supplied here. The accepted syntax for -URIs is an Internet Standard, defined in . anyURI -is one of the datatypes defined by the W3C -Schema datatype library. -furthermore, because there is no indication of optionality on the -attribute pattern, it must be supplied on each occurrence—a -poemRef with no referent is an impossibility.

- -

With these declarations in force, we can now encode a reference to -the poem whose xml:id attribute specifies that its -identifier is Rose as follows: - -Blake's poem on the sick rose - ... - -

-

A processor may take any number of actions when it encounters a -link encoded in this way: a formatter might construct an exact page -and line reference for the location of the poem in the current -document and insert it, or just quote the poem's title or first lines. -A hypertext style processor might use this element as a signal to -activate a link to the poem being referred to, for example by -displaying it in a new window. Note, however, that the purpose of the -XML markup is simply to indicate that a cross-reference exists: it -does not necessarily determine what the processor is to do with it.

- -

The target of a URI can be located anywhere: it may not necessarily -be part of the same document, nor even located on the same computer -system. Equally, it can be a resource of any kind, not necessarily an -XML document or document fragment. It is thus a very convenient way of -including references to non-XML data such as image files within a -document. If, for example, we wished to include an illustration -containing a reproduction of Blake's original in our anthology, the -most appropriate method would probably be to define a new element -called (for the sake of argument) graphic -with a target attribute of datatype URI: - With these additions to the schema, we -can now represent the location of the illustration within our text -like this: - By providing a location from which a reproduction of -the required image can be downloaded, this encoding makes it possible -for appropriate software able to display the image as well as record -its existence.

-

Attributes form part of the structure of an XML document in the -same way as elements, and can therefore be accessed using XPath. For -example, to refer to all the poems in our anthology whose -status attribute has the value draft, we might -use an XPath such as /anthology/poem[@status='draft']. To -find the headings of all such poems, we would use the XPath -/anthology/poem[@status='draft']/heading.

-
-
- -
Other Components of an XML Document - -

In addition to the elements and attributes so far discussed, an XML -document can contain a few other formally distinct things. An XML -document may contain references to predefined strings of data that a -validator must resolve before attempting to validate the document's -structure; these are called entity references. They may -be useful as a means of providing boilerplate text or -representing character data which cannot easily be keyboarded. As -noted earlier, an XML document may also contain instances of elements -taken from some other namespace. And an XML -document may also contain arbitrary signals or flags for use when the -document is processed in a particular way by some class of processor -(a common example in document production is the need to force a -formatter to start a new page at some specific point in a document); -such flags are called processing instructions. We discuss each of these -three cases in the rest of this section.

- -

The XML declaration should be supplied at the very -beginning of every XML file; while it looks like a processing -instruction, it is not, and may not occur anywhere other than at the -very beginning of an XML file. For example: ]]> The XML declaration specifies -the version number of the XML Recommendation applicable to the -document it introduces (in this case, version 1.0), and optionally -also the character encoding used to represent the Unicode characters -within it. By default an XML document uses the character encoding -UTF-8 or UTF-16; other commonly-encountered encodings include ISO -8859-1. If any character present in the document is not available in -the specified character encoding, it must be represented as a -character reference (). The XML declaration is -documentary, but should normally be supplied at the start of any XML -file. If it is missing many XML-aware processors will be unable to -process the associated text correctly.

- -
Character References - -

As mentioned above, all XML documents use the same internal -character encoding. Since not all computer systems currently support -this encoding directly, a special syntax is defined -that can be used to represent individual characters from the Unicode -character set in a portable way by providing their numeric value, in -decimal or hexadecimal notation.

- -

For example, the character é is represented -within an XML document as the Unicode character with hexadecimal value -00E9. If such a document is being prepared on (or -exported to) a system using a different character set in which this -character is not available, it may instead be represented by the -character reference &#x00E9; (the x indicating -that what follows is a hexadecimal value) or -&#0233; (its decimal equivalent). References of this type do not need -to be predefined, since the underlying character encoding for XML is -always the same.

- -

To aid legibility, however, it is also possible to use a mnemonic -name (such as eacute) for such character references, -provided that each such name is mapped to the required Unicode value -by means of a construct known as an entity -declaration. A reference to a named character entity always -takes the form of an ampersand, followed by the name, followed by a -semicolon. For example an XML document containing the string -T&C might be encoded as T&amp;C.

- -

There is a small set of such character -entity references that do not have to be declared because they form -part of the definition of XML. These include the names used for -characters such as the ampersand (amp) and the open angle -bracket or less-than sign (lt), which could not easily -otherwise be included in an XML document without ambiguity. Other -predeclared entity names are those for quotation marks (quot -and apos for double and single respectively), and for -completeness the closing angle bracket or greater-than sign -(gt).

- -

For all other named character entities, a set of entity declarations -must be provided to an XML processor before the document referring to -them can be validated. The declaration itself uses a non-XML syntax -inherited from SGML; for example, to define an entity named -eacute with the replacement value é, the declaration -could have any of the following forms: ]]> or, using hexadecimal notation: ]]> or, using decimal notation: -]]> -

- -

Entities of this kind are useful also for string -substitution purposes, where the same text needs to be repeated -uniformly throughout a text. For example, if a declaration such as -]]> is included with a document, -then references such as &TEI; may be used within it, -each of which will be expanded in the same way and replaced by the -string Text Encoding Initiative before the text is validated.

- - -
-
Namespaces - -

A valid XML document necessarily specifies the schema in which its -constituent elements are defined. However, a well-formed XML document -is not required to specify its schema (indeed, it may not even have a -schema). It would still be useful to indicate that the element names used -in it have some defined provenance. Furthermore, it might be desirable -to include in a document elements that are defined (possibly -differently) in different schemas. A cabinet-maker's schema might well -define an element called table with very different -characteristics from those of a documentalist's.

-

The concept of namespace was introduced into the XML -language as a means of addressing these and related problems. If the -markup of an XML document is thought of as an expression in some -language, then a namespace may be thought of as analogous to the -lexicon of that language. Just as a document can contain words taken -from different languages, so a well-formed XML document can include -elements taken from different namespaces. A namespace resembles a -schema in that we may say that a given -set of elements belongs to a given namespace, or -are defined by a given schema. However, a schema -is a set of element definitions, whereas a namespace is really only a -property of a collection of elements: the only tangible form it takes -in an XML document is its distinctive prefix and the -identifying name associated with it.

- -

Suppose for example that we wish to extend our anthology to include -a complex diagram. We might start by considering whether or -not to extend our simple schema to include XML markup for such -features as arcs, polygons, and other graphical elements. XML can be -used to represent any kind of structure, not simply text, and there -are clear advantages to having our text and our diagrams all expressed -in the same way.

-

Fortunately we do not need to invent a schema for the -representation of graphical components such as diagrams; it already -exists in the shape of the Scalable Vector Graphics (SVG) language -defined by the W3C.The W3C Recommendation is -defined at . SVG -is a widely used and rich XML vocabulary for representing all kinds of -two-dimensional graphics; it is also well supported by existing -software. Using an SVG-aware drawing package, we can easily draw our -diagram and save it in XML format for inclusion within our -anthology. When we do so, we need to indicate that this part of -the document contains elements taken from the SVG namespace, if only -to ensure that processing software does not confuse our line -element with the SVG line, which means something quite -different.

-

An XML document need not specify any namespace: it is then said to -use the null namespace. Alternatively, the root element of a -document may supply a default namespace, understood to apply to all elements which have no namespace prefix. This is the function of the -xmlns attribute which provides a -unique name for the default namespace, in the form of a URI: - - - - - -In exactly the same way, on the root element for each part of our -document which uses the SVG language, we might introduce the SVG -namespace name: - - - - - - - - - -Although a namespace name usually uses the URI (Uniform Resource -Identifier) syntax, it is not treated as an online address -and an XML processor regards it just as a string, providing a longer name for the -namespace.

-

The xmlns attribute can also be used to associate a short prefix -name with the namespace it defines. This is very useful if we want to -mingle elements from different namespaces within the same document, -since the prefix can be attached to any element, overriding the -implicit namespace for itself (but not its children): - - - - - - - - - -

-

There is no limit on the number of namespaces that a document can -use. Provided that each is uniquely identified, an XML processor can -identify those that are relevant, and validate them appropriately. To -extend our example further, we might decide to add a linguistic -analysis to each of the poems, using a set of elements such as aux, adj, etc., -derived from some pre-existing XML vocabulary for linguistic analysis. - - - - - - - - O - Rose - thou - art - sick - - - -

- -
Marked Sections -

We mentioned above that the syntax of XML requires the encoder to -take special action if characters with a syntactic meaning in XML -(such as the left angle bracket or ampersand) are to be used in a -document to stand for themselves, rather than to signal the start of a -tag or an entity reference respectively. The predefined entities -&amp;, &lt;, and -&gt; provide one method of dealing with this problem, -if the number of occurrences of such things is small. Other methods -may be considered when the number is large, as in an XML document like -the present Guidelines, which contains hundreds of examples of XML -markup. One is to label the XML examples as belonging to a different -namespace from that of the document itself, which is the approach -taken in the present Guidelines. Another and simpler approach is -provided by one of the features inherited by XML from its parent SGML: -the marked section.

-

A marked section is a block of text within an XML document -introduced by the characters <![CDATA[ and terminated -by the characters ]]>. Between these rather strange -brackets, markup recognition is turned off, and any tags or entity -references encountered are therefore treated as if they were plain -text. For example, when we come to write the users' manual for our -anthology, we may find ourselves often producing text like the -following: -line element: -[...]]]]]>]]>

- -
-
- -
Processing Instructions - -

Although one of the aims of using XML is to remove any information -specific to the processing of a document from the document itself, it -is occasionally very convenient to be able to include such information—if -only so that it can be clearly distinguished from the -structure of the document. As suggested above, one common example is -the need, when processing an XML document for printed output, to -include a suggestion that the formatting processor might use to -determine where to begin a new page of output. Page-breaking decisions -are usually best made by the formatting engine alone, but there will -always be occasions when it may be necessary to override these. An XML -processing instruction inserted into the document is one very simple -and effective way of doing this without interfering with other aspects -of the markup.

-

Here is an example XML processing instruction: ]]> It begins with <? and ends with -?>. In between are two strings separated by a space: -the first is the name of some processor (tex in the above -example) and the second is some data intended for the use of that -processor (in this case, the instruction to start a new page). The -only constraint placed by XML on the strings is that the first one -must be a valid XML name other than XML, -Xml, or xml, etc. The second string can be -any arbitrary sequence of characters, not including the closing -character-sequence ?>.

-
-
- -
Putting It All Together - -

In this chapter we have discussed most of the components of an XML -document and its associated schema. We have described informally -how an XML document is represented, and also introduced one -way of representing the rules a RELAX NG validator might use to -validate it. In a working system, the following issues will also need -to be addressed: - -how does a processor determine the schema (or schemas) that -should be used to validate a given XML document instance? -if a document contains entity references that must be processed before the -document can be validated, where are those entities defined? -an XML document instance may be stored in a number of different -operating system files; how should they be assembled together? -how does a processor determine which stylesheets it should use -when processing an XML document, or how to interpret any processing -instructions it contains? -how does a processor enforce more exact validation than simple -datatypes permit (for example of element content)? - -

- -

Different schema languages and different XML processing systems -take very different positions on all of these topics, since none of -them is explicitly addressed in the XML specification itself. Consequently, -the best answer is likely to be specific to a particular software -environment and schema language. Since this chapter is concerned with -XML considered independently of its processing environment, we only -address them in summary detail here.

- -
Associating Entity Definitions with a Document -Instance -

In we introduced the syntax used for the -definition of named character entities such as eacute, -which XML inherited from SGML. Different schema languages vary in the -ways they make a collection of such definitions available -to an XML processor, but fortunately there is one method that all -current schema languages support.

-

As well as, and following, the XML declaration (), an XML document instance may be prefixed with a -special DOCTYPE statement. This declarative statement has -been inherited by XML from SGML; in its full form it provides a large -number of facilities, but we are here concerned only with the small -subset of those facilities recognized by all schema languages.

-

Here is an example DOCTYPE statement which we might consider -prefixing to the final version of our anthology: - - -]>]]> -Any XML processor encountering this statement will use it to add the -two named entities it defines to those already predefined for -XML. Before the document instance itself is validated, any references -to these entities will be expanded to the character string -given. Thus, wherever in the document instance the string -&legalese; appears, it will be replaced by the -formulation above. This makes life a little easier for those -keyboarding our anthology.And, indeed, for those -responsible for deciding the licensing conditions if they change their -minds later. The word anthology following the string -DOCTYPE in this example is, of course, the name of the root element of -the document to which this declaration is prefixed; however, only an XML -DTD processor will take note of this fact.

- -
Associating a Document Instance with Its Schema - -

In the past, different schema languages adopted entirely different attitudes to -this question, leading to a variety of different methods of associating schemas with -document instances. However, a W3C Working Group Note, - Associating Schemas with XML documents, -() now provides a -standardized method of doing this through the use of a processing instruction: - - ]]> - -The href pseudo-attribute points to the location of the schema. This is the only mandatory - pseudo-attribute, but others can be added to give more information about the schema: - - ]]> - -See the XML Model WG Note for more information on the pseudo-attributes available and -how to use them.

- -

A document instance may be valid according to many -different schemas, each appropriate to a different processing task. All of these may be expressed in the same way: - - -]]> - -This example includes a standard schema in XML Schema format, along with a Schematron schema which might be -used for checking the format and linking of names.

- -

Any modern XML processing software tool will provide -convenient methods of validating documents which are appropriate to the particular -schema language chosen. In the interests of maximizing portability of -document instances, they should contain as little processing-specific -information as possible.

- -
-
Assembling Multiple Resources into a Single Document -

As we have already indicated, a single XML document may be made up -of several different operating system files that need to be pulled -together by a processor before the whole document can be -validated. The XML DTD language defines a special kind of entity (a -system entity) that can be used to embed references to -whole files into a document for this purpose, in much the same way as -the character or string entities discussed in . Neither RELAX NG nor W3C Schema directly supports -this mechanism, however, and we do not -discuss it further here.

-

An alternative way of achieving the same effect is to use a special -kind of pointer element to refer to the resources that need to be -assembled, in exactly the same way as we proposed for the illustration -in our anthology. The W3C Recommendation XML Inclusions - (XInclude). defines a generic mechanism -for this purpose, which is supported by an increasing number of XML -processors.

- -
Stylesheet Association and Processing -

As mentioned above, the processing of an XML document will usually -involve the use of one or more stylesheets, often but not exclusively -to provide specific details of how the document should be displayed or -rendered. In general, there is no reason to associate a document -instance with any specific stylesheet and the schema languages we have -discussed so far do not therefore make any special provision for such -association. The association is made when the stylesheet processor is -invoked, and is thus entirely application-specific.

-

However, since one very common application for XML documents is to -serve them as browsable documents over the Web, the W3C has defined a -procedure and a syntax for associating a document instance with its -stylesheet (see ). This Recommendation -allows a document to supply a link to a default stylesheet and also to -categorize the stylesheet according to its MIME type, -for example to indicate whether the stylesheet is written in CSS or -XSLT, using a specialized form of processing instruction.

-

Assuming therefore that we have made a CSS-conformant stylesheet -for our anthology and stored it in a file called -anthology.css which is available from the same location -as the anthology itself, we could make it available over the Web simply -by adding a processing instruction like the following to the anthology: -]]>

-

Multiple stylesheets can be defined for the same document, and -options are available to specify how a web browser should select -amongst them. For example, if the document also contained a directive: -]]>a different stylesheet -called anthology_m.css could be used when rendering the -document on a handheld device such as a mobile phone.

-

Most modern web browsers support CSS (although the extent -of their implementation varies), and some of them -support XSLT.

- -
Content Validation - -

As we noted above, most schema languages provide some degree of -datatype validation for attribute values (). They vary greatly in the validation facilities -they offer for the content of elements, other than the syntactic -constraints already discussed. Thus, while we may very easily check -that our stanza elements contain only line elements, we cannot easily check that line elements contain between five and 500 -correctly-spelled English words, should we wish to constrain our -poetry in such a way. Also, because attributes and elements are -treated differently, it is difficult or impossible to express -co-occurrence constraints: for example, if the status of a poem is draft we might -wish to permit elements such as editorialQuery within its content, but not -otherwise.

- -

The XML DTD language offers very little beyond syntactic checking -of element content. By contrast, a major impetus behind the design and -development of the W3C schema language was the addition of a much more -general and powerful constraint language to the existing structural -constraints of XML DTDs. In RELAX NG the opposite approach was taken, -in that all datatype validation, whether of attributes or element -content, is regarded as external to the schema language. For -attributes, as we have seen, RELAX NG makes use of the W3C Schema -Datatype Library (but permits use of others). Because RELAX NG treats -both elements and attributes as special cases of patterns, the same -datatype validation facilities are available for element content as -for attribute values; it is unlike other schema languages in -this respect. In addition, for content validation, -a different component of DSDL known as Schematron can be used. Schematron -is a pattern matching (rather than a grammar-based) language, which -allows us to test the components of a document against -templates that express constraints such as those mentioned above.

- -

Like other XML processors, Schematron uses XPath to identify parts -of an XML document; in addition, it provides elements that describe -assertions to be tested and conditions which must be validated, as -well as elements to report the results of the test.

-
-
diff --git a/P5/Source/Guidelines/fr/SG-GentleIntroduction.xml b/P5/Source/Guidelines/fr/SG-GentleIntroduction.xml new file mode 120000 index 0000000000..7d37fad42f --- /dev/null +++ b/P5/Source/Guidelines/fr/SG-GentleIntroduction.xml @@ -0,0 +1 @@ +../en/./SG-GentleIntroduction.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/ST-Infrastructure.xml b/P5/Source/Guidelines/fr/ST-Infrastructure.xml deleted file mode 100644 index 9a981eb043..0000000000 --- a/P5/Source/Guidelines/fr/ST-Infrastructure.xml +++ /dev/null @@ -1,1425 +0,0 @@ - - - - -
- The TEI Infrastructure -

This chapter describes the infrastructure for the encoding scheme defined by these Guidelines. - It introduces the conceptual framework within which the following chapters are to be understood, - and the means by which that conceptual framework is implemented. It assumes some familiarity - with XML and XML schemas (see chapter ) but is intended to be accessible to - any user of these Guidelines. Other chapters supply further technical details, in particular - chapter which describes the XML schema used to express these Guidelines - themselves, and chapter which combines a discussion of modification and - conformance issues with a description of the intended behaviour of an ODD processor; these - chapters should be read by anyone intending to implement a new TEI-based system.

-

The TEI encoding scheme consists of a number of modules, each of which declares - particular XML elements and their attributes. Part of an element's declaration includes its - assignment to one or more element classes. Another part defines its possible - content and attributes with reference to these classes. This indirection gives the TEI system - much of its strength and its flexibility. Elements may be combined more or less freely to form a - schema appropriate to a particular set of requirements. It is also easy to add - new elements which reference existing classes or elements to a schema, as it is to exclude some - of the elements provided by any module included in a schema.

-

In principle, a TEI schema may be constructed using any combination of modules. However, - certain TEI modules are of particular importance, and should always be included in all but - exceptional circumstances: the module tei described in the present - chapter is of this kind because it defines classes, macros, and datatypes which are used by all - other modules. The core module, defined in chapter contains declarations for elements and attributes which are likely to be needed - in almost any kind of document, and is therefore recommended for global use. The header module defined in chapter provides - declarations for the metadata elements and attributes constituting the TEI header, a component - which is required for TEI conformance, while the textstructure - module defined in chapter declares basic structural elements needed for the - encoding of most book-like objects. Most schemas will therefore need to include these four - modules.

-

The specification for a TEI schema is itself a TEI document, using elements from the module - described in chapter : we refer to such a document informally as an - ODD document, from the design goal originally formulated for the system: One - Document Does it all. Stylesheets for maintaining and processing ODD documents are - maintained by the TEI, and these Guidelines are also maintained as such a document. As further - discussed in , an ODD document can be processed to generate a schema - expressed using any of the three schema languages currently in wide use: the XML DTD language, - the ISO RELAX NG language, or the W3C Schema language, as well as to generate documentation such - as the Guidelines and their associated web site.

-

The bulk of this chapter describes the TEI infrastructure module itself. Although it may be - skipped at a first reading, an understanding of the topics addressed here is essential for - anyone planning to take full advantage of the TEI customization techniques described in chapter - .

-

The chapter begins by briefly characterizing each of the modules available in the TEI scheme. - Section describes in general terms the method of constructing a TEI schema - in a specific schema language such as XML DTD language, RELAX NG, or W3C Schema.

-

The next and largest part of the chapter introduces the attribute and element classes used to - define groups of elements and their characteristics (section ).

-

Finally, section introduces the concept of macros, which - are used to express some commonly used content models, and lists the datatypes used - to constrain the range of legal values for TEI attributes (section ).

-
- TEI Modules -

These Guidelines define several hundred elements and attributes for marking up documents of - any kind. Each definition has the following components: - a prose description - a formal declaration, expressed using a special-purpose XML vocabulary defined by - these Guidelines in combination with elements taken from the ISO schema language RELAX - NG - usage examples -

-

Each chapter of these Guidelines presents a group of related elements, and also defines a - corresponding set of declarations, which we call a module. All the definitions - are collected together in the reference sections provided as an appendix. Formal declarations - for a given chapter are collected together within the corresponding module. For convenience, - each element is assigned to a single module, typically for use in some specific application - area, or to support a particular kind of usage. A module is thus simply a convenient way of - grouping together a number of associated element declarations. In the simple case, a TEI - schema is made by combining together a small number of modules, as further described in - section below.

-

The following table lists the modules defined by the current release of these Guidelines: - - - - Module name - Formal public identifier - Where defined - - - analysis - Analysis and Interpretation - - - - certainty - Certainty and Uncertainty - - - - core - Common Core - - - - corpus - Metadata for Language Corpora - - - - - dictionaries - Print Dictionaries - - - - drama - Performance Texts - - - - figures - Tables, Formulae, Figures - - - - gaiji - Character and Glyph Documentation - - - - header - Common Metadata - - - - iso-fs - Feature Structures - - - - linking - Linking, Segmentation, and Alignment - - - - msdescription - Manuscript Description - - - - namesdates - Names, Dates, People, and Places - - - - nets - Graphs, Networks, and Trees - - - - spoken - Transcribed Speech - - - - tagdocs - Documentation Elements - - - - tei - TEI Infrastructure - - - - - textcrit - Text Criticism - - - - textstructure - Default Text Structure - - - - transcr - Transcription of Primary Sources - - - - verse - Verse - - -
-

-

For each module listed above, the corresponding chapter gives a full description of the - classes, elements, and macros which it makes available when it is included in a schema. Other - chapters of these Guidelines explore other aspects of using the TEI scheme.

-
-
- Defining a TEI Schema -

To determine that an XML document is valid (as opposed to merely well-formed), its structure - must be checked against a schema, as discussed in chapter . For a valid TEI - document, this schema must be a conformant TEI schema, as further defined in chapter . Local systems may allow their schema to be implicit, but for interchange - purposes the schema associated with a document must be made explicit. The method - of doing this recommended by these Guidelines is to provide explicitly or by reference a TEI - schema specification against which the document may be validated.

-

A TEI-conformant schema is a specific combination of TEI modules, possibly also including - additional declarations that modify the element and attribute declarations contained by each - module, for example to suppress or rename some elements. The TEI provides an - application-independent way of specifying a TEI schema by means of the schemaSpec - element defined in chapter . The same system may also be used to specify a - schema which extends the TEI by adding new elements explicitly, or by reference to other XML - vocabularies. In either case, the specification may be processed to generate a formal schema, - expressed in a variety of specific schema languages, such as XML DTD language, RELAX NG, or - W3C Schema. These output schemas can then be used by an XML processor such as a validator or - editor to validate or otherwise process documents. Further information about the processing of - a TEI formal specification is given in chapter .

-
- A Simple Customization -

The simplest customization of the TEI scheme combines just the four recommended modules - mentioned above. In ODD format, this schema specification takes this form: - - - - - - -

-

This schema specification contains references to each of four modules, identified by the - key attribute on the moduleRef element. The schema specification - itself is also given an identifier (TEI-minimal). An ODD processor will - generate an appropriate schema from this set of declarations, expressed using the XML DTD - language, the ISO RELAX NG language, the W3C Schema language, or in principle any other - adequately powerful schema language. The resulting schema may then be associated with the - document instance by one of a number of different mechanisms, as further described in - chapter . The start point (or root element) of document instances to be - validated against the schema is specified by means of the start attribute. - Further information about the processing of an ODD specification is given in .

-
-
- A Larger Customization -

These Guidelines introduce each of the modules making up the TEI scheme one by one, and - therefore, for clarity of exposition, each chapter focusses on elements drawn from a single - module. In reality, of course, the markup of a text will draw on elements taken from many - different modules, partly because texts are heterogeneous objects, and partly because - encoders have different goals. Some examples of this heterogeneity include: - a text may be a collection of other texts of different types: for example, an - anthology of prose, verse, and drama; - a text may contain other smaller, embedded texts: for example, a poem or song - included in a prose narrative; - some sections of a text may be written in one form, and others in a different form: - for example, a novel where some chapters are in prose, others take the form of - dictionary entries, and still others the form of scenes in a play; - an encoded text may include detailed analytic annotation, for example of rhetorical - or linguistic features; - an encoded text may combine a literal transcription with a diplomatic edition of the - same or different sources; - the description of a text may require additional specialized metadata elements, for - example when describing manuscript material in detail. -

-

The TEI provides mechanisms to support all of these and many other use cases. The - architecture permits elements and attributes from any combination of modules to co-exist - within a single schema. Within particular modules, elements and attributes are provided to - support differing views of the granularity of a text, for example: - - a definition of a corpus or collection as a series of TEI documents, - sharing a common TEI header (see chapter ) - a definition of composite texts which combine optional front- and back-matter with a - group of collected texts, themselves possibly composite (see section ) - an element for the representation of embedded texts, where one - narrative appears to float within another (see section ) -

-

Subsequent chapters of these Guidelines describe in detail markup constructs appropriate - for these and many other possible features of interest. The markup constructs can be - combined as needed for any given set of applications or project.

-

For example, a project aiming to produce an ambitious digital edition of a collection of - manuscript materials, to include detailed metadata about each source, digital images of the - content, along with a detailed transcription of each source, and a supporting biographical - and geographical database might need a schema combining several modules, as follows: - - - - - - - - - - - - -

-

Alternatively, a simpler schema might be used for a part of such a project: those preparing - the transcriptions, for example, might need only elements from the core, textstructure, and transcr modules, and might therefore prefer to use a simpler schema such as that - generated by the following: - - - - - -

-

The TEI architecture also supports more detailed customization beyond the simple selection - of modules. A schema may suppress elements from a module, suppress some of their attributes, - change their names, or even add new elements and attributes. Detailed discussion of the kind - of modification possible in this way is provided in and conformance - rules relating to their application are discussed in . These facilities - are available for any schema language (though some features may not be available in all - languages). The ODD language also makes it possible to combine TEI and non-TEI modules into - a single schema, provided that the non-TEI module is expressed using the RELAX NG schema - language (see further ).

-
-
-
- The TEI Class System -

The TEI scheme distinguishes about five hundred different elements. To aid comprehension, - modularity, and modification, the majority of these elements are formally classified in some - way. Classes are used to express two distinct kinds of commonality among elements. The - elements of a class may share some set of attributes, or they may appear in the same locations - in a content model. A class is known as an attribute class if its members share - attributes, and as a model class if its members appear in the same locations. In - either case, an element is said to inherit properties from any classes of which - it is a member.

-

Classes (and therefore elements which are members of those classes) may also inherit - properties from other classes. For example, supposing that class A is a member (or a - subclass) of class B, any element which is a member of class A will inherit not - only the properties defined by class A, but also those defined by class B. In such a - situation, we also say that class B is a superclass of class A. The properties of - a superclass are inherited by all members of its subclasses.

-

A basic understanding of the classes into which the TEI scheme is organized is strongly - recommended and is essential for any successful customization of the system.

-
- Attribute Classes -

An attribute class groups together elements which share some set of common attributes. - Attribute classes are given names composed of the prefix att., often followed - by an adjective. For example, the members of the class att.canonical have in common a key and a ref attribute, - both of which are inherited from their membership in the class rather than individually - defined for each element. These attributes are said to be defined by (or inherited from) the - att.canonical class. If another element were to be added to - the TEI scheme for which these attributes were considered useful, the simplest way to - provide them would be to make the new element a member of the att.canonical class. Note also that this method ensures that the attributes in - question are always defined in the same way, taking the same default values etc., no matter - which element they are attached to.

-

Some attribute classes are defined within the tei - infrastructural module and are thus globally available. Other attribute classes are specific - to particular modules and thus defined in other chapters. Attributes defined by such classes - will not be available unless the module concerned is included in a schema.

-

The attributes provided by an attribute class are those specified by the class itself, - either directly, or by inheritance from another class. For example, the attribute class - att.pointing.group provides attributes domains and - targFunc to all of its members. This class is however a subclass of the att.pointing class, from which its members also inherit the - attributes target, targetLang and evaluate. Members of the - class att.pointing will thus have these three attributes, while - members of the class att.pointing.group will have all five.

-

Note that some modules define superclasses of an existing infrastructural class. For - example, the global attribute class att.divLike makes attributes - org and sample available, while the att.metrical class, which is specific to the verse - module, provides attributes met, real, and rhyme. Because - att.metrical is defined as a superclass of att.divLike, all five of these attributes are available to elements; the - declaration for att.metrical adds its three attributes to the - three already defined by att.divLike when the verse module is included in a schema. If, however, this module is - not included in a schema, then the att.divLike class supplies - only the two attributes first mentioned.

-

Attributes specific to particular modules are documented along with the relevant module - rather than in the present chapter. One particular attribute class, known as att.global, is common to all modules, and is therefore described in - some detail in the next section. A full list of all attribute classes is given in below.

-
- Global Attributes -

The following attributes are defined in the infrastructure module for every TEI element. - - -

-

Some of these attributes (specifically xml:id, n, xml:lang, - xml:base and xml:space) are provided by the att.global attribute class itself. - The others are provided by one its subclasses att.global.rendition, - att.global.responsibility, or att.global.source. - Their usage is discussed in the following subsections.

Several other globally-available - attributes are defined by other subclasses of the att.global class. These - are provided by other modules, and are therefore discussed in the chapter discussing that module. - A brief summary table is provided in section below.

-
- Element Identifiers and Labels -

The value supplied for the xml:id attribute must be a legal - name, as defined in the World Wide Web Consortium's XML Recommendation. This means that it - must begin with a letter, or the underscore character (_), and contain no - characters other than letters, digits, hyphens, underscores, full stops, and certain - combining and extension characters.The colon is also by default a - valid name character; however, it has a specific purpose in XML (to indicate namespace - prefixes), and may not therefore be used in any other way within a name.

-

In XML names (and thus the values of xml:id in an XML TEI document) - uppercase and lowercase letters are distinguished, and thus - partTime and parttime are two distinctly - different names, and could (though perhaps unwisely) be used to denote two different - element occurrences.

-

If two elements are given the same identifier, a validating XML parser will signal a - syntax error. The following example, therefore, is not valid: -<p xml:id="PAGE1"><q>What's it going to be then, eh?</q></p> -<p xml:id="PAGE1">There was me, that is Alex, and my three droogs, that is Pete, -Georgie, and Dim, ... </p> -

-

For a discussion of methods of providing unique identifiers for elements, see section - .

-

The n attribute also provides an identifying name or number for an element, - but in this case the information need not be a legal xml:id value. Its value - may be any string of characters; typically it is a number or other similar enumerator or - label. For example, the numbers given to the items of a numbered list may be recorded - with the n attribute; this would make it possible to record errors in the - numeration of the original, as in this list of chapters, transcribed from a faulty - original in which the number 10 is used twice, and 11 is omitted: - About These Guidelines - A Gentle Introduction to XML - Verse - Drama - Spoken Materials - Dictionaries - The n attribute may also be used to record non-unique names - associated with elements in a text, possibly together with a unique identifier as in the - following example:

- -
- -
-
-

-

As noted above there is no requirement to record a value for either the - xml:id or the n attribute. Any XML processor can identify the - sequential position of one element within another in an XML document without any - additional tagging. An encoding in which each line of a long poem is explicitly labelled - with its numerical sequence such as the following - - - - - is therefore probably redundant.

-
-
- Language Indicators -

The xml:lang attribute indicates the natural language and writing system - applicable to the content of a given element. If it is not specified, the value is - inherited from that of the immediately enclosing element. As a rule, therefore, it is - simplest to specify the base language of the text on the TEI element, and allow - most elements to take the default value for xml:lang; the language of an - element then need be explicitly specified only for elements in languages other than the - base language. For this reason, it is recommended practice to supply a default value for - the xml:lang attribute, either on the TEI root element, or on both - the teiHeader and the text element. The latter is appropriate in the - not uncommon case where the text element in a TEI document uses a different default - language from that of the TEI header attached to it. Other language shifts in the source - should be explicitly identified by use of the xml:lang attribute on an - element at an appropriate level wherever possible.

-

In the following example schematic, an English language TEI header is attached to an - English language text: - - - - - - - - -

-

The same effect would be obtained by specifying the default language for both header - and text: - - - - - - - - -

-

The latter approach is necessary in the case where the two differ: for example, where - an English language header is applied to a French text: - - - - - - - - -

-

The same principle applies at any hierarchic level. In the following example, the - default language of the text is French, but one section of it is in German: - - - - - - -

- -
-
- -
-
- -
- - - - -

-

Similarly, in the following example the xml:lang attribute on the - term element allows us to record the fact that the technical terms used are - Latin rather than English; no xml:lang attribute is needed on the q - element, by contrast, because it is in the same language as its parent.

The - constitution declares that no bill of attainder or ex post - facto law shall be passed. ...

-

-

Note that in cases where it is advisable or necessary to identify the language of the - text that is pointed at, the (non-global) attribute targetLang should be - used, for example in the pointer references text written in French.

-

The values used for the xml:lang and targetLang attributes must - be constructed in a particular way, using values from standard lists. See further .

-

Additional information about a particular language may be supplied in the - language element within the header (see section ).

-
-
- Rendition Indicators -

The rend, rendition, and style attributes are all used - to give information about the physical presentation of the text in the source. In the - following example, rend is used to indicate that both the emphasized word and - the proper name are printed in italics:

... Their motives might be pure - and pious; but he was equally alarmed by his knowledge of the ambitious Bohemond, and his ignorance of the Transalpine chiefs: - ...

The same effect might be achieved using the style - attribute, as follows:

... Their motives might be pure and pious; but he was equally alarmed by his knowledge of - the ambitious Bohemond, and his ignorance of - the Transalpine chiefs: ...

 If all or most emph and - name elements are rendered in the text by italics, it will be more convenient - to register that fact in the TEI header once and for all (using the rendition - element discussed below) and specify a rend or style value only - for any elements which deviate from the stated rendition.

-

The main difference between rend attribute and style is that the - value used for the former may contain one or more tokens from any vocabulary devised by - the encoder, separated by space characters, whereas the value used for the latter must - be a single string taken from a formally-defined style definition language such as CSS. - The rend attribute values are sequence-indeterminate set of - whitespace-separated tokens, whereas style values allow whitespace and - sequence relationships as part of the formally-defined style definition language.

-

The rendition element defined in may be used to hold - repeatedly-used format descriptions. A rendition element can then be associated - with any element, either by default, or by means of the global rendition - attribute. For example: - - - font-style: italic; - - font-family: serif; - - - - -

-

- -

-

- -

-
- - - -

-

The rendition attribute always points to one or more rendition - elements, each of which defines some aspect of the rendering or appearance of the text - in its original form. These details may most conveniently be described using a formal - style definition language, such as CSS () or XSL-FO (); in some other formal language developed for a specific project; or - even informally in running prose. Although languages such as CSS and XSL-FO are - generally used to describe document output to screen or print, they nonetheless provide - formal and precise mechanisms for describing the appearance of source documents, - especially print documents, but also many aspects of manuscript documents. For example, - both CSS and XSL-FO provide mechanisms for describing typefaces, weight, and styles; - character and line spacing; and so on.

-

As noted above, the style attribute is provided for encoders wishing to - describe the appearance of individual source elements using a language such as CSS - directly rather than by reference to a rendition element. Its value may be any - expression in the chosen formal style definition language.

-

Formal definition languages such as CSS typically identity a series of - properties (such as font-style or margin-left) for which - values are specified. A sequence of such property-value pairs makes up a - stylesheet. The TEI uses such languages simply to describe the appearance of a source - document, rather than to control how it should be formatted.

-

In the TEI scheme, it is possible to supply information about the appearance of - elements within a source document in the following distinct ways: - One or more properties may be specified as the - default for a set of elements (based on an external - scheme, by default CSS), using rendition elements - and their selector attributes; - One or more properties may be specified for individual element occurrences, - using the rend attribute with any convenient set of one or more - sequence-indeterminate tokens; - One or more properties may be specified for individual element occurrences, - using the rendition attribute to point to rendition elements; - One or more properties may be supplied explicitly for individual element - occurrences, using the style attribute. - -

-

If the same property is specified in more than one of the above ways, the one with the - highest number in the list above is understood to be applicable. The resulting - properties from each way are then combined to provide the full set of property-value - pairs applicable to the given element, and (by default) to all of its children.

-

For simplicity of processing, the same formal style definition should be used - throughout; however, the architecture does permit this to be varied, by using the - scheme attribute to indicate a different language for one or more - rendition elements. Care should be taken to ensure that such values can be - meaningfully combined. Similar considerations apply to the use of the rend - attribute, if this is used in combination with either rendition or - style.

-

Note that these TEI attributes always describe the rendition or appearance of the - source document, not intended output renditions, although often the two may - be closely related.

-
- - -
- Sources, certainty, and responsibility -

The source attribute is used to indicate the source of an element and its content, for example - by pointing to a bibliographic citation for a quotation to indicate the source from which it derives. The target of the - pointer may be an entry in a bibliographic list of some kind, or a pointer to a digital version of the source itself.

- -

As with other TEI pointers, the value of this attribute - is expressed as any form of URI, for example an absolute - URL, a relative URL, or a private scheme URI that is - expanded to a relative or absolute URL as documented in a - prefixDef. In the following typical example a - relative bare name URL value is used - to point to a bibl elsewhere in the bibliography - of the document which contains a bibliographic source for - the quotation itself: - -

- - Grammatical theories - are in flux, and the more we learn, the less we - seem to know. - -

- - The Chicago Manual of Style, - 15th edition. - Chicago: - University of Chicago Press - (2003), - p.147. - -

- Alternatively, the quotation might be directly linked to the online edition of this source using a full URI : - -

- - Grammatical theories - are in flux, and the more we learn, the less we - seem to know. - -

- -

-

The source attribute is - also used on schema documentation elements such as schemaSpec or elementRef to indicate - the location from which declarations for the components being defined may - be obtained by an ODD processor. For example, a customization wishing to include the p element specifically as it was in version 2.0.1 of TEI P5 would indicate the source for this on an elementRef element like - the following: - - - - Here the value of the source attribute is provided using - private URI syntax, using a short cut predefined for the TEI Guidelines. More generally, an ODD customization can - point to a URI from which a compiled version of any ODD can be downloaded. The above shortcut is equivalent to - - - - Elements such as moduleRef or elementRef can use the source attribute in this way to - point to any previously compiled set of TEI ODD specifications which are to be included in a schema, as further - discussed in section

- -

The cert attribute provides a method of indicating the encoder's certainty - concerning an intervention or interpretation represented by the markup. It is typically used where - the encoder wishes to supply one or more possible corrections to a text, indicating the - certainty they wish to attach to each, as in the following example: - - - Blessed are the cheesemakerspeacemakersplacemakers: -for they shall be called the children of God. - The cert attribute will usually, as here, characterize the degree of certainty simply as high, medium or low. - In situations where a more detailed or nuanced indication is required, it can instead supply a probability value between 0 (minimal - probability) and 1 (maximal probability). Other more sophisticated mechanisms are discussed in chapter . -

-

The resp attribute is used to indicate the person or organization considered responsible for some aspects - of the information encoded by an element. For example, the preceding example might be revised as follows to indicate the editors responsible - for the two corrections: - - ... peacemakers - placemakers... - When a more detailed or nuanced representation of responsibility is required, it is recommended that the element - indicated by the resp attribute should not be a generic agent (for example a person or org) - but a more precise element such as respStmt, author, or editor which can document the - exact role played by the agent. In the following example, we indicate that the correction of n to u - was made by a particular named transcriber: - - - - - Punkes, Panders, baſe extortionizing - slanues, - - - - - - Transcriber - Janelle Jenstad - - - Pointing to multiple respStmts allows the encoder to specify clearly each of the roles played in part of a TEI file (creating, transcribing, encoding, editing, proofing etc.). - If appropriate, the name element inside a respStmt may also be associated with a more detailed person - or org element using methods discussed in chapter .

-
- -
- Evaluation of Links -

Several TEI elements carry attributes whose values are defined as anyURI, - meaning that such attributes supply a link or pointer, typically expressed as a URL. - Like other XML applications, the TEI allows use of a special attribute to set the - context within which relative URLs are to be evaluated. The global attribute - xml:base is defined as part of the XML specification and belongs to the XML - namespace rather than the TEI namespace. We do not describe it in detail here: reference - information about xml:base is provided by -

-

In essence xml:base is used to set a context for all relative URLs within - the scope of the element on which it is specified. For example: - -

-

- - -

-
-
-

- - -

-
- The first ptr element here is within the scope of a - div which supplies a value for xml:base; its target is therefore - to be found at http://www.example.org/elsewhere.xml. The second - ptr, however, is within the scope of a div which does not change the - default context, and its target is therefore a document in the same directory as the current - document.

-

The xml:base attribute is intended to enable the stable resolution of - relative URIs in a document after that document's context may have changed (for example as a - result of being embedded in another document via XInclude). Setting the xml:base - simply as a way to allow encoders to write shorter URIs is not recommended. In - particular, xml:base may cause ambiguity as to the referent of same-document - references in the form #id (where id is an xml:id). - RFC 3986 states that - URIs of this type should not result in the loading of a different document. The RFC - therefore assumes that such references are internal to the document in which they are located. - Using xml:base to denote arbitrary external bases while also using same-document - references may mean that software agents deal with these links in unexpected and - inconsistent ways. Further discussion of this attribute and its effect on TEI linking methods - is provided in chapter .

-
-
- XML Whitespace -

The global attribute xml:space provides a mechanism for indicating to - systems processing an XML file how they should treat whitespace, that is, any sequences - of consecutive tab (#x09), space (#x20), carriage return (#x0D) or linefeed (#x0A) - characters. Like xml:id this attribute is defined as part of the XML - specification and belongs to the XML namespace rather than the TEI namespace. Complete - information about this attribute is provided by section 2.10 of the XML - Specification; here we provide a summary of how its use affects users of the TEI - scheme.

-

The xml:space attribute has only two permitted values: preserve - and default. The first indicates that whitespace in a text node—every - carriage return, every tab, etc.—should be maintained as is when the document is - processed. The second (which is implied when the attribute is not supplied), indicates - that whitespace should be handled as appropriate. Exactly what is - deemed appropriate is left unspecified by the XML Recommendation.

-

These Guidelines assume one of two different ways of processing whitespace will apply - in a given case, depending on an element's content model. For an element that can - contain only other elements with no intervening non-whitespace characters, whitespace is - considered to have no semantic significance, and should therefore be discarded by a - processor. For example, in a choice element, such as - - 1724 - 1728 - - since non-whitespace text is not permitted between the choice - start-tag and the sic tags or between the sic and corr tags, - any whitespace found there has no significance and can be ignored completely by a - processor.

-

Similarly, the address element has a content model containing only elements: - any punctuation or whitespace required between the lines of an address must therefore be - supplied by the processor, as any whitespace present in the input document will be - ignored.

-

Elements with content models of this type are comparatively unusual in the TEI: a list - of them is provided in the TEI release file stripspace.xsl.model, formatted there for use as an xsl:strip-space - command for XSL stylesheets.

-

Most TEI elements permit what is known as mixed-content: that is, they can contain both - text and other elements. Here the assumption of these Guidelines is that whitespace will - be normalized. This means that all space, carriage return, linefeed, and tab characters - are converted into spaces, all consecutive spaces are then deleted and replaced by one - space, and then space immediately after a start-tag or immediately before an end-tag is - deleted. The result is that this encoding, - - Edward - George - Bulwer-Lytton, Baron Lytton of - Knebworth - - - would be rendered as Edward George Bulwer-Lytton, Baron Lytton of - Knebworth. The space before his name has been removed, a space is included between - his forenames, the comma is preserved, and the newlines within his name have all been - removed.

- -

If the default treatment described above is not appropriate for a mixed content - element, the processing required may be described in the encodingDesc element - of the TEI header, but generic XML processing tools may not take note of this.

-

Alternatively, the xml:space attribute may be supplied with a value of - preserve in order to indicate that every space, tab, carriage return and - linefeed character found within that element in the document being processed is - significant. Typically, the result of that processing will be to retain the whitespace - characters in the output. Thus if the above example began persName - xml:space="preserve", the resulting text would most likely be rendered over five - lines, indented, and with a blank line following.

-

The xml:space="preserve" attribute is rarely used in TEI documents because - such layout features are generally captured with less risk and more precision by using - native TEI elements such as lb or space, or by using the renditional - attributes described in section .

-
Other Globally Available Attributes -

The following table lists for convenience other potentially available global attributes. - The table specifies the name of the attribute class providing the attributes concerned, the module which must - be included in a schema if the attributes are to be made available, and the section of these Guidelines - where the class is discussed. - - class namemodule namesee further - att.global.linkinglinking - att.global.analyticanalysis - att.global.facstranscr - att.global.changetranscr -
-

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-
-
-
- Model Classes -

As noted above, the members of a given TEI model class share the property that they can all - appear in the same location within a document. Wherever possible, the content model of a TEI - element is expressed not directly in terms of specific elements, but indirectly in terms of - particular model classes. This makes content models simpler and more consistent; it also - makes them much easier to understand and to modify.

-

Like attribute classes, model classes may have subclasses or superclasses. Just as elements - inherit from a class the ability to appear in certain locations of a document (wherever the - class can appear), so all members of a subclass inherit the ability to appear wherever any - superclass can appear. To some extent, the class system thus provides a way of reducing the - whole TEI galaxy of elements into a tidy hierarchy. This is however not entirely the - case.

-

In fact, the nature of a given class of elements can be considered along two dimensions: as - noted, it defines a set of places where the class members are permitted within the document - hierarchy; it also implies a semantic grouping of some kind. For example, the very large - class of elements which can appear within a paragraph comprises a number of other classes, - all of which have the same structural property, but which differ in their field of - application. Some are related to highlighting, while others relate to names or places, and - so on. In some cases, the set of places where class members are - permitted is very constrained: it may just be within one specific element, or - one class of element, for example. In other cases, elements may be permitted to appear in - very many places, or in more than one such set of places.

-

These factors are reflected in the way that model classes are named. If a model class has a - name containing part, such as model.divPart or model.biblPart then it is primarily defined in terms of its - structural location. For example, those elements (or classes of element) which appear as - content of a div constitute the model.divPart class; - those which appear as content of a bibl constitute the model.biblPart class. If, however, a model class has a name containing - like, such as model.biblLike or model.nameLike, the implication is that its members all have some additional - semantic property in common, for example containing a bibliographic description, or - containing some form of name, respectively. These semantically-motivated classes often - provide a useful way of dividing up large structurally-motivated classes: for example, the - very general structural class model.pPart.data (data - elements that form part of a paragraph) has four semantically-motivated member - classes (model.addressLike, model.dateLike, model.measureLike, and model.nameLike), the last of these being itself a superclass with - several members.

-

Although most classes are defined by the tei infrastructure - module, a class cannot be populated unless some other specific module is included in a - schema, since element declarations are contained by modules. Classes are not declared - top down, but instead gain their members as a consequence of - individual elements' declaration of their membership. The same class may therefore contain - different members, depending on which modules are active. Consequently, the content model of - a given element (being expressed in terms of model classes) may differ depending on which - modules are active.

-

Some classes contain only a single member, even when all modules are loaded. One reason for - declaring such a class is to make it easier for a customization to add new member elements - in a specific place, particularly in areas where the TEI does not make fully elaborated - proposals. For example, the TEI class model.rdgLike, initially - empty, is expanded by the textcrit module to include just the - TEI rdg element. A project wishing to add an alternative way of structuring - text-critical information could do so by defining their own elements and adding it to this - class.

-

Another reason for declaring single-member classes is where the class members are not - needed in all documents, but appear in the same place as elements which are very frequently - required. For example, the specialized element g used to represent a non-Unicode - character or glyph is provided as the only member of the model.gLike class when the gaiji module is added to - a schema. References to this class are included in almost every content model, since if it - is used at all the g must be available wherever text is available; however these - references have no effect unless the gaiji module is loaded.

-

At the other end of the scale, a few of the classes predefined by the tei module are - subsequently populated with very many members. For example, the class model.pPart.edit groups all the classes of element for simple editorial - correction and transcription which can appear within a p or paragraph element. The - core module alone adds more than fifty elements to this - class; the namesdates module adds another twenty, as does the - tagdocs module. Since the p element is one of the - basic building blocks of a TEI document it is not surprising that each module will need to - add elements to it. The class system here provides a very convenient way of controlling the - resulting complexity. Typically, elements are not added directly to these very general - classes, but via some intermediate semantically-motivated class.

-

Just as there are a few classes which have a single member, so there are some classes which - are used only once in the TEI architecture. These classes, which have no superclass and - therefore do not fit into the class hierarchy defined here, are a convenient way of - maintaining elements which are highly structured internally, but which appear from the - outside to be uniform objects like others at the same level.In former - editions of these Guidelines, such elements were known metaphorically as - crystals. Members of such classes can only ever appear - within one element, or one class of elements. For example, the class model.addrPart is used only to express the content model for the element - address; it references some other classes of elements, which can appear - elsewhere, and also some elements which can only appear inside an address.

-
- Informal Element Classifications -

Most TEI elements may also be informally classified as belonging to one of the following - groupings: - - high level, possibly self-nesting, major divisions of texts. These elements - populate such classes as model.divLike or model.div1Like, and typically form the largest component units - of a text. - - elements such as paragraphs and other paragraph-level elements, which can appear - directly within texts or within divisions of them, but not (usually) within other - chunks. These elements populate the class model.divPart, - either directly or by means of other classes such as model.pLike (paragraph-like elements), model.entryLike, etc. - - elements such as highlighted phrases, book titles, or editorial corrections which - can occur only within chunks, but not between them (and thus cannot appear directly - within a division). These elements populate the class model.phrase.Note that in this context, - phrase means any string of characters, and can apply to individual - words, parts of words, and groups of words indifferently; it does not refer only to - linguistically-motivated phrasal units. This may cause confusion for readers - accustomed to applying the word in a more restrictive sense. - -

-

The TEI also identifies two further groupings derived from these three: - - elements such as lists, notes, quotations, etc. which can appear either between - chunks (as children of a div) or within them; these elements populate the - class model.inter. Note that this class is not a superset - of the model.phrase and model.divPart classes but rather a distinct grouping of elements which are - both chunk-like and phrase-like. However, the classes model.phrase, model.pLike, and model.inter are all disjoint. - - elements which can appear directly within texts or text divisions; this is a - combination of the inter- and chunk- level elements defined above. These elements - populate the class model.common, which is defined as a - superset of the classes model.divPart, model.inter, and (when the dictionary module is included in a schema) - model.entryLike. - Broadly speaking, the front, body, and back of a text each comprises a series of - components, optionally grouped into divisions.

-

As noted above, some elements do not belong to any model class, and some model classes - are not readily associated with any of the above informal groupings. However, over - two-thirds of the elements defined in the present edition of - these Guidelines are classified in this way, and future editions of these recommendations - will extend and develop this classification scheme.

-

A complete alphabetical list of all model classes is provided in .

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-
-
-
- Macros -

The infrastructure module defined by this chapter also declares a number of - macros, or shortcut names for frequently occurring parts of other declarations. - Macros are used in two ways in the TEI scheme: to stand for frequently-encountered content - models, or parts of content models (); and to stand for attribute - datatypes ().

-
- Standard Content Models -

As far as possible, the TEI schemas use the following set of frequently-encountered content - models to help achieve consistency among different elements. - - - - - - - -

- - -

The present version of the TEI Guidelines includes some different - elements. shows, in descending order of frequency, the - seven most commonly used content models.

- - - - - - - - - -
-
- Datatype Specifications -

The values which attributes may take in a TEI schema are defined, for the most part, by - reference to a TEI datatype specification. Each such specification is defined - in terms of other primitive datatypes, derived mostly from W3C Schema - Datatypes, literal values, or other datatypes. This indirection makes it possible - for a TEI application to set constraints either globally or in individual cases, by - redefining the datatype definition or the reference to it respectively. In some cases, the - TEI datatype includes additional usage constraints which cannot be enforced by existing - schema languages, although a TEI-compliant processor should attempt to validate them (see - further discussion in chapter ).

-

The following element is used to define a TEI datatype: - - -

-

TEI-defined datatypes may be grouped into those which define normalized values for numeric - quantities, probabilities, or temporal expressions, those which define various kinds of - shorthand codes or keys, and those which define pointers or links.

-

The following datatypes are used for attributes which are intended to hold normalized - values of various kinds. First, expressions of quantity or probability: - - - - - - -

-

Examples of attributes using the teidata.probability - datatype include degree on damage or certainty; examples of - teidata.numeric include quantity on members of - the att.measurement class or value on - numeric; examples of teidata.count include - cols on cell and table.

- - - - - - - -

Next, the datatypes used for attributes which are intended to hold normalized dates or - times, durations, truth values, and language identifiers: - - - - - - - - - - -

-

Note that in each of these cases the values used are those - recommended by existing international standards: ISO 8601 as - profiled by XML Schema Part 2: Datatypes - Second Edition in the case of durations, times, and - date; W3C Schema datatypes in the case of truth values; and BCP - 47 in the case of language.

- - - - - - - - - - -

The following datatypes have more specialized uses: - - - - - - - - - - - - -

- - - - - - - - - - - - - -

By far the largest number of TEI attributes take values which are coded values or names of - some kind. These values may be constrained or defined in a number of different ways, each of - which is given a different name, as follows: - - - - - - - - - -

-

Attributes of type teidata.word, such as age on - person, are used to supply an identifier expressed as any kind of single token or - word. The TEI places a few constraints on the characters which may be used for this purpose: - only Unicode characters classified as letters, digits, punctuation characters, or symbols - can appear in an attribute value of this kind. Note in particular that such values cannot - include whitespace characters. Legal values include cholmondeley, été, - 1234, e_content, or xml:id, but not grand - wazoo. Attributes of this kind are sometimes used to associate (by co-reference) - elements of different types.

-

Where identifiers are defined externally, for example as part of a database or file system, - the inability to include whitespace or other special characters in a value may be - problematic. In other cases, it may also be simply more convenient to supply a short - sequence of natural language words including spaces as a single value. For these reasons, we - also provide a datatype teidata.text which does permit whitespace and indeed - any other Unicode character. Legal values include cholmondeley, été, - 1234, e-content, xml:id, and grand wazoo. This - datatype should be used with care since XML will not normalize whitespace characters within - it: for example the values n="a  b" (two spaces) and n="a   b" (three - spaces) would be considered distinct. This case should be distinguished from that of an - attribute permitting multiple values, each of which may be separated by whitespace which - will be normalized (see further ).

-

Attributes of type teidata.name are similar to those of type - teidata.word, but with the additional constraint that they - must be legal XML identifiers, as defined by the XML 1.0 specification, or successors. - Hence, they may not begin with digits or punctuation characters. Legal identifiers include - cholmondeley, été, e_content, or xml:id, but - not grand wazoo or 1234. Attributes of this kind are typically used to - represent XML element or attribute names.

-

Attributes of type teidata.xmlName are similar to those of - type teidata.name, but with the - additional constraint that they must not contain a colon - character (:, U+003A). Thus attributes of - this kind are used to represent XML element or attribute names - that do not have a namespace prefix.

-

Attributes of type teidata.prefix, such as ident - of prefixDef, are restricted to strings that form legal - URI prefixes.Technically the - specification permits the 26 uppercase letters - A-Z; however, since the canonical - form is lowercase and documents that specify schemes must do so - with lowercase letters, the TEI teidata.prefix datatype does not permit - uppercase letters. Examples of valid values are - http, https, tn3270, - xmlrpc.beep, and view-source.

-

Attributes of type teidata.enumerated, such as - new on shift or evidence supplied by att.editLike, have the same definition as teidata.word above, with the added constraint that the word supplied is taken - from a specific list of possibilities. In each case, the element or class specification - which includes the definition for the attribute will also contain a list of possible values, - together with a prose description of their intended significance. This list may be open (in - which case the list is advisory), or closed (in which case it determines the range of legal - values). In this latter case, the datatype will not be teidata.enumerated, but an explicit list of the possible values.

- - - - - - - - - - -

An attribute may, of course, take more than one value of a given type, for example a list - of pointer values, or a list of words. In the TEI scheme, this information is regarded as a - property of the datatype element used to document the attribute in question rather - than as a distinct datatype, and is provided by the - minOccurs or maxOccurs attribute. See further .

-

In a small number of cases, an attribute may take a value of either one datatype or - another. These cases are considered as distinct datatypes: - - - - -

- - - - - -
-
-
- The TEI Infrastructure Module -

The tei module defined by this chapter is a required component - of any TEI schema. It provides declarations for all datatypes, and initial declarations for - the attribute classes, model classes, and macros used by other modules in the TEI scheme. Its - components are listed below in alphabetical order: - - TEI Infrastructure - Declarations for classes, datatypes, and macros available to all TEI modules - Infrastructure de la TEI - 所有TEI模組可用的元素集、資料類型、巨集指令之宣告 - Dichiarazione di classi, tipi di dati (datatype)e macro disponibili in tutti i moduli TEI - Declaraçoes de classes, tipos de dados, e macros disponíveis em todos os módulos TEI - 全TEIモジュールで使用可能なデータ型，クラス，マクロ。 - -

-

The order in which declarations are made within the infrastructure module is critical, since - several class declarations refer to others, which must therefore precede them. Other - constraints on the order of declarations derive from the way in which the modularity of the - TEI scheme is implemented in different schema languages. The XML DTD fragment implementing - this TEI module makes extensive use of parameter entities and marked - sections to effect a kind of conditional construction; the RELAX NG schema fragment - similarly predeclares a number of patterns with null (notAllowed) values. - These issues are further discussed in chapter .

-
-
diff --git a/P5/Source/Guidelines/fr/ST-Infrastructure.xml b/P5/Source/Guidelines/fr/ST-Infrastructure.xml new file mode 120000 index 0000000000..52b6a1da6f --- /dev/null +++ b/P5/Source/Guidelines/fr/ST-Infrastructure.xml @@ -0,0 +1 @@ +../en/./ST-Infrastructure.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/TC-CriticalApparatus.xml b/P5/Source/Guidelines/fr/TC-CriticalApparatus.xml deleted file mode 100644 index d803b421f1..0000000000 --- a/P5/Source/Guidelines/fr/TC-CriticalApparatus.xml +++ /dev/null @@ -1,1239 +0,0 @@ - - - - -
- Critical Apparatus -

Scholarly editions of texts, especially texts of great antiquity or importance, often record - some or all of the known variations among different witnesses to the text. - Witnesses to a text may include authorial or other manuscripts, printed editions of the work, - early translations, or quotations of a work in other texts. Information concerning variant - readings of a text may be accumulated in highly structured form in a critical apparatus of - variants. This chapter defines a module for use in encoding such an apparatus of variants, which - may be used in conjunction with any of the modules defined in these Guidelines. It also defines - an element class which provides extra attributes for some elements of the core tag set when this - module is selected. In printed critical editions, the apparatus takes the form of highly-compressed - notes at the bottom of each page. TEI’s critical apparatus module allows variation to be encoded - so that such notes may be generated, but it also models the variation so that, for example, - interactive editions in which readers can choose which witness readings to display are possible.

- -

Information about variant readings (whether or not represented by a critical apparatus in the - source text) may be recorded in a series of apparatus entries, each entry - documenting one variation, or set of readings, in the text. Elements for the - apparatus entry and readings, and for the documentation of the witnesses whose readings are - included in the apparatus, are described in section . Special tags for - fragmentary witnesses are described in section . The available methods - for embedding the apparatus in the rest of the text, or for linking an external apparatus to the - text of the edition, are described in section . Finally, several extra - attributes for some tags of the core tag set, made available when the additional tag set for - text criticism is selected, are documented in section .

- -

Scholarly practice in representing critical editions differs widely across disciplines, time - periods, and languages. The TEI does not make any recommendations as to which text-critical - methods are best suited to any given text. Editors will wish to consider questions such as: - - What source documents will be used? Are there many witnesses, few, or one? Are the - sources relatively close copies or not? - Will there be a single base text? Or will witnesses be separately - transcribed? - If a single base text will be used, will it be that of a particular witness, or will the - editor attempt to reconstruct an ideal or original text? - Will each reading in an apparatus entry record every attestation (a positive - apparatus), or merely witnesses that deviate from the base text (a negative - apparatus)? - Will the readings of most or all witnesses be represented in the apparatus, or only a - selection the editor deems relevant? - What level of variation will require distinguishing one witness reading from another? - For example, will the editor consider an abbreviated word in a witness as agreeing with the - base text, or not? - Will conjectures (variant readings suggested by an editor) be treated differently than - readings found in witnesses? - Will there be a need to distinguish different types of variation, for example - orthographic vs. morphological or lexical variants? -

- -

Different editorial methodologies will produce different answers to these questions, and those - answers may influence choices of markup used in the edition. For example, if there will be - multiple witness transcriptions and a single apparatus, then the double - end-point attachment method may be the best choice of apparatus linking style. The parallel segmentation method may present several advantages to editors - producing an edition with a single base text. Editors of single-source editions may care to note - material aspects of the text (such as damage or unclear text). On the other - hand, editors attempting to synthesize an ideal or original text from many witnesses may feel - little need to represent the material aspects of individual witnesses. Editors wishing to - distinguish witness readings from conjectures by modern editors may wish to use wit - to indicate the former and source for the latter. Differences in types of variation - might be marked using type or ana on the rdg element.

- -

Many examples given in this chapter refer to the following texts of the opening (usually just - line 1) of Chaucer's Wife of Bath's Prologue, as it appears in each of the four - different manuscripts - Ellesmere, Huntingdon Library 26.C.9 () - - Hengwrt, National Library of Wales, Aberystwyth, Peniarth 392D () - - British Library Lansdowne 851 () - - Bodleian Library Rawlinson Poetic 149 () - - -

- -
- The Apparatus Entry, Readings, and Witnesses -

This section introduces the fundamental markup methods used to encode textual variations: - - the app element for entries in the critical apparatus: see section . - elements for identifying individual readings: see section . - ways of grouping readings together: see section . - methods of identifying which witnesses support a particular reading, and for - describing the witnesses included in the apparatus: see section . - elements for indicating which portions of a text are covered by fragmentary witnesses: - see section . -

-

The app element is in one sense a more sophisticated and complex version of the - choice element introduced in as a way of marking points - where the encoding of a passage in a single source may be carried out in more than one way. - Unlike choice, however, the app element allows for the representation of - many different versions of the same passage taken from different sources.

- -
- The Apparatus Entry -

Individual textual variations are encoded using the app element, which groups - together all the readings constituting the variation. The identification of discrete textual - variations or apparatus entries is not a purely mechanical process; different editors will - group readings differently. No rules are given here as to how to collect readings into - apparatus entries.

-

The individual apparatus entry is encoded with the app element: - -

-

The attributes loc, from, and to, are used to link the - apparatus entry to the base text, if present. In such cases, several methods may be used for - such linkage, each involving a slightly different usage for these attributes. Linkage - between text and apparatus is described below in section . For the - use of the app element without a base text, see .

-

Each app element usually comprises one or more readings, which in turn are encoded using - the rdg or other elements, as described in the next section. A very simple partial - apparatus for the first line of the Wife of Bath's Prologue might take a form - something like this: - - Experience though noon Auctoritee - Experiment thouh noon Auctoritee - Eryment though none auctorite - - Of course, in practice the apparatus will be somewhat more complex. Specifically, it may be - desired to record more obviously that manuscripts El and La agree on the words noon - Auctoritee, to indicate a preference for one reading, etc. The following sections on - readings, subvariation, and witness information describe some of the more important - complications which can arise.

- -
-
- Readings -

Individual readings are the crucial elements in any critical apparatus of variants. The - following elements should be used to tag individual readings within an apparatus entry: - - - N.B. the term lemma is used here in the text-critical sense of - the reading accepted as that of the original or of the base text. This sense - differs from that in which the word is used elsewhere in the Guidelines, for example as in - the attribute lemma where the intended sense is the root form of an inflected - word, or the heading of an entry in a reference book, especially a dictionary. -

-

In recording readings within an apparatus entry, the rdg element should always be - used; each app usually contains at least one rdg, though it may contain only - notes.

-

The lem element may also be used to record the base text of the source edition, - to mark the readings of a base witness, to indicate the preference of an editor or encoder - for a particular reading, or (e.g. in the case of an external apparatus) to indicate - precisely to which portion of the main text the variation applies. Those who prefer to work - without the notion of a base text or who are not using the parallel segmentation method - may prefer not to use it at all. How it is used depends in part on the method chosen for - linking the apparatus to the text; for more information, see section .

-

Readings may be encoded individually, or grouped for clarity using the rdgGrp - element described in section .

-

As members of the attribute class att.textCritical, both of these elements - inherit the following attributes: . - rdg (but not rdgGrp) is also a member of att.witnessed: - These elements also inherit the following attributes from the - att.global.responsibility class: - - As elsewhere, these attributes may be used to indicate the person responsible - for the editorial decision being recorded, and also the degree of certainty associated with - that decision by the person carrying out the encoding.

-

The wit attribute identifies the witnesses which have the reading in question. - It is required if the apparatus gathers together readings from different witnesses, but may - be omitted in an apparatus recording the readings of only one witness, e.g. substitutions, - divergent opinions on what is in the witness or on how to expand abbreviations, etc. Even in - such a one-witness apparatus, however, the wit attribute may still be useful when - it is desired to record the occurrence of a particular reading in some other witness. For - other methods of identifying the witnesses to a reading, see section .

-

The type attribute allows the encoder to classify readings in any convenient - way, for example as substantive variants of the lemma: - - Experience - Experiment - Eryment - - or as orthographic variants: - - though - thouh -

-

The varSeq and cause attributes may be used to convey information on - the sequence and cause of variation. In the following apparatus fragment, the reading - Eryment is tagged as sequential to (derived from) the reading - Experiment, and the cause is given as loss of the abbreviation for - per. - - Experiment - Eryment -

-

If a manuscript is written in several hands, and it is desired to report which hand wrote a - particular reading, the hand attribute should be used. For example, in the Munich - manuscript containing the Carmina Burana, the word - alle has been changed to allen: Swaz hi gât umbe -daz sint alle megede, -die wellent ân man - - - alle - allen - -disen sumer gân. - - - -

-

Similarly, if a witness is hard to decipher, it may be desired to indicate responsibility - for the claim that a particular reading is supported by a particular witness. In line 2212a - of Beowulf, for example, the manuscript is read in different ways by - different scholars; the editor Klaeber prints one text, using parentheses to indicate his - expansion, and records in the apparatus two different accounts of the manuscript reading, by - Zupitza and Chambers:For the sake of legibility in the example, long - marks over vowels are omitted. - se ðe on - - hea(um) h(æþ)e - heaðo hlæwe - heaum hope - -hord beweotode, -

-

Because the hand attribute indicates a particular manuscript hand, it is intelligible - only on a reading from a single witness. If an encoder wishes to indicate that a particular - reading from a list in wit is in a particular hand, the witDetail element - should be used; see section .

-

Where there is a greater weight of editorial discussion and interpretation than can - conveniently be expressed through the attributes provided on these elements (for example - where the editor wishes to discuss how a section of text might be punctuated) this information - can be attached to the apparatus in a note.

-

The note element may also be used to record the specific wording of notes in the - apparatus of the source edition, as here in a transcription of Friedrich Klaeber's note on - Beowulf 2207a: syððan Beowulfe -Fol. 179a beowulfe. - Folio 179, with the last page (Fol. 198b), is the worst part of the - entire MS. It has been freshened up by a later hand, but not always - correctly. Information on doubtful readings is in the notes of - Zupitza and Chambers. -brade rice - - Notes providing details of - the reading of one particular witness should be encoded using the specialized - witDetail element described in section .

-

Encoders should be aware of the distinct fields of use of the attribute values - wit, hand, and source. Broadly, wit identifies - the physical entity in which the reading is found (manuscript, clay tablet, papyrus, printed - edition); hand refers to the agent responsible for inscribing that reading in - that physical entity (scribe, author, inscriber, hand 1, hand 2); source indicates - the scholar responsible for asserting the existence of that reading in that physical entity. - In some cases, the categories may blur: a scholar may produce an edition introducing - readings for which he or she is responsible; that edition may itself become a witness in a - later critical apparatus. Thus, readings introduced as corrections in the earlier edition - will be seen in the later apparatus as witnessed by the earlier edition. As observed in the - discussion concerning the discrimination of hand and resp in - transcription of primary sources in section , the division of layers of - responsibility through various scholars for particular aspects of a particular reading may - require the more complex mechanisms for assigning responsibility described in chapter .

- -
-
- Indicating Subvariation in Apparatus Entries -

The rdgGrp element may be used to group readings, either because they have - identical values on one or more attributes, or because they are seen as forming a - self-contained variant sequence, or for some other reason. This grouping of readings is - entirely optional: no such grouping of readings is required. - -

-

The rdgGrp element is a member of class att.textCritical and therefore can carry the type, - cause, varSeq, hand, and resp attributes - described in the preceding section. When values for any of these attributes are given on a - rdgGrp element, the values given are inherited by the rdg or - lem elements nested within the reading group, unless overridden by a new - specification on the individual reading element.

-

To indicate that both Hg and La vary only orthographically from the lemma, one might tag - both readings rdg type='orthographic', as shown in the preceding section. This - fact can be expressed more perspicuously, however, by grouping their readings into a - rdgGrp, thus: - - though - - thogh - thouh - -

-

Similarly, rdgGrp may be used to organize the substantive variants of an apparatus - entry. Editors may need to indicate that each of a group of witnesses may be taken as all - supporting a particular reading, even though there may be variation concerning the exact - form of that reading in, or the degree of support offered by, those witnesses. For example: - one may identify three substantive variants on the first word of Chaucer's Wife of - Bath's Prologue in the manuscripts: these might be expressed in regularized - spelling as Experience, Experiment, and - Eriment. In fact, the manuscripts display many different spellings - of these words, and a scholar may wish both to show that the manuscripts have all these - variant spellings and that these variant spellings actually support only the three - regularized spelling forms. One may term these variant spellings as - subvariants of the regularized spelling forms.

-

This subvariation can be expressed within an app element by gathering the readings - into three groups according to the normalized form of their reading. All the readings within - each group may be accounted subvariants of the main reading for the group, which may be - indicated by tagging it as a lem element or as rdg type='groupBase'.

-

In this example, the different subvariants on Experience, - Experiment, and Eriment are held within - three rdgGrp elements nested within the enclosing app element: - - - Experience - Experiens - - - Experiment - Eximent - - - Eriment - Eryment - - - From this, one may deduce that the regularized reading Experience is - supported by all three manuscripts El Hg Ha4, although the spelling differs in Ha4, and that - the regularized reading Eriment is supported by Ra2, even though the - form differs in that manuscript. Accordingly, an application which recognizes that these - apparatus entries show subvariation may then assign all the witnesses instanced as attesting - the sub-variants on that lemma as actually supporting the reading of the lemma itself at a - higher level of classification. Thus, Ha4 here supports the reading - Experience found in El and Hg, even though it is spelt slightly - differently in Ha4.

-

Reading groups may nest recursively, so that variants can be classified to any desired - depth. Because apparatus entries may also nest, the app element might also be used - to group readings in the same way. The example above is substantially identical to the - following, which uses app instead of rdgGrp: - - - - Experience - Experiens - - - - - Experiment - Eximent - - - - - Eriment - Eryment - - - - This expresses even more clearly than the previous encoding of this material that at the - highest level of classification (apparatus entry A1), this variation has three normalized - readings, and that the first of these is supported by manuscripts El, Hg, and Ha4; the - second by Cp, Ld1, and La; and the third by Ra2. Some encoders may find the use of nested - apparatus entries less intuitive than the use of reading groups, however, so both methods of - classifying the readings of a variation are allowed.

-

Reading groups may also be used to bring together variants which form an apparent - developmental sequence, and to make clear that other readings are not part of that sequence, - as in the following example, which makes clear that the variant sequence - experiment to eriment says nothing about the - relative priority of experiment and - experience: - - - Experience - Experiens - - - - Experiment - Eximent - - - Eriment - Eryment - - -

- -
-
- Witness Information -

A given reading is associated with the set of witnesses attesting it by listing the - witnesses in the wit attribute on the rdg or lem element. Special - mechanisms, described in the following sections, are needed to associate annotation on a reading - with one specific witness among several (section ), to transcribe - witness information verbatim from a source edition (section ), and to - identify the formal lists of witnesses typically provided in the front matter of critical - editions (section ).

-
- Witness Detail Information -

When it is desired to give additional information about the reading of a particular witness - or witnesses, such as noting that it appears in the margin or was corrected - for the reading, that information may be given in a witDetail element. This is a - specialized note, which can be linked to both a reading and to one or more of the - witnesses for that reading. The link to the reading may be inferred from witDetail's - position or made explicit by the target attribute which witDetail inherits - from the attribute class - att.pointing; the link to the witness, by the wit attribute. - - -

-

Because it annotates an attribute value, witDetail cannot be included in the text at the point of - attachment; without a target attribute, it refers to the closest preceding lem or rdg. - But if there is any ambiguity or if the witDetail refers to multiple readings, target must be - used to point to the reading(s) being annotated. To indicate that the - Ellesmere manuscript has an ornamental capital in the word - Experience, for example, one might write: - - Experience - Ornamental capital. - Experiens - - - This encoding makes clear that the ornamental capital mentioned is in the Ellesmere - manuscript, and not in Hengwrt or Ha4.

-

Like note, witDetail may be used to record the specific wording of - information in the source text, even when the information itself is captured in some more - formal way elsewhere. The example from the Carmina Burana above (section - ), for example, might be extended thus, to record the wording of - the note explaining that the variant reading adds n to the original - in a second hand: Swaz hi gât umbe -daz sint alle megede, -die wellent ân man - - - alle - allen - - n nachgetragen. - - -disen sumer gân. - - - -

-

Feature structures containing information about the text in a witness (whether retroversion, - regularization, or other) can also be linked to specific lem and rdg - instances. See chapter .

- -
-
- Witness Information in the Source -

Although witDetail provides a good way to annotate witness references in wit, lists - of sigla The Latin word siglum (sign), pl. - sigla denotes the abbreviation used in a critical apparatus to indicate a - particular witness. may be complex enough that it is impractical to use the combination of - wit and witDetail. - Moreover, in the transcription of printed critical editions, it may be desirable to retain for - future reference the exact form in which the source edition records the witnesses to a - particular reading; this is particularly important in cases of ambiguity in the - information, or uncertainty as to the correct interpretation. The wit element may - be used to transcribe such lists of witnesses to a particular reading. - - The wit list may appear following a rdg, rdgGrp, or - lem element in any apparatus entry. wit may be used in a way functionally equivalent - to wit if the sigla therein are wrapped in refs with target attributes - pointing to a predefined witness. For example - - Nondum - nundum - corr. G1 - - - which indicates that the reading nundum for nondum is to be found in MSS G (although it is - corrected to nondum in the primary hand) and P, might be written: - - Nondum - nundum - G(corr. G1)P - - - This is somewhat more verbose, but accomplishes the same goal. Because wit is more succinct, and because it makes - the automated verification of correct witness references easier, using wit (with witDetail when - needed) is almost always to be preferred. -

- -
-
- The Witness List -

A list of all identified witnesses should normally be supplied in the front matter of the - edition, or in the sourceDesc element of its header. This may be given either as - a simple bibliographic list, using the listBibl element described in - , or as a listWit element, which contains a series of - witness elements. Each witness element may contain a brief - characterization of the witness, given as one or more prose paragraphs. If more detailed - information about a manuscript witness is available, it should be represented using the - msDesc element provided by the msdescription - module; an msDesc may appear within a listBibl.

-

Whether information about a particular witness is supplied by means of a bibl, - msDesc, or witness element, a unique siglum for this source should - always be supplied, using the global xml:id attribute. This identifier can then - be used elsewhere to refer to this particular witness. - - - - - -

-

The minimal information provided by a witness list is thus the set of sigla for all the - witnesses named in the apparatus. For example, the witnesses referenced by the examples of - this chapter might simply be listed thus: - - - - - - - - - - - - - - - -

-

It is more helpful, however, for witness lists to be somewhat more informative: each - witness element should contain at least a brief prose description of the - witness, perhaps including a bibliographic citation, as in the following examples: - - Ellesmere, Huntingdon Library 26.C.9 - Hengwrt, National Library of Wales, - Aberystwyth, Peniarth 392D - Bodleian Library Rawlinson Poetic 149 -(see further ) - - As the last example shows, the witness description here may be complemented by a reference - to a full description of the manuscript supplied elsewhere, typically as the content of an - msDesc or bibl element. Alternatively, it may contain a whole - paragraph of commentary for each witness: - die sog. Kleine (oder alte) - Heidelberger Liederhandschrift. - Universitätsbibliothek Heidelberg col. pal. - germ. 357. Pergament, 45 Fll. 18,5 × 13,5 cm. - Wahrscheinlich die älteste der drei großen Hss. Sie - datiert aus dem 13. Jahrhundert, etwa um 1275. Ihre Sprache - weist ins Elsaß, evtl. nach Straßburg. Man geht wohl nicht - fehl, in ihr eine Sammlung aus dem Stadtpatriziat zu sehen - (Blank, [vgl. Lit. z. Hss. Bd. 2, - S. 39] S. 14). Sie enthält 34 namentlich - genannte Dichter. Zu den Vorzügen von A gehört, daß - sie kaum je bewußt geändert hat, so daß sie für - manche Dichter ... oft den besten Text liefert (so wohl mit - Recht v. Kraus). - Bezeichnung Lachmann - s für die von einer 2. Hand auf bl. 40–43 - geschriebenen Strophen der Hs. A. - die Weingartner (Stuttgarter) - Liederhandschrift. Württembergische - Landesbibliothek Stuttgart, HB XIII poetae germanici 1. - Pergament, 156 Bll. 15 × 11,5 cm; 25 teils ganzseitig, - teils halbseitige Miniaturen. Kaum vor 1306 in Konstanz - geschrieben. Sie enthält Lieder von 25 namentlich genannten - Dichtern. (Dazu kommen Gedichte von einigen ungenannten - bzw. unbekannten Dichtern, ein Marienlobpreis und eine - Minnelehre.) - - -

-

It would however generally be preferable to represent such detailed information using an - appropriately structured msDesc element, as discussed in chapter . Note also that if the witnesses being recorded are not manuscripts but - printed works, it may be preferable to document them using the standard bibl or - biblStruct elements described in , as in this example: - - -T. Kempis, De la imitació de Jesuchrist e del -menyspreu del món (trad. Miquel Peres); Barcelona, 1482, Pere -Posa. Editio princeps. -T. Kempis, Del menyspreu del món (trad. Miquel -Peres); València, 1491. -T. Kempis, Libre del menysprey del món e de la -imitació de nostre senyor Déu Jesucrist, (trad. Miquel Peres); -Barcelona, 1518, Carles Amorós. - - -

-

In text-critical work it is customary to refer to frequently occurring groups of - witnesses by means of a single common siglum. Such sigla may be documented as - pseudo-witnesses in their own right by including a nested witness list within the witness - list, which uses the siglum for the group as its identifier, and supplies a fuller name for - the group in its optional child head element, before listing the other witnesses - contained by the group. - For example, the Constant Group C of manuscripts comprising witnesses Cp, La, and S12, - might be represented as follows: - -Ellesmere, Huntingdon Library 26.C.9 - - - Constant Group C - Corpus Christi Oxford MS 198 - British Library Lansdowne 851 - British Library Sloane MS 1686 - - - That the reading Experiment occurs in all three manuscripts can now be - indicated simply as follows: Experiment

-

The more elaborate example below shows both multiple levels of nesting and a strategy for mapping - the the xml:id of the witness to the siglum which will be displayed to the reader of a derived visualisation: - Servius (Σ) = ΔΓ - - Δ - J = Metens. Bibl. mun. 292, s. IX - L = Leid. Bibl. der Rijksuniv. B.P.L. 52, s. VIII / IX - - Γ - θ - A = Caroliruh. Bad. Landesbibl. Aug. CXVI, s. IX2 (Reichenau); de codice A derivati: - - S = Sangall. Stiftsbibl. 861 + 862, s. IX / X - Guelf. = Guelf. HAB 2546 (44.23 Aug. fol.), s. XV - - - O = Oxon. Bodl. Laud lat. 117, s. XI2 - - τ - - Pa = Paris. BnF lat. 7959, s. IX (Tours) - Pc = Paris. BnF lat. 7961, s. X / XI - Q Flor. BML Plut. 45.14, s. IX - Lb = corrector cod. L (sup.) - - - γ - E = Escorial. Bibl. S. Lorenzo T.II.17, s. IX2 (Ital. septentrion.) - Pb Paris. BnF lat. 16236, s. X / XI - Y = Trident. Bib. com. 3388 (olim Vind. 72), s. - IX2 - M = Monac. Bay. Staatsbibl. Clm 6394, s. XI - - - σ - W = Guelf. HAB 2091, s. XIIIex. - N = Neap. Bibl. naz. lat. 5 (olim Vind. 27), s. - X1 - U = Berolin. Staatsbibl. lat. quart. 219, s. XII - - º classis codicum de Γ defluentium quibus lectiones faciliores in contextum contaminatione inferre valde placuit (= PaPcγσ in A. 9.1-10.190, 10.397-12.162; PaPcγU in A. 12.162-320; PaPcγ in A. 12.320-522); cf. praef. n. 30. - - - - Here we have a summary of the witnesses, with their sigla, used in an edition, as is generally - found in the conspectus siglorum in the front matter of a critical edition. - Families are indicated with Greek letters and manuscript witnesses with Latin letters. The siglum for - display is always contained in the abbr with type siglum child of each - witness, so it is always easy to retrieve the display siglum for a given identifier reference. -

- - -

Situations commonly arise where there are many more or less fragmentary witnesses, such - that there may be quite distinct groups of witnesses for different parts of a text or - collection of texts. One may treat this with distinct listWit elements for each - different part. Alternatively, one may have a single listWit element at the - beginning of the file or in its header listing all the witnesses, partial and complete, - for the text, with the attestation of fragmentary witnesses indicated within the apparatus - by use of the witStart and witEnd elements described in section .

-

If a witness list is provided, it may be unnecessary to give, in each apparatus entry, an - exhaustive list of the witnesses which agree with the base text. An application program - can—in principle—compare the witnesses given for each variant found with those given in - the full list of witnesses, subtracting from this list all the witnesses not active at - this point (perhaps because of lacuna, or because they contain a variation on a different, - overlapping lemma) and thence calculate all the manuscripts agreeing with the base text. - In practice, encoders may find it less error-prone to list all witnesses explicitly in - each apparatus entry.

- -
-
-
- Fragmentary Witnesses -

If a witness is incomplete (whether a single fragment, a series of fragments, or a - relatively complete text with one or more lacunae), it is usually desirable to record - explicitly where its preserved portions begin and end. The following empty tags, which may - occur within any lem or rdg element, indicate the beginning or end of a - fragmentary witness or of a lacuna within a witness: - - - - - These elements constitute the class model.rdgPart, - members of which are permitted within the elements lem and rdg when the - module defined by this chapter is included in a schema.

-

Suppose a fragment of a manuscript X of the Wife of Bath's Prologue has a - physical lacuna, and the text of the manuscript begins with - auctorite. In an apparatus this might appear thus, distinguished from - the reading of other manuscripts by the presence of the lacunaEnd element: - - Auctoritee - auctorite - auctorite - - Alternatively, it may be clearer to record this as - - Auctoritee - auctorite - - since this shows more clearly that the lacuna and the reading of auctorite both - appear in witness X. In some cases, the apparatus in the source may commence recording the - readings for a particular witness without its being clear whether the previous absence of - readings for this witness is due to a lacuna, or to some other reason. The witStart - element may be used in this circumstance: - - Auctoritee - auctorite - auctorite -

- - -
-
-
- Linking the Apparatus to the Text -

Three different methods may be used to link a critical apparatus to the text: - the location-referenced method, - the double-end-point-attached method, and - the parallel segmentation method. -

-

Both the location-referenced and the double end-point methods may be used with either - in-line or external apparatus, the former dispersed within the - base text, the latter held in some separate location, within or outside the document containing the - base text. The parallel segmentation method may only be used for in-line apparatus.

- - - -

Where an external apparatus is used, the listApp element - provides a useful means of grouping together a series of app elements of a specific type, - or from a particular source: - - - - - - listApp elements would normally appear in the back of - a document, but they may also be placed in any other convenient location.

- -

Any document containing app elements requires a variantEncoding declaration - in the encodingDesc element of its TEI header, thus: - -

- -
- The Location-referenced Method -

The location-referenced method of encoding apparatus provides a convenient method for - encoding printed apparatus; in this method as in most printed editions, the apparatus is - linked to the base text by indicating explicitly only the block of text on which there is a - variant (noted usually by a canonical reference scheme, or by line number in the edition, - such as A 137 or Page 15 line 1).

-

If the location-referenced method is used for an apparatus stored externally to the base - text, the TEI header must have the declaration: -

-

In the body of the document, the base text (here El) will appear: - - -

- The Prologe of the Wyves Tale of Bathe - Experience though noon Auctoritee - Were in this world ... -
- -

-

Elsewhere in the document, or in a separate file, the apparatus will appear. On each - app element, the loc attribute should be specified to indicate where - the variant occurs in the base text. - - Experiment - Eryment -

-

If the same text is encoded using in-line storage, the apparatus is dispersed through the - base text block to which it refers. In this case, the location of the variant can be read - from the line in which it occurs. - - -Experience - - Experiment - Eryment - - though noon Auctoritee -Were in this world ...

-

Since the location is not required to be exact, the apparatus for a line might also appear - at the end of the line: - Experience though noon Auctoritee - - Experiment - Eryment - -Were in this world ...

-

When the apparatus is linked to the text by means of location references, as shown here, it - is not possible to find automatically the precise portion of text varied by the readings. In - order to show explicitly what portion of the base text is replaced by the variant readings, - the lem element may be used: - Experience though noon Auctoritee - - Experience - Experiment - Eryment - -Were in this world ... - Often the lemma will have no attributes, being simply the base text - reading and requiring no qualification, but it may optionally carry the normal - attributes, as shown here. Some text critics prefer to abbreviate or elide the lemma, in - order to save space or trouble; such practice is not forbidden by these Guidelines, but no - recommendations are made for conventions of abbreviating the lemma, whether abbreviation of - each word, or suppression of all but the first and last word, etc.

-

Where it is intended that the apparatus be complete enough to allow the reconstruction of - the witnesses (or at least of their non-orthographic variations), simple location-reference - methods are unlikely to be as successful as the other two methods, which allow the - unambiguous reconstruction of the lemma from the encoding.

-
-
- The Double End-Point Attachment Method -

In the double end-point attachment method, the beginning and end of the lemma in the base - text are both explicitly indicated. It thus differs from the location-referenced method, in - which only the larger span of text containing the lemma is indicated. Double end-point - attachment permits unambiguous matching of each variant reading against its lemma. It or the - parallel-segmentation method should be used in all cases where this is desired, for example - where the apparatus is intended to enable full reconstruction of the text, or of the - substantives, of every witness.

-

When the double end-point attachment method is used, the from and to - attributes of the app element are used to indicate the beginning and ending points - of the reading in the base text: their values are identifiers which occur at the locations - in question. If no other markup is present there, the beginning and ending points should be - marked using the anchor element defined in chapter . In cases - where it is not possible to insert anchors within the base text (e.g. where the text is on a - read-only medium) the beginning and end of the lemma may be indicated by using the - indirect pointing mechanisms discussed in chapter . Explicit anchors are more likely to be reliable, and are therefore to be preferred.

-

The double end-point attachment method may be used with in-line or external apparatus. In - the latter case, the base text (here El) will appear with anchor elements inserted - at every place where a variant begins or ends (unless some element with an identifier - already begins or ends at that point): - - - -

The Prologe ... - Experience though noon Auctoritee - Were in this world ... -
- - The apparatus will be separately encoded: - - Experiment - Eryment - - No anchor element is needed at the beginning of the line, since the from - attribute can use the identifier for the line as a whole; the lemma is assumed to run from - the beginning of the element indicated by the from attribute, to the end of that - indicated by the to attribute. If no value is given for to, the lemma - runs from the beginning to the end of the element indicated by the from - attribute.

-

When the apparatus is encoded in-line, it is dispersed through the base text. Only the - beginning of the lemma need be marked with an anchor, since the app is - inserted at the end of the lemma, and itself therefore marks the end of the lemma. - - -Experience - - Experiment - Eryment - - though noon Auctoritee -Were in this world ...

-

The lemma need not be repeated within the app element in this method, as it may be - extracted reliably from the base text. If an exhaustive list of witnesses is available, it - will also not be necessary to specify just which manuscripts agree with the base text to - enable reconstruction of witnesses. An application will be able to determine the manuscripts - that witness the base reading, by noting which witnesses are attested as having a variant - reading, and inferring the base text reading for all others after adjusting for fragmentary - witnesses and for witnesses carrying overlapping variant readings.

-

Alternatively, if it is desired to make an explicit record of the attestation of the base - text, the lem element may be embedded within app, carrying the witnesses - to the base. Thus - - Experience - Experiment - Eryment -

-

This method is designed to cope with overlapping lemmata. For example, - at line 117 of the Wife of Bath's Prologue, the manuscripts Hg (Hengwrt), El (Ellesmere), - and Ha4 (British Library Harleian 7334) read: - - And of so parfit wys a wight ywroght - - And for what profit was a wight ywroght - - And in what wise was a wight ywroght -

-

In this case, one might wish to record in what wise was in Ha4 as a - single variant for of so parfit wys in Hg, and was a - wight in El and Ha4 as a variant on wys a wight in Hg. - This method can readily cope with such difficult situations, typically found in large and - complex traditions: - And - of so parfit - wys - a wight - ywroght - - of so parfit wys - in what wise was - - - wys a wight - was a wight - - The parallel segmentation method, to be discussed next, cannot handle overlaps among - variants, and would require the individual variants to be split into pieces.

-

Because creation and interpretation of double end-point attachment apparatus will be - lengthy and difficult it is likely that they will usually be created and examined by - scholars only with mechanical assistance.

-
-
- The Parallel Segmentation Method -

This method differs from the double end-point attachment method in that all variants at any - point of the text are expressed as variants on one another. In this method, no two - variations can overlap, although they may nest. The texts compared are divided into matching - segments all synchronized with one another. This permits direct comparison of any span of - text in any witness with that in any other witness. With a positive apparatus, it is - straightforward for an application to extract the full text of any one witness from the - apparatus.Some care must be taken with this approach, as a derived - view of a witness may not be a complete and accurate transcription of that witness. It is - more likely to be the base text with all readings from that witness applied.

-

This method will (by definition) always be satisfactory when there are just two texts for - comparison (assuming they are in the same language and script). It will however be less - convenient for textual traditions where establishing a base text with variations from - it is not a satisfactory goal for the edition, or in some cases where every detail of - variation needs to be modeled.

-

In the parallel segmentation method, each segment of text on which there is variation is - marked by an app element. If there is a preferred (or base) reading it is tagged - with lem; each reading is given in a rdg element: - - - Experience - Experiment - Eryment though noon Auctoritee - Were in this world ...

-

This method cannot be used with external apparatus: it must be used in-line. Note that - apparatus encoded with this method may be translated into the double end-point attachment - method and back without loss of information. Where double-end-point-attachment encodings - have no overlapping lemmata, translation of these to the parallel segmentation encoding and - back will also be possible without loss of information.

- -

As noted, apparatus entries may nest in this method: if an imaginary fifth manuscript of - the text read Auctoritee, though none experience, the variation on - the individual words of the line would nest within that for the line as a whole: - - Auctoritee, though none experience - - - Experience - Experiment - Eryment - - - though - thogh - thouh - - - noon Auctorite - none auctorite - - - -

-

Parallel segmentation cannot, however, deal very gracefully with variants which overlap - without nesting: such variants must be broken up into pieces in order to keep all witnesses - synchronized.

-
- - - -
- Other Linking Methods -

When an apparatus is provided it does not need to be given at the location in the - transcription where the variation, emendation, attribution, or other apparatus observation - occurs. Instead it may be stored in a separate place in the same file, or indeed in another - file, and point to the location at which it is meant to be used. Storing apparatus entries - separately can be beneficial when encoding multiple competing, potentially overlapping, - interpretations of the same point in the source texts.

-

The location-referenced method can be used to point a position in a text using the - loc attribute and a canonical reference that is understood and documented in - the context of the file where it is used. Where possible it is recommended that other - methods use the from attribute to point to an xml:id attribute on an - anchor or other element at the location where the apparatus observation takes - place. The contents of an element pointed to are understood to be equivalent to a - lem if none exists in the app, and if a lem does exist this - should replace any content.

-

The from attribute is a teidata.pointer datatype and - thus contains a URI as a value. This means that it can point directly to an - xml:id, an xml:id in another local file, or indeed a file identified - by any URL or URN. - - Experience though noon Auctoritee - - - - - Experiment - Eryment - - - This could also be encoded as: - - though noon Auctoritee - - - - - Experience - Experiment - Eryment - - - However, this should be considered more fragile since a full reading of the lem is - not provided in the source file.

-

In addition, URLs can contain XPointer schemes including xpath(), range(), and - string-range() which can be used in providing the location of an app that is stored - separately from the text to which it applies. Both from and to can be - used, as in the double end-point attachment method, to identify the starting and ending - location for an apparatus using XPointer schemes described in section - to more precisely identify this location where beneficial. - - Experience though noon Auctoritee - - - - - Experience - Experiment - Eryment - - -

-

If only the from attribute is provided then it should be understood that this - supplies the location of the textual variance that the apparatus documents. If the - from attribute contains an XPointer scheme that identifies a range of text (or - elements) then this is understood to record the starting and ending of the range as in the - double end-point attachment method. In such a case a @to attribute is unnecessary.

-
- -
- - - - -
- Using Apparatus Elements in Transcriptions -

It is often desirable to record different transcriptions of one stretch of text. These - variant transcriptions may be grouped within a single app element. An application may - then construct different views of the transcription by extraction of the - appropriate variant readings from the apparatus elements embedded in the transcription.

-

For example, alternative expansions can be recorded in several different expan - elements, all grouped within an app element. Consider, for example, the three - different transcriptions given below of line 105 of the Hengwrt manuscript of Chaucer's - The Wife of Bath's Prologue. The last word of the line Virginite - is grete perfection is written perfectio followed by two - minims over which a bar has been drawn, which has been read in different ways by different - scholars. The first transcription, by Elizabeth Solopova, represents the two minims with bar - above as a special composite character using the g element. This transcription notes - this as a mark of abbreviation but gives no expansion for it. A second transcriber, F. J. - Furnivall, regards the bar as an abbreviation of u, and therefore reads - the two minims as an n. A third transcriber, P. G. Ruggiers, regards - the bar as an abbreviation of n, reading the minims as - u. This information may be held within an app structure, as - follows: - Virginite is grete - - perfectio - perfectioun - perfectioun - - This example uses special purpose elements am and ex used to represent - abbreviation marks and editorial expansion respectively; these elements are provided by the - transcr module documented in chapter , which - should be consulted for further discussion of methods of representing multiple readings of a - source. -

-

Editorial notes may also be attached to app structures within transcriptions. Here, - editorial preference for Ruggiers' expansion and an explanation of that preference is given: - Virginite is grete - - perfecti - perfectioun - perfectioun - - -Furnivall's expansion implies that the bar - is an abbreviation for 'u'. There are no certain instances of - this mark as an abbreviation for 'u' in these manuscripts and it is - widely used as an abbreviation for 'n'. Ruggiers' expansion is to - be accepted. -

-

In most cases, elements used to indicate features of a primary textual source may be - represented within an app structure simply by nesting them within its readings, just - as the am and ex elements are nested within the rdg elements in the - example just given. However, in cases where the tagged feature extends across a span of text - which might itself contain variant readings which it is desired to represent by app - structures, some adaptation of the tagging may be necessary. For example, a span of text may - be marked in the transcription of the primary source as a single deletion but it may be - desirable to represent just a few words from this source as individual deletions within the - context of a critical apparatus drawing together readings from this and several other - witnesses. In this case, the tagging of the span of words as one deletion may need to be - decomposed into a series of one-word deletions for encoding within the apparatus. If it is - important to record the fact that all were deleted by the same act, the markup may use the - join element or the next and prev attributes defined by - chapter .

-
- -
- Strategies for Encoding Variation -

Textual variation may manifest itself in many ways. Variation most frequently occurs at the phrase level, - but is also common at higher structural levels, such as the verse line, paragraph, or chapter. When - these structures are involved, some care must be taken in their encoding to ensure that TEI's - Abstract Model is not being broken. It would be an error, for example, to have a div in - the lem, but a p in a rdg inside the same apparatus entry, because these - structures cannot occur at the same level. Similarly, it is an error if the contents of an - apparatus entry place a p inside another p or an l inside an l.

-

Phenomena such as omissions and transpositions in witnesses will require some encoding strategies - that differ from those in the examples above. An editor wishing to signal an omission in one witness - should encode the omission using an empty rdg, thus: - - Hypsipyle uacuo constitit in thalamo: - - - Notice that in this example, the variation occurs at the unit of the verse line. The scribe of MS J has - skipped line 18 (probably by mistake) because, like line 19, it begins with the name "Hypsipyle." If a witness - contains an interpolation that the editor does not wish to show in the base text, an empty - lem should be used, in the same fashion. -

-

Transpositions are harder to encode, because they involve variation that occurs in different - locations. A single app will therefore not be sufficient, and the variants must be linked. - For example, in his edition of Propertius 1.16, Housman printed lines 25-6 after line 32, Heyworth prints - them in place. We might encode Heyworth's edition, which records Housman's conjecture despite disagreeing - with it, as follows: - - - desine iam reuocare tuis periuria verbis, - Cynthia, et oblitos parce movere deos; - - and then, after line 32: - - - - - - Housman put these lines after 32. - - Note that both apps are linked via the exclude attribute, because they are mutually - exclusive: if one reading is chosen for display in a reading interface, for example, the other must - disappear and vice versa. To avoid repetition, the second pair of lines can make use of the copyOf - attribute. If they were both transposed and somewhat different, then both sets should be written in full. -

-

Apparatus entries may nest when there is variation at both higher and lower structural levels, e.g.: - - - utetac perhapsquam formosa nouo quae parat ire uiro. - atet non sic, Ithaci digressu motaimmota, Calypso - desertis olim fleuerat aequoribus: - multos illa dies incomptis maesta capillis - - omits lines 8-11 because of homoeoteleuton. - - Here, MS C omits lines 8-11, but there are variations the editor wishes to record in the other witnesses - which do have these lines. Therefore, an outer app gives the lines in the lem and the - omission in a rdg. Further variation is encoded for lines 8 and 9 using nested apps. -

-
- -
- Module for Critical Apparatus -

The module described in this chapter makes available the following components: - - Text Criticism - Critical Apparatus - Apparat critique - 學術編輯註解 - Apparato critico - Critical Apparatus - 校勘モジュール - - - The selection and combination of modules to form a TEI schema is - described in .

- - - - - - - - - - - - - - - -
- -
diff --git a/P5/Source/Guidelines/fr/TC-CriticalApparatus.xml b/P5/Source/Guidelines/fr/TC-CriticalApparatus.xml new file mode 120000 index 0000000000..2d8c114e35 --- /dev/null +++ b/P5/Source/Guidelines/fr/TC-CriticalApparatus.xml @@ -0,0 +1 @@ +../en/./TC-CriticalApparatus.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/TD-DocumentationElements.xml b/P5/Source/Guidelines/fr/TD-DocumentationElements.xml deleted file mode 100644 index 36910d7800..0000000000 --- a/P5/Source/Guidelines/fr/TD-DocumentationElements.xml +++ /dev/null @@ -1,2164 +0,0 @@ - - - - -
- Documentation Elements -

This chapter describes a module which may be used for the documentation of the XML elements and element - classes which make up any markup scheme, in particular that described by the TEI Guidelines, and also for - the automatic generation of schemas or DTDs conforming to that documentation. It should be used also by - those wishing to customize or modify these Guidelines in a conformant manner, as further described in - chapters and and may also be useful in the documentation of any - other comparable encoding scheme, even though it contains some aspects which are specific to the TEI and - may not be generally applicable.

-

An overview of the kind of processing environment envisaged for the module described by this chapter may - be helpful. In the remainder of this chapter we refer to software which provides such a processing - environment as an ODD processor.ODD is short for One Document Does it - all, and was the name invented by the original TEI Editors for the predecessor of the system - currently used for this purpose. See further and . Like any other piece of XML software, an ODD processor may be instantiated in many ways: the - current system uses a number of XSLT stylesheets which are freely available from the TEI, but this - specification makes no particular assumptions about the tools which will be used to provide an ODD - processing environment.

-

As the name suggests, an ODD processor uses a single XML document to generate multiple outputs. These - outputs will include: - formal reference documentation for elements, attributes, element classes, patterns, etc. such as - those provided in below; - detailed descriptive documentation, embedding some parts of the formal reference documentation, - such as the tag description lists provided in this and other chapters of these Guidelines; - declarative code for one or more XML schema languages, such as RELAX NG, W3C Schema, ISO - Schematron, or DTD. - - -

-

The input required to generate these outputs consists of running prose, and special purpose elements - documenting the components (elements, classes, etc.) which are to be declared in the chosen schema - language. All of this input is encoded in XML using elements defined in this chapter. In order to support - more than one schema language, these elements constitute a comparatively high-level model which can then - be mapped by an ODD processor to the specific constructs appropriate for the schema language in use. - Although some modern schema languages such as RELAX NG or W3C Schema natively support self-documentary - features of this kind, we have chosen to retain the ODD model, if only for reasons of compatibility with - earlier versions of these Guidelines. For reasons of backwards compatibility, the ISO standard XML schema - language RELAX NG () may be used as a means of declaring content - models and datatypes, but it is also possible to express content models using native TEI XML constructs. - We also use the ISO Schematron language to define additional constraints beyond those expressed in the - content model, as further discussed in below.

-

In the TEI system, a schema is built by combining element and attribute declarations, more - or less as required. Each element is documented by an appropriate specification element and - has an identifier unique across the whole TEI scheme. For convenience, these specifications are grouped - into a number of discrete modules, which can also be combined more or less as required. Each - major chapter of these Guidelines defines a distinct module. Each module declares a number of - elements specific to that module, and may also populate particular classes. - All classes are available globally, irrespective of the module in which they are declared; particular - modules extend the meaning of a class by adding elements or attributes to it. Wherever possible, element - content models are defined in terms of classes rather than in terms of specific elements. Modules can also - declare particular patterns, which act as short-cuts for commonly used content models or - class references.

-

In the present chapter, we discuss the components needed to support this system. In addition, section - discusses some general purpose elements which may be useful in any kind of - technical documentation, wherever there is need to talk about technical features of an XML encoding such - as element names and attributes. Section discusses the elements which are used - to document XML modules and their high-level components. Section - discusses the elements which document XML elements and their attributes, element classes, and generic - patterns or macros. Finally, section provides a summary overview of the elements - provided by this module.

-
- Phrase Level Documentary Elements -
- Phrase Level Terms -

In any kind of technical documentation, the following phrase-level elements may be found useful for - marking up strings of text which need to be distinguished from the running text because they come from - some formal language: - - - Like other phrase-level elements used to indicate the semantics of a typographically - distinct string, these are members of the model.emphLike class. They are - available anywhere that running prose is permitted when the module defined by this chapter is included - in a schema.

-

The code and ident elements are intended for use when citing brief passages in some - formal language such as a programming language, as in the following example: - -

If the variable z has a value of zero, a statement such as x=y/z will - usually cause a fatal error.

- -

-

If the cited phrase is a mathematical or chemical formula, the more specific formula element - defined by the figures module () may be more - appropriate.

-

A further group of similar phrase-level elements is also defined for the special case of representing - parts of an XML document: - - - - - These elements constitute the model.phrase.xml class, which is - also a subclass of model.phrase. They are also available anywhere that - running prose is permitted when the module defined by this chapter is included in a schema.

-

As an example of the recommended use of these elements, we quote from an imaginary TEI working paper: -

The gi element is used to tag element - names when they appear in the text; the tag element however is used to show how a tag as - such might appear. So one might talk of an occurrence of the blort element which had been - tagged blort type='runcible'. The type attribute may take any name token as - value; the default value is spqr, in memory of its creator.

-

-

Within technical documentation, it is also often necessary to provide more extended examples of usage - or to present passages of markup for discussion. The following special elements are provided for these - purposes: - - - -

-

Like the code element, the egXML element is used to mark strings of formal code, or - passages of XML markup. The eg element may be used to enclose any kind of example, which will - typically be rendered as a distinct block, possibly using particular formatting conventions, when the - document is processed. It is a specialized form of the more general q element provided by the - TEI core module. In documents containing examples of XML markup, the egXML element should be - used for preference, as further discussed below in , since the content of this - element can be checked for well-formedness.

-

These elements are added to the class model.egLike when this module is - included in a schema. That class is a part of the general model.inter - class, thus permitting eg or egXML elements to appear either within or between - paragraph-like elements.

-
-
- Element and Attribute Descriptions -

Within the body of a document using this module, the following elements may be used to reference - parts of the specification elements discussed in section , in particular - the brief prose descriptions these provide for elements and attributes. - - - -

-

TEI practice recommends that a specList listing the elements under discussion introduce each - subsection of a module's documentation. The source for the present section, for example, begins as - follows: - -

- Element and Attribute Descriptions -

Within the body of a document using this module, the … the brief prose descriptions these provide for elements and attributes. - - - -

-

TEI practice recommends that a specList listing the elements under …

- -
- -

-

When formatting the ptr element in this example, an ODD processor might simply generate the - section number and title of the section referred to, perhaps additionally inserting a link to the - section. In a similar way, when processing the specDesc elements, an ODD processor may - recover relevant details of the elements being specified (specList and specDesc in - this case) from their associated declaration elements: typically, the details recovered will include a - brief description of the element and its attributes. These, and other data, will be stored in a - specification element elsewhere within the current document, or they may be supplied by the ODD - processor in some other way, for example from a database. For this reason, the link to the required - specification element is always made using a TEI-defined key rather than an XML IDREF value. The ODD - processor uses this key as a means of accessing the specification element required. There is no - requirement that this be performed using the XML ID/IDREF mechanism, but there is an assumption that - the identifier be unique.

-

A specDesc generates in the documentation the identifier, and also the contents of the - desc child of whatever specification element is indicated by its key attribute, - as in the example above. Documentation for any attributes specified by the atts attribute - will also be generated as an associated attribute list.

- - - - - - - - - - - - -
-
-
- Modules and Schemas -

As mentioned above, the primary purpose of this module is to facilitate the documentation and creation - of an XML schema derived from the TEI Guidelines. The following elements are provided for this purpose: - - - - - - - - - A module is a convenient way of grouping together element and - other declarations, and of associating an externally-visible name with the resulting group. A - specification group performs essentially the same function, but the resulting group is - not accessible outside the scope of the ODD document in which it is defined, whereas a module can be - accessed by name from any TEI schema specification. Elements, and their attributes, element classes, and - patterns are all individually documented using further elements described in section below; part of that specification includes the name of the module to which the - component belongs.

-

An ODD processor generating XML DTD or schema fragments from a document marked up according to the - recommendations of this chapter will generate such fragments for each moduleSpec element found. - For example, the chapter documenting the TEI module for names and dates contains a module specification - like the following: - - - Names and Dates - Additional elements for names and dates - - - together with specifications for all the elements, classes, and patterns which make up that module, - expressed using elementSpec, classSpec, or macroSpec elements as appropriate. - (These elements are discussed in section below.) Each of those - specifications carries a module attribute, the value of which is namesdates. An - ODD processor encountering the moduleSpec element above can thus generate a schema fragment for - the TEI namesdates module that includes declarations for all the elements - (etc.) which reference it.

-

In most realistic applications, it will be desirable to combine more than one module together to form a - complete schema. A schema consists of references to one or more modules or specification - groups, and may also contain explicit declarations or redeclarations of elements (see further ). Any combination of modules can be used to create a schema The distinction between base and additional tagsets in earlier versions of the TEI scheme has not - been carried forward into P5. -

-

A schema can combine references to TEI modules with references to other (non-TEI) modules using - different namespaces, for example to include mathematical markup expressed using MathML in a TEI - document. By default, the effect of combining modules is to allow all of the components declared by the - constituent modules to coexist (where this is syntactically possible: where it is not—for example, - because of name clashes—a schema cannot be generated). It is also possible to over-ride declarations - contained by a module, as further discussed in section

-

It is often convenient to describe and operate on sets of declarations smaller than the whole, and to - document them in a specific order: such collections are called specGrps (specification - groups). Individual specGrp elements are identified using the global xml:id - attribute, and may then be referenced from any point in an ODD document using the specGrpRef - element. This is useful if, for example, it is desired to describe particular groups of elements in a - specific sequence. Note however that the order in which element declarations appear within the schema - code generated from an ODD file element is not in general affected by the order of declarations within a - specGrp.

-

An ODD processor will generate a piece of schema code corresponding with the declarations contained by - a specGrp element in the documentation being output, and a cross-reference to such a piece of - schema code when processing a specGrpRef. For example, if the input text reads -

This module contains three red elements: - - - - and two blue ones: - - -

- - then the output documentation will replace the two specGrp elements above with a - representation of the schema code declaring the elements beetroot, east, and rose and that declaring the elements sky and bayou respectively. Similarly, if the - input text contains elsewhere a passage such as -
- An overview of the imaginary module -

The imaginary module contains declarations for coloured things: - -

-
- then the specGrpRef elements may be replaced by an appropriate piece of reference text such as - The RED elements were declared in section 4.2 above, or even by a copy of the relevant - declarations. As stated above, the order of declarations within the imaginary module described above - will not be affected in any way. Indeed, it is possible that the imaginary module will contain - declarations not present in any specification group, or that the specification groups will refer to - elements that come from different modules. Specification groups are always local to the document in - which they are defined, and cannot be referenced externally (unlike modules).

- - - - - - - - - - - -
-
- Specification Elements -

The following elements are used to specify elements, classes, patterns, and datatypes: - - - - - -

-

Unlike most elements in the TEI scheme, each of these specification elements has a - fairly rigid internal structure consisting of a large number of child elements which are always - presented in the same - order. - Furthermore, since these elements all describe markup objects in broadly similar ways, they have several - child elements in common. In the remainder of this chapter, we discuss first the elements which are - common to all the specification elements, and then those which are specific to a particular type.

-

Specification elements may appear at any point in an ODD document, both between and within paragraphs - as well as inside a specGrp element, but the specification element for any particular component - may only appear once (except in the case where a modification is being defined; see further ). The order in which they appear will not affect the order in which they are - presented within any schema module generated from the document. In documentation mode, however, an ODD - processor will output the schema declarations corresponding with a specification element at the point in - the text where they are encountered, provided that they are contained by a specGrp element, - - as discussed in the previous section. An ODD processor will also associate all declarations found with - the nominated module, thus including them within the schema code generated for that module, and it will - also generate a full reference description for the object concerned in a catalogue of markup objects. - These latter two actions always occur irrespective of whether or not the declaration is included in a - specGrp.

- - - - - - -
-
- Common Elements -

This section discusses the child elements common to all of the specification elements; some of these - are defined in the core module (). These child elements are used to specify the - naming, description, exemplification, and classification of the specification elements.

-
- Description of Components -

- - - - - - - - -

-

The gloss element may be used to provide a brief explanation for the name of the object if - this is not self-explanatory. For example, the specification for the element ab used to mark - arbitrary blocks of text begins as follows: - - anonymous block - - - A gloss may also be supplied for an attribute name or an attribute value in similar - circumstances: - - - suspension - the abbreviation provides the first letter(s) of the word or phrase, omitting the - remainder. - - - contraction - the abbreviation omits some letter(s) in the middle. - - - -

-

Note that the gloss element is needed to explain the significance of the identifier for an - item only when this is not apparent, for example because it is abbreviated, as in the above example. - It should not be used to provide a full description of the intended meaning (this is the function of - the desc element), nor to comment on equivalent values in other schemes (this is the purpose - of the equiv element), nor to provide alternative versions of the ident attribute - value in other languages (this is the purpose of the altIdent element).

-

The contents of the desc element provide a brief characterization of the intended function - of the object being documented in a form that permits its quotation out of context, as in the - following example: - - - identifies a word or phrase as belonging to some - language other than that of the surrounding text. - - - By convention, a desc element begins with a verb such as contains, - indicates, specifies, etc. and contains a single - clause.

-

Both the gloss and desc elements (in - addition to exemplum, remarks, and - valDesc) are members of att.translatable, and thus carry the - versionDate attributre. Where specifications are - supplied in multiple languages, these elements may be repeated - as often as needed. Each such element should carry both an - xml:lang and a versionDate attribute to - indicate the language used and the date on which the - translated text was last checked against its source.

- -

The equiv element is used to document equivalencies between the concept represented by this - object and the same concept as described in other schemes or ontologies. The uri attribute - is used to supply a pointer to some location where such external concepts are defined. For example, to - indicate that the TEI death element corresponds to the concept defined by the CIDOC CRM - category E69, the declaration for the former might begin as follows: - - - - - - -

-

The equiv element may also be used to map newly-defined elements onto existing constructs in - the TEI, using the filter and name attributes to point to an implementation of - the mapping. This is useful when a TEI customization (see ) defines - shortcuts for convenience of data entry or markup readability. For example, - suppose that in some TEI customization an element bo has been defined - which is conceptually equivalent to the standard markup construct hi rend='bold'. The - following declarations would additionally indicate that instances of the bo element can be converted to canonical TEI by obtaining a filter from the URI specified, and - running the procedure with the name bold. The mimeType attribute specifies - the language (in this case XSL) in which the filter is written: - - - - bold - contains a sequence of characters rendered in a bold face. - - - -

-

The altIdent element is used to provide an alternative name for an object, for example using - a different natural language. Thus, the following might be used to indicate that the abbr - element should be identified using the German word Abkürzung: - - Abkürzung - - In the same way, the following specification for the graphic element indicates that the - attribute url may also be referred to using the alternate identifier href: - - - - href - - - - - -

-

By default, the altIdent of a component is identical to the value of its ident - attribute.

-

The remarks element contains any additional commentary about how the item concerned may be - used, details of implementation-related issues, suggestions for other ways of treating related - information etc., as in the following example: - - - -

This element is intended for use only where no other element is available to mark the phrase - or words concerned. The global xml:lang attribute should be used in preference to - this element where it is intended to mark the language of the whole of some text element.

-

The distinct element may be used to identify phrases belonging to sublanguages or - registers not generally regarded as true languages.

- - - -

-

A specification element will usually conclude with a list of references, each tagged using the - standard ptr element, and grouped together into a listRef element: in the case of - the foreign element discussed above, the list is as follows: - - - - - - where the value COHQF is the identifier of the section in these Guidelines where this - element is fully documented.

-
-
- Exemplification of Components -

- - - - - -

-

The exemplum element is used to combine a single illustrative example with an optional - paragraph of commentary following or preceding it. The illustrative example itself may be marked up - using either the eg or the egXML element.

-

The source attribute may be used on either element to indicate the source from which an - example is taken, typically by means of a pointer to an entry in an associated bibliography, as in the - following example: - -

L'element foreign s'applique également aux termes considerés étrangers.

- -

Pendant ce temps-là, dans le bureau du rez- de-chaussée, les secrétaires faisaient du - hulla-hoop.

- - -]]> -

-

When, as here, an example contains valid XML markup, the egXML element should be used. In - such a case, it will clearly be necessary to distinguish the markup within the example from the markup - of the document itself. In an XML environment, this is easily done by using a different name space for - the content of the egXML element. For example: - The term element may be used -to mark any technical term, thus: - - This recursion is - giving me a headache.

]]>

-

Alternatively, the XML tagging within an example may be escaped, either by using - entity references to represent the opening angle bracket, or by wrapping the whole example in a CDATA - marked section: The term element may be used -to mark any technical term, thus: - - This <term>recursion</term> is - giving me a headache.

]]> or, equivalently: - The term element may be used -to mark any technical term, thus: -recursion is - giving me a headache.]]]]>

]]> - However, escaping the markup in this way will make it impossible to validate, and should therefore - generally be avoided.

-

If the XML contained in an example is not well-formed then it must either be enclosed in a CDATA - marked section, or escaped as above: this applies whether the eg or - egXML is used. The valid attribute on egXML may be used to indicate the - XML validity of the example with respect to some schema, as being valid, invalid, or feasibly valid.

-

The egXML element should not be used to tag non-XML examples: the general purpose - eg or q elements should be used for such purposes.

-
-
- Classification of Components -

In the TEI scheme elements are assigned to one or more classes, which may themselves - have subclasses. The following elements are used to indicate class membership: - - - -

-

The classes element appears within either the elementSpec or classSpec - element. It specifies the classes of which the element or class concerned is a member by means of one - or more memberOf child elements. Each such element references a class by means of its - key attribute. Classes themselves are defined by the classSpec element described - in section below.

-

For example, to show that the element gi is a member of the class model.phrase.xml, the elementSpec which documents this element contains the - following classes element: - - - - -

- - - - - - - - - -
-
-
- Element Specifications -

The elementSpec element is used to document an element - type, together with its associated attributes. In addition to the - elements listed above, it may contain the following subcomponents: - - - - - - -

-

These subcomponents are discussed in the following sections.

-
- Defining Content Models -

As described in and , the content of the element being - defined — that is, what elements are allowed inside it, and in - what order they are permitted — is described by its - content model. The content model is defined by the - content child of elementSpec. There are three - distinctly different ways of specifying a content model: - - The content model can be described using TEI elements - defined by this chapter, as discussed in immediately below. Two such TEI elements - that may be used to define a content model are - dataRef and valList. But because these are - most often used to define attribute values, they are discussed - separately near the beginning and towards the end of , respectively. - Alternatively, and primarily for backwards - compatibility, the content model may be expressed using a - RELAX NG pattern. This is discussed in , below. - Lastly, content models may be expressed using a schema - language other than TEI or RELAX NG, but no further - recommendations on doing so are provided by these - Guidelines. -

-
- Defining Content Models: TEI -

In the simplest case, the content model of an element may - be expressed using a single empty element as the only - child of content. This describes the element being - defined as empty, meaning a valid instance of - said element can not have any content.It - would still be allowed to contain comments or processing - instructions, as these are not considered part of the content - model. - - - -

-

More commonly, one or more of the following elements are used - to define a content model: - - - - - - -

-

An elementRef provides the name of an element which - may appear at a certain point in a content model. An - anyElement also asserts that an element may appear at a - certain point in a content model, but rather than providing the - name of a particular element type that may appear, any element - regardless of its name may appear (and may have any attributes). - A classRef provides the name of a model class, members - of which may appear at a certain point in content model.The classRef element may be used to - refer to attribute classes, but this should not be done within a - content. A macroRef provides the name - of a predefined macro, the expansion of which is to be inserted - at a certain point in a content model.

-

These three elements are all members of an attribute class - which provides attributes that further modify their significance - as follows: - - - -

-

Additionally, two wrapper elements are provided to indicate - whether the components listed as their children form a sequence - or an alternation: - - - - - These two wrapper elements are also members of att.repeatable. References listed as - children of sequence must appear in the order and - cardinality specified. Only one of the references listed as - children of alternate may appear, although the - cardinality of the alternate itself applies. Thus the - following fanciful content model permits either any number of - ptr elements (except zero) or any number of - ref elements (except zero); at least one element must - be present, but having both a ptr and a ref would be - invalid. - - - - - - - - - However, the following content model permits any number of - either ptr or ref elements (except zero); one - element must be present, and having both ptr elements - and ref elements (even intermixed) would be valid. - - - - - - - - -

-

The sequence and alternate elements may be - used in combination with great expressive power. For example, in - the following example, which might be imagined as a clean - replacement for the content of the choice element, one - and only one of the element pairs sic and - corr, orig and reg, or - abbr and expan is allowed. - - - - - - - - - - - - - - - - - - - In the following example, which might be imagined as a clean - replacement for the content of the address element, the - encoder is given a choice of either: - - a single street followed by a single - placeName followed by a single postCode - followed by an optional country, or - 2, 3, or 4 - addrLine elements. - - - - - - - - - - - - - - -

-

In addition to expressing where certain elements, members of - a class of elements, or constructs matching a predefined macro - may occur inside an element, a content model may permit a string - of zero or more Unicode characters to occur at a certain point - in the content model. This is indicated by supplying the element - textNode within the content element. - - - - If nothing but a textNode element is present inside a - content element, valid instances of the element being - defined may contain a sequence of zero or more Unicode - characters, but may not contain any elements.This content model is not used very often in the - TEI scheme. Because only Unicode characters are permitted, there - is no way to record characters that are not (yet) represented in - Unicode. Thus in TEI instead of textNode we often use a - reference to macro.xtext which - permits both Unicode characters and the g - element.

-
-
- Defining Content Models: RELAX NG -

Element content models may also be defined using RELAX NG - patterns. Here is a very simple example - - - - - The element within whose specification element this - content element appears will have a content model which - is expressed in RELAX NG as text, using the RELAX - NG namespace. This model will be copied unchanged to the output - when RELAX NG schemas are being generated. When an XML DTD is - being generated, an equivalent declaration (in this case - (#PCDATA)) will be output.

-

Here is a more complex example: - - - - - - - - - - - - - This is the content model for the teiHeader element, expressed in the RELAX NG syntax, which - again is copied unchanged to the output during schema generation. The equivalent DTD notation - generated from this is (fileDesc, (%model.teiHeaderPart;)*, revisionDesc?).

-

The RELAX NG language does not formally distinguish element names, attribute names, class names, or - macro names: all names are patterns which are handled in the same way, as the above example shows. - Within the TEI scheme, however, different naming conventions are used to distinguish amongst the - objects being named. Unqualified names (fileDesc, revisionDesc) are always - element names. Names prefixed with model. or att. (e.g. model.teiHeaderPart and att.typed) are always class names. In - DTD language, classes are represented by parameter entities (%model.teiHeaderPart; in the - above example); see further .

-

The RELAX NG pattern names generated by an ODD processor by default include a special prefix, the - default value for which is set using the prefix attribute on schemaSpec. - The purpose of this is to ensure that the pattern name - generated is uniquely identified as belonging to a particular schema, and thus avoid name clashes. For - example, in a RELAX NG schema combining the TEI element ident with another element called - ident from some other vocabulary, the former will be defined by a pattern called - TEI_ident rather than simply ident. Most of the time, this behaviour is - entirely transparent to the user; the one occasion when it is not will be where a content model - (expressed using RELAX NG syntax) needs explicitly to reference either the TEI ident or the - other one. In such a situation, the autoPrefix attribute on content may be used. - For example, suppose that we wish to define a content model for term which permits either a - TEI ident or the ident defined by some other vocabulary. A suitable content model - would be generated from the following content element: - - - - - - -

-
-
-
- Additional Constraints -

In addition to the content element, a set of general constraintSpec elements can be - used to express rules about the validity of an element. Like some other specification elements, they - are identifiable (using the ident attribute) in order that a TEI customization may - override, delete, or change them individually. Each constraintSpec can be expressed in any - notation which is found useful; the notation used must be recorded using the scheme - attribute.

-

Schematron is an ISO standard (ISO/IEC 19757-3:2006) that defines a - simple XML vocabulary for an assertion language which provides a powerful way of - expressing constraints on the content of any XML document in addition to those provided by other - schema languages. Such constraints can be embedded within a TEI schema specification — including - a TEI customization specification — using the methods exemplified in this chapter.Indeed, these Guidelines themselves include many additional constraints - which are expressed in the ISO Schematron language using this mechanism. A conformant TEI document - should respect these constraints, although automatic validation of them may not be possible for all - processors. - An ODD processor will typically process any constraintSpec elements in a TEI - specification whose scheme attribute indicates that they are expressed in Schematron to - create an ISO Schematron schema which may be used to validate document instances. The ISO Schematron - schema may be a free-standing document, or may be embedded in the RELAX NG schema output of the ODD - processor.

-

Constraints are generally used to model local rules which may be outside the scope of the target - schema language. For example, in earlier versions of these Guidelines several constraints on the usage - of the attributes of the TEI element relation were expressed informally as follows: only - one of the attributes active and mutual may be supplied; the attribute - passive may be supplied only if the attribute active is supplied.. In the - current version of the Guidelines, constraint specifications expressed as Schematron rules have been - added, as follows: - - - - One of the - attributes 'name', 'ref' or 'key' must be supplied - - - - - Only one of the - attributes @active and @mutual may be supplied - - - - - the - attribute 'passive' may be supplied only if the attribute 'active' is supplied - - - -

-

The constraints in the preceding example all related to attributes in the empty namespace, and the - Schematron rules did not therefore need to define a TEI namespace prefix. The Schematron language ns element should be used to do this when a constraint needs to refer to a - TEI element, as in the following example, which models the constraint that a TEI div must - contain either no subdivisions or at least two of them: - - - - - - if it contains any subdivisions, a - division must contain at least two of them - - - - - Schematron rules are also useful where an application needs to enforce rules on attribute values, as - in the following examples which check that various types of title are provided: - - - - an introductory component - of the title is expected - - - - - a main title must be supplied - - - - -

-

As a further example, Schematron may be used to enforce rules applicable to a TEI document which is - going to be rendered into accessible HTML, for example to check that some sort of content is available - from which the alt attribute of an HTML img can be - created: - - - - - - - You should provide information in a figure from - which we can construct an alt attribute in HTML - - - - - - Schematron rules can also be used to enforce other HTML accessibility rules about tables; note here - the use of a report and an assertion within one pattern: - - - - - - - A <table> should have a caption, using a <head> - element - Do not use tables to lay out the document body - - - - - -

-

Constraints can be expressed using any convenient language. - The following example uses a pattern matching language called - SPITBOL to express the requirement that title and author should - be different. - - - (output = leq(title,author) "title and author cannot be the same") - - - Note that the value of scheme is - SPITBOL. In order to properly constrain and - document the values of scheme used in their - customization file, a project may wish to create a - customization that (among other things) adds and explains this - value for use in validating their customization file. Thus - using schemes other than those provided for by the TEI - (currently schematron and isoschematron) - may require somewhat more effort when creating a customization - file. Such private schemes will generally be even more - problematic on implementation of the constraints themselves, - as it may require siginficant programming work. The TEI only - provides this capability for the suggested values.

-
-
- Attribute List Specification -

The attList element is used to document information about a collection of attributes, either - within an elementSpec, or within a classSpec. An attribute list can be organized - either as a group of attribute definitions, all of which are understood to be available, or as a - choice of attribute definitions, of which only one is understood to be available. An attribute list - may thus contain nested attribute lists.

-

The attribute org is used to indicate whether its child attDef elements are all - to be made available, or whether only one of them may be used. For example, the attribute list for the - element moduleRef contains a nested attribute list to indicate that either the - include or the except attribute may be supplied, but not both: - - - - - - - - - - - - -

-

The attDef element is used to document a single attribute, using an appropriate selection - from the common elements already mentioned and the following : - - - - - - - - -

-

The attList within an elementSpec is used to specify only the attributes which are - specific to that particular element. Instances of the element may carry other attributes which are - declared by the classes of which the element is a member. These extra attributes, which are shared by - other elements, or by all elements, are specified by an attList contained within a - classSpec element, as described in section below.

-
- Datatypes -

The datatype (i.e. the kind of value) for an attribute may be specified using - the elements datatype and dataRef. A datatype may be defined in any of the - following three ways: - by reference to an existing TEI datatype definition, itself defined by a dataSpec; - by use of its name in XML Schema - Part 2: Datatypes Second Edition, the widely used - datatype library maintained by the W3C as part of - the definition of its schema language; - by referencing its URI within some other datatype library. - The TEI defines a number of datatypes, each with an identifier beginning - teidata., which are used in preference to the datatypes available natively from a - target schema such as RELAX NG or W3C Schema since the facilities provided by different schema - languages vary so widely. The TEI datatypes available are described in section above. Note that each is, of necessity, mapped eventually to an externally defined datatype such - as W3C Schema's text or name, possibly combined to give more - expressivity, or constrained to a particular defined usage.

-

It is possible to reference a W3C schema datatype directly using name. In this case, - the child dataFacet can be used instead of restriction to set W3C schema compliant - restrictions on the datatype. A dataFacet is particularly useful for restrictions that can be difficult to impose and to read as a - regular expression pattern. - - - - - Note that restrictions are either expressed with restriction or dataFacet, never both.

-

A datatype may be used to constrain the textual content of - an element, rather than the value of an attribute. But because - they are intended for use in defining ranges of attribute - values, datatypes may not contain elements or attributes.

-

The attributes minOccurs and - maxOccurs are available for the case where an - attribute may take more than one value of the type - specified. For example, the columns attribute of - the layout element can have one or two non-negative - integers as its value: - - - columns - specifies the number of columns per page - - - - -

If a single number is given, all pages referenced - have this number of columns. If two numbers are given, - the number of columns per page varies between the - values supplied. Where columns is omitted - the number is assumed to be 1.

- - - - indicating that the target attribute may take any number of values, each being of the - same datatype, namely the TEI data specification teidata.pointer. As is usual in XML, - multiple values for a single attribute are separated by one or more white space characters. Hence, - values such as #a #b #c or http://example.org - http://www.tei-c.org/index.xml may be supplied. - -

-
-
- Value Specification -

The valDesc element may be used to describe constraints on data content in an informal - way: for example - must point to another align - element logically preceding this one. - Values should be Library of Congress - subject headings. - A bookseller's surname, taken from the list - in Pollard and Redgrave -

-

Constraints expressed in this way are purely documentary; to enforce them, the - constraintSpec element described in section must be used. For - example, to specify that an imaginary attribute ageAtDeath must take - positive integer values less than 150, the datatype teidata.numeric - might be used in combination with a constraintSpec such as the following: - - - age in years at death - - - - age at death must be an integer less than 150 - - - - -

-

The elements altIdent, equiv, gloss and desc may all be used in - the same way as they are elsewhere to describe fully the meaning of a coded value, as in the - following example: - - - dou - - dubious - used when the application of this element is doubtful or uncertain - - -

-

Where all the possible values for an attribute can be enumerated, the datatype - teidata.enumerated should be used, together with a valList element - specifying the values and their significance, as in the following example: - - required - recommended - optional - - - Note the use of the gloss element here to explain the otherwise less than obvious meaning - of the codes used for these values. Since this value list specifies that it is of type - closed, only the values enumerated are legal, and an ODD processor will typically - enforce these constraints in the schema fragment generated.

-

The valList element can also be used to provide illustrative examples of the kinds of - values expected without listing all of them. In such cases the type attribute will have - the value open, as in the following example: - - characterizes the movement, for example as an - entrance or exit. - 예를 들어 입장 또는 퇴장과 같은, 이동의 특성을 기술한다. - - - - - - character is entering the stage. - 등장인물이 무대에 등장하고 있다. - - - character is exiting the stage. - 등장인물이 무대에서 퇴장하고 있다. - - - character moves on stage - 등장인물이 무대에서 이동한다. - - - - The datatype will be teidata.enumerated in either case.

-

The valList or dataRef elements may also be used (as a child of the - content element) to put constraints on the permitted content of an element, as noted at - . This use is not however supported by all schema languages, and is - therefore not recommended if support for non-RELAX NG systems is a consideration.

-
- - -
-
- Processing Models -

As far as possible, the TEI defines elements and their attributes in a way which is entirely - independent of their subsequent processing, since its intention is to maximize the reusability of - encoded documents and their use in multiple contexts. Nevertheless, it can be very useful to specify - one or more possible models for such processing, both to clarify the intentions of the encoder, and to - provide default behaviours for a software engineer to implement when documents conforming to a - particular TEI customization are processed. To that end, the following elements may be used to - document one or more processing models for a given element. - - - - -

-

One or more of these elements may appear directly within an element specification to define the - processing anticipated for that element, more specifically how it should be processed to produce the - kind of output indicated by the output attribute. Where multiple such elements appear - directly within an elementSpec, they are understood to document mutually exclusive processing - models, possibly for different outputs or applicable in different contexts. Alternatively, the - modelGrp element may be used to group alternative model elements intended for a - single kind of output. The modelSequence element is provided for the case where a sequence of - models is to be processed, functioning as a single unit.

-

A processing model suggests how a given element may be transformed to produce one or more outputs. - The model is expressed in terms of behaviours and parameters, using - high-level formatting concepts familiar to software engineers and web designers, such as - block or inline. As such, it has a different purpose from - existing TEI mechanisms for documenting the appearance of source materials, such as the global - attributes rend, rendition and style, described in sections and . It does not necessarily describe anything present in - the original source, nor does it necessarily represent its original structure or semantics. A - processing model is a template description, which may be used to simplify the task of producing or - customizing the stylesheets needed by a formatting engine or any other form of processor.

-
- The TEI processing model -

The model element is used to document the processing model intended for a particular - element in an abstract manner, independently of its implementation in whatever processing language - is chosen. This is achieved by means of the following attributes and elements: - - - The mandatory behaviour attribute defines in broad terms how an element - should be processed, for example as a block or as an inline element. The optional - predicate attribute may be used to specify a subset of contexts in which this model - should be applicable: for example, an element might be treated as a block element in some contexts, - but not in others. The output attribute supplies a name for the output for which this - model is intended, for example for screen display, for a printed reading copy, for a scholarly - publication, etc. The way in which an element should be rendered is declared independently of its - behaviour, using either the attribute useSourceRendition or the element - outputRendition. These Guidelines recommend that outputRendition be expressed - using the W3C Cascading Stylesheet Language (CSS), but other possibilities are not excluded. The - particular language used may be documented by means of the styleDefDecl element described - in . -

-
-
- Output Rendition -

Here is a simple example of a processing model which might be included in the specification for an - element such as hi or foreign. The intent is that these elements should be - presented inline using an italic font. - - - font-style: italic; - - - If the rendition element, or the attributes style, rend, or - rendition have already been used in the source document to indicate elements that were - originally rendered in italic, and we wish simply to follow this in our processing, then there is no - need to include an outputRendition element, and the attribute useSourceRendition - could be used as follows: - - - - Any rendition information present in the source document will be ignored unless the - useSourceRendition attribute has the value true. If that is the case, then - such information will be combined with any rendition information supplied by the - outputRendition element. For example, using CSS, an element which appears in the source - as follows - - this is in bold - - would appear in bold and italic if processed by the following model - - - font-style: italic; - - -

-
-
- CSS Class -

In a typical workflow processing TEI documents for display on the web, a system designer will often - wish to use an externally defined CSS stylesheet. The cssClass attribute simplifies the - task of maintaining compatibility amongst the possibly many applications using such a stylesheet and - also enables a TEI application to specify the names of classes to be used for particular processing - models. For example, supposing that the associated CSS stylesheet includes a CSS class called - labeled-list, the following processing model might be used to request it be used - for list elements containing a child label element: - - - - - - - -

-

In the following example, a table will be formatted using renditional information provided in the - source if that is available, or by an external stylesheet, using one of the CSS classes specified, - if it is not: - - - - - - - - -

-

As discussed further below, the input data available to a processing model is by default the - content of the element being processed, together with its child nodes.

- - - -
-
- Model Contexts and Outputs -

Sometimes different processing models are required for the same element in different contexts. For - example, we may wish to process the quote element as an inline italic element when it - appears inside a p element, but as an indented block when it appears elsewhere. To achieve - this, we need to change the specification for the quote element to include two - model elements as follows: - - - font-style: italic; - - - left-margin: 2em; - - - As noted above, these two models are mutually exclusive. The first processing model will be used - only for quote elements which match the XPath expression given as value for the - predicate attribute. All other element occurrences will use the second processing - model.

-

When, as here, multiple behaviours are required for the same element, it will often be the case - that the appropriate processing will depend on the context. It may however be the case that the - choice of an appropriate model will be made on the basis of the intended output. For example, we - might wish to define quite different behaviours when a document is to be displayed on a mobile - device and when it is to be displayed on a desktop screen. Different behaviours again might be - specified for a print version intended for the general reader, and for a print version aimed at the - technical specialist.

-

The modelGrp element can be used to group together all the processing models which have in - common a particular intended output, as in the following example: - - - - font-size: 7pt; - - - text-color: red; - - - - - font-size: 12pt; - - - text-align: center; - - - -

-
-
- Behaviours and their parameters -

In the examples above we have used without explanation or definition two simple - behaviours: inline and block, but many other behaviours - are possible. A list of recommended behaviour names forms part of the specification for the element - model. A processing model can specify any named behaviour, some of which have additional - parameters. The parameters of a behaviour resemble the - arguments of a function in many programming languages: they provide names which can be used to - distinguish particular parts of the input data available to the process used to implement the - behaviour in question.

-

The following elements are used to represent and to define parameters: - - - -

-

By default, a processor implementing the TEI processing model for a particular element has - available to it as input data the content of the element itself, and all of its children. One or - more param elements may be supplied within a model element to specify - parameters which modify this, either by selecting particular parts of the default - input data, or by selecting data which would not otherwise be available. In either case, the value - supplied for the parameter is given as an XPath expression, evaluated with respect to the element - node being processed. An arbitrary name (defined in the corresponding paramSpec) is also - supplied to a processor to identify each parameter.

-

For example, an element such as the TEI ref element will probably be associated with a - processing model which treats it as a hyperlink. But a hyperlink (in most implementations) often has - two associated pieces of information: the address indicated, and some textual content serving to - label the link . In HTML, the former is provided as value of the href - element, and the latter by the content of an a element. In the following - processing model we define a behaviour called link, which will use whatever is - indicated by the parameter called uri - - to provide the former, while the latter is provided by the content of the ref element itself: - - - - - - - - The value attribute of a param element supplies an XPath expression that - indicates where the required value may be found. The context for this XPath is the element which is - being processed; hence in this example, the uri parameter takes the value of the - target attribute on the ref element being processed. The content - parameter indicates that the content of that ref element should be provided as its value. (This parameter is not - strictly necessary, since by default the whole content of the element being processed is always available to a processor, but - supplying it in this way makes the procedure more explicit). -

-

All the parameters available for a given behaviour are defined as a part of the definition of the - behaviour itself, as further discussed in section below.

-

As a further example, the TEI choice element requires a different behaviour for which the - name alternate is proposed as in the following example: - - - - - - - - The processing model shown here will be selected for processing a choice element which has both sic and corr child elements. - The names default and alternate here are provided for convenience. - The default parameter provides the value of the child corr element, and the alternate - parameter will provide that of the child sic elements. If neither param element was supplied, both elements would - still be available to an application, but the application would need to distinguish them for itself. -

-

A choice element might contain multiple corrections, each with differing values for their - cert attribute. In the following processing model, we will accept as value of the default attribute only - those child corr elements which have a value high for that attribute: - - - - - - - -

-

A choice element might contain several different pairs of alternate elements (abbr - and expan, orig and reg, etc.) We might wish to group together a set of - processing models for these, for example to determine which of the possible alternatives is - displayed by default whenever a choice element is processed for output to the web: - - - - - - - - - - - - - - - - - -

-

If nothing matches the XPath defining the value of a particular parameter (e.g. if in the above - example there is no correction with cert=high) then the default - parameter has no value. It is left to implementors to determine how null-valued parameters should be - processed.

-
-
- Outputs -

As noted above, the output attribute is used to associate particular processing models - with a specific type of output. The following example documents a range of processing intentions for - the date element, intended to cope with at least the following three situations:

- - there is text inside the element, and the output is print; - there is no text inside the element but there is a when attribute, and the output - is print; - there is a when attribute, there is text inside the element, and the output is - web - - - - - - - - - - - - - - - -

For output to print we supply two processing models, one for the simplest case where the content of - the date is to be treated as an inline element, and the other for the case where there is - no content and the value of the when attribute is to be used in its place. This is - specified by a parameter, called content in this example. For output to web, we use - the alternate behaviour discussed in the previous section to indicate that by default - the content of the element will be used, while retaining access to the value of the when - attribute, this time via a parameter called alternate.

-
-
- Model sequence -

As well as being combined to form model groups, several models may be combined to form a - model sequence. All of the individual components of a model sequence are understood - to be applied, rather than considered to be mutually exclusive alternatives. For example, we might - wish to define two different behaviours for a note element: the inline behaviour should be - used to display the value of the note number (given by its n attribute), while a - different behaviour (here called footnote) should be used to display the content of - the element at a specified place, given by the parameter place. Because both of these - actions are required, the two models are grouped by a modelSequence element: - - - - - - - - - - - - -

-

The value of the parameter called place above is an XPath expression supplying an - arbitrary string (foot), which is therefore quoted. It is left to implementors to validate or - constrain the possible values for such expressions.

-
- -
- Defining a processing model -

The processing model for an element is defined using some combination of model, - modelSequence, or modelGrp elements within the elementSpec element containing its specification. - The processing to be carried out is defined by means of the behaviour specified for each - model element, possibly supplying specified values for a number of named parameters. The - parameters available for a given behaviour are specified using a number of param elements - grouped together in a paramList element. This paramList is supplied within the - valItem used to document and name the behaviour. Here for example is the valItem - which defines the link behaviour presented above: - - - create a hyperlink - - - supplies the location of some content describing the link - - - supplies the location of the intended hyperlink - - - - -

-

Similarly the valItem which defines the behaviour named alternate includes specifications for two - parameters: one also called alternate and the other called default - - - support display of alternative visualisations, for - example by displaying the preferred content, by displaying both in parallel, or by toggling - between the two. - - - supplies the location of the preferred - content - - - supplies the location of the alternative - content - - - - -

-

The suggested behaviours provided by the model element are informally defined using - commonly understood terminology, but specific details of how they should be implemented are left to - the implementor. Such decisions may vary greatly depending on the kind of processing environment, - the kind of output envisaged, etc. The intention is to reduce as far as possible any requirement for - the implementor to be aware of TEI-specific rules, and to maximize the ability of the ODD to express - processing intentions without fully specifying an implementation.

-
-
- Implementation of Processing Models -

As elsewhere in these Guidelines, the recommendations of this section are intended to be - implementation-agnostic, not favouring any particular implementation method or technology. An - implementor may choose, for example, whether to pre-process processing model specifications into a - free standing pipeline, or to extract and process them dynamically during - document processing. However, although implementors are generally free to interpret the processing - model documentation according to their own requirements, some general assumptions underlie the - recommendations made here: - If a model element has no child param elements, the action specified by - its behaviour should be applied to the whole element node concerned, including its child nodes - of whatever type. If that behaviour requires distinguishing particular parts of the input, an - implementation may choose either to make those distinctions itself, or to raise an error. - If a model element has no predicate or output attribute then - it is assumed to apply to all instances of the element defined in its parent - elementSpec for all outputs. Otherwise its applicability depends on these - attributes. - Only one of the models is to be applied for a particular instance of the element, except when they appear - within a modelSequence - - A matching model is one where the element to be processed satisfies the XPath in the - predicate attribute of the model or modelSequence and the current - output method matches the method specified in the output attribute of the model, - modelSequence, or a containing modelGrp. A model or modelSequence - without a predicate always matches the element to be processed. A model, - modelGrp, or modelSequence without an output attribute matches any output method. - Processing Model implementations must execute only the first matching model or - modelSequence in document order. - If there are two or more model elements provided for an elementSpec but - they have different output attributes then the implementation should choose the - model appropriate to the desired output. - If there are two or more model elements provided for an elementSpec but - they have different predicate attributes then the implementation should choose the - model whose predicate provides the most specific context (where - specific is understood in the same way as in XSLT) - - In the following example, which shows part of the element specification for the head - element, there are two model elements, one with and one without a predicate - attribute: - - - Model for list headings - - - - Default model for all headings. - - - - In this example, an implementation should use the first processing model only for head - elements with a list element as parent; for all other head elements, the second - processing model should be used.

- - - - - - - - - - - - -
-
-
-
- Class Specifications -

The element classSpec is used to document either an attribute class or a - model class, as defined in section . A corresponding - classRef element may be used to select a specific named class from those available. - - - - -

-

A model class specification does not list all of its members. Instead, its members declare that they - belong to it by means of a classes element contained within the relevant elementSpec. - This will contain a memberOf element for each class of which the relevant element is a member, - supplying the name of the relevant class. For example, the elementSpec for the element - hi contains the following: - - - - - This indicates that the hi element is a member of the class with identifier model.hiLike. The classSpec element that documents this class contains - the following declarations: - - groups phrase-level elements related to highlighting that have no specific semantics - - - - - - which indicate that the class model.hiLike is actually a member (or - subclass) of the class model.highlighted.

-

The function of a model class declaration is to provide another way of referring to a group of - elements. It does not confer any other properties on the elements which constitute its membership.

-

The attribute type is used to distinguish between model and - attribute classes. In the case of attribute classes, the attributes provided by - membership in the class are documented by an attList element contained within the - classSpec. In the case of model classes, no further information is needed to define the class - beyond its description, its identifier, and optionally any classes of which it is a member.

-

When a model class is referenced in the content model of an element (i.e. by means of a - classRef element within the content of an elementSpec), its meaning will - depend on the value of its expand attribute.

-

If this attribute is not specified, the classRef is interpreted to mean an alternated list of - all the current members of the class named. For example, suppose that the members of the class model.hiLike are elements hi, it, and bo. Then a content model such as - - - - would be equivalent to the explicit content model: - - - - - - - - (or, to use RELAX NG compact syntax, - ( hi | it | bo )). - However, a content model of <classRef - expand="sequence"/> would be equivalent to the - following explicit content model: - - - - - - - (or, in RELAX NG compact syntax, - ( hi, it, bo )).

- -

An attribute class (a classSpec of type - atts) contains an attList element which lists the attributes that all the members of - that class inherit from it. For example, the class att.interpLike defines a - small set of attributes common to all elements which are members of that class: those attributes are - listed by the attList element contained by the classSpec for att.interpLike. When processing the documentation elements for elements which are members of - that class, an ODD processor is required to extend the attList (or equivalent) for such - elements to include any attributes defined by the classSpec elements concerned. There is a - single global attribute class, att.global, to which some modules contribute - additional attributes when they are included in a schema.

- - - - - - - - - - - - - - - - - - - - - - -
-
- Macro Specifications -

The macroSpec element is used to declare and document predefined strings or patterns not - otherwise documented by the elements described in this section. A corresponding macroRef - element may be used to select a specific named pattern from those available. Patterns are used as a - shorthand chiefly to describe common content models and datatypes, but may be used for any purpose. The - following elements are used to represent patterns: - - - -

-
-
- Building a TEI Schema - -

The specification elements, and some of their children, are all members of the att.identified class, from which they inherit the following attributes: - - This attribute class is a subclass of the att.combinable class - from which it (and some other elements) inherits the following attribute: - - This attribute class, in turn, is a subclass of the att.deprecated class, from which it inherits the following attribute: - - The validUntil attribute may be used to signal an intent to remove a construct - from future versions of the schema being specified.

- - - -

The elementSpec, attDef and schemaSpec specification elements also have an - attribute which determines which namespace to which the object being created will belong. In the case of - schemaSpec, this namespace is inherited by all the elements created in the schema, unless - they have their own ns. - - -

- -

These attributes are used by an ODD processor to determine how declarations are to be combined to form - a schema or DTD, as further discussed in this section.

- -
- TEI customizations -

As noted above, a TEI schema is defined by a schemaSpec element containing an arbitrary - mixture of explicit declarations for objects (i.e. elements, classes, patterns, or macro - specifications) and references to other objects containing such declarations (i.e. references to - specification groups, or to modules). A major purpose of this mechanism is to simplify the process of - defining user customizations, by providing a formal method for the user to combine new declarations - with existing ones, or to modify particular parts of existing declarations.

-

In the simplest case, a user-defined schema might just combine all the declarations from two - nominated modules: - - - - - An ODD processor, given such a document, should combine the declarations which belong to the named - modules, and deliver the result as a schema of the requested type. It may also generate documentation - for the elements declared by those modules. No source is specified for the modules, and the schema - will therefore combine the declarations found in the most recent release version of the TEI Guidelines - known to the ODD processor in use.

-

The value specified for the source attribute, when it is supplied as a URL, specifies any - convenient location from which the relevant ODD files may be obtained. For the current release of the - TEI Guidelines, a URL in the form - http://www.tei-c.org/Vault/P5/x.y.z/xml/tei/odd/p5subset.xml may be used, where - x.y.z represents the P5 version number, e.g. 1.3.0. Alternatively, if the - ODD files are locally installed, it may be more convenient to supply a value such as - ../ODDs/p5subset.xml". -

-

The value for the source attribute may be any form of URI. A set of TEI-conformant - specifications in a form directly usable by an ODD processor must be available at the location - indicated. When no source value is supplied, an ODD processor may either raise an error or - assume that the location of the current release of the TEI Guidelines is intended.

-

If the source is specified in the form of a private URI, the form recommended is - aaa:x.y.z, where aaa is a prefix indicating the markup language in use, - and x.y.z indicates the version number. For example, tei:1.2.1 should be - used to reference release 1.2.1 of the current TEI Guidelines. When such a URI is used, it will - usually be necessary to translate it before such a file can be used in blind interchange.

-

The effect of a moduleRef element is to include in the schema all declarations provided by - that module. This may be modified by means of the attributes include and except - which allow the encoder to supply an explicit lists of elements from the stated module which are to be - included or excluded respectively. For example: - - - - - The schema specified here will include all the elements supplied by the core module except for - add, del, orig, and reg. It will also include only the - linkGrp and link elements from the linking module.

-

Alternatively, the element elementRef may be used to indicate explicitly which elements are - to be included in a schema. The same effect as the preceding example might thus be achieved by the - following: - - - - - - Note that in this last case, there is no need to specify the name of the module from which the two - element declarations are to be found; in the TEI scheme, element names are unique across all modules. - The module is simply a convenient way of grouping together a number of related declarations.

-

In the same way, a schema may select a subset of the attributes available in a specific class, - using the classRef element to point to an attribute class: - - - - - - - Here, only the corresp attribute is included; the other attributes in the class - are not available. The same effect can be achieved using except: - - - - - - -

-

A schema may also include declarations for new elements, as in the following example: - - - - - - - - A declaration for the element soundClip, which is not defined in the TEI - scheme, will be added to the output schema. This element will also be added to the existing TEI class - model.pPart.data, and will thus be available in TEI conformant - documents. Attributes from existing TEI classes could be added to the new element using attRef: - - - - - - - - - - - This will provide the source attribute from the att.global.source class on the new - soundClip element. -

-

A schema might also include re-declarations of existing elements, as in the following example: - - - - - - - - - The effect of this is to redefine the content model for the element head as plain text, by - over-riding the content child of the selected elementSpec. The attribute - specification mode="change" has the effect of over-riding only those children elements of - the elementSpec which appear both in the original specification and in the new specification - supplied above: content in this example. Note that if the value for mode were - replace, the effect would be to replace all children elements of the original - specification with the the children elements of the new specification, and thus (in this example) to - delete all of them except content.

-

A schema may not contain more than two declarations for any given component. The value of the - mode attribute is used to determine exactly how the second declaration (and its - constituents) should be combined with the first. The following table summarizes how a processor should - resolve duplicate declarations; the term identifiable refers to those elements which can - have a mode attribute: - - mode value - existing declaration - effect - - - add - no - add new declaration to schema; process its children in add mode - - - add - yes - raise error - - - replace - no - raise error - - - replace - yes - retain existing declaration; process new children in replace mode; ignore existing - children - - - change - no - raise error - - - change - yes - process identifiable children according to their modes; process unidentifiable children in - replace mode; retain existing children where no replacement or change is provided - - - delete - no - raise error - - - delete - yes - ignore existing declaration and its children - -
-

-
-
- Combining TEI and Non-TEI Modules -

In the simplest case, all that is needed to include a non-TEI module in a schema is to reference its - RELAX NG source using the url attribute on moduleRef. The following specification, - for example, creates a schema in which declarations from the non-TEI module svg11.rng (defining Standard Vector Graphics) are included. To avoid any risk of name - clashes, the schema specifies that all TEI patterns generated should be prefixed by the string "TEI_". - - - - - - - - -

-

This specification generates a single schema which might be used to validate either a TEI document - (with the root element TEI), or an SVG document (with a root element svg:svg), but - would not validate a TEI document containing svg:svg or other elements from the - SVG language. For that to be possible, the svg:svg element must become a member of a TEI - model class (), so that it may be referenced by other TEI elements. To achieve - this, we modify the last moduleRef in the above example as follows: - - - - - - - - - -

-

This states that when the declarations from the svg11.rng module are - combined with those from the other modules, the declaration for the model class model.graphicLike in the TEI module should be extended to include the element - svg:svg as an alternative. This has the effect that elements in the TEI scheme which define - their content model in terms of that element class (notably figure) can now include it. A - RELAX NG schema generated from such a specification can be used to validate documents in which the TEI - figure element contains any valid SVG representation of a graphic, embedded within an - svg:svg element.

- -
-
- Linking Schemas to XML Documents -

Schemas can be linked to XML documents by means of the ?xml-model? processing - instruction described in the W3C Working Group Note Associating Schemas with XML - documents (). ?xml-model? can be used for any type of schema, and may be used for multiple schemas: - -]]> - This example includes a standard RELAX NG schema, a Schematron schema which might be used for checking - that all pointing attributes point at existing targets, and also a link to the TEI ODD file from which - the RELAX NG schema was generated. See also for details of another method - of linking an ODD specification into your file by including a schemaSpec element in - encodingDesc.

-
-
-
- Module for Documentation Elements -

The module described in this chapter makes available the following components: - - Documentation Elements - Documentation of TEI and other XML markup languages - Éléments de déclaration d’un modèle - TEI模組說明 - Documentazione dei moduli TEI - Documentação dos módulos TEI - タグ定義モジュール - - The selection and combination of modules to form a TEI schema is - described in .

The elements described - in this chapter are all members of one of three classes: model.oddDecl, model.oddRef, or model.phrase.xml, with the exceptions of - schemaSpec (a member of model.divPart) and both eg and egXML - (members of model.common and model.egLike). All of these classes are - declared along with the other general TEI classes, in the basic - structure module documented in .

-

In addition, some elements are members of the att.identified class, which is documented in - above.

- - - - - - - -
-
diff --git a/P5/Source/Guidelines/fr/TD-DocumentationElements.xml b/P5/Source/Guidelines/fr/TD-DocumentationElements.xml new file mode 120000 index 0000000000..301d781642 --- /dev/null +++ b/P5/Source/Guidelines/fr/TD-DocumentationElements.xml @@ -0,0 +1 @@ +../en/./TD-DocumentationElements.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/TS-TranscriptionsofSpeech.xml b/P5/Source/Guidelines/fr/TS-TranscriptionsofSpeech.xml deleted file mode 100644 index 282af7921b..0000000000 --- a/P5/Source/Guidelines/fr/TS-TranscriptionsofSpeech.xml +++ /dev/null @@ -1,1470 +0,0 @@ - - - - -
-Transcriptions of Speech - -

The module described in this chapter is intended for use with a -wide variety of transcribed spoken material. It should be stressed, -however, that the present proposals are not intended to support -unmodified every variety of research undertaken upon spoken material -now or in the future; some discourse analysts, some phonologists, and -doubtless others may wish to extend the scheme presented here to -express more precisely the set of distinctions they wish to draw in -their transcriptions. Speech regarded as a purely acoustic phenomenon -may well require different methods from those outlined here, as may -speech regarded solely as a process of social interaction. -

-

This chapter begins with a discussion of some of the problems -commonly encountered in transcribing spoken language (section ). Section documents some -additional TEI header elements which may be used to document the -recording or other source from which transcribed text is taken. -Section describes the basic structural elements -provided by this module. Finally, section of this -chapter reviews further problems specific to the encoding of spoken -language, demonstrating how mechanisms and elements discussed -elsewhere in these Guidelines may be applied to them.

- - -
General Considerations and Overview -

There is great variation in the ways different researchers have -chosen to represent speech using the written medium.For a -discussion of several of these see ; ; and -. This -reflects the special difficulties which apply to the encoding or transcription of speech. Speech varies according to -a large number of dimensions, many of which have no counterpart in -writing (for example, tempo, loudness, pitch, etc.). The audibility of -speech recorded in natural communication situations is often less than -perfect, affecting the accuracy of the transcription. Spoken material -may be transcribed in the course of linguistic, acoustic, -anthropological, psychological, ethnographic, journalistic, or many -other types of research. Even in the same field, the interests and -theoretical perspectives of different transcribers may lead them to -prefer different levels of detail in the transcript and different styles -of visual display. The production and comprehension of speech are -intimately bound up with the situation in which speech occurs, far more -so than is the case for written texts. A speech transcript must -therefore include some contextual features; determining which are -relevant is not always simple. Moreover, the ethical problems in -recording and making public what was produced in a private setting and -intended for a limited audience are more frequently encountered in -dealing with spoken texts than with written ones. -

-

Speech also poses difficult structural problems. Unlike a written -text, a speech event takes place in time. Its beginning and end may be -hard to determine and its internal composition difficult to define. -Most researchers agree that the utterances or turns of -individual speakers form an important structural component in most kinds -of speech, but these are rarely as well-behaved (in the structural -sense) as paragraphs or other analogous units in written texts: -speakers frequently interrupt each other, use gestures as well as words, -leave remarks unfinished and so on. Speech itself, though it may be -represented as words, frequently contains items such as vocalized pauses -which, although only semi-lexical, have immense importance in the -analysis of spoken text. Even non-vocal elements such as gestures may -be regarded as forming a component of spoken text for some analytic -purposes. -Below the level of the individual utterance, speech may be segmented -into units defined by phonological, prosodic, or syntactic phenomena; -no clear agreement exists, however, even as to appropriate names for -such segments. -

- -

Spoken texts transcribed according to the guidelines presented here -are organized as follows. The overall structure of a TEI spoken text -is identical to that of any other TEI text: the TEI element -for a spoken text contains a teiHeader element, followed by a -text element. Even texts primarily composed of transcribed -speech may also include conventional front and back matter, and may -even be organized into divisions like printed texts.

-

We may say, therefore, that these Guidelines regard transcribed -speech as being composed of arbitrary high-level units called texts.textsas -organizing unit for spoken material A spoken -text might typically be a conversation between a small number -of people, a lecture, a broadcast TV item, or a similar event. Each -such unit has associated with it a teiHeader providing -detailed contextual information such as the source of the transcript, -the identity of the participants, whether the speech is scripted or -spontaneous, the physical and social setting in which the discourse -takes place and a range of other aspects. Details of the header -in general are provided in chapter ; the -particular elements it provides for use with spoken texts are -described below (). Details concerning -additional elements which may be used for the documentation of participant and -contextual information are given in . -

- -

Defining the bounds of a spoken text is frequently a matter of -arbitrary convention or convenience. In public or semi-public contexts, -a text may be regarded as synonymous with, for example, a lecture, a broadcast item, -a meeting, etc. In informal or private -contexts, a text may be simply a conversation involving a specific group -of participants. Alternatively, researchers may elect to define spoken -texts solely in terms of their duration in time or length in words. By -default, these Guidelines assume of a text only that: - -it is internally cohesive, -it is describable by a single header, and -it represents a single stretch of time with no significant -discontinuities. -

- -

Within a text it may be necessary to identify subdivisions -of various kinds, if only for convenience of handling. The neutral -div element discussed in section is -recommended for this purpose. It may be found useful also for -representing subdivisions relating to discourse structure, speech act -theory, transactional analysis, etc., provided only that these divisions -are hierarchically well-behaved. Where they are not, as is often the -case, the mechanisms discussed in chapters and - may be used. -

- -

A spoken text may contain any of the following components: - -utterances -pauses -vocalized but non-lexical phenomena such as coughs -kinesic (non-verbal, non-lexical) phenomena such as gestures -entirely non-linguistic incidents occurring during and possibly -influencing the course of speech -writing, regarded as a special class of incident in that it can -be transcribed, for example captions or overheads displayed during -a lecture -shifts or changes in vocal quality -

-

Elements to represent all of these features of spoken language are -discussed in section below. -

-

An utterance (tagged u) may contain lexical items -interspersed with pauses and non-lexical vocal sounds; during an -utterance, non-linguistic incidents may occur and written materials may be -presented. The u element can thus contain any of the other -elements listed, interspersed with a transcription of the lexical items -of the utterance; the other elements may all appear between utterances -or next to each other, but except for writing they do not -contain any other elements nor any data. -

- -

A spoken text itself may be without substructure, that is, it may -consist simply of units such as utterances or pauses, not grouped -together in any way, or it may be subdivided. If the notion of what -constitutes a text in spoken discourse is -inevitably rather an arbitrary one, the notion of formal subdivisions -within such a text may appear even more debatable. -Nevertheless, such divisions may be useful for such types of discourse -as debates, broadcasts, etc., where structural subdivisions can easily -be identified, or more generally wherever it is desired to aggregate -utterances or other parts of a transcript into units smaller than a -complete text. Examples might include -conversations or discourse fragments, or more narrowly, -that part of the conversation where topic x was discussed, -provided only that the set of all such divisions is coextensive with -the text. -

-

Each such division of a spoken text should be represented by the -numbered or unnumbered div elements defined in chapter . For some detailed kinds of analysis a hierarchy of -such divisions may be found useful; nested div elements may -be used for this purpose, as in the following example showing how a -collection made up of transcribed sound bites -taken from speeches given by a politician on different occasions -might be encoded. Each extract is regarded as a distinct -div, nested within a single composite div as -follows:

-
-
-
-
-
-
-
-

-

As a member of the class att.declaring, the -div element may also carry a decls attribute, for -use where the divisions of a text do not all share the same set of the -contextual declarations specified in the TEI header. (See further -section ). -

- -
- -
Documenting the Source of Transcribed Speech -

Where a computer file is derived from a spoken text rather than a -written one, it will usually be desirable to record additional -information about the recording or broadcast which constitutes its -source. Several additional elements are provided for this purpose -within the source description component of the TEI header: - - - - - - -As a member of the att.duration class, -the recording element inherits the following attribute: - - - -

-

Note that detailed information about the participants or setting of -an interview or other transcript of spoken language should be recorded -in the appropriate division of the profile description, discussed in -chapter , rather than as part of the source -description. The source description is used to hold information only -about the source from which the transcribed speech was taken, for -example, any script being read and any technical details of how the -recording was produced. If the source was a previously-created -transcript, it should be treated in the same way as any other source -text. -

-

The scriptStmt element should be used where it is known that -one or more of the participants in a spoken text is speaking from a -previously prepared script. The script itself should be documented in -the same way as any other written text, using one of the three citation -tags mentioned above. Utterances or groups of utterances may be linked -to the script concerned by means of the decls attribute, -described in section . - - - - CNN Network News - News headlines - 12 Jun 91 - - - -

-

The recordingStmt is used to group together information -relating to the recordings from which the spoken text was transcribed. -The element may contain either a prose description or, more helpfully, -one or more recording elements, each corresponding with a -particular recording. The linkage between utterances or groups of -utterances and the relevant recording statement is made by means of the -decls attribute, described in section . -

-

The recording element should be used to provide a -description of how and by whom a recording was made. This information -may be provided in the form of a prose description, within which such items as statements of -responsibility, names, places, and dates may be identified using the -appropriate phrase-level tags. Alternatively, a selection of elements -from the model.recordingPart class may be -provided. This element class makes available the following elements: - - - - - - - -

-

Specialized -collections may wish to add further sub-elements to these major -components. These elements should be used only for -information relating to the recording process itself; information about -the setting or participants (for example) is recorded elsewhere: see -sections and . - - -

U-matic recording made by college audio-visual department staff, - available as PAL-standard VHS transfer or sound-only cassette

- - - - - Location recording by - Sound Services Ltd. - - -

Multiple close microphones mixed down to stereo Digital - Audio Tape, standard play, 44.1 KHz sampling frequency

- - 12 Jan 1987 - - - - -14 Feb 2001 - - -17 Feb 2001 - - -22 Feb 2001 - - -

-

When a recording has been made from a public broadcast, details of -the broadcast itself should be supplied within the recording -element, as a nested broadcast element. A broadcast is closely -analogous to a publication and the broadcast element should -therefore contain one or the other of the bibliographic citation -elements bibl, biblStruct, or biblFull. The -broadcasting agency responsible for a broadcast is regarded as its -author, while other participants (for example interviewers, -interviewees, script writers, directors, producers, etc.) should be specified using the -respStmt or editor element with an appropriate -resp (see further section ). - -

Recorded from FM Radio to digital tape

- - - Interview on foreign policy BBC Radio 5 - interviewerRobin Day - intervieweeMargaret Thatcher - The World Tonight - First broadcast on 27 Nov 1989 - - -

-

When a broadcast contains several distinct recordings (for example a -compilation), additional recording elements may be further -nested within the broadcast element. - - - - - - - - -

-

The transcriptionDesc element can be used to document the particular transcription conventions (use of space, -punctuation, special characters etc.) used in making the transcription. A number of sets of such conventions have been defined -within particular research communities, or by users of particular transcription tools. The attributes ident -and version may be used to refer to such conventions in a machine tractable way, where this is appropriate. - - - - - -

- - - - - - - - - -
- -
Elements Unique to Spoken Texts -

The following elements characterize spoken texts, transcribed -according to these Guidelines: - -

-

The u element may appear directly within a spoken text, -and may contain any of the others; the others may also appear directly -(for example, a vocal may appear between two utterances) but cannot -contain a u element. In terms of the basic TEI model, -therefore, we regard the u element as analogous to a -paragraph, and the others as analogous to phrase -elements, but with the important difference that they can exist either -as siblings or as children of utterances. The class model.divPart.spoken provides the u -element; the class model.global.spoken -provides the six other elements listed above.

- -

As members of the att.ascribed class, -all of these elements share the following attributes: - -As members of the att.typed, att.timed and att.duration classes, -all of these elements except shift share the following attribute: - - - - - -

-

Each of these elements is further discussed and specified in -sections to . -

-

We can show the relationship between four of these constituents of -speech using the features eventive, communicative, anthropophonic (for sounds produced by the human -vocal apparatus), and lexical: - - eventivecommunicativeanthropophoniclexical -incident+--- -kinesic++-- -vocal+++- -utterance++++ -
-The differences are not always clear-cut. Among incidents might be included actions like slamming -the door, which can certainly be communicative. Vocals include coughing and sneezing, which -arevocal eventsin -transcription of speech usually -involuntary noises. Equally, the distinction between utterances and -vocals is not always clear, although for many analytic purposes it -will be convenient to regard them as distinct. Individual scholars -may differ in the way borderlines are drawn and should declare their -definitions in the editorialDecl element of the header (see -). -

-

The following short extract exemplifies several of these elements. It -is recoded from a text originally transcribed in the CHILDES -format.The original is a conversation between two children and -their parents, recorded in 1987, and discussed in - -Each utterance is encoded using a u element (see section ). The speakers are defined using the -listPerson element discussed in and each is -given a unique identifier also used to identify their speech. Pauses marked by the transcriber are indicated -using the pause element (see section ). -Non-verbal vocal effects such as the child's meowing are indicated -either with orthographic transcriptions or with the vocal -element, and entirely non-linguistic but significant incidents such as -the sound of the toy cat are represented by the incident -elements (see section ). - - - - - - - - -you -never take this cat for show and tell - meow meow -yeah well I dont want to -toy cat has bell in tail which continues to make a tinkling sound -meows -because it is so old -how boutabout - your cat yours is new - shows Father the cat -thats darling -no mine isnt old -mine is just um a little dirty - -

-

This example also uses some elements common to all TEI texts, -notably the reg tag for editorial regularization. Unusually -stressed syllables have been encoded with the emph -element. The seg element has also been used to segment the -last utterance. Further discussion of all of such options is provided -in section . -

-

Contextual information is of particular importance in spoken texts, -and should be provided by the TEI header of a text. In general, all of -the information in a header is understood to be relevant to the whole -of the associated text. The element u as a member of the -att.declaring class, may however specify a -different context by means of the decls attribute (see -further section ). -

-
Utterances -

Each distinct utterance in a spoken text is represented -by a u element, described as follows: - - -

-

Use of the who attribute to associate the utterance with a -particular speaker is recommended but not required. Its use implies as -a further requirement that all speakers be identified by a -person or personGrp element, typically in the TEI -header (see section ), but it may also point to another -external source of information about the speaker. Where utterances or -other parts of the transcription cannot be -attributed with confidence to any particular participant or group of -participants, the encoder may choose to create personGrp elements -with xml:id attributes such as various or unknown, -and perhaps give the root listPerson element an xml:id value of -all, then point to those as appropriate using who.

- -

The trans attribute is provided as a means of -characterizing the transition from one utterance to the next at a -simpler level of detail than that provided by the temporal alignment -mechanism discussed in section . The value specified -applies to the transition from the preceding utterance into the -utterance bearing the attribute. For example:For -the most part, the examples in this chapter use no sentence punctuation -except to mark the rising intonation often found in interrogative -statements; for further discussion, see section . -Have you heard the -the election results? yes -it's a disaster -it's a miracle -In this example, utterance ts_b1 latches on to utterance -ts_a1, while there is a marked pause between -ts_b1 and ts_a2. ts_b2 and -ts_a2 overlap, but by an unspecified amount. For ways of -providing a more precise indication of the degree of overlap, see -section . -

-

An utterance may contain either running text, or text within which -other basic structural elements are nested. Where such nesting occurs, -the who attribute is considered to be inherited for the -elements pause, vocal, shift, and -kinesic; that is, a pause or shift (etc.) within an utterance -is regarded as being produced by that speaker only, while a pause -between utterances applies to all speakers. -

-

Occasionally, an utterance may seem to contain other utterances, -for example where one speaker interrupts himself, or -when another speaker produces a back-channel -while they are still speaking. The present version of these -Guidelines does not support nesting of one u element within -another. The transcriber must therefore decide whether such -interruptions constitute a change of utterance, or whether other -elements may be used. In the case of self-interruption, the -shift element may be used to show that the speaker has -changed the quality of their speech: -Listen to this The government is -confident, he said, that the current economic problems will be -completely overcome by June what nonsense -Alternatively the incident element described in section might be used, without transcribing the read material: Listen to this -reads aloud from newspaper what -nonsense -

-

Often, back-channelling is only semi-lexicalized and may therefore be -represented using the vocal element: -So what could I have done tut-tutting about it anyway? -Where this is not possible, it is simplest to regard the back-channel -as a distinct utterance.

-
-
Pausing -

Speakers differ very much in their rhythm and in particular in the -amount of time they leave between words. The following element is -provided to mark occasions where the transcriber judges that -speech has been paused, irrespective of the actual amount of silence: - -A pause contained by an utterance applies to the speaker of that -utterance. A pause between utterances applies to all speakers. The -type attribute may be used to categorize the pause, for -example as short, medium, or long; alternatively the attribute -dur may be used to indicate its length more exactly, as in -the following example: -Okay U-mthe scene opens up - with um you see -a tree okay? - -If detailed synchronization of pausing with other vocal phenomena is -required, the alignment mechanism defined at section -and discussed informally below should be used. Note that the -trans attribute mentioned in the previous section may also be -used to characterize the degree of pausing between (but not within) -utterances. -

-
Vocal, Kinesic, Incident -

The presence of -non-transcribed semi-lexical or non-lexical phenomena either between or -within utterances may be indicated with the following three elements. - -

-

The who attribute should be used to specify the person or -group responsible for a vocal, kinesic, or incident which is contained -within an utterance, if this differs from that of the enclosing -utterance. The attribute must be supplied for a vocal, kinesic, or incident -which is not contained within an utterance. -

-

The iterated attribute may be used to indicate that the -vocal, kinesic, or incident is repeated, for example laughter as opposed to laugh. -These should both be distinguished from laughing, -where what is being encoded is a shift in voice quality. For this last -case, the shift element discussed in section should be used. -

-

A child desc element may be used to supply a conventional -representation for the phenomenon, for example: - -burp, click, cough, exhale, giggle, gulp, - inhale, laugh, sneeze, sniff, snort, sob, swallow, throat, yawn - -ah, aha, aw, eh, ehm, er, erm, hmm, huh, - mm, mmhm, oh, ooh, oops, phew, tsk, uh, uh-huh, uh-uh, um, urgh, - yup -Researchers may prefer to regard some semi-lexical phenomena as -words within the bounds of the u element. -See further the discussion at section below. As -for all basic categories, the definition should be made clear in the -encodingDesc element of the TEI header. -

-

Some typical examples follow: -This is just delicious -telephone rings -I'll get it -I used to cough smoke a lot -sniffsHe thinks he's tough -snorts - - - - - - - - - - -Note that Ann's snorting could equally well be encoded as follows: - - snorts - -

-

The extent to which encoding of incidents or kinesics is included in a -transcription will depend entirely on the purpose for which the -transcription was made. As elsewhere, this will depend on the -particular research agenda and the extent to which their presence is -felt to be significant for the interpretation of spoken interactions. -

-
Writing -

Written text may also be encountered when speech is transcribed, for -example in a television broadcast or cinema performance, or where one -participant shows written text to another. The writing element -may be used to distinguish such written elements from the spoken text in -which they are embedded. - - -For example, if speaker A in the breakfast table conversation in section - above had simply shown the newspaper passage to her -interlocutor instead of reading it, the interaction might have been -encoded as follows: -look at this - -Government claims economic problems -over by June what nonsense! -

-

If the source of the writing being displayed is known, -bibliographic information -about it may be stored in a listBibl within the -sourceDesc element of the TEI header, and then pointed to -using the source attribute. For example, in the following -imaginary example, a lecturer displays two different versions of the same -passage of text: - - - -Shakespeare First Folio text -Shakespeare Second Folio text - - - -[...] now compare the punctuation of lines 12 and 14 in these two -versions of page 42... -[...] -[...] - -

-
-
Temporal Information -

As noted above, utterances, vocals, pauses, kinesics, incidents, -and writing elements all inherit attributes providing information -about their position in time from the classes att.timed and att.duration. These attributes can be used to -link parts of the transcription very exactly with points on a -timeline, or simply to indicate their duration. Note that if -start and end point to when elements -whose temporal distance from each other is specified in a timeline, -then dur is ignored. -

-

The anchor element (see ) may be used as -an alternative means of aligning the start and end of timed elements, -and is required when the temporal alignment involves points within an -element. -

-

For further discussion of temporal alignment and synchronization -see below.

-
-
Shifts -

A common requirement in transcribing spoken language is to mark -positions at which a variety of prosodic features change. Many -paralinguistic features (pitch, prominence, loudness, etc.) characterize -stretches of speech which are not co-extensive with utterances or any of -the other units discussed so far. One simple method of encoding such -units is simply to mark their boundaries. An empty element called -shift is provided for this purpose. - -A shift element may appear within an utterance or a segment to -mark a significant change in the particular feature defined by its -attributes, which is then understood to apply to all subsequent -utterances for the same speaker, unless changed by a new shift for the -same feature in the same speaker. Intervening utterances by other -speakers do not normally carry the same feature. -For example: -Elizabeth -Yes -Come and try this - come on -In this example, the word Elizabeth is spoken loudly, the -words Yes and Come and try this with -normal volume, and the words come on very loudly. -

-

The values proposed here for the feature attribute are -based on those used by the Survey of English Usage (see further -Boase 1990); this list may be revised or supplemented using -the methods outlined in section .

-

The new attribute specifies the new state of the feature -following the shift. If this attribute has the special value normal, the -implication is that the feature concerned ceases to be remarkable at this point.

-

A list of suggested values for each of the features proposed follows: - -tempo - - -allegro (fast) - -very fast -accelerando (getting faster) -lento (slow) -very slow -rallentando (getting slower) -loud (for loudness): - -forte (loud) -very loud -crescendo (getting louder) -piano (soft) -very soft -diminuendo (getting softer) -pitch (for pitch range): - -high pitch-range -low pitch-range -wide pitch-range -narrow pitch-range -ascending -descending -monotonous -scandent, each succeeding syllable higher than - the last, generally ending in a falling tone -tension: - -slurred -lax, a little slurred -tense -very precise -staccato, every stressed syllable being doubly - stressed -legato, every syllable receiving more or less equal - stress -rhythm: - -beatable rhythm -arrhythmic, particularly halting -spiky rising, with markedly higher unstressed - syllables -spiky falling, with markedly lower unstressed - syllables -glissando rising, like spiky rising but the - unstressed syllables, usually several, also rise - in pitch relative to each other -glissando falling, like spiky falling but with the - unstressed syllables also falling in pitch relative - to each other -voice (for voice quality): - -whisper -breathy -husky -creaky -falsetto -resonant -unvoiced laugh or giggle -voiced laugh -tremulous -sobbing -yawning - sighing -

-

A full definition of the sense of the values provided for each -feature may be provided either in the encoding description section of the -text header (see section ) or as part of a TEI customization, - as described in section . - -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-
-
Elements Defined Elsewhere -

This section describes the following features characteristic of -spoken texts for which elements are defined elsewhere in these -Guidelines: - -segmentation below the utterance level -synchronization and overlap -regularization of orthography The elements -discussed here are not provided by the module for spoken texts. Some -of them are included in the core module and others are contained in -the modules for linking and for analysis respectively. The selection -of modules and their combination to define a TEI schema is discussed -in section . - - -

-
Segmentation -

For some analytic purposes it may be desirable to subdivide the -divisions of a spoken text into units smaller than the individual -utterance or turn. Segmentation may be performed for a number of -different purposes and in terms of a variety of speech phenomena. -Common examples include units defined both prosodically (by intonation, -pausing, etc.) and syntactically (clauses, phrases, etc.) The term -macrosyntagm has been used by a number of researchers to -define units peculiar to speech transcripts.The term was -apparently first proposed by , -where it is defined as follows: A text can be analysed as a sequence -of segments which are internally connected by a network of syntactic -relations and externally delimited by the absence of such relations with -respect to neighbouring segments. Such a segment is a syntactic unit -called a macrosyntagm (trans. S. Johansson).

-

These Guidelines propose that such analyses be performed in terms of -neutrally-named segments, represented by the seg -element, which is discussed more fully in section . -This element may take a type attribute to specify the kind of -segmentation applicable to a particular segment, if more than one is -possible in a text. A full definition of the segmentation scheme or -schemes used should be provided in the segmentation element of -the editorialDecl element in the TEI header (see ).

-

In the first example below, an utterance has been segmented according -to a notion of syntactic completeness not necessarily marked by the -speech, although in this case a pause has been recorded between the two -sentence-like units. In the second, the segments are defined -prosodically (an acute accent -has been used to mark the position immediately following the syllable -bearing the primary accent or stress), and may be thought of as -tone units. - - we went to the pub yesterday - - there was no one there - - - although its an old ide´a - it hasnt been on the mar´ket very long - - -In either case, the segmentation element in the header of the -text should specify the principles adopted to define the segments marked -in this way.

-

When utterances are segmented end-to-end in the same way as the -s-units in written texts, the s element discussed in chapter - may be used, either as an alternative or in addition to -the more general purpose seg element. The s element -is available without formality in all texts, but does not allow segments -to nest within each other. -

-

Where segments of different kinds are to be distinguished within the -same stretch of speech, the type attribute may be used, as in -the following example: - -I think -this chap was writing -and he said hello said -hello -and he said -I'm going to a gate - at twenty past seven -he said -ok -right away -and so on they went -and they were - writing there - - -In this example, recoded from a corpus of language-impaired speech -prepared by Fletcher and Garman, the speaker's utterance has been fully -segmented into clausal (type="C") -or minor (type="M") units.

- -

For some features, it may be -more appropriate or convenient to introduce a new element in a custom namespace: - - -and he said -I'm going to a -gate -at twenty past seven - - - -Here, ext:paraphasia has been used to define a particular -characteristic of this corpus for which no element exists in the TEI scheme. -See further chapter for a discussion of the way in -which this kind of user-defined extension of the TEI scheme may be -performed and chapter for the mechanisms on which it -depends.

-

This example also uses the core elements gap and -del to mark editorial decisions concerning matter completely -omitted from the transcript (because of inaudibility), and words which -have been transcribed but which the transcriber wishes to exclude from -the segment because they are repeated, respectively. See -section for a discussion of these and related -elements.

-

It is often the case that the desired segmentation does not respect -utterance boundaries; for example, syntactic units may cross utterance -boundaries. For a detailed discussion of this problem, and the various -methods proposed by these Guidelines for handling it, see chapter -. Methods discussed there include these: - -milestone tags may be used; -the special-purpose shift tag discussed -in section is an extension of this method -where several discontinuous segments are to be grouped -together to form a syntactic unit (e.g. a phrasal verb with interposed -complement), the join element may be used -

-
Synchronization and Overlap -

A major difference between spoken and written texts is the importance -of the temporal dimension to the former. As a very simple example, -consider the following, first as it might be represented in a -playscript: - Jane: Have you read Vanity Fair? -Stig: Yes -Lou: (nods vigorously) -To encode this, we first define the participants: - - - - - -Let us assume that Stig and Lou respond to Jane's question before she -has finished asking it—a fairly normal situation in spontaneous -speech. The simplest way of representing this overlap -would be to use the trans attribute previously discussed: -have you read Vanity Fair -yes - -However, this does not allow us to indicate either the extent to which -Stig's utterance is overlapped, nor does it show that there are in -fact three things which are synchronous: the end of Jane's utterance, -Stig's whole utterance, and Lou's kinesic. To overcome these problems, -more sophisticated techniques, employing the mechanisms for pointing and -alignment discussed in detail in section , are needed. -If the module for linking has been enabled (as described in -section above), one way to represent the simple -example above would be as follows: -have you read Vanity Fair -yes -nods head vertically

-

For a full discussion of this and related mechanisms, section should be consulted. The rest of the present -section, which should be read in conjunction with that more detailed -discussion, presents a number of ways in which these mechanisms may be -applied to the specific problem of representing temporal alignment, -synchrony, or overlap in transcribing spoken texts.

-

In the simple example above, the first utterance (that with -identifier utt1) contains an anchor element, the function of -which is simply to mark a point within it. The synch -attribute associated with this anchor point specifies the identifiers of -the other two elements which are to be synchronized with it: -specifically, the second utterance (utt2) and the kinesic (k1). Note that -one of these elements has content and the other is empty.

-

This example demonstrates only a way of indicating a point within one -utterance at which it can be synchronized with another utterance and a -kinesic. For more complex kinds of alignment, involving possibly -multiple synchronization points, an additional element is provided, -known as a timeline. This consists of a series of -when elements, each representing a point in time, and bearing -attributes which indicate its exact temporal position relative to other -elements in the same timeline, in addition to the sequencing implied by -its position within it.

-

For example: - - - - - - -This timeline represents four points in time, named TS-P1, TS-P2, TS-P6, and TS-P3 -(as with all attributes named xml:id in the TEI scheme, the -names must be unique within the document but have no other -significance). TS-P1 is located absolutely, at 12:20:01:01 BST. TS-P2 is 4.5 -seconds later than TS-P2 (i.e. at 12:20:46). TS-P6 is -at some unspecified time later than TS-P2 and previous to TS-P3 (this is -implied by its position within the timeline, as no attribute values have -been specified for it). The fourth point, TS-P3, is 1.5 seconds -later than TS-P6.

-

One or more such timelines may be specified within a spoken text, to -suit the encoder's convenience. If more than one is supplied, the -origin attribute may be used on each to specify which other -timeline element it follows. The unit attribute -indicates the units used for timings given on when elements -contained by the alignment map. Alternatively, to avoid the need to -specify times explicitly, the interval attribute may be used -to indicate that all the when elements in a time line are a -fixed distance apart.

-

Three methods are available for aligning points or elements within a -spoken text with the points in time defined by the timeline: - -The elements to be synchronized may specify the identifier -of a when element as the value of one of the start, -end, or synch attributes -The when -element may specify the identifiers of all the elements to be -synchronized with it using the synch attribute -A -free-standing link element may be used to associate the -when element and the elements synchronized with it by -specifying their identifiers as values for its target -attribute.

-

For example, using the timeline given above: This is my turn The start of utterance -TS-U1 is aligned with TS-P2 and its end with -TS-P3. The transition between the words -my and turn occurs at -point TS-P6A, which is synchronous with point -TS-P6 on the timeline.

-

The synchronization represented by the preceding examples could -equally well be represented as follows: - - - - - - -This is my turn -Here, the whole of the object with identifier ts-u1 (the -utterance) has been aligned with two different points, -ts-p2 and ts-p3. This is interpreted to mean -that the utterance spans at least those two points.

-

Finally, a linkGrp may be used as an alternative to the -synch attribute: - - - - - - - - - This is my turn - - - - - - -

-

As a further example of the three possibilities, consider the -following dialogue, represented first as it might appear in a -conventional playscript: -Tom: I used to smoke - - -Bob: (interrupting) You used to smoke? -Tom: (at the same time) a lot more than this. But I never - inhaled the smoke - -A commonly used convention might be to transcribe such a passage as -follows: - (1) I used to smoke [ a lot more than this ] -(2)                 [ you used to smoke ] -(1) but I never inhaled the smoke -Such conventions have the drawback that they are hard to generalize or -to extend beyond the very simple case presented here. Their reliance on -the accidentals of physical layout may also make them difficult to -transport and to process computationally. These Guidelines recommend -the following mechanisms to encode this.

-

Where the whole of one or another utterance is to be synchronized, -the start and end attributes may be used: -I used to smoke a lot more than this -but I never inhaled the smoke -You used to smoke -Note that the second utterance above could equally well be encoded as -follows with exactly the same effect: -You used to smoke

-

If synchronization with specific timing information is required, a -timeline must be included: - - - - -I used to smoke - a lot more than this - but I never inhaled the smoke - - You used to smoke - -(Note that If only the ordering or sequencing of utterances is needed, -then specific timing information shown here in unit, absolute -and interval does not need to be provided.) -

-

As above, since the whole of Bob's utterance is to be aligned, the -start and end attributes may be used as an -alternative to the second pair of anchor elements: -You used to smoke

-

An alternative approach is to mark the synchronization by pointing -from the timeline to the text: - - - - -I used to smoke - a lot more than this - but I never inhaled the smoke -You used to smoke -To avoid deciding whether to point from the timeline to the text or vice -versa, a linkGrp may be used: - - - - - - I used to smoke - a lot more than this - but I never inhaled the smoke - You used to smoke - - - - -

-

Note that in each case, although Bob's utterance follows Tom's -sequentially in the text, it is aligned temporally with its middle, -without any need to disrupt the normal syntax of the text.

-

As a final example, consider the following exchange, first as it -might be represented using a musical-score-like notation, in which -points of synchronization are represented by vertical alignment of the -text: - Stig: This is |my  |turn -Jane:         |Balderdash -Lou :         |No, |it's mine -All three speakers are simultaneous at the words my, -Balderdash, and No; speakers Stig and Lou are -simultaneous at the words turn and it's. -This could be encoded as follows, using pointers from the alignment map -into the text: - - - - - -this is my turn -balderdash - no it's mine -

-
Regularization of Word Forms -

When speech is transcribed using ordinary orthographic notation, as -is customary, some compromise must be made between the sounds produced -and conventional orthography. Particularly when dealing with informal, -dialectal, or other varieties of language, the transcriber will -frequently have to decide whether a particular sound is to be treated as -a distinct vocabulary item or not. For example, while in a given -project kinda may not be worth distinguishing as a -vocabulary item from kind of, isn't may -clearly be worth distinguishing from is not; for some -purposes, the regional variant isnae might also be worth -distinguishing in the same way.

-

One rule of thumb might be to allow such variation only where a -generally accepted orthographic form exists, for example, in published -dictionaries of the language register being encoded; this has the -disadvantage that such dictionaries may not exist. Another is to -maintain a controlled (but extensible) set of normalized forms for all -such words; this has the advantage of enforcing some degree of -consistency among different transcribers. Occasionally, as for example -when transcribing abbreviations or acronyms, it may be felt necessary to -depart from conventional spelling to distinguish between cases where the -abbreviation is spelled out letter by letter (e.g. B B C -or V A T) and where it is pronounced as a single word -(VAT or RADA). Similar considerations -might apply to pronunciation of foreign words -(e.g. Monsewer vs. Monsieur).

-

In general, use of punctuation, capitalization, etc., in spoken -transcripts should be carefully controlled. It is important to -distinguish the transcriber's intuition as to what the punctuation -should be from the marking of prosodic features such as pausing, -intonation, etc.

-

Whatever practice is adopted, it is essential that it be clearly and -fully documented in the editorial declarations section of the header. -It may also be found helpful to include normalized forms of -non-conventional spellings within the text, using the elements for -simple editorial changes described in section (see -further section ).

-
Prosody -

In the absence of conventional punctuation, the marking of prosodic -features assumes paramount importance, since these structure and -organize the spoken message. Indeed, such prosodic features as points -of primary or secondary stress may be represented by specialized -punctuation marks, or other characters such as those provided by the -Unicode Spacing Modifier Letters block. Pauses have already been dealt with in section -; while tone units (or intonational phrases) -can be indicated by the segmentation tag discussed in section -. The shift element discussed in section -may also be used to encode some prosodic features, for example where all -that is required is the ability to record shifts in voice quality.

- -

In a more detailed phonological transcript, it is common practice -to include a number of conventional signs to mark prosodic features of -the surrounding or (more usually) preceding speech. Such signs may be -used to record, for example, particular intonation patterns, -truncation, vowel quality (long or short) etc. These signs may be -preserved in a transcript either by using conventional punctuation or -by marking their presence by g -elements. Where a transcript -includes many phonetic or phonemic aspects, it will generally be -more convenient to use the appropriate Unicode characters (see -further chapters and ). For -representation of phonemic information, the use of the International -Phonetic Alphabet, which can be represented in Unicode characters, is -recommended.

-

In the following example, special characters have been defined as -follows within the encodingDesc of the TEI header - - low fall intonation - low rise intonation - fall rise intonation - rise fall intonation - lengthened syllable - shortened syllable - - -These declarations might additionally provide information about -how the characters concerned should be rendered, their equivalent -IPA form, etc. In the transcript itself references to them can then -be included as follows: - - - -

Customer WN

-

Assistant K

 - - -
- C is with a friend - - Excuse me You dont have some - aesthetic specially on early - aesthetics terminology - - No No I'm - afraid - - No Well thanks Oh - you couldnt can we kind of - I mean ask you to order it for us - - Yes if you know the title Yeah - - - - Yes thats fine. just as soon as it comes in we'll send - you a postcard -
-

-

This example, which is taken from a corpus of bookshop service -encounters, -also demonstrates the use of the unclear and gap -elements discussed in section . Where words are so -unclear that only their extent can be recorded, the empty gap -element may be used; where the encoder can identify the words but wishes -to record a degree of uncertainty about their accuracy, the -unclear element may be used. More flexible and detailed -methods of indicating uncertainty are discussed in chapter .

- - -

For more detailed work, involving a detailed phonological transcript -including representation of stress and pitch patterns, it is probably -best to maintain the prosodic description in parallel with the -conventional written transcript, rather than attempt to embed detailed -prosodic information within it. The two parallel streams may be aligned -with each other and with other streams, for example an acoustic -encoding, using the general alignment mechanisms discussed in section -.

- - -
-
Speech Management -

Phenomena of speech management include disfluencies such -as filled and unfilled pauses, interrupted or repeated words, -corrections, and reformulations as well as interactional devices asking -for or providing feedback. Depending on the importance attached to such -features, transcribers may choose to adopt conventionalized -representations for them (as discussed in section -above), or to transcribe them using IPA or some other transcription -system. To simplify analysis of the lexical features of a speech -transcript, it may be felt useful to tidy away many -of these disfluencies. Where this policy has been adopted, these -Guidelines recommend the use of the tags for simple editorial -intervention discussed in section , to make explicit -the extent of regularization or normalization performed by the -transcriber.

-

For example, false starts, repetition, and truncated words might all -be included within a transcript, but marked as editorially deleted, in -the following way: -ssee -you you you know -it's he's crazy

-

As previously noted, the gap element may be used to mark -points within a transcript where words have been omitted, for example -because they are inaudible, as in the following example in which 5 seconds of -speech is drowned out by an external event: -

-

The unclear element may be used to mark words which have -been included although the transcriber is unsure of their accuracy: -...and then marbled queen

-

Where a transcriber is believed to have incorrectly identified a -word, the elements corr or sic embedded within a -choice element may be used to indicate -both the original and a corrected form of it: - -SCSIskuzzy - -These elements are further discussed in section . -

-

Finally phenomena such as code-switching, where a -speaker switches from one language to another, may easily be -represented in a transcript by using the foreign element -provided by the core tagset: - -I proposed that wir können - vielleicht go to warsaw -and vienna - - - -

-
-
Analytic Coding -

The recommendations made here only concern the establishment of a -basic text. Where a more sophisticated analysis is needed, more -sophisticated methods of markup will also be appropriate, for example, -using stand-off markup to indicate multiple segmentation of the -stream of discourse, or complex alignment of several segments within it. -Where additional annotations (sometimes called -codes or tags) are used to -represent such features as linguistic word class (noun, verb, etc.), -type of speech act (imperative, concessive, etc.), or information status -(theme/rheme, given/new, active/semi-active/new), etc., a selection from -the general purpose analytic tools discussed in chapters , , and may be used to -advantage. -

-

The general-purpose annotationBlock element may be used to group together a transcription and multiple layers of annotation. It also serves -to divide a transcribed text up into meaningful analytic sections. - - - -

- -
-
- -
- Module for Transcribed Speech -

The module described in this chapter makes available the following components: - - Transcribed Speech - Transcribed Speech - Transcriptions de la parole - 轉錄的言詞 - Trascrizione del parlato - Transcrição do discurso - 発話モジュール - - The selection and combination of modules to form a TEI schema is - described in .

- - - - - -
-
diff --git a/P5/Source/Guidelines/fr/TS-TranscriptionsofSpeech.xml b/P5/Source/Guidelines/fr/TS-TranscriptionsofSpeech.xml new file mode 120000 index 0000000000..c2ac9637a1 --- /dev/null +++ b/P5/Source/Guidelines/fr/TS-TranscriptionsofSpeech.xml @@ -0,0 +1 @@ +../en/./TS-TranscriptionsofSpeech.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/TitlePageVerso.xml b/P5/Source/Guidelines/fr/TitlePageVerso.xml deleted file mode 100644 index 5d98709f3a..0000000000 --- a/P5/Source/Guidelines/fr/TitlePageVerso.xml +++ /dev/null @@ -1,22 +0,0 @@ - - - - - - - -
- Releases of the TEI Guidelines - - - 1990, C.M. Sperberg-McQueen and Lou Burnard - - 1992, C.M. Sperberg-McQueen and Lou Burnard - - 1994, C.M. Sperberg-McQueen and Lou Burnard - - 2001, Lou Burnard, Syd Bauman, and Steven DeRose - - 2007, Lou Burnard and Syd Bauman - -
diff --git a/P5/Source/Guidelines/fr/TitlePageVerso.xml b/P5/Source/Guidelines/fr/TitlePageVerso.xml new file mode 120000 index 0000000000..6cf093865c --- /dev/null +++ b/P5/Source/Guidelines/fr/TitlePageVerso.xml @@ -0,0 +1 @@ +../en/TitlePageVerso.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/USE.xml b/P5/Source/Guidelines/fr/USE.xml deleted file mode 100644 index 9ae95e93a7..0000000000 --- a/P5/Source/Guidelines/fr/USE.xml +++ /dev/null @@ -1,2315 +0,0 @@ - - - - -
- Using the TEI - - -

This section discusses some technical topics concerning the deployment of the TEI markup schema - documented elsewhere in these Guidelines. - - In section we discuss the scope and variety of the TEI customization - mechanisms. - In we define the notions of TEI Conformance and - TEI - Extension. Since the ODD markup description language defined in chapter is fundamental to the way conformance and customization are handled in the TEI - system, these two definitional sections are followed by a section () which - describes the intended behaviour of an ODD processor.

- - - -
- Serving TEI files with the TEI Media Type -

In February 2011, the media type application/tei+xml was registered with IANA - for markup languages defined in accordance with the Text Encoding and Interchange - guidelines (RFC 6129). We - recommend that any XML file whose root element is in the TEI namespace be served with the - media type application/tei+xml to enable and encourage automated recognition and - processing of TEI files by external applications.

-
- -
- Obtaining the TEI -

As discussed in chapter , all components of the TEI schema are generated - from a single set of TEI XML source files. Schemas can be generated in each of XML DTD - language, W3C schema language, and RELAX NG schema language. Documentation can be generated in - a variety of commonly-used document formats, including HTML, DOCX, or PDF. -

-

TEI components are freely available over the Internet and elsewhere. The canonical home for - the TEI source, the schema fragments generated from it, and example modifications, is the TEI - repository at ; versions are also available in - other formats, along with copies of these Guidelines and related materials, from the TEI web - site at .

- -
- - - -
- - Customization - -

These Guidelines provide an encoding schema suitable for encoding a very wide range of texts, - and capable of supporting a wide variety of applications. For this reason, the TEI schema - supports a variety of different approaches to solving similar problems, and also defines a - much richer set of elements than is likely to be necessary in any given project. Furthermore, - the TEI schema may be extended in well-defined and documented ways for texts that cannot be - conveniently or appropriately encoded using what is provided. For these reasons, it is almost - impossible to use the TEI schema without customizing it in some way.

- -

This section describes how the TEI encoding schema may be customized, and should be read in - conjunction with chapter , which describes how a specific application of - the TEI encoding schema should be documented. The documentation system described in that - chapter is, like the rest of the TEI schema, independent of any particular schema or document - type definition language.

- -

Formally speaking, these Guidelines provide both syntactic rules about how elements and - attributes may be used in valid documents and semantic recommendations about what - interpretation should be attached to a given syntactic construct. In this sense, they provide - both a document type definition and a document type declaration. - More exactly, we may distinguish between the TEI Abstract Model, which defines a - set of related concepts, and the TEI schema which defines a set of syntactic - rules and constraints. Many (though not all) of the semantic recommendations are provided - solely as informal descriptive prose, though some of them are also enforced by means of such - constructs as datatypes (see ), or by schema constraints expressed - using the Schematron language. Schematron constraints provide information about special kinds - of validation errors dependent on conditional relationships, such as the invalidity of an - attribute name or value on one element when another is present, or when, given a pair of - attributes such as minOccurs and maxOccurs, the minimum value exceeds - the maximum value. Schematron constraints also provide warnings when a particular element, - attribute, or combination is to be deprecated in future releases of the TEI scheme, to alert - users that the feature in question is no longer to be used after a certain date. Very rarely, - TEI Schematron constraints offer warnings that do not explicitly break with the TEI but - suggest a more efficient or less ambiguous encoding. - - Although the descriptions, validation errors, and warnings have been written with care, there - will inevitably be cases where the intention of the contributors has not been conveyed with - sufficient clarity to prevent users of these Guidelines from extending - them in the sense of attaching slightly variant semantics to them.

- -

Beyond this unintentional semantic extension, some of the elements described can - intentionally be used in a variety of ways; for example, the element note has an - attribute type which can take on arbitrary string values, depending on how it is - used in a document. A new type of note, therefore, requires no change in the existing - model. On the other hand, for many applications, it may be desirable to constrain the possible - values for the type attribute to a small set of possibilities. A schema modified in - this way would no longer necessarily regard as valid the same set of documents as the - corresponding unmodified TEI schema, but would remain faithful to the same conceptual - model.

- - -

This section explains how the TEI schema can be customized by suppressing elements, modifying - classes of elements, or adding elements. Documents which - validate against an application of the TEI schema which has been customized in this way may or - may not be considered TEI-conformant, as further discussed in section - .

- -

The TEI system is designed to support modification and customization in a documented way that - can be validated by an XML processor. This is achieved by writing a small TEI-conformant - document, known informally as an ODD (One Document Does it all), from which an appropriate - processor can generate both human-readable documentation, and a schema expressed in a language - such as RELAX NG or DTD. The mechanisms used to instantiate a TEI schema differ for different - schema languages, and are therefore not defined here. In XML DTDs, for example, extensive use - is made of parameter entities, while in RELAX NG schemas, extensive use is made of patterns. - In either case, the names of elements and, wherever possible, their attributes and content - models are defined indirectly. The syntax used to implement this indirection also varies with - the schema language used, but the underlying constructs in the TEI Abstract Model are given - the same names. - - This indirection makes it simpler to implement customization of the TEI system in an - accessible and human-readable way.

- -

As further discussed in section , the TEI encoding schema comprises a set - of class and macro declarations, and a number of modules. Each module is made up - of element and attribute declarations, and a schema is made by combining a particular set of - modules together. In the absence of any other kind of customization, when modules are combined - together: - all the elements defined by the module (and described in the corresponding section of - these Guidelines) are included in the schema; - each such element is identified by the canonical name given it in these - Guidelines; - the content model of each such element is as defined by these Guidelines; - the names, datatypes, and permitted values declared for each attribute associated with - each such element are as given in these Guidelines; - the elements comprising element classes and the meaning of macro declarations - expressed in terms of element classes is determined by the particular combination of - modules selected. - The TEI customization mechanisms allow the user to control this behaviour as follows: - - particular elements may be suppressed, removing them from any classes in which they - are members, and also from any generated schema; - new elements may be added to an existing class, thus making them available in macros - or content models defined in terms of those classes; - additional attributes, or attribute values, may be specified for an individual element - or for classes of elements; - within certain limits, attributes, or attribute values, may also be removed either - from an individual element or for classes of elements; - the characteristics inherited by one class from another class may be modified by - modifying its class membership: all members of the class then inherit the changed - characteristics; - the set of values legal for an attribute or attribute class may be constrained or - relaxed by supplying or modifying a value list, or by modifying its datatype. - within certain limits, the name (generic identifier) associated with an element may be - changed, without changing the semantic or syntactic properties of the element; - - The modification mechanisms presented in this section are quite general, and may be - used to make all the types of changes just listed.

- -

The recommended way of implementing and documenting all such modifications is by means of the - ODD system described in chapter ; in the remainder of this section we give - specific examples to illustrate how that system may be applied. An ODD processor, such as the - Roma application supported by the TEI, or any other comparable set of stylesheets will use the - declarations provided by an ODD to generate appropriate sets of declarations in a specific - schema language such as RELAX NG or the XML DTD language. We do not discuss in detail here how - this should be done, since the details are schema language-specific; some background - information about the methods used for XML DTD and RELAX NG schema generation is however - provided in section . Several example ODD files are also provided as part - of the standard TEI release: see further section below.

- -
- Kinds of Modification -

For ease of discussion, we distinguish the following different kinds of modification: - deletion of elements; - modification of content models; - modification of attribute and attribute-value lists; - modification of class membership; - addition of new elements. - renaming of elements; - - Each of these is described in the following sections.

- -

Each kind of modification changes the set of documents that will be considered valid - according to the resulting schema. A schema derived from any combination of unmodified TEI - declarations (an "unmodified schema") may be thought of as defining a certain set of - documents. A schema deriving from a combination of modified TEI declarations (a "modified - schema") will define a different set of documents. The set of documents valid according to - the modified schema may or may not be properly contained by the set of documents considered - to be valid according to the unmodified schema. The schema TEI-All is the - special case of the unmodified schema which includes all currently available TEI modules. We - use the term clean modification for cases where the set of documents defined by a - modified schema is a proper subset of the set of documents defined by TEI-All. Where this is - not the case, that is, where the modified schema considers valid some documents which - TEI-All does not, we use the term unclean modification. Despite this - terminology, unclean modifications are not particularly deprecated, and their use may often - be vital to the success of a project. The concept is introduced solely to distinguish the - effects of different kinds of modification.

- - - -
- Deletion of Elements - -

The simplest way to modify the supplied modules is to suppress one or more of the - supplied elements. This is simply done by setting the mode attribute to - delete on an elementSpec for the element concerned.

- -

For example, if the note element is not to be used in a particular application, - but has been included via one of the supplied modules, then the schema specification - concerned will contain a declaration like the following: The ident attribute here supplies the - canonical name of the element to be deleted and the mode attribute specifies - what is to be done with it. There is no need to specify the module concerned, since - element names are unique across all TEI modules. The full specification for a schema in - which this modification is applied would thus be something like the following: - - - - -

- -

In most cases, deletion is a clean modification, since most elements are optional. - Documents that are valid with respect to the modified schema are also valid according to - TEI-All. To say this another way, the set of documents matching the new schema is - contained by the set of documents matching the original schema.

- -

There are however some elements in the TEI schema which have mandatory children; for - example, the element listPerson must contain at least one element from the - model.personLike class. If that class has no members because all of its - member elements have been removed, then the content model cannot be satisfied. A - modification which keeps listPerson but removes all of its possible children - would therefore be regarded as unclean. So long as at least one member of the class - remains available, however, deleting other members would not have this effect, and would - therefore be regarded as a clean modification.

- -

In general, whenever the element deleted by a modification is mandatory within the - content model of some other (undeleted) element, the result is an unclean modification, - and may also break the TEI Abstract Model (). However, the parent of - a mandatory child can be safely removed if it is itself optional.

- -

To determine whether or not an element is mandatory in a given context, the user must - inspect the content model of the element concerned. In most cases, content models are - expressed in terms of model classes rather than elements; hence, removing an element will - generally be a clean modification, since there will generally be other members of the - class available. If a class is completely depopulated by a modification, then the - cleanliness of the modification will depend upon whether or not the class reference is - mandatory or optional, in the same way as for an individual element.

- -
- - -
- Modification of Content Models - -

The content model for an element in the TEI schema is defined by means of a - content element within the elementSpec which specifies it. For - example, the specification for the element term provided by these Guidelines - contains a content element like the following: - - - - This content model consists of a reference to a macro called macro.phraseSeq. Further examination shows that this macro in turn expands to - an optional repeatable alternation of text (textNode) with references to three - other classes (model.gLike, model.phrase, or model.global). For some particular - application it might be preferable to insist that term elements should only - contain plain text, excluding these other possibilities.Excluding - model.gLike is generally inadvisable however, since - without it the resulting schema has no way of referencing non-Unicode characters. - This could be achieved simply by supplying a specification for term like the - following: - - - - -

- -

This is a clean modification which does not change the meaning of a TEI element; there is - therefore no need to assign the element to some other namespace than that of the TEI, - though it may be considered good practice; see further below.

-

A change of this kind, which simplifies the possible content of an element by reducing - its model to one of its existing components, is always clean, because the set of documents - matched by the resulting schema is a subset of the set of documents which would have been - matched by TEI-All.

- -

Note that content models are generally defined (as far as possible) in terms of - references to model classes, rather than to explicit elements. This means that the need to - modify content models is greatly reduced: if an element is deleted or modified, for - example, then the deletion or modification will be available for every content model which - references that element via its class, as well as those which reference it explicitly. For - this reason it is not (in general) good practice to replace class references by explicit - element references, since this may have unintended side effects.

- -

An unqualified reference to an element class within a content model generates a content - model which is equivalent to an alternation of all the members of the class referenced. - Thus, a content model which refers to the model class model.phrase will generate a content model in which any one of the members of - that class is equally acceptable. The classRef element used to reference a class - has an expand attribute which may be used to vary this behaviour, for example - to require an optional repeatable alternation of all members of a class, a - sequence containing no more than one of each member of the class, etc. as described - further in .

- -

Content model changes which are not simple restrictions on an existing model should be - undertaken with caution. The set of documents matching the schema which results from such - changes is unlikely to be contained by the set of documents matching TEI-All, and such - changes are therefore regarded as unclean. When content models are changed or extended, - care should be taken to respect the existing semantics of the element concerned as stated - in these Guidelines. For example, the element l is defined as containing a line - of verse. It would not therefore make sense to redefine its content model so that it could - also include members of the class model.pLike such as - p or ab. Although syntactically feasible, such a modification would - not be regarded as TEI-conformant because it breaks the TEI Abstract Model.

- -
- - -
- Modification of Attribute and Attribute Value Lists - -

The attributes applicable to a given element may be specified in two ways: they may be - given explicitly, by means of an attList element within the corresponding - elementSpec, or they may be inherited from an attribute class, as specified in - the classes element. To add a new attribute to an element, the designer should - therefore first check to see whether this attribute is already available from some - existing attribute class. If it is, then the simplest method of adding it will be to make - the element in question a member of that class, as further discussed below. If this is not - possible, then a new attDef element must be added to the existing - attList for the element in question.

- -

Whichever method is adopted, the modification capabilities are the same as those - available for elements. Attributes may be added or deleted from the list, using the - mode attribute on attDef in the same way as on elementSpec. - The content of an attribute is defined by means of the datatype, - valList, or valDesc elements within the attDef element. Any - of these elements may be changed.

- -

Suppose, for example, that we wish to add two attributes to the eg element (used - to indicate examples in a text), type to characterize the example in some way, - and valid to indicate whether the example is considered valid or not. A quick - glance through the Guidelines indicates that the attribute class att.typed could be used to provide the type attribute, but there is - no comparable class which will provide a valid attribute. The existing - eg element in fact has no local attributes defined for it at all: we will - therefore need to add not only an attDef element to define the new attribute, but - also an attList to hold it.

-

We begin by adding the new valid attribute: - - - indicates whether or not the example is considered to be valid - - - - - - -

-

The value supplied for the mode attribute on the attDef element is - add; if this attribute already existed on the element we are modifying this - should generate an error, since a specification cannot have more than one attribute of the - same name. If the attribute is already present, we can replace the whole of the existing - declaration by supplying replace as the value for mode; - alternatively, we can change some parts of an existing declaration only by supplying just - the new parts, and setting change as the value for mode.

- -

Because the new attribute is not defined by the TEI, it is good practice to specify a - namespace for it on the attDef; see further .

- - -

As noted above, adding the new type attribute involves changing this element's - class membership; we therefore discuss that in the next section ().

- -

The canonical name for the new attribute is valid, and is supplied on the - ident attribute of the attDef element. In this simple example, we - supply only a description and datatype for the new attribute; the former is given by the - desc element, and the latter by the datatype element. (There are of - course many other pieces of information which could be supplied, as documented in ). The content of the datatype - element - is a dataRef element which references an existing TEI data specification.

- -

It is often desirable to constrain the possible values for an attribute to a greater - extent than is possible by simply supplying a TEI datatype for it. This facility is - provided by the valList element, which can also appear as a child of the - attDef element. Suppose for example that, rather than simply indicating whether - or not the example is considered valid by means of the values true and - false we wish to provide a more nuanced indication, using encoded values such - as A, B, and C. A declaration like the following might be appropriate: - - - - indicates the validity of the example by supplying one of three predefined - codes for it. - - - - - - validity is of the highest class - - - validity is of the second highest class - - - validity is of the lowest class - - - - - -

- -

The same technique may be used to replace or extend the valList supplied as part - of any attribute in the TEI schema.

- - -
-
- Class Modification - -

The concept of element classes was introduced in ; an - understanding of it is fundamental to successful use of the TEI system. As noted there, we - distinguish model classes, the members of which all have structural - similarity, from attribute classes, the members of which simply share a set - of attributes.

-

The part of an element specification which determines its class membership is an element - called classes. All classes to which the element belongs must be specified within - this, using a memberOf element for each.

-

To add an element to a class in which it is not already a member, all that is needed is - to supply a new memberOf element within the classes element for the - element concerned. For example, to add an element to the att.typed class, we include a declaration like the following: - - - - Any existing class memberships for the element being changed are - not affected because the mode attribute of the classes element is set - to change (rather than its default value of replace). Consequently, - in this case, the eg element retains its membership of the two classes (model.common and model.graphicLike) to - which it already belongs.

-

Equally, to remove the attributes which an element inherits from its membership in some - class, all that is needed is to remove the relevant memberOf element. For - example, the element term defined in the core module is a member of two attribute - classes, att.typed and att.declaring. It inherits the attributes type and - subtype from the former, and the attribute decls from the latter. - To remove the last of these attributes from this element, we need to remove it from that - class: - - - - -

-

If the intention is to change the class membership of an element completely, rather than - simply add or remove it to or from one or more classes, the value of the mode - attribute of classes can be set to replace (which is the default if no - value is specified), indicating that the memberships indicated by its child - memberOf elements are the only ones applicable. Thus the following declaration: - - - - - would have the effect of removing the element term from - both its existing attribute classes, and adding it to the att.interpLike class.

-

If however the mode attribute is set to change, the implication is - that the memberships indicated by its child memberOf elements are to be combined - with the existing memberships for the element.

- -

To change or remove attributes inherited from an attribute class for all members of the - class (as opposed to specific members of that class), it is also possible to modify the - class specification itself. For example, the class att.global.rendition defines several attributes which are available for all - elements, namely rend, style, and rendition. If we decide - that we never wish to use the rend attribute, the simplest way of removing it - is to supply a modified class specification for att.global.rendition as follows: - - - - - Because the mode attribute on the classSpec defining the - attributes inherited through membership of this class has the value change, any - of its existing identifiable components not specified in the modification above will - remain unchanged. The only effect will therefore be to delete the rend - attribute from the class, and hence from all elements which are members of the class.

- -

The classes used in the TEI schema are further discussed in chapter . - Note in particular that classes are themselves classified: the attributes inherited by a - member of attribute class A may come to it directly from that class, or from another class - of which A is itself a member. For example, the class att.global is itself a member of the classes att.global.linking and att.global.analytic. By - default, these two classes are predefined as empty. However, if (for example) the linking module is included in a schema, a number of attributes - (corresp, sameAs, etc.) are defined as members of the att.global.linking class. All elements which are members of att.global will then inherit these new attributes (see further - section ). A new attribute may thus be added to the global class in - two ways: either by adding it to the attList defined within the class - specification for att.global; or by defining a new attribute - class, and changing the class membership of the att.global - class to reference it.

- - -

Such global changes should be undertaken with caution: in general removing existing - non-mandatory attributes from a class will always be a clean modification, in the same way - as removing non-mandatory elements. Adding a new attribute to a class however can be a - clean modification only if the new attribute is labelled as belonging to some namespace - other than the TEI.

- -

The same mechanisms are available for modification of model classes. Care should be taken - when modifying the model class membership of existing elements since model class - membership is what determines the content model of most elements in the TEI schema, and a - small change may have unintended consequences.

- - -
- - -
- Addition of New Elements - -

To add a completely new element into a schema involves providing a complete element - specification for it. It is recommended that the classes element of this new - declaration should include a reference to at least one TEI model class. Without such a - reference, the new element would not otherwise be referenced by the content model of any - other TEI element, and would therefore be inaccessible within a TEI document. It is also - possible to modify the content models of one or more existing elements to refer to the new - element explicitly, as discussed in - but this will generally be less convenient.

- -

For example, the three elements bibl, biblFull, and biblStruct - are all defined as members of the class model.biblLike. To add - a fourth member (say myBibl) to this class, we need to include - in the elementSpec defining our new element a memberOf element which - nominates the intended class: - - - - - The other parts of this declaration will typically include a - description for the new element and information about its content model, its attributes, - etc., as further described in .

-
- -
- Renaming of Elements - -

Every element and other named markup construct in the TEI schema has a canonical - name, usually composed of English language words or syllables: this name is supplied as the value of the - ident attribute on the elementSpec, attDef, - classSpec, or macroSpec used to define it. In some circumstances, it may be - convenient for the element or attribute - declaration used within a schema generated from that specification to take a different form, for example, permitting schemas to use generic identifiers - from a different language, or in an abbreviated form. There may be many alternative - identifiers for the same markup construct, and an ODD processor may choose which of them - to use for a given purpose. Each such alternative name is supplied by means of an - altIdent element within the specification element concerned.

-

For example, the following declaration converts note to nt: - nt - Note that the mode attribute on the - elementSpec now takes the value change to indicate that those parts - of the element specification not supplied are to be inherited from the standard - definition. The content of the altIdent element is now available for use in place of the - canonical ident value in the schema generated.

- -

Renaming in this way is is an - inherently unclean modification (because the set of documents matched by the resulting - schema is not contained by the set matched by TEI-All), even though the process of - converting any document in which elements have been renamed into an exactly equivalent - document using canonical names is completely deterministic. Documents using such a schema should not claim to be - in the TEI namespace, but either use a null namespace or some user-defined - namespace, as further discussed in ; this is necessary to - avoid the risk of name collision between the new name and all existing TEI names as well as for reasons - of conformance - (see further ).

- -
- -
- -
- Modification and Namespaces - - -

All the elements defined by the TEI schema are labelled as belonging to a single - namespace, maintained by the TEI and with the URI - http://www.tei-c.org/ns/1.0.This is not strictly the case, - since the element egXML used to represent TEI examples has its own namespace, - http://www.tei-c.org/ns/Examples; this is the only exception however. - Only elements which are unmodified or which have undergone a clean modification may use this - namespace. Note however that TEI-defined attributes are not associated with any namespace. -

- -

This implies that any other modification - must either specify a different - namespace or, equivalently, specify no namespace at all. The ns attribute is - provided on elements schemaSpec, elementSpec, and attDef for this - purpose.

-

Suppose, for example, that we wish to add a new attribute topic to the existing TEI element p. In the absence of namespace - considerations, this would be an unclean modification, since p does not currently - have such an attribute. The most appropriate action is to explicitly attach the new - attribute to a new namespace by a declaration such as the following: - - - - indicates the topic of a TEI paragraph - - - - -

-

Document instances using a schema derived from this ODD can now indicate clearly the status - of this attribute: -

- -

Flopsy, Mopsy, Cottontail, and Peter...

-

- -

Since topic is explicitly labelled as belonging to something - other than the TEI namespace, we regard the modification which introduced it as clean. A - namespace-aware processor will be able to validate those elements in the TEI namespace - against the unmodified schema.Full namespace support does not exist in - the DTD language, and therefore these techniques are available only to users of more - modern schema languages such as RELAX NG or W3C Schema.

- -

Similar considerations apply when modification is made to the content model or some other - aspect of an element, or when a new element is declared. - All such changes should be explicitly - labelled as belonging to some non-TEI namespace or to no namespace at all.

-

If the ns attribute is supplied on a schemaSpec element, it identifies - the namespace applicable to all components of the schema being specified. Even if such a - schema includes unmodified modules from the TEI namespace, the elements contained by such - modules will now be regarded as belonging to the namespace specified on the - schemaSpec. This can be useful if it is desired simply to avoid namespace - processing. For example, the following schema specification results in a schema called - noName which has no namespace, even though it comprises declarations from - the TEI header module: - - - -

-

In addition to the TEI canonical namespace mentioned above, the TEI may also define - namespaces for approved translations of the TEI schema into other languages. - - The namespace for such translations is the same as that for the canonical namespace, - suffixed by the appropriate ISO language identifier (). A schema - specification using the Chinese translation, for example, would use the namespace http://www.tei-c.org/ns/1.0/zh -

-
- -
- Documenting the Modification - -

The elements used to define a TEI customization (schemaSpec, moduleRef, - elementSpec, etc.) will typically be used within a TEI document which supplies - further information about the intended use of the new schema, the meaning and application of - any new or modified elements within it, and so on. This document will typically conform to a - schema which includes components from the module described in - chapter .This module can be used to document any XML - schema, and has indeed been used to document several non-TEI schemas.

-

Where the customization to be documented simply consists in a selection of TEI modules, - perhaps with some deletion of unwanted elements or attributes, the documentation need not - specify anything further. Even here however it may be considered worthwhile to replace some - of the semantic information provided by the unmodified TEI specification. For example, the - desc element of an unmodified TEI elementSpec may describe an element in - terms more general than appropriate to a particular project, or the exemplum - elements within it may not illustrate the project's actual intended usage of the element, or - the remarks element may contain discussions of matters irrelevant to the project. - These elements may therefore be replaced or deleted within an elementSpec as - necessary.

- - - -

Radical revision is also possible. It is feasible to produce a modification in which the - teiHeader or text elements are not required, or in which any other rule - stated in these Guidelines is either not enforced or not enforceable. In fact, the - mechanism, if used in an extreme way, permits replacement of all that the TEI has to say - about every component of its schema. Such revisions would result in documents that are not - TEI-conformant in even the broadest sense, and it is not intended that encoders use the - mechanism in this way. We discuss exactly what is meant by the concept of TEI - conformance in the next section, .

-
- - - -
- Examples of Modification - -

Several examples of customizations of the TEI are provided as part of the standard release. - They include the following: - - The schema generated from this customization is the minimum needed for TEI - Conformance. It provides only a handful of elements. - - The schema generated from this customization combines all available TEI modules, - providing elements. - - The schema generated from this customization combines all available TEI modules with - three other non-TEI vocabularies, specifically MathML, SVG, and XInclude. - -

-

It is unlikely that any project would wish to use any of these extremes unchanged. However, - they form a useful starting point for customization, whether by removing modules from - tei_all or tei_allPlus, or by replacing elements deleted from tei_bare. They also - demonstrate how an ODD document may be constructed to provide a basic reference manual to - accompany schemas generated from it.

- -

Shortly after publication of the first edition of these Guidelines, as a demonstration of - how the TEI encoding schema might be adopted to meet 90% of the needs of 90% of the TEI user - community, the TEI editors produced a brief tutorial defining one specific - clean modification of the TEI schema, which they called TEI Lite. - This tutorial and its associated DTD became very popular and are still available from the - TEI web site at . The - tutorial and associated schema specification is also included as one of the exemplars - provided with TEI P5.

-

An updated and expanded version of this schema known as TEI simplePrint was - added to the Exemplars at release 3.1.0. The elements it defines have been modified to take - advantage of the processing model features (see further ) introduced to the Guidelines at release 3.0.0.

-

The exemplars provided with TEI P5 also include a customization file from which a schema - for the validation of other customization files may be generated. This ODD, called tei_odds, - combines the four basic modules with the tagdocs, dictionaries, gaiji, linking, and figures - modules and also provides facilities for including RELAX NG or Schematron code within a - document. -

-
- - - - -
- - - -
- - Conformance - -

The notion of TEI Conformance is intended to assist in the description of the - format and contents of a particular XML document instance or set of documents. It may be found - useful in such situations as: - interchange or integration of documents amongst different researchers or users; - software specifications for TEI-aware processing tools; - agreements for the deposit of texts in, and distribution of texts from, archives; - specifying the form of documents to be produced by or for a given project. - It is not intended to provide any other evaluation, for example of scholarly merit, - intellectual integrity, or value for money. A document may be of major intellectual importance - and yet not be TEI-conformant; a TEI-conformant document may be of no scholarly value - whatsoever.

- -

In this section we explore several aspects of conformance, and in particular attempt to - define how the term TEI-conformant should be used. The terminology defined here - should be considered normative: users and implementors of the TEI Guidelines should use the - phrases TEI-conformant and - TEI Extension only in the senses given and with the usages described.

- -

A document is TEI-conformant if it: - is a well-formed XML document () - can be validated against a TEI Schema, that is, a schema derived from the - TEI Guidelines () - conforms to the TEI Abstract Model () - uses the TEI namespace (and other namespaces where relevant) correctly - () - is documented by means of a TEI-conformant ODD file () which refers to the TEI Guidelines - Each of these criteria is discussed in more detail below.

- - - -

A document is said to use a TEI Extension if it is a well-formed XML document - which is valid against a TEI Schema which contains additional distinctions, representing - concepts not present in the TEI Abstract Model, and therefore not documented in these - Guidelines. Such a document - cannot necessarily be transformed automatically to a TEI-conformant document without loss of - information. However, since one of the goals of the TEI is to support extensions and - modifications, it should not be assumed that no TEI document can include extensions: an - extension which is expressed by means of the recommended mechanisms is also a TEI-conformant - document provided that those parts of it which are not extensions are - TEI-conformant.

- -

A TEI-conformant document is said to follow TEI Recommended - Practice if, wherever these Guidelines prefer one encoding practice to another, the - preferred practice is used.

- -
- - Well-formedness Criterion - -

These Guidelines mandate the use of well-formed XML as representation format. Documents - must conform to the World Wide Web Consortium recommendation of the Extensible Markup - Language (XML) 1.0 (Fourth Edition) or successor editions found at . Other ways of - representing the concepts of the TEI Abstract Model are possible, and other representations - may be considered appropriate for use in particular situations (for example, for data - capture, or project-internal processing). But such alternative representations - should not be - considered in any way TEI-conformant.

- -

Previous versions of these Guidelines used SGML as a representation format. With the - release of P5, the only representation format supported by these Guidelines became valid - XML; legacy documents in SGML format should therefore be converted using appropriate - software.

-

A TEI-conformant document must use the TEI namespace, and therefore must also include an - XML-conformant namespace declaration, as defined below ().

-

The use of XML greatly reduces the need to consider hardware or software differences - between processing environments when exchanging data. No special packing or interchange - format is required for an XML document, beyond that defined by the W3C recommendations, and - no special interchange format is therefore proposed by these - Guidelines. For discussion of encoding issues that may arise in the processing of special - character sets or non-standard writing systems, see further chapter .

- -

In addition to the well-formedness criterion, the W3C defines the notion of a - valid document, as being a well-formed document which matches a specific set - of rules or syntactic constraints, defined by a schema. As noted above, TEI - conformance implies that the schema used to determine validity of a given document should be - derived from the present Guidelines, by means of an ODD which references and documents - components which these Guidelines define.

-
- -
- Validation Constraint - -

All TEI-conformant documents must validate against a schema file that has been - derived from the published TEI Guidelines, combined and documented in the manner described - in section . We call the formal output of this process a TEI - Schema.

- -

The TEI does not mandate use of any particular schema language, only that this schemaHere and elsewhere we use the word schema to refer - to any formal document grammar language, irrespective of the formalism used to represent - it. should have been generated from a TEI ODD file that references the - TEI Guidelines. Currently available tools permit the expression of schemas in any or all of - the XML DTD language, W3C XML Schema, and RELAX NG (both compact and XML formats). Some of - what is syntactically possible using the ODD formalism cannot be represented by all schema - languages; and there are some features of some schema languages which have no counterpart in - ODD. No single schema language fully captures all the constraints implied by conformance to - the TEI Abstract Model. A document which is valid according to a TEI schema represented - using one schema language may not be valid against the same schema expressed in other - languages; for example, the DTD language does not support namespaces. -

- -

As noted in section , many varieties of TEI schema are possible and not - all of them are necessarily TEI-conformant; derivation from an ODD is a - necessary but not a sufficient condition for TEI Conformance.

- - -
- -
- - Conformance to the TEI Abstract Model - -

The TEI Abstract Model is the conceptual schema instantiated by the TEI - Guidelines. These Guidelines define, both formally and informally, a set of abstract - concepts such as paragraph or heading, and their structural relationships, for - example stating that paragraphs do not contain - headings. These Guidelines also define classes of elements, which - have both semantic and structural properties in common. Those semantic and structural - properties are also a part of the TEI Abstract Model; the class membership of an existing - TEI element cannot therefore be changed without changing the model. Elements can however be - removed from a class by deletion, and new non-TEI elements within their own namespaces can - be added to existing TEI classes.

- - -
- Semantic Constraints - -

It is an important condition of TEI conformance that elements defined in the TEI - Guidelines as having one specific meaning should not be used with another. For example, - the element l is defined in the TEI Guidelines as containing a line of verse. A - schema in which it is redefined to mean a typographic line, or an ordered queue of objects - of some kind, cannot therefore be TEI-conformant, whatever its other properties.

- -

The semantics of elements defined in the TEI Guidelines are conveyed in a number of ways, - ranging from formally verifiable datatypes to informal descriptive prose. In addition, a - mapping between TEI elements and concepts in other conceptual models may be provided by - the equiv element where this is available.

- -

A schema which shares equivalent concepts to those of the TEI conceptual model may be - mappable to the TEI Schema by means of such a mechanism. For example, the concept of - paragraph expressed in the TEI schema by the p element is probably the same - concept as that expressed in the DocBook schema by the para element. - Such - areas of overlap facilitate - interchange - because elements from one namespace may be readily integrated with those from another, but - do not affect the definition of conformance.

- -

A document is said to conform to the TEI Abstract Model if features for - which an encoding is proposed by the TEI Guidelines are encoded within it using the markup - and other syntactic properties defined by means of a valid TEI-conformant - schema. Hence, even though the names of elements or attributes may vary, a TEI-conformant - document must respect the TEI Semantic Model, and be valid with respect to a - TEI-conformant Schema. Although it may be possible to transform a document which follows - the TEI Abstract Model into a TEI-conformant document, such a - document is not itself conformant.

-

As noted above, the notion of semantic conformance cannot be completely enforced in a - formal way. The TEI conceptual model is expressed by means of formal specification in a - customization file, by means of descriptive prose in the body of these Guidelines, and - implicitly by examples of usage. Any inconsistency between, for example, the text of these - Guidelines and a part of a specification should be considered an error and reported to the - TEI Council for correction.

- -
- -
- Mandatory Components of a TEI Document - -

It is a long-standing requirement for any TEI-conformant document that it - should contain a teiHeader element. To be more specific a - TEI-conformant document must contain - a single teiHeader element followed by one or more elements from the - model.resource class; or - in the case of a corpus or collection, a single overall teiHeader - element followed by a series of TEI elements each with its own - teiHeader - All teiHeader elements in a TEI-conformant document must - include elements for: - - This should include the title of the TEI document expressed using a - titleStmt element. - - This should include the place and date of publication or distribution of the TEI - document, expressed using the publicationStmt element. - - For a document derived from some previously existing document, this must include a - bibliographic description of that source. For a document not so derived, this must - include a brief statement that the document has no pre-existing source. In either - case, this will be expressed using the sourceDesc element. -

- -
- -
- - -
- Use of the TEI Namespace - -

The Namespaces Recommendation of the W3C () provides a way for - an XML document to combine markup from different vocabularies without risking name collision - and consequent processing difficulties. While the scope of the TEI is large, there are many - areas in which it makes no particular recommendation, or where it recommends that other - defined markup schemas should be adopted, such as graphics or mathematics. It is also - considered desirable that users of other markup schemas should be able to integrate - documents using TEI markup with their own system. To meet these objectives without - compromising the reliability of its encoding, a TEI-conformant document is required to make - appropriate use of the TEI namespace.

- -

Essentially all elements in a TEI Schema which represents concepts from the TEI Abstract - Model belong to the TEI namespace, http://www.tei-c.org/ns/1.0, - maintained by the TEI. A TEI-conformant document is required to declare the namespace for - all the elements it contains whether these come from the TEI namespace or from other - schemas.

- -

A TEI Schema may be created which assigns TEI elements to some other namespace, or to no - namespace at all. A document using such a schema cannot be considered - TEI-conformant. A document which places non-TEI - elements or attributes within the TEI namespace cannot be considered TEI-conformant; such - practices are strongly deprecated as they may lead to serious difficulties for processing or - interchange.

- -
- -
- Documentation Constraint - -

As noted in above, a TEI Schema can only be generated from a TEI ODD, - which also serves to document the semantics of the elements defined by it. A TEI-conformant - document should therefore always be accompanied by (or refer to) a valid TEI ODD - file specifying which modules, elements, classes, etc. are in use together with any - modifications applied, and from which a TEI Schema can be generated to - validate the document. The TEI supplies a number of predefined TEI Customization - exemplar ODD files and the schemas already generated from them (see ), but most projects will typically need to customize the TEI beyond - what these examples provide. It is assumed, for example, that most projects will customize - the TEI schema by removing those elements that are not needed for the texts they are - encoding, and by providing further constraints on the attribute values and element content - models the TEI provides. All such customizations must be specified by means of a valid - TEI ODD file.

- -

As different sorts of customization have different implications for the interchange and - interoperability of TEI documents, it cannot be assumed that every customization will - necessarily result in a schema that validates only TEI-conformant documents. The ODD - language permits modifications which conflict with the TEI Abstract Model, even though - observing this model is a requirement for TEI Conformance. The ODD language can in fact be - used to describe many kinds of markup schema, including schemas which have nothing to do - with the TEI at all.

- -

Equally, it is possible to construct a TEI Schema which is identical to that derived from a - given TEI ODD file without using the ODD schema. A schema can constructed simply by - combining the predefined schema language fragments corresponding with the required set of - TEI modules and other statements in the relevant schema language. However, the status of - such a schema with respect to the tei_all schema cannot in - general be easily determined; it may therefore be impractical to determine whether such a - schema represents a clean modification or an extension. This is one reason for making the - presence of a TEI ODD file a requirement for conformance.

- -
- - - - -
- Varieties of TEI Conformance - -

The conformance status of a given document may be assessed by answering the following - questions, in the order indicated: - Is it a valid XML document, for which a TEI Schema exists? If not, then the document - cannot be considered TEI-conformant in any sense. - Is the document accompanied by a TEI-conformant ODD specification describing its - markup schema and intended semantics? If not, then the document can only be considered - TEI-conformant if it validates against a predefined TEI Schema and conforms to the TEI - abstract model. - Does the markup in the document correctly represent the TEI abstract model? Though - difficult to assess, this is essential to TEI conformance. - Does the document claim that all of its elements come from some namespace other than - the TEI (or no namespace)? If so, the document cannot be TEI-conformant. - If the document claims to use the TEI namespace, in part or wholly, do the elements - associated with that namespace in fact belong to it? If not, the document cannot be - TEI-conformant; if so, and if all non-TEI elements and attributes are correctly - associated with other namespaces, then the document may be TEI-conformant. - Is the document valid according to a schema made by combining all TEI modules as - well as valid according to the schema derived from its associated ODD specification? If - so, the document is TEI-conformant. - Is the document valid according to the schema derived from its associated ODD - specification, but not according to tei_all? If so, the - document uses a TEI extension. - Is it possible automatically to transform the document into a document which is - valid according to tei_all, using only information supplied - in the accompanying ODD and without loss of information? If so, the document is - TEI-conformant. - -

- -

In the following table, we examine more closely some specific, though imaginary, cases: - - - - A - B - C - D - E - F - G - H - - - Conforms to TEI Abstract Model - Y - N - Y - Y - ? - Y - N - ? - - - Valid ODD present - Y - Y - Y - Y - Y - Y - Y - N - - - Uses only non-TEI namespace(s) or none - N - N - N - N - Y - N - Y - N - - - Uses TEI and other namespaces correctly - Y - Y - N - Y - N - Y - N - Y - - - Document is valid as a subset of tei_all - Y - N - Y - N - N - Y - N - Y - - - Document can be converted automatically to a form which is valid as a subset of - tei_all - Y - N - Y - N - N - Y - N - ? - -
-

-

We assume firstly that each sample document assessed here is a well-formed XML document, - and that it is valid against some schema.

-

The document in column A is TEI-conformant. Its tagging follows the TEI Abstract Model, - both as regards syntactic constraints (its l elements appear within div - elements and not the reverse) and semantic constraints (its l elements appear to - contain verse lines rather than typographic ones). It is accompanied by a valid ODD which - documents exactly how it uses the TEI. All the TEI-defined elements and attributes in the - document are placed in the TEI namespace. The schema against which it is valid is a - clean subset of the tei_all schema.

- -

The document in column B is not a TEI document. Although it is accompanied by a valid TEI - ODD, the resulting schema includes some unclean modifications, and - represents some concepts from the TEI Abstract Model using non-TEI elements; for example, it - re-defines the content model of p to permit div within it, and it includes - an element pageTrimming which appears to have the same meaning - as the existing TEI fw element, but the equivalence is not made explicit in the - ODD. It uses the TEI namespace correctly to identify the TEI elements it contains, but the - ODD does not contain enough information automatically to convert its non-TEI elements into - TEI equivalents.

- -

The document in column C is TEI conformant. It is almost the same as - the document in column A, except that the names of the elements used are not those specified - for the TEI namespace. Because the ODD accompanying it contains an exact mapping for each - element name (using the altIdent element) and there are no name conflicts, it is - possible to make an automatic conversion of this document.

- -

The document in column D is a TEI Extension. It combines elements from its own namespace - with unmodified TEI elements in the TEI namespace. Its usage of TEI elements conforms to the - TEI Abstract Model. Its ODD defines a new blort element which - has no exact TEI equivalent, but which is assigned to an existing TEI class; consequently - its schema is not a clean subset of tei_all. If the associated - ODD provided a way of mapping this element to an existing TEI element, then this would be - TEI-conformant.

- -

The document in column E is superficially similar to document D, but because it does not - use any namespace declarations (or, equivalently, it assigns unmodified TEI elements to its - own namespace), it may contain name collisions; there is no way of knowing whether a - p within it is the same as the TEI's p or has some other meaning. The - accompanying ODD file may be used to provide the human reader with information about - equivalently named elements in the TEI namespace, and hence to determine whether the - document is valid with respect to the TEI Abstract Model but this is not an automatable - process. In particular, cases of apparent conflict (for example use of an element p - to represent a concept not in the TEI Abstract Model but in the abstract model of some other - system, whose namespace has been removed as well) cannot be reliably resolved. By our - current definition therefore, this is not a TEI document.

- -

The document in column F is TEI-conformant. The difference between it and that in - column D is that the new element blort which is used in this - document is a specialization of an existing TEI element, and the ODD in which it is defined - specifies the mapping (a my:blort may be automatically converted - to a tei:seg type="blort", for example). For this to work, however, the blort must observe the same syntactic constraints as the - seg; if it does not, this would also be a case of TEI Extension.

- -

The document in column G is not a TEI document. Its structure is fully documented by a - valid TEI ODD, but it does not claim to represent the TEI Abstract Model, does not use the - TEI namespace, and is not intended to validate against any TEI schema.

- -

The document in column H is very like that in column A, but it lacks an accompanying ODD. - Instead, the schema used to validate it is produced simply by combining TEI schema fragments - in the same way as an ODD processor would, given the ODD. If the resulting schema is a clean - subset of tei_all, such a document is indistinguishable from a - TEI-conformant one, but there is no way of determining (without inspection) whether this is - the case if any modification or extension has been applied. Its status is therefore, like - that of Text E, impossible to determine.

- -
- - -
- - - - - -
- Implementation of an ODD System -

This section specifies how a processing system may take advantage of the markup specification - elements documented in chapter of these Guidelines in order to produce - project specific user documentation, schemas in one or more schema languages, and validation - tools for other processors.

- -

The specifications in this section are illustrative but not normative. Its function is to - further illustrate the intended scope and application of the elements documented in chapter - , since it is believed that these may have application beyond the areas - directly addressed by the TEI.

- -

An ODD processing system has to accomplish two main tasks. A set of selections, deletions, - changes, and additions supplied by an ODD customization (as described in ) - must first be merged with the published TEI P5 ODD specifications. Next, the resulting unified - ODD must be processed to produce the desired outputs.

- -

An ODD processor is not required to do these two stages in sequence, but that may well be the - simplest approach; the ODD processing tools currently provided by the TEI Consortium, which - are also used to process the source of these Guidelines, adopt this approach.

- -
- Making a Unified ODD -

An ODD customization must contain a single schemaSpec element, which defines the - schema to be constructed. - - Amongst other attributes inherited from the att.identified class, this element also carries a required ident - attribute. This provides a name for the generated schema, which other components of the - processing system may use to refer to the schema being generated, e.g. in issuing error - messages or as part of the generated output schema file or files. The ns - attribute may be used to specify the default namespace within which elements valid against - the resulting schema belong, as discussed in .

-

The schemaSpec element contains an unordered series of specialized elements, each - of which is of one of the following four types: - - elements from the class model.oddDecl (by default - elementSpec, classSpec, moduleSpec, and - macroSpec); these must have a mode attribute which determines how - they will be processed.An ODD processor should recognize as - erroneous such obvious inconsistencies as an attempt to include an - elementSpec in add mode for an element which is already present - in an imported module. If the value of mode is add, then - the object is simply copied to the output, but if it is change, - delete, or replace, then it will be looked at by other parts of - the process. - - specGrpRef elements refer to specGrp elements that occur elsewhere - in this, or another, document. A specGrp element, in turn, groups together a - set of ODD specifications (among other things, including further specGrpRef - elements). The use of specGrp and specGrpRef permits the ODD markup to - occur at the points in documentation where they are discussed, rather than all inside - schemaSpec. The target attribute of any specGrpRef should - be followed, and the elementSpec, classSpec, and macroSpec, - elements in the corresponding specGrp should be processed as described in the - previous item; specGrpRef elements should be processed as described - here. - - moduleRef elements with key attributes refer to components of - the TEI. The value of the key attribute matches the ident - attribute of the moduleSpec element defining a TEI module. The key - must be dereferenced by some means, such as reading an XML file with the TEI ODD - specification (either from the local hard drive or off the Web), or looking up the - reference in an XML database (again, locally or remotely); whatever means is used, it - should return a stream of XML containing the element, class, and macro specifications - collected together in the specified module. These specification elements are then - processed in the same way as if they had been supplied directly within the - schemaSpec being processed. - - - a moduleRef element may also refer to a compatible external module by means - of its url attribute; the content of such modules, which must be available in - the RELAX NG XML syntax, are passed directly and without modification to the output - schema when that is created. - -

- -

Each object obtained from the TEI ODD specification using moduleRef by means of - the key attribute must be checked against objects in the customization - schemaSpec according to the following rules: - if there is an object in the ODD customization with the same value for the - ident attribute, and a mode value of delete, then the - object from the module is ignored; - if there is an object in the ODD customization with the same value for the - ident attribute, and a mode value of replace, then - the object from the module is ignored, and the one from the ODD customization is used in - its place; - if there is an object in the ODD customization with the same value for the - ident attribute, and a mode value of change, then the - two objects must be merged, as described below; - if there is an object in the ODD customization with the same value for the - ident attribute, and a mode value of add, then an - error condition should be raised; - - otherwise, the object from the module is copied to the result. - -

- -

To merge two objects with the same ident, their component attributes and child - elements must be looked at recursively. Each component may fall into one of the following - four categories: - - Some components may occur only once within the merged object (for example - attributes, and altIdent, content, or classes elements). If - such a component is found in the ODD customization, it will be copied to the output; if - it is not found there, but is present in the TEI ODD specification, then that will be - copied to the output. - - Some components are grouping objects (attList, valList, for - example); these are always copied to the output, and their children are then processed - following the rules given in this list. - - Some components are identifiable: this means that they are - members of the att.identified class from which they inherit - the ident attribute; examples include attDef and valItem. A - component of this type will be processed according to its mode attribute, - following the rules given above. - - Some components may occur multiple times, but are neither grouped nor identifiable. - Examples include the desc, exemplum, remarks, listRef, - datatype and defaultVal elements, and the members of - model.identSynonyms, i.e., the equiv, - altIdent, and gloss, elements. These should be copied from both the TEI - ODD specification and the ODD customization, and all occurrences included in the output. - -

- -

A special problem arises with elements which are members of attribute classes, as they are - permitted to override attributes inherited from a class. For example, consider this simple - modification: - - - - - - - The effect of its membership in the att.typed class is - to provide p with a type attribute and a subtype attribute. - If we wish p to not have subtype, we could extend the - customization in our schema as follows: - - - - - - - - - - This means that when memberOf key="att.typed"/ is processed, that class - is looked up, each attribute which it defines is examined in turn, and the customization is - searched for an override. If the modification is of the attribute class itself, work - proceeds as usual; if, however, the modification is at the element level, the class - reference is deleted and a series of attRef elements is added to the element, one - for each attribute inherited from the class. Since attribute classes can themselves be - members of other attribute classes, membership must be followed recursively.

- -

The effect of the concatenation of unidentifiable components should be considered - carefully. An original may have - - marks paragraphs in prose. - - - which would usefully be extended with this: - - marca párrafos en prosa. - - - to provide an alternate description in another language. Nothing prevents the user - from supplying desc several times in the same language, and subsequent applications - will have to decide what that may mean.

- -

Similar considerations apply to multiple example elements, though these are less likely to - cause problems in documentation. Note that existing examples can only be deleted by - supplying a completely new elementSpec in replace mode, since the - exemplum element is not identifiable.

- -

In the processing of the content models of elements and the content of macros, deleted - elements may require special attention.The carthago program behind the - Pizza Chef application, written by Michael Sperberg-McQueen for TEI P3 and P4, went to - very great efforts to get this right. The XSLT transformations used by the P5 Roma - application are not as sophisticated, partly because the RELAX NG language is more - forgiving than DTDs. A content model like this: - - - - - - - - - - - - - - - requires no special treatment because everything is expressed in terms of model - classes; if the class model.personPart is deleted explicitly, or - removed because all of its members have been deleted, then model.global is left as the only child of the inner alternate. An ODD - processor may or may not elect to simplify the resulting choice between nothing and model.global by removing the wrapper alternate element. - However, such simplification may be considerably more complex in the general case - and - an ODD processor is therefore likely to be more successful in carrying out such - simplification as a distinct stage during processing of ODD sources.

-

If an element refers directly to an element child, like this: - - - - - - - - - - - - - - - and figDesc has been deleted,Note that deletion of - required elements will cause the schema specification to accept as valid documents which - cannot be TEI-conformant, since they no longer conform to the TEI Abstract Model; - conformance topics are addressed in more detail in . it will be - necessary to remove that reference, or the resulting schema will be - invalid.

- -

The result of the work carried out should be a new schemaSpec which contains a - complete and internally consistent set of element, class, and macro specifications, possibly - also including moduleRef elements with url attributes identifying - external modules.

- -
- -
- Generating Schemas -

Assuming that any modifications have been resolved, as outlined in the previous section, - making a schema is now a four stage process: - all datatype and other macro specifications must be collected together and declared - at the start of the output schema; - all classes must be declared in the right order (order is significant because since - some classes reference others); - all elements are declared; - any moduleRef elements with a url attribute identifying an - external schema must be processed. - Working in this order gives the best chance of successfully supporting all the - schema languages. However, there are a number of obstacles to overcome along the way.

- -

An ODD processor may choose to use any desired schema language or languages for its schema - output, since ODD specifications are expressed as far as possible in a form independent of - any schema language. - - The current TEI ODD processing system produces schema output in the three main schema - languages as follows: - A RELAX NG (XML) schema is generated by converting content models, datatypes, and - macro specifications provided within the ODD specification; a version re-expressed in - the RELAX NG compact syntax is generated using James Clark's trang - application. - - A DTD schema is generated by converting the RELAX NG content models to DTD language, - often simplifying it to allow for the less-sophisticated output language. - - A W3C Schema schema is created by generating a RELAX NG schema and then using James - Clark's trang application. - Note that the method used to generate W3C Schema means that a processor must ensure - that the RELAX NG it generates follows the subset which trang is able to - translate properly (see further below)—this may involve simple trial and error.

- -

Other projects may decide to follow a different route, perhaps implementing a direct ODD to - W3C Schema translator.

- -

Secondly, it is possible to create two rather different styles of schema. On the one hand, - the schema can try to maintain all the flexibility of ODD by using the facilities of the - schema language for parameterization; on the other, it can remove all customization features - and produce a flat result which is not suitable for further manipulation. The TEI project - currently generates both styles of schema; the first as a set of schema fragments in DTD and - RELAX NG languages, which can be included as modules in other schemas, and customized - further; the second as the output from a processor such as Roma, in which many of the - parameterization features have been removed.

- -

The difference between the schema styles may be illustrated by considering this ODD - specification: - - - - - - - - - - - - - - - - - - - - - - - - A simple rendering to RELAX NG produces this: - In the above, a subsequent redefinition of the attribute class (such as att.global) would have no effect, since references to such classes have been - expanded to reference their constituent attributes.

-

The equivalent parameterized version might look like this: - Here, the attribute class att.global is provided via an - explicit reference (att.global.attributes), and can therefore be redefined. - Moreover, the attributes are separated from the content model, allowing either to be - overridden.

-

In the remainder of these section, the terms simple schema and - parameterized schema are used to distinguish the two schema types. An ODD - processor is not required to support both, though the simple schema output is generally - preferable for most applications.

- -

Thirdly, the problem of missing components must be resolved. For example, consider this - (fictitious) model for sp: - - - - - - - - - - - - - - This proposes anything from the class model.global, - followed optionally by a speaker element followed by anything from the model.global class. What happens if speaker is removed from - the schema? The following would result: - - - - - - - - - - - which is illegal in DTD and W3C schema languages, since for a given member of - model.global it is impossible to be sure which rule is being - used. This situation is not detected when RELAX NG is used, since the language is able to - cope with non-deterministic content models of this kind and does not require that only a - single rule be used.

- - -

Finally, an application will need to have some method of associating the schema with - document instances that use it. The TEI does not mandate any particular method of doing - this, since different schema languages and processors vary considerably in their - requirements. ODD processors may wish to build in support for some of the methods for - associating a document instance with a schema. The TEI does not mandate any particular - method, but does suggest that those which are already part of XML (the DOCTYPE declaration - for DTDs) and W3C Schema (the xsi:schemaLocation attribute) be supported where - possible.

- -

In order for the xsi:schemaLocation attribute to be valid when a document is - validated against either a DTD or a RELAX NG schema, ODD processors may wish to add - declarations for this attribute and its namespace to the root element, even though these are - not part of the TEI per se. For DTDs this means adding to the list of attributes on the root element, - which permits the non-namespace-aware DTD language to recognize the - xsi:schemaLocation notation. For RELAX NG, the namespace and attribute would - be declared in the usual way: and inside the root element - declaration.

- -

Note that declaration of the xsi:schemaLocation attribute in a W3C Schema schema - is not permitted. Therefore, if W3C Schemas are being generated by converting the RELAX NG - schema (for example, with trang), it may be necessary to perform that - conversion prior to adding the xsi:schemaLocation declaration to the RELAX - NG.

- -

It is recognized that this is an unsatisfactory solution, but it permits users to take - advantage of the W3C Schema facility for indicating a schema, while still permitting - documents to be validated using DTD and RELAX NG processors without any conflict.

- -
- -
- Names and Documentation in Generated Schemas -

When processing class, element, or macro specifications, there are three general rules: - - If a RELAX NG pattern or DTD parameter entity is being created, its name is the - value of the corresponding ident attribute, prefixed by the value of any - prefix attribute on schemaSpec. This allows for elements from an - external schema to be mixed in without risk of name clashes, since all TEI elements can - be given a distinctive prefix such as tei_. Thus - - - - - - may generate a RELAX NG (compact syntax) pattern like this: - References to these patterns (or, in DTDs, parameter entities) also need to be prefixed - with the same value. - - If an element or attribute is being created, its default name is the value of the - ident attribute, but if there is an altIdent child, its content is - used instead. - - Where appropriate, the documentation strings in gloss and desc - should be copied into the generated schema. If there is only one occurrence of either of - these elements, it should be used regardless, but if there are several, local processing - rules will need to be applied. For example, if there are several with different values - of xml:lang, a locale indication in the processing environment might be used - to decide which to use. For example, - - - heading - en-tête - encabezamiento - titolo - - - might generate a RELAX NG schema fragment like the following, if the locale is - determined to be French: - - Alternatively, a selection might be made on the basis of the value of the - version attribute which these elements carry as members of the att.translatable class.

-

In addition, there are three conventions about naming patterns relating to classes; ODD - processors need not follow them, but those reading the schemas generated by the TEI project - will find it necessary to understand them: - when a pattern for an attribute class is created, it is named after the attribute - class identifier (as above) suffixed by .attributes (e.g. - att.editLike.attributes); - when a pattern for an attribute is created, it is named after the attribute class - identifier (as above) suffixed by .attribute. and then the identifier of - the attribute (e.g. att.editLike.attribute.resp); - - - when a parameterized schema is created, each element generates patterns for its - attributes and its contents separately, suffixing respectively .attributes - and .contents to the element name. - -

-
- -
- Making a RELAX NG Schema - -

To create a RELAX NG schema, the processor processes every macroSpec, - classSpec, and elementSpec in turn, creating a RELAX NG pattern for - each, using the naming conventions listed above. The order of declaration is not important, - and a processor may well sort them into alphabetical order of identifier.

- -

A complete RELAX NG schema must have an rng:start element defining which elements - can occur as the root of a document. The ODD schemaSpec has an optional - start attribute, containing one or more patterns, which can be used to - construct the rng:start. A pattern normally corresponds to an element name, but if - a prefix (see above, ) is supplied for an element, the pattern - consists of the prefix name with the element name.

- -
- Macros -

An ODD macro generates a corresponding RELAX NG pattern by processing the body of the - content element in the same way as elsewhere. Thus - - - - - - - - - - - produces the following - - - - - - - - - - - -

-
- -
- Classes -

An ODD model class always generates a RELAX NG pattern definition listing all the members - of the class in alternation. For example - - - - will produce something like the following: - - - - - - - - assuming that the elements num, measure, and - measureGrp are all defined in the schema concerned as members of that class. A - model declaration may also generate a number of other patterns corresponding with - sequences or alternations of the class members: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - where the pattern name is created by appending an underscore and the name of the - generation type to the class name.

-

When classes are referenced using the classRef element, it is possible to - indicate which of the available patterns is required by means of the expand - attribute.

-

Attribute classes work by producing a pattern containing definitions of the appropriate - attributes. So - - - - - indicates whether the end of a verse line is marked by enjambement. - - - - - - - the line is end-stopped - - - - the line in question runs on into the next - - - - the line is weakly enjambed - - - - the line is strongly enjambed - - - - - - produces - - - - - - - - (enjambement) indicates whether the end of a verse line is marked by - enjambement. Sample values include: 1] no; 2] yes; 3] weak; 4] - strong - - - - - Since the processor may have expanded the attribute classes already, separate - patterns are generated for each attribute in the class as well as one for the class - itself. This allows an element to refer directly to a member of a class. Notice that the - desc element is used to add an a:documentation element to the schema, - which some editors use to provide help during composition. The desc elements in - the valList are used to create the human-readable sentence Sample values - include: 1] no; 2] yes; 3] weak; 4] strong Naturally, this behaviour is not - mandatory; and other ODD processors may create documentation in other ways, or ignore - those parts of the ODD specifications when creating schemas.

- -

An individual attribute consists of an rng:attribute with a name - attribute derived according to the naming rules described above (). In addition, the ODD model supports a defaultVal, which is transformed to a - defaultValue attribute in the namespace http://relaxng.org/ns/compatibility/annotations/1.0 on the - rng:attribute. The body of the attribute is taken from the datatype - child, unless there is a supporting valList with a type value of - closed. In that case an rng:choice is created, listing the allowed - values. Thus the following attribute definition - - yes - - - the name component is spelled out in full. - - - abbreviated - the name component is given in an abbreviated form. - - - initial letter - the name component is indicated only by one initial. - - - - may generate this RELAX NG code: - - - - - yes - the name component is spelled out in full. - abb - the name component is given in an abbreviated form. - init - the name component is indicated only by one initial. - - - - - - Note the use of the http://relaxng.org/ns/compatibility/annotations/1.0 namespace to provide - default values and documentation.

-
- -
- Elements -

An elementSpec produces a RELAX NG specification in two parts; firstly, it must - generate an rng:define pattern by which other elements can refer to it, and then - it must generate an rng:element with the content model and attributes. It may be - convenient to make two separate patterns, one for the element's attributes and one for its - content model.

-

The content model is created by processing the TEI declarations found within the - content element; ; the attributes are processed in the same way as those from - attribute classes, described above.

-
- -
- - -
- Making a DTD -

Generation of DTDs largely follows the same pattern as RELAX NG generation, with one - important exception—the order of declaration matters. A DTD may not refer to an - entity which has not yet been declared. Since both macros and classes generate DTD parameter - entities, the TEI Guidelines are constructed so that they can be declared in the right - order. A processor must therefore work in the following order: - declare all model classes which have a predeclare value of - true - declare all macros which have a predeclare value of - true - declare all other classes - declare the modules (if DTD fragments are being constructed) - declare any remaining macros - declare the elements and their attributes - -

-

Let us consider a complete example, a simple element with no attributes of its own: - - specifies the faith, religion, or belief set of a person. - - - - - - - - - - If DTD fragments are being generated (for use as described in ), this will result in the following: - - - - - -]]]]>]]> Here the whole stanza is contained in a marked section (for use as described in ), the element name is parameterized (see ), and - the class attributes are entity references derived from the memberOf records in - classes. Note the additional attribute which provides a default xmlns declaration for the element; the effect of this is that if the document is - processed by a DTD-aware XML processor, the namespace declaration will be present - automatically without the document author even being aware of it.

- -

A simpler rendition for a flattened DTD generated from a customization will result in the - following, with no containing marked section, and no parameterized name: - - -]]> Here the attributes from classes have been expanded into individual entity references.

- - - -
- -
- Generating Documentation -

In Donald Knuth's literate programming terminology (), the previous - sections have dealt with the tangle process; to generate documentation, we now - turn to the weave process.

- -

An ODD customization may consist largely of general documentation and examples, requiring - no ODD-specific processing. It will normally however also contain a schemaSpec - element and possibly some specGrp fragments.

- -

The generated documentation may be of two forms. On the one hand, we may document the - customization itself, that is, only those elements (etc.) which differ in their - specification from that provided by the TEI reference documentation. Alternatively, we may - generate reference documentation for the complete subset of the TEI which results from - applying the customization. The TEI Roma tools take the latter approach, and operate on the - result of the first stage processing described in .

- -

Generating reference documentation for elementSpec, classSpec, and - macroSpec elements is largely dependent on the design of the preferred output. - Some applications may, for example, want to turn all names of objects into hyperlinks, show - lists of class members, or present lists of attributes as tables, lists, or inline prose. - Another technique implemented in these Guidelines is to show lists of potential - parents for each element, by tracing which other elements have them - as possible members of their content models.

-

One model of display on a web page is shown in , corresponding to - the faith element shown in section .

-
- - Example reference documentation for faith -
- -
- - - - - -
- Using TEI Parameterized Schema Fragments -

The TEI parameterized DTD and RELAX NG fragments make use of parameter entities and - patterns for several purposes. In this section we describe their interface for the user. In - general we recommend use of ODD instead of this technique, which has been retained only for - compatability reasons.

- -
- Selection of Modules - -

Special-purpose parameter entities are used to specify which modules are to be combined - into a TEI DTD. They take the form TEI.xxxxx where xxxx is the - name of the module as given in table in . - For example, the parameter entity TEI.linking is used to define - whether or not to include the module linking. All such - parameter entities are declared by default with the value IGNORE: to select a - module, therefore, the encoder declares the appropriate parameter entities with the value - INCLUDE.

- -

For XML DTD fragments, note that some modules generate two DTD fragments: for example the - analysis module generates fragments called analysis-decl and analysis. This is - because the declarations they contain are needed at different points in the creation of an - XML DTD.

- -

The parameter entity named for the module is used as the keyword controlling a - conditional marked section in the DTD fragment generated by the tei module. The declarations for each DTD fragment constituting the module are - contained within such marked sections. For example, the parameter entity TEI.linking appears twice in tei.dtd, once for the - linking-decl schema fragment: - - -%file.linking-decl; -]] >]]> and once for the linking schema fragment: - -%file.linking;]] >]]> If TEI.linking has its default value of IGNORE, neither declaration has any effect. If - however it has the value INCLUDE, then the content of each marked section is acted upon: - the parameter entities file.linking and file.linking-decl are referenced, which has the effect of embedding the content - of the files they represent at the appropriate point in the DTD.

- -

The RELAX NG schema fragments can be combined in a wrapper schema using the standard - mechanism of rng:include in that language.

- -
- - -
- Inclusion and Exclusion of Elements - -

The TEI DTD fragments also use marked sections and parameter entity references to allow - users to exclude the definitions of individual elements, in order either to make the - elements illegal in a document or to allow the element to be redefined. The parameter - entities used for this purpose have exactly the same name as the generic identifier of the - element concerned. The default definition for these parameter entities is - INCLUDE but they may be changed to IGNORE in order to exclude the - standard element and attribute definition list declarations from the DTD.

- -

The declarations for the element p, for example, are preceded by a definition - for a parameter entity with the name p and - contained within a marked section whose keyword is given as %p;: - -]]]]>

-

These parameter entities are defined immediately preceding the element whose declarations - they control; because their names are completely regular, they are not documented further.

-

To define a DTD in which the element p is excluded therefore, the entity p needs to be redefined as IGNORE by - ensuring that a declaration such as - ]]> is added earlier in the - DTD than the default (see further ).

- -

Similarly, in the parameterized RELAX NG schemas, every element is defined by a pattern - named after the element. To undefine an element therefore all that is necessary is to add - a declaration like the following: - -

-
- -
- Changing the Names of Generic Identifiers - -

In the TEI DTD fragments, elements are not referred to directly by their generic - identifiers; instead, the DTD fragments refer to parameter entities which expand to the - standard generic identifiers. This allows users to rename elements by redefining the - appropriate parameter entity. Parameter entities used for this purpose are formed by - taking the standard generic identifier of the element and attaching the string - n. as a prefix. Thus the standard generic identifiers for paragraphs, notes, - and quotations, p, note, and persName are defined by - declarations of the following form: - -]]> Note that since all names are case-sensitive, the specific - mix of uppercase and lowercase letters in the standard generic identifier must be - preserved in the entity name.

- -

These declarations are generated by an ODD processor when TEI DTD fragments are created.

- -

In the RELAX NG schemas, all elements are normally defined using a pattern with the same - name as the element (as described in ): for example - The easiest way of renaming the element is thus simply to rewrite the pattern with a - different element name; any references use the pattern, not the element, name. - More complex revisions, such as redefining the content of the element (defined by the - pattern abbr.content) or its attributes (defined by the pattern - abbr.attributes) can be accomplished in a similar way, using - the features of the RELAX NG language. The recommended method of carrying out such - modifications is however to use the ODD language as further described in section .

-
- - -
- Embedding Local Modifications (DTD only) - -

Any local modifications to a DTD (i.e. changes to a schema other than simple inclusion or - exclusion of modules) are made by declarations stored in one of two local extension files, - one containing modifications to the TEI parameter entities, and the other new or changed - declarations of elements and their attributes. Entity declarations must be made which - associate the names of these two files with the appropriate parameter entity so that the - declarations they contain can be embedded within the TEI DTD at an appropriate point.

- -

The following entities are referred to by the main tei.dtd - file to embed portions of the TEI DTD fragments or locally developed extensions. - - identifies a local file containing extensions to the TEI parameter entities - - identifies a local file containing extensions to the TEI module -

-

For example, if the relevant files are called project.ent and project.dtd, then - declarations like the following would be appropriate: -]]>

- -

When an entity is declared more than once, the first declaration is binding and the - others are ignored. The local modifications to parameter entities should therefore be - handled before the standard parameter entities themselves are declared in tei.dtd. The entity TEI.extensions.ent is - referred to before any TEI declarations are handled, to allow the user's declarations to - take priority. If the user does not provide a TEI.extensions.ent - entity, the entity will be expanded to the empty string.

-

For example the encoder might wish to add two phrase-level elements it and bd, perhaps as synonyms for - hi rend='italics' and hi rend='bold'. As described in chapter , this involves two distinct steps: one to define the new elements, and - the other to ensure that they are placed into the TEI document structure at the right - place.

-

Creating the new declarations is done in the same way for user-defined elements as for - any other; the same parameter entities need to be defined so that they may be referenced - by other elements. The content models of these new elements may also reference other - parameter entities, which is why they need to be declared after other declarations.

-

The second step involves modifying the element class to which the new elements should be - attached. This requires that the parameter entity macro.phraseSeq - should be modified to include the generic identifiers for the new elements we wish to - create. The declaration for each modifiable parameter entity in the DTD includes a - reference to an additional parameter entity with the same name prefixed by an - x.; these entities are declared by default as the null string. However, in - the file containing local declarations they may be redeclared to include references to the - new class members: ]]> and this declaration will take precedence over the default when the declaration for - macro.phraseSeq is evaluated.

-
- -
- -
- -
diff --git a/P5/Source/Guidelines/fr/USE.xml b/P5/Source/Guidelines/fr/USE.xml new file mode 120000 index 0000000000..51bee9af4d --- /dev/null +++ b/P5/Source/Guidelines/fr/USE.xml @@ -0,0 +1 @@ +../en/USE.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/VE-Verse.xml b/P5/Source/Guidelines/fr/VE-Verse.xml deleted file mode 100644 index a1b8cb35f4..0000000000 --- a/P5/Source/Guidelines/fr/VE-Verse.xml +++ /dev/null @@ -1,916 +0,0 @@ - - - - -
- Verse -

This module is intended for use when encoding texts which are entirely or predominantly in - verse, and for which the elements for encoding verse structure already provided by the core - module are inadequate.

-

The tags described in section include elements for the encoding of verse - lines and line groups such as stanzas: these are available for any TEI document, irrespective - of the module it uses. Like the modules for prose and for drama, the module for verse - additionally makes use of the module defined in chapter to define the - basic formal structure of a text, in terms of front, body and back - elements and the text-division elements into which these may be subdivided.

-

The module for verse extends the facilities provided by these modules in the following ways: - - a special purpose caesura element is provided, to allow for segmentation of - the verse line (see section ) - a set of attributes is provided for the encoding of rhyme scheme and metrical - information (see sections and ) - a special purpose rhyme element is provided to support simple analysis of - rhyming words (see section ) -

- - -
- Structural Divisions of Verse Texts -

Like other kinds of text, texts written in verse may be of widely differing lengths and - structures. A complete poem, no matter how short, may be treated as a free-standing text, - and encoded in the same way as a distinct prose text. A group of poems functioning as a - single unit may be encoded either as a group or as a text, depending on - the encoder's view of the text. For further discussion, including an example encoding for a - verse anthology, see chapter .

-

Many poems consist only of ungrouped lines. - - - - - - - - - - - - - - - - - - - - - - - This short poem by Emily - Dickinson is a simple case: - - 1755 - - - To make a prairie it takes a clover and one bee, - One clover, and a bee, - And revery. - The revery alone will do, - If bees are few. - - - - - -

-

Often, however, lines are grouped, formally or informally, into stanzas, verse paragraphs, - etc. The lg element defined in the core tag set (in section ) - may be used for all such groupings. It may thus serve for informal groupings of lines such - as those of the following example from Allen Ginsberg: - - My Alba - - Now that I've wasted - five years in Manhattan - life decaying - talent a blank - - - talking disconnected - patient and mental - sliderule and number - machine on a desk - - - - - - -

-

It may also be used to mark the verse paragraphs into which longer poems are often divided, - as in the following example from Samuel Taylor Coleridge's Frost at - Midnight: - The Frost performs its secret ministry, - Unhelped by any wind. ... - Whose puny flaps and freaks the idling Spirit - By its own moods interprets, every where - Echo or mirror seeking of itself, - And makes a toy of Thought. - - - But O! how oft, - How oft, at school, with most believing mind - Presageful, have I gazed upon the bars, - To watch that fluttering stranger! ... - - - Dear Babe, that sleepest cradled by my side, - - Note, in the above example, - the use of the part attribute on the l element, where a verse line is - broken between two line groups, as discussed in section .

-

Most typically, however, the lg element is used to mark the highly regular line - groups which characterize stanzaic and similar verse forms, as in the following example - from Chaucer: - Sire Thopas was a doghty swayn; - White was his face as payndemayn, - His lippes rede as rose; - His rode is lyk scarlet in grayn, - And I yow telle in good certayn, - He hadde a semely nose. - - - His heer, his ber was lyk saffroun, - That to his girdel raughte adoun; - - -

-

Like other text-division elements, lg elements may be nested hierarchically. For - example, one particularly common English stanzaic form consists of a quatrain or sestet - followed by a couplet. The lg element may be used to encode both the stanza and - its components, as in the following example from Byron: - - In the first year of Freedom's second dawn - Died George the Third; although no tyrant, one - Who shielded tyrants, till each sense withdrawn - Left him nor mental nor external sun: - A better farmer ne'er brushed dew from lawn, - A worse king never left a realm undone! - - - He died — but left his subjects still behind, - One half as mad — and t'other no less blind. - - - -

-

Note the use of the type attribute to name the type of unit encoded by the - lg element; this attribute is common to all members of the att.divLike class (see section ).For discussion of other attributes of this class, see . - When used on lg, the type attribute is intended solely for conventional - names of different classes of text block. For systematic analysis of metrical and rhyme - schemes, use the met and rhyme attributes, for which see below, - section .

-

As a further example, consider the Shakespearean sonnet. This may be divided into two - parts: a concluding couplet, and a body of twelve lines, itself subdivided into three quatrains: - - - - - - - - My Mistres eyes are nothing like the Sunne, - Currall is farre more red, then her lips red - If snow be white, why then her brests are dun: - If haires be wiers, black wiers grown on her head: - - - I have seene Roses damaskt, red and white, - But no such Roses see I in her cheekes, - And in some perfumes is there more delight, - Then in the breath that from my Mistres reekes. - - - I love to heare her speake, yet well I know, - That Musicke hath a farre more pleasing sound: - I graunt I never saw a goddesse goe, - My Mistres when shee walkes treads on the ground. - - - - And yet by heaven I think my love as rare, - As any she beli'd with false compare. - - - - -

-

Particularly lengthy poetic texts are often subdivided into units larger than stanzas or - paragraphs, which may themselves be subdivided. Spenser's Faery Queene, for - example, consists of twelve books each of which contains a prologue - followed by twelve cantos. Each prologue and each canto consists of - nine-line stanzas, each of which follows the same regular pattern. - Other examples in the same tradition are easy to find.

- -

Large structures of this kind are most conveniently represented by div or - div1 elements, as described in section . Thus the start - of the Faerie Queene might be encoded as follows: -

-
- - A Gentle Knight was pricking on the plain - Y cladd in mightie armes and silver shielde, - -
-
- The encoder must choose at which point in the hierarchy of structural - units to introduce lg elements rather than a yet smaller div element: it - would (for example) also be possible to encode the above example as follows: -
-
-
- A gentle knight was pricking on the plain - Ycladd in mightie armes and silver shielde, -
-
-
-

- -

One reason for using div rather than lg elements is that the former may - contain non-metrical elements, such as epigraphs or dedications and other members of the - model.divTop class, whereas lg elements may contain - only headings or metrical lines.

-
-
- Components of the Verse Line -

It is often convenient for various kinds of analysis to encode subdivisions of verse lines. - The general purpose seg element defined in the tag set for segmentation and - alignment (section ) is provided for this purpose: - -

-

To use this element together with the module for verse, the module for segmentation and - alignment must also be enabled as further described in section .

-

In Old and Middle English alliterative verse, individual verse lines are typically split - into half lines. The seg element may be used to mark these explicitly, as in the - following example from Langland's Piers Plowman: In a somer - seson, - whan softe was the sonne, - I shoop me into shroudes - as I a sheep were, - In habite as an heremite - unholy of werkes, - Went wide in this world - wondres to here. - -

-

The seg element can be nested hierarchically, in the same way as the lg - element, down to whatever level of detailed structure is required. In the following - example, the line has been divided into feet, each of which has been further - subdivided into syllables.As elsewhere in these Guidelines, this - example has been formatted for clarity of exposition rather than correct display. Note - in particular that whether an XML processor retains whitespace within the seg - element or not (this can be configured by means of the xml:space attribute) - this example will still require additional processing, since whitespace should be - retained for the lower level seg elements (those of type syll) but - not for the higher level one (those of type foot). - - Arma vi - rumque ca - no Tro - iae qui - primus ab - oris - -

-

The seg element may be used to identify any subcomponent of a line which has - content; its type attribute may characterize such units in any way appropriate to the needs - of the encoder. For the specific case of labeling each foot with its formal type - (dactyl, spondee, etc.), and each syllable with its metrical or prosodic - status (syllables bearing primary or secondary stress, long syllables, short syllables), - however, the specialized attributes met and real are defined, which - provide a more systematic framework than the type attribute; see section below.

-

In classical verse, a hexameter like that above may also be formally divided into two - cola or hemistiches. This example provides a typical - case, in that the boundary of the first colon falls in the middle of one of the feet - (between the syllables no and Tro). If both kinds of segmentation are - required, the part attribute might be used to mark the overlapping structure as - follows. - - - Ar - ma - vi - - - rum - que - ca - - - no - - - - - Tro - - - iae - qui - - - -

-

Instead of using the part attribute on the seg element, it might be - simpler just to mark the point at which the caesura occurs. An additional element is - provided for analyses of this kind, in which what is to be marked are points between the - words, which have some significance within a verse line: - - In classical prosody, the caesura, which occurs within a foot, is - distinguished from a diaeresis, which occurs on a foot boundary (not to be - confused with the division of a diphthong into two syllables, or the diacritic symbol used - to indicate such division, each of which is also termed diaeresis). This - distinction is rarely made nowadays, the term caesura being used for - any division irrespective of foot boundaries. No special-purpose diaeresis element is therefore provided.

-

As an example of the caesura element, we refer again to the example from Langland. - An encoder might choose simply to record the location of the caesura within each line, - rather than encoding each half-line as a segment in its own right, as follows: In a somer seson, - whan softe was the sonne, - I shoop me into shroudes as I a sheep were, - In habite as an heremite unholy of werkes, - Went wide in this world wondres to here. -

-

Logically, the opposite of caesura might be considered to be enjambement. When - the verse module is included in a schema, an additional class - called att.enjamb is defined as follows: - - The following lines demonstrate the use of the enjamb attribute to - mark places where there is a discrepancy between the boundaries of the l elements - and the syntactic structure of the verse (a discrepancy of some significance in some - schools of verse): Un astrologue, un jour, se laissa choir - Au fond d'un puits. - - - - - -

-
-
- Encoding Textual Structures Across Verses -

It is possible that certain textual structures may span multiple lines of verse, either by - incorporating more than one, or by crossing line hierarchy. This is common, - for example, when lines contain reported thought or speech (i.e. said), - or other forms of quotation (i.e. q). For these cases, it is recommended practice - to fragment and reconstruct the elements representing the textual structures. -

-

The following example from Margaret Cavendish's Nature's Pictures shows speech - encoded across two lines reconstructed by chaining elements with prev and - next attributes: - - Our lives, ſaid he, - wee'll give before we yield, - - - Wee'll win your battles, or dye in the field. - - -

-

Alternatively, the elements may be reconstructed with stand-off markup using the element join: - - - Our lives, ſaid he, - wee'll give before we yield, - - - Wee'll win your battles, or dye in the field. - - - -

- -

- -

-

- A more general discussion of these and other strategies to deal with fragmentation and reconstruction - appears in section . -

-
-
- Rhyme and Metrical Analysis -

When the module for verse is in use, the following additional attributes are available to - record information about rhyme and metrical form: - - -

-

These attributes may be attached to the lg element, or to the higher-level - text-division elements div, div1, etc. In general, the attributes should - be specified at the highest level possible; they may not however be specifiable at the - highest level if some of the subdivisions of a text are in prose and others in verse. All - these attributes may also be attached to the l and seg elements, but the - default notation for the rhyme attribute has no defined meaning when specified - on l or seg. The value for these attributes may take any form desired by - the encoder, but the nature of the notation used will determine how well the attribute - values can be processed by automatic means.

-

The primary function of the metrical attributes is to encode the conventional metrical or - rhyming structure within which the poet is working, rather than the actual prosodic - realization of each line; the latter can be recorded using the real attribute, - as further discussed below. A simple mechanism is also provided for recording the actual - realization of a rhyme pattern; see .

-
- Sample Metrical Analyses -

As a simple example of the use of these attributes, consider the following lines from - Pope's Essay on Criticism:

- - 'Tis hard to say, if greater Want of Skill - Appear in Writing or in Judging ill; - But, of the two, less dang'rous is th'Offence, - To tire our Patience, than mis-lead our Sense: - -
- -

-

This text is written entirely in heroic couplets; each line is an iambic - pentameter (which, using a common notation, can be described with the formula - -+|-+|-+|-+|-+/, each - denoting a metrically unstressed - syllable, each + a metrically stressed one, each | a foot - boundary, and the / a line-end), and the couplets rhyme (which can be - represented with the conventional formula aa).

-

Because both rhyme pattern and metrical form are consistent throughout the poem, they - may be conveniently specified on the div element; the values given for the - attributes will be inherited by any metrical unit contained within the div - elements of this poem, and must be interpreted in the appropriate way.

-

Since the notation used in the met, real, and rhyme - attributes is user-defined, no binding description can be given of its details or of how - its interpretation must proceed. (A default notation is provided for the - rhyme attribute, which however the encoder can replace with another; see - section .) It is expected, however, that software should be able to - support these attributes in useful ways; the more intelligent the software is, and the - more knowledge of metrics is built into it, the better it will be able to support these - attributes. In the extract given above, for example, the met and - rhyme attribute values specified on the div element are inherited - directly by the lg elements nested within it. Since the met value - specifies the metrical form of a single verse line, the structure of the lg as - a whole is understood to involve as many repetitions of the pattern as there are lines - in the verse paragraph. The same attribute value, when inherited in turn by the - l element, must be understood not to repeat. With sufficiently - sophisticated software, segments within the line might even be understood as inheriting - precisely that portion of the formula which applies to the segment in question; this - will, however, be easier to accomplish for some languages than for others.

-

The rhyme attribute in this example uses the default notation to specify a - rhyme scheme applicable only to pairs of lines. As elsewhere, the default notation for - the rhyme attribute has no meaning for metrical units at the line level or - below. In verse forms where line-internal rhyme is structurally significant, e.g. in - some skaldic poetry, the default notation is incapable of expressing the required - information, since the rhyme pattern may need to be specified for units smaller than the - line. In such cases, a user-specified rhyme notation must be substituted for the default - notation, or else the rhyme pattern must be described using some alternative method - (e.g. by using the link mechanism described below).

-

The precise semantics of the met attribute and the inferences which software - is expected or able to draw from it, are implementation-dependent; so are the semantics - and processing of the rhyme attribute, when user-specified notations are - used.

-

A formal definition of the significance of each component of the pattern given as the - value of the met attribute may be provided in the metDecl element - within the encodingDesc element in the TEI header (see section ). The encoder is free to invent any notation appropriate to his or - her analytic needs, provided that it is adequately documented in this element. The - notation may define metrical components using invented or traditional names (such as - iamb or hexameter) or in terms of basic units such as codes for - stressed or unstressed syllables, or a combination of the two.

-

The real (for realization) attribute may optionally be specified to - indicate any deviation from the pattern defined by the met attribute which - the encoder wishes to record. By default, the real attribute has the same - value as the met attribute on the same element; it is only necessary to - provide an explicit value when the realization differs in some way from the abstract - metrical pattern. The tension between conventional metrical pattern and its realization - may thus be recorded explicitly. For example, many readers of the above passage would - stress the word But at the beginning of the third line rather than the word - of following it, as the metrical pattern would normally require. This - variation might be encoded as follows: - - But, of the two, ... - -

-

Where the real attribute is used to over-ride the default or conventional - metrical pattern, it applies only to the element on which it is specified. The default - pattern for any subsequent lines is unaffected.

-

As it happens, this particular kind of variation is very common in the English iambic - pentameter—it even has a name: trochaic substitution—an encoder might - therefore - - choose to regard this not as an - instance of a variant realization, but as an instance of a variant metrical form: - - But, of the two, ... - Alternatively, a different metrical notation might be defined, in - which this kind of variation was permitted throughout the text.

-

In choosing whether to over-ride a metrical specification in this way or by using the - real attribute, the encoder is required to determine whether the change is - a systematic or conventional one (as in this example) or an occasional variation, - perhaps for local effect. In the following example, from Goethe's Auf - dem See, the variation is a matter of local realization: - - - - Und frische Nahrung, neues Blut - Saug' ich aus freier Welt; - Wie ist Natur so hold und gut, - Die mich am Busen hält! - Die Welle wieget unsern Kahn - Im Rudertakt hinauf, - Und Berge, wolkig himmelan, - Begegnen unserm Lauf. - On the other hand, the famous inserted alexandrine in Pope's Essay - on Criticism, might be encoded as follows: A - needless alexandrine ends the song, - That, like a wounded - snake, drags its slow length along. - - Here the - met attribute indicates that a different metrical convention (the - alexandrine) is in force, while the real attribute indicates that there is a - variation from that convention. As with many other aspects of metrical analysis, - however, this is of necessity an entirely interpretive judgment.

-
-
- Segment-Level versus Line-level Tagging -

The examples given so far have encoded information about the realization of metrical - conventions at the level of the whole verse-line. This has obvious advantages of - simplicity, but the disadvantage that any deviation from metrical convention is not - marked at its precise point of occurrence in the text. Greater precision may be - achieved, but only at the cost of marking deviant metrical units explicitly. This may be - done with the seg element, giving the variant realization as the value of the - real attribute on that element. Using this method, the example given - immediately above might be encoded as follows: A needless alexandrine ends the song, - - That, like a wounded snake, - drags its - slow length along. The marking of the - foot boundaries with the symbol | in the met attribute value of - the l element allows the human reader, or a sufficiently intelligent software - program, to isolate the correct portion of that attribute value as the default value for - the same attribute on the seg elements for feet, namely -+. It is of - course up to the encoder to decide whether or not to include the n attribute - of seg here, and whether or not also to tag the feet in the line in which there - is no deviation from the metrical convention. The ability of software to infer which - foot is being marked, if not all are tagged, will depend heavily on the language of the - text and the knowledge of prosody built into the software; the fuller and more explicit - the markup, the easier it will be for software to handle it. It may prove useful, - however, to mark metrical deviations in the manner shown, even if the available software - is not sufficiently intelligent to scan lines without aid from the markup. Human readers - who are interested in prosody may well be able to exploit the markup in useful ways even - with less sophisticated software.

-

There are circumstances where it may also be useful to use the met attribute - of seg. If we wish to identify the exact location of the different types of - foot in the first line of Virgil's Aeneid, the text could be encoded as - follows (for simplicity's sake the caesura has been omitted): Arma vi - rumque ca - no Tro - iae qui - primus ab - oris - An appropriate value of the met attribute might also be - supplied on the enclosing div element, to indicate that each foot may be made - up of a dactyl or a spondee, so that the values given here for met at the - level of the foot may be considered a series of local variations on this fundamental - pattern; in cases like this, of course, the local variations may also be considered - aspects of realization rather than of convention, in which case the real - attribute may be used instead of met, if desired.

-
-
- Metrical Analysis of Stanzaic Verse -

The method described above may be used to encode quite complex verse forms, for instance - various kinds of fixed-form stanzas. Let us take one of Dante's canzoni, in which each - stanza except the last has the same combination of eleven-syllable and seven-syllable - lines, and the same rhyme scheme:

- - Doglia mi reca nello core ardire - -
-

-

Here the met attribute specifies a metrical pattern for each of the - twenty-one lines making up a stanza of the canzone. Each stanza inherits - this definition from the parent div element. The rhyme attribute - specifies a rhyme scheme for each stanza, in the same way.

-

In the metrical notation used here, the letter E represents a line containing - nine syllables which may or may not be metrically prominent, a tenth which is prominent - and an optional non-prominent eleventh syllable. The letter S is used to - represent a line containing five syllables which may or may not be metrically prominent, - a sixth which is prominent and an optional non-prominent seventh syllable. A suitable - definition for this notation might be given by a metDecl element like the - following: - - - xxxxxxxxx+o - xxxxx+o - metrically prominent or non-prominent - metrically prominent - optional non prominent - line division - - -

-

As noted above, the metrical pattern specified on the div applies to each - lg (stanza) element contained within the div. In fact however, - after seven stanzas of this type, there is a final stanza, known as a - commiato or envoi, which follows a different metrical and rhyming - scheme. The solution to this problem is simply to specify a new met attribute - on the eighth stanza itself, which will override the default value inherited from parent - div, as follows:

- - ... - - - Canzone, presso di qui è une donna - -

-

Note that, in the same way as for the real attribute, over-riding of this - kind does not affect subsequent elements at the same hierarchic level. Any lg - element following the commiato above would be assumed to use the same - metrical and rhyming scheme as the one preceding the commiato. Moreover, - although it is quite regular (in the sense that the last stanza of each - canzone is a commiato), the over-riding must be specified - for each case.

-
-
-
- Rhyme - -

The rhyme attribute is used to specify the rhyme pattern of a verse form. It - should not be confused with the rhyme element, which is used to mark the actual - rhyming word or words: - -

- -

Like the met attribute, the rhyme attribute can be used with a - user-specified notation documented by the metDecl element in the TEI header. - Unlike met, however, the rhyme attribute has a default notation; if - this default notation is used, no metDecl element need be given.

-

The default notation for rhyme offers the ability to record patterns of rhyming lines, - using the traditional notation in which distinct letters stand for rhyming lines. For a - work in rhyming couplets, like the Pope example above, the rhyme attribute - simply specifies aa, indicating that pairs of adjacent lines rhyme with each - other. For a slightly more complex scheme, applicable to groups of four lines, in which - lines 1 and 3 rhyme, as do lines 2 and 4, this attribute would have the value - abab. The traditional Spenserian stanza has the pattern ababbcbcc, - indicating that within each nine line stanza, lines 1 and 3 rhyme with each other, as do - lines 2, 4, 5 and 7, and lines 6, 8 and 9.

-

Non-rhyming lines within such a group may be represented using a hyphen or an x, as in the - following example: - - Why, all the Saints and Sages who discuss'd - Of the Two Worlds so learnedly, are thrust - Like foolish Prophets forth; their Words to Scorn - Are scatter'd, and their Mouths are stopt with Dust. - -

-

The rhyme element may be used to mark the words (or parts of words) which rhyme - according to a predefined pattern: - Outside in the distance a wildcat did growl - Two riders were approaching and the wind began to howl - - -

-

The label attribute is used to specify which parts of a rhyme scheme a given set - of rhyming words represent: - I wander thro' each charter'd street, - Near where the charter'd Thames does flow, - And mark in every face I meet - Marks of weakness, marks of woe. - - In every cry of every Man - In every Infant's cry of fear, - In every voice, in every ban, - The mind-forg'd manacles I hear. - -

-

Within a given scope, all rhyme elements with the same value for their - label attribute are assumed to rhyme with each other: thus, in the above - example, the two rhymes labelled a in the first stanza rhyme with each other, - but not necessarily with those labelled a in the second stanza. The scope is - defined by the nearest ancestor element for which the rhyme attribute has been - supplied.

- -

The rhyme element can appear anywhere within a verse line, and not necessarily - around a single word. It can thus be used to mark quite complex internal rhyming schemes, - as in the following example: - The sunlight on the garden - Hardens and grows cold, - We cannot cage the minute - Within its nets of gold - When all is told - We cannot beg for pardon. - - -

-

This mechanism, although reasonably simple for simple cases, may not be appropriate for - more complex applications. In general, rhyme may be considered as a special form of - correspondence, and hence encoded using the mechanisms defined for - that purpose in section . Similar considerations apply to other - metrical features such as alliteration or assonance.

-

To use the correspondence mechanisms to represent the complex rhyming pattern of the above - example, each rhyme element must be given a unique identifier, as follows: - The sunlight on the garden - Hardens and grows cold, - We cannot cage the minute - Within its nets of gold - When all is told - We cannot beg for pardon. - - Now that each rhyming word, or part-word, has been tagged and allocated an - arbitrary identifier, the general purpose link element may be used to indicate - which of the rhyme elements share the same rhyme, as follows: - - - - - -

-

For further discussion of the link and linkGrp element, see section .

-

The rhyme and caesura phrase level elements are made available by the - model.lPart class when the module defined by this chapter is - included in a schema.

-
- -
- Metrical Notation Declaration -

When the module defined in this chapter is included in a schema, a specialized element is - optionally available in the encodingDesc element of the TEI header to document the - metrical notation used in marking up a text. - - -

-

As with other components of the header, metrical notation may be specified either formally - or informally. In a formal specification, every symbol used in the metrical notation must - be documented by a corresponding metSym element; in an informal one, only a brief - prose description of the way in which the notation is used need be given. In either case, - the optional pattern attribute may be used to supply a regular expression which - a processor can use to validate expressions in the intended notation. The following - constraints apply: - if pattern is supplied, any notation used which does not conform to it - should be regarded as invalid - if any metSym is defined, then any notation using undefined symbols - should be regarded as invalid - if both pattern and symbol are defined, then every symbol appearing explicitly - within pattern must be defined - symbols which are not matched by pattern may be defined within a - metDecl element -

-

As a simple example, consider the case of the notation in - which metrical prominence, metrical feet, and line boundaries - are all to be encoded. Legal specifications in this notation may - be written for any sequence of metrically prominent or - non-prominent features, optionally separated by foot or metrical - line boundaries at arbitrary points. Assuming that the symbol - 1 is used for metrical prominence, - 0 for non-prominence, - | for foot boundary and - / for line boundary, then the following - declaration achieves this objective: - - - metrical prominence - metrical non-prominence - foot boundary - metrical line boundary - - -

-

The same notation might also be specified less formally, as follows: - - -

Metrically prominent syllables are marked '1' and other - syllables '0'. Foot divisions are marked by a vertical bar, - and line divisions with a solidus.

-

This notation may be applied to any metrical unit, of any - size (including, for example, individual feet as well as - groups of lines).

- - - Note that in this case, because the pattern attribute has - not been supplied, no processor can validate met attribute values within the - text which use this metrical notation.

-

For more complex cases, it will often be more convenient to - define a notation incrementally. The terminal - attribute should be used to indicate for a given symbol whether - or not it may be re-defined in terms of other symbols used - within the same notation. For example, here is a notation for - encoding classical metres, in which symbols are provided for the - most common types of foot. These symbols are themselves - documented within the same notation, in terms of more primitive - long and short syllables: - - - -oo - -o - o- - -- - ooo - oo- - short syllable - long syllable - - - Note here the use of the global n attribute to supply - an additional name for the symbols being documented.

- -

Where an encoder wishes to use more than one different - pattern for metrical notation, multiple metDecl - elements may be included in the encodingDesc, each - supplied with an xml:id. The decls - attribute may be used in the text of the document to specify - which metDecl is in force at a particular point in the - text. In this example, two metDecls are defined in the - header, one with an English verse pattern and one with a French - pattern. In the body of the document, there are two div - elements, one declaring the English pattern and one the - French: - - - - - stressed syllable - unstressed syllable - metrical line boundary - - - syllabe tonique - syllabe atone - pause métrique - - - - - -

- - - - -
-
- - - - -
- - -

- - - - -
- -
- Encoding Procedures for Other Verse Features -

A number of procedures that may be of particular concern to encoders of verse texts are - dealt with elsewhere in these guidelines. Some aspects of layout and physical appearance, - especially important in the case of free verse, are dealt with in chapter . Some initial recommendations for the encoding of phonetic or prosodic transcripts, - which may be helpful in the analysis of sound structures in poetry, are to be found in - chapter ; it may also be found convenient to use standard entity names - (those proposed for the International Phonetic Alphabet suggest themselves) to mark - positions of suprasegmentals such as primary and secondary stress, or other aspects of - accentual structure.

- -

As already indicated, chapter contains much which will be found useful - for the aligning of multiple levels of commentary and structure within verse analysis. - Encoders of verse (as of other types of literary text) will frequently wish to attach - identifying labels to portions of text that are not part of a system of hierarchical - divisions, may overlap with one another, and/or may be discontinuous; for instance passages - associated with particular characters, themes, images, allusions, topoi, styles, or modes - of narration. Much of the computerized analysis of verse seems likely to require dividing - texts up into blocks in this way. The span element discussed in provides the means for doing this. Finally, the procedures for the - tagging of feature structures, described in chapter , provide a powerful - means of encoding a wide variety of aspects of verse literature, including not only the - metrical structures discussed above, but also such stylistic and rhetorical features as - metaphor.

-

For other features it must for the time being be left to encoders to devise their own - terminology. Elements such as metaphor tenor="..." vehicle="..." ... - /metaphor might well suggest themselves; but given the problems of definition - involved, and the great richness of modern metaphor theory, it is clear that any such - format, if predefined by these Guidelines, would have seemed objectionable to some and - excessively restrictive to many. Leaving the choice of tagging terminology to individual - encoders carries with it one vital corollary, however: the encoder must be utterly - explicit, in the TEI header, about the methods of tagging used and the criteria and - definitions on which they rest. Where no formal elements are currently proposed, such - information may readily be given as simple prose description within the - encodingDesc element defined in section .

-
- -
- Module for Verse -

The module described in this chapter makes available the - following components: - - Verse - Verse structures - Poésie - 韻文結構 - Strutture poetiche - Estrutura dos versos - 韻文モジュール - - - The selection and combination of modules to form a TEI schema - is described in .

- - - - - - -
-
\ No newline at end of file diff --git a/P5/Source/Guidelines/fr/VE-Verse.xml b/P5/Source/Guidelines/fr/VE-Verse.xml new file mode 120000 index 0000000000..50ee373466 --- /dev/null +++ b/P5/Source/Guidelines/fr/VE-Verse.xml @@ -0,0 +1 @@ +../en/./VE-Verse.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/WD-NonStandardCharacters.xml b/P5/Source/Guidelines/fr/WD-NonStandardCharacters.xml deleted file mode 100644 index ed1ec4eb83..0000000000 --- a/P5/Source/Guidelines/fr/WD-NonStandardCharacters.xml +++ /dev/null @@ -1,1329 +0,0 @@ - - - - -
-Characters, Glyphs, and Writing Modes - - -

Chapter introduced the fundamental notions of -language identification and character representation in an encoded TEI -document. In this chapter we discuss some additional issues relating -to the way that written language is represented in a TEI document. In -sections and we -introduce markup which may be used to represent and document -non-standard characters, that is, written symbols for which no -codepoint exists in Unicode. The same markup may be used to annotate -existing characters according to their visual or other properties, and -thus process them as distinct glyphs (see section ), or to define new characters or glyphs (section -). We also provide recommendations concerning -the Unicode Private Use Area (. Finally, in -section we -discuss ways of documenting the writing mode used in a source text, -that is, the directionality of the script, the orientation of -individual characters, and related questions.

- - - -
Is Your Journey Really Necessary? -

Despite the availability of Unicode, text encoders still -sometimes find that the published repertoire of available -characters is inadequate to their needs. This is particularly the -case when dealing with ancient languages, for which encoding -standards do not yet exist, or where an encoder wishes to -represent variant forms of a character or glyphs. -The module defined by this chapter provides a mechanism to satisfy -that need, while retaining compatibility with standards. -

-

When encoders encounter some graphical unit in a document which is -to be represented electronically, the first issue to be resolved -should be Is this really a different character? To determine -whether a particular graphical unit is a character or -not, see .

-

If the unit is indeed determined to be a character, the next -question should be Has this character been encoded already? -In order to determine whether a character has been encoded, -encoders should follow the following steps: - -

Check the Unicode - web site at , in particular the page "Where is my - Character?", and the associated character code charts. - Alternatively, users can check the latest published version of - The Unicode Standard (Unicode Consortium (2006)), though the web site is - often more up to date than the printed version, and should be - checked for preference.

-

The pictures (glyphs) in the Unicode code -charts are only meant to be representative, not definitive. If a -specific form of an already encoded character is required for a -project, refer to the guidelines contained below under Annotating Characters. Remember that your -encoded document may be rendered on a system which has different fonts -from yours: if the specific form of a character is important to you, -then you should document it.

- Check the Proposed New Characters web page () to see whether - the character is in line for approval. - -Ask on the Unicode email list () to -see whether a proposal is pending, or to determine whether this -character is considered eligible for addition -to the Unicode Standard. - -

-

Since there are now over 130,000 characters in Unicode, -chances are good that what you need is already there, but it might -not be easy to find, since it might have a different name in -Unicode. Editors working with East Asian writing systems should consult -the Unihan Database. -Look again, this time at other sites, preferably ones which also provide searches based on scripts and languages. For example (for CJK characters) or (for non-CJK characters) . -Take care, however, that all the -properties of what seems to be a relevant character are consistent -with those of the character you are looking for. For example, if -your character is definitely a digit, but the properties of the -best match you can find for it say that it is a letter, you may -have a character not yet defined in Unicode.

-

In general, it is advisable to avoid Unicode characters generally -described as presentation forms.Specifically, -characters in the Unicode blocks Alphabetic Presentation Forms, Arabic Presentation Forms-A, Arabic Presentation Forms-B, Letterlike Symbols,and Number Forms. However, if the character you are looking for is being used in a notation (rather than as part of the orthography of a language) then it is quite acceptable to select characters from the Mathematical Operators block, provided that they have the appropriate properties (i.e. So: Symbol, Other; or Sm: -Symbol, Math).

-

An encoded character may be precomposed or it may be formed -from base characters and combining diacritical marks. Either will -suffice for a character to be "found" as an encoded character. If there are several possible Unicode characters to choose amongst, -it is good practice to consult other colleagues and practitioners to -see whether a consensus has emerged in favour of one or other of -them.

-

If, however, no suitable form of your character seems to exist, the -next question will be: Does the graphical unit in question -represent a variant form of a known character, or does it represent a -completely unencoded character? If the character is determined to -be missing from the Unicode Standard, it would be helpful to submit -the new character for inclusion (see ). For assistance -on writing or submitting a proposal, potential proposers can contact -the UC Berkeley Script Encoding Initiative ().

-

These guidelines will help you proceed once you have - identified a given graphical unit as either a variant or an - unencoded character. Determining this will require knowledge of - the contents of the document that you have. The first case will - be called annotation of a character, while the - second case will be called adding of a new - character. How to handle graphical units that represent variants - will be discussed below () - while the problem of representing new characters will be dealt - with in section .

-

While there is some overlap between these requirements, -distinct specialized markup constructs have been created for each -of these cases. These constructs are presented in section -below.

-
-
- -Markup Constructs for Representation of Characters and Glyphs -

An XML document can, in principle, contain any defined Unicode -character. The standard allows these characters to be represented -either directly, using an appropriate encoding (UTF-8 by default), or -indirectly by means of a numeric character reference (NCR), such as -&#196; (A-umlaut). The encoder can also restrict the -range of characters which are represented directly in a document (or -part of it) by adding a suitable encoding declaration. For example, if -a document begins with the declaration <?xml -encoding="iso-8859-1"?> any Unicode characters which are not -in the ISO-8859-1 character set must be represented by NCRs.

-

The gaiji module defined by this - chapter adds a further way of representing specific characters - and glyphs in a document. (Gaiji is from Japanese 外字, meaning external - characters.) This allows the encoder to distinguish - characters and glyphs which Unicode regards as identical, to add - new nonstandard characters or glyphs, and to represent Unicode - characters not available in the document encoding by an - alternative means.

-

The mechanism provided here consists functionally of two parts: - - an element g, which serves as a proxy for new - characters or glyphs - elements char and glyph, providing information about such characters or glyphs; these elements are stored in the - charDecl element in the header. - -

-

When the gaiji module is included in a schema, the -charDecl element is added to the model.encodingDescPart -class, and the g element is added to the phrase class. These -elements and their components are documented in the rest of this -section.

-

The Unicode standard defines properties for all the characters it -defines in the Unicode Character Database , knowledge of which is usually built into text processing systems. If the -character represented by the g element does not exist in Unicode at -all, its properties are not available. If the character represented is -an existing Unicode character, but is not available in the document -character set recognized by a given text processing system, it may -also be convenient to have access to its properties in the same way. -The char element makes it possible to store properties -for use by such applications in a standard way.

-

The list of attributes (properties) for characters is modelled on -those in the Unicode Character Database, which distinguishes -normative and informative character -properties. The Unicode Consortium also maintains a separate set of character properties specific to East Asian characters in the Unihan database which TEI fully supports. Lastly, non-Unicode properties may also be supplied. -Since the list of properties will vary with different versions of the -Unicode Standard, there may not be an exact correspondence between -them and the list of properties defined in these Guidelines.

- -

Usage examples for these elements are given below at and . The gaiji module -itself is formally defined in section -below. It declares the following additional elements: - - - - -The charDecl element is a member of the class model.encodingDescPart, and thus becomes -available within encodingDesc when this module is included in -a schema. The g element is the only member of the class -model.gLike: this class is referenced as -an alternative to plain text in almost every element which contains -plain text, thus permitting the g element also to appear at -such places when this module is included in a schema. -

-

The following elements may appear within a charDecl - element: - - - - - -

-

The char and glyph elements have similar contents -and are used in similar ways, but their functions are different. The -char element is provided to define a character which is not -available in the current document character set, for whatever reason, -as stated above. The glyph element is used to annotate a -character that has already been defined somewhere (either in the -document character set, or through a char element) by -providing a specific glyph that shows how a character appeared in the -original document. This is necessary since Unicode code points refer -not to a single, specific glyph shape of a character, but rather to a -set of glyphs, any of which may be used to render the code point in -question; in some cases they can differ considerably.

-

The glyph element is provided for cases where the encoder -wants to specify a specific glyph (or family of glyphs) out of all -possible glyphs. Unfortunately, due to the way Unicode has been -defined, there are cases where several glyphs that logically belong -together have been given separate code points, especially in the blocks -defining East Asian characters. In such cases, glyph elements -can also be used to express the view that these apparently distinct -characters are to be regarded as instances of the same character (see -further ).

-

The Unicode Standard recommends naming conventions which should be -followed strictly where the intention is to annotate an existing -Unicode character, and which may also be used as a model when -creating new names for characters or glyphsIt should be noted, however, that this naming convention cannot meaningfully be applied to East Asian characters; the typical Unicode descriptions for these characters take the form CJK Unified Ideograph U+4E00, where U+4E00 is simply the Unicode code point value of the character in question. In cases where no Unicode code point exists, there is little hope of finding a name that helps to identify the character. Names should therefore be constructed in a way meaningful to local practice, for example by using a reference number from a well-known character dictionary or a project-specific serial number.:

-

Within both char and glyph, the following elements are available: - - - - - - - - - - -

- -

Four of these elements (gloss, desc, -figure, and note) are defined by other TEI -modules, and their usage here is no different from their usage -elsewhere. The figure element, however, is used here only to -link to an image of the character or glyph under discussion, or to -contain a representation of it in SVG. The figure element may -contain more than one graphic -element, for example to provide images with different -resolution, or in different formats, or may itself be repeated. As -elsewhere, the mimeType attribute -of graphic should be used to specify -the format of the image.

-

The mapping element is similar to the standard TEI -equiv element. While the latter is used to express -correspondence relationships between TEI concepts or elements and -those in other systems or ontologies, the former is used to express -any kind of relationship between the character or glyph under -discussion and characters or glyphs defined elsewhere. It may contain -any Unicode character, or a g element linked to some other -char or glyph element, if, for example, the -intention is to express an association between two non-standard -characters. The type of association is indicated by the -type attribute, which may take such values as -exact for exact equivalences, uppercase for -uppercase equivalences, lowercase for lowercase -equivalences, standard for standardized forms, and -simplified for simplified characters, etc., as in the -following example: - - - -a - - - -

-

The mapping element may also be used to represent a mapping of the -character or (more likely) glyph under discussion onto a character -from the private use area as in this example: - - - -Z -U+E304 - - - -

-

A more precise documentation of the properties of any character or -glyph may be supplied using one of the three property elements: localProp, unicodeProp, or unihanProp; these are described in the next section.

-
Character Properties -

The Unicode Standard documents ideal -characters, defined by reference to a number of -properties (or attribute-value pairs) which they are said -to possess. For example, a lowercase letter is said to have the value -Ll for the property General_Category. The -Standard distinguishes between normative properties -(i.e. properties which form part of the definition of a given -character), and informative or additional -properties which are not normative. It also allows for the addition of -new properties, and (in some circumstances) alteration of the values -currently assigned to certain properties. When making such -modifications, great care should be taken not to override standard -informative properties for characters which already exist in the Unicode -Standard, as documented in Freytag (2006).

- -

The unicodeProp, unihanProp, and -localProp elements allow a TEI encoder to record information -about a character or glyph: - - - - - -

-

Where the information concerned relates to a property which has -already been identified in the Unicode Standard, use of the -appropriate Unicode property name with unicodeProp is -strongly encouraged. The use of available Unihan property names with -unihanProp is similarly encouraged. Validation rules for -property names according to Unicode conventions -are incorporated into the TEI schemas. Where neither of these -standards suffices use localProp.

- -

The three elements for recording Unicode or locally defined properties belong to the att.gaijiProp class. This class defines two required attributes for record key-value pairs for character properties: - - - - -For each property, the encoder must supply both a -name and a value. In cases of boolean properties TEI requires an explict true or false value attribute: - - - -

-

For convenience, we list here some of the normative character -properties and their values. For full information, refer to chapter 4 of The Unicode Standard, or the online documentation of the Unicode Character Database. - - The general - category (described in the Unicode Standard chapter 4 section 5) is an assignment to some - major classes and subclasses of characters. Suggested - values for this property are listed here: - -LuLetter, uppercase -LlLetter, lowercase -LtLetter, titlecase -Lm Letter, modifier -LoLetter, other -MnMark, nonspacing -McMark, spacing combining -MeMark, enclosing -NdNumber, decimal digit -NlNumber, letter -NoNumber, other -PcPunctuation, connector -PdPunctuation, dash -PsPunctuation, open -PePunctuation, close -PiPunctuation, initial quote -PfPunctuation, final quote -PoPunctuation, other -SmSymbol, math -ScSymbol, currency -SkSymbol, modifier -SoSymbol, other -ZsSeparator, space -ZlSeparator, line -ZpSeparator, paragraph -CcOther, control -CfOther, format -CsOther, surrogate -CoOther, private use -CnOther, not assigned -
- - -This property applies to all Unicode characters. It governs the -application of the algorithm for bi-directional behaviour, as further -specified in Unicode Annex 9, The Bidirectional -Algorithm. The following 21 different values are currently -defined for this property: - -LLeft-to-Right -RRight-to-Left -ALRight-to-Left Arabic -ENEuropean Number -ESEuropean Number Separator -ETEuropean Number Terminator -ANArabic Number -CSCommon Number Separator -NSMNonspacing Mark -BNBoundary Neutral -BParagraph Separator -SSegment Separator -WSWhitespace -ONOther Neutrals -LRELeft-to-Right Embedding -LROLeft-to-Right Override -RLERight-to-Left Embedding -RLORight-to-Left Override -PDFPop Directional Format -LRILeft-to-Right Isolate -RLIRight-to-Left Isolate -FSIFirst Strong Isolate -PDIPop Directional Isolate -
 - This - property exists for characters that are not used - independently, but in combination with other characters, for - example the strokes making up CJK (Chinese, Japanese, and Korean) characters. It - records a class for these characters, which is used to - determine how they interact typographically. The following - values are defined in the Unicode Standard: (see Unicode -Character Database: Canonical Combining Class Values); these were taken from version 12.1: - -0Spacing, split, enclosing, reordrant, and Tibetan subjoined -1Overlays and interior -7Nuktas -8Hiragana/Katakana voicing marks -9Viramas -10Start of fixed position classes -199End of fixed position classes -200Below left attached -202Below attached -204Below right attached -208Left attached (reordrant around single base character) -210Right attached -212Above left attached -214Above attached -216Above right attached -218Below left -220Below -222Below right -224Left (reordrant around single base character) -226Right -228Above left -230Above -232Above right -233Double below -234Double above -240Below (iota subscript) -
 - - This property is defined for characters, - which may be decomposed, for example to a canonical form - plus a typographic variation of some kind. For such characters the Unicode standard specifies both - a decomposition type and a decomposition mapping - (i.e. another Unicode character to which this one may be - mapped in the way specified by the decomposition type). The - following types of mapping are defined in the Unicode Standard: - -fontA font variant (e.g. a blackletter form) -noBreakA no-break version of a space or hyphen -initialAn initial presentation form (Arabic) -medialA medial presentation form (Arabic) -finalA final presentation form (Arabic) -isolatedAn isolated presentation form (Arabic) -circleAn encircled form -superA superscript form -subA subscript form -verticalA vertical layout presentation form -wideA wide (or zenkaku) compatibility character -narrowA narrow (or hankaku) compatibility character -smallA small variant form (CNS compatibility) -squareA CJK squared font variant -fractionA vulgar fraction form -compatOtherwise-unspecified compatibility character -
- - This property applies for - any character which expresses any kind of numeric value. Its - value is the intended value in decimal notation. - The mirrored - character property is used to properly render characters such - as U+0028, OPENING PARENTHESIS independent of - the text direction: it has the value Y -(character is mirrored) or N (code is not mirrored). -

-

The Unicode Standard also defines a set of informative (but non-normative) properties for Unicode characters. If encoders wish to provide such properties, they should be included using the Unicode name. If a Unicode name exists for a given character this should always be used, however encoders may also supply locally defined names. To tag a Unicode name, use unicodeProp name="Name" (or unihanProp name="Name"). For names specified elsewhere or specified locally use localProp.

-
-
-
-Annotating Characters -

Annotation of a character becomes necessary when it is desired -to distinguish it on the basis of certain aspects (typically, its -graphical appearance) only. In a manuscript, for example, where -distinctly different forms of the letter r can be recognized, it -might be useful to distinguish them for analytic purposes, quite -distinct from the need to provide an accurate representation of the -page. A digital facsimile, particularly one linked to a -transcribed and encoded version of the text, will always provide a -superior visual representation (for information on how to link a -digital facsimile to a transcribed text see ), but cannot be used to support arguments based -on the distribution of such different forms. Character annotation -as described here provides a solution to this problem. It should be kept in mind that any kind of text -encoding is an abstraction and an interpretation of the text at -hand, which will not necessarily be useful in reproducing an exact -facsimile of the appearance of a manuscript.

- -

Assuming that we wish to distinguish the variant glyphs from the -standard representation for the character concerned, we will need to -define distinct glyph elements, one for each of the forms of -the letter we wish to distinguish: - - - -

- - - - -
- - - With these definitions in place, occurrences of these two special - rs in the text can be represented using the element g: - -

Words in this - manuscript are sometimes - written in a funny way.

-

- As can be seen in this example, the glyph element pointed - to from the g element will be interpreted as an - annotation on the content of the element g. This mechanism - can be used to represent common manuscript abbreviations or ligatures, as in the - following examples: -

... Filthy riches...

- - - -
- - -

... per ardua

- - - -
- - - -(In fact the Unicode Standard does provide a character to represent the - Fi ligature; the encoder may however prefer not to - use it in order to simplify other text processing operations, - such as indexing).

-

With this - markup in place, it will be possible to write programs to analyze - the distribution of the different letters r as well as produce - more faithful renderings of the original. It - will also be possible to produce normalized versions by simply ignoring - the annotation pointed to by the element g. -

-

For brevity of encoding, it may be preferred to predefine -internal entities such as the following: - r' > -r' >]]> -which would enable the same material to be encoded as follows: - Wo&r1;ds in this manusc&r2;ipt are - sometimes written in a funny way.

]]> -

-

The same technique may be used to represent particular -abbreviation marks as well as to represent other characters or -glyphs. For example, if we believe that the r-with-one-funny-stroke is -being used as an abbreviation for receipt, this might be -represented as follows:&r1;]]>

-

Note however that this technique employs markup objects to -provide a link between a character in the document and some -annotation on that character. Therefore, it cannot be used in -places where such markup constructs are not allowed, notably in -attribute values. -

- -

Since the need to use these constructs to annotate or define -characters occurs frequently in Chinese, Korean, and Japanese -documents, here are some issues that are specific to these -documents. There are two slightly different versions of the -problem. In the first case, due to the way Unicode is defined, -there are occasions when more than one glyph is defined for a -character. In such an occasion, one might want to retain the -character as used, but add information in a way so that a -normalizer (for search or indexing operations) could take -advantage of this information. To achieve this, we simply define -within a charDecl element a glyph that has two -mapping elements, as shown here: - - - - 說 - 説 - - - -The first of these mappings, of type Unicode, -simply maps our glyph to the code point where Unicode defined it. -The other one, of type standard, encodes the fact that -in our view, this glyph is a variation of the standard character -given in the content of the element. We could then use this -glyph element's unique identifier u8aaa to -refer to it from within a text as follows. - - 說 - -

-

A slightly different, but related problem occurs when we have -multiple variants, none of which has been defined in Unicode. In -this case, we need to define one as a new character using -char, and the others as glyphs using glyph. - - - - - - - - - - - -The char defines a new character, while the -glyph element then defines a variant glyph of this newly -defined character. Additional properties should be specified in -order to make these both identifiable.

-
- -
-Adding New Characters -

The creation of additional characters for use in text encoding -is quite similar to the annotation of existing characters. The -same element g is used to provide a link from the -character instance in the text to a character definition provided -within the charDecl element. This character definition -takes the form of a char element. The element g -itself will usually be empty, but could contain a code point from -the Private Use Area (PUA) of the Unicode Standard, which is an -area set aside for the very purpose of privately adding new -characters to a document. Recommendations on how to use such PUA -characters are given in the following section.

-

In some circumstances, it may be desirable to provide a single -precomposed form of a character that is encoded in Unicode only as a -sequence of code points. For example, in Medieval -Nordic material, a character looking like a lowercase letter Y with a -dot and an acute-accent above it may be encountered so frequently that -the encoder wishes to treat it as a single precomposed character with -one single coded value. In the -transcription concerned, the encoder enters this letter as -&ydotacute;, which when the -transcription is processed can then be expanded in one of three ways, -depending on the mapping in force. The entity reference might be -translated into the sequence of corresponding Unicode code points -or into some locally-defined PUA character -(say &#xE0A4;) for local -processing only. Both these options have disadvantages; the former -loses the fact that the sequence of composed characters is regarded as -a single object; the second is not reliably portable. -Therefore, the recommended -representation is to use the g element defined by -the module defined in this chapter: . This makes it possible for the encoder to -provide useful documentation for the particular character or glyph so referenced: - - - - &#x0079;&#x0307;&#x0301; - U+E0A4 This - definition specifies the mapping between this composed character - and the individual Unicode-defined code points which make it - up. It also supplies a single locally-defined property - (entity) for the character concerned, the - purpose of which is to supply a recommended character entity name - for the character. -

-

The composition rules for ideographic characters typically require more complex rules than the &ydotacute; above. For these cases Unicode provides dedicated symbols to capture the composition in Ideographic Description Sequences (IDS). Encoders are strongly encouraged to provide IDS for each variant ideograph in the header component of the gaiji module to faciliated greater human and machine readability of rare or unencoded characters, as in the following example: - - - - ⿻人為 - 偽 - - -The composition rules and further examples appear in Chapter 18.2: Ideographic Description Characters of the Unicode Standard. Editors should be aware that different sequences can accurately describe the same character. In the example, the character "人" (U+4EBA) could have been substituted with "亻" (U+4EBB). Local preferences about how sequences are constructed should be documented in the encodingDesc of the corresponding TEI header (see ). Additionally, a number of online services, such as CHISE, offer querying and retrieving characters via IDS, which facilitates a greater degree of stability across different applications.

-

Under certain circumstances, Chinese Han characters can be written -within a circle. Rather than considering this as simply an aspect of the rendering, an encoder may wish to treat such circled characters as entirely distinct derived characters. For a given character -(say that represented by the numeric-character reference &#x4EBA;) -the circled variant might conveniently be represented as - , which references a -definition such as the following: - - - - - - &#x4EBA; - - - &#xE000; - -

-

In this example, the circled ideograph -character has been defined with two mappings, and with two -properties. The two properties are the Unicode-defined -character-decomposition which specifies that this is a circled -character, using the appropriate terminology (see above) and a locally defined property known as -daikanwa. The two mappings indicate firstly that the standard form of this character is the character &#x4EBA;, and secondly that the character used to represent this character locally is the PUA character &#xE000;. For convenience of local processing this PUA character may in fact appear as content of the g element. In general, however, the g element -will be empty.

-
-
-How to Use Code Points from the Private Use Area -

The developers of the Unicode Standard have set aside an -area of the codespace for the private use of software vendors, -user groups, or individuals. As of this writing (Unicode 12.1), -there are around 137,000 code points available in this area, which -should be enough for most needs. No code point assignments will be made -to this area by standard bodies and only some very basic default -properties have been assigned (which may be overridden where -necessary by the mechanism outlined in this chapter). Therefore, -unlike all other code points defined by the Unicode Standard, PUA code points should -not be used directly in documents intended for blind interchange. -

-

In the two previous examples, we mentioned that the variant -characters concerned might well be assigned specific code points from -the PUA. This might, for example, facilitate the use of a particular -font which displays the desired character at this code point in the -local processing environment. Since however this assignment would be -valid only on the local site, documents containing such code points are -unsuitable for blind interchange. During the process of preparing -such documents for interchange, any PUA code points should be replaced by an appropriate use of the g element, such as g ref="#xxxx", thus associating the character required -with the documentation of it provided by the referenced char element. The PUA character -used during the preparation of the document might be recorded in the -char element, as shown in the example in , or retained as content of the g element. However, since there is no requirement that the same PUA -character be used to represent it at the receiving site, and since it -may well be the case that this other site has already made an -assignment of some other character to the original PUA code point, it is best practice to remove the locally-defined PUA character. It is to be expected that a further translation into the -local processing environment at the receiving site will be necessary -to handle such characters, during which variant letters can be -converted to hitherto unused code points on the basis of the -information provided in the char element.

-

This mechanism is rather weak in cases where DOM trees or -parsed XML fragments are exchanged, which may increasingly be the -case. The best an application can do here is to treat any -occurrence of a PUA character only in the context of the local -document and use the properties provided through the char -element as a handle to the character in other contexts.

-

In the fullness of time, a character may become standardized, and -thus assigned a specific code point outside the PUA. Documents which -have been encoded using the mechanism must at the least ensure that -this changed code point is recorded within the relevant char -element; it will however normally be simpler to remove the -char element and replace all occurrences of g -elements which reference it by occurrences of the newly coded -character.

-
- - -
- - Writing Modes - -

The scripts used for writing human languages vary not only in the -glyphs they use, but also in the way (or ways) that those glyphs are -arranged on the writing surface. For the majority of modern languages, -writing is arranged as a series of lines which are to be read from top -to bottom. Within each line, individual characters are frequently -presented from left to right (English, Russian, Greek), but there are -also several widely-used scripts which run right-to-left (Arabic, -Hebrew). Writing in which the lines of glyphs are presented vertically -and read from right to left is also often encountered, notably in -East Asian scripts (Sinitic characters, Japanese Kana, Korean -Hangul, Vietnamese chữ nôm). In many cases, a language normally uses -the same writing mode (we use this term to -refer to the orientation of individual glyphs within a line and the -order in which glyphs and lines should be read), but there are exceptions in which -the same language may appear in different modes, for example either -vertically or horizontally. Many East Asian scripts were traditionally -written from top to bottom within the line, with their lines sequenced -from right to left. Although modern Japanese, Chinese, and Korean are -often written horizontally, the traditional vertical writing mode is -still widely used. There are also comparatively rare cases of ancient -scripts written with lines running left to right, each line being read -top to bottom (Ancient Uighur, classical Mongolian and Manchu), or -scripts such as Ogham where the writing direction may start from the -bottom left and run around the edge of an inscribed object.

- -

When different languages are combined, it is possible that -different writing modes will be needed: for example, in Hebrew text, -running right to left, sequences of Latin digits still run left to -right. When different writing modes are available for the same -language, it may be that different glyphs will be preferred when the -script is used in different modes. For example, when Japanese is -written horizontally, the Unicode character U+3001, the -ideographic comma, is used in preference to -Unicode character U+FE11, the vertical mode comma. This ensures that -the comma appears in the correct position relative to the surrounding -glyphs. Even for scripts which are usually written in exactly the same -way, different writing modes may be encountered in particular -contexts; for example when a language using Roman script is embedded -within vertically-organized Chinese text, it may sometimes be -displayed vertically and sometimes horizontally. The writing mode may -also vary in response to layout constraints such as those imposed by a -complex table, where column or row labels may be written vertically or -diagonally to make the most effective use of available space, just as -it may vary in response to the size and shape of the carrier in the -case of a monumental inscription.

- -

For many, perhaps most, TEI documents there may be no need to -encode the writing mode explicitly, even in so-called "mixed mode" -texts containing passages written in languages which use different -writing modes. Modern printed texts in most European languages, for -instance, may be expected to use left-to-right/top-to-bottom -directionality; while Arabic or Hebrew texts are expected to run -right-to-left/top-to-bottom. In a TEI document, language and script -are explicitly stated in the markup using the attribute -xml:lang; this indication will usually imply a particular -default writing mode. Even where this attribute is not used, passages -in different scripts will use different Unicode characters, and will -thus imply a particular default writing mode.

- -

Consider the case of an English text containing a few Arabic words: - The Arabic term قلم رصاص means "pencil". -A correct TEI encoding might read as follows: - - The Arabic term - قلم رصاص means "pencil". - -We might assume that it is the presence of the xml:lang -attribute with value ar that causes processing software to -display the Arabic from right to left, but in fact, this is not the -case. The order in which the Arabic characters appear when rendered -would be the same, even if the markup were not present: - - The Arabic term قلم رصاص means "pencil". - -This is because Arabic glyphs are always displayed right to left, -even when they appear within a left-to-right English sentence. Like -most other codepoints in the Unicode standard, they have a specific -directionality setting which helps any rendering software determine -how they should be ordered. The Latin glyph "a" has a strong -left-to-right bidirectionality setting, as do the digits 0 to 9; the -Hebrew א (alef) is strongly right-to-left. Of course, some glyphs -(common punctuation marks such as the period or comma for example) -have weak or neutral settings because they may appear in several -contexts.

- -

The Unicode Bidirectional Algorithm (Unicode -Consortium, 2017) - defines a number of -rules enabling software to render sequences of characters which have -differing directionality properties in a predictable and reliable way, -using only those properties. Because this -algorithm may not always give the desired result, Unicode also -provides a set of "directional formatting characters" (). These -additional codepoints can be used to signal to rendering software that -a specific directionality setting should be turned on or off. However, -in the case of documents encoded in XML, there is generally no need to use such -characters, and the W3C advises against it unless markup is unavailable. (). It -should be remembered however that individual sequences of characters -are always stored in a file in the order in which they should be read, -irrespective of the order in which the characters making up a sequence -should be displayed or rendered. For example, in a RTL language such -as Hebrew, the first character in a file will be that which is -displayed at the rightmost end of the first line of text.

- -

An encoder wishing to document or to control the order in which -sequences of characters in a TEI document are displayed will usually -do so by segmenting the text into sequences presented in the desired -order and specifying an appropriate language code for each. In -situations where this approach may result in ambiguity or lack of -precision, or if the encoder wishes to record directional information -explicitly in their encoding, we recommend using the global @style -attribute to supply detail about the writing mode applicable to the -content of any element. The style attribute (discussed in -) permits use of any formatting language; for -these purposes however, we recommend use of CSS, which includes a -Writing Modes module At the time of writing, this -W3C module has the status of a candidate recommendation: see further - - which permits direct specification of a number of useful properties -associated with writing modes, notably direction (ltr -or rtl); writing-mode -(horizontal-tb, vertical-rl, or vertical-lr); -and text-orientation (mixed, upright, -sideways ...) - -as well as properties affecting the behaviour of the unicode-bidi (bidirectional) algorithm. -We discuss and exemplify how these properties may be used below.

- -

The global TEI style attribute applies to the element on -which it is specified (and in most cases, its descendants). Rather -than specify it on every element, it will often be more efficient to -express sets of commonly-used styling rules as rendition -elements in the teiHeader and then point to them using the -global rendition attribute, as further discussed in . Although the CSS specifications are mainly used to -provide instructions for software when rendering a digital text, they -also provide a useful means of describing the visual properties of a -pre-existing document in a formal and standardized way.

- -

The next section presents some examples of how CSS can be used to -describe a variety of writing modes. A full description of the appearance -of a document will probably include many other properties of course.

-
- -
- Examples of Different Writing Modes -

The CSS recommendations provides several properties which can be used to encode aspects of the "writing mode". The most useful of these is the property "writing-mode" which may be used to specify a reading-order for both characters within a single line and lines within a single block of text. The property "text-orientation" may also used to indicate the orientation of individual characters with respect to the line, and the property "direction" to determine the reading order of characters within a line only. We give some examples of each below.

-
- Vertical Writing Modes -

The writing-mode property is particularly useful for languages - which can be written in different writing modes, such as Chinese - and Japanese. Its possible values include horizontal-tb, - vertical-rl and vertical-lr. Each value has - two components: horizontal or vertical specifies the inline - writing direction, while the second component specifies the - direction in which lines in a block, and blocks in a sequence are - arranged: from top to bottom (as in most European languages, in - which lines and paragraphs are arranged from top to bottom on a - page), from right to left (as in the case of Japanese written vertically), or - left-to-right (as in the case of Mongolian).

-

The following example shows three versions of the same poem: first in - Japanese, written top to bottom; next in romaji (Japanese in - Latin script); and finally in an English translation.

-

-

- - Taken from p.42 of Haiku: Japanese Art and Poetry. Judith Patt, Michiko Warkentyne (calligraphy) and Barry Till. 2010. -
-

-

-

We might encode this as follows:

-
- - 古池や - 蛙 - 飛び込む - 水の音 - - - furu ike ya - kawazu tobikomu - mizu no oto - - - Old pond, - and a frog dives in— - "Splash"! - -
 -

For the sake of simplicity, we have not attempted to capture in - this encoding such aspects as the indenting of lines in the first - Japanese version, or the central alignment of the other two - versions, nor any other renditional features such as font weight or - size etc. The Japanese transcription has writing-mode: - vertical-rl, which is required because Japanese may be - written either in this mode or horizontally. The transcription in - romaji uses the attribute xml:lang to supply a value of - ja-Latn, indicating Japanese written in Latin - script. Its style attribute specifies a horizontal - writing mode; this may seem superfluous, but vertically-written - romaji is not unknown.

-
-
- Vertical Text with Embedded Horizontal Text - -

When Japanese is written vertically, the glyph orientation - remains the same as when it is written horizontally. In other - words, glyphs are not rotated (although as noted above some - different glyphs may be used for some characters, in particular for - punctuation which needs to be positioned differently in vertical - and in horizontal text). However, it is very common for languages - written vertically to have embedded runs of text from languages - which are normally written horizontally. This raises the issue of - the orientation of the glyphs from the horizontal language. Are - they written upright, as they would normally appear in horizontal - text runs, or are they rotated? Consider this fragment from a - Japanese article about the Indonesian language, which takes the - form of a glossary list:

-

-

- -Detail from p.62 of インドネシア語". 崎山理. 1985. 外国語との対照 II. 講座日本語学 11. -
-

- -

The text-orientation property allows us to indicate whether or - not glyphs are rotated. In the following example, we have indicated - that the list uses a vertical-rl writing mode, but that the orientation - of individual glyphs may vary:

- - - - 「近い、ほとんど」 - - 「新しい、ばかい」 - - -

The rule text-orientation: mixed specifies that - characters from horizontal-only scripts are set sideways, - i.e. 90° clockwise from their standard orientation in horizontal - text. Characters from vertical scripts are set with their intrinsic - orientation (fantasai - 2014). Since the default value for - text-orientation is mixed, this rule is - not strictly required. However, if the Indonesian glyphs (which are - roman characters) had been set vertically, like this:

-

-

- - Fragment of previous image with Indonesian glyphs upright. -
-

-

then an encoding like the following could be used to make this explicit:

- - - - 「近い、ほとんど」 - - 「新しい、ばかい」 - - - -

The rule text-orientation: upright specifies that - characters from horizontal-only scripts are rendered - upright, i.e. in their standard horizontal orientation. Characters - from vertical scripts are set with their intrinsic orientation and - shaped normally (fantasai - 2014).

-
-
- Vertical Orientation in Horizontal Scripts -

It is not unusual to see text from horizontal languages - written vertically even where no vertically-written script is - involved. This example is a fragment from a table of information - about agricultural development on Vancouver Island, written in - 1855:

-

-

- - Enclosure with Despatch to London 10048, CO - 305/6, p. 131v from -
-

-

Four of the subheading cells in this fragment contain English text written vertically, - bottom-to-top, to conserve space on the page. To describe this sort of phenomenon, - we can use the text-orientation property again:

- -

text-orientation: mixed | upright | sideways-right | sideways-left | sideways | use-glyph-orientation

- -

For full details on this property, we refer the reader to the CSS Writing Modes specification. - For the present example, we will make use only of the sideways-left value, - which causes text to be set as if in a horizontal layout, but rotated 90° counter-clockwise. - We might encode the third of the four cells containing vertical text like this:

- - - Cash Value - of - Farms - - -

The writing-mode property captures the fact that the script is written vertically, and - its lines are to be read from left to right (so the line containing of - is to the right of that containing Cash value), while the text-orientation - value encodes the orientation (rotated 90° counter-clockwise). We might also add - text-align: center to the style, to express the fact that the text is centrally-aligned.

-
-
- Bottom-to-top Writing -

Of the rather small number of scripts which appear to be written - bottom-to-top, perhaps the best-known is Ogham, an alphabet used - mainly to write Archaic Irish. Ogham is typically found inscribed - along the edge of a standing stone, starting at its base. The CSS Writing - Modes specification does not explicitly distinguish between - vertical scripts which are written top-to-bottom and those which - are written bottom-to-top. Instead, such bottom-to-top scripts are best treated - as left-to-right horizontal scripts, oriented vertically because of - the constraints of the medium on which they are inscribed. Such - scripts are analogous to the vertical English text-runs in the - table cells in the example above, and can be handled in exactly the - same manner (writing-mode: vertical-lr; text-orientation: - sideways-left). In cases where writing follows a curved path - (such as Ogham running around the edge of a stone), a meticulous - encoder might resort to the use of SVG to describe the path, rather - than treating the phenomenon as a writing mode.

-
-
- Mixed Horizontal Directionality - -

Returning to our previous simple example

- The Arabic term قلم رصاص means "pencil". -

we could use the direction property to make directionality explicit:

-

direction: ltr | rtl

- - The Arabic term - قلم رصاص means "pencil". - -

The use of the direction property to record the observed directionality - of the text is unambiguous, even though it is (as we noted above) superfluous. - The use of the unicode-bidi property here may require some explanation. - By default this property has the value normal, the effect of which in this - context would be to ignore any value supplied for the direction property. The CSS Writing - Modes specification stipulates that the direction property has no effect on bidi - reordering when specified on inline boxes whose unicode-bidi property’s - value is normal, because the element does not open an additional - level of embedding with respect to the bidirectional algorithm. -

- -

Mixed horizontal directionality is very common in languages such as Arabic - and Hebrew, particularly when numbers (which are always given LTR) - or phrases from LTR languages are embedded. It is not - impossible, though quite unusual, for ambiguities -to arise in such situations, which may give rise to the -parts of a document being displayed in unexpected ways that do -not correspond to the natural reading order. A more detailed - discussion of this issue from an HTML perspective is provided by a - W3C Internationalization Working Group report Inline - markup and bidirectional text in HTML.

- - - - - -
-
- - Summary -

For most texts, information about text directionality need not be explicitly - encoded in a TEI text, either because it follows unambiguously from - xml:lang values, or because it can be expected to be handled - unequivocally by the Unicode Bidi Algorithm. Where it is considered important - to encode such information, properties and values taken from the CSS Writing - Modes module may be used by means of the global TEI style attribute - (or using the TEI rendition element, linked with the rendition - attribute). Most phenomena can be well described in this way; of those which - cannot, other approaches based on the CSS Transforms module are presented - in the next section.

-
-
-
- - Text Rotation -

In what follows, we examine a range of textual phenomena which - in some ways appear very similar to those examined above, and even - overlap with them. We can categorize these as text transformation - features, and suggest some strategies for encoding them based on - the properties detailed in the CSS Transforms (Fraser et al 2013) specification. - This CSS module provides a complex array of properties, values and - functions which can be used to rotate, skew, translate and otherwise - transform textual and graphical objects. We can borrow this vocabulary - in order to describe textual phenomena in a precise manner.

- -

We begin with a simple example of a rotational transform:

-

-

- -
-

-

Here a block of text has been rotated around its z-axis. This is clearly - not a writing mode; the writing mode for this text - is horizontal, left to right. Furthermore, even if we wished to treat this - as a writing mode, we could not do so, because there is no way to use - writing modes properties to describe an text orientation which is angled - at 45 degrees; no human languages are consistently written in this - orientation. It is more appropriate to treat this as a rotational transformation. - We can do this using two properties: transform and - transform-origin. (Both of these properties have quite complex - value sets, and we will not look at all of them here. See the - specification for full details.)

- -

The transform property takes as its value one or more of the transform functions, - one of which is the function rotateZ():

- - TEI-C.ORG - -

Any rotation must take place clockwise around an axis positioned relative - to the element being rotated, and the transform-origin property - can be used to specify the pivot point. By default, the value of transform-origin - is 50% 50%, the point at the centre of the element, but these - values can be changed to reflect rotation around a different origin point. - (The TEI zone element also bears an attribute rotate which can - specify rotation in degrees around the z-axis, but it is not available for any other - element.)

- -

A block of text may also be rotated about either of its other axes. For example, - this shows rotation around the Y (vertical) axis:

-

-

- -
-

- TEI-C.ORG - -

These are obviously trivial examples, but similar features do appear in historical texts. - George Herbert's The Temple includes two stanzas headed - Easter Wings which are both normally printed in a rotated form - so that they represent a pair of wings:

-

-

- - Page 35 of George Herbert's The Temple - (1633), from a copy in the Folger Library. -
-

- -

This could be encoded thus:

- - - My tender age in ſorrow did beginne: - And ſtill with ſickneſſes and ſhame - - -

We might also argue that this is in fact a vertical writing - mode by supplying writing-mode: vertical-rl; - text-orientation: sideways-right as the value for the - style attribute in the preceding example.

- -

Rotation is also useful as a method of handling a true writing - mode which is not covered by the CSS Writing Modes: - boustrophedon. This is a writing mode common in - inscriptions in Latin, Greek and other languages, in which - alternate lines run from left to right and from right to leftThe name is taken from the Greek βουστροφηδόν, meaning - ox-turning from βοῦς (an ox) and στροφή (turn); that is, - turning as an ox does when pulling a plough.. Right-to-left - lines in boustrophedon have another unexpected feature: their - glyphs are reversed, so that these lines appear as mirror - writing, as in the following ancient Greek inscription: -

- -Leaden plaque bearing an inquiry by Hermon from the oracular -precinct at Dodona. (L.H. Jeffery Archive) -
-

-

This might be transcribed as follows (ignoring word boundaries for the moment):

- - ΗΕΡΜΟΝΤΙΝA - ΚΑΘΕΟΝΠΟΤΘΕΜ - ΕΝΟΣΥΕΝΕΑϜ - ΟΙΥΕΝΟΙΤΙΕΚΚ - ΡΕΤΑΙΑΣΟΝΑ - ΣΙΜΟΣΟΤΤΑΙΕ - ΑΣΣΑΙ - -

The 180-degree rotation around the Y (vertical) axis here - describes what is happening in the RTL line in boustrophedon; the order of glyphs - is reversed, and so is their individual orientation (in fact, we see them - from the back, as it were). seg elements - have been used here because these are clearly not lines - in the sense of poetic lines; the text is continuous prose, and linebreaks - are incidental.

- -

There are obviously some unsatisfactory aspects of this manner of encoding - boustrophedon. In the inscription above, some words run across linebreaks, - so if we wished to tag both words and the right-to-left phenomena, one - hierarchy would have to be privileged over the other. By using a transform - function rather than a writing mode property, we are apparently suggesting - that boustrophedon is not in fact a writing mode, whereas it clearly is. But - the CSS Writing Modes specification does not provide support for boustrophedon, - because it is a rather obscure historical phenomenon; using a rotational transform - is one practical alternative.

- -
-
- Caveat - -

As with other parts of the CSS specification, the intended - effect of CSS Transforms properties and values is defined with - reference to a specific Visual formatting - model; the language is designed to describe how an HTML - document should be formatted. This is not, of course, the case for - the TEI, which lacks any explicit processing or formatting model, - and attempts to define objects as far as possible without - consideration of their visual appearance. As long as the properties - and values from the CSS Transforms module are used as a convenient, - well-specified descriptive language to capture features of a text, - without any expectation of using them directly and reliably for - rendering, this is not particularly problematic. CSS provides a - useful and well-defined vocabulary to describe many aspects of the - appearance of source texts, benefitting particularly from the - clarity of definition provided by the specification. However, if - there is any expectation of using this information to render a text - in a predictable and accurate way, it will be essential to provide - enough styling information throughout the document hierarchy to - resolve all ambiguities with regard to size, positioning, block - status, etc. before any element undergoes a transform - operation.

-
- - -
Formal Definition -

The gaiji module described in this chapter makes available the following -components: - - Character and Glyph Documentation - Character and glyph documentation - Représentation des caractères et des glyphes non standard - 文字與字體說明 - Documentazione di caratteri non standard e glifi - Documentação dos carateres - 外字モジュール - - -The selection and combination of modules to form a TEI schema is described in -. -

- - - - - - - - - - - - -
-
diff --git a/P5/Source/Guidelines/fr/WD-NonStandardCharacters.xml b/P5/Source/Guidelines/fr/WD-NonStandardCharacters.xml new file mode 120000 index 0000000000..58533a1b20 --- /dev/null +++ b/P5/Source/Guidelines/fr/WD-NonStandardCharacters.xml @@ -0,0 +1 @@ +../en/./WD-NonStandardCharacters.xml \ No newline at end of file diff --git a/P5/Source/Specs/TEI.xml b/P5/Source/Specs/TEI.xml index f9e779ce03..8f058f55d7 100644 --- a/P5/Source/Specs/TEI.xml +++ b/P5/Source/Specs/TEI.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/ab.xml b/P5/Source/Specs/ab.xml index 8718461882..94036c4042 100644 --- a/P5/Source/Specs/ab.xml +++ b/P5/Source/Specs/ab.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/abbr.xml b/P5/Source/Specs/abbr.xml index e6cd6f0f6e..4c66655d09 100644 --- a/P5/Source/Specs/abbr.xml +++ b/P5/Source/Specs/abbr.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/abstract.xml b/P5/Source/Specs/abstract.xml index fc53a09f63..aed6ce706f 100644 --- a/P5/Source/Specs/abstract.xml +++ b/P5/Source/Specs/abstract.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/accMat.xml b/P5/Source/Specs/accMat.xml index 10aa249263..e7b7d75de0 100644 --- a/P5/Source/Specs/accMat.xml +++ b/P5/Source/Specs/accMat.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/actor.xml b/P5/Source/Specs/actor.xml index 3c2e9db59a..de765a29a4 100644 --- a/P5/Source/Specs/actor.xml +++ b/P5/Source/Specs/actor.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/add.xml b/P5/Source/Specs/add.xml index 8f55105eed..f65ba3530b 100644 --- a/P5/Source/Specs/add.xml +++ b/P5/Source/Specs/add.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/addName.xml b/P5/Source/Specs/addName.xml index ec28e8c578..736b0b7967 100644 --- a/P5/Source/Specs/addName.xml +++ b/P5/Source/Specs/addName.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/addSpan.xml b/P5/Source/Specs/addSpan.xml index ffbfc6622a..acaeea22c4 100644 --- a/P5/Source/Specs/addSpan.xml +++ b/P5/Source/Specs/addSpan.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/additional.xml b/P5/Source/Specs/additional.xml index aefeac5d47..bc044829e4 100644 --- a/P5/Source/Specs/additional.xml +++ b/P5/Source/Specs/additional.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/additions.xml b/P5/Source/Specs/additions.xml index 072f726d3c..1eed0204c2 100644 --- a/P5/Source/Specs/additions.xml +++ b/P5/Source/Specs/additions.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/addrLine.xml b/P5/Source/Specs/addrLine.xml index 0a3a27ba6d..3c6dacb5d5 100644 --- a/P5/Source/Specs/addrLine.xml +++ b/P5/Source/Specs/addrLine.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/address.xml b/P5/Source/Specs/address.xml index 3fc9b7f3f7..e9905c503b 100644 --- a/P5/Source/Specs/address.xml +++ b/P5/Source/Specs/address.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/adminInfo.xml b/P5/Source/Specs/adminInfo.xml index 187093982e..dcf9e77604 100644 --- a/P5/Source/Specs/adminInfo.xml +++ b/P5/Source/Specs/adminInfo.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/alt.xml b/P5/Source/Specs/alt.xml index 02ba2c3b87..04693d7422 100644 --- a/P5/Source/Specs/alt.xml +++ b/P5/Source/Specs/alt.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/altGrp.xml b/P5/Source/Specs/altGrp.xml index df42c046d2..aa13ad11a0 100644 --- a/P5/Source/Specs/altGrp.xml +++ b/P5/Source/Specs/altGrp.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/altIdent.xml b/P5/Source/Specs/altIdent.xml index 1e4f07e909..5396cfb634 100644 --- a/P5/Source/Specs/altIdent.xml +++ b/P5/Source/Specs/altIdent.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/alternate.xml b/P5/Source/Specs/alternate.xml index d9f194a44e..74b743d2bf 100644 --- a/P5/Source/Specs/alternate.xml +++ b/P5/Source/Specs/alternate.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/am.xml b/P5/Source/Specs/am.xml index 89487bf824..cb310b015f 100644 --- a/P5/Source/Specs/am.xml +++ b/P5/Source/Specs/am.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/analytic.xml b/P5/Source/Specs/analytic.xml index 3ac57fee55..d16227469d 100644 --- a/P5/Source/Specs/analytic.xml +++ b/P5/Source/Specs/analytic.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/anchor.xml b/P5/Source/Specs/anchor.xml index bd66b33b79..3716cd863e 100644 --- a/P5/Source/Specs/anchor.xml +++ b/P5/Source/Specs/anchor.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/annotation.xml b/P5/Source/Specs/annotation.xml index 4d0191b677..cf50df7357 100644 --- a/P5/Source/Specs/annotation.xml +++ b/P5/Source/Specs/annotation.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/anyElement.xml b/P5/Source/Specs/anyElement.xml index 0a6034270d..1623b944db 100644 --- a/P5/Source/Specs/anyElement.xml +++ b/P5/Source/Specs/anyElement.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/app.xml b/P5/Source/Specs/app.xml index ee3da7cdfc..6d860edfed 100644 --- a/P5/Source/Specs/app.xml +++ b/P5/Source/Specs/app.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/appInfo.xml b/P5/Source/Specs/appInfo.xml index 45c7f9dbb8..7f5136c182 100644 --- a/P5/Source/Specs/appInfo.xml +++ b/P5/Source/Specs/appInfo.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/arc.xml b/P5/Source/Specs/arc.xml index c4e920af76..af9d075df2 100644 --- a/P5/Source/Specs/arc.xml +++ b/P5/Source/Specs/arc.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/argument.xml b/P5/Source/Specs/argument.xml index 13b4adb462..a7b3f4862c 100644 --- a/P5/Source/Specs/argument.xml +++ b/P5/Source/Specs/argument.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.anchoring.xml b/P5/Source/Specs/att.anchoring.xml index 8841f61c63..4dec26ca88 100644 --- a/P5/Source/Specs/att.anchoring.xml +++ b/P5/Source/Specs/att.anchoring.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.ascribed.directed.xml b/P5/Source/Specs/att.ascribed.directed.xml index 8eb1e80143..e622a8fae3 100644 --- a/P5/Source/Specs/att.ascribed.directed.xml +++ b/P5/Source/Specs/att.ascribed.directed.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.ascribed.xml b/P5/Source/Specs/att.ascribed.xml index 7aeb0f4421..35aeb401fd 100644 --- a/P5/Source/Specs/att.ascribed.xml +++ b/P5/Source/Specs/att.ascribed.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.breaking.xml b/P5/Source/Specs/att.breaking.xml index 1a92710321..75aa797a6f 100644 --- a/P5/Source/Specs/att.breaking.xml +++ b/P5/Source/Specs/att.breaking.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.cReferencing.xml b/P5/Source/Specs/att.cReferencing.xml index a450cd5516..4d93a69506 100644 --- a/P5/Source/Specs/att.cReferencing.xml +++ b/P5/Source/Specs/att.cReferencing.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.calendarSystem.xml b/P5/Source/Specs/att.calendarSystem.xml index abdfc796ea..735166ae98 100644 --- a/P5/Source/Specs/att.calendarSystem.xml +++ b/P5/Source/Specs/att.calendarSystem.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.canonical.xml b/P5/Source/Specs/att.canonical.xml index cb1d8afe9b..79d247f589 100644 --- a/P5/Source/Specs/att.canonical.xml +++ b/P5/Source/Specs/att.canonical.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.citeStructurePart.xml b/P5/Source/Specs/att.citeStructurePart.xml index 7c15aeabbe..6602536ce4 100644 --- a/P5/Source/Specs/att.citeStructurePart.xml +++ b/P5/Source/Specs/att.citeStructurePart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.citing.xml b/P5/Source/Specs/att.citing.xml index ee841a807b..b641d071b1 100644 --- a/P5/Source/Specs/att.citing.xml +++ b/P5/Source/Specs/att.citing.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.combinable.xml b/P5/Source/Specs/att.combinable.xml index 5b05f5735b..25e6a4b9b7 100644 --- a/P5/Source/Specs/att.combinable.xml +++ b/P5/Source/Specs/att.combinable.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.coordinated.xml b/P5/Source/Specs/att.coordinated.xml index aa9c818d63..a6b3e5de71 100644 --- a/P5/Source/Specs/att.coordinated.xml +++ b/P5/Source/Specs/att.coordinated.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.damaged.xml b/P5/Source/Specs/att.damaged.xml index ffbf926c28..9402e33774 100644 --- a/P5/Source/Specs/att.damaged.xml +++ b/P5/Source/Specs/att.damaged.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.datable.custom.xml b/P5/Source/Specs/att.datable.custom.xml index 298ff2d19d..a0ef6b64e1 100644 --- a/P5/Source/Specs/att.datable.custom.xml +++ b/P5/Source/Specs/att.datable.custom.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.datable.iso.xml b/P5/Source/Specs/att.datable.iso.xml index a222fbb8a3..12b4dfdfcf 100644 --- a/P5/Source/Specs/att.datable.iso.xml +++ b/P5/Source/Specs/att.datable.iso.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.datable.w3c.xml b/P5/Source/Specs/att.datable.w3c.xml index 8563ab0a09..4245b2c142 100644 --- a/P5/Source/Specs/att.datable.w3c.xml +++ b/P5/Source/Specs/att.datable.w3c.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.datable.xml b/P5/Source/Specs/att.datable.xml index cf817927a5..671fbc2406 100644 --- a/P5/Source/Specs/att.datable.xml +++ b/P5/Source/Specs/att.datable.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.datcat.xml b/P5/Source/Specs/att.datcat.xml index 89f1611e30..1081434b20 100644 --- a/P5/Source/Specs/att.datcat.xml +++ b/P5/Source/Specs/att.datcat.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.declaring.xml b/P5/Source/Specs/att.declaring.xml index ffebd1514c..300f0708fc 100644 --- a/P5/Source/Specs/att.declaring.xml +++ b/P5/Source/Specs/att.declaring.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.deprecated.xml b/P5/Source/Specs/att.deprecated.xml index 2e39248858..20253e6a30 100644 --- a/P5/Source/Specs/att.deprecated.xml +++ b/P5/Source/Specs/att.deprecated.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.dimensions.xml b/P5/Source/Specs/att.dimensions.xml index 2d79c3b0f9..d6508d4a3e 100644 --- a/P5/Source/Specs/att.dimensions.xml +++ b/P5/Source/Specs/att.dimensions.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.divLike.xml b/P5/Source/Specs/att.divLike.xml index 25b4efbb9c..e265fe802a 100644 --- a/P5/Source/Specs/att.divLike.xml +++ b/P5/Source/Specs/att.divLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.docStatus.xml b/P5/Source/Specs/att.docStatus.xml index 47866c32af..368efd4e62 100644 --- a/P5/Source/Specs/att.docStatus.xml +++ b/P5/Source/Specs/att.docStatus.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.duration.iso.xml b/P5/Source/Specs/att.duration.iso.xml index 737d550651..16621af215 100644 --- a/P5/Source/Specs/att.duration.iso.xml +++ b/P5/Source/Specs/att.duration.iso.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.duration.w3c.xml b/P5/Source/Specs/att.duration.w3c.xml index 9f0b36e673..d4651a2362 100644 --- a/P5/Source/Specs/att.duration.w3c.xml +++ b/P5/Source/Specs/att.duration.w3c.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.duration.xml b/P5/Source/Specs/att.duration.xml index 5cc32e857f..6cc0e96f21 100644 --- a/P5/Source/Specs/att.duration.xml +++ b/P5/Source/Specs/att.duration.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.editLike.xml b/P5/Source/Specs/att.editLike.xml index 49a594ecde..8640add267 100644 --- a/P5/Source/Specs/att.editLike.xml +++ b/P5/Source/Specs/att.editLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.edition.xml b/P5/Source/Specs/att.edition.xml index 6b2d9f968f..7b9d75a576 100644 --- a/P5/Source/Specs/att.edition.xml +++ b/P5/Source/Specs/att.edition.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.enjamb.xml b/P5/Source/Specs/att.enjamb.xml index 073c2b1104..18da1c2d3a 100644 --- a/P5/Source/Specs/att.enjamb.xml +++ b/P5/Source/Specs/att.enjamb.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.entryLike.xml b/P5/Source/Specs/att.entryLike.xml index 4b11831056..2d7250e04d 100644 --- a/P5/Source/Specs/att.entryLike.xml +++ b/P5/Source/Specs/att.entryLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.formula.xml b/P5/Source/Specs/att.formula.xml index e3f8ba5cfb..1c586dfc1e 100644 --- a/P5/Source/Specs/att.formula.xml +++ b/P5/Source/Specs/att.formula.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.fragmentable.xml b/P5/Source/Specs/att.fragmentable.xml index c9e3a9b4a9..f7dc410d45 100644 --- a/P5/Source/Specs/att.fragmentable.xml +++ b/P5/Source/Specs/att.fragmentable.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.gaijiProp.xml b/P5/Source/Specs/att.gaijiProp.xml index bce2f4a029..c4c2f03a60 100644 --- a/P5/Source/Specs/att.gaijiProp.xml +++ b/P5/Source/Specs/att.gaijiProp.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.global.analytic.xml b/P5/Source/Specs/att.global.analytic.xml index 2dd56940c4..eb1687301f 100644 --- a/P5/Source/Specs/att.global.analytic.xml +++ b/P5/Source/Specs/att.global.analytic.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.global.change.xml b/P5/Source/Specs/att.global.change.xml index 3b08692d6a..ef080b28b3 100644 --- a/P5/Source/Specs/att.global.change.xml +++ b/P5/Source/Specs/att.global.change.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.global.facs.xml b/P5/Source/Specs/att.global.facs.xml index 484fc218a3..28007af28a 100644 --- a/P5/Source/Specs/att.global.facs.xml +++ b/P5/Source/Specs/att.global.facs.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.global.linking.xml b/P5/Source/Specs/att.global.linking.xml index 4dbf7b053c..5ad6efa452 100644 --- a/P5/Source/Specs/att.global.linking.xml +++ b/P5/Source/Specs/att.global.linking.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.global.rendition.xml b/P5/Source/Specs/att.global.rendition.xml index b28d1524be..9980cede90 100644 --- a/P5/Source/Specs/att.global.rendition.xml +++ b/P5/Source/Specs/att.global.rendition.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.global.responsibility.xml b/P5/Source/Specs/att.global.responsibility.xml index b3a09b3cc5..aefec8b5db 100644 --- a/P5/Source/Specs/att.global.responsibility.xml +++ b/P5/Source/Specs/att.global.responsibility.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.global.source.xml b/P5/Source/Specs/att.global.source.xml index 1ff09275c0..97371be41d 100644 --- a/P5/Source/Specs/att.global.source.xml +++ b/P5/Source/Specs/att.global.source.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.global.xml b/P5/Source/Specs/att.global.xml index f3d180c526..f1d22e983b 100644 --- a/P5/Source/Specs/att.global.xml +++ b/P5/Source/Specs/att.global.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.handFeatures.xml b/P5/Source/Specs/att.handFeatures.xml index c7a7c63184..e4ad0a6e81 100644 --- a/P5/Source/Specs/att.handFeatures.xml +++ b/P5/Source/Specs/att.handFeatures.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.identified.xml b/P5/Source/Specs/att.identified.xml index def3639b3c..dbb3a3afb2 100644 --- a/P5/Source/Specs/att.identified.xml +++ b/P5/Source/Specs/att.identified.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.internetMedia.xml b/P5/Source/Specs/att.internetMedia.xml index b0ae3c6564..9aa4efe255 100644 --- a/P5/Source/Specs/att.internetMedia.xml +++ b/P5/Source/Specs/att.internetMedia.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.interpLike.xml b/P5/Source/Specs/att.interpLike.xml index 17debf1f49..98431f97c8 100644 --- a/P5/Source/Specs/att.interpLike.xml +++ b/P5/Source/Specs/att.interpLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.lexicographic.xml b/P5/Source/Specs/att.lexicographic.xml index 2edad5524a..2679a2a94a 100644 --- a/P5/Source/Specs/att.lexicographic.xml +++ b/P5/Source/Specs/att.lexicographic.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.linguistic.xml b/P5/Source/Specs/att.linguistic.xml index ba3f7b3a8f..1994494e63 100644 --- a/P5/Source/Specs/att.linguistic.xml +++ b/P5/Source/Specs/att.linguistic.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.locatable.xml b/P5/Source/Specs/att.locatable.xml index 173f78b874..830ae5281b 100644 --- a/P5/Source/Specs/att.locatable.xml +++ b/P5/Source/Specs/att.locatable.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.media.xml b/P5/Source/Specs/att.media.xml index b8047e105b..baaec18dac 100644 --- a/P5/Source/Specs/att.media.xml +++ b/P5/Source/Specs/att.media.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.metrical.xml b/P5/Source/Specs/att.metrical.xml index 26ec9bbd6d..e63bd07782 100644 --- a/P5/Source/Specs/att.metrical.xml +++ b/P5/Source/Specs/att.metrical.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.milestoneUnit.xml b/P5/Source/Specs/att.milestoneUnit.xml index c8b41afa3b..b722615eef 100644 --- a/P5/Source/Specs/att.milestoneUnit.xml +++ b/P5/Source/Specs/att.milestoneUnit.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.msExcerpt.xml b/P5/Source/Specs/att.msExcerpt.xml index 2c08f8654e..92bc6df421 100644 --- a/P5/Source/Specs/att.msExcerpt.xml +++ b/P5/Source/Specs/att.msExcerpt.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.namespaceable.xml b/P5/Source/Specs/att.namespaceable.xml index f330c1d0be..605fbe4f52 100644 --- a/P5/Source/Specs/att.namespaceable.xml +++ b/P5/Source/Specs/att.namespaceable.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.naming.xml b/P5/Source/Specs/att.naming.xml index 02661b59ef..8fc1e7b118 100644 --- a/P5/Source/Specs/att.naming.xml +++ b/P5/Source/Specs/att.naming.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.notated.xml b/P5/Source/Specs/att.notated.xml index 4d32a7d9a8..07055a8055 100644 --- a/P5/Source/Specs/att.notated.xml +++ b/P5/Source/Specs/att.notated.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.partials.xml b/P5/Source/Specs/att.partials.xml index e0a596e52b..ea22dbe46a 100644 --- a/P5/Source/Specs/att.partials.xml +++ b/P5/Source/Specs/att.partials.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.patternReplacement.xml b/P5/Source/Specs/att.patternReplacement.xml index 2d4120e515..95bd7803b9 100644 --- a/P5/Source/Specs/att.patternReplacement.xml +++ b/P5/Source/Specs/att.patternReplacement.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.personal.xml b/P5/Source/Specs/att.personal.xml index b9de4ef0da..aedeb3f6a4 100644 --- a/P5/Source/Specs/att.personal.xml +++ b/P5/Source/Specs/att.personal.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.placement.xml b/P5/Source/Specs/att.placement.xml index ea39dd853e..e500b40c38 100644 --- a/P5/Source/Specs/att.placement.xml +++ b/P5/Source/Specs/att.placement.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.pointing.group.xml b/P5/Source/Specs/att.pointing.group.xml index 608afc689e..1d0b692f75 100644 --- a/P5/Source/Specs/att.pointing.group.xml +++ b/P5/Source/Specs/att.pointing.group.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.pointing.xml b/P5/Source/Specs/att.pointing.xml index be6706a871..068af0dec9 100644 --- a/P5/Source/Specs/att.pointing.xml +++ b/P5/Source/Specs/att.pointing.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.predicate.xml b/P5/Source/Specs/att.predicate.xml index c59aa6d56b..35fe5f572b 100644 --- a/P5/Source/Specs/att.predicate.xml +++ b/P5/Source/Specs/att.predicate.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.ranging.xml b/P5/Source/Specs/att.ranging.xml index de53817f95..b56565c95e 100644 --- a/P5/Source/Specs/att.ranging.xml +++ b/P5/Source/Specs/att.ranging.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.rdgPart.xml b/P5/Source/Specs/att.rdgPart.xml index e8beac7127..f67751789a 100644 --- a/P5/Source/Specs/att.rdgPart.xml +++ b/P5/Source/Specs/att.rdgPart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.repeatable.xml b/P5/Source/Specs/att.repeatable.xml index d998311c9c..47943bf7fb 100644 --- a/P5/Source/Specs/att.repeatable.xml +++ b/P5/Source/Specs/att.repeatable.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.resourced.xml b/P5/Source/Specs/att.resourced.xml index 063cfa695d..24775f1a3b 100644 --- a/P5/Source/Specs/att.resourced.xml +++ b/P5/Source/Specs/att.resourced.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.scoping.xml b/P5/Source/Specs/att.scoping.xml index 564e87fac2..c8fd3ca714 100644 --- a/P5/Source/Specs/att.scoping.xml +++ b/P5/Source/Specs/att.scoping.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.segLike.xml b/P5/Source/Specs/att.segLike.xml index ec569cd46b..15bb6a8e2a 100644 --- a/P5/Source/Specs/att.segLike.xml +++ b/P5/Source/Specs/att.segLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.sortable.xml b/P5/Source/Specs/att.sortable.xml index 1b66543ebb..124c80d0d9 100644 --- a/P5/Source/Specs/att.sortable.xml +++ b/P5/Source/Specs/att.sortable.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.spanning.xml b/P5/Source/Specs/att.spanning.xml index 71b1611f64..6a95a334da 100644 --- a/P5/Source/Specs/att.spanning.xml +++ b/P5/Source/Specs/att.spanning.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.styleDef.xml b/P5/Source/Specs/att.styleDef.xml index c51ad1314c..940244f693 100644 --- a/P5/Source/Specs/att.styleDef.xml +++ b/P5/Source/Specs/att.styleDef.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.tableDecoration.xml b/P5/Source/Specs/att.tableDecoration.xml index 32616a0f09..8c070340f0 100644 --- a/P5/Source/Specs/att.tableDecoration.xml +++ b/P5/Source/Specs/att.tableDecoration.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.textCritical.xml b/P5/Source/Specs/att.textCritical.xml index 0a615ba848..47dc41845a 100644 --- a/P5/Source/Specs/att.textCritical.xml +++ b/P5/Source/Specs/att.textCritical.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.timed.xml b/P5/Source/Specs/att.timed.xml index 3212075348..a9773626a0 100644 --- a/P5/Source/Specs/att.timed.xml +++ b/P5/Source/Specs/att.timed.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.transcriptional.xml b/P5/Source/Specs/att.transcriptional.xml index af34c63c6c..b3904c4cd2 100644 --- a/P5/Source/Specs/att.transcriptional.xml +++ b/P5/Source/Specs/att.transcriptional.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.translatable.xml b/P5/Source/Specs/att.translatable.xml index 4565876756..547d2185ce 100644 --- a/P5/Source/Specs/att.translatable.xml +++ b/P5/Source/Specs/att.translatable.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.typed.xml b/P5/Source/Specs/att.typed.xml index f9adf9696c..49cc5c4c0c 100644 --- a/P5/Source/Specs/att.typed.xml +++ b/P5/Source/Specs/att.typed.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.witnessed.xml b/P5/Source/Specs/att.witnessed.xml index c08ec0f2cb..f094331a9c 100644 --- a/P5/Source/Specs/att.witnessed.xml +++ b/P5/Source/Specs/att.witnessed.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.written.xml b/P5/Source/Specs/att.written.xml index ccde47fe80..16b8ff40fc 100644 --- a/P5/Source/Specs/att.written.xml +++ b/P5/Source/Specs/att.written.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/att.xml b/P5/Source/Specs/att.xml index 46f891d634..a68bf3029e 100644 --- a/P5/Source/Specs/att.xml +++ b/P5/Source/Specs/att.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/attDef.xml b/P5/Source/Specs/attDef.xml index c4a55b11f7..4dc8ac0e27 100644 --- a/P5/Source/Specs/attDef.xml +++ b/P5/Source/Specs/attDef.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/attList.xml b/P5/Source/Specs/attList.xml index 06f0db90cf..a2a7c7fbc6 100644 --- a/P5/Source/Specs/attList.xml +++ b/P5/Source/Specs/attList.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/attRef.xml b/P5/Source/Specs/attRef.xml index 9c7dc32e87..7fc2e4859b 100644 --- a/P5/Source/Specs/attRef.xml +++ b/P5/Source/Specs/attRef.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/authority.xml b/P5/Source/Specs/authority.xml index 4f269ce281..cf06e094f6 100644 --- a/P5/Source/Specs/authority.xml +++ b/P5/Source/Specs/authority.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/availability.xml b/P5/Source/Specs/availability.xml index f6fa6a0b0d..461e029701 100644 --- a/P5/Source/Specs/availability.xml +++ b/P5/Source/Specs/availability.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/back.xml b/P5/Source/Specs/back.xml index 9453ec0cc2..aeca2168e9 100644 --- a/P5/Source/Specs/back.xml +++ b/P5/Source/Specs/back.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/bibl.xml b/P5/Source/Specs/bibl.xml index 89eb998995..3a6df7d3f7 100644 --- a/P5/Source/Specs/bibl.xml +++ b/P5/Source/Specs/bibl.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/biblFull.xml b/P5/Source/Specs/biblFull.xml index de359d2876..0210fdb6a9 100644 --- a/P5/Source/Specs/biblFull.xml +++ b/P5/Source/Specs/biblFull.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/biblScope.xml b/P5/Source/Specs/biblScope.xml index 3682ffd5b1..a4b425029d 100644 --- a/P5/Source/Specs/biblScope.xml +++ b/P5/Source/Specs/biblScope.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/biblStruct.xml b/P5/Source/Specs/biblStruct.xml index 36ec4f8b7a..1d011834d7 100644 --- a/P5/Source/Specs/biblStruct.xml +++ b/P5/Source/Specs/biblStruct.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/bicond.xml b/P5/Source/Specs/bicond.xml index 5059a0a142..86d96ebb67 100644 --- a/P5/Source/Specs/bicond.xml +++ b/P5/Source/Specs/bicond.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/binary.xml b/P5/Source/Specs/binary.xml index 919333114f..b9be6e9697 100644 --- a/P5/Source/Specs/binary.xml +++ b/P5/Source/Specs/binary.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/binaryObject.xml b/P5/Source/Specs/binaryObject.xml index 88ce086b59..f205dc4dfb 100644 --- a/P5/Source/Specs/binaryObject.xml +++ b/P5/Source/Specs/binaryObject.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/bindingDesc.xml b/P5/Source/Specs/bindingDesc.xml index 5af5063ac9..96fcfb40f3 100644 --- a/P5/Source/Specs/bindingDesc.xml +++ b/P5/Source/Specs/bindingDesc.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/body.xml b/P5/Source/Specs/body.xml index d997b57c2a..8cd927de7d 100644 --- a/P5/Source/Specs/body.xml +++ b/P5/Source/Specs/body.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/broadcast.xml b/P5/Source/Specs/broadcast.xml index 0c0d7d2f26..d18684b500 100644 --- a/P5/Source/Specs/broadcast.xml +++ b/P5/Source/Specs/broadcast.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/byline.xml b/P5/Source/Specs/byline.xml index 7a3caf9f0e..7791edd8a2 100644 --- a/P5/Source/Specs/byline.xml +++ b/P5/Source/Specs/byline.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/c.xml b/P5/Source/Specs/c.xml index 5151bf6108..f4c4d54a59 100644 --- a/P5/Source/Specs/c.xml +++ b/P5/Source/Specs/c.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/cRefPattern.xml b/P5/Source/Specs/cRefPattern.xml index 32cbe8280c..dc58b6f9f9 100644 --- a/P5/Source/Specs/cRefPattern.xml +++ b/P5/Source/Specs/cRefPattern.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/caesura.xml b/P5/Source/Specs/caesura.xml index 2e4769ff90..198a841591 100644 --- a/P5/Source/Specs/caesura.xml +++ b/P5/Source/Specs/caesura.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/calendar.xml b/P5/Source/Specs/calendar.xml index 1795e00f7e..1d27b8a48f 100644 --- a/P5/Source/Specs/calendar.xml +++ b/P5/Source/Specs/calendar.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/calendarDesc.xml b/P5/Source/Specs/calendarDesc.xml index 5b43b3eab7..c7ed2b1e1a 100644 --- a/P5/Source/Specs/calendarDesc.xml +++ b/P5/Source/Specs/calendarDesc.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/camera.xml b/P5/Source/Specs/camera.xml index 362ee40d6d..1b9448cef2 100644 --- a/P5/Source/Specs/camera.xml +++ b/P5/Source/Specs/camera.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/caption.xml b/P5/Source/Specs/caption.xml index a4cf82f135..4be4953868 100644 --- a/P5/Source/Specs/caption.xml +++ b/P5/Source/Specs/caption.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/case.xml b/P5/Source/Specs/case.xml index 1e84cdb86a..449e3c61fe 100644 --- a/P5/Source/Specs/case.xml +++ b/P5/Source/Specs/case.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/castGroup.xml b/P5/Source/Specs/castGroup.xml index 420fad30d0..104ff6e9ca 100644 --- a/P5/Source/Specs/castGroup.xml +++ b/P5/Source/Specs/castGroup.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/castItem.xml b/P5/Source/Specs/castItem.xml index cb38befe7b..9dcf03c2df 100644 --- a/P5/Source/Specs/castItem.xml +++ b/P5/Source/Specs/castItem.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/castList.xml b/P5/Source/Specs/castList.xml index 0c6db4b5d7..30081fa397 100644 --- a/P5/Source/Specs/castList.xml +++ b/P5/Source/Specs/castList.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/catDesc.xml b/P5/Source/Specs/catDesc.xml index 7c5eee627d..d94f20bf5c 100644 --- a/P5/Source/Specs/catDesc.xml +++ b/P5/Source/Specs/catDesc.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/catRef.xml b/P5/Source/Specs/catRef.xml index dc1d662095..dd50289688 100644 --- a/P5/Source/Specs/catRef.xml +++ b/P5/Source/Specs/catRef.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/catchwords.xml b/P5/Source/Specs/catchwords.xml index 0dea6a3fc2..5db3ac3d98 100644 --- a/P5/Source/Specs/catchwords.xml +++ b/P5/Source/Specs/catchwords.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/category.xml b/P5/Source/Specs/category.xml index c65549e62f..add5e24715 100644 --- a/P5/Source/Specs/category.xml +++ b/P5/Source/Specs/category.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/cb.xml b/P5/Source/Specs/cb.xml index ad01b8ce5c..8733f949aa 100644 --- a/P5/Source/Specs/cb.xml +++ b/P5/Source/Specs/cb.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/cell.xml b/P5/Source/Specs/cell.xml index 194b1fdcbc..c5b8e783a5 100644 --- a/P5/Source/Specs/cell.xml +++ b/P5/Source/Specs/cell.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/certainty.xml b/P5/Source/Specs/certainty.xml index dbab1a7661..cc4245e8bf 100644 --- a/P5/Source/Specs/certainty.xml +++ b/P5/Source/Specs/certainty.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/channel.xml b/P5/Source/Specs/channel.xml index 420031e21e..cbc26f9f1e 100644 --- a/P5/Source/Specs/channel.xml +++ b/P5/Source/Specs/channel.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/char.xml b/P5/Source/Specs/char.xml index b0af7995d8..0ee8e4a39a 100644 --- a/P5/Source/Specs/char.xml +++ b/P5/Source/Specs/char.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/charDecl.xml b/P5/Source/Specs/charDecl.xml index 03f34fab08..cb28b4f15c 100644 --- a/P5/Source/Specs/charDecl.xml +++ b/P5/Source/Specs/charDecl.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/choice.xml b/P5/Source/Specs/choice.xml index 9cd79835c8..5bd682b7b7 100644 --- a/P5/Source/Specs/choice.xml +++ b/P5/Source/Specs/choice.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/cit.xml b/P5/Source/Specs/cit.xml index 7c846a1267..a91da2eba5 100644 --- a/P5/Source/Specs/cit.xml +++ b/P5/Source/Specs/cit.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/citeData.xml b/P5/Source/Specs/citeData.xml index 1a526b59d5..765b2a6745 100644 --- a/P5/Source/Specs/citeData.xml +++ b/P5/Source/Specs/citeData.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/citeStructure.xml b/P5/Source/Specs/citeStructure.xml index 2992cab228..1267156072 100644 --- a/P5/Source/Specs/citeStructure.xml +++ b/P5/Source/Specs/citeStructure.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/citedRange.xml b/P5/Source/Specs/citedRange.xml index 658a506ce0..96ab927cc7 100644 --- a/P5/Source/Specs/citedRange.xml +++ b/P5/Source/Specs/citedRange.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/cl.xml b/P5/Source/Specs/cl.xml index 2b5d42838a..ffb6558a25 100644 --- a/P5/Source/Specs/cl.xml +++ b/P5/Source/Specs/cl.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/classCode.xml b/P5/Source/Specs/classCode.xml index 0159b376af..99a61f1f23 100644 --- a/P5/Source/Specs/classCode.xml +++ b/P5/Source/Specs/classCode.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/classDecl.xml b/P5/Source/Specs/classDecl.xml index fedc67a79b..324705b85f 100644 --- a/P5/Source/Specs/classDecl.xml +++ b/P5/Source/Specs/classDecl.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/classRef.xml b/P5/Source/Specs/classRef.xml index c54c02cd8b..2b4ed3ae86 100644 --- a/P5/Source/Specs/classRef.xml +++ b/P5/Source/Specs/classRef.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/classSpec.xml b/P5/Source/Specs/classSpec.xml index bd2ba92970..35b92073eb 100644 --- a/P5/Source/Specs/classSpec.xml +++ b/P5/Source/Specs/classSpec.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/classes.xml b/P5/Source/Specs/classes.xml index 600a936395..5ae286a64a 100644 --- a/P5/Source/Specs/classes.xml +++ b/P5/Source/Specs/classes.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/closer.xml b/P5/Source/Specs/closer.xml index 7cf7854dc8..d62ca55468 100644 --- a/P5/Source/Specs/closer.xml +++ b/P5/Source/Specs/closer.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/code.xml b/P5/Source/Specs/code.xml index c522f2d104..4d3a193ed8 100644 --- a/P5/Source/Specs/code.xml +++ b/P5/Source/Specs/code.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/collation.xml b/P5/Source/Specs/collation.xml index 9078d3d630..0763b55d71 100644 --- a/P5/Source/Specs/collation.xml +++ b/P5/Source/Specs/collation.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/collection.xml b/P5/Source/Specs/collection.xml index 7787d7a429..1b2a33d3b9 100644 --- a/P5/Source/Specs/collection.xml +++ b/P5/Source/Specs/collection.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/colloc.xml b/P5/Source/Specs/colloc.xml index f08d542912..d6ff1f2402 100644 --- a/P5/Source/Specs/colloc.xml +++ b/P5/Source/Specs/colloc.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/colophon.xml b/P5/Source/Specs/colophon.xml index e595695616..023ef2c58a 100644 --- a/P5/Source/Specs/colophon.xml +++ b/P5/Source/Specs/colophon.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/cond.xml b/P5/Source/Specs/cond.xml index 651c00877b..075eb6604b 100644 --- a/P5/Source/Specs/cond.xml +++ b/P5/Source/Specs/cond.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/condition.xml b/P5/Source/Specs/condition.xml index 062ff74942..b8557cf82f 100644 --- a/P5/Source/Specs/condition.xml +++ b/P5/Source/Specs/condition.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/constitution.xml b/P5/Source/Specs/constitution.xml index 7db2fdf463..1a93567456 100644 --- a/P5/Source/Specs/constitution.xml +++ b/P5/Source/Specs/constitution.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/constraint.xml b/P5/Source/Specs/constraint.xml index a174228e3e..0fed8d29f4 100644 --- a/P5/Source/Specs/constraint.xml +++ b/P5/Source/Specs/constraint.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/constraintSpec.xml b/P5/Source/Specs/constraintSpec.xml index d4372507c7..730a21006f 100644 --- a/P5/Source/Specs/constraintSpec.xml +++ b/P5/Source/Specs/constraintSpec.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/content.xml b/P5/Source/Specs/content.xml index 3fa014b639..0a16393c33 100644 --- a/P5/Source/Specs/content.xml +++ b/P5/Source/Specs/content.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/corr.xml b/P5/Source/Specs/corr.xml index 6625d423f2..18a41fe203 100644 --- a/P5/Source/Specs/corr.xml +++ b/P5/Source/Specs/corr.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/correction.xml b/P5/Source/Specs/correction.xml index 7544d27ae4..986ff0c72f 100644 --- a/P5/Source/Specs/correction.xml +++ b/P5/Source/Specs/correction.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/correspAction.xml b/P5/Source/Specs/correspAction.xml index e984573497..63b7665597 100644 --- a/P5/Source/Specs/correspAction.xml +++ b/P5/Source/Specs/correspAction.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/correspContext.xml b/P5/Source/Specs/correspContext.xml index 3dbdfa6896..95725f99c8 100644 --- a/P5/Source/Specs/correspContext.xml +++ b/P5/Source/Specs/correspContext.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/correspDesc.xml b/P5/Source/Specs/correspDesc.xml index f34d1f8252..61185f249b 100644 --- a/P5/Source/Specs/correspDesc.xml +++ b/P5/Source/Specs/correspDesc.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/custodialHist.xml b/P5/Source/Specs/custodialHist.xml index 8c45b16d06..63a149864d 100644 --- a/P5/Source/Specs/custodialHist.xml +++ b/P5/Source/Specs/custodialHist.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/damageSpan.xml b/P5/Source/Specs/damageSpan.xml index 78adc5279b..39c84ff87b 100644 --- a/P5/Source/Specs/damageSpan.xml +++ b/P5/Source/Specs/damageSpan.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/dataFacet.xml b/P5/Source/Specs/dataFacet.xml index 44799e9694..6954775c24 100644 --- a/P5/Source/Specs/dataFacet.xml +++ b/P5/Source/Specs/dataFacet.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/dataRef.xml b/P5/Source/Specs/dataRef.xml index 5de6997ea0..44b85684e0 100644 --- a/P5/Source/Specs/dataRef.xml +++ b/P5/Source/Specs/dataRef.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/dataSpec.xml b/P5/Source/Specs/dataSpec.xml index d8c90e46c1..4cbf602afc 100644 --- a/P5/Source/Specs/dataSpec.xml +++ b/P5/Source/Specs/dataSpec.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/datatype.xml b/P5/Source/Specs/datatype.xml index 2277562fd1..5cda5dca0b 100644 --- a/P5/Source/Specs/datatype.xml +++ b/P5/Source/Specs/datatype.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/date.xml b/P5/Source/Specs/date.xml index 709566274b..ea67955764 100644 --- a/P5/Source/Specs/date.xml +++ b/P5/Source/Specs/date.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/dateline.xml b/P5/Source/Specs/dateline.xml index 40f6626e0e..7024c733a2 100644 --- a/P5/Source/Specs/dateline.xml +++ b/P5/Source/Specs/dateline.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/decoDesc.xml b/P5/Source/Specs/decoDesc.xml index 13a9317457..ff67a4a0dd 100644 --- a/P5/Source/Specs/decoDesc.xml +++ b/P5/Source/Specs/decoDesc.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/decoNote.xml b/P5/Source/Specs/decoNote.xml index 5883c93015..0b1670c677 100644 --- a/P5/Source/Specs/decoNote.xml +++ b/P5/Source/Specs/decoNote.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/def.xml b/P5/Source/Specs/def.xml index 606675b53a..bc45f93afe 100644 --- a/P5/Source/Specs/def.xml +++ b/P5/Source/Specs/def.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/default.xml b/P5/Source/Specs/default.xml index feaa206473..2abea157b0 100644 --- a/P5/Source/Specs/default.xml +++ b/P5/Source/Specs/default.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/defaultVal.xml b/P5/Source/Specs/defaultVal.xml index d45c68a302..5d7aa6381b 100644 --- a/P5/Source/Specs/defaultVal.xml +++ b/P5/Source/Specs/defaultVal.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/del.xml b/P5/Source/Specs/del.xml index 0cafd9eeae..921f09ece1 100644 --- a/P5/Source/Specs/del.xml +++ b/P5/Source/Specs/del.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/delSpan.xml b/P5/Source/Specs/delSpan.xml index fbeea67ab8..bb11e0a97e 100644 --- a/P5/Source/Specs/delSpan.xml +++ b/P5/Source/Specs/delSpan.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/depth.xml b/P5/Source/Specs/depth.xml index d422b8a927..d127fc9cfb 100644 --- a/P5/Source/Specs/depth.xml +++ b/P5/Source/Specs/depth.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/derivation.xml b/P5/Source/Specs/derivation.xml index 2bd0f6439e..1f060134da 100644 --- a/P5/Source/Specs/derivation.xml +++ b/P5/Source/Specs/derivation.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/desc.xml b/P5/Source/Specs/desc.xml index 456113e9ab..b83b04119f 100644 --- a/P5/Source/Specs/desc.xml +++ b/P5/Source/Specs/desc.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/dictScrap.xml b/P5/Source/Specs/dictScrap.xml index 19840ec46c..035e180c62 100644 --- a/P5/Source/Specs/dictScrap.xml +++ b/P5/Source/Specs/dictScrap.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/dim.xml b/P5/Source/Specs/dim.xml index a9454860f7..3b7b15c68b 100644 --- a/P5/Source/Specs/dim.xml +++ b/P5/Source/Specs/dim.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/dimensions.xml b/P5/Source/Specs/dimensions.xml index 52b4d0dfd5..af40664086 100644 --- a/P5/Source/Specs/dimensions.xml +++ b/P5/Source/Specs/dimensions.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/distinct.xml b/P5/Source/Specs/distinct.xml index 1072eb9b40..8b4a38ebac 100644 --- a/P5/Source/Specs/distinct.xml +++ b/P5/Source/Specs/distinct.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/distributor.xml b/P5/Source/Specs/distributor.xml index 1cb8a7bbb7..0f6497090b 100644 --- a/P5/Source/Specs/distributor.xml +++ b/P5/Source/Specs/distributor.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/div.xml b/P5/Source/Specs/div.xml index 39e8c989b9..368d51c391 100644 --- a/P5/Source/Specs/div.xml +++ b/P5/Source/Specs/div.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/div1.xml b/P5/Source/Specs/div1.xml index 7200b5b6e5..1ed1c0d817 100644 --- a/P5/Source/Specs/div1.xml +++ b/P5/Source/Specs/div1.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/div2.xml b/P5/Source/Specs/div2.xml index 00fc2e827d..b569201c71 100644 --- a/P5/Source/Specs/div2.xml +++ b/P5/Source/Specs/div2.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/div3.xml b/P5/Source/Specs/div3.xml index 0ef90c0416..38126a40fd 100644 --- a/P5/Source/Specs/div3.xml +++ b/P5/Source/Specs/div3.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/div4.xml b/P5/Source/Specs/div4.xml index 77098e55f3..00e3a63e16 100644 --- a/P5/Source/Specs/div4.xml +++ b/P5/Source/Specs/div4.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/div5.xml b/P5/Source/Specs/div5.xml index 8de091464d..98ffb36330 100644 --- a/P5/Source/Specs/div5.xml +++ b/P5/Source/Specs/div5.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/div6.xml b/P5/Source/Specs/div6.xml index 8a106356c2..effa7143f1 100644 --- a/P5/Source/Specs/div6.xml +++ b/P5/Source/Specs/div6.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/div7.xml b/P5/Source/Specs/div7.xml index 7c12ef44ff..76cd431222 100644 --- a/P5/Source/Specs/div7.xml +++ b/P5/Source/Specs/div7.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/divGen.xml b/P5/Source/Specs/divGen.xml index b07284e1ea..f0fc89a123 100644 --- a/P5/Source/Specs/divGen.xml +++ b/P5/Source/Specs/divGen.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/docAuthor.xml b/P5/Source/Specs/docAuthor.xml index ebcb1fa30b..974f175a18 100644 --- a/P5/Source/Specs/docAuthor.xml +++ b/P5/Source/Specs/docAuthor.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/docDate.xml b/P5/Source/Specs/docDate.xml index 84d3bc7db5..a1762ddae6 100644 --- a/P5/Source/Specs/docDate.xml +++ b/P5/Source/Specs/docDate.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/docEdition.xml b/P5/Source/Specs/docEdition.xml index ca9b1a3a18..f7b516b48b 100644 --- a/P5/Source/Specs/docEdition.xml +++ b/P5/Source/Specs/docEdition.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/docImprint.xml b/P5/Source/Specs/docImprint.xml index 04680f550a..2a7e5ffbb6 100644 --- a/P5/Source/Specs/docImprint.xml +++ b/P5/Source/Specs/docImprint.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/docTitle.xml b/P5/Source/Specs/docTitle.xml index 6d6e15bdac..4ba9ff0707 100644 --- a/P5/Source/Specs/docTitle.xml +++ b/P5/Source/Specs/docTitle.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/domain.xml b/P5/Source/Specs/domain.xml index 75b7a63b1c..36de7e0537 100644 --- a/P5/Source/Specs/domain.xml +++ b/P5/Source/Specs/domain.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/eLeaf.xml b/P5/Source/Specs/eLeaf.xml index 3824945b89..dd2ababbb9 100644 --- a/P5/Source/Specs/eLeaf.xml +++ b/P5/Source/Specs/eLeaf.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/eTree.xml b/P5/Source/Specs/eTree.xml index c5ed6fc3d7..2db1826f14 100644 --- a/P5/Source/Specs/eTree.xml +++ b/P5/Source/Specs/eTree.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/edition.xml b/P5/Source/Specs/edition.xml index e97f543484..ad9ef780be 100644 --- a/P5/Source/Specs/edition.xml +++ b/P5/Source/Specs/edition.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/editionStmt.xml b/P5/Source/Specs/editionStmt.xml index 0361735562..e77529a1c5 100644 --- a/P5/Source/Specs/editionStmt.xml +++ b/P5/Source/Specs/editionStmt.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/editorialDecl.xml b/P5/Source/Specs/editorialDecl.xml index 99fadb634a..ef6caf312b 100644 --- a/P5/Source/Specs/editorialDecl.xml +++ b/P5/Source/Specs/editorialDecl.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/eg.xml b/P5/Source/Specs/eg.xml index ff6fc2ccc4..a866fb5d9d 100644 --- a/P5/Source/Specs/eg.xml +++ b/P5/Source/Specs/eg.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/egXML.xml b/P5/Source/Specs/egXML.xml index a29290d82e..e0889cfd6c 100644 --- a/P5/Source/Specs/egXML.xml +++ b/P5/Source/Specs/egXML.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/elementRef.xml b/P5/Source/Specs/elementRef.xml index 95babaa2a4..ee3077650b 100644 --- a/P5/Source/Specs/elementRef.xml +++ b/P5/Source/Specs/elementRef.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/elementSpec.xml b/P5/Source/Specs/elementSpec.xml index ca33f9e5e6..0c065a5d4f 100644 --- a/P5/Source/Specs/elementSpec.xml +++ b/P5/Source/Specs/elementSpec.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/ellipsis.xml b/P5/Source/Specs/ellipsis.xml index 6299c4932a..f9e8e31dfb 100644 --- a/P5/Source/Specs/ellipsis.xml +++ b/P5/Source/Specs/ellipsis.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/email.xml b/P5/Source/Specs/email.xml index c39c4ea84e..75c9d9058d 100644 --- a/P5/Source/Specs/email.xml +++ b/P5/Source/Specs/email.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/emph.xml b/P5/Source/Specs/emph.xml index d918421d13..22a625864e 100644 --- a/P5/Source/Specs/emph.xml +++ b/P5/Source/Specs/emph.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/empty.xml b/P5/Source/Specs/empty.xml index 663ba5de5b..daccd52c84 100644 --- a/P5/Source/Specs/empty.xml +++ b/P5/Source/Specs/empty.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/encodingDesc.xml b/P5/Source/Specs/encodingDesc.xml index 52a8b2eb94..5f393b68a9 100644 --- a/P5/Source/Specs/encodingDesc.xml +++ b/P5/Source/Specs/encodingDesc.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/entry.xml b/P5/Source/Specs/entry.xml index d2a6cb13b6..c93b53d4c6 100644 --- a/P5/Source/Specs/entry.xml +++ b/P5/Source/Specs/entry.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/entryFree.xml b/P5/Source/Specs/entryFree.xml index a88b644654..93613ffa7c 100644 --- a/P5/Source/Specs/entryFree.xml +++ b/P5/Source/Specs/entryFree.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/epigraph.xml b/P5/Source/Specs/epigraph.xml index 0bf803b7fa..0b9e75656f 100644 --- a/P5/Source/Specs/epigraph.xml +++ b/P5/Source/Specs/epigraph.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/epilogue.xml b/P5/Source/Specs/epilogue.xml index 7575f42858..6d8e6feeee 100644 --- a/P5/Source/Specs/epilogue.xml +++ b/P5/Source/Specs/epilogue.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/equipment.xml b/P5/Source/Specs/equipment.xml index 8aacead70f..dd63dbdd67 100644 --- a/P5/Source/Specs/equipment.xml +++ b/P5/Source/Specs/equipment.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/equiv.xml b/P5/Source/Specs/equiv.xml index f52b301199..5109b7e769 100644 --- a/P5/Source/Specs/equiv.xml +++ b/P5/Source/Specs/equiv.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/etym.xml b/P5/Source/Specs/etym.xml index df05226923..e4c5a9816b 100644 --- a/P5/Source/Specs/etym.xml +++ b/P5/Source/Specs/etym.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/event.xml b/P5/Source/Specs/event.xml index 1902d9df0d..51979fb276 100644 --- a/P5/Source/Specs/event.xml +++ b/P5/Source/Specs/event.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/eventName.xml b/P5/Source/Specs/eventName.xml index 16a33b74f2..fd76bcc327 100644 --- a/P5/Source/Specs/eventName.xml +++ b/P5/Source/Specs/eventName.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/ex.xml b/P5/Source/Specs/ex.xml index 2eea604d73..fd9315b5d3 100644 --- a/P5/Source/Specs/ex.xml +++ b/P5/Source/Specs/ex.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/exemplum.xml b/P5/Source/Specs/exemplum.xml index 84bd2bbdda..5bb19cb7d0 100644 --- a/P5/Source/Specs/exemplum.xml +++ b/P5/Source/Specs/exemplum.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/expan.xml b/P5/Source/Specs/expan.xml index f892e1b14f..4602e558e1 100644 --- a/P5/Source/Specs/expan.xml +++ b/P5/Source/Specs/expan.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/explicit.xml b/P5/Source/Specs/explicit.xml index dce7ce320d..f04a365de5 100644 --- a/P5/Source/Specs/explicit.xml +++ b/P5/Source/Specs/explicit.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/extent.xml b/P5/Source/Specs/extent.xml index c702bf7ba8..af9ea8b811 100644 --- a/P5/Source/Specs/extent.xml +++ b/P5/Source/Specs/extent.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/f.xml b/P5/Source/Specs/f.xml index 18ca1fba66..fc21582245 100644 --- a/P5/Source/Specs/f.xml +++ b/P5/Source/Specs/f.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/fDecl.xml b/P5/Source/Specs/fDecl.xml index 5e94d789f9..d31d8ec638 100644 --- a/P5/Source/Specs/fDecl.xml +++ b/P5/Source/Specs/fDecl.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/fDescr.xml b/P5/Source/Specs/fDescr.xml index bffcee4ac8..0d24fff402 100644 --- a/P5/Source/Specs/fDescr.xml +++ b/P5/Source/Specs/fDescr.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/fLib.xml b/P5/Source/Specs/fLib.xml index b7645f61c3..c2a9514f1f 100644 --- a/P5/Source/Specs/fLib.xml +++ b/P5/Source/Specs/fLib.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/facsimile.xml b/P5/Source/Specs/facsimile.xml index a97e0a346b..5adeacaa4e 100644 --- a/P5/Source/Specs/facsimile.xml +++ b/P5/Source/Specs/facsimile.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/factuality.xml b/P5/Source/Specs/factuality.xml index 8a664c5fa2..b505238511 100644 --- a/P5/Source/Specs/factuality.xml +++ b/P5/Source/Specs/factuality.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/figDesc.xml b/P5/Source/Specs/figDesc.xml index d6c79130db..ff42825bc6 100644 --- a/P5/Source/Specs/figDesc.xml +++ b/P5/Source/Specs/figDesc.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/figure.xml b/P5/Source/Specs/figure.xml index f61c5c06d7..bba891c05e 100644 --- a/P5/Source/Specs/figure.xml +++ b/P5/Source/Specs/figure.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/fileDesc.xml b/P5/Source/Specs/fileDesc.xml index c32b869120..71817e08fa 100644 --- a/P5/Source/Specs/fileDesc.xml +++ b/P5/Source/Specs/fileDesc.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/filiation.xml b/P5/Source/Specs/filiation.xml index 213c38dbb1..8d34706eac 100644 --- a/P5/Source/Specs/filiation.xml +++ b/P5/Source/Specs/filiation.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/finalRubric.xml b/P5/Source/Specs/finalRubric.xml index d36766bfe3..4698e6e34e 100644 --- a/P5/Source/Specs/finalRubric.xml +++ b/P5/Source/Specs/finalRubric.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/floatingText.xml b/P5/Source/Specs/floatingText.xml index f97cec2d38..b54546da6d 100644 --- a/P5/Source/Specs/floatingText.xml +++ b/P5/Source/Specs/floatingText.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/foliation.xml b/P5/Source/Specs/foliation.xml index 235e69008a..f4ecf6e06e 100644 --- a/P5/Source/Specs/foliation.xml +++ b/P5/Source/Specs/foliation.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/foreign.xml b/P5/Source/Specs/foreign.xml index fc9247d40a..9eeb2fd526 100644 --- a/P5/Source/Specs/foreign.xml +++ b/P5/Source/Specs/foreign.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/forename.xml b/P5/Source/Specs/forename.xml index 1877c1f7cf..9b24e9ace0 100644 --- a/P5/Source/Specs/forename.xml +++ b/P5/Source/Specs/forename.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/forest.xml b/P5/Source/Specs/forest.xml index 124df837a2..8b2855b64c 100644 --- a/P5/Source/Specs/forest.xml +++ b/P5/Source/Specs/forest.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/form.xml b/P5/Source/Specs/form.xml index 7745d6b013..d52cb803ab 100644 --- a/P5/Source/Specs/form.xml +++ b/P5/Source/Specs/form.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/formula.xml b/P5/Source/Specs/formula.xml index d1f3b6e0ee..00c871f755 100644 --- a/P5/Source/Specs/formula.xml +++ b/P5/Source/Specs/formula.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/front.xml b/P5/Source/Specs/front.xml index f2b5eea61e..06bef4f50e 100644 --- a/P5/Source/Specs/front.xml +++ b/P5/Source/Specs/front.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/fs.xml b/P5/Source/Specs/fs.xml index 6298a58894..c62b4e84fb 100644 --- a/P5/Source/Specs/fs.xml +++ b/P5/Source/Specs/fs.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/fsConstraints.xml b/P5/Source/Specs/fsConstraints.xml index fdb36a3d17..1062e69845 100644 --- a/P5/Source/Specs/fsConstraints.xml +++ b/P5/Source/Specs/fsConstraints.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/fsDecl.xml b/P5/Source/Specs/fsDecl.xml index 80824faec2..13ce5aacb5 100644 --- a/P5/Source/Specs/fsDecl.xml +++ b/P5/Source/Specs/fsDecl.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/fsDescr.xml b/P5/Source/Specs/fsDescr.xml index 8412c4cc63..3906c7054a 100644 --- a/P5/Source/Specs/fsDescr.xml +++ b/P5/Source/Specs/fsDescr.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/fsdDecl.xml b/P5/Source/Specs/fsdDecl.xml index f925669f9f..96cd1f1bbd 100644 --- a/P5/Source/Specs/fsdDecl.xml +++ b/P5/Source/Specs/fsdDecl.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/fsdLink.xml b/P5/Source/Specs/fsdLink.xml index beba71bcd0..0d13671f7f 100644 --- a/P5/Source/Specs/fsdLink.xml +++ b/P5/Source/Specs/fsdLink.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/fvLib.xml b/P5/Source/Specs/fvLib.xml index 928faec915..3003d9959d 100644 --- a/P5/Source/Specs/fvLib.xml +++ b/P5/Source/Specs/fvLib.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/fw.xml b/P5/Source/Specs/fw.xml index 37927f3111..e0689bf233 100644 --- a/P5/Source/Specs/fw.xml +++ b/P5/Source/Specs/fw.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/g.xml b/P5/Source/Specs/g.xml index 96528f1c51..b7ee6383f2 100644 --- a/P5/Source/Specs/g.xml +++ b/P5/Source/Specs/g.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/gap.xml b/P5/Source/Specs/gap.xml index 216734fe88..ef715fd3c7 100644 --- a/P5/Source/Specs/gap.xml +++ b/P5/Source/Specs/gap.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/gb.xml b/P5/Source/Specs/gb.xml index fb2d89919a..44b80bc33b 100644 --- a/P5/Source/Specs/gb.xml +++ b/P5/Source/Specs/gb.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/gen.xml b/P5/Source/Specs/gen.xml index 9c3d63e449..f3a197c8ae 100644 --- a/P5/Source/Specs/gen.xml +++ b/P5/Source/Specs/gen.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/genName.xml b/P5/Source/Specs/genName.xml index b2cbfa4e34..84552c75ff 100644 --- a/P5/Source/Specs/genName.xml +++ b/P5/Source/Specs/genName.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/geo.xml b/P5/Source/Specs/geo.xml index 75cb35e44f..6b431e97aa 100644 --- a/P5/Source/Specs/geo.xml +++ b/P5/Source/Specs/geo.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/geoDecl.xml b/P5/Source/Specs/geoDecl.xml index 461e6d109d..f15b783c8a 100644 --- a/P5/Source/Specs/geoDecl.xml +++ b/P5/Source/Specs/geoDecl.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/gi.xml b/P5/Source/Specs/gi.xml index 57e953156d..1d603e90a7 100644 --- a/P5/Source/Specs/gi.xml +++ b/P5/Source/Specs/gi.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/gloss.xml b/P5/Source/Specs/gloss.xml index 78e3a546ee..1248276ca9 100644 --- a/P5/Source/Specs/gloss.xml +++ b/P5/Source/Specs/gloss.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/glyph.xml b/P5/Source/Specs/glyph.xml index f93c75c354..d18376ccb8 100644 --- a/P5/Source/Specs/glyph.xml +++ b/P5/Source/Specs/glyph.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/gram.xml b/P5/Source/Specs/gram.xml index 1e71133303..7c8216fdd8 100644 --- a/P5/Source/Specs/gram.xml +++ b/P5/Source/Specs/gram.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/gramGrp.xml b/P5/Source/Specs/gramGrp.xml index 11684c3d89..a32f855a22 100644 --- a/P5/Source/Specs/gramGrp.xml +++ b/P5/Source/Specs/gramGrp.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/graph.xml b/P5/Source/Specs/graph.xml index 4a6ed4df6b..ae8a2e5352 100644 --- a/P5/Source/Specs/graph.xml +++ b/P5/Source/Specs/graph.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/graphic.xml b/P5/Source/Specs/graphic.xml index 484b498b96..785dedf488 100644 --- a/P5/Source/Specs/graphic.xml +++ b/P5/Source/Specs/graphic.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/group.xml b/P5/Source/Specs/group.xml index 3c1e70c7ef..250606b879 100644 --- a/P5/Source/Specs/group.xml +++ b/P5/Source/Specs/group.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/handDesc.xml b/P5/Source/Specs/handDesc.xml index 5502f8cf3b..9c334f76ec 100644 --- a/P5/Source/Specs/handDesc.xml +++ b/P5/Source/Specs/handDesc.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/handNote.xml b/P5/Source/Specs/handNote.xml index a3f276004f..fb50a57c50 100644 --- a/P5/Source/Specs/handNote.xml +++ b/P5/Source/Specs/handNote.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/handNotes.xml b/P5/Source/Specs/handNotes.xml index 0bda313232..0d9bb6fd17 100644 --- a/P5/Source/Specs/handNotes.xml +++ b/P5/Source/Specs/handNotes.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/handShift.xml b/P5/Source/Specs/handShift.xml index c1b125314c..d9db2cf54e 100644 --- a/P5/Source/Specs/handShift.xml +++ b/P5/Source/Specs/handShift.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/head.xml b/P5/Source/Specs/head.xml index 044a79606a..82593026ba 100644 --- a/P5/Source/Specs/head.xml +++ b/P5/Source/Specs/head.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/headItem.xml b/P5/Source/Specs/headItem.xml index d56ac58f59..ee23a7f20f 100644 --- a/P5/Source/Specs/headItem.xml +++ b/P5/Source/Specs/headItem.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/headLabel.xml b/P5/Source/Specs/headLabel.xml index 5654aa3589..2aab40ad81 100644 --- a/P5/Source/Specs/headLabel.xml +++ b/P5/Source/Specs/headLabel.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/height.xml b/P5/Source/Specs/height.xml index 6955af7abc..7b0519755f 100644 --- a/P5/Source/Specs/height.xml +++ b/P5/Source/Specs/height.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/heraldry.xml b/P5/Source/Specs/heraldry.xml index 157d67fe9f..816133e3fe 100644 --- a/P5/Source/Specs/heraldry.xml +++ b/P5/Source/Specs/heraldry.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/hi.xml b/P5/Source/Specs/hi.xml index 38d552d7d7..27538b990a 100644 --- a/P5/Source/Specs/hi.xml +++ b/P5/Source/Specs/hi.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/history.xml b/P5/Source/Specs/history.xml index 33acee2629..372b9160fe 100644 --- a/P5/Source/Specs/history.xml +++ b/P5/Source/Specs/history.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/hom.xml b/P5/Source/Specs/hom.xml index de6f25101c..e0708cec05 100644 --- a/P5/Source/Specs/hom.xml +++ b/P5/Source/Specs/hom.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/hyph.xml b/P5/Source/Specs/hyph.xml index de8cb05498..ac45dd7e88 100644 --- a/P5/Source/Specs/hyph.xml +++ b/P5/Source/Specs/hyph.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/hyphenation.xml b/P5/Source/Specs/hyphenation.xml index 8788509470..02c8821df3 100644 --- a/P5/Source/Specs/hyphenation.xml +++ b/P5/Source/Specs/hyphenation.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/iNode.xml b/P5/Source/Specs/iNode.xml index 3f504ce3a1..0c1fdfa15d 100644 --- a/P5/Source/Specs/iNode.xml +++ b/P5/Source/Specs/iNode.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/iType.xml b/P5/Source/Specs/iType.xml index 5d17618783..2c1491ea85 100644 --- a/P5/Source/Specs/iType.xml +++ b/P5/Source/Specs/iType.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/ident.xml b/P5/Source/Specs/ident.xml index 8f6e42e8fe..e619eb3e00 100644 --- a/P5/Source/Specs/ident.xml +++ b/P5/Source/Specs/ident.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/if.xml b/P5/Source/Specs/if.xml index ec21615270..6e32083c09 100644 --- a/P5/Source/Specs/if.xml +++ b/P5/Source/Specs/if.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/iff.xml b/P5/Source/Specs/iff.xml index 2ea5058680..0a506718cc 100644 --- a/P5/Source/Specs/iff.xml +++ b/P5/Source/Specs/iff.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/imprimatur.xml b/P5/Source/Specs/imprimatur.xml index dfe6eb7348..5abd8d91eb 100644 --- a/P5/Source/Specs/imprimatur.xml +++ b/P5/Source/Specs/imprimatur.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/imprint.xml b/P5/Source/Specs/imprint.xml index 4de2c11dca..a61b0d1fa8 100644 --- a/P5/Source/Specs/imprint.xml +++ b/P5/Source/Specs/imprint.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/incident.xml b/P5/Source/Specs/incident.xml index 897b8ab58e..c7c434419d 100644 --- a/P5/Source/Specs/incident.xml +++ b/P5/Source/Specs/incident.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/incipit.xml b/P5/Source/Specs/incipit.xml index a3db06c937..24b7f3ac16 100644 --- a/P5/Source/Specs/incipit.xml +++ b/P5/Source/Specs/incipit.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/index.xml b/P5/Source/Specs/index.xml index 99f022c5bf..34d581418e 100644 --- a/P5/Source/Specs/index.xml +++ b/P5/Source/Specs/index.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/institution.xml b/P5/Source/Specs/institution.xml index 9e5fb18b2a..b40c2ca634 100644 --- a/P5/Source/Specs/institution.xml +++ b/P5/Source/Specs/institution.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/interaction.xml b/P5/Source/Specs/interaction.xml index 34ec2d8803..7754feb09a 100644 --- a/P5/Source/Specs/interaction.xml +++ b/P5/Source/Specs/interaction.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/interp.xml b/P5/Source/Specs/interp.xml index 207f4324c5..f7e47b68fa 100644 --- a/P5/Source/Specs/interp.xml +++ b/P5/Source/Specs/interp.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/interpGrp.xml b/P5/Source/Specs/interpGrp.xml index 754f723f6e..9b0b5cce97 100644 --- a/P5/Source/Specs/interpGrp.xml +++ b/P5/Source/Specs/interpGrp.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/interpretation.xml b/P5/Source/Specs/interpretation.xml index 52aa24ada9..76fb98af6e 100644 --- a/P5/Source/Specs/interpretation.xml +++ b/P5/Source/Specs/interpretation.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/item.xml b/P5/Source/Specs/item.xml index ee76e6984f..633fec8101 100644 --- a/P5/Source/Specs/item.xml +++ b/P5/Source/Specs/item.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/join.xml b/P5/Source/Specs/join.xml index 3ea81278ff..676e232121 100644 --- a/P5/Source/Specs/join.xml +++ b/P5/Source/Specs/join.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/joinGrp.xml b/P5/Source/Specs/joinGrp.xml index 2473c6af84..78ec57a710 100644 --- a/P5/Source/Specs/joinGrp.xml +++ b/P5/Source/Specs/joinGrp.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/keywords.xml b/P5/Source/Specs/keywords.xml index 0aa4daec7b..3f6b7a752e 100644 --- a/P5/Source/Specs/keywords.xml +++ b/P5/Source/Specs/keywords.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/kinesic.xml b/P5/Source/Specs/kinesic.xml index b2ce01a9bc..ca3627b025 100644 --- a/P5/Source/Specs/kinesic.xml +++ b/P5/Source/Specs/kinesic.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/l.xml b/P5/Source/Specs/l.xml index 6ce96e2937..c8658bb7ff 100644 --- a/P5/Source/Specs/l.xml +++ b/P5/Source/Specs/l.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/label.xml b/P5/Source/Specs/label.xml index 8fcffea4b6..46803c5e47 100644 --- a/P5/Source/Specs/label.xml +++ b/P5/Source/Specs/label.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/lacunaEnd.xml b/P5/Source/Specs/lacunaEnd.xml index c202f074a3..03e6b06fee 100644 --- a/P5/Source/Specs/lacunaEnd.xml +++ b/P5/Source/Specs/lacunaEnd.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/lacunaStart.xml b/P5/Source/Specs/lacunaStart.xml index 470c2eeda1..60c7eb588a 100644 --- a/P5/Source/Specs/lacunaStart.xml +++ b/P5/Source/Specs/lacunaStart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/lang.xml b/P5/Source/Specs/lang.xml index fadc375705..4bccd75d18 100644 --- a/P5/Source/Specs/lang.xml +++ b/P5/Source/Specs/lang.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/langUsage.xml b/P5/Source/Specs/langUsage.xml index c98816d9b6..877e6b75bf 100644 --- a/P5/Source/Specs/langUsage.xml +++ b/P5/Source/Specs/langUsage.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/language.xml b/P5/Source/Specs/language.xml index 2f0b0a198a..2d3715148c 100644 --- a/P5/Source/Specs/language.xml +++ b/P5/Source/Specs/language.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/layout.xml b/P5/Source/Specs/layout.xml index 10d211629b..fd1697ebc1 100644 --- a/P5/Source/Specs/layout.xml +++ b/P5/Source/Specs/layout.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/layoutDesc.xml b/P5/Source/Specs/layoutDesc.xml index 12404fd0ae..d0f0f79925 100644 --- a/P5/Source/Specs/layoutDesc.xml +++ b/P5/Source/Specs/layoutDesc.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/lb.xml b/P5/Source/Specs/lb.xml index 20d1d12c0b..729d8b207b 100644 --- a/P5/Source/Specs/lb.xml +++ b/P5/Source/Specs/lb.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/lbl.xml b/P5/Source/Specs/lbl.xml index be29884354..00a5cbacc4 100644 --- a/P5/Source/Specs/lbl.xml +++ b/P5/Source/Specs/lbl.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/leaf.xml b/P5/Source/Specs/leaf.xml index ff5bc06eb4..0407e423af 100644 --- a/P5/Source/Specs/leaf.xml +++ b/P5/Source/Specs/leaf.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/lg.xml b/P5/Source/Specs/lg.xml index 236f42407e..904310e6a7 100644 --- a/P5/Source/Specs/lg.xml +++ b/P5/Source/Specs/lg.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/line.xml b/P5/Source/Specs/line.xml index c964955051..fcc1831531 100644 --- a/P5/Source/Specs/line.xml +++ b/P5/Source/Specs/line.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/link.xml b/P5/Source/Specs/link.xml index 53d6a029cb..52f5fa6ffa 100644 --- a/P5/Source/Specs/link.xml +++ b/P5/Source/Specs/link.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/linkGrp.xml b/P5/Source/Specs/linkGrp.xml index c69cba235e..c9a3d8ea37 100644 --- a/P5/Source/Specs/linkGrp.xml +++ b/P5/Source/Specs/linkGrp.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/list.xml b/P5/Source/Specs/list.xml index 5f965639ae..0fc538af51 100644 --- a/P5/Source/Specs/list.xml +++ b/P5/Source/Specs/list.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/listAnnotation.xml b/P5/Source/Specs/listAnnotation.xml index 4d0c6c9af4..4de68c2b20 100644 --- a/P5/Source/Specs/listAnnotation.xml +++ b/P5/Source/Specs/listAnnotation.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/listChange.xml b/P5/Source/Specs/listChange.xml index f18dcc2f6a..c9d3a0db37 100644 --- a/P5/Source/Specs/listChange.xml +++ b/P5/Source/Specs/listChange.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/listEvent.xml b/P5/Source/Specs/listEvent.xml index 9b82a6b07d..2a9465b1ad 100644 --- a/P5/Source/Specs/listEvent.xml +++ b/P5/Source/Specs/listEvent.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/listForest.xml b/P5/Source/Specs/listForest.xml index 6aaafc3d48..ba40ab4ba2 100644 --- a/P5/Source/Specs/listForest.xml +++ b/P5/Source/Specs/listForest.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/listNym.xml b/P5/Source/Specs/listNym.xml index d4d5b53c20..3484bd324f 100644 --- a/P5/Source/Specs/listNym.xml +++ b/P5/Source/Specs/listNym.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/listObject.xml b/P5/Source/Specs/listObject.xml index 3fba9dd5e0..d5ae2075b1 100644 --- a/P5/Source/Specs/listObject.xml +++ b/P5/Source/Specs/listObject.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/listOrg.xml b/P5/Source/Specs/listOrg.xml index 35d0dc7d76..7cde9a8430 100644 --- a/P5/Source/Specs/listOrg.xml +++ b/P5/Source/Specs/listOrg.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/listPerson.xml b/P5/Source/Specs/listPerson.xml index fa5d589253..2901787068 100644 --- a/P5/Source/Specs/listPerson.xml +++ b/P5/Source/Specs/listPerson.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/listPlace.xml b/P5/Source/Specs/listPlace.xml index 67e5dca76a..4fd1e6d0a4 100644 --- a/P5/Source/Specs/listPlace.xml +++ b/P5/Source/Specs/listPlace.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/listPrefixDef.xml b/P5/Source/Specs/listPrefixDef.xml index d62136ef0c..23b467cedb 100644 --- a/P5/Source/Specs/listPrefixDef.xml +++ b/P5/Source/Specs/listPrefixDef.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/listRef.xml b/P5/Source/Specs/listRef.xml index d4d888cee7..753935ac94 100644 --- a/P5/Source/Specs/listRef.xml +++ b/P5/Source/Specs/listRef.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/listRelation.xml b/P5/Source/Specs/listRelation.xml index d1510dbe9f..81e321d2bd 100644 --- a/P5/Source/Specs/listRelation.xml +++ b/P5/Source/Specs/listRelation.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/listTranspose.xml b/P5/Source/Specs/listTranspose.xml index 53507ffd4f..35758e0cfc 100644 --- a/P5/Source/Specs/listTranspose.xml +++ b/P5/Source/Specs/listTranspose.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/listWit.xml b/P5/Source/Specs/listWit.xml index 76bb5f9dcc..71e25eedac 100644 --- a/P5/Source/Specs/listWit.xml +++ b/P5/Source/Specs/listWit.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/localProp.xml b/P5/Source/Specs/localProp.xml index 4bd08517ad..797ff3f99d 100644 --- a/P5/Source/Specs/localProp.xml +++ b/P5/Source/Specs/localProp.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/locus.xml b/P5/Source/Specs/locus.xml index 811bb7a855..05438e07cd 100644 --- a/P5/Source/Specs/locus.xml +++ b/P5/Source/Specs/locus.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/locusGrp.xml b/P5/Source/Specs/locusGrp.xml index 7ddc2b7b61..798aa873f1 100644 --- a/P5/Source/Specs/locusGrp.xml +++ b/P5/Source/Specs/locusGrp.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/m.xml b/P5/Source/Specs/m.xml index acf7cf9e38..1cb3c310e4 100644 --- a/P5/Source/Specs/m.xml +++ b/P5/Source/Specs/m.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/macro.abContent.xml b/P5/Source/Specs/macro.abContent.xml index 334fcc3b12..bbfc8461d2 100644 --- a/P5/Source/Specs/macro.abContent.xml +++ b/P5/Source/Specs/macro.abContent.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/macro.limitedContent.xml b/P5/Source/Specs/macro.limitedContent.xml index 01874ed5ff..204eb07cad 100644 --- a/P5/Source/Specs/macro.limitedContent.xml +++ b/P5/Source/Specs/macro.limitedContent.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/macro.paraContent.xml b/P5/Source/Specs/macro.paraContent.xml index 69a2a4f275..74a2771895 100644 --- a/P5/Source/Specs/macro.paraContent.xml +++ b/P5/Source/Specs/macro.paraContent.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/macro.phraseSeq.limited.xml b/P5/Source/Specs/macro.phraseSeq.limited.xml index efc9dc1dc8..dbb93623eb 100644 --- a/P5/Source/Specs/macro.phraseSeq.limited.xml +++ b/P5/Source/Specs/macro.phraseSeq.limited.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/macro.phraseSeq.xml b/P5/Source/Specs/macro.phraseSeq.xml index ffb6fd08cb..39d2fe7767 100644 --- a/P5/Source/Specs/macro.phraseSeq.xml +++ b/P5/Source/Specs/macro.phraseSeq.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/macro.specialPara.xml b/P5/Source/Specs/macro.specialPara.xml index 931b331a37..7c589d54b2 100644 --- a/P5/Source/Specs/macro.specialPara.xml +++ b/P5/Source/Specs/macro.specialPara.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/macro.xtext.xml b/P5/Source/Specs/macro.xtext.xml index e6eaeafc40..70e2073584 100644 --- a/P5/Source/Specs/macro.xtext.xml +++ b/P5/Source/Specs/macro.xtext.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/macroRef.xml b/P5/Source/Specs/macroRef.xml index 76eb78bb86..de5698dce3 100644 --- a/P5/Source/Specs/macroRef.xml +++ b/P5/Source/Specs/macroRef.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/macroSpec.xml b/P5/Source/Specs/macroSpec.xml index 039a67c863..5ec54e85be 100644 --- a/P5/Source/Specs/macroSpec.xml +++ b/P5/Source/Specs/macroSpec.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/mapping.xml b/P5/Source/Specs/mapping.xml index 35c2b5c2a0..ed766e8285 100644 --- a/P5/Source/Specs/mapping.xml +++ b/P5/Source/Specs/mapping.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/material.xml b/P5/Source/Specs/material.xml index b874df85cb..099a08c612 100644 --- a/P5/Source/Specs/material.xml +++ b/P5/Source/Specs/material.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/measure.xml b/P5/Source/Specs/measure.xml index 78f8d26b9a..c28e598124 100644 --- a/P5/Source/Specs/measure.xml +++ b/P5/Source/Specs/measure.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/measureGrp.xml b/P5/Source/Specs/measureGrp.xml index 764e9feb13..d5c9314e9a 100644 --- a/P5/Source/Specs/measureGrp.xml +++ b/P5/Source/Specs/measureGrp.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/media.xml b/P5/Source/Specs/media.xml index 79b94f79a9..ea14edfa18 100644 --- a/P5/Source/Specs/media.xml +++ b/P5/Source/Specs/media.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/memberOf.xml b/P5/Source/Specs/memberOf.xml index d65b7cc231..c10c9e3397 100644 --- a/P5/Source/Specs/memberOf.xml +++ b/P5/Source/Specs/memberOf.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/mentioned.xml b/P5/Source/Specs/mentioned.xml index 102bff58cb..a665e7e67c 100644 --- a/P5/Source/Specs/mentioned.xml +++ b/P5/Source/Specs/mentioned.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/metDecl.xml b/P5/Source/Specs/metDecl.xml index 67e137bd56..a02918702c 100644 --- a/P5/Source/Specs/metDecl.xml +++ b/P5/Source/Specs/metDecl.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/metSym.xml b/P5/Source/Specs/metSym.xml index deb5f32d8c..b966ea0ece 100644 --- a/P5/Source/Specs/metSym.xml +++ b/P5/Source/Specs/metSym.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/metamark.xml b/P5/Source/Specs/metamark.xml index 69855f11a2..5f6f9935fa 100644 --- a/P5/Source/Specs/metamark.xml +++ b/P5/Source/Specs/metamark.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/milestone.xml b/P5/Source/Specs/milestone.xml index 1a70a9ee47..d42a00d3be 100644 --- a/P5/Source/Specs/milestone.xml +++ b/P5/Source/Specs/milestone.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/mod.xml b/P5/Source/Specs/mod.xml index 98e3f4b768..9d9a668621 100644 --- a/P5/Source/Specs/mod.xml +++ b/P5/Source/Specs/mod.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.addrPart.xml b/P5/Source/Specs/model.addrPart.xml index 847584ab25..7ba411f4c1 100644 --- a/P5/Source/Specs/model.addrPart.xml +++ b/P5/Source/Specs/model.addrPart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.addressLike.xml b/P5/Source/Specs/model.addressLike.xml index f8634bf901..b0cb56b841 100644 --- a/P5/Source/Specs/model.addressLike.xml +++ b/P5/Source/Specs/model.addressLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.annotationLike.xml b/P5/Source/Specs/model.annotationLike.xml index ef3037faa7..2f3b0648d6 100644 --- a/P5/Source/Specs/model.annotationLike.xml +++ b/P5/Source/Specs/model.annotationLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.annotationPart.body.xml b/P5/Source/Specs/model.annotationPart.body.xml index da785f57b1..4ed5fe24b5 100644 --- a/P5/Source/Specs/model.annotationPart.body.xml +++ b/P5/Source/Specs/model.annotationPart.body.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.applicationLike.xml b/P5/Source/Specs/model.applicationLike.xml index 5dd5316e47..7ef827e172 100644 --- a/P5/Source/Specs/model.applicationLike.xml +++ b/P5/Source/Specs/model.applicationLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.availabilityPart.xml b/P5/Source/Specs/model.availabilityPart.xml index 4075da2b94..6203ff3fe5 100644 --- a/P5/Source/Specs/model.availabilityPart.xml +++ b/P5/Source/Specs/model.availabilityPart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.biblLike.xml b/P5/Source/Specs/model.biblLike.xml index 0ef6a0ef2d..f153110052 100644 --- a/P5/Source/Specs/model.biblLike.xml +++ b/P5/Source/Specs/model.biblLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.biblPart.xml b/P5/Source/Specs/model.biblPart.xml index 8be9a7204b..fe071e78f6 100644 --- a/P5/Source/Specs/model.biblPart.xml +++ b/P5/Source/Specs/model.biblPart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.castItemPart.xml b/P5/Source/Specs/model.castItemPart.xml index cd34fa265f..4c12d14030 100644 --- a/P5/Source/Specs/model.castItemPart.xml +++ b/P5/Source/Specs/model.castItemPart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.catDescPart.xml b/P5/Source/Specs/model.catDescPart.xml index 1fb3154064..3caed96273 100644 --- a/P5/Source/Specs/model.catDescPart.xml +++ b/P5/Source/Specs/model.catDescPart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.certLike.xml b/P5/Source/Specs/model.certLike.xml index 36cc33bc97..7d3b910a1d 100644 --- a/P5/Source/Specs/model.certLike.xml +++ b/P5/Source/Specs/model.certLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.choicePart.xml b/P5/Source/Specs/model.choicePart.xml index e5751b9830..e36a7706e4 100644 --- a/P5/Source/Specs/model.choicePart.xml +++ b/P5/Source/Specs/model.choicePart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.common.xml b/P5/Source/Specs/model.common.xml index a280903eb3..3a8345c6a4 100644 --- a/P5/Source/Specs/model.common.xml +++ b/P5/Source/Specs/model.common.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.contentPart.xml b/P5/Source/Specs/model.contentPart.xml index 4f632739e1..6f6a58baa3 100644 --- a/P5/Source/Specs/model.contentPart.xml +++ b/P5/Source/Specs/model.contentPart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.correspActionPart.xml b/P5/Source/Specs/model.correspActionPart.xml index d21ce9fae8..5fce18c220 100644 --- a/P5/Source/Specs/model.correspActionPart.xml +++ b/P5/Source/Specs/model.correspActionPart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.correspContextPart.xml b/P5/Source/Specs/model.correspContextPart.xml index 571b58d3ec..c5aa85f88e 100644 --- a/P5/Source/Specs/model.correspContextPart.xml +++ b/P5/Source/Specs/model.correspContextPart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.correspDescPart.xml b/P5/Source/Specs/model.correspDescPart.xml index bc7361c439..d9fec20b59 100644 --- a/P5/Source/Specs/model.correspDescPart.xml +++ b/P5/Source/Specs/model.correspDescPart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.dateLike.xml b/P5/Source/Specs/model.dateLike.xml index cc5e64f093..6e90e0a624 100644 --- a/P5/Source/Specs/model.dateLike.xml +++ b/P5/Source/Specs/model.dateLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.descLike.xml b/P5/Source/Specs/model.descLike.xml index 2156d0fe50..bc0b30bc33 100644 --- a/P5/Source/Specs/model.descLike.xml +++ b/P5/Source/Specs/model.descLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.describedResource.xml b/P5/Source/Specs/model.describedResource.xml index d23feec3a8..cd32d9dd5a 100644 --- a/P5/Source/Specs/model.describedResource.xml +++ b/P5/Source/Specs/model.describedResource.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.dimLike.xml b/P5/Source/Specs/model.dimLike.xml index 582c736f6e..875460f33c 100644 --- a/P5/Source/Specs/model.dimLike.xml +++ b/P5/Source/Specs/model.dimLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.div1Like.xml b/P5/Source/Specs/model.div1Like.xml index 75ed9ca237..8949d95c77 100644 --- a/P5/Source/Specs/model.div1Like.xml +++ b/P5/Source/Specs/model.div1Like.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.div2Like.xml b/P5/Source/Specs/model.div2Like.xml index f641e7d38a..3305b2d5e5 100644 --- a/P5/Source/Specs/model.div2Like.xml +++ b/P5/Source/Specs/model.div2Like.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.div3Like.xml b/P5/Source/Specs/model.div3Like.xml index 170fe3dafe..0a7d22ae4d 100644 --- a/P5/Source/Specs/model.div3Like.xml +++ b/P5/Source/Specs/model.div3Like.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.div4Like.xml b/P5/Source/Specs/model.div4Like.xml index 21403a6383..e1985e8b0e 100644 --- a/P5/Source/Specs/model.div4Like.xml +++ b/P5/Source/Specs/model.div4Like.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.div5Like.xml b/P5/Source/Specs/model.div5Like.xml index d1fbe5b62a..9200705136 100644 --- a/P5/Source/Specs/model.div5Like.xml +++ b/P5/Source/Specs/model.div5Like.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.div6Like.xml b/P5/Source/Specs/model.div6Like.xml index 69c74d0dcd..5cae7f5656 100644 --- a/P5/Source/Specs/model.div6Like.xml +++ b/P5/Source/Specs/model.div6Like.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.div7Like.xml b/P5/Source/Specs/model.div7Like.xml index 0f3bb314bb..819acfd4d5 100644 --- a/P5/Source/Specs/model.div7Like.xml +++ b/P5/Source/Specs/model.div7Like.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.divBottom.xml b/P5/Source/Specs/model.divBottom.xml index 45ccdefce6..1fd3bc39ee 100644 --- a/P5/Source/Specs/model.divBottom.xml +++ b/P5/Source/Specs/model.divBottom.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.divBottomPart.xml b/P5/Source/Specs/model.divBottomPart.xml index be152a9006..6175322295 100644 --- a/P5/Source/Specs/model.divBottomPart.xml +++ b/P5/Source/Specs/model.divBottomPart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.divGenLike.xml b/P5/Source/Specs/model.divGenLike.xml index a9374d82a2..db05db0e83 100644 --- a/P5/Source/Specs/model.divGenLike.xml +++ b/P5/Source/Specs/model.divGenLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.divLike.xml b/P5/Source/Specs/model.divLike.xml index 9b16663607..5bb834f6f7 100644 --- a/P5/Source/Specs/model.divLike.xml +++ b/P5/Source/Specs/model.divLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.divPart.spoken.xml b/P5/Source/Specs/model.divPart.spoken.xml index d27191ad49..6b19d4ec7d 100644 --- a/P5/Source/Specs/model.divPart.spoken.xml +++ b/P5/Source/Specs/model.divPart.spoken.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.divPart.xml b/P5/Source/Specs/model.divPart.xml index a322a9803f..85b74f98ec 100644 --- a/P5/Source/Specs/model.divPart.xml +++ b/P5/Source/Specs/model.divPart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.divTop.xml b/P5/Source/Specs/model.divTop.xml index 83ab4ca3e8..336d6e3c96 100644 --- a/P5/Source/Specs/model.divTop.xml +++ b/P5/Source/Specs/model.divTop.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.divTopPart.xml b/P5/Source/Specs/model.divTopPart.xml index 30314ebd9c..5038063ad9 100644 --- a/P5/Source/Specs/model.divTopPart.xml +++ b/P5/Source/Specs/model.divTopPart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.divWrapper.xml b/P5/Source/Specs/model.divWrapper.xml index 2844c3759e..c8c0f0bbda 100644 --- a/P5/Source/Specs/model.divWrapper.xml +++ b/P5/Source/Specs/model.divWrapper.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.editorialDeclPart.xml b/P5/Source/Specs/model.editorialDeclPart.xml index 0d647afe9c..14edb0c6ab 100644 --- a/P5/Source/Specs/model.editorialDeclPart.xml +++ b/P5/Source/Specs/model.editorialDeclPart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.egLike.xml b/P5/Source/Specs/model.egLike.xml index de9279727e..46fa32e6d9 100644 --- a/P5/Source/Specs/model.egLike.xml +++ b/P5/Source/Specs/model.egLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.emphLike.xml b/P5/Source/Specs/model.emphLike.xml index 5f3d8d23ce..78e6c32fc2 100644 --- a/P5/Source/Specs/model.emphLike.xml +++ b/P5/Source/Specs/model.emphLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.encodingDescPart.xml b/P5/Source/Specs/model.encodingDescPart.xml index 4e81fb7352..3f639ac7a3 100644 --- a/P5/Source/Specs/model.encodingDescPart.xml +++ b/P5/Source/Specs/model.encodingDescPart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.entryLike.xml b/P5/Source/Specs/model.entryLike.xml index f353dae501..8f4c9e27a6 100644 --- a/P5/Source/Specs/model.entryLike.xml +++ b/P5/Source/Specs/model.entryLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.entryPart.top.xml b/P5/Source/Specs/model.entryPart.top.xml index a876bd47d2..2e27558c91 100644 --- a/P5/Source/Specs/model.entryPart.top.xml +++ b/P5/Source/Specs/model.entryPart.top.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.entryPart.xml b/P5/Source/Specs/model.entryPart.xml index 175ba2e294..2f5d7a0022 100644 --- a/P5/Source/Specs/model.entryPart.xml +++ b/P5/Source/Specs/model.entryPart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.eventLike.xml b/P5/Source/Specs/model.eventLike.xml index e962a0cdae..55feb20a45 100644 --- a/P5/Source/Specs/model.eventLike.xml +++ b/P5/Source/Specs/model.eventLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.featureVal.complex.xml b/P5/Source/Specs/model.featureVal.complex.xml index c43ff4e8f6..19ec360806 100644 --- a/P5/Source/Specs/model.featureVal.complex.xml +++ b/P5/Source/Specs/model.featureVal.complex.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.featureVal.single.xml b/P5/Source/Specs/model.featureVal.single.xml index a23dc83436..7c6db41df8 100644 --- a/P5/Source/Specs/model.featureVal.single.xml +++ b/P5/Source/Specs/model.featureVal.single.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.featureVal.xml b/P5/Source/Specs/model.featureVal.xml index 1c530fb21f..c5b5aa8292 100644 --- a/P5/Source/Specs/model.featureVal.xml +++ b/P5/Source/Specs/model.featureVal.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.formPart.xml b/P5/Source/Specs/model.formPart.xml index f0c8385f9c..9c1ceb3753 100644 --- a/P5/Source/Specs/model.formPart.xml +++ b/P5/Source/Specs/model.formPart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.frontPart.drama.xml b/P5/Source/Specs/model.frontPart.drama.xml index 6fb75c05d1..ebc9920e22 100644 --- a/P5/Source/Specs/model.frontPart.drama.xml +++ b/P5/Source/Specs/model.frontPart.drama.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.frontPart.xml b/P5/Source/Specs/model.frontPart.xml index 350fd52d0d..e6ac36c010 100644 --- a/P5/Source/Specs/model.frontPart.xml +++ b/P5/Source/Specs/model.frontPart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.fsdDeclPart.xml b/P5/Source/Specs/model.fsdDeclPart.xml index 57a8bbbed5..ca83d64783 100644 --- a/P5/Source/Specs/model.fsdDeclPart.xml +++ b/P5/Source/Specs/model.fsdDeclPart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.gLike.xml b/P5/Source/Specs/model.gLike.xml index aae54d3233..549c8e2f21 100644 --- a/P5/Source/Specs/model.gLike.xml +++ b/P5/Source/Specs/model.gLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.global.edit.xml b/P5/Source/Specs/model.global.edit.xml index c17467604b..6a30b24222 100644 --- a/P5/Source/Specs/model.global.edit.xml +++ b/P5/Source/Specs/model.global.edit.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.global.meta.xml b/P5/Source/Specs/model.global.meta.xml index 8d4c514ac4..ed80bdb7d1 100644 --- a/P5/Source/Specs/model.global.meta.xml +++ b/P5/Source/Specs/model.global.meta.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.global.spoken.xml b/P5/Source/Specs/model.global.spoken.xml index e8046e67a1..25bb62990f 100644 --- a/P5/Source/Specs/model.global.spoken.xml +++ b/P5/Source/Specs/model.global.spoken.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.global.xml b/P5/Source/Specs/model.global.xml index e6da0f33f7..5079a3498b 100644 --- a/P5/Source/Specs/model.global.xml +++ b/P5/Source/Specs/model.global.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.gramPart.xml b/P5/Source/Specs/model.gramPart.xml index 69878ff4c4..f3169f7f98 100644 --- a/P5/Source/Specs/model.gramPart.xml +++ b/P5/Source/Specs/model.gramPart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.graphicLike.xml b/P5/Source/Specs/model.graphicLike.xml index 3a75a3df6c..3d309f3344 100644 --- a/P5/Source/Specs/model.graphicLike.xml +++ b/P5/Source/Specs/model.graphicLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.headLike.xml b/P5/Source/Specs/model.headLike.xml index 6d5eb489e4..e5a218c1b0 100644 --- a/P5/Source/Specs/model.headLike.xml +++ b/P5/Source/Specs/model.headLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.hiLike.xml b/P5/Source/Specs/model.hiLike.xml index c05ff7bc6e..f2e4281555 100644 --- a/P5/Source/Specs/model.hiLike.xml +++ b/P5/Source/Specs/model.hiLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.highlighted.xml b/P5/Source/Specs/model.highlighted.xml index 96664c4dc3..033508e9e1 100644 --- a/P5/Source/Specs/model.highlighted.xml +++ b/P5/Source/Specs/model.highlighted.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.identEquiv.xml b/P5/Source/Specs/model.identEquiv.xml index b455592949..c8b44db1cb 100644 --- a/P5/Source/Specs/model.identEquiv.xml +++ b/P5/Source/Specs/model.identEquiv.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.identSynonyms.xml b/P5/Source/Specs/model.identSynonyms.xml index b5729c6eef..79187a0b83 100644 --- a/P5/Source/Specs/model.identSynonyms.xml +++ b/P5/Source/Specs/model.identSynonyms.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.imprintPart.xml b/P5/Source/Specs/model.imprintPart.xml index ea2e52ba0a..4323c9bd0d 100644 --- a/P5/Source/Specs/model.imprintPart.xml +++ b/P5/Source/Specs/model.imprintPart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.inter.xml b/P5/Source/Specs/model.inter.xml index ce5d9d92af..8c701142d7 100644 --- a/P5/Source/Specs/model.inter.xml +++ b/P5/Source/Specs/model.inter.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.lLike.xml b/P5/Source/Specs/model.lLike.xml index 89815c76a0..e576766768 100644 --- a/P5/Source/Specs/model.lLike.xml +++ b/P5/Source/Specs/model.lLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.lPart.xml b/P5/Source/Specs/model.lPart.xml index 374a2e2cad..f07c52d2ab 100644 --- a/P5/Source/Specs/model.lPart.xml +++ b/P5/Source/Specs/model.lPart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.labelLike.xml b/P5/Source/Specs/model.labelLike.xml index 940ae3ed7a..d9a671bf18 100644 --- a/P5/Source/Specs/model.labelLike.xml +++ b/P5/Source/Specs/model.labelLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.lexicalRefinement.xml b/P5/Source/Specs/model.lexicalRefinement.xml index 64a5b5bbf3..196cbedba9 100644 --- a/P5/Source/Specs/model.lexicalRefinement.xml +++ b/P5/Source/Specs/model.lexicalRefinement.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.limitedPhrase.xml b/P5/Source/Specs/model.limitedPhrase.xml index 5b6c2ea0d5..2084f4fdc2 100644 --- a/P5/Source/Specs/model.limitedPhrase.xml +++ b/P5/Source/Specs/model.limitedPhrase.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.linePart.xml b/P5/Source/Specs/model.linePart.xml index 6595c90937..bf07c615c4 100644 --- a/P5/Source/Specs/model.linePart.xml +++ b/P5/Source/Specs/model.linePart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.listLike.xml b/P5/Source/Specs/model.listLike.xml index 933ca683a1..ca16d79da6 100644 --- a/P5/Source/Specs/model.listLike.xml +++ b/P5/Source/Specs/model.listLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.measureLike.xml b/P5/Source/Specs/model.measureLike.xml index 240dfd3398..63be2d9015 100644 --- a/P5/Source/Specs/model.measureLike.xml +++ b/P5/Source/Specs/model.measureLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.milestoneLike.xml b/P5/Source/Specs/model.milestoneLike.xml index 86aa7ea019..ef5da5015c 100644 --- a/P5/Source/Specs/model.milestoneLike.xml +++ b/P5/Source/Specs/model.milestoneLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.morphLike.xml b/P5/Source/Specs/model.morphLike.xml index 01178cb65d..b2f40ef7b2 100644 --- a/P5/Source/Specs/model.morphLike.xml +++ b/P5/Source/Specs/model.morphLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.msItemPart.xml b/P5/Source/Specs/model.msItemPart.xml index 8252284491..a4b3c71bac 100644 --- a/P5/Source/Specs/model.msItemPart.xml +++ b/P5/Source/Specs/model.msItemPart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.msQuoteLike.xml b/P5/Source/Specs/model.msQuoteLike.xml index ab9d6cc53a..9bb52bbbb5 100644 --- a/P5/Source/Specs/model.msQuoteLike.xml +++ b/P5/Source/Specs/model.msQuoteLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.nameLike.agent.xml b/P5/Source/Specs/model.nameLike.agent.xml index 31d40a42f8..baa013cab5 100644 --- a/P5/Source/Specs/model.nameLike.agent.xml +++ b/P5/Source/Specs/model.nameLike.agent.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.nameLike.xml b/P5/Source/Specs/model.nameLike.xml index 794fef0801..9361febe84 100644 --- a/P5/Source/Specs/model.nameLike.xml +++ b/P5/Source/Specs/model.nameLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.noteLike.xml b/P5/Source/Specs/model.noteLike.xml index dc030037ae..5e0ae356bb 100644 --- a/P5/Source/Specs/model.noteLike.xml +++ b/P5/Source/Specs/model.noteLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.oddDecl.xml b/P5/Source/Specs/model.oddDecl.xml index 4cfcea94d9..6f90f2c7b6 100644 --- a/P5/Source/Specs/model.oddDecl.xml +++ b/P5/Source/Specs/model.oddDecl.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.oddRef.xml b/P5/Source/Specs/model.oddRef.xml index b68930eb85..5071985070 100644 --- a/P5/Source/Specs/model.oddRef.xml +++ b/P5/Source/Specs/model.oddRef.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.offsetLike.xml b/P5/Source/Specs/model.offsetLike.xml index 9990330de2..a00aa1cfe9 100644 --- a/P5/Source/Specs/model.offsetLike.xml +++ b/P5/Source/Specs/model.offsetLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.orgPart.xml b/P5/Source/Specs/model.orgPart.xml index 27aa48a4dc..0d97c3f0b5 100644 --- a/P5/Source/Specs/model.orgPart.xml +++ b/P5/Source/Specs/model.orgPart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.orgStateLike.xml b/P5/Source/Specs/model.orgStateLike.xml index 0495ebe712..17cb8daf6c 100644 --- a/P5/Source/Specs/model.orgStateLike.xml +++ b/P5/Source/Specs/model.orgStateLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.pLike.front.xml b/P5/Source/Specs/model.pLike.front.xml index 58a2a3f4ab..5ed337cc1a 100644 --- a/P5/Source/Specs/model.pLike.front.xml +++ b/P5/Source/Specs/model.pLike.front.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.pLike.xml b/P5/Source/Specs/model.pLike.xml index 109954fa1b..acc1d35a36 100644 --- a/P5/Source/Specs/model.pLike.xml +++ b/P5/Source/Specs/model.pLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.pPart.data.xml b/P5/Source/Specs/model.pPart.data.xml index fee3950155..bdd8acf840 100644 --- a/P5/Source/Specs/model.pPart.data.xml +++ b/P5/Source/Specs/model.pPart.data.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.pPart.edit.xml b/P5/Source/Specs/model.pPart.edit.xml index da05b24dc0..f1906e500a 100644 --- a/P5/Source/Specs/model.pPart.edit.xml +++ b/P5/Source/Specs/model.pPart.edit.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.pPart.editorial.xml b/P5/Source/Specs/model.pPart.editorial.xml index 0cf401ddf3..f01cdcb0de 100644 --- a/P5/Source/Specs/model.pPart.editorial.xml +++ b/P5/Source/Specs/model.pPart.editorial.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.pPart.msdesc.xml b/P5/Source/Specs/model.pPart.msdesc.xml index ab4625ae0c..bf597ac580 100644 --- a/P5/Source/Specs/model.pPart.msdesc.xml +++ b/P5/Source/Specs/model.pPart.msdesc.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.pPart.transcriptional.xml b/P5/Source/Specs/model.pPart.transcriptional.xml index 37389adddf..03ce7fbfe8 100644 --- a/P5/Source/Specs/model.pPart.transcriptional.xml +++ b/P5/Source/Specs/model.pPart.transcriptional.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.paraPart.xml b/P5/Source/Specs/model.paraPart.xml index 7242f4a202..b593f26b43 100644 --- a/P5/Source/Specs/model.paraPart.xml +++ b/P5/Source/Specs/model.paraPart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.persNamePart.xml b/P5/Source/Specs/model.persNamePart.xml index 4dcc7c8a7a..d1c52cbda0 100644 --- a/P5/Source/Specs/model.persNamePart.xml +++ b/P5/Source/Specs/model.persNamePart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.persStateLike.xml b/P5/Source/Specs/model.persStateLike.xml index 7391695f01..3749a55a8b 100644 --- a/P5/Source/Specs/model.persStateLike.xml +++ b/P5/Source/Specs/model.persStateLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.personLike.xml b/P5/Source/Specs/model.personLike.xml index 0066b0c904..c5e0d466dc 100644 --- a/P5/Source/Specs/model.personLike.xml +++ b/P5/Source/Specs/model.personLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.personPart.xml b/P5/Source/Specs/model.personPart.xml index 6cbf0040e0..7a526ee0e0 100644 --- a/P5/Source/Specs/model.personPart.xml +++ b/P5/Source/Specs/model.personPart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.phrase.xml b/P5/Source/Specs/model.phrase.xml index 8f370d52cd..26e5a5c08b 100644 --- a/P5/Source/Specs/model.phrase.xml +++ b/P5/Source/Specs/model.phrase.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.phrase.xml.xml b/P5/Source/Specs/model.phrase.xml.xml index 01b2d63cd1..5ab4b83846 100644 --- a/P5/Source/Specs/model.phrase.xml.xml +++ b/P5/Source/Specs/model.phrase.xml.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.physDescPart.xml b/P5/Source/Specs/model.physDescPart.xml index 46328bbd62..c349770cbf 100644 --- a/P5/Source/Specs/model.physDescPart.xml +++ b/P5/Source/Specs/model.physDescPart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.placeLike.xml b/P5/Source/Specs/model.placeLike.xml index 833179ea38..3dc27043b9 100644 --- a/P5/Source/Specs/model.placeLike.xml +++ b/P5/Source/Specs/model.placeLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.placeNamePart.xml b/P5/Source/Specs/model.placeNamePart.xml index 19b1a60558..6580f89223 100644 --- a/P5/Source/Specs/model.placeNamePart.xml +++ b/P5/Source/Specs/model.placeNamePart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.placeStateLike.xml b/P5/Source/Specs/model.placeStateLike.xml index 8929e9833b..c5b08f4451 100644 --- a/P5/Source/Specs/model.placeStateLike.xml +++ b/P5/Source/Specs/model.placeStateLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.profileDescPart.xml b/P5/Source/Specs/model.profileDescPart.xml index 4cb0466848..d744a63fb5 100644 --- a/P5/Source/Specs/model.profileDescPart.xml +++ b/P5/Source/Specs/model.profileDescPart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.ptrLike.form.xml b/P5/Source/Specs/model.ptrLike.form.xml index 65d7347683..7b597902b3 100644 --- a/P5/Source/Specs/model.ptrLike.form.xml +++ b/P5/Source/Specs/model.ptrLike.form.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.ptrLike.xml b/P5/Source/Specs/model.ptrLike.xml index 6e3281bb2f..7a4d193a66 100644 --- a/P5/Source/Specs/model.ptrLike.xml +++ b/P5/Source/Specs/model.ptrLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.publicationStmtPart.agency.xml b/P5/Source/Specs/model.publicationStmtPart.agency.xml index babb6af6df..d955608d5c 100644 --- a/P5/Source/Specs/model.publicationStmtPart.agency.xml +++ b/P5/Source/Specs/model.publicationStmtPart.agency.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.publicationStmtPart.detail.xml b/P5/Source/Specs/model.publicationStmtPart.detail.xml index 795e20a135..7392139710 100644 --- a/P5/Source/Specs/model.publicationStmtPart.detail.xml +++ b/P5/Source/Specs/model.publicationStmtPart.detail.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.quoteLike.xml b/P5/Source/Specs/model.quoteLike.xml index 26ee6d9b55..588084aa88 100644 --- a/P5/Source/Specs/model.quoteLike.xml +++ b/P5/Source/Specs/model.quoteLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.rdgLike.xml b/P5/Source/Specs/model.rdgLike.xml index 980447303c..de9acb1da0 100644 --- a/P5/Source/Specs/model.rdgLike.xml +++ b/P5/Source/Specs/model.rdgLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.rdgPart.xml b/P5/Source/Specs/model.rdgPart.xml index 8fd44c5ee5..8f1f3bca3d 100644 --- a/P5/Source/Specs/model.rdgPart.xml +++ b/P5/Source/Specs/model.rdgPart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.recordingPart.xml b/P5/Source/Specs/model.recordingPart.xml index e5c23ad431..6d84cc11a5 100644 --- a/P5/Source/Specs/model.recordingPart.xml +++ b/P5/Source/Specs/model.recordingPart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.resource.xml b/P5/Source/Specs/model.resource.xml index 8065ea297d..d0b5370a6f 100644 --- a/P5/Source/Specs/model.resource.xml +++ b/P5/Source/Specs/model.resource.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.respLike.xml b/P5/Source/Specs/model.respLike.xml index dd94ae118b..b4beb3d50c 100644 --- a/P5/Source/Specs/model.respLike.xml +++ b/P5/Source/Specs/model.respLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.segLike.xml b/P5/Source/Specs/model.segLike.xml index ab419a58db..d5601a7ef3 100644 --- a/P5/Source/Specs/model.segLike.xml +++ b/P5/Source/Specs/model.segLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.settingPart.xml b/P5/Source/Specs/model.settingPart.xml index e9e477ab6e..e1c86d8482 100644 --- a/P5/Source/Specs/model.settingPart.xml +++ b/P5/Source/Specs/model.settingPart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.sourceDescPart.xml b/P5/Source/Specs/model.sourceDescPart.xml index 61ad43bb34..cd404efdf7 100644 --- a/P5/Source/Specs/model.sourceDescPart.xml +++ b/P5/Source/Specs/model.sourceDescPart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.specDescLike.xml b/P5/Source/Specs/model.specDescLike.xml index 88f2ca4594..b2d7d0f8b2 100644 --- a/P5/Source/Specs/model.specDescLike.xml +++ b/P5/Source/Specs/model.specDescLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.stageLike.xml b/P5/Source/Specs/model.stageLike.xml index 3a81f417aa..900ada33b0 100644 --- a/P5/Source/Specs/model.stageLike.xml +++ b/P5/Source/Specs/model.stageLike.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.standOffPart.xml b/P5/Source/Specs/model.standOffPart.xml index 0a22ae432b..11c0b46a9b 100644 --- a/P5/Source/Specs/model.standOffPart.xml +++ b/P5/Source/Specs/model.standOffPart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.teiHeaderPart.xml b/P5/Source/Specs/model.teiHeaderPart.xml index f60280913e..2991c623b8 100644 --- a/P5/Source/Specs/model.teiHeaderPart.xml +++ b/P5/Source/Specs/model.teiHeaderPart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.textDescPart.xml b/P5/Source/Specs/model.textDescPart.xml index 8b7162bdc1..78120f80d3 100644 --- a/P5/Source/Specs/model.textDescPart.xml +++ b/P5/Source/Specs/model.textDescPart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.titlepagePart.xml b/P5/Source/Specs/model.titlepagePart.xml index 7ce67bed5c..4534cbe3b5 100644 --- a/P5/Source/Specs/model.titlepagePart.xml +++ b/P5/Source/Specs/model.titlepagePart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/model.xml b/P5/Source/Specs/model.xml index d09274f70f..31fe8a749d 100644 --- a/P5/Source/Specs/model.xml +++ b/P5/Source/Specs/model.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/modelGrp.xml b/P5/Source/Specs/modelGrp.xml index ca4e11a00d..7267ad191c 100644 --- a/P5/Source/Specs/modelGrp.xml +++ b/P5/Source/Specs/modelGrp.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/modelSequence.xml b/P5/Source/Specs/modelSequence.xml index 51f31ed829..b76bfdfa97 100644 --- a/P5/Source/Specs/modelSequence.xml +++ b/P5/Source/Specs/modelSequence.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/moduleRef.xml b/P5/Source/Specs/moduleRef.xml index 80563bf2e3..65d7c7be4d 100644 --- a/P5/Source/Specs/moduleRef.xml +++ b/P5/Source/Specs/moduleRef.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/moduleSpec.xml b/P5/Source/Specs/moduleSpec.xml index 49f5e2123d..433fb78ebc 100644 --- a/P5/Source/Specs/moduleSpec.xml +++ b/P5/Source/Specs/moduleSpec.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/monogr.xml b/P5/Source/Specs/monogr.xml index 1e4599a9af..b14dc8c461 100644 --- a/P5/Source/Specs/monogr.xml +++ b/P5/Source/Specs/monogr.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/mood.xml b/P5/Source/Specs/mood.xml index 628538c53c..29b642a98e 100644 --- a/P5/Source/Specs/mood.xml +++ b/P5/Source/Specs/mood.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/move.xml b/P5/Source/Specs/move.xml index 41358c33cb..56ba897744 100644 --- a/P5/Source/Specs/move.xml +++ b/P5/Source/Specs/move.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/msContents.xml b/P5/Source/Specs/msContents.xml index 5ec0587876..73c08df756 100644 --- a/P5/Source/Specs/msContents.xml +++ b/P5/Source/Specs/msContents.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/msDesc.xml b/P5/Source/Specs/msDesc.xml index fc7440d97b..da8621afd2 100644 --- a/P5/Source/Specs/msDesc.xml +++ b/P5/Source/Specs/msDesc.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/msFrag.xml b/P5/Source/Specs/msFrag.xml index b8a51b5106..ecf91cb7a6 100644 --- a/P5/Source/Specs/msFrag.xml +++ b/P5/Source/Specs/msFrag.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/msIdentifier.xml b/P5/Source/Specs/msIdentifier.xml index 07414f1311..508a745707 100644 --- a/P5/Source/Specs/msIdentifier.xml +++ b/P5/Source/Specs/msIdentifier.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/msItem.xml b/P5/Source/Specs/msItem.xml index 431746ea67..a27ab89b98 100644 --- a/P5/Source/Specs/msItem.xml +++ b/P5/Source/Specs/msItem.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/msItemStruct.xml b/P5/Source/Specs/msItemStruct.xml index dfae4ef9ab..98f6a26bb3 100644 --- a/P5/Source/Specs/msItemStruct.xml +++ b/P5/Source/Specs/msItemStruct.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/msName.xml b/P5/Source/Specs/msName.xml index 38f6294ca4..eadcc467ee 100644 --- a/P5/Source/Specs/msName.xml +++ b/P5/Source/Specs/msName.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/msPart.xml b/P5/Source/Specs/msPart.xml index 23492df635..26a51986f2 100644 --- a/P5/Source/Specs/msPart.xml +++ b/P5/Source/Specs/msPart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/musicNotation.xml b/P5/Source/Specs/musicNotation.xml index 147bfda3c9..ab05959f7c 100644 --- a/P5/Source/Specs/musicNotation.xml +++ b/P5/Source/Specs/musicNotation.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/nameLink.xml b/P5/Source/Specs/nameLink.xml index 8e1ddc0eba..e01796e8b1 100644 --- a/P5/Source/Specs/nameLink.xml +++ b/P5/Source/Specs/nameLink.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/namespace.xml b/P5/Source/Specs/namespace.xml index 083902310e..910c90ea44 100644 --- a/P5/Source/Specs/namespace.xml +++ b/P5/Source/Specs/namespace.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/node.xml b/P5/Source/Specs/node.xml index 838cecea70..9396e9c03b 100644 --- a/P5/Source/Specs/node.xml +++ b/P5/Source/Specs/node.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/normalization.xml b/P5/Source/Specs/normalization.xml index 2d456d9ab9..b97117e589 100644 --- a/P5/Source/Specs/normalization.xml +++ b/P5/Source/Specs/normalization.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/notatedMusic.xml b/P5/Source/Specs/notatedMusic.xml index a3f3851d1a..a9d62e1b9c 100644 --- a/P5/Source/Specs/notatedMusic.xml +++ b/P5/Source/Specs/notatedMusic.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/note.xml b/P5/Source/Specs/note.xml index a880eafaae..0798511e1a 100644 --- a/P5/Source/Specs/note.xml +++ b/P5/Source/Specs/note.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/notesStmt.xml b/P5/Source/Specs/notesStmt.xml index 6b13620a81..4bbcd6a711 100644 --- a/P5/Source/Specs/notesStmt.xml +++ b/P5/Source/Specs/notesStmt.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/num.xml b/P5/Source/Specs/num.xml index 06c2701efe..c0786c0062 100644 --- a/P5/Source/Specs/num.xml +++ b/P5/Source/Specs/num.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/number.xml b/P5/Source/Specs/number.xml index cb387e9f25..63446c5ead 100644 --- a/P5/Source/Specs/number.xml +++ b/P5/Source/Specs/number.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/numeric.xml b/P5/Source/Specs/numeric.xml index fc94f495b9..61dd6cedce 100644 --- a/P5/Source/Specs/numeric.xml +++ b/P5/Source/Specs/numeric.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/nym.xml b/P5/Source/Specs/nym.xml index 412bd2f4fa..5e49136cad 100644 --- a/P5/Source/Specs/nym.xml +++ b/P5/Source/Specs/nym.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/oRef.xml b/P5/Source/Specs/oRef.xml index a386b7aeed..5a5608fcdb 100644 --- a/P5/Source/Specs/oRef.xml +++ b/P5/Source/Specs/oRef.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/objectDesc.xml b/P5/Source/Specs/objectDesc.xml index 49058f9b60..f3367b7fe6 100644 --- a/P5/Source/Specs/objectDesc.xml +++ b/P5/Source/Specs/objectDesc.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/objectType.xml b/P5/Source/Specs/objectType.xml index 6502e4177c..e8db622519 100644 --- a/P5/Source/Specs/objectType.xml +++ b/P5/Source/Specs/objectType.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/opener.xml b/P5/Source/Specs/opener.xml index ff5e5039da..ec89c7d444 100644 --- a/P5/Source/Specs/opener.xml +++ b/P5/Source/Specs/opener.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/org.xml b/P5/Source/Specs/org.xml index 8c888d73c2..cccb50a29c 100644 --- a/P5/Source/Specs/org.xml +++ b/P5/Source/Specs/org.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/orig.xml b/P5/Source/Specs/orig.xml index d418ce08bd..9c049b722f 100644 --- a/P5/Source/Specs/orig.xml +++ b/P5/Source/Specs/orig.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/origDate.xml b/P5/Source/Specs/origDate.xml index fe9da4b27f..b91153b077 100644 --- a/P5/Source/Specs/origDate.xml +++ b/P5/Source/Specs/origDate.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/orth.xml b/P5/Source/Specs/orth.xml index 8b9152649e..eb9172b5b7 100644 --- a/P5/Source/Specs/orth.xml +++ b/P5/Source/Specs/orth.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/outputRendition.xml b/P5/Source/Specs/outputRendition.xml index d486a403ef..9bdaeffe86 100644 --- a/P5/Source/Specs/outputRendition.xml +++ b/P5/Source/Specs/outputRendition.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/p.xml b/P5/Source/Specs/p.xml index fec443c9b3..e1b14d504b 100644 --- a/P5/Source/Specs/p.xml +++ b/P5/Source/Specs/p.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/pRef.xml b/P5/Source/Specs/pRef.xml index 2d35095af1..68ea99eb49 100644 --- a/P5/Source/Specs/pRef.xml +++ b/P5/Source/Specs/pRef.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/param.xml b/P5/Source/Specs/param.xml index 6fed3ad2aa..4eec04bfbd 100644 --- a/P5/Source/Specs/param.xml +++ b/P5/Source/Specs/param.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/paramList.xml b/P5/Source/Specs/paramList.xml index 50ba643cc6..1824691268 100644 --- a/P5/Source/Specs/paramList.xml +++ b/P5/Source/Specs/paramList.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/paramSpec.xml b/P5/Source/Specs/paramSpec.xml index b32bb2ec4b..3e5f7daead 100644 --- a/P5/Source/Specs/paramSpec.xml +++ b/P5/Source/Specs/paramSpec.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/particDesc.xml b/P5/Source/Specs/particDesc.xml index 1cf432ee1a..0e2b6df990 100644 --- a/P5/Source/Specs/particDesc.xml +++ b/P5/Source/Specs/particDesc.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/path.xml b/P5/Source/Specs/path.xml index fd203e73b6..bc6af60964 100644 --- a/P5/Source/Specs/path.xml +++ b/P5/Source/Specs/path.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/pause.xml b/P5/Source/Specs/pause.xml index 541ed408b0..263008f955 100644 --- a/P5/Source/Specs/pause.xml +++ b/P5/Source/Specs/pause.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/pb.xml b/P5/Source/Specs/pb.xml index c8dd57831c..e4b83b5881 100644 --- a/P5/Source/Specs/pb.xml +++ b/P5/Source/Specs/pb.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/pc.xml b/P5/Source/Specs/pc.xml index a1d5d8d54a..84f5b40628 100644 --- a/P5/Source/Specs/pc.xml +++ b/P5/Source/Specs/pc.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/per.xml b/P5/Source/Specs/per.xml index e56026742e..b4d9299b45 100644 --- a/P5/Source/Specs/per.xml +++ b/P5/Source/Specs/per.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/performance.xml b/P5/Source/Specs/performance.xml index b35e13e3e3..49bf2edd14 100644 --- a/P5/Source/Specs/performance.xml +++ b/P5/Source/Specs/performance.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/person.xml b/P5/Source/Specs/person.xml index 68f6af3ec5..64eef6dcd0 100644 --- a/P5/Source/Specs/person.xml +++ b/P5/Source/Specs/person.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/personGrp.xml b/P5/Source/Specs/personGrp.xml index 5542cddf31..5e1ec78f8d 100644 --- a/P5/Source/Specs/personGrp.xml +++ b/P5/Source/Specs/personGrp.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/persona.xml b/P5/Source/Specs/persona.xml index 39ee662a6a..91a38e340a 100644 --- a/P5/Source/Specs/persona.xml +++ b/P5/Source/Specs/persona.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/phr.xml b/P5/Source/Specs/phr.xml index 552ef58b2e..83de82fd78 100644 --- a/P5/Source/Specs/phr.xml +++ b/P5/Source/Specs/phr.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/physDesc.xml b/P5/Source/Specs/physDesc.xml index 284df79517..94685466e1 100644 --- a/P5/Source/Specs/physDesc.xml +++ b/P5/Source/Specs/physDesc.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/place.xml b/P5/Source/Specs/place.xml index 1ee05ebe3d..ec9b883172 100644 --- a/P5/Source/Specs/place.xml +++ b/P5/Source/Specs/place.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/pos.xml b/P5/Source/Specs/pos.xml index 087aad96b1..ac2037416d 100644 --- a/P5/Source/Specs/pos.xml +++ b/P5/Source/Specs/pos.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/postBox.xml b/P5/Source/Specs/postBox.xml index e889aec6a3..4eb7b47412 100644 --- a/P5/Source/Specs/postBox.xml +++ b/P5/Source/Specs/postBox.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/postCode.xml b/P5/Source/Specs/postCode.xml index ec1382a9f7..8f6a3ec265 100644 --- a/P5/Source/Specs/postCode.xml +++ b/P5/Source/Specs/postCode.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/postscript.xml b/P5/Source/Specs/postscript.xml index 5ff28a29a5..af2f6938f1 100644 --- a/P5/Source/Specs/postscript.xml +++ b/P5/Source/Specs/postscript.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/prefixDef.xml b/P5/Source/Specs/prefixDef.xml index 8291193a01..fce4879962 100644 --- a/P5/Source/Specs/prefixDef.xml +++ b/P5/Source/Specs/prefixDef.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/preparedness.xml b/P5/Source/Specs/preparedness.xml index 55741f0bf9..0b2189fc40 100644 --- a/P5/Source/Specs/preparedness.xml +++ b/P5/Source/Specs/preparedness.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/profileDesc.xml b/P5/Source/Specs/profileDesc.xml index 171410364b..fb11c233f7 100644 --- a/P5/Source/Specs/profileDesc.xml +++ b/P5/Source/Specs/profileDesc.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/projectDesc.xml b/P5/Source/Specs/projectDesc.xml index 56441a21dc..c8e50f0b22 100644 --- a/P5/Source/Specs/projectDesc.xml +++ b/P5/Source/Specs/projectDesc.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/prologue.xml b/P5/Source/Specs/prologue.xml index abdfb7e041..947fdafd2d 100644 --- a/P5/Source/Specs/prologue.xml +++ b/P5/Source/Specs/prologue.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/pron.xml b/P5/Source/Specs/pron.xml index d5158e0914..7a7d2424ea 100644 --- a/P5/Source/Specs/pron.xml +++ b/P5/Source/Specs/pron.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/ptr.xml b/P5/Source/Specs/ptr.xml index d04b16f53b..2fb1bf6c13 100644 --- a/P5/Source/Specs/ptr.xml +++ b/P5/Source/Specs/ptr.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/pubPlace.xml b/P5/Source/Specs/pubPlace.xml index 628111b22d..ca26d0a9c2 100644 --- a/P5/Source/Specs/pubPlace.xml +++ b/P5/Source/Specs/pubPlace.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/publicationStmt.xml b/P5/Source/Specs/publicationStmt.xml index d436a01003..37df6d2352 100644 --- a/P5/Source/Specs/publicationStmt.xml +++ b/P5/Source/Specs/publicationStmt.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/punctuation.xml b/P5/Source/Specs/punctuation.xml index bd3bd1012c..93821375bc 100644 --- a/P5/Source/Specs/punctuation.xml +++ b/P5/Source/Specs/punctuation.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/purpose.xml b/P5/Source/Specs/purpose.xml index 857fee64f9..9aee9bb848 100644 --- a/P5/Source/Specs/purpose.xml +++ b/P5/Source/Specs/purpose.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/q.xml b/P5/Source/Specs/q.xml index 5e930fc498..99fd3d39b6 100644 --- a/P5/Source/Specs/q.xml +++ b/P5/Source/Specs/q.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/quotation.xml b/P5/Source/Specs/quotation.xml index 53241f45dc..1e124d2630 100644 --- a/P5/Source/Specs/quotation.xml +++ b/P5/Source/Specs/quotation.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/quote.xml b/P5/Source/Specs/quote.xml index 4efc5359d8..36d43a000f 100644 --- a/P5/Source/Specs/quote.xml +++ b/P5/Source/Specs/quote.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/rb.xml b/P5/Source/Specs/rb.xml index 9a3b993fa2..cffe1d7e11 100644 --- a/P5/Source/Specs/rb.xml +++ b/P5/Source/Specs/rb.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/rdg.xml b/P5/Source/Specs/rdg.xml index acdfe07712..519ed3a6a7 100644 --- a/P5/Source/Specs/rdg.xml +++ b/P5/Source/Specs/rdg.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/rdgGrp.xml b/P5/Source/Specs/rdgGrp.xml index 957e83f3a3..487da66324 100644 --- a/P5/Source/Specs/rdgGrp.xml +++ b/P5/Source/Specs/rdgGrp.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/re.xml b/P5/Source/Specs/re.xml index 13dd822119..2fbcd74061 100644 --- a/P5/Source/Specs/re.xml +++ b/P5/Source/Specs/re.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/recording.xml b/P5/Source/Specs/recording.xml index 7131f9ebc3..c312a4eec9 100644 --- a/P5/Source/Specs/recording.xml +++ b/P5/Source/Specs/recording.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/recordingStmt.xml b/P5/Source/Specs/recordingStmt.xml index 01e0e456be..3161ca2d7b 100644 --- a/P5/Source/Specs/recordingStmt.xml +++ b/P5/Source/Specs/recordingStmt.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/redo.xml b/P5/Source/Specs/redo.xml index 786a606ad2..0da621df85 100644 --- a/P5/Source/Specs/redo.xml +++ b/P5/Source/Specs/redo.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/ref.xml b/P5/Source/Specs/ref.xml index 736e9099d5..d769a34f05 100644 --- a/P5/Source/Specs/ref.xml +++ b/P5/Source/Specs/ref.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/refState.xml b/P5/Source/Specs/refState.xml index b31c07a137..b808c03b4b 100644 --- a/P5/Source/Specs/refState.xml +++ b/P5/Source/Specs/refState.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/refsDecl.xml b/P5/Source/Specs/refsDecl.xml index 39a83d06d1..02befb6aa4 100644 --- a/P5/Source/Specs/refsDecl.xml +++ b/P5/Source/Specs/refsDecl.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/reg.xml b/P5/Source/Specs/reg.xml index a9d7df25cb..1429cc50c0 100644 --- a/P5/Source/Specs/reg.xml +++ b/P5/Source/Specs/reg.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/relatedItem.xml b/P5/Source/Specs/relatedItem.xml index ef12cb724d..7e1943e7cb 100644 --- a/P5/Source/Specs/relatedItem.xml +++ b/P5/Source/Specs/relatedItem.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/remarks.xml b/P5/Source/Specs/remarks.xml index 2fbbcb8413..eab9bc66a2 100644 --- a/P5/Source/Specs/remarks.xml +++ b/P5/Source/Specs/remarks.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/rendition.xml b/P5/Source/Specs/rendition.xml index b732b40468..7cadc85f19 100644 --- a/P5/Source/Specs/rendition.xml +++ b/P5/Source/Specs/rendition.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/repository.xml b/P5/Source/Specs/repository.xml index aa9dc49ac1..be1df64396 100644 --- a/P5/Source/Specs/repository.xml +++ b/P5/Source/Specs/repository.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/respStmt.xml b/P5/Source/Specs/respStmt.xml index 7393d5c125..381e7fe5d0 100644 --- a/P5/Source/Specs/respStmt.xml +++ b/P5/Source/Specs/respStmt.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/respons.xml b/P5/Source/Specs/respons.xml index 50a01c8c01..673454b07c 100644 --- a/P5/Source/Specs/respons.xml +++ b/P5/Source/Specs/respons.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/restore.xml b/P5/Source/Specs/restore.xml index 5856c337e1..97b0704019 100644 --- a/P5/Source/Specs/restore.xml +++ b/P5/Source/Specs/restore.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/retrace.xml b/P5/Source/Specs/retrace.xml index 88ff77aa5c..7fe3ce2c36 100644 --- a/P5/Source/Specs/retrace.xml +++ b/P5/Source/Specs/retrace.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/revisionDesc.xml b/P5/Source/Specs/revisionDesc.xml index 811f8d6e56..1f37dff596 100644 --- a/P5/Source/Specs/revisionDesc.xml +++ b/P5/Source/Specs/revisionDesc.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/rhyme.xml b/P5/Source/Specs/rhyme.xml index 44c9cc969f..a491783533 100644 --- a/P5/Source/Specs/rhyme.xml +++ b/P5/Source/Specs/rhyme.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/role.xml b/P5/Source/Specs/role.xml index 672e332b30..a39524281a 100644 --- a/P5/Source/Specs/role.xml +++ b/P5/Source/Specs/role.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/roleDesc.xml b/P5/Source/Specs/roleDesc.xml index b91187f0c4..4192d1f359 100644 --- a/P5/Source/Specs/roleDesc.xml +++ b/P5/Source/Specs/roleDesc.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/roleName.xml b/P5/Source/Specs/roleName.xml index 592f62728f..9986b7c983 100644 --- a/P5/Source/Specs/roleName.xml +++ b/P5/Source/Specs/roleName.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/root.xml b/P5/Source/Specs/root.xml index d16d8672fd..4e704653b2 100644 --- a/P5/Source/Specs/root.xml +++ b/P5/Source/Specs/root.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/row.xml b/P5/Source/Specs/row.xml index 33e81bc137..db4c1e60aa 100644 --- a/P5/Source/Specs/row.xml +++ b/P5/Source/Specs/row.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/rs.xml b/P5/Source/Specs/rs.xml index 7110efa93c..8e49a17a7e 100644 --- a/P5/Source/Specs/rs.xml +++ b/P5/Source/Specs/rs.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/rt.xml b/P5/Source/Specs/rt.xml index c0b562a740..71c2cd09c8 100644 --- a/P5/Source/Specs/rt.xml +++ b/P5/Source/Specs/rt.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/rubric.xml b/P5/Source/Specs/rubric.xml index f1bfae2e68..584606f6ef 100644 --- a/P5/Source/Specs/rubric.xml +++ b/P5/Source/Specs/rubric.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/ruby.xml b/P5/Source/Specs/ruby.xml index ed9ed1a697..db2f095b75 100644 --- a/P5/Source/Specs/ruby.xml +++ b/P5/Source/Specs/ruby.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/s.xml b/P5/Source/Specs/s.xml index 9d434e3a6d..2df1d961fc 100644 --- a/P5/Source/Specs/s.xml +++ b/P5/Source/Specs/s.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/said.xml b/P5/Source/Specs/said.xml index 7424cb5186..28f5966631 100644 --- a/P5/Source/Specs/said.xml +++ b/P5/Source/Specs/said.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/salute.xml b/P5/Source/Specs/salute.xml index eaef9619b3..5dedecdf62 100644 --- a/P5/Source/Specs/salute.xml +++ b/P5/Source/Specs/salute.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/samplingDecl.xml b/P5/Source/Specs/samplingDecl.xml index 2ea1365ea5..005ece69e4 100644 --- a/P5/Source/Specs/samplingDecl.xml +++ b/P5/Source/Specs/samplingDecl.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/schemaRef.xml b/P5/Source/Specs/schemaRef.xml index 94115574da..f5f622ddd2 100644 --- a/P5/Source/Specs/schemaRef.xml +++ b/P5/Source/Specs/schemaRef.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/schemaSpec.xml b/P5/Source/Specs/schemaSpec.xml index 02ef7756cf..8389f70a1d 100644 --- a/P5/Source/Specs/schemaSpec.xml +++ b/P5/Source/Specs/schemaSpec.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/scriptDesc.xml b/P5/Source/Specs/scriptDesc.xml index 1fe086068a..ead5c2de53 100644 --- a/P5/Source/Specs/scriptDesc.xml +++ b/P5/Source/Specs/scriptDesc.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/scriptNote.xml b/P5/Source/Specs/scriptNote.xml index 0fbbb277ed..52d4803d81 100644 --- a/P5/Source/Specs/scriptNote.xml +++ b/P5/Source/Specs/scriptNote.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/scriptStmt.xml b/P5/Source/Specs/scriptStmt.xml index 44b57d0246..4f97bc576e 100644 --- a/P5/Source/Specs/scriptStmt.xml +++ b/P5/Source/Specs/scriptStmt.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/sealDesc.xml b/P5/Source/Specs/sealDesc.xml index 54905c1d4f..bc6f609024 100644 --- a/P5/Source/Specs/sealDesc.xml +++ b/P5/Source/Specs/sealDesc.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/secFol.xml b/P5/Source/Specs/secFol.xml index ca5f89e229..1affd7b4cc 100644 --- a/P5/Source/Specs/secFol.xml +++ b/P5/Source/Specs/secFol.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/secl.xml b/P5/Source/Specs/secl.xml index f83a261942..3518cb120c 100644 --- a/P5/Source/Specs/secl.xml +++ b/P5/Source/Specs/secl.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/seg.xml b/P5/Source/Specs/seg.xml index 4fc42aca7d..a82d6d40fe 100644 --- a/P5/Source/Specs/seg.xml +++ b/P5/Source/Specs/seg.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/segmentation.xml b/P5/Source/Specs/segmentation.xml index 148322e2d3..fe76c035cf 100644 --- a/P5/Source/Specs/segmentation.xml +++ b/P5/Source/Specs/segmentation.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/sense.xml b/P5/Source/Specs/sense.xml index dc7f3cbc5f..2c0991d7f7 100644 --- a/P5/Source/Specs/sense.xml +++ b/P5/Source/Specs/sense.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/sequence.xml b/P5/Source/Specs/sequence.xml index 6af5939002..bae4321128 100644 --- a/P5/Source/Specs/sequence.xml +++ b/P5/Source/Specs/sequence.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/series.xml b/P5/Source/Specs/series.xml index 254b30b4a0..c2d2cda2f7 100644 --- a/P5/Source/Specs/series.xml +++ b/P5/Source/Specs/series.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/seriesStmt.xml b/P5/Source/Specs/seriesStmt.xml index 29e503c1ac..63698a8965 100644 --- a/P5/Source/Specs/seriesStmt.xml +++ b/P5/Source/Specs/seriesStmt.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/set.xml b/P5/Source/Specs/set.xml index 1b5d08b0d4..47cfbfa483 100644 --- a/P5/Source/Specs/set.xml +++ b/P5/Source/Specs/set.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/setting.xml b/P5/Source/Specs/setting.xml index 69a5956412..64c800e7b1 100644 --- a/P5/Source/Specs/setting.xml +++ b/P5/Source/Specs/setting.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/settingDesc.xml b/P5/Source/Specs/settingDesc.xml index b02d9e58bc..ccf1394356 100644 --- a/P5/Source/Specs/settingDesc.xml +++ b/P5/Source/Specs/settingDesc.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/shift.xml b/P5/Source/Specs/shift.xml index b73d1fd52e..062aeb1ea7 100644 --- a/P5/Source/Specs/shift.xml +++ b/P5/Source/Specs/shift.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/sic.xml b/P5/Source/Specs/sic.xml index 83b7b9ace4..8231191379 100644 --- a/P5/Source/Specs/sic.xml +++ b/P5/Source/Specs/sic.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/signatures.xml b/P5/Source/Specs/signatures.xml index fbf77d5463..da4fb74723 100644 --- a/P5/Source/Specs/signatures.xml +++ b/P5/Source/Specs/signatures.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/signed.xml b/P5/Source/Specs/signed.xml index f49316e0e0..c8a8f0cf93 100644 --- a/P5/Source/Specs/signed.xml +++ b/P5/Source/Specs/signed.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/soCalled.xml b/P5/Source/Specs/soCalled.xml index 0557283655..2bbe980c98 100644 --- a/P5/Source/Specs/soCalled.xml +++ b/P5/Source/Specs/soCalled.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/sound.xml b/P5/Source/Specs/sound.xml index 44400d7a3b..2c2ff455e8 100644 --- a/P5/Source/Specs/sound.xml +++ b/P5/Source/Specs/sound.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/source.xml b/P5/Source/Specs/source.xml index 07aab737f2..e947709180 100644 --- a/P5/Source/Specs/source.xml +++ b/P5/Source/Specs/source.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/sourceDesc.xml b/P5/Source/Specs/sourceDesc.xml index cbf92ec831..c6cd51625e 100644 --- a/P5/Source/Specs/sourceDesc.xml +++ b/P5/Source/Specs/sourceDesc.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/sourceDoc.xml b/P5/Source/Specs/sourceDoc.xml index 745cfaa0ab..e1139403c7 100644 --- a/P5/Source/Specs/sourceDoc.xml +++ b/P5/Source/Specs/sourceDoc.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/sp.xml b/P5/Source/Specs/sp.xml index 304e05c17b..2ea0276125 100644 --- a/P5/Source/Specs/sp.xml +++ b/P5/Source/Specs/sp.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/spGrp.xml b/P5/Source/Specs/spGrp.xml index 74189f9318..e124a5f898 100644 --- a/P5/Source/Specs/spGrp.xml +++ b/P5/Source/Specs/spGrp.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/space.xml b/P5/Source/Specs/space.xml index 0ccf08fe91..896094e328 100644 --- a/P5/Source/Specs/space.xml +++ b/P5/Source/Specs/space.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/span.xml b/P5/Source/Specs/span.xml index e4db80bedc..a0d2d2a16c 100644 --- a/P5/Source/Specs/span.xml +++ b/P5/Source/Specs/span.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/spanGrp.xml b/P5/Source/Specs/spanGrp.xml index 3aa3efa293..3f86d96918 100644 --- a/P5/Source/Specs/spanGrp.xml +++ b/P5/Source/Specs/spanGrp.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/speaker.xml b/P5/Source/Specs/speaker.xml index 97f236f2b0..46d6ded603 100644 --- a/P5/Source/Specs/speaker.xml +++ b/P5/Source/Specs/speaker.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/specDesc.xml b/P5/Source/Specs/specDesc.xml index 1d56a95780..35f3f5b1d6 100644 --- a/P5/Source/Specs/specDesc.xml +++ b/P5/Source/Specs/specDesc.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/specGrp.xml b/P5/Source/Specs/specGrp.xml index 3759c4c82b..961e3e511d 100644 --- a/P5/Source/Specs/specGrp.xml +++ b/P5/Source/Specs/specGrp.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/specGrpRef.xml b/P5/Source/Specs/specGrpRef.xml index 3362ea72d9..3e914fd8ae 100644 --- a/P5/Source/Specs/specGrpRef.xml +++ b/P5/Source/Specs/specGrpRef.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/specList.xml b/P5/Source/Specs/specList.xml index c45e6dee1e..daf80dd6cd 100644 --- a/P5/Source/Specs/specList.xml +++ b/P5/Source/Specs/specList.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/stage.xml b/P5/Source/Specs/stage.xml index 40b592d57c..decf7c7fdd 100644 --- a/P5/Source/Specs/stage.xml +++ b/P5/Source/Specs/stage.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/standOff.xml b/P5/Source/Specs/standOff.xml index 679102b394..2fd9814065 100644 --- a/P5/Source/Specs/standOff.xml +++ b/P5/Source/Specs/standOff.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/street.xml b/P5/Source/Specs/street.xml index 7ad04f1d0f..b5d8888ae2 100644 --- a/P5/Source/Specs/street.xml +++ b/P5/Source/Specs/street.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/stress.xml b/P5/Source/Specs/stress.xml index e00c87c03b..2d59a1b40f 100644 --- a/P5/Source/Specs/stress.xml +++ b/P5/Source/Specs/stress.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/string.xml b/P5/Source/Specs/string.xml index 7706028626..e2cfb527f6 100644 --- a/P5/Source/Specs/string.xml +++ b/P5/Source/Specs/string.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/styleDefDecl.xml b/P5/Source/Specs/styleDefDecl.xml index 6809677d58..62809d322c 100644 --- a/P5/Source/Specs/styleDefDecl.xml +++ b/P5/Source/Specs/styleDefDecl.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/subc.xml b/P5/Source/Specs/subc.xml index 5cc296352c..08a1897755 100644 --- a/P5/Source/Specs/subc.xml +++ b/P5/Source/Specs/subc.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/subst.xml b/P5/Source/Specs/subst.xml index 3e7b2cc575..5ae7359022 100644 --- a/P5/Source/Specs/subst.xml +++ b/P5/Source/Specs/subst.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/substJoin.xml b/P5/Source/Specs/substJoin.xml index 70c91a8138..cc6101fd28 100644 --- a/P5/Source/Specs/substJoin.xml +++ b/P5/Source/Specs/substJoin.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/summary.xml b/P5/Source/Specs/summary.xml index 6e4e6db0c7..658ee76957 100644 --- a/P5/Source/Specs/summary.xml +++ b/P5/Source/Specs/summary.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/superEntry.xml b/P5/Source/Specs/superEntry.xml index 65220fab2b..cab6f06146 100644 --- a/P5/Source/Specs/superEntry.xml +++ b/P5/Source/Specs/superEntry.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/supplied.xml b/P5/Source/Specs/supplied.xml index 029f9d2972..8ca8261e1b 100644 --- a/P5/Source/Specs/supplied.xml +++ b/P5/Source/Specs/supplied.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/support.xml b/P5/Source/Specs/support.xml index ac90f6d69a..93018995bd 100644 --- a/P5/Source/Specs/support.xml +++ b/P5/Source/Specs/support.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/supportDesc.xml b/P5/Source/Specs/supportDesc.xml index 093c210637..6e7aa4bbdc 100644 --- a/P5/Source/Specs/supportDesc.xml +++ b/P5/Source/Specs/supportDesc.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/surface.xml b/P5/Source/Specs/surface.xml index 1583ed2125..e6c82216d8 100644 --- a/P5/Source/Specs/surface.xml +++ b/P5/Source/Specs/surface.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/surfaceGrp.xml b/P5/Source/Specs/surfaceGrp.xml index 8ac125249e..a519536497 100644 --- a/P5/Source/Specs/surfaceGrp.xml +++ b/P5/Source/Specs/surfaceGrp.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/surname.xml b/P5/Source/Specs/surname.xml index 85d72fc318..77c00ff363 100644 --- a/P5/Source/Specs/surname.xml +++ b/P5/Source/Specs/surname.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/surplus.xml b/P5/Source/Specs/surplus.xml index dbbda6824d..0403081c34 100644 --- a/P5/Source/Specs/surplus.xml +++ b/P5/Source/Specs/surplus.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/surrogates.xml b/P5/Source/Specs/surrogates.xml index 6623e368d4..569de8ced0 100644 --- a/P5/Source/Specs/surrogates.xml +++ b/P5/Source/Specs/surrogates.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/syll.xml b/P5/Source/Specs/syll.xml index 0a1749ef40..c9901c316c 100644 --- a/P5/Source/Specs/syll.xml +++ b/P5/Source/Specs/syll.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/symbol.xml b/P5/Source/Specs/symbol.xml index 43152cafe3..2b0e10a514 100644 --- a/P5/Source/Specs/symbol.xml +++ b/P5/Source/Specs/symbol.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/table.xml b/P5/Source/Specs/table.xml index 9c14ffb87c..006341f9e3 100644 --- a/P5/Source/Specs/table.xml +++ b/P5/Source/Specs/table.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/tag.xml b/P5/Source/Specs/tag.xml index 2201b0c96f..340052f631 100644 --- a/P5/Source/Specs/tag.xml +++ b/P5/Source/Specs/tag.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/tagUsage.xml b/P5/Source/Specs/tagUsage.xml index 4997fe03ff..8d30ff80e6 100644 --- a/P5/Source/Specs/tagUsage.xml +++ b/P5/Source/Specs/tagUsage.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/tagsDecl.xml b/P5/Source/Specs/tagsDecl.xml index 728167e24b..49c2afd87b 100644 --- a/P5/Source/Specs/tagsDecl.xml +++ b/P5/Source/Specs/tagsDecl.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/taxonomy.xml b/P5/Source/Specs/taxonomy.xml index 089d2aaea4..d27bc30c31 100644 --- a/P5/Source/Specs/taxonomy.xml +++ b/P5/Source/Specs/taxonomy.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/tech.xml b/P5/Source/Specs/tech.xml index da4991e0d0..01a8038611 100644 --- a/P5/Source/Specs/tech.xml +++ b/P5/Source/Specs/tech.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/teiCorpus.xml b/P5/Source/Specs/teiCorpus.xml index 20e651a103..1977aac53f 100644 --- a/P5/Source/Specs/teiCorpus.xml +++ b/P5/Source/Specs/teiCorpus.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/teiHeader.xml b/P5/Source/Specs/teiHeader.xml index 8c42224c5b..14b9998179 100644 --- a/P5/Source/Specs/teiHeader.xml +++ b/P5/Source/Specs/teiHeader.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/teidata.authority.xml b/P5/Source/Specs/teidata.authority.xml index 8a0d3456cc..694dfb2c67 100644 --- a/P5/Source/Specs/teidata.authority.xml +++ b/P5/Source/Specs/teidata.authority.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/teidata.certainty.xml b/P5/Source/Specs/teidata.certainty.xml index 6324feddb3..ad8777a528 100644 --- a/P5/Source/Specs/teidata.certainty.xml +++ b/P5/Source/Specs/teidata.certainty.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/teidata.count.xml b/P5/Source/Specs/teidata.count.xml index 2c9ac37563..583ae1667d 100644 --- a/P5/Source/Specs/teidata.count.xml +++ b/P5/Source/Specs/teidata.count.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/teidata.duration.iso.xml b/P5/Source/Specs/teidata.duration.iso.xml index 84bd548c1a..ff803c7ffa 100644 --- a/P5/Source/Specs/teidata.duration.iso.xml +++ b/P5/Source/Specs/teidata.duration.iso.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/teidata.duration.w3c.xml b/P5/Source/Specs/teidata.duration.w3c.xml index ec001f8c1b..c712ae001e 100644 --- a/P5/Source/Specs/teidata.duration.w3c.xml +++ b/P5/Source/Specs/teidata.duration.w3c.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/teidata.enumerated.xml b/P5/Source/Specs/teidata.enumerated.xml index 9777ea1301..16c7fb66f3 100644 --- a/P5/Source/Specs/teidata.enumerated.xml +++ b/P5/Source/Specs/teidata.enumerated.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/teidata.gender.xml b/P5/Source/Specs/teidata.gender.xml index 40ec63b81b..fe83c77288 100644 --- a/P5/Source/Specs/teidata.gender.xml +++ b/P5/Source/Specs/teidata.gender.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/teidata.interval.xml b/P5/Source/Specs/teidata.interval.xml index 8bb14ea458..ef3feb4eb6 100644 --- a/P5/Source/Specs/teidata.interval.xml +++ b/P5/Source/Specs/teidata.interval.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/teidata.key.xml b/P5/Source/Specs/teidata.key.xml index e82339f174..1003467073 100644 --- a/P5/Source/Specs/teidata.key.xml +++ b/P5/Source/Specs/teidata.key.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/teidata.language.xml b/P5/Source/Specs/teidata.language.xml index e97a3fc5db..ab68557d7a 100644 --- a/P5/Source/Specs/teidata.language.xml +++ b/P5/Source/Specs/teidata.language.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/teidata.name.xml b/P5/Source/Specs/teidata.name.xml index 38f7544005..75c58adab1 100644 --- a/P5/Source/Specs/teidata.name.xml +++ b/P5/Source/Specs/teidata.name.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/teidata.namespace.xml b/P5/Source/Specs/teidata.namespace.xml index 14580b7d5c..6d0613bae5 100644 --- a/P5/Source/Specs/teidata.namespace.xml +++ b/P5/Source/Specs/teidata.namespace.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/teidata.namespaceOrName.xml b/P5/Source/Specs/teidata.namespaceOrName.xml index 5c597b5a5c..be04283789 100644 --- a/P5/Source/Specs/teidata.namespaceOrName.xml +++ b/P5/Source/Specs/teidata.namespaceOrName.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/teidata.nullOrName.xml b/P5/Source/Specs/teidata.nullOrName.xml index d8165b539a..8b944dd974 100644 --- a/P5/Source/Specs/teidata.nullOrName.xml +++ b/P5/Source/Specs/teidata.nullOrName.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/teidata.numeric.xml b/P5/Source/Specs/teidata.numeric.xml index 4649dd6f81..9015adcaa7 100644 --- a/P5/Source/Specs/teidata.numeric.xml +++ b/P5/Source/Specs/teidata.numeric.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/teidata.outputMeasurement.xml b/P5/Source/Specs/teidata.outputMeasurement.xml index a3bb6c9b45..77679f1c10 100644 --- a/P5/Source/Specs/teidata.outputMeasurement.xml +++ b/P5/Source/Specs/teidata.outputMeasurement.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/teidata.pattern.xml b/P5/Source/Specs/teidata.pattern.xml index d9c41dd206..2ed5381daf 100644 --- a/P5/Source/Specs/teidata.pattern.xml +++ b/P5/Source/Specs/teidata.pattern.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/teidata.point.xml b/P5/Source/Specs/teidata.point.xml index 34db58485b..db8aec7bb0 100644 --- a/P5/Source/Specs/teidata.point.xml +++ b/P5/Source/Specs/teidata.point.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/teidata.pointer.xml b/P5/Source/Specs/teidata.pointer.xml index 9bb29db87f..efb7aac0c7 100644 --- a/P5/Source/Specs/teidata.pointer.xml +++ b/P5/Source/Specs/teidata.pointer.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/teidata.prefix.xml b/P5/Source/Specs/teidata.prefix.xml index 562c4ef6c3..ff2f82d0ef 100644 --- a/P5/Source/Specs/teidata.prefix.xml +++ b/P5/Source/Specs/teidata.prefix.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/teidata.probability.xml b/P5/Source/Specs/teidata.probability.xml index 5267be894d..55c99415a4 100644 --- a/P5/Source/Specs/teidata.probability.xml +++ b/P5/Source/Specs/teidata.probability.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/teidata.replacement.xml b/P5/Source/Specs/teidata.replacement.xml index a7b7e7ae38..d1f7ea7d08 100644 --- a/P5/Source/Specs/teidata.replacement.xml +++ b/P5/Source/Specs/teidata.replacement.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/teidata.sex.xml b/P5/Source/Specs/teidata.sex.xml index b57a7f5892..be3b96f47f 100644 --- a/P5/Source/Specs/teidata.sex.xml +++ b/P5/Source/Specs/teidata.sex.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/teidata.temporal.iso.xml b/P5/Source/Specs/teidata.temporal.iso.xml index d395a42d73..75964bf230 100644 --- a/P5/Source/Specs/teidata.temporal.iso.xml +++ b/P5/Source/Specs/teidata.temporal.iso.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/teidata.temporal.w3c.xml b/P5/Source/Specs/teidata.temporal.w3c.xml index dbd4117f63..bcee15e3e6 100644 --- a/P5/Source/Specs/teidata.temporal.w3c.xml +++ b/P5/Source/Specs/teidata.temporal.w3c.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/teidata.temporal.working.xml b/P5/Source/Specs/teidata.temporal.working.xml index c154784dc2..cf91487174 100644 --- a/P5/Source/Specs/teidata.temporal.working.xml +++ b/P5/Source/Specs/teidata.temporal.working.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/teidata.text.xml b/P5/Source/Specs/teidata.text.xml index 49773b8e81..6ba64e7103 100644 --- a/P5/Source/Specs/teidata.text.xml +++ b/P5/Source/Specs/teidata.text.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/teidata.truthValue.xml b/P5/Source/Specs/teidata.truthValue.xml index 55f8efcf02..f18af99ec4 100644 --- a/P5/Source/Specs/teidata.truthValue.xml +++ b/P5/Source/Specs/teidata.truthValue.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/teidata.unboundedCount.xml b/P5/Source/Specs/teidata.unboundedCount.xml index cf07468081..13bc913069 100644 --- a/P5/Source/Specs/teidata.unboundedCount.xml +++ b/P5/Source/Specs/teidata.unboundedCount.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/teidata.version.xml b/P5/Source/Specs/teidata.version.xml index 43519979cd..f5637c06ff 100644 --- a/P5/Source/Specs/teidata.version.xml +++ b/P5/Source/Specs/teidata.version.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/teidata.versionNumber.xml b/P5/Source/Specs/teidata.versionNumber.xml index a4599773fd..23227e843c 100644 --- a/P5/Source/Specs/teidata.versionNumber.xml +++ b/P5/Source/Specs/teidata.versionNumber.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/teidata.word.xml b/P5/Source/Specs/teidata.word.xml index 5c140b765d..9dd5f9390f 100644 --- a/P5/Source/Specs/teidata.word.xml +++ b/P5/Source/Specs/teidata.word.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/teidata.xTruthValue.xml b/P5/Source/Specs/teidata.xTruthValue.xml index 7e5a6939a5..70d229382d 100644 --- a/P5/Source/Specs/teidata.xTruthValue.xml +++ b/P5/Source/Specs/teidata.xTruthValue.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/teidata.xmlName.xml b/P5/Source/Specs/teidata.xmlName.xml index 6f9df6ff7e..dfb525e396 100644 --- a/P5/Source/Specs/teidata.xmlName.xml +++ b/P5/Source/Specs/teidata.xmlName.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/teidata.xpath.xml b/P5/Source/Specs/teidata.xpath.xml index 8f83f1e816..88fa12e371 100644 --- a/P5/Source/Specs/teidata.xpath.xml +++ b/P5/Source/Specs/teidata.xpath.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/term.xml b/P5/Source/Specs/term.xml index 951ef269c0..8b205ffcbb 100644 --- a/P5/Source/Specs/term.xml +++ b/P5/Source/Specs/term.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/text.xml b/P5/Source/Specs/text.xml index af7211b633..45927be403 100644 --- a/P5/Source/Specs/text.xml +++ b/P5/Source/Specs/text.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/textClass.xml b/P5/Source/Specs/textClass.xml index dd488c822e..30b7879dbd 100644 --- a/P5/Source/Specs/textClass.xml +++ b/P5/Source/Specs/textClass.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/textDesc.xml b/P5/Source/Specs/textDesc.xml index 0f2fc18b21..c9ebd1c9e3 100644 --- a/P5/Source/Specs/textDesc.xml +++ b/P5/Source/Specs/textDesc.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/textLang.xml b/P5/Source/Specs/textLang.xml index 479142edea..2a5db7d142 100644 --- a/P5/Source/Specs/textLang.xml +++ b/P5/Source/Specs/textLang.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/textNode.xml b/P5/Source/Specs/textNode.xml index 26a6f80f09..b1880ce002 100644 --- a/P5/Source/Specs/textNode.xml +++ b/P5/Source/Specs/textNode.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/then.xml b/P5/Source/Specs/then.xml index d9eec07272..ca933db3dd 100644 --- a/P5/Source/Specs/then.xml +++ b/P5/Source/Specs/then.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/time.xml b/P5/Source/Specs/time.xml index ad92fe1a22..57f9fc9630 100644 --- a/P5/Source/Specs/time.xml +++ b/P5/Source/Specs/time.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/timeline.xml b/P5/Source/Specs/timeline.xml index f4e0f564c4..b707d5350e 100644 --- a/P5/Source/Specs/timeline.xml +++ b/P5/Source/Specs/timeline.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/titlePage.xml b/P5/Source/Specs/titlePage.xml index c60811e765..88e8be433d 100644 --- a/P5/Source/Specs/titlePage.xml +++ b/P5/Source/Specs/titlePage.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/titlePart.xml b/P5/Source/Specs/titlePart.xml index 1030d9c704..0e97fa4922 100644 --- a/P5/Source/Specs/titlePart.xml +++ b/P5/Source/Specs/titlePart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/titleStmt.xml b/P5/Source/Specs/titleStmt.xml index 0455cf0e2b..783e8749e9 100644 --- a/P5/Source/Specs/titleStmt.xml +++ b/P5/Source/Specs/titleStmt.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/tns.xml b/P5/Source/Specs/tns.xml index c616e4ad2f..8d292fd826 100644 --- a/P5/Source/Specs/tns.xml +++ b/P5/Source/Specs/tns.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/trailer.xml b/P5/Source/Specs/trailer.xml index 051734a859..7253cb814f 100644 --- a/P5/Source/Specs/trailer.xml +++ b/P5/Source/Specs/trailer.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/transcriptionDesc.xml b/P5/Source/Specs/transcriptionDesc.xml index ea2b4a1bd2..618c60aff7 100644 --- a/P5/Source/Specs/transcriptionDesc.xml +++ b/P5/Source/Specs/transcriptionDesc.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/transpose.xml b/P5/Source/Specs/transpose.xml index 2a00899d61..1329f0e8b2 100644 --- a/P5/Source/Specs/transpose.xml +++ b/P5/Source/Specs/transpose.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/tree.xml b/P5/Source/Specs/tree.xml index fb60d50287..a73125c013 100644 --- a/P5/Source/Specs/tree.xml +++ b/P5/Source/Specs/tree.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/triangle.xml b/P5/Source/Specs/triangle.xml index 0eeceaa997..4b746544c5 100644 --- a/P5/Source/Specs/triangle.xml +++ b/P5/Source/Specs/triangle.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/typeDesc.xml b/P5/Source/Specs/typeDesc.xml index d289209798..49d5692505 100644 --- a/P5/Source/Specs/typeDesc.xml +++ b/P5/Source/Specs/typeDesc.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/typeNote.xml b/P5/Source/Specs/typeNote.xml index 311207cb6b..e5aea87904 100644 --- a/P5/Source/Specs/typeNote.xml +++ b/P5/Source/Specs/typeNote.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/u.xml b/P5/Source/Specs/u.xml index 7996e27497..886455ea40 100644 --- a/P5/Source/Specs/u.xml +++ b/P5/Source/Specs/u.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/unclear.xml b/P5/Source/Specs/unclear.xml index 4fcf4d47bb..55d644b6b8 100644 --- a/P5/Source/Specs/unclear.xml +++ b/P5/Source/Specs/unclear.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/undo.xml b/P5/Source/Specs/undo.xml index 74fc3329f8..4b91a953e1 100644 --- a/P5/Source/Specs/undo.xml +++ b/P5/Source/Specs/undo.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/unicodeProp.xml b/P5/Source/Specs/unicodeProp.xml index accd341a78..f759a5680e 100644 --- a/P5/Source/Specs/unicodeProp.xml +++ b/P5/Source/Specs/unicodeProp.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/usg.xml b/P5/Source/Specs/usg.xml index 6425b822f2..e36a7412b3 100644 --- a/P5/Source/Specs/usg.xml +++ b/P5/Source/Specs/usg.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/vAlt.xml b/P5/Source/Specs/vAlt.xml index 76b8696dc2..c16caa0f54 100644 --- a/P5/Source/Specs/vAlt.xml +++ b/P5/Source/Specs/vAlt.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/vColl.xml b/P5/Source/Specs/vColl.xml index 15aa41de5b..14ad51e4fd 100644 --- a/P5/Source/Specs/vColl.xml +++ b/P5/Source/Specs/vColl.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/vDefault.xml b/P5/Source/Specs/vDefault.xml index 9c23ea6d5a..c09ac7b8ba 100644 --- a/P5/Source/Specs/vDefault.xml +++ b/P5/Source/Specs/vDefault.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/vLabel.xml b/P5/Source/Specs/vLabel.xml index e36049018c..9a3afe2e03 100644 --- a/P5/Source/Specs/vLabel.xml +++ b/P5/Source/Specs/vLabel.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/vMerge.xml b/P5/Source/Specs/vMerge.xml index e262c194d8..fe135a153e 100644 --- a/P5/Source/Specs/vMerge.xml +++ b/P5/Source/Specs/vMerge.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/vNot.xml b/P5/Source/Specs/vNot.xml index 02e5ac4b1e..5eb473360a 100644 --- a/P5/Source/Specs/vNot.xml +++ b/P5/Source/Specs/vNot.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/vRange.xml b/P5/Source/Specs/vRange.xml index e2c29bad4a..1e01198ad0 100644 --- a/P5/Source/Specs/vRange.xml +++ b/P5/Source/Specs/vRange.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/val.xml b/P5/Source/Specs/val.xml index 983e06b0a8..adc9675a45 100644 --- a/P5/Source/Specs/val.xml +++ b/P5/Source/Specs/val.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/valDesc.xml b/P5/Source/Specs/valDesc.xml index a490d925fc..65d03f1a79 100644 --- a/P5/Source/Specs/valDesc.xml +++ b/P5/Source/Specs/valDesc.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/valItem.xml b/P5/Source/Specs/valItem.xml index a2f0c381cd..fab5338e0e 100644 --- a/P5/Source/Specs/valItem.xml +++ b/P5/Source/Specs/valItem.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/valList.xml b/P5/Source/Specs/valList.xml index bc3ab4a215..5272421a27 100644 --- a/P5/Source/Specs/valList.xml +++ b/P5/Source/Specs/valList.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/variantEncoding.xml b/P5/Source/Specs/variantEncoding.xml index 51d2616312..3648eedb2a 100644 --- a/P5/Source/Specs/variantEncoding.xml +++ b/P5/Source/Specs/variantEncoding.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/view.xml b/P5/Source/Specs/view.xml index 66a71671dd..51ddf993cf 100644 --- a/P5/Source/Specs/view.xml +++ b/P5/Source/Specs/view.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/vocal.xml b/P5/Source/Specs/vocal.xml index 6c2f8d053f..fc4d99cba3 100644 --- a/P5/Source/Specs/vocal.xml +++ b/P5/Source/Specs/vocal.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/w.xml b/P5/Source/Specs/w.xml index b5ff2b7b1d..20e59131ae 100644 --- a/P5/Source/Specs/w.xml +++ b/P5/Source/Specs/w.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/watermark.xml b/P5/Source/Specs/watermark.xml index f2b8f6f3ce..3c97949666 100644 --- a/P5/Source/Specs/watermark.xml +++ b/P5/Source/Specs/watermark.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/when.xml b/P5/Source/Specs/when.xml index f109777b30..859bc110cc 100644 --- a/P5/Source/Specs/when.xml +++ b/P5/Source/Specs/when.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/width.xml b/P5/Source/Specs/width.xml index 610d9418c8..3613d9952e 100644 --- a/P5/Source/Specs/width.xml +++ b/P5/Source/Specs/width.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/wit.xml b/P5/Source/Specs/wit.xml index 9779c7992b..084fa3989d 100644 --- a/P5/Source/Specs/wit.xml +++ b/P5/Source/Specs/wit.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/witDetail.xml b/P5/Source/Specs/witDetail.xml index 08983d6465..c7687ab897 100644 --- a/P5/Source/Specs/witDetail.xml +++ b/P5/Source/Specs/witDetail.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/witEnd.xml b/P5/Source/Specs/witEnd.xml index 19fce91bd6..011b9967bc 100644 --- a/P5/Source/Specs/witEnd.xml +++ b/P5/Source/Specs/witEnd.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/witStart.xml b/P5/Source/Specs/witStart.xml index 8c42075373..37ef1986a6 100644 --- a/P5/Source/Specs/witStart.xml +++ b/P5/Source/Specs/witStart.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/witness.xml b/P5/Source/Specs/witness.xml index 3e17e4ef15..9d77bcea17 100644 --- a/P5/Source/Specs/witness.xml +++ b/P5/Source/Specs/witness.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/writing.xml b/P5/Source/Specs/writing.xml index 7bad204353..6f526b0324 100644 --- a/P5/Source/Specs/writing.xml +++ b/P5/Source/Specs/writing.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/xenoData.xml b/P5/Source/Specs/xenoData.xml index 3cb07cc48a..dbb1df763b 100644 --- a/P5/Source/Specs/xenoData.xml +++ b/P5/Source/Specs/xenoData.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/xr.xml b/P5/Source/Specs/xr.xml index 90be25df53..27fbc63be8 100644 --- a/P5/Source/Specs/xr.xml +++ b/P5/Source/Specs/xr.xml @@ -1,4 +1,3 @@ - diff --git a/P5/Source/Specs/zone.xml b/P5/Source/Specs/zone.xml index cfa9bff22c..7adee8a624 100644 --- a/P5/Source/Specs/zone.xml +++ b/P5/Source/Specs/zone.xml @@ -1,4 +1,3 @@ - From 9f058cb2cf4bbc7e558467db6383176a9487f699 Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Sat, 24 Feb 2024 16:53:27 -0500 Subject: [PATCH 033/127] Re-insert XML decls. (Thanks to @joeytakeda for noticing the boo-boo.) --- P5/Source/Guidelines/en/AB-About.xml | 1 + .../Guidelines/en/AI-AnalyticMechanisms.xml | 1 + P5/Source/Guidelines/en/BIB-Bibliography.xml | 4 +- .../Guidelines/en/CC-LanguageCorpora.xml | 1 + .../en/CE-CertaintyResponsibility.xml | 1 + .../en/CH-LanguagesCharacterSets.xml | 1 + P5/Source/Guidelines/en/CO-CoreElements.xml | 1 + P5/Source/Guidelines/en/COL-Colophon.xml | 1 + P5/Source/Guidelines/en/DEPRECATIONS.xml | 1 + .../Guidelines/en/DI-PrintDictionaries.xml | 1 + .../Guidelines/en/DR-PerformanceTexts.xml | 1 + .../Guidelines/en/DS-DefaultTextStructure.xml | 1 + P5/Source/Guidelines/en/Dedication.xml | 1 + .../Guidelines/en/FM1-IntroductoryNote.xml | 1 + .../Guidelines/en/FS-FeatureStructures.xml | 1 + .../en/FT-TablesFormulaeGraphics.xml | 1 + .../Guidelines/en/GD-GraphsNetworksTrees.xml | 1 + P5/Source/Guidelines/en/HD-Header.xml | 1 + .../en/MS-ManuscriptDescription.xml | 1 + P5/Source/Guidelines/en/ND-NamesDates.xml | 1 + .../Guidelines/en/NH-Non-hierarchical.xml | 1 + P5/Source/Guidelines/en/PARTIND.xml | 1 + P5/Source/Guidelines/en/PH-PrimarySources.xml | 1 + P5/Source/Guidelines/en/PrefatoryNote.xml | 1 + P5/Source/Guidelines/en/REF-ATTRIBUTES.xml | 1 + P5/Source/Guidelines/en/REF-CLASSES-ATTS.xml | 1 + P5/Source/Guidelines/en/REF-CLASSES-MODEL.xml | 1 + P5/Source/Guidelines/en/REF-ELEMENTS.xml | 1 + P5/Source/Guidelines/en/REF-MACROS.xml | 1 + .../en/SA-LinkingSegmentationAlignment.xml | 1 + .../Guidelines/en/SG-GentleIntroduction.xml | 1 + P5/Source/Guidelines/en/ST-Infrastructure.xml | 1 + .../Guidelines/en/TC-CriticalApparatus.xml | 1 + .../en/TD-DocumentationElements.xml | 1 + .../en/TS-TranscriptionsofSpeech.xml | 1 + P5/Source/Guidelines/en/TitlePageVerso.xml | 1 + P5/Source/Guidelines/en/USE.xml | 1 + P5/Source/Guidelines/en/VE-Verse.xml | 1 + .../en/WD-NonStandardCharacters.xml | 1 + P5/Source/Guidelines/fr/BIB-Bibliography.xml | 6374 ++++++++++++++++- P5/Source/Guidelines/fr/HD-Header.xml | 1 + P5/Source/Specs/TEI.xml | 1 + P5/Source/Specs/ab.xml | 1 + P5/Source/Specs/abbr.xml | 1 + P5/Source/Specs/abstract.xml | 1 + P5/Source/Specs/accMat.xml | 1 + P5/Source/Specs/acquisition.xml | 4 +- P5/Source/Specs/activity.xml | 4 +- P5/Source/Specs/actor.xml | 1 + P5/Source/Specs/add.xml | 1 + P5/Source/Specs/addName.xml | 1 + P5/Source/Specs/addSpan.xml | 1 + P5/Source/Specs/additional.xml | 1 + P5/Source/Specs/additions.xml | 1 + P5/Source/Specs/addrLine.xml | 1 + P5/Source/Specs/address.xml | 1 + P5/Source/Specs/adminInfo.xml | 1 + P5/Source/Specs/affiliation.xml | 4 +- P5/Source/Specs/age.xml | 4 +- P5/Source/Specs/alt.xml | 1 + P5/Source/Specs/altGrp.xml | 1 + P5/Source/Specs/altIdent.xml | 1 + P5/Source/Specs/altIdentifier.xml | 4 +- P5/Source/Specs/alternate.xml | 1 + P5/Source/Specs/am.xml | 1 + P5/Source/Specs/analytic.xml | 1 + P5/Source/Specs/anchor.xml | 1 + P5/Source/Specs/annotation.xml | 1 + P5/Source/Specs/annotationBlock.xml | 1 + P5/Source/Specs/anyElement.xml | 1 + P5/Source/Specs/app.xml | 1 + P5/Source/Specs/appInfo.xml | 1 + P5/Source/Specs/application.xml | 4 +- P5/Source/Specs/arc.xml | 1 + P5/Source/Specs/argument.xml | 1 + P5/Source/Specs/att.anchoring.xml | 1 + P5/Source/Specs/att.ascribed.directed.xml | 1 + P5/Source/Specs/att.ascribed.xml | 1 + P5/Source/Specs/att.breaking.xml | 1 + P5/Source/Specs/att.cReferencing.xml | 1 + P5/Source/Specs/att.calendarSystem.xml | 1 + P5/Source/Specs/att.canonical.xml | 1 + P5/Source/Specs/att.citeStructurePart.xml | 1 + P5/Source/Specs/att.citing.xml | 1 + P5/Source/Specs/att.combinable.xml | 1 + P5/Source/Specs/att.coordinated.xml | 1 + P5/Source/Specs/att.damaged.xml | 1 + P5/Source/Specs/att.datable.custom.xml | 1 + P5/Source/Specs/att.datable.iso.xml | 1 + P5/Source/Specs/att.datable.w3c.xml | 1 + P5/Source/Specs/att.datable.xml | 1 + P5/Source/Specs/att.datcat.xml | 1 + P5/Source/Specs/att.declarable.xml | 1 + P5/Source/Specs/att.declaring.xml | 1 + P5/Source/Specs/att.deprecated.xml | 1 + P5/Source/Specs/att.dimensions.xml | 1 + P5/Source/Specs/att.divLike.xml | 1 + P5/Source/Specs/att.docStatus.xml | 1 + P5/Source/Specs/att.duration.iso.xml | 1 + P5/Source/Specs/att.duration.w3c.xml | 1 + P5/Source/Specs/att.duration.xml | 1 + P5/Source/Specs/att.editLike.xml | 1 + P5/Source/Specs/att.edition.xml | 1 + P5/Source/Specs/att.enjamb.xml | 1 + P5/Source/Specs/att.entryLike.xml | 1 + P5/Source/Specs/att.formula.xml | 1 + P5/Source/Specs/att.fragmentable.xml | 1 + P5/Source/Specs/att.gaijiProp.xml | 1 + P5/Source/Specs/att.global.analytic.xml | 1 + P5/Source/Specs/att.global.change.xml | 1 + P5/Source/Specs/att.global.facs.xml | 1 + P5/Source/Specs/att.global.linking.xml | 1 + P5/Source/Specs/att.global.rendition.xml | 1 + P5/Source/Specs/att.global.responsibility.xml | 1 + P5/Source/Specs/att.global.source.xml | 1 + P5/Source/Specs/att.global.xml | 1 + P5/Source/Specs/att.handFeatures.xml | 1 + P5/Source/Specs/att.identified.xml | 1 + P5/Source/Specs/att.internetMedia.xml | 1 + P5/Source/Specs/att.interpLike.xml | 1 + .../Specs/att.lexicographic.normalized.xml | 4 +- P5/Source/Specs/att.lexicographic.xml | 1 + P5/Source/Specs/att.linguistic.xml | 1 + P5/Source/Specs/att.locatable.xml | 1 + P5/Source/Specs/att.measurement.xml | 1 + P5/Source/Specs/att.media.xml | 1 + P5/Source/Specs/att.metrical.xml | 1 + P5/Source/Specs/att.milestoneUnit.xml | 1 + P5/Source/Specs/att.msClass.xml | 1 + P5/Source/Specs/att.msExcerpt.xml | 1 + P5/Source/Specs/att.namespaceable.xml | 1 + P5/Source/Specs/att.naming.xml | 1 + P5/Source/Specs/att.notated.xml | 1 + P5/Source/Specs/att.partials.xml | 1 + P5/Source/Specs/att.patternReplacement.xml | 1 + P5/Source/Specs/att.personal.xml | 1 + P5/Source/Specs/att.placement.xml | 1 + P5/Source/Specs/att.pointing.group.xml | 1 + P5/Source/Specs/att.pointing.xml | 1 + P5/Source/Specs/att.predicate.xml | 1 + P5/Source/Specs/att.ranging.xml | 1 + P5/Source/Specs/att.rdgPart.xml | 1 + P5/Source/Specs/att.repeatable.xml | 1 + P5/Source/Specs/att.resourced.xml | 1 + P5/Source/Specs/att.scoping.xml | 1 + P5/Source/Specs/att.segLike.xml | 1 + P5/Source/Specs/att.sortable.xml | 1 + P5/Source/Specs/att.spanning.xml | 1 + P5/Source/Specs/att.styleDef.xml | 1 + P5/Source/Specs/att.tableDecoration.xml | 1 + P5/Source/Specs/att.textCritical.xml | 1 + P5/Source/Specs/att.timed.xml | 1 + P5/Source/Specs/att.transcriptional.xml | 1 + P5/Source/Specs/att.translatable.xml | 1 + P5/Source/Specs/att.typed.xml | 1 + P5/Source/Specs/att.witnessed.xml | 1 + P5/Source/Specs/att.written.xml | 1 + P5/Source/Specs/att.xml | 1 + P5/Source/Specs/attDef.xml | 1 + P5/Source/Specs/attList.xml | 1 + P5/Source/Specs/attRef.xml | 1 + P5/Source/Specs/author.xml | 4 +- P5/Source/Specs/authority.xml | 1 + P5/Source/Specs/availability.xml | 1 + P5/Source/Specs/back.xml | 1 + P5/Source/Specs/bibl.xml | 1 + P5/Source/Specs/biblFull.xml | 1 + P5/Source/Specs/biblScope.xml | 1 + P5/Source/Specs/biblStruct.xml | 1 + P5/Source/Specs/bicond.xml | 1 + P5/Source/Specs/binary.xml | 1 + P5/Source/Specs/binaryObject.xml | 1 + P5/Source/Specs/binding.xml | 4 +- P5/Source/Specs/bindingDesc.xml | 1 + P5/Source/Specs/birth.xml | 4 +- P5/Source/Specs/bloc.xml | 4 +- P5/Source/Specs/body.xml | 1 + P5/Source/Specs/broadcast.xml | 1 + P5/Source/Specs/byline.xml | 1 + P5/Source/Specs/c.xml | 1 + P5/Source/Specs/cRefPattern.xml | 1 + P5/Source/Specs/caesura.xml | 1 + P5/Source/Specs/calendar.xml | 1 + P5/Source/Specs/calendarDesc.xml | 1 + P5/Source/Specs/camera.xml | 1 + P5/Source/Specs/caption.xml | 1 + P5/Source/Specs/case.xml | 1 + P5/Source/Specs/castGroup.xml | 1 + P5/Source/Specs/castItem.xml | 1 + P5/Source/Specs/castList.xml | 1 + P5/Source/Specs/catDesc.xml | 1 + P5/Source/Specs/catRef.xml | 1 + P5/Source/Specs/catchwords.xml | 1 + P5/Source/Specs/category.xml | 1 + P5/Source/Specs/cb.xml | 1 + P5/Source/Specs/cell.xml | 1 + P5/Source/Specs/certainty.xml | 1 + P5/Source/Specs/change.xml | 4 +- P5/Source/Specs/channel.xml | 1 + P5/Source/Specs/char.xml | 1 + P5/Source/Specs/charDecl.xml | 1 + P5/Source/Specs/choice.xml | 1 + P5/Source/Specs/cit.xml | 1 + P5/Source/Specs/citeData.xml | 1 + P5/Source/Specs/citeStructure.xml | 1 + P5/Source/Specs/citedRange.xml | 1 + P5/Source/Specs/cl.xml | 1 + P5/Source/Specs/classCode.xml | 1 + P5/Source/Specs/classDecl.xml | 1 + P5/Source/Specs/classRef.xml | 1 + P5/Source/Specs/classSpec.xml | 1 + P5/Source/Specs/classes.xml | 1 + P5/Source/Specs/climate.xml | 4 +- P5/Source/Specs/closer.xml | 1 + P5/Source/Specs/code.xml | 1 + P5/Source/Specs/collation.xml | 1 + P5/Source/Specs/collection.xml | 1 + P5/Source/Specs/colloc.xml | 1 + P5/Source/Specs/colophon.xml | 1 + P5/Source/Specs/cond.xml | 1 + P5/Source/Specs/condition.xml | 1 + P5/Source/Specs/constitution.xml | 1 + P5/Source/Specs/constraint.xml | 1 + P5/Source/Specs/constraintSpec.xml | 1 + P5/Source/Specs/content.xml | 1 + P5/Source/Specs/conversion.xml | 4 +- P5/Source/Specs/corr.xml | 1 + P5/Source/Specs/correction.xml | 1 + P5/Source/Specs/correspAction.xml | 1 + P5/Source/Specs/correspContext.xml | 1 + P5/Source/Specs/correspDesc.xml | 1 + P5/Source/Specs/country.xml | 4 +- P5/Source/Specs/creation.xml | 4 +- P5/Source/Specs/custEvent.xml | 4 +- P5/Source/Specs/custodialHist.xml | 1 + P5/Source/Specs/damage.xml | 4 +- P5/Source/Specs/damageSpan.xml | 1 + P5/Source/Specs/dataFacet.xml | 1 + P5/Source/Specs/dataRef.xml | 1 + P5/Source/Specs/dataSpec.xml | 1 + P5/Source/Specs/datatype.xml | 1 + P5/Source/Specs/date.xml | 1 + P5/Source/Specs/dateline.xml | 1 + P5/Source/Specs/death.xml | 4 +- P5/Source/Specs/decoDesc.xml | 1 + P5/Source/Specs/decoNote.xml | 1 + P5/Source/Specs/def.xml | 1 + P5/Source/Specs/default.xml | 1 + P5/Source/Specs/defaultVal.xml | 1 + P5/Source/Specs/del.xml | 1 + P5/Source/Specs/delSpan.xml | 1 + P5/Source/Specs/depth.xml | 1 + P5/Source/Specs/derivation.xml | 1 + P5/Source/Specs/desc.xml | 1 + P5/Source/Specs/dictScrap.xml | 1 + P5/Source/Specs/dim.xml | 1 + P5/Source/Specs/dimensions.xml | 1 + P5/Source/Specs/distinct.xml | 1 + P5/Source/Specs/distributor.xml | 1 + P5/Source/Specs/district.xml | 4 +- P5/Source/Specs/div.xml | 1 + P5/Source/Specs/div1.xml | 1 + P5/Source/Specs/div2.xml | 1 + P5/Source/Specs/div3.xml | 1 + P5/Source/Specs/div4.xml | 1 + P5/Source/Specs/div5.xml | 1 + P5/Source/Specs/div6.xml | 1 + P5/Source/Specs/div7.xml | 1 + P5/Source/Specs/divGen.xml | 1 + P5/Source/Specs/docAuthor.xml | 1 + P5/Source/Specs/docDate.xml | 1 + P5/Source/Specs/docEdition.xml | 1 + P5/Source/Specs/docImprint.xml | 1 + P5/Source/Specs/docTitle.xml | 1 + P5/Source/Specs/domain.xml | 1 + P5/Source/Specs/eLeaf.xml | 1 + P5/Source/Specs/eTree.xml | 1 + P5/Source/Specs/edition.xml | 1 + P5/Source/Specs/editionStmt.xml | 1 + P5/Source/Specs/editor.xml | 4 +- P5/Source/Specs/editorialDecl.xml | 1 + P5/Source/Specs/education.xml | 4 +- P5/Source/Specs/eg.xml | 1 + P5/Source/Specs/egXML.xml | 1 + P5/Source/Specs/elementRef.xml | 1 + P5/Source/Specs/elementSpec.xml | 1 + P5/Source/Specs/ellipsis.xml | 1 + P5/Source/Specs/email.xml | 1 + P5/Source/Specs/emph.xml | 1 + P5/Source/Specs/empty.xml | 1 + P5/Source/Specs/encodingDesc.xml | 1 + P5/Source/Specs/entry.xml | 1 + P5/Source/Specs/entryFree.xml | 1 + P5/Source/Specs/epigraph.xml | 1 + P5/Source/Specs/epilogue.xml | 1 + P5/Source/Specs/equipment.xml | 1 + P5/Source/Specs/equiv.xml | 1 + P5/Source/Specs/etym.xml | 1 + P5/Source/Specs/event.xml | 1 + P5/Source/Specs/eventName.xml | 1 + P5/Source/Specs/ex.xml | 1 + P5/Source/Specs/exemplum.xml | 1 + P5/Source/Specs/expan.xml | 1 + P5/Source/Specs/explicit.xml | 1 + P5/Source/Specs/extent.xml | 1 + P5/Source/Specs/f.xml | 1 + P5/Source/Specs/fDecl.xml | 1 + P5/Source/Specs/fDescr.xml | 1 + P5/Source/Specs/fLib.xml | 1 + P5/Source/Specs/facsimile.xml | 1 + P5/Source/Specs/factuality.xml | 1 + P5/Source/Specs/faith.xml | 4 +- P5/Source/Specs/figDesc.xml | 1 + P5/Source/Specs/figure.xml | 1 + P5/Source/Specs/fileDesc.xml | 1 + P5/Source/Specs/filiation.xml | 1 + P5/Source/Specs/finalRubric.xml | 1 + P5/Source/Specs/floatingText.xml | 1 + P5/Source/Specs/floruit.xml | 4 +- P5/Source/Specs/foliation.xml | 1 + P5/Source/Specs/foreign.xml | 1 + P5/Source/Specs/forename.xml | 1 + P5/Source/Specs/forest.xml | 1 + P5/Source/Specs/form.xml | 1 + P5/Source/Specs/formula.xml | 1 + P5/Source/Specs/front.xml | 1 + P5/Source/Specs/fs.xml | 1 + P5/Source/Specs/fsConstraints.xml | 1 + P5/Source/Specs/fsDecl.xml | 1 + P5/Source/Specs/fsDescr.xml | 1 + P5/Source/Specs/fsdDecl.xml | 1 + P5/Source/Specs/fsdLink.xml | 1 + P5/Source/Specs/funder.xml | 4 +- P5/Source/Specs/fvLib.xml | 1 + P5/Source/Specs/fw.xml | 1 + P5/Source/Specs/g.xml | 1 + P5/Source/Specs/gap.xml | 1 + P5/Source/Specs/gb.xml | 1 + P5/Source/Specs/gen.xml | 1 + P5/Source/Specs/genName.xml | 1 + P5/Source/Specs/gender.xml | 4 +- P5/Source/Specs/geo.xml | 1 + P5/Source/Specs/geoDecl.xml | 1 + P5/Source/Specs/geogFeat.xml | 4 +- P5/Source/Specs/geogName.xml | 4 +- P5/Source/Specs/gi.xml | 1 + P5/Source/Specs/gloss.xml | 1 + P5/Source/Specs/glyph.xml | 1 + P5/Source/Specs/gram.xml | 1 + P5/Source/Specs/gramGrp.xml | 1 + P5/Source/Specs/graph.xml | 1 + P5/Source/Specs/graphic.xml | 1 + P5/Source/Specs/group.xml | 1 + P5/Source/Specs/handDesc.xml | 1 + P5/Source/Specs/handNote.xml | 1 + P5/Source/Specs/handNotes.xml | 1 + P5/Source/Specs/handShift.xml | 1 + P5/Source/Specs/head.xml | 1 + P5/Source/Specs/headItem.xml | 1 + P5/Source/Specs/headLabel.xml | 1 + P5/Source/Specs/height.xml | 1 + P5/Source/Specs/heraldry.xml | 1 + P5/Source/Specs/hi.xml | 1 + P5/Source/Specs/history.xml | 1 + P5/Source/Specs/hom.xml | 1 + P5/Source/Specs/hyph.xml | 1 + P5/Source/Specs/hyphenation.xml | 1 + P5/Source/Specs/iNode.xml | 1 + P5/Source/Specs/iType.xml | 1 + P5/Source/Specs/ident.xml | 1 + P5/Source/Specs/idno.xml | 4 +- P5/Source/Specs/if.xml | 1 + P5/Source/Specs/iff.xml | 1 + P5/Source/Specs/imprimatur.xml | 1 + P5/Source/Specs/imprint.xml | 1 + P5/Source/Specs/incident.xml | 1 + P5/Source/Specs/incipit.xml | 1 + P5/Source/Specs/index.xml | 1 + P5/Source/Specs/institution.xml | 1 + P5/Source/Specs/interaction.xml | 1 + P5/Source/Specs/interp.xml | 1 + P5/Source/Specs/interpGrp.xml | 1 + P5/Source/Specs/interpretation.xml | 1 + P5/Source/Specs/item.xml | 1 + P5/Source/Specs/join.xml | 1 + P5/Source/Specs/joinGrp.xml | 1 + P5/Source/Specs/keywords.xml | 1 + P5/Source/Specs/kinesic.xml | 1 + P5/Source/Specs/l.xml | 1 + P5/Source/Specs/label.xml | 1 + P5/Source/Specs/lacunaEnd.xml | 1 + P5/Source/Specs/lacunaStart.xml | 1 + P5/Source/Specs/lang.xml | 1 + P5/Source/Specs/langKnowledge.xml | 4 +- P5/Source/Specs/langKnown.xml | 4 +- P5/Source/Specs/langUsage.xml | 1 + P5/Source/Specs/language.xml | 1 + P5/Source/Specs/layout.xml | 1 + P5/Source/Specs/layoutDesc.xml | 1 + P5/Source/Specs/lb.xml | 1 + P5/Source/Specs/lbl.xml | 1 + P5/Source/Specs/leaf.xml | 1 + P5/Source/Specs/lem.xml | 4 +- P5/Source/Specs/lg.xml | 1 + P5/Source/Specs/licence.xml | 4 +- P5/Source/Specs/line.xml | 1 + P5/Source/Specs/link.xml | 1 + P5/Source/Specs/linkGrp.xml | 1 + P5/Source/Specs/list.xml | 1 + P5/Source/Specs/listAnnotation.xml | 1 + P5/Source/Specs/listApp.xml | 1 + P5/Source/Specs/listBibl.xml | 1 + P5/Source/Specs/listChange.xml | 1 + P5/Source/Specs/listEvent.xml | 1 + P5/Source/Specs/listForest.xml | 1 + P5/Source/Specs/listNym.xml | 1 + P5/Source/Specs/listObject.xml | 1 + P5/Source/Specs/listOrg.xml | 1 + P5/Source/Specs/listPerson.xml | 1 + P5/Source/Specs/listPlace.xml | 1 + P5/Source/Specs/listPrefixDef.xml | 1 + P5/Source/Specs/listRef.xml | 1 + P5/Source/Specs/listRelation.xml | 1 + P5/Source/Specs/listTranspose.xml | 1 + P5/Source/Specs/listWit.xml | 1 + P5/Source/Specs/localProp.xml | 1 + P5/Source/Specs/locale.xml | 1 + P5/Source/Specs/location.xml | 4 +- P5/Source/Specs/locus.xml | 1 + P5/Source/Specs/locusGrp.xml | 1 + P5/Source/Specs/m.xml | 1 + P5/Source/Specs/macro.abContent.xml | 1 + P5/Source/Specs/macro.limitedContent.xml | 1 + P5/Source/Specs/macro.paraContent.xml | 1 + P5/Source/Specs/macro.phraseSeq.limited.xml | 1 + P5/Source/Specs/macro.phraseSeq.xml | 1 + P5/Source/Specs/macro.specialPara.xml | 1 + P5/Source/Specs/macro.xtext.xml | 1 + P5/Source/Specs/macroRef.xml | 1 + P5/Source/Specs/macroSpec.xml | 1 + P5/Source/Specs/mapping.xml | 1 + P5/Source/Specs/material.xml | 1 + P5/Source/Specs/measure.xml | 1 + P5/Source/Specs/measureGrp.xml | 1 + P5/Source/Specs/media.xml | 1 + P5/Source/Specs/meeting.xml | 4 +- P5/Source/Specs/memberOf.xml | 1 + P5/Source/Specs/mentioned.xml | 1 + P5/Source/Specs/metDecl.xml | 1 + P5/Source/Specs/metSym.xml | 1 + P5/Source/Specs/metamark.xml | 1 + P5/Source/Specs/milestone.xml | 1 + P5/Source/Specs/mod.xml | 1 + P5/Source/Specs/model.addrPart.xml | 1 + P5/Source/Specs/model.addressLike.xml | 1 + P5/Source/Specs/model.annotationLike.xml | 1 + P5/Source/Specs/model.annotationPart.body.xml | 1 + P5/Source/Specs/model.applicationLike.xml | 1 + P5/Source/Specs/model.attributable.xml | 4 +- P5/Source/Specs/model.availabilityPart.xml | 1 + P5/Source/Specs/model.biblLike.xml | 1 + P5/Source/Specs/model.biblPart.xml | 1 + P5/Source/Specs/model.castItemPart.xml | 1 + P5/Source/Specs/model.catDescPart.xml | 1 + P5/Source/Specs/model.certLike.xml | 1 + P5/Source/Specs/model.choicePart.xml | 1 + P5/Source/Specs/model.common.xml | 1 + P5/Source/Specs/model.contentPart.xml | 1 + P5/Source/Specs/model.correspActionPart.xml | 1 + P5/Source/Specs/model.correspContextPart.xml | 1 + P5/Source/Specs/model.correspDescPart.xml | 1 + P5/Source/Specs/model.dateLike.xml | 1 + P5/Source/Specs/model.descLike.xml | 1 + P5/Source/Specs/model.describedResource.xml | 1 + P5/Source/Specs/model.dimLike.xml | 1 + P5/Source/Specs/model.div1Like.xml | 1 + P5/Source/Specs/model.div2Like.xml | 1 + P5/Source/Specs/model.div3Like.xml | 1 + P5/Source/Specs/model.div4Like.xml | 1 + P5/Source/Specs/model.div5Like.xml | 1 + P5/Source/Specs/model.div6Like.xml | 1 + P5/Source/Specs/model.div7Like.xml | 1 + P5/Source/Specs/model.divBottom.xml | 1 + P5/Source/Specs/model.divBottomPart.xml | 1 + P5/Source/Specs/model.divGenLike.xml | 1 + P5/Source/Specs/model.divLike.xml | 1 + P5/Source/Specs/model.divPart.spoken.xml | 1 + P5/Source/Specs/model.divPart.xml | 1 + P5/Source/Specs/model.divTop.xml | 1 + P5/Source/Specs/model.divTopPart.xml | 1 + P5/Source/Specs/model.divWrapper.xml | 1 + P5/Source/Specs/model.editorialDeclPart.xml | 1 + P5/Source/Specs/model.egLike.xml | 1 + P5/Source/Specs/model.emphLike.xml | 1 + P5/Source/Specs/model.encodingDescPart.xml | 1 + P5/Source/Specs/model.entryLike.xml | 1 + P5/Source/Specs/model.entryPart.top.xml | 1 + P5/Source/Specs/model.entryPart.xml | 1 + P5/Source/Specs/model.eventLike.xml | 1 + P5/Source/Specs/model.featureVal.complex.xml | 1 + P5/Source/Specs/model.featureVal.single.xml | 1 + P5/Source/Specs/model.featureVal.xml | 1 + P5/Source/Specs/model.formPart.xml | 1 + P5/Source/Specs/model.frontPart.drama.xml | 1 + P5/Source/Specs/model.frontPart.xml | 1 + P5/Source/Specs/model.fsdDeclPart.xml | 1 + P5/Source/Specs/model.gLike.xml | 1 + P5/Source/Specs/model.global.edit.xml | 1 + P5/Source/Specs/model.global.meta.xml | 1 + P5/Source/Specs/model.global.spoken.xml | 1 + P5/Source/Specs/model.global.xml | 1 + P5/Source/Specs/model.gramPart.xml | 1 + P5/Source/Specs/model.graphicLike.xml | 1 + P5/Source/Specs/model.headLike.xml | 1 + P5/Source/Specs/model.hiLike.xml | 1 + P5/Source/Specs/model.highlighted.xml | 1 + P5/Source/Specs/model.identEquiv.xml | 1 + P5/Source/Specs/model.identSynonyms.xml | 1 + P5/Source/Specs/model.imprintPart.xml | 1 + P5/Source/Specs/model.inter.xml | 1 + P5/Source/Specs/model.lLike.xml | 1 + P5/Source/Specs/model.lPart.xml | 1 + P5/Source/Specs/model.labelLike.xml | 1 + P5/Source/Specs/model.lexicalRefinement.xml | 1 + P5/Source/Specs/model.limitedPhrase.xml | 1 + P5/Source/Specs/model.linePart.xml | 1 + P5/Source/Specs/model.listLike.xml | 1 + P5/Source/Specs/model.measureLike.xml | 1 + P5/Source/Specs/model.milestoneLike.xml | 1 + P5/Source/Specs/model.morphLike.xml | 1 + P5/Source/Specs/model.msItemPart.xml | 1 + P5/Source/Specs/model.msQuoteLike.xml | 1 + P5/Source/Specs/model.nameLike.agent.xml | 1 + P5/Source/Specs/model.nameLike.xml | 1 + P5/Source/Specs/model.noteLike.xml | 1 + P5/Source/Specs/model.objectLike.xml | 4 +- P5/Source/Specs/model.oddDecl.xml | 1 + P5/Source/Specs/model.oddRef.xml | 1 + P5/Source/Specs/model.offsetLike.xml | 1 + P5/Source/Specs/model.orgPart.xml | 1 + P5/Source/Specs/model.orgStateLike.xml | 1 + P5/Source/Specs/model.pLike.front.xml | 1 + P5/Source/Specs/model.pLike.xml | 1 + P5/Source/Specs/model.pPart.data.xml | 1 + P5/Source/Specs/model.pPart.edit.xml | 1 + P5/Source/Specs/model.pPart.editorial.xml | 1 + P5/Source/Specs/model.pPart.msdesc.xml | 1 + .../Specs/model.pPart.transcriptional.xml | 1 + P5/Source/Specs/model.paraPart.xml | 1 + P5/Source/Specs/model.persNamePart.xml | 1 + P5/Source/Specs/model.persStateLike.xml | 1 + P5/Source/Specs/model.personLike.xml | 1 + P5/Source/Specs/model.personPart.xml | 1 + P5/Source/Specs/model.phrase.xml | 1 + P5/Source/Specs/model.phrase.xml.xml | 1 + P5/Source/Specs/model.physDescPart.xml | 1 + P5/Source/Specs/model.placeLike.xml | 1 + P5/Source/Specs/model.placeNamePart.xml | 1 + P5/Source/Specs/model.placeStateLike.xml | 1 + P5/Source/Specs/model.profileDescPart.xml | 1 + P5/Source/Specs/model.ptrLike.form.xml | 1 + P5/Source/Specs/model.ptrLike.xml | 1 + .../model.publicationStmtPart.agency.xml | 1 + .../model.publicationStmtPart.detail.xml | 1 + P5/Source/Specs/model.quoteLike.xml | 1 + P5/Source/Specs/model.rdgLike.xml | 1 + P5/Source/Specs/model.rdgPart.xml | 1 + P5/Source/Specs/model.recordingPart.xml | 1 + P5/Source/Specs/model.resource.xml | 1 + P5/Source/Specs/model.respLike.xml | 1 + P5/Source/Specs/model.segLike.xml | 1 + P5/Source/Specs/model.settingPart.xml | 1 + P5/Source/Specs/model.sourceDescPart.xml | 1 + P5/Source/Specs/model.specDescLike.xml | 1 + P5/Source/Specs/model.stageLike.xml | 1 + P5/Source/Specs/model.standOffPart.xml | 1 + P5/Source/Specs/model.teiHeaderPart.xml | 1 + P5/Source/Specs/model.textDescPart.xml | 1 + P5/Source/Specs/model.titlepagePart.xml | 1 + P5/Source/Specs/model.xml | 1 + P5/Source/Specs/modelGrp.xml | 1 + P5/Source/Specs/modelSequence.xml | 1 + P5/Source/Specs/moduleRef.xml | 1 + P5/Source/Specs/moduleSpec.xml | 1 + P5/Source/Specs/monogr.xml | 1 + P5/Source/Specs/mood.xml | 1 + P5/Source/Specs/move.xml | 1 + P5/Source/Specs/msContents.xml | 1 + P5/Source/Specs/msDesc.xml | 1 + P5/Source/Specs/msFrag.xml | 1 + P5/Source/Specs/msIdentifier.xml | 1 + P5/Source/Specs/msItem.xml | 1 + P5/Source/Specs/msItemStruct.xml | 1 + P5/Source/Specs/msName.xml | 1 + P5/Source/Specs/msPart.xml | 1 + P5/Source/Specs/musicNotation.xml | 1 + P5/Source/Specs/name.xml | 4 +- P5/Source/Specs/nameLink.xml | 1 + P5/Source/Specs/namespace.xml | 1 + P5/Source/Specs/nationality.xml | 4 +- P5/Source/Specs/node.xml | 1 + P5/Source/Specs/normalization.xml | 1 + P5/Source/Specs/notatedMusic.xml | 1 + P5/Source/Specs/note.xml | 1 + P5/Source/Specs/noteGrp.xml | 4 +- P5/Source/Specs/notesStmt.xml | 1 + P5/Source/Specs/num.xml | 1 + P5/Source/Specs/number.xml | 1 + P5/Source/Specs/numeric.xml | 1 + P5/Source/Specs/nym.xml | 1 + P5/Source/Specs/oRef.xml | 1 + P5/Source/Specs/object.xml | 4 +- P5/Source/Specs/objectDesc.xml | 1 + P5/Source/Specs/objectIdentifier.xml | 4 +- P5/Source/Specs/objectName.xml | 4 +- P5/Source/Specs/objectType.xml | 1 + P5/Source/Specs/occupation.xml | 4 +- P5/Source/Specs/offset.xml | 4 +- P5/Source/Specs/opener.xml | 1 + P5/Source/Specs/org.xml | 1 + P5/Source/Specs/orgName.xml | 4 +- P5/Source/Specs/orig.xml | 1 + P5/Source/Specs/origDate.xml | 1 + P5/Source/Specs/origPlace.xml | 4 +- P5/Source/Specs/origin.xml | 4 +- P5/Source/Specs/orth.xml | 1 + P5/Source/Specs/outputRendition.xml | 1 + P5/Source/Specs/p.xml | 1 + P5/Source/Specs/pRef.xml | 1 + P5/Source/Specs/param.xml | 1 + P5/Source/Specs/paramList.xml | 1 + P5/Source/Specs/paramSpec.xml | 1 + P5/Source/Specs/particDesc.xml | 1 + P5/Source/Specs/path.xml | 1 + P5/Source/Specs/pause.xml | 1 + P5/Source/Specs/pb.xml | 1 + P5/Source/Specs/pc.xml | 1 + P5/Source/Specs/per.xml | 1 + P5/Source/Specs/performance.xml | 1 + P5/Source/Specs/persName.xml | 4 +- P5/Source/Specs/persPronouns.xml | 4 +- P5/Source/Specs/person.xml | 1 + P5/Source/Specs/personGrp.xml | 1 + P5/Source/Specs/persona.xml | 1 + P5/Source/Specs/phr.xml | 1 + P5/Source/Specs/physDesc.xml | 1 + P5/Source/Specs/place.xml | 1 + P5/Source/Specs/placeName.xml | 4 +- P5/Source/Specs/population.xml | 4 +- P5/Source/Specs/pos.xml | 1 + P5/Source/Specs/postBox.xml | 1 + P5/Source/Specs/postCode.xml | 1 + P5/Source/Specs/postscript.xml | 1 + P5/Source/Specs/precision.xml | 4 +- P5/Source/Specs/prefixDef.xml | 1 + P5/Source/Specs/preparedness.xml | 1 + P5/Source/Specs/principal.xml | 4 +- P5/Source/Specs/profileDesc.xml | 1 + P5/Source/Specs/projectDesc.xml | 1 + P5/Source/Specs/prologue.xml | 1 + P5/Source/Specs/pron.xml | 1 + P5/Source/Specs/provenance.xml | 4 +- P5/Source/Specs/ptr.xml | 1 + P5/Source/Specs/pubPlace.xml | 1 + P5/Source/Specs/publicationStmt.xml | 1 + P5/Source/Specs/publisher.xml | 4 +- P5/Source/Specs/punctuation.xml | 1 + P5/Source/Specs/purpose.xml | 1 + P5/Source/Specs/q.xml | 1 + P5/Source/Specs/quotation.xml | 1 + P5/Source/Specs/quote.xml | 1 + P5/Source/Specs/rb.xml | 1 + P5/Source/Specs/rdg.xml | 1 + P5/Source/Specs/rdgGrp.xml | 1 + P5/Source/Specs/re.xml | 1 + P5/Source/Specs/recordHist.xml | 1 + P5/Source/Specs/recording.xml | 1 + P5/Source/Specs/recordingStmt.xml | 1 + P5/Source/Specs/redo.xml | 1 + P5/Source/Specs/ref.xml | 1 + P5/Source/Specs/refState.xml | 1 + P5/Source/Specs/refsDecl.xml | 1 + P5/Source/Specs/reg.xml | 1 + P5/Source/Specs/region.xml | 4 +- P5/Source/Specs/relatedItem.xml | 1 + P5/Source/Specs/relation.xml | 4 +- P5/Source/Specs/remarks.xml | 1 + P5/Source/Specs/rendition.xml | 1 + P5/Source/Specs/repository.xml | 1 + P5/Source/Specs/residence.xml | 4 +- P5/Source/Specs/resp.xml | 4 +- P5/Source/Specs/respStmt.xml | 1 + P5/Source/Specs/respons.xml | 1 + P5/Source/Specs/restore.xml | 1 + P5/Source/Specs/retrace.xml | 1 + P5/Source/Specs/revisionDesc.xml | 1 + P5/Source/Specs/rhyme.xml | 1 + P5/Source/Specs/role.xml | 1 + P5/Source/Specs/roleDesc.xml | 1 + P5/Source/Specs/roleName.xml | 1 + P5/Source/Specs/root.xml | 1 + P5/Source/Specs/row.xml | 1 + P5/Source/Specs/rs.xml | 1 + P5/Source/Specs/rt.xml | 1 + P5/Source/Specs/rubric.xml | 1 + P5/Source/Specs/ruby.xml | 1 + P5/Source/Specs/s.xml | 1 + P5/Source/Specs/said.xml | 1 + P5/Source/Specs/salute.xml | 1 + P5/Source/Specs/samplingDecl.xml | 1 + P5/Source/Specs/schemaRef.xml | 1 + P5/Source/Specs/schemaSpec.xml | 1 + P5/Source/Specs/scriptDesc.xml | 1 + P5/Source/Specs/scriptNote.xml | 1 + P5/Source/Specs/scriptStmt.xml | 1 + P5/Source/Specs/seal.xml | 4 +- P5/Source/Specs/sealDesc.xml | 1 + P5/Source/Specs/secFol.xml | 1 + P5/Source/Specs/secl.xml | 1 + P5/Source/Specs/seg.xml | 1 + P5/Source/Specs/segmentation.xml | 1 + P5/Source/Specs/sense.xml | 1 + P5/Source/Specs/sequence.xml | 1 + P5/Source/Specs/series.xml | 1 + P5/Source/Specs/seriesStmt.xml | 1 + P5/Source/Specs/set.xml | 1 + P5/Source/Specs/setting.xml | 1 + P5/Source/Specs/settingDesc.xml | 1 + P5/Source/Specs/settlement.xml | 4 +- P5/Source/Specs/sex.xml | 4 +- P5/Source/Specs/shift.xml | 1 + P5/Source/Specs/sic.xml | 1 + P5/Source/Specs/signatures.xml | 1 + P5/Source/Specs/signed.xml | 1 + P5/Source/Specs/soCalled.xml | 1 + P5/Source/Specs/socecStatus.xml | 4 +- P5/Source/Specs/sound.xml | 1 + P5/Source/Specs/source.xml | 1 + P5/Source/Specs/sourceDesc.xml | 1 + P5/Source/Specs/sourceDoc.xml | 1 + P5/Source/Specs/sp.xml | 1 + P5/Source/Specs/spGrp.xml | 1 + P5/Source/Specs/space.xml | 1 + P5/Source/Specs/span.xml | 1 + P5/Source/Specs/spanGrp.xml | 1 + P5/Source/Specs/speaker.xml | 1 + P5/Source/Specs/specDesc.xml | 1 + P5/Source/Specs/specGrp.xml | 1 + P5/Source/Specs/specGrpRef.xml | 1 + P5/Source/Specs/specList.xml | 1 + P5/Source/Specs/sponsor.xml | 4 +- P5/Source/Specs/stage.xml | 1 + P5/Source/Specs/stamp.xml | 4 +- P5/Source/Specs/standOff.xml | 1 + P5/Source/Specs/state.xml | 4 +- P5/Source/Specs/stdVals.xml | 1 + P5/Source/Specs/street.xml | 1 + P5/Source/Specs/stress.xml | 1 + P5/Source/Specs/string.xml | 1 + P5/Source/Specs/styleDefDecl.xml | 1 + P5/Source/Specs/subc.xml | 1 + P5/Source/Specs/subst.xml | 1 + P5/Source/Specs/substJoin.xml | 1 + P5/Source/Specs/summary.xml | 1 + P5/Source/Specs/superEntry.xml | 1 + P5/Source/Specs/supplied.xml | 1 + P5/Source/Specs/support.xml | 1 + P5/Source/Specs/supportDesc.xml | 1 + P5/Source/Specs/surface.xml | 1 + P5/Source/Specs/surfaceGrp.xml | 1 + P5/Source/Specs/surname.xml | 1 + P5/Source/Specs/surplus.xml | 1 + P5/Source/Specs/surrogates.xml | 1 + P5/Source/Specs/syll.xml | 1 + P5/Source/Specs/symbol.xml | 1 + P5/Source/Specs/table.xml | 1 + P5/Source/Specs/tag.xml | 1 + P5/Source/Specs/tagUsage.xml | 1 + P5/Source/Specs/tagsDecl.xml | 1 + P5/Source/Specs/taxonomy.xml | 1 + P5/Source/Specs/tech.xml | 1 + P5/Source/Specs/teiCorpus.xml | 1 + P5/Source/Specs/teiHeader.xml | 1 + P5/Source/Specs/teidata.authority.xml | 1 + P5/Source/Specs/teidata.certainty.xml | 1 + P5/Source/Specs/teidata.count.xml | 1 + P5/Source/Specs/teidata.duration.iso.xml | 1 + P5/Source/Specs/teidata.duration.w3c.xml | 1 + P5/Source/Specs/teidata.enumerated.xml | 1 + P5/Source/Specs/teidata.gender.xml | 1 + P5/Source/Specs/teidata.interval.xml | 1 + P5/Source/Specs/teidata.key.xml | 1 + P5/Source/Specs/teidata.language.xml | 1 + P5/Source/Specs/teidata.name.xml | 1 + P5/Source/Specs/teidata.namespace.xml | 1 + P5/Source/Specs/teidata.namespaceOrName.xml | 1 + P5/Source/Specs/teidata.nullOrName.xml | 1 + P5/Source/Specs/teidata.numeric.xml | 1 + P5/Source/Specs/teidata.outputMeasurement.xml | 1 + P5/Source/Specs/teidata.pattern.xml | 1 + P5/Source/Specs/teidata.point.xml | 1 + P5/Source/Specs/teidata.pointer.xml | 1 + P5/Source/Specs/teidata.prefix.xml | 1 + P5/Source/Specs/teidata.probCert.xml | 1 + P5/Source/Specs/teidata.probability.xml | 1 + P5/Source/Specs/teidata.replacement.xml | 1 + P5/Source/Specs/teidata.sex.xml | 1 + P5/Source/Specs/teidata.temporal.iso.xml | 1 + P5/Source/Specs/teidata.temporal.w3c.xml | 1 + P5/Source/Specs/teidata.temporal.working.xml | 1 + P5/Source/Specs/teidata.text.xml | 1 + P5/Source/Specs/teidata.truthValue.xml | 1 + P5/Source/Specs/teidata.unboundedCount.xml | 1 + P5/Source/Specs/teidata.version.xml | 1 + P5/Source/Specs/teidata.versionNumber.xml | 1 + P5/Source/Specs/teidata.word.xml | 1 + P5/Source/Specs/teidata.xTruthValue.xml | 1 + P5/Source/Specs/teidata.xmlName.xml | 1 + P5/Source/Specs/teidata.xpath.xml | 1 + P5/Source/Specs/term.xml | 1 + P5/Source/Specs/terrain.xml | 4 +- P5/Source/Specs/text.xml | 1 + P5/Source/Specs/textClass.xml | 1 + P5/Source/Specs/textDesc.xml | 1 + P5/Source/Specs/textLang.xml | 1 + P5/Source/Specs/textNode.xml | 1 + P5/Source/Specs/then.xml | 1 + P5/Source/Specs/time.xml | 1 + P5/Source/Specs/timeline.xml | 1 + P5/Source/Specs/title.xml | 4 +- P5/Source/Specs/titlePage.xml | 1 + P5/Source/Specs/titlePart.xml | 1 + P5/Source/Specs/titleStmt.xml | 1 + P5/Source/Specs/tns.xml | 1 + P5/Source/Specs/trailer.xml | 1 + P5/Source/Specs/trait.xml | 4 +- P5/Source/Specs/transcriptionDesc.xml | 1 + P5/Source/Specs/transpose.xml | 1 + P5/Source/Specs/tree.xml | 1 + P5/Source/Specs/triangle.xml | 1 + P5/Source/Specs/typeDesc.xml | 1 + P5/Source/Specs/typeNote.xml | 1 + P5/Source/Specs/u.xml | 1 + P5/Source/Specs/unclear.xml | 1 + P5/Source/Specs/undo.xml | 1 + P5/Source/Specs/unicodeProp.xml | 1 + P5/Source/Specs/unihanProp.xml | 1 + P5/Source/Specs/unit.xml | 1 + P5/Source/Specs/unitDecl.xml | 4 +- P5/Source/Specs/unitDef.xml | 4 +- P5/Source/Specs/usg.xml | 1 + P5/Source/Specs/vAlt.xml | 1 + P5/Source/Specs/vColl.xml | 1 + P5/Source/Specs/vDefault.xml | 1 + P5/Source/Specs/vLabel.xml | 1 + P5/Source/Specs/vMerge.xml | 1 + P5/Source/Specs/vNot.xml | 1 + P5/Source/Specs/vRange.xml | 1 + P5/Source/Specs/val.xml | 1 + P5/Source/Specs/valDesc.xml | 1 + P5/Source/Specs/valItem.xml | 1 + P5/Source/Specs/valList.xml | 1 + P5/Source/Specs/variantEncoding.xml | 1 + P5/Source/Specs/view.xml | 1 + P5/Source/Specs/vocal.xml | 1 + P5/Source/Specs/w.xml | 1 + P5/Source/Specs/watermark.xml | 1 + P5/Source/Specs/when.xml | 1 + P5/Source/Specs/width.xml | 1 + P5/Source/Specs/wit.xml | 1 + P5/Source/Specs/witDetail.xml | 1 + P5/Source/Specs/witEnd.xml | 1 + P5/Source/Specs/witStart.xml | 1 + P5/Source/Specs/witness.xml | 1 + P5/Source/Specs/writing.xml | 1 + P5/Source/Specs/xenoData.xml | 1 + P5/Source/Specs/xr.xml | 1 + P5/Source/Specs/zone.xml | 1 + 878 files changed, 7396 insertions(+), 74 deletions(-) mode change 120000 => 100644 P5/Source/Guidelines/fr/BIB-Bibliography.xml diff --git a/P5/Source/Guidelines/en/AB-About.xml b/P5/Source/Guidelines/en/AB-About.xml index 42ba61a551..f5bea382ae 100644 --- a/P5/Source/Guidelines/en/AB-About.xml +++ b/P5/Source/Guidelines/en/AB-About.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Guidelines/en/AI-AnalyticMechanisms.xml b/P5/Source/Guidelines/en/AI-AnalyticMechanisms.xml index 51916016ff..d478467d37 100644 --- a/P5/Source/Guidelines/en/AI-AnalyticMechanisms.xml +++ b/P5/Source/Guidelines/en/AI-AnalyticMechanisms.xml @@ -1,3 +1,4 @@ +
Simple Analytic Mechanisms diff --git a/P5/Source/Guidelines/en/BIB-Bibliography.xml b/P5/Source/Guidelines/en/BIB-Bibliography.xml index 885cba0cea..afcbd6e9e5 100644 --- a/P5/Source/Guidelines/en/BIB-Bibliography.xml +++ b/P5/Source/Guidelines/en/BIB-Bibliography.xml @@ -1,4 +1,6 @@ - + + +
Bibliography
diff --git a/P5/Source/Guidelines/en/CC-LanguageCorpora.xml b/P5/Source/Guidelines/en/CC-LanguageCorpora.xml index f4ca35b1c3..eaadfd720b 100644 --- a/P5/Source/Guidelines/en/CC-LanguageCorpora.xml +++ b/P5/Source/Guidelines/en/CC-LanguageCorpora.xml @@ -1,3 +1,4 @@ +
Language Corpora diff --git a/P5/Source/Guidelines/en/CE-CertaintyResponsibility.xml b/P5/Source/Guidelines/en/CE-CertaintyResponsibility.xml index 02675dd175..a0c5b4f902 100644 --- a/P5/Source/Guidelines/en/CE-CertaintyResponsibility.xml +++ b/P5/Source/Guidelines/en/CE-CertaintyResponsibility.xml @@ -1,3 +1,4 @@ +
Certainty, Precision, and Responsibility diff --git a/P5/Source/Guidelines/en/CH-LanguagesCharacterSets.xml b/P5/Source/Guidelines/en/CH-LanguagesCharacterSets.xml index ad367a5213..dca8219668 100644 --- a/P5/Source/Guidelines/en/CH-LanguagesCharacterSets.xml +++ b/P5/Source/Guidelines/en/CH-LanguagesCharacterSets.xml @@ -1,3 +1,4 @@ +
diff --git a/P5/Source/Guidelines/en/CO-CoreElements.xml b/P5/Source/Guidelines/en/CO-CoreElements.xml index 676c389f19..0a15fa3776 100644 --- a/P5/Source/Guidelines/en/CO-CoreElements.xml +++ b/P5/Source/Guidelines/en/CO-CoreElements.xml @@ -1,3 +1,4 @@ +
diff --git a/P5/Source/Guidelines/en/COL-Colophon.xml b/P5/Source/Guidelines/en/COL-Colophon.xml index 23f593e6a0..7500dddd9d 100644 --- a/P5/Source/Guidelines/en/COL-Colophon.xml +++ b/P5/Source/Guidelines/en/COL-Colophon.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Guidelines/en/DEPRECATIONS.xml b/P5/Source/Guidelines/en/DEPRECATIONS.xml index 5436fb1f7f..7f139ec965 100644 --- a/P5/Source/Guidelines/en/DEPRECATIONS.xml +++ b/P5/Source/Guidelines/en/DEPRECATIONS.xml @@ -1,3 +1,4 @@ +
diff --git a/P5/Source/Guidelines/en/DI-PrintDictionaries.xml b/P5/Source/Guidelines/en/DI-PrintDictionaries.xml index bcefb264a3..e031829598 100644 --- a/P5/Source/Guidelines/en/DI-PrintDictionaries.xml +++ b/P5/Source/Guidelines/en/DI-PrintDictionaries.xml @@ -1,3 +1,4 @@ +
diff --git a/P5/Source/Guidelines/en/DR-PerformanceTexts.xml b/P5/Source/Guidelines/en/DR-PerformanceTexts.xml index bfcf74fdea..233e1dbc4b 100644 --- a/P5/Source/Guidelines/en/DR-PerformanceTexts.xml +++ b/P5/Source/Guidelines/en/DR-PerformanceTexts.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Guidelines/en/DS-DefaultTextStructure.xml b/P5/Source/Guidelines/en/DS-DefaultTextStructure.xml index 953c585d79..b160c7afdd 100644 --- a/P5/Source/Guidelines/en/DS-DefaultTextStructure.xml +++ b/P5/Source/Guidelines/en/DS-DefaultTextStructure.xml @@ -1,3 +1,4 @@ +
diff --git a/P5/Source/Guidelines/en/Dedication.xml b/P5/Source/Guidelines/en/Dedication.xml index 3f105ab8b9..766e7443d7 100644 --- a/P5/Source/Guidelines/en/Dedication.xml +++ b/P5/Source/Guidelines/en/Dedication.xml @@ -1,3 +1,4 @@ +
diff --git a/P5/Source/Guidelines/en/FM1-IntroductoryNote.xml b/P5/Source/Guidelines/en/FM1-IntroductoryNote.xml index eb1ada5f01..c3492bfca2 100644 --- a/P5/Source/Guidelines/en/FM1-IntroductoryNote.xml +++ b/P5/Source/Guidelines/en/FM1-IntroductoryNote.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Guidelines/en/FS-FeatureStructures.xml b/P5/Source/Guidelines/en/FS-FeatureStructures.xml index 1a4c2cf972..933e6a14b5 100644 --- a/P5/Source/Guidelines/en/FS-FeatureStructures.xml +++ b/P5/Source/Guidelines/en/FS-FeatureStructures.xml @@ -1,3 +1,4 @@ +
Feature Structures diff --git a/P5/Source/Guidelines/en/FT-TablesFormulaeGraphics.xml b/P5/Source/Guidelines/en/FT-TablesFormulaeGraphics.xml index 4a66f2484c..4c4102bb21 100644 --- a/P5/Source/Guidelines/en/FT-TablesFormulaeGraphics.xml +++ b/P5/Source/Guidelines/en/FT-TablesFormulaeGraphics.xml @@ -1,3 +1,4 @@ +
diff --git a/P5/Source/Guidelines/en/GD-GraphsNetworksTrees.xml b/P5/Source/Guidelines/en/GD-GraphsNetworksTrees.xml index f4491bd8c6..415d9f2e62 100644 --- a/P5/Source/Guidelines/en/GD-GraphsNetworksTrees.xml +++ b/P5/Source/Guidelines/en/GD-GraphsNetworksTrees.xml @@ -1,3 +1,4 @@ +
Graphs, Networks, and Trees diff --git a/P5/Source/Guidelines/en/HD-Header.xml b/P5/Source/Guidelines/en/HD-Header.xml index 01ca4db0b6..b03c51e5d7 100644 --- a/P5/Source/Guidelines/en/HD-Header.xml +++ b/P5/Source/Guidelines/en/HD-Header.xml @@ -1,3 +1,4 @@ +
diff --git a/P5/Source/Guidelines/en/MS-ManuscriptDescription.xml b/P5/Source/Guidelines/en/MS-ManuscriptDescription.xml index 707db494e2..e43d0b3bc6 100644 --- a/P5/Source/Guidelines/en/MS-ManuscriptDescription.xml +++ b/P5/Source/Guidelines/en/MS-ManuscriptDescription.xml @@ -1,3 +1,4 @@ +
diff --git a/P5/Source/Guidelines/en/ND-NamesDates.xml b/P5/Source/Guidelines/en/ND-NamesDates.xml index c19d65555f..eff14c5bed 100644 --- a/P5/Source/Guidelines/en/ND-NamesDates.xml +++ b/P5/Source/Guidelines/en/ND-NamesDates.xml @@ -1,3 +1,4 @@ +
diff --git a/P5/Source/Guidelines/en/NH-Non-hierarchical.xml b/P5/Source/Guidelines/en/NH-Non-hierarchical.xml index a810a46b98..9a2e0f15af 100644 --- a/P5/Source/Guidelines/en/NH-Non-hierarchical.xml +++ b/P5/Source/Guidelines/en/NH-Non-hierarchical.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Guidelines/en/PARTIND.xml b/P5/Source/Guidelines/en/PARTIND.xml index 7efdd6160c..48e76ceaae 100644 --- a/P5/Source/Guidelines/en/PARTIND.xml +++ b/P5/Source/Guidelines/en/PARTIND.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Guidelines/en/PH-PrimarySources.xml b/P5/Source/Guidelines/en/PH-PrimarySources.xml index 4ac22926a4..73fb70d1a4 100644 --- a/P5/Source/Guidelines/en/PH-PrimarySources.xml +++ b/P5/Source/Guidelines/en/PH-PrimarySources.xml @@ -1,3 +1,4 @@ +
diff --git a/P5/Source/Guidelines/en/REF-ATTRIBUTES.xml b/P5/Source/Guidelines/en/REF-ATTRIBUTES.xml index 160ec9182d..24d14cad0f 100644 --- a/P5/Source/Guidelines/en/REF-ATTRIBUTES.xml +++ b/P5/Source/Guidelines/en/REF-ATTRIBUTES.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Guidelines/en/REF-CLASSES-ATTS.xml b/P5/Source/Guidelines/en/REF-CLASSES-ATTS.xml index f01fb8cecb..b52965be87 100644 --- a/P5/Source/Guidelines/en/REF-CLASSES-ATTS.xml +++ b/P5/Source/Guidelines/en/REF-CLASSES-ATTS.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Guidelines/en/REF-CLASSES-MODEL.xml b/P5/Source/Guidelines/en/REF-CLASSES-MODEL.xml index a22126f37f..5c12bc541f 100644 --- a/P5/Source/Guidelines/en/REF-CLASSES-MODEL.xml +++ b/P5/Source/Guidelines/en/REF-CLASSES-MODEL.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Guidelines/en/REF-ELEMENTS.xml b/P5/Source/Guidelines/en/REF-ELEMENTS.xml index 7342f68b86..581769398c 100644 --- a/P5/Source/Guidelines/en/REF-ELEMENTS.xml +++ b/P5/Source/Guidelines/en/REF-ELEMENTS.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Guidelines/en/REF-MACROS.xml b/P5/Source/Guidelines/en/REF-MACROS.xml index d30784f2bf..eeb913d8b2 100644 --- a/P5/Source/Guidelines/en/REF-MACROS.xml +++ b/P5/Source/Guidelines/en/REF-MACROS.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Guidelines/en/SA-LinkingSegmentationAlignment.xml b/P5/Source/Guidelines/en/SA-LinkingSegmentationAlignment.xml index e20d6056b9..3d8e462b99 100644 --- a/P5/Source/Guidelines/en/SA-LinkingSegmentationAlignment.xml +++ b/P5/Source/Guidelines/en/SA-LinkingSegmentationAlignment.xml @@ -1,3 +1,4 @@ +
diff --git a/P5/Source/Guidelines/en/SG-GentleIntroduction.xml b/P5/Source/Guidelines/en/SG-GentleIntroduction.xml index 90585c375c..9a63cb7059 100644 --- a/P5/Source/Guidelines/en/SG-GentleIntroduction.xml +++ b/P5/Source/Guidelines/en/SG-GentleIntroduction.xml @@ -1,3 +1,4 @@ +
diff --git a/P5/Source/Guidelines/en/ST-Infrastructure.xml b/P5/Source/Guidelines/en/ST-Infrastructure.xml index a474073f17..b141ec6789 100644 --- a/P5/Source/Guidelines/en/ST-Infrastructure.xml +++ b/P5/Source/Guidelines/en/ST-Infrastructure.xml @@ -1,3 +1,4 @@ +
diff --git a/P5/Source/Guidelines/en/TC-CriticalApparatus.xml b/P5/Source/Guidelines/en/TC-CriticalApparatus.xml index 93fcb0d8f1..d9970210f6 100644 --- a/P5/Source/Guidelines/en/TC-CriticalApparatus.xml +++ b/P5/Source/Guidelines/en/TC-CriticalApparatus.xml @@ -1,3 +1,4 @@ +
diff --git a/P5/Source/Guidelines/en/TD-DocumentationElements.xml b/P5/Source/Guidelines/en/TD-DocumentationElements.xml index 0b2b595ebd..1c08f566e9 100644 --- a/P5/Source/Guidelines/en/TD-DocumentationElements.xml +++ b/P5/Source/Guidelines/en/TD-DocumentationElements.xml @@ -1,3 +1,4 @@ +
diff --git a/P5/Source/Guidelines/en/TitlePageVerso.xml b/P5/Source/Guidelines/en/TitlePageVerso.xml index ea1b857235..b822117af9 100644 --- a/P5/Source/Guidelines/en/TitlePageVerso.xml +++ b/P5/Source/Guidelines/en/TitlePageVerso.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Guidelines/en/USE.xml b/P5/Source/Guidelines/en/USE.xml index f6fd2cb557..d49abb5a03 100644 --- a/P5/Source/Guidelines/en/USE.xml +++ b/P5/Source/Guidelines/en/USE.xml @@ -1,3 +1,4 @@ +
diff --git a/P5/Source/Guidelines/en/VE-Verse.xml b/P5/Source/Guidelines/en/VE-Verse.xml index 0e46ad5d72..62f662afa2 100644 --- a/P5/Source/Guidelines/en/VE-Verse.xml +++ b/P5/Source/Guidelines/en/VE-Verse.xml @@ -1,3 +1,4 @@ +
diff --git a/P5/Source/Guidelines/en/WD-NonStandardCharacters.xml b/P5/Source/Guidelines/en/WD-NonStandardCharacters.xml index 46d74b6d20..70be97f315 100644 --- a/P5/Source/Guidelines/en/WD-NonStandardCharacters.xml +++ b/P5/Source/Guidelines/en/WD-NonStandardCharacters.xml @@ -1,3 +1,4 @@ +
diff --git a/P5/Source/Guidelines/fr/BIB-Bibliography.xml b/P5/Source/Guidelines/fr/BIB-Bibliography.xml deleted file mode 120000 index 084ad41329..0000000000 --- a/P5/Source/Guidelines/fr/BIB-Bibliography.xml +++ /dev/null @@ -1 +0,0 @@ -../en/./BIB-Bibliography.xml \ No newline at end of file diff --git a/P5/Source/Guidelines/fr/BIB-Bibliography.xml b/P5/Source/Guidelines/fr/BIB-Bibliography.xml new file mode 100644 index 0000000000..d85642f5d5 --- /dev/null +++ b/P5/Source/Guidelines/fr/BIB-Bibliography.xml @@ -0,0 +1,6373 @@ + + + + + +
+ Bibliography +
+ Works Cited in Examples in these Guidelines + + + 阿城，《棋王》。 + Académie française, + Rectifications de l'orthographe - J.O. du 06-12-1990, En ligne, + consulté le 05-03-2010. + + Adams, Douglas. The Hitchhiker's Guide to the + Galaxy, New York: Pocket Books, 1979, + chapter 31. + Agence bibliographique de l'enseignement + supérieur, ABES:Site internet + par l'ABES,consulté le 05-03-2010. + 阿拉伯短劍，國史館：嚴家淦總統文物。 + Alighieri, Dante. Doglia mi + reca ne lo core ardire, Rime, XLIX. + Allinson, E.P. and B. Penrose. + Philadelphia 1681-1887 (1887), p. 138. + American National Standard for Bibliographic + References, ANSI Z39.29-1977, New York: American + National Standards Institute (1977). + + + + Andersson, Theodore M.. A Preface to the Nibelungenlied, + Stanford University Press (1987). + + Andrews, Mr.. Song, Chambers's + Edinburgh Journal Series 1 + 9:463 (12 + December 1840), 376. + + Anouilh, Jean, + Antigone, 1842. + + [As in Visions of] Single leaf of Notes for a poem about night "visions," + possibly related to the untitled 1855 poem that Whitman eventually titled "The Sleepers." + Fragments of an unidentified newspaper clipping about the Puget Sound area have been pasted + to the leaf. The Trent Collection of Walt Whitman Manuscripts, Duke University Rare Book, + Manuscript, and Special Collections Library. + + + Atkins et al. + Collins Robert French-English English-French Dictionary. + London: Collins (1978). + + Atkinson, J. Maxwell and John Heritage. Structures of social action: Studies in conversation analysis, + Cambridge and Paris: Cambridge + University Press, Editions de la Maison des Sciences de + l'Homme (1984), ix-xvi. + Austen, Jane. Pride and + Prejudice. (1813), chapter + 1. + + + + 白先勇，〈金大班的最後一夜〉，《台北人》。 + 白先勇，《孽子》。 + 白居易，《憶江南》。 + + Amheida I: Ostraka from Trimithis Volume 1: Texts from the 2004–2007 Seasons, + Bagnall, R. S. and G. R. Ruffini, with contributions by R. Cribiore and G. Vittmann + (2012). + + + Baker, James K.. Night in Tarras. In Hilltop: A Literary Paper, vol 1 no 2. Wellington: Victoria University College + Literary Society. (1949). + Balzac, Honoré de, + Les Chouans, 1845. + Balzac, Honoré de, + Le Père Goriot, 1843. + Balzac, Honoré de, Petites misères de la + vie conjugale, 1850. + Barbauld, Lucy Aikin. The Works of Anna + Laetitia Barbauld (1826). + + Barker, Jane. The Lining to the Patch-Work Screen + (1726). + + Base de datos paleográfica da lírica galego-portuguesa (PalMed). Versión 1.2. + Santiago de Compostela: Centro Ramón Piñeiro para a + Investigación en Humanidades. . + f. B126r, column a, l. 21-32. + + Bataille, Michel , + L'Arbre de Noël, 1967. + + Les Chats, in : Baudelaire, Charles, Les Fleurs du mal, 1861. + + La Vie antérieure, in : Baudelaire, Charles, + Les Fleurs du mal, 1861. + 電影《霸王別姬》，1993年。 + Beck, Béatrice, Léon + Morin, prêtre, 1952. + Beckett, Samuel. Waiting for + Godot, London: Faber and Faber + (1956). + Beckett, Samuel. Murphy + (1963), chap 2. + Becque, Henry, La + Parisienne. Edition + électronique par l'ATILF et le CNRTL, d'après + l'édition de Fasquelle (Paris, 1922). + + Bowers, Jack + Mixtepec-Mixtec Project Personography + + + + + Beerbohm, Max. Autograph manuscript of The Golden Drugget, + Pierpont Morgan MA 3391. in 123. + Behn, Aphra. The Rover, + (1697). + + Beeton, Isabella. The book of Household Management, + London: S.O. Beeton + (1861). + Belloc, Denis , + Képas, 1989. + + Belloc, Denis , Néons, 1987. + Bentham, Jeremy. The Book of + Fallacies. (1824). + + Beowulf and The fight at Finnsburg; edited, with introduction, bibliography, + notes, glossary, and appendices, by Fr. Klaeber. Boston, New York + [etc.] + D.C. Heath & Co. (1922). + + Bibliographie dans le cadre de la semaine italienne du 11 au 18 mars 2006, , + document électronique. + Bibliothèque nationale de + France, Projet de description des reliures remarquables de la Réserve des + livres rares selon le modèle de la TEI manuscrits. + Billetdoux, Marie, Un + peu de désir sinon je meurs, 2006. + + Blake, William. London, in Songs + of Experience (1791). + + Blake, William. The Sick Rose, in Songs of Experience (1794). + + Blake, William. The Tyger, in Songs of Experience (1794). + Bloomfield, Leonard. Literate and + Illiterate Speech, American Speech, 2, (1927), pp. + 432-441. + Borges, Jorge Luis, tr. R. + Simms. The Analytical Language of John Wilkins. In + Emir Rodriguez Monegal and Alistair Reid, eds. Borges: A reader, Dutton Adult + (1981), p.141. + Borges, Jorge Luis. Avatars of + the Tortoise In James E. Irby tr. Labyrinths: Selected Stories and Other Writings, New York: + New Directions, (1962), pp.202-203. + Bouillier, Grégoire, + Rapport sur moi, 2002. + Bresson, Robert, Mouchette : script, l'Avant-scène cinéma, + n° 80, avril 1968. + Extract from British National Corpus () Text KB7, sentence 13730. + + Brontë, Charlotte. Jane Eyre: An Autobiography, + Third edition; reprintLondon + Service & Paton, 1897; + Project Gutenberg, 1 December 2020. + chapter XII. + + + + Browning, Robert. Letter to George Moulton-Barrett, Pierpont + Morgan MA 310, ( 23). + Buirette de Belloy, Pierre Laurent, + Gabrielle de Vergy, 1777. + + Bunyan, John. The Pilgrim's Progress from this world to that which + is to come..., London (1678). + Burgess, Anthony. A Clockwork + Orange. (1962), opening. + Burnard, Lou. Principles of + Database Design in S. Rahtz. ed. Information + Technology in the Humanities: tools, techniques and applications, Ellis + Horwood Ltd, Ellis Horwood Series in Computers and Their + Applications, (1987), p. 54. + Burnard, Lou, + Sperberg-McQueen, C. M., + <ref target="http://www.gutenberg.eu.org/publications/autres/TEILITE/">La TEI simplifiée, + une introduction au codage des textes électroniques en vue de leur échange -- version de + travail </ref> + , 1996. + + Burton, Robert. Anatomy of Melancholy + (1621), 16th ed. reprinted 1846, p. 743. + Butler, Samuel. The Way of All + Flesh (1903), chapter 37. + Byron, George Gordon. Don Juan + (1819), I.xxii. + Byron, George Gordon. Vision of + Judgment In E.H. Coleridge ed. The Poetical + Works of Lord Byron, viii, 1922. + + + + C 60/16 Fine Roll 6 HENRY III (28 October 1221-27 + October 1222), membrane 5, entry 154. + CBETA + Cædmon's Hymn in Bede's Historia Ecclesiastica (MS Kk. + 5. 16, Cambridge, University Library). + + Cabaret. A musical play, with book by Joe Masteroff, lyrics by Fred Ebb, and + music by John Kaner. Based on the play by John van Druten and stories by Christopher + Isherwood. 1966 + Edward Barkley, describing how Essex drove the Irish from the + plains into the woods to freeze or famish in winter; quoted by Canny, Nicholas + P. + The Ideology of English Colonization: From Ireland to America. In + Stanley N. Katz and John M. Murrin eds. Colonial America: Essays in Politics and Social Development, 3d + ed + New York: Knopf, (1983), p.53. + + + Carroll, Lewis. Through the Looking Glass, and what Alice + found there. (1871). + Catéchisme de l'Eglise + catholique, 1968. + + Cavendish, Margaret. Nature's Pictures. + London, 1656. Women Writers Online. Women + Writers Project, Northeastern University. 29 Mar. + 2015. + Centre national de la recherche scientifique + (France). UMR 7118 ATILF, <ref target="http://atilf.atilf.fr/tlf.htm">Le + Trésor de la Langue Française Informatisé (TLFI)</ref>, + 2004. + Example recoded from Chafe, W. + Adequacy, user-friendliness, and practicality in transcribing In + Leech, G., G. Myers, J. Thomas eds. + Spoken English on Computer: Transcription, Markup and + Applications. Harlow: Longman, + 1995. + + Chandler, Lloyd. + Conversation with Death (also known as Oh, + Death). In Journal of Folklore Research, 41.2/3, (2004), pp. + 125-126. + Chapman, Graham, Cleese, John, + Gilliam, Terry, Idle, Eric, Jones, + Terry. The complete Monty Pythons Flying Circus. + Chapman, Graham, Cleese, John, + Gilliam, Terry, Idle, Eric, Jones, + Terry. Monty Python's Life of Brian (1979). + + + Chaucer, Geoffrey. Canterbury Tales, f52r, in Holkham MS. + + Chaucer, Geoffrey. The Tale of Sir Topas, The Canterbury Tales, In F. N. Robinson ed. The Works of Geoffrey Chaucer, 2nd edition + Boston: Houghton Mifflin Co., + 1957. + 陳政彥，〈戰後臺灣現代詩論戰史研究〉，2007。 + + Cholières, Nicolas de, La Forest Nuptiale + (1600). + + Chomsky, Noam and Morris Halle. The Sound Pattern + of English. New York: Harper & Row (1968), p. 415. + Claude Simon + Le jardin des plantes, 1997, p 284 + + Cleaver, Eldridge. Soul on Ice. New + York (1968). + + Cloud of Unknowing In Hodgson, Phyllis ed. The Cloud of Unknowing and The Book of Privy Counselling, + London: Oxford University Press, Early + English Text Society, 218, (1944). + Clover, Carol J.The Medieval + Saga, Ithaca: Cornell University Press + (1982). + + Cocteau, Jean. La Machine Infernale. + Coleridge, Samuel Taylor. The + Rime of the Ancient Mariner. In Wordsworth, William and + Samuel Taylor Coleridge. Lyrical Ballads + (1798). + Coleridge, Samuel Taylor. Frost at + Midnight In E.H. Coleridge ed. Poetical + Works, Oxford: Oxford University + Press, (1967), p.240. + Colette, Colette à + l'école, 1900. + + Collins English Dictionary, 12th edition + Glasgow: Collins + (2014). + + Collins Pocket Dictionary of the English language. + London: Collins. + + Collins, Wilkie. The Moonstone, + Penguin, 6th narrative. + + Comenius, John Amos. Orbis Pictus: a facsimile of the + first English edition of 1659 (ed. John + E. + Sadler + ) Oxford University Press (1968). + Cope, Thomas Pym. Philadelphia + merchant: the diary of Thomas P. Cope, 1800-1851, Eliza Cope + Harrison ed. + Corneille, Pierre, + La Place Royale ou L'Amoureux extravagant, 1637. + Corneille, Pierre, + Théodore, vierge et martyre : tragédie chrétienne, + 1646. + + Cowley, Hannah. The Runaway (1813). + + Crashaw, Richard, ed. J.R. Tutin. The + Poems of Richard Crashaw. Muses Library Edition: + (1900). + + Creeley, Robert + A counterpoint in For Love: Poems 1950-1960 + (1962). + 崔西．雪佛蘭。《戴珍珠耳環的少女》。台北：皇冠，2003。 + + + + Dallas, George Mifflin. Unpublished + letter cited in Russell F. Weigley, Nicholas B. + Wainwright, Edwin Wolf eds. Philadelphia: A 300 + Year History, New York and London: + W. W. Norton & Company, 1982, p. 349. + Danhauser, Adolphe-Leopold, + Théorie de la musique, 1872. + + Darwin, Charles. Narrative of the Surveying Voyages of His Majesty's + ships Adventure and Beagle... volume 3 : Journal and Remarks (The Voyage of the + Beagle), chap 3. 1839. + Daudet, Alphonse, Les + contes du lundi, 1873. + + Davenant, William. The vvitts. A comedie, presented at the + private house in Blacke Fryers, by his Majesties servants. The author VVilliam D'avenant, + servant to Her Majestie. + London, 1636. [STC S109311] + + De Nutrimento et Nutribili, Tractatus 1, fol 217r col b of Merton College + Oxford MS O.2.1; in pl. 16. + + Dean of Sarum Churchwardens' presentments, 1731, Hurst; Wiltshire Record + Office; transcribed by Donald A. Spaeth. + Defoe, Daniel. The Fortunes and + Misfortunes of the Famous Moll Flanders (1722). + Defoe, Daniel. Robinson + Crusoe (1719). + + Defoe, Daniel. Journal of the Plague Year. + London (1722). + + Dekker, Thomas and Thomas Middleton. The Honest + Whore, Part One (1604). + Deloney, Thomas. Thomas of Reading or the + Sixe Worthie Yeomen of the West (1612). + Dennery, Annie. Du mélos à la note : Les notations musicales au Moyen Age, Médiévales, n° 3 + 1983. + Dickens, Charles. A Christmas + Carol in Prose, Being a Ghost Story of Christmas, Chapman and + Hall, (1843), p. 5, p. + 12. + Dickens, Charles. Little + Dorrit, (1857). + Dickinson, Emily. 1755 In + Arthur Eastman et al. eds. The Norton Anthology of + Poetry, New York: W.W. Norton, + 1970, p.859. + Diderot, Denis, + Lettres à Sophie Volland, 26 sept. 1762. + 〈第三屆第一次大會第一次會議記錄〉，臺灣省諮議會。 + Disraeli, Benjamin. Coningsby (1844), preface. + Doyle, Arthur Conan. The + Red-headed league. In The Adventures of Sherlock Holmes + (1892). + + Doyle, Arthur Conan. The Original Illustrated Sherlock + Holmes, Castle Books, 1989. + Drawing of a leaden plaque bearing an inquiry by Hermon from the + oracular precinct at Dodona. Catalogue no 725; LSAG 230.13. Image from + Dubois, Jacques, Nyssen, + Hubert (dir. de collection), Babel, Actes + sud,1989-.... + Dubois, Jean, + Dictionnaire de linguistique, 1974. + + Dudo of St Quentin. De moribus et actis primorum Normannie + ducum, fol 4v of British Library MS Harley 3742; in pl + 6(i). + Dufournaud, Nicole, + Numérisation des Titres de famille, édition électronique, 2002. + Duhamel, Georges, + Chronique des Pasquier, 1933-1945. + + Dutt, Toru. Lakshman In Ancient + Ballads and Legends of Hindustan, Kegan Paul, Trench & + Co., (1882) + Dylan, Bob. All Along the + Watchtower In John Wesley Harding + (1967). + Dylan, Bob. Positively 4th + Street In Highway 61 Revisited + (1965). + + + + + Eddic poems, in Reykjavík, Landsbókasafn Íslands, Lbs 1562 4to. + Editorial, .EXE + magazine, 6.11 (1992), + p. 2. + Eliot, George. Middlemarch (1871), I.1. + + Eliot, George. Middlemarch (1871), + I.XXI. + + Eliot, George. Daniel Deronda (1876), + III.1. + Eliot, Thomas Stearns. The + waste land: a facsimile and transcript of the original drafts including the annotations of + Ezra Pound, Eliot, Valerie ed. Faber and Faber + Ltd. (1971), p. 37. + + Scalable Vector Graphics (SVG) 1.1 (Second Edition). Editors + Erik Dahlström, Jon Ferraiolo, 藤沢 淳, Anthony Grasso, Dean + Jackson, Chris Lilley, Cameron McCormack + Doug Schepers, Jonathan Watt and Patrick + Dengler. World Wide Web Consortium (W3C) (22 June + 2010). Available from . + Ernaux, Annie, Se + perdre, 1988. + Ernaux, Annie, L'usage + de la photo, 2005. + + + <ref target="http://www.etudes-litteraires.com/figures-de-style/deictique.php">Études + littéraires</ref> + , consulté le 07-05-2010. + + + + Fallet , René, Le + Triporteur, 1951. + Field, Syd + Screenplay: the Foundations of Screenwriting (1998). + Fielding, Henry. The History of + the Adventures of Joseph Andrews and his Friend, Mr. Abraham Abrams + (1742). + + Fielding, Henry. Tragedy of Tragedies, + (1737). + + Fish, Stanley. Is there a text in this class? The authority of + interpretive communities. Harvard University Press + (1980). + Fisher, M. F. K. I Was Really Very + Hungry In As They Were, Knopf + (1982), p. 43. + + + FitzGerald, Edward. The Rubáiyát of Omar Khayyám, translated into + English Verse (1859), stanza 25. + Flaubert, Gustave, + Salammbô, 1862. + Flaubert, Gustave, + La Tentation de saint Antoine, 1874. + Foley James D., Andries van Dam, + Steven K. Feiner and John F. Hughes. Computer Graphics: Principles and Practice, 2nd edition + Reading: Addison-Wesley, p.259. + Forster, E.M., Howards + End. Edward Arnold. (1910). + + + <ref target="http://sites.radiofrance.fr/franceinter/em/labassijysuis">France inter, + Là-bas si j'y suis</ref> + , consulté le 07-05-2010. + + + <ref target="http://sites.radiofrance.fr/franceinter/em/letelephonesonne/contact.php" + >France inter, Le téléphone sonne</ref> + , consulté le 07-05-2010. + + + <ref target="http://franglais.ini.hu/">Franglais et franricain</ref> + , consulté le 07-05-2010. + Fry, Christopher, The firstborn + (1948). + 福春嫁女 + + Fussell, Paul. The Norton Book of Travel. W. W. + Norton (1987). + + + + Galilei, Galileo, Sidereus + Nuncius, Venetiis: Apud Thomam + Baglionum, 1610, quoted by Tufte, Edward R., + Envisioning Information, Cheshire: + Graphics Press (1990), p. + 97. + Galland, Antoine, Les + Mille et une nuits, 1704. + Galsworthy, John, Strife. In + Plays, vol 1. (1909). + Gaskell, Elizabeth Cleghorn. The Grey Woman, MS. + Gavioli, Laura and Gillian + Mansfield. The PIXI corpora: bookshop encounters in English and + Italian, Bologna: Cooperativa Libraria + Universitaria Editrice (1990), p.74. + Gay, John. The Beggar's Opera + (1728). + Gazdar, Gerald and Mellish, + Christopher. Natural language processing in Prolog. + Addison-Wesley (1989), p.5. + + Gazdar, Gerald, Ewan Klein, Geoffrey Pullum, and Ivan Sag: + Generalized Phrase Structure Grammar, Harvard + University Press (1985). + + Gershwin, Ira + By Strauss (from An American in Paris, 1953). + Gianfraco Contini, Poeti del + Duecento, Milano-Napoli:Ricciardi I, (1960). pp 155-64. + Gibbon, Edward, The History of the + Decline and Fall of the Roman Empire, (1789), chapter 58. + Gide, André, Le + Journal des Faux-Monnayeurs, 1927. + Gide, André, Journal : + 1889-1939, 1939. + + Gilbert, William Schwenck and Sullivan, Arthur. HMS Pinafore (1878), I. + Gilbert, William Schwenck and Sullivan, + Arthur. The Mikado (1885). + Ginsberg, Allen. My alba, + Reality Sandwiches, San Francisco: + City Lights, (1963). + Giono, Jean, + Regain, 1930. + Giraudoux, Jean, La + guerre de Troie n'aura pas lieu, 1935. + + Godefroy, Frédéric, Dictionnaire de l'ancienne langue française et + de tous ses dialectes du IXe au XVe siècle, 1881. + Goethe, Johann Wolfgang von, tr. Philip Wayne. Faust, Part + 1, London: Penguin. (1949). + + Goethe, Johann Wolfgang von. Auf dem See + (1775). + + [Goldsmith, Oliver], The History of Little GOODY TWO-SHOES; + Otherwise called, Mrs. MARGERY TWO-SHOES... (Printed for J. Newbery, + 1766). + + Grallert, Till, Tools for the Computational Normalisation and + Analysis of Food Prices and Food Riots in the Eastern Mediterranean (Bilād al-Shām) in the + 19th and 20th Centuries. Zenodo, 2021. . + + Graves, Robert. Rough draft of letter to Desmond Flower. + 17 Dec 1938. (from Diary of Robert Graves 1935-39 and + ancillary materials, compiled by Beryl Graves, C.G. Petter, L.R. Roberts, + University of Victoria Libraries). + + Greene, Robert. Groatsworth of Wit Bought with a Million + of Repentance (1592). + + Gregory of Tours. Ecclesiastical History of the + Franks (translated by Lewis Thorpe). + Greimas, Algirdas Julien + et Courtés, Joseph, Sémiotique : dictionnaire raisonné de la théorie + du langage, 1979. + Grune, Dick and Ceriel J. H. + Jacobs. Parsing Techniques: A Practical Guide, + New York and London: Ellis + Horwood, 1990, p. 24. + + Guerard, Françoise. Le Dictionnaire de Notre Temps, ed. + Paris: Hachette, 1990 + + + + + Hall, Radclyffe. The well of + loneliness. (1928). + Halliday, M.A.K. and R. + Hassan. Language, Context and Text: Aspects of Language in a + Social-Semiotic Perspective, Oxford: Oxford + University Press, 1990, p. + 104. + Hanks, Patrick. Definitions and + Explanations. In J. M. Sinclair ed. Looking Up. + Collins, 1987, p. 121 + . + Hannam's last farewell to the world:: being a full and true + relation of the notorious life and shamfull death of Mr. Richard Hannam... + (1656). + + Hansberry, Lorraine. A raisin in the sun. + (1959). + Harvey, Gabriel. Four letters and certain + sonnets specially touching Robert Greene... (1592). + Harvey, William. Exercitatio Anatomica De Motu Cordis Et Sanguinis In Animalibus, 1949 (Third edition, second printing), p. 74. + Hobbes, Thomas. Leviathan + (1681). + 《紅樓夢》第六回：賈寶玉初試云雨情 劉姥姥一進榮國府 + 〈紅頭嶼踏查報告〉，國立台灣大學圖書館：田代文庫。 + Hoola Van Nooten, + BertheFleurs, fruits et feuillages choisis de l'île de Java peints d'après + nature, troisième édition par C. Muquardt, Bruxelles, + 1880. + + Hornby, A.S. et al. Oxford Advanced Learner's Dictionary of Current + English. Oxford University Press (1974). + 黃晨淳編著，《希臘羅馬神話故事》，p76。 + Hugo, Victor, + Notre-Dame de Paris, 1845. + + Souvenir de la nuit du 4, in : Hugo, Victor, + Les Contemplations, 1853. + Hugo, Victor, Les + Misérables, 1862. + + A la fenêtre pendant la nuit, in : Hugo, Victor , + Les Contemplations, 1856. + Huizinga, Johan, + L'Automne du Moyen-Âge, 1919. + + + + ISO 690:1987: Information and documentation – + Bibliographic references – Content, form and structure + clause 4.1, p.2. + ISO 24611:2012 Language resource management — Morpho-syntactic annotation framework (MAF). + International Organization for Standardization. 2012. + + Ibsen, Henrik, tr. William and Charles Archer. + Peer Gynt (1875). + + Ibsen, Henrik + Den episke Brand KBK Collin 2869, 4º I, fol. 11v. + + Ibsen, Henrik + Digte NBO Ms.4º 1110a, p. 36. + + Ibsen, Henrik + Brand, The Royal Library, Denmark. KBK Collin 262, 4°, I.1.1, fol. + [4]v + Ibsen, Henrik, tr. R. + Farquharson Sharp and Eleanor Marx-Aveling. + A Doll's House In A Doll's House; and Two Other + Plays by Henrik Ibsen, Everyman's library: the drama 494 + , London: J. M. Dent & Sons, + 1910. + Idle, Eric, Michael Palin, + Graham Chapman, John Cleese, Terry + Gilliam. The Complete Monty Python's Flying Circus: All the + Words, Pantheon Books, (1989), 2, p.230. + Imbs, Paul, Martin, + Robert, Straka, Georges, Mélanges de linguistique + française et de philologie et littérature médiévales offerts à Monsieur Paul + Imbs, 1973 . + Institut de Littérature Française Moderne de + l’Université de Neuchâtel, Présentation du projet Cyrus, En ligne, consulté le + 05-03-2010. + Ionesco, Eugène, La + cantatrice chauve, 1950. + 羅貫中，《三國演義》。 + + + + + Jakacki, Diane. Schema question: further constraining + @subtype based on @type. January 18, + 2021. TEI (Text Encoding Initiative) public discussion + list, . + Jarry, Alfred, tr. Simon Watson + Taylor and Cyril Connolly. The Ubu + plays, London: Methuen, + 1968. + Jean-Jacques Rousseau + Les confessions vol 6 + Jerome, Jerome K. + Three men in a boat (1889), chapter 6. + Joachim Heinrich + CampeWörterbuch der Deutschen Sprache. Erster Theil. A - bis - E., + 1807. + John, Lord Sheffield, The + Auto-biography of Edward Gibbon esq., (1846), 222. + Jonson, Ben. Bartholomew + Fair. + Jonson, Ben. Volpone, + J. B. Bamborough ed. Macmillan, 1963, + p.14. + Jonson, Ben. The Alchemist + , Douglas Brown ed. London: + Benn, 1966, I.1, + p.9. + Joyce, James. Ulysses: + The Bodley Head, 1960. p. + 933. + + Judith Patt, Michiko Warkentyne and Barry + Till. Haiku: Japanese Art and Poetry. 2010. + Pomegranate Communications, Inc. San Francisco. . + + + + + Karlstadt, Andreas + Bodenstein. Distinctiones Thomistarum. + Wittenberg + 1507. In Harald Bollbuck ed. Kritische Gesamtausgabe + Karlstadt + I, available: + + Kersey, John. Dictionarium + Anglo-Brittannicum: Or, a General English Dictionary. London: + J. Wilde, 1715. 2nd ed. + Kilian, Wilfrid, <ref + target="http://jubil.upmc.fr/sdx/pl/toc.xsp?id=GH_000484_001&fmt=upmc&idtoc=GH_000484_001-pleadetoc&base=fa" + >Neige et glaciers ; notes prises au cours de géologie de la Faculté des Sciences de + Grenoble par M. Alamelle</ref>, 1891-1895. + King, Martin Luther. Letter from Birmingham City + Jail. Philadelphia, PA: American Friends Service + Committee (1963). + Kipling, Rudyard. The mother + hive. In Actions and Reactions, + London: Macmillan, (1909). + + Kipling, Rudyard. Stalky & Co., + London: Macmillan (1899). + Kipling, Rudyard. Kim, + Macmillan, (1901), p. + 9. + Knuth, Donald Ervin. The Potrzebie + System of Weights and Measures, Mad Magazine33June 1957. + Koltès, + Bernard-Marie, Quai ouest, 1985. + Krummrey, Hans, Panciera, Silvio + Criteri di edizione e segni diacritici, Tituli 2 (1980), + 205-215. + Kyd, Thomas. Spanish Tragedy + (1592). + + + + La Fayette, Marie-Madeleine Pioche + de La Vergne, comtesse de, La Princesse de Clèves, + 1678. + La Fontaine, Jean de. L'Astrologue + qui se laisse tomber dans un puits In Fables Choisies, + Classiques Larousse, Paris: Librairie + Larousse, 1, 1940. + La Fontaine, Jean de. Le corbeau + et le renard In Fables Choisies, Classiques + Larousse, Paris: Librairie Larousse, + 1, 1940. + Laboratoire ATILF + + <ref target="http://www.atilf.fr/">Analyse et traitement informatique de la langue + française (ATILF)</ref> + , consulté le 07-05-2010. + + Laclos, Pierre Choderlos de. Les Liaisons + dangereuses (1772), 1963, p. + 13. + Ladurie, Emmanuel Le Roy. Montaillou, Middlesex: Penguin Books, + 1980, p. 3. + Lamartine, Alphonse de, + Méditations poétiques, 1820. + Lamothe, Alexandre + de + Principaux manuscrits latins et français conservés dans la Bibliothèque + impériale et dans celle de l'Ermitage à Saint-Pétersbourg, édition numérique, Bibliothèque de l'école nationale des + chartes, 1864. + Langendoen, D. Terence and Paul M. + Postal. Vastness of Natural Languages, + Oxford: Basil Blackwell, 1984, p. + 24, note 12. + Langendoen, D. Terence and Paul Postal. The + vastness of natural languages, Blackwell, , 1, 1984. + + Langland, William. The Vision of Piers Plowman. In + A.V.C. Schmidt ed. Langland: Vision of Piers Plowman: + "B" Text, opening. + Latin liturgical manuscript: Bod MS. Lat liturg. b. + 19, folio 4r. Taken from the digitized image described at . + Lavrentev, Alexei, + <ref target="http://ccfm.ens-lsh.fr/IMG/pdf/BFM-Mss_Encodage-XML.pdf">Manuel + d’encodage XML-TEI étendu des transcriptions de manuscrits dans le projet + BFM-Manuscrits</ref>, dernier enregistrement le 26 juin + 2008. + + Lawrence, David Herbert. Autograph manuscript of Eloi, Eloi, lama + sabachthani, Pierpont Morgan MA 1892; in p.129. + + Layamon. Brut, fol 65v of Bodleian MS. Rawlinson Poetry 32; + in 12(ii). + Le Grand Robert de la langue + française, 2004. + LeTourneau, Mark S. + English Grammar, 2001, New York: + Harcourt + p. 89. + + Leech, G., G. Myers, J. Thomas eds. + Spoken English on Computer: Transcription, Markup and + Applications. Harlow: Longman, + 1995. + Leech, Geoffrey and Mick Short. + Style in Fiction, London: + Longman, 1981, p.272. + + Lennon, John and McCartney, Paul. She + Loves You. The Beatles Anthology 1. + Capitol, 1995. + Léry, Jean de, Histoire faict + en la terre de Brésil, 1580. + + Lessing, Doris. Martha Quest. 1952, + pp. 52-53. + Letter of Mikołaj Orlik to Mikołaj Serafin, Gródek, January 13 + [1438]. Edited by Skolimowska et al. Available from + Lewis, Leopold Davis. The + Bells, (1871), translated from Erckmann-Chatrian, + Le Juif Polonais. + + Lewis, Wyndham. Tarr (1928), + Jupiter, 1968, p. 17. + 李白，《黃鶴樓送孟浩然之廣陵》。 + 李白，《靜夜思》。 + 《梁山伯與祝英台》 + 電影《梁山伯與祝英台》，舊版。 + 〈歷代漢文大藏經概述〉，李圓淨，原載《南行》第六期（南行學社編印）。 + Lillo, George. The London + Merchant (1731), epilogue. + 林覺民，《與妻訣別書》。 + Lincoln, Abraham. Second Inaugural + Address, 4 March 1865. In H. S. Commager, ed., + Documents of American History, 5th ed + Crofts American history series. New York: + Appleton-Century-Crofts, 1949, p.442. + 劉康，《對話的喧囂：巴赫汀文化理論評述》，台北：麥田，2005，二版。 + 劉康，《對話的喧聲：巴赫汀文化理論述評》，台北：麥田，2005，頁20-23。 + + Longman Dictionary of Contemporary English. Harlow, + Essex: Longman (1978). + Lorris, Guillaume de et + Meun, Jean deLe Roman de la Rose, 1230, + 1270-1285. + Lowe, David. Lost + Chicago, Boston: Houghton Mifflin, + (1978), p.30. + + Lowell, Amy. Autumn + haze.(1919). + Lucie Lichtig, M. + Klein de Joseph Losey : script, . l'Avant-scène cinéma, + n° 175, nov. 1976. + Luther, Martin [tr]. Die gantze + Heilige Schrifft Deudsch, Wittenberg 1545. Letzte zu Luthers Lebzeiten erchienene Ausgabe, + hsg. Hans Volz unter Mitarbeit von Heinz Blanke. Textredaktion Friedrich Kur, + München: Rogner & Bernhard, + 1972. + 《論語》卷七：憲問第十四。 + 羅貫中，《三國演義》。 + 魯迅，《狂人日記 》。 + 魯迅，《狂人日記》。 + 魯迅，《狂人日記》。 + + + + MacNeice, Louis. The Sunlight on + the Garden In E.R. Dodds, + The collected poems of Louis MacNeice, London: + Faber, 1966. + Examples from MacWhinney, Brian, 88, 87, cited by Johansson, S. + The approach of the Text Encoding Initiative to the encoding of spoken + discourse In Leech, G., G. Myers, J. + Thomas eds. Spoken English on Computer: Transcription, Markup + and Applications. Harlow: Longman, + 1995. + + Madan, Falconer, et al, A summary catalogue of western manuscripts + in the Bodleian Library at Oxford which have not hitherto been catalogued ... + Oxford, 1895-1953. 5: 515. + Cited in Driscoll, M.J. P5-MS: A general purpose tagset for + manuscript description in Digital Medievalist: + 2.1, (2006) + + Maingeneau, Dominique, + Analyser les textes de communication, 2007. + Any issue of the Malawi Daily Times. + + Malle, Louis, Zazie + dans le métro : script, l'Avant-scène cinéma, n° + 104, juin 1970. + + Manuélian, Hélène, Schang, Emmanuel, XML, DTD et + TEI pour un dictionnaire étymologique des créoles, édition électronique, + 12 Octobre 2007. + + The Manere of Good Lyuynge: fol. 126v of Bodleian MS Laud Misc 517; + in , p.8. + Marbury v. Madison, 1 Cranch, + 137 (1803), rpt. In H. S. Commager, ed., Documents of American History, 5th ed + Crofts American history series. New York: + Appleton-Century-Crofts, 1949, + p.192. + Marvell, Andrew. An Horatian + Ode, Bod. MS Eng. Poet d.49. + Mauriac, Claude, + La Marquise sortit à cinq heures, 1961. + Mauss, Marcel, + Sociologie et anthropologie, 1950. + McCarthy, Niall, No + Parachute: The Highest Falls People Survived, Statista, + November 18, 2020. . + McCarty, Willard. Introduction in Collaborative Research in the Digital + Humanities: A volume in honour of Harold Short on the occasion of his 65th + birthday, September 2010, ed. Marilyn Deegan and Willard + McCarty. London: Ashgate + (2012). + Melville, Herman, Moby + Dick. (1851). + Mendès-France, Pierre, + Œuvres complètes, 1984-1985. + 《孟子》〈三十三〉。 + + Miller, Henry. Death of a Salesman in + Atkinson, Brooks, + New Voices in the American Theatre, New York: + Modern Library, 1955, p.113. + + Milne, A. A. + The House at Pooh Corner. London: + Methuen & Co., 1928, p. + 83. + + Milton, John. Paradise Lost: A poem in X books + (1667), I, 1-10. + Milton, John. Poems of Mr John Milton, both + English and Latin... (1645). + Molière, L'École des + femmes, 1663. + Molière, Le Médecin + malgré lui, 1667. + Molière, Le Médecin + volant, 1673. + Montaigne, Michel de, + Essais, 1592. + Montesquieu, Charles-Louis de Secondat, + baron de la Brède et de, Lettres persanes, + 1721. + Montherlant, Henry de , + Pitié pour les femmes, 1936. + + Moore, George. Autograph manuscript of Memoirs of my dead + life, Pierpont Morgan MA 3421; in + + Moore, Thomas. Autograph manuscript of the second version of Lalla + Rookh, Pierpont Morgan MA 310; in 23. + + Moreland, Floyd L. and Rita M. Fleischer. Latin: An + Intensive Course, (1977) p.53. + + Des Minnesangs Frühling, Moser, Hugo, Helmut + Tervooren eds. 36., neugestaltete und erweiterte Auflage + I Texte, Stuttgart: S. + Hirzel Verlag, 1977. + Mošin, Vladimir A. Anchor Watermarks. + Amsterdam: Paper Publications Society (Labarre Foundation), 1973. + Monumenta Chartæ Papyraceæ Historiam Illustrantia; v. 13. + Mréjen, Valérie, Eau + sauvage, 2004. + + Zuigan calls himself "Master". Mumon Ekai. (In + The Gateless Gate, Case 12.) + Mustafa Siddik Altinakar, + René Walther (éds.), Hydraulique fluviale. Tome 16, Écoulement et + phénomènes de transport dans les canaux à géométrie simple , + 2008. + Mégnin, Michel (éd.), Tunis + 1900 Lehnert & Landrock photographes,2005. + + Nabokov, Vladimir + Pnin (1953) , p.14 + + + The New Penguin English Dictionary. London: + Penguin Books (1986). + + Derived from + New Zealand Parliament, Legislative Council. Nga Korero Paramete: 1881-1885 + (New Zealand Electronic Text Collection). 2008 + Wellington, New Zealand. + . + + + Njal's saga. tr. Magnus Magnusson and Hermann + Palsson. Penguin. (1960), chapter + 12, p.60. + + O'Casey, Sean. Time to go (1951). + Ollagnier, Jeanne, + Main, 2008. + Herodotus. On Libya, from the + Histories. + + [Letter of Capt. E. Hopkins. Providence, 10 Sep 1764] + + "[I am a curse]" in Original Manuscript Drafts for the Song of + Myself, Collection MSS3829, part of the Papers of Walt Whitman, Clifton Waller + Barrett Library of American Literature, Albert and Shirley Small Special Collections + Library, University of Virginia. + Ormesson, Jean d', La Douane de mer, 1993. + + Orwell, George. Nineteen-Eighty-Four. + London: Gollancz (1949). + + 大隅亜希子. 1996. 律令制下における権衡普及の実態: + 海産物の貢納単位を中心として. 史論 + 49. pp. 22–44. . + + Owen, Wilfred. Dulce et decorum est, from autograph + manuscript in the English Faculty Library, Oxford University. + + Owenson, Sydney. The Wild Irish Girl. Ed. + Kathryn Kirkpatrick. Oxford: Oxford + University Press, 1999, p. 17. + + + + 擺夷文經，中央研究院歷史語言研究所 。 + Pascal, Blaise, Le Mémorial, in Pensées,1670. + + Payne, J. + Report on the compatibility of J P French's spoken corpus transcription + conventions with the TEI guidelines for transcription of spoken texts, Working Paper, Dec 1992, NERC WP8/WP4 122. + + Peacock, Thomas Love. Gryll Grange + (1861), chapter 1. + Pennac, Daniel , + La Petite marchande de prose, 1978. + Perec, Georges, Espèces + d'espaces, 1974. + Perec, Georges, La Vie + mode d'emploi : romans, 1978. + Perec, Georges , Les + Choses, 1965. + Partial family tree for Bertrand Russell + based on an example in Pereira, Fernando C.N. and Stuart M. + Shieber, Prolog and Natural Language Analysis, + Stanford: Center for the Study of Language and + Information. (1987), p.22. + Pernoud, Régine, La + Femme au temps des Cathédrales, 1982. + Perreault, Simon, vCard Format Specification + Internet Engineering Task Force (IETF) (2011). + . + + Petit Larousse en Couleurs. Paris: + Larousse, (1990). + + Philipott, Thomas + Poems. (1646). + + Pinsky, Robert. Essays on Psychiatrists in Sadness and Happiness (1975). + Pix, Mary. The False Friend + (1699). + Plautus, Titus Macchius. Asinaria, or the + Comedy of Asses. Edited and translated by Wolfgang de Melo. Loeb + Classical Library 60. Cambridge, MA: Harvard University + Press (2011). + Plautus, Titus Macchius. Menaechmi. + Polac, Michel, Un + fils unique : script, l'Avant-scène cinéma, n° + 99, janvier. 1970. + + Pope, Alexander. The Rape of the Lock + (1714) III.7. + Pope, Alexander. An Essay on + Criticism (1711). + Pope, Alexander. Dunciad Variorum + (1729), III.284. + From letter 'JK' found in Poulson's Daily + Advertiser, + 8 Oct 1835. + Proust, Marcel, A la + recherche du temps perdu : Du côté de chez Swann, 1913. + Queneau, Raymond. Exercices de + style. Paris: Gallimard, + (1947), p. 192. + + + + 瓊瑤，《還珠格格》。 + Queneau, Raymond , + Journaux, 1914-1965. + + + + Rabelais, François. + Gargantua Lyon, 1542 + Rabelais, François + Tiers livre des faictz et dictz Heroïques du noble Pantagruel... + (1546), adapted from the website at + Renard, Jules, + Journal : 1887-1910, 1910. + Reference from the bibliography in Reps, Thomas + William and Teitelbaum, Tim eds. The + Synthesizer Generator: A system for constructing language-based editors, + New York and Berlin: + Springer-Verlag, 1989, p.304. + 日本法隆寺貝葉心經 (Wikipedia Sept 2008). + Richardson, Samuel. Clarissa; + or the History of a Young Lady (1748), 2 Letter XIV. + + Robert, Paul. Le Petit Robert. Paris: + Dictionnaires Le Robert (1967). + Rohmer, Eric, Ma nuit chez Maud : script, l'Avant-scène cinéma, + n°98, 2001. + Romains, Jules, + Knock, 1923. + Rostand, Edmond, Cyrano de + Bergerac, 1898. + Roubaud, Jacques, La + Boucle, 1993. + Rowling, J. K. + The Sorting Hat. In Harry Potter and the + Sorcerer's Stone, New York: Scholastic, Inc. (1999), chapter + 7, p. 121. + + + + + The Saga of the Volsungs: the Norse epic of Sigurd the Dragon + Slayer. trans. Jesse L. Byock. University of + California Press (1990). + Le Sanctoral du lectionnaire de + l'office dominicain (ms. Rome, Sainte-Sabine XIV L 1, f.142r et 189r-230v, Ecclesiasticum + officium secundum ordinem fratrum praedicatorum), édition électronique par + l'Ecole nationale des chartes, d'après l'édition d'Anne-Élisabeth + Urfels-Capot (Paris : Ecole nationale des chartes, 2007). + + 崎山理. 1985 + インドネシア語. 講座日本語学 + 11. 外国語との対照II. + 東京:明治書院 + 61-80 + + 三毛，〈沙漠中的飯店〉，《撒哈拉的故事》。 + 《三家詩鈔》，華培昌，藏於國家圖書館。 + Sapir, Edward. Language: an + introduction to the study of speech, New York: + Harcourt, Brace and World, 1921, p.79. + Shakespeare William, + Richard III, 1597. + Shakespeare, William. Henry V + In Mr. William Shakespeares Comedies, Histories, & Tragedies, + London: Jaggard and Blount, + 1623. + Shakespeare, William. Henry V + In The Works of Shakespeare in seven volumes, ed. Lewis + Theobald, London: Bettesworth, Hitch, Tonson et + al, (1733). + Shakespeare, William. Antony and + Cleopatra, IV.4, 14-21. + Shakespeare, William. Merchant of + Venice, I.ii, speech 5 (Portia). + Shakespeare, William. Macbeth, Act V, Scene 1. + Shakespeare, William. Antony + and Cleopatra (1623), V. + ii. + Shakespeare, William. Hamlet In Stanley Wells and Gary Taylor eds. + The Complete Works, Oxford: Clarendon + Press, 1986, I.i. + Shakespeare, William. Hamlet, London: Valentine Simmes. + (1603), I.i. + Shakespeare, William. The Tempest + In Mr. William Shakespeares Comedies, Histories, & + Tragedies, London: Jaggard and Blount, + (1623). + Shakespeare, William. Twelfth Night, or + What you Will In Mr. William Shakespeares Comedies, Histories, + & Tragedies, London: Jaggard and + Blount, (1623). + Shakespeare, William, The + Sonnets (1609), 18. + Shakespeare, William, The + Sonnets (1609), 130. + 莎士比亞，《終成眷屬 》。 + 莎士比亞，《馬克白》。 + Sharing Ancient Wisdoms, 2013, + available: . + Shaw, George Bernard. Heartbreak + House: a fantasia in the Russian manner on English themes (1919). + Shaw, George Bernard. Pygmalion, 1913. + Shields, David. Dead + Languages, HarperCollins Canada/Perennial + Rack, rpt. 1990, p.10. + Sinclair, John ed. Collins + COBUILD English Language Dictionary. London and + Glasgow: Collins, (1987), + p. 337 s.v. croissant. + 京劇《四郎探母》，1947年梅蘭芳演出。 + Smith, Adam. An Inquiry into the + Nature and Causes of the Wealth of Nations, London. + (1776), index to vol. 1. + + Smith, Sydney. Autograph letter. In Pierpont Morgan library; + 11. + + Smith, William. A New Classical Dictionary of Greek and + Roman Biography, Mythology, and Geography, Partly Based Upon the Dictionary of Greek and + Roman Biography and Mythology, New York: Harper + & Brothers, Publishers, 1860, 1026. + + Southey, Robert. Autograph manuscript of The Life of Cowper. + In Pierpont Morgan MA 412 ( 15). + Soyinka, Akinwande Oluwole Wole. Madmen and Specialists, London: + Methuen (1971). + + Spenser, Edmund. The Faerie Queene: Disposed into twelue + bookes, Fashioning XII. Morall vertues. (1596). + + Sterne, Laurence. The Life and Opinions of Tristram + Shandy, Gentleman. (1760). + + Stow, John A survey of the cities of London and Westminster: + containing the original, antiquity, increase, modern estate and government of those + cities. Written at first in the year MDXCVIII. By John Stow, citizen and native of London. + ... Now lastly, corrected, improved, and very much enlarged: ... by John Strype, ... In + six books. ... (London c.1525 - London 1605). + Sudetic, Chuck Serbs Tighten Grip On Eastern + Bosnia. New York Times, + April 20, 1992. + + SUEtheTrex, Twitter biography. . Accessed March 25th, + 2020. + Sutherland, L.S. and L.G. + Mitchell eds. The Eighteenth century, The + History of the University of Oxford V + , p.178. + 蘇童，《妻妾成群》。 + 蘇軾，《定風波》。 + + Swift, Jonathan. Travels into Several Remote Nations of + the World, in Four Parts. By Lemuel Gulliver... (1735). + Swift, Jonathan. Law is a bottomless pit, or + the history of John Bull (1712). + + Swinburne, Algernon Charles. Poems and Ballads (First + Series). London: Chatto & Windus. + (1904). + Swinnerton, Frank Arthur. The + Georgian Literary Scene 1910-1935, 1938, London: + J. M. Dent, p. 195. + + + + + 台灣，《結婚入盟誓》，1997年5月。 + 台灣區三碼與三加二碼郵遞區號 + 《台灣叢書》，伊能嘉矩著，藏於國立台灣大學圖書館。(http://catalog.ndap.org.tw/?URN=2155366 (Aug 2008)). + 唐．白居易．琵琶行 + + Taylor, John + The Cold Tearme or, The Frozen age, Or, The Metamorphosis of the Riuer of + Thames. London, 1621. [STC (2nd ed.) 23910]. + + TEI Consortium + Call for Papers - TEI 2022 Newcastle, 2022. + + The Castle of the Fly, in Russian Fairy Tales, + translated by Norbert Guterman from the collections of Aleksandr Afanas'ev, illustrations by + Alexander Alexeieff, folkloristic commentary by Roman Jakobson (New York: Pantheon Books, + 1947, rpt. [n.d.]), p. 25. + The Daily Telegraph, 21 Dec + 1992. + The Guardian, + 26 Oct 1992, p. 2 + The Guardian, + 21 Dec 1992, p. 2. + The Holy Bible, conteyning the Old Testament and the new... + appointed to be read in Churches. (1611), Genesis + 1:1. + The Independent, + 26 Oct 1775, headline. + Thurber, James. The 13 + Clocks (1950). + Tolkien, J. R. R. + The Monsters and the Critics. London: + George Allen & Unwin (1983). + + Townsend, Sue. The growing pains of Adrian Mole + (1984), p.43. + + Trollope, Anthony. An Autobiography + (1883). + + Trollope, Anthony. North America + (1862). + Truffaut, François et + Gruault, Jean, Les deux Anglaises et le continent : + script, l'Avant-scène cinéma, n° 121, + nov. 1971. + Tufte, Edward R., Envisioning + Information, Cheshire: Graphics Press. + (1990). + + + Ukraine Relief Fund + UBS + . + + United States Code Title 17, Section 107, found at . + + United States District Court for the Middle District of Pennsylvania. + Kitzmiller v. Dover Area School District et al.: 2005. + 04cv2688, p. 33. Available from and transcribed at . + + + + Valéry, Paul, Monsieur + Teste, 1929. + + Vergil (Publius Vergilius Naso). Aeneid, + I.1. + Verne, Jules, Cinq + semaines en ballon, 1863. + Verne, Jules, La + Chasse au météore, 1908. + Verne, Jules, Vingt + mille lieues sous les mers, 1870. + + Vinge, Vernor + Across realtime + ch 10 (1986). + Viton de Saint-Allais, Nicolas + , Dictionnaire encyclopédique de la noblesse de France, + 1816. + + Vóluspá recto of folio 5 of the unique manuscript of the Elder Edda. Codex + Regius, ed. L. F. A. Wimmer and F. Jónsson (Copenhagen 1891). + + + + + Wanklyn, M.D.G. et al. Gloucester Port Books, 1575-1765. + Available from . + + Wanton, Joseph. Unpublished letter to Nicholas Brown and Co, + 1761 + Brown University Steering Committee on Slavery and Justice: Repository of + Historical Documents. (). + + Warriner, John E. + English Composition and Grammar (1988), p.280. + + Webster's Seventh Collegiate Dictionary. Springfield, Mass. + G. & C. Merriam Co. (1975). + 魏飴，《小說鑑賞入門》，台北：萬卷樓，1999。 + Weil, Simone, Lettres à Antonio Atarès, in Oeuvres + complètes1988-. + + Williams, Nigel. The Wimbledon Poisoner + (1990), p. 204. + Winock, Michel, + Jeanne et les siens : récit, 2003. + + Wölfflin, Heinrich, trans. Hottinger, Marie + Donald Mackie (1932). Principles of art history: the problem + of the development of style in later art.. Originally published as Kunstgeschichtliche Grundbegriffe (1915). + + Woolf, Virginia. Mrs Dalloway (1925), + p.64, p.65. + + Wordsworth, William. Scorn not the sonnet in + Poetical Works (1827). + + Wordsworth, William. The Prelude (1850). + + Wrenn C. L. ed. Beowulf: with the Finnesburg + fragment, London: Harrap + (1953). + + 吳承恩，《西遊記》。 + + + Wycherley, William. The Country Wife + (1675). + + + 夏宇，〈甜蜜的復仇〉，《備忘錄》。 + 蕭紅，《呼蘭河傳》。 + + + + 幼莘貢俚賀曉濤之新婚賀詞 + 余秋雨 + 元曲。馬致遠，《天淨沙：秋思》。 + + + + 張錯， 《西洋文學術與手冊》，台北：書林，2005。頁201。 + + 珍．奧斯丁，《傲慢與偏見》。 + + 中國青年守則 + 中國學位論文全文數據庫 + 周慧玲，《表演中國：女明星表演文化視覺政治1910-1945》，2004。 + 朱自清， 《憶》跋。 + + Zimman, Lal. Lal Zimman + , accessed February 1, + 2021. + + Zupko, Ronald Edward + British Weights & Measures: A History from Antiquity to the Seventeenth + Century. Madison: University of Wisconsin + Press, 141-151. + + + + No source, made up for these Guidelines. + Example is copied from the source of these + Guidelines. + Undetermined. + + + +
+
+ Works Cited Elsewhere in the Text of these Guidelines + + + + + Knuth + Donald E. + + Literate Programming + CSLI Lecture Notes 27 + 0-937073-80-6 + + Stanford, California + Center for the Study of Language and Information + 1992 + + + + + + + Mazzolini + Renato + G. + + Colonialism and the Emergence of Racial Theories + + + + Reproduction: Antiquity to the Present Day + + Nick + Hopwood + + + Rebecca + Flemming + + + Lauren + Kassell + + + Cambridge + Cambridge University Press + 2018 + + 361-374 + + + + + + Rubin + Gayle + + The Traffic in Women: Notes on the <q>Political Economy</q> of Sex + + + + Toward an Anthropology of Women + + Rayna + R. + Reiter + + + New York + Monthly Review Press + 1975 + + 157–210, 165 + + + + + + + A. G. + Petty + + English literary hands from Chaucer to Dryden + + London + Edward Arnold + 1977 + + 22–25 + + + + + + Lou + Burnard + + Report of Workshop on Text Encoding Guidelines + + + Literary & Linguistic Computing + + 3 + 1988 + + + + + + + Lou + Burnard + + + C. + Michael + Sperberg-McQueen + + The Design of the TEI Encoding Scheme + 10.1007/BF01830314 + + + Computers and the Humanities + + 29 + 1 + 1995 + 17–39 + + + Reprinted in , pp. 17-40 + + + + + Lou + Burnard + + + Sebastian + Rahtz + + RelaxNG with Son of ODD + + + + Proceedings of Extreme Markup Languages 2004 + + 2004 + + + + + + + M. + B. + Parkes + + English Cursive Book Hands 1250–1500 + + Oxford + Clarendon Press + 1969 + + + + + + British Literary Manuscripts. Series 2: from 1800 to 1914 + + Klinkenborg + Verlyn + + + Cahoon + Herbert + + + New York + Pierpont Morgan Library + 1981 + + + + + + + Paul + Grosso + + + Eve + Maler + + + Jonathan + Marsh + + + Norman + Walsh + + XPointer Framework + + + W3C + 25 March 2003 + + + + + + + Paul + Grosso + + + Eve + Maler + + + Jonathan + Marsh + + + Norman + Walsh + + XPointer element() Scheme + + + W3C + 25 March 2003 + + + + + + XHTML™ 1.0 The Extensible HyperText Markup Language (Second + Edition) + + + W3C + 26 January 2000 + + + + + + + Dave + Ragget + + + Arnaud + Le Hors + + + Ian + Jacobs + + HTML 4.01 Specification + + + W3C + 24 December 1999 + + + + + + + David + Carlisle + + + Patrick + Ion + + + Robert + Miner + + + Nico + Poppelier + + Mathematical Markup Language (MathML) Version 2.0 (Second + edition) + + + W3C + 21 October 2003 + + + + + + + Paul V. + Biron + + + Ashok + Malhotra + + XML Schema Part 2: Datatypes Second Edition + + + W3C + 28 October 2004 + + + + + + + Anders + Berglund + + Extensible Stylesheet Language (XSL) Version 1.1 + + + W3C + 5 December 2006 + + + + + + + James + Clark + + XSL Transformations (XSLT) Version 1.0 + + + W3C + 16 November 1999 + + + + + + + Michael + Kay + + XSL Transformations (XSLT) Version 2.0 + + + W3C + 23 January 2007 + + + + + + + Michael + Kay + + XSL Transformations (XSLT) Version 3.0 + + + W3C + 8 June 2017 + + + + + + + Tim + Bray + + + Jean + Paoli + + + C. M. + Sperberg-McQueen + + + Eve + Maler + + + François + Yergau + + Extensible Markup Language (XML) Version 1.0 (Fourth edition) + + + W3C + 16 August 2006 + + + + + + + Bert + Bos + + + Tantek + Çelik + + + Ian + Hickson + + + Håkon Wium + Lie + + Cascading Style Sheets Level 2 Revision 1 + + + W3C + 7 June 2011 + + + + + + + Håkon Wium + Lie + + + Bert + Bos + + Cascading Style Sheets, Level 1 + + + W3C + 11 January 1999 + + + + + + + fantasai + + + Koji + Ishi + + CSS Writing Modes Level 3 (W3C Candidate Recommendation) + + + W3C + 15 December 2015 + + + + + + + Simon + Fraser + + + Dean + Jackson + + + Edward + O'Connor + + + Dirk + Schulze + + CSS Transforms Module Level 1 (W3C Working Draft) + + + W3C + 26 November 2013 + + + + + + + Frank + Manola + + + Eric + Miller + + + Brian + McBride + + RDF 1.1 Primer + + + W3C + 24 June 2014 + + + + + + + Jonathan + Marsh + + + Richard + Tobin + + XML Base (Second Edition) + + + W3C + 28 January 2009 + + + + + + + James + Clark + + + Steve + DeRose + + XML Path Language (XPath) Version 1.0 + + + W3C + 16 November 1999 + + + + + + + Anders + Berglund + + + Scot + Boag + + + Mary F. + Fernández + + + Michael + Kay + + + Jonathan + Robie + + + Jérôme + Siméon + + XML Path Language (XPath) 2.0 + + + W3C + 23 January 2007 + + + + + + + Jonathan + Robie + + + Don + Chamberlin + + + Michael + Dyck + + + Jon + Snelson + + XML Path Language (XPath) 3.0 + + + W3C + 8 April 2014 + + + + + + + Jonathan + Robie + + + Michael + Dyck + + + Josh + Spiegel + + XML Path Language (XPath) 3.1 + + + W3C + 21 March 2017 + + + + + + + Tim + Bray + + + Dave + Hollander + + + Andrew + Laymon + + + Richard + Tobin + + Namespaces in XML 1.0 (second edition) + + + W3C + 16 August 2006 + + + + + + + Eric + van der Vlist + + RELAX NG + + + O'Reilly + 2004 + + + + + + + Renear + A. + + + Mylonas + E. + + + Durand + D. + + Refining our notion of what text really is: the problem of overlapping + hierarchies + + + + Nancy + Ide + + + Susan + Hockey + + Research in Humanities Computing + + Oxford University Press + 1996 + + + + + + + Robert + Sanderson + + + Paolo + Ciccarese + + + Benjamin + Young + + Web Annotation Data Model + + + W3C + 23 February 2017 + + + + + + + Robert + Sanderson + + + Paolo + Ciccarese + + + Benjamin + Young + + Web Annotation Vocabulary + + + W3C + 23 February 2017 + + + + + + The Unicode Standard, Version 5.0 + + Unicode Consortium + + Addison-Wesley Professional + 2006 + + + + + + + Addison + Phillips + + + Mark + Davis + + Tags for Identifying Languages + RFC 4646 + + 2006 + IETF + + + + + + + Addison + Phillips + + + Mark + Davis + + Matching of Language Tags + RFC 4647 + + 2006 + IETF + + + + + + + Mark + Davis + + + Ken + Whistler + + + Asmus + Freytag + + Unicode Character Database + + + Unicode Consortium + 2006 + + + + + + + + Fernando + C. + N. + Pereira + + Grammars and logics of partial information + + Menlo Park, CA + SRI International + 1987 + + + + SRI International Technical Note + 420 + + + + + + Bob + Carpenter + + The logic of typed feature structures + + Cambridge + Cambridge University Press + 1992 + + + + Cambridge Tracts in Theoretical Computer Science + 32 + + + + + + Stuart + Shieber + + An Introduction to Unification-based Approaches to Grammar + CSLI Lecture Notes 4 + + Center for the Study of Language and Information + Palo Alto, CA + 1986 + + + + + + Anglo-American Cataloguing Rules + Second Edition, 2002 revision, 2005 update + + Chicago + American Library Association + Ottawa + Canadian Library Association + 2002–2005 + + + + + + + + John + Burrows + + Computation into Criticism: A Study of Jane Austen's Novel and an + Experiment in Method + + Oxford + Clarendon Press + 1987 + + + + + + + + Klaus + Mattheier + + + Ulrich + Ammon + + + Peter + Trudgill + + Sociolinguistics + Soziolinguistik + An international handbook of the science of + language and society + Ein internationales Handbuch zur Wissenschaft + von Sprache und Gesellschaft + + Berlin + New York + De Gruyter + 1988 + I + 271 and 274 + + + + + + + J. + A. + Edwards + + + M. + D. + Lampert + + Talking Language: Transcription and Coding of Spoken Discourse + + Hillsdale, N.J. + Lawrence Erlbaum Associates + 1993 + + + + + + + Asmus + Freytag + + The Unicode Character Property Model + Unicode Technical Report #23 + + + 2006 + + + + + + + Mark + Davis + + + Aharon + Lanin + + + Andrew + Glass + + Unicode Bidirectional Algorithm + Unicode Standard Annex #9 + + + 2017-05-04 + + r. 37 + + + + + + + Stig + Johansson + + Encoding a Corpus in Machine-Readable Form + + + + + Sue + Atkins + + + Antonio + Zampolli + + Computational Approaches to the Lexicon: An Overview + + Oxford + Oxford University Press + 1994 + + + + + + + + Stig + Johansson + + + Lou + Burnard + + + Jane + Edwards + + + And + Rosta + + Working Paper on Spoken Texts + TEI document TEI AI2 W1 + + 1991 + + + + + + + + Brian + MacWhinney + + CHAT Manual + + Pittsburgh + Dept of Psychology, Carnegie-Mellon University + 1988 + 87ff + + + + + + + Bengt + Loman + + + Nils + Jørgensen + + Manual for analys och beskrivning av makrosyntagmer + + Lund + Studentlitteratur + 1971 + + + + + + + Robert + A. + Amsler + + + Frank + W. + Tompa + + An SGML-Based Standard for English Monolingual Dictionaries + + + Information in Text + Fourth Annual Conference of the U[niversity of] W[aterloo] + Centre for the New Oxford English Dictionary + Fourth Annual Conference of the U[niversity of] W[aterloo] Centre for the New + Oxford English Dictionary, October 26-28, 1988, Waterloo, Canada + + Waterloo, Canada + October 1988 + 61-79 + + + + + + + + N. + Calzolari + + + C. + Peters + + + A. + Roventini + + Computational Model of the Dictionary Entry: Preliminary + Report + Acquilex: Esprit Basic Research Action No. 3030, Six-Month + Deliverable + + Pisa + April 1990 + + + + + + + + John + Fought + + + Carol + Van Ess-Dykema + + Toward an SGML Document Type Definition for Bilingual + Dictionaries + TEI working paper TEI AIW20 + + available from the TEI. + + + + + + + + Nancy + Ide + + + Jean + Veronis + + Encoding Print Dictionaries + + + Computers and the Humanities + + 29 + 1995 + 167-195 + + + + + + + Nancy + Ide + + + Jacques + Le Maitre + + + Jean + Veronis + + Outline of a Model for Lexical Databases + + + Information Processing and Management + + 29 + 2 + 1993 + 159-186 + + + + + + + Nancy + Ide + + + Jean + Veronis + + + Susan + Warwick-Amstrong + + + Nicoletta + Calzolari + + Principles for Encoding machine readable dictionaries + + + Proceedings of the Fifth EURALEX International Congress, + EURALEX'92 + Fifth EURALEX International Congress, EURALEX'92, University of Tampere, + Finland + + 1992 + + + + + + + + The + DANLEX Group + + Descriptive tools for electronic processing of dictionary data + + + Lexicographica, Series Maior + + Tübingen + Niemeyer + 1987 + + + + + + + + Agnès + Tutin + + + Jean + Veronis + + Electronic dictionary encoding: customizing the TEI Guidelines + + + Proceedings of the Eighth Euralex International Congress + Eighth Euralex International Congress + + 1998 + + + + + + + N. + Ide + + + A. + Kilgarriff + + + L. + Romary + + A Formal Model of Dictionary Structure and Content + + + Proceedings of Euralex 2000 + Euralex 2000 + + Stuttgart + 2000 + 113-126 + + + + + + + William + A. + Gale + + + Kenneth + W. + Church + + Program for aligning sentences in bilingual corpora + + + Computational Linguistics + + 19 + 1993 + 75-102 + + + + + + + G. + N. + Leech + + + R. + G. + Garside + + Running a Grammar Factory + + + + S. + Johansson + + + A.-B. + Stenstrøm + + English Computer Corpora: Selected Papers and Research Guide + + Berlin + de Gruyter + New York + Mouton + 1991 + pp. 15-32. + + + + + + + + I. + Marshall + + Choice of Grammatical Word Class without Global Syntactic Analysis: + Tagging Words in the LOB Corpus + + + Computers and the Humanities + + 17 + 1983 + 139-50 + + + + + + + + R. + G. + Garside + + + G. + N. + Leech + + + G. + R. + Sampson + + The Computational Analysis of English: a Corpus-Based Approach + + Oxford + Oxford University Press + 1991 + + + + + + + + Gary + Chartrand + + + Linda + Lesniak + + Graphs and Digraphs + + Menlo Park, CA + Wadsworth + 1986 + + + + + + + + R. + Jackendoff + + X-Bar Syntax: A study of phrase structure + + + Linguistic Inquiry Monograph + + 2 + 1977 + + + + + + + + M. + Kytö + + + M. + Rissanen + + The Helsinki Corpus of English Texts + + + + M. + Kytö + + + O. + Ihalainen + + + M. + Rissanen + + Corpus Linguistics: hard and soft + + Amsterdam + Rodopi + 1988 + + + + + + + + Steven + DeRose + + Markup overlap: a review and a horse + + + + Proceedings of Extreme Markup Languages 2004 + + 2004 + + + + + + + Andreas + Witt + + Multiple Informationsstrukturierung mit + Auszeichnungssprachen. XML-basierte Methoden und deren Nutzen für die + Sprachtechnologie + + 2002 + + + Ph D thesis, Bielefeld University + See also + + + + + + + Mirco + Hilbert + + + Oliver + Schonefeld + + + Andreas + Witt + + Making CONCUR work + + + + Proceedings of Extreme Markup Languages 2005 + + 2005 + + + + + + + + Alex + Dekhtyar + + + Ionut + E. + Iacob + + A framework for management of concurrent XML markup + + + + + 2005 + + + + + + + + H. + V. + Jagadish + + + Laks + V. + S. + Lakshmanan + + + Monica + Scannapieco + + + Divesh + Srivastava + + + Nuwee + Wiwatwattana + + Colorful XML: one hierarchy isn't enough + + + + + + + 2004 + + + + + + + + Noureddine + Chatti + + + Suha + Kaouk + + + Sylvie + Calabretto + + + Jean + Marie + Pinon + + MultiX: an XML based formalism to encode multistructured + documents + + + + + + Proceedings of Extreme Markup Languages 2007 + + 2007 + + + + + + + + Patrick + Durusau + + + Matthew + Brook + O'Donnell + + Coming down from the trees: next step in the evolution of markup? + + + Proceedings of Extreme Markup Languages 2002 + + 2002 + + + + + + + + Jeni + Tennison + + + Wendell + Piez + + The layered markup and annotation language + + + Proceedings of Extreme Markup Languages Conference + + 2002 + + + + + + + + Claus + Huitfeldt + + + C. + Michael + Sperberg-McQueen + + TexMECS: An experimental markup meta-language for complex + documents + + + 2001 + + + + + + + D. Terence + Langendoen + + + Gary F. + Simons + + A rationale for the TEI recommendations for feature-structure + markup, + + + Computers and the Humanities + + 29 + 1995 + 167-195 + + + + + + British Standards Institute + BS 5605:1990: Recommendations for Citing and Referencing Published + Material + + 1990 + + + + + + British Standards Institute + BS 6371:1983: Recommendations for Citation of Unpublished + Documents + + 1983 + + + + + + Deutsches Institut für Normung + DIN 1505-2: Titelangaben von Dokumenten; Zitierregeln + + 1984 + + + + + + Die Deutsche Bibliothek + Regeln für die alphabetische Katalogisierung in wissenschaftlichen + Bibliotheken RAK-WB + + 2006 + + + + + + International Organization for Standardization + ISO 690:1987: Information and documentation – Bibliographic references – Content, + form and structure + + 1987 + + + + + + International Organization for Standardization + ISO 8601:2004: Data elements and interchange formats — Information interchange — + Representation of dates and times + + 2004 + + + + + + International Organization for Standardization + ISO 12620:2009: Terminology and other language and content resources – + Specification of data categories and management of a Data Category Registry for language + resources + + + 2009 + + + + + + International Organization for Standardization + ISO 19136:2007: Geographic information — Geography Markup Language (GML) + + 2006 + + + + + + International Organization for Standardization + ISO/IEC 19757-3:2006: Information technology — Document Schema Definition Languages + (DSDL) – Part 3: Rule-based validation – Schematron + + 2006 + + + + + + Istituto Centrale per il Catalogo Unico + Regole italiane di catalogazione per autori + + 1979 + + + + + + National Information Standards Organization + ANSI/NISO Z39.29 – 2005 (R2010) Bibliographic References + + 2010 + + + + + + ISBD: International Standard Bibliographic Description + + Berlin, München + De Gruyter Saur + 2011 + + + + IFLA Series on Bibliographic Control + 44 + + + + + Федеральное агентство по техническому регулированию и метрологии + (РОССТАНДАРТ) + ГОСТ Р 7.0.5-2008: Система стандартов по информации, библиотечному и + издательскому делу. Библиографическая ссылка. Общие требования и правила + составления + + 2008 + + + + + + Федеральное агентство по техническому регулированию и метрологии + (РОССТАНДАРТ) + ГОСТ 7.1—2003. Система стандартов по информации, библиотечному и + издательскому делу. Библиографическая запись. Библоиграфическое описание. Общие + требования и правила составления + + 2003 + + + + + + DCMI Usage Board + Dublin Core™ Metadata Element Set, Version 1.1: Reference Description + + + 2012-06-14 + + + + +
+
+ Reading List +

The following lists of readings in markup theory and the TEI derive from work + originally prepared by Susan Schreibman and Kevin Hawkins for the TEI Education Special + Interest Group, recoded in TEI P5 by Sabine Krott and Eva Radermacher. They should be regarded + only as a snapshot of work in progress, to which further contributions and corrections are + welcomed (see further ).

+
+ Theory of Markup and XML + + + + + C. + Michael + Sperberg-McQueen + + + Claus + Huitfeld + + Concurrent Document Hierarchies in MECS and SGML + + + Literary and Linguistic Computing + + 14 + 1 + 1999 + 29-42 + + + + + + + C. + Michael + Sperberg-McQueen + + Rabbit/duck grammars: a validation method for overlapping + structures + + + + Proceedings of Extreme Markup Languages 2006 + + 2006 + + + + + + + David + T. + Barnard + + + Lou + Burnard + + + Jean-Pierre + Gaspart + + + Lynne + A. + Price + + + C. + Michael + Sperberg-McQueen + + + Giovanni + Battista + Varile + + Hierarchical Encoding of Text: Technical Problems and SGML + Solutions + 10.1007/BF01830617 + + + + Computers and the Humanities + + 29 + 3 + 1995 + 211–231 + + + + + + + David + T. + Barnard + + + Lou + Burnard + + + C. + Michael + Sperberg-McQueen + + Lessons learned from using SGML in the Text Encoding Initiative + 10.1016/0920-5489(95)00035-6 + + + Computer Standards & Interfaces + + 18 + 1 + 1996 + 3–10 + + + + + + + Lou + Burnard + + What is SGML and how does it help? + + + + + Daniel + Greenstein + + Modelling Historical Data: Towards a Standard for Encoding and + Exchanging Machine-readable Texts + + St Katherinen + Max-Planck-Institut für Geschichte In Kommission bei Scripta Mercaturae + Verlag + 1991 + 81–91 + + + + Halbgraue Reihe zur Historischen Fachinformatik + + Herausg. von + + Manfred + Thaller + + + serie A + 11 + + + Revised version published as + + + + + Lou + Burnard + + SGML on the Web: Too Little Too Soon or Too Much Too Late? + + + + Computers & Texts + + 15 + 1995 + 12–15 + + + + + + + + Lou + Burnard + + What is SGML and How Does It Help? + 10.1007/BF01830315 + + + + Computers and the Humanities + + 29 + 1 + 1995 + 41–50 + + + Reprinted in , pp. 41-50 + + + + + Nancy + Ide + + + Jean + Veronis + + The Text Encoding Initiative: Background and Contexts + + Dordrecht + Boston + Kluwer Academic Publisher + 1995 + + + + + + + Lou + Burnard + + Is Humanities Computing an Academic Discipline? or, Why Humanities + Computing Matters + + + + 1999 + + + + Presented at an interdisciplinary seminar at the Institute for Advanced Technology + in the Humanities, University of Virginia, November 1999. + + + + + Lou + Burnard + + Using SGML for Linguistic Analysis: The Case of the BNC + + + + Markup Languages Theory and Practice + + 2 + 1999 + Cambridge, Massachusettes + MIT Press + 31–51 + + + Also published in , pp. 53–72 + + + + + Stephan + Moser + + + Peter + Stahl + + + Werner + Wegstein + + + Norbert + Richard + Wolf + + Maschinelle Verarbeitung Altdeutscher Texte V (Beiträge zum Fünften + Internationalen Symposion, Würzburg, 4–6 März 1997) + + Tübingen + Niemeyer + 2001 + + + + + + + Lou + Burnard + + + Elizabeth + Lalou + + + Peter + Robinson + + Vers un Standard Européen de Description des Manuscrits: Le Projet + Master + + + Documents Numeriques + Les Documents Anciens + + 3 + 1–2 + 1999 + Paris + Hermes Science Publications + 151-169 + + + + + + + Lou + Burnard + + XML: The Dream and the Reality + + + 1999 + + + Closing plenary address at the XML Europe Conference, Granada, May 1999 + + + + + Lou + Burnard + + + Claudia + Claridge + + + Josef + Schmied + + + Rainer + Siemund + + Encoding the Lampeter Corpus + + + + DRH98: Selected Papers from Digital Resources for the + Humanities + + London + Office for Humanities Communication + 2000 + + + + + + + + Lou + Burnard + + From Two Cultures to Digital Culture: The Rise of the Digital + Demotic + + + 2000 + + + Presented at CLIP, Alicante + + Published in Italian as + + + + + + Lou + Burnard + + Dalle «Due Culture» Alla Cultura Digitale: La Nascita del Demotico + Digitale + + Translated by + + Federico + Pellizi + + + + + Il Verri + Nella Rete + + 16 + 2001 + Milano + Monogramma + 9–22 + + + + + + + Lou + Burnard + + On the Hermeneutic Implications of Text Encoding + + + + + Domenico + Fiormonte + + + Jonathan + Usher + + New Media and the Humanities: Research and Applications + + Oxford + Humanities Computing Unit + 2001 + 31–38 + + + + + + + + Lou + Burnard + + Encoding Standards for the Electronic Edition + + + + + Matija + Ogrin + + Znanstvene Izdaje in Elektronski + Medij + Scholarly Editions and the Digital + Medium + + Ljubljana + Studia Litteraria ZRC ZAZU + 2005 + 12–67 + + + + + + + + Lou + Burnard + + Metadata for corpus work + + + + + Martin + Wynne + + Developing Linguistic Corpora: A Guide to Good Practice + + Oxford + Oxbow Books + 2005 + 30–46 + + + + + + + + Lou + Burnard + + + Katherine + O'Brien + O'Keefe + + + John + Unsworth + + Electronic Textual Editing + + + New York + Modern Languages Association + 2006 + + + + + + + Dino + Buzzetti + + Digital Representation and the Text Model + + + + New Literary History + + 33 + 1 + 2002 + 61–88 + + + + + + + + Paul + Caton + + Markup's Current Imbalance + + + Markup Languages: Theory and Practice + + 3 + 1 + 2001 + 1–13 + + + This paper was proceeded by reports at the Joint Annual Conference of the + Association for Computers and the Humanities and the Association for Literary and + Linguistic Computing in 1999 (Charlottesville, Virginia) and Extreme Markup Languages + 2000 (Montreal, Canada) + + + + + Ruey-Shun + Chen + + + Shien-Chiang + Yu + + Developing an XML Framework for Metadata System + + + + Proceedings of the 1st International Symposium on Information and + Communication Technologies + + Dublin + 2003 + 267–272 + + + + ACM International Conference Proceeding Series + 49 + + + This paper was presented in a session entitled "Electronic Document + Technology." + + + + + James + H. + Coombs + + Information Management System for Scholars + Technical Memorandum TM 69–2 + + Providence + Brown Computer Center + 1986 + + + + + + + James + H. + Coombs + + + Allen + Renear + + + Steven + J. + DeRose + + Markup Systems and The Future of Scholarly Text Processing + 10.1145/32206.32209 + + + + + Communications of the ACM + + 30 + 11 + 1987 + 933–947 + + + Reprinted with new commentary in , pp 85–118 + + + + + George + P. + Landow + + + Paul + Delany + + The Digital Word: Text-based Computing in the Humanities + + Cambridge, MA + MIT Press + 1993 + + + + + + + Robin + Cover + + Markup Languages and (Non-) Hierarchies + + + 2005 + + + Technology report from the Cover Pages + + + + + + Steven + J. + DeRose + + Structured Information: Navigation, Access, and Control + + + 1995 + + + Paper presented at the Berkeley Finding Aid Conference, April 4–6, 1995 + + + + + + Steven + J. + DeRose + + + David + G. + Durand + + + Elli + Mylonas + + + Allen + H. + Renear + + What is Text, Really? + + + Journal of Computing in Higher Education + + 1 + 2 + 1990 + 3–26 + + + Republished () as a "classic reprint" with invited + commentary and authors' replies in the ACM/SIGDOC + + + + + Steven + J. + DeRose + + + David + G. + Durand + + + Elli + Mylonas + + + Allen + H. + Renear + + What is Text, Really? + 10.1145/264842.264843 + + + Journal of Computer Documentation + + 21 + 3 + 1997 + 1–24 + + + + + + + Charles + F. + Goldfarb + + A Generalized Approach to Document Markup + + + + Proceedings of the ACM SIGPLAN SIGOA Symposium on Text + Manipulation + + New York + ACM + 1981 + 68–73 + + + Adapted as "Annex A. Introduction to Generalized Markup" in ISO 8879 + + + + + + Tony + Graham + + Unicode: What Is It and How Do I Use It? + + + Markup Languages: Theory & Practice + + 1 + 4 + 1999 + 75 + + + + + + + Susan + Hockey + + Creating and Using Electronic Editions + + + + Richard + J. + Finneran + + The Literary Text in the Digital Age + + Ann Arbor, MI + University of Michigan Press + 1996 + 1–22 + + + + + + + Susan + Hockey + + + Allen + Renear + + + Jerome + J. + McGann + + What is Text? A Debate on the Philosophical and Epistemological Nature + of Text in the Light of Humanities Computing Research + + + 1999 + + + Panel presented at ACH/ALLC 1999 + + + + + + Susan + Hockey + + Electronic Texts in the Humanities + + New York, NY + Oxford University Press + 2000 + + + + + + + Claus + Huitfeldt + + Multi-dimensional Texts in a One-dimensional Medium + 10.1007/BF01830270 + + + Computers and the Humanities + + 28 + 4/5 + 1994 + 235–241 + + + + + + + Claus + Huitfeldt + + Toward a Machine-Readable Version of Wittgenstein's Nachlaß: Some + Editorial Problems + + + + Hans + Gerhard + Senger + + Philosophische Editionen. Erwartungen an sie — Wirkungen durch + sie + + Tübingen + Max Niemeyer Verlag + 1994 + 37–43 + + + + Beihefte zu editio + 6 + + + + + + Leslie + Lamport + + Document Production: Visual or Logical? + + + + Notices of the American Mathematical Society + + 34 + 1987 + 621–624 + + + + Republished as + + + + + Leslie + Lamport + + Document Production: Visual or Logical? + + + + TUGboat + + 9 + 1 + 1988 + 8-10 + + + + + + + + + + John + Lavagnino + + Completeness and Adequacy in Text Encoding + + + + Richard + J. + Finneran + + The Literary Text in the Digital Age + + Ann Arbor, MI + University of Michigan Press + 1996 + 63–76 + + + + + + + Charles + Lightfoot + + Generic Textual Element Identification—A Primer + + Arlington + Graphic Communications Computer Association + 1979 + + + + + + + Joshua + Lubell + + Structured Markup on the Web: A Tale of Two Sites + + + + Markup Languages: Theory & Practice + + 1 + 3 + 1999 + 7–22 + + + + + + + + Tony + McEnery + + + Lou + Burnard + + + Andrew + Wilson + + + Paul + Baker + + Validation of Linguistic Corpora + + + 1998 + + + + Report commissioned by ELRA + + + + + Jerome + McGann + + The Rationale of Hypertext + + + + Kathryn + Sutherland + + Electronic Text: Investigations in Method and Theory + + New York, NY + Clarendon Press Oxford + 1997 + 19–46 + + + + + + + Jerome + McGann + + Radiant Textuality: Literature After the World Wide Web + + New York, NY + Palgrave Macmillian + 2001 + + + + + + + Jerome + McGann + + Marking Texts of Many Dimensions + + + + + Susan + Schreibman + + + Ray + Siemens + + + John + Unsworth + + A Companion to Digital Humanities + + Oxford + Blackwell + 2004 + 198–217 + + + + + + + + Alan + Morrison + + + Michael + Popham + + + Karen + Wikander + + Creating and Documenting Electronic Texts: A Guide to Good + Practice + + + (no date) + + + + + + + + Alois + Pichler + + Advantages of a Machine-Readable Version of Wittgenstein's + Nachlaß + + + + + Kjell + S. + Johannessen + + + Tore + Nordenstam + + Culture and Value: Philosophy and the Cultural Sciences. Beiträge des + 18. Internationalen Wittgenstein Symposiums 13–20. August 1995 Kirchberg am + Wechsel + + Kirchberg am Wechsel + Die Österreichische Ludwig Wittgenstein Gesellschaft + 1995 + 770–776 + + + + + + + + + Wendell + Piez + + Beyond the 'Descriptive vs. Procedural' Distinction + + + + + B. + Tommie + Usdin + + + Steven + R. + Newcomb + + Proceedings of Extreme Markup Languages 2001: Montreal, Canada + + 2001 + + + + + + + + + Michael + Popham + + What Is Markup and Why Does It Matter + + + + Michael + Popham + + + Lorna + Hughes + + Computers and Teaching in the Humanities: Selected Papers from the + CATH94 Conference held in Glasgow University September 9th-12th 1994 + + Oxford + CTI Centre for Textual Studies + 1996 + + + + + + + Liam + Quin + + Suggestive Markup: Explicit Relationships in Descriptive and + Prescriptive DTDs + + + + + B. + Tommie + Usdin + + + Deborah + A. + Lapeyre + + SGML'96 Conference Proceedings + + Alexandria, VA + Graphic Communications Association + 1996 + 405–418 + + + + + + + + Darrell + Raymond + + + Frank + Tompa + + + Derick + Wood + + From Data Representation to Data Model: Meta-Semantic Issues in the + Evolution of SGML + + + + Computer Standards & Interfaces + + 18 + 1 + 1996 + 25–36 + + + + + + + Allen + Renear + + + David + Durand + + + Elli + Mylonas + + Refining our Notion of What Text Really Is: The Problem of Overlapping + Hierarchies + + + + + Susan + Hockey + + + Nancy + Ide + + Research in Humanities Computing 4: Selected Papers from the 1992 + ALLC/ACH Conference + + Oxford + Oxford University Press + 1996 + 263–280 + + + + + + + + Allen + Renear + + Out of Praxis: Three (Meta)Theories of Textuality + + + + Kathryn + Sutherland + + Electronic Text: Investigations in Method and Theory + + New York, NY + Clarendon Press Oxford + 1997 + 107–126 + + + + + + + Allen + Renear + + The Descriptive/Procedural Distinction is Flawed + + + Markup Languages: Theory and Practice + + 2 + 4 + 2000 + 411–420 + + + + + + + + Allen + H. + Renear + + + David + Dubin + + + C. + Michael + Sperberg-McQueen + + Towards a Semantics for XML Markup + 10.1145/585058.585081 + + + + Richard + Furuta + + + Jonathan + I. + Maletic + + + Ethan + V. + Munson + + Proceedings of the 2002 ACM Symposium on Document Engineering + + McLean, VA + Association for Computing Machinery + 2002 + 119–126 + + + + + + + Allen + H. + Renear + + + Christopher + Phillippe + + + Pat + Lawton + + + David + Dubin + + An XML Document Corresponds to Which FRBR Group 1 Entity? + + + + + + B. + Tommie + Usdin + + + Steven + R. + Newcomb + + Proceedings of Extreme Markup Languages 2003: Montreal, Canada + + 2003 + + + + + + + + + Allen + H. + Renear + + + David + Dubin + + + C. + Michael + Sperberg-McQueen + + + Claus + Huitfeldt + + XML Semantics and Digital Libraries + + + + Proceedings of the 3rd ACM/IEEE–CS Joint Conference on Digital + Libraries + + Los Alamitos, CA + IEEE Computer Society + 2003 + 303–305 + + + + + + + + Allen + H. + Renear + + Text Encoding + + + + + Susan + Schreibman + + + Ray + Siemans + + + John + Unsworth + + A Companion to Digital Humanities + + Oxford + Blackwell + 2004 + 218–239 + + + + + + + + Susanne + Salmon-Alt + + Data Structures for Etymology: Towards an Etymological Lexical + Network + + + + BULAG: revue internationale annuelle + Numéro Etymologie + + 31 + 2006 + Besançon + Presses Universitaires de Franche-Comté + + + + + + + + Susan + Schreibman + + Computer-mediated Texts and Textuality: Theory and Practice + 10.1023/A:1016178200469 + + + Computers and the Humanities + + 36 + 3 + 2002 + 283–293 + + + + + + + Susan + Schreibman + + The Text Ported + 10.1093/llc/17.1.77 + + + Literary and Linguistic Computing + + 17 + 1 + 2002 + 77–87 + + + + + + + SGML Users' Group + + A Brief History of the Development of SGML + + + 1990 + + + + + + + + Frank + M. + Shipman + III + + + Catherine + C. + Marshall + + Formality Considered Harmful: Experiences, Emerging Themes, and + Directions on the Use of Formal Representations in Interactive Systems + 10.1023/A:1008716330212 + + + + Computer-Supported Cooperative Work + + 8 + 4 + 1999 + 333–352 + + + + + + + C. + Michael + Sperberg-McQueen + + + Claus + Huitfeldt + + Concurrent document hierarchies in MECS and SGML + 10.1093/llc/14.1.29 + + + Literary and Linguistic Computing + + 14 + 1 + 1999 + 29–42 + + + + + + + C. + Michael + Sperberg-McQueen + + + Claus + Huitfeldt + + + Allen + H. + Renear + + Meaning and Interpretation in Markup + + + Markup Languages: Theory and Practice + + 2 + 3 + 2000 + 215–234 + + + + + + + C. + Michael + Sperberg-McQueen + + + David + Dubin + + + Claus + Huitfeldt + + + Allen + Renear + + Drawing Inferences on the Basis of Markup + + + + + + B. + Tommie + Usdin + + + Steven + R. + Newcomb + + Proceedings of Extreme Markup Languages 2002: Montreal, Canada + + 2002 + + + + + + + + + Suzana + Sukovic + + Beyond the Scriptorium: The Role of the Library in Text + Encoding + + + + D-Lib + + 8 + 1 + 2002 + + + + + + + + University of Nebraska — Lincoln Libraries + + A Basic Guide to Text Encoding + + + + + + 2003 + + + + + + + + John + Unsworth + + Knowledge Representation in Humanities Computing + + + 2001 + + + Lecture I in the eHumanities NEH Lecture Series on Technology & the Humanities, + Washington, DC, April 3, 2001 + + + + + + John + Unsworth + + Scholarly Primitives: What Methods Do Humanities Researchers Have in + Common, How Might Our Tools Reflect This? + + + 2000 + + + Part of a Symposium on "Humanities Computing: Formal Methods, Experimental + Practice" sponsored by King's College, London + + + + + + Fabio + Vitali + + + Luca + Bompani + + + Paolo + Ciancarini + + Hypertext Functionalities with XML + + + Markup Languages: Theory & Practice + + 2 + 4 + 2000 + 389 + + + + + + + Dennis + G. + Watson + + Brief History of Document Markup + + + 1992 + + + Circular 1086. Florida Cooperative Extension Service, Institute of Food and + Agricultural Sciences, University of Florida + + + + + + Adriaan + van der + Weel + + The Concept of Markup + + + + Digital Text and the Gutenberg Heritage + + (no date) + 3 + + + in preparation; draft only + + + + + + Christopher + Welty + + + Nancy + Ide + + Using the Right Tools: Enhancing Retrieval from Marked-up + Documents + 10.1023/A:1001800717376 + + + + Computers and the Humanities + + 33 + 1–2 + 1999 + 59–84 + + + + +
+
+ TEI + + + + + Syd + Bauman + + Keying NAMEs: the WWP Approach + + + + Brown University Women Writers Project Newsletter + + 2 + 3 + 1996 + 3–6 + 10–11 + + + + + + + Syd + Bauman + + + Julia + Flanders + + Odd Customizations + + + + Proceedings of Extreme Markup Languages 2004 + + 2004 + + + + + + + Syd + Bauman + + Tables of Contents TEI-style + + + + Lou + Burnard + + TEXT Technology: The Journal of Computer Text + Processing + Electronic Texts and the Text Encoding Initiative. A Special + Issue of TEXT Technology + + 5 + 3 + 1995 + Madison, SD + College of Liberal Arts, Dakota State University + 235–247 + + + + + + + Syd + Bauman + + + Terry + Catapano + + TEI and the Encoding of the Physical Structure of Books + 10.1023/A:1001769103586 + + + Computers and the Humanities + + 33 + 1–2 + 1999 + 113–127 + + + + + + + Syd + Bauman + + TEI HORSEing Around + + + + Proceedings of the Extreme Markup Languages 2005 + + 2005 + + + + + + + Malcolm + B. + Brown + + What is the TEI? + + + Information Technology and Libraries + + 13 + 1 + 1994 + 8 + + + + + + + Lou + Burnard + + The Text Encoding Initiative: A Progress Report + + + + Gerhard + Leitner + + New Directions in Corpus Linguistics + + Berlin + Mouton de Gruyter + 1992 + + + + + + + Lou + Burnard + + Rolling your own with the TEI + + + Information Services and Use + + 13 + 2 + 1993 + Amsterdam + IOS Press + 141–154 + + + + + + + Lou + Burnard + + The TEI: Towards an Extensible Standard for the Encoding of + Texts + + + + Seamus + Ross + + + Edward + Higgs + + Electronic Information Resources and Historians + + London + British Academy + 1994 + + + + + + + Lou + Burnard + + The Text Encoding Initiative: An Overview + + + + Geoffrey + Leech + + + Greg + Myers + + + Jenny + Thomas + + Spoken English on Computer: Transcription, Mark-up and + Application + + London + Longman + 1995 + + + + + + + Lou + Burnard + + The Text Encoding Initiative's Recommendations for the Encoding of + Language Corpora: Theory and Practice + + + 1997 + + + Prepared for a seminar on Etiquetación y extracción de información de grandes corpus + textuales within the Curso Industrias de la Lengua (14–18 de Julio de 1997). Sponsored + by the Fundacion Duques de Soria. + + + + + Lou + Burnard + + + Michael + Popham + + Putting Our Headers Together: A Report on the TEI Header Meeting 12 + September 1997 + 10.1023/A:1001710828622 + + + Computers and the Humanities + + 33 + 1-2 + 1999 + Dordrecht, Boston + Kluwer Academic Publishers + 39–47 + + + + + + An Agreement to Establish a Consortium for the Maintenance of the Text Encoding + Initiative + + + March 1999 + + + + + + + Lou + Burnard + + Text Encoding for Interchange: A New Consortium + + + 2000 + + + + + + + Fabio + Ciotti + + Il Manuale TEI Lite: Introduzione Alla Codifica Elettronica Dei Testi + Letterari + + Milano + Sylvestre Bonnard + 2005 + + + + + + + Sheau-Hwang + Chang + + The Implications of TEI + + + OCLC Systems and Services + + 17 + 3 + 2001 + 101–103 + + + + + + + Mavis + Cournane + + The Application of SGML/TEI to the Processing of Complex, Multi-lingual + Text + PhD Dissertation + + Cork, Ireland + University College Cork + 1997 + + + + + + + Digital Library Federation + + TEI and XML in Digital Libraries: Meeting June 30 and July 1, 1998, + Library of Congress, Summary/Proceedings + + + + 1998 + + + + + + + + Digital Library Federation + + TEI Text Encoding in Libraries: Guidelines for Best + Encoding Practices + Version 3.0 (October 2011) + + + 2011 + + + + + + + Timothy + J. + Finney + + Manuscript Markup + + + + Larry + W. + Hurtado + + The Freer Biblical Manuscripts: Fresh Studies of an American Treasure + Trove + + Atlanta, GA + Society of Biblical Literature + 2006 + 263-288 + + + + Text-critical studies + 6 + + + + + + Matthew + Gibson + + + Christine + Ruotolo + + Beyond the Web: TEI, the Digital Library, and the Ebook + Revolution + 10.1023/A:1021895322291 + + + Computers and the Humanities + + 37 + 1 + 2003 + 57–63 + + + + + + + Sylvain + Loiseau + + Les standards : autour d'XML et de la TEI + + + 2002 + + + + + + + + Lynn + Marko + + + Christina + Kelleher Powell + + Descriptive Metadata Strategy for TEI Headers: A University of Michigan + Library Case Study + 10.1108/10650750110402585 + + + OCLC Systems & Services + + 17 + 3 + 2001 + 117-20 + + + + + + + David + Mertz + + XML Matters: TEI — the Text Encoding Initiative + An XML Dialect for Archival and Complex Documents + + + 2003 + + + + + + + Alan + Morrison + + Delivering Electronic Texts Over the Web: The Current and Planned + Practices of the Oxford Text Archive + 10.1023/A:1001726011322 + + + Computers and the Humanities + + 33 + 1-2 + 1999 + 193-198 + + + + + + + Elli + Mylonas + + + Allen + Renear + + The Text Encoding Initiative at 10: Not Just an Interchange Format + Anymore — But a New Research Community + 10.1023/A:1001832310939 + + + Computers and the Humanities + + 33 + 1-2 + 1999 + 1-9 + + + + + + + Tobin + Nellhaus + + XML, TEI, Digital Libraries in the Humanities + + + + Portal: Libraries and the Academy + + 1 + 3 + 2001 + 267-277 + + + + + + + + Sebastian + Rahtz + + Building TEI DTDs and Schemas on demand + + + + 2003 + + + Paper presented at XML Europe 2003, London, March 2003 + + + + + Sebastian + Rahtz + + + Norman + Walsh + + + Lou + Burnard + + A unified model for text markup: TEI, Docbook, and beyond + + + 2004 + + + Paper presented at XML Europe 2004, Amsterdam, April 2004 + + + + + Allen + Renear + + Theory and Metatheory in the Development of Text Encoding + + + + + Michael + A. + R. + Biggs + + + Claus + Huitfeldt + + Philosophy and Electronic Publishing + + 1995 + + + Interactive seminar for the Monist + + + + + + Peter + Robinson + + Making a Digital Edition with TEI and Anastasia + + + (no date) + + + + + + + + David + Seaman + + The Electronic Text Center Introduction to TEI and Guide to Document + Preparation + + + 1995 + + + + + + + Gary + F. + Simons + + Using Architectural Forms to Map TEI Data into an Object-Oriented + Database + 10.1023/A:1001765030032 + + + Computers and the Humanities + + 33 + 1-2 + 1999 + 85-101 + + + + + + + David + Smith + + Textual Variation and Version Control in the TEI + 10.1023/A:1001795210724 + + + Computers and the Humanities + + 33 + 1-2 + 1999 + 103-112 + + + + + + + C. + Michael + Sperberg-McQueen + + Text in the Electronic Age: Textual Study and Text Encoding, with + Examples from Medieval Texts + 10.1093/llc/6.1.34 + + + Literary & Linguistic Computing + + 6 + 1 + 1991 + 34-46 + + + + + + + C. + Michael + Sperberg-McQueen + + The Text Encoding Initiative: Electronic Text Markup for + Research + + + + Brett + Sutton + + Literary Texts in an Electronic Age + + Urbana-Champaign, IL + University of Illinois at Urbana-Champaign, Graduate School of Library and + Information Science + 1994 + 35–55 + + + + + + + C. + Michael + Sperberg-McQueen + + Textual Criticism and the Text Encoding Initiative + + + + Richard + J. + Finneran + + The Literary Text in the Digital Age + + Ann Arbor, MI + University of Michigan Press + 1996 + 37–62 + + + + + + + Edward + Vanhoutte + + An Introduction to the TEI and the TEI Consortium + 10.1093/llc/19.1.9 + + + Literary & Linguistic Computing + + 19 + 1 + 2004 + 9 + + + + + + + T. + Kindberg + + + S. + Hawke + + The 'tag' URI Scheme + + RFC 4151 + + 2005 + IETF + + + + + +
+
+
diff --git a/P5/Source/Guidelines/fr/HD-Header.xml b/P5/Source/Guidelines/fr/HD-Header.xml index a260362732..1b41c58497 100644 --- a/P5/Source/Guidelines/fr/HD-Header.xml +++ b/P5/Source/Guidelines/fr/HD-Header.xml @@ -1,3 +1,4 @@ +
diff --git a/P5/Source/Specs/TEI.xml b/P5/Source/Specs/TEI.xml index 8f058f55d7..f9e779ce03 100644 --- a/P5/Source/Specs/TEI.xml +++ b/P5/Source/Specs/TEI.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/ab.xml b/P5/Source/Specs/ab.xml index 94036c4042..8718461882 100644 --- a/P5/Source/Specs/ab.xml +++ b/P5/Source/Specs/ab.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/abbr.xml b/P5/Source/Specs/abbr.xml index 4c66655d09..e6cd6f0f6e 100644 --- a/P5/Source/Specs/abbr.xml +++ b/P5/Source/Specs/abbr.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/abstract.xml b/P5/Source/Specs/abstract.xml index aed6ce706f..fc53a09f63 100644 --- a/P5/Source/Specs/abstract.xml +++ b/P5/Source/Specs/abstract.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/accMat.xml b/P5/Source/Specs/accMat.xml index e7b7d75de0..10aa249263 100644 --- a/P5/Source/Specs/accMat.xml +++ b/P5/Source/Specs/accMat.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/acquisition.xml b/P5/Source/Specs/acquisition.xml index ed909fd03d..0fa7daab86 100644 --- a/P5/Source/Specs/acquisition.xml +++ b/P5/Source/Specs/acquisition.xml @@ -1,4 +1,6 @@ - + + + acquisition adquisición acquisition diff --git a/P5/Source/Specs/activity.xml b/P5/Source/Specs/activity.xml index bcd2a98aea..d2a37a1512 100644 --- a/P5/Source/Specs/activity.xml +++ b/P5/Source/Specs/activity.xml @@ -1,4 +1,6 @@ - + + + activity actividad activité diff --git a/P5/Source/Specs/actor.xml b/P5/Source/Specs/actor.xml index de765a29a4..3c2e9db59a 100644 --- a/P5/Source/Specs/actor.xml +++ b/P5/Source/Specs/actor.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/add.xml b/P5/Source/Specs/add.xml index f65ba3530b..8f55105eed 100644 --- a/P5/Source/Specs/add.xml +++ b/P5/Source/Specs/add.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/addName.xml b/P5/Source/Specs/addName.xml index 736b0b7967..ec28e8c578 100644 --- a/P5/Source/Specs/addName.xml +++ b/P5/Source/Specs/addName.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/addSpan.xml b/P5/Source/Specs/addSpan.xml index acaeea22c4..ffbfc6622a 100644 --- a/P5/Source/Specs/addSpan.xml +++ b/P5/Source/Specs/addSpan.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/additional.xml b/P5/Source/Specs/additional.xml index bc044829e4..aefeac5d47 100644 --- a/P5/Source/Specs/additional.xml +++ b/P5/Source/Specs/additional.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/additions.xml b/P5/Source/Specs/additions.xml index 1eed0204c2..072f726d3c 100644 --- a/P5/Source/Specs/additions.xml +++ b/P5/Source/Specs/additions.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/addrLine.xml b/P5/Source/Specs/addrLine.xml index 3c6dacb5d5..0a3a27ba6d 100644 --- a/P5/Source/Specs/addrLine.xml +++ b/P5/Source/Specs/addrLine.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/address.xml b/P5/Source/Specs/address.xml index e9905c503b..3fc9b7f3f7 100644 --- a/P5/Source/Specs/address.xml +++ b/P5/Source/Specs/address.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/adminInfo.xml b/P5/Source/Specs/adminInfo.xml index dcf9e77604..187093982e 100644 --- a/P5/Source/Specs/adminInfo.xml +++ b/P5/Source/Specs/adminInfo.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/affiliation.xml b/P5/Source/Specs/affiliation.xml index 72d8565e83..319d91a482 100644 --- a/P5/Source/Specs/affiliation.xml +++ b/P5/Source/Specs/affiliation.xml @@ -1,4 +1,6 @@ - + + + affiliation affiliation contains an informal description of a person's present or past affiliation with some diff --git a/P5/Source/Specs/age.xml b/P5/Source/Specs/age.xml index 1ee5fa574a..9d04b05f7c 100644 --- a/P5/Source/Specs/age.xml +++ b/P5/Source/Specs/age.xml @@ -1,4 +1,6 @@ - + + + age âge specifies the age of a person. diff --git a/P5/Source/Specs/alt.xml b/P5/Source/Specs/alt.xml index 04693d7422..02ba2c3b87 100644 --- a/P5/Source/Specs/alt.xml +++ b/P5/Source/Specs/alt.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/altGrp.xml b/P5/Source/Specs/altGrp.xml index aa13ad11a0..df42c046d2 100644 --- a/P5/Source/Specs/altGrp.xml +++ b/P5/Source/Specs/altGrp.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/altIdent.xml b/P5/Source/Specs/altIdent.xml index 5396cfb634..1e4f07e909 100644 --- a/P5/Source/Specs/altIdent.xml +++ b/P5/Source/Specs/altIdent.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/altIdentifier.xml b/P5/Source/Specs/altIdentifier.xml index bec4171154..1e2fea1795 100644 --- a/P5/Source/Specs/altIdentifier.xml +++ b/P5/Source/Specs/altIdentifier.xml @@ -1,4 +1,6 @@ - + + + alternative identifier 대체 확인소 替換識別符碼 diff --git a/P5/Source/Specs/alternate.xml b/P5/Source/Specs/alternate.xml index 74b743d2bf..d9f194a44e 100644 --- a/P5/Source/Specs/alternate.xml +++ b/P5/Source/Specs/alternate.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/am.xml b/P5/Source/Specs/am.xml index cb310b015f..89487bf824 100644 --- a/P5/Source/Specs/am.xml +++ b/P5/Source/Specs/am.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/analytic.xml b/P5/Source/Specs/analytic.xml index d16227469d..3ac57fee55 100644 --- a/P5/Source/Specs/analytic.xml +++ b/P5/Source/Specs/analytic.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/anchor.xml b/P5/Source/Specs/anchor.xml index 3716cd863e..bd66b33b79 100644 --- a/P5/Source/Specs/anchor.xml +++ b/P5/Source/Specs/anchor.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/annotation.xml b/P5/Source/Specs/annotation.xml index cf50df7357..4d0191b677 100644 --- a/P5/Source/Specs/annotation.xml +++ b/P5/Source/Specs/annotation.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/anyElement.xml b/P5/Source/Specs/anyElement.xml index 1623b944db..0a6034270d 100644 --- a/P5/Source/Specs/anyElement.xml +++ b/P5/Source/Specs/anyElement.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/app.xml b/P5/Source/Specs/app.xml index 6d860edfed..ee3da7cdfc 100644 --- a/P5/Source/Specs/app.xml +++ b/P5/Source/Specs/app.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/appInfo.xml b/P5/Source/Specs/appInfo.xml index 7f5136c182..45c7f9dbb8 100644 --- a/P5/Source/Specs/appInfo.xml +++ b/P5/Source/Specs/appInfo.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/application.xml b/P5/Source/Specs/application.xml index 835695be44..afad54c82d 100644 --- a/P5/Source/Specs/application.xml +++ b/P5/Source/Specs/application.xml @@ -1,4 +1,6 @@ - + + + provides information about an application which has acted upon the document. 문서에 사용한 애플리케이션에 관한 정보를 제시한다. proporciona información sobre la aplicación que ha diff --git a/P5/Source/Specs/arc.xml b/P5/Source/Specs/arc.xml index af9d075df2..c4e920af76 100644 --- a/P5/Source/Specs/arc.xml +++ b/P5/Source/Specs/arc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/argument.xml b/P5/Source/Specs/argument.xml index a7b3f4862c..13b4adb462 100644 --- a/P5/Source/Specs/argument.xml +++ b/P5/Source/Specs/argument.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.anchoring.xml b/P5/Source/Specs/att.anchoring.xml index 4dec26ca88..8841f61c63 100644 --- a/P5/Source/Specs/att.anchoring.xml +++ b/P5/Source/Specs/att.anchoring.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.ascribed.directed.xml b/P5/Source/Specs/att.ascribed.directed.xml index e622a8fae3..8eb1e80143 100644 --- a/P5/Source/Specs/att.ascribed.directed.xml +++ b/P5/Source/Specs/att.ascribed.directed.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.ascribed.xml b/P5/Source/Specs/att.ascribed.xml index 35aeb401fd..7aeb0f4421 100644 --- a/P5/Source/Specs/att.ascribed.xml +++ b/P5/Source/Specs/att.ascribed.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.breaking.xml b/P5/Source/Specs/att.breaking.xml index 75aa797a6f..1a92710321 100644 --- a/P5/Source/Specs/att.breaking.xml +++ b/P5/Source/Specs/att.breaking.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.cReferencing.xml b/P5/Source/Specs/att.cReferencing.xml index 4d93a69506..a450cd5516 100644 --- a/P5/Source/Specs/att.cReferencing.xml +++ b/P5/Source/Specs/att.cReferencing.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.calendarSystem.xml b/P5/Source/Specs/att.calendarSystem.xml index 735166ae98..abdfc796ea 100644 --- a/P5/Source/Specs/att.calendarSystem.xml +++ b/P5/Source/Specs/att.calendarSystem.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.canonical.xml b/P5/Source/Specs/att.canonical.xml index 79d247f589..cb1d8afe9b 100644 --- a/P5/Source/Specs/att.canonical.xml +++ b/P5/Source/Specs/att.canonical.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.citeStructurePart.xml b/P5/Source/Specs/att.citeStructurePart.xml index 6602536ce4..7c15aeabbe 100644 --- a/P5/Source/Specs/att.citeStructurePart.xml +++ b/P5/Source/Specs/att.citeStructurePart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.citing.xml b/P5/Source/Specs/att.citing.xml index b641d071b1..ee841a807b 100644 --- a/P5/Source/Specs/att.citing.xml +++ b/P5/Source/Specs/att.citing.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.combinable.xml b/P5/Source/Specs/att.combinable.xml index 25e6a4b9b7..5b05f5735b 100644 --- a/P5/Source/Specs/att.combinable.xml +++ b/P5/Source/Specs/att.combinable.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.coordinated.xml b/P5/Source/Specs/att.coordinated.xml index a6b3e5de71..aa9c818d63 100644 --- a/P5/Source/Specs/att.coordinated.xml +++ b/P5/Source/Specs/att.coordinated.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.damaged.xml b/P5/Source/Specs/att.damaged.xml index 9402e33774..ffbf926c28 100644 --- a/P5/Source/Specs/att.damaged.xml +++ b/P5/Source/Specs/att.damaged.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.datable.custom.xml b/P5/Source/Specs/att.datable.custom.xml index a0ef6b64e1..298ff2d19d 100644 --- a/P5/Source/Specs/att.datable.custom.xml +++ b/P5/Source/Specs/att.datable.custom.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.datable.iso.xml b/P5/Source/Specs/att.datable.iso.xml index 12b4dfdfcf..a222fbb8a3 100644 --- a/P5/Source/Specs/att.datable.iso.xml +++ b/P5/Source/Specs/att.datable.iso.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.datable.w3c.xml b/P5/Source/Specs/att.datable.w3c.xml index 4245b2c142..8563ab0a09 100644 --- a/P5/Source/Specs/att.datable.w3c.xml +++ b/P5/Source/Specs/att.datable.w3c.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.datable.xml b/P5/Source/Specs/att.datable.xml index 671fbc2406..cf817927a5 100644 --- a/P5/Source/Specs/att.datable.xml +++ b/P5/Source/Specs/att.datable.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.datcat.xml b/P5/Source/Specs/att.datcat.xml index 1081434b20..89f1611e30 100644 --- a/P5/Source/Specs/att.datcat.xml +++ b/P5/Source/Specs/att.datcat.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.declaring.xml b/P5/Source/Specs/att.declaring.xml index 300f0708fc..ffebd1514c 100644 --- a/P5/Source/Specs/att.declaring.xml +++ b/P5/Source/Specs/att.declaring.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.deprecated.xml b/P5/Source/Specs/att.deprecated.xml index 20253e6a30..2e39248858 100644 --- a/P5/Source/Specs/att.deprecated.xml +++ b/P5/Source/Specs/att.deprecated.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.dimensions.xml b/P5/Source/Specs/att.dimensions.xml index d6508d4a3e..2d79c3b0f9 100644 --- a/P5/Source/Specs/att.dimensions.xml +++ b/P5/Source/Specs/att.dimensions.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.divLike.xml b/P5/Source/Specs/att.divLike.xml index e265fe802a..25b4efbb9c 100644 --- a/P5/Source/Specs/att.divLike.xml +++ b/P5/Source/Specs/att.divLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.docStatus.xml b/P5/Source/Specs/att.docStatus.xml index 368efd4e62..47866c32af 100644 --- a/P5/Source/Specs/att.docStatus.xml +++ b/P5/Source/Specs/att.docStatus.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.duration.iso.xml b/P5/Source/Specs/att.duration.iso.xml index 16621af215..737d550651 100644 --- a/P5/Source/Specs/att.duration.iso.xml +++ b/P5/Source/Specs/att.duration.iso.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.duration.w3c.xml b/P5/Source/Specs/att.duration.w3c.xml index d4651a2362..9f0b36e673 100644 --- a/P5/Source/Specs/att.duration.w3c.xml +++ b/P5/Source/Specs/att.duration.w3c.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.duration.xml b/P5/Source/Specs/att.duration.xml index 6cc0e96f21..5cc32e857f 100644 --- a/P5/Source/Specs/att.duration.xml +++ b/P5/Source/Specs/att.duration.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.editLike.xml b/P5/Source/Specs/att.editLike.xml index 8640add267..49a594ecde 100644 --- a/P5/Source/Specs/att.editLike.xml +++ b/P5/Source/Specs/att.editLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.edition.xml b/P5/Source/Specs/att.edition.xml index 7b9d75a576..6b2d9f968f 100644 --- a/P5/Source/Specs/att.edition.xml +++ b/P5/Source/Specs/att.edition.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.enjamb.xml b/P5/Source/Specs/att.enjamb.xml index 18da1c2d3a..073c2b1104 100644 --- a/P5/Source/Specs/att.enjamb.xml +++ b/P5/Source/Specs/att.enjamb.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.entryLike.xml b/P5/Source/Specs/att.entryLike.xml index 2d7250e04d..4b11831056 100644 --- a/P5/Source/Specs/att.entryLike.xml +++ b/P5/Source/Specs/att.entryLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.formula.xml b/P5/Source/Specs/att.formula.xml index 1c586dfc1e..e3f8ba5cfb 100644 --- a/P5/Source/Specs/att.formula.xml +++ b/P5/Source/Specs/att.formula.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.fragmentable.xml b/P5/Source/Specs/att.fragmentable.xml index f7dc410d45..c9e3a9b4a9 100644 --- a/P5/Source/Specs/att.fragmentable.xml +++ b/P5/Source/Specs/att.fragmentable.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.gaijiProp.xml b/P5/Source/Specs/att.gaijiProp.xml index c4c2f03a60..bce2f4a029 100644 --- a/P5/Source/Specs/att.gaijiProp.xml +++ b/P5/Source/Specs/att.gaijiProp.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.global.analytic.xml b/P5/Source/Specs/att.global.analytic.xml index eb1687301f..2dd56940c4 100644 --- a/P5/Source/Specs/att.global.analytic.xml +++ b/P5/Source/Specs/att.global.analytic.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.global.change.xml b/P5/Source/Specs/att.global.change.xml index ef080b28b3..3b08692d6a 100644 --- a/P5/Source/Specs/att.global.change.xml +++ b/P5/Source/Specs/att.global.change.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.global.facs.xml b/P5/Source/Specs/att.global.facs.xml index 28007af28a..484fc218a3 100644 --- a/P5/Source/Specs/att.global.facs.xml +++ b/P5/Source/Specs/att.global.facs.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.global.linking.xml b/P5/Source/Specs/att.global.linking.xml index 5ad6efa452..4dbf7b053c 100644 --- a/P5/Source/Specs/att.global.linking.xml +++ b/P5/Source/Specs/att.global.linking.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.global.rendition.xml b/P5/Source/Specs/att.global.rendition.xml index 9980cede90..b28d1524be 100644 --- a/P5/Source/Specs/att.global.rendition.xml +++ b/P5/Source/Specs/att.global.rendition.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.global.responsibility.xml b/P5/Source/Specs/att.global.responsibility.xml index aefec8b5db..b3a09b3cc5 100644 --- a/P5/Source/Specs/att.global.responsibility.xml +++ b/P5/Source/Specs/att.global.responsibility.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.global.source.xml b/P5/Source/Specs/att.global.source.xml index 97371be41d..1ff09275c0 100644 --- a/P5/Source/Specs/att.global.source.xml +++ b/P5/Source/Specs/att.global.source.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.global.xml b/P5/Source/Specs/att.global.xml index f1d22e983b..f3d180c526 100644 --- a/P5/Source/Specs/att.global.xml +++ b/P5/Source/Specs/att.global.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.handFeatures.xml b/P5/Source/Specs/att.handFeatures.xml index e4ad0a6e81..c7a7c63184 100644 --- a/P5/Source/Specs/att.handFeatures.xml +++ b/P5/Source/Specs/att.handFeatures.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.identified.xml b/P5/Source/Specs/att.identified.xml index dbb3a3afb2..def3639b3c 100644 --- a/P5/Source/Specs/att.identified.xml +++ b/P5/Source/Specs/att.identified.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.internetMedia.xml b/P5/Source/Specs/att.internetMedia.xml index 9aa4efe255..b0ae3c6564 100644 --- a/P5/Source/Specs/att.internetMedia.xml +++ b/P5/Source/Specs/att.internetMedia.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.interpLike.xml b/P5/Source/Specs/att.interpLike.xml index 98431f97c8..17debf1f49 100644 --- a/P5/Source/Specs/att.interpLike.xml +++ b/P5/Source/Specs/att.interpLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.lexicographic.normalized.xml b/P5/Source/Specs/att.lexicographic.normalized.xml index 0008557043..15844831db 100644 --- a/P5/Source/Specs/att.lexicographic.normalized.xml +++ b/P5/Source/Specs/att.lexicographic.normalized.xml @@ -1,4 +1,6 @@ - + + + provides attributes for usage within word-level elements in the analysis module and within lexicographic microstructure in the dictionaries module. diff --git a/P5/Source/Specs/att.lexicographic.xml b/P5/Source/Specs/att.lexicographic.xml index 2679a2a94a..2edad5524a 100644 --- a/P5/Source/Specs/att.lexicographic.xml +++ b/P5/Source/Specs/att.lexicographic.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.linguistic.xml b/P5/Source/Specs/att.linguistic.xml index 1994494e63..ba3f7b3a8f 100644 --- a/P5/Source/Specs/att.linguistic.xml +++ b/P5/Source/Specs/att.linguistic.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.locatable.xml b/P5/Source/Specs/att.locatable.xml index 830ae5281b..173f78b874 100644 --- a/P5/Source/Specs/att.locatable.xml +++ b/P5/Source/Specs/att.locatable.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.media.xml b/P5/Source/Specs/att.media.xml index baaec18dac..b8047e105b 100644 --- a/P5/Source/Specs/att.media.xml +++ b/P5/Source/Specs/att.media.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.metrical.xml b/P5/Source/Specs/att.metrical.xml index e63bd07782..26ec9bbd6d 100644 --- a/P5/Source/Specs/att.metrical.xml +++ b/P5/Source/Specs/att.metrical.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.milestoneUnit.xml b/P5/Source/Specs/att.milestoneUnit.xml index b722615eef..c8b41afa3b 100644 --- a/P5/Source/Specs/att.milestoneUnit.xml +++ b/P5/Source/Specs/att.milestoneUnit.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.msExcerpt.xml b/P5/Source/Specs/att.msExcerpt.xml index 92bc6df421..2c08f8654e 100644 --- a/P5/Source/Specs/att.msExcerpt.xml +++ b/P5/Source/Specs/att.msExcerpt.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.namespaceable.xml b/P5/Source/Specs/att.namespaceable.xml index 605fbe4f52..f330c1d0be 100644 --- a/P5/Source/Specs/att.namespaceable.xml +++ b/P5/Source/Specs/att.namespaceable.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.naming.xml b/P5/Source/Specs/att.naming.xml index 8fc1e7b118..02661b59ef 100644 --- a/P5/Source/Specs/att.naming.xml +++ b/P5/Source/Specs/att.naming.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.notated.xml b/P5/Source/Specs/att.notated.xml index 07055a8055..4d32a7d9a8 100644 --- a/P5/Source/Specs/att.notated.xml +++ b/P5/Source/Specs/att.notated.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.partials.xml b/P5/Source/Specs/att.partials.xml index ea22dbe46a..e0a596e52b 100644 --- a/P5/Source/Specs/att.partials.xml +++ b/P5/Source/Specs/att.partials.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.patternReplacement.xml b/P5/Source/Specs/att.patternReplacement.xml index 95bd7803b9..2d4120e515 100644 --- a/P5/Source/Specs/att.patternReplacement.xml +++ b/P5/Source/Specs/att.patternReplacement.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.personal.xml b/P5/Source/Specs/att.personal.xml index aedeb3f6a4..b9de4ef0da 100644 --- a/P5/Source/Specs/att.personal.xml +++ b/P5/Source/Specs/att.personal.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.placement.xml b/P5/Source/Specs/att.placement.xml index e500b40c38..ea39dd853e 100644 --- a/P5/Source/Specs/att.placement.xml +++ b/P5/Source/Specs/att.placement.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.pointing.group.xml b/P5/Source/Specs/att.pointing.group.xml index 1d0b692f75..608afc689e 100644 --- a/P5/Source/Specs/att.pointing.group.xml +++ b/P5/Source/Specs/att.pointing.group.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.pointing.xml b/P5/Source/Specs/att.pointing.xml index 068af0dec9..be6706a871 100644 --- a/P5/Source/Specs/att.pointing.xml +++ b/P5/Source/Specs/att.pointing.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.predicate.xml b/P5/Source/Specs/att.predicate.xml index 35fe5f572b..c59aa6d56b 100644 --- a/P5/Source/Specs/att.predicate.xml +++ b/P5/Source/Specs/att.predicate.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.ranging.xml b/P5/Source/Specs/att.ranging.xml index b56565c95e..de53817f95 100644 --- a/P5/Source/Specs/att.ranging.xml +++ b/P5/Source/Specs/att.ranging.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.rdgPart.xml b/P5/Source/Specs/att.rdgPart.xml index f67751789a..e8beac7127 100644 --- a/P5/Source/Specs/att.rdgPart.xml +++ b/P5/Source/Specs/att.rdgPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.repeatable.xml b/P5/Source/Specs/att.repeatable.xml index 47943bf7fb..d998311c9c 100644 --- a/P5/Source/Specs/att.repeatable.xml +++ b/P5/Source/Specs/att.repeatable.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.resourced.xml b/P5/Source/Specs/att.resourced.xml index 24775f1a3b..063cfa695d 100644 --- a/P5/Source/Specs/att.resourced.xml +++ b/P5/Source/Specs/att.resourced.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.scoping.xml b/P5/Source/Specs/att.scoping.xml index c8fd3ca714..564e87fac2 100644 --- a/P5/Source/Specs/att.scoping.xml +++ b/P5/Source/Specs/att.scoping.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.segLike.xml b/P5/Source/Specs/att.segLike.xml index 15bb6a8e2a..ec569cd46b 100644 --- a/P5/Source/Specs/att.segLike.xml +++ b/P5/Source/Specs/att.segLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.sortable.xml b/P5/Source/Specs/att.sortable.xml index 124c80d0d9..1b66543ebb 100644 --- a/P5/Source/Specs/att.sortable.xml +++ b/P5/Source/Specs/att.sortable.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.spanning.xml b/P5/Source/Specs/att.spanning.xml index 6a95a334da..71b1611f64 100644 --- a/P5/Source/Specs/att.spanning.xml +++ b/P5/Source/Specs/att.spanning.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.styleDef.xml b/P5/Source/Specs/att.styleDef.xml index 940244f693..c51ad1314c 100644 --- a/P5/Source/Specs/att.styleDef.xml +++ b/P5/Source/Specs/att.styleDef.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.tableDecoration.xml b/P5/Source/Specs/att.tableDecoration.xml index 8c070340f0..32616a0f09 100644 --- a/P5/Source/Specs/att.tableDecoration.xml +++ b/P5/Source/Specs/att.tableDecoration.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.textCritical.xml b/P5/Source/Specs/att.textCritical.xml index 47dc41845a..0a615ba848 100644 --- a/P5/Source/Specs/att.textCritical.xml +++ b/P5/Source/Specs/att.textCritical.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.timed.xml b/P5/Source/Specs/att.timed.xml index a9773626a0..3212075348 100644 --- a/P5/Source/Specs/att.timed.xml +++ b/P5/Source/Specs/att.timed.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.transcriptional.xml b/P5/Source/Specs/att.transcriptional.xml index b3904c4cd2..af34c63c6c 100644 --- a/P5/Source/Specs/att.transcriptional.xml +++ b/P5/Source/Specs/att.transcriptional.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.translatable.xml b/P5/Source/Specs/att.translatable.xml index 547d2185ce..4565876756 100644 --- a/P5/Source/Specs/att.translatable.xml +++ b/P5/Source/Specs/att.translatable.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.typed.xml b/P5/Source/Specs/att.typed.xml index 49cc5c4c0c..f9adf9696c 100644 --- a/P5/Source/Specs/att.typed.xml +++ b/P5/Source/Specs/att.typed.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.witnessed.xml b/P5/Source/Specs/att.witnessed.xml index f094331a9c..c08ec0f2cb 100644 --- a/P5/Source/Specs/att.witnessed.xml +++ b/P5/Source/Specs/att.witnessed.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.written.xml b/P5/Source/Specs/att.written.xml index 16b8ff40fc..ccde47fe80 100644 --- a/P5/Source/Specs/att.written.xml +++ b/P5/Source/Specs/att.written.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/att.xml b/P5/Source/Specs/att.xml index a68bf3029e..46f891d634 100644 --- a/P5/Source/Specs/att.xml +++ b/P5/Source/Specs/att.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/attDef.xml b/P5/Source/Specs/attDef.xml index 4dc8ac0e27..c4a55b11f7 100644 --- a/P5/Source/Specs/attDef.xml +++ b/P5/Source/Specs/attDef.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/attList.xml b/P5/Source/Specs/attList.xml index a2a7c7fbc6..06f0db90cf 100644 --- a/P5/Source/Specs/attList.xml +++ b/P5/Source/Specs/attList.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/attRef.xml b/P5/Source/Specs/attRef.xml index 7fc2e4859b..9c7dc32e87 100644 --- a/P5/Source/Specs/attRef.xml +++ b/P5/Source/Specs/attRef.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/author.xml b/P5/Source/Specs/author.xml index cb9631791c..ef98008da4 100644 --- a/P5/Source/Specs/author.xml +++ b/P5/Source/Specs/author.xml @@ -1,4 +1,6 @@ - + + + author autor/a auteur diff --git a/P5/Source/Specs/authority.xml b/P5/Source/Specs/authority.xml index cf06e094f6..4f269ce281 100644 --- a/P5/Source/Specs/authority.xml +++ b/P5/Source/Specs/authority.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/availability.xml b/P5/Source/Specs/availability.xml index 461e029701..f6fa6a0b0d 100644 --- a/P5/Source/Specs/availability.xml +++ b/P5/Source/Specs/availability.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/back.xml b/P5/Source/Specs/back.xml index aeca2168e9..9453ec0cc2 100644 --- a/P5/Source/Specs/back.xml +++ b/P5/Source/Specs/back.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/bibl.xml b/P5/Source/Specs/bibl.xml index 3a6df7d3f7..89eb998995 100644 --- a/P5/Source/Specs/bibl.xml +++ b/P5/Source/Specs/bibl.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/biblFull.xml b/P5/Source/Specs/biblFull.xml index 0210fdb6a9..de359d2876 100644 --- a/P5/Source/Specs/biblFull.xml +++ b/P5/Source/Specs/biblFull.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/biblScope.xml b/P5/Source/Specs/biblScope.xml index a4b425029d..3682ffd5b1 100644 --- a/P5/Source/Specs/biblScope.xml +++ b/P5/Source/Specs/biblScope.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/biblStruct.xml b/P5/Source/Specs/biblStruct.xml index 1d011834d7..36ec4f8b7a 100644 --- a/P5/Source/Specs/biblStruct.xml +++ b/P5/Source/Specs/biblStruct.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/bicond.xml b/P5/Source/Specs/bicond.xml index 86d96ebb67..5059a0a142 100644 --- a/P5/Source/Specs/bicond.xml +++ b/P5/Source/Specs/bicond.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/binary.xml b/P5/Source/Specs/binary.xml index b9be6e9697..919333114f 100644 --- a/P5/Source/Specs/binary.xml +++ b/P5/Source/Specs/binary.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/binaryObject.xml b/P5/Source/Specs/binaryObject.xml index f205dc4dfb..88ce086b59 100644 --- a/P5/Source/Specs/binaryObject.xml +++ b/P5/Source/Specs/binaryObject.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/binding.xml b/P5/Source/Specs/binding.xml index a195459dcf..4bbdf2f2f6 100644 --- a/P5/Source/Specs/binding.xml +++ b/P5/Source/Specs/binding.xml @@ -1,4 +1,6 @@ - + + + binding reliure contains a description of one binding, i.e. type of covering, boards, diff --git a/P5/Source/Specs/bindingDesc.xml b/P5/Source/Specs/bindingDesc.xml index 96fcfb40f3..5af5063ac9 100644 --- a/P5/Source/Specs/bindingDesc.xml +++ b/P5/Source/Specs/bindingDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/birth.xml b/P5/Source/Specs/birth.xml index 897232af4b..c42885dd3e 100644 --- a/P5/Source/Specs/birth.xml +++ b/P5/Source/Specs/birth.xml @@ -1,4 +1,6 @@ - + + + birth naissance contains information about a person's birth, such as its date and place. diff --git a/P5/Source/Specs/bloc.xml b/P5/Source/Specs/bloc.xml index 2746d5b0c8..81f5354fee 100644 --- a/P5/Source/Specs/bloc.xml +++ b/P5/Source/Specs/bloc.xml @@ -1,4 +1,6 @@ - + + + bloc bloc contains the name of a geo-political unit consisting of two or more nation states or diff --git a/P5/Source/Specs/body.xml b/P5/Source/Specs/body.xml index 8cd927de7d..d997b57c2a 100644 --- a/P5/Source/Specs/body.xml +++ b/P5/Source/Specs/body.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/broadcast.xml b/P5/Source/Specs/broadcast.xml index d18684b500..0c0d7d2f26 100644 --- a/P5/Source/Specs/broadcast.xml +++ b/P5/Source/Specs/broadcast.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/byline.xml b/P5/Source/Specs/byline.xml index 7791edd8a2..7a3caf9f0e 100644 --- a/P5/Source/Specs/byline.xml +++ b/P5/Source/Specs/byline.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/c.xml b/P5/Source/Specs/c.xml index f4c4d54a59..5151bf6108 100644 --- a/P5/Source/Specs/c.xml +++ b/P5/Source/Specs/c.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/cRefPattern.xml b/P5/Source/Specs/cRefPattern.xml index dc58b6f9f9..32cbe8280c 100644 --- a/P5/Source/Specs/cRefPattern.xml +++ b/P5/Source/Specs/cRefPattern.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/caesura.xml b/P5/Source/Specs/caesura.xml index 198a841591..2e4769ff90 100644 --- a/P5/Source/Specs/caesura.xml +++ b/P5/Source/Specs/caesura.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/calendar.xml b/P5/Source/Specs/calendar.xml index 1d27b8a48f..1795e00f7e 100644 --- a/P5/Source/Specs/calendar.xml +++ b/P5/Source/Specs/calendar.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/calendarDesc.xml b/P5/Source/Specs/calendarDesc.xml index c7ed2b1e1a..5b43b3eab7 100644 --- a/P5/Source/Specs/calendarDesc.xml +++ b/P5/Source/Specs/calendarDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/camera.xml b/P5/Source/Specs/camera.xml index 1b9448cef2..362ee40d6d 100644 --- a/P5/Source/Specs/camera.xml +++ b/P5/Source/Specs/camera.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/caption.xml b/P5/Source/Specs/caption.xml index 4be4953868..a4cf82f135 100644 --- a/P5/Source/Specs/caption.xml +++ b/P5/Source/Specs/caption.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/case.xml b/P5/Source/Specs/case.xml index 449e3c61fe..1e84cdb86a 100644 --- a/P5/Source/Specs/case.xml +++ b/P5/Source/Specs/case.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/castGroup.xml b/P5/Source/Specs/castGroup.xml index 104ff6e9ca..420fad30d0 100644 --- a/P5/Source/Specs/castGroup.xml +++ b/P5/Source/Specs/castGroup.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/castItem.xml b/P5/Source/Specs/castItem.xml index 9dcf03c2df..cb38befe7b 100644 --- a/P5/Source/Specs/castItem.xml +++ b/P5/Source/Specs/castItem.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/castList.xml b/P5/Source/Specs/castList.xml index 30081fa397..0c6db4b5d7 100644 --- a/P5/Source/Specs/castList.xml +++ b/P5/Source/Specs/castList.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/catDesc.xml b/P5/Source/Specs/catDesc.xml index d94f20bf5c..7c5eee627d 100644 --- a/P5/Source/Specs/catDesc.xml +++ b/P5/Source/Specs/catDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/catRef.xml b/P5/Source/Specs/catRef.xml index dd50289688..dc1d662095 100644 --- a/P5/Source/Specs/catRef.xml +++ b/P5/Source/Specs/catRef.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/catchwords.xml b/P5/Source/Specs/catchwords.xml index 5db3ac3d98..0dea6a3fc2 100644 --- a/P5/Source/Specs/catchwords.xml +++ b/P5/Source/Specs/catchwords.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/category.xml b/P5/Source/Specs/category.xml index add5e24715..c65549e62f 100644 --- a/P5/Source/Specs/category.xml +++ b/P5/Source/Specs/category.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/cb.xml b/P5/Source/Specs/cb.xml index 8733f949aa..ad01b8ce5c 100644 --- a/P5/Source/Specs/cb.xml +++ b/P5/Source/Specs/cb.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/cell.xml b/P5/Source/Specs/cell.xml index c5b8e783a5..194b1fdcbc 100644 --- a/P5/Source/Specs/cell.xml +++ b/P5/Source/Specs/cell.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/certainty.xml b/P5/Source/Specs/certainty.xml index cc4245e8bf..dbab1a7661 100644 --- a/P5/Source/Specs/certainty.xml +++ b/P5/Source/Specs/certainty.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/change.xml b/P5/Source/Specs/change.xml index 41432e8858..6a0dc87069 100644 --- a/P5/Source/Specs/change.xml +++ b/P5/Source/Specs/change.xml @@ -1,4 +1,6 @@ - + + + change Änderung 変更 diff --git a/P5/Source/Specs/channel.xml b/P5/Source/Specs/channel.xml index cbc26f9f1e..420031e21e 100644 --- a/P5/Source/Specs/channel.xml +++ b/P5/Source/Specs/channel.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/char.xml b/P5/Source/Specs/char.xml index 0ee8e4a39a..b0af7995d8 100644 --- a/P5/Source/Specs/char.xml +++ b/P5/Source/Specs/char.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/charDecl.xml b/P5/Source/Specs/charDecl.xml index cb28b4f15c..03f34fab08 100644 --- a/P5/Source/Specs/charDecl.xml +++ b/P5/Source/Specs/charDecl.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/choice.xml b/P5/Source/Specs/choice.xml index 5bd682b7b7..9cd79835c8 100644 --- a/P5/Source/Specs/choice.xml +++ b/P5/Source/Specs/choice.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/cit.xml b/P5/Source/Specs/cit.xml index a91da2eba5..7c846a1267 100644 --- a/P5/Source/Specs/cit.xml +++ b/P5/Source/Specs/cit.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/citeData.xml b/P5/Source/Specs/citeData.xml index 765b2a6745..1a526b59d5 100644 --- a/P5/Source/Specs/citeData.xml +++ b/P5/Source/Specs/citeData.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/citeStructure.xml b/P5/Source/Specs/citeStructure.xml index 1267156072..2992cab228 100644 --- a/P5/Source/Specs/citeStructure.xml +++ b/P5/Source/Specs/citeStructure.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/citedRange.xml b/P5/Source/Specs/citedRange.xml index 96ab927cc7..658a506ce0 100644 --- a/P5/Source/Specs/citedRange.xml +++ b/P5/Source/Specs/citedRange.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/cl.xml b/P5/Source/Specs/cl.xml index ffb6558a25..2b5d42838a 100644 --- a/P5/Source/Specs/cl.xml +++ b/P5/Source/Specs/cl.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/classCode.xml b/P5/Source/Specs/classCode.xml index 99a61f1f23..0159b376af 100644 --- a/P5/Source/Specs/classCode.xml +++ b/P5/Source/Specs/classCode.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/classDecl.xml b/P5/Source/Specs/classDecl.xml index 324705b85f..fedc67a79b 100644 --- a/P5/Source/Specs/classDecl.xml +++ b/P5/Source/Specs/classDecl.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/classRef.xml b/P5/Source/Specs/classRef.xml index 2b4ed3ae86..c54c02cd8b 100644 --- a/P5/Source/Specs/classRef.xml +++ b/P5/Source/Specs/classRef.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/classSpec.xml b/P5/Source/Specs/classSpec.xml index 35b92073eb..bd2ba92970 100644 --- a/P5/Source/Specs/classSpec.xml +++ b/P5/Source/Specs/classSpec.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/classes.xml b/P5/Source/Specs/classes.xml index 5ae286a64a..600a936395 100644 --- a/P5/Source/Specs/classes.xml +++ b/P5/Source/Specs/classes.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/climate.xml b/P5/Source/Specs/climate.xml index 1f8409cdb6..28422e2901 100644 --- a/P5/Source/Specs/climate.xml +++ b/P5/Source/Specs/climate.xml @@ -1,4 +1,6 @@ - + + + climate climat contains information about the physical climate of a place. diff --git a/P5/Source/Specs/closer.xml b/P5/Source/Specs/closer.xml index d62ca55468..7cf7854dc8 100644 --- a/P5/Source/Specs/closer.xml +++ b/P5/Source/Specs/closer.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/code.xml b/P5/Source/Specs/code.xml index 4d3a193ed8..c522f2d104 100644 --- a/P5/Source/Specs/code.xml +++ b/P5/Source/Specs/code.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/collation.xml b/P5/Source/Specs/collation.xml index 0763b55d71..9078d3d630 100644 --- a/P5/Source/Specs/collation.xml +++ b/P5/Source/Specs/collation.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/collection.xml b/P5/Source/Specs/collection.xml index 1b2a33d3b9..7787d7a429 100644 --- a/P5/Source/Specs/collection.xml +++ b/P5/Source/Specs/collection.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/colloc.xml b/P5/Source/Specs/colloc.xml index d6ff1f2402..f08d542912 100644 --- a/P5/Source/Specs/colloc.xml +++ b/P5/Source/Specs/colloc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/colophon.xml b/P5/Source/Specs/colophon.xml index 023ef2c58a..e595695616 100644 --- a/P5/Source/Specs/colophon.xml +++ b/P5/Source/Specs/colophon.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/cond.xml b/P5/Source/Specs/cond.xml index 075eb6604b..651c00877b 100644 --- a/P5/Source/Specs/cond.xml +++ b/P5/Source/Specs/cond.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/condition.xml b/P5/Source/Specs/condition.xml index b8557cf82f..062ff74942 100644 --- a/P5/Source/Specs/condition.xml +++ b/P5/Source/Specs/condition.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/constitution.xml b/P5/Source/Specs/constitution.xml index 1a93567456..7db2fdf463 100644 --- a/P5/Source/Specs/constitution.xml +++ b/P5/Source/Specs/constitution.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/constraint.xml b/P5/Source/Specs/constraint.xml index 0fed8d29f4..a174228e3e 100644 --- a/P5/Source/Specs/constraint.xml +++ b/P5/Source/Specs/constraint.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/constraintSpec.xml b/P5/Source/Specs/constraintSpec.xml index 730a21006f..d4372507c7 100644 --- a/P5/Source/Specs/constraintSpec.xml +++ b/P5/Source/Specs/constraintSpec.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/content.xml b/P5/Source/Specs/content.xml index 0a16393c33..3fa014b639 100644 --- a/P5/Source/Specs/content.xml +++ b/P5/Source/Specs/content.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/conversion.xml b/P5/Source/Specs/conversion.xml index baa605de6c..3978f6164a 100644 --- a/P5/Source/Specs/conversion.xml +++ b/P5/Source/Specs/conversion.xml @@ -1,4 +1,6 @@ - + + + defines how to calculate one unit of measure in terms of another. diff --git a/P5/Source/Specs/corr.xml b/P5/Source/Specs/corr.xml index 18a41fe203..6625d423f2 100644 --- a/P5/Source/Specs/corr.xml +++ b/P5/Source/Specs/corr.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/correction.xml b/P5/Source/Specs/correction.xml index 986ff0c72f..7544d27ae4 100644 --- a/P5/Source/Specs/correction.xml +++ b/P5/Source/Specs/correction.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/correspAction.xml b/P5/Source/Specs/correspAction.xml index 63b7665597..e984573497 100644 --- a/P5/Source/Specs/correspAction.xml +++ b/P5/Source/Specs/correspAction.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/correspContext.xml b/P5/Source/Specs/correspContext.xml index 95725f99c8..3dbdfa6896 100644 --- a/P5/Source/Specs/correspContext.xml +++ b/P5/Source/Specs/correspContext.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/correspDesc.xml b/P5/Source/Specs/correspDesc.xml index 61185f249b..f34d1f8252 100644 --- a/P5/Source/Specs/correspDesc.xml +++ b/P5/Source/Specs/correspDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/country.xml b/P5/Source/Specs/country.xml index 5261f47454..54940fbeee 100644 --- a/P5/Source/Specs/country.xml +++ b/P5/Source/Specs/country.xml @@ -1,4 +1,6 @@ - + + + country pays contains the name of a geo-political unit, such as a nation, country, colony, or diff --git a/P5/Source/Specs/creation.xml b/P5/Source/Specs/creation.xml index 0d327c884c..2d67392cbd 100644 --- a/P5/Source/Specs/creation.xml +++ b/P5/Source/Specs/creation.xml @@ -1,4 +1,6 @@ - + + + creation création Entstehung diff --git a/P5/Source/Specs/custEvent.xml b/P5/Source/Specs/custEvent.xml index 24d4f5e63e..c95bf23258 100644 --- a/P5/Source/Specs/custEvent.xml +++ b/P5/Source/Specs/custEvent.xml @@ -1,4 +1,6 @@ - + + + custodial event 보관 사건 diff --git a/P5/Source/Specs/custodialHist.xml b/P5/Source/Specs/custodialHist.xml index 63a149864d..8c45b16d06 100644 --- a/P5/Source/Specs/custodialHist.xml +++ b/P5/Source/Specs/custodialHist.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/damage.xml b/P5/Source/Specs/damage.xml index 9a55399d2f..dbcdf306b8 100644 --- a/P5/Source/Specs/damage.xml +++ b/P5/Source/Specs/damage.xml @@ -1,4 +1,6 @@ - + + + damage 当該文献におけるテキストの損傷部分を示す。 dommage diff --git a/P5/Source/Specs/damageSpan.xml b/P5/Source/Specs/damageSpan.xml index 39c84ff87b..78adc5279b 100644 --- a/P5/Source/Specs/damageSpan.xml +++ b/P5/Source/Specs/damageSpan.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/dataFacet.xml b/P5/Source/Specs/dataFacet.xml index 6954775c24..44799e9694 100644 --- a/P5/Source/Specs/dataFacet.xml +++ b/P5/Source/Specs/dataFacet.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/dataRef.xml b/P5/Source/Specs/dataRef.xml index 44b85684e0..5de6997ea0 100644 --- a/P5/Source/Specs/dataRef.xml +++ b/P5/Source/Specs/dataRef.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/dataSpec.xml b/P5/Source/Specs/dataSpec.xml index 4cbf602afc..d8c90e46c1 100644 --- a/P5/Source/Specs/dataSpec.xml +++ b/P5/Source/Specs/dataSpec.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/datatype.xml b/P5/Source/Specs/datatype.xml index 5cda5dca0b..2277562fd1 100644 --- a/P5/Source/Specs/datatype.xml +++ b/P5/Source/Specs/datatype.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/date.xml b/P5/Source/Specs/date.xml index ea67955764..709566274b 100644 --- a/P5/Source/Specs/date.xml +++ b/P5/Source/Specs/date.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/dateline.xml b/P5/Source/Specs/dateline.xml index 7024c733a2..40f6626e0e 100644 --- a/P5/Source/Specs/dateline.xml +++ b/P5/Source/Specs/dateline.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/death.xml b/P5/Source/Specs/death.xml index 2eea349840..0afa055d90 100644 --- a/P5/Source/Specs/death.xml +++ b/P5/Source/Specs/death.xml @@ -1,4 +1,6 @@ - + + + death décès contains information about a person's death, such as its date and place. diff --git a/P5/Source/Specs/decoDesc.xml b/P5/Source/Specs/decoDesc.xml index ff67a4a0dd..13a9317457 100644 --- a/P5/Source/Specs/decoDesc.xml +++ b/P5/Source/Specs/decoDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/decoNote.xml b/P5/Source/Specs/decoNote.xml index 0b1670c677..5883c93015 100644 --- a/P5/Source/Specs/decoNote.xml +++ b/P5/Source/Specs/decoNote.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/def.xml b/P5/Source/Specs/def.xml index bc45f93afe..606675b53a 100644 --- a/P5/Source/Specs/def.xml +++ b/P5/Source/Specs/def.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/default.xml b/P5/Source/Specs/default.xml index 2abea157b0..feaa206473 100644 --- a/P5/Source/Specs/default.xml +++ b/P5/Source/Specs/default.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/defaultVal.xml b/P5/Source/Specs/defaultVal.xml index 5d7aa6381b..d45c68a302 100644 --- a/P5/Source/Specs/defaultVal.xml +++ b/P5/Source/Specs/defaultVal.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/del.xml b/P5/Source/Specs/del.xml index 921f09ece1..0cafd9eeae 100644 --- a/P5/Source/Specs/del.xml +++ b/P5/Source/Specs/del.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/delSpan.xml b/P5/Source/Specs/delSpan.xml index bb11e0a97e..fbeea67ab8 100644 --- a/P5/Source/Specs/delSpan.xml +++ b/P5/Source/Specs/delSpan.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/depth.xml b/P5/Source/Specs/depth.xml index d127fc9cfb..d422b8a927 100644 --- a/P5/Source/Specs/depth.xml +++ b/P5/Source/Specs/depth.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/derivation.xml b/P5/Source/Specs/derivation.xml index 1f060134da..2bd0f6439e 100644 --- a/P5/Source/Specs/derivation.xml +++ b/P5/Source/Specs/derivation.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/desc.xml b/P5/Source/Specs/desc.xml index b83b04119f..456113e9ab 100644 --- a/P5/Source/Specs/desc.xml +++ b/P5/Source/Specs/desc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/dictScrap.xml b/P5/Source/Specs/dictScrap.xml index 035e180c62..19840ec46c 100644 --- a/P5/Source/Specs/dictScrap.xml +++ b/P5/Source/Specs/dictScrap.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/dim.xml b/P5/Source/Specs/dim.xml index 3b7b15c68b..a9454860f7 100644 --- a/P5/Source/Specs/dim.xml +++ b/P5/Source/Specs/dim.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/dimensions.xml b/P5/Source/Specs/dimensions.xml index af40664086..52b4d0dfd5 100644 --- a/P5/Source/Specs/dimensions.xml +++ b/P5/Source/Specs/dimensions.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/distinct.xml b/P5/Source/Specs/distinct.xml index 8b4a38ebac..1072eb9b40 100644 --- a/P5/Source/Specs/distinct.xml +++ b/P5/Source/Specs/distinct.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/distributor.xml b/P5/Source/Specs/distributor.xml index 0f6497090b..1cb8a7bbb7 100644 --- a/P5/Source/Specs/distributor.xml +++ b/P5/Source/Specs/distributor.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/district.xml b/P5/Source/Specs/district.xml index d4a370db59..b5d07dfcb5 100644 --- a/P5/Source/Specs/district.xml +++ b/P5/Source/Specs/district.xml @@ -1,4 +1,6 @@ - + + + district district contains the name of any kind of subdivision of a settlement, such as a parish, ward, or other administrative or geographic unit. diff --git a/P5/Source/Specs/div.xml b/P5/Source/Specs/div.xml index 368d51c391..39e8c989b9 100644 --- a/P5/Source/Specs/div.xml +++ b/P5/Source/Specs/div.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/div1.xml b/P5/Source/Specs/div1.xml index 1ed1c0d817..7200b5b6e5 100644 --- a/P5/Source/Specs/div1.xml +++ b/P5/Source/Specs/div1.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/div2.xml b/P5/Source/Specs/div2.xml index b569201c71..00fc2e827d 100644 --- a/P5/Source/Specs/div2.xml +++ b/P5/Source/Specs/div2.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/div3.xml b/P5/Source/Specs/div3.xml index 38126a40fd..0ef90c0416 100644 --- a/P5/Source/Specs/div3.xml +++ b/P5/Source/Specs/div3.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/div4.xml b/P5/Source/Specs/div4.xml index 00e3a63e16..77098e55f3 100644 --- a/P5/Source/Specs/div4.xml +++ b/P5/Source/Specs/div4.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/div5.xml b/P5/Source/Specs/div5.xml index 98ffb36330..8de091464d 100644 --- a/P5/Source/Specs/div5.xml +++ b/P5/Source/Specs/div5.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/div6.xml b/P5/Source/Specs/div6.xml index effa7143f1..8a106356c2 100644 --- a/P5/Source/Specs/div6.xml +++ b/P5/Source/Specs/div6.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/div7.xml b/P5/Source/Specs/div7.xml index 76cd431222..7c12ef44ff 100644 --- a/P5/Source/Specs/div7.xml +++ b/P5/Source/Specs/div7.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/divGen.xml b/P5/Source/Specs/divGen.xml index f0fc89a123..b07284e1ea 100644 --- a/P5/Source/Specs/divGen.xml +++ b/P5/Source/Specs/divGen.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/docAuthor.xml b/P5/Source/Specs/docAuthor.xml index 974f175a18..ebcb1fa30b 100644 --- a/P5/Source/Specs/docAuthor.xml +++ b/P5/Source/Specs/docAuthor.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/docDate.xml b/P5/Source/Specs/docDate.xml index a1762ddae6..84d3bc7db5 100644 --- a/P5/Source/Specs/docDate.xml +++ b/P5/Source/Specs/docDate.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/docEdition.xml b/P5/Source/Specs/docEdition.xml index f7b516b48b..ca9b1a3a18 100644 --- a/P5/Source/Specs/docEdition.xml +++ b/P5/Source/Specs/docEdition.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/docImprint.xml b/P5/Source/Specs/docImprint.xml index 2a7e5ffbb6..04680f550a 100644 --- a/P5/Source/Specs/docImprint.xml +++ b/P5/Source/Specs/docImprint.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/docTitle.xml b/P5/Source/Specs/docTitle.xml index 4ba9ff0707..6d6e15bdac 100644 --- a/P5/Source/Specs/docTitle.xml +++ b/P5/Source/Specs/docTitle.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/domain.xml b/P5/Source/Specs/domain.xml index 36de7e0537..75b7a63b1c 100644 --- a/P5/Source/Specs/domain.xml +++ b/P5/Source/Specs/domain.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/eLeaf.xml b/P5/Source/Specs/eLeaf.xml index dd2ababbb9..3824945b89 100644 --- a/P5/Source/Specs/eLeaf.xml +++ b/P5/Source/Specs/eLeaf.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/eTree.xml b/P5/Source/Specs/eTree.xml index 2db1826f14..c5ed6fc3d7 100644 --- a/P5/Source/Specs/eTree.xml +++ b/P5/Source/Specs/eTree.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/edition.xml b/P5/Source/Specs/edition.xml index ad9ef780be..e97f543484 100644 --- a/P5/Source/Specs/edition.xml +++ b/P5/Source/Specs/edition.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/editionStmt.xml b/P5/Source/Specs/editionStmt.xml index e77529a1c5..0361735562 100644 --- a/P5/Source/Specs/editionStmt.xml +++ b/P5/Source/Specs/editionStmt.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/editor.xml b/P5/Source/Specs/editor.xml index a7b4b07ec9..20e8a0fba4 100644 --- a/P5/Source/Specs/editor.xml +++ b/P5/Source/Specs/editor.xml @@ -1,4 +1,6 @@ - + + + contains a secondary statement of responsibility for a bibliographic item, for example the name of an individual, institution or organization, (or of several such) acting as editor, compiler, diff --git a/P5/Source/Specs/editorialDecl.xml b/P5/Source/Specs/editorialDecl.xml index ef6caf312b..99fadb634a 100644 --- a/P5/Source/Specs/editorialDecl.xml +++ b/P5/Source/Specs/editorialDecl.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/education.xml b/P5/Source/Specs/education.xml index 49f0f7bd33..6e02651045 100644 --- a/P5/Source/Specs/education.xml +++ b/P5/Source/Specs/education.xml @@ -1,4 +1,6 @@ - + + + education éducation contains a description of the educational experience of a person. diff --git a/P5/Source/Specs/eg.xml b/P5/Source/Specs/eg.xml index a866fb5d9d..ff6fc2ccc4 100644 --- a/P5/Source/Specs/eg.xml +++ b/P5/Source/Specs/eg.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/egXML.xml b/P5/Source/Specs/egXML.xml index e0889cfd6c..a29290d82e 100644 --- a/P5/Source/Specs/egXML.xml +++ b/P5/Source/Specs/egXML.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/elementRef.xml b/P5/Source/Specs/elementRef.xml index ee3077650b..95babaa2a4 100644 --- a/P5/Source/Specs/elementRef.xml +++ b/P5/Source/Specs/elementRef.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/elementSpec.xml b/P5/Source/Specs/elementSpec.xml index 0c065a5d4f..ca33f9e5e6 100644 --- a/P5/Source/Specs/elementSpec.xml +++ b/P5/Source/Specs/elementSpec.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/ellipsis.xml b/P5/Source/Specs/ellipsis.xml index f9e8e31dfb..6299c4932a 100644 --- a/P5/Source/Specs/ellipsis.xml +++ b/P5/Source/Specs/ellipsis.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/email.xml b/P5/Source/Specs/email.xml index 75c9d9058d..c39c4ea84e 100644 --- a/P5/Source/Specs/email.xml +++ b/P5/Source/Specs/email.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/emph.xml b/P5/Source/Specs/emph.xml index 22a625864e..d918421d13 100644 --- a/P5/Source/Specs/emph.xml +++ b/P5/Source/Specs/emph.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/empty.xml b/P5/Source/Specs/empty.xml index daccd52c84..663ba5de5b 100644 --- a/P5/Source/Specs/empty.xml +++ b/P5/Source/Specs/empty.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/encodingDesc.xml b/P5/Source/Specs/encodingDesc.xml index 5f393b68a9..52a8b2eb94 100644 --- a/P5/Source/Specs/encodingDesc.xml +++ b/P5/Source/Specs/encodingDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/entry.xml b/P5/Source/Specs/entry.xml index c93b53d4c6..d2a6cb13b6 100644 --- a/P5/Source/Specs/entry.xml +++ b/P5/Source/Specs/entry.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/entryFree.xml b/P5/Source/Specs/entryFree.xml index 93613ffa7c..a88b644654 100644 --- a/P5/Source/Specs/entryFree.xml +++ b/P5/Source/Specs/entryFree.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/epigraph.xml b/P5/Source/Specs/epigraph.xml index 0b9e75656f..0bf803b7fa 100644 --- a/P5/Source/Specs/epigraph.xml +++ b/P5/Source/Specs/epigraph.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/epilogue.xml b/P5/Source/Specs/epilogue.xml index 6d8e6feeee..7575f42858 100644 --- a/P5/Source/Specs/epilogue.xml +++ b/P5/Source/Specs/epilogue.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/equipment.xml b/P5/Source/Specs/equipment.xml index dd63dbdd67..8aacead70f 100644 --- a/P5/Source/Specs/equipment.xml +++ b/P5/Source/Specs/equipment.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/equiv.xml b/P5/Source/Specs/equiv.xml index 5109b7e769..f52b301199 100644 --- a/P5/Source/Specs/equiv.xml +++ b/P5/Source/Specs/equiv.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/etym.xml b/P5/Source/Specs/etym.xml index e4c5a9816b..df05226923 100644 --- a/P5/Source/Specs/etym.xml +++ b/P5/Source/Specs/etym.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/event.xml b/P5/Source/Specs/event.xml index 51979fb276..1902d9df0d 100644 --- a/P5/Source/Specs/event.xml +++ b/P5/Source/Specs/event.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/eventName.xml b/P5/Source/Specs/eventName.xml index fd76bcc327..16a33b74f2 100644 --- a/P5/Source/Specs/eventName.xml +++ b/P5/Source/Specs/eventName.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/ex.xml b/P5/Source/Specs/ex.xml index fd9315b5d3..2eea604d73 100644 --- a/P5/Source/Specs/ex.xml +++ b/P5/Source/Specs/ex.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/exemplum.xml b/P5/Source/Specs/exemplum.xml index 5bb19cb7d0..84bd2bbdda 100644 --- a/P5/Source/Specs/exemplum.xml +++ b/P5/Source/Specs/exemplum.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/expan.xml b/P5/Source/Specs/expan.xml index 4602e558e1..f892e1b14f 100644 --- a/P5/Source/Specs/expan.xml +++ b/P5/Source/Specs/expan.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/explicit.xml b/P5/Source/Specs/explicit.xml index f04a365de5..dce7ce320d 100644 --- a/P5/Source/Specs/explicit.xml +++ b/P5/Source/Specs/explicit.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/extent.xml b/P5/Source/Specs/extent.xml index af9ea8b811..c702bf7ba8 100644 --- a/P5/Source/Specs/extent.xml +++ b/P5/Source/Specs/extent.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/f.xml b/P5/Source/Specs/f.xml index fc21582245..18ca1fba66 100644 --- a/P5/Source/Specs/f.xml +++ b/P5/Source/Specs/f.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/fDecl.xml b/P5/Source/Specs/fDecl.xml index d31d8ec638..5e94d789f9 100644 --- a/P5/Source/Specs/fDecl.xml +++ b/P5/Source/Specs/fDecl.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/fDescr.xml b/P5/Source/Specs/fDescr.xml index 0d24fff402..bffcee4ac8 100644 --- a/P5/Source/Specs/fDescr.xml +++ b/P5/Source/Specs/fDescr.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/fLib.xml b/P5/Source/Specs/fLib.xml index c2a9514f1f..b7645f61c3 100644 --- a/P5/Source/Specs/fLib.xml +++ b/P5/Source/Specs/fLib.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/facsimile.xml b/P5/Source/Specs/facsimile.xml index 5adeacaa4e..a97e0a346b 100644 --- a/P5/Source/Specs/facsimile.xml +++ b/P5/Source/Specs/facsimile.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/factuality.xml b/P5/Source/Specs/factuality.xml index b505238511..8a664c5fa2 100644 --- a/P5/Source/Specs/factuality.xml +++ b/P5/Source/Specs/factuality.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/faith.xml b/P5/Source/Specs/faith.xml index d6dc13905e..196da017d8 100644 --- a/P5/Source/Specs/faith.xml +++ b/P5/Source/Specs/faith.xml @@ -1,4 +1,6 @@ - + + + faith religion specifies the faith, religion, or belief set of a person. diff --git a/P5/Source/Specs/figDesc.xml b/P5/Source/Specs/figDesc.xml index ff42825bc6..d6c79130db 100644 --- a/P5/Source/Specs/figDesc.xml +++ b/P5/Source/Specs/figDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/figure.xml b/P5/Source/Specs/figure.xml index bba891c05e..f61c5c06d7 100644 --- a/P5/Source/Specs/figure.xml +++ b/P5/Source/Specs/figure.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/fileDesc.xml b/P5/Source/Specs/fileDesc.xml index 71817e08fa..c32b869120 100644 --- a/P5/Source/Specs/fileDesc.xml +++ b/P5/Source/Specs/fileDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/filiation.xml b/P5/Source/Specs/filiation.xml index 8d34706eac..213c38dbb1 100644 --- a/P5/Source/Specs/filiation.xml +++ b/P5/Source/Specs/filiation.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/finalRubric.xml b/P5/Source/Specs/finalRubric.xml index 4698e6e34e..d36766bfe3 100644 --- a/P5/Source/Specs/finalRubric.xml +++ b/P5/Source/Specs/finalRubric.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/floatingText.xml b/P5/Source/Specs/floatingText.xml index b54546da6d..f97cec2d38 100644 --- a/P5/Source/Specs/floatingText.xml +++ b/P5/Source/Specs/floatingText.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/floruit.xml b/P5/Source/Specs/floruit.xml index 5f01cb680d..9e7a14f539 100644 --- a/P5/Source/Specs/floruit.xml +++ b/P5/Source/Specs/floruit.xml @@ -1,4 +1,6 @@ - + + + floruit période d'activité contains information about a person's period of activity. diff --git a/P5/Source/Specs/foliation.xml b/P5/Source/Specs/foliation.xml index f4ecf6e06e..235e69008a 100644 --- a/P5/Source/Specs/foliation.xml +++ b/P5/Source/Specs/foliation.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/foreign.xml b/P5/Source/Specs/foreign.xml index 9eeb2fd526..fc9247d40a 100644 --- a/P5/Source/Specs/foreign.xml +++ b/P5/Source/Specs/foreign.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/forename.xml b/P5/Source/Specs/forename.xml index 9b24e9ace0..1877c1f7cf 100644 --- a/P5/Source/Specs/forename.xml +++ b/P5/Source/Specs/forename.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/forest.xml b/P5/Source/Specs/forest.xml index 8b2855b64c..124df837a2 100644 --- a/P5/Source/Specs/forest.xml +++ b/P5/Source/Specs/forest.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/form.xml b/P5/Source/Specs/form.xml index d52cb803ab..7745d6b013 100644 --- a/P5/Source/Specs/form.xml +++ b/P5/Source/Specs/form.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/formula.xml b/P5/Source/Specs/formula.xml index 00c871f755..d1f3b6e0ee 100644 --- a/P5/Source/Specs/formula.xml +++ b/P5/Source/Specs/formula.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/front.xml b/P5/Source/Specs/front.xml index 06bef4f50e..f2b5eea61e 100644 --- a/P5/Source/Specs/front.xml +++ b/P5/Source/Specs/front.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/fs.xml b/P5/Source/Specs/fs.xml index c62b4e84fb..6298a58894 100644 --- a/P5/Source/Specs/fs.xml +++ b/P5/Source/Specs/fs.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/fsConstraints.xml b/P5/Source/Specs/fsConstraints.xml index 1062e69845..fdb36a3d17 100644 --- a/P5/Source/Specs/fsConstraints.xml +++ b/P5/Source/Specs/fsConstraints.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/fsDecl.xml b/P5/Source/Specs/fsDecl.xml index 13ce5aacb5..80824faec2 100644 --- a/P5/Source/Specs/fsDecl.xml +++ b/P5/Source/Specs/fsDecl.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/fsDescr.xml b/P5/Source/Specs/fsDescr.xml index 3906c7054a..8412c4cc63 100644 --- a/P5/Source/Specs/fsDescr.xml +++ b/P5/Source/Specs/fsDescr.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/fsdDecl.xml b/P5/Source/Specs/fsdDecl.xml index 96cd1f1bbd..f925669f9f 100644 --- a/P5/Source/Specs/fsdDecl.xml +++ b/P5/Source/Specs/fsdDecl.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/fsdLink.xml b/P5/Source/Specs/fsdLink.xml index 0d13671f7f..beba71bcd0 100644 --- a/P5/Source/Specs/fsdLink.xml +++ b/P5/Source/Specs/fsdLink.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/funder.xml b/P5/Source/Specs/funder.xml index ced649f52f..83425147ff 100644 --- a/P5/Source/Specs/funder.xml +++ b/P5/Source/Specs/funder.xml @@ -1,4 +1,6 @@ - + + + funding body financeur 재정 지원 조직체 diff --git a/P5/Source/Specs/fvLib.xml b/P5/Source/Specs/fvLib.xml index 3003d9959d..928faec915 100644 --- a/P5/Source/Specs/fvLib.xml +++ b/P5/Source/Specs/fvLib.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/fw.xml b/P5/Source/Specs/fw.xml index e0689bf233..37927f3111 100644 --- a/P5/Source/Specs/fw.xml +++ b/P5/Source/Specs/fw.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/g.xml b/P5/Source/Specs/g.xml index b7ee6383f2..96528f1c51 100644 --- a/P5/Source/Specs/g.xml +++ b/P5/Source/Specs/g.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/gap.xml b/P5/Source/Specs/gap.xml index ef715fd3c7..216734fe88 100644 --- a/P5/Source/Specs/gap.xml +++ b/P5/Source/Specs/gap.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/gb.xml b/P5/Source/Specs/gb.xml index 44b80bc33b..fb2d89919a 100644 --- a/P5/Source/Specs/gb.xml +++ b/P5/Source/Specs/gb.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/gen.xml b/P5/Source/Specs/gen.xml index f3a197c8ae..9c3d63e449 100644 --- a/P5/Source/Specs/gen.xml +++ b/P5/Source/Specs/gen.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/genName.xml b/P5/Source/Specs/genName.xml index 84552c75ff..b2cbfa4e34 100644 --- a/P5/Source/Specs/genName.xml +++ b/P5/Source/Specs/genName.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/gender.xml b/P5/Source/Specs/gender.xml index a33ae2075a..627f37a24d 100644 --- a/P5/Source/Specs/gender.xml +++ b/P5/Source/Specs/gender.xml @@ -1,4 +1,6 @@ - + + + gender specifies the gender identity of a person, persona, or character. especifica la identidad de género de una persona. diff --git a/P5/Source/Specs/geo.xml b/P5/Source/Specs/geo.xml index 6b431e97aa..75cb35e44f 100644 --- a/P5/Source/Specs/geo.xml +++ b/P5/Source/Specs/geo.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/geoDecl.xml b/P5/Source/Specs/geoDecl.xml index f15b783c8a..461e6d109d 100644 --- a/P5/Source/Specs/geoDecl.xml +++ b/P5/Source/Specs/geoDecl.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/geogFeat.xml b/P5/Source/Specs/geogFeat.xml index 29be061dfa..20c4ecadab 100644 --- a/P5/Source/Specs/geogFeat.xml +++ b/P5/Source/Specs/geogFeat.xml @@ -1,4 +1,6 @@ - + + + geographical feature name 지리적 특성명 nom de caractéristique géographique diff --git a/P5/Source/Specs/geogName.xml b/P5/Source/Specs/geogName.xml index 91eaf46f7a..a3bc05bf42 100644 --- a/P5/Source/Specs/geogName.xml +++ b/P5/Source/Specs/geogName.xml @@ -1,4 +1,6 @@ - + + + geographical name 지리명 地理名稱 diff --git a/P5/Source/Specs/gi.xml b/P5/Source/Specs/gi.xml index 1d603e90a7..57e953156d 100644 --- a/P5/Source/Specs/gi.xml +++ b/P5/Source/Specs/gi.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/gloss.xml b/P5/Source/Specs/gloss.xml index 1248276ca9..78e3a546ee 100644 --- a/P5/Source/Specs/gloss.xml +++ b/P5/Source/Specs/gloss.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/glyph.xml b/P5/Source/Specs/glyph.xml index d18376ccb8..f93c75c354 100644 --- a/P5/Source/Specs/glyph.xml +++ b/P5/Source/Specs/glyph.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/gram.xml b/P5/Source/Specs/gram.xml index 7c8216fdd8..1e71133303 100644 --- a/P5/Source/Specs/gram.xml +++ b/P5/Source/Specs/gram.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/gramGrp.xml b/P5/Source/Specs/gramGrp.xml index a32f855a22..11684c3d89 100644 --- a/P5/Source/Specs/gramGrp.xml +++ b/P5/Source/Specs/gramGrp.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/graph.xml b/P5/Source/Specs/graph.xml index ae8a2e5352..4a6ed4df6b 100644 --- a/P5/Source/Specs/graph.xml +++ b/P5/Source/Specs/graph.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/graphic.xml b/P5/Source/Specs/graphic.xml index 785dedf488..484b498b96 100644 --- a/P5/Source/Specs/graphic.xml +++ b/P5/Source/Specs/graphic.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/group.xml b/P5/Source/Specs/group.xml index 250606b879..3c1e70c7ef 100644 --- a/P5/Source/Specs/group.xml +++ b/P5/Source/Specs/group.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/handDesc.xml b/P5/Source/Specs/handDesc.xml index 9c334f76ec..5502f8cf3b 100644 --- a/P5/Source/Specs/handDesc.xml +++ b/P5/Source/Specs/handDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/handNote.xml b/P5/Source/Specs/handNote.xml index fb50a57c50..a3f276004f 100644 --- a/P5/Source/Specs/handNote.xml +++ b/P5/Source/Specs/handNote.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/handNotes.xml b/P5/Source/Specs/handNotes.xml index 0d9bb6fd17..0bda313232 100644 --- a/P5/Source/Specs/handNotes.xml +++ b/P5/Source/Specs/handNotes.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/handShift.xml b/P5/Source/Specs/handShift.xml index d9db2cf54e..c1b125314c 100644 --- a/P5/Source/Specs/handShift.xml +++ b/P5/Source/Specs/handShift.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/head.xml b/P5/Source/Specs/head.xml index 82593026ba..044a79606a 100644 --- a/P5/Source/Specs/head.xml +++ b/P5/Source/Specs/head.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/headItem.xml b/P5/Source/Specs/headItem.xml index ee23a7f20f..d56ac58f59 100644 --- a/P5/Source/Specs/headItem.xml +++ b/P5/Source/Specs/headItem.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/headLabel.xml b/P5/Source/Specs/headLabel.xml index 2aab40ad81..5654aa3589 100644 --- a/P5/Source/Specs/headLabel.xml +++ b/P5/Source/Specs/headLabel.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/height.xml b/P5/Source/Specs/height.xml index 7b0519755f..6955af7abc 100644 --- a/P5/Source/Specs/height.xml +++ b/P5/Source/Specs/height.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/heraldry.xml b/P5/Source/Specs/heraldry.xml index 816133e3fe..157d67fe9f 100644 --- a/P5/Source/Specs/heraldry.xml +++ b/P5/Source/Specs/heraldry.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/hi.xml b/P5/Source/Specs/hi.xml index 27538b990a..38d552d7d7 100644 --- a/P5/Source/Specs/hi.xml +++ b/P5/Source/Specs/hi.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/history.xml b/P5/Source/Specs/history.xml index 372b9160fe..33acee2629 100644 --- a/P5/Source/Specs/history.xml +++ b/P5/Source/Specs/history.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/hom.xml b/P5/Source/Specs/hom.xml index e0708cec05..de6f25101c 100644 --- a/P5/Source/Specs/hom.xml +++ b/P5/Source/Specs/hom.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/hyph.xml b/P5/Source/Specs/hyph.xml index ac45dd7e88..de8cb05498 100644 --- a/P5/Source/Specs/hyph.xml +++ b/P5/Source/Specs/hyph.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/hyphenation.xml b/P5/Source/Specs/hyphenation.xml index 02c8821df3..8788509470 100644 --- a/P5/Source/Specs/hyphenation.xml +++ b/P5/Source/Specs/hyphenation.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/iNode.xml b/P5/Source/Specs/iNode.xml index 0c1fdfa15d..3f504ce3a1 100644 --- a/P5/Source/Specs/iNode.xml +++ b/P5/Source/Specs/iNode.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/iType.xml b/P5/Source/Specs/iType.xml index 2c1491ea85..5d17618783 100644 --- a/P5/Source/Specs/iType.xml +++ b/P5/Source/Specs/iType.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/ident.xml b/P5/Source/Specs/ident.xml index e619eb3e00..8f6e42e8fe 100644 --- a/P5/Source/Specs/ident.xml +++ b/P5/Source/Specs/ident.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/idno.xml b/P5/Source/Specs/idno.xml index 3945300712..f906ecaef2 100644 --- a/P5/Source/Specs/idno.xml +++ b/P5/Source/Specs/idno.xml @@ -1,4 +1,6 @@ - + + + identifier identifiant 식별 숫자 diff --git a/P5/Source/Specs/if.xml b/P5/Source/Specs/if.xml index 6e32083c09..ec21615270 100644 --- a/P5/Source/Specs/if.xml +++ b/P5/Source/Specs/if.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/iff.xml b/P5/Source/Specs/iff.xml index 0a506718cc..2ea5058680 100644 --- a/P5/Source/Specs/iff.xml +++ b/P5/Source/Specs/iff.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/imprimatur.xml b/P5/Source/Specs/imprimatur.xml index 5abd8d91eb..dfe6eb7348 100644 --- a/P5/Source/Specs/imprimatur.xml +++ b/P5/Source/Specs/imprimatur.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/imprint.xml b/P5/Source/Specs/imprint.xml index a61b0d1fa8..4de2c11dca 100644 --- a/P5/Source/Specs/imprint.xml +++ b/P5/Source/Specs/imprint.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/incident.xml b/P5/Source/Specs/incident.xml index c7c434419d..897b8ab58e 100644 --- a/P5/Source/Specs/incident.xml +++ b/P5/Source/Specs/incident.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/incipit.xml b/P5/Source/Specs/incipit.xml index 24b7f3ac16..a3db06c937 100644 --- a/P5/Source/Specs/incipit.xml +++ b/P5/Source/Specs/incipit.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/index.xml b/P5/Source/Specs/index.xml index 34d581418e..99f022c5bf 100644 --- a/P5/Source/Specs/index.xml +++ b/P5/Source/Specs/index.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/institution.xml b/P5/Source/Specs/institution.xml index b40c2ca634..9e5fb18b2a 100644 --- a/P5/Source/Specs/institution.xml +++ b/P5/Source/Specs/institution.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/interaction.xml b/P5/Source/Specs/interaction.xml index 7754feb09a..34ec2d8803 100644 --- a/P5/Source/Specs/interaction.xml +++ b/P5/Source/Specs/interaction.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/interp.xml b/P5/Source/Specs/interp.xml index f7e47b68fa..207f4324c5 100644 --- a/P5/Source/Specs/interp.xml +++ b/P5/Source/Specs/interp.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/interpGrp.xml b/P5/Source/Specs/interpGrp.xml index 9b0b5cce97..754f723f6e 100644 --- a/P5/Source/Specs/interpGrp.xml +++ b/P5/Source/Specs/interpGrp.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/interpretation.xml b/P5/Source/Specs/interpretation.xml index 76fb98af6e..52aa24ada9 100644 --- a/P5/Source/Specs/interpretation.xml +++ b/P5/Source/Specs/interpretation.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/item.xml b/P5/Source/Specs/item.xml index 633fec8101..ee76e6984f 100644 --- a/P5/Source/Specs/item.xml +++ b/P5/Source/Specs/item.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/join.xml b/P5/Source/Specs/join.xml index 676e232121..3ea81278ff 100644 --- a/P5/Source/Specs/join.xml +++ b/P5/Source/Specs/join.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/joinGrp.xml b/P5/Source/Specs/joinGrp.xml index 78ec57a710..2473c6af84 100644 --- a/P5/Source/Specs/joinGrp.xml +++ b/P5/Source/Specs/joinGrp.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/keywords.xml b/P5/Source/Specs/keywords.xml index 3f6b7a752e..0aa4daec7b 100644 --- a/P5/Source/Specs/keywords.xml +++ b/P5/Source/Specs/keywords.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/kinesic.xml b/P5/Source/Specs/kinesic.xml index ca3627b025..b2ce01a9bc 100644 --- a/P5/Source/Specs/kinesic.xml +++ b/P5/Source/Specs/kinesic.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/l.xml b/P5/Source/Specs/l.xml index c8658bb7ff..6ce96e2937 100644 --- a/P5/Source/Specs/l.xml +++ b/P5/Source/Specs/l.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/label.xml b/P5/Source/Specs/label.xml index 46803c5e47..8fcffea4b6 100644 --- a/P5/Source/Specs/label.xml +++ b/P5/Source/Specs/label.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/lacunaEnd.xml b/P5/Source/Specs/lacunaEnd.xml index 03e6b06fee..c202f074a3 100644 --- a/P5/Source/Specs/lacunaEnd.xml +++ b/P5/Source/Specs/lacunaEnd.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/lacunaStart.xml b/P5/Source/Specs/lacunaStart.xml index 60c7eb588a..470c2eeda1 100644 --- a/P5/Source/Specs/lacunaStart.xml +++ b/P5/Source/Specs/lacunaStart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/lang.xml b/P5/Source/Specs/lang.xml index 4bccd75d18..fadc375705 100644 --- a/P5/Source/Specs/lang.xml +++ b/P5/Source/Specs/lang.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/langKnowledge.xml b/P5/Source/Specs/langKnowledge.xml index d4d6167587..83e50c9602 100644 --- a/P5/Source/Specs/langKnowledge.xml +++ b/P5/Source/Specs/langKnowledge.xml @@ -1,4 +1,6 @@ - + + + language knowledge 언어 지식 conocimiento del lenguaje diff --git a/P5/Source/Specs/langKnown.xml b/P5/Source/Specs/langKnown.xml index ad8017b6c2..e1de5b9ccb 100644 --- a/P5/Source/Specs/langKnown.xml +++ b/P5/Source/Specs/langKnown.xml @@ -1,4 +1,6 @@ - + + + language known 언어 능력 語言能力 diff --git a/P5/Source/Specs/langUsage.xml b/P5/Source/Specs/langUsage.xml index 877e6b75bf..c98816d9b6 100644 --- a/P5/Source/Specs/langUsage.xml +++ b/P5/Source/Specs/langUsage.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/language.xml b/P5/Source/Specs/language.xml index 2d3715148c..2f0b0a198a 100644 --- a/P5/Source/Specs/language.xml +++ b/P5/Source/Specs/language.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/layout.xml b/P5/Source/Specs/layout.xml index fd1697ebc1..10d211629b 100644 --- a/P5/Source/Specs/layout.xml +++ b/P5/Source/Specs/layout.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/layoutDesc.xml b/P5/Source/Specs/layoutDesc.xml index d0f0f79925..12404fd0ae 100644 --- a/P5/Source/Specs/layoutDesc.xml +++ b/P5/Source/Specs/layoutDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/lb.xml b/P5/Source/Specs/lb.xml index 729d8b207b..20d1d12c0b 100644 --- a/P5/Source/Specs/lb.xml +++ b/P5/Source/Specs/lb.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/lbl.xml b/P5/Source/Specs/lbl.xml index 00a5cbacc4..be29884354 100644 --- a/P5/Source/Specs/lbl.xml +++ b/P5/Source/Specs/lbl.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/leaf.xml b/P5/Source/Specs/leaf.xml index 0407e423af..ff5bc06eb4 100644 --- a/P5/Source/Specs/leaf.xml +++ b/P5/Source/Specs/leaf.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/lem.xml b/P5/Source/Specs/lem.xml index 3ec658f386..7cee12f6ab 100644 --- a/P5/Source/Specs/lem.xml +++ b/P5/Source/Specs/lem.xml @@ -1,4 +1,6 @@ - + + + lemma 레마 主題 diff --git a/P5/Source/Specs/lg.xml b/P5/Source/Specs/lg.xml index 904310e6a7..236f42407e 100644 --- a/P5/Source/Specs/lg.xml +++ b/P5/Source/Specs/lg.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/licence.xml b/P5/Source/Specs/licence.xml index ec3a0b6db1..e9682c37ad 100644 --- a/P5/Source/Specs/licence.xml +++ b/P5/Source/Specs/licence.xml @@ -1,4 +1,6 @@ - + + + contains information about a licence or other legal agreement applicable to the text. contient des informations diff --git a/P5/Source/Specs/line.xml b/P5/Source/Specs/line.xml index fcc1831531..c964955051 100644 --- a/P5/Source/Specs/line.xml +++ b/P5/Source/Specs/line.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/link.xml b/P5/Source/Specs/link.xml index 52f5fa6ffa..53d6a029cb 100644 --- a/P5/Source/Specs/link.xml +++ b/P5/Source/Specs/link.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/linkGrp.xml b/P5/Source/Specs/linkGrp.xml index c9a3d8ea37..c69cba235e 100644 --- a/P5/Source/Specs/linkGrp.xml +++ b/P5/Source/Specs/linkGrp.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/list.xml b/P5/Source/Specs/list.xml index 0fc538af51..5f965639ae 100644 --- a/P5/Source/Specs/list.xml +++ b/P5/Source/Specs/list.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/listAnnotation.xml b/P5/Source/Specs/listAnnotation.xml index 4de68c2b20..4d0c6c9af4 100644 --- a/P5/Source/Specs/listAnnotation.xml +++ b/P5/Source/Specs/listAnnotation.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/listChange.xml b/P5/Source/Specs/listChange.xml index c9d3a0db37..f18dcc2f6a 100644 --- a/P5/Source/Specs/listChange.xml +++ b/P5/Source/Specs/listChange.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/listEvent.xml b/P5/Source/Specs/listEvent.xml index 2a9465b1ad..9b82a6b07d 100644 --- a/P5/Source/Specs/listEvent.xml +++ b/P5/Source/Specs/listEvent.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/listForest.xml b/P5/Source/Specs/listForest.xml index ba40ab4ba2..6aaafc3d48 100644 --- a/P5/Source/Specs/listForest.xml +++ b/P5/Source/Specs/listForest.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/listNym.xml b/P5/Source/Specs/listNym.xml index 3484bd324f..d4d5b53c20 100644 --- a/P5/Source/Specs/listNym.xml +++ b/P5/Source/Specs/listNym.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/listObject.xml b/P5/Source/Specs/listObject.xml index d5ae2075b1..3fba9dd5e0 100644 --- a/P5/Source/Specs/listObject.xml +++ b/P5/Source/Specs/listObject.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/listOrg.xml b/P5/Source/Specs/listOrg.xml index 7cde9a8430..35d0dc7d76 100644 --- a/P5/Source/Specs/listOrg.xml +++ b/P5/Source/Specs/listOrg.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/listPerson.xml b/P5/Source/Specs/listPerson.xml index 2901787068..fa5d589253 100644 --- a/P5/Source/Specs/listPerson.xml +++ b/P5/Source/Specs/listPerson.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/listPlace.xml b/P5/Source/Specs/listPlace.xml index 4fd1e6d0a4..67e5dca76a 100644 --- a/P5/Source/Specs/listPlace.xml +++ b/P5/Source/Specs/listPlace.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/listPrefixDef.xml b/P5/Source/Specs/listPrefixDef.xml index 23b467cedb..d62136ef0c 100644 --- a/P5/Source/Specs/listPrefixDef.xml +++ b/P5/Source/Specs/listPrefixDef.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/listRef.xml b/P5/Source/Specs/listRef.xml index 753935ac94..d4d888cee7 100644 --- a/P5/Source/Specs/listRef.xml +++ b/P5/Source/Specs/listRef.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/listRelation.xml b/P5/Source/Specs/listRelation.xml index 81e321d2bd..d1510dbe9f 100644 --- a/P5/Source/Specs/listRelation.xml +++ b/P5/Source/Specs/listRelation.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/listTranspose.xml b/P5/Source/Specs/listTranspose.xml index 35758e0cfc..53507ffd4f 100644 --- a/P5/Source/Specs/listTranspose.xml +++ b/P5/Source/Specs/listTranspose.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/listWit.xml b/P5/Source/Specs/listWit.xml index 71e25eedac..76bb5f9dcc 100644 --- a/P5/Source/Specs/listWit.xml +++ b/P5/Source/Specs/listWit.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/localProp.xml b/P5/Source/Specs/localProp.xml index 797ff3f99d..4bd08517ad 100644 --- a/P5/Source/Specs/localProp.xml +++ b/P5/Source/Specs/localProp.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/location.xml b/P5/Source/Specs/location.xml index bd84c76f3b..10d9caaad7 100644 --- a/P5/Source/Specs/location.xml +++ b/P5/Source/Specs/location.xml @@ -1,4 +1,6 @@ - + + + location localisation defines the location of a place as a set of geographical coordinates, in terms of other named geo-political entities, or as an diff --git a/P5/Source/Specs/locus.xml b/P5/Source/Specs/locus.xml index 05438e07cd..811bb7a855 100644 --- a/P5/Source/Specs/locus.xml +++ b/P5/Source/Specs/locus.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/locusGrp.xml b/P5/Source/Specs/locusGrp.xml index 798aa873f1..7ddc2b7b61 100644 --- a/P5/Source/Specs/locusGrp.xml +++ b/P5/Source/Specs/locusGrp.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/m.xml b/P5/Source/Specs/m.xml index 1cb3c310e4..acf7cf9e38 100644 --- a/P5/Source/Specs/m.xml +++ b/P5/Source/Specs/m.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/macro.abContent.xml b/P5/Source/Specs/macro.abContent.xml index bbfc8461d2..334fcc3b12 100644 --- a/P5/Source/Specs/macro.abContent.xml +++ b/P5/Source/Specs/macro.abContent.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/macro.limitedContent.xml b/P5/Source/Specs/macro.limitedContent.xml index 204eb07cad..01874ed5ff 100644 --- a/P5/Source/Specs/macro.limitedContent.xml +++ b/P5/Source/Specs/macro.limitedContent.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/macro.paraContent.xml b/P5/Source/Specs/macro.paraContent.xml index 74a2771895..69a2a4f275 100644 --- a/P5/Source/Specs/macro.paraContent.xml +++ b/P5/Source/Specs/macro.paraContent.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/macro.phraseSeq.limited.xml b/P5/Source/Specs/macro.phraseSeq.limited.xml index dbb93623eb..efc9dc1dc8 100644 --- a/P5/Source/Specs/macro.phraseSeq.limited.xml +++ b/P5/Source/Specs/macro.phraseSeq.limited.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/macro.phraseSeq.xml b/P5/Source/Specs/macro.phraseSeq.xml index 39d2fe7767..ffb6fd08cb 100644 --- a/P5/Source/Specs/macro.phraseSeq.xml +++ b/P5/Source/Specs/macro.phraseSeq.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/macro.specialPara.xml b/P5/Source/Specs/macro.specialPara.xml index 7c589d54b2..931b331a37 100644 --- a/P5/Source/Specs/macro.specialPara.xml +++ b/P5/Source/Specs/macro.specialPara.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/macro.xtext.xml b/P5/Source/Specs/macro.xtext.xml index 70e2073584..e6eaeafc40 100644 --- a/P5/Source/Specs/macro.xtext.xml +++ b/P5/Source/Specs/macro.xtext.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/macroRef.xml b/P5/Source/Specs/macroRef.xml index de5698dce3..76eb78bb86 100644 --- a/P5/Source/Specs/macroRef.xml +++ b/P5/Source/Specs/macroRef.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/macroSpec.xml b/P5/Source/Specs/macroSpec.xml index 5ec54e85be..039a67c863 100644 --- a/P5/Source/Specs/macroSpec.xml +++ b/P5/Source/Specs/macroSpec.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/mapping.xml b/P5/Source/Specs/mapping.xml index ed766e8285..35c2b5c2a0 100644 --- a/P5/Source/Specs/mapping.xml +++ b/P5/Source/Specs/mapping.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/material.xml b/P5/Source/Specs/material.xml index 099a08c612..b874df85cb 100644 --- a/P5/Source/Specs/material.xml +++ b/P5/Source/Specs/material.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/measure.xml b/P5/Source/Specs/measure.xml index c28e598124..78f8d26b9a 100644 --- a/P5/Source/Specs/measure.xml +++ b/P5/Source/Specs/measure.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/measureGrp.xml b/P5/Source/Specs/measureGrp.xml index d5c9314e9a..764e9feb13 100644 --- a/P5/Source/Specs/measureGrp.xml +++ b/P5/Source/Specs/measureGrp.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/media.xml b/P5/Source/Specs/media.xml index ea14edfa18..79b94f79a9 100644 --- a/P5/Source/Specs/media.xml +++ b/P5/Source/Specs/media.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/meeting.xml b/P5/Source/Specs/meeting.xml index 2662ca20b4..882c6cf57e 100644 --- a/P5/Source/Specs/meeting.xml +++ b/P5/Source/Specs/meeting.xml @@ -1,4 +1,6 @@ - + + + contains the formalized descriptive title for a meeting or conference, for use in a bibliographic description for an item derived from such a meeting, or as a heading or preamble to publications emanating from it. diff --git a/P5/Source/Specs/memberOf.xml b/P5/Source/Specs/memberOf.xml index c10c9e3397..d65b7cc231 100644 --- a/P5/Source/Specs/memberOf.xml +++ b/P5/Source/Specs/memberOf.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/mentioned.xml b/P5/Source/Specs/mentioned.xml index a665e7e67c..102bff58cb 100644 --- a/P5/Source/Specs/mentioned.xml +++ b/P5/Source/Specs/mentioned.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/metDecl.xml b/P5/Source/Specs/metDecl.xml index a02918702c..67e137bd56 100644 --- a/P5/Source/Specs/metDecl.xml +++ b/P5/Source/Specs/metDecl.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/metSym.xml b/P5/Source/Specs/metSym.xml index b966ea0ece..deb5f32d8c 100644 --- a/P5/Source/Specs/metSym.xml +++ b/P5/Source/Specs/metSym.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/metamark.xml b/P5/Source/Specs/metamark.xml index 5f6f9935fa..69855f11a2 100644 --- a/P5/Source/Specs/metamark.xml +++ b/P5/Source/Specs/metamark.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/milestone.xml b/P5/Source/Specs/milestone.xml index d42a00d3be..1a70a9ee47 100644 --- a/P5/Source/Specs/milestone.xml +++ b/P5/Source/Specs/milestone.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/mod.xml b/P5/Source/Specs/mod.xml index 9d9a668621..98e3f4b768 100644 --- a/P5/Source/Specs/mod.xml +++ b/P5/Source/Specs/mod.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.addrPart.xml b/P5/Source/Specs/model.addrPart.xml index 7ba411f4c1..847584ab25 100644 --- a/P5/Source/Specs/model.addrPart.xml +++ b/P5/Source/Specs/model.addrPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.addressLike.xml b/P5/Source/Specs/model.addressLike.xml index b0cb56b841..f8634bf901 100644 --- a/P5/Source/Specs/model.addressLike.xml +++ b/P5/Source/Specs/model.addressLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.annotationLike.xml b/P5/Source/Specs/model.annotationLike.xml index 2f3b0648d6..ef3037faa7 100644 --- a/P5/Source/Specs/model.annotationLike.xml +++ b/P5/Source/Specs/model.annotationLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.annotationPart.body.xml b/P5/Source/Specs/model.annotationPart.body.xml index 4ed5fe24b5..da785f57b1 100644 --- a/P5/Source/Specs/model.annotationPart.body.xml +++ b/P5/Source/Specs/model.annotationPart.body.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.applicationLike.xml b/P5/Source/Specs/model.applicationLike.xml index 7ef827e172..5dd5316e47 100644 --- a/P5/Source/Specs/model.applicationLike.xml +++ b/P5/Source/Specs/model.applicationLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.attributable.xml b/P5/Source/Specs/model.attributable.xml index 2c59ae16bb..04d38832dc 100644 --- a/P5/Source/Specs/model.attributable.xml +++ b/P5/Source/Specs/model.attributable.xml @@ -1,4 +1,6 @@ - + + + groups elements that contain a word or phrase that can be attributed to a source. gruppiert Elemente, die ein Wort oder eine Phrase enthalten, welche einer Quelle zugeschrieben werden können. diff --git a/P5/Source/Specs/model.biblLike.xml b/P5/Source/Specs/model.biblLike.xml index f153110052..0ef6a0ef2d 100644 --- a/P5/Source/Specs/model.biblLike.xml +++ b/P5/Source/Specs/model.biblLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.biblPart.xml b/P5/Source/Specs/model.biblPart.xml index fe071e78f6..8be9a7204b 100644 --- a/P5/Source/Specs/model.biblPart.xml +++ b/P5/Source/Specs/model.biblPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.castItemPart.xml b/P5/Source/Specs/model.castItemPart.xml index 4c12d14030..cd34fa265f 100644 --- a/P5/Source/Specs/model.castItemPart.xml +++ b/P5/Source/Specs/model.castItemPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.catDescPart.xml b/P5/Source/Specs/model.catDescPart.xml index 3caed96273..1fb3154064 100644 --- a/P5/Source/Specs/model.catDescPart.xml +++ b/P5/Source/Specs/model.catDescPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.certLike.xml b/P5/Source/Specs/model.certLike.xml index 7d3b910a1d..36cc33bc97 100644 --- a/P5/Source/Specs/model.certLike.xml +++ b/P5/Source/Specs/model.certLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.choicePart.xml b/P5/Source/Specs/model.choicePart.xml index e36a7706e4..e5751b9830 100644 --- a/P5/Source/Specs/model.choicePart.xml +++ b/P5/Source/Specs/model.choicePart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.common.xml b/P5/Source/Specs/model.common.xml index 3a8345c6a4..a280903eb3 100644 --- a/P5/Source/Specs/model.common.xml +++ b/P5/Source/Specs/model.common.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.contentPart.xml b/P5/Source/Specs/model.contentPart.xml index 6f6a58baa3..4f632739e1 100644 --- a/P5/Source/Specs/model.contentPart.xml +++ b/P5/Source/Specs/model.contentPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.correspActionPart.xml b/P5/Source/Specs/model.correspActionPart.xml index 5fce18c220..d21ce9fae8 100644 --- a/P5/Source/Specs/model.correspActionPart.xml +++ b/P5/Source/Specs/model.correspActionPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.correspContextPart.xml b/P5/Source/Specs/model.correspContextPart.xml index c5aa85f88e..571b58d3ec 100644 --- a/P5/Source/Specs/model.correspContextPart.xml +++ b/P5/Source/Specs/model.correspContextPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.correspDescPart.xml b/P5/Source/Specs/model.correspDescPart.xml index d9fec20b59..bc7361c439 100644 --- a/P5/Source/Specs/model.correspDescPart.xml +++ b/P5/Source/Specs/model.correspDescPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.dateLike.xml b/P5/Source/Specs/model.dateLike.xml index 6e90e0a624..cc5e64f093 100644 --- a/P5/Source/Specs/model.dateLike.xml +++ b/P5/Source/Specs/model.dateLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.descLike.xml b/P5/Source/Specs/model.descLike.xml index bc0b30bc33..2156d0fe50 100644 --- a/P5/Source/Specs/model.descLike.xml +++ b/P5/Source/Specs/model.descLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.describedResource.xml b/P5/Source/Specs/model.describedResource.xml index cd32d9dd5a..d23feec3a8 100644 --- a/P5/Source/Specs/model.describedResource.xml +++ b/P5/Source/Specs/model.describedResource.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.dimLike.xml b/P5/Source/Specs/model.dimLike.xml index 875460f33c..582c736f6e 100644 --- a/P5/Source/Specs/model.dimLike.xml +++ b/P5/Source/Specs/model.dimLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.div1Like.xml b/P5/Source/Specs/model.div1Like.xml index 8949d95c77..75ed9ca237 100644 --- a/P5/Source/Specs/model.div1Like.xml +++ b/P5/Source/Specs/model.div1Like.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.div2Like.xml b/P5/Source/Specs/model.div2Like.xml index 3305b2d5e5..f641e7d38a 100644 --- a/P5/Source/Specs/model.div2Like.xml +++ b/P5/Source/Specs/model.div2Like.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.div3Like.xml b/P5/Source/Specs/model.div3Like.xml index 0a7d22ae4d..170fe3dafe 100644 --- a/P5/Source/Specs/model.div3Like.xml +++ b/P5/Source/Specs/model.div3Like.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.div4Like.xml b/P5/Source/Specs/model.div4Like.xml index e1985e8b0e..21403a6383 100644 --- a/P5/Source/Specs/model.div4Like.xml +++ b/P5/Source/Specs/model.div4Like.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.div5Like.xml b/P5/Source/Specs/model.div5Like.xml index 9200705136..d1fbe5b62a 100644 --- a/P5/Source/Specs/model.div5Like.xml +++ b/P5/Source/Specs/model.div5Like.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.div6Like.xml b/P5/Source/Specs/model.div6Like.xml index 5cae7f5656..69c74d0dcd 100644 --- a/P5/Source/Specs/model.div6Like.xml +++ b/P5/Source/Specs/model.div6Like.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.div7Like.xml b/P5/Source/Specs/model.div7Like.xml index 819acfd4d5..0f3bb314bb 100644 --- a/P5/Source/Specs/model.div7Like.xml +++ b/P5/Source/Specs/model.div7Like.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.divBottom.xml b/P5/Source/Specs/model.divBottom.xml index 1fd3bc39ee..45ccdefce6 100644 --- a/P5/Source/Specs/model.divBottom.xml +++ b/P5/Source/Specs/model.divBottom.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.divBottomPart.xml b/P5/Source/Specs/model.divBottomPart.xml index 6175322295..be152a9006 100644 --- a/P5/Source/Specs/model.divBottomPart.xml +++ b/P5/Source/Specs/model.divBottomPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.divGenLike.xml b/P5/Source/Specs/model.divGenLike.xml index db05db0e83..a9374d82a2 100644 --- a/P5/Source/Specs/model.divGenLike.xml +++ b/P5/Source/Specs/model.divGenLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.divLike.xml b/P5/Source/Specs/model.divLike.xml index 5bb834f6f7..9b16663607 100644 --- a/P5/Source/Specs/model.divLike.xml +++ b/P5/Source/Specs/model.divLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.divPart.spoken.xml b/P5/Source/Specs/model.divPart.spoken.xml index 6b19d4ec7d..d27191ad49 100644 --- a/P5/Source/Specs/model.divPart.spoken.xml +++ b/P5/Source/Specs/model.divPart.spoken.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.divPart.xml b/P5/Source/Specs/model.divPart.xml index 85b74f98ec..a322a9803f 100644 --- a/P5/Source/Specs/model.divPart.xml +++ b/P5/Source/Specs/model.divPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.divTop.xml b/P5/Source/Specs/model.divTop.xml index 336d6e3c96..83ab4ca3e8 100644 --- a/P5/Source/Specs/model.divTop.xml +++ b/P5/Source/Specs/model.divTop.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.divTopPart.xml b/P5/Source/Specs/model.divTopPart.xml index 5038063ad9..30314ebd9c 100644 --- a/P5/Source/Specs/model.divTopPart.xml +++ b/P5/Source/Specs/model.divTopPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.divWrapper.xml b/P5/Source/Specs/model.divWrapper.xml index c8c0f0bbda..2844c3759e 100644 --- a/P5/Source/Specs/model.divWrapper.xml +++ b/P5/Source/Specs/model.divWrapper.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.editorialDeclPart.xml b/P5/Source/Specs/model.editorialDeclPart.xml index 14edb0c6ab..0d647afe9c 100644 --- a/P5/Source/Specs/model.editorialDeclPart.xml +++ b/P5/Source/Specs/model.editorialDeclPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.egLike.xml b/P5/Source/Specs/model.egLike.xml index 46fa32e6d9..de9279727e 100644 --- a/P5/Source/Specs/model.egLike.xml +++ b/P5/Source/Specs/model.egLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.emphLike.xml b/P5/Source/Specs/model.emphLike.xml index 78e6c32fc2..5f3d8d23ce 100644 --- a/P5/Source/Specs/model.emphLike.xml +++ b/P5/Source/Specs/model.emphLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.encodingDescPart.xml b/P5/Source/Specs/model.encodingDescPart.xml index 3f639ac7a3..4e81fb7352 100644 --- a/P5/Source/Specs/model.encodingDescPart.xml +++ b/P5/Source/Specs/model.encodingDescPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.entryLike.xml b/P5/Source/Specs/model.entryLike.xml index 8f4c9e27a6..f353dae501 100644 --- a/P5/Source/Specs/model.entryLike.xml +++ b/P5/Source/Specs/model.entryLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.entryPart.top.xml b/P5/Source/Specs/model.entryPart.top.xml index 2e27558c91..a876bd47d2 100644 --- a/P5/Source/Specs/model.entryPart.top.xml +++ b/P5/Source/Specs/model.entryPart.top.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.entryPart.xml b/P5/Source/Specs/model.entryPart.xml index 2f5d7a0022..175ba2e294 100644 --- a/P5/Source/Specs/model.entryPart.xml +++ b/P5/Source/Specs/model.entryPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.eventLike.xml b/P5/Source/Specs/model.eventLike.xml index 55feb20a45..e962a0cdae 100644 --- a/P5/Source/Specs/model.eventLike.xml +++ b/P5/Source/Specs/model.eventLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.featureVal.complex.xml b/P5/Source/Specs/model.featureVal.complex.xml index 19ec360806..c43ff4e8f6 100644 --- a/P5/Source/Specs/model.featureVal.complex.xml +++ b/P5/Source/Specs/model.featureVal.complex.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.featureVal.single.xml b/P5/Source/Specs/model.featureVal.single.xml index 7c6db41df8..a23dc83436 100644 --- a/P5/Source/Specs/model.featureVal.single.xml +++ b/P5/Source/Specs/model.featureVal.single.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.featureVal.xml b/P5/Source/Specs/model.featureVal.xml index c5b5aa8292..1c530fb21f 100644 --- a/P5/Source/Specs/model.featureVal.xml +++ b/P5/Source/Specs/model.featureVal.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.formPart.xml b/P5/Source/Specs/model.formPart.xml index 9c1ceb3753..f0c8385f9c 100644 --- a/P5/Source/Specs/model.formPart.xml +++ b/P5/Source/Specs/model.formPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.frontPart.drama.xml b/P5/Source/Specs/model.frontPart.drama.xml index ebc9920e22..6fb75c05d1 100644 --- a/P5/Source/Specs/model.frontPart.drama.xml +++ b/P5/Source/Specs/model.frontPart.drama.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.frontPart.xml b/P5/Source/Specs/model.frontPart.xml index e6ac36c010..350fd52d0d 100644 --- a/P5/Source/Specs/model.frontPart.xml +++ b/P5/Source/Specs/model.frontPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.fsdDeclPart.xml b/P5/Source/Specs/model.fsdDeclPart.xml index ca83d64783..57a8bbbed5 100644 --- a/P5/Source/Specs/model.fsdDeclPart.xml +++ b/P5/Source/Specs/model.fsdDeclPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.gLike.xml b/P5/Source/Specs/model.gLike.xml index 549c8e2f21..aae54d3233 100644 --- a/P5/Source/Specs/model.gLike.xml +++ b/P5/Source/Specs/model.gLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.global.edit.xml b/P5/Source/Specs/model.global.edit.xml index 6a30b24222..c17467604b 100644 --- a/P5/Source/Specs/model.global.edit.xml +++ b/P5/Source/Specs/model.global.edit.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.global.meta.xml b/P5/Source/Specs/model.global.meta.xml index ed80bdb7d1..8d4c514ac4 100644 --- a/P5/Source/Specs/model.global.meta.xml +++ b/P5/Source/Specs/model.global.meta.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.global.spoken.xml b/P5/Source/Specs/model.global.spoken.xml index 25bb62990f..e8046e67a1 100644 --- a/P5/Source/Specs/model.global.spoken.xml +++ b/P5/Source/Specs/model.global.spoken.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.global.xml b/P5/Source/Specs/model.global.xml index 5079a3498b..e6da0f33f7 100644 --- a/P5/Source/Specs/model.global.xml +++ b/P5/Source/Specs/model.global.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.gramPart.xml b/P5/Source/Specs/model.gramPart.xml index f3169f7f98..69878ff4c4 100644 --- a/P5/Source/Specs/model.gramPart.xml +++ b/P5/Source/Specs/model.gramPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.graphicLike.xml b/P5/Source/Specs/model.graphicLike.xml index 3d309f3344..3a75a3df6c 100644 --- a/P5/Source/Specs/model.graphicLike.xml +++ b/P5/Source/Specs/model.graphicLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.headLike.xml b/P5/Source/Specs/model.headLike.xml index e5a218c1b0..6d5eb489e4 100644 --- a/P5/Source/Specs/model.headLike.xml +++ b/P5/Source/Specs/model.headLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.hiLike.xml b/P5/Source/Specs/model.hiLike.xml index f2e4281555..c05ff7bc6e 100644 --- a/P5/Source/Specs/model.hiLike.xml +++ b/P5/Source/Specs/model.hiLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.highlighted.xml b/P5/Source/Specs/model.highlighted.xml index 033508e9e1..96664c4dc3 100644 --- a/P5/Source/Specs/model.highlighted.xml +++ b/P5/Source/Specs/model.highlighted.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.identEquiv.xml b/P5/Source/Specs/model.identEquiv.xml index c8b44db1cb..b455592949 100644 --- a/P5/Source/Specs/model.identEquiv.xml +++ b/P5/Source/Specs/model.identEquiv.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.identSynonyms.xml b/P5/Source/Specs/model.identSynonyms.xml index 79187a0b83..b5729c6eef 100644 --- a/P5/Source/Specs/model.identSynonyms.xml +++ b/P5/Source/Specs/model.identSynonyms.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.imprintPart.xml b/P5/Source/Specs/model.imprintPart.xml index 4323c9bd0d..ea2e52ba0a 100644 --- a/P5/Source/Specs/model.imprintPart.xml +++ b/P5/Source/Specs/model.imprintPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.inter.xml b/P5/Source/Specs/model.inter.xml index 8c701142d7..ce5d9d92af 100644 --- a/P5/Source/Specs/model.inter.xml +++ b/P5/Source/Specs/model.inter.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.lLike.xml b/P5/Source/Specs/model.lLike.xml index e576766768..89815c76a0 100644 --- a/P5/Source/Specs/model.lLike.xml +++ b/P5/Source/Specs/model.lLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.lPart.xml b/P5/Source/Specs/model.lPart.xml index f07c52d2ab..374a2e2cad 100644 --- a/P5/Source/Specs/model.lPart.xml +++ b/P5/Source/Specs/model.lPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.labelLike.xml b/P5/Source/Specs/model.labelLike.xml index d9a671bf18..940ae3ed7a 100644 --- a/P5/Source/Specs/model.labelLike.xml +++ b/P5/Source/Specs/model.labelLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.lexicalRefinement.xml b/P5/Source/Specs/model.lexicalRefinement.xml index 196cbedba9..64a5b5bbf3 100644 --- a/P5/Source/Specs/model.lexicalRefinement.xml +++ b/P5/Source/Specs/model.lexicalRefinement.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.limitedPhrase.xml b/P5/Source/Specs/model.limitedPhrase.xml index 2084f4fdc2..5b6c2ea0d5 100644 --- a/P5/Source/Specs/model.limitedPhrase.xml +++ b/P5/Source/Specs/model.limitedPhrase.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.linePart.xml b/P5/Source/Specs/model.linePart.xml index bf07c615c4..6595c90937 100644 --- a/P5/Source/Specs/model.linePart.xml +++ b/P5/Source/Specs/model.linePart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.listLike.xml b/P5/Source/Specs/model.listLike.xml index ca16d79da6..933ca683a1 100644 --- a/P5/Source/Specs/model.listLike.xml +++ b/P5/Source/Specs/model.listLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.measureLike.xml b/P5/Source/Specs/model.measureLike.xml index 63be2d9015..240dfd3398 100644 --- a/P5/Source/Specs/model.measureLike.xml +++ b/P5/Source/Specs/model.measureLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.milestoneLike.xml b/P5/Source/Specs/model.milestoneLike.xml index ef5da5015c..86aa7ea019 100644 --- a/P5/Source/Specs/model.milestoneLike.xml +++ b/P5/Source/Specs/model.milestoneLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.morphLike.xml b/P5/Source/Specs/model.morphLike.xml index b2f40ef7b2..01178cb65d 100644 --- a/P5/Source/Specs/model.morphLike.xml +++ b/P5/Source/Specs/model.morphLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.msItemPart.xml b/P5/Source/Specs/model.msItemPart.xml index a4b3c71bac..8252284491 100644 --- a/P5/Source/Specs/model.msItemPart.xml +++ b/P5/Source/Specs/model.msItemPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.msQuoteLike.xml b/P5/Source/Specs/model.msQuoteLike.xml index 9bb52bbbb5..ab9d6cc53a 100644 --- a/P5/Source/Specs/model.msQuoteLike.xml +++ b/P5/Source/Specs/model.msQuoteLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.nameLike.agent.xml b/P5/Source/Specs/model.nameLike.agent.xml index baa013cab5..31d40a42f8 100644 --- a/P5/Source/Specs/model.nameLike.agent.xml +++ b/P5/Source/Specs/model.nameLike.agent.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.nameLike.xml b/P5/Source/Specs/model.nameLike.xml index 9361febe84..794fef0801 100644 --- a/P5/Source/Specs/model.nameLike.xml +++ b/P5/Source/Specs/model.nameLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.noteLike.xml b/P5/Source/Specs/model.noteLike.xml index 5e0ae356bb..dc030037ae 100644 --- a/P5/Source/Specs/model.noteLike.xml +++ b/P5/Source/Specs/model.noteLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.objectLike.xml b/P5/Source/Specs/model.objectLike.xml index 8be357e26b..f6949ef47e 100644 --- a/P5/Source/Specs/model.objectLike.xml +++ b/P5/Source/Specs/model.objectLike.xml @@ -1,4 +1,6 @@ - + + + groups elements which describe objects. diff --git a/P5/Source/Specs/model.oddDecl.xml b/P5/Source/Specs/model.oddDecl.xml index 6f90f2c7b6..4cfcea94d9 100644 --- a/P5/Source/Specs/model.oddDecl.xml +++ b/P5/Source/Specs/model.oddDecl.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.oddRef.xml b/P5/Source/Specs/model.oddRef.xml index 5071985070..b68930eb85 100644 --- a/P5/Source/Specs/model.oddRef.xml +++ b/P5/Source/Specs/model.oddRef.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.offsetLike.xml b/P5/Source/Specs/model.offsetLike.xml index a00aa1cfe9..9990330de2 100644 --- a/P5/Source/Specs/model.offsetLike.xml +++ b/P5/Source/Specs/model.offsetLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.orgPart.xml b/P5/Source/Specs/model.orgPart.xml index 0d97c3f0b5..27aa48a4dc 100644 --- a/P5/Source/Specs/model.orgPart.xml +++ b/P5/Source/Specs/model.orgPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.orgStateLike.xml b/P5/Source/Specs/model.orgStateLike.xml index 17cb8daf6c..0495ebe712 100644 --- a/P5/Source/Specs/model.orgStateLike.xml +++ b/P5/Source/Specs/model.orgStateLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.pLike.front.xml b/P5/Source/Specs/model.pLike.front.xml index 5ed337cc1a..58a2a3f4ab 100644 --- a/P5/Source/Specs/model.pLike.front.xml +++ b/P5/Source/Specs/model.pLike.front.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.pLike.xml b/P5/Source/Specs/model.pLike.xml index acc1d35a36..109954fa1b 100644 --- a/P5/Source/Specs/model.pLike.xml +++ b/P5/Source/Specs/model.pLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.pPart.data.xml b/P5/Source/Specs/model.pPart.data.xml index bdd8acf840..fee3950155 100644 --- a/P5/Source/Specs/model.pPart.data.xml +++ b/P5/Source/Specs/model.pPart.data.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.pPart.edit.xml b/P5/Source/Specs/model.pPart.edit.xml index f1906e500a..da05b24dc0 100644 --- a/P5/Source/Specs/model.pPart.edit.xml +++ b/P5/Source/Specs/model.pPart.edit.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.pPart.editorial.xml b/P5/Source/Specs/model.pPart.editorial.xml index f01cdcb0de..0cf401ddf3 100644 --- a/P5/Source/Specs/model.pPart.editorial.xml +++ b/P5/Source/Specs/model.pPart.editorial.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.pPart.msdesc.xml b/P5/Source/Specs/model.pPart.msdesc.xml index bf597ac580..ab4625ae0c 100644 --- a/P5/Source/Specs/model.pPart.msdesc.xml +++ b/P5/Source/Specs/model.pPart.msdesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.pPart.transcriptional.xml b/P5/Source/Specs/model.pPart.transcriptional.xml index 03ce7fbfe8..37389adddf 100644 --- a/P5/Source/Specs/model.pPart.transcriptional.xml +++ b/P5/Source/Specs/model.pPart.transcriptional.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.paraPart.xml b/P5/Source/Specs/model.paraPart.xml index b593f26b43..7242f4a202 100644 --- a/P5/Source/Specs/model.paraPart.xml +++ b/P5/Source/Specs/model.paraPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.persNamePart.xml b/P5/Source/Specs/model.persNamePart.xml index d1c52cbda0..4dcc7c8a7a 100644 --- a/P5/Source/Specs/model.persNamePart.xml +++ b/P5/Source/Specs/model.persNamePart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.persStateLike.xml b/P5/Source/Specs/model.persStateLike.xml index 3749a55a8b..7391695f01 100644 --- a/P5/Source/Specs/model.persStateLike.xml +++ b/P5/Source/Specs/model.persStateLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.personLike.xml b/P5/Source/Specs/model.personLike.xml index c5e0d466dc..0066b0c904 100644 --- a/P5/Source/Specs/model.personLike.xml +++ b/P5/Source/Specs/model.personLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.personPart.xml b/P5/Source/Specs/model.personPart.xml index 7a526ee0e0..6cbf0040e0 100644 --- a/P5/Source/Specs/model.personPart.xml +++ b/P5/Source/Specs/model.personPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.phrase.xml b/P5/Source/Specs/model.phrase.xml index 26e5a5c08b..8f370d52cd 100644 --- a/P5/Source/Specs/model.phrase.xml +++ b/P5/Source/Specs/model.phrase.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.phrase.xml.xml b/P5/Source/Specs/model.phrase.xml.xml index 5ab4b83846..01b2d63cd1 100644 --- a/P5/Source/Specs/model.phrase.xml.xml +++ b/P5/Source/Specs/model.phrase.xml.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.physDescPart.xml b/P5/Source/Specs/model.physDescPart.xml index c349770cbf..46328bbd62 100644 --- a/P5/Source/Specs/model.physDescPart.xml +++ b/P5/Source/Specs/model.physDescPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.placeLike.xml b/P5/Source/Specs/model.placeLike.xml index 3dc27043b9..833179ea38 100644 --- a/P5/Source/Specs/model.placeLike.xml +++ b/P5/Source/Specs/model.placeLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.placeNamePart.xml b/P5/Source/Specs/model.placeNamePart.xml index 6580f89223..19b1a60558 100644 --- a/P5/Source/Specs/model.placeNamePart.xml +++ b/P5/Source/Specs/model.placeNamePart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.placeStateLike.xml b/P5/Source/Specs/model.placeStateLike.xml index c5b08f4451..8929e9833b 100644 --- a/P5/Source/Specs/model.placeStateLike.xml +++ b/P5/Source/Specs/model.placeStateLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.profileDescPart.xml b/P5/Source/Specs/model.profileDescPart.xml index d744a63fb5..4cb0466848 100644 --- a/P5/Source/Specs/model.profileDescPart.xml +++ b/P5/Source/Specs/model.profileDescPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.ptrLike.form.xml b/P5/Source/Specs/model.ptrLike.form.xml index 7b597902b3..65d7347683 100644 --- a/P5/Source/Specs/model.ptrLike.form.xml +++ b/P5/Source/Specs/model.ptrLike.form.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.ptrLike.xml b/P5/Source/Specs/model.ptrLike.xml index 7a4d193a66..6e3281bb2f 100644 --- a/P5/Source/Specs/model.ptrLike.xml +++ b/P5/Source/Specs/model.ptrLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.publicationStmtPart.agency.xml b/P5/Source/Specs/model.publicationStmtPart.agency.xml index d955608d5c..babb6af6df 100644 --- a/P5/Source/Specs/model.publicationStmtPart.agency.xml +++ b/P5/Source/Specs/model.publicationStmtPart.agency.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.publicationStmtPart.detail.xml b/P5/Source/Specs/model.publicationStmtPart.detail.xml index 7392139710..795e20a135 100644 --- a/P5/Source/Specs/model.publicationStmtPart.detail.xml +++ b/P5/Source/Specs/model.publicationStmtPart.detail.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.quoteLike.xml b/P5/Source/Specs/model.quoteLike.xml index 588084aa88..26ee6d9b55 100644 --- a/P5/Source/Specs/model.quoteLike.xml +++ b/P5/Source/Specs/model.quoteLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.rdgLike.xml b/P5/Source/Specs/model.rdgLike.xml index de9acb1da0..980447303c 100644 --- a/P5/Source/Specs/model.rdgLike.xml +++ b/P5/Source/Specs/model.rdgLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.rdgPart.xml b/P5/Source/Specs/model.rdgPart.xml index 8f1f3bca3d..8fd44c5ee5 100644 --- a/P5/Source/Specs/model.rdgPart.xml +++ b/P5/Source/Specs/model.rdgPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.recordingPart.xml b/P5/Source/Specs/model.recordingPart.xml index 6d84cc11a5..e5c23ad431 100644 --- a/P5/Source/Specs/model.recordingPart.xml +++ b/P5/Source/Specs/model.recordingPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.resource.xml b/P5/Source/Specs/model.resource.xml index d0b5370a6f..8065ea297d 100644 --- a/P5/Source/Specs/model.resource.xml +++ b/P5/Source/Specs/model.resource.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.respLike.xml b/P5/Source/Specs/model.respLike.xml index b4beb3d50c..dd94ae118b 100644 --- a/P5/Source/Specs/model.respLike.xml +++ b/P5/Source/Specs/model.respLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.segLike.xml b/P5/Source/Specs/model.segLike.xml index d5601a7ef3..ab419a58db 100644 --- a/P5/Source/Specs/model.segLike.xml +++ b/P5/Source/Specs/model.segLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.settingPart.xml b/P5/Source/Specs/model.settingPart.xml index e1c86d8482..e9e477ab6e 100644 --- a/P5/Source/Specs/model.settingPart.xml +++ b/P5/Source/Specs/model.settingPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.sourceDescPart.xml b/P5/Source/Specs/model.sourceDescPart.xml index cd404efdf7..61ad43bb34 100644 --- a/P5/Source/Specs/model.sourceDescPart.xml +++ b/P5/Source/Specs/model.sourceDescPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.specDescLike.xml b/P5/Source/Specs/model.specDescLike.xml index b2d7d0f8b2..88f2ca4594 100644 --- a/P5/Source/Specs/model.specDescLike.xml +++ b/P5/Source/Specs/model.specDescLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.stageLike.xml b/P5/Source/Specs/model.stageLike.xml index 900ada33b0..3a81f417aa 100644 --- a/P5/Source/Specs/model.stageLike.xml +++ b/P5/Source/Specs/model.stageLike.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.standOffPart.xml b/P5/Source/Specs/model.standOffPart.xml index 11c0b46a9b..0a22ae432b 100644 --- a/P5/Source/Specs/model.standOffPart.xml +++ b/P5/Source/Specs/model.standOffPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.teiHeaderPart.xml b/P5/Source/Specs/model.teiHeaderPart.xml index 2991c623b8..f60280913e 100644 --- a/P5/Source/Specs/model.teiHeaderPart.xml +++ b/P5/Source/Specs/model.teiHeaderPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.textDescPart.xml b/P5/Source/Specs/model.textDescPart.xml index 78120f80d3..8b7162bdc1 100644 --- a/P5/Source/Specs/model.textDescPart.xml +++ b/P5/Source/Specs/model.textDescPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.titlepagePart.xml b/P5/Source/Specs/model.titlepagePart.xml index 4534cbe3b5..7ce67bed5c 100644 --- a/P5/Source/Specs/model.titlepagePart.xml +++ b/P5/Source/Specs/model.titlepagePart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/model.xml b/P5/Source/Specs/model.xml index 31fe8a749d..d09274f70f 100644 --- a/P5/Source/Specs/model.xml +++ b/P5/Source/Specs/model.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/modelGrp.xml b/P5/Source/Specs/modelGrp.xml index 7267ad191c..ca4e11a00d 100644 --- a/P5/Source/Specs/modelGrp.xml +++ b/P5/Source/Specs/modelGrp.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/modelSequence.xml b/P5/Source/Specs/modelSequence.xml index b76bfdfa97..51f31ed829 100644 --- a/P5/Source/Specs/modelSequence.xml +++ b/P5/Source/Specs/modelSequence.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/moduleRef.xml b/P5/Source/Specs/moduleRef.xml index 65d7c7be4d..80563bf2e3 100644 --- a/P5/Source/Specs/moduleRef.xml +++ b/P5/Source/Specs/moduleRef.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/moduleSpec.xml b/P5/Source/Specs/moduleSpec.xml index 433fb78ebc..49f5e2123d 100644 --- a/P5/Source/Specs/moduleSpec.xml +++ b/P5/Source/Specs/moduleSpec.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/monogr.xml b/P5/Source/Specs/monogr.xml index b14dc8c461..1e4599a9af 100644 --- a/P5/Source/Specs/monogr.xml +++ b/P5/Source/Specs/monogr.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/mood.xml b/P5/Source/Specs/mood.xml index 29b642a98e..628538c53c 100644 --- a/P5/Source/Specs/mood.xml +++ b/P5/Source/Specs/mood.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/move.xml b/P5/Source/Specs/move.xml index 56ba897744..41358c33cb 100644 --- a/P5/Source/Specs/move.xml +++ b/P5/Source/Specs/move.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/msContents.xml b/P5/Source/Specs/msContents.xml index 73c08df756..5ec0587876 100644 --- a/P5/Source/Specs/msContents.xml +++ b/P5/Source/Specs/msContents.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/msDesc.xml b/P5/Source/Specs/msDesc.xml index da8621afd2..fc7440d97b 100644 --- a/P5/Source/Specs/msDesc.xml +++ b/P5/Source/Specs/msDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/msFrag.xml b/P5/Source/Specs/msFrag.xml index ecf91cb7a6..b8a51b5106 100644 --- a/P5/Source/Specs/msFrag.xml +++ b/P5/Source/Specs/msFrag.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/msIdentifier.xml b/P5/Source/Specs/msIdentifier.xml index 508a745707..07414f1311 100644 --- a/P5/Source/Specs/msIdentifier.xml +++ b/P5/Source/Specs/msIdentifier.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/msItem.xml b/P5/Source/Specs/msItem.xml index a27ab89b98..431746ea67 100644 --- a/P5/Source/Specs/msItem.xml +++ b/P5/Source/Specs/msItem.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/msItemStruct.xml b/P5/Source/Specs/msItemStruct.xml index 98f6a26bb3..dfae4ef9ab 100644 --- a/P5/Source/Specs/msItemStruct.xml +++ b/P5/Source/Specs/msItemStruct.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/msName.xml b/P5/Source/Specs/msName.xml index eadcc467ee..38f6294ca4 100644 --- a/P5/Source/Specs/msName.xml +++ b/P5/Source/Specs/msName.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/msPart.xml b/P5/Source/Specs/msPart.xml index 26a51986f2..23492df635 100644 --- a/P5/Source/Specs/msPart.xml +++ b/P5/Source/Specs/msPart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/musicNotation.xml b/P5/Source/Specs/musicNotation.xml index ab05959f7c..147bfda3c9 100644 --- a/P5/Source/Specs/musicNotation.xml +++ b/P5/Source/Specs/musicNotation.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/name.xml b/P5/Source/Specs/name.xml index 6c70961cc5..e9dd5e286a 100644 --- a/P5/Source/Specs/name.xml +++ b/P5/Source/Specs/name.xml @@ -1,4 +1,6 @@ - + + + name, proper noun 이름, 고유명사 名稱，特定名稱 diff --git a/P5/Source/Specs/nameLink.xml b/P5/Source/Specs/nameLink.xml index e01796e8b1..8e1ddc0eba 100644 --- a/P5/Source/Specs/nameLink.xml +++ b/P5/Source/Specs/nameLink.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/namespace.xml b/P5/Source/Specs/namespace.xml index 910c90ea44..083902310e 100644 --- a/P5/Source/Specs/namespace.xml +++ b/P5/Source/Specs/namespace.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/nationality.xml b/P5/Source/Specs/nationality.xml index a308adf8f4..bca3fe2130 100644 --- a/P5/Source/Specs/nationality.xml +++ b/P5/Source/Specs/nationality.xml @@ -1,4 +1,6 @@ - + + + nationality nationalité contains an informal description of a person's present or past nationality or citizenship. diff --git a/P5/Source/Specs/node.xml b/P5/Source/Specs/node.xml index 9396e9c03b..838cecea70 100644 --- a/P5/Source/Specs/node.xml +++ b/P5/Source/Specs/node.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/normalization.xml b/P5/Source/Specs/normalization.xml index b97117e589..2d456d9ab9 100644 --- a/P5/Source/Specs/normalization.xml +++ b/P5/Source/Specs/normalization.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/notatedMusic.xml b/P5/Source/Specs/notatedMusic.xml index a9d62e1b9c..a3f3851d1a 100644 --- a/P5/Source/Specs/notatedMusic.xml +++ b/P5/Source/Specs/notatedMusic.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/note.xml b/P5/Source/Specs/note.xml index 0798511e1a..a880eafaae 100644 --- a/P5/Source/Specs/note.xml +++ b/P5/Source/Specs/note.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/noteGrp.xml b/P5/Source/Specs/noteGrp.xml index 63489d1d0a..8aa224f178 100644 --- a/P5/Source/Specs/noteGrp.xml +++ b/P5/Source/Specs/noteGrp.xml @@ -1,4 +1,6 @@ - + + + note group contains a group of notes diff --git a/P5/Source/Specs/notesStmt.xml b/P5/Source/Specs/notesStmt.xml index 4bbcd6a711..6b13620a81 100644 --- a/P5/Source/Specs/notesStmt.xml +++ b/P5/Source/Specs/notesStmt.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/num.xml b/P5/Source/Specs/num.xml index c0786c0062..06c2701efe 100644 --- a/P5/Source/Specs/num.xml +++ b/P5/Source/Specs/num.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/number.xml b/P5/Source/Specs/number.xml index 63446c5ead..cb387e9f25 100644 --- a/P5/Source/Specs/number.xml +++ b/P5/Source/Specs/number.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/numeric.xml b/P5/Source/Specs/numeric.xml index 61dd6cedce..fc94f495b9 100644 --- a/P5/Source/Specs/numeric.xml +++ b/P5/Source/Specs/numeric.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/nym.xml b/P5/Source/Specs/nym.xml index 5e49136cad..412bd2f4fa 100644 --- a/P5/Source/Specs/nym.xml +++ b/P5/Source/Specs/nym.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/oRef.xml b/P5/Source/Specs/oRef.xml index 5a5608fcdb..a386b7aeed 100644 --- a/P5/Source/Specs/oRef.xml +++ b/P5/Source/Specs/oRef.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/object.xml b/P5/Source/Specs/object.xml index 1d49e2339c..9fea6e1389 100644 --- a/P5/Source/Specs/object.xml +++ b/P5/Source/Specs/object.xml @@ -1,4 +1,6 @@ - + + + contains a description of a single identifiable physical object. enthält die Beschreibung eines einzelnen identifizierbaren physischen Objekts. diff --git a/P5/Source/Specs/objectDesc.xml b/P5/Source/Specs/objectDesc.xml index f3367b7fe6..49058f9b60 100644 --- a/P5/Source/Specs/objectDesc.xml +++ b/P5/Source/Specs/objectDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/objectIdentifier.xml b/P5/Source/Specs/objectIdentifier.xml index 04a17e9922..e18550165a 100644 --- a/P5/Source/Specs/objectIdentifier.xml +++ b/P5/Source/Specs/objectIdentifier.xml @@ -1,4 +1,6 @@ - + + + object identifier Objektidentifikator diff --git a/P5/Source/Specs/objectName.xml b/P5/Source/Specs/objectName.xml index d53f53b8af..b81d46a684 100644 --- a/P5/Source/Specs/objectName.xml +++ b/P5/Source/Specs/objectName.xml @@ -1,4 +1,6 @@ - + + + name of an object Name eines Objekts contains a proper noun or noun phrase used to refer to an object. diff --git a/P5/Source/Specs/objectType.xml b/P5/Source/Specs/objectType.xml index e8db622519..6502e4177c 100644 --- a/P5/Source/Specs/objectType.xml +++ b/P5/Source/Specs/objectType.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/occupation.xml b/P5/Source/Specs/occupation.xml index 59416ab32e..43dc51d239 100644 --- a/P5/Source/Specs/occupation.xml +++ b/P5/Source/Specs/occupation.xml @@ -1,4 +1,6 @@ - + + + occupation activité contains an informal description of a person's trade, profession or occupation. diff --git a/P5/Source/Specs/offset.xml b/P5/Source/Specs/offset.xml index 4014780b5a..568ae446ed 100644 --- a/P5/Source/Specs/offset.xml +++ b/P5/Source/Specs/offset.xml @@ -1,4 +1,6 @@ - + + + offset distance relative marks that part of a relative temporal or spatial expression which indicates the direction of the offset between the two place names, dates, or diff --git a/P5/Source/Specs/opener.xml b/P5/Source/Specs/opener.xml index ec89c7d444..ff5e5039da 100644 --- a/P5/Source/Specs/opener.xml +++ b/P5/Source/Specs/opener.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/org.xml b/P5/Source/Specs/org.xml index cccb50a29c..8c888d73c2 100644 --- a/P5/Source/Specs/org.xml +++ b/P5/Source/Specs/org.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/orgName.xml b/P5/Source/Specs/orgName.xml index 0afffd8701..53fdb586d7 100644 --- a/P5/Source/Specs/orgName.xml +++ b/P5/Source/Specs/orgName.xml @@ -1,4 +1,6 @@ - + + + organization name 조직명 組織名稱 diff --git a/P5/Source/Specs/orig.xml b/P5/Source/Specs/orig.xml index 9c049b722f..d418ce08bd 100644 --- a/P5/Source/Specs/orig.xml +++ b/P5/Source/Specs/orig.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/origDate.xml b/P5/Source/Specs/origDate.xml index b91153b077..fe9da4b27f 100644 --- a/P5/Source/Specs/origDate.xml +++ b/P5/Source/Specs/origDate.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/origPlace.xml b/P5/Source/Specs/origPlace.xml index a112425a27..9771eecc11 100644 --- a/P5/Source/Specs/origPlace.xml +++ b/P5/Source/Specs/origPlace.xml @@ -1,4 +1,6 @@ - + + + origin place 생산 장소 diff --git a/P5/Source/Specs/origin.xml b/P5/Source/Specs/origin.xml index cb7d9560e7..f3c318c27f 100644 --- a/P5/Source/Specs/origin.xml +++ b/P5/Source/Specs/origin.xml @@ -1,4 +1,6 @@ - + + + origin origine contains any descriptive or other information diff --git a/P5/Source/Specs/orth.xml b/P5/Source/Specs/orth.xml index eb9172b5b7..8b9152649e 100644 --- a/P5/Source/Specs/orth.xml +++ b/P5/Source/Specs/orth.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/outputRendition.xml b/P5/Source/Specs/outputRendition.xml index 9bdaeffe86..d486a403ef 100644 --- a/P5/Source/Specs/outputRendition.xml +++ b/P5/Source/Specs/outputRendition.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/p.xml b/P5/Source/Specs/p.xml index e1b14d504b..fec443c9b3 100644 --- a/P5/Source/Specs/p.xml +++ b/P5/Source/Specs/p.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/pRef.xml b/P5/Source/Specs/pRef.xml index 68ea99eb49..2d35095af1 100644 --- a/P5/Source/Specs/pRef.xml +++ b/P5/Source/Specs/pRef.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/param.xml b/P5/Source/Specs/param.xml index 4eec04bfbd..6fed3ad2aa 100644 --- a/P5/Source/Specs/param.xml +++ b/P5/Source/Specs/param.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/paramList.xml b/P5/Source/Specs/paramList.xml index 1824691268..50ba643cc6 100644 --- a/P5/Source/Specs/paramList.xml +++ b/P5/Source/Specs/paramList.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/paramSpec.xml b/P5/Source/Specs/paramSpec.xml index 3e5f7daead..b32bb2ec4b 100644 --- a/P5/Source/Specs/paramSpec.xml +++ b/P5/Source/Specs/paramSpec.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/particDesc.xml b/P5/Source/Specs/particDesc.xml index 0e2b6df990..1cf432ee1a 100644 --- a/P5/Source/Specs/particDesc.xml +++ b/P5/Source/Specs/particDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/path.xml b/P5/Source/Specs/path.xml index bc6af60964..fd203e73b6 100644 --- a/P5/Source/Specs/path.xml +++ b/P5/Source/Specs/path.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/pause.xml b/P5/Source/Specs/pause.xml index 263008f955..541ed408b0 100644 --- a/P5/Source/Specs/pause.xml +++ b/P5/Source/Specs/pause.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/pb.xml b/P5/Source/Specs/pb.xml index e4b83b5881..c8dd57831c 100644 --- a/P5/Source/Specs/pb.xml +++ b/P5/Source/Specs/pb.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/pc.xml b/P5/Source/Specs/pc.xml index 84f5b40628..a1d5d8d54a 100644 --- a/P5/Source/Specs/pc.xml +++ b/P5/Source/Specs/pc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/per.xml b/P5/Source/Specs/per.xml index b4d9299b45..e56026742e 100644 --- a/P5/Source/Specs/per.xml +++ b/P5/Source/Specs/per.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/performance.xml b/P5/Source/Specs/performance.xml index 49bf2edd14..b35e13e3e3 100644 --- a/P5/Source/Specs/performance.xml +++ b/P5/Source/Specs/performance.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/persName.xml b/P5/Source/Specs/persName.xml index 25c76698ad..91e400b877 100644 --- a/P5/Source/Specs/persName.xml +++ b/P5/Source/Specs/persName.xml @@ -1,4 +1,6 @@ - + + + personal name 개인 이름 個人名稱 diff --git a/P5/Source/Specs/persPronouns.xml b/P5/Source/Specs/persPronouns.xml index e2e65c67fe..818f4c30cc 100644 --- a/P5/Source/Specs/persPronouns.xml +++ b/P5/Source/Specs/persPronouns.xml @@ -1,4 +1,6 @@ - + + + personal pronouns indicates the personal pronouns used, or assumed to be used, by the individual being described. diff --git a/P5/Source/Specs/person.xml b/P5/Source/Specs/person.xml index 64eef6dcd0..68f6af3ec5 100644 --- a/P5/Source/Specs/person.xml +++ b/P5/Source/Specs/person.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/personGrp.xml b/P5/Source/Specs/personGrp.xml index 5e1ec78f8d..5542cddf31 100644 --- a/P5/Source/Specs/personGrp.xml +++ b/P5/Source/Specs/personGrp.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/persona.xml b/P5/Source/Specs/persona.xml index 91a38e340a..39ee662a6a 100644 --- a/P5/Source/Specs/persona.xml +++ b/P5/Source/Specs/persona.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/phr.xml b/P5/Source/Specs/phr.xml index 83de82fd78..552ef58b2e 100644 --- a/P5/Source/Specs/phr.xml +++ b/P5/Source/Specs/phr.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/physDesc.xml b/P5/Source/Specs/physDesc.xml index 94685466e1..284df79517 100644 --- a/P5/Source/Specs/physDesc.xml +++ b/P5/Source/Specs/physDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/place.xml b/P5/Source/Specs/place.xml index ec9b883172..1ee05ebe3d 100644 --- a/P5/Source/Specs/place.xml +++ b/P5/Source/Specs/place.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/placeName.xml b/P5/Source/Specs/placeName.xml index 8f1da61e5a..92b726af47 100644 --- a/P5/Source/Specs/placeName.xml +++ b/P5/Source/Specs/placeName.xml @@ -1,4 +1,6 @@ - + + + place name nom de lieu contains an absolute or relative place name. diff --git a/P5/Source/Specs/population.xml b/P5/Source/Specs/population.xml index c7345cd428..8dad06a3c1 100644 --- a/P5/Source/Specs/population.xml +++ b/P5/Source/Specs/population.xml @@ -1,4 +1,6 @@ - + + + population population contains information about the population of a place. diff --git a/P5/Source/Specs/pos.xml b/P5/Source/Specs/pos.xml index ac2037416d..087aad96b1 100644 --- a/P5/Source/Specs/pos.xml +++ b/P5/Source/Specs/pos.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/postBox.xml b/P5/Source/Specs/postBox.xml index 4eb7b47412..e889aec6a3 100644 --- a/P5/Source/Specs/postBox.xml +++ b/P5/Source/Specs/postBox.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/postCode.xml b/P5/Source/Specs/postCode.xml index 8f6a3ec265..ec1382a9f7 100644 --- a/P5/Source/Specs/postCode.xml +++ b/P5/Source/Specs/postCode.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/postscript.xml b/P5/Source/Specs/postscript.xml index af2f6938f1..5ff28a29a5 100644 --- a/P5/Source/Specs/postscript.xml +++ b/P5/Source/Specs/postscript.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/precision.xml b/P5/Source/Specs/precision.xml index 7d0f01dd2d..46d6fff714 100644 --- a/P5/Source/Specs/precision.xml +++ b/P5/Source/Specs/precision.xml @@ -1,4 +1,6 @@ - + + + indicates the numerical accuracy or precision associated with some aspect of the text markup. diff --git a/P5/Source/Specs/prefixDef.xml b/P5/Source/Specs/prefixDef.xml index fce4879962..8291193a01 100644 --- a/P5/Source/Specs/prefixDef.xml +++ b/P5/Source/Specs/prefixDef.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/preparedness.xml b/P5/Source/Specs/preparedness.xml index 0b2189fc40..55741f0bf9 100644 --- a/P5/Source/Specs/preparedness.xml +++ b/P5/Source/Specs/preparedness.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/principal.xml b/P5/Source/Specs/principal.xml index 4c933f4431..e5c2e4e77d 100644 --- a/P5/Source/Specs/principal.xml +++ b/P5/Source/Specs/principal.xml @@ -1,4 +1,6 @@ - + + + principal researcher chercheur principal 책임 연구자 diff --git a/P5/Source/Specs/profileDesc.xml b/P5/Source/Specs/profileDesc.xml index fb11c233f7..171410364b 100644 --- a/P5/Source/Specs/profileDesc.xml +++ b/P5/Source/Specs/profileDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/projectDesc.xml b/P5/Source/Specs/projectDesc.xml index c8e50f0b22..56441a21dc 100644 --- a/P5/Source/Specs/projectDesc.xml +++ b/P5/Source/Specs/projectDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/prologue.xml b/P5/Source/Specs/prologue.xml index 947fdafd2d..abdfb7e041 100644 --- a/P5/Source/Specs/prologue.xml +++ b/P5/Source/Specs/prologue.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/pron.xml b/P5/Source/Specs/pron.xml index 7a7d2424ea..d5158e0914 100644 --- a/P5/Source/Specs/pron.xml +++ b/P5/Source/Specs/pron.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/provenance.xml b/P5/Source/Specs/provenance.xml index f201996069..71b78766da 100644 --- a/P5/Source/Specs/provenance.xml +++ b/P5/Source/Specs/provenance.xml @@ -1,4 +1,6 @@ - + + + provenance provenance contains any descriptive or other information diff --git a/P5/Source/Specs/ptr.xml b/P5/Source/Specs/ptr.xml index 2fb1bf6c13..d04b16f53b 100644 --- a/P5/Source/Specs/ptr.xml +++ b/P5/Source/Specs/ptr.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/pubPlace.xml b/P5/Source/Specs/pubPlace.xml index ca26d0a9c2..628111b22d 100644 --- a/P5/Source/Specs/pubPlace.xml +++ b/P5/Source/Specs/pubPlace.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/publicationStmt.xml b/P5/Source/Specs/publicationStmt.xml index 37df6d2352..d436a01003 100644 --- a/P5/Source/Specs/publicationStmt.xml +++ b/P5/Source/Specs/publicationStmt.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/publisher.xml b/P5/Source/Specs/publisher.xml index 2037b6a70b..b43cdbe04c 100644 --- a/P5/Source/Specs/publisher.xml +++ b/P5/Source/Specs/publisher.xml @@ -1,4 +1,6 @@ - + + + publisher editorial éditeur diff --git a/P5/Source/Specs/punctuation.xml b/P5/Source/Specs/punctuation.xml index 93821375bc..bd3bd1012c 100644 --- a/P5/Source/Specs/punctuation.xml +++ b/P5/Source/Specs/punctuation.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/purpose.xml b/P5/Source/Specs/purpose.xml index 9aee9bb848..857fee64f9 100644 --- a/P5/Source/Specs/purpose.xml +++ b/P5/Source/Specs/purpose.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/q.xml b/P5/Source/Specs/q.xml index 99fd3d39b6..5e930fc498 100644 --- a/P5/Source/Specs/q.xml +++ b/P5/Source/Specs/q.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/quotation.xml b/P5/Source/Specs/quotation.xml index 1e124d2630..53241f45dc 100644 --- a/P5/Source/Specs/quotation.xml +++ b/P5/Source/Specs/quotation.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/quote.xml b/P5/Source/Specs/quote.xml index 36d43a000f..4efc5359d8 100644 --- a/P5/Source/Specs/quote.xml +++ b/P5/Source/Specs/quote.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/rb.xml b/P5/Source/Specs/rb.xml index cffe1d7e11..9a3b993fa2 100644 --- a/P5/Source/Specs/rb.xml +++ b/P5/Source/Specs/rb.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/rdg.xml b/P5/Source/Specs/rdg.xml index 519ed3a6a7..acdfe07712 100644 --- a/P5/Source/Specs/rdg.xml +++ b/P5/Source/Specs/rdg.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/rdgGrp.xml b/P5/Source/Specs/rdgGrp.xml index 487da66324..957e83f3a3 100644 --- a/P5/Source/Specs/rdgGrp.xml +++ b/P5/Source/Specs/rdgGrp.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/re.xml b/P5/Source/Specs/re.xml index 2fbcd74061..13dd822119 100644 --- a/P5/Source/Specs/re.xml +++ b/P5/Source/Specs/re.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/recording.xml b/P5/Source/Specs/recording.xml index c312a4eec9..7131f9ebc3 100644 --- a/P5/Source/Specs/recording.xml +++ b/P5/Source/Specs/recording.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/recordingStmt.xml b/P5/Source/Specs/recordingStmt.xml index 3161ca2d7b..01e0e456be 100644 --- a/P5/Source/Specs/recordingStmt.xml +++ b/P5/Source/Specs/recordingStmt.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/redo.xml b/P5/Source/Specs/redo.xml index 0da621df85..786a606ad2 100644 --- a/P5/Source/Specs/redo.xml +++ b/P5/Source/Specs/redo.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/ref.xml b/P5/Source/Specs/ref.xml index d769a34f05..736e9099d5 100644 --- a/P5/Source/Specs/ref.xml +++ b/P5/Source/Specs/ref.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/refState.xml b/P5/Source/Specs/refState.xml index b808c03b4b..b31c07a137 100644 --- a/P5/Source/Specs/refState.xml +++ b/P5/Source/Specs/refState.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/refsDecl.xml b/P5/Source/Specs/refsDecl.xml index 02befb6aa4..39a83d06d1 100644 --- a/P5/Source/Specs/refsDecl.xml +++ b/P5/Source/Specs/refsDecl.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/reg.xml b/P5/Source/Specs/reg.xml index 1429cc50c0..a9d7df25cb 100644 --- a/P5/Source/Specs/reg.xml +++ b/P5/Source/Specs/reg.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/region.xml b/P5/Source/Specs/region.xml index ed2cf9dd95..6eeeebf99a 100644 --- a/P5/Source/Specs/region.xml +++ b/P5/Source/Specs/region.xml @@ -1,4 +1,6 @@ - + + + region région contains the name of an administrative unit such as a state, province, or county, larger diff --git a/P5/Source/Specs/relatedItem.xml b/P5/Source/Specs/relatedItem.xml index 7e1943e7cb..ef12cb724d 100644 --- a/P5/Source/Specs/relatedItem.xml +++ b/P5/Source/Specs/relatedItem.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/relation.xml b/P5/Source/Specs/relation.xml index 7813d5d2ac..9db6be91db 100644 --- a/P5/Source/Specs/relation.xml +++ b/P5/Source/Specs/relation.xml @@ -1,4 +1,6 @@ - + + + relationship 관련성 人際關係 diff --git a/P5/Source/Specs/remarks.xml b/P5/Source/Specs/remarks.xml index eab9bc66a2..2fbbcb8413 100644 --- a/P5/Source/Specs/remarks.xml +++ b/P5/Source/Specs/remarks.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/rendition.xml b/P5/Source/Specs/rendition.xml index 7cadc85f19..b732b40468 100644 --- a/P5/Source/Specs/rendition.xml +++ b/P5/Source/Specs/rendition.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/repository.xml b/P5/Source/Specs/repository.xml index be1df64396..aa9dc49ac1 100644 --- a/P5/Source/Specs/repository.xml +++ b/P5/Source/Specs/repository.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/residence.xml b/P5/Source/Specs/residence.xml index c0e3cac801..64bc701ce1 100644 --- a/P5/Source/Specs/residence.xml +++ b/P5/Source/Specs/residence.xml @@ -1,4 +1,6 @@ - + + + residence 거주 住所 diff --git a/P5/Source/Specs/resp.xml b/P5/Source/Specs/resp.xml index 0fa4f7499a..4319b35f03 100644 --- a/P5/Source/Specs/resp.xml +++ b/P5/Source/Specs/resp.xml @@ -1,4 +1,6 @@ - + + + responsibility 책임성 diff --git a/P5/Source/Specs/respStmt.xml b/P5/Source/Specs/respStmt.xml index 381e7fe5d0..7393d5c125 100644 --- a/P5/Source/Specs/respStmt.xml +++ b/P5/Source/Specs/respStmt.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/respons.xml b/P5/Source/Specs/respons.xml index 673454b07c..50a01c8c01 100644 --- a/P5/Source/Specs/respons.xml +++ b/P5/Source/Specs/respons.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/restore.xml b/P5/Source/Specs/restore.xml index 97b0704019..5856c337e1 100644 --- a/P5/Source/Specs/restore.xml +++ b/P5/Source/Specs/restore.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/retrace.xml b/P5/Source/Specs/retrace.xml index 7fe3ce2c36..88ff77aa5c 100644 --- a/P5/Source/Specs/retrace.xml +++ b/P5/Source/Specs/retrace.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/revisionDesc.xml b/P5/Source/Specs/revisionDesc.xml index 1f37dff596..811f8d6e56 100644 --- a/P5/Source/Specs/revisionDesc.xml +++ b/P5/Source/Specs/revisionDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/rhyme.xml b/P5/Source/Specs/rhyme.xml index a491783533..44c9cc969f 100644 --- a/P5/Source/Specs/rhyme.xml +++ b/P5/Source/Specs/rhyme.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/role.xml b/P5/Source/Specs/role.xml index a39524281a..672e332b30 100644 --- a/P5/Source/Specs/role.xml +++ b/P5/Source/Specs/role.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/roleDesc.xml b/P5/Source/Specs/roleDesc.xml index 4192d1f359..b91187f0c4 100644 --- a/P5/Source/Specs/roleDesc.xml +++ b/P5/Source/Specs/roleDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/roleName.xml b/P5/Source/Specs/roleName.xml index 9986b7c983..592f62728f 100644 --- a/P5/Source/Specs/roleName.xml +++ b/P5/Source/Specs/roleName.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/root.xml b/P5/Source/Specs/root.xml index 4e704653b2..d16d8672fd 100644 --- a/P5/Source/Specs/root.xml +++ b/P5/Source/Specs/root.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/row.xml b/P5/Source/Specs/row.xml index db4c1e60aa..33e81bc137 100644 --- a/P5/Source/Specs/row.xml +++ b/P5/Source/Specs/row.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/rs.xml b/P5/Source/Specs/rs.xml index 8e49a17a7e..7110efa93c 100644 --- a/P5/Source/Specs/rs.xml +++ b/P5/Source/Specs/rs.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/rt.xml b/P5/Source/Specs/rt.xml index 71c2cd09c8..c0b562a740 100644 --- a/P5/Source/Specs/rt.xml +++ b/P5/Source/Specs/rt.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/rubric.xml b/P5/Source/Specs/rubric.xml index 584606f6ef..f1bfae2e68 100644 --- a/P5/Source/Specs/rubric.xml +++ b/P5/Source/Specs/rubric.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/ruby.xml b/P5/Source/Specs/ruby.xml index db2f095b75..ed9ed1a697 100644 --- a/P5/Source/Specs/ruby.xml +++ b/P5/Source/Specs/ruby.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/s.xml b/P5/Source/Specs/s.xml index 2df1d961fc..9d434e3a6d 100644 --- a/P5/Source/Specs/s.xml +++ b/P5/Source/Specs/s.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/said.xml b/P5/Source/Specs/said.xml index 28f5966631..7424cb5186 100644 --- a/P5/Source/Specs/said.xml +++ b/P5/Source/Specs/said.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/salute.xml b/P5/Source/Specs/salute.xml index 5dedecdf62..eaef9619b3 100644 --- a/P5/Source/Specs/salute.xml +++ b/P5/Source/Specs/salute.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/samplingDecl.xml b/P5/Source/Specs/samplingDecl.xml index 005ece69e4..2ea1365ea5 100644 --- a/P5/Source/Specs/samplingDecl.xml +++ b/P5/Source/Specs/samplingDecl.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/schemaRef.xml b/P5/Source/Specs/schemaRef.xml index f5f622ddd2..94115574da 100644 --- a/P5/Source/Specs/schemaRef.xml +++ b/P5/Source/Specs/schemaRef.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/schemaSpec.xml b/P5/Source/Specs/schemaSpec.xml index 8389f70a1d..02ef7756cf 100644 --- a/P5/Source/Specs/schemaSpec.xml +++ b/P5/Source/Specs/schemaSpec.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/scriptDesc.xml b/P5/Source/Specs/scriptDesc.xml index ead5c2de53..1fe086068a 100644 --- a/P5/Source/Specs/scriptDesc.xml +++ b/P5/Source/Specs/scriptDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/scriptNote.xml b/P5/Source/Specs/scriptNote.xml index 52d4803d81..0fbbb277ed 100644 --- a/P5/Source/Specs/scriptNote.xml +++ b/P5/Source/Specs/scriptNote.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/scriptStmt.xml b/P5/Source/Specs/scriptStmt.xml index 4f97bc576e..44b57d0246 100644 --- a/P5/Source/Specs/scriptStmt.xml +++ b/P5/Source/Specs/scriptStmt.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/seal.xml b/P5/Source/Specs/seal.xml index 8d70bb1b56..0ad0c62de6 100644 --- a/P5/Source/Specs/seal.xml +++ b/P5/Source/Specs/seal.xml @@ -1,4 +1,6 @@ - + + + seal sceau contains a description of one seal or similar applied to the object described diff --git a/P5/Source/Specs/sealDesc.xml b/P5/Source/Specs/sealDesc.xml index bc6f609024..54905c1d4f 100644 --- a/P5/Source/Specs/sealDesc.xml +++ b/P5/Source/Specs/sealDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/secFol.xml b/P5/Source/Specs/secFol.xml index 1affd7b4cc..ca5f89e229 100644 --- a/P5/Source/Specs/secFol.xml +++ b/P5/Source/Specs/secFol.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/secl.xml b/P5/Source/Specs/secl.xml index 3518cb120c..f83a261942 100644 --- a/P5/Source/Specs/secl.xml +++ b/P5/Source/Specs/secl.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/seg.xml b/P5/Source/Specs/seg.xml index a82d6d40fe..4fc42aca7d 100644 --- a/P5/Source/Specs/seg.xml +++ b/P5/Source/Specs/seg.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/segmentation.xml b/P5/Source/Specs/segmentation.xml index fe76c035cf..148322e2d3 100644 --- a/P5/Source/Specs/segmentation.xml +++ b/P5/Source/Specs/segmentation.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/sense.xml b/P5/Source/Specs/sense.xml index 2c0991d7f7..dc7f3cbc5f 100644 --- a/P5/Source/Specs/sense.xml +++ b/P5/Source/Specs/sense.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/sequence.xml b/P5/Source/Specs/sequence.xml index bae4321128..6af5939002 100644 --- a/P5/Source/Specs/sequence.xml +++ b/P5/Source/Specs/sequence.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/series.xml b/P5/Source/Specs/series.xml index c2d2cda2f7..254b30b4a0 100644 --- a/P5/Source/Specs/series.xml +++ b/P5/Source/Specs/series.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/seriesStmt.xml b/P5/Source/Specs/seriesStmt.xml index 63698a8965..29e503c1ac 100644 --- a/P5/Source/Specs/seriesStmt.xml +++ b/P5/Source/Specs/seriesStmt.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/set.xml b/P5/Source/Specs/set.xml index 47cfbfa483..1b5d08b0d4 100644 --- a/P5/Source/Specs/set.xml +++ b/P5/Source/Specs/set.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/setting.xml b/P5/Source/Specs/setting.xml index 64c800e7b1..69a5956412 100644 --- a/P5/Source/Specs/setting.xml +++ b/P5/Source/Specs/setting.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/settingDesc.xml b/P5/Source/Specs/settingDesc.xml index ccf1394356..b02d9e58bc 100644 --- a/P5/Source/Specs/settingDesc.xml +++ b/P5/Source/Specs/settingDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/settlement.xml b/P5/Source/Specs/settlement.xml index 32beba5df6..3efa4ac5aa 100644 --- a/P5/Source/Specs/settlement.xml +++ b/P5/Source/Specs/settlement.xml @@ -1,4 +1,6 @@ - + + + settlement lieu de peuplement contains the name of a settlement such as a city, town, or village identified as a single geo-political or administrative unit. diff --git a/P5/Source/Specs/sex.xml b/P5/Source/Specs/sex.xml index 7ee34128e7..3b6f8af157 100644 --- a/P5/Source/Specs/sex.xml +++ b/P5/Source/Specs/sex.xml @@ -1,4 +1,6 @@ - + + + sex sexe specifies the sex of an organism. diff --git a/P5/Source/Specs/shift.xml b/P5/Source/Specs/shift.xml index 062aeb1ea7..b73d1fd52e 100644 --- a/P5/Source/Specs/shift.xml +++ b/P5/Source/Specs/shift.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/sic.xml b/P5/Source/Specs/sic.xml index 8231191379..83b7b9ace4 100644 --- a/P5/Source/Specs/sic.xml +++ b/P5/Source/Specs/sic.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/signatures.xml b/P5/Source/Specs/signatures.xml index da4fb74723..fbf77d5463 100644 --- a/P5/Source/Specs/signatures.xml +++ b/P5/Source/Specs/signatures.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/signed.xml b/P5/Source/Specs/signed.xml index c8a8f0cf93..f49316e0e0 100644 --- a/P5/Source/Specs/signed.xml +++ b/P5/Source/Specs/signed.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/soCalled.xml b/P5/Source/Specs/soCalled.xml index 2bbe980c98..0557283655 100644 --- a/P5/Source/Specs/soCalled.xml +++ b/P5/Source/Specs/soCalled.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/socecStatus.xml b/P5/Source/Specs/socecStatus.xml index 5b91821cfa..686b51cf0c 100644 --- a/P5/Source/Specs/socecStatus.xml +++ b/P5/Source/Specs/socecStatus.xml @@ -1,4 +1,6 @@ - + + + socio-economic status statut socio-économique 사회-경제적 지위 diff --git a/P5/Source/Specs/sound.xml b/P5/Source/Specs/sound.xml index 2c2ff455e8..44400d7a3b 100644 --- a/P5/Source/Specs/sound.xml +++ b/P5/Source/Specs/sound.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/source.xml b/P5/Source/Specs/source.xml index e947709180..07aab737f2 100644 --- a/P5/Source/Specs/source.xml +++ b/P5/Source/Specs/source.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/sourceDesc.xml b/P5/Source/Specs/sourceDesc.xml index c6cd51625e..cbf92ec831 100644 --- a/P5/Source/Specs/sourceDesc.xml +++ b/P5/Source/Specs/sourceDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/sourceDoc.xml b/P5/Source/Specs/sourceDoc.xml index e1139403c7..745cfaa0ab 100644 --- a/P5/Source/Specs/sourceDoc.xml +++ b/P5/Source/Specs/sourceDoc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/sp.xml b/P5/Source/Specs/sp.xml index 2ea0276125..304e05c17b 100644 --- a/P5/Source/Specs/sp.xml +++ b/P5/Source/Specs/sp.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/spGrp.xml b/P5/Source/Specs/spGrp.xml index e124a5f898..74189f9318 100644 --- a/P5/Source/Specs/spGrp.xml +++ b/P5/Source/Specs/spGrp.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/space.xml b/P5/Source/Specs/space.xml index 896094e328..0ccf08fe91 100644 --- a/P5/Source/Specs/space.xml +++ b/P5/Source/Specs/space.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/span.xml b/P5/Source/Specs/span.xml index a0d2d2a16c..e4db80bedc 100644 --- a/P5/Source/Specs/span.xml +++ b/P5/Source/Specs/span.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/spanGrp.xml b/P5/Source/Specs/spanGrp.xml index 3f86d96918..3aa3efa293 100644 --- a/P5/Source/Specs/spanGrp.xml +++ b/P5/Source/Specs/spanGrp.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/speaker.xml b/P5/Source/Specs/speaker.xml index 46d6ded603..97f236f2b0 100644 --- a/P5/Source/Specs/speaker.xml +++ b/P5/Source/Specs/speaker.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/specDesc.xml b/P5/Source/Specs/specDesc.xml index 35f3f5b1d6..1d56a95780 100644 --- a/P5/Source/Specs/specDesc.xml +++ b/P5/Source/Specs/specDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/specGrp.xml b/P5/Source/Specs/specGrp.xml index 961e3e511d..3759c4c82b 100644 --- a/P5/Source/Specs/specGrp.xml +++ b/P5/Source/Specs/specGrp.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/specGrpRef.xml b/P5/Source/Specs/specGrpRef.xml index 3e914fd8ae..3362ea72d9 100644 --- a/P5/Source/Specs/specGrpRef.xml +++ b/P5/Source/Specs/specGrpRef.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/specList.xml b/P5/Source/Specs/specList.xml index daf80dd6cd..c45e6dee1e 100644 --- a/P5/Source/Specs/specList.xml +++ b/P5/Source/Specs/specList.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/sponsor.xml b/P5/Source/Specs/sponsor.xml index 95ef299da2..6fafac89ab 100644 --- a/P5/Source/Specs/sponsor.xml +++ b/P5/Source/Specs/sponsor.xml @@ -1,4 +1,6 @@ - + + + sponsor commanditaire Förderer diff --git a/P5/Source/Specs/stage.xml b/P5/Source/Specs/stage.xml index decf7c7fdd..40b592d57c 100644 --- a/P5/Source/Specs/stage.xml +++ b/P5/Source/Specs/stage.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/stamp.xml b/P5/Source/Specs/stamp.xml index fbf1ad349a..a058966f22 100644 --- a/P5/Source/Specs/stamp.xml +++ b/P5/Source/Specs/stamp.xml @@ -1,4 +1,6 @@ - + + + stamp cachet contains a word or phrase describing a stamp or similar device. diff --git a/P5/Source/Specs/standOff.xml b/P5/Source/Specs/standOff.xml index 2fd9814065..679102b394 100644 --- a/P5/Source/Specs/standOff.xml +++ b/P5/Source/Specs/standOff.xml @@ -1,3 +1,4 @@ + + + + state statut contains a description of some status or quality attributed to a person, place, or organization often at some specific time or for a specific date range. diff --git a/P5/Source/Specs/stdVals.xml b/P5/Source/Specs/stdVals.xml index f74bb60d36..95d2965314 100644 --- a/P5/Source/Specs/stdVals.xml +++ b/P5/Source/Specs/stdVals.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/street.xml b/P5/Source/Specs/street.xml index b5d8888ae2..7ad04f1d0f 100644 --- a/P5/Source/Specs/street.xml +++ b/P5/Source/Specs/street.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/stress.xml b/P5/Source/Specs/stress.xml index 2d59a1b40f..e00c87c03b 100644 --- a/P5/Source/Specs/stress.xml +++ b/P5/Source/Specs/stress.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/string.xml b/P5/Source/Specs/string.xml index e2cfb527f6..7706028626 100644 --- a/P5/Source/Specs/string.xml +++ b/P5/Source/Specs/string.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/styleDefDecl.xml b/P5/Source/Specs/styleDefDecl.xml index 62809d322c..6809677d58 100644 --- a/P5/Source/Specs/styleDefDecl.xml +++ b/P5/Source/Specs/styleDefDecl.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/subc.xml b/P5/Source/Specs/subc.xml index 08a1897755..5cc296352c 100644 --- a/P5/Source/Specs/subc.xml +++ b/P5/Source/Specs/subc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/subst.xml b/P5/Source/Specs/subst.xml index 5ae7359022..3e7b2cc575 100644 --- a/P5/Source/Specs/subst.xml +++ b/P5/Source/Specs/subst.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/substJoin.xml b/P5/Source/Specs/substJoin.xml index cc6101fd28..70c91a8138 100644 --- a/P5/Source/Specs/substJoin.xml +++ b/P5/Source/Specs/substJoin.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/summary.xml b/P5/Source/Specs/summary.xml index 658ee76957..6e4e6db0c7 100644 --- a/P5/Source/Specs/summary.xml +++ b/P5/Source/Specs/summary.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/superEntry.xml b/P5/Source/Specs/superEntry.xml index cab6f06146..65220fab2b 100644 --- a/P5/Source/Specs/superEntry.xml +++ b/P5/Source/Specs/superEntry.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/supplied.xml b/P5/Source/Specs/supplied.xml index 8ca8261e1b..029f9d2972 100644 --- a/P5/Source/Specs/supplied.xml +++ b/P5/Source/Specs/supplied.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/support.xml b/P5/Source/Specs/support.xml index 93018995bd..ac90f6d69a 100644 --- a/P5/Source/Specs/support.xml +++ b/P5/Source/Specs/support.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/supportDesc.xml b/P5/Source/Specs/supportDesc.xml index 6e7aa4bbdc..093c210637 100644 --- a/P5/Source/Specs/supportDesc.xml +++ b/P5/Source/Specs/supportDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/surface.xml b/P5/Source/Specs/surface.xml index e6c82216d8..1583ed2125 100644 --- a/P5/Source/Specs/surface.xml +++ b/P5/Source/Specs/surface.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/surfaceGrp.xml b/P5/Source/Specs/surfaceGrp.xml index a519536497..8ac125249e 100644 --- a/P5/Source/Specs/surfaceGrp.xml +++ b/P5/Source/Specs/surfaceGrp.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/surname.xml b/P5/Source/Specs/surname.xml index 77c00ff363..85d72fc318 100644 --- a/P5/Source/Specs/surname.xml +++ b/P5/Source/Specs/surname.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/surplus.xml b/P5/Source/Specs/surplus.xml index 0403081c34..dbbda6824d 100644 --- a/P5/Source/Specs/surplus.xml +++ b/P5/Source/Specs/surplus.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/surrogates.xml b/P5/Source/Specs/surrogates.xml index 569de8ced0..6623e368d4 100644 --- a/P5/Source/Specs/surrogates.xml +++ b/P5/Source/Specs/surrogates.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/syll.xml b/P5/Source/Specs/syll.xml index c9901c316c..0a1749ef40 100644 --- a/P5/Source/Specs/syll.xml +++ b/P5/Source/Specs/syll.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/symbol.xml b/P5/Source/Specs/symbol.xml index 2b0e10a514..43152cafe3 100644 --- a/P5/Source/Specs/symbol.xml +++ b/P5/Source/Specs/symbol.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/table.xml b/P5/Source/Specs/table.xml index 006341f9e3..9c14ffb87c 100644 --- a/P5/Source/Specs/table.xml +++ b/P5/Source/Specs/table.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/tag.xml b/P5/Source/Specs/tag.xml index 340052f631..2201b0c96f 100644 --- a/P5/Source/Specs/tag.xml +++ b/P5/Source/Specs/tag.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/tagUsage.xml b/P5/Source/Specs/tagUsage.xml index 8d30ff80e6..4997fe03ff 100644 --- a/P5/Source/Specs/tagUsage.xml +++ b/P5/Source/Specs/tagUsage.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/tagsDecl.xml b/P5/Source/Specs/tagsDecl.xml index 49c2afd87b..728167e24b 100644 --- a/P5/Source/Specs/tagsDecl.xml +++ b/P5/Source/Specs/tagsDecl.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/taxonomy.xml b/P5/Source/Specs/taxonomy.xml index d27bc30c31..089d2aaea4 100644 --- a/P5/Source/Specs/taxonomy.xml +++ b/P5/Source/Specs/taxonomy.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/tech.xml b/P5/Source/Specs/tech.xml index 01a8038611..da4991e0d0 100644 --- a/P5/Source/Specs/tech.xml +++ b/P5/Source/Specs/tech.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teiCorpus.xml b/P5/Source/Specs/teiCorpus.xml index 1977aac53f..20e651a103 100644 --- a/P5/Source/Specs/teiCorpus.xml +++ b/P5/Source/Specs/teiCorpus.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teiHeader.xml b/P5/Source/Specs/teiHeader.xml index 14b9998179..8c42224c5b 100644 --- a/P5/Source/Specs/teiHeader.xml +++ b/P5/Source/Specs/teiHeader.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.authority.xml b/P5/Source/Specs/teidata.authority.xml index 694dfb2c67..8a0d3456cc 100644 --- a/P5/Source/Specs/teidata.authority.xml +++ b/P5/Source/Specs/teidata.authority.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.certainty.xml b/P5/Source/Specs/teidata.certainty.xml index ad8777a528..6324feddb3 100644 --- a/P5/Source/Specs/teidata.certainty.xml +++ b/P5/Source/Specs/teidata.certainty.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.count.xml b/P5/Source/Specs/teidata.count.xml index 583ae1667d..2c9ac37563 100644 --- a/P5/Source/Specs/teidata.count.xml +++ b/P5/Source/Specs/teidata.count.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.duration.iso.xml b/P5/Source/Specs/teidata.duration.iso.xml index ff803c7ffa..84bd548c1a 100644 --- a/P5/Source/Specs/teidata.duration.iso.xml +++ b/P5/Source/Specs/teidata.duration.iso.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.duration.w3c.xml b/P5/Source/Specs/teidata.duration.w3c.xml index c712ae001e..ec001f8c1b 100644 --- a/P5/Source/Specs/teidata.duration.w3c.xml +++ b/P5/Source/Specs/teidata.duration.w3c.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.enumerated.xml b/P5/Source/Specs/teidata.enumerated.xml index 16c7fb66f3..9777ea1301 100644 --- a/P5/Source/Specs/teidata.enumerated.xml +++ b/P5/Source/Specs/teidata.enumerated.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.gender.xml b/P5/Source/Specs/teidata.gender.xml index fe83c77288..40ec63b81b 100644 --- a/P5/Source/Specs/teidata.gender.xml +++ b/P5/Source/Specs/teidata.gender.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.interval.xml b/P5/Source/Specs/teidata.interval.xml index ef3feb4eb6..8bb14ea458 100644 --- a/P5/Source/Specs/teidata.interval.xml +++ b/P5/Source/Specs/teidata.interval.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.key.xml b/P5/Source/Specs/teidata.key.xml index 1003467073..e82339f174 100644 --- a/P5/Source/Specs/teidata.key.xml +++ b/P5/Source/Specs/teidata.key.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.language.xml b/P5/Source/Specs/teidata.language.xml index ab68557d7a..e97a3fc5db 100644 --- a/P5/Source/Specs/teidata.language.xml +++ b/P5/Source/Specs/teidata.language.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.name.xml b/P5/Source/Specs/teidata.name.xml index 75c58adab1..38f7544005 100644 --- a/P5/Source/Specs/teidata.name.xml +++ b/P5/Source/Specs/teidata.name.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.namespace.xml b/P5/Source/Specs/teidata.namespace.xml index 6d0613bae5..14580b7d5c 100644 --- a/P5/Source/Specs/teidata.namespace.xml +++ b/P5/Source/Specs/teidata.namespace.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.namespaceOrName.xml b/P5/Source/Specs/teidata.namespaceOrName.xml index be04283789..5c597b5a5c 100644 --- a/P5/Source/Specs/teidata.namespaceOrName.xml +++ b/P5/Source/Specs/teidata.namespaceOrName.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.nullOrName.xml b/P5/Source/Specs/teidata.nullOrName.xml index 8b944dd974..d8165b539a 100644 --- a/P5/Source/Specs/teidata.nullOrName.xml +++ b/P5/Source/Specs/teidata.nullOrName.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.numeric.xml b/P5/Source/Specs/teidata.numeric.xml index 9015adcaa7..4649dd6f81 100644 --- a/P5/Source/Specs/teidata.numeric.xml +++ b/P5/Source/Specs/teidata.numeric.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.outputMeasurement.xml b/P5/Source/Specs/teidata.outputMeasurement.xml index 77679f1c10..a3bb6c9b45 100644 --- a/P5/Source/Specs/teidata.outputMeasurement.xml +++ b/P5/Source/Specs/teidata.outputMeasurement.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.pattern.xml b/P5/Source/Specs/teidata.pattern.xml index 2ed5381daf..d9c41dd206 100644 --- a/P5/Source/Specs/teidata.pattern.xml +++ b/P5/Source/Specs/teidata.pattern.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.point.xml b/P5/Source/Specs/teidata.point.xml index db8aec7bb0..34db58485b 100644 --- a/P5/Source/Specs/teidata.point.xml +++ b/P5/Source/Specs/teidata.point.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.pointer.xml b/P5/Source/Specs/teidata.pointer.xml index efb7aac0c7..9bb29db87f 100644 --- a/P5/Source/Specs/teidata.pointer.xml +++ b/P5/Source/Specs/teidata.pointer.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.prefix.xml b/P5/Source/Specs/teidata.prefix.xml index ff2f82d0ef..562c4ef6c3 100644 --- a/P5/Source/Specs/teidata.prefix.xml +++ b/P5/Source/Specs/teidata.prefix.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.probability.xml b/P5/Source/Specs/teidata.probability.xml index 55c99415a4..5267be894d 100644 --- a/P5/Source/Specs/teidata.probability.xml +++ b/P5/Source/Specs/teidata.probability.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.replacement.xml b/P5/Source/Specs/teidata.replacement.xml index d1f7ea7d08..a7b7e7ae38 100644 --- a/P5/Source/Specs/teidata.replacement.xml +++ b/P5/Source/Specs/teidata.replacement.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.sex.xml b/P5/Source/Specs/teidata.sex.xml index be3b96f47f..b57a7f5892 100644 --- a/P5/Source/Specs/teidata.sex.xml +++ b/P5/Source/Specs/teidata.sex.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.temporal.iso.xml b/P5/Source/Specs/teidata.temporal.iso.xml index 75964bf230..d395a42d73 100644 --- a/P5/Source/Specs/teidata.temporal.iso.xml +++ b/P5/Source/Specs/teidata.temporal.iso.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.temporal.w3c.xml b/P5/Source/Specs/teidata.temporal.w3c.xml index bcee15e3e6..dbd4117f63 100644 --- a/P5/Source/Specs/teidata.temporal.w3c.xml +++ b/P5/Source/Specs/teidata.temporal.w3c.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.temporal.working.xml b/P5/Source/Specs/teidata.temporal.working.xml index cf91487174..c154784dc2 100644 --- a/P5/Source/Specs/teidata.temporal.working.xml +++ b/P5/Source/Specs/teidata.temporal.working.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.text.xml b/P5/Source/Specs/teidata.text.xml index 6ba64e7103..49773b8e81 100644 --- a/P5/Source/Specs/teidata.text.xml +++ b/P5/Source/Specs/teidata.text.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.truthValue.xml b/P5/Source/Specs/teidata.truthValue.xml index f18af99ec4..55f8efcf02 100644 --- a/P5/Source/Specs/teidata.truthValue.xml +++ b/P5/Source/Specs/teidata.truthValue.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.unboundedCount.xml b/P5/Source/Specs/teidata.unboundedCount.xml index 13bc913069..cf07468081 100644 --- a/P5/Source/Specs/teidata.unboundedCount.xml +++ b/P5/Source/Specs/teidata.unboundedCount.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.version.xml b/P5/Source/Specs/teidata.version.xml index f5637c06ff..43519979cd 100644 --- a/P5/Source/Specs/teidata.version.xml +++ b/P5/Source/Specs/teidata.version.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.versionNumber.xml b/P5/Source/Specs/teidata.versionNumber.xml index 23227e843c..a4599773fd 100644 --- a/P5/Source/Specs/teidata.versionNumber.xml +++ b/P5/Source/Specs/teidata.versionNumber.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.word.xml b/P5/Source/Specs/teidata.word.xml index 9dd5f9390f..5c140b765d 100644 --- a/P5/Source/Specs/teidata.word.xml +++ b/P5/Source/Specs/teidata.word.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.xTruthValue.xml b/P5/Source/Specs/teidata.xTruthValue.xml index 70d229382d..7e5a6939a5 100644 --- a/P5/Source/Specs/teidata.xTruthValue.xml +++ b/P5/Source/Specs/teidata.xTruthValue.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.xmlName.xml b/P5/Source/Specs/teidata.xmlName.xml index dfb525e396..6f9df6ff7e 100644 --- a/P5/Source/Specs/teidata.xmlName.xml +++ b/P5/Source/Specs/teidata.xmlName.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/teidata.xpath.xml b/P5/Source/Specs/teidata.xpath.xml index 88fa12e371..8f83f1e816 100644 --- a/P5/Source/Specs/teidata.xpath.xml +++ b/P5/Source/Specs/teidata.xpath.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/term.xml b/P5/Source/Specs/term.xml index 8b205ffcbb..951ef269c0 100644 --- a/P5/Source/Specs/term.xml +++ b/P5/Source/Specs/term.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/terrain.xml b/P5/Source/Specs/terrain.xml index 7a2c69461c..134bdc0a29 100644 --- a/P5/Source/Specs/terrain.xml +++ b/P5/Source/Specs/terrain.xml @@ -1,4 +1,6 @@ - + + + terrain terrain contains information about the physical terrain of a place. diff --git a/P5/Source/Specs/text.xml b/P5/Source/Specs/text.xml index 45927be403..af7211b633 100644 --- a/P5/Source/Specs/text.xml +++ b/P5/Source/Specs/text.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/textClass.xml b/P5/Source/Specs/textClass.xml index 30b7879dbd..dd488c822e 100644 --- a/P5/Source/Specs/textClass.xml +++ b/P5/Source/Specs/textClass.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/textDesc.xml b/P5/Source/Specs/textDesc.xml index c9ebd1c9e3..0f2fc18b21 100644 --- a/P5/Source/Specs/textDesc.xml +++ b/P5/Source/Specs/textDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/textLang.xml b/P5/Source/Specs/textLang.xml index 2a5db7d142..479142edea 100644 --- a/P5/Source/Specs/textLang.xml +++ b/P5/Source/Specs/textLang.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/textNode.xml b/P5/Source/Specs/textNode.xml index b1880ce002..26a6f80f09 100644 --- a/P5/Source/Specs/textNode.xml +++ b/P5/Source/Specs/textNode.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/then.xml b/P5/Source/Specs/then.xml index ca933db3dd..d9eec07272 100644 --- a/P5/Source/Specs/then.xml +++ b/P5/Source/Specs/then.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/time.xml b/P5/Source/Specs/time.xml index 57f9fc9630..ad92fe1a22 100644 --- a/P5/Source/Specs/time.xml +++ b/P5/Source/Specs/time.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/timeline.xml b/P5/Source/Specs/timeline.xml index b707d5350e..f4e0f564c4 100644 --- a/P5/Source/Specs/timeline.xml +++ b/P5/Source/Specs/timeline.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/title.xml b/P5/Source/Specs/title.xml index 671ce855e5..b20d445223 100644 --- a/P5/Source/Specs/title.xml +++ b/P5/Source/Specs/title.xml @@ -1,4 +1,6 @@ - + + + title titre Titel diff --git a/P5/Source/Specs/titlePage.xml b/P5/Source/Specs/titlePage.xml index 88e8be433d..c60811e765 100644 --- a/P5/Source/Specs/titlePage.xml +++ b/P5/Source/Specs/titlePage.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/titlePart.xml b/P5/Source/Specs/titlePart.xml index 0e97fa4922..1030d9c704 100644 --- a/P5/Source/Specs/titlePart.xml +++ b/P5/Source/Specs/titlePart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/titleStmt.xml b/P5/Source/Specs/titleStmt.xml index 783e8749e9..0455cf0e2b 100644 --- a/P5/Source/Specs/titleStmt.xml +++ b/P5/Source/Specs/titleStmt.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/tns.xml b/P5/Source/Specs/tns.xml index 8d292fd826..c616e4ad2f 100644 --- a/P5/Source/Specs/tns.xml +++ b/P5/Source/Specs/tns.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/trailer.xml b/P5/Source/Specs/trailer.xml index 7253cb814f..051734a859 100644 --- a/P5/Source/Specs/trailer.xml +++ b/P5/Source/Specs/trailer.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/trait.xml b/P5/Source/Specs/trait.xml index dc29afb298..037559c53b 100644 --- a/P5/Source/Specs/trait.xml +++ b/P5/Source/Specs/trait.xml @@ -1,4 +1,6 @@ - + + + trait trait distinctif contains a description of some status or quality attributed to a person, place, or organization typically, but not necessarily, diff --git a/P5/Source/Specs/transcriptionDesc.xml b/P5/Source/Specs/transcriptionDesc.xml index 618c60aff7..ea2b4a1bd2 100644 --- a/P5/Source/Specs/transcriptionDesc.xml +++ b/P5/Source/Specs/transcriptionDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/transpose.xml b/P5/Source/Specs/transpose.xml index 1329f0e8b2..2a00899d61 100644 --- a/P5/Source/Specs/transpose.xml +++ b/P5/Source/Specs/transpose.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/tree.xml b/P5/Source/Specs/tree.xml index a73125c013..fb60d50287 100644 --- a/P5/Source/Specs/tree.xml +++ b/P5/Source/Specs/tree.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/triangle.xml b/P5/Source/Specs/triangle.xml index 4b746544c5..0eeceaa997 100644 --- a/P5/Source/Specs/triangle.xml +++ b/P5/Source/Specs/triangle.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/typeDesc.xml b/P5/Source/Specs/typeDesc.xml index 49d5692505..d289209798 100644 --- a/P5/Source/Specs/typeDesc.xml +++ b/P5/Source/Specs/typeDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/typeNote.xml b/P5/Source/Specs/typeNote.xml index e5aea87904..311207cb6b 100644 --- a/P5/Source/Specs/typeNote.xml +++ b/P5/Source/Specs/typeNote.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/u.xml b/P5/Source/Specs/u.xml index 886455ea40..7996e27497 100644 --- a/P5/Source/Specs/u.xml +++ b/P5/Source/Specs/u.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/unclear.xml b/P5/Source/Specs/unclear.xml index 55d644b6b8..4fcf4d47bb 100644 --- a/P5/Source/Specs/unclear.xml +++ b/P5/Source/Specs/unclear.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/undo.xml b/P5/Source/Specs/undo.xml index 4b91a953e1..74fc3329f8 100644 --- a/P5/Source/Specs/undo.xml +++ b/P5/Source/Specs/undo.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/unicodeProp.xml b/P5/Source/Specs/unicodeProp.xml index f759a5680e..accd341a78 100644 --- a/P5/Source/Specs/unicodeProp.xml +++ b/P5/Source/Specs/unicodeProp.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/unitDecl.xml b/P5/Source/Specs/unitDecl.xml index 605de2d176..bc0265fc85 100644 --- a/P5/Source/Specs/unitDecl.xml +++ b/P5/Source/Specs/unitDecl.xml @@ -1,4 +1,6 @@ - + + + unit declarations provides information about units of measurement that are not members of the International System of Units. diff --git a/P5/Source/Specs/unitDef.xml b/P5/Source/Specs/unitDef.xml index 6710cd2cdf..2700be715c 100644 --- a/P5/Source/Specs/unitDef.xml +++ b/P5/Source/Specs/unitDef.xml @@ -1,4 +1,6 @@ - + + + unit definition contains descriptive information related to a specific unit of measurement. diff --git a/P5/Source/Specs/usg.xml b/P5/Source/Specs/usg.xml index e36a7412b3..6425b822f2 100644 --- a/P5/Source/Specs/usg.xml +++ b/P5/Source/Specs/usg.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/vAlt.xml b/P5/Source/Specs/vAlt.xml index c16caa0f54..76b8696dc2 100644 --- a/P5/Source/Specs/vAlt.xml +++ b/P5/Source/Specs/vAlt.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/vColl.xml b/P5/Source/Specs/vColl.xml index 14ad51e4fd..15aa41de5b 100644 --- a/P5/Source/Specs/vColl.xml +++ b/P5/Source/Specs/vColl.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/vDefault.xml b/P5/Source/Specs/vDefault.xml index c09ac7b8ba..9c23ea6d5a 100644 --- a/P5/Source/Specs/vDefault.xml +++ b/P5/Source/Specs/vDefault.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/vLabel.xml b/P5/Source/Specs/vLabel.xml index 9a3afe2e03..e36049018c 100644 --- a/P5/Source/Specs/vLabel.xml +++ b/P5/Source/Specs/vLabel.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/vMerge.xml b/P5/Source/Specs/vMerge.xml index fe135a153e..e262c194d8 100644 --- a/P5/Source/Specs/vMerge.xml +++ b/P5/Source/Specs/vMerge.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/vNot.xml b/P5/Source/Specs/vNot.xml index 5eb473360a..02e5ac4b1e 100644 --- a/P5/Source/Specs/vNot.xml +++ b/P5/Source/Specs/vNot.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/vRange.xml b/P5/Source/Specs/vRange.xml index 1e01198ad0..e2c29bad4a 100644 --- a/P5/Source/Specs/vRange.xml +++ b/P5/Source/Specs/vRange.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/val.xml b/P5/Source/Specs/val.xml index adc9675a45..983e06b0a8 100644 --- a/P5/Source/Specs/val.xml +++ b/P5/Source/Specs/val.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/valDesc.xml b/P5/Source/Specs/valDesc.xml index 65d03f1a79..a490d925fc 100644 --- a/P5/Source/Specs/valDesc.xml +++ b/P5/Source/Specs/valDesc.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/valItem.xml b/P5/Source/Specs/valItem.xml index fab5338e0e..a2f0c381cd 100644 --- a/P5/Source/Specs/valItem.xml +++ b/P5/Source/Specs/valItem.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/valList.xml b/P5/Source/Specs/valList.xml index 5272421a27..bc3ab4a215 100644 --- a/P5/Source/Specs/valList.xml +++ b/P5/Source/Specs/valList.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/variantEncoding.xml b/P5/Source/Specs/variantEncoding.xml index 3648eedb2a..51d2616312 100644 --- a/P5/Source/Specs/variantEncoding.xml +++ b/P5/Source/Specs/variantEncoding.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/view.xml b/P5/Source/Specs/view.xml index 51ddf993cf..66a71671dd 100644 --- a/P5/Source/Specs/view.xml +++ b/P5/Source/Specs/view.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/vocal.xml b/P5/Source/Specs/vocal.xml index fc4d99cba3..6c2f8d053f 100644 --- a/P5/Source/Specs/vocal.xml +++ b/P5/Source/Specs/vocal.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/w.xml b/P5/Source/Specs/w.xml index 20e59131ae..b5ff2b7b1d 100644 --- a/P5/Source/Specs/w.xml +++ b/P5/Source/Specs/w.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/watermark.xml b/P5/Source/Specs/watermark.xml index 3c97949666..f2b8f6f3ce 100644 --- a/P5/Source/Specs/watermark.xml +++ b/P5/Source/Specs/watermark.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/when.xml b/P5/Source/Specs/when.xml index 859bc110cc..f109777b30 100644 --- a/P5/Source/Specs/when.xml +++ b/P5/Source/Specs/when.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/width.xml b/P5/Source/Specs/width.xml index 3613d9952e..610d9418c8 100644 --- a/P5/Source/Specs/width.xml +++ b/P5/Source/Specs/width.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/wit.xml b/P5/Source/Specs/wit.xml index 084fa3989d..9779c7992b 100644 --- a/P5/Source/Specs/wit.xml +++ b/P5/Source/Specs/wit.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/witDetail.xml b/P5/Source/Specs/witDetail.xml index c7687ab897..08983d6465 100644 --- a/P5/Source/Specs/witDetail.xml +++ b/P5/Source/Specs/witDetail.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/witEnd.xml b/P5/Source/Specs/witEnd.xml index 011b9967bc..19fce91bd6 100644 --- a/P5/Source/Specs/witEnd.xml +++ b/P5/Source/Specs/witEnd.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/witStart.xml b/P5/Source/Specs/witStart.xml index 37ef1986a6..8c42075373 100644 --- a/P5/Source/Specs/witStart.xml +++ b/P5/Source/Specs/witStart.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/witness.xml b/P5/Source/Specs/witness.xml index 9d77bcea17..3e17e4ef15 100644 --- a/P5/Source/Specs/witness.xml +++ b/P5/Source/Specs/witness.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/writing.xml b/P5/Source/Specs/writing.xml index 6f526b0324..7bad204353 100644 --- a/P5/Source/Specs/writing.xml +++ b/P5/Source/Specs/writing.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/xenoData.xml b/P5/Source/Specs/xenoData.xml index dbb1df763b..3cb07cc48a 100644 --- a/P5/Source/Specs/xenoData.xml +++ b/P5/Source/Specs/xenoData.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/xr.xml b/P5/Source/Specs/xr.xml index 27fbc63be8..90be25df53 100644 --- a/P5/Source/Specs/xr.xml +++ b/P5/Source/Specs/xr.xml @@ -1,3 +1,4 @@ + diff --git a/P5/Source/Specs/zone.xml b/P5/Source/Specs/zone.xml index 7adee8a624..cfa9bff22c 100644 --- a/P5/Source/Specs/zone.xml +++ b/P5/Source/Specs/zone.xml @@ -1,3 +1,4 @@ + From e231d6c5c5a6f4bf7e008476e6891f35b8286d1f Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Sat, 24 Feb 2024 17:01:04 -0500 Subject: [PATCH 034/127] No idea why French BIB was messed up. Fixed. --- P5/Source/Guidelines/fr/BIB-Bibliography.xml | 6374 +----------------- 1 file changed, 1 insertion(+), 6373 deletions(-) mode change 100644 => 120000 P5/Source/Guidelines/fr/BIB-Bibliography.xml diff --git a/P5/Source/Guidelines/fr/BIB-Bibliography.xml b/P5/Source/Guidelines/fr/BIB-Bibliography.xml deleted file mode 100644 index d85642f5d5..0000000000 --- a/P5/Source/Guidelines/fr/BIB-Bibliography.xml +++ /dev/null @@ -1,6373 +0,0 @@ - - - - - -
- Bibliography -
- Works Cited in Examples in these Guidelines - - - 阿城，《棋王》。 - Académie française, - Rectifications de l'orthographe - J.O. du 06-12-1990, En ligne, - consulté le 05-03-2010. - - Adams, Douglas. The Hitchhiker's Guide to the - Galaxy, New York: Pocket Books, 1979, - chapter 31. - Agence bibliographique de l'enseignement - supérieur, ABES:Site internet - par l'ABES,consulté le 05-03-2010. - 阿拉伯短劍，國史館：嚴家淦總統文物。 - Alighieri, Dante. Doglia mi - reca ne lo core ardire, Rime, XLIX. - Allinson, E.P. and B. Penrose. - Philadelphia 1681-1887 (1887), p. 138. - American National Standard for Bibliographic - References, ANSI Z39.29-1977, New York: American - National Standards Institute (1977). - - - - Andersson, Theodore M.. A Preface to the Nibelungenlied, - Stanford University Press (1987). - - Andrews, Mr.. Song, Chambers's - Edinburgh Journal Series 1 - 9:463 (12 - December 1840), 376. - - Anouilh, Jean, - Antigone, 1842. - - [As in Visions of] Single leaf of Notes for a poem about night "visions," - possibly related to the untitled 1855 poem that Whitman eventually titled "The Sleepers." - Fragments of an unidentified newspaper clipping about the Puget Sound area have been pasted - to the leaf. The Trent Collection of Walt Whitman Manuscripts, Duke University Rare Book, - Manuscript, and Special Collections Library. - - - Atkins et al. - Collins Robert French-English English-French Dictionary. - London: Collins (1978). - - Atkinson, J. Maxwell and John Heritage. Structures of social action: Studies in conversation analysis, - Cambridge and Paris: Cambridge - University Press, Editions de la Maison des Sciences de - l'Homme (1984), ix-xvi. - Austen, Jane. Pride and - Prejudice. (1813), chapter - 1. - - - - 白先勇，〈金大班的最後一夜〉，《台北人》。 - 白先勇，《孽子》。 - 白居易，《憶江南》。 - - Amheida I: Ostraka from Trimithis Volume 1: Texts from the 2004–2007 Seasons, - Bagnall, R. S. and G. R. Ruffini, with contributions by R. Cribiore and G. Vittmann - (2012). - - - Baker, James K.. Night in Tarras. In Hilltop: A Literary Paper, vol 1 no 2. Wellington: Victoria University College - Literary Society. (1949). - Balzac, Honoré de, - Les Chouans, 1845. - Balzac, Honoré de, - Le Père Goriot, 1843. - Balzac, Honoré de, Petites misères de la - vie conjugale, 1850. - Barbauld, Lucy Aikin. The Works of Anna - Laetitia Barbauld (1826). - - Barker, Jane. The Lining to the Patch-Work Screen - (1726). - - Base de datos paleográfica da lírica galego-portuguesa (PalMed). Versión 1.2. - Santiago de Compostela: Centro Ramón Piñeiro para a - Investigación en Humanidades. . - f. B126r, column a, l. 21-32. - - Bataille, Michel , - L'Arbre de Noël, 1967. - - Les Chats, in : Baudelaire, Charles, Les Fleurs du mal, 1861. - - La Vie antérieure, in : Baudelaire, Charles, - Les Fleurs du mal, 1861. - 電影《霸王別姬》，1993年。 - Beck, Béatrice, Léon - Morin, prêtre, 1952. - Beckett, Samuel. Waiting for - Godot, London: Faber and Faber - (1956). - Beckett, Samuel. Murphy - (1963), chap 2. - Becque, Henry, La - Parisienne. Edition - électronique par l'ATILF et le CNRTL, d'après - l'édition de Fasquelle (Paris, 1922). - - Bowers, Jack - Mixtepec-Mixtec Project Personography - - - - - Beerbohm, Max. Autograph manuscript of The Golden Drugget, - Pierpont Morgan MA 3391. in 123. - Behn, Aphra. The Rover, - (1697). - - Beeton, Isabella. The book of Household Management, - London: S.O. Beeton - (1861). - Belloc, Denis , - Képas, 1989. - - Belloc, Denis , Néons, 1987. - Bentham, Jeremy. The Book of - Fallacies. (1824). - - Beowulf and The fight at Finnsburg; edited, with introduction, bibliography, - notes, glossary, and appendices, by Fr. Klaeber. Boston, New York - [etc.] - D.C. Heath & Co. (1922). - - Bibliographie dans le cadre de la semaine italienne du 11 au 18 mars 2006, , - document électronique. - Bibliothèque nationale de - France, Projet de description des reliures remarquables de la Réserve des - livres rares selon le modèle de la TEI manuscrits. - Billetdoux, Marie, Un - peu de désir sinon je meurs, 2006. - - Blake, William. London, in Songs - of Experience (1791). - - Blake, William. The Sick Rose, in Songs of Experience (1794). - - Blake, William. The Tyger, in Songs of Experience (1794). - Bloomfield, Leonard. Literate and - Illiterate Speech, American Speech, 2, (1927), pp. - 432-441. - Borges, Jorge Luis, tr. R. - Simms. The Analytical Language of John Wilkins. In - Emir Rodriguez Monegal and Alistair Reid, eds. Borges: A reader, Dutton Adult - (1981), p.141. - Borges, Jorge Luis. Avatars of - the Tortoise In James E. Irby tr. Labyrinths: Selected Stories and Other Writings, New York: - New Directions, (1962), pp.202-203. - Bouillier, Grégoire, - Rapport sur moi, 2002. - Bresson, Robert, Mouchette : script, l'Avant-scène cinéma, - n° 80, avril 1968. - Extract from British National Corpus () Text KB7, sentence 13730. - - Brontë, Charlotte. Jane Eyre: An Autobiography, - Third edition; reprintLondon - Service & Paton, 1897; - Project Gutenberg, 1 December 2020. - chapter XII. - - - - Browning, Robert. Letter to George Moulton-Barrett, Pierpont - Morgan MA 310, ( 23). - Buirette de Belloy, Pierre Laurent, - Gabrielle de Vergy, 1777. - - Bunyan, John. The Pilgrim's Progress from this world to that which - is to come..., London (1678). - Burgess, Anthony. A Clockwork - Orange. (1962), opening. - Burnard, Lou. Principles of - Database Design in S. Rahtz. ed. Information - Technology in the Humanities: tools, techniques and applications, Ellis - Horwood Ltd, Ellis Horwood Series in Computers and Their - Applications, (1987), p. 54. - Burnard, Lou, - Sperberg-McQueen, C. M., - <ref target="http://www.gutenberg.eu.org/publications/autres/TEILITE/">La TEI simplifiée, - une introduction au codage des textes électroniques en vue de leur échange -- version de - travail </ref> - , 1996. - - Burton, Robert. Anatomy of Melancholy - (1621), 16th ed. reprinted 1846, p. 743. - Butler, Samuel. The Way of All - Flesh (1903), chapter 37. - Byron, George Gordon. Don Juan - (1819), I.xxii. - Byron, George Gordon. Vision of - Judgment In E.H. Coleridge ed. The Poetical - Works of Lord Byron, viii, 1922. - - - - C 60/16 Fine Roll 6 HENRY III (28 October 1221-27 - October 1222), membrane 5, entry 154. - CBETA - Cædmon's Hymn in Bede's Historia Ecclesiastica (MS Kk. - 5. 16, Cambridge, University Library). - - Cabaret. A musical play, with book by Joe Masteroff, lyrics by Fred Ebb, and - music by John Kaner. Based on the play by John van Druten and stories by Christopher - Isherwood. 1966 - Edward Barkley, describing how Essex drove the Irish from the - plains into the woods to freeze or famish in winter; quoted by Canny, Nicholas - P. - The Ideology of English Colonization: From Ireland to America. In - Stanley N. Katz and John M. Murrin eds. Colonial America: Essays in Politics and Social Development, 3d - ed - New York: Knopf, (1983), p.53. - - - Carroll, Lewis. Through the Looking Glass, and what Alice - found there. (1871). - Catéchisme de l'Eglise - catholique, 1968. - - Cavendish, Margaret. Nature's Pictures. - London, 1656. Women Writers Online. Women - Writers Project, Northeastern University. 29 Mar. - 2015. - Centre national de la recherche scientifique - (France). UMR 7118 ATILF, <ref target="http://atilf.atilf.fr/tlf.htm">Le - Trésor de la Langue Française Informatisé (TLFI)</ref>, - 2004. - Example recoded from Chafe, W. - Adequacy, user-friendliness, and practicality in transcribing In - Leech, G., G. Myers, J. Thomas eds. - Spoken English on Computer: Transcription, Markup and - Applications. Harlow: Longman, - 1995. - - Chandler, Lloyd. - Conversation with Death (also known as Oh, - Death). In Journal of Folklore Research, 41.2/3, (2004), pp. - 125-126. - Chapman, Graham, Cleese, John, - Gilliam, Terry, Idle, Eric, Jones, - Terry. The complete Monty Pythons Flying Circus. - Chapman, Graham, Cleese, John, - Gilliam, Terry, Idle, Eric, Jones, - Terry. Monty Python's Life of Brian (1979). - - - Chaucer, Geoffrey. Canterbury Tales, f52r, in Holkham MS. - - Chaucer, Geoffrey. The Tale of Sir Topas, The Canterbury Tales, In F. N. Robinson ed. The Works of Geoffrey Chaucer, 2nd edition - Boston: Houghton Mifflin Co., - 1957. - 陳政彥，〈戰後臺灣現代詩論戰史研究〉，2007。 - - Cholières, Nicolas de, La Forest Nuptiale - (1600). - - Chomsky, Noam and Morris Halle. The Sound Pattern - of English. New York: Harper & Row (1968), p. 415. - Claude Simon - Le jardin des plantes, 1997, p 284 - - Cleaver, Eldridge. Soul on Ice. New - York (1968). - - Cloud of Unknowing In Hodgson, Phyllis ed. The Cloud of Unknowing and The Book of Privy Counselling, - London: Oxford University Press, Early - English Text Society, 218, (1944). - Clover, Carol J.The Medieval - Saga, Ithaca: Cornell University Press - (1982). - - Cocteau, Jean. La Machine Infernale. - Coleridge, Samuel Taylor. The - Rime of the Ancient Mariner. In Wordsworth, William and - Samuel Taylor Coleridge. Lyrical Ballads - (1798). - Coleridge, Samuel Taylor. Frost at - Midnight In E.H. Coleridge ed. Poetical - Works, Oxford: Oxford University - Press, (1967), p.240. - Colette, Colette à - l'école, 1900. - - Collins English Dictionary, 12th edition - Glasgow: Collins - (2014). - - Collins Pocket Dictionary of the English language. - London: Collins. - - Collins, Wilkie. The Moonstone, - Penguin, 6th narrative. - - Comenius, John Amos. Orbis Pictus: a facsimile of the - first English edition of 1659 (ed. John - E. - Sadler - ) Oxford University Press (1968). - Cope, Thomas Pym. Philadelphia - merchant: the diary of Thomas P. Cope, 1800-1851, Eliza Cope - Harrison ed. - Corneille, Pierre, - La Place Royale ou L'Amoureux extravagant, 1637. - Corneille, Pierre, - Théodore, vierge et martyre : tragédie chrétienne, - 1646. - - Cowley, Hannah. The Runaway (1813). - - Crashaw, Richard, ed. J.R. Tutin. The - Poems of Richard Crashaw. Muses Library Edition: - (1900). - - Creeley, Robert - A counterpoint in For Love: Poems 1950-1960 - (1962). - 崔西．雪佛蘭。《戴珍珠耳環的少女》。台北：皇冠，2003。 - - - - Dallas, George Mifflin. Unpublished - letter cited in Russell F. Weigley, Nicholas B. - Wainwright, Edwin Wolf eds. Philadelphia: A 300 - Year History, New York and London: - W. W. Norton & Company, 1982, p. 349. - Danhauser, Adolphe-Leopold, - Théorie de la musique, 1872. - - Darwin, Charles. Narrative of the Surveying Voyages of His Majesty's - ships Adventure and Beagle... volume 3 : Journal and Remarks (The Voyage of the - Beagle), chap 3. 1839. - Daudet, Alphonse, Les - contes du lundi, 1873. - - Davenant, William. The vvitts. A comedie, presented at the - private house in Blacke Fryers, by his Majesties servants. The author VVilliam D'avenant, - servant to Her Majestie. - London, 1636. [STC S109311] - - De Nutrimento et Nutribili, Tractatus 1, fol 217r col b of Merton College - Oxford MS O.2.1; in pl. 16. - - Dean of Sarum Churchwardens' presentments, 1731, Hurst; Wiltshire Record - Office; transcribed by Donald A. Spaeth. - Defoe, Daniel. The Fortunes and - Misfortunes of the Famous Moll Flanders (1722). - Defoe, Daniel. Robinson - Crusoe (1719). - - Defoe, Daniel. Journal of the Plague Year. - London (1722). - - Dekker, Thomas and Thomas Middleton. The Honest - Whore, Part One (1604). - Deloney, Thomas. Thomas of Reading or the - Sixe Worthie Yeomen of the West (1612). - Dennery, Annie. Du mélos à la note : Les notations musicales au Moyen Age, Médiévales, n° 3 - 1983. - Dickens, Charles. A Christmas - Carol in Prose, Being a Ghost Story of Christmas, Chapman and - Hall, (1843), p. 5, p. - 12. - Dickens, Charles. Little - Dorrit, (1857). - Dickinson, Emily. 1755 In - Arthur Eastman et al. eds. The Norton Anthology of - Poetry, New York: W.W. Norton, - 1970, p.859. - Diderot, Denis, - Lettres à Sophie Volland, 26 sept. 1762. - 〈第三屆第一次大會第一次會議記錄〉，臺灣省諮議會。 - Disraeli, Benjamin. Coningsby (1844), preface. - Doyle, Arthur Conan. The - Red-headed league. In The Adventures of Sherlock Holmes - (1892). - - Doyle, Arthur Conan. The Original Illustrated Sherlock - Holmes, Castle Books, 1989. - Drawing of a leaden plaque bearing an inquiry by Hermon from the - oracular precinct at Dodona. Catalogue no 725; LSAG 230.13. Image from - Dubois, Jacques, Nyssen, - Hubert (dir. de collection), Babel, Actes - sud,1989-.... - Dubois, Jean, - Dictionnaire de linguistique, 1974. - - Dudo of St Quentin. De moribus et actis primorum Normannie - ducum, fol 4v of British Library MS Harley 3742; in pl - 6(i). - Dufournaud, Nicole, - Numérisation des Titres de famille, édition électronique, 2002. - Duhamel, Georges, - Chronique des Pasquier, 1933-1945. - - Dutt, Toru. Lakshman In Ancient - Ballads and Legends of Hindustan, Kegan Paul, Trench & - Co., (1882) - Dylan, Bob. All Along the - Watchtower In John Wesley Harding - (1967). - Dylan, Bob. Positively 4th - Street In Highway 61 Revisited - (1965). - - - - - Eddic poems, in Reykjavík, Landsbókasafn Íslands, Lbs 1562 4to. - Editorial, .EXE - magazine, 6.11 (1992), - p. 2. - Eliot, George. Middlemarch (1871), I.1. - - Eliot, George. Middlemarch (1871), - I.XXI. - - Eliot, George. Daniel Deronda (1876), - III.1. - Eliot, Thomas Stearns. The - waste land: a facsimile and transcript of the original drafts including the annotations of - Ezra Pound, Eliot, Valerie ed. Faber and Faber - Ltd. (1971), p. 37. - - Scalable Vector Graphics (SVG) 1.1 (Second Edition). Editors - Erik Dahlström, Jon Ferraiolo, 藤沢 淳, Anthony Grasso, Dean - Jackson, Chris Lilley, Cameron McCormack - Doug Schepers, Jonathan Watt and Patrick - Dengler. World Wide Web Consortium (W3C) (22 June - 2010). Available from . - Ernaux, Annie, Se - perdre, 1988. - Ernaux, Annie, L'usage - de la photo, 2005. - - - <ref target="http://www.etudes-litteraires.com/figures-de-style/deictique.php">Études - littéraires</ref> - , consulté le 07-05-2010. - - - - Fallet , René, Le - Triporteur, 1951. - Field, Syd - Screenplay: the Foundations of Screenwriting (1998). - Fielding, Henry. The History of - the Adventures of Joseph Andrews and his Friend, Mr. Abraham Abrams - (1742). - - Fielding, Henry. Tragedy of Tragedies, - (1737). - - Fish, Stanley. Is there a text in this class? The authority of - interpretive communities. Harvard University Press - (1980). - Fisher, M. F. K. I Was Really Very - Hungry In As They Were, Knopf - (1982), p. 43. - - - FitzGerald, Edward. The Rubáiyát of Omar Khayyám, translated into - English Verse (1859), stanza 25. - Flaubert, Gustave, - Salammbô, 1862. - Flaubert, Gustave, - La Tentation de saint Antoine, 1874. - Foley James D., Andries van Dam, - Steven K. Feiner and John F. Hughes. Computer Graphics: Principles and Practice, 2nd edition - Reading: Addison-Wesley, p.259. - Forster, E.M., Howards - End. Edward Arnold. (1910). - - - <ref target="http://sites.radiofrance.fr/franceinter/em/labassijysuis">France inter, - Là-bas si j'y suis</ref> - , consulté le 07-05-2010. - - - <ref target="http://sites.radiofrance.fr/franceinter/em/letelephonesonne/contact.php" - >France inter, Le téléphone sonne</ref> - , consulté le 07-05-2010. - - - <ref target="http://franglais.ini.hu/">Franglais et franricain</ref> - , consulté le 07-05-2010. - Fry, Christopher, The firstborn - (1948). - 福春嫁女 - - Fussell, Paul. The Norton Book of Travel. W. W. - Norton (1987). - - - - Galilei, Galileo, Sidereus - Nuncius, Venetiis: Apud Thomam - Baglionum, 1610, quoted by Tufte, Edward R., - Envisioning Information, Cheshire: - Graphics Press (1990), p. - 97. - Galland, Antoine, Les - Mille et une nuits, 1704. - Galsworthy, John, Strife. In - Plays, vol 1. (1909). - Gaskell, Elizabeth Cleghorn. The Grey Woman, MS. - Gavioli, Laura and Gillian - Mansfield. The PIXI corpora: bookshop encounters in English and - Italian, Bologna: Cooperativa Libraria - Universitaria Editrice (1990), p.74. - Gay, John. The Beggar's Opera - (1728). - Gazdar, Gerald and Mellish, - Christopher. Natural language processing in Prolog. - Addison-Wesley (1989), p.5. - - Gazdar, Gerald, Ewan Klein, Geoffrey Pullum, and Ivan Sag: - Generalized Phrase Structure Grammar, Harvard - University Press (1985). - - Gershwin, Ira - By Strauss (from An American in Paris, 1953). - Gianfraco Contini, Poeti del - Duecento, Milano-Napoli:Ricciardi I, (1960). pp 155-64. - Gibbon, Edward, The History of the - Decline and Fall of the Roman Empire, (1789), chapter 58. - Gide, André, Le - Journal des Faux-Monnayeurs, 1927. - Gide, André, Journal : - 1889-1939, 1939. - - Gilbert, William Schwenck and Sullivan, Arthur. HMS Pinafore (1878), I. - Gilbert, William Schwenck and Sullivan, - Arthur. The Mikado (1885). - Ginsberg, Allen. My alba, - Reality Sandwiches, San Francisco: - City Lights, (1963). - Giono, Jean, - Regain, 1930. - Giraudoux, Jean, La - guerre de Troie n'aura pas lieu, 1935. - - Godefroy, Frédéric, Dictionnaire de l'ancienne langue française et - de tous ses dialectes du IXe au XVe siècle, 1881. - Goethe, Johann Wolfgang von, tr. Philip Wayne. Faust, Part - 1, London: Penguin. (1949). - - Goethe, Johann Wolfgang von. Auf dem See - (1775). - - [Goldsmith, Oliver], The History of Little GOODY TWO-SHOES; - Otherwise called, Mrs. MARGERY TWO-SHOES... (Printed for J. Newbery, - 1766). - - Grallert, Till, Tools for the Computational Normalisation and - Analysis of Food Prices and Food Riots in the Eastern Mediterranean (Bilād al-Shām) in the - 19th and 20th Centuries. Zenodo, 2021. . - - Graves, Robert. Rough draft of letter to Desmond Flower. - 17 Dec 1938. (from Diary of Robert Graves 1935-39 and - ancillary materials, compiled by Beryl Graves, C.G. Petter, L.R. Roberts, - University of Victoria Libraries). - - Greene, Robert. Groatsworth of Wit Bought with a Million - of Repentance (1592). - - Gregory of Tours. Ecclesiastical History of the - Franks (translated by Lewis Thorpe). - Greimas, Algirdas Julien - et Courtés, Joseph, Sémiotique : dictionnaire raisonné de la théorie - du langage, 1979. - Grune, Dick and Ceriel J. H. - Jacobs. Parsing Techniques: A Practical Guide, - New York and London: Ellis - Horwood, 1990, p. 24. - - Guerard, Françoise. Le Dictionnaire de Notre Temps, ed. - Paris: Hachette, 1990 - - - - - Hall, Radclyffe. The well of - loneliness. (1928). - Halliday, M.A.K. and R. - Hassan. Language, Context and Text: Aspects of Language in a - Social-Semiotic Perspective, Oxford: Oxford - University Press, 1990, p. - 104. - Hanks, Patrick. Definitions and - Explanations. In J. M. Sinclair ed. Looking Up. - Collins, 1987, p. 121 - . - Hannam's last farewell to the world:: being a full and true - relation of the notorious life and shamfull death of Mr. Richard Hannam... - (1656). - - Hansberry, Lorraine. A raisin in the sun. - (1959). - Harvey, Gabriel. Four letters and certain - sonnets specially touching Robert Greene... (1592). - Harvey, William. Exercitatio Anatomica De Motu Cordis Et Sanguinis In Animalibus, 1949 (Third edition, second printing), p. 74. - Hobbes, Thomas. Leviathan - (1681). - 《紅樓夢》第六回：賈寶玉初試云雨情 劉姥姥一進榮國府 - 〈紅頭嶼踏查報告〉，國立台灣大學圖書館：田代文庫。 - Hoola Van Nooten, - BertheFleurs, fruits et feuillages choisis de l'île de Java peints d'après - nature, troisième édition par C. Muquardt, Bruxelles, - 1880. - - Hornby, A.S. et al. Oxford Advanced Learner's Dictionary of Current - English. Oxford University Press (1974). - 黃晨淳編著，《希臘羅馬神話故事》，p76。 - Hugo, Victor, - Notre-Dame de Paris, 1845. - - Souvenir de la nuit du 4, in : Hugo, Victor, - Les Contemplations, 1853. - Hugo, Victor, Les - Misérables, 1862. - - A la fenêtre pendant la nuit, in : Hugo, Victor , - Les Contemplations, 1856. - Huizinga, Johan, - L'Automne du Moyen-Âge, 1919. - - - - ISO 690:1987: Information and documentation – - Bibliographic references – Content, form and structure - clause 4.1, p.2. - ISO 24611:2012 Language resource management — Morpho-syntactic annotation framework (MAF). - International Organization for Standardization. 2012. - - Ibsen, Henrik, tr. William and Charles Archer. - Peer Gynt (1875). - - Ibsen, Henrik - Den episke Brand KBK Collin 2869, 4º I, fol. 11v. - - Ibsen, Henrik - Digte NBO Ms.4º 1110a, p. 36. - - Ibsen, Henrik - Brand, The Royal Library, Denmark. KBK Collin 262, 4°, I.1.1, fol. - [4]v - Ibsen, Henrik, tr. R. - Farquharson Sharp and Eleanor Marx-Aveling. - A Doll's House In A Doll's House; and Two Other - Plays by Henrik Ibsen, Everyman's library: the drama 494 - , London: J. M. Dent & Sons, - 1910. - Idle, Eric, Michael Palin, - Graham Chapman, John Cleese, Terry - Gilliam. The Complete Monty Python's Flying Circus: All the - Words, Pantheon Books, (1989), 2, p.230. - Imbs, Paul, Martin, - Robert, Straka, Georges, Mélanges de linguistique - française et de philologie et littérature médiévales offerts à Monsieur Paul - Imbs, 1973 . - Institut de Littérature Française Moderne de - l’Université de Neuchâtel, Présentation du projet Cyrus, En ligne, consulté le - 05-03-2010. - Ionesco, Eugène, La - cantatrice chauve, 1950. - 羅貫中，《三國演義》。 - - - - - Jakacki, Diane. Schema question: further constraining - @subtype based on @type. January 18, - 2021. TEI (Text Encoding Initiative) public discussion - list, . - Jarry, Alfred, tr. Simon Watson - Taylor and Cyril Connolly. The Ubu - plays, London: Methuen, - 1968. - Jean-Jacques Rousseau - Les confessions vol 6 - Jerome, Jerome K. - Three men in a boat (1889), chapter 6. - Joachim Heinrich - CampeWörterbuch der Deutschen Sprache. Erster Theil. A - bis - E., - 1807. - John, Lord Sheffield, The - Auto-biography of Edward Gibbon esq., (1846), 222. - Jonson, Ben. Bartholomew - Fair. - Jonson, Ben. Volpone, - J. B. Bamborough ed. Macmillan, 1963, - p.14. - Jonson, Ben. The Alchemist - , Douglas Brown ed. London: - Benn, 1966, I.1, - p.9. - Joyce, James. Ulysses: - The Bodley Head, 1960. p. - 933. - - Judith Patt, Michiko Warkentyne and Barry - Till. Haiku: Japanese Art and Poetry. 2010. - Pomegranate Communications, Inc. San Francisco. . - - - - - Karlstadt, Andreas - Bodenstein. Distinctiones Thomistarum. - Wittenberg - 1507. In Harald Bollbuck ed. Kritische Gesamtausgabe - Karlstadt - I, available: - - Kersey, John. Dictionarium - Anglo-Brittannicum: Or, a General English Dictionary. London: - J. Wilde, 1715. 2nd ed. - Kilian, Wilfrid, <ref - target="http://jubil.upmc.fr/sdx/pl/toc.xsp?id=GH_000484_001&fmt=upmc&idtoc=GH_000484_001-pleadetoc&base=fa" - >Neige et glaciers ; notes prises au cours de géologie de la Faculté des Sciences de - Grenoble par M. Alamelle</ref>, 1891-1895. - King, Martin Luther. Letter from Birmingham City - Jail. Philadelphia, PA: American Friends Service - Committee (1963). - Kipling, Rudyard. The mother - hive. In Actions and Reactions, - London: Macmillan, (1909). - - Kipling, Rudyard. Stalky & Co., - London: Macmillan (1899). - Kipling, Rudyard. Kim, - Macmillan, (1901), p. - 9. - Knuth, Donald Ervin. The Potrzebie - System of Weights and Measures, Mad Magazine33June 1957. - Koltès, - Bernard-Marie, Quai ouest, 1985. - Krummrey, Hans, Panciera, Silvio - Criteri di edizione e segni diacritici, Tituli 2 (1980), - 205-215. - Kyd, Thomas. Spanish Tragedy - (1592). - - - - La Fayette, Marie-Madeleine Pioche - de La Vergne, comtesse de, La Princesse de Clèves, - 1678. - La Fontaine, Jean de. L'Astrologue - qui se laisse tomber dans un puits In Fables Choisies, - Classiques Larousse, Paris: Librairie - Larousse, 1, 1940. - La Fontaine, Jean de. Le corbeau - et le renard In Fables Choisies, Classiques - Larousse, Paris: Librairie Larousse, - 1, 1940. - Laboratoire ATILF - - <ref target="http://www.atilf.fr/">Analyse et traitement informatique de la langue - française (ATILF)</ref> - , consulté le 07-05-2010. - - Laclos, Pierre Choderlos de. Les Liaisons - dangereuses (1772), 1963, p. - 13. - Ladurie, Emmanuel Le Roy. Montaillou, Middlesex: Penguin Books, - 1980, p. 3. - Lamartine, Alphonse de, - Méditations poétiques, 1820. - Lamothe, Alexandre - de - Principaux manuscrits latins et français conservés dans la Bibliothèque - impériale et dans celle de l'Ermitage à Saint-Pétersbourg, édition numérique, Bibliothèque de l'école nationale des - chartes, 1864. - Langendoen, D. Terence and Paul M. - Postal. Vastness of Natural Languages, - Oxford: Basil Blackwell, 1984, p. - 24, note 12. - Langendoen, D. Terence and Paul Postal. The - vastness of natural languages, Blackwell, , 1, 1984. - - Langland, William. The Vision of Piers Plowman. In - A.V.C. Schmidt ed. Langland: Vision of Piers Plowman: - "B" Text, opening. - Latin liturgical manuscript: Bod MS. Lat liturg. b. - 19, folio 4r. Taken from the digitized image described at . - Lavrentev, Alexei, - <ref target="http://ccfm.ens-lsh.fr/IMG/pdf/BFM-Mss_Encodage-XML.pdf">Manuel - d’encodage XML-TEI étendu des transcriptions de manuscrits dans le projet - BFM-Manuscrits</ref>, dernier enregistrement le 26 juin - 2008. - - Lawrence, David Herbert. Autograph manuscript of Eloi, Eloi, lama - sabachthani, Pierpont Morgan MA 1892; in p.129. - - Layamon. Brut, fol 65v of Bodleian MS. Rawlinson Poetry 32; - in 12(ii). - Le Grand Robert de la langue - française, 2004. - LeTourneau, Mark S. - English Grammar, 2001, New York: - Harcourt - p. 89. - - Leech, G., G. Myers, J. Thomas eds. - Spoken English on Computer: Transcription, Markup and - Applications. Harlow: Longman, - 1995. - Leech, Geoffrey and Mick Short. - Style in Fiction, London: - Longman, 1981, p.272. - - Lennon, John and McCartney, Paul. She - Loves You. The Beatles Anthology 1. - Capitol, 1995. - Léry, Jean de, Histoire faict - en la terre de Brésil, 1580. - - Lessing, Doris. Martha Quest. 1952, - pp. 52-53. - Letter of Mikołaj Orlik to Mikołaj Serafin, Gródek, January 13 - [1438]. Edited by Skolimowska et al. Available from - Lewis, Leopold Davis. The - Bells, (1871), translated from Erckmann-Chatrian, - Le Juif Polonais. - - Lewis, Wyndham. Tarr (1928), - Jupiter, 1968, p. 17. - 李白，《黃鶴樓送孟浩然之廣陵》。 - 李白，《靜夜思》。 - 《梁山伯與祝英台》 - 電影《梁山伯與祝英台》，舊版。 - 〈歷代漢文大藏經概述〉，李圓淨，原載《南行》第六期（南行學社編印）。 - Lillo, George. The London - Merchant (1731), epilogue. - 林覺民，《與妻訣別書》。 - Lincoln, Abraham. Second Inaugural - Address, 4 March 1865. In H. S. Commager, ed., - Documents of American History, 5th ed - Crofts American history series. New York: - Appleton-Century-Crofts, 1949, p.442. - 劉康，《對話的喧囂：巴赫汀文化理論評述》，台北：麥田，2005，二版。 - 劉康，《對話的喧聲：巴赫汀文化理論述評》，台北：麥田，2005，頁20-23。 - - Longman Dictionary of Contemporary English. Harlow, - Essex: Longman (1978). - Lorris, Guillaume de et - Meun, Jean deLe Roman de la Rose, 1230, - 1270-1285. - Lowe, David. Lost - Chicago, Boston: Houghton Mifflin, - (1978), p.30. - - Lowell, Amy. Autumn - haze.(1919). - Lucie Lichtig, M. - Klein de Joseph Losey : script, . l'Avant-scène cinéma, - n° 175, nov. 1976. - Luther, Martin [tr]. Die gantze - Heilige Schrifft Deudsch, Wittenberg 1545. Letzte zu Luthers Lebzeiten erchienene Ausgabe, - hsg. Hans Volz unter Mitarbeit von Heinz Blanke. Textredaktion Friedrich Kur, - München: Rogner & Bernhard, - 1972. - 《論語》卷七：憲問第十四。 - 羅貫中，《三國演義》。 - 魯迅，《狂人日記 》。 - 魯迅，《狂人日記》。 - 魯迅，《狂人日記》。 - - - - MacNeice, Louis. The Sunlight on - the Garden In E.R. Dodds, - The collected poems of Louis MacNeice, London: - Faber, 1966. - Examples from MacWhinney, Brian, 88, 87, cited by Johansson, S. - The approach of the Text Encoding Initiative to the encoding of spoken - discourse In Leech, G., G. Myers, J. - Thomas eds. Spoken English on Computer: Transcription, Markup - and Applications. Harlow: Longman, - 1995. - - Madan, Falconer, et al, A summary catalogue of western manuscripts - in the Bodleian Library at Oxford which have not hitherto been catalogued ... - Oxford, 1895-1953. 5: 515. - Cited in Driscoll, M.J. P5-MS: A general purpose tagset for - manuscript description in Digital Medievalist: - 2.1, (2006) - - Maingeneau, Dominique, - Analyser les textes de communication, 2007. - Any issue of the Malawi Daily Times. - - Malle, Louis, Zazie - dans le métro : script, l'Avant-scène cinéma, n° - 104, juin 1970. - - Manuélian, Hélène, Schang, Emmanuel, XML, DTD et - TEI pour un dictionnaire étymologique des créoles, édition électronique, - 12 Octobre 2007. - - The Manere of Good Lyuynge: fol. 126v of Bodleian MS Laud Misc 517; - in , p.8. - Marbury v. Madison, 1 Cranch, - 137 (1803), rpt. In H. S. Commager, ed., Documents of American History, 5th ed - Crofts American history series. New York: - Appleton-Century-Crofts, 1949, - p.192. - Marvell, Andrew. An Horatian - Ode, Bod. MS Eng. Poet d.49. - Mauriac, Claude, - La Marquise sortit à cinq heures, 1961. - Mauss, Marcel, - Sociologie et anthropologie, 1950. - McCarthy, Niall, No - Parachute: The Highest Falls People Survived, Statista, - November 18, 2020. . - McCarty, Willard. Introduction in Collaborative Research in the Digital - Humanities: A volume in honour of Harold Short on the occasion of his 65th - birthday, September 2010, ed. Marilyn Deegan and Willard - McCarty. London: Ashgate - (2012). - Melville, Herman, Moby - Dick. (1851). - Mendès-France, Pierre, - Œuvres complètes, 1984-1985. - 《孟子》〈三十三〉。 - - Miller, Henry. Death of a Salesman in - Atkinson, Brooks, - New Voices in the American Theatre, New York: - Modern Library, 1955, p.113. - - Milne, A. A. - The House at Pooh Corner. London: - Methuen & Co., 1928, p. - 83. - - Milton, John. Paradise Lost: A poem in X books - (1667), I, 1-10. - Milton, John. Poems of Mr John Milton, both - English and Latin... (1645). - Molière, L'École des - femmes, 1663. - Molière, Le Médecin - malgré lui, 1667. - Molière, Le Médecin - volant, 1673. - Montaigne, Michel de, - Essais, 1592. - Montesquieu, Charles-Louis de Secondat, - baron de la Brède et de, Lettres persanes, - 1721. - Montherlant, Henry de , - Pitié pour les femmes, 1936. - - Moore, George. Autograph manuscript of Memoirs of my dead - life, Pierpont Morgan MA 3421; in - - Moore, Thomas. Autograph manuscript of the second version of Lalla - Rookh, Pierpont Morgan MA 310; in 23. - - Moreland, Floyd L. and Rita M. Fleischer. Latin: An - Intensive Course, (1977) p.53. - - Des Minnesangs Frühling, Moser, Hugo, Helmut - Tervooren eds. 36., neugestaltete und erweiterte Auflage - I Texte, Stuttgart: S. - Hirzel Verlag, 1977. - Mošin, Vladimir A. Anchor Watermarks. - Amsterdam: Paper Publications Society (Labarre Foundation), 1973. - Monumenta Chartæ Papyraceæ Historiam Illustrantia; v. 13. - Mréjen, Valérie, Eau - sauvage, 2004. - - Zuigan calls himself "Master". Mumon Ekai. (In - The Gateless Gate, Case 12.) - Mustafa Siddik Altinakar, - René Walther (éds.), Hydraulique fluviale. Tome 16, Écoulement et - phénomènes de transport dans les canaux à géométrie simple , - 2008. - Mégnin, Michel (éd.), Tunis - 1900 Lehnert & Landrock photographes,2005. - - Nabokov, Vladimir - Pnin (1953) , p.14 - - - The New Penguin English Dictionary. London: - Penguin Books (1986). - - Derived from - New Zealand Parliament, Legislative Council. Nga Korero Paramete: 1881-1885 - (New Zealand Electronic Text Collection). 2008 - Wellington, New Zealand. - . - - - Njal's saga. tr. Magnus Magnusson and Hermann - Palsson. Penguin. (1960), chapter - 12, p.60. - - O'Casey, Sean. Time to go (1951). - Ollagnier, Jeanne, - Main, 2008. - Herodotus. On Libya, from the - Histories. - - [Letter of Capt. E. Hopkins. Providence, 10 Sep 1764] - - "[I am a curse]" in Original Manuscript Drafts for the Song of - Myself, Collection MSS3829, part of the Papers of Walt Whitman, Clifton Waller - Barrett Library of American Literature, Albert and Shirley Small Special Collections - Library, University of Virginia. - Ormesson, Jean d', La Douane de mer, 1993. - - Orwell, George. Nineteen-Eighty-Four. - London: Gollancz (1949). - - 大隅亜希子. 1996. 律令制下における権衡普及の実態: - 海産物の貢納単位を中心として. 史論 - 49. pp. 22–44. . - - Owen, Wilfred. Dulce et decorum est, from autograph - manuscript in the English Faculty Library, Oxford University. - - Owenson, Sydney. The Wild Irish Girl. Ed. - Kathryn Kirkpatrick. Oxford: Oxford - University Press, 1999, p. 17. - - - - 擺夷文經，中央研究院歷史語言研究所 。 - Pascal, Blaise, Le Mémorial, in Pensées,1670. - - Payne, J. - Report on the compatibility of J P French's spoken corpus transcription - conventions with the TEI guidelines for transcription of spoken texts, Working Paper, Dec 1992, NERC WP8/WP4 122. - - Peacock, Thomas Love. Gryll Grange - (1861), chapter 1. - Pennac, Daniel , - La Petite marchande de prose, 1978. - Perec, Georges, Espèces - d'espaces, 1974. - Perec, Georges, La Vie - mode d'emploi : romans, 1978. - Perec, Georges , Les - Choses, 1965. - Partial family tree for Bertrand Russell - based on an example in Pereira, Fernando C.N. and Stuart M. - Shieber, Prolog and Natural Language Analysis, - Stanford: Center for the Study of Language and - Information. (1987), p.22. - Pernoud, Régine, La - Femme au temps des Cathédrales, 1982. - Perreault, Simon, vCard Format Specification - Internet Engineering Task Force (IETF) (2011). - . - - Petit Larousse en Couleurs. Paris: - Larousse, (1990). - - Philipott, Thomas - Poems. (1646). - - Pinsky, Robert. Essays on Psychiatrists in Sadness and Happiness (1975). - Pix, Mary. The False Friend - (1699). - Plautus, Titus Macchius. Asinaria, or the - Comedy of Asses. Edited and translated by Wolfgang de Melo. Loeb - Classical Library 60. Cambridge, MA: Harvard University - Press (2011). - Plautus, Titus Macchius. Menaechmi. - Polac, Michel, Un - fils unique : script, l'Avant-scène cinéma, n° - 99, janvier. 1970. - - Pope, Alexander. The Rape of the Lock - (1714) III.7. - Pope, Alexander. An Essay on - Criticism (1711). - Pope, Alexander. Dunciad Variorum - (1729), III.284. - From letter 'JK' found in Poulson's Daily - Advertiser, - 8 Oct 1835. - Proust, Marcel, A la - recherche du temps perdu : Du côté de chez Swann, 1913. - Queneau, Raymond. Exercices de - style. Paris: Gallimard, - (1947), p. 192. - - - - 瓊瑤，《還珠格格》。 - Queneau, Raymond , - Journaux, 1914-1965. - - - - Rabelais, François. - Gargantua Lyon, 1542 - Rabelais, François - Tiers livre des faictz et dictz Heroïques du noble Pantagruel... - (1546), adapted from the website at - Renard, Jules, - Journal : 1887-1910, 1910. - Reference from the bibliography in Reps, Thomas - William and Teitelbaum, Tim eds. The - Synthesizer Generator: A system for constructing language-based editors, - New York and Berlin: - Springer-Verlag, 1989, p.304. - 日本法隆寺貝葉心經 (Wikipedia Sept 2008). - Richardson, Samuel. Clarissa; - or the History of a Young Lady (1748), 2 Letter XIV. - - Robert, Paul. Le Petit Robert. Paris: - Dictionnaires Le Robert (1967). - Rohmer, Eric, Ma nuit chez Maud : script, l'Avant-scène cinéma, - n°98, 2001. - Romains, Jules, - Knock, 1923. - Rostand, Edmond, Cyrano de - Bergerac, 1898. - Roubaud, Jacques, La - Boucle, 1993. - Rowling, J. K. - The Sorting Hat. In Harry Potter and the - Sorcerer's Stone, New York: Scholastic, Inc. (1999), chapter - 7, p. 121. - - - - - The Saga of the Volsungs: the Norse epic of Sigurd the Dragon - Slayer. trans. Jesse L. Byock. University of - California Press (1990). - Le Sanctoral du lectionnaire de - l'office dominicain (ms. Rome, Sainte-Sabine XIV L 1, f.142r et 189r-230v, Ecclesiasticum - officium secundum ordinem fratrum praedicatorum), édition électronique par - l'Ecole nationale des chartes, d'après l'édition d'Anne-Élisabeth - Urfels-Capot (Paris : Ecole nationale des chartes, 2007). - - 崎山理. 1985 - インドネシア語. 講座日本語学 - 11. 外国語との対照II. - 東京:明治書院 - 61-80 - - 三毛，〈沙漠中的飯店〉，《撒哈拉的故事》。 - 《三家詩鈔》，華培昌，藏於國家圖書館。 - Sapir, Edward. Language: an - introduction to the study of speech, New York: - Harcourt, Brace and World, 1921, p.79. - Shakespeare William, - Richard III, 1597. - Shakespeare, William. Henry V - In Mr. William Shakespeares Comedies, Histories, & Tragedies, - London: Jaggard and Blount, - 1623. - Shakespeare, William. Henry V - In The Works of Shakespeare in seven volumes, ed. Lewis - Theobald, London: Bettesworth, Hitch, Tonson et - al, (1733). - Shakespeare, William. Antony and - Cleopatra, IV.4, 14-21. - Shakespeare, William. Merchant of - Venice, I.ii, speech 5 (Portia). - Shakespeare, William. Macbeth, Act V, Scene 1. - Shakespeare, William. Antony - and Cleopatra (1623), V. - ii. - Shakespeare, William. Hamlet In Stanley Wells and Gary Taylor eds. - The Complete Works, Oxford: Clarendon - Press, 1986, I.i. - Shakespeare, William. Hamlet, London: Valentine Simmes. - (1603), I.i. - Shakespeare, William. The Tempest - In Mr. William Shakespeares Comedies, Histories, & - Tragedies, London: Jaggard and Blount, - (1623). - Shakespeare, William. Twelfth Night, or - What you Will In Mr. William Shakespeares Comedies, Histories, - & Tragedies, London: Jaggard and - Blount, (1623). - Shakespeare, William, The - Sonnets (1609), 18. - Shakespeare, William, The - Sonnets (1609), 130. - 莎士比亞，《終成眷屬 》。 - 莎士比亞，《馬克白》。 - Sharing Ancient Wisdoms, 2013, - available: . - Shaw, George Bernard. Heartbreak - House: a fantasia in the Russian manner on English themes (1919). - Shaw, George Bernard. Pygmalion, 1913. - Shields, David. Dead - Languages, HarperCollins Canada/Perennial - Rack, rpt. 1990, p.10. - Sinclair, John ed. Collins - COBUILD English Language Dictionary. London and - Glasgow: Collins, (1987), - p. 337 s.v. croissant. - 京劇《四郎探母》，1947年梅蘭芳演出。 - Smith, Adam. An Inquiry into the - Nature and Causes of the Wealth of Nations, London. - (1776), index to vol. 1. - - Smith, Sydney. Autograph letter. In Pierpont Morgan library; - 11. - - Smith, William. A New Classical Dictionary of Greek and - Roman Biography, Mythology, and Geography, Partly Based Upon the Dictionary of Greek and - Roman Biography and Mythology, New York: Harper - & Brothers, Publishers, 1860, 1026. - - Southey, Robert. Autograph manuscript of The Life of Cowper. - In Pierpont Morgan MA 412 ( 15). - Soyinka, Akinwande Oluwole Wole. Madmen and Specialists, London: - Methuen (1971). - - Spenser, Edmund. The Faerie Queene: Disposed into twelue - bookes, Fashioning XII. Morall vertues. (1596). - - Sterne, Laurence. The Life and Opinions of Tristram - Shandy, Gentleman. (1760). - - Stow, John A survey of the cities of London and Westminster: - containing the original, antiquity, increase, modern estate and government of those - cities. Written at first in the year MDXCVIII. By John Stow, citizen and native of London. - ... Now lastly, corrected, improved, and very much enlarged: ... by John Strype, ... In - six books. ... (London c.1525 - London 1605). - Sudetic, Chuck Serbs Tighten Grip On Eastern - Bosnia. New York Times, - April 20, 1992. - - SUEtheTrex, Twitter biography. . Accessed March 25th, - 2020. - Sutherland, L.S. and L.G. - Mitchell eds. The Eighteenth century, The - History of the University of Oxford V - , p.178. - 蘇童，《妻妾成群》。 - 蘇軾，《定風波》。 - - Swift, Jonathan. Travels into Several Remote Nations of - the World, in Four Parts. By Lemuel Gulliver... (1735). - Swift, Jonathan. Law is a bottomless pit, or - the history of John Bull (1712). - - Swinburne, Algernon Charles. Poems and Ballads (First - Series). London: Chatto & Windus. - (1904). - Swinnerton, Frank Arthur. The - Georgian Literary Scene 1910-1935, 1938, London: - J. M. Dent, p. 195. - - - - - 台灣，《結婚入盟誓》，1997年5月。 - 台灣區三碼與三加二碼郵遞區號 - 《台灣叢書》，伊能嘉矩著，藏於國立台灣大學圖書館。(http://catalog.ndap.org.tw/?URN=2155366 (Aug 2008)). - 唐．白居易．琵琶行 - - Taylor, John - The Cold Tearme or, The Frozen age, Or, The Metamorphosis of the Riuer of - Thames. London, 1621. [STC (2nd ed.) 23910]. - - TEI Consortium - Call for Papers - TEI 2022 Newcastle, 2022. - - The Castle of the Fly, in Russian Fairy Tales, - translated by Norbert Guterman from the collections of Aleksandr Afanas'ev, illustrations by - Alexander Alexeieff, folkloristic commentary by Roman Jakobson (New York: Pantheon Books, - 1947, rpt. [n.d.]), p. 25. - The Daily Telegraph, 21 Dec - 1992. - The Guardian, - 26 Oct 1992, p. 2 - The Guardian, - 21 Dec 1992, p. 2. - The Holy Bible, conteyning the Old Testament and the new... - appointed to be read in Churches. (1611), Genesis - 1:1. - The Independent, - 26 Oct 1775, headline. - Thurber, James. The 13 - Clocks (1950). - Tolkien, J. R. R. - The Monsters and the Critics. London: - George Allen & Unwin (1983). - - Townsend, Sue. The growing pains of Adrian Mole - (1984), p.43. - - Trollope, Anthony. An Autobiography - (1883). - - Trollope, Anthony. North America - (1862). - Truffaut, François et - Gruault, Jean, Les deux Anglaises et le continent : - script, l'Avant-scène cinéma, n° 121, - nov. 1971. - Tufte, Edward R., Envisioning - Information, Cheshire: Graphics Press. - (1990). - - - Ukraine Relief Fund - UBS - . - - United States Code Title 17, Section 107, found at . - - United States District Court for the Middle District of Pennsylvania. - Kitzmiller v. Dover Area School District et al.: 2005. - 04cv2688, p. 33. Available from and transcribed at . - - - - Valéry, Paul, Monsieur - Teste, 1929. - - Vergil (Publius Vergilius Naso). Aeneid, - I.1. - Verne, Jules, Cinq - semaines en ballon, 1863. - Verne, Jules, La - Chasse au météore, 1908. - Verne, Jules, Vingt - mille lieues sous les mers, 1870. - - Vinge, Vernor - Across realtime - ch 10 (1986). - Viton de Saint-Allais, Nicolas - , Dictionnaire encyclopédique de la noblesse de France, - 1816. - - Vóluspá recto of folio 5 of the unique manuscript of the Elder Edda. Codex - Regius, ed. L. F. A. Wimmer and F. Jónsson (Copenhagen 1891). - - - - - Wanklyn, M.D.G. et al. Gloucester Port Books, 1575-1765. - Available from . - - Wanton, Joseph. Unpublished letter to Nicholas Brown and Co, - 1761 - Brown University Steering Committee on Slavery and Justice: Repository of - Historical Documents. (). - - Warriner, John E. - English Composition and Grammar (1988), p.280. - - Webster's Seventh Collegiate Dictionary. Springfield, Mass. - G. & C. Merriam Co. (1975). - 魏飴，《小說鑑賞入門》，台北：萬卷樓，1999。 - Weil, Simone, Lettres à Antonio Atarès, in Oeuvres - complètes1988-. - - Williams, Nigel. The Wimbledon Poisoner - (1990), p. 204. - Winock, Michel, - Jeanne et les siens : récit, 2003. - - Wölfflin, Heinrich, trans. Hottinger, Marie - Donald Mackie (1932). Principles of art history: the problem - of the development of style in later art.. Originally published as Kunstgeschichtliche Grundbegriffe (1915). - - Woolf, Virginia. Mrs Dalloway (1925), - p.64, p.65. - - Wordsworth, William. Scorn not the sonnet in - Poetical Works (1827). - - Wordsworth, William. The Prelude (1850). - - Wrenn C. L. ed. Beowulf: with the Finnesburg - fragment, London: Harrap - (1953). - - 吳承恩，《西遊記》。 - - - Wycherley, William. The Country Wife - (1675). - - - 夏宇，〈甜蜜的復仇〉，《備忘錄》。 - 蕭紅，《呼蘭河傳》。 - - - - 幼莘貢俚賀曉濤之新婚賀詞 - 余秋雨 - 元曲。馬致遠，《天淨沙：秋思》。 - - - - 張錯， 《西洋文學術與手冊》，台北：書林，2005。頁201。 - - 珍．奧斯丁，《傲慢與偏見》。 - - 中國青年守則 - 中國學位論文全文數據庫 - 周慧玲，《表演中國：女明星表演文化視覺政治1910-1945》，2004。 - 朱自清， 《憶》跋。 - - Zimman, Lal. Lal Zimman - , accessed February 1, - 2021. - - Zupko, Ronald Edward - British Weights & Measures: A History from Antiquity to the Seventeenth - Century. Madison: University of Wisconsin - Press, 141-151. - - - - No source, made up for these Guidelines. - Example is copied from the source of these - Guidelines. - Undetermined. - - - -
-
- Works Cited Elsewhere in the Text of these Guidelines - - - - - Knuth - Donald E. - - Literate Programming - CSLI Lecture Notes 27 - 0-937073-80-6 - - Stanford, California - Center for the Study of Language and Information - 1992 - - - - - - - Mazzolini - Renato - G. - - Colonialism and the Emergence of Racial Theories - - - - Reproduction: Antiquity to the Present Day - - Nick - Hopwood - - - Rebecca - Flemming - - - Lauren - Kassell - - - Cambridge - Cambridge University Press - 2018 - - 361-374 - - - - - - Rubin - Gayle - - The Traffic in Women: Notes on the <q>Political Economy</q> of Sex - - - - Toward an Anthropology of Women - - Rayna - R. - Reiter - - - New York - Monthly Review Press - 1975 - - 157–210, 165 - - - - - - - A. G. - Petty - - English literary hands from Chaucer to Dryden - - London - Edward Arnold - 1977 - - 22–25 - - - - - - Lou - Burnard - - Report of Workshop on Text Encoding Guidelines - - - Literary & Linguistic Computing - - 3 - 1988 - - - - - - - Lou - Burnard - - - C. - Michael - Sperberg-McQueen - - The Design of the TEI Encoding Scheme - 10.1007/BF01830314 - - - Computers and the Humanities - - 29 - 1 - 1995 - 17–39 - - - Reprinted in , pp. 17-40 - - - - - Lou - Burnard - - - Sebastian - Rahtz - - RelaxNG with Son of ODD - - - - Proceedings of Extreme Markup Languages 2004 - - 2004 - - - - - - - M. - B. - Parkes - - English Cursive Book Hands 1250–1500 - - Oxford - Clarendon Press - 1969 - - - - - - British Literary Manuscripts. Series 2: from 1800 to 1914 - - Klinkenborg - Verlyn - - - Cahoon - Herbert - - - New York - Pierpont Morgan Library - 1981 - - - - - - - Paul - Grosso - - - Eve - Maler - - - Jonathan - Marsh - - - Norman - Walsh - - XPointer Framework - - - W3C - 25 March 2003 - - - - - - - Paul - Grosso - - - Eve - Maler - - - Jonathan - Marsh - - - Norman - Walsh - - XPointer element() Scheme - - - W3C - 25 March 2003 - - - - - - XHTML™ 1.0 The Extensible HyperText Markup Language (Second - Edition) - - - W3C - 26 January 2000 - - - - - - - Dave - Ragget - - - Arnaud - Le Hors - - - Ian - Jacobs - - HTML 4.01 Specification - - - W3C - 24 December 1999 - - - - - - - David - Carlisle - - - Patrick - Ion - - - Robert - Miner - - - Nico - Poppelier - - Mathematical Markup Language (MathML) Version 2.0 (Second - edition) - - - W3C - 21 October 2003 - - - - - - - Paul V. - Biron - - - Ashok - Malhotra - - XML Schema Part 2: Datatypes Second Edition - - - W3C - 28 October 2004 - - - - - - - Anders - Berglund - - Extensible Stylesheet Language (XSL) Version 1.1 - - - W3C - 5 December 2006 - - - - - - - James - Clark - - XSL Transformations (XSLT) Version 1.0 - - - W3C - 16 November 1999 - - - - - - - Michael - Kay - - XSL Transformations (XSLT) Version 2.0 - - - W3C - 23 January 2007 - - - - - - - Michael - Kay - - XSL Transformations (XSLT) Version 3.0 - - - W3C - 8 June 2017 - - - - - - - Tim - Bray - - - Jean - Paoli - - - C. M. - Sperberg-McQueen - - - Eve - Maler - - - François - Yergau - - Extensible Markup Language (XML) Version 1.0 (Fourth edition) - - - W3C - 16 August 2006 - - - - - - - Bert - Bos - - - Tantek - Çelik - - - Ian - Hickson - - - Håkon Wium - Lie - - Cascading Style Sheets Level 2 Revision 1 - - - W3C - 7 June 2011 - - - - - - - Håkon Wium - Lie - - - Bert - Bos - - Cascading Style Sheets, Level 1 - - - W3C - 11 January 1999 - - - - - - - fantasai - - - Koji - Ishi - - CSS Writing Modes Level 3 (W3C Candidate Recommendation) - - - W3C - 15 December 2015 - - - - - - - Simon - Fraser - - - Dean - Jackson - - - Edward - O'Connor - - - Dirk - Schulze - - CSS Transforms Module Level 1 (W3C Working Draft) - - - W3C - 26 November 2013 - - - - - - - Frank - Manola - - - Eric - Miller - - - Brian - McBride - - RDF 1.1 Primer - - - W3C - 24 June 2014 - - - - - - - Jonathan - Marsh - - - Richard - Tobin - - XML Base (Second Edition) - - - W3C - 28 January 2009 - - - - - - - James - Clark - - - Steve - DeRose - - XML Path Language (XPath) Version 1.0 - - - W3C - 16 November 1999 - - - - - - - Anders - Berglund - - - Scot - Boag - - - Mary F. - Fernández - - - Michael - Kay - - - Jonathan - Robie - - - Jérôme - Siméon - - XML Path Language (XPath) 2.0 - - - W3C - 23 January 2007 - - - - - - - Jonathan - Robie - - - Don - Chamberlin - - - Michael - Dyck - - - Jon - Snelson - - XML Path Language (XPath) 3.0 - - - W3C - 8 April 2014 - - - - - - - Jonathan - Robie - - - Michael - Dyck - - - Josh - Spiegel - - XML Path Language (XPath) 3.1 - - - W3C - 21 March 2017 - - - - - - - Tim - Bray - - - Dave - Hollander - - - Andrew - Laymon - - - Richard - Tobin - - Namespaces in XML 1.0 (second edition) - - - W3C - 16 August 2006 - - - - - - - Eric - van der Vlist - - RELAX NG - - - O'Reilly - 2004 - - - - - - - Renear - A. - - - Mylonas - E. - - - Durand - D. - - Refining our notion of what text really is: the problem of overlapping - hierarchies - - - - Nancy - Ide - - - Susan - Hockey - - Research in Humanities Computing - - Oxford University Press - 1996 - - - - - - - Robert - Sanderson - - - Paolo - Ciccarese - - - Benjamin - Young - - Web Annotation Data Model - - - W3C - 23 February 2017 - - - - - - - Robert - Sanderson - - - Paolo - Ciccarese - - - Benjamin - Young - - Web Annotation Vocabulary - - - W3C - 23 February 2017 - - - - - - The Unicode Standard, Version 5.0 - - Unicode Consortium - - Addison-Wesley Professional - 2006 - - - - - - - Addison - Phillips - - - Mark - Davis - - Tags for Identifying Languages - RFC 4646 - - 2006 - IETF - - - - - - - Addison - Phillips - - - Mark - Davis - - Matching of Language Tags - RFC 4647 - - 2006 - IETF - - - - - - - Mark - Davis - - - Ken - Whistler - - - Asmus - Freytag - - Unicode Character Database - - - Unicode Consortium - 2006 - - - - - - - - Fernando - C. - N. - Pereira - - Grammars and logics of partial information - - Menlo Park, CA - SRI International - 1987 - - - - SRI International Technical Note - 420 - - - - - - Bob - Carpenter - - The logic of typed feature structures - - Cambridge - Cambridge University Press - 1992 - - - - Cambridge Tracts in Theoretical Computer Science - 32 - - - - - - Stuart - Shieber - - An Introduction to Unification-based Approaches to Grammar - CSLI Lecture Notes 4 - - Center for the Study of Language and Information - Palo Alto, CA - 1986 - - - - - - Anglo-American Cataloguing Rules - Second Edition, 2002 revision, 2005 update - - Chicago - American Library Association - Ottawa - Canadian Library Association - 2002–2005 - - - - - - - - John - Burrows - - Computation into Criticism: A Study of Jane Austen's Novel and an - Experiment in Method - - Oxford - Clarendon Press - 1987 - - - - - - - - Klaus - Mattheier - - - Ulrich - Ammon - - - Peter - Trudgill - - Sociolinguistics - Soziolinguistik - An international handbook of the science of - language and society - Ein internationales Handbuch zur Wissenschaft - von Sprache und Gesellschaft - - Berlin - New York - De Gruyter - 1988 - I - 271 and 274 - - - - - - - J. - A. - Edwards - - - M. - D. - Lampert - - Talking Language: Transcription and Coding of Spoken Discourse - - Hillsdale, N.J. - Lawrence Erlbaum Associates - 1993 - - - - - - - Asmus - Freytag - - The Unicode Character Property Model - Unicode Technical Report #23 - - - 2006 - - - - - - - Mark - Davis - - - Aharon - Lanin - - - Andrew - Glass - - Unicode Bidirectional Algorithm - Unicode Standard Annex #9 - - - 2017-05-04 - - r. 37 - - - - - - - Stig - Johansson - - Encoding a Corpus in Machine-Readable Form - - - - - Sue - Atkins - - - Antonio - Zampolli - - Computational Approaches to the Lexicon: An Overview - - Oxford - Oxford University Press - 1994 - - - - - - - - Stig - Johansson - - - Lou - Burnard - - - Jane - Edwards - - - And - Rosta - - Working Paper on Spoken Texts - TEI document TEI AI2 W1 - - 1991 - - - - - - - - Brian - MacWhinney - - CHAT Manual - - Pittsburgh - Dept of Psychology, Carnegie-Mellon University - 1988 - 87ff - - - - - - - Bengt - Loman - - - Nils - Jørgensen - - Manual for analys och beskrivning av makrosyntagmer - - Lund - Studentlitteratur - 1971 - - - - - - - Robert - A. - Amsler - - - Frank - W. - Tompa - - An SGML-Based Standard for English Monolingual Dictionaries - - - Information in Text - Fourth Annual Conference of the U[niversity of] W[aterloo] - Centre for the New Oxford English Dictionary - Fourth Annual Conference of the U[niversity of] W[aterloo] Centre for the New - Oxford English Dictionary, October 26-28, 1988, Waterloo, Canada - - Waterloo, Canada - October 1988 - 61-79 - - - - - - - - N. - Calzolari - - - C. - Peters - - - A. - Roventini - - Computational Model of the Dictionary Entry: Preliminary - Report - Acquilex: Esprit Basic Research Action No. 3030, Six-Month - Deliverable - - Pisa - April 1990 - - - - - - - - John - Fought - - - Carol - Van Ess-Dykema - - Toward an SGML Document Type Definition for Bilingual - Dictionaries - TEI working paper TEI AIW20 - - available from the TEI. - - - - - - - - Nancy - Ide - - - Jean - Veronis - - Encoding Print Dictionaries - - - Computers and the Humanities - - 29 - 1995 - 167-195 - - - - - - - Nancy - Ide - - - Jacques - Le Maitre - - - Jean - Veronis - - Outline of a Model for Lexical Databases - - - Information Processing and Management - - 29 - 2 - 1993 - 159-186 - - - - - - - Nancy - Ide - - - Jean - Veronis - - - Susan - Warwick-Amstrong - - - Nicoletta - Calzolari - - Principles for Encoding machine readable dictionaries - - - Proceedings of the Fifth EURALEX International Congress, - EURALEX'92 - Fifth EURALEX International Congress, EURALEX'92, University of Tampere, - Finland - - 1992 - - - - - - - - The - DANLEX Group - - Descriptive tools for electronic processing of dictionary data - - - Lexicographica, Series Maior - - Tübingen - Niemeyer - 1987 - - - - - - - - Agnès - Tutin - - - Jean - Veronis - - Electronic dictionary encoding: customizing the TEI Guidelines - - - Proceedings of the Eighth Euralex International Congress - Eighth Euralex International Congress - - 1998 - - - - - - - N. - Ide - - - A. - Kilgarriff - - - L. - Romary - - A Formal Model of Dictionary Structure and Content - - - Proceedings of Euralex 2000 - Euralex 2000 - - Stuttgart - 2000 - 113-126 - - - - - - - William - A. - Gale - - - Kenneth - W. - Church - - Program for aligning sentences in bilingual corpora - - - Computational Linguistics - - 19 - 1993 - 75-102 - - - - - - - G. - N. - Leech - - - R. - G. - Garside - - Running a Grammar Factory - - - - S. - Johansson - - - A.-B. - Stenstrøm - - English Computer Corpora: Selected Papers and Research Guide - - Berlin - de Gruyter - New York - Mouton - 1991 - pp. 15-32. - - - - - - - - I. - Marshall - - Choice of Grammatical Word Class without Global Syntactic Analysis: - Tagging Words in the LOB Corpus - - - Computers and the Humanities - - 17 - 1983 - 139-50 - - - - - - - - R. - G. - Garside - - - G. - N. - Leech - - - G. - R. - Sampson - - The Computational Analysis of English: a Corpus-Based Approach - - Oxford - Oxford University Press - 1991 - - - - - - - - Gary - Chartrand - - - Linda - Lesniak - - Graphs and Digraphs - - Menlo Park, CA - Wadsworth - 1986 - - - - - - - - R. - Jackendoff - - X-Bar Syntax: A study of phrase structure - - - Linguistic Inquiry Monograph - - 2 - 1977 - - - - - - - - M. - Kytö - - - M. - Rissanen - - The Helsinki Corpus of English Texts - - - - M. - Kytö - - - O. - Ihalainen - - - M. - Rissanen - - Corpus Linguistics: hard and soft - - Amsterdam - Rodopi - 1988 - - - - - - - - Steven - DeRose - - Markup overlap: a review and a horse - - - - Proceedings of Extreme Markup Languages 2004 - - 2004 - - - - - - - Andreas - Witt - - Multiple Informationsstrukturierung mit - Auszeichnungssprachen. XML-basierte Methoden und deren Nutzen für die - Sprachtechnologie - - 2002 - - - Ph D thesis, Bielefeld University - See also - - - - - - - Mirco - Hilbert - - - Oliver - Schonefeld - - - Andreas - Witt - - Making CONCUR work - - - - Proceedings of Extreme Markup Languages 2005 - - 2005 - - - - - - - - Alex - Dekhtyar - - - Ionut - E. - Iacob - - A framework for management of concurrent XML markup - - - - - 2005 - - - - - - - - H. - V. - Jagadish - - - Laks - V. - S. - Lakshmanan - - - Monica - Scannapieco - - - Divesh - Srivastava - - - Nuwee - Wiwatwattana - - Colorful XML: one hierarchy isn't enough - - - - - - - 2004 - - - - - - - - Noureddine - Chatti - - - Suha - Kaouk - - - Sylvie - Calabretto - - - Jean - Marie - Pinon - - MultiX: an XML based formalism to encode multistructured - documents - - - - - - Proceedings of Extreme Markup Languages 2007 - - 2007 - - - - - - - - Patrick - Durusau - - - Matthew - Brook - O'Donnell - - Coming down from the trees: next step in the evolution of markup? - - - Proceedings of Extreme Markup Languages 2002 - - 2002 - - - - - - - - Jeni - Tennison - - - Wendell - Piez - - The layered markup and annotation language - - - Proceedings of Extreme Markup Languages Conference - - 2002 - - - - - - - - Claus - Huitfeldt - - - C. - Michael - Sperberg-McQueen - - TexMECS: An experimental markup meta-language for complex - documents - - - 2001 - - - - - - - D. Terence - Langendoen - - - Gary F. - Simons - - A rationale for the TEI recommendations for feature-structure - markup, - - - Computers and the Humanities - - 29 - 1995 - 167-195 - - - - - - British Standards Institute - BS 5605:1990: Recommendations for Citing and Referencing Published - Material - - 1990 - - - - - - British Standards Institute - BS 6371:1983: Recommendations for Citation of Unpublished - Documents - - 1983 - - - - - - Deutsches Institut für Normung - DIN 1505-2: Titelangaben von Dokumenten; Zitierregeln - - 1984 - - - - - - Die Deutsche Bibliothek - Regeln für die alphabetische Katalogisierung in wissenschaftlichen - Bibliotheken RAK-WB - - 2006 - - - - - - International Organization for Standardization - ISO 690:1987: Information and documentation – Bibliographic references – Content, - form and structure - - 1987 - - - - - - International Organization for Standardization - ISO 8601:2004: Data elements and interchange formats — Information interchange — - Representation of dates and times - - 2004 - - - - - - International Organization for Standardization - ISO 12620:2009: Terminology and other language and content resources – - Specification of data categories and management of a Data Category Registry for language - resources - - - 2009 - - - - - - International Organization for Standardization - ISO 19136:2007: Geographic information — Geography Markup Language (GML) - - 2006 - - - - - - International Organization for Standardization - ISO/IEC 19757-3:2006: Information technology — Document Schema Definition Languages - (DSDL) – Part 3: Rule-based validation – Schematron - - 2006 - - - - - - Istituto Centrale per il Catalogo Unico - Regole italiane di catalogazione per autori - - 1979 - - - - - - National Information Standards Organization - ANSI/NISO Z39.29 – 2005 (R2010) Bibliographic References - - 2010 - - - - - - ISBD: International Standard Bibliographic Description - - Berlin, München - De Gruyter Saur - 2011 - - - - IFLA Series on Bibliographic Control - 44 - - - - - Федеральное агентство по техническому регулированию и метрологии - (РОССТАНДАРТ) - ГОСТ Р 7.0.5-2008: Система стандартов по информации, библиотечному и - издательскому делу. Библиографическая ссылка. Общие требования и правила - составления - - 2008 - - - - - - Федеральное агентство по техническому регулированию и метрологии - (РОССТАНДАРТ) - ГОСТ 7.1—2003. Система стандартов по информации, библиотечному и - издательскому делу. Библиографическая запись. Библоиграфическое описание. Общие - требования и правила составления - - 2003 - - - - - - DCMI Usage Board - Dublin Core™ Metadata Element Set, Version 1.1: Reference Description - - - 2012-06-14 - - - - -
-
- Reading List -

The following lists of readings in markup theory and the TEI derive from work - originally prepared by Susan Schreibman and Kevin Hawkins for the TEI Education Special - Interest Group, recoded in TEI P5 by Sabine Krott and Eva Radermacher. They should be regarded - only as a snapshot of work in progress, to which further contributions and corrections are - welcomed (see further ).

-
- Theory of Markup and XML - - - - - C. - Michael - Sperberg-McQueen - - - Claus - Huitfeld - - Concurrent Document Hierarchies in MECS and SGML - - - Literary and Linguistic Computing - - 14 - 1 - 1999 - 29-42 - - - - - - - C. - Michael - Sperberg-McQueen - - Rabbit/duck grammars: a validation method for overlapping - structures - - - - Proceedings of Extreme Markup Languages 2006 - - 2006 - - - - - - - David - T. - Barnard - - - Lou - Burnard - - - Jean-Pierre - Gaspart - - - Lynne - A. - Price - - - C. - Michael - Sperberg-McQueen - - - Giovanni - Battista - Varile - - Hierarchical Encoding of Text: Technical Problems and SGML - Solutions - 10.1007/BF01830617 - - - - Computers and the Humanities - - 29 - 3 - 1995 - 211–231 - - - - - - - David - T. - Barnard - - - Lou - Burnard - - - C. - Michael - Sperberg-McQueen - - Lessons learned from using SGML in the Text Encoding Initiative - 10.1016/0920-5489(95)00035-6 - - - Computer Standards & Interfaces - - 18 - 1 - 1996 - 3–10 - - - - - - - Lou - Burnard - - What is SGML and how does it help? - - - - - Daniel - Greenstein - - Modelling Historical Data: Towards a Standard for Encoding and - Exchanging Machine-readable Texts - - St Katherinen - Max-Planck-Institut für Geschichte In Kommission bei Scripta Mercaturae - Verlag - 1991 - 81–91 - - - - Halbgraue Reihe zur Historischen Fachinformatik - - Herausg. von - - Manfred - Thaller - - - serie A - 11 - - - Revised version published as - - - - - Lou - Burnard - - SGML on the Web: Too Little Too Soon or Too Much Too Late? - - - - Computers & Texts - - 15 - 1995 - 12–15 - - - - - - - - Lou - Burnard - - What is SGML and How Does It Help? - 10.1007/BF01830315 - - - - Computers and the Humanities - - 29 - 1 - 1995 - 41–50 - - - Reprinted in , pp. 41-50 - - - - - Nancy - Ide - - - Jean - Veronis - - The Text Encoding Initiative: Background and Contexts - - Dordrecht - Boston - Kluwer Academic Publisher - 1995 - - - - - - - Lou - Burnard - - Is Humanities Computing an Academic Discipline? or, Why Humanities - Computing Matters - - - - 1999 - - - - Presented at an interdisciplinary seminar at the Institute for Advanced Technology - in the Humanities, University of Virginia, November 1999. - - - - - Lou - Burnard - - Using SGML for Linguistic Analysis: The Case of the BNC - - - - Markup Languages Theory and Practice - - 2 - 1999 - Cambridge, Massachusettes - MIT Press - 31–51 - - - Also published in , pp. 53–72 - - - - - Stephan - Moser - - - Peter - Stahl - - - Werner - Wegstein - - - Norbert - Richard - Wolf - - Maschinelle Verarbeitung Altdeutscher Texte V (Beiträge zum Fünften - Internationalen Symposion, Würzburg, 4–6 März 1997) - - Tübingen - Niemeyer - 2001 - - - - - - - Lou - Burnard - - - Elizabeth - Lalou - - - Peter - Robinson - - Vers un Standard Européen de Description des Manuscrits: Le Projet - Master - - - Documents Numeriques - Les Documents Anciens - - 3 - 1–2 - 1999 - Paris - Hermes Science Publications - 151-169 - - - - - - - Lou - Burnard - - XML: The Dream and the Reality - - - 1999 - - - Closing plenary address at the XML Europe Conference, Granada, May 1999 - - - - - Lou - Burnard - - - Claudia - Claridge - - - Josef - Schmied - - - Rainer - Siemund - - Encoding the Lampeter Corpus - - - - DRH98: Selected Papers from Digital Resources for the - Humanities - - London - Office for Humanities Communication - 2000 - - - - - - - - Lou - Burnard - - From Two Cultures to Digital Culture: The Rise of the Digital - Demotic - - - 2000 - - - Presented at CLIP, Alicante - - Published in Italian as - - - - - - Lou - Burnard - - Dalle «Due Culture» Alla Cultura Digitale: La Nascita del Demotico - Digitale - - Translated by - - Federico - Pellizi - - - - - Il Verri - Nella Rete - - 16 - 2001 - Milano - Monogramma - 9–22 - - - - - - - Lou - Burnard - - On the Hermeneutic Implications of Text Encoding - - - - - Domenico - Fiormonte - - - Jonathan - Usher - - New Media and the Humanities: Research and Applications - - Oxford - Humanities Computing Unit - 2001 - 31–38 - - - - - - - - Lou - Burnard - - Encoding Standards for the Electronic Edition - - - - - Matija - Ogrin - - Znanstvene Izdaje in Elektronski - Medij - Scholarly Editions and the Digital - Medium - - Ljubljana - Studia Litteraria ZRC ZAZU - 2005 - 12–67 - - - - - - - - Lou - Burnard - - Metadata for corpus work - - - - - Martin - Wynne - - Developing Linguistic Corpora: A Guide to Good Practice - - Oxford - Oxbow Books - 2005 - 30–46 - - - - - - - - Lou - Burnard - - - Katherine - O'Brien - O'Keefe - - - John - Unsworth - - Electronic Textual Editing - - - New York - Modern Languages Association - 2006 - - - - - - - Dino - Buzzetti - - Digital Representation and the Text Model - - - - New Literary History - - 33 - 1 - 2002 - 61–88 - - - - - - - - Paul - Caton - - Markup's Current Imbalance - - - Markup Languages: Theory and Practice - - 3 - 1 - 2001 - 1–13 - - - This paper was proceeded by reports at the Joint Annual Conference of the - Association for Computers and the Humanities and the Association for Literary and - Linguistic Computing in 1999 (Charlottesville, Virginia) and Extreme Markup Languages - 2000 (Montreal, Canada) - - - - - Ruey-Shun - Chen - - - Shien-Chiang - Yu - - Developing an XML Framework for Metadata System - - - - Proceedings of the 1st International Symposium on Information and - Communication Technologies - - Dublin - 2003 - 267–272 - - - - ACM International Conference Proceeding Series - 49 - - - This paper was presented in a session entitled "Electronic Document - Technology." - - - - - James - H. - Coombs - - Information Management System for Scholars - Technical Memorandum TM 69–2 - - Providence - Brown Computer Center - 1986 - - - - - - - James - H. - Coombs - - - Allen - Renear - - - Steven - J. - DeRose - - Markup Systems and The Future of Scholarly Text Processing - 10.1145/32206.32209 - - - - - Communications of the ACM - - 30 - 11 - 1987 - 933–947 - - - Reprinted with new commentary in , pp 85–118 - - - - - George - P. - Landow - - - Paul - Delany - - The Digital Word: Text-based Computing in the Humanities - - Cambridge, MA - MIT Press - 1993 - - - - - - - Robin - Cover - - Markup Languages and (Non-) Hierarchies - - - 2005 - - - Technology report from the Cover Pages - - - - - - Steven - J. - DeRose - - Structured Information: Navigation, Access, and Control - - - 1995 - - - Paper presented at the Berkeley Finding Aid Conference, April 4–6, 1995 - - - - - - Steven - J. - DeRose - - - David - G. - Durand - - - Elli - Mylonas - - - Allen - H. - Renear - - What is Text, Really? - - - Journal of Computing in Higher Education - - 1 - 2 - 1990 - 3–26 - - - Republished () as a "classic reprint" with invited - commentary and authors' replies in the ACM/SIGDOC - - - - - Steven - J. - DeRose - - - David - G. - Durand - - - Elli - Mylonas - - - Allen - H. - Renear - - What is Text, Really? - 10.1145/264842.264843 - - - Journal of Computer Documentation - - 21 - 3 - 1997 - 1–24 - - - - - - - Charles - F. - Goldfarb - - A Generalized Approach to Document Markup - - - - Proceedings of the ACM SIGPLAN SIGOA Symposium on Text - Manipulation - - New York - ACM - 1981 - 68–73 - - - Adapted as "Annex A. Introduction to Generalized Markup" in ISO 8879 - - - - - - Tony - Graham - - Unicode: What Is It and How Do I Use It? - - - Markup Languages: Theory & Practice - - 1 - 4 - 1999 - 75 - - - - - - - Susan - Hockey - - Creating and Using Electronic Editions - - - - Richard - J. - Finneran - - The Literary Text in the Digital Age - - Ann Arbor, MI - University of Michigan Press - 1996 - 1–22 - - - - - - - Susan - Hockey - - - Allen - Renear - - - Jerome - J. - McGann - - What is Text? A Debate on the Philosophical and Epistemological Nature - of Text in the Light of Humanities Computing Research - - - 1999 - - - Panel presented at ACH/ALLC 1999 - - - - - - Susan - Hockey - - Electronic Texts in the Humanities - - New York, NY - Oxford University Press - 2000 - - - - - - - Claus - Huitfeldt - - Multi-dimensional Texts in a One-dimensional Medium - 10.1007/BF01830270 - - - Computers and the Humanities - - 28 - 4/5 - 1994 - 235–241 - - - - - - - Claus - Huitfeldt - - Toward a Machine-Readable Version of Wittgenstein's Nachlaß: Some - Editorial Problems - - - - Hans - Gerhard - Senger - - Philosophische Editionen. Erwartungen an sie — Wirkungen durch - sie - - Tübingen - Max Niemeyer Verlag - 1994 - 37–43 - - - - Beihefte zu editio - 6 - - - - - - Leslie - Lamport - - Document Production: Visual or Logical? - - - - Notices of the American Mathematical Society - - 34 - 1987 - 621–624 - - - - Republished as - - - - - Leslie - Lamport - - Document Production: Visual or Logical? - - - - TUGboat - - 9 - 1 - 1988 - 8-10 - - - - - - - - - - John - Lavagnino - - Completeness and Adequacy in Text Encoding - - - - Richard - J. - Finneran - - The Literary Text in the Digital Age - - Ann Arbor, MI - University of Michigan Press - 1996 - 63–76 - - - - - - - Charles - Lightfoot - - Generic Textual Element Identification—A Primer - - Arlington - Graphic Communications Computer Association - 1979 - - - - - - - Joshua - Lubell - - Structured Markup on the Web: A Tale of Two Sites - - - - Markup Languages: Theory & Practice - - 1 - 3 - 1999 - 7–22 - - - - - - - - Tony - McEnery - - - Lou - Burnard - - - Andrew - Wilson - - - Paul - Baker - - Validation of Linguistic Corpora - - - 1998 - - - - Report commissioned by ELRA - - - - - Jerome - McGann - - The Rationale of Hypertext - - - - Kathryn - Sutherland - - Electronic Text: Investigations in Method and Theory - - New York, NY - Clarendon Press Oxford - 1997 - 19–46 - - - - - - - Jerome - McGann - - Radiant Textuality: Literature After the World Wide Web - - New York, NY - Palgrave Macmillian - 2001 - - - - - - - Jerome - McGann - - Marking Texts of Many Dimensions - - - - - Susan - Schreibman - - - Ray - Siemens - - - John - Unsworth - - A Companion to Digital Humanities - - Oxford - Blackwell - 2004 - 198–217 - - - - - - - - Alan - Morrison - - - Michael - Popham - - - Karen - Wikander - - Creating and Documenting Electronic Texts: A Guide to Good - Practice - - - (no date) - - - - - - - - Alois - Pichler - - Advantages of a Machine-Readable Version of Wittgenstein's - Nachlaß - - - - - Kjell - S. - Johannessen - - - Tore - Nordenstam - - Culture and Value: Philosophy and the Cultural Sciences. Beiträge des - 18. Internationalen Wittgenstein Symposiums 13–20. August 1995 Kirchberg am - Wechsel - - Kirchberg am Wechsel - Die Österreichische Ludwig Wittgenstein Gesellschaft - 1995 - 770–776 - - - - - - - - - Wendell - Piez - - Beyond the 'Descriptive vs. Procedural' Distinction - - - - - B. - Tommie - Usdin - - - Steven - R. - Newcomb - - Proceedings of Extreme Markup Languages 2001: Montreal, Canada - - 2001 - - - - - - - - - Michael - Popham - - What Is Markup and Why Does It Matter - - - - Michael - Popham - - - Lorna - Hughes - - Computers and Teaching in the Humanities: Selected Papers from the - CATH94 Conference held in Glasgow University September 9th-12th 1994 - - Oxford - CTI Centre for Textual Studies - 1996 - - - - - - - Liam - Quin - - Suggestive Markup: Explicit Relationships in Descriptive and - Prescriptive DTDs - - - - - B. - Tommie - Usdin - - - Deborah - A. - Lapeyre - - SGML'96 Conference Proceedings - - Alexandria, VA - Graphic Communications Association - 1996 - 405–418 - - - - - - - - Darrell - Raymond - - - Frank - Tompa - - - Derick - Wood - - From Data Representation to Data Model: Meta-Semantic Issues in the - Evolution of SGML - - - - Computer Standards & Interfaces - - 18 - 1 - 1996 - 25–36 - - - - - - - Allen - Renear - - - David - Durand - - - Elli - Mylonas - - Refining our Notion of What Text Really Is: The Problem of Overlapping - Hierarchies - - - - - Susan - Hockey - - - Nancy - Ide - - Research in Humanities Computing 4: Selected Papers from the 1992 - ALLC/ACH Conference - - Oxford - Oxford University Press - 1996 - 263–280 - - - - - - - - Allen - Renear - - Out of Praxis: Three (Meta)Theories of Textuality - - - - Kathryn - Sutherland - - Electronic Text: Investigations in Method and Theory - - New York, NY - Clarendon Press Oxford - 1997 - 107–126 - - - - - - - Allen - Renear - - The Descriptive/Procedural Distinction is Flawed - - - Markup Languages: Theory and Practice - - 2 - 4 - 2000 - 411–420 - - - - - - - - Allen - H. - Renear - - - David - Dubin - - - C. - Michael - Sperberg-McQueen - - Towards a Semantics for XML Markup - 10.1145/585058.585081 - - - - Richard - Furuta - - - Jonathan - I. - Maletic - - - Ethan - V. - Munson - - Proceedings of the 2002 ACM Symposium on Document Engineering - - McLean, VA - Association for Computing Machinery - 2002 - 119–126 - - - - - - - Allen - H. - Renear - - - Christopher - Phillippe - - - Pat - Lawton - - - David - Dubin - - An XML Document Corresponds to Which FRBR Group 1 Entity? - - - - - - B. - Tommie - Usdin - - - Steven - R. - Newcomb - - Proceedings of Extreme Markup Languages 2003: Montreal, Canada - - 2003 - - - - - - - - - Allen - H. - Renear - - - David - Dubin - - - C. - Michael - Sperberg-McQueen - - - Claus - Huitfeldt - - XML Semantics and Digital Libraries - - - - Proceedings of the 3rd ACM/IEEE–CS Joint Conference on Digital - Libraries - - Los Alamitos, CA - IEEE Computer Society - 2003 - 303–305 - - - - - - - - Allen - H. - Renear - - Text Encoding - - - - - Susan - Schreibman - - - Ray - Siemans - - - John - Unsworth - - A Companion to Digital Humanities - - Oxford - Blackwell - 2004 - 218–239 - - - - - - - - Susanne - Salmon-Alt - - Data Structures for Etymology: Towards an Etymological Lexical - Network - - - - BULAG: revue internationale annuelle - Numéro Etymologie - - 31 - 2006 - Besançon - Presses Universitaires de Franche-Comté - - - - - - - - Susan - Schreibman - - Computer-mediated Texts and Textuality: Theory and Practice - 10.1023/A:1016178200469 - - - Computers and the Humanities - - 36 - 3 - 2002 - 283–293 - - - - - - - Susan - Schreibman - - The Text Ported - 10.1093/llc/17.1.77 - - - Literary and Linguistic Computing - - 17 - 1 - 2002 - 77–87 - - - - - - - SGML Users' Group - - A Brief History of the Development of SGML - - - 1990 - - - - - - - - Frank - M. - Shipman - III - - - Catherine - C. - Marshall - - Formality Considered Harmful: Experiences, Emerging Themes, and - Directions on the Use of Formal Representations in Interactive Systems - 10.1023/A:1008716330212 - - - - Computer-Supported Cooperative Work - - 8 - 4 - 1999 - 333–352 - - - - - - - C. - Michael - Sperberg-McQueen - - - Claus - Huitfeldt - - Concurrent document hierarchies in MECS and SGML - 10.1093/llc/14.1.29 - - - Literary and Linguistic Computing - - 14 - 1 - 1999 - 29–42 - - - - - - - C. - Michael - Sperberg-McQueen - - - Claus - Huitfeldt - - - Allen - H. - Renear - - Meaning and Interpretation in Markup - - - Markup Languages: Theory and Practice - - 2 - 3 - 2000 - 215–234 - - - - - - - C. - Michael - Sperberg-McQueen - - - David - Dubin - - - Claus - Huitfeldt - - - Allen - Renear - - Drawing Inferences on the Basis of Markup - - - - - - B. - Tommie - Usdin - - - Steven - R. - Newcomb - - Proceedings of Extreme Markup Languages 2002: Montreal, Canada - - 2002 - - - - - - - - - Suzana - Sukovic - - Beyond the Scriptorium: The Role of the Library in Text - Encoding - - - - D-Lib - - 8 - 1 - 2002 - - - - - - - - University of Nebraska — Lincoln Libraries - - A Basic Guide to Text Encoding - - - - - - 2003 - - - - - - - - John - Unsworth - - Knowledge Representation in Humanities Computing - - - 2001 - - - Lecture I in the eHumanities NEH Lecture Series on Technology & the Humanities, - Washington, DC, April 3, 2001 - - - - - - John - Unsworth - - Scholarly Primitives: What Methods Do Humanities Researchers Have in - Common, How Might Our Tools Reflect This? - - - 2000 - - - Part of a Symposium on "Humanities Computing: Formal Methods, Experimental - Practice" sponsored by King's College, London - - - - - - Fabio - Vitali - - - Luca - Bompani - - - Paolo - Ciancarini - - Hypertext Functionalities with XML - - - Markup Languages: Theory & Practice - - 2 - 4 - 2000 - 389 - - - - - - - Dennis - G. - Watson - - Brief History of Document Markup - - - 1992 - - - Circular 1086. Florida Cooperative Extension Service, Institute of Food and - Agricultural Sciences, University of Florida - - - - - - Adriaan - van der - Weel - - The Concept of Markup - - - - Digital Text and the Gutenberg Heritage - - (no date) - 3 - - - in preparation; draft only - - - - - - Christopher - Welty - - - Nancy - Ide - - Using the Right Tools: Enhancing Retrieval from Marked-up - Documents - 10.1023/A:1001800717376 - - - - Computers and the Humanities - - 33 - 1–2 - 1999 - 59–84 - - - - -
-
- TEI - - - - - Syd - Bauman - - Keying NAMEs: the WWP Approach - - - - Brown University Women Writers Project Newsletter - - 2 - 3 - 1996 - 3–6 - 10–11 - - - - - - - Syd - Bauman - - - Julia - Flanders - - Odd Customizations - - - - Proceedings of Extreme Markup Languages 2004 - - 2004 - - - - - - - Syd - Bauman - - Tables of Contents TEI-style - - - - Lou - Burnard - - TEXT Technology: The Journal of Computer Text - Processing - Electronic Texts and the Text Encoding Initiative. A Special - Issue of TEXT Technology - - 5 - 3 - 1995 - Madison, SD - College of Liberal Arts, Dakota State University - 235–247 - - - - - - - Syd - Bauman - - - Terry - Catapano - - TEI and the Encoding of the Physical Structure of Books - 10.1023/A:1001769103586 - - - Computers and the Humanities - - 33 - 1–2 - 1999 - 113–127 - - - - - - - Syd - Bauman - - TEI HORSEing Around - - - - Proceedings of the Extreme Markup Languages 2005 - - 2005 - - - - - - - Malcolm - B. - Brown - - What is the TEI? - - - Information Technology and Libraries - - 13 - 1 - 1994 - 8 - - - - - - - Lou - Burnard - - The Text Encoding Initiative: A Progress Report - - - - Gerhard - Leitner - - New Directions in Corpus Linguistics - - Berlin - Mouton de Gruyter - 1992 - - - - - - - Lou - Burnard - - Rolling your own with the TEI - - - Information Services and Use - - 13 - 2 - 1993 - Amsterdam - IOS Press - 141–154 - - - - - - - Lou - Burnard - - The TEI: Towards an Extensible Standard for the Encoding of - Texts - - - - Seamus - Ross - - - Edward - Higgs - - Electronic Information Resources and Historians - - London - British Academy - 1994 - - - - - - - Lou - Burnard - - The Text Encoding Initiative: An Overview - - - - Geoffrey - Leech - - - Greg - Myers - - - Jenny - Thomas - - Spoken English on Computer: Transcription, Mark-up and - Application - - London - Longman - 1995 - - - - - - - Lou - Burnard - - The Text Encoding Initiative's Recommendations for the Encoding of - Language Corpora: Theory and Practice - - - 1997 - - - Prepared for a seminar on Etiquetación y extracción de información de grandes corpus - textuales within the Curso Industrias de la Lengua (14–18 de Julio de 1997). Sponsored - by the Fundacion Duques de Soria. - - - - - Lou - Burnard - - - Michael - Popham - - Putting Our Headers Together: A Report on the TEI Header Meeting 12 - September 1997 - 10.1023/A:1001710828622 - - - Computers and the Humanities - - 33 - 1-2 - 1999 - Dordrecht, Boston - Kluwer Academic Publishers - 39–47 - - - - - - An Agreement to Establish a Consortium for the Maintenance of the Text Encoding - Initiative - - - March 1999 - - - - - - - Lou - Burnard - - Text Encoding for Interchange: A New Consortium - - - 2000 - - - - - - - Fabio - Ciotti - - Il Manuale TEI Lite: Introduzione Alla Codifica Elettronica Dei Testi - Letterari - - Milano - Sylvestre Bonnard - 2005 - - - - - - - Sheau-Hwang - Chang - - The Implications of TEI - - - OCLC Systems and Services - - 17 - 3 - 2001 - 101–103 - - - - - - - Mavis - Cournane - - The Application of SGML/TEI to the Processing of Complex, Multi-lingual - Text - PhD Dissertation - - Cork, Ireland - University College Cork - 1997 - - - - - - - Digital Library Federation - - TEI and XML in Digital Libraries: Meeting June 30 and July 1, 1998, - Library of Congress, Summary/Proceedings - - - - 1998 - - - - - - - - Digital Library Federation - - TEI Text Encoding in Libraries: Guidelines for Best - Encoding Practices - Version 3.0 (October 2011) - - - 2011 - - - - - - - Timothy - J. - Finney - - Manuscript Markup - - - - Larry - W. - Hurtado - - The Freer Biblical Manuscripts: Fresh Studies of an American Treasure - Trove - - Atlanta, GA - Society of Biblical Literature - 2006 - 263-288 - - - - Text-critical studies - 6 - - - - - - Matthew - Gibson - - - Christine - Ruotolo - - Beyond the Web: TEI, the Digital Library, and the Ebook - Revolution - 10.1023/A:1021895322291 - - - Computers and the Humanities - - 37 - 1 - 2003 - 57–63 - - - - - - - Sylvain - Loiseau - - Les standards : autour d'XML et de la TEI - - - 2002 - - - - - - - - Lynn - Marko - - - Christina - Kelleher Powell - - Descriptive Metadata Strategy for TEI Headers: A University of Michigan - Library Case Study - 10.1108/10650750110402585 - - - OCLC Systems & Services - - 17 - 3 - 2001 - 117-20 - - - - - - - David - Mertz - - XML Matters: TEI — the Text Encoding Initiative - An XML Dialect for Archival and Complex Documents - - - 2003 - - - - - - - Alan - Morrison - - Delivering Electronic Texts Over the Web: The Current and Planned - Practices of the Oxford Text Archive - 10.1023/A:1001726011322 - - - Computers and the Humanities - - 33 - 1-2 - 1999 - 193-198 - - - - - - - Elli - Mylonas - - - Allen - Renear - - The Text Encoding Initiative at 10: Not Just an Interchange Format - Anymore — But a New Research Community - 10.1023/A:1001832310939 - - - Computers and the Humanities - - 33 - 1-2 - 1999 - 1-9 - - - - - - - Tobin - Nellhaus - - XML, TEI, Digital Libraries in the Humanities - - - - Portal: Libraries and the Academy - - 1 - 3 - 2001 - 267-277 - - - - - - - - Sebastian - Rahtz - - Building TEI DTDs and Schemas on demand - - - - 2003 - - - Paper presented at XML Europe 2003, London, March 2003 - - - - - Sebastian - Rahtz - - - Norman - Walsh - - - Lou - Burnard - - A unified model for text markup: TEI, Docbook, and beyond - - - 2004 - - - Paper presented at XML Europe 2004, Amsterdam, April 2004 - - - - - Allen - Renear - - Theory and Metatheory in the Development of Text Encoding - - - - - Michael - A. - R. - Biggs - - - Claus - Huitfeldt - - Philosophy and Electronic Publishing - - 1995 - - - Interactive seminar for the Monist - - - - - - Peter - Robinson - - Making a Digital Edition with TEI and Anastasia - - - (no date) - - - - - - - - David - Seaman - - The Electronic Text Center Introduction to TEI and Guide to Document - Preparation - - - 1995 - - - - - - - Gary - F. - Simons - - Using Architectural Forms to Map TEI Data into an Object-Oriented - Database - 10.1023/A:1001765030032 - - - Computers and the Humanities - - 33 - 1-2 - 1999 - 85-101 - - - - - - - David - Smith - - Textual Variation and Version Control in the TEI - 10.1023/A:1001795210724 - - - Computers and the Humanities - - 33 - 1-2 - 1999 - 103-112 - - - - - - - C. - Michael - Sperberg-McQueen - - Text in the Electronic Age: Textual Study and Text Encoding, with - Examples from Medieval Texts - 10.1093/llc/6.1.34 - - - Literary & Linguistic Computing - - 6 - 1 - 1991 - 34-46 - - - - - - - C. - Michael - Sperberg-McQueen - - The Text Encoding Initiative: Electronic Text Markup for - Research - - - - Brett - Sutton - - Literary Texts in an Electronic Age - - Urbana-Champaign, IL - University of Illinois at Urbana-Champaign, Graduate School of Library and - Information Science - 1994 - 35–55 - - - - - - - C. - Michael - Sperberg-McQueen - - Textual Criticism and the Text Encoding Initiative - - - - Richard - J. - Finneran - - The Literary Text in the Digital Age - - Ann Arbor, MI - University of Michigan Press - 1996 - 37–62 - - - - - - - Edward - Vanhoutte - - An Introduction to the TEI and the TEI Consortium - 10.1093/llc/19.1.9 - - - Literary & Linguistic Computing - - 19 - 1 - 2004 - 9 - - - - - - - T. - Kindberg - - - S. - Hawke - - The 'tag' URI Scheme - - RFC 4151 - - 2005 - IETF - - - - - -
-
-
diff --git a/P5/Source/Guidelines/fr/BIB-Bibliography.xml b/P5/Source/Guidelines/fr/BIB-Bibliography.xml new file mode 120000 index 0000000000..855da26128 --- /dev/null +++ b/P5/Source/Guidelines/fr/BIB-Bibliography.xml @@ -0,0 +1 @@ +../en/BIB-Bibliography.xml \ No newline at end of file From 0a482afd5cefb9356463f21797eb5334d2472ca0 Mon Sep 17 00:00:00 2001 From: Kiyonori Nagasaki Date: Wed, 28 Feb 2024 10:35:35 +0900 Subject: [PATCH 035/127] Add Japanese translation --- P5/Source/Specs/charDecl.xml | 1 + 1 file changed, 1 insertion(+) diff --git a/P5/Source/Specs/charDecl.xml b/P5/Source/Specs/charDecl.xml index 773cc98e34..21154aab05 100644 --- a/P5/Source/Specs/charDecl.xml +++ b/P5/Source/Specs/charDecl.xml @@ -11,6 +11,7 @@ $Id$ character declarations 문자 선언 文字描述 + 文字宣言 description de caractère descripción del carácter descrizione del carattere From 2d40b879c3312e5977ffef24062cee6fd0b4665c Mon Sep 17 00:00:00 2001 From: Kiyonori Nagasaki Date: Wed, 28 Feb 2024 11:56:24 +0900 Subject: [PATCH 036/127] Add Japanese translations --- P5/Source/Specs/choice.xml | 17 ++++++----------- P5/Source/Specs/cit.xml | 1 + P5/Source/Specs/citedRange.xml | 6 +++++- P5/Source/Specs/cl.xml | 6 ++++++ P5/Source/Specs/classCode.xml | 3 ++- P5/Source/Specs/classDecl.xml | 7 ++++--- P5/Source/Specs/classRef.xml | 20 ++++++++++++++++++++ P5/Source/Specs/classSpec.xml | 3 +++ P5/Source/Specs/closer.xml | 2 +- P5/Source/Specs/code.xml | 1 + P5/Source/Specs/colloc.xml | 3 ++- P5/Source/Specs/cond.xml | 1 + P5/Source/Specs/constitution.xml | 1 + P5/Source/Specs/constraint.xml | 2 ++ P5/Source/Specs/constraintSpec.xml | 9 +++++++++ P5/Source/Specs/content.xml | 11 ++++++++++- P5/Source/Specs/corr.xml | 1 + P5/Source/Specs/correction.xml | 1 + 18 files changed, 76 insertions(+), 19 deletions(-) diff --git a/P5/Source/Specs/choice.xml b/P5/Source/Specs/choice.xml index 481c3da878..3a9deedff0 100644 --- a/P5/Source/Specs/choice.xml +++ b/P5/Source/Specs/choice.xml @@ -99,18 +99,13 @@

Se Observa también que los elementos opción pueden ser uno mismo-jerarquía.

Para una versión especializada de la opción para codificar los testimonios múltiples de un único trabajo, ver la sección .

- +

- 要素choiceの子要素は全て、選択的な符号化方法を示している。 - 従って、それらは互いに排他的であるとするのが自然である。けれども、 - 並列的に符号化されていると考えられる場合もあるだろう。 -

-

要素choiceは、入れ子化できることにも注意して欲しい。 -

-

- 1つの作品にある複数の現存資料を要素choice符号化することに - ついては、を参照のこと。 -

+ choice要素の子要素は全て、同じ部分の異なる選択肢を示しているので、それらは択一的であるとするのが自然である。 + けれども、テキストを完全に表現するには複数の選択肢を並列的に扱う必要がある場合もあるだろう。

+

choice要素は、自らを入れ子にできることにも注意して欲しい。

+

符号化時にありうる選択肢ではなく、1つの作品にある複数の本文を記録する目的では、 + で扱われているapp要素などが望ましい。

diff --git a/P5/Source/Specs/cit.xml b/P5/Source/Specs/cit.xml index 452b3b4dee..4d60a8d3bd 100644 --- a/P5/Source/Specs/cit.xml +++ b/P5/Source/Specs/cit.xml @@ -15,6 +15,7 @@ citation citazione Zitat mit Referenz + 引用内容 contains a quotation from some other document, together with a bibliographic reference to its source. In a dictionary it may contain an example text with at least one occurrence of the word form, used in the sense being described, or a translation of the headword, or an example. diff --git a/P5/Source/Specs/citedRange.xml b/P5/Source/Specs/citedRange.xml index deb0192e3d..6e570c5c91 100644 --- a/P5/Source/Specs/citedRange.xml +++ b/P5/Source/Specs/citedRange.xml @@ -9,7 +9,9 @@ cited range + 引用範囲 defines the range of cited content, often represented by pages or other units + しばしばページやその他の単位で表される、引用の範囲を定める。 @@ -38,7 +40,9 @@ an identical value. When no clear endpoint is provided, the from attribute may be used without to; for example a citation such as p. 3ff might be encoded <citedRange from="3">p. 3ff</citedRange>.

- + +

1頁だけ引用された時は、同一の値を伴うfromとtoの属性を用いる。引用の終わりが与えられていない場合は、from属性は、toなしで用いることが許されている。例えば、p. 3ffのような引用は<citedRange from="3">p. 3ff</citedRange>と符号化されうる。

 + \ No newline at end of file diff --git a/P5/Source/Specs/cl.xml b/P5/Source/Specs/cl.xml index 93f9fa9fe5..573a7aadf4 100644 --- a/P5/Source/Specs/cl.xml +++ b/P5/Source/Specs/cl.xml @@ -13,6 +13,7 @@ $Id$ 子句 cláusula frase + 節 represents a grammatical clause. 문법적인 절을 표시한다. proposition @@ -62,6 +63,11 @@ etc. as appropriate.

L'attribut type peut être utilisé pour indiquer le type de proposition, avec des valeurs telles que subordonnée, infinitive, declarative, interrogative, relative etc.

+ +

type 属性は節のタイプを示すのに用いることができる。 + 内容に応じて finite（定形）、nonfinite（不定形）、declarative（平叙）、 + interrogative（疑問）、relative（連体修飾）などの値をとる。

+ diff --git a/P5/Source/Specs/classCode.xml b/P5/Source/Specs/classCode.xml index 8037f787b2..b60dae0927 100644 --- a/P5/Source/Specs/classCode.xml +++ b/P5/Source/Specs/classCode.xml @@ -14,6 +14,7 @@ $Id$ código de clasificación Klassifikationscode codice di clasificazione + 分類コード contains the classification code used for this text in some standard classification system. contient le code de classification attribué à ce texte en référence à un système standard de classification. @@ -40,7 +41,7 @@ $Id$ taxinomie utilisée. 사용하고 있는 분류 체계 또는 분류법을 표시한다. 說明使用中的分類系統或分類法。 - 当該分類法を定義する。 + 用いられている分類体系を定義するtaxonomy要素や他の資料などを指す。 benennt das verwendete Klassifikationssystem, definiert z. B. durch Verweis auf ein taxonomy-Element oder eine andere Ressource identifica el sistema de clasificación o taxonomía en diff --git a/P5/Source/Specs/classDecl.xml b/P5/Source/Specs/classDecl.xml index ebb75fedae..3e94e74a39 100644 --- a/P5/Source/Specs/classDecl.xml +++ b/P5/Source/Specs/classDecl.xml @@ -12,7 +12,8 @@ $Id$ déclaration de classification 분류 선언 分類宣告 - Angabe zur Klassifikation + 分類法宣言 + Angabe zur Klassifikation declaraciones de clasificación dichiarazioni sulla ckassificazione contains one or more taxonomies defining any classificatory @@ -20,8 +21,8 @@ codes used elsewhere in the text. contient une ou plusieurs taxinomies définissant les codes de classification utilisés n’importe où dans le texte. 텍스트 내 어디서든 사용될 수 있는 분류 부호를 정의하는 분류법을 포함한다. 包含一個或多個分類法，用來定義在文件中他處所使用之任何分類碼。 - 当該テキスト中で使用されている分類コードを定義する、ひとつ以上の分類 - 法を示す。 + 当該テキスト中で使用されている分類コードを定義する、 + ひとつ以上の分類法を示す。 enthält eine oder mehrere Taxonomien, die im Text verwendete Klassifikationscodes definieren. contiene una o más taxonomías que definen cualquier código usado en algún punto del texto. contiene una o più tassonomie che definiscono un qualsiasi codice classificatorio usato in un'altra porzione del testo. diff --git a/P5/Source/Specs/classRef.xml b/P5/Source/Specs/classRef.xml index f28b7afa08..9b9f8d7221 100644 --- a/P5/Source/Specs/classRef.xml +++ b/P5/Source/Specs/classRef.xml @@ -9,6 +9,7 @@ points to the specification for an attribute or model class which is to be included in a schema + スキーマに含まれる属性クラスあるいはモデルクラスの仕様を指し示す。 @@ -20,33 +21,40 @@ the identifier used for the required class within the source indicated. + 指示されたソースの中の要求されたクラスに対して使用される識別子。 indicates how references to this class within a content model should be interpreted. + 内容モデル内でこのクラスへの参照がどのように解釈されるべきなのかを示す。 any one member of the class may appear + クラスのいずれかのメンバーが出現し得る。 a single occurrence of all members of the class may appear in sequence + クラスのすべてのメンバーが順に1回ずつ出現し得る。 a single occurrence of one or more members of the class may appear in sequence + クラスの1つ以上のメンバーが順に1回ずつ出現し得る。 one or more occurrences of one or more members of the class may appear in sequence. + クラスの1つまたは複数のメンバーが1回以上、順に出現し得る。 one or more occurrences of all members of the class may appear in sequence + クラスのすべてのメンバーが1回以上、順に出現し得る。 @@ -63,14 +71,20 @@ (a+,b+,c+) when it has the value sequenceRepeatable.

 +

クラスのメンバーが a、bそしてcであるとして、 + expandの値がalternationならば、内容モデル内の該当クラスへの参照は，a|b|cへの参照として理解される。 + また、expandの値がsequenceならば、a,b,cへの，sequenceOptionalならば(a?,b?,c?)への、 + sequenceOptionalRepeatableならば(a*,b*,c*)への、そしてsequenceRepeatableならば(a+,b+,c+)への参照としてそれぞれ理解される。

 supplies a list of class members which are to be included in the schema being defined. + 定義されているスキーマに含まれるクラスメンバーのリスト。 supplies a list of class members which are to be excluded from the schema being defined. + 定義されているスキーマから除外するクラスメンバーのリスト。 @@ -94,6 +108,12 @@ class names conventionally begin with the letters att..

+ +

+ 属性クラスとモデルクラスは、それらが宣言されたclassSpecの要素においてident属性の値として指定された名前により、識別される。 + TEI内のすべての名前は一意である。属性クラス名は通常att.という文字ではじまる。 +

+ diff --git a/P5/Source/Specs/classSpec.xml b/P5/Source/Specs/classSpec.xml index a9e64e6e77..4560faed75 100644 --- a/P5/Source/Specs/classSpec.xml +++ b/P5/Source/Specs/classSpec.xml @@ -14,6 +14,7 @@ $Id$ especificación de la clase spécification de classe indicazione di classe + クラス仕様 contains reference information for a TEI element class; that is a group of elements which appear together in content models, or @@ -65,6 +66,7 @@ that is a group of modelo de contenido modèle de contenu modello di contenuto + 内容モデル members of this class appear in the same content models 이 부류의 원소는 동일 내용 모델에서 나타난다. 該元素集的元素出現在相同的內容模組中 @@ -80,6 +82,7 @@ that is a group of atributos attributs attributi + 属性の集合 members of this class share common attributes 이 부류의 원소는 공통 속성을 공유한다. 該元素集的元素有共用的屬性 diff --git a/P5/Source/Specs/closer.xml b/P5/Source/Specs/closer.xml index 8346d985d3..ec40b92766 100644 --- a/P5/Source/Specs/closer.xml +++ b/P5/Source/Specs/closer.xml @@ -16,7 +16,7 @@ $Id$ 구역의 마지막, 특히 편지의 종료부에 발문으로 나타나는 인사말, 날짜 표시란, 그리고 유사 구를 합하여 모아 놓는다. 匯集日期地點、署名、稱呼語、及其他在區段結尾出現的類似措辭，尤指信件結尾。 - 挨拶文言、日付欄など、ある区分の終わり、特に手紙の終わりにある一連の 文言をまとめる。 + 挨拶文言、日付欄など、ある区分の終わり、特に手紙の終わりにある一連の文言をまとめる。 regroupe une formule de politesse, une indication d'une date et d'autres expressions semblables figurant comme expression à la fin d’une division, en particulier à la fin d’une lettre. diff --git a/P5/Source/Specs/code.xml b/P5/Source/Specs/code.xml index 40e0259249..f0f386b5ec 100644 --- a/P5/Source/Specs/code.xml +++ b/P5/Source/Specs/code.xml @@ -31,6 +31,7 @@ programming language. lenguaje formal langage formel linguaggio formale + 形式言語 a name identifying the formal language in which the code is expressed 부호가 표현된 형식 언어를 식별하는 이름 diff --git a/P5/Source/Specs/colloc.xml b/P5/Source/Specs/colloc.xml index 0de6099e7d..b1d72b276f 100644 --- a/P5/Source/Specs/colloc.xml +++ b/P5/Source/Specs/colloc.xml @@ -14,10 +14,11 @@ $Id$ collocation colocación collocato + 連語 contains any sequence of words that co-occur with the headword with significant frequency. 표제어의 연어를 포함한다. 包含標題字的組合字。 - 見出し語の連語関係を示す。 + 見出し語と高い頻度で共起する任意の単語の連続を含む。 contient une collocation de l'entrée. indica la colocación de un lema contiene il collocato di un lemma. diff --git a/P5/Source/Specs/cond.xml b/P5/Source/Specs/cond.xml index 48d88ca063..503c21291b 100644 --- a/P5/Source/Specs/cond.xml +++ b/P5/Source/Specs/cond.xml @@ -14,6 +14,7 @@ $Id$ contrainte conditionnelle de structure de traits restricciones de estructura de rasgo condicional vincolo della struttura di tratti condizionato + 条件付き素性構造制約 defines a conditional feature-structure constraint; the consequent and the antecedent are specified as feature structures or feature-structure collections; the constraint is satisfied if both the diff --git a/P5/Source/Specs/constitution.xml b/P5/Source/Specs/constitution.xml index 25f8214d7e..cd9992436c 100644 --- a/P5/Source/Specs/constitution.xml +++ b/P5/Source/Specs/constitution.xml @@ -67,6 +67,7 @@ items, individuellement complets. plusieurs items plus petits, pas nécessairement complets. frammenti un texto construido a partir de la combinación de varios pequeños, no necesariamenteelementos completos. + 断片 a text made by combining several smaller, not necessarily complete, items 텍스트가 몇몇의 작은 항목으로 구성되어 있으나, 이 항목들은 반드시 완성된 것들은 아니다. diff --git a/P5/Source/Specs/constraint.xml b/P5/Source/Specs/constraint.xml index 0183768f58..10fa37b4dd 100644 --- a/P5/Source/Specs/constraint.xml +++ b/P5/Source/Specs/constraint.xml @@ -9,7 +9,9 @@ $Id$ constraint rules + 制約規則 the formal rules of a constraint + 形式的な制約規則 diff --git a/P5/Source/Specs/constraintSpec.xml b/P5/Source/Specs/constraintSpec.xml index 04455bddd5..710f7180f9 100644 --- a/P5/Source/Specs/constraintSpec.xml +++ b/P5/Source/Specs/constraintSpec.xml @@ -9,8 +9,11 @@ $Id$ constraint on schema + スキーマの制約 contains a formal constraint, typically expressed in a rule-based schema language, to which a construct must conform in order to be considered valid + 〔データの〕構造が妥当であるために満たしていなければならない形式的な制約。 + 通常は規則ベースのスキーマ言語で表現される。 @@ -87,10 +90,12 @@ $Id$ supplies the name of the language in which the constraints are defined + 制約を定義する言語名を示す。 ISO Schematron + ISO スキマトロン @@ -100,6 +105,10 @@ $Id$ schematron is used to indicate that ISO Schematron is used within the constraintSpec.

 + +

constraintSpecでのSchematron 1.xの利用は、このガイドラインでは推奨せず最近のTEIスタイルシートでもサポートしない。 + それ故、schematronの値はISO SchematronがconstraintSpecで用いられることを示すのに使う。

+ characterizes the diff --git a/P5/Source/Specs/content.xml b/P5/Source/Specs/content.xml index a0b75ca295..9288bfcb8f 100644 --- a/P5/Source/Specs/content.xml +++ b/P5/Source/Specs/content.xml @@ -14,10 +14,11 @@ $Id$ modèle de contenu declaración del esquema dichiarazione dello schema + 内容モデル contains a declaration of the intended content model for the element (or other construct) being specified. 기록된 스키마에 대한 선언 텍스트를 포함한다. 包含所記錄之模型的宣告文字。 - 当該スキーマの宣言を示す。 + 現在の要素（あるいは他の構造）に期待される内容モデルの宣言を含む。 contient la déclaration d'un modèle de contenu pour le schéma documenté. contiene el texto de la @@ -73,6 +74,9 @@ $Id$ not pattern names generated in the corresponding RELAX NG schema source are automatically prefixed to avoid potential nameclashes. + 名前衝突の可能性を避けるために、 + パターン名 [pattern name] + に生成元のRELAX NGスキーマソースに応じた接頭辞を自動的に付けるかどうかを制御する。 true @@ -83,6 +87,11 @@ $Id$ prefix attribute on the current schemaSpec + + 参照された個々の名前。 + たとえば、ある内容モデルの中での rng:ref + 要素には自動的にその時点のschemaSpecのprefix属性の値が付く。 + No prefixes are diff --git a/P5/Source/Specs/corr.xml b/P5/Source/Specs/corr.xml index 9bde810624..925b93f3e5 100644 --- a/P5/Source/Specs/corr.xml +++ b/P5/Source/Specs/corr.xml @@ -14,6 +14,7 @@ corrección correzione Korrektur + 修正 contains the correct form of a passage apparently erroneous in the copy text. 복사된 텍스트에서 오류로 보이는 단락의 정정 형식을 포함한다. 包含文本中看似錯誤並加以更正過後的文字。 diff --git a/P5/Source/Specs/correction.xml b/P5/Source/Specs/correction.xml index 21683e3e93..d8366e9e4a 100644 --- a/P5/Source/Specs/correction.xml +++ b/P5/Source/Specs/correction.xml @@ -15,6 +15,7 @@ $Id$ Korrekturverfahren principios de corrección principi di correzione + 修正の原則 states how and under what circumstances corrections have been made in the text. établit comment et dans quelles circonstances des corrections ont été apportées au texte. From 49c35a57e596c62d30b333229150775ac7744d00 Mon Sep 17 00:00:00 2001 From: Kiyonori Nagasaki Date: Thu, 7 Mar 2024 18:57:24 +0900 Subject: [PATCH 037/127] Add Japanese translation --- P5/Source/Specs/correspAction.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/P5/Source/Specs/correspAction.xml b/P5/Source/Specs/correspAction.xml index de1cfa7afc..6fccb22625 100644 --- a/P5/Source/Specs/correspAction.xml +++ b/P5/Source/Specs/correspAction.xml @@ -49,19 +49,19 @@ information concerning the transmission of a message, i.e. between the dispatch and the next receipt, redirect or forwarding. - メッセージの転送に関する情報。発送者と次の受信者、転送等。 + メッセージの伝達手段に関する情報。発信とその後の受信・転送等の間の情報。 information concerning the redirection of an unread message. - 未読なままに転送されるメッセージに関する情報。 + 〔開封せずに〕未読のままに転送されるメッセージに関する情報。 information concerning the forwarding of a message. - メッセージの転送に関する情報。 + 〔開封後の〕メッセージの転送に関する情報。 From 42da9bfecd6ac797a8ca62cd36fe472fe255f05c Mon Sep 17 00:00:00 2001 From: trishaoconnor Date: Thu, 7 Mar 2024 18:54:09 +0100 Subject: [PATCH 038/127] Added facets to constrain probability (#2519) --- P5/Source/Specs/teidata.probability.xml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/P5/Source/Specs/teidata.probability.xml b/P5/Source/Specs/teidata.probability.xml index 5267be894d..4b55a13514 100644 --- a/P5/Source/Specs/teidata.probability.xml +++ b/P5/Source/Specs/teidata.probability.xml @@ -13,8 +13,11 @@ definisce la gamma di valori di attributi che esprimono una probabilità - - + + + + +

Probability is expressed as a real number between 0 and 1; 0 representing certainly false and 1 representing certainly From fd666e9f0b88906520a42a0c8ab09b015ef69a61 Mon Sep 17 00:00:00 2001 From: Patricia O Connor Date: Thu, 7 Mar 2024 20:08:08 +0100 Subject: [PATCH 039/127] Update prose and added deprecation information for superEntry element --- .../Guidelines/en/DI-PrintDictionaries.xml | 26 +++++++++---------- P5/Source/Specs/superEntry.xml | 3 ++- 2 files changed, 14 insertions(+), 15 deletions(-) diff --git a/P5/Source/Guidelines/en/DI-PrintDictionaries.xml b/P5/Source/Guidelines/en/DI-PrintDictionaries.xml index e031829598..454de68c56 100644 --- a/P5/Source/Guidelines/en/DI-PrintDictionaries.xml +++ b/P5/Source/Guidelines/en/DI-PrintDictionaries.xml @@ -88,8 +88,7 @@ text.

Overall, dictionaries have the same structure of front matter, body, and back matter familiar from other texts. In addition, -this module defines entry, entryFree, -and superEntry as component-level elements which can occur +this module defines entry, and entryFree, as component-level elements which can occur directly within a text division or the text body.

The following tags can therefore be used to mark the gross structure of a @@ -102,7 +101,6 @@ in the following section. -

As members of the classes att.entryLike and @@ -162,9 +160,9 @@ etc.

basis of etymology, part-of-speech, or both, and typically provide a numeric superscript on the headword identifying the homograph number. In these cases each homograph should be encoded as a separate -entry; the superEntry element may optionally be used to group +entry; an outer entry element with a type attribute value of encompassing may be used to group such successive homograph entries. In addition to a series of -entry elements, the superEntry may contain a +entry elements, the entry may contain a preliminary form group (see section ) when information about hyphenation, pronunciation, etc., is given only once for two or more homograph entries. If the homograph number is to @@ -182,7 +180,7 @@ place where three-D would appear).

A dictionary with no internal divisions might thus have a structure like -the following; a superEntry is shown grouping two homograph + the following; an outer entry element with a type attribute value of encompassing is shown grouping two homograph entries. @@ -194,7 +192,7 @@ entries.

émeute
- +
grève @@ -205,7 +203,7 @@ entries. grève
- +

@@ -316,8 +314,8 @@ anomalous, as further discussed in section . In some dictionaries, homographs have separate entries; in such a case, as noted in section , the two homographs may be - treated as entries, optionally grouped in a superEntry: - + treated as entries, optionally grouped in an outer entry element with a type attribute value of encompassing: + @@ -330,7 +328,7 @@ such a case, as noted in section , the two homographs may b - +

The hierarchic structure of a dictionary entry is enforced by the @@ -646,14 +644,14 @@ appeal earnestly to ... [CP] -->

Alone among the constituent groups, form can appear at the -superEntry level as well as at the entry, hom, and +entry, hom, and sense levels: a.ban.don 1/@"band@n/ v [T1] 1 to leave completely and for ever; desert: The sailors abandoned the burning ship. 2 …abandon 2 n [U] the state when one's feelings and actions are uncontrolled; freedom from control...LDOCE - +

abandon a|ban|don @@ -679,7 +677,7 @@ feelings and actions are uncontrolled; freedom from control... - + + Because an entry can now occur inside an entry, the superEntry element is no longer needed. These Guidelines recommend using an entry with a type attribute value of encompassing instead. super entry groupe d'entrées groups a sequence of entries within any kind of lexical resource, such From 703bc6409b79d53a9b1a6ad0d6d7eb9faea7ea11 Mon Sep 17 00:00:00 2001 From: Patricia O Connor Date: Thu, 7 Mar 2024 20:25:50 +0100 Subject: [PATCH 040/127] Edited description in superEntry spec page --- P5/Source/Specs/superEntry.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/P5/Source/Specs/superEntry.xml b/P5/Source/Specs/superEntry.xml index e4505cd24d..58ddb6c909 100644 --- a/P5/Source/Specs/superEntry.xml +++ b/P5/Source/Specs/superEntry.xml @@ -2,7 +2,7 @@ - Because an entry can now occur inside an entry, the superEntry element is no longer needed. These Guidelines recommend using an entry with a type attribute value of encompassing instead. + Because an entry can now occur inside an entry, the superEntry element is no longer needed. For instances where the superEntry element was used to group multiple entry elements, these Guidelines recommend using an outer entry element with a type attribute value of encompassing instead. super entry groupe d'entrées groups a sequence of entries within any kind of lexical resource, such From 448787544d13aa8b5f6b76b6d851759fee9b2b8f Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Fri, 15 Mar 2024 11:45:33 -0400 Subject: [PATCH 041/127] =?UTF-8?q?initial=20creation=20of=20branch=20for?= =?UTF-8?q?=20work=20on=20the=20CMC-SIG=E2=80=99s=20new=20chapter=20(#2535?= =?UTF-8?q?)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * initial commit of new specs * lower-case model name * bibliography additions for CMC * add listRef and remove bibl references we don't do these bibl references here, do we? might go into a remalr, though? * migrate chapter from GoogleDoc * fix minor quirks * add membership to `att.cmc` * Various minor: * add xml:id= attrs to divisions (may not have all names right) * un-comment ref to character entry * change comments about work-to-be-done to processing instructions (yes, "winita" = “work is needed in this area” is obtuse, but it is what we use in the rest of the Guidelines) * in a few cases, changed quotation marks to phrase-level encoding * Re-generated spec lists. * testing * another test * Get build _almost_ working * Re-generated spec lists. * Fix a dozen validity errs. * fixes in exemplums: generation->generatedBy; closed

before and added rend=inline to the latter; added # to @synch and @who values; removed @who from and

` * update `xml:id`s on `` elements * example code for 9.3.2.1.3, and fixed several typos * section CMCanalysis * improved IDs in sect. analyses * Re-generated spec lists. * sections on analysis and multimodal * bib entries * correction emphasis * Pull in latest from TEI dev branch (including manual merge of docDate.xml), and correct a duplicate ID * Updates, mostly of REF placeholders * Add a PI reminding us to move a ref to bibl * Various minor edits, mostly made w/ CMC group during mtg * mocoda example for multimodal CMC 1st version * section and example with spoken/written/image post in encoding of multimodal cmc * Various updates, including constrain @generateBy to use within 'post' element * Updated another reference to 'children' of post element to descendants * entries mocoda, scilog * fixed timeline; improved bibliography, references and examples as specified in minutes * Add comment warning: need to use Schematron processor that can handle attribute context nodes. Note that I have not committed and pushed the addition of tests of the generatedBy= attribute in detest.xml, as it will break the build until it (the TEI build process) uses a Schematron processor that can handle. * more multimodal CMC and fixed some typos * promoted section Named Entities to 9.5.5 * Added tests for @generatedBy * Minor updates made at CMC meeting. * Invalid version we are in the middle of working on (particularly anonyization) * some typos * changed @corresp in @ref in example * fixed bib entries for corpora * extended section on NEs by pseudonymisation example using gap and supplied * some typos * some typos * fixed typo * restructuring of sections * some final typos * Fixes made during 2023-12-09 meeting with Harald * Editing pass through chapter; fix detest * addressed tei winita's by Syd, changed twitter examples by removing occurrences of and references to @key * some smithing re early CMC systems * use ptr for retweets and adapted descriptions * Minor wording (and whitespace) updates * minor tweaks, mostly removing previous questions that have been answered * Re-write last sentence of 9.5.5 and lots of spelling corrextions. * Tweak wording with Harald & Michael * Mostly typo corrections --------- Co-authored-by: Peter Stadler Co-authored-by: peterstadler Co-authored-by: Harald Luengen Co-authored-by: luengen --- P5/Exemplars/tei_all.odd | 27 +- P5/Exemplars/tei_allPlus.odd | 27 +- P5/Exemplars/tei_basic.odd | 27 +- P5/Source/Guidelines/en/BIB-Bibliography.xml | 351 ++++- .../en/CMC-ComputerMediatedCommunication.xml | 1302 +++++++++++++++++ .../en/Images/cmcunits-taxonomy.png | Bin 0 -> 24066 bytes .../en/Images/cmcunits-taxonomy.pptx | Bin 0 -> 39218 bytes P5/Source/Guidelines/en/ST-Infrastructure.xml | 2 + P5/Source/Specs/ab.xml | 1 + P5/Source/Specs/abbr.xml | 1 + P5/Source/Specs/add.xml | 1 + P5/Source/Specs/addName.xml | 1 + P5/Source/Specs/address.xml | 1 + P5/Source/Specs/affiliation.xml | 1 + P5/Source/Specs/alt.xml | 1 + P5/Source/Specs/altGrp.xml | 1 + P5/Source/Specs/anchor.xml | 1 + P5/Source/Specs/argument.xml | 1 + P5/Source/Specs/att.cmc.xml | 145 ++ P5/Source/Specs/bibl.xml | 1 + P5/Source/Specs/biblFull.xml | 1 + P5/Source/Specs/biblStruct.xml | 1 + P5/Source/Specs/binaryObject.xml | 1 + P5/Source/Specs/bloc.xml | 1 + P5/Source/Specs/byline.xml | 1 + P5/Source/Specs/c.xml | 1 + P5/Source/Specs/cb.xml | 1 + P5/Source/Specs/choice.xml | 1 + P5/Source/Specs/cit.xml | 1 + P5/Source/Specs/cl.xml | 1 + P5/Source/Specs/climate.xml | 1 + P5/Source/Specs/closer.xml | 1 + P5/Source/Specs/corr.xml | 1 + P5/Source/Specs/country.xml | 1 + P5/Source/Specs/date.xml | 1 + P5/Source/Specs/dateline.xml | 1 + P5/Source/Specs/del.xml | 1 + P5/Source/Specs/desc.xml | 1 + P5/Source/Specs/distinct.xml | 1 + P5/Source/Specs/district.xml | 1 + P5/Source/Specs/docAuthor.xml | 1 + P5/Source/Specs/docDate.xml | 1 + P5/Source/Specs/email.xml | 1 + P5/Source/Specs/emph.xml | 1 + P5/Source/Specs/epigraph.xml | 1 + P5/Source/Specs/expan.xml | 1 + P5/Source/Specs/fLib.xml | 1 + P5/Source/Specs/figure.xml | 1 + P5/Source/Specs/floatingText.xml | 1 + P5/Source/Specs/foreign.xml | 1 + P5/Source/Specs/forename.xml | 1 + P5/Source/Specs/formula.xml | 1 + P5/Source/Specs/fs.xml | 1 + P5/Source/Specs/fvLib.xml | 1 + P5/Source/Specs/gap.xml | 1 + P5/Source/Specs/gb.xml | 1 + P5/Source/Specs/genName.xml | 1 + P5/Source/Specs/geo.xml | 1 + P5/Source/Specs/geogFeat.xml | 3 +- P5/Source/Specs/geogName.xml | 1 + P5/Source/Specs/gloss.xml | 1 + P5/Source/Specs/graphic.xml | 8 +- P5/Source/Specs/head.xml | 1 + P5/Source/Specs/hi.xml | 1 + P5/Source/Specs/idno.xml | 1 + P5/Source/Specs/incident.xml | 1 + P5/Source/Specs/index.xml | 1 + P5/Source/Specs/interp.xml | 1 + P5/Source/Specs/interpGrp.xml | 1 + P5/Source/Specs/join.xml | 1 + P5/Source/Specs/joinGrp.xml | 1 + P5/Source/Specs/kinesic.xml | 1 + P5/Source/Specs/l.xml | 1 + P5/Source/Specs/label.xml | 1 + P5/Source/Specs/lb.xml | 1 + P5/Source/Specs/lg.xml | 1 + P5/Source/Specs/link.xml | 1 + P5/Source/Specs/linkGrp.xml | 1 + P5/Source/Specs/list.xml | 1 + P5/Source/Specs/listBibl.xml | 1 + P5/Source/Specs/listEvent.xml | 1 + P5/Source/Specs/listNym.xml | 1 + P5/Source/Specs/listObject.xml | 1 + P5/Source/Specs/listOrg.xml | 1 + P5/Source/Specs/listPerson.xml | 1 + P5/Source/Specs/listPlace.xml | 1 + P5/Source/Specs/listRelation.xml | 1 + P5/Source/Specs/location.xml | 1 + P5/Source/Specs/m.xml | 1 + P5/Source/Specs/macro.specialPara.cmc.xml | 29 + P5/Source/Specs/measure.xml | 1 + P5/Source/Specs/measureGrp.xml | 1 + P5/Source/Specs/media.xml | 1 + P5/Source/Specs/meeting.xml | 1 + P5/Source/Specs/mentioned.xml | 1 + P5/Source/Specs/milestone.xml | 1 + P5/Source/Specs/model.cmc.xml | 20 + P5/Source/Specs/name.xml | 1 + P5/Source/Specs/nameLink.xml | 1 + P5/Source/Specs/notatedMusic.xml | 1 + P5/Source/Specs/note.xml | 1 + P5/Source/Specs/noteGrp.xml | 1 + P5/Source/Specs/num.xml | 1 + P5/Source/Specs/objectName.xml | 1 + P5/Source/Specs/offset.xml | 3 +- P5/Source/Specs/opener.xml | 1 + P5/Source/Specs/orgName.xml | 1 + P5/Source/Specs/orig.xml | 1 + P5/Source/Specs/p.xml | 1 + P5/Source/Specs/pause.xml | 1 + P5/Source/Specs/pb.xml | 1 + P5/Source/Specs/pc.xml | 1 + P5/Source/Specs/persName.xml | 1 + P5/Source/Specs/persPronouns.xml | 1 + P5/Source/Specs/phr.xml | 1 + P5/Source/Specs/placeName.xml | 1 + P5/Source/Specs/population.xml | 1 + P5/Source/Specs/post.xml | 252 ++++ P5/Source/Specs/postscript.xml | 1 + P5/Source/Specs/ptr.xml | 1 + P5/Source/Specs/q.xml | 1 + P5/Source/Specs/quote.xml | 1 + P5/Source/Specs/ref.xml | 1 + P5/Source/Specs/reg.xml | 1 + P5/Source/Specs/region.xml | 1 + P5/Source/Specs/roleName.xml | 1 + P5/Source/Specs/rs.xml | 1 + P5/Source/Specs/ruby.xml | 3 +- P5/Source/Specs/s.xml | 1 + P5/Source/Specs/said.xml | 1 + P5/Source/Specs/salute.xml | 1 + P5/Source/Specs/seg.xml | 1 + P5/Source/Specs/settlement.xml | 1 + P5/Source/Specs/shift.xml | 1 + P5/Source/Specs/sic.xml | 1 + P5/Source/Specs/signed.xml | 1 + P5/Source/Specs/soCalled.xml | 1 + P5/Source/Specs/span.xml | 1 + P5/Source/Specs/spanGrp.xml | 1 + P5/Source/Specs/stage.xml | 1 + P5/Source/Specs/state.xml | 1 + P5/Source/Specs/surname.xml | 1 + P5/Source/Specs/table.xml | 3 +- P5/Source/Specs/term.xml | 1 + P5/Source/Specs/terrain.xml | 1 + P5/Source/Specs/time.xml | 1 + P5/Source/Specs/timeline.xml | 1 + P5/Source/Specs/title.xml | 1 + P5/Source/Specs/trailer.xml | 1 + P5/Source/Specs/trait.xml | 1 + P5/Source/Specs/unclear.xml | 3 +- P5/Source/Specs/unit.xml | 1 + P5/Source/Specs/vocal.xml | 1 + P5/Source/Specs/w.xml | 1 + P5/Source/Specs/writing.xml | 1 + P5/Source/guidelines-en.xml | 1 + P5/Test/detest.odd | 1 + P5/Test/detest.xml | 25 +- .../expected-results/detest_xml_relaxng.log | 34 +- P5/p5odds-examples.odd | 13 +- P5/p5odds.odd | 2 + P5/spec_lists.json | 2 +- 162 files changed, 2300 insertions(+), 120 deletions(-) create mode 100644 P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml create mode 100644 P5/Source/Guidelines/en/Images/cmcunits-taxonomy.png create mode 100644 P5/Source/Guidelines/en/Images/cmcunits-taxonomy.pptx create mode 100644 P5/Source/Specs/att.cmc.xml create mode 100644 P5/Source/Specs/macro.specialPara.cmc.xml create mode 100644 P5/Source/Specs/model.cmc.xml create mode 100644 P5/Source/Specs/post.xml diff --git a/P5/Exemplars/tei_all.odd b/P5/Exemplars/tei_all.odd index 2e7d468ea8..997b87b938 100644 --- a/P5/Exemplars/tei_all.odd +++ b/P5/Exemplars/tei_all.odd @@ -70,19 +70,20 @@ - - - - - - - - - - - - - + + + + + + + + + + + + + + diff --git a/P5/Exemplars/tei_allPlus.odd b/P5/Exemplars/tei_allPlus.odd index 27b61d2892..89b5137dec 100644 --- a/P5/Exemplars/tei_allPlus.odd +++ b/P5/Exemplars/tei_allPlus.odd @@ -70,19 +70,20 @@ - - - - - - - - - - - - - + + + + + + + + + + + + + + ERROR: cannot locate ODD changes for SVG diff --git a/P5/Exemplars/tei_basic.odd b/P5/Exemplars/tei_basic.odd index 924d39f7f8..03823d520d 100644 --- a/P5/Exemplars/tei_basic.odd +++ b/P5/Exemplars/tei_basic.odd @@ -4,7 +4,8 @@ TEI Basic - Hugh Cayless + Hugh Cayless + Syd Bauman TEI Consortium @@ -23,6 +24,9 @@

Derived from TEI All.

+ + Added CMC and re-numbered accordingly. + @@ -42,16 +46,17 @@ - - - - - - - - - + + + + + + + + + + - \ No newline at end of file + diff --git a/P5/Source/Guidelines/en/BIB-Bibliography.xml b/P5/Source/Guidelines/en/BIB-Bibliography.xml index afcbd6e9e5..c2044de1aa 100644 --- a/P5/Source/Guidelines/en/BIB-Bibliography.xml +++ b/P5/Source/Guidelines/en/BIB-Bibliography.xml @@ -5,7 +5,6 @@ Bibliography
Works Cited in Examples in these Guidelines - 阿城，《棋王》。 Académie française, @@ -14,8 +13,8 @@ consulté le 05-03-2010. Adams, Douglas. The Hitchhiker's Guide to the - Galaxy, New York: Pocket Books, 1979, - chapter 31. + Galaxy, New York: Pocket Books, + 1979, chapter 31. Agence bibliographique de l'enseignement supérieur, ABES:Site internet @@ -73,9 +72,8 @@ 白居易，《憶江南》。 Amheida I: Ostraka from Trimithis Volume 1: Texts from the 2004–2007 Seasons, - Bagnall, R. S. and G. R. Ruffini, with contributions by R. Cribiore and G. Vittmann - (2012). - + Bagnall, R. S. and G. R. Ruffini, with contributions by R. Cribiore and G. + Vittmann (2012). Baker, James K.. Night in Tarras. In Hilltop: A Literary Paper, vol 1 no 2. Wellington: Victoria University College @@ -120,8 +118,9 @@ Bowers, Jack Mixtepec-Mixtec Project Personography - - + + Beerbohm, Max. Autograph manuscript of The Golden Drugget, @@ -130,7 +129,7 @@ (1697). Beeton, Isabella. The book of Household Management, - London: S.O. Beeton + London: S.O. Beeton (1861). Belloc, Denis , Képas, 1989. @@ -184,12 +183,11 @@ Extract from British National Corpus () Text KB7, sentence 13730. - Brontë, Charlotte. Jane Eyre: An Autobiography, - Third edition; reprintLondon - Service & Paton, 1897; - Project Gutenberg, 1 December 2020. - chapter XII. - + Brontë, Charlotte. Jane Eyre: An Autobiography, + Third edition; reprintLondon + Service & Paton, 1897; Project + Gutenberg, 1 December 2020. chapter + XII. Browning, Robert. Letter to George Moulton-Barrett, Pierpont @@ -260,8 +258,8 @@ Writers Project, Northeastern University. 29 Mar. 2015. + temporarily removed until #1564 is resolved, i.e. WWP puts this somewhere that is not + behind paywall. -->. Centre national de la recherche scientifique (France). UMR 7118 ATILF, <ref target="http://atilf.atilf.fr/tlf.htm">Le Trésor de la Langue Française Informatisé (TLFI)</ref>, @@ -328,8 +326,8 @@ l'école, 1900. Collins English Dictionary, 12th edition - Glasgow: Collins - (2014). + Glasgow: Collins (2014). Collins Pocket Dictionary of the English language. London: Collins. @@ -664,7 +662,10 @@ (1959). Harvey, Gabriel. Four letters and certain sonnets specially touching Robert Greene... (1592). - Harvey, William. Exercitatio Anatomica De Motu Cordis Et Sanguinis In Animalibus, 1949 (Third edition, second printing), p. 74. + Harvey, William. Exercitatio Anatomica De Motu + Cordis Et Sanguinis In Animalibus, 1949 (Third edition, second + printing), p. 74. Hobbes, Thomas. Leviathan (1681). 《紅樓夢》第六回：賈寶玉初試云雨情 劉姥姥一進榮國府 @@ -695,8 +696,9 @@ ISO 690:1987: Information and documentation – Bibliographic references – Content, form and structure clause 4.1, p.2. - ISO 24611:2012 Language resource management — Morpho-syntactic annotation framework (MAF). - International Organization for Standardization. 2012. + ISO 24611:2012 Language resource management — + Morpho-syntactic annotation framework (MAF). International Organization + for Standardization. 2012. Ibsen, Henrik, tr. William and Charles Archer. Peer Gynt (1875). @@ -729,7 +731,7 @@ Institut de Littérature Française Moderne de l’Université de Neuchâtel, Présentation du projet Cyrus, En ligne, consulté le - 05-03-2010. + 05-03-2010. Ionesco, Eugène, La cantatrice chauve, 1950. 羅貫中，《三國演義》。 @@ -1002,7 +1004,8 @@ Parachute: The Highest Falls People Survived, Statista, November 18, 2020. . + />. + McCarty, Willard. Introduction in Collaborative Research in the Digital Humanities: A volume in honour of Harold Short on the occasion of his 65th @@ -1028,7 +1031,7 @@ Milton, John. Paradise Lost: A poem in X books (1667), I, 1-10. - Milton, John. Poems of Mr John Milton, both + <bibl xml:id="miltPo"><author>Milton, John</author>. <title>Poems of Mr John Milton, both English and Latin... (1645). Molière, L'École des femmes, 1663. @@ -1057,9 +1060,10 @@ Tervooren eds. 36., neugestaltete und erweiterte Auflage I Texte, Stuttgart: S. Hirzel Verlag, 1977. - Mošin, Vladimir A. Anchor Watermarks. - Amsterdam: Paper Publications Society (Labarre Foundation), 1973. - Monumenta Chartæ Papyraceæ Historiam Illustrantia; v. 13. + Mošin, Vladimir A. Anchor + Watermarks. Amsterdam: Paper Publications Society + (Labarre Foundation), 1973. Monumenta Chartæ Papyraceæ + Historiam Illustrantia; v. 13. Mréjen, Valérie, Eau sauvage, 2004. @@ -1078,13 +1082,11 @@ The New Penguin English Dictionary. London: Penguin Books (1986). - - Derived from - New Zealand Parliament, Legislative Council. Nga Korero Paramete: 1881-1885 - (New Zealand Electronic Text Collection). 2008 - Wellington, New Zealand. - . - + Derived from New Zealand Parliament, Legislative + Council. Nga Korero Paramete: 1881-1885 (New + Zealand Electronic Text Collection). 2008 + Wellington, New Zealand. . Njal's saga. tr. Magnus Magnusson and Hermann Palsson. Penguin. (1960), chapter @@ -1150,9 +1152,10 @@ >p.22. Pernoud, Régine, La Femme au temps des Cathédrales, 1982. - Perreault, Simon, vCard Format Specification - Internet Engineering Task Force (IETF) (2011). - . + Perreault, Simon, vCard Format + Specification + Internet Engineering Task Force (IETF) (2011). . Petit Larousse en Couleurs. Paris: Larousse, (1990). @@ -1229,9 +1232,10 @@ Boucle, 1993. Rowling, J. K. The Sorting Hat. In Harry Potter and the - Sorcerer's Stone, New York: Scholastic, Inc. (1999), chapter - 7, p. 121. - + Sorcerer's Stone, New York: Scholastic, + Inc. (1999), chapter 7, + p. 121. + @@ -1248,7 +1252,7 @@ 崎山理. 1985 インドネシア語. 講座日本語学 11. 外国語との対照II. - 東京:明治書院 + 東京:明治書院 61-80 三毛，〈沙漠中的飯店〉，《撒哈拉的故事》。 @@ -1382,7 +1386,8 @@ TEI Consortium Call for Papers - TEI 2022 Newcastle, 2022. + target="https://web.archive.org/web/20220516140643/https://conferences.ncl.ac.uk/tei2022/cfp/" + /> The Castle of the Fly, in Russian Fairy Tales, translated by Norbert Guterman from the collections of Aleksandr Afanas'ev, illustrations by @@ -1422,11 +1427,11 @@ (1990). - Ukraine Relief Fund + Ukraine Relief Fund UBS . - + target="https://web.archive.org/web/20220307150159/https://www.ubs.com/global/en/ubs-society/philanthropy/optimus-foundation/ukrainerelief.html" + />. United States Code Title 17, Section 107, found at . @@ -1555,6 +1560,12 @@
Works Cited Elsewhere in the Text of these Guidelines + + Scott E. Fahlman + "Joke" Conversation Thread in which the :-) Was Invented + + + @@ -1609,7 +1620,8 @@ Rubin Gayle - The Traffic in Women: Notes on the <q>Political Economy</q> of Sex + The Traffic in Women: Notes on the <q>Political Economy</q> of + Sex @@ -1658,6 +1670,248 @@ 22–25 + + + + + Michael + Beißwenger + + + Thomas + Bartz + + + Angelika + Storrer + + + Swantje + Westpfahl + + Tagset and guidelines for the PoS tagging of language data from genres of + computer-mediated communication / social media + + + 2015-09-13 + EmpiriST + 2015 Task Force: Michael Beißwenger, Kay-Michael Würzner, Sabine Bartsch, + Stefan Evert + + + + + + + + Michael + Beißwenger + + + Harald + Lüngen + + CMC-core: a schema for the representation of CMC corpora in TEI + + + + Corpus 20 (Special issue "Traitements, standardisation et analyse des + corpus de communication médiée par les réseaux sociaux) + Céline Poudat + Ciara R. Wigham + Loïc Liégeois + + 2020 + + + + + + Gerry and demolog + Blog comments to "Scheinzwerge oder Viele Probleme werden größer, wenn man sie + anpackt (Griechenland)" + https://scilogs.spektrum.de/wild-dueck-blog/scheinzwerge-oder-viele-probleme-werden-groesser-wenn-man-sie-anpackt-griechenland/ + 29-30 July 2015 + + + WILD DUECK BLOG + Gunter Dück + + https://scilogs.spektrum.de/wild-dueck-blog/ + + + SciLogs + + + Jossi et al. (2006-): Talk:Eiffel + (programming language)/Archive_1. URL: https://en.wikipedia.org/wiki/Talk:Eiffel_(programming_language)/Archive_1. English + Wikipedia talk page, Wikimedia Foundation. + + MiszaBot I et al. (2011-): Talk:Astronomical object. URL: https://en.wikipedia.org/wiki/Talk:Astronomical_object. English Wikipedia talk + page, Wikimedia Foundation. + + OnkelSchuppig et al. (2001-): Diskussion:FKM-Richtlinie. URL: https://de.wikipedia.org/wiki/Diskussion:FKM-Richtlinie. German Wikipedia talk + page, Wikimedia Foundation. + + + + Mobile Communication Database 2 (MoCoDa2) + + Michael + Beißwenger + + + Evelyn + Ziegler + + + Marcel + Fladrich + + + Wolfgang + Imo + + + Katharina + König + + + + https://db.mocoda2.de/c/home + + visited 30 March 2022 + + + + + + + Dortmund Chat Corpus + + Angelika + Storrer + + + Michael + Beißwenger + + + + http://hdl.handle.net/10932/00-03B0-14FA-A8D0-0F01-F + + 2017 + Leibniz-Institut für Deutsche Sprache + + + + + + + + Chanier + Thierry + + + Poudat + Céline + + + Sagot + Benoit + + + Antoniadis + Georges + + + Wigham + Ciara R. + + + Hriba + Linda + + + Longhi + Julien + + + Seddah + Djamé + + The CoMeRe corpus for French: structuring and annotating heterogeneous CMC + genres + + + JLCL (Journal of Language Technology and Computational Linguistics) (Special issue + on « Building And Annotating Corpora Of Computer-Mediated Discourse: Issues and + Challenges at the Interface of Corpus and Computational Linguistics) + + http://www.jlcl.org/2014_Heft2/Heft2-2014.pdf + 2014 + + 2 + 1-31 + + + + + + + Louis Alexander + Cotgrove + + Nottinghamer Korpus Deutscher YouTube-Sprache (The NottDeuYTSch Corpus) + + + http://hdl.handle.net/11372/LRT-4806 + + LINDAT/CLARIAH-CZ + 2018 + + + + + + + + + Ciara + Wigham + + + Thierry + Chanier + + Interactions between text chat and audio modalities for L2 communication and + feedback in the synthetic world Second Life + 10.1080/09588221.2013.851702 + + + Computer Assisted Language Learning + + 2015 + + 23 + 3 + + + @@ -3375,7 +3629,7 @@ International Organization for Standardization - ISO 8601:2004: Data elements and interchange formats — Information interchange — + <title>ISO 8601:2004: Data elements and interchange formats — Information interchange — Representation of dates and times 2004 @@ -4431,7 +4685,6 @@ + +
+ Computer-mediated Communication +

This chapter describes the TEI encoding mechanisms available for textual data which represents + discourse from genres of computer-mediated communication (CMC). It is intended to provide the + basic framework needed to encode CMC corpora.

+
+ General Considerations and Overview +

While the term computer-mediated communication, in a broader sense, might be used to + describe all sorts of communications between humans which are mediated by digital technologies + (for example, text on web pages, dialogic written interaction in chats and forums, the spoken + language in internet video meetings), herein we use the term to apply to forms of + communication which share the following features: + they are dialogic; + they are organized in the form of interactional sequences so that each communicative + move may determine the context for subsequent moves (typically taken by another + interlocutor) and may react to the context created by a prior move; + the communicative moves which may be put into practice as posts (cf. ), utterances, onscreen activities, or bodily activities exerted + by a virtual avatar are created and displayed using computer + technology (keyboard, mouse, speech-to-text conversion software, monitor or + screen) and transmitted over a computer network (typically the + internet). + +

+

Computer-mediated communication is conducted using + communication technologies such as chats, messengers, or online forums; + social media platforms and applications such as X (the platform formerly known as + Twitter), Facebook, Instagram, or WhatsApp; + the communication functions of collaborative platforms and projects (e.g. an online + learning environment, or a Wikipedia talk page); + 3D environments (e.g. Second Life or gaming environments); + or similar technologies and services on the internet. +

+

CMC is, by default, multimodal. Whereas early CMC systems + (e.g. Internet Relay Chat, IRC for short, the Usenet + newsgroups, or even the Unix talk system) + were completely ASCII-based, the lion’s share of contemporary CMC technologies and + applications allow for the combination of different semiotic resources (e.g. written or spoken + language with graphic icons and images) and even for the combined use of different CMC + technologies on one platform (e.g. combined use of an audio connection, a chat system, and a + 3D interface in which users control a virtual avatar as in many multiplayer online computer + games or in virtual worlds such as Second Life).

+
+
+ Basic Units of CMC +

This section describes the encoding mechanisms for the basic units of CMC and for their + combined use to encode CMC data.

+

We refer to units which are produced by an interlocutor to contribute to an ongoing CMC + interaction or joint CMC activity as basic CMC units. Contributions + to an ongoing interaction are produced to perform a move as part of the further development of + the interactional sequence, for instance in chats or forum discussions. Contributions to joint + CMC activities may not all be directly interactional; some may be part of a collaborative + project of the involved individuals. For example, editing activities in a shared text editor + or whiteboard in parallel with an ongoing CMC interaction (chat, audio conversation, or + audiovideo conference) in the same CMC environment in which these editing activities are + discussed by the collaborators.

+

Basic units of CMC can be described according to three criteria: (i) the temporal properties + of how these contributions are produced by their creators, transmitted via CMC systems, and + made accessible for the recipients; (ii) whether the unit as a whole is realised in a verbal + or nonverbal mode; (iii) for verbal units: whether the unit is realised in the written or + spoken mode. A taxonomy of basic CMC units resulting from these criteria is given in Fig. + . +

+
+ + Taxonomy of basic CMC units according to +
+

The most important distinction in the taxonomy + concerns the temporal nature of units exchanged via CMC technologies. The left part of the + taxonomy describes units that are performed (by a producer) and perceived (by a recipient) as + a continuous stream of behaviour. Units of this type can be performed as

+ + + i.e. stretches of speech which are produced to perform a speaker turn in a + conversation, + + i.e. nonverbal behavior (gesture, gaze) produced to perform a speaker turn, either + performed by the real body of an interlocutor (e.g. in a video conference) or through the + virtual avatar of an interlocutor in a 3D environment, + + i.e. non-bodily forms of behaviour that are transmitted to the group of interacting or + coworking participants, for instance the editing of content in a shared text editor which + can be perceived by the other parties simultaneously (as may be the case in learning or + collaboration environments). + +

The right part of the taxonomy describes units in + which the production, transmission, and perception of contributions to CMC interactions are + organised in a strictly consecutive order: The content — verbal, nonverbal, or multimodal — of + the contribution has to be produced before it can be transmitted via the internet and made + available on the computer monitor or mobile screen of any other party as a preserved and + persistent unit. We term this type of unit a post. Posts occur in + two different variants: + as written or multimodal posts, which are produced with an + editor form that is designed for the composition of stretches of written text. Most + contemporary post-based CMC technologies provide features for the inclusion of graphic and + audiovisual content (emoji graphics, images, videos) into posts and even to produce posts + without verbal content (which then may consist only of emojis, an image, or a video file). + Written and multimodal posts are the standard formats for user contributions in primarily + text-based CMC genres and applications such as chat, SMS, WhatsApp, Instagram, Facebook, X + (Twitter), online forums, or Wikipedia talk pages. + as audio posts, which are produced using a recording + function. In contrast to CMC units of the type utterance which + are produced and transmitted simultaneously, audio posts first have to be recorded as a + whole and are then transmitted — as audio files — via the internet; the availability of + the recording is indicated in the screen protocol by a template-generated, visual post; + the recipients can play the recording (repeatedly) by activating the play button displayed + in the post on the screen. Examples of CMC applications that implement audio posts are + WhatsApp or RocketChat. +

+

Three of the four basic CMC units described above can be represented with models that are + described elsewhere in the TEI Guidelines:

+ + + CMC unit + Type of corpus data + + TEI P5 element + + + utterance + transcription of speech + ⇒ + + u + + + + bodily activity + textual description + ⇒ + + kinesic + + + + onscreen activity + textual description + ⇒ + + incident + + +
+

The u, kinesic, and incident elements are not specific to CMC, but + are nonetheless used to encode textual transcriptions of spoken turns, bodily activity, and + onscreen activity that occur in CMC data. The CMC unit post, which is specific to + CMC, is introduced in .

+
+
+ Encoding Unique to CMC +

This section describes elements, attributes, and models which are unique to CMC and the TEI + CMC module.

+
+ CMC Posts +

The element post is unique to computer-mediated communication (CMC). + + A post is defined as a written (or spoken) contribution to an ongoing CMC + interaction which has been composed (or recorded) by its author in its entirety as part of a + private activity, transmitted through the internet, and made available on the monitor or + screen of the other parties en bloc. Posts occur in a broad range of written CMC genres, + including (but not limited to) messages in chats and WhatsApp dialogues, tweets in X + (Twitter) timelines, comments on Facebook pages, posts in forum threads, and comments or + contributions to discussions on Wikipedia talk pages or in the comment sections of + weblogs.

+

Posts can be either written or spoken: + written or multimodal posts: In + the majority of CMC technologies posts are composed as stretches of text using a + keyboard or speech-to-text conversion software in an entry form on the screen. In + many cases the technology allows authors to include or embed graphics (emojis or + images), video files, and hyperlinks into their posts. + audio posts: A growing number of CMC technologies, e.g. + messenger software such as WhatsApp or RocketChat, allow for an alternative, spoken + production of posts by providing a recording function which allows users to record a + stretch of spoken language and transmit the resulting audio file to the other + parties. +

+

The element post may co-occur with u, kinesic, + incident, or other existing TEI elements within a div, or directly within + the body, and may contain headings, paragraphs, openers, closers, or + salutations.

+

The post element is a member of the TEI attribute classes att.ascribed, att.canonical, att.datable, att.global, att.timed, and att.typed, and as such may take a + variety of attributes. Common attributes used in conjunction with post include + who, synch, type, subtype, rend, + and xml:id.

+
+
+ Attributes specific to CMC post +

Three attributes pertain specifically to post: + + + + The type of the content of a post (i.e., whether the content is written, an + image, a video clip, etc.) is indicated by the child elements of the post. (E.g., a + post might have a child p, or a child figure with a + graphic, or a child figure with a media, or some combination + thereof.) How that content was created — in particular whether it was recorded speech or not + — may be described with the modality attribute. Because spoken language differs + significantly from written language the suggested values only separate written + modality — which covers all cases other than spoken natural language — from + spoken. The use of modality is recommended but not required. + + +

+ screenshot of the google search for hairdresser "Pasha's Haare'm" + with the average google rating (4,5 of 5 stars), the address, the phone number, and + the opening hours. +
+ + +

+

The replyTo attribute is used to capture information drawn from the original + metadata associated with a post that asserts to which previous post the current post is a + response, or to which previous post it refers. This metadata is included by many, but not + all, CMC environments, when the user executes a formal reply action (e.g., by clicking or + tapping a reply button). This attribute should not be used to encode interpreted or inferred + reply relations based on linguistic cues or discourse markers.

+

The replyTo attribute indicates the replied-to or referred-to posts by providing + one or more pointers to them. In the following example, reply references in the source + indicate that the first post is a reply to an initial post that is not part of the + example, the second is a reply to the first, and the third is a reply to the second. + + +

Es hat den Anschein, als wäre bei BER durchaus große Kompetenz am Bau, allerdings + nicht in Form von Handwerkern….

+

http://www.zeit.de/2015/29/imtech-flughafen-berlin-ber-verzoegerung/komplettansicht

+ + +

Nein Nein, an den Handwerkern kann es rein strukturel nicht gelegen haben. Niemand + lässt seine Handwerker auf der Baustelle derart allein. Zudem gibt es höchstoffizielle + “Abnahmen” von Bauabschnitten/phasen. Welcher Mangel auch bestanden hatte, er hätte + Zeitnah auffallen müssen.

+

Uuups, für Imtek hab ich mal in einer Nachunternehmerfirma gearbeitet. Imtek is + offenbar ein universeler Bauträger, der alles baut.

+ + +

Stahlkunstruktionen dacht ich mal, was die bauen — oder bauen lassen.

+

Das ist schon ein übles Ding. Die Ausschreibungenund Angebote sind unauffällig, aber + wenn Unregelmässigkeiten auftreten (im Bauverlauf) dann gibt es die saftigen + Rechnungen. Da steht dann der Bauherr da und fragt sich, wie er denn so schnell einen + fähigen Ersatz herbekommt. Und diese Frage erübrigt sich meist, weil der Markt der + Baufirmen das nicht hergibt — weil tendenziel 100 % Auslastung. (und noch schlimmer: + Absprachen) Was auch Folge des Marktdrucks gewesen war.

+ + +

+

In the CMC genre of Wiki talk, users insert their contribution to a discussion by modifying + the wiki page of the discussion — the talk page. Since there is no technical reply action + available in wiki software, users apply textual indentation in the wiki code to indicate a + reply to a previous message, and a threaded structure is formed by a series of such + indentations. The attribute indentLevel records the level of indentation, that is + the nesting depth of the current post in such a thread-like structure (as defined by its + author and in relation to the standard level of non-indentation which should be encoded with + an indentLevel of 0). It is used in wiki talk corpora but may also be + used for other threaded genres, e.g. when HTML is used as a source.

+

The following is a sample encoding of a portion of a discussion among four different users + on a Wikipedia talk page. + +

+ [[WP:AUTO]] + +

I would kindly request from Mr. Meyer to allow others to edit the [...]

+ + +

I dont agree, this article is not about Dr. Meyer, [...]

+ + +

Why don't you read the policy. [...]

+ + +

Because the policy makes no sense, [...]

+ +
+ +

+
+
+ Attributes for General CMC Encoding +

The attribute generatedBy is also unique to CMC encoding. But unlike + modality, replyTo, and indentLevel, it is available not + only on the post element, but on any of its descendants as well. + + +

+

The generatedBy attribute may indicate, for post or any of its + descendants, how the content transcribed in an element was generated in a CMC environment. + That is, whether the source text being transcribed was created by a human user, created by + the CMC system at the request of a human user (e.g., when the user activates a template that + generates the content, such as in a signature), outright generated by the CMC system (e.g. a + status message or a timestamp), or generated by an automated process external to the CMC + system itself. This attribute is optional; when it is not specified on a post + element its value is presumed to be unspecified; when it is unspecified on any + descendant of post its value is inherited from the immediately enclosing element. + (And, in turn, if generatedBy is not specified on that element it inherits the + value from its immediately enclosing element, and so on up the document hierarchy until a + post is reached; the post either has a generatedBy attribute + specified or its presumed value is unspecified).

+ + +

A list of suggested values for generatedBy follows: + + when then content of the respective element was naturally typed or spoken by + a human user (cf. the chat posts in Example haircut) + + when the content of the respective element was generated after a human user + activated a template for its insertion (cf. signed and time i.e. the + signature in wiki talk in the second example below. + + when the content of the respective element was generated by the system, i.e. the CMC + environment (cf. the system message in an IRC chat in the fourth example below. + + when the content of the respective element was generated by a bot i.e. a non-human + agent, mostly external to the CMC environment + + when it is unspecified or unknown how the content of the respective element was + generated (cf. the retweet that forms the second post in the third example + below). + +

+ +

The following is a sample encoding of a chat post that contains an emoji. + Although the post was written by a human, the emoji itself was marked in + the source as having been generated by a template: + + + Da kostet ein Haarschnitt 50 € +

+ face screaming in fear + U+1F631 +
+ + +

+

In the following example, the user signature of a wiki talk post was inserted by activating + a template, and is thus marked accordingly: + +

I'm not sure that this is a proper criterium, or even what this means. What if we set + an explosion that breaks a comet into two pieces? What if we build a moon? Cheers, +

Greenodd (talk) + + +

+

In the following example, a tweet is specified as having been written by a human; however + inside the tweet, the timestamp is marked as generated by the CMC system: + + Heute mit super Unterstützung, wir grunzen, + wenn die Zeit vorbei ist. #bcrn18 + #wikidach PS: Die beiden brauchen noch Namen. Hinweise dazu am Empfang abgeben! + @AndreLo79 +

+ +
+ + + + + + +
+ +
+ + +

+

Finally, in the following example of an IRC post, the status message that user Interseb + has entered the room was generated by the system, i.e. the chat environment. + +

Interseb betritt den Raum.

+ + +

+
+
+
+ CMC Macrostructure +

In many CMC genres, posts come in a CMC document according to + which they are displayed, e.g. in a sequence or in threads; + posts within the document may be grouped. For example, in chat communication + such as WhatsApp, posts are part of a chat of one user with another user or among a + + group of users. When an entire chat is saved, typically a logfile of the + chat is obtained from the CMC system and downloaded. Similarly, Wikipedia discussions come in + a talk page, which ultimately is a web page containing the user posts, + sub-structured in threads. Likewise, YouTube comments come in a webpage containing the YouTube + video along with comment posts and posts replying to those comments displayed below the video. + The video serves as a prompt for the whole discussion. In forum discussions, the + prompt may be a news item, and in Wikipedia, an article may be viewed as the prompt for the + discussion on the talk page associated with that article.

+
+ Macrostructure of CMC Collections and Documents +

When CMC documents are compiled into a collection, dataset, or corpus, we distinguish the + following levels in the macrostructure of CMC in TEI: + +

The level of a corpus or collection of CMC texts of a particular genre, generally + obtained from a particular CMC platform, sometimes even from several platforms. This + level may be represented by either a TEI element or a teiCorpus + element. The teiHeader of the corpus (i.e., the teiHeader that is a + child of the outermost TEI or teiCorpus) will contain metadata in + its sourceDesc about the CMC platform(s). Metadata about the project + responsible for collecting the data and building the corpus, if applicable, should be + recorded as well.

+ + +

A set of posts collected (or sampled) by a researcher for analysis. The posts of + the document will often map directly to the set of posts grouped on an existing web + page, thread, or document within a CMC environment. Within the CMC environment the + document as such is often created by a particular user, thereby initiating the + communication which other users may read, and to which some other users might + contribute. This level will naturally be represented by the TEI element. The + teiCorpus (or TEI) element that represents the corpus will contain + one or more TEI elements as usual.

+

In the teiHeader of a document level TEI, the sourceDesc + will contain metadata about the CMC document such as its title, its author or owner, + its URL, the date of its creation, the date of the last change made to it, and other + metadata that are available and to be recorded such as one or more categories + associated with the document.

+

The document sometimes contains, or is associated with, a prompt such as a video or a + news item, either provided by the initiating user herself or located elsewhere and + referenced at the beginning of the document. In such cases, the teiHeader of + the document should also contain metadata about this prompt.

+ + +

The level of the individual post is naturally represented by the post + element; its encoding is further described in section . A + TEI element will contain a number of post elements, which can be + grouped or ordered in div elements representing sequences or threads (section + ) if appropriate.

 + + + + + + + + + + + + + + +
+ + + + + +
+ + + + + + +

+
+
+ Sequences, Sections, Threads +

As shown in Example above, nested threads of posts may be + encoded sequentially, while the indentLevel attribute of post is used to + keep track of the original nesting depth. This is especially meant for CMC text obtained + from a wiki code or HTML source, where it is not always entirely clear whether the + indentation information actually reflects a reply action from a user.

+

In genres where technical reply information is available for each post, reply links can be + encoded using the replyTo attribute on post elements, as shown in the + second example of . The network of all reply links will then + also form a threaded structure, and visual indentations can be reconstructed from it and + need not be explicitly encoded.

+

Threads may also be explicitly encoded as nested div elements as in the following + skeleton. +

+ ... +
+ ... + ... +
+ +
+
+
+ +

+

Using this encoding strategy, the thread from the second example in could be encoded as follows. +

+ +

Es hat den Anschein, ...

+ +
+ +

Nein Nein, an den Handwerkern kann es ...

+ +
+ +

Stahlkunstruktionen dacht ich mal, ....

+ +
+
+
+ +

+
+
+ Multimodal CMC +

As explained in section , the elements post, u, + kinesic, and incident are available to to encode textual transcriptions + of written posts, spoken turns, bodily activities of avatars, and onscreen activity by users + that occur in CMC data; and, as discussed in section , + graphics or other media data within posts are encoded in a post with + modality set to written. When two or more of these features occur in + a CMC interaction, we can speak of multimodal CMC.

+

Some basic multimodality is available in many private chat systems such as WhatsApp, where spoken and + written posts and media posts containing images or video clips can alternate in the sequence + of posts. The following shows the suggested encoding of an extended part of the haircut chat example from above, including a spoken post, several + written posts, and a post containing a graphic image (adapted from the MoCoDa2 corpus )

+ + In Düsseldorf gibt's da so Abstufungen. Da gibt's einmal Oliver + Schmidt, Oliver Schmidt's Hair Design, also dann, ist eher also, keine Ahnung, zum + Beispiel ich war da bei dem etwas Günstigeren dann. Ich weiß nicht, ob's das in Essen auch + gibt diese Abstufungen + Ich schau mal :) + Ich gehe immer nach Katernberg zu Pasha’s + haarem Hahaha also die sind echt entspannt und gut und nicht teuer + +
+ screenshot of the google search for hairdresser "Pasha's Haare'm" + with the average google rating (4,5 of 5 stars), the address, the phone number, and + the opening hours. +
+ + Olivers hair und Oliver Schmidt gehören + zusammen + +

In the graphical user interface (GUI) of a more complex multimodal CMC environment such as + Second life, a gaming and learning platform, interactions may consist of interleaved + occurrences of posts (p), utterances (u) and non-verbal acts such as + bodily activities (kinesic) or other on-screen activities (incident). In + the following example a spoken utterance, an avatar's bodily activity, and a written post + occur on the same level within the body element, representing parts of a multimodal + chat in Second Life (adapted from the Archi21 corpus). + + + ok + hm for me this presentation was hm become too fast because it's + always the same in our architecture school euh we have not time and hm too quickly sorry [...] + + + eat(popcorn) + + + + +

it went too quickly?

+ + + + +

+

Note that the spoken utterance u represents a speaker turn that was transmitted + via an audio channel of the application that is continuously open during a session, whereas + a spoken post represents a spoken message that has been recorded in private and + been posted to the CMC server as a whole. See section .

+
+
+
+ Documenting CMC (and providing general metadata) +
+ Documenting the Source of a Corpus of CMC data +

The teiHeader of the corpus should contain metadata about the CMC platform(s), + e.g. its name, information about its owner (often a company) including their address or + location, the URL of the server where the CMC data were collected from, or the filename of a + database dump that was used as a source. Metadata about the project responsible for + collecting the data and building the corpus, if applicable, should be recorded as well.

+

The following example shows the sourceDesc of a Twitter corpus. + + + + Twitter Sample + + + Twitter International Company +

+ 1 Cumberland Place + Fenian Street + Dublin 2 + D02 AX07 + Ireland +
+ + + + +

+

The following example shows how a Wikipedia database dump may be encoded as the source. + + + + + German Wikipedia Data Dump of 2019-08-01 + + + Dump file in XML (compressed) + + + + + + Wikimedia Foundation, Inc. + + + + 01 Aug 19 + dewiki-2019-08-01-pages-meta-current + + + + +

+
+
+ Documenting the Source of a CMC Document +

A CMC document may be a chat logfile, a discussion page, or a thematical thread of posts + and is encoded within a TEI element. Among the metadata to be recorded in the + sourceDesc of its teiHeader are, if available, its title, author or + owner, its URL, the date of its creation and/or the date of its last change (i.e. the time + when the last post was added to it).

+

The following example is the sourceDesc of a TEI encoding of a YouTube page that + contained a video and user comments on the video (which are encoded in the body of + the text as posts). The metadata contain a URL reference to the video and the YouTube + channel that posted the video in relatedItem elements. The date when the page was + created is not known. The example is adapted from the NottDeuYTSch corpus (), where the video itself is not contained in the corpus. + + + Iron Man 3 in 3D (Official Trailer German) Parodie + + DieAussenseiter + posted video, created page + + YouTube + + + DieAussenseiter’s Channel + + + + + +

+

The following example is the sourceDesc of a Wikipedia talk page. Note that a + relatedItem element is used to record a reference to the Wikipedia article that + the transcribed discussion is about. + + + Diskussion:FKM-Richtlinie + OnkelSchuppig, et al. + Wikimedia Foundation, Inc. + + + 7632113 + + FKM-Richtlinie + + + + +

+
+
+ Documenting the Sampling of CMC data +

The documentation of how the data were collected, e.g. how it was scraped or sampled from + the web, or downloaded from a server, should be recorded in the samplingDecl. Like + other metadata, information about sampling should be recorded at the highest level + applicable. That is, if the information applies to an entire corpus, the + samplingDecl should appear in the teiHeader of the corpus level; if the + information is different for each document, it should appear in the teiHeader of + the document level texts.

+

The sampling information typically considered of interest consists of at least the + following four components: + interface: The API that was used for the download, possibly encoded as a name + type="API"; + client: The client or other tool that was used for the download, possibly encoded as + a name type="client"; + query: The query or command used for the download, possibly encoded with a ptr + type="query" when it is a URI, or a code when it is a command; + date: The date of the download. + For example, in the case of an X (Twitter) corpus a sampling declaration might look + like the following: + +

Sampled using the Twitter Filtered stream v2-API (see ) Filtered for the German language and the following countries: Germany, Austria, + Belgium, Switzerland, Denmark, and Luxembourg. Downloaded on Mon 12 Dec 22 using the command + requests.get("https://api.twitter.com/2/tweets/search/stream", + headers=headers, params=params, stream=True,) in the python script collectFilteredTwitterStream.py.

+ + +

+

The samplingDecl of a Usenet Newsgroup corpus: + +

Downloaded from the news.individual.de server on 2016-01-15 using nntp client in + Python

+ + +

+
+
+ Participants +

A listPerson may be used to maintain an inventory of users and bots taking part in + a CMC interaction, along with information about them. As with other such contextual + information, it may be kept in the teiHeader (where it would occur in a + particDesc within a profileDesc) or in a separate document completely. + In either case, an encoded post may then be linked to its author by use of the + who attribute.

+

In the following example, a list of participants is maintained in a teiHeader. + + + + + + + M + /wiki/User:M + + mike@mydomain.com + CH + + + + + P + /wiki/User:P + + pat@super.net + ES + + + + PKP + /wiki/User:Pi + + + + + +

+ + +

Those haven't happened. If they do, we can revisit the concern.

+ + P + 01:35, 8 April 2014 (UTC) + + +
+ +

+

In the following version of the body portion of the same example, the list of + interactants is stored in a separate file (in this case the file userList.xml in the same directory). + +

+ + +

Those haven't happened. If they do, we can revisit the concern.

+ + P + 01:35, 8 April 2014 (UTC) + + +
+ Alternatively, a prefixDef may be used to declare a prefix which can be + used in the value of who to generate a complete URI, thus making the values of + who shorter, less error-prone, and easier to maintain. For example, the prefix + uL: could be used to map the value uL:06 to + file:/userList.xml#cmc_user_06. See for more + information on establishing prefix definitions.

+

This indirection — using a listPerson, particularly one in a separate file, to + store information about the users involved in a CMC interaction — is particularly useful + when there is both a need to keep such information locally, and to remove it (e.g., to + anonymize the data) when the data are published or shared with other + researchers.

+
+
+ Timeline +

From most CMC environments, user posts come provided with a timestamp marking the time + (often down to the the second) when the post arrived and was registered at the CMC server. + In the display of chat interactions, for instance, the time is automatically added by the + system and usually precedes or follows the actual content of the post. In Wikipedia talk, a + timestamp is automatically added when the user inserts his or her signature. A timestamp in + the text body may be transcribed using a date or time element, in which + case the when attribute may be used to record a normalized version of the date, + time, or date and time if this information is available or reconstructible. + + + + das ist auf jedenfall krankheit + + + + +

Those haven't happened. If they do, we can revisit the concern.

+ + P + 01:35, 8 April 2014 (UTC) + + + + Alternatively the timestamp may be recorded using the + when attribute of post. In this case, if + the details of how the timestamp appeared in the original are + considered unimportant, the actual transcription may be omitted. + + +

Those haven't happened. If they do, we can revisit the concern.

+ + P + + + +

+

Instead of transcribing timestamps or recording the timestamp + directly on an attribute of post, all timestamps of a + set of posts can be collected in when elements in a + timeline element in the teiHeader, most + suitably in the interaction element (itself in the + textDesc in the profileDesc). In which case, + similar to the encoding of transcripts of spoken utterances (for + which see ), each individual post can be + linked to its timestamp via the synch attribute as in + the following alternative encoding of the Wikipedia talk example + above. + + + + + + M + /wiki/User:M + + + + P + /wiki/User:P + + + PKP + /wiki/User:Pi + + + + + + + + + + + + + + + + + + + + Note that the synch attribute is provided by the module described in + chapter .

+

Removing timestamps from the text body can help meet + requirements of text anonymisation. For instance, if the particDesc and the + timeline are stored in a separate file, the rest of the corpus can be distributed + without this separate file. Thus the recipient of the corpus may know in what order posts + were made (if the values of the synch are sequential), and will be able to + group posts made by the same user, but will not have exact timestamps or actual user names, + thus providing a significant degree of anonymisation. + + +

Those haven't happened. If they do, we can revisit the concern.

+ + [_DELETED-SIGNATURE_] + [_DELETED-TIMESTAMP_] + + + + As demonstrated above, the synch attribute can be + used on date or time (or indeed any other + element) rather than on the post itself.

+
+
+
+ Recommendations for Encoding CMC Microstructure +
+ Emojis and Emoticons +

Emojis are iconic or symbolic, invariant graphic units which the users of social media + applications such as WhatsApp, Instagram, and X (Twitter) can select from a menu or + emoji keyboard and embed into their written posts. Examples are + 😁, 😷, 🌈, 😱, and 🙈. An emoji is encoded by one or + more Unicode characters which are intended to be mapped directly to a pictorial symbol.

+

Emoticons predate emojis and are created as combinations of ASCII punctuation and other + characters using the keyboard. Examples are :-), ;-), + :-(, :-x, \O/, and Oo. They first + occurred on a Usenet newsgroup (Fahlman, 2021) and then + became frequent in chat communications during the mid-1980s. An emoticon typically consists + of several Unicode characters (from the ASCII subset) in a row, each of which has an + intended use other than as part of an emoticon.

+

Both emoticons and emojis may be simply transcribed as a sequence of characters. As with + any other characters, they may be entered as numeric character entities if this is more + convenient. (E.g., ❤; might be transcribed as + &#x2764; in any XML document, including a TEI document; see .)

+

When the text of a post is being tokenized, e.g. for linguistic analysis, it may be useful + to encode the emoticon or emoji as a separate token. In such cases elements such as + w or c may be used for tokenization, and the pos attribute + may be used to indicate that the encoded string is an emoji or an emoticon. (See .)

+

For example, the source post da bin ich nicht so empfindlich ;) (English:. I am not + so touchy with that ;)) ends with an emoticon, and might be encoded as follows: + + da + bin + ich + nicht + so + empfindlich + ;) + +

+

Similarly, the source post Klar 😁 (Sure 😁 in English) might + be encoded as follows: + + Klar + 😁 + +

+

The values of pos in the above examples are from the STTS_IBK Tagset for German + (see ), which includes tags for CMC-specific elements + such as EMOASC for an ASCII-based emoticon and EMOIMG for an + icon-based emoji.

+

Alternatively, e.g. when w is not regularly used to encode tokens in the TEI + document, c may be used to mark an emoji. For example, the source post Da kostet + ein Haarschnitt 50 € 😱 (from the corpus , in + English A haircut there costs 50 € 😱) might be encoded as follows: + Da kostet ein Haarschnitt 50 € 😱 + +

+

Sometimes, e.g. when the source of the TEI document was a web page in HTML, the emojis may + occur only as an icon graphic in the source. In such a case, they may be encoded using + figure. The corresponding Unicode character can then be recorded in the + desc element by the encoder if desired.

+

For example, the source text: ... ich überlege noch 🙈 (English: ... I'm + still thinking 🙈) might be encoded as follows: + ... ich überlege noch

+ + see no evil monkey + U+1F648 +
+ +

+
+
+ Posts with Graphics +

A post in a CMC interaction may contain a graphic in addition to some text or even contain + only a graphic (without any text). As explained in , the + modality of such a post should be considered as written. To encode the graphic + information, the TEI element figure may be used in the appropriate place. + +

+ screenshot of the google search for hairdresser "Pasha's Haare'm" with the + average google rating (4,5 of 5 stars), the address, the phone number, and the + opening hours. +
+ + The preceding example represents an encoding of a private chat post that contained + only a screenshot of a google search result for a hairdresser. A link to the graphic file + itself is not included because this is a text-only corpus that did not include images.

+

+ + + Bro Tri-Engel...so hab ich mir das + vorgestellt!!! @AndreLo79 #bcrn18 #wikidach @Heiko komm' mal Twitter! #Engel

+ +
+ + The preceding example represents an encoding of a tweet that contains some text + (including hashtags and mentions) and a graphic. The graphic element retains the + URL of the graphic on the web just as in the source.

+
+
+ Circulation +

The following recommendations on how to encode features of the circulation of posts, such + as IDs, re-posts (retweets), hashtags, and mentions use twitter posts (tweets) as an + example; this phenomenon is not in any way unique to X (Twitter), however.

+

+ + + Ich mich auch? #dynamicduo + #wirkümmernunsauchumIhrenEmpfang + #bcrn18 + #wikidach + + + Immer wieder gerne. Kann ich mich schon für + nächstes Jahr als Empfangs- #Engel für das nächste + BarCamp bewerben 🤪 + #bcrn18 + + + + + + + + + In the preceding example, we first encode the type of post (in this case, a tweet) + in the type attribute, and if it is a specific subtype of tweet, that will be + encoded in a subtype attribute of the post element accordingly.

+

Second, the original tweet-ID as supplied by X (Twitter) is contained in the value of the + global attribute xml:id.

+

Third, a retweet and its corresponding retweeted tweet are encoded as two separate posts + each with its own set of attributes. The post representing the retweet itself does not + contain or duplicate the content of the retweeted tweet. Instead it refers to the ID of the + retweeted tweet via a ptr in the post content. All original + content of the retweet goes in the content of the post element as well.

+

Fourth, hashtags occur in the body of tweets and are links like any other hyperlink and + should be encoded using the element ref. The type attribute of the ref + should contain the value hashtag, the target attribute should contain + the URL of the hashtag, and the content of refshould be the string of the hashtag + itself.

+

Note that in the above example CoMeRe style (cf. ) encoding is used to represent the number of favorites. It would + also be reasonable to use a TEI measure element instead of the fs.

+
+
+ Linguistic Annotation +

For encoding linguistic analyses of CMC text, we may use the dedicated elements and + attributes from the analysis module, which is described in . For example, + the tokenisation (segmentation into word-like units) of a CMC text should be encoded using + the w element.

+

Let us take, for example a posting that contains the content 00:22 Bin + soooooo im stress gewesen ich Armer lol (in English: I was soooooo stressed out + poor me lol). This may be encoded as follows. + + + + Bin + soooooo + im + stress + gewesen + ich + Armer + lol + + +

+

In many CMC genres, especially in private chat, sloppy and creative writing abound + including irregular spellings imitating spoken language, omitted word boundaries, and + spurious boundaries leading to tokens separated in parts. For encoding these writing + phenomena typical of CMC, the TEI attributes norm and join may be + used.

+

For example, the normalized spelling of an irregularly spelled word may be recorded using + the norm attribute (from att.linguistic): + + + + + Bin + soooooo + im + stress + gewesen + ich + Armer + lol + + +

+

When the boundaries between w elements are generally thought of as denoting word + boundaries, we can keep track of boundaries not present in the source by using the + join attribute, also from att.linguistic. For + example, for an original post that has nothing more than the token Inmyoffice, the + following encoding demonstrates an interpretation that the single token represents the three + words In my office: + + + In + my + office + + +

+

Alternatively, and especially when the normalization information pertains to more than one + token, we can apply the notation using the elements reg and orig, related + by a choice element as described in . + + + + hastes + + + hast + du + es + + + + +

+

Other analysis attributes like lemma and pos (for part of speech) may + be used as with traditional text. It is a matter of the tagset used to cater for POS + categories that are appropriate for CMC. In the example below, for instance, the tag + AKW stands for Aktionswort (action word, see ). + + + + + Bin + soooooo + im + stress + gewesen + ich + Armer + lol + + +

+
+
+ Named Entities and Anonymisation +

Named entities (NEs) may be marked up using name or the elements encoding different + subcategories of names as described in such as surname or + geogName, or rs for a general referencing string. In the following chat + example (adapted from ), nicknames are linked to a person + entry as shown in section via the ref attribute. + + + + Konstanze + + versucht + + nasenloch + + den + wunsch + zu + erfüllen + + + +

+

In the the following version of the same chat snippet, the text strings with the nicknames + have been replaced by category label strings for the purpose of anonymisation. + + + + + [_FEMALE-PARTICIPANT-A04_] + + versucht + + + + [_PARTICIPANT-A04_] + + den + wunsch + zu + erfüllen + + + +

+

In the preceding example, pairs of a gap and a supplied element encode + the fact that some substring has been removed and replaced with another string for + anonymisation purposes. Note that in this example, the name and the w + elements and their attributes also provide some categorical information about what has been + removed. Using gap and supplied to record the anonymisation is especially + recommendable when the original name or referencing string has been + pseudonymised, i.e. replaced by a different referencing string of the + same ontological category (such as replacing the female name + Konstanze by the female name Kornelia.). In + that case, the markup would be the only place where it can be seen that a pseudonymisation + has been carried out, as in the following version of the example.

+

+ + + + + + Kornelia + + + versucht + + + +

+
+
+
+ The TEI CMC Module +

The module described in this chapter makes available the following components: + Computer-mediated communication + TEI-CMC + The selection and combination of modules to form a TEI schema is described in + .

+ + + + + +
+
diff --git a/P5/Source/Guidelines/en/Images/cmcunits-taxonomy.png b/P5/Source/Guidelines/en/Images/cmcunits-taxonomy.png new file mode 100644 index 0000000000000000000000000000000000000000..08d72e7ad8a38e43892cdf2a257a8585f8da6965 GIT binary patch literal 24066 zcmd@4Wl&{JumA|sxVtqjja?iXcWK<+-5PgycWK<+;o=u}cN%vZcXwaD_jV^@cjwpq zo0t>lRAgmkWo2e%W!Z^PkP}CO$Abq014ELO5LE&LgIodw`*sHl@s;YaAas8fz&K0F z{(?Dx`vy%6aoq0Q`GtbBm(X+q14DNH@B3!;qhaw23281QD+C5s7l-g>2n7ZP0j40M z^6T^S)6voKs}unN;pF7x_4QR&R+fc@<^KM@rKN?Hl~q7MV19mHK|vuXDCqI=QBY9O z&(9AU8hUhel!%CEXJ@Chv~+WG6AcY*Vq!vETwGUIx3jaeprC-7nmRi>o1UJ&rly9Q zn|p9@(8I%{zrSBaMa9U-XlrXrQ&TfEG*m`L#>>m=&!0a_OG~M#sWUS(Ha0fl;o(V1 zNevARIXO8|QBmgR=F!p7)6>%$8X5)$2A7wY-QC?`VPO&y5~!%COiWA`78YY;W4XDx zoSdA^&CTxa?!&{wxVX57hleC2B=+|9adC05u&@UQ2NV<(goK3G*Vp^|`*U-1qN1W& zT3R3wXl-rH$;qj$t*y7WcVuM5(9p1?q@<&xAP@rsqq@3!dwbi=%*?T7 z9n8K5!L@Jy>Pa?pjwO2H{`pNIYc6}_;Pvg}6|rsf;x1xVC<-K6AkeZ=_S=GExGYc!96n%Pso=B>wW*5+lKkGoRPz*&K-foY4h@x=&l``>eWBJd!i{bL9PFmj_zeL zW>W|DCw8v4&L0o1o;33pv2xITm17msbr=e_Hf zUk>p9%tu8DF#4rA&{;`N`D-lv-{%2)Gb=s>1JfLr6cti&Up?;}kK7x%`FGCw19Mef z!t(FFFBFJCj4=s7AQUS4LJRq?Uz zruYpdYdT2B`qm&tWLn^ECG4tE5qTA~a3R$+h{bBZPP56aYx$N&Qx3IAuiHxdOlk^t zp^n6*YQzUPJ?AF>;BIzi8g~}O?17tUKk^jJs2SG3-)xi z8sVt~u`6J5dspnF-6KtOpCiWl>HBDB?a+{~67CjI=kWQ@Qp=M-MB-+r^&{8E@6DM|KZVy{N=jRh zcK9>sn(^=k=?_RBYxK$ZevJGmgj_EVwLfj!%NUK(jXL6Tbrz|vHr#o=!s(@!OBRzbx z1bH5tsJdqFhT1SDn~%=6zlnXMAMPIF%;M}NOAH9NGGpHYJO%^1k9`Ktqg&Z2ZOzB* zF`J>Y9HwF-*3yMbm>qcff3I&ECi)gB57Wi1UHr1mnN2FT?th5p^NS`-U@Z=dTxZcd zAC6u2$T(h`3t@a~OucN7MG=U)J)V;W>`%|$t)=6OzR>bLO6vVfBox@Aw)J}63hJ;P zufWlpx1|h=lH8zv1rmDnM%aQ|KccD;3KA z865RY=D`$9ZWuE+LKyge$UQx9B)E;>@_1Dh=Pv$jCp#e;c#=6?3?-bFA6H>$E{A+@ zxIL%I5(&lC%;F$&2KV?au-Gn_Z6BRI*>T{2VZK%pp|x08e7-hO@9>=^pHnGwRjPRx zJzC$b-y&|MAC>1g5GS6!7AQ544xhJeDM>4%+oE z-z90v*?NQpoQ_wZsk6Bze}Zbr*~KW&C4pVkjS^NT2P8PObQ6m?UwDyj9$oD%e8gt6I@?8=I!J>N*&BQeXW zZGBx$!$i>X(JNEOrUq=Y53NXGm9plbRY#J%bg32#r^hQ5a@*K4F2T&?k)@LD4)Yxl zvsimOQnwy{udR1ISGF7HbHX~q&Opt|=}f-arQHBL{WUB-zV*b?PAdCGBiCb(jz^X0 zH*dt;@Yb}xA3LHqI8{K%y3ImbgC&PKf^eOLXcb~JLpVT*@SH}Wz1&VZ1mk&y2~Gba zULJCyuGVzjDcFCm&nC%7fvhtk-#o46oc|bU-D`{XS4m)teFxfm)MUyiAYnGJyg;3R zF6jiL0>z7^1SEsSaCetbGSNSGH68kssF#K(5QDx%MS!CB)s%o2R?Ak!|AdKuYLZ(n zo0q5DkDX#RGfmVw-bQ8?aW>E4qb>f#bj?AZuh=>^ps11|r7tOeJ9UBoX z>q8!%@!(=tUoTOeTVjM!1CPdQLTFe9C5V5>EzaOf24juSplx|(*#%&xyT3@Z(HVg> zBq2-@ed+9Ils`K%?1Ds&-$vi_^F{5`2!nr5!^*dkkWF_Dy1**d2DsdjPuR+^5}R){ z*LrOrMn4DAE?s3&uwH=tDJUzc8e_*YSQ2rrGcJ_-hv!lSv}jp4;L0_6$J*G?U69Fa zROwS3%lg5lxN=}=6S|CNX4&i+Y;$3?xH5!THyNupKuJKE2f@;^$u!jQJiFh9!P>7n z$he7Kn{3=p7x0Udi!Nl7Adbp39$}(ov{Ue!)U%f`i@LmQv~GR(Eld;79woKU^kIP}#To~Af6X1{VKt(b zJw7SI7gaqs^HNgY`1#DG^{ASywkA`QaBKDll-`SJr0ox4tEef+y89nbkGM+{Yqgv< zV)cm42>n^%b*gENkj7tHy{tq!i;~hc_G!RXl|(peCquMS0`q`zIA$E`YBk{M7QPqp9eoLiCZg2xYOtENot!>-w857R*1X|tmJ z-Y6!$1WLI@XY2H?GvXnjY8NN`xuq!EXdMwJbCE_hpWZ7Igr!?+IRFBythArUr zm8Y6zQ7O~*^ODwWKt`PZe>v5B5QIKo;#fEGHFDj7H`uCF|2fJxgQxSZ1C&-7Ftw zTql}F&4}v7RKn`pOPzs5_gN{wB=ALo0gx?^itCfZLrK*6VuZ=Ap}8BArnPR={-XV$ zr^w*q(p&q3pcOwJHE6M<3fj(pw$sq))JpEm_{B902|bh5dh4xdn$ak9IW$A+Ep2ms z`*?7%nWoZ9hw8RVY+mpl^c#tev<1AY(*y zau-izV4Yi3tq_gbmt<>RaAI^J zB2nv^fazUk1bZaJJC1@`!!u%&Q&nbgXEytMWDiVM1C6%+p%C7-aC(&-s9-z8M|v!S zG!H?#nUFc{96tZ$EVVEgkw)%y^f7c>BS77xH)Y`OfzV&!T=HT}AqNWcaAlR}{#@vnC3)Bjc^p0Z^1}H5v$`061*QkxG zRMt2vk1fSewRbZ@zZWm$4=&1KHjEO6VrhF_8c}|X_!~LdHQY8_`NLpn!!)G}rCZ_F zMa24yMo+7Tp=vWCK&PLN-ZO$W@dQhc2Nn=3Hag+Z*JSS)*e8U%oVA%JQ8Yq)wWr5E z2Cy5j805h}+rndDER!*^+yc1ZrVRe_5OA|W@#g4Q%T#~wO+O9EZk*JThWW80^rJsW z%wP&;M0ElE=S}z8+c?qSkmgSLZ^}Shqac1qw7nvbB@qZ3cQ?PQHlyVL`hrdRDDC1> z)tZo5(>jQwXfx+&5(|I%MCf#@Z9Xys0P1CvJD4U(3DC4(1DLrn{VlWV?+=-M{IXNyd8BmC@a1w-N05nC(8F8TSN>sNEQ z&%p|bp; z8l4h6O)6WHzZ;h~94YkgaN5G?>AIQGt&fV)w`b?hieKNH3=~KzJJ+e#*k_!zCV!t@ z;!%K}1;0jb`C#Y+D&>Csr@Qk?_CA9SRhmMfyY}9i+5&tIho(nBGoHQuF;`*~QauAr zO)}Of@4ll0A&-Rp2HkpN6&QE}-4ivLQvb|3!aJRbSiHeM+6nLA^U6{kfR!vAyR8@M zg2beWk-iEU{z6P8*C!rrX7M0&;SL7h=3B=y!Lc(WXnbj65QuTZg5t{HlULqU4ah3N zLhXDkF1J)o$kzjm|0k$H_%a^1%#iaDo2Yf?-JdRr&rWzGH0^%$gP6;$?mu{BpwZ1w zF+{Yr+ViU@*`mbG&lp@XkfFJUUKNPVnyKwCh+fTl&wm|~i$ug|qER9=+-8|{{2fL9 ziysoHO{MTE`(D(>(}(hY(J{lCWb^MfX|Fi3{wXVtuFsxTkfgrm%k};4DUX+wpY-=m zUr7PIxuo;rq7U*!Tg|xRIB^Sws!!vgkbl0%>hJ_0EpK_cb4S*8JyrAkjb=|XJ5IKDOk{Bt-ukV|lS&Q=A zjuBcQWta0nHbsuEv!LfW8G6=?qaW=sbx3`VgAZh%KA+`Ew?xfbH9u@zLZs5x&hi+P za+rC(rgig|kNwI<^ZG1m*LKX??MJ`Q6p!z35`*7j_rQZ?zJG>ApD}NIY?{M#jjip6 z8p3YjFtU%h})la^u+~Vtm5L z4|Rg}BhJHpDl0SFvZ8R-nBJlw#iOBU@R{+7tOqRO>(L5@#>Aqb{}%y~pmU*!?=Twa zK*WSEJ_KI+4Uy^l(?EPZ666s)PW1D71DA6`B;8YtNa+HW_u%)({cdY+I*(P&@qVVB zj3CgBW)=B7ff6VHR$-;bKcB%NKM83*EKF&8kC9_rZ=#rch;tMv)?B}zU76i=L2wF1 ziQVX@#7g*I5>s-qpd=gcvw_jW5nV1;4a^2Ai50N{ltO6{H>1*KRkF#DBpdg!&?;z- zyXf?iLO+R>(A`MV%3cteF(ugvni6R9x8aB->Spz-C1sIyXB~W@p%_%ukDq2O4qu$w zjHo)OMAXF5<@g6ZIV4tWO_{!O|0YxqC04Xpa!4ylEqG(vnB(i&OiVS!xKH_W<%^kU z)?A{QP1q(1NCT73c}wu>+bqH&dXxK#tg(tnGXp}(29fwMXhS4d;**=IPLx9k(-%-3 zw#F#Ub`o5?$45|8|M4fwdYX)vCEA5>xQGmN(yX1Gl)RX8$Fy^pl2e*&jzJfuN+F0w zo}mB2QJdr?R&o3&aWc#z>UWo!3W3Tvlk%n&2=;onYzJflaVxC@E0eXzFIEYl4MJyA zE*P@Xe6{rRph~jAW~@y^9S#*sOF_~&??c^ z@GxmDrx26(esdx6PLcR1UF^XsZYK-ZCV9WGQ}0X5`jn`B)}hptijr|v+$DX zjzY4dC1)g$Ay+!blKv-`AAHug02~(7!!?3LIO#JCd-lO(j#g#QEp(KGTjew$0A2AY zMPQs^sE?}nT5N?_(S@Q9^TnDg;w=2N?x-pLV1$B?V!!ntr1dsQ5)if9o94B4Q6B&& zC67P0#g6-%Q0M=cl+duStdfjpk7Vjqy#s$eo?QJVY!6W+mjA;9hU6Da%@BtwX~i^& z>6~m=#t=o9>FKZkVT~4352* z5sVUHczp%CJX<0y+U?xN*;%jM)ynsI&67ij~)0k;vW|fCnYx4mwWgI19-Nv;=!J;7bgcGXGtRHTdoJ3N(7spD}AxX@&4)25I@WyHqakGx6r z+fs4pIsPX-yh^+gwdj(Pf@J^}Ra!@9my!A3Lv`@D?15ncnUXjSqzIP#QeoTme`apA z$qCPr#-J%A5fbC8cjJm(y_Lr+hM2lnm6j^c;!iWheZQ=r-42-BpIp|+*S(Y|d{LSb zUI{m~S06hNIn6g#@$37YHuAI;RX=FRB@l7ZQHn;hrm#G<0)N%C#Gbb=IK~cEVAcn| z#ysjrgrWq>xz1qM<2G}iA;wSweOzfhK3G+ykNYQ8<199F>{KIKKN7$yfq+kjk4ytT zD$()vE+iKVf171+6_}`tteXvaf)Hg9u=zYVXtb>cdMK$cNcGvjIH|cC-&1NAVTg|{ zCYjt3*g9a57g-}|$Tx!>768N~R)7sGd8U%Ms9|~}rtRTYNn1bfRRnzm$6Qkk0qkw) z6YCM=rsOHe|Ap8gT5ZGYNjl^du_PIF6SI!1Z z|7HwwKBcU2z9;h~*B}2q@Z_wC3@SwbMkFbm;*PrDL5&}lewY=1?Gi0~f2q3?-uo|6 z4fD_cF#~9O86Cl)PPXm?BEBOG`+ZXar6gg8+?a9Ejnl(xU5|*EORlWi&t|eP)w7+C zA!MaBFfW~vnOcpV2)j+*>xj`+F-~%k4xJ>(j4i^RRs=P$_@1DymA8`Ml8?sMFU(SJ zw?jWd)ZsnM;B_<;eFayw$>b4s2hDZWcK*9cp{;kX8&3!PPQ7b4+fniL zsz$15Kj;O*Bk$E5ZJs;=5%WhJjH#Q#QiiHJ+aCEY@>z zy#R*zMb+cM3RqDDY$N4gGU=9xW)TYK$W521C^MiWAwOV2c)vm@M zaQE4|61X>T;C7M6Q}%)urtb=N#!y|#J9`J)9AelyJMd66*zPi!BvuG);DhU}Et$lE zX=N(oFimJ}9-n6FO%d!JBvsfKUq}J4*#MUDP-b<-A=&P+P&iin1dL~1Z55qzkyOVf ztrs-)yG6s*74$y{itLHFPCtvw@4AQZ{&U?D+BFR*W$pbO|F^X^s1Ho(y`X0Y{{wrC z!=;nOrq5~?zRRDepGpB@!LDodvBzWV)QSTH#}v@)IBCD&FQA@P^T82*_;pK-ZKU504CT4hCLI-c;sLt3(#se%r0t*@z>)pR_S{qWgx zJ;s4#wf2Y$7(pZ=<#5+`IH9M>`3YaOOK1*tnevxicZCu^d(_Kz&h5TIp+VXPok5j@J}Qa_mzYWh-JkzTu7m3S9#Unse{G=J@@qs#8r9{7RP z>HTkA|K(WD+=SB{1U~az@8sy#2y_wPyE|`3(V6w0Yiqb!t~^ zEyXi;cdlldStvtgh+N?_T3`HWdc0-@ua!cxMrr!G5tjrv!}gQz&lkCK`IF#O;3;nTaFK?K4lYQoKT!B&Zx6s1}v?q1v;JmEVNVoM1zrO26k&NRK z>-5Xq_xC@-ZL{6=fyc< z5yueN3nB1I(mP958C{Pr$S0%VMAZlmsL#GhF+yJ}2Nl+5!X)0!Ik;q`t|0^n8gswD z;g$MQ1FQ8LX1;E}{XF`j6-?B^e6-`}d8$qa$%AT~BpAmk!vmDR5OcE3k zvM<~t(h|wg_|E=EV_M*K4Mi+AOz)YTeJ9!u3NHmd@XCf#Riy7xadOcJ2tyL&zpp-KsZK9wGt zsedw#dTbbl}^{NEO)lNW;QDP&j_?5-gCqzX7U&iy^IAP3fT4-ZnT2 zr6HIH$h(uT~z54C%^OP`QD;?<%>mPrC6YZwH>)@EXWPXP}F-3Ryc>ho`zgD;H9-akmJ%5G10(lBibQE)#%jE;ilOyBL8gGxY@l zd8?%5U1Kc#=YgUX=*ni&t8~bj?oa?+5q>~**8Go|CIvl{e9IwKUE{qbG$e&CH8uEn zu8J2ZcBBc_0vDv{EZ1@C^K~IP_%^W*y#K=xe~BGTs=dwmTz-a!?1m{Wl9BL6;lYF( zYTWL%c)IT2HG*RbS)A=T=A;K#vJ0UN{OaMWZ2$4&R?N9*FJ}Rb(_}LopKCW~;hz>! zQ!~bS%R$Zps=eRIGKN!rfR|bj;V;)_)bRZV%Zo1(r;1Yw2GWfN-)gjld-T%fQ3W-N zeMseQ0z*WHpU$dPI77u zDx+!6Y4@OZrZ&XGsKQGP<_m>zoHN<_04QnO^r)@JR;(&CL!z0M$*Q`=Wx7O z{`$wK3XN2ev4uqRKZhHDoL807&}nP`CGDibMbqch9FCxxsrmiY_^G%|v;E>^F3{Pq)xrq>`D zJ`eyNGY`L>2?I%4Xlu_;S%)mL+q*&{q$+{^z?iEIb>V#1E~!?}PgEtv9WZPTorWI< zy;7VLDeObB`=9yP7}U@VR0N`Q`fv$cpm}f@U#%DFlMG--vgA+jQ7F{1H!E%7sDys< zB|5M0L51rZRB5-~I#KFtoNHWSqQe9c#Zf;knOaVhhfwB$IVJ4X)MLuT*jVqXV1ge~ zkq)Gc--8XFzGGMaM#SNUoI@+8KrxIEu|1xKHFsf9A|jK5bJgsKES4*) zOgeL}P59`>EW@N?=q@9I+X5#hbJT6Pt!?cR(mU)`%G-CBAt7^T7ejU-4eSD-3WcYu z2rq{`1-vg@7U+*0R%{H+8j7Bf0fB0E@P`ojCiTv`#_vrD?s=&&|J-M4lcR;W}Ap@g!d} zmO0H`T>x<`vC#+|y_3=rhAy&+>&D#lq5jp6dfstCT5?JL$k6J?@@Bm-p@i8hh>6Dx zhhd0JTq9b>h|dm;2rOi1QAS%OUf)}sR;?Vc{8cwkF5NaH^7a!gRHF?ccKcEU`B7Ozv>VK{5c3l$vY z#8(&y2(q5)r>^|AOSY3!fz-!+@o!?mv%eniM`}53LrjI=tQ%&Su9?F{KT4%@WwBL} zGtvTN*&&bG$CO-oCuAkUIP(N>$^;UrSjpsMxN6gjz@P(TNwrEt@xoJTX{N(LH}~?0 z_MatH_o`wl(*Yb2Ybd^?bvgH1l^&nMWaf(D_CS@z>4a||rBzfKkj($khV+-L-)6}- z`m|(RGj;K0&9Tu{q5E>K&PPuF{II(UJYvE#H?X!6ypk3m#ZH?fDQA}!g{>*7Ap||E z)!JClj7J#-7Bf#3P}PU8>Ws>E%%*DY-_hYNPpTGEgIcjAqDNQmIJH&J&aLOAgM@H8 z^GT@DSvOd>@7}V+~zhg88^QWR}o7Jk&1vkRudq94iv>r2pNk zTeNW&2_SISUH`BG(Cgb&`f5}-rJ$(qiV^8t(~(kfXEu$6UDxXz6l>FCoh7*FWML3zvDfxZf1MN7d;7BDvkaSsXIbueF~L&o;4~j|Ge~u%Um& zLGt>pelFv1np*EF07zsP?Lw`H`<0xjfpvBU|{R0B|BjzpCI6w8aqIF~wn zq2>{STOyatW30WKozziXmgTnQh~V*jM6*b7DW|`97DVFOm%D!PgntWIODV&F&BrZd ziLMX~|ES}(|^ zGcuz};37I#Bls&i(6pzDG2)v82{a{p@o0F3Aof(*SD^x9{Jv3G3D-V5mK07zx(D_> z7a43I$=4hHm!>+}(9Be%PGgYnFt4smCfm3Ji1lms`;k^3y#~L_py9`#c&{6u5q`FQ622PNvD+`8hBAP2XLUUHl z{#HA?)y-NtR3TSYU*%%?B(`!k8B4N@UNtUKT5)Q3)16UmEKXR%3|r|8o0;}{o0qN= z=eWAqV6yq`pb8b3i!A-Qz(%ZH5*k#gY z8FwG=rFeD131hNMVM8GCR4a3In#+M40^HoOR{L2)4{M=Tqjt!OE;f3}EL(HX zsj0A)>meYG$9au%w#oKSPDiEUe2`6NcS^9N^Wm0Pvn{=eP~8 z+H*eM0J{_Z#mHOtbX+lgsBwi);33B|BCgtsFNN$KZgm$%;p$bB(?mx%>h-*U8}u80 z2zEo3@!Er`!htofH^)`{nfia$rn0bCpLLu$Z?RF-n2Bx~RtW4*x$dg(okPNFsC&c2 zPB;C^y2f7x?ID6$Lv6#Gc+#|yW77=tvzS>?*5{E%+ACwc~2?j%{#_)zRVPK0+M4lDS z9LoNoQOT>upX!_zVZ-lM0xOxmdsNU->q{WL#j;HXu5{Rl;TfR<3Jm(y0ARVN)Z{15 zb{bt8T%O;c^A}Zj)c9F_Q@!QCd+AUFmt$obEJQdS-HQ2!YXCCpt(HqwPPDpiAVd;z zhUL2XlA3-wMbe+(?W##fK&R^}Qy_d#X|zhIw?Z{t-z$CXbx0db2IhB{1TLs0#|IZsA*S{|{&q(T`n90DEZtWB4amV&k@YtvigSux=q=ANE&Y(XWO@uc z+0SdrmDz1QK~}Z?D^kaJ?gR-j(+jIJ6;*XP9mpEZ5VIs#pO@8!&wCIh|cD%R{d0x9QA7a|ce9c$az z#9>;Jv;tSj<9z%w1}2&};Y^PtSPK zhKmwdhTSOYr&@dW&5dm;zqvVIEThz(DCzz@*S;YpgmvoI5|2mz;$%Llcec?$ zCo*;*fux6^4P(Iau8wbQhW!)P1z`#?;wwDEcJ;is1%@a3D$NnF$oAd4sI3mG&CJ-# zq0dy!{2I%y(2D&|X2$`H{v}?-@wi9mtxkqqT8aC5WLtYPnmjvFE!t&Ba<9P{e1zT47qiE4wOL15v?AgL7Jp|~oLX*WO8!o@ z_1zq-glTsn|M+w|+Cf00=8NdeZ#i=0JO0~2^y%G%Mo~ZI*mr~>6;G_=7Fi;d!@ud@ zdH7gkU*Oynk&C(GLKU)yC(`P)>x(jWBl5UWjOfay3Q51nzE|8@z%F=9Af6mLOi#EY z_ftGuxfw1EWjke@@G=Ox5OuN|Cn#l$o15{1OovuJ;gZ50VXselzby8I3>>(D*jcfgYt_|-mw28hOdNH%2hyZX|9f~^Sb=d&6Qk!3qT8^GV) z$NXbB;T?K6=!|q;FH`<%V~AdF@=KExQ5g&w!0buDBc_4nYey!xFH)LA_HYYDg0F|P z!2Sc5&mXBfdY=G4l;1Bs%hS%ZO%|!XlT#o5v>eBFGfky;mv>OUokj7)eEtvHL_F&y zR;;d`U#G4Z(ABq33H6;nC3z?pXx=%LKfAid3bj){nk4o8#&ta&7*jrymPW=oj*Z9o zXP4qsHs5M#j`3ETG>^3YQ~5R5Av;V7sT{CXG$bia@!1(T)j^l@pTyN9+hyCw9N+is!`eJ6rOVAG-NcuW?h22xmO5*u zUG6xC#L=u%-kIIhmxo?QU5wYe*I{JL}}P&smnl(YW4;Z+c(+rz;lk8<7QH$>b}opUq0`pbL*QCoCRnY ztf(1@rK`X4$I?XM9iRA#-J&ngk9vS=L?yQM(Y~jThD*OYOh80S~9xJ@Bxc*vWGg&6z<-vE7W3@8kL~& z!~0>mrfospL)t}-)+8_Q{zIA7UqDOgBaJmv-3 z2J?b{PLC%EPALyy_E=%~BGu9D~OKMX_!1?C&Kt1eS#A zk_!E9vkdx8!sp!!`qkcK*9;rsa~C@0U6+EZtc5u>R^lpKeAP?l@v4YwA4y^+*%KXW z@Y3CJZhplHGGgW&JlkIz`)MAR9WI-fqoqH<13J z{+tbb4Dd5S|Md#irFGWqyzb=m`1{@I_Ukq|U-(bHBAAELj*IJ8WI&4koU<4D1A}aL z@k|xeqo3^D7C*6ZMdnoKdH9t*0+?OzSQ(QSwF{iYdJt( z>q4Mc7-PnpzOD9+pn10E;8c#3%EQClo6YWSmSxb*B53K6Ed9H_F3)v5=VB#{p zuZ$zL$VURjpS;Yiw-t0z^JU`Cw5DS~$>L{JJ1>_e-on_RRfC+Tq>|}j!^`XW3)Rq< z>-u4DP9M(@?b>7;6t22@D}!Yc1+0*`)PCs-F$Z`;?@J{6fu|9aH^fzlbMRwYS9fr> z5$E%JzsM?w?$p+T*``PR6Yil#U}w(wwvrFKkAfQ0#>cWSYwBW?h$4S{r1MkTO8)PV zsQtMu72ZZ5(#%&E#7t13%y1&A?a`)H@U2#g&#)1^>N=CY#FuU+0fkPFwy`o{+{}6S z$jYo(hB229&k0pLQoD-Ftd#ckq=`0(GPa3(4_{$k!+R$`ds_a`_F^Cy3sM~~tJ!!S zSBp+0g*mrO!G-N2s}@=Pw+~}R`^?}5|AIPi80)_P+7HCCyx8CDdx!wQ95Q2G zErexf*UCk8HFj>{wS_wv(;4?gCD)g$`VaKvYE7AtOWtTcZi^9rKN?9TagVdTU zV7Pfzqi!OOM5RR`z8ZHmV6S!_Zo$U1{ouE{eX-pVN|qMMfaVAg&8cA47A)DO66-~t znVpoN86R_hpvA&y1mO=^gH`gJe@vX9-%QPuRlaY9_W#-pHc$i4WaraULlPdoEthnP_)<6})_FSXs{WhP5;oN>i0P|&g#Bf{%H9WZ zqUzBOdWd?ffxa?_Y0Fw4`3#OnP$rx*NxK+bP|DZUz`st-Z|Tjg!mcrC92@Hmcmrdn z(`x9uLSK1`_cn8vDs-wJx9sF!EE|jz9;;$CGMY`;nqb2{|I^Vx=dmgjm%FRFOuwf0 zOAeW#2fp7T6KB2w2Qi`axNs|MeS(c%>``RIh}z*_G@4&Dh<$ogvE>(wRRH_yd2X|_oQ2NsNZM(bUt%B8jqp`^DQ|sUH7E6x0$o`)Iyys z@lbxbS$-?=mrTir!9T*7zf?jT-1rjt>&l|{%Tjkpt>%;AK}oAGkKp)z`U6I_ zh5NCg{m=0JqMhd`_ML^&4odW6zXYD)IpFW*Ab}%m=W&k$zoc3fx>&(2Gek)Gy$-*^ zR)DsbBO8!sh|v6Hn3hnI#|f}`=RK3n3=!8DPMB76XtG*;MkH;EF9ix9Tg{yee!Y91 zehI|nIBgbz2NKkr;Ti#MusNV!$FDbNLcDv9b`T1=o)gu*|0r?=nQqV4hM=1)UBEd` zW5-F)B|v<^V2;xl$haW;>A8eNU2PWrR`W+BWbKyWSknJ9C;4Buu{GUywz7feJOr+C z;V78smS1#x-W)OORcgSMu3CD&OWH5Go$Su;wdoLvMolAp9TVCi3S}?NlUQOugp9vg z=7EgWP9ayCw7KkJGj>Bf1b5Dk^)i?U`X#ypgc0OQ+W+ug`1^aM`y-65$US>;U+upc z8xoDGZlGKGRX;H(91ZZ!bUPjE0fAD7x4`wl%6C*0Ve)F*e>;vQHf%fP7b-Z{g-JX2=ShL z+YmK}JH#*4%r8*!(8Zk6k*h~5A4{1LuEzF zRS6&I>4<`2)LBqFGm<#_(o}w2fTjRAa}DM*0HH~+7a*hFn|F}gg*lukI0~G^O^+IV zlf>@QNnSc;oLX|kA16R=;NTfM*INJveEq78U#GNh-y?z}A0TZ04U5A}2!K$*;#gb_ zphIC-*!h>jS?<6fF8u72oCd#dq)Hcw^1$XNeHk4Bs&5GKB>M z+tt}#@*BIA^cW-EsDmiRO+d zkN;O2*BK7ixAl{#(Mt$|C?RSPy@cpwl#m#8w84;x9)!_*CwfV=gos{3FnVv%8AgvD zy^iiZ{`cPZxgYMA^E_wobM|U`ul-wVuX8Z$ND&Ix(Yu_KO19_uGi=cO&Z#Ww%Z8qk zW4YFCUuQyP8U^V{o)*Rk#)+wEa-c>^-#gfF8mPp)%UPgn;SGAwy5SOE=E8rzbBBsb zLQ~JqC8k^~L1rR{qAogZ2Nk9@JSgVo!e~Gy_taOoomdjb^k`5@$Awtz#sDKnIUdSY zz^tLOek78{VPJd7ijr{(FISr zRKnk$c-9M?>qwYuC^dQN?$!r4d)SgsqRRb3f-`u&gAqy+=}k@Ide$!&!*wN5nQgWg zNmf$bRz{!9BDAH;wOhHI6q4%*QPvF7VCV@#)jdqh$NkLxL+Ld*3jSQ`{>Abi7e+!Y zcPGa()UKCeR9DcJ0bc@crzu{sdEjd!#;v&Ns-?S}x$@ou{Jj*pWmltRvn(l|AJp*y zDf=)A8{zL~-n#3l>6ODLThwAy_)H)Kx|p#JS}~~?25ZYd#$iR#CY#1JMRa!h*SY&J zo$(s>Ht4umW6e4bzAiYpII#`ZcQI#y^2nC*6?+Sf*2E=46baST67r-tfS^Yjv zl@QV~D!k;7*M!;1S%tOMEW&tdjvz(mk{}578;N{a%ziK8H3@HwoNjh<4(_SD*FevB zL6%XV;rQWF<&=U1%6QW_|HiW+U&-cK_Mbm;V>AgI1Ca*}Py4&NOO9J(c|nABRdskO z!g;=cnqvkd`Urh!-EnrE!+-lwr*GF9r3EBi(nbQHF z=di3*^tDWGdV1+aou*q;0*IWA+wHF>rGqrBCvZi>dyy{2P{f z+eGO&HbHC{^og?%7x=sZXt=+>{rijE*e(lG;07>Cf0qV*DcnyRIL?v;@Q9hvxG_Cs zA33dTP6G6*DHeUP_PwSnS8RAm4FL64g?Ao~A39DxEAbYzs{wF_Cit=NX2&oUx!7Ic z7!1HHt@Plz$uBm#W(sX3)BvV##WxyMW#^*p)Ka0cBMbn5uCN_xgIFDl_2hUCfK}A+ zkN)t(gqkHj&ook80f;FDcad}?;wv|I-}9~^ieG>XGz^P|0VjXf!#Bm*m1FWlfHAnd zg-Fwx?`br=TqOk18xMGHM#=izD|(Sd=@v`h8;XGD&1tH|?+%awaIUP`h~C-F!}?&h z7SI3<5yDoRFS=xC87T-zEP&lgs=ft?kml*e4v6fbbUKj(`|i@9*fjSXVDKpPvH0eX zC4O92{$F{sl7Ixmr2AX9T38d>>U|5?=1ck7^ew|_o+uUI77~k7VX@O7Cedelq`wp@ z0W^tL6dBVqWV5CG1_%x_E{43ll(1X@7zhRgw(b}~IDQC9G8F-)hXNE#uJc6LFUd56 z9=MYSC%m10xpKr=TN-Zizb4NYmDAK`23jh|cIwP`HTtw+u1}E@VZNEFevE8=ow0Ym zKUwh1j$=oHHCxMhdp`a6ts%BH31trV9I#F0$+gp)#0Zfb*LEA^SA1qAfPflBwsIUC z*cV1x4DO=8-vfTXfTvwTK-O65DqH5EYary(!SX_+0#1z2nkN-;XY^gO?(^*p$WANR zc)`~{l)t{xVxt9lQFi}h>rbBWfMgt+FH~8?_v#BH&G^4r>#AK?palYCs@vp$)mYqe zHE~CmONHm=zB0_k9X;BSpQ!e^I({V-V~KiAV$3mbat33H;E<#VP`URY%aA%N2&U>Q zpA(ftxcXbmooFXQ#VdenstTdZE~!%GY7^ewUt%_~=D29S+D-3%S~5dy8L*Hje~i|q z4uT+AUb-yl-;IN81`uASNv9`}@BuR;DpV|QxPRWk8M*qguEby5y{ZGk24cgTLjY8N>)2Z!O@Mh&xaV$_04kmA6U0dBupY7?W#o;&7VfFtGR) zP1#-I0(c76Kp0h+jba3Yn(XV)*`|;mn?3)uzpzW8e;m&6+!jg^(({QqUi^3KcO1af zcPrq+MSSA0au+_T7nIPai#UYU66LNS|1AT&?h;70_PJC5D9_e>!lL~63&6rl z*KG>NNelfK(>WcO;MS_NDzciSU+qcQ6>tV7q$^3eYntxdIQ# zR2AS4BxQf@sxYy{s2TdqfbDU=yv&Ps&jfZepqI<>BQ!Bp$QHyy6cx>&&rlRUpMPM= z_^-};q0X8S~pLr)cyY9(PqoLt{efWk3zDOTyXbwf!6QHxfTPl zh;QO3wAlG&UNLVnGJjTsA439!_yF_8&KrkBSlG2jmxhHxa2vE%yBeUog@NrfTSY7? zy$K669e@3bK4v34h5+DtrV?UEJhRr5iBPrHQ{W#d(lpOV%(%4#a4HZwvPNqS{z_Q% z*%5xyh)lEUi$=$#4uGg`Kk_YxSySEZpQ^NjCNx1*xT2(kn{;P8P0RMCx6Zah_;$!!6XPWBf%=@r!fnHr!@0=5x zyG1DZgj5x~OTNVBkL~Q;ab;t)vsGKCM`)gXF69}3Q1|h6O>nz&B(1rabcih*xr_|% z3Xsu?>Nfg*5AJA2TFiDYs)K_dhaWjuqI)=3J%@H4EAntr9LpOk2vL^Qw{{IOIdQHb z#&-os?{V5!)dp|Vh)0HPr7fB|S@9&es_(8D8gfz5Cxx*mTo8?VoW;)Irkr50Tl}TW zMGz@;4pcB#|K*j-TiX3YUPdODCIrfAVy73fX2#$~YKc=@hDnfRpQ_ZH!8pDdZ6)rC zL{Y^sUj%xx5Pg&NO+Jz1wB&T_R$yi4=kDNUsWPnZRM;`d`m@-Yk-Uxm%k+fQL5x9a z)hPPH8dwF3{*cj3!lpF>87?R~JK$Rhsd(A0>>uoKMC6A@N9pHeE)1|4REhp->HQL*PVZFC%H?smRWoTMiH@A6KDaW^Zu12jhyCr;9+Ks9set|BT;c)gW-BH{47}gHRCvi4|CiC}-Un&u zk!XjO_}eVL0*LU6lG(dQB04K8LoSLr&!kbE)*OqygO$Crt8%>^q6g~L@czngs1+wd zLO9qAWwcG~o?_OyaGpQvzMW{OdnH0PLL5LXWYf?L>-uO82@1)Zd_w{YbUinpQ4ZWf zb3VUv80>K30L#|uMUhmEJ~vxh_O6}wKi=e4xpC)er@)@@Zd>Es5g^Nt3O`uy&;pMI zDAnf7Hji|wPil2VjJr?LSayJTu>X_k*{ncithrDg6;Sj7ehKViCU6(+WYo7_`M|4d-s ze6Zh2zpviXGgLeVcskQ}H&M7XxsGJ2B4|b8MDn5G<`pC1jZI_5zhefei30D9jKWPF z9>{7c4)H0*MlrS|Jz@UfgZ~;mv<4D4D2w9pW6d8@!udEQ(WG`9tb+yB$)x`Y=T}Gy z*p!HcR348II)<3%;rCc+fG;`{lwTifx6M;3lo8)0(v4!6$>AM9 z=B`|)0TqCYHIU0M{Ihr>txeFL#F+N%ML%pw!meM>A(;M~Q4QBG!0-e=t&$03T?v{a&gDNU zJDrg_i6#-@2(AkG6dlKS6bAjSx8CAL=H9Ny2zAeMVgaXGuil?C2(`W4j`~q0oH3ox zqWoNnb$Z_OzZf75G52`)+EgTIjLvl(A@2Xj09%oNj=!J zHcfG-r!!&*OTin*Q%)ZM>6mt2N#UFK0Bgnyw-&0vd%I2hth}aV`tc}CKNAR8@%qmb zFbD7QN_NKaa3j2owVooCKDY7kHat?l#*QLdz!Cs9b=6LL3+q>DN9-3G|jNr!hKb|FnN%#fA%rr{_Q*2m*2Q=>27n z04i3b2?3j@jQ^bFwzAon<%gE1C(-}`!5V*!lXs`II`6Fvx0oZ+8AU6vElTn47mhi1 zSH}Cf_KqT2%rkYzdT!qUfp&2z5Sq77$H6`NgGL%ZwJZHYvn&`=>G6t4WC~Ob$Nhh* zPvlDr1R4HAc02(DB#lE_5)TDWY~Bg#z3smfm^^9dL;046J?R~qWk{-7Ix z_vr5Y{CGe&0!!E;u>R*Hg28|~lZ-~8&n%px+Kbu&AcjRa0Qn7Q_djGQux=qqO8<2}f(8yJur&lFICBF!on&n4oRPwL{@1E~+424{_(xWxRML)x(b} zZZU~(&Sx~vo%D^WH*Pwb?8!VF9Yk{=hGlP{Nl9S6vN3gP1cQ}V64=!?fPLBaB5k`s zX5>yo%ZBKcTc-36lRqw**B5L}81*Z6p83KZa>T~Rjke4K0-Fr3@4agk-S0&Iph@x%0R{de1~pPYEISc0?H{J)Sup#sjD3FSzC7q8CwiqM_2YnAbhVm8+u%sU zIV1kg8`=V5bk%NC_?ziV$MiV+ylr&CH5&NQ35dIY^81et)AGTHN0(K}v(sTs;A(iP zA6IOLu49YI1(>EZPSbVh+Q1I=>;m59YTJJL}Mor=IpN9x%m~W`2ID~?pMIk5>p)zbu)$L0)Ro&Ar;mG7xye3NLUbE_bZ?bV5do9=#5LE`BEMCHGcP6zZ-*%t9%D?o?(9fMm&4Msi zpBv}tSjH3JpL{}`4^N*oHG-)&dN=8;P|{_2hT-Ry$$6QtCYn}uuKCou?1z}mFXEy! z(^wAPpoM7+s&Hi2=V+&P`7Vym6vJ1s>O8D}te{?fYP>8aY1(8qsHF*U<1(I)u;bpV zl^!KVbeKV>OXGX?J5SrJ4Xi_21n3fF;qT~YFuh`8>vSBiST{U8H>I@2Ja@j*$D1!O zW^fZ%^+7qq^;T!Yj3aNJoJl5kJxs!*p^non6^fd6CP*n2x;lIEwyCIeOO$8?*X0z0 zWj%~5-G4$ze_i<9nCut-7s#~l>vl$LKiA?TL-dauU(=BroFv;fwP426v*Se{%aF(A z0n-mp*52arR%Fn+&!T#Eo`6@Yb(85)H1*0epxh}5z z^M^W0|7=D}d5(uv*PK2j8FrkH+8Qpke%FDwYIc*^veQy~x|uQDYr-9Nd?_Zj!k?%# z^5W!ZB3H#y;H>4SyLM!0Z~wwPA0nPKukj(Lv^(m6nQ3JytMy=^J#JaO0#2c|e^$lI zJuU3sLm7Ir7O1$+xs5ig=7ac!9PIX&F#Lp2`aD=0h%7OWNu}vpfSNqXeYi(q`M}3J zT`BZe*JDM@{bzbRrIt${24e!=1n1JIqIL}nRdk>g#Y8h$3_a4Pj1*&oEJ;t@XE*7k zRj-*V_Je?wy0g<<)g#zU)*1>+>57ym#7;om2Ub8|5Uw%uY}ZLrR60IMetvR^aZH#S zYS9F`MlTsZ6cb?c>SDQ!*?RIq@li;UQiJZ8hy9ru$jc@UazdXYG z&RuilCy!do#Cfb0rn+C#y97FhJM0^(J~cj?s(tPK_25oh+_FhtfoEyV`4Yl7>b`XT zGhs7^nVrJM)r$v7wymyM227PPjpoFuL;Vf~bC^BlS$w7GOfoa}+;FxAQ6mFep^o3kmHTAc+YOV%5vi33}L@U}TKfFA@ocNY{ za3%Sn>?)#M<``d*9-SM^+PISiyQg#^`r+KqER)RECNBHoZ`Wk^d{2DJw+Fq>?e|c78N2`_5wV`lo%Al_B~4YAqPWFb!cw=nX|`Id2ySS`Nv3Bi-&!};ft z^L2e2_6#!!@(NE3@5w0oTRLBvSA6-rbT@`K{hIM#O3`@FpKUkHBr6Uty)5S?Iv88Z z;UB&}L{zqwTMtn(;A!Gpjto#qS!VCJ-2C)uF`uUo=NO1qPMH9kO%%{Gt98yj^j9K;Uu z%P+)CdCfnr7E7^D|Ghpsnxz0_vWCMd{KT4lo26)B$jtTA_nF>JJ5`QAc@(h#ne~D+ z_jQ^Ooq45Ydcb58l^Oiu2A{Atk0?ihX(4Zb6ZuUM#&v9IyrFE?r)zj?L^`>DKZ36L zG*wyha75wUHJdIrEEz`sI9PFLn^DfY+cmchlaqJT-Q`@!^{dEX4uvoFZw_AH_u>9f z4#$$e^llz|l9JZp93E8Lzu%JJbJ{4QYat~Cf^D*iol;78K+S2c}Hd73QG) z)fVD5Z}<HdOl{u*zxF?K8i6J&bCPU#4sDSCmG#smi2t9m4m4_r$JNRDQv8f>N-V zOxuFi%)(DPy%ukp_UB`JamJ<1(_2p&B7meW6Z`Uh)+?Jsa}&wMHY>CM7zhi^C8{^7 p5lrp(|NBU5q=XzOvWd8PoMCSAF+mWdbNef9RYeVj5;;@<{{xmlN>Km+ literal 0 HcmV?d00001 diff --git a/P5/Source/Guidelines/en/Images/cmcunits-taxonomy.pptx b/P5/Source/Guidelines/en/Images/cmcunits-taxonomy.pptx new file mode 100644 index 0000000000000000000000000000000000000000..7ceec830cb23a3c7f50a1210d0dddaedea720c7e GIT binary patch literal 39218 zcmeEtW0Wo3l5JI;vTdKTZJe@g+qP}jDciPf+qP}<)T{5_ey?%w7~Su0cju42GjrwI zd#o4{bIpjDDJ$^<7#RQ*02}}SfB;~70{yWP5CA|J8UO$Z031j|z{c9q$l6gy(aqM# zL5s%K$`U^h7>Fzf0OdHPGgI6~sR<9jKO8VruI3Yr5K^*|~Cx2&ET2@=#p3099EGfI%4|IUuy-5tl*= zQFYj`FE9@NH@WJZS$0-~y8;Z$uf_%h431(Ovc_9@d1HY>KK-I<$uaC;<6q1XysH4F zo$6LIs$yVsN}5M}Yn7ZQ^}lU$MSf&5UD7PsF1D^^%z+EqV=( z=wyZ&)CkKH6bUHqF*y&`vh;e>VAYJh0_30lW9Dyw{b?AlQVUgu8l4rfYD&f}`X{9+ zWtF<84MY{W#N`la(hB!P(2F9+SMis6RsC4AQ=HfyBls?74579-=@XfTcUOdC&Dw;` zJR)C5qnZ&S**$TBbget0dUiRX2c5peMy#5g4X=T;Hx+w&MLKmm=g&M06`1W0F{%9b zD+c=Bt0kS_Qm42L+iqe{=LCv^LnKvj8JNGXpJGdu9}&*FyAH^vU9`ELF<-d*FJjY5 zDKVpZ*t*2HkKpMKgWBKdr2Y~Fqi*nN!$J`&^BYWRL4D}u5 zI`&4E4zx6Xeg1EB{|^r7f3x(8xOMR#^zgygAln2JUaadBgmacQf+v|HZvX}i?O2=G zqD6CEow+-Dder`%6BE36+eB(MPu9rS33V{qy>(@LvCF-x+mx=>c&N?z4Ed~VpfZrK z33~II+7;QRf;0kdHS`huw`#pT*w+OU?)V|CkiR`o9SPVE>?J!ROSWrBTg%R|QoR{+ zQt1Yl$V4?9K=QZ+-|#dz^qEG;oJ1Q!OC?F0jL>HF&%#hra_}VB@sN}V0y5ClGgU%E zGCgihhcObXwI4A{zoblGU2I7PCKJBq?=iqX}E1Y40~P8C=ky`%}&7~KSp z9`f}fvxV*N7}Mdt&G3&gW1#u7q33&q^*e6xzrSs59cdjb%?ynkX#XBQf4iXnYlr+> zAVp4hn)lPegWYh?xWG57)NuyFQyGzi2o%Ti^bllP$!Q>Rv<}$dMbSHsxaxHCE^A$l zQ~e>UkKq%b#DYh*bmWP|^tRTyCWY6eW6LnWhry!PoLJ9opNlNSy*)sRC<9)iON^Tm zugx^&OQM%6i6=M$k)XaWL0r?p7V~17lsh!}F)@YQIUnn>?B8M)rd_*F=PHpsTLl$# zClk20%K0`#T~%0@B0_;#;CXeOq^|b!SE}^o7V|$}Jr)f!81(nbXMO+x-~oUG{q4k=3(<(A|({3--lmMA8u*2D(BbI_0;b2OW-4M$mnTv%41AGTj9gy zoVv&br3Fo(AP=H7Q?#_ov?WHNLJJfkR7L2BGr>Do?8SA1((?K^X|D1b+oSM>HZAdo zA(pYUbB?2*bU*IoNY)jBK8o5vl^5hGTYkQY;g{f!-~LuqUGxRJ%Qf{`8*ML}nL9(ncgG zW=iMO1Eazims`0sIdQL8TgWV@l9!8Zh(%zLr$>?9DIcd|tHU^*Eva8kf+Dh{?LDMz z$)dz(BUD>X;CU=4zjTz_q?GS&GilP1sdCFhEcE2q=^?Lp>~8_$I0H1MT=5~4P;_VF zR{by-u8@dvXO|La1|QNRJv9L-N_U6qaLs#kJ)9X&#$NvfcJ8qGn67}0Pmd=Dxll!ERhoLP6slG{FjMH6JECj)UMEq=P zt8q1>yoS3U=43%|%LJSs{t5axi~!6LcXa-(G6r18Y^hAvemePX(AH_<%8nCc7L~sj zLG98tm-DKa3fZ-<^!A>=kiAaUl~ToD$w-@iNqQo9{#ug518DXkx8EmsQP}CB*6$9A zZDZT~iouF$G%^kfkT^3(7R{d@h7A`Q_IjW{?-qHprtWgQzunqMrH-W!!b?wXtFnaOFY}i=8TT8H6$;$ zi+ehlTVOJ)tNr~l(;gcG&P|M#lDzF)^9S48%)_!0K@cLAms03j7jB1ehx}@2nb$Af zZj0A;TrB(3ZY$@l_u{ENyl>b1$Gw0;5P(PQJ451e0{}qz7w7$#z2IMWfeS4ShjkWI z@9or2IBf2RJ737;fb?}oFrpr7lQk=o_)Qn#JOgPWd5O8`PR`G3sMt75iD-S1Xo*#E zW2*20oEO-sS6kS}{%xA$`V+$H^gIfks1X-e)G}Oa(m3*I0vEP_NQt65Fmdc5* z<+Dm#k$;}{b-wQU_X<*_erC5@O4q66*EeZpL=I0LP-UA;x-1gXe%8;IWtmidsdr<^ zoL>acI`LpBL=L)Up&Xi~c6Z7AIeTbGIcQ4Dn7*&OgetvPTY5`kH5trPOKfV9F^k}^ z@ub(f(vW(aeYU)FXMxF{+>^>Y-Yx5RDb?=K{?K-b`Let9z(G;q)y^-OIPz8%-aia5 zs=Kmqo7IYBt?Sm%GA2zfe&q6e>k>+?7WTfW?%TF&N!DqaE$C)%?c!vAzl?5(XLJ!c zyDjs-jS?5AejBoK0aM;|+o$B6{QRh!tt0Pdx-64BcDglx=w>RUcOlPN&>`rd&sp&k zCN~J_#ADVjH%;T|@Lo_( zwCk)^IB2=VT5YqiN5tggj*`{&nBB#TcQ(t&ZBWeranwZp@^n#l}z2xXz`^wWe*(+`j5loHr!mEDXEDW3$3wULtjazkyCv0 zGG(XR0pYNg4gc(Aj7@z}ir{Fqn4>nT6;jrtMDdkLF4p~`s!RX3!+1i;(8+SiW!Q#; z2q+>3^#I`KR|-f29l{%=7TgfI=J_&%&+UfEhqcN!-vTE9>dx+mDF~lhsXb5JIOd3& zt9J_?%Q<0oPEOZF?E%KQo|~a5AubrSBh!4~oH$JRDu3c;^8*`xtBZ z`Rh|&YKwJqgQe1^sV+U-OjbJys4k-_EA%kl`^p;4RReRo<&)k|5~5e}u_#zq9HLgw zToyn&`TJaOuZj;3ZKOVL!Uf_$ZS}D}4P_obwVhUvn!$cA-R33CE>B1fo9$%z`^~jIWxpi`}oAX zYV3UCKCj}e9kK;C*yye6*{iz0p&I{*yy7==ehm!ET(g%iMTBh_v94@}uZm(#9a)lD zWQQ054jpM^4xGrk*UsQ`kcuM*C901O^$_t4S7;!7%@0$4Kq!dlUsx0~Jl2r0RvNz0 zi|9Rs&KdAg`a7U}6-41d24r%~+2#PZ zVi*(w#{mi)D-(qCpCwh|=@d9r_#u>74OAQ~T2KiLoWX|dFwwasQYlSus{4Exajp2O z9KP8!hSqdVn{zK$nW_WDy-v&=Zys<-nBkUqU2>08V<+T-uHslSgi=p37(5iZrs#$; zLvHxtQXr{M{wyQpuEX<^D;ggos=d)rdNs5>xmn%6Y`zrpg4rP@w3@^(dMevYWAiI@ zKvxhV+UrsfABKW&!OWt=h1CA1I9i}+#O;L`;EFvPWa}7^! z-J8v^B$};MVeFj8R}l#MwU8>-kBKk*rHtHH0@?$!ji0d!nVay89lwkMt6TB@E;r?^ zK&X)f=(?sPcnsXW^rMLgk*HGC>vDo1h*~JFPSIh|z+jUHbule>g{9O#>%){}QEJRz zY^da9p`UtMFIFDGnW+divSNh~YA$!qzZM_1m|g%nBwkkpCS1xg7C$L{L48804y{2s zVE|`FJrj|ahIXV@QSy0R7p^XgX2^QP0ZJUd|h4)ub5;GcRT` z;#&S+zT8q=YC7@Qqg2uy_44FzLBz1 z1v0AUvoWLcm0`>Ynin9;I87j42|dTxpoo*>$KhmBX8q8pElG2>nTxS{C#%h6K!nW@ zV_qf;D-A(l#vYX9Gz8F3gQv3c)TuXpi8-sImkyFS*6@zQQlm){5r>fVA*$kfxK@RNcuK27T8akNnTjgP$4+eSJCbLa{35}?|0_N zu4ZM!#LozC-Koa)Kztku0#iDI@IZ$W;LzxPU1W>2KCd6w&rVf`<;lsm z;fW_W_|_|0;Sjj|Hn8hg?qpc5ShbJs&F4YkwF9H((ALD9zpQNK7oD!6nix8U>D>3d zqwmykwXs$osA@f}OJLWxs|cAWSLD}VJ=@~I>Fc`_m<)vO5o;7zP_SnHka z0}7V8eu1O8-!9Q@+ur=k0%g^~oIx@e*BwmE=1<6MUdRZ0dC5+SH#WMC{lrND7*q+# zIDbjHK6zIorh#U%5Rh;f+58mo_!l$(!2(@=knBxw#sO{SO?MN<;$0<8TIz;FkY2is zNI^JWOgDm`3$4(|my6}q$z8xYyf-HogVd!WzmL}a!Yxbu!pF=gVT#CGJ zzqX+#OkN|Y74|U*NAMIr_p2B?`zdIpg8dvx>T~h!*Mn=tn_90JC*4ReB!6Xv1FVH% zYZL;2^GJa>A)h`Jja<*F7xn4;>pQSci%7&vJAxckoL(O5BQp*mL;DP|6u=9D`SifE ziAV-DH1m}54^?4e{NtW9Zp64f$5H~^wU0j>Ak zuwH{j3Oy23qbbdP64CWaSUTe9Wta^TJp|sgSgfBp!1x}@d`cTXRB=y{EoE-mMHR|uTSpHvG=DQ{Z z+4omXO6vxv?~_X1$M8zN@@GT1T+D zGX6-qZss-fM%C~lDzM1|>hO+Oe>(cprTwg?>40XmtL<+gIW7xy`)JO>6=)`carn_> zF|@hB)`U_Ogh?C^`SY^1k_W3_oQ#8`=Axt;0WDoWKMg{v9D-qcxk&C_MFRI`)i{2d zhzAWWC@kS0y7)9Hjw1q=SuI>_K7Ci5{xJjl|F;6`|61YOJ=p)7TY>t&6cO}v|IN+t zUjqiV|K?WsFFM1&tJ(jL#mE1(!e84b!+-OT_^$y2h}H z{Rj3arRU&iWdHBjDH(9YB^Z5b`%qxmHu`9`7)4Fu8v(GF&WB{u`mQX7b3G>Bd2^_$Cu=w zP3Msbcu2*_P7e4~(D!lAw5L-irR9QxE9HbC`;PT9<(xB!)}8?kPruM=21<1P{Bu=i zohcH)S)(bETtmK2N^&(g&ghlfjAvsI+kqrZGLFYZh^tQm|QmV{(np??bFR zUugS|^feB)G%<4}x|3$Fk5(c)4P$D8ow49)_11(MV@;bG7f! zW5KUntEg}n6q`3`stX7Dwdok|kKI*UHkL&w@2%=Y5SF&vSlWw3`TpGfZ%s~vC)Wws zY;U^}twz<3To!xc!F8|mI@^GgSMi~f$@Rk_&)cWHS~B7JxDzD@Gsf?{UC0kSl}Ea% zrC_fL82L!uAyc2rI1W5~bD5a&SUp&_^99Qy=XkfJ2@vJS4Hn+brW;296 z7FKuMiDX1RGD>(oo-p+M4`C7RA9FP&_7I?RCAg~-aWHH)SJbtptUF`=o>7UC6 z5;?|J@vq925J0`(oVns&a7fn{nDE(wN1egTQ1q~7t~dvy54I&uVmg@?mkQ{BnwPVE zsG9p6saC>H6;oJxxS*c~8FBa)J$Ict;Et`?MY6kl-nAT2@^}mOF8Jt1Uc)p*rFA zJeBI?kmW$=dt>JW5+R5)Al9R|^U1o#=q#Wh-?{?+zA;Vh#Q0d%_`?8OZ{tB|)l5ElcJe`J;W6gVybG!(Pqj^k8 zZ}kh&=k<#xilW;vln?G83cloKmE8Z@B~qhcuf2L^4rwAZ+1qr8&M0O_0>_x9}Bb+}n<>qK#I$nZKg z7C^!#vQxx|L?am>gOyF#1xA1iW`aehIWeloNN+>*J=x+ux*zV=9u1hr`}zY*Jp_G! zyq)2~xL!*tMwnfo=Z`o6d6JHRul9nw0ZeXShB!n%$?O3-VOq0x>1aF&1BtDxS;h3?J!>^56o6KcZ z-*XQ-sYZ6`JjegFMKnE|*W4kNRUjaKx28s_4aTw)AsQ9jpZeN`Az!UseJ-v+zm;so zIDhL`YEdz|o@Ys8@|Jy!apzQt)DEcm;#E6;s$H^M3czT5tCG;4=WB>Xx9eJBE*w_D?|nlE%*s{@TAING zJ}%TvY_fz*6_V>JM%iCu*MKTqaXHSQXSY!9zP+m8JT(8jJxj1KBDjolb~N~)D=S?# zE+iRZ9j7fO=hmEdqZS#7Xv#VT*cRr2A^$*pz^0<4*6^aBwL36>Fq?P=LXQF#%8i(?2f(n5^ECx3Pn&$?`d0GitLx zgE464dT@a0;wncYnce2ynFjW*3D=CF7RGnb5Lns$wU<$0yFL>ggoqv?tR}`kc7P0; zJ~}M37s(k95r9V~KfDipALmE5?@2qW)t|2AG*sWX7TA_eQ)u0>T8+pH#KMx55>`*e zc&j84)KI4dRIJufkVtV+xN_}`FsZ=>2~xZ<7}#Hmil{cdvT?9G;rY!CXmMEpV?92X z{&L>Ezh*{ug5e9n#!_lG7gBcq@SHpWzqPlc%CS}Z{s0p0RXH^u`O%BA7+ zBZ9rI*#EX@ufh>Z$~4-#XXM)}v!JHU#emTgX=~o1@rLGB{F!zdDb5B8bP-n=&!wis z`q&NThJWGJa(@X*5r}7Vvz*9ORESog=b_qw+mv!6&()XrSu^NTDA~J(I@*s~Py5Au zkC)=9i4a!`jzp2<Ztq{iE~)NV`C_#aC$lestC!(uKy1x`}RWQmmFK0aD}l`ymrSAj6Qax-MYi% z>E((FRflxPgP=H?dIqQ|_mi97*Mx{IJmHp+zp>!?friBb7JR(tCPDC2pP%FSHFlA1 zy^FSeLR@7cnmhuWHG0Vxsm{}GIej^48^;5^57LPOLF4(8ZzZ7sWDJmtov{rVAE<^s zy?b^|PF>ZuBU(A8vRYPG5T5erMq)GBW9_j#$V6=eslbBS9>AwA(v9a;jCuiPJ3S_r zWxlZQ1FEzCc=@B|2cMFfjkTvmU4-TJH0ty6BamP`O!f%q9dVF3Sn}_Uz!`8RUYydc z8o_}-8^|nc({D8vz7-D~iRPdrCjSU|Nl_he63zilvg}Np$sT>tt9a2^%d9|_GIz2G zPb`UFz*cOgV0bzueLL~_reFU^(7g9fIb^;8P4Zi|LGYgtw7+FR6RO`DBo^c@yc!pH zCS8|sq3{J6<>DC|R(z?5LJxp%35VVrmQcHN1dvxe_i*s$qtqJ_X93Z=+1%86S`RCU z5FV~K*Y0q14;UdCnvrI~L`5wDSh1G$k4NBZMy+;Ro48Ru4yPlWPB+NA7l zJ!3vM$!ovRhP>R<|CC2J%GHdnnpk}qHZ8(SZ@ik|N%iJ-T0J!;Fkj@ijGWv6hO}9@ zmW;ZMV!G3#+m1RKM|)m58h^k&Uv22Iw2^Bp2i(}a+%e;<79XV)0Fm5hyFLswB_3;i zWf`{>oR3t+c%af383>n0RK;-qK=x3J#Cgt4i`tmiw4I!j87yEq*wSmEahQF&= z;ubfO$BvB{5v}5XU3#ovaNsvDL??(Ks)D0iX9dgiqD zB+R>>TK`zyGF8VHzvZ}TYD6DVv}(piA(2qKowa^ZaB-IFO4i@zK9Ki&6=gFH26oE81)8u9^Wa-HFKV zZSi4b)hiUE(D<>qoxW0v$1T%S5MKHqZ%Zi_!hEpmup~iK5I14VA4NGefD+;-%#H<) zj_rc^6{ulzI3DNN6c-5Y6idBDr3NyN@gh2C)=rS;4SC8c#szNz&W&d%E|)L>%vqaG z3`Z+n2nHfbe)eUWAj^wibx#~cXudwetD2vUR3yh}S9PzliX6MDq%y6p)pIT}y*5ux z@^s^}t!(r=QK=9QS&yqKu+|tQV`eh8*Kl=2Zy=wu(YS$_yO*IDWUbj9cOa6W$c_?thu(tlX{-rFqOHJS({?uyhFnbDfTi-+Ci znz;i-A=N|o#De&V6+9qhmJcJqhNPCf)#gtuQsoqdDxU@e{+ z0wKo1WKVtHM4_@U&fmb8RO###zO@_|olBBi>pd-^iuzH6&oBmP4&{e4HrmxhS9y2b z1XEM#X4!%KCEl7im&s;CW0F{<&T}p9SppN-d}i3%`vc0uh0Q-jW0-cHG{tWcDg8|% z|1&iHTV-xS<=#BfdHXoj;z`p}#3Ne~0;p8dHuQLcq@I zz<<;Cs*K5U{vk3PrIDu!?Y+VVHG*(oEWVOLdz>$9hd5r>rV@*O+gY& z{HisJMiw_=I`zCrL6q5#{RpWj@q&012IVAB%(N9PPj`#MwN@YX-k@|^Yx;Rr#v zea3-u348Ez>k#tm#kH5N*Nf)k=|=v~B^{%r&T3mf1j`ALq?V};s=-w|pX`|@-6@JGmuK zd&B~6tcF18*vw#kUcz{{%Z)WWgfDx-MLo@9BFT+h&zx{o-Y)Y8>DolSm_;Bg=@J_Y_qgy5ikoFsC9k%oVKS zCPZkxU7(#DN_)AyY;O;D=L!mB15OiBUOYBi7H*e}xTYPAz+7&)VItJE>+{36Kj7F= zi96iQCj+Nth3)sD$PSBr2^4_~6<$yn3c-312?-DA@pZVA3MxC8;BysyHt&ZMMKq7k z%R2yZkxh}vH1cy7YaMAg|8#T!xDaZQEUN$>0wkL483+0>0#S85#Zv>S_XuvvMhv%= zL%+~E@@M-Dg9uP%D#w`Ayq&&&&mrkw3V3SP2Q2WPaIu`=Z^as#4H)ydrZ7OR zmOr1cekc$0|+t_RxzGdR@eR-vN-Cp4DFGQI3-q2NK-a8n z<)B$ZX6TH>xF3c}_MZjUQ^3b%%N0Hdn`SPA5B~X&VRU2sfRRv>t1r44MK*s?L2K&n zl(yABhx`j=L2T&B4oD|$^2@21`^j@7A-$fAX|yrdsp+)w9>&u}Fvc3`6xE>nS8W0$ zE{@pHD7aR`dbFew%6S>-+4Bj3&T$M0{BZP?hGdc{G4lMKfh}f&CHF#=LsQ-~Eyf4S z`tqpGS2b$Mt)}nJ1kc~OtPy=FROo;uk-XaLs{N(!TUdl9Bo-s9y<7?hdZAv1p!dN5 z-+>p#4*(XK$|rr6H%<;7gjtsmt3Mt#Ow{m&t~jpksr0d>Yu4;#9# zIoC!Q>w#)ZJ$OUF{6a1m&-7R%WF!Q6RR){84n0>-hej)?D&~*u4Lt@+2ji%)+poTA zk9UgNN}A8hC|3&!XL++v7T!=@FEF6*=dGtDS|L$GtpYw!`3h*4iM~QgMTio;av9L; zqXBSgw5_rIeDWsqY{#i=$8xIlX+xAb~>;jZ-Gm(&InLtK}U63 znFg`)*TXOs(I~s^jIN{~&;v!UJfSv;a2fTD*P!f#URu^b+&ZeeVKf0@*KSfV@L@JVesyu|)#v;uk4`ifzNcyj(NNj5rVi!X1x&dF-mHb${D zooQB=r(3QKv&to_wH)9|Cd?K_AcTHb-tmBt8jX=z3SwfOhOZb*r~&KiPOo*!ebrT8 zWK~CnDsgCR*7Lu_S87y%7pO1*s)h9j2I1RTBZ#Jp+FfMANc@Y|6(0_Y-|QzYAa5xr z&n`2Rxh`!i6x{Xr!@>K+s0LaRfv}ivrSB0Tr6N92NAZZ*J`uGzK2B#ZcT~96Q*%5C z3k{?9vq5ts%K@SAAIKqdXosc*><>urBL<$vplt%lM=NjQl}r9=A=&*DDZN47?W9?s zf>}Qks5Db{njD1PeZnHp81%)4i}gI$n~}v^6d8 z3f3?~nr14=vbiQ5BdvE5n9Gh1sSACU-hC50&ylwMzlh!T+wZ@KT}Wv<`PlO*+)Qux zKP7fQ&3S+jzuzclVEGRy`hVL@f9r$%n+DT``nvW02!a<}tPlPRrtLu24M}7NKCvC6 zugj9E%w23V>S7)GeUkCGfd_rhhnVk&kblQz_C#_)o0xcl)##Hk^hhxNFH2>#h()Kf zCF;(vU5@EUN}96p024S;DhAaLC?U;cF1l25ZYg!6UEf8 z%Ox4l#@mrfng?qE+k^t`OfFMm9^2G`y-K<#Pvj~G$XX{JPbg;!{*fqcu}a>IcslaI z9Bp?XX<$A`S66}~N0~O)6Hb3yyb>{-(xS64KY~NzZ!y6$!MQDP#ockwgkYpabI@Ke zp)q{=0hc4(@W@kmQ%w*?niZf)Y0E#IN6^6*TGV7D;vGo3U>7FQ-OvP(*cMELa z6wB3!bL>6^C#1Pn8Jsz0gxkHIS4AQ+3`JSTIe(%?G|ieuJr z2T+w?c=8Zj-Bg2>W`=m-?uMYD@~+JbtP8hv8=-$DEG>kM_ZjA|hQommA}0hPDe!n}=7*^63P#oCTaDwPBQZ?$hx}y8 zT4CD8Ues4~>m@tyKC5Jws^FfkJ$QIzr(?YKgsdeiY9sg~+O8JDHMwfBIfWfB5P6;R zlb=0<3gty#&%clWMuwx?d4b66;0gZhiuBZHcFF(oF3esWAO!|YIU%RFeFnkI|D=6c zHzA%#nR4yT#z)|#u_Kg!g%0BwzD#~uR!rR)MLgX{+~5AALG={ssm+k9#gIzZI(F{O zK>(H}O}Hog#FnONFr2B1>^1=TgR7A&QyyxtMF zSncT-7FBgRiA+(DC0Uliy4KHDW9usxd(h4FhZ>~w8qCslJ==bT++14{$CyDIW1Vj!kOcCLu$2Cd3OWBUUE0E z>*zLw?zt>rJ5Ylkkq|}Dj-*&0S*|W^t}!azpZ7_{7_@KnGH^^sxh=w3*97BFK&Axz zyiGv*NKhVr5^@&=q(iiL_fWQ`mxW)d^do0^QSU{IUeX&1=`U>>D=06>1ZUlcJ=f}2 z{ZOCRST0k;}P`^(hZB1gPu(5T(3W>$bu!sGD=HK=y%Kdm#p|Wa=LT(c;-V zv3#|R;e~T-QgBzVwT*0HIoWh=;F?cVj#G!lq6P6;{zm_ZLOf9G1r|be-eG{{9(gp> zvbJzV2?=$#PyBp(+{PPhx6%2!#|f|Kax}5d+&-7X>XbunalH^x4m5?%6xdPIyWmj1 zfEOSBjTb$tC}b0K@_7QXH=ox`!RsKGSjtl>=#15aNhAmq$$ha`#ltMuHme+@?E#c( zxJRmtQ4a;oohqoiYk@vVtH;#d6CR8LLx~xw8h67FB*J+@){h$UWg`0A4QUZJ-cPa9UPw zAf#2AuiXs?#SEv~`uh1M54W1-6<2#>e=*Dwj`sBS%(EdR`N?%t#5EJQ`Wd`>eSh&7 z)5EnB*X9PidV83E_!ReudZ%sA4$sxCGG3x`_^id@c&p#{;~{Kv%4QvV{Xi*Gk)4y8 z(5`fPa&gsXcB^jz5fK=9qF(8@D04M2+Og7HLdyY_S-qjIO`TyjfjsH+dd0b6TUKTz zPm++s-Q4(cR9x~5Ki5x}=Dc@JcQKAA8dadu2btIHO39|h*v-_P3huV*Ye^y}%J*Kb zZmUmml`aq21IY}afflonc_2g%^u;sqkbs1W^@_D}PwtvMMDzV2j$Ba;Q?1&(iru9l zXW&Y(Ad6=|(MtJLDublrRC89}SgO>LR!xXzp(CU)kW3B2(sn|87L=U-JWS54x^#*PB@(zyIO&$LWz~5oVJ8 z=-^udXcn6VcD~l;Xa6nC_|xyH2)0p+`rCdHyf@N}d@pBQWJh7PHIw10G*@#2FQ%C) zZnC@D>PB8n)8S~Ta&#~rm#7n3#MNOGm$2q5VccJ82;l`!8Vy=R*B)v6NM1D|%Vg zX8mrog+>Q;Tb+5#^M%gV5q?c2UtN=-)AAkndnDY`{U@G}>(Vu>(`#I&6QvnB&SlN` z(?wyzXVpIRU>vLE%BlNSnM;H;lVq8Q-9>_bCfTOcCI0ebMzB&P_a)l;#WiX~*^Ze? z1?JY6T-XkC{Ma8owa5O7%57l{+LxS#l+9$RIFrsh*HPR($OPVb);WeXHVl}(JDDM_ir&Q>H- ziI>Co371(kg83pSkmrum%AuL3IwIpQr48Y7s+I+VcRRt2gADC@jf{9Zo^~Zq=1f;@ zoTkplR>W>rrvMn7+OYObro?63?^;>;DaP!8t!aRJL%;(V5PZ?Lu>`y_@K0Okn=|Xw zz^pkPWG41}*O)m{N}<*#sP@GtX<-4J>e==hdtXG1$kxiRhL)RV+pV z-Xn7KlL7a`RpuAOiwEp)t;=47vYI+IzEv@`6(|B@lSLUTpo4~ggzwCFKn9(ehjL^< zk|Y@FT};4LvXQFMcCgUWS%{$2O$(h08sOrxaS_m*V}Kgu3O53!J9iCn%mIuBYy%bOeCA^G>%FdLD36GunQ_QgbqCC?6EJf0QsGaU;E*uKtq(i z?rIuE!ANLgpgsTl71vu_RI4wb%c?5Z^{TYs2nk;gnZ|0BWOl?;M!SkK$()>+1uHm1 zBC&k<;Bc_l{U1CFhv!NTKaX6Pptlt*ZJ|HeART-ioZ^Ym-|!{%py8DS5MP0hUh-C; zos{f@PL`OD?nAn@BQmG){&@Q$8U(+_k6^nnrmr9k=Z3`LgVGbVmZj%bV{*s%XXx|C zv4tXLm_0qjYMR6#S`TM+aqi|_Q{2yjw;}m0Nq!}koAYr?=I{bC*BKgA2LF+LuO3qG z(EsdRn<=38QqULdEIMj&tQUOe@gZLSLi=Z>s2NoaU=&aQfLq-E9P^m}(kfo4{cEq% zb6WMI*qSOtzChNW2vZHtS-KRY=(8!!E!}wyFi8^E>54+PM*{%7+_pV zRN-LQ;l=CtM$rBCj%zxjuq?fS>Pgsk7>B(qB}q&@<0{IVJ?U3uMp0A*(bO3KWfYAf zqkHSuJ{)b?CW(ahFxp|B6O-`l#gIq7+q!c5z8zy`IhVEbm^jMYYDL9;%Odajyq)~8 z2`1s8mLUe@mBbFr?orq4DS-sm#!JAWTt^nKu@ z(>rZ(%v;;GVP;Oju})-8<-^nu_k->?N=2z;+Ocl(1#k|Vl`{-yL^tj`&BLNnpE=q* z@QEYOh$7-U!NIfQ2A~bZyU={cW~p&Lc`;#ke?qj=MH>mcS}cRWlq^v!N$Ukf$;lOcRvQ z${hj!Qyimf$_PyBvgw#FRWs#~w5?G+!lk~5+nkoc$Vc%ghBD?{k^b-3)FlaD8 z>?lyEM~G~$uMhr(A09t&I!`RHH6ni)Es0%bN@?y9x^%qi;%O@K?fk2PDE zRQVt2WQ?j>KGYlVF_yc(8i9$g2 z-_%N!l|!s*m%vGnG$$xoK)kkAxYLxg0Mp|6yC614e28Dvkz%%U(YQFh_mPV$w2JJ=%^A~sVG-|8UVL9Pc{$LcwuxIGaFzj5ac(^xEOjXOQfQx1t(l6Tb-m5y)LE85#*h+OwVyK32jwMS4F z6JOVLqm65}!%3GoOT)$^WTOX{rs4T|)hSP~k}E;#|}bo)gJOg4;*zv9G)PY*2l z)^|@HLL?YN+oq;rLvggLvK6x>;<}w|bscxfAfY5jb*H(g0*)rbJRTYvPj}}#{R13a z-|q?n6g*y3SRUUin}=stDhZqFE-J(4ka;2?4h9w<&Qk`6s+7kbn*D}^4j}Z5j7#J33Joa3d&VTVlQw@})j$W9O&cG`SWoaxZqU^d_RlIoo>xH@8 zY8$9Uphw*e-2dFC{PY_fP|^BfwdYAc@*3K0TOx*{xT?pBa4(NyWk%!x-#e~OJL8sG z*s=)`euIot^e!=Jg9KY4YC2e}jl!ah9>QRZSSTmM(WI(W_x=ioff~**(FZ^oq79nI@04qLc zBQ|xXQL?=rhxKmxjq_*`?$4ZRqC^^`5 zBTG;{sEg{DPs?J&1hF^rNk>DeWrNPUXj4;7J{Rv4V<)i|)*X^L@w7mNltsI3$ND)l z1!Bz46yrE2B$<7gu!!^&eN7|;V>qoMxcX_FG@oQ#^}S-@N(6426M6$4M7^gB>E>D% z`-GRK(3p*ULE;jm-WF2u&7ud!WMjWVY!4#2L=6zf$!g1*xI92^6tH8*0O+OW41G;J zO+iib*=dYsdn#fF+UhCPeX3j32z^I2dw`E>R`HVjV&&~-FvRJHnr{NYomK_v*}}ce z0B$ACCx^YP4rIWaZxgPx91>%|f%8q9TW^3;dT0!L2?v@gE_#@Rm6W`2`isg>N$SiC zPY4aK{Zbh?Cp@5_j-9%xW=3q5C_vUY$avfFU+GF9_r6V|x85rOkH&DHR{I+S`S@ec77JKF-*>eq6-Z86Fqf%PTyZK*Oo{K~T@6tU)H*Svr2ZPj=2QeEJdQV`GhopJ2_S3gn+eWa01QX84)sYi zYZ?kS)hJKsfn;lln&oBu8fn;9`1;RKq|W6H8jQl9pk95712;bOsN5~8Sn=MebRVc4 zeo7Ac2K?E=|8Z2$Gi}guIxCnb=0gh_6uP|BN^yk0Bsxe8#hIp{9?qNcB&th?1a2cF zinQ+3l7}AQ>9|{nj|aj0?kWXB*c?vC4JGWr0p|u*vG1ecCQ=0|!CU8=X_kTu4+3-L zynN0?d}*b_vuKYqyuTW6BIea_MgZG}JDC5uZTRU;I}rD?ZRlQxJ4f_gst20%nnyYk z?q&UG8&dGSBkQz@Zr@QJ8cqB7EM#w+=(tBG11)+hqGurPSI}Ki3P#~MnOj>an%zA1 z)xWoG&cHu(bx}{(xac4_jxSs6FE7VY)D+8?w-_CaoP~L;Wj);PZ>MPoU(8Hx@3ZX3 zLYSYgCtB{ODCiw<=vS}fy;SvE;o+V~tk8$G+6+^ayabs#RPVN59NB$4K5yUjUgo}R zkqu)w&}{icTl%Be5);Htc%w*Yzu6jR5lpY>+pafWDN$T7`IlP#w^ucW3mYKtGrWF% zMc->`+@^e1lkH6{vRtS+rz;?1-&OR1X{?s$u3!SRAnQVnEwYI!-d| zo9Zs!KZnLE`}Fc9f6DpfD4VB}3M+OIlzDaI`>(Zg7_u&}`yq#3B<&UEZs5nS({64^ z9W=@VeCP4ZG2-K_qI!4VD@i)J&syw<8}5##Q@~K^eh89;$%GJ>+r6<}6*kM?xZxmH(_T_d~OIg#xgku3S|m|M`nuH zJjAo(n21RsJx-C%(c!7RKr2}Kd985QWp-hov~_{nPY%@F1#E>RpR*6Hr%_R@U(Ji2 z%yH}M=g2SI(`OEixw!&}AKZ0x7<)bMjA9GgzfRPnZ_+5-S-0POT$aCGM}ZF_@Z^8^Kf-++G-m5>=4fu2tek?9{tfz(G5V!8_P?FoR(JM`l2P<(62 znZx3J2yr4A>1jVe{cs(clry&n?p@DV(8^dVpG8+q0VlG@CHC3PxXuf^i<|LfdYjG! z-5Vu(5B5qmo*1%>co4o2ahPo*)Ql>4FeOM{BJ8m70s1O8aI)}8u&(U_QFwwnbRqpm z-LltkJ8kOM6>B3`T6~CW*b~`NfflT{=30EA#qT>hH`{x_*}w)qGs4gg_Fl9LPq*Ax zr91#T^Z#ziATwMG+6uH};08`E|0m5ElUIX!OqRe)iRGc;`}T3&zeBHZV=H)d@|9j zdWFGNmxWw=d9nk6#UR+nq{#{?bnd>7wq((@ZCaT6dh>^MQm1AU;qiB&rN))q7~@=8 zF_{W@!RW%7?;a1ht>=7-X9J5PGa+!8Z*OBJ48fMBwp&w+MdEyVNgY;38C_CSF+VGl zk~%cyZ;5AoVN#vS;~Ub&8?PTQ?rWRdl7h`BHoNh&kV#@63*}X7iBw57tw}XxIegmD z-6~hd(QjhC*JFt8n3RfZ2oNq;5hV^<%z4E7&RedaGUu49+Pr&zK|AAszvzpPM2}_N zq~ty+eVF^&z-F69HM8to{j+P6#Uw*kz(Baj(RzZv3_3HqUqAvL6S_!fR)QSgD{XF~ ziHCGi{VRspum0P@Y(4Oe?1CCw1z+afauLTG_F0+45Hds52$XsHugZ@CQ5;`&y7Hr} zF9;<|;j#qte0bPpv3Yfwp#w-b8^NLPYHn>_7b2Y7GE8}#QddUs8M8fDs}XT%pRi;; z%E_@)4#J;)FbyqIZei`@-Ap}7nqlk)Yt}|$+l)cpa}?+-vAhZzlye#w%uo+-bSe-{ z6M`d>Ds<59Amcvb_^6Un*e{6XuD0SS_&MPLdgT(Y=^(@dVdS!_P2?%T78MdBc!=sV z|9HN8AeU!sm4sLh#JHu@cTJL0O@7gw-iFPipqI=~x=UTLjS%8c0#1!pmV~lR<8cv~ zu9F-91R<0 zh}G#tJ`Y^w&l6qBZ>jc-CTx(!T_??e0LYpl`q|3C08&nHQ%jwQ0EQGT;JdkvaIXPv z=T5p%fP_c7eE=Z(=&O_We2sgS^KHdj)p(v7zI=nU#nuN<;_*hE<9-ckBjN2#RCk7` z#Zbl1MeYn^i=lkmZZMZd294P3vQJ8tuPKh=MP?gHgp%3pDLgVcV;Xp~-V4fY=s|ME z=ysZ}5K0tuC--!dtcB~WI-cTuP66v@9aq%20ChL%C9he(=-q*1O}oW&nuXw-PnReBRbUQU%KUe@Fs$u>e zt|c(PQ?Ho3J40pTp2G1rw0-8rikENB3J2@ZIN5+EVtGLj3;}IPsBe5JvT4#ma!=N` zC#4p93hO@JzZfs9mtFpRKj1go4S#sqHP7%>2Dt;a67b$Y5!4(H90k_5&0dhZ-2uk~ zs|DR47?p}%I9Z1#+ogF#2Vm9LXC}!?`9`65GVhb+`*&wxdT4f}lnH*p?y=3{2ALQw zq(gzwLwMjX=y@M*WHtiw*@U;b?>W}z4GxVgjzkQqXh0aEwjxnam_hKek@dv$%&W-J>(tre$DHQt?4Ka5B0KBkf0`c zUG7cYdSi6k*(%ljH3-ma%|Lz$=M2xd4vO?8j$Yk@U!Uo|_c*$HkgRP`5Euf-ppDdY zZ!WD}ejr1mhyB2IxK~QgPyZ}P$}X0Uz(L)`u*o8F_SVWl!kY2S9JkKf@0e>dw2C&A?vN~r zbVvuk=R}H|_C0huu&O8Gox^5&5VW`vJpEiR(G7;Zr&f zxEW>8I0GF^b;P{OC5|aznyghu!h(2n|Fqa)jR`bt zt2LIs6t$i}_-WXtAqsC$SfdsCH7bDS8y5S0{_7-Vpoc@e+kzvj^T1a6lvYK7C``tC zLX_8WtRfbQoP@RAr(`Cl8mxD)>gf!{mBL^e$7XFb?yf}Ek{NeJsNpc1dXF!`uZ~ts zU!FU9?^#P*Oa`V-w`Vgcr$)h{f9qi0*e$Ax&y1E}=%`^Sc{8U4gO!glQ+5w#Q*@Sg zI+gQYE5ZRadoGLiZD*sf`qy>%Q>h&6wTRbNE9q^OjCvfIBkTAfwDep4H*um(dGTZ} zseRi#WWgj)+Dj4Q^AX zxH2?6-(MC^YE}5)Tuo`abS`!&5)$JtuDB+YH=ihN;K=%fx>)!HQmQt(%krDQl*A;hgj^x0ZJ6a>5U*tCU?;lVEJ+){MK+I zoMh}0vcO;Ouc_vN7&_gs4}d;y#Z zH%|VGL4o(X2=cSx1*U$RiQ!9PE!)Rraf96+k8QisTA`Lfj~Pq((wp8(LC#J4cg-kA zE>|E;C?94h$XEiUSY-dB{jR9zWIWO34IORDy+-O49z_kJ~n)?GTR zd=J9k^$}m#Ygr=e&&$3G_)O5QE($(1ccs5^$6E`AtB3QAAorzLsszzT36gIY6=
I`mnkDN0pgqvx(?mmam0gATe zu`(hwFu7A2dWb=UiK_MJ9cYF>d9{6Wr)v~&^rBN_@V7!;Vn5`15_JhQOe&qV>Jyx} zs3?3>D^zzT1=C$Z@O3v>euE3QoB=-K#WxT;yrf&YU?J+$wAAC4f#LYc=47vRyhC{- zA+Q0kWl3adi??G{KVA>JI-lRHw?dU+ElPRG z%X}|!&vFBHUt&9u6m2vh%jX=YXx$>g(%5id@8Y{8cxa8BC&B#g3i2$MLP{)QAB^d0 zL_mraIA($edHPq6-I!5X^9`blGam&fkt}DMCFZB8X`>|wt}^h=Vp#%5q=9jVZ?A68 z`To+7?teYb)z6)ve@CGI|4B5PTw5X^5@5s%6`-f_zk`K4m>60b(*OMV(++!IeemN; zcJ$U4w|wyS&iAbA;iNKU-A-c$>}pQzl$?F|t|H||1|+V|(l9X_6OtJbaoVuW7jhC{ z2rTDgd}I+Lxn6Hb2Sbew%o}cI{Q0LLHOB6j#$}IqczA}dPbbHrHM%31-mIl+wJKH8 zV#x-FucaF=bKomGNJKR()BmUW5aJKCc4*D&z9f;zRC8OH=`#?g=oAH&ku{ zzC@1A%kRVAPd^qX1Qs~L+YDneUvF$cr`pYb^|rOmFrJ?1FVU{o)PmF1ex(udvPhLG z9`^d|LsV9~0qqV)$@pIB1vOx6zE0kK0;hWF79Aj!rum6NgtAdv{U*l}5= zHhm27Fi87;Io2AXlwW*&_G@^zwp9lxg=vF^i}MH`yyF9G42y=wwNo*l!yJybk6`H9 z4Q9huO`>+q9IJuIu_JNQcdm6O;(+aZGol96n}qmp>fncHT$q4O%{F<9lS$B_Hl-DA z?@|9(<}V;Jpqn6qV9+|MMJzSVLu7B9lq6lz_xa@_WIp6tn2Vj3&%|Ux9L=)(t26>! zPxfce0%d_N0uMJ?qQH&W#Gz(dXS_}U`NK)s<@>Xa_^IXAhwHtQS|e`iHJ!)P$$q}a zd-@B_tc%6yc-ge3>&Ne{o}L!oSCk3ptD+RX0}T+eU%*g zkijVR`NLiEGpvgNkdO<2J*Or~;RXhfQraVPeZwPfsG1cx$WVtJ5V^_{!9aD`(#$?sQ)Wbnj zz6vxr3?Nj;;>_Zp(c{y%N6BoPBVQ2n-Ff}yGJt?zbMLSb+U$_m-Fg|tv0HjhH-v!fvV{-RuQ1Dhsx}cb!z6dyw9XrJvW8+cjTj&Q!#kqff+B3txI)B)YC@?P zS+kjZjaZ$2lkn?aljhXLMRZW_?e)z2zAoYNuIN#f*R5f-Dy42d4U35=5f#>gnGBz0 zGEE6bhaiUuGgO@DXc{0f@d{dE0&XRmUm=pi^=Pb>L^GhSk_pbmdrE9DAEh?t^@kSF zH|oCCR<+|HkToZPUCoWA@Ykh43?E#zzjS1GE)bDT)Jqa+JmY;&8{H#f)mFY#Dbty1 z-XJ)LPUChdb#H?@XhL+(__+XpxR%PZS&*?zR!Kv#F4XoFJeQ92dpL67#8(Q`a%~5& zPxe+9A{r$p#H7>39`EB6b%e<~X5nRAd&QP8rcp_|ijJV;@G8)=k%XQ)6IV!i0AJ;- z8tD*rh`Xkz&QWN=ovprwImB8C9~4No2!m+*6Y|K1^m6+YT_(!t;)U#P6`p%GB#0BH zoDbz4&I-O1uiOAc=H+sFHMI)0v{4P;;S`ZLT5mO2#eMIS33lc~hMhR=Wig8?_femn zwfzJkpxfYR5|@Iq?SW$w$73BwtKt%jBy+su=U)js=^8I_k#s zlBUYLZ(KRoMDTu+SNh9v)MDHWnIt&}uQxN?O`ckh)j%|Fpf-7jpMO3#*tD<6(T*=A zuk1VPS50v}5>M4-g@@9xc4yhwomAiVqt!LHzR+3+rA45-%qp&t&=!r-Os3hHi^~r` zW^P^Lm9DzQs(0flC+8{_IV^ZqjyW$Hd2CFXcL=Qeq<44ZACmbnK%#stI+sN^d;dKg zUH-Chdo1RSa;9gDQf%2Rv2e5QHF1C=N$LDoDqoc%#zVG7Kb4&M{c!3bn~?&C=Bach z3)h2Hm!0~Q!)qT)JnFJ>Yd0D5iGr%VR8?DbR`J&H;;IyptfQ*Cl*n0vZAW92^1`3JMY$9u^)R4i*j$ z0TC4$0TBfe4h|U;83hd;0|Nsd=>--hIuRRh zfC3GO00Dr3yaIrtfPkTZJaqz7)Br#rfTjIW;C~$;pujRhLP5j8!T~=}jSK(<0RsaC z2m4WK;HN!+e+Pi0K%f#a3P7UC>q5P zMovLV#lp(Q&cVqg^hQ`jR7_k#QAt@v^{tw^zJZ~Uv5Bdfy@R8Zvx}>npMSuIz@Xre zsOXs3xcG$6iJ4j1Ik|cH1%(xrRn;}Mb@dHjJ37C0b@%l4jg3!CPEF6u&aJMkZ)|RD z@9gfKoSvOuTwYz@-2Ra3hn)XD{t)b$Tqr=fK*7Pmz@dJ~1p?{}Ji$=FA&3|uQ3d3o zbZyaIG5J8F3r1#?w*z}4g<}joyHQw75|&lclOLk}l zC<+(~fDiDXm>EI=`2Y4iYh0d#Ys0bJ+)P;x(ywi*N;G#Z-uR$wb0YD|Yjwlg5TpV3 z;yXWnu(0c6^~rpDDnVIgOXEZ?CcEU8s3TtTAhIlj2wnmih9p63I6R~PapFgzhx8`6 zQWtG{l=h-t$dAmgzPY-ZvcM1-+JPSNi{mSK-=Y(aKxK|<$_9EeU-Ny_CelKZn!JCI z_hXu`ZYn>VgLwx>fh~uq%83V!F)s%qjQ&s0SrRdQQxd~Ba%!JH0l*5#yzzvMo&eT! zz2C|b&(j(#GmS-fQ;pa>Ehz3(a%>+9yIwo)HtgxvxgYSigAn3fs}mIBEz3*P;Z$ z!n?}0j%y-4>`A}6FiV>Um^#i&_~wV%qiWgd?fH(&zNe(hwrxdW1d5W~+rkk9 z82{%yC@Ua4io{PkERif?OZv-7ctU77G#oMl!iqbGejH<#iJL!DPgIlrED6ow$7&KM z*!Iu-fcIHoxm>EM!T@`fOD?vQeA@F=+;Eu|Il;wlgHJP@i)UR}`5W6#%+W_0Q}I)C z{zj4-K_zmym;oIC4<;(N0_W`6WigV(CHBuEnC}>0JpmflBd>7)wLk8d;ey5!pgT8% z31o~qayzd@yd&-I=zJ}_+DzqMS}$I5geN~|Wy7q5*q`_10ouN0NuJ$E z&s6^9NoEmfHc~uEPgpNhz}?LDXj0oFUZer4iMm6JL6pRnhLYVNF{Yh3Zq(cD?~+dd zXud#Bf*BlbMEl180z2_X0tMN1etdKMoG&8f-A@2G4aq3#o*Z{O3u05e&kK}NY!V+J z_;K&EjYG<<*OhDUB$nRGj#^31_Ry{g!0WswGKeYbB?O7A0tg_4C%_)kom<0qxCo5V zlvt~v0DP&HBd544A?8D0MIH3E-PE({JR+y?-l%z%v3PJnauUu8(-gPko>a@q-@AgJ zrz6s>t51Eo$TB4VhDTA|+$p~>8^*;}59NCjil2=e9`Dn8_eF|bo1z(wW$eAeSk;VH z>f80ZS74R)8=l9}wVPMezU(+h^8#g+sp6$guk#i@lcF_mrX*If_(dGy!&&vN6xdIk zsH_|>f2byTfxN4()wdcypkXp!gsGeC<(d$=Ck=4bd?cTsJ(6Vq_J9N7WX+0@{RRQJ zgBKmJ4t_DjfxA`HMDAX)Hy2YTeDXqi$|$Z+bk^D|M84-0CHVUl(6&@p#&rUByz^9q z6C5{&Uc3icD|VALr0ilThxp6MB+j%ZDy<%fhodIT>c3BXw3u z`B4kjz*_U~9M%YppI@CtaEK6N1FqUxKsM}M{N7H{9Tgw6P?}s8?rl-5R*K^QeMATe zHkbI}PDAm%Qv=egPUwR!q=gvX%Z)@0bknv882IYYs@g(e89L?Dyp3+ZYo(;!OFQ645>;z0p6L^gHg z$X_$()%hL$?ZFg7xjIQy&o1g`l3|k5k_FqawrwaFuQgf~wlM=fREI`tqY7PHCri2D z991YAm6viBj>7}Y5w^b2=R86JV-A+Qd$;3a<<@BMv7Vx!R8R%(z`zc~qgyX|AHt0WetvR0;Z0gRTn@SJoPqPu4l*Y3v>_R z75c4#JPAs+ZDuzPpfH319nl-{YZ^ZUy8NF{CN%}6cFc2dr4gg|yqKC~R?HISN zqpRJmb#O6DF_-+NFm@FJ6*IW<>mKfS+IeqL#U8+}R}IehFy2|<&b|I-$HkJ!TLL9` z-WV?KJ*mrbwjfD&EVZ$1mMYaovY#x6qAC#0eAM{9U0%L-?(aE`Sf`%&_toLsO; z(t2QbDL|<;-qK{CXmsGBAVzj(D0zbBWQG8!Vy7al9T`)cH5T;=OuP>~xr{48cG|+t z8ifHyu5%yK9vg`A`S~`#fLWw_RRw-nFHnqnds=sL`y#0ifeg%~_LHpjYK#MjuEsSLbH%pW#T(-j+ z&aXW9-CJZy#MvSAcXCkKqngA14y~v&OJ+>wx796K@R>yB=qTWf`c4m>Aa%*590bnk zLr~Ixy1&><#7}@occmvlshZb0m^y3Ed&%k(o~hWpC%{+6618i$w@1oH*4BDz$QsZa zeF5(TNC!NoL+?8>`mfFNuG<}77PTU~RLpCaG2Ym!cbJrMBLxi~F@#7O5A410MO?B; z#}E8ZeYe`&)x8VQsz66&`Id)rZu>I+QhNH5Z}wAOB?H{oei&;JDj2}6x9yI3&-nxW z`T&6`S6uyytDY{iAooXK6@}J1%>(%|4$TeB4qRNH2qg2&rXu0$>&eUSd+JS75IQEf6;CFoN62N${77{vJk3>wtk`zwSR%7Vi-t5{Ti-19!D3`l6(48ZjRQ78%W4G~~MzLwsUaK=# znJ+mNfzF>dC^j~%cbtj=9&p0;1W3anFGcITFtkmsuIw}`)dw@OKf=^fH8SBwH@>d) z6@lJra05_eW;8VVb}i=BC%$%3eVHBWo8Q~k%e&=G`epdQxaG#7XKGdUzL~QVYyrRY z2>`P03kQ1^rqPMd<{nqeb>+P-LOKRx5Px-y=B`}nLVlSu|YLQbaD9(p%Q=O8-&FX~#h7T1-(rcG|Rc(Bmd$Taa57#%m$t9u+ zf*~WmYt;EFZw*SHA-K0ZP?<*X}V<+cTdWYcwhfyH?myqL`R>6Pv9a5jLn` z8n2TR_b$HouebRcW&6DG@^&w8WzsBx!8_YcEm1q*B}Y;CVY7AsMZhis_X+T^2`c@1 z?={P`!$qqGC;Zf1%1Gy?#GyhqvW*MRC+H2M`q*pi6)l;U1%}5D1@(z*qUNzireH;N z2=&1m#u@88<=SD&4(mzI+k7qYHGG>{a$pV~WYYp;7FGRNO-a-osB_S#GCiY$`Mnz} zAX6nkVKHP?#w;!dc{N^MV{VOUHLiIEf-^ku^95*TdUMpbU|h>kW`GF=bdE*Lf1W{# zNjtK=65T$MiC($#+juvaDPq%pveg^vi)Gu0$6u0p_Q*?9H+&TSUjNGaX0j0Y;Di9y zj(8ETh2$nmF5tq*2U;5K&SdCFMfB?v2x31lXhwbtgv!UjxhFr)lBzM!`JytFE{)DG zOa<<&dj`*r#gL)tG4(Q#d)ii6fA})y3E++|zq{k^!`E#Lj68%nt#Mt<*V*PPOH_rM|2lLI2 z=PD5eTwdUb=gcV_O4n;?1#LpdycVbwNbaqQt-w$;NjYx_>2+a_;urbB`=q-{L zqP}5Fq$4C_I;$n+&N+kjq~AO2UG{cXFqHAtH%@Th!Jl)da$XjL_95_z)z;S3vX$kN z>KZvwM~QE?SY=-n!%}ly2db%0-PGPx?C8e6a9`et-|($J!ZOE64L1wdO_wYoUy9VN zLurWUuL6i@aFTyYGSA4Y&mzUvDoRn1k?5Vt%hu9bGCh&@FnmaHm|eEq3U;#NzX^mQ zhB_&Vkyp5I#u8C#_yg016#3_wT|+ojrXC0 zU~;V!U*@!gq#p<32Z&ys`8P&`Ati${N4En)?bRLR--_oR#)hpWs#tA9FR`3x+G~oE z`{pRC!hWg^S@8=ch?No5PGJIR>xaL%_F0F1oW#{ZI>d|Zj_W$6s#y^yr*dQ9Jn&_Z zRorz@l_-`iCcSDs<4nOxq2jCeiWC)YYHArDGyhJo|NVmzBod3bH%xmESblpK6SHc5 zX1zvZg9=xasaj(IhK^h%PC$0tmT5XtXsG&yM`W`8Nr|@Chwp4i_av!A3ME=% zE#M{gZGEW&q9xQ~U8vVNdZd)}0h&bx*Zn%RC*U=bD~%uXi-9_eFsBt(0>?yoR|oFx zG9cTs;z7-U2Ib`N2-T2i|rV74$63+?X+Ojj#{;h#5+$b-tbDYPWJOY0TODq@UR;w^q4UCv9SBh zwbA`Fn>0StTOXw8qXbmfQPlNv&WEDf`=w@uY-|RymgZ$ly3Sorv=(V<&F$8ry;Y}u zn4{CLF?}N_v|Hy3wSMbZg3@HWPDvZLH@~_cMl-VEnixe%K#c(*;md0Qiiku$&qaHj z+cAXp1TZrzrShvBtY65eK$HQHY#4L)UKBZ}A<-NX1?aX;SZt|4Y6Mwnyk97I-8+2c z(gmRDM3i^AG|!v z3oHH-tvw{*pKv=!T0XK*E$^ofT_f0YC0Y=mgH65d!iJM49HimQ?}rwC0?LztuK%G* zj=655F?=J*R;hU-mv0xE}@H7q4O?K81sZaOZ4G3kBYQQeI7!-rfQnZfA&j zN5d)p54(s)B$B!sPP7KeBcS@eNmVX4vC9sLh_3qnpkbA20UG6Hfb0eY==fS)BTyUc=(x&s@_$!$iOK-Dm zR)>Ng-IJ3vIBUN4uOcKq!Lc-dh%(>cq+9;vNpN-`3#^&{Ze~045ElLg_?H^s33N{X zS$7V)dKQL?4z3o4_CIP5en1@2mjR1^wK>??9tc$o(JsG97V7$< z;mv6j{UD!2X8hZI0~WBS6%f=0*2Qcn$Z&T*ef}xiMO)LVcV)0}t~JX!+_ti=_C@Hb z-$!yyl58Ne?Ck}EEJZWwcoNih4la!37cA@Hvo)^W$74x+w()}3q9G@OQ`^}KeF-zG z+Vc80gG|N1G~HObY?Y=a>kA&JXgv8V{@VQDSZDZSGEgx^ep5^*Q$y$fQp`|AY3q3g z_-3RTFJuRugDT-T9NQ4g4yRpR{-#CN;BwX-xXfg(n;&aA(j$0o%r`yVS0-i;9B(@= zk>%Z0&%R0bVsq@qI#~{Su`aiM;piYqM(ui?e*+T1XT|HK9%xp&dSPtvW~B_3^+*9$ zSw4Ng4Yuh71XuSpL9rNmSB;!}6KXl@H%m1-IO?i(d#`)3*5!jLe{1baOwB~GS6Go^ z+)i98!L;xFY2WZ?_AX9Gg|?k1EllEunKdju+6pEycCZ^PgpqKP+@*wf8>7^A3Vkov z8&M$;*c8Nxcn^L7+Sqyg_RP@Lx%=}@w3mXHyA&(EtF7AXbp#y2VSGP4#`JoZI*WR{ z21TvNp!!Jg$Tfj{Q6z^Sa|L;T0+vEuk1MX5Q0rYiMAlZXw}ZlGJ>_2x#CPFxu{q#UdP*!g(f}{9PS=c$U!;~^(2?oJ>(MJb zsdDXdt8vgjnB>pxgsjJPO6H@?uE> ztj^5>+L+j!$hXX?Bw6y!=kjI;mkj9HqS;LQVZp37?pxMROjzbsa%w>={i7IRMZjGN z>-z#|^vHln4$9n#~9R-iZp7-rkTEjlP-KPwH*lbn~ zEQsqK^^w?mjuA?71JeDH4Zp`C#^C_37%K#L39^k&w3+ULG$Dlbvk0zT0aa+kJ#6x|5qU$-mB`^6p>+7agdkFhKiN4>m6u8q#_G;qO%RGMdc@wiT6m%6fta+ZHgV7YK=L=JO?kDD`Kl?CvI0=odI&Ea_GrR6 zgPiW|v9YlfZ5)zTR+YP(M{PjS>iOnk7MAPq3RY?2S|+pPMH%oGg^slY#}x zC?A`oGr$P;1s_4t^2CVQa-99Qd-BZ-lM?tt?iS3CCFK;m79y_?jfIA(8Q$J4x8Bx! z5-D6YdOfVL&K<3mNGuAXICQw|p(iQ0jx>!vlwBg0>yb7UoNeb+KTO9TDn*E zo)~bf<*CgNsnQ!cZ}$A^zd=B0fktxw9$GFBU|kgd=)vLt7@qvno*%C?gsiO`46Ph= zlw55L?X`Y9Tym0s2AEtsWB_+(0c*eq5@>1u+pz`gXLRfgE$r!knj1d9P+ya{stx$@ zABjo{f4d9-zyX@_{TSl@jM?+2lvBTwO+BZ*q+^AG2a-mB|CHcQG%Vm4`UmZgqWl;( z0|nA`FtxV&AR{{5!zWAL9MQJx}ZU&&l~X|AhQ2Rq8({m%RKZ zDDNZ26zb zf208WOBMak+R+14|9^n~kIMg_$wP$yg#0T-;@{nlKi}vHqJKhW{@*C`+^c^={*}t_ zd6}Ol#QUWmE5yH%{~fpVx2N#8=%s&IgU@rp{UY;`{zm?{+Wq!q|DhJoOZq(H(k~t* z)&IcznSbdy?|CYeU%VB%zvum|r{}omvHXAGtXTdY_fw&ssR}G+|P#iIqtcm+b>+N&fnvH zc1F)}|G9OHF#HSLZ|%V!mHo^8;yL-b6T`29#u@!Ve(uun2jM>(Z2ltbTmDD$&F95< zzSj5);^g;7G5)mj`26zc%U!=NXA1b26n|d)dJcHLr1T4b^x+S{pB9*&U;gK1j9(W6 x0CR!A-GhHGYCOOE&r{3aFAoU$?ec$3H02~AfbrJ=08-$WG;r`c9QNb4{|7;YEG7T| literal 0 HcmV?d00001 diff --git a/P5/Source/Guidelines/en/ST-Infrastructure.xml b/P5/Source/Guidelines/en/ST-Infrastructure.xml index b141ec6789..5ddc207958 100644 --- a/P5/Source/Guidelines/en/ST-Infrastructure.xml +++ b/P5/Source/Guidelines/en/ST-Infrastructure.xml @@ -871,6 +871,7 @@ one, or vice versa, should be done with care.

+ @@ -1141,6 +1142,7 @@ one, or vice versa, should be done with care.

+ diff --git a/P5/Source/Specs/ab.xml b/P5/Source/Specs/ab.xml index 8718461882..9cdb6861be 100644 --- a/P5/Source/Specs/ab.xml +++ b/P5/Source/Specs/ab.xml @@ -23,6 +23,7 @@ + diff --git a/P5/Source/Specs/abbr.xml b/P5/Source/Specs/abbr.xml index e6cd6f0f6e..a6456fd71b 100644 --- a/P5/Source/Specs/abbr.xml +++ b/P5/Source/Specs/abbr.xml @@ -23,6 +23,7 @@ + diff --git a/P5/Source/Specs/add.xml b/P5/Source/Specs/add.xml index 8f55105eed..49002cf71f 100644 --- a/P5/Source/Specs/add.xml +++ b/P5/Source/Specs/add.xml @@ -36,6 +36,7 @@ + diff --git a/P5/Source/Specs/addName.xml b/P5/Source/Specs/addName.xml index ec28e8c578..d133c0309b 100644 --- a/P5/Source/Specs/addName.xml +++ b/P5/Source/Specs/addName.xml @@ -25,6 +25,7 @@ + diff --git a/P5/Source/Specs/address.xml b/P5/Source/Specs/address.xml index 3fc9b7f3f7..23a6b13b4b 100644 --- a/P5/Source/Specs/address.xml +++ b/P5/Source/Specs/address.xml @@ -20,6 +20,7 @@ + diff --git a/P5/Source/Specs/affiliation.xml b/P5/Source/Specs/affiliation.xml index 319d91a482..d53e4fc2d9 100644 --- a/P5/Source/Specs/affiliation.xml +++ b/P5/Source/Specs/affiliation.xml @@ -25,6 +25,7 @@ + diff --git a/P5/Source/Specs/alt.xml b/P5/Source/Specs/alt.xml index 02ba2c3b87..9a4e607e40 100644 --- a/P5/Source/Specs/alt.xml +++ b/P5/Source/Specs/alt.xml @@ -24,6 +24,7 @@ + diff --git a/P5/Source/Specs/altGrp.xml b/P5/Source/Specs/altGrp.xml index df42c046d2..c34ed13d32 100644 --- a/P5/Source/Specs/altGrp.xml +++ b/P5/Source/Specs/altGrp.xml @@ -23,6 +23,7 @@ + diff --git a/P5/Source/Specs/anchor.xml b/P5/Source/Specs/anchor.xml index bd66b33b79..3637ec981a 100644 --- a/P5/Source/Specs/anchor.xml +++ b/P5/Source/Specs/anchor.xml @@ -22,6 +22,7 @@ + diff --git a/P5/Source/Specs/argument.xml b/P5/Source/Specs/argument.xml index 13b4adb462..32f5ab4d0b 100644 --- a/P5/Source/Specs/argument.xml +++ b/P5/Source/Specs/argument.xml @@ -20,6 +20,7 @@ + diff --git a/P5/Source/Specs/att.cmc.xml b/P5/Source/Specs/att.cmc.xml new file mode 100644 index 0000000000..0784fad43d --- /dev/null +++ b/P5/Source/Specs/att.cmc.xml @@ -0,0 +1,145 @@ + + + + + computer mediated communication + provides attributes + categorizing how the element content was created in a CMC + environment. + + + generated by + categorizes + how the content of an element was generated in a CMC + environment. + + + + + + + + The @generatedBy attribute is for use within a <post> element. + + + + + + + + the content was + naturally typed or spoken by a human user + + + the content was + generated after a human user activated a template for its + insertion + + + the content was + generated by the system, i.e. the CMC environment + + + the content was + generated by a bot, i.e. a non-human agent, typically external + to the CMC environment. + + + the content of + the respective element was generated by an unknown or + unspecified process. + + + + +

automatic system message in chat: user moves on to another + chatroom

+ + +

+ McMike geht + in einen anderen Raum: Kreuzfahrt +

+ + + + + +

automatic system message in chat: user enters a chatroom

+ + +

+ c_bo betritt + den Raum.

+ + + + + +

automatic system message in chat: user changes his font color

+ + +

+ c_bo hat die + Farbe gewechselt. +

+ + + + + +

An automatic signature of user including an automatic timestamp + (Wikipedia discussion, anonymized). The specification of + generatedBy at the inner element signed is + meant to override the specification at the outer element + post. This is generally possible when the outer + generatedBy value is "human".

+ + +

Kurze Nachfrage: Die Hieros für den Goldnamen stammen + auch von Beckerath gem. Literatur ? Grüße --

+ + + + + +

Usenet news message: a client-generated line that introduces a + quotation from a previous message (similar to email):

+ + + Am 03.04.2015 um + 09:46 schrieb [_NAME_]: + + + + + + + + +

Wikipedia talk page, user signature

+ + + + + + + + + + + diff --git a/P5/Source/Specs/bibl.xml b/P5/Source/Specs/bibl.xml index 89eb998995..f1dc7682d6 100644 --- a/P5/Source/Specs/bibl.xml +++ b/P5/Source/Specs/bibl.xml @@ -33,6 +33,7 @@ + diff --git a/P5/Source/Specs/biblFull.xml b/P5/Source/Specs/biblFull.xml index de359d2876..9f7fb863d5 100644 --- a/P5/Source/Specs/biblFull.xml +++ b/P5/Source/Specs/biblFull.xml @@ -27,6 +27,7 @@ + diff --git a/P5/Source/Specs/biblStruct.xml b/P5/Source/Specs/biblStruct.xml index 36ec4f8b7a..ce4aef2a32 100644 --- a/P5/Source/Specs/biblStruct.xml +++ b/P5/Source/Specs/biblStruct.xml @@ -28,6 +28,7 @@ + diff --git a/P5/Source/Specs/binaryObject.xml b/P5/Source/Specs/binaryObject.xml index 88ce086b59..ebf576bfa5 100644 --- a/P5/Source/Specs/binaryObject.xml +++ b/P5/Source/Specs/binaryObject.xml @@ -20,6 +20,7 @@ + diff --git a/P5/Source/Specs/bloc.xml b/P5/Source/Specs/bloc.xml index 81f5354fee..b3af6e85b7 100644 --- a/P5/Source/Specs/bloc.xml +++ b/P5/Source/Specs/bloc.xml @@ -20,6 +20,7 @@ + diff --git a/P5/Source/Specs/byline.xml b/P5/Source/Specs/byline.xml index 7a3caf9f0e..35c92ab58f 100644 --- a/P5/Source/Specs/byline.xml +++ b/P5/Source/Specs/byline.xml @@ -22,6 +22,7 @@ on its title page or at the head or end of the work. + diff --git a/P5/Source/Specs/c.xml b/P5/Source/Specs/c.xml index 5151bf6108..eb74afc88c 100644 --- a/P5/Source/Specs/c.xml +++ b/P5/Source/Specs/c.xml @@ -23,6 +23,7 @@ + diff --git a/P5/Source/Specs/cb.xml b/P5/Source/Specs/cb.xml index ad01b8ce5c..81a1d50328 100644 --- a/P5/Source/Specs/cb.xml +++ b/P5/Source/Specs/cb.xml @@ -25,6 +25,7 @@ + diff --git a/P5/Source/Specs/choice.xml b/P5/Source/Specs/choice.xml index 9cd79835c8..c15f723ba3 100644 --- a/P5/Source/Specs/choice.xml +++ b/P5/Source/Specs/choice.xml @@ -19,6 +19,7 @@ + diff --git a/P5/Source/Specs/cit.xml b/P5/Source/Specs/cit.xml index 7c846a1267..f8d39b827a 100644 --- a/P5/Source/Specs/cit.xml +++ b/P5/Source/Specs/cit.xml @@ -32,6 +32,7 @@ + diff --git a/P5/Source/Specs/cl.xml b/P5/Source/Specs/cl.xml index 2b5d42838a..587094ba24 100644 --- a/P5/Source/Specs/cl.xml +++ b/P5/Source/Specs/cl.xml @@ -21,6 +21,7 @@ + diff --git a/P5/Source/Specs/climate.xml b/P5/Source/Specs/climate.xml index 28422e2901..03c67acf3e 100644 --- a/P5/Source/Specs/climate.xml +++ b/P5/Source/Specs/climate.xml @@ -18,6 +18,7 @@ + diff --git a/P5/Source/Specs/closer.xml b/P5/Source/Specs/closer.xml index 7cf7854dc8..302d389613 100644 --- a/P5/Source/Specs/closer.xml +++ b/P5/Source/Specs/closer.xml @@ -24,6 +24,7 @@ aparecen en la última sección al final de una división, especialmente en una + diff --git a/P5/Source/Specs/corr.xml b/P5/Source/Specs/corr.xml index 6625d423f2..8c77067379 100644 --- a/P5/Source/Specs/corr.xml +++ b/P5/Source/Specs/corr.xml @@ -22,6 +22,7 @@ + diff --git a/P5/Source/Specs/country.xml b/P5/Source/Specs/country.xml index 54940fbeee..a5d82b5797 100644 --- a/P5/Source/Specs/country.xml +++ b/P5/Source/Specs/country.xml @@ -25,6 +25,7 @@ + diff --git a/P5/Source/Specs/date.xml b/P5/Source/Specs/date.xml index 709566274b..0e3b905fcb 100644 --- a/P5/Source/Specs/date.xml +++ b/P5/Source/Specs/date.xml @@ -24,6 +24,7 @@ + diff --git a/P5/Source/Specs/dateline.xml b/P5/Source/Specs/dateline.xml index 40f6626e0e..18a60f4e8d 100644 --- a/P5/Source/Specs/dateline.xml +++ b/P5/Source/Specs/dateline.xml @@ -26,6 +26,7 @@ + + diff --git a/P5/Source/Specs/listEvent.xml b/P5/Source/Specs/listEvent.xml index 9b82a6b07d..5bda7a3425 100644 --- a/P5/Source/Specs/listEvent.xml +++ b/P5/Source/Specs/listEvent.xml @@ -15,6 +15,7 @@ + diff --git a/P5/Source/Specs/listNym.xml b/P5/Source/Specs/listNym.xml index d4d5b53c20..da5d7390d5 100644 --- a/P5/Source/Specs/listNym.xml +++ b/P5/Source/Specs/listNym.xml @@ -20,6 +20,7 @@ + diff --git a/P5/Source/Specs/listObject.xml b/P5/Source/Specs/listObject.xml index 3fba9dd5e0..6cb154da51 100644 --- a/P5/Source/Specs/listObject.xml +++ b/P5/Source/Specs/listObject.xml @@ -16,6 +16,7 @@ + diff --git a/P5/Source/Specs/listOrg.xml b/P5/Source/Specs/listOrg.xml index 35d0dc7d76..180007e8cc 100644 --- a/P5/Source/Specs/listOrg.xml +++ b/P5/Source/Specs/listOrg.xml @@ -24,6 +24,7 @@ + diff --git a/P5/Source/Specs/listPerson.xml b/P5/Source/Specs/listPerson.xml index fa5d589253..6f8933ee6e 100644 --- a/P5/Source/Specs/listPerson.xml +++ b/P5/Source/Specs/listPerson.xml @@ -33,6 +33,7 @@ + diff --git a/P5/Source/Specs/listPlace.xml b/P5/Source/Specs/listPlace.xml index 67e5dca76a..aff7a1d57a 100644 --- a/P5/Source/Specs/listPlace.xml +++ b/P5/Source/Specs/listPlace.xml @@ -25,6 +25,7 @@ + diff --git a/P5/Source/Specs/listRelation.xml b/P5/Source/Specs/listRelation.xml index d1510dbe9f..3c1a36d775 100644 --- a/P5/Source/Specs/listRelation.xml +++ b/P5/Source/Specs/listRelation.xml @@ -22,6 +22,7 @@ + diff --git a/P5/Source/Specs/location.xml b/P5/Source/Specs/location.xml index 10d9caaad7..8a97bc6322 100644 --- a/P5/Source/Specs/location.xml +++ b/P5/Source/Specs/location.xml @@ -19,6 +19,7 @@ + diff --git a/P5/Source/Specs/m.xml b/P5/Source/Specs/m.xml index acf7cf9e38..89b603d836 100644 --- a/P5/Source/Specs/m.xml +++ b/P5/Source/Specs/m.xml @@ -21,6 +21,7 @@ + diff --git a/P5/Source/Specs/macro.specialPara.cmc.xml b/P5/Source/Specs/macro.specialPara.cmc.xml new file mode 100644 index 0000000000..25436043f2 --- /dev/null +++ b/P5/Source/Specs/macro.specialPara.cmc.xml @@ -0,0 +1,29 @@ + + + + + 'special' + paragraph content with added CMC element(s) + defines the + content model of the quote element, whose content + is just like others (such as notes or list items) which + either contain a series of component-level elements or else + have the same structure as a paragraph, containing a series + of phrase-level and inter-level elements, but also contains + element(s) for transcription of CMC. + + + + + + + + + + + + \ No newline at end of file diff --git a/P5/Source/Specs/measure.xml b/P5/Source/Specs/measure.xml index 78f8d26b9a..df8cf1e651 100644 --- a/P5/Source/Specs/measure.xml +++ b/P5/Source/Specs/measure.xml @@ -24,6 +24,7 @@ + diff --git a/P5/Source/Specs/measureGrp.xml b/P5/Source/Specs/measureGrp.xml index 764e9feb13..f88de771e7 100644 --- a/P5/Source/Specs/measureGrp.xml +++ b/P5/Source/Specs/measureGrp.xml @@ -24,6 +24,7 @@ + diff --git a/P5/Source/Specs/media.xml b/P5/Source/Specs/media.xml index 79b94f79a9..af44d3a9a2 100644 --- a/P5/Source/Specs/media.xml +++ b/P5/Source/Specs/media.xml @@ -13,6 +13,7 @@ + diff --git a/P5/Source/Specs/meeting.xml b/P5/Source/Specs/meeting.xml index 882c6cf57e..c398fb4cdf 100644 --- a/P5/Source/Specs/meeting.xml +++ b/P5/Source/Specs/meeting.xml @@ -22,6 +22,7 @@ + diff --git a/P5/Source/Specs/mentioned.xml b/P5/Source/Specs/mentioned.xml index 102bff58cb..9594dc4b47 100644 --- a/P5/Source/Specs/mentioned.xml +++ b/P5/Source/Specs/mentioned.xml @@ -15,6 +15,7 @@ + diff --git a/P5/Source/Specs/milestone.xml b/P5/Source/Specs/milestone.xml index 1a70a9ee47..00b317d738 100644 --- a/P5/Source/Specs/milestone.xml +++ b/P5/Source/Specs/milestone.xml @@ -34,6 +34,7 @@ + + + + includes the CMC-specific element post and + makes it available on the divPart level. This allows for + using (and combining) occurrences of post, + u, incident, and kinesic in one + and the same div in order to be able to represent + the combined use of written and spoken posts, utterances, + and nonverbal acts on the GUI of multimodal CMC + environments. + + + + diff --git a/P5/Source/Specs/name.xml b/P5/Source/Specs/name.xml index e9dd5e286a..c9f8567c19 100644 --- a/P5/Source/Specs/name.xml +++ b/P5/Source/Specs/name.xml @@ -24,6 +24,7 @@ + diff --git a/P5/Source/Specs/nameLink.xml b/P5/Source/Specs/nameLink.xml index 8e1ddc0eba..75b0c2d56f 100644 --- a/P5/Source/Specs/nameLink.xml +++ b/P5/Source/Specs/nameLink.xml @@ -21,6 +21,7 @@ + diff --git a/P5/Source/Specs/notatedMusic.xml b/P5/Source/Specs/notatedMusic.xml index a3f3851d1a..c73e464de4 100644 --- a/P5/Source/Specs/notatedMusic.xml +++ b/P5/Source/Specs/notatedMusic.xml @@ -8,6 +8,7 @@ + diff --git a/P5/Source/Specs/note.xml b/P5/Source/Specs/note.xml index a880eafaae..344a53a8f4 100644 --- a/P5/Source/Specs/note.xml +++ b/P5/Source/Specs/note.xml @@ -24,6 +24,7 @@ + diff --git a/P5/Source/Specs/noteGrp.xml b/P5/Source/Specs/noteGrp.xml index 8aa224f178..bf93865b72 100644 --- a/P5/Source/Specs/noteGrp.xml +++ b/P5/Source/Specs/noteGrp.xml @@ -14,6 +14,7 @@ + diff --git a/P5/Source/Specs/num.xml b/P5/Source/Specs/num.xml index 06c2701efe..de0480b0ec 100644 --- a/P5/Source/Specs/num.xml +++ b/P5/Source/Specs/num.xml @@ -22,6 +22,7 @@ + diff --git a/P5/Source/Specs/objectName.xml b/P5/Source/Specs/objectName.xml index b81d46a684..6ca1d33a6e 100644 --- a/P5/Source/Specs/objectName.xml +++ b/P5/Source/Specs/objectName.xml @@ -12,6 +12,7 @@ + diff --git a/P5/Source/Specs/offset.xml b/P5/Source/Specs/offset.xml index 568ae446ed..430ec7fe63 100644 --- a/P5/Source/Specs/offset.xml +++ b/P5/Source/Specs/offset.xml @@ -21,7 +21,8 @@ - + + diff --git a/P5/Source/Specs/opener.xml b/P5/Source/Specs/opener.xml index ff5e5039da..0e49ba6bbd 100644 --- a/P5/Source/Specs/opener.xml +++ b/P5/Source/Specs/opener.xml @@ -26,6 +26,7 @@ + diff --git a/P5/Source/Specs/orgName.xml b/P5/Source/Specs/orgName.xml index 53fdb586d7..7c8016e5be 100644 --- a/P5/Source/Specs/orgName.xml +++ b/P5/Source/Specs/orgName.xml @@ -21,6 +21,7 @@ + diff --git a/P5/Source/Specs/orig.xml b/P5/Source/Specs/orig.xml index d418ce08bd..ed3baeac32 100644 --- a/P5/Source/Specs/orig.xml +++ b/P5/Source/Specs/orig.xml @@ -25,6 +25,7 @@ + + + + a written (or spoken) contribution to an ongoing + CMC interaction which has been composed (or recorded) by its author in its entirety as part + of a private activity, and has been transmitted through the internet and is made available + on the monitor or screen of the other parties en bloc. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + written or spoken mode + + + + + + for stretches of text and/or multimodal elements + + + for audio posts + + + +

This attribute is intended to convey information about the CMC environment in + which the post was created, as opposed to the MIME type of the content conveyed, + which is indicated by the elements contained within the post.

+ + + + indicates to which previous post the + current post replies or refers to. This attribute should be used to encode + "technical" reply information, i.e. which is due to a formal reply action (such as + activating a "reply" button in the client software) and which is also formally + represented in the source, e.g. in the "references" field of a Usenet message header + or in the subject line of a forum post. It should rather not be used for inferred, + or interpreted reply relations such as based on linguistic discourse markers, nor + for the indentation relations in Wiki talk pages. + + + + + + + marks the level of indentation of the + current post in a thread-like structure (as defined by its author and in relation to + the standard level of indentation which should be encoded as indentLevel="0"). + Basically used for Wiki talk pages, but may and should also be used for genres such + as webblog comments when the source was HTML. + + + + + + + + +

standard user postings in chat

+ + +

oh ja, in die Wärme...

+ + +

nein, hast du nicht !!

+ + + + +

chat message-type "system": user enters a chatroom, "system" defined in listPerson

+ + + + system + + + + + +

+ Interseb betritt den Raum.

+ + + + +

action message in chat

+ + +

+ McMike hechtet zum Steuer

+ + + + +

chat messages incl. interaction words (types: inflective and acronym) and an interaction + phrase

+ + +

+ *schwank* + + *seekrank* +

+ + + +

+ *lol* [...]

+ + + +

+ *McMike einen fallschirm umbind* +

+ + + + +

user posting incl. an emoticon

+ + +

naja, der war gestrandet :( +

+ + + + +

Twitter: Tweet containing an addressing term and a hashtag expression

+ + +

+ + @textarchiv Erfurter + Europäische Welt- und Staats-Geschichte: 20 Ausgaben von 1744 aus dem MKHZ + bereits in DTAQ + http://www.deutschestextarchiv.de/dtaq/about + #dtaclarin14 +

+ + + + +

example from Wikipedia discussion

+ + +

Wie du siehst hab ich die Lemma geändert, danke für den Hinweis, ich war nämlich + selbst auch etwas unsicher bei der ganzen Sache und bin jetzt damit auch viel + glücklicher!--

+ + + + + + +

Blog comment: Die Anthropodizee-Frage. Wer den Himmel leerräumt, schafft die Menschheit + ab. by Volker Birk. + https://scilogs.spektrum.de/natur-des-glaubens/die-anthropodizee-frage-wer-himmel/#comment-31899

+ + + +

“Wenn Sie diesen Gruppen also “mangelnde Bildung“ attestieren wollen, so + verwenden Sie bereits einen bestimmten, kulturgebundenen Bildungsbegriff.”

+

Ich hoffe doch, wir können beim Bildungsbegriff der Aufklärung bleiben. Wer das + nicht möchte, hat die Wissenschaft verlassen.

 + + + +

Even though in some CMC genres (e.g., WhatsApp), the other parties are informed by an + automated alert about the fact that another party is currently composing a new post, + they cannot track the process of verbalization, i.e. how the written utterance emerges + in the entry form on the user interface of its author. It is not until the author + performs a ‘posting’ action (e.g., by hitting the ‘enter’ key or by activating a ‘send’ + button with the mouse) that the result of the composition process — the post — is made + available for the other parties. From the perspective of its addressees/readers, a post + is a stretch of text that has been composed in advance. Different from spoken utterances + but similar to edited text, (1) the reader of a post does not have access to the + verbalization process and (2) the mental processing of a post is not possible until the + process of verbalization (the composition) has been finished and the posting action has + been performed by the author. Posts occur in a broad range of written CMC genres: as + user ‘messages’ in chats and WhatsApp dialogues, as SMS messages, as tweets in Twitter + timelines, as individual comments following a status update on Facebook pages, as posts + in forum threads, as contributions on Wikipedia talk pages or in the comments section of + a weblog. [Element adopted from the DeRiK schema. + Aspects of the model adopted from the CoMeRe Schema]. The + post element is a member of the model class model.common (via model.CMC). + This allows for using (and combining) occurrences of post, u, + incident, and kinesicin one and the same div in order to + be able to represent the combined use of written and spoken utterances and nonverbal + acts on the GUI of multimodal CMC environments.

+

The use of the modality attribute is + recommended, but not required. Its value is either + written or spoken. Because spoken + language differs fundamentally from written language, when + the value is spoken projects may wish to limit + the content of the post to character data and + only those elements available in the u element, + thus avoiding elements like p or head + that are used for the encoding of written text.

+ + + + + + diff --git a/P5/Source/Specs/postscript.xml b/P5/Source/Specs/postscript.xml index 5ff28a29a5..ee1fc613e3 100644 --- a/P5/Source/Specs/postscript.xml +++ b/P5/Source/Specs/postscript.xml @@ -14,6 +14,7 @@ lettre. + diff --git a/P5/Source/Specs/ptr.xml b/P5/Source/Specs/ptr.xml index d04b16f53b..c0531b5a89 100644 --- a/P5/Source/Specs/ptr.xml +++ b/P5/Source/Specs/ptr.xml @@ -24,6 +24,7 @@ + diff --git a/P5/Source/Specs/q.xml b/P5/Source/Specs/q.xml index 5e930fc498..2298158d02 100644 --- a/P5/Source/Specs/q.xml +++ b/P5/Source/Specs/q.xml @@ -43,6 +43,7 @@ + diff --git a/P5/Source/Specs/quote.xml b/P5/Source/Specs/quote.xml index 4efc5359d8..5ff8e4c031 100644 --- a/P5/Source/Specs/quote.xml +++ b/P5/Source/Specs/quote.xml @@ -26,6 +26,7 @@ + diff --git a/P5/Source/Specs/ref.xml b/P5/Source/Specs/ref.xml index 736e9099d5..d8c79c3ac4 100644 --- a/P5/Source/Specs/ref.xml +++ b/P5/Source/Specs/ref.xml @@ -28,6 +28,7 @@ + diff --git a/P5/Source/Specs/reg.xml b/P5/Source/Specs/reg.xml index a9d7df25cb..4d3726f988 100644 --- a/P5/Source/Specs/reg.xml +++ b/P5/Source/Specs/reg.xml @@ -27,6 +27,7 @@ + + - @@ -41,9 +42,9 @@ - - - + + + diff --git a/P5/p5odds.odd b/P5/p5odds.odd index 1b7af79fb8..191ef8224f 100644 --- a/P5/p5odds.odd +++ b/P5/p5odds.odd @@ -625,10 +625,12 @@ $Id$ + + diff --git a/P5/spec_lists.json b/P5/spec_lists.json index feacc562e9..8922cf27a8 100644 --- a/P5/spec_lists.json +++ b/P5/spec_lists.json @@ -1 +1 @@ -{"elements":[{"id":"teiHeader","URL":"teiHeader.xml","de":{"out-of-date":true,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"fileDesc","URL":"fileDesc.xml","de":{"out-of-date":true,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"titleStmt","URL":"titleStmt.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"sponsor","URL":"sponsor.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"funder","URL":"funder.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"principal","URL":"principal.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"editionStmt","URL":"editionStmt.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"edition","URL":"edition.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"extent","URL":"extent.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"publicationStmt","URL":"publicationStmt.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"distributor","URL":"distributor.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"authority","URL":"authority.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"idno","URL":"idno.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"availability","URL":"availability.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"licence","URL":"licence.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"seriesStmt","URL":"seriesStmt.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"notesStmt","URL":"notesStmt.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"sourceDesc","URL":"sourceDesc.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"biblFull","URL":"biblFull.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"encodingDesc","URL":"encodingDesc.xml","de":{"out-of-date":true,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"schemaRef","URL":"schemaRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"projectDesc","URL":"projectDesc.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"samplingDecl","URL":"samplingDecl.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"editorialDecl","URL":"editorialDecl.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"correction","URL":"correction.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"normalization","URL":"normalization.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"quotation","URL":"quotation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"hyphenation","URL":"hyphenation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"segmentation","URL":"segmentation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"stdVals","URL":"stdVals.xml","de":{"out-of-date":true,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"interpretation","URL":"interpretation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"punctuation","URL":"punctuation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"tagsDecl","URL":"tagsDecl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"tagUsage","URL":"tagUsage.xml","de":{"out-of-date":true,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"namespace","URL":"namespace.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"rendition","URL":"rendition.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"styleDefDecl","URL":"styleDefDecl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"refsDecl","URL":"refsDecl.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"citeStructure","URL":"citeStructure.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"citeData","URL":"citeData.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"cRefPattern","URL":"cRefPattern.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"prefixDef","URL":"prefixDef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listPrefixDef","URL":"listPrefixDef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"refState","URL":"refState.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"classDecl","URL":"classDecl.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"taxonomy","URL":"taxonomy.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"category","URL":"category.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"catDesc","URL":"catDesc.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"geoDecl","URL":"geoDecl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"unitDecl","URL":"unitDecl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"unitDef","URL":"unitDef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"conversion","URL":"conversion.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"appInfo","URL":"appInfo.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"application","URL":"application.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"profileDesc","URL":"profileDesc.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"handNote","URL":"handNote.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"abstract","URL":"abstract.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"creation","URL":"creation.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"langUsage","URL":"langUsage.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"language","URL":"language.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"textClass","URL":"textClass.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"keywords","URL":"keywords.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"classCode","URL":"classCode.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"catRef","URL":"catRef.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"calendarDesc","URL":"calendarDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"calendar","URL":"calendar.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"correspDesc","URL":"correspDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"correspAction","URL":"correspAction.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"correspContext","URL":"correspContext.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"xenoData","URL":"xenoData.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"revisionDesc","URL":"revisionDesc.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"change","URL":"change.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"p","URL":"p.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"foreign","URL":"foreign.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"emph","URL":"emph.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"hi","URL":"hi.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"distinct","URL":"distinct.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"said","URL":"said.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"quote","URL":"quote.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"q","URL":"q.xml","de":{"out-of-date":true,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"cit","URL":"cit.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"mentioned","URL":"mentioned.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"soCalled","URL":"soCalled.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"desc","URL":"desc.xml","de":{"out-of-date":true,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"gloss","URL":"gloss.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"term","URL":"term.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"ruby","URL":"ruby.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"rb","URL":"rb.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"rt","URL":"rt.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"sic","URL":"sic.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"corr","URL":"corr.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"choice","URL":"choice.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"reg","URL":"reg.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"orig","URL":"orig.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"gap","URL":"gap.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"ellipsis","URL":"ellipsis.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"add","URL":"add.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"del","URL":"del.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"unclear","URL":"unclear.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"name","URL":"name.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"rs","URL":"rs.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"email","URL":"email.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"address","URL":"address.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"addrLine","URL":"addrLine.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"street","URL":"street.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"postCode","URL":"postCode.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"postBox","URL":"postBox.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"num","URL":"num.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"measure","URL":"measure.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"measureGrp","URL":"measureGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"unit","URL":"unit.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"date","URL":"date.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"time","URL":"time.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"abbr","URL":"abbr.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"expan","URL":"expan.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"ptr","URL":"ptr.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"ref","URL":"ref.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"list","URL":"list.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"item","URL":"item.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"label","URL":"label.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"head","URL":"head.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"headLabel","URL":"headLabel.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"headItem","URL":"headItem.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"note","URL":"note.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"noteGrp","URL":"noteGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"index","URL":"index.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"media","URL":"media.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"graphic","URL":"graphic.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"binaryObject","URL":"binaryObject.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"milestone","URL":"milestone.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"gb","URL":"gb.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"pb","URL":"pb.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"lb","URL":"lb.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"cb","URL":"cb.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"analytic","URL":"analytic.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"monogr","URL":"monogr.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"series","URL":"series.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"author","URL":"author.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"editor","URL":"editor.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"respStmt","URL":"respStmt.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"resp","URL":"resp.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"title","URL":"title.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"meeting","URL":"meeting.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"imprint","URL":"imprint.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"publisher","URL":"publisher.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"biblScope","URL":"biblScope.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"citedRange","URL":"citedRange.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"pubPlace","URL":"pubPlace.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"bibl","URL":"bibl.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"biblStruct","URL":"biblStruct.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"listBibl","URL":"listBibl.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"relatedItem","URL":"relatedItem.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"l","URL":"l.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"lg","URL":"lg.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"sp","URL":"sp.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"speaker","URL":"speaker.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"stage","URL":"stage.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"TEI","URL":"TEI.xml","de":{"out-of-date":true,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teiCorpus","URL":"teiCorpus.xml","de":{"out-of-date":true,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"text","URL":"text.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"body","URL":"body.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"group","URL":"group.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"floatingText","URL":"floatingText.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"div","URL":"div.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"div1","URL":"div1.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"div2","URL":"div2.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"div3","URL":"div3.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"div4","URL":"div4.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"div5","URL":"div5.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"div6","URL":"div6.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"div7","URL":"div7.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"divGen","URL":"divGen.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"trailer","URL":"trailer.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"byline","URL":"byline.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"dateline","URL":"dateline.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"argument","URL":"argument.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"epigraph","URL":"epigraph.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"opener","URL":"opener.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"closer","URL":"closer.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"salute","URL":"salute.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"signed","URL":"signed.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"postscript","URL":"postscript.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"titlePage","URL":"titlePage.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"docTitle","URL":"docTitle.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"titlePart","URL":"titlePart.xml","de":{"out-of-date":true,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"docAuthor","URL":"docAuthor.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"imprimatur","URL":"imprimatur.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"docEdition","URL":"docEdition.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"docImprint","URL":"docImprint.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"docDate","URL":"docDate.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"front","URL":"front.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"back","URL":"back.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"g","URL":"g.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"charDecl","URL":"charDecl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"char","URL":"char.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"glyph","URL":"glyph.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"localProp","URL":"localProp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"mapping","URL":"mapping.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"unihanProp","URL":"unihanProp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"unicodeProp","URL":"unicodeProp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"metDecl","URL":"metDecl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"metSym","URL":"metSym.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"caesura","URL":"caesura.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"rhyme","URL":"rhyme.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"set","URL":"set.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"prologue","URL":"prologue.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"epilogue","URL":"epilogue.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"performance","URL":"performance.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"castList","URL":"castList.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"castGroup","URL":"castGroup.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"castItem","URL":"castItem.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"role","URL":"role.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"roleDesc","URL":"roleDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"actor","URL":"actor.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"spGrp","URL":"spGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"move","URL":"move.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"view","URL":"view.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"camera","URL":"camera.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"sound","URL":"sound.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"caption","URL":"caption.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"tech","URL":"tech.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"scriptStmt","URL":"scriptStmt.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"recordingStmt","URL":"recordingStmt.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"recording","URL":"recording.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"equipment","URL":"equipment.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"broadcast","URL":"broadcast.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"transcriptionDesc","URL":"transcriptionDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"u","URL":"u.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"pause","URL":"pause.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"vocal","URL":"vocal.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"kinesic","URL":"kinesic.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"incident","URL":"incident.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"writing","URL":"writing.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"shift","URL":"shift.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"annotationBlock","URL":"annotationBlock.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"superEntry","URL":"superEntry.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"entry","URL":"entry.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"entryFree","URL":"entryFree.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"hom","URL":"hom.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"sense","URL":"sense.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"dictScrap","URL":"dictScrap.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"form","URL":"form.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"orth","URL":"orth.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"pron","URL":"pron.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"hyph","URL":"hyph.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"syll","URL":"syll.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"stress","URL":"stress.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"gram","URL":"gram.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"gen","URL":"gen.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"number","URL":"number.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"case","URL":"case.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"per","URL":"per.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"tns","URL":"tns.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"mood","URL":"mood.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"iType","URL":"iType.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"gramGrp","URL":"gramGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"pos","URL":"pos.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"subc","URL":"subc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"colloc","URL":"colloc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"def","URL":"def.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"etym","URL":"etym.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"lang","URL":"lang.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"usg","URL":"usg.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"lbl","URL":"lbl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"xr","URL":"xr.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"re","URL":"re.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"oRef","URL":"oRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"pRef","URL":"pRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"msDesc","URL":"msDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"catchwords","URL":"catchwords.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"dimensions","URL":"dimensions.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"dim","URL":"dim.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"height","URL":"height.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"depth","URL":"depth.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"width","URL":"width.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"heraldry","URL":"heraldry.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"locus","URL":"locus.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"locusGrp","URL":"locusGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"material","URL":"material.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"objectType","URL":"objectType.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"origDate","URL":"origDate.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"origPlace","URL":"origPlace.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"secFol","URL":"secFol.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"signatures","URL":"signatures.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"stamp","URL":"stamp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"watermark","URL":"watermark.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"msIdentifier","URL":"msIdentifier.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"institution","URL":"institution.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"repository","URL":"repository.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"collection","URL":"collection.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"altIdentifier","URL":"altIdentifier.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"msName","URL":"msName.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"colophon","URL":"colophon.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"explicit","URL":"explicit.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"filiation","URL":"filiation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"finalRubric","URL":"finalRubric.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"incipit","URL":"incipit.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"msContents","URL":"msContents.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"msItem","URL":"msItem.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"msItemStruct","URL":"msItemStruct.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"rubric","URL":"rubric.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"summary","URL":"summary.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"textLang","URL":"textLang.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"physDesc","URL":"physDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"objectDesc","URL":"objectDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"supportDesc","URL":"supportDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"support","URL":"support.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"collation","URL":"collation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"foliation","URL":"foliation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"condition","URL":"condition.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"layoutDesc","URL":"layoutDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"layout","URL":"layout.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"handDesc","URL":"handDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"typeDesc","URL":"typeDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"typeNote","URL":"typeNote.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"scriptDesc","URL":"scriptDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"scriptNote","URL":"scriptNote.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"musicNotation","URL":"musicNotation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"decoDesc","URL":"decoDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"decoNote","URL":"decoNote.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"additions","URL":"additions.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"bindingDesc","URL":"bindingDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"binding","URL":"binding.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"sealDesc","URL":"sealDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"seal","URL":"seal.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"accMat","URL":"accMat.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"history","URL":"history.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"origin","URL":"origin.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"provenance","URL":"provenance.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"acquisition","URL":"acquisition.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"additional","URL":"additional.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"adminInfo","URL":"adminInfo.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"recordHist","URL":"recordHist.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"source","URL":"source.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"custodialHist","URL":"custodialHist.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"custEvent","URL":"custEvent.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"surrogates","URL":"surrogates.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"msPart","URL":"msPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"msFrag","URL":"msFrag.xml","de":{"out-of-date":true,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"facsimile","URL":"facsimile.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"sourceDoc","URL":"sourceDoc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"surface","URL":"surface.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"surfaceGrp","URL":"surfaceGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"zone","URL":"zone.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"path","URL":"path.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"addSpan","URL":"addSpan.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"damage","URL":"damage.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"damageSpan","URL":"damageSpan.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"delSpan","URL":"delSpan.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"ex","URL":"ex.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"fw","URL":"fw.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"handNotes","URL":"handNotes.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"handShift","URL":"handShift.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"am","URL":"am.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"restore","URL":"restore.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"space","URL":"space.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"subst","URL":"subst.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"substJoin","URL":"substJoin.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"supplied","URL":"supplied.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"surplus","URL":"surplus.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"secl","URL":"secl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"line","URL":"line.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listChange","URL":"listChange.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listTranspose","URL":"listTranspose.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"metamark","URL":"metamark.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"mod","URL":"mod.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"redo","URL":"redo.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"retrace","URL":"retrace.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"transpose","URL":"transpose.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"undo","URL":"undo.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"app","URL":"app.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"listApp","URL":"listApp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"lem","URL":"lem.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"rdg","URL":"rdg.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"rdgGrp","URL":"rdgGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"witDetail","URL":"witDetail.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"wit","URL":"wit.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listWit","URL":"listWit.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"witness","URL":"witness.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"witStart","URL":"witStart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"witEnd","URL":"witEnd.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"lacunaStart","URL":"lacunaStart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"lacunaEnd","URL":"lacunaEnd.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"variantEncoding","URL":"variantEncoding.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"orgName","URL":"orgName.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"persName","URL":"persName.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"surname","URL":"surname.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"forename","URL":"forename.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"genName","URL":"genName.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"nameLink","URL":"nameLink.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"addName","URL":"addName.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"roleName","URL":"roleName.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"placeName","URL":"placeName.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"bloc","URL":"bloc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"country","URL":"country.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"region","URL":"region.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"settlement","URL":"settlement.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"district","URL":"district.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"offset","URL":"offset.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"geogName","URL":"geogName.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"geogFeat","URL":"geogFeat.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"affiliation","URL":"affiliation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"age","URL":"age.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"birth","URL":"birth.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"climate","URL":"climate.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"death","URL":"death.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"education","URL":"education.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"event","URL":"event.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"faith","URL":"faith.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"floruit","URL":"floruit.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"gender","URL":"gender.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"geo","URL":"geo.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"langKnowledge","URL":"langKnowledge.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"langKnown","URL":"langKnown.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"listOrg","URL":"listOrg.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listEvent","URL":"listEvent.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listPerson","URL":"listPerson.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listPlace","URL":"listPlace.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listRelation","URL":"listRelation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"location","URL":"location.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"nationality","URL":"nationality.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"occupation","URL":"occupation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"org","URL":"org.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"person","URL":"person.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"persona","URL":"persona.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"personGrp","URL":"personGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"persPronouns","URL":"persPronouns.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"place","URL":"place.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"population","URL":"population.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"relation","URL":"relation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"residence","URL":"residence.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"sex","URL":"sex.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"socecStatus","URL":"socecStatus.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"state","URL":"state.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"terrain","URL":"terrain.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"trait","URL":"trait.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"objectName","URL":"objectName.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"object","URL":"object.xml","de":{"out-of-date":true,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listObject","URL":"listObject.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"objectIdentifier","URL":"objectIdentifier.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"nym","URL":"nym.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"listNym","URL":"listNym.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"table","URL":"table.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"row","URL":"row.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"cell","URL":"cell.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"formula","URL":"formula.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"notatedMusic","URL":"notatedMusic.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"figure","URL":"figure.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"figDesc","URL":"figDesc.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"textDesc","URL":"textDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"particDesc","URL":"particDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"settingDesc","URL":"settingDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"channel","URL":"channel.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"constitution","URL":"constitution.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"derivation","URL":"derivation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"domain","URL":"domain.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"factuality","URL":"factuality.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"interaction","URL":"interaction.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"preparedness","URL":"preparedness.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"purpose","URL":"purpose.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"setting","URL":"setting.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"locale","URL":"locale.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"activity","URL":"activity.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"link","URL":"link.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"linkGrp","URL":"linkGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"ab","URL":"ab.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"anchor","URL":"anchor.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"seg","URL":"seg.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"when","URL":"when.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"timeline","URL":"timeline.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"join","URL":"join.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"joinGrp","URL":"joinGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"alt","URL":"alt.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"altGrp","URL":"altGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"standOff","URL":"standOff.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listAnnotation","URL":"listAnnotation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"annotation","URL":"annotation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"s","URL":"s.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"cl","URL":"cl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"phr","URL":"phr.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"w","URL":"w.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"m","URL":"m.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"c","URL":"c.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"pc","URL":"pc.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"span","URL":"span.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"spanGrp","URL":"spanGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"interp","URL":"interp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"interpGrp","URL":"interpGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"fsdDecl","URL":"fsdDecl.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"fsDecl","URL":"fsDecl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"fsDescr","URL":"fsDescr.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"fsdLink","URL":"fsdLink.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"fDecl","URL":"fDecl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"fDescr","URL":"fDescr.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"vRange","URL":"vRange.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"vDefault","URL":"vDefault.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"if","URL":"if.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"then","URL":"then.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"fsConstraints","URL":"fsConstraints.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"cond","URL":"cond.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"bicond","URL":"bicond.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"iff","URL":"iff.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"fs","URL":"fs.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"f","URL":"f.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"binary","URL":"binary.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"symbol","URL":"symbol.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"numeric","URL":"numeric.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"string","URL":"string.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"vLabel","URL":"vLabel.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"vColl","URL":"vColl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"default","URL":"default.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"vAlt","URL":"vAlt.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"vNot","URL":"vNot.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"vMerge","URL":"vMerge.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"fLib","URL":"fLib.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"fvLib","URL":"fvLib.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"graph","URL":"graph.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"node","URL":"node.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"arc","URL":"arc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"tree","URL":"tree.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"root","URL":"root.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"iNode","URL":"iNode.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"leaf","URL":"leaf.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"eTree","URL":"eTree.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"triangle","URL":"triangle.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"eLeaf","URL":"eLeaf.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"forest","URL":"forest.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listForest","URL":"listForest.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"precision","URL":"precision.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"certainty","URL":"certainty.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"respons","URL":"respons.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att","URL":"att.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"code","URL":"code.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"eg","URL":"eg.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"egXML","URL":"egXML.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"gi","URL":"gi.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"ident","URL":"ident.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"tag","URL":"tag.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"val","URL":"val.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"specList","URL":"specList.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"specDesc","URL":"specDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"classRef","URL":"classRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"elementRef","URL":"elementRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"macroRef","URL":"macroRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"moduleRef","URL":"moduleRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"moduleSpec","URL":"moduleSpec.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"schemaSpec","URL":"schemaSpec.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"specGrp","URL":"specGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"specGrpRef","URL":"specGrpRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"elementSpec","URL":"elementSpec.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"classSpec","URL":"classSpec.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"dataSpec","URL":"dataSpec.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"macroSpec","URL":"macroSpec.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"remarks","URL":"remarks.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listRef","URL":"listRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"exemplum","URL":"exemplum.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"classes","URL":"classes.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"memberOf","URL":"memberOf.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"equiv","URL":"equiv.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"altIdent","URL":"altIdent.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model","URL":"model.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"modelSequence","URL":"modelSequence.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"modelGrp","URL":"modelGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"outputRendition","URL":"outputRendition.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"paramList","URL":"paramList.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"paramSpec","URL":"paramSpec.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"param","URL":"param.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"content","URL":"content.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"sequence","URL":"sequence.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"alternate","URL":"alternate.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"constraint","URL":"constraint.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"constraintSpec","URL":"constraintSpec.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"attList","URL":"attList.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"attDef","URL":"attDef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"attRef","URL":"attRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"datatype","URL":"datatype.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"dataRef","URL":"dataRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"dataFacet","URL":"dataFacet.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"defaultVal","URL":"defaultVal.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"valDesc","URL":"valDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"valItem","URL":"valItem.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"valList","URL":"valList.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"textNode","URL":"textNode.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"anyElement","URL":"anyElement.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"empty","URL":"empty.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}}],"att_classes":[{"id":"att.anchoring","URL":"att.anchoring.xml","de":{"out-of-date":true,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.ascribed","URL":"att.ascribed.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.ascribed.directed","URL":"att.ascribed.directed.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.canonical","URL":"att.canonical.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.ranging","URL":"att.ranging.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.dimensions","URL":"att.dimensions.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.written","URL":"att.written.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.damaged","URL":"att.damaged.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.breaking","URL":"att.breaking.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.cReferencing","URL":"att.cReferencing.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.datable.custom","URL":"att.datable.custom.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.datable.w3c","URL":"att.datable.w3c.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.datable","URL":"att.datable.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.datcat","URL":"att.datcat.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.declarable","URL":"att.declarable.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.declaring","URL":"att.declaring.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.fragmentable","URL":"att.fragmentable.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.divLike","URL":"att.divLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.docStatus","URL":"att.docStatus.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.duration.w3c","URL":"att.duration.w3c.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.duration","URL":"att.duration.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.global.responsibility","URL":"att.global.responsibility.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.editLike","URL":"att.editLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.global.rendition","URL":"att.global.rendition.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.global.source","URL":"att.global.source.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.global","URL":"att.global.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.handFeatures","URL":"att.handFeatures.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.internetMedia","URL":"att.internetMedia.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.media","URL":"att.media.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.resourced","URL":"att.resourced.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.interpLike","URL":"att.interpLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.measurement","URL":"att.measurement.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.milestoneUnit","URL":"att.milestoneUnit.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.naming","URL":"att.naming.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.notated","URL":"att.notated.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.placement","URL":"att.placement.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.typed","URL":"att.typed.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.pointing","URL":"att.pointing.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.pointing.group","URL":"att.pointing.group.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.scoping","URL":"att.scoping.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.segLike","URL":"att.segLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.sortable","URL":"att.sortable.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.edition","URL":"att.edition.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.spanning","URL":"att.spanning.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.styleDef","URL":"att.styleDef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.tableDecoration","URL":"att.tableDecoration.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.timed","URL":"att.timed.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.transcriptional","URL":"att.transcriptional.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.citing","URL":"att.citing.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.citeStructurePart","URL":"att.citeStructurePart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.patternReplacement","URL":"att.patternReplacement.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.formula","URL":"att.formula.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.locatable","URL":"att.locatable.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.gaijiProp","URL":"att.gaijiProp.xml","de":{"out-of-date":true,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.metrical","URL":"att.metrical.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.enjamb","URL":"att.enjamb.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.entryLike","URL":"att.entryLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.lexicographic","URL":"att.lexicographic.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.partials","URL":"att.partials.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.msExcerpt","URL":"att.msExcerpt.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.msClass","URL":"att.msClass.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.global.facs","URL":"att.global.facs.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.global.change","URL":"att.global.change.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.coordinated","URL":"att.coordinated.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.rdgPart","URL":"att.rdgPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.witnessed","URL":"att.witnessed.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.textCritical","URL":"att.textCritical.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.personal","URL":"att.personal.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.datable.iso","URL":"att.datable.iso.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.calendarSystem","URL":"att.calendarSystem.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.duration.iso","URL":"att.duration.iso.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.global.linking","URL":"att.global.linking.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.lexicographic.normalized","URL":"att.lexicographic.normalized.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.linguistic","URL":"att.linguistic.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.global.analytic","URL":"att.global.analytic.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.translatable","URL":"att.translatable.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.predicate","URL":"att.predicate.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.repeatable","URL":"att.repeatable.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.combinable","URL":"att.combinable.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.identified","URL":"att.identified.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"att.deprecated","URL":"att.deprecated.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.namespaceable","URL":"att.namespaceable.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}}],"model_classes":[{"id":"model.nameLike.agent","URL":"model.nameLike.agent.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.segLike","URL":"model.segLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.hiLike","URL":"model.hiLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.emphLike","URL":"model.emphLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.highlighted","URL":"model.highlighted.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.dateLike","URL":"model.dateLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.dimLike","URL":"model.dimLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.measureLike","URL":"model.measureLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.egLike","URL":"model.egLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.graphicLike","URL":"model.graphicLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.offsetLike","URL":"model.offsetLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.pPart.msdesc","URL":"model.pPart.msdesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.pPart.editorial","URL":"model.pPart.editorial.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.pPart.transcriptional","URL":"model.pPart.transcriptional.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.pPart.edit","URL":"model.pPart.edit.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.linePart","URL":"model.linePart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.ptrLike","URL":"model.ptrLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.lPart","URL":"model.lPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.global.meta","URL":"model.global.meta.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"model.milestoneLike","URL":"model.milestoneLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.gLike","URL":"model.gLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.oddDecl","URL":"model.oddDecl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.oddRef","URL":"model.oddRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.phrase.xml","URL":"model.phrase.xml.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.specDescLike","URL":"model.specDescLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.biblLike","URL":"model.biblLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.headLike","URL":"model.headLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.labelLike","URL":"model.labelLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.listLike","URL":"model.listLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.noteLike","URL":"model.noteLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.lLike","URL":"model.lLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.pLike","URL":"model.pLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.stageLike","URL":"model.stageLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"model.featureVal.complex","URL":"model.featureVal.complex.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.featureVal.single","URL":"model.featureVal.single.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.entryPart","URL":"model.entryPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.entryPart.top","URL":"model.entryPart.top.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"model.eventLike","URL":"model.eventLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.global.edit","URL":"model.global.edit.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.global.spoken","URL":"model.global.spoken.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.divPart","URL":"model.divPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"model.persStateLike","URL":"model.persStateLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"model.personLike","URL":"model.personLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.personPart","URL":"model.personPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.placeNamePart","URL":"model.placeNamePart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.placeStateLike","URL":"model.placeStateLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.orgPart","URL":"model.orgPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.publicationStmtPart.agency","URL":"model.publicationStmtPart.agency.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"model.publicationStmtPart.detail","URL":"model.publicationStmtPart.detail.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"model.availabilityPart","URL":"model.availabilityPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.certLike","URL":"model.certLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.descLike","URL":"model.descLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.identEquiv","URL":"model.identEquiv.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.identSynonyms","URL":"model.identSynonyms.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.quoteLike","URL":"model.quoteLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.attributable","URL":"model.attributable.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.rdgLike","URL":"model.rdgLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"model.respLike","URL":"model.respLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.divWrapper","URL":"model.divWrapper.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.divTopPart","URL":"model.divTopPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.divTop","URL":"model.divTop.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.frontPart.drama","URL":"model.frontPart.drama.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.pLike.front","URL":"model.pLike.front.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.divBottomPart","URL":"model.divBottomPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.divBottom","URL":"model.divBottom.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.titlepagePart","URL":"model.titlepagePart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.msQuoteLike","URL":"model.msQuoteLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.msItemPart","URL":"model.msItemPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.choicePart","URL":"model.choicePart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.recordingPart","URL":"model.recordingPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.imprintPart","URL":"model.imprintPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.catDescPart","URL":"model.catDescPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.settingPart","URL":"model.settingPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.textDescPart","URL":"model.textDescPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.castItemPart","URL":"model.castItemPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.physDescPart","URL":"model.physDescPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.addressLike","URL":"model.addressLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.nameLike","URL":"model.nameLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"model.persNamePart","URL":"model.persNamePart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.global","URL":"model.global.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.featureVal","URL":"model.featureVal.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.biblPart","URL":"model.biblPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.frontPart","URL":"model.frontPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.addrPart","URL":"model.addrPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.pPart.data","URL":"model.pPart.data.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.inter","URL":"model.inter.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.common","URL":"model.common.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.phrase","URL":"model.phrase.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"model.paraPart","URL":"model.paraPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.limitedPhrase","URL":"model.limitedPhrase.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.divLike","URL":"model.divLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.divGenLike","URL":"model.divGenLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.div1Like","URL":"model.div1Like.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.div2Like","URL":"model.div2Like.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.div3Like","URL":"model.div3Like.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.div4Like","URL":"model.div4Like.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.div5Like","URL":"model.div5Like.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.div6Like","URL":"model.div6Like.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.div7Like","URL":"model.div7Like.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.annotationLike","URL":"model.annotationLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.annotationPart.body","URL":"model.annotationPart.body.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.applicationLike","URL":"model.applicationLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.teiHeaderPart","URL":"model.teiHeaderPart.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.sourceDescPart","URL":"model.sourceDescPart.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.encodingDescPart","URL":"model.encodingDescPart.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.editorialDeclPart","URL":"model.editorialDeclPart.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.profileDescPart","URL":"model.profileDescPart.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.standOffPart","URL":"model.standOffPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.correspActionPart","URL":"model.correspActionPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.correspContextPart","URL":"model.correspContextPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.correspDescPart","URL":"model.correspDescPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.divPart.spoken","URL":"model.divPart.spoken.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"model.entryLike","URL":"model.entryLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.morphLike","URL":"model.morphLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.lexicalRefinement","URL":"model.lexicalRefinement.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.gramPart","URL":"model.gramPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.formPart","URL":"model.formPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.ptrLike.form","URL":"model.ptrLike.form.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.resource","URL":"model.resource.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.describedResource","URL":"model.describedResource.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.rdgPart","URL":"model.rdgPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.objectLike","URL":"model.objectLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.orgStateLike","URL":"model.orgStateLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.placeLike","URL":"model.placeLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.fsdDeclPart","URL":"model.fsdDeclPart.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.contentPart","URL":"model.contentPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}}],"macros":[{"id":"macro.abContent","URL":"macro.abContent.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"macro.paraContent","URL":"macro.paraContent.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"macro.limitedContent","URL":"macro.limitedContent.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"macro.phraseSeq","URL":"macro.phraseSeq.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"macro.phraseSeq.limited","URL":"macro.phraseSeq.limited.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"macro.specialPara","URL":"macro.specialPara.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"macro.xtext","URL":"macro.xtext.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}}],"datatypes":[{"id":"teidata.certainty","URL":"teidata.certainty.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.probability","URL":"teidata.probability.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.numeric","URL":"teidata.numeric.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.interval","URL":"teidata.interval.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.count","URL":"teidata.count.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.temporal.w3c","URL":"teidata.temporal.w3c.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.temporal.working","URL":"teidata.temporal.working.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.duration.w3c","URL":"teidata.duration.w3c.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.truthValue","URL":"teidata.truthValue.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.xTruthValue","URL":"teidata.xTruthValue.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.language","URL":"teidata.language.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.namespace","URL":"teidata.namespace.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.namespaceOrName","URL":"teidata.namespaceOrName.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.outputMeasurement","URL":"teidata.outputMeasurement.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.pattern","URL":"teidata.pattern.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.point","URL":"teidata.point.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.pointer","URL":"teidata.pointer.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.authority","URL":"teidata.authority.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.version","URL":"teidata.version.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.versionNumber","URL":"teidata.versionNumber.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.replacement","URL":"teidata.replacement.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.xpath","URL":"teidata.xpath.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.word","URL":"teidata.word.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.text","URL":"teidata.text.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.name","URL":"teidata.name.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.xmlName","URL":"teidata.xmlName.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.prefix","URL":"teidata.prefix.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.enumerated","URL":"teidata.enumerated.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.gender","URL":"teidata.gender.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.sex","URL":"teidata.sex.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.probCert","URL":"teidata.probCert.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.unboundedCount","URL":"teidata.unboundedCount.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.nullOrName","URL":"teidata.nullOrName.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.temporal.iso","URL":"teidata.temporal.iso.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.duration.iso","URL":"teidata.duration.iso.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}}]} \ No newline at end of file +{"elements":[{"id":"teiHeader","URL":"teiHeader.xml","de":{"out-of-date":true,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"fileDesc","URL":"fileDesc.xml","de":{"out-of-date":true,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"titleStmt","URL":"titleStmt.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"sponsor","URL":"sponsor.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"funder","URL":"funder.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"principal","URL":"principal.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"editionStmt","URL":"editionStmt.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"edition","URL":"edition.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"extent","URL":"extent.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"publicationStmt","URL":"publicationStmt.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"distributor","URL":"distributor.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"authority","URL":"authority.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"idno","URL":"idno.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"availability","URL":"availability.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"licence","URL":"licence.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"seriesStmt","URL":"seriesStmt.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"notesStmt","URL":"notesStmt.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"sourceDesc","URL":"sourceDesc.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"biblFull","URL":"biblFull.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"encodingDesc","URL":"encodingDesc.xml","de":{"out-of-date":true,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"schemaRef","URL":"schemaRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"projectDesc","URL":"projectDesc.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"samplingDecl","URL":"samplingDecl.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"editorialDecl","URL":"editorialDecl.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"correction","URL":"correction.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"normalization","URL":"normalization.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"quotation","URL":"quotation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"hyphenation","URL":"hyphenation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"segmentation","URL":"segmentation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"stdVals","URL":"stdVals.xml","de":{"out-of-date":true,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"interpretation","URL":"interpretation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"punctuation","URL":"punctuation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"tagsDecl","URL":"tagsDecl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"tagUsage","URL":"tagUsage.xml","de":{"out-of-date":true,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"namespace","URL":"namespace.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"rendition","URL":"rendition.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"styleDefDecl","URL":"styleDefDecl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"refsDecl","URL":"refsDecl.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"citeStructure","URL":"citeStructure.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"citeData","URL":"citeData.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"cRefPattern","URL":"cRefPattern.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"prefixDef","URL":"prefixDef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listPrefixDef","URL":"listPrefixDef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"refState","URL":"refState.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"classDecl","URL":"classDecl.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"taxonomy","URL":"taxonomy.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"category","URL":"category.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"catDesc","URL":"catDesc.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"geoDecl","URL":"geoDecl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"unitDecl","URL":"unitDecl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"unitDef","URL":"unitDef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"conversion","URL":"conversion.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"appInfo","URL":"appInfo.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"application","URL":"application.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"profileDesc","URL":"profileDesc.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"handNote","URL":"handNote.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"abstract","URL":"abstract.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"creation","URL":"creation.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"langUsage","URL":"langUsage.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"language","URL":"language.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"textClass","URL":"textClass.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"keywords","URL":"keywords.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"classCode","URL":"classCode.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"catRef","URL":"catRef.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"calendarDesc","URL":"calendarDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"calendar","URL":"calendar.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"correspDesc","URL":"correspDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"correspAction","URL":"correspAction.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"correspContext","URL":"correspContext.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"xenoData","URL":"xenoData.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"revisionDesc","URL":"revisionDesc.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"change","URL":"change.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"p","URL":"p.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"foreign","URL":"foreign.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"emph","URL":"emph.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"hi","URL":"hi.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"distinct","URL":"distinct.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"said","URL":"said.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"quote","URL":"quote.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"q","URL":"q.xml","de":{"out-of-date":true,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"cit","URL":"cit.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"mentioned","URL":"mentioned.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"soCalled","URL":"soCalled.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"desc","URL":"desc.xml","de":{"out-of-date":true,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"gloss","URL":"gloss.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"term","URL":"term.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"ruby","URL":"ruby.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"rb","URL":"rb.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"rt","URL":"rt.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"sic","URL":"sic.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"corr","URL":"corr.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"choice","URL":"choice.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"reg","URL":"reg.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"orig","URL":"orig.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"gap","URL":"gap.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"ellipsis","URL":"ellipsis.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"add","URL":"add.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"del","URL":"del.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"unclear","URL":"unclear.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"name","URL":"name.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"rs","URL":"rs.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"email","URL":"email.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"address","URL":"address.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"addrLine","URL":"addrLine.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"street","URL":"street.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"postCode","URL":"postCode.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"postBox","URL":"postBox.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"num","URL":"num.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"measure","URL":"measure.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"measureGrp","URL":"measureGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"unit","URL":"unit.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"date","URL":"date.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"time","URL":"time.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"abbr","URL":"abbr.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"expan","URL":"expan.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"ptr","URL":"ptr.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"ref","URL":"ref.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"list","URL":"list.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"item","URL":"item.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"label","URL":"label.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"head","URL":"head.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"headLabel","URL":"headLabel.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"headItem","URL":"headItem.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"note","URL":"note.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"noteGrp","URL":"noteGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"index","URL":"index.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"media","URL":"media.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"graphic","URL":"graphic.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"binaryObject","URL":"binaryObject.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"milestone","URL":"milestone.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"gb","URL":"gb.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"pb","URL":"pb.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"lb","URL":"lb.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"cb","URL":"cb.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"analytic","URL":"analytic.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"monogr","URL":"monogr.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"series","URL":"series.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"author","URL":"author.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"editor","URL":"editor.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"respStmt","URL":"respStmt.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"resp","URL":"resp.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"title","URL":"title.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"meeting","URL":"meeting.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"imprint","URL":"imprint.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"publisher","URL":"publisher.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"biblScope","URL":"biblScope.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"citedRange","URL":"citedRange.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"pubPlace","URL":"pubPlace.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"bibl","URL":"bibl.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"biblStruct","URL":"biblStruct.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"listBibl","URL":"listBibl.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"relatedItem","URL":"relatedItem.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"l","URL":"l.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"lg","URL":"lg.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"sp","URL":"sp.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"speaker","URL":"speaker.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"stage","URL":"stage.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"TEI","URL":"TEI.xml","de":{"out-of-date":true,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teiCorpus","URL":"teiCorpus.xml","de":{"out-of-date":true,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"text","URL":"text.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"body","URL":"body.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"group","URL":"group.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"floatingText","URL":"floatingText.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"div","URL":"div.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"div1","URL":"div1.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"div2","URL":"div2.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"div3","URL":"div3.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"div4","URL":"div4.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"div5","URL":"div5.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"div6","URL":"div6.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"div7","URL":"div7.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"divGen","URL":"divGen.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"trailer","URL":"trailer.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"byline","URL":"byline.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"dateline","URL":"dateline.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"argument","URL":"argument.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"epigraph","URL":"epigraph.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"opener","URL":"opener.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"closer","URL":"closer.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"salute","URL":"salute.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"signed","URL":"signed.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"postscript","URL":"postscript.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"titlePage","URL":"titlePage.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"docTitle","URL":"docTitle.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"titlePart","URL":"titlePart.xml","de":{"out-of-date":true,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"docAuthor","URL":"docAuthor.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"imprimatur","URL":"imprimatur.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"docEdition","URL":"docEdition.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"docImprint","URL":"docImprint.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"docDate","URL":"docDate.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"front","URL":"front.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"back","URL":"back.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"g","URL":"g.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"charDecl","URL":"charDecl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"char","URL":"char.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"glyph","URL":"glyph.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"localProp","URL":"localProp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"mapping","URL":"mapping.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"unihanProp","URL":"unihanProp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"unicodeProp","URL":"unicodeProp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"metDecl","URL":"metDecl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"metSym","URL":"metSym.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"caesura","URL":"caesura.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"rhyme","URL":"rhyme.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"set","URL":"set.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"prologue","URL":"prologue.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"epilogue","URL":"epilogue.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"performance","URL":"performance.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"castList","URL":"castList.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"castGroup","URL":"castGroup.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"castItem","URL":"castItem.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"role","URL":"role.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"roleDesc","URL":"roleDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"actor","URL":"actor.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"spGrp","URL":"spGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"move","URL":"move.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"view","URL":"view.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"camera","URL":"camera.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"sound","URL":"sound.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"caption","URL":"caption.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"tech","URL":"tech.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"scriptStmt","URL":"scriptStmt.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"recordingStmt","URL":"recordingStmt.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"recording","URL":"recording.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"equipment","URL":"equipment.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"broadcast","URL":"broadcast.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"transcriptionDesc","URL":"transcriptionDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"u","URL":"u.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"pause","URL":"pause.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"vocal","URL":"vocal.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"kinesic","URL":"kinesic.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"incident","URL":"incident.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"writing","URL":"writing.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"shift","URL":"shift.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"annotationBlock","URL":"annotationBlock.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"superEntry","URL":"superEntry.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"entry","URL":"entry.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"entryFree","URL":"entryFree.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"hom","URL":"hom.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"sense","URL":"sense.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"dictScrap","URL":"dictScrap.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"form","URL":"form.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"orth","URL":"orth.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"pron","URL":"pron.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"hyph","URL":"hyph.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"syll","URL":"syll.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"stress","URL":"stress.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"gram","URL":"gram.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"gen","URL":"gen.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"number","URL":"number.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"case","URL":"case.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"per","URL":"per.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"tns","URL":"tns.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"mood","URL":"mood.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"iType","URL":"iType.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"gramGrp","URL":"gramGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"pos","URL":"pos.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"subc","URL":"subc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"colloc","URL":"colloc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"def","URL":"def.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"etym","URL":"etym.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"lang","URL":"lang.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"usg","URL":"usg.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"lbl","URL":"lbl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"xr","URL":"xr.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"re","URL":"re.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"oRef","URL":"oRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"pRef","URL":"pRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"msDesc","URL":"msDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"catchwords","URL":"catchwords.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"dimensions","URL":"dimensions.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"dim","URL":"dim.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"height","URL":"height.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"depth","URL":"depth.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"width","URL":"width.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"heraldry","URL":"heraldry.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"locus","URL":"locus.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"locusGrp","URL":"locusGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"material","URL":"material.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"objectType","URL":"objectType.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"origDate","URL":"origDate.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"origPlace","URL":"origPlace.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"secFol","URL":"secFol.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"signatures","URL":"signatures.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"stamp","URL":"stamp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"watermark","URL":"watermark.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"msIdentifier","URL":"msIdentifier.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"institution","URL":"institution.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"repository","URL":"repository.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"collection","URL":"collection.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"altIdentifier","URL":"altIdentifier.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"msName","URL":"msName.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"colophon","URL":"colophon.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"explicit","URL":"explicit.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"filiation","URL":"filiation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"finalRubric","URL":"finalRubric.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"incipit","URL":"incipit.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"msContents","URL":"msContents.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"msItem","URL":"msItem.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"msItemStruct","URL":"msItemStruct.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"rubric","URL":"rubric.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"summary","URL":"summary.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"textLang","URL":"textLang.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"physDesc","URL":"physDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"objectDesc","URL":"objectDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"supportDesc","URL":"supportDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"support","URL":"support.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"collation","URL":"collation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"foliation","URL":"foliation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"condition","URL":"condition.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"layoutDesc","URL":"layoutDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"layout","URL":"layout.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"handDesc","URL":"handDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"typeDesc","URL":"typeDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"typeNote","URL":"typeNote.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"scriptDesc","URL":"scriptDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"scriptNote","URL":"scriptNote.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"musicNotation","URL":"musicNotation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"decoDesc","URL":"decoDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"decoNote","URL":"decoNote.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"additions","URL":"additions.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"bindingDesc","URL":"bindingDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"binding","URL":"binding.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"sealDesc","URL":"sealDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"seal","URL":"seal.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"accMat","URL":"accMat.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"history","URL":"history.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"origin","URL":"origin.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"provenance","URL":"provenance.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"acquisition","URL":"acquisition.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"additional","URL":"additional.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"adminInfo","URL":"adminInfo.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"recordHist","URL":"recordHist.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"source","URL":"source.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"custodialHist","URL":"custodialHist.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"custEvent","URL":"custEvent.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"surrogates","URL":"surrogates.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"msPart","URL":"msPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"msFrag","URL":"msFrag.xml","de":{"out-of-date":true,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"facsimile","URL":"facsimile.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"sourceDoc","URL":"sourceDoc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"surface","URL":"surface.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"surfaceGrp","URL":"surfaceGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"zone","URL":"zone.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"path","URL":"path.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"addSpan","URL":"addSpan.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"damage","URL":"damage.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"damageSpan","URL":"damageSpan.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"delSpan","URL":"delSpan.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"ex","URL":"ex.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"fw","URL":"fw.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"handNotes","URL":"handNotes.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"handShift","URL":"handShift.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"am","URL":"am.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"restore","URL":"restore.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"space","URL":"space.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"subst","URL":"subst.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"substJoin","URL":"substJoin.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"supplied","URL":"supplied.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"surplus","URL":"surplus.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"secl","URL":"secl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"line","URL":"line.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listChange","URL":"listChange.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listTranspose","URL":"listTranspose.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"metamark","URL":"metamark.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"mod","URL":"mod.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"redo","URL":"redo.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"retrace","URL":"retrace.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"transpose","URL":"transpose.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"undo","URL":"undo.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"app","URL":"app.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"listApp","URL":"listApp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"lem","URL":"lem.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"rdg","URL":"rdg.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"rdgGrp","URL":"rdgGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"witDetail","URL":"witDetail.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"wit","URL":"wit.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listWit","URL":"listWit.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"witness","URL":"witness.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"witStart","URL":"witStart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"witEnd","URL":"witEnd.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"lacunaStart","URL":"lacunaStart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"lacunaEnd","URL":"lacunaEnd.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"variantEncoding","URL":"variantEncoding.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"orgName","URL":"orgName.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"persName","URL":"persName.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"surname","URL":"surname.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"forename","URL":"forename.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"genName","URL":"genName.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"nameLink","URL":"nameLink.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"addName","URL":"addName.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"roleName","URL":"roleName.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"placeName","URL":"placeName.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"bloc","URL":"bloc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"country","URL":"country.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"region","URL":"region.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"settlement","URL":"settlement.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"district","URL":"district.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"offset","URL":"offset.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"geogName","URL":"geogName.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"geogFeat","URL":"geogFeat.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"affiliation","URL":"affiliation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"age","URL":"age.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"birth","URL":"birth.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"climate","URL":"climate.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"death","URL":"death.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"education","URL":"education.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"event","URL":"event.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"faith","URL":"faith.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"floruit","URL":"floruit.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"gender","URL":"gender.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"geo","URL":"geo.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"langKnowledge","URL":"langKnowledge.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"langKnown","URL":"langKnown.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"listOrg","URL":"listOrg.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listEvent","URL":"listEvent.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listPerson","URL":"listPerson.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listPlace","URL":"listPlace.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listRelation","URL":"listRelation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"location","URL":"location.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"nationality","URL":"nationality.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"occupation","URL":"occupation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"org","URL":"org.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"person","URL":"person.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"persona","URL":"persona.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"personGrp","URL":"personGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"persPronouns","URL":"persPronouns.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"place","URL":"place.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"population","URL":"population.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"relation","URL":"relation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"residence","URL":"residence.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"sex","URL":"sex.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"socecStatus","URL":"socecStatus.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"state","URL":"state.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"terrain","URL":"terrain.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"trait","URL":"trait.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"objectName","URL":"objectName.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"object","URL":"object.xml","de":{"out-of-date":true,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listObject","URL":"listObject.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"objectIdentifier","URL":"objectIdentifier.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"nym","URL":"nym.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"listNym","URL":"listNym.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"table","URL":"table.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"row","URL":"row.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"cell","URL":"cell.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"formula","URL":"formula.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"notatedMusic","URL":"notatedMusic.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"figure","URL":"figure.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"figDesc","URL":"figDesc.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"textDesc","URL":"textDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"particDesc","URL":"particDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"settingDesc","URL":"settingDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"channel","URL":"channel.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"constitution","URL":"constitution.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"derivation","URL":"derivation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"domain","URL":"domain.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"factuality","URL":"factuality.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"interaction","URL":"interaction.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"preparedness","URL":"preparedness.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"purpose","URL":"purpose.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"setting","URL":"setting.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"locale","URL":"locale.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"activity","URL":"activity.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"link","URL":"link.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"linkGrp","URL":"linkGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"ab","URL":"ab.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"anchor","URL":"anchor.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"seg","URL":"seg.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"when","URL":"when.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"timeline","URL":"timeline.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"join","URL":"join.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"joinGrp","URL":"joinGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"alt","URL":"alt.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"altGrp","URL":"altGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"standOff","URL":"standOff.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listAnnotation","URL":"listAnnotation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"annotation","URL":"annotation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"s","URL":"s.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"cl","URL":"cl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"phr","URL":"phr.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"w","URL":"w.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"m","URL":"m.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"c","URL":"c.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"pc","URL":"pc.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"span","URL":"span.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"spanGrp","URL":"spanGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"interp","URL":"interp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"interpGrp","URL":"interpGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"fsdDecl","URL":"fsdDecl.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"fsDecl","URL":"fsDecl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"fsDescr","URL":"fsDescr.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"fsdLink","URL":"fsdLink.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"fDecl","URL":"fDecl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"fDescr","URL":"fDescr.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"vRange","URL":"vRange.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"vDefault","URL":"vDefault.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"if","URL":"if.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"then","URL":"then.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"fsConstraints","URL":"fsConstraints.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"cond","URL":"cond.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"bicond","URL":"bicond.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"iff","URL":"iff.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"fs","URL":"fs.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"f","URL":"f.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"binary","URL":"binary.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"symbol","URL":"symbol.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"numeric","URL":"numeric.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"string","URL":"string.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"vLabel","URL":"vLabel.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"vColl","URL":"vColl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"default","URL":"default.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"vAlt","URL":"vAlt.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"vNot","URL":"vNot.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"vMerge","URL":"vMerge.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"fLib","URL":"fLib.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"fvLib","URL":"fvLib.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"graph","URL":"graph.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"node","URL":"node.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"arc","URL":"arc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"tree","URL":"tree.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"root","URL":"root.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"iNode","URL":"iNode.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"leaf","URL":"leaf.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"eTree","URL":"eTree.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"triangle","URL":"triangle.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"eLeaf","URL":"eLeaf.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"forest","URL":"forest.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listForest","URL":"listForest.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"precision","URL":"precision.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"certainty","URL":"certainty.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"respons","URL":"respons.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att","URL":"att.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"code","URL":"code.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"eg","URL":"eg.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"egXML","URL":"egXML.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"gi","URL":"gi.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"ident","URL":"ident.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"tag","URL":"tag.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"val","URL":"val.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"specList","URL":"specList.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"specDesc","URL":"specDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"classRef","URL":"classRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"elementRef","URL":"elementRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"macroRef","URL":"macroRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"moduleRef","URL":"moduleRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"moduleSpec","URL":"moduleSpec.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"schemaSpec","URL":"schemaSpec.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"specGrp","URL":"specGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"specGrpRef","URL":"specGrpRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"elementSpec","URL":"elementSpec.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"classSpec","URL":"classSpec.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"dataSpec","URL":"dataSpec.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"macroSpec","URL":"macroSpec.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"remarks","URL":"remarks.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listRef","URL":"listRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"exemplum","URL":"exemplum.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"classes","URL":"classes.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"memberOf","URL":"memberOf.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"equiv","URL":"equiv.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"altIdent","URL":"altIdent.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model","URL":"model.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"modelSequence","URL":"modelSequence.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"modelGrp","URL":"modelGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"outputRendition","URL":"outputRendition.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"paramList","URL":"paramList.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"paramSpec","URL":"paramSpec.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"param","URL":"param.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"content","URL":"content.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"sequence","URL":"sequence.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"alternate","URL":"alternate.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"constraint","URL":"constraint.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"constraintSpec","URL":"constraintSpec.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"attList","URL":"attList.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"attDef","URL":"attDef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"attRef","URL":"attRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"datatype","URL":"datatype.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"dataRef","URL":"dataRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"dataFacet","URL":"dataFacet.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"defaultVal","URL":"defaultVal.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"valDesc","URL":"valDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"valItem","URL":"valItem.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"valList","URL":"valList.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"textNode","URL":"textNode.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"anyElement","URL":"anyElement.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"empty","URL":"empty.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}}],"att_classes":[{"id":"att.anchoring","URL":"att.anchoring.xml","de":{"out-of-date":true,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.ascribed","URL":"att.ascribed.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.ascribed.directed","URL":"att.ascribed.directed.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.canonical","URL":"att.canonical.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.ranging","URL":"att.ranging.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.dimensions","URL":"att.dimensions.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.written","URL":"att.written.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.damaged","URL":"att.damaged.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.breaking","URL":"att.breaking.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.cReferencing","URL":"att.cReferencing.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.datable.custom","URL":"att.datable.custom.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.datable.w3c","URL":"att.datable.w3c.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.datable","URL":"att.datable.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.datcat","URL":"att.datcat.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.declarable","URL":"att.declarable.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.declaring","URL":"att.declaring.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.fragmentable","URL":"att.fragmentable.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.divLike","URL":"att.divLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.docStatus","URL":"att.docStatus.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.duration.w3c","URL":"att.duration.w3c.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.duration","URL":"att.duration.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.global.responsibility","URL":"att.global.responsibility.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.editLike","URL":"att.editLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.global.rendition","URL":"att.global.rendition.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.global.source","URL":"att.global.source.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.global","URL":"att.global.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.handFeatures","URL":"att.handFeatures.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.internetMedia","URL":"att.internetMedia.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.media","URL":"att.media.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.resourced","URL":"att.resourced.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.interpLike","URL":"att.interpLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.measurement","URL":"att.measurement.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.milestoneUnit","URL":"att.milestoneUnit.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.naming","URL":"att.naming.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.notated","URL":"att.notated.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.placement","URL":"att.placement.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.typed","URL":"att.typed.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.pointing","URL":"att.pointing.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.pointing.group","URL":"att.pointing.group.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.scoping","URL":"att.scoping.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.segLike","URL":"att.segLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.sortable","URL":"att.sortable.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.edition","URL":"att.edition.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.spanning","URL":"att.spanning.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.styleDef","URL":"att.styleDef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.tableDecoration","URL":"att.tableDecoration.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.timed","URL":"att.timed.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.transcriptional","URL":"att.transcriptional.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.citing","URL":"att.citing.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.citeStructurePart","URL":"att.citeStructurePart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.patternReplacement","URL":"att.patternReplacement.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.formula","URL":"att.formula.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.locatable","URL":"att.locatable.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.gaijiProp","URL":"att.gaijiProp.xml","de":{"out-of-date":true,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.metrical","URL":"att.metrical.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.enjamb","URL":"att.enjamb.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.entryLike","URL":"att.entryLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.lexicographic","URL":"att.lexicographic.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.partials","URL":"att.partials.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.msExcerpt","URL":"att.msExcerpt.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.msClass","URL":"att.msClass.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.global.facs","URL":"att.global.facs.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.global.change","URL":"att.global.change.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.coordinated","URL":"att.coordinated.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.rdgPart","URL":"att.rdgPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.witnessed","URL":"att.witnessed.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.textCritical","URL":"att.textCritical.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.personal","URL":"att.personal.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.datable.iso","URL":"att.datable.iso.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.calendarSystem","URL":"att.calendarSystem.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.duration.iso","URL":"att.duration.iso.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.global.linking","URL":"att.global.linking.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.lexicographic.normalized","URL":"att.lexicographic.normalized.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.linguistic","URL":"att.linguistic.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.global.analytic","URL":"att.global.analytic.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.translatable","URL":"att.translatable.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.predicate","URL":"att.predicate.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.repeatable","URL":"att.repeatable.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.combinable","URL":"att.combinable.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.identified","URL":"att.identified.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"att.deprecated","URL":"att.deprecated.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.namespaceable","URL":"att.namespaceable.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}}],"model_classes":[{"id":"model.nameLike.agent","URL":"model.nameLike.agent.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.segLike","URL":"model.segLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.hiLike","URL":"model.hiLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.emphLike","URL":"model.emphLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.highlighted","URL":"model.highlighted.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.dateLike","URL":"model.dateLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.dimLike","URL":"model.dimLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.measureLike","URL":"model.measureLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.egLike","URL":"model.egLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.graphicLike","URL":"model.graphicLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.offsetLike","URL":"model.offsetLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.pPart.msdesc","URL":"model.pPart.msdesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.pPart.editorial","URL":"model.pPart.editorial.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.pPart.transcriptional","URL":"model.pPart.transcriptional.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.pPart.edit","URL":"model.pPart.edit.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.linePart","URL":"model.linePart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.ptrLike","URL":"model.ptrLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.lPart","URL":"model.lPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.global.meta","URL":"model.global.meta.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"model.milestoneLike","URL":"model.milestoneLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.gLike","URL":"model.gLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.oddDecl","URL":"model.oddDecl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.oddRef","URL":"model.oddRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.phrase.xml","URL":"model.phrase.xml.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.specDescLike","URL":"model.specDescLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.biblLike","URL":"model.biblLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.headLike","URL":"model.headLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.labelLike","URL":"model.labelLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.listLike","URL":"model.listLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.noteLike","URL":"model.noteLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.lLike","URL":"model.lLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.pLike","URL":"model.pLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.stageLike","URL":"model.stageLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"model.featureVal.complex","URL":"model.featureVal.complex.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.featureVal.single","URL":"model.featureVal.single.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.entryPart","URL":"model.entryPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.entryPart.top","URL":"model.entryPart.top.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"model.eventLike","URL":"model.eventLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.global.edit","URL":"model.global.edit.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.global.spoken","URL":"model.global.spoken.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.divPart","URL":"model.divPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"model.persStateLike","URL":"model.persStateLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"model.personLike","URL":"model.personLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.personPart","URL":"model.personPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.placeNamePart","URL":"model.placeNamePart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.placeStateLike","URL":"model.placeStateLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.orgPart","URL":"model.orgPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.publicationStmtPart.agency","URL":"model.publicationStmtPart.agency.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"model.publicationStmtPart.detail","URL":"model.publicationStmtPart.detail.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"model.availabilityPart","URL":"model.availabilityPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.certLike","URL":"model.certLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.descLike","URL":"model.descLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.identEquiv","URL":"model.identEquiv.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.identSynonyms","URL":"model.identSynonyms.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.quoteLike","URL":"model.quoteLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.attributable","URL":"model.attributable.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.rdgLike","URL":"model.rdgLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"model.respLike","URL":"model.respLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.divWrapper","URL":"model.divWrapper.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.divTopPart","URL":"model.divTopPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.divTop","URL":"model.divTop.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.frontPart.drama","URL":"model.frontPart.drama.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.pLike.front","URL":"model.pLike.front.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.divBottomPart","URL":"model.divBottomPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.divBottom","URL":"model.divBottom.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.titlepagePart","URL":"model.titlepagePart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.msQuoteLike","URL":"model.msQuoteLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.msItemPart","URL":"model.msItemPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.choicePart","URL":"model.choicePart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.recordingPart","URL":"model.recordingPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.imprintPart","URL":"model.imprintPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.catDescPart","URL":"model.catDescPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.settingPart","URL":"model.settingPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.textDescPart","URL":"model.textDescPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.castItemPart","URL":"model.castItemPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.physDescPart","URL":"model.physDescPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.addressLike","URL":"model.addressLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.nameLike","URL":"model.nameLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"model.persNamePart","URL":"model.persNamePart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.global","URL":"model.global.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.featureVal","URL":"model.featureVal.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.biblPart","URL":"model.biblPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.frontPart","URL":"model.frontPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.addrPart","URL":"model.addrPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.pPart.data","URL":"model.pPart.data.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.inter","URL":"model.inter.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.common","URL":"model.common.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.phrase","URL":"model.phrase.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"model.paraPart","URL":"model.paraPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.limitedPhrase","URL":"model.limitedPhrase.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.divLike","URL":"model.divLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.divGenLike","URL":"model.divGenLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.div1Like","URL":"model.div1Like.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.div2Like","URL":"model.div2Like.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.div3Like","URL":"model.div3Like.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.div4Like","URL":"model.div4Like.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.div5Like","URL":"model.div5Like.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.div6Like","URL":"model.div6Like.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.div7Like","URL":"model.div7Like.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.annotationLike","URL":"model.annotationLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.annotationPart.body","URL":"model.annotationPart.body.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.applicationLike","URL":"model.applicationLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.teiHeaderPart","URL":"model.teiHeaderPart.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.sourceDescPart","URL":"model.sourceDescPart.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.encodingDescPart","URL":"model.encodingDescPart.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.editorialDeclPart","URL":"model.editorialDeclPart.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.profileDescPart","URL":"model.profileDescPart.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.standOffPart","URL":"model.standOffPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.correspActionPart","URL":"model.correspActionPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.correspContextPart","URL":"model.correspContextPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.correspDescPart","URL":"model.correspDescPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.divPart.spoken","URL":"model.divPart.spoken.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"model.entryLike","URL":"model.entryLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.morphLike","URL":"model.morphLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.lexicalRefinement","URL":"model.lexicalRefinement.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.gramPart","URL":"model.gramPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.formPart","URL":"model.formPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.ptrLike.form","URL":"model.ptrLike.form.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.resource","URL":"model.resource.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.describedResource","URL":"model.describedResource.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.rdgPart","URL":"model.rdgPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.objectLike","URL":"model.objectLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.orgStateLike","URL":"model.orgStateLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.placeLike","URL":"model.placeLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.fsdDeclPart","URL":"model.fsdDeclPart.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.contentPart","URL":"model.contentPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}}],"macros":[{"id":"macro.abContent","URL":"macro.abContent.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"macro.paraContent","URL":"macro.paraContent.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"macro.limitedContent","URL":"macro.limitedContent.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"macro.phraseSeq","URL":"macro.phraseSeq.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"macro.phraseSeq.limited","URL":"macro.phraseSeq.limited.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"macro.specialPara","URL":"macro.specialPara.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"macro.xtext","URL":"macro.xtext.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}}],"datatypes":[{"id":"teidata.certainty","URL":"teidata.certainty.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.probability","URL":"teidata.probability.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.numeric","URL":"teidata.numeric.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.interval","URL":"teidata.interval.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.count","URL":"teidata.count.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.temporal.w3c","URL":"teidata.temporal.w3c.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.temporal.working","URL":"teidata.temporal.working.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.duration.w3c","URL":"teidata.duration.w3c.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.truthValue","URL":"teidata.truthValue.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.xTruthValue","URL":"teidata.xTruthValue.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.language","URL":"teidata.language.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.namespace","URL":"teidata.namespace.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.namespaceOrName","URL":"teidata.namespaceOrName.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.outputMeasurement","URL":"teidata.outputMeasurement.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.pattern","URL":"teidata.pattern.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.point","URL":"teidata.point.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.pointer","URL":"teidata.pointer.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.authority","URL":"teidata.authority.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.version","URL":"teidata.version.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.versionNumber","URL":"teidata.versionNumber.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.replacement","URL":"teidata.replacement.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.xpath","URL":"teidata.xpath.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.word","URL":"teidata.word.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.text","URL":"teidata.text.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.name","URL":"teidata.name.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.xmlName","URL":"teidata.xmlName.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.prefix","URL":"teidata.prefix.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.enumerated","URL":"teidata.enumerated.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.gender","URL":"teidata.gender.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.sex","URL":"teidata.sex.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.probCert","URL":"teidata.probCert.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.unboundedCount","URL":"teidata.unboundedCount.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.nullOrName","URL":"teidata.nullOrName.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.temporal.iso","URL":"teidata.temporal.iso.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.duration.iso","URL":"teidata.duration.iso.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}}]} From 9595070444b811fe2450fb70002a830f20fd73c8 Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Fri, 15 Mar 2024 12:59:50 -0400 Subject: [PATCH 042/127] =?UTF-8?q?Updated=20some=20old=20attrs=20in=20eam?= =?UTF-8?q?ple=20to=20current=20versions.=20But=20=E2=80=A6=20=E2=80=A6=20?= =?UTF-8?q?this=20begs=20the=20question,=20=E2=80=9Cwhy=20didn=E2=80=99t?= =?UTF-8?q?=20'make=20validate'=20catch=20these=20errors=20earlier=3F?= =?UTF-8?q?=E2=80=9D,=20to=20which=20I=20do=20not=20have=20an=20answer=20a?= =?UTF-8?q?t=20the=20moment.?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .../Guidelines/en/CMC-ComputerMediatedCommunication.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml index b0ad1e39fe..8813041aec 100644 --- a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml +++ b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml @@ -382,10 +382,10 @@ See the file COPYING.txt for details. synch="#tweetsbcrn18.t002" xml:id="cmc_post_1043769240136880128"> - - -
+ +
From d341f16c336b584293adbeea0feb5ccba358e609 Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Fri, 15 Mar 2024 16:26:36 -0400 Subject: [PATCH 043/127] ooops; correct a typo in the previous fix --- P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml index 8813041aec..b3321bea2f 100644 --- a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml +++ b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml @@ -382,7 +382,7 @@ See the file COPYING.txt for details. synch="#tweetsbcrn18.t002" xml:id="cmc_post_1043769240136880128"> -
From 0cf0adae802f1cd5307820b6de4452b01e0712c9 Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Fri, 15 Mar 2024 22:41:48 -0400 Subject: [PATCH 044/127] NA council subgroup tweaks: * Made deprecation message a warning, not an error. * Used 2025-03-15 as the end of deprecation period. * Added validUntil= (and a description) to the constraint specification that does the work, so that this shows up in Appendix G. * Added test for this in Test/detest.odd. * NOTE: The test in detest.odd will not actually fire, apparently because it is a warning not an error. So it will start to fire when we change it to an error on 2025-03-15. --- P5/Source/Specs/constraintSpec.xml | 9 +++++++-- P5/Test/detest.odd | 9 +++++++++ 2 files changed, 16 insertions(+), 2 deletions(-) diff --git a/P5/Source/Specs/constraintSpec.xml b/P5/Source/Specs/constraintSpec.xml index cbcfcd1fab..04305455ea 100644 --- a/P5/Source/Specs/constraintSpec.xml +++ b/P5/Source/Specs/constraintSpec.xml @@ -59,7 +59,12 @@ - + + + The use of ISO Schematron sch:assert and + sch:report elements without a parent sch:rule + with a context attribute is deprecated — it will be + an error after 2025-03-15. - - - -
+
+ + +
émeute -
 - - -
- grève -
- - -
- grève -
- - - + + + + +
+ grève +
+ + +
+ grève +
+ + +

@@ -298,37 +300,38 @@ anomalous, as further discussed in section .

An entry with two homographs, the first with two senses and the second with three (one of which has two sub-senses), may have a structure like this: - - - - - - - - - - - - - + + + + + + + + + + + + + In some dictionaries, homographs have separate entries; in such a case, as noted in section , the two homographs may be - treated as entries, optionally grouped in an outer entry element with a type attribute value of encompassing: - - - - - - - - - - - - - - +treated as entries, optionally grouped in an outer entry element: + + + + + + + + + + + + + + +

The hierarchic structure of a dictionary entry is enforced by the diff --git a/P5/Source/Specs/superEntry.xml b/P5/Source/Specs/superEntry.xml index 58ddb6c909..2f6024e3f1 100644 --- a/P5/Source/Specs/superEntry.xml +++ b/P5/Source/Specs/superEntry.xml @@ -2,17 +2,20 @@ - Because an entry can now occur inside an entry, the superEntry element is no longer needed. For instances where the superEntry element was used to group multiple entry elements, these Guidelines recommend using an outer entry element with a type attribute value of encompassing instead. + Because an entry can now occur + inside an entry, the superEntry element is no + longer needed. For instances where the superEntry element + was used to group multiple entry elements, these Guidelines + recommend using instead an outer entry element, perhaps + with a type attribute. super entry groupe d'entrées - groups a sequence of entries within any kind of lexical resource, such - as a dictionary or lexicon which function as a single unit, for - example a set of homographs. + groups a sequence of entries within any kind of lexical resource, such as a dictionary or lexicon which function as a single unit, for example a set of homographs. 동형이의어 집합의 연속된 표제 항목을 모아 놓는다. 匯集一組同形異義字的連續辭條。 同形異義語の集合にある、一連の項目をまとめる。 - regroupe des entrées successives pour un ensemble - d'homographes. + regroupe des entrées successives pour un ensemble d'homographes. agrupa las entradas sucesivas para una serie de homógrafos. raggruppa voci successive per una serie di omografi. @@ -25,12 +28,8 @@ - - - - - - + + @@ -121,4 +120,4 @@ - \ No newline at end of file + From ddce5fef9356368ed0a18376b92d9db43704baef Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Sat, 16 Mar 2024 06:22:35 -0400 Subject: [PATCH 047/127] Remove extraneous namespace declarations (per request European subgroup) --- P5/Source/Guidelines/en/TD-DocumentationElements.xml | 4 ++-- P5/Source/Specs/moduleRef.xml | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/P5/Source/Guidelines/en/TD-DocumentationElements.xml b/P5/Source/Guidelines/en/TD-DocumentationElements.xml index 05e2be7953..d5acac80bc 100644 --- a/P5/Source/Guidelines/en/TD-DocumentationElements.xml +++ b/P5/Source/Guidelines/en/TD-DocumentationElements.xml @@ -867,7 +867,7 @@ to mark any technical term, thus: - + if it contains any subdivisions, a division must contain at least two of them @@ -901,7 +901,7 @@ to mark any technical term, thus: - + You should provide information in a figure from which we can construct an alt attribute in HTML diff --git a/P5/Source/Specs/moduleRef.xml b/P5/Source/Specs/moduleRef.xml index 2f715b4fde..0ecd6a33f1 100644 --- a/P5/Source/Specs/moduleRef.xml +++ b/P5/Source/Specs/moduleRef.xml @@ -36,7 +36,7 @@ - + The prefix attribute of should not match that of any other element (it would defeat the purpose) @@ -45,7 +45,7 @@ - + It is an error to supply both the @include and @except attributes From e22c6463ab6f2edd498d6c888ca512eddd5d10f4 Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Tue, 19 Mar 2024 11:58:19 -0400 Subject: [PATCH 048/127] Cosmetic changes: use namespace prefixes instead of declarations, and some whitespace tweaks --- P5/Exemplars/tei_enrich.odd | 1 - P5/Exemplars/tei_simplePrint.odd | 85 ++++++++++++++++++-------------- P5/p5odds.odd | 20 ++++---- 3 files changed, 57 insertions(+), 49 deletions(-) diff --git a/P5/Exemplars/tei_enrich.odd b/P5/Exemplars/tei_enrich.odd index e16ee4dcbd..113fa12ff5 100644 --- a/P5/Exemplars/tei_enrich.odd +++ b/P5/Exemplars/tei_enrich.odd @@ -1,7 +1,6 @@ - + @@ -3483,13 +3483,13 @@ live without God in the world, and only mind earthly things. - - + - Error: Every local pointer - in "" must point to an ID in this document - () - + Error: Every local pointer + in "" must point to an ID in this document + () + @@ -3498,24 +3498,28 @@ live without God in the world, and only mind earthly things. - - - Error: Each of the rendition - values in "" must point to a local ID or to a - token in the Simple scheme () - + + + Error: Each of the rendition + values in "" must point to a local ID or to a + token in the Simple scheme () + - - + - Error: Every local pointer in - "" must point to an ID in this document - () - + Error: Every local pointer in + "" must point to an ID in this document + () + @@ -3993,9 +3997,8 @@ live without God in the world, and only mind earthly things. - Element - "" may not be empty. + Element + "" may not be empty. @@ -4109,16 +4112,26 @@ live without God in the world, and only mind earthly things. - Element "" must have at least two child elements. + Element "" must have at least two child elements. - Element "" must have corresponding corr/sic, expand/abbr, - reg/orig + + Element "" must have corresponding corr/sic, expand/abbr, reg/orig @@ -5082,22 +5095,18 @@ live without God in the world, and only mind earthly things. - + - - - Error: The element is not permitted - outside the header - + + Error: The element is not permitted outside the header + diff --git a/P5/p5odds.odd b/P5/p5odds.odd index 1b7af79fb8..70b7db60eb 100644 --- a/P5/p5odds.odd +++ b/P5/p5odds.odd @@ -714,9 +714,9 @@ $Id$ - - Error: TEI element must be member of att.global class - + + Error: TEI element must be member of att.global class + @@ -724,14 +724,14 @@ $Id$ - - - - Error: There should only be one element per - language. Merge the contents of multiple elements + + + + Error: There should only be one element per + language. Merge the contents of multiple elements using separate p elements. - - + + From 420eb765a653eada4939820f2a476fb5f0eff1a6 Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Tue, 19 Mar 2024 12:19:38 -0400 Subject: [PATCH 049/127] Cosmetic changes: (#2539) use namespace prefixes instead of declarations, and some whitespace tweaks --- P5/Exemplars/tei_enrich.odd | 1 - P5/Exemplars/tei_simplePrint.odd | 85 ++++++++++++++++++-------------- P5/p5odds.odd | 20 ++++---- 3 files changed, 57 insertions(+), 49 deletions(-) diff --git a/P5/Exemplars/tei_enrich.odd b/P5/Exemplars/tei_enrich.odd index e16ee4dcbd..113fa12ff5 100644 --- a/P5/Exemplars/tei_enrich.odd +++ b/P5/Exemplars/tei_enrich.odd @@ -1,7 +1,6 @@ - + @@ -3483,13 +3483,13 @@ live without God in the world, and only mind earthly things. - - + - Error: Every local pointer - in "" must point to an ID in this document - () - + Error: Every local pointer + in "" must point to an ID in this document + () + @@ -3498,24 +3498,28 @@ live without God in the world, and only mind earthly things. - - - Error: Each of the rendition - values in "" must point to a local ID or to a - token in the Simple scheme () - + + + Error: Each of the rendition + values in "" must point to a local ID or to a + token in the Simple scheme () + - - + - Error: Every local pointer in - "" must point to an ID in this document - () - + Error: Every local pointer in + "" must point to an ID in this document + () + @@ -3993,9 +3997,8 @@ live without God in the world, and only mind earthly things. - Element - "" may not be empty. + Element + "" may not be empty. @@ -4109,16 +4112,26 @@ live without God in the world, and only mind earthly things. - Element "" must have at least two child elements. + Element "" must have at least two child elements. - Element "" must have corresponding corr/sic, expand/abbr, - reg/orig + + Element "" must have corresponding corr/sic, expand/abbr, reg/orig @@ -5082,22 +5095,18 @@ live without God in the world, and only mind earthly things. - + - - - Error: The element is not permitted - outside the header - + + Error: The element is not permitted outside the header + diff --git a/P5/p5odds.odd b/P5/p5odds.odd index 1b7af79fb8..70b7db60eb 100644 --- a/P5/p5odds.odd +++ b/P5/p5odds.odd @@ -714,9 +714,9 @@ $Id$ - - Error: TEI element must be member of att.global class - + + Error: TEI element must be member of att.global class + @@ -724,14 +724,14 @@ $Id$ - - - - Error: There should only be one element per - language. Merge the contents of multiple elements + + + + Error: There should only be one element per + language. Merge the contents of multiple elements using separate p elements. - - + + From f6f76b79cda68ef868162f7012d99cfb4dea21df Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Tue, 19 Mar 2024 12:45:37 -0400 Subject: [PATCH 050/127] Add missing Schematron rule elements --- P5/Exemplars/tei_enrich.odd | 6 +- P5/Exemplars/tei_simplePrint.odd | 40 +-- P5/Test/testmeta2010.odd | 273 +++++++++++---------- P5/Utilities/TEI-to-tei_customization.xslt | 259 +++++++++---------- 4 files changed, 300 insertions(+), 278 deletions(-) diff --git a/P5/Exemplars/tei_enrich.odd b/P5/Exemplars/tei_enrich.odd index 113fa12ff5..457e47184b 100644 --- a/P5/Exemplars/tei_enrich.odd +++ b/P5/Exemplars/tei_enrich.odd @@ -3453,8 +3453,10 @@ which should be supported by a more detailed description using the - - You must provide either @when or @to/@from, or @notAfter/@notBefore. + + + You must provide either @when or @to/@from, or @notAfter/@notBefore. + diff --git a/P5/Exemplars/tei_simplePrint.odd b/P5/Exemplars/tei_simplePrint.odd index 58c8e49a31..1ddcf9f99e 100644 --- a/P5/Exemplars/tei_simplePrint.odd +++ b/P5/Exemplars/tei_simplePrint.odd @@ -3997,8 +3997,10 @@ live without God in the world, and only mind earthly things. - Element - "" may not be empty. + + Element + "" may not be empty. + @@ -4112,26 +4114,30 @@ live without God in the world, and only mind earthly things. - Element "" must have at least two child elements. + + Element "" must have at least two child elements. + - + + Element "" must have corresponding corr/sic, expand/abbr, reg/orig + diff --git a/P5/Test/testmeta2010.odd b/P5/Test/testmeta2010.odd index b7b011b5f0..ebd717c707 100644 --- a/P5/Test/testmeta2010.odd +++ b/P5/Test/testmeta2010.odd @@ -8,8 +8,8 @@ Testing new ODD features added spring 2010 -

- +

+

authored from scratch

 @@ -20,89 +20,90 @@

First, define the very bare list of the elements we expect to see in the output schema. Just these elements, no more and no less.

- - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + +

Now make some changes and deletions

- - - - - - list - too short - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - italic - - - bold - - - - - - - - - - - - - - - + + + + + + + list too short + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + italic + + + bold + + + + + + + + + + + + + + + @@ -110,86 +111,86 @@ of TBX. The admin element has hi as its content model, but the TBX one and not the TEI one.

- - Contains information of an administrative nature for the node (parent element) - in question, such as the source of information, or the project or client for - which it applies. - - - - - - - - - - Highlights a segment of text and optionally points to another element. - - - - + + Contains information of an administrative nature for the node (parent element) + in question, such as the source of information, or the project or client for + which it applies. + + + + + + + + + + Highlights a segment of text and optionally points to another element. + + + +

The schema built using version 1.5 of TEI P5

- - - - - + + + + +

The schema build using a tei: URI

- - - - - + + + + +

Including attribute classes

- - - - - - + + + + + +

The schema build using defaults

- - - - + + + + diff --git a/P5/Utilities/TEI-to-tei_customization.xslt b/P5/Utilities/TEI-to-tei_customization.xslt index a7c9400eb7..6c85ab54d6 100644 --- a/P5/Utilities/TEI-to-tei_customization.xslt +++ b/P5/Utilities/TEI-to-tei_customization.xslt @@ -54,29 +54,29 @@ - - Remove the altIdent-only-NCName - constraint, as it is no longer needed — the content of - altIdent in P5 is now just xs:NCName. + + Remove the altIdent-only-NCName + constraint, as it is no longer needed — the content of + altIdent in P5 is now just xs:NCName. update to use version 4.6.0 of P5 - Per TEI ticket - #2285 disallow altIdent as a direct child of - classSpec, constraintSpec, - dataSpec, macroSpec; thus leaving it as - only available as a child of attDef, - elementSpec, and valItem. In order to do - this, remove altIdent from model.identSynonyms (leaving that class - with only gloss and equiv, i.e. the same - as model.identEquiv, sigh) and add - it back to attDef and valItem. - + Per TEI ticket + #2285 disallow altIdent as a direct child of + classSpec, constraintSpec, + dataSpec, macroSpec; thus leaving it as + only available as a child of attDef, + elementSpec, and valItem. In order to do + this, remove altIdent from model.identSynonyms (leaving that class + with only gloss and equiv, i.e. the same + as model.identEquiv, sigh) and add + it back to attDef and valItem. + - We will soon not allow more than 1 child of content, - so updated the content model of schemaSpec to have - only 1 child (in this case, sequence). + We will soon not allow more than 1 child of content, + so updated the content model of schemaSpec to have + only 1 child (in this case, sequence). Since - Fix bug in only-1-per contraint (which was added - 674 days ago — why did this bug last even 1 day?) + Fix bug in only-1-per contraint (which was added + 674 days ago — why did this bug last even 1 day?) - Changes for Pure ODD: - + Changes for Pure ODD: + constrain content of content delete att.global.rendition and att.global.responsibility + type="class" >att.global.responsibility delete allowText (as I think TEI has decided to go with textNode instead) require key of elementRef @@ -214,8 +214,8 @@ - Changes for Pure ODD: - + Changes for Pure ODD: + constrain key of classRef, elementRef, and macroRef constrain include and except of classRef, also @@ -235,9 +235,9 @@ - Add constraint only-1-per, which warns user iff - there are more than 1 elementSpec with the same - ident + Add constraint only-1-per, which warns user iff + there are more than 1 elementSpec with the same + ident @@ -262,11 +262,11 @@ - Added sch:pattern to list of elements allowed inside - constraint. + Added sch:pattern to list of elements allowed inside + constraint. - Remove the new notatedMusic and gb elments. + Remove the new notatedMusic and gb elments. @@ -277,7 +277,7 @@ - Test that required elements are not removed. + Test that required elements are not removed. @@ -288,8 +288,8 @@ - Beefed up prose, then corrections per Julia, including - changing name of language (and thus prefix). + Beefed up prose, then corrections per Julia, including + changing name of language (and thus prefix). @@ -313,18 +313,18 @@ - Constrain ident of classSpec. + Constrain ident of classSpec. - During workshop: - + During workshop: + constrain start of schemaSpec constrain key of elmentRef improve remakrs of constraint so that it correctly reflects that we only permit ISO Schematron constrain content of altIdent, unless it is a child of valItem - + @@ -746,28 +746,37 @@ - + - + required modules - missing one or more of the required modules (tei, core, header, - textstructure). + + missing one or more of the required modules (tei, core, header, textstructure). + @@ -1122,25 +1131,25 @@ - adding altIdent to content model because it was removed from model.identSynonyms - - - - - - - - - - - - - - - - - - + adding altIdent to content model because it was removed from model.identSynonyms + + + + + + + + + + + + + + + + + + @@ -1150,25 +1159,25 @@ - adding altIdent to content model because it was removed from model.identSynonyms - - - - - - - - - - - - - - - - - - + adding altIdent to content model because it was removed from model.identSynonyms + + + + + + + + + + + + + + + + + + @@ -1204,43 +1213,48 @@ - in a customization ODD, the mode= attribute of - ＜elementSpec＞ should be specified - the module= attribute of ＜elementSpec＞ must be specified anytime the mode= is - not 'add' + + + in a customization ODD, the mode= attribute of ＜elementSpec＞ should be specified + + + the module= attribute of ＜elementSpec＞ must be specified anytime the mode= is not 'add' + + - + Current ODD processors will not correctly handle more than one ＜elementSpec＞ with the same @ident + - Removing ＜TEI＞ from your - schema guarantees it is not TEI conformant - Removing ＜teiHeader＞ - from your schema guarantees it is not TEI conformant - Removing ＜fileDesc＞ from - your schema guarantees it is not TEI conformant - Removing ＜titleStmt＞ - from your schema guarantees it is not TEI conformant - Removing ＜title＞ from your - schema guarantees it is not TEI conformant - Removing - ＜publicationStmt＞ from your schema guarantees it is not TEI - conformant - Removing ＜sourceDesc＞ - from your schema guarantees it is not TEI conformant + + Removing ＜TEI＞ from your + schema guarantees it is not TEI conformant + Removing ＜teiHeader＞ + from your schema guarantees it is not TEI conformant + Removing ＜fileDesc＞ from + your schema guarantees it is not TEI conformant + Removing ＜titleStmt＞ + from your schema guarantees it is not TEI conformant + Removing ＜title＞ from your + schema guarantees it is not TEI conformant + Removing + ＜publicationStmt＞ from your schema guarantees it is not TEI + conformant + Removing ＜sourceDesc＞ + from your schema guarantees it is not TEI conformant + - + When adding a new element (whether replacing an old one or not), a content model must be specified; but this ＜elementSpec＞ does not have a ＜content＞ child. @@ -1362,9 +1376,9 @@ - - - + + + @@ -1514,18 +1528,17 @@ - - The @xml:id "" on ＜＞ duplicates an @xml:id found earlier in the document + + + The @xml:id "" on ＜＞ duplicates an @xml:id found earlier in the document + - From 948a97d6899a36e5baad0c199bf267f36ebe642e Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Tue, 19 Mar 2024 12:45:37 -0400 Subject: [PATCH 051/127] Add missing Schematron rule elements --- P5/Exemplars/tei_enrich.odd | 6 +- P5/Exemplars/tei_simplePrint.odd | 40 +-- P5/Test/testmeta2010.odd | 273 +++++++++++---------- P5/Utilities/TEI-to-tei_customization.xslt | 259 +++++++++---------- 4 files changed, 300 insertions(+), 278 deletions(-) diff --git a/P5/Exemplars/tei_enrich.odd b/P5/Exemplars/tei_enrich.odd index 113fa12ff5..457e47184b 100644 --- a/P5/Exemplars/tei_enrich.odd +++ b/P5/Exemplars/tei_enrich.odd @@ -3453,8 +3453,10 @@ which should be supported by a more detailed description using the - - You must provide either @when or @to/@from, or @notAfter/@notBefore. + + + You must provide either @when or @to/@from, or @notAfter/@notBefore. + diff --git a/P5/Exemplars/tei_simplePrint.odd b/P5/Exemplars/tei_simplePrint.odd index 58c8e49a31..1ddcf9f99e 100644 --- a/P5/Exemplars/tei_simplePrint.odd +++ b/P5/Exemplars/tei_simplePrint.odd @@ -3997,8 +3997,10 @@ live without God in the world, and only mind earthly things. - Element - "" may not be empty. + + Element + "" may not be empty. + @@ -4112,26 +4114,30 @@ live without God in the world, and only mind earthly things. - Element "" must have at least two child elements. + + Element "" must have at least two child elements. + - + + Element "" must have corresponding corr/sic, expand/abbr, reg/orig + diff --git a/P5/Test/testmeta2010.odd b/P5/Test/testmeta2010.odd index b7b011b5f0..ebd717c707 100644 --- a/P5/Test/testmeta2010.odd +++ b/P5/Test/testmeta2010.odd @@ -8,8 +8,8 @@ Testing new ODD features added spring 2010 -

- +

+

authored from scratch

 @@ -20,89 +20,90 @@

First, define the very bare list of the elements we expect to see in the output schema. Just these elements, no more and no less.

- - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + +

Now make some changes and deletions

- - - - - - list - too short - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - italic - - - bold - - - - - - - - - - - - - - - + + + + + + + list too short + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + italic + + + bold + + + + + + + + + + + + + + + @@ -110,86 +111,86 @@ of TBX. The admin element has hi as its content model, but the TBX one and not the TEI one.

- - Contains information of an administrative nature for the node (parent element) - in question, such as the source of information, or the project or client for - which it applies. - - - - - - - - - - Highlights a segment of text and optionally points to another element. - - - - + + Contains information of an administrative nature for the node (parent element) + in question, such as the source of information, or the project or client for + which it applies. + + + + + + + + + + Highlights a segment of text and optionally points to another element. + + + +

The schema built using version 1.5 of TEI P5

- - - - - + + + + +

The schema build using a tei: URI

- - - - - + + + + +

Including attribute classes

- - - - - - + + + + + +

The schema build using defaults

- - - - + + + + diff --git a/P5/Utilities/TEI-to-tei_customization.xslt b/P5/Utilities/TEI-to-tei_customization.xslt index a7c9400eb7..6c85ab54d6 100644 --- a/P5/Utilities/TEI-to-tei_customization.xslt +++ b/P5/Utilities/TEI-to-tei_customization.xslt @@ -54,29 +54,29 @@ - - Remove the altIdent-only-NCName - constraint, as it is no longer needed — the content of - altIdent in P5 is now just xs:NCName. + + Remove the altIdent-only-NCName + constraint, as it is no longer needed — the content of + altIdent in P5 is now just xs:NCName. update to use version 4.6.0 of P5 - Per TEI ticket - #2285 disallow altIdent as a direct child of - classSpec, constraintSpec, - dataSpec, macroSpec; thus leaving it as - only available as a child of attDef, - elementSpec, and valItem. In order to do - this, remove altIdent from model.identSynonyms (leaving that class - with only gloss and equiv, i.e. the same - as model.identEquiv, sigh) and add - it back to attDef and valItem. - + Per TEI ticket + #2285 disallow altIdent as a direct child of + classSpec, constraintSpec, + dataSpec, macroSpec; thus leaving it as + only available as a child of attDef, + elementSpec, and valItem. In order to do + this, remove altIdent from model.identSynonyms (leaving that class + with only gloss and equiv, i.e. the same + as model.identEquiv, sigh) and add + it back to attDef and valItem. + - We will soon not allow more than 1 child of content, - so updated the content model of schemaSpec to have - only 1 child (in this case, sequence). + We will soon not allow more than 1 child of content, + so updated the content model of schemaSpec to have + only 1 child (in this case, sequence). Since - Fix bug in only-1-per contraint (which was added - 674 days ago — why did this bug last even 1 day?) + Fix bug in only-1-per contraint (which was added + 674 days ago — why did this bug last even 1 day?) - Changes for Pure ODD: - + Changes for Pure ODD: + constrain content of content delete att.global.rendition and att.global.responsibility + type="class" >att.global.responsibility delete allowText (as I think TEI has decided to go with textNode instead) require key of elementRef @@ -214,8 +214,8 @@ - Changes for Pure ODD: - + Changes for Pure ODD: + constrain key of classRef, elementRef, and macroRef constrain include and except of classRef, also @@ -235,9 +235,9 @@ - Add constraint only-1-per, which warns user iff - there are more than 1 elementSpec with the same - ident + Add constraint only-1-per, which warns user iff + there are more than 1 elementSpec with the same + ident @@ -262,11 +262,11 @@ - Added sch:pattern to list of elements allowed inside - constraint. + Added sch:pattern to list of elements allowed inside + constraint. - Remove the new notatedMusic and gb elments. + Remove the new notatedMusic and gb elments. @@ -277,7 +277,7 @@ - Test that required elements are not removed. + Test that required elements are not removed. @@ -288,8 +288,8 @@ - Beefed up prose, then corrections per Julia, including - changing name of language (and thus prefix). + Beefed up prose, then corrections per Julia, including + changing name of language (and thus prefix). @@ -313,18 +313,18 @@ - Constrain ident of classSpec. + Constrain ident of classSpec. - During workshop: - + During workshop: + constrain start of schemaSpec constrain key of elmentRef improve remakrs of constraint so that it correctly reflects that we only permit ISO Schematron constrain content of altIdent, unless it is a child of valItem - + @@ -746,28 +746,37 @@ - + - + required modules - missing one or more of the required modules (tei, core, header, - textstructure). + + missing one or more of the required modules (tei, core, header, textstructure). + @@ -1122,25 +1131,25 @@ - adding altIdent to content model because it was removed from model.identSynonyms - - - - - - - - - - - - - - - - - - + adding altIdent to content model because it was removed from model.identSynonyms + + + + + + + + + + + + + + + + + + @@ -1150,25 +1159,25 @@ - adding altIdent to content model because it was removed from model.identSynonyms - - - - - - - - - - - - - - - - - - + adding altIdent to content model because it was removed from model.identSynonyms + + + + + + + + + + + + + + + + + + @@ -1204,43 +1213,48 @@ - in a customization ODD, the mode= attribute of - ＜elementSpec＞ should be specified - the module= attribute of ＜elementSpec＞ must be specified anytime the mode= is - not 'add' + + + in a customization ODD, the mode= attribute of ＜elementSpec＞ should be specified + + + the module= attribute of ＜elementSpec＞ must be specified anytime the mode= is not 'add' + + - + Current ODD processors will not correctly handle more than one ＜elementSpec＞ with the same @ident + - Removing ＜TEI＞ from your - schema guarantees it is not TEI conformant - Removing ＜teiHeader＞ - from your schema guarantees it is not TEI conformant - Removing ＜fileDesc＞ from - your schema guarantees it is not TEI conformant - Removing ＜titleStmt＞ - from your schema guarantees it is not TEI conformant - Removing ＜title＞ from your - schema guarantees it is not TEI conformant - Removing - ＜publicationStmt＞ from your schema guarantees it is not TEI - conformant - Removing ＜sourceDesc＞ - from your schema guarantees it is not TEI conformant + + Removing ＜TEI＞ from your + schema guarantees it is not TEI conformant + Removing ＜teiHeader＞ + from your schema guarantees it is not TEI conformant + Removing ＜fileDesc＞ from + your schema guarantees it is not TEI conformant + Removing ＜titleStmt＞ + from your schema guarantees it is not TEI conformant + Removing ＜title＞ from your + schema guarantees it is not TEI conformant + Removing + ＜publicationStmt＞ from your schema guarantees it is not TEI + conformant + Removing ＜sourceDesc＞ + from your schema guarantees it is not TEI conformant + - + When adding a new element (whether replacing an old one or not), a content model must be specified; but this ＜elementSpec＞ does not have a ＜content＞ child. @@ -1362,9 +1376,9 @@ - - - + + + @@ -1514,18 +1528,17 @@ - - The @xml:id "" on ＜＞ duplicates an @xml:id found earlier in the document + + + The @xml:id "" on ＜＞ duplicates an @xml:id found earlier in the document + - From e56aacd098f3f415b56358fbd217987b57874ff0 Mon Sep 17 00:00:00 2001 From: Klaus Rettinghaus Date: Thu, 11 Apr 2024 14:06:09 +0200 Subject: [PATCH 052/127] add German descriptions --- P5/Source/Specs/postBox.xml | 3 +++ P5/Source/Specs/postCode.xml | 3 +++ 2 files changed, 6 insertions(+) diff --git a/P5/Source/Specs/postBox.xml b/P5/Source/Specs/postBox.xml index e889aec6a3..9db2797571 100644 --- a/P5/Source/Specs/postBox.xml +++ b/P5/Source/Specs/postBox.xml @@ -8,6 +8,7 @@ boîte postale buzón Casella postale + Postfach contains a number or other identifier for some postal delivery point other than a street address. 주소 이외의 우편 배달 지점을 위한 숫자 또는 다른 확인소를 포함한다. @@ -19,6 +20,8 @@ de entrega postal distinto a una dirección postal. contiene il numero o altro identificatore per un luogo di consegna della posta diverso da un indirizzo postale. + enthält eine Nummer oder eine andere Kennung für eine Postanschrift, + bei der es sich nicht um eine Straßenadresse handelt. diff --git a/P5/Source/Specs/postCode.xml b/P5/Source/Specs/postCode.xml index ec1382a9f7..f02e9dddf4 100644 --- a/P5/Source/Specs/postCode.xml +++ b/P5/Source/Specs/postCode.xml @@ -8,6 +8,7 @@ code postal Código postal Codice di Avviamento Postale + Postleitzahl contains a numerical or alphanumeric code used as part of a postal address to simplify sorting or delivery of mail. 우편의 분류 및 배달을 용이하도록 우편 주소의 일부로 사용되는 숫자 또는 문자와 숫자가 혼용된 @@ -20,6 +21,8 @@ parte de la dirección postal para simplificar la clasificación o entrega de correo. contiene il codice alfanumerico utilizzato nell'indirizzo postale per semplificare l'ordine e la distribuzione della posta. + enthält einen numerischen oder alphanumerischen Schlüssel, + der als Teil einer Postadresse zur Vereinfachung der Sortierung oder Zustellung von Postsendungen verwendet wird. From 50128749da424d5d307586779d458a579a897b8f Mon Sep 17 00:00:00 2001 From: Klaus Rettinghaus Date: Thu, 11 Apr 2024 14:22:21 +0200 Subject: [PATCH 053/127] some more German translations --- P5/Source/Specs/accMat.xml | 1 + P5/Source/Specs/acquisition.xml | 1 + P5/Source/Specs/activity.xml | 1 + P5/Source/Specs/addSpan.xml | 1 + P5/Source/Specs/adminInfo.xml | 1 + P5/Source/Specs/affiliation.xml | 3 +++ P5/Source/Specs/caption.xml | 1 + P5/Source/Specs/case.xml | 2 ++ P5/Source/Specs/castList.xml | 1 + P5/Source/Specs/prologue.xml | 1 + P5/Source/Specs/provenance.xml | 1 + 11 files changed, 14 insertions(+) diff --git a/P5/Source/Specs/accMat.xml b/P5/Source/Specs/accMat.xml index 10aa249263..5b8e5e448f 100644 --- a/P5/Source/Specs/accMat.xml +++ b/P5/Source/Specs/accMat.xml @@ -9,6 +9,7 @@ material adicional materiale allegato 添付資料 + Begleitmaterial contains details of any significant additional material which may be closely associated with the manuscript or object being described, such as non-contemporaneous documents or fragments bound in diff --git a/P5/Source/Specs/acquisition.xml b/P5/Source/Specs/acquisition.xml index 0fa7daab86..4f78ee023d 100644 --- a/P5/Source/Specs/acquisition.xml +++ b/P5/Source/Specs/acquisition.xml @@ -4,6 +4,7 @@ acquisition adquisición acquisition + Akquisition contains any descriptive or other information concerning the process by which a manuscript or manuscript part or other object entered the holding institution. diff --git a/P5/Source/Specs/activity.xml b/P5/Source/Specs/activity.xml index d2a37a1512..41e479420f 100644 --- a/P5/Source/Specs/activity.xml +++ b/P5/Source/Specs/activity.xml @@ -4,6 +4,7 @@ activity actividad activité + Aktivität contains a brief informal description of what a participant in a language interaction is doing other than speaking, if anything. 언어 상호작용 참여자의 발화 외의 다른 행위에 대한 간단한 일상적 기술을 포함한다. diff --git a/P5/Source/Specs/addSpan.xml b/P5/Source/Specs/addSpan.xml index 3cb70524e9..f308457fbf 100644 --- a/P5/Source/Specs/addSpan.xml +++ b/P5/Source/Specs/addSpan.xml @@ -9,6 +9,7 @@ fragmento de texto añadido porzione di testo aggiunta 追加テキストの範囲 + hinzugefügter Textabschnitt marks the beginning of a longer sequence of text added by an author, scribe, annotator or corrector (see also add). 저자, 필기사, 주석자, 또는 교정자에 의해 추가된 긴 연쇄의 텍스트 시작부를 표시한다.(add 참조) 標記由作者、抄寫者、註解者或更正者所加入的較長連續文字之開端 (參照add) 。 diff --git a/P5/Source/Specs/adminInfo.xml b/P5/Source/Specs/adminInfo.xml index 187093982e..b778777787 100644 --- a/P5/Source/Specs/adminInfo.xml +++ b/P5/Source/Specs/adminInfo.xml @@ -9,6 +9,7 @@ información administrativa. informazioni amministrative 管理情報 + administrative Information contains information about the present custody and availability of the manuscript or other object, and also about the record description itself. diff --git a/P5/Source/Specs/affiliation.xml b/P5/Source/Specs/affiliation.xml index 319d91a482..81bc1d5759 100644 --- a/P5/Source/Specs/affiliation.xml +++ b/P5/Source/Specs/affiliation.xml @@ -3,6 +3,7 @@ affiliation affiliation + Affiliation contains an informal description of a person's present or past affiliation with some organization, for example an employer or sponsor. 고용주 또는 후원자와 같이 개인의 현재 또는 과거 소속 조직에 대한 비공식적 기술을 포함한다. @@ -17,6 +18,8 @@ contiene una descrizione informale dell'appartenenza presente o passata di una persona a una determinata organizzazione, per esempio un'azienda o un ente finanziatore + enthält eine informelle Beschreibung der gegenwärtigen + oder früheren Zugehörigkeit einer Person zu einer Organisation, z. B. eines Arbeitgebers oder Sponsors. diff --git a/P5/Source/Specs/caption.xml b/P5/Source/Specs/caption.xml index a4cf82f135..79dd6e5c54 100644 --- a/P5/Source/Specs/caption.xml +++ b/P5/Source/Specs/caption.xml @@ -4,6 +4,7 @@ caption sous-titre + Beschriftung contains the text of a caption or other text displayed as part of a film script or screenplay. 영화 스크립트 또는 시나리오의 일부로서 제시되는 자막 또는 다른 텍스트를 포함한다. diff --git a/P5/Source/Specs/case.xml b/P5/Source/Specs/case.xml index 1e84cdb86a..8a919bdcfe 100644 --- a/P5/Source/Specs/case.xml +++ b/P5/Source/Specs/case.xml @@ -4,6 +4,7 @@ case cas + Fall contains grammatical case information given by a dictionary for a given form. 주어진 형식에 대하여 사전에 제시된 문법적 격 정보를 포함한다. 包含文法上格的資訊。 @@ -11,6 +12,7 @@ contient des informations sur le cas grammatical présenté par le dictionnaire pour une forme donnée. contiene la información del caso gramatical. contiene informazioni grammaticali sul caso fornite dal dizionario per una determinata froma. + enthält grammatikalische Kasusinformationen, die von einem Wörterbuch für eine bestimmte Form geliefert werden. diff --git a/P5/Source/Specs/castList.xml b/P5/Source/Specs/castList.xml index 0c6db4b5d7..f78bd14168 100644 --- a/P5/Source/Specs/castList.xml +++ b/P5/Source/Specs/castList.xml @@ -7,6 +7,7 @@ 角色清單 reparto distribution + Besetzungsliste elenco dei personaggi 配役リスト contains a single cast list or dramatis personae. diff --git a/P5/Source/Specs/prologue.xml b/P5/Source/Specs/prologue.xml index abdfb7e041..877cafbdd1 100644 --- a/P5/Source/Specs/prologue.xml +++ b/P5/Source/Specs/prologue.xml @@ -4,6 +4,7 @@ prologue prologue + Prolog contains the prologue to a drama, typically spoken by an actor out of character, possibly in association with a particular performance or venue. 전형적으로 등장인물들 중 하나가 말하는, 때로는 특정 공연 또는 행위의 현장과 관련된, 드라마의 diff --git a/P5/Source/Specs/provenance.xml b/P5/Source/Specs/provenance.xml index 71b78766da..2c5a6ebbcd 100644 --- a/P5/Source/Specs/provenance.xml +++ b/P5/Source/Specs/provenance.xml @@ -3,6 +3,7 @@ provenance provenance + Provenienz contains any descriptive or other information concerning a single identifiable episode during the history of a manuscript, manuscript part, or other object after its creation but before its acquisition. 생성된 후부터 획득되기 전까지 원고 또는 원고 일부의 이력에 대해 확인가능한 에피소드에 관련한 기술적 또는 기타 정보를 포함한다. From 53dad9ea059b55f309cf4ca898258ea92ab5763b Mon Sep 17 00:00:00 2001 From: Klaus Rettinghaus Date: Thu, 11 Apr 2024 15:31:24 +0200 Subject: [PATCH 054/127] unify order of attributes (#2545) --- P5/Source/Specs/acquisition.xml | 6 +++--- P5/Source/Specs/addSpan.xml | 4 ++-- P5/Source/Specs/affiliation.xml | 10 +++++----- P5/Source/Specs/caption.xml | 6 +++--- P5/Source/Specs/case.xml | 6 +++--- 5 files changed, 16 insertions(+), 16 deletions(-) diff --git a/P5/Source/Specs/acquisition.xml b/P5/Source/Specs/acquisition.xml index 0fa7daab86..d1712e07f2 100644 --- a/P5/Source/Specs/acquisition.xml +++ b/P5/Source/Specs/acquisition.xml @@ -1,8 +1,8 @@ - acquisition - adquisición + acquisition + adquisición acquisition contains any descriptive or other information concerning the process by which a manuscript or manuscript part or other object entered the holding @@ -34,7 +34,7 @@ institution. date represented by the content of this element belongs. 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. indica el sistema o calendario en que se muestra diff --git a/P5/Source/Specs/addSpan.xml b/P5/Source/Specs/addSpan.xml index 3cb70524e9..719e68f18c 100644 --- a/P5/Source/Specs/addSpan.xml +++ b/P5/Source/Specs/addSpan.xml @@ -74,11 +74,11 @@ end by the spanTo attribute.

Tanto el inicio como el final del material que se agrego debe ser marcado; el inicio con el mismo elemento addSpan y el final con el atributo spanTo.

 - +

Le début et la fin de la partie de texte ajoutée doivent être marqués ; le début, par l'élément addSpan lui-même, la fin, par l'attribut spanTo.

 - +

追加する情報の始めと終わりの両方にマークアップすべきである。 始めは、要素addSpan自身によって、終わりは属性 diff --git a/P5/Source/Specs/affiliation.xml b/P5/Source/Specs/affiliation.xml index 319d91a482..3932f4df14 100644 --- a/P5/Source/Specs/affiliation.xml +++ b/P5/Source/Specs/affiliation.xml @@ -1,7 +1,7 @@ - affiliation + affiliation affiliation contains an informal description of a person's present or past affiliation with some organization, for example an employer or sponsor. @@ -41,7 +41,7 @@ date represented by the content of this element belongs. 날짜 표현 시스템 또는 달력 표시 형식을 표시한다. 指明該日期表示所使用的曆法計算系統。 - この要素を含むコンテントにおける日付の暦やシステムを示す。 + この要素を含むコンテントにおける日付の暦やシステムを示す。 indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. indica el sistema o calendario en que se muestra @@ -82,7 +82,7 @@ - +

This example indicates that the person was affiliated with the Australian Journalists Association at some point between the dates listed.

@@ -92,7 +92,7 @@ - +

This example indicates that the person was affiliated with Mount Holyoke College throughout the entire span of the date range listed.

Was an assistant professor at Mount Holyoke College. @@ -124,7 +124,7 @@ name comme ci-dessus, soit l'élément plus spécifique orgName.

 - +

組織名は、要素nameまたは、より特化した要素 orgNameでマークアップした方がよい。

diff --git a/P5/Source/Specs/caption.xml b/P5/Source/Specs/caption.xml index a4cf82f135..4201b00b52 100644 --- a/P5/Source/Specs/caption.xml +++ b/P5/Source/Specs/caption.xml @@ -2,7 +2,7 @@ - caption + caption sous-titre contains the text of a caption or other text displayed as part of a film script or screenplay. @@ -65,10 +65,10 @@ laughing affectedly and drinking champagne.

A specialized form of stage direction.

 - +

Forme particulière d'indication scénique.

 - +

ト書きの特別な形。

 diff --git a/P5/Source/Specs/case.xml b/P5/Source/Specs/case.xml index 1e84cdb86a..20f6ca4a42 100644 --- a/P5/Source/Specs/case.xml +++ b/P5/Source/Specs/case.xml @@ -2,7 +2,7 @@ - case + case cas contains grammatical case information given by a dictionary for a given form. 주어진 형식에 대하여 사전에 제시된 문법적 격 정보를 포함한다. @@ -91,7 +91,7 @@ dative, genitive, etc.

This element is synonymous with gram type="case".

 - +

Peut contenir des caractères et des éléments du niveau expression. Les valeurs types seront nominative, accusative, dative, @@ -99,7 +99,7 @@

Cet élément est synonyme degram type="case"

- +

文字データまたは句レベルの要素。典型的な値は、 nominative(主格)、accusative(対格)、dative(与格)、genitive(属格) From d16c7979061dc0083a4f118a3bef229e8c8708b6 Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Fri, 12 Apr 2024 16:16:38 -0400 Subject: [PATCH 055/127] Fix several remaining contextless assertions & reports --- P5/Exemplars/tei_enrich.odd | 7 +- P5/Exemplars/tei_simplePrint.odd | 44 ++++++----- P5/Test/testmeta2010.odd | 7 +- P5/Utilities/TEI-to-tei_customization.xslt | 92 ++++++++++++---------- P5/p5odds.odd | 10 ++- 5 files changed, 93 insertions(+), 67 deletions(-) diff --git a/P5/Exemplars/tei_enrich.odd b/P5/Exemplars/tei_enrich.odd index 113fa12ff5..ef8361356e 100644 --- a/P5/Exemplars/tei_enrich.odd +++ b/P5/Exemplars/tei_enrich.odd @@ -3453,8 +3453,11 @@ which should be supported by a more detailed description using the - - You must provide either @when or @to/@from, or @notAfter/@notBefore. + + + You must provide either @when or @to/@from, or @notAfter/@notBefore. + + diff --git a/P5/Exemplars/tei_simplePrint.odd b/P5/Exemplars/tei_simplePrint.odd index 58c8e49a31..7dd26e0d14 100644 --- a/P5/Exemplars/tei_simplePrint.odd +++ b/P5/Exemplars/tei_simplePrint.odd @@ -3484,8 +3484,13 @@ live without God in the world, and only mind earthly things. + + value="for $t in tokenize(normalize-space(@target),'\s+') return starts-with($t,'#') and not(id(substring($t,2)))"/> Error: Every local pointer in "" must point to an ID in this document () @@ -3997,8 +4002,11 @@ live without God in the world, and only mind earthly things. - Element - "" may not be empty. + + + Element "" may not be empty. + + @@ -4112,26 +4120,24 @@ live without God in the world, and only mind earthly things. - Element "" must have at least two child elements. + + + Element "" must have at least two child elements. + + - - Element "" must have corresponding corr/sic, expand/abbr, reg/orig + + + Element "" must have corresponding corr/sic, expand/abbr, reg/orig + + diff --git a/P5/Test/testmeta2010.odd b/P5/Test/testmeta2010.odd index b7b011b5f0..b48063547c 100644 --- a/P5/Test/testmeta2010.odd +++ b/P5/Test/testmeta2010.odd @@ -51,9 +51,10 @@ - list - too short + + list too short + + diff --git a/P5/Utilities/TEI-to-tei_customization.xslt b/P5/Utilities/TEI-to-tei_customization.xslt index a7c9400eb7..2f2cc7d821 100644 --- a/P5/Utilities/TEI-to-tei_customization.xslt +++ b/P5/Utilities/TEI-to-tei_customization.xslt @@ -53,6 +53,10 @@ + + Added sch:rule elements PRN to avoid new warning + about contextless Schematron. + Remove the altIdent-only-NCName @@ -758,16 +762,17 @@ required modules - missing one or more of the required modules (tei, core, header, - textstructure). + + missing one or more of the required modules (tei, core, header, textstructure). + @@ -1204,38 +1209,44 @@ - in a customization ODD, the mode= attribute of - ＜elementSpec＞ should be specified - the module= attribute of ＜elementSpec＞ must be specified anytime the mode= is - not 'add' + + + in a customization ODD, the mode= attribute of ＜elementSpec＞ should be specified + + + the module= attribute of ＜elementSpec＞ must be specified anytime the mode= is not 'add' + + - Current ODD processors will not correctly handle more than one ＜elementSpec＞ with the same @ident + + + Current ODD processors will not correctly handle more than one ＜elementSpec＞ with the same @ident + + - Removing ＜TEI＞ from your - schema guarantees it is not TEI conformant - Removing ＜teiHeader＞ - from your schema guarantees it is not TEI conformant - Removing ＜fileDesc＞ from - your schema guarantees it is not TEI conformant - Removing ＜titleStmt＞ - from your schema guarantees it is not TEI conformant - Removing ＜title＞ from your - schema guarantees it is not TEI conformant - Removing - ＜publicationStmt＞ from your schema guarantees it is not TEI - conformant - Removing ＜sourceDesc＞ - from your schema guarantees it is not TEI conformant + + Removing ＜TEI＞ from your + schema guarantees it is not TEI conformant + Removing ＜teiHeader＞ + from your schema guarantees it is not TEI conformant + Removing ＜fileDesc＞ from + your schema guarantees it is not TEI conformant + Removing ＜titleStmt＞ + from your schema guarantees it is not TEI conformant + Removing ＜title＞ from your + schema guarantees it is not TEI conformant + Removing + ＜publicationStmt＞ from your schema guarantees it is not TEI + conformant + Removing ＜sourceDesc＞ + from your schema guarantees it is not TEI conformant + @@ -1514,18 +1525,19 @@ - - The @xml:id "" on ＜＞ duplicates an @xml:id found earlier in the document + + + The @xml:id "" on ＜＞ duplicates an @xml:id found earlier in the document + - diff --git a/P5/p5odds.odd b/P5/p5odds.odd index 70b7db60eb..60885698a4 100644 --- a/P5/p5odds.odd +++ b/P5/p5odds.odd @@ -183,8 +183,10 @@ $Id$ if you really want a newline at the end, follow it with U+00A0. - trailing newline not allowed - leading newline not allowed + + trailing newline not allowed + leading newline not allowed + @@ -740,7 +742,9 @@ $Id$ - The <altIdent> element should only be used as a child of <elementSpec>, <attDef>, or <valItem>. + + The <altIdent> element should only be used as a child of <elementSpec>, <attDef>, or <valItem>. + From 6f121507eb408fa03da8ccf1ae531743edb666ac Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Fri, 15 Mar 2024 11:45:33 -0400 Subject: [PATCH 056/127] =?UTF-8?q?initial=20creation=20of=20branch=20for?= =?UTF-8?q?=20work=20on=20the=20CMC-SIG=E2=80=99s=20new=20chapter=20(#2535?= =?UTF-8?q?)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * initial commit of new specs * lower-case model name * bibliography additions for CMC * add listRef and remove bibl references we don't do these bibl references here, do we? might go into a remalr, though? * migrate chapter from GoogleDoc * fix minor quirks * add membership to `att.cmc` * Various minor: * add xml:id= attrs to divisions (may not have all names right) * un-comment ref to character entry * change comments about work-to-be-done to processing instructions (yes, "winita" = “work is needed in this area” is obtuse, but it is what we use in the rest of the Guidelines) * in a few cases, changed quotation marks to phrase-level encoding * Re-generated spec lists. * testing * another test * Get build _almost_ working * Re-generated spec lists. * Fix a dozen validity errs. * fixes in exemplums: generation->generatedBy; closed

before and added rend=inline to the latter; added # to @synch and @who values; removed @who from and

` * update `xml:id`s on `` elements * example code for 9.3.2.1.3, and fixed several typos * section CMCanalysis * improved IDs in sect. analyses * Re-generated spec lists. * sections on analysis and multimodal * bib entries * correction emphasis * Pull in latest from TEI dev branch (including manual merge of docDate.xml), and correct a duplicate ID * Updates, mostly of REF placeholders * Add a PI reminding us to move a ref to bibl * Various minor edits, mostly made w/ CMC group during mtg * mocoda example for multimodal CMC 1st version * section and example with spoken/written/image post in encoding of multimodal cmc * Various updates, including constrain @generateBy to use within 'post' element * Updated another reference to 'children' of post element to descendants * entries mocoda, scilog * fixed timeline; improved bibliography, references and examples as specified in minutes * Add comment warning: need to use Schematron processor that can handle attribute context nodes. Note that I have not committed and pushed the addition of tests of the generatedBy= attribute in detest.xml, as it will break the build until it (the TEI build process) uses a Schematron processor that can handle. * more multimodal CMC and fixed some typos * promoted section Named Entities to 9.5.5 * Added tests for @generatedBy * Minor updates made at CMC meeting. * Invalid version we are in the middle of working on (particularly anonyization) * some typos * changed @corresp in @ref in example * fixed bib entries for corpora * extended section on NEs by pseudonymisation example using gap and supplied * some typos * some typos * fixed typo * restructuring of sections * some final typos * Fixes made during 2023-12-09 meeting with Harald * Editing pass through chapter; fix detest * addressed tei winita's by Syd, changed twitter examples by removing occurrences of and references to @key * some smithing re early CMC systems * use ptr for retweets and adapted descriptions * Minor wording (and whitespace) updates * minor tweaks, mostly removing previous questions that have been answered * Re-write last sentence of 9.5.5 and lots of spelling corrextions. * Tweak wording with Harald & Michael * Mostly typo corrections --------- Co-authored-by: Peter Stadler Co-authored-by: peterstadler Co-authored-by: Harald Luengen Co-authored-by: luengen --- P5/Exemplars/tei_all.odd | 27 +- P5/Exemplars/tei_allPlus.odd | 27 +- P5/Exemplars/tei_basic.odd | 27 +- P5/Source/Guidelines/en/BIB-Bibliography.xml | 351 ++++- .../en/CMC-ComputerMediatedCommunication.xml | 1302 +++++++++++++++++ .../en/Images/cmcunits-taxonomy.png | Bin 0 -> 24066 bytes .../en/Images/cmcunits-taxonomy.pptx | Bin 0 -> 39218 bytes P5/Source/Guidelines/en/ST-Infrastructure.xml | 2 + P5/Source/Specs/ab.xml | 1 + P5/Source/Specs/abbr.xml | 1 + P5/Source/Specs/add.xml | 1 + P5/Source/Specs/addName.xml | 1 + P5/Source/Specs/address.xml | 1 + P5/Source/Specs/affiliation.xml | 1 + P5/Source/Specs/alt.xml | 1 + P5/Source/Specs/altGrp.xml | 1 + P5/Source/Specs/anchor.xml | 1 + P5/Source/Specs/argument.xml | 1 + P5/Source/Specs/att.cmc.xml | 145 ++ P5/Source/Specs/bibl.xml | 1 + P5/Source/Specs/biblFull.xml | 1 + P5/Source/Specs/biblStruct.xml | 1 + P5/Source/Specs/binaryObject.xml | 1 + P5/Source/Specs/bloc.xml | 1 + P5/Source/Specs/byline.xml | 1 + P5/Source/Specs/c.xml | 1 + P5/Source/Specs/cb.xml | 1 + P5/Source/Specs/choice.xml | 1 + P5/Source/Specs/cit.xml | 1 + P5/Source/Specs/cl.xml | 1 + P5/Source/Specs/climate.xml | 1 + P5/Source/Specs/closer.xml | 1 + P5/Source/Specs/corr.xml | 1 + P5/Source/Specs/country.xml | 1 + P5/Source/Specs/date.xml | 1 + P5/Source/Specs/dateline.xml | 1 + P5/Source/Specs/del.xml | 1 + P5/Source/Specs/desc.xml | 1 + P5/Source/Specs/distinct.xml | 1 + P5/Source/Specs/district.xml | 1 + P5/Source/Specs/docAuthor.xml | 1 + P5/Source/Specs/docDate.xml | 1 + P5/Source/Specs/email.xml | 1 + P5/Source/Specs/emph.xml | 1 + P5/Source/Specs/epigraph.xml | 1 + P5/Source/Specs/expan.xml | 1 + P5/Source/Specs/fLib.xml | 1 + P5/Source/Specs/figure.xml | 1 + P5/Source/Specs/floatingText.xml | 1 + P5/Source/Specs/foreign.xml | 1 + P5/Source/Specs/forename.xml | 1 + P5/Source/Specs/formula.xml | 1 + P5/Source/Specs/fs.xml | 1 + P5/Source/Specs/fvLib.xml | 1 + P5/Source/Specs/gap.xml | 1 + P5/Source/Specs/gb.xml | 1 + P5/Source/Specs/genName.xml | 1 + P5/Source/Specs/geo.xml | 1 + P5/Source/Specs/geogFeat.xml | 3 +- P5/Source/Specs/geogName.xml | 1 + P5/Source/Specs/gloss.xml | 1 + P5/Source/Specs/graphic.xml | 8 +- P5/Source/Specs/head.xml | 1 + P5/Source/Specs/hi.xml | 1 + P5/Source/Specs/idno.xml | 1 + P5/Source/Specs/incident.xml | 1 + P5/Source/Specs/index.xml | 1 + P5/Source/Specs/interp.xml | 1 + P5/Source/Specs/interpGrp.xml | 1 + P5/Source/Specs/join.xml | 1 + P5/Source/Specs/joinGrp.xml | 1 + P5/Source/Specs/kinesic.xml | 1 + P5/Source/Specs/l.xml | 1 + P5/Source/Specs/label.xml | 1 + P5/Source/Specs/lb.xml | 1 + P5/Source/Specs/lg.xml | 1 + P5/Source/Specs/link.xml | 1 + P5/Source/Specs/linkGrp.xml | 1 + P5/Source/Specs/list.xml | 1 + P5/Source/Specs/listBibl.xml | 1 + P5/Source/Specs/listEvent.xml | 1 + P5/Source/Specs/listNym.xml | 1 + P5/Source/Specs/listObject.xml | 1 + P5/Source/Specs/listOrg.xml | 1 + P5/Source/Specs/listPerson.xml | 1 + P5/Source/Specs/listPlace.xml | 1 + P5/Source/Specs/listRelation.xml | 1 + P5/Source/Specs/location.xml | 1 + P5/Source/Specs/m.xml | 1 + P5/Source/Specs/macro.specialPara.cmc.xml | 29 + P5/Source/Specs/measure.xml | 1 + P5/Source/Specs/measureGrp.xml | 1 + P5/Source/Specs/media.xml | 1 + P5/Source/Specs/meeting.xml | 1 + P5/Source/Specs/mentioned.xml | 1 + P5/Source/Specs/milestone.xml | 1 + P5/Source/Specs/model.cmc.xml | 20 + P5/Source/Specs/name.xml | 1 + P5/Source/Specs/nameLink.xml | 1 + P5/Source/Specs/notatedMusic.xml | 1 + P5/Source/Specs/note.xml | 1 + P5/Source/Specs/noteGrp.xml | 1 + P5/Source/Specs/num.xml | 1 + P5/Source/Specs/objectName.xml | 1 + P5/Source/Specs/offset.xml | 3 +- P5/Source/Specs/opener.xml | 1 + P5/Source/Specs/orgName.xml | 1 + P5/Source/Specs/orig.xml | 1 + P5/Source/Specs/p.xml | 1 + P5/Source/Specs/pause.xml | 1 + P5/Source/Specs/pb.xml | 1 + P5/Source/Specs/pc.xml | 1 + P5/Source/Specs/persName.xml | 1 + P5/Source/Specs/persPronouns.xml | 1 + P5/Source/Specs/phr.xml | 1 + P5/Source/Specs/placeName.xml | 1 + P5/Source/Specs/population.xml | 1 + P5/Source/Specs/post.xml | 252 ++++ P5/Source/Specs/postscript.xml | 1 + P5/Source/Specs/ptr.xml | 1 + P5/Source/Specs/q.xml | 1 + P5/Source/Specs/quote.xml | 1 + P5/Source/Specs/ref.xml | 1 + P5/Source/Specs/reg.xml | 1 + P5/Source/Specs/region.xml | 1 + P5/Source/Specs/roleName.xml | 1 + P5/Source/Specs/rs.xml | 1 + P5/Source/Specs/ruby.xml | 3 +- P5/Source/Specs/s.xml | 1 + P5/Source/Specs/said.xml | 1 + P5/Source/Specs/salute.xml | 1 + P5/Source/Specs/seg.xml | 1 + P5/Source/Specs/settlement.xml | 1 + P5/Source/Specs/shift.xml | 1 + P5/Source/Specs/sic.xml | 1 + P5/Source/Specs/signed.xml | 1 + P5/Source/Specs/soCalled.xml | 1 + P5/Source/Specs/span.xml | 1 + P5/Source/Specs/spanGrp.xml | 1 + P5/Source/Specs/stage.xml | 1 + P5/Source/Specs/state.xml | 1 + P5/Source/Specs/surname.xml | 1 + P5/Source/Specs/table.xml | 3 +- P5/Source/Specs/term.xml | 1 + P5/Source/Specs/terrain.xml | 1 + P5/Source/Specs/time.xml | 1 + P5/Source/Specs/timeline.xml | 1 + P5/Source/Specs/title.xml | 1 + P5/Source/Specs/trailer.xml | 1 + P5/Source/Specs/trait.xml | 1 + P5/Source/Specs/unclear.xml | 3 +- P5/Source/Specs/unit.xml | 1 + P5/Source/Specs/vocal.xml | 1 + P5/Source/Specs/w.xml | 1 + P5/Source/Specs/writing.xml | 1 + P5/Source/guidelines-en.xml | 1 + P5/Test/detest.odd | 1 + P5/Test/detest.xml | 25 +- .../expected-results/detest_xml_relaxng.log | 34 +- P5/p5odds-examples.odd | 13 +- P5/p5odds.odd | 2 + P5/spec_lists.json | 2 +- 162 files changed, 2300 insertions(+), 120 deletions(-) create mode 100644 P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml create mode 100644 P5/Source/Guidelines/en/Images/cmcunits-taxonomy.png create mode 100644 P5/Source/Guidelines/en/Images/cmcunits-taxonomy.pptx create mode 100644 P5/Source/Specs/att.cmc.xml create mode 100644 P5/Source/Specs/macro.specialPara.cmc.xml create mode 100644 P5/Source/Specs/model.cmc.xml create mode 100644 P5/Source/Specs/post.xml diff --git a/P5/Exemplars/tei_all.odd b/P5/Exemplars/tei_all.odd index 2e7d468ea8..997b87b938 100644 --- a/P5/Exemplars/tei_all.odd +++ b/P5/Exemplars/tei_all.odd @@ -70,19 +70,20 @@ - - - - - - - - - - - - - + + + + + + + + + + + + + + diff --git a/P5/Exemplars/tei_allPlus.odd b/P5/Exemplars/tei_allPlus.odd index 27b61d2892..89b5137dec 100644 --- a/P5/Exemplars/tei_allPlus.odd +++ b/P5/Exemplars/tei_allPlus.odd @@ -70,19 +70,20 @@ - - - - - - - - - - - - - + + + + + + + + + + + + + + ERROR: cannot locate ODD changes for SVG diff --git a/P5/Exemplars/tei_basic.odd b/P5/Exemplars/tei_basic.odd index 924d39f7f8..03823d520d 100644 --- a/P5/Exemplars/tei_basic.odd +++ b/P5/Exemplars/tei_basic.odd @@ -4,7 +4,8 @@ TEI Basic - Hugh Cayless + Hugh Cayless + Syd Bauman TEI Consortium @@ -23,6 +24,9 @@

Derived from TEI All.

+ + Added CMC and re-numbered accordingly. + @@ -42,16 +46,17 @@ - - - - - - - - - + + + + + + + + + + - \ No newline at end of file + diff --git a/P5/Source/Guidelines/en/BIB-Bibliography.xml b/P5/Source/Guidelines/en/BIB-Bibliography.xml index afcbd6e9e5..c2044de1aa 100644 --- a/P5/Source/Guidelines/en/BIB-Bibliography.xml +++ b/P5/Source/Guidelines/en/BIB-Bibliography.xml @@ -5,7 +5,6 @@ Bibliography
Works Cited in Examples in these Guidelines - 阿城，《棋王》。 Académie française, @@ -14,8 +13,8 @@ consulté le 05-03-2010. Adams, Douglas. The Hitchhiker's Guide to the - Galaxy, New York: Pocket Books, 1979, - chapter 31. + Galaxy, New York: Pocket Books, + 1979, chapter 31. Agence bibliographique de l'enseignement supérieur, ABES:Site internet @@ -73,9 +72,8 @@ 白居易，《憶江南》。 Amheida I: Ostraka from Trimithis Volume 1: Texts from the 2004–2007 Seasons, - Bagnall, R. S. and G. R. Ruffini, with contributions by R. Cribiore and G. Vittmann - (2012). - + Bagnall, R. S. and G. R. Ruffini, with contributions by R. Cribiore and G. + Vittmann (2012). Baker, James K.. Night in Tarras. In Hilltop: A Literary Paper, vol 1 no 2. Wellington: Victoria University College @@ -120,8 +118,9 @@ Bowers, Jack Mixtepec-Mixtec Project Personography - - + + Beerbohm, Max. Autograph manuscript of The Golden Drugget, @@ -130,7 +129,7 @@ (1697). Beeton, Isabella. The book of Household Management, - London: S.O. Beeton + London: S.O. Beeton (1861). Belloc, Denis , Képas, 1989. @@ -184,12 +183,11 @@ Extract from British National Corpus () Text KB7, sentence 13730. - Brontë, Charlotte. Jane Eyre: An Autobiography, - Third edition; reprintLondon - Service & Paton, 1897; - Project Gutenberg, 1 December 2020. - chapter XII. - + Brontë, Charlotte. Jane Eyre: An Autobiography, + Third edition; reprintLondon + Service & Paton, 1897; Project + Gutenberg, 1 December 2020. chapter + XII. Browning, Robert. Letter to George Moulton-Barrett, Pierpont @@ -260,8 +258,8 @@ Writers Project, Northeastern University. 29 Mar. 2015. + temporarily removed until #1564 is resolved, i.e. WWP puts this somewhere that is not + behind paywall. -->. Centre national de la recherche scientifique (France). UMR 7118 ATILF, <ref target="http://atilf.atilf.fr/tlf.htm">Le Trésor de la Langue Française Informatisé (TLFI)</ref>, @@ -328,8 +326,8 @@ l'école, 1900. Collins English Dictionary, 12th edition - Glasgow: Collins - (2014). + Glasgow: Collins (2014). Collins Pocket Dictionary of the English language. London: Collins. @@ -664,7 +662,10 @@ (1959). Harvey, Gabriel. Four letters and certain sonnets specially touching Robert Greene... (1592). - Harvey, William. Exercitatio Anatomica De Motu Cordis Et Sanguinis In Animalibus, 1949 (Third edition, second printing), p. 74. + Harvey, William. Exercitatio Anatomica De Motu + Cordis Et Sanguinis In Animalibus, 1949 (Third edition, second + printing), p. 74. Hobbes, Thomas. Leviathan (1681). 《紅樓夢》第六回：賈寶玉初試云雨情 劉姥姥一進榮國府 @@ -695,8 +696,9 @@ ISO 690:1987: Information and documentation – Bibliographic references – Content, form and structure clause 4.1, p.2. - ISO 24611:2012 Language resource management — Morpho-syntactic annotation framework (MAF). - International Organization for Standardization. 2012. + ISO 24611:2012 Language resource management — + Morpho-syntactic annotation framework (MAF). International Organization + for Standardization. 2012. Ibsen, Henrik, tr. William and Charles Archer. Peer Gynt (1875). @@ -729,7 +731,7 @@ Institut de Littérature Française Moderne de l’Université de Neuchâtel, Présentation du projet Cyrus, En ligne, consulté le - 05-03-2010. + 05-03-2010. Ionesco, Eugène, La cantatrice chauve, 1950. 羅貫中，《三國演義》。 @@ -1002,7 +1004,8 @@ Parachute: The Highest Falls People Survived, Statista, November 18, 2020. . + />. + McCarty, Willard. Introduction in Collaborative Research in the Digital Humanities: A volume in honour of Harold Short on the occasion of his 65th @@ -1028,7 +1031,7 @@ Milton, John. Paradise Lost: A poem in X books (1667), I, 1-10. - Milton, John. Poems of Mr John Milton, both + <bibl xml:id="miltPo"><author>Milton, John</author>. <title>Poems of Mr John Milton, both English and Latin... (1645). Molière, L'École des femmes, 1663. @@ -1057,9 +1060,10 @@ Tervooren eds. 36., neugestaltete und erweiterte Auflage I Texte, Stuttgart: S. Hirzel Verlag, 1977. - Mošin, Vladimir A. Anchor Watermarks. - Amsterdam: Paper Publications Society (Labarre Foundation), 1973. - Monumenta Chartæ Papyraceæ Historiam Illustrantia; v. 13. + Mošin, Vladimir A. Anchor + Watermarks. Amsterdam: Paper Publications Society + (Labarre Foundation), 1973. Monumenta Chartæ Papyraceæ + Historiam Illustrantia; v. 13. Mréjen, Valérie, Eau sauvage, 2004. @@ -1078,13 +1082,11 @@ The New Penguin English Dictionary. London: Penguin Books (1986). - - Derived from - New Zealand Parliament, Legislative Council. Nga Korero Paramete: 1881-1885 - (New Zealand Electronic Text Collection). 2008 - Wellington, New Zealand. - . - + Derived from New Zealand Parliament, Legislative + Council. Nga Korero Paramete: 1881-1885 (New + Zealand Electronic Text Collection). 2008 + Wellington, New Zealand. . Njal's saga. tr. Magnus Magnusson and Hermann Palsson. Penguin. (1960), chapter @@ -1150,9 +1152,10 @@ >p.22. Pernoud, Régine, La Femme au temps des Cathédrales, 1982. - Perreault, Simon, vCard Format Specification - Internet Engineering Task Force (IETF) (2011). - . + Perreault, Simon, vCard Format + Specification + Internet Engineering Task Force (IETF) (2011). . Petit Larousse en Couleurs. Paris: Larousse, (1990). @@ -1229,9 +1232,10 @@ Boucle, 1993. Rowling, J. K. The Sorting Hat. In Harry Potter and the - Sorcerer's Stone, New York: Scholastic, Inc. (1999), chapter - 7, p. 121. - + Sorcerer's Stone, New York: Scholastic, + Inc. (1999), chapter 7, + p. 121. + @@ -1248,7 +1252,7 @@ 崎山理. 1985 インドネシア語. 講座日本語学 11. 外国語との対照II. - 東京:明治書院 + 東京:明治書院 61-80 三毛，〈沙漠中的飯店〉，《撒哈拉的故事》。 @@ -1382,7 +1386,8 @@ TEI Consortium Call for Papers - TEI 2022 Newcastle, 2022. + target="https://web.archive.org/web/20220516140643/https://conferences.ncl.ac.uk/tei2022/cfp/" + /> The Castle of the Fly, in Russian Fairy Tales, translated by Norbert Guterman from the collections of Aleksandr Afanas'ev, illustrations by @@ -1422,11 +1427,11 @@ (1990). - Ukraine Relief Fund + Ukraine Relief Fund UBS . - + target="https://web.archive.org/web/20220307150159/https://www.ubs.com/global/en/ubs-society/philanthropy/optimus-foundation/ukrainerelief.html" + />. United States Code Title 17, Section 107, found at . @@ -1555,6 +1560,12 @@
Works Cited Elsewhere in the Text of these Guidelines + + Scott E. Fahlman + "Joke" Conversation Thread in which the :-) Was Invented + + + @@ -1609,7 +1620,8 @@ Rubin Gayle - The Traffic in Women: Notes on the <q>Political Economy</q> of Sex + The Traffic in Women: Notes on the <q>Political Economy</q> of + Sex @@ -1658,6 +1670,248 @@ 22–25 + + + + + Michael + Beißwenger + + + Thomas + Bartz + + + Angelika + Storrer + + + Swantje + Westpfahl + + Tagset and guidelines for the PoS tagging of language data from genres of + computer-mediated communication / social media + + + 2015-09-13 + EmpiriST + 2015 Task Force: Michael Beißwenger, Kay-Michael Würzner, Sabine Bartsch, + Stefan Evert + + + + + + + + Michael + Beißwenger + + + Harald + Lüngen + + CMC-core: a schema for the representation of CMC corpora in TEI + + + + Corpus 20 (Special issue "Traitements, standardisation et analyse des + corpus de communication médiée par les réseaux sociaux) + Céline Poudat + Ciara R. Wigham + Loïc Liégeois + + 2020 + + + + + + Gerry and demolog + Blog comments to "Scheinzwerge oder Viele Probleme werden größer, wenn man sie + anpackt (Griechenland)" + https://scilogs.spektrum.de/wild-dueck-blog/scheinzwerge-oder-viele-probleme-werden-groesser-wenn-man-sie-anpackt-griechenland/ + 29-30 July 2015 + + + WILD DUECK BLOG + Gunter Dück + + https://scilogs.spektrum.de/wild-dueck-blog/ + + + SciLogs + + + Jossi et al. (2006-): Talk:Eiffel + (programming language)/Archive_1. URL: https://en.wikipedia.org/wiki/Talk:Eiffel_(programming_language)/Archive_1. English + Wikipedia talk page, Wikimedia Foundation. + + MiszaBot I et al. (2011-): Talk:Astronomical object. URL: https://en.wikipedia.org/wiki/Talk:Astronomical_object. English Wikipedia talk + page, Wikimedia Foundation. + + OnkelSchuppig et al. (2001-): Diskussion:FKM-Richtlinie. URL: https://de.wikipedia.org/wiki/Diskussion:FKM-Richtlinie. German Wikipedia talk + page, Wikimedia Foundation. + + + + Mobile Communication Database 2 (MoCoDa2) + + Michael + Beißwenger + + + Evelyn + Ziegler + + + Marcel + Fladrich + + + Wolfgang + Imo + + + Katharina + König + + + + https://db.mocoda2.de/c/home + + visited 30 March 2022 + + + + + + + Dortmund Chat Corpus + + Angelika + Storrer + + + Michael + Beißwenger + + + + http://hdl.handle.net/10932/00-03B0-14FA-A8D0-0F01-F + + 2017 + Leibniz-Institut für Deutsche Sprache + + + + + + + + Chanier + Thierry + + + Poudat + Céline + + + Sagot + Benoit + + + Antoniadis + Georges + + + Wigham + Ciara R. + + + Hriba + Linda + + + Longhi + Julien + + + Seddah + Djamé + + The CoMeRe corpus for French: structuring and annotating heterogeneous CMC + genres + + + JLCL (Journal of Language Technology and Computational Linguistics) (Special issue + on « Building And Annotating Corpora Of Computer-Mediated Discourse: Issues and + Challenges at the Interface of Corpus and Computational Linguistics) + + http://www.jlcl.org/2014_Heft2/Heft2-2014.pdf + 2014 + + 2 + 1-31 + + + + + + + Louis Alexander + Cotgrove + + Nottinghamer Korpus Deutscher YouTube-Sprache (The NottDeuYTSch Corpus) + + + http://hdl.handle.net/11372/LRT-4806 + + LINDAT/CLARIAH-CZ + 2018 + + + + + + + + + Ciara + Wigham + + + Thierry + Chanier + + Interactions between text chat and audio modalities for L2 communication and + feedback in the synthetic world Second Life + 10.1080/09588221.2013.851702 + + + Computer Assisted Language Learning + + 2015 + + 23 + 3 + + + @@ -3375,7 +3629,7 @@ International Organization for Standardization - ISO 8601:2004: Data elements and interchange formats — Information interchange — + <title>ISO 8601:2004: Data elements and interchange formats — Information interchange — Representation of dates and times 2004 @@ -4431,7 +4685,6 @@ + +
+ Computer-mediated Communication +

This chapter describes the TEI encoding mechanisms available for textual data which represents + discourse from genres of computer-mediated communication (CMC). It is intended to provide the + basic framework needed to encode CMC corpora.

+
+ General Considerations and Overview +

While the term computer-mediated communication, in a broader sense, might be used to + describe all sorts of communications between humans which are mediated by digital technologies + (for example, text on web pages, dialogic written interaction in chats and forums, the spoken + language in internet video meetings), herein we use the term to apply to forms of + communication which share the following features: + they are dialogic; + they are organized in the form of interactional sequences so that each communicative + move may determine the context for subsequent moves (typically taken by another + interlocutor) and may react to the context created by a prior move; + the communicative moves which may be put into practice as posts (cf. ), utterances, onscreen activities, or bodily activities exerted + by a virtual avatar are created and displayed using computer + technology (keyboard, mouse, speech-to-text conversion software, monitor or + screen) and transmitted over a computer network (typically the + internet). + +

+

Computer-mediated communication is conducted using + communication technologies such as chats, messengers, or online forums; + social media platforms and applications such as X (the platform formerly known as + Twitter), Facebook, Instagram, or WhatsApp; + the communication functions of collaborative platforms and projects (e.g. an online + learning environment, or a Wikipedia talk page); + 3D environments (e.g. Second Life or gaming environments); + or similar technologies and services on the internet. +

+

CMC is, by default, multimodal. Whereas early CMC systems + (e.g. Internet Relay Chat, IRC for short, the Usenet + newsgroups, or even the Unix talk system) + were completely ASCII-based, the lion’s share of contemporary CMC technologies and + applications allow for the combination of different semiotic resources (e.g. written or spoken + language with graphic icons and images) and even for the combined use of different CMC + technologies on one platform (e.g. combined use of an audio connection, a chat system, and a + 3D interface in which users control a virtual avatar as in many multiplayer online computer + games or in virtual worlds such as Second Life).

+
+
+ Basic Units of CMC +

This section describes the encoding mechanisms for the basic units of CMC and for their + combined use to encode CMC data.

+

We refer to units which are produced by an interlocutor to contribute to an ongoing CMC + interaction or joint CMC activity as basic CMC units. Contributions + to an ongoing interaction are produced to perform a move as part of the further development of + the interactional sequence, for instance in chats or forum discussions. Contributions to joint + CMC activities may not all be directly interactional; some may be part of a collaborative + project of the involved individuals. For example, editing activities in a shared text editor + or whiteboard in parallel with an ongoing CMC interaction (chat, audio conversation, or + audiovideo conference) in the same CMC environment in which these editing activities are + discussed by the collaborators.

+

Basic units of CMC can be described according to three criteria: (i) the temporal properties + of how these contributions are produced by their creators, transmitted via CMC systems, and + made accessible for the recipients; (ii) whether the unit as a whole is realised in a verbal + or nonverbal mode; (iii) for verbal units: whether the unit is realised in the written or + spoken mode. A taxonomy of basic CMC units resulting from these criteria is given in Fig. + . +

+
+ + Taxonomy of basic CMC units according to +
+

The most important distinction in the taxonomy + concerns the temporal nature of units exchanged via CMC technologies. The left part of the + taxonomy describes units that are performed (by a producer) and perceived (by a recipient) as + a continuous stream of behaviour. Units of this type can be performed as

+ + + i.e. stretches of speech which are produced to perform a speaker turn in a + conversation, + + i.e. nonverbal behavior (gesture, gaze) produced to perform a speaker turn, either + performed by the real body of an interlocutor (e.g. in a video conference) or through the + virtual avatar of an interlocutor in a 3D environment, + + i.e. non-bodily forms of behaviour that are transmitted to the group of interacting or + coworking participants, for instance the editing of content in a shared text editor which + can be perceived by the other parties simultaneously (as may be the case in learning or + collaboration environments). + +

The right part of the taxonomy describes units in + which the production, transmission, and perception of contributions to CMC interactions are + organised in a strictly consecutive order: The content — verbal, nonverbal, or multimodal — of + the contribution has to be produced before it can be transmitted via the internet and made + available on the computer monitor or mobile screen of any other party as a preserved and + persistent unit. We term this type of unit a post. Posts occur in + two different variants: + as written or multimodal posts, which are produced with an + editor form that is designed for the composition of stretches of written text. Most + contemporary post-based CMC technologies provide features for the inclusion of graphic and + audiovisual content (emoji graphics, images, videos) into posts and even to produce posts + without verbal content (which then may consist only of emojis, an image, or a video file). + Written and multimodal posts are the standard formats for user contributions in primarily + text-based CMC genres and applications such as chat, SMS, WhatsApp, Instagram, Facebook, X + (Twitter), online forums, or Wikipedia talk pages. + as audio posts, which are produced using a recording + function. In contrast to CMC units of the type utterance which + are produced and transmitted simultaneously, audio posts first have to be recorded as a + whole and are then transmitted — as audio files — via the internet; the availability of + the recording is indicated in the screen protocol by a template-generated, visual post; + the recipients can play the recording (repeatedly) by activating the play button displayed + in the post on the screen. Examples of CMC applications that implement audio posts are + WhatsApp or RocketChat. +

+

Three of the four basic CMC units described above can be represented with models that are + described elsewhere in the TEI Guidelines:

+ + + CMC unit + Type of corpus data + + TEI P5 element + + + utterance + transcription of speech + ⇒ + + u + + + + bodily activity + textual description + ⇒ + + kinesic + + + + onscreen activity + textual description + ⇒ + + incident + + +
+

The u, kinesic, and incident elements are not specific to CMC, but + are nonetheless used to encode textual transcriptions of spoken turns, bodily activity, and + onscreen activity that occur in CMC data. The CMC unit post, which is specific to + CMC, is introduced in .

+
+
+ Encoding Unique to CMC +

This section describes elements, attributes, and models which are unique to CMC and the TEI + CMC module.

+
+ CMC Posts +

The element post is unique to computer-mediated communication (CMC). + + A post is defined as a written (or spoken) contribution to an ongoing CMC + interaction which has been composed (or recorded) by its author in its entirety as part of a + private activity, transmitted through the internet, and made available on the monitor or + screen of the other parties en bloc. Posts occur in a broad range of written CMC genres, + including (but not limited to) messages in chats and WhatsApp dialogues, tweets in X + (Twitter) timelines, comments on Facebook pages, posts in forum threads, and comments or + contributions to discussions on Wikipedia talk pages or in the comment sections of + weblogs.

+

Posts can be either written or spoken: + written or multimodal posts: In + the majority of CMC technologies posts are composed as stretches of text using a + keyboard or speech-to-text conversion software in an entry form on the screen. In + many cases the technology allows authors to include or embed graphics (emojis or + images), video files, and hyperlinks into their posts. + audio posts: A growing number of CMC technologies, e.g. + messenger software such as WhatsApp or RocketChat, allow for an alternative, spoken + production of posts by providing a recording function which allows users to record a + stretch of spoken language and transmit the resulting audio file to the other + parties. +

+

The element post may co-occur with u, kinesic, + incident, or other existing TEI elements within a div, or directly within + the body, and may contain headings, paragraphs, openers, closers, or + salutations.

+

The post element is a member of the TEI attribute classes att.ascribed, att.canonical, att.datable, att.global, att.timed, and att.typed, and as such may take a + variety of attributes. Common attributes used in conjunction with post include + who, synch, type, subtype, rend, + and xml:id.

+
+
+ Attributes specific to CMC post +

Three attributes pertain specifically to post: + + + + The type of the content of a post (i.e., whether the content is written, an + image, a video clip, etc.) is indicated by the child elements of the post. (E.g., a + post might have a child p, or a child figure with a + graphic, or a child figure with a media, or some combination + thereof.) How that content was created — in particular whether it was recorded speech or not + — may be described with the modality attribute. Because spoken language differs + significantly from written language the suggested values only separate written + modality — which covers all cases other than spoken natural language — from + spoken. The use of modality is recommended but not required. + + +

+ screenshot of the google search for hairdresser "Pasha's Haare'm" + with the average google rating (4,5 of 5 stars), the address, the phone number, and + the opening hours. +
+ + +

+

The replyTo attribute is used to capture information drawn from the original + metadata associated with a post that asserts to which previous post the current post is a + response, or to which previous post it refers. This metadata is included by many, but not + all, CMC environments, when the user executes a formal reply action (e.g., by clicking or + tapping a reply button). This attribute should not be used to encode interpreted or inferred + reply relations based on linguistic cues or discourse markers.

+

The replyTo attribute indicates the replied-to or referred-to posts by providing + one or more pointers to them. In the following example, reply references in the source + indicate that the first post is a reply to an initial post that is not part of the + example, the second is a reply to the first, and the third is a reply to the second. + + +

Es hat den Anschein, als wäre bei BER durchaus große Kompetenz am Bau, allerdings + nicht in Form von Handwerkern….

+

http://www.zeit.de/2015/29/imtech-flughafen-berlin-ber-verzoegerung/komplettansicht

+ + +

Nein Nein, an den Handwerkern kann es rein strukturel nicht gelegen haben. Niemand + lässt seine Handwerker auf der Baustelle derart allein. Zudem gibt es höchstoffizielle + “Abnahmen” von Bauabschnitten/phasen. Welcher Mangel auch bestanden hatte, er hätte + Zeitnah auffallen müssen.

+

Uuups, für Imtek hab ich mal in einer Nachunternehmerfirma gearbeitet. Imtek is + offenbar ein universeler Bauträger, der alles baut.

+ + +

Stahlkunstruktionen dacht ich mal, was die bauen — oder bauen lassen.

+

Das ist schon ein übles Ding. Die Ausschreibungenund Angebote sind unauffällig, aber + wenn Unregelmässigkeiten auftreten (im Bauverlauf) dann gibt es die saftigen + Rechnungen. Da steht dann der Bauherr da und fragt sich, wie er denn so schnell einen + fähigen Ersatz herbekommt. Und diese Frage erübrigt sich meist, weil der Markt der + Baufirmen das nicht hergibt — weil tendenziel 100 % Auslastung. (und noch schlimmer: + Absprachen) Was auch Folge des Marktdrucks gewesen war.

+ + +

+

In the CMC genre of Wiki talk, users insert their contribution to a discussion by modifying + the wiki page of the discussion — the talk page. Since there is no technical reply action + available in wiki software, users apply textual indentation in the wiki code to indicate a + reply to a previous message, and a threaded structure is formed by a series of such + indentations. The attribute indentLevel records the level of indentation, that is + the nesting depth of the current post in such a thread-like structure (as defined by its + author and in relation to the standard level of non-indentation which should be encoded with + an indentLevel of 0). It is used in wiki talk corpora but may also be + used for other threaded genres, e.g. when HTML is used as a source.

+

The following is a sample encoding of a portion of a discussion among four different users + on a Wikipedia talk page. + +

+ [[WP:AUTO]] + +

I would kindly request from Mr. Meyer to allow others to edit the [...]

+ + +

I dont agree, this article is not about Dr. Meyer, [...]

+ + +

Why don't you read the policy. [...]

+ + +

Because the policy makes no sense, [...]

+ +
+ +

+
+
+ Attributes for General CMC Encoding +

The attribute generatedBy is also unique to CMC encoding. But unlike + modality, replyTo, and indentLevel, it is available not + only on the post element, but on any of its descendants as well. + + +

+

The generatedBy attribute may indicate, for post or any of its + descendants, how the content transcribed in an element was generated in a CMC environment. + That is, whether the source text being transcribed was created by a human user, created by + the CMC system at the request of a human user (e.g., when the user activates a template that + generates the content, such as in a signature), outright generated by the CMC system (e.g. a + status message or a timestamp), or generated by an automated process external to the CMC + system itself. This attribute is optional; when it is not specified on a post + element its value is presumed to be unspecified; when it is unspecified on any + descendant of post its value is inherited from the immediately enclosing element. + (And, in turn, if generatedBy is not specified on that element it inherits the + value from its immediately enclosing element, and so on up the document hierarchy until a + post is reached; the post either has a generatedBy attribute + specified or its presumed value is unspecified).

+ + +

A list of suggested values for generatedBy follows: + + when then content of the respective element was naturally typed or spoken by + a human user (cf. the chat posts in Example haircut) + + when the content of the respective element was generated after a human user + activated a template for its insertion (cf. signed and time i.e. the + signature in wiki talk in the second example below. + + when the content of the respective element was generated by the system, i.e. the CMC + environment (cf. the system message in an IRC chat in the fourth example below. + + when the content of the respective element was generated by a bot i.e. a non-human + agent, mostly external to the CMC environment + + when it is unspecified or unknown how the content of the respective element was + generated (cf. the retweet that forms the second post in the third example + below). + +

+ +

The following is a sample encoding of a chat post that contains an emoji. + Although the post was written by a human, the emoji itself was marked in + the source as having been generated by a template: + + + Da kostet ein Haarschnitt 50 € +

+ face screaming in fear + U+1F631 +
+ + +

+

In the following example, the user signature of a wiki talk post was inserted by activating + a template, and is thus marked accordingly: + +

I'm not sure that this is a proper criterium, or even what this means. What if we set + an explosion that breaks a comet into two pieces? What if we build a moon? Cheers, +

Greenodd (talk) + + +

+

In the following example, a tweet is specified as having been written by a human; however + inside the tweet, the timestamp is marked as generated by the CMC system: + + Heute mit super Unterstützung, wir grunzen, + wenn die Zeit vorbei ist. #bcrn18 + #wikidach PS: Die beiden brauchen noch Namen. Hinweise dazu am Empfang abgeben! + @AndreLo79 +

+ +
+ + + + + + +
+ +
+ + +

+

Finally, in the following example of an IRC post, the status message that user Interseb + has entered the room was generated by the system, i.e. the chat environment. + +

Interseb betritt den Raum.

+ + +

+
+
+
+ CMC Macrostructure +

In many CMC genres, posts come in a CMC document according to + which they are displayed, e.g. in a sequence or in threads; + posts within the document may be grouped. For example, in chat communication + such as WhatsApp, posts are part of a chat of one user with another user or among a + + group of users. When an entire chat is saved, typically a logfile of the + chat is obtained from the CMC system and downloaded. Similarly, Wikipedia discussions come in + a talk page, which ultimately is a web page containing the user posts, + sub-structured in threads. Likewise, YouTube comments come in a webpage containing the YouTube + video along with comment posts and posts replying to those comments displayed below the video. + The video serves as a prompt for the whole discussion. In forum discussions, the + prompt may be a news item, and in Wikipedia, an article may be viewed as the prompt for the + discussion on the talk page associated with that article.

+
+ Macrostructure of CMC Collections and Documents +

When CMC documents are compiled into a collection, dataset, or corpus, we distinguish the + following levels in the macrostructure of CMC in TEI: + +

The level of a corpus or collection of CMC texts of a particular genre, generally + obtained from a particular CMC platform, sometimes even from several platforms. This + level may be represented by either a TEI element or a teiCorpus + element. The teiHeader of the corpus (i.e., the teiHeader that is a + child of the outermost TEI or teiCorpus) will contain metadata in + its sourceDesc about the CMC platform(s). Metadata about the project + responsible for collecting the data and building the corpus, if applicable, should be + recorded as well.

+ + +

A set of posts collected (or sampled) by a researcher for analysis. The posts of + the document will often map directly to the set of posts grouped on an existing web + page, thread, or document within a CMC environment. Within the CMC environment the + document as such is often created by a particular user, thereby initiating the + communication which other users may read, and to which some other users might + contribute. This level will naturally be represented by the TEI element. The + teiCorpus (or TEI) element that represents the corpus will contain + one or more TEI elements as usual.

+

In the teiHeader of a document level TEI, the sourceDesc + will contain metadata about the CMC document such as its title, its author or owner, + its URL, the date of its creation, the date of the last change made to it, and other + metadata that are available and to be recorded such as one or more categories + associated with the document.

+

The document sometimes contains, or is associated with, a prompt such as a video or a + news item, either provided by the initiating user herself or located elsewhere and + referenced at the beginning of the document. In such cases, the teiHeader of + the document should also contain metadata about this prompt.

+ + +

The level of the individual post is naturally represented by the post + element; its encoding is further described in section . A + TEI element will contain a number of post elements, which can be + grouped or ordered in div elements representing sequences or threads (section + ) if appropriate.

 + + + + + + + + + + + + + + +
+ + + + + +
+ + + + + + +

+
+
+ Sequences, Sections, Threads +

As shown in Example above, nested threads of posts may be + encoded sequentially, while the indentLevel attribute of post is used to + keep track of the original nesting depth. This is especially meant for CMC text obtained + from a wiki code or HTML source, where it is not always entirely clear whether the + indentation information actually reflects a reply action from a user.

+

In genres where technical reply information is available for each post, reply links can be + encoded using the replyTo attribute on post elements, as shown in the + second example of . The network of all reply links will then + also form a threaded structure, and visual indentations can be reconstructed from it and + need not be explicitly encoded.

+

Threads may also be explicitly encoded as nested div elements as in the following + skeleton. +

+ ... +
+ ... + ... +
+ +
+
+
+ +

+

Using this encoding strategy, the thread from the second example in could be encoded as follows. +

+ +

Es hat den Anschein, ...

+ +
+ +

Nein Nein, an den Handwerkern kann es ...

+ +
+ +

Stahlkunstruktionen dacht ich mal, ....

+ +
+
+
+ +

+
+
+ Multimodal CMC +

As explained in section , the elements post, u, + kinesic, and incident are available to to encode textual transcriptions + of written posts, spoken turns, bodily activities of avatars, and onscreen activity by users + that occur in CMC data; and, as discussed in section , + graphics or other media data within posts are encoded in a post with + modality set to written. When two or more of these features occur in + a CMC interaction, we can speak of multimodal CMC.

+

Some basic multimodality is available in many private chat systems such as WhatsApp, where spoken and + written posts and media posts containing images or video clips can alternate in the sequence + of posts. The following shows the suggested encoding of an extended part of the haircut chat example from above, including a spoken post, several + written posts, and a post containing a graphic image (adapted from the MoCoDa2 corpus )

+ + In Düsseldorf gibt's da so Abstufungen. Da gibt's einmal Oliver + Schmidt, Oliver Schmidt's Hair Design, also dann, ist eher also, keine Ahnung, zum + Beispiel ich war da bei dem etwas Günstigeren dann. Ich weiß nicht, ob's das in Essen auch + gibt diese Abstufungen + Ich schau mal :) + Ich gehe immer nach Katernberg zu Pasha’s + haarem Hahaha also die sind echt entspannt und gut und nicht teuer + +
+ screenshot of the google search for hairdresser "Pasha's Haare'm" + with the average google rating (4,5 of 5 stars), the address, the phone number, and + the opening hours. +
+ + Olivers hair und Oliver Schmidt gehören + zusammen + +

In the graphical user interface (GUI) of a more complex multimodal CMC environment such as + Second life, a gaming and learning platform, interactions may consist of interleaved + occurrences of posts (p), utterances (u) and non-verbal acts such as + bodily activities (kinesic) or other on-screen activities (incident). In + the following example a spoken utterance, an avatar's bodily activity, and a written post + occur on the same level within the body element, representing parts of a multimodal + chat in Second Life (adapted from the Archi21 corpus). + + + ok + hm for me this presentation was hm become too fast because it's + always the same in our architecture school euh we have not time and hm too quickly sorry [...] + + + eat(popcorn) + + + + +

it went too quickly?

+ + + + +

+

Note that the spoken utterance u represents a speaker turn that was transmitted + via an audio channel of the application that is continuously open during a session, whereas + a spoken post represents a spoken message that has been recorded in private and + been posted to the CMC server as a whole. See section .

+
+
+
+ Documenting CMC (and providing general metadata) +
+ Documenting the Source of a Corpus of CMC data +

The teiHeader of the corpus should contain metadata about the CMC platform(s), + e.g. its name, information about its owner (often a company) including their address or + location, the URL of the server where the CMC data were collected from, or the filename of a + database dump that was used as a source. Metadata about the project responsible for + collecting the data and building the corpus, if applicable, should be recorded as well.

+

The following example shows the sourceDesc of a Twitter corpus. + + + + Twitter Sample + + + Twitter International Company +

+ 1 Cumberland Place + Fenian Street + Dublin 2 + D02 AX07 + Ireland +
+ + + + +

+

The following example shows how a Wikipedia database dump may be encoded as the source. + + + + + German Wikipedia Data Dump of 2019-08-01 + + + Dump file in XML (compressed) + + + + + + Wikimedia Foundation, Inc. + + + + 01 Aug 19 + dewiki-2019-08-01-pages-meta-current + + + + +

+
+
+ Documenting the Source of a CMC Document +

A CMC document may be a chat logfile, a discussion page, or a thematical thread of posts + and is encoded within a TEI element. Among the metadata to be recorded in the + sourceDesc of its teiHeader are, if available, its title, author or + owner, its URL, the date of its creation and/or the date of its last change (i.e. the time + when the last post was added to it).

+

The following example is the sourceDesc of a TEI encoding of a YouTube page that + contained a video and user comments on the video (which are encoded in the body of + the text as posts). The metadata contain a URL reference to the video and the YouTube + channel that posted the video in relatedItem elements. The date when the page was + created is not known. The example is adapted from the NottDeuYTSch corpus (), where the video itself is not contained in the corpus. + + + Iron Man 3 in 3D (Official Trailer German) Parodie + + DieAussenseiter + posted video, created page + + YouTube + + + DieAussenseiter’s Channel + + + + + +

+

The following example is the sourceDesc of a Wikipedia talk page. Note that a + relatedItem element is used to record a reference to the Wikipedia article that + the transcribed discussion is about. + + + Diskussion:FKM-Richtlinie + OnkelSchuppig, et al. + Wikimedia Foundation, Inc. + + + 7632113 + + FKM-Richtlinie + + + + +

+
+
+ Documenting the Sampling of CMC data +

The documentation of how the data were collected, e.g. how it was scraped or sampled from + the web, or downloaded from a server, should be recorded in the samplingDecl. Like + other metadata, information about sampling should be recorded at the highest level + applicable. That is, if the information applies to an entire corpus, the + samplingDecl should appear in the teiHeader of the corpus level; if the + information is different for each document, it should appear in the teiHeader of + the document level texts.

+

The sampling information typically considered of interest consists of at least the + following four components: + interface: The API that was used for the download, possibly encoded as a name + type="API"; + client: The client or other tool that was used for the download, possibly encoded as + a name type="client"; + query: The query or command used for the download, possibly encoded with a ptr + type="query" when it is a URI, or a code when it is a command; + date: The date of the download. + For example, in the case of an X (Twitter) corpus a sampling declaration might look + like the following: + +

Sampled using the Twitter Filtered stream v2-API (see ) Filtered for the German language and the following countries: Germany, Austria, + Belgium, Switzerland, Denmark, and Luxembourg. Downloaded on Mon 12 Dec 22 using the command + requests.get("https://api.twitter.com/2/tweets/search/stream", + headers=headers, params=params, stream=True,) in the python script collectFilteredTwitterStream.py.

+ + +

+

The samplingDecl of a Usenet Newsgroup corpus: + +

Downloaded from the news.individual.de server on 2016-01-15 using nntp client in + Python

+ + +

+
+
+ Participants +

A listPerson may be used to maintain an inventory of users and bots taking part in + a CMC interaction, along with information about them. As with other such contextual + information, it may be kept in the teiHeader (where it would occur in a + particDesc within a profileDesc) or in a separate document completely. + In either case, an encoded post may then be linked to its author by use of the + who attribute.

+

In the following example, a list of participants is maintained in a teiHeader. + + + + + + + M + /wiki/User:M + + mike@mydomain.com + CH + + + + + P + /wiki/User:P + + pat@super.net + ES + + + + PKP + /wiki/User:Pi + + + + + +

+ + +

Those haven't happened. If they do, we can revisit the concern.

+ + P + 01:35, 8 April 2014 (UTC) + + +
+ +

+

In the following version of the body portion of the same example, the list of + interactants is stored in a separate file (in this case the file userList.xml in the same directory). + +

+ + +

Those haven't happened. If they do, we can revisit the concern.

+ + P + 01:35, 8 April 2014 (UTC) + + +
+ Alternatively, a prefixDef may be used to declare a prefix which can be + used in the value of who to generate a complete URI, thus making the values of + who shorter, less error-prone, and easier to maintain. For example, the prefix + uL: could be used to map the value uL:06 to + file:/userList.xml#cmc_user_06. See for more + information on establishing prefix definitions.

+

This indirection — using a listPerson, particularly one in a separate file, to + store information about the users involved in a CMC interaction — is particularly useful + when there is both a need to keep such information locally, and to remove it (e.g., to + anonymize the data) when the data are published or shared with other + researchers.

+
+
+ Timeline +

From most CMC environments, user posts come provided with a timestamp marking the time + (often down to the the second) when the post arrived and was registered at the CMC server. + In the display of chat interactions, for instance, the time is automatically added by the + system and usually precedes or follows the actual content of the post. In Wikipedia talk, a + timestamp is automatically added when the user inserts his or her signature. A timestamp in + the text body may be transcribed using a date or time element, in which + case the when attribute may be used to record a normalized version of the date, + time, or date and time if this information is available or reconstructible. + + + + das ist auf jedenfall krankheit + + + + +

Those haven't happened. If they do, we can revisit the concern.

+ + P + 01:35, 8 April 2014 (UTC) + + + + Alternatively the timestamp may be recorded using the + when attribute of post. In this case, if + the details of how the timestamp appeared in the original are + considered unimportant, the actual transcription may be omitted. + + +

Those haven't happened. If they do, we can revisit the concern.

+ + P + + + +

+

Instead of transcribing timestamps or recording the timestamp + directly on an attribute of post, all timestamps of a + set of posts can be collected in when elements in a + timeline element in the teiHeader, most + suitably in the interaction element (itself in the + textDesc in the profileDesc). In which case, + similar to the encoding of transcripts of spoken utterances (for + which see ), each individual post can be + linked to its timestamp via the synch attribute as in + the following alternative encoding of the Wikipedia talk example + above. + + + + + + M + /wiki/User:M + + + + P + /wiki/User:P + + + PKP + /wiki/User:Pi + + + + + + + + + + + + + + + + + + + + Note that the synch attribute is provided by the module described in + chapter .

+

Removing timestamps from the text body can help meet + requirements of text anonymisation. For instance, if the particDesc and the + timeline are stored in a separate file, the rest of the corpus can be distributed + without this separate file. Thus the recipient of the corpus may know in what order posts + were made (if the values of the synch are sequential), and will be able to + group posts made by the same user, but will not have exact timestamps or actual user names, + thus providing a significant degree of anonymisation. + + +

Those haven't happened. If they do, we can revisit the concern.

+ + [_DELETED-SIGNATURE_] + [_DELETED-TIMESTAMP_] + + + + As demonstrated above, the synch attribute can be + used on date or time (or indeed any other + element) rather than on the post itself.

+
+
+
+ Recommendations for Encoding CMC Microstructure +
+ Emojis and Emoticons +

Emojis are iconic or symbolic, invariant graphic units which the users of social media + applications such as WhatsApp, Instagram, and X (Twitter) can select from a menu or + emoji keyboard and embed into their written posts. Examples are + 😁, 😷, 🌈, 😱, and 🙈. An emoji is encoded by one or + more Unicode characters which are intended to be mapped directly to a pictorial symbol.

+

Emoticons predate emojis and are created as combinations of ASCII punctuation and other + characters using the keyboard. Examples are :-), ;-), + :-(, :-x, \O/, and Oo. They first + occurred on a Usenet newsgroup (Fahlman, 2021) and then + became frequent in chat communications during the mid-1980s. An emoticon typically consists + of several Unicode characters (from the ASCII subset) in a row, each of which has an + intended use other than as part of an emoticon.

+

Both emoticons and emojis may be simply transcribed as a sequence of characters. As with + any other characters, they may be entered as numeric character entities if this is more + convenient. (E.g., ❤; might be transcribed as + &#x2764; in any XML document, including a TEI document; see .)

+

When the text of a post is being tokenized, e.g. for linguistic analysis, it may be useful + to encode the emoticon or emoji as a separate token. In such cases elements such as + w or c may be used for tokenization, and the pos attribute + may be used to indicate that the encoded string is an emoji or an emoticon. (See .)

+

For example, the source post da bin ich nicht so empfindlich ;) (English:. I am not + so touchy with that ;)) ends with an emoticon, and might be encoded as follows: + + da + bin + ich + nicht + so + empfindlich + ;) + +

+

Similarly, the source post Klar 😁 (Sure 😁 in English) might + be encoded as follows: + + Klar + 😁 + +

+

The values of pos in the above examples are from the STTS_IBK Tagset for German + (see ), which includes tags for CMC-specific elements + such as EMOASC for an ASCII-based emoticon and EMOIMG for an + icon-based emoji.

+

Alternatively, e.g. when w is not regularly used to encode tokens in the TEI + document, c may be used to mark an emoji. For example, the source post Da kostet + ein Haarschnitt 50 € 😱 (from the corpus , in + English A haircut there costs 50 € 😱) might be encoded as follows: + Da kostet ein Haarschnitt 50 € 😱 + +

+

Sometimes, e.g. when the source of the TEI document was a web page in HTML, the emojis may + occur only as an icon graphic in the source. In such a case, they may be encoded using + figure. The corresponding Unicode character can then be recorded in the + desc element by the encoder if desired.

+

For example, the source text: ... ich überlege noch 🙈 (English: ... I'm + still thinking 🙈) might be encoded as follows: + ... ich überlege noch

+ + see no evil monkey + U+1F648 +
+ +

+
+
+ Posts with Graphics +

A post in a CMC interaction may contain a graphic in addition to some text or even contain + only a graphic (without any text). As explained in , the + modality of such a post should be considered as written. To encode the graphic + information, the TEI element figure may be used in the appropriate place. + +

+ screenshot of the google search for hairdresser "Pasha's Haare'm" with the + average google rating (4,5 of 5 stars), the address, the phone number, and the + opening hours. +
+ + The preceding example represents an encoding of a private chat post that contained + only a screenshot of a google search result for a hairdresser. A link to the graphic file + itself is not included because this is a text-only corpus that did not include images.

+

+ + + Bro Tri-Engel...so hab ich mir das + vorgestellt!!! @AndreLo79 #bcrn18 #wikidach @Heiko komm' mal Twitter! #Engel

+ +
+ + The preceding example represents an encoding of a tweet that contains some text + (including hashtags and mentions) and a graphic. The graphic element retains the + URL of the graphic on the web just as in the source.

+
+
+ Circulation +

The following recommendations on how to encode features of the circulation of posts, such + as IDs, re-posts (retweets), hashtags, and mentions use twitter posts (tweets) as an + example; this phenomenon is not in any way unique to X (Twitter), however.

+

+ + + Ich mich auch? #dynamicduo + #wirkümmernunsauchumIhrenEmpfang + #bcrn18 + #wikidach + + + Immer wieder gerne. Kann ich mich schon für + nächstes Jahr als Empfangs- #Engel für das nächste + BarCamp bewerben 🤪 + #bcrn18 + + + + + + + + + In the preceding example, we first encode the type of post (in this case, a tweet) + in the type attribute, and if it is a specific subtype of tweet, that will be + encoded in a subtype attribute of the post element accordingly.

+

Second, the original tweet-ID as supplied by X (Twitter) is contained in the value of the + global attribute xml:id.

+

Third, a retweet and its corresponding retweeted tweet are encoded as two separate posts + each with its own set of attributes. The post representing the retweet itself does not + contain or duplicate the content of the retweeted tweet. Instead it refers to the ID of the + retweeted tweet via a ptr in the post content. All original + content of the retweet goes in the content of the post element as well.

+

Fourth, hashtags occur in the body of tweets and are links like any other hyperlink and + should be encoded using the element ref. The type attribute of the ref + should contain the value hashtag, the target attribute should contain + the URL of the hashtag, and the content of refshould be the string of the hashtag + itself.

+

Note that in the above example CoMeRe style (cf. ) encoding is used to represent the number of favorites. It would + also be reasonable to use a TEI measure element instead of the fs.

+
+
+ Linguistic Annotation +

For encoding linguistic analyses of CMC text, we may use the dedicated elements and + attributes from the analysis module, which is described in . For example, + the tokenisation (segmentation into word-like units) of a CMC text should be encoded using + the w element.

+

Let us take, for example a posting that contains the content 00:22 Bin + soooooo im stress gewesen ich Armer lol (in English: I was soooooo stressed out + poor me lol). This may be encoded as follows. + + + + Bin + soooooo + im + stress + gewesen + ich + Armer + lol + + +

+

In many CMC genres, especially in private chat, sloppy and creative writing abound + including irregular spellings imitating spoken language, omitted word boundaries, and + spurious boundaries leading to tokens separated in parts. For encoding these writing + phenomena typical of CMC, the TEI attributes norm and join may be + used.

+

For example, the normalized spelling of an irregularly spelled word may be recorded using + the norm attribute (from att.linguistic): + + + + + Bin + soooooo + im + stress + gewesen + ich + Armer + lol + + +

+

When the boundaries between w elements are generally thought of as denoting word + boundaries, we can keep track of boundaries not present in the source by using the + join attribute, also from att.linguistic. For + example, for an original post that has nothing more than the token Inmyoffice, the + following encoding demonstrates an interpretation that the single token represents the three + words In my office: + + + In + my + office + + +

+

Alternatively, and especially when the normalization information pertains to more than one + token, we can apply the notation using the elements reg and orig, related + by a choice element as described in . + + + + hastes + + + hast + du + es + + + + +

+

Other analysis attributes like lemma and pos (for part of speech) may + be used as with traditional text. It is a matter of the tagset used to cater for POS + categories that are appropriate for CMC. In the example below, for instance, the tag + AKW stands for Aktionswort (action word, see ). + + + + + Bin + soooooo + im + stress + gewesen + ich + Armer + lol + + +

+
+
+ Named Entities and Anonymisation +

Named entities (NEs) may be marked up using name or the elements encoding different + subcategories of names as described in such as surname or + geogName, or rs for a general referencing string. In the following chat + example (adapted from ), nicknames are linked to a person + entry as shown in section via the ref attribute. + + + + Konstanze + + versucht + + nasenloch + + den + wunsch + zu + erfüllen + + + +

+

In the the following version of the same chat snippet, the text strings with the nicknames + have been replaced by category label strings for the purpose of anonymisation. + + + + + [_FEMALE-PARTICIPANT-A04_] + + versucht + + + + [_PARTICIPANT-A04_] + + den + wunsch + zu + erfüllen + + + +

+

In the preceding example, pairs of a gap and a supplied element encode + the fact that some substring has been removed and replaced with another string for + anonymisation purposes. Note that in this example, the name and the w + elements and their attributes also provide some categorical information about what has been + removed. Using gap and supplied to record the anonymisation is especially + recommendable when the original name or referencing string has been + pseudonymised, i.e. replaced by a different referencing string of the + same ontological category (such as replacing the female name + Konstanze by the female name Kornelia.). In + that case, the markup would be the only place where it can be seen that a pseudonymisation + has been carried out, as in the following version of the example.

+

+ + + + + + Kornelia + + + versucht + + + +

+
+
+
+ The TEI CMC Module +

The module described in this chapter makes available the following components: + Computer-mediated communication + TEI-CMC + The selection and combination of modules to form a TEI schema is described in + .

+ + + + + +
+
diff --git a/P5/Source/Guidelines/en/Images/cmcunits-taxonomy.png b/P5/Source/Guidelines/en/Images/cmcunits-taxonomy.png new file mode 100644 index 0000000000000000000000000000000000000000..08d72e7ad8a38e43892cdf2a257a8585f8da6965 GIT binary patch literal 24066 zcmd@4Wl&{JumA|sxVtqjja?iXcWK<+-5PgycWK<+;o=u}cN%vZcXwaD_jV^@cjwpq zo0t>lRAgmkWo2e%W!Z^PkP}CO$Abq014ELO5LE&LgIodw`*sHl@s;YaAas8fz&K0F z{(?Dx`vy%6aoq0Q`GtbBm(X+q14DNH@B3!;qhaw23281QD+C5s7l-g>2n7ZP0j40M z^6T^S)6voKs}unN;pF7x_4QR&R+fc@<^KM@rKN?Hl~q7MV19mHK|vuXDCqI=QBY9O z&(9AU8hUhel!%CEXJ@Chv~+WG6AcY*Vq!vETwGUIx3jaeprC-7nmRi>o1UJ&rly9Q zn|p9@(8I%{zrSBaMa9U-XlrXrQ&TfEG*m`L#>>m=&!0a_OG~M#sWUS(Ha0fl;o(V1 zNevARIXO8|QBmgR=F!p7)6>%$8X5)$2A7wY-QC?`VPO&y5~!%COiWA`78YY;W4XDx zoSdA^&CTxa?!&{wxVX57hleC2B=+|9adC05u&@UQ2NV<(goK3G*Vp^|`*U-1qN1W& zT3R3wXl-rH$;qj$t*y7WcVuM5(9p1?q@<&xAP@rsqq@3!dwbi=%*?T7 z9n8K5!L@Jy>Pa?pjwO2H{`pNIYc6}_;Pvg}6|rsf;x1xVC<-K6AkeZ=_S=GExGYc!96n%Pso=B>wW*5+lKkGoRPz*&K-foY4h@x=&l``>eWBJd!i{bL9PFmj_zeL zW>W|DCw8v4&L0o1o;33pv2xITm17msbr=e_Hf zUk>p9%tu8DF#4rA&{;`N`D-lv-{%2)Gb=s>1JfLr6cti&Up?;}kK7x%`FGCw19Mef z!t(FFFBFJCj4=s7AQUS4LJRq?Uz zruYpdYdT2B`qm&tWLn^ECG4tE5qTA~a3R$+h{bBZPP56aYx$N&Qx3IAuiHxdOlk^t zp^n6*YQzUPJ?AF>;BIzi8g~}O?17tUKk^jJs2SG3-)xi z8sVt~u`6J5dspnF-6KtOpCiWl>HBDB?a+{~67CjI=kWQ@Qp=M-MB-+r^&{8E@6DM|KZVy{N=jRh zcK9>sn(^=k=?_RBYxK$ZevJGmgj_EVwLfj!%NUK(jXL6Tbrz|vHr#o=!s(@!OBRzbx z1bH5tsJdqFhT1SDn~%=6zlnXMAMPIF%;M}NOAH9NGGpHYJO%^1k9`Ktqg&Z2ZOzB* zF`J>Y9HwF-*3yMbm>qcff3I&ECi)gB57Wi1UHr1mnN2FT?th5p^NS`-U@Z=dTxZcd zAC6u2$T(h`3t@a~OucN7MG=U)J)V;W>`%|$t)=6OzR>bLO6vVfBox@Aw)J}63hJ;P zufWlpx1|h=lH8zv1rmDnM%aQ|KccD;3KA z865RY=D`$9ZWuE+LKyge$UQx9B)E;>@_1Dh=Pv$jCp#e;c#=6?3?-bFA6H>$E{A+@ zxIL%I5(&lC%;F$&2KV?au-Gn_Z6BRI*>T{2VZK%pp|x08e7-hO@9>=^pHnGwRjPRx zJzC$b-y&|MAC>1g5GS6!7AQ544xhJeDM>4%+oE z-z90v*?NQpoQ_wZsk6Bze}Zbr*~KW&C4pVkjS^NT2P8PObQ6m?UwDyj9$oD%e8gt6I@?8=I!J>N*&BQeXW zZGBx$!$i>X(JNEOrUq=Y53NXGm9plbRY#J%bg32#r^hQ5a@*K4F2T&?k)@LD4)Yxl zvsimOQnwy{udR1ISGF7HbHX~q&Opt|=}f-arQHBL{WUB-zV*b?PAdCGBiCb(jz^X0 zH*dt;@Yb}xA3LHqI8{K%y3ImbgC&PKf^eOLXcb~JLpVT*@SH}Wz1&VZ1mk&y2~Gba zULJCyuGVzjDcFCm&nC%7fvhtk-#o46oc|bU-D`{XS4m)teFxfm)MUyiAYnGJyg;3R zF6jiL0>z7^1SEsSaCetbGSNSGH68kssF#K(5QDx%MS!CB)s%o2R?Ak!|AdKuYLZ(n zo0q5DkDX#RGfmVw-bQ8?aW>E4qb>f#bj?AZuh=>^ps11|r7tOeJ9UBoX z>q8!%@!(=tUoTOeTVjM!1CPdQLTFe9C5V5>EzaOf24juSplx|(*#%&xyT3@Z(HVg> zBq2-@ed+9Ils`K%?1Ds&-$vi_^F{5`2!nr5!^*dkkWF_Dy1**d2DsdjPuR+^5}R){ z*LrOrMn4DAE?s3&uwH=tDJUzc8e_*YSQ2rrGcJ_-hv!lSv}jp4;L0_6$J*G?U69Fa zROwS3%lg5lxN=}=6S|CNX4&i+Y;$3?xH5!THyNupKuJKE2f@;^$u!jQJiFh9!P>7n z$he7Kn{3=p7x0Udi!Nl7Adbp39$}(ov{Ue!)U%f`i@LmQv~GR(Eld;79woKU^kIP}#To~Af6X1{VKt(b zJw7SI7gaqs^HNgY`1#DG^{ASywkA`QaBKDll-`SJr0ox4tEef+y89nbkGM+{Yqgv< zV)cm42>n^%b*gENkj7tHy{tq!i;~hc_G!RXl|(peCquMS0`q`zIA$E`YBk{M7QPqp9eoLiCZg2xYOtENot!>-w857R*1X|tmJ z-Y6!$1WLI@XY2H?GvXnjY8NN`xuq!EXdMwJbCE_hpWZ7Igr!?+IRFBythArUr zm8Y6zQ7O~*^ODwWKt`PZe>v5B5QIKo;#fEGHFDj7H`uCF|2fJxgQxSZ1C&-7Ftw zTql}F&4}v7RKn`pOPzs5_gN{wB=ALo0gx?^itCfZLrK*6VuZ=Ap}8BArnPR={-XV$ zr^w*q(p&q3pcOwJHE6M<3fj(pw$sq))JpEm_{B902|bh5dh4xdn$ak9IW$A+Ep2ms z`*?7%nWoZ9hw8RVY+mpl^c#tev<1AY(*y zau-izV4Yi3tq_gbmt<>RaAI^J zB2nv^fazUk1bZaJJC1@`!!u%&Q&nbgXEytMWDiVM1C6%+p%C7-aC(&-s9-z8M|v!S zG!H?#nUFc{96tZ$EVVEgkw)%y^f7c>BS77xH)Y`OfzV&!T=HT}AqNWcaAlR}{#@vnC3)Bjc^p0Z^1}H5v$`061*QkxG zRMt2vk1fSewRbZ@zZWm$4=&1KHjEO6VrhF_8c}|X_!~LdHQY8_`NLpn!!)G}rCZ_F zMa24yMo+7Tp=vWCK&PLN-ZO$W@dQhc2Nn=3Hag+Z*JSS)*e8U%oVA%JQ8Yq)wWr5E z2Cy5j805h}+rndDER!*^+yc1ZrVRe_5OA|W@#g4Q%T#~wO+O9EZk*JThWW80^rJsW z%wP&;M0ElE=S}z8+c?qSkmgSLZ^}Shqac1qw7nvbB@qZ3cQ?PQHlyVL`hrdRDDC1> z)tZo5(>jQwXfx+&5(|I%MCf#@Z9Xys0P1CvJD4U(3DC4(1DLrn{VlWV?+=-M{IXNyd8BmC@a1w-N05nC(8F8TSN>sNEQ z&%p|bp; z8l4h6O)6WHzZ;h~94YkgaN5G?>AIQGt&fV)w`b?hieKNH3=~KzJJ+e#*k_!zCV!t@ z;!%K}1;0jb`C#Y+D&>Csr@Qk?_CA9SRhmMfyY}9i+5&tIho(nBGoHQuF;`*~QauAr zO)}Of@4ll0A&-Rp2HkpN6&QE}-4ivLQvb|3!aJRbSiHeM+6nLA^U6{kfR!vAyR8@M zg2beWk-iEU{z6P8*C!rrX7M0&;SL7h=3B=y!Lc(WXnbj65QuTZg5t{HlULqU4ah3N zLhXDkF1J)o$kzjm|0k$H_%a^1%#iaDo2Yf?-JdRr&rWzGH0^%$gP6;$?mu{BpwZ1w zF+{Yr+ViU@*`mbG&lp@XkfFJUUKNPVnyKwCh+fTl&wm|~i$ug|qER9=+-8|{{2fL9 ziysoHO{MTE`(D(>(}(hY(J{lCWb^MfX|Fi3{wXVtuFsxTkfgrm%k};4DUX+wpY-=m zUr7PIxuo;rq7U*!Tg|xRIB^Sws!!vgkbl0%>hJ_0EpK_cb4S*8JyrAkjb=|XJ5IKDOk{Bt-ukV|lS&Q=A zjuBcQWta0nHbsuEv!LfW8G6=?qaW=sbx3`VgAZh%KA+`Ew?xfbH9u@zLZs5x&hi+P za+rC(rgig|kNwI<^ZG1m*LKX??MJ`Q6p!z35`*7j_rQZ?zJG>ApD}NIY?{M#jjip6 z8p3YjFtU%h})la^u+~Vtm5L z4|Rg}BhJHpDl0SFvZ8R-nBJlw#iOBU@R{+7tOqRO>(L5@#>Aqb{}%y~pmU*!?=Twa zK*WSEJ_KI+4Uy^l(?EPZ666s)PW1D71DA6`B;8YtNa+HW_u%)({cdY+I*(P&@qVVB zj3CgBW)=B7ff6VHR$-;bKcB%NKM83*EKF&8kC9_rZ=#rch;tMv)?B}zU76i=L2wF1 ziQVX@#7g*I5>s-qpd=gcvw_jW5nV1;4a^2Ai50N{ltO6{H>1*KRkF#DBpdg!&?;z- zyXf?iLO+R>(A`MV%3cteF(ugvni6R9x8aB->Spz-C1sIyXB~W@p%_%ukDq2O4qu$w zjHo)OMAXF5<@g6ZIV4tWO_{!O|0YxqC04Xpa!4ylEqG(vnB(i&OiVS!xKH_W<%^kU z)?A{QP1q(1NCT73c}wu>+bqH&dXxK#tg(tnGXp}(29fwMXhS4d;**=IPLx9k(-%-3 zw#F#Ub`o5?$45|8|M4fwdYX)vCEA5>xQGmN(yX1Gl)RX8$Fy^pl2e*&jzJfuN+F0w zo}mB2QJdr?R&o3&aWc#z>UWo!3W3Tvlk%n&2=;onYzJflaVxC@E0eXzFIEYl4MJyA zE*P@Xe6{rRph~jAW~@y^9S#*sOF_~&??c^ z@GxmDrx26(esdx6PLcR1UF^XsZYK-ZCV9WGQ}0X5`jn`B)}hptijr|v+$DX zjzY4dC1)g$Ay+!blKv-`AAHug02~(7!!?3LIO#JCd-lO(j#g#QEp(KGTjew$0A2AY zMPQs^sE?}nT5N?_(S@Q9^TnDg;w=2N?x-pLV1$B?V!!ntr1dsQ5)if9o94B4Q6B&& zC67P0#g6-%Q0M=cl+duStdfjpk7Vjqy#s$eo?QJVY!6W+mjA;9hU6Da%@BtwX~i^& z>6~m=#t=o9>FKZkVT~4352* z5sVUHczp%CJX<0y+U?xN*;%jM)ynsI&67ij~)0k;vW|fCnYx4mwWgI19-Nv;=!J;7bgcGXGtRHTdoJ3N(7spD}AxX@&4)25I@WyHqakGx6r z+fs4pIsPX-yh^+gwdj(Pf@J^}Ra!@9my!A3Lv`@D?15ncnUXjSqzIP#QeoTme`apA z$qCPr#-J%A5fbC8cjJm(y_Lr+hM2lnm6j^c;!iWheZQ=r-42-BpIp|+*S(Y|d{LSb zUI{m~S06hNIn6g#@$37YHuAI;RX=FRB@l7ZQHn;hrm#G<0)N%C#Gbb=IK~cEVAcn| z#ysjrgrWq>xz1qM<2G}iA;wSweOzfhK3G+ykNYQ8<199F>{KIKKN7$yfq+kjk4ytT zD$()vE+iKVf171+6_}`tteXvaf)Hg9u=zYVXtb>cdMK$cNcGvjIH|cC-&1NAVTg|{ zCYjt3*g9a57g-}|$Tx!>768N~R)7sGd8U%Ms9|~}rtRTYNn1bfRRnzm$6Qkk0qkw) z6YCM=rsOHe|Ap8gT5ZGYNjl^du_PIF6SI!1Z z|7HwwKBcU2z9;h~*B}2q@Z_wC3@SwbMkFbm;*PrDL5&}lewY=1?Gi0~f2q3?-uo|6 z4fD_cF#~9O86Cl)PPXm?BEBOG`+ZXar6gg8+?a9Ejnl(xU5|*EORlWi&t|eP)w7+C zA!MaBFfW~vnOcpV2)j+*>xj`+F-~%k4xJ>(j4i^RRs=P$_@1DymA8`Ml8?sMFU(SJ zw?jWd)ZsnM;B_<;eFayw$>b4s2hDZWcK*9cp{;kX8&3!PPQ7b4+fniL zsz$15Kj;O*Bk$E5ZJs;=5%WhJjH#Q#QiiHJ+aCEY@>z zy#R*zMb+cM3RqDDY$N4gGU=9xW)TYK$W521C^MiWAwOV2c)vm@M zaQE4|61X>T;C7M6Q}%)urtb=N#!y|#J9`J)9AelyJMd66*zPi!BvuG);DhU}Et$lE zX=N(oFimJ}9-n6FO%d!JBvsfKUq}J4*#MUDP-b<-A=&P+P&iin1dL~1Z55qzkyOVf ztrs-)yG6s*74$y{itLHFPCtvw@4AQZ{&U?D+BFR*W$pbO|F^X^s1Ho(y`X0Y{{wrC z!=;nOrq5~?zRRDepGpB@!LDodvBzWV)QSTH#}v@)IBCD&FQA@P^T82*_;pK-ZKU504CT4hCLI-c;sLt3(#se%r0t*@z>)pR_S{qWgx zJ;s4#wf2Y$7(pZ=<#5+`IH9M>`3YaOOK1*tnevxicZCu^d(_Kz&h5TIp+VXPok5j@J}Qa_mzYWh-JkzTu7m3S9#Unse{G=J@@qs#8r9{7RP z>HTkA|K(WD+=SB{1U~az@8sy#2y_wPyE|`3(V6w0Yiqb!t~^ zEyXi;cdlldStvtgh+N?_T3`HWdc0-@ua!cxMrr!G5tjrv!}gQz&lkCK`IF#O;3;nTaFK?K4lYQoKT!B&Zx6s1}v?q1v;JmEVNVoM1zrO26k&NRK z>-5Xq_xC@-ZL{6=fyc< z5yueN3nB1I(mP958C{Pr$S0%VMAZlmsL#GhF+yJ}2Nl+5!X)0!Ik;q`t|0^n8gswD z;g$MQ1FQ8LX1;E}{XF`j6-?B^e6-`}d8$qa$%AT~BpAmk!vmDR5OcE3k zvM<~t(h|wg_|E=EV_M*K4Mi+AOz)YTeJ9!u3NHmd@XCf#Riy7xadOcJ2tyL&zpp-KsZK9wGt zsedw#dTbbl}^{NEO)lNW;QDP&j_?5-gCqzX7U&iy^IAP3fT4-ZnT2 zr6HIH$h(uT~z54C%^OP`QD;?<%>mPrC6YZwH>)@EXWPXP}F-3Ryc>ho`zgD;H9-akmJ%5G10(lBibQE)#%jE;ilOyBL8gGxY@l zd8?%5U1Kc#=YgUX=*ni&t8~bj?oa?+5q>~**8Go|CIvl{e9IwKUE{qbG$e&CH8uEn zu8J2ZcBBc_0vDv{EZ1@C^K~IP_%^W*y#K=xe~BGTs=dwmTz-a!?1m{Wl9BL6;lYF( zYTWL%c)IT2HG*RbS)A=T=A;K#vJ0UN{OaMWZ2$4&R?N9*FJ}Rb(_}LopKCW~;hz>! zQ!~bS%R$Zps=eRIGKN!rfR|bj;V;)_)bRZV%Zo1(r;1Yw2GWfN-)gjld-T%fQ3W-N zeMseQ0z*WHpU$dPI77u zDx+!6Y4@OZrZ&XGsKQGP<_m>zoHN<_04QnO^r)@JR;(&CL!z0M$*Q`=Wx7O z{`$wK3XN2ev4uqRKZhHDoL807&}nP`CGDibMbqch9FCxxsrmiY_^G%|v;E>^F3{Pq)xrq>`D zJ`eyNGY`L>2?I%4Xlu_;S%)mL+q*&{q$+{^z?iEIb>V#1E~!?}PgEtv9WZPTorWI< zy;7VLDeObB`=9yP7}U@VR0N`Q`fv$cpm}f@U#%DFlMG--vgA+jQ7F{1H!E%7sDys< zB|5M0L51rZRB5-~I#KFtoNHWSqQe9c#Zf;knOaVhhfwB$IVJ4X)MLuT*jVqXV1ge~ zkq)Gc--8XFzGGMaM#SNUoI@+8KrxIEu|1xKHFsf9A|jK5bJgsKES4*) zOgeL}P59`>EW@N?=q@9I+X5#hbJT6Pt!?cR(mU)`%G-CBAt7^T7ejU-4eSD-3WcYu z2rq{`1-vg@7U+*0R%{H+8j7Bf0fB0E@P`ojCiTv`#_vrD?s=&&|J-M4lcR;W}Ap@g!d} zmO0H`T>x<`vC#+|y_3=rhAy&+>&D#lq5jp6dfstCT5?JL$k6J?@@Bm-p@i8hh>6Dx zhhd0JTq9b>h|dm;2rOi1QAS%OUf)}sR;?Vc{8cwkF5NaH^7a!gRHF?ccKcEU`B7Ozv>VK{5c3l$vY z#8(&y2(q5)r>^|AOSY3!fz-!+@o!?mv%eniM`}53LrjI=tQ%&Su9?F{KT4%@WwBL} zGtvTN*&&bG$CO-oCuAkUIP(N>$^;UrSjpsMxN6gjz@P(TNwrEt@xoJTX{N(LH}~?0 z_MatH_o`wl(*Yb2Ybd^?bvgH1l^&nMWaf(D_CS@z>4a||rBzfKkj($khV+-L-)6}- z`m|(RGj;K0&9Tu{q5E>K&PPuF{II(UJYvE#H?X!6ypk3m#ZH?fDQA}!g{>*7Ap||E z)!JClj7J#-7Bf#3P}PU8>Ws>E%%*DY-_hYNPpTGEgIcjAqDNQmIJH&J&aLOAgM@H8 z^GT@DSvOd>@7}V+~zhg88^QWR}o7Jk&1vkRudq94iv>r2pNk zTeNW&2_SISUH`BG(Cgb&`f5}-rJ$(qiV^8t(~(kfXEu$6UDxXz6l>FCoh7*FWML3zvDfxZf1MN7d;7BDvkaSsXIbueF~L&o;4~j|Ge~u%Um& zLGt>pelFv1np*EF07zsP?Lw`H`<0xjfpvBU|{R0B|BjzpCI6w8aqIF~wn zq2>{STOyatW30WKozziXmgTnQh~V*jM6*b7DW|`97DVFOm%D!PgntWIODV&F&BrZd ziLMX~|ES}(|^ zGcuz};37I#Bls&i(6pzDG2)v82{a{p@o0F3Aof(*SD^x9{Jv3G3D-V5mK07zx(D_> z7a43I$=4hHm!>+}(9Be%PGgYnFt4smCfm3Ji1lms`;k^3y#~L_py9`#c&{6u5q`FQ622PNvD+`8hBAP2XLUUHl z{#HA?)y-NtR3TSYU*%%?B(`!k8B4N@UNtUKT5)Q3)16UmEKXR%3|r|8o0;}{o0qN= z=eWAqV6yq`pb8b3i!A-Qz(%ZH5*k#gY z8FwG=rFeD131hNMVM8GCR4a3In#+M40^HoOR{L2)4{M=Tqjt!OE;f3}EL(HX zsj0A)>meYG$9au%w#oKSPDiEUe2`6NcS^9N^Wm0Pvn{=eP~8 z+H*eM0J{_Z#mHOtbX+lgsBwi);33B|BCgtsFNN$KZgm$%;p$bB(?mx%>h-*U8}u80 z2zEo3@!Er`!htofH^)`{nfia$rn0bCpLLu$Z?RF-n2Bx~RtW4*x$dg(okPNFsC&c2 zPB;C^y2f7x?ID6$Lv6#Gc+#|yW77=tvzS>?*5{E%+ACwc~2?j%{#_)zRVPK0+M4lDS z9LoNoQOT>upX!_zVZ-lM0xOxmdsNU->q{WL#j;HXu5{Rl;TfR<3Jm(y0ARVN)Z{15 zb{bt8T%O;c^A}Zj)c9F_Q@!QCd+AUFmt$obEJQdS-HQ2!YXCCpt(HqwPPDpiAVd;z zhUL2XlA3-wMbe+(?W##fK&R^}Qy_d#X|zhIw?Z{t-z$CXbx0db2IhB{1TLs0#|IZsA*S{|{&q(T`n90DEZtWB4amV&k@YtvigSux=q=ANE&Y(XWO@uc z+0SdrmDz1QK~}Z?D^kaJ?gR-j(+jIJ6;*XP9mpEZ5VIs#pO@8!&wCIh|cD%R{d0x9QA7a|ce9c$az z#9>;Jv;tSj<9z%w1}2&};Y^PtSPK zhKmwdhTSOYr&@dW&5dm;zqvVIEThz(DCzz@*S;YpgmvoI5|2mz;$%Llcec?$ zCo*;*fux6^4P(Iau8wbQhW!)P1z`#?;wwDEcJ;is1%@a3D$NnF$oAd4sI3mG&CJ-# zq0dy!{2I%y(2D&|X2$`H{v}?-@wi9mtxkqqT8aC5WLtYPnmjvFE!t&Ba<9P{e1zT47qiE4wOL15v?AgL7Jp|~oLX*WO8!o@ z_1zq-glTsn|M+w|+Cf00=8NdeZ#i=0JO0~2^y%G%Mo~ZI*mr~>6;G_=7Fi;d!@ud@ zdH7gkU*Oynk&C(GLKU)yC(`P)>x(jWBl5UWjOfay3Q51nzE|8@z%F=9Af6mLOi#EY z_ftGuxfw1EWjke@@G=Ox5OuN|Cn#l$o15{1OovuJ;gZ50VXselzby8I3>>(D*jcfgYt_|-mw28hOdNH%2hyZX|9f~^Sb=d&6Qk!3qT8^GV) z$NXbB;T?K6=!|q;FH`<%V~AdF@=KExQ5g&w!0buDBc_4nYey!xFH)LA_HYYDg0F|P z!2Sc5&mXBfdY=G4l;1Bs%hS%ZO%|!XlT#o5v>eBFGfky;mv>OUokj7)eEtvHL_F&y zR;;d`U#G4Z(ABq33H6;nC3z?pXx=%LKfAid3bj){nk4o8#&ta&7*jrymPW=oj*Z9o zXP4qsHs5M#j`3ETG>^3YQ~5R5Av;V7sT{CXG$bia@!1(T)j^l@pTyN9+hyCw9N+is!`eJ6rOVAG-NcuW?h22xmO5*u zUG6xC#L=u%-kIIhmxo?QU5wYe*I{JL}}P&smnl(YW4;Z+c(+rz;lk8<7QH$>b}opUq0`pbL*QCoCRnY ztf(1@rK`X4$I?XM9iRA#-J&ngk9vS=L?yQM(Y~jThD*OYOh80S~9xJ@Bxc*vWGg&6z<-vE7W3@8kL~& z!~0>mrfospL)t}-)+8_Q{zIA7UqDOgBaJmv-3 z2J?b{PLC%EPALyy_E=%~BGu9D~OKMX_!1?C&Kt1eS#A zk_!E9vkdx8!sp!!`qkcK*9;rsa~C@0U6+EZtc5u>R^lpKeAP?l@v4YwA4y^+*%KXW z@Y3CJZhplHGGgW&JlkIz`)MAR9WI-fqoqH<13J z{+tbb4Dd5S|Md#irFGWqyzb=m`1{@I_Ukq|U-(bHBAAELj*IJ8WI&4koU<4D1A}aL z@k|xeqo3^D7C*6ZMdnoKdH9t*0+?OzSQ(QSwF{iYdJt( z>q4Mc7-PnpzOD9+pn10E;8c#3%EQClo6YWSmSxb*B53K6Ed9H_F3)v5=VB#{p zuZ$zL$VURjpS;Yiw-t0z^JU`Cw5DS~$>L{JJ1>_e-on_RRfC+Tq>|}j!^`XW3)Rq< z>-u4DP9M(@?b>7;6t22@D}!Yc1+0*`)PCs-F$Z`;?@J{6fu|9aH^fzlbMRwYS9fr> z5$E%JzsM?w?$p+T*``PR6Yil#U}w(wwvrFKkAfQ0#>cWSYwBW?h$4S{r1MkTO8)PV zsQtMu72ZZ5(#%&E#7t13%y1&A?a`)H@U2#g&#)1^>N=CY#FuU+0fkPFwy`o{+{}6S z$jYo(hB229&k0pLQoD-Ftd#ckq=`0(GPa3(4_{$k!+R$`ds_a`_F^Cy3sM~~tJ!!S zSBp+0g*mrO!G-N2s}@=Pw+~}R`^?}5|AIPi80)_P+7HCCyx8CDdx!wQ95Q2G zErexf*UCk8HFj>{wS_wv(;4?gCD)g$`VaKvYE7AtOWtTcZi^9rKN?9TagVdTU zV7Pfzqi!OOM5RR`z8ZHmV6S!_Zo$U1{ouE{eX-pVN|qMMfaVAg&8cA47A)DO66-~t znVpoN86R_hpvA&y1mO=^gH`gJe@vX9-%QPuRlaY9_W#-pHc$i4WaraULlPdoEthnP_)<6})_FSXs{WhP5;oN>i0P|&g#Bf{%H9WZ zqUzBOdWd?ffxa?_Y0Fw4`3#OnP$rx*NxK+bP|DZUz`st-Z|Tjg!mcrC92@Hmcmrdn z(`x9uLSK1`_cn8vDs-wJx9sF!EE|jz9;;$CGMY`;nqb2{|I^Vx=dmgjm%FRFOuwf0 zOAeW#2fp7T6KB2w2Qi`axNs|MeS(c%>``RIh}z*_G@4&Dh<$ogvE>(wRRH_yd2X|_oQ2NsNZM(bUt%B8jqp`^DQ|sUH7E6x0$o`)Iyys z@lbxbS$-?=mrTir!9T*7zf?jT-1rjt>&l|{%Tjkpt>%;AK}oAGkKp)z`U6I_ zh5NCg{m=0JqMhd`_ML^&4odW6zXYD)IpFW*Ab}%m=W&k$zoc3fx>&(2Gek)Gy$-*^ zR)DsbBO8!sh|v6Hn3hnI#|f}`=RK3n3=!8DPMB76XtG*;MkH;EF9ix9Tg{yee!Y91 zehI|nIBgbz2NKkr;Ti#MusNV!$FDbNLcDv9b`T1=o)gu*|0r?=nQqV4hM=1)UBEd` zW5-F)B|v<^V2;xl$haW;>A8eNU2PWrR`W+BWbKyWSknJ9C;4Buu{GUywz7feJOr+C z;V78smS1#x-W)OORcgSMu3CD&OWH5Go$Su;wdoLvMolAp9TVCi3S}?NlUQOugp9vg z=7EgWP9ayCw7KkJGj>Bf1b5Dk^)i?U`X#ypgc0OQ+W+ug`1^aM`y-65$US>;U+upc z8xoDGZlGKGRX;H(91ZZ!bUPjE0fAD7x4`wl%6C*0Ve)F*e>;vQHf%fP7b-Z{g-JX2=ShL z+YmK}JH#*4%r8*!(8Zk6k*h~5A4{1LuEzF zRS6&I>4<`2)LBqFGm<#_(o}w2fTjRAa}DM*0HH~+7a*hFn|F}gg*lukI0~G^O^+IV zlf>@QNnSc;oLX|kA16R=;NTfM*INJveEq78U#GNh-y?z}A0TZ04U5A}2!K$*;#gb_ zphIC-*!h>jS?<6fF8u72oCd#dq)Hcw^1$XNeHk4Bs&5GKB>M z+tt}#@*BIA^cW-EsDmiRO+d zkN;O2*BK7ixAl{#(Mt$|C?RSPy@cpwl#m#8w84;x9)!_*CwfV=gos{3FnVv%8AgvD zy^iiZ{`cPZxgYMA^E_wobM|U`ul-wVuX8Z$ND&Ix(Yu_KO19_uGi=cO&Z#Ww%Z8qk zW4YFCUuQyP8U^V{o)*Rk#)+wEa-c>^-#gfF8mPp)%UPgn;SGAwy5SOE=E8rzbBBsb zLQ~JqC8k^~L1rR{qAogZ2Nk9@JSgVo!e~Gy_taOoomdjb^k`5@$Awtz#sDKnIUdSY zz^tLOek78{VPJd7ijr{(FISr zRKnk$c-9M?>qwYuC^dQN?$!r4d)SgsqRRb3f-`u&gAqy+=}k@Ide$!&!*wN5nQgWg zNmf$bRz{!9BDAH;wOhHI6q4%*QPvF7VCV@#)jdqh$NkLxL+Ld*3jSQ`{>Abi7e+!Y zcPGa()UKCeR9DcJ0bc@crzu{sdEjd!#;v&Ns-?S}x$@ou{Jj*pWmltRvn(l|AJp*y zDf=)A8{zL~-n#3l>6ODLThwAy_)H)Kx|p#JS}~~?25ZYd#$iR#CY#1JMRa!h*SY&J zo$(s>Ht4umW6e4bzAiYpII#`ZcQI#y^2nC*6?+Sf*2E=46baST67r-tfS^Yjv zl@QV~D!k;7*M!;1S%tOMEW&tdjvz(mk{}578;N{a%ziK8H3@HwoNjh<4(_SD*FevB zL6%XV;rQWF<&=U1%6QW_|HiW+U&-cK_Mbm;V>AgI1Ca*}Py4&NOO9J(c|nABRdskO z!g;=cnqvkd`Urh!-EnrE!+-lwr*GF9r3EBi(nbQHF z=di3*^tDWGdV1+aou*q;0*IWA+wHF>rGqrBCvZi>dyy{2P{f z+eGO&HbHC{^og?%7x=sZXt=+>{rijE*e(lG;07>Cf0qV*DcnyRIL?v;@Q9hvxG_Cs zA33dTP6G6*DHeUP_PwSnS8RAm4FL64g?Ao~A39DxEAbYzs{wF_Cit=NX2&oUx!7Ic z7!1HHt@Plz$uBm#W(sX3)BvV##WxyMW#^*p)Ka0cBMbn5uCN_xgIFDl_2hUCfK}A+ zkN)t(gqkHj&ook80f;FDcad}?;wv|I-}9~^ieG>XGz^P|0VjXf!#Bm*m1FWlfHAnd zg-Fwx?`br=TqOk18xMGHM#=izD|(Sd=@v`h8;XGD&1tH|?+%awaIUP`h~C-F!}?&h z7SI3<5yDoRFS=xC87T-zEP&lgs=ft?kml*e4v6fbbUKj(`|i@9*fjSXVDKpPvH0eX zC4O92{$F{sl7Ixmr2AX9T38d>>U|5?=1ck7^ew|_o+uUI77~k7VX@O7Cedelq`wp@ z0W^tL6dBVqWV5CG1_%x_E{43ll(1X@7zhRgw(b}~IDQC9G8F-)hXNE#uJc6LFUd56 z9=MYSC%m10xpKr=TN-Zizb4NYmDAK`23jh|cIwP`HTtw+u1}E@VZNEFevE8=ow0Ym zKUwh1j$=oHHCxMhdp`a6ts%BH31trV9I#F0$+gp)#0Zfb*LEA^SA1qAfPflBwsIUC z*cV1x4DO=8-vfTXfTvwTK-O65DqH5EYary(!SX_+0#1z2nkN-;XY^gO?(^*p$WANR zc)`~{l)t{xVxt9lQFi}h>rbBWfMgt+FH~8?_v#BH&G^4r>#AK?palYCs@vp$)mYqe zHE~CmONHm=zB0_k9X;BSpQ!e^I({V-V~KiAV$3mbat33H;E<#VP`URY%aA%N2&U>Q zpA(ftxcXbmooFXQ#VdenstTdZE~!%GY7^ewUt%_~=D29S+D-3%S~5dy8L*Hje~i|q z4uT+AUb-yl-;IN81`uASNv9`}@BuR;DpV|QxPRWk8M*qguEby5y{ZGk24cgTLjY8N>)2Z!O@Mh&xaV$_04kmA6U0dBupY7?W#o;&7VfFtGR) zP1#-I0(c76Kp0h+jba3Yn(XV)*`|;mn?3)uzpzW8e;m&6+!jg^(({QqUi^3KcO1af zcPrq+MSSA0au+_T7nIPai#UYU66LNS|1AT&?h;70_PJC5D9_e>!lL~63&6rl z*KG>NNelfK(>WcO;MS_NDzciSU+qcQ6>tV7q$^3eYntxdIQ# zR2AS4BxQf@sxYy{s2TdqfbDU=yv&Ps&jfZepqI<>BQ!Bp$QHyy6cx>&&rlRUpMPM= z_^-};q0X8S~pLr)cyY9(PqoLt{efWk3zDOTyXbwf!6QHxfTPl zh;QO3wAlG&UNLVnGJjTsA439!_yF_8&KrkBSlG2jmxhHxa2vE%yBeUog@NrfTSY7? zy$K669e@3bK4v34h5+DtrV?UEJhRr5iBPrHQ{W#d(lpOV%(%4#a4HZwvPNqS{z_Q% z*%5xyh)lEUi$=$#4uGg`Kk_YxSySEZpQ^NjCNx1*xT2(kn{;P8P0RMCx6Zah_;$!!6XPWBf%=@r!fnHr!@0=5x zyG1DZgj5x~OTNVBkL~Q;ab;t)vsGKCM`)gXF69}3Q1|h6O>nz&B(1rabcih*xr_|% z3Xsu?>Nfg*5AJA2TFiDYs)K_dhaWjuqI)=3J%@H4EAntr9LpOk2vL^Qw{{IOIdQHb z#&-os?{V5!)dp|Vh)0HPr7fB|S@9&es_(8D8gfz5Cxx*mTo8?VoW;)Irkr50Tl}TW zMGz@;4pcB#|K*j-TiX3YUPdODCIrfAVy73fX2#$~YKc=@hDnfRpQ_ZH!8pDdZ6)rC zL{Y^sUj%xx5Pg&NO+Jz1wB&T_R$yi4=kDNUsWPnZRM;`d`m@-Yk-Uxm%k+fQL5x9a z)hPPH8dwF3{*cj3!lpF>87?R~JK$Rhsd(A0>>uoKMC6A@N9pHeE)1|4REhp->HQL*PVZFC%H?smRWoTMiH@A6KDaW^Zu12jhyCr;9+Ks9set|BT;c)gW-BH{47}gHRCvi4|CiC}-Un&u zk!XjO_}eVL0*LU6lG(dQB04K8LoSLr&!kbE)*OqygO$Crt8%>^q6g~L@czngs1+wd zLO9qAWwcG~o?_OyaGpQvzMW{OdnH0PLL5LXWYf?L>-uO82@1)Zd_w{YbUinpQ4ZWf zb3VUv80>K30L#|uMUhmEJ~vxh_O6}wKi=e4xpC)er@)@@Zd>Es5g^Nt3O`uy&;pMI zDAnf7Hji|wPil2VjJr?LSayJTu>X_k*{ncithrDg6;Sj7ehKViCU6(+WYo7_`M|4d-s ze6Zh2zpviXGgLeVcskQ}H&M7XxsGJ2B4|b8MDn5G<`pC1jZI_5zhefei30D9jKWPF z9>{7c4)H0*MlrS|Jz@UfgZ~;mv<4D4D2w9pW6d8@!udEQ(WG`9tb+yB$)x`Y=T}Gy z*p!HcR348II)<3%;rCc+fG;`{lwTifx6M;3lo8)0(v4!6$>AM9 z=B`|)0TqCYHIU0M{Ihr>txeFL#F+N%ML%pw!meM>A(;M~Q4QBG!0-e=t&$03T?v{a&gDNU zJDrg_i6#-@2(AkG6dlKS6bAjSx8CAL=H9Ny2zAeMVgaXGuil?C2(`W4j`~q0oH3ox zqWoNnb$Z_OzZf75G52`)+EgTIjLvl(A@2Xj09%oNj=!J zHcfG-r!!&*OTin*Q%)ZM>6mt2N#UFK0Bgnyw-&0vd%I2hth}aV`tc}CKNAR8@%qmb zFbD7QN_NKaa3j2owVooCKDY7kHat?l#*QLdz!Cs9b=6LL3+q>DN9-3G|jNr!hKb|FnN%#fA%rr{_Q*2m*2Q=>27n z04i3b2?3j@jQ^bFwzAon<%gE1C(-}`!5V*!lXs`II`6Fvx0oZ+8AU6vElTn47mhi1 zSH}Cf_KqT2%rkYzdT!qUfp&2z5Sq77$H6`NgGL%ZwJZHYvn&`=>G6t4WC~Ob$Nhh* zPvlDr1R4HAc02(DB#lE_5)TDWY~Bg#z3smfm^^9dL;046J?R~qWk{-7Ix z_vr5Y{CGe&0!!E;u>R*Hg28|~lZ-~8&n%px+Kbu&AcjRa0Qn7Q_djGQux=qqO8<2}f(8yJur&lFICBF!on&n4oRPwL{@1E~+424{_(xWxRML)x(b} zZZU~(&Sx~vo%D^WH*Pwb?8!VF9Yk{=hGlP{Nl9S6vN3gP1cQ}V64=!?fPLBaB5k`s zX5>yo%ZBKcTc-36lRqw**B5L}81*Z6p83KZa>T~Rjke4K0-Fr3@4agk-S0&Iph@x%0R{de1~pPYEISc0?H{J)Sup#sjD3FSzC7q8CwiqM_2YnAbhVm8+u%sU zIV1kg8`=V5bk%NC_?ziV$MiV+ylr&CH5&NQ35dIY^81et)AGTHN0(K}v(sTs;A(iP zA6IOLu49YI1(>EZPSbVh+Q1I=>;m59YTJJL}Mor=IpN9x%m~W`2ID~?pMIk5>p)zbu)$L0)Ro&Ar;mG7xye3NLUbE_bZ?bV5do9=#5LE`BEMCHGcP6zZ-*%t9%D?o?(9fMm&4Msi zpBv}tSjH3JpL{}`4^N*oHG-)&dN=8;P|{_2hT-Ry$$6QtCYn}uuKCou?1z}mFXEy! z(^wAPpoM7+s&Hi2=V+&P`7Vym6vJ1s>O8D}te{?fYP>8aY1(8qsHF*U<1(I)u;bpV zl^!KVbeKV>OXGX?J5SrJ4Xi_21n3fF;qT~YFuh`8>vSBiST{U8H>I@2Ja@j*$D1!O zW^fZ%^+7qq^;T!Yj3aNJoJl5kJxs!*p^non6^fd6CP*n2x;lIEwyCIeOO$8?*X0z0 zWj%~5-G4$ze_i<9nCut-7s#~l>vl$LKiA?TL-dauU(=BroFv;fwP426v*Se{%aF(A z0n-mp*52arR%Fn+&!T#Eo`6@Yb(85)H1*0epxh}5z z^M^W0|7=D}d5(uv*PK2j8FrkH+8Qpke%FDwYIc*^veQy~x|uQDYr-9Nd?_Zj!k?%# z^5W!ZB3H#y;H>4SyLM!0Z~wwPA0nPKukj(Lv^(m6nQ3JytMy=^J#JaO0#2c|e^$lI zJuU3sLm7Ir7O1$+xs5ig=7ac!9PIX&F#Lp2`aD=0h%7OWNu}vpfSNqXeYi(q`M}3J zT`BZe*JDM@{bzbRrIt${24e!=1n1JIqIL}nRdk>g#Y8h$3_a4Pj1*&oEJ;t@XE*7k zRj-*V_Je?wy0g<<)g#zU)*1>+>57ym#7;om2Ub8|5Uw%uY}ZLrR60IMetvR^aZH#S zYS9F`MlTsZ6cb?c>SDQ!*?RIq@li;UQiJZ8hy9ru$jc@UazdXYG z&RuilCy!do#Cfb0rn+C#y97FhJM0^(J~cj?s(tPK_25oh+_FhtfoEyV`4Yl7>b`XT zGhs7^nVrJM)r$v7wymyM227PPjpoFuL;Vf~bC^BlS$w7GOfoa}+;FxAQ6mFep^o3kmHTAc+YOV%5vi33}L@U}TKfFA@ocNY{ za3%Sn>?)#M<``d*9-SM^+PISiyQg#^`r+KqER)RECNBHoZ`Wk^d{2DJw+Fq>?e|c78N2`_5wV`lo%Al_B~4YAqPWFb!cw=nX|`Id2ySS`Nv3Bi-&!};ft z^L2e2_6#!!@(NE3@5w0oTRLBvSA6-rbT@`K{hIM#O3`@FpKUkHBr6Uty)5S?Iv88Z z;UB&}L{zqwTMtn(;A!Gpjto#qS!VCJ-2C)uF`uUo=NO1qPMH9kO%%{Gt98yj^j9K;Uu z%P+)CdCfnr7E7^D|Ghpsnxz0_vWCMd{KT4lo26)B$jtTA_nF>JJ5`QAc@(h#ne~D+ z_jQ^Ooq45Ydcb58l^Oiu2A{Atk0?ihX(4Zb6ZuUM#&v9IyrFE?r)zj?L^`>DKZ36L zG*wyha75wUHJdIrEEz`sI9PFLn^DfY+cmchlaqJT-Q`@!^{dEX4uvoFZw_AH_u>9f z4#$$e^llz|l9JZp93E8Lzu%JJbJ{4QYat~Cf^D*iol;78K+S2c}Hd73QG) z)fVD5Z}<HdOl{u*zxF?K8i6J&bCPU#4sDSCmG#smi2t9m4m4_r$JNRDQv8f>N-V zOxuFi%)(DPy%ukp_UB`JamJ<1(_2p&B7meW6Z`Uh)+?Jsa}&wMHY>CM7zhi^C8{^7 p5lrp(|NBU5q=XzOvWd8PoMCSAF+mWdbNef9RYeVj5;;@<{{xmlN>Km+ literal 0 HcmV?d00001 diff --git a/P5/Source/Guidelines/en/Images/cmcunits-taxonomy.pptx b/P5/Source/Guidelines/en/Images/cmcunits-taxonomy.pptx new file mode 100644 index 0000000000000000000000000000000000000000..7ceec830cb23a3c7f50a1210d0dddaedea720c7e GIT binary patch literal 39218 zcmeEtW0Wo3l5JI;vTdKTZJe@g+qP}jDciPf+qP}<)T{5_ey?%w7~Su0cju42GjrwI zd#o4{bIpjDDJ$^<7#RQ*02}}SfB;~70{yWP5CA|J8UO$Z031j|z{c9q$l6gy(aqM# zL5s%K$`U^h7>Fzf0OdHPGgI6~sR<9jKO8VruI3Yr5K^*|~Cx2&ET2@=#p3099EGfI%4|IUuy-5tl*= zQFYj`FE9@NH@WJZS$0-~y8;Z$uf_%h431(Ovc_9@d1HY>KK-I<$uaC;<6q1XysH4F zo$6LIs$yVsN}5M}Yn7ZQ^}lU$MSf&5UD7PsF1D^^%z+EqV=( z=wyZ&)CkKH6bUHqF*y&`vh;e>VAYJh0_30lW9Dyw{b?AlQVUgu8l4rfYD&f}`X{9+ zWtF<84MY{W#N`la(hB!P(2F9+SMis6RsC4AQ=HfyBls?74579-=@XfTcUOdC&Dw;` zJR)C5qnZ&S**$TBbget0dUiRX2c5peMy#5g4X=T;Hx+w&MLKmm=g&M06`1W0F{%9b zD+c=Bt0kS_Qm42L+iqe{=LCv^LnKvj8JNGXpJGdu9}&*FyAH^vU9`ELF<-d*FJjY5 zDKVpZ*t*2HkKpMKgWBKdr2Y~Fqi*nN!$J`&^BYWRL4D}u5 zI`&4E4zx6Xeg1EB{|^r7f3x(8xOMR#^zgygAln2JUaadBgmacQf+v|HZvX}i?O2=G zqD6CEow+-Dder`%6BE36+eB(MPu9rS33V{qy>(@LvCF-x+mx=>c&N?z4Ed~VpfZrK z33~II+7;QRf;0kdHS`huw`#pT*w+OU?)V|CkiR`o9SPVE>?J!ROSWrBTg%R|QoR{+ zQt1Yl$V4?9K=QZ+-|#dz^qEG;oJ1Q!OC?F0jL>HF&%#hra_}VB@sN}V0y5ClGgU%E zGCgihhcObXwI4A{zoblGU2I7PCKJBq?=iqX}E1Y40~P8C=ky`%}&7~KSp z9`f}fvxV*N7}Mdt&G3&gW1#u7q33&q^*e6xzrSs59cdjb%?ynkX#XBQf4iXnYlr+> zAVp4hn)lPegWYh?xWG57)NuyFQyGzi2o%Ti^bllP$!Q>Rv<}$dMbSHsxaxHCE^A$l zQ~e>UkKq%b#DYh*bmWP|^tRTyCWY6eW6LnWhry!PoLJ9opNlNSy*)sRC<9)iON^Tm zugx^&OQM%6i6=M$k)XaWL0r?p7V~17lsh!}F)@YQIUnn>?B8M)rd_*F=PHpsTLl$# zClk20%K0`#T~%0@B0_;#;CXeOq^|b!SE}^o7V|$}Jr)f!81(nbXMO+x-~oUG{q4k=3(<(A|({3--lmMA8u*2D(BbI_0;b2OW-4M$mnTv%41AGTj9gy zoVv&br3Fo(AP=H7Q?#_ov?WHNLJJfkR7L2BGr>Do?8SA1((?K^X|D1b+oSM>HZAdo zA(pYUbB?2*bU*IoNY)jBK8o5vl^5hGTYkQY;g{f!-~LuqUGxRJ%Qf{`8*ML}nL9(ncgG zW=iMO1Eazims`0sIdQL8TgWV@l9!8Zh(%zLr$>?9DIcd|tHU^*Eva8kf+Dh{?LDMz z$)dz(BUD>X;CU=4zjTz_q?GS&GilP1sdCFhEcE2q=^?Lp>~8_$I0H1MT=5~4P;_VF zR{by-u8@dvXO|La1|QNRJv9L-N_U6qaLs#kJ)9X&#$NvfcJ8qGn67}0Pmd=Dxll!ERhoLP6slG{FjMH6JECj)UMEq=P zt8q1>yoS3U=43%|%LJSs{t5axi~!6LcXa-(G6r18Y^hAvemePX(AH_<%8nCc7L~sj zLG98tm-DKa3fZ-<^!A>=kiAaUl~ToD$w-@iNqQo9{#ug518DXkx8EmsQP}CB*6$9A zZDZT~iouF$G%^kfkT^3(7R{d@h7A`Q_IjW{?-qHprtWgQzunqMrH-W!!b?wXtFnaOFY}i=8TT8H6$;$ zi+ehlTVOJ)tNr~l(;gcG&P|M#lDzF)^9S48%)_!0K@cLAms03j7jB1ehx}@2nb$Af zZj0A;TrB(3ZY$@l_u{ENyl>b1$Gw0;5P(PQJ451e0{}qz7w7$#z2IMWfeS4ShjkWI z@9or2IBf2RJ737;fb?}oFrpr7lQk=o_)Qn#JOgPWd5O8`PR`G3sMt75iD-S1Xo*#E zW2*20oEO-sS6kS}{%xA$`V+$H^gIfks1X-e)G}Oa(m3*I0vEP_NQt65Fmdc5* z<+Dm#k$;}{b-wQU_X<*_erC5@O4q66*EeZpL=I0LP-UA;x-1gXe%8;IWtmidsdr<^ zoL>acI`LpBL=L)Up&Xi~c6Z7AIeTbGIcQ4Dn7*&OgetvPTY5`kH5trPOKfV9F^k}^ z@ub(f(vW(aeYU)FXMxF{+>^>Y-Yx5RDb?=K{?K-b`Let9z(G;q)y^-OIPz8%-aia5 zs=Kmqo7IYBt?Sm%GA2zfe&q6e>k>+?7WTfW?%TF&N!DqaE$C)%?c!vAzl?5(XLJ!c zyDjs-jS?5AejBoK0aM;|+o$B6{QRh!tt0Pdx-64BcDglx=w>RUcOlPN&>`rd&sp&k zCN~J_#ADVjH%;T|@Lo_( zwCk)^IB2=VT5YqiN5tggj*`{&nBB#TcQ(t&ZBWeranwZp@^n#l}z2xXz`^wWe*(+`j5loHr!mEDXEDW3$3wULtjazkyCv0 zGG(XR0pYNg4gc(Aj7@z}ir{Fqn4>nT6;jrtMDdkLF4p~`s!RX3!+1i;(8+SiW!Q#; z2q+>3^#I`KR|-f29l{%=7TgfI=J_&%&+UfEhqcN!-vTE9>dx+mDF~lhsXb5JIOd3& zt9J_?%Q<0oPEOZF?E%KQo|~a5AubrSBh!4~oH$JRDu3c;^8*`xtBZ z`Rh|&YKwJqgQe1^sV+U-OjbJys4k-_EA%kl`^p;4RReRo<&)k|5~5e}u_#zq9HLgw zToyn&`TJaOuZj;3ZKOVL!Uf_$ZS}D}4P_obwVhUvn!$cA-R33CE>B1fo9$%z`^~jIWxpi`}oAX zYV3UCKCj}e9kK;C*yye6*{iz0p&I{*yy7==ehm!ET(g%iMTBh_v94@}uZm(#9a)lD zWQQ054jpM^4xGrk*UsQ`kcuM*C901O^$_t4S7;!7%@0$4Kq!dlUsx0~Jl2r0RvNz0 zi|9Rs&KdAg`a7U}6-41d24r%~+2#PZ zVi*(w#{mi)D-(qCpCwh|=@d9r_#u>74OAQ~T2KiLoWX|dFwwasQYlSus{4Exajp2O z9KP8!hSqdVn{zK$nW_WDy-v&=Zys<-nBkUqU2>08V<+T-uHslSgi=p37(5iZrs#$; zLvHxtQXr{M{wyQpuEX<^D;ggos=d)rdNs5>xmn%6Y`zrpg4rP@w3@^(dMevYWAiI@ zKvxhV+UrsfABKW&!OWt=h1CA1I9i}+#O;L`;EFvPWa}7^! z-J8v^B$};MVeFj8R}l#MwU8>-kBKk*rHtHH0@?$!ji0d!nVay89lwkMt6TB@E;r?^ zK&X)f=(?sPcnsXW^rMLgk*HGC>vDo1h*~JFPSIh|z+jUHbule>g{9O#>%){}QEJRz zY^da9p`UtMFIFDGnW+divSNh~YA$!qzZM_1m|g%nBwkkpCS1xg7C$L{L48804y{2s zVE|`FJrj|ahIXV@QSy0R7p^XgX2^QP0ZJUd|h4)ub5;GcRT` z;#&S+zT8q=YC7@Qqg2uy_44FzLBz1 z1v0AUvoWLcm0`>Ynin9;I87j42|dTxpoo*>$KhmBX8q8pElG2>nTxS{C#%h6K!nW@ zV_qf;D-A(l#vYX9Gz8F3gQv3c)TuXpi8-sImkyFS*6@zQQlm){5r>fVA*$kfxK@RNcuK27T8akNnTjgP$4+eSJCbLa{35}?|0_N zu4ZM!#LozC-Koa)Kztku0#iDI@IZ$W;LzxPU1W>2KCd6w&rVf`<;lsm z;fW_W_|_|0;Sjj|Hn8hg?qpc5ShbJs&F4YkwF9H((ALD9zpQNK7oD!6nix8U>D>3d zqwmykwXs$osA@f}OJLWxs|cAWSLD}VJ=@~I>Fc`_m<)vO5o;7zP_SnHka z0}7V8eu1O8-!9Q@+ur=k0%g^~oIx@e*BwmE=1<6MUdRZ0dC5+SH#WMC{lrND7*q+# zIDbjHK6zIorh#U%5Rh;f+58mo_!l$(!2(@=knBxw#sO{SO?MN<;$0<8TIz;FkY2is zNI^JWOgDm`3$4(|my6}q$z8xYyf-HogVd!WzmL}a!Yxbu!pF=gVT#CGJ zzqX+#OkN|Y74|U*NAMIr_p2B?`zdIpg8dvx>T~h!*Mn=tn_90JC*4ReB!6Xv1FVH% zYZL;2^GJa>A)h`Jja<*F7xn4;>pQSci%7&vJAxckoL(O5BQp*mL;DP|6u=9D`SifE ziAV-DH1m}54^?4e{NtW9Zp64f$5H~^wU0j>Ak zuwH{j3Oy23qbbdP64CWaSUTe9Wta^TJp|sgSgfBp!1x}@d`cTXRB=y{EoE-mMHR|uTSpHvG=DQ{Z z+4omXO6vxv?~_X1$M8zN@@GT1T+D zGX6-qZss-fM%C~lDzM1|>hO+Oe>(cprTwg?>40XmtL<+gIW7xy`)JO>6=)`carn_> zF|@hB)`U_Ogh?C^`SY^1k_W3_oQ#8`=Axt;0WDoWKMg{v9D-qcxk&C_MFRI`)i{2d zhzAWWC@kS0y7)9Hjw1q=SuI>_K7Ci5{xJjl|F;6`|61YOJ=p)7TY>t&6cO}v|IN+t zUjqiV|K?WsFFM1&tJ(jL#mE1(!e84b!+-OT_^$y2h}H z{Rj3arRU&iWdHBjDH(9YB^Z5b`%qxmHu`9`7)4Fu8v(GF&WB{u`mQX7b3G>Bd2^_$Cu=w zP3Msbcu2*_P7e4~(D!lAw5L-irR9QxE9HbC`;PT9<(xB!)}8?kPruM=21<1P{Bu=i zohcH)S)(bETtmK2N^&(g&ghlfjAvsI+kqrZGLFYZh^tQm|QmV{(np??bFR zUugS|^feB)G%<4}x|3$Fk5(c)4P$D8ow49)_11(MV@;bG7f! zW5KUntEg}n6q`3`stX7Dwdok|kKI*UHkL&w@2%=Y5SF&vSlWw3`TpGfZ%s~vC)Wws zY;U^}twz<3To!xc!F8|mI@^GgSMi~f$@Rk_&)cWHS~B7JxDzD@Gsf?{UC0kSl}Ea% zrC_fL82L!uAyc2rI1W5~bD5a&SUp&_^99Qy=XkfJ2@vJS4Hn+brW;296 z7FKuMiDX1RGD>(oo-p+M4`C7RA9FP&_7I?RCAg~-aWHH)SJbtptUF`=o>7UC6 z5;?|J@vq925J0`(oVns&a7fn{nDE(wN1egTQ1q~7t~dvy54I&uVmg@?mkQ{BnwPVE zsG9p6saC>H6;oJxxS*c~8FBa)J$Ict;Et`?MY6kl-nAT2@^}mOF8Jt1Uc)p*rFA zJeBI?kmW$=dt>JW5+R5)Al9R|^U1o#=q#Wh-?{?+zA;Vh#Q0d%_`?8OZ{tB|)l5ElcJe`J;W6gVybG!(Pqj^k8 zZ}kh&=k<#xilW;vln?G83cloKmE8Z@B~qhcuf2L^4rwAZ+1qr8&M0O_0>_x9}Bb+}n<>qK#I$nZKg z7C^!#vQxx|L?am>gOyF#1xA1iW`aehIWeloNN+>*J=x+ux*zV=9u1hr`}zY*Jp_G! zyq)2~xL!*tMwnfo=Z`o6d6JHRul9nw0ZeXShB!n%$?O3-VOq0x>1aF&1BtDxS;h3?J!>^56o6KcZ z-*XQ-sYZ6`JjegFMKnE|*W4kNRUjaKx28s_4aTw)AsQ9jpZeN`Az!UseJ-v+zm;so zIDhL`YEdz|o@Ys8@|Jy!apzQt)DEcm;#E6;s$H^M3czT5tCG;4=WB>Xx9eJBE*w_D?|nlE%*s{@TAING zJ}%TvY_fz*6_V>JM%iCu*MKTqaXHSQXSY!9zP+m8JT(8jJxj1KBDjolb~N~)D=S?# zE+iRZ9j7fO=hmEdqZS#7Xv#VT*cRr2A^$*pz^0<4*6^aBwL36>Fq?P=LXQF#%8i(?2f(n5^ECx3Pn&$?`d0GitLx zgE464dT@a0;wncYnce2ynFjW*3D=CF7RGnb5Lns$wU<$0yFL>ggoqv?tR}`kc7P0; zJ~}M37s(k95r9V~KfDipALmE5?@2qW)t|2AG*sWX7TA_eQ)u0>T8+pH#KMx55>`*e zc&j84)KI4dRIJufkVtV+xN_}`FsZ=>2~xZ<7}#Hmil{cdvT?9G;rY!CXmMEpV?92X z{&L>Ezh*{ug5e9n#!_lG7gBcq@SHpWzqPlc%CS}Z{s0p0RXH^u`O%BA7+ zBZ9rI*#EX@ufh>Z$~4-#XXM)}v!JHU#emTgX=~o1@rLGB{F!zdDb5B8bP-n=&!wis z`q&NThJWGJa(@X*5r}7Vvz*9ORESog=b_qw+mv!6&()XrSu^NTDA~J(I@*s~Py5Au zkC)=9i4a!`jzp2<Ztq{iE~)NV`C_#aC$lestC!(uKy1x`}RWQmmFK0aD}l`ymrSAj6Qax-MYi% z>E((FRflxPgP=H?dIqQ|_mi97*Mx{IJmHp+zp>!?friBb7JR(tCPDC2pP%FSHFlA1 zy^FSeLR@7cnmhuWHG0Vxsm{}GIej^48^;5^57LPOLF4(8ZzZ7sWDJmtov{rVAE<^s zy?b^|PF>ZuBU(A8vRYPG5T5erMq)GBW9_j#$V6=eslbBS9>AwA(v9a;jCuiPJ3S_r zWxlZQ1FEzCc=@B|2cMFfjkTvmU4-TJH0ty6BamP`O!f%q9dVF3Sn}_Uz!`8RUYydc z8o_}-8^|nc({D8vz7-D~iRPdrCjSU|Nl_he63zilvg}Np$sT>tt9a2^%d9|_GIz2G zPb`UFz*cOgV0bzueLL~_reFU^(7g9fIb^;8P4Zi|LGYgtw7+FR6RO`DBo^c@yc!pH zCS8|sq3{J6<>DC|R(z?5LJxp%35VVrmQcHN1dvxe_i*s$qtqJ_X93Z=+1%86S`RCU z5FV~K*Y0q14;UdCnvrI~L`5wDSh1G$k4NBZMy+;Ro48Ru4yPlWPB+NA7l zJ!3vM$!ovRhP>R<|CC2J%GHdnnpk}qHZ8(SZ@ik|N%iJ-T0J!;Fkj@ijGWv6hO}9@ zmW;ZMV!G3#+m1RKM|)m58h^k&Uv22Iw2^Bp2i(}a+%e;<79XV)0Fm5hyFLswB_3;i zWf`{>oR3t+c%af383>n0RK;-qK=x3J#Cgt4i`tmiw4I!j87yEq*wSmEahQF&= z;ubfO$BvB{5v}5XU3#ovaNsvDL??(Ks)D0iX9dgiqD zB+R>>TK`zyGF8VHzvZ}TYD6DVv}(piA(2qKowa^ZaB-IFO4i@zK9Ki&6=gFH26oE81)8u9^Wa-HFKV zZSi4b)hiUE(D<>qoxW0v$1T%S5MKHqZ%Zi_!hEpmup~iK5I14VA4NGefD+;-%#H<) zj_rc^6{ulzI3DNN6c-5Y6idBDr3NyN@gh2C)=rS;4SC8c#szNz&W&d%E|)L>%vqaG z3`Z+n2nHfbe)eUWAj^wibx#~cXudwetD2vUR3yh}S9PzliX6MDq%y6p)pIT}y*5ux z@^s^}t!(r=QK=9QS&yqKu+|tQV`eh8*Kl=2Zy=wu(YS$_yO*IDWUbj9cOa6W$c_?thu(tlX{-rFqOHJS({?uyhFnbDfTi-+Ci znz;i-A=N|o#De&V6+9qhmJcJqhNPCf)#gtuQsoqdDxU@e{+ z0wKo1WKVtHM4_@U&fmb8RO###zO@_|olBBi>pd-^iuzH6&oBmP4&{e4HrmxhS9y2b z1XEM#X4!%KCEl7im&s;CW0F{<&T}p9SppN-d}i3%`vc0uh0Q-jW0-cHG{tWcDg8|% z|1&iHTV-xS<=#BfdHXoj;z`p}#3Ne~0;p8dHuQLcq@I zz<<;Cs*K5U{vk3PrIDu!?Y+VVHG*(oEWVOLdz>$9hd5r>rV@*O+gY& z{HisJMiw_=I`zCrL6q5#{RpWj@q&012IVAB%(N9PPj`#MwN@YX-k@|^Yx;Rr#v zea3-u348Ez>k#tm#kH5N*Nf)k=|=v~B^{%r&T3mf1j`ALq?V};s=-w|pX`|@-6@JGmuK zd&B~6tcF18*vw#kUcz{{%Z)WWgfDx-MLo@9BFT+h&zx{o-Y)Y8>DolSm_;Bg=@J_Y_qgy5ikoFsC9k%oVKS zCPZkxU7(#DN_)AyY;O;D=L!mB15OiBUOYBi7H*e}xTYPAz+7&)VItJE>+{36Kj7F= zi96iQCj+Nth3)sD$PSBr2^4_~6<$yn3c-312?-DA@pZVA3MxC8;BysyHt&ZMMKq7k z%R2yZkxh}vH1cy7YaMAg|8#T!xDaZQEUN$>0wkL483+0>0#S85#Zv>S_XuvvMhv%= zL%+~E@@M-Dg9uP%D#w`Ayq&&&&mrkw3V3SP2Q2WPaIu`=Z^as#4H)ydrZ7OR zmOr1cekc$0|+t_RxzGdR@eR-vN-Cp4DFGQI3-q2NK-a8n z<)B$ZX6TH>xF3c}_MZjUQ^3b%%N0Hdn`SPA5B~X&VRU2sfRRv>t1r44MK*s?L2K&n zl(yABhx`j=L2T&B4oD|$^2@21`^j@7A-$fAX|yrdsp+)w9>&u}Fvc3`6xE>nS8W0$ zE{@pHD7aR`dbFew%6S>-+4Bj3&T$M0{BZP?hGdc{G4lMKfh}f&CHF#=LsQ-~Eyf4S z`tqpGS2b$Mt)}nJ1kc~OtPy=FROo;uk-XaLs{N(!TUdl9Bo-s9y<7?hdZAv1p!dN5 z-+>p#4*(XK$|rr6H%<;7gjtsmt3Mt#Ow{m&t~jpksr0d>Yu4;#9# zIoC!Q>w#)ZJ$OUF{6a1m&-7R%WF!Q6RR){84n0>-hej)?D&~*u4Lt@+2ji%)+poTA zk9UgNN}A8hC|3&!XL++v7T!=@FEF6*=dGtDS|L$GtpYw!`3h*4iM~QgMTio;av9L; zqXBSgw5_rIeDWsqY{#i=$8xIlX+xAb~>;jZ-Gm(&InLtK}U63 znFg`)*TXOs(I~s^jIN{~&;v!UJfSv;a2fTD*P!f#URu^b+&ZeeVKf0@*KSfV@L@JVesyu|)#v;uk4`ifzNcyj(NNj5rVi!X1x&dF-mHb${D zooQB=r(3QKv&to_wH)9|Cd?K_AcTHb-tmBt8jX=z3SwfOhOZb*r~&KiPOo*!ebrT8 zWK~CnDsgCR*7Lu_S87y%7pO1*s)h9j2I1RTBZ#Jp+FfMANc@Y|6(0_Y-|QzYAa5xr z&n`2Rxh`!i6x{Xr!@>K+s0LaRfv}ivrSB0Tr6N92NAZZ*J`uGzK2B#ZcT~96Q*%5C z3k{?9vq5ts%K@SAAIKqdXosc*><>urBL<$vplt%lM=NjQl}r9=A=&*DDZN47?W9?s zf>}Qks5Db{njD1PeZnHp81%)4i}gI$n~}v^6d8 z3f3?~nr14=vbiQ5BdvE5n9Gh1sSACU-hC50&ylwMzlh!T+wZ@KT}Wv<`PlO*+)Qux zKP7fQ&3S+jzuzclVEGRy`hVL@f9r$%n+DT``nvW02!a<}tPlPRrtLu24M}7NKCvC6 zugj9E%w23V>S7)GeUkCGfd_rhhnVk&kblQz_C#_)o0xcl)##Hk^hhxNFH2>#h()Kf zCF;(vU5@EUN}96p024S;DhAaLC?U;cF1l25ZYg!6UEf8 z%Ox4l#@mrfng?qE+k^t`OfFMm9^2G`y-K<#Pvj~G$XX{JPbg;!{*fqcu}a>IcslaI z9Bp?XX<$A`S66}~N0~O)6Hb3yyb>{-(xS64KY~NzZ!y6$!MQDP#ockwgkYpabI@Ke zp)q{=0hc4(@W@kmQ%w*?niZf)Y0E#IN6^6*TGV7D;vGo3U>7FQ-OvP(*cMELa z6wB3!bL>6^C#1Pn8Jsz0gxkHIS4AQ+3`JSTIe(%?G|ieuJr z2T+w?c=8Zj-Bg2>W`=m-?uMYD@~+JbtP8hv8=-$DEG>kM_ZjA|hQommA}0hPDe!n}=7*^63P#oCTaDwPBQZ?$hx}y8 zT4CD8Ues4~>m@tyKC5Jws^FfkJ$QIzr(?YKgsdeiY9sg~+O8JDHMwfBIfWfB5P6;R zlb=0<3gty#&%clWMuwx?d4b66;0gZhiuBZHcFF(oF3esWAO!|YIU%RFeFnkI|D=6c zHzA%#nR4yT#z)|#u_Kg!g%0BwzD#~uR!rR)MLgX{+~5AALG={ssm+k9#gIzZI(F{O zK>(H}O}Hog#FnONFr2B1>^1=TgR7A&QyyxtMF zSncT-7FBgRiA+(DC0Uliy4KHDW9usxd(h4FhZ>~w8qCslJ==bT++14{$CyDIW1Vj!kOcCLu$2Cd3OWBUUE0E z>*zLw?zt>rJ5Ylkkq|}Dj-*&0S*|W^t}!azpZ7_{7_@KnGH^^sxh=w3*97BFK&Axz zyiGv*NKhVr5^@&=q(iiL_fWQ`mxW)d^do0^QSU{IUeX&1=`U>>D=06>1ZUlcJ=f}2 z{ZOCRST0k;}P`^(hZB1gPu(5T(3W>$bu!sGD=HK=y%Kdm#p|Wa=LT(c;-V zv3#|R;e~T-QgBzVwT*0HIoWh=;F?cVj#G!lq6P6;{zm_ZLOf9G1r|be-eG{{9(gp> zvbJzV2?=$#PyBp(+{PPhx6%2!#|f|Kax}5d+&-7X>XbunalH^x4m5?%6xdPIyWmj1 zfEOSBjTb$tC}b0K@_7QXH=ox`!RsKGSjtl>=#15aNhAmq$$ha`#ltMuHme+@?E#c( zxJRmtQ4a;oohqoiYk@vVtH;#d6CR8LLx~xw8h67FB*J+@){h$UWg`0A4QUZJ-cPa9UPw zAf#2AuiXs?#SEv~`uh1M54W1-6<2#>e=*Dwj`sBS%(EdR`N?%t#5EJQ`Wd`>eSh&7 z)5EnB*X9PidV83E_!ReudZ%sA4$sxCGG3x`_^id@c&p#{;~{Kv%4QvV{Xi*Gk)4y8 z(5`fPa&gsXcB^jz5fK=9qF(8@D04M2+Og7HLdyY_S-qjIO`TyjfjsH+dd0b6TUKTz zPm++s-Q4(cR9x~5Ki5x}=Dc@JcQKAA8dadu2btIHO39|h*v-_P3huV*Ye^y}%J*Kb zZmUmml`aq21IY}afflonc_2g%^u;sqkbs1W^@_D}PwtvMMDzV2j$Ba;Q?1&(iru9l zXW&Y(Ad6=|(MtJLDublrRC89}SgO>LR!xXzp(CU)kW3B2(sn|87L=U-JWS54x^#*PB@(zyIO&$LWz~5oVJ8 z=-^udXcn6VcD~l;Xa6nC_|xyH2)0p+`rCdHyf@N}d@pBQWJh7PHIw10G*@#2FQ%C) zZnC@D>PB8n)8S~Ta&#~rm#7n3#MNOGm$2q5VccJ82;l`!8Vy=R*B)v6NM1D|%Vg zX8mrog+>Q;Tb+5#^M%gV5q?c2UtN=-)AAkndnDY`{U@G}>(Vu>(`#I&6QvnB&SlN` z(?wyzXVpIRU>vLE%BlNSnM;H;lVq8Q-9>_bCfTOcCI0ebMzB&P_a)l;#WiX~*^Ze? z1?JY6T-XkC{Ma8owa5O7%57l{+LxS#l+9$RIFrsh*HPR($OPVb);WeXHVl}(JDDM_ir&Q>H- ziI>Co371(kg83pSkmrum%AuL3IwIpQr48Y7s+I+VcRRt2gADC@jf{9Zo^~Zq=1f;@ zoTkplR>W>rrvMn7+OYObro?63?^;>;DaP!8t!aRJL%;(V5PZ?Lu>`y_@K0Okn=|Xw zz^pkPWG41}*O)m{N}<*#sP@GtX<-4J>e==hdtXG1$kxiRhL)RV+pV z-Xn7KlL7a`RpuAOiwEp)t;=47vYI+IzEv@`6(|B@lSLUTpo4~ggzwCFKn9(ehjL^< zk|Y@FT};4LvXQFMcCgUWS%{$2O$(h08sOrxaS_m*V}Kgu3O53!J9iCn%mIuBYy%bOeCA^G>%FdLD36GunQ_QgbqCC?6EJf0QsGaU;E*uKtq(i z?rIuE!ANLgpgsTl71vu_RI4wb%c?5Z^{TYs2nk;gnZ|0BWOl?;M!SkK$()>+1uHm1 zBC&k<;Bc_l{U1CFhv!NTKaX6Pptlt*ZJ|HeART-ioZ^Ym-|!{%py8DS5MP0hUh-C; zos{f@PL`OD?nAn@BQmG){&@Q$8U(+_k6^nnrmr9k=Z3`LgVGbVmZj%bV{*s%XXx|C zv4tXLm_0qjYMR6#S`TM+aqi|_Q{2yjw;}m0Nq!}koAYr?=I{bC*BKgA2LF+LuO3qG z(EsdRn<=38QqULdEIMj&tQUOe@gZLSLi=Z>s2NoaU=&aQfLq-E9P^m}(kfo4{cEq% zb6WMI*qSOtzChNW2vZHtS-KRY=(8!!E!}wyFi8^E>54+PM*{%7+_pV zRN-LQ;l=CtM$rBCj%zxjuq?fS>Pgsk7>B(qB}q&@<0{IVJ?U3uMp0A*(bO3KWfYAf zqkHSuJ{)b?CW(ahFxp|B6O-`l#gIq7+q!c5z8zy`IhVEbm^jMYYDL9;%Odajyq)~8 z2`1s8mLUe@mBbFr?orq4DS-sm#!JAWTt^nKu@ z(>rZ(%v;;GVP;Oju})-8<-^nu_k->?N=2z;+Ocl(1#k|Vl`{-yL^tj`&BLNnpE=q* z@QEYOh$7-U!NIfQ2A~bZyU={cW~p&Lc`;#ke?qj=MH>mcS}cRWlq^v!N$Ukf$;lOcRvQ z${hj!Qyimf$_PyBvgw#FRWs#~w5?G+!lk~5+nkoc$Vc%ghBD?{k^b-3)FlaD8 z>?lyEM~G~$uMhr(A09t&I!`RHH6ni)Es0%bN@?y9x^%qi;%O@K?fk2PDE zRQVt2WQ?j>KGYlVF_yc(8i9$g2 z-_%N!l|!s*m%vGnG$$xoK)kkAxYLxg0Mp|6yC614e28Dvkz%%U(YQFh_mPV$w2JJ=%^A~sVG-|8UVL9Pc{$LcwuxIGaFzj5ac(^xEOjXOQfQx1t(l6Tb-m5y)LE85#*h+OwVyK32jwMS4F z6JOVLqm65}!%3GoOT)$^WTOX{rs4T|)hSP~k}E;#|}bo)gJOg4;*zv9G)PY*2l z)^|@HLL?YN+oq;rLvggLvK6x>;<}w|bscxfAfY5jb*H(g0*)rbJRTYvPj}}#{R13a z-|q?n6g*y3SRUUin}=stDhZqFE-J(4ka;2?4h9w<&Qk`6s+7kbn*D}^4j}Z5j7#J33Joa3d&VTVlQw@})j$W9O&cG`SWoaxZqU^d_RlIoo>xH@8 zY8$9Uphw*e-2dFC{PY_fP|^BfwdYAc@*3K0TOx*{xT?pBa4(NyWk%!x-#e~OJL8sG z*s=)`euIot^e!=Jg9KY4YC2e}jl!ah9>QRZSSTmM(WI(W_x=ioff~**(FZ^oq79nI@04qLc zBQ|xXQL?=rhxKmxjq_*`?$4ZRqC^^`5 zBTG;{sEg{DPs?J&1hF^rNk>DeWrNPUXj4;7J{Rv4V<)i|)*X^L@w7mNltsI3$ND)l z1!Bz46yrE2B$<7gu!!^&eN7|;V>qoMxcX_FG@oQ#^}S-@N(6426M6$4M7^gB>E>D% z`-GRK(3p*ULE;jm-WF2u&7ud!WMjWVY!4#2L=6zf$!g1*xI92^6tH8*0O+OW41G;J zO+iib*=dYsdn#fF+UhCPeX3j32z^I2dw`E>R`HVjV&&~-FvRJHnr{NYomK_v*}}ce z0B$ACCx^YP4rIWaZxgPx91>%|f%8q9TW^3;dT0!L2?v@gE_#@Rm6W`2`isg>N$SiC zPY4aK{Zbh?Cp@5_j-9%xW=3q5C_vUY$avfFU+GF9_r6V|x85rOkH&DHR{I+S`S@ec77JKF-*>eq6-Z86Fqf%PTyZK*Oo{K~T@6tU)H*Svr2ZPj=2QeEJdQV`GhopJ2_S3gn+eWa01QX84)sYi zYZ?kS)hJKsfn;lln&oBu8fn;9`1;RKq|W6H8jQl9pk95712;bOsN5~8Sn=MebRVc4 zeo7Ac2K?E=|8Z2$Gi}guIxCnb=0gh_6uP|BN^yk0Bsxe8#hIp{9?qNcB&th?1a2cF zinQ+3l7}AQ>9|{nj|aj0?kWXB*c?vC4JGWr0p|u*vG1ecCQ=0|!CU8=X_kTu4+3-L zynN0?d}*b_vuKYqyuTW6BIea_MgZG}JDC5uZTRU;I}rD?ZRlQxJ4f_gst20%nnyYk z?q&UG8&dGSBkQz@Zr@QJ8cqB7EM#w+=(tBG11)+hqGurPSI}Ki3P#~MnOj>an%zA1 z)xWoG&cHu(bx}{(xac4_jxSs6FE7VY)D+8?w-_CaoP~L;Wj);PZ>MPoU(8Hx@3ZX3 zLYSYgCtB{ODCiw<=vS}fy;SvE;o+V~tk8$G+6+^ayabs#RPVN59NB$4K5yUjUgo}R zkqu)w&}{icTl%Be5);Htc%w*Yzu6jR5lpY>+pafWDN$T7`IlP#w^ucW3mYKtGrWF% zMc->`+@^e1lkH6{vRtS+rz;?1-&OR1X{?s$u3!SRAnQVnEwYI!-d| zo9Zs!KZnLE`}Fc9f6DpfD4VB}3M+OIlzDaI`>(Zg7_u&}`yq#3B<&UEZs5nS({64^ z9W=@VeCP4ZG2-K_qI!4VD@i)J&syw<8}5##Q@~K^eh89;$%GJ>+r6<}6*kM?xZxmH(_T_d~OIg#xgku3S|m|M`nuH zJjAo(n21RsJx-C%(c!7RKr2}Kd985QWp-hov~_{nPY%@F1#E>RpR*6Hr%_R@U(Ji2 z%yH}M=g2SI(`OEixw!&}AKZ0x7<)bMjA9GgzfRPnZ_+5-S-0POT$aCGM}ZF_@Z^8^Kf-++G-m5>=4fu2tek?9{tfz(G5V!8_P?FoR(JM`l2P<(62 znZx3J2yr4A>1jVe{cs(clry&n?p@DV(8^dVpG8+q0VlG@CHC3PxXuf^i<|LfdYjG! z-5Vu(5B5qmo*1%>co4o2ahPo*)Ql>4FeOM{BJ8m70s1O8aI)}8u&(U_QFwwnbRqpm z-LltkJ8kOM6>B3`T6~CW*b~`NfflT{=30EA#qT>hH`{x_*}w)qGs4gg_Fl9LPq*Ax zr91#T^Z#ziATwMG+6uH};08`E|0m5ElUIX!OqRe)iRGc;`}T3&zeBHZV=H)d@|9j zdWFGNmxWw=d9nk6#UR+nq{#{?bnd>7wq((@ZCaT6dh>^MQm1AU;qiB&rN))q7~@=8 zF_{W@!RW%7?;a1ht>=7-X9J5PGa+!8Z*OBJ48fMBwp&w+MdEyVNgY;38C_CSF+VGl zk~%cyZ;5AoVN#vS;~Ub&8?PTQ?rWRdl7h`BHoNh&kV#@63*}X7iBw57tw}XxIegmD z-6~hd(QjhC*JFt8n3RfZ2oNq;5hV^<%z4E7&RedaGUu49+Pr&zK|AAszvzpPM2}_N zq~ty+eVF^&z-F69HM8to{j+P6#Uw*kz(Baj(RzZv3_3HqUqAvL6S_!fR)QSgD{XF~ ziHCGi{VRspum0P@Y(4Oe?1CCw1z+afauLTG_F0+45Hds52$XsHugZ@CQ5;`&y7Hr} zF9;<|;j#qte0bPpv3Yfwp#w-b8^NLPYHn>_7b2Y7GE8}#QddUs8M8fDs}XT%pRi;; z%E_@)4#J;)FbyqIZei`@-Ap}7nqlk)Yt}|$+l)cpa}?+-vAhZzlye#w%uo+-bSe-{ z6M`d>Ds<59Amcvb_^6Un*e{6XuD0SS_&MPLdgT(Y=^(@dVdS!_P2?%T78MdBc!=sV z|9HN8AeU!sm4sLh#JHu@cTJL0O@7gw-iFPipqI=~x=UTLjS%8c0#1!pmV~lR<8cv~ zu9F-91R<0 zh}G#tJ`Y^w&l6qBZ>jc-CTx(!T_??e0LYpl`q|3C08&nHQ%jwQ0EQGT;JdkvaIXPv z=T5p%fP_c7eE=Z(=&O_We2sgS^KHdj)p(v7zI=nU#nuN<;_*hE<9-ckBjN2#RCk7` z#Zbl1MeYn^i=lkmZZMZd294P3vQJ8tuPKh=MP?gHgp%3pDLgVcV;Xp~-V4fY=s|ME z=ysZ}5K0tuC--!dtcB~WI-cTuP66v@9aq%20ChL%C9he(=-q*1O}oW&nuXw-PnReBRbUQU%KUe@Fs$u>e zt|c(PQ?Ho3J40pTp2G1rw0-8rikENB3J2@ZIN5+EVtGLj3;}IPsBe5JvT4#ma!=N` zC#4p93hO@JzZfs9mtFpRKj1go4S#sqHP7%>2Dt;a67b$Y5!4(H90k_5&0dhZ-2uk~ zs|DR47?p}%I9Z1#+ogF#2Vm9LXC}!?`9`65GVhb+`*&wxdT4f}lnH*p?y=3{2ALQw zq(gzwLwMjX=y@M*WHtiw*@U;b?>W}z4GxVgjzkQqXh0aEwjxnam_hKek@dv$%&W-J>(tre$DHQt?4Ka5B0KBkf0`c zUG7cYdSi6k*(%ljH3-ma%|Lz$=M2xd4vO?8j$Yk@U!Uo|_c*$HkgRP`5Euf-ppDdY zZ!WD}ejr1mhyB2IxK~QgPyZ}P$}X0Uz(L)`u*o8F_SVWl!kY2S9JkKf@0e>dw2C&A?vN~r zbVvuk=R}H|_C0huu&O8Gox^5&5VW`vJpEiR(G7;Zr&f zxEW>8I0GF^b;P{OC5|aznyghu!h(2n|Fqa)jR`bt zt2LIs6t$i}_-WXtAqsC$SfdsCH7bDS8y5S0{_7-Vpoc@e+kzvj^T1a6lvYK7C``tC zLX_8WtRfbQoP@RAr(`Cl8mxD)>gf!{mBL^e$7XFb?yf}Ek{NeJsNpc1dXF!`uZ~ts zU!FU9?^#P*Oa`V-w`Vgcr$)h{f9qi0*e$Ax&y1E}=%`^Sc{8U4gO!glQ+5w#Q*@Sg zI+gQYE5ZRadoGLiZD*sf`qy>%Q>h&6wTRbNE9q^OjCvfIBkTAfwDep4H*um(dGTZ} zseRi#WWgj)+Dj4Q^AX zxH2?6-(MC^YE}5)Tuo`abS`!&5)$JtuDB+YH=ihN;K=%fx>)!HQmQt(%krDQl*A;hgj^x0ZJ6a>5U*tCU?;lVEJ+){MK+I zoMh}0vcO;Ouc_vN7&_gs4}d;y#Z zH%|VGL4o(X2=cSx1*U$RiQ!9PE!)Rraf96+k8QisTA`Lfj~Pq((wp8(LC#J4cg-kA zE>|E;C?94h$XEiUSY-dB{jR9zWIWO34IORDy+-O49z_kJ~n)?GTR zd=J9k^$}m#Ygr=e&&$3G_)O5QE($(1ccs5^$6E`AtB3QAAorzLsszzT36gIY6=
I`mnkDN0pgqvx(?mmam0gATe zu`(hwFu7A2dWb=UiK_MJ9cYF>d9{6Wr)v~&^rBN_@V7!;Vn5`15_JhQOe&qV>Jyx} zs3?3>D^zzT1=C$Z@O3v>euE3QoB=-K#WxT;yrf&YU?J+$wAAC4f#LYc=47vRyhC{- zA+Q0kWl3adi??G{KVA>JI-lRHw?dU+ElPRG z%X}|!&vFBHUt&9u6m2vh%jX=YXx$>g(%5id@8Y{8cxa8BC&B#g3i2$MLP{)QAB^d0 zL_mraIA($edHPq6-I!5X^9`blGam&fkt}DMCFZB8X`>|wt}^h=Vp#%5q=9jVZ?A68 z`To+7?teYb)z6)ve@CGI|4B5PTw5X^5@5s%6`-f_zk`K4m>60b(*OMV(++!IeemN; zcJ$U4w|wyS&iAbA;iNKU-A-c$>}pQzl$?F|t|H||1|+V|(l9X_6OtJbaoVuW7jhC{ z2rTDgd}I+Lxn6Hb2Sbew%o}cI{Q0LLHOB6j#$}IqczA}dPbbHrHM%31-mIl+wJKH8 zV#x-FucaF=bKomGNJKR()BmUW5aJKCc4*D&z9f;zRC8OH=`#?g=oAH&ku{ zzC@1A%kRVAPd^qX1Qs~L+YDneUvF$cr`pYb^|rOmFrJ?1FVU{o)PmF1ex(udvPhLG z9`^d|LsV9~0qqV)$@pIB1vOx6zE0kK0;hWF79Aj!rum6NgtAdv{U*l}5= zHhm27Fi87;Io2AXlwW*&_G@^zwp9lxg=vF^i}MH`yyF9G42y=wwNo*l!yJybk6`H9 z4Q9huO`>+q9IJuIu_JNQcdm6O;(+aZGol96n}qmp>fncHT$q4O%{F<9lS$B_Hl-DA z?@|9(<}V;Jpqn6qV9+|MMJzSVLu7B9lq6lz_xa@_WIp6tn2Vj3&%|Ux9L=)(t26>! zPxfce0%d_N0uMJ?qQH&W#Gz(dXS_}U`NK)s<@>Xa_^IXAhwHtQS|e`iHJ!)P$$q}a zd-@B_tc%6yc-ge3>&Ne{o}L!oSCk3ptD+RX0}T+eU%*g zkijVR`NLiEGpvgNkdO<2J*Or~;RXhfQraVPeZwPfsG1cx$WVtJ5V^_{!9aD`(#$?sQ)Wbnj zz6vxr3?Nj;;>_Zp(c{y%N6BoPBVQ2n-Ff}yGJt?zbMLSb+U$_m-Fg|tv0HjhH-v!fvV{-RuQ1Dhsx}cb!z6dyw9XrJvW8+cjTj&Q!#kqff+B3txI)B)YC@?P zS+kjZjaZ$2lkn?aljhXLMRZW_?e)z2zAoYNuIN#f*R5f-Dy42d4U35=5f#>gnGBz0 zGEE6bhaiUuGgO@DXc{0f@d{dE0&XRmUm=pi^=Pb>L^GhSk_pbmdrE9DAEh?t^@kSF zH|oCCR<+|HkToZPUCoWA@Ykh43?E#zzjS1GE)bDT)Jqa+JmY;&8{H#f)mFY#Dbty1 z-XJ)LPUChdb#H?@XhL+(__+XpxR%PZS&*?zR!Kv#F4XoFJeQ92dpL67#8(Q`a%~5& zPxe+9A{r$p#H7>39`EB6b%e<~X5nRAd&QP8rcp_|ijJV;@G8)=k%XQ)6IV!i0AJ;- z8tD*rh`Xkz&QWN=ovprwImB8C9~4No2!m+*6Y|K1^m6+YT_(!t;)U#P6`p%GB#0BH zoDbz4&I-O1uiOAc=H+sFHMI)0v{4P;;S`ZLT5mO2#eMIS33lc~hMhR=Wig8?_femn zwfzJkpxfYR5|@Iq?SW$w$73BwtKt%jBy+su=U)js=^8I_k#s zlBUYLZ(KRoMDTu+SNh9v)MDHWnIt&}uQxN?O`ckh)j%|Fpf-7jpMO3#*tD<6(T*=A zuk1VPS50v}5>M4-g@@9xc4yhwomAiVqt!LHzR+3+rA45-%qp&t&=!r-Os3hHi^~r` zW^P^Lm9DzQs(0flC+8{_IV^ZqjyW$Hd2CFXcL=Qeq<44ZACmbnK%#stI+sN^d;dKg zUH-Chdo1RSa;9gDQf%2Rv2e5QHF1C=N$LDoDqoc%#zVG7Kb4&M{c!3bn~?&C=Bach z3)h2Hm!0~Q!)qT)JnFJ>Yd0D5iGr%VR8?DbR`J&H;;IyptfQ*Cl*n0vZAW92^1`3JMY$9u^)R4i*j$ z0TC4$0TBfe4h|U;83hd;0|Nsd=>--hIuRRh zfC3GO00Dr3yaIrtfPkTZJaqz7)Br#rfTjIW;C~$;pujRhLP5j8!T~=}jSK(<0RsaC z2m4WK;HN!+e+Pi0K%f#a3P7UC>q5P zMovLV#lp(Q&cVqg^hQ`jR7_k#QAt@v^{tw^zJZ~Uv5Bdfy@R8Zvx}>npMSuIz@Xre zsOXs3xcG$6iJ4j1Ik|cH1%(xrRn;}Mb@dHjJ37C0b@%l4jg3!CPEF6u&aJMkZ)|RD z@9gfKoSvOuTwYz@-2Ra3hn)XD{t)b$Tqr=fK*7Pmz@dJ~1p?{}Ji$=FA&3|uQ3d3o zbZyaIG5J8F3r1#?w*z}4g<}joyHQw75|&lclOLk}l zC<+(~fDiDXm>EI=`2Y4iYh0d#Ys0bJ+)P;x(ywi*N;G#Z-uR$wb0YD|Yjwlg5TpV3 z;yXWnu(0c6^~rpDDnVIgOXEZ?CcEU8s3TtTAhIlj2wnmih9p63I6R~PapFgzhx8`6 zQWtG{l=h-t$dAmgzPY-ZvcM1-+JPSNi{mSK-=Y(aKxK|<$_9EeU-Ny_CelKZn!JCI z_hXu`ZYn>VgLwx>fh~uq%83V!F)s%qjQ&s0SrRdQQxd~Ba%!JH0l*5#yzzvMo&eT! zz2C|b&(j(#GmS-fQ;pa>Ehz3(a%>+9yIwo)HtgxvxgYSigAn3fs}mIBEz3*P;Z$ z!n?}0j%y-4>`A}6FiV>Um^#i&_~wV%qiWgd?fH(&zNe(hwrxdW1d5W~+rkk9 z82{%yC@Ua4io{PkERif?OZv-7ctU77G#oMl!iqbGejH<#iJL!DPgIlrED6ow$7&KM z*!Iu-fcIHoxm>EM!T@`fOD?vQeA@F=+;Eu|Il;wlgHJP@i)UR}`5W6#%+W_0Q}I)C z{zj4-K_zmym;oIC4<;(N0_W`6WigV(CHBuEnC}>0JpmflBd>7)wLk8d;ey5!pgT8% z31o~qayzd@yd&-I=zJ}_+DzqMS}$I5geN~|Wy7q5*q`_10ouN0NuJ$E z&s6^9NoEmfHc~uEPgpNhz}?LDXj0oFUZer4iMm6JL6pRnhLYVNF{Yh3Zq(cD?~+dd zXud#Bf*BlbMEl180z2_X0tMN1etdKMoG&8f-A@2G4aq3#o*Z{O3u05e&kK}NY!V+J z_;K&EjYG<<*OhDUB$nRGj#^31_Ry{g!0WswGKeYbB?O7A0tg_4C%_)kom<0qxCo5V zlvt~v0DP&HBd544A?8D0MIH3E-PE({JR+y?-l%z%v3PJnauUu8(-gPko>a@q-@AgJ zrz6s>t51Eo$TB4VhDTA|+$p~>8^*;}59NCjil2=e9`Dn8_eF|bo1z(wW$eAeSk;VH z>f80ZS74R)8=l9}wVPMezU(+h^8#g+sp6$guk#i@lcF_mrX*If_(dGy!&&vN6xdIk zsH_|>f2byTfxN4()wdcypkXp!gsGeC<(d$=Ck=4bd?cTsJ(6Vq_J9N7WX+0@{RRQJ zgBKmJ4t_DjfxA`HMDAX)Hy2YTeDXqi$|$Z+bk^D|M84-0CHVUl(6&@p#&rUByz^9q z6C5{&Uc3icD|VALr0ilThxp6MB+j%ZDy<%fhodIT>c3BXw3u z`B4kjz*_U~9M%YppI@CtaEK6N1FqUxKsM}M{N7H{9Tgw6P?}s8?rl-5R*K^QeMATe zHkbI}PDAm%Qv=egPUwR!q=gvX%Z)@0bknv882IYYs@g(e89L?Dyp3+ZYo(;!OFQ645>;z0p6L^gHg z$X_$()%hL$?ZFg7xjIQy&o1g`l3|k5k_FqawrwaFuQgf~wlM=fREI`tqY7PHCri2D z991YAm6viBj>7}Y5w^b2=R86JV-A+Qd$;3a<<@BMv7Vx!R8R%(z`zc~qgyX|AHt0WetvR0;Z0gRTn@SJoPqPu4l*Y3v>_R z75c4#JPAs+ZDuzPpfH319nl-{YZ^ZUy8NF{CN%}6cFc2dr4gg|yqKC~R?HISN zqpRJmb#O6DF_-+NFm@FJ6*IW<>mKfS+IeqL#U8+}R}IehFy2|<&b|I-$HkJ!TLL9` z-WV?KJ*mrbwjfD&EVZ$1mMYaovY#x6qAC#0eAM{9U0%L-?(aE`Sf`%&_toLsO; z(t2QbDL|<;-qK{CXmsGBAVzj(D0zbBWQG8!Vy7al9T`)cH5T;=OuP>~xr{48cG|+t z8ifHyu5%yK9vg`A`S~`#fLWw_RRw-nFHnqnds=sL`y#0ifeg%~_LHpjYK#MjuEsSLbH%pW#T(-j+ z&aXW9-CJZy#MvSAcXCkKqngA14y~v&OJ+>wx796K@R>yB=qTWf`c4m>Aa%*590bnk zLr~Ixy1&><#7}@occmvlshZb0m^y3Ed&%k(o~hWpC%{+6618i$w@1oH*4BDz$QsZa zeF5(TNC!NoL+?8>`mfFNuG<}77PTU~RLpCaG2Ym!cbJrMBLxi~F@#7O5A410MO?B; z#}E8ZeYe`&)x8VQsz66&`Id)rZu>I+QhNH5Z}wAOB?H{oei&;JDj2}6x9yI3&-nxW z`T&6`S6uyytDY{iAooXK6@}J1%>(%|4$TeB4qRNH2qg2&rXu0$>&eUSd+JS75IQEf6;CFoN62N${77{vJk3>wtk`zwSR%7Vi-t5{Ti-19!D3`l6(48ZjRQ78%W4G~~MzLwsUaK=# znJ+mNfzF>dC^j~%cbtj=9&p0;1W3anFGcITFtkmsuIw}`)dw@OKf=^fH8SBwH@>d) z6@lJra05_eW;8VVb}i=BC%$%3eVHBWo8Q~k%e&=G`epdQxaG#7XKGdUzL~QVYyrRY z2>`P03kQ1^rqPMd<{nqeb>+P-LOKRx5Px-y=B`}nLVlSu|YLQbaD9(p%Q=O8-&FX~#h7T1-(rcG|Rc(Bmd$Taa57#%m$t9u+ zf*~WmYt;EFZw*SHA-K0ZP?<*X}V<+cTdWYcwhfyH?myqL`R>6Pv9a5jLn` z8n2TR_b$HouebRcW&6DG@^&w8WzsBx!8_YcEm1q*B}Y;CVY7AsMZhis_X+T^2`c@1 z?={P`!$qqGC;Zf1%1Gy?#GyhqvW*MRC+H2M`q*pi6)l;U1%}5D1@(z*qUNzireH;N z2=&1m#u@88<=SD&4(mzI+k7qYHGG>{a$pV~WYYp;7FGRNO-a-osB_S#GCiY$`Mnz} zAX6nkVKHP?#w;!dc{N^MV{VOUHLiIEf-^ku^95*TdUMpbU|h>kW`GF=bdE*Lf1W{# zNjtK=65T$MiC($#+juvaDPq%pveg^vi)Gu0$6u0p_Q*?9H+&TSUjNGaX0j0Y;Di9y zj(8ETh2$nmF5tq*2U;5K&SdCFMfB?v2x31lXhwbtgv!UjxhFr)lBzM!`JytFE{)DG zOa<<&dj`*r#gL)tG4(Q#d)ii6fA})y3E++|zq{k^!`E#Lj68%nt#Mt<*V*PPOH_rM|2lLI2 z=PD5eTwdUb=gcV_O4n;?1#LpdycVbwNbaqQt-w$;NjYx_>2+a_;urbB`=q-{L zqP}5Fq$4C_I;$n+&N+kjq~AO2UG{cXFqHAtH%@Th!Jl)da$XjL_95_z)z;S3vX$kN z>KZvwM~QE?SY=-n!%}ly2db%0-PGPx?C8e6a9`et-|($J!ZOE64L1wdO_wYoUy9VN zLurWUuL6i@aFTyYGSA4Y&mzUvDoRn1k?5Vt%hu9bGCh&@FnmaHm|eEq3U;#NzX^mQ zhB_&Vkyp5I#u8C#_yg016#3_wT|+ojrXC0 zU~;V!U*@!gq#p<32Z&ys`8P&`Ati${N4En)?bRLR--_oR#)hpWs#tA9FR`3x+G~oE z`{pRC!hWg^S@8=ch?No5PGJIR>xaL%_F0F1oW#{ZI>d|Zj_W$6s#y^yr*dQ9Jn&_Z zRorz@l_-`iCcSDs<4nOxq2jCeiWC)YYHArDGyhJo|NVmzBod3bH%xmESblpK6SHc5 zX1zvZg9=xasaj(IhK^h%PC$0tmT5XtXsG&yM`W`8Nr|@Chwp4i_av!A3ME=% zE#M{gZGEW&q9xQ~U8vVNdZd)}0h&bx*Zn%RC*U=bD~%uXi-9_eFsBt(0>?yoR|oFx zG9cTs;z7-U2Ib`N2-T2i|rV74$63+?X+Ojj#{;h#5+$b-tbDYPWJOY0TODq@UR;w^q4UCv9SBh zwbA`Fn>0StTOXw8qXbmfQPlNv&WEDf`=w@uY-|RymgZ$ly3Sorv=(V<&F$8ry;Y}u zn4{CLF?}N_v|Hy3wSMbZg3@HWPDvZLH@~_cMl-VEnixe%K#c(*;md0Qiiku$&qaHj z+cAXp1TZrzrShvBtY65eK$HQHY#4L)UKBZ}A<-NX1?aX;SZt|4Y6Mwnyk97I-8+2c z(gmRDM3i^AG|!v z3oHH-tvw{*pKv=!T0XK*E$^ofT_f0YC0Y=mgH65d!iJM49HimQ?}rwC0?LztuK%G* zj=655F?=J*R;hU-mv0xE}@H7q4O?K81sZaOZ4G3kBYQQeI7!-rfQnZfA&j zN5d)p54(s)B$B!sPP7KeBcS@eNmVX4vC9sLh_3qnpkbA20UG6Hfb0eY==fS)BTyUc=(x&s@_$!$iOK-Dm zR)>Ng-IJ3vIBUN4uOcKq!Lc-dh%(>cq+9;vNpN-`3#^&{Ze~045ElLg_?H^s33N{X zS$7V)dKQL?4z3o4_CIP5en1@2mjR1^wK>??9tc$o(JsG97V7$< z;mv6j{UD!2X8hZI0~WBS6%f=0*2Qcn$Z&T*ef}xiMO)LVcV)0}t~JX!+_ti=_C@Hb z-$!yyl58Ne?Ck}EEJZWwcoNih4la!37cA@Hvo)^W$74x+w()}3q9G@OQ`^}KeF-zG z+Vc80gG|N1G~HObY?Y=a>kA&JXgv8V{@VQDSZDZSGEgx^ep5^*Q$y$fQp`|AY3q3g z_-3RTFJuRugDT-T9NQ4g4yRpR{-#CN;BwX-xXfg(n;&aA(j$0o%r`yVS0-i;9B(@= zk>%Z0&%R0bVsq@qI#~{Su`aiM;piYqM(ui?e*+T1XT|HK9%xp&dSPtvW~B_3^+*9$ zSw4Ng4Yuh71XuSpL9rNmSB;!}6KXl@H%m1-IO?i(d#`)3*5!jLe{1baOwB~GS6Go^ z+)i98!L;xFY2WZ?_AX9Gg|?k1EllEunKdju+6pEycCZ^PgpqKP+@*wf8>7^A3Vkov z8&M$;*c8Nxcn^L7+Sqyg_RP@Lx%=}@w3mXHyA&(EtF7AXbp#y2VSGP4#`JoZI*WR{ z21TvNp!!Jg$Tfj{Q6z^Sa|L;T0+vEuk1MX5Q0rYiMAlZXw}ZlGJ>_2x#CPFxu{q#UdP*!g(f}{9PS=c$U!;~^(2?oJ>(MJb zsdDXdt8vgjnB>pxgsjJPO6H@?uE> ztj^5>+L+j!$hXX?Bw6y!=kjI;mkj9HqS;LQVZp37?pxMROjzbsa%w>={i7IRMZjGN z>-z#|^vHln4$9n#~9R-iZp7-rkTEjlP-KPwH*lbn~ zEQsqK^^w?mjuA?71JeDH4Zp`C#^C_37%K#L39^k&w3+ULG$Dlbvk0zT0aa+kJ#6x|5qU$-mB`^6p>+7agdkFhKiN4>m6u8q#_G;qO%RGMdc@wiT6m%6fta+ZHgV7YK=L=JO?kDD`Kl?CvI0=odI&Ea_GrR6 zgPiW|v9YlfZ5)zTR+YP(M{PjS>iOnk7MAPq3RY?2S|+pPMH%oGg^slY#}x zC?A`oGr$P;1s_4t^2CVQa-99Qd-BZ-lM?tt?iS3CCFK;m79y_?jfIA(8Q$J4x8Bx! z5-D6YdOfVL&K<3mNGuAXICQw|p(iQ0jx>!vlwBg0>yb7UoNeb+KTO9TDn*E zo)~bf<*CgNsnQ!cZ}$A^zd=B0fktxw9$GFBU|kgd=)vLt7@qvno*%C?gsiO`46Ph= zlw55L?X`Y9Tym0s2AEtsWB_+(0c*eq5@>1u+pz`gXLRfgE$r!knj1d9P+ya{stx$@ zABjo{f4d9-zyX@_{TSl@jM?+2lvBTwO+BZ*q+^AG2a-mB|CHcQG%Vm4`UmZgqWl;( z0|nA`FtxV&AR{{5!zWAL9MQJx}ZU&&l~X|AhQ2Rq8({m%RKZ zDDNZ26zb zf208WOBMak+R+14|9^n~kIMg_$wP$yg#0T-;@{nlKi}vHqJKhW{@*C`+^c^={*}t_ zd6}Ol#QUWmE5yH%{~fpVx2N#8=%s&IgU@rp{UY;`{zm?{+Wq!q|DhJoOZq(H(k~t* z)&IcznSbdy?|CYeU%VB%zvum|r{}omvHXAGtXTdY_fw&ssR}G+|P#iIqtcm+b>+N&fnvH zc1F)}|G9OHF#HSLZ|%V!mHo^8;yL-b6T`29#u@!Ve(uun2jM>(Z2ltbTmDD$&F95< zzSj5);^g;7G5)mj`26zc%U!=NXA1b26n|d)dJcHLr1T4b^x+S{pB9*&U;gK1j9(W6 x0CR!A-GhHGYCOOE&r{3aFAoU$?ec$3H02~AfbrJ=08-$WG;r`c9QNb4{|7;YEG7T| literal 0 HcmV?d00001 diff --git a/P5/Source/Guidelines/en/ST-Infrastructure.xml b/P5/Source/Guidelines/en/ST-Infrastructure.xml index b141ec6789..5ddc207958 100644 --- a/P5/Source/Guidelines/en/ST-Infrastructure.xml +++ b/P5/Source/Guidelines/en/ST-Infrastructure.xml @@ -871,6 +871,7 @@ one, or vice versa, should be done with care.

+ @@ -1141,6 +1142,7 @@ one, or vice versa, should be done with care.

+ diff --git a/P5/Source/Specs/ab.xml b/P5/Source/Specs/ab.xml index c4fb583143..b1b68a70f1 100644 --- a/P5/Source/Specs/ab.xml +++ b/P5/Source/Specs/ab.xml @@ -23,6 +23,7 @@ + diff --git a/P5/Source/Specs/abbr.xml b/P5/Source/Specs/abbr.xml index e6cd6f0f6e..a6456fd71b 100644 --- a/P5/Source/Specs/abbr.xml +++ b/P5/Source/Specs/abbr.xml @@ -23,6 +23,7 @@ + diff --git a/P5/Source/Specs/add.xml b/P5/Source/Specs/add.xml index 8f55105eed..49002cf71f 100644 --- a/P5/Source/Specs/add.xml +++ b/P5/Source/Specs/add.xml @@ -36,6 +36,7 @@ + diff --git a/P5/Source/Specs/addName.xml b/P5/Source/Specs/addName.xml index ec28e8c578..d133c0309b 100644 --- a/P5/Source/Specs/addName.xml +++ b/P5/Source/Specs/addName.xml @@ -25,6 +25,7 @@ + diff --git a/P5/Source/Specs/address.xml b/P5/Source/Specs/address.xml index 3fc9b7f3f7..23a6b13b4b 100644 --- a/P5/Source/Specs/address.xml +++ b/P5/Source/Specs/address.xml @@ -20,6 +20,7 @@ + diff --git a/P5/Source/Specs/affiliation.xml b/P5/Source/Specs/affiliation.xml index 3932f4df14..e67a8c494a 100644 --- a/P5/Source/Specs/affiliation.xml +++ b/P5/Source/Specs/affiliation.xml @@ -25,6 +25,7 @@ + diff --git a/P5/Source/Specs/alt.xml b/P5/Source/Specs/alt.xml index 02ba2c3b87..9a4e607e40 100644 --- a/P5/Source/Specs/alt.xml +++ b/P5/Source/Specs/alt.xml @@ -24,6 +24,7 @@ + diff --git a/P5/Source/Specs/altGrp.xml b/P5/Source/Specs/altGrp.xml index df42c046d2..c34ed13d32 100644 --- a/P5/Source/Specs/altGrp.xml +++ b/P5/Source/Specs/altGrp.xml @@ -23,6 +23,7 @@ + diff --git a/P5/Source/Specs/anchor.xml b/P5/Source/Specs/anchor.xml index bd66b33b79..3637ec981a 100644 --- a/P5/Source/Specs/anchor.xml +++ b/P5/Source/Specs/anchor.xml @@ -22,6 +22,7 @@ + diff --git a/P5/Source/Specs/argument.xml b/P5/Source/Specs/argument.xml index 13b4adb462..32f5ab4d0b 100644 --- a/P5/Source/Specs/argument.xml +++ b/P5/Source/Specs/argument.xml @@ -20,6 +20,7 @@ + diff --git a/P5/Source/Specs/att.cmc.xml b/P5/Source/Specs/att.cmc.xml new file mode 100644 index 0000000000..0784fad43d --- /dev/null +++ b/P5/Source/Specs/att.cmc.xml @@ -0,0 +1,145 @@ + + + + + computer mediated communication + provides attributes + categorizing how the element content was created in a CMC + environment. + + + generated by + categorizes + how the content of an element was generated in a CMC + environment. + + + + + + + + The @generatedBy attribute is for use within a <post> element. + + + + + + + + the content was + naturally typed or spoken by a human user + + + the content was + generated after a human user activated a template for its + insertion + + + the content was + generated by the system, i.e. the CMC environment + + + the content was + generated by a bot, i.e. a non-human agent, typically external + to the CMC environment. + + + the content of + the respective element was generated by an unknown or + unspecified process. + + + + +

automatic system message in chat: user moves on to another + chatroom

+ + +

+ McMike geht + in einen anderen Raum: Kreuzfahrt +

+ + + + + +

automatic system message in chat: user enters a chatroom

+ + +

+ c_bo betritt + den Raum.

+ + + + + +

automatic system message in chat: user changes his font color

+ + +

+ c_bo hat die + Farbe gewechselt. +

+ + + + + +

An automatic signature of user including an automatic timestamp + (Wikipedia discussion, anonymized). The specification of + generatedBy at the inner element signed is + meant to override the specification at the outer element + post. This is generally possible when the outer + generatedBy value is "human".

+ + +

Kurze Nachfrage: Die Hieros für den Goldnamen stammen + auch von Beckerath gem. Literatur ? Grüße --

+ + + + + +

Usenet news message: a client-generated line that introduces a + quotation from a previous message (similar to email):

+ + + Am 03.04.2015 um + 09:46 schrieb [_NAME_]: + + + + + + + + +

Wikipedia talk page, user signature

+ + + + + + + + + + + diff --git a/P5/Source/Specs/bibl.xml b/P5/Source/Specs/bibl.xml index 89eb998995..f1dc7682d6 100644 --- a/P5/Source/Specs/bibl.xml +++ b/P5/Source/Specs/bibl.xml @@ -33,6 +33,7 @@ + diff --git a/P5/Source/Specs/biblFull.xml b/P5/Source/Specs/biblFull.xml index de359d2876..9f7fb863d5 100644 --- a/P5/Source/Specs/biblFull.xml +++ b/P5/Source/Specs/biblFull.xml @@ -27,6 +27,7 @@ + diff --git a/P5/Source/Specs/biblStruct.xml b/P5/Source/Specs/biblStruct.xml index 36ec4f8b7a..ce4aef2a32 100644 --- a/P5/Source/Specs/biblStruct.xml +++ b/P5/Source/Specs/biblStruct.xml @@ -28,6 +28,7 @@ + diff --git a/P5/Source/Specs/binaryObject.xml b/P5/Source/Specs/binaryObject.xml index 88ce086b59..ebf576bfa5 100644 --- a/P5/Source/Specs/binaryObject.xml +++ b/P5/Source/Specs/binaryObject.xml @@ -20,6 +20,7 @@ + diff --git a/P5/Source/Specs/bloc.xml b/P5/Source/Specs/bloc.xml index 81f5354fee..b3af6e85b7 100644 --- a/P5/Source/Specs/bloc.xml +++ b/P5/Source/Specs/bloc.xml @@ -20,6 +20,7 @@ + diff --git a/P5/Source/Specs/byline.xml b/P5/Source/Specs/byline.xml index 7a3caf9f0e..35c92ab58f 100644 --- a/P5/Source/Specs/byline.xml +++ b/P5/Source/Specs/byline.xml @@ -22,6 +22,7 @@ on its title page or at the head or end of the work. + diff --git a/P5/Source/Specs/c.xml b/P5/Source/Specs/c.xml index 5151bf6108..eb74afc88c 100644 --- a/P5/Source/Specs/c.xml +++ b/P5/Source/Specs/c.xml @@ -23,6 +23,7 @@ + diff --git a/P5/Source/Specs/cb.xml b/P5/Source/Specs/cb.xml index ad01b8ce5c..81a1d50328 100644 --- a/P5/Source/Specs/cb.xml +++ b/P5/Source/Specs/cb.xml @@ -25,6 +25,7 @@ + diff --git a/P5/Source/Specs/choice.xml b/P5/Source/Specs/choice.xml index cb0e7e28e9..697fd79571 100644 --- a/P5/Source/Specs/choice.xml +++ b/P5/Source/Specs/choice.xml @@ -19,6 +19,7 @@ + diff --git a/P5/Source/Specs/cit.xml b/P5/Source/Specs/cit.xml index d8d6df1cfc..9d7fa9519b 100644 --- a/P5/Source/Specs/cit.xml +++ b/P5/Source/Specs/cit.xml @@ -33,6 +33,7 @@ + diff --git a/P5/Source/Specs/cl.xml b/P5/Source/Specs/cl.xml index c4d3dc80a6..c269c36af3 100644 --- a/P5/Source/Specs/cl.xml +++ b/P5/Source/Specs/cl.xml @@ -22,6 +22,7 @@ + diff --git a/P5/Source/Specs/climate.xml b/P5/Source/Specs/climate.xml index 28422e2901..03c67acf3e 100644 --- a/P5/Source/Specs/climate.xml +++ b/P5/Source/Specs/climate.xml @@ -18,6 +18,7 @@ + diff --git a/P5/Source/Specs/closer.xml b/P5/Source/Specs/closer.xml index 7e8698cdc3..db22a1f970 100644 --- a/P5/Source/Specs/closer.xml +++ b/P5/Source/Specs/closer.xml @@ -24,6 +24,7 @@ aparecen en la última sección al final de una división, especialmente en una + diff --git a/P5/Source/Specs/corr.xml b/P5/Source/Specs/corr.xml index 42e4804492..9cd0e01455 100644 --- a/P5/Source/Specs/corr.xml +++ b/P5/Source/Specs/corr.xml @@ -23,6 +23,7 @@ + diff --git a/P5/Source/Specs/country.xml b/P5/Source/Specs/country.xml index 54940fbeee..a5d82b5797 100644 --- a/P5/Source/Specs/country.xml +++ b/P5/Source/Specs/country.xml @@ -25,6 +25,7 @@ + diff --git a/P5/Source/Specs/date.xml b/P5/Source/Specs/date.xml index 709566274b..0e3b905fcb 100644 --- a/P5/Source/Specs/date.xml +++ b/P5/Source/Specs/date.xml @@ -24,6 +24,7 @@ + diff --git a/P5/Source/Specs/dateline.xml b/P5/Source/Specs/dateline.xml index 40f6626e0e..18a60f4e8d 100644 --- a/P5/Source/Specs/dateline.xml +++ b/P5/Source/Specs/dateline.xml @@ -26,6 +26,7 @@ + + diff --git a/P5/Source/Specs/listEvent.xml b/P5/Source/Specs/listEvent.xml index 9b82a6b07d..5bda7a3425 100644 --- a/P5/Source/Specs/listEvent.xml +++ b/P5/Source/Specs/listEvent.xml @@ -15,6 +15,7 @@ + diff --git a/P5/Source/Specs/listNym.xml b/P5/Source/Specs/listNym.xml index d4d5b53c20..da5d7390d5 100644 --- a/P5/Source/Specs/listNym.xml +++ b/P5/Source/Specs/listNym.xml @@ -20,6 +20,7 @@ + diff --git a/P5/Source/Specs/listObject.xml b/P5/Source/Specs/listObject.xml index 3fba9dd5e0..6cb154da51 100644 --- a/P5/Source/Specs/listObject.xml +++ b/P5/Source/Specs/listObject.xml @@ -16,6 +16,7 @@ + diff --git a/P5/Source/Specs/listOrg.xml b/P5/Source/Specs/listOrg.xml index 35d0dc7d76..180007e8cc 100644 --- a/P5/Source/Specs/listOrg.xml +++ b/P5/Source/Specs/listOrg.xml @@ -24,6 +24,7 @@ + diff --git a/P5/Source/Specs/listPerson.xml b/P5/Source/Specs/listPerson.xml index fa5d589253..6f8933ee6e 100644 --- a/P5/Source/Specs/listPerson.xml +++ b/P5/Source/Specs/listPerson.xml @@ -33,6 +33,7 @@ + diff --git a/P5/Source/Specs/listPlace.xml b/P5/Source/Specs/listPlace.xml index 67e5dca76a..aff7a1d57a 100644 --- a/P5/Source/Specs/listPlace.xml +++ b/P5/Source/Specs/listPlace.xml @@ -25,6 +25,7 @@ + diff --git a/P5/Source/Specs/listRelation.xml b/P5/Source/Specs/listRelation.xml index d1510dbe9f..3c1a36d775 100644 --- a/P5/Source/Specs/listRelation.xml +++ b/P5/Source/Specs/listRelation.xml @@ -22,6 +22,7 @@ + diff --git a/P5/Source/Specs/location.xml b/P5/Source/Specs/location.xml index 10d9caaad7..8a97bc6322 100644 --- a/P5/Source/Specs/location.xml +++ b/P5/Source/Specs/location.xml @@ -19,6 +19,7 @@ + diff --git a/P5/Source/Specs/m.xml b/P5/Source/Specs/m.xml index acf7cf9e38..89b603d836 100644 --- a/P5/Source/Specs/m.xml +++ b/P5/Source/Specs/m.xml @@ -21,6 +21,7 @@ + diff --git a/P5/Source/Specs/macro.specialPara.cmc.xml b/P5/Source/Specs/macro.specialPara.cmc.xml new file mode 100644 index 0000000000..25436043f2 --- /dev/null +++ b/P5/Source/Specs/macro.specialPara.cmc.xml @@ -0,0 +1,29 @@ + + + + + 'special' + paragraph content with added CMC element(s) + defines the + content model of the quote element, whose content + is just like others (such as notes or list items) which + either contain a series of component-level elements or else + have the same structure as a paragraph, containing a series + of phrase-level and inter-level elements, but also contains + element(s) for transcription of CMC. + + + + + + + + + + + + \ No newline at end of file diff --git a/P5/Source/Specs/measure.xml b/P5/Source/Specs/measure.xml index 78f8d26b9a..df8cf1e651 100644 --- a/P5/Source/Specs/measure.xml +++ b/P5/Source/Specs/measure.xml @@ -24,6 +24,7 @@ + diff --git a/P5/Source/Specs/measureGrp.xml b/P5/Source/Specs/measureGrp.xml index 764e9feb13..f88de771e7 100644 --- a/P5/Source/Specs/measureGrp.xml +++ b/P5/Source/Specs/measureGrp.xml @@ -24,6 +24,7 @@ + diff --git a/P5/Source/Specs/media.xml b/P5/Source/Specs/media.xml index 79b94f79a9..af44d3a9a2 100644 --- a/P5/Source/Specs/media.xml +++ b/P5/Source/Specs/media.xml @@ -13,6 +13,7 @@ + diff --git a/P5/Source/Specs/meeting.xml b/P5/Source/Specs/meeting.xml index 882c6cf57e..c398fb4cdf 100644 --- a/P5/Source/Specs/meeting.xml +++ b/P5/Source/Specs/meeting.xml @@ -22,6 +22,7 @@ + diff --git a/P5/Source/Specs/mentioned.xml b/P5/Source/Specs/mentioned.xml index 102bff58cb..9594dc4b47 100644 --- a/P5/Source/Specs/mentioned.xml +++ b/P5/Source/Specs/mentioned.xml @@ -15,6 +15,7 @@ + diff --git a/P5/Source/Specs/milestone.xml b/P5/Source/Specs/milestone.xml index 1a70a9ee47..00b317d738 100644 --- a/P5/Source/Specs/milestone.xml +++ b/P5/Source/Specs/milestone.xml @@ -34,6 +34,7 @@ + + + + includes the CMC-specific element post and + makes it available on the divPart level. This allows for + using (and combining) occurrences of post, + u, incident, and kinesic in one + and the same div in order to be able to represent + the combined use of written and spoken posts, utterances, + and nonverbal acts on the GUI of multimodal CMC + environments. + + + + diff --git a/P5/Source/Specs/name.xml b/P5/Source/Specs/name.xml index e9dd5e286a..c9f8567c19 100644 --- a/P5/Source/Specs/name.xml +++ b/P5/Source/Specs/name.xml @@ -24,6 +24,7 @@ + diff --git a/P5/Source/Specs/nameLink.xml b/P5/Source/Specs/nameLink.xml index 8e1ddc0eba..75b0c2d56f 100644 --- a/P5/Source/Specs/nameLink.xml +++ b/P5/Source/Specs/nameLink.xml @@ -21,6 +21,7 @@ + diff --git a/P5/Source/Specs/notatedMusic.xml b/P5/Source/Specs/notatedMusic.xml index a3f3851d1a..c73e464de4 100644 --- a/P5/Source/Specs/notatedMusic.xml +++ b/P5/Source/Specs/notatedMusic.xml @@ -8,6 +8,7 @@ + diff --git a/P5/Source/Specs/note.xml b/P5/Source/Specs/note.xml index a880eafaae..344a53a8f4 100644 --- a/P5/Source/Specs/note.xml +++ b/P5/Source/Specs/note.xml @@ -24,6 +24,7 @@ + diff --git a/P5/Source/Specs/noteGrp.xml b/P5/Source/Specs/noteGrp.xml index 8aa224f178..bf93865b72 100644 --- a/P5/Source/Specs/noteGrp.xml +++ b/P5/Source/Specs/noteGrp.xml @@ -14,6 +14,7 @@ + diff --git a/P5/Source/Specs/num.xml b/P5/Source/Specs/num.xml index 06c2701efe..de0480b0ec 100644 --- a/P5/Source/Specs/num.xml +++ b/P5/Source/Specs/num.xml @@ -22,6 +22,7 @@ + diff --git a/P5/Source/Specs/objectName.xml b/P5/Source/Specs/objectName.xml index b81d46a684..6ca1d33a6e 100644 --- a/P5/Source/Specs/objectName.xml +++ b/P5/Source/Specs/objectName.xml @@ -12,6 +12,7 @@ + diff --git a/P5/Source/Specs/offset.xml b/P5/Source/Specs/offset.xml index 568ae446ed..430ec7fe63 100644 --- a/P5/Source/Specs/offset.xml +++ b/P5/Source/Specs/offset.xml @@ -21,7 +21,8 @@ - + + diff --git a/P5/Source/Specs/opener.xml b/P5/Source/Specs/opener.xml index ff5e5039da..0e49ba6bbd 100644 --- a/P5/Source/Specs/opener.xml +++ b/P5/Source/Specs/opener.xml @@ -26,6 +26,7 @@ + diff --git a/P5/Source/Specs/orgName.xml b/P5/Source/Specs/orgName.xml index 53fdb586d7..7c8016e5be 100644 --- a/P5/Source/Specs/orgName.xml +++ b/P5/Source/Specs/orgName.xml @@ -21,6 +21,7 @@ + diff --git a/P5/Source/Specs/orig.xml b/P5/Source/Specs/orig.xml index d418ce08bd..ed3baeac32 100644 --- a/P5/Source/Specs/orig.xml +++ b/P5/Source/Specs/orig.xml @@ -25,6 +25,7 @@ + + + + a written (or spoken) contribution to an ongoing + CMC interaction which has been composed (or recorded) by its author in its entirety as part + of a private activity, and has been transmitted through the internet and is made available + on the monitor or screen of the other parties en bloc. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + written or spoken mode + + + + + + for stretches of text and/or multimodal elements + + + for audio posts + + + +

This attribute is intended to convey information about the CMC environment in + which the post was created, as opposed to the MIME type of the content conveyed, + which is indicated by the elements contained within the post.

+ + + + indicates to which previous post the + current post replies or refers to. This attribute should be used to encode + "technical" reply information, i.e. which is due to a formal reply action (such as + activating a "reply" button in the client software) and which is also formally + represented in the source, e.g. in the "references" field of a Usenet message header + or in the subject line of a forum post. It should rather not be used for inferred, + or interpreted reply relations such as based on linguistic discourse markers, nor + for the indentation relations in Wiki talk pages. + + + + + + + marks the level of indentation of the + current post in a thread-like structure (as defined by its author and in relation to + the standard level of indentation which should be encoded as indentLevel="0"). + Basically used for Wiki talk pages, but may and should also be used for genres such + as webblog comments when the source was HTML. + + + + + + + + +

standard user postings in chat

+ + +

oh ja, in die Wärme...

+ + +

nein, hast du nicht !!

+ + + + +

chat message-type "system": user enters a chatroom, "system" defined in listPerson

+ + + + system + + + + + +

+ Interseb betritt den Raum.

+ + + + +

action message in chat

+ + +

+ McMike hechtet zum Steuer

+ + + + +

chat messages incl. interaction words (types: inflective and acronym) and an interaction + phrase

+ + +

+ *schwank* + + *seekrank* +

+ + + +

+ *lol* [...]

+ + + +

+ *McMike einen fallschirm umbind* +

+ + + + +

user posting incl. an emoticon

+ + +

naja, der war gestrandet :( +

+ + + + +

Twitter: Tweet containing an addressing term and a hashtag expression

+ + +

+ + @textarchiv Erfurter + Europäische Welt- und Staats-Geschichte: 20 Ausgaben von 1744 aus dem MKHZ + bereits in DTAQ + http://www.deutschestextarchiv.de/dtaq/about + #dtaclarin14 +

+ + + + +

example from Wikipedia discussion

+ + +

Wie du siehst hab ich die Lemma geändert, danke für den Hinweis, ich war nämlich + selbst auch etwas unsicher bei der ganzen Sache und bin jetzt damit auch viel + glücklicher!--

+ + + + + + +

Blog comment: Die Anthropodizee-Frage. Wer den Himmel leerräumt, schafft die Menschheit + ab. by Volker Birk. + https://scilogs.spektrum.de/natur-des-glaubens/die-anthropodizee-frage-wer-himmel/#comment-31899

+ + + +

“Wenn Sie diesen Gruppen also “mangelnde Bildung“ attestieren wollen, so + verwenden Sie bereits einen bestimmten, kulturgebundenen Bildungsbegriff.”

+

Ich hoffe doch, wir können beim Bildungsbegriff der Aufklärung bleiben. Wer das + nicht möchte, hat die Wissenschaft verlassen.

 + + + +

Even though in some CMC genres (e.g., WhatsApp), the other parties are informed by an + automated alert about the fact that another party is currently composing a new post, + they cannot track the process of verbalization, i.e. how the written utterance emerges + in the entry form on the user interface of its author. It is not until the author + performs a ‘posting’ action (e.g., by hitting the ‘enter’ key or by activating a ‘send’ + button with the mouse) that the result of the composition process — the post — is made + available for the other parties. From the perspective of its addressees/readers, a post + is a stretch of text that has been composed in advance. Different from spoken utterances + but similar to edited text, (1) the reader of a post does not have access to the + verbalization process and (2) the mental processing of a post is not possible until the + process of verbalization (the composition) has been finished and the posting action has + been performed by the author. Posts occur in a broad range of written CMC genres: as + user ‘messages’ in chats and WhatsApp dialogues, as SMS messages, as tweets in Twitter + timelines, as individual comments following a status update on Facebook pages, as posts + in forum threads, as contributions on Wikipedia talk pages or in the comments section of + a weblog. [Element adopted from the DeRiK schema. + Aspects of the model adopted from the CoMeRe Schema]. The + post element is a member of the model class model.common (via model.CMC). + This allows for using (and combining) occurrences of post, u, + incident, and kinesicin one and the same div in order to + be able to represent the combined use of written and spoken utterances and nonverbal + acts on the GUI of multimodal CMC environments.

+

The use of the modality attribute is + recommended, but not required. Its value is either + written or spoken. Because spoken + language differs fundamentally from written language, when + the value is spoken projects may wish to limit + the content of the post to character data and + only those elements available in the u element, + thus avoiding elements like p or head + that are used for the encoding of written text.

+ + + + + + diff --git a/P5/Source/Specs/postscript.xml b/P5/Source/Specs/postscript.xml index 5ff28a29a5..ee1fc613e3 100644 --- a/P5/Source/Specs/postscript.xml +++ b/P5/Source/Specs/postscript.xml @@ -14,6 +14,7 @@ lettre. + diff --git a/P5/Source/Specs/ptr.xml b/P5/Source/Specs/ptr.xml index e6b25a802b..38ff888b62 100644 --- a/P5/Source/Specs/ptr.xml +++ b/P5/Source/Specs/ptr.xml @@ -24,6 +24,7 @@ + diff --git a/P5/Source/Specs/q.xml b/P5/Source/Specs/q.xml index 5e930fc498..2298158d02 100644 --- a/P5/Source/Specs/q.xml +++ b/P5/Source/Specs/q.xml @@ -43,6 +43,7 @@ + diff --git a/P5/Source/Specs/quote.xml b/P5/Source/Specs/quote.xml index 4efc5359d8..5ff8e4c031 100644 --- a/P5/Source/Specs/quote.xml +++ b/P5/Source/Specs/quote.xml @@ -26,6 +26,7 @@ + diff --git a/P5/Source/Specs/ref.xml b/P5/Source/Specs/ref.xml index 124bb948c3..24bde143f9 100644 --- a/P5/Source/Specs/ref.xml +++ b/P5/Source/Specs/ref.xml @@ -26,6 +26,7 @@ + diff --git a/P5/Source/Specs/reg.xml b/P5/Source/Specs/reg.xml index d690ed37f9..b1018de842 100644 --- a/P5/Source/Specs/reg.xml +++ b/P5/Source/Specs/reg.xml @@ -27,6 +27,7 @@ + + - @@ -41,9 +42,9 @@ - - - + + + diff --git a/P5/p5odds.odd b/P5/p5odds.odd index 60885698a4..b448cf55ac 100644 --- a/P5/p5odds.odd +++ b/P5/p5odds.odd @@ -627,10 +627,12 @@ $Id$ + + diff --git a/P5/spec_lists.json b/P5/spec_lists.json index feacc562e9..8922cf27a8 100644 --- a/P5/spec_lists.json +++ b/P5/spec_lists.json @@ -1 +1 @@ -{"elements":[{"id":"teiHeader","URL":"teiHeader.xml","de":{"out-of-date":true,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"fileDesc","URL":"fileDesc.xml","de":{"out-of-date":true,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"titleStmt","URL":"titleStmt.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"sponsor","URL":"sponsor.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"funder","URL":"funder.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"principal","URL":"principal.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"editionStmt","URL":"editionStmt.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"edition","URL":"edition.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"extent","URL":"extent.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"publicationStmt","URL":"publicationStmt.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"distributor","URL":"distributor.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"authority","URL":"authority.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"idno","URL":"idno.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"availability","URL":"availability.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"licence","URL":"licence.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"seriesStmt","URL":"seriesStmt.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"notesStmt","URL":"notesStmt.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"sourceDesc","URL":"sourceDesc.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"biblFull","URL":"biblFull.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"encodingDesc","URL":"encodingDesc.xml","de":{"out-of-date":true,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"schemaRef","URL":"schemaRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"projectDesc","URL":"projectDesc.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"samplingDecl","URL":"samplingDecl.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"editorialDecl","URL":"editorialDecl.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"correction","URL":"correction.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"normalization","URL":"normalization.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"quotation","URL":"quotation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"hyphenation","URL":"hyphenation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"segmentation","URL":"segmentation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"stdVals","URL":"stdVals.xml","de":{"out-of-date":true,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"interpretation","URL":"interpretation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"punctuation","URL":"punctuation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"tagsDecl","URL":"tagsDecl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"tagUsage","URL":"tagUsage.xml","de":{"out-of-date":true,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"namespace","URL":"namespace.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"rendition","URL":"rendition.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"styleDefDecl","URL":"styleDefDecl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"refsDecl","URL":"refsDecl.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"citeStructure","URL":"citeStructure.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"citeData","URL":"citeData.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"cRefPattern","URL":"cRefPattern.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"prefixDef","URL":"prefixDef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listPrefixDef","URL":"listPrefixDef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"refState","URL":"refState.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"classDecl","URL":"classDecl.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"taxonomy","URL":"taxonomy.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"category","URL":"category.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"catDesc","URL":"catDesc.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"geoDecl","URL":"geoDecl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"unitDecl","URL":"unitDecl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"unitDef","URL":"unitDef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"conversion","URL":"conversion.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"appInfo","URL":"appInfo.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"application","URL":"application.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"profileDesc","URL":"profileDesc.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"handNote","URL":"handNote.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"abstract","URL":"abstract.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"creation","URL":"creation.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"langUsage","URL":"langUsage.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"language","URL":"language.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"textClass","URL":"textClass.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"keywords","URL":"keywords.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"classCode","URL":"classCode.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"catRef","URL":"catRef.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"calendarDesc","URL":"calendarDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"calendar","URL":"calendar.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"correspDesc","URL":"correspDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"correspAction","URL":"correspAction.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"correspContext","URL":"correspContext.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"xenoData","URL":"xenoData.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"revisionDesc","URL":"revisionDesc.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"change","URL":"change.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"p","URL":"p.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"foreign","URL":"foreign.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"emph","URL":"emph.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"hi","URL":"hi.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"distinct","URL":"distinct.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"said","URL":"said.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"quote","URL":"quote.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"q","URL":"q.xml","de":{"out-of-date":true,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"cit","URL":"cit.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"mentioned","URL":"mentioned.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"soCalled","URL":"soCalled.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"desc","URL":"desc.xml","de":{"out-of-date":true,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"gloss","URL":"gloss.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"term","URL":"term.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"ruby","URL":"ruby.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"rb","URL":"rb.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"rt","URL":"rt.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"sic","URL":"sic.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"corr","URL":"corr.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"choice","URL":"choice.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"reg","URL":"reg.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"orig","URL":"orig.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"gap","URL":"gap.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"ellipsis","URL":"ellipsis.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"add","URL":"add.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"del","URL":"del.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"unclear","URL":"unclear.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"name","URL":"name.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"rs","URL":"rs.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"email","URL":"email.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"address","URL":"address.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"addrLine","URL":"addrLine.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"street","URL":"street.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"postCode","URL":"postCode.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"postBox","URL":"postBox.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"num","URL":"num.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"measure","URL":"measure.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"measureGrp","URL":"measureGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"unit","URL":"unit.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"date","URL":"date.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"time","URL":"time.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"abbr","URL":"abbr.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"expan","URL":"expan.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"ptr","URL":"ptr.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"ref","URL":"ref.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"list","URL":"list.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"item","URL":"item.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"label","URL":"label.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"head","URL":"head.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"headLabel","URL":"headLabel.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"headItem","URL":"headItem.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"note","URL":"note.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"noteGrp","URL":"noteGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"index","URL":"index.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"media","URL":"media.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"graphic","URL":"graphic.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"binaryObject","URL":"binaryObject.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"milestone","URL":"milestone.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"gb","URL":"gb.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"pb","URL":"pb.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"lb","URL":"lb.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"cb","URL":"cb.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"analytic","URL":"analytic.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"monogr","URL":"monogr.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"series","URL":"series.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"author","URL":"author.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"editor","URL":"editor.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"respStmt","URL":"respStmt.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"resp","URL":"resp.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"title","URL":"title.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"meeting","URL":"meeting.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"imprint","URL":"imprint.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"publisher","URL":"publisher.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"biblScope","URL":"biblScope.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"citedRange","URL":"citedRange.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"pubPlace","URL":"pubPlace.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"bibl","URL":"bibl.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"biblStruct","URL":"biblStruct.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"listBibl","URL":"listBibl.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"relatedItem","URL":"relatedItem.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"l","URL":"l.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"lg","URL":"lg.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"sp","URL":"sp.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"speaker","URL":"speaker.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"stage","URL":"stage.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"TEI","URL":"TEI.xml","de":{"out-of-date":true,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teiCorpus","URL":"teiCorpus.xml","de":{"out-of-date":true,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"text","URL":"text.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"body","URL":"body.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"group","URL":"group.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"floatingText","URL":"floatingText.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"div","URL":"div.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"div1","URL":"div1.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"div2","URL":"div2.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"div3","URL":"div3.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"div4","URL":"div4.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"div5","URL":"div5.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"div6","URL":"div6.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"div7","URL":"div7.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"divGen","URL":"divGen.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"trailer","URL":"trailer.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"byline","URL":"byline.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"dateline","URL":"dateline.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"argument","URL":"argument.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"epigraph","URL":"epigraph.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"opener","URL":"opener.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"closer","URL":"closer.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"salute","URL":"salute.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"signed","URL":"signed.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"postscript","URL":"postscript.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"titlePage","URL":"titlePage.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"docTitle","URL":"docTitle.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"titlePart","URL":"titlePart.xml","de":{"out-of-date":true,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"docAuthor","URL":"docAuthor.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"imprimatur","URL":"imprimatur.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"docEdition","URL":"docEdition.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"docImprint","URL":"docImprint.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"docDate","URL":"docDate.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"front","URL":"front.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"back","URL":"back.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"g","URL":"g.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"charDecl","URL":"charDecl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"char","URL":"char.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"glyph","URL":"glyph.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"localProp","URL":"localProp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"mapping","URL":"mapping.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"unihanProp","URL":"unihanProp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"unicodeProp","URL":"unicodeProp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"metDecl","URL":"metDecl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"metSym","URL":"metSym.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"caesura","URL":"caesura.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"rhyme","URL":"rhyme.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"set","URL":"set.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"prologue","URL":"prologue.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"epilogue","URL":"epilogue.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"performance","URL":"performance.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"castList","URL":"castList.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"castGroup","URL":"castGroup.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"castItem","URL":"castItem.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"role","URL":"role.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"roleDesc","URL":"roleDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"actor","URL":"actor.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"spGrp","URL":"spGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"move","URL":"move.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"view","URL":"view.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"camera","URL":"camera.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"sound","URL":"sound.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"caption","URL":"caption.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"tech","URL":"tech.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"scriptStmt","URL":"scriptStmt.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"recordingStmt","URL":"recordingStmt.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"recording","URL":"recording.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"equipment","URL":"equipment.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"broadcast","URL":"broadcast.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"transcriptionDesc","URL":"transcriptionDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"u","URL":"u.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"pause","URL":"pause.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"vocal","URL":"vocal.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"kinesic","URL":"kinesic.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"incident","URL":"incident.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"writing","URL":"writing.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"shift","URL":"shift.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"annotationBlock","URL":"annotationBlock.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"superEntry","URL":"superEntry.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"entry","URL":"entry.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"entryFree","URL":"entryFree.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"hom","URL":"hom.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"sense","URL":"sense.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"dictScrap","URL":"dictScrap.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"form","URL":"form.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"orth","URL":"orth.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"pron","URL":"pron.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"hyph","URL":"hyph.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"syll","URL":"syll.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"stress","URL":"stress.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"gram","URL":"gram.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"gen","URL":"gen.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"number","URL":"number.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"case","URL":"case.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"per","URL":"per.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"tns","URL":"tns.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"mood","URL":"mood.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"iType","URL":"iType.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"gramGrp","URL":"gramGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"pos","URL":"pos.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"subc","URL":"subc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"colloc","URL":"colloc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"def","URL":"def.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"etym","URL":"etym.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"lang","URL":"lang.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"usg","URL":"usg.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"lbl","URL":"lbl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"xr","URL":"xr.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"re","URL":"re.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"oRef","URL":"oRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"pRef","URL":"pRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"msDesc","URL":"msDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"catchwords","URL":"catchwords.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"dimensions","URL":"dimensions.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"dim","URL":"dim.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"height","URL":"height.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"depth","URL":"depth.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"width","URL":"width.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"heraldry","URL":"heraldry.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"locus","URL":"locus.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"locusGrp","URL":"locusGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"material","URL":"material.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"objectType","URL":"objectType.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"origDate","URL":"origDate.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"origPlace","URL":"origPlace.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"secFol","URL":"secFol.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"signatures","URL":"signatures.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"stamp","URL":"stamp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"watermark","URL":"watermark.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"msIdentifier","URL":"msIdentifier.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"institution","URL":"institution.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"repository","URL":"repository.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"collection","URL":"collection.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"altIdentifier","URL":"altIdentifier.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"msName","URL":"msName.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"colophon","URL":"colophon.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"explicit","URL":"explicit.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"filiation","URL":"filiation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"finalRubric","URL":"finalRubric.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"incipit","URL":"incipit.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"msContents","URL":"msContents.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"msItem","URL":"msItem.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"msItemStruct","URL":"msItemStruct.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"rubric","URL":"rubric.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"summary","URL":"summary.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"textLang","URL":"textLang.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"physDesc","URL":"physDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"objectDesc","URL":"objectDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"supportDesc","URL":"supportDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"support","URL":"support.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"collation","URL":"collation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"foliation","URL":"foliation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"condition","URL":"condition.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"layoutDesc","URL":"layoutDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"layout","URL":"layout.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"handDesc","URL":"handDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"typeDesc","URL":"typeDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"typeNote","URL":"typeNote.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"scriptDesc","URL":"scriptDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"scriptNote","URL":"scriptNote.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"musicNotation","URL":"musicNotation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"decoDesc","URL":"decoDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"decoNote","URL":"decoNote.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"additions","URL":"additions.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"bindingDesc","URL":"bindingDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"binding","URL":"binding.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"sealDesc","URL":"sealDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"seal","URL":"seal.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"accMat","URL":"accMat.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"history","URL":"history.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"origin","URL":"origin.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"provenance","URL":"provenance.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"acquisition","URL":"acquisition.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"additional","URL":"additional.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"adminInfo","URL":"adminInfo.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"recordHist","URL":"recordHist.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"source","URL":"source.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"custodialHist","URL":"custodialHist.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"custEvent","URL":"custEvent.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"surrogates","URL":"surrogates.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"msPart","URL":"msPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"msFrag","URL":"msFrag.xml","de":{"out-of-date":true,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"facsimile","URL":"facsimile.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"sourceDoc","URL":"sourceDoc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"surface","URL":"surface.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"surfaceGrp","URL":"surfaceGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"zone","URL":"zone.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"path","URL":"path.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"addSpan","URL":"addSpan.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"damage","URL":"damage.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"damageSpan","URL":"damageSpan.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"delSpan","URL":"delSpan.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"ex","URL":"ex.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"fw","URL":"fw.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"handNotes","URL":"handNotes.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"handShift","URL":"handShift.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"am","URL":"am.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"restore","URL":"restore.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"space","URL":"space.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"subst","URL":"subst.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"substJoin","URL":"substJoin.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"supplied","URL":"supplied.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"surplus","URL":"surplus.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"secl","URL":"secl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"line","URL":"line.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listChange","URL":"listChange.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listTranspose","URL":"listTranspose.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"metamark","URL":"metamark.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"mod","URL":"mod.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"redo","URL":"redo.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"retrace","URL":"retrace.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"transpose","URL":"transpose.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"undo","URL":"undo.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"app","URL":"app.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"listApp","URL":"listApp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"lem","URL":"lem.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"rdg","URL":"rdg.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"rdgGrp","URL":"rdgGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"witDetail","URL":"witDetail.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"wit","URL":"wit.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listWit","URL":"listWit.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"witness","URL":"witness.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"witStart","URL":"witStart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"witEnd","URL":"witEnd.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"lacunaStart","URL":"lacunaStart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"lacunaEnd","URL":"lacunaEnd.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"variantEncoding","URL":"variantEncoding.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"orgName","URL":"orgName.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"persName","URL":"persName.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"surname","URL":"surname.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"forename","URL":"forename.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"genName","URL":"genName.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"nameLink","URL":"nameLink.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"addName","URL":"addName.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"roleName","URL":"roleName.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"placeName","URL":"placeName.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"bloc","URL":"bloc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"country","URL":"country.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"region","URL":"region.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"settlement","URL":"settlement.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"district","URL":"district.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"offset","URL":"offset.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"geogName","URL":"geogName.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"geogFeat","URL":"geogFeat.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"affiliation","URL":"affiliation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"age","URL":"age.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"birth","URL":"birth.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"climate","URL":"climate.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"death","URL":"death.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"education","URL":"education.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"event","URL":"event.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"faith","URL":"faith.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"floruit","URL":"floruit.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"gender","URL":"gender.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"geo","URL":"geo.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"langKnowledge","URL":"langKnowledge.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"langKnown","URL":"langKnown.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"listOrg","URL":"listOrg.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listEvent","URL":"listEvent.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listPerson","URL":"listPerson.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listPlace","URL":"listPlace.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listRelation","URL":"listRelation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"location","URL":"location.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"nationality","URL":"nationality.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"occupation","URL":"occupation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"org","URL":"org.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"person","URL":"person.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"persona","URL":"persona.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"personGrp","URL":"personGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"persPronouns","URL":"persPronouns.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"place","URL":"place.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"population","URL":"population.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"relation","URL":"relation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"residence","URL":"residence.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"sex","URL":"sex.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"socecStatus","URL":"socecStatus.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"state","URL":"state.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"terrain","URL":"terrain.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"trait","URL":"trait.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"objectName","URL":"objectName.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"object","URL":"object.xml","de":{"out-of-date":true,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listObject","URL":"listObject.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"objectIdentifier","URL":"objectIdentifier.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"nym","URL":"nym.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"listNym","URL":"listNym.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"table","URL":"table.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"row","URL":"row.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"cell","URL":"cell.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"formula","URL":"formula.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"notatedMusic","URL":"notatedMusic.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"figure","URL":"figure.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"figDesc","URL":"figDesc.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"textDesc","URL":"textDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"particDesc","URL":"particDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"settingDesc","URL":"settingDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"channel","URL":"channel.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"constitution","URL":"constitution.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"derivation","URL":"derivation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"domain","URL":"domain.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"factuality","URL":"factuality.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"interaction","URL":"interaction.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"preparedness","URL":"preparedness.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"purpose","URL":"purpose.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"setting","URL":"setting.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"locale","URL":"locale.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"activity","URL":"activity.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"link","URL":"link.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"linkGrp","URL":"linkGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"ab","URL":"ab.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"anchor","URL":"anchor.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"seg","URL":"seg.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"when","URL":"when.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"timeline","URL":"timeline.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"join","URL":"join.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"joinGrp","URL":"joinGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"alt","URL":"alt.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"altGrp","URL":"altGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"standOff","URL":"standOff.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listAnnotation","URL":"listAnnotation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"annotation","URL":"annotation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"s","URL":"s.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"cl","URL":"cl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"phr","URL":"phr.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"w","URL":"w.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"m","URL":"m.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"c","URL":"c.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"pc","URL":"pc.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"span","URL":"span.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"spanGrp","URL":"spanGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"interp","URL":"interp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"interpGrp","URL":"interpGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"fsdDecl","URL":"fsdDecl.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"fsDecl","URL":"fsDecl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"fsDescr","URL":"fsDescr.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"fsdLink","URL":"fsdLink.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"fDecl","URL":"fDecl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"fDescr","URL":"fDescr.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"vRange","URL":"vRange.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"vDefault","URL":"vDefault.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"if","URL":"if.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"then","URL":"then.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"fsConstraints","URL":"fsConstraints.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"cond","URL":"cond.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"bicond","URL":"bicond.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"iff","URL":"iff.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"fs","URL":"fs.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"f","URL":"f.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"binary","URL":"binary.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"symbol","URL":"symbol.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"numeric","URL":"numeric.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"string","URL":"string.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"vLabel","URL":"vLabel.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"vColl","URL":"vColl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"default","URL":"default.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"vAlt","URL":"vAlt.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"vNot","URL":"vNot.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"vMerge","URL":"vMerge.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"fLib","URL":"fLib.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"fvLib","URL":"fvLib.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"graph","URL":"graph.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"node","URL":"node.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"arc","URL":"arc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"tree","URL":"tree.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"root","URL":"root.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"iNode","URL":"iNode.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"leaf","URL":"leaf.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"eTree","URL":"eTree.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"triangle","URL":"triangle.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"eLeaf","URL":"eLeaf.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"forest","URL":"forest.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listForest","URL":"listForest.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"precision","URL":"precision.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"certainty","URL":"certainty.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"respons","URL":"respons.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att","URL":"att.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"code","URL":"code.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"eg","URL":"eg.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"egXML","URL":"egXML.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"gi","URL":"gi.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"ident","URL":"ident.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"tag","URL":"tag.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"val","URL":"val.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"specList","URL":"specList.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"specDesc","URL":"specDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"classRef","URL":"classRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"elementRef","URL":"elementRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"macroRef","URL":"macroRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"moduleRef","URL":"moduleRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"moduleSpec","URL":"moduleSpec.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"schemaSpec","URL":"schemaSpec.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"specGrp","URL":"specGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"specGrpRef","URL":"specGrpRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"elementSpec","URL":"elementSpec.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"classSpec","URL":"classSpec.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"dataSpec","URL":"dataSpec.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"macroSpec","URL":"macroSpec.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"remarks","URL":"remarks.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listRef","URL":"listRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"exemplum","URL":"exemplum.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"classes","URL":"classes.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"memberOf","URL":"memberOf.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"equiv","URL":"equiv.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"altIdent","URL":"altIdent.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model","URL":"model.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"modelSequence","URL":"modelSequence.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"modelGrp","URL":"modelGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"outputRendition","URL":"outputRendition.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"paramList","URL":"paramList.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"paramSpec","URL":"paramSpec.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"param","URL":"param.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"content","URL":"content.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"sequence","URL":"sequence.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"alternate","URL":"alternate.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"constraint","URL":"constraint.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"constraintSpec","URL":"constraintSpec.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"attList","URL":"attList.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"attDef","URL":"attDef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"attRef","URL":"attRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"datatype","URL":"datatype.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"dataRef","URL":"dataRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"dataFacet","URL":"dataFacet.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"defaultVal","URL":"defaultVal.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"valDesc","URL":"valDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"valItem","URL":"valItem.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"valList","URL":"valList.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"textNode","URL":"textNode.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"anyElement","URL":"anyElement.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"empty","URL":"empty.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}}],"att_classes":[{"id":"att.anchoring","URL":"att.anchoring.xml","de":{"out-of-date":true,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.ascribed","URL":"att.ascribed.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.ascribed.directed","URL":"att.ascribed.directed.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.canonical","URL":"att.canonical.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.ranging","URL":"att.ranging.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.dimensions","URL":"att.dimensions.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.written","URL":"att.written.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.damaged","URL":"att.damaged.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.breaking","URL":"att.breaking.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.cReferencing","URL":"att.cReferencing.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.datable.custom","URL":"att.datable.custom.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.datable.w3c","URL":"att.datable.w3c.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.datable","URL":"att.datable.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.datcat","URL":"att.datcat.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.declarable","URL":"att.declarable.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.declaring","URL":"att.declaring.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.fragmentable","URL":"att.fragmentable.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.divLike","URL":"att.divLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.docStatus","URL":"att.docStatus.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.duration.w3c","URL":"att.duration.w3c.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.duration","URL":"att.duration.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.global.responsibility","URL":"att.global.responsibility.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.editLike","URL":"att.editLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.global.rendition","URL":"att.global.rendition.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.global.source","URL":"att.global.source.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.global","URL":"att.global.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.handFeatures","URL":"att.handFeatures.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.internetMedia","URL":"att.internetMedia.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.media","URL":"att.media.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.resourced","URL":"att.resourced.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.interpLike","URL":"att.interpLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.measurement","URL":"att.measurement.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.milestoneUnit","URL":"att.milestoneUnit.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.naming","URL":"att.naming.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.notated","URL":"att.notated.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.placement","URL":"att.placement.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.typed","URL":"att.typed.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.pointing","URL":"att.pointing.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.pointing.group","URL":"att.pointing.group.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.scoping","URL":"att.scoping.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.segLike","URL":"att.segLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.sortable","URL":"att.sortable.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.edition","URL":"att.edition.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.spanning","URL":"att.spanning.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.styleDef","URL":"att.styleDef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.tableDecoration","URL":"att.tableDecoration.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.timed","URL":"att.timed.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.transcriptional","URL":"att.transcriptional.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.citing","URL":"att.citing.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.citeStructurePart","URL":"att.citeStructurePart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.patternReplacement","URL":"att.patternReplacement.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.formula","URL":"att.formula.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.locatable","URL":"att.locatable.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.gaijiProp","URL":"att.gaijiProp.xml","de":{"out-of-date":true,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.metrical","URL":"att.metrical.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.enjamb","URL":"att.enjamb.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.entryLike","URL":"att.entryLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.lexicographic","URL":"att.lexicographic.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.partials","URL":"att.partials.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.msExcerpt","URL":"att.msExcerpt.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.msClass","URL":"att.msClass.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.global.facs","URL":"att.global.facs.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.global.change","URL":"att.global.change.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.coordinated","URL":"att.coordinated.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.rdgPart","URL":"att.rdgPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.witnessed","URL":"att.witnessed.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.textCritical","URL":"att.textCritical.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.personal","URL":"att.personal.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.datable.iso","URL":"att.datable.iso.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.calendarSystem","URL":"att.calendarSystem.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.duration.iso","URL":"att.duration.iso.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.global.linking","URL":"att.global.linking.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.lexicographic.normalized","URL":"att.lexicographic.normalized.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.linguistic","URL":"att.linguistic.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.global.analytic","URL":"att.global.analytic.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.translatable","URL":"att.translatable.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.predicate","URL":"att.predicate.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.repeatable","URL":"att.repeatable.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.combinable","URL":"att.combinable.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.identified","URL":"att.identified.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"att.deprecated","URL":"att.deprecated.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.namespaceable","URL":"att.namespaceable.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}}],"model_classes":[{"id":"model.nameLike.agent","URL":"model.nameLike.agent.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.segLike","URL":"model.segLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.hiLike","URL":"model.hiLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.emphLike","URL":"model.emphLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.highlighted","URL":"model.highlighted.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.dateLike","URL":"model.dateLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.dimLike","URL":"model.dimLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.measureLike","URL":"model.measureLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.egLike","URL":"model.egLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.graphicLike","URL":"model.graphicLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.offsetLike","URL":"model.offsetLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.pPart.msdesc","URL":"model.pPart.msdesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.pPart.editorial","URL":"model.pPart.editorial.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.pPart.transcriptional","URL":"model.pPart.transcriptional.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.pPart.edit","URL":"model.pPart.edit.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.linePart","URL":"model.linePart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.ptrLike","URL":"model.ptrLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.lPart","URL":"model.lPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.global.meta","URL":"model.global.meta.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"model.milestoneLike","URL":"model.milestoneLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.gLike","URL":"model.gLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.oddDecl","URL":"model.oddDecl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.oddRef","URL":"model.oddRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.phrase.xml","URL":"model.phrase.xml.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.specDescLike","URL":"model.specDescLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.biblLike","URL":"model.biblLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.headLike","URL":"model.headLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.labelLike","URL":"model.labelLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.listLike","URL":"model.listLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.noteLike","URL":"model.noteLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.lLike","URL":"model.lLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.pLike","URL":"model.pLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.stageLike","URL":"model.stageLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"model.featureVal.complex","URL":"model.featureVal.complex.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.featureVal.single","URL":"model.featureVal.single.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.entryPart","URL":"model.entryPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.entryPart.top","URL":"model.entryPart.top.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"model.eventLike","URL":"model.eventLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.global.edit","URL":"model.global.edit.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.global.spoken","URL":"model.global.spoken.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.divPart","URL":"model.divPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"model.persStateLike","URL":"model.persStateLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"model.personLike","URL":"model.personLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.personPart","URL":"model.personPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.placeNamePart","URL":"model.placeNamePart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.placeStateLike","URL":"model.placeStateLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.orgPart","URL":"model.orgPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.publicationStmtPart.agency","URL":"model.publicationStmtPart.agency.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"model.publicationStmtPart.detail","URL":"model.publicationStmtPart.detail.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"model.availabilityPart","URL":"model.availabilityPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.certLike","URL":"model.certLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.descLike","URL":"model.descLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.identEquiv","URL":"model.identEquiv.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.identSynonyms","URL":"model.identSynonyms.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.quoteLike","URL":"model.quoteLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.attributable","URL":"model.attributable.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.rdgLike","URL":"model.rdgLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"model.respLike","URL":"model.respLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.divWrapper","URL":"model.divWrapper.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.divTopPart","URL":"model.divTopPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.divTop","URL":"model.divTop.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.frontPart.drama","URL":"model.frontPart.drama.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.pLike.front","URL":"model.pLike.front.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.divBottomPart","URL":"model.divBottomPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.divBottom","URL":"model.divBottom.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.titlepagePart","URL":"model.titlepagePart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.msQuoteLike","URL":"model.msQuoteLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.msItemPart","URL":"model.msItemPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.choicePart","URL":"model.choicePart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.recordingPart","URL":"model.recordingPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.imprintPart","URL":"model.imprintPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.catDescPart","URL":"model.catDescPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.settingPart","URL":"model.settingPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.textDescPart","URL":"model.textDescPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.castItemPart","URL":"model.castItemPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.physDescPart","URL":"model.physDescPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.addressLike","URL":"model.addressLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.nameLike","URL":"model.nameLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"model.persNamePart","URL":"model.persNamePart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.global","URL":"model.global.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.featureVal","URL":"model.featureVal.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.biblPart","URL":"model.biblPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.frontPart","URL":"model.frontPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.addrPart","URL":"model.addrPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.pPart.data","URL":"model.pPart.data.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.inter","URL":"model.inter.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.common","URL":"model.common.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.phrase","URL":"model.phrase.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"model.paraPart","URL":"model.paraPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.limitedPhrase","URL":"model.limitedPhrase.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.divLike","URL":"model.divLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.divGenLike","URL":"model.divGenLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.div1Like","URL":"model.div1Like.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.div2Like","URL":"model.div2Like.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.div3Like","URL":"model.div3Like.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.div4Like","URL":"model.div4Like.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.div5Like","URL":"model.div5Like.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.div6Like","URL":"model.div6Like.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.div7Like","URL":"model.div7Like.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.annotationLike","URL":"model.annotationLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.annotationPart.body","URL":"model.annotationPart.body.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.applicationLike","URL":"model.applicationLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.teiHeaderPart","URL":"model.teiHeaderPart.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.sourceDescPart","URL":"model.sourceDescPart.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.encodingDescPart","URL":"model.encodingDescPart.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.editorialDeclPart","URL":"model.editorialDeclPart.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.profileDescPart","URL":"model.profileDescPart.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.standOffPart","URL":"model.standOffPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.correspActionPart","URL":"model.correspActionPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.correspContextPart","URL":"model.correspContextPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.correspDescPart","URL":"model.correspDescPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.divPart.spoken","URL":"model.divPart.spoken.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"model.entryLike","URL":"model.entryLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.morphLike","URL":"model.morphLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.lexicalRefinement","URL":"model.lexicalRefinement.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.gramPart","URL":"model.gramPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.formPart","URL":"model.formPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.ptrLike.form","URL":"model.ptrLike.form.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.resource","URL":"model.resource.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.describedResource","URL":"model.describedResource.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.rdgPart","URL":"model.rdgPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.objectLike","URL":"model.objectLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.orgStateLike","URL":"model.orgStateLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.placeLike","URL":"model.placeLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.fsdDeclPart","URL":"model.fsdDeclPart.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.contentPart","URL":"model.contentPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}}],"macros":[{"id":"macro.abContent","URL":"macro.abContent.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"macro.paraContent","URL":"macro.paraContent.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"macro.limitedContent","URL":"macro.limitedContent.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"macro.phraseSeq","URL":"macro.phraseSeq.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"macro.phraseSeq.limited","URL":"macro.phraseSeq.limited.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"macro.specialPara","URL":"macro.specialPara.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"macro.xtext","URL":"macro.xtext.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}}],"datatypes":[{"id":"teidata.certainty","URL":"teidata.certainty.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.probability","URL":"teidata.probability.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.numeric","URL":"teidata.numeric.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.interval","URL":"teidata.interval.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.count","URL":"teidata.count.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.temporal.w3c","URL":"teidata.temporal.w3c.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.temporal.working","URL":"teidata.temporal.working.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.duration.w3c","URL":"teidata.duration.w3c.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.truthValue","URL":"teidata.truthValue.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.xTruthValue","URL":"teidata.xTruthValue.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.language","URL":"teidata.language.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.namespace","URL":"teidata.namespace.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.namespaceOrName","URL":"teidata.namespaceOrName.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.outputMeasurement","URL":"teidata.outputMeasurement.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.pattern","URL":"teidata.pattern.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.point","URL":"teidata.point.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.pointer","URL":"teidata.pointer.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.authority","URL":"teidata.authority.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.version","URL":"teidata.version.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.versionNumber","URL":"teidata.versionNumber.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.replacement","URL":"teidata.replacement.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.xpath","URL":"teidata.xpath.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.word","URL":"teidata.word.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.text","URL":"teidata.text.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.name","URL":"teidata.name.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.xmlName","URL":"teidata.xmlName.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.prefix","URL":"teidata.prefix.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.enumerated","URL":"teidata.enumerated.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.gender","URL":"teidata.gender.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.sex","URL":"teidata.sex.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.probCert","URL":"teidata.probCert.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.unboundedCount","URL":"teidata.unboundedCount.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.nullOrName","URL":"teidata.nullOrName.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.temporal.iso","URL":"teidata.temporal.iso.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.duration.iso","URL":"teidata.duration.iso.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}}]} \ No newline at end of file +{"elements":[{"id":"teiHeader","URL":"teiHeader.xml","de":{"out-of-date":true,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"fileDesc","URL":"fileDesc.xml","de":{"out-of-date":true,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"titleStmt","URL":"titleStmt.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"sponsor","URL":"sponsor.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"funder","URL":"funder.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"principal","URL":"principal.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"editionStmt","URL":"editionStmt.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"edition","URL":"edition.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"extent","URL":"extent.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"publicationStmt","URL":"publicationStmt.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"distributor","URL":"distributor.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"authority","URL":"authority.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"idno","URL":"idno.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"availability","URL":"availability.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"licence","URL":"licence.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"seriesStmt","URL":"seriesStmt.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"notesStmt","URL":"notesStmt.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"sourceDesc","URL":"sourceDesc.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"biblFull","URL":"biblFull.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"encodingDesc","URL":"encodingDesc.xml","de":{"out-of-date":true,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"schemaRef","URL":"schemaRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"projectDesc","URL":"projectDesc.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"samplingDecl","URL":"samplingDecl.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"editorialDecl","URL":"editorialDecl.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"correction","URL":"correction.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"normalization","URL":"normalization.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"quotation","URL":"quotation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"hyphenation","URL":"hyphenation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"segmentation","URL":"segmentation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"stdVals","URL":"stdVals.xml","de":{"out-of-date":true,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"interpretation","URL":"interpretation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"punctuation","URL":"punctuation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"tagsDecl","URL":"tagsDecl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"tagUsage","URL":"tagUsage.xml","de":{"out-of-date":true,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"namespace","URL":"namespace.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"rendition","URL":"rendition.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"styleDefDecl","URL":"styleDefDecl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"refsDecl","URL":"refsDecl.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"citeStructure","URL":"citeStructure.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"citeData","URL":"citeData.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"cRefPattern","URL":"cRefPattern.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"prefixDef","URL":"prefixDef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listPrefixDef","URL":"listPrefixDef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"refState","URL":"refState.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"classDecl","URL":"classDecl.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"taxonomy","URL":"taxonomy.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"category","URL":"category.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"catDesc","URL":"catDesc.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"geoDecl","URL":"geoDecl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"unitDecl","URL":"unitDecl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"unitDef","URL":"unitDef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"conversion","URL":"conversion.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"appInfo","URL":"appInfo.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"application","URL":"application.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"profileDesc","URL":"profileDesc.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"handNote","URL":"handNote.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"abstract","URL":"abstract.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"creation","URL":"creation.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"langUsage","URL":"langUsage.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"language","URL":"language.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"textClass","URL":"textClass.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"keywords","URL":"keywords.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"classCode","URL":"classCode.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"catRef","URL":"catRef.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"calendarDesc","URL":"calendarDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"calendar","URL":"calendar.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"correspDesc","URL":"correspDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"correspAction","URL":"correspAction.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"correspContext","URL":"correspContext.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"xenoData","URL":"xenoData.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"revisionDesc","URL":"revisionDesc.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"change","URL":"change.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"p","URL":"p.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"foreign","URL":"foreign.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"emph","URL":"emph.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"hi","URL":"hi.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"distinct","URL":"distinct.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"said","URL":"said.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"quote","URL":"quote.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"q","URL":"q.xml","de":{"out-of-date":true,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"cit","URL":"cit.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"mentioned","URL":"mentioned.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"soCalled","URL":"soCalled.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"desc","URL":"desc.xml","de":{"out-of-date":true,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"gloss","URL":"gloss.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"term","URL":"term.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"ruby","URL":"ruby.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"rb","URL":"rb.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"rt","URL":"rt.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"sic","URL":"sic.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"corr","URL":"corr.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"choice","URL":"choice.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"reg","URL":"reg.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"orig","URL":"orig.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"gap","URL":"gap.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"ellipsis","URL":"ellipsis.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"add","URL":"add.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"del","URL":"del.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"unclear","URL":"unclear.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"name","URL":"name.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"rs","URL":"rs.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"email","URL":"email.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"address","URL":"address.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"addrLine","URL":"addrLine.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"street","URL":"street.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"postCode","URL":"postCode.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"postBox","URL":"postBox.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"num","URL":"num.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"measure","URL":"measure.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"measureGrp","URL":"measureGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"unit","URL":"unit.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"date","URL":"date.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"time","URL":"time.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"abbr","URL":"abbr.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"expan","URL":"expan.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"ptr","URL":"ptr.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"ref","URL":"ref.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"list","URL":"list.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"item","URL":"item.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"label","URL":"label.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"head","URL":"head.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"headLabel","URL":"headLabel.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"headItem","URL":"headItem.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"note","URL":"note.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"noteGrp","URL":"noteGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"index","URL":"index.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"media","URL":"media.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"graphic","URL":"graphic.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"binaryObject","URL":"binaryObject.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"milestone","URL":"milestone.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"gb","URL":"gb.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"pb","URL":"pb.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"lb","URL":"lb.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"cb","URL":"cb.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"analytic","URL":"analytic.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"monogr","URL":"monogr.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"series","URL":"series.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"author","URL":"author.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"editor","URL":"editor.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"respStmt","URL":"respStmt.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"resp","URL":"resp.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"title","URL":"title.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"meeting","URL":"meeting.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"imprint","URL":"imprint.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"publisher","URL":"publisher.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"biblScope","URL":"biblScope.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"citedRange","URL":"citedRange.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"pubPlace","URL":"pubPlace.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"bibl","URL":"bibl.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"biblStruct","URL":"biblStruct.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"listBibl","URL":"listBibl.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"relatedItem","URL":"relatedItem.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"l","URL":"l.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"lg","URL":"lg.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"sp","URL":"sp.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"speaker","URL":"speaker.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"stage","URL":"stage.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"TEI","URL":"TEI.xml","de":{"out-of-date":true,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teiCorpus","URL":"teiCorpus.xml","de":{"out-of-date":true,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"text","URL":"text.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"body","URL":"body.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"group","URL":"group.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"floatingText","URL":"floatingText.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"div","URL":"div.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"div1","URL":"div1.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"div2","URL":"div2.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"div3","URL":"div3.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"div4","URL":"div4.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"div5","URL":"div5.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"div6","URL":"div6.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"div7","URL":"div7.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"divGen","URL":"divGen.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"trailer","URL":"trailer.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"byline","URL":"byline.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"dateline","URL":"dateline.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"argument","URL":"argument.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"epigraph","URL":"epigraph.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"opener","URL":"opener.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"closer","URL":"closer.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"salute","URL":"salute.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"signed","URL":"signed.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"postscript","URL":"postscript.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"titlePage","URL":"titlePage.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"docTitle","URL":"docTitle.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"titlePart","URL":"titlePart.xml","de":{"out-of-date":true,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"docAuthor","URL":"docAuthor.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"imprimatur","URL":"imprimatur.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"docEdition","URL":"docEdition.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"docImprint","URL":"docImprint.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"docDate","URL":"docDate.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"front","URL":"front.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"back","URL":"back.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"g","URL":"g.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"charDecl","URL":"charDecl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"char","URL":"char.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"glyph","URL":"glyph.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"localProp","URL":"localProp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"mapping","URL":"mapping.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"unihanProp","URL":"unihanProp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"unicodeProp","URL":"unicodeProp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"metDecl","URL":"metDecl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"metSym","URL":"metSym.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"caesura","URL":"caesura.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"rhyme","URL":"rhyme.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"set","URL":"set.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"prologue","URL":"prologue.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"epilogue","URL":"epilogue.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"performance","URL":"performance.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"castList","URL":"castList.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"castGroup","URL":"castGroup.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"castItem","URL":"castItem.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"role","URL":"role.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"roleDesc","URL":"roleDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"actor","URL":"actor.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"spGrp","URL":"spGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"move","URL":"move.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"view","URL":"view.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"camera","URL":"camera.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"sound","URL":"sound.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"caption","URL":"caption.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"tech","URL":"tech.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"scriptStmt","URL":"scriptStmt.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"recordingStmt","URL":"recordingStmt.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"recording","URL":"recording.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"equipment","URL":"equipment.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"broadcast","URL":"broadcast.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"transcriptionDesc","URL":"transcriptionDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"u","URL":"u.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"pause","URL":"pause.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"vocal","URL":"vocal.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"kinesic","URL":"kinesic.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"incident","URL":"incident.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"writing","URL":"writing.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"shift","URL":"shift.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"annotationBlock","URL":"annotationBlock.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"superEntry","URL":"superEntry.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"entry","URL":"entry.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"entryFree","URL":"entryFree.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"hom","URL":"hom.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"sense","URL":"sense.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"dictScrap","URL":"dictScrap.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"form","URL":"form.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"orth","URL":"orth.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"pron","URL":"pron.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"hyph","URL":"hyph.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"syll","URL":"syll.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"stress","URL":"stress.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"gram","URL":"gram.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"gen","URL":"gen.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"number","URL":"number.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"case","URL":"case.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"per","URL":"per.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"tns","URL":"tns.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"mood","URL":"mood.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"iType","URL":"iType.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"gramGrp","URL":"gramGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"pos","URL":"pos.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"subc","URL":"subc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"colloc","URL":"colloc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"def","URL":"def.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"etym","URL":"etym.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"lang","URL":"lang.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"usg","URL":"usg.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"lbl","URL":"lbl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"xr","URL":"xr.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"re","URL":"re.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"oRef","URL":"oRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"pRef","URL":"pRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"msDesc","URL":"msDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"catchwords","URL":"catchwords.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"dimensions","URL":"dimensions.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"dim","URL":"dim.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"height","URL":"height.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"depth","URL":"depth.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"width","URL":"width.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"heraldry","URL":"heraldry.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"locus","URL":"locus.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"locusGrp","URL":"locusGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"material","URL":"material.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"objectType","URL":"objectType.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"origDate","URL":"origDate.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"origPlace","URL":"origPlace.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"secFol","URL":"secFol.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"signatures","URL":"signatures.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"stamp","URL":"stamp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"watermark","URL":"watermark.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"msIdentifier","URL":"msIdentifier.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"institution","URL":"institution.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"repository","URL":"repository.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"collection","URL":"collection.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"altIdentifier","URL":"altIdentifier.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"msName","URL":"msName.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"colophon","URL":"colophon.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"explicit","URL":"explicit.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"filiation","URL":"filiation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"finalRubric","URL":"finalRubric.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"incipit","URL":"incipit.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"msContents","URL":"msContents.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"msItem","URL":"msItem.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"msItemStruct","URL":"msItemStruct.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"rubric","URL":"rubric.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"summary","URL":"summary.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"textLang","URL":"textLang.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"physDesc","URL":"physDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"objectDesc","URL":"objectDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"supportDesc","URL":"supportDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"support","URL":"support.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"collation","URL":"collation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"foliation","URL":"foliation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"condition","URL":"condition.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"layoutDesc","URL":"layoutDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"layout","URL":"layout.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"handDesc","URL":"handDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"typeDesc","URL":"typeDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"typeNote","URL":"typeNote.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"scriptDesc","URL":"scriptDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"scriptNote","URL":"scriptNote.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"musicNotation","URL":"musicNotation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"decoDesc","URL":"decoDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"decoNote","URL":"decoNote.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"additions","URL":"additions.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"bindingDesc","URL":"bindingDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"binding","URL":"binding.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"sealDesc","URL":"sealDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"seal","URL":"seal.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"accMat","URL":"accMat.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"history","URL":"history.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"origin","URL":"origin.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"provenance","URL":"provenance.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"acquisition","URL":"acquisition.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"additional","URL":"additional.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"adminInfo","URL":"adminInfo.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"recordHist","URL":"recordHist.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"source","URL":"source.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"custodialHist","URL":"custodialHist.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"custEvent","URL":"custEvent.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"surrogates","URL":"surrogates.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"msPart","URL":"msPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"msFrag","URL":"msFrag.xml","de":{"out-of-date":true,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"facsimile","URL":"facsimile.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"sourceDoc","URL":"sourceDoc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"surface","URL":"surface.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"surfaceGrp","URL":"surfaceGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"zone","URL":"zone.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"path","URL":"path.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"addSpan","URL":"addSpan.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"damage","URL":"damage.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"damageSpan","URL":"damageSpan.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"delSpan","URL":"delSpan.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"ex","URL":"ex.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"fw","URL":"fw.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"handNotes","URL":"handNotes.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"handShift","URL":"handShift.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"am","URL":"am.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"restore","URL":"restore.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"space","URL":"space.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"subst","URL":"subst.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"substJoin","URL":"substJoin.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"supplied","URL":"supplied.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"surplus","URL":"surplus.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"secl","URL":"secl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"line","URL":"line.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listChange","URL":"listChange.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listTranspose","URL":"listTranspose.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"metamark","URL":"metamark.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"mod","URL":"mod.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"redo","URL":"redo.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"retrace","URL":"retrace.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"transpose","URL":"transpose.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"undo","URL":"undo.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"app","URL":"app.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"listApp","URL":"listApp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"lem","URL":"lem.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"rdg","URL":"rdg.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"rdgGrp","URL":"rdgGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"witDetail","URL":"witDetail.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"wit","URL":"wit.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listWit","URL":"listWit.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"witness","URL":"witness.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"witStart","URL":"witStart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"witEnd","URL":"witEnd.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"lacunaStart","URL":"lacunaStart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"lacunaEnd","URL":"lacunaEnd.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"variantEncoding","URL":"variantEncoding.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"orgName","URL":"orgName.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"persName","URL":"persName.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"surname","URL":"surname.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"forename","URL":"forename.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"genName","URL":"genName.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"nameLink","URL":"nameLink.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"addName","URL":"addName.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"roleName","URL":"roleName.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"placeName","URL":"placeName.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"bloc","URL":"bloc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"country","URL":"country.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"region","URL":"region.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"settlement","URL":"settlement.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"district","URL":"district.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"offset","URL":"offset.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"geogName","URL":"geogName.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"geogFeat","URL":"geogFeat.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"affiliation","URL":"affiliation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"age","URL":"age.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"birth","URL":"birth.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"climate","URL":"climate.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"death","URL":"death.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"education","URL":"education.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"event","URL":"event.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"faith","URL":"faith.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"floruit","URL":"floruit.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"gender","URL":"gender.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"geo","URL":"geo.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"langKnowledge","URL":"langKnowledge.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"langKnown","URL":"langKnown.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"listOrg","URL":"listOrg.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listEvent","URL":"listEvent.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listPerson","URL":"listPerson.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listPlace","URL":"listPlace.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listRelation","URL":"listRelation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"location","URL":"location.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"nationality","URL":"nationality.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"occupation","URL":"occupation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"org","URL":"org.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"person","URL":"person.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"persona","URL":"persona.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"personGrp","URL":"personGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"persPronouns","URL":"persPronouns.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"place","URL":"place.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"population","URL":"population.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"relation","URL":"relation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"residence","URL":"residence.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"sex","URL":"sex.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"socecStatus","URL":"socecStatus.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"state","URL":"state.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"terrain","URL":"terrain.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"trait","URL":"trait.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"objectName","URL":"objectName.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"object","URL":"object.xml","de":{"out-of-date":true,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listObject","URL":"listObject.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"objectIdentifier","URL":"objectIdentifier.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"nym","URL":"nym.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"listNym","URL":"listNym.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"table","URL":"table.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"row","URL":"row.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"cell","URL":"cell.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"formula","URL":"formula.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"notatedMusic","URL":"notatedMusic.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"figure","URL":"figure.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"figDesc","URL":"figDesc.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"textDesc","URL":"textDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"particDesc","URL":"particDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"settingDesc","URL":"settingDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"channel","URL":"channel.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"constitution","URL":"constitution.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"derivation","URL":"derivation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"domain","URL":"domain.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"factuality","URL":"factuality.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"interaction","URL":"interaction.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"preparedness","URL":"preparedness.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"purpose","URL":"purpose.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"setting","URL":"setting.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"locale","URL":"locale.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"activity","URL":"activity.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"link","URL":"link.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"linkGrp","URL":"linkGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"ab","URL":"ab.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"anchor","URL":"anchor.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"seg","URL":"seg.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"when","URL":"when.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"timeline","URL":"timeline.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"join","URL":"join.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"joinGrp","URL":"joinGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"alt","URL":"alt.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"altGrp","URL":"altGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"standOff","URL":"standOff.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listAnnotation","URL":"listAnnotation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"annotation","URL":"annotation.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"s","URL":"s.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"cl","URL":"cl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"phr","URL":"phr.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"w","URL":"w.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"m","URL":"m.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"c","URL":"c.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"pc","URL":"pc.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"span","URL":"span.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"spanGrp","URL":"spanGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"interp","URL":"interp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"interpGrp","URL":"interpGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"fsdDecl","URL":"fsdDecl.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"fsDecl","URL":"fsDecl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"fsDescr","URL":"fsDescr.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"fsdLink","URL":"fsdLink.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"fDecl","URL":"fDecl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"fDescr","URL":"fDescr.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"vRange","URL":"vRange.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"vDefault","URL":"vDefault.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"if","URL":"if.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"then","URL":"then.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"fsConstraints","URL":"fsConstraints.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"cond","URL":"cond.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"bicond","URL":"bicond.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"iff","URL":"iff.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"fs","URL":"fs.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"f","URL":"f.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"binary","URL":"binary.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"symbol","URL":"symbol.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"numeric","URL":"numeric.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"string","URL":"string.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"vLabel","URL":"vLabel.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"vColl","URL":"vColl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"default","URL":"default.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"vAlt","URL":"vAlt.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"vNot","URL":"vNot.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"vMerge","URL":"vMerge.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"fLib","URL":"fLib.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"fvLib","URL":"fvLib.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"graph","URL":"graph.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"node","URL":"node.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"arc","URL":"arc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"tree","URL":"tree.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"root","URL":"root.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"iNode","URL":"iNode.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"leaf","URL":"leaf.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"eTree","URL":"eTree.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"triangle","URL":"triangle.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"eLeaf","URL":"eLeaf.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"forest","URL":"forest.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listForest","URL":"listForest.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"precision","URL":"precision.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"certainty","URL":"certainty.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"respons","URL":"respons.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att","URL":"att.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"code","URL":"code.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"eg","URL":"eg.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"egXML","URL":"egXML.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"gi","URL":"gi.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"ident","URL":"ident.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"tag","URL":"tag.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"val","URL":"val.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"specList","URL":"specList.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"specDesc","URL":"specDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"classRef","URL":"classRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"elementRef","URL":"elementRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"macroRef","URL":"macroRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"moduleRef","URL":"moduleRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"moduleSpec","URL":"moduleSpec.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"schemaSpec","URL":"schemaSpec.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"specGrp","URL":"specGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"specGrpRef","URL":"specGrpRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"elementSpec","URL":"elementSpec.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"classSpec","URL":"classSpec.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"dataSpec","URL":"dataSpec.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"macroSpec","URL":"macroSpec.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"remarks","URL":"remarks.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"listRef","URL":"listRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"exemplum","URL":"exemplum.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"classes","URL":"classes.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"memberOf","URL":"memberOf.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"equiv","URL":"equiv.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"altIdent","URL":"altIdent.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model","URL":"model.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"modelSequence","URL":"modelSequence.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"modelGrp","URL":"modelGrp.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"outputRendition","URL":"outputRendition.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"paramList","URL":"paramList.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"paramSpec","URL":"paramSpec.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"param","URL":"param.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"content","URL":"content.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"sequence","URL":"sequence.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"alternate","URL":"alternate.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"constraint","URL":"constraint.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"constraintSpec","URL":"constraintSpec.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"attList","URL":"attList.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"attDef","URL":"attDef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"attRef","URL":"attRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"datatype","URL":"datatype.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"dataRef","URL":"dataRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"dataFacet","URL":"dataFacet.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"defaultVal","URL":"defaultVal.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"valDesc","URL":"valDesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"valItem","URL":"valItem.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"valList","URL":"valList.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"textNode","URL":"textNode.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"anyElement","URL":"anyElement.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"empty","URL":"empty.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}}],"att_classes":[{"id":"att.anchoring","URL":"att.anchoring.xml","de":{"out-of-date":true,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.ascribed","URL":"att.ascribed.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.ascribed.directed","URL":"att.ascribed.directed.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.canonical","URL":"att.canonical.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.ranging","URL":"att.ranging.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.dimensions","URL":"att.dimensions.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.written","URL":"att.written.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.damaged","URL":"att.damaged.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.breaking","URL":"att.breaking.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.cReferencing","URL":"att.cReferencing.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.datable.custom","URL":"att.datable.custom.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.datable.w3c","URL":"att.datable.w3c.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.datable","URL":"att.datable.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.datcat","URL":"att.datcat.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.declarable","URL":"att.declarable.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.declaring","URL":"att.declaring.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.fragmentable","URL":"att.fragmentable.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.divLike","URL":"att.divLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.docStatus","URL":"att.docStatus.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.duration.w3c","URL":"att.duration.w3c.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.duration","URL":"att.duration.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.global.responsibility","URL":"att.global.responsibility.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.editLike","URL":"att.editLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.global.rendition","URL":"att.global.rendition.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.global.source","URL":"att.global.source.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.global","URL":"att.global.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.handFeatures","URL":"att.handFeatures.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.internetMedia","URL":"att.internetMedia.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.media","URL":"att.media.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.resourced","URL":"att.resourced.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.interpLike","URL":"att.interpLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.measurement","URL":"att.measurement.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.milestoneUnit","URL":"att.milestoneUnit.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.naming","URL":"att.naming.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.notated","URL":"att.notated.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.placement","URL":"att.placement.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.typed","URL":"att.typed.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.pointing","URL":"att.pointing.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.pointing.group","URL":"att.pointing.group.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.scoping","URL":"att.scoping.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.segLike","URL":"att.segLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.sortable","URL":"att.sortable.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.edition","URL":"att.edition.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.spanning","URL":"att.spanning.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.styleDef","URL":"att.styleDef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.tableDecoration","URL":"att.tableDecoration.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.timed","URL":"att.timed.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.transcriptional","URL":"att.transcriptional.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.citing","URL":"att.citing.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.citeStructurePart","URL":"att.citeStructurePart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.patternReplacement","URL":"att.patternReplacement.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.formula","URL":"att.formula.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.locatable","URL":"att.locatable.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.gaijiProp","URL":"att.gaijiProp.xml","de":{"out-of-date":true,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.metrical","URL":"att.metrical.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.enjamb","URL":"att.enjamb.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.entryLike","URL":"att.entryLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.lexicographic","URL":"att.lexicographic.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.partials","URL":"att.partials.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.msExcerpt","URL":"att.msExcerpt.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.msClass","URL":"att.msClass.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.global.facs","URL":"att.global.facs.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.global.change","URL":"att.global.change.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.coordinated","URL":"att.coordinated.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.rdgPart","URL":"att.rdgPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.witnessed","URL":"att.witnessed.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.textCritical","URL":"att.textCritical.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.personal","URL":"att.personal.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.datable.iso","URL":"att.datable.iso.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.calendarSystem","URL":"att.calendarSystem.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.duration.iso","URL":"att.duration.iso.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.global.linking","URL":"att.global.linking.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.lexicographic.normalized","URL":"att.lexicographic.normalized.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.linguistic","URL":"att.linguistic.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.global.analytic","URL":"att.global.analytic.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.translatable","URL":"att.translatable.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.predicate","URL":"att.predicate.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.repeatable","URL":"att.repeatable.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.combinable","URL":"att.combinable.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"att.identified","URL":"att.identified.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"att.deprecated","URL":"att.deprecated.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"att.namespaceable","URL":"att.namespaceable.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}}],"model_classes":[{"id":"model.nameLike.agent","URL":"model.nameLike.agent.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.segLike","URL":"model.segLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.hiLike","URL":"model.hiLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.emphLike","URL":"model.emphLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.highlighted","URL":"model.highlighted.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.dateLike","URL":"model.dateLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.dimLike","URL":"model.dimLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.measureLike","URL":"model.measureLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.egLike","URL":"model.egLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.graphicLike","URL":"model.graphicLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.offsetLike","URL":"model.offsetLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.pPart.msdesc","URL":"model.pPart.msdesc.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.pPart.editorial","URL":"model.pPart.editorial.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.pPart.transcriptional","URL":"model.pPart.transcriptional.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.pPart.edit","URL":"model.pPart.edit.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.linePart","URL":"model.linePart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.ptrLike","URL":"model.ptrLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.lPart","URL":"model.lPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.global.meta","URL":"model.global.meta.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"model.milestoneLike","URL":"model.milestoneLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.gLike","URL":"model.gLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.oddDecl","URL":"model.oddDecl.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.oddRef","URL":"model.oddRef.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.phrase.xml","URL":"model.phrase.xml.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.specDescLike","URL":"model.specDescLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.biblLike","URL":"model.biblLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.headLike","URL":"model.headLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.labelLike","URL":"model.labelLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.listLike","URL":"model.listLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.noteLike","URL":"model.noteLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.lLike","URL":"model.lLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.pLike","URL":"model.pLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.stageLike","URL":"model.stageLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"model.featureVal.complex","URL":"model.featureVal.complex.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.featureVal.single","URL":"model.featureVal.single.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.entryPart","URL":"model.entryPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.entryPart.top","URL":"model.entryPart.top.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"model.eventLike","URL":"model.eventLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.global.edit","URL":"model.global.edit.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.global.spoken","URL":"model.global.spoken.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.divPart","URL":"model.divPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"model.persStateLike","URL":"model.persStateLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"model.personLike","URL":"model.personLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.personPart","URL":"model.personPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.placeNamePart","URL":"model.placeNamePart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.placeStateLike","URL":"model.placeStateLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.orgPart","URL":"model.orgPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.publicationStmtPart.agency","URL":"model.publicationStmtPart.agency.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"model.publicationStmtPart.detail","URL":"model.publicationStmtPart.detail.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"model.availabilityPart","URL":"model.availabilityPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.certLike","URL":"model.certLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.descLike","URL":"model.descLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.identEquiv","URL":"model.identEquiv.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.identSynonyms","URL":"model.identSynonyms.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.quoteLike","URL":"model.quoteLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.attributable","URL":"model.attributable.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.rdgLike","URL":"model.rdgLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"model.respLike","URL":"model.respLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.divWrapper","URL":"model.divWrapper.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.divTopPart","URL":"model.divTopPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.divTop","URL":"model.divTop.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.frontPart.drama","URL":"model.frontPart.drama.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.pLike.front","URL":"model.pLike.front.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.divBottomPart","URL":"model.divBottomPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.divBottom","URL":"model.divBottom.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.titlepagePart","URL":"model.titlepagePart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.msQuoteLike","URL":"model.msQuoteLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.msItemPart","URL":"model.msItemPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.choicePart","URL":"model.choicePart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.recordingPart","URL":"model.recordingPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.imprintPart","URL":"model.imprintPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.catDescPart","URL":"model.catDescPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.settingPart","URL":"model.settingPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.textDescPart","URL":"model.textDescPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.castItemPart","URL":"model.castItemPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.physDescPart","URL":"model.physDescPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.addressLike","URL":"model.addressLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.nameLike","URL":"model.nameLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"model.persNamePart","URL":"model.persNamePart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.global","URL":"model.global.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.featureVal","URL":"model.featureVal.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.biblPart","URL":"model.biblPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.frontPart","URL":"model.frontPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.addrPart","URL":"model.addrPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.pPart.data","URL":"model.pPart.data.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.inter","URL":"model.inter.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.common","URL":"model.common.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.phrase","URL":"model.phrase.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"model.paraPart","URL":"model.paraPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.limitedPhrase","URL":"model.limitedPhrase.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.divLike","URL":"model.divLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.divGenLike","URL":"model.divGenLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.div1Like","URL":"model.div1Like.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.div2Like","URL":"model.div2Like.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.div3Like","URL":"model.div3Like.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.div4Like","URL":"model.div4Like.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.div5Like","URL":"model.div5Like.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.div6Like","URL":"model.div6Like.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.div7Like","URL":"model.div7Like.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.annotationLike","URL":"model.annotationLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.annotationPart.body","URL":"model.annotationPart.body.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.applicationLike","URL":"model.applicationLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.teiHeaderPart","URL":"model.teiHeaderPart.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.sourceDescPart","URL":"model.sourceDescPart.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.encodingDescPart","URL":"model.encodingDescPart.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.editorialDeclPart","URL":"model.editorialDeclPart.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.profileDescPart","URL":"model.profileDescPart.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.standOffPart","URL":"model.standOffPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.correspActionPart","URL":"model.correspActionPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.correspContextPart","URL":"model.correspContextPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.correspDescPart","URL":"model.correspDescPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.divPart.spoken","URL":"model.divPart.spoken.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"model.entryLike","URL":"model.entryLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.morphLike","URL":"model.morphLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.lexicalRefinement","URL":"model.lexicalRefinement.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.gramPart","URL":"model.gramPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.formPart","URL":"model.formPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"model.ptrLike.form","URL":"model.ptrLike.form.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"model.resource","URL":"model.resource.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":false},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.describedResource","URL":"model.describedResource.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.rdgPart","URL":"model.rdgPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.objectLike","URL":"model.objectLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.orgStateLike","URL":"model.orgStateLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.placeLike","URL":"model.placeLike.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.fsdDeclPart","URL":"model.fsdDeclPart.xml","de":{"out-of-date":false,"missing":false},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"model.contentPart","URL":"model.contentPart.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}}],"macros":[{"id":"macro.abContent","URL":"macro.abContent.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"macro.paraContent","URL":"macro.paraContent.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"macro.limitedContent","URL":"macro.limitedContent.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":false},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":true,"missing":false}},{"id":"macro.phraseSeq","URL":"macro.phraseSeq.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"macro.phraseSeq.limited","URL":"macro.phraseSeq.limited.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"macro.specialPara","URL":"macro.specialPara.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}},{"id":"macro.xtext","URL":"macro.xtext.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":false},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":false},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":false},"zh-TW":{"out-of-date":false,"missing":false}}],"datatypes":[{"id":"teidata.certainty","URL":"teidata.certainty.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.probability","URL":"teidata.probability.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.numeric","URL":"teidata.numeric.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.interval","URL":"teidata.interval.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.count","URL":"teidata.count.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.temporal.w3c","URL":"teidata.temporal.w3c.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.temporal.working","URL":"teidata.temporal.working.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.duration.w3c","URL":"teidata.duration.w3c.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.truthValue","URL":"teidata.truthValue.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.xTruthValue","URL":"teidata.xTruthValue.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.language","URL":"teidata.language.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.namespace","URL":"teidata.namespace.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.namespaceOrName","URL":"teidata.namespaceOrName.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.outputMeasurement","URL":"teidata.outputMeasurement.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.pattern","URL":"teidata.pattern.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.point","URL":"teidata.point.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.pointer","URL":"teidata.pointer.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.authority","URL":"teidata.authority.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.version","URL":"teidata.version.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.versionNumber","URL":"teidata.versionNumber.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.replacement","URL":"teidata.replacement.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.xpath","URL":"teidata.xpath.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.word","URL":"teidata.word.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.text","URL":"teidata.text.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.name","URL":"teidata.name.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.xmlName","URL":"teidata.xmlName.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.prefix","URL":"teidata.prefix.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.enumerated","URL":"teidata.enumerated.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":true,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":true,"missing":true},"ja":{"out-of-date":true,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.gender","URL":"teidata.gender.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.sex","URL":"teidata.sex.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":true,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":true,"missing":true},"ko":{"out-of-date":true,"missing":true},"zh-TW":{"out-of-date":true,"missing":true}},{"id":"teidata.probCert","URL":"teidata.probCert.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.unboundedCount","URL":"teidata.unboundedCount.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.nullOrName","URL":"teidata.nullOrName.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":true},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":true},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.temporal.iso","URL":"teidata.temporal.iso.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}},{"id":"teidata.duration.iso","URL":"teidata.duration.iso.xml","de":{"out-of-date":false,"missing":true},"es":{"out-of-date":false,"missing":true},"fr":{"out-of-date":false,"missing":false},"it":{"out-of-date":false,"missing":true},"ja":{"out-of-date":false,"missing":false},"ko":{"out-of-date":false,"missing":true},"zh-TW":{"out-of-date":false,"missing":true}}]} From 504b0b635f5d3c05579ed6f4234eec594585a560 Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Fri, 15 Mar 2024 12:59:50 -0400 Subject: [PATCH 057/127] =?UTF-8?q?Updated=20some=20old=20attrs=20in=20eam?= =?UTF-8?q?ple=20to=20current=20versions.=20But=20=E2=80=A6=20=E2=80=A6=20?= =?UTF-8?q?this=20begs=20the=20question,=20=E2=80=9Cwhy=20didn=E2=80=99t?= =?UTF-8?q?=20'make=20validate'=20catch=20these=20errors=20earlier=3F?= =?UTF-8?q?=E2=80=9D,=20to=20which=20I=20do=20not=20have=20an=20answer=20a?= =?UTF-8?q?t=20the=20moment.?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .../Guidelines/en/CMC-ComputerMediatedCommunication.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml index b0ad1e39fe..8813041aec 100644 --- a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml +++ b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml @@ -382,10 +382,10 @@ See the file COPYING.txt for details. synch="#tweetsbcrn18.t002" xml:id="cmc_post_1043769240136880128"> - - -
+ +
From 693b784ad1b090fde34809cb0cde60cd9198da8e Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Fri, 15 Mar 2024 16:26:36 -0400 Subject: [PATCH 058/127] ooops; correct a typo in the previous fix --- P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml index 8813041aec..b3321bea2f 100644 --- a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml +++ b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml @@ -382,7 +382,7 @@ See the file COPYING.txt for details. synch="#tweetsbcrn18.t002" xml:id="cmc_post_1043769240136880128"> -
From 92ddadb26e4997f4ccff213524425f3a0e230c5b Mon Sep 17 00:00:00 2001 From: Klaus Rettinghaus Date: Wed, 1 May 2024 13:32:58 +0200 Subject: [PATCH 059/127] change Akquisition into Akquise --- P5/Source/Specs/acquisition.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/P5/Source/Specs/acquisition.xml b/P5/Source/Specs/acquisition.xml index 4f78ee023d..62f1d9a88f 100644 --- a/P5/Source/Specs/acquisition.xml +++ b/P5/Source/Specs/acquisition.xml @@ -4,7 +4,7 @@ acquisition adquisición acquisition - Akquisition + Akquise contains any descriptive or other information concerning the process by which a manuscript or manuscript part or other object entered the holding institution. From d6eb80eea8986975aaeb129d655171296179a6d0 Mon Sep 17 00:00:00 2001 From: Joey Takeda Date: Sun, 12 May 2024 10:33:10 -0700 Subject: [PATCH 060/127] Attempting fix for #2508 (#2553) Thanks to @martindholmes --- P5/Utilities/guidelines.xsl.model | 40 +++++++++++++++++-------------- 1 file changed, 22 insertions(+), 18 deletions(-) diff --git a/P5/Utilities/guidelines.xsl.model b/P5/Utilities/guidelines.xsl.model index 691e2491e8..a556447a11 100644 --- a/P5/Utilities/guidelines.xsl.model +++ b/P5/Utilities/guidelines.xsl.model @@ -125,12 +125,14 @@ false - + + TEI P5: Guidelines for Electronic Text and Interchange @@ -144,12 +146,13 @@ - + THIS IS A GENERATED FILE. DO NOT EDIT (97) @@ -195,12 +198,13 @@ - + THIS IS A GENERATED FILE. DO NOT EDIT (98) From 36fe9e0a0367550557a95b8ef8795d78dd0a0a50 Mon Sep 17 00:00:00 2001 From: James Cummings <296651+jamescummings@users.noreply.github.com> Date: Thu, 16 May 2024 15:00:09 +0000 Subject: [PATCH 061/127] Adding xenoData to standOff as per #2436 --- P5/Source/Guidelines/en/HD-Header.xml | 6 +++++- P5/Source/Specs/xenoData.xml | 1 + 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/P5/Source/Guidelines/en/HD-Header.xml b/P5/Source/Guidelines/en/HD-Header.xml index b03c51e5d7..f9d5ed5657 100644 --- a/P5/Source/Guidelines/en/HD-Header.xml +++ b/P5/Source/Guidelines/en/HD-Header.xml @@ -2519,7 +2519,11 @@ grouping makes it easy to avoid accidentally flagging non-TEI data as errors during validation of the file against a TEI schema. The xenoData element, which may appear in the TEI header after the fileDesc but before the optional revisionDesc, -is provided for this purpose. +is provided for this purpose. Where the use of xenoData is primarily +to store linked data, contextual information, or stand-off annotations +that refer to the contents of the TEI file itself, +then it is also possible to place xenoData inside the standOff +element.

diff --git a/P5/Source/Specs/xenoData.xml b/P5/Source/Specs/xenoData.xml index 3cb07cc48a..ba086b9f48 100644 --- a/P5/Source/Specs/xenoData.xml +++ b/P5/Source/Specs/xenoData.xml @@ -11,6 +11,7 @@ + From 530d098be978e3cdcf06de0c41983420973dee8f Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Thu, 16 May 2024 19:15:14 -0400 Subject: [PATCH 062/127] Fixed typo --- P5/Source/Guidelines/en/SA-LinkingSegmentationAlignment.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/P5/Source/Guidelines/en/SA-LinkingSegmentationAlignment.xml b/P5/Source/Guidelines/en/SA-LinkingSegmentationAlignment.xml index 3d8e462b99..0a4efbe554 100644 --- a/P5/Source/Guidelines/en/SA-LinkingSegmentationAlignment.xml +++ b/P5/Source/Guidelines/en/SA-LinkingSegmentationAlignment.xml @@ -3289,7 +3289,7 @@ will only select the text of the poem, with no markup inside.

standOff is largely the same as the metadata that describes the associated resource (e.g., the transcribed text in text), then the standOff and the encoded associated resource may appear as children of the same TEI element. The example below - has a transcription with placename elements in the text linked to a list of place elements in the + has a transcription with placeName elements in the text linked to a list of place elements in the standOff section. From 87e5ad1c8431dafb330b8597e004158a20d42c8e Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Fri, 17 May 2024 10:25:24 -0400 Subject: [PATCH 063/127] Add quote element to model.biblPart per #544. --- P5/Source/Specs/quote.xml | 18 +++++++----------- 1 file changed, 7 insertions(+), 11 deletions(-) diff --git a/P5/Source/Specs/quote.xml b/P5/Source/Specs/quote.xml index 4efc5359d8..e19387dbb9 100644 --- a/P5/Source/Specs/quote.xml +++ b/P5/Source/Specs/quote.xml @@ -8,21 +8,17 @@ citation cita citazione - contains a phrase or passage attributed by the narrator or author to some agency external - to the text. - 해설자 또는 저자에 의해, 텍스트의 외부 주체에 의해 생성된 것이라 밝혀진 구 또는 단락을 - 포함한다. + contains a phrase or passage attributed by the narrator or author to some agency external to the text. + 해설자 또는 저자에 의해, 텍스트의 외부 주체에 의해 생성된 것이라 밝혀진 구 또는 단락을 포함한다. 包含敘述者或作者引用自文本以外來源的字 (句) 詞或段落。 語り手や著者が、当該テキスト外にあるものに向けた、一節を示す。 - contient une expression ou un passage que le - narrateur ou l'auteur attribue à une origine extérieure au texte. - contiene una frase o pasaje atribuido por el narrador o - autor a un agente externo al texto. - contiene una frase o un brano attribuito dall'autore o - dal narratore a soggetti esterni al testo + contient une expression ou un passage que le narrateur ou l'auteur attribue à une origine extérieure au texte. + contiene una frase o pasaje atribuido por el narrador o autor a un agente externo al texto. + contiene una frase o un brano attribuito dall'autore o dal narratore a soggetti esterni al testo + @@ -69,4 +65,4 @@ - \ No newline at end of file + From a28ca43bddab141150e93fd55c8d8b68a130f5ae Mon Sep 17 00:00:00 2001 From: GusRiva Date: Fri, 17 May 2024 17:05:31 +0200 Subject: [PATCH 064/127] Added att.indentation and indentLevel --- .../en/CMC-ComputerMediatedCommunication.xml | 3 +- P5/Source/Guidelines/en/ST-Infrastructure.xml | 1 + P5/Source/Specs/att.indentation.xml | 37 +++++++++++++++++++ P5/Source/Specs/post.xml | 14 +------ 4 files changed, 41 insertions(+), 14 deletions(-) create mode 100644 P5/Source/Specs/att.indentation.xml diff --git a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml index b3321bea2f..91f344aa41 100644 --- a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml +++ b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml @@ -197,7 +197,8 @@ See the file COPYING.txt for details. Attributes specific to CMC post

Three attributes pertain specifically to post: - + + The type of the content of a post (i.e., whether the content is written, an image, a video clip, etc.) is indicated by the child elements of the post. (E.g., a diff --git a/P5/Source/Guidelines/en/ST-Infrastructure.xml b/P5/Source/Guidelines/en/ST-Infrastructure.xml index 5ddc207958..be280599f1 100644 --- a/P5/Source/Guidelines/en/ST-Infrastructure.xml +++ b/P5/Source/Guidelines/en/ST-Infrastructure.xml @@ -903,6 +903,7 @@ one, or vice versa, should be done with care.

+ diff --git a/P5/Source/Specs/att.indentation.xml b/P5/Source/Specs/att.indentation.xml new file mode 100644 index 0000000000..b466e8c9f0 --- /dev/null +++ b/P5/Source/Specs/att.indentation.xml @@ -0,0 +1,37 @@ + + + + + provides attributes for describing the indentation of a textual + element on the source page or object. + proporciona atributos para + describir el sangrado de un elemento textual en la página fuente o en un objeto. + stellt Attribute zur Beschreibung der Einrückung eines Textelements + in der Quelle oder im Objekt bereit. + + + + specifies the level of indentation of an item using a numeric value. + + + + + + +

Wie du siehst hab ich die Lemma geändert, danke für den Hinweis, ich war nämlich selbst auch etwas unsicher bei der ganzen Sache und bin jetzt damit auch viel glücklicher!--

+ + + + + + +

This attribute can be used to mark the level of indentation of a post in a thread-like structure (as defined by its author and in relation to the standard level of indentation which should be encoded with 0). This is commonly used for Wiki talk pages, but should also be used for genres such as webblog comments when the source was HTML.

+ + + + + + + diff --git a/P5/Source/Specs/post.xml b/P5/Source/Specs/post.xml index cc0f5801a7..dc0c54fe02 100644 --- a/P5/Source/Specs/post.xml +++ b/P5/Source/Specs/post.xml @@ -20,6 +20,7 @@ See the file COPYING.txt for details. + @@ -70,19 +71,6 @@ See the file COPYING.txt for details. - - marks the level of indentation of the - current post in a thread-like structure (as defined by its author and in relation to - the standard level of indentation which should be encoded as indentLevel="0"). - Basically used for Wiki talk pages, but may and should also be used for genres such - as webblog comments when the source was HTML. - - - - - -

standard user postings in chat

From de63dc472d0e7bc802fbcd9fa0b9c412fbae6ba4 Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Fri, 17 May 2024 11:21:05 -0400 Subject: [PATCH 065/127] Remove etraneous "choiceSize" constraint from simplePrint --- P5/Exemplars/tei_simplePrint.odd | 9 --------- 1 file changed, 9 deletions(-) diff --git a/P5/Exemplars/tei_simplePrint.odd b/P5/Exemplars/tei_simplePrint.odd index 7dd26e0d14..3fcf287a9c 100644 --- a/P5/Exemplars/tei_simplePrint.odd +++ b/P5/Exemplars/tei_simplePrint.odd @@ -4118,15 +4118,6 @@ live without God in the world, and only mind earthly things. - - - - - Element "" must have at least two child elements. - - - - From 9f52fe431d66e3ecefcfec5b850d3c3e0321fc5f Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Fri, 17 May 2024 13:08:41 -0400 Subject: [PATCH 066/127] Add post element to att.fragmentable per 2024-04-27 discussion --- P5/Source/Specs/post.xml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/P5/Source/Specs/post.xml b/P5/Source/Specs/post.xml index dc0c54fe02..8cf46cec7b 100644 --- a/P5/Source/Specs/post.xml +++ b/P5/Source/Specs/post.xml @@ -14,13 +14,14 @@ See the file COPYING.txt for details. + - + - + From 31f496f6053bb06fd5fc519875505f73d30f6d8e Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Fri, 17 May 2024 16:45:39 -0400 Subject: [PATCH 067/127] Rewrite of prose around Circulation xmp --- .../en/CMC-ComputerMediatedCommunication.xml | 104 +++++++++--------- 1 file changed, 55 insertions(+), 49 deletions(-) diff --git a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml index 91f344aa41..b441b09905 100644 --- a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml +++ b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml @@ -1057,56 +1057,62 @@ See the file COPYING.txt for details.
Circulation -

The following recommendations on how to encode features of the circulation of posts, such - as IDs, re-posts (retweets), hashtags, and mentions use twitter posts (tweets) as an - example; this phenomenon is not in any way unique to X (Twitter), however.

-

- - - Ich mich auch? #dynamicduo - #wirkümmernunsauchumIhrenEmpfang - #bcrn18 - #wikidach - - - Immer wieder gerne. Kann ich mich schon für - nächstes Jahr als Empfangs- #Engel für das nächste - BarCamp bewerben 🤪 - #bcrn18 - - - - - - - - - In the preceding example, we first encode the type of post (in this case, a tweet) - in the type attribute, and if it is a specific subtype of tweet, that will be - encoded in a subtype attribute of the post element accordingly.

-

Second, the original tweet-ID as supplied by X (Twitter) is contained in the value of the - global attribute xml:id.

-

Third, a retweet and its corresponding retweeted tweet are encoded as two separate posts - each with its own set of attributes. The post representing the retweet itself does not - contain or duplicate the content of the retweeted tweet. Instead it refers to the ID of the - retweeted tweet via a ptr in the post content. All original - content of the retweet goes in the content of the post element as well.

-

Fourth, hashtags occur in the body of tweets and are links like any other hyperlink and - should be encoded using the element ref. The type attribute of the ref - should contain the value hashtag, the target attribute should contain - the URL of the hashtag, and the content of refshould be the string of the hashtag - itself.

+

The following recommendations on how to encode features of + the circulation of posts, such as IDs, re-posts (retweets), + hashtags, and mentions use X (Twitter) posts (tweets) as an + example; this phenomenon is not in any way unique to X + (Twitter), however.

+

In the following example, the type of post (in this case, a + tweet) is recorded using the type attribute of + post. If it were useful to record a particular + sub-catagorization of tweet, the subtype attribute + could also be used. Furthermore, the original unique identifer + of the tweet as supplied by X (Twitter) is recorded as part of + the value of the xml:id attribute of the + post.

+

Also in the following example a retweet and its corresponding + retweeted tweet are encoded as two separate posts each with its + own set of attributes. The post representing the retweet itself + does not contain or duplicate the content of the retweeted + tweet. Instead it refers to the ID of the retweeted tweet via a + ptr in the post content. All original content of the + retweet goes in the content of the post element as + well. In addition, the hashtags found in the body of the source + tweets have been encoded using ref elements (with a + type of hashtag), as they are links like + any other hyperlink.

+ + + Ich mich auch? #dynamicduo + #wirkümmernunsauchumIhrenEmpfang + #bcrn18 + #wikidach + + + Immer wieder gerne. Kann ich mich schon für + nächstes Jahr als Empfangs- #Engel für das nächste + BarCamp bewerben 🤪 + #bcrn18 + + + + + + + + +

Note that in the above example CoMeRe style (cf. ) encoding is used to represent the number of favorites. It would - also be reasonable to use a TEI measure element instead of the fs.

+ target="#BIB_CoMeRe"/>) encoding is used to represent the number of favorites. It would + also be reasonable to use a TEI measure element instead of the fs.

Linguistic Annotation From 58842bd722c867f4b1f351447b5f67f3a7fbd7a6 Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Fri, 17 May 2024 17:41:23 -0400 Subject: [PATCH 068/127] =?UTF-8?q?Rewrite=20of=20prose=20around=20?= =?UTF-8?q?=E2=80=9CPosts=20with=20Graphics=E2=80=9D=20xmps?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .../en/CMC-ComputerMediatedCommunication.xml | 27 ++++++++++++------- 1 file changed, 17 insertions(+), 10 deletions(-) diff --git a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml index b441b09905..86109107c4 100644 --- a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml +++ b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml @@ -1029,8 +1029,14 @@ See the file COPYING.txt for details.

A post in a CMC interaction may contain a graphic in addition to some text or even contain only a graphic (without any text). As explained in , the modality of such a post should be considered as written. To encode the graphic - information, the TEI element figure may be used in the appropriate place. + information, the figure element may be used at the appropriate place.

+

In the following example a private chat post that contained + only a screenshot of a google search result for a hairdresser + is encoded as a post with a child figure. A + link to the graphic file itself is not included presumably + because this is a text-only corpus that does not include + images. +

screenshot of the google search for hairdresser "Pasha's Haare'm" with the @@ -1038,10 +1044,12 @@ See the file COPYING.txt for details. opening hours.
- The preceding example represents an encoding of a private chat post that contained - only a screenshot of a google search result for a hairdresser. A link to the graphic file - itself is not included because this is a text-only corpus that did not include images.

-

+ +

+

The following is an example of the encoding of a tweet which + contains both text (including hashtags and mentions) and a + graphic. The graphic element retains the URL of the + graphic on the web just as in the source. @@ -1051,10 +1059,9 @@ See the file COPYING.txt for details.

- The preceding example represents an encoding of a tweet that contains some text - (including hashtags and mentions) and a graphic. The graphic element retains the - URL of the graphic on the web just as in the source.

-
+ +

+
Circulation

The following recommendations on how to encode features of From f0e7d1e269f0800afa9814ff95867720900bdac3 Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Fri, 17 May 2024 18:41:46 -0400 Subject: [PATCH 069/127] Fix ellipses --- P5/Source/Specs/att.cmc.xml | 4 +--- P5/Source/Specs/post.xml | 12 ++++++------ 2 files changed, 7 insertions(+), 9 deletions(-) diff --git a/P5/Source/Specs/att.cmc.xml b/P5/Source/Specs/att.cmc.xml index 0784fad43d..d1aa98ec1a 100644 --- a/P5/Source/Specs/att.cmc.xml +++ b/P5/Source/Specs/att.cmc.xml @@ -121,9 +121,7 @@ See the file COPYING.txt for details. Am 03.04.2015 um 09:46 schrieb [_NAME_]: - - - + ... diff --git a/P5/Source/Specs/post.xml b/P5/Source/Specs/post.xml index 8cf46cec7b..ae9c09778d 100644 --- a/P5/Source/Specs/post.xml +++ b/P5/Source/Specs/post.xml @@ -91,9 +91,9 @@ See the file COPYING.txt for details. system - + - +

Interseb betritt den Raum.

@@ -117,17 +117,17 @@ See the file COPYING.txt for details.

*schwank* - + *seekrank*

- +

*lol* [...]

+ >* ...

- +

* Date: Fri, 17 May 2024 21:52:49 -0400 Subject: [PATCH 070/127] Various minor tweaks based on reviews in #2537 --- .../en/CMC-ComputerMediatedCommunication.xml | 71 +++++++++++-------- P5/Source/Specs/att.cmc.xml | 11 ++- P5/Source/Specs/post.xml | 9 +-- 3 files changed, 50 insertions(+), 41 deletions(-) diff --git a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml index 86109107c4..51dc86904c 100644 --- a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml +++ b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml @@ -52,8 +52,8 @@ See the file COPYING.txt for details. Basic Units of CMC

This section describes the encoding mechanisms for the basic units of CMC and for their combined use to encode CMC data.

-

We refer to units which are produced by an interlocutor to contribute to an ongoing CMC - interaction or joint CMC activity as basic CMC units. Contributions +

We refer to units which are produced by an interlocutor to initiate or contribute to an ongoing + CMC interaction or joint CMC activity as basic CMC units. Contributions to an ongoing interaction are produced to perform a move as part of the further development of the interactional sequence, for instance in chats or forum discussions. Contributions to joint CMC activities may not all be directly interactional; some may be part of a collaborative @@ -65,14 +65,15 @@ See the file COPYING.txt for details. of how these contributions are produced by their creators, transmitted via CMC systems, and made accessible for the recipients; (ii) whether the unit as a whole is realised in a verbal or nonverbal mode; (iii) for verbal units: whether the unit is realised in the written or - spoken mode. A taxonomy of basic CMC units resulting from these criteria is given in Fig. + spoken mode. A taxonomy of basic CMC units resulting from these criteria is given in .

Taxonomy of basic CMC units according to
-

The most important distinction in the taxonomy +

The most important distinction in the CMC taxonomy concerns the temporal nature of units exchanged via CMC technologies. The left part of the taxonomy describes units that are performed (by a producer) and perceived (by a recipient) as a continuous stream of behaviour. Units of this type can be performed as

@@ -159,12 +160,15 @@ See the file COPYING.txt for details. CMC module.

CMC Posts -

The element post is unique to computer-mediated communication (CMC). - - A post is defined as a written (or spoken) contribution to an ongoing CMC - interaction which has been composed (or recorded) by its author in its entirety as part of a - private activity, transmitted through the internet, and made available on the monitor or - screen of the other parties en bloc. Posts occur in a broad range of written CMC genres, +

While the concept of a post is not unique to + computer-mediated communication (ask anyone who has posted a + lost cat sign in the local market), this chapter concerns + itself only with postings within a framework of a CMC system. + Thus the element post is unique to the encoding of + computer-mediated communication (CMC). + + + Posts occur in a broad range of written CMC genres, including (but not limited to) messages in chats and WhatsApp dialogues, tweets in X (Twitter) timelines, comments on Facebook pages, posts in forum threads, and comments or contributions to discussions on Wikipedia talk pages or in the comment sections of @@ -206,7 +210,7 @@ See the file COPYING.txt for details. graphic, or a child figure with a media, or some combination thereof.) How that content was created — in particular whether it was recorded speech or not — may be described with the modality attribute. Because spoken language differs - significantly from written language the suggested values only separate written + significantly from written language, the suggested values only separate written modality — which covers all cases other than spoken natural language — from spoken. The use of modality is recommended but not required. @@ -317,25 +321,27 @@ See the file COPYING.txt for details. If you make a change here, make it in the att.cmc.xml file, as well! --> -

A list of suggested values for generatedBy follows: +

A list of suggested values for generatedBy follows: + - when then content of the respective element was naturally typed or spoken by + when the content of the respective element was naturally typed or spoken by a human user (cf. the chat posts in Example haircut) when the content of the respective element was generated after a human user - activated a template for its insertion (cf. signed and time i.e. the - signature in wiki talk in the second example below. + activated a template for its insertion + (often applicable to signed and time; e.g. see the + signature in wiki talk in the second example below) when the content of the respective element was generated by the system, i.e. the CMC - environment (cf. the system message in an IRC chat in the fourth example below. + environment (see, e.g., the system message in an IRC chat in the fourth example below) when the content of the respective element was generated by a bot i.e. a non-human - agent, mostly external to the CMC environment + agent, typically one that is not part of the CMC environment itself when it is unspecified or unknown how the content of the respective element was - generated (cf. the retweet that forms the second post in the third example - below). + generated (see, e.g. the retweet that forms the second post in the third example + below).

@@ -405,15 +411,16 @@ See the file COPYING.txt for details.
CMC Macrostructure -

In many CMC genres, posts come in a CMC document according to +

In many CMC genres, posts occur in a CMC document according to which they are displayed, e.g. in a sequence or in threads; posts within the document may be grouped. For example, in chat communication such as WhatsApp, posts are part of a chat of one user with another user or among a + group of users. When an entire chat is saved, typically a logfile of the - chat is obtained from the CMC system and downloaded. Similarly, Wikipedia discussions come in + chat is obtained from the CMC system and downloaded. Similarly, Wikipedia discussions occur on a talk page, which ultimately is a web page containing the user posts, - sub-structured in threads. Likewise, YouTube comments come in a webpage containing the YouTube + sub-structured in threads. Likewise, YouTube comments occur on a webpage containing the YouTube video along with comment posts and posts replying to those comments displayed below the video. The video serves as a prompt for the whole discussion. In forum discussions, the prompt may be a news item, and in Wikipedia, an article may be viewed as the prompt for the @@ -503,8 +510,8 @@ See the file COPYING.txt for details.

...
- ... - ... + ... + ...
@@ -536,7 +543,7 @@ See the file COPYING.txt for details.
Multimodal CMC

As explained in section , the elements post, u, - kinesic, and incident are available to to encode textual transcriptions + kinesic, and incident are available to encode textual transcriptions of written posts, spoken turns, bodily activities of avatars, and onscreen activity by users that occur in CMC data; and, as discussed in section , graphics or other media data within posts are encoded in a post with @@ -619,8 +626,8 @@ See the file COPYING.txt for details. location, the URL of the server where the CMC data were collected from, or the filename of a database dump that was used as a source. Metadata about the project responsible for collecting the data and building the corpus, if applicable, should be recorded as well.

-

The following example shows the sourceDesc of a Twitter corpus. +

The following example shows the sourceDesc of a Twitter corpus. + @@ -635,13 +642,15 @@ See the file COPYING.txt for details. D02 AX07 Ireland + +

The following example shows how a Wikipedia database dump may be encoded as the source. - + @@ -844,7 +853,7 @@ See the file COPYING.txt for details.

Timeline

From most CMC environments, user posts come provided with a timestamp marking the time - (often down to the the second) when the post arrived and was registered at the CMC server. + (often down to the second) when the post arrived and was registered at the CMC server. In the display of chat interactions, for instance, the time is automatically added by the system and usually precedes or follows the actual content of the post. In Wikipedia talk, a timestamp is automatically added when the user inserts his or her signature. A timestamp in @@ -966,7 +975,7 @@ See the file COPYING.txt for details. intended use other than as part of an emoticon.

Both emoticons and emojis may be simply transcribed as a sequence of characters. As with any other characters, they may be entered as numeric character entities if this is more - convenient. (E.g., ❤; might be transcribed as + convenient. (E.g., ❤ might be transcribed as &#x2764; in any XML document, including a TEI document; see .)

When the text of a post is being tokenized, e.g. for linguistic analysis, it may be useful @@ -1247,7 +1256,7 @@ See the file COPYING.txt for details.

-

In the the following version of the same chat snippet, the text strings with the nicknames +

In the following version of the same chat snippet, the text strings with the nicknames have been replaced by category label strings for the purpose of anonymisation. - the content was - generated by a bot, i.e. a non-human agent, typically external - to the CMC environment. + the content was + generated by a bot, i.e. a non-human agent, typically one + that is not part of the CMC environment itself - the content of - the respective element was generated by an unknown or - unspecified process. + the content was + generated by an unknown or unspecified process diff --git a/P5/Source/Specs/post.xml b/P5/Source/Specs/post.xml index ae9c09778d..cc8b40f990 100644 --- a/P5/Source/Specs/post.xml +++ b/P5/Source/Specs/post.xml @@ -6,10 +6,11 @@ See the file COPYING.txt for details. --> - a written (or spoken) contribution to an ongoing - CMC interaction which has been composed (or recorded) by its author in its entirety as part - of a private activity, and has been transmitted through the internet and is made available - on the monitor or screen of the other parties en bloc. + a written (or spoken) + contribution to a CMC interaction which has been composed + (or recorded) by its author in its entirety before being + transmitted over a network (e.g., the internet) and made available + on the monitor or screen of the other parties en bloc. From 8b4a9eeb1fa696be1939db37d65428c7cec7b0d5 Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Sun, 19 May 2024 13:50:32 -0400 Subject: [PATCH 071/127] Remove extraneous comma from wihin examples of geo element, thus addressing #2560. --- P5/Source/Guidelines/en/ND-NamesDates.xml | 12 ++++++------ P5/Source/Specs/eventName.xml | 2 +- P5/Source/Specs/object.xml | 2 +- 3 files changed, 8 insertions(+), 8 deletions(-) diff --git a/P5/Source/Guidelines/en/ND-NamesDates.xml b/P5/Source/Guidelines/en/ND-NamesDates.xml index eff14c5bed..24b0854cc2 100644 --- a/P5/Source/Guidelines/en/ND-NamesDates.xml +++ b/P5/Source/Guidelines/en/ND-NamesDates.xml @@ -879,7 +879,7 @@ target="#CONA"/>). The tag -->The Rome - 41.891775, 12.486137 + 41.891775 12.486137 423025 capital of the Roman Empire @@ -2206,7 +2206,7 @@ occupation and residence.

Gare de Saint-Nazaire - 47.28657,-2.21171 + 47.28657 -2.21171 @@ -2234,7 +2234,7 @@ occupation and residence.

Arnsberg Hochsauerlandkreis Schmallenberg - 51.154,8.357 + 51.154 8.357 @@ -2254,7 +2254,7 @@ occupation and residence.

Sebnitz - 50.966667,14.283333 + 50.966667 14.283333 @@ -2439,7 +2439,7 @@ occupation and residence.

Cairo Egypt - 30.047778, 31.233333 + 30.047778 31.233333 @@ -2470,7 +2470,7 @@ occupation and residence.

Cairo Egypt - 30.047778, 31.233333 + 30.047778 31.233333 diff --git a/P5/Source/Specs/eventName.xml b/P5/Source/Specs/eventName.xml index 16a33b74f2..e5b516e6ac 100644 --- a/P5/Source/Specs/eventName.xml +++ b/P5/Source/Specs/eventName.xml @@ -33,7 +33,7 @@ Gdańsk - 54.350556, 18.652778 + 54.350556 18.652778 diff --git a/P5/Source/Specs/object.xml b/P5/Source/Specs/object.xml index 9fea6e1389..710c0f8ed4 100644 --- a/P5/Source/Specs/object.xml +++ b/P5/Source/Specs/object.xml @@ -105,7 +105,7 @@ Cairo Egypt - 30.047778, 31.233333 + 30.047778 31.233333 From e1673c3cf46df3f3dcf25e29aade5113622e7cec Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Tue, 21 May 2024 22:40:15 -0400 Subject: [PATCH 072/127] Improved wording per PR comments --- P5/Source/Guidelines/en/HD-Header.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/P5/Source/Guidelines/en/HD-Header.xml b/P5/Source/Guidelines/en/HD-Header.xml index f9d5ed5657..d60c17254d 100644 --- a/P5/Source/Guidelines/en/HD-Header.xml +++ b/P5/Source/Guidelines/en/HD-Header.xml @@ -2521,9 +2521,9 @@ during validation of the file against a TEI schema. The the fileDesc but before the optional revisionDesc, is provided for this purpose. Where the use of xenoData is primarily to store linked data, contextual information, or stand-off annotations -that refer to the contents of the TEI file itself, -then it is also possible to place xenoData inside the standOff -element. +that refer to the contents of the TEI file itself, the +xenoData element may be placed inside the standOff +element instead.

From f79ba7c3e917c2c67be00d80284956c6031ba604 Mon Sep 17 00:00:00 2001 From: Klaus Rettinghaus Date: Wed, 5 Jun 2024 16:18:58 +0200 Subject: [PATCH 073/127] ci: update used actions --- .github/workflows/generate-spec-lists.yml | 4 ++-- .github/workflows/test.yml | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/.github/workflows/generate-spec-lists.yml b/.github/workflows/generate-spec-lists.yml index db069cce3f..d7a18acfc1 100644 --- a/.github/workflows/generate-spec-lists.yml +++ b/.github/workflows/generate-spec-lists.yml @@ -11,13 +11,13 @@ jobs: contents: write steps: - name: Checkout TEI Repository - uses: actions/checkout@v3 + uses: actions/checkout@v4 - name: Generate JSON Spec list uses: ./.github/actions/generate-spec-lists - name: Auto-commit Spec list - uses: stefanzweifel/git-auto-commit-action@v4 + uses: stefanzweifel/git-auto-commit-action@v5 with: commit_user_name: ${{ github.actor }} commit_message: Re-generated spec lists. diff --git a/.github/workflows/test.yml b/.github/workflows/test.yml index 0cbd6e1456..ff4eb544af 100644 --- a/.github/workflows/test.yml +++ b/.github/workflows/test.yml @@ -17,10 +17,10 @@ jobs: steps: - name: Checkout Guidelines repo - uses: actions/checkout@v3 + uses: actions/checkout@v4 - name: Checkout Stylesheets repo - uses: actions/checkout@v3 + uses: actions/checkout@v4 with: repository: TEIC/Stylesheets ref: dev From 8f114c3fb0f80011c35ab3fc8222ccf429fdf26c Mon Sep 17 00:00:00 2001 From: Klaus Rettinghaus Date: Wed, 5 Jun 2024 16:55:05 +0200 Subject: [PATCH 074/127] add German gloss --- P5/Source/Specs/unclear.xml | 1 + 1 file changed, 1 insertion(+) diff --git a/P5/Source/Specs/unclear.xml b/P5/Source/Specs/unclear.xml index 4fcf4d47bb..8d55ac0f31 100644 --- a/P5/Source/Specs/unclear.xml +++ b/P5/Source/Specs/unclear.xml @@ -5,6 +5,7 @@ unclear poco claro incertain + unklar contains a word, phrase, or passage which cannot be transcribed with certainty because it is illegible or inaudible in the source. 원본에서 읽거나 듣기 어려워서 분명하게 전사할 수 없는 단어, 구, 단락들을 포함한다. From 416cc9a007679580d79634184112bb679ca7032b Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Fri, 21 Jun 2024 12:48:47 -0400 Subject: [PATCH 075/127] Add required elements to example --- .../Guidelines/en/CMC-ComputerMediatedCommunication.xml | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml index 51dc86904c..223eb50e40 100644 --- a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml +++ b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml @@ -919,6 +919,11 @@ See the file COPYING.txt for details. + + + + + From 175133ff4e7708475eea2deb4264422f897ed0c8 Mon Sep 17 00:00:00 2001 From: helenasabel Date: Sun, 30 Jun 2024 14:46:19 +0200 Subject: [PATCH 076/127] minor tweaks raised in PR thread --- P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml | 4 ++-- P5/Source/Specs/post.xml | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml index 223eb50e40..11de560573 100644 --- a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml +++ b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml @@ -94,7 +94,7 @@ See the file COPYING.txt for details.

The right part of the taxonomy describes units in which the production, transmission, and perception of contributions to CMC interactions are organised in a strictly consecutive order: The content — verbal, nonverbal, or multimodal — of - the contribution has to be produced before it can be transmitted via the internet and made + the contribution has to be produced before it can be transmitted through a network and made available on the computer monitor or mobile screen of any other party as a preserved and persistent unit. We term this type of unit a post. Posts occur in two different variants: @@ -626,7 +626,7 @@ See the file COPYING.txt for details. location, the URL of the server where the CMC data were collected from, or the filename of a database dump that was used as a source. Metadata about the project responsible for collecting the data and building the corpus, if applicable, should be recorded as well.

-

The following example shows the sourceDesc of a Twitter corpus. +

The following example shows the sourceDesc of a X (Twitter) corpus. diff --git a/P5/Source/Specs/post.xml b/P5/Source/Specs/post.xml index cc8b40f990..05f6b00d2c 100644 --- a/P5/Source/Specs/post.xml +++ b/P5/Source/Specs/post.xml @@ -50,7 +50,7 @@ See the file COPYING.txt for details. for stretches of text and/or multimodal elements - for audio posts + for audio (or audio-visual) posts From a63375711dddd341dd337a415d0671f33d5f5f3e Mon Sep 17 00:00:00 2001 From: ebeshero Date: Sun, 30 Jun 2024 19:01:55 -0400 Subject: [PATCH 077/127] revisions to CMC intro section --- .../en/CMC-ComputerMediatedCommunication.xml | 54 +++++++++---------- 1 file changed, 26 insertions(+), 28 deletions(-) diff --git a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml index 11de560573..de534be3fb 100644 --- a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml +++ b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml @@ -7,46 +7,44 @@ See the file COPYING.txt for details.

Computer-mediated Communication -

This chapter describes the TEI encoding mechanisms available for textual data which represents +

This chapter describes the TEI encoding mechanisms available for textual data that represents discourse from genres of computer-mediated communication (CMC). It is intended to provide the basic framework needed to encode CMC corpora.

-
- General Considerations and Overview -

While the term computer-mediated communication, in a broader sense, might be used to - describe all sorts of communications between humans which are mediated by digital technologies - (for example, text on web pages, dialogic written interaction in chats and forums, the spoken - language in internet video meetings), herein we use the term to apply to forms of - communication which share the following features: - they are dialogic; - they are organized in the form of interactional sequences so that each communicative +

+ General Considerations +

While the term computer-mediated communication might be used broadly to + describe all kinds of communications that are mediated by digital technologies + (such as text on web pages, written interactions in chats and forums, the spoken + conversations in internet video meetings), for the purposes of these Guidelines we use the term to apply to forms of + communication that share the following features: + they are dialogic; + they are organized as interactional sequences so that each communicative move may determine the context for subsequent moves (typically taken by another interlocutor) and may react to the context created by a prior move; - the communicative moves which may be put into practice as posts (cf. ), utterances, onscreen activities, or bodily activities exerted - by a virtual avatar are created and displayed using computer - technology (keyboard, mouse, speech-to-text conversion software, monitor or - screen) and transmitted over a computer network (typically the + they are created and displayed using computer + technology (keyboard, mouse, speech-to-text conversion software, monitor or + screen) and transmitted over a computer network (typically the internet). + Such communications may be expressed as posts (cf. ), utterances, onscreen activities, or bodily activities exerted + by a virtual avatar.

-

Computer-mediated communication is conducted using - communication technologies such as chats, messengers, or online forums; - social media platforms and applications such as X (the platform formerly known as - Twitter), Facebook, Instagram, or WhatsApp; +

The following technologies may support CMC: + chats, messengers, or online forums; + social media platforms and applications the communication functions of collaborative platforms and projects (e.g. an online - learning environment, or a Wikipedia talk page); - 3D environments (e.g. Second Life or gaming environments); - or similar technologies and services on the internet. + learning environment, or a talk page); + 3D virtual world environments; + other interactive services supported by the internet.

-

CMC is, by default, multimodal. Whereas early CMC systems +

CMC supports multimodal expression combining text, images, sound. Whereas early CMC systems (e.g. Internet Relay Chat, IRC for short, the Usenet newsgroups, or even the Unix talk system) - were completely ASCII-based, the lion’s share of contemporary CMC technologies and - applications allow for the combination of different semiotic resources (e.g. written or spoken - language with graphic icons and images) and even for the combined use of different CMC - technologies on one platform (e.g. combined use of an audio connection, a chat system, and a + were completely ASCII-based, most CMC applications now permit combining media formats (e.g. written or spoken + language with graphic icons and images) and mixing communication technologies on one platform (e.g. combined use of an audio connection, a chat system, and a 3D interface in which users control a virtual avatar as in many multiplayer online computer - games or in virtual worlds such as Second Life).

+ games or in virtual worlds).

Basic Units of CMC From 5bdda679adcae9954d01398bcfc2bb0483ea70ff Mon Sep 17 00:00:00 2001 From: ebeshero Date: Sun, 30 Jun 2024 21:39:15 -0400 Subject: [PATCH 078/127] edits to regularize use of term and list parallelism --- .../en/CMC-ComputerMediatedCommunication.xml | 54 +++++++++---------- 1 file changed, 27 insertions(+), 27 deletions(-) diff --git a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml index de534be3fb..a4e4545618 100644 --- a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml +++ b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml @@ -12,9 +12,9 @@ See the file COPYING.txt for details. basic framework needed to encode CMC corpora.

General Considerations -

While the term computer-mediated communication might be used broadly to +

While the term computer-mediated communication might be used broadly to describe all kinds of communications that are mediated by digital technologies - (such as text on web pages, written interactions in chats and forums, the spoken + (such as text on web pages, written exchanges in chats and forums, interactions with artificial intelligence systems, the spoken conversations in internet video meetings), for the purposes of these Guidelines we use the term to apply to forms of communication that share the following features: they are dialogic; @@ -30,9 +30,9 @@ See the file COPYING.txt for details. target="#CMCcmcpost"/>), utterances, onscreen activities, or bodily activities exerted by a virtual avatar.

-

The following technologies may support CMC: +

The following kinds of platforms support CMC: chats, messengers, or online forums; - social media platforms and applications + social media platforms and applications; the communication functions of collaborative platforms and projects (e.g. an online learning environment, or a talk page); 3D virtual world environments; @@ -50,21 +50,25 @@ See the file COPYING.txt for details. Basic Units of CMC

This section describes the encoding mechanisms for the basic units of CMC and for their combined use to encode CMC data.

-

We refer to units which are produced by an interlocutor to initiate or contribute to an ongoing - CMC interaction or joint CMC activity as basic CMC units. Contributions - to an ongoing interaction are produced to perform a move as part of the further development of - the interactional sequence, for instance in chats or forum discussions. Contributions to joint +

We use the term basic CMC unit to refer to a communication produced by an interlocutor to initiate or contribute to an ongoing + CMC interaction or joint CMC activity. Contributions + to an ongoing interaction are produced to perform a move to develop + the interactional sequence, for instance to respond in chats or forum discussions. Contributions to joint CMC activities may not all be directly interactional; some may be part of a collaborative - project of the involved individuals. For example, editing activities in a shared text editor + project of the involved individuals. Such collaboration could involve editing activities in a shared text editor or whiteboard in parallel with an ongoing CMC interaction (chat, audio conversation, or audiovideo conference) in the same CMC environment in which these editing activities are - discussed by the collaborators.

-

Basic units of CMC can be described according to three criteria: (i) the temporal properties - of how these contributions are produced by their creators, transmitted via CMC systems, and - made accessible for the recipients; (ii) whether the unit as a whole is realised in a verbal - or nonverbal mode; (iii) for verbal units: whether the unit is realised in the written or - spoken mode. A taxonomy of basic CMC units resulting from these criteria is given in - . + discussed by the participants.

+

Basic units of CMC can be described according to three criteria: + + the temporal properties + of when these contributions are produced by their creators, transmitted via CMC systems, and + made accessible for the recipients; + the modality of the unit as a whole, whether verbal or noverbal; + for verbal units: whether the unit is expressed in the written or + spoken mode. + + A taxonomy of basic CMC units resulting from these criteria is given in the following figure.

@@ -80,11 +84,11 @@ See the file COPYING.txt for details. i.e. stretches of speech which are produced to perform a speaker turn in a conversation, - i.e. nonverbal behavior (gesture, gaze) produced to perform a speaker turn, either + i.e. nonverbal behavior (gesture, gaze) produced to perform a speaker turn, either performed by the real body of an interlocutor (e.g. in a video conference) or through the virtual avatar of an interlocutor in a 3D environment, - i.e. non-bodily forms of behaviour that are transmitted to the group of interacting or + i.e. non-bodily expressions that are transmitted to the group of interacting or coworking participants, for instance the editing of content in a shared text editor which can be perceived by the other parties simultaneously (as may be the case in learning or collaboration environments). @@ -94,7 +98,7 @@ See the file COPYING.txt for details. organised in a strictly consecutive order: The content — verbal, nonverbal, or multimodal — of the contribution has to be produced before it can be transmitted through a network and made available on the computer monitor or mobile screen of any other party as a preserved and - persistent unit. We term this type of unit a post. Posts occur in + persistent unit. We term this type of unit a post. Posts occur in two different variants: as written or multimodal posts, which are produced with an editor form that is designed for the composition of stretches of written text. Most @@ -105,7 +109,7 @@ See the file COPYING.txt for details. text-based CMC genres and applications such as chat, SMS, WhatsApp, Instagram, Facebook, X (Twitter), online forums, or Wikipedia talk pages. as audio posts, which are produced using a recording - function. In contrast to CMC units of the type utterance which + function. In contrast to CMC units of the type utterance which are produced and transmitted simultaneously, audio posts first have to be recorded as a whole and are then transmitted — as audio files — via the internet; the availability of the recording is indicated in the screen protocol by a template-generated, visual post; @@ -119,13 +123,11 @@ See the file COPYING.txt for details. CMC unit Type of corpus data - TEI P5 element utterance transcription of speech - ⇒ u @@ -133,7 +135,6 @@ See the file COPYING.txt for details. bodily activity textual description - ⇒ kinesic @@ -141,15 +142,14 @@ See the file COPYING.txt for details. onscreen activity textual description - ⇒ incident -

The u, kinesic, and incident elements are not specific to CMC, but - are nonetheless used to encode textual transcriptions of spoken turns, bodily activity, and - onscreen activity that occur in CMC data. The CMC unit post, which is specific to +

The u, kinesic, and incident elements are not limited to CMC, but + apply to encode textual transcriptions of spoken turns and CMC data about bodily activity and + onscreen activity. The CMC unit post, which is specific to CMC, is introduced in .

From 3a7c963795a907665996cd005eb90f40a86086af Mon Sep 17 00:00:00 2001 From: Elisa Beshero-Bondar Date: Sun, 30 Jun 2024 21:48:34 -0400 Subject: [PATCH 079/127] amending 'sloppy' to 'informal' re CMC writing MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Helena Bermúdez Sabel --- P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml index a4e4545618..982c8d0046 100644 --- a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml +++ b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml @@ -1157,7 +1157,7 @@ See the file COPYING.txt for details.

-

In many CMC genres, especially in private chat, sloppy and creative writing abound +

In many CMC genres, especially in private chat, informal writing abounds including irregular spellings imitating spoken language, omitted word boundaries, and spurious boundaries leading to tokens separated in parts. For encoding these writing phenomena typical of CMC, the TEI attributes norm and join may be From 7135b2564c326b466677f1b0876bbb5c61e4a08f Mon Sep 17 00:00:00 2001 From: Elisa Beshero-Bondar Date: Sun, 30 Jun 2024 21:51:14 -0400 Subject: [PATCH 080/127] amending quotes in attDef desc re #1955 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Helena Bermúdez Sabel --- P5/Source/Specs/post.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/P5/Source/Specs/post.xml b/P5/Source/Specs/post.xml index 05f6b00d2c..586e9a4bd8 100644 --- a/P5/Source/Specs/post.xml +++ b/P5/Source/Specs/post.xml @@ -62,7 +62,7 @@ See the file COPYING.txt for details. indicates to which previous post the current post replies or refers to. This attribute should be used to encode - "technical" reply information, i.e. which is due to a formal reply action (such as + technical reply information, i.e. which is due to a formal reply action (such as activating a "reply" button in the client software) and which is also formally represented in the source, e.g. in the "references" field of a Usenet message header or in the subject line of a forum post. It should rather not be used for inferred, From 7ca18f41bc4f8544b249cfff84478c1003bdb634 Mon Sep 17 00:00:00 2001 From: ebeshero Date: Sun, 30 Jun 2024 23:37:19 -0400 Subject: [PATCH 081/127] more consistency edits to CMC re #1955 --- .../en/CMC-ComputerMediatedCommunication.xml | 16 +++++++--------- P5/Source/Specs/post.xml | 11 +++++------ 2 files changed, 12 insertions(+), 15 deletions(-) diff --git a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml index 982c8d0046..5f5446854f 100644 --- a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml +++ b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml @@ -206,11 +206,9 @@ See the file COPYING.txt for details. image, a video clip, etc.) is indicated by the child elements of the post. (E.g., a post might have a child p, or a child figure with a graphic, or a child figure with a media, or some combination - thereof.) How that content was created — in particular whether it was recorded speech or not - — may be described with the modality attribute. Because spoken language differs - significantly from written language, the suggested values only separate written - modality — which covers all cases other than spoken natural language — from - spoken. The use of modality is recommended but not required. + thereof.) How that content was created—whether it was recorded speech or not—may be described with the modality attribute. Because spoken language differs + significantly from written language, the suggested values only separate the spoken modality from the written + modality, which covers all cases other than spoken natural language. The use of modality is recommended but not required.

@@ -260,14 +258,14 @@ See the file COPYING.txt for details.

In the CMC genre of Wiki talk, users insert their contribution to a discussion by modifying - the wiki page of the discussion — the talk page. Since there is no technical reply action + the wiki page of the discussion—the talk page. Since there is no technical reply action available in wiki software, users apply textual indentation in the wiki code to indicate a reply to a previous message, and a threaded structure is formed by a series of such indentations. The attribute indentLevel records the level of indentation, that is the nesting depth of the current post in such a thread-like structure (as defined by its author and in relation to the standard level of non-indentation which should be encoded with an indentLevel of 0). It is used in wiki talk corpora but may also be - used for other threaded genres, e.g. when HTML is used as a source.

+ used for other threaded genres, for example when HTML is used as a source.

The following is a sample encoding of a portion of a discussion among four different users on a Wikipedia talk page. @@ -305,12 +303,12 @@ See the file COPYING.txt for details. descendants, how the content transcribed in an element was generated in a CMC environment. That is, whether the source text being transcribed was created by a human user, created by the CMC system at the request of a human user (e.g., when the user activates a template that - generates the content, such as in a signature), outright generated by the CMC system (e.g. a + generates the content, such as in a signature), generated by the CMC system (e.g. a status message or a timestamp), or generated by an automated process external to the CMC system itself. This attribute is optional; when it is not specified on a post element its value is presumed to be unspecified; when it is unspecified on any descendant of post its value is inherited from the immediately enclosing element. - (And, in turn, if generatedBy is not specified on that element it inherits the + In turn, if generatedBy is not specified on that element it inherits the value from its immediately enclosing element, and so on up the document hierarchy until a post is reached; the post either has a generatedBy attribute specified or its presumed value is unspecified).

diff --git a/P5/Source/Specs/post.xml b/P5/Source/Specs/post.xml index 586e9a4bd8..2d79b8f5b0 100644 --- a/P5/Source/Specs/post.xml +++ b/P5/Source/Specs/post.xml @@ -62,12 +62,11 @@ See the file COPYING.txt for details. indicates to which previous post the current post replies or refers to. This attribute should be used to encode - technical reply information, i.e. which is due to a formal reply action (such as - activating a "reply" button in the client software) and which is also formally - represented in the source, e.g. in the "references" field of a Usenet message header - or in the subject line of a forum post. It should rather not be used for inferred, - or interpreted reply relations such as based on linguistic discourse markers, nor - for the indentation relations in Wiki talk pages. + technical reply information that is due to a formal reply action (such as + activating a reply button in the client software) and that is formally + represented in the source, e.g. in the references field of a Usenet message header + or in the subject line of a forum post. It should not be used for inferred, + or interpreted reply relations based only on ambiguous signs such as linguistic discourse markers or the indentation relations in Wiki talk pages. From 9407cd7f6a866ec8c7df720685569d12b39bbfc5 Mon Sep 17 00:00:00 2001 From: ebeshero Date: Sun, 30 Jun 2024 23:43:10 -0400 Subject: [PATCH 082/127] em dash consistency in cmc chapter re #1955 --- .../en/CMC-ComputerMediatedCommunication.xml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml index 5f5446854f..395683859b 100644 --- a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml +++ b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml @@ -95,7 +95,7 @@ See the file COPYING.txt for details.

The right part of the taxonomy describes units in which the production, transmission, and perception of contributions to CMC interactions are - organised in a strictly consecutive order: The content — verbal, nonverbal, or multimodal — of + organised in a strictly consecutive order: The content—verbal, nonverbal, or multimodal—of the contribution has to be produced before it can be transmitted through a network and made available on the computer monitor or mobile screen of any other party as a preserved and persistent unit. We term this type of unit a post. Posts occur in @@ -111,7 +111,7 @@ See the file COPYING.txt for details. as audio posts, which are produced using a recording function. In contrast to CMC units of the type utterance which are produced and transmitted simultaneously, audio posts first have to be recorded as a - whole and are then transmitted — as audio files — via the internet; the availability of + whole and are then transmitted, as audio files, via the internet; the availability of the recording is indicated in the screen protocol by a template-generated, visual post; the recipients can play the recording (repeatedly) by activating the play button displayed in the post on the screen. Examples of CMC applications that implement audio posts are @@ -247,12 +247,12 @@ See the file COPYING.txt for details. -

Stahlkunstruktionen dacht ich mal, was die bauen — oder bauen lassen.

+

Stahlkunstruktionen dacht ich mal, was die bauen—oder bauen lassen.

Das ist schon ein übles Ding. Die Ausschreibungenund Angebote sind unauffällig, aber wenn Unregelmässigkeiten auftreten (im Bauverlauf) dann gibt es die saftigen Rechnungen. Da steht dann der Bauherr da und fragt sich, wie er denn so schnell einen fähigen Ersatz herbekommt. Und diese Frage erübrigt sich meist, weil der Markt der - Baufirmen das nicht hergibt — weil tendenziel 100 % Auslastung. (und noch schlimmer: + Baufirmen das nicht hergibt—weil tendenziel 100 % Auslastung. (und noch schlimmer: Absprachen) Was auch Folge des Marktdrucks gewesen war.

@@ -840,8 +840,8 @@ See the file COPYING.txt for details. uL: could be used to map the value uL:06 to file:/userList.xml#cmc_user_06. See for more information on establishing prefix definitions.

-

This indirection — using a listPerson, particularly one in a separate file, to - store information about the users involved in a CMC interaction — is particularly useful +

This indirection—using a listPerson, particularly one in a separate file, to + store information about the users involved in a CMC interaction—is particularly useful when there is both a need to keep such information locally, and to remove it (e.g., to anonymize the data) when the data are published or shared with other researchers.

From 6e1edb0d985b4d78cc0c33bb894b65743069806b Mon Sep 17 00:00:00 2001 From: ebeshero Date: Mon, 1 Jul 2024 01:34:11 -0400 Subject: [PATCH 083/127] regularizing isation spellings to ization in conformance with TEI style guide, re #1955 --- .../en/CMC-ComputerMediatedCommunication.xml | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml index 395683859b..5c74584d5d 100644 --- a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml +++ b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml @@ -938,12 +938,12 @@ See the file COPYING.txt for details. Note that the synch attribute is provided by the module described in chapter .

Removing timestamps from the text body can help meet - requirements of text anonymisation. For instance, if the particDesc and the + requirements of text anonymization. For instance, if the particDesc and the timeline are stored in a separate file, the rest of the corpus can be distributed without this separate file. Thus the recipient of the corpus may know in what order posts were made (if the values of the synch are sequential), and will be able to group posts made by the same user, but will not have exact timestamps or actual user names, - thus providing a significant degree of anonymisation. + thus providing a significant degree of anonymization.

Those haven't happened. If they do, we can revisit the concern.

@@ -1135,7 +1135,7 @@ See the file COPYING.txt for details. Linguistic Annotation

For encoding linguistic analyses of CMC text, we may use the dedicated elements and attributes from the analysis module, which is described in . For example, - the tokenisation (segmentation into word-like units) of a CMC text should be encoded using + the tokenization (segmentation into word-like units) of a CMC text should be encoded using the w element.

Let us take, for example a posting that contains the content 00:22 Bin soooooo im stress gewesen ich Armer lol (in English: I was soooooo stressed out @@ -1233,7 +1233,7 @@ See the file COPYING.txt for details.

- Named Entities and Anonymisation + Named Entities and Anonymization

Named entities (NEs) may be marked up using name or the elements encoding different subcategories of names as described in such as surname or geogName, or rs for a general referencing string. In the following chat @@ -1258,7 +1258,7 @@ See the file COPYING.txt for details.

In the following version of the same chat snippet, the text strings with the nicknames - have been replaced by category label strings for the purpose of anonymisation. @@ -1283,14 +1283,14 @@ See the file COPYING.txt for details.

In the preceding example, pairs of a gap and a supplied element encode the fact that some substring has been removed and replaced with another string for - anonymisation purposes. Note that in this example, the name and the w + anonymization purposes. Note that in this example, the name and the w elements and their attributes also provide some categorical information about what has been - removed. Using gap and supplied to record the anonymisation is especially + removed. Using gap and supplied to record the anonymization is especially recommendable when the original name or referencing string has been pseudonymised, i.e. replaced by a different referencing string of the same ontological category (such as replacing the female name Konstanze by the female name Kornelia.). In - that case, the markup would be the only place where it can be seen that a pseudonymisation + that case, the markup would be the only place where it can be seen that a pseudonymization has been carried out, as in the following version of the example.

From 91770ccdbcc5dc22769bf43a809704e2df6e9336 Mon Sep 17 00:00:00 2001 From: ebeshero Date: Mon, 1 Jul 2024 13:49:09 -0400 Subject: [PATCH 084/127] further cleanup to regularize ize and iza words --- .../en/CMC-ComputerMediatedCommunication.xml | 24 +++++++++---------- 1 file changed, 11 insertions(+), 13 deletions(-) diff --git a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml index 5c74584d5d..e0076c76d5 100644 --- a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml +++ b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml @@ -95,7 +95,7 @@ See the file COPYING.txt for details.

The right part of the taxonomy describes units in which the production, transmission, and perception of contributions to CMC interactions are - organised in a strictly consecutive order: The content—verbal, nonverbal, or multimodal—of + organized in a strictly consecutive order: The content—verbal, nonverbal, or multimodal—of the contribution has to be produced before it can be transmitted through a network and made available on the computer monitor or mobile screen of any other party as a preserved and persistent unit. We term this type of unit a post. Posts occur in @@ -167,7 +167,7 @@ See the file COPYING.txt for details. Posts occur in a broad range of written CMC genres, - including (but not limited to) messages in chats and WhatsApp dialogues, tweets in X + including (but not limited to) messages in chats and WhatsApp dialogues, tweets in X (Twitter) timelines, comments on Facebook pages, posts in forum threads, and comments or contributions to discussions on Wikipedia talk pages or in the comment sections of weblogs.

@@ -407,10 +407,8 @@ See the file COPYING.txt for details.
CMC Macrostructure -

In many CMC genres, posts occur in a CMC document according to - which they are displayed, e.g. in a sequence or in threads; - posts within the document may be grouped. For example, in chat communication - such as WhatsApp, posts are part of a chat of one user with another user or among a +

In many CMC genres, posts may occur in a variety of ways: e.g. in a sequence or in threads, or grouped in some other way. + For example, in chat communication such as WhatsApp, posts are part of a chat of one user with another user or among a group of users. When an entire chat is saved, typically a logfile of the @@ -1264,14 +1262,14 @@ See the file COPYING.txt for details. type="standard" who="#f2213001a.A04" xml:id="f2213001a.m27.eg35"> - - [_FEMALE-PARTICIPANT-A04_] + + [_FEMALE-PARTICIPANT-A04_] versucht - - [_PARTICIPANT-A04_] + + [_PARTICIPANT-A04_] den wunsch @@ -1287,7 +1285,7 @@ See the file COPYING.txt for details. elements and their attributes also provide some categorical information about what has been removed. Using gap and supplied to record the anonymization is especially recommendable when the original name or referencing string has been - pseudonymised, i.e. replaced by a different referencing string of the + pseudonymized, i.e. replaced by a different referencing string of the same ontological category (such as replacing the female name Konstanze by the female name Kornelia.). In that case, the markup would be the only place where it can be seen that a pseudonymization @@ -1298,8 +1296,8 @@ See the file COPYING.txt for details. type="standard" who="#f2213001p.A04" xml:id="f2213001p.m27.eg35"> - - Kornelia + + Kornelia versucht From 7b3795fccbe236b77a72867d710c87ac3d5698bf Mon Sep 17 00:00:00 2001 From: ebeshero Date: Mon, 1 Jul 2024 13:52:28 -0400 Subject: [PATCH 085/127] commenting out overly prescriptive sentence re #1955 --- .../Guidelines/en/CMC-ComputerMediatedCommunication.xml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml index e0076c76d5..fdb0868486 100644 --- a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml +++ b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml @@ -191,9 +191,10 @@ See the file COPYING.txt for details. >att.ascribed, att.canonical, att.datable, att.global, att.timed, and att.typed, and as such may take a - variety of attributes. Common attributes used in conjunction with post include + variety of attributes.

Attributes specific to CMC post From 53c8e4bcb54404706bcbf23882cb9ec261d8b02f Mon Sep 17 00:00:00 2001 From: ebeshero Date: Mon, 1 Jul 2024 15:12:55 -0400 Subject: [PATCH 086/127] polishing edits re #1955 --- .../en/CMC-ComputerMediatedCommunication.xml | 10 +++++----- P5/Source/Specs/att.cmc.xml | 2 +- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml index fdb0868486..38680e97e4 100644 --- a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml +++ b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml @@ -197,7 +197,7 @@ See the file COPYING.txt for details. and xml:id.-->

- Attributes specific to CMC post + Attributes Specific to CMC post

Three attributes pertain specifically to post: @@ -258,7 +258,7 @@ See the file COPYING.txt for details.

-

In the CMC genre of Wiki talk, users insert their contribution to a discussion by modifying +

In the CMC genre of wiki talk, users insert their contribution to a discussion by modifying the wiki page of the discussion—the talk page. Since there is no technical reply action available in wiki software, users apply textual indentation in the wiki code to indicate a reply to a previous message, and a threaded structure is formed by a series of such @@ -295,7 +295,7 @@ See the file COPYING.txt for details.

Attributes for General CMC Encoding

The attribute generatedBy is also unique to CMC encoding. But unlike - modality, replyTo, and indentLevel, it is available not + modality, replyTo, and indentLevel, generatedBy is available not only on the post element, but on any of its descendants as well. @@ -444,7 +444,7 @@ See the file COPYING.txt for details. teiCorpus (or TEI) element that represents the corpus will contain one or more TEI elements as usual.

In the teiHeader of a document level TEI, the sourceDesc - will contain metadata about the CMC document such as its title, its author or owner, + will contain metadata about the CMC document such as a title, its author or owner, its URL, the date of its creation, the date of the last change made to it, and other metadata that are available and to be recorded such as one or more categories associated with the document.

@@ -1081,7 +1081,7 @@ See the file COPYING.txt for details.

In the following example, the type of post (in this case, a tweet) is recorded using the type attribute of post. If it were useful to record a particular - sub-catagorization of tweet, the subtype attribute + sub-categorization of tweet, the subtype attribute could also be used. Furthermore, the original unique identifer of the tweet as supplied by X (Twitter) is recorded as part of the value of the xml:id attribute of the diff --git a/P5/Source/Specs/att.cmc.xml b/P5/Source/Specs/att.cmc.xml index bd05545b5d..7b86a21452 100644 --- a/P5/Source/Specs/att.cmc.xml +++ b/P5/Source/Specs/att.cmc.xml @@ -27,7 +27,7 @@ See the file COPYING.txt for details. PR 2509). —Syd, 2023-11-27 --> - The @generatedBy attribute is for use within a <post> element. + The @generatedBy attribute is for use within a <post> element. From 2c48d4a685409315ddd12e7379e67d0b9e8c1017 Mon Sep 17 00:00:00 2001 From: ebeshero Date: Mon, 1 Jul 2024 15:21:50 -0400 Subject: [PATCH 087/127] small edits to reduce ambiguity, repetitiveness re 'CMC document' re #1955 --- P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml index 38680e97e4..5bf809abd7 100644 --- a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml +++ b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml @@ -671,9 +671,9 @@ See the file COPYING.txt for details.

- Documenting the Source of a CMC Document + Describing the Source of a CMC Document

A CMC document may be a chat logfile, a discussion page, or a thematical thread of posts - and is encoded within a TEI element. Among the metadata to be recorded in the + as encoded within a TEI element. Among the metadata to be recorded in the sourceDesc of its teiHeader are, if available, its title, author or owner, its URL, the date of its creation and/or the date of its last change (i.e. the time when the last post was added to it).

From f0e29240872d9b132cfc406cbd60f7f4ca85ba03 Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Mon, 1 Jul 2024 22:35:08 -0400 Subject: [PATCH 088/127] Repair CMC_generatedBy_within_post so that it does not depend on an attribute as the context node. Also add a test for this constraint to detest.xml. This set of changes has *not* been thoroughly tested, because it breaks the build. (Because there are 2 examples that have one or more generatedBy= attributes that are not in a post element.) This constraint did not previously break the build because when the context was an attribute it never fired at all due to a bug in the Skeleton Schematron implementation. --- P5/Source/Specs/att.cmc.xml | 9 ++------- P5/Test/detest.xml | 7 +++++++ P5/Test/expected-results/detest_xml_relaxng.log | 2 +- P5/Test/expected-results/detest_xml_schematron.log | 2 ++ 4 files changed, 12 insertions(+), 8 deletions(-) diff --git a/P5/Source/Specs/att.cmc.xml b/P5/Source/Specs/att.cmc.xml index 7b86a21452..15af1f8071 100644 --- a/P5/Source/Specs/att.cmc.xml +++ b/P5/Source/Specs/att.cmc.xml @@ -20,14 +20,9 @@ See the file COPYING.txt for details. - - - The @generatedBy attribute is for use within a <post> element. + + The @generatedBy attribute is for use within a <post> element. diff --git a/P5/Test/detest.xml b/P5/Test/detest.xml index c9e73ae042..8e2b4719d1 100644 --- a/P5/Test/detest.xml +++ b/P5/Test/detest.xml @@ -121,6 +121,13 @@ This post should be invalid due to an illegal value of modality +
+

+ This sentence should flag an + error, as the generatedBy is not within a + post. +

+
diff --git a/P5/Test/expected-results/detest_xml_relaxng.log b/P5/Test/expected-results/detest_xml_relaxng.log index cc6c29609d..82270f0f46 100644 --- a/P5/Test/expected-results/detest_xml_relaxng.log +++ b/P5/Test/expected-results/detest_xml_relaxng.log @@ -73,7 +73,7 @@ allowed: element http://www.tei-c.org/ns/1.0^listRef element http://www.tei-c.org/ns/1.0^relatedItem element http://www.tei-c.org/ns/1.0^citedRange -detest.xml:434:12: error: attribute ^target with invalid value "" +detest.xml:450:12: error: attribute ^target with invalid value "" required: data http://www.w3.org/2001/XMLSchema-datatypes^anyURI error: some documents are invalid diff --git a/P5/Test/expected-results/detest_xml_schematron.log b/P5/Test/expected-results/detest_xml_schematron.log index 6ecfa77abc..c2e7ec994c 100644 --- a/P5/Test/expected-results/detest_xml_schematron.log +++ b/P5/Test/expected-results/detest_xml_schematron.log @@ -1,3 +1,5 @@ +The @generatedBy attribute is for use within a <post> element. (ancestor-or-self::tei:post) +The @generatedBy attribute is for use within a <post> element. (ancestor-or-self::tei:post) The abbr element should not be categorized in detail with @subtype unless also categorized in general with @type (@type) The div element should not be categorized in detail with @subtype unless also categorized in general with @type (@type) From 567c4c0d2fe1879e98ce21f75d965f2b4622d21a Mon Sep 17 00:00:00 2001 From: ebeshero Date: Tue, 2 Jul 2024 01:16:48 -0400 Subject: [PATCH 089/127] adding post elements to exempla in att.cmc re release blocker for #1955 --- P5/Source/Specs/att.cmc.xml | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/P5/Source/Specs/att.cmc.xml b/P5/Source/Specs/att.cmc.xml index 15af1f8071..d5331f7a0f 100644 --- a/P5/Source/Specs/att.cmc.xml +++ b/P5/Source/Specs/att.cmc.xml @@ -112,22 +112,27 @@ See the file COPYING.txt for details.

Usenet news message: a client-generated line that introduces a quotation from a previous message (similar to email):

- - Am 03.04.2015 um + + + Am 03.04.2015 um 09:46 schrieb [_NAME_]: ... +

Wikipedia talk page, user signature

- + + + From dc77933c814f69d8c71236373d588639338bd148 Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Tue, 2 Jul 2024 10:14:23 -0400 Subject: [PATCH 090/127] Fix build by updating a detest log. (The only differences were the line numbers, BTW.) --- .../expected-results/detest_xml_relaxng.log | 34 +++++++++---------- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git a/P5/Test/expected-results/detest_xml_relaxng.log b/P5/Test/expected-results/detest_xml_relaxng.log index 82270f0f46..396e10c622 100644 --- a/P5/Test/expected-results/detest_xml_relaxng.log +++ b/P5/Test/expected-results/detest_xml_relaxng.log @@ -6,22 +6,22 @@ required: element http://www.tei-c.org/ns/1.0^desc element http://www.tei-c.org/ns/1.0^label element http://www.tei-c.org/ns/1.0^lg -detest.xml:188:10: error: attribute ^truth with invalid value "no" +detest.xml:195:10: error: attribute ^truth with invalid value "no" required: data http://www.w3.org/2001/XMLSchema-datatypes^boolean -detest.xml:190:10: error: attribute http://www.w3.org/XML/1998/namespace^lang not allowed +detest.xml:197:10: error: attribute http://www.w3.org/XML/1998/namespace^lang not allowed required: after -detest.xml:193:10: error: attribute ^enumerated with invalid value " dog breath" +detest.xml:200:10: error: attribute ^enumerated with invalid value " dog breath" required: data http://www.w3.org/2001/XMLSchema-datatypes^token -detest.xml:198:10: error: attribute ^name with invalid value "123" +detest.xml:205:10: error: attribute ^name with invalid value "123" required: data http://www.w3.org/2001/XMLSchema-datatypes^Name -detest.xml:207:10: error: unfinished content of element http://www.tei-c.org/ns/1.0^lg +detest.xml:214:10: error: unfinished content of element http://www.tei-c.org/ns/1.0^lg required: element http://www.tei-c.org/ns/1.0^l -detest.xml:234:37: error: invalid data or text not allowed +detest.xml:241:37: error: invalid data or text not allowed required: element http://www.tei-c.org/ns/1.0^add element http://www.tei-c.org/ns/1.0^surplus @@ -33,34 +33,34 @@ required: element http://www.tei-c.org/ns/1.0^cb element http://www.tei-c.org/ns/1.0^fw element http://www.tei-c.org/ns/1.0^anchor -detest.xml:254:11: error: attribute ^target with invalid value "#spanTest" +detest.xml:261:11: error: attribute ^target with invalid value "#spanTest" required: data http://www.w3.org/2001/XMLSchema-datatypes^anyURI -detest.xml:260:11: error: missing attributes of http://www.tei-c.org/ns/1.0^media +detest.xml:267:11: error: missing attributes of http://www.tei-c.org/ns/1.0^media required: attribute ^url -detest.xml:261:11: error: missing attributes of http://www.tei-c.org/ns/1.0^media +detest.xml:268:11: error: missing attributes of http://www.tei-c.org/ns/1.0^media required: attribute ^mimeType -detest.xml:267:51: error: invalid data or text not allowed +detest.xml:274:51: error: invalid data or text not allowed required: after -detest.xml:268:41: error: invalid data or text not allowed +detest.xml:275:41: error: invalid data or text not allowed required: after -detest.xml:269:61: error: invalid data or text not allowed +detest.xml:276:61: error: invalid data or text not allowed required: after -detest.xml:270:25: error: invalid data or text not allowed +detest.xml:277:25: error: invalid data or text not allowed required: after -detest.xml:334:12: error: element http://www.tei-c.org/ns/1.0^altIdentifier not allowed +detest.xml:341:12: error: element http://www.tei-c.org/ns/1.0^altIdentifier not allowed required: element http://www.tei-c.org/ns/1.0^msIdentifier -detest.xml:337:10: error: unfinished content of element http://www.tei-c.org/ns/1.0^msPart +detest.xml:344:10: error: unfinished content of element http://www.tei-c.org/ns/1.0^msPart required: element http://www.tei-c.org/ns/1.0^msIdentifier -detest.xml:366:10: error: element http://www.tei-c.org/ns/1.0^idno not allowed +detest.xml:373:10: error: element http://www.tei-c.org/ns/1.0^idno not allowed required: after allowed: @@ -73,7 +73,7 @@ allowed: element http://www.tei-c.org/ns/1.0^listRef element http://www.tei-c.org/ns/1.0^relatedItem element http://www.tei-c.org/ns/1.0^citedRange -detest.xml:450:12: error: attribute ^target with invalid value "" +detest.xml:441:12: error: attribute ^target with invalid value "" required: data http://www.w3.org/2001/XMLSchema-datatypes^anyURI error: some documents are invalid From 2dc29b3701feaf040bb520f7737ac3b192123d0c Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Tue, 2 Jul 2024 10:28:54 -0400 Subject: [PATCH 091/127] Minor tweak to example --- P5/Source/Specs/att.cmc.xml | 32 +++++++++++++------------------- 1 file changed, 13 insertions(+), 19 deletions(-) diff --git a/P5/Source/Specs/att.cmc.xml b/P5/Source/Specs/att.cmc.xml index d5331f7a0f..75502db9eb 100644 --- a/P5/Source/Specs/att.cmc.xml +++ b/P5/Source/Specs/att.cmc.xml @@ -7,15 +7,11 @@ See the file COPYING.txt for details. computer mediated communication - provides attributes - categorizing how the element content was created in a CMC - environment. + provides attributes categorizing how the element content was created in a CMC environment. generated by - categorizes - how the content of an element was generated in a CMC - environment. + categorizes how the content of an element was generated in a CMC environment. @@ -27,7 +23,7 @@ See the file COPYING.txt for details. - + @@ -114,10 +110,9 @@ See the file COPYING.txt for details. - Am 03.04.2015 um - 09:46 schrieb [_NAME_]: - ... - + Am 03.04.2015 um 09:46 schrieb [_NAME_]: + ... + @@ -125,14 +120,13 @@ See the file COPYING.txt for details.

Wikipedia talk page, user signature

- - - - - - + + + + + + + From 260b946624cc455dd96a98959147e0acccbc395e Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Tue, 2 Jul 2024 13:40:07 -0400 Subject: [PATCH 092/127] Correct historical source of smiley --- .../en/CMC-ComputerMediatedCommunication.xml | 23 ++++++++++--------- 1 file changed, 12 insertions(+), 11 deletions(-) diff --git a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml index 5bf809abd7..10d6e670ee 100644 --- a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml +++ b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml @@ -327,7 +327,7 @@ See the file COPYING.txt for details. when the content of the respective element was generated after a human user activated a template for its insertion - (often applicable to signed and time; e.g. see the + (often applicable to signed and time; e.g. see the signature in wiki talk in the second example below) when the content of the respective element was generated by the system, i.e. the CMC @@ -918,7 +918,7 @@ See the file COPYING.txt for details. - + @@ -969,7 +969,8 @@ See the file COPYING.txt for details.

Emoticons predate emojis and are created as combinations of ASCII punctuation and other characters using the keyboard. Examples are :-), ;-), :-(, :-x, \O/, and Oo. They first - occurred on a Usenet newsgroup (Fahlman, 2021) and then + occurred on a computer bulletin board system at Carnegie + Mellon University (Fahlman, 2021) and then became frequent in chat communications during the mid-1980s. An emoticon typically consists of several Unicode characters (from the ASCII subset) in a row, each of which has an intended use other than as part of an emoticon.

@@ -1039,13 +1040,13 @@ See the file COPYING.txt for details. only a graphic (without any text). As explained in , the modality of such a post should be considered as written. To encode the graphic information, the figure element may be used at the appropriate place.

-

In the following example a private chat post that contained - only a screenshot of a google search result for a hairdresser - is encoded as a post with a child figure. A - link to the graphic file itself is not included presumably - because this is a text-only corpus that does not include - images. - +

In the following example a private chat post that contained + only a screenshot of a google search result for a hairdresser + is encoded as a post with a child figure. A + link to the graphic file itself is not included presumably + because this is a text-only corpus that does not include + images. +

screenshot of the google search for hairdresser "Pasha's Haare'm" with the @@ -1054,7 +1055,7 @@ See the file COPYING.txt for details.
-

+

The following is an example of the encoding of a tweet which contains both text (including hashtags and mentions) and a graphic. The graphic element retains the URL of the From 86e6a4b5cd6ccff675bbe081c69b94b2f4cff2ca Mon Sep 17 00:00:00 2001 From: ebeshero Date: Tue, 2 Jul 2024 16:57:04 -0400 Subject: [PATCH 093/127] new usenet example with bib update on post spec for #1955 --- P5/Source/Guidelines/en/BIB-Bibliography.xml | 5 +++++ P5/Source/Specs/att.cmc.xml | 9 ++++----- P5/Source/Specs/post.xml | 20 ++++++++++++++++++++ 3 files changed, 29 insertions(+), 5 deletions(-) diff --git a/P5/Source/Guidelines/en/BIB-Bibliography.xml b/P5/Source/Guidelines/en/BIB-Bibliography.xml index c2044de1aa..1c462292de 100644 --- a/P5/Source/Guidelines/en/BIB-Bibliography.xml +++ b/P5/Source/Guidelines/en/BIB-Bibliography.xml @@ -199,6 +199,11 @@ is to come..., London (1678). Burgess, Anthony. A Clockwork Orange. (1962), opening. + + <ref target="https://www.usenetarchives.com/view.php?id=comp.text.sgml&mid=PDI5MzIxLjkwMDkzMDEzMzBAbWFudXRpdXMuZWNzLnNvdG9uLmFjLnVrPg">Burnard SGML reading list</ref>, + COMP.TEXT.SGML, September 30 to October 11, 1990 in Usenet Archives + (UsenetArchives.com, 2024). + Burnard, Lou. Principles of Database Design in S. Rahtz. ed. Information Technology in the Humanities: tools, techniques and applications, Ellis diff --git a/P5/Source/Specs/att.cmc.xml b/P5/Source/Specs/att.cmc.xml index 75502db9eb..683be52512 100644 --- a/P5/Source/Specs/att.cmc.xml +++ b/P5/Source/Specs/att.cmc.xml @@ -102,9 +102,9 @@ See the file COPYING.txt for details. /> - - - + +

Wikipedia talk page, user signature

diff --git a/P5/Source/Specs/post.xml b/P5/Source/Specs/post.xml index 2d79b8f5b0..2e3410b4c2 100644 --- a/P5/Source/Specs/post.xml +++ b/P5/Source/Specs/post.xml @@ -189,6 +189,26 @@ See the file COPYING.txt for details. nicht möchte, hat die Wissenschaft verlassen.

 + +

Usenet reply that comments on material quoted in an earlier message.

+ + + +

In article <2****.**********0@m*******.***.*****.**c.uk> S.*.*.*****z@e**.*****.**c.uk (Sebastian Rahtz) writes: + [for] Lou Burnard: + the Text Encoding Initiative document is a many-splendoured thing, + redolent of the mysterious east, caribbean evenings and the scent of + fresh pine in the himalayas [...] + +

+

Very poetic.

+

But really, what is it?

+ Doug + Doug Merritt ****@e***.********y.edu (ucbvax!eris!doug) + or uunet.uu.net!crossck!dougm + + +

Even though in some CMC genres (e.g., WhatsApp), the other parties are informed by an automated alert about the fact that another party is currently composing a new post, From 4d9be6d5e3a71c630da6a69699b0a1cf6ab4f685 Mon Sep 17 00:00:00 2001 From: ebeshero Date: Tue, 2 Jul 2024 17:13:09 -0400 Subject: [PATCH 094/127] repairing usenet example for #1955 --- P5/Source/Specs/post.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/P5/Source/Specs/post.xml b/P5/Source/Specs/post.xml index 2e3410b4c2..50505a1bb2 100644 --- a/P5/Source/Specs/post.xml +++ b/P5/Source/Specs/post.xml @@ -195,7 +195,7 @@ See the file COPYING.txt for details.

In article <2****.**********0@m*******.***.*****.**c.uk> S.*.*.*****z@e**.*****.**c.uk (Sebastian Rahtz) writes: - [for] Lou Burnard: + [for] Lou Burnard: the Text Encoding Initiative document is a many-splendoured thing, redolent of the mysterious east, caribbean evenings and the scent of fresh pine in the himalayas [...] From 61894c209aaefa3afcafc7da37b9a0c6ebfa4f06 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Helena=20Berm=C3=BAdez=20Sabel?= Date: Wed, 3 Jul 2024 09:56:36 +0200 Subject: [PATCH 095/127] apply some of the edits by @martinascholger --- .../en/CMC-ComputerMediatedCommunication.xml | 14 +++++++------- P5/Source/Specs/att.cmc.xml | 2 +- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml index 10d6e670ee..7b2b72111a 100644 --- a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml +++ b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml @@ -57,7 +57,7 @@ See the file COPYING.txt for details. CMC activities may not all be directly interactional; some may be part of a collaborative project of the involved individuals. Such collaboration could involve editing activities in a shared text editor or whiteboard in parallel with an ongoing CMC interaction (chat, audio conversation, or - audiovideo conference) in the same CMC environment in which these editing activities are + audio-video conference) in the same CMC environment in which these editing activities are discussed by the participants.

Basic units of CMC can be described according to three criteria: @@ -74,8 +74,8 @@ See the file COPYING.txt for details. Taxonomy of basic CMC units according to -

The most important distinction in the CMC taxonomy +

The most important distinction in the CMC taxonomy concerns the temporal nature of units exchanged via CMC technologies. The left part of the taxonomy describes units that are performed (by a producer) and perceived (by a recipient) as a continuous stream of behaviour. Units of this type can be performed as

@@ -93,7 +93,7 @@ See the file COPYING.txt for details. can be perceived by the other parties simultaneously (as may be the case in learning or collaboration environments). -

The right part of the taxonomy describes units in +

The right part of the CMC taxonomy describes units in which the production, transmission, and perception of contributions to CMC interactions are organized in a strictly consecutive order: The content—verbal, nonverbal, or multimodal—of the contribution has to be produced before it can be transmitted through a network and made @@ -103,7 +103,7 @@ See the file COPYING.txt for details. as written or multimodal posts, which are produced with an editor form that is designed for the composition of stretches of written text. Most contemporary post-based CMC technologies provide features for the inclusion of graphic and - audiovisual content (emoji graphics, images, videos) into posts and even to produce posts + audio-visual content (emoji graphics, images, videos) into posts and even to produce posts without verbal content (which then may consist only of emojis, an image, or a video file). Written and multimodal posts are the standard formats for user contributions in primarily text-based CMC genres and applications such as chat, SMS, WhatsApp, Instagram, Facebook, X @@ -253,7 +253,7 @@ See the file COPYING.txt for details. wenn Unregelmässigkeiten auftreten (im Bauverlauf) dann gibt es die saftigen Rechnungen. Da steht dann der Bauherr da und fragt sich, wie er denn so schnell einen fähigen Ersatz herbekommt. Und diese Frage erübrigt sich meist, weil der Markt der - Baufirmen das nicht hergibt—weil tendenziel 100 % Auslastung. (und noch schlimmer: + Baufirmen das nicht hergibt — weil tendenziel 100 % Auslastung. (und noch schlimmer: Absprachen) Was auch Folge des Marktdrucks gewesen war.

@@ -312,7 +312,7 @@ See the file COPYING.txt for details. In turn, if generatedBy is not specified on that element it inherits the value from its immediately enclosing element, and so on up the document hierarchy until a post is reached; the post either has a generatedBy attribute - specified or its presumed value is unspecified).

+ specified or its presumed value is unspecified.

- computer mediated communication + computer-mediated communication provides attributes categorizing how the element content was created in a CMC environment. From e083f5abd3be54ae8a177db208171edf0cc110ab Mon Sep 17 00:00:00 2001 From: helenasabel Date: Wed, 3 Jul 2024 19:48:17 +0200 Subject: [PATCH 096/127] minor tweaks suggested by @martinascholger --- .../Guidelines/en/CMC-ComputerMediatedCommunication.xml | 6 +++--- P5/Source/Specs/att.cmc.xml | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml index 7b2b72111a..ccb1329e55 100644 --- a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml +++ b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml @@ -232,13 +232,13 @@ See the file COPYING.txt for details. example, the second is a reply to the first, and the third is a reply to the second. + replyTo="#cmc_post09" when-iso="2015-07-29T21:44">

Es hat den Anschein, als wäre bei BER durchaus große Kompetenz am Bau, allerdings nicht in Form von Handwerkern….

http://www.zeit.de/2015/29/imtech-flughafen-berlin-ber-verzoegerung/komplettansicht

 + replyTo="#cmc_post10" when-iso="2015-07-30T19:11">

Nein Nein, an den Handwerkern kann es rein strukturel nicht gelegen haben. Niemand lässt seine Handwerker auf der Baustelle derart allein. Zudem gibt es höchstoffizielle “Abnahmen” von Bauabschnitten/phasen. Welcher Mangel auch bestanden hatte, er hätte @@ -247,7 +247,7 @@ See the file COPYING.txt for details. offenbar ein universeler Bauträger, der alles baut.

 + replyTo="#cmc_post11" when-iso="2015-07-30T19:26">

Stahlkunstruktionen dacht ich mal, was die bauen—oder bauen lassen.

Das ist schon ein übles Ding. Die Ausschreibungenund Angebote sind unauffällig, aber wenn Unregelmässigkeiten auftreten (im Bauverlauf) dann gibt es die saftigen diff --git a/P5/Source/Specs/att.cmc.xml b/P5/Source/Specs/att.cmc.xml index 8f31d3fe26..7b7c612433 100644 --- a/P5/Source/Specs/att.cmc.xml +++ b/P5/Source/Specs/att.cmc.xml @@ -117,7 +117,7 @@ See the file COPYING.txt for details. --> -

Wikipedia talk page, user signature

+

Wikipedia talk page: user signature

From c80e27a81a28faa21873fa2d5e16f44f223b2568 Mon Sep 17 00:00:00 2001 From: ebeshero Date: Wed, 3 Jul 2024 14:17:46 -0400 Subject: [PATCH 097/127] revisions to post exempla for #1955 --- P5/Source/Specs/post.xml | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/P5/Source/Specs/post.xml b/P5/Source/Specs/post.xml index 50505a1bb2..699d5bc949 100644 --- a/P5/Source/Specs/post.xml +++ b/P5/Source/Specs/post.xml @@ -73,7 +73,7 @@ See the file COPYING.txt for details. - +

standard user postings in chat

@@ -84,7 +84,7 @@ See the file COPYING.txt for details. - +

chat message-type "system": user enters a chatroom, "system" defined in listPerson

@@ -100,7 +100,7 @@ See the file COPYING.txt for details. - +

action message in chat

@@ -109,7 +109,7 @@ See the file COPYING.txt for details. - +

chat messages incl. interaction words (types: inflective and acronym) and an interaction phrase

@@ -137,7 +137,7 @@ See the file COPYING.txt for details. - +

user posting incl. an emoticon

@@ -146,7 +146,7 @@ See the file COPYING.txt for details. - +

Twitter: Tweet containing an addressing term and a hashtag expression

@@ -162,7 +162,7 @@ See the file COPYING.txt for details. - +

example from Wikipedia discussion

 - +

Blog comment: Die Anthropodizee-Frage. Wer den Himmel leerräumt, schafft die Menschheit ab. by Volker Birk. https://scilogs.spektrum.de/natur-des-glaubens/die-anthropodizee-frage-wer-himmel/#comment-31899

@@ -194,7 +194,7 @@ See the file COPYING.txt for details. -

In article <2****.**********0@m*******.***.*****.**c.uk> S.*.*.*****z@e**.*****.**c.uk (Sebastian Rahtz) writes: +

In article <2****.**********0@m*******.***.*****.**c.uk> S.*.*.*****z@e**.*****.**c.uk (Sebastian Rahtz) writes: [for] Lou Burnard: the Text Encoding Initiative document is a many-splendoured thing, redolent of the mysterious east, caribbean evenings and the scent of From 6076fc10bfa53b9782abd3db2ef017d25bb5c589 Mon Sep 17 00:00:00 2001 From: ebeshero Date: Wed, 3 Jul 2024 14:39:31 -0400 Subject: [PATCH 098/127] small edits to intro of cmc chapter re #1955 --- .../en/CMC-ComputerMediatedCommunication.xml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml index ccb1329e55..9dd5e68b57 100644 --- a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml +++ b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml @@ -22,8 +22,8 @@ See the file COPYING.txt for details. move may determine the context for subsequent moves (typically taken by another interlocutor) and may react to the context created by a prior move; they are created and displayed using computer - technology (keyboard, mouse, speech-to-text conversion software, monitor or - screen) and transmitted over a computer network (typically the + technology or human-machine interfaces such as keyboard, mouse, speech-to-text conversion software, monitor or + screen and transmitted over a computer network (typically the internet). Such communications may be expressed as posts (cf. i.e. stretches of speech which are produced to perform a speaker turn in a conversation, - i.e. nonverbal behavior (gesture, gaze) produced to perform a speaker turn, either + i.e. nonverbal behaviour (gesture, gaze) produced to perform a speaker turn, either performed by the real body of an interlocutor (e.g. in a video conference) or through the virtual avatar of an interlocutor in a 3D environment, @@ -203,7 +203,7 @@ See the file COPYING.txt for details. - The type of the content of a post (i.e., whether the content is written, an + The type of the content of a post (i.e., whether the content is text, an image, a video clip, etc.) is indicated by the child elements of the post. (E.g., a post might have a child p, or a child figure with a graphic, or a child figure with a media, or some combination @@ -1238,7 +1238,7 @@ See the file COPYING.txt for details. subcategories of names as described in such as surname or geogName, or rs for a general referencing string. In the following chat example (adapted from ), nicknames are linked to a person - entry as shown in section via the ref attribute. + entry as shown in section via the ref attribute. From 251bb50f51b0235ddae08e521751601fd763d2d8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Helena=20Berm=C3=BAdez=20Sabel?= Date: Wed, 3 Jul 2024 20:52:44 +0200 Subject: [PATCH 099/127] Apply suggestions by @martinascholger --- .../en/CMC-ComputerMediatedCommunication.xml | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml index 9dd5e68b57..1a4557a002 100644 --- a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml +++ b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml @@ -126,7 +126,7 @@ See the file COPYING.txt for details. TEI P5 element - utterance + spoken utterance transcription of speech u @@ -177,7 +177,7 @@ See the file COPYING.txt for details. keyboard or speech-to-text conversion software in an entry form on the screen. In many cases the technology allows authors to include or embed graphics (emojis or images), video files, and hyperlinks into their posts. - audio posts: A growing number of CMC technologies, e.g. + spoken (audio posts): A growing number of CMC technologies, e.g. messenger software such as WhatsApp or RocketChat, allow for an alternative, spoken production of posts by providing a recording function which allows users to record a stretch of spoken language and transmit the resulting audio file to the other @@ -322,7 +322,7 @@ See the file COPYING.txt for details. when the content of the respective element was naturally typed or spoken by - a human user (cf. the chat posts in Example haircut) when the content of the respective element was generated after a human user @@ -333,7 +333,7 @@ See the file COPYING.txt for details. when the content of the respective element was generated by the system, i.e. the CMC environment (see, e.g., the system message in an IRC chat in the fourth example below) - when the content of the respective element was generated by a bot i.e. a non-human + when the content of the respective element was generated by a bot, i.e. a non-human agent, typically one that is not part of the CMC environment itself when it is unspecified or unknown how the content of the respective element was @@ -501,7 +501,7 @@ See the file COPYING.txt for details. also form a threaded structure, and visual indentations can be reconstructed from it and need not be explicitly encoded.

Threads may also be explicitly encoded as nested div elements as in the following - skeleton. + skeleton:

...
@@ -515,7 +515,7 @@ See the file COPYING.txt for details.

Using this encoding strategy, the thread from the second example in could be encoded as follows. could be encoded as follows:

@@ -574,7 +574,7 @@ See the file COPYING.txt for details. zusammen

In the graphical user interface (GUI) of a more complex multimodal CMC environment such as - Second life, a gaming and learning platform, interactions may consist of interleaved + Second Life, a gaming and learning platform, interactions may consist of interleaved occurrences of posts (p), utterances (u) and non-verbal acts such as bodily activities (kinesic) or other on-screen activities (incident). In the following example a spoken utterance, an avatar's bodily activity, and a written post From 325d14b2f78b64853c3d7031e728cc820e26d7f7 Mon Sep 17 00:00:00 2001 From: helenasabel Date: Wed, 3 Jul 2024 21:16:10 +0200 Subject: [PATCH 100/127] change how examples are referred --- .../Guidelines/en/CMC-ComputerMediatedCommunication.xml | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml index 1a4557a002..1354ad3cd4 100644 --- a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml +++ b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml @@ -328,17 +328,16 @@ See the file COPYING.txt for details. when the content of the respective element was generated after a human user activated a template for its insertion (often applicable to signed and time; e.g. see the - signature in wiki talk in the second example below) + signature in wiki talk in this example below) when the content of the respective element was generated by the system, i.e. the CMC - environment (see, e.g., the system message in an IRC chat in the fourth example below) + environment (see, e.g., the system message in an IRC chat in the this other example below) when the content of the respective element was generated by a bot, i.e. a non-human agent, typically one that is not part of the CMC environment itself when it is unspecified or unknown how the content of the respective element was - generated (see, e.g. the retweet that forms the second post in the third example - below). + generated (see, e.g. the retweet that forms the second post in this example below).

@@ -514,7 +513,7 @@ See the file COPYING.txt for details.

-

Using this encoding strategy, the thread from the second example in Using this encoding strategy, this example from could be encoded as follows:

From 56195138c33659ae1c8542605c19e5db7e79ea0a Mon Sep 17 00:00:00 2001 From: helenasabel Date: Wed, 3 Jul 2024 21:21:39 +0200 Subject: [PATCH 101/127] minor tweak in list of classes --- P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml index 1354ad3cd4..9e4736d788 100644 --- a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml +++ b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml @@ -187,7 +187,7 @@ See the file COPYING.txt for details. incident, or other existing TEI elements within a div, or directly within the body, and may contain headings, paragraphs, openers, closers, or salutations.

-

The post element is a member of the TEI attribute classes The post element is a member of several TEI attribute classes, including att.ascribed, att.canonical, att.datable, att.global, att.timed, and att.typed, and as such may take a From 9cc186b8a5480bd3c970d5dd9bae80441d9a1d7b Mon Sep 17 00:00:00 2001 From: helenasabel Date: Wed, 3 Jul 2024 21:23:40 +0200 Subject: [PATCH 102/127] correct spelling of nonverbal --- P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml index 9e4736d788..557efe0912 100644 --- a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml +++ b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml @@ -64,7 +64,7 @@ See the file COPYING.txt for details. the temporal properties of when these contributions are produced by their creators, transmitted via CMC systems, and made accessible for the recipients; - the modality of the unit as a whole, whether verbal or noverbal; + the modality of the unit as a whole, whether verbal or nonverbal; for verbal units: whether the unit is expressed in the written or spoken mode. @@ -574,7 +574,7 @@ See the file COPYING.txt for details.

In the graphical user interface (GUI) of a more complex multimodal CMC environment such as Second Life, a gaming and learning platform, interactions may consist of interleaved - occurrences of posts (p), utterances (u) and non-verbal acts such as + occurrences of posts (p), utterances (u) and nonverbal acts such as bodily activities (kinesic) or other on-screen activities (incident). In the following example a spoken utterance, an avatar's bodily activity, and a written post occur on the same level within the body element, representing parts of a multimodal From 34dbbc0c172b8c4fa7adec711d223039dbda1c29 Mon Sep 17 00:00:00 2001 From: Klaus Rettinghaus Date: Thu, 4 Jul 2024 13:26:15 +0200 Subject: [PATCH 103/127] encode quotes in descriptions --- P5/Source/Specs/ab.xml | 2 +- P5/Source/Specs/fsdLink.xml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/P5/Source/Specs/ab.xml b/P5/Source/Specs/ab.xml index b1b68a70f1..8e608a1eed 100644 --- a/P5/Source/Specs/ab.xml +++ b/P5/Source/Specs/ab.xml @@ -13,7 +13,7 @@ 의미적 부담 없이, 문단과 유사한 구 또는 상호층위 요소에 대한 익명 전달체로 기능하는 임의적 성분-층위 단위를 포함한다. 包含文件中任何隨機組合性層次的單元，匿名收容類似一個段落、但不包含段落語義的字詞或中間層元素。 任意の部分的テキスト単位を示す。特定の意味はなくとも、段落に相当する、 句レベル・挿入レベルの単位として無名単位になる。 - contient une unité de texte quelconque, de niveau "composant", faisant office de contenant anonyme pour une expression ou des éléments de niveau intermédiaire, analogue à un paragraphe mais sans sa portée sémantique. + contient une unité de texte quelconque, de niveau composant, faisant office de contenant anonyme pour une expression ou des éléments de niveau intermédiaire, analogue à un paragraphe mais sans sa portée sémantique. contiene cualquier unidad textual a nivel de componente que actua como un contenedor anónimo de sintagmas o de elementos de internivel similares al párrafo pero sin la carga semántica de este último. contiene una qualsiasi unità testuale a livello di componente che funge da contenitore anonimo di sintagmi o elementi interlivello simili al paragrafo ma senza il bagaglio semantico di quest'ultimo diff --git a/P5/Source/Specs/fsdLink.xml b/P5/Source/Specs/fsdLink.xml index beba71bcd0..47e2320be2 100644 --- a/P5/Source/Specs/fsdLink.xml +++ b/P5/Source/Specs/fsdLink.xml @@ -13,7 +13,7 @@ structure declaration for it. asocia el nombre de una estructura de rasgos dada con una declaración de la estructura de rasgos para ella. 素性構造宣言により素性構造の名前を示す。 - associe le nom d'une structure de traits "type" à + associe le nom d'une structure de traits type à sa déclaration de structure de traits. associa il nome di una struttura di tratti alla dichiarazione relativa From c54378d79c0664f647dfbe471ab9ce3edb2f5c51 Mon Sep 17 00:00:00 2001 From: Klaus Rettinghaus Date: Thu, 4 Jul 2024 13:46:24 +0200 Subject: [PATCH 104/127] encode quotes in desc --- P5/Source/Specs/dictScrap.xml | 2 +- P5/Source/Specs/lbl.xml | 2 +- P5/Source/Specs/model.choicePart.xml | 2 +- P5/Source/Specs/nameLink.xml | 2 +- P5/Source/Specs/param.xml | 8 ++++---- P5/Source/Specs/sourceDesc.xml | 6 +++--- 6 files changed, 11 insertions(+), 11 deletions(-) diff --git a/P5/Source/Specs/dictScrap.xml b/P5/Source/Specs/dictScrap.xml index 19840ec46c..44f703ed05 100644 --- a/P5/Source/Specs/dictScrap.xml +++ b/P5/Source/Specs/dictScrap.xml @@ -14,7 +14,7 @@ 字典辭條的片段，包含自由組合的詞組層次字典元素。 句レベルの辞書要素をとる辞書項目を示す。 contient la partie d'une entrée de dictionnaire - dans laquelle d'autres éléments de niveau "expression" sont librement associés. + dans laquelle d'autres éléments de niveau expression sont librement associés. engloba una parte de la entrada del diccionario en la que otros elementos de nivel sintagmático del diccionario se combinan de forma libre. include una parte di una voce di dizionario in cui sono combinati liberamente altri elementi di dizionario a livello sintagmatico diff --git a/P5/Source/Specs/lbl.xml b/P5/Source/Specs/lbl.xml index be29884354..18112fa278 100644 --- a/P5/Source/Specs/lbl.xml +++ b/P5/Source/Specs/lbl.xml @@ -16,7 +16,7 @@ 語形のラベルを示す。例えば、翻訳、短縮形などの各種省略形など。 étiquette pour la forme d’un mot, pour un exemple, pour une traduction, ou pour tout autre type d’information, par exemple "abréviation pour", - "contraction de", "littéralement", "approximativement", "synonymes", etc. + contraction de, littéralement, approximativement, synonymes, etc. en diccionarios, contiene una etiqueta para una forma, ejemplo, traducción u otra información, p.ej. abreviatura para, contracción de, literal., aproximadamente, sinónimo, etc. diff --git a/P5/Source/Specs/model.choicePart.xml b/P5/Source/Specs/model.choicePart.xml index e5751b9830..8e7c47914f 100644 --- a/P5/Source/Specs/model.choicePart.xml +++ b/P5/Source/Specs/model.choicePart.xml @@ -12,7 +12,7 @@ peuvent être utilisés en alternance avec choice agrupa los elementos (excluída el propio elemento - "choice") que pueden ser usados en alternancia con choice. + choice) que pueden ser usados en alternancia con choice. raggruppa gli elementi (escluso l'elemento choice) che possono essere usati in alternanza con choice diff --git a/P5/Source/Specs/nameLink.xml b/P5/Source/Specs/nameLink.xml index 75b0c2d56f..1fd44b2673 100644 --- a/P5/Source/Specs/nameLink.xml +++ b/P5/Source/Specs/nameLink.xml @@ -12,7 +12,7 @@ 名前の中で使われているが、その一部としては見られない、関連する句やリ ンクを示す。例えば、van derや ofなど。 contient une particule ou une expression exprimant un lien, utilisés dans un nom mais considérés comme - n'en faisant pas partie, comme "van der" ou "de". + n'en faisant pas partie, comme van der ou de. contiene un afijo de conexión al interno del nombre no considerado parte del nombre, como p.ej. Van Der, o De Las. contiene un affisso di connessione all'interno del nome non considerato parte del nome, come van der diff --git a/P5/Source/Specs/param.xml b/P5/Source/Specs/param.xml index 6fed3ad2aa..03bd44bb62 100644 --- a/P5/Source/Specs/param.xml +++ b/P5/Source/Specs/param.xml @@ -41,7 +41,7 @@ when used with behaviour graphic, a parameter of this name supplies a value for the height of - the graphic e.g. "300px", "50%". + the graphic e.g. 300px, 50%. a parameter of this name should supply a @@ -68,8 +68,8 @@ when used with the note behaviour, a parameter of this name should provide a string which describes the intended - placement of some text; typical values include "margin", "footnote", "endnote", - "inline", "bottom" + placement of some text; typical values include margin, footnote, endnote, + inline, bottom a parameter of this name can be used to @@ -85,7 +85,7 @@ when used with behaviour graphic, a parameter of this name supplies a value for the width of the - graphic e.g. "400px", "70%". + graphic e.g. 400px, 70%. diff --git a/P5/Source/Specs/sourceDesc.xml b/P5/Source/Specs/sourceDesc.xml index cbf92ec831..4a1dc421ec 100644 --- a/P5/Source/Specs/sourceDesc.xml +++ b/P5/Source/Specs/sourceDesc.xml @@ -10,17 +10,17 @@ descrizione della fonte Beschreibung der Quellen describes the source(s) from which an electronic text was derived or generated, typically a - bibliographic description in the case of a digitized text, or a phrase such as "born digital" + bibliographic description in the case of a digitized text, or a phrase such as born digital for a text which has no previous existence. décrit la source à partir de laquelle un texte électronique a été dérivé ou produit, habituellement une description bibliographique pour un texte numérisé, ou une - expression comme "document numérique natif " pour un texte qui n'a aucune existence précédente. + expression comme document numérique natif pour un texte qui n'a aucune existence précédente. 전자 파일을 생성하거나 도출한 원전 텍스트에 대한 기술을 제시한다. 提供所製電子文件的一個或數個來源文件的書目描述。 電子テキストが作られた元テキストの情報を示す。 beschreibt die Quelle, von der sich der elektronische Text ableitet. Üblicherweise eine bibliografische Beschreibung im Falle eines digitalisierten Textes oder eine Bezeichnung wie - "born digital" für einen nur in elektronischer Form vorliegenden Text. + born digital für einen nur in elektronischer Form vorliegenden Text. proporciona una descripción del texto (o textos) fuente del que un texto electrónico deriva o ha sido generado. fornisce una descrizione relativa alla o alle fonti da From b2eebc2cbb135392c941786570b14b6c909243d0 Mon Sep 17 00:00:00 2001 From: Klaus Rettinghaus Date: Thu, 4 Jul 2024 15:03:58 +0200 Subject: [PATCH 105/127] remove whitespace at end of description --- P5/Source/Specs/TEI.xml | 6 ++-- P5/Source/Specs/abstract.xml | 2 +- P5/Source/Specs/accMat.xml | 3 +- P5/Source/Specs/acquisition.xml | 2 +- P5/Source/Specs/anyElement.xml | 3 +- P5/Source/Specs/att.coordinated.xml | 12 +++---- P5/Source/Specs/att.damaged.xml | 5 ++- P5/Source/Specs/att.datable.custom.xml | 2 +- P5/Source/Specs/att.declarable.xml | 6 ++-- P5/Source/Specs/att.dimensions.xml | 2 +- P5/Source/Specs/att.divLike.xml | 18 ++++------ P5/Source/Specs/att.duration.w3c.xml | 6 ++-- P5/Source/Specs/att.duration.xml | 3 +- P5/Source/Specs/att.enjamb.xml | 3 +- P5/Source/Specs/att.entryLike.xml | 3 +- P5/Source/Specs/att.gaijiProp.xml | 2 +- P5/Source/Specs/att.global.analytic.xml | 6 ++-- P5/Source/Specs/att.global.responsibility.xml | 2 +- P5/Source/Specs/att.global.xml | 11 +++--- P5/Source/Specs/att.handFeatures.xml | 32 ++++++----------- P5/Source/Specs/att.internetMedia.xml | 3 +- P5/Source/Specs/att.linguistic.xml | 3 +- P5/Source/Specs/att.measurement.xml | 3 +- P5/Source/Specs/att.msClass.xml | 2 +- P5/Source/Specs/att.msExcerpt.xml | 6 ++-- P5/Source/Specs/att.pointing.group.xml | 3 +- P5/Source/Specs/att.pointing.xml | 9 ++--- P5/Source/Specs/att.scoping.xml | 2 +- P5/Source/Specs/att.tableDecoration.xml | 18 ++++------ P5/Source/Specs/att.textCritical.xml | 3 +- P5/Source/Specs/att.transcriptional.xml | 36 +++++++------------ P5/Source/Specs/att.translatable.xml | 6 ++-- P5/Source/Specs/att.typed.xml | 3 +- P5/Source/Specs/att.witnessed.xml | 3 +- P5/Source/Specs/att.written.xml | 3 +- P5/Source/Specs/broadcast.xml | 3 +- P5/Source/Specs/castItem.xml | 2 +- P5/Source/Specs/catRef.xml | 3 +- P5/Source/Specs/change.xml | 2 +- P5/Source/Specs/channel.xml | 4 +-- P5/Source/Specs/citeStructure.xml | 2 +- P5/Source/Specs/classRef.xml | 5 ++- P5/Source/Specs/classSpec.xml | 15 +++----- P5/Source/Specs/classes.xml | 6 ++-- P5/Source/Specs/correspAction.xml | 21 ++++------- P5/Source/Specs/damageSpan.xml | 2 +- P5/Source/Specs/dataFacet.xml | 3 +- P5/Source/Specs/dataRef.xml | 2 +- P5/Source/Specs/decoDesc.xml | 3 +- P5/Source/Specs/derivation.xml | 18 ++++------ P5/Source/Specs/dimensions.xml | 9 ++--- P5/Source/Specs/eLeaf.xml | 3 +- P5/Source/Specs/epigraph.xml | 2 +- P5/Source/Specs/equipment.xml | 3 +- P5/Source/Specs/facsimile.xml | 3 +- P5/Source/Specs/factuality.xml | 12 +++---- P5/Source/Specs/filiation.xml | 3 +- P5/Source/Specs/forename.xml | 2 +- P5/Source/Specs/fsDecl.xml | 3 +- P5/Source/Specs/fsdDecl.xml | 3 +- P5/Source/Specs/fsdLink.xml | 9 ++--- P5/Source/Specs/fw.xml | 18 ++++------ P5/Source/Specs/graph.xml | 12 +++---- P5/Source/Specs/heraldry.xml | 3 +- P5/Source/Specs/idno.xml | 3 +- P5/Source/Specs/incident.xml | 3 +- P5/Source/Specs/incipit.xml | 3 +- P5/Source/Specs/interaction.xml | 30 ++++++---------- P5/Source/Specs/langKnowledge.xml | 6 ++-- P5/Source/Specs/listForest.xml | 3 +- P5/Source/Specs/listNym.xml | 2 +- P5/Source/Specs/listOrg.xml | 2 +- P5/Source/Specs/mapping.xml | 3 +- P5/Source/Specs/metDecl.xml | 3 +- P5/Source/Specs/model.choicePart.xml | 6 ++-- P5/Source/Specs/model.formPart.xml | 3 +- P5/Source/Specs/model.pPart.editorial.xml | 3 +- P5/Source/Specs/model.xml | 4 +-- P5/Source/Specs/occupation.xml | 3 +- P5/Source/Specs/param.xml | 15 ++++---- P5/Source/Specs/reg.xml | 2 +- P5/Source/Specs/respons.xml | 3 +- P5/Source/Specs/rhyme.xml | 3 +- P5/Source/Specs/sealDesc.xml | 3 +- P5/Source/Specs/secFol.xml | 3 +- P5/Source/Specs/socecStatus.xml | 3 +- P5/Source/Specs/sourceDesc.xml | 2 +- P5/Source/Specs/spanGrp.xml | 3 +- P5/Source/Specs/standOff.xml | 2 +- P5/Source/Specs/surface.xml | 3 +- P5/Source/Specs/teidata.count.xml | 3 +- P5/Source/Specs/teidata.duration.iso.xml | 2 +- P5/Source/Specs/teidata.name.xml | 2 +- P5/Source/Specs/teidata.namespace.xml | 3 +- P5/Source/Specs/teidata.numeric.xml | 2 +- P5/Source/Specs/teidata.probability.xml | 2 +- P5/Source/Specs/teidata.sex.xml | 2 +- P5/Source/Specs/teidata.temporal.iso.xml | 3 +- P5/Source/Specs/teidata.xTruthValue.xml | 2 +- P5/Source/Specs/textClass.xml | 3 +- P5/Source/Specs/textLang.xml | 3 +- P5/Source/Specs/unclear.xml | 8 ++--- P5/Source/Specs/unit.xml | 4 +-- P5/Source/Specs/vColl.xml | 3 +- P5/Source/Specs/vMerge.xml | 3 +- P5/Source/Specs/valDesc.xml | 3 +- P5/Source/Specs/when.xml | 3 +- P5/Source/Specs/zone.xml | 3 +- 108 files changed, 207 insertions(+), 374 deletions(-) diff --git a/P5/Source/Specs/TEI.xml b/P5/Source/Specs/TEI.xml index f9e779ce03..729dd547f0 100644 --- a/P5/Source/Specs/TEI.xml +++ b/P5/Source/Specs/TEI.xml @@ -22,10 +22,8 @@ enthält ein einzelnes TEI-konformes Dokument, das aus einem einzigen TEI-Header und einem oder mehreren Mitgliedern der model.resource-Klasse besteht. Mehrere TEI-Elemente können in einem teiCorpus-Element zusammengefasst werden. - contiene un solo documento conforme a la norma TEI, combinando un solo encabezado TEI (teiHeader) con uno o más miembros de la clase model.resource. Múltiples elementos TEI se pueden combinar al interno de un elemento TEI o teiCorpus. - - contiene un documento TEI-conforme, comprendente un'intestazione e un testo, sia esso isolato o parte di un elemento teiCorpus - + contiene un solo documento conforme a la norma TEI, combinando un solo encabezado TEI (teiHeader) con uno o más miembros de la clase model.resource. Múltiples elementos TEI se pueden combinar al interno de un elemento TEI o teiCorpus. + contiene un documento TEI-conforme, comprendente un'intestazione e un testo, sia esso isolato o parte di un elemento teiCorpus diff --git a/P5/Source/Specs/abstract.xml b/P5/Source/Specs/abstract.xml index fc53a09f63..b014d87d5e 100644 --- a/P5/Source/Specs/abstract.xml +++ b/P5/Source/Specs/abstract.xml @@ -5,7 +5,7 @@ contains a summary or formal abstract prefixed to an existing source document by the encoder. Contiene un resumen o abstract formal prefijado a una fuente documental por el codificador. - contiene un riepilogo o abstract formale aggiunto, in testa a un dato documento di origine, da chi codifica. + contiene un riepilogo o abstract formale aggiunto, in testa a un dato documento di origine, da chi codifica. enthält eine (formale) Zusammenfassung, die einem bestehenden Quelldokument vorangestellt wird. 符号化する人によって既存の元文書の前に付加された要約または正式な要約を含む。 diff --git a/P5/Source/Specs/accMat.xml b/P5/Source/Specs/accMat.xml index 5b8e5e448f..266469d7c7 100644 --- a/P5/Source/Specs/accMat.xml +++ b/P5/Source/Specs/accMat.xml @@ -16,8 +16,7 @@ described, such as non-contemporaneous documents or fragments bound in with it at some earlier historical period. 기술하고 있는 원고와 밀접히 관련된 중요한 부가적 자료를 세밀하게 기술한다. 예를 들어, 어떤 이전 시기에 원고와 함께 제본된 비동시대의 문서 또는 문서 일부. 包含可能與該手稿關係密切的重要附加資料之細節，例如非同時期的文件或是在早期與手稿裝訂一起的片段。 - 当該手書き資料と密接に関連していると考えられる重要な追加資料、例えば、時代を異にする文書、歴史的に早い時期に手書き資料と合わされた断片などの詳細を示す。 - + 当該手書き資料と密接に関連していると考えられる重要な追加資料、例えば、時代を異にする文書、歴史的に早い時期に手書き資料と合わされた断片などの詳細を示す。 donne des détails sur tout matériel d'accompagnement étroitement associé au manuscrit, tel que documents non contemporains ou fragments reliés avec le manuscrit à une époque antérieure. diff --git a/P5/Source/Specs/acquisition.xml b/P5/Source/Specs/acquisition.xml index e6e0a4109a..bbf02eb4be 100644 --- a/P5/Source/Specs/acquisition.xml +++ b/P5/Source/Specs/acquisition.xml @@ -14,7 +14,7 @@ institution. contient des informations sur les modalités et circonstances de l'entrée du manuscrit ou de la partie du manuscrit dans l'institution qui le détient - contiene cualquier descripción u otra información concerniente al proceso de adquisición del manuscrito o de una de sus partes o cualquier otro objeto que haya ingresado en la institución + contiene cualquier descripción u otra información concerniente al proceso de adquisición del manuscrito o de una de sus partes o cualquier otro objeto que haya ingresado en la institución contiene informazioni relative al processo di acquisizione di un manoscritto o di una sua parte diff --git a/P5/Source/Specs/anyElement.xml b/P5/Source/Specs/anyElement.xml index 0a6034270d..6b17133e57 100644 --- a/P5/Source/Specs/anyElement.xml +++ b/P5/Source/Specs/anyElement.xml @@ -15,8 +15,7 @@ supplies a list of namespaces to one of which the - permitted elements must belong. - + permitted elements must belong. 許可された要素が属していなければならない名前空間のリストを提供する。 diff --git a/P5/Source/Specs/att.coordinated.xml b/P5/Source/Specs/att.coordinated.xml index aa9c818d63..1ac5439c72 100644 --- a/P5/Source/Specs/att.coordinated.xml +++ b/P5/Source/Specs/att.coordinated.xml @@ -23,8 +23,7 @@ or surface. rectangular space. 직사각형 공간의 좌측 상단에 대한 x 좌표 값을 제시한다. proporciona el valor de la coordinada X para el ángulo superior izquierdo de un espacio rectangular. - 矩形における左上点のX軸の値を示す。 - + 矩形における左上点のX軸の値を示す。 donne la valeur x de l'abscisse du coin supérieur gauche d'un rectangle. assegna il valore x all'angolo superiore sinistro di uno spazio rettangolare @@ -35,8 +34,7 @@ rectangular space. rectangular space. 직사각형 공간의 좌측 상단에 대한 y 좌표 값을 제시한다. proporciona el valor de la coordinada Y para el ángulo superior izquierdo de un espacio rectangular. - 矩形における左上点のY軸の値を示す。 - + 矩形における左上点のY軸の値を示す。 donne la valeur y de l'ordonnée du coin supérieur gauche d'un rectangle. assegna il valore y all'angolo superiore sinistro di uno spazio rettangolare @@ -46,8 +44,7 @@ rectangular space. rectangular space. 직사각형 공간의 오른쪽 하단에 대한 x 좌표 값을 제시한다. proporciona el valor de la coordinada X para el ángulo inferior derecho de un espacio rectangular - 矩形における右下点のX軸の値を示す。 - + 矩形における右下点のX軸の値を示す。 donne la valeur x de l'abscisse du coin inférieur droit d'un rectangle. assegna il valore x all'angolo inferiore destro di uno spazio rettangolare @@ -57,8 +54,7 @@ rectangular space. rectangular space. 직사각형 공간의 오른쪽 하단에 대한 y 좌표 값을 제시한다. proporciona el valor de la coordinada Y para el ángulo inferior izquierdo de un espacio rectangular - 矩形における右下点のY軸の値を示す。 - + 矩形における右下点のY軸の値を示す。 donne la valeur y de l'ordonnée du coin inférieur droit d'un rectangle. assegna il valore y all'angolo inferiore destro di uno spazio rettangolare diff --git a/P5/Source/Specs/att.damaged.xml b/P5/Source/Specs/att.damaged.xml index ffbf926c28..71ddfe9907 100644 --- a/P5/Source/Specs/att.damaged.xml +++ b/P5/Source/Specs/att.damaged.xml @@ -4,7 +4,7 @@ provides attributes describing the nature of any physical damage affecting a reading. 독법에 영향을 미치는 물리적 손상의 특성을 기술하는 속성을 제공한다. - 読みに影響を与える物理的損傷の性格を示す属性を示す。 + 読みに影響を与える物理的損傷の性格を示す属性を示す。 proporciona los atributos que describen la naturaleza de cualquier daño físico que afecta a una lectura. fournit des attributs décrivant la nature de tout dommage @@ -90,8 +90,7 @@ indica l'entità del danneggiamento misurato in base a una scala funzionale; il marcatore damage con l'attributo degree dovranno essere utilizzati solo se il testo può essere letto con una certa sicurezza; i - testi derivanti da altre fonti andranno marcati come supplied - + testi derivanti da altre fonti andranno marcati come supplied >indica el grado del daño medido en base a una escala funcional; la etiqueta damage (daño) con el atributo degree (grado) deberán utilizarse sólo si el texto puede ser leído con una cierta certeza; los diff --git a/P5/Source/Specs/att.datable.custom.xml b/P5/Source/Specs/att.datable.custom.xml index 298ff2d19d..6f16f1b017 100644 --- a/P5/Source/Specs/att.datable.custom.xml +++ b/P5/Source/Specs/att.datable.custom.xml @@ -63,7 +63,7 @@ supplies a pointer to some location defining a named point in time with reference to which the datable item is understood to have occurred - ある時点につけた名前とその事柄が起きたとされる時間をともに定義している場所へのポインタを示す。たとえば、「令和改元」という日付をともなうID付きイベント要素を作成した場合にそのIDに対する参照を行う。 + ある時点につけた名前とその事柄が起きたとされる時間をともに定義している場所へのポインタを示す。たとえば、「令和改元」という日付をともなうID付きイベント要素を作成した場合にそのIDに対する参照を行う。 diff --git a/P5/Source/Specs/att.declarable.xml b/P5/Source/Specs/att.declarable.xml index bc208825e9..e72a2acad0 100644 --- a/P5/Source/Specs/att.declarable.xml +++ b/P5/Source/Specs/att.declarable.xml @@ -11,8 +11,7 @@ l'en-tête TEI qui peuvent être choisis indépendamment au moyen de l'attribut decls. proporciona atributos para los elementos contenidos en el encabezado que pueden ser seleccionados autónomamente mediante el atributo decls adecuado. - individua attributi per gli elementi contenuti nell'intestazione che possono essere selezionati autonomamente grazie all'apposito attributo decls - + individua attributi per gli elementi contenuti nell'intestazione che possono essere selezionati autonomamente grazie all'apposito attributo decls indicates whether or not this element is selected by default when @@ -20,8 +19,7 @@ its parent is selected. 그 부모가 선택될 때 기본값으로 이 요소가 선택되었는지를 표시한다. 當父元素被選擇時，指出此元素是否會被選擇。 親要素が選択された場合に、当該要素がデフォルトとして選択されるか - どうかを示す。 - + どうかを示す。 indique si oui ou non cet élément est affecté par défaut quand son élément parent a été sélectionné. indica si el elemento es seleccionado automáticamente o no cuando es seleccionado el padre diff --git a/P5/Source/Specs/att.dimensions.xml b/P5/Source/Specs/att.dimensions.xml index 2d79c3b0f9..1ea0303634 100644 --- a/P5/Source/Specs/att.dimensions.xml +++ b/P5/Source/Specs/att.dimensions.xml @@ -5,7 +5,7 @@ provides attributes for describing the size of physical objects. 물리적 대상의 크기를 기술하는 속성을 제공한다. 提供符合某種度量值的屬性值。 - 物理的対象の大きさを表す属性を示す。 + 物理的対象の大きさを表す属性を示す。 fournit des attributs pour décrire la taille des objets physiques assegna degli attributi che descrivono la grandezza di diff --git a/P5/Source/Specs/att.divLike.xml b/P5/Source/Specs/att.divLike.xml index 25b4efbb9c..7bcb893951 100644 --- a/P5/Source/Specs/att.divLike.xml +++ b/P5/Source/Specs/att.divLike.xml @@ -67,8 +67,7 @@ logique et doivent être traités dans l'ordre séquentiel 이 구역이 원본의 표본이며 어떤 부분인지를 나타낸다. 指出此區段是否為來源文件的樣本，若為樣本，則說明出自哪一部分。 当該区分が、元資料のものを含むかどうか、そうであればその場所はど - こかを示す。 - + こかを示す。 indique si cette division est un échantillon de la source originale et dans ce cas, de quelle partie. indica si la división es una muestra de la fuente original y, en ese caso, de que parte de este se trata @@ -81,8 +80,7 @@ logique et doivent être traités dans l'ordre séquentiel 구역이 원본의 후반부에서 제시된 자료가 부족하다. 區段的末端無資料 la división falta el material presente en el extremo en la fuente. - 当該区分は、元資料の終わりの部分が欠けている。 - + 当該区分は、元資料の終わりの部分が欠けている。 par rapport à la source, lacune à la fin de la division alla partizione testuale manca del materiale nella parte finale presente nell'originale @@ -91,8 +89,7 @@ logique et doivent être traités dans l'ordre séquentiel 구역이 초반부와 후반부 자료가 부족하다. 區段的起始與末端無資料 el fragmento carece de material al comienzo y al final. - 当該区分は、元資料の始めと終わりの部分が欠けている。 - + 当該区分は、元資料の始めと終わりの部分が欠けている。 par rapport à la source, lacune au début et à la fin de la division alla partizione testuale manca del materiale nella parte iniziale e in quella finale @@ -102,8 +99,7 @@ début et à la fin de la division 구역이 초반부 자료가 부족하다. 區段的起始部分無資料 el fragmento carece de material en el comienzo. - 当該区分は、元資料の始めの部分が欠けている。 - + 当該区分は、元資料の始めの部分が欠けている。 par rapport à la source, lacune au début de la division alla partizione manca del materiale nella parte iniziale @@ -113,8 +109,7 @@ début de la division 표본 자료의 원본 내의 위치를 알 수 없다. 來源文件中的樣本資料位置不明 ubicación del material de muestra dentro del original desconocido. - 元資料のどの部分かは不明。 - + 元資料のどの部分かは不明。 par rapport à la source, position de l'échantillon inconnue la posizione del materiale prelevato dall'originale all'interno di quest'ultimo è sconosciuta @@ -124,8 +119,7 @@ l'échantillon inconnue 구역이 표본이 아니다. 區段非樣本 el fragmento no es una muestra. - 当該領域は、元資料の一部ではない。 - + 当該領域は、元資料の一部ではない。 la division n'est pas un échantillon la partizione testuale non è stata prelevata da alcun originale diff --git a/P5/Source/Specs/att.duration.w3c.xml b/P5/Source/Specs/att.duration.w3c.xml index 9f0b36e673..b808592eb7 100644 --- a/P5/Source/Specs/att.duration.w3c.xml +++ b/P5/Source/Specs/att.duration.w3c.xml @@ -20,10 +20,8 @@ 時間幅 indicates the length of this element in time. 시간선상에서 이 요소의 길이를 나타낸다. - 指明此元素的時間長度。 - - 時間幅を示す。 - + 指明此元素的時間長度。 + 時間幅を示す。 indique la longueur de cet élément dans le temps indica la durata nel tempo di tale elemento diff --git a/P5/Source/Specs/att.duration.xml b/P5/Source/Specs/att.duration.xml index 5cc32e857f..e08bb07ea0 100644 --- a/P5/Source/Specs/att.duration.xml +++ b/P5/Source/Specs/att.duration.xml @@ -6,8 +6,7 @@ provides attributes for normalization of elements that contain datable events. 날짜를 정할 수 있는 사건을 포함하는 요소의 규격화를 위한 속성을 제공한다. 提供用於元素規格化的屬性，這些元素包含日期明確的事件。 - 時間事象を含む要素の正規化手法を表す属性を示す。 - + 時間事象を含む要素の正規化手法を表す属性を示す。 fournit des attributs pour la normalisation des éléments qui contiennent des mentions d'événements datables indica degli attributi per la normalizzazione di elementi che contengono eventi databili diff --git a/P5/Source/Specs/att.enjamb.xml b/P5/Source/Specs/att.enjamb.xml index 073c2b1104..231bcd1c58 100644 --- a/P5/Source/Specs/att.enjamb.xml +++ b/P5/Source/Specs/att.enjamb.xml @@ -36,8 +36,7 @@ 행이 끝을 맺는다. 該詩句在行尾結束 el verso contiene un punto y final. - 当該行が、最終である。 - + 当該行が、最終である。 le vers se termine à la fin de la ligne il verso finisce a fine riga diff --git a/P5/Source/Specs/att.entryLike.xml b/P5/Source/Specs/att.entryLike.xml index 4b11831056..4c60e2bb7b 100644 --- a/P5/Source/Specs/att.entryLike.xml +++ b/P5/Source/Specs/att.entryLike.xml @@ -72,8 +72,7 @@ esthete to aesthete). 다른 주 표제 항목을 지시하는 기능만을 수행하도록 제한된 표제 항목(예를 들어, 불규칙 동사형 또는 다양한 철자법; be를 지시하는 was, 또는 - aesthete를 지시하는 esthete - + aesthete를 지시하는 esthete 縮減的辭條，其唯一作用為指向另一個主要辭條 (例如不規則動辭形式或不同拼法的字) una breve entrada cuya única función es apuntar a otra entrada principal (p.ej. para formas de un verbo irregular o para otras variantes ortográficas: was señala a be, o esthete a aesthete). 相互参照。主項目への参照。例えば、不規則変化動詞の場合には、 diff --git a/P5/Source/Specs/att.gaijiProp.xml b/P5/Source/Specs/att.gaijiProp.xml index 8c396052dc..a42895fdf9 100644 --- a/P5/Source/Specs/att.gaijiProp.xml +++ b/P5/Source/Specs/att.gaijiProp.xml @@ -3,7 +3,7 @@ provides attributes for defining the properties of - non-standard characters or glyphs. + non-standard characters or glyphs. liefert Attribute zur Definition der Eigenschaften von nicht standardisierten Zeichen und Glyphen. fornisce attributi per definire le proprietà di caratteri o glifi non standard diff --git a/P5/Source/Specs/att.global.analytic.xml b/P5/Source/Specs/att.global.analytic.xml index 2dd56940c4..f35866df69 100644 --- a/P5/Source/Specs/att.global.analytic.xml +++ b/P5/Source/Specs/att.global.analytic.xml @@ -27,10 +27,8 @@ element on which the ana attribute appears. 属性anaを伴う要素の解釈を含む要素を示す。 indique un ou plusieurs éléments contenant des interprétations de l'élément qui porte l'attribut ana. - indica uno o más elementos que contienen interpretaciones del elemento en el cual aparece el atributo ana - - indica uno o più elementi che contengono interpretazioni dell'elemento specificato dall'attributo ana - + indica uno o más elementos que contienen interpretaciones del elemento en el cual aparece el atributo ana + indica uno o più elementi che contengono interpretazioni dell'elemento specificato dall'attributo ana diff --git a/P5/Source/Specs/att.global.responsibility.xml b/P5/Source/Specs/att.global.responsibility.xml index b3a09b3cc5..44f7eb1574 100644 --- a/P5/Source/Specs/att.global.responsibility.xml +++ b/P5/Source/Specs/att.global.responsibility.xml @@ -27,7 +27,7 @@ intervención o la interpretación. corrisponde al grado di certezza associato all'intervento o interpretazione - 介入や解釈に関する確信度を示す。 + 介入や解釈に関する確信度を示す。 diff --git a/P5/Source/Specs/att.global.xml b/P5/Source/Specs/att.global.xml index f3d180c526..0b0d877c83 100644 --- a/P5/Source/Specs/att.global.xml +++ b/P5/Source/Specs/att.global.xml @@ -5,7 +5,7 @@ provides attributes common to all elements in the TEI encoding scheme. TEI 부호화 스키마의 모든 요소에 공통 속성을 제공한다. 提供一組屬性，通用於TEI編碼標準中的所有元素。 - TEI符号化スキーム中の全要素に共通する属性を示す。 + TEI符号化スキーム中の全要素に共通する属性を示す。 fournit un jeu d'attributs communs à tous les éléments dans le système de codage TEI. proporciona un conjunto de atributos común a todos los @@ -107,16 +107,13 @@ 使用RFC3066的代碼，指出該元素內容的使用語言 BCP 47に従って生成されたタグを用いて要素の内容の言語を示す。 indique la langue du contenu de l'élément en - utilisant les codes du RFC 3066 - + utilisant les codes du RFC 3066 indica la lengua del contenido del elemento utilizando los códigos extraídos de RFC - 3066 - + 3066 indica la lingua del contenuto dell'elemento utilizzando i codici tratti da RFC - 3066 - + 3066 diff --git a/P5/Source/Specs/att.handFeatures.xml b/P5/Source/Specs/att.handFeatures.xml index c7a7c63184..07c0839da0 100644 --- a/P5/Source/Specs/att.handFeatures.xml +++ b/P5/Source/Specs/att.handFeatures.xml @@ -5,9 +5,8 @@ provides attributes describing aspects of the hand in which a manuscript is written. 원고가 쓰여진 필적의 측면을 기술하는 속성을 제공한다. - proporciona atributos que describen los aspectos de la mano que ha escrito un manuscrito. - 手書き資料の筆致に関する情報を表す情報を示す。 - + proporciona atributos que describen los aspectos de la mano que ha escrito un manuscrito. + 手書き資料の筆致に関する情報を表す情報を示す。 fournit des attributs décrivant les caractéristiques de la main par laquelle un manuscrit est écrit. indica degli attributi che descrivono aspetti delle mano utilizzata per la scrittura del manoscritto @@ -16,8 +15,7 @@ de la main par laquelle un manuscrit est écrit. gives a name or other identifier for the scribe believed to be responsible for this hand. 이 필적에 대한 책임이 있다고 간주되는 필기사에 대한 표준명 또는 다른 확인소를 제시한다. - 当該筆致に対応すると考えられる筆写者の名前またはその他の識別子を示す。 - + 当該筆致に対応すると考えられる筆写者の名前またはその他の識別子を示す。 donne un nom normalisé ou un autre identifiant pour le scribe reconnu comme responsable de cette main. assegna un nome o altro identificatore standard al trascrittore che si ritiene corrisponda alla mano in questione @@ -39,8 +37,7 @@ this hand, for example secretary, copperplate< えば、secretary(書記官スタイル)、 copperplate(銅板スタイル)、 Chancery(公文書スタイル)、 - Italian(イタリアスタイル)など。 - + Italian(イタリアスタイル)など。 caractérise la calligraphie ou le style d'écriture particuliers utilisés par cette main, par exemple écriture anglaise, de chancellerie, italienne, etc. @@ -59,24 +56,20 @@ this hand, typically supplied by a scriptNote element describes the tint or type of ink, e.g. brown, or other -writing medium, e.g. pencil - +writing medium, e.g. pencil brown와 같이 잉크의 색 또는 유형, 또는 pencil와 같이 글쓰기 방식 기술한다. インクの種類や色合い、例えば、茶色 - や、筆記具の種類、例えば、鉛筆など。 - + や、筆記具の種類、例えば、鉛筆など。 décrit la teinte ou le type d'encre, par exemple brune, ou un autre outil d'écriture, par exemple un crayon. - descrive la tinta o il tipo di inchiostro, per esempio marrone, o altri strumenti di scrittura, per esempio matita - + descrive la tinta o il tipo di inchiostro, per esempio marrone, o altri strumenti di scrittura, per esempio matita describe la tinta o el tipo de tinta, p.ej. marrón, u otros instrumentos de escritura, p.ej. lápiz. specifies how widely this hand is used in the manuscript. 이 필적이 원고에서 사용된 범위를 명시한다. - 当該筆致が、当該手書き資料中で、どの程度出現しているかを示す。 - + 当該筆致が、当該手書き資料中で、どの程度出現しているかを示す。 spécifie la fréquence d'apparition de cette main dans le manuscrit. specifica in quale misura è utilizzata la mano in questione nel manoscritto @@ -86,8 +79,7 @@ main dans le manuscrit. only this hand is used throughout the manuscript 이 필적만이 원고 전체에 사용되었다. - 当該筆致だけで全てが書かれている。 - + 当該筆致だけで全てが書かれている。 il n'y a que cette main dans le manuscrit. unica mano utilizzata nel manoscritto @@ -96,8 +88,7 @@ manuscrit. this hand is used through most of the manuscript 이 필적이 원고 대부분에서 사용되었다. - 当該筆致で、殆どが書かれている。 - + 当該筆致で、殆どが書かれている。 cette main est utilisée dans la majeure partie du manuscrit. mano utilizzata nella maggior parte del manoscritto @@ -106,8 +97,7 @@ majeure partie du manuscrit. this hand is used occasionally in the manuscript 이 필적이 원고에서 가끔 사용되었다. - 当該筆致で、所々が書かれている。 - + 当該筆致で、所々が書かれている。 cette main est utilisée occasionnellement dans le manuscrit. mano utilizzata solo di rado nel manoscritto diff --git a/P5/Source/Specs/att.internetMedia.xml b/P5/Source/Specs/att.internetMedia.xml index b0ae3c6564..a036741ed9 100644 --- a/P5/Source/Specs/att.internetMedia.xml +++ b/P5/Source/Specs/att.internetMedia.xml @@ -5,8 +5,7 @@ provides attributes for specifying the type of a computer resource using a standard taxonomy. 표준 분류법을 사용하는 컴퓨터 자원의 유형을 명시하는 속성을 제시한다. - 標準的な用語による計算機資源の種類を表す属性を示す。 - + 標準的な用語による計算機資源の種類を表す属性を示す。 fournit des attributs pour spécifier le type de ressource informatique selon une taxinomie normalisée. indica degli attributi che specificano il tipo di risorsa informatica utilizzando una tassonomia standard diff --git a/P5/Source/Specs/att.linguistic.xml b/P5/Source/Specs/att.linguistic.xml index ba3f7b3a8f..7e4d703e0c 100644 --- a/P5/Source/Specs/att.linguistic.xml +++ b/P5/Source/Specs/att.linguistic.xml @@ -94,8 +94,7 @@ (morphosyntactic description) supplies morphosyntactic information for a token, usually according to some official reference - vocabulary (e.g. for German: STTS-large tagset; for a feature description system designed as (pragmatically) universal, see Universal Features). - + vocabulary (e.g. for German: STTS-large tagset; for a feature description system designed as (pragmatically) universal, see Universal Features). diff --git a/P5/Source/Specs/att.measurement.xml b/P5/Source/Specs/att.measurement.xml index ed1b1a373e..dd410f70dd 100644 --- a/P5/Source/Specs/att.measurement.xml +++ b/P5/Source/Specs/att.measurement.xml @@ -5,8 +5,7 @@ provides attributes to represent a regularized or normalized measurement. 정상화 또는 규격화된 측정 방식을 표상하는 속성을 제시한다. 提供屬性，代表一般化或規格化的度量。 - 正規化単位を表す属性を示す。 - + 正規化単位を表す属性を示す。 donne des attributs pour représenter une mesure régularisée ou normalisée. proporciona atributos que representen una medición regularizada o normalizada. diff --git a/P5/Source/Specs/att.msClass.xml b/P5/Source/Specs/att.msClass.xml index a292aa60b7..0e16bbce7b 100644 --- a/P5/Source/Specs/att.msClass.xml +++ b/P5/Source/Specs/att.msClass.xml @@ -7,7 +7,7 @@ identifies the text types or classifications applicable to this item by pointing to other elements or resources defining the - classification concerned. + classification concerned. 이 항목에 적용할 수 있는 텍스트 유형 또는 분류를 식별한다. 標明適合的文字類型或分類。 関連する分類を定義する他の要素またはリソースを指すことによって、この項目に適用可能なテキストタイプまたは分類を特定する。 diff --git a/P5/Source/Specs/att.msExcerpt.xml b/P5/Source/Specs/att.msExcerpt.xml index 2c08f8654e..18806f3aa9 100644 --- a/P5/Source/Specs/att.msExcerpt.xml +++ b/P5/Source/Specs/att.msExcerpt.xml @@ -12,8 +12,7 @@ provides attributes used to describe excerpts from a manuscript placed in a description thereof. 원고의 발췌본을 기술하는 속성을 제시한다. 提供用來描述關於手稿摘錄的屬性 - 手書き資料からの引用を記述するための属性を示す。 - + 手書き資料からの引用を記述するための属性を示す。 fournit des attributs pour décrire les extraits d'un manuscrit. assegna degli attributi utilizzati per descrivere estratti di un manoscritto inseriti in una descrizione dello stesso proporciona atributos usados para describir extractos de un manuscrito ****** @@ -24,8 +23,7 @@ 인용 어구의 결합 여부를 표시한다. 즉, 손실 또는 손상을 통한 불완전성 指出所引用的段落是否不完全，例如因遺失或損毀而不完全。 当該部分に問題があるかどうかを示す。例えば、欠損や損傷による不完 - 全さなど。 - + 全さなど。 indique si le passage décrit est fautif, i.e. incomplet en raison d'une lacune ou d'une détérioration. indica se il brano citato sia o meno incompleto a causa di perdite o danni indica si el pasaje que se describe es completo o no, p.ej. si ha sufrido pérdidas o daños. diff --git a/P5/Source/Specs/att.pointing.group.xml b/P5/Source/Specs/att.pointing.group.xml index 608afc689e..275e4e3924 100644 --- a/P5/Source/Specs/att.pointing.group.xml +++ b/P5/Source/Specs/att.pointing.group.xml @@ -74,8 +74,7 @@ alt. describe la función de cada uno de los valores del atributo target (metas) de los marcadores correspondientes link, join, o alt. descrive la funzione di ognuno dei valori dell'attributo target dei marcatori corrispondenti link, - join, o alt - + join, o alt

The number of separate values must match the number of diff --git a/P5/Source/Specs/att.pointing.xml b/P5/Source/Specs/att.pointing.xml index be6706a871..f2ad538a07 100644 --- a/P5/Source/Specs/att.pointing.xml +++ b/P5/Source/Specs/att.pointing.xml @@ -95,8 +95,7 @@ 若指向的元素本身為指標，則該指標的目標會被移除，依此類推，直到找到一個非指標的元素為止。 si el elemento que señala a sí mismo es un indicador, entonces el target de ese indicador será tomado, y así sucesivamente, hasta que se encuentre un elemento que no sea un indicador. 参照先の要素がポインターである場合、そのポインターの参照先へ - と展開する。これを、参照先がポインターでなくなるまで続ける。 - + と展開する。これを、参照先がポインターでなくなるまで続ける。 si l'élément pointé est lui-même un pointeur, alors on prendra la cible de ce pointeur, et ainsi de suite jusqu'à trouver un élément qui n'est pas un pointeur. se l'elemento puntato è esso stesso un puntatore, allora sarà presa la destinazione di quel puntatore e così via fino a trovare un elemento che non è un puntatore @@ -108,8 +107,7 @@ 若指向的元素本身為指標，則該指標的目標(無論是否為指標)會作為這項指標的目標。 si el elemento que señala a sí mismo es un puntero, entonces el target (puntero o no) se toma como el target de este puntero. 参照先の要素がポインターである場合、(そのポインターの参照先 - がどうであれ)そのポインターが参照先になる。 - + がどうであれ)そのポインターが参照先になる。 si l'élément pointé est lui-même un pointeur, alors sa cible (qui est ou non un pointeur) devient la cible retenue. se l'elemento puntato è esso stesso un puntatore, allora la sua destinazione (che sia un puntatore o meno) è presa come destinazione del puntatore @@ -120,8 +118,7 @@ 포인터의 대상에서 명시된 요소를 발견할 필요가 없을 때 더 이상의 대상에 대한 평가는 수행되지 않는다. 尋找指標的目標元素時，未對目標進行不必要的延伸評估。 no se realiza ninguna otra evaluación de los targets más allá de la necesaria para encontrar el elemento especificado en el target del puntero. - 当該ポインターの参照先から先にあるリンクへの展開は行わない。 - + 当該ポインターの参照先から先にあるリンクへの展開は行わない。 aucune évaluation ultérieure des cibles n'est menée au-delà de la recherche de l'élément désigné dans la cible du pointeur. non viene condotta altra valutazione delle destinazioni se non quella necessaria a rintracciare l'elemento specificato nella destinazione del puntatore diff --git a/P5/Source/Specs/att.scoping.xml b/P5/Source/Specs/att.scoping.xml index 564e87fac2..20d70636ec 100644 --- a/P5/Source/Specs/att.scoping.xml +++ b/P5/Source/Specs/att.scoping.xml @@ -20,7 +20,7 @@ supplies an XPath selection pattern using the syntax defined in which identifies a set of nodes, selected within the context identified by the target attribute if this is supplied, or within the - context of the parent element if it is not. + context of the parent element if it is not. に定義された構文を用いて、ノードの集合を指し示す任意の XPath 式を記入する。 選択範囲は target 属性が与えられた場合はそのコンテクスト、 なければ親要素のコンテクストとなる。 diff --git a/P5/Source/Specs/att.tableDecoration.xml b/P5/Source/Specs/att.tableDecoration.xml index 32616a0f09..91cf2073c5 100644 --- a/P5/Source/Specs/att.tableDecoration.xml +++ b/P5/Source/Specs/att.tableDecoration.xml @@ -5,8 +5,7 @@ provides attributes used to decorate rows or cells of a table. 테이블의 행 또는 셀을 장식하는 속성을 제공한다. 提供屬性，用以裝飾表格內的儲存格或列。 - 表の行またはセルを修飾する属性を示す。 - + 表の行またはセルを修飾する属性を示す。 fournit des attributs pour mettre en forme les lignes ou les cellules d'un tableau. proporciona atributos usados para decorar filas o celdas de una tabla. assegna degli attributi utilizzati per decorare righe e celle di una tabella @@ -18,8 +17,7 @@ in each cell of this row. 이 셀에 또는 이 행의 각 셀에 나타난 정보의 종류를 제시한다. 指出此儲存格或列當中，各儲存格所包含的資訊類型。 - 当該セル、または当該行中のセルにある情報の種類を示す。 - + 当該セル、または当該行中のセルにある情報の種類を示す。 indique le type des informations contenues dans cette cellule ou dans chaque cellule de cette ligne. especifica el tipo de información contenida en la celda en cuestión o en cada una de las celdas de la fila. @@ -32,8 +30,7 @@ in each cell of this row. 표지 또는 기술적 정보만 허용 僅為標號或描述性資訊。 etiquetado o información descriptiva solamente. - 記述的情報またはラベルのみ。 - + 記述的情報またはラベルのみ。 uniquement des informations relatives au codage ou à la description informazione esclusivamente descrittiva o del tipo etichetta @@ -42,8 +39,7 @@ in each cell of this row. 데이터 값 數據值。 valores de datos. - 日付情報。 - + 日付情報。 valeurs de données valori di dati @@ -80,8 +76,7 @@ el atributo role (papel) del elemento padre row (fila).

indicates the number of rows occupied by this cell or row. 이 셀 또는 행에 의해 사용된 행의 수를 나타낸다. 指出此儲存格或列所占的列數。 - 当該セルまたは行を含む行の数を示す。 - + 当該セルまたは行を含む行の数を示す。 indique le nombre de lignes occupées par la cellule ou la ligne en question. indica el número de filas ocupado por una celda o por la fila en cuestión. indica il numero di righe occupate dalla cella o riga in questione @@ -116,8 +111,7 @@ to use nested tables.

row. 이 셀 또는 행에 의해 사용된 열의 수를 나타낸다. 指出此儲存格或列所佔的欄位數。 - 当該セルまたは行を含む列の数を示す。 - + 当該セルまたは行を含む列の数を示す。 indique le nombre de colonnes occupées par cette cellule ou cette ligne. indica el número de columnas que abraza una celda o fila. indica il numero di colonne occupate dalla cella o riga diff --git a/P5/Source/Specs/att.textCritical.xml b/P5/Source/Specs/att.textCritical.xml index 0a615ba848..32ca1a5dbc 100644 --- a/P5/Source/Specs/att.textCritical.xml +++ b/P5/Source/Specs/att.textCritical.xml @@ -89,8 +89,7 @@ sequence, when there is reason to presume a sequence to the variants. 어떤 연쇄를 임의의 레마에 관한 이문으로 추정하는 이유가 있을 때, 어떤 연쇄에서 이 독본의 위치를 나타내는 수를 제공한다. 當有理由假設任一主題的一系列變異對應本時，則提供一個數字，指出此對應本於連續系列中的位置。 1つの対象語に対する一連の異形を想定する理由がある場合、当該解釈 - がある場所を番号で示す。 - + がある場所を番号で示す。 fournit un nombre indiquant la position de la leçon dans une séquence, lorsqu'on peut supposer un ordre pour les variantes de chaque lemme. diff --git a/P5/Source/Specs/att.transcriptional.xml b/P5/Source/Specs/att.transcriptional.xml index af34c63c6c..ba8ce455a6 100644 --- a/P5/Source/Specs/att.transcriptional.xml +++ b/P5/Source/Specs/att.transcriptional.xml @@ -8,8 +8,7 @@ 원고 또는 유사 원본을 전사할 때 텍스트의 저작 또는 필사 간섭을 부호화하는 요소에 특징적으로 사용되는 속성을 제시한다. proporciona a los atributos específicos a los elementos que codifican la intervención authorial o scribal en un texto al transcribir el manuscrito o las fuentes similares. 手書き資料や同様の資料を転記する場合、著者や筆写者に関する調整を記録 - する要素に付与される属性を示す。 - + する要素に付与される属性を示す。 fournit des attributs spécifiques au codage d'éléments relatifs à l'intervention de l'auteur ou du copiste dans un texte lors de la transcription de sources manuscrites ou assimilées. @@ -23,8 +22,7 @@ transcription de sources manuscrites ou assimilées. 간섭을 만든 당사자의 필적을 나타낸다. - 当該調整を行った主体の筆致を特定する。 - + 当該調整を行った主体の筆致を特定する。 signale la main de celui qui est intervenue. indica il responsabile dell'aggiunta o della cancellazione indica el responsable de la adición o de la omisión. diff --git a/P5/Source/Specs/broadcast.xml b/P5/Source/Specs/broadcast.xml index 0c0d7d2f26..09c17d5091 100644 --- a/P5/Source/Specs/broadcast.xml +++ b/P5/Source/Specs/broadcast.xml @@ -8,8 +8,7 @@ décrit une émission utilisée comme source de la parole transcrite. 구어 텍스트의 원본으로 사용된 방송에 대해 기술한다. 描述口說文本的公開播送影音來源相關資訊。 - 発話されたテキストの元となる放送を示す。 - + 発話されたテキストの元となる放送を示す。 beschreibt eine Sendung, die als Quelle eines gesprochenen Textes genutzt wird describe la emisión usada como fuente de un texto escrito. diff --git a/P5/Source/Specs/castItem.xml b/P5/Source/Specs/castItem.xml index cb38befe7b..9994bcea02 100644 --- a/P5/Source/Specs/castItem.xml +++ b/P5/Source/Specs/castItem.xml @@ -48,7 +48,7 @@ either a single role or a list of non-speaking roles. 항목이 하나의 배역을 기술한다. 該項目為單一角色 el elemeto describe un único papel. - ひとつの役を示す。 + ひとつの役を示す。 l'item décrit un simple rôle. l'oggetto descrive un solo ruolo. diff --git a/P5/Source/Specs/catRef.xml b/P5/Source/Specs/catRef.xml index dc1d662095..005250e62d 100644 --- a/P5/Source/Specs/catRef.xml +++ b/P5/Source/Specs/catRef.xml @@ -38,8 +38,7 @@ 標明該分類架構，其中相關的類目群組已被定義 たとえばtaxonomy要素あるいはその他の資料によって、当該分類項目が定義されている分類スキームを同定する。 gibt das Klassifikationsschema an, in dem die entsprechenden Kategorien definiert sind, - z. B. über ein taxonomy-Element oder eine andere Ressource. - + z. B. über ein taxonomy-Element oder eine andere Ressource. indica el esquema de clasificación al interno del cual se define una serie de categorias referidas. identifica lo schema di classificazione all'interno diff --git a/P5/Source/Specs/change.xml b/P5/Source/Specs/change.xml index 6a0dc87069..2be3ccd442 100644 --- a/P5/Source/Specs/change.xml +++ b/P5/Source/Specs/change.xml @@ -76,7 +76,7 @@ Ziel 対象 points to one or more elements that belong to this change. - verweist auf ein oder mehrere Elemente, die zu dieser Änderung gehören. + verweist auf ein oder mehrere Elemente, die zu dieser Änderung gehören. この変更の対象となる一つ以上の要素を指す。 diff --git a/P5/Source/Specs/channel.xml b/P5/Source/Specs/channel.xml index 420031e21e..3185bcb2b5 100644 --- a/P5/Source/Specs/channel.xml +++ b/P5/Source/Specs/channel.xml @@ -66,7 +66,7 @@ for a spoken one, radio, telephone, face-to-face, etc. e.g. dictation 書き起こし 예, 받아쓰기 - 為寫而說 (例如聽寫) 　 + 為寫而說 (例如聽寫) p.ej. dictado 発話されたものを書いたもの。例えば書き起こしなど。 une dictée par exemple. @@ -82,7 +82,7 @@ for a spoken one, radio, telephone, face-to-face, etc. 台本 e.g. a script 예, 스크립트 - 為說而寫 (例如稿子) 　 + 為說而寫 (例如稿子) p.ej. un guión 書かれたものを発話したもの。例えば、台本など。 un script par exemple. diff --git a/P5/Source/Specs/citeStructure.xml b/P5/Source/Specs/citeStructure.xml index 78e0d86b2b..e28f94d93a 100644 --- a/P5/Source/Specs/citeStructure.xml +++ b/P5/Source/Specs/citeStructure.xml @@ -32,7 +32,7 @@ syntax defined in which identifies a set of nodes which are citable structural components. The expression may be absolute (beginning with /) or relative. match on a citeStructure without a citeStructure parent must be an absolute XPath. If it is - relative, its context is set by the match of the parent citeStructure. + relative, its context is set by the match of the parent citeStructure. diff --git a/P5/Source/Specs/classRef.xml b/P5/Source/Specs/classRef.xml index 3f8e68792d..1a83843b50 100644 --- a/P5/Source/Specs/classRef.xml +++ b/P5/Source/Specs/classRef.xml @@ -35,14 +35,13 @@ a single occurrence of one or more members - of the class may appear in sequence - + of the class may appear in sequence クラスの1つ以上のメンバーが順に1回ずつ出現し得る。 one or more occurrences of one or more members of the class - may appear in sequence. + may appear in sequence. クラスの1つまたは複数のメンバーが1回以上、順に出現し得る。 diff --git a/P5/Source/Specs/classSpec.xml b/P5/Source/Specs/classSpec.xml index a9a1c619ee..cf625aaf65 100644 --- a/P5/Source/Specs/classSpec.xml +++ b/P5/Source/Specs/classSpec.xml @@ -107,8 +107,7 @@ that is a group of members of the class are alternatives 부류의 원소들은 선택가능 항목이다. 該元素集的元素是替換元素 - 当該クラスの構成要素は、選択的である。 - + 当該クラスの構成要素は、選択的である。 les membres de la classe constituent des alternatives los miembros de las clase estan en relación de alternancia. @@ -118,8 +117,7 @@ that is a group of members of the class are to be provided in sequence 부류의 원소는 차례대로 제시된다. 該元素集的元素會依序呈現 - 当該クラスの構成要素は、リストとしてある。 - + 当該クラスの構成要素は、リストとしてある。 les membres de la classe doivent tous être donnés dans l'ordre indiqué los miembros de las clase se indican en secuencia. @@ -130,8 +128,7 @@ that is a group of but are optional 부류의 원소는 차례대로 제시될 수 있지만 수의적이다. 該元素集的元素可依序呈現，但非必須 - 当該クラスの構成要素は、リストから選択される。 - + 当該クラスの構成要素は、リストから選択される。 les membres de la classe peuvent être donnés, dans l'ordre indiqué, mais sont facultatifs los miembros de la clase pueden proporcionarse en modo de secuencia pero son opcionales. @@ -142,8 +139,7 @@ that is a group of times, in sequence, but are optional. 부류의 원소들은 한 번 이상 그리고 차례대로 제시될 수 있지만 수의적이다. 該元素集的元素可一次或多次依序呈現，但非必須 - 当該クラスの構成要素は、リストから1つ以上が選択される。 - + 当該クラスの構成要素は、リストから1つ以上が選択される。 les membres de la classe peuvent être donnés une ou plusieurs fois, dans l'ordre indiqué, mais sont facultatifs @@ -154,8 +150,7 @@ that is a group of members of the class may be provided one or more times, in sequence 부류의 원소들은 차례대로 한 번 이상 제시될 수 있다. 該元素集的元素可一次或多次依序呈現 - 当該クラスの構成要素は、リストから1つ以上が選択される。 - + 当該クラスの構成要素は、リストから1つ以上が選択される。 les membres de la classe doivent être donnés au moins une fois, dans l'ordre indiqué. miembros de la clase pueden ser indicados una o más veces en secuencia. diff --git a/P5/Source/Specs/classes.xml b/P5/Source/Specs/classes.xml index 600a936395..cb4fe11442 100644 --- a/P5/Source/Specs/classes.xml +++ b/P5/Source/Specs/classes.xml @@ -40,8 +40,7 @@ module parent. name in the current definition 이 선언은 현 정의에서 동일 이름의 선언을 변경한다. esta declaración cambia la declaración del mismo nombre en la definición actual - 当該宣言は、現行定義中にある同名宣言を修正する。 - + 当該宣言は、現行定義中にある同名宣言を修正する。 cette déclaration modifie la déclaration de même nom dans la définition courante. la dichiarazione modifica la dichiarazione con lo stesso nome nella definizione corrente @@ -51,8 +50,7 @@ déclaration de même nom dans la définition courante. name in the current definition 이 선언은 현 정의에서 동일 이름의 선언을 대체한다. esta declaración substituye la declaración del mismo nombre en la definición actual - 当該宣言は、現行定義中の同名宣言に置き換わる。 - + 当該宣言は、現行定義中の同名宣言に置き換わる。 cette déclaration remplace la déclaration de même nom dans la définition courante. la dichiarazione sostituisce la dichiarazione con lo stesso nome nella definizione corrente diff --git a/P5/Source/Specs/correspAction.xml b/P5/Source/Specs/correspAction.xml index 460d58f5f3..e3c2bdd2b9 100644 --- a/P5/Source/Specs/correspAction.xml +++ b/P5/Source/Specs/correspAction.xml @@ -8,8 +8,7 @@ description of the place, the name of a person/organization and the date related to the sending/receiving of a message or any other action related to the correspondence. - メッセージの送信・受信をはじめとする書簡に関する所作についての場所、人名／組織名、日付の構造的記述を含む。 - + メッセージの送信・受信をはじめとする書簡に関する所作についての場所、人名／組織名、日付の構造的記述を含む。 @@ -25,38 +24,32 @@ describes the nature of the action. - （書簡に関する）所作の性質を記述する。 - + （書簡に関する）所作の性質を記述する。 information concerning the sending or dispatch of a message. - メッセージの送信や発送に関する情報。 - + メッセージの送信や発送に関する情報。 information concerning the receipt of a message. - メッセージの受信に関する情報。 - + メッセージの受信に関する情報。 information concerning the transmission of a message, i.e. between the dispatch and the next receipt, redirect or forwarding. - メッセージの伝達手段に関する情報。発信とその後の受信・転送等の間の情報。 - + メッセージの伝達手段に関する情報。発信とその後の受信・転送等の間の情報。 information concerning the redirection of an unread message. - 〔開封せずに〕未読のままに転送されるメッセージに関する情報。 - + 〔開封せずに〕未読のままに転送されるメッセージに関する情報。 information concerning the forwarding of a message. - 〔開封後の〕メッセージの転送に関する情報。 - + 〔開封後の〕メッセージの転送に関する情報。 diff --git a/P5/Source/Specs/damageSpan.xml b/P5/Source/Specs/damageSpan.xml index 3f9e9bcdf4..ba545957d8 100644 --- a/P5/Source/Specs/damageSpan.xml +++ b/P5/Source/Specs/damageSpan.xml @@ -10,7 +10,7 @@ marks the beginning of a longer sequence of text which is damaged in some way but still legible. 어떤 방식으로 손상되었지만 여전히 읽을 수 있는 긴 텍스트 연쇄 시작부를 표시한다. marca el inicio de una secuencia de texto larga dañada de alguna manera pero aún legible. - 読める程度の損傷がある、一連のテキストの始点を示す。 + 読める程度の損傷がある、一連のテキストの始点を示す。 marque le début d'une longue partie de texte, endommagée d'une manière quelconque mais toujours lisible. segnala l'inizio di una sequenza più estesa di testo danneggiata ma ancora leggibile diff --git a/P5/Source/Specs/dataFacet.xml b/P5/Source/Specs/dataFacet.xml index 44799e9694..c3c76d57e5 100644 --- a/P5/Source/Specs/dataFacet.xml +++ b/P5/Source/Specs/dataFacet.xml @@ -3,8 +3,7 @@ Restricts the value of the strings used to represent values of a datatype, - according to XML Schema Part 2: Datatypes Second Edition. - + according to XML Schema Part 2: Datatypes Second Edition. diff --git a/P5/Source/Specs/dataRef.xml b/P5/Source/Specs/dataRef.xml index 5de6997ea0..142ee8db7f 100644 --- a/P5/Source/Specs/dataRef.xml +++ b/P5/Source/Specs/dataRef.xml @@ -37,7 +37,7 @@ the name of a datatype in the list provided by - XML Schema Part 2: Datatypes Second Edition + XML Schema Part 2: Datatypes Second Edition diff --git a/P5/Source/Specs/decoDesc.xml b/P5/Source/Specs/decoDesc.xml index 13a9317457..cedd9735c5 100644 --- a/P5/Source/Specs/decoDesc.xml +++ b/P5/Source/Specs/decoDesc.xml @@ -15,8 +15,7 @@ decoNoteで示す。 contient la description de la décoration du manuscrit, soit en une série de paragraphes p, soit sous la forme d'une série - d'éléments thématiques decoNote - + d'éléments thématiques decoNote contiene una descripción de la decoración de un manuscrito en forma de secuencia de párrafos o de secuencia de elementos decoNote organizados por el argumento. contiene una descrizione della decorazione di un manoscritto in forma di sequenza di paragrafi oppure di sequenza di elementi decoNote organizzati per argomento diff --git a/P5/Source/Specs/derivation.xml b/P5/Source/Specs/derivation.xml index 2bd0f6439e..f688b93532 100644 --- a/P5/Source/Specs/derivation.xml +++ b/P5/Source/Specs/derivation.xml @@ -36,8 +36,7 @@ 텍스트가 원본이다. 該文本為原創文本 el texto es original - 当該テキストはオリジナルである。 - + 当該テキストはオリジナルである。 le texte est un texte original. il testo è originale @@ -46,8 +45,7 @@ 텍스트가 다른 텍스트의 수정본이다. 該文本為另一文本的修訂版 el texto es una revisión de algún otro texto - 当該テキストは、他のテキストを元にした改訂である。 - + 当該テキストは、他のテキストを元にした改訂である。 le texte est une révision d'un autre texte. il testo è una revisione di qualche altro testo @@ -57,8 +55,7 @@ texte. 텍스트가 다른 텍스트의 번역본이다. 該文本為另一文本的翻譯版 el texto es una traducción de algún otro texto - 当該テキストは、他のテキストを翻訳したものである。 - + 当該テキストは、他のテキストを翻訳したものである。 le texte est une traduction d'un autre texte. il testo è la traduzione di qualche altro testo @@ -68,8 +65,7 @@ texte. 텍스가 다른 텍스트의 요약본이다. 該文本為另一文本的刪節版 el texto es una versión abreviada de algún otro texto - 当該テキストは、他のテキストを簡約したものである。 - + 当該テキストは、他のテキストを簡約したものである。 le texte est une version abrégée d'un autre texte. il testo è una versione ridotta di qualche altro testo @@ -79,8 +75,7 @@ autre texte. 텍스트가 다른 텍스트의 표절본이다. 該文本抄襲自另一文本 el texto es un plagio de algún otro texto - 当該テキストは、他のテキストを剽窃したものである。 - + 当該テキストは、他のテキストを剽窃したものである。 le texte est un plagiat d'un autre texte. il testo è un plagio di qualche altro testo @@ -92,8 +87,7 @@ texte. 該文本無明確來源，但和其他文本有共同的衍生來歷 el texto no tiene ninguna fuente obvia, pero es uno de los derivados de algún antepasado común 当該テキストは、元資料が不明であるが、何かしらを元にたテキス - トである。 - + トである。 le texte n'a pas de source évidente mais est l'un des nombreux textes dérivés d'un ancêtre commun. il testo è privo di una specifica fonte, ma è uno dei testi derivati da una fonte comune diff --git a/P5/Source/Specs/dimensions.xml b/P5/Source/Specs/dimensions.xml index ac54cc27cd..ab9558ec10 100644 --- a/P5/Source/Specs/dimensions.xml +++ b/P5/Source/Specs/dimensions.xml @@ -68,8 +68,7 @@ preparation for writing. 글쓰기를 준비하기 위해 줄 그은 종이 부분과 관련된 차원 頁面上劃好線以備書寫的範圍大小。 las dimensiones se refieren al área de una hoja que se ha preparado para la escritura. - 書記の準備として罫が引かれている領域を示す。 - + 書記の準備として罫が引かれている領域を示す。 les dimensions concernent la zone de la réglure d'une feuille. le dimensioni si riferiscono alla porzione di un foglio sulla quale sono state disegnate delle righe al fine di scriverci @@ -87,8 +86,7 @@ preparation for writing. 글의 첫 번째 줄 상단부터 마지막 줄 하단까지 측정된 높이를 통해 한 장의 글 쓴 영역과 관련된 차원 頁面上已書寫文字的範圍大小，高度由最頂行文字的頂端測量至最底行文字的底端。 las dimensiones se refiere al área de una hoja que ha sido escrita, con la altura medida desde la línea superior de escritura a la parte inferior de la última línea de la escritura. - 書記領域を示す。先頭文字行から最終文字行までの高さ。 - + 書記領域を示す。先頭文字行から最終文字行までの高さ。 les dimensions concernent la zone écrite de la feuille, dont la hauteur est mesurée depuis le haut des blancs sur la ligne d'écriture supérieure jusqu'au dernier des blancs sur la dernière ligne écrite. le dimensioni si riferiscono ad un'area del foglio su cui è stato scritto e la cui altezza è misurata dalla cima degli uncini sulla prima riga scritta fino al fondo degli uncini sull'ultima riga scritta @@ -97,8 +95,7 @@ preparation for writing. 원고의 축소형과 관련된 차원 手稿中圖畫的尺寸大小 las dimensiones relativas a las miniaturas del manuscrito - 当該手書き資料の彩飾図の大きさを示す。 - + 当該手書き資料の彩飾図の大きさを示す。 les dimensions concernent les miniatures contenues dans le manuscrit. le dimensioni si riferiscono alle miniature contenute nel manoscritto diff --git a/P5/Source/Specs/eLeaf.xml b/P5/Source/Specs/eLeaf.xml index 3824945b89..5c5c728542 100644 --- a/P5/Source/Specs/eLeaf.xml +++ b/P5/Source/Specs/eLeaf.xml @@ -13,8 +13,7 @@ be encoded with the eTree element. 내포 수형도의 단말 노드를 명시적으로 제공한다. 내포 수형도는 또한 eTree 요소로 부호화될 수 있다. 為嵌入樹狀結構的葉節點所明確提供的元素，也可用元素eTree來標記。 部分木における葉を示す。要素eTree中で使用される。 - la feuille d'un arbre englobant, qui peut aussi être encodée au moyen d'un élément eTree - + la feuille d'un arbre englobant, qui peut aussi être encodée au moyen d'un élément eTree proporciona explícitamente una hoja de un árbol integrado, que puede ser codificado también con el elemento eTree. definisce esplicitamente una foglia di un albero integrato, che può essere codificato anche con l'elemento eTree. diff --git a/P5/Source/Specs/epigraph.xml b/P5/Source/Specs/epigraph.xml index 6cfd54868f..88a07ed5ea 100644 --- a/P5/Source/Specs/epigraph.xml +++ b/P5/Source/Specs/epigraph.xml @@ -8,7 +8,7 @@ the start or end of a section or on a title page. 절 또는 장의 시작, 또는 제목 페이지에 나타나는 인용, 작자미상, 또는 추정을 포함한다. 包含一段匿名或署名引文，出現在段落或章節的開頭，或在題名頁中。 - 章や節の始め、タイトルページなどにある引用(題辞)を示す。 + 章や節の始め、タイトルページなどにある引用(題辞)を示す。 contient une citation, anonyme ou attribuée et qui apparaît au début d’une section ou d’un chapitre ou sur une page de titre. enthält ein anonymes oder jemandem zugeschriebenes Zitat, das am Beginn eines Abschnitts, diff --git a/P5/Source/Specs/equipment.xml b/P5/Source/Specs/equipment.xml index 8aacead70f..5ad1bcca2e 100644 --- a/P5/Source/Specs/equipment.xml +++ b/P5/Source/Specs/equipment.xml @@ -13,8 +13,7 @@ an audio or video recording used as the source for a spoken text. す。 gibt die technischen Details zu Geräteausstattung und Medien an, welche für die Ton- oder - Videoaufnahme als Quelle des gesprochenen Textes benutzt wurden - + Videoaufnahme als Quelle des gesprochenen Textes benutzt wurden proporciona detalles técnicos sobre el equipo y los medios empleados para la grabación de un audio o video usados como fuente de un texto hablado. fornisce dettagli tecnici sull'attrezzatura per una registrazione audio o video utilizzata quale fonte di un testo orale. diff --git a/P5/Source/Specs/facsimile.xml b/P5/Source/Specs/facsimile.xml index a97e0a346b..8b77367204 100644 --- a/P5/Source/Specs/facsimile.xml +++ b/P5/Source/Specs/facsimile.xml @@ -7,8 +7,7 @@ a set of images rather than as transcribed or encoded text. 전사 또는 부호화된 텍스트 형태보다는 이미지 집합의 형태로 기록 원본의 표상을 포함한다. contiene una representación de una cierta fuente escrita bajo la forma de conjunto de las imágenes algo que como texto transcrito o codificado. 転記または符号化されたテキストではなく、画像データ中にある、書記資料の -表現を示す。 - +表現を示す。 contient une représentation d'une source écrite quelconque sous la forme d'un ensemble d'images plutôt que sous la forme d'un texte transcrit ou encodé. diff --git a/P5/Source/Specs/factuality.xml b/P5/Source/Specs/factuality.xml index 8a664c5fa2..7ca7a480f4 100644 --- a/P5/Source/Specs/factuality.xml +++ b/P5/Source/Specs/factuality.xml @@ -38,8 +38,7 @@ or a non-fictional world. 텍스트가 전적으로 상상적이라 간주된다. 文本為完全虛構 el texto debe ser considerado como enteramente imaginativo - 当該テキストは、想像の産物である。 - + 当該テキストは、想像の産物である。 le texte est à considérer comme purement imaginaire. il testo deve essere considerato interamente fittizio @@ -49,8 +48,7 @@ purement imaginaire. 텍스트가 전적으로 정보적이거나 사실적이라고 간주된다. 文本完全根據事實 el texto debe ser considerado como enteramente informativo o efectivo - 当該テキストは、事実的なものである。 - + 当該テキストは、事実的なものである。 le texte est à considérer comme entièrement informatif ou basé sur des faits. il testo deve essere considerato interamente informativo e basato su fatti @@ -60,8 +58,7 @@ entièrement informatif ou basé sur des faits. 텍스트가 사실과 허구의 혼합이다. 文本內容部分虛構、部分根據事實 el texto contiene una mezcla de realidad y de ficción - 当該テキストは、フィクション、ノンフィクションが混在している。 - + 当該テキストは、フィクション、ノンフィクションが混在している。 le texte contient un mélange de faits et de fiction. il testo contiene un misto di fatti e finzione @@ -72,8 +69,7 @@ et de fiction. 사실과 허구의 구별은 이 텍스트에 적절치 않은 것으로 간주된다. 該文本不適宜使用虛構／真實的區分方法 la distinción ficción/realidad no se considera útil o apropiada para este texto - フィクション、ノンフィクションの区別は問題にならない。 - + フィクション、ノンフィクションの区別は問題にならない。 la distinction entre faits et fiction n'est pas considérée comme utile ou appropriée pour ce texte. la distinzione fittivo reale non è considerata utile o appropriata per il testo diff --git a/P5/Source/Specs/filiation.xml b/P5/Source/Specs/filiation.xml index 213c38dbb1..d993592327 100644 --- a/P5/Source/Specs/filiation.xml +++ b/P5/Source/Specs/filiation.xml @@ -15,8 +15,7 @@ connus du même texte, ses protographes, antigraphes et apographes. contiene información referente a la filiación de un manuscrito, p.ej. su relación con otros manuscritos supervivientes del mismo texto, es decir, sus protógrafos, antígrafos y apógrafos. - contiene informazioni relative alla filiazione del manoscritto, cioè la sua relazione con altri manoscritti sopravvissuti per lo stesso testo, cioè i suoi protografi, antigrafi e apografi - + contiene informazioni relative alla filiazione del manoscritto, cioè la sua relazione con altri manoscritti sopravvissuti per lo stesso testo, cioè i suoi protografi, antigrafi e apografi diff --git a/P5/Source/Specs/forename.xml b/P5/Source/Specs/forename.xml index 7ece8321bf..f5d91779c0 100644 --- a/P5/Source/Specs/forename.xml +++ b/P5/Source/Specs/forename.xml @@ -9,7 +9,7 @@ 包含名字或教名。 人物に与えられた名前のうち、名の部分、すなわち個人を表す部分を示す。 contient un prénom, qu'il soit donné ou un nom de baptême. - contiene el nombre de pila asignado en el bautismo. + contiene el nombre de pila asignado en el bautismo. contiene un prenome assegnato o un nome di battesimo diff --git a/P5/Source/Specs/fsDecl.xml b/P5/Source/Specs/fsDecl.xml index 80824faec2..0be1fce17d 100644 --- a/P5/Source/Specs/fsDecl.xml +++ b/P5/Source/Specs/fsDecl.xml @@ -57,8 +57,7 @@ derived by combining those specified explicitly within this element with those implied by the baseTypes attribute. When no baseTypes attribute is specified, no - feature specification or constraint is inherited. - + feature specification or constraint is inherited. 유형으로부터 상속받은 자질 명세와 제약으로 구성된 하나 이상의 유형화된 자질 구조의 이름을 제시한다; 만약 이 유형이 속성에 의해 명시된 것과 동일한 이름을 갖는 자질 명세를 포함한다면, 또는 동일 이름의 하나 이상의 명세가 상속된다면, 가능한 값의 집합은 통합에 의해 정의된다. 비슷하게 적용가능한 제약 집합이 baseTypes 속성에 의해 지시된 제약을 가진 요소 내에서 명백하게 명시된 제약의 결합에 의해 도출된다. baseTypes이 명시되지 않았다면, 어떤 자질 명세 또는 제약도 상속되지 않는다. 提供一個或多個已分類的功能結構名稱，此類型從該功能結構中獲得功能細節與限制；若該類型包含的功能細節名稱同於此屬性所標明的任一功能細節，或者該類型獲得一個以上同名的功能細節，則所有可能的屬性值是為統一定義。同樣地，適用限制的衍生，是將此元素中所明確標明的和屬性baseTypes所標明的結合。若未使用屬性baseTypes，則沒有獲得任何功能細節或限制。 ひとつ以上の素性構造を示す。ここから、属性typeは素性定義・制約を diff --git a/P5/Source/Specs/fsdDecl.xml b/P5/Source/Specs/fsdDecl.xml index f925669f9f..8493faefe1 100644 --- a/P5/Source/Specs/fsdDecl.xml +++ b/P5/Source/Specs/fsdDecl.xml @@ -17,8 +17,7 @@ ひとつ以上の素性構造宣言または素性構造宣言へのリンクを含む、素性シス テム宣言を示す。 bietet eine Deklaration des Merkmalsystems, die aus einer oder mehreren - Merkmalstrukturdeklarationen oder Links zu Merkmalstrukturdeklarationen besteht. - + Merkmalstrukturdeklarationen oder Links zu Merkmalstrukturdeklarationen besteht. indica la declaración del sistema de rasgos que contiene definiciones para un tipo particular de estructura de rasgos. identifica la dichiarazione del sistema di tratti che contiene le definifioni di un particolare tipo di struttura di tratti. diff --git a/P5/Source/Specs/fsdLink.xml b/P5/Source/Specs/fsdLink.xml index 47e2320be2..33d7abe57e 100644 --- a/P5/Source/Specs/fsdLink.xml +++ b/P5/Source/Specs/fsdLink.xml @@ -11,8 +11,7 @@ structure declaration for it. 자질 구조 선언에 유형화된 자질 구조의 이름을 관련시킨다. asocia el nombre de una estructura de rasgos dada con una declaración de la estructura de rasgos para ella. - 素性構造宣言により素性構造の名前を示す。 - + 素性構造宣言により素性構造の名前を示す。 associe le nom d'une structure de traits type à sa déclaration de structure de traits. associa il nome di una struttura di tratti alla dichiarazione relativa @@ -28,8 +27,7 @@ sa déclaration de structure de traits. feature structure. 기록된 자질 구조의 유형을 식별한다; 이것은 적어도 하나 이상의 자질 구조에 대한 유형 값이 될 것이다. 解説される素性構造を示す。少なくともひとつの素性構造に関する属性 - typeの値が付与される。 - + typeの値が付与される。 identifica il tipo di dichiarazione del sistema di tratti attraverso il FSD, sarà il valore dell'attributo type di almeno una struttura di tratti. identifica el tipo de estructura de rasgos documentada por el FSD; éste será el valor del atributo type al menos en una estructura de rasgos. identifie le type de structure de traits à documenter ; ce sera la valeur de l’attribut type d’au moins une structure de traits. @@ -40,8 +38,7 @@ feature structure. (fsDecl) element within the current document or elsewhere. 현 문서 내 또는 다른 문서에서 자질 구조 선언 (fsDecl) 요소에 대한 포인터를 제공한다. proporciona un puntero a una declaración de estructura de rasgos (elemento fsDecl) al interno del documento actual u otro. - 素性構造宣言要素(fsDecl)へのポインタが示される。 - + 素性構造宣言要素(fsDecl)へのポインタが示される。 fournit un pointeur vers un élément de déclaration de structure de traits (fsDecl) dans le document courant ou ailleurs. diff --git a/P5/Source/Specs/fw.xml b/P5/Source/Specs/fw.xml index 37927f3111..92c72bafb4 100644 --- a/P5/Source/Specs/fw.xml +++ b/P5/Source/Specs/fw.xml @@ -41,8 +41,7 @@ a running title at the top of the page 페이지 상단의 현 제목 頁面頂端的欄外標題 - 天にタイトル。 - + 天にタイトル。 un titre courant en haut de la page título o asunto en el encabezamiento de la página titolo nell'intestazione di pagina @@ -51,8 +50,7 @@ a running title at the bottom of the page 페이지 하단의 제목 頁面底端的欄外標題 - 地にあるタイトル。 - + 地にあるタイトル。 un titre courant en bas de la page título o asunto a pie de página titolo nel piè di pagina @@ -66,8 +64,7 @@ a page number or foliation symbol 페이지 숫자 또는 페이지 기호 編頁數號或是編張符號 - ノンブル。 - + ノンブル。 un numéro de page ou un symbole de foliotation numero di pagina o simbolo di foliazione número de página o símbolo de la foliación @@ -81,8 +78,7 @@ a line number, either of prose or poetry 산문 또는 시에서 행 번호 un número de línea, en prosa o verso - 韻文・散文における行番号。 - + 韻文・散文における行番号。 numéro d'une ligne en prose ou en vers numero di riga di testo in prosa o componimento poetico @@ -95,8 +91,7 @@ 서명 혹은 서명 기호 signature ou marque de cahier 簽名或是聚集符號 - 折丁記号。 - + 折丁記号。 firma o símbolo común firma o simbolo comune @@ -109,8 +104,7 @@ a catch-word 색인어 標語 - 柱。 - + 柱。 une réclame reclamo reclamo diff --git a/P5/Source/Specs/graph.xml b/P5/Source/Specs/graph.xml index 4a6ed4df6b..88163cd22c 100644 --- a/P5/Source/Specs/graph.xml +++ b/P5/Source/Specs/graph.xml @@ -65,8 +65,7 @@ connect the nodes. 무방향 그래프 無方向圖形 gráfico no-dirigido - 無向グラフ。 - + 無向グラフ。 graphe non orienté. grafo non orientato @@ -75,8 +74,7 @@ connect the nodes. 방향 그래프 有方向圖形 gráfico dirigido - 有向グラフ。 - + 有向グラフ。 graphe orienté. grafo orientato @@ -85,8 +83,7 @@ connect the nodes. 시작과 종료 노드가 구분되는 방향 그래프 清楚標明起始節點與末端節點的有向圖形 un gráfico dirigido con los nodos iniciales y finales distinguidos - 遷移ネットワーク。初期ノードと最終ノードを分けた有向グラフ。 - + 遷移ネットワーク。初期ノードと最終ノードを分けた有向グラフ。 un graphe orienté avec un nœud initial et un nœud terminal bien distincts. grafo orientato con nodi finale e iniziale distinti. @@ -96,8 +93,7 @@ connect the nodes. 각 호에 두 개의 표지를 부착한 전이망 每條連線上最多兩個標籤的過境網絡 una red de transición con hasta dos escrituras de la etiqueta en cada arco - トランスデューサ。各矢に高々2つのラベルを持つ遷移ネットワーク。 - + トランスデューサ。各矢に高々2つのラベルを持つ遷移ネットワーク。 un réseau de transition avec jusqu'à deux étiquettes par arc. rete di transizione con un massimo di due etichette per arco diff --git a/P5/Source/Specs/heraldry.xml b/P5/Source/Specs/heraldry.xml index 157d67fe9f..a336171bb4 100644 --- a/P5/Source/Specs/heraldry.xml +++ b/P5/Source/Specs/heraldry.xml @@ -5,8 +5,7 @@ heraldry héraldique contains a heraldic formula -or phrase, typically found as part of a blazon, coat of arms, etc. - +or phrase, typically found as part of a blazon, coat of arms, etc. 보통 문장이 새겨진 방패의 일부로 사용되는 문장 형식 또는 구를 포함한다. 包含一個紋章學的常規或詞彙，通常是裝飾、或盾形紋章等的一部分。 紋章学的記述を含む。例えば、紋章記述や紋章など。 diff --git a/P5/Source/Specs/idno.xml b/P5/Source/Specs/idno.xml index c83b3b4e19..04b262782b 100644 --- a/P5/Source/Specs/idno.xml +++ b/P5/Source/Specs/idno.xml @@ -101,8 +101,7 @@ International Standard Book Number: a 13- or (if assigned prior to 2007) 10-digit identifying number assigned by the publishing - industry to a published book or similar item, registered with the International ISBN Agency. - + industry to a published book or similar item, registered with the International ISBN Agency. International Standard Serial Number: an diff --git a/P5/Source/Specs/incident.xml b/P5/Source/Specs/incident.xml index 8863718002..cc7bd3d303 100644 --- a/P5/Source/Specs/incident.xml +++ b/P5/Source/Specs/incident.xml @@ -10,8 +10,7 @@ communication. 예를 들어 일시적인 소음 또는 의사소통에 영향을 미치는 다른 사건과 같이, 현상 또는 발생이지만 반드시 목소리나 의사소통을 수반하지는 않는다. 必ずしも言語化またはコミュニケーションには上らない現象や出来事を示す。 例えば、偶発的な雑音またはコミュニケーションに影響を与える他の事象な - ど。 - + ど。 tout phénomène ou événement, non nécessairement vocalisé ou destiné à la communication, par exemple des bruits fortuits ou d'autres événements affectant la communication diff --git a/P5/Source/Specs/incipit.xml b/P5/Source/Specs/incipit.xml index a3db06c937..91513d7b05 100644 --- a/P5/Source/Specs/incipit.xml +++ b/P5/Source/Specs/incipit.xml @@ -9,8 +9,7 @@ ストの書き出しにある語句で、これに先行してある朱書き部分を除いた、当 該作品を特定するに充分な文量の部分である。 冒頭語句は、タイトル部分において、作品への参照を示す手段としてよく使 - 用されていた。 - + 用されていた。 contient l'incipit d'une section d'un manuscrit, c'est-à-dire les mots commençant le texte proprement dit, à l'exclusion de toute rubrique qui pourrait les précéder, la transcription étant de longueur diff --git a/P5/Source/Specs/interaction.xml b/P5/Source/Specs/interaction.xml index 34ec2d8803..563dcf4915 100644 --- a/P5/Source/Specs/interaction.xml +++ b/P5/Source/Specs/interaction.xml @@ -43,8 +43,7 @@ form of response or interjection, commentary, etc. 종류의 상호작용이 없다. 예, 독백. 無任何互動，例如獨白 no hay ninguna interacción de ningún tipo, p.ej. un monólogo - 相互作用ではない。例えば、独白など。 - + 相互作用ではない。例えば、独白など。 pas la moindre interaction, un monologue par exemple. mancanza di qualsiasi interazione, ad esempio un monologo @@ -54,8 +53,7 @@ monologue par exemple. 어느 정도의 상호작용, 예, 고정된 반응을 유발하는 독백 某種程度上的互動，例如具有背景回應的獨白 cierto grado de interacción, p.ej. un monólogo con las respuestas de grupo - ある程度の相互作用。例えば、反応する人がいる状況での独白など。 - + ある程度の相互作用。例えば、反応する人がいる状況での独白など。 un certain degré d'interaction, par exemple un monologue avec une série de réponses. qualche grado di interazione, ad esempio un monologo con risposte stabilite @@ -65,8 +63,7 @@ exemple un monologue avec une série de réponses. 완전한 상호작용, 예, 대면 대화 完全性的互動，例如面對面交談 interacción completa, p.ej. una conversación cara a cara - 完全なる相互作用。例えば、直接対話など。 - + 完全なる相互作用。例えば、直接対話など。 une interaction complète, par exemple une conversation en tête-à-tête. interazione completa. ad esempio conversazione faccia a faccia @@ -76,8 +73,7 @@ une conversation en tête-à-tête. 이 매개변인은 이 경우에 부적절하거나 적용불가능하다. 這項特性在此不適當或不適用 este parámetro es inadecuado o inaplicable en este caso - 当該パラメータは、不適切、または使用が相応しくない。 - + 当該パラメータは、不適切、または使用が相応しくない。 ce paramètre est inapproprié ou inapplicable dans ce cas. il parametro è inappropriato o inapplicabile in questo caso @@ -101,8 +97,7 @@ inapplicable dans ce cas. 단일 화자 一位傳達者 un solo interlocutor - 個人の参加者。 - + 個人の参加者。 un seul émetteur. un singolo partecipante attivo @@ -111,8 +106,7 @@ inapplicable dans ce cas. 다수의 화자 多位傳達者 muchos interlocutores - 複数の参加者。 - + 複数の参加者。 plusieurs émetteurs. molti partecipanti attivi @@ -121,8 +115,7 @@ inapplicable dans ce cas. 집단적 화자 集體傳達者 un interlocutor colectivo - 団体としての参加者。 - + 団体としての参加者。 un émetteur collectif. un partecipante attivo collettivo @@ -131,8 +124,7 @@ inapplicable dans ce cas. 미지의 또는 미명시된 화자의 수 傳達人數未知或未指明 número de interlocutores desconocidos o inespecificables - 参加者は不明または特定不可能。 - + 参加者は不明または特定不可能。 un nombre d'émetteurs inconnu ou impossible à spécifier. un numero di partecipanti attivi sconosciuto o non specificabile @@ -158,8 +150,7 @@ impossible à spécifier. 텍스트가 창작자에게 전달된다. 예, 일기. 文本內容傳遞給原創作者，例如日記 el texto se dirige a su creador, p.ej. un diario - テキストは作成者に向けられたもの。例えば、日記など。 - + テキストは作成者に向けられたもの。例えば、日記など。 le texte est adressé à soi-même, comme un journal intime par exemple. il testo è indirizzato a colui chè l'ha prodotto, ad esempio un diario @@ -169,8 +160,7 @@ un journal intime par exemple. 텍스트가 다른 한 사람에게 전달된다. 예, 개인적 편지 文本內容傳遞給另一個人，例如私人信件 el texto se dirige a cualquier otra persona, p.ej. una carta personal - テキストは他の人物に向けられたもの。例えば、個人書簡など。 - + テキストは他の人物に向けられたもの。例えば、個人書簡など。 le texte est adressé à une seule autre personne, comme une lettre personnelle par exemple. il testo è indirizzato ad una sola altra persona, ad esempio una lettera privata diff --git a/P5/Source/Specs/langKnowledge.xml b/P5/Source/Specs/langKnowledge.xml index 83e50c9602..5c76e41a1d 100644 --- a/P5/Source/Specs/langKnowledge.xml +++ b/P5/Source/Specs/langKnowledge.xml @@ -13,11 +13,9 @@ synthétise l'état des connaissances linguistiques d'une personne, soit en texte libre soit par une liste d'éléments langKnown. resume los conocimientos lingüísticos de una persona de forma descriptiva o a través de una lista de - elementos langKnown - + elementos langKnown riassume la conoscenza linguistica di una persona in forma descrittiva o tramite una lista di elementi - langKnown - + langKnown diff --git a/P5/Source/Specs/listForest.xml b/P5/Source/Specs/listForest.xml index 6aaafc3d48..f972862f78 100644 --- a/P5/Source/Specs/listForest.xml +++ b/P5/Source/Specs/listForest.xml @@ -20,8 +20,7 @@ identifies the type of the forest group. 수형도군의 유형을 식별한다. 標明森林群組的類型。 - 当該森集合の種類を示す。 - + 当該森集合の種類を示す。 précise le type du groupe de forêts. identifica el tipo de grupo de bosque identifica il tipo di gruppo di foresta diff --git a/P5/Source/Specs/listNym.xml b/P5/Source/Specs/listNym.xml index da5d7390d5..50358658e0 100644 --- a/P5/Source/Specs/listNym.xml +++ b/P5/Source/Specs/listNym.xml @@ -10,7 +10,7 @@ contains a list of nyms, that is, standardized names for any thing. 어떤 사물에 대한 표준화된 이름 목록을 포함한다. 包含一正式名稱列表，即任何事物的標準名稱。 - 別名、すなわち、一般的に使われている名前のリストを示す。 + 別名、すなわち、一般的に使われている名前のリストを示す。 contient une liste de noms normalisés pour tous types d'objets. contiene una lista di nym, cioè nomi standard per qualsiasi cosa contiene una lista de nyms, es decir, nombres estándard para cualquier cosa. diff --git a/P5/Source/Specs/listOrg.xml b/P5/Source/Specs/listOrg.xml index 180007e8cc..64e174fa57 100644 --- a/P5/Source/Specs/listOrg.xml +++ b/P5/Source/Specs/listOrg.xml @@ -12,7 +12,7 @@ 식별 가능한 조직에 관한 정보를 제공하며, 각각에 대한 기술 목록을 포함한다. contiene una lista de descripciones, que proporciona a la información sobre una organización identificable. - 特定可能な団体に関する情報を示す解説のリストを示す。 + 特定可能な団体に関する情報を示す解説のリストを示す。 contient une liste d'éléments, chacun d'eux fournissant des informations sur une organisation identifiable. contiene una lista di descrizioni, ognuna delle quali diff --git a/P5/Source/Specs/mapping.xml b/P5/Source/Specs/mapping.xml index c83d52d505..fc8f2c6bc8 100644 --- a/P5/Source/Specs/mapping.xml +++ b/P5/Source/Specs/mapping.xml @@ -11,8 +11,7 @@ contains one or more characters which are related to the parent character or glyph in some respect, as specified by the type - attribute. - + attribute. type 상위 문자 또는 그림 문자와 관련된 하나 이상의 문자들을 포함한다. 속성으로 명시된다. 包含與父文字或字體在某方面有所關聯的一個或多個文字，在屬性type中加以說明。 属性typeで示される、親文字またはグリフと関連する、ひとつ diff --git a/P5/Source/Specs/metDecl.xml b/P5/Source/Specs/metDecl.xml index 67e137bd56..985537c340 100644 --- a/P5/Source/Specs/metDecl.xml +++ b/P5/Source/Specs/metDecl.xml @@ -132,8 +132,7 @@ declaration applies to the rhyme scheme recorded on the rhyme attribute 선언은 rhyme 속성에 기록된 운 스키마에 적용한다. la declaración se aplica al esquema de rima - registrado en el atributo rima - + registrado en el atributo rima 属性rhymeにある押韻スキームに該当する。 la déclaration s'applique à la structure métrique abstraite notée par l'attribut diff --git a/P5/Source/Specs/model.choicePart.xml b/P5/Source/Specs/model.choicePart.xml index 8e7c47914f..24e7853175 100644 --- a/P5/Source/Specs/model.choicePart.xml +++ b/P5/Source/Specs/model.choicePart.xml @@ -9,13 +9,11 @@ 匯集的元素 (而非選擇本身) 可用於元素choice之替換 要素choice中に現れる(要素choice以外の)要素をまとめ る。 regroupe des éléments (autres que choice) qui - peuvent être utilisés en alternance avec choice - + peuvent être utilisés en alternance avec choice agrupa los elementos (excluída el propio elemento choice) que pueden ser usados en alternancia con choice. raggruppa gli elementi (escluso l'elemento choice) che - possono essere usati in alternanza con choice - + possono essere usati in alternanza con choice diff --git a/P5/Source/Specs/model.formPart.xml b/P5/Source/Specs/model.formPart.xml index f0c8385f9c..b63dee8db9 100644 --- a/P5/Source/Specs/model.formPart.xml +++ b/P5/Source/Specs/model.formPart.xml @@ -11,8 +11,7 @@ agrupa los elementos permitidos al interno de un elemento form en un diccionario. in un dizionario, raggruppa gli elementi ammesi - all'inerno di un elemento form - + all'inerno di un elemento form diff --git a/P5/Source/Specs/model.pPart.editorial.xml b/P5/Source/Specs/model.pPart.editorial.xml index 0cf401ddf3..bd9c719f61 100644 --- a/P5/Source/Specs/model.pPart.editorial.xml +++ b/P5/Source/Specs/model.pPart.editorial.xml @@ -5,8 +5,7 @@ groups phrase-level elements for simple editorial interventions that may be useful both in transcribing and in authoring. 전사와 저작 모두에서 유용할 수 있는 간단한 편집 간섭에 대한 구-층위 요소를 모아 놓는다. - 匯集的詞組層次元素用於簡單的編輯更正，且有助於轉錄和編寫 - + 匯集的詞組層次元素用於簡單的編輯更正，且有助於轉錄和編寫 転記や編集の両方で使用される、単純な編集上の調整を示す、句レベルの要 素をまとめる。 regroupe des éléments de niveau expression, utilisés pour de diff --git a/P5/Source/Specs/model.xml b/P5/Source/Specs/model.xml index d09274f70f..d06cb1be81 100644 --- a/P5/Source/Specs/model.xml +++ b/P5/Source/Specs/model.xml @@ -145,7 +145,7 @@ if url is present, uses it to - display graphic, else display a placeholder image. + display graphic, else display a placeholder image. @@ -167,7 +167,7 @@ - creates a heading. + creates a heading. diff --git a/P5/Source/Specs/occupation.xml b/P5/Source/Specs/occupation.xml index 43dc51d239..cc29459fde 100644 --- a/P5/Source/Specs/occupation.xml +++ b/P5/Source/Specs/occupation.xml @@ -94,8 +94,7 @@ identifica un código relativo a la ocupación definido en el sistema de clasificación o taxonomía establecido por el atributo scheme. corrisponde a un codice relativo all'occupazione definito nel sistema di classificazione o - tassonomia stabiliti dall'attributo scheme - + tassonomia stabiliti dall'attributo scheme diff --git a/P5/Source/Specs/param.xml b/P5/Source/Specs/param.xml index 03bd44bb62..da9a19d2dc 100644 --- a/P5/Source/Specs/param.xml +++ b/P5/Source/Specs/param.xml @@ -19,13 +19,13 @@ when used with behaviour alternate, a parameter of this name supplies one of the pair of possible values; for example the regularized form rather than the original form within a - choice element. + choice element. when used with behaviour alternate, a parameter of this name supplies one of the pair of possible values; for example the original form rather than the regularized form within a - choice element. + choice element. - + link. when used with the note behaviour, a parameter of this name should provide a string which describes the intended placement of some text; typical values include margin, footnote, endnote, - inline, bottom + inline, bottom a parameter of this name can be used to categorize the specified behaviour in any way; for example the kind of break (when used with the break behaviour) or the kind of index to be generated (if used - with the index behaviour) etc. + with the index behaviour) etc. when used with behaviour diff --git a/P5/Source/Specs/reg.xml b/P5/Source/Specs/reg.xml index b1018de842..ee0076107b 100644 --- a/P5/Source/Specs/reg.xml +++ b/P5/Source/Specs/reg.xml @@ -20,7 +20,7 @@ normalizada en algún sentido. contiene una lettura è stata regolarizzata o normalizzata in qualche modo. - enthält eine normalisierte Schreibweise einer Textstelle. + enthält eine normalisierte Schreibweise einer Textstelle. diff --git a/P5/Source/Specs/respons.xml b/P5/Source/Specs/respons.xml index 50a01c8c01..6d50c9d8dd 100644 --- a/P5/Source/Specs/respons.xml +++ b/P5/Source/Specs/respons.xml @@ -155,8 +155,7 @@ markup of particular element(s). Ashley did not know what to do with this; I have decided it - best fits as a braced spGrp - + best fits as a braced spGrp fixed rend attributes diff --git a/P5/Source/Specs/rhyme.xml b/P5/Source/Specs/rhyme.xml index 44c9cc969f..c38ee68f1c 100644 --- a/P5/Source/Specs/rhyme.xml +++ b/P5/Source/Specs/rhyme.xml @@ -27,8 +27,7 @@ 当該押韻が起こる韻スキーム部分を特定するラベルを示す。 donne une étiquette pour identifier à quelle shéma métrique correspond cette alternance de rimes. - proporciona una etiqueta (normalmente una sola letra) que identifica qué parte del esquema métrico ejemplifica esta cadena de caracteres en cuestión. - + proporciona una etiqueta (normalmente una sola letra) que identifica qué parte del esquema métrico ejemplifica esta cadena de caracteres en cuestión. fornisce un'etichetta che identifica quale parte dello schema rimico è rappresentata dalla stringa in questione diff --git a/P5/Source/Specs/sealDesc.xml b/P5/Source/Specs/sealDesc.xml index 54905c1d4f..a1ce8733dc 100644 --- a/P5/Source/Specs/sealDesc.xml +++ b/P5/Source/Specs/sealDesc.xml @@ -18,8 +18,7 @@ d'éléments seal, complétés éventuellement par des éléments decoNote. describe los sellos u otros objetos externos aplicados a un manuscrito mediante una serie de párrafos o una serie de diversos elementos seal (sellos), eventualmente con ulteriores elementos decoNote. descrive i sigilli o altri oggetti esterni applicati a un manoscritto sotto forma di una sequenza di paragrafi o una serie di diversi elementi seal, -eventualmente con ulteriori elementi decoNote - +eventualmente con ulteriori elementi decoNote diff --git a/P5/Source/Specs/secFol.xml b/P5/Source/Specs/secFol.xml index 63f765eaa3..c33f2d40b9 100644 --- a/P5/Source/Specs/secFol.xml +++ b/P5/Source/Specs/secFol.xml @@ -8,8 +8,7 @@ segundo folio deuxième folio secondo foglio - marks the word or words taken from a fixed point in a codex (typically the beginning of the second leaf) in order to provide a unique identifier for it. - + marks the word or words taken from a fixed point in a codex (typically the beginning of the second leaf) in order to provide a unique identifier for it. 고유한 확인소를 제공하기 위해 미제본 원고의 고정 위치(일반적으로 두 번째 장의 시작)에서 얻어진 단어 또는 단어군 從手抄本中固定位置所拿開的一個或多個字 (通常在第二張書頁的開頭) ，目的是提供一個專有的識別符號。 ユニークな識別子を示すために、冊子中の特定点にある単語を示す。 diff --git a/P5/Source/Specs/socecStatus.xml b/P5/Source/Specs/socecStatus.xml index 686b51cf0c..24f7724434 100644 --- a/P5/Source/Specs/socecStatus.xml +++ b/P5/Source/Specs/socecStatus.xml @@ -79,8 +79,7 @@ identifica un código relativo a la condición socio-económica definido en el sistema de clasificación o taxonomía establecidos por el attributo source. corrisponde a un codice relativo alla condizione socio-economica definito nel sistema di - classificazione o tassonomia stabiliti dall'attributo source - + classificazione o tassonomia stabiliti dall'attributo source diff --git a/P5/Source/Specs/sourceDesc.xml b/P5/Source/Specs/sourceDesc.xml index 4a1dc421ec..045330b3bd 100644 --- a/P5/Source/Specs/sourceDesc.xml +++ b/P5/Source/Specs/sourceDesc.xml @@ -20,7 +20,7 @@ 電子テキストが作られた元テキストの情報を示す。 beschreibt die Quelle, von der sich der elektronische Text ableitet. Üblicherweise eine bibliografische Beschreibung im Falle eines digitalisierten Textes oder eine Bezeichnung wie - born digital für einen nur in elektronischer Form vorliegenden Text. + born digital für einen nur in elektronischer Form vorliegenden Text. proporciona una descripción del texto (o textos) fuente del que un texto electrónico deriva o ha sido generado. fornisce una descrizione relativa alla o alle fonti da diff --git a/P5/Source/Specs/spanGrp.xml b/P5/Source/Specs/spanGrp.xml index 4ce6c45c43..a117d5daca 100644 --- a/P5/Source/Specs/spanGrp.xml +++ b/P5/Source/Specs/spanGrp.xml @@ -12,8 +12,7 @@ 범위 태그를 모아놓는다. 匯集文字段標籤。 要素spanをまとめる。 - regroupe des éléments span - + regroupe des éléments span Agrupa las etiquetas del periodo raggruppa i marcatori di porzione diff --git a/P5/Source/Specs/standOff.xml b/P5/Source/Specs/standOff.xml index ca33308b78..734299c579 100644 --- a/P5/Source/Specs/standOff.xml +++ b/P5/Source/Specs/standOff.xml @@ -3,7 +3,7 @@ Functions as a container element for linked data, contextual information, and stand-off annotations embedded in a TEI document. - リンクト・データや文脈情報、TEI文書に埋め込まれたスタンドオフ・アノテーションをコンテナ化する要素として機能する。 + リンクト・データや文脈情報、TEI文書に埋め込まれたスタンドオフ・アノテーションをコンテナ化する要素として機能する。 diff --git a/P5/Source/Specs/surface.xml b/P5/Source/Specs/surface.xml index 1583ed2125..bedf912ee6 100644 --- a/P5/Source/Specs/surface.xml +++ b/P5/Source/Specs/surface.xml @@ -8,8 +8,7 @@ that space, zones of interest within that space, and, when using an embedded tra 직사각형의 좌표 공간과 그 내부에서 기록 표면부를 정의한다. 수의적으로 그 공간의 하나 이상의 그림 표상과 관심 있는 직사각형 공간을 모아놓는다. define una superficie escrita en coordinadas rectangulares, agrupando opcionalmente una o más representaciones gráficas de ese espacio, y las zonas rectangulares de interés dentro de él. 矩形の座標により、書記の表面を定義する。選択的に、空間や矩形範囲中のひ -とつ以上の図表表現をまとめる。 - +とつ以上の図表表現をまとめる。 définit une surface écrite comme un rectangle décrit par ses coordonnées spatiales, en regroupant éventuellement une ou plusieurs représentations graphiques de cet espace et des zones rectangulaires intéressantes à l'intérieur de celui-ci. diff --git a/P5/Source/Specs/teidata.count.xml b/P5/Source/Specs/teidata.count.xml index 2c9ac37563..ae324402b4 100644 --- a/P5/Source/Specs/teidata.count.xml +++ b/P5/Source/Specs/teidata.count.xml @@ -5,8 +5,7 @@ defines the range of attribute values used for a non-negative integer value used as a count. 계산으로 사용된 음이 아닌 정수 값의 속성 값 범위를 정의한다. - 定義的屬性值範圍，用於作為總數的非負整數值 - + 定義的屬性值範圍，用於作為總數的非負整數值 非負整数値を採る属性値の範囲を定義する。 définit la gamme des valeurs des attributs exprimant une valeur entière et non négative utilisé pour des calculs. diff --git a/P5/Source/Specs/teidata.duration.iso.xml b/P5/Source/Specs/teidata.duration.iso.xml index 84bd548c1a..458fbb5813 100644 --- a/P5/Source/Specs/teidata.duration.iso.xml +++ b/P5/Source/Specs/teidata.duration.iso.xml @@ -6,7 +6,7 @@ using ISO 8601 standard formats ISO 8601 표준 형식을 사용하여 시간의 지속을 나타내는 속성 값 범위를 정의한다. 以ISO 8601標準格式定義表示一段持續性時間的屬性值範圍 - ISO 8601にある標準形式を使い、時間幅を表現する当該属性値の範囲を定義 する。 + ISO 8601にある標準形式を使い、時間幅を表現する当該属性値の範囲を定義 する。 définit la gamme de valeurs d'attributs exprimant une durée temporaraire utilisant le norme ISO 8601. define la gama de valores de atributos posibles para representar la duración en el tiempo usando formatos estàndards ISO 8601. diff --git a/P5/Source/Specs/teidata.name.xml b/P5/Source/Specs/teidata.name.xml index 38f7544005..74cb8e9e34 100644 --- a/P5/Source/Specs/teidata.name.xml +++ b/P5/Source/Specs/teidata.name.xml @@ -5,7 +5,7 @@ defines the range of attribute values expressed as an XML Name. XML 이름으로 표현되는 속성 값 범위를 정의한다. 定義的屬性值範圍以XML名稱或識別符碼表示 - XML名前としてある属性値の範囲を定義する。 + XML名前としてある属性値の範囲を定義する。 définit la gamme des valeurs d'attribut exprimant un nom XML define la gama de valores de atributos expresados como diff --git a/P5/Source/Specs/teidata.namespace.xml b/P5/Source/Specs/teidata.namespace.xml index 14580b7d5c..0179d69262 100644 --- a/P5/Source/Specs/teidata.namespace.xml +++ b/P5/Source/Specs/teidata.namespace.xml @@ -17,8 +17,7 @@ W3C. define la gama de valores de atributos usados para indicar los nombres de los espacios en XML como establecen las recomendaciones técnicas del W3C - para los - + para los definisce la gamma di valori di attributi usati per indicare i nomi degli spazi in XML come stabilito dalle raccomandazioni tecniche del W3C per gli spazi dei nomi in XML. diff --git a/P5/Source/Specs/teidata.numeric.xml b/P5/Source/Specs/teidata.numeric.xml index 4649dd6f81..9544677a2d 100644 --- a/P5/Source/Specs/teidata.numeric.xml +++ b/P5/Source/Specs/teidata.numeric.xml @@ -5,7 +5,7 @@ defines the range of attribute values used for numeric values. 수치에 사용되는 속성 값의 범위를 정의한다. 定義用於數值的屬性值範圍 - 数値をとる属性値の範囲を定義する。 + 数値をとる属性値の範囲を定義する。 définit la gamme des valeurs d'attributs utilisées pour des valeurs numériques define la gama de valores de atributos para valores diff --git a/P5/Source/Specs/teidata.probability.xml b/P5/Source/Specs/teidata.probability.xml index 4b55a13514..84bf6cc5c8 100644 --- a/P5/Source/Specs/teidata.probability.xml +++ b/P5/Source/Specs/teidata.probability.xml @@ -5,7 +5,7 @@ defines the range of attribute values expressing a probability. 확률을 표현하는 속성 값의 범위를 정의한다. 定義表示可能性的屬性值範圍 - 出現度を示す属性値の範囲を定義する。 + 出現度を示す属性値の範囲を定義する。 définit la gamme des valeurs d'attributs exprimant une probabilité. define la gama de valores de atributos que exprimen un diff --git a/P5/Source/Specs/teidata.sex.xml b/P5/Source/Specs/teidata.sex.xml index b57a7f5892..36f01b8d6f 100644 --- a/P5/Source/Specs/teidata.sex.xml +++ b/P5/Source/Specs/teidata.sex.xml @@ -6,7 +6,7 @@ the sex of an organism. 인간 또는 동물의 성을 식별하는 속성 값 범위를 정의한다. 定義的屬性值範圍用以識別人類或動物的性別 - 人間または動物の性を示す属性値の範囲を定義する。 + 人間または動物の性を示す属性値の範囲を定義する。 définit la gamme des valeurs d'attributs employés pour identifier le sexe d’un organisme. define la gama de valores de atributos usados para diff --git a/P5/Source/Specs/teidata.temporal.iso.xml b/P5/Source/Specs/teidata.temporal.iso.xml index d395a42d73..24cd537dba 100644 --- a/P5/Source/Specs/teidata.temporal.iso.xml +++ b/P5/Source/Specs/teidata.temporal.iso.xml @@ -16,8 +16,7 @@ définit la gamme des valeurs d'attribut qui sont capables d''exprimer une valeur temporelle comme une date, une période, ou une combinaison des deux qui se conforment au standard international Data elements and interchange formats – - Information interchange – Representation of dates and times - + Information interchange – Representation of dates and times define la gama de valores de atributos que expresan una expresión temporal como una fecha, una hora, o una combinación de estas, de acuerdo a un estándard internacional Elementos de datos y formatos de intercambio - Intercambio de diff --git a/P5/Source/Specs/teidata.xTruthValue.xml b/P5/Source/Specs/teidata.xTruthValue.xml index 7e5a6939a5..69bdc6363b 100644 --- a/P5/Source/Specs/teidata.xTruthValue.xml +++ b/P5/Source/Specs/teidata.xTruthValue.xml @@ -8,7 +8,7 @@ <desc versionDate="2007-10-18" xml:lang="en">defines the range of attribute values used to express a truth value which may be unknown.</desc> <desc versionDate="2007-12-20" xml:lang="ko">알려지지 않을 수 있는 진리값을 표현하는 속성 값 범위를 정의한다.</desc> <desc versionDate="2007-05-02" xml:lang="zh-TW">定義的屬性值範圍表示一個可能未知的真實值</desc> - <desc versionDate="2008-04-05" xml:lang="ja">不明の場合もある真偽値をとる属性値の範囲を定義する。 </desc> + <desc versionDate="2008-04-05" xml:lang="ja">不明の場合もある真偽値をとる属性値の範囲を定義する。</desc> <desc versionDate="2007-06-12" xml:lang="fr">définit la gamme des valeurs d'attributs exprimant une vérité potentiellement inconnue.</desc> <desc versionDate="2007-05-04" xml:lang="es">define la gama de valores de atributos usados para diff --git a/P5/Source/Specs/textClass.xml b/P5/Source/Specs/textClass.xml index dd488c822e..f5d8dabe6e 100644 --- a/P5/Source/Specs/textClass.xml +++ b/P5/Source/Specs/textClass.xml @@ -18,8 +18,7 @@ <desc versionDate="2007-05-02" xml:lang="zh-TW">匯集以標準分類架構、索引典等來描述文件性質或主題的資訊。</desc> <desc versionDate="2008-04-05" xml:lang="ja">標準的な分類スキーム、分類語彙などにより、テキストの性格や話題を示す 情報をまとめる。</desc> <desc versionDate="2016-11-24" xml:lang="de">gruppiert Informationen über Art oder Thematik eines Textes unter - Bezug auf ein Standard-Klassifikationsschema, einen Thesaurus o. ä. - </desc> + Bezug auf ein Standard-Klassifikationsschema, einen Thesaurus o. ä.</desc> <desc versionDate="2007-05-04" xml:lang="es">agrupa información que describe la naturaleza o la temática de un texto en términos de un esquema de clasificación estándard.</desc> <desc versionDate="2007-01-21" xml:lang="it">raggruppa le informazioni che descrivono la natura o diff --git a/P5/Source/Specs/textLang.xml b/P5/Source/Specs/textLang.xml index 479142edea..2217dbab82 100644 --- a/P5/Source/Specs/textLang.xml +++ b/P5/Source/Specs/textLang.xml @@ -21,8 +21,7 @@ en un manuscrito (no se ha de confundir con la descripción contenida en el elemento <gi>langUsage</gi>. ****</desc> <desc versionDate="2007-01-21" xml:lang="it">descrive le lingue e i sistemi di scrittura usati da un - manoscritto (da non confondere con la descrizione contenuta nell'elemento <gi>langUsage</gi> - </desc> + manoscritto (da non confondere con la descrizione contenuta nell'elemento <gi>langUsage</gi></desc> <classes> <memberOf key="att.global"/> <memberOf key="model.msItemPart"/> diff --git a/P5/Source/Specs/unclear.xml b/P5/Source/Specs/unclear.xml index c293cbab16..5413579bc2 100644 --- a/P5/Source/Specs/unclear.xml +++ b/P5/Source/Specs/unclear.xml @@ -13,13 +13,11 @@ <desc versionDate="2008-04-05" xml:lang="ja">元資料からは判読できないまたは聞こえないという理由で、確実に転記でき ない語句や一節を示す。</desc> <desc versionDate="2009-01-06" xml:lang="fr">contient un mot, une expression ou bien un passage qui ne peut être transcrit avec certitude parce qu'il est illisible ou inaudible dans la source.</desc> - <desc versionDate="2022-02-20" xml:lang="es">contiene una palabra, frase o pasaje que no puede ser transcrito con certeza porque en la fuente es ilegible o inaudible. </desc> + <desc versionDate="2022-02-20" xml:lang="es">contiene una palabra, frase o pasaje que no puede ser transcrito con certeza porque en la fuente es ilegible o inaudible.</desc> <desc versionDate="2007-01-21" xml:lang="it">contiene una parola, una frase o un brano che non può essere trascritto con certezza perché è parzialmente illeggibile o incomprensibile nell'originale.</desc> - <desc versionDate="2016-11-24" xml:lang="de"> - enthält ein Wort, einen Satz oder eine Textpassage, welche in der Quelle nicht oder nur schwer lesbar bzw. hörbar ist. - </desc> + <desc versionDate="2016-11-24" xml:lang="de">enthält ein Wort, einen Satz oder eine Textpassage, welche in der Quelle nicht oder nur schwer lesbar bzw. hörbar ist.</desc> <classes> <memberOf key="att.global"/> <memberOf key="model.pPart.transcriptional"/> @@ -120,7 +118,7 @@ usually each word will refer to a single cause.</p> <desc versionDate="2007-06-27" xml:lang="en">damage results from rubbing of the leaf edges</desc> <desc versionDate="2007-12-20" xml:lang="ko">책장 모서리의 마모로 인한 훼손</desc> <desc versionDate="2007-05-02" xml:lang="zh-TW">損毀起因於書頁邊緣摩擦受損</desc> - <desc versionDate="2022-02-20" xml:lang="es">Daños resultantes del frotamiento de los bordes de la hoja. </desc> + <desc versionDate="2022-02-20" xml:lang="es">Daños resultantes del frotamiento de los bordes de la hoja.</desc> <desc versionDate="2008-04-05" xml:lang="ja">葉の端がこすれたことによる損傷。</desc> <desc versionDate="2008-03-30" xml:lang="fr">des dommages résultent du frottement des bords de la feuille</desc> diff --git a/P5/Source/Specs/unit.xml b/P5/Source/Specs/unit.xml index b40a0d972a..3cfea5f40e 100644 --- a/P5/Source/Specs/unit.xml +++ b/P5/Source/Specs/unit.xml @@ -4,9 +4,7 @@ <elementSpec xmlns="http://www.tei-c.org/ns/1.0" module="core" ident="unit"> <desc versionDate="2018-07-17" xml:lang="en">contains a symbol, a word or a phrase referring to a unit of measurement in any kind of formal or informal system.</desc> <desc versionDate="2018-07-17" xml:lang="de">enthält ein Symbol, ein Wort oder eine Phrase, die sich auf eine Maßeinheit in einem formellen oder informellen System bezieht.</desc> - <desc versionDate="2023-07-29" xml:lang="ja"> - 公式・非公式に関わらず、単位を表す記号や単語、語句を含む。 - </desc> + <desc versionDate="2023-07-29" xml:lang="ja">公式・非公式に関わらず、単位を表す記号や単語、語句を含む。</desc> <classes> <memberOf key="att.global"/> <memberOf key="att.typed"/> diff --git a/P5/Source/Specs/vColl.xml b/P5/Source/Specs/vColl.xml index 15aa41de5b..41d5e87dbb 100644 --- a/P5/Source/Specs/vColl.xml +++ b/P5/Source/Specs/vColl.xml @@ -71,8 +71,7 @@ bag (multiset).</desc> <desc versionDate="2008-04-06" xml:lang="es">indica que los valores dados están ordenados como una bolsa (conjunto múltiple).</desc> <desc versionDate="2008-04-05" xml:lang="ja">バック(順序なし、重複あり)としてある値を示す。</desc> <desc versionDate="2008-03-30" xml:lang="fr">indique que les valeurs données sont -organisées en paquet (de plusieurs ensembles). -</desc> +organisées en paquet (de plusieurs ensembles).</desc> <desc versionDate="2007-01-21" xml:lang="it">indica che i valori dati sono organizzati in una borsa (insieme multiplo).</desc> </valItem> <valItem ident="list"> diff --git a/P5/Source/Specs/vMerge.xml b/P5/Source/Specs/vMerge.xml index e262c194d8..fafba4f131 100644 --- a/P5/Source/Specs/vMerge.xml +++ b/P5/Source/Specs/vMerge.xml @@ -63,8 +63,7 @@ sont organisées en ensemble.</desc> <desc versionDate="2008-04-05" xml:lang="ja">結果として得られた値の構造が、バック(順序なし、重複あり)であ ることを示す。</desc> <desc versionDate="2008-03-30" xml:lang="fr">indique que les valeurs résultantes -sont organisées en paquet (de plusieurs ensembles). -</desc> +sont organisées en paquet (de plusieurs ensembles).</desc> <desc versionDate="2007-01-21" xml:lang="it">indica che i valori risultanti dall'unificazione sono organizzati in una borsa (insieme multiplo).</desc> </valItem> <valItem ident="list"> diff --git a/P5/Source/Specs/valDesc.xml b/P5/Source/Specs/valDesc.xml index a490d925fc..20a81231bc 100644 --- a/P5/Source/Specs/valDesc.xml +++ b/P5/Source/Specs/valDesc.xml @@ -17,8 +17,7 @@ an attribute may take, additional to the information carried by the を示す。</desc> <desc versionDate="2007-06-12" xml:lang="fr">précise toute contrainte sémantique ou syntaxique sur la valeur que peut prendre un attribut, en supplément de l'information portée par - l'élément <gi>datatype</gi>. - </desc> + l'élément <gi>datatype</gi>.</desc> <desc versionDate="2007-05-04" xml:lang="es">especifica cualquier vínculo de tipo semántico o sintáctico respecto al valor que un atributo puede asumir, añadiendo informaciones referentes al elemento datatype.</desc> <desc versionDate="2007-01-21" xml:lang="it">specifica un qualsiasi vincolo di tipo semantico o sintattico rispetto al valore che un diff --git a/P5/Source/Specs/when.xml b/P5/Source/Specs/when.xml index f109777b30..b69d351628 100644 --- a/P5/Source/Specs/when.xml +++ b/P5/Source/Specs/when.xml @@ -40,8 +40,7 @@ <desc versionDate="2008-04-05" xml:lang="ja">親要素<gi>timeLine</gi>から継承されない場合、属性 <att>interval</att>で示される時間の単位を示す。</desc> <desc versionDate="2007-06-12" xml:lang="fr">spécifie l'unité de temps dans laquelle la valeur de l'attribut <att>interval</att> est exprimée, si elle n'est pas héritée de l'élément parent <gi>timeLine</gi>.</desc> <desc versionDate="2007-05-04" xml:lang="es">especifica la unidad temporal en la que se expresa el valor <att>interval</att>, si este valor no es heredado del padre <gi>timeline</gi>.</desc> - <desc versionDate="2007-01-21" xml:lang="it">specifica l'unità temporale nel quale è espresso l'attributo <att>interval</att>, se questo non è ereditato dal genitore <gi>timeline</gi> - </desc> + <desc versionDate="2007-01-21" xml:lang="it">specifica l'unità temporale nel quale è espresso l'attributo <att>interval</att>, se questo non è ereditato dal genitore <gi>timeline</gi></desc> <datatype><dataRef key="teidata.enumerated"/></datatype> <valList type="semi"> <valItem ident="d"> diff --git a/P5/Source/Specs/zone.xml b/P5/Source/Specs/zone.xml index cfa9bff22c..896b153c6e 100644 --- a/P5/Source/Specs/zone.xml +++ b/P5/Source/Specs/zone.xml @@ -40,8 +40,7 @@ element.</desc> <desc versionDate="2018-04-15" xml:lang="de">gibt das Ausmaß der Drehung (im Uhrzeigersinn) dieser <gi>zone</gi> an. Als Bezugspunkt gilt dabei die natürliche Ausrichtung des <gi>surface</gi>-Elternelements, die entweder im <gi>msDesc</gi>-Element beschrieben ist oder durch die Koordinaten des <gi>surface</gi>-Elements selbst. - Die Drehung wird in Bogengrad angegeben. - </desc> + Die Drehung wird in Bogengrad angegeben.</desc> <datatype minOccurs="1" maxOccurs="1"><dataRef key="teidata.count"/></datatype> <defaultVal>0</defaultVal> </attDef> From 5748b8e24f3569df5b272314f31afd6f3eda0836 Mon Sep 17 00:00:00 2001 From: ebeshero <ebbondar@gmail.com> Date: Sat, 6 Jul 2024 06:37:48 -0400 Subject: [PATCH 106/127] release notes compiled for 4.8.0 --- P5/ReleaseNotes/readme-4.8.0.xml | 198 +++++++++++++++++++++++++++++++ 1 file changed, 198 insertions(+) create mode 100644 P5/ReleaseNotes/readme-4.8.0.xml diff --git a/P5/ReleaseNotes/readme-4.8.0.xml b/P5/ReleaseNotes/readme-4.8.0.xml new file mode 100644 index 0000000000..2637a8bcf7 --- /dev/null +++ b/P5/ReleaseNotes/readme-4.8.0.xml @@ -0,0 +1,198 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!-- +Copyright TEI Consortium. +Dual-licensed under CC-by and BSD2 licences +See the file COPYING.txt for details +--> +<?xml-model href="http://www.tei-c.org/release/xml/tei/custom/schema/relaxng/tei_all.rng" type="application/xml" schematypens="http://relaxng.org/ns/structure/1.0"?> +<?xml-model href="http://www.tei-c.org/release/xml/tei/custom/schema/relaxng/tei_all.rng" type="application/xml" schematypens="http://purl.oclc.org/dsdl/schematron"?> +<TEI xmlns="http://www.tei-c.org/ns/1.0"> + <teiHeader> + <fileDesc> + <titleStmt> + <title>TEI P5 version 4.8.0 and Stylesheets version 7.57.0 release notes + + + + Monday, 8 July 2024 + + + + The Text Encoding Initiative + + +

Created retrospectively from ChangeLog and GitHub trackers

+ + + + + +

Release 4.8.0 is codenamed The Six Degrees Release.

+

This release introduces new features and resolves a number of issues raised by the TEI + community. The majority of these changes and corrections are a consequence of feature + requests or bugs reported by the TEI community using the GitHub tracking system. A full list + of the issues resolved in the course of this release cycle may be found under the 4.8.0 milestone.

+

+

The following changes are particularly worth highlighting in this release: + New encoding features + A new + chapter on computer-mediated communication (CMC) provides guidelines for + structuring texts and corpora in TEI that encode the data and metadata of interactive + posts in multiple media (#1955 and PR #2537). + The chapter introduces a new post element to encode a contribution to a CMC + interaction, and with it: + two new attribute classes att.cmc and att.indentation, of which it is a member. + The following new attributes are distinct to post: + modality to document whether a post is written or spoken, + replyTo to indicate a previous post to which a post replies or + references, + generatedBy (a member of att.cmc) with + suggested values human, template, system, bot, and + unspecified to indicate how content in a post is generated. + + The post element is also a member of att.global, att.ascribed, att.datable, att.timed, att.fragmentable, att.docStatus, att.typed, and att.canonical giving + it access to many attributes to identify agents responsible for posts, indicate + their timing, and categorize them. + A new attribute related but not restricted to CMC, indentLevel, is + provided in the class att.indentation to describe + indentation of text content in a source, as for example, to mark a post’s level of + indentation discussion thread. + + + + + + + Changes to content models + With this release, quote is now a member of model.biblPart, permitting it to be used within bibl (#2544 and PR #2557). + The Guidelines now deprecate the use of superEntry and re elements + as superfluous since the entry element may now self-nest (#2488, #2487, PR #2532, and #2521. + Following a deprecation period, the content element now requires just one + and no more than one element child (#2381 and PR #2409) + The event element is now more efficiently modeled using model.eventLike with no changes to its content. (#2524 and PR #2525). + To improve gaiji descriptions, the scheme attribute was added to att.gaijiProp, and mapping, localProp + unicodeProp, and unihanProp were added to att.datable. (#2132 and PR + #2511. + The datatype teidata.probability was previously defined + too broadly as xsd:double, and has now been constrained to a value between + 0 and 1 (#2518 and PR #2519. + Schematron constraints in ODDs must now include a <sch:rule> + element with a @context attribute to improve ODD processing, and the + Guidelines have been updated to reflect this change (#2510 and PR #2513. + + +

+

The following changes introduced with this release could invalidate ODD customizations in + TEI projects. Those maintaining ODD customizations of the TEI may want to be aware of the + following changes and adapt your ODD files accordingly. + ODD-breaking changes and deprecation + + + +

+

+ + Improvements of prose and examples + The definition of surface has been updated to reflect the context of + embedded transcription (#2476). + The description of teiCorpus has been updated in the language corpora + chapter (#2445 and PR #2503). + Examples of geo elements no longer include a comma to separate + geocoordinates to better align with the prose of the Guidelines (#2560). + Schematron constraints were simplified to remove redundancies in the simplePrint ODD + (PR #2540). + + + + + + + Housekeeping + The HTML Guidelines pages have been updated to output the current standard HTML 5 + doctype (#2508). + For Guidelines processing, we have removed unnecessary @mode="add" + attributes from the element specifications, since all content is simply added to the + Guidelines with no other mode possible (#2498 and #2520). + The copyright notice in XML comments at the top of the Guidelines XML files has been + simplified (#2514 and PR #2526). + Superfluous namespace declarations have been removed from Guidelines datatype + specification files (PR + #2522). + +

+ +

In addition, many improvements have been made to the XSLT stylesheets (which provide + processing of TEI ODD files for Roma and + TEIGarage as well as other TEI + conversions). The Stylesheets are maintained separately from the Guidelines at https://github.com/TEIC/Stylesheets. A + full list of the issues resolved in the course of this release cycle may be found under the + 7.57.0 + milestone.

+ +

Highlights of this release include: + Updating the Stylesheets from XSLT 2.0 to XSLT 3.0 (Stylesheets #639, PR #649, and PR #663). + Correcting a bug that permitted any attributes to be copied from the + constraint element to a generated sch:rule/@context (Stylesheets + #659 and PR #660) + Solving a serious problem mentioned in several tickets (Stylesheets #645, #678, #680) in which + multiple elementSpec sharing the same ident lead to a build error in odd2odd.xsl, solved with Stylesheets PR #681. + Identifying and solving a problem in ODD processing when an ODD attempts to replace, + change, or delete an attribute in the wrong class (e.g. in an outdated class after it + has been relocated to a different class), the processed ODD produces duplicate + attDef elements (Stylesheets #687). + +

+ + + From 98f72abbf5385ed99901a2a81fad7c9c3edb2c46 Mon Sep 17 00:00:00 2001 From: ebeshero Date: Sat, 6 Jul 2024 06:43:20 -0400 Subject: [PATCH 107/127] commenting out unused section in release notes --- P5/ReleaseNotes/readme-4.8.0.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/P5/ReleaseNotes/readme-4.8.0.xml b/P5/ReleaseNotes/readme-4.8.0.xml index 2637a8bcf7..a5d44adaf2 100644 --- a/P5/ReleaseNotes/readme-4.8.0.xml +++ b/P5/ReleaseNotes/readme-4.8.0.xml @@ -111,14 +111,14 @@ See the file COPYING.txt for details -->

-

The following changes introduced with this release could invalidate ODD customizations in +

Improvements of prose and examples From 049f7d7195d3b72d72173a0f04fff0e40afea1a4 Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Sat, 6 Jul 2024 17:58:37 -0400 Subject: [PATCH 108/127] =?UTF-8?q?Tweaks=20to=20readme=20for=20upcoming?= =?UTF-8?q?=206=C2=B0=20release?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- P5/ReleaseNotes/readme-4.8.0.xml | 20 ++++++++++++-------- 1 file changed, 12 insertions(+), 8 deletions(-) diff --git a/P5/ReleaseNotes/readme-4.8.0.xml b/P5/ReleaseNotes/readme-4.8.0.xml index a5d44adaf2..e346cc7fb7 100644 --- a/P5/ReleaseNotes/readme-4.8.0.xml +++ b/P5/ReleaseNotes/readme-4.8.0.xml @@ -27,7 +27,9 @@ See the file COPYING.txt for details -

Release 4.8.0 is codenamed The Six Degrees Release.

+

Release 4.8.0 is codenamed The Six Degrees + Release.

This release introduces new features and resolves a number of issues raised by the TEI community. The majority of these changes and corrections are a consequence of feature requests or bugs reported by the TEI community using the GitHub tracking system. A full list @@ -44,7 +46,7 @@ See the file COPYING.txt for details The chapter introduces a new post element to encode a contribution to a CMC interaction, and with it: two new attribute classes att.cmc and att.indentation, of which it is a member. + type="class">att.indentation, each of which it is a member. The following new attributes are distinct to post: modality to document whether a post is written or spoken, replyTo to indicate a previous post to which a post replies or @@ -80,11 +82,13 @@ See the file COPYING.txt for details target="#https://github.com/TEIC/TEI/issues/2488">#2488, #2487, PR #2532, and #2521. + target="https://github.com/TEIC/TEI/pull/2521">#2521). Following a deprecation period, the content element now requires just one - and no more than one element child ( + (#2381 and PR #2409) + target="https://github.com/TEIC/TEI/pull/2409">PR #2409). The event element is now more efficiently modeled using model.eventLike with no changes to its content. (#2524 and unicodeProp, and unihanProp were added to att.datable. (#2132 and PR - #2511. + #2511). The datatype teidata.probability was previously defined too broadly as xsd:double, and has now been constrained to a value between 0 and 1 (#2518 and PR #2519. + target="https://github.com/TEIC/TEI/pull/2519">PR #2519). Schematron constraints in ODDs must now include a <sch:rule> element with a @context attribute to improve ODD processing, and the Guidelines have been updated to reflect this change (#2510 and PR #2513. + target="https://github.com/TEIC/TEI/pull/2513">PR #2513).

From f42eb3eeb85ae6aa3157b757c8f3e6b6da3ff55f Mon Sep 17 00:00:00 2001 From: ebeshero Date: Sun, 7 Jul 2024 14:00:58 -0400 Subject: [PATCH 110/127] updating release notes with Stylesheets 687 --- P5/ReleaseNotes/readme-4.8.0.xml | 48 +++++++++++++++++--------------- 1 file changed, 25 insertions(+), 23 deletions(-) diff --git a/P5/ReleaseNotes/readme-4.8.0.xml b/P5/ReleaseNotes/readme-4.8.0.xml index 3a8905ef92..cff72ef55b 100644 --- a/P5/ReleaseNotes/readme-4.8.0.xml +++ b/P5/ReleaseNotes/readme-4.8.0.xml @@ -28,13 +28,15 @@ See the file COPYING.txt for details

Release 4.8.0 is codenamed The Six Degrees - Release.

+ Release.

This release introduces new features and resolves a number of issues raised by the TEI community. The majority of these changes and corrections are a consequence of feature requests or bugs reported by the TEI community using the GitHub tracking system. A full list of the issues resolved in the course of this release cycle may be found under the 4.8.0 milestone.

+ target="https://github.com/TEIC/TEI/milestone/16?closed=1">4.8.0 milestone. + Very special thanks to Michael Beißwenger and Harald Lüngen for their essential contributions + to the new CMC chapter.

The following changes are particularly worth highlighting in this release: New encoding features @@ -68,8 +70,6 @@ See the file COPYING.txt for details indentation discussion thread. - - Changes to content models @@ -83,12 +83,7 @@ See the file COPYING.txt for details target="https://github.com/TEIC/TEI/issues/2487">#2487, PR #2532, and #2521). - Following a deprecation period, the content element now requires just one - and no more than one child element - - (#2381 and PR #2409). + The event element is now more efficiently modeled using model.eventLike with no changes to its content. (#2524 and -->

- +

Improvements of prose and examples @@ -179,23 +179,25 @@ See the file COPYING.txt for details target="https://github.com/TEIC/Stylesheets/issues/639">#639, PR #649, and PR #663). + Correcting a bug that permitted any attributes to be copied from the + constraint element to a generated sch:rule/@context (Stylesheets + #659 and PR #660) Solving a serious problem mentioned in several tickets (Stylesheets #645, #678, #680) in which - multiple elementSpec sharing the same ident lead to a build error in odd2odd.xsl, solved with Stylesheets PR #681. + target="https://github.com/TEIC/Stylesheets/issues/680">#680) in which multiple + elementSpec sharing the same ident lead to a build error in + odd2odd.xsl, solved with Stylesheets PR #681. Identifying and solving a problem in ODD processing when an ODD attempts to replace, change, or delete an attribute in the wrong class (e.g. in an outdated class after it has been relocated to a different class), the processed ODD produces duplicate attDef elements (Stylesheets #687). - + +

From 3fcefa7b328fbc92320d28ae6f6ebe649b800e14 Mon Sep 17 00:00:00 2001 From: ebeshero Date: Sun, 7 Jul 2024 14:35:11 -0400 Subject: [PATCH 111/127] adding contributor list with gratitude --- P5/ReleaseNotes/readme-4.8.0.xml | 30 +++++++++++++++++------------- 1 file changed, 17 insertions(+), 13 deletions(-) diff --git a/P5/ReleaseNotes/readme-4.8.0.xml b/P5/ReleaseNotes/readme-4.8.0.xml index cff72ef55b..c4904cfa2c 100644 --- a/P5/ReleaseNotes/readme-4.8.0.xml +++ b/P5/ReleaseNotes/readme-4.8.0.xml @@ -34,9 +34,12 @@ See the file COPYING.txt for details community. The majority of these changes and corrections are a consequence of feature requests or bugs reported by the TEI community using the GitHub tracking system. A full list of the issues resolved in the course of this release cycle may be found under the 4.8.0 milestone. - Very special thanks to Michael Beißwenger and Harald Lüngen for their essential contributions - to the new CMC chapter.

+ target="https://github.com/TEIC/TEI/milestone/16?closed=1">4.8.0 milestone. Very + special thanks to Michael Beißwenger and Harald Lüngen for their essential contributions to + the new computer-mediated communication chapter. Thanks also to several community contributors to + TEI and Stylesheets issues that led to this release including: Benjamin W. Bohl, Lou Burnard, + Martin Holmes, Dominique Meeùs, Bastian Politycki, Daniel Schwarz, Peter Stadler, Nicolas Vaughan, +

The following changes are particularly worth highlighting in this release: New encoding features @@ -179,25 +182,26 @@ See the file COPYING.txt for details target="https://github.com/TEIC/Stylesheets/issues/639">#639, PR #649, and PR #663). - Correcting a bug that permitted any attributes to be copied from the - constraint element to a generated sch:rule/@context (Stylesheets - #659 and PR #660) + Correcting a bug that permitted any attributes to be copied from the + constraint element to a generated sch:rule/@context (Stylesheets + #659 and PR #660) Solving a serious problem mentioned in several tickets (Stylesheets #645, #678, #680) in which multiple - elementSpec sharing the same ident lead to a build error in + elementSpec sharing the same ident led to a build error in odd2odd.xsl, solved with Stylesheets PR #681. Identifying and solving a problem in ODD processing when an ODD attempts to replace, change, or delete an attribute in the wrong class (e.g. in an outdated class after it has been relocated to a different class), the processed ODD produces duplicate - attDef elements (Stylesheets #687). - - + attDef elements (Stylesheets #687 and PR #690). + +

From dddf5ade8c4e3b65441d95efa344f75e8c2e177e Mon Sep 17 00:00:00 2001 From: ebeshero Date: Sun, 7 Jul 2024 15:42:40 -0400 Subject: [PATCH 112/127] more Stylesheets commentary in Release Notes --- P5/ReleaseNotes/readme-4.8.0.xml | 71 +++++++++++++++++++++----------- 1 file changed, 48 insertions(+), 23 deletions(-) diff --git a/P5/ReleaseNotes/readme-4.8.0.xml b/P5/ReleaseNotes/readme-4.8.0.xml index c4904cfa2c..3702257a3f 100644 --- a/P5/ReleaseNotes/readme-4.8.0.xml +++ b/P5/ReleaseNotes/readme-4.8.0.xml @@ -36,10 +36,11 @@ See the file COPYING.txt for details of the issues resolved in the course of this release cycle may be found under the 4.8.0 milestone. Very special thanks to Michael Beißwenger and Harald Lüngen for their essential contributions to - the new computer-mediated communication chapter. Thanks also to several community contributors to - TEI and Stylesheets issues that led to this release including: Benjamin W. Bohl, Lou Burnard, - Martin Holmes, Dominique Meeùs, Bastian Politycki, Daniel Schwarz, Peter Stadler, Nicolas Vaughan, -

+ the new computer-mediated communication chapter. Many thanks also to many community + contributors to TEI and Stylesheets issues that led to this release, including: John + Bampton, Benjamin W. Bohl, Lou Burnard, Martin Holmes, Martin de la Iglesia, Dominique + Meeùs, Kiyonori Nagasaki, Bastian Politycki, Klaus Rettinghaus, Daniel Schwarz, Peter + Stadler, Christian Thomas, Conal Tuohy, and Nicolas Vaughan.

The following changes are particularly worth highlighting in this release: New encoding features @@ -181,26 +182,50 @@ See the file COPYING.txt for details Updating the Stylesheets from XSLT 2.0 to XSLT 3.0 (Stylesheets #639, PR #649, and PR #663). - Correcting a bug that permitted any attributes to be copied from the - constraint element to a generated sch:rule/@context (Stylesheets - #659 and PR #660) - Solving a serious problem mentioned in several tickets (Stylesheets #645, #678, #680) in which multiple - elementSpec sharing the same ident led to a build error in - odd2odd.xsl, solved with Stylesheets PR #681. - Identifying and solving a problem in ODD processing when an ODD attempts to replace, - change, or delete an attribute in the wrong class (e.g. in an outdated class after it - has been relocated to a different class), the processed ODD produces duplicate - attDef elements (Stylesheets #687 and PR #690). + target="https://github.com/TEIC/Stylesheets/pull/663">PR #663); + Identifying and solving a problem with in our testing of DOCX to TEI conversion + when the Stylesheets version changes (Stylesheets + #646 and + PR #650); + Correcting a bug in the common function.xsl that allowed a sup value of + rend to be treated the same as a sub value (Stylesheets #584 and PR #670; + Updating the processing of non-TEI ODDs by looking for them in ident rather + than altIdent elements (Stylesheets #598 and PR #651); + Identifying and solving several problems in ODD processing: + Ensuring that att.repeatable is properly processed on sequence, + alternate, and anyElement (Stylesheets #627 and PR #633); + Correcting a bug that permitted any attributes to be copied from the + constraint element to a generated sch:rule/@context + (Stylesheets #659 + and PR #660); + Repairing another bug that caused an output constraintSpec to appear in + the wrong location in a constructed ODD (Stylesheets PR + #675); + Solving a serious problem mentioned in several tickets (Stylesheets #645, #678, #680) in which + multiple elementSpec sharing the same ident led to a build error + in odd2odd.xsl, solved with Stylesheets PR + #681; + Solving a problem when replacing, changing, or deleting an attribute marked with + the wrong class (e.g. in an outdated class after it has been relocated to a + different class), the processed ODD produces duplicate attDef elements + (Stylesheets #687 + and PR #690). +

From 9e046a7386ecd47175b5d5a59298197c33c041ca Mon Sep 17 00:00:00 2001 From: ebeshero Date: Sun, 7 Jul 2024 15:59:46 -0400 Subject: [PATCH 113/127] completely documented release notes --- P5/ReleaseNotes/readme-4.8.0.xml | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/P5/ReleaseNotes/readme-4.8.0.xml b/P5/ReleaseNotes/readme-4.8.0.xml index 3702257a3f..1d454bc109 100644 --- a/P5/ReleaseNotes/readme-4.8.0.xml +++ b/P5/ReleaseNotes/readme-4.8.0.xml @@ -191,12 +191,16 @@ See the file COPYING.txt for details rend to be treated the same as a sub value (Stylesheets #584 and PR #670; - Updating the processing of non-TEI ODDs by looking for them in ident rather - than altIdent elements (Stylesheets #598 and PR #651); + Identifying and solving several problems in ODD processing: + Repairs to our transform scripts (Stylesheets + #652 and + PR #653); + Updating the processing of non-TEI ODDs by looking for them in ident rather + than altIdent elements (Stylesheets #598 and PR #651); Ensuring that att.repeatable is properly processed on sequence, alternate, and anyElement (Stylesheets #627 and Date: Sun, 7 Jul 2024 16:05:15 -0400 Subject: [PATCH 114/127] cutting issue that was not resolved --- P5/ReleaseNotes/readme-4.8.0.xml | 1 - 1 file changed, 1 deletion(-) diff --git a/P5/ReleaseNotes/readme-4.8.0.xml b/P5/ReleaseNotes/readme-4.8.0.xml index 1d454bc109..10e5689dd4 100644 --- a/P5/ReleaseNotes/readme-4.8.0.xml +++ b/P5/ReleaseNotes/readme-4.8.0.xml @@ -199,7 +199,6 @@ See the file COPYING.txt for details PR #653); Updating the processing of non-TEI ODDs by looking for them in ident rather than altIdent elements (Stylesheets #598 and PR #651); Ensuring that att.repeatable is properly processed on sequence, alternate, and anyElement (Stylesheets Date: Sun, 7 Jul 2024 16:24:44 -0400 Subject: [PATCH 115/127] fixing bugs in Release Notes --- P5/ReleaseNotes/readme-4.8.0.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/P5/ReleaseNotes/readme-4.8.0.xml b/P5/ReleaseNotes/readme-4.8.0.xml index 10e5689dd4..8d06f53a85 100644 --- a/P5/ReleaseNotes/readme-4.8.0.xml +++ b/P5/ReleaseNotes/readme-4.8.0.xml @@ -71,7 +71,7 @@ See the file COPYING.txt for details A new attribute related but not restricted to CMC, indentLevel, is provided in the class att.indentation to describe indentation of text content in a source, as for example, to mark a post’s level of - indentation discussion thread. + indentation in a discussion thread. @@ -83,7 +83,7 @@ See the file COPYING.txt for details target="https://github.com/TEIC/TEI/pull/2557">PR #2557). The Guidelines now deprecate the use of superEntry and re elements as superfluous since the entry element may now self-nest (#2488, #2488, #2487, PR #2532, and #2521). From 8302252512fefbe834889d632d64a341f38952bf Mon Sep 17 00:00:00 2001 From: ebeshero Date: Sun, 7 Jul 2024 16:27:31 -0400 Subject: [PATCH 116/127] tiny bug fix --- P5/ReleaseNotes/readme-4.8.0.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/P5/ReleaseNotes/readme-4.8.0.xml b/P5/ReleaseNotes/readme-4.8.0.xml index 8d06f53a85..80d637781a 100644 --- a/P5/ReleaseNotes/readme-4.8.0.xml +++ b/P5/ReleaseNotes/readme-4.8.0.xml @@ -96,7 +96,7 @@ See the file COPYING.txt for details type="class">att.gaijiProp, and mapping, localProp unicodeProp, and unihanProp were added to att.datable. (#2132 and PR + >#2132 and PR #2511). The datatype teidata.probability was previously defined too broadly as xsd:double, and has now been constrained to a value between From dd30760f003995a3d16f449f9f9914faa3b249dd Mon Sep 17 00:00:00 2001 From: ebeshero Date: Sun, 7 Jul 2024 16:35:56 -0400 Subject: [PATCH 117/127] moving an item in Release Notes --- P5/ReleaseNotes/readme-4.8.0.xml | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/P5/ReleaseNotes/readme-4.8.0.xml b/P5/ReleaseNotes/readme-4.8.0.xml index 80d637781a..0b3f1d5b57 100644 --- a/P5/ReleaseNotes/readme-4.8.0.xml +++ b/P5/ReleaseNotes/readme-4.8.0.xml @@ -102,11 +102,6 @@ See the file COPYING.txt for details too broadly as xsd:double, and has now been constrained to a value between 0 and 1 (#2518 and PR #2519). - Schematron constraints in ODDs must now include a <sch:rule> - element with a @context attribute to improve ODD processing, and the - Guidelines have been updated to reflect this change (#2510 and PR #2513). + @@ -44,7 +40,7 @@ See the file COPYING.txt for details

The following changes are particularly worth highlighting in this release: New encoding features - A new + A new chapter on computer-mediated communication (CMC) provides guidelines for structuring texts and corpora in TEI that encode the data and metadata of interactive posts in multiple media (The following new attributes are distinct to post: modality to document whether a post is written or spoken, replyTo to indicate a previous post to which a post replies or - references, + refers, generatedBy (a member of att.cmc) with - suggested values human, template, system, bot, and - unspecified to indicate how content in a post is generated. + suggested values human, template, system, bot, and + unspecified to indicate how content in a post is generated. The post element is also a member of att.global, att.ascribed, PR #2557). The Guidelines now deprecate the use of superEntry and re elements as superfluous since the entry element may now self-nest (#2488, #2488, #2487, PR #2532, and #2521). - The event element is now more efficiently modeled using model.eventLike with no changes to its content. (#2524 and xsd:double, and has now been constrained to a value between 0 and 1 (#2518 and PR #2519). - Schematron constraints in ODDs must now include a <sch:rule> - element with a @context attribute to improve ODD processing, and the - Guidelines have been updated to reflect this change (In order to avoid ambiguity, Schematron constraints in ODDs must now include an + sch:rule> element with a context attribute, and + the Guidelines have been updated to reflect this change (#2510 and PR #2513). @@ -115,16 +110,15 @@ See the file COPYING.txt for details -->

The following changes introduced with this release could invalidate ODD customizations in - TEI projects. Those maintaining ODD customizations of the TEI may want to be aware of the - following changes and adapt your ODD files accordingly. + TEI projects. Those maintaining ODD customizations of the TEI should be aware of the + following changes, and may need to adapt their ODD files accordingly. ODD-breaking changes and deprecation Following a deprecation period that has now ended, the content element, which declares the content model of an element being specified in an ODD, now requires exactly one and only one child element. If several RELAX NG elements are desired, they - must now be wrapped in a rng:div (rng:div (#2381 and PR #2409). -

@@ -141,9 +135,6 @@ See the file COPYING.txt for details target="https://github.com/TEIC/TEI/issues/2560">#2560). Schematron constraints were simplified to remove redundancies in the simplePrint ODD (PR #2540). - - -