[Standards] Date time values in XEP54, vcard?

Florian Zeitz florian.zeitz at gmx.de
Wed Oct 13 11:57:03 UTC 2010

Hash: SHA1

Am 12.10.2010 21:35, schrieb Peter Flindt:
> Hello,
> seems to me http://xmpp.org/extensions/xep-0054.html contain some false
> examples (And the RFC http://tools.ietf.org/html/rfc2426 too)
> E.g. from the XEP:
> <BDAY>1966-08-06</BDAY>
> Example in the RFC:
> BDAY:1996-04-15
> BUT:
> http://datatracker.ietf.org/doc/draft-ietf-vcarddav-vcardrev/ and
> http://dotat.at/tmp/ISO_8601-2004_E.pdf
> Say the format is the ISO basic format YYYYMMDD
You are comparing apples and oranges here. draft-ietf-vcarddav-vcardrev
is a new revised version of the vCard specification. It has changed the
date format.
The older vCard specification XEP--0056 is based on references
http://tools.ietf.org/html/rfc2425 which defines:
   date = date-fullyear ["-"] date-month ["-"] date-mday

Take note that currently when dealing with vCards in XMPP your dealing
with a format that was a) never finished and b) isn't optimal or well
defined at all (as is noted in the XEP I think). Therefore vcard-temp

> The format 1966-08-06 is US specific, here in Germany it's 08.06.1966
> as a result the field for the birthday is an text input field where the
> user can enter anything and the other side display it in text too, or
> try to convert the textformat in a local format, that can fail too.
Indeed clients tend to treat BDAY as a text field. Strictly speaking it
should use the YYYY-MM-DD format though. I would recommend you let the
user only set dates of that form, but parse incoming values as a text
filed (which indeed may not allow for interpretation, but only display).

> I guess the phone numbers in the vCard have a standard too and I not
> trust the example <NUMBER>303-555-1212</NUMBER>.
> However, what should a client do?
> Peter
- --
Version: GnuPG v1.4.10 (GNU/Linux)


More information about the Standards mailing list