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

p:log feels clunky

From: James Fuller <james.fuller.2007@gmail.com>
Date: Sun, 17 Feb 2008 01:03:58 +0100
Message-ID: <a0ad8ffe0802161603k17963df6p220e49db827f34f2@mail.gmail.com>
To: public-xml-processing-model-comments@w3.org

Hello,

It seems clunky to have a sibling element to control logging behavior
over p:output / p:input;

* makes refactoring port names more difficult, e.g. change on
input/output means change in p:log

* its restricted just to input/outputs, I would like to see the output
at some 'out of band' point

I would propose something a bit more all encompassing, e.g. a p:log
attribute which could be placed on steps, inputs/outputs, and/or other
xproc elements

some examples;

<p:group log="href">
   ....
</p:group>

<p:choose log="href">
...
</p:choose>

<p:declare-step log="href">
....
</p:declare-step>

and of course input/output

<p:input log=""/>

we may even want to place these global type attributes in a different
namespace ?

no conviction here for this, but it becomes apparent in implementation
that p:log is a bit limited and an exetension attribute becomes
useful.

cheers, Jim Fuller
Received on Sunday, 17 February 2008 00:04:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 17 February 2008 00:04:22 GMT