Re: PipX, a portable library of XProc pipelines and steps

There's no dedicated place for a general discussion, but you can create
issues on the issue tracker for specific questions or issues:
https://github.com/daisy-consortium/xprocspec/issues

Feel free to create a new thread on xproc-dev.

re: context scope: yes, I considered wrapping the context declaration and
assertions in groups, but that would make it even more verbose. Assertions
(x:expect) currently always refer to their first preceding context
declaration (x:context).


Jostein


On 21 February 2014 14:36, Florent Georges <fgeorges@fgeorges.org> wrote:

> On 21 February 2014 13:24, Jostein Austvik Jacobsen wrote:
>
> > I think it is useful to be able to define a context, rather than
> referring
> > directly to output ports etc. from the assertion element. You often want
> to
> > perform multiple assertions against the same context
>
>   True.  In that case, it would probably make more sense to say:
>
>     <x:context ...>
>        <x:assert-1 .../>
>        <x:assert-2 .../>
>     </x:context>
>
> so that the context scope is well defined.  This thread becomes really
> XProcSpec-oriented.  Is there a dedicated place to discuss it, or
> should we start a new thread on XProc Dev?
>
>   Regards,
>
> --
> Florent Georges
> http://fgeorges.org/
> http://h2oconsulting.be/
>

Received on Friday, 21 February 2014 13:45:26 UTC