- From: John Keeping <john@metanate.com>
- Date: Fri, 12 Jun 2009 18:57:17 +0100
- To: w3c-ietf-xmldsig@w3.org
Hi, We've recently implemented XML digital signature support for an XML format with an associated schema which defines an element as type xs:base64Binary. This implies that white space in the element's content is to be collapsed. Indeed, when reading in the XML file, Xerces-C generates a DOM tree in which new lines in the content have been collapsed to single spaces. However the digest has been calculated over text content containing the new lines. Given that both applications have the schema available to them, what would you expect the behaviour to be in this case? As far as I can see there are three possibilities: 1. The generating application collapses white space in its output in order to be compatible with both a receiving application which has the schema and one which does not 2. The receiving application ignores the white space directive from the schema 3. The generating application adds an explicit xml:space="collapse" attribute to the element Thanks, John -- John Keeping Metanate Ltd www.metanate.com (Software consultancy) www.schemus.com (Data synchronisation) This e-mail and all attachments it may contain is confidential and intended solely for the use of the individual to whom it is addressed. Any views or opinions presented are those of the author and do not necessarily represent those of Metanate Ltd. If you are not the intended recipient, be advised that you have received this e-mail in error and that any use, dissemination, printing, forwarding or copying of this e-mail is strictly prohibited. Please contact the sender if you have received this e-mail in error.
Received on Friday, 12 June 2009 20:59:55 UTC