Minutes Minutes

T H E C A L E N D A R I N G A N D S C H E D U L I N G C O N S O R T I U M CCaallCCoonnnneecctt

Volume 5, Issue 3 October 2012

From the Executive Director

Dear Members, • Calendaring futures and CalConnect • CalConnect XXVII, June 3-7, 2013, directions University of Wisconsin, Madison, CalConnect events generally consist of Wisconsin two parts: the first half of the week is • Internationalization/Localization for interoperability testing, and the last half calendaring • CalConnect XXVIII, Autumn, 2013, is the Roundtable Technical data TBD Conference. At CalConnect XXV in Zurich, our second full CalConnect • Best practices Based on the success of this event event in Europe, for publishing and last year’s European event in nearly everyone iCalendar data Innovation Prague, we are looking forward to who participated to ensure CalConnect in the optimum interoperability XXVIII being interoperability hosted in Europe, • BOF on VTODOs Tests testing stayed for and are soliciting the Roundtable, • BOF on Consensus Scheduling offers to host the Events and we had a few additional event from our participants, making a total of 26 at the Following the BOF on VTODOs, a European members. We hope to be Roundtable, of which 17 were VTODO Ad Hoc able to announce the week, city, and European, overall representing 11 Committee was host by our next event at Oracle in late members and 5 observers (prospective formed to January. examine members). Members requirements and CalConnect’s European events are ongoing work on restructured to move the formal VTODOs and recommend future technical committee sessions to the activity in this area to CalConnect. The afternoon (to allow remote attendance Ad Hoc committee will report out at Dave Thewlis from North America), and special Roundtable XXVI. symposia and BOFs (birds of a feather sessions) are offered on Thursday and More detail about the event may be Friday mornings. The special offerings found at Report on Roundtable XXV. this time were: Next CalConnect events: • Improving the web calendaring • CalConnect XXVI, January 28- experience for end users February 1, 2013, Oracle, Santa Clara, California

CalConnect XXVI

Oracle Corporation  Santa Clara, California

Interoperability Test Event  January 28 - 30

Roundtable XXVI  January 30 - February 1

Inside this Minutes:

• Executive Director’s Letter – page 1  New Members Welcome – page 5

• Interop Report – page 2  CalConnect XXV photos – page 6 • Tech Committees Summaries – pages 3 & 4  About CalConnect – page 7

M i n u t e s Page 2

C a l C o n n e c t T H E C A L E N D A R I N G A N D S C H E D U L I N G C O N S O R T I U M

October 2012

Interop Report

 DaviCal  Problems with content type  Oracle (Oracle Communications  Redirections causing issues Calendar Server)  Lack of support for required A number of those present properties concentrated on iSchedule with DKIM  Errors in report formats The testing event drew 22 on-site and discovery. Testing was fairly participants, 14 from Europe, intensive and participants found a As ever, the benefits of working representing the following number of issues with the draft together in one room to discover and organizations and products: protocol as well as with server fix interoperability issues were implementations. A number of servers enormous. Most of the participants  Apple (iCal Server, iCal Client, managed to connect successfully and test remotely during the year, iCloud Server, iCloud Outlook interact with each other, handling however, these sessions provide a Client, iOS 6) freebusy requests and meeting much more productive environment.  Bedework invitations and replies. Many participants were staying for the following Roundtable and took the  Testing of sharing and notifications CalDAV-Sync and CardDAV- opportunity to continue testing. Sync also took place with a generally successful outcome for all. Bugs in Mike Douglass, Senior Systems  Evolution plugin the client and server software were Programmer, Communication &  EGroupware found and rectified when possible. Collaboration Technologies at RPI, served as CalConnect Interoperability  emClient Discovery was also a hot topic and Test Event Manager. there were a number of issues  Google discovered in the current use of .well-  Kerio Technologies known and SRV records. Some CalConnect XXVI participants also tested the Brief and  Mozilla Prefer header. Oracle Corporation  SabreDAV In addition, many issues surfaced Santa Clara, California  Zimbra when participants tested the basic Interoperability Test Event CalDAV and CardDAV access In addition, the following January 28 - 30 protocols. The kinds of issues seen organizations/products participated remotely: were: Roundtable XXVI January 30 - February 1  AOL (AOL Calendar Server)  Misreporting of missing DAV properties  CMU (Cyrus Calendar Server)

About CalConnect Minutes

 Issued after each CalConnect Roundtable, this newsletter provides highlights of those gatherings and links to more in-depth coverage on the CalConnect web site.

 You will also find links to new Technical Committee Reports.

 This is also a source for details on upcoming CalConnect meetings and conferences.

 To subscribe to CalConnect Minutes send an e-mail to [email protected] and put "Subscribe " in the subject

line.

M i n u t e s Page 3

C a l C o n n e c t T H E C A L E N D A R I N G A N D S C H E D U L I N G C O N S O R T I U M October 2012

Tech Committee Summaries – Roundtable XXV

means to do that, in consultation with incorporated into the next version of the Internet Engineering Task Force the draft. Testing will continue to (IETF). verify that reliable levels of interoperability are achievable. TC-Eventpub The Committee will next progress the The Committee presented the new specification at the IETF. TC-AutoDiscovery properties: styled descriptions (aka The Committee presented the "rich text"), structured location, TC-Resource motivation behind autodiscovery in structured resource, and participants. The TC presented information about addition to introducing the technical They discussed some implications the latest version of the Committee’s solution itself to all CalConnect for CalDAVsize of the property, calendar resource specification. attendees. Members then went allowing suppression of rich text, They have moved to a new model, through open questions that need to language negotiation—and defining an “objectClass” that be addressed and collected described how Participants and represents a schedulable entity with feedback. The next steps are locations could refer to a vcard and a set of attributes that can be added continuing the standardization about the overall requirement to to any vCard to indicate how process and encouraging early search and index. It was noted that scheduling will take place with the implementations of the autodiscovery Structured location has superseded entity that the vCard represents. draft. TC participants believe that the earlier venue effort. Structured Next steps are to take this work to they will get some client support resources builds upon the work of the IETF for further discussion and soon and anticipate being ready for TC-Resource. The value could be to consider possible enhancements testing by the next interoperability URI, with the same syntax as to CalDAV to provide a richer testing event in January 2013. Structured location. Next steps resource scheduling experience include finishing the IETF RFC draft there. TC-CalDAV and starting on implementations. The TC discussed managed TC-Timezone attachments, sharing and TC-Freebusy The Committee presented a notifications and the prefer header. The TC had a lively discussion of the description of the timezone service On managed attachments, the group proposed VPOLL specification, as presently defined and discussed the issue of what limits drilling down into some key details of implemented. The intent is to try to a server should advertise and how a the specification. The group hopes to have systems treat timezones as client should react to those, as continue development of a full data rather than system components. well as how they would handle the specification and encourage more Participants talked about the case of attendees being able to implementations, particularly from possible future role of a timezone add attachments themselves. The clients. They also discussed the service and what, if any, were latter option will need follow- “reverse” poll idea as it pertains to the implications of a JSON iCalendar up discussion and specification by booking systems. representation on such a service. They presented the current state of the TC. For sharing, the Committee TC-iSchedule the draft and the implementations. discussed the current sharing draft Members presented an overview of and how it might be extended to the iSchedule protocol including the The TC felt it was clear they should facilitate some “public events” style new DKIM security pieces that the advertise the Committee’s services sharing modes, as well as per-event TC has been working on. Results on the CalConnect site so that others sharing. On prefer, they discussed from the successful interoperability can test against them. They the issue of whether servers need to event were discussed. Several indicated how much timezone related indicate to clients that the prefer issues found during testing were data, such as borders, aliases, and behavior was triggered, and settled discussed and solutions proposed even the names themselves, are on using the Vary header as a and agreed upon, and will be politically sensitive. (continued)

M i n u t e s Page 4

C a l C o n n e c t T H E C A L E N D A R I N G A N D S C H E D U L I N G C O N S O R T I U M October 2012

Tech Committee Summaries – Roundtable XXV (continued)

Continued from Page 3 – A higher priority, however, is to handle those types that were forward. Two scenarios were then getting a registry of timezone ids. special cased in xCal. These are presented for areas of extension of PERIOD, GEO, request status and VTODO. They also talked about timezones recurrence rules. They decided to by reference and the implications The consensus was to form an Ad special-case those except for CalDAV. Hoc committee to assess current recurrence rules. They expect to work items concerning, TC-XML have additional TC call participants and deficiencies with, VTODOs, Committee members presented a moving forward in order to make determine a scope of work and summary of the status of RFC6321 some rapid progress towards both deliverables, and recommend a - iCal in XML. They then addressed an RFC and an API. way to move forward, probably their work with OASIS, WS- VTODO BOF either to form a new TC or to Calendar, the CalWS RESTful and The BOF reviewed previous activity morph an existing one to adopt this SOAP protocols, and where those on VTODOs in CalConnect, new area. Apple, DHL, Mozilla, might go in the future. A good part including the 2007 Min-IOP Subset and RPI are participating initially. of the session was devoted to the Use Cases on Tasks published by A call for additional participants will TC’s work with iCalendar in JSON TC USECASE, and the Tasks be sent out after the Roundtable. and presenting the formats they Workshops in May and October of Conference calls for this committee had come up with. They had 2011. Participants noted that in are tentatively bi-weekly Tuesday a presentation of the Mozilla the second Workshop, although at 1100 Eastern, alternating with javascript code for handling JSON they concluded there was work to TC XML. The committee will report calendar entities and then followed do, they had no resources to move out at CalConnect XXVI. that with a discussion on how

Thanks to our contributors to this issue of Minutes

Cyrus Daboo, Apple Gary Schwartz, RPI

Tomas Hnetila Adrian Apthorp Kerio Technologies, Inc. DHL Express

Michael Douglass, RPI Ciny Joy Oracle

Guy Stalnaker Andrew McMillan University of Wisconsin www.andrew.mcmillan.net.nz

Patrick Ohly Marten Gajda www.estamos.de www.dmfs.org

M i n u t e s Page 5

C a l C o n n e c t T H E C A L E N D A R I N G A N D S C H E D U L I N G C O N S O R T I U M October 2012

New Members Welcome

scheduling. This opens up a number Patrick notes, “CalConnect is the of areas of to tackle and therefore in right forum to meet with other the short term we’re focusing on developers working on calendaring specific tasks in our business.” solutions. The interoperability testing becomes a lot easier when meeting  face-to-face and discussing (or even Patrick Ohly fixing) problems as they are found. DHL Express In a past life, The technical discussions about Patrick Ohly future standards provide early DHL Express worked on insights into what is coming next and is a global performance what changes may be useful to express analysis software implement. delivery for HPC clusters organization,  (“Intel Trace which calls Marten Gajda Analyzer and itself “the Collector”) and cluster technology in A Dresden, world’s most general (PTP and hardware time German native international company.” According to stamping, included in Linux since and current representative, Adrian Apthorp 2.6.30). Since January 2009, he has resident, Marten (pictured here), the company “has a worked for Intel’s Open Source Gajda first natural affinity with a number of Technology on data began topics and objectives of CalConnect,” synchronization+storage and more programming in including specifically SyncEvolution, his open 1990. After 1. Task / Event scheduling and source project, which synchronizes several semesters in computer recording – DHL’s product is time PIM data in various local storages sciences, he switched to Electrical sensitive and therefore scheduling (Evolution, KDE, Nokia N900/N9) Engineering. He launched his career and communication of tasks and using different protocols (SyncML, as an independent developer in 2006 events is critical CalDAV/CardDAV, ActiveSync). and started development for CardDAV-Sync and CalDAV-Sync 2. Locations - DHL’s pickup and In parallel to his work on commercial, for Android in February 2011. delivery from/to locations in 220+ closed source software, Patrick has countries and territories often contributed to free and open Regarding his reason for joining source software (including Evolution, Calconnect, Marten says, “My 3. Timezones – The company mkisofs, doxygen, Roundup, primary intention to join CalConnect operates across all of them gpsbabel, fcron, UAE) before he was to get in contact with other 4. Interoperability – standards started his own SyncEvolution developers of CalDAV and CardDAV enabling interoperability are key to project. Patrick began his love/hate software. I want to give the users of communication with the relationship with computers in his my apps a smooth synchronization company’s customers and teens on the Commodore 64 and experience with all kinds of clients business partners (more seriously) the Amiga, for which and servers. The interop tests are a Adrian notes, “Given the heritage of he wrote both public domain good opportunity to spot issues (in Internet Calendaring standards in programs (DiskProtection) and my software as well as in other personal collaboration, I’d like to shareware (MakeCD). Later he software) ideally before the users do. work with and see CalConnect take a studied Computer Science in Also, I want to be up to date with the more active interest in better support Karlsruhe and Edinburgh before latest news and developments in for business planning and working for Nero, Pallas and then calendar and contacts Intel. synchronization.”

M i n u t e s Page 6

C a l C o n n e c t T H E C A L E N D A R I N G A N D S C H E D U L I N G C O N S O R T I U M October 2012

CalConnect XXV hosted by Google in Zurich, Switzerland

M i n u t e s Page 7

C a l C o n n e c t T H E C A L E N D A R I N G A N D S C H E D U L I N G C O N S O R T I U M

October 2012

About CalConnect

The Calendaring and Scheduling Consortium (www.CalConnect.org) CalConnect members are: is a partnership among vendors, developers, and customers to  Apple advance calendaring and scheduling standards and  Ralf Becker implementations. The mission is to provide mechanisms to allow  Cabo Communications calendaring and scheduling methodologies to interoperate, and to  Carnegie Mellon promote broad understanding of these methodologies so that  DHL Express calendaring and scheduling tools and applications can enter the  eM Client mainstream of computing. The Consortium develops  Marten Gajda recommendations for improvement and extension of relevant  Genentech  standards, develops requirements and use cases for calendaring Google, Inc.  IBM Corporation and scheduling specifications, conducts interoperability testing for  IceWarp, Ltd. calendaring and scheduling implementations, and promotes  Intand calendaring and scheduling.  Gershon Janssen  Kerio Technologies

 MailSite Software, Inc.  Andrew McMillan  Microsoft

 Mozilla Foundation  NASA  New York University

 Nokia Corporation  OASIS  Patrick Ohly

 The Omni Group

Register Now  Oracle  Patricia Egen Consulting CalConnect XXVI  Rensselaer Polytechnic Institute (Bedework) Oracle Corporation  Santa Clara, California Pascal Robert  TimeTrade Systerms Interoperability Test Event  University of California January 28 - 30  University of Wisconsin, Madison Roundtable XXVI  Yahoo! January 30 - February 1  Zimbra, a division of VMware