The definition of Event.timeStamp is currently:

  Used to specify the time at which the event was created in
  milliseconds relative to 1970-01-01T00:00:00Z. Due to the fact that
  some systems may not provide this information the value of timeStamp
  may be not available for all events. When not available, the value
  shall be 0.

I think we should remove the allowance for implementations to have
Event.timeStamp be 0.  It might be that implementations are running on
systems that don’t know what the actual time is, but surely JS Date is
returning something; I think it would be fine for those implementations
to assume a particular time on startup, for example.

I don’t think we need to worry about implementations that can’t even
track the progress of time.

I also think we should make Event.timeStamp be not the time at which the
event was created (the construction of the Event object?) but the time
at which the event represented by the Event object occurred.  For user
created events, we could have it be either the time that createEvent()
is called or the time that initEvent() is called (since timeStamp is
read only).

Cameron McCormack ≝ http://mcc.id.au/

Received on Tuesday, 19 October 2010 02:42:11 UTC