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

Phillip Mienk <phillip@shingl.com> Fri, 27 May 2011 01:29 UTC

Return-Path: <phillip@shingl.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 E224CE0745 for <icalendar@ietfa.amsl.com>; Thu, 26 May 2011 18:29:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.976
X-Spam-Level:
X-Spam-Status: No, score=-5.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 cpz8kPvN4w1M for <icalendar@ietfa.amsl.com>; Thu, 26 May 2011 18:29:45 -0700 (PDT)
Received: from exprod7og102.obsmtp.com (exprod7og102.obsmtp.com [64.18.2.157]) by ietfa.amsl.com (Postfix) with SMTP id 1CE5FE0697 for <icalendar@ietf.org>; Thu, 26 May 2011 18:29:45 -0700 (PDT)
Received: from mail-qw0-f45.google.com ([209.85.216.45]) (using TLSv1) by exprod7ob102.postini.com ([64.18.6.12]) with SMTP ID DSNKTd7+iDWfBEKgPK+vdXmbveOsovP4fmNH@postini.com; Thu, 26 May 2011 18:29:45 PDT
Received: by qwj8 with SMTP id 8so1041154qwj.18 for <icalendar@ietf.org>; Thu, 26 May 2011 18:29:43 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.101.36 with SMTP id a36mr1208690qco.74.1306459783643; Thu, 26 May 2011 18:29:43 -0700 (PDT)
Received: by 10.229.188.146 with HTTP; Thu, 26 May 2011 18:29:43 -0700 (PDT)
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>
Date: Thu, 26 May 2011 18:29:43 -0700
Message-ID: <BANLkTinm2dfq7drFL=SGn8QQsYbktQsmOg@mail.gmail.com>
From: Phillip Mienk <phillip@shingl.com>
To: Bernard Desruisseaux <bernard.desruisseaux@oracle.com>
Content-Type: multipart/alternative; boundary=0016364ee01e51441b04a437df5a
Cc: draft-daboo-et-al-icalendar-in-xml@tools.ietf.org, icalendar@ietf.org, Peter Saint-Andre <stpeter@stpeter.im>, iana-prot-param-comment@iana.org, iana@iana.org
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 01:29:47 -0000

I'm new to this list and in looking over the draft, I have a question about
the fundamental intent of iana-tokens.  In my reading of rfc5545 I was under
the impression that properties (and by extension iana-tokens) were meant to
encode semantic information.  Is this inference in error?

It appears to me that the concept of xml-encoding is akin to the difference
between a date and date-time.  In the same way that the start and end of an
appointment are encoded by DTSTART and DTEND as opposed to some 'DATETIME'
or 'DATE' property.  I would think that the semantic title of the content of
the xml-encoded information would be the intended token/property name and
the encoding be communicated via parameter.

Please let me know where I have strayed in my understanding.

-- Phillip Mienk

On Thu, May 26, 2011 at 5:47 PM, 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
>
>
> 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.
>
>
>
>
> _______________________________________________
> icalendar mailing list
> icalendar@ietf.org
> https://www.ietf.org/mailman/listinfo/icalendar
>
>