RE: ISSUE-7: Gathering requirements [Calendar API]

On Sep 16, 2009, at 18:32 , Robin Berjon <robin@robineko.com> wrote:
> 
> On Sep 16, 2009, at 18:32 , 
> <richard.tibbett@orange-ftgroup.com> 
> <richard.tibbett@orange-ftgroup.com
>  > wrote:
> > Key Functionality:
> >
> > * Create a new calendar event
> > * Update an existing calendar event
> > * Remove an existing calendar event
> > * Find existing calendar events
> 
> This does not include support for multiple calendars, is that 
> intentional?
> 

Good point. I suggest multiple calendars should be supported. I have
also included a requirement below that says each calendar should be
uniquely identifiable by name (name probably being a straightforward
DOMString). This name should also maintain agnosticity of the given
calendar identifier from any given device (i.e. I see 'Home' working or
a URI scheme but 'C:/Home' does not). This may or may not be a good
requirement to add, any thoughts welcome on this of course.


Key Functionality:

* Get a list of calendars available
* Create a new calendar event
* Update an existing calendar event
* Remove an existing calendar event
* Find existing calendar events

* Calendar API 'event' objects MUST support a 1:1 mapping to iCalendar
VEVENT properties and values
* Calendar API 'calendar' objects MUST be uniquely identifiable by name




Assessing these requirements with the Calendar API inputs:

- both the BONDI [1] and Nokia [2] inputs support all of the key
functionality defined above but in programmatically different models.

- both the BONDI [1] and Nokia [2] inputs do not support a complete 1:1
mapping to iCalendar VEVENT properties and values (though the BONDI
'event' object does provide extensibility it mandates relatively simple
calendar information only).



[1] <http://bondi.omtp.org/modules/calendar.html> - BONDI Calendar API
[2]
<http://lists.w3.org/Archives/Public/public-device-apis/2009Apr/att-0001
/calendar.html> - Nokia Calendar API

Received on Wednesday, 30 September 2009 09:26:59 UTC