[Spaceapi-devel] Specify a time zone for state.lastchange

[nog3]

I'd like to see a timezone offset field too, though our state is UTC+10 but
doesn't do daylight saving. So I can forsee this adding interesting issues.


On Mon, Jun 2, 2014 at 7:07 PM, Sebastian Mai <bastinat0r at bastinat0r.de>
wrote:

>
> For my Spacestatus App[1] I thought about times zones as well – it would be
> neat to be able to compare different spaces as to whether they are more
> day- or
> night active – and that wont work with locale time (currently I just use
> the
> browser default).
>
> > I noticed that the last change time is given on this site with a time
> > zone. However, the SpaceAPI specs don't mention any time zone for the
> > state.lastchange field. The site seems to interpret this value as UTC,
> > which makes most sense to me; so we should probably also specify this
> > field to be UTC.
> Yes!
>
> > One could argue that the endpoint's local time is a also valid time zone
> > for this field, but for global evaluation there would be the additional
> > need to know the local time zone as well, which probably changes more
> > often than one might think.
>
> Maybe there could be an optional(?) field for the timezone offset so apps
> are
> able to use the correct local time in the next api-version.
>
> Greetings
> Basti
>
> [1] http://spacestatus.bastinat0r.de
> _______________________________________________
> Spaceapi-devel mailing list
> Spaceapi-devel at lists.hackerspaces.org
> http://lists.hackerspaces.org/mailman/listinfo/spaceapi-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hackerspaces.org/pipermail/spaceapi-devel/attachments/20140602/a04dcb4b/attachment.html>