- From: John Boyer <jboyer@PureEdge.com>
- Date: Wed, 19 Jul 2000 11:22:51 -0700
- To: "Anli Shundi" <anli.shundi@nue.et-inf.uni-siegen.de>, <w3c-ietf-xmldsig@w3.org>
Hi Anli, The newlines are included. They are represented by text nodes in the XPath data model, so we don't need to add extra linefeeds to get the multiline effect. So, if the document element and all its content are on one line, then so it will be in the output, but if the document element contains new lines, they will appear in the output. John Boyer Development Team Leader, Distributed Processing and XML PureEdge Solutions Inc. Creating Binding E-Commerce v: 250-479-8334, ext. 143 f: 250-479-3772 1-888-517-2675 http://www.PureEdge.com <http://www.pureedge.com/> -----Original Message----- From: w3c-ietf-xmldsig-request@w3.org [mailto:w3c-ietf-xmldsig-request@w3.org]On Behalf Of Anli Shundi Sent: Wednesday, July 05, 2000 5:42 AM To: w3c-ietf-xmldsig@w3.org Subject: no newlines after end-element tags in c14n ? The new canonicalization does not seem to specify whether a newline is appended after end-element tags. It mentions those after processing instructions and comments, though. Does this mean that the canonical output would be a single line, unpleasant to the eye like: <root attrib1="dsadsa"><son attr="fdsfds"><daughter>value</daughter></son></root> I would have expected something along the lines of <root attrib1="dsadsa"> <son attr="fdsfds"> <daughter>value</daughter> </son> </root> Am I overlooking something pretty obvious ? Anli Shundi Institute for Data Communications Systems University of Siegen Germany
Received on Wednesday, 19 July 2000 14:21:56 UTC