Re: XForms 2.0 and XPath

Hi Leigh,

I am curious as to what other topics it is hampering the discussion of?

Surely it's not the context issue for delete, which is only exacerbated by 
this new feature called iterate but is already a problem in XForms 1.1.

I feel I've been very clear about the fact that this issue exists 
independently of the version of XPath.  The version of XPath makes a minor 
order difference on exactly what happens when a context node is deleted, 
and I think it is perfectly reasonable to have that difference, but 
otherwise the major order issue is deciding whether a deleted node can 
provide context after its deletion. 

Since that topic is unrelated to the version of XPath, maybe we could get 
a list of what other issues are significantly blocked by the version of 
XPath. 

Thanks,
John M. Boyer, Ph.D.
Distinguished Engineer, IBM Forms and Smarter Web Applications
IBM Canada Software Lab, Victoria
E-Mail: boyerj@ca.ibm.com 

Blog: http://www.ibm.com/developerworks/blogs/page/JohnBoyer
Blog RSS feed: 
http://www.ibm.com/developerworks/blogs/rss/JohnBoyer?flavor=rssdw





From:   Leigh L Klotz Jr <leigh.klotz@xerox.com>
To:     public-forms@w3.org
Date:   02/12/2011 10:43 AM
Subject:        Re: XForms 2.0 and XPath



Sorry, "behavior of XForms 2.0 with XPath 1.0."
On 12/02/2011 10:37 AM, Leigh L Klotz Jr wrote: 
I propose that we drop XPath 1.0 from the XForms 2.0 specification.   An 
XForms 2.0 processor can certainly support XPath 1.0 in its XForms 1.1 
mode, but I believe we should expend no more group effort describing the 
behavior of XForms 2.0 with XForms 1.1. 
We have enough work to get XForms 2.0 out the door, and XPath 2.0 became 
a W3C Recommendation in 2007. 
We've worked out a lot of the practical issues of supporting XPath 1.0 
with XForms 2.0, but the spec-level precision necessary makes for some 
uncomfortable sections and restrictions, and is currently hampering 
discussion on other topics. 
Leigh.