W3C home > Mailing lists > Public > public-xml-processing-model-wg@w3.org > October 2008

RE: C14N remark

From: <Toman_Vojtech@emc.com>
Date: Thu, 9 Oct 2008 03:02:18 -0400
Message-ID: <6E216CCE0679B5489A61125D0EFEC7870CECEFA1@CORPUSMX10A.corp.emc.com>
To: <public-xml-processing-model-wg@w3.org>

> But C14N is defined to produce a sequence of characters. I don't think
> it's meaningful to speak of a C14N infoset.
> > But if you want to do C14N in step A and then
> > pass its (canonicalized) output to step B, you are in 
> trouble. You will
> > have to run step A, store its result (with C14N turned on) to an
> > external location, and let step B read the data from there. Not very
> > nice nor reliable, I think.
> Doesn't
>   <p:wrap wrapper="c14n-content" match="/*"/>
>   <p:escape-markup method="p:c14n"/>
> do what you want? That will return a <c14n-content> document that
> contains a single text node which is the C14N'd characters.

I think both you and Mohamed are right in your answers, I guess was off
the trail here.

Received on Thursday, 9 October 2008 07:03:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 9 October 2008 07:03:12 GMT