Interpretation limit
Do not automatically apply today's offset to past or future dates. A zone does not complete an incomplete source date.
Public sources / INT
Find civil-time rules, UTC offsets and daylight-saving changes in an identified tz database release. When comparing times, retain the zone identifier and database version used for conversion.

AI-generated illustration
Read this source in practice
tz organises civil-time rules and history. A zone name and numeric offset serve different roles: resolve time for the relevant date and retain the rule version.
Do not automatically apply today's offset to past or future dates. A zone does not complete an incomplete source date.
Raw text, zone, date, chosen resolution, offset and rule version.
A fictional zone has two seasonal offsets. Replacing its ID with one year-round offset changes some instants.
Consulted reference : IANA — Theory and pragmatics of the tz code and data · Consulted on
Updated on :
The reference documents the reading method. The example is fictional; this note does not attest a portal test today or a mission outcome.
Open the work, its version and editorial status. A bibliographic record or citation identifies an object without validating its findings.
Find civil-time rules, UTC offsets and daylight-saving changes in an identified tz database release. When comparing times, retain the zone identifier and database version used for conversion.
A zone name is not a fixed offset. Rules depend on date and release; the database does not establish when an event occurred.
Original text, IANA zone, explicit offset, precision, tz release and access date.
Distinguish calendar date from instant. A local time without an offset may be ambiguous or nonexistent at a clock change.
Access, download and API conditions depend on the service. Consult the official documentation and the resource terms.
Retain each observation’s original timestamp, role and offset before converting instants to UTC.
Capture or network-query time is not necessarily publication or content-modification time.
Compare sourcesInspect the exact resource and its terms. Being viewable does not authorise redistribution; retain the resource licence and restrictions instead of inferring them from the portal.
Record consultation date, covered period, last update and version separately. For revised data, retain the file or exact extraction reference.
The web page, export and API may differ in coverage or terms. Check pagination, filters, authentication, quotas and licence for the access method used.
RFC 3339 uses it for an unknown local offset when UTC time is known. Preserve that status instead of treating it as evidence of a local zone.
Keep IANA zone, local date, chosen offset and tz version. Recalculation with another version may differ; retain both outputs and explain.
Normalise dates in a source dossierDEEPER READING / PRACTICE
A list indicates where to look for and what limits to keep in mind. It helps to prepare a consultation but does not replace the reading of the obtained document.
Updated on .
Select a precise question, open the source and raise the request, result and date. Compare the possibilities announced with the information actually available at the time of the consultation.
The availability of a service and its content may vary. The directory does not turn an absent, partial or ambiguous result into a definitive response.
The consultation report documentes the search path, document found, useful elements and reserves. The result is included in the file with its origin.