13 Names, Dates, People, and Places
Table des matières
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 3.5 Names, Numbers, Dates, Abbreviations, and Addresses 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 (13.1 Attribute Classes Defined by This Module) before discussing specifically the elements provided for the encoding of component parts of personal names (section 13.2.1 Personal Names), place names (section 13.2.3 Place Names) and organizational names (section 13.2.2 Organizational Names). Elements for encoding personal and organizational data are discussed in section 13.3 Biographical and Prosopographical Data. Elements for the encoding of geographical data are discussed in section 13.3.4 Places. Finally, elements for encoding onomastic data are discussed in 13.3.5 Names and Nyms, and the detailed encoding of dates and times is described in section 13.3.6 Dates and Times.
TEI: Attribute Classes Defined by This Module¶13.1 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.
TEI: Linking Names and Their Referents¶13.1.1 Linking Names and Their Referents
- att.canonical fournit des attributs qui peuvent être utilisés pour associer une représentation telle qu'un nom ou un titre à l'information canonique concernant l'objet nommé ou auquel il est fait référence.
key fournit un moyen, défini de façon externe, d'identifier l'entité (ou les entités) nommé(es), en utilisant une valeur codée d'un certain type. ref (référence) fournit un moyen explicite de localiser une définition complète de l'entité nommée au moyen d'un ou plusieurs URIs.
- att.naming fournit des attributs communs aux éléments qui font référence à des personnes, lieux, organismes, etc., nommés.
role may be used to specify further information about the entity referenced by this name in the form of a set of whitespace-separated values, for example the occupation of a person, or the status of a place. nymRef (référence au nom canonique) indique comment localiser la forme canonique (nym) des noms qui sont associés à l'objet nommé par l'élément qui le contient.
<name role="politician" type="person">David Paul Brown</name> has suffered ...
<name ref="#DPB1" type="person">David Paul Brown</name> has suffered ...
DPB1
, which will contain canonical information about this particular person, marked up using the elements discussed in 13.3 Biographical and Prosopographical Data 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 16.2 Pointing Mechanisms: <name ref="http://www.example.com/personography.xml#DPB1"
type="person">David Paul Brown</name> has suffered
...
EBB1
, a reference to ‘the Browns’ might be encoded <name ref="#DPB1 #EBB1" type="person">the Browns</name> came to dine
...
to
<name key="FR" type="place">France</name>
However, as explained in 3.5.1 Referring Strings, 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 13.3.5 Names and Nyms for further discussion.
All members of the att.naming class inherit the following attributes from the att.global.responsibility class:
- att.global.responsibility provides attributes indicating the agency responsible for some aspect of the text, the markup or something asserted by the markup, and the degree of certainty associated with it.
resp (responsable) indique l'agent responsable de l'intervention ou de l'interprétation, par exemple un éditeur ou un transcripteur. cert (certitude) donne le degré de certitude associée à l'intervention ou à l'interprétation.
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.
TEI: Dating Attributes¶13.1.2 Dating Attributes
Members of the att.datable class share the following attributes:
- att.datable fournit des attributs pour la normalisation d'éléments qui contiennent des mentions d'événements datés ou susceptibles de l'être
period fournit un pointeur vers un emplacement donné définissant une période de temps nommée durant laquelle l'item concerné s'inscrit. - att.datable.w3c fournit des attributs pour la normalisation d'éléments qui contiennent des mentions d'événements datés ou susceptibles de l'être
when spécifie une date exacte pour un événement sous une forme normalisée, par ex. aaaa-mm-jj. notBefore spécifie la date la plus ancienne pour l'événement sous une forme normalisée, par ex. aaaa-mm-jj notAfter spécifie la date la plus récente possible pour l'événement sous une forme normalisée, par ex. aaaa-mm-jj from indique le point de départ d'une période sous une forme normalisée, par ex. aaaa-mm-jj to indique le terme de la période sous une forme normalisée, par ex. aaaa-mm-jj
period is approaching which will terminate my present
copartnership. On the <date when="1808-01-01">1st Jany.</date> next,
it expires by its own limitation.
<category xml:id="tyranny">
<catDesc>Before 510 BC</catDesc>
</category>
<category xml:id="classical">
<catDesc>Between 510 and 323 BC</catDesc>
</category>
<category xml:id="hellenistic">
<catDesc>
<ref target="http://www.wikipedia.com/wiki/Hellenistic">Hellenistic</ref>. Commonly treated as
<date notBefore="-0323" notAfter="-0031">from
the death of Alexander to the Roman conquest.</date>
</catDesc>
</category>
<category xml:id="roman">
<catDesc>
<ref target="http://www.wikipedia.com/wiki/Roman_Empire">Roman</ref>
</catDesc>
</category>
<category xml:id="christian">
<catDesc> The Christian period technically starts at the
birth of Jesus, but in
practice is considered to date from the conversion of Constantine
in <date when="0312">312 AD</date>. </catDesc>
</category>
</taxonomy>
notAfter="1857-04-30">Some time
in March or April of 1857.</birth>
to="1857-04-30">In March and April of 1857.</residence>
notAfter="1857-04-30">From the 1st of March to
some time in April of 1857.</residence>
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 13.3.6.3 More Expressive Normalizations below.
TEI: Names¶13.2 Names
TEI: Personal Names¶13.2.1 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:
- persName (nom de personne) contient un nom propre ou une expression nominale se référant à une personne, pouvant inclure tout ou partie de ses prénoms, noms de famille, titres honorifiques, noms ajoutés, etc.
- surname (nom de famille) contient un nom de famille (hérité) par opposition à un nom donné, nom de baptême ou surnom.
- forename (prénom) contient un prénom, qu'il soit donné ou un nom de baptême.
- roleName (rôle) contient un composant du nom d'une personne, indiquant que celle-ci a un rôle ou une position particulière dans la société, comme un titre ou un rang officiel.
- addName (nom additionnel) contient une composante de nom additionnelle, comme un surnom, une épithète, un alias ou toute autre expression descriptive utilisée dans un nom de personne.
- nameLink (lien entre les composants d'un nom) 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".
- genName (qualificatif générationnel de nom) contient une composante de nom utilisée pour distinguer des noms, par ailleurs similaires, sur la base de l'âge ou de la génération des personnes concernées.
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:
- att.personal (attributs des composantes des noms de personnes) attributs communs des éléments qui composent un nom de personne
full indique si la composante du nom est donnée en intégralité, sous forme d'abréviation ou simplement d'initiale. sort (ordre) précise dans quel ordre est placé la composante par rapport aux autres dans le nom d'une personne.
<rs ref="tag:projectname.org,2012:DPB1"
type="person">David Paul Brown</rs> has suffered the
furniture of his office to be seized
the third time for rent.
<rs ref="tag:projectname.org,2012:DPB1"
type="person">
<name>David Paul Brown</name>
</rs> has suffered ...
<name ref="tag:projectname.org,2012:DPB1"
type="person">David Paul Brown</name> has suffered ...
<persName ref="tag:projectname.org,2012:DPB1">David Paul Brown</persName> 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.
<surname>Roosevelt</surname>,
<forename>Franklin</forename>
<forename>Delano</forename>
</persName>
<persName>
<forename>Franklin</forename>
<forename>Delano</forename>
<surname>Roosevelt</surname>
</persName>
<forename type="first">Franklin</forename>
<forename type="middle">Delano</forename>
<surname>Roosevelt</surname>
</persName>
<persName>
<forename type="given">Margaret</forename>
<forename type="unused">Hilda</forename>
<surname type="birth">Roberts</surname>
<surname type="married">Thatcher</surname>
</persName>
<persName type="religious">Muhammad Ali</persName>
<persName>
<forename>Norman</forename>
<surname type="complex">St John Stevas</surname>
</persName>
<forename>Johan</forename>
<surname type="toponymic" ref="#dystvold">Dystvold</surname>
</persName>
<!-- ... -->
<placeName xml:id="dystvold">Dystvold</placeName>
<forename>Kara</forename>
<surname type="complex">
<surname type="paternal">Hattersley</surname>-
<surname type="maternal">Smith</surname>
</surname>
</persName>
<forename full="abb">Maggie</forename>
<surname>Thatcher</surname>
</persName>
<persName>
<forename>Peter</forename>
<surname>son of Herbert</surname>
</persName> gives the king 40 m. for
having custody of the land and heir of <persName>
<forename>John</forename>
<surname>son of Hugh</surname>
</persName>...
</s>
<persName>
<forename>Snorri</forename>
<forename>Sturluson</forename>
</persName>
to combine the two traditions in cyclic form.
<forename>Finnur</forename>
<surname>Jonsson</surname>
</persName>
acknowledged the artificiality of the procedure...
<forename>Egill</forename>
<addName type="patronym">Skallagrmsson</addName>
</persName>
<forename sort="2">Sergei</forename>
<forename sort="3" type="patronym">Mikhailovic</forename>
<surname sort="1">Uspensky</surname>
</persName>
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.
<surname>Marques</surname>
<genName>Junior</genName>,
<forename>Henrique</forename>
</persName>
<forename>Charles</forename>
<genName>II</genName>
</persName>
<forename>Rudolf</forename>
<genName>II</genName>
<surname type="dynasty">Hapsburg</surname>
</persName>
<surname>Smith</surname>
<genName>Minor</genName>
</persName>
<roleName type="honorific" full="abb">Mme</roleName>
<nameLink>de la</nameLink>
<surname>Rochefoucault</surname>
</persName>
<forename>Walter</forename>
<surname>de la Mare</surname>
</persName>
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:
- nobility
- An inherited or life-time title of nobility such as Lord, Viscount, Baron, etc.
- honorific
- An academic or other honorific prefixed to a name e.g. Doctor, Professor, Mrs., etc.
- office
- Membership of some elected or appointed organization such as President, Governor, etc.
- military
- Military rank such as Colonel.
- epithet
- 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 13.3 Biographical and Prosopographical Data.
<roleName type="nobility">Princess</roleName>
<forename>Grace</forename>
</persName>
type="pseudo">
<addName type="honorific">Grandma</addName>
<surname>Moses</surname>
</persName>
<roleName type="office">President</roleName>
<forename>Bill</forename>
<surname>Clinton</surname>
</persName>
<roleName type="military">Colonel</roleName>
<surname>Gaddafi</surname>
</persName>
<forename>Frederick</forename>
<addName type="epithet">the Great</addName>
</persName>
<roleName type="office">Governor</roleName>
<forename sort="2">Edmund</forename>
<forename full="init" sort="3">G.</forename>
<addName type="nick">Jerry</addName>
<addName type="epithet">Moonbeam</addName>
<surname sort="1">Brown</surname>
<genName full="abb">Jr</genName>.
</persName>
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 18 Feature Structures.
White space is allowed and therefore significant between elements within name, persName, orgName, and placeName. Therefore
<persName> <forename>Mary</forename> <forename>Ann</forename> <nameLink>De</nameLink><surname>Mint</surname> </persName>
encodes ‘Mary Ann DeMint’ and
<persName> <forename>Mary</forename><forename>Ann</forename> <nameLink>De</nameLink> <surname>Mint</surname> </persName>
encodes ‘MaryAnn De Mint’. See 1.3.1.1.5 XML Whitespace for more information on whitespace in XML.
TEI: Organizational Names¶13.2.2 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.
- orgName (nom d'organisation) contient le nom d'une organisation.
This element is a member of the same attribute classes as persName, as discussed above in 13.1.1 Linking Names and Their Referents.
interest was agitated in the
<orgName type="voluntary"
ref="tag:projectname.org,2012:PAS1">Pennsyla. Abolition Society</orgName>
interest was agitated in the <rs ref="tag:projectname.org,2012:PAS1"
type="org">
<name>Pennsyla. Abolition Society</name>
</rs>.
interest was agitated in the
<name ref="tag:projectname.org,2012:PAS1"
type="org">Pennsyla. Abolition
Society</name>.
<orgName type="acronym">BSkyB</orgName>
rather than the
<orgName type="acronym">BBC</orgName>
strong aversion to the <orgName type="phrase">United
States Government</orgName>, and of
predilection for self-government under
the
<orgName type="phrase">English Crown</orgName>
<surname>Ernst</surname> & <surname>Young</surname>
</orgName>
<orgName type="regional">
<orgName>IBM</orgName>
<country>UK</country>
</orgName> said ...
the <orgName>Democratic Whig <name type="role">party</name>
</orgName> 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 <hi>Welfare and Best Interests of the Community</hi>.
<orgName>Department of Modern History</orgName>
<orgName>
<name type="city">Glasgow</name>
<name type="role">University</name>
</orgName>
</orgName>
TEI: Place Names¶13.2.3 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 13.2.3.1 Geo-political Place Names). A place named simply in terms of geographical features such as mountains or rivers is represented using the geogName element (see section 13.2.3.2 Geographic Names). 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 13.2.3.3 Relative Place Names).
- placeName (nom de lieu) contient un nom de lieu absolu ou relatif.
- geogName (nom de lieu géographique) un nom associé à une caractéristique géographique comme Windrush Valley ou le Mont Sinaï.
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 13.3.4 Places below.
spending some time in our <rs ref="tag:projectname.org,2012:NY1"
type="place">modern <name ref="tag:projectname.org,2012:BA1"
type="place">Babylon</name>
</rs>, <name ref="tag:projectname.org,2012:NY1"
type="place">New York</name>, I have proceeded to
the <rs ref="tag:projectname.org,2012:PH1"
type="place">City of Brotherly Love</rs>.
time in our <placeName ref="tag:projectname.org,2012:NY1">modern
<placeName ref="tag:projectname.org,2012:BA1">Babylon</placeName>
</placeName>,
<placeName ref="tag:projectname.org,2012:NY1">New
York</placeName>, I have proceeded to the <placeName ref="tag:projectname.org,2012:PH1">City of
Brotherly Love</placeName>.
TEI: Geo-political Place Names¶13.2.3.1 Geo-political Place Names
NY</placeName>
- district (district) contient le nom d'une subdivision quelconque d'une ville, comme une paroisse, une circonscription électorale ou toute autre unité administrative ou géographique.
- settlement (lieu de peuplement) contient le nom d'un lieu de peuplement comme une cité, une ville ou un village, identifié comme une unité géo-politique ou administrative unique.
- region (région) contient le nom d'une unité administrative comme un état, une province ou un comté, plus grande qu'un lieu de peuplement, mais plus petite qu'un pays.
- country (pays) contient le nom d'une unité géo-politique, comme une nation, un pays, une colonie ou une communauté, plus grande ou administrativement supérieure à une région et plus petite qu'un bloc.
- bloc (bloc) contient le nom d'une unité géo-politique composée d'au moins deux états ou pays
<settlement type="city">Rochester</settlement>,
<region type="state">New York</region>
</placeName>
<country type="nation">Laos</country>,
<bloc type="sub-continent">Southeast Asia</bloc>
</placeName>
<district type="arondissement">6ème</district>
<settlement type="city">Paris, </settlement>
<country>France</country>
</placeName>
TEI: Geographic Names¶13.2.3.2 Geographic Names
type="river">Mississippi River</geogName>
In addition to the usual phrase level elements, the geogName element may contain the following specialized element:
- geogFeat (nom de caractéristique géographique) contient un nom commun identifiant une caractéristique géographique contenue dans un nom de lieu, comme vallée, mont, etc.
type="river">
<name>Mississippi</name>
<geogFeat>River</geogFeat>
</geogName>
separates two great corridors which run from <name ref="tag:projectname.org,2012:GLCO1"
type="place">Glencoe</name> into
<geogName ref="tag:projectname.org,2012:GLET1"
type="glen">
<geogFeat>Glen</geogFeat>
<name>Etive</name>
</geogName>, the
<geogName ref="tag:projectname.org,2012:LAGA1"
type="hill">
<geogFeat xml:lang="gd">Lairig</geogFeat>
<name>Gartain</name>
</geogName> and the
<geogName ref="tag:projectname.org,2012:LAEI1"
type="hill">
<geogFeat xml:lang="gd">Lairig</geogFeat>
<name>Eilde</name>
</geogName>
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 13.3.5 Names and Nyms.
TEI: Relative Place Names¶13.2.3.3 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’).
- offset (distance relative) la partie d'une expression temporelle ou spatiale qui indique la distance et/ou la direction entre les deux lieux, dates ou heures sur lesquels porte l'expression.
- measure (mesure) contient un mot ou une expression faisant référence à la quantité d'un objet ou d'un produit, comprenant en général un nombre, une unité et le nom d'un produit.
<offset>near the top of</offset>
<geogName>
<geogFeat>Mount</geogFeat>
<name>Sinai</name>
</geogName>
</placeName>
<measure>20 km</measure>
<offset>north of</offset>
<settlement type="city">Paris</settlement>
</placeName>
<measure unit="km" quantity="17.7">11 miles</measure>
<offset>Northwest of</offset>
<settlement type="city">Providence</settlement>, <region type="state">RI</region>
</placeName>
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 23.3 Personalization and Customization 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 13.3.5 Names and Nyms may also be of use. Alternatively, the meaning structure itself may be represented using feature structures (18 Feature Structures).
TEI: Biographical and Prosopographical Data¶13.3 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, for example 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 13.3.2 The Person Element) 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.
TEI: Basic Principles¶13.3.1 Basic Principles
Information about people, places, and organizations, 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.
‘Characteristics’ or ‘traits’ are typically independent of an individual's volition or action and can be either physical, such as sex or hair and eye colour, or cultural, such as ethnicity, caste, or faith. The distinction is not entirely straightforward, however: while sex is fairly obviously a physical trait, gender should rather be regarded as culturally determined, and the division of mankind into different ‘races’, proposed by early (white European) anthropologists on the basis of physical characteristics such as skin colour, hair type and skull measurements, is now considered to be more a social or mental construct. Furthermore, while some characteristics will obviously change over time, hair colour for example, none, in principle—not even sex—is immutable.
‘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.
By ‘changes in state’ are meant the events in a person's life 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 on any of 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 able to be documented, put into a time frame and be relatable to other statements or assertions of the same or any of the other types.
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 (statut) contient la description d'un statut ou d'une qualité actuels attribués à une personne, un lieu ou une organisation.
- trait (trait distinctif) contient la description d'une caractéristique culturelle et en principe permanente, attribuée à une personne ou à un lieu.
- event (évènement) contient des données liées à tout type d'évènement significatif dans l'existence d'une personne, d'un lieu ou d'une organisation.
where indique la localisation d'un évènement en pointant vers un élément place - listEvent (liste d'événements) contient une liste de descriptions, chacune d'entre elles fournissant des informations sur un événement connu.
TEI: The Person Element¶13.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 13.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 (liste de personnes) contient une liste d'éléments, chacun d'entre eux apportant des informations sur une personne précise ou sur un groupe de personnes, par exemple les participants à une interaction linguistique, ou les personnes citées dans une source historique.
- listRelation donne des informations sur les relations qui existent entre des personnes, des lieux, ou des organisations, soit de manière informelle en prose, soit de manière formelle.
One or more listPerson elements may be supplied within the particDesc (participant description) element in the profileDesc element of a TEI header (see 2.4 The Profile Description). Like other forms of list, however, the listPerson can also appear within the body of a text when the module defined by this chapter is included in a schema.
<particDesc>
<listPerson type="historical">
<person xml:id="ART1">
<persName>Arthur</persName>
</person>
<person xml:id="BERT1">
<persName>Bertrand</persName>
</person>
<!-- ... -->
</listPerson>
<listPerson type="mythological">
<person xml:id="ART2">
<persName>Arthur</persName>
</person>
<person xml:id="BERT2">
<persName>Bertrand</persName>
</person>
<!-- ... -->
</listPerson>
</particDesc>
</profileDesc>
The person element carries several attributes. As a member of the classes att.global.responsibility, and att.editLike, which is a subclass of the att.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 agency responsible for some aspect of the text, the markup or something asserted by the markup, and the degree of certainty associated with it.
cert (certitude) donne le degré de certitude associée à l'intervention ou à l'interprétation. resp (responsable) indique l'agent responsable de l'intervention ou de l'interprétation, par exemple un éditeur ou un transcripteur. - att.editLike fournit des attributs décrivant la nature d'une intervention savante encodée ou de tout autre interprétation.
evidence indique la nature de la preuve attestant la fiabilité ou la justesse de l'intervention ou de l'interprétation. Les valeurs suggérées comprennent: 1] internal; 2] external; 3] conjecture - att.source provides attributes for pointing to the source of a bibliographic reference.
source provides a pointer to the bibliographical source from which a quotation or citation is drawn.
In addition, a small number of very commonly used personal properties may be recorded using attributes specific to person and personGrp:
- person (personne) fournit des informations sur un individu identifiable, par exemple un participant à une interaction linguistique, ou une personne citée dans une source historique.
role précise un rôle principal ou une classification principale pour cette personne. sex précise le sexe de la personne. age précise une tranche d'âge pour la personne. - personGrp (groupe de personnes) décrit un groupe d'individus traité comme une personne unique à des fins d'analyse.
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.
module="namesdates" mode="change">
<attList>
<attDef mode="replace" ident="age">
<datatype>
<rng:ref name="data.enumerated"/>
</datatype>
<valList type="closed">
<valItem ident="child">
<desc>less than 18 years of age</desc>
</valItem>
<valItem ident="adult">
<desc>18 to 65 years of age</desc>
</valItem>
<valItem ident="retired">
<desc>over 65 years of age</desc>
</valItem>
</valList>
</attDef>
</attList>
</elementSpec>
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 fournit des attributs pour la normalisation d'éléments qui contiennent des mentions d'événements datés ou susceptibles de l'être
when spécifie une date exacte pour un événement sous une forme normalisée, par ex. aaaa-mm-jj. notBefore spécifie la date la plus ancienne pour l'événement sous une forme normalisée, par ex. aaaa-mm-jj notAfter spécifie la date la plus récente possible pour l'événement sous une forme normalisée, par ex. aaaa-mm-jj from indique le point de départ d'une période sous une forme normalisée, par ex. aaaa-mm-jj to indique le terme de la période sous une forme normalisée, par ex. aaaa-mm-jj
as discussed in 13.1 Attribute Classes Defined by This Module above.
TEI: Personal Characteristics¶13.3.2.1 Personal Characteristics
- faith (religion) précise la foi, la religion ou les croyances d'une personne.
- langKnowledge (connaissances linguistiques) synthétise l'état des connaissances linguistiques d'une personne, soit en texte libre soit par une liste d'éléments langKnown.
- nationality (nationalité) contient une description non formalisée de la nationalité ou citoyenneté présente ou passée d'une personne.
- sex (sexe) précise le sexe d'une personne.
- age (âge) précise l'âge d'une personne
- socecStatus (statut socio-économique) contient une description non formalisée du statut social ou économique d'une personne.
- persName (nom de personne) contient un nom propre ou une expression nominale se référant à une personne, pouvant inclure tout ou partie de ses prénoms, noms de famille, titres honorifiques, noms ajoutés, etc.
- occupation (activité) contient une description non formalisée de l'activité, de la profession ou de l'occupation d'une personne.
- residence (résidence) décrit les lieux de résidence présents ou passés d'une personne.
- affiliation (affiliation) contient une description non formalisée portant sur l'affiliation présente ou passée d'une personne à une organisation, par exemple un employeur ou un sponsor.
- education (éducation) contient la description du parcours scolaire d'une personne.
- floruit (période d'activité) contient des informations sur la période d'activité d'une personne.
- state (statut) contient la description d'un statut ou d'une qualité actuels attribués à une personne, un lieu ou une organisation.
- trait (trait distinctif) contient la description d'une caractéristique culturelle et en principe permanente, attribuée à une personne ou à un lieu.
The meanings of concepts such as sex, nationality, or age are highly culturally-dependent, and the encoder should take particular care to be explicit about any assumptions underlying their usage of them. For example, when recording personal age in different cultures, there may be different assumptions about the point from which age is reckoned. A statement of the practice adopted in a given encoding may usefully be provided in the editorialDecl element discussed in 2.3.3 The Editorial Practices Declaration.
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 ‘tag’s 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 vi.1. Language Identification.
<p>Speaks fluent Fulani, Wolof, and French. Some knowledge of English.</p>
</langKnowledge>
<langKnown level="fluent" tag="ff">Fulani</langKnown>
<langKnown level="fluent" tag="wo">Wolof</langKnown>
<langKnown level="fluent" tag="fr">French</langKnown>
<langKnown level="basic" tag="en">English</langKnown>
</langKnowledge>
- trait (trait distinctif) contient la description d'une caractéristique culturelle et en principe permanente, attribuée à une personne ou à un lieu.
- state (statut) contient la description d'un statut ou d'une qualité actuels attribués à une personne, un lieu ou une organisation.
<label>Ethnicity</label>
<desc>Ethnic Albanian.</desc>
</trait>
<label>eye colour</label>
<desc>blue</desc>
</trait>
<trait type="physical">
<label>hair colour</label>
<desc>brown</desc>
</trait>
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.
<persName xml:lang="is">Árni Magnússon</persName>
<persName xml:lang="da">Arne Magnusson</persName>
<persName xml:lang="la">Arnas Magnæus</persName>
</person>
<persName>Simon, son of Richard</persName>
<residence>
<placeName>
<region>Essex</region>
</placeName>
</residence>
<floruit notBefore="1219" notAfter="1223">1219-1223</floruit>
</person>
to="1780-07-12">
<p>Jón's first living — which he apparently accepted rather reluctantly — was at
<name type="place">Háls í Hamarsfirði</name>, <name type="place">Múlasýsla</name>, 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 <q xml:lang="da">promoveres til andet bedre kald, end det
hand hidindtil har havt</q>, and on 12 July it was agreed that
he should exchange livings with
<name type="person"
ref="tag:projectname.org,2012:ThorJon">sr. Þórður Jónsson</name> at
<name type="place">Kálfafell á Síðu</name>,
<name type="place">Skaftafellssýsla</name>.</p>
<bibl>ÞÍ, Stms I.15, p. 733.</bibl>
<bibl>ÞÍ, Stms I.17, p. 102.</bibl>
</state>
notBefore="2002-01-15">
<label>Nationality</label>
<desc>American citizen from 15 January 2002.</desc>
</state>
key="US"/>
TEI: Personal Events¶13.3.2.2 Personal Events
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 persons life, namely birth and death, are both ubiquitous and usually considered particularly important, and thus may be represented by specialized elements for the purpose:
- birth (naissance) contient des informations sur la naissance d'une personne, comme la date et le lieu
- death (décès) contient des informations sur le décès d'une personne, comme la date et le lieu.
<!-- ... -->
<event type="marriage" when="1859-04-26">
<label>Marriage</label>
<desc>
<name type="person" ref="#WM">William Morris</name> and <name type="person"
ref="http://en.wikipedia.org/wiki/Jane_Burden">Jane Burden</name> were
married at <name type="place">St Michael's Church, Ship Street, Oxford</name> on
<date when="1859-04-26">26 April 1859</date>. The wedding was
conducted by Morris's friend <name type="person" ref="#RWD">R. W.
Dixon</name> with <name type="person" ref="#CBF">Charles
Faulkner</name> as
the best man. The bride was given away by her father,
<name type="person" ref="#RB">Robert Burden</name>.
According to the account that <name type="person"
ref="http://en.wikipedia.org/wiki/Edward_Burne-Jones">Burne-Jones</name>
gave <name type="person" ref="#JWM">Mackail</name>
<quote>M. said to Dixon beforehand <said>Mind
you don't call her Mary</said> but he did</quote>. The entry in the
Register reads: <quote>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.</quote> 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.</desc>
<bibl>J. W. Mackail, <title>The Life of William Morris</title>, 1899.</bibl>
</event>
</person>
<person xml:id="RB">
<persName>Robert Burden</persName>
</person>
<person xml:id="RWD">
<persName>R.W. Dixon</persName>
</person>
<person xml:id="CBF">
<persName>Charles Faulkner</persName>
</person>
<person xml:id="EBJ">
<persName>
<forename>Edward</forename>
<surname>Burne-Jones</surname>
</persName>
</person>
<person xml:id="JWM">
<persName>J.W. Mackail</persName>
</person>
<relation name="friend" mutual="#WM #RWD"/>
<relation name="parent" active="#RB"
passive="#JBM"/>
<persName notAfter="1966">David Jones</persName>
<persName notBefore="1966">David Bowie</persName>
</person>
<p>Born in <name type="place">Brixton</name> on 8 January 1947.</p>
</event>
<event type="birth" resp="#ABC" cert="low">
<p>Born in <name type="place">Berkhamsted</name> on 9 January 1947.</p>
</event>
TEI: Personal Relationships¶13.3.2.3 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:
- listRelation donne des informations sur les relations qui existent entre des personnes, des lieux, ou des organisations, soit de manière informelle en prose, soit de manière formelle.
- relation (relation) décrit tout type de relation ou de lien à l'intérieur d'un groupe donné de participants.
name fournit un nom pour le type de relation dont elle est une instance. active identifie les participants actifs dans une relation à sens unique, ou tous les participants dans une relation réciproque. mutual fournit une liste de participants entre lesquels la relation est réciproque. passive identifie les participants ‘passifs’ dans une relation non mutuelle.
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’.
<relation name="parent" active="#P1 #P2"
passive="#P3 #P4"/>
<relation name="spouse" mutual="#P1 #P2"/>
<relation type="social" name="employer"
active="#P1" passive="#P3 #P4"/>
</listRelation>
- 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.
TEI: Organizational Data¶13.3.3 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.
- org (organisation) fournit des informations sur une organisation identifiable, telle qu'une entreprise, une tribu ou tout autre groupement de personnes.
- listOrg (liste d'organisations) contient une liste d'éléments, chacun d'eux fournissant des informations sur une organisation identifiable.
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 13.2.2 Organizational Names is however strongly recommended.
<orgName notAfter="1960">The Silver Beetles</orgName>
<orgName from="1960-08">The Beatles</orgName>
</org>
<orgName notAfter="1960">The Silver Beetles</orgName>
<orgName notBefore="1960">The Beatles</orgName>
<state type="membership" from="1960-08"
to="1962-05">
<desc>
<persName>John Lennon</persName>
<persName>Paul McCartney</persName>
<persName>George Harrison</persName>
<persName>Stuart Sutcliffe</persName>
<persName>Pete Best</persName>
</desc>
</state>
<state type="membership" notBefore="1963">
<desc>
<persName>John Lennon</persName>
<persName>Paul McCartney</persName>
<persName>George Harrison</persName>
<persName>Ringo Starr</persName>
</desc>
</state>
</org>
<orgName>Oxford University Computing Services</orgName>
<org xml:id="OUCSisg">
<orgName>Information and Support Group</orgName>
</org>
<org xml:id="OUCSig">
<orgName>Infrastructure Group</orgName>
<org xml:id="OUCSig.nt">
<orgName>Networking Team</orgName>
</org>
<org xml:id="OUCSig.sdt">
<orgName>System Development Team</orgName>
</org>
</org>
<org xml:id="OUCSltg">
<orgName>Learning Technologies Group</orgName>
</org>
</org>
<org xml:id="bu">
<orgName>Brown University</orgName>
<desc>The host contribution is made jointly by the <name type="project">Brown University Women Writers Project</name> and the
<orgName>Brown University Library's Center for Digital
Initiatives</orgName>.</desc>
</org>
<org xml:id="na">
<orgName>Nancy</orgName>
<desc>Hosting is provided by a group of institutions located in
Nancy, France, coordinated by <orgName>Loria</orgName> and also
including <orgName>ATILF</orgName> and <orgName>INIST</orgName>.</desc>
</org>
<org xml:id="ou">
<orgName>Oxford University</orgName>
<desc>Hosting is provided by the <orgName>Research Technologies
Service</orgName> at <orgName>Oxford University Computing
Services</orgName>.</desc>
</org>
<org xml:id="uv">
<orgName>University of Virginia</orgName>
<desc>Virginia's host support comes jointly from the
<orgName>Institute for Advanced Technology in the
Humanities</orgName> and the <orgName>University of Virginia
Library</orgName>.</desc>
</org>
</listOrg>
</p>
TEI: Places¶13.3.4 Places
In 13.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 (liste de lieux) contient une liste de lieux, qui peut être suivie d'une liste de relations définies entre les lieux (autres que la relation d'inclusion).
- place (lieu) contient des informations sur un lieu géographique.
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.
A place is defined, however, by its physical location, which does not typically change over time. 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 (nom de lieu) contient un nom de lieu absolu ou relatif.
- location (localisation) définit l'emplacement d'un lieu par des coordonnées géographiques, en termes d'entités nommées dites géopolitiques, ou par une adresse.
TEI: Varieties of Location¶13.3.4.1 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.
<placeName notBefore="1400">Lyon</placeName>
<placeName notAfter="0056">Lugdunum</placeName>
<location>
<geo>45.769559 4.834843</geo>
</location>
</place>
<placeName notBefore="1400">Lyon</placeName>
<placeName notAfter="0056">Lugdunum</placeName>
<location>
<bloc>EU</bloc>
<country>France</country>
</location>
</place>
<placeName>Brasserie Georges</placeName>
<location>
<country key="FR"/>
<settlement type="city">Lyon</settlement>
<district type="arrondissement">IIème</district>
<district type="quartier">Perrache</district>
<placeName type="street">Cours de Verdun</placeName>
</location>
</place>
<placeName>Atlantis</placeName>
<location>
<offset>beyond</offset>
<placeName>The Pillars of <persName>Hercules</persName>
</placeName>
</location>
</place>
<placeName notAfter="1969">Yasgur's Farm</placeName>
<placeName notBefore="1969">Woodstock Festival Site</placeName>
<location>
<measure>one mile</measure>
<offset>north west of</offset>
<settlement>Bethel</settlement>
<region>New York</region>
</location>
</place>
<placeName>Protestant Cemetery</placeName>
<placeName type="official" xml:lang="it">Cimitero Acattolico</placeName>
<location type="geopolitical">
<country>Italy</country>
<settlement>Rome</settlement>
<district>Testaccio</district>
</location>
<location type="address">
<address>
<addrLine>Via Caio Cestio, 6</addrLine>
<addrLine>00153 Roma</addrLine>
</address>
</location>
</place>
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 the Guidelines where specialized markup is required, for example to embed mathematical expressions or vector graphics, and is further described and exemplified in 23.3.4 Examples of Modification . For geographic information, suitable non-TEI vocabularies include:
- the OpenGIS Geography Markup Language (GML) being defined by the OGC50
- the Keyhole Markup Language (KML) used by Google Maps51
<placeName notBefore="1400">Lyon</placeName>
<placeName notAfter="0056">Lugdunum</placeName>
<location>
<geo>
<gml:Polygon>
<gml:exterior>
<gml:LinearRing> 45.256 -110.45 46.46 -109.48 43.84 -109.86 45.8 -109.2
45.256 -110.45 </gml:LinearRing></gml:exterior></gml:Polygon>
</geo>
</location>
</place>
A bibl element may be used within location to indicate the source of the location information.
<geo>53.226658 -0.541254</geo>
<bibl>
<title>Roman Inscriptions of Britain</title>, <idno>262</idno>
</bibl>
</location>
TEI: Multiple Places¶13.3.4.2 Multiple Places
<country>Lithuania</country>
<country xml:lang="lt">Lietuva</country>
<place>
<settlement>Vilnius</settlement>
</place>
<place>
<settlement>Kaunas</settlement>
</place>
</place>
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 (13.3.4.4 Relations Between Places).
type="islandGroup">
<placeName>Mascarene Islands</placeName>
<placeName>Mascarenhas Archipelago</placeName>
<place type="island">
<placeName>Mauritius</placeName>
<listPlace type="offshoreIslands">
<place>
<placeName>La roche qui pleure</placeName>
</place>
<place>
<placeName>Île aux cerfs</placeName>
</place>
</listPlace>
</place>
<place type="island">
<placeName>Rodrigues</placeName>
</place>
<place type="island">
<placeName>Réunion</placeName>
</place>
</place>
<placeName xml:lang="cy">Cymru</placeName>
<placeName xml:lang="en">Wales</placeName>
<placeName xml:lang="la">Wallie</placeName>
<placeName xml:lang="la">Wallia</placeName>
<placeName xml:lang="fro">Le Waleis</placeName>
<place xml:id="carmarthenshire"
type="region">
<region type="county" xml:lang="en"
notBefore="1284">Carmarthenshire</region>
<place xml:id="carmarthen"
type="settlement">
<placeName xml:lang="en">Carmarthen</placeName>
<placeName xml:lang="la"
notBefore="1090" notAfter="1300">Kaermerdin</placeName>
<placeName xml:lang="cy">Caerfyrddin</placeName>
<place xml:id="carmarthen_castle"
type="castle">
<settlement>castle of Carmarthen</settlement>
</place>
</place>
</place>
</place>
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.
<placeName>Herefordshire</placeName>
<listPlace type="villages">
<place xml:id="pl-v-AD">
<placeName>Abbey Dore</placeName>
<location>
<geo>51.969604 -2.893146</geo>
</location>
</place>
<place xml:id="pl-v-AB">
<placeName>Acton Beauchamp</placeName>
</place>
<!-- ... -->
</listPlace>
<listPlace type="towns">
<place xml:id="pl-t-H">
<placeName>Hereford</placeName>
</place>
<place xml:id="pl-t-L">
<placeName>Leominster</placeName>
</place>
<!-- ... -->
</listPlace>
</place>
TEI: States, Traits, and Events¶13.3.4.3 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:
- population (population) contient des informations sur la population d'un lieu.
- climate (climat) contient des informations sur le climat physique d'un lieu.
- terrain (terrain) contient des informations sur le terrain physique d'un lieu.
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.
<placeName xml:lang="en">Iceland</placeName>
<placeName xml:lang="is">Ísland</placeName>
<location>
<geo>65.00 -18.00</geo>
</location>
<terrain>
<desc>Area: 103,000 sq km</desc>
</terrain>
<state type="governance" notBefore="1944">
<p>Constitutional republic</p>
</state>
<state type="governance" notAfter="1944">
<p>Part of the kingdom of <placeName key="DK">Denmark</placeName>
</p>
</state>
<event type="governance" when="1944-06-17">
<desc>Iceland became independent on 17 June 1944.</desc>
</event>
<state type="governance" from="1944-06-17">
<p>An independent republic since June 1944</p>
</state>
</place>
<placeName>Greece</placeName>
<climate>
<desc>Greece's climate is divided into three well defined
classes:</desc>
<climate>
<label>Mediterranean</label>
<desc>It features mild, wet winters and hot, dry
summers. Temperatures rarely reach extremes, although snowfalls do
occur occasionally even in <placeName>Athens</placeName>,
<placeName>Cyclades</placeName> or <placeName>Crete</placeName>
during the winter.</desc>
</climate>
<climate>
<label>Alpine</label>
<desc>It is found primarily in <placeName>
<offset>Western</offset>
Greece</placeName> (<placeName>Epirus</placeName>,
<placeName>
<offset>Central</offset> Greece</placeName>,
<placeName>Thessaly</placeName>,
<placeName>
<offset>Western</offset> Macedonia</placeName> as well
as central parts of <placeName>Peloponnesus</placeName> like
<placeName>Achaea</placeName>, <placeName>Arcadia</placeName> and
parts of <placeName>Laconia</placeName> where the Alpine range pass
by)</desc>
</climate>
<climate>
<label>Temperate</label>
<desc>It is found in <placeName>
<offset>Central</offset> and
<offset>Eastern</offset> Macedonia</placeName> as well as in
<placeName>Thrace</placeName> at places like
<placeName>Komotini</placeName>, <placeName>Xanthi</placeName> and
<placeName>
<offset>northern</offset> Evros</placeName>. It features
cold, damp winters and hot, dry summers.</desc>
</climate>
</climate>
</place>
notBefore="1901" notAfter="1902-01-11" resp="#strabo">
<population type="red" when="1901-01-10">
<population type="female">
<desc>12</desc>
</population>
<population type="male">
<desc>15</desc>
</population>
</population>
<population type="gray" when="1902-01-10"
cert="high">
<population type="female">
<desc>23</desc>
</population>
<population type="male" cert="low"
resp="#biber">
<desc>45</desc>
</population>
</population>
</population>
<desc>All day meeting to resolve content models</desc>
<event type="preamble" notAfter="13:00:00">
<desc>first part</desc>
</event>
<event type="conclusions"
notBefore="13:00:00">
<desc>second part</desc>
</event>
</event>
An event element is usually used to record information about a place, or a person; for this reason the element usually appears as content of a place or person. However, it is also possible to describe events independently of either a person or a place. This may be useful in such applications as chronologies, lists of significant events such as battles, legislation, etc.
The listEvent element is a member of the model.listLike class, and may therefore appear wherever lists are permitted, in the same way as the listPerson, listPlace etc. elements described elsewhere in this chapter.
<event when="1713"
ref="http://eco.canadiana.ca/view/oocihm.9_01832">
<label>Treaty of Utrecht</label>
<desc>France ceded to Great Britain its claims to the <orgName>Hudson's Bay
Company</orgName> territories in <placeName>Rupert's Land</placeName>,
<placeName>Newfoundland</placeName>, and
<placeName>Acadia</placeName> and recognized British suzerainty over <orgName type="tribe">the Iroquois</orgName> but retained its other pre-war
North American possessions, including
<placeName key="PEI">Île-Saint-Jean</placeName> (now <placeName key="PEI">Prince Edward
Island</placeName>)...</desc>
</event>
<event when="1774" key="14-GeoIII-c83">
<label>Quebec Act</label>
<desc>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 <ref>Treaty of Paris</ref>.</desc>
</event>
<event when="1778"
ref="http://avalon.law.yale.edu/18th_century/del1778.asp">
<label>Treaty of Fort Pitt</label>
<desc>Also known as the <name type="event">Treaty with the
Delawares</name>, this was the first written treaty between the newly
formed <orgName>United States</orgName> and any Native American people, in this
case, the <orgName type="tribe">Lenape</orgName> or Delawares.</desc>
</event>
</listEvent>
TEI: Relations Between Places¶13.3.4.4 Relations Between Places
<place xml:id="MASC">
<placeName>Mascarene islands</placeName>
<placeName>Mascarenhas Archipelago</placeName>
</place>
<place xml:id="MRU">
<placeName>Mauritius</placeName>
<!-- ... -->
</place>
<place xml:id="ROD">
<placeName>Rodrigues</placeName>
</place>
<place xml:id="REN">
<placeName>Réunion</placeName>
</place>
<relation name="contains" active="#MASC"
passive="#ROD #MRU #REN"/>
</listPlace>
<placeName>France</placeName>
</place>
passive="#FRA #MASC"/>
TEI: Names and Nyms¶13.3.5 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:
- listNym (liste de noms canoniques) contient une liste de noms normalisés pour tous types d'objets.
- nym (nom canonique) contient la définition de tout nom ou partie de nom dans leur forme canonique.
<nym xml:id="N123">
<form>Antony</form>
</nym>
<!-- other nym definitions here -->
</listNym>
....
<person xml:id="BLT">
<persName>Tony Blair</persName>
<occupation>politician</occupation>
</person>
<form>
<orth xml:lang="en-US">Ian</orth>
<orth xml:lang="en-x-Scots">Iain</orth>
</form>
</nym>
<form>Bogomil</form>
<etym>Means <gloss>favoured by God</gloss> from the
<lang>Slavic</lang> elements <mentioned xml:lang="ru">bog</mentioned>
<gloss>God</gloss> and <mentioned xml:lang="ru">mil</mentioned>
<gloss>favour</gloss>
</etym>
</nym>
<form>
<choice>
<seg type="morph">
<seg>Bog</seg>
<seg>o</seg>
<seg>mil</seg>
</seg>
<seg type="morph">
<seg>Bogo</seg>
<seg>mil</seg>
</seg>
</choice>
</form>
</nym>
<form>bog</form>
</nym>
<nym xml:id="M1" type="part">
<form>mil</form>
</nym>
<form>Bogomil</form>
</nym>
<form xml:lang="la">Iohannes</form>
<nym xml:id="J450">
<form xml:lang="en">John</form>
<nym xml:id="J4501">
<form>Johnny</form>
</nym>
<nym xml:id="J4502">
<form>Jon</form>
</nym>
</nym>
<nym xml:id="J455">
<form xml:lang="ru">Ivan</form>
</nym>
<nym xml:id="J453">
<form xml:lang="fr">Jean</form>
</nym>
</nym>
type="hill">
<geogFeat xml:lang="gd" nymRef="#LAIRG">Lairig</geogFeat>
<name>Eilde</name>
</geogName>
...
<nym xml:id="LAIRG">
<form xml:lang="gd">lairig</form>
<def>sloping hill face</def>
</nym>
...
As noted above, use of these elements implies that both the dictionaries and the namesdates modules are included in a schema.
TEI: Dates and Times¶13.3.6 Dates and Times
The following elements for the encoding of dates and times were introduced in section 3.5.4 Dates and Times:
- date (date) contient une date exprimée dans n'importe quel format.
- time (temps) contient une expression qui précise un moment de la journée sous n'importe quelle forme.
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:
- offset (distance relative) la partie d'une expression temporelle ou spatiale qui indique la distance et/ou la direction entre les deux lieux, dates ou heures sur lesquels porte l'expression.
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:
- att.datable.w3c fournit des attributs pour la normalisation d'éléments qui contiennent des mentions d'événements datés ou susceptibles de l'être
when spécifie une date exacte pour un événement sous une forme normalisée, par ex. aaaa-mm-jj. - att.duration.w3c attributs pour enregistrer des durées de temps normalisées
dur (durée) indique la longueur de cet élément dans le temps
TEI: Relative Dates and Times ¶13.3.6.1 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.
<date dur="P14D">A fortnight</date>
<offset>before</offset>
<date when="1786-12-25" type="holiday">Christmas 1786</date>
</date>
<time dur="PT30M0S">precisely half an hour</time>
<offset>after</offset>
<time when="13:45:00" type="occasion">the departure of the afternoon train to Boston</time>
</time>
<date>A week</date>
<offset>before</offset>
<date when="--12-09">
<date type="occasion">my birthday</date>
on <date>9th December</date>
</date>
</date>
<date>A week</date>
<offset>before</offset>
<date type="occasion" when="--12-16">my birthday</date>
on <date>9th December</date>
</date>
and wickedness; it sends our multitudes to pollute and demoralize the
country.
<f name="event">
<string>the Fair</string>
</f>
<f name="place">
<string>Glasgow</string>
</f>
<f name="year">
<numeric value="1850"/>
</f>
<f name="from-value">
<string>1850-08-08</string>
</f>
<f name="to-value">
<string>1850-09-19</string>
</f>
</fs>
TEI: Absolute Dates and Times¶13.3.6.2 Absolute Dates and Times
The following are examples of absolute temporal expressions.
of American affairs produced a stinging attack by Edmund Burke in the
Commons debate of <date when="1775-10-26">26 October 1775</date>
holidays, <date when="--07-04" type="occasion">Independence Day</date>
the most turbulent.
<time type="twentyfourHour" when="13:45:00">13:45</time>
<time xml:lang="en-US" type="descriptive"
when="13:45:00-05:00"> a quarter of two
</time>
TEI: More Expressive Normalizations¶13.3.6.3 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.
- att.datable.iso fournit des attributs pour la normalisation, selon la norme ISO 8601, d'éléments contenant des évènements datables.
when-iso précise une date exacte pour l'évènement selon la forme normalisée ISO 8601, c'est-à-dire aaaa-mm-jj. notBefore-iso précise la première date possible pour l'évènement selon la forme normalisée, c'est-à-dire aaaa-mm-jj. notAfter-iso précise la dernière date possible pour l'évènement selon la forme normalisée, c'est-à-dire aaaa-mm-jj. from-iso Indique le point de départ de la période sous une forme normalisée to-iso Indique le point final de la période sous une forme normalisée - att.duration.iso attributs pour l'enregistrement de durées temporelles normalisées.
dur-iso (durée) indique la longueur de cet élément dans le temps
<date from="1301" dur="P100Y">fourteenth century</date>
<date when-iso="1301/1400">fourteenth century</date>
<date when-iso="1301/P100Y">fourteenth century</date>
TEI: Using Non-Gregorian Calendars¶13.3.6.4 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 2.4.5 Calendar Description:
<calendar xml:id="Julian_England">
<p>The Julian calendar, as used in late 16th-century England.</p>
</calendar>
</calendarDesc>
- att.datable fournit des attributs pour la normalisation d'éléments qui contiennent des mentions d'événements datés ou susceptibles de l'être
calendar indique le système ou le calendrier auquel appartient la date exprimée dans le contenu de l'élément. - att.datable.custom provides attributes for normalization of elements that contain datable events to a custom dating system (i.e. other than the Gregorian used by W3 and ISO).
when-custom supplies the value of a date or time in some custom standard form. notBefore-custom specifies the earliest possible date for the event in some custom standard form. notAfter-custom specifies the latest possible date for the event in some custom standard form. from-custom indicates the starting point of the period in some custom standard form. to-custom indicates the ending point of the period in some custom standard form. datingMethod supplies a pointer to a calendar element or other means of interpreting the values of the custom dating attributes.
large water in the yeare <date calendar="#Julian_England">1244</date>.
</p>
That Celebrated the Solemnity of the right Honorable
Sr Francis Iones Knight, at his Inauguration into the
Maioraltie of London, on Monday being the
<date when-custom="1620-10-30"
datingMethod="#Julian_England" calendar="#Julian_England"> 30. of October, 1620.
</date>
</head>
when="1620-11-09" datingMethod="#Julian_England"
calendar="#Julian_England"> 30. of October, 1620.
</date>
TEI: Module for Names and Dates¶13.4 Module for Names and Dates
The module described in this chapter makes available the following components:
- Module namesdates: Noms, dates, personnes et lieux
- Eléments définis: addName affiliation age birth bloc climate country death district education event faith floruit forename genName geo geogFeat geogName langKnowledge langKnown listEvent listNym listOrg listPerson listPlace listRelation location nameLink nationality nym occupation offset org orgName persName person personGrp place placeName population region relation residence roleName settlement sex socecStatus state surname terrain trait
- Classes définies: att.datable.custom att.datable.iso model.persNamePart
The selection and combination of modules to form a TEI schema is described in 1.2 Defining a TEI Schema.