On 5 Feb 2015, at 14:09, Poul-Henning Kamp p...@phk.freebsd.dk wrote:
I think the dialog shows one thing clearly: The UK's historical
zero offset from UTC has made it very hard for them to generalize
that this is not a law of nature.
It is certainly clear that very few
On 6 Feb 2015, at 02:18, Tom Van Baak t...@leapsecond.com wrote:
Many aspects of local time or civil time are left to common
practice which is not good enough to expect uniform inter-operable
implementations.
Brooks, can you give some examples?
An obvious example is the UK. Our legal
Ian Batten via LEAPSECS leapsecs@leapsecond.com wrote:
An obvious example is the UK. Our legal time is GMT with DST, usually taken
to be
UT1 with DST. Our de facto civil time is UTC with DST, and over the years
this
has become more and more ingrained (the Greenwich pips on the hour on
On 9 Feb 2015, at 12:43, Tony Finch d...@dotat.at wrote:
Ian Batten via LEAPSECS leapsecs@leapsecond.com wrote:
An obvious example is the UK. Our legal time is GMT with DST, usually taken
to be
UT1 with DST. Our de facto civil time is UTC with DST, and over the years
this
has
Kevin Birth kevin.bi...@qc.cuny.edu wrote:
In my view, in a strictly Biblical perspective, the problem is with mean
time not with leap seconds.
I tend to go further and argue that people don't like to base their days
on noon. DST is a bodge to recover a bit of seasonal movement to follow
Hi Tom,
On 2015-02-05 09:18 PM, Tom Van Baak wrote:
Many aspects of local time or civil time are left to common
practice which is not good enough to expect uniform inter-operable
implementations.
Brooks, can you give some examples?
I'm not sure what examples you mean, but perhaps comparing
In message 20150206023406.ga10...@ucolick.org, Steve Allen writes:
doesn't address the elephant in the room - local time.
It is all too common to find situations where it is difficult to
ascertain who has authority, over what geographic region, and what
exactly they are trying to say.
I've looked at the report and it is bad social science. The protocols are
too leading to provide reliable information. Basically, from a
methodological perspective, the deck was stacked in this research to
ensure the results it obtained.
That said, the report does reflect a dominant opinion of
I think the dialog shows one thing clearly: The UK's historical
zero offset from UTC has made it very hard for them to generalize
that this is not a law of nature.
It is certainly clear that very few involved realized that UK could
run on a non-zero UTC offset, without any more harm to
On 2/5/15 9:09 AM, Poul-Henning Kamp p...@phk.freebsd.dk wrote:
I wonder how different the outcome of the dialog would have been,
if they had been told that leap seconds would happen at 8 or 9am
on any day of the week, ie: during the busiest hour of traffic,
on roads, rails and in the air ?
@leapsecond.commailto:leapsecs@leapsecond.com
Subject: Re: [LEAPSECS] final report of the UK leap seconds dialog
I trust Kevin Birth. Without questioning the efforts of the stakeholders such
as Peter Vince to be impartial, it is well known that there are dozens of ways
a person makes his opinions known inadvertently
Hello Kevin.
The information specifying that for Japan the next Leap Second will be
applied Wednesday, July 1, at 9:00. is interesting in that this is the
first official policy on when the Leap second shall be applied to a
local timescale. Maybe I have been looking in teh wrong places.
This
seconds had large costs, they would have
gone his way.
From: Kevin Birth kevin.bi...@qc.cuny.edu
To: Leap Second Discussion List leapsecs@leapsecond.com
Sent: Thursday, February 5, 2015 9:06 AM
Subject: Re: [LEAPSECS] final report of the UK leap seconds dialog
I've looked at the report
The leap second happens world wide in UTC at 23:59:60. Since all time zones
follow UTC,
it is whatever time that is offset from UTC. Otherwise, the offset would no
longer be fixed,
but variable for a few hours. While there isn’t a standard for this, I believe
it follows trivially
from the
To: stephensc...@videotron.ca; Leap Second Discussion List
Subject: Re: [LEAPSECS] final report of the UK leap seconds dialog
The leap second happens world wide in UTC at 23:59:60. Since all time zones
follow UTC,
it is whatever time that is offset from UTC. Otherwise, the offset would no
longer be fixed
] final report of the UK leap seconds dialog
The leap second happens world wide in UTC at 23:59:60. Since all time zones
follow UTC,
it is whatever time that is offset from UTC. Otherwise, the offset would no
longer be fixed,
but variable for a few hours. While there isn’t a standard for this, I
,
however, a June leap second occurs just before 5 PM PDT (UTC-7) and just before
4 PM PST (UTC-8) if December.
/tvb
- Original Message -
From: Stephen Scott
To: leapsecs@leapsecond.com
Sent: Thursday, February 05, 2015 1:37 PM
Subject: Re: [LEAPSECS] final report of the UK leap seconds
Many aspects of local time or civil time are left to common
practice which is not good enough to expect uniform inter-operable
implementations.
Brooks, can you give some examples?
We here concentrate on discussions of UTC and Leap
Seconds, which is foundational, yet obviously local time
Watching the video interviews on that site, with the members of the public,
I was disappointed that most of them seemed unaware of any technical
problems the leap-seconds cause. I think the team running those sessions
did the whole idea a dis-service by not making those problems clearer :-(
On 5
Rob Seaman sea...@noao.edu wrote:
|Dr. Birth gave two excellent presentations at the 2013 Charlottesville \
|colloquium, “Requirements for UTC and Civil Timekeeping on Earth”:
|
| http://futureofutc.org/preprints/files/30_AAS%2013-516_Birth.pdf *
What these methods reveal is that the
On 2015-02-05 11:16, Peter Vince wrote:
Yes, I took part in the initial meeting of professionals (so-called
stakeholders), where the issues were indeed thoroughly discussed, and well
understood (apart from some unfortunate absences - no-one from the military was
there, for example).
21 matches
Mail list logo