- From: Gregor Karlinger <gregor.karlinger@iaik.at>
- Date: Fri, 15 Sep 2000 06:45:34 +0200
- To: "John Boyer" <jboyer@PureEdge.com>, "Gregor Karlinger" <gregor.karlinger@iaik.at>, "XMLSigWG" <w3c-ietf-xmldsig@w3.org>
- Message-ID: <NDBBIMACDKCOPBLEJCCDAEPICKAA.gregor.karlinger@iaik.at>
Hi John, Thanks for clarification. I have not been aware of this substantive change in attribute value normalization. Regards, Gregor --------------------------------------------------------------- Gregor Karlinger mailto://gregor.karlinger@iaik.at http://www.iaik.at Phone +43 316 873 5541 Institute for Applied Information Processing and Communications Austria --------------------------------------------------------------- > -----Ursprüngliche Nachricht----- > Von: w3c-ietf-xmldsig-request@w3.org > [mailto:w3c-ietf-xmldsig-request@w3.org]Im Auftrag von John Boyer > Gesendet: Freitag, 15. September 2000 00:21 > An: Gregor Karlinger; XMLSigWG > Betreff: RE: Canonical XML comment (example 3.4) > > > Hi Gregor, > > Actually, I did originally intend to violate the validity constraint as is > done in XML errata 70 (with an NMTOKENS in their case) in order to > demonstrate the attribute value normalization that occurs in this case. > > However, the example is still wrong, not because of validation failure but > rather because the leading and trailing spaces need to be > removed. As well, > I should probably highlight the existence of this purposeful validity > constraint violation in Section 3.4 and in the paragraph at the top of > section 3. > > As well, I will suggest removal of the line containing that element for > those creating canonical forms with a validating processor, and I > will add a > line that shows the validating processors should use. > > > -----Original Message----- > From: w3c-ietf-xmldsig-request@w3.org > [mailto:w3c-ietf-xmldsig-request@w3.org]On Behalf Of Gregor Karlinger > Sent: Wednesday, September 13, 2000 10:28 PM > To: XMLSigWG; John Boyer > Subject: Canonical XML comment (example 3.4) > > > Hi John, > > In example 3.4 you declared the attribute "id" for the element > "normId" as being of type ID. An ID attribute value must meet > the name production according to XML 1.0 [1]. Therefore the > value you are using in the input document will produce a parsing > error: > > <normId id=' '   
	 ' '/> > > [1] http://www.xml.com/axml/target.html#sec-attribute-types > > Regards, Gregor > --------------------------------------------------------------- > Gregor Karlinger > mailto://gregor.karlinger@iaik.at > http://www.iaik.at > Phone +43 316 873 5541 > Institute for Applied Information Processing and Communications > Austria > --------------------------------------------------------------- > > > >
Received on Friday, 15 September 2000 00:44:49 UTC