|
IBM Connections publishes a series of additive extensions to the CMIS standard to expose the Files application through the CMIS APIs. |
|
The Files CMIS API imposes some query restrictions on the CMIS query specification. |
|
The Files CMIS API supports extensions to support HTML form endpoints. To protect against CSRF attack vectors, all HTML form endpoints that accept a POST or PUT operation require a nonce security token to provided by the caller to complete. |
|
The Files API introduces a set of feature extensions to the standard CMIS domain model to support additional use cases for social file sharing. |
|
The Files CMIS API provides the following extension elements for use in CMIS responses. |
|
The Files CMIS API introduces the following features to support the ability to introspect downloads for a select resource. |
|
The Files CMIS API introduces the following features to support the ability to soft-delete and later choose to purge or restore select resources in the system. |
|
The Files CMIS API uses the following namespaces and prefixes when referring to XML or XML schema elements in the text or examples. |
|
Download history documents contain the representation for the set of download activities that have been logged by the service. This resource can be paged per the Atom Publishing Protocol (RFC5023). |
|
The Files CMIS API introduces the following features to express the who-shared-what-with-whom relationship on select resources. |
|
The Files CMIS API introduces the following features to support the ability to tag select resources, navigate by tag, or get a cloud of tags for a particular repository scope. |
|
The Files CMIS API provides the following extensions for use in CMIS clients to simplify interaction from a browser client that needs to use an HTML form to perform binary transfer operations. |
|
To update resources made available through the Atom APIs, you must retrieve the service document for the application. |
|
The Files CMIS API introduces the following features to enable the ability to manage recommendations on select resources. |
|
These are the CMIS object types that can show in repositories exposed in the Files CMIS API. |
|
The Files CMIS API defines the following link relations. |
|
Content appears in this folder based on system managed criteria |
|
An administrative policy that can be enforced by a repository. |
|
Administrative constraint to monitor system usage |
|
Folder |
|
The root object in the repository |
|
Container for comments about a specific file |
|
Container for user contributed folders |
|
Container for all comments about files in the system |
|
An explicit, binary, directional, non-invasive, and typed relationship between a source and target object. |