W3C home > Mailing lists > Public > xml-encryption@w3.org > September 2001

Minor comments on Section 4

From: Takeshi Imamura <IMAMU@jp.ibm.com>
Date: Tue, 18 Sep 2001 01:10:29 +0900
To: xml-encryption@w3.org
Message-ID: <OF9A79D07A.F7140316-ON49256ACA.0053244A@LocalDomain>


I have a few comments on Section 4.

In Section 4.1, step 3.2,

>If the data is of any other type that is not already octets,
>the Encryptor must serialize it as octets.  For example, the data
>might be a serialization of an XML Information Set, set of
>characters, binary image data, or a compressed XML element.

I believe that this serialization should be also done by not the Encryptor
but the application.  That is, given data being serialized, the Encryptor
just calls a serialization module provided by the application.  Of course,
it should be allowed for the Encryptor to provide original serialization
modules for certain types of data.

In Section 4.1, step 5.1,

>When an application
>requires an XML element or content to be replaced, it supplies the
>XML Document context in addition to identifying the element or
>content to be encrypted.

"to be encrypted" would be "to be replaced".

In Section 4.2, step 1,

>Parse the application identified EncryptedType
>element to determine the algorithm, parameters and
>ds:KeyInfo element to be used. If some information is
>omitted, the application must supply it.

Because we already do not care whether the input to this step is an octet
sequence, "parsing an EncryptedType element" is not always correct and
should be revised to another expression.

Tokyo Research Laboratory
IBM Research
Received on Monday, 17 September 2001 12:10:16 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:32:02 UTC