Handling VTIMEZONE non-compliance for DTSTART values #751

benfortuna · 2024-11-06T22:07:48Z

benfortuna
Nov 6, 2024
Maintainer

If I may, I'd like to conduct a quick poll regarding VTIMEZONE implementation, and how to handle a specific deviation from the specification.

An iCal4j issue (#748) has identified an implementation using UTC time in the DTSTART property of VTIMEZONE definitions

Currently iCal4j will throw an exception, but I am curious if others handle this differently. Any feedback is most appreciated.

RFC5545 requires DTSTART for VTIMEZONE to be floating (local) time. How would you handle UTC values?

Allow UTC time, assuming that appropriate pre-processing was done to convert local time for each TZ definition to UTC

0%

Do not allow (throw an exception) as we can't know the intention of such a definition (is it really UTC or local?)

0%

Remove the 'Z' from the string value, assuming intention was a local time definition

0%

Other that is not listed here

0%

0 votes