W3C home > Mailing lists > Public > public-device-apis@w3.org > December 2009

[Calendar API] Draft Use Cases and Requirements

From: Suresh Chitturi <schitturi@rim.com>
Date: Wed, 16 Dec 2009 17:09:59 -0500
Message-ID: <B35D8F122C08BC43BBA1D02713D2BB5D0868C0CD@XCH69YKF.rim.net>
To: <public-device-apis@w3.org>
Dear all,

 

Here are some draft use cases and requirements for Calendar API as
promised. If the group is fine with this list, they will be added to the
Editor's draft.

 

Use Case 1: A web application would like to access the device calendar

 

A Web Application on behalf of the user would like to access the user's
device calendar so it can be presented to the user in the context of
browsing a Web Application. For example, the user is in the process of
completing an online flight reservation and would like to view the
device calendar to check his/her schedule.

 

Use Case 2: A user would like to create/modify/delete a Calendar
appointment 

 

A user of the Web Application would like to create a new Calendar
appointment with details (e.g. subject, location, start/end time,
description, and note) and add it to his/her device calendar. Later the
user may wish to modify the existing appointment with new details and
save it, or may decide to delete it after the event has occurred or is
no longer valid.

 

Use Case 3: A user would like to enter a birthday of his friend with a
recurrence event

 

A user of the Web Application meets his/her close friend and learns
about his/her birth date, and would like to enter it to the device
calendar with the ability to set a recurrence appointment such that
he/she is reminded of the birthday every year. This will allow the user
to take an action such as send a greeting card, a phone call to wish
his/her friend, etc.

 

Use Case 4: A user would like to set a reminder for upcoming events.

 

A user of the Web Application is shopping online (e.g. auction site) and
would like to be reminded 5 minutes prior to the auction is closed so he
may wish to change his bid price. Or the user has a meeting with his
doctor and would like to be reminded one hour prior to the appointment
that may allow him to prepare for the appointment.

 

Use Case 5: A user would like to create and add attendees to a Calendar
appointment

 

A user of the Web Application, in addition to creating a Calendar
appointment would like to add attendees that he/she wishes to meet or
invite. For example, a user is trying to organize a meeting and would
like to create an appointment and invite his/her friends for the meeting
after populating the meeting details.

 

 

Requirements:

 

1) The Calendar API MUST provide access to the device Calendar.

2) The Calendar API MUST support CRUD operations on individual Calendar
entries (e.g. create, add, delete, update)

3) The Calendar API MUST provide the ability to set a reminder on per
Calendar entry basis.

4) The Calendar API MUST provide the ability to set a recurrence
function on per Calendar entry basis.

5) The Calendar API MUST provide search capabilities (e.g. finding a
calendar entry based on key words, calendar entry parameters).

6) The Calendar API MUST provide the ability to add attendees to a
Calendar appointment.

 

Regards,

Suresh 

 


---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
Received on Wednesday, 16 December 2009 22:10:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:14:03 GMT