The file is created in the same way as the ics source file. The status of the event will be different. The UID will identify the event, and the sequence number will indicate the priority of the update, and then the details of the event (changes or cancellations) will be marked
If you want to change / cancel the event after sending the invitation, you need to determine the event / destination by its UID and allocate a higher SEQUENCE number than the original ics event.
UID (unique identifier): http://tools.ietf.org/html/rfc5545#page-117
Sequence: http://tools.ietf.org/html/rfc5545#page-138
and set the status of the event
/ "CANCELLED" ;Indicates event was cancelled.
Status: http://tools.ietf.org/html/rfc5545#page-92
oh - and method If you need to send an event cancel, the UID must be the same as the original event, and the component properties must be set to cancel Ex. METHOD: CANCEL STATUS: CANCEL
Of course, this will only “cancel” the event, if the recipient then actually clicks to download / subscribe to one calendar application for the first time. For applications that “signed” the remote ics — the next time they check for “updates,” the update must be processed and overwrite the original event.
source share