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

Re: Relationship between @xpath-version and p:system-property('p:xpath-version')

From: Norman Walsh <ndw@nwalsh.com>
Date: Thu, 22 May 2008 13:49:51 -0400
To: public-xml-processing-model-wg@w3.org
Message-ID: <m24p8q5iv4.fsf@nwalsh.com>
/ Toman_Vojtech@emc.com was heard to say:
| what are the values of the 'xpath' option that will be passed to the
| steps? Is p:xpath-version sensitive to @xpath-version in the step
| declaration, or does it contain the default XPath version supported by
| the XProc processor? I would prefer the latter, otherwise things may
| become too complex/unclear.

It contains the version that the processor is using for this entire
pipeline. I expect that an implementation will always return either
1.0 or 2.0, depending on what they support. But if they can support
both, I think they should make that decision on a per-run basis, not a
per-step basis.

| Just thinking: Wouldn't it make sense to have an XPath extension
| function p:xpath-version-supported(version), similarly to
| p:psvi-supported()? Some of the processors will support only XPath 1.0,
| some 2.0, but not necessarily 1.0, etc., so perhaps it could be useful
| to have access to this information in the pipeline.

I thought the resolution from last Thursday used only the system
property, I thought p:psvi-supported() whent away? I've never
understood how the system property and the function would ever be
different.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | There is something fundamentally wrong
http://nwalsh.com/            | with treating the earth as if it were a
                              | business in liquidation.--Herman Daly

Received on Thursday, 22 May 2008 17:50:37 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 22 May 2008 17:50:37 GMT