W3C home > Mailing lists > Public > www-forms@w3.org > December 2006

If function

From: Klotz, Leigh <Leigh.Klotz@xerox.com>
Date: Fri, 15 Dec 2006 17:15:05 -0800
Message-ID: <E254B0A7E0268949ABFE5EA97B7D0CF402962CF2@usa7061ms01.na.xerox.net>
To: <www-forms@w3.org>

Below are comments from Michael Kay on the tail end of a discussion of
the boolean and control operators.
Dr. Kay made these suggestions about the avoiding future conflict
between XForms 1.0 if(0 and XPath 2.0 if().
I believe we should consider these options for XForms 1.1.

Furthermore, he made some comments about namespaces prefixes on XPath
functions in general; interested readers should consult the xml-dev
archives.

Leigh. 

-----Original Message-----
From: Michael Kay [mailto:mike@saxonica.com] 
Sent: Friday, December 15, 2006 5:10 PM
To: Klotz, Leigh; 'Rick Marshall'
Cc: 'Ken North'; xml-dev@lists.xml.org
Subject: RE: [xml-dev] XML design of ((a and b) or c)

 
> Personally, I would welcome any helpful suggestions you have 
> about upward compatibility, with XForms 1.1 and with XPath 2.0.

I think one useful idea would be to enable a function prefix (or absence
of
a prefix) to be bound essentially to a search path containing multiple
namespaces. The WG rejected this notion when I proposed it, but that's
because I presented it badly. In fact I think it's currently legal: we
don't
constrain how you build a library of functions and assign them to a
namespace, and one way of doing it is to assemble a new namespace from
multiple existing namespaces with a priority rule for resolving any
clashes:
a sort of "virtual function namespace". That mechanism would allow you
to
put the XForms functions in a separate namespace and then allow the user
to
bind a prefix to a URI that identifies a search path containing first
the
XForms functions and then the XPath 2.0 functions.

That leaves "if", which is a nasty problem. Technically you can probably
disambiguate the XForms function from the XPath 2.0 conditional
expression
by lookahead based on the presence of "then" after the ")", but that's
difficult to specify, and adds yet another nasty glitch to XPath
parsing.
Orbeon Forms has this problem because it already uses XPath 2.0, and I
think
it simply forces the user to prefix the "if" function.

Michael Kay
http://www.saxonica.com/
Received on Saturday, 16 December 2006 01:15:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 10 March 2012 06:22:08 GMT