Re: [calsify] draft-ietf-calext-jscalendar - excluded

["Neil Jenkins" <[e-mail]>]

On Fri, 17 May 2019, at 13:50, Doug Royer wrote:
> On 5/14/19 2:24 PM, Marten Gajda wrote:
> > I don't see much of an issue here, especially since the `false` path is 
> > the same as the "absent" path.
> 
> And I just checked, that is not in the spec. A reader would have to 
> assume that. From the spec:
> 
> 4.3.3. excluded
> 
>  Type: "Boolean" (optional, default:"false")

The *default: "false"* bit means that absent is the same as false. This is what the default annotation is for.

>  Defines if this object is an overridden, excluded instance of a
>  recurring JSCalendar object (also see Section 4.3.2). If this
>  property value is "true", this calendar object instance MUST be
>  removed from the occurrence expansion.
> 
> I could assume that when set to false, it is added as an instance and 
> not intended to indicate an instance removed.

I agree it never hurts to be explicit and say that a value of `false` has no effect.

Neil.