<?tei:SOF p2hd3.odd ?>
<!-- $Id: p2hd3.odd,v 1.7 1994/04/01 16:23:58 msmcq Exp $ -->
<!-- $Log: p2hd3.odd,v $
# Revision 1.7  1994/04/01  16:23:58  msmcq
# Misc. changes/fixes while validating DTDs
#
# Revision 1.6  1994/03/24  22:14:56  msmcq
# typo corrections from David Barnard, Peter Robinson, and others
#
# Revision 1.5  1994/01/04  13:02:03  lou
# fix examples
#
# Revision 1.3  1993/08/18  21:31:24  msmcq
# name shift (role/resp, resp/respStmt) on account of DR role
#
# Revision 1.2  1993/06/22  14:29:49  msmcq
# Changes post Eynsham and for DTD generation
# -->
<!-- Revisions:                                               -->
<!-- 94-03-29 : MSM : explicitly embed d2231                  -->
<!-- 94-03-29 : MSM : suppress supererogatory file att on dtdfrags -->
<!-- 94-03-24 : CMSMcQ : one more typo                        -->
<!-- 94-03-22 : CMSMcQ : typos, TEI - &tei, code, ident tags  -->
<!--                     notes from DB                        -->
<!-- 93-08-18 : MSM : new names for respStmt, role/resp       -->
<!-- 93-06-02 : MSM : rename listbibl from bibllist           -->
<!-- 93-06-01 : MSM : normalize citn, teihead, xrefs to ah    -->
<!-- 93-02-10 : MSM : update xref targets                     -->
<!-- 92-08-18 : MSM : some points of style and detail         -->
<!-- 92-08-14 : MSM : revisions, restore recording stmt       -->
<!-- 1 aug 92: LB: some juggling with ids and ordering        -->
<!--     also, gritted teeth and moved recording and script stmts -->
<!--     to aux header. You can explain to Stig!              -->
<!-- 26 Jul 92 : MSM : very light revision, almost nothing    -->
<!--                   except in 22.3.2 (reordering)          -->
<!-- 25 Jul 92 : MSM : names updated, ids updated             -->
 
<div3 id='HD3'><head>The Source Description</head>
 
<!-- was div2: demoted for consistency with structure of dtd (LB) -->
<!--   (maybe its id should change too ; left as is for now )     -->
 
<p>The <gi>sourceDesc</gi> element is the seventh and final component of
the <gi>fileDesc</gi> element.  It is a mandatory element, and is used to
record details of the source or sources from which a computer file is
derived.  This might be a printed text or manuscript, another computer
file, an audio or video recording of some kind, or a combination of
these.  An electronic file may also have no source, if what is being
catalogued is an original text created in electronic form.
<tagList>
<tagDesc tagDoc='SOUSTMT'>
</tagList>
 
<p>The <gi>sourceDesc</gi> element may contain a simple prose
description, or, more usefully, a bibliographic citation of some kind
specifying the provenance of the text.  For written or printed sources,
the source should be described in the same way as any other
bibliographic citation, using one of the following elements:
 
<tagList>
<tagDesc tagDoc="BIBL">
<tagDesc tagDoc="BIBLSTRU">
<tagDesc tagDoc="BIBLFULL">
<tagDesc tagDoc="LISTBIBL">
</tagList>
 
These elements are described in more detail in section
<xref target=COBI>.
<!-- or:  target=COBIBL>. -->
<p>
When the header describes a transcription of spoken material, the
<gi>sourceDesc</gi> element may also include the following
special-purpose elements, intended for cases where an electronic text
is derived from a spoken text rather than a written one:
<tagList>
<tagDesc tagDoc=SCRSTMT>
<tagDesc tagDoc=RECSTMT>
</tagList>
Full descriptions of these elements and their contents are given in
section <xref target=HD32>.
<p>
The <gi>sourceDesc</gi> element may contain a mixture of one or more
of the above elements, as in the following examples:
 
<eg><![ CDATA[
<sourceDesc>
   <bibl>The first folio of Shakespeare, prepared by
   Charlton Hinman (The Norton Facsimile, 1968)</bibl>
</sourceDesc>
]]>
</eg>
<eg><![ CDATA[
<sourceDesc>
   <p>No source: created in machine-readable form.</p>
</sourceDesc>
]]>
</eg>
<eg><![ CDATA[
<sourceDesc>
   <biblStruct lang=FR>
   <monogr>
    <author>Eug&egrave;ne Sue</>
    <title>Martin, l'enfant trouv&eacute;</>
    <title type=sub>M&eacute;moires d'un valet de chambre</>
    <imprint>
         <pubPlace>Bruxelles et Leipzig</>
         <publisher>C. Muquardt</>
         <date>1846</>
    </imprint>
   </monogr></biblStruct>
</sourceDesc>
]]>
</eg>
 
<p>The source description itself has the following formal definition:
<dtdFrag id=D223 n='The source description'>
<tagDecl tagDoc=SOUSTMT>
<dtdRef dtdFrag=D2231>
</dtdFrag>
 
<div3 id='HD31'><head>Computer Files Derived from Other Computer Files
 
<p>If a machine-readable text (call it B) is based not on a
printed source but upon another machine-readable text (call it
A) which includes a &tei; file header, then the source text of
computer file B is another computer file, A.  The four sections
of A's file header will need to be incorporated into the new
header for B in slightly differing ways, as listed below:
 
<list type=gloss>
 
<label>fileDesc
<item>A's file description should be copied into the
<gi>sourceDesc</gi> section of B's file description, enclosed
within a <gi>biblFull</gi> element
(see section <xref target=COBI>).
<!-- was:  target='P2.235'>). -->
<!-- was:  target='COBIBL'>). -->
 
<label>profileDesc<item>A's <gi>profileDesc</gi> should be
copied into B's, in principle unchanged.
 
<label>encodingDesc
<item>A's coding practice may or (more likely) may not be the
same as B's. Since the object of the coding description is to
define the relationship between the current file and its source,
in principle only changes in encoding practice between A and B
need be documented in B. The relationship between A and its
source(s) is then only recoverable from the original header of
A. In practice it may be more convenient to create a new
complete <gi>encodingDesc</gi> for B based on A's.
 
<label>revisionDesc
<item>B is a new electronic file, and should therefore have a
new revision description. If, however, it is felt useful to
include some information from A's <gi>revisionDesc</gi>, for
example dates of major updates or versions, such information
must be clearly marked as relating to A rather than to B.
 
</list>
 
<div3 id='HD32'><head>Computer Files Composed of Transcribed Speech
 
<p>Where an electronic text is derived from a spoken text rather than a
written one, it will usually be desirable to record additional
information about the recording or broadcast which constitutes its
source.  Several additional elements are provided for this purpose
within the source description element:
 
<tagList>
<tagDesc tagDoc=SCRSTMT>
<tagDesc tagDoc=RECSTMT>
<tagDesc tagDoc=RECORDIN atts="type dur">
<tagDesc tagDoc=EQUIPMEN>
<tagDesc tagDoc=BROADCAS>
</tagList>
 
<p>Note that detailed information about the participants or setting of
an interview or other transcript of spoken language should be recorded
in the appropriate division of the profile description, discussed in
chapter <xref target='CC'>, rather than as part of the source
description.  The source description is used to hold information only
about the source from which the transcribed speech was taken, for
example, any script being read and any technical details of how the
recording was  produced.  If the source was a previously-created
transcript, it should be treated in the same way as any other source
text.
 
<p>The <gi>scriptStmt</gi> element should be used where it is known that
one or more of the participants in a spoken text is speaking from a
previously prepared script.  The script itself should be documented in
the same way as any other written text, using one of the three citation
tags mentioned above.  Utterances or groups of utterances may be linked
to the script concerned by means of the <att>decls</att> attribute,
described in section <xref target=CCAS>.
<!-- was:  target='P2.3431'>. -->
<!-- or :  target='SP31'>. -->
 
<eg><![ CDATA[
<sourceDesc>
  <scriptStmt id=CNN12>
  <bibl><author>CNN Network News</>
     <title>News headlines</>
     <date>12 Jun 1991</>
  </bibl>
  </scriptStmt>
  <!-- this script statement might be used to document
       the parts of a spoken transcript which included
       a news broadcast -->
  <!-- possibly other script statements or recording
       statements follow -->
</sourceDesc>
]]>
</eg>
 
<p>The <gi>recordingStmt</gi> is used to group together information
relating to the recordings from which the spoken text was transcribed.
The element may contain either a prose description or, more helpfully,
one or more <gi>recording</gi> elements, each corresponding with a
particular recording.  The linkage between utterances or groups of
utterances and the relevant recording statement is made by means of the
<att>decls</att> attribute, described in section <xref target=CCAS>.
<!-- was:  target=P2.3431>. -->
<!-- was:  target=SP31>. -->
 
<p>The <gi>recording</gi> element should be used to provide a
description of how and by whom a recording was made.  This information
may be a prose description, within which such items as statements of
responsibility, names, places and dates should be identified using the
appropriate phrase level tags.  The <gi>recording</gi> element takes two
additional attributes, as indicated above:  <att>type</att> is used to
specify the kind of recording concerned and <att>dur</att> to specify
its length.
 
<p>In addition, descriptive information relating to the kind of
recording equipment used should be specified using the
<gi>equipment</gi> element.  Where a recording is taken from a public
broadcast, details of the broadcast should be given using the
<gi>broadcast</gi> element described further below.  Specialized
collections may wish to add further sub-elements to these major
components.  Note however that this element should be used only for
information relating to the recording process itself; information about
the setting or participants (for example) is recorded elsewhere:  see
sections <xref target=CCAHSE> and <xref target=CCAHPA> below.
<!-- was:  xref target=HD44 and xref target=HD45 -->
 
<eg><![ CDATA[
  <recording type=video>
  <p>U-matic recording made by college audio-visual
    department staff,available as PAL-standard VHS
    transfer or sound-only casssette
  </recording>
]]>
</eg>
 
<eg><![ CDATA[
  <recording type=audio dur="30 mins">
  <respStmt>
     <resp>Location recording by</resp>
     <name>Sound Services Ltd.</name>
  </respStmt>
  <equipment>
     <p>Multiple close microphones mixed down to stereo Digital
     Audio Tape, standard play, 44.1 KHz sampling frequency
  </equipment>
  <date>12 Jan 1987</date>
  </recording>
]]>
</eg>
 
<p>When a recording has been made from a public broadcast, details of
the broadcast itself should be supplied within the <gi>recording</gi>
element, as a nested <gi>broadcast</gi> element.  A broadcast is closely
analogous to a publication and the <gi>broadcast</gi> element should
therefore contain one or the other of the bibliographic citation
elements <gi>bibl</gi>, <gi>biblStruct</gi> or <gi>biblFull</gi>.  The
broadcasting agency responsible for a broadcast is regarded as its
author, while other participants (for example interviewers,
interviewees, directors, producers, etc.) should be specified using the
<gi>respStmt</gi> or <gi>editor</gi> element with an appropriate
<gi>resp</gi> (see further section <xref target=COBI>).
<!-- was:  target='P2.235'>). -->
<!-- was:  target=COBIBL>). -->
 
<eg><![ CDATA[
<recording type=audio dur="10 mins">
  <equipment><p>Recorded from FM Radio to digital tape</>
  <broadcast>
     <bibl><title>Interview on foreign policy</>
              <author>BBC Radio 5</>
       <respStmt><resp>interviewer</><name>Robin Day</></>
       <respStmt><resp>interviewee</><name>Margaret Thatcher</></>
       <series><title>The World Tonight</></>
       <note>First broadcast on <date>27 Nov 1989</></note>
    </bibl>
  </broadcast>
</recording>
]]>
</eg>
 
<p>When a broadcast contains several distinct recordings (for example a
compilation), additional <gi>recording</gi> elements may be further
nested within the <gi>broadcast</gi> element.
 
<eg><![ CDATA[
    <recording dur=100>
       <broadcast>
         <!-- details of broadcast -->
         <recording>
            <!-- details of broadcast recording -->
         </recording>
      </broadcast>
   </recording>
]]>
</eg>
<!-- need a real example here -->
<!-- damn straight.  -msm     -->
 
<p>Formal definitions for the elements discussed in this section are as
follows:
<dtdFrag id=D2231 n='Script statement and recording statement'>
<tagDecl tagDoc=SCRSTMT>
<tagDecl tagDoc=RECSTMT>
<tagDecl tagDoc=RECORDIN>
<tagDecl tagDoc=EQUIPMEN>
<tagDecl tagDoc=BROADCAS>
</dtdFrag>
<p>This concludes the discussion of the <gi>fileDesc</gi> element and
its contents.
<?tei:EOF p2hd3.odd ?>
