Re: Registration of media type application/calendar+xml

Peter Saint-Andre <stpeter@stpeter.im> Fri, 10 September 2010 17:38 UTC

Return-Path: <stpeter@stpeter.im>
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 929D03A685C for <ietf@core3.amsl.com>; Fri, 10 Sep 2010 10:38:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.573
X-Spam-Level:
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 mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jFPnsvvW1Kzw for <ietf@core3.amsl.com>; Fri, 10 Sep 2010 10:38:03 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id EF0853A6783 for <IETF@IETF.ORG>; Fri, 10 Sep 2010 10:38:02 -0700 (PDT)
Received: from dhcp-64-101-72-245.cisco.com (dhcp-64-101-72-245.cisco.com [64.101.72.245]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 18F2640074; Fri, 10 Sep 2010 11:42:11 -0600 (MDT)
Message-ID: <4C8A6D0D.8080201@stpeter.im>
Date: Fri, 10 Sep 2010 11:38:21 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.12) Gecko/20100824 Thunderbird/3.0.7
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: Registration of media type application/calendar+xml
References: <F842A373EE7E9C439CA07CCB01BBD1D0564C4899@TK5EX14MBXC138.redmond.corp.microsoft.com> <341B449F-7DFE-4A40-84B0-D008658A08DF@cs.utk.edu> <B0EA09C87A5701A94419DB8F@socrates.local> <673F57D3-B2EC-4ABF-B450-EEEA3A4C185A@cs.utk.edu> <00A143E2295D950F3C6DE2D1@caldav.corp.apple.com> <D672DBCE-C53E-477A-991C-213460306C81@network-heretics.com>
In-Reply-To: <D672DBCE-C53E-477A-991C-213460306C81@network-heretics.com>
X-Enigmail-Version: 1.0.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: Douglass Mike <douglm@rpi.edu>, Cyrus Daboo <cyrus@daboo.name>, Keith Moore <moore@cs.utk.edu>, Alexey Melnikov <Alexey.Melnikov@isode.com>, ietf-types@iana.org, Steven Lees <Steven.Lees@microsoft.com>, IETF@IETF.ORG
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: 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 ietf@ietf.org lists.

https://www.ietf.org/mailman/listinfo/apps-discuss

Peter

-- 
Peter Saint-Andre
https://stpeter.im/