W3C home > Mailing lists > Public > public-geolocation@w3.org > July 2008

Re: Remarks on GeoLocation Spec

From: Doug Schepers <schepers@w3.org>
Date: Wed, 09 Jul 2008 21:52:45 -0400
Message-ID: <48756B6D.7050807@w3.org>
To: public-geolocation@w3.org

Hi, Doug-

Doug Turner wrote (on 7/9/08 9:06 PM):
> Keeping it milliseconds matches the timestamp of the mouse event:
> timeStamp of type DOMTimeStamp, readonly
>     Used to specify the time (in milliseconds relative to the epoch) at 
> which the event was created. 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, a value of 0 will be returned. Examples 
> of epoch time are the time of the system start or 0:0:0 UTC 1st January 
> 1970.
> I think we should be consistent here.

I agree that consistency is a good general goal, but only when the 
conditions and needs are the same.  It's unlikely that an author will 
need to use the same code for mouse event timestamps as for a date of a 
geolocation timestamp, which seems like it would benefit from more 

This being a geolocation API introduces both an opportunity and an 
obligation to deal with dates in a sophisticated manner.  DOMTimeStamp 
is simply not as expressive as xs:dateTime.

-Doug Schepers
W3C Team Contact, WebApps, SVG, and CDF
Received on Thursday, 10 July 2008 01:53:19 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:50:51 UTC