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

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

From: Joseph M. Reagle Jr. <reagle@w3.org>
Date: Fri, 27 Jul 2001 16:47:15 -0400
Message-Id: <4.3.2.7.2.20010727164053.02ed1be8@localhost>
To: "XML Encryption WG " <xml-encryption@w3.org>
I've tried to reflect the decision (but have two questions):

http://www.w3.org/Encryption/2001/Minutes/0720-Redwood/minutes.html#processingRules
>    A Poll was taken of the group on the behaviors. Based on that poll it
>    was determined that:
>     1. Taking in octet and deliver encrypted, take in encrypted and
>        deliver octet is Required.
>     2. Replace and encrypt will be Recommended (optional).

  as follows

http://www.w3.org/Encryption/2001/Drafts/xmlenc-core/
$Revision: 1.29 $ on $Date: 2001/07/27 20:43:17 $
4.2 Decryption
...
  4. If it is an EncryptedData structure and the Type is "Element" or
     "Content", then:
      1. provide the octets to the application (REQUIRED to implement), or
      2. place the resulting octets as characters in place of the
         EncryptedData element with the encoding of the parent XML document
         (RECOMMENDED to implement).
     Else (if not of type "Element" or "Content") provide the octets to the
     application

1. Was our intent to make this distinction upon encryption as well.
2. As written, I know it's wrong in that both are REQUIRED to implement, but 
exactly is the nature of the RECOMMENDED? I think the "or" is sufficient, 
and we needn't speak of required or recommended.


--
Joseph Reagle Jr.                 http://www.w3.org/People/Reagle/
W3C Policy Analyst                mailto:reagle@w3.org
IETF/W3C XML-Signature Co-Chair   http://www.w3.org/Signature
W3C XML Encryption Chair          http://www.w3.org/Encryption/2001/
Received on Friday, 27 July 2001 16:47:16 UTC

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