Rob Seaman sea...@noao.edu wrote:
In an earlier message I also said:
Scheduling software does a pretty good job of supporting the range of
timezones and DST rules (presumably layered on Olson), except for
educating the users who often forget during changeover that Arizona
and Hawaii, in
Rob Seaman said:
You've imposed the additional requirement that you can't have a primary
timezone, for political reasons.
Requirements are discovered, not imposed.
This from the person who insists that a priori civil time must synchronize
with the sun?
--
Clive D.W. Feather | If
Almost overlooked this one! That would never do...
Clive D.W. Feather wrote:
Rob Seaman said:
Requirements are discovered, not imposed.
This from the person who insists that a priori civil time must synchronize
with the sun?
Rather, it is ITU-R Study Group 7 that has insisted on a
On 25 Jan 2012 at 12:05, Rob Seaman wrote:
I don't recall saying any such thing. The original reply was to
this comment from Daniel R. Tobias:
Usually such events are only fixed relative to local civil
time in the place where the event is to take place...
I was pointing out that in
Rob Seaman sea...@noao.edu wrote:
The way to deal with multi-location metings is to choose a primary
location, then it it obvious what will happen when TZ rules change.
Interesting. Immediately after that I said:
Whatever our individual positions on the issues, they will be better
On 1/25/2012 8:40 AM, Tony Finch explained it would be desirable to store
information about events that are to be observed in local civil time as a
local time and a location, so that the time zone could be looked up close
to the time of the event, and thereby avoid reliance on stale time zone
Gerard Ashton ashto...@comcast.net wrote:
This suggest a desire for an algorithm that accepts as input a latitude
and longitude of a point of interest, and a set of boundaries, and
determines which of the regions the point of interest falls in. Does
anyone know of such an algorithm?
I
Tony Finch wrote:
You'll have to explain why you think videoconferencing breaks the Olson
timezone database to me, because I don't get it.
I don't recall saying any such thing. The original reply was to this comment
from Daniel R. Tobias:
Usually such events are only fixed relative to
On 25 Jan 2012, at 19:05, Rob Seaman sea...@noao.edu wrote:
Tony Finch wrote:
You'll have to explain why you think videoconferencing breaks the Olson
timezone database to me, because I don't get it.
I don't recall saying any such thing.
I said:
Displaying the time correctly for
Ian Batten wrote:
You've imposed the additional requirement that you can't have a primary
timezone, for political reasons.
Requirements are discovered, not imposed.
That's not an engineering requirement, or at least, it's a constraint more
easily solved by sacking people than dreaming up
Tony Finch wrote:
Rob Seaman wrote:
Virtually all of our meetings take place in more than one place since we
have sites in Arizona and Chile, Corporate HQ in DC, partners in
California and Hawaii (and a dozen other places). I imagine this is not
atypical these days. Scheduling changes
11 matches
Mail list logo
