© 2007 The Calendaring and Scheduling Consortium, Inc.
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior written permission. Permission can be requested from the address below.
The Calendaring and Scheduling Consortium, Inc.
4390 Chaffin Lane
McKinleyville
California 95519
United States of America
www.calconnect.org
This document incorporates by reference the CalConnect Intellectual Property Rights, Appropriate Usage, Trademarks and Disclaimer of Warranty for External (Public) Documents as located at
.
This document contains notes and results from the May 2007 calendar interoperability event, sponsored by Boeing, held in Seattle Washington. The basic purpose of the event was to test CALDAV Free Busy and Scheduling and iCalendar iMIP and iTIP events.
The chart below shows the attendees, their organization and the products they were testing.
| Attendees | Organization | Products |
|---|---|---|
| Cyrus Daboo | Apple | Apple Client and CALDAV server |
| Michael Douglass | RPI | Bedework CALDAV Server |
| Daniel Boelzle | Mozilla | Lightning and Thunderbird Calendar clients |
| Tony Becker | Marware | Marware Calendar |
| Mikeal Rogers | OSAF | Cosmo CALDAV server and Chandler Client |
| Daniel Rauschenbach | Synchronica | CALDAV Server |
The following applications and products were tested:
Four CALDAV servers — RPI, Oracle, Apple and OSAF (Cosmo)
Four CALDAV clients — OSAF (Chandler), Mozilla, Marware and Apple
iCalendar interoperability — Mozilla and Apple
The focus of this event was Free Busy and Scheduling testing in CALDAV. As more and more clients are adding in the features, we are able to test more of the spec. During testing, bugs in code were found and noted. One of the benefits of interoperability testing is to stress test implementations in a controlled environment. Each product found situations where they need to go back and adjust their implementations in order to improve interoperability.
Examples of what is tested:
Connection to all CALDAV servers from all clients.
Successfully publishing events
Publishing separate calendars
Handling of errors and authentication
Examples of issues found are:
Serialization of all requests
Handling of Mkcalendar
Products not showing first instances
Not handling EXDATE=a,b,c
Fetching ETags on non-existing resources when adding items
Error reporting
Weekly recurring event 4 times — Queries “in between” weeks return no results
Deleting recurring event with multiple overridden instances
UI handling of switching between recurring event with count (1.2) that do not update the recurrence field
Deleting some instances, then changing the whole event into an all-day daily recurring one failed (err 500)
A server that seems to filter out a VALARM and doesn’t write it.
We continue to have good results testing CALDAV clients and servers. General comments again are that it is always good to have interops in person. The ability to stress test in a controlled, “safe” environment is a plus.
The aim of the next interop is to test more CALDAV Scheduling features.
Respectfully submitted,
Pat Egen,
Interoperability Event Manager