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

Re: Remarks on GeoLocation Spec

From: Doug Turner <doug.turner@gmail.com>
Date: Wed, 9 Jul 2008 18:06:27 -0700
Cc: "Innovimax SARL" <innovimax@gmail.com>, public-geolocation@w3.org
Message-Id: <CCA5ACF0-C30E-41AF-8319-6EDF1DC5AED5@gmail.com>
To: Chris Prince <cprince@google.com>

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.

Doug Turner


On Jul 9, 2008, at 6:03 PM, Chris Prince wrote:

>
> Good catch.  Changing the type of that field to Date makes a lot of  
> sense.
>
> On Wed, Jul 9, 2008 at 2:43 PM, Innovimax SARL <innovimax@gmail.com>  
> wrote:
>> Dear,
>>
>> In
>>
>> Position interface
>>
>>  why is timestamp in milliseconds since midnight on January 1st,  
>> 1970. -->
>>
>> Why isn't it a xs:dateTime ?
>> if not which timezone ?
>>
>> Mohamed ZERGAOUI
>>
>> --
>> Innovimax SARL
>> Consulting, Training & XML Development
>> 9, impasse des Orteaux
>> 75020 Paris
>> Tel : +33 9 52 475787
>> Fax : +33 1 4356 1746
>> http://www.innovimax.fr
>> RCS Paris 488.018.631
>> SARL au capital de 10.000 
>
Received on Thursday, 10 July 2008 01:07:35 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 22 March 2012 18:13:39 GMT