Hi Javier,--On June 10, 2009 11:55:55 AM -0300 Javier Godoy <rjgodoy at fich.unl.edu.ar> wrote:
As far as I can see, neither DRINK, AN, nor CAR fit any of these.+1 for not including DRINK and CAR in the core spec. About AN, I think it is a common use case. There are already different X-properties for representing this information (e.g. X-ANNIVERSARY, X-EVOLUTION-ANNIVERSARY). Besides, some contact management software, such as Outlook (whose vCard implementation is rather incomplete) allows an anniversary date.
I don't really want to re-invent iCalendar in vCard (really) but perhaps we should generalize this a little bit more. How about a "DATES" property which can include a TYPE parameter which initially we define a single value for: "ANNIVERSARY", with the definition that the data supplied is implicitly a yearly recurring "event".
However, a question is whether data like this really belongs in an address book vs a calendar. Maybe the vCard should have a pointer to an iCalendar object containing "personal" dates like this. Ultimately the vcard data is likely to be "imported" into a calendar so that alarms and other annotations could be added.
-- Cyrus Daboo