CMIS(内容管理互操作服务)技术委员会成形

source: http://xml.coverpages.org/cmis.html

Contents

• CMIS TC Overview
• From the CMIS TC Charter and Call For Participation
• Comments on the CMIS TC Proposed Charter
• Related Specifications and Implementations
• Publication of CMIS by ECM Vendors
• Bibliographic Information: CMIS Version 0.5
• Vendor Company Announcements for CMIS
  • EMC, IBM, Microsoft Joint Announcement
  • Alfresco Announcement
  • Open Text Announcement
• CMIS Overview: Vendor Statements
  • IBM
  • Microsoft
  • Alfresco
  • EMC
• CMIS Resources from the Vendor Companies
• Principal URIs
• General: News, Announcements, Industry Analysis, Blogs, Commentary

---

Overview

On October 06, 2008, OASIS issued a public call for participation in a new technical committee chartered to define specifications for use of Web services and Web 2.0 interfaces to enable information sharing across content management repositories from different vendors. The OASIS Content Management Interoperability Services (CMIS) TC will build upon existing specifications to "define a domain model and bindings that are designed to be layered on top of existing Content Management systems and their existing programmatic interfaces. The TC will not prescribe how specific features should be implemented within those Enterprise Content Management (ECM) systems. Rather it will seek to define a generic/universal set of capabilities provided by an ECM system and a set of services for working with those capabilities."

As of November 14, 2008, the CMIS technical work had received broad support through analyst opinion and declarations of interest from major companies. Some of these include Alfresco, Day Software, EMC, FatWire, IBM, Magnolia, Microsoft, Nuxeo, Open Text, Oracle, Quark, SAP, Saperion, Vamosa, and Vignette. Early commentary from industry analysts and software engineers is positive about the value proposition in standardizing an enterprise content-centric management specification. The OASIS announcement of November 17, 2008 includes endorsements.

Principal use cases motivating the CMIS technical work include collaborative content applications, portals leveraging content management repositories, mashups, and searching a content repository. Subject to TC vote, the members may also address additional use cases like 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.

Core deliverables produced by the CMIS technical committes will build upon Input Specifications to be contributed at the commencement of TC work. In particular, the TC will accept as input Version 0.5 of the September 2008 CMIS specification as published by EMC, IBM, and Microsoft. Proposed specification titles include Content Management Interoperability Standard, Domain Model Content Management Interoperability Standard, Web Service Binding Content Management Interoperability Standard, and REST/Atom Binding.

Initial TC proposers include representatives from OASIS member companies Alfresco, Day Software, EMC, IBM, Microsoft, Open Text, Oracle, SAP AG. The Convenor (Al Brown, IBM) was scheduled to lead an intial meeting of the TC on November 10, 2008, to be held as a conference call. The TC operates under the OASIS RF on RAND IPR Mode. Persons eligible to become voting members at the first meeting of the CMIS TC included: Al Brown (IBM), Mark Carlson (Sun), Derek Carr (IBM), David Caruana (Alfresco), David Choy (EMC), Scott Conroy (Individual), Cornelia Davis (EMC), Doug Domeny (Ektron), Kevin Dorr (Flatirons), Dustin Friesenhahn (Microsoft), Gary Gershon (Individual), Paul Goetz (SAP), Ethan Gur-esh (Microsoft), Dennis Hamilton (Individual), Martin Hermes (SAP), Jens Hübel (Open Text), Gershon Janssen (Individual), John Volker (Saperion), Ijonas Kisselbach (Vamosa), Gregory Melahn (IBM), Pat Miller (Microsoft), Florian Müller (Open Text), John Newton (Alfresco), David Nuescheler (Day), Mark Poston (Mekon), Norrie Quinn (EMC), Craig Randall (EMC), Patrick Ryan (IBM), Patrick Ward (Booz Allen Hamilton).

According to the CMIS TC 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.

From the CMIS TC Charter and Call For Participation

The complete (hyper)text of the CMIS TC Call for Participation is also available online. It explains eligibility requirements for becoming a participant in the TC at the first meeting, and indicates how to join the CMIS TC.

• Charter and Call For Participation
  • 1A Name of the TC
  • 1B Statement of Purpose
  • 1C Scope of Work
  • 1D List of Deliverables
  • 1E IPR Mode
  • 1F Audience for the TC
  • 1G Language
• Additional Information
  • 2A Similar or Applicable Work
  • 2B First Meeting
  • 2C Schedule
  • 2D Proposers
  • 2E Convenor
  • 2G Input Specifications
  • 2I Proposed Specification Titles

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:

• http://community.emc.com/community/labs/cmis
• http://www.ibm.com/software/data/content-management/cm-interoperablity-services.html
• http://www.microsoft.com/sharepoint/capabilities/ecm/cmis.mspx

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

Maintenance

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:

English

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]):

• Albert Brown, [e-mail]
• Cornelia Davis, [e-mail]
• Craig Randall, [e-mail]
• Derek Carr, [e-mail]
• David Caruana, [e-mail]
• David Choy, [e-mail]
• Dustin Friesenhahn, [e-mail]
• Paul Goetz, [e-mail]
• Ethan Gur-esh, [e-mail]
• Dennis Hamilton, [e-mail]
• Martin Hermes, [e-mail]
• Jens Hübel, [e-mail]
• Ryan McVeigh, [e-mail]
• Gregory Melahn, [e-mail]
• Pat Miller, [e-mail]
• Florian Müller, [e-mail]
• John Newton, [e-mail]
• David Nuescheler, [e-mail]
• Norrie Quinn, [e-mail]
• Steve Roth, [e-mail]

2E Convenor

Al Brown, IBM, [e-mail]

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:

• http://community.emc.com/community/labs/cmis
• http://www.ibm.com/software/data/content-management/cm-interoperablity-services.html
• http://www.microsoft.com/sharepoint/capabilities/ecm/cmis.mspx

2I Proposed Specification Titles

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

Comments on the CMIS TC Proposed Charter

Comments on the CMIS Proposed Charter posted to the 'oasis-charter-discuss' list, with disposition in the CMIS Comment Resolution Log.

• IPR Mode. Dennis E. Hamilton ([e-mail]): "I am curious about the value that 'RF on RAND' has in contrast with maximizing assurance of easy entry into an integration model..." Response: "Al: Thank you for the feedback. The goal is the widest use possible. However, the proposers have already agreed to RF on RAND and we are unlikely to get the same or larger group with RF on Limited."

• Scope. Jeff Mischkinsky ([e-mail]): "I have a concern that the charter IPR scope is too unbounded with respect to future versions of the the spec (after the first deliverable) for some companies to make a proper determination on whether to join or not..." Response: "Al: Thank you for the feedback on the IPR issue around future versions. The charter has been updated to resolve this issue."

• Search Web Services. Kerry Blinco ([e-mail]): "Can I suggest that the CMIS TC also look at the work being done by the OASIS Search Web Services TC when assessing the relationship of CMIS to other efforts as the work currently being undertaken by this TC. The Search Web Services TC is developing Web services definitions for search and retrieval applications..." Response: "Al: Thank you for the awareness of this TC. Search Web Services TC has been added to the charter as a potential interesting related standard. The TC when it first meets will discuss which standards to coordinate with and at which levels."

• WebDAV Search. Dennis E. Hamilton ([e-mail]): "I see that the WebDAV SEARCH (formerly known as DASL) has been accepted as an IETF Proposed Standard... I notice that Search within a CM repository is not explicitly mentioned in the CMIS scope as either in- or out-of scope..." Response: "Al: Thank you. The charter has been updated to also include WebDAV search, DASL, explicitly. The TC when it meets will discuss interacting with WebDAV and DASL. The focus of the TC is for providing specification around common Enterprise Content Management (ECM) functionality and thus a searching paradigm designed for that environment. Search also has been added as an explicit use case."

• Overall Design. Gary Gershon ([e-mail]): "The proposed CMIS TC is building upon a substantial base of trail-blazing work accomplished by the convening companies... I would like to encourage the CMIS technical committee leadership to devote sufficient attention in the design of the TC deliverables to embrace several core SOA architectural principles..." Response: Al: These are great tenets and the TC should give them due thought. This will be referred to the TC for consideration during its work.

• java JSR 170 and 283. William Cox ([e-mail]): "I urge the proposed TC to revisit the importance of java JSR 170 and 283. Speaking for JSR170, the work did a good job of establishing common interfaces to the major content management systems..." Response: "Al: Thank you. JSR 170 and 283 (JCR) is an important standard and the TC has in its charter to interact with JCR. We might potentially combine efforts where that makes sense. I have started the discussion with David Nuescheller from JSR-283 who has been quite helpful. JCR's domain model might not be a good starting place for the services this TC wants to specify. Please see the draft specification. The TC when it first meets will discuss the level of interaction with JCR."

• java JSR 170 and 283. William Cox ([e-mail]): "The last paragraph of section 1B is an excellent description of the work done (in the java domain) on JSR 170. I suggest a clear statement that alignment with the model and interfaces of the JSRs for CMIS as part of the charter..." Response: [preceding]

• Acronyms. William Cox ([e-mail]): "Please spell out acronyms, e.g., ECM and BCS and ECM..." Response: "Al: Thank you."

• Also on java JSR 170. Rex Brooks ([e-mail]) [re: "I urge the proposed TC to revisit the importance of java JSR 170 and 283.." — (Rex) "Having worked on v1.0 and much of v2.0 of WSRP before it got a bit bogged down prior to completing work and achieving approval, I heartily concur." Response: "Al: See above."

Related Specifications and Implementations

• Java Content Repository (JCR): JSR 170 and JSR 283
• Apache Sling
• WebDAV
• OASIS SRU/CQL Specifications
• Atom
• SOAP
• Open Document Management API (ODMA)

......
......
......

"The objective of the CMIS standard is to define a common content management web services interface that can be implemented by content repositories and enable interoperability across repositories. 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 will not require major product changes or significant data model changes like other standards such as JSR 170 have required..."

"The CMIS standard will expose core/common ECM repository capabilities in an intentionally generic way. These will allow for applications to be constructed that can work with content residing in one or more ECM repositories, without having to understand implementation differences between the individual repositories or worrying about interface inconsistencies between the repositories... Thusly:

While most/all of the capabilities that will be exposed via CMIS generally fall into the core/basic functions of an ECM repository, the goal of this standard is to ensure that ECM applications can be built on top of the CMIS interfaces that enable richer/business critical applications and use cases, like Business Process Management and Electronic Discovery. Because those application use cases have been under consideration through the CMIS design process, CMIS will enable ECM applications to focus on solving business logic problems at the application-level without worrying about the implementations of specific ECM repositories...

"By providing a services-oriented architecture for interacting with an ECM repository, ECM applications can use CMIS to be loosely-coupled to individual repositories, rather than more tightly integrated. This will make it simpler for (a) applications to use CMIS interfaces 'a la carte' rather than having to having to invoke the full-set of CMIS interfaces, and (b) allow applications to be built in a Services Oriented Architecture.

According to the published "Overview of Content Management Interoperability Services 1.0," CMIS "defines four base types of objects that exist within a Repository, where the Repository can define additional Object Types for any of these type of objects. An Object Type specifies the schema of Properties that are allowed or required for the object. (1) Documents represent individual content objects in the repository. A Document may or may not include one content-stream. (2) Folders represent organizational containers in which Documents (or other folders) can be stored.(3) Relationships represent loose relationships between exactly two (2) objects (documents or folders) in the Repository. (4) Policies represent administrative policies that may be applied to objects."

CMIS "exposes services for:

• Discovering Object Type definitions and other Repository information — including which optional capabilities are supported by a particular Repository
• Creating, Reading, Updating, and Deleting objects
• Filing Documents into zero, one, or more Folders — if the repository supports the optional multi-filing capability
• Navigating and traversing the hierarchy of folders in the Repository
• Creating versions of Documents and accessing a Document's version history
• Querying a repository to retrieve one or more objects matching user-specified search criteria, including full-text search queries"

Document objects can be versioned, but 'folder', 'relationship', and 'policy' objects are not versioned. All methods for referring/retrieving a Document can specify whether they refer to a specific version of a Document, or should always retrieve the latest version.

A CMIS Repository has the option of supporting multi-filing of Documents into zero, one, or more than one folder concurrently. Folders can never be multi-filed. The Repository's level of support for multi-filing will be exposed to applications through the Repository service..."

On September 10, 2008, OASIS member companies submitted a proposed charter for a new OASIS Content Management Interoperability Services (CMIS) Technical Committee. Based upon Version 0.5 of the CMIS specification, the TC would "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."