W3C home > Mailing lists > Public > w3c-ietf-xmldsig@w3.org > January to March 2000

Re: minor typos in WD-xmldsig-core-20000228

From: by way of <lesch@w3.org>
Date: Wed, 15 Mar 2000 17:57:38 -0500
Message-Id: <3.0.5.32.20000315175738.00958a90@localhost>
To: "IETF/W3C XML-DSig WG" <w3c-ietf-xmldsig@w3.org>
I apologize as this is a duplicate report. It was sent two weeks ago 
and may have been lost in the shuffle; (the same typos are in the 
Internet-Draft 
http://www.ietf.org/internet-drafts/draft-ietf-xmldsig-core-05.txt).

Susan Lesch
Intern, World Wide Web Consortium (W3C)


--- Original message follows ---
> Please send comments to the editors and
> cc: the list <w3c-ietf-xmldsig@w3.org>.

These are very minor typos in the XML Signature last call Working 
Draft [1] "work in progress." Please use or ignore this list as you 
see fit. A section and paragraph number is followed by a quote, 
followed by an idea for an improvement. Comments are in brackets [].

1.1 par. 1
to to
to

stricly
strictly

Security Model.
Security Model.)

1.1 last par. [could link the first time it's mentioned]
the XML-namespace specification
the XML-namespace specification [XML-ns]

1.3 par. 3
[URI] and [URN] could link to References
[Also, I didn't understand the meaning of FIPS PUB 180-1 etc. Is it 
meant to be here as a reference or another example?]

2.0 par. 1
3:Processing Rules.
3: Processing Rules.
[Also, there is a stray <a> tag after Rules.]

2.0 par. 2
an  informal
an informal

2.0 par. 3
are be applied to
are to be applied to
[or:]
are applied to

2.1 par. 1
HTML4.1 in XML
HTML4 in XML

2.1.1 last par.
what bind's
what binds

3.1.2 list item 3
Object (s)
Object(s)

3.2 par. 2
undesireable
undesirable

side affects
side effects

4.2 par. 1
it is encoded according by the identifier
it is encoded by the identifier
[or:]
it is encoded according to the indentifier

4.3.3 pars. 2 and 3
URI-Reference [URI], as specified by RFC2396 [URI]
[URI in brackets could link to References or be omitted.]

4.3.3 par. 6
all-together
altogether

4.3.3.1 par. 1
document [section 8.2: Only What is "Seen" Should be Signed].
document. (See section 8.2: Only What is "Seen" Should be Signed.)

4.3.3.1 par. 4
base-64 [twice]
base64

4.3.3.3 par. 1
Base 64
base64

4.4 par. 3 list item 1
encoded DN
encoded domain name

4.4 last par. list item 4
(RFC 2253)
[RFC2253] and a link to References maybe

4.4 last par. list item 6
DH key exchange
Diffie-Hellman key exchange

4.5 par. 2
advisory, no validation
advisory; no validation

5.0 par. 1
Processing Instructions and Comments
processing instructions and comments

5.2 par. 1
generation.)
generation).

6.1 last par.
is the complete URIs
is the complete URI

6.2.1 par. 3
Example,
Example:

6.4.1 par. 1
http://www.w3.org/2000/02/xmldsig#</a><a name="dsa">dsa </a>
[Not sure why here but dsa is separated from the identifier's URI by 
a named anchor.]

6.6 par. 1
or as the output
or the output

6.6.2 heading
Base-64
Base64

6.6.2
base 64 and base-64 [three instances in par. 1, and in the identifier 
which I think needs to match the URI in the table in 6.1]
base64

6.6.3.3 par. 2
linefeeds
line feeds

6.6.3.3 par. 3
is unavailable
is unavailable.

6.6.3.3 list
<strong>Root Node-</strong> etc.
[You might consider using a colon outside the markup in place of the 
dashes after each node type. That would match the list of orderings 
in 6.6.3.2.]

7.0 par. 5
[XML]
XML or [XML] and link to References

8.1 par. 1
[XML-Signature-RD])
[XML-Signature-RD].)

8.2 par. 2
name space
namespace

9.0 RDF Data Model GIF
[The GIF has a transparent background. It will be partly invisible 
for people viewing with browser preferences set to any of its 
foreground colors. Could the GIF be opaque? Also, the bottom section 
was cut off and it was unclear to me if this was intended.]

9.0 XML Signature Example
Well formed
Well-formed


[1] http://www.w3.org/TR/2000/WD-xmldsig-core-20000228/
Received on Wednesday, 15 March 2000 17:57:39 GMT

This archive was generated by hypermail 2.2.0 + w3c-0.29 : Thursday, 13 January 2005 12:10:09 GMT