Technical Committees are the technical working groups of the Consortium. A Technical Committee is established with a specific charter (scope of work), time frame, deliverables and expected schedule, and will disband when its scope of work is completed.
Provisional Committees (formerly called Ad Hoc Committees) are established at a CalConnect Conference to explore a possible new work area of work and recommend whether CalConnect should move forward in that area, generally by forming a new Technical Committee. Provisional Committees are usually very short-lived, reporting out at the next Conference.
Technical Committees generally produce CalConnect Work Products: Reports, Recommendations, code artifacts, etc. Technical Committees also product draft specifications which are submitted to an external SDO for progression within that organization to become a standard (e.g. the IETF). Finally Technical Committees may also collaborate externally towards the development of material which will not become a CalConnect Work Product but may be part of some other joint effort. See CalConnect Resources for more information.
Representatives of CalConnect members may participate upon any Technical Committee by contacting the Chair of the TC. Mmembers may propose new Technical Committees to address areas of work not currently under consideration, and may offer a Chair for a new TC (or PC).
Click on the committee name for more information about that committee if it has been made available.
For Closed Technical Committees please see Closed Technical Committees.
|Active Provisional Committees (formerly Ad Hoc Committees)|
|PC-QR||Explore a proposal for integrating QRCODE and extended VCARD4 incorporating Asian requirements|
|PC-SEC||Explore a proposal for Security and Encryption for Calendars|
|Active Technical Committees|
|TC-API||Develop an Abstract API for Calendaring and Scheduling|
|TC-AUTODISCOVERY||Autodiscovery of services based on internet standard protocols|
|TC-CALDAV||Assist and participate in development of CalDAV specifications|
|TC-CHAIRS||TC Chairs Coordination Committee|
|TC-DEVGUIDE||Develope "cookbook" and supporting materials on how to use iCalendar and potentially other APIs such as CalDAV|
|TC-EVENTPUB||Establish standards elements and mechanisms to support event publishing|
|TC-FREEBUSY||Develop mechanisms to support Freebusy services including consensus scheduling|
|TC-FSC||Federated Shared Calendars - Develop mechanisms to share individual calendars between separate calendaring systems|
|TC-IMIP||Identify interoperability issues with IMIP and develop fixes where appropriate|
|TC-IOPTEST||Support and manage CalConnect Interoperability Test Events|
|TC-ISCHEDULE||Develop proposal for Internet Scheduling Protocol (iSchedule)|
|TC-PUSH||Define a generic framework for push notifications within CalDAV (and CardDAV)|
|TC-RESOURCE||Develop recommendations for seamless interoperable resource scheduling|
|TC-SHARING||Evolve DAV protocols to combine intrasystem shared contacts and calendars|
|TC-TASKS||Develop iCalendar extensions for VTODO|