Re: Registration of media type application/calendar+xml

Cyrus Daboo <> Fri, 10 September 2010 13:56 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 85F623A68D7 for <>; Fri, 10 Sep 2010 06:56:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -102.454
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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id KhzMbcZq3uJ1 for <>; Fri, 10 Sep 2010 06:56:36 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 2E89A3A68BC for <IETF@IETF.ORG>; Fri, 10 Sep 2010 06:56:36 -0700 (PDT)
Received: from localhost (localhost []) by (Postfix) with ESMTP id DA0571924004A; Fri, 10 Sep 2010 09:57:02 -0400 (EDT)
X-Virus-Scanned: amavisd-new at
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id RV+bq4BcclFF; Fri, 10 Sep 2010 09:56:58 -0400 (EDT)
Received: from (unknown []) by (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 <>
To: Keith Moore <>, Ned Freed <>
Subject: Re: Registration of media type application/calendar+xml
Message-ID: <>
In-Reply-To: <>
References: <> <> <> <>
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:, Steven Lees <>, Douglass Mike <>, 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 13:56:37 -0000

Hi Keith,

--On September 10, 2010 1:40:16 AM -0400 Keith Moore <> 

> 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 

Cyrus Daboo