summaryrefslogtreecommitdiff
path: root/KEP-0003.txt
diff options
context:
space:
mode:
authorGeorg C. F. Greve <greve@kolabsys.com>2010-11-25 15:57:31 (GMT)
committerGeorg C. F. Greve <greve@kolabsys.com>2010-11-25 15:57:31 (GMT)
commit84ca5c237eeb2da5d7a57951bf7de75d6a1bc137 (patch)
tree70c11b66ce78f3d956457295287e729cf71799c5 /KEP-0003.txt
parent15cb1e7cc85b9501b7def3ad7762067b928c3a49 (diff)
downloadkeps-84ca5c237eeb2da5d7a57951bf7de75d6a1bc137.tar.gz
Minor formatting update, make this explicit for event XML 1.1
Diffstat (limited to 'KEP-0003.txt')
-rw-r--r--KEP-0003.txt24
1 files changed, 7 insertions, 17 deletions
diff --git a/KEP-0003.txt b/KEP-0003.txt
index 8a4c4a5..eb382ca 100644
--- a/KEP-0003.txt
+++ b/KEP-0003.txt
@@ -1,6 +1,6 @@
{{kep
|number=3
- |ticketnumber=31
+ |ticketnumber=
|title=Introduction of 'subevent' sub-tag for 'exclusion' from 'recurrence'
|author=Georg Greve
|author_email=greve@kolabsys.com
@@ -22,14 +22,14 @@ The solution is to introduce a hierarchically nested 'subevent' sub-tag for an e
== Update to the XML Format ==
-The type for datetime storage in Kolab XML is modified as follows:
+The following changes for recurrence storage in Kolab XML is part of the changest for version 1.1 of the 'event' object:
* Clients '''MUST''' treat the date of the 'exclusion' as the Recurrence ID<ref name="rfc2445">[[RFC:2445 | RFC2445: Internet Calendaring and Scheduling Core Object Specification, 4.8.4.4 Recurrence ID]]</ref> where applicable, in particular iTIP<ref name="rfc2446">[[RFC:2446 | RFC2446: iCalendar Transport-Independent Interoperability Protocol (iTIP)]]</ref> handling.
* A 'subevent' XML tag '''MAY''' be added hierarchically nested within an 'exclusion' to a 'recurrence' of an 'event' object.
-* There '''MUST''' be only one 'subevent' per 'exclusion.
+* There '''MAY''' be only one 'subevent' per 'exclusion'.
* All event values of the 'subevent' default to the 'event' within which it is nested. Values within 'subevent' change these values for this 'exception' from the 'recurrence' only.
-* Fields for 'event' that 'subevent' '''MUST NOT''' use/override are: *'uid'* and *'recurrence'*
-* Fields that 'subevent' '''MUST''' define are: *'creation-date'* and *'last-modification-date'*
+* Fields for 'event' that 'subevent' '''MUST NOT''' specify are: 'uid' and 'recurrence'
+* Fields that 'subevent' '''MUST''' define are: 'creation-date' and 'last-modification-date'
=== Example ===
@@ -37,32 +37,22 @@ Moving one instance of a recurring event from date1, a normal date in the recurr
<event>
...
-
<recurrence>
...
-
<exclusion>date1
-
<subevent>
-
<start-date>new-date1</start-date>
-
</subevent>
-
</exclusion>
-
</recurrence>
-
</event>
== Upgrade Path ==
-When this KEP becomes active, the version number of the Kolab Storage Format specification will be updated to 2.1.
-
-New clients that correspond to 2.1 will be fully compatible with older data sets.
+New clients that correspond to 'event' objects of version 1.1 will be fully compatible with older data sets.
-Older clients can continue to behave as before at their own choice, and will remain consistent with the 2.0 specification and no data will be lost or corrupted. So whilst this is important, it is not urgent. Older clients will however not be able to display recurrence exceptions of newer clients properly, so it is highly recommended to move to the newer 2.1 format when feasible.
+Older clients can continue to behave as before at their own choice, and will remain consistent with the 1.0 version and no data will be lost or corrupted. So whilst this is important, it is not urgent. Older clients will however not be able to display recurrence exceptions of newer clients properly, so it is highly recommended to move to the newer format whenever feasible.
== References ==