<!-- $Id: p2nd.odd,v 1.9 1998/01/31 19:50:52 tei Exp $ -->
<!--*
    * $Log: p2nd.odd,v $
    * Revision 1.9  1998/01/31 19:50:52  tei
    * Change system 'tei2.dtd' to public identifier
    * fix log keyword (if not already fixed)
    * normalize the sgml
    *
    * Revision 1.8  1998/01/30 12:07:28  tei
    * *** empty log message ***
    *
    * Revision 1.7  1998/01/29 17:05:51  tei
    * lowercase DTD filename
    * normalize SGML
    *
    * Revision 1.6  1994/04/08 18:54:36  msmcq
    * Last-second fixes for P3
    *
    * Revision 1.5  1994/04/01  16:25:55  msmcq
    * Changes while validating DTDs
    *-->
<!-- Revisions:                                               -->
<!-- 98-01-29 : MSM : lowercase DTD file name, normalize      -->
<!-- 94-04-07 : MSM : trivia                                  -->
<!-- 94-03-31 : MSM : add declaration for a.names             -->
<!-- 94-03-31 : MSM : explicitly identify files for this tag set -->
<!-- 6 mar: killed measure; add para on virtual objects -->
<!-- 93-06-03 : MSM : add editorial note                      -->
<!-- 21 May LB : rewrote to go with DG's post-Eynsham version -->
<!-- 9 apr 93: added tagdecls -->
<!-- From: Dan Greenstein <digger@uk.ac.glasgow.udcf>   -->
<!-- Date: Wed, 1 Jul 92 15:20:47 BST   -->


<div1 id="ND" n="20"><head>Names and Dates</head>

<p>This chapter describes an additional tag set which may be used for
the encoding of proper names and other phrases descriptive of persons,
places, organizations, and also of dates and times, in a manner more
detailed than that possible using the elements already provided for
these purposes in the core tag set described in chapter <ptr
target="CO">.</p>

<p>In section <ptr target="COna"> it was noted that the elements
provided in the core allow the encoder to specify that a given
text segment is a proper noun, or a <term>referring string</term>, and
to specify the kind of object named or referred to only by supplying a
value for the <att>type</att> attribute. The elements provided by the
present tag set allow the encoder both to supply a detailed
sub-structure for such referring strings, and also to distinguish
explicitly between names of persons, places or organizations.</p>

<p>Similarly, the elements provided here allow the encoder to supply a
detailed analysis of the component parts of any expression which
denotes a date or time, which is not possible using the elements
described in section <ptr target="COnada">.</p>

<p>It should be noted however that no provision is made by the present
tag set for the representation of the abstract structures, or
<socalled> virtual objects</socalled> to which names or dates may be
said to refer. In simple terms, where the core tag set allows one to
represent a <term>name</term>, this additional tag set allows one to
represent a <term>personal name</term>, but neither provides for the
direct representation of a <term>person</term>. Appropriate
mechanisms for the encoding of such interpretative gestures may be
found in chapters <ptr target="AI"> and <ptr target="FS">.</p>

<p>To enable the additional tag set described in the present chapter,
a parameter entity <term>TEI.names.dates</term> must be declared in
the document type subset with the value <code>INCLUDE</code>, as
further described in section <ptr target="STin">. A document using the
prose base tag set and this additional tag set will thus begin as
follows:

<eg>
<![ CDATA [
 <!DOCTYPE TEI.2 PUBLIC "-//TEI P3//DTD Main Document Type//EN"
                        "tei2.dtd" [
      <!ENTITY % TEI.prose 'INCLUDE' >
      <!ENTITY % TEI.names.dates 'INCLUDE' >
 ]>
]]>
</eg></p>

<p>The chapter begins by discussing additional tags for the
encoding of component parts of personal names (section <ptr
target="NDper">, place names (section <ptr target="NDplac">) and
organizational names (section <ptr target="NDorg">). Detailed encoding of
dates and times is described in section <ptr target="NDdate">.
<!-- ) and on measures (section <ptr target=NDmeas>). --></p>

<p>The additional tag set for names and dates, included in the file
<ident type="file">teind2.dtd</ident>, has the following overall
structure:

<eg id=dnd>
<![ CDATA [
<!-- 20:  Additional tags for names and dates                 -->
<!-- ... declarations from section 20.1                       -->
<!--     (Personal names)                                     -->
<!--     go here ...                                          -->
<!-- ... declarations from section 20.2.3                     -->
<!--     (Names for places)                                   -->
<!--     go here ...                                          -->
<!-- ... declarations from section 20.3                       -->
<!--     (Organization names)                                 -->
<!--     go here ...                                          -->
<!-- ... declarations from section 20.4.2                     -->
<!--     (Date components)                                    -->
<!--     go here ...                                          -->
<!-- <dtdref dtdfrag=dndmeas> -->
]]>
</eg>
</p>

<p>When this tag set is enabled, three additional element classes
called <term>persPart</term>, <term>placePart</term>, and
<term>temporalExpr</term> are declared.  The parameter entities
corresponding with these classes are declared in the file
<ident type="file">teind2.ent</ident>, as follows:

<eg id=dndent>
<![ CDATA [
<!-- 20:  Additional classes for names and dates              -->
<!ENTITY % x.personPart ''                                      >
<!ENTITY % m.personPart '%x.personPart addName | forename | 
           genName | nameLink | roleName | surname'             >
<!ENTITY % x.placePart ''                                       >
<!ENTITY % m.placePart '%x.placePart bloc | country | distance 
           | geog | offset | region | settlement'               >
<!ENTITY % x.temporalExpr ''                                    >
<!ENTITY % m.temporalExpr '%x.temporalExpr dateStruct | day | 
           distance | hour | minute | month | occasion | offset 
           | second | timeStruct | week | year'                 >
<!ENTITY % a.names '
          reg                CDATA               #IMPLIED
          key                CDATA               #IMPLIED'      >
<!ENTITY % a.personPart '    %a.names;
          sort               NUMBER              #IMPLIED
          type               CDATA               #IMPLIED
          full               (yes | abb | init)  yes'           >
<!ENTITY % a.placePart '     %a.names;
          type               CDATA               #IMPLIED
          full               (yes | abb | init)  yes'           >
<!ENTITY % a.temporalExpr '
          reg                CDATA               #IMPLIED
          value              CDATA               #IMPLIED
          type               CDATA               #IMPLIED
          full               (yes | abb | init)  yes'           >
]]>
</eg>

</p>
<!--* $Id: p2ndper.odd,v 1.7 1998/01/28 12:01:27 lou Exp $ *-->
<!--*
    * $Log: p2ndper.odd,v $
# Revision 1.7  1998/01/28  12:01:27  lou
# LB changes of Jan 1998 and RCS keywords
#
    *-->
<!-- $Id: p2ndper.odd,v 1.7 1998/01/28 12:01:27 lou Exp $ -->
<!-- $Log: p2ndper.odd,v $
# Revision 1.7  1998/01/28  12:01:27  lou
# LB changes of Jan 1998 and RCS keywords
#
# Revision 1.6  1994/04/08  18:54:36  msmcq
# Last-second fixes for P3
#
# Revision 1.5  1994/04/01  16:25:55  msmcq
# Changes while validating DTDs
# -->
<!-- Revisions:                                               -->
<!-- 5 jan 98 : LB : fix typos in egs; typo from MSM          -->
<!-- 94-04-07 : MSM : clarify treatment of patronymics        -->
<!-- 94-03-31 : MSM : disambiguate TERM, Q                    -->
<!-- 94-03-29 : MSM : include persname in dtdfrag             -->
<!-- 94-03-29 : MSM : Added RCS id                            -->
<!-- 93-06-05 : MSM : remove leading blank from P elems       -->
<!-- 21 may LB made parseable; lightly edited -->
<div2 id=NDper><head>Personal Names</head>

<p>The core <gi>rs</gi> and <gi>name</gi> 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 referencing string
such as <q>John, by the grace of God, king of England, lord of
Ireland, duke of Normandy and Aquitaine, and count of Anjou</q>, the
analyst will often wish to distinguish among components giving some
hint as to the status, occupation or residence of the person to whom
the name belongs.  The following elements are provided for these and
related purposes:

<list type=gloss>
<label><gi>persName</gi></label>
<item>contains a proper noun or proper-noun phrase referring to

a person, possibly including any or all of the person's 
forename,
surname, honorific, added names, etc.</item>
<label><gi>surname</gi></label>
<item>contains a family (inherited) name, as opposed to a given,

baptismal, or nick name.</item>
<label><gi>forename</gi></label>
<item>contains a forename, given or baptismal name.</item>
<label><gi>roleName</gi></label>
<item>contains a name component which indicates that the referent 
has a
particular role or position in society, such as an 
official title or
rank.</item>
<label><gi>addName</gi></label>
<item>contains an additional name component, such as a nickname,

epithet, or alias, or any other descriptive phrase used 
within a
personal name.</item>
<label><gi>nameLink</gi></label>
<item>contains a connecting phrase or link used within a name but 
not
regarded as part of it, such as  <q>van der</q> or 
<q>of</q>.</item>
<label><gi>genName</gi></label>
<item>contains a name component used to indicating generational

information, such as <q>Junior</q>, or a number used in a 
monarch's
name.</item>
</list>


<p>As members of the <ident type=class>names</ident> class, all of these
elements share the following attributes:

<list type=gloss>
<label><att>key</att></label>
<item>provides an alternative identifier for the object being 
named, such as a database record key.</item>
<label><att>reg</att></label>
<item>gives a normalized or regularized form of the name used.</item>
</list>

<p>Additionally, all of the above elements except for <gi>persName</gi>
are members of the class <ident type=class>personPart</ident>, and thus
share the following attributes:

<list type=gloss>
<label><att>type</att></label>
<item>provides more culture- linguistic- or application- specific 
information used to categorize this name component.</item>
<label><att>full</att></label>
<item>indicates whether the name component is given in full, as 
an abbreviation or simply as an initial.
Legal values are:
<list type=gloss>
<label><term>init</term></label>
<item>the name component is indicated only by one initial.</item>
<label><term>yes</term></label>
<item>the name component is spelled out in full.</item>
<label><term>abb</term></label>
<item>the name component is given in an abbreviated form.</item>
</list></item>
<label><att>sort</att></label>
<item>specifies the sort order of the name component in relation 
to others within the personal name.</item>
</list>

<!-- key and reg are inherited by pname from name -->

<p>The <gi>persName</gi> element may be used in preference to the
general <gi>name</gi> element irrespective of whether or not the
components of the personal name are also to be marked. Its
<att>key</att> and <att>reg</att> attributes are used in exactly the
same way as those on the <gi>rs</gi> and <gi>name</gi> elements (see
section <ptr target=COna>). The tag <gi>persName</gi> is synonymous
with the tag <tag>name type=person</tag>, except that its
<att>type</att> attribute allows for further subcategorization of the
personal name for example as a <q>married</q>, <q>maiden</q>,
<q>pen</q>, <q>pseudo</q> or <q>religious</q> name.  Consequently the
following examples are equivalent:

<eg> <![CDATA [

That silly man <rs key=DPB1 type=person reg='Brown, David
Paul'>David Paul Brown</rs> has suffered the furniture of
his office to be seized the third time for rent.

That silly man
<rs key=DPB1 type=person reg='Brown, David Paul'>
<name>David Paul Brown</name>
</rs> has suffered the furniture of
his office to be seized the third time for rent.

That silly man
<name key=DPB1 type=person reg='Brown, David Paul'>
David Paul Brown</name> has suffered ...

That silly man
<persName key=DPB1 type=person reg='Brown, David Paul'>
David Paul Brown</persName> has suffered ...

]]>
</eg>

<p>The <gi>persName</gi> element is more powerful than the
<gi>rs</gi> and <gi>name</gi> elements because distinctive name
components occurring within it can be marked as such.

<p>Many cultures distinguish between a family or inherited
<term>surname</term> and additional personal names, often known as
<term>given names</term>.  These should be tagged using the
<gi>surname</gi> and <gi>forename</gi> elements respectively and may
occur in any order:

<eg><![ CDATA[
<persName key=FDR1>
  <surname>Roosevelt</surname>,
  <forename>Franklin</forename>
  <forename>Delano</forename>
</persName>

<persName key=FDR1>
  <forename>Franklin</forename>
  <forename>Delano</forename>
  <surname>Roosevelt</surname>
</persName>
]]>
</eg>

<p>The <att>type</att> attribute may be used with both
<gi>forename</gi> and <gi>surname</gi> elements to provide further
culture- or project- specific detail about the name component, for
example:

<eg><![ CDATA[

<persName key=FDR1>
 <forename type='first'>Franklin</forename>
 <forename type='middle'>Delano</forename>
 <surname type='last'>Roosevelt</surname>
</persName>

<persName key=MRT1>
 <forename type='Christian'>Margaret</forename>
 <forename type='unused'>Hilda</forename>
 <surname type='maiden'>Roberts</surname>
 <surname type='married'>Thatcher</surname>
</persName>

<persName key=MUAL1 type=religious>
 <forename>Muhammad</forename>
 <surname>Ali</surname>
</persName>
]]>
</eg>

In the following two examples the <att>type</att> attribute of the
<gi>surname</gi> element is used to indicate so-called
double-barrelled or hyphenated surnames:

<eg><![ CDATA[
<persName key=KHS1>
  <forename>Kara</forename>
  <surname type=combine>Hattersley-Smith</surname>
</persName>

<persName key=NSJS1>
   <forename>Norman</forename>
   <surname type=combine>St John Stevas</surname>
</persName>
]]>
</eg>

<p>In most cases, patronymics should be treated as forenames, thus:

<eg>
<![ CDATA [
 ... but it remained for
 <persName>
   <forename>Snorri</>
   <forename>Sturluson</>
 </persName>
 to combine the two traditions in cyclic form.
]]>
</eg>
<!-- Carol Clover, The Medieval Saga (Ithaca:  Cornell        -->
<!-- Univ. Press, 1982), p. 57.                               -->

When a patronymic is used as a surname, however (e.g. by an individual
who otherwise would have no surname, but lives in a culture which
requires surnames), it may be tagged as such:

<eg>
<![ CDATA [
Even <persName><forename>Finnur</> <surname>Jonsson</>
</persName> acknowledged the artificiality of the
procedure:  <q>As <title>Nj&aacute;la</> now begins,
no original saga ever began.</q>
]]>
</eg>
<!-- Clover, p. 77.                                           -->

In the following example, the <att>type</att> attribute is used
to distinguish a patronymic from other forenames:

<eg><![ CDATA[
<persName key=pn9>
  <forename sort=2>Sergei</forename>
  <forename sort=3 type='patronym'>Mikhailovic</forename>
  <surname sort=1>Uspensky</surname>
</persName>
]]>
</eg>

<p>This example also demonstrates the use of the <att>sort</att>
attribute common to all members of the
<ident type=class>personPart</ident> class; its effect is to state the
sequence in which <gi>forename</gi> and <gi>surname</gi> elements should
be combined when constructing a sort key for the name.

<p>Some names include generational or dynastic information, such as
<q>Junior</q> or <q>senior</q>, or a number: the <gi>genName</gi>
element may be used to distinguish these from other parts of the name,
as in the following examples:

<eg><![ CDATA[
<persName key=HEMA1>
  <surname>Marques</surname>
  <genName>Junior</genName>,
  <forename>Henrique</forename>
</persName>

<persName>
  <foreName>Charles</foreName>
  <genName>II</genName>
</persName>

]]>
</eg>

<p>It is also often convenient to distinguish phrases (historically
similar to the generational labels mentioned above) used to link parts
of a name together, such as <q>von</q>, <q>of</q>, <q>de</q> etc. It
is often a matter of arbitrary choice whether or not such components
are regarded as part of the surname or not; the <gi>nameLink</gi>
element is provided as a means of making clear what the correct usage
should be in a given case, as in the following examples:

<eg>
<![ CDATA [
<persName key=DUDO1>
 <roleName type=honorific full=abb>Mme</roleName>
 <nameLink>de la</nameLink>
 <surname>Rochefoucault</surname>
</persName>

<persName>
  <foreName>Walter</foreName>
   <surname>de la Mare</surname>
</persname>
]]>
</eg>

<p>Finally, the <gi>addName</gi> and <gi>roleName</gi> elements are
used to mark all name components other than those already listed. The
distinction between them is that a <gi>roleName</gi> 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
<att>type</att> 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:
<list type=gloss>
<label>nobility<item>An inherited or life-time
title of nobility such as Lord, Viscount, Baron, etc.
<label>honorific<item>An academic or other honorific prefixed to a name
e.g.  Dr., Professor, Mrs., etc.
<label>office<item>Membership of some elected or
appointed organization such as President, Governor, etc.
<label>military<item>Military rank such as Colonel.
<label>epithet<item>A traditional descriptive phrase
or nick-name such as The Hammer, The Great, etc.
</list>

<p>Here are some further examples of the usage of these elements:

<eg><![ CDATA[
<persName key=PGK1>
<roleName type=nobility>Princess</roleName>
<forename>Grace</forename>
</persName>

<persName key=GRMO1 type=pseudo>
<addName type=honorific>Grandma</addName>
<surname>Moses</surname>
</persName>

<persName key=MRSRO1>
<addName type=honorific>Mrs</addName>
<surname>Robinson</surname>
</persName>

<persName key=STAU1>
<roleName type=office>Saint</roleName>
<forename>Augustine</forename>
</persName>

<persName key=SLWICL1>
<roleName type=office>President</roleName>
<foreName>Bill</foreName>
<surname>Clinton</surname>
</persName>

<persName key=MOGA1>
<roleName type=military>Colonel</roleName>
<surname>Gaddafi</surname>
</persName>

<persName key=FRTG1>
<forename>Frederick</forename>
<addname type=epithet>the Great</addname>
</persName>
]]>
</eg>

<p>A name may have any combination of the above elements:

<eg><![ CDATA[
     <persName key=EGBR1>
     <roleName type=office>Governor</roleName>
     <forename sort=2>Edmund</foreName>
     <forename sort=3 full=init reg='Gerald'>G</forename>.
     <addName type=nick>Jerry</addName>
     <addName type=epithet>Moonbeam</addName>
     <surname sort=1>Brown</surname>
     <genName full=abb>Jr</genName>.
     </persName>
]]>
</eg>

<p>Although highly flexible, these mechanisms for marking
personal name components will not cater for every personal name
and 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 <ptr target=FS>.

<!-- Earl/Marquis example cut for now. Sorry. -->

<!--

<p>In the following brief example a feature structure is used to
represent an analyis of a personal name that appears twice in a
seventeenth-century Scottish legal document known as a sasine.  In the
sasine, the expressions <q>Archibald late earl of Argyle</q> and
<q>the late Marquis of Argyle</q> occur, but in context which make
apparent that both phrases refer to the same person at different times
in his life.  (Archibald would have remained a Marquis until his
father died at which time he would have become an Earl).  Though
crucial to a prosopographical analysis or a study of land ownership
based partly on the sasine, the interpretation of these two names
would be difficult or even impossible to mark with the elements
described in this section.

<p>The feature structure presented below is envisaged as a
collective biography about individuals.  An individual's
biographical detail are represented as features of a feature
structure of type <code type=val>person</code>.  For each feature
structure of type <code type=val>person</code>, features include
<code type=val>persName</code>, <code type=val>date-of-birth</code>,
<code type=val>place-of-birth</code>, etc.  The several feature
structures of type <code type=val>person</code> are then grouped
together in a so-called library of feature structures (<gi>fsLib</gi>)
not dissimilar to a database comprising biographical information on
several individuals.

<p>The portion of
the feature structure library shown below refers to Archibald.
It shows that several pieces of information have been collected
for Archibald, amongst them, information pertaining to his
personal name. It is this particular portion of the feature
structure that we are particularly interested in.

<p>Notice three things. Firstly, that the value of the feature
<code type=val>persName</code> is itself a feature structure
(<code type=val>name-structure</code>).  This enables the component
parts of the
personal name to be identified.  Secondly, that this feature structure
points to the sasine segment where the nominal expressions referring
to Archibald occur. In this way, secondary analysts can have immediate
access to the information upon which such the analysis was made in the
first place. Thirdly, that the <gi>vAlt</gi> mechanism is used to
indicate the alternate readings of Archibald's names; that is, that he
was either a Marquis or an Earl but not both. For more information
about the use of feature structures, see chapter <ptr target=FS>.

<eg><![CDATA[

<text>

<s id=s1 anal=AEA1>
<lb><p>Item ane charter granted by Archibald late earl
<lb>of Argyle to Donald McNeill of Gallachalzie which
<lb>makes mention that the lands &illegible; and
<lb>Isles
<pagebreak header='Gallachalzie' n='141'>
<lb>underwritten were &illegible; by Hector McNeill
<lb> of Gallachalzie of the late Marquis of Argyle and

<text>

<fsLib>

<fs type=person>
 <f name=place-of-birth>

 <f name=date-of-birth>

 <f name=persName>
  <fs type=name-structure id=AEA1 instance=s1>
   <f name=forename<str>Archibald</str></f>
   <f name=rank>
   <f name=origin><str>Argyle</str></f>
    <vAlt>
     <sym value='earl'>
     <sym>value='marquis'>
     </vAlt>
    </f>
   </fs>
  </f>
 <f name=place-of-birth>

  </f>
 </fs>
<fs type=person>


 </fs>


</fsLib>

  ]]>
</eg>
-->

<!-- end of deleted section -->

<p>The elements discussed in this section are formally defined as
follows:

<eg id=dndper>
<![ CDATA [
<!-- 20.1:  Personal names                                    -->
<!ELEMENT persName      - -  (#PCDATA | %m.personPart; | 
                             %m.phrase; )*                      >
<!ATTLIST persName           %a.global;
                             %a.names;
          type               CDATA               #IMPLIED       >
<!ELEMENT surname       - -  (%phrase.seq;)                     >
<!ATTLIST surname            %a.global;
                             %a.personPart;                     >
<!ELEMENT forename      - -  (%phrase.seq;)                     >
<!ATTLIST forename           %a.global;
                             %a.personPart;                     >
<!ELEMENT genName       - -  (%phrase.seq;)                     >
<!ATTLIST genName            %a.global;
                             %a.personPart;                     >
<!ELEMENT nameLink      - -  (%phrase.seq;)                     >
<!ATTLIST nameLink           %a.global;
                             %a.personPart;                     >
<!ELEMENT addName       - -  (%phrase.seq;)                     >
<!ATTLIST addName            %a.global;
                             %a.personPart;                     >
<!ELEMENT roleName      - -  (%phrase.seq)                      >
<!ATTLIST roleName           %a.global;
                             %a.personPart;                     >
<!-- This fragment is used in sec. 20                         -->
]]>
</eg>


<!-- $Id: p2ndplac.odd,v 1.6 1998/02/01 17:56:37 tei Exp $ -->
<!--*
    * $Log: p2ndplac.odd,v $
    * Revision 1.6  1998/02/01 17:56:37  tei
    * fix log keyword
    *
    * Revision 1.5  98/02/01  17:45:38  tei
    * make examples parse somehow
    *
    * Revision 1.4  94/04/08  18:54:36  msmcq
    * Last-second fixes for P3
    *
    * Revision 1.3  1994/04/01  16:25:55  msmcq
    * Changes while validating DTDs
    * -->
<!-- Revisions:                                               -->
<!-- 94-04-07 : MSM : normalize caps in headings              -->
<!-- 94-03-31 : MSM : disambiguate TERM, Q                    -->
<!-- 94-03-28 : MSM : correct xref to ndplr(e)                -->
<!-- 94-03-28 : MSM : Added RCS id                            -->
<div2 id=NDplac><head>Place Names</head>

<p>Like other proper nouns or noun phrases used as names, place names
can simply be marked up with the <gi>rs</gi> element, or with the
<gi>name</gi> 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 importance evidence in historical
linguistics.  For such applications and others in which the internal
structure of a place name is to be encoded, the <gi>placeName></gi>
element and its subcomponents should be used.

<list type=gloss>
<label><gi>placeName</gi></label>
<item>contains an absolute or relative place name. </item>
<label><gi>settlement</gi></label>
<item>contains the name of the smallest component of a
place 
name expressed as a hierarchy of geo-political or

administrative units as in <q>Rochester</q>, New York;

<q>Glasgow</q>, Scotland.</item>
<label><gi>region</gi></label>
<item>in an address, contains the state, province, county or 
region
name; in a place name given as a hierarchy of 
geo-political
units, the <gi>region</gi> is larger or 
administratively
superior to the <gi>settlement</gi> and

smaller or administratively less important than the

<gi>country</gi>.</item>
<label><gi>country</gi></label>
<item>in an address, gives the name of the nation, country, 
colony, or
commonwealth; in a place name given as a 
hierarchy of geo-political
units, the <gi>country</gi> is 
larger or administratively superior
to the <gi>region</gi> 
and smaller than the <gi>bloc</gi>.</item>
<label><gi>bloc</gi></label>
<item>a geo-political unit containing one or more nation states.</item>
<label><gi>geogName</gi></label>
<item>a name associated with  some geographical feature such as
 
<q>Windrush Valley</q> or <q>Mount Sinai</q>.</item>
<label><gi>geog</gi></label>
<item>contains a common noun identifying some geographical 
feature
contained within a geographic name, such as 
<q>valley</q>,
<q>mount</q> etc.</item>
<label><gi>distance</gi></label>
<item>that part of a relative temporal or spatial expression 
which indicates
the distance between the place or time 
denoted by it and the place or
time referred to within it.</item>
<label><gi>offset</gi></label>
<item>that  part of a relative temporal or spatial expression

which indicates the direction of the offset between the two 
place
names, dates, or times involved in the expression.</item>
</list>


<p>As members of the <ident type=class>names</ident> class, all these
elements share the following attributes:

<list type=gloss>
<label><att>key</att></label>
<item>provides an alternative identifier for the object being 
named, such as a database record key.</item>
<label><att>reg</att></label>
<item>gives a normalized or regularized form of the name used.</item>
</list>

<p>Additionally, all of the above elements
are members of the class <ident type=class>placePart</ident>, and
thus share the following attributes:

<list type=gloss>
<label><att>type</att></label>
<item>provides more culture- linguistic- or application- specific 
information used to categorize this name component.</item>
<label><att>full</att></label>
<item>indicates whether the place name component is given in 
full, as an abbreviation or simply as an initial
Legal values are:
<list type=gloss>
<label><term>init</term></label>
<item>the name component is indicated only by one initial.</item>
<label><term>yes</term></label>
<item>the name component is spelled out in full.</item>
<label><term>abb</term></label>
<item>the name component is given in an abbreviated form.</item>
</list></item>
</list>

<!-- key and reg are inherited by pname from name -->

<p>Like the <gi>persName</gi> element discussed in section <ptr
target=NDper>, the <gi>placeName</gi> element may be regarded simply
as an abbreviation for the tags <tag>name type=place</tag> or <tag>rs
type=place</tag>. The following encodings are thus equivalent:
<note>Strictly, a suitable value such as <code>figurative</code> should be
added to the two place names which are presented periphrastically in
the second example here, in order to preserve the distinction
indicated by the choice of <gi>rs</gi> rather than <gi>name</gi> to
encode them in the first version.</note>

<eg><![CDATA[

After spending some time in our
<rs type=place key=NY1>modern
  <name type=place key=BA1>Babylon</name>
</rs>,
<name type=place key=NY1>New York</name>,
I have proceeded to the
<rs type=place key=PH1>City of Brotherly Love</rs>.

After spending some time in our
<placeName key=NY1>modern
  <placeName key=BA1>Babylon</placeName>
</placeName>,
<placeName key=NY1>New York</placeName>,
I have proceeded to the
<placeName key=PH1>City of Brotherly Love</placeName>.

]]>
</eg>
<!-- from letter from 'JK' found in Poulson's Daily Advertiser -->
<!-- 8 October, 1835, -->

<p>As indicated above, the <gi>placeName</gi> may simply contain a
character string and its <att>type</att> attribute may be used to
provide a sub-categorization of place names. Alternatively, it may
contain more detailed sub components. A place name may be analysed in
several different ways: as a geo-political unit, using a hierarchy of
descriptive names (see section <ptr target=NDplgu>); in terms of
geographic features such as mountains and rivers (see section <ptr
target=NDplgf>); relative to other place names (see section <ptr
target=NDplr>.


<div3 id=NDplgu><head>Geo-political Place Names

<p>A place name is sometimes given as sequence of
geo-political or administrative units, often arranged in
ascending sequence according to their size or administrative
importance, for example: <q>Rochester, New York</q>, or as a single
such unit, for example <q>Belgium</q>. The more detailed component
elements listed above (<gi>settle</gi> for a settlement, such as a
village, town or city; <gi>region</gi> for any administrative unit
such as a county, parish or state; <gi>country</gi> for a politically
recognized national entity; or <gi>bloc</gi> for any grouping of such
entities) have been chosen for their generality of application. They
may be tailored more closely to project- and
culture-specific needs by specifying appropriate values in their
respective <att>type</att> attributes, as in the following example:

<eg><![ CDATA[
<placeName key=RNY1>
  <settlement type=city>Rochester</settlement>,
  <region type=state>New York</region>
</placeName>

<placeName key=LSEA1>
  <country type=nation>Laos</country>,
  <bloc type=sub-continent>Southeast Asia</bloc>
</placeName>

]]>
</eg>

<!-- <p>When place names which are given in terms of a single -->
<!-- geo-political unit, the lower-level elements -->
<!-- (<gi>settlement</gi>, <gi>region</gi>, <gi>country</gi>, -->
<!-- <gi>bloc</gi>) may be used and the <gi>gu</gi> element -->
<!-- dispensed with as in: -->
<!-- Not without serious damage to your content model it cant!  -->

<p>Note that, even in the case where only one of these component place
name elements is used, the <gi>placeName</gi> element must still be
present.


<eg><![ CDATA[
I'd rather be in
<placeName>
<settlement key=RNY1 type=city>Rochester</settlement>
</placeName>
than any other place I know.
]]>
</eg>


<div3 id=NDplgf><head>Geographic Names

<p>Places may also be named in terms of geographic features such as
mountains, lakes or rivers, independently of geo-political units. The
<gi>geogName</gi> is provided to mark up such names, as an alternative
to the <gi>placeName</gi> element discussed above. It contains a
sequence of phrase level elements, optionally extended by the following
special element:
<list type=gloss>
<label><gi>geog</gi></label>
<item>contains a common noun identifying some geographical 
feature
contained within a geographic name, such as 
<q>valley</q>,
<q>mount</q> etc.</item>
</list>


<p>For example:

<eg>
<![CDATA[
  <geogName key=MIRI1 type=river>
    Mississippi River
  </geogName>

]]>
</eg>

<p>Where the <gi>geog</gi> element is used to characterize the kind of
geographic feature being named, the <gi>name</gi> element will generally
also be used to mark the associated proper noun or noun phrase:

<eg>
<![CDATA[
  <geogName key=MIRI1 type=river>
    <name>Mississippi</name>
    <geog>River</geog>
  </geogName>
]]>
</eg>

A more complex example, showing a variety of practices, follows:

<eg><![CDATA[
The isolated ridge separates two great corridors which run from
<name key=GLCO1 type=place>Glencoe</name> into
<geogName key=GLET1 type=glen>
  <geog reg='glen'>Glen</geog>
  <name>Etive</name>
</geogName>, the
<geogName key=LAGA1 type=hill>
  <geog lang='gaelic' reg='sloping hill face'>Lairig</geog>
  <name>Gartain</name>
</geogName> and the
<geogName key=LAEI1 type=hill>
  <geog lang='gaelic' reg='sloping hill face'>Lairig</geog>
  <name>Eilde</name>
</geogName>
]]>
</eg>


<div3 id=NDplr><head>Relative Place Names

<p>All the place name specifications so far discussed are
<term rend=noindex>absolute</term>, 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 <q>10 miles northeast of Paris</q> or <q>near the top
of Mount Sinai</q>. These <term>relative place names</term> will contain
a place name which acts as a referent (e.g. <q>Paris</q> and <q>Mount
Sinai</q>). They will also contain a word or phrase indicating the the
position of the place being named in relation to the referent
(e.g. <q>the top of</q>, <q>north of</q>). A distance, possibly only
vaguely specified, between the referent place and the place being
indicated may also be present (e.g. <q>10 miles</q>, <q>near</q>)

<p>Relative place names may be encoded using the following elements in
combination with either a <gi>placeName</gi> or a <gi>geogName</gi>
element.

<list type=gloss>
<label><gi>offset</gi></label>
<item>that  part of a relative temporal or spatial expression

which indicates the direction of the offset between the two 
place
names, dates, or times involved in the expression.</item>
<label><gi>distance</gi></label>
<item>that part of a relative temporal or spatial expression 
which indicates
the distance between the place or time 
denoted by it and the place or
time referred to within it.</item>
</list>



Some examples of relative place names are:

<eg>
<![CDATA[
<placeName key=NRPA1>
 <offset>near the top of
  </offset>
  <geogName>
     <geog>Mount</geog>
     <name>Sinai</name>
  </geogName>
</placeName>

<placeName key=NEPA1>
  <distance>10 miles</distance>
  <offset>north of</offset>
  <settlement type=city>Paris
  </settlement>
</placeName>

]]>
</eg>

<!--
  Where appropriate, the
internal structure of the distance component may be tagged using the
<gi>measure</gi> elements described in  section <ptr type='div2'
target=NDmeas>, as follows:

<eg>
<![ CDATA [
<relplace key=NRTA1>
  <distance type=measured>
    <measure type=length>
      <num type=cardinal value='2'>2</num>
      <unit>miles</unit>
    </measure>
  </distance>
  <offset reg='east'>
    east of
  </offset>
  <settlement type=city>
      Tel Aviv
  </settlement>
</relplace>
]]>
</eg>

<p>Some place names combine the distinctive place name
types discussed above, for example:

<eg>
<![ CDATA[
<relplace key=LIIT1>
  <distance type=measured>
     <measure type='length'>
       <num type='cardinal' value='2'>2</num>
       <unit type=area>blocks</unit>
     </measure>
   </distance>
   <offset reg='west'>west of</offset>
   <name>Little Italy</name>
</relplace>
]]>
</eg>

<p>Before concluding, it is worth considering a number of
substantive issues which need to be considered locally before
tagging a particular document. Firstly, the tags provided here
are sufficiently powerful to handle a wide variety of
geographical place names whose internal structure varies
considerably. The same flexibility, however, allows the encoder
to treat the same geographical place name differently. Thus,
the following variations on <q>The Mississippi River</q> are all
valid but might make local processing different or error prone
if all were implemented in the same document. The principal
problem is that the keys which associate the place names with some
particular place all refer to something slightly different:

<eg><![CDATA[

<rs key=pln15 type='place'>
  The Mississippi River
</rs>

<name key=pln15 type='place'>
  The Mississippi River
</name>

<rs key=pln15 type='place'>
The
  <name>Mississippi
  </name>
  <geog>River</geog>
</rs>

]]>
</eg>

Suffice it to say here as elsewhere in this volume, the encoder is urged
to
be as consistent as possible in applying encoding solutions to a
given machine-readable text or project.
-->

<p>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
will be adequate for a majority of users and applications. They may
not, however, satisfy the most specialized inquiries and/or
applications in which case it is recommended that the internal
structure of place names be represented using feature structures
<ptr target=FS>.

<p>The elements discussed in this section are formally defined as
follows:

<eg id=dndplac>
<![ CDATA [
<!-- 20.2.3:  Names for places                                -->
<!ELEMENT placeName     - -  ((#PCDATA | %m.placePart; | 
                             %m.phrase; )*)                     >
<!ATTLIST placeName          %a.global;
                             %a.names;                          >
<!ELEMENT settlement    - -  (%phrase.seq;)                     >
<!ATTLIST settlement         %a.global;
                             %a.placePart;                      >
<!ELEMENT region        - -  (%paraContent)                     >
<!ATTLIST region             %a.global;
                             %a.placePart;                      >
<!ELEMENT country       - o  (%paraContent)                     >
<!ATTLIST country            %a.global;
                             %a.placePart;                      >
<!ELEMENT bloc          - -  (%phrase.seq)                      >
<!ATTLIST bloc               %a.global;
                             %a.placePart;                      >
<!ELEMENT offset        - -  (#PCDATA)                          >
<!ATTLIST offset             %a.global;
          value              CDATA               #IMPLIED
                             %a.placePart;                      >
<!ELEMENT distance      - -  (%phrase.seq)                      >
<!ATTLIST distance           %a.global;
          key                CDATA               #IMPLIED
          value              CDATA               #IMPLIED
          type               CDATA               #IMPLIED
          full               (yes | abb | init)  yes
          reg                CDATA               #IMPLIED
          exact              (Y | N | U)         U              >
<!ELEMENT geogName      - -  (#PCDATA | geog | name )*          >
<!ATTLIST geogName           %a.global;
                             %a.names;
          type               CDATA               #IMPLIED       >
<!ELEMENT geog          - -  (#PCDATA)                          >
<!ATTLIST geog               %a.global;
                             %a.placePart;                      >
<!-- This fragment is used in sec. 20                         -->
]]>
</eg>


<!--* $Id: p2ndorg.odd,v 1.3 1998/02/01 17:45:38 tei Exp $ *-->
<!--*
    **
    * $Log: p2ndorg.odd,v $
    * Revision 1.3  1998/02/01 17:45:38  tei
    * make examples parse somehow
    *
    * Revision 1.2  98/01/28  12:01:27  lou
    * LB changes of Jan 1998 and RCS keywords
    *
    *-->
<!-- 5 Jan 95 : LB : corrected typos in egs -->
<div2 id=NDorg><head>Organization names</head>

<p>Like names of persons or places, organization names can be marked as
referent strings or as proper names with the <gi>rs</gi> and
<gi>name</gi> elements.  For certain applications it may be desirable
to mark the component parts of an organization. In some historical and
social scientific studies, for example, the component parts of an
organization names may give crucial clues which help to  characterizing
the organization in terms of its geographical location, ownership,
likely number of employees, management structure etc.  The elements
discussed in this section are recommended for this purpose and include:

<list type=gloss>
<label><gi>orgName</gi></label>
<item>contains an organizational name. 
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>more fully describes the organization indicated in the 
organizational name. Possible values include 
<q>voluntary</q>, <q>political</q>, <q>governmental</q>, 
<q>industrial</q>, <q>commercial</q>, etc.</item>
<label><att>key</att></label>
<item>provides an alternative identifier for the organization 
being named, such as a database record key.</item>
<label><att>reg</att></label>
<item>gives a normalized or regularized form of the organization 
name</item>
</list>
</item>
<label><gi>orgTitle</gi></label>
<item>contains the proper name component of an organizational

name. 
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>more fully describes the organization title. Possible 
values include <q>formal</q>, <q>colloquial</q>, 
<q>acronym</q>, etc.</item>
<label><att>reg</att></label>
<item>gives a normalized or regularized form of the organization 
title.</item>
</list>
</item>
<label><gi>orgType</gi></label>
<item>indicates a part of the organization name which contains

information about the organization's structure or function.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>more fully describes the organization type specified in the 
name component. Possible values include <q>function</q>, 
<q>structure</q>, etc.</item>
<label><att>reg</att></label>
<item>gives a normalized or regularized form of the organization 
type</item>
</list>
</item>
<label><gi>orgDivn</gi></label>
<item>indicates a division, branch or department specified
in an 
organizational name.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>more fully describes the organization division specified in 
the name component. Possible values include <q>branch</q>, 
<q>department</q>, <q>section</q>, <q>division</q>, etc.</item>
<label><att>reg</att></label>
<item>gives a normalized or regularized form of the 
organizational division.</item>
</list>
</item>
</list>


<p>The <gi>orgname</gi> element should be used when it is desirable to
mark an organization name irrespective of whether or not its components
are also to be marked. In effect the <gi>orgname</gi> element is a
special case of a <gi>name</gi> and thus of an <gi>rs</gi> element.
Consequently, the following examples are synonymous, though the last is
preferred:

<eg>
<![ CDATA [
About a year back, a question of considerable interest was
agitated in the <rs type=org key=PAS1>Pennsyla. Abolition Society</rs>.

About a year back, a question of considerable interest was
agitated in the <rs type=org key=PAS1><name>Pennsyla. Abolition
Society</name</rs>.

About a year back, a question of considerable interest was
agitated in the <name type=org key=PAS1>Pennsyla. Abolition Society</name>.

About a year back, a question of considerable interest was
agitated in the <orgname key=PAS1 type=voluntary
reg="Pennsylvania Abolition Society">Pennsyla. Abolition Society</orgname>.
]]>
</eg><!-- From the Diary of Thomas Pym Cope -->

Like the <gi>rs</gi> and <gi>name</gi> elements, the <gi>orgname</gi>
element has a <att>key</att> attribute with which an external
identifier such as a database key can be assigned to the organization
name. It also has a <att>type</att> attribute with which the
organization named in the expression can be described, and a
<att>reg</att> attribute with which the organization name can be
presented in a regularized form.

<p>The <gi>orgtitle</gi> element is used to mark the expression
which provides the proper name component of an organization name
for example:

<eg><![CDATA[

Mr Frost will be able to earn an extra fee from
<orgname type=media key=BSB1>
  <orgtitle type=acronym>BSkyB</orgtitle>
</orgname>
rather than the
<orgname type=media key=BBC1>
   <orgtitle type=acronym
             reg='British Broadcasting Corporation'>
   BBC</orgtitle>
</orgname>

]]></eg>

<p>Where personal names are encountered as component parts of an
organization's title, as in <q>Ernst & Young</q>, these may be
tagged with the appropriate personal name elements as discussed
in <ptr type=div2 target=NDPer>. Examples include:


<eg><![ CDATA[
<orgname type='accountancy partnership' key=EY1>
<orgtitle>
  <persname><surname>Ernst</surname></persname> &
  <persname><surname>Young</surname></persname>
</orgtitle>
</orgname>
]]></eg>

<p>Organization names may also contain within them place names
which, in some applications, may yield vital clues as to the
organization's location and or sphere of influence. These
components should be tagged with the approprate place name tags
<ptr type=div2 target=NDplac>. Examples include:

<eg><![ CDATA[
A spokesman from
<orgname type=computers key=IBM1>
  <orgtitle reg='International Business Machines'>IBM</orgtitle>
  <placeName><country reg='United Kingdom' key=UNKI1>UK
  </country></placeName>
</orgname> said...

The feeling in
<country type=nation key=CAN1>Canada</country>
is one of strong aversion to the
<orgname type=government key=USG1>
  United States  Government
</orgname>, and of predilection for self-government
under the
<orgname type=government
      reg='British monarchy'>English Crown</orgname>

]]></eg><!-- Anthony Trollope, North America, Penguin ed., 51 -->


<p>The <gi>orgtype</gi> element is used to mark those components
of an organization name which indicate something about the
structure or function of the organization. Examples include:

<eg><![ CDATA[
<orgname type='utility company' key=WWPC1>
  <name type=state>Washington</name>
  <orgtype type=function>Water Power</orgtype>
  <orgtype reg='incorporated' type=structure>Inc.</orgtype>
</orgname>

THE TICKET which you will receive herewith has been formed by
the
<orgname type=political reg='Whig party' key=WHI1>
  <orgtitle>Democratic Whig</orgtitle>
  <orgtype type=function>Party</orgtype>
</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
<emph>Welfare and Best Interests of the Community</emph>.

]]></eg>


<p>Organizational names may also be specified hierarchically
particularly where the named organization is itself a department
or a branch of a larger organizational entity.  <q>The
Department of Modern History, Glasgow University</q> is an
example. The <gi>orgdivn</gi> element is recommended wherever
it is desirable to isolate the independent levels of an
organizational hierarchy that are specified in an organization name.
Examples include:

<eg><![ CDATA[
<orgname type=academic key=DMHGU1>
  <orgdivn type=department>
     Department of Modern History
  </orgdivn>,
  <name type=city>Glasgow</name>
  <orgtype type=function>University</orgtype>
</orgname>

]]></eg>

<p>Although highly flexible, the mechanisms discussed here for
marking the components of organization names will not cater for
every processing need or organizational name that is
encountered. Where the internal structure of organization names
is highly complex, where name components are particularly
ambiguous, or where it is important to indicate the assumptions
made in the evaluation of an organization name, then feature
structure notation is recommended <ptr target=FS>

<p>The formal declaration of the elements discussed in this section include:

<eg id=dndorg>
<![ CDATA [
<!-- 20.3:  Organization names                                -->
<!ELEMENT orgName       - -  (orgTitle | orgType | orgDivn | 
                             %m.phrase | #pcdata)*              >
<!ATTLIST orgName            %a.global;
          reg                CDATA               #IMPLIED
          key                CDATA               #IMPLIED
          type               CDATA               #IMPLIED       >
<!ELEMENT orgTitle      - -  (%phrase.seq)                      >
<!ATTLIST orgTitle           %a.global;
          reg                CDATA               #IMPLIED
          type               CDATA               #IMPLIED       >
<!ELEMENT orgType       - -  (%phrase.seq)                      >
<!ATTLIST orgType            %a.global;
          reg                CDATA               #IMPLIED
          type               CDATA               #IMPLIED       >
<!ELEMENT orgDivn       - -  (%phrase.seq)                      >
<!ATTLIST orgDivn            %a.global;
          reg                CDATA               #IMPLIED
          type               CDATA               #IMPLIED       >
<!-- This fragment is used in sec. 20                         -->
]]>
</eg>


<!--* $Id: p2nddate.odd,v 1.4 1998/01/28 12:01:27 lou Exp $ *-->
<!--*
    * $Log: p2nddate.odd,v $
# Revision 1.4  1998/01/28  12:01:27  lou
# LB changes of Jan 1998 and RCS keywords
#
    *-->
<!-- $Id: p2nddate.odd,v 1.4 1998/01/28 12:01:27 lou Exp $ -->
<!-- $Log: p2nddate.odd,v $
# Revision 1.4  1998/01/28  12:01:27  lou
# LB changes of Jan 1998 and RCS keywords
#
# Revision 1.3  1994/04/08  18:54:36  msmcq
# Last-second fixes for P3
# -->
<!-- Revisions:                                               -->
<!-- 5 jan 98 : LB : fix typos in egs -->
<!-- 94-04-07 : MSM : normalize caps in headings              -->
<!-- 94-04-07 : MSM : Added RCS id                            -->
<!-- 94-03-31 : MSM : disambiguate TERM, Q                    -->
<!-- 94-03-31 : MSM : cosmetics                               -->
<!-- 6 Mar 94 : LB extensive revision: introduce              -->
<!--            dateStruct, timeStruct                        -->
<!-- 93-06-03 : MSM : rename event as relEvent as per DGr     -->
<!-- Lou, in order for this section to make sense, you need   -->
<!-- to introduce the <gi>time</gi> and <gi>timerange</gi>    -->
<!-- elements in the core where you currently discuss         -->
<!-- dates.  the tags are identical to <gi>date</gi> and      -->
<!-- <gi>daterange</gi> but for clock time as opposed to      -->
<!-- calendar dates.                                          -->


<div2 id=NDdate><head>Dates and Time</head>

<p>The following elements for the encoding of dates and times were
introduced in section <ptr target=COnada>:

<list type=gloss>
<label><gi>date</gi></label>
<item>contains a date in any format.
Attributes include:
<list type=gloss>
<label><att>calendar</att></label>
<item>indicates the system or calendar to which the date belongs.</item>
<label><att>value</att></label>
<item>gives the value of the date in some standard form, usually 
yyyy-mm-dd.</item>
<label><att>certainty</att></label>
<item>indicates the degree of precision to be attributed to the 
date.</item>
</list>
</item>
<label><gi>time</gi></label>
<item>contains a phrase defining a time of day in any format.
Attributes include:
<list type=gloss>
<label><att>zone</att></label>
<item>indicates time zone or place name wherever this is 
necessary to evaluate a temporal expression.</item>
<label><att>value</att></label>
<item>gives the value of the time in a standard form.</item>
<label><att>type</att></label>
<item>indicates something about the type of temporal expression 
being tagged.
Legal values are:
<list type=gloss>
<label><term>descriptive</term></label>
<item>indicates a temporal expression made in descriptive terms, 
e.g. <q>noon</q>.</item>
<label><term>am</term></label>
<item>indicates a temporal expression made on the basis of a 
twelve-hour clock and referring to a time between midnight 
and noon.</item>
<label><term>24hour</term></label>
<item>indicates a temporal expression made on the basis of a 
twenty-four-hour clock.</item>
<label><term>pm</term></label>
<item>indicates a temporal expression made on the basis of a 
twelve-hour clock and referring to a time between noon and 
midnight.</item>
</list></item>
</list>
</item>
</list>


<p>While adequate for many applications, these elements do not allow
for the representation of the internal structure of expressions
indicating dates or times, which may however be of importance for the
correct interpretation of such expressions, or for certain kinds of
analytic applications. In this section, we introduce the following
special-purpose elements, for use when the internal structure of a
temporal expression is to be encoded:

<list type=gloss>
<label><gi>dateStruct</gi></label>
<item>contains an internally structured representation of a date.</item>
<label><gi>timeStruct</gi></label>
<item>contains an internally structured representation for a time 
of day.</item>
</list>


<p>Two types of temporal expressions are envisaged for dates and
times: absolute and relative. An <term>absolute temporal
expression</term> is composed of a sequence of the following elements,
possibly interspersed with character data:

<list type=gloss>
<label><gi>day</gi></label>
<item>the day component of a structured date.</item>
<label><gi>week</gi></label>
<item>the week component of a structured date.</item>
<label><gi>month</gi></label>
<item>the month component of a structured date.</item>
<label><gi>year</gi></label>
<item>the year component of a date.</item>
<label><gi>second</gi></label>
<item>the second component of a structured time-expression.</item>
<label><gi>minute</gi></label>
<item>the minute component of a structured time-expression.</item>
<label><gi>hour</gi></label>
<item>the hour component of a temporal expression such as</item>
<label><gi>occasion</gi></label>
<item>a temporal expression (either a date or a time)
given in 
terms of a named occasion such as a holiday,
a named time 
of day, or some notable event.</item>
</list>


<p>A <term>relative temporal expression</term> describes a date or time
with reference to some other (absolute) temporal expression, and thus
contains the following elements in addition to those listed above:

<list type=gloss>
<label><gi>distance</gi></label>
<item>that part of a relative temporal or spatial expression 
which indicates
the distance between the place or time 
denoted by it and the place or
time referred to within it.</item>
<label><gi>offset</gi></label>
<item>that  part of a relative temporal or spatial expression

which indicates the direction of the offset between the two 
place
names, dates, or times involved in the expression.</item>
</list>


<p>As members of the class <ident type=class>temporalExpr</ident>
(temporal expression)
these elements all share the following attributes:

<list type=gloss>
<label><att>value</att></label>
<item>supplies the value of a date or time in a standard form.</item>
<label><att>type</att></label>
<item>provides any application-, linguistic- or culture-specific 
classication for the component.</item>
<label><att>reg</att></label>
<item>gives a normalized or regularized form of the temporal 
expression.</item>
</list>


<div3 id=NDdatea><head>Absolute Dates and Times

<p>An absolute temporal expression which is a date will contain only a
sequence of <gi>day</gi>, <gi>month</gi> <gi>week</gi>, <gi>year</gi>
or <gi>occasion</gi> elements, as in the following examples:

<eg><![ CDATA [
The university's view of American affairs produced
a stinging attack by Edmund Burke in the Commons
debate of
<dateStruct value='26-10-1775'>
  <day value='26'>26</day>
  <month value='10'>October</month>
  <year value='1775'>1775</year>
</dateStruct>
]]>
</eg><!-- The History of the University of Oxford, vol v, 178 -->

Component elements of a <gi>dateStruct</gi> may be repeated, provided
that only a single  temporal expression is intended:

<eg><![ CDATA [
<dateStruct value='14-05-1993'>
  <day type=name>Friday</day>,
  <day type=number>14</day>
  <month>May</month>
  <year>1993</year>
</dateStruct>
]]>
</eg><!-- the headline on the Independent Newspaper on that day -->

<p>The <gi>occasion</gi> element may be used for any component of a
temporal expression which is given in terms of a named event, such as
a public holiday for dates, or a named time such as <q>tea time</q> or
<q>matins</q>:

<eg>
<![ CDATA [
In New York,
  <dateStruct value='1-1'>
    <occasion type=holiday>New Years Day</occasion>
  </dateStruct> is the quietest of holidays,
  <dateStruct value='4 July'>
    <occasion type=holiday>Independence Day</occasion>
  </dateStruct>
the most turbulent.
]]>
</eg>

<p>These components may be applied to dates using any calendar system
using  subcomponents equivalent to those listed above:
<eg>
<![ CDATA [
<title>Le Vieux Cordelier:
Journal r&eacute;dig&eacute; par Camille Desmoulins</title>,
<dateStruct type=Revolutionary value='03-02-1794'>
   <day type=name>Quintidi</day>
   <month>Pluviose</month>
   <week value=2>2e d&eacute;cade</week>,
   <year value=2>l'an 2 de la R&eacute;publique Indivisible</year>
</dateStruct>
]]>
</eg>
<!-- NB put acutes in same example in week.tag -->
<!-- Date headline from Le Vieux Cordelier of that date -->
<!-- Thanks to T. Munck for providing the above example -->

<p>Absolute temporal expressions denoting times which are given
in terms of seconds, minutes, hours or of well defined events
(e.g. <q>noon</q>, <q>sunset</q>) may similarly be represented using
the <gi>timeStruct</gi> element:

<eg>
<![ CDATA [
The train leaves for Boston at
  <timeStruct type='24hour' zone=EST>
    <hour>13</hour>:<minute>45</minute>
   </timeStruct>

At <timeStruct>
     <occasion>sunset</occasion>
   </timeStruct> we walked to the beach.

The train leaves for Boston at
  <timeStruct type='descriptive' zone=EST value='13:45'>
     a quarter of <hour reg='1400'>two</hour>
  </timeStruct>
]]>
</eg><!-- maybe should add lang=AmE to last?! -->

<p>The <att>type</att> attribute may be used to distinguish sub-types of
component elements (for example, months or days presented as words or
as numbers) or to provide additional information about the function of
this particular component (for example, to distinguish types of
<gi>occasion</gi>).
The <att>value</att> and <att>reg</att> attributes
are both used to provide a standardized or regularized form of the
content of an element. The distinction is that the value specified by
the <att>reg</att> attribute is simply that chosen as a convenient way
of grouping together a number of variant forms, whereas that specified
for the <att>value</att> attribute must always be given in some
application-dependent standard form, described in the <gi>stdVals</gi>
element of the TEI header.

<p>For example:

<eg><![CDATA[
<dateStruct value='09-06-1807'>
  <month type=name value=06>June</month>
  <day type=number value=09>9th</day>
</dateStruct>:
The period is approaching which will terminate my
present copartnership. On the
<dateStruct value='01-01-1808'>
  <day type=number value=01>1st</day>
  <month type=name value=01 reg='January'>Jany.</month>
</dateStruct> next, it expires by its own limitation.
]]>
</eg><!-- Philadelphia Merchant: The Diary of TP Cope, 210 -->


<div3 id=NDdater><head>Relative Dates and Times

<p>As noted above, relative dates and times such as <q>in the Two
Hundredth and First Year of the Republic</q>, <q>twenty minutes before
noon</q>, and, more ambiguously, <q>after the lamented death of the
Doctor</q> or <q>an hour after the game</q> have two distinct
components. As well as the absolute temporal expression or event to
which reference is made (e.g. <q>noon</q>, <q>the game</q>, <q>the
death of the Doctor</q> <q>[the foundation of] the Republic</q>), they
also contain a description of the <soCalled>distance</soCalled>
between the time or date which is indicated and the referent
expression (e.g. <q>the Two Hundredth and First Year</q>, <q>twenty
minutes</q>, <q>an hour</q>); and (optionally) an
<soCalled>offset</soCalled> describing the direction of the distance
between the time or date indicated and the referent expression
(e.g. <q>of</q> implying after, <q>before</q>, <q>after</q>).

<p>The elements <gi>distance</gi> (or <gi>measure</gi>) and
<gi>offset</gi> are used to encode these last two components within a
<gi>dateStruct</gi> or <gi>timeStruct</gi>. The absolute temporal
expression contained within the relative expression may be encoded
using a <gi>occasion</gi> element, or by a nested <gi>dateStruct</gi>
or <gi>timeStruct</gi>, or by a simple <gi>date</gi> or
<gi>time</gi>. This allows for endlessly recursive structures such as
<q>the third Sunday after the first Monday before Lammastide in the
fifth year of the King's second marriage ...</q> --- but so does
natural language.

In the following examples, the <att>reg</att> attribute has been used
to simplify processing of variant forms of expression:

<eg><![CDATA[
<dateStruct value='11-12-1786'>
     <distance reg='14 days'>A fortnight</distance
     <offset>before</offset>
     <dateStruct>
       <occasion type='holiday'>Christmas</occasion>
       <year>1786</year>
     </dateStruct>
</dateStruct>

I reached the station
<timeStruct value='14:15'>
 <distance exact=N reg='30 minutes'>
   about a half hour</distance>
 <offset>after</offset>
 <occasion value='13:45'>
   the departure of the afternoon train to Boston</occasion>
</timeStruct>
]]>
</eg>

<p>In the following example, the <att>exact</att> attribute has been
used to indicate a lack of precision in the distance stated:

<eg><![CDATA[
In practice, festival candles are lit
<timeStruct>
  <distance exact=N>just</distance>
  <offset>before</offset>
  <occasion reg='evening'>sundown</occasion>
</timeStruct>

]]>
</eg>


<p>In the following example, a nested <gi>dateStruct</gi> element is
used to show that <q>my birthday</q> and the cited date are parts of
the same temporal expression, and hence to disambiguate the phrase
<q>A week before my birthday on 9th December</q>:

<eg>
<![ CDATA [
<dateStruct value='02-12'>
  <distance>A week</distance>
  <offset>before</offset>
  <dateStruct value='09-12'>
    <occasion>my birthday</occasion>
    on <day>9th</day><month>December</month>
  </dateStruct>
</dateStruct>
]]>
</eg>

The alternative reading of this phrase would be encoded as follows:
<eg>
<![ CDATA [
<dateStruct value='09-12'>
  <distance>A week</distance>
  <offset>before</offset>
  <occasion>my birthday</occasion>
  on <day>9th</day><month>December</month>
</dateStruct>
]]>
</eg>

<!-- really dont want to keep distance : shd be same as measure -->

<p>Where more complex or ambiguous expressions are involved, and
where it is desirable to make more explicit  the interpretive
processes required, the feature
structure notation described in chapter  <ptr target=FS> is
recommended.  Consider, for example, the following
temporal expression which occurs in the <title>Scottish Temperance
Review</title> of August 1850, referring  to the summer  holiday known
in Glasgow simply as <q>the Fair</q>:

<eg><![CDATA[
Not only is the city, <date ana=GF50>during the Fair</date>, a
horrible nucleus of immorality and wickedness; it sends our
multitudes to pollute and demoralize the country.
]]>
</eg>

<p>For the definition of the <att>ana</att> attribute, see chapter
<ptr target=AI>. It is used here to link the temporal phrase with an
interpretation of it. Like most traditional fairs and market days, the
Glasgow Fair was established by local custom and could vary from year
to year.  Consequently, in order to provide such an interpretation, it
is necessary to drawn upon additional information which may or may not
be located in the particular text in question. In this case, it is
necessary at least to know the spatial and temporal context (year and
place) of the fair referred to.
These and other features required for
the analysis of this particular temporal
expression may be combined together as one feature
structure of type <code>date-analysis</code>:

<eg>
<![ CDATA [
<fs type=date-analysis id=GF50>
<f name=event><str>the Fair</str></f>
<f name=place><str>Glasgow</str></f>
<f name=year><nbr value=1850></f>
<f name=from-value><str>08-08-1850</str></f>
<f name=to-value><str>19-09-1850</str></f>
</fs>
]]></eg>


The elements described in this section are formally defined as follows:

<eg id=dnddate>
<![ CDATA [
<!-- 20.4.2:  Date components                                 -->
<!ELEMENT dateStruct    - -  (#PCDATA | %m.temporalExpr;)*      >
<!ATTLIST dateStruct         %a.global;
                             %a.temporalExpr;
          exact              CDATA               #IMPLIED
          calendar           CDATA               #IMPLIED       >
<!ELEMENT day           - -  (#PCDATA)                          >
<!ATTLIST day                %a.global;
                             %a.temporalExpr;                   >
<!ELEMENT week          - -  (#PCDATA)                          >
<!ATTLIST week               %a.global;
                             %a.temporalExpr;                   >
<!ELEMENT month         - -  (#PCDATA)                          >
<!ATTLIST month              %a.global;
                             %a.temporalExpr;                   >
<!ELEMENT year          - -  (#PCDATA)                          >
<!ATTLIST year               %a.global;
                             %a.temporalExpr;                   >
<!ELEMENT occasion      - -  (%phrase.seq)                      >
<!ATTLIST occasion           %a.global;
                             %a.temporalExpr;                   >
<!ELEMENT timeStruct    - -  ((#PCDATA | %m.temporalExpr;)*)    >
<!ATTLIST timeStruct         %a.global;
                             %a.temporalExpr;
          zone               CDATA               #IMPLIED       >
<!ELEMENT second        - -  (#PCDATA)                          >
<!ATTLIST second             %a.global;
                             %a.temporalExpr;                   >
<!ELEMENT minute        - -  (#PCDATA)                          >
<!ATTLIST minute             %a.global;
                             %a.temporalExpr;                   >
<!ELEMENT hour          - -  (#PCDATA)                          >
<!ATTLIST hour               %a.global;
                             %a.temporalExpr;                   >
<!-- offset and distance were defined above                   -->

<!-- This fragment is used in sec. 20                         -->
]]>
</eg>



</div1>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/fullodd.ced"
sgml-parent-document:("/home/tei/P3/Master/Odds/p2.odd" "TEI.1" "TEXT" "BODY" "DIV1")
sgml-omittag:t
sgml-shorttag:t
End:
-->

             <!-- 20 Names and Dates ... -->
