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

Lester Caine <lester@lsces.co.uk> Thu, 11 December 2014 21:32 UTC

Return-Path: <lester@lsces.co.uk>
X-Original-To: tzdist@ietfa.amsl.com
Delivered-To: tzdist@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 117C51A07BD for <tzdist@ietfa.amsl.com>; Thu, 11 Dec 2014 13:32:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2HIDrEKa-4tG for <tzdist@ietfa.amsl.com>; Thu, 11 Dec 2014 13:32:05 -0800 (PST)
Received: from mail4.serversure.net (mail4-2.serversure.net [217.147.176.214]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EB90B1A0056 for <tzdist@ietf.org>; Thu, 11 Dec 2014 13:32:04 -0800 (PST)
Received: (qmail 31897 invoked by uid 89); 11 Dec 2014 21:32:03 -0000
Received: by simscan 1.3.1 ppid: 31891, pid: 31894, t: 0.0989s scanners: attach: 1.3.1 clamav: 0.96/m:52/d:10677
Received: from unknown (HELO ?10.0.0.8?) (lester@rainbowdigitalmedia.org.uk@86.178.188.220) by mail4.serversure.net with ESMTPA; 11 Dec 2014 21:32:03 -0000
Message-ID: <548A0D52.8050608@lsces.co.uk>
Date: Thu, 11 Dec 2014 21:32:02 +0000
From: Lester Caine <lester@lsces.co.uk>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: tzdist@ietf.org
References: <059.5da79d7c9d394e20e3c22513cfe04c33@tools.ietf.org> <54888249.9080607@lsces.co.uk> <CAFpi07z8NauUZ5aBqqg9sXDsmSA+hG4HuZNDkLe7fnk=mg4wgA@mail.gmail.com> <676B23282D9F7F1DCE6A54C7@caldav.corp.apple.com> <CAFpi07x79gJLEBWmpxWv7V13CiwmeKGy7bwS1=+ukp-sKmwFxA@mail.gmail.com> <5488921B.8020900@lsces.co.uk> <5488973F.7050400@andrew.cmu.edu> <54889C39.1080103@lsces.co.uk> <D2BE5C3BFE11019ECF4BEF62@caldav.corp.apple.com> <5488A6E6.8050903@lsces.co.uk> <CADC+-gTiyJ4QHZT6m3je9M9-ifSELnSWgmgy7iXSWNS+p8pthg@mail.gmail.com> <5488C0EA.8090505@lsces.co.uk> <CADC+-gTgckSe1ca6Sai6RguQid=ReM7bH6K8+dVVFm-YfbpFbA@mail.gmail.com> <5488DA56.2090306@lsces.co.uk> <CADC+-gQN=Qb2y8M-bHnPzMcK8r=xUG-seQ7XzvZwwcWsHpHnBQ@mail.gmail.com> <54895986.6060806@lsces.co.uk> <5489CA90.1070307@gmail.com> <35BC5886C9A58F866E8A46A8@caldav.corp.apple.com> <5489D9F7.3080207@gmail.com> <D196D63077FEC1B090DF7C86@caldav.corp.apple.com> <5489F79E.4080909@gmail.com> <BC19CC6916DC0E59CA63737D@caldav.corp.apple.com>
In-Reply-To: <BC19CC6916DC0E59CA63737D@caldav.corp.apple.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/tzdist/9MJ_IkZlgS09yXSyyiKDPS-XXpA
Subject: Re: [Tzdist] Fwd: [tzdist] #32 (service): managing historical data
X-BeenThere: tzdist@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <tzdist.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tzdist>, <mailto:tzdist-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tzdist/>
List-Post: <mailto:tzdist@ietf.org>
List-Help: <mailto:tzdist-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tzdist>, <mailto:tzdist-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Dec 2014 21:32:07 -0000

On 11/12/14 21:01, Cyrus Daboo wrote:
> Having everyone agree to use a reliable and timely tzdist service
> eliminates many (not all) of the big issues that exist today. Yes,
> clients will still need to be smarter about dealing with time zone
> changes when they occur - and that is what this debate needs to stay
> focussed on. What information does tzdist need to provide in the data it
> provides to ensure that clients have the necessary information to do
> more advanced reconciliation of events when a time zone change occurs.

I feel the case has been made for the ability to manage each published
version of a published data set? Using the version tagging. That a
server only needs to maintain versions for those TZid's which have
changed keeps the volume of data down. Probably 90% of data will never
change and so the very first version will still be used to provide that
material. Many updates will only be perhaps three or four TZid's and
potentially clients may never even read those as they are out of scope
for their calendars.

As new material is published using the current data, the correct version
can be tagged, so an archive can maintain a consistent view of it's
content. SO that only needs a server which is able to provide the
versioned views. As far as I am concerned, genealogical data needs this
facility and so has to use a server capable of it - with a backzoneTZ
base probably complimented by a historic location mapping database as well.

The problem is if event calendars published today need this versioning?
If they only contain data that is never likely to be part of a new
version, then obviously not, but it's what level of 'error' is
acceptable for material which is subsequently retained in archives and
used later in other cross references. That a meeting time is an hour
adrift may not matter so we can simply say 'tough' and ignore
discrepancies, but I'd still like a better explanation on how one
ensures that when a change in offsets are applied which invalidates
existing forthcoming events, this is notified without the use of a version?

-- 
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