Re: Do we need an XForms actions module if we switch to XML events 2?

HI all, 

I recall seeing a resolution while I was away to go to XML Events 2 for 
XForms 1.2, but this reverses previous decisions we made about 
modularizing what we have and focusing on stream-lined syntax for web 

It seems problematic to go up a major version number on a baseline 
technology while only going up a minor version number in our own language.

As a result, I thought the actions module would have if, while, and 
event() in them.

A version of that module could be created in which it inherits those 
capabilities from XML Events 2, but that should not prevent the actions 
module from having if, while and events() available, regardless of where 
it gets them from.

It should be possible to use if, while and event() from XForms 1.1 in the 
XForms 1.2 module whether or not you adopt XML Events 2 or stick with the 
current XML Events.  Moreover, even if XForms 1.2 were defined as a 
consuming profile that did import XML Events 2, this would not change the 
point about the actions module, which we are presumably modularizing so 
that it can be used by consuming profiles other than XForms 1.2.  To 
encumber all consuming profiles with adopting XML Events 2 seems 
excessive, particularly since we have already defined all of this without 
using XML Events 2.

John M. Boyer, Ph.D.
Senior Technical Staff Member
Lotus Forms Architect and Researcher
Chair, W3C Forms Working Group
Workplace, Portal and Collaboration Software
IBM Victoria Software Lab

Blog RSS feed:

Erik Bruchez <>
"public-forms (new)" <>
08/12/2008 10:27 AM
Re: Do we need an XForms actions module if we switch to XML events 2?


The event() function is already part of XML Events 2, at least as of 
the 16 February 2007 draft. [1]



On Aug 12, 2008, at 5:55 AM, 

> Hi,
> When doing my action item 'move Actions module for XForms 1.2 to XML 
> Events 2.'  I wasn't sure we need the XForms actions module anymore.
> XML events contains:
>   - the action element
>   - if and while attributes
> It also contains a dipatchEvent element what our dispatch element 
> does, excluding our delay attribute. Shouldn't we use the same 
> element as defined in XML events 2 (if we don't want to change our 
> element name, maybe we should contact the people from XML events 2, 
> and ask them to change it, our spec is already a Public REC). We 
> should also contact them asking to add the delay attribute that we 
> introduced in XForms 1.1.
> So the only missing bit is the event() function which we also could 
> add in one of the XPath functions modules.
> What does everybody think about this?
> Regards,
> Nick Van den Bleeken  -  Research & Development Manager
> Inventive Designers
> Phone: +32 - 3 - 8210170
> Fax: +32 - 3 - 8210171
> Email:
> Inventive Designers' Email Disclaimer:
> -- 
> This message has been scanned for viruses and
> dangerous content, and is believed to be clean.
> -- 

Orbeon Forms - Web Forms for the Enterprise Done the Right Way

Received on Tuesday, 12 August 2008 17:46:00 UTC