W3C home > Mailing lists > Public > w3c-ietf-xmldsig@w3.org > July to September 2002

Comments for Exclusive XML Canonicalization

From: Susan Lesch <lesch@w3.org>
Date: Mon, 1 Jul 2002 03:40:26 -0700
Message-Id: <p05111b01b945df6057e4@[192.168.123.158]>
To: jboyer@PureEdge.com, Donald.Eastlake@Motorola.com, reagle@w3.org, w3c-ietf-xmldsig@w3.org

These are minor editorial comments for your Exclusive XML
Canonicalization Proposed Recommendation [1]. Apologies, these were due
about 10 days ago. If they are too late to be useful please ignore.

s/Proposed Recommendations/Proposed Recommendation/
s/W3C membership/W3C Membership/
s/The Names in XML Recommendation/The Namespaces in XML Recommendation/
(or The namespaces Recommendation)

There are six occurrences of "node set" and four of "nodeset". I am not
sure but think that would be "node-set" with a hyphen. (The XPath
Recommendation has one "Node Set" in a heading, the rest "node-set".)

In 1.1, I guess you have nodes marked up as code and elements as em.
If that's right, I would say element <em>E</em> in paragraph 8. That
paragraph also needs an ending period after "prefix."

There are two occurrences of "xml namespace" and one "XML namespace".
If you need lowercase, can the xml be code, or could all three be "XML
namespace"?

    XPath node-set, that is an octet sequence,
maybe could be either:
    XPath node-set that is an octet sequence
or:
    XPath node-set, that is, an octet sequence,
(not sure there)

In 1.3 item 2, visibly utilized could be <a
class="link-def" href="#def-visibly-utilizes">visibly utilized</a>

s/the following XPath expression/the following XPath expression:/
s/presense/presence/
s/thestate/the state/

s/whitespace delimited list/white space delimited list/
or change the other:
s/a white space separated list/a whitespace separated list/

s/in in/in/

First person could be hard to translate.
(see http://www.w3.org/2001/06/manual/#Translations)

    While we feel such choices are consistent with other XML
    specifications and satisfy our application requirements it is
    important that....
could be:
    While such choices are consistent with other XML specifications
    and satisfy [?] application requirements it is important that....

    We provide this example to caution
could be:
    This example is provided to caution

In 6. Keywords, "S. Bradner. March 1997." appears twice.

In 6. URI, there is an extra space in "RFC 2396 ."

In 6. XPath, "eds." could be omitted and the names could be J. Clark
and S. DeRose to match your other references.


[1] http://www.w3.org/TR/2002/PR-xml-exc-c14n-20020524/

Best wishes for your project,
-- 
Susan Lesch           http://www.w3.org/People/Lesch/
mailto:lesch@w3.org               tel:+1.858.483.4819
World Wide Web Consortium (W3C)    http://www.w3.org/
Received on Monday, 1 July 2002 06:40:37 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:10:10 UTC