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

RE: "Replace and encrypt will be Recommended (optional)."

From: Takeshi Imamura <IMAMU@jp.ibm.com>
Date: Tue, 7 Aug 2001 00:56:58 +0900
To: edsimon@xmlsec.com
Cc: "Joseph M. Reagle Jr." <reagle@w3.org>, XML Encryption WG <xml-encryption@w3.org>, Blair Dillaway <blaird@microsoft.com>
Message-ID: <OF5F244F89.00B1134F-ON49256AA0.0053B91B@LocalDomain>


>My gut reaction is forget about octet handling (for XML data only, steps
>1 and 2) unless we hear that there is a need for it.  If applications need
>the octets for XML data, they can serialize a returned nodeset.
>I'd be glad to hear of reasonable scenarios where octet handling (for XML
>data) is deemed valuable.  Otherwise, I'll probably just stick with my gut

If the processing rules are defined on the basis of nodeset (infoset?),
they will fit in with the existing "decryption transform" well, and so I
like them.  But also how to parse a decrypted XML fragment into a nodeset
has to be defined and it may need a lot of effort...

Tokyo Research Laboratory
IBM Research
Received on Monday, 6 August 2001 11:57:45 UTC

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