OASIS Integrated Collaboration Object Model for Interoperable Collaboration Services (ICOM) TC

Join TC     TC Page     Send a comment to this TC

A standard for integrated and interoperable enterprise collaboration

Eric Chan, eric.s.chan@oracle.com, Chair
Ken Baclawski, kenb@ccs.neu.edu, Chair

Table of Contents

Announcements

A discussion list on forming a new OASIS Technical Committee to develop a CMIS profile for Digital Asset Management (DAM) has been created. All are invited to subscribe. The next step is to draft a charter, and everyone's input is welcome. More details can be found in the minutes from the 2 Oct 2013 meeting, the 16 Sept 2013 meeting, and Ralph Windor's article in DAM News.

Participation in the OASIS ICOM TC is open to all interested parties. Commercial and open source providers of specific channel applications including wiki, blog, email, and conferencing will benefit by integrating their components into the ICOM framework. Contact member-services@oasis-open.org for more information on joining the TC.


Overview

The OASIS ICOM TC works to define a standard for integrated and interoperable enterprise collaboration.

For more information, see the TC Charter.


Subcommittees

No subcommittees have been formed for this TC.


Technical Work Produced by the Committee

Wiki for OASIS ICOM TC member collaboration


Expository Work Produced by the Committee

There are no approved expository work products for this TC yet.


External Resources

Although not produced by the OASIS ICOM TC, the following information offers useful insights into its work:

Cover Pages Report


Mailing Lists and Comments

icom: the list used by TC members to conduct Committee work. TC membership is required to post. TC members are automatically subscribed; the public may view archives.

icom-comment: a public mail list for providing input to the OASIS ICOM TC members. Send a comment or view archives.


Additional Information


Providing Feedback: OASIS welcomes feedback on its technical activities from potential users, developers, and others to better assure the interoperability and quality of OASIS work.