- From: <richard.tibbett@orange-ftgroup.com>
- Date: Thu, 18 Mar 2010 11:56:08 +0100
- To: <chan@etri.re.kr>, <public-device-apis@w3.org>
- Message-ID: <31b401cac689$9febbee0$0501400a@rd.francetelecom.fr>
Hi Kangchan, My thought on this is seperating storage from usage is the way to go. For example, conversion functions on the ECMA date object would be sufficient for runtime conversion between calendaring systems. This gets more interesting when we get to recurring events. I suggest that lunar dates can be captured in the recurence object, only that lunar based recurrence will result in more verbose recurrence objects (i.e. converting lunar recurrences to solar dates and storing those specific dates as part of the recurrence object). We still have some work to do around dates but iCalendar and vCard not supporting lunar dates is telling..and I don't believe that's an oversight on their part - rather that conversion is a sufficient solution. - Richard ??? <chan@etri.re.kr> wrote: Dear all, I reviewed Icalendar[1][2][3], Vcalendar[4], Vcard[5][6], and there is not supporting Lunisolar Calendar on those specifications. [1] http://www.absoluteastronomy.com/topics/ICalendar [2] http://en.wikipedia.org/wiki/ICalendar [3] http://tools.ietf.org/html/rfc5545 [4] http://en.wikipedia.org/wiki/ICalendar#vCalendar_1.0 [5] http://en.wikipedia.org/wiki/VCard [6] http://www.imc.org/pdi/vcard-21.doc Best Regards, Kangchan ----- ------------------------------------------------------------- Kangchan Lee, Ph.D. ETRI, Protocol Engineering Center 161 Kajong-Dong, Yusong-Gu, Daejeon, 305-700, South Korea Voice : +82-42-860-6659, FAX : +82-42-861-5404 E-mail : chan@etri.re.kr, chan@w3.org -------------------------------------------------------------
Received on Thursday, 18 March 2010 10:56:41 UTC