• Apple Inc.

• Boeing

• California State University, Fresno

• Carnegie Mellon

• Dartmouth

• Duke University

  Founding member

• Eventful

  Founding member

• Google

• IBM

• Kerio Technology

• MailSite Software

• Marware

• M.I.T.

  Founding member

• Microsoft

• Mirapoint

• Mozilla Foundation

  Founding member

• New York University

• Open Connector Groupware

• Oracle Corporation

  Founding member

• Open Source Applications Foundation

  Founding member

• PeopleCube

  Founding member

• Princeton University OIT

• Rensselaer Polytechnic Institute (RPI)

• Scalix

• Sony Ericsson

• Stanford University

  Founding member

• Sun Microsystems

• Symbian

  Founding member

• Synchronica

• Timebridge

• Trumba Corp

• University of California, Berkeley

  Founding member

• University of Chicago

• University of Michigan

• University of Pennsylvania

• University of Washington

  Founding member

• University of Wisconsin, Madison

  Founding member

• Yahoo!

  Founding member

• Zimbra

• Patricia R. Egen

• TC participants from member organizations

• Determined by TC Chair and TC membership

• TC Chair provides regular status to Steering Committee

• Any Consortium member may propose new work

• Charter, scope and deliverables identified in the proposal

• Chair confirmed by SC

• Committee terminates when chartered work is complete

• In-progress work confidential to Consortium members only

• Completed work published and freely available on Consortium web site

• No proprietary information discussed

• Founding Members plus first member from each membership category

• Monthly teleconference

• Meetings at Roundtables or other activities if needed

• Chair chosen by Steering Committee members

• Chair participates in Board of Directors meetings

• Overall technical direction

• Management of Technical Committees via TC CHAIRS committee

• Consortium program elements

• Advice to the Board of Directors

Any company, institution or individual who:

• supports the goals of the Consortium

• agrees to abide by its rules

• submits the proper membership application

• pays the appropriate membership fee

• Published on the Consortium web site

• Based on membership category

• Due annually upon anniversary of joining the Consortium

• Commercial Vendor

  • >$100 million annual revenue

  • $10-100 million annual revenue

  • >$10 million annual revenue

• Customer Organizations/Companies

• Non-Profit Organizations

• Open Source Organizations

• Academic Institutions

• Standards Setting Organizations

• Individuals

Define problems CalConnect wishes to solve with extensions to WebDAV; assist IETF with development of CalDAV Specification

Define event publishing & establish differences from regular calendaring and scheduling

Develop and conduct Federated Free/Busy Challenge Response; review Free/Busy related proposals

Support interoperability testing for all technical committees, develop test suites & reference implementation, publish Interop results

Define issues for mobile support of standards-based Calendaring and recommend extensions to standards for mobile support

Clarify issues involved with realtime server-to-server calendaring and scheduling issues & provide recommendations

Develop proposals for a formal, authoritative Timezone Registry and a Timezone Service Protocol

Develop sets of real world use cases that can be used to validate identified functionality & testing scenarios for existing & future C&S implementations

• Developed RFCs 2445/6/7

• Shut down in 2004 at same time as CAP removed from table

• Assigned “experimental draft” status by IETF in 2004 (effectively removed from program of work in IETF)

• Still in use especially in mobile calendaring, travel industry websites

• Not fully compatible with iCalendar (e.g. recurrence); encourage move to iCalendar

• The Benefits of iCalendar for the Mobile Industry

• Not precisely “calendaring” — but contacts/address book central to calendaring

• Current version 3.0 needs work

• Mobile calendaring mostly obsolete vCard 2.1

• CalConnect vCard workshop

• Simplify (rationalize) RFCs 2445/6/7

• Target of initial CalConnect work products

• All have revised drafts underway

• Expect publication of revised RFCs in 2008

• Still require interoperability demonstration to progress to Draft Standards (i.e. CalConnect)

• “Calendaring Extensions to WebDAV” published as Proposed Standard, RFC 4791

• “Scheduling Extensions to CalDAV” is under review for submission

• Several CalDAV implementations today

  • Apple iCal Server (Darwin Calendar Server)

  • Bedework

  • Evolution

  • Kerio Technologies (Kerio MailServer)

  • Marware (Project X Client)

  • Mozilla Lightning & Sunbird (CalDAV client)

  • Mulberry (Client)

  • Oracle Calendar

  • OSAF Cosmo (Chandler Project)

  • Etc.

• Proposed extensions (additions) to the revised iCalendar when it is complete

• VAVAILABILITY

  • New iCalendar component allowing publication of available and unavailable time periods associated with calendar user

• VVENUE

  • New iCalendar component allowing the specification of structured location data for publishing event information

• Identifies location on website of structured event information for use by event publication aggregators

• Begin: October 2004

• Define problems CalConnect wishes to resolve with CalDAV Extensions to WebDAV

• Assist IETF with CalDAV Specifications

• Act as “real world” input to CalDAV Specification authors (two of three are members of TC CALDAV)

• Develop CalDAV testing matrices for TC IOPTEST

• Develop VAVAILABILITY with TC FREEBUSY

• Develop use cases and requirements for CalDAV Scheduling

• CalDAV scheduling extensions (discovery, auth/auth, etc.)

• CalDAV testing matrices for Interoperability testing

• CalDAV Use Cases and Requirements

• CalDAV Scheduling Requirements

• VAVAILABILITY extension to iCalendar

• Begin: March 2005

• Define Event Publication and distinguish from regular calendaring

• Determine requirements for event publication not met by existing specifications and propose remedies

• Review of possible extensions to iCalendar to support event publication and venue information

• Develop mechanism for event “crawlers” to find and consume event information on websites, analogous to “sitemap”

• VVENUE extension to iCalendar

• EVENTMAP proposal under development

• Begin: May 2006

• Act as CalConnect Liaison with The Open Group for the Federated Freebusy Challenge in 2006

• Inform the work of CALDAV, REALTIME, and other TCs

• Participate in drafting the final report for The Open Group

• Demo-ed a Federated Freebusy Aggregator at The Open Group meeting in July 2006

• Assist Boeing to “productize” components used in the demo as well as those being further developed by Boeing

• Addressing “office hours”/“availability” — joint VAVAILABILITY project with TC CALDAV

• Standardize and simplify FREEBUSY URL

• Begin: October 2004

• Conduct CalConnect Interoperability Test Events and publish results

• CalConnect Interoperability Test Events scheduled with each Consortium event week (i.e. together with Roundtables)

• Public and CalConnect-internal IOP test event reports

• Begin: September 2005

• Identify issues related to mobile calendaring and scheduling and develop recommendations to address

• Determine mobile calendaring issues and problems

• Survey mobile users about calendaring

• Evaluate continued reliance on vCalendar and develop ways to move vendors forward

• Develop Mobile Calendaring Interoperability Test Suite

• Implement Mobile IOP Test Events (with TC IOPTEST)

• Define Mobile Calendaring issues for CalDAV

• Report on Mobile Calendaring Questionnaires

• Mobile Calendaring Interoperability Test Suite

• Benefits of iCalendar for the Mobile Industry

• Begin: June 2007

• Identify issues related realtime server-server scheduling and make recommendations to address

• Discovery, Authentication and Authorization

• iTIP evaluation and extensions

• Work with TC CALDAV, TC FREEBUSY

• Begin: October 2004 (completed February 2006)

• Identify problems with Recurrences in iCalendar

• Make recommendations to IETF CALSIFY effort (revision of RFC 2445 iCalendar)

• Questionnaires to determine problems with recurrence in implementations of iCalendar

• Develop problem statement and recommendations

• Results from Recurrence Questionnaire

• iCalendar Recurrence Problems and Recommendations

• Begin: October 2004 (completed February 2006)

• Identify problems with timezone usage in iCalendar and timezone support in genera

• Conduct survey on problems with timezone management

• Develop problem statements and recommendations for IETF CALSIFY effort for iCalendar

• Timezone Questionnaire

• Report on Timezone Questionnaire

• Timezone Problems and Recommendations

• Timezone Registry and Service Recommendations

• Begin: May 2007

• Continue work of TC TIMEZONE by developing formal proposals based on Timezone Registry and Service Recommendations

• Develop proposal for formal, authoritative Timezone Registry for submission to IETF to be published as an RFC

• Develop requirements for Timezone Registry Service

• Develop proposals for Timezone Registry Service implementations using current protocols

• Begin: October 2004

• Develop use cases for calendaring and scheduling and their contextual environments

• Establish the ways that users actually want to use calendaring environments

• Establish “Minimum Interoperable Subsets” (the minimum set of functions which must be interoperable to make an implementation useful to a customer)

• Assessment of access control in existing calendaring implementations for TC CALDAV

• Develop Min-IOP use cases for Resources

• Min-IOP Use Cases for iCalendar

• CalDAV Use Cases (with TC CALDAV)

• Min-IOP Use Cases for Tasks

• Calendaring and Scheduling Glossary of Terms

• Min-IOP Use Cases for Resources

• Begin: June 2005

• Establish CalConnect position on Extended Daylight Savings Time Proposal by U.S. Congress

• Continue DST Advisory Work

• Develop CalConnect position on EDST and communicate to U.S. Congress prior to enactment of law

• Develop guidance for industry on planning for and implementing EDST Changes in March and October

• Work with TC TIMEZONE on recommendations on future of timezone and DST support

• Extended Daylight Savings Time Advisory

• Extended Daylight Savings Time Review and Considerations

• EDST Links, Advisories and Changes

• CalConnect Reflections and Recommendations

• Begin: January 2007

• Determine interest in and support for revision of vCard standard

• vCard Workshop planning and implementation

• Liaisons with OMA/DS on interest in vCard Revision

• Identify products of vCard Technical Committee

• Develop charter for vCard Technical Committee in support of IETF working group on vCard revision

• Recommendation on establishment of vCard TC

• vCard Workshop (September 2007)

• Draft Charter for vCard Technical Committee

• Begin: May 2007

• Plan for and explore XML representations of iCalendar

• Determine need for XML Technical Committee

• Conduct BOFs to determine level of support for roundtrip iCalendar/XML

• Review prior art in this are

• Develop charter for XML Technical Committee

• Identify potential products of XML TC

• Recommendation for establishment of XML TC

• Draft charter for XML Technical Committee