RE: Minor comments on Section 4

I concur with Takeshi's suggested corrections and Ed's proposed wording change in Section 4.1 Step 3.1.  I also like the explicit definitions of application, encryptor and decryptor.  This will likely help out external folks reading this for the first time.

The only possible issue I can see with the current Step 3 text is that we're explicit the Application is responsible for serializing the data if not Element or Content, while we're ambiguous in Step 3.1 about who is responsible for serializing the data.

Since the there is no serialization algorithm the Encryptor must implement, its implicit the Application must be prepared to handle this.  We could make this explicit while also noting the Encryptor might supply a serialization algorithm to address other comments that have been made.

How about something along the lines of:

3.1 If the data is an [ XML] Element or [ XML] Element Content, obtain the octets by serializing the data in UTF-8 as specified in [ XML]. The Application must be prepared to perform this serialization since Encryptors are not required to implement this functionality.  Of course, if the Encryptor implements an optional serialization algorithm the Application could take advantage of it.

Blair

-----Original Message-----
From: Joseph Reagle [mailto:reagle@w3.org] 
Sent: Wednesday, September 19, 2001 12:47 PM
To: edsimon@xmlsec.com; Takeshi Imamura; xml-encryption@w3.org
Subject: Re: Minor comments on Section 4


On Wednesday 19 September 2001 09:49, edsimon@xmlsec.com wrote:
>  I don't see this as "inconsistent and awkward".

Ok, I just took a stab at making things a little more explicit to check our 
understanding (though I might tone down the bold'ed roles once we are 
satisfied).

[
http://www.w3.o rg/Encryption/2001/Drafts/xmlenc-core/#sec-Processing
$Revision: 1.53 $ on $Date: 2001/09/19 19:45:11 $
]

Received on Wednesday, 19 September 2001 17:10:18 UTC