CharterHistorically 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. OASIS Content Management Interoperability Services TCCMISTC_a311cc2c-1347-11e2-a828-da8497258a28The OASIS CMIS TC works to standardize a Web services interface specification that will enable greater interoperability of Enterprise Content Management (ECM) systems. CMIS uses Web services and Web 2.0 interfaces to enable rich information to be shared across Internet protocols in vendor-neutral formats, among document systems, publishers and repositories, within one enterprise and between companies. David Choydavid.choy500@gmail.com, ChairRyan McVeighrmcveigh@ziaconsulting.com, SecretaryEMC IBMMicrosoftUsing Web services and Web 2.0 interfaces to enable information sharing across content management repositories from different vendors_a313accc-1347-11e2-a828-da8497258a28To 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 _a313afd8-1347-11e2-a828-da8497258a28Initial DeliverablesThe initial set of deliverables will be targeted for the following use cases
_a313b082-1347-11e2-a828-da8497258a281Collaborative Content Applications_a313b104-1347-11e2-a828-da8497258a281.1PortalsPortals leveraging Content Management repositories_a313b190-1347-11e2-a828-da8497258a281.2Mashups_a313b212-1347-11e2-a828-da8497258a281.3SearchingSearching a Content Repository
_a313b29e-1347-11e2-a828-da8497258a281.4Other Use CasesThe following use cases should be able to be supported by CMIS Domain Model and Bindings, but are not primary drivers
_a313b320-1347-11e2-a828-da8497258a282 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
Workflow & BPMWorkflow and Business Process Management (BPM)-centric applications utilizing Content
_a313b3ac-1347-11e2-a828-da8497258a282.1ArchivalArchival Applications
_a313b438-1347-11e2-a828-da8497258a282.2Compound and Virtual Documents_a313b4e2-1347-11e2-a828-da8497258a282.3DiscoveryElectronic and Legal Discovery
_a313b578-1347-11e2-a828-da8497258a282.4SpecificationsEngage in maintenance of the specifications produced by this TC._a313b5fa-1347-11e2-a828-da8497258a283PrinciplesArticulate the principles of the interoperable content management through formal specifications_a313b686-1347-11e2-a828-da8497258a283.1RelationshipsAssess the relationship of CMIS to other related standards and industry efforts. _a313b712-1347-11e2-a828-da8497258a283.2These include Java Content Repository (JCR) (JSR-170, JSR-283), WebDAV and its related specifications including DASL, Search Web Services TC, and other relevant standards.DefinitionDefine appropriate specifications for interoperable content management
_a313b79e-1347-11e2-a828-da8497258a283.3SchemasSchemas, such as XML Schema Definition (XSD)_a313b834-1347-11e2-a828-da8497258a283.3.1Service DefinitionsService definitions, such as Web Service Definition Language (WSDL)
_a313b8c0-1347-11e2-a828-da8497258a283.3.2Entities & CapabilitiesStandardize the common types of entities and capabilities in CM
_a313b94c-1347-11e2-a828-da8497258a283.4CooperationEncourage cooperation within and between the various topical domains and groups_a313b9ec-1347-11e2-a828-da8497258a283.5Next VersionWork on the next versions of the specification._a313ba82-1347-11e2-a828-da8497258a284After 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 CapabilitiesCore ECM Repository capabilities
_a313bb0e-1347-11e2-a828-da8497258a284.1Collaborative ApplicationsCollaborative Content Applications
_a313bbae-1347-11e2-a828-da8497258a284.2PortalsPortals leveraging Content Management repositories_a313bc44-1347-11e2-a828-da8497258a284.3MashupsMashups utilizing Content
_a313bcda-1347-11e2-a828-da8497258a284.4Workflow & BPMWorkflow and BPM-centric applications utilizing Content
_a313bdac-1347-11e2-a828-da8497258a284.5ArchivalContent Archival Applications
_a313be56-1347-11e2-a828-da8497258a284.6Compound & Virtual DocumentsCompound and Virtual Documents applications_a313bf00-1347-11e2-a828-da8497258a284.7DiscoveryElectronic and Legal Discovery of Content applications
_a313bfaa-1347-11e2-a828-da8497258a284.8Records ManagementRecords Management and Compliance
_a313c040-1347-11e2-a828-da8497258a284.9Digital Asset ManagementDigital Asset Management Applications
_a313c0e0-1347-11e2-a828-da8497258a284.10Web Content ManagementWeb Content Management Applications_a313c19e-1347-11e2-a828-da8497258a284.11Information Rights ManagementInformation Rights Management applications
_a313c23e-1347-11e2-a828-da8497258a284.12Desktop IntegrationDesktop Integration of Content Management repositories_a313c2de-1347-11e2-a828-da8497258a284.11Other BindingsThe TC MAY define other bindings explicitly listed below after the first deliverable.
_a313c39c-1347-11e2-a828-da8497258a285Web Services_a313c446-1347-11e2-a828-da8497258a285.1REST_a313c4f0-1347-11e2-a828-da8497258a285.2JSON-RPC_a313c5c2-1347-11e2-a828-da8497258a285.3XMPP_a313c716-1347-11e2-a828-da8497258a285.4JMS_a313c7d4-1347-11e2-a828-da8497258a285.5JCA _a313c89c-1347-11e2-a828-da8497258a285.6SMTP_a313c950-1347-11e2-a828-da8497258a285.72012-10-10https://www.oasis-open.org/committees/cmis/charter.phpOwenAmburOwen.Ambur@verizon.net