Re: Registration of media type application/calendar+xml

Keith Moore <moore@network-heretics.com> Sat, 11 September 2010 14:26 UTC

Return-Path: <moore@network-heretics.com>
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 B4A7D3A687C for <ietf@core3.amsl.com>; Sat, 11 Sep 2010 07:26:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.384
X-Spam-Level:
X-Spam-Status: No, score=-2.384 tagged_above=-999 required=5 tests=[AWL=0.216, BAYES_00=-2.599]
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 6VYhMy0tHnL7 for <ietf@core3.amsl.com>; Sat, 11 Sep 2010 07:26:35 -0700 (PDT)
Received: from m1.imap-partners.net (m1.imap-partners.net [64.13.152.131]) by core3.amsl.com (Postfix) with ESMTP id CCC3B3A67E6 for <IETF@ietf.org>; Sat, 11 Sep 2010 07:26:35 -0700 (PDT)
Received: from 173-137-249-197.pools.spcsdns.net (173-137-249-197.pools.spcsdns.net [173.137.249.197]) by m1.imap-partners.net (MOS 4.1.8-GA) with ESMTP id CEA94995 (AUTH admin@network-heretics.com); Sat, 11 Sep 2010 07:26:45 -0700
X-Mirapoint-Received-SPF: 173.137.249.197 173-137-249-197.pools.spcsdns.net <moore@network-heretics.com> 5 none
X-Mirapoint-Received-SPF: 173.137.249.197 173-137-249-197.pools.spcsdns.net <moore@network-heretics.com> 5 none
X-Mirapoint-Received-SPF: 173.137.249.197 173-137-249-197.pools.spcsdns.net <moore@network-heretics.com> 5 none
X-Mirapoint-Received-SPF: 173.137.249.197 173-137-249-197.pools.spcsdns.net <moore@network-heretics.com> 5 none
X-Mirapoint-Received-SPF: 173.137.249.197 173-137-249-197.pools.spcsdns.net <moore@network-heretics.com> 5 none
X-Mirapoint-Received-SPF: 173.137.249.197 173-137-249-197.pools.spcsdns.net <moore@network-heretics.com> 5 none
Subject: Re: Registration of media type application/calendar+xml
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <AANLkTimci+HE-ETqAQnSBt=G6eKYMrUv=5b+3PgL8HF3@mail.gmail.com>
Date: Sat, 11 Sep 2010 10:26:37 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <9D60E7E7-349E-4714-B523-5AC82C81A953@network-heretics.com>
References: <F842A373EE7E9C439CA07CCB01BBD1D0564C4899@TK5EX14MBXC138.redmond.corp.microsoft.com> <341B449F-7DFE-4A40-84B0-D008658A08DF@cs.utk.edu> <01NRP8H2AP2Y003JZ5@mauve.mrochek.com> <4C8A7AB2.5090500@dcrocker.net> <6D1B9008-8C93-4DFA-98AB-75BBE642964D@network-heretics.com> <AANLkTimci+HE-ETqAQnSBt=G6eKYMrUv=5b+3PgL8HF3@mail.gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
X-Mailer: Apple Mail (2.1081)
Cc: Steven Lees <Steven.Lees@microsoft.com>, dcrocker@bbiw.net, "IETF@ietf.org" <IETF@ietf.org>, Douglass Mike <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: Sat, 11 Sep 2010 14:26:36 -0000

On Sep 11, 2010, at 10:20 AM, Phillip Hallam-Baker wrote:

> I don't see any point in having a design conversation based on what might happen to future iterations of the design.

I don't see the point in having a design conversation that isn't based on what might happen to the design.  If the design is carved in stone, the conversation is no longer about design; it's about history.

> It is of course possible, likely even that two variants of a syntax would diverge over time. At some point there will be a decision that future versions of the format will use only one of the syntaxes.

Why wait, and further confuse the market?  We can make that decision now.

> Given the way that calendar applications behave, an incompatible format change would be no bad thing. In particular, calendar applications seem to have no idea that there is a difference between local time and UTC or that daylight savings rules vary with place. I don't know if there is also a problem in the iCal format, but the applications are certainly broken.

Maybe you're using the wrong calendar applications.  The ones I've used haven't had trouble with that.  

(and BTW, the format is iCalendar.  iCal is a Macintosh application)

Keith