Issue86

Title iTIP: Enhance description of SEQUENCE
Priority urgent Status in-progress
Superseder Nosy List cyrusdaboo
Assigned To cyrusdaboo Topics rfc2446bis

Created on 2007-09-13.13:35:27 by cyrusdaboo, last changed 2008-05-12.02:09:04 by cyrusdaboo.

Messages
msg279 (view) Author: cyrusdaboo Date: 2008-05-12.02:09:04
New text proposed on the list. Some minor feedback received and tweaks done. Will 
be includes in the next draft.
msg270 (view) Author: lear Date: 2007-11-07.15:18:07
cyrus to propose text to clarify.
msg262 (view) Author: cyrusdaboo Date: 2007-09-13.13:35:27
SEQUENCE is used as a synchronization aid and as a change indicator.

However as a synchronization aid we already have DTSTAMP.

However as a change indicator there is already a requirement that attendee CUAs 
have to spot significant changes that are relevant to their calendar user, so 
SEQUENCE is not important.

Proposal: deprecate use of SEQUENCE.

At the very least if we choose not to do that, we should be much more explicit 
about when SEQUENCE is supposed to change (e.g. ORGANIZER MUST change SEQUENCE 
for these things (...) and SHOULD change SEQUENCE for these things (...) under 
certain circumstances.
History
Date User Action Args
2008-05-12 02:09:04cyrusdaboosetstatus: notext -> in-progress
messages: + msg279
2008-01-09 14:45:06learsettitle: iTIP: DEPRECATE SEQUENCE -> iTIP: Enhance description of SEQUENCE
2007-11-07 15:18:07learsetstatus: Discuss -> notext
messages: + msg270
2007-09-13 14:19:05learsettopic: + rfc2446bis
assignedto: cyrusdaboo
title: iTIP: SEQUENCE -> iTIP: DEPRECATE SEQUENCE
2007-09-13 13:35:27cyrusdaboocreate