Opened 8 years ago

Closed 8 years ago

#13 closed defect (fixed)

definition of "Timezone Data"

Reported by: eggert@… Owned by: cyrus@…
Priority: major Milestone:
Component: service Version:
Severity: Candidate WG Document Keywords:

Description (last modified by lear@…)

Section 1.2's definition of "Timezone Data" should mention other information that may be part of that data. I suggest appending the following text: ", and which may include other information such as time zone abbreviations".

The set of aliases may vary depending on the client and on whether timezone data is truncated (see Section 3.4). For example, a client located in Michigan may see "US/Eastern" as an alias for "America/Detroit?" whereas a client in New Jersey may see it as an alias for "America/New_York", and all three names may be aliases if timezones are truncated to post-2013 data.

Change History (3)

comment:1 Changed 8 years ago by lear@…

  • Description modified (diff)

comment:2 Changed 8 years ago by lear@…

  • Component set to service

Although the precise text above wasn't used, in my opinion, the author has addressed this by a change in the definition of Time Zone Data. Working group participants are encouraged to review the change.

comment:3 Changed 8 years ago by mglt.ietf@…

  • Resolution set to fixed
  • Status changed from new to closed

Section 1.2 has been modified consequently

Time Zone Data: Data that defines a single time zone, including an

identifier, UTC offset values, DST rules, and other information
such as time zone abbreviations;

Note: See TracTickets for help on using tickets.