RE: draft-douglass-timezone-xml-00 & Presence

Cyrus Daboo <cyrus@daboo.name> Wed, 07 July 2010 13:41 UTC

Return-Path: <cyrus@daboo.name>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A73033A67E9 for <ietf@core3.amsl.com>; Wed, 7 Jul 2010 06:41:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.649
X-Spam-Level:
X-Spam-Status: No, score=-0.649 tagged_above=-999 required=5 tests=[AWL=-0.650, BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IdhJPCgjNftw for <ietf@core3.amsl.com>; Wed, 7 Jul 2010 06:41:23 -0700 (PDT)
Received: from daboo.name (daboo.name [151.201.22.177]) by core3.amsl.com (Postfix) with ESMTP id A26583A67CC for <ietf@ietf.org>; Wed, 7 Jul 2010 06:41:23 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 8A4C018679811; Wed, 7 Jul 2010 09:41:26 -0400 (EDT)
X-Virus-Scanned: amavisd-new at daboo.name
Received: from daboo.name ([127.0.0.1]) by localhost (chewy.mulberrymail.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wVu3stOf6rkx; Wed, 7 Jul 2010 09:41:25 -0400 (EDT)
Received: from caldav.corp.apple.com (unknown [17.101.32.44]) by daboo.name (Postfix) with ESMTPSA id 4383618679805; Wed, 7 Jul 2010 09:41:23 -0400 (EDT)
Date: Wed, 07 Jul 2010 09:41:19 -0400
From: Cyrus Daboo <cyrus@daboo.name>
To: Glen Zorn <gwz@net-zen.net>
Subject: RE: draft-douglass-timezone-xml-00 & Presence
Message-ID: <D22391916E4A79042B2285F0@caldav.corp.apple.com>
In-Reply-To: <016201cb1d86$d658ad30$830a0790$@net>
References: <20100705203002.29AB83A69F4@core3.amsl.com> <201007061939.o66JdA21017261@sj-core-1.cisco.com> <E1A7CB773934BD03145232ED@caldav.corp.apple.com> <016201cb1d86$d658ad30$830a0790$@net>
X-Mailer: Mulberry/4.1.0a1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size="1233"
Cc: 'IETF-Discussion list' <ietf@ietf.org>, douglm@rpi.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Jul 2010 13:41:24 -0000

Hi Glen,

--On July 7, 2010 10:45:23 AM +0700 Glen Zorn <gwz@net-zen.net> wrote:

>> > How is this unique wrt to what Presence has provided in XML for 4-6
>> > years? A comparison is at least preferable to what already exists for
>> > timezones in XML, IMO.
>>
>> Can you provide a specific reference to what you are referring to?
>
> For example, see http://www.w3.org/TR/timezone/.

Our draft is not about how you represent timezone (UTC offsets) in 
date-time values (which is mostly what that w3.org reference talks about).

Our draft is about representing timezone definitions (standard time 
offsets, daylight saving time rules, how they varying over time, etc) in 
XML. This is akin to iCalendar's VTIMEZONE data or zoneinfo data found on 
Unix systems (and in a more "raw" form the Olson timezone database). One of 
the primary goals for this is to support exchange of timezone definitions 
between system via a timezone service protocol 
(draft-douglass-timezone-service - another draft we submitted a short while 
ago).

I believe this is clear in our draft, though admittedly the abstract may 
not convey that in as much detail as it should (and I will endeavor to beef 
up the abstract to clarify this).

-- 
Cyrus Daboo