In the context of CMIS, the object type definition (or "type definition" for short) defines the CMIS objects, along with their respective properties, functions, and constraints, within a repository.
The object type definition specifies what a particular object type looks like and what function it performs. The type definition describes the following levels:
-
Properties of objects of this type.
-
Allowed functions (e.g., versioning objects or saving them in folders).
-
Applicable restrictions (e.g., whether a content stream is permitted or even required).
One notable feature is that object type definitions can inherit properties from one another. If an object type definition is derived from another type definition, the child type definition inherits all properties of the parent type definition.
Benefits of object type definitions
-
The repository validates each object based on its type definition. If an object does not match the definition, it is rejected.
-
Type definitions enable the creation of custom document types (categories) for your organization (e.g., Invoice, Contract, Packing slip) based on the CMIS base types.
-
Type definitions ensure interoperability: Every CMIS-compliant system understands the type definitions and can work with them accordingly.