I\'m doing some work with an icalndar appointment generation; this would allow a delegate to view an event\'s website and click on a link provided to add an appointment to their
It is possible to update PUBLISH
ed entries. You do not need to change your METHOD
to REQUEST
(and set RSVP=FALSE
on every ATTENDEE
).
To have a new copy replace any existing one, all you need to do is bump the SEQUENCE
value. The SEQUENCE
property is primarily intended to differentiate between versions of an entry where something time related changed (e.g. DTSTART
).
However RFC 2445 does not preclude SEQUENCE
being bumped for any arbitrary reason (e.g. fixing a typo). Doing so would invalidate any workflow responses for the entry since they would be for lower SEQUENCE
values but in the PUBLISH
case there is no workflow really; its all one way.
If you are not making any time related changes to the entry then you can simply change the DTSTAMP
value to a newer one. The recipient will see they already have the UID
and SEQUENCE
value but an older DTSTAMP
, so they should simply update what they have already.
Anyone who fails to update a PUBLISH
ed entry when its SEQUENCE
or DTSTAMP
have been updated does not understand the standard or failed to implement it properly.