TEI: TEI指引

TEI: Basic Principles⚓︎14.3.1 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.⁵³ 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:

• state (state) 標明分界方法所定義的權威參照標準裡其中ㄧ個組件。
• trait (trait) contains a description of some status or quality attributed to a person, place, or organization typically, but not necessarily, independent of the volition or action of the holder and usually not at some specific time or for a specific date range.
• event (event) 任何未必是口說的或溝通上的現象或發生情況，例如偶然的噪音或其他影響溝通的事件。
• att.locatable provides attributes for referencing locations by pointing to entries in a canonical list of places.

  where

  indicates one or more locations by pointing to a place element or other canonical description.

• listEvent (list of events) contains a list of descriptions, each of which provides information about an identifiable event.

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.

• idno (識別代碼) 提供任何用來識別書目項目的標準或非標準編碼。

  type	表明編碼的種類，例如國際標準書號 (ISBN) 或其他標準系列編碼。

TEI: The Person Element⚓︎14.3.2 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 14.3.3 Organizational Data below.

These elements may appear only within a listPerson element, which groups such descriptions together, and optionally also describes relationships amongst the people listed.

• listPerson (list of persons) 人物描述清單，其中每個項目包含一個已知人物的相關資料，例如語言互動中的參與者、或是歷史來源中提及的人物。
• listRelation 描述一項語言互動中參與者之間的關係或社交關聯。

One or more listPerson elements may be supplied within the standOff element (see 17.10 The standOff Container) 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 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:

• att.global.responsibility provides attributes indicating the agent responsible for some aspect of the text, the markup or something asserted by the markup, and the degree of certainty associated with it.

  cert	(certainty) 表示該更動或詮釋的相關正確度。
  resp	(responsible party) 指出負責該更動或詮釋的代理者，例如編輯或轉錄者。

• att.editLike 提供屬性，描述任何已標記的學者更正或詮釋的性質。

  evidence

  指出支持該更動或詮釋可信度或正確性的證明 被推薦的值包含: 1] internal; 2] external; 3] conjecture

• att.global.source provides attributes used by elements to point to an external source.

  source

  specifies the source from which some aspect of this element is drawn.

In addition, a small number of very commonly used personal properties may be recorded using attributes specific to person and personGrp:

• person (person) 提供一個已知人物的相關資料，例如語言互動中的參與者、或是歷史來源中提及的人物。

  role	說明該人物的主要角色或分類。
  sex	指出該人物的性別。
  age	指出該人物所屬的年齡層。

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

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:

• att.datable.w3c 提供用於元素規格化的屬性，這些元素包含以W3C datatypes所定義的日期明確之事件。

  when	supplies the value of the date or time in a standard form, e.g. yyyy-mm-dd.
  notBefore	以標準格式說明該事件可能發生的最早日期，例如年-月-日。
  notAfter	以標準形式標明該事件可能的最晚日期，例如年-月-日。
  from	以標準格式表示該段時間的起始點。
  to	以標準格式表示該段時間的結束點。

as discussed in 14.1 Attribute Classes Defined by This Module above.

TEI: Places⚓︎14.3.4 Places

In 14.2.3 Place Names 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:

• listPlace (list of places) contains a list of places, optionally followed by a list of relationships (other than containment) defined amongst them.
• place (place) contains data about a geographic location

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:

• placeName (place name) 包含一個確切位置或相對位置的名稱。
• location (location) defines the location of a place as a set of geographical coordinates, in terms of other named geo-political entities, or as an address.

TEI: Events⚓︎14.3.5 Events

• event (event) 任何未必是口說的或溝通上的現象或發生情況，例如偶然的噪音或其他影響溝通的事件。
• eventName (name of an event) contains a proper noun or noun phrase used to refer to an event.
• listEvent (list of events) contains a list of descriptions, each of which provides information about an identifiable event.

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.

The next example demonstrates the use of the where attribute with event, coordinated with location information stored in listPlace.

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

For event as a child element of person, note the Section 14.3.2.2 Personal Events.