spec 1 linked patterns checked
Google Calendar API recurring event time zone
Documents that recurring events require a single time zone so recurrences can be expanded correctly.
Read with a purpose
What this source can teach
Use this source to check a technical or accessibility requirement against its exact wording and scope.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Scheduling | Choose scheduling when users coordinate time across participants, calendars, availability, resources, recurrence, reminders, or invitations. | Changing date, time, duration, attendees, resources, timezone, recurrence, or checked calendars recomputes availability before send. | Google Calendar API requires a timezone for recurring events so recurrences expand correctly. |
Comparisons supported by this source
- Scheduling vs booking vs calendar view vs date picker
Google Calendar API documents recurring event timezone requirements for expanding recurrences correctly.
Evidence Role
This source is treated as spec evidence. Its value comes from the specific claims and setting described above.
Publisher: Google for Developers. Last checked: .