Re: Registration of media type application/calendar+xml

Cyrus Daboo <cyrus@daboo.name> Fri, 10 September 2010 13:56 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 85F623A68D7 for <ietf@core3.amsl.com>; Fri, 10 Sep 2010 06:56:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.454
X-Spam-Level:
X-Spam-Status: No, score=-102.454 tagged_above=-999 required=5 tests=[AWL=0.145, 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 KhzMbcZq3uJ1 for <ietf@core3.amsl.com>; Fri, 10 Sep 2010 06:56:36 -0700 (PDT)
Received: from daboo.name (daboo.name [151.201.22.177]) by core3.amsl.com (Postfix) with ESMTP id 2E89A3A68BC for <IETF@IETF.ORG>; Fri, 10 Sep 2010 06:56:36 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id DA0571924004A; Fri, 10 Sep 2010 09:57:02 -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 RV+bq4BcclFF; Fri, 10 Sep 2010 09:56:58 -0400 (EDT)
Received: from caldav.corp.apple.com (unknown [17.101.32.44]) by daboo.name (Postfix) with ESMTPSA id 1527E1924003D; Fri, 10 Sep 2010 09:56:55 -0400 (EDT)
Date: Fri, 10 Sep 2010 09:56:53 -0400
From: Cyrus Daboo <cyrus@daboo.name>
To: Keith Moore <moore@cs.utk.edu>, Ned Freed <ned.freed@mrochek.com>
Subject: Re: Registration of media type application/calendar+xml
Message-ID: <43F23935E7908D7304FE0482@caldav.corp.apple.com>
In-Reply-To: <22026_1284097229_o8A5eRUG005394_D07F8B0F-3157-47BF-8F8E-38A7B4C7A34E@cs.utk.edu>
References: <F842A373EE7E9C439CA07CCB01BBD1D0564C4899@TK5EX14MBXC138.redmond.corp.microsoft.com> <341B449F-7DFE-4A40-84B0-D008658A08DF@cs.utk.edu> <01NRP8H2AP2Y003JZ5@mauve.mrochek.com> <22026_1284097229_o8A5eRUG005394_D07F8B0F-3157-47BF-8F8E-38A7B4C7A34E@cs.utk.edu>
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=1325
Cc: ietf-types@iana.org, Steven Lees <Steven.Lees@microsoft.com>, Douglass Mike <douglm@rpi.edu>, 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 13:56:37 -0000

Hi Keith,

--On September 10, 2010 1:40:16 AM -0400 Keith Moore <moore@cs.utk.edu> 
wrote:

> But here's the acid test.  If you can define a mapping from iCalendar to
> XML that doesn't require any string constants to describe it (other than
> for iCalendar keywords that imply nesting, and separators that are used
> in a regular fashion in iCalendar), and if you can define the inverse
> mapping from XML to iCalendar without naming more than a couple of
> specific element or parameter names - then I'll concede that the mapping
> will probably continue to work in the face of extensions to the iCalendar
> data model.   Otherwise, I'm highly dubious.

That is precisely the goal of draft-daboo-et-al-icalendar-in-xml. iCalendar 
components, properties, parameters and values all map to XML in a 
consistent manner with no need to "special case" based on type or value. 
New components, properties, parameters, values, either registered with IANA 
or using X- prefixes map in exactly the same way.

Conversion to/from XML is trivial - I have coded at least one half of that 
and I know others who have done both ways.It should also be easy to put 
together an XSLT to go from XML to iCalendar - with the only possible 
difficulty being having to apply escaping and line folding as required by 
iCalendar.

-- 
Cyrus Daboo