W3C home > Mailing lists > Public > public-xmlsec@w3.org > June 2010

Proposed resolution for LC-2386

From: <Frederick.Hirsch@nokia.com>
Date: Tue, 1 Jun 2010 14:55:25 +0200
To: <public-xmlsec@w3.org>
CC: <Frederick.Hirsch@nokia.com>
Message-ID: <2AEC3834-F2CE-4E53-93D3-57638FC9F2EC@nokia.com>
Proposed resolution for LC-2386

http://www.w3.org/2006/02/lc-comments-tracker/42458/WD-xmlenc-core1-20100513/

Add to end of section  2.1.4, http://www.w3.org/TR/2010/WD-xmlenc-core1-20100513/#sec-eg-Arbitrary-Data :

[[

Where appropriate, such as in the case of encrypting an entire EXI stream, the Type attribute may be provided and the Mime type adjusted appropriately, as in the following EXI encryption example:

  <?xml version='1.0'?> 
  <EncryptedData xmlns='http://www.w3.org/2001/04/xmlenc#'
   Type='http://www.w3.org/2009/xmlenc11#EXI'
   MimeType='application/exi'>
    <CipherData>
      <CipherValue>A23B45C56</CipherValue>
    </CipherData>
  </EncryptedData>

]]

Note that in the response to this comment we should emphasize that the Type attribute needs to be used.

In looking at this I noted a potential new issue, that in section 3.1 (Encrypted Type element, http://www.w3.org/TR/2010/WD-xmlenc-core1-20100513/#sec-EncryptedType )
it might be misleading to refer to

 [[ contains data of Type 'EXI', ]] 

and that it might be clearer to state

[[ contains data of Type 'http://www.w3.org/2009/xmlenc11#EXI', ]]


Comment on the proposal for 2.1.4 and the suggestion for 3.1?

Thanks

regards, Frederick

Frederick Hirsch
Nokia
Received on Tuesday, 1 June 2010 12:56:38 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 1 June 2010 12:56:39 GMT