W3C home > Mailing lists > Public > public-forms@w3.org > October 2013

Re: Checking if an extension function exists and implementation/version sniffing

From: Erik Bruchez <erik@bruchez.org>
Date: Tue, 1 Oct 2013 14:07:29 -0700
Message-ID: <CAAc0PEVQ4o9r4B=VSL9HmR=fQODvUPFLFKfH2JRBR=P=hNtCsA@mail.gmail.com>
To: Eric van der Vlist <vdv@dyomedea.com>
Cc: "public-xformsusers@w3.org" <public-xformsusers@w3.org>, public-forms@w3.org
Eric,

We discussed this during our last XForms call.

We discussed two solutions:

1. Import the XSLT 2 function-available() function:

http://www.w3.org/TR/xslt20/#function-function-available

Note that XPath 3 now has function-lookup(), but this cannot be used
with XPath 2 as this requires support for function() items:

http://www.w3.org/TR/2013/CR-xpath-functions-30-20130108/#func-function-lookup

2. Improved error handling in XForms

This is a separate but related topic. XPath and action errors should
be, at least optionally, recoverable. This way, if you have a an error
in an action which uses an unknown function, you could recover from
that, and deduct that there was an issue with an XPath expression.

#1 would be easy, both at the spec level and for implementors. This
would also be the most direct solutions to your requirement.

#2 is more involved, but also more useful, and a more indirect way,
and solves in general a slightly different problem.

My proposal would be to do both for XForms 2.0. I have an action item
to make a proposal for improved error handling already.

Please let us know if you have any comments on this!

-Erik
Received on Tuesday, 1 October 2013 21:15:58 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:14:09 UTC