Re: [Tzdist] Fwd: [tzdist] #32 (service): managing historical data

[Lester Caine <[e-mail]>]

On 11/12/14 18:11, Cyrus Daboo wrote:
> Note, that even what I describe above is problematic because few, if
> any, calendar clients actually have a concept of what time zone a user
> is likely to be in at some particular point in the future. Most clients
> allow users to change the "view" time zone to view events relative to a
> specific zone, but they don't let you say "next week I will be in
> London, so use Europe/London when viewing any of the days next week).
> Ultimately clients may do something like that if they need to fix these
> types of problem.

Calendaring systems still do not cover cross timezone activities well,
and I don't think iCalendar is particularly friendly in solving the
problems that need to be handled? For genealogical data we often flag a
time range covering the uncertainty in when an event happened so that
when time lining events one can see if something could have been
concurrent which can then can be researched in further detail. While
planning new events where a site may have a variation of local offset it
would be useful that the tzdist data actually flagged that there is
uncertainty in a forthcoming event if only to allow an organiser to
block bookings on that day or period. Often the organisers have no
understanding that these events may happen, so in addition to cleanly
publishing a short notice change, publishing a potential race problem is
an equally valid objective?

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk