Cover Pages Logo SEARCH
Advanced Search
Site Map
CP RSS Channel
Contact Us
Sponsoring CP
About Our Sponsors

Cover Stories
Articles & Papers
Press Releases

XML Query

XML Applications
General Apps
Government Apps
Academic Apps

Technology and Society
Tech Topics
Related Standards

Call for Participation: OASIS CMIS TC

Note: See now complete references in Content Management Interoperability Services (CMIS)

Call for Participation: OASIS Content Management Interoperability Services (CMIS) TC

Subject:   Call for Participation: OASIS Content Management Interoperability Services (CMIS) TC
From:      "Mary McRae" <>
To:        <>,<>
Date:      Mon, 6 Oct 2008 13:13:57 -0400

To: OASIS members and interested parties,

A new OASIS technical committee is being formed. The OASIS Content Management Interoperability Services (CMIS) Technical Committee has been proposed by the members of OASIS listed below. The TC name, statement of purpose, scope, list of deliverables, audience, and language specified in the proposal will constitute the TC's official charter. Submissions of technology for consideration by the TC, and the beginning of technical discussions, may occur no sooner than the TC's first meeting.

The eligibility requirements for becoming a participant in the TC at the first meeting (see details below) are:

  1. you must be an employee of an OASIS member organization or an individual member of OASIS
  2. you must join the Technical Committee, which members may do by using the "Join this TC" button on the TC's public page at [a]

To be considered a voting member at the first meeting, you must:

  1. join the Technical Committee at least seven (7) days prior to the first meeting
  2. you must attend the first meeting of the TC, at the time and date fixed below

Of course, participants also may join the TC at a later time. OASIS and the TC welcomes all interested parties.

Non-OASIS members who wish to participate may contact us about joining OASIS [b]. In addition, the public may access the information resources maintained for each TC: a mail list archive, document repository and public comments facility, which will be linked from the TC's public home page at [a].

Please feel free to forward this announcement to any other appropriate lists. OASIS is an open standards organization; we encourage your participation.



Mary P McRae
Director, Technical Committee Administration
OASIS: Advancing open standards for the information society
phone: 1.603.232.9090


Charter and Call For Participation

OASIS Content Management Interoperability Services (CMIS) TC

1A Name of the TC

Content Management Interoperability Services (CMIS) Technical Committee

1B Statement of Purpose

Historically content management systems were purchased for specific application uses and this led to islands of incompatible systems. The lack of a standard interface to content management systems made it difficult to integrate content from multiple repositories into a single application such as a portal, CRM system, or office desktop. It also made it difficult for Independent Software Vendors (ISVs) and integrators to build applications that supported multiple content management systems consistently or easily.

The purpose of the Content Management Interoperability Services (CMIS) TC will define a domain model including a data model and abstract capabilities for Content Management (CM) and a set of bindings that can be used by applications to work with one or more Content Management Repositories/systems and that can be implemented by content repositories and enable interoperability across repositories for the set of use cases below. These capabilities and interfaces will not match every existing content management system and may require some level of change to existing products, at least in terms of conforming existing interfaces to those defined here. However, it is an explicit goal that CMIS Domain Model and Bindings will NOT require major product changes or significant data model changes in existing major CM repositories.

As such, the CMIS TC should define a domain model and bindings that are designed to be layered on top of existing Content Management systems and their existing programmatic interfaces. This TC should not prescribe how specific features should be implemented within those Enterprise Content Management (ECM) systems. This TC is intended to define a generic/universal set of capabilities provided by an ECM system and a set of services for working with those capabilities.

1C Scope of Work

The TC will accept as input Version 0.5 of the CMIS specification as published by EMC, IBM and Microsoft on September 10th, 2008. The specification is located at:

Other contributions and changes to the input documents will be accepted for consideration without any prejudice or restrictions and evaluated based on technical merit in so far as they conform to this charter.

The initial set of deliverables will be targeted for the following use cases:

  • Collaborative Content Applications
  • Portals leveraging Content Management repositories
  • Mashups
  • Searching a Content Repository

The following use cases should be able to be supported by CMIS Domain Model and Bindings, but are not primary drivers:

  • Workflow and Business Process Management (BPM)-centric applications utilizing Content
  • Archival Applications
  • Compound and Virtual Documents
  • Electronic and Legal Discovery

The following use cases are out of scope for the initial set of deliverables:

  • Records Management (RM) and Compliance
  • Digital Asset Management (DAM)
  • Web Content Management (WCM)
  • Subscription and Notification Services

Also, this TC will engage in maintenance of the specifications produced by this TC.

The tasks of the TC include:

  • To articulate the principles of the interoperable content management through formal specifications
  • To assess the relationship of CMIS to other related standards and industry efforts. These include Java Content Repository (JCR) (JSR-170, JSR-283), WebDAV and its related specifications including DASL, Search Web Services TC, and other relevant standards.
  • To define appropriate specifications for interoperable content management
    • Including schemas, such as XML Schema Definition (XSD)
    • Including service definitions, such as Web Service Definition Language (WSDL)
  • To standardize the common types of entities and capabilities in CM
  • To encourage cooperation within and between the various topical domains and groups

After the first set of deliverables, the TC will continue to work on the next versions of the specification. Specific functional content of the next versions will be determined by a TC vote. The next versions may address the following use cases:

  • Core ECM Repository capabilities
  • Collaborative Content Applications
  • Portals leveraging Content Management repositories
  • Mashups utilizing Content
  • Workflow and BPM-centric applications utilizing Content
  • Content Archival Applications
  • Compound and Virtual Documents applications
  • Electronic and Legal Discovery of Content applications
  • Records Management and Compliance
  • Digital Asset Management Applications
  • Web Content Management Applications
  • Information Rights Management applications
  • Desktop Integration of Content Management repositories

The TC MAY define other bindings explicitly listed below after the first deliverable:

  • Web Services
  • REST
  • XMPP
  • JMS
  • JCA
  • SMTP


Once the TC has completed work on a deliverable and it has become an OASIS standard, the TC will enter "maintenance mode" for the deliverable.

The purpose of maintenance mode is to provide minor revisions to previously adopted deliverables to clarify ambiguities, inconsistencies and obvious errors. Maintenance mode is not intended to enhance a deliverable or extend its functionality.

The TC will collect issues raised against the deliverables and periodically process those issues. Issues that request or require new or enhanced functionality shall be marked as enhancement requests and set aside. Issues that result in the clarification or correction of the deliverables shall be processed. The TC shall maintain a list of these adopted clarifications and shall periodically create a new minor revision of the deliverables including these updates. Periodically, but at least once a year, the TC shall produce and vote upon a new minor revision of the deliverables.

1D List of Deliverables

The initial set of deliverables and projected duration:

  • CMIS Domain model specification (September 2009)
  • CMIS SOAP-based Web Services binding specification (September 2009)
  • CMIS REST/Atom-based Web Services binding specification (September 2009)

1E IPR Mode

The IP mode for the TC will be RF on RAND.

1F Audience for the TC

The primary audience for the final output of this TC includes ECM and BCS application architects and ECM repository architects and implementers.

1G Language

The language in which the TC shall conduct business:


Additional Information

Section 2: Non-normative Information

2A Similar or Applicable Work

Identification of similar or applicable work that is being done in other OASIS TCs or by other organizations:

  • WebDAV: Not targeting ECM and does not provide a CM domain model
  • JCR: Java based specification and does not specify a protocol

2B First Meeting

Date, time and place of the first TC meeting:

12PM EST/9AM PST, 10 November 2008, conference call

2C Schedule

Ongoing meeting schedule:

The CMIS TC will meet by telephone every other week at Monday 9AM PST. The time, date and recurrence of the periodic phone call will be confirmed at the first TC meeting. The meetings will last no more than two hours. The CMIS TC will hold face-to-face meetings three (3) times a year for three days starting:

1/26/2009 (Redmond, Washington, hosted by Ethan Gur-esh, Microsoft)

2D Proposers

Names and email addresses of members (minimum three [Eligible Persons]):

2E Convenor

Al Brown, IBM,

2G Input Specifications

  • CMIS Part I — Domain Model v0.5
  • CMIS Part II — Web Services Binding v0.5
  • CMIS Part II — REST-Atom Binding v0.5
  • CMIS — Appendices v0.5

Specifications available at:

2I Proposed Specification Titles

  • Content Management Interoperability Standard
  • Domain Model Content Management Interoperability Standard
  • Web Service Binding Content Management Interoperability Standard
  • REST/Atom Binding


Prepared by Robin Cover for The XML Cover Pages archive.

Globe Image

Document URI:  —  Legal stuff
Robin Cover, Editor: