>If I may soapbox about certainty and uncertainty:

>(1) Assigning certainties by category:

I think this is a good point. We should certainly add text
recommending the use of bands of certainty rather than numerical
values for the reasons you suggest.


>(2) Uncertainty is ubiquitous. Why not make cert a universal attribute?

If you use this tagset, then the cert attribute does become universal.


SUGGESTED CHANGES:

17 Certainty and Responsibility, para 3:

   Change "To use the note and respStmt elements, no special steps are
needed, since they are defined in the core tag set and header
respectively."  to "No special steps are needed to use the note and
respStmt elements since they are defined in the core tag set and
header, respectively."

OK; done.

17.1, para 3:

   Change "though they may be expressed using note."  to "though they may
be expressed using the note element."

"note" should actually appear as "<note>", but the formatting didnt work properly in this draft. However your emendation is still better!

17.1.1, second example <note>:

   Rearrange so there is no hyphen in target="p1 p2"? (Hyphens appear in
the other examples as well.)

This one is definitely an artefact of the HTML formatting. Fixed.

17.1.2, assertedValue:

   "if none is given, it applies to the markup in the text" is ambiguous
with respect to the precedents.

? I dont see the ambiguity. If you supply a value for assertedValue
you are talking about the (lackof) certainty for that value, if you
dont, you're talking about the (lack of) certainty in the markup with
which the <certainty> tag itself is associated (by means of the target
attribute). Please explain!

para 3:

>Maybe precede "The certainty element may be used to record doubts"
 with "Returning to the example,"

Sure!

>  Change "(here: whether we have used the correct element type):" to
"(here, whether we have used the correct element type):"

Changed "here:" to "in this case,"

First example:

Change  "<!-  ...   elsewhere  in  the  document  ...   ->"  to  "<!--
... elsewhere  in the document ...  -->" (Similar "-"  for "--" errors
need to be corrected in the other examples as well.)

Caused by a formatting bug.


p. 409, para 2:

>  Change "Both elements indicate the same location in the text, but the
second provides an alternative choice of generic identifier (here:
persName) is given as the value of the assertedValue attribute:" to
"Both elements indicate the same location in the text, but the second
provides an alternative choice of generic identifier (here, persName)
which is given as the value of the assertedValue attribute:"


Changed "here:" to "in this case,"

>(The font size of persName needs to be changed.)

Caused by a bug in the xml conversion! fixed.

p. 410:

>Check font size of #transcribedContent and #suppliedContent.

OK. 

para 6:

>  Change "(specifically, when the alternate reading has no elements
nested within it)" to "(specifically, when the alternative reading has
no elements nested within it)".

OK: also changed an earlier occurrence of "alternate" to "alternative"

> Last para: Are commas required in "discursive unstructured
indication" and "complex structured project-specific expressions"?

You tell me. I've revised the sentence anyway!
 
p. 411, para 2:

> Change "While they may take any string of characters as value," to
"While each may take any string of characters as its value,"

I've changed "they" to "these attributes": reads better to my ears!


> Change "encoders are should provide their own controlled vocabulary"
to "encoders should provide their own controlled vocabulary"

Whoops!


17.2, para 2:

> Change "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."  to "In some cases, however, more detailed
element-by-element information may be desired. For example, one may
wish to distinguish between the individuals responsible for
transcribing the content and those responsible for determining that a
given word or phrase constitutes a proper noun."

OK. 

Description of <respons>:

> Change "markup of some particular element(s)" to "markup of particular
element(s)"

OK

target:
> Delete "SGML"?

Yes. This is probably a generic problem...

para 3:

> Change "as they do on the certainty element" to "as they do in the
certainty element"

? We usually talk about attributes being ON elements rather than IN them (the latter implying containment)

> Delete the comma following "encoding of those elements"

OK

> "combined as appropriate:" change the colon to a semicolon

OK

p. 412, para 2:

> Change "Some elements bear specialized resp or agent attributes,
which have specific meaning which varies from element to element;" to
"Some elements bear specialized resp or agent attributes which have
specific meanings that vary from element to element;"

OK

Thanks!

Lou
