- From: Daniel Barclay <daniel@fgm.com>
- Date: Thu, 15 Feb 2007 13:36:38 -0500
- To: w3c-ietf-xmldsig@w3.org
The current XML-Signature Syntax and Processing specification at http://www.w3.org/TR/2002/REC-xmldsig-core-20020212/ contains a couple grammtical errors: * Section 7.1 says: ... if the following syntax constraints are observed ...: 1. attributes having default values be explicitly present, 2. all entity references (except "amp", "lt", "gt", "apos", "quot", and other character entities not representable in the encoding chosen) be expanded, 3. attribute value white space be normalized Specifically, the occurrences of "be" should be "are" or "is." (It appears that the text before the list was reworded from a form that required the subjunctive in the list to a form that doesn't, but that the wording in the list wasn't adjusted accordingly.) (Also, there probably should be a period (full stop) at the end of item number three, and an "and" at the end of item number two.) * Section 7.3 says: ... When serializing a Signature element or signed XML data that's the child of other elements using these data models, that Signature element and its children, may contain namespace declarations from its ancestor context. The second comma is extraneous. (Also, a sentence or two later, XML appears as "xml" (instead of as "XML").) * Section 7.3 also says: To avoid these problems, the application may: 1. Rely upon ... . Or, 2. Use ... . It seems that that should be capitalized and punctuated as: To avoid these problems, the application may: 1. rely upon ... , or 2. use ... . (Perhaps there's another way of fixing that that still retains the initial capital in each item.) Daniel --
Received on Thursday, 15 February 2007 18:37:11 UTC