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_9984f7d8-1347-11e2-9525-b88297258a28The 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_9984fa80-1347-11e2-9525-b88297258a28To 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 _9984fb5c-1347-11e2-9525-b88297258a28Initial DeliverablesThe initial set of deliverables will be targeted for the following use cases _9984fc06-1347-11e2-9525-b88297258a281Collaborative Content Applications _9984fca6-1347-11e2-9525-b88297258a281.1PortalsPortals leveraging Content Management repositories_9984fd46-1347-11e2-9525-b88297258a281.2Mashups _9984fdfa-1347-11e2-9525-b88297258a281.3SearchingSearching a Content Repository _9984feae-1347-11e2-9525-b88297258a281.4Other Use CasesThe following use cases should be able to be supported by CMIS Domain Model and Bindings, but are not primary drivers _9984ff6c-1347-11e2-9525-b88297258a282 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 _9985003e-1347-11e2-9525-b88297258a282.1ArchivalArchival Applications _99850106-1347-11e2-9525-b88297258a282.2Compound and Virtual Documents _998501ce-1347-11e2-9525-b88297258a282.3DiscoveryElectronic and Legal Discovery _998502a0-1347-11e2-9525-b88297258a282.4SpecificationsEngage in maintenance of the specifications produced by this TC._9985039a-1347-11e2-9525-b88297258a283PrinciplesArticulate the principles of the interoperable content management through formal specifications_99850480-1347-11e2-9525-b88297258a283.1RelationshipsAssess the relationship of CMIS to other related standards and industry efforts. _99850552-1347-11e2-9525-b88297258a283.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 _99850638-1347-11e2-9525-b88297258a283.3SchemasSchemas, such as XML Schema Definition (XSD)_9985071e-1347-11e2-9525-b88297258a283.3.1Service DefinitionsService definitions, such as Web Service Definition Language (WSDL) _9985087c-1347-11e2-9525-b88297258a283.3.2Entities & CapabilitiesStandardize the common types of entities and capabilities in CM _99850980-1347-11e2-9525-b88297258a283.4CooperationEncourage cooperation within and between the various topical domains and groups_99850a7a-1347-11e2-9525-b88297258a283.5Next VersionWork on the next versions of the specification._99850b7e-1347-11e2-9525-b88297258a284After 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 _99850c8c-1347-11e2-9525-b88297258a284.1Collaborative ApplicationsCollaborative Content Applications _99850d90-1347-11e2-9525-b88297258a284.2PortalsPortals leveraging Content Management repositories_99850e9e-1347-11e2-9525-b88297258a284.3MashupsMashups utilizing Content _99850fc0-1347-11e2-9525-b88297258a284.4Workflow & BPMWorkflow and BPM-centric applications utilizing Content _998510e2-1347-11e2-9525-b88297258a284.5ArchivalContent Archival Applications _998511fa-1347-11e2-9525-b88297258a284.6Compound & Virtual DocumentsCompound and Virtual Documents applications_99851330-1347-11e2-9525-b88297258a284.7DiscoveryElectronic and Legal Discovery of Content applications _99851452-1347-11e2-9525-b88297258a284.8Records ManagementRecords Management and Compliance _99851588-1347-11e2-9525-b88297258a284.9Digital Asset ManagementDigital Asset Management Applications _998516c8-1347-11e2-9525-b88297258a284.10Web Content ManagementWeb Content Management Applications_99851812-1347-11e2-9525-b88297258a284.11Information Rights ManagementInformation Rights Management applications _99851966-1347-11e2-9525-b88297258a284.12Desktop IntegrationDesktop Integration of Content Management repositories_99851ac4-1347-11e2-9525-b88297258a284.11Other BindingsThe TC MAY define other bindings explicitly listed below after the first deliverable. _99851c0e-1347-11e2-9525-b88297258a285Web Services_99851d62-1347-11e2-9525-b88297258a285.1REST_99851ed4-1347-11e2-9525-b88297258a285.2JSON-RPC_99852028-1347-11e2-9525-b88297258a285.3XMPP_99852190-1347-11e2-9525-b88297258a285.4JMS _9985230c-1347-11e2-9525-b88297258a285.5JCA _9985247e-1347-11e2-9525-b88297258a285.6SMTP _998525f0-1347-11e2-9525-b88297258a285.72012-10-10https://www.oasis-open.org/committees/cmis/charter.phpOwenAmburOwen.Ambur@verizon.net