Content Management Interoperability Services (CMIS) Version 1.1

The repository MAY also create new document objects in a "major version" state. This state is logically
equivalent to having a version series that contains exactly one major version and 0 other documents.
The repository MAY also create new document objects in a "non-major version" state. This state is logically
equivalent to having a version series that contains exactly one non-major version and 0 other documents.
If the repository does not support versioning the repository MUST ignore the value of the versioningState
parameter.
2.1.13.8 Version Specific/Independent membership in Folders
Repositories MAY treat membership of a document object in a folder collection as "version-specific" or
"version-independent".
Repositories MUST indicate whether they support version-specific membership in a folder via the "capabilityVersionSpecificFiling"
optional capability flag. (See section 2.1.1.1 Optional Capabilities.)
If the repository is treating folder collection membership as "version-independent", then:
• Moving or filing a document object into a folder MUST result in ALL documents in the version series
being moved/filed into the folder.
• The repository MAY return only the latest-version OR latest major-version document object in a version
series in the response to Navigation service requests (getChildren, getDescendants), and NEED
NOT return other document objects filed in the folder that are in the version series.
If the repository is treating folder collection membership as "version-specific", then moving or filing a document
object into a folder MUST NOT result in other documents in the version series being moved/filed.
2.1.13.9 Version Specific/Independent membership in Relationships
A relationship object MAY have either a version-specific or version-independent binding to its source and/or
target objects. This behavior MAY vary between repositories and between individual relationship types
defined for a repository.
If a relationship object has a version-independent binding to its source/target object, then:
• The getObjectRelationships service invoked on a document object MUST return the relationship
if relationship was source/target is set to ANY Document Object in the version series.
If a relationship object has a version-specific binding to its source/target object, then:
• The getObjectRelationships service invoked on a document object MUST return the relationship
if relationship was source/target is set to the id of the document object on which the service was
invoked.
2.1.13.10 Versioning visibility in Query Services
Repositories MAY include non-latest-versions of document objects in results to the query service.
Repositories MUST indicate whether they support querying for non-latest-versions via the "capabilityAllVersionsSearchable"
optional capability flag. (See section 2.1.1.1 Optional Capabilities.)
If "capabilityAllVersionsSearchable" is TRUE then the repository MUST include in the query results ANY
document object in the version series that matches the query criteria. (Subject to other query constraints
such as security.)
Additionally, repositories MAY include Private Working Copy objects in results to the query service. Repositories
MUST indicate whether they support querying for Private Working Copy objects via the "capabilityP-
WCSearchable" optional capability flag.
CMIS-v1.1-csprd01
Standards Track Work Product
Copyright © OASIS Open 2012. All Rights Reserved.
18 August 2012
Page 99 of 331