At 11:46 6/14/2001, Blair Dillaway wrote: >I am open to adopting this interpretation. But I don't find the wording >in draft specs clearly indicate what should happen when the type is >Element, Content, or some non-XML external data. We should also cover >XML Document since this can't generally be inserted in place of the >EncrytpedData element. Blair, 4.2.4 states: >If it is an EncryptedData structure and the type is "Element" or "Content", >then place the resulting characters in place of the EncryptedData element >with the encoding of the parent XML document if necessary. Otherwise, the >octet sequence is the final result. What would you suggest to make it more clear? -- 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 Monday, 18 June 2001 13:20:41 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 08:42:19 GMT