[Tickets #12782] vCard export via CardDAV interface contains properties with empty values violating the spec
noreply at bugs.horde.org
noreply at bugs.horde.org
Tue Oct 22 13:32:37 UTC 2013
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: http://bugs.horde.org/ticket/12782
------------------------------------------------------------------------------
Ticket | 12782
Created By | ralf at kruedewagen.de
Summary | vCard export via CardDAV interface contains properties
| with empty values violating the spec
Queue | Turba
Version | 4.1.2
Type | Bug
State | Unconfirmed
Priority | 2. Medium
Milestone |
Patch |
Owners |
------------------------------------------------------------------------------
ralf at kruedewagen.de (2013-10-22 13:32) wrote:
When sending contact data to a CardDAV client, Horde 5 creates files like:
####################
BEGIN:VCARD
VERSION:3.0
UID:20131018104100.uYYOysmgwqS6tRPiYvf9wA1 at domain.de
NICKNAME:
X-EPOCSECONDNAME:
BDAY:
X-ANNIVERSARY:
X-SPOUSE:
PHOTO:
TZ;VALUE=text:
EMAIL;TYPE=INTERNET:
TEL;TYPE=HOME,VOICE:
TEL;TYPE=FAX,HOME:
TEL;TYPE=WORK,VOICE:
TEL;TYPE=CELL,VOICE:
TEL;TYPE=FAX:
TEL;TYPE=PAGER:
TITLE:
ROLE:
LOGO:
CATEGORIES:Business
NOTE:Eine Notiz
URL:
X-WV-ID:
N:ABC AG;;;;
FN:ABC AG
ORG:ABC AG;
ADR;TYPE=HOME:;;;;;;
ADR;TYPE=WORK:;;;;;;
END:VCARD
####################
There are many properties like BDAY (birthday) which have no value
assigned. This confuses some CardDAV sync clients like the well known
CardDAV-Sync app http://dmfs.org/carddav/. This sync clients sets
"01.01.1970" as birthday, which results in getting many wrong calendar
entries on Jan 1st.
According to discussions with the app developer and my own research on
common vCard file style, fields like "BDAY" must have a proper
property value assigned if they are given at all. The ABNF does
explicitly say that the value must be "date-value" or
"date-time-value" (not optional, i.e. not empty).
See specs:
http://tools.ietf.org/html/rfc2426#page-31
http://tools.ietf.org/html/rfc6350
Remark: Manual vCard exports of the address book do not contain those
properties with empty values. So, this is probably just related to the
CardDAV interface.
So, please just export properties which have a value (like the regular
address book export already does).
More information about the bugs
mailing list