Hi Joseph, Attached are: signature-example-dsa.xml - DSA example signature signature-example-rsa.xml - RSA example signature merlin-xmldsig-fourteen.tar.gz - one signature covering many things merlin-xmldsig-fifteen.tar.gz - several signatures covering some things Namespaces are: <!ENTITY dsig "http://www.w3.org/2000/09/xmldsig#"> <!ENTITY c14n "http://www.w3.org/TR/2001/REC-xml-c14n-20010315"> Brian and I have had recent interop success; hopefully the namespace change won't affect that. However, it would probably be a good idea to check that someone can verify the signatures before we assert validity. Merlin r/reagle@w3.org/2001.03.22/16:10:35 ----------------------------------------------------------------------------- Baltimore Technologies plc will not be liable for direct, special, indirect or consequential damages arising from alteration of the contents of this message by a third party or as a result of any virus being passed on. In addition, certain Marketing collateral may be added from time to time to promote Baltimore Technologies products, services, Global e-Security or appearance at trade shows and conferences. This footnote confirms that this email message has been swept by Baltimore MIMEsweeper for Content Security threats, including computer viruses. http://www.baltimore.com
This archive was generated by hypermail 2.2.0 + w3c-0.29 : Thursday, 13 January 2005 12:10:12 GMT