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

Am 14.05.19 um 03:40 schrieb Doug Royer:
> >> 12. _excluded_ property (4.3.2). I assume (ambiguous) if it can ever
> >> be set to false? Can I send it in object set to false at all? When
> >> would it be valid to set it to false? What is the point of ever being
> >> able to send one set to false?
> >
> > This property represents what's EXDATEs in iCalendar. It could be set
> > to false, but it's only really useful to set it to true, or not at
> > all.
>
> Just trying to reduce dead code issues in implementations (ambiguous
> handling and expectations). If the spec specifically said that it
> should only be supplied when TRUE, then no code will ever be written
> to do otherwise.
>
> No need to code "... else when set to false ..." because that code
> would NEVER execute == dead code.

Every implementation should be able to handle `false`. It's the default
if the property is absent and there may be implementations which prefer
being explicit rather than relying on defaults. We see this in iCalendar
a lot when implementations specify VALUE=DATE-TIME even though it's the
default for those properties.

I don't see much of an issue here, especially since the `false` path is
the same as the "absent" path.

Marten

>
>
>
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify

-- 
Marten Gajda
CEO

dmfs GmbH
Schandauer Straße 34
01309 Dresden
GERMANY

phone: +49 177 4427167
email: marten@dmfs.org

Managing Director: Marten Gajda
Registered address: Dresden
Registered No.: AG Dresden HRB 34881
VAT Reg. No.: DE303248743

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