Date: Thu, 17 Aug 2000 15:55:25 -0400
Message-ID: <3120721CA75DD411B8340090273D20B10C1B55@sottmxs06.entrust.com>
To: XML DSig <w3c-ietf-xmldsig@w3.org>
The XSLT spec requires XSLT processors to create a "result tree". How and whether an XSLT processor writes the "result tree" is up to the processor itself. After processing with XSLT and before signing, applications SHOULD canonicalize the output from the result tree. Ed -----Original Message----- From: John Boyer [mailto:jboyer@PureEdge.com] Sent: Thursday, August 17, 2000 3:31 PM To: XML DSig Subject: XSLT I've often wondered, how open-ended is XSLT regarding the output. Are there permissible implementation differences that are not covered off by throwing a c14n transform after (or before and after)? Or rather, is there an XSLT conformance mode that guarantees any implementation adhering to that mode produces the exact same output (except possibly for differences that can be corrected by c14n, and possibly only if the input is canonicalized)? Or is it the case, for example, that random extra whitespace may be added outside of start tags by some processors and not by others? 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
(image/gif attachment: LINE.gif)
(image/jpeg attachment: PureEdge.jpg)