RE: First shot at ACTION-561 (event context info)

Hi Erik,

Looks good, here is my opinion to your todo's/pending questions:

 - timestamp type: I think the type should be xs:long in XPath 2.0

 - timeStamp : it is indeed a pity that we can't return a xs:dateTime, but this is a limitation due to DOM events, so not much we can do about it. I know that it's cumbersome, but the form author can always convert it to a xs:dateTime if he knows it is milliseconds since Epoch using : xs:dateTime('1970-01-01T00:00:00') + xs:double(text()) * xs:dayTimeDuration('PT0.001S')

 - I think returning the empty sequence/empty string is the correct behavior if no id is available on the target/currentTarget element

 - Camel case names: I think we should use those because these are the names defined in DOM level 2 events (currentTargetId and targetId are good for me).


Regards,

Nick Van den Bleeken
R&D Manager

Phone: +32 3 821 01 70
Office Fax: +32 3 821 01 71
Nick_Van_den_Bleeken@inventivegroup.com
http://www.inventivegroup.com

> -----Original Message-----
> From: public-forms-request@w3.org [mailto:public-forms-request@w3.org]
> On Behalf Of Erik Bruchez
> Sent: woensdag 29 juli 2009 18:50
> To: public-forms@w3.org
> Subject: First shot at ACTION-561 (event context info)
>
> All,
>
> Here is a first shot at describing base event context information. [1]
>
> Feedback welcome.
>
> -Erik
>
> [1] http://www.w3.org/MarkUp/Forms/wiki/EventContextInfo
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> --
>


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

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
--

Received on Thursday, 30 July 2009 06:46:24 UTC