|
|
| <prev next> |
Sponsor |
Comments for Exclusive XML Canonicalization: msg#00000ietf.xmldsig
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@xxxxxx tel:+1.858.483.4819 World Wide Web Consortium (W3C) http://www.w3.org/
|
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Next by Date: | Re: [xml-dev] canonicalization, Christian Geuer-Pollmann |
|---|---|
| Next by Thread: | Re: [xml-dev] canonicalization, Christian Geuer-Pollmann |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
Free MagazinesCisco NewsReceive a free quarterly e-newsletter with exclusive articles on how Cisco IT uses its own products and solutions to enable the business. subscribe Systems Management News, the newspaper for IT systems administration and data center managers! Each issue of Systems Management News is chock-full of news and analysis to help you understand what's happening in your field. subscribe The Enterprise Newsweekly eWeek is the essential technology information source for builders of e-business. subscribe Oracle Magazine Oracle Magazine contains technology strategy articles, sample code, tips, Oracle and partner news, how to articles for developers and DBAs, and more. Oracle (NASDAQ: ORCL) is the world's largest enterprise software company. subscribe Total Telecom Total Telecom is "The Economist of the communications industry". subscribe |
Home | sitemap
| advertise | OSDir is
an inevitable website.
|