summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChristian Mollekopf <mollekopf@kolabsys.com>2012-03-16 16:21:55 (GMT)
committerChristian Mollekopf <mollekopf@kolabsys.com>2012-03-16 16:21:55 (GMT)
commit70af06a04c8ab2f712739c4a99ad698645030f96 (patch)
treed9548f7244ea90495ca60e3759ef9470bca1d815
parent6f9f04580730146c7f16b5904eed2ccb21d62646 (diff)
downloadkeps-70af06a04c8ab2f712739c4a99ad698645030f96.tar.gz
Removed x-uid uses, some notes for x-properties. Allow the use of either urn or mailto.
-rw-r--r--KEP-0017.txt68
1 files changed, 35 insertions, 33 deletions
diff --git a/KEP-0017.txt b/KEP-0017.txt
index cb4ac52..1319466 100644
--- a/KEP-0017.txt
+++ b/KEP-0017.txt
@@ -602,12 +602,12 @@ Implements:
element parameters {
element cn { element text { [[#String]] } } ?
} ?,
- element cal-address { [[#Mailto URL]] }
+ element cal-address { [[#Contact URI]] }
}
''The organizer of the incidence.''
-The cal-address '''MUST''' be a [[#Mailto URL]] email address.
+The cal-address '''MUST''' be a valid [[#Contact URI]].
* The cn parameter '''SHALL''' represent the display name of the organizer.
@@ -617,9 +617,6 @@ Implements:
===== Contact =====
property-contact = element contact {
- element parameters {
- element x-uid { [[#UID|text-uid]] } ?
- } ?,
element text { [[#String]] }
}
@@ -627,13 +624,10 @@ Implements:
The text property '''SHOULD''' contain the name of the contact.
-* "x-uid": This parameter '''MAY''' be used to refer to the [[#Contact]] object of the contact. This parameter '''MUST''' contain the [[#UID]] of a [[#Contact]] if specified.
-
Implements:
* {{rfc|5545}} [https://tools.ietf.org/html/rfc5545#section-3.8.4.2 section-3.8.4.2]
{{note|Needs clarification: Useless?|not sure if we need this property (dont know where it is used).}}
-{{note|Needs clarification: x-uid|not sure if the x-uid is valid, see attendee. Specifying the uid separately helps clients to display something if they are not able to lookup the other contact.}}
===== Attendee =====
@@ -653,15 +647,14 @@ Implements:
"REQ-PARTICIPANT" |
"OPT-PARTICIPANT" |
"NON-PARTICIPANT"
- } } ?,
- element x-uid { [[#UID|text-uid]]] } ?
+ } } ?
}?,
- element cal-address { [[#Mailto URL]] }
+ element cal-address { [[#Contact URI]] }
}
''An attendee of an event.''
-The cal-address '''MUST''' be a [[#Mailto URL]] email address.
+The cal-address '''MUST''' be a valid [[#Contact URI]].
* "cn": The display name of the contact.
* "rsvp": Used by the [[#Organizer]] to request a participation status reply from an attendee of a group-scheduled event or to-do. This parameter '''SHALL''' default to "FALSE" if not specified.
@@ -676,12 +669,10 @@ The cal-address '''MUST''' be a [[#Mailto URL]] email address.
:* "REQ-PARTICIPANT": Indicates a participant whose participation is required.
:* "OPT-PARTICIPANT": Indicates a participant whose participation is optional.
:* "NON-PARTICIPANT": Indicates a participant who is copied for information purposes only.
-* "x-uid": This propery may '''MAY''' be used to refer to the [[#Contact]] object of the attendee. The x-uid '''MUST''' contain the globally unique [[#UID]] of a [[#Contact]] if specified, internally used UID's '''MUST NOT''' be used.
Implements:
* {{rfc|5545}} [https://tools.ietf.org/html/rfc5545#section-3.8.4.1 section-3.8.4.1]
-{{note|Needs clarification: x-uid param| instead of cal-address as uid? This is what kontact does with X-UID=30f35c1792c219de35c07d91456f1208 used in kontact. x-uid might not work this way because kontact uses the internal uid in this field.}}
{{note|Needs clarification: LDAP|There would be an additonal dir parameter for an ldap uri available. useful?}}
{{note|Needs clarification: cutype|For "resource" role? i.e. a meeting room. Currently this is not possible and it was in the old format specification. But I don't know if this is used anywhere.}}
@@ -711,6 +702,7 @@ 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.}}
+{{note|x-label|This property should be replaced with something standard compliant or added to the official standard.}}
==== Alarm ====
@@ -739,7 +731,7 @@ If a date-time value is used it '''MUST''' be in UTC.
element action { text { "EMAIL" } },
element summary { [[#Summary]] },
element description { [[#Description]] },
- element attendee { element cal-address { [[#Mailto URL]] } } +,
+ element attendee { element cal-address { [[#Contact URI]] } } +,
property-trigger,
(
element duration { [[#Duration]] },
@@ -1116,6 +1108,7 @@ Implements:
* {{rfc|6350}} [https://tools.ietf.org/html/rfc6350#section-6.7.8 section-6.7.8]
{{note|RFC conflict|RFC 6351 permits only home, work types although RFC 6350 permits own x-values. An erratum has been submitted and confirmed.}}
+{{note|x-blog|This property should be replaced with something standard compliant or added to the official standard.}}
===== Address =====
@@ -1181,11 +1174,14 @@ Implements:
} +
}?
}?,
- ( element uri { [[#URI|xsd:anyURI]] } | element text { [[#String]] } )
+ ( element uri { [[#UID|uri-uid]] } | element text { [[#String]] } )
}
''Specifies a relation of the contact to another contact.''
+Clients SHALL use a [[#UID|uri-uid]] to reference a Contact object when using the uri element.
+Clients MUST be able to deal with [[#UID|uri-uid]].
+
Types:
* "spouse": Specifies that the related contact is the spouse of this contact.
* "child": Specifies that the related contact is the child of this contact.
@@ -1193,7 +1189,6 @@ Types:
Implements:
* {{rfc|6350}} [https://tools.ietf.org/html/rfc6350#section-6.6.6 section-6.6.6]
-{{note|Needs clarification: uri|maybe we should us x-uid instead of uri as well which can be specified additionally to the text. This way clients which dont support getting the name from a nother object can still display the name.}}
{{note|Needs clarification: manager/assistat|extend for manager and assistant (in which case this should be added to the affiliation group as well? This would obsolete the x-manager x-assistant properties}}
===== Birthday =====
@@ -1399,30 +1394,18 @@ Uses:
{{note|Opaque signing|Opaque signing refers to the technique of embedding the text into the base64 encoded CMS (PKCS #7 based Cryptographic Message Syntax) object (content type: application/x-pkcs7-mime) of the signature, so it can only be read if the client supports S/MIME. Clear signing transmits the clear text and only appends the signature (content type: application/x-pkcs7-signature), which allows clients without S/MIME support to read the message.}}
{{note|Needs clarification: Key storage|Im not sure yet how the key should be stored. Im also dont think the application/pkcs7-mime mimetype is correct for the key itself.}}
{{note|Needs clarification: allowed|Is this correct that it is only for incoming content? (the allowed element is derived from the KAddressbook Crypto settings page)}}
+{{note|x-crypto|This property is missing in the xCard standard and should be added to it.}}
+{{note|identities|Ideally crypto settings would be per identity and not per contact.}}
===== Member =====
property-member = element member {
- element parameters { element x-uid { [[#UID|uri-uid]] } ? } ?,
- element uri { [[#Mailto URL]] }
+ element uri { [[#Contact URI]] }
}
''A member of the distribution list.''
-A member '''MUST''' contain a [[#Mailto URL]].
-
-The name of the member '''MAY''' be embedded in the email address as specified in {{rfc|822}}<ref name="rfc822">{{rfc|822}} Standard for ARPA Internet Text Messages</ref> [https://tools.ietf.org/html/rfc822#section-6.1 section-6.1].
-In case the name is included, URL-reserved characters '''MUST''' be encoded.
-
-Example:
-
- mailto:John%20Doe%3cjdoe@example.com%3e
-
- <member>
- <uri>"mailto:John%20Doe%3cjdoe@example.com%3e"</uri>
- </member>
-
-* "x-uid": This parameter '''MAY''' be used to refer to the [[#Contact]] object of the member. This parameter '''MUST''' contain the [[#UID]] of a [[#Contact]] if specified. In case this parameter is used, the mailto: email address remains authorative for distribution-list usage. Clients '''MUST NOT''' use an email address from a referenced contact directly in this case.
+A member '''MUST''' contain a valid [[#Contact URI]].
Implements:
* {{rfc|6350}} [https://tools.ietf.org/html/rfc6350#section-6.6.5 section-6.6.5]
@@ -1479,6 +1462,7 @@ Implements:
{{note|Obsoletion of KEP 13|This obsoletes draft [[KEP:13]]<ref name="kep13">[[KEP:13]] Update contact object (Draft)</ref> as this update will fully replace everything that KEP would have addressed.}}
{{note|Needs clarification: Attachment| Do we need an attachment property? There is none in the RFC and RC and KAddressbook dont use attachments for contacts}}
+{{note|Identities| Contacts currently lack the notion of different identities of the same person, respectively don't support a Person/Identities modeling.}}
==== Distribution List ====
@@ -1721,6 +1705,24 @@ The uri scheme '''MUST''' be according to {{rfc|2397}}<ref name="rfc2397">{{rfc|
A mailto url '''MUST''' conform to {{rfc|6068}}<ref name="rfc6068">{{rfc|6068}} The 'mailto' URI Scheme</ref>.
+The name of the contact '''MAY''' be embedded in the email address as specified in {{rfc|822}}<ref name="rfc822">{{rfc|822}} Standard for ARPA Internet Text Messages</ref> [https://tools.ietf.org/html/rfc822#section-6.1 section-6.1].
+This technique '''SHALL''' only be used if no other means to indicate the name are available.
+In case the name is included, URL-reserved characters '''MUST''' be encoded.
+
+Example:
+
+ mailto:John%20Doe%3cjdoe@example.com%3e
+
+== Contact URI ==
+
+ value-uri = xsd:AnyURI
+
+''Any URI which is somehow relevant to identify/contact a Contact.''
+
+Clients SHALL either use a [[#UID|uri-uid]] to reference a Contact object or a [[#Mailto URL]] to specify a single email address.
+Clients MUST be able to deal with both [[#UID|uri-uid]] and [[#Mailto URL]].
+
+
==== Geo URI ====
A geographic location identifier '''MUST''' conform to {{rfc|5870}}<ref name="rfc5870">{{rfc|5870}} A Uniform Resource Identifier for Geographic Locations ('geo' URI)</ref>.