Opened 8 years ago

Closed 8 years ago

#33 closed defect (fixed)

“substantive” change

Reported by: cyrus@… Owned by: draft-ietf-tzdist-service@…
Priority: major Milestone:
Component: service Version:
Severity: Active WG Document Keywords:


Current draft has:

When listing time zones, a timestamp is returned by the server, and
that can be used later by clients to determine if any "substantive"
change has occurred in the time zone data. Clients can use a
conditional "list" action (see Section 6.2), supplying a previous
timestamp value, to limit the results to time zones which have
changed in a "substantive" manner since that previous timestamp.
This allows clients to cache the last timestamp and to periodically
poll the server for possible changes.

A "substantive" change is one which affects the calculated onsets for
a time zone. Changes to properties such as a description are not
treated as a "substantive" change.

There has been debate on the list as to what exactly a “substantive” change is. We need to clarify this. Or alternatively do away with “substantive” and instead require any change, no matter how minor, to result in the corresponding tzid being reported as changed.

Change History (1)

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

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.