- From: Ignatius Feng <Ignatius.Feng@healthlink.net>
- Date: Wed, 30 Jul 2003 10:02:34 +1200
- To: "Joseph Reagle" <reagle@w3.org>
- Cc: <xml-encryption@w3.org>
Hi Joseph, Thank you very much for clarifying. Ignatius -----Original Message----- From: Joseph Reagle [mailto:reagle@w3.org] Sent: Wednesday, 30 July 2003 1:32 a.m. To: Ignatius Feng Cc: xml-encryption@w3.org Subject: Re: a question regarding section "http://www.w3.org/TR/xmlenc-core/#sec-Serializing-XML" On Monday 28 July 2003 19:51, Ignatius Feng wrote: > it seems > that the output of canonicalization of <Document > xmlns="http://example.org/"> > <ToBeEncrypted xmlns="" /> > </Document> > should already include the xmlns="" as follows: > <Document xmlns="http://example.org/"> > <ToBeEncrypted xmlns=""><ToBeEncrypted> > </Document> Hi Ignatius, the tricky bit here is that it's *not* the Document element that is being canonicalized, because it is *not* the Document element being encrypted. Instead, it is the fragment ToBeEncrypted that is being encrypted and consequently isolated from its context and canonicalized. When you isolate ToBeEncrypted from its context the canonicalization will not emit the xmlns="" because as far as it's concerned, ToBeEncrypted is the root element and there's no context to "over-ride". --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.504 / Virus Database: 302 - Release Date: 24/07/2003 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.504 / Virus Database: 302 - Release Date: 24/07/2003
Received on Tuesday, 29 July 2003 18:02:43 UTC