- From: Christian Geuer-Pollmann <geuer-pollmann@nue.et-inf.uni-siegen.de>
- Date: Mon, 10 Dec 2001 13:13:17 +0100
- To: reagle@w3.org
- Cc: XML Encryption WG <xml-encryption@w3.org>
Hi Joseph, hope it's not too late ;-) http://www.w3.org/Encryption/2001/Drafts/xmlenc-core/ $Revision: 1.84 $ on $Date: 2001/12/06 16:48:55 $ First of all, in "section 3.1" and "section 4.1 point 3.1" a quote is (probably) wrong: 'element' or element 'content' should be 'element' or 'element content' OR it should read 'element' or 'content' ------------------------------------- In "section 4.1 point 3.1", the last sentence is correct but reads a little bit bad. I would end the sentence: "If the encryptor does not serialize, then the application MUST perform the serialization." ------------------------------------- I would add the following as a note to section 4.1 bullet 5.1: <EXISTING_TEXT>The application MAY use this as the top-level element in a new XML document or insert it into another XML document. </EXISTING_TEXT> <P>Note: If the <CODE>EncryptedData</CODE> element is used as the root element of a new document, the <STRONG>encryptor</STRONG> MUST ensure that the Type is not element '<A href="http://www.w3.org/TR/2000/REC-xml-20001006#NT-content">content</A>'. Otherwise <A HREF="http://www.w3.org/TR/2000/REC-xml-20001006#dt-wellformed">well-formed ness</A> would be broken after decryption. </P> Thanks, Christian > Hi Christian, wonder what the status of this was? > > ---------- Forwarded Message ---------- > > As requested in [1], could Christian to propose some text where he thinks > this is weak in the spec.
Received on Monday, 10 December 2001 07:10:31 UTC