- From: Dominique Hazael-Massieux <dom@w3.org>
- Date: Wed, 27 Jan 2010 11:32:58 +0100
- To: richard.tibbett@orange-ftgroup.com
- Cc: public-device-apis@w3.org, schitturi@rim.com
Le vendredi 22 janvier 2010 à 15:10 +0100, richard.tibbett@orange-ftgroup.com a écrit : > The first editor's draft of the Calendar API is now available: > http://dev.w3.org/2009/dap/calendar/ I think this is a great start, thanks! A few early comments: • converting all date and times into UTC timestamps prevents having recurring events in a given timezone; typically, our DAP WG calls are recurring in the US Eastern Timezone, but I don't know that you could create such an event with the current API (nor how they would get converted to the relevant object by an implementation) • recurrent events need to have exceptions; the Nokia API had "attribute sequence<DOMTimeStamp> exceptionDates;" http://lists.w3.org/Archives/Public/public-device-apis/2009Apr/att-0001/calendar.html#calendar_entry_interface • recurrent events needs an interval (e.g. for events that occur every two weeks): the Nokia API has it • the Nokia API had also instanceStartTime for recurring events; I'm not entirely sure if it's needed in addition to the base start/end times of the base event • I think CalendarOptions should probably be renamed to CalendarSearchFilter (as a note suggested similarly in the contacts API) Dom
Received on Wednesday, 27 January 2010 10:33:10 UTC