Re: XForms 2.0 Draft review: The xforms-script-language-not-supported-exception Event / The xforms-script-exception Event

couldn't come up with a good name at the time, so went for a real bad one, to ensure people will come up with a better name and here we go ;)

Kind regards,

Nick Van den Bleeken
R&D Manager

Phone: +32 3 425 41 02
Office fax: +32 3 821 01 71
nick.van.den.bleeken@inventivegroup.com<mailto:nick.van.den.bleeken@inventivegroup.com>
www.inventivedesigners.com


[cid:image001.png@01CBF2F8.1DA19110][cid:image002.png@01CBF2F8.1DA19110][cid:image003.png@01CBF2F8.1DA19110]

On 30 Jan 2013, at 19:53, Erik Bruchez <erik@bruchez.org<mailto:erik@bruchez.org>> wrote:

+1, the event name is ugly enough to be a bad idea!

Agreed with the need for harmonization.

-Erik

On Wed, Jan 30, 2013 at 12:48 AM, Ulrich Nicolas Lissé
<unlisse@gmail.com<mailto:unlisse@gmail.com>> wrote:
Dear Group,

the http://www.w3.org/MarkUp/Forms/wiki/XForms_2.0#The_xforms-script-language-not-supported-exception_Event
Event has a horrible name. That said I would like to question wether
we need this event at all. The occurrence of an unsupported script
language could as well be indicated by an
http://www.w3.org/MarkUp/Forms/wiki/XForms_2.0#The_xforms-script-exception_Event
Event. The "language" property should be added to this event then.

Related: The xforms-script-exception Event has an "error" property,
the xforms-compute-exception Event has an "error-message" property and
the xforms-version-exception Event has an "error-information"
property. To add confusion, the xforms-binding-exception Event has no
error properties while xforms-submit-error has an "error-type"
property. This is inconsistent and should be harmonized.

Regards,
Uli.
--
Ulrich Nicolas Lissé







________________________________

Inventive Designers' Email Disclaimer:
http://www.inventivedesigners.com/email-disclaimer

Received on Friday, 1 February 2013 08:34:05 UTC