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

C14N remark

From: <Toman_Vojtech@emc.com>
Date: Wed, 8 Oct 2008 10:06:24 -0400
Message-ID: <6E216CCE0679B5489A61125D0EFEC7870CECEA31@CORPUSMX10A.corp.emc.com>
To: <public-xml-processing-model-wg@w3.org>

>From the meeting minutes October 2:

>   ... On C14N, we've already discussed this and said it was a
>   option on serialization.
>   Norm: Good point! Thank you, Mohamed.

True, but do we mention this in the spec somewhere? (Perhaps we don't
have to...)

It just occurred to me that having C14N as an option on p:serialization
can make using C14N in XProc quite tedious. Because it is on the
p:serialization level, you can do C14N only in environments where you
actually *serialize* the outputs (p:store or when you run a pipeline in
a shell, for instance). 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.

So, it seems to me that if you want to do something serious with C14N in
XProc, you will have to use some sort of an C14N extension step for

Received on Wednesday, 8 October 2008 14:07:19 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:41:40 UTC