GCWS Case Study

Overview

Having tested and researched a number of calendaring systems and calendar software, we were left pondering what exactly would be unique and new about the GCWS we planned to develop.

Google calendar for example met most of the envisaged group and calendaring use cases we had in mind. There are many groupware and enterprise mail systems offer calendaring and scheduling services. There are tools to sync, there are a number of active open source calendar projects. The world of calendaring is very proactive with regards to interoperability at least with respect to iCal or iCal derived calendar sharing standard CalDav.

Nevertheless the original concept of group calendars web services is quite novel, furthermore using work from previous projects ioMorph and ioNetwork we still maintain there are problems we can solve with GCWS.

GCWS is designed to allow GROUPS [inter organisational, cross department, one-off, social or teams] to share and exchange central calendaring information and central calendaring processes via web service based interchanges.

The unique aspects of our design include;

* agent and node architecture [ioNetworkNode] so that implementers can build trust networks for cross institutional use cases
* plug-in transformations so that implementers can quickly turn their sources of data into standards like RSS and iCal
* novel client use cases for organising and viewing data in calendars, not just meetings and events

Visit the GCWS homepage for more information.