Re: [icalendar] [IANA #453987] Registration of new iCalendar property

Cyrus Daboo <cyrus@daboo.name> Fri, 27 May 2011 14:09 UTC

Return-Path: <cyrus@daboo.name>
X-Original-To: icalendar@ietfa.amsl.com
Delivered-To: icalendar@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E42CE06DD for <icalendar@ietfa.amsl.com>; Fri, 27 May 2011 07:09:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.602
X-Spam-Level:
X-Spam-Status: No, score=-100.602 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_36=0.6, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BfBdInQSqPgA for <icalendar@ietfa.amsl.com>; Fri, 27 May 2011 07:09:46 -0700 (PDT)
Received: from daboo.name (daboo.name [151.201.22.177]) by ietfa.amsl.com (Postfix) with ESMTP id 63DB6E06DA for <icalendar@ietf.org>; Fri, 27 May 2011 07:09:44 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 0C886A79F5A; Fri, 27 May 2011 10:09:44 -0400 (EDT)
X-Virus-Scanned: amavisd-new at daboo.name
Received: from daboo.name ([127.0.0.1]) by localhost (chewy.daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6yxOtcSh+qFF; Fri, 27 May 2011 10:09:36 -0400 (EDT)
Received: from [17.151.71.145] (unknown [208.51.138.98]) by daboo.name (Postfix) with ESMTPSA id C262DA79F45; Fri, 27 May 2011 10:09:33 -0400 (EDT)
Date: Fri, 27 May 2011 07:09:33 -0700
From: Cyrus Daboo <cyrus@daboo.name>
To: Bernard Desruisseaux <bernard.desruisseaux@oracle.com>, iana-prot-param-comment@iana.org, icalendar@ietf.org, iana@iana.org
Message-ID: <715DF9985D2BFC1C75434F9B@wdyn-50-139.arc.nasa.gov>
In-Reply-To: <4DDEF49C.8080108@oracle.com>
References: <RT-Ticket-453987@icann.org> <EBA8A5D01BFAEE29217B04F9@wdyn-50-139.arc.nasa.gov> <rt-3.8.HEAD-7548-1306346038-1753.453987-9-0@icann.org> <4DDEF49C.8080108@oracle.com>
X-Mailer: Mulberry/4.1.0a1 (Mac OS X)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="==========C32029A1482AA24E6B9A=========="
Cc: draft-daboo-et-al-icalendar-in-xml@tools.ietf.org, Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: [icalendar] [IANA #453987] Registration of new iCalendar property
X-BeenThere: icalendar@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: iCalendar <icalendar.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/icalendar>, <mailto:icalendar-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/icalendar>
List-Post: <mailto:icalendar@ietf.org>
List-Help: <mailto:icalendar-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/icalendar>, <mailto:icalendar-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 May 2011 14:09:48 -0000

Hi Bernard,

--On May 26, 2011 5:47:24 PM -0700 Bernard Desruisseaux 
<bernard.desruisseaux@oracle.com> wrote:

> Here's my review of section 4.2 of draft-daboo-et-al-icalendar-in-xml-10:
>
> 1- Change:
>
>    Purpose: To embed XML-encoded calendar data in the iCalendar format
>  to:
>
>    Purpose: To embed extended XML-encoded iCalendar data in the iCalendar
> format

Fixed.

>  2- Change:
>
>    Conformance: The property can appear on any iCalendar component.
>  to:
>
>    Conformance: This property can be specified multiple times in any
>       calendar component.

Fixed.

> 3- Text should make it clear whether the value can include an XML
> declaration or not (i.e., <?xml version="1.0" ... ?>).

I have taken text from the vcardxml spec that states clearly that the 
embedded XML must be version 1.0. Hence there is no need for the <?xml ...> 
declaration.

> 4- May want to remove or relax the restriction on "X-" iCalendar
> extension property in the following paragraph, since one never can tell
> whether there is such an extension being used out there.
>
>    The "XML"
>    property MUST NOT be used to contain properties that are already
>    defined in iCalendar, or properties that use the "X-" iCalendar
>    extension property syntax.

Fixed by removing.

>
> 5- Change:
>
>    Note that the source XML may contain characters not allowed in
>    iCalendar such as control characters.
>  to:
>
>    Note that the source XML may contain characters not allowed in
>    "TEXT" property values.
>  It might also be a good idea to talk about the special characters that
> can simply be escaped with a BACKSLASH..

Fixed.

> 6- Change:
>
>    There can be more than one "XML" property present for a given
>    iCalendar object.  The ordering of "XML" properties is not preserved
>    in the conversion between xCal and iCalendar.
>
>  to:
>
>    The ordering of "XML" properties is not preserved in the conversion
>    between xCal and iCalendar.

Fixed.

> 7- The example is not a valid iCalendar object.  DTSTART is missing the
> VALUE parameter (i.e., DTSTART;VALUE=DATE:20081006).  There is actually
> no need to specify a complete iCalendar object as an example.  Please
> consider providing a complete XML example instead (i.e., without "...").

Fixed. I have included an example for the property only, but have added a 
more complete sample of xml, including some backslash escaping.

Please find attached an HTML diff with the proposed changes. Let me know if 
this addresses all your comments and I will submit the new draft.

-- 
Cyrus Daboo