CalConnect Proposals

CalConnect Proposals are experimental specifications intended for research and exploration, e.g. through trial implementations, to determine its usefulness and applicability. Proposals deemed successful may be candidates to be offered to an appropriate standards body for adoption and progression as a standard.

The entries are in reverse chronological order by date of publication by CalConnect.

 

CalWS-SOAP SOAP Web Services Protocol for Calendaring (January 10, 2013):

This document, developed by the XML Technical Committee, specifies a SOAP web services Protocol for calendaring operations. This protocol has been contributed to OASIS WS-CALENDAR as a component of the WS-CALENDAR Specification under development by OASIS.

CalConnect and OASIS have agreed that any future work by CalConnect TC XML or OASIS WS-Calendar (or other committees in CalConnect and OASIS) on their respective versions of CalWS will be harmonized to maintain consistency between the versions. CalConnect and OASIS reserve the right to jointly and formally agree to fork the specifications at some point in the future if need arises.

 

CalWS-Rest Restful Web Services Protocol for Calendaring (September 13, 2010):

This document, developed by the XML Technical Committee, specifies a RESTful web services Protocol for calendaring operations. This protocol has been contributed to OASIS WS-CALENDAR as a component of the WS-CALENDAR Specification under development by OASIS.

CalConnect and OASIS have agreed that any future work by CalConnect TC XML or OASIS WS-Calendar (or other committees in CalConnect and OASIS) on their respective versions of CalWS will be harmonized to maintain consistency between the versions. CalConnect and OASIS reserve the right to jointly and formally agree to fork the specifications at some point in the future if need arises.

 

Freebusy Read URL (April 15, 2009):

This document, developed by the Freebusy Technical Committee, defines a standardized form of Freebusy read URL to improve interoperability between client and server implementations, while extending the functionality and utility through the use of optional parameters.