OASIS Content Management Interoperability Services (CMIS) Technical Committee

The original Call For Participation for this TC may be found at http://lists.oasis-open.org/archives/tc-announce/200810/msg00003.html

  1. Name

    OASIS Content Management Interoperability Services (CMIS) Technical Committee

  2. 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.

  3. 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
    • JSON-RPC
    • 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.

  4. 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)
  5. IPR Mode:

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

  6. 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.

  7. The language in which the TC shall conduct business: