W3C home > Mailing lists > Public > xml-encryption@w3.org > February 2002

Re: Data replacement

From: Takeshi Imamura <IMAMU@jp.ibm.com>
Date: Tue, 5 Feb 2002 16:52:59 +0900
To: reagle@w3.org
Cc: xml-encryption@w3.org
Message-ID: <OFEA9FE3C4.4A33BCF7-ON49256B57.00260D85@LocalDomain>


>Yes, I thought we agreed that the octets long ago that what you encrypt is
>the UTF-8 encoding of the XML data you want to secure. What other
>serializations would you want,

I don't have any concrete serialization, but one may want to serialize an
element in UTF8 and then compress it...

>what does this permit (instead of being
>presently precluded/limited), and if I understand you properly, then we'd
>need to include an attribute that indicates the encoding of the decrypted
>content, right?

Yes.  But anyway, I think I understand what the spec says, and to my
understanding, the sentence in step 3.2 for encryption:

For example, the data might be a serialization of an XML Information Set,
set of characters, binary image data, or a compressed XML element.

may be confusing because "an XML Information Set" and "a compressed XML
element" seem to hint an element or element content being encrypted.

Tokyo Research Laboratory
IBM Research
Received on Tuesday, 5 February 2002 02:53:07 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:13:07 UTC