Content Management Interoperability Services (CMIS) Version 1.1

– cmisra:collectiontype = 'update'
The workspace element MUST also contain the following link element with the relation:
http://docs.oasis-open.org/ns/cmis/link/200908/typedescendants
• This link relation points to the Type Descendants Feed for the base types in the repository.
The workspace element MUST contain the following link elements of the following relations for those services
which are supported by the repository:
http://docs.oasis-open.org/ns/cmis/link/200908/foldertree
• This link relation points to the Folder Tree Feed for the root folder.
http://docs.oasis-open.org/ns/cmis/link/200908/rootdescendants
• This link relation points to the Folder Descendants Feed for the root folder.
http://docs.oasis-open.org/ns/cmis/link/200908/changes
• This link relation points to the Changes Feed for the repository.
The workspace element may include app:collection elements for the collections that represent folders
in the repository. However, an alternative approach, especially for a repository with many folders, is to not
enumerate those collections here, but include the app:collection element per [RFC5023] in the Atom
Feed document.
The repository MUST include the URI templates in the workspace elements.
3.7.1.1 URI Templates
CMIS defines the following URI templates:
• objectbyid
• objectbypath
• query
• typebyid
Repositories MUST provide the following URI templates:
• objectbyid
• objectbypath
• typebyid
Repositories MUST provide the URI template query if the repository supports query.
Repositories MAY extend that set of templates. Those URI template types will be repository specific. Repositories
MAY have more than one entry per URI template type if the entries have different media types.
URI templates are simple replacement of the template parameter with the specified value. If a client does
not want to specify a value for some of these variables, then the client MUST substitute an empty string for
the variable.
For example, if the URI template that supports the variable {id} is:
http://example.com/rep1/getbyid/{id}
If the client wants to find the entry for an object with an id of 'obj_1' then the URI would be:
http://example.com/rep1/getbyid/obj_1
CMIS-v1.1-csprd01
Standards Track Work Product
Copyright © OASIS Open 2012. All Rights Reserved.
18 August 2012
Page 219 of 331