summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChristian Mollekopf <mollekopf@kolabsys.com>2012-03-07 00:56:04 (GMT)
committerChristian Mollekopf <mollekopf@kolabsys.com>2012-03-07 00:56:04 (GMT)
commitf74ff652afe14e6718807a0b1d96dcf1dcd63022 (patch)
treecf77bc58651f2da0f56cf144720baca989dc6af1
parentf98aab49ef45c282934ed8ef129675618dfbdbf8 (diff)
downloadkeps-f74ff652afe14e6718807a0b1d96dcf1dcd63022.tar.gz
Fix wording as suggested by Florian v. Samson, a couple of other fixes.
- Grammar - Note on how attachments should be handled.
-rw-r--r--KEP-0017.txt21
1 files changed, 11 insertions, 10 deletions
diff --git a/KEP-0017.txt b/KEP-0017.txt
index 7902106..7cc06f1 100644
--- a/KEP-0017.txt
+++ b/KEP-0017.txt
@@ -151,7 +151,7 @@ The classification '''MUST''' be one of "PRIVATE", "CONFIDENTIAL" and "PUBLIC".
* "CONFIDENTIAL": The object contains confidential information and is meant for an authorized group only.
* "PUBLIC": The object doesn't contain any private/confidential information and doesn't have to be handled with extra care.
-This property servers mainly the purpose of giving the user an indication how the contained information should be handled.
+This property serves mainly the purpose of giving the user an indication how the contained information should be handled.
Client implementations '''MAY''' behave differently depending on the classifcation of the object. The implementation '''SHOULD''' give the user an indication of the classification so he can act accordingly.
If the "Classification" property is absent, the client '''SHALL''' behave as if the classification was "PUBLIC".
@@ -319,12 +319,13 @@ Implements:
element text { "OPAQUE" | "TRANSPARENT" }
}
-''Specifies if an event shows up in freebusy time searches.''
+''Specifies, if an event is free/busy-relevant.''
-* "OPAQUE": The event is visible in freebusy time searchs.
-* "TRANSPARENT": The event is invisible in freebusy time searchs.
+* "OPAQUE": The event is visible in freebusy time searches.
+* "TRANSPARENT": The event is invisible in freebusy time searches.
If not specified this property '''SHALL''' default to "OPAQUE".
+Events with the transparency set to "TRANSPARENT" '''MUST NOT''' be used in any free/busy time searches/generation.
Implements:
* {{rfc|5545}} [https://tools.ietf.org/html/rfc5545#section-3.8.2.7 section-3.8.2.7]
@@ -335,7 +336,7 @@ Implements:
element integer { [[#Integer|xsd:integer]] }
}
-''The sequence number of the object''
+''The sequence number of the object.''
This property '''MUST''' be increased by one everytime the object is modified.
@@ -372,7 +373,7 @@ Implements:
element vtodo { [[#Todo|todo]] }
)
-''A recurrence exception overwrites properties of the base object in a specific recurrence of an event/todo''
+''A recurrence exception overwrites properties of the base object in a specific recurrence of an event/todo.''
A recurrence exception can be identified as exception by the presence of the [[#Recurrence ID]] property which '''MUST''' be specified on recurrence exceptions and '''MUST NOT''' be specified on the base object.
@@ -700,6 +701,8 @@ The binary content '''MUST''' be "Base 64"-encoded according to {{rfc|4648}}<ref
Implements:
* {{rfc|5545}} [https://tools.ietf.org/html/rfc5545#section-3.8.1.1 section-3.8.1.1]
+{{note|Attachments in separate Mimeparts|Attachments '''SHOULD''' be attached using a seperate Mime-Part. If this technique is used the Attachment '''MUST''' be referenced using the Content-Id(cid:) of the Mimepart in the uri element.}}
+
==== Alarm ====
property-trigger = element trigger {
@@ -861,8 +864,6 @@ Implements:
}?
}
-{{note|Needs clarification: transp|tranp has only TRANSPARENT or OPAQUE as state to differentiate if it should show up in F/B, but show-time-as is one of free, tentative, busy, or outofoffice. Not sure what show-time-as is good for though}}
-
''An object representing an event.''
* Content-Type: application/calendar+xml
@@ -1028,13 +1029,13 @@ Implements:
element uri { [[#URI inline encoding]] }
}
-''A a logo of the organization the contact is affiliated with''
+''A logo of the organization the contact is affiliated with''
Implements:
* {{rfc|6350}} [https://tools.ietf.org/html/rfc6350#section-6.6.3 section-6.6.3]
{{note|Implementation note: Roundcube|roundcube does not support this property, but only the photo}}
-{{note|Purpose|The purpose of this property was changed so the logo is now associated with the affiliated organization and not the "object the vCard presents" as the RFC puts it (thats how its used in kontact)}}
+{{note|Purpose|The purpose of this property was changed so the logo is now associated with the affiliated organization and not the "object the vCard presents" as the RFC puts it, which is how it is also used in Kontact}}
====== Title ======