W3C home > Mailing lists > Public > public-forms@w3.org > August 2008

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

From: Ulrich Nicolas Lissť <unl@dreamlab.net>
Date: Tue, 12 Aug 2008 16:27:37 +0200
Message-ID: <48A19DD9.30603@dreamlab.net>
To: Nick_Van_den_Bleeken@inventivegroup.com
CC: public-forms <public-forms@w3.org>, public-xhtml2@w3.org

Nick,

did you miss http://www.w3.org/TR/xml-events2/#xpath-event-function ? So 
the event() function is already there.

I wondered about the naming scheme in XML Events 2, too. It's not only 
the dispatchEvent element (and the missing delay attribute) but there is 
also @raise instead of @name and @destid instead of @target. Furthermore 
there is @declare on the action element which I do not really understand.

Since the XML Events is modeled after DOM Events and uses the IDL's 
method names, I don't understand why the attribute names do not resemble 
the method's parameters names like they do on other elements. Mark, can 
you shed some light on this?

For most consistency I'd suggest to rename some attributes in XML Events 2:

* dispatchEvent/@raise -> dispatchEvent/@event

The verb raise is misleading. A normal developer would associate an 
exception rather than an event. I think it should be named event for 
consistency with action, addEventListener, removeEventListener, 
stopPropagation, preventDefault. Other options would be name (like in 
XForms) or type (like in DOM Events).

* dispatchEvent/@destid -> dispatchEvent/@target

I think destid is a comparably poor naming choice. It contains an 
abbreviation, a redundant id, and does not follow the usual naming scheme.

* action/@targetid -> action/@target

See above.

When these naming issues are resolved, I'd like to drop the XForms 
Action module.

Regards,
Uli.

Nick_Van_den_Bleeken@inventivegroup.com wrote:
> 
> 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: Nick_Van_den_Bleeken@inventivegroup.com
> 
> Inventive Designers' Email Disclaimer:
> http://www.inventivedesigners.com/email-disclaimer
> 
> 
> -- 
> This message has been scanned for viruses and
> dangerous content, and is believed to be clean.
> -- 
> 

-- 
Ulrich Nicolas Lissť
Received on Tuesday, 12 August 2008 14:28:33 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 October 2013 22:06:48 UTC