[Ietf-calsify] Issue 13, 24, 25: Generation of the recurrence set

[Mike Higginbottom]

On Thu, 19 Oct 2006 21:00:45 +0100, Bernard Desruisseaux  
<bernard.desruisseaux at oracle.com> wrote:

> I propose to modify the iCalendar specification to state the
> following:
>
>    - In a recurring component, the value of the DTSTART property
>      SHOULD match the pattern of the recurrence rule. The recurrence
>      set generated with a DTSTART property value that doesn't match
>      the pattern of the rule is undefined.
>
>    - The RRULE property SHOULD NOT occur more than once in a
>      recurring component. The recurrence set generated with
>      multiple RRULE properties is undefined.
>
>    - The use of the EXRULE property is deprecated.
>
>      Every reference to EXRULE would be removed from the draft.
>      The EXRULE property would be documented as "Deprecated" in
>      an Appendix of the draft and would refer readers to RFC 2445
>      for more information on this property.

Have we defined what actions are to be taken when implementations  
encounter undefined/deprecated content? I guess a blanket statement along  
the lines of 'ignore any undefined/illegal content' would be the best  
approach but some implementors might ignore only part of the data or make  
some kind of best guess. A defined, standard approach would be beneficial.  
I'm assuming this hasn't already been done somewhere of course...


-- 
Mike Higginbottom
Paul Smith Computer Services
Silk Mill House
196 Huddersfield Road
Meltham
Holmfirth
HD9 4AW
United Kingdom

http://www.pscs.co.uk
+44 (0)1484 855800