W3C home > Mailing lists > Public > w3c-ietf-xmldsig@w3.org > July to September 2011

Re: Canonical XML error

From: Steve DeRose <steve.derose@openamplify.com>
Date: Wed, 07 Sep 2011 12:47:35 -0400
To: Thomas Roessler <tlr@w3.org>
Cc: Frederick.Hirsch@nokia.com, jboyer@PureEdge.com, w3c-ietf-xmldsig@w3.org, public-xmlsec@w3.org, "C. M. Sperberg-McQueen" <cmsmcq@blackmesatech.com>, Henry Thompson <ht@cogsci.ed.ac.uk>, chris lilley <chris@w3.org>
Message-ID: <1315414055.19616.41.camel@sderose-ThinkPad-T400>
*That* solves the problem; sorry I hadn't spotted that. I better go fix
my canonicalizer code!

Thanks!

s

On Wed, 2011-09-07 at 17:16 +0200, Thomas Roessler wrote:
> On 2011-09-07, at 16:24 +0200, Steve DeRose wrote:
> 
> 
> 
> > To include that literal text content, an encoder must "escape" at
> > least one of the 3 characters. Such escaping is obviously possible
> > (if it were not, we would have dealt with it in the XML spec). For
> > example:
> > 
> > 
> >         <p>In XML, the end of a marked section is indicated by
> >         "]]&gt;".</p>
> 
> 
> 
> So, this is a bit hidden, but processing of the string "]]>" when it
> occurs as part of a text node actually is specified and has a
> well-defined processing model:  Canonical XML encodes all ">" signs in
> text nodes as "&gt;".
> 
> 
> See the note about text nodes here:
> http://www.w3.org/TR/xml-c14n11/#ProcessingModel
> 
> 
> 
> 
Received on Wednesday, 7 September 2011 16:48:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 7 September 2011 16:48:10 GMT