<!-- $Id: p2ce.odd,v 1.10 1998/01/31 19:50:52 tei Exp $ -->
<!--*
    * $Log: p2ce.odd,v $
    * Revision 1.10  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.9  98/01/28  11:09:58  cmsmcq
    * LB changes of January 1998
    *
    * Revision 1.8  1994/03/27  16:28:51  lou
    * semifinal check
    *
    * Revision 1.5  1994/03/07  14:37:11  lou
    * fix typos noted by CH; add ref to SA
    *
    * Revision 1.4  1994/02/12  21:37:58  msmcq
    * strip ^Z
    *
    * Revision 1.3  1994/01/21  18:09:59  lou
    *  fix typos (respon for respons; abbrev for abbr)
    *
    * Revision 1.2  1993/09/22  18:12:55  msmcq
    * As of publication of CE, 17 Sept 93
    *-->
<!-- CE:  Indications of Certainty and Confidence             -->
<!-- Revisions:                                               -->
<!-- 8 jan 98 : LB : fix typos from MSM -->
<!-- 5 mar:  fix typos noted by Claus; add ref to SAat -->
<!-- 9 jan 93: LB: fix another typo ; abbrev is now abbr      -->
<!-- 93-09-17 : MSM : correct a typo                          -->
<!-- 93-09-17 : MSM : correct example of expan                -->
<!-- 93-09-17 : MSM : Change xref tctr to PHda                -->
<!-- 93-05-27 : MSM : remove tagdoc to separate file          -->
<!-- 93-05-25 : AHR : made file with second draft             -->
<!-- 93-02-27 : MSM : made file with first draft              -->

<div1 id="CE" n="17"><head>Certainty and Responsibility</head>

<p>Encoders of text often find it useful to indicate that some aspects
of the encoded text are problematic or uncertain, and to indicate who is
responsible for various aspects of the markup of the electronic text.
These Guidelines provide three methods of recording uncertainty about the
text or its markup:

<list type="bullets">
<item>the <gi>note</gi> element defined in section <ptr target="COno"> may
be used with a value of <code>certainty</code> for its <att>type</att>
attribute.</item>
<item>the <gi>certainty</gi> element defined in this chapter may be used
to record the nature and degree of the uncertainty in a more structured
way.</item>
<item>the <gi>alt</gi> element defined in the additional tag set for
linking and segmentation may be used to provide alternative encodings
for parts of a text, as described in section <ptr target="SAat">.</item>
</list>

There are three methods of indicating responsibility for different
aspects of the electronic text:
<list type="bullets">
<item>the TEI header records who is responsible for an electronic text
by means of the <gi>respStmt</gi> element and other more specific elements
(<gi>author</gi>, <gi>sponsor</gi>, <gi>funder</gi>, <gi>principal</gi>,
etc.) used within the <gi>titleStmt</gi>, <gi>editionStmt</gi>, and
<gi>revisionDesc</gi> elements.</item>
<item>the <gi>note</gi> element may be used with a value of <code>resp</code>
or <code>responsibility</code> in its <att>type</att> attribute.</item>
<item>the <gi>respons</gi> element defined in this chapter may be used
to record fine-grained structured information about responsibility for
individual tags in the text.</item>
</list>

To use the <gi>note</gi> and <gi>respStmt</gi> elements, no special steps
are needed, since they are defined in the core tag set and header
respectively.  The <gi>alt</gi> element is only available when the
additional tag set for linking has been selected, as described in
chapter <ptr target="SA">. To use the <gi>certainty</gi> and
<gi>respons</gi> elements, the additional tag set for certainty and
responsibility must be selected; this is done by defining the
parameter entity <ident type="pe">TEI.certainty</ident> with the value
<code type="kw">INCLUDE</code>, as shown in the example below:

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

<div2 id="CEcert"><head>Levels of Certainty</head>

<p>Many types of uncertainty may be distinguished.  The
<gi>certainty</gi> element is designed to encode the following sorts:

<list type="bullets">
<item>a given tag may or may not correctly apply (e.g. a given word may
be a personal name, or perhaps not)</item>

<item>the precise point at which an element begins or ends is
uncertain</item>

<item>the value to be given for an attribute is uncertain</item>

<item>content supplied by the encoder (such as the expansion of
an abbreviation marked by the <gi>abbr</gi> tag) is
uncertain</item>

<item>the transcription of a source text is uncertain, perhaps
because it is hard to read or hard to hear; this sort of
uncertainty is also handled by the <gi>unclear</gi> element in
section <ptr target="PHda"></item>
</list></p>

<p>The following types of uncertainty are <emph>not</emph> indicated
with the <gi>certainty</gi> element:

<list>

<item>a number or date is imprecise</item>

<item>the text is ambiguous, so a given passage has several possible
interpretations</item>

<item>a transcriber, editor, or author wishes to indicate a level of
confidence in a factual assertion made in the text</item>

<item>an author is not sure if the sentence she has chosen to start a
paragraph is really the one she wants to retain in the final version</item>

</list>

Precision of numbers and dates is discussed in section <ptr
target="COna">
<!-- and chapter <ptr target=ND> -->; well-defined ambiguity is handled with
alternations in feature-structure values in chapter <ptr target="FS">.
Uncertainty about the truth of assertions in the text and other sorts of
authorial and editorial uncertainty about whether the content is
satisfactory are not handled by the <gi>certainty</gi> element,
though they may be expressed using <gi>note</gi>.</p>

<div3 id="CEceno"><head>Using Notes to Record Uncertainty</head>

<p>The simplest way of recording uncertainty about markup is to attach a
note to the element or location about which one is unsure.  In the
following (invented) paragraph, for example, an encoder might be
uncertain whether to mark <q>Essex</q> as a place name or a personal
name, since both might be plausible in the given context:

<q rend="display">
Elizabeth went to Essex.  She had always liked Essex.
</q>

Using <gi>note</gi>, the uncertainty here may be recorded quite simply:

<eg>
<![ CDATA [
<persName>Elizabeth</> went to
<placeName>Essex</>.
She had always liked <placeName>Essex</>.
<note type='uncertainty' resp='MSM'>It is not
clear here whether <mentioned>Essex</mentioned>
refers to the place or to the nobleman. -MSM</note>
]]>
</eg></p>

<p>Using the normal mechanisms, the note may be associated
unambiguously with specific elements of the text, thus:

<eg>
<![ CDATA [
<persName>Elizabeth</> went to
<placeName id=p1>Essex</>.
She had always liked <placeName id=p2>Essex</>.
<note type='uncertainty' resp='MSM' target='p1 p2'>
It is not clear here whether <mentioned>Essex</mentioned>
refers to the place or to the nobleman.  If the latter,
it should be tagged as a personal name. -MSM</note>
]]>
</eg></p>

<p>The advantage of this technique is its relative simplicity.  Its
disadvantage is that the nature and degree of uncertainty are not
conveyed in any systematic way and thus are not susceptible to any sort
of automatic processing.</p></div3>

<div3 id="CEcece"><head>Structured Indications of Uncertainty</head>

<p>To record uncertainty in a more structured way, susceptible of at
least simple automatic processing, the <gi>certainty</gi> element may be
used:

<list type=gloss>
<label><gi>certainty</gi></label>
<item>indicates the degree of certainty or uncertainty associated 
with
some aspect of the text markup.
Attributes include:
<list type=gloss>
<label><att>target</att></label>
<item>points at the elements whose markup is uncertain.</item>
<label><att>locus</att></label>
<item>indicates the precise location of the uncertainty in the 
markup: applicability of the element, precise position of 
the start- or end-tag, value of a specific attribute, etc.
Suggested values include:
<list type=gloss>
<label><term>name</term></label>
<item>the value given for the attribute <att>name</att> is 
uncertain.</item>
<label><term>#suppliedContent</term></label>
<item>the content of the element may not have been correctly 
supplied by the reader, e.g. as in the cases of 
<gi>corr</gi> and <gi>abbrev</gi> elements.</item>
<label><term>#location</term></label>
<item>both the start-tag and the end-tag may not be correctly 
located.</item>
<label><term>#startloc</term></label>
<item>start-tag may not be correctly located.</item>
<label><term>#endloc</term></label>
<item>end-tag may not be correctly located.</item>
<label><term>#transcribedContent</term></label>
<item>the content of the element may not be a correct 
transcription of the source text.</item>
<label><term>#gi</term></label>
<item>uncertain whether the element used actually applies to the 
passage.</item>
</list></item>
<label><att>given</att></label>
<item>indicates conditions assumed in the assignment of a degree 
of confidence.</item>
<label><att>degree</att></label>
<item>indicates the degree of confidence assigned to the aspect 
of the markup named by the <att>locus</att> attribute.</item>
<label><att>assertedValue</att></label>
<item>provides an alternative value for the aspect of the markup 
in question---an alternative generic identifier, 
transcription, or attribute value, or the ID of an 
<gi>anchor</gi> element (to indicate an alternative 
starting or ending location). If an 
<att>assertedValue</att> is given, the confidence level 
specified by <att>degree</att> applies to the alternative 
markup specified by <att>assertedValue</att>; if none is 
given, it applies to the markup in the text.</item>
<label><att>desc</att></label>
<item>further describes the uncertainty in prose, perhaps 
indicating its nature, cause, or the justification for the 
degree of confidence asserted.</item>
</list>
</item>
</list>
</p>

<p>The <gi>certainty</gi> element may be used to record doubts about
the proper encoding of <q>Essex</q> in several ways of varying
precision.  To record merely that we are not certain that <q>Essex</q>
is in fact a place name, as it is tagged, we use the <att>target</att>
attribute to identify the element in question, and the <att>locus</att>
attribute to indicate what aspect of the markup we are uncertain about
(here:  whether we have used the correct element type):

<eg><![ CDATA [
Elizabeth went to <placeName id=p1>Essex</>.

<!-- ... elsewhere in the document ... -->
<certainty target=p1 locus='#gi' desc='possibly not a placename'>
]]>
</eg>

Because it is linked to the location of the uncertainty by an IDREF, the
<gi>certainty</gi> element will typically be included in the same SGML
document as its target.  It may be placed adjacent to the target
element, or elsewhere in the document.</p>

<p>To record the further information that we estimate, subjectively,
that there is a 60 percent chance of <q>Essex</q> being a place name here, we
can add a value for our <att>degree</att> of confidence (usually a
number between 0 and 1, representing the estimated probability):

<eg><![ CDATA [
Elizabeth went to <placeName id=p1>Essex</>.

<!-- ... -->
<certainty target=p1 locus='#gi'
           degree='0.6'
           desc='possibly not a placename'>
]]>
</eg>

According to one expert, there is a 60 percent chance of
<q>Essex</q> being a place name here, and a 40 percent chance of its being a
personal name. We use two <gi>certainty</gi> elements to indicate the
two probabilities independently. Both elements indicate
<!-- , we use the <att>resp</att> attribute to associate the
certainty information with AR.  To specify the second probability, we
use a second <gi>certainty</gi> element, pointing at -->
the same location in the text, but the second provides an alternative
choice of generic identifier (here: <code>persName</code>) is given as the
value of the <att>assertedValue</att> attribute:

<eg><![ CDATA [
Elizabeth went to <placeName id=p1>Essex</>.

<!-- ... -->
<certainty target=p1 locus='#gi'
           degree='0.6'
           desc='probably a placename, but possibly not'>
<certainty target=p1 locus='#gi'
           degree='0.4'
           assertedValue='persName'
           desc='may refer to the Earl of Essex'>
]]>
</eg></p>

<p>Finally, we may wish to make our probability estimates contingent
on some condition.  In the passage <q>Elizabeth went to Essex; she had
always liked Essex,</q> for example, we may feel there is a 60 percent chance
that the county is meant, and a 40 percent chance that the earl is meant.  But
the two occurrences of the word are not independent:  there is (we may
feel) no chance at all that one occurrence refers to the county and one
to the earl.  We can express this by using the <att>given</att>
attribute to list the SGML identifiers of <gi>certainty</gi> elements.

<eg><![ CDATA [
Elizabeth went to <placeName id=p1>Essex</>.
She had always liked <placeName id=p2>Essex</>.

<!-- ... -->
<!-- 60% chance that P1 is a placename,
     40% chance a personal name. -->
<certainty id=cert-1
           target=p1 locus='#gi' degree='0.6'
           desc='probably a placename, but possibly not'>
<certainty id=cert-2
           target=p1 locus='#gi' degree='0.4'
           assertedValue='persName'
           desc='may refer to the Earl of Essex'>

<!-- 60% chance that P2 is a placename,
     40% chance a personal name.
     100% chance that it agrees with P1. -->
<certainty given=cert-1
           target=p2 locus='#gi' degree='1.0'
           desc='if P1 is a placename, P2 certainly is'>
<certainty given=cert-2
           target=p2 locus='#gi' degree='1.0'
           assertedValue='persName'
           desc='if p1 refers to the Earl of Essex, so does P2'>
]]>
</eg>

When <att>given</att> conditions are listed, the <gi>certainty</gi>
element is interpreted as claiming a given degree of confidence in a
particular markup given the assertional content of the
<gi>certainty</gi> elements indicated---that is, <emph>if the markup
described in the indicated <gi>certainty</gi> elements is
correct.</emph></p>

<p>Conditional confidence may be less that 100 percent:  given the sentence
<q>Ernest went to old Saybrook</q>, we may interpret <q>Saybrook</q> as
a personal name or a place name, assigning a 60 percent probability to the
former.  If it is a place name, there may be a 50 percent chance that the
place name actually in question is <q>Old Saybrook</q> rather than
<q>Saybrook</q>, while if it is correctly tagged as a personal name, it
is much more likely (say, 90 percent certain) that the name is <q>Saybrook</q>.
This state of affairs can be expressed using the
<gi>certainty</gi> element thus:

<eg><![ CDATA [
Earnest went to <anchor id=a1> old
<persName id=p1>Saybrook</persName>.

<certainty id=c1 target=p1 locus='#gi' degree='0.6'>
<certainty given=c1 target=p1 locus=startloc degree='0.9'>

<certainty id=c2 target=p1 locus='#gi'
           assertedValue='persName' degree='0.4'>
<certainty given=c2 target=p1 locus=startloc degree='0.5'>
<certainty id=c3
           given=c1 target=p1 locus=startloc
           assertedValue='a1' degree='0.5' >
]]>
</eg>
In this case, the <att>assertedValue</att> on <gi>certainty</gi> element
c3 is an IDREF to an <gi>anchor</gi> element at the alternate starting
point for the element.</p>

<p>Multiplying the numeric values out, this markup may be interpreted as
assigning specific probabilities to three different ways of
marking up the sentence:

<eg><![ CDATA [
Earnest went to old <persName>Saybrook</>.   (0.6 * 0.9, or 0.54)
Earnest went to old <placeName>Saybrook</>.  (0.4 * 0.5, or 0.20)
Earnest went to <placeName>old Saybrook</>.  (0.4 * 0.5, or 0.20)
]]>
</eg>

The probabilities do not add up to 1.00 because the markup indicates
that if <q>Saybrook</q> is (part of) a personal name, there is a
10 percent likelihood that the element should start somewhere other than the
place indicated, without however giving an alternative location; there
is thus a 6 percent chance (0.1 * 0.6) that none of the alternatives given is
correct.</p>

<p>If an attribute value is uncertain, the <att>locus</att> attribute
takes as its value the name of the attribute in question.  In this
example, there is only a 50 percent chance that the question was spoken by
participant A:

<eg><![ CDATA [
<u id=u1 who=A>Have you heard the election results?</u>
<!-- ... -->
<certainty target=u1 locus=who degree='0.5'>
]]>
</eg></p>

<p>Doubts about whether the transcription is correct may be expressed
by assigning to <att>locus</att> the value
<code>#transcribedContent</code>.  For example, if the source is
hard to read and so the transcription is uncertain:

<eg><![ CDATA [
I have a <emph id=p1>gub</emph>.
<certainty target=p1 locus='#transcribedContent' degree='0.5'>
]]>
</eg></p>

<p>Degrees of confidence in the proper expansion of abbreviations may
also be expressed, by using the value <code>#suppliedContent</code>:

<eg><![ CDATA [
You will want to use <expan id=e1 abbr='SGML'>Standard
Generalized Markup Language</expan> ...

<!-- ... -->
<certainty target=e1 locus='#suppliedContent' degree='0.9'>
]]>
</eg></p>

<p>The <att>assertedValue</att> attribute should be used to provide an
alternative value for whatever aspect of the markup is in doubt:  an
alternative generic identifier, or the ID of an alternative starting or
ending point, as already shown, an alternative attribute value, or
alternative element content, as in this example:

<eg><![ CDATA [
I have a <emph id=p1>gub</emph>.

<certainty target=p1 locus='#transcribedContent'
           assertedValue='gun'
           degree='0.8'
           desc='a gun makes more sense in a holdup'>
]]>
</eg>

Since attribute values have no internal substructure, the
<att>assertedValue</att> attribute is useful for specifying alternative
transcriptions only in relatively restricted circumstances
(specifically, when the alternate reading has no elements nested within
it).  More robust methods of handling uncertainties of transcription are
the <gi>unclear</gi> element and the <gi>app</gi> and <gi>rdg</gi>
elements described in chapter <ptr target="TC">.
<!-- Parts of this para cut according to Durand's recommendation -->
<!--
<p>There are many subtleties in the indication of uncertainty and the
<gi>certainty</gi> element does not provide a fully general solution, or
even an unproblematic one.  In particular no claim is made that this
mechanism can express every sort of uncertainty that an encoder may wish
to assert, nor that it is wholly free from ambiguities.  However, the
--> The
<gi>certainty</gi> element allows for indications of uncertainty to
be structured with at least as much detail and clarity as appears to be
currently required in most ongoing text projects.
<!-- Encoders who wish to
disambiguate some use of this element, or to extend the recommended
attribute values, may document these assumptions or special vocabulary.
-->
It is expected that in the future more adequate systems for expressing
uncertainty will be developed.  These may extend the <gi>certainty</gi>
element or they may make use of the feature-structure encoding
mechanisms described in chapter <ptr target="FS">.</p>

<p>The <gi>certainty</gi> element and the other TEI mechanisms for
indicating uncertainty provide a range of methods of graduated
complexity.  Simple expressions of uncertainty may be made by using the
<gi>note</gi> element.  This is simple and convenient, and can
accommodate either discursive unstructured indication of uncertainty, or
complex structured project-specific expressions of uncertainty.  In
general, however, unless special steps are taken, the <gi>note</gi>
element does not provide as much expressive power as the
<gi>certainty</gi> element, and in cases where highly structured
certainty information must be given, it is recommended that the
<gi>certainty</gi> element be used.</p>

<p>The <gi>certainty</gi> element may be used for simple unqualified
indications of uncertainty, in which case only the <att>locus</att>
and <gi>target</gi> might be specified.  In more complex cases, the
other attributes may be used to provide fuller information.  While
they may take any string of characters as value, the recommended
values should be used wherever possible; if they are not appropriate
in a given situation, encoders are should provide their own controlled
vocabulary and document it in the <gi>encodingDesc</gi> or
<gi>tagUsage</gi> elements of the TEI header.</p>

<p>The <gi>certainty</gi> element has the following formal declaration:

<eg id=dce>
<![ CDATA [
<!-- 17.1.2:  Certainty and uncertainty                       -->
<!-- Text Encoding Initiative: Guidelines for Electronic      -->
<!-- Text Encoding and Interchange. Document TEI P3, 1994.    -->

<!-- Copyright (c) 1994 ACH, ACL, ALLC. Permission to copy    -->
<!-- in any form is granted, provided this notice is          -->
<!-- included in all copies.                                  -->

<!-- These materials may not be altered; modifications to     -->
<!-- these DTDs should be performed as specified in the       -->
<!-- Guidelines in chapter "Modifying the TEI DTD."           -->

<!-- These materials subject to revision. Current versions    -->
<!-- are available from the Text Encoding Initiative.         -->

<!ELEMENT certainty     - O  EMPTY                              >
<!ATTLIST certainty          %a.global;
          given              CDATA               #IMPLIED
          target             IDREFS              #REQUIRED
          desc               CDATA               #IMPLIED
          assertedValue      CDATA               #IMPLIED
          locus              CDATA               #REQUIRED
          degree             CDATA               #IMPLIED       >
<!-- ... declarations from section 17.2                       -->
<!--     (Responsibility for markup)                          -->
<!--     go here ...                                          -->
]]>
</eg>
</p></div3></div2>


<div2 id="CEresp"><head>Attribution of Responsibility</head>

<p>In general, attribution of responsibility for the transcription and
markup of an electronic text is made by <gi>respStmt</gi> elements
within the header: specifically, within the title statement, the
edition statement(s), and the revision history.</p>

<p>In some cases, however, more detailed element-by-element information
may be desired, in order to distinguish, for example, between the
individuals responsible for transcribing the content and those
responsible for determining that a given word or phrase constitutes a
proper noun.  Where such fine-grained attribution of responsibility is
required, the <gi>respons</gi> element may be used:

<list type=gloss>
<label><gi>respons</gi></label>
<item>identifies the individual(s) responsible for some aspect of 
the
markup of some particular element(s).
Attributes include:
<list type=gloss>
<label><att>target</att></label>
<item>gives the SGML identifier(s) of the element(s) for which 
some aspect of the responsibility is being assigned.</item>
<label><att>locus</att></label>
<item>indicates the specific aspect of the markup for which 
responsibility is being assigned.
Suggested values include:
<list type=gloss>
<label><term>name</term></label>
<item>responsibility for the claim that the <att>name</att> 
attribute has the value given in the markup</item>
<label><term>#suppliedContent</term></label>
<item>responsibility for the contents supplied by the encoder 
(corrections, expansions of abbreviations, etc.)</item>
<label><term>#location</term></label>
<item>responsibility for the claim that the element begins and 
ends where indicated</item>
<label><term>#startloc</term></label>
<item>responsibility for the claim that the element begins where 
indicated</item>
<label><term>#endloc</term></label>
<item>responsibility for the claim that the element ends where 
indicated</item>
<label><term>#transcribedContent</term></label>
<item>responsibility for the transcription of the element content</item>
<label><term>#gi</term></label>
<item>responsibility for the claim that the element is of the 
type indicated by the markup</item>
</list></item>
<label><att>resp</att></label>
<item>identifies the individual or agency responsible for the 
indicated aspect of the electronic text.</item>
<label><att>desc</att></label>
<item>gives a brief prose note supplying any additional 
information which should be recorded</item>
</list>
</item>
</list>
</p>

<p>This element allows one or more aspects of the markup to be
attributed to a given individual.  The <att>target</att> and
<att>locus</att> attributes function as they do on the
<gi>certainty</gi> element described in section <ptr target="CEcert">:
the <att>target</att> attribute points at a particular SGML element (or
set of elements), and <att>locus</att> indicates the particular aspect
of the encoding of those elements, for which responsibility is to be
assigned.  The suggested values may be combined as appropriate:  to
indicate, for example, that RC is responsible for transcribing an
illegible word, and that AR is responsible for identifying that word
as a proper noun, the text might be encoded thus:

<eg>
<![ CDATA [
 Earnest went to old <persName id=p1>Saybrook</persName>.
 <!-- ... -->
 <respons target=p1 locus='#transcribedContent' resp=RC>
 <respons target=p1 locus='#gi #location' resp=AR>
]]>
</eg></p>


<p>Some elements bear specialized <att>resp</att> or <att>agent</att>
attributes, which have specific meaning which varies from element to
element; the <gi>respons</gi> element should be reserved for the general
aspects of responsibility common to all text transcription and SGML
markup, and should not be confused with the more specific attributes on
individual elements.
<!-- oh yeah? which ones? (LB) --></p>

<p>The formal declaration of the <gi>respons</gi> element is this:

<eg id=dceresp>
<![ CDATA [
<!-- 17.2:  Responsibility for markup                         -->
<!ELEMENT respons       - O  EMPTY                              >
<!ATTLIST respons            %a.global;
          target             IDREFS              #REQUIRED
          desc               CDATA               #IMPLIED
          resp               CDATA               #REQUIRED
          locus              CDATA               #REQUIRED      >
<!-- This fragment is used in sec. 17.1.2                     -->
]]>
</eg>

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