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

Re: Section 4.1 and 4.2 proposal

From: <edsimon@xmlsec.com>
Date: Wed, 8 Aug 2001 08:16:59 -0400
Message-ID: <3B708CFA000001BE@mail.san.yahoo.com>
To: Takeshi Imamura <IMAMU@jp.ibm.com>, Blair Dillaway <blaird@microsoft.com>
Cc: Joseph M. Reagle Jr. <reagle@w3.org>, XML Encryption WG <xml-encryption@w3.org>
Blair, I agree that your text looks great.  

Regarding Takeshi's comment on step 4 of decryption, perhaps the text would
be clearer if it was slightly reordered like this:

<new>
c. The Decryptor may support the ability to replace the
EncryptedData element with the decrypted Element or Content XML
(RECOMMENDED). In this case, the Decryptor does the following steps: 

1. Convert the XML source string to the character encoding of the
containing XML document (not necessary, of course, if the containing 
document is encoded in UTF-8).  

2. Parse the XML source string to obtain a node list.  

3. If the Type was Element, the node list will have exactly one top-level
Element.  Replace the EncryptedData element with the decrypted Element.
  
   If the Type was Content, the node list may have one or more top-level
nodes
including CDATA, Element, ProcessingInstructions, and Comment nodes.  In
this case remove the EncryptedData element and insert the nodes in the 
decrypted node list as children of the EncryptedData's parent element.
</new>
Ed


>
>>    4.  Decrypting data whose Type is [XML <> ] Element
>><http://www.w3.org/TR/2000/REC-xml-20001006>  or [XML <> ] element
>>Content <http://www.w3.org/TR/2000/REC-xml-20001006>
>>...
>>         c. The Decryptor may support the ability to replace the
>>EncryptedData element with the decrypted Element or Content XML
>>(RECOMMENDED). In this case, the Decryptor parses the XML source string
>>to obtain a NodeList.  If the Type was Element, this will have exactly
>>one top-level Element which replaces the EncryptedData element.  If the
>>Type was Content, the NodeList may have one or more top-level nodes
>>including CDATA, Element, ProcessingInstructions, and Comment nodes. 
In
>>this case the EncryptedData element is removed and the nodes in the
>>NodeList inserted as children of the EncryptedData's parent element.
>>When replacing the EncryptedData elements, it may be necessary to
>>transform the encoding of the inserted nodes from UTF-8 to the character
>>encoding of the containing XML Document.
>
>Sorry, I don't follow this step.  It seems node-based and octet-based
>processings are mixed up.  Which processing do you intend?
>

-----------------------------------------------------------------------------------------------
Ed Simon
XMLsec Inc.

Interested in XML Security Training and Consulting services?  Visit "www.xmlsec.com".
Received on Thursday, 9 August 2001 08:41:17 UTC

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