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

[Phillip Mienk <[e-mail]>]

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 <
[e-mail]> 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
> [e-mail]
> https://www.ietf.org/mailman/listinfo/icalendar
>
>