W3C home > Mailing lists > Public > public-xml-processing-model-comments@w3.org > March 2009

RE: Reading p:log output

From: <Toman_Vojtech@emc.com>
Date: Tue, 10 Mar 2009 08:33:32 -0400
Message-ID: <6E216CCE0679B5489A61125D0EFEC7870ED139B3@CORPUSMX10A.corp.emc.com>
To: <public-xml-processing-model-comments@w3.org>
> Consider this pipeline[1]:
> 
> <p:declare-step xmlns:p="http://www.w3.org/ns/xproc"
>                 xmlns:br="http://example.org/br/"
>                 name="main">
> 
>    <p:input port="source">
>      <p:inline>
>        <br:someDocument>
> 	 <br:someContent/>
>        </br:someDocument>
>      </p:inline>
>    </p:input>
> 
>    <p:output port="result">
>      <p:pipe step="lastStep" port="result"/>
>    </p:output>
> 
>     <p:identity>
>       <p:log port="result" href="malformedLogOutput.xml"/>
>     </p:identity>
> 
>     <p:identity name="lastStep">
>       <p:input port="source">
>         <p:document href="malformedLogOutput.xml"/>
>       </p:input>
>     </p:identity>
> 
> </p:declare-step>
> 
> Whether this works or not is, at best, implementation dependent, I
> think. Do we want to say anything more about it?

As for myself, I think we cover this case well enough. But to make
things really clear, we could consider making it more explicit in 5.5
(p:log) that the output of p:log is not only implementation-defined, but
it *may also not be XML at all*.

Another thing: the output of p:log may not be retrievable at all - for
instance when you use some kind of a 'write-only' service that just
stores some records somewhere. You can log to /dev/null as well.

Regards,
Vojtech
Received on Tuesday, 10 March 2009 12:34:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 10 March 2009 12:34:29 GMT