Re: [Jcardcal] Last Minute jCal changes? RSCALE extension might mess with data type

[Cyrus Daboo <[e-mail]>]

Hi Peter,

--On April 3, 2014 at 7:51:36 AM -0600 Peter Saint-Andre 
<[e-mail]> wrote:

> With my WG chair hat on, I have concerns.
>
> Why is the RSCALE draft modifying an existing element from RFC 5545
> instead of defining a new element? How certain are we that the draft
> Cyrus and Gregory are working on will end up changing monthnum? Do we
> really want to be tracking an I-D with an uncertain future?
>
> It seems more prudent, at this late date, to align only with RFC 5545.

I would agree that jcal should not change at this point. RSCALE is still a 
draft and can be changed if real problems are encountered.

That said, the reason we chose to use the "L" suffix and chose to add a new 
element to RRULE was precisely because we want parsers to "blow-up" and not 
interpret the event incorrectly. As a general rule all parsers should 
handle illegal data formats in properties or parameters in a sane way 
(simple choice being to just ignore the entire iCalendar object being 
parsed - though keep parsing other iCalendar objects in the stream).

That choice for RSCALE is still up for debate - but that discussion should 
take place on the calsify mailing list.

-- 
Cyrus Daboo