Content Management Interoperability Services ( CMIS ) is an open standard that allows different content management systems to inter-operate over the Internet . Specifically, CMIS defines an abstraction layer for controlling diverse document management systems and repositories using web protocols .
16-402: CMIS defines a domain model plus bindings that can be used by applications to manipulate content stored in a repository. CMIS provides a common data model covering typed files and folders with generic properties that can be set or read. There is a set of services for adding and retrieving documents ('objects'). There may be an access control system, a checkout and version control facility, and
32-442: A coherent platform. A conceptual model can be described using various notations, such as UML , ORM or OMT for object modelling, ITE , or IDEF1X for Entity Relationship Modelling . In UML notation, the conceptual model is often described with a class diagram in which classes represent concepts, associations represent relationships between concepts and role types of an association represent role types taken by instances of
48-439: A form influenced by design or implementation concerns. This is often used for defining different processes in a particular company or institute. A domain model is a system of abstractions that describes selected aspects of a sphere of knowledge, influence or activity (a domain ). The model can then be used to solve problems related to that domain. The domain model is a representation of meaningful real-world concepts pertinent to
64-472: A solution, where the conceptual model provides a key artifact of business understanding and clarity. Once the domain concepts have been modeled, the model becomes a stable basis for subsequent development of applications in the domain. The concepts of the conceptual model can be mapped into physical design or implementation constructs using either manual or automated code generation approaches . The realization of conceptual models of many domains can be combined to
80-619: Is a formal representation of a knowledge domain with concepts, roles, datatypes, individuals, and rules, typically grounded in a description logic . In the field of computer science a conceptual model aims to express the meaning of terms and concepts used by domain experts to discuss the problem, and to find the correct relationships between different concepts. The conceptual model is explicitly chosen to be independent of design or implementation concerns, for example, concurrency or data storage . Conceptual modeling in computer science should not be confused with other modeling disciplines within
96-488: Is available for public comment at OASIS. OASIS approved CMIS as an OASIS Specification on May 1, 2010. CMIS 1.1 has been approved as an OASIS specification on December 12, 2012. The specification is currently approved as OASIS CMIS v1.1 standard. There are public discussion lists. The TC was closed on May 9, 2017, and is no longer active. There is some discussion on the name of CMIS. Some blogs and authors say that it should be named "DMIS", with D for Document since it
112-577: Is generally implemented as an object model within a layer that uses a lower-level layer for persistence and "publishes" an API to a higher-level layer to gain access to the data and behavior of the model. In the Unified Modeling Language (UML), a class diagram is used to represent the domain model. Description logic Too Many Requests If you report this error to the Wikimedia System Administrators, please include
128-522: Is more targeted on ECM. From the CMIS Specification 1.1, page: "[...] this data model does not cover all the concepts that a full-function ECM repository [...] transient entities (such as programming interface objects), administrative entities (such as user profiles), and extended concepts (such as compound or virtual document, work flow and business process, event and subscription) are not included." A CMIS server stores content, and offers access via
144-496: The CMIS protocol. Some servers also allow access via other protocols. Each CMIS server declares a set of capabilities. For instance, servers that allow documents to be filed in different places declare the capability "Multifiling". This mechanism allows clients to interact differently with servers that support or don't support a particular operation. Some server products allow certain capabilities to be disabled or enabled by configuration.
160-400: The ability to define generic relations. Three protocol bindings are defined, one using WSDL and SOAP , another using AtomPub , and a last browser-friendly one using JSON . The model is based on common architectures of document management systems. The CMIS specification provides an API that is programming language-agnostic , as REST and SOAP are implemented in many languages. Many of
176-446: The broader field of conceptual models such as data modelling , logical modelling and physical modelling. The conceptual model attempts to clarify the meaning of various, usually ambiguous terms, and ensure that confusion caused by different interpretations of the terms and concepts cannot occur. Such differing interpretations could easily cause confusion amongst stakeholders, especially those responsible for designing and implementing
SECTION 10
#1732858996181192-506: The domain that need to be modeled in software. The concepts include the data involved in the business and rules the business uses in relation to that data. A domain model leverages natural language of the domain. A domain model generally uses the vocabulary of the domain, thus allowing a representation of the model to be communicated to non-technical stakeholders. It should not refer to any technical implementations such as databases or software components that are being designed. A domain model
208-401: The modelled concepts in various situations. In ER notation, the conceptual model is described with an ER Diagram in which entities represent concepts, cardinality and optionality represent relationships between concepts. Regardless of the notation used, it is important not to compromise the richness and clarity of the business meaning depicted in the conceptual model by expressing it directly in
224-570: The momentum and use cases that led to the CMIS proposal was conducted by the iECM Initiative sponsored by AIIM. This ongoing project to foster interoperability among ECM systems is supported by the collaborative efforts of governmental, commercial, vendor, and consulting organizations. Although initiated by AIIM, CMIS is now administered by OASIS , a web standards consortium. Participants in the process include Adobe Systems Incorporated , Alfresco , EMC , FatWire , HP , IBM , Liferay , Microsoft , Nuxeo , OpenText , Oracle , and SAP . The standard
240-406: The original contributors to the specification believed a simplified and standardized way to access unstructured content across all vendors would increase the adoption of ECM products, but only if the standard could remain compatible with existing deployed systems, much the way that ODBC Open Database Connectivity did for the relational database market in the 1990s. The initial work of developing
256-403: The table below lists maximum capabilities. A CMIS server library allows developers to create CMIS server applications. A CMIS client application typically allows users to browse, read and modify content. Domain model In software engineering , a domain model is a conceptual model of the domain that incorporates both behavior and data. In ontology engineering , a domain model
#180819