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

Bernard Desruisseaux <bernard.desruisseaux@oracle.com> Fri, 27 May 2011 00:50 UTC

Return-Path: <bernard.desruisseaux@oracle.com>
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 58EF6E068C for <icalendar@ietfa.amsl.com>; Thu, 26 May 2011 17:50:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.598
X-Spam-Level:
X-Spam-Status: No, score=-7.598 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 J98DV40hsFlf for <icalendar@ietfa.amsl.com>; Thu, 26 May 2011 17:50:42 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by ietfa.amsl.com (Postfix) with ESMTP id 368EBE0680 for <icalendar@ietf.org>; Thu, 26 May 2011 17:50:42 -0700 (PDT)
Received: from rtcsinet22.oracle.com (rtcsinet22.oracle.com [66.248.204.30]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id p4R0lgE9009472 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 27 May 2011 00:47:44 GMT
Received: from acsmt357.oracle.com (acsmt357.oracle.com [141.146.40.157]) by rtcsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id p4R0lc4Y018035 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 27 May 2011 00:47:40 GMT
Received: from hqdfmt01.oracle.com (hqdfmt01.oracle.com [148.87.24.194]) by acsmt357.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id p4R0lWB7007221; Thu, 26 May 2011 19:47:32 -0500
Received: from [10.159.54.55] (/10.159.54.55) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 26 May 2011 17:47:31 -0700
USER-AGENT: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 X-ORACLE-DEBUG=STACK X-ORACLE-LIMIT=2500 OracleBeehiveExtension/1.1.0.0pre29-Alpha Thunderbird/3.1.10
MIME-Version: 1.0
Message-ID: <4DDEF49C.8080108@oracle.com>
Date: Thu, 26 May 2011 17:47:24 -0700 (PDT)
From: Bernard Desruisseaux <bernard.desruisseaux@oracle.com>
To: iana-prot-param-comment@iana.org, icalendar@ietf.org, iana@iana.org
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>
In-Reply-To: <rt-3.8.HEAD-7548-1306346038-1753.453987-9-0@icann.org>
Content-Type: multipart/alternative; boundary="------------080900000602030107080400"
Content-Transfer-Encoding: 7bit
X-Source-IP: rtcsinet22.oracle.com [66.248.204.30]
X-CT-RefId: str=0001.0A090202.4DDEF4B2.0090,ss=1,fgs=0
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 00:50:43 -0000

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


2- Change:

    Conformance: The property can appear on any iCalendar component.

to:

    Conformance: This property can be specified multiple times in any
       calendar component.


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


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.


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..


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.


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 
"...").

Cheers,
Bernard

On 5/25/2011 1:53 PM, Amanda Baber via RT wrote:
> Hi Bernard,
>
> As one of the designated experts for iCalendar, can you review this
> proposed registration for us?
>
> thanks,
>
> Amanda Baber
> IANA
>
> ===
>
> Hi,
> As per the requirements of the iCalendar IANA registration procedures I
> am requesting approval of a new iCalendar property registration. This
> property is being registered by draft-daboo-et-al-icalendar-in-xml-09.
> In particular, Section 7.3 lists the new items and the section where its
> template is defined.
>
> Note: I am one of the designated expert reviewers for this registry but
> will recuse myself since I am a co-author of this document.
>