W3C home > Mailing lists > Public > xproc-dev@w3.org > September 2008

Re: possible bug in p:iteration select

From: Norman Walsh <ndw@nwalsh.com>
Date: Tue, 30 Sep 2008 18:00:57 -0400
To: XProc Dev <xproc-dev@w3.org>
Message-ID: <m24p3xnvja.fsf@nwalsh.com>
"Josh Matthews" <joshmatthews@gmail.com> writes:

> On Tue, Sep 30, 2008 at 4:12 PM, Jeni Tennison <jeni@jenitennison.com>wrote:
>
>>
>> If you had a known URI, you'd do:
>>
>>  <p:load>
>>    <p:option name="href" select="'/path/to/file.xml'" />
>>  </p:load>
>>
>
> Shouldn't this (and the original example) use <p:with-option> - I thought
> <p:option> was for option declaration, not invocation?

Yes, you're absolutely right. I haven't assimilated that change yet.
My bad.

> I wonder if it'd be nice if you could also do this:
>
> <p:load>
>    <p:with-option name="href">/path/to/file.xml</p:with-option>
> </p:load>
>
> Not that it's a shorter shortcut than just passing the option directly via
> an actual href attribute, but it would be nicely consistent with XSLT's
> with-param, for those more familiar with that.

Yes, but can't do that because you can also put p:pipe in there to
specify the context and that would just get too confusing.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | The skill of writing is to create a
http://nwalsh.com/            | context in which other people can
                              | think.--Edwin Schlossberg

Received on Tuesday, 30 September 2008 22:01:44 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 30 September 2008 22:01:47 GMT