CMIS defines a data model, which encapsulates the core concepts found in most repositories. Content Services provides an implementation of the CMIS bindings and maps the content metamodel to the CMIS domain model. This allows content models defined in Content Services to be exposed and manipulated by using CMIS.
The following summarizes the CMIS data model:
The core of the domain model allows for the definition of object types with associated properties. A type ID identifies types, which inherits their definition from a parent type. Features of a type include whether they can be queried by the CMIS query language, filed into multiple folders, and controlled by using permissions. Features of a property include its data type, whether a value is required, and a default value if one is not explicitly provided.
Because these features are familiar, you can map between the CMIS data model and the content metamodel with little loss of information.
The Content Services content metamodel is mapped to the CMIS data model as follows:
- Type: Maps to CMIS Object Type
- Property: Maps to CMIS Property Definition
- Peer Association: Maps to CMIS Relationship