https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30927
Aaron Sakovich <asakov...@hmcpl.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |asakov...@hmcpl.org --- Comment #6 from Aaron Sakovich <asakov...@hmcpl.org> --- RFC 5545 https://datatracker.ietf.org/doc/html/rfc5545 on page 54 (section 3.6.1 Event Component) says the following: > ... For cases where a "VEVENT" calendar component > specifies a "DTSTART" property with a DATE value type but no > "DTEND" nor "DURATION" property, the event's duration is taken to > be one day. For cases where a "VEVENT" calendar component > specifies a "DTSTART" property with a DATE-TIME value type but no > "DTEND" property, the event ends on the same calendar date and > time of day specified by the "DTSTART" property. What if the DTSTART is a DATE or DATE-TIME, and DTEND and DURATION are left blank? We could set it to be a DATE if the due time is 23:59, and a DATE-TIME otherwise. That would result in either an all day event as desired per option A) (when due at midnight) or an event with a specific due time and the end time set to the end of the day, the inverse of Option B) (which might be a more palatable solution as event reminders are typical set based on the start time of an event). Alternatively, a DURATION could be specified in the latter case, but note that DURATION (section 3.8.2.5) is a _positive_ value, and no mention is made in the spec of a zero duration, so I'd be hesitant to reference a zero-value duration. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list Koha-bugs@lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/