All-day Calendar Recurrence Evidence

How to use All-day Calendar Recurrence Evidence

Explain a small all-day recurrence set from actual calendar source instead of guessing from a date list. Inspect how DTSTART, a supported RRULE, added RDATE values and excluded EXDATE values combine, with exclusive event ends and the pre-exclusion rule count retained as evidence.

1. Paste one original all-day calendar event in the explicitly supported profile.
2. Choose a bounded inclusive window for occurrence start dates.
3. Run the expansion and inspect each inclusion source, excluded date and exclusive event end before downloading the JSON report.

Good to know

• One VCALENDAR/VEVENT; 30,000 characters, 1,000 physical lines, 2,000 characters per unfolded line, 200 RDATE and 200 EXDATE values. LF input is accepted as a declared convenience; bare CR is refused. VERSION, PRODID, UID, DTSTAMP and DATE DTSTART are required. Supported optional properties are CALSCALE:GREGORIAN, DTEND, SUMMARY, DESCRIPTION and LOCATION.
• All-day Gregorian DATE values only, with unquoted VALUE=DATE parameters. DAILY interval; WEEKLY interval and unnumbered BYDAY/WKST; MONTHLY interval and positive BYMONTHDAY are supported. INTERVAL 1–99, COUNT 1–1,000 or inclusive DATE UNTIL, never both. Every other rule part/property/parameter, nested component, TZID, override, alarm and timed/floating event is refused.
• The query selects start dates in an inclusive window of at most 366 days, at most 3,660 calendar days after DTSTART. Event duration is 1–366 days and DTEND is exclusive. Years 0001–9999; out-of-domain generated end dates are refused. This is a JSON explanation, not a full iCalendar validator, calendar-file editor, DST interpreter or calendar-app import guarantee.
• Processing is local. Output is limited to 1,000,000 text characters unless a stricter file limit is stated.