Last Updated 18 October 2018
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 may be 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.
The work of Technical Committees and Provisional Committees is guided and coordinated by the Technical Coordination Committee (TCC).
Technical Committees generally produce CalConnect Work Products: Reports, Recommendations, specifications, code artifacts, etc. Technical Committees also produce draft specifications which may be published by CalConnect as a CalConnect Standard, and/or submitted to an external SDO for progression within that organization. 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 and Ad Hoc Committees|
|iCal4J Ad hoc||Develop a CalConnect version of iCal4J usable by all members and drive back into the mainline iCal4J|
|Active Technical Committees|
|TC-API||Develop an Abstract API for Calendaring and Scheduling|
|TC-AUTODISCOVERY||Autodiscovery of services based on internet standard protocols|
|TC-CALENDAR||Iimprovements and extensions to iCalendar, CalDAV, and iTIP transports, including but not limited to: iCalendardiff/patch, more compact recurrences, extensions to tasks, consensus scheduling, best current practices for iMIP, and iTIP over HTTP (iSchedule).|
|TC-CALSPAM||CalConnect and M3AAWG combined efforts of preventing users from being affected by calendar spam|
|TC-DEVGUIDE||Develop "cookbook" and supporting materials on how to use iCalendar and potentially other APIs such as CalDAV|
|TC-PUBLISH||Develop and maintain CalConnect document requirements and publication processes for CalConnect Standards and other public documents|
|TC-PUSH||Define a generic framework for push notifications within CalDAV (and CardDAV)|
|TC-SHARING||Extend the existing caldav-sharing and caldav-notifications specifications to support address books and other resource types.|
|TC-STREAMING||Define and document a streaming protocol for calendar data|
|TC-TESTER||Generalize and extend capabilities of the CalDAV/CardDAV Tester|
|TC-VCARD||Extend VCARD standards to support world-wide address formats and new capabilities|