Hi Cyrus, On Wednesday, June 10, 2009 2:06 PM Cyrus Daboo wrote:
Hi Javier,--On June 10, 2009 11:55:55 AM -0300 Javier Godoy <rjgodoy at fich.unl.edu.ar> wrote: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",
Moving in that direction, BDAY and DDAY become special cases of DATE (in the same way we dropped AGENT in favor of RELATED) . I like the approach, though I'm also fine with BDAY + DDAY + ANNIVERSARY.
with the definition that the data supplied is implicitly a yearly recurring "event".
Not sure. Actually ANNIVERSARY is an euphemism for WEDDING-DAY (or any similar event other than wedding). This makes sense because complete dates (yyyymmdd) are allowed. On the other hand, --mmdd dates are (by definition) in the "implied year" (ISO 8601:2000 5.2.1.3.d), which would be the year when the event happened.
This case is similar to BDAY, which specifies the "birth date" instead of "birthday".
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.
In an ideal world, yes. But it is unlikely to expect systems implementing iCalendar only to record the anniversary date and some other information. Of course, if you need iCalendar-specific features (such as additional information about the "event", or tracking mutable dates) you should be usign iCalendar, but as long as the information is (almost) inmutable, I think it can find its place within vCard as DATE types or date-valued properties
Regards Javier