W3C home > Mailing lists > Public > xproc-dev@w3.org > April 2009

Re: calabash with primary attributes

From: Leif Warner <abimelech@gmail.com>
Date: Tue, 31 Mar 2009 20:27:14 -0700
Message-ID: <54d4ec0f0903312027icbf0eb0u372dd5fa7f08144c@mail.gmail.com>
To: Norman Walsh <ndw@nwalsh.com>
Cc: XProc Dev <xproc-dev@w3.org>
I thought the <p:pipeline/> construct had an automatic "source" port
declared primary, but when I add a secondary input port to it, I find that
Calabash requires it to me marked explicitly with "primary='false' ".

As it is now, Example 2 in the spec (http://www.w3.org/TR/xproc/#ex1-abbr)
does not run for me (on Calabash 0.9.5-ish to 0.9.7), instead giving:

Error  : Pipeline failed: err:XS0030: null  It is a static error to specify
that more than one input port is the primary.

-Leif Warner

On Tue, Mar 31, 2009 at 4:49 AM, Norman Walsh <ndw@nwalsh.com> wrote:

> James Fuller <james.fuller.2007@gmail.com> writes:
> > I guess the question is, can't we augment the algorithm > its trivial
> > either way to implement and I don't see any confusion allowing such.
> I suppose we could, but I think the idea was to keep it simple. If you
> have exactly one port, then it should be primary by default. If you've
> reached a level of complexity where you have multiple input ports, you
> should make it explicit yourself.
> In your example, you could simply say that the source is primary and
> you wouldn't have to say that the extra port was not.
>                                        Be seeing you,
>                                          norm
> --
> Norman Walsh <ndw@nwalsh.com> | One should always be a little
> http://nwalsh.com/            | improbable.--Oscar Wilde
Received on Wednesday, 1 April 2009 03:27:56 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:03:04 UTC