Foreword

This document incorporates by reference the CalConnect Intellectual Property Rights, Appropriate Usage, Trademarks and Disclaimer of Warranty for External (Public) Documents as located at

http://www.calconnect.org/documents/disclaimerpublic.pdf.

January 2005 CalConnect Interoperability Test Scenarios

1. Basic Calendar Access Test Scenarios

1.1. Event creation

1.1.1.

Create new single-instance meeting titled “Meeting 1.1” with the location “Seattle”.

1.1.2.

Create new meeting titled “Meeting 1.2” recurring every Monday from 10:00 AM to 11:00 AM for 4 weeks.

1.1.3.

Create new single-instance meeting titled “Meeting 1.3” with 2 other attendees.

1.1.4.

Create new single-instance meeting titled “Meeting 1.4” with an alarm set to trigger 15 minutes prior to the schedule time of the meeting.

1.2. Event modification

1.2.1.

Modify the title of meeting “Meeting 1.1” to “Meeting 1.1bis”.

1.2.2.

Modify the location of the meeting “Meeting 1.1bis” to “Seattle bis”.

1.2.3.

Reschedule meeting “Meeting 1.1bis” to the next day.

1.2.4.

Add an attendee to “Meeting 1.1bis”.

1.2.5.

Add an alarm to “Meeting 1.1bis”.

1.2.6.

Modify the title of the 1st instance of the recurring meeting created in Clause 1.1.2.

1.2.7.

Modify the participation status of

1.2.8.

Cancel the 4th instance of the recurring meeting created in Clause 1.1.2.

1.2.9.

One client changes “Meeting 1.1bis” to a different time, second client ‘refreshes’ its display to see the modification.

1.3. Event retrieval

1.3.1.

Retrieve all the components and properties of the meetings scheduled for the current day (i.e., midnight to midnight local time).

1.3.2.

Retrieve all the components and properties of the meetings scheduled for the current week.

1.3.3.

Retrieve all the components and properties of the meetings scheduled for the current month.

1.3.4.

Retrieve only the SUMMARY, DTSTART and DTEND (or DURATION) properties of the meetings scheduled for the current week.