2 commits - KEP-0009.txt
Georg Greve
greve at kolabsys.com
Thu Aug 25 13:22:25 CEST 2011
KEP-0009.txt | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
New commits:
commit ac52cb17fd6a00f9c21482c0d2fff2f923540c1f
Merge: acb6ecb... d7ab22c...
Author: Georg Greve <greve at kolabsys.com>
Date: Thu Aug 25 13:22:12 2011 +0200
Merge branch 'master' of ssh://git.kolabsys.com/git/keps
commit acb6ecb4ac7eeb337138752b8895aea85d429f8b
Author: Georg Greve <greve at kolabsys.com>
Date: Thu Aug 25 13:22:03 2011 +0200
Fixed RFC number & some language improvement, courtesy by Jeroen
diff --git a/KEP-0009.txt b/KEP-0009.txt
index ee99907..79dd9e8 100644
--- a/KEP-0009.txt
+++ b/KEP-0009.txt
@@ -34,9 +34,9 @@ form part of the comprehensive toolset for storing configuration and application
This is a '''new''' mechanism:
-=== IMAP ANNOTATE RFC 5256 message annotations ===
+=== IMAP ANNOTATE RFC 5257 message annotations ===
-The Kolab Groupware Solution currently does not make use of message annotations according to {{rfc|5256}} <ref name="rfc5256">{{rfc|5256|title=Internet Message Access Protocol - ANNOTATE Extension}}</ref>, but it has been argued that in some cases such annotations would be the most efficient approach, e.g. single-message encryption and ACL scenarios of groupware items.
+The Kolab Groupware Solution currently does not make use of message annotations according to {{rfc|5257}} <ref name="rfc5257">{{rfc|5257|title=Internet Message Access Protocol - ANNOTATE Extension}}</ref>, but it has been argued that in some cases such annotations would be the most efficient approach, e.g. single-message encryption and ACL scenarios of groupware items.
As this mechanism is closely related on a conceptual level to the folder annotations according to RFC 5464 it shall inherit all the general rules for usage of RFC 5464 folder annotations defined below.
@@ -52,7 +52,7 @@ With application of this changeset against the Kolab Format 2.0, all clients '''
=== Public and private annotations ===
-RFC 5464 provides means for public and private annotations. Both kinds MAY be used in the Kolab Groupware Solution, but each annotations usage in all namespaces MUST be defined in a single KEP to avoid namespace confusion.
+RFC 5464 provides means for public and private annotations. Both kinds MAY be used in the Kolab Groupware Solution, but use of each annotation MUST be defined in a single KEP for all prefixes.
=== Values ===
More information about the commits
mailing list