<?tei:SOF p2ndorg.odd ?>
<!--* $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:
 
<tagList>
<tagDesc tagDoc=ORGNAME atts='type key reg'>
<tagDesc tagDoc=ORGTITLE atts='type reg'>
<tagDesc tagDoc=ORGTYPE atts='type reg'>
<tagDesc tagDoc=ORGDIVN atts='type reg'>
</tagList>
 
<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 <xref 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
<xref 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 <xref target=FS>
 
<p>The formal declaration of the elements discussed in this section include:
 
<dtdFrag id=DNDORG n='Organization names' file=teind2>
<tagDecl tagDoc=ORGNAME>
<tagDecl tagDoc=ORGTITLE>
<tagDecl tagDoc=ORGTYPE>
<tagDecl tagDoc=ORGDIVN>
</dtdFrag>
<?tei:EOF p2ndorg.odd ?>
