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

Data replacement

From: Takeshi Imamura <IMAMU@jp.ibm.com>
Date: Mon, 21 Jan 2002 23:30:54 +0900
To: xml-encryption@w3.org
Message-ID: <OFDDD35FA0.B9205893-ON49256B48.004697D8@LocalDomain>


This question might be asked before, but let me ask it again.

Step 3.1 of the encryptor's processing says:

If the data is an 'element' [XML, section 3] or element 'content' [XML,
section 3.1], obtain the octets by serializing the data in UTF-8 as
specified in [XML].
What does "data is an 'element' or element 'content'" mean?  To my
understanding, it means the type of the serialized version of data is
'element' or element 'content', but is it right?  If yes, step 5.1:

If the Type of the encrypted data is 'element' or element 'content', then
the encryptor MUST be able to return the EncryptedData element to the
application. ... The encryptor SHOULD be able to replace the unencrypted
'element' or 'content' with the EncryptedData element.

means the encryptor replaces only the data that is 'element' or element
'content'.  However, it is a little limiting because the application may
want to have the encryptor replace data that is actually an element but is
not serialized to octets of type 'element'.  So, I think we should relax
the limitation by allowing the encryptor to replace data as far as it is
actually an element.  How do you feel?

Tokyo Research Laboratory
IBM Research
Received on Monday, 21 January 2002 09:37:22 UTC

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