
Establish whether the source time is ambiguous
Start with the full programme date, the organizer’s location and the clock used by the listing. Do not assume the change rules of your Canadian province also apply there. If the appointment falls within a local clock transition, ask whether the publisher supplies an explicit UTC time, offset or clarified event entry. Preserve the original listing. A familiar weekly start time is insufficient evidence when one occurrence of that hour repeats or disappears on the particular date.
Know that a calendar file can make a default choice
The i Calendar standard defines how a local time with a time-zone reference is interpreted when the hour repeats or is skipped. For a repeated time it selects the first occurrence; for a missing time it uses the offset before the gap. That is file-format behaviour, not proof that the broadcaster intended that interpretation. If an imported reminder lands unexpectedly, compare the publisher’s actual announcement rather than treating the calendar’s successful parsing as confirmation of the programme time.
Resolve the instant before adjusting the Canadian display
Find a current dated publisher entry that removes the ambiguity, ideally with an explicitly identified zone or UTC reference. Then inspect the resulting reminder in your calendar’s Canadian city zone. Avoid manually adding an hour to one version while leaving a second conflicting reminder active. Keep a note explaining the clarified appointment and the source used. The practical aim is one reliable event, not several plausible-looking conversions that represent different instants.
Check the actual calendar application
A standard describes intended data semantics, while an individual application or malformed publisher file may behave differently. Open the imported event and compare its date, zone and displayed time with the clarified source. If the file has no useful zone information, obtain a better appointment reference rather than guessing. This is a scheduling check only: a correctly timed reminder does not prove the stream will play, that a recording will remain available or that the programme is included in a particular service.
Related questions
Does a repeated1:30 identify only one instant?
Not without the date, zone and intended occurrence.
Does a calendar’s default interpretation prove the broadcaster’s intent?
No. Confirm the actual dated publisher announcement.
Sources and scope
Scope notes distinguish published documentation, supplied information and editorial methods. They do not report a hands-on service test.
- RFC5545 date-time semantics — Specific repeated/missing local-time interpretation; separate from publisher intent
- Google calendar import troubleshooting — Check source/destination time-zone settings when imported events shift