Re: Registration of media type application/calendar+xml

Peter Saint-Andre <> Fri, 10 September 2010 17:38 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 929D03A685C for <>; Fri, 10 Sep 2010 10:38:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -102.573
X-Spam-Status: No, score=-102.573 tagged_above=-999 required=5 tests=[AWL=0.026, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id jFPnsvvW1Kzw for <>; Fri, 10 Sep 2010 10:38:03 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id EF0853A6783 for <IETF@IETF.ORG>; Fri, 10 Sep 2010 10:38:02 -0700 (PDT)
Received: from ( []) (Authenticated sender: stpeter) by (Postfix) with ESMTPSA id 18F2640074; Fri, 10 Sep 2010 11:42:11 -0600 (MDT)
Message-ID: <>
Date: Fri, 10 Sep 2010 11:38:21 -0600
From: Peter Saint-Andre <>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv: Gecko/20100824 Thunderbird/3.0.7
MIME-Version: 1.0
To: Keith Moore <>
Subject: Re: Registration of media type application/calendar+xml
References: <> <> <B0EA09C87A5701A94419DB8F@socrates.local> <> <> <>
In-Reply-To: <>
X-Enigmail-Version: 1.0.1
OpenPGP: url=
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Douglass Mike <>, Cyrus Daboo <>, Keith Moore <>, Alexey Melnikov <>,, Steven Lees <>, IETF@IETF.ORG
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 10 Sep 2010 17:38:07 -0000

On 9/10/10 11:21 AM, Keith Moore wrote:
>>>> An XML representation for iCalendar is vital if we are to keep
>>>> iCalendar relevant in the web-based world. The drive for this
>>>> work comes from a number of areas - in particular the smart
>>>> grid effort sponsored by NIST will make use of this as part of
>>>> the standards suite they are defining.
>>> Somebody needs to talk some sense into those people.  Defining
>>> another calendar format will only harm interoperability.  It
>>> doesn't save any calendar implementation from needing to
>>> implement another parser, because if it wants to interoperate
>>> with existing products or be able to read old events it's still
>>> going to have to support iCalendar and probably vCalendar also.
>>> So what's the _technical_ (not political) benefit from doing
>>> this?
>> First of all look at the mess we have got into with contacts (see
>> recent discussion on the vcarddav WG mailing list). There we now
>> have vCard, PoCo, OpenSocial and some new thing the OMA is doing
>> (and their are lots of private apis too). Yet vCard has been around
>> for a long time - why didn't those other folks just use that or at
>> least propose fixes or extension to vcard that would satisfy their
>> issues? Well, certainly in the case of PoCo one clear requirement
>> was for a simple web/browser based solution - so they designed JSON
>> and XML representations.
> Mumble.  It's a lot harder to make a web browser do something useful
> with a calendar object (no matter what the syntax) than it is to make
> a web browser do something useful with contact information.
> And I *like* JSON.  I think it's a good approximation to what XML
> should have been.

It's not clear to me how your personal preference for JSON over XML is
relevant to registration of the application/calendar+xml media type or
continued work on draft-daboo-et-al-icalendar-in-xml. However, given
that you seem to object to the XML representation of vCards, calendaring
objects, and just about anything else, I suggest that you start a thread
about XML vs. JSON on the apps-discuss list rather than filling up the
archives of the ietf-types and lists.


Peter Saint-Andre