W3C home > Mailing lists > Public > w3c-ietf-xmldsig@w3.org > October to December 2004

RE: Encoding of signed document question

From: John Boyer <JBoyer@PureEdge.com>
Date: Tue, 21 Dec 2004 08:57:05 -0800
Message-ID: <7874BFCCD289A645B5CE3935769F0B52D885CD@tigger.pureedge.com>
To: "Hess Yvan" <yvan.hess@imtf.ch>, <w3c-ietf-xmldsig@w3.org>

You certainly can use any encoding you want.  In fact you can take
store the document using pretty much any XML syntactic convenience
as well.

You're allowed to vary encodings, vary attribute order, switch between 
empty tags and empty content, use CDATA sections, etc. because C14N 
"corrects" for all of these syntactic variations when generating the 
XML serialization to be hashed.

Actually, this is the very point of using C14N in the signature generation 
and validation processes.  

John Boyer, Ph.D.
Senior Product Architect and Research Scientist
PureEdge Solutions Inc.

-----Original Message-----
From: Hess Yvan [mailto:yvan.hess@imtf.ch]
Sent: Tuesday, December 21, 2004 7:24 AM
To: 'w3c-ietf-xmldsig@w3.org'
Subject: Encoding of signed document question


Do I have the right to store a signed XML document into a filesystem or a
database using a different encoding than "UTF-8"? In the context of my
application I have to save it using encoding "ISO-8859-1".
Is it conform to specifications ? What will be the incidence of a such
choice ?

Thanks for your answer.

Regards. Yvan Hess
Received on Tuesday, 21 December 2004 16:57:44 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:21:40 UTC