<?tei:SOF p2ndplac.odd ?>
<!-- $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.
 
<tagList>
<tagDesc tagDoc=PLACNAME >
<tagDesc tagDoc=SETTLE >
<tagDesc tagDoc=REGION >
<tagDesc tagDoc=COUNTRY>
<tagDesc tagDoc=BLOC >
<tagDesc tagDoc=GEOGNAME>
<tagDesc tagDoc=GEOG >
<tagDesc tagDoc=DISTANCE >
<tagDesc tagDoc=OFFSET >
</tagList>
 
<p>As members of the <ident type=class>names</ident> class, all these
elements share the following attributes:
 
<adList classDoc=NAMES atts='key reg'>
 
<p>Additionally, all of the above elements
are members of the class <ident type=class>placePart</ident>, and
thus share the following attributes:
 
<adList classDoc=PLACPART atts='type full'>
 
<!-- key and reg are inherited by pname from name -->
 
<p>Like the <gi>persName</gi> element discussed in section <xref
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 <xref target=NDPLGU>); in terms of
geographic features such as mountains and rivers (see section <xref
target=NDPLGF>); relative to other place names (see section <xref
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:
<tagList>
<tagDesc tagDoc=GEOG>
</tagList>
 
<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.
 
<tagList>
<tagDesc tagDoc=OFFSET >
<tagDesc tagDoc=DISTANCE>
</tagList>
 
 
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 <xref 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
<xref target=FS>.
 
<p>The elements discussed in this section are formally defined as
follows:
 
<dtdFrag id=DNDPLAC n='Names for places' file=teind2>
<tagDecl tagDoc=PLACNAME>
<tagDecl tagDoc=SETTLE>
<tagDecl tagDoc=REGION>
<tagDecl tagDoc=COUNTRY>
<tagDecl tagDoc=BLOC>
<tagDecl tagDoc=OFFSET>
<tagDecl tagDoc=DISTANCE>
<tagDecl tagDoc=GEOGNAME>
<tagDecl tagDoc=GEOG>
</dtdFrag>
<?tei:EOF p2ndplac.odd ?>
