298
Content Management Interoperability Services (CMIS) Version 1.0 Committee Draft 06 11 January 2010 Specification URIs: This Version: http://docs.oasis-open.org/cmis/CMIS/v1.0/cd06/cmis-spec-v1.0.doc (Authoritative) http://docs.oasis-open.org/cmis/CMIS/v1.0/cd06/cmis-spec-v1.0.html http://docs.oasis-open.org/cmis/CMIS/v1.0/cd06/cmis-spec-v1.0.pdf Previous Version: http://docs.oasis-open.org/cmis/CMIS/v1.0/cd04/cmis-spec-v1.0.doc (Authoritative) http://docs.oasis-open.org/cmis/CMIS/v1.0/cd04/cmis-spec-v1.0.html http://docs.oasis-open.org/cmis/CMIS/v1.0/cd04/cmis-spec-v1.0.pdf Latest Version: http://docs.oasis-open.org/cmis/CMIS/v1.0/cmis-spec-v1.0.doc (Authoritative) http://docs.oasis-open.org/cmis/CMIS/v1.0/cmis-spec-v1.0.html http://docs.oasis-open.org/cmis/CMIS/v1.0/cmis-spec-v1.0.pdf Technical Committee: OASIS Content Management Interoperability Services (CMIS) TC Chair(s): David Choy, EMC Editor(s): Al Brown, IBM Ethan Gur-Esh, Microsoft Ryan McVeigh, Oracle Florian Müller, OpenText Related work: N/A cmis-spec-v1.0 11 January 2010 Copyright © OASIS® 2010. All Rights Reserved. Page 1 of 298 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 1 2 3

OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

  • Upload
    others

  • View
    4

  • Download
    0

Embed Size (px)

Citation preview

Page 1: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Content Management Interoperability Services (CMIS) Version 1.0Committee Draft 0611 January 2010Specification URIs:This Version:

http://docs.oasis-open.org/cmis/CMIS/v1.0/cd06/cmis-spec-v1.0.doc (Authoritative)http://docs.oasis-open.org/cmis/CMIS/v1.0/cd06/cmis-spec-v1.0.htmlhttp://docs.oasis-open.org/cmis/CMIS/v1.0/cd06/cmis-spec-v1.0.pdf

Previous Version:http://docs.oasis-open.org/cmis/CMIS/v1.0/cd04/cmis-spec-v1.0.doc (Authoritative)http://docs.oasis-open.org/cmis/CMIS/v1.0/cd04/cmis-spec-v1.0.htmlhttp://docs.oasis-open.org/cmis/CMIS/v1.0/cd04/cmis-spec-v1.0.pdf

Latest Version:http://docs.oasis-open.org/cmis/CMIS/v1.0/cmis-spec-v1.0.doc (Authoritative)http://docs.oasis-open.org/cmis/CMIS/v1.0/cmis-spec-v1.0.htmlhttp://docs.oasis-open.org/cmis/CMIS/v1.0/cmis-spec-v1.0.pdf

Technical Committee:OASIS Content Management Interoperability Services (CMIS) TC

Chair(s):David Choy, EMC

Editor(s):Al Brown, IBMEthan Gur-Esh, MicrosoftRyan McVeigh, OracleFlorian Müller, OpenText

Related work:N/A

Declared XML Namespace(s):http://docs.oasis-open.org/ns/cmis/core/200908/ http://docs.oasis-open.org/ns/cmis/restatom/200908/ http://docs.oasis-open.org/ns/cmis/messaging/200908/http://docs.oasis-open.org/ns/cmis/ws/200908/ http://docs.oasis-open.org/ns/cmis/link/200908/

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 1 of 240

1

2

3

4

5

67891011121314151617181920212223242526272829303132333435363738

123

Page 2: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Abstract:The Content Management Interoperability Services (CMIS) standard defines a domain model and Web Services and Restful AtomPub bindings that can be used by applications to work with one or more Content Management repositories/systems.

The CMIS interface is designed to be layered on top of existing Content Management systems and their existing programmatic interfaces. It is not intended to prescribe how specific features should be implemented within those CM systems, not to exhaustively expose all of the CM system’s capabilities through the CMIS interfaces. Rather, it is intended to define a generic/universal set of capabilities provided by a CM system and a set of services for working with those capabilities.

Status:This document was last revised or approved by the CMIS TC on the above date. The level of approval is also listed above. Check the “Latest Version” or “Latest Approved Version” location noted above for possible later revisions of this document.Technical Committee members should send comments on this specification to the Technical Committee’s email list. Others should send comments to the Technical Committee by using the “Send A Comment” button on the Technical Committee’s web page at http://www.oasis-open.org/committees/cmis/.For information on whether any patents have been disclosed that may be essential to implementing this specification, and any offers of patent licensing terms, please refer to the Intellectual Property Rights section of the Technical Committee web page (http://www.oasis-open.org/committees/cmis/ipr.php).The non-normative errata page for this specification is located at http://www.oasis-open.org/committees/cmis/.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 2 of 240

394041424344454647484950

515253545556575859606162636465

456

Page 3: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

NoticesCopyright © OASIS® 2009, 2010. All Rights Reserved.All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website.This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this section are included on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to OASIS, except as needed for the purpose of developing any document or deliverable produced by an OASIS Technical Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must be followed) or as required to translate it into languages other than English.The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.OASIS requests that any OASIS Party or any other party that believes it has patent claims that would necessarily be infringed by implementations of this OASIS Committee Specification or OASIS Standard, to notify OASIS TC Administrator and provide an indication of its willingness to grant patent licenses to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification.OASIS invites any party to contact the OASIS TC Administrator if it is aware of a claim of ownership of any patent claims that would necessarily be infringed by implementations of this specification by a patent holder that is not willing to provide a license to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification. OASIS may include such claims on its website, but disclaims any obligation to do so.OASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS' procedures with respect to rights in any document or deliverable produced by an OASIS Technical Committee can be found on the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this OASIS Committee Specification or OASIS Standard, can be obtained from the OASIS TC Administrator. OASIS makes no representation that any information or list of intellectual property rights will at any time be complete, or that any claims in such list are, in fact, Essential Claims.The names "OASIS", “CMIS” are trademarks of OASIS, the owner and developer of this specification, and should be used only to refer to the organization and its official outputs. OASIS welcomes reference to, and implementation and use of, specifications, while reserving the right to enforce its marks against misleading uses. Please see http://www.oasis-open.org/who/trademark.php for above guidance.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 3 of 240

66

676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109

110

789

Page 4: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Table of Contents1 Introduction....................................................................................................................................... 10

1.1 Terminology..................................................................................................................................... 101.2 Normative References.....................................................................................................................101.3 Non-Normative References.............................................................................................................10

2 Domain Model................................................................................................................................... 112.1 Data Model...................................................................................................................................... 11

2.1.1 Repository................................................................................................................................ 112.1.1.1 Optional Capabilities...........................................................................................................................11

See Section: 2.8 Access Control .............................................................................................................142.1.1.2 Implementation Information................................................................................................................14

2.1.2 Object....................................................................................................................................... 142.1.2.1 Property..............................................................................................................................................15

2.1.3 Object-Type.............................................................................................................................. 162.1.3.1 Object-Type Hierarchy and Inheritance..............................................................................................162.1.3.2 Object-Type Attributes........................................................................................................................172.1.3.3 Object-Type Property Definitions........................................................................................................19

2.1.4 Document Object.....................................................................................................................232.1.4.1 Content Stream...................................................................................................................................242.1.4.2 Renditions...........................................................................................................................................242.1.4.3 Document Object-Type Definition.......................................................................................................25

2.1.5 Folder Object............................................................................................................................ 332.1.5.1 File-able Objects.................................................................................................................................332.1.5.2 Folder Hierarchy.................................................................................................................................342.1.5.3 Paths...................................................................................................................................................352.1.5.4 Folder Object-Type Definition.............................................................................................................36

2.1.6 Relationship Object.................................................................................................................. 402.1.6.1 Relationship Object-Type Definition....................................................................................................41

2.1.7 Policy Object............................................................................................................................ 452.1.7.1 Policy Object-Type Definition..............................................................................................................46

2.1.8 Access Control.........................................................................................................................502.1.8.1 ACL, ACE, Principal, and Permission.................................................................................................502.1.8.2 CMIS Permissions..............................................................................................................................502.1.8.3 ACL Capabilities.................................................................................................................................50

2.1.9 Versioning................................................................................................................................ 592.1.9.1 Version Series.....................................................................................................................................592.1.9.2 Latest Version.....................................................................................................................................592.1.9.3 Major Versions....................................................................................................................................592.1.9.4 Services that modify Version Series...................................................................................................602.1.9.5 Versioning Properties on Document Objects......................................................................................612.1.9.6 Document Creation and Initial Versioning State.................................................................................622.1.9.7 Version Specific/Independent membership in Folders........................................................................622.1.9.8 Version Specific/Independent membership in Relationships..............................................................622.1.9.9 Versioning visibility in Query Services................................................................................................63

2.1.10 Query..................................................................................................................................... 63

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 4 of 240

111

112113114115116117118119

120121

122123

124125126127

128129130131

132133134135136

137138

139140

141142143144

145146147148149150151152153154

155

101112

Page 5: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

2.1.10.1 Relational View Projection of the CMIS Data Model.........................................................................642.1.10.2 Query Language Definition...............................................................................................................652.1.10.3 Escaping...........................................................................................................................................74

2.1.11 Change Log............................................................................................................................ 742.1.11.1 Completeness of the Change Log....................................................................................................752.1.11.2 Change Log Token...........................................................................................................................752.1.11.3 Change Event...................................................................................................................................75

2.2 Services........................................................................................................................................... 752.2.1 Common Service Elements......................................................................................................76

2.2.1.1 Paging.................................................................................................................................................762.2.1.2 Retrieving additional information on objects in CMIS service calls.....................................................762.2.1.3 Change Tokens...................................................................................................................................782.2.1.4 Exceptions..........................................................................................................................................792.2.1.5 ACLs...................................................................................................................................................82

2.2.2 Repository Services................................................................................................................. 822.2.2.1 getRepositories...................................................................................................................................822.2.2.2 getRepositoryInfo................................................................................................................................832.2.2.3 getTypeChildren..................................................................................................................................842.2.2.4 getTypeDescendants..........................................................................................................................852.2.2.5 getTypeDefinition................................................................................................................................86

2.2.3 Navigation Services.................................................................................................................862.2.3.1 getChildren..........................................................................................................................................862.2.3.2 getDescendants..................................................................................................................................872.2.3.3 getFolderTree.....................................................................................................................................882.2.3.4 getFolderParent..................................................................................................................................892.2.3.5 getObjectParents................................................................................................................................902.2.3.6 getCheckedOutDocs...........................................................................................................................91

2.2.4 Object Services........................................................................................................................ 922.2.4.1 createDocument..................................................................................................................................922.2.4.2 createDocumentFromSource..............................................................................................................932.2.4.3 createFolder........................................................................................................................................942.2.4.4 createRelationship..............................................................................................................................952.2.4.5 createPolicy........................................................................................................................................962.2.4.6 getAllowableActions............................................................................................................................972.2.4.7 getObject.............................................................................................................................................972.2.4.8 getProperties.......................................................................................................................................982.2.4.9 getObjectByPath.................................................................................................................................992.2.4.10 getContentStream.............................................................................................................................992.2.4.11 getRenditions..................................................................................................................................1002.2.4.12 updateProperties.............................................................................................................................1002.2.4.13 moveObject.....................................................................................................................................1012.2.4.14 deleteObject....................................................................................................................................1022.2.4.15 deleteTree.......................................................................................................................................1022.2.4.16 setContentStream...........................................................................................................................1032.2.4.17 deleteContentStream......................................................................................................................104

2.2.5 Multi-filing Services................................................................................................................1042.2.5.1 addObjectToFolder...........................................................................................................................1042.2.5.2 removeObjectFromFolder.................................................................................................................105

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 5 of 240

156157158

159160161162

163164165166167168169

170171172173174175

176177178179180181182

183184185186187188189190191192193194195196197198199200

201202203

131415

Page 6: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

2.2.6 Discovery Services................................................................................................................. 1052.2.6.1 query................................................................................................................................................. 1052.2.6.2 getContentChanges..........................................................................................................................106

2.2.7 Versioning Services...............................................................................................................1072.2.7.1 checkOut...........................................................................................................................................1072.2.7.2 cancelCheckOut................................................................................................................................1082.2.7.3 checkIn..............................................................................................................................................1082.2.7.4 getObjectOfLatestVersion.................................................................................................................1092.2.7.5 getPropertiesOfLatestVersion...........................................................................................................1102.2.7.6 getAllVersions...................................................................................................................................111

2.2.8 Relationship Services.............................................................................................................1112.2.8.1 getObjectRelationships.....................................................................................................................111

2.2.9 Policy Services....................................................................................................................... 1122.2.9.1 applyPolicy........................................................................................................................................1132.2.9.2 removePolicy....................................................................................................................................1132.2.9.3 getAppliedPolicies.............................................................................................................................113

2.2.10 ACL Services.......................................................................................................................1142.2.10.1 getACL............................................................................................................................................1142.2.10.2 applyACL........................................................................................................................................114

3 Restful AtomPub Binding................................................................................................................1163.1 Overview....................................................................................................................................... 116

3.1.1 Namespaces..........................................................................................................................1163.1.2 Authentication........................................................................................................................1163.1.3 Response Formats.................................................................................................................1163.1.4 Optional Arguments...............................................................................................................1173.1.5 Errors and Exceptions............................................................................................................1173.1.6 Renditions.............................................................................................................................. 1173.1.7 Content Streams.................................................................................................................... 1173.1.8 Paging of Feeds..................................................................................................................... 1173.1.9 Services not Exposed............................................................................................................117

3.2 HTTP............................................................................................................................................. 1183.2.1 Entity Tag............................................................................................................................... 1183.2.2 HTTP Range..........................................................................................................................1183.2.3 HTTP OPTIONS Method........................................................................................................1183.2.4 HTTP Status Codes...............................................................................................................118

3.2.4.1 CommonGeneral CMIS Exceptions..................................................................................................1183.2.4.2 OtherSpecific Exceptions..................................................................................................................1193.2.4.3 Notable HTTP Status Codes.............................................................................................................119

3.3 Media Types.................................................................................................................................. 1193.3.1 CMIS Atom............................................................................................................................. 1203.3.2 CMIS Query........................................................................................................................... 1203.3.3 CMIS Allowable Actions.........................................................................................................1213.3.4 CMIS Tree.............................................................................................................................. 1223.3.5 CMIS ACL.............................................................................................................................. 126

3.4 Atom Extensions for CMIS............................................................................................................1273.4.1 Atom Element Extensions......................................................................................................127

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 6 of 240

204205206

207208209210211212213

214215

216217218219

220221222

223224225226227228229230231232233234235236237238239240241

242243244245246247248249

161718

Page 7: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

3.4.1.1 AtomPub Workspace........................................................................................................................1273.4.1.2 Atom Feed........................................................................................................................................1273.4.1.3 Atom Entry........................................................................................................................................127

3.4.2 Attributes................................................................................................................................ 1283.4.2.1 cmisra:id............................................................................................................................................1283.4.2.2 cmisra:renditionKind.........................................................................................................................128

3.4.3 CMIS Link Relations...............................................................................................................1293.4.3.1 Existing Link Relations......................................................................................................................1293.4.3.2 Hierarchy Navigation Internet Draft Link Relations...........................................................................1313.4.3.3 Versioning Internet Draft Link Relations...........................................................................................1313.4.3.4 CMIS Specific Link Relations............................................................................................................131

3.5 Atom Resources............................................................................................................................ 1333.5.1 Feeds..................................................................................................................................... 1333.5.2 Entries.................................................................................................................................... 134

3.5.2.1 Hierarchical Atom Entries.................................................................................................................1353.6 AtomPub Service Document (Repository).....................................................................................136

3.6.1 URI Templates....................................................................................................................... 1383.6.1.1 Object By Id......................................................................................................................................1393.6.1.2 Object By Path..................................................................................................................................1403.6.1.3 Query................................................................................................................................................ 1413.6.1.4 Type By Id.........................................................................................................................................141

3.6.2 HTTP Methods.......................................................................................................................1423.6.2.1 GET................................................................................................................................................... 142

3.7 Service Collections........................................................................................................................ 1423.7.1 Root Folder Collection............................................................................................................1423.7.2 Query Collection..................................................................................................................... 142

3.7.2.1 POST................................................................................................................................................ 1433.7.3 Checked Out Collection.........................................................................................................145

3.7.3.1 GET................................................................................................................................................... 1463.7.3.2 POST................................................................................................................................................ 146

3.7.4 Unfiled Collection................................................................................................................... 1493.7.4.1 GETPOST.........................................................................................................................................150

3.7.4.2 POST5 Types Children Collection.......................................................................................1533.7.5 Types Children Collection.1 GET.........................................................................................................154

3.7.5.1 GET8 Collections.....................................................................................................................1543.8 Collections.1 Relationships Collection......................................................................................154

3.8.1 Relationships Collection.1 GET...........................................................................................................1553.8.1.1 GET2 POST......................................................................................................................................155

3.8.1.2 POSTFolder Children Collection.........................................................................................1583.8.2 Folder Children Collection.1 GET........................................................................................................1593.8.2.1 GET2 POST......................................................................................................................................159

3.8.2.2 POST3 Policies Collection..................................................................................................1663.8.3 Policies Collection.1 GET....................................................................................................................1673.8.3.1 GET2 POST......................................................................................................................................1673.8.3.2 POST3 DELETE...............................................................................................................................167

3.9 Feeds............................................................................................................................................ 1693.9.1 Object Parents Feed..............................................................................................................170

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 7 of 240

250251252

253254255

256257258259260

261262263264

265266267268269270

271272

273274275276

277278279

280281

282283

284285286287

288289290

291292293294

295296

192021

Page 8: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

3.9.1.1 GET................................................................................................................................................... 1723.9.2 Changes................................................................................................................................. 172

3.9.2.1 GET................................................................................................................................................... 1783.9.3 Folder Descendants...............................................................................................................178

3.9.3.1 GET................................................................................................................................................... 1833.9.3.2 DELETE............................................................................................................................................184

3.9.4 Folder Tree............................................................................................................................. 1843.9.4.1 GET................................................................................................................................................... 1873.9.4.2 DELETE............................................................................................................................................187

3.9.5 AllVersions Feed.................................................................................................................... 1873.9.5.1 GET................................................................................................................................................... 1893.9.5.2 DELETE............................................................................................................................................189

3.9.6 Type Descendants Feed........................................................................................................1893.9.6.1 GET................................................................................................................................................... 197

3.10 Resources................................................................................................................................... 1983.10.1 Type Entry............................................................................................................................ 198

3.10.1.1 GET.................................................................................................................................................1983.10.2 Document Entry...................................................................................................................200

3.10.2.1 GET.................................................................................................................................................2003.10.2.2 PUT.................................................................................................................................................2023.10.2.3 DELETE..........................................................................................................................................202

3.10.3 Document Private Working Copy (PWC) Entry....................................................................2023.10.3.1 GET.................................................................................................................................................2033.10.3.2 PUT.................................................................................................................................................2053.10.3.3 DELETE..........................................................................................................................................205

Success HTTP code: 204 .......................................................................................3.10.4 Folder Entry ........................................................................................................................................................ 205

3.10.4 Folder Entry.1 GET............................................................................................................................2063.10.4.1 GET2 PUT......................................................................................................................................2083.10.4.2 PUT3 DELETE................................................................................................................................208

3.10.4.3 DELETE5 Relationship Entry............................................................................................2083.10.5 Relationship Entry.1 GET..................................................................................................................2093.10.5.1 GET2 PUT......................................................................................................................................2103.10.5.2 PUT3 DELETE................................................................................................................................210

3.10.5.3 DELETE6 Policy Entry......................................................................................................2103.10.6 Policy Entry.1 GET.............................................................................................................................2113.10.6.1 GET2 PUT......................................................................................................................................2123.10.6.2 PUT3 DELETE................................................................................................................................212

3.10.6.3 DELETE7 Content Stream................................................................................................2123.10.7 Content Stream.1 GET......................................................................................................................2133.10.7.1 GET2 PUT......................................................................................................................................2133.10.7.2 PUT3 DELETE................................................................................................................................213

3.10.7.3 DELETE8 ACL Resource..................................................................................................2133.10.8 ACL Resource.1 GET........................................................................................................................213

3.10.8.1 GET ............................................................................................................................................... 4 Web Services Binding ..................................................................................................................... 215

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 8 of 240

297

298299

300301302

303304305

306307308

309310

311312313

314315316317

318319320321

322323324325326

327328329330

331332333334

335336337338

339340

341342

222324

Page 9: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

4 .............................................................................................................................Web Services Binding ............................................................................................................................................. 4.1 Overview ............................................................................................................................................................ 215

4.1 Overview.1 WS-I....................................................................................................................... 2154.1.1 WS-I2 Authentication.............................................................................................................2154.1.2 Authentication3 Content Transfer...........................................................................................2154.1.3 Content Transfer4 Reporting Errors.......................................................................................215

4.1.4 Reporting Errors .......................................................................4.2 Web Services Binding Mapping ............................................................................................................................................................ 2154.2 Web3 Additions to the Services Binding Mappingsection..............................................................215

4.3 Additions to the Services section ..........................4.3.1 updateProperties and checkIn Semantics ........................................................................................................................................................ 2154.3.1 updateProperties and checkIn Semantics .................................................4.3.2 Content Ranges ........................................................................................................................................................ 2154.3.2 Content Ranges3 Extensions.................................................................................................2164.3.3 Extensions4 Web Services Specific Structures......................................................................216

4.3.4 Web Services Specific Structures.1 cmisFaultType and cmisFault.....................................................2164.3.4.1 cmisFaultType and cmisFault2 cmisRepositoryEntryType...............................................................2164.3.4.2 cmisRepositoryEntryType3 cmisTypeContainer...............................................................................2164.3.4.3 cmisTypeContainer4 cmisTypeDefinitionListType............................................................................2164.3.4.4 cmisTypeDefinitionListType .................4.3.4.5 cmisObjectInFolderType, cmisObjectParentsType and cmisObjectInFolderContainerType ...............................................................................................................2164.3.4.5 cmisObjectInFolderType, cmisObjectParentsType and cmisObjectInFolderContainerType ......4.3.4.6 cmisObjectListType and cmisObjectInFolderListType ..................................................................................2164.3.4.6 cmisObjectListType and cmisObjectInFolderListType ........................4.3.4.7 cmisContentStreamType ...................................................................................................................................................................... 2174.3.4.7 cmisContentStreamType8 cmisACLType.........................................................................................2174.3.4.8 cmisACLType9 cmisExtensionType.................................................................................................217

4.3.4.9 cmisExtensionType .......................................................................................................................... 5 IANA Considerations ....................................................................................................................... 218

5 ...............................................................................................................................IANA Considerations ................................................................................................................... 5.1 Content-Type Registration ............................................................................................................................................................ 218

5.1 Content-Type Registration.1 CMIS Query.................................................................................2185.1.12 CMIS QueryAllowableActions..............................................................................................2185.1.23 CMIS AllowableActionsTree.................................................................................................2195.1.34 CMIS TreeAtom................................................................................................................... 2205.1.45 CMIS AtomACL.................................................................................................................... 221

5.1.5 CMIS ACL .................................................................................................................... 6 Conformance ................................................................................................................................................................. 2236 Conformance A. Acknowledgements 225A. Acknowledgements ............................................................................................................................B. Non-Normative Text ........................................................................................................................227B. Non-Normative Text ..........................................................................................................................C. Revision History .............................................................................................................................. 228C. Revision History .............................................................................................................................. 226

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 9 of 240

343344345346347348349350351352353354355356357358359360361362363364365366367368369370

371372373374375376377378379380381382383384385386387388

389390

252627

Page 10: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

1 IntroductionThe Content Management Interoperability Services (CMIS) standard defines a domain model and set of bindings such as Web Services and ReSTful AtomPub that can be used by applications to work with one or more Content Management repositories/systems. The CMIS interface is designed to be layered on top of existing Content Management systems and their existing programmatic interfaces. It is not intended to prescribe how specific features should be implemented within those CM systems, nor to exhaustively expose all of the CM system’s capabilities through the CMIS interfaces. Rather, it is intended to define a generic/universal set of capabilities provided by a CM system and a set of services for working with those capabilities.

1.1 TerminologyThe key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC2119.

1.2 Normative References[RFC4287] M. Nottingham, R. Sayre, Atom Syndication Format,

http://www.ietf.org/rfc/rfc4287.txt, December 2005[RFC5023] J. Gregorio, B. de hOra, Atom Publishing Protocol,

http://www.ietf.org/rfc/rfc5023.txt, October 2007[RFC2616] R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P. Leach, T. Berners-

Lee, Hypertext Transfer Protocol --HTTP/1.1, http://www.ietf.org/rfc/rfc2616.txt, June 1999

[RFC2119] S. Bradner, Key words for use in RFCs to Indicate Requirement Levels, http://www.ietf.org/rfc/rfc2119.txt, March 1997

[RFC4918] L. Dusseault, HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV), June 2007

[RFC3986] T. Berners-Lee, R. Fielding, L. Masinter, Unified Resource Identifier, January 2005

[CMISDM] OASIS, Committee Draft 0.63, “Content Management Interoperability Services (CMIS) Domain Model”, March 2009

1.3 Non-Normative References

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 10 of 240

391392393394395396397398399

400401402403

404405406407408409410411412413414415416417418419

420

282930

Page 11: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

2 Domain Model2.1 Data ModelCMIS provides an interface for an application to access a Repository. To do so, CMIS specifies a core data model that defines the persistent information entities that are managed by the repository, and specifies a set of basic services that an application can use to access and manipulate these entities. In accordance with the CMIS objectives, this data model does not cover all the concepts that a full-function ECM repository typically supports. Specifically, transient entities (such as programming interface objects), administrative entities (such as user profiles), and extended concepts (such as compound or virtual document, work flow and business process, event and subscription) are not included.However, when an application connects to a CMIS service endpoint, the same endpoint MAY provide access to more than one CMIS repository. (How an application obtains a CMIS service endpoint is outside the scope of CMIS. How the application connects to the endpoint is a part of the protocol that the application uses.) An application MUST use the CMIS “Get Repositories” service (getRepositories) to obtain a list of repositories that are available at that endpoint. The Repository Identity MUST uniquely identify an available repository at this service endpoint. Both the repository name and the repository identity are opaque to CMIS. Aside from the “Get Repositories” service, all other CMIS services are single-repository-scoped, and require a Repository Identity as an input parameter. In other words, except for the “Get Repositories” service, multi-repository and inter-repository operations are not supported by CMIS.

2.1.1 RepositoryThe repository itself is described by the CMIS “Get Repository Information” service. The service output is fully described in section 2.2.2.2 getRepositoryInfo.

2.1.1.1 Optional CapabilitiesCommercial ECM repositories vary in their designs. Moreover, some repositories are designed for a specific application domain and may not provide certain capabilities that are not needed for their targeted domain. Thus, a repository implementation may not necessarily be able to support all CMIS capabilities. A few CMIS capabilities are therefore “optional” for a repository to be compliant. A repository’s support for each of these optional capabilities is discoverable using the getRepositoryInfo service. The following is the list of these optional capabilities. All capabilities are “Boolean” (i.e. the Repository either supports the capability entirely or not at all) unless otherwise noted.

Navigation Capabilities:capabilityGetDescendants

Ability for an application to enumerate the descendants of a folder via the getDescendants service.See section: 2.2.3.2 getDescendants

capabilityGetFolderTreeAbility for an application to retrieve the folder tree via the getFolderTree service.See section: 2.2.3.3 getFolderTree

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 11 of 240

421

422423424425426427428429430431432433434435436437438439

440441442

443444445446447448449450

451452453

454455456

457458

459460

461

313233

Page 12: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Object Capabilities:capabilityContentStreamUpdatability (enumCapabilityContentStreamUpdates)

Indicates the support a repository has for updating a document’s content stream. Valid values are:

none: The content stream may never be updated.

anytime: The content stream may be updated any time. pwconly: The content stream may be updated only when checked out. The abbreviation

PWC is described in section .See Section: 2.1.4.1 Content Stream

capabilityChanges (enumCapabilityChanges)

Indicates what level of changes (if any) the repository exposes via the “change log” service. Valid values are:

none: The repository does not support the change log feature.

objectidsonly: The change log can return only the ObjectIDs for changed objects in the repository and an indication of the type of change, not details of the actual change.

properties: The change log can return properties and the ObjectID for the changed objects

all: The change log can return the ObjectIDs for changed objects in the repository and more information about the actual change

See Section: 2.1.11 Change Log

capabilityRenditions (enumCapabilityRendition) Indicates whether or not the repository exposes renditions of document or folder objects.

none: The repository does not expose renditions at all.

read: Renditions are provided by the repository and readable by the client.

Filing Capabilities:capabilityMultifiling

Ability for an application to file a document or other file-able object in more than one folderSee Section: 2.1.5 Folder Object

capabilityUnfilingAbility for an application to leave a document or other file-able object not filed in any folderSee Section: 2.1.5 Folder Object

capabilityVersionSpecificFilingAbility for an application to file individual versions (i.e., not all versions) of a document in a folderSee Section:

Versioning Capabilities:capabilityPWCUpdatable

Ability for an application to update the “Private Working Copy” of a checked-out documentcmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 12 of 240

462463464465466467468469470

471472473474475476477478479480481482

483484485486487488489490

491492

493494

495496

497498

499500

501502503

504343536

Page 13: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

See Section:

capabilityPWCSearchableAbility of the Repository to include the "Private Working Copy" of checked-out documents in query search scope; otherwise PWC's are not searchableSee Section:

capabilityAllVersionsSearchableAbility of the Repository to include non-latestall versions of document in query search scope; otherwise only.If False, typically either the latest or the latest major version of each document iswill be searchable.See Section:

Query Capabilities:capabilityQuery (enumCapabilityQuery)

Indicates the types of queries that the Repository has the ability to fulfill. Query support levels are: none: No queries of any kind can be fulfilled.

metadataonly: Only queries that filter based on object properties can be fulfilled. Specifically, the CONTAINS() predicate function is not supported.

fulltextonly: Only queries that filter based on the full-text content of documents can be fulfilled. Specifically, only the CONTAINS() predicate function can be included in the WHERE clause.

bothseparate: The repository can fulfill queries that filter EITHER on the full-text content of documents OR on their properties, but NOT if both types of filters are included in the same query.

bothcombined: The repository can fulfill queries that filter on both the full-text content of documents and their properties in the same query.

See Section: 2.1.10 Query

capabilityJoin (enumCapabilityJoin)

Indicates the types of JOIN keywords that the Repository can fulfill in queries. Support levels are: none: The repository cannot fulfill any queries that include any JOIN clauses.

inneronly: The repository can fulfill queries that include an INNER JOIN clause, but cannot fulfill queries that include other types of JOIN clauses.

innerandouter: The repository can fulfill queries that include any type of JOIN clause defined by the CMIS query grammar.

See Section: 2.1.10 Query

ACL Capabilities:capabilityACL (enumCapabilityACL)

Indicates the level of support for ACLs by the repository none: The repository does not support ACL services

discover: The repository supports discovery of ACLs (getACL and other services)

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 13 of 240

505

506507

508509510

511512

513514515516

517518519520521522523524525526527528529530531532

533534535536537538539540541

542543544

545546547

373839

Page 14: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

manage: The repository supports discovery of ACLs AND applying ACLs (getACL and applyACL services)

See Section: 2.8 Access Control

2.1.1.2 Implementation InformationThe “Get Repository Information” service MUST also return implementation information including vendor name, product name, product version, version of CMIS that it supports, the root folder ID (see section 2.1.5.2 Folder Hierarchy), and MAY include other implementation-specific information. The version of CMIS that the repository supports MUST be expressed as a Decimal that matches the specification version.

2.1.2 Object

The entities managed by CMIS are modeled as typed Objects. There are four base types of objects: Document Objects, Folder Objects, Relationship Objects, and Policy Objects.

A document object represents a standalone information asset. Document objects are the elementary entities managed by a CMIS repository.

A folder object represents a logical container for a collection of “file-able” objects, which include folder objects and document objects. Folder objects are used to organize file-able objects. Whether or not an object is file-able is specified in its object-type definition.

A relationship object represents an instance of directional relationship between two objects. The support for relationship objects is optional, and may be discovered via the “Get Type Children” service.

A policy object represents an administrative policy, which may be “applied” to one or more “controllablePolicy” objects. Whether or not an object is controllable is specified in its object-type definition. The support for policy objects is optional, and may be discovered via the “Get Type Children” service.

Additional object-types MAY be defined in a repository as subtypes of these base types. CMIS services are provided for the discovery of object-types that are defined in a repository. However, object-type management services, such as the creation, modification, and deletion of an object-type, are outside the scope of CMIS.

Every CMIS object has an opaque and immutable Object Identity (ID), which is assigned by the repository when the object is created. An ID uniquely identifies an object within a repository regardless of the type of the object. Repositories SHOULD assign IDs that are “permanent” – that is, they remain unchanged during the lifespan of the identified objects, and they are never reused or reassigned after the objects are deleted from the repository.

Every CMIS object has a set of named, but not explicitly ordered, Properties. (However, a Repository SHOULD always return object properties in a consistent order.) Within an object, each property is uniquely identified by its property definition id.

In addition, a document object MAY have a Content-Stream, which may be used to hold a raw digital asset such as an image or a word-processing document. A repository MUST specify, in each object-type definition, whether document objects of that type MAY, MUST, or MUST NOT have a content-stream. A document MAY also have one or more Renditions associated with it. A rendition can be a thumbnail or an alternate representation of the content stream.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 14 of 240

548549550

551552553554555556

557

558559

560561562563564565566567568569570571

572573574575

576577578579580

581582583

584585586587588

404142

Page 15: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Document or folder objects MAY have one Access Control List (ACL), which controls access to the document or folder. A policy object may also control access to the document or folder. An ACL represents a list of Access Control Entries (ACEs). An ACE in turn represents one or more permissions being granted to a principal (a user, group, role, or something similar).

The notion of localization of the objects in the data model is entirely repository specific.

2.1.2.1 Property

A property MAY hold zero, one, or more typed data value(s). Each property MAY be single-valued or multi-valued. A single-valued property contains a single data value, whereas a multi-valued property contains an ordered list of data values of the same type. The ordering of values in a multi-valued property MAY be preserved by the repository.

If a value is not provided for a property, the property is in a “value not set” state. There is no “null” value for a property. Through protocol binding, a property is either not set, or is set to a particular value or a list of values.

A multi-valued property is either set or not set in its entirety. An individual value of a multi-valued property MUST NOT be in an individual “value not set” state and hold a position in the list of values. An empty list of values MUST NOT be allowed.

Every property is typed. The Property-type defines the data type of the data value(s) held by the property. CMIS specifies the following Property-types. They include the following data types defined by “XML Schema Part 2: Datatypes Second Edition” (W3C Recommendation, 28 October 2004, http://www.w3.org/TR/xmlschema-2/):

string (xsd:string) boolean (xsd:boolean) decimal (see section 2.1.3.3.5 Attributes specific to Decimal Object-Type Property Definitions) integer (xsd:integer) datetime (xsd:dateTime and see section 2.1.3.3.5 Attributes specific to Decimal Object-Type

Property Definitions) uri (xsd:anyURI)

In addition, the following Property-Types are also specified by CMIS: id html

Individual protocol bindings MAY override or re-specify these property types.

All properties MUST supply a String queryName attribute which is used for query and filter operations on object-types. This is an opaque String with limitations. This string SHOULD NOT contain any characters that negatively interact with the BNF grammar.

The string MUST NOT contain: whitespace “ “, comma “,” double quotes ‘”’ single quotes “’” backslash “\”

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 15 of 240

589590591592

593

594

595596597598

599600601

602603604

605606607608609610611612613614615616617618619620621

622623624625

626627628629630631632

434445

Page 16: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

the period “.” character or, the open “(“ or close “)” parenthesis characters.

2.1.2.1.1 ID Property

An ID property holds a system-generated, read-only identifier, such as an Object ID, an Object-Type ID, etc. (The ID Property-Type is NOT defined by xsd:id.) The lexical representation of an ID is an opaque string. As such, an ID cannot be assumed to be interpretable syntactically or assumed to be to be collate-able with other IDs, and can only be used in its entirety as a single atomic value. When used in a query predicate, an ID can only participate in an “equal” or a “not equal” comparison with a string literal or with another ID.

While all CMIS identities share the same Property-Type, they do not necessarily share the same address space. Unless explicitly specified, ID properties NEED NOT maintain a referential integrity constraint. Therefore, storing the ID of one object in another object NEED NOT constrain the behavior of either object. A repository MAY, however, support referential constraint underneath CMIS if the effect on CMIS services remains consistent with an allowable behavior of the CMIS model. For example, a repository MAY return an exception when a CMIS service call violates an underlying referential constraint maintained by the repository. In that case, an error message SHOULD be returned to the application to describe the cause of exception and suggest a remedial action. The content of such messages is outside the scope of CMIS.

2.1.2.1.2 HTML PropertyAn HTML property holds a document or fragment of Hypertext Markup Language (HTML) content. HTML properties are not guaranteed to be validated in any way. The validation behavior is entirely repository specific.

2.1.3 Object-Type

An Object-Type defines a fixed and non-hierarchical set of properties (“schema”) that all objects of that type have. This schema is used by a repository to validate objects and enforce constraints, and is also used by a user to compose object-type-based (structured) queries.

All CMIS objects are strongly typed. If a property not specified in an object’s object-type definition is supplied by an application, an exception SHOULD be thrown.

Each object-type is uniquely identified within a repository by a system-assigned and immutable Object-Type Identifier, which is of type ID.

A CMIS repository MUST expose exactly one collection of Object-Types via the “Repository” services (getTypeChildren, getTypeDescendants, getTypeDefinition).

While a repository MAY define additional object-types beyond the CMIS Base Object-Types, these Object-Types MUST NOT extend or alter the behavior or semantics of a CMIS service (for example, by adding new services). A repository MAY attach additional constraints to an object-type underneath CMIS, provided that the effect visible through the CMIS interface is consistent with the allowable behavior of CMIS.

2.1.3.1 Object-Type Hierarchy and Inheritance

Hierarchy and Inheritance for Object-Types are supported by CMIS in the following manner:

A CMIS repository MUST have these base types:

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 16 of 240

633634

635

636

637638639640641642

643644645646647648649650651

652653654655

656

657658659

660661

662663

664665

666667668669670

671

672

673

464748

Page 17: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

o cmis:document object-type

o cmis:folder object-type

A CMIS repository MAY have these base types:

o cmis:relationship object-type

o cmis:policy object-type

Additional base types MUST NOT exist. Additional object-types MAY be defined as sub-types or descendant types of these four base types.

A Base Type does not have a parent type.

A non-base type has one and only one parent type. An object-type’s Parent Type is a part of the object-type definition.

An object-type definition includes a set of object-type attributes (e.g. Fileable, Queryable, etc.) and a property schema that will apply to Objects of that type.

o There is no inheritance of object-type attributes from a parent object-type to its sub-types.

The properties of a CMIS base type MUST be inherited by its descendant types.

A Child Type whose immediate parent is NOT its base type SHOULD inherit all the property definitions that are specified for its parent type. In addition, it MAY have its own property definitions.

o If a property is NOT inherited by a subtype, the exhibited behavior for query MUST be as if the value of this property is “not set” for all objects of this sub-type.

The scope of a query on a given object-type is automatically expanded to include all the Descendant Types of the given object-type with the attribute includedInSuperTypeQuery equals TRUE. This was added for synthetic types as well as to support different type hierarchies that are not necessarily the same as CMIS. Only the properties of the given object-type, including inherited ones, MUST be used in the query. Properties defined for its descendant types MAY NOT be used in the query, and CAN NOT be returned by the query.

o If a property of its parent type is not inherited by this type, the property MUST still appear as a column in the corresponding virtual table in the relational view, but this column MUST contain a NULL value for all objects of this type. (See section 2.1.10 Query.)

2.1.3.2 Object-Type Attributes

2.1.3.2.1 Attributes common to ALL Object-Type Definitions

All Object-Type Definitions MUST contain the following attributes:id ID

This opaque attribute uniquely identifies this object-type in the repository.

localName String (optional)

This attribute represents the underlying repository’s name for the object-type. This field is opaque and has no uniqueness constraint imposed by this specification.Two properties with the same localName and localNamespace MUST have the same semantic equality.

localNamespace String (optional)

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 17 of 240

674675676

677678679680

681

682683

684685

686687

688689690

691692

693694695696697698

699700701

702

703

704705706

707708709710711712

713714

495051

Page 18: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

This attribute allows repositories to represent the internal namespace of the underlying repository’s name for the object-type.

queryName String

Used for query and filter operations on object-types. This is an opaque String with limitations. This string SHOULD NOT contain any characters that negatively interact with the BNF grammar.

The string MUST NOT contain: whitespace “ “, comma “,” double quotes ‘”’ single quotes “’” backslash “\” the period “.” character or, the open “(“ or close “)” parenthesis characters.

displayName String (optional)

Used for presentation by application.

baseId Enum

A value that indicates whether the base type for this Object-Type is the Document, Folder, Relationship, or Policy base type.

parentId ID

The ID of the Object-Type’s immediate parent type. It MUST be “not set” for a base type.

description String (optional)

Description of this object-type, such as the nature of content, or its intended use. Used for presentation by application.

creatable Boolean

Indicates whether new objects of this type MAY be created. If the value of this attribute is FALSE, the repository MAY contain objects of this type already, but MUST NOT allow new objects of this type to be created.

fileable Boolean

Indicates whether or not objects of this type are file-able.

queryable Boolean

Indicates whether or not this object-type can appear in the FROM clause of a query statement. A non-queryable object-type is not visible through the relational view that is used for query, and CAN NOT appear in the FROM clause of a query statement.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 18 of 240

715716

717718719720

721722723724725726727728729

730731732

733734735736

737738739740

741742743744

745746747748749

750751752

753754755756757

525354

Page 19: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

controllablePolicy Boolean

Indicates whether or not objects of this type are controllable via policies. Policy objects can only be applied to controllablePolicy objects.

controllableACL Boolean

This attribute indicates whether or not objects of this type are controllable by ACL’s. Only objects that are controllableACL can have an ACL.

fulltextIndexed Boolean

Indicates whether objects of this type are indexed for full-text search for querying via the CONTAINS() query predicate.

includedInSupertypeQuery Boolean

Indicates whether this type and its subtypes appear in a query of this type’s ancestor types.

For example: if Invoice is a sub-type of cmis:document, if this is TRUE on Invoice then for a query on cmis:document, instances of Invoice will be returned if they match. If this attribute is FALSE, no instances of Invoice will be returned even if they match the query.

2.1.3.3 Object-Type Property Definitions

Besides these object-type attributes, an object-type definition SHOULD contain inherited property definitions and zero or more additional property definitions. All the properties of an object, including inherited properties, MUST be retrievable through the “get” services, and MAY appear in the SELECT clause of a query.

2.1.3.3.1 Property TypesProperty types are defined in section 2.1.2.1 Property.

2.1.3.3.2 Attributes common to ALL Object-Type Property Definitions

All Object-Type Property Definitions MUST contain the following attributes:id ID

This opaque attribute uniquely identifies the property in the repository. If two Object-Types each contain property definitions with the same ID, those property definitions are the same.

localName String (optional)

This attribute represents the underlying repository’s name for the property. This field is opaque and has no uniqueness constraint imposed by this specification.

localNamespace String (optional)

This attribute allows repositories to represent the internal namespace of the underlying repository’s name for the property.

queryName String

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 19 of 240

758759760761

762763764765

766767768769

770771772

773774775

776

777778779780

781782

783

784785786787

788789790791

792793794795

796797

555657

Page 20: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Used for query operations on properties. This is an opaque String with limitations. Please see queryName in Object-Type Attributes for the limitations on what characters are not allowed.

displayName String (optional)

Used for presentation by application.

description String (optional)

This is an optional attribute containing a description of the property

propertyType Enum

This attribute indicates the type of this property. It MUST be one of the allowed property types. (See section 2.1.2.1 Property.)

cardinality Enum

Indicates whether the property can have “zero or one” or “zero or more” values.Values:

single: Property can have zero or one values (if property is not required), or exactly one value (if property is required)

multi: Property can have zero or more values (if property is not required), or one or more values (if property is required).

Repositories SHOULD preserve the ordering of values in a multi-valued property. That is, the order in which the values of a multi-valued property are returned in get operations SHOULD be the same as the order in which they were supplied during previous create/update operation.

updatability Enum

Indicates under what circumstances the value of this property MAY be updated. Values:

readonly: The value of this property MUST NOT ever be set directly by an application. It is a system property that is either maintained or computed by the repository. o The value of a readOnly property MAY be indirectly modified by other repository

interactions (for example, calling “updateProperties” on an object will change the object’s last modified date, even though that property cannot be directly set via an updateProperties() service call.)

readwrite: The property value can be modified using the updateProperties service.

whencheckedout: The property value MUST only be update-able using a “private working copy” Document.o I.e. the update is either made on a “private working copy” object or made using a

“check in” service. oncreate: The property value MUST only be update-able during the Create operation on

that Object.

inherited Boolean

Indicates whether the property definition is inherited from the parent-type when TRUE or it is explicitly defined for this object-type when FALSE.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 20 of 240

798799800801802

803804805

806807808809

810811812813814815816817818819820

821822823824825826827828829830831832833834835836837

838839840841

585960

Page 21: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

required Boolean

If TRUE, then the value of this property MUST never be set to the “not set” state when an object of this type is created/updated. If not provided during a create or update operation, the repository MUST provide a value for this property.If a value is not provided, then the default value defined for the property MUST be set. If no default value is provided and no default value is defined, the repository MUST throw an exception.A property definition SHOULD never state that a property has a “required” value of TRUE and an updatability value of “readonly”.

queryable Boolean

Indicates whether or not the property MAY appear in the WHERE clause of a CMIS query statement. This attribute MUST have a value of FALSE if the Object-type’s attribute for “Queryable” is set to FALSE.

orderable Boolean

Indicates whether the property can appear in the ORDER BY clause of a CMIS query statement or an ORDERBY parameter. This property MUST be FALSE for any property whose cardinality is “multi”.

choices <PropertyChoiceType list> (multi-valued)

Indicates an explicit ordered set of single values allowed for this property. If the cardinatity of the property definition is “single” and the “openChoice” attribute is FALSE, then the property value MUST be at most one of the values listed in this attribute. If the cardinatity of the property definition is “single” and the “openChoice” attribute is TRUE, then the property value MAY be one of the values listed in this attribute.If the cardinatity of the property definition is “multi” and the “openChoice” attribute is FALSE, then the property value MUST be zero, one or more than one of the values listed in this attribute. If the cardinatity of the property definition is “multi” and the “openChoice” attribute is TRUE, then the property value MAY be zero, one, or more than one of the values listed in this attribute.If this attribute is “not set”, then any valid value for this property based on its type may be used.

Each choice includes a displayName and a value. The displayName is used for presentation purpose. The value will be stored in the property when selected. Choices MAY be hierarchically presented. For example: a value of “choices” for a geographic location would be represented as follows:

o Europe:

England France Germany

o North America

Canada USA Mexico

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 21 of 240

842843844845846847848849850851

852853854855856857

858859860861862

863864865866867868869870871872873874

875876877878879880881882883884885886

616263

Page 22: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

openChoice Boolean

This attribute is only applicable to properties that provide a value for the “Choices” attribute. If FALSE, then the data value for the property MUST only be one of the values specified in the “Choices” attribute. If TRUE, then values other than those included in the “Choices” attribute may be set for the property.

defaultValue <PropertyType>

The value that the repository MUST set for the property if a value is not provided by an application when the object is created. If no default value is specified and an application creates an object of this type without setting a value for the property, the repository MUST attempt to store a “value not set” state for the property value. If this occurs for a property that is defined to be required, then the creation attempt MUST throw an exception.The attributes on the default value element are the same as the attributes on the property definition.

2.1.3.3.3 Attributes specific to Integer Object-Type Property DefinitionsThe following Object attributes MUST only apply to Property-Type definitions whose propertyType is “Integer”, in addition to the common attributes specified above. A repository MAY provide additional guidance on what values can be accepted. If the following attributes are not present the repository behavior is undefined and it MAY throw an exception if a runtime constraint is encountered.

minValue Integer

The minimum value allowed for this property.If an application tries to set the value of this property to a value lower than minValue, the repository MUST throw a constraint exception.

maxValue Integer

The maximum value allowed for this property.If an application tries to set the value of this property to a value higher than maxValue, the repository MUST throw a constraint exception.

2.1.3.3.4 Attributes specific to DateTime Object-Type Property DefinitionsThe following Object attributes MUST only apply to Property-Type definitions whose propertyType is “Decimal”, in addition to the common attributes specified above. A repository MAY provide additional guidance on what values can be accepted. If the following attributes are not present the repository behavior is undefined and it MAY throw an exception if a runtime constraint is encountered.

resolution String Enumeration

This is the precision in bits supported for values of this property. Valid values for this attribute are: Year: Year resolution is persisted Date: Date resolution is persisted Time: Time resolution is persisted

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 22 of 240

887888889890891

892893

894895896897898899900901

902903904905906907908909910911912913914915916

917918919920921922923924925926

927

646566

Page 23: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

2.1.3.3.5 Attributes specific to Decimal Object-Type Property DefinitionsThe following Object attributes MUST only apply to Property-Type definitions whose propertyType is “Decimal”, in addition to the common attributes specified above. A repository MAY provide additional guidance on what values can be accepted. If the following attributes are not present the repository behavior is undefined and it MAY throw an exception if a runtime constraint is encountered.

precision Integer Enumeration

This is the precision in bits supported for values of this property. Valid values for this attribute are: 32: 32-bit precision (“single” as specified in IEEE-754-1985). 64: 64-bit precision (“double” as specified in IEEE-754-1985.)

minValue Decimal

The minimum value allowed for this property.If an application tries to set the value of this property to a value lower than minValue, the repository MUST throw a constraint exception.

maxValue Decimal

The maximum value allowed for this property.If an application tries to set the value of this property to a value higher than maxValue, the repository MUST throw a constraint exception.

2.1.3.3.6 Attributes specific to String Object-Type Property DefinitionsThe following Object attributes MUST only apply to Property-Type definitions whose propertyType is “String”, in addition to the common attributes specified above. A repository MAY provide additional guidance on what values can be accepted. If the following attributes are not present the repository behavior is undefined and it MAY throw an exception if a runtime constraint is encountered.

maxLength Integer

The maximum length (in characters) allowed for a value of this property.If an application attempts to set the value of this property to a string larger than the specified maximum length, the repository MUST throw a constraint exception.

2.1.4 Document Object

Document objects are the elementary information entities managed by the repository.

Depending on its Object-type definition, a Document Object may be:

Version-able: Can be acted upon via the Versioning Services (for example: checkOut, checkIn).

File-able: Can be filed in zero, one, or more than one folder via the Multi-filing services.

Query-able: Can be located via the Discovery Services (query).

Controllable-Policy: Can have Policies applied to it (see section 2.1.7 Policy Object.)

Controllable-ACL: Can have an ACL applied to it (see section 2.8 Access Control)

Additionally, whether a Document object MUST, MAY or MUST NOT have a content-stream is specified in its object-type definition. A Document Object MAY be associated with zero or more renditions.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 23 of 240

928929930931932933934935936

937938939940941942943944945946

947948949950951952953954955

956

957

958

959

960

961

962

963

964965

676869

Page 24: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Note: When a document is versioned, each version of the document is a separate document object. Thus, for document objects, an object ID actually identifies a specific version of a document.

2.1.4.1 Content Stream

A content-stream is a binary stream. Its maximum length is repository-specific. Each content-stream has a MIME Media Type, as defined by RFC2045 and RFC2046. A content-stream’s attributes are represented as properties of the content-stream’s containing document object. There is no MIME-type-specific attribute or name directly associated with the content-stream outside of the document object.

CMIS provides basic CRUD services for content-stream, using the ID of a content-stream’s containing document object for identification. A content stream also has a streamId which is used for access to the stream. The “Set Content-Stream” service (setContentStream) either creates a new content-stream for a document object or replaces an existing content-stream. The “Get Content-Stream” service (getContentStream) retrieves a content-stream. The “Delete Content-Stream” service (deleteContentStream) deletes a content-stream from a document object. In addition, the “CreateDocument” and “Check-in” services MAY also take a content-stream as an optional input. A content stream MUST be specified if required by the type definition. These are the only services that operate on content-stream. The “Get Properties” and “Query” services, for example, do not return a content-stream.

“Set Content-Stream” and “Delete Content-Stream” services are considered modifications to a content-stream’s containing document object, and SHOULD therefore change the object’s LastModificationDate property upon successful completion.

The ability to set or delete a content stream is controlled by the capabilityContentStreamUpdatability capability.

2.1.4.2 RenditionsSome ECM repositories provide a facility to retrieve alternative representations of a document. These alternative representations are known as renditions. This could apply to a preview case which would enable the client to preview the content of a document without needing to download the full content. Previews are generally reduced fidelity representations such as thumbnails. Renditions can take on any general form, such as a PDF version of a word document.A CMIS repository MAY expose zero or more renditions for a document or folder in addition to a document’s content stream. CMIS provides no capability to create or update renditions accessed through the rendition services. Renditions are specific to the version of the document or folder and may differ between document versions. Each rendition consists of a set of rendition attributes and a rendition stream. Rendition attributes are not object properties, and are not queryable. They can be retrieved using the getRenditions service. A rendition stream can be retrieved using the getContentStream service with the rendition’s streamId parameter.

2.1.4.2.1 Rendition AttributesA rendition has the following attributes:

streamId ID

Identifies the rendition stream.

mimeType String

The MIME type of the rendition stream.

length Integer (optional)

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 24 of 240

966967

968

969970971972

973974975976977978979980981982

983984985

986987

9889899909919929939949959969979989991000

1001100210031004

100510061007

10081009

707172

Page 25: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

The length of the rendition stream in bytes.

title String (optional)

Human readable information about the rendition.

kind String

A categorization String associated with the rendition.

height Integer (optional)

Typically used for ‘image’ renditions (expressed as pixels). SHOULD be present if kind = cmis:thumbnail.

width Integer (optional)

Typically used for ‘image’ renditions (expressed as pixels). SHOULD be present if kind = cmis:thumbnail.

renditionDocumentId ID (optional)

If specified, then the rendition can also be accessed as a document object in the CMIS services. If not set, then the rendition can only be accessed via the rendition services. Referential integrity of this ID is repository-specific.

2.1.4.2.2 Rendition KindA Rendition may be categorized via its kind. The repository is responsible for assigning kinds to Renditions, including custom kinds. A repository kind does not necessarily identify a single Rendition for a given Object.CMIS defines the following kind:

cmis:thumbnail : A rendition whose purpose is to a provide an image preview of the document without requiring the client to download the full document content stream. Thumbnails are generally reduced fidelity representations.

2.1.4.3 Document Object-Type DefinitionThis section describes the definition of the Document Object-Type’s attribute values and property definitions which must be present on Document instance objects. All attributes and property definitions are listed by their ID.

2.1.4.3.1 Attributes specific to Document Object-TypesThe following Object attributes MUST only apply to Object-Type definitions whose baseId is the cmis:document Object-Type, in addition to the common attributes specified above:

versionable Boolean

Indicates whether or not objects of this type are version-able. (See section .)

contentStreamAllowed Enum

A value that indicates whether a content-stream MAY, MUST, or MUST NOT be included in objects of this type. Values:

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 25 of 240

1010

101110121013

101410151016

10171018101910201021102210231024

10251026102710281029

10301031103210331034

103510361037

1038103910401041

10421043104410451046

1047104810491050

737475

Page 26: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

notallowed: A content-stream MUST NOT be included

allowed: A content-stream MAY be included

required: A content-stream MUST be included (i.e. MUST be included when the object is created, and MUST NOT be deleted.)

2.1.4.3.2 Attribute ValuesThe Document Object-Type MUST have the following attribute values.Notes:

A value of <repository-specific> indicates that the value of the property MAY be set to any valid value for the attribute type.

Unless explicitly stated otherwise, all values specified in the list MUST be followed for the Object-Type definition.

idValue: cmis:document

localNameValue: <repository-specific>

localNamespaceValue: <repository-specific>

queryNameValue: cmis:document

displayNameValue: <repository-specific>

baseIdValue: cmis:document

parentIdValue: Not set

descriptionValue: <repository-specific>

creatableValue: <repository-specific>

fileableValue: TRUE

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 26 of 240

1051105210531054

1055105610571058105910601061

10621063

1064

10651066

1067

10681069

1070

10711072

1073

10741075

1076

10771078

1079

10801081

1082

10831084

1085

10861087

1088

10891090

1091

767778

Page 27: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

queryableValue: SHOULD be TRUE

controllablePolicyValue: <repository-specific>

includedInSupertypeQueryValue: <repository-specific>

versionableValue: <repository-specific>

contentStreamAllowedValue: <repository-specific>

controllableACLValue: <repository-specific>

fulltextIndexedValue: <repository-specific>

2.1.4.3.3 Property DefinitionsThe Document base Object-Type MUST have the following property definitions, and MAY include additional property definitions. Any attributes not specified for the property definition are repository specific. For all property definitions on base types, the query name MUST be the same as the property ID. The repository MUST have the following property definitions on the Document Type:

cmis:name Name of the objectInherited: FalseProperty Type: StringCardinality: Single

cmis:objectId Id of the objectRequired: FalseInherited: FalseProperty Type: IDCardinality: SingleUpdatability: Read OnlyChoices: Not ApplicableOpen Choice: Not ApplicableMUST be set on the object

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 27 of 240

10921093

1094

10951096

1097

1099

1100

11011102

1103

11041105

1106

11071108

1109

11101111

1112

11131114111511161117

11181119112011211122

1123112411251126112711281129113011311132

1133

798081

Page 28: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

cmis:baseTypeId Id of the base object-type for the objectRequired: FalseInherited: FalseProperty Type: IDCardinality: SingleUpdatability: Read OnlyChoices: Not ApplicableOpen Choice: Not ApplicableMUST be set on the object

cmis:objectTypeId Id of the object’s typeRequired: TrueInherited: FalseProperty Type: IDCardinality: SingleUpdatability: oncreateChoices: Not ApplicableOpen Choice: Not ApplicableMUST be set on the object

cmis:createdBy User who created the object.Required: FalseInherited: FalseProperty Type: StringCardinality: SingleUpdatability: Read OnlyChoices: Not ApplicableOpen Choice: Not ApplicableQueryable: TrueOrderable: TrueMUST be set on the object

cmis:creationDate DateTime when the object was created.Required: FalseInherited: FalseProperty Type: DateTimeCardinality: SingleUpdatability: Read OnlyChoices: Not ApplicableOpen Choice: Not ApplicableQueryable: TrueOrderable: True

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 28 of 240

113411351136113711381139114011411142

1143114411451146114711481149115011511152

115311541155115611571158115911601161116211631164

11651166116711681169117011711172117311741175

828384

Page 29: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

MUST be set on the object

cmis:lastModifiedBy User who last modified the object.Required: FalseInherited: FalseProperty Type: StringCardinality: SingleUpdatability: Read OnlyChoices: Not ApplicableOpen Choice: Not ApplicableQueryable: TrueOrderable: TrueMUST be set on the object

cmis:lastModificationDate DateTime when the object was last modified.Required: FalseInherited: FalseProperty Type: DateTimeCardinality: SingleUpdatability: Read OnlyChoices: Not ApplicableOpen Choice: Not ApplicableQueryable: TrueOrderable: TrueMUST be set on the object

cmis:changeToken Opaque token used for optimistic locking & concurrency checking. (see section 2.2.1.3 Change Tokens)

Required: FalseInherited: FalseProperty Type: StringCardinality: SingleUpdatability: Read OnlyChoices: Not ApplicableOpen Choice: Not ApplicableMUST be set on the object

cmis:isImmutable TRUE if the repository MUST throw an error at any attempt to update or delete the object.

Required: FalseInherited: FalseProperty Type: Boolean

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 29 of 240

1176

117711781179118011811182118311841185118611871188

118911901191119211931194119511961197119811991200

12011202120312041205120612071208120912101211

121212131214121512161217

858687

Page 30: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Cardinality: SingleUpdatability: Read OnlyChoices: Not ApplicableOpen Choice: Not ApplicableMUST be set on the object

cmis:isLatestVersion See section .Required: FalseInherited: FalseProperty Type: BooleanCardinality: SingleUpdatability: Read OnlyChoices: Not ApplicableOpen Choice: Not ApplicableMUST be set on the object. Version Property Values are repository-specific when a document is defined as non-versionable.

cmis:isMajorVersion See section .Required: FalseInherited: FalseProperty Type: BooleanCardinality: SingleUpdatability: Read OnlyChoices: Not ApplicableOpen Choice: Not ApplicableMUST be set on the object. Version Property Values are repository-specific when a document is defined as non-versionable.

cmis:isLatestMajorVersion See section .Required: FalseInherited: FalseProperty Type: BooleanCardinality: SingleUpdatability: Read OnlyChoices: Not ApplicableOpen Choice: Not ApplicableMUST be set on the object. Version Property Values are repository-specific when a document is defined as non-versionable.

cmis:versionLabel See section .Required: FalseInherited: False

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 30 of 240

12181219122012211222

12231224122512261227122812291230123112321233

12341235123612371238123912401241124212431244

12451246124712481249125012511252125312541255

1256125712581259

888990

Page 31: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Property Type: StringUpdatability: Read OnlyChoices: Not ApplicableOpen Choice: Not ApplicableMUST be set on the object. Version Property Values are repository-specific when a document is defined as non-versionable.

cmis:versionSeriesId See section .Required: FalseInherited: FalseProperty Type: IDCardinality: SingleUpdatability: Read OnlyChoices: Not ApplicableOpen Choice: Not ApplicableMUST be set on the object. Version Property Values are repository-specific when a document is defined as non-versionable.

cmis:isVersionSeriesCheckedOut See section .Required: FalseInherited: FalseProperty Type: BooleanCardinality: SingleUpdatability: Read OnlyChoices: Not ApplicableOpen Choice: Not ApplicableMUST be set on the object. Version Property Values are repository-specific when a document is defined as non-versionable.

cmis:versionSeriesCheckedOutBy See section .Required: FalseInherited: FalseProperty Type: StringCardinality: SingleUpdatability: Read OnlyChoices: Not ApplicableOpen Choice: Not Applicable

Version Property Values are repository-specific when a document is defined as non-versionable.

cmis:versionSeriesCheckedOutId See section .Required: FalseInherited: False

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 31 of 240

126012611262126312641265

12661267126812691270127112721273127412751276

12771278127912801281128212831284128512861287

1288128912901291129212931294129512961297

1298129913001301

919293

Page 32: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Property Type: IDCardinality: SingleUpdatability: Read OnlyChoices: Not ApplicableOpen Choice: Not Applicable

Version Property Values are repository-specific when a document is defined as non-versionable.

cmis:checkinComment See section .Required: FalseInherited: FalseProperty Type: StringCardinality: SingleUpdatability: Read OnlyChoices: Not ApplicableOpen Choice: Not Applicable

Version Property Values are repository-specific when a document is defined as non-versionable.

cmis:contentStreamLength Length of the content stream (in bytes).Required: False Inherited: FalseProperty Type: IntegerCardinality: SingleUpdatability: Read OnlyChoices: Not ApplicableOpen Choice: Not ApplicableMUST be set if the document has a content stream

cmis:contentStreamMimeType MIME type of the Content StreamRequired: FalseInherited: FalseProperty Type: StringCardinality: SingleUpdatability: Read OnlyChoices: Not ApplicableOpen Choice: Not ApplicableMUST be set if the document has a content stream

cmis:contentStreamFileName File name of the Content StreamRequired: FalseInherited: FalseProperty Type: StringCardinality: Single

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 32 of 240

130213031304130513061307

1308130913101311131213131314131513161317

1318131913201321132213231324132513261327

1328132913301331133213331334133513361337

133813391340134113421343

949596

Page 33: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

MUST be set if the document has a content stream

cmis:contentStreamId Id of the streamRequired: FalseInherited: FalseProperty Type: IDCardinality: SingleUpdatability: Read OnlyChoices: Not ApplicableOpen Choice: Not Applicable

2.1.5 Folder Object

A folder object serves as the anchor for a collection of file-able objects. The folder object has an implicit hierarchical relationship with each object in its collection, with the anchor folder object being the Parent object and each object in the collection being a Child object. This implicit relationship has specific containment semantics which MUST be maintained by the repository with implicit referential integrity. (That is, there will never be a dangling parent-relationship or a dangling child-relationship. Furthermore, object A is a parent of object B if and only if object B is a child of object A.) This system-maintained implicit relationship is distinct from an explicit relationship which is instantiated by an application-maintained Relationship Object. (See section 2.1.6 Relationship Object.)

A folder object does not have a content-stream and is not version-able. A folder object MAY be associated with zero or more renditions (see section 2.1.4.2 Renditions).

2.1.5.1 File-able Objects

A file-able object is one that MAY be “filed” into a folder. That is, it MAY be a child object of a folder object. The following list defines whether the base CMIS Object-types are file-able:

cmis:folderMUST be file-able

cmis:documentMUST be file-able

cmis:relationshipMUST NOT be file-able

cmis:policyMAY be file-able

2.1.5.1.1 Document Version Series and Filing

Since document objects are versionable, a document object’s membership in a folder MAY be version-specific or version-independent. That is, the folder membership MAY be restricted to that particular version of the document or MAY apply to all versions of the document. Whether or not a repository supports version-specific filing is discoverable via the “Get Repository Information” service (getRepositoryInfo).

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 33 of 240

1344

134513461347134813491350135113521353

1354

13551356135713581359136013611362

13631364

1365

1366136713681369

137013711372

137313741375

137613771378

1379

13801381138213831384

979899

Page 34: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

When the child objects of a folder are retrieved, a specific version of a document MAY be returned. If the repository supports version-specific filing, the specific version filed in that folder is returned. If the repository does not support version-specific filing, the latest version of the document is returned.

Likewise, this version sensitivity in child-binding also affects the behavior of parent retrieval for a document object, as well as the scope of the IN_FOLDER() and IN_TREE() function calls in a query. For non-versionable fileable objects, their membership in a folder does not have version sensitivity.

2.1.5.1.2 Filing Restrictions by Object-TypeA folder collection’s membership MAY be restricted by object-type. Each folder object has a multi-valued AllowedChildObjectTypeIDs property, which specifies that only objects of these types are allowed to be its children. If this property is “not set”, then objects of any file-able type MAY be filed in the Folder. It is repository-specific if subtypes of the types listed in the AllowedChildObjectTypeIDs property MAY be filed in the folder.

Because of these filing constraints, when a new folder object is created, an existing folder object MUST be specified as its parent.

When a non-file-able object is created, a parent folder MUST NOT be specified.

When a file-able object is deleted, it is removed from any folder collection in which the object is a member. In other words, when an object is deleted, all implicit parent-child relationships with the deleted object as a child cease to exist.

2.1.5.2 Folder Hierarchy

CMIS imposes the following constraints on folder objects:

Every folder object, except for one which is called the Root Folder, MUST have one and only one parent folder. The Root Folder does not have a parent.

A cycle in folder containment relationships is not allowed. That is, a folder object cannot have itself as one of its descendant objects.

A child object that is a folder object can itself be the parent object of other file-able objects.

With these constraints, the folder objects in a CMIS repository necessarily form a strict hierarchy, with the Root Folder being the root of the hierarchy.

The child objects of a given folder object, their child objects, and grandchild objects, etc., are called Descendant objects of the given folder objectA folder object together with all its descendant objects are collectively called a Tree rooted at that folder object.

A non-folder object does not have any descendant object. Thus, a Folder Graph that consists of all fileable objects as nodes, and all the implicit folder containment relationships as directed edges from parent to child, is a directed acyclic graph, possibly with some disconnected (orphan) nodes. It follows that the tree rooted at any given folder object is also a directed acyclic graph, although a non-folder object in the tree MAY have ancestors that are not ancestors of the rooted folder.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 34 of 240

138513861387

138813891390

139113921393139413951396

13971398

1399

140014011402

1403

1404

14051406140714081409

14101411

141214131414

14151416141714181419

100101102

Page 35: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Folder objects are handled using the basic CRUD services for objects, and the folder graph is traversed using the Navigation Services.

The Root Folder is a special folder such that it cannot be created, deleted, or moved using CMIS services. Otherwise, it behaves like any other folder object.

2.1.5.3 PathsA folder hierarchy MAY be represented in a canonical notation such as path. For CMIS, a path is represented by:

‘/’ for the root folder All paths start with the root folder. A set of the folder and object path segments separated by ‘/’ in order of closest to the root. Folder and object path segments are specified by pathSegment tokens which can be retrieved by

all services that take an includePathSegments parameter.

A pathSegment token MUST not include a ‘/’ character.o It is repository specific how a repository chooses the value for pathSegment.

Repositories might choose to use cmis:name or content stream filename for pathSegment token.

The pathSegment token for each item MUST uniquely identify the item in the folder.

E.g., if folder A is under the root, and folder B is under A, then the path would be /A/B.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 35 of 240

1420

14211422

14231424

1425142614271428142914301431143214331434143514361437

14381439

103104105

Page 36: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

A path for an object may be calculated by taking the item’s parent folder cmis:path property and appending the “/” character and the object’s pathSegment. This constructed path may be given as input to the getObjectByPath service for object by path retrieval.The getObjectParents service returns relativePathSegment tokens. These tokens are the pathSegment of the input object relative to the parent folders.

2.1.5.4 Folder Object-Type DefinitionThis section describes the definition of the Folder Object-Type’s attribute values and property definitions which must be present on Folder instance objects. All attributes and property definitions are listed by their ID.

2.1.5.4.1 Attribute ValuesThe Folder Object-Type MUST have the following attribute values.Notes:

A value of <repository-specific> indicates that the value of the property MAY be set to any valid value for the attribute type.

Unless explicitly stated otherwise, all values specified in the table MUST be followed for the Object-Type definition.

idValue: cmis:folder

localNameValue: <repository-specific>

localNamespaceValue: <repository-specific>

queryNameValue: cmis:folder

displayNameValue: <repository-specific>

baseIdValue: cmis:folder

parentIdValue: Not set

descriptionValue: <repository-specific>

creatable

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 36 of 240

14401441144214431444

1445144614471448

1449145014511452145314541455

14561457

1458

14591460

1461

14621463

1464

14651466

1467

14681469

1470

14711472

1473

14741475

1476

14771478

1479

14801481

106107108

Page 37: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Value: <repository-specific>

fileableValue: TRUE

queryableValue: SHOULD be TRUE

controllablePolicyValue: <repository-specific>

includedInSupertypeQueryValue: <repository-specific>

controllableACLValue: <repository-specific>

fulltextIndexedValue: <repository-specific>

2.1.5.4.2 Property DefinitionsThe Folder base Object-Type MUST have the following property definitions, and MAY include additional property definitions. Any attributes not specified for the Property Definition are repository specific. For all property definitions on base types, the query name MUST be the same as the property ID. The repository MUST have the following property definitions on the Folder Type:

cmis:name Name of the objectInherited: FalseProperty Type: StringCardinality: SingleRequired: True

cmis:objectId Id of the objectRequired: FalseInherited: FalseProperty Type: IDCardinality: SingleUpdatability: Read OnlyChoices: Not ApplicableOpen Choice: Not ApplicableMUST be set on the object

cmis:baseTypeId Id of the base object-type for the object

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 37 of 240

1482

14831484

1485

14861487

1488

14891490

1491

14921493

1494

14951496

1497

14981499

1500

1501

1502150315041505150615071508150915101511

1512151315141515151615171518151915201521

15221523

109110111

Page 38: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Required: FalseInherited: FalseProperty Type: IDCardinality: SingleUpdatability: Read OnlyChoices: Not ApplicableOpen Choice: Not ApplicableMUST be set on the object

cmis:objectTypeId Id of the object’s typeRequired: FalseInherited: FalseProperty Type: IDCardinality: SingleUpdatability: oncreateChoices: Not ApplicableOpen Choice: Not ApplicableMUST be set on the object

cmis:createdBy User who created the object.Required: FalseInherited: FalseProperty Type: StringCardinality: SingleUpdatability: Read OnlyChoices: Not ApplicableOpen Choice: Not ApplicableQueryable: TrueOrderable: TrueMUST be set on the object

cmis:creationDate DateTime when the object was created.Required: FalseInherited: FalseProperty Type: DateTimeCardinality: SingleUpdatability: Read OnlyChoices: Not ApplicableOpen Choice: Not ApplicableQueryable: TrueOrderable: TrueMUST be set on the object

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 38 of 240

15241525152615271528152915301531

1532153315341535153615371538153915401541

154215431544154515461547154815491550155115521553

155415551556155715581559156015611562156315641565

112113114

Page 39: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

cmis:lastModifiedBy User who last modified the object.Required: FalseInherited: FalseProperty Type: StringCardinality: SingleUpdatability: Read OnlyChoices: Not ApplicableOpen Choice: Not ApplicableQueryable: TrueOrderable: TrueMUST be set on the object

cmis:lastModificationDate DateTime when the object was last modified.Required: FalseInherited: FalseProperty Type: DateTimeCardinality: SingleUpdatability: Read OnlyChoices: Not ApplicableOpen Choice: Not ApplicableQueryable: TrueOrderable: TrueMUST be set on the object

cmis:changeToken Token used for optimistic locking & concurrency checking. (see section 2.2.1.3 Change Tokens)

Required: FalseInherited: FalseProperty Type: StringCardinality: SingleUpdatability: Read OnlyChoices: Not ApplicableOpen Choice: Not ApplicableMUST be set on the object

cmis:parentId ID of the parent folder of the folder.Required: FalseInherited: FalseProperty Type: IDCardinality: SingleUpdatability: Read Only

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 39 of 240

156615671568156915701571157215731574157515761577

157815791580158115821583158415851586158715881589

15901591159215931594159515961597159815991600

1601160216031604160516061607

115116117

Page 40: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Choices: Not ApplicableOpen Choice: Not ApplicableMUST be set on the object

cmis:path The fully qualified path to this folder. See section 2.1.5.3 Paths.

Required: FalseInherited: FalseProperty Type: StringCardinality: SingleUpdatability: Read OnlyChoices: Not ApplicableOpen Choice: Not ApplicableMUST be set on the object

cmis:allowedChildObjectTypeIds Id’s of the set of Object-types that can be created, moved or filed into this folder.

Required: FalseInherited: FalseProperty Type: IDCardinality: MultiUpdatability: Read OnlyChoices: Not ApplicableOpen Choice: Not Applicable

2.1.6 Relationship Object

A relationship object is semantically a dependent object. A relationship object MUST NOT have a content-stream, and MUST NOT be versionable, MUST NOTMAY be queryable, and MUST NOT be fileable, although it MAY be controllable.

If a repository does not support relationship objects, the relationship base object-type SHOULD NOT be returned by a “Get Types” service call.

A Relationship Object instantiates an explicit, binary, directional, non-invasive, and typed relationship between a Source Object and a Target Object. The source object and the target object MUST both be independent objects, such as a document object, a folder object, or a policy object. Whether a policy object is allowed to be the source or target object of a relationship object is repository-specific.

The relationship instantiated by a relationship object is explicit since it is explicitly represented by an object and is explicitly managed by application.

This relationship is non-invasive in the sense that creating or removing this relationship SHOULD NOT modify either the source or the target object. That is, it SHOULD NOT require an update capability (or permission) on either object; SHOULD NOT affect the versioning state of either object; and SHOULD NOT change their “Last Modification Date”.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 40 of 240

160816091610

16111612161316141615161616171618161916201621

1622162316241625162616271628162916301631

1632

163316341635

16361637

1638163916401641

16421643

1644164516461647

118119120

Page 41: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Explicit relationships can be used to create an arbitrary relationship graph among independent objects. Such a relationship graph is only structural in nature. No inheritance or transitive properties are attached to a relationship graph.

The notion of a source object and a target object of a relationship is used solely to indicate the direction of the relationship. No semantics or implementation bias is implied by this terminology.

The binding of a relationship object to a source document object or to a target document object MAY be either version-specific or version-independent. This version sensitivity is repository-specific, and is largely transparent to CMIS. An independent object MAY participate in any number of explicit relationships, as the source object for some and as the target object for others. Multiple relationships MAY exist between the same pair of source and target objects.

Referential integrity, either between the source object and the target object, or between the relationship object and the source or target object, is repository-specific. Therefore, creating an explicit relationship between two objects MAY impose a constraint on any of the three objects, and removing a relationship or deleting either the source or the target object MAY be restricted by such a constraint. If the source or the target object of a relationship is deleted, the repository MAY automatically delete the relationship object.

Like all CMIS objects, relationship objects are typed. Typing relationship allows them to be grouped, identified, and traversed by type id, and for properties to be defined for individual relationship types.

Additionally, a relationship object-type MAY specify that only Objects of a specific Object-Type can participate as the source object or target object for relationship objects of that type. If no such constraints are specified, then an independent object of any type MAY be the source or the target of a relationship object of that type.

When a relationship object is created, the source object ID and the target object ID MUST reference valid non-relationship CMIS objects.

When a relationship object is retrieved, its source object or target object MAY no longer exist, since referential integrity MAY not be maintained by a repository.

In addition to object CRUD services, a “Get Relationships” service (getObjectRelationships) may be used to return a set of relationship objects in which a given independent object is identified as the source or the target object, according to the binding semantics maintained by the repository (i.e., either a version-specific or a version-independent binding as described above).

2.1.6.1 Relationship Object-Type DefinitionThis section describes the definition of the Relationship Object-Type’s attribute values and property definitions which must be present on Relationship instance objects. All attributes and property definitions are listed by their ID.

2.1.6.1.1 Attributes specific to Relationship Object-TypesThe following Object attributes MUST only apply to Object-Type definitions whose baseId is the cmis:relationship Object-Type, in addition to the common attributes specified above:

allowedSourceTypes ID (multi-valued)

A list of object-type IDs, indicating that the source object of a relationship object of this type MUST only be one of the types listed. If this attribute is “not set”, then the source object MAY be of any type.

allowedTargetTypes ID (multi-valued)

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 41 of 240

164816491650

16511652

16531654165516561657

16581659166016611662

16631664

1665166616671668

16691670

16711672

1673167416751676

1677167816791680

1681168216831684168516861687

16881689

121122123

Page 42: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

A list of object-type IDs, indicating that the target object of a relationship object of this type MUST only be one of the types listed. If this attribute is “not set”, then the target object MAY be of any type.

2.1.6.1.2 Attribute ValuesThe Relationship Object-Type MUST have the following attribute values.Notes:

A value of <repository-specific> indicates that the value of the property MAY be set to any valid value for the attribute type.

Unless explicitly stated otherwise, all values specified in the table MUST be followed for the Object-Type definition.

idValue: cmis:relationship

localNameValue: <repository-specific>

localNamespaceValue: <repository-specific>

queryNameValue: cmis:relationship

displayNameValue: <repository-specific>

baseIdValue: cmis:relationship

parentIdValue: Not set

descriptionValue: <repository-specific>

creatableValue: <repository-specific>

fileableValue: FALSE

queryable

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 42 of 240

169016911692

1693169416951696169716981699

17001701

1702

17031704

1705

17061707

1708

17091710

1711

17121713

1714

17151716

1717

17181719

1720

17211722

1723

17241725

1726

17271728

1729

17301731

124125126

Page 43: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Value: <repository-specific>

includedInSupertypeQueryValue: <repository-specific>

controllablePolicyValue: <repository-specific>

allowedSourceTypesValue: <repository-specific>

allowedTargetTypesValue: <repository-specific>

controllableACLValue: <repository-specific>

fulltextIndexedValue: <repository-specific>

2.1.6.1.3 Property DefinitionsThe Relationship base Object-Type MUST have the following property definitions, and MAY include additional property definitions. Any attributes not specified by the Property Definitions are repository specific. For all property definitions on base types, the query name MUST be the same as the property ID. The repository MUST have the following property definitions on the Relationship Type:

cmis:name Name of the objectInherited: FalseProperty Type: StringCardinality: Single

cmis:objectId Id of the objectRequired: FalseInherited: FalseProperty Type: IDCardinality: SingleUpdatability: Read OnlyChoices: Not ApplicableOpen Choice: Not ApplicableMUST be set on the object

cmis:baseTypeId Id of the base object-type for the object

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 43 of 240

1732

17331734

1735

17361737

1738

17391740

1741

17421743

1744

17451746

1747

17481749

1750

1751

17521753175417551756

17571758175917601761

1762176317641765176617671768176917701771

17721773

127128129

Page 44: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Required: FalseInherited: FalseProperty Type: IDCardinality: SingleUpdatability: Read OnlyChoices: Not ApplicableOpen Choice: Not ApplicableMUST be set on the object

cmis:objectTypeId Id of the object’s typeRequired: FalseInherited: FalseProperty Type: IDCardinality: SingleUpdatability: oncreateChoices: Not ApplicableOpen Choice: Not ApplicableMUST be set on the object

cmis:createdBy User who created the object.Required: FalseInherited: FalseProperty Type: StringCardinality: SingleUpdatability: Read OnlyChoices: Not ApplicableOpen Choice: Not ApplicableMUST be set on the object

cmis:creationDate DateTime when the object was created.Required: FalseInherited: FalseProperty Type: DateTimeCardinality: SingleUpdatability: Read OnlyChoices: Not ApplicableOpen Choice: Not ApplicableMUST be set on the object

cmis:lastModifiedBy User who last modified the object.Required: FalseInherited: False

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 44 of 240

17741775177617771778177917801781

1782178317841785178617871788178917901791

1792179317941795179617971798179918001801

1802180318041805180618071808180918101811

1812181318141815

130131132

Page 45: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Property Type: StringCardinality: SingleUpdatability: Read OnlyChoices: Not ApplicableOpen Choice: Not ApplicableMUST be set on the object

cmis:lastModificationDate DateTime when the object was last modified.Required: FalseInherited: FalseProperty Type: DateTimeCardinality: SingleUpdatability: Read OnlyChoices: Not ApplicableOpen Choice: Not ApplicableMUST be set on the object

cmis:changeToken Opaque token used for optimistic locking & concurrency checking. (see section 2.2.1.3 Change Tokens)

Required: FalseInherited: FalseProperty Type: StringCardinality: SingleUpdatability: Read OnlyChoices: Not ApplicableOpen Choice: Not Applicable

cmis:sourceId ID of the source object of the relationship.Required: TrueInherited: FalseProperty Type: IDCardinality: SingleChoices: Not ApplicableOpen Choice: Not Applicable

cmis:targetId ID of the target object of the relationship.Required: TrueInherited: FalseProperty Type: IDCardinality: SingleChoices: Not ApplicableOpen Choice: Not Applicable

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 45 of 240

181618171818181918201821

1822182318241825182618271828182918301831

1832183318341835183618371838183918401841

18421843184418451846184718481849

18501851185218531854185518561857

133134135

Page 46: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

2.1.7 Policy Object

A policy object represents an administrative policy that can be enforced by a repository, such as a retention management policy. CMIS 1.0 does not specify what kinds of administrative policies that are specifically supported, nor attempts to model administrative policy of any particular kind. Only a base object-type is specified for policy objects. Each policy object holds the text of an administrative policy as a repository-specific string, which is opaque to CMIS and which may be used to support policies of various kinds. A repository may create subtypes of this base type to support different kinds of administrative policies more specifically. If a repository does not support policy objects, the policy base object-type SHOULD NOT be returned by a “Get Types” service call. This is an extension point for repositories that want to expose other capabilities via CMIS that are not supported directly in CMIS 1.0.

Aside from allowing an application to create and maintain policy objects, CMIS allows an application to “apply” a policy to an object, and to remove an applied policy from an object. An object to which a policy may be applied is called a controllable object. A policy MAY be applied to multiple controllable objects. Conversely, a repository MAY allow multiple policies applied to a controllable object. (A repository may, for example, impose constraints such as only one policy of each kind can be applied to an object.) Whether or not an object is controllable is specified by the object’s type definition. Applying a policy to an object is to place the object under the control of that policy (while the object may also be under the control of other policies at the same time), and removing an applied policy from one of its controlled objects is to remove the corresponding control from that object. This control may change the state of the object, may impose certain constraints on service calls operating on this object, or may cause certain management actions to take place. The effect of this control, when this effect takes place, and how this control interacts with other controls, are repository-specific. Only directly/explicitly applied policies are covered by CMIS 1.0. Indirectly applying policy to an object, e.g. through inheritance, is outside the scope of CMIS 1.0.

A policy object does not have a content-stream and is not versionable. It may be fileable, queryable or controllable. Policy objects are handled using the basic CRUD services for objects. If a policy is updated, the change may alter the corresponding control on objects that the policy is currently applied to. If a controlled object is deleted, all the policies applied to that object, if there are any, are removed from that object. A policy object that is currently applied to one or more controllable objects CAN NOT be deleted. That is, there is an implicit referential constraint from a controlled object to its controlling policy object(s). Besides the basic CRUD services, the “Apply Policy” (applyPolicy) and the “Remove Policy” (removePolicy) services may be used to apply a policy object to a controllable object and respectively to remove an applied policy from one of its controlled objects. In addition, the “Get Applied Policies” (getAppliedPolicies) service may be used to obtain the policy objects that are currently applied to a controllable object.

2.1.7.1 Policy Object-Type DefinitionThis section describes the definition of the Policy Object-Type’s attribute values and property definitions which must be present on Policy instance objects. All attributes and property definitions are listed by their ID.

2.1.7.1.1 Attribute ValuesThe Policy Object-Type MUST have the following attribute values.Notes:

A value of <repository-specific> indicates that the value of the property MAY be set to any valid value for the attribute type.

Unless explicitly stated otherwise, all values specified in the table MUST be followed for the Object-Type definition.

id

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 46 of 240

1858

185918601861186218631864186518661867

1868186918701871187218731874187518761877187818791880

18811882188318841885188618871888188918901891

1892189318941895

1896189718981899190019011902

19031904

136137138

Page 47: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Value: cmis:policy

localNameValue: <repository-specific>

localNamespaceValue: <repository-specific>

queryNameValue: cmis:policy

displayNameValue: <repository-specific>

baseIdValue: cmis:policy

parentIdValue: Not set

descriptionValue: <repository-specific>

creatableValue: <repository-specific>

fileableValue: <repository-specific>

queryableValue: <repository-specific>

includedInSupertypeQueryValue: <repository-specific>

controllablePolicyValue: <repository-specific>

controllableACLValue: <repository-specific>

fulltextIndexed

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 47 of 240

1905

19061907

1908

19091910

1911

19121913

1914

19151916

1917

19181919

1920

19211922

1923

19241925

1926

19271928

1929

19301931

1932

19331934

1935

19361937

1938

19391940

1941

19421943

1944

19451946

139140141

Page 48: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Value: <repository-specific>

2.1.7.1.2 Property DefinitionsThe Policy base Object-Type MUST have the following property definitions, and MAY include additional property definitions. Any attributes not specified by the Property Definitions are repository specific. For all property definitions on base types, the query name MUST be the same as the property ID. The repository MUST have the following property definitions on the Policy Type:

cmis:name Name of the objectInherited: FalseProperty Type: StringCardinality: Single

cmis:objectId Id of the objectRequired: FalseInherited: FalseProperty Type: IDCardinality: SingleUpdatability: Read OnlyChoices: Not ApplicableOpen Choice: Not Applicable

cmis:baseTypeId Id of the base object-type for the objectRequired: FalseInherited: FalseProperty Type: IDCardinality: SingleUpdatability: Read OnlyChoices: Not ApplicableOpen Choice: Not Applicable

cmis:objectTypeId Id of the object’s typeRequired: FalseInherited: FalseProperty Type: IDCardinality: SingleUpdatability: oncreateChoices: Not ApplicableOpen Choice: Not Applicable

cmis:createdBy User who created the object.Required: False

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 48 of 240

1947

1948

19491950195119521953

19541955195619571958

195919601961196219631964196519661967

196819691970197119721973197419751976

197719781979198019811982198319841985

198619871988

142143144

Page 49: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Inherited: FalseProperty Type: StringCardinality: SingleUpdatability: Read OnlyChoices: Not ApplicableOpen Choice: Not Applicable

cmis:creationDate DateTime when the object was created.Required: FalseInherited: FalseProperty Type: DateTimeCardinality: SingleUpdatability: Read OnlyChoices: Not ApplicableOpen Choice: Not Applicable

cmis:lastModifiedBy User who last modified the object.Required: FalseInherited: FalseProperty Type: StringCardinality: SingleUpdatability: Read OnlyChoices: Not ApplicableOpen Choice: Not Applicable

cmis:lastModificationDate DateTime when the object was last modified.Required: FalseInherited: FalseProperty Type: DateTimeCardinality: SingleUpdatability: Read OnlyChoices: Not ApplicableOpen Choice: Not Applicable

cmis:changeToken Opaque token used for optimistic locking & concurrency checking. (see section 2.2.1.3 Change Tokens)

Required: FalseInherited: FalseProperty Type: StringCardinality: SingleUpdatability: Read OnlyChoices: Not Applicable

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 49 of 240

198919901991199219931994

199519961997199819992000200120022003

200420052006200720082009201020112012

201320142015201620172018201920202021

202220232024202520262027202820292030

145146147

Page 50: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Open Choice: Not Applicable

cmis:policyText User-friendly description of the policyRequired: TrueInherited: FalseProperty Type: StringCardinality: SingleChoices: Not ApplicableOpen Choice: Not Applicable

2.1.8 Access Control

A repository can support either a base set of CMIS-defined permissions and/or its own set of repository specific permissions. The getACL service allows the requestor to specify that the result be expressed using only the CMIS defined permissions. Without this restriction, the response may include, or be solely expressed in repository specific permissions. The applyACL service permits either CMIS permissions or repository permissions, or a combination of both, to be used.

2.1.8.1 ACL, ACE, Principal, and PermissionAn ACL is a list of Access Control Entries (ACEs) and MAY hold zero or more ACEs. If an ACL has no ACEs, the behavior is the same as if the ACL is not set.An ACE holds:

one Principal: A principal represents a user management object, e.g. a user, group, or role.It holds one String with the principalid.

One or more Strings with the names of the permissions. a Boolean flag direct, which indicates if TRUE the ACE is directly assigned to the object. If

FALSE, that the ACE is somehow derived.

2.1.8.2 CMIS PermissionsThere are three basic permissions predefined by CMIS:

cmis:read: to be used to express “permission to read”. A Repository SHOULD express the permission for reading properties AND reading content with this permission.

cmis:write: to be used to express “permission to write”. SHOULD be used to express permission to write properties and content of an object. MAY include other basic CMIS permissions.

cmis:all: SHOULD be used to express all the permissions of a repository. SHOULD include all other basic CMIS permissions.

How these basic permissions can be mapped to the allowable actions is repository specific. However, the actual repository semantics for the basic permissions with regard to allowable actions can be discovered by the mappings parameter returned by getRepositoryInfo (see below).Repositories MAY extend this set with repository-specific permissions.

2.1.8.3 ACL CapabilitiesWhether a repository supports ACLs at all, may be discovered via capabilityACL returned by getRepositoryInfo (see section 2.1.1.1 Optional Capabilities). If capabilityACL is none, ACLs are not supported by the repository.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 50 of 240

2031

20322033203420352036203720382039

2040

204120422043204420452046

204720482049205020512052205320542055

20562057205820592060206120622063

2064206520662067

2068206920702071

148149150

Page 51: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

If capabilityACL is discover or manage, additional information about the repositories permission model and how changes to ACL are handled, can be discovered via the getRepositoryInfo service:

<Array> Enum propagation: specifies, how non-direct ACEs can be handled by the repository using the following values (see section 2.2.10.2 applyACL):

o objectonly indicates, that the repository is able to apply ACEs to a document or folder, without changing the ACLs of other objects.

o propagate: indicates that the ACEs is to be applied to the given object and all inheriting objects.

o repositorydetermined indicates, that the repository has its own mechanism of computing how changing an ACL for an object influences the non-direct ACEs of other objects.

<Array> PermissionDefinition repositoryPermissions: is a list with names and descriptions of the supported permissions.

<Array> PermissionMapping mappings: contains a list with mappings for the basic CMIS permissions to allowed actions.

2.1.8.3.1 Supported Permissions

The list of permission definitions returned by getRepositoryInfo lists all the permissions a repository supports. This list also includes the CMIS permissions if supported by the repository.A PermissionDefinition holds:

String permission: the (technical) name of the permission (unique within the list of permission definitions).

(Optional) String description: an optional description of the permission that should be used as the permission’s name to be presented to the user.

2.1.8.3.2 AllowableActions & Permission MappingCMIS provides a mechanism called “AllowableActions” which allows an application to discover the set of service operations that can currently be performed on a particular object, without having to actually invoke the service. The set of allowable actions on an object at a point in time are affected not only by CMIS ACLs, but also by other factors such as:

Constraints inherent in the CMIS Domain Model based on the object’s base type or current versioning state.

Policies or other control mechanisms that are opaque to CMIS.

CMIS defines several services that applications can use at run-time to discover the AllowableActions for an object.If a Repository supports ACLs, then the repository MUST provide a mapping table that defines how the permissions supported by the repository interact with the CMIS allowable actions, i.e. which permissions are necessary for a principal to have on one or more objects in order to potentially perform each action, subject to the other constraints on allowable actions above. This section defines both the allowable actions as well as how those actions are presented in the PermissionMapping table. The Permission Mapping table contains a set of (key, permissions) pairs:

String Key: Because several allowable actions may require permissions on more than one object – for example, moving a document from one folder to another may require permissions on the document and each of the folders – the mapping table is defined in terms of permission “keys”,

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 51 of 240

207220732074207520762077207820792080208120822083208420852086

2087

2088208920902091209220932094

209520962097209820992100210121022103

2104210521062107210821092110211121122113211421152116

151152153

Page 52: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

where each key combines the name of the allowable action as the object for which the principal needs the required permission.

o For example – the canMoveObject.Source key indicates the permissions that the principal must have on the” “source folder” to move an object from that folder into another folder.

<Array> String permissions: The names of one or more permissions that the principal MUST have. If more than one permission is specified, then the principal MUST be allowed to perform the operation if they have ANY of the listed permissions.

The list below defines all mapping keys, as well as a permissions mapping that repositories SHOULD use. Repositories MAY require additional permissions. For convenience, the list below groups all mapping entries by the underlying Allowable Actions, and includes descriptive information. For each Allowable Action the following information is given:

Description: The description and name of the service the AllowableAction enables.Base Object: The base object-types for which the allowable action MAY be TRUE.Operand: The object the permission applies to.Key: The permission mapping key.Permissions: The permission values.

Navigation Services:canGetDescendants

Description: Can get the descendants of the folder (getDescendants)

Base Object: cmis:folderOperand: cmis:folderKey: canGetDescendants.FolderPermission: Read

canGetFolderTreeDescription: Can get the sub-folder tree of the folder (getFolderTree)

Base Object: cmis:folderOperand: cmis:folderKey: canGetFolderTree.FolderPermission: Read

canGetChildrenDescription: Can get the children of the folder (getChildren)

Base Object: cmis:folderOperand: cmis:folderKey: canGetChildren.FolderPermission: Read

canGetFolderParentDescription: Can get the parent/ancestor folder(s) of the folder (getFolderParent)

Base Object: cmis:folder

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 52 of 240

21172118211921202121212221232124212521262127212821292130213121322133

21342135213621372138213921402141

2142214321442145214621472148

2149215021512152215321542155

2156215721582159

154155156

Page 53: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Operand: cmis:folderKey: canGetFolderParent.FolderPermission: Read

canGetObjectParentsDescription: Can get the parent folders of the object. (getObjectParents)

Base Object: cmis:document, cmis:folder, cmis:policyOperand ObjectKey: canGetObjectParents.ObjectPermission: Read

Object Services:canCreateDocument

Description: Can create a cmis:document Object in the folder (createDocument)

Base Object: cmis:folderOperand: FolderKey: canCreateDocument.FolderPermission: Read

canCreateFolderDescription: Can create a cmis:folder Object as a child of the specified folder (createFolder)

Base Object: cmis:folderOperand: FolderKey: canCreateFolder.FolderPermission: Read

canCreateRelationshipDescription: Can create a Relationship in which this Object is a source

(createRelationship)

Base Object: cmis:document, cmis:folderOperand: ObjectKey: canCreateRelationship.SourcePermission: Read

canCreateRelationshipDescription: Can create a Relationship in which this Object is a target

(createRelationship)

Base Object: cmis:document, cmis:folderOperand: ObjectKey: canCreateRelationship.TargetPermission: Read

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 53 of 240

216021612162

2163216421652166216721682169

2170217121722173217421752176217721782179218021812182218321842185

21862187218821892190219121922193

21942195219621972198219922002201

157158159

Page 54: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

canGetPropertiesDescription: Can read the properties of this object (getProperties)

Base Object: cmis:document, cmis:folder, cmis:relationship, cmis:policyOperand: ObjectKey: canGetProperties.ObjectPermission: Read

canGetRenditionsDescription: Can retrieve the renditions of this object (getRenditions)

Base Object: cmis:document, or cmis:folderOperand: ObjectKey: canGetRenditions.ObjectPermission: Read

canGetContentStreamDescription: Can get the content stream for the Document object

(getContentStream)

Base Object: cmis:documentOperand: ObjectKey: canGetContentStream.ObjectPermission: Read

canUpdatePropertiesDescription: Can update the properties of this object (updateProperties)

Base Object: cmis:document, cmis:folder, cmis:relationship, cmis:policyOperand: ObjectKey: canUpdateProperties.ObjectPermission: Write

canMoveObjectDescription: Can move the object (moveObject)

Base Object: cmis:document, cmis:folder, cmis:policyOperand: ObjectKey: canMoveObject.ObjectPermission: Write

canMoveObjectDescription: Can move an object into this folder (moveObject)

Base Object: cmis:folderOperand: FolderKey: canMoveObject.Target

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 54 of 240

2202220322042205220622072208

2209221022112212221322142215

22162217221822192220222122222223

2224222522262227222822292230

2231223222332234223522362237

223822392240224122422243160161162

Page 55: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Permission: Read

canMoveObjectDescription: Can move an object from this folder (moveObject)

Base Object: cmis:folderOperand: FolderKey: canMoveObject.SourcePermission: Read

canDeleteObjectDescription: Can delete this object (deleteObject)

Base Object: cmis:document, cmis:folder, cmis:relationship, cmis:policyOperand: ObjectKey: canDelete.ObjectPermission: Write

canDeleteObjectDescription: Can delete an object that is a child of this folder (deleteObject)

Base Object: cmis:folderOperand: FolderKey: canDelete.FolderPermission: Read

canSetContentStreamDescription: Can set the content stream for the Document object

(setContentStream)

Base Object: cmis:documentOperand: ObjectKey: canSetContentStream.DocumentPermission: Write

canDeleteContentStreamBase Object: cmis:documentAction: Can delete the content stream for the Document object

(deleteContentStream)

Operand: ObjectKey: canDeleteContentStream.DocumentPermission: Write

canDeleteTreeBase Object: cmis:folderAction: Can delete the folder and all contained objects (deleteTree)

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 55 of 240

2244

2245224622472248224922502251

2252225322542255225622572258

2259226022612262226322642265

22662267226822692270227122722273

22742275227622772278227922802281

2282228322842285

163164165

Page 56: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Operand: ObjectKey: canDeleteTree.FolderPermission: Write

Filing Services:canAddObjectToFolder

Description: Can file the document in a folder (addObjectToFolder)

Base Object: cmis:document, cmis:policyOperand: ObjectKey: canAddObjectToFolder.ObjectPermission: Read

canAddObjectToFolderDescription: Can file a document in the specified folder (addObjectToFolder)

Base Object: cmis:document, cmis:policyOperand: ObjectKey: canAddObjectToFolder.FolderPermission: Read

canRemoveObjectFromFolderDescription: Can unfile the specified document from a folder (removeObjectFromFolder)

Base Object: cmis:document, cmis:policyOperand: ObjectKey: canRemoveObjectFromFolder.ObjectPermission: Read

canRemoveObjectFromFolderDescription: Can unfile a document from the specified folder (removeObjectFromFolder)

Base Object: cmis:document, cmis:policyOperand: ObjectKey: canRemoveObjectFromFolder.FolderPermission: Read

Versioning Services:canCheckOut

Description: Can check out the Document object (checkOut)

Base Object: cmis:documentOperand: ObjectKey: canCheckOut.Document

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 56 of 240

228622872288

22892290229122922293229422952296

2297229822992300230123022303

23042305230623072308230923102311

23122313231423152316231723182319

2320232123222323232423252326

166167168

Page 57: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Permission: Write

canCancelCheckOutDescription: Can cancel the check out the Document object (cancelCheckOut)

Base Object: cmis:documentOperand: ObjectKey: canCancelCheckOut.DocumentPermission: Write

canCheckInDescription: Can check in the Document object (checkIn)

Base Object: cmis:documentOperand: ObjectKey: canCheckIn.DocumentPermission: Write

canGetAllVersionsDescription: Can get the version series for the Document object (getAllVersions)

Base Object: cmis:documentOperand: ObjectKey: canGetAllVersions.DocumentPermission: Read

Relationship Services:canGetObjectRelationships

Description: Can get the relationship in which this object is a source/target (getObjectRelationships)

Base Object: cmis:document, cmis:folder, cmis:policyOperand: ObjectKey: canGetObjectRelationships.ObjectPermission: Read

Policy Services:canApplyPolicy

Description: Can apply a policy to the Object (applyPolicy)

Base Object: cmis:document, cmis:folderOperand: ObjectKey: canApplyPolicy.ObjectPermission: Read

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 57 of 240

2327

2328232923302331233223332334

2335233623372338233923402341

2342234323442345234623472348

234923502351235223532354235523562357

23582359236023612362236323642365

169170171

Page 58: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

canApplyPolicyDescription: Can apply the specified policy to an Object (applyPolicy)

Base Object: cmis:policyOperand: ObjectKey: canApplyPolicy.PolicyPermission: Read

canRemovePolicyDescription: Can remove a policy from the specified Object (removePolicy)

Base Object: cmis:document, cmis:folderOperand: ObjectKey: canRemovePolicy.ObjectPermission: Read

canRemovePolicyDescription: Can remove the specified policy from an Object (removePolicy)

Base Object: cmis:document, cmis:folderOperand: cmis:policyKey: canRemovePolicy.PolicyPermission: Read

canGetAppliedPoliciesDescription: Can get the list of Policies applied to the Object

(getAppliedPolicies)

Base Object: cmis:document, cmis:folderOperand: ObjectKey: canGetAppliedPolicies.ObjectPermission: Read

ACL Services:canGetACL

Description: Can get ACL for object (getACL)

Base Object: cmis:document, cmis:folder, cmis:relationship, cmis:policyOperand: ObjectKey: canGetACL.ObjectPermission: Read

canApplyACLDescription: Can apply ACL to this object (applyACL)

Base Object: cmis:document, cmis:folder, cmis:relationship, cmis:policy

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 58 of 240

2366236723682369237023712372

2373237423752376237723782379

2380238123822383238423852386

23872388238923902391239223932394

23952396239723982399240024012402

2403240424052406

172173174

Page 59: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Operand: ObjectKey: canApplyACL.ObjectPermission: Write

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 59 of 240

240724082409

175176177

Page 60: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

2.1.9 VersioningCMIS supports versioning of Document objects. Folder objects, relationship objects, and policy objects cannot be versioned. Whether or not a Document object is versionable (i.e. whether or not operations performed on the object via the Versioning Services MUST be allowed) is specified by the “versionable” attribute on its Object-type. A version of a Document object is an explicit/”deep” copy of the object, preserving its state at a certain point in time. Each version of a Document object is itself a Document object, i.e. has its own ObjectId, property values, MAY be acted upon using all CMIS services that act upon Document objects, etc.

2.1.9.1 Version SeriesA version series for a Document object is a transitively closed collection of all Document objects that have been created from an original Document in the Repository. Each version series has a unique, system-assigned, and immutable version series ID. The version series has transitive closure -- that is, if object B is a version of object A, and object C is a version of object B, then object C is also a version of object A. The objects in a version series can be conceptually sequenced by their respective CreationDate properties. Additionally, the repository MAY expose a textual VersionLabel that describes to a user the position of an individual object with respect to the version series. (For example, version 1.0). Note: A Document object that is NOT versionable will always have a single object in its Version Series. A versionable Document object MAY have one or more objects in its Version Series.

2.1.9.2 Latest VersionThe version that has the most recent LastModificationDate is called the Latest Version of the series, or equivalently, the latest version of any Document object in the series.When the latest version of a version series is deleted, a previous version (if there is one) becomes the latest version.

2.1.9.2.1 Behavioral constraints on non-Latest VersionsRepositories NEED NOT allow the non-latest versions in a Version Series to be updated, queried, or searched.

2.1.9.3 Major VersionsA Document object in a Version Series MAY be designated as a Major Version. The CMIS specification does not define any semantic/behavioral differences between Major and non-Major versions in a Version Series. Repositories may enforce/apply additional constraints or semantics for Major versions, if the effect on CMIS services remains consistent with an allowable behavior of the CMIS model.If the Version Series contains one or more Major versions, the one that has the most recent LastModificationDate is the Latest Major Version of the version series. (Note that while a Version Series MUST always have a Latest Version, it NEED NOT have a Latest Major Version.)When the latest major version is deleted, a previous major version (if there is one) becomes the latest major version.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 60 of 240

2410

241124122413241424152416241724182419

24202421242224232424242524262427242824292430

24312432243324342435

243624372438

243924402441244224432444244524462447244824492450

178179180

Page 61: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

2.1.9.4 Services that modify Version Series

2.1.9.4.1 CheckoutA new version of a versionable Document object is created when the checkIn service is invoked on the Private Working copy (PWC) of this object. A PWC is created by invoking checkOut on a versionable Document object. A repository MAY allow any Document object in a version series to be checked out, or MAY only allow the Latest Version to be checked out. The effects of invoking the checkout service MUST be as follows:

A new Document object, referred to herein as the Private Working Copy (PWC), is created.o The PWC NEED NOT be visible to users who have permissions to view other Document

objects in the Version Series. o Until it is checked in (using the checkIn service), the PWC MUST NOT be considered the

LatestMajorVersion in the Version Series. o The property values for the PWC SHOULD be identical to the properties of the Document

object on which the checkout service was invoked. Certain properties such as cmis:objectId may be different. Properties such as cmis:creationDate most likely will be different. The content-stream of the PWC MAY be identical to the content-stream of the Document object on which the checkout service was invoked, or MAY be “not set”.

After a successful checkout operation is completed, and until such time when the PWC is deleted (via the cancelCheckOut service) or checked-in (via the checkIn) service, the effects on other Documents in the Version Series MUST be as follows:

The repository MUST throw an exception if the checkout service is invoked on any Document in the Version Series. (I.e. there can only be one PWC for a version series at a time.)

The value of the cmis:isVersionSeriesCheckedOut property MUST be TRUE. The value of the cmis:versionSeriesCheckedOutBy property MAY be set to a value indicating

which user created the PWC. (The Repository MAY still show the “not set” value for this property.)

The value of the cmis:versionSeriesCheckedOutId property MAY be set to the ObjectId of the PWC. (The Repository MAY still show the “not set” value for this property).

The repository MAY prevent operations that modify or delete the other Documents in the Version Series.

2.1.9.4.2 Updates to the Private Working CopyIf the repository supports the optional “PWCUpdatable” capability, then the repository MUST allow authorized users to modify the PWC Object using the Object services (e.g. UpdateProperties). If the repository does NOT support the “PWCUpdatable” capability, then the PWC object can only be modified as part of the checkIn service call.

2.1.9.4.3 Discarding Check outAn authorized user MAY discard the check-out using the cancelCheckOut service on any Document in the Version Series or by using the deleteObject service on the PWC Object. The effects of discarding a check-out MUST be as follows:

The PWC Object MUST be deleted. For all other Documents in the Version Series:

o The value of the cmis:isVersionSeriesCheckedOut property MUST be FALSE.

o The value of the cmis:versionSeriesCheckedOutBy property MUST be “not set”.

o The value of the cmis:versionSeriesCheckedOutId property MUST be “not set”.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 61 of 240

2451

24522453245424552456245724582459246024612462246324642465246624672468246924702471247224732474247524762477247824792480

24812482248324842485

248624872488248924902491249224932494

181182183

Page 62: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

o The repository MUST allow authorized users to invoke the checkout service.

2.1.9.4.4 CheckinAn authorized user/application MAY “check in” the Private Working Copy object via the checkIn service. The checkIn service allows users/applications to provide update property values and a content-stream for the PWC object. The effects of the checkIn service MUST be as follows for successful checkins:

The PWC object MUST be updated as specified by the inputs to the checkIn service. (Note that for repositories that do NOT support the “PWCUpdatable” property, this is the only way to update the PWC object.)

The Document object resulting from the checkIn operation MUST be considered the Latest Version in the Version Series.

If the inputs to the checkIn service specified that the PWC MUST be a “major version”, then the PWC MUST be considered the Latest Major Version in the Version Series.

If the checkin returns a new cmis:objected, then the PWC object MUST disappear if the checkIn call was successful and the new checked in version will use the new specified id.

For all Documents in the Version Series:o The value of the cmis:isVersionSeriesCheckedOut property MUST be FALSE.

o The value of the cmis:versionSeriesCheckedOutBy property MUST be “not set”.

o The value of the cmis:versionSeriesCheckedOutId property MUST be “not set”.

o The repository MUST allow authorized users to invoke the checkout service.

Note: The Repository MAY change the ID of the PWC upon completion of the checkin service invocation.Note: A repository MAY automatically create new versions of Document objects without an explicit invocation of the checkout/checkin services.

2.1.9.5 Versioning Properties on Document ObjectsAll Document objects will have the following read-only property values pertaining to versioning:

cmis:isLatestVersion Boolean

TRUE if the Document object is the Latest Version in its Version Series. FALSE otherwise.

cmis:isMajorVersion Boolean

TRUE if the Document object is a Major Version in its Version Series. FALSE otherwise.

cmis:isLatestMajorVersion Boolean

TRUE if the Document object is the Latest Major Version in its Version Series. FALSE otherwise.

cmis:versionLabel String (optional)

Optional textual description the position of an individual object with respect to the version series. (For example, version 1.0).

cmis:versionSeriesId ID

ID of the Version Series for this Object.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 62 of 240

2495

2496249724982499250025012502250325042505250625072508250925102511251225132514251525162517

25182519

25202521

2522

25232524

2525

25262527

2528

25292530

25312532

25332534

2535

2536

184185186

Page 63: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

cmis:isVersionSeriesCheckedOut Boolean

TRUE if there currenly exists a Private Working Copy for this Version Series. FALSE otherwise

cmis:versionSeriesCheckedOutBy String

If IsVersionSeriesCheckedOut is TRUE: then an identifier for the user who created the Private Working Copy. “Not set” otherwise.

cmis:versionSeriesCheckedOutId ID

If IsVersionSeriesCheckedOut is TRUE: The Identifier for the Private Working Copy. “Not set” otherwise.

cmis:checkinComment String

Textual comment associated with the given version.

Note: Changes made via the Versioning Services that affect the values of these properties MUST NOT constitute modifications to the Document objects in the Version Series (e.g. MUST NOT affect the cmis:lastModificationDate, etc.)

2.1.9.6 Document Creation and Initial Versioning StateA repository MAY create new Document objects in a “Private Working Copy” state when they are created via the createDocument or createDocumentFromSource services. This state is logically equivalent to having a Version Series that contains exactly one object (the PWC) and 0 other documents. 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 MAY create new Document objects in a “Major Version” state. MUST ignore the value of the versioningState parameter.

2.1.9.7 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 “VersionSpecificFiling” optional capability flag. 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.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 63 of 240

2537

2538

25392540

25412542

25432544

25452546

25472548

2549

255025512552

25532554255525562557255825592560256125622563

25642565256625672568256925702571257225732574257525762577

187188189

Page 64: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

2.1.9.8 Version Specific/Independent membership in RelationshipsA 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.9.9 Versioning visibility in Query ServicesRepositories MAY include non-latest-versions of Document Objects in results to the Discovery Services (query). Repositories MUST indicate whether they support querying for non-latest-versions via the “AllVersionsSearchable” optional capability flag. If “AllVersionsSearchable” 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 in results to the Discovery Services (query). Repositories MUST indicate whether they support querying for Private Working Copy objects via the “PWCSearchable” optional capability flag. If “PWCSearchable” is TRUE then the Repository MUST include in the query results ANY Private Working Copy Document Objects that matches the query criteria (subject to other query constraints such as security.)If “PWCSearchable” is FALSE then the Repository MUST NOT include in the query results ANY Private Working Copy Document Objects that match the query criteria (subject to other query constraints such as security.)

2.1.10 QueryCMIS provides a type-based query service for discovering objects that match specified criteria, by defining a read-only projection of the CMIS data model into a Relational View. Through this relational view, queries may be performed via a simplified SQL SELECT statement. This query language is based on a subset of the SQL-92 grammar (ISO/IEC 9075: 1992 – Database Language SQL), with a few extensions to enhance its filtering capability for the CMIS data model, such as existential quantification for multi-valued property, full-text search, and folder membership. Other statements of the SQL language are not adopted by CMIS. The semantics of this query language is defined by the SQL-92 standard, plus the extensions, in conjunction with the model mapping defined by CMIS’s relational view.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 64 of 240

25782579258025812582258325842585258625872588

258925902591259225932594259525962597259825992600260126022603260426052606

260726082609261026112612261326142615

190191192

Page 65: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

2.1.10.1 Relational View Projection of the CMIS Data ModelThe relational view of a CMIS repository consists of a collection of virtual tables that are defined on top of the CMIS data model. This relational view is used for query purposes only.

In this relational view a Virtual Table is implicitly defined for each queryable Object-Type defined in the repository. (Non-queryable Object-Types are NOT exposed through this Relational View.)

In each Virtual Table, a Virtual Column is implicitly defined for each property defined in the Object-Type Definition AND for all properties defined on ANY ancestor-type of the Object-Type but NOT defined in the Object-Type definition. Virtual Columns for properties defined on ancestor-types of the Object-type but NOT defined in the Object-Type definition MUST contain the SQL NULL value. Virtual Columns for properties whose value is “not set” MUST contain the SQL NULL value.

An object-type’s queryName attribute is used as the table name for the corresponding virtual table, and a property’s queryName attribute is used as the column name for the corresponding table column. Please see the restrictions on queryName in the appropriate data model section.

The Virtual Column for a multi-valued property MUST contain a single list value that includes all values of the property.

2.1.10.1.1 Object-Type Hierarchy in the Relational View Projection

The Relational View projection of the CMIS Data Model ensures that the Virtual Table for a particular Object-type is a complete super-set of the Virtual Table for any and all of its ancestor types.

Additionally, an Object-Type definition’s “includedInSupertypeQuery” specifies whether objects of that Object-Type MUST be included in the Virtual Table for any of its ancestor types. If the “includedInSupertypeQuery” attribute of the Object-Type is FALSE, then objects of that Object-Type MUST NOT be included in the Virtual Table for any of its ancestor types.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 65 of 240

2616

261726182619

26202621

26222623262426252626

262726282629

26302631

2632

26332634

2635263626372638

193194195

Page 66: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Thus the Virtual Table for an Object-type includes a row not only for each Object of that type, but all Objects of any of that Object-types’ Descendant Types for which the “includedInSupertypeQuery” attribute is TRUE.

But since the Virtual Table will include only columns for properties defined in the Object-Type underlying the Virtual Table, a row that is a query result representing an Object of a Descendant Type can only include those columns for properties defined on the Object-Type underlying the Virtual Table.

2.1.10.1.2 Content Streams

Content-streams are NOT exposed through this relational view.

2.1.10.1.3 Result SetWhen a query is submitted, a set of pseudo CMIS objects will be returned. These pseudo objects are comprised of the properties specified in the select clause of the query statement. For each property in each object in the result set, the Repository MUST include the property definition ID as well as either the query name (if no alias is used) or the alias in place of the query name (if an alias is used). If the select clause of the query statement contains properties from a single type reference then the repository MAY represent these pseudo-objects with additional object information.

2.1.10.2 Query Language DefinitionThis query languages is based on a subset of the SQL-92 grammar. CMIS-specific language extensions to SQL-92 are called out explicitly. The basic structure of a CMIS query is a SQL statement that MUST include the following clauses:

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 66 of 240

263926402641

264226432644

2645

2646

2647

26482649265026512652265326542655

2656265726582659

196197198

Page 67: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

SELECT [virtual columns]: This clause identifies the set of virtual columns that will be included in the query results for each row.

FROM [Virtual Table Names]: This clause identifies which Virtual Table(s) the query will run against.

Additionally, a CMIS query MAY include the following clauses: WHERE [conditions]: This clause identifies the constraints that rows MUST satisfy to be

considered a result for the query. ORDER BY [sort specification]: This clause identifies the order in which the result rows MUST

be sorted in the result row set.

2.1.10.2.1 BNF GrammarThis BNF grammar is a “subset” of the SQL-92 grammar (ISO/IEC 9075: 1992 – Database Language SQL), except for some production alternatives. Specifically, except for these extensions, the following production rules are derived from the SQL-92 grammar. The non-terminals used in this grammar are also borrowed from the SQL-92 grammar without altering their semantics. Accordingly, the non-terminal <column name> is used for single-valued properties only so that the semantics of SQL can be preserved and borrowed. This approach not only facilitates comparison of the two query languages, and simplifies the translation of a CMIS query to a SQL query for a RDBMS-based implementation, but also allows future expansion of this query language to cover a larger subset of SQL with minimum conflict. The CMIS extensions are introduced primarily to support multi-valued properties and full-text search, and to test folder membership. Multi-valued properties are handled separately from single-valued properties, using separate non-terminals and separate production rules to prevent the extensions from corrupting SQL-92 semantics.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 67 of 240

266026612662266326642665266626672668

2669267026712672267326742675267626772678267926802681

199200201

Page 68: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<CMIS 1.0 query statement> ::= <simple table> [ <order by clause> ]<simple table> ::= SELECT <select list> <from clause> [ <where clause> ]<select list> ::= “*”

| <select sublist> [ { “,” <select sublist> }… ]<select sublist> ::= <value expression> [ [ AS ] <column name> ]

| <qualifier> “.*”| <multi-valued-column reference>

<value expression> ::= <column reference> | <numeric value function><column reference> ::= [ <qualifier> “.” ] <column name><multi-valued-column reference> ::= [ <qualifier> “.” ] <multi-valued-column name><numeric value function> ::= SCORE()<qualifier> ::= <table name> | <correlation name><from clause> ::= FROM <table reference><table reference> ::= <table name> [ [ AS ] <correlation name> ]

| <joined table><joined table> ::= “(“ <joined table> “)”

| <table reference> [ <join type> ] JOIN <table reference> <join specification><join type> ::= INNER | LEFT [ OUTER ]<join specification> ::= ON <column reference> "=" <column reference> <where clause> ::= WHERE <search condition><search condition> ::= <boolean term> | <search condition> OR <boolean term><boolean term> ::= <boolean factor> | <boolean term> AND <boolean factor><boolean factor> ::= [ NOT ] <boolean test><boolean test> ::= <predicate> | “(“ <search condition> “)”<predicate> ::= <comparison predicate> | <in predicate> | <like predicate> | <null predicate>

| <quantified comparison predicate> | <quantified in predicate>| <text search predicate> | <folder predicate>

<comparison predicate> ::= <value expression> <comp op> <literal><comp op> ::= “=” | “<>” | “<” | “>” | “<=” | “>=”<literal> ::= <signed numeric literal> | <character string literal> | <datetime literal> | <boolean literal><in predicate> ::= <column reference> [ NOT ] IN “(“ <in value list> “)”<in value list> ::= <literal> [{ “,” <literal> }…]<like predicate> ::= <column reference> [ NOT ] LIKE <character string literal><null predicate> ::= { <column reference> | <multi-valued-column reference> } IS [ NOT ] NULL<quantified comparison predicate> ::= <literal> “=” ANY <multi-valued-column reference><quantified in predicate> ::= ANY <multi-valued-column reference> [ NOT ] IN “(“ <in value list> “)”<text search predicate> ::= CONTAINS "("

[ <qualifier> "," ] <quote> <text search expression> <quote> ")" <folder predicate> ::= { IN_FOLDER | IN_TREE } “(“ [ <qualifier> “,” ] <folder id> “)”<order by clause> ::= ORDER BY <sort specification> [ { “,” <sort specification> }… ]

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 68 of 240

26822683268426852686268726882689269026912692269326942695269626972698269927002701270227032704270527062707270827092710271127122713271427152716271727182719272027212722

202203204

Page 69: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<sort specification> ::= <column reference> [ ASC | DESC ]<correlation name> ::= <identifier><table name> ::= <identifier> !! This MUST be the name of an object-type.<column name> ::= <identifier> !! This MUST be the name of a single-valued property,

or an alias for a scalar output value.<multi-valued-column name> ::= <identifier> !! This MUST be the name of a multi-valued property.<folder id> ::= <character string literal> !! This MUST be the object identity of a folder object.<identifier> ::= !! As defined by queryName attribute.<signed numeric literal> ::= !! As defined by SQL-92 grammar.<character string literal> ::= !! As defined by SQL-92 grammar. (i.e. enclosed in single-quotes)

!! This is full-text search criteria. <text search expression> ::= <disjunct>conjunct> [ {<space> OR <space> <disjunct>}conjunct>} … ]<disjunctconjunct> ::= <term> [ {<space> <term>} … ]<term> ::= ['-'] <simple term><simple term> ::= <word> | <phrase><word> ::= <non space char> [ {<non space char>} … ]<phrase> ::= <quote> <word> [ {<space> <word>} … ] <quote><space> ::= <space char> [ {<space char>} … ]<non space char> ::= <char> - <space char> <space char> ::= ' '<char> ::= !! Any character

<datetime literal> ::= TIMESTAMP <quote> <datetime string> <quote> <datetime string> ::= YYYY-MM-DDThh:mm:ss.sss[Z | +hh:mm | -hh:mm] <boolean literal> ::= TRUE | FALSE | true | false<quote> ::= ‘”’ | “’”“’” !! Single-quote only, consistent with SQL-92 string literal

2.1.10.2.2 SELECT ClauseThe SELECT clause MUST contain exactly one of the following:

A comma separated list of one or more column names. o If an explicit column list is provided: A repository MUST include in its result row set all of the

columns specified in the SELECT clause. * : If this token is specified, then the repository MUST return columns for ALL single-valued

properties defined in the Object-Types whose Virtual Tables are listed in the FROM clause, and SHOULD also return all multi-valued properties.

All column names MUST be valid “queryName” values for properties that are defined as “queryable” in the Object-Type(s) whose Virtual Tables are listed in the FROM clause.

2.1.10.2.3 FROM ClauseThe FROM clause identifies which Virtual Table(s) the query will be run against, as described in the previous section. The FROM clause MUST contain only the queryNames of Object-Types whose queryable attribute value is TRUE. cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 69 of 240

2723272427252726272727282729273027312732

273327342735273627372738273927402741274227432744

27452746274727482749

2750275127522753275427552756275727582759

27602761276227632764205206207

Page 70: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

2.1.10.2.3.1 Join Support CMIS repositories MAY support the use of SQL JOIN queries, and MUST indicate their support level using the Optional Capability attribute “capabilityJoin”.

If the Repository’s value for the capabilityJoin attribute is none, then no JOIN clauses can be used in queries.

If the Repository’s value for the capabilityJoin attribute is inneronly, then only inner JOIN clauses can be used in queries.

If the Repository’s value for the capabilityJoin attribute is innerandouter, then inner and/or outer JOIN clauses can be used in queries.

Only explicit joins using the “JOIN” keyword is supported. Queries MUST NOT include implicit joins as part of the WHERE clause of a CMIS query. CMIS queries MUST only support join operations using the “equality” predicate on single-valued properties.

2.1.10.2.4 WHERE ClauseThis clause identifies the constraints that rows MUST satisfy to be considered a result for the query.All column names MUST be valid “queryName” or their aliased values for properties that are defined as “queryable” in the Object-Type(s) whose Virtual Tables are listed in the FROM clause. Properties are defined to not support a “null” value, therefore the <null predicate> MUST be interpreted as testing the not set or set state of the specified property.

2.1.10.2.4.1 Comparisons permitted in the WHERE clause.

SQL’s simple comparison predicate, IN predicate, and LIKE predicate are supported, for single-valued properties only (so that SQL’s semantics is preserved). Boolean conjunction (AND), disjunction (OR), and negation (NOT) of predicates are also supported.

Repositories SHOULD support the comparisons for the property types as described in the list below. Repositories MAY support additional comparisons and operators. Any additional operators not specified are repository-specific:

<Property Type>Supported Operators: <List of Operators supported on Type>Supported Literal: <Supported type of Literal in comparison>

String (Single)Supported Operators: =, <>, [NOT] LIKESupported Literal: String

String (IN)Supported Operators: [NOT] INSupported Literal: List of Strings

DecimalSupported Operators: =, <>, <, <=, >, >= Supported Literal: Decimal

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 70 of 240

2765276627672768276927702771277227732774277527762777

277827792780278127822783

2784

278527862787

278827892790

2791279227932794

2795279627972798

2799280028012802

2803280428052806

208209210

Page 71: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Decimal (IN)Supported Operators: [NOT] INSupported Literal: List of Decimal IntegerSupported Operators: =, <>, <, <=, >, >= Supported Literal: Integer

Integer (IN)Supported Operators: [NOT] INSupported Literal: List of Integer

BooleanSupported Operators: = Supported Literal: <boolean literal> DateTimeSupported Operators: =, <>, <*, <=*, >*, >=* Supported Literal: <datetime literal>* - comparison is based on chronological before or after date.

DateTime (IN)Supported Operators: [NOT] INSupported Literal: List of <datetime literal>’s IDSupported Operators: =, <> Supported Literal: String ID (IN)Supported Operators: [NOT] INSupported Literal: List of strings

URISupported Operators: =, <> Supported Literal: String

URI (IN)Supported Operators: [NOT] INSupported Literal: List of strings

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 71 of 240

28072808280928102811281228132814

2815281628172818

281928202821282228232824282528262827

282828292830283128322833283428352836283728382839

2840284128422843

2844284528462847

2848211212213

Page 72: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

URISupported Operators: [NOT] LIKESupported Literal: String Operations on the SCORE() output MUST be treated the same as decimal operations.

When using properties in a join statement, comparison MUST be allowed on properties of the same types as defined by the table above. Repositories MAY extend this behavior.

The ANY operation argument MUST be one of the properties found in the table above which supports equality operations

2.1.10.2.4.2 Multi-valued property support (SQL-92 Extension)The CMIS query language includes several new non-terminals to expose semantics for querying multi-valued properties, in a way that does not alter the semantics of existing SQL-92 production rules.

2.1.10.2.4.2.1 Multi-valued column referencesBNF grammar structure: <Multi-valued-column reference>, <multi-valued-column name>

These are non-terminals defined for multi-valued properties whereas SQL-92’s <column reference> and <column name> are retained for single-valued properties only. This is to preserve the single-value semantics of a regular “column” in the SQL-92 grammar.

2.1.10.2.4.2.2 <Quantified comparison predicate>The SQL-92 production rule for <quantified comparison predicate> is extended to accept a multi-valued property in place of a <table subquery>. This operation is restricted to equality tests only.

<Table subquery> is not supported in CMIS-SQL.

The SQL-92 <quantifier> is restricted to ANY only.

The SQL-92 <row value constructor> is restricted to a literal only.

Example: SELECT Y.CLAIM_NUM, X.PROPERTY_ADDRESS, Y.DAMAGE_ESTIMATESFROM POLICY AS X JOIN CLAIMS AS Y ON ( X.POLICY_NUM = Y.POLICY_NUM )WHERE ( 100000 = ANY Y.DAMAGE_ESTIMATES )

(Note: DAMAGE_ESTIMATES is a multi-valued Integer property.)

2.1.10.2.4.2.3 IN/ANY PredicateBNF grammar structure: <Quantified in predicate>

CMIS-SQL exposes a new IN predicate defined for a multi-valued property. It is modeled after the SQL-92 IN predicate, but since the entire predicate is different semantically, it has its own production rule in the BNF grammar below.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 72 of 240

28492850285128522853

285428552856

285728582859

286028612862

28632864286528662867

2868286928702871287228732874

28752876

2877287828792880

2881

28822883

28842885288628872888

214215216

Page 73: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

The quantifier is restricted to ANY. The predicate MUST be evaluated to TRUE if at least one of the property’s values is (or, is not, if NOT is specified) among the given list of literal values. Otherwise the predicate is evaluated to FALSE.

The ANY operation argument MUST be one of the properties found in the comparison list above which supports IN operations.Example:

SELECT *FROM CAR_REVIEWWHERE (MAKE = “buick”‘buick’ ) OR ( ANY FEATURES IN (“(‘NAVIGATION SYSTEM”, “SYSTEM’, ‘SATELLITE RADIO”, ”MP3”) )

RADIO’, ‘MP3’) ) (Note: FEATURES is a multi-valued String property.)

2.1.10.2.4.3 CONTAINS() predicate function (CMIS-SQL Extension)

BNF grammar structure:: CONTAINS ( [ <qualifier> ,] ‘ <text search expression> ‘ )

Usage: This is a predicate function that encapsulates the full-text search capability that MAY be provided by a Repository (See previous section.)Inputs:

<Qualifier>The value of this optional parameter MUST be the name of one of the Virtual Tables listed in the FROM clause for the query. If specified, then the predicate SHOULD only be applied to objects in the specified Virtual

Table, but a repository MAY ignore the value of the parameter. If not specified, applies to the single virtual table. If the query is a join, a server SHOULD

throw an exception if the qualifier is not specified.

<Text Search Expression>The <text search expression> parameter MUST be a character string literal in quotes, specifying the full-text search criteria.

The Text Search Expression may be a set of terms or phrases with an optional ‘-‘ to signal negation. A phrase is defined as a word or group of words. A group of words must be surrounded by quotes to be considered a single phrase.

Terms separated by whitespace are AND’ed together.Terms separated by “OR” are OR’ed togetherImplicit “AND” has higher precedence than “OR”Within a word or phrase, each double (single-)quote must also be escaped by a preceding backslash “\”

Return value: The predicate returns a Boolean value. The predicate MUST return TRUE if the object is considered by the repository as “relevant” with respect to the given <text search expression> parameter. The predicate MUST return FALSE if the object is considered by the repository as not “relevant” with respect to the given <text search expression> parameter.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 73 of 240

2889289028912892289328942895

28962897289828992900

2901

2902

2903

290429052906

2907290829092910291129122913

2914291529162917291829192920292129222923292429252926292729282929293029312932

217218219

Page 74: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Constraints:At most one CONTAINS() function MUST be included in a single query statement. The repository MUST throw an exception if more than one CONTAINS() function is found.

The return value of the CONTAINS() function MAY only be included conjunctively (ANDed) with the aggregate of all other predicates, if there is any, in the WHERE clause.

2.1.10.2.4.4 SCORE() predicate functionBNF grammar structure: SCORE ()

Usage: This is a predicate function that encapsulates the full-text search capability that MAY be provided by a Repository (See previous section.)

Inputs: No inputs MUST be provided for this predicate function. Return value:

The SCORE() predicate function returns a decimal value in the interval [0,1] .A repository MUST return the value 0 if the object is considered by the repository as having absolutely no relevance with respect to the CONTAINS() function specified in the query. A repository MUST return the value 1 if the object is considered by the repository as having absolutely complete relevance with respect to the CONTAINS() function specified in the query.

Constraints:The SCORE() function MUST only be used in queries that also include a CONTAINS() predicate functionThe SCORE() function MUST only be used in the SELECT clause of a query. It MUST NOT be used in the WHERE clause or in the ORDER BY clauses. An alias column name defined for the SCORE() function call in the SELECT clause (i.e., "SELECT SCORE() AS column_name …") may be used in the ORDER BY clause. If SCORE() is included in the SELECT clause and an alias column name is not provided, then a query name of SEARCH_SCORE is used for the query output, and the property definition ID is repository-specific.

2.1.10.2.4.5 IN_FOLDER() predicate function

BNF grammar structure: IN_FOLDER( [ <qualifier>, ] <folder id> )

Usage: This is a predicate function that tests whether or not a candidate object is a child-object of the folder object identified by the given <folder id>.Inputs:

<qualifier>The value of this optional parameter MUST be the name of one of the Virtual Tables listed in the FROM clause for the query. If specified, then the predicate SHOULD only be applied to objects in the specified Virtual

Table, but a repository MAY ignore the value of the parameter. If not specified, applies to the single virtual table. If the query is a join, a server SHOULD

throw an exception if the qualifier is not specified.

<folder id>

The value of this parameter MUST be the ID of a folder object in the repository.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 74 of 240

293329342935

293629372938

29392940

29412942

29432944294529462947294829492950295129522953295429552956295729582959

2960

2961

296229632964

2965296629672968296929702971

2972

2973

220221222

Page 75: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Return value: The predicate function MUST return TRUE if the object is a child-object of the folder specified by <folder id>.The predicate function MUST return FALSE if the object is a NOT a child-object of the folder specified by <folder id>.

2.1.10.2.4.6 IN_TREE() predicate function

BNF grammar structure: IN_TREE( [ <qualifier>, ] <folder id> )

Usage: This is a predicate function that tests whether or not a candidate object is a descendant-object of the folder object identified by the given <folder id>. Inputs:

<qualifier>The value of this optional parameter MUST be the name of one of the Virtual Tables listed in the FROM clause for the query. If specified, then the predicate SHOULD only be applied to objects in the specified Virtual

Table, but a repository MAY ignore the value of the parameter. If not specified, applies to the single virtual table. If the query is a join, a server SHOULD

throw an exception if the qualifier is not specified. <folder id>

The value of this parameter MUST be the ID of a folder object in the repository. Return value:

The predicate function MUST return TRUE if the object is a descendant-object of the folder specified by <folder id>.The predicate function MUST return FALSE if the object is a NOT a descendant -object of the folder specified by <folder id>.

2.1.10.2.5 ORDER BY ClauseThis clause MUST contain a comma separated list of one or more column names. All column names referenced in this clause MUST be valid “queryName” or their aliased values for properties defined as orderable in the Object-type(s) whose Virtual Tables are listed in the FROM clause. Only columns in the SELECT clause MAY be in the ORDER BY clause.Collation rules for the ORDER BY clause are repository specific.

2.1.10.3 EscapingRepositories MUST support the escaping of characters using a backslash (\) in the query statement. The backslash character (\) will be used to escape characters within quoted strings in the query as follows:

1. \" will represent a double-quote (") character2. \’ will represent a single-quote(‘) character3. \ \ will represent a backslash (\) character4. Within a LIKE string, \% and \_ will represent the literal characters % and _, respectively.5. All other instances of a \ are errors.

2.1.11 Change LogCMIS provides a “change log” mechanism to allow applications to easily discover the set of changes that have occurred to objects stored in the repository since a previous point in time. This change log can then

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 75 of 240

29742975297629772978

2979

2980

298129822983

29842985298629872988298929902991

299229932994299529962997

299829993000300130023003

30043005300630073008300930103011

301230133014

223224225

Page 76: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

be used by applications such as search services that maintain an external index of the repository to efficiently determine how to synchronize their index to the current state of the repository (rather than having to query for all objects currently in the repository).Entries recorded in the change log are referred to below as “change events”.Note that change events in the change log MUST be returned in ascending order from the time when the change event occurred.

2.1.11.1 Completeness of the Change LogThe Change Log mechanism exposed by a repository MAY be able to return an entry for every change ever made to content in the repository, or may only be able to return an entry for all changes made since a particular point in time. This “completeness” level of the change log is indicated via the optional changesIncomplete value found on the getRepositoryInfo service response

However, repositories MUST ensure that if an application requests the entire contents of the repository’s change log, that the contents of the change log includes ALL changes made to any object in the repository after the first change listed in the change log. (I.e. repositories MAY truncate events from the change log on a “first-in first-out” basis, but not in any other order.)A Repository MAY record events such as filing/unfiling/moving of Documents as change events on the Documents, their parent Folder(s), or both the Documents and the parent Folders.

2.1.11.2 Change Log TokenThe primary index into the change log of a repository is the “change log token”. The change log token is an opaque string that uniquely identifies a particular change in the change log.

2.1.11.2.1 “Latest Change Token” repository informationRepositories that support the changeLogToken event MUST expose the latest change log token (i.e. the change log token corresponding to the most recent change to any object in the repository) as a property returned by the getRepositoryInfo service.This will enable applications to begin “subscribing” to the change log for a repository by discovering what change log token they should use on a going-forward basis to discover change events to the repository.

2.1.11.3 Change EventA change event represents a single action that occurred to an object in the repository that affected the persisted state of the object.A Repository that supports the change log capability MUST expose at least the following information for each change object:

ID ObjectId: The ObjectId of the object to which the change occurred Enum ChangeType: An enumeration that indicates the type of the change. Valid values are:

o created: The object was created.

o updated: The object was updated.

o deleted: The object was deleted

o security: The access control or security policy for the object were changed.

<Properties> properties: Additionally, for events of changeType “updated”, the repository MAY optionally include the new values of properties on the object (if any).

Repositories MUST indicate whether they include properties for “updated” change events via the optional enumCapabilityChanges capability.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 76 of 240

301530163017301830193020

30213022302330243025302630273028302930303031

303230333034

303530363037303830393040

3041304230433044304530463047304830493050305130523053305430553056

226227228

Page 77: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

2.2 Services Part IThe Services section of the CMIS specification defines a set of services that are described in a protocol/binding-agnostic fashion. Every protocol binding of the CMIS specification MUST implement all of the methods described in this section or explain why the service is not implemented. However, the details of how each service & method is implemented will be described in those protocol binding specifications.

2.2.1 Common Service ElementsThe following elements are common across many of the CMIS services.

2.2.1.1 Paging All of the methods that allow for the retrieval of a collection of CMIS objects support paging of their result sets except where explicitly stated otherwise. The following pattern is used:Input Parameters:

(optional) Integer maxItems: This is the maximum number of items to return in a response. The repository MUST NOT exceed this maximum. Default is repository-specific.

(optional) Integer skipCount: This is the number of potential results that the repository MUST skip/page over before returning any results. Defaults to 0.

Output Parameters: Boolean hasMoreItems: TRUE if the Repository contains additional items after those contained

in the response. FALSE otherwise. If TRUE, a request with a larger skipCount or larger maxItems is expected to return additional results (unless the contents of the repository has changed).

Integer numItems: If the repository knows the total number of items in a result set, the repository SHOULD include the number here. If the repository does not know the number of items in a result set, this parameter SHOULD not be set. The value in the parameter MAY NOT be accurate the next time the client retrieves the result set or the next page in the result set.

If the caller of a method does not specify a value for maxItems, then the Repository MAY select an appropriate number of items to return, and MUST use the hasMoreItems output parameter to indicate if any additional results were not returned. Repositories MAY return a smaller number of items than the specified value for maxItems. Each binding will express the above in context and may have different mechanisms for communicating hasMoreItems and numItems.

2.2.1.2 Retrieving additional information on objects in CMIS service callsSeveral CMIS services that return object information have the ability to return dependent object information as part of their response, such as the Allowable Actions for an object, rendition information, etc.The CMIS service methods that support returning a result set of objects will include the ability to return the following object information:

Properties (retrieves a subset instead of additional information) Relationships Renditions ACLs AllowableActions

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 77 of 240

3057305830593060306130623063

30643065

30663067306830693070307130723073307430753076307730783079308030813082308330843085308630873088

30893090309130923093309430953096309730983099

229230231

Page 78: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

This section describes the input parameter & output pattern for those services. All input parameters are optional.

2.2.1.2.1 PropertiesDescription: All of the methods that allow for the retrieval of properties for CMIS Objects have a “Property Filter” as an optional parameter, which allows the caller to specify a subset of properties for Objects that MUST be returned by the repository in the output of the method. Optional Input Parameter:

String filter: Value indicating which properties for Objects MUST be returned. Values are: o Not set: The set of properties to be returned MUST be determined by the repository.

o A comma-delimited list of property definition Query Names: The properties listed MUST be returned.

o “*” : All properties MUST be returned for all objects.

Repositories SHOULD return only the properties specified in the property filter if they exist on the object’s type definition.

If a property filter specifies a property that is ‘not set’, it MUST be represented as a property element without a value element.

2.2.1.2.2 RelationshipsDescription: Used to retrieve the relationships in which the object(s) are participating. Optional Input Parameter:

Enum includeRelationships: Value indicating what relationships in which the objects returned participate MUST be returned, if any. Values are:

none:No relationships MUST be returned. (Default).

source: Only relationships in which the objects returned are the source MUST be returned.target: Only relationships in which the objects returned are the target MUST be returned.both: Relationships in which the objects returned are the source or the target MUST be returned.

Output Parameter for each object: <Array> Relationships: A collection of the relationship objects.

2.2.1.2.3 PoliciesDescription: Used to retrieve the policies currently applied to the object(s). Optional Input Parameter:

Boolean includePolicyIds: If TRUE, then the Repository MUST return the Ids of the policies applied to the object. Defaults to FALSE.

Output Parameter or each object: <Array> Policies: A collection of the policy objects.

2.2.1.2.4 RenditionsDescription: Used to retrieve the renditions of the object(s).

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 78 of 240

310031013102

310331043105310631073108310931103111311231133114

311531163117

31183119312031213122312331243125312631273128312931303131

3132313331343135313631373138

31393140

232233234

Page 79: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Optional Input Parameter: String renditionFilter: The Repository MUST return the set of renditions whose kind matches

this filter. See section below for the filter grammar. o Defaults to “cmis:none”.

Output Parameter for each object: <Array> Renditions: The set of renditions.

2.2.1.2.4.1 Rendition Filter GrammarThe Rendition Filter grammar is defined as follows:

<renditionInclusion> ::= <none> | <wildcard> | <termlist><termlist> ::= <term> | <term> ',' <termlist><term> ::= <kind> | <mimetype><kind> ::= <text><mimetype> ::= <type> '/' <subtype><type> ::= <text><subtype> ::= <text> | <wildcard><text> ::= /* any char except whitespace */<wildcard> ::= '*'<none> ::= 'cmis:none'

An inclusion pattern allows: Wildcard : include all associated Renditions Comma-separated list of Rendition kinds or mimetypes : include only those Renditions

that match one of the specified kinds or mimetypes cmis:none: (Default) exclude all associated Renditions

Examples: * (include all Renditions) cmis:thumbnail (include only Thumbnails)

Image/* (include all image Renditions) application/pdf, application/x-shockwave-flash (include web ready Renditions) cmis:none (exclude all Renditions)

2.2.1.2.5 ACLsDescription: Used to retrieve the ACLs for the object(s) described in the service response. Optional Input Parameter:

Boolean includeACL: If TRUE, then the Repository MUST return the ACLs for each object in the result set. Defaults to FALSE.

Output Parameter for each object: <Array> ACLs: The list of access control entries of the ACL for the object.

2.2.1.2.6 Allowable ActionsDescription: Used to retrieve the allowable actions for the object(s) described in the service response.Optional Input Parameter:

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 79 of 240

314131423143314431453146

314731483149315031513152315331543155315631573158

31593160316131623163316431653166316731683169

3170317131723173317431753176

317731783179

235236237

Page 80: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Boolean includeAllowableActions: If TRUE, then the Repository MUST return the available actions for each object in the result set. Defaults to FALSE.

Output Parameter for each object: AllowableActions: See cmisAllowableActionsType in the CMIS schema.

2.2.1.3 Change TokensThe CMIS base object-type definitions include an opaque string “ChangeToken” property that a Repository MAY use for optimistic locking and/or concurrency checking to ensure that user updates do not conflict. If a Repository provides values for the ChangeLogTokenChangeToken property for an Object, then all invocations of the “update” methods on that object (updateProperties, setContentStream, deleteContentStream) MUST provide the value of the changeLogTokenchangeToken property as an input parameter, and the Repository MUST throw an updateConflictException if the value specified for the changeLogTokenchangeToken does NOT match the changeLogTokenchangeToken value for the object being updated.

2.2.1.4 ExceptionsThe following sections list the complete set of exceptions that MAY be returned by a repository in response to a CMIS service method call.

2.2.1.4.1 General Exceptions The following exceptions MAY be returned by a repository in response to ANY CMIS service method call.The “Cause” field indicates the circumstances under which a repository SHOULD return a particular exception.

invalidArgumentCause: One or more of the input parameters to the service method is missing or invalid.

objectNotFoundCause: The service call has specified an object that does not exist in the Repository.

notSupportedCause: The service method invoked requires an optional capability not supported by the

repository.

permissionDeniedCause: The caller of the service method does not have sufficient permissions to perform the

operation.

runtimeCause: Any other cause not expressible by another CMIS exception.

2.2.1.4.2 Specific ExceptionsThe following exceptions MAY be returned by a repositiory in response to one or more CMIS service methods calls. For each exception, the general intent is listed as well as a list of the methods which MAY cause the exception to be thrown.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 80 of 240

3180318131823183

3184318531863187318831893190319131923193

319431953196

31973198319932003201

3202

32033204

3205

32063207

32083209

32103211

32123213

32143215

3216

32173218321932203221

238239240

Page 81: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

constraintIntent: The operation violates a Repository- or Object-level constraint defined in the CMIS

domain model.Methods:

Navigation Services:o getObjectParents

Object Services:o createDocument

o createDocumentFromSource

o createFolder

o createRelationship

o createPolicy

o updateProperties

o moveObject

o deleteObject

o setContentStream

o deleteContentStream

Multi-filing Services:o addObjectToFolder

Versioning Services:o checkOut

o cancelCheckOut

o checkIn

Policy Services:o applyPolicy

o removePolicy

Change Log Services:o getContentChanges

contentAlreadyExists Intent: The operation attempts to set the content stream for a Document that already has a

content stream without explicitly specifying the “overwriteFlag” parameter.Methods:

Object Services:o setContentStream

filterNotValid Intent: The property filter or rendition filter input to the operation is not valid.Methods:

Navigation Services:o getDescendants

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 81 of 240

3222

32233224322532263227322832293230323132323233323432353236323732383239324032413242324332443245324632473248324932503251

3252325332543255325632573258

3259326032613262

241242243

Page 82: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

o getChildren

o getFolderParent

o getObjectParents

o getCheckedOutDocs

Object Services:o getProperties

o getRenditions

o getObject

o getObjectByPath

Versioning Services:o getPropertiesOfLatestVersion

o getAllVersions

Policy Services:o getAppliedPolicies

nameConstraintViolation Intent: The repository is not able to store the object that the user is creating/updating due to

a name constraint violation.Methods:

Object Services:o createDocument

o createDocumentFromSource

o createFolder

o createRelationship

o createPolicy

o updateProperties

o moveObject

storage Intent: The repository is not able to store the object that the user is creating/updating due to

an internal storage problem.Methods:

Object Services:o createDocument

o createDocumentFromSource

o createFolder

o createRelationship

o createPolicy

o updateProperties

o moveObject

o setContentStream

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 82 of 240

3263326432653266326732683269327032713272327332743275327632773278

3279328032813282328332843285328632873288328932903291

329232933294329532963297329832993300330133023303

244245246

Page 83: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

o deleteContentStream

Versioning Services:o checkOut

o checkIn

streamNotSupported Intent: The operation is attempting to get or set a contentStream for a Document whose

Object-type specifies that a content stream is not allowed for Document’s of that type.Methods:

Object Services:o createDocument

o createDocumentFromSource

o getContentStream

o setContentStream

Versioning Services:o checkIn

updateConflict Intent: The operation is attempting to update an object that is no longer current (as

determined by the repository).Methods:

Object Services:o updateProperties

o moveObject

o deleteObject

o deleteTree

o setContentStream

o deleteContentStream

Versioning Services:o checkOut

o cancelCheckOut

o checkIn

versioning Intent: The operation is attempting to perform an action on a non-current version of a

Document that cannot be performed on a non-current version.Methods:

Object Services:o updateProperties

o moveObject

o setContentStream

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 83 of 240

330433053306330733083309

331033113312331333143315331633173318331933203321

3322332333243325332633273328332933303331333233333334333533363337

3338333933403341334233433344

247248249

Page 84: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

o deleteContentStream

Versioning Services:o checkOut

o cancelCheckOut

o checkIn

2.2.1.5 ACLsThose services which allow for the setting of ACLs may take the optional macro cmis:user which allows the caller to indicate the operation applies to the current authenticated user.

2.2.2 Repository ServicesThe Repository Services (getRepositories, getRepositoryInfo, getTypeChildren, getTypeDescendants, getTypeDefinition) are used to discover information about the repository, including information about the repository and the object-types defined for the repository.

2.2.2.1 getRepositoriesDescription: Returns a list of CMIS repositories available from this CMIS service endpoint.

2.2.2.1.1 InputsNone.

2.2.2.1.2 OutputsA list of repository information, with (at least) the following information for each entry:

ID repositoryId: The identifier for the Repository. String repositoryName: A display name for the Repository.

2.2.2.1.3 Exceptions Thrown & ConditionsSee section 2.2.1.4.1 General Exceptions

2.2.2.2 getRepositoryInfoDescription: Returns information about the CMIS repository, the optional capabilities it supports and its Access Control information if applicable. .

2.2.2.2.1 InputsRequired:

ID repositoryId: The identifier for the Repository.

2.2.2.2.2 Outputs ID repositoryId: The identifier for the Repository.

o Note: This MUST be the same identifier as the input to the method.

String repositoryName: A display name for the Repository.

String repositoryDescription: A display description for the Repository.

String vendorName: A display name for the vendor of the Repository’s underlying application.

String productName: A display name for the Repository’s underlying application.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 84 of 240

33453346334733483349

335033513352

3353335433553356

33573358

33593360

3361336233633364

33653366

336733683369

337033713372

3373337433753376337733783379

250251252

Page 85: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

String productVersion: A display name for the version number of the Repository’s underlying application.

ID rootFolderId: The ID of the Root Folder Object for the Repository.

<List of capabilities>: The set of values for the repository-optional capabilities specified in section 2.1.1.1 Optional Capabilities

String latestChangeLogToken: The change log token corresponding to the most recent change event for any object in the repository.

DecimalString cmisVersionSupported: A decimal that indicates what version of the CMIS specification this repository supports as specified in 2.1.1.2 Implementation Information.

URI thinClientURI: A optional repository-specific URI pointing to the repository’s web interface.

Boolean changesIncomplete: Indicates whether or not the repository’s change log can return all changes ever made to any object in the repository or only changes made after a particular point in time. Applicable when the repository’s optional capability capabilityChanges is not none.

o If FALSE, then the change log can return all changes ever made to every object.

o If TRUE, then the change log includes all changes made since a particular point in time, but not all changes ever made.

<List of enum values> changesOnType: Indicates whether changes are available for base types in the repository. Valid values are from enumBaseObjectTypeIds. See section 2.1.11 Change Log.

o cmis:document

o cmis:folder

o cmis:policy

o cmis:relationship

Enum supportedPermissions: specifies which types of permissions are supported.

o basic: indicates that the CMIS Basic permissions are supported.

o repository: Indicates that repository specific permissions are supported.

o both: indicates that both CMIS basic permissions and repository specific permissions are supported.

Enum propagation: The list of allowed values for applyACL, which control how non-direct ACEs are handled by the repository:

o objectonly: indicates that the repository is able to apply ACEs without changing the ACLs of other objects – i.e. ACEs are applied, potentially “breaking” the “sharing” dependency for non-direct ACEs.

o propagate: indicates that the repository is able to apply ACEs to a given object and propagate this change to all inheriting objects – i.e. ACEs are applied with the (intended) side effect to inheriting objects.

o repositorydetermined: indicates that the repository uses its own mechanisms to handle non-direct ACEs when applying ACLs.

<Array> Permission permissions: The list of repository-specific permissions the repository supports for managing ACEs (see section 2.8 Access Control).

<Array> PermissionMapping mapping: The list of mappings for the CMIS Basic permissions to allowable actions (see section 2.8 Access Control).

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 85 of 240

33803381338233833384338533863387338833893390339133923393339433953396339733983399340034013402340334043405340634073408340934103411341234133414341534163417341834193420342134223423

253254255

Page 86: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

String principalAnonymous: If set, this field holds the principal who is used for anonymous access. This principal can then be passed to the ACL services to specify what permissions anonymous users should have.

String principalAnyone: If set, this field holds the principal who is used to indicate any authenticated user. This principal can then be passed to the ACL services to specify what permissions any authenticated user should have.

The cmisRepositoryInfoType schema describes the markup that will be included in all CMIS protocol bindings to implement this service.

2.2.2.2.3 Exceptions Thrown & ConditionsSee section 2.2.1.4.1 General Exceptions

2.2.2.3 getTypeChildrenDescription: Returns the list of Object-Types defined for the Repository that are children of the specified Type.

2.2.2.3.1 InputsRequired:

String repositoryId: The identifier for the Repository.Optional:

String typeId: The typeId of an Object-Type specified in the Repository.o If specified, then the Repository MUST return all of child types of the specified type.

o If not specified, then the Repository MUST return all Base Object-Types.

Boolean includePropertyDefinitions: If TRUE, then the Repository MUST return the property definitions for each Object-Type returned.

o If FALSE (default), the Repository MUST return only the attributes for each Object-Type.

Integer maxItems: See section 2.2.1.1 Paging. Integer skipCount: See section 2.2.1.1 Paging.

2.2.2.3.2 Outputs<Array> Object-Types: The list of child Object-Types defined for the given typeId.Boolean hasMoreItems: See section 2.2.1.1 Paging.

Optional: Integer numItems: See section 2.2.1.1 Paging.

2.2.2.3.3 Exceptions Thrown & ConditionsSee section 2.2.1.4.1 General Exceptions

2.2.2.4 getTypeDescendantsDescription: Returns the set of descendant Object-Types defined for the Repository under the specified Type.Notes:

This method does NOT support paging as defined in the 2.2.1.1 Paging section. The order in which results are returned is respository-specific.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 86 of 240

34243425342634273428342934303431

34323433

343434353436

343734383439344034413442344334443445344634473448

34493450345134523453

34543455

345634573458345934603461

256257258

Page 87: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

2.2.2.4.1 InputsRequired:

String repositoryId: The identifier for the Repository.Optional:

String typeId: The typeId of an Object-Type specified in the Repository.o If specified, then the Repository MUST return all descendant types for the specified type.

o If not specified, then the Repository MUST return all types and MUST ignore the value of the depth parameter

Integer depth: The number of levels of depth in the type hierarchy from which to return results. Valid values are:

o 1: Return only types that are children of the type.

o <Integer value greater than 1>: Return only types that are children of the type and descendants up to <value> levels deep.

o -1: Return ALL descendant types at all depth levels in the CMIS hierarchy.

o The default value is repository specific and SHOULD be at least 2 or -1.

Boolean includePropertyDefinitions: If TRUE, then the Repository MUST return the property definitions for each Object-Type returned.

o If FALSE (default), the Repository MUST return only the attributes for each Object-Type.

2.2.2.4.2 Outputs<Array> Object-Types: The hierarchy of Object-Types defined for the Repository.

2.2.2.4.3 Exceptions Thrown & ConditionsSee section 2.2.1.4.1 General Exceptions

invalidArgument: The Repository MUST throw this exception if the service is invoked with an invalid depth.

2.2.2.5 getTypeDefinitionDescription: Gets the definition of the specified Object-Type.Inputs

2.2.2.5.1 InputsRequired:

String repositoryId: The identifier for the Repository. String typeId: The typeId of an Object-Type specified in the Repository.

2.2.2.5.2 Outputs Object-type including all property definitions. See section 2.1.3.3 (Object-Type Property

Definitions) for further details.

2.2.2.5.3 Exceptions Thrown & ConditionsSee section 2.2.1.4.1 General Exceptions

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 87 of 240

346234633464346534663467346834693470347134723473347434753476347734783479

34803481

3482348334843485

34863487

3488348934903491

349234933494

34953496

259260261

Page 88: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

2.2.3 Navigation Services The Navigation Services (getDescendants, getChildren, getFolderParent, getObjectParents, getCheckedoutDocs), are used to traverse the folder hierarchy in a CMIS Repository, and to locate Documents that are checked out.

2.2.3.1 getChildrenDescription: Gets the list of child objects contained in the specified folder. Notes:

If the Repository supports the optional “VersionSpecificFiling” capability, then the repository MUST return the document versions filed in the specified folder.

o Otherwise, the latest version of the documents MUST be returned.

2.2.3.1.1 InputsRequired:

ID repositoryId: The identifier for the Repository. ID folderId: The identifier for the folder.

Optional: Integer maxItems: See section 2.2.1.1 Paging. Integer skipCount: See section 2.2.1.1 Paging. String orderBy: See ORDER BY Clause in the query String orderBy: The orderBy parameter MUST be a comma-separated list of query names and

the ascending modifier “ASC” or the descending modifier “DESC” for each query name. A repository's handling of the orderBy input is repository-specific.

String filter: See Error: Reference source not foundsection 2.2.1.2.1 Properties. The service will only return the properties in the matched object if they exist on the matched object type definition and in the filter.

Enum includeRelationships: See section 2.2.1.2.2 Relationships. String renditionFilter: See section 2.2.1.2.4 Renditions. Boolean includeAllowableActions: See section 2.2.1.2.6 Allowable Actions. Boolean includePathSegment: Defaults to FALSE. If TRUE, returns a PathSegment for each

child object for use in constructing that object’s path.

2.2.3.1.2 Outputs <Array> ObjectResults: A list of the child objects for the specified folder. Each object result

MUST include the following elements if they are requested:o <Array> Properties: The list of properties for the object.

o <Array> Relationships: See section 2.2.1.2.2 Relationships.

o <Array> Renditions: See section 2.2.1.2.4 Renditions.

o AllowableActions: See section 2.2.1.2.6 Allowable Actions.

o String PathSegment: If includePathSegment was TRUE. See section 2.1.5.3 Paths.

Boolean hasMoreItems: See section 2.2.1.1 Paging.Optional:

Integer numItems: See section 2.2.1.1 Paging.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 88 of 240

3497349834993500

350135023503350435053506

3507350835093510351135123513351435153516351735183519352035213522352335243525

35263527352835293530353135323533353435353536

262263264

Page 89: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

2.2.3.1.3 Exceptions Thrown & Conditions See section 2.2.1.4.1 General Exceptions filterNotValid: The Repository MUST throw this exception if this property filter input

parameter is not valid. invalidArgument: if the specified folder is not a folder

2.2.3.2 getDescendantsDescription: Gets the set of descendant objects contained in the specified folder or any of its child-folders.Notes:

This method does NOT support paging as defined in the 2.2.1.1 Paging section. The order in which results are returned is respository-specific.. If the Repository supports the optional capability capabilityVersionSpecificFiling, then

the repository MUST return the document versions filed in the specified folder or its descendant folders. Otherwise, the latest version of the documents MUST be returned.

If the Repository supports the optional capability capabilityMutlifiling and the same document is encountered multiple times in the hierarchy, then the repository MUST return that document each time is encountered.

2.2.3.2.1 InputsRequired:

ID repositoryId: The identifier for the Repository. ID folderId: The identifier for the folder.

Optional: Integer depth: The number of levels of depth in the folder hierarchy from which to return results.

Valid values are:o 1: Return only objects that are children of the folder.

o <Integer value greater than 1>: Return only objects that are children of the folder and descendants up to <value> levels deep.

o -1: Return ALL descendant objects at all depth levels in the CMIS hierarchy.

o The default value is repository specific and SHOULD be at least 2 or -1

String filter: See section 2.2.1.2.1 Properties. Enum includeRelationships: See section 2.2.1.2.2 Relationships. String renditionFilter: See section 2.2.1.2.4 Renditions. Boolean includeAllowableActions: See section 2.2.1.2.6 Allowable Actions. Boolean includePathSegment: Defaults to FALSE. If TRUE, returns a PathSegment for each

child object for use in constructing that object’s path.

2.2.3.2.2 Outputs <Array> ObjectResults: A list of the descendant objects for the specified folder. Each object

result MUST include the following elements if they are requested:o <Array> Properties: The list of properties for the object.

o <Array> Relationships: See section 2.2.1.2.2 Relationships.

o <Array> Renditions: See section 2.2.1.2.4 Renditions.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 89 of 240

35373538353935403541

354235433544354535463547354835493550355135523553

355435553556355735583559356035613562356335643565356635673568356935703571

357235733574357535763577

265266267

Page 90: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

o AllowableActions: See section 2.2.1.2.6 Allowable Actions.

o String PathSegment: If includePathSegment was TRUE. See section 2.1.5.3 Paths.

2.2.3.2.3 Exceptions Thrown & ConditionsSee section 2.2.1.4.1 General Exceptions filterNotValid: The Repository MUST throw this exception if this property filter input

parameter is not valid. invalidArgument: The Repository MUST throw this exception if the service is invoked with

“depth = 0”. invalidArgument: if the specified folder is not a folder

2.2.3.3 getFolderTreeDescription: Gets the set of descendant folder objects contained in the specified folder.

Notes: This method does NOT support paging as defined in the 2.2.1.1 Paging section. The order in which results are returned is respository-specific..

2.2.3.3.1 InputsRequired:

ID repositoryId: The identifier for the Repository. ID folderId: The identifier for the folder.

Optional: Integer depth: The number of levels of depth in the folder hierarchy from which to return results.

Valid values are:o 1: Return only folders that are children of the folder.

o <Integer value greater than 1>: Return only folders that are children of the folder and descendant folders up to <value> levels deep.

o -1: Return ALL descendant folders at all depth levels in the CMIS hierarchy.

o The default value is repository specific and SHOULD be at least 2 or -1

String filter: See section 2.2.1.2.1 Properties. Enum includeRelationships: See section 2.2.1.2.2 Relationships. String renditionFilter: See section 2.2.1.2.4 Renditions. Boolean includeAllowableActions: See section 2.2.1.2.6 Allowable Actions. Boolean includePathSegment: Defaults to FALSE. If TRUE, returns a PathSegment for each

child object for use in constructing that object’s path.

2.2.3.3.2 Outputs <Array> ObjectResults: A list of the descendant folders for the specified folder. Each object

result MUST include the following elements if they are requested:o <Array> Properties: The list of properties for the object.

o <Array> Relationships: See section 2.2.1.2.2 Relationships.

o <Array> Renditions: See section 2.2.1.2.4 Renditions.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 90 of 240

35783579

3580358135823583358435853586

35873588

3589359035913592

359335943595359635973598359936003601360236033604360536063607360836093610

361136123613361436153616

268269270

Page 91: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

o AllowableActions: See section 2.2.1.2.6 Allowable Actions.

o String pathSegment: If includePathSegment was TRUE. See section 2.1.5.3 Paths.

2.2.3.3.3 Exceptions Thrown & Conditions See section 2.2.1.4.1 General Exceptions filterNotValid: The Repository MUST throw this exception if this property filter input

parameter is not valid. invalidArgument: The Repository MUST throw this exception if the service is invoked with

an invalid depth invalidArgument: if the specified folder is not a folder

2.2.3.4 getFolderParentDescription: Gets the parent folder object for the specified folder object.

2.2.3.4.1 InputsRequired:

ID repositoryId: The identifier for the Repository. ID folderId: The identifier for the folder.

Optional: String filter: See section 2.2.1.2.1 Properties.Error: Reference source not found.

2.2.3.4.2 Outputs Object: The parent folder object of the specified folder.

2.2.3.4.3 Exceptions Thrown & Conditions See section 2.2.1.4.1 General Exceptions filterNotValid: The Repository MUST throw this exception if this property filter input

parameter is not valid. invalidArgument: The Repository MUST throw this exception if the folderId input is the root

folder.

2.2.3.5 getObjectParentsDescription: Gets the parent folder(s) for the specified non-folder, fileable object.

2.2.3.5.1 InputsRequired:

ID repositoryId: The identifier for the Repository. ID objectId: The identifier for the object.

Optional: String filter: See section 2.2.1.2.1 Properties Enum includeRelationships: See section 2.2.1.2.2 Relationships. String renditionFilter: See section 2.2.1.2.4 Renditions.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 91 of 240

36173618

361936203621362236233624362536263627

36283629

363036313632363336343635

36363637

363836393640364136423643

36443645

36463647364836493650365136523653

271272273

Page 92: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Boolean includeAllowableActions: See section 2.2.1.2.6 Allowable Actions. Boolean includeRelativePathSegment: See section 2.1.5.3 Paths.

2.2.3.5.2 Outputs <Array> ObjectResults: A list of the parent folder(s) of the specified objects. Empty for unfiled

objects or for the root folder. Each object result MUST include the following elements if they are requested:

o <Array> Properties: The list of properties for the object.

o <Array> Relationships: See section 2.2.1.2.2 Relationships.

o <Array> Renditions: See section 2.2.1.2.4 Renditions.

o AllowableActions: See section 2.2.1.2.6 Allowable Actions.

o String relativePathSegment: If includeRelativePathSegment was TRUE. See section 2.1.5.3 Paths.

2.2.3.5.3 Exceptions Thrown & Conditions See section 2.2.1.4.1 General Exceptions constraint: The Repository MUST throw this exception if this method is invoked on an object

who Object-Type Definition specifies that it is not fileable. filterNotValid: The Repository MUST throw this exception if this property filter input

parameter is not valid. invalidArgument: if the specified folder is not a folder

2.2.3.6 getCheckedOutDocsDescription: Gets the list of documents that are checked out that the user has access to.

2.2.3.6.1 InputsRequired:

ID repositoryId: The identifier for the Repository.Optional:

ID folderId: The identifier for a folder in the repository from which documents should be returned.o If specified, the Repository MUST only return checked out documents that are child-

objects of the specified folder.o If not specified, the Repository MUST return checked out documents from anywhere in

the repository hierarchy. Integer maxItems: See section 2.2.1.1 Paging. Integer skipCount: See section 2.2.1.1 Paging. String orderBy: See ORDER BY Clause in the query String orderBy: The orderBy parameter MUST be a comma-separated list of query names and

the ascending modifier “ASC” or the descending modifier “DESC” for each query name. A repository's handling of the orderBy input is repository-specific.

String filter: See section 2.2.1.2.1 Properties. Enum includeRelationships: See section 2.2.1.2.2 Relationships. String renditionFilter: See section 2.2.1.2.4 Renditions. Boolean includeAllowableActions: See section 2.2.1.2.6 Allowable Actions.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 92 of 240

36543655

3656365736583659366036613662366336643665

3666366736683669367036713672

36733674

3675367636773678367936803681368236833684368536863687368836893690369136923693

274275276

Page 93: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

2.2.3.6.2 Outputs <Array> ObjectResults: A list of checked out documents. Each object result MUST include the

following elements if they are requested:o <Array> Properties: The list of properties for the object.

o <Array> Relationships: See section 2.2.1.2.2 Relationships.

o <Array> Renditions: See section 2.2.1.2.4 Renditions.

o AllowableActions: See section 2.2.1.2.6 Allowable Actions.

Boolean hasMoreItems: See section 2.2.1.1 Paging.Optional:

Integer numItems: See section 2.2.1.1 Paging.

2.2.3.6.3 Exceptions Thrown & Conditions See section 2.2.1.4.1 General Exceptions filterNotValid: The Repository MUST throw this exception if this property filter input

parameter is not valid.

2.2.4 Object ServicesCMIS provides ID-based CRUD (Create, Retrieve, Update, Delete), operations on objects in a Repository.

2.2.4.1 createDocumentDescription: Creates a document object of the specified type (given by the cmis:objectTypeId property) in the (optionally) specified location.

2.2.4.1.1 InputsRequired:

ID repositoryId: The identifier for the Repository. <Array> properties: The property values that MUST be applied to the newly-created Document

Object.Optional:

ID folderId: If specified, the identifier for the folder that MUST be the parent folder for the newly-created Document Object.

o This parameter MUST be specified if the Repository does NOT support the optional “unfiling” capability.

<contentStream> contentStream: The Content Stream that MUST be stored for the newly-created Document Object. The method of passing the contentStream to the server and the encoding mechanism will be specified by each specific binding. MUST be required if the type requires it.

Enum versioningState: An enumeration specifying what the versioing state of the newly-created object MUST be. If the repository does not support versioning, the repository MUST ignore the versioningState parameter. Valid values are:

o none: The document MUST be created as a non-versionable document.

o checkedout: The document MUST be created in the checked-out state.

o major (default): The document MUST be created as a major version

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 93 of 240

3694369536963697369836993700370137023703

3704

3705370637073708

37093710

371137123713

37143715371637173718371937203721372237233724372537263727372837293730373137323733

277278279

Page 94: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

o minor: The document MUST be created as a minor version.

<Array> policies: A list of policy IDs that MUST be applied to the newly-created Document object.

<Array> ACE addACEs: A list of ACEs that MUST be added to the newly-created Document object, either using the ACL from folderId if specified, or being applied if no folderId is specified.

<Array> ACE removeACEs: A list of ACEs that MUST be removed from the newly-created Document object, either using the ACL from folderId if specified, or being ignored if no folderId is specified.

2.2.4.1.2 OutputsID objectId: The ID of the newly-created document.

2.2.4.1.3 Exceptions Thrown & Conditions See section 2.2.1.4.1 General Exceptions constraint: The Repository MUST throw this exception if ANY of the following conditions are

met:o The cmis:objectTypeId property value is not an Object-Type whose baseType is

“Document”.o The cmis:objectTypeId property value is NOT in the list of AllowedChildObjectTypeIds of

the parent-folder specified by folderId. o The value of any of the properties violates the min/max/required/length constraints

specified in the property definition in the Object-Type.o The “contentStreamAllowed” attribute of the Object-Type definition specified by the

cmis:objectTypeId property value is set to “required” and no contentStream input parameter is provided.

o The “versionable” attribute of the Object-Type definition specified by the cmis:objectTypeId property value is set to FALSE and a value for the versioningState input parameter is provided that is something other than “none”.

o The “versionable” attribute of the Object-Type definition specified by the cmis:objectTypeId property value is set to TRUE and the value for the versioningState input parameter is provided that is “none”.

o The “controllablePolicy” attribute of the Object-Type definition specified by the cmis:objectTypeId property value is set to FALSE and at least one policy is provided.

o The “controllableACL” attribute of the Object-Type definition specified by the cmis:objectTypeId property value is set to FALSE and at least one ACE is provided.

o At least one of the permissions is used in an ACE provided which is not supported by the repository.

nameConstraintViolation: See section 2.2.1.4.2 Specific Exceptions. If the repository detects a violation with the given cmis:name property value, the repository MAY throw this exception or chose a name which does not conflict.

storage: See section 2.2.1.4.2 Specific Exceptions.

streamNotSupported: The Repository MUST throw this exception if the “contentStreamAllowed” attribute of the Object-Type definition specified by the cmis:objectTypeId property value is set to “not allowed” and a contentStream input parameter is provided.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 94 of 240

37343735373637373738373937403741

37423743

37443745374637473748374937503751375237533754375537563757375837593760376137623763376437653766376737683769377037713772377337743775

280281282

Page 95: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

2.2.4.2 createDocumentFromSourceDescription: Creates a document object as a copy of the given source document in the (optionally) specified location.

2.2.4.2.1 InputsRequired:

ID repositoryId: The identifier for the Repository. ID sourceId: The identifier for the source document.

Optional: <Array> properties: The property values that MUST be applied to the Object. This list of

properties SHOULD only contain properties whose values differ from the source document. ID folderId: If specified, the identifier for the folder that MUST be the parent folder for the newly-

created Document Object.o This parameter MUST be specified if the Repository does NOT support the optional

“unfiling” capability. Enum versioningState: An enumeration specifying what the versioing state of the newly-created

object MUST be. Valid values are:o none: The document MUST be created as a non-versionable document.

o checkedout: The document MUST be created in the checked-out state.

o major (default): The document MUST be created as a major version

o minor: The document MUST be created as a minor version.

<Array> policies: A list of policy IDs that MUST be applied to the newly-created Document object.

<Array> ACE addACEs: A list of ACEs that MUST be added to the newly-created Document object, either using the ACL from folderId if specified, or being applied if no folderId is specified.

<Array> ACE removeACEs: A list of ACEs that MUST be removed from the newly-created Document object, either using the ACL from folderId if specified, or being ignored if no folderId is specified.

2.2.4.2.2 OutputsID objectId: The ID of the newly-created document.

2.2.4.2.3 Exceptions Thrown & Conditions See section 2.2.1.4.1 General Exceptions constraint: The Repository MUST throw this exception if ANY of the following conditions are

met:o The sourceId is not an Object whose baseType is “Document”.

o The source document’s cmis:objectTypeId property value is NOT in the list of AllowedChildObjectTypeIds of the parent-folder specified by folderId.

o The “versionable” attribute of the Object-Type definition specified by the cmis:objectTypeId property value is set to FALSE and a value for the versioningState input parameter is provided that is something other than “none”.

o The “versionable” attribute of the Object-Type definition specified by the cmis:objectTypeId property value is set to TRUE and the value for the versioningState input parameter is provided that is “none”.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 95 of 240

377637773778

377937803781378237833784378537863787378837893790379137923793379437953796379737983799380038013802

38033804

3805380638073808380938103811381238133814381538163817

283284285

Page 96: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

o The “controllablePolicy” attribute of the Object-Type definition specified by the cmis:objectTypeId property value is set to FALSE and at least one policy is provided.

o The “controllableACL” attribute of the Object-Type definition specified by the cmis:objectTypeId property value is set to FALSE and at least one ACE is provided.

o At least one of the permissions is used in an ACE provided which is not supported by the repository.

nameConstraintViolation: See section 2.2.1.4.2 Specific Exceptions. If the repository detects a violation with the given cmis:name property value, the repository MAY throw this exception or chose a name which does not conflict.

storage: See section 2.2.1.4.2 Specific Exceptions.

streamNotSupported: The Repository MUST throw this exception if the “contentStreamAllowed” attribute of the Object-Type definition specified by the cmis:objectTypeId property value is set to “not allowed” and a contentStream input parameter is provided.

2.2.4.3 createFolderDescription: Creates a folder object of the specified type in the specified location.

2.2.4.3.1 InputsRequired:

ID repositoryId: The identifier for the Repository. <Array> properties: The property values that MUST be applied to the newly-created Folder

Object. ID folderId: The identifier for the folder that MUST be the parent folder for the newly-created

Folder Object.Optional:

<Array> policies: A list of policy IDs that MUST be applied to the newly-created Folder object. <Array> ACE addACEs: A list of ACEs that MUST be added to the newly-created Folder object,

either using the ACL from folderId if specified, or being applied if no folderId is specified. <Array> ACE removeACEs: A list of ACEs that MUST be removed from the newly-created

Folder object, either using the ACL from folderId if specified, or being ignored if no folderId is specified.

2.2.4.3.2 Outputs ID objectId: The ID of the newly-created folder.

2.2.4.3.3 Exceptions Thrown & Conditions See section 2.2.1.4.1 General Exceptions constraint: The Repository MUST throw this exception if ANY of the following conditions are

met:o The cmis:objectTypeId property value is not an Object-Type whose baseType is “Folder”.

o The value of any of the properties violates the min/max/required/length constraints specified in the property definition in the Object-Type.

o The cmis:objectTypeId property value is NOT in the list of AllowedChildObjectTypeIds of the parent-folder specified by folderId.

o The “controllablePolicy” attribute of the Object-Type definition specified by the cmis:objectTypeId property value is set to FALSE and at least one policy is provided.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 96 of 240

3818381938203821382238233824382538263827382838293830

38313832

38333834383538363837383838393840384138423843384438453846

38473848

38493850385138523853385438553856385738583859

286287288

Page 97: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

o The “controllableACL” attribute of the Object-Type definition specified by the cmis:objectTypeId property value is set to FALSE and at least one ACE is provided.

o At least one of the permissions is used in an ACE provided which is not supported by the repository.

nameConstraintViolation: See section 2.2.1.4.2 Specific Exceptions. If the repository detects a violation with the given cmis:name property value, the repository MAY throw this exception or chose a name which does not conflict.

storage: See section 2.2.1.4.2 Specific Exceptions.

2.2.4.4 createRelationshipDescription: Creates a relationship object of the specified type

2.2.4.4.1 InputsRequired:

ID repositoryId: The identifier for the Repository. <Array> properties: The property values that MUST be applied to the newly-created

Relationship Object.Optional:

<Array> policies: A list of policy IDs that MUST be applied to the newly-created Replationship object.

<Array> ACE addACEs: A list of ACEs that MUST be added to the newly-created Relationship object, either using the ACL from folderId if specified, or being applied if no folderId is specified. <Array> ACE removeACEs: A list of ACEs that MUST be removed from the newly-created Relationship object, either using the ACL from folderId if specified, or being ignored if no folderId is specified.

2.2.4.4.2 Outputs ID objectId: The ID of the newly-created relationship.

2.2.4.4.3 Exceptions Thrown & Conditions See section 2.2.1.4.1 General Exceptions constraint: The Repository MUST throw this exception if ANY of the following conditions are

met:o The cmis:objectTypeId property value is not an Object-Type whose baseType is

“Relationship”.o The value of any of the properties violates the min/max/required/length constraints

specified in the property definition in the Object-Type. o The sourceObjectId’s ObjectType is not in the list of “allowedSourceTypes” specified by

the Object-Type definition specified by cmis:objectTypeId property value.o The targetObjectId’s ObjectType is not in the list of “allowedTargetTypes” specified by the

Object-Type definition specified by cmis:objectTypeId property value.o The “controllablePolicy” attribute of the Object-Type definition specified by the

cmis:objectTypeId property value is set to FALSE and at least one policy is provided.o The “controllableACL” attribute of the Object-Type definition specified by the

cmis:objectTypeId property value is set to FALSE and at least one ACE is provided.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 97 of 240

38603861386238633864386538663867

38683869

3870387138723873387438753876387738783879388038813882

38833884

3885388638873888388938903891389238933894389538963897389838993900

289290291

Page 98: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

o At least one of the permissions is used in an ACE provided which is not supported by the repository.

nameConstraintViolation: See section 2.2.1.4.2 Specific Exceptions. If the repository detects a violation with the given cmis:name property value, the repository MAY throw this exception or chose a name which does not conflict.

storage: See section 2.2.1.4.2 Specific Exceptions.

2.2.4.5 createPolicyDescription: Creates a policy object of the specified type

2.2.4.5.1 InputsRequired:

ID repositoryId: The identifier for the Repository. <Array> properties: The property values that MUST be applied to the newly-created Policy

Object.Optional:

ID folderId: If specified, the identifier for the folder that MUST be the parent folder for the newly-created Policy Object.o This parameter MUST be specified if the Repository does NOT support the optional “unfiling”

capability. <Array> policies: A list of policy IDs that MUST be applied to the newly-created Policy object. <Array> ACE addACEs: A list of ACEs that MUST be added to the newly-created Policy object,

either using the ACL from folderId if specified, or being applied if no folderId is specified. <Array> ACE removeACEs: A list of ACEs that MUST be removed from the newly-created Policy

object, either using the ACL from folderId if specified, or being ignored if no folderId is specified.

2.2.4.5.2 Outputs ID objectId: The ID of the newly-created Policy Object.

2.2.4.5.3 Exceptions Thrown & Conditions See section 2.2.1.4.1 General Exceptions constraint: The Repository MUST throw this exception if ANY of the following conditions are

met:o The cmis:objectTypeId property value is not an Object-Type whose baseType is “Policy”.

o The value of any of the properties violates the min/max/required/length constraints specified in the property definition in the Object-Type.

o The cmis:objectTypeId property value is NOT in the list of AllowedChildObjectTypeIds of the parent-folder specified by folderId.

o The “controllablePolicy” attribute of the Object-Type definition specified by the cmis:objectTypeId property value is set to FALSE and at least one policy is provided.

o The “controllableACL” attribute of the Object-Type definition specified by the cmis:objectTypeId property value is set to FALSE and at least one ACE is provided.

o At least one of the permissions is used in an ACE provided which is not supported by the repository.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 98 of 240

390139023903390439053906

39073908

390939103911391239133914391539163917391839193920392139223923

39243925

392639273928392939303931393239333934393539363937393839393940

292293294

Page 99: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

nameConstraintViolation: See section 2.2.1.4.2 Specific Exceptions. If the repository detects a violation with the given cmis:name property value, the repository MAY throw this exception or chose a name which does not conflict.

storage: See section 2.2.1.4.2 Specific Exceptions.

2.2.4.6 getAllowableActions Description: Gets the list of allowable actions for an Object (see section.2.2.1.2.6 Allowable Actions).

2.2.4.6.1 InputsRequired:

ID repositoryId: The identifier for the Repository. ID objectId: The identifier for the object

2.2.4.6.2 Outputs <Array> AllowableActions: see section 2.2.1.2.6 Allowable Actions.

2.2.4.6.3 Exceptions Thrown & ConditionsSee section 2.2.1.4.1 General Exceptions

2.2.4.7 getObjectDescription: Gets the specified information for the Object.

2.2.4.7.1 InputsRequired:

ID repositoryId: The identifier for the Repository. ID objectId: The identifier for the object

Optional: String filter: See Error: Reference source not foundsection 2.2.1.2.1 Properties. Enum includeRelationships: See section 2.2.1.2.2 Relationships. Boolean includePolicyIds: See section 2.2.1.2.3 Policies. String renditionFilter: See section 2.2.1.2.4 Renditions. Boolean includeACL: See section 2.2.1.2.5 ACLs. Boolean includeAllowableActions: See section 2.2.1.2.6 Allowable Actions.

2.2.4.7.2 Outputs<Array> Properties: The list of properties for the object. <Array> Relationships: See section 2.2.1.2.2 Relationships.<Array> Policy Ids: See section 2.2.1.2.3 Policies.<Array> Renditions: See section 2.2.1.2.4 Renditions. <Array> ACLs: See section 2.2.1.2.5 ACLs.AllowableActions: See section 2.2.1.2.6 Allowable Actions.

2.2.4.7.3 Exceptions Thrown & ConditionsSee section 2.2.1.4.1 General Exceptions

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 99 of 240

3941394239433944

39453946

3947394839493950

39513952

39533954

39553956

39573958395939603961396239633964396539663967

3968396939703971397239733974

39753976

295296297

Page 100: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

filterNotValid: The Repository MUST throw this exception if this property filter input parameter is not valid.

2.2.4.8 getPropertiesDescription: Gets the list of properties for an Object.

2.2.4.8.1 InputsRequired:

ID repositoryId: The identifier for the Repository. ID objectId: The identifier for the object

Optional: String filter: See Error: Reference source not foundsection 2.2.1.2.1 Properties.

2.2.4.8.2 Outputs<Array> Properties: The list of properties for the object.

2.2.4.8.3 Exceptions Thrown & ConditionsSee section 2.2.1.4.1 General ExceptionsfilterNotValid: The Repository MUST throw this exception if this property filter input parameter

is not valid.

2.2.4.9 getObjectByPathDescription: Gets the specified object.

2.2.4.9.1 InputsRequired:

ID repositoryId: The identifier for the Repository. String path: The path to the object. See section 2.1.5.3 Paths.

Optional: String filter: See section 2.2.1.2.1 Properties. Boolean includeAllowableActions: See section 2.2.1.2.6 Allowable Actions. Enum includeRelationships: See section 2.2.1.2.2 Relationships. String renditionFilter: See section 2.2.1.2.4 Renditions. Boolean includePolicyIds: See section 2.2.1.2.2 Relationships. Boolean includeACL: See section 2.2.1.2.5 ACLs.

2.2.4.9.2 Outputs<Array> Properties: The list of properties for the object.AllowableActions: See section 2.2.1.2.6 Allowable Actions.

2.2.4.9.3 Exceptions Thrown & Conditions See section 2.2.1.4.1 General ExceptionsfilterNotValid: The Repository MUST throw this exception if this property filter input parameter

is not valid.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 100 of 240

39773978

39793980

398139823983398439853986

39873988

3989399039913992

39933994

39953996399739983999400040014002400340044005

400640074008

4009401040114012

298299300

Page 101: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

2.2.4.10 getContentStreamDescription: Gets the content stream for the specified Document object, or gets a rendition stream for a specified rendition of a document or folder object.Notes: Each CMIS protocol binding MAY provide a way for fetching a sub-range within a content stream, in a manner appropriate to that protocol.

2.2.4.10.1 InputsRequired:

ID repositoryId: The identifier for the Repository. ID objectId: The identifier for the object

Optional: ID streamId: The identifier for the rendition stream, when used to get a rendition stream. For

Documents, if not provided then this method returns the content stream. For Folders, it MUST be provided.

2.2.4.10.2 Outputs <Stream> ContentStream: The specified content stream or rendition stream for the object.

2.2.4.10.3 Exceptions Thrown & Conditions See section 2.2.1.4.1 General Exceptionsconstraint: The Repository MUST throw this exception if the object specified by objectId does

NOT have a content stream or rendition stream.

2.2.4.11 getRenditionsDescription: Gets the list of associated Renditions for the specified object. Only rendition attributes are returned, not rendition stream.Notes: Each CMIS protocol binding MAY provide a way for fetching a sub-range within a content stream, in a manner appropriate to that protocol.

2.2.4.11.1 InputsRequired:

ID repositoryId: The identifier for the Repository. ID objectId: The identifier for the object

Optional: String renditionFilter: See Section 2.2.1.2.4 Integer maxItems: See section 2.2.1.1 Paging. Integer skipCount: See section 2.2.1.1 Paging.

2.2.4.11.2 Outputs <Array> Renditions: The set of renditions available on this object

2.2.4.11.3 Exceptions Thrown & Conditions See section 2.2.1.4.1 General Exceptions notSupported: The service method requires functionality that is not supported by the

repository

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 101 of 240

40134014401540164017

40184019402040214022402340244025

40264027

4028402940304031

40324033403440354036

40374038403940404041404240434044

40454046

4047404840494050

301302303

Page 102: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

filterNotValid : The filter specified is not valid

2.2.4.12 updatePropertiesDescription: Updates properties of the specified object. Notes:

A Repository MAY automatically create new Document versions as part of an update properties operation. Therefore, the objectId output NEED NOT be identical to the objectId input.

Each CMIS protocol bindings MUST specify whether the updateProperties service MUST always include all updatable properties, or only those properties whose values are different than the original value of the object.

2.2.4.12.1 InputsRequired:

ID repositoryId: The identifier for the Repository.ID objectId: The identifier of the object to be updated. <Array> properties: The updated property values that MUST be applied to the Object.

Optional: String changeToken: See section 2.2.1.3 Change Tokens.

2.2.4.12.2 Outputs ID objectId: The ID of the updated object. String changeToken: See section 2.2.1.3 Change Tokens.

2.2.4.12.3 Exceptions Thrown & Conditions See section 2.2.1.4.1 General Exceptions constraint: The Repository MUST throw this exception if the value of any of the properties

violates the min/max/required/length constraints specified in the property definition in the Object-Type.

nameConstraintViolation: See section 2.2.1.4.2 Specific Exceptions. The repository MAY throw this exception or chose a name which does not conflict.

storage: See section 2.2.1.4.2 Specific Exceptions.

updateConflict: See section 2.2.1.4.2 Specific Exceptions.

versioning: The Repository MUST throw this exception if ANY of the following conditions are met:

o The object is not checked out and ANY of the properties being updated are defined in their Object-Type definition have an attribute value of Updatability when checked-out.

o Additionally, the repository MAY throw this exception if the object is a non-current Document Version.

2.2.4.13 moveObjectDescription: Moves the specified file-able object from one folder to another.

2.2.4.13.1 InputsRequired:

ID repositoryId: The identifier for the Repository.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 102 of 240

4051

40524053405440554056405740584059

4060406140624063406440654066

406740684069

407040714072407340744075407640774078407940804081408240834084

40854086

408740884089

304305306

Page 103: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

ID objectId: The identifier of the object to be moved. ID targetFolderId: The folder into which the object is to be moved. ID sourceFolderId: The folder from which the object is to be moved.

2.2.4.13.2 Outputs ID objectId: The identifier of the object to be moved.

2.2.4.13.3 Exceptions Thrown & Conditions See section 2.2.1.4.1 General Exceptions invalidArgument: The Repository MUST throw this exception if the service is invoked with a

missing sourceFolderId or the sourceFolderId doesn’t match the specified object’s parent folder (or one of the parent folders if the repository supports multifiling.).

constraint: The Repository MUST throw this exception if the cmis:objectTypeId property value of the given object is NOT in the list of AllowedChildObjectTypeIds of the parent-folder specified by targetFolderId.

nameConstraintViolation: See section 2.2.1.4.2 Specific Exceptions. The repository MAY throw this exception or chose a name which does not conflict.

storage: See section 2.2.1.4.2 Specific Exceptions.

updateConflict: See section 2.2.1.4.2 Specific Exceptions.

versioning: The repository MAY throw this exception if the object is a non-current Document Version.

2.2.4.14 deleteObjectDescription: Deletes the specified object.

2.2.4.14.1 InputsRequired:

ID repositoryId: The identifier for the Repository. ID objectId: The identifier of the object to be deleted.

Optional: Boolean allVersions: If TRUE (default), then delete all versions of the document. If FALSE,

delete only the document object specified. The Repository MUST ignore the value of this parameter when this service is invoke on a non-document object or non-versionable document object.

2.2.4.14.2 Exceptions Thrown & Conditions See section 2.2.1.4.1 General Exceptions constraint: The Repository MUST throw this exception if the method is invoked on a Folder

object that contains one or more objects. updateConflict: See section 2.2.1.4.2 Specific Exceptions.

2.2.4.15 deleteTreeDescription: Deletes the specified folder object and all of its child- and descendant-objects.Notes:

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 103 of 240

409040914092

40934094

40954096409740984099410041014102410341044105410641074108

41094110

411141124113411441154116411741184119

4120

41214122412341244125

412641274128

307308309

Page 104: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

A Repository MAY attempt to delete child- and descendant-objects of the specified folder in any order.

Any child- or descendant-object that the Repository cannot delete MUST persist in a valid state in the CMIS domain model.

This is not atomic. However, if deletesinglefiled is chosen and some objects fail to delete, then single-filed objects

are either deleted or kept, never just unfiled. This is so that a user can call this command again to recover from the error by using the same tree.

2.2.4.15.1 InputsRequired:

ID repositoryId: The identifier for the Repository. ID folderId: The identifier of the folder to be deleted.

Optional: Boolean allVersions: If TRUE (default), then delete all versions of the document. If FALSE,

delete only the document object specified. The Repository MUST ignore the value of this parameter when this service is invoke on a non-document object or non-versionable document object.

Enum unfileObjects: An enumeration specifying how the repository MUST process file-able child- or descendant-objects. Valid values are:o unfile: Unfile all fileable objects.

o deletesinglefiled: Delete all fileable non-folder objects whose only parent-folders are in the current folder tree. Unfile all other fileable non-folder objects from the current folder tree.

o delete (default): Delete all fileable objects.

boolean continueOnFailure: If TRUE, then the repository SHOULD continue attempting to perform this operation even if deletion of a child- or descendant-object in the specified folder cannot be deleted.o If FALSE (default), then the repository SHOULD abort this method when it fails to delete a

single child- or descendant-object.

2.2.4.15.2 Outputs <Array> ID failedToDelete: A list of identifiers of objects in the folder tree that were not deleted.

2.2.4.15.3 Exceptions Thrown & Conditions See section 2.2.1.4.1 General Exceptions updateConflict: See section 2.2.1.4.2 Specific Exceptions.

2.2.4.16 setContentStreamDescription: Sets the content stream for the specified Document object.Notes: A Repository MAY automatically create new Document versions as part of this service method. Therefore, the obejctId output NEED NOT be identical to the objectId input.

2.2.4.16.1 InputsRequired:

ID repositoryId: The identifier for the Repository. ID objectId: The identifier for the Document object.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 104 of 240

41294130413141324133413441354136

41374138413941404141414241434144414541464147414841494150415141524153415441554156

41574158

415941604161

4162416341644165

4166416741684169

310311312

Page 105: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<contentStream> contentStream: The Content Stream Optional:

Boolean overwriteFlag: If TRUE (default), then the Repository MUST replace the existing content stream for the object (if any) with the input contentStream. o If FALSE, then the Repository MUST only set the input contentStream for the object if the

object currently does not have a content-stream. String changeToken: See section 2.2.1.3 Change Tokens.

2.2.4.16.2 Outputs ID objectId: The ID of the document. String changeToken: See section 2.2.1.3 Change Tokens.

2.2.4.16.3 Exceptions Thrown & Conditions See section 2.2.1.4.1 General Exceptions contentAlreadyExists: The Repository MUST throw this exception if the input parameter

overwriteFlag is FALSE and the Object already has a content-stream. storage: See section 2.2.1.4.2 Specific Exceptions.

streamNotSupported: The Repository MUST throw this exception if the “contentStreamAllowed” attribute of the Object-Type definition specified by the cmis:objectTypeId property value of the given document is set to “notallowed”.

updateConflict: See section 2.2.1.4.2 Specific Exceptions.

versioning: The repository MAY throw this exception if the object is a non-current Document Version.

2.2.4.17 deleteContentStream Description: Deletes the content stream for the specified Document object.Notes: A Repository MAY automatically create new Document versions as part of this service method. Therefore, the objectId output NEED NOT be identical to the objectId input.

2.2.4.17.1 InputsRequired:

ID repositoryId: The identifier for the Repository. ID objectId: The identifier for the Document object.

Optional: String changeToken: See section 2.2.1.3 Change Tokens.

2.2.4.17.2 Outputs ID objectId: The ID of the Document object. String changeToken: See section 2.2.1.3 Change Tokens.

2.2.4.17.3 Exceptions Thrown & Conditions See section 2.2.1.4.1 General Exceptions constraint: The Repository MUST throw this exception if the Object’s Object-Type definition

“contentStreamAllowed” attribute is set to “required”.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 105 of 240

4170417141724173417441754176

417741784179

41804181418241834184418541864187418841894190

4191419241934194

419541964197419841994200

420142024203

4204420542064207

313314315

Page 106: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

storage: See section 2.2.1.4.2 Specific Exceptions.

updateConflict: See section 2.2.1.4.2 Specific Exceptions.

versioning: The repository MAY throw this exception if the object is a non-current Document Version.

2.2.5 Multi-filing ServicesThe Multi-filing services (addObjectToFolder, removeObjectFromFolder) are supported only if the repository supports the multifiling or unfiling optional capabilities. The Multi-filing Services are used to file/un-file objects into/from folders.This service is NOT used to create or delete objects in the repository.

2.2.5.1 addObjectToFolderDescription: Adds an existing fileable non-folder object to a folder.

2.2.5.1.1 InputsRequired:

ID repositoryId: The identifier for the Repository. ID objectId: The identifier of the object. ID folderId: The folder into which the object is to be filed.

Optional: Boolean allVersions: Add all versions of the object to the folder if the repository supports

version-specific filing. Defaults to TRUE.

2.2.5.1.2 Exceptions Thrown & Conditions See section 2.2.1.4.1 General Exceptions. constraint: The Repository MUST throw this exception if the cmis:objectTypeId property value

of the given object is NOT in the list of AllowedChildObjectTypeIds of the parent-folder specified by folderId.

2.2.5.2 removeObjectFromFolderDescription: Removes an existing fileable non-folder object from a folder.

2.2.5.2.1 InputsRequired:

ID repositoryId: The identifier for the Repository. ID objectId: The identifier of the object.

Optional: ID folderId: The folder from which the object is to be removed.

o If no value is specified, then the Repository MUST remove the object from all folders in which it is currently filed.

2.2.5.2.2 Exceptions Thrown & Conditions See section 2.2.1.4.1 General Exceptions

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 106 of 240

4208420942104211

42124213421442154216

42174218

42194220422142224223422442254226

42274228422942304231

42324233

42344235423642374238423942404241

42424243

316317318

Page 107: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

2.2.6 Discovery ServicesThe Discovery Services (query) are used to search for query-able objects within the Repository.

2.2.6.1 queryDescription: Executes a CMIS query statement against the contents of the Repository.

2.2.6.1.1 InputsRequired:

ID repositoryId: The identifier for the Repository. String statement: CMIS query to be executed. (See section 2.1.10 Query.)

Optional: Boolean searchAllVersions:

o If TRUE, then the Repository MUST include latest and non-latest versions of document objects in the query search scope.

o If FALSE (default), then the Repository MUST only include latest versions of documents in the query search scope.

o If the Repository does not support the optional capabilityAllVersionsSearchable capability, then this parameter value MUST be set to FALSE.

Enum includeRelationships: See section 2.2.1.2.2 Relationships.o Note: For query statements where the SELECT clause contains properties from only one

virtual table reference (i.e. referenced object-type), any value for this enum may be used. If the SELECT clause contains properties from more than one table, then the value of this parameter MUST be “none”.

String renditionFilter: See section 2.2.1.2.4 Renditions. Boolean includeAllowableActions: See section 2.2.1.2.6 Allowable Actions.

o Note: For query statements where the SELECT clause contains properties from only one virtual table reference (i.e. referenced object-type), any value for this parameter may be used. If the SELECT clause contains properties from more than one table, then the value of this parameter MUST be “FALSE”.

Integer maxItems: See section 2.2.1.1 Paging. Integer skipCount: See section 2.2.1.1 Paging.

2.2.6.1.2 Outputs <Array> Object QueryResults: The set of results for the query. (See section 2.1.10 Query.).

Each object result MUST include the following elements if they are requested:o <Array> Relationships: See section 2.2.1.2.2 Relationships.

o <Array> Renditions: See section 2.2.1.2.4 Renditions.

o AllowableActions: See section 2.2.1.2.6 Allowable Actions.

Boolean hasMoreItems: See section 2.2.1.1 Paging.Optional:

Integer numItems: See section 2.2.1.1 Paging.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 107 of 240

42444245

42464247

4248424942504251425242534254425542564257425842594260426142624263426442654266426742684269427042714272

427342744275427642774278427942804281

4282

319320321

Page 108: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

2.2.6.1.3 Exceptions Thrown & Conditions See section 2.2.1.4.1 General Exceptions If the select clause includes properties from more than a single type reference, then the

repository SHOULD throw an exception if includeRelationships is something other than “none” or includeAllowableActions is specified as TRUE.

2.2.6.2 getContentChangesDescription: Gets a list of content changes. This service is intended to be used by search crawlers or other applications that need to efficiently understand what has changed in the repository.Notes:

The content stream is NOT returned for any change event. The definition of the authority needed to call this service is repository specific. The latest change log token for a repository can be acquired via the getRepositoryInfo service.

2.2.6.2.1 InputsRequired:

ID repositoryId: The identifier for the Repository.Optional:

String changeLogToken: o If specified, then the Repository MUST return the change event corresponding to the value of

the specified change log token as the first result in the output.o If not specified, then the Repository MUST return the first change event recorded in the

change log. Boolean includeProperties:

o If TRUE, then the Repository MUST include the updated property values for “updated” change events. if the repository supports returning property values as specified by capbilityChanges.

o If FALSE (default), then the Repository MUST NOT include the updated property values for “updated” change events. The single exception to this is that the objectId MUST always be included.

Boolean includePolicyIDs:includePolicyIds: If TRUE, then the Repository MUST include the IDs of Policies applied to the object referenced in

each change event, if the change event modified the set of policies applied to the object.If FALSE (default), then the Repository will not include policy information.

String filter: See section 2.2.1.2.1 Properties. The service will only return the properties in the matched object if they exist on the matched object type definition and in the filter.

Boolean includeACL: See section 2.2.1.2.5 ACLs. Integer maxItems: See section 2.2.1.1 Paging.

2.2.6.2.2 Outputs <Array> changeEvents: A collection of CMIS objects that MUST include the information as

specified in 2.1.11.3. Each result MUST include the following elements if they are requested:o <Array> policyIDs: The IDs of Policies applied to the object referenced in the change event.

o <Array> ACLs: The ACLs applied to the object reference in the change event.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 108 of 240

42834284428542864287

4288428942904291429242934294

429542964297429842994300430143024303430443054306430743084309431043114312431343144315431643174318

43194320432143224323

322323324

Page 109: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

String lastChangeLogTokenlatestChangeLogToken: The change log token corresponding to the last change event in changeEvents.

Boolean hasMoreItems: See section 2.2.1.1 Paging.Optional:

Integer numItems: See section 2.2.1.1 Paging.

2.2.6.2.3 Exceptions Thrown & Conditions See section 2.2.1.4.1 General Exceptions constraint: The Repository MUST throw this exception if the event corresponding to the

change log token provided as an input parameter is no longer available in the change log. (E.g. because the change log was truncated).

2.2.7 Versioning ServicesThe Versioning services (checkOut, cancelCheckOut, getPropertiesOfLatestVersion, getAllVersions, deleteAllVersions) are used to navigate or update a Document Version Series.

2.2.7.1 checkOutDescription: Create a private working copy of the document.

2.2.7.1.1 InputsRequired:

ID repositoryId: The identifier for the Repository. ID objectId: The identifier of the object.document version.

2.2.7.1.2 Outputs ID objectId: The identifier for the “Private Working Copy” document.

Boolean contentCopied: TRUE if the content-stream of the Private Working Copy is a copy of the contentStream of the Document that was checked out. o FALSE if the content-stream of the Private Working Copy is “not set”.

2.2.7.1.3 Exceptions Thrown & Conditions See section 2.2.1.4.1 General Exceptions constraint: The Repository MUST throw this exception if the Document’s Object-Type

definition’s versionable attribute is FALSE. storage: See section 2.2.1.4.2 Specific Exceptions.

updateConflict: See section 2.2.1.4.2 Specific Exceptions.

versioning: The repository MAY throw this exception if the object is a non-current Document Version.

2.2.7.2 cancelCheckOutDescription: Reverses the effect of a check-out. Removes the private working copy of the checked-out document, allowing other documents in the version series to be checked out again.

2.2.7.2.1 InputsRequired:

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 109 of 240

43244325432643274328

43294330433143324333

433443354336

43374338

4339434043414342

43434344

434543464347

43484349435043514352435343544355

435643574358

43594360

325326327

Page 110: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

ID repositoryId: The identifier for the Repository. ID objectId: The identifier of the document.Private Working Copy.

2.2.7.2.2 Exceptions Thrown & Conditions See section 2.2.1.4.1 General Exceptions constraint: The Repository MUST throw this exception if the Document’s Object-Type

definition’s versionable attribute is FALSE. updateConflict: See section 2.2.1.4.2 Specific Exceptions.

versioning: The repository MAY throw this exception if the object is a non-current Document Version.

2.2.7.3 checkInDescription: Checks-in the Private Working Copy document.Notes:

For repositories that do NOT support the optional “capabilityPWCUpdatable” capability, the properties and contentStream input parameters MUST be provided on the checkIn method for updates to happen as part of checkIn.

Each CMIS protocol bindings MUST specify whether the checkin service MUST always include all updatable properties, or only those properties whose values are different than the original value of the object.

2.2.7.3.1 InputsRequired:

ID repositoryId: The identifier for the Repository. ID objectId: The identifier of the document.

Optional: Boolean major: TRUE (default) if the checked-in Document Object MUST be a major version.

o FALSE if the checked-in Document Object MUST NOT be a major version.

<Array> properties: The property values that MUST be applied to the checked-in Document Object.

<contentStream> contentStream: The Content Stream that MUST be stored for the checked-in Document Object. The method of passing the contentStream to the server and the encoding mechanism will be specified by each specific binding.

String checkinComment: See section 2.1.9.5 Versioning Properties on Document Objects. <Array> policies: A list of policy IDs that MUST be applied to the newly-created Document

object. <Array> ACE addACEs: A list of ACEs that MUST be added to the newly-created Document

object, either using the ACL from folderId if specified, or being applied if no folderId is specified. <Array> ACE removeACEs: A list of ACEs that MUST be removed from the newly-created

Document object, either using the ACL from folderId if specified, or being ignored if no folderId is specified.

2.2.7.3.2 OutputsID objectId: The ID of the checked-in document.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 110 of 240

43614362

4363436443654366436743684369

437043714372437343744375437643774378

43794380438143824383438443854386438743884389439043914392439343944395439643974398

43994400

328329330

Page 111: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

2.2.7.3.3 Exceptions Thrown & Conditions See section 2.2.1.4.1 General Exceptions constraint: The Repository MUST throw this exception if the Document’s Object-Type

definition’s versionable attribute is FALSE. storage: See section 2.2.1.4.2 Specific Exceptions.

streamNotSupported: The Repository MUST throw this exception if the “contentStreamAllowed” attribute of the Object-Type definition specified by the cmis:objectTypeId property value is set to “not allowed” and a contentStream input parameter is provided.

updateConflict: See section 2.2.1.4.2 Specific Exceptions.

2.2.7.4 getObjectOfLatestVersionDescription: Get a the latest Document object in the Version Series.

2.2.7.4.1 InputsRequired:

ID repositoryId: The identifier for the Repository. ID objectId: The identifier for the Version Series.

Optional: Boolean major: If TRUE, then the Repository MUST returnthe properties for the latest major

version object in the Version Series.o If FALSE (default), the Repository MUST return the properties for the latest (major or non-

major) version object in the Version Series. String filter: See Error: Reference source not foundsection 2.2.1.2.1 Properties. Enum includeRelationships: See section 2.2.1.2.2 Relationships. Boolean includePolicyIds: See section 2.2.1.2.3 Policies. String renditionFilter: See section 2.2.1.2.4 Renditions. Boolean includeACL: See section 2.2.1.2.5 ACLs. Boolean includeAllowableActions: See section 2.2.1.2.6 Allowable Actions.

2.2.7.4.2 Outputs <Array> Properties: The list of properties for the object. <Array> Relationships: See section 2.2.1.2.2 Relationships. <Array> Policy Ids: See section 2.2.1.2.3 Policies. <Array> Renditions: See section 2.2.1.2.4 Renditions. <Array> ACLs: See section 2.2.1.2.5 ACLs. AllowableActions: See section 2.2.1.2.6 Allowable Actions.

2.2.7.4.3 Exceptions Thrown & Conditions See section 2.2.1.4.1 General Exceptions filterNotValid: The Repository MUST throw this exception if this property filter input

parameter is not valid. objectNotFound: The Repository MUST throw this exception if the input parameter major is

TRUE and the Version Series contains no major versions.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 111 of 240

440144024403440444054406440744084409

44104411

441244134414441544164417441844194420442144224423442444254426

4427442844294430443144324433

443444354436443744384439

331332333

Page 112: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

2.2.7.5 getPropertiesOfLatestVersionDescription: Get a subset of the properties for the latest Document Object in the Version Series.

2.2.7.5.1 InputsRequired:

ID repositoryId: The identifier for the Repository. ID objectId: The identifier for the Version Series.

Optional: Boolean major: If TRUE, then the Repository MUST return the properties for the latest major

version object in the Version Series.o If FALSE (default), the Repository MUST return the properties for the latest (major or non-

major) version object in the Version Series. String filter: See Error: Reference source not foundsection 2.2.1.2.1 Properties.

2.2.7.5.2 Outputs<Array> Properties: The list of properties for the object.

2.2.7.5.3 Exceptions Thrown & Conditions See section 2.2.1.4.1 General Exceptions filterNotValid: The Repository MUST throw this exception if this property filter input

parameter is not valid. objectNotFound: The Repository MUST throw this exception if the input parameter major is

TRUE and the Version Series contains no major versions.

2.2.7.6 getAllVersionsDescription: Returns the list of all Document Objects in the specified Version Series, sorted by cmis:creationDate descending.Notes:

The result set for this operation MUST include the Private Working Copy, subject to caller’s access privileges.

2.2.7.6.1 InputsRequired:

ID repositoryId: The identifier for the Repository. ID objectId: The identifier for the Version Series.

Optional: String filter: See Error: Reference source not foundsection 2.2.1.2.1 Properties. Boolean includeAllowableActions: See section 2.2.1.2.6 Allowable Actions.

2.2.7.6.2 Outputs <Array> ObjectResults: A list of Document Objects in the specified Version Series. Each object

result MUST include the following elements if they are requested:o <Array> Properties: The list of properties for the object.

o AllowableActions: See section 2.2.1.2.6 Allowable Actions.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 112 of 240

44404441

4442444344444445444644474448444944504451

44524453

445444554456445744584459

446044614462446344644465

4466446744684469447044714472

44734474447544764477

334335336

Page 113: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

2.2.7.6.3 Exceptions Thrown & Conditions See section 2.2.1.4.1 General Exceptions filterNotValid: The Repository MUST throw this exception if this property filter input

parameter is not valid.

2.2.8 Relationship ServicesThe Relationship Services (getObjectRelationships) are used to retrieve the dependent Relationship objects associated with an independent object.

2.2.8.1 getObjectRelationshipsDescription: Gets all or a subset of relationships associated with an independent object.

2.2.8.1.1 InputsRequired:

ID repositoryId: The identifier for the Repository. ID objectId: The identifier of the object.

Optional: Boolean includeSubRelationshipTypes: If TRUE, then the Repository MUST return all

relationships whose Object-Types are descendant-types of the given object’s cmis:objectTypeId property value. as well as relationships of the specified type. o Default is FALSE

o If FALSE, then the Repository MUST only return relationships whose Object-Type is equivalent to the given object’s cmis:objectTypeId property value.

Enum relationshipDirection: An enumeration specifying whether the Repository MUST return relationships where the specified Object is the source of the relationship, the target of the relationship, or both. Valid values are:o source: (default) The Repository MUST return only relationship objects where the specified

object is the source object. o target: The Repository MUST return only relationship objects where the specified object is

the target object. o either: The Repository MUST return relationship objects where the specified object is

either the source or the target object. ID typeId: If specified, then the Repository MUST return only relationships whose Object-Type is

of the type specified (and possibly its descendant-types – see next parameter.)o If not specified, then the repository MUST return Relationship objects of all types.

Integer maxItems: See section 2.2.1.1 Paging. Integer skipCount: See section 2.2.1.1 Paging. String filter: See section 2.2.1.2.1 Properties. Boolean includeAllowableActions: See section 2.2.1.2.6 Allowable Actions.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 113 of 240

4478

4479448044814482

448344844485

44864487

4488448944904491

449244934494449544964497449844994500450145024503450445054506450745084509451045114512451345144515

337338339

Page 114: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

2.2.8.1.2 Outputs <Array> Objects: A list of the relationship objects. Each object result MUST include the following

elements if they are requested:o <Array> Properties: The list of properties for the object.

o AllowableActions: See section 2.2.1.2.6 Allowable Actions.

Boolean hasMoreItems: See section 2.2.1.1 Paging.Optional:

Integer numItems: See section 2.2.1.1 Paging.

2.2.8.1.3 Exceptions Thrown & Conditions See section 2.2.1.4.1 General Exceptions filterNotValid: The Repository MUST throw this exception if this property filter input

parameter is not valid.

2.2.9 Policy Services The Policy Services (applyPolicy, removePolicy, getAppliedPolicies) are used to apply or remove a policy object to a controllablePolicy object.

2.2.9.1 applyPolicyDescription: Applies a specified policy to an object.

2.2.9.1.1 InputsRequired:

ID repositoryId: The identifier for the Repository. ID policyId: The identifier for the Policy to be applied. ID objectId: The identifier of the object.

2.2.9.1.2 Exceptions Thrown & ConditionsSee section 2.2.1.4.1 General Exceptionsconstraint : The Repository MUST throw this exception if the specified object’s Object-Type

definition’s attribute for controllablePolicy is FALSE.

2.2.9.2 removePolicyDescription: Removes a specified policy from an object.

2.2.9.2.1 InputsRequired:

ID repositoryId: The identifier for the Repository. ID policyId: The identifier for the Policy to be removed. ID objectId: The identifier of the object.

2.2.9.2.2 Exceptions Thrown & Conditions See section 2.2.1.4.1 General Exceptions

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 114 of 240

45164517451845194520452145224523

4524

4525452645274528

452945304531

45324533

45344535453645374538

4539454045414542

45434544

45454546454745484549

45504551

340341342

Page 115: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

constraint: The Repository MUST throw this exception if the specified object’s Object-Type definition’s attribute for controllablePolicy is FALSE.

2.2.9.3 getAppliedPoliciesDescription: Gets the list of policies currently applied to the specified object.

2.2.9.3.1 InputsRequired:

ID repositoryId: The identifier for the Repository. ID objectId: The identifier of the object.

Optional: String filter: See Error: Reference source not foundsection 2.2.1.2.1 Properties.

2.2.9.3.2 Outputs<Array> Objects: A list of Policy Objects.

2.2.9.3.3 Exceptions Thrown & Conditions See section 2.2.1.4.1 General Exceptions filterNotValid: The Repository MUST throw this exception if this property filter input

parameter is not valid.

2.2.10 ACL Services

2.2.10.1 getACLDescription: Get the ACL currently applied to the specified document or folder object.

2.2.10.1.1 InputsRequired:

ID repositoryId: The identifier for the repository. ID objectId: The identifier for the object

Optional: Boolean onlyBasicPermissions: See section 2.8 Access Control. The repository SHOULD

make a best effort to fully express the native security applied to the objecto TRUE: (default value if not provided) indicates that the client requests that the returned

ACL be expressed using only the CMIS Basic permissions.o FALSE: indicates that the server may respond using either solely CMIS Basic

permissions, or repository specific permissions or some combination of both.

2.2.10.1.2 Outputs <Array> AccessControlEntryType: The list of access control entries of the ACL for the object.

Optional: Boolean exact: An indicator that the ACL returned fully describes the permission for this object –

i.e. there are no other security constraints applied to this object. Not provided defaults to FALSE.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 115 of 240

45524553

45544555

455645574558455945604561

45624563

4564456545664567

4568

45694570

45714572457345744575457645774578457945804581

45824583458445854586

343344345

Page 116: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

2.2.10.1.3 Exceptions Thrown & Conditions See section 2.2.1.4.1 General Exceptions

2.2.10.1.4 NotesThis service MUST be supported by a repository, if getRepository returns capabilityACL=discover or =manage.How an ACL for the object is computed is up to the repository. A client MUST NOT assume that the ACEs from the ACL as returned by this service can be applied via applyACL.

2.2.10.2 applyACLDescription: Adds or removes the given ACEs to or from the ACL of document or folder object.

2.2.10.2.1 InputsRequired:

ID repositoryId: The identifier for the repository. ID objectId: The identifier for the object

Optional: <Array> AccessControlEntryType addACEs: The ACEs to be added. <Array> AccessControlEntryType removeACEs: The ACEs to be removed. Enum ACLPropagation: Specifies how ACEs should be handled:

o objectonly: ACEs must be applied without changing the ACLs of other objects.

o propagate: ACEs must be applied by propagate the changes to all “inheriting” objects.

o repositorydetermined: Default value. Indicates that the client leaves the behavior to the repository.

2.2.10.2.2 Outputs <Array> AccessControlEntryType: The list of access control entries of the resulting ACL for the

objectOptional:

Boolean exact: An indicator that the ACL returned fully describes the permission for this object – i.e. there are no other security constraints applied to this object. Not provided defaults to FALSE.

String changeToken: See section 2.2.1.3 Change Tokens.

2.2.10.2.3 Exceptions Thrown & Conditions See section 2.2.1.4.1 General Exceptions constraint: The Repository MUST throw this exception if ANY of the following conditions are

met:o The specified object’s Object-Type definition’s attribute for controllableACL is FALSE.

o The value for ACLPropagation does not match the values as returned via getACLCapabilities.

o At least one of the specified values for permission in ANY of the ACEs does not match ANY of the permissionNames as returned by getACLCapability and is not a CMIS Basic permission

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 116 of 240

45874588

45894590459145924593

45944595

459645974598459946004601460246034604460546064607

4608460946104611461246134614

4615461646174618461946204621462246234624

346347348

Page 117: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

2.2.10.2.4 NotesThis service MUST be supported by a repository, if getRepository returns capabilityACL=manage.How ACEs are added or removed to or from the object is up to the repository – with respect to the ACLPropagation provided by the client. For “shared” ACEs (e.g. via inheritance), the repository MAY merge the ACEs provided with the ACEs of the ACL already applied to the object (i.e. the ACEs provided MAY not be completely added or removed from the effective ACL for the object).

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 117 of 240

462546264627462846294630

46314632

349350351

Page 118: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

3 Restful AtomPub Binding3.1 OverviewThis binding is based upon the Atom (RFC4287) and Atom Publishing Protocol (RFC5023). Implementations of CMIS MUST be compliant with RFC4287 and RFC5023.

In this binding, the client interacts with the repository by acquiring the service document. The client will request the service document by the URI provided by the vendor. The client will then choose a CMIS collection, and then start accessing the repository by following the references in the returned documents.

This binding consists of a service document specifying at least CMIS service collections, atom collections, feeds and entry documents. CMIS extends the Atom and AtomPub documents utilizing the Atom and AtomPub extension mechanism. CMIS also leverages link tags to specify additional resources related to the requested resource.

When requesting a resource, optional parameters may be specified to change default behavior via query parameters.

3.1.1 NamespacesThis specification uses the following namespaces and prefixes when referring to xml or xml schema elements in the text or examples:

CMIS-Core: http://docs.oasis-open.org/ns/cmis/core/200908/o Prefix: cmis

CMIS-RestAtom: http://docs.oasis-open.org/ns/cmis/restatom/200908/o Prefix: cmisra

Atom : http://www.w3.org/2005/Atomo Prefix: atom

AtomPub: http://www.w3.org/2007/appo Prefix: app

3.1.2 AuthenticationAuthentication SHOULD be handled by the transport protocol. Please see AtomPub (RFC5023) section 14.

3.1.3 Response FormatsThe client can specify, in HTTP the Accept header, which formats are acceptable to the client. With this mechanism the client can chose which response format the CMIS implementation should respond with. The CMIS compliant implementation MUST support the appropriate Media Types specified in this document.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 118 of 240

4633

463446354636

4637463846394640

46414642464346444645

464646474648

464946504651465246534654465546564657465846594660

466146624663

4664

46654666466746684669

352353354

Page 119: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

3.1.4 Optional ArgumentsThe binding supports adding optional parameters to CMIS resources to modify the default behavior. CMIS implementations MUST support arguments being specified as HTTP query string parameters.Names and valid values for HTTP query string parameters are as described in the appropriate CMIS Service descriptions [see CMIS Domain Model]. Valid values of enumeration types are also represented in the CMIS Core XML Schema

3.1.5 Errors and ExceptionsExceptions MUST be mapped to the appropriate HTTP status code.Repositories SHOULD provide sufficient information in the body of the HTTP response for a user to determine corrective action.See Section 3.2.4 HTTP Status Codes for more information.

3.1.6 RenditionsEach Rendition included in a CMIS AtomPub response is represented as an Atom link with relationship alternate.

The following attributes SHOULD be included on the link element: href: URI to the rendition content stream type: The Media Type of the Rendition cmisra:renditionKind: The Rendition Kind for the Rendition

The following attributes MAY be included title: The Filename (or name property if object) of Rendition length: The length of the rendition

3.1.7 Content StreamsThe content stream for a document SHOULD be referenced by the content src attribute as well as the edit-media link relation. A CMIS Repository MAY use different URIs for both content src attribute and the edit-media link relation for the same content stream.The following attributes SHOULD be included on the link element:

href: URI to the content stream type: The Media Type of the content stream

3.1.8 Paging of FeedsFor paging, please see the AtomPub RFC. CMIS leverages first, next, previous, and last link relations to express paging.If the repository can include the number of items (numItems in CMIS Domain Model) in a feed, then the repository SHOULD include the cmisra:numItems extension element in the feed.

3.1.9 Services not ExposedThe following services are not exposed in this binding:

getRenditions: This is exposed as part of getObject

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 119 of 240

467046714672467346744675

46764677467846794680

468146824683

46844685468646874688

4689469046914692

46934694469546964697469846994700

47014702470347044705

470647074708

355356357

Page 120: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

getProperties: This is exposed as part of getObject createDocumentFromSource: This is not exposed in this binding except as the client saving the

resource and resubmitting it without the cmis:objectId.

Setting ACL on Create or Checkin operationso This is currently not possible with the REST binding. The Create or Checkin operation

must be performed first, then the dependent resource, ACL, must be retrieved and updated.

setContentStream: This does not return the new object id and change token as specified by the domain model. This is not possible without introducing a new HTTP header.

deleteContentStream: This does not return the new object id and change token as specified by the domain model. This is not possible without introducing a new HTTP header.

checkOut: This does not return whether or not content was copied. This is not possible without introducing a new HTTP header.

3.1.9.1 removePolicyThis service is exposed from the domain model in the RESTful Atom Binding. However, it is not as straightforward. To remove a policy from an object, one must do:

Get the object. Fetch the policies collection of the object. Walk through the feed and find the policy object where cmis:objectId == policy id to remove. Get the self lin of this policy object. Perform a DELETE on this URL.

This is also the only case in the RESTful Atom Binding where an URI in a collection (policies) is specific to that collection.

3.2 HTTP

3.2.1 Entity TagCMIS changeTokens are represented as Entity Tags and follow HTTP’s use of Entity Tags. CMIS server implementations SHOULD support Entity Tags. ChangeTokens are also provided as properties and SHOULD be provided when the object is included inside an atom entry or feed.

3.2.2 HTTP Range Repositories MAY support HTTP Range requests on Content Streams.

3.2.3 HTTP OPTIONS Method The repository MAY support the HTTP OPTIONS method on all the resources defined in this specification. If the repository supports OPTIONS, then the repository MUST at least return the HTTP methods specified for that resource in the Allow header.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 120 of 240

470947104711

471247134714471547164717471847194720472147224723

47244725472647274728472947304731

473247334734

4735

4736473747384739

47404741

4742474347444745

358359360

Page 121: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

3.2.4 HTTP Status CodesCommonPlease see the HTTP specification for more information on the HTTP status codes. These are provided as guidance from the HTTP specification. If any conflict arises, the HTTP specification is authoritative.

3.2.4.1 General CMIS ExceptionsThe following listing defines the HTTP status codes that repositories MUST return for the various common exceptions defined in CMIS Domain Model.

CMIS Services Exception HTTP Status CodeinvalidArgument 400objectNotFound 404permissionDenied 403operationNotSupportednotSupported 405updateConflict 409runtime 500

3.2.4.2 Other ExceptionsCMIS Services Exception HTTP Status Codeconstraint 409filterNotValid 400streamNotSupported 403storage 500contentAlreadyExists 409versioning 409updateConflict 409nameConstraintViolation 409

3.2.4.3 Notable HTTP Status Codes 415 Unsupported Media Type

o When a document is POST’ed to a collection that does not support the media type of the document, this status code MUST be returned

422 Unprocessable Entity (Defined in RFC4918 Section 11.2)o When a request has been POST’ed but cannot be processed, this status code MUST be

returned

Please see RFC2616 Section 10 for more information.

3.3 Media TypesCMIS introduces new media types for:

a CMIS Query document (application/cmisquery+xml) a CMIS AllowableActions document (application/cmisallowableactions+xml)

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 121 of 240

4746474747484749

4750475147524753475447554756475747584759

4760476147624763476447654766476747684769

4770

4771477247734774477547764777

47784779

4780

4781478247834784

361362363

Page 122: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

an Atom Document (Entry or Feed) with any CMIS Markup (application/cmisatom+xml) an Atom Feed Document with CMIS Hierarchy extensions (application/cmistree+xml)

In addition to those media types specified by CMIS, CMIS also leverages these media types: AtomPub Service (application/atomsvc+xml) Atom Entry (application/atom+xml;type=entry) Atom Feed (application/atom+xml;type=feed)

3.3.1 CMIS AtomMedia Type: application/cmisatom+xmlStarting tag: atom:feed or atom:entryType Parameters:

type – the semantics of the type parameter MUST be the same as the media type parameter for atom documents.

This allows clients to differentiate between repositories that require atom media type with CMIS extensions (application/cmisatom+xml) for creation and repositories that allow generic atom media type without CMIS extensions (application/atom+xml).

This is only used for CMIS repositories to advertise what media types are accepted for adding to a collection (e.g., creating resources in a collection). As such CMIS does not require specifying whether an atom feed has CMIS markup. It is included to be consistent with the Atom media type.

All feeds and entries from a CMIS repository MUST utilize the atom media type for exposing Atom resources. Please see the individual resources for more information on the media type. This provides the interoperability with Atom clients.

Example:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><atom:entry xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:app="http://www.w3.org/2007/app" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <atom:author> <atom:name>Al Brown</atom:name> </atom:author> <atom:id>urn:uuid:5f716462-7b6b-4a0d-bd1d-34677d5514d7efe0542e-8933-4b3e-93f2-4d1caa3fc2d9</atom:id> <atom:title type="text">CMIS Example Document</atom:title> <atom:updated>2009-10-19T10:09:59.296-072010-01-25T10:20:58.318-08:00</atom:updated> <atom:content type="text">some text</atom:content> <cmisra:object> <cmis:properties> <cmis:propertyId localName="rep-cmis:objectTypeId" propertyDefinitionId="cmis:objectTypeId"> <cmis:value>invoice</cmis:value> </cmis:propertyId>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 122 of 240

47854786

47874788478947904791

479247934794479547964797

4798479948004801

4802480348044805

4806480748084809

481048114812481348144815481648174818481948204821482248234824482548264827482848294830483148324833

364365366

Page 123: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<cmis:propertyString localName="rep-cmis:name" propertyDefinitionId="cmis:name"> <cmis:value>CMIS Example Document</cmis:value> </cmis:propertyString> </cmis:properties> </cmisra:object></atom:entry>

3.3.2 CMIS QueryMedia Type: application/cmisquery+xmlStarting tag: cmis:query

This document contains the representation of a query to be executed in a CMIS repository.

Example:<?xml version="1.0" encoding="UTF-8" standalone="yes"?><cmis:query xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:app="http://www.w3.org/2007/app" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <cmis:statement>SELECT * FROM cmis:document</cmis:statement> <cmis:searchAllVersions>true</cmis:searchAllVersions> <cmis:includeAllowableActions>false</cmis:includeAllowableActions> <cmis:includeRelationships>none</cmis:includeRelationships> <cmis:renditionFilter>*</cmis:renditionFilter> <cmis:maxItems>50</cmis:maxItems> <cmis:skipCount>0</cmis:skipCount></cmis:query>

Please also see the example documents included with the schema.

3.3.3 CMIS Allowable ActionsMedia Type: application/cmisallowableactions+xmlStarting tag: cmis:allowableactionsallowableActions

This document contains the representation of the allowable actions the user may perform on the referenced object.

Example:<?xml version="1.0" encoding="UTF-8" standalone="yes"?><cmis:allowableActions xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:app="http://www.w3.org/2007/app" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <cmis:canDeleteObject>true</cmis:canDeleteObject> <cmis:canUpdateProperties>true</cmis:canUpdateProperties> <cmis:canGetProperties>true</cmis:canGetProperties> <cmis:canGetObjectRelationships>true</cmis:canGetObjectRelationships>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 123 of 240

48344835483648374838483948404841

484248434844

48454846

4847484848494850485148524853485448554856485748584859486048614862

48634864

4865

486648674868

486948704871

4872487348744875487648774878487948804881488248834884

367368369

Page 124: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<cmis:canGetObjectParents>true</cmis:canGetObjectParents> <cmis:canMoveObject>true</cmis:canMoveObject> <cmis:canDeleteContentStream>true</cmis:canDeleteContentStream> <cmis:canCheckOut>true</cmis:canCheckOut> <cmis:canCancelCheckOut>true</cmis:canCancelCheckOut> <cmis:canCheckIn>true</cmis:canCheckIn> <cmis:canSetContentStream>true</cmis:canSetContentStream> <cmis:canGetAllVersions>true</cmis:canGetAllVersions> <cmis:canAddObjectToFolder>true</cmis:canAddObjectToFolder> <cmis:canRemoveObjectFromFolder>true</cmis:canRemoveObjectFromFolder> <cmis:canGetContentStream>true</cmis:canGetContentStream> <cmis:canApplyPolicy>true</cmis:canApplyPolicy> <cmis:canGetAppliedPolicies>true</cmis:canGetAppliedPolicies> <cmis:canRemovePolicy>true</cmis:canRemovePolicy> <cmis:canCreateDocument>true</cmis:canCreateDocument></cmis:allowableActions>

Please also see the example documents included with the schema.

3.3.4 CMIS TreeMedia Type: application/cmistree+xmlStarting tag: atom:feed

This document is an atom feed (application/atom+xml;type=feed) with CMIS markup to nest a hierarchy.

Please see Section 3.5.2.1 for more information.

Example:<?xml version="1.0" encoding="UTF-8" standalone="yes"?><atom:feed xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:app="http://www.w3.org/2007/app" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <atom:title type="text">Feed for folder1</atom:title> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:updated>2009-10-19T10:09:59.515-072010-01-25T10:20:58.536-08:00</atom:updated> <atom:id>urn:uuid:08d13325-cba1-4290-95e3-f485068b08e84a80905c-f774-4a9e-a57d-bf0dae5a796e</atom:id> <atom:link type="application/atom+xml;type=feed" rel="self" href="http://cmisexample.oasis-open.org/rep1/4f942e30-895c-4c82-9b31-58f639b6c2d7cf3c076e-36e9-4ace-8fed-41e0d92dfc71/3"/> <atom:link type="application/atomsvc+xml" rel="service" href="http://cmisexample.oasis-open.org/rep1//service"/> <atom:link type="application/atom+xml;type=entry" rel="via" href="http://cmisexample.oasis-open.org/rep1/4f942e30-895c-4c82-9b31-58f639b6c2d7cf3c076e-36e9-4ace-8fed-41e0d92dfc71"/>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 124 of 240

4885488648874888488948904891489248934894489548964897489848994900

49014902

4903

490449054906

49074908

49094910

49114912491349144915491649174918491949204921492249234924492549264927492849294930493149324933493449354936

370371372

Page 125: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/foldertree" href="http://cmisexample.oasis-open.org/rep1/4f942e30-895c-4c82-9b31-58f639b6c2d7cf3c076e-36e9-4ace-8fed-41e0d92dfc71/foldertree"/> <atom:link type="application/atom+xml;type=feed" rel="down" href="http://cmisexample.oasis-open.org/rep1/4f942e30-895c-4c82-9b31-58f639b6c2d7cf3c076e-36e9-4ace-8fed-41e0d92dfc71/children"/> <atom:link type="application/atom+xml;type=entry" rel="up" href="http://cmisexample.oasis-open.org/rep1/b8803070-0253-4160-9ad6-26ad7adbf561bb11830c-7d1e-4b0f-9ff2-af4857c49200"/> <atom:entry> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:content src="http://cmisexample.oasis-open.org/rep1/962b4fb8-aefa-4d0c-8562-a84e297e810763a9c18c-5e31-4590-8462-86d181e345a4"/> <atom:id>urn:uuid:962b4fb8-aefa-4d0c-8562-a84e297e810763a9c18c-5e31-4590-8462-86d181e345a4</atom:id> <atom:title type="text">CMIS Example Folder as Customer type</atom:title> <atom:updated>2009-10-19T10:09:59.515-072010-01-25T10:20:58.536-08:00</atom:updated> <atom:link rel="self" href="http://cmisexample.oasis-open.org/rep1/962b4fb8-aefa-4d0c-8562-a84e297e810763a9c18c-5e31-4590-8462-86d181e345a4"/> <atom:link rel="edit" href="http://cmisexample.oasis-open.org/rep1/962b4fb8-aefa-4d0c-8562-a84e297e810763a9c18c-5e31-4590-8462-86d181e345a4"/> <atom:link type="application/cmis+xml;type=allowableActions" rel="http://docs.oasis-open.org/ns/cmis/link/200908/allowableactions" href="http://cmisexample.oasis-open.org/rep1/962b4fb8-aefa-4d0c-8562-a84e297e810763a9c18c-5e31-4590-8462-86d181e345a4/allowableactions"/> <atom:link type="application/atom+xml;type=entry" rel="describedby" href="http://cmisexample.oasis-open.org/rep1/962b4fb8-aefa-4d0c-8562-a84e297e810763a9c18c-5e31-4590-8462-86d181e345a4/type"/> <atom:link type="application/atomsvc+xml" rel="service" href="http://cmisexample.oasis-open.org/rep1//service"/> <atom:published>2009-10-19T10:09:59.515-072010-01-25T10:20:58.536-08:00</atom:published> <atom:summary type="html">HTML summary of Entry 962b4fb8-aefa-4d0c-8562-a84e297e810763a9c18c-5e31-4590-8462-86d181e345a4</atom:summary> <atom:link type="application/atom+xml;type=entry" rel="up" href="http://cmisexample.oasis-open.org/rep1/962b4fb8-aefa-4d0c-8562-a84e297e810763a9c18c-5e31-4590-8462-86d181e345a4/up"/> <atom:link type="application/atom+xml;type=feed" rel="down" href="http://cmisexample.oasis-open.org/rep1/962b4fb8-aefa-4d0c-8562-a84e297e810763a9c18c-5e31-4590-8462-86d181e345a4/children"/> <atom:link type="application/cmistree+xml" rel="down" href="http://cmisexample.oasis-open.org/rep1/962b4fb8-aefa-4d0c-8562-a84e297e810763a9c18c-5e31-4590-8462-86d181e345a4/tree"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/foldertree" href="http://cmisexample.oasis-open.org/rep1/962b4fb8-aefa-4d0c-8562-a84e297e810763a9c18c-5e31-4590-8462-86d181e345a4/foldertree"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/relationships" href="http://cmisexample.oasis-open.org/rep1/962b4fb8-aefa-4d0c-8562-a84e297e810763a9c18c-5e31-4590-8462-86d181e345a4/relationships"/>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 125 of 240

493749384939494049414942494349444945494649474948494949504951495249534954495549564957495849594960496149624963496449654966496749684969497049714972497349744975497649774978497949804981498249834984498549864987498849894990499149924993499449954996

373374375

Page 126: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/policies" href="http://cmisexample.oasis-open.org/rep1/962b4fb8-aefa-4d0c-8562-a84e297e810763a9c18c-5e31-4590-8462-86d181e345a4/policies"/> <atom:link type="application/cmisacl+xml" rel="http://docs.oasis-open.org/ns/cmis/link/200908/acl" href="http://cmisexample.oasis-open.org/rep1/962b4fb8-aefa-4d0c-8562-a84e297e810763a9c18c-5e31-4590-8462-86d181e345a4/acl"/> <cmisra:object> <cmis:properties> <cmis:propertyId localName="rep-cmis:objectId" propertyDefinitionId="cmis:objectId"> <cmis:value>962b4fb8-aefa-4d0c-8562-a84e297e810763a9c18c-5e31-4590-8462-86d181e345a4</cmis:value> </cmis:propertyId> </cmis:properties> </cmisra:object> <cmisra:pathSegment>customer</cmisra:pathSegment> <cmisra:children> <atom:feed> <atom:title type="text">CMIS Example Folder as Customer type</atom:title> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:updated>2009-10-19T10:09:59.515-072010-01-25T10:20:58.536-08:00</atom:updated> <atom:id>urn:uuid:084edab9-418a-42b9-813f-cf450418181d51b5c0cd-e473-4492-82b3-666fbf913cf0</atom:id> <atom:link type="application/atom+xml;type=feed" rel="self" href="http://cmisexample.oasis-open.org/rep1/962b4fb8-aefa-4d0c-8562-a84e297e810763a9c18c-5e31-4590-8462-86d181e345a4/3"/> <atom:link type="application/atomsvc+xml" rel="service" href="http://cmisexample.oasis-open.org/rep1//service"/> <atom:link type="application/atom+xml;type=entry" rel="via" href="http://cmisexample.oasis-open.org/rep1/962b4fb8-aefa-4d0c-8562-a84e297e810763a9c18c-5e31-4590-8462-86d181e345a4"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/foldertree" href="http://cmisexample.oasis-open.org/rep1/962b4fb8-aefa-4d0c-8562-a84e297e810763a9c18c-5e31-4590-8462-86d181e345a4/foldertree"/> <atom:link type="application/atom+xml;type=feed" rel="down" href="http://cmisexample.oasis-open.org/rep1/962b4fb8-aefa-4d0c-8562-a84e297e810763a9c18c-5e31-4590-8462-86d181e345a4/children"/> <atom:link type="application/atom+xml;type=entry" rel="up" href="http://cmisexample.oasis-open.org/rep1/4f942e30-895c-4c82-9b31-58f639b6c2d7cf3c076e-36e9-4ace-8fed-41e0d92dfc71"/> <atom:entry> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:content src="http://cmisexample.oasis-open.org/rep1/fba295fd-c8ed-40d1-8ddc-93671a9c89a520cb7e68-0a7e-46ea-87e0-09fb8d85286e"/> <atom:id>urn:uuid:fba295fd-c8ed-40d1-8ddc-93671a9c89a520cb7e68-0a7e-46ea-87e0-09fb8d85286e</atom:id> <atom:title type="text">CMIS Example Doc as Invoice type</atom:title>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 126 of 240

49974998499950005001500250035004500550065007500850095010501150125013501450155016501750185019502050215022502350245025502650275028502950305031503250335034503550365037503850395040504150425043504450455046504750485049505050515052505350545055505650575058

376377378

Page 127: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<atom:updated>2009-10-19T10:09:59.515-072010-01-25T10:20:58.536-08:00</atom:updated> <atom:link rel="self" href="http://cmisexample.oasis-open.org/rep1/fba295fd-c8ed-40d1-8ddc-93671a9c89a520cb7e68-0a7e-46ea-87e0-09fb8d85286e"/> <atom:link rel="edit" href="http://cmisexample.oasis-open.org/rep1/fba295fd-c8ed-40d1-8ddc-93671a9c89a520cb7e68-0a7e-46ea-87e0-09fb8d85286e"/> <atom:link type="application/cmis+xml;type=allowableActions" rel="http://docs.oasis-open.org/ns/cmis/link/200908/allowableactions" href="http://cmisexample.oasis-open.org/rep1/fba295fd-c8ed-40d1-8ddc-93671a9c89a520cb7e68-0a7e-46ea-87e0-09fb8d85286e/allowableactions"/> <atom:link type="application/atom+xml;type=entry" rel="describedby" href="http://cmisexample.oasis-open.org/rep1/fba295fd-c8ed-40d1-8ddc-93671a9c89a520cb7e68-0a7e-46ea-87e0-09fb8d85286e/type"/> <atom:link type="application/atomsvc+xml" rel="service" href="http://cmisexample.oasis-open.org/rep1//service"/> <atom:published>2009-10-19T10:09:59.515-072010-01-25T10:20:58.536-08:00</atom:published> <atom:summary type="html">HTML summary of Entry fba295fd-c8ed-40d1-8ddc-93671a9c89a520cb7e68-0a7e-46ea-87e0-09fb8d85286e</atom:summary> <atom:link rel="edit-media" href="http://cmisexample.oasis-open.org/rep1/fba295fd-c8ed-40d1-8ddc-93671a9c89a520cb7e68-0a7e-46ea-87e0-09fb8d85286e/edit-media"/> <atom:link rel="alternate" href="http://cmisexample.oasis-open.org/rep1/fba295fd-c8ed-40d1-8ddc-93671a9c89a520cb7e68-0a7e-46ea-87e0-09fb8d85286e/alternate"/> <atom:link type="application/atom+xml;type=feed" rel="up" href="http://cmisexample.oasis-open.org/rep1/fba295fd-c8ed-40d1-8ddc-93671a9c89a520cb7e68-0a7e-46ea-87e0-09fb8d85286e/parents"/> <atom:link type="application/atom+xml;type=feed" rel="version-history" href="http://cmisexample.oasis-open.org/rep1/fba295fd-c8ed-40d1-8ddc-93671a9c89a520cb7e68-0a7e-46ea-87e0-09fb8d85286e/allversions"/> <atom:link type="application/atom+xml;type=entry" rel="current-version" href="http://cmisexample.oasis-open.org/rep1/fba295fd-c8ed-40d1-8ddc-93671a9c89a520cb7e68-0a7e-46ea-87e0-09fb8d85286e/latest"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/relationships" href="http://cmisexample.oasis-open.org/rep1/fba295fd-c8ed-40d1-8ddc-93671a9c89a520cb7e68-0a7e-46ea-87e0-09fb8d85286e/relationships"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/policies" href="http://cmisexample.oasis-open.org/rep1/fba295fd-c8ed-40d1-8ddc-93671a9c89a520cb7e68-0a7e-46ea-87e0-09fb8d85286e/policies"/> <atom:link type="application/cmisacl+xml" rel="http://docs.oasis-open.org/ns/cmis/link/200908/acl" href="http://cmisexample.oasis-open.org/rep1/fba295fd-c8ed-40d1-8ddc-93671a9c89a520cb7e68-0a7e-46ea-87e0-09fb8d85286e/acl"/> <cmisra:object> <cmis:properties> <cmis:propertyId localName="rep-cmis:objectId" propertyDefinitionId="cmis:objectId"> <cmis:value>fba295fd-c8ed-40d1-8ddc-93671a9c89a520cb7e68-0a7e-46ea-87e0-09fb8d85286e</cmis:value> </cmis:propertyId> </cmis:properties> </cmisra:object> <cmisra:pathSegment>invoice1.pdf</cmisra:pathSegment> </atom:entry> </atom:feed> </cmisra:children> </atom:entry>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 127 of 240

505950605061506250635064506550665067506850695070507150725073507450755076507750785079508050815082508350845085508650875088508950905091509250935094509550965097509850995100510151025103510451055106510751085109511051115112511351145115511651175118511951205121

379380381

Page 128: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<atom:entry> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:content src="http://cmisexample.oasis-open.org/rep1/affc2158-6c8f-4245-a045-688225f8c2ad1de1d476-11fb-47bf-b136-8a8d0b4b030a"/> <atom:id>urn:uuid:affc2158-6c8f-4245-a045-688225f8c2ad1de1d476-11fb-47bf-b136-8a8d0b4b030a</atom:id> <atom:title type="text">CMIS Example Doc as Invoice type</atom:title> <atom:updated>2009-10-19T10:09:59.531-072010-01-25T10:20:58.568-08:00</atom:updated> <atom:link rel="self" href="http://cmisexample.oasis-open.org/rep1/affc2158-6c8f-4245-a045-688225f8c2ad1de1d476-11fb-47bf-b136-8a8d0b4b030a"/> <atom:link rel="edit" href="http://cmisexample.oasis-open.org/rep1/affc2158-6c8f-4245-a045-688225f8c2ad1de1d476-11fb-47bf-b136-8a8d0b4b030a"/> <atom:link type="application/cmis+xml;type=allowableActions" rel="http://docs.oasis-open.org/ns/cmis/link/200908/allowableactions" href="http://cmisexample.oasis-open.org/rep1/affc2158-6c8f-4245-a045-688225f8c2ad1de1d476-11fb-47bf-b136-8a8d0b4b030a/allowableactions"/> <atom:link type="application/atom+xml;type=entry" rel="describedby" href="http://cmisexample.oasis-open.org/rep1/affc2158-6c8f-4245-a045-688225f8c2ad1de1d476-11fb-47bf-b136-8a8d0b4b030a/type"/> <atom:link type="application/atomsvc+xml" rel="service" href="http://cmisexample.oasis-open.org/rep1//service"/> <atom:published>2009-10-19T10:09:59.531-072010-01-25T10:20:58.568-08:00</atom:published> <atom:summary type="html">HTML summary of Entry affc2158-6c8f-4245-a045-688225f8c2ad1de1d476-11fb-47bf-b136-8a8d0b4b030a</atom:summary> <atom:link rel="edit-media" href="http://cmisexample.oasis-open.org/rep1/affc2158-6c8f-4245-a045-688225f8c2ad1de1d476-11fb-47bf-b136-8a8d0b4b030a/edit-media"/> <atom:link rel="alternate" href="http://cmisexample.oasis-open.org/rep1/affc2158-6c8f-4245-a045-688225f8c2ad1de1d476-11fb-47bf-b136-8a8d0b4b030a/alternate"/> <atom:link type="application/atom+xml;type=feed" rel="up" href="http://cmisexample.oasis-open.org/rep1/affc2158-6c8f-4245-a045-688225f8c2ad1de1d476-11fb-47bf-b136-8a8d0b4b030a/parents"/> <atom:link type="application/atom+xml;type=feed" rel="version-history" href="http://cmisexample.oasis-open.org/rep1/affc2158-6c8f-4245-a045-688225f8c2ad1de1d476-11fb-47bf-b136-8a8d0b4b030a/allversions"/> <atom:link type="application/atom+xml;type=entry" rel="current-version" href="http://cmisexample.oasis-open.org/rep1/affc2158-6c8f-4245-a045-688225f8c2ad1de1d476-11fb-47bf-b136-8a8d0b4b030a/latest"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/relationships" href="http://cmisexample.oasis-open.org/rep1/affc2158-6c8f-4245-a045-688225f8c2ad1de1d476-11fb-47bf-b136-8a8d0b4b030a/relationships"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/policies" href="http://cmisexample.oasis-open.org/rep1/affc2158-6c8f-4245-a045-688225f8c2ad1de1d476-11fb-47bf-b136-8a8d0b4b030a/policies"/> <atom:link type="application/cmisacl+xml" rel="http://docs.oasis-open.org/ns/cmis/link/200908/acl" href="http://cmisexample.oasis-open.org/rep1/affc2158-6c8f-4245-a045-688225f8c2ad1de1d476-11fb-47bf-b136-8a8d0b4b030a/acl"/> <cmisra:object> <cmis:properties> <cmis:propertyId localName="rep-cmis:objectId" propertyDefinitionId="cmis:objectId">

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 128 of 240

512251235124512551265127512851295130513151325133513451355136513751385139514051415142514351445145514651475148514951505151515251535154515551565157515851595160516151625163516451655166516751685169517051715172517351745175517651775178517951805181518251835184

382383384

Page 129: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<cmis:value>affc2158-6c8f-4245-a045-688225f8c2ad1de1d476-11fb-47bf-b136-8a8d0b4b030a</cmis:value> </cmis:propertyId> </cmis:properties> </cmisra:object> <cmisra:pathSegment>invoice3.pdf</cmisra:pathSegment> </atom:entry></atom:feed>

Note: This media type is used on links with relation down (see section 3.4.3.2 Hierarchy Navigation Internet Draft Link Relations). When the individual resources are returned by the CMIS repository they will use the atom media type (application/atom+xml)

Please also see the example documents included with the schema.

3.3.5 CMIS ACLMedia Type: application/cmisacl+xmlStarting tag: cmis:acl

This document specifies an Access Control List based on the schema in CMIS Domain Model.

Example:<?xml version="1.0" encoding="UTF-8" standalone="yes"?><cmis:acl xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:app="http://www.w3.org/2007/app" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <cmis:permission> <cmis:principal> <cmis:principalId>Al Brown</cmis:principalId> </cmis:principal> <cmis:permission>cmis:read</cmis:permission> <cmis:permission>cmis:write</cmis:permission> <cmis:permission>cmis:all</cmis:permission> <cmis:permission>publish</cmis:permission> <cmis:direct>true</cmis:direct> </cmis:permission></cmis:acl>

Please also see the example documents included with the schema.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 129 of 240

51855186518751885189519051915192

5193519451955196

51975198

5199

520052015202

52035204

5205520652075208520952105211521252135214521552165217521852195220522152225223

52245225

5226

385386387

Page 130: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

3.4 Atom Extensions for CMIS

3.4.1 Atom Element Extensions

3.4.1.1 AtomPub Workspace

3.4.1.1.1 cmisra:collectionTypeThis element is included inside the app:collection element. This specifies the cmis collection type.

3.4.1.1.2 cmisra:repositoryInfoThis element is included inside the app:workspace element. This specifies information about the CMIS repository.

3.4.1.1.3 cmis:uritemplateThis element is included inside the app:workspace element. This specifies information about URI templates

3.4.1.2 Atom Feed

3.4.1.2.1 cmisra:numItemsThis element is included inside the atom:feed element. This specifies the number of items in the feed.

3.4.1.3 Atom Entry

3.4.1.3.1 cmisra:childrenThis element is included inside the atom:entry element. This includes the children of the atom entry. This element MUST include an atom:feed element.

3.4.1.3.2 cmisra:objectThis element is included inside the atom:entry element for CMIS Document, Folder, Relationship and Policy objects. This specifies the CMIS object information for the atom entry.

3.4.1.3.3 cmisra:pathSegmentThis element is included inside the atom:entry element for CMIS Type Definitions that are filable. This specifies the pathSegment for this object in the folder representing the feed.

3.4.1.3.4 cmisra:relativePathSegmentThis element is included inside the atom:entry element. This specifies the relative pathSegment for the object in that particular folder. This MUST be used only inside an object parents feed.

3.4.1.3.5 cmisra:typeThis element is included inside the atom:entry element for CMIS Type Definitions. This specifies the type definition the atom entry represents.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 130 of 240

5227

5228

5229

52305231

523252335234

523552365237

5238

52395240

5241

524252435244

5245

524652475248

5249

525052515252

5253

525452555256

525752585259

388389390

Page 131: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

3.4.1.3.6 cmisra:contentThis element specifies the content of the atom:entry element. The content is base64 encoded. in the base64 element. The elements of a cmisra:content element are:

mediaType: This contains the media type of the content as described by RFC4288. base64: This contains the base64 content of the file

This element MUST take precedence over atom:content on submission of an atom entry to a repository.

A repository MUST use the atom:content element to return back to the client the content of the document.

Note: This is required when the client has an XML document stored that is might not be well formed and thus would not be able to be included inside atom:content element.

3.4.2 AttributesThese attributes are in the CMIS RestAtom namespace (cmisra).

3.4.2.1 cmisra:idThis attribute is used on the atom:link element to specify the cmis id of the resource. This attribute SHOULD be on all link relations that point to a CMIS object.

This attribute MAY also be on cmisra:type. The value of the attribute on cmis:type MUST be the same as the type definition id.

Example:<?xml version="1.0" encoding="UTF-8" standalone="yes"?><atom:link xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:app="http://www.w3.org/2007/app" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/" type="application/atom+xml;type=feed" rel="down" href="http://cmisexample.oasis-open.org/rep1//children/ba2cb793-6d6d-48cd-b6c2-62dcddedc4b5e170da7d-d322-472d-b1eb-67bdb1ec18ca/1" cmisra:id="ba2cb793-6d6d-48cd-b6c2-62dcddedc4b5e170da7d-d322-472d-b1eb-67bdb1ec18ca"/>

Please also see the example documents included with the schema.

3.4.2.2 cmisra:renditionKindThis attribute is used on the atom:link element with relation alternate to specify the renditionKind of the resource. This attribute SHOULD be on all link elements with relation alternate that are a CMIS rendition.

Example:<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 131 of 240

52605261526252635264

52655266

52675268

526952705271

5272

52735274

527552765277

527852795280

528152825283528452855286528752885289529052915292

52935294

5295

529652975298

529953005301

391392393

Page 132: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<atom:link xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:app="http://www.w3.org/2007/app" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/" type="text/html" rel="alternate" href="http://cmisexample.oasis-open.org/rep1//rendition/ba2cb793-6d6d-48cd-b6c2-62dcddedc4b5e170da7d-d322-472d-b1eb-67bdb1ec18ca/1" cmisra:renditionKind="cmis:thumbnail"/>

Please also see the example documents included with the schema.

3.4.3 CMIS Link Relations The listing below outlines the different link relation types in CMIS. This is in addition to the link relations specified by Atom and Atom Publishing Protocol. The registry for link relations is located at http://www.iana.org/assignments/link-relations/link-relations.xhtml.

The link element with a specified relation MUST be included if client can perform the operation. The repository SHOULD omit the link relation if the operation is not available. The operation may not be available due to a variety of reasons such as access control, administrative policies, or other mechanisms.

Links may have the following attribute in addition to the ones specified by Atom and Atom Publishing Protocol:

(CMIS) id: Specifies the CMIS ID of the resource referenced by the link. Repositories SHOULD include this attribute for elements such as atom:link that point to CMIS resources that have an id.

These are the link relation types specified by CMIS:

3.4.3.1 Existing Link RelationsExisting link relations should be used where appropriate by the implementation. In addition, the following link relations are leveraged for the CMIS specification:

selfo This link relation provides the URI to retrieve this resource again.

o Service: The appropriate service that generated the atom entry or feed.

o Resources: All except AllowableActions, ACL and Content Streams

serviceo The service link relation when provided on a CMIS resource MUST point to an AtomPub

service document with only one workspace element. This workspace element MUST represent the repository containing that resource.

o Media Type: application/atomsvc+xml

o Resources: All except AllowableActions, ACL and Content Streams

describedbyo When used on a CMIS resource, this link relation MUST point to an atom entry that

describes the type of that resource. o Service: getTypeDefinition on specified object

o Media Type: application/atom+xml;type=entry

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 132 of 240

53025303530453055306530753085309

53105311

5312531353145315

53165317531853195320

53215322532353245325

53265327

532853295330533153325333533453355336533753385339534053415342534353445345

394395396

Page 133: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

o Resources: CMIS Document, CMIS Folder, CMIS Relationship, CMIS Policy objects and CMIS Types

viao When used on an Atom Feed document, this link relation MUST point to the atom entry

representing the CMIS resource from whom this feed is derived. o Media Type: application/atom+xml;type=entry

o Resources: All CMIS Feeds and Collections

edit-mediao When used on a CMIS document resource, this link relation MUST point to the URI for

content stream of the CMIS document. This URI MUST be used to set or delete the content stream. This URI MAY be used to retrieve the content stream for the document.

o Service: setContentStream (PUT) , deleteContentStream (DELETE)

o Media Type: Specific to resource

o Resources: CMIS Document

edito When used on a CMIS resource, this link relation MUST provide an URI that can be used

with the HTTP PUT method to modify the atom:entry for the CMIS resource o Service: getObject (GET), updateProperties (PUT)

o Media Type: application/atom+xml;type=entry

o Resources: CMIS Documents, CMIS Folders, CMIS Relationships and CMIS Policies

alternateo This is used to express Renditions on a CMIS resource. See section 3.1.6 Renditions.

o Service: getContentStream for specified rendition

o Resources: CMIS Document, CMIS Folder and CMIS Policies

firsto This is used for Paging. Please see the AtomPub specification.

o Media Type: application/atom+xml;type=feed

o Resources: All Feeds

previouso This is used for Paging. Please see the AtomPub specification.

o Media Type: application/atom+xml;type=feed

o Resources: All Feeds

nexto This is used for Paging. Please see the AtomPub specification.

o Media Type: application/atom+xml;type=feed

o Resources: All Feeds

lasto This is used for Paging. Please see the AtomPub specification.

o Media Type: application/atom+xml;type=feed

o Resources: All Feeds

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 133 of 240

53465347534853495350535153525353535453555356535753585359536053615362536353645365536653675368536953705371537253735374537553765377537853795380538153825383538453855386

397398399

Page 134: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Please see http://www.iana.org/assignments/link-relations/link-relations.xhtml for more information on these link relations.

3.4.3.2 Hierarchy Navigation Internet Draft Link RelationsPlease refer to the Internet Draft here: http://www.ietf.org/internet-drafts/draft-divilly-atom-hierarchy-03.txt.

CMIS leverages the following link relations from the Internet Draft: up

o Service: getFolderParent, getObjectParents, getTypeDefnition, getObject

o Media Type: application/atom+xml;type=feed, application/atom+xml;type=entry

o Resources: CMIS Document, CMIS Folder, CMIS Type Definitions, CMIS Folder Children, CMIS Folder Descendants, CMIS FolderTree, CMIS Type Children, CMIS Type Descendants

This link relation is not included on CMIS Base Type Definitions or the CMIS Root Folder

downo Service: getChildren, getDescendants, getTypeChildren, getTypeDescendants

o Media Type:

For children: application/atom+xml;type=feed For descendants: application/cmistree+xml

The descendants feed resource when retrieved from the CMIS repository will use the Atom Feed Media Type (application/atom+xmll;type=feed)

o Resources: CMIS Folder, Type

3.4.3.3 Versioning Internet Draft Link RelationsPlease refer to the Internet Draft here: http://www.ietf.org/internet-drafts/draft-brown-versioning-link-relations-01.txt.

CMIS leverages the following link relations from the Internet Draft: version-history

o Service: getAllVersions

o Media Type: application/atom+xml;type=feed

o Resources: CMIS Document

current-versiono Service: getObjectForLatestVersion

o Media Type: application/atom+xml;type=entry

o Resources: CMIS Document

working-copyo Service: getObject for private-working-copy specified by

cmis:versionSeriesCheckedOutId propertyo Media Type: application/atom+xml;type=entry

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 134 of 240

538753885389

539053915392539353945395539653975398539954005401540254035404540554065407540854095410

541154125413

54145415541654175418541954205421542254235424542554265427

400401402

Page 135: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

o Resources: CMIS Document

3.4.3.4 CMIS Specific Link RelationsCMIS defines the following link relations:

o http://docs.oasis-open.org/ns/cmis/link/200908/allowableactions

This link relation MUST point to a resource containing a CMIS AllowableActions document for the CMIS resource containing this link relation.

Service: getAllowableActions Media Type: application/cmisallowableactions+xml Resources: CMIS Documents, CMIS Folders, CMIS Policies, and CMIS

Relationshipso http://docs.oasis-open.org/ns/cmis/link/200908/relationships

This link relation MUST point to a resource containing an Atom Feed of CMIS relationship resources for the CMIS resource containing this link relation.

Service: getObjectRelationships Media Type: application/atom+xml;type=feed Resources: CMIS Documents, CMIS Folders, and CMIS Policies

o http://docs.oasis-open.org/ns/cmis/link/200908/source

When used on a CMIS Relationship resource, this link relation MUST point to an atom entry document for the CMIS Resource specified by the cmis:sourceId property on the relationship.

Source Link on Relationship Media Type: application/atom+xml;type=entry Resources: CMIS Relationships

o http://docs.oasis-open.org/ns/cmis/link/200908/target

When used on a CMIS Relationship resource, this link relation MUST point to an atom entry document for the CMIS Resource specified by the cmis:targetId property on the relationship.

Target Link on Relationship Media Type: application/atom+xml;type=entry Resources: CMIS Relationships

o http://docs.oasis-open.org/ns/cmis/link/200908/policies

This link relation MUST point to a resource containing an Atom Feed of CMIS Policy resources for the CMIS resource containing this link relation.

Service: getAppliedPolicies Media Type: application/atom+xml;type=feed Resources: CMIS Documents and CMIS Folders

o http://docs.oasis-open.org/ns/cmis/link/200908/acl

This link relation MUST point to a resource containing a CMIS ACL document for the CMIS resource containing this link relation.

Service: getACL

Media Type: application/cmisacl+xml

Resources: CMIS Documents, CMIS Folders, CMIS Relationships, and CMIS Policies that are securable

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 135 of 240

5428

542954305431543254335434543554365437543854395440544154425443544454455446544754485449545054515452545354545455545654575458545954605461546254635464546554665467

5468

54695470

403404405

Page 136: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

o http://docs.oasis-open.org/ns/cmis/link/200908/changes

This link relation MUST point to an Atom Feed containing the set of changes Service: getContentChanges Media Type: application/atom+xml;type=feed Resources: AtomPub Workspace Element in Service Document

o http://docs.oasis-open.org/ns/cmis/link/200908/foldertree

Used in AtomPub Service Document to identify the folder tree for a specified folder

Service: getFolderTree Media Type: application/atom+xml;type=feed Resources: CMIS Folder, also used in AtomPub Service Document for root folder

o http://docs.oasis-open.org/ns/cmis/link/200908/typedescendants

Used in AtomPub Service Document to identify the base types descendants Service: getTypeDescendants Media Type: application/atom+xml;type=feed Resources: AtomPub Workspace Element in Service Document

o http://docs.oasis-open.org/ns/cmis/link/200908/rootdescendants

Used in AtomPub Service Document to identify the root folder descendants Service: getDescendants for root folder Media Type: application/atom+xml;type=feed Resources: AtomPub Workspace Element in Service Document

3.5 Atom ResourcesFor all Atom Resources used in this specification, the following MUST be followed:

3.5.1 Feeds Any feed MUST be a valid Atom Feed document and conform to the guidelines below for cmis objects:

atom:updated SHOULD be the latest time the folder or its contents was updated. If unknown by the underlying repository, it MUSTbe the current time.

atom:author/atom:name MUST be the CMIS property cmis:createdBy atom:title MUST be the CMIS property cmis:name The atom:link with relation self MUST be generated to return the URI of the feed. If paging or any

other mechanism is used to filter, sort, or change the representation of the feed, the URI MUST point back a resource with the same representation.

A feed SHOULD contain the element app:collection, describing the appropriate media types supported for creation of new entries in the feed

atom:id SHOULD be derived from cmis:objectId. This id MUST be compliant with atom’s specification and be a valid URI.

Feeds MAY be paged via the link relations specified in AtomPub. If more items are available than contained in the feed, then a link with the relation next MUST be included in the feed.

Any feed MUST be a valid Atom Feed document and conform to the guidelines below for cmis types:

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 136 of 240

547154725473547454755476547754785479548054815482548354845485548654875488548954905491

5492

54935494

549554965497549854995500550155025503550455055506550755085509

55105511

406407408

Page 137: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

atom:updated SHOULD be the latest time type definition was updated. If unknown by the underlying repository, it MUSTbe the current time.

atom:author/atom:name is repository specific atom:title MUST be the displayName attribute of the CMIS Type Definition. The atom:link with relation self MUST be generated to return the URI of the feed atom:id SHOULD be derived from the id attribute of the CMIS Type Definition. This id MUST be

compliant with atom’s specification and be a valid URI. Feeds MAY be paged via the link relations specified in AtomPub. If more items are available than

contained in the feed, then a link with the relation next MUST be included in the feed.

If on the root type, all fields are repository specific.

Ordering of entries in a feed is repository-specific if orderBy argument is not specified. If orderBy argument is specified, the order of the entries in the feed SHOULD conform to the ordering specified by the orderBy argument.

Note: Please see feedvalidator.org to validate Atom compliance.

3.5.2 EntriesAt any point where an Atom document of type Entry is sent or returned, it must be a valid Atom Entry document and conform to the guidelines below for a cmis object:

atom:title MUST be the cmis:name property app:edited MUST be cmis:lastModifiedDate atom:updated MUST be cmis:lastModifiedDate atom:published MUST be cmis:createdDate atom:author/atom:name MUST be cmis:createdBy All CMIS properties MUST be exposed in CMIS cmis:properties elements even if they are

duplicated in an atom element atom:id SHOULD be derived from cmis:objectId. This id MUST be compliant with atom’s

specification and be a valid URI. The repository SHOULD populate the atom:summary tag with text that best represents a

summary of the object. For example, an HTML table containing the properties and their values or the description of the document if available.

For Documents that support Content Streams:The repository SHOULD use the atom:content/src attribute to point to the content stream. The client SHOULD use cmisra:content if the content is not well-formed or would have trouble fitting inside an atom:content element. The repository MUST use the cmisra:content element if provided by the client over the atom:content element.

Other Objects (Folders, Relationships, and other Document Types that do not support Content Streams, etc):

The repository MUST comply with the atom specification and have an atom:content element. This is repository specific. Any value in the content field MUST be ignored if the atom entry represents a non-document object by the CMIS repository when the atom entry is POST’ed to a collection or sent to the repository via a PUT.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 137 of 240

551255135514551555165517551855195520

55215522

5523552455255526

55275528

552955305531553255335534553555365537553855395540554155425543

554455455546554755485549

5550555155525553555455555556

409410411

Page 138: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

When POSTing an Atom Document, the Atom elements MUST take precedence over the corresponding writable CMIS property. For example, atom:title will overwrite cmis:name.

At any point where an Atom document of CMIS Type is sent or returned, it must be a valid Atom Entry document and conform to the guidelines below for a cmis type definition:

atom:title MUST be the cmis:displayName The repository SHOULD populate the atom:summary tag with text that best represents a

summary of the object. For example, the type description if available. The repository MUST comply with the atom specification and have an atom:content element. This

is repository specific. Any value in the content field MUST be ignored if the atom entry represents a non-document object by the CMIS repository when the atom entry is POST’ed to a collection or sent to the repository via a PUT.

Any atom element that is not specified is repository-specific.

3.5.2.1 Hierarchical Atom EntriesThe repository SHOULD NOT provide any links to hierarchical objects if those capabilities are not supported with the exception of getTypeDescendants which is required

For atom entries that are hierarchical such as Folder Tree or Descendants, the repository MUST populate a cmisra:children element in the atom:entry with the enclosing feed of its direct children. This pattern continues until the depth is satisfied.

The cmisra:children element that MUST be included ininclude an atom entry::feed element that contains the children entries of this resource.<xs:element name="children" type="atom:feedType" />

If an entry does not contain cmisra:children element, then the entry MAY have children even though it is not represented in the atom entry.

For Example, here is a minimal Atom Entry with CMIS Children Extension Element:<?xml version="1.0" encoding="UTF-8" standalone="yes"?><atom:entry xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:app="http://www.w3.org/2007/app" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <atom:author> <atom:name>Al Brown</atom:name> </atom:author> <atom:content src="http://cmisexample.oasis-open.org/rep1/78a66015-ffd3-4233-85d3-39cad56fa091af1d8c7f-b554-4dfb-bfe1-1f41e4b34fef"/> <atom:id>urn:uuid:78a66015-ffd3-4233-85d3-39cad56fa091af1d8c7f-b554-4dfb-bfe1-1f41e4b34fef</atom:id> <atom:title type="text">CMIS Example Folder as Customer type</atom:title> <atom:updated>2009-10-19T10:09:58.906-072010-01-25T10:20:57.818-08:00</atom:updated> <cmisra:object> <cmis:properties>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 138 of 240

555755585559

5560556155625563556455655566556755685569

557055715572

557355745575

5576557755785579

5580558155825583

558455855586

55875588558955905591559255935594559555965597559855995600560156025603560456055606

412413414

Page 139: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<cmis:propertyId localName="rep-cmis:objectId" propertyDefinitionId="cmis:objectId"> <cmis:value>78a66015-ffd3-4233-85d3-39cad56fa091af1d8c7f-b554-4dfb-bfe1-1f41e4b34fef</cmis:value> </cmis:propertyId> </cmis:properties> </cmisra:object> <cmisra:pathSegment>customer</cmisra:pathSegment> <cmisra:children> <atom:feed> <atom:title type="text">CMIS Example Folder as Customer type</atom:title> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:updated>2009-10-19T10:09:58.906-072010-01-25T10:20:57.818-08:00</atom:updated> <atom:id>urn:uuid:d05a1c90-bb02-42e2-baba-f51366e701c1ce2d65af-b246-454b-90ff-0986d9b05178</atom:id> <atom:link type="application/atom+xml;type=feed" rel="self" href="http://cmisexample.oasis-open.org/rep1/78a66015-ffd3-4233-85d3-39cad56fa091af1d8c7f-b554-4dfb-bfe1-1f41e4b34fef/3"/> <atom:link type="application/atomsvc+xml" rel="service" href="http://cmisexample.oasis-open.org/rep1//service"/> <atom:link type="application/atom+xml;type=entry" rel="via" href="http://cmisexample.oasis-open.org/rep1/78a66015-ffd3-4233-85d3-39cad56fa091af1d8c7f-b554-4dfb-bfe1-1f41e4b34fef"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/foldertree" href="http://cmisexample.oasis-open.org/rep1/78a66015-ffd3-4233-85d3-39cad56fa091af1d8c7f-b554-4dfb-bfe1-1f41e4b34fef/foldertree"/> <atom:link type="application/atom+xml;type=feed" rel="down" href="http://cmisexample.oasis-open.org/rep1/78a66015-ffd3-4233-85d3-39cad56fa091af1d8c7f-b554-4dfb-bfe1-1f41e4b34fef/children"/> <atom:link type="application/atom+xml;type=entry" rel="up" href="http://cmisexample.oasis-open.org/rep1/c84ae842-15a2-4571-93fe-65cca95faa242eb09309-58f7-4627-b735-4d5cf4ba6554"/> <atom:entry> <atom:author> <atom:name>Al Brown</atom:name> </atom:author> <atom:content src="http://cmisexample.oasis-open.org/rep1/78a66015-ffd3-4233-85d3-39cad56fa091af1d8c7f-b554-4dfb-bfe1-1f41e4b34fef"/> <atom:id>urn:uuid:78a66015-ffd3-4233-85d3-39cad56fa091af1d8c7f-b554-4dfb-bfe1-1f41e4b34fef</atom:id> <atom:title type="text">CMIS Example Child of Folder</atom:title> <atom:updated>2009-10-19T10:09:58.906-072010-01-25T10:20:57.818-08:00</atom:updated> <cmisra:object> <cmis:properties> <cmis:propertyId localName="rep-cmis:objectId" propertyDefinitionId="cmis:objectId"> <cmis:value>78a66015-ffd3-4233-85d3-39cad56fa091af1d8c7f-b554-4dfb-bfe1-1f41e4b34fef</cmis:value> </cmis:propertyId> </cmis:properties> </cmisra:object> <cmisra:pathSegment>document</cmisra:pathSegment> </atom:entry>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 139 of 240

560756085609561056115612561356145615561656175618561956205621562256235624562556265627562856295630563156325633563456355636563756385639564056415642564356445645564656475648564956505651565256535654565556565657565856595660566156625663566456655666566756685669

415416417

Page 140: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

</atom:feed> </cmisra:children></atom:entry>

Please also see the example documents included with the schema.

3.6 AtomPub Service Document (Repository)The AtomPub Service Document contains the set of repositories that are available. Each repository is mapped to a app:workspace element in the AtomPub Service document.

CMIS Services exposed:GET: getRepositories, getRepositoryInfo

Media Type: application/atomsvc+xml

How the client will get the initial AtomPub (APP) service document or the URI for the service document is repository specific. Examples are via URI, or loading the service document from disk.

The service document will be available from Atom Entry and Atom Feed documents via a link relationship, service. That AtomPub service document MUST contain only one workspace element which MUST be the workspace representing the repository containing the Atom Entry or Atom Feed document.

A workspace element for a CMIS repository MUST have a collection element for each of following collections: Each collection MUST also contain a cmisra:collectionType attributeelement with the given value:

Root Folder Children Collection: Root folder of the Repositoryo ‘root’ for the children collection of the root folder

o cmisra:collectiontype=’root’

Types Children Collection: Collection containing all the base types in the repositoryo ‘types’ for the children collection

o cmisra:collectiontype=’types’

The workspace element SHOULD contain these collections if the repository supports this functionality: CheckedOut collection: collection containing all checked out documents user can see

o ‘checkedout’

o cmisra:collectiontype=’checkedout’

Query collection: Collection for posting queries to be executedo ‘query’

o cmisra:collectiontype=’query’

Unfiled folder: Folder for posting documents to be unfiled; read can be disabledo ‘unfiled’

o cmisra:collectiontype=’unfiled’

The repository MUST include the URI templates in the workspace elements.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 140 of 240

5670567156725673

5674

567556765677

567856795680

56815682

568356845685

5686568756885689

56905691569256935694569556965697569856995700570157025703570457055706570757085709571057115712

418419420

Page 141: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

The workspace element MUST also contain the following link element with the relation: http://docs.oasis-open.org/ns/cmis/link/200908/typesdescendants:http://docs.oasis-open.org/ns/

cmis/link/200908/typedescendants: This link relation points to the types descendants 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 of the root folder. See Folder Tree resource for more information.

http://docs.oasis-open.org/ns/cmis/link/200908/rootdescendants: This link relation points to the descendants feedRoot 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 element 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.

3.6.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} ishttp://example.org/rep1/getbyid/{id}

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 141 of 240

57135714571557165717

571857195720572157225723572457255726

5728572957305731

5732

573357345735573657375738

57395740574157425743

57445745

5746574757485749

5750575157525753

575457555756

421422423

Page 142: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

If the client wants to find the entry for an object with an id of ‘obj_1’ then the URI would be:http://example.org/rep1/getbyid/obj_1

Arguments that are substituted for URI template parameters MUST be percent escaped according to RFC3986. Please see that RFC for more information.

All variables MUST be in the template.

Structure of URI Template:<xs:complexType name="cmisUriTemplateType">

<xs:sequence><xs:element name="template" type="xs:string" /><xs:element name="type" type="xs:string" /><xs:element name="mediatype" type="xs:string" /><xs:any processContents="lax" namespace="##other"

minOccurs="0"maxOccurs="unbounded" />

</xs:sequence></xs:complexType>

Example of URI Template element in an AtomPub Workspace Element:<?xml version="1.0" encoding="UTF-8" standalone="yes"?><cmisra:uritemplate xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:app="http://www.w3.org/2007/app" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <cmisra:template>http://cmisexample.oasis-open.org/rep1/objectbyid/{id}?filter={filter}&amp;includeAllowableActions={includeAllowableActions}&amp;includePolicyIds={includePolicyIds}&amp;includeRelationships={includeRelationships}&amp;includeACL={includeACL}</cmisra:template> <cmisra:type>objectbyid</cmisra:type> <cmisra:mediatype>application/atom+xml;type=entry</cmisra:mediatype></cmisra:uritemplate>

Please also see the example documents included with the schema.

3.6.1.1 Object By Id This URI template provides a method for creating an URI that directly accesses an atom entry representing documents, folders, policies or relationship objects. See section 3.10 for more information.

Type: objectbyidMedia Type: application/atom+xml;type=entry

Service: getObjectById

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 142 of 240

575757585759

576057615762

57635764

576557665767576857695770577157725773577457755776

57775778577957805781578257835784578557865787578857895790579157925793

57945795

5796

579757985799

580058015802

58035804

5805

424425426

Page 143: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Variables that are supported by the template: {id}: Id of object {filter}: Property Filter {includeAllowableActions}

o Valid values: true, false

{includePolicyIds}: Include Policy Ids:o Valid values: true, false

{includeRelationships}: Include relationshipso Valid values: See enumIncludeRelationships

{includeACL}: Include ACLso Valid values: true, false

{renditionFilter}o Valid values: Please see renditionFilter in CMIS Domain Model

Example:<?xml version="1.0" encoding="UTF-8" standalone="yes"?><cmisra:uritemplate xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:app="http://www.w3.org/2007/app" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <cmisra:template>http://cmisexample.oasis-open.org/rep1/objectbyid/{id}?filter={filter}&amp;includeAllowableActions={includeAllowableActions}&amp;includePolicyIds={includePolicyIds}&amp;includeRelationships={includeRelationships}&amp;includeACL={includeACL}</cmisra:template> <cmisra:type>objectbyid</cmisra:type> <cmisra:mediatype>application/atom+xml;type=entry</cmisra:mediatype></cmisra:uritemplate>

Please also see the example documents included with the schema.

3.6.1.2 Object By PathThis URI template provides a method for creating an URI that directly accesses an atom entry representing documents, folders or policy objects. See section 3.10 for more information.

Type: objectbypathMedia Type: application/atom+xml;type=entry

Service: getObjectByPath

Variables that are supported by the template: {path}: Path of Object {filter}: Property Filter {includeAllowableActions}: Boolean for include Allowable Actions

o Valid values: true, false

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 143 of 240

580658075808580958105811581258135814581558165817581858195820582158225823582458255826582758285829583058315832583358345835

58365837

583858395840

584158425843

58445845

584658475848584958505851

427428429

Page 144: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

{includePolicyIds}: Include Policy Ids:o Valid values: true, false

{includeRelationships}: Include relationshipso Valid values: See enumIncludeRelationships

{includeACL}: Include ACLso Valid values: true, false

{renditionFilter}o Valid values: Please see renditionFilter in CMIS Domain Model

Example:<?xml version="1.0" encoding="UTF-8" standalone="yes"?><cmisra:uritemplate xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:app="http://www.w3.org/2007/app" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <cmisra:template>http://cmisexample.oasis-open.org/rep1/objectbypath?p={path}&amp;filter={filter}&amp;includeAllowableActions={includeAllowableActions}&amp;includePolicyIds={includePolicyIds}&amp;includeRelationships={includeRelationships}&amp;includeACL={includeACL}</cmisra:template> <cmisra:type>objectbypath</cmisra:type> <cmisra:mediatype>application/atom+xml;type=entry</cmisra:mediatype></cmisra:uritemplate>

Please also see the example documents included with the schema.

3.6.1.3 QueryType: queryMedia Type: application/atom+xml;type=feed

Service: query

Variables that are supported by the template: {q}: CMIS Query Statement {searchAllVersions}: Boolean, true if to search all versions {maxItems}: Integer, Max items to return {skipCount}: Integer, Items to skip {includeAllowableActions}: Boolean {includeRelationships}: Boolean

Example:<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 144 of 240

58525853585458555856585758585859586058615862586358645865586658675868586958705871587258735874587558765877

58785879

5880

588158825883

58845885

58865887588858895890589158925893

5894589558965897

430431432

Page 145: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<cmisra:uritemplate xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:app="http://www.w3.org/2007/app" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <cmisra:template>http://cmisexample.oasis-open.org/rep1/query?q={q}&amp;searchAllVersions={searchAllVersions}&amp;maxItems={maxItems}&amp;skipCount={skipCount}&amp;includeAllowableActions={includeAllowableActions}=&amp;includeRelationships={includeRelationships}</cmisra:template> <cmisra:type>query</cmisra:type> <cmisra:mediatype>application/atom+xml;type=feed</cmisra:mediatype></cmisra:uritemplate>

Please also see the example documents included with the schema.

3.6.1.4 Type By IdType: typebyidMedia Type: application/atom+xml;type=entry

Service: getTypeDefinition

Variables that are supported by the template: {id}: CMIS Type Id

Example:<?xml version="1.0" encoding="UTF-8" standalone="yes"?><cmisra:uritemplate xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:app="http://www.w3.org/2007/app" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <cmisra:template>http://cmisexample.oasis-open.org/rep1/type?id={id}</cmisra:template> <cmisra:type>query</cmisra:type> <cmisra:mediatype>application/atom+xml;type=entry</cmisra:mediatype></cmisra:uritemplate>

Please also see the example documents included with the schema.

3.6.2 HTTP Methods

3.6.2.1 GETThis retrieves the AtomPub Service document for a specified repository. This exposes the capabilities defined in getRepositories and getRepositoryInfo in the Domain Model.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 145 of 240

58985899590059015902590359045905590659075908590959105911

59125913

5914

591559165917

59185919

592059215922

592359245925592659275928592959305931593259335934593559365937

59385939

59405941

5942

594359445945

433434435

Page 146: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

The optional argument MAY be specified: repositoryId:

o This query parameter allows a client to specify a different repository than the one that is referenced by the URI.

o If specified, the repository MUST return the AtomPub services document for the specified repository if that repository exists.

o If not specified, the repository MUST return the service document for the repository that is referenced by URI.

3.7 Service CollectionsThese are the collections that are included on an AtomPub Service document in the workspace element.For any HTTP verb not specified on a resource,each implementation MAY chose to implement that HTTP verb in a repository-specific manner.

3.7.1 Root Folder CollectionThis is a collection described in the service document. Please see Folder Children.

3.7.2 Query CollectionThis is a collection for processing queries. If the implementation supports GET on this collection, then the implementation SHOULD at least return a feed consisting of zero or more atom entries. These atom entries should represent persisted objects related to query such as persisted queries, long running queries or search templates.

CMIS Services exposed via HTTP verbs:POST: Query

Media Type: application/atom+xml;type=feedAccept:

MUST support CMIS Query document, MAY support other media type

Link Relations on resulting feed from Query Collection: service: Points to service document containing the CMIS repository. The service document

MUST contain only one workspace element.o Media Type: application/atomsvc+xml

paging link relations as appropriate: first, next, previous, last

The following CMIS Atom extension element MAY be included inside the atom feed: cmisra:numItems

The following CMIS Atom extension element MUST be included inside the atom entries: cmisra:object inside atom:entry

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 146 of 240

594659475948594959505951595259535954

5955

5956595759585959

59605961

59625963596459655966

596759685969

59705971597259735974

597559765977597859795980

598159825983

598459855986

436437438

Page 147: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

3.7.2.1 POSTThis collection MUST accept CMIS Query documents (application/cmisquery+xml).

Upon submission (creation) of a query document, a response must be returned with a Location header representing the feed for that query. If the query cannot be performed and an atom feed returned, the repository MUST return the appropriate HTTP status code. In addition, the server SHOULD return the feed directly. If the server does so, the server should also return the Content-Location header.

The feed returned MUST contain a set of atom entries representing the result set from the query.

The atom entries should contain the bare minimum necessary for Atom compliance [RFC4287]. The atom entries MUST contain the CMIS extension element (cmis:object) containing the properties specified by the query in the select clause of the query statement.

If all the selected properties can be mapped to the same type reference, then the repository MAY include additional information in the atom entry.

Please see http://tools.ietf.org/html/rfc5023#section-5.3.

Status Codes: 201 Success

Headers returned: Location Header Content-Location Header

Link Relations on resulting feed from POST to Query Collection: service: Points to service document containing the CMIS repository. The service document

MUST contain only one workspace element.o Media Type: application/atomsvc+xml

paging link relations as appropriate: first, next, previous, last

Example client request:POST /Query HTTP/1.1Host: example.orgContent-Length: 756Content-Type: application/cmisquery+xml

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><cmis:query xmlns:app="http://www.w3.org/2007/app" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <cmis:statement>SELECT cmis:objectId FROM cmis:document</cmis:statement> <cmis:searchAllVersions>true</cmis:searchAllVersions> <cmis:includeAllowableActions>false</cmis:includeAllowableActions> <cmis:includeRelationships>none</cmis:includeRelationships>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 147 of 240

5987

59885989

59905991599259935994

59955996

5997599859996000

600160026003

60046005

6006600760086009601060116012601360146015601660176018

601960206021602260236024602560266027602860296030603160326033603460356036

439440441

Page 148: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<cmis:renditionFilter>*</cmis:renditionFilter> <cmis:maxItems>50</cmis:maxItems> <cmis:skipCount>0</cmis:skipCount></cmis:query>

Example server response:HTTP/1.1 201 CreatedDate: Mon, 19 Oct 200925 Jan 2010 10:10:01 -070021:00 -0800Content-Length: 1830Content-Type: application/atom+xml;type=feedContent-Location: http://cmisexample.oasis-open.org/rep1/queryresult/6e23b7c6-e377-4a6b-b21c-7450f28b4b5d44ce5b47-ebc3-4513-86e0-d3f46c77d0a8Location: http://cmisexample.oasis-open.org/rep1/queryresult/6e23b7c6-e377-4a6b-b21c-7450f28b4b5d44ce5b47-ebc3-4513-86e0-d3f46c77d0a8

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><atom:feed xmlns:app="http://www.w3.org/2007/app" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <atom:title type="text">CMIS Query Result for SELECT cmis:objectId FROM cmis:document</atom:title> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:updated>2009-10-19T10:10:2010-01.078-07-25T10:21:00.427-08:00</atom:updated> <atom:id>urn:uuid:7fd19974-9597-4eb9-88ca-3a2297cd893c811b1b9b-80f5-4788-b46c-aa77564e294b</atom:id> <atom:link type="application/atom+xml;type=feed" rel="self" href="http://cmisexample.oasis-open.org/rep1/c7f915fb-c222-45c9-8fa2-5062102c62b911355977-434b-4e71-b83a-77dea9878e04/3"/> <atom:link type="application/atomsvc+xml" rel="service" href="http://cmisexample.oasis-open.org/rep1//service"/> <atom:entry> <atom:author> <atom:name>Al Brown</atom:name> </atom:author> <atom:content src="http://cmisexample.oasis-open.org/rep1/b4519062-6b13-4160-8abe-1c43bfbfe32ea3386ea0-0477-4a74-96bd-70d3da1c483a"/> <atom:id>urn:uuid:b4519062-6b13-4160-8abe-1c43bfbfe32ea3386ea0-0477-4a74-96bd-70d3da1c483a</atom:id> <atom:title type="text">Resulting Document</atom:title> <atom:updated>2009-10-19T10:10:2010-01.078-07-25T10:21:00.427-08:00</atom:updated> <cmisra:object> <cmis:properties> <cmis:propertyId queryName="cmis:objectId" localName="rep-cmis:objectId" propertyDefinitionId="cmis:objectId"> <cmis:value>b4519062-6b13-4160-8abe-1c43bfbfe32ea3386ea0-0477-4a74-96bd-70d3da1c483a</cmis:value> </cmis:propertyId> </cmis:properties> </cmisra:object> </atom:entry></atom:feed>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 148 of 240

603760386039604060416042

60436044604560466047604860496050605160526053605460556056605760586059606060616062606360646065606660676068606960706071607260736074607560766077607860796080608160826083608460856086608760886089609060916092609360946095609660976098

442443444

Page 149: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Please also see the example documents included with the schema.

3.7.3 Checked Out CollectionThis is a collection described in the service document that contains allthe private working copies (PWCs) of the checkedout documents in the repository.CMIS Services:

GET: getCheckedOutDocs POST: checkOut

Media Type: application/atom+xml;type=feedAccept:

MUST support Atom Entry Documents with CMIS extensions o application/atom+xml;type=entry or

o application/cmisatom+xml

MAY support other media type

Link Relations: service: Points to service document containing the CMIS repository. The service document

MUST contain only one workspace element.o Media Type: application/atomsvc+xml

paging link relations as appropriate: first, next, previous, last

The following CMIS Atom extension element MAY be included inside the atom feed: cmisra:numItems

The following CMIS Atom extension element MUST be included inside the atom entries: cmisra:object inside atom:entry

3.7.3.1 GETThe following arguments may be supplied. Please see the domain model for more information:

filter folderId maxItems skipCount renditionFilter includeAllowableActions includeRelationships

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 149 of 240

609961006101

6102

610361046105610661076108610961106111611261136114

611561166117611861196120

612161226123

612461256126

6127

612861296130613161326133613461356136

445446447

Page 150: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

3.7.3.2 POSTWhen an atom entry is POST’ed to this collection, the atom entry will be checked out. A Content-Location header MUST be returned containing the location of the private working copy.

Example client request:POST /CheckedOut HTTP/1.1Host: example.orgContent-Length: 1044Content-Type: application/atom+xml;type=entry

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><atom:entry xmlns:app="http://www.w3.org/2007/app" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <atom:author> <atom:name>Al Brown</atom:name> </atom:author> <atom:content src="http://cmisexample.oasis-open.org/rep1/46559af4-db97-471d-b229-d9b27322bf438d32d716-701b-4491-84e8-ad57c8230940"/> <atom:id>urn:uuid:46559af4-db97-471d-b229-d9b27322bf438d32d716-701b-4491-84e8-ad57c8230940</atom:id> <atom:title type="text">CMIS Example Document to checkout</atom:title> <atom:updated>2009-10-19T10:10:2010-01.031-07-25T10:21:00.380-08:00</atom:updated> <cmisra:object> <cmis:properties> <cmis:propertyId localName="rep-cmis:objectId" propertyDefinitionId="cmis:objectId"> <cmis:value>46559af4-db97-471d-b229-d9b27322bf438d32d716-701b-4491-84e8-ad57c8230940</cmis:value> </cmis:propertyId> </cmis:properties> </cmisra:object></atom:entry>

Example server response:HTTP/1.1 201 Created </cmis:propertyId> </cmis:properties> </cmisra:object></atom:entry>

Example server response:HTTP/1.1 201 CreatedDate: Mon, 19 Oct 200925 Jan 2010 10:10:01 -070021:00 -0800Content-Length: 7846Content-Type: application/atom+xml;type=entryContent-Location: http://cmisexample.oasis-open.org/rep1/64f55634-f2de-443c-bf6b-e9e30341581f6cce57fc-4e31-491c-8fab-4aa6e6797dbeLocation: http://cmisexample.oasis-open.org/rep1/64f55634-f2de-443c-bf6b-e9e30341581f6cce57fc-4e31-491c-8fab-4aa6e6797dbe

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 150 of 240

613761386139

6140614161426143614461456146614761486149615061516152615361546155615661576158615961606161616261636164616561666167616861696170617161726173617461756176617761786179618061816182

618361846185618661876188618961906191619261936194448449450

Page 151: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><atom:entry xmlns:app="http://www.w3.org/2007/app" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:content src="http://cmisexample.oasis-open.org/rep1/6cce57fc-4e31-491c-8fab-4aa6e6797dbe"/><?xml version="1.0" encoding="UTF-8" standalone="yes"?><atom:entry xmlns:app="http://www.w3.org/2007/app" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:content src="http://cmisexample.oasis-open.org/rep1/64f55634-f2de-443c-bf6b-e9e30341581f"/> <atom:id>urn:uuid:64f55634-f2de-443c-bf6b-e9e30341581f6cce57fc-4e31-491c-8fab-4aa6e6797dbe</atom:id> <atom:title type="text">CMIS Example Child of Folder</atom:title> <atom:updated>2009-10-19T10:10:2010-01.046-07-25T10:21:00.396-08:00</atom:updated> <atom:link rel="self" href="http://cmisexample.oasis-open.org/rep1/64f55634-f2de-443c-bf6b-e9e30341581f6cce57fc-4e31-491c-8fab-4aa6e6797dbe"/> <atom:link rel="edit" href="http://cmisexample.oasis-open.org/rep1/64f55634-f2de-443c-bf6b-e9e30341581f6cce57fc-4e31-491c-8fab-4aa6e6797dbe"/> <atom:link type="application/cmis+xml;type=allowableActions" rel="http://docs.oasis-open.org/ns/cmis/link/200908/allowableactions" href="http://cmisexample.oasis-open.org/rep1/64f55634-f2de-443c-bf6b-e9e30341581f6cce57fc-4e31-491c-8fab-4aa6e6797dbe/allowableactions"/> <atom:link type="application/atom+xml;type=entry" rel="describedby" href="http://cmisexample.oasis-open.org/rep1/64f55634-f2de-443c-bf6b-e9e30341581f6cce57fc-4e31-491c-8fab-4aa6e6797dbe/type"/> <atom:link type="application/atomsvc+xml" rel="service" href="http://cmisexample.oasis-open.org/rep1//service"/> <atom:published>2009-10-19T10:10:01.046-072010-01-25T10:21:00.396-08:00</atom:published> <atom:summary type="html">HTML summary of Entry 64f55634-f2de-443c-bf6b-e9e30341581f6cce57fc-4e31-491c-8fab-4aa6e6797dbe</atom:summary> <atom:link rel="edit-media" href="http://cmisexample.oasis-open.org/rep1/64f55634-f2de-443c-bf6b-e9e30341581f6cce57fc-4e31-491c-8fab-4aa6e6797dbe/edit-media"/> <atom:link rel="alternate" href="http://cmisexample.oasis-open.org/rep1/64f55634-f2de-443c-bf6b-e9e30341581f6cce57fc-4e31-491c-8fab-4aa6e6797dbe/alternate"/> <atom:link type="application/atom+xml;type=feed" rel="up" href="http://cmisexample.oasis-open.org/rep1/64f55634-f2de-443c-bf6b-e9e30341581f6cce57fc-4e31-491c-8fab-4aa6e6797dbe/parents"/> <atom:link type="application/atom+xml;type=feed" rel="version-history" href="http://cmisexample.oasis-open.org/rep1/64f55634-f2de-443c-bf6b-e9e30341581f6cce57fc-4e31-491c-8fab-4aa6e6797dbe/allversions"/>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 151 of 240

61956196619761986199620062016202620362046205620662076208620962106211621262136214621562166217621862196220622162226223622462256226622762286229623062316232623362346235623662376238623962406241624262436244624562466247624862496250625162526253625462556256

451452453

Page 152: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<atom:link type="application/atom+xml;type=entry" rel="current-version" href="http://cmisexample.oasis-open.org/rep1/64f55634-f2de-443c-bf6b-e9e30341581f6cce57fc-4e31-491c-8fab-4aa6e6797dbe/latest"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/relationships" href="http://cmisexample.oasis-open.org/rep1/64f55634-f2de-443c-bf6b-e9e30341581f6cce57fc-4e31-491c-8fab-4aa6e6797dbe/relationships"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/policies" href="http://cmisexample.oasis-open.org/rep1/64f55634-f2de-443c-bf6b-e9e30341581f6cce57fc-4e31-491c-8fab-4aa6e6797dbe/policies"/> <atom:link type="application/cmisacl+xml" rel="http://docs.oasis-open.org/ns/cmis/link/200908/acl" href="http://cmisexample.oasis-open.org/rep1/64f55634-f2de-443c-bf6b-e9e30341581f6cce57fc-4e31-491c-8fab-4aa6e6797dbe/acl"/> <atom:link type="application/atom+xml;type=feed" rel="working-copy" href="http://cmisexample.oasis-open.org/rep1/64f55634-f2de-443c-bf6b-e9e30341581f6cce57fc-4e31-491c-8fab-4aa6e6797dbe/pwc"/> <cmisra:object> <cmis:properties> <cmis:propertyId localName="rep-cmis:objectId" propertyDefinitionId="cmis:objectId"> <cmis:value>64f55634-f2de-443c-bf6b-e9e30341581f6cce57fc-4e31-491c-8fab-4aa6e6797dbe</cmis:value> </cmis:propertyId> <cmis:propertyId localName="rep-cmis:objectTypeId" propertyDefinitionId="cmis:objectTypeId"> <cmis:value>customer</cmis:value> </cmis:propertyId> <cmis:propertyString localName="rep-cmis:name" propertyDefinitionId="cmis:name"> <cmis:value>CMIS Example Child of Folder</cmis:value> </cmis:propertyString> <cmis:propertyDateTime localName="rep-cmis:creationDate" propertyDefinitionId="cmis:creationDate"> <cmis:value>2009-10-19T10:10:2010-01.046-07-25T10:21:00.396-08:00</cmis:value> </cmis:propertyDateTime> <cmis:propertyDateTime localName="rep-cmis:lastModificationDate" propertyDefinitionId="cmis:lastModificationDate"> <cmis:value>2009-10-19T10:10:2010-01.046-07-25T10:21:00.396-08:00</cmis:value> </cmis:propertyDateTime> <cmis:propertyId localName="rep-cmis:baseTypeId" propertyDefinitionId="cmis:baseTypeId"> <cmis:value>cmis:document</cmis:value> </cmis:propertyId> <cmis:propertyString localName="rep-cmis:lastModifiedBy" propertyDefinitionId="cmis:lastModifiedBy"> <cmis:value>Al Brown</cmis:value> </cmis:propertyString> <cmis:propertyString localName="rep-cmis:createdBy" propertyDefinitionId="cmis:createdBy"> <cmis:value>Al Brown</cmis:value> </cmis:propertyString> <cmis:propertyBoolean localName="rep-cmis:isLatestVersion" propertyDefinitionId="cmis:isLatestVersion"> <cmis:value>true</cmis:value> </cmis:propertyBoolean> <cmis:propertyBoolean localName="rep-cmis:isVersionSeriesCheckedOut" propertyDefinitionId="cmis:isVersionSeriesCheckedOut"> <cmis:value>true</cmis:value>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 152 of 240

625762586259626062616262626362646265626662676268626962706271627262736274627562766277627862796280628162826283628462856286628762886289629062916292629362946295629662976298629963006301630263036304630563066307630863096310631163126313631463156316631763186319

454455456

Page 153: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

</cmis:propertyBoolean> <cmis:propertyBoolean localName="rep-cmis:isMajorVersion" propertyDefinitionId="cmis:isMajorVersion"> <cmis:value>false</cmis:value> </cmis:propertyBoolean> <cmis:propertyBoolean localName="rep-cmis:isLatestMajorVersion" propertyDefinitionId="cmis:isLatestMajorVersion"> <cmis:value>false</cmis:value> </cmis:propertyBoolean> <cmis:propertyBoolean localName="rep-cmis:isImmutable" propertyDefinitionId="cmis:isImmutable"> <cmis:value>false</cmis:value> </cmis:propertyBoolean> <cmis:propertyString localName="rep-cmis:checkinComment" propertyDefinitionId="cmis:checkinComment"> <cmis:value>Checkin comment</cmis:value> </cmis:propertyString> <cmis:propertyString localName="rep-cmis:versionLabel" propertyDefinitionId="cmis:versionLabel"> <cmis:value>0.1</cmis:value> </cmis:propertyString> <cmis:propertyString localName="rep-cmis:contentStreamMimeType" propertyDefinitionId="cmis:contentStreamMimeType"> <cmis:value>text/plain</cmis:value> </cmis:propertyString> <cmis:propertyString localName="rep-cmis:contentStreamFileName" propertyDefinitionId="cmis:contentStreamFileName"> <cmis:value>text.txt</cmis:value> </cmis:propertyString> <cmis:propertyInteger localName="rep-cmis:contentStreamLength" propertyDefinitionId="cmis:contentStreamLength"> <cmis:value>4234</cmis:value> </cmis:propertyInteger> <cmis:propertyString displayName="Keywords for Document" localName="keywords" propertyDefinitionId="keywords"> <cmis:value>document</cmis:value> <cmis:value>example</cmis:value> <cmis:value>sample</cmis:value> <cmis:value>cmis</cmis:value> </cmis:propertyString> <cmis:propertyId localName="rep-cmis:versionSeriesCheckedOutId" propertyDefinitionId="cmis:versionSeriesCheckedOutId"> <cmis:value>64f55634-f2de-443c-bf6b-e9e30341581f6cce57fc-4e31-491c-8fab-4aa6e6797dbe</cmis:value> </cmis:propertyId> <cmis:propertyString localName="rep-cmis:versionSeriesCheckedOutBy" propertyDefinitionId="cmis:versionSeriesCheckedOutBy"> <cmis:value>Al Brown</cmis:value> </cmis:propertyString> </cmis:properties> </cmisra:object></atom:entry>

Please also see the example documents included with the schema.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 153 of 240

63206321632263236324632563266327632863296330633163326333633463356336633763386339634063416342634363446345634663476348634963506351635263536354635563566357635863596360636163626363636463656366636763686369637063716372637363746375

6376

457458459

Page 154: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

3.7.4 Unfiled CollectionThis is a collection described in the service document that contains all the unfiled documents in the repository. This collection MUST be available if unfilingun-filing or multi-filing is supported by the repository. A repository that supports un-filing MAY provide read access (GET). If read access is not provided, the repository SHOULD respond to a read attempt with the HTTP status code 405 (notSupported).CMIS Services:

GET: getUnfiledPOST: removeObjectFromFolder

Media Type: application/atom+xml;type=feedAccept:

MUST support Atom Entry Documents with CMIS extensions o application/atom+xml;type=entry or

o application/cmisatom+xml

MAY support other media type

Link Relations: service: Points to service document containing the CMIS repository. The service document

MUST contain only one workspace element.o Media Type: application/atomsvc+xml

paging link relations as appropriate: first, next, previous, last

The following CMIS Atom extension element MAY be included inside the atom feed: cmisra:numItems

The following CMIS Atom extension element MUST be included inside the atom entries: cmisra:object inside atom:entry

3.7.4.1 GETThe following arguments may be supplied. Please see the domain model for more information:

filter folderId maxItems skipCount includeAllowableActions includeRelationships

3.7.4.2 POSTThis removes the object from all folders in the repository by default. If the optional argument removeFrom is specified, the object will only be removed from that folder only.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 154 of 240

637763786379638063816382638363846385638663876388638963906391

639263936394639563966397

639863996400

640164026403

6404

64056406640764086409641064116412

641364146415

6416

460461462

Page 155: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

If the Atom Entry POST’ed, does not have the CMIS extensions with a valid cmis:objectId, the document does not exist, or the document is not in that folder, the appropriate HTTP status code MUST be returned.

This adheres to AtomPub model. Please see http://tools.ietf.org/html/rfc5023#section-5.3. HTTP Success: 201 Location Header

The following arguments may be supplied. Please see the domain model for more information: removeFrom: For repositories which support multi-filing, this parameter identifies which folder to

remove this object from. If specified, it indicates the folder from which the object shall be moved. If not specified, the object will be removed from all folders.

Example client request:POST /Unfiled HTTP/1.1Host: example.orgContent-Length: 1043Content-Type: application/atom+xml;type=entry

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><atom:entry xmlns:app="http://www.w3.org/2007/app" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <atom:author> <atom:name>Al Brown</atom:name> </atom:author> <atom:content src="http://cmisexample.oasis-open.org/rep1/1f8ceb22-cc15-4d75-9221-00588cd22bdc12aa2bec-6f43-47d1-99ef-21797867173c"/> <atom:id>urn:uuid:1f8ceb22-cc15-4d75-9221-00588cd22bdc12aa2bec-6f43-47d1-99ef-21797867173c</atom:id> <atom:title type="text">CMIS Example Document to unfiled</atom:title> <atom:updated>2009-10-19T10:10:2010-01.078-07-25T10:21:00.427-08:00</atom:updated> <cmisra:object> <cmis:properties> <cmis:propertyId localName="rep-cmis:objectId" propertyDefinitionId="cmis:objectId"> <cmisra:object> <cmis:properties> <cmis:propertyId localName="rep-cmis:objectId" propertyDefinitionId="cmis:objectId"> <cmis:value>1f8ceb22-cc15-4d75-9221-00588cd22bdc12aa2bec-6f43-47d1-99ef-21797867173c</cmis:value> </cmis:propertyId> </cmis:properties> </cmisra:object></atom:entry>

Example server response:HTTP/1.1 201 Created </cmis:propertyId> </cmis:properties> </cmisra:object></atom:entry>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 155 of 240

64176418

6419642064216422

64236424642564266427

642864296430643164326433643464356436643764386439644064416442644364446445644664476448644964506451645264536454645564566457645864596460646164626463646464656466

6467646864696470647164726473

463464465

Page 156: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Example server response:HTTP/1.1 201 CreatedDate: Mon, 19 Oct 200925 Jan 2010 10:10:01 -070021:00 -0800Content-Length: 7234Content-Type: application/atom+xml;type=entryContent-Location: http://cmisexample.oasis-open.org/rep1/queryresult/e2d2c9b3-dab4-4c65-866a-d8006d1bb16f15118373-8911-442b-9774-da3b102f224cLocation: http://cmisexample.oasis-open.org/rep1/queryresult/e2d2c9b3-dab4-4c65-866a-d8006d1bb16f15118373-8911-442b-9774-da3b102f224c

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><atom:entry xmlns:app="http://www.w3.org/2007/app" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:content src="http://cmisexample.oasis-open.org/rep1/<?xml version="1.0" encoding="UTF-8" standalone="yes"?><atom:entry xmlns:app="http://www.w3.org/2007/app" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:content src="http://cmisexample.oasis-open.org/rep1/e2d2c9b3-dab4-4c65-866a-d8006d1bb16f"/>15118373-8911-442b-9774-da3b102f224c"/> <atom:id>urn:uuid:e2d2c9b3-dab4-4c65-866a-d8006d1bb16f15118373-8911-442b-9774-da3b102f224c</atom:id> <atom:title type="text">CMIS Example Document to unfiled</atom:title> <atom:updated>2009-10-19T10:10:2010-01.093-07-25T10:21:00.443-08:00</atom:updated> <atom:link rel="self" href="http://cmisexample.oasis-open.org/rep1/e2d2c9b3-dab4-4c65-866a-d8006d1bb16f15118373-8911-442b-9774-da3b102f224c"/> <atom:link rel="edit" href="http://cmisexample.oasis-open.org/rep1/e2d2c9b3-dab4-4c65-866a-d8006d1bb16f15118373-8911-442b-9774-da3b102f224c"/> <atom:link type="application/cmis+xml;type=allowableActions" rel="http://docs.oasis-open.org/ns/cmis/link/200908/allowableactions" href="http://cmisexample.oasis-open.org/rep1/e2d2c9b3-dab4-4c65-866a-d8006d1bb16f15118373-8911-442b-9774-da3b102f224c/allowableactions"/> <atom:link type="application/atom+xml;type=entry" rel="describedby" href="http://cmisexample.oasis-open.org/rep1/e2d2c9b3-dab4-4c65-866a-d8006d1bb16f15118373-8911-442b-9774-da3b102f224c/type"/> <atom:link type="application/atomsvc+xml" rel="service" href="http://cmisexample.oasis-open.org/rep1//service"/> <atom:published>2009-10-19T10:10:01.093-072010-01-25T10:21:00.443-08:00</atom:published>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 156 of 240

6474647564766477647864796480648164826483648464856486648764886489649064916492649364946495649664976498649965006501650265036504650565066507650865096510651165126513651465156516651765186519652065216522652365246525652665276528652965306531653265336534

466467468

Page 157: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<atom:summary type="html">HTML summary of Entry e2d2c9b3-dab4-4c65-866a-d8006d1bb16f15118373-8911-442b-9774-da3b102f224c</atom:summary> <atom:link rel="edit-media" href="http://cmisexample.oasis-open.org/rep1/e2d2c9b3-dab4-4c65-866a-d8006d1bb16f15118373-8911-442b-9774-da3b102f224c/edit-media"/> <atom:link rel="alternate" href="http://cmisexample.oasis-open.org/rep1/e2d2c9b3-dab4-4c65-866a-d8006d1bb16f15118373-8911-442b-9774-da3b102f224c/alternate"/> <atom:link type="application/atom+xml;type=feed" rel="up" href="http://cmisexample.oasis-open.org/rep1/e2d2c9b3-dab4-4c65-866a-d8006d1bb16f15118373-8911-442b-9774-da3b102f224c/parents"/> <atom:link type="application/atom+xml;type=feed" rel="version-history" href="http://cmisexample.oasis-open.org/rep1/e2d2c9b3-dab4-4c65-866a-d8006d1bb16f15118373-8911-442b-9774-da3b102f224c/allversions"/> <atom:link type="application/atom+xml;type=entry" rel="current-version" href="http://cmisexample.oasis-open.org/rep1/e2d2c9b3-dab4-4c65-866a-d8006d1bb16f15118373-8911-442b-9774-da3b102f224c/latest"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/relationships" href="http://cmisexample.oasis-open.org/rep1/e2d2c9b3-dab4-4c65-866a-d8006d1bb16f15118373-8911-442b-9774-da3b102f224c/relationships"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/policies" href="http://cmisexample.oasis-open.org/rep1/e2d2c9b3-dab4-4c65-866a-d8006d1bb16f15118373-8911-442b-9774-da3b102f224c/policies"/> <atom:link type="application/cmisacl+xml" rel="http://docs.oasis-open.org/ns/cmis/link/200908/acl" href="http://cmisexample.oasis-open.org/rep1/e2d2c9b3-dab4-4c65-866a-d8006d1bb16f15118373-8911-442b-9774-da3b102f224c/acl"/> <cmisra:object> <cmis:properties> <cmis:propertyId localName="rep-cmis:objectId" propertyDefinitionId="cmis:objectId"> <cmisra:object> <cmis:properties> <cmis:propertyId localName="rep-cmis:objectId" propertyDefinitionId="cmis:objectId"> <cmis:value>e2d2c9b3-dab4-4c65-866a-d8006d1bb16f15118373-8911-442b-9774-da3b102f224c</cmis:value> </cmis:propertyId> <cmis:propertyId localName="rep-cmis:objectTypeId" propertyDefinitionId="cmis:objectTypeId"> <cmis:value>customer</cmis:value> </cmis:propertyId> <cmis:propertyString localName="rep-cmis:name" propertyDefinitionId="cmis:name"> <cmis:value>CMIS Example Document to unfiled</cmis:value> </cmis:propertyString> <cmis:propertyDateTime localName="rep-cmis:creationDate" propertyDefinitionId="cmis:creationDate"> <cmis:value>2009-10-19T10:10:2010-01.093-07-25T10:21:00.443-08:00</cmis:value> </cmis:propertyDateTime> <cmis:propertyDateTime localName="rep-cmis:lastModificationDate" propertyDefinitionId="cmis:lastModificationDate"> <cmis:value>2009-10-19T10:10:2010-01.093-07-25T10:21:00.443-08:00</cmis:value> </cmis:propertyDateTime> <cmis:propertyId localName="rep-cmis:baseTypeId" propertyDefinitionId="cmis:baseTypeId"> <cmis:value>cmis:document</cmis:value> </cmis:propertyId>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 157 of 240

65356536653765386539654065416542654365446545654665476548654965506551655265536554655565566557655865596560656165626563656465656566656765686569657065716572657365746575657665776578657965806581658265836584658565866587658865896590659165926593659465956596

469470471

Page 158: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<cmis:propertyString localName="rep-cmis:lastModifiedBy" propertyDefinitionId="cmis:lastModifiedBy"> <cmis:value>Al Brown</cmis:value> </cmis:propertyString> <cmis:propertyString localName="rep-cmis:createdBy" propertyDefinitionId="cmis:createdBy"> <cmis:value>Al Brown</cmis:value> </cmis:propertyString> <cmis:propertyBoolean localName="rep-cmis:isLatestVersion" propertyDefinitionId="cmis:isLatestVersion"> <cmis:value>true</cmis:value> </cmis:propertyBoolean> <cmis:propertyBoolean localName="rep-cmis:isVersionSeriesCheckedOut" propertyDefinitionId="cmis:isVersionSeriesCheckedOut"> <cmis:value>false</cmis:value> </cmis:propertyBoolean> <cmis:propertyBoolean localName="rep-cmis:isMajorVersion" propertyDefinitionId="cmis:isMajorVersion"> <cmis:value>false</cmis:value> </cmis:propertyBoolean> <cmis:propertyBoolean localName="rep-cmis:isLatestMajorVersion" propertyDefinitionId="cmis:isLatestMajorVersion"> <cmis:value>false</cmis:value> </cmis:propertyBoolean> <cmis:propertyBoolean localName="rep-cmis:isImmutable" propertyDefinitionId="cmis:isImmutable"> <cmis:value>false</cmis:value> </cmis:propertyBoolean> <cmis:propertyString localName="rep-cmis:checkinComment" propertyDefinitionId="cmis:checkinComment"> <cmis:value>Checkin comment</cmis:value> </cmis:propertyString> <cmis:propertyString localName="rep-cmis:versionLabel" propertyDefinitionId="cmis:versionLabel"> <cmis:value>0.1</cmis:value> </cmis:propertyString> <cmis:propertyString localName="rep-cmis:contentStreamMimeType" propertyDefinitionId="cmis:contentStreamMimeType"> <cmis:value>text/plain</cmis:value> </cmis:propertyString> <cmis:propertyString localName="rep-cmis:contentStreamFileName" propertyDefinitionId="cmis:contentStreamFileName"> <cmis:value>text.txt</cmis:value> </cmis:propertyString> <cmis:propertyInteger localName="rep-cmis:contentStreamLength" propertyDefinitionId="cmis:contentStreamLength"> <cmis:value>4234</cmis:value> </cmis:propertyInteger> <cmis:propertyString displayName="Keywords for Document" localName="keywords" propertyDefinitionId="keywords"> <cmis:value>document</cmis:value> <cmis:value>example</cmis:value> <cmis:value>sample</cmis:value> <cmis:value>cmis</cmis:value> </cmis:propertyString> </cmis:properties> </cmisra:object></atom:entry>

Please also see the example documents included with the schema.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 158 of 240

65976598659966006601660266036604660566066607660866096610661166126613661466156616661766186619662066216622662366246625662666276628662966306631663266336634663566366637663866396640664166426643664466456646664766486649665066516652665366546655665666576658

472473474

Page 159: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

3.7.5 Types Children CollectionThis is a collection described in the service document that contains the types in the repository under the specified parent type. If no parent type is specified, then the base types are returned in the feed. This feed does not include any nesting and is a flat feed.CMIS Services:GET: getTypeChildrenMedia Type: application/atom+xml;type=feed

Link Relations: service: Points to service document containing the CMIS repository. The service document

MUST contain only one workspace element.o Media Type: application/atomsvc+xml

via: points to the type definition entry whose children represent this feed down: points to the atom feed document representing the descendents collection for this same

type with media type of application/cmistree+xml paging link relations as appropriate: first, next, previous, last up: points to the parent type definition

o If this is a children feed for a base object type, this link is not present.

This feed contains a set of atom entries for each child type definition.

The following CMIS Atom extension element MAY be included inside the atom feed: cmisra:numItems

The following CMIS Atom extension element MUST be included inside the atom entries: cmisra:type inside atom:entry

3.7.5.1 GETThe following arguments may be supplied. Please see the domain model for more information:

includePropertyDefinitions maxItems skipCount typeId

3.8 CollectionsFor any HTTP verb not specified on a resource,each implementation MAY chose to implement that HTTP verb in a repository-specific manner.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 159 of 240

6659

6660666166626663666466656666

6667666866696670667166726673667466756676667766786679

668066816682

668366846685

66866687

668866896690669166926693

669466956696

6697

475476477

Page 160: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

3.8.1 Relationships CollectionThis is the set of relationships available (either source or target or both) from a specific item such as a document, folder or policy. CMIS Services:

GET: getObjectRelationshipsPOST: createRelationship

Media Type: application/atom+xml;type=feedAccept:

MUST support Atom Entry Documents with CMIS extensions o application/atom+xml;type=entry or

o application/cmisatom+xml

MAY support other media type

Link Relations: service: Points to service document containing the CMIS repository. The service document

MUST contain only one workspace element.o Media Type: application/atomsvc+xml

paging link relations as appropriate: first, next, previous, last

The following CMIS Atom extension element MAY be included inside the atom feed: cmisra:numItems

The following CMIS Atom extension element MUST be included inside the atom entries: cmisra:object inside atom:entry

3.8.1.1 GETThe following arguments may be supplied. Please see the domain model for more information:

typeId includeSubRelationshipTypes relationshipDirection maxItems skipCount filter includeAllowableActions

3.8.1.2 POSTWhen an atom entry with CMIS markup is posted to this collection, if that atom entry represents a new CMIS relationship, then that relationship will be created.The server MUST return the appropriate HTTP status code if the source is different than the sourceId or target different than the targetId for the source and targets specified in this collection.The server MUST return the appropriate status code if the cmis:objectTypeId is not specified.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 160 of 240

669866996700670167026703670467056706670767086709

671067116712671367146715

671667176718

671967206721

6722

672367246725672667276728672967306731

673267336734673567366737

6738478479480

Page 161: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Example client request:POST /relationships/source/76a5d5bc-cdfe-42ac-9fde-dd09ad384a71dbf0316c-47b5-47c9-a2fa-f005eb93f0a4 HTTP/1.1Host: example.orgContent-Length: 1432Content-Type: application/atom+xml;type=entry

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><atom:entry xmlns:app="http://www.w3.org/2007/app" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <atom:author> <atom:name>Al Brown</atom:name> </atom:author> <atom:content src="http://cmisexample.oasis-open.org/rep1/235d5fdc-6193-4ec0-8a78-c0da832a06d9dab97641-8c94-4a12-a604-7532980f05cb"/> <atom:id>urn:uuid:235d5fdc-6193-4ec0-8a78-c0da832a06d9dab97641-8c94-4a12-a604-7532980f05cb</atom:id> <atom:title type="text">New Relationship</atom:title> <atom:updated>2009-10-19T10:09:59.796-072010-01-25T10:20:58.864-08:00</atom:updated> <cmisra:object> <cmis:properties> <cmis:propertyId localName="rep-cmis:objectTypeId" propertyDefinitionId="cmis:objectTypeId"> <cmis:value>customerRelationships</cmis:value> </cmis:propertyId> <cmis:propertyId localName="rep-cmis:sourceId" propertyDefinitionId="cmis:sourceId"> <cmis:value>76a5d5bc-cdfe-42ac-9fde-dd09ad384a71dbf0316c-47b5-47c9-a2fa-f005eb93f0a4</cmis:value> </cmis:propertyId> <cmis:propertyId localName="rep-cmis:targetId" propertyDefinitionId="cmis:targetId"> </cmis:propertyId> <cmis:propertyId localName="rep-cmis:targetId" propertyDefinitionId="cmis:targetId"> <cmis:value>5f3afe79-1e78-4ff9-a3bf-782c5a492e11b9baac7d-7584-445e-bcd1-29af9b25bf2f</cmis:value> </cmis:propertyId> </cmis:properties> </cmisra:object></atom:entry>

Example server response:HTTP/1.1 201 Created </cmis:propertyId> </cmis:properties> </cmisra:object></atom:entry>

Example server response:HTTP/1.1 201 CreatedDate: Mon, 19 Oct 200925 Jan 2010 10:09:59 -070020:58 -0800Content-Length: 4684

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 161 of 240

6739674067416742674367446745674667476748674967506751675267536754675567566757675867596760676167626763676467656766676767686769677067716772677367746775677667776778677967806781678267836784678567866787678867896790679167926793

67946795679667976798

481482483

Page 162: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Content-Type: application/atom+xml;type=entryContent-Location: http://cmisexample.oasis-open.org/rep1/5f3287a5-7442-4e5c-8cd2-30900d7a73a6b3006a8f-345b-4c27-86df-3f4b157bb495Location: http://cmisexample.oasis-open.org/rep1/5f3287a5-7442-4e5c-8cd2-30900d7a73a6b3006a8f-345b-4c27-86df-3f4b157bb495

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><atom:entry xmlns:app="http://www.w3.org/2007/app" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:content src="http://cmisexample.oasis-open.org/rep1/5f3287a5-7442-4e5c-8cd2-30900d7a73a6b3006a8f-345b-4c27-86df-3f4b157bb495"/> <atom:id>urn:uuid:5f3287a5-7442-4e5c-8cd2-30900d7a73a6b3006a8f-345b-4c27-86df-3f4b157bb495</atom:id> <atom:title type="text">New Relationship</atom:title> <atom:updated>2009-10-19T10:09:59.812-072010-01-25T10:20:58.880-08:00</atom:updated> <atom:link rel="self" href="http://cmisexample.oasis-open.org/rep1/5f3287a5-7442-4e5c-8cd2-30900d7a73a6b3006a8f-345b-4c27-86df-3f4b157bb495"/> <atom:link rel="edit" href="http://cmisexample.oasis-open.org/rep1/5f3287a5-7442-4e5c-8cd2-30900d7a73a6b3006a8f-345b-4c27-86df-3f4b157bb495"/> <atom:link type="application/cmis+xml;type=allowableActions" rel="http://docs.oasis-open.org/ns/cmis/link/200908/allowableactions" href="http://cmisexample.oasis-open.org/rep1/5f3287a5-7442-4e5c-8cd2-30900d7a73a6b3006a8f-345b-4c27-86df-3f4b157bb495/allowableactions"/> <atom:link type="application/atom+xml;type=entry" rel="describedby" href="http://cmisexample.oasis-open.org/rep1/5f3287a5-7442-4e5c-8cd2-30900d7a73a6b3006a8f-345b-4c27-86df-3f4b157bb495/type"/> <atom:link type="application/atomsvc+xml" rel="service" href="http://cmisexample.oasis-open.org/rep1//service"/> <atom:published>2009-10-19T10:09:59.812-072010-01-25T10:20:58.880-08:00</atom:published> <atom:summary type="html">HTML summary of Entry 5f3287a5-7442-4e5c-8cd2-30900d7a73a6b3006a8f-345b-4c27-86df-3f4b157bb495</atom:summary> <atom:link type="application/atom+xml;type=entry" rel="http://docs.oasis-open.org/ns/cmis/link/200908/source" href="http://cmisexample.oasis-open.org/rep1/5f3287a5-7442-4e5c-8cd2-30900d7a73a6b3006a8f-345b-4c27-86df-3f4b157bb495/source"/> <atom:link type="application/atom+xml;type=entry" rel="http://docs.oasis-open.org/ns/cmis/link/200908/target" href="http://cmisexample.oasis-open.org/rep1/5f3287a5-7442-4e5c-8cd2-30900d7a73a6b3006a8f-345b-4c27-86df-3f4b157bb495/target"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/policies" href="http://cmisexample.oasis-open.org/rep1/5f3287a5-7442-4e5c-8cd2-30900d7a73a6b3006a8f-345b-4c27-86df-3f4b157bb495/policies"/> <atom:link type="application/cmisacl+xml" rel="http://docs.oasis-open.org/ns/cmis/link/200908/acl" href="http://cmisexample.oasis-open.org/rep1/5f3287a5-7442-4e5c-8cd2-30900d7a73a6b3006a8f-345b-4c27-86df-3f4b157bb495/acl"/> <cmisra:object> <cmis:properties>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 162 of 240

67996800680168026803680468056806680768086809681068116812681368146815681668176818681968206821682268236824682568266827682868296830683168326833683468356836683768386839684068416842684368446845684668476848684968506851685268536854685568566857685868596860

484485486

Page 163: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<cmis:propertyId localName="rep-cmis:objectId" propertyDefinitionId="cmis:objectId"> <cmis:value>5f3287a5-7442-4e5c-8cd2-30900d7a73a6b3006a8f-345b-4c27-86df-3f4b157bb495</cmis:value> </cmis:propertyId> <cmis:propertyId localName="rep-cmis:objectTypeId" propertyDefinitionId="cmis:objectTypeId"> <cmis:value>customerRelationships</cmis:value> </cmis:propertyId> <cmis:propertyString localName="rep-cmis:name" propertyDefinitionId="cmis:name"> <cmis:value>New Relationship</cmis:value> </cmis:propertyString> <cmis:propertyDateTime localName="rep-cmis:creationDate" propertyDefinitionId="cmis:creationDate"> <cmis:value>2009-10-19T10:09:59.812-072010-01-25T10:20:58.880-08:00</cmis:value> </cmis:propertyDateTime> <cmis:propertyDateTime localName="rep-cmis:lastModificationDate" propertyDefinitionId="cmis:lastModificationDate"> <cmis:value>2009-10-19T10:09:59.812-072010-01-25T10:20:58.880-08:00</cmis:value> </cmis:propertyDateTime> <cmis:propertyId localName="rep-cmis:baseTypeId" propertyDefinitionId="cmis:baseTypeId"> <cmis:value>cmis:relationship</cmis:value> </cmis:propertyId> <cmis:propertyString localName="rep-cmis:lastModifiedBy" propertyDefinitionId="cmis:lastModifiedBy"> <cmis:value>Al Brown</cmis:value> </cmis:propertyString> <cmis:propertyString localName="rep-cmis:createdBy" propertyDefinitionId="cmis:createdBy"> <cmis:value>Al Brown</cmis:value> </cmis:propertyString> <cmis:propertyId localName="rep-cmis:sourceId" propertyDefinitionId="cmis:sourceId"> <cmis:value>36f25b8d-c920-4d1f-86ab-3fb8d7ea5f97d4551c6d-30bd-4fc2-9c84-a55f11559e89</cmis:value> </cmis:propertyId> <cmis:propertyId localName="rep-cmis:targetId" propertyDefinitionId="cmis:targetId"> <cmis:value>3f4b0e37-a49d-4bf0-b71d-f8ed0c865029fe7e056f-c4bf-42f1-a03e-3ababcf2491d</cmis:value> </cmis:propertyId> </cmis:properties> </cmisra:object></atom:entry>

Please also see the example documents included with the schema.

3.8.2 Folder Children CollectionThis is a collection comprised of all the direct children of a particular folder represented as a feed.CMIS Services:

GET: getChildrenPOST:

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 163 of 240

686168626863686468656866686768686869687068716872687368746875687668776878687968806881688268836884688568866887688868896890689168926893689468956896689768986899690069016902690369046905690669076908690969106911

6912

69136914691569166917

487488489

Page 164: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

createDocumentor createFolder or createPolicyor moveObjector addObjectToFolder

Media Type: application/atom+xml;type=feed

Accept: MUST support Atom Entry Documents with CMIS extensions MAY support other media type

Link Relations: service: Points to service document containing the CMIS repository. The service document

MUST contain only one workspace element.o Media Type: application/atomsvc+xml

via: points to the atom entry of the folder generating this collection up: points to the atom entry document for this folder’s parent

o If the root folder, this link relation MUST NOT be included.

o Media Type: application/atom+xml;type=entry

down: points to the atom feed document representing the descendents feed with a media type of application/cmistree+xml

o If a repository does not support capabilityGetDescendants, then this link SHOULD NOT be included.

http://docs.oasis-open.org/ns/cmis/link/200908/foldertree: Points to the folder tree for this folder. This is represented as a feed with CMIS hierarchy extensions.

o Media Type: application/atom+xml;type=feed

paging link relations as appropriate: first, next, previous, last

The following CMIS Atom extension element MAY be included inside the atom feed: cmisra:numItems

The following CMIS Atom extension element MUST be included inside the atom entries: cmisra:object inside atom:entry cmisra:pathSegment inside atom:entry

3.8.2.1 GETHTTP Code:

200 OK (Success)

The following arguments may be supplied. Please see the domain model for more information: maxItems

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 164 of 240

69186919692069216922

69236924

6925692669276928

69296930693169326933693469356936693769386939694069416942694369446945

694669476948

6949695069516952

6953

695469556956695769586959

490491492

Page 165: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

skipCount filter includeAllowableActions includeRelationships renditionFilter

o If specified, renditions will be returned as links with relation alternate. orderBy includePathSegment

3.8.2.2 POSTCMIS repositories MUST be compliant with RFC5023 for POSTing new entries into a collection. Please see http://tools.ietf.org/html/rfc5023#section-5.3.

HTTP Success: 201 Location Header

The following arguments MAY be supplied. sourceFolderId: This parameter indicates the folder from which the object shall be moved from to

the current specified folder. This parameter is not allowed for create operations.o If specified moveObject will be performed.

o If not specified, addObjectToFolder will be performed.

versioningState: The optional argument versioningState MAY specify additional versioning behavior such as checkIn as major or minor. Please see CMIS Domain Model for more information on this parameter.

POSTing an Atom Entry document with CMIS markup: Adding a document to a folder:If the atom entry has a cmis property cmis:objectId that is valid for the repository, the object will be added to the folder.

When an object is added to the folder, in repositories that do not support multi-filing it will be removed from the previous folder and the operation treated as move. If the repository supports multiple folders, it will be added to the new folder. If the optional argument sourceFolderId is specified, then the object will be removed from the folder specified.

If atom:content is missing from the request, the repository MUST treat the missing atom:content element as an empty atom:content element.Example client request:

POST /obj/8a7761eb-2a0c-4400-b515-964308d6cb5e1cd0d82f-d579-4897-9b0a-ad0917595445?sourceFolderId=0571b0e4-8043-4e48-8a89-448206c2b365313fd58d-2eab-41af-9517-06dadb010d49 HTTP/1.1Host: example.orgContent-Length: 1227Content-Type: application/atom+xml;type=entry

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 165 of 240

69606961696269636964696569666967

69686969697069716972

697369746975697669776978697969806981

69826983698469856986

698769886989699069916992

6993699469956996699769986999700070017002700370047005

493494495

Page 166: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<atom:entry xmlns:app="http://www.w3.org/2007/app" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <atom:author> <atom:name>Al Brown</atom:name> </atom:author> <atom:id>urn:uuid:8a7761eb-2a0c-4400-b515-964308d6cb5e1cd0d82f-d579-4897-9b0a-ad0917595445</atom:id> <atom:title type="text">Document - To Be Moved</atom:title> <atom:updated>2009-10-19T10:09:59.640-072010-01-25T10:20:58.708-08:00</atom:updated> <atom:content src="http://cmisexample.oasis-open.org/rep1//content/8a7761eb-2a0c-4400-b515-964308d6cb5e1cd0d82f-d579-4897-9b0a-ad0917595445"/> <cmisra:object> <cmis:properties> <cmis:propertyId localName="rep-cmis:objectId" propertyDefinitionId="cmis:objectId"> <cmis:value>8a7761eb-2a0c-4400-b515-964308d6cb5e1cd0d82f-d579-4897-9b0a-ad0917595445</cmis:value> </cmis:propertyId> <cmis:propertyId localName="rep-cmis:objectTypeId" propertyDefinitionId="cmis:objectTypeId"> <cmis:value>invoice</cmis:value> </cmis:propertyId> </cmis:properties> </cmisra:object></atom:entry>

Example server response:HTTP/1.1 201 Created </cmis:propertyId> <cmis:propertyId localName="rep-cmis:objectTypeId" propertyDefinitionId="cmis:objectTypeId"> <cmis:value>invoice</cmis:value> </cmis:propertyId> </cmis:properties> </cmisra:object></atom:entry>

Example server response:HTTP/1.1 201 CreatedDate: Mon, 19 Oct 200925 Jan 2010 10:09:59 -070020:58 -0800Content-Length: 7213Content-Type: application/atom+xml;type=entryContent-Location: http://cmisexample.oasis-open.org/rep1/69553581-2311-4aa4-826b-3aa0a8eb8b15b4423b8a-e46e-49fb-8141-4aed91d28b5bLocation: http://cmisexample.oasis-open.org/rep1/69553581-2311-4aa4-826b-3aa0a8eb8b15b4423b8a-e46e-49fb-8141-4aed91d28b5b

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 166 of 240

7006700770087009701070117012701370147015701670177018701970207021702270237024702570267027702870297030703170327033703470357036

7037703870397040704170427043704470457046704770487049705070517052705370547055705670577058705970607061

496497498

Page 167: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<atom:entry xmlns:app="http://www.w3.org/2007/app" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:content src="http://cmisexample.oasis-open.org/rep1/b4423b8a-e46e-49fb-8141-4aed91d28b5b"/><?xml version="1.0" encoding="UTF-8" standalone="yes"?><atom:entry xmlns:app="http://www.w3.org/2007/app" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:content src="http://cmisexample.oasis-open.org/rep1/69553581-2311-4aa4-826b-3aa0a8eb8b15"/> <atom:id>urn:uuid:69553581-2311-4aa4-826b-3aa0a8eb8b15b4423b8a-e46e-49fb-8141-4aed91d28b5b</atom:id> <atom:title type="text">Document - To Be Moved</atom:title> <atom:updated>2009-10-19T10:09:59.671-072010-01-25T10:20:58.786-08:00</atom:updated> <atom:link rel="self" href="http://cmisexample.oasis-open.org/rep1/69553581-2311-4aa4-826b-3aa0a8eb8b15b4423b8a-e46e-49fb-8141-4aed91d28b5b"/> <atom:link rel="edit" href="http://cmisexample.oasis-open.org/rep1/69553581-2311-4aa4-826b-3aa0a8eb8b15b4423b8a-e46e-49fb-8141-4aed91d28b5b"/> <atom:link type="application/cmis+xml;type=allowableActions" rel="http://docs.oasis-open.org/ns/cmis/link/200908/allowableactions" href="http://cmisexample.oasis-open.org/rep1/69553581-2311-4aa4-826b-3aa0a8eb8b15b4423b8a-e46e-49fb-8141-4aed91d28b5b/allowableactions"/> <atom:link type="application/atom+xml;type=entry" rel="describedby" href="http://cmisexample.oasis-open.org/rep1/69553581-2311-4aa4-826b-3aa0a8eb8b15b4423b8a-e46e-49fb-8141-4aed91d28b5b/type"/> <atom:link type="application/atomsvc+xml" rel="service" href="http://cmisexample.oasis-open.org/rep1//service"/> <atom:published>2009-10-19T10:09:59.687-072010-01-25T10:20:58.786-08:00</atom:published> <atom:summary type="html">HTML summary of Entry 69553581-2311-4aa4-826b-3aa0a8eb8b15b4423b8a-e46e-49fb-8141-4aed91d28b5b</atom:summary> <atom:link rel="edit-media" href="http://cmisexample.oasis-open.org/rep1/69553581-2311-4aa4-826b-3aa0a8eb8b15b4423b8a-e46e-49fb-8141-4aed91d28b5b/edit-media"/> <atom:link rel="alternate" href="http://cmisexample.oasis-open.org/rep1/69553581-2311-4aa4-826b-3aa0a8eb8b15b4423b8a-e46e-49fb-8141-4aed91d28b5b/alternate"/> <atom:link type="application/atom+xml;type=feed" rel="up" href="http://cmisexample.oasis-open.org/rep1/69553581-2311-4aa4-826b-3aa0a8eb8b15b4423b8a-e46e-49fb-8141-4aed91d28b5b/parents"/> <atom:link type="application/atom+xml;type=feed" rel="version-history" href="http://cmisexample.oasis-open.org/rep1/69553581-2311-4aa4-826b-3aa0a8eb8b15b4423b8a-e46e-49fb-8141-4aed91d28b5b/allversions"/>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 167 of 240

7062706370647065706670677068706970707071707270737074707570767077707870797080708170827083708470857086708770887089709070917092709370947095709670977098709971007101710271037104710571067107710871097110711171127113711471157116711771187119712071217122

499500501

Page 168: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<atom:link type="application/atom+xml;type=entry" rel="current-version" href="http://cmisexample.oasis-open.org/rep1/69553581-2311-4aa4-826b-3aa0a8eb8b15b4423b8a-e46e-49fb-8141-4aed91d28b5b/latest"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/relationships" href="http://cmisexample.oasis-open.org/rep1/69553581-2311-4aa4-826b-3aa0a8eb8b15b4423b8a-e46e-49fb-8141-4aed91d28b5b/relationships"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/policies" href="http://cmisexample.oasis-open.org/rep1/69553581-2311-4aa4-826b-3aa0a8eb8b15b4423b8a-e46e-49fb-8141-4aed91d28b5b/policies"/> <atom:link type="application/cmisacl+xml" rel="http://docs.oasis-open.org/ns/cmis/link/200908/acl" href="http://cmisexample.oasis-open.org/rep1/69553581-2311-4aa4-826b-3aa0a8eb8b15b4423b8a-e46e-49fb-8141-4aed91d28b5b/acl"/> <cmisra:object> <cmis:properties> <cmis:propertyId localName="rep-cmis:objectId" propertyDefinitionId="cmis:objectId"> <cmis:value>69553581-2311-4aa4-826b-3aa0a8eb8b15b4423b8a-e46e-49fb-8141-4aed91d28b5b</cmis:value> </cmis:propertyId> <cmis:propertyId localName="rep-cmis:objectTypeId" propertyDefinitionId="cmis:objectTypeId"> <cmis:value>invoice</cmis:value> </cmis:propertyId> <cmis:propertyString localName="rep-cmis:name" propertyDefinitionId="cmis:name"> <cmis:value>Document - To Be Moved</cmis:value> </cmis:propertyString> <cmis:propertyDateTime localName="rep-cmis:creationDate" propertyDefinitionId="cmis:creationDate"> <cmis:value>2009-10-19T10:09:59.687-072010-01-25T10:20:58.786-08:00</cmis:value> </cmis:propertyDateTime> <cmis:propertyDateTime localName="rep-cmis:lastModificationDate" propertyDefinitionId="cmis:lastModificationDate"> <cmis:value>2009-10-19T10:09:59.687-072010-01-25T10:20:58.786-08:00</cmis:value> </cmis:propertyDateTime> <cmis:propertyId localName="rep-cmis:baseTypeId" propertyDefinitionId="cmis:baseTypeId"> <cmis:value>cmis:document</cmis:value> </cmis:propertyId> <cmis:propertyString localName="rep-cmis:lastModifiedBy" propertyDefinitionId="cmis:lastModifiedBy"> <cmis:value>Al Brown</cmis:value> </cmis:propertyString> <cmis:propertyString localName="rep-cmis:createdBy" propertyDefinitionId="cmis:createdBy"> <cmis:value>Al Brown</cmis:value> </cmis:propertyString> <cmis:propertyBoolean localName="rep-cmis:isLatestVersion" propertyDefinitionId="cmis:isLatestVersion"> <cmis:value>true</cmis:value> </cmis:propertyBoolean> <cmis:propertyBoolean localName="rep-cmis:isVersionSeriesCheckedOut" propertyDefinitionId="cmis:isVersionSeriesCheckedOut"> <cmis:value>false</cmis:value> </cmis:propertyBoolean> <cmis:propertyBoolean localName="rep-cmis:isMajorVersion" propertyDefinitionId="cmis:isMajorVersion">

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 168 of 240

712371247125712671277128712971307131713271337134713571367137713871397140714171427143714471457146714771487149715071517152715371547155715671577158715971607161716271637164716571667167716871697170717171727173717471757176717771787179718071817182718371847185

502503504

Page 169: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<cmis:value>false</cmis:value> </cmis:propertyBoolean> <cmis:propertyBoolean localName="rep-cmis:isLatestMajorVersion" propertyDefinitionId="cmis:isLatestMajorVersion"> <cmis:value>false</cmis:value> </cmis:propertyBoolean> <cmis:propertyBoolean localName="rep-cmis:isImmutable" propertyDefinitionId="cmis:isImmutable"> <cmis:value>false</cmis:value> </cmis:propertyBoolean> <cmis:propertyString localName="rep-cmis:checkinComment" propertyDefinitionId="cmis:checkinComment"> <cmis:value>Checkin comment</cmis:value> </cmis:propertyString> <cmis:propertyString localName="rep-cmis:versionLabel" propertyDefinitionId="cmis:versionLabel"> <cmis:value>0.1</cmis:value> </cmis:propertyString> <cmis:propertyString localName="rep-cmis:contentStreamMimeType" propertyDefinitionId="cmis:contentStreamMimeType"> <cmis:value>text/plain</cmis:value> </cmis:propertyString> <cmis:propertyString localName="rep-cmis:contentStreamFileName" propertyDefinitionId="cmis:contentStreamFileName"> <cmis:value>text.txt</cmis:value> </cmis:propertyString> <cmis:propertyInteger localName="rep-cmis:contentStreamLength" propertyDefinitionId="cmis:contentStreamLength"> <cmis:value>4234</cmis:value> </cmis:propertyInteger> <cmis:propertyString displayName="Keywords for Document" localName="keywords" propertyDefinitionId="keywords"> <cmis:value>document</cmis:value> <cmis:value>example</cmis:value> <cmis:value>sample</cmis:value> <cmis:value>cmis</cmis:value> </cmis:propertyString> </cmis:properties> </cmisra:object></atom:entry>

Please also see the example documents included with the schema.

Creating a CMIS Object (in that folder):If the cmis:objectId property is missing, the object will be created and then added to the folder. If the cmis:objectId property is present but not a valid object Id, the repository MUST return the appropriate HTTP status code.

For Documents:If Content Stream is not provided and it is required by the type definition, the repository MUST return the appropriate HTTP status code.

Content Streams MAY be provided by any of the following mechanisms:o As part of the atom entry via the src attribute on the content element (AtomPub)

src attribute: Implementers MAY support external references to content

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 169 of 240

7186718771887189719071917192719371947195719671977198719972007201720272037204720572067207720872097210721172127213721472157216721772187219722072217222722372247225722672277228

72297230723172327233

7234723572367237

7238723972407241

505506507

Page 170: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

If the URI in the src attribute is not reachable, then an appropriate http status code should be returned.

o As part of the atom entry inlining via the content element (AtomPub)

Please see the AtomPub specification RFC5023 for the processing model of the content element.

o If the cmisra:content is provided by the client inside the atom:entry, the cmisra:content element MUST take precendence over the atom:content element. (CMIS)

This element cmisra:content is base64 encodedo At a later time (AtomPub)

At a later time by replacing the edit-media link with a new content

The optional argument versioningState MAY specify additional versioning behavior such as checkin.

Example client request:POST /obj/4f833ce6-f53d-4fb5-a268-7c53705a0807bb2b208b-3acd-4abe-9788-8078a239f228 HTTP/1.1Host: example.orgContent-Length: 1190Content-Type: application/atom+xml;type=entry

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><atom:entry xmlns:app="http://www.w3.org/2007/app" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <atom:author> <atom:name>Al Brown</atom:name> </atom:author> <atom:id>urn:uuid:4f833ce6-f53d-4fb5-a268-7c53705a0807bb2b208b-3acd-4abe-9788-8078a239f228</atom:id> <atom:title type="text">New Invoice</atom:title> <atom:updated>2009-10-19T10:09:59.718-072010-01-25T10:20:58.818-08:00</atom:updated> <atom:content type="text">this is the content of the new document</atom:content> <cmisra:object> <cmis:properties> <cmis:propertyId localName="rep-cmis:objectId" propertyDefinitionId="cmis:objectId"> <atom:content type="text">this is the content of the new document</atom:content> <cmisra:object> <cmis:properties> <cmis:propertyId localName="rep-cmis:objectId" propertyDefinitionId="cmis:objectId"> <cmis:value>4f833ce6-f53d-4fb5-a268-7c53705a0807bb2b208b-3acd-4abe-9788-8078a239f228</cmis:value> </cmis:propertyId> <cmis:propertyId localName="rep-cmis:objectTypeId" propertyDefinitionId="cmis:objectTypeId"> <cmis:value>invoice</cmis:value> </cmis:propertyId> </cmis:properties>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 170 of 240

72427243724472457246724772487249725072517252

725372547255

7256725772587259726072617262726372647265726672677268726972707271727272737274727572767277727872797280728172827283728472857286728772887289729072917292729372947295729672977298

508509510

Page 171: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

</cmisra:object></atom:entry>

Example server response:HTTP/1.1 201 Created </cmis:propertyId> <cmis:propertyId localName="rep-cmis:objectTypeId" propertyDefinitionId="cmis:objectTypeId"> <cmis:value>invoice</cmis:value> </cmis:propertyId> </cmis:properties> </cmisra:object></atom:entry>

Example server response:HTTP/1.1 201 CreatedDate: Mon, 19 Oct 200925 Jan 2010 10:09:59 -070020:58 -0800Content-Length: 7191Content-Type: application/atom+xml;type=entryContent-Location: http://cmisexample.oasis-open.org/rep1/8f714453-f9cf-40ae-8d72-ea72987af21213475008-6a20-4454-ad0b-10ea94c4b93dLocation: http://cmisexample.oasis-open.org/rep1/8f714453-f9cf-40ae-8d72-ea72987af21213475008-6a20-4454-ad0b-10ea94c4b93d

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><atom:entry xmlns:app="http://www.w3.org/2007/app" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:content src="http://cmisexample.oasis-open.org/rep1/<?xml version="1.0" encoding="UTF-8" standalone="yes"?><atom:entry xmlns:app="http://www.w3.org/2007/app" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:content src="http://cmisexample.oasis-open.org/rep1/8f714453-f9cf-40ae-8d72-ea72987af212"/>13475008-6a20-4454-ad0b-10ea94c4b93d"/> <atom:id>urn:uuid:8f714453-f9cf-40ae-8d72-ea72987af21213475008-6a20-4454-ad0b-10ea94c4b93d</atom:id> <atom:title type="text">New Invoice</atom:title> <atom:updated>2009-10-19T10:09:59.734-072010-01-25T10:20:58.818-08:00</atom:updated>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 171 of 240

729973007301730273037304730573067307730873097310731173127313

7314731573167317731873197320732173227323732473257326732773287329733073317332733373347335733673377338733973407341734273437344734573467347734873497350735173527353735473557356

511512513

Page 172: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<atom:link rel="self" href="http://cmisexample.oasis-open.org/rep1/8f714453-f9cf-40ae-8d72-ea72987af21213475008-6a20-4454-ad0b-10ea94c4b93d"/> <atom:link rel="edit" href="http://cmisexample.oasis-open.org/rep1/8f714453-f9cf-40ae-8d72-ea72987af21213475008-6a20-4454-ad0b-10ea94c4b93d"/> <atom:link type="application/cmis+xml;type=allowableActions" rel="http://docs.oasis-open.org/ns/cmis/link/200908/allowableactions" href="http://cmisexample.oasis-open.org/rep1/8f714453-f9cf-40ae-8d72-ea72987af21213475008-6a20-4454-ad0b-10ea94c4b93d/allowableactions"/> <atom:link type="application/atom+xml;type=entry" rel="describedby" href="http://cmisexample.oasis-open.org/rep1/8f714453-f9cf-40ae-8d72-ea72987af21213475008-6a20-4454-ad0b-10ea94c4b93d/type"/> <atom:link type="application/atomsvc+xml" rel="service" href="http://cmisexample.oasis-open.org/rep1//service"/> <atom:published>2009-10-19T10:09:59.734-072010-01-25T10:20:58.833-08:00</atom:published> <atom:summary type="html">HTML summary of Entry 8f714453-f9cf-40ae-8d72-ea72987af21213475008-6a20-4454-ad0b-10ea94c4b93d</atom:summary> <atom:link rel="edit-media" href="http://cmisexample.oasis-open.org/rep1/8f714453-f9cf-40ae-8d72-ea72987af21213475008-6a20-4454-ad0b-10ea94c4b93d/edit-media"/> <atom:link rel="alternate" href="http://cmisexample.oasis-open.org/rep1/8f714453-f9cf-40ae-8d72-ea72987af21213475008-6a20-4454-ad0b-10ea94c4b93d/alternate"/> <atom:link type="application/atom+xml;type=feed" rel="up" href="http://cmisexample.oasis-open.org/rep1/8f714453-f9cf-40ae-8d72-ea72987af21213475008-6a20-4454-ad0b-10ea94c4b93d/parents"/> <atom:link type="application/atom+xml;type=feed" rel="version-history" href="http://cmisexample.oasis-open.org/rep1/8f714453-f9cf-40ae-8d72-ea72987af21213475008-6a20-4454-ad0b-10ea94c4b93d/allversions"/> <atom:link type="application/atom+xml;type=entry" rel="current-version" href="http://cmisexample.oasis-open.org/rep1/8f714453-f9cf-40ae-8d72-ea72987af21213475008-6a20-4454-ad0b-10ea94c4b93d/latest"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/relationships" href="http://cmisexample.oasis-open.org/rep1/8f714453-f9cf-40ae-8d72-ea72987af21213475008-6a20-4454-ad0b-10ea94c4b93d/relationships"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/policies" href="http://cmisexample.oasis-open.org/rep1/8f714453-f9cf-40ae-8d72-ea72987af21213475008-6a20-4454-ad0b-10ea94c4b93d/policies"/> <atom:link type="application/cmisacl+xml" rel="http://docs.oasis-open.org/ns/cmis/link/200908/acl" href="http://cmisexample.oasis-open.org/rep1/8f714453-f9cf-40ae-8d72-ea72987af21213475008-6a20-4454-ad0b-10ea94c4b93d/acl"/> <cmisra:object> <cmis:properties> <cmis:propertyId localName="rep-cmis:objectId" propertyDefinitionId="cmis:objectId"> <cmis:value>8f714453-f9cf-40ae-8d72-ea72987af21213475008-6a20-4454-ad0b-10ea94c4b93d</cmis:value> </cmis:propertyId> <cmis:propertyId localName="rep-cmis:objectTypeId" propertyDefinitionId="cmis:objectTypeId"> <cmis:value>invoice</cmis:value> </cmis:propertyId> <cmis:propertyString localName="rep-cmis:name" propertyDefinitionId="cmis:name"> <cmis:value>New Invoice</cmis:value> </cmis:propertyString> <cmis:propertyDateTime localName="rep-cmis:creationDate" propertyDefinitionId="cmis:creationDate">

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 172 of 240

735773587359736073617362736373647365736673677368736973707371737273737374737573767377737873797380738173827383738473857386738773887389739073917392739373947395739673977398739974007401740274037404740574067407740874097410741174127413741474157416741774187419

514515516

Page 173: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<cmis:value>2009-10-19T10:09:59.734-072010-01-25T10:20:58.833-08:00</cmis:value> </cmis:propertyDateTime> <cmis:propertyDateTime localName="rep-cmis:lastModificationDate" propertyDefinitionId="cmis:lastModificationDate"> <cmis:value>2009-10-19T10:09:59.734-072010-01-25T10:20:58.833-08:00</cmis:value> </cmis:propertyDateTime> <cmis:propertyId localName="rep-cmis:baseTypeId" propertyDefinitionId="cmis:baseTypeId"> <cmis:value>cmis:document</cmis:value> </cmis:propertyId> <cmis:propertyString localName="rep-cmis:lastModifiedBy" propertyDefinitionId="cmis:lastModifiedBy"> <cmis:value>Al Brown</cmis:value> </cmis:propertyString> <cmis:propertyString localName="rep-cmis:createdBy" propertyDefinitionId="cmis:createdBy"> <cmis:value>Al Brown</cmis:value> </cmis:propertyString> <cmis:propertyBoolean localName="rep-cmis:isLatestVersion" propertyDefinitionId="cmis:isLatestVersion"> <cmis:value>true</cmis:value> </cmis:propertyBoolean> <cmis:propertyBoolean localName="rep-cmis:isVersionSeriesCheckedOut" propertyDefinitionId="cmis:isVersionSeriesCheckedOut"> <cmis:value>false</cmis:value> </cmis:propertyBoolean> <cmis:propertyBoolean localName="rep-cmis:isMajorVersion" propertyDefinitionId="cmis:isMajorVersion"> <cmis:value>false</cmis:value> </cmis:propertyBoolean> <cmis:propertyBoolean localName="rep-cmis:isLatestMajorVersion" propertyDefinitionId="cmis:isLatestMajorVersion"> <cmis:value>false</cmis:value> </cmis:propertyBoolean> <cmis:propertyBoolean localName="rep-cmis:isImmutable" propertyDefinitionId="cmis:isImmutable"> <cmis:value>false</cmis:value> </cmis:propertyBoolean> <cmis:propertyString localName="rep-cmis:checkinComment" propertyDefinitionId="cmis:checkinComment"> <cmis:value>Checkin comment</cmis:value> </cmis:propertyString> <cmis:propertyString localName="rep-cmis:versionLabel" propertyDefinitionId="cmis:versionLabel"> <cmis:value>0.1</cmis:value> </cmis:propertyString> <cmis:propertyString localName="rep-cmis:contentStreamMimeType" propertyDefinitionId="cmis:contentStreamMimeType"> <cmis:value>text/plain</cmis:value> </cmis:propertyString> <cmis:propertyString localName="rep-cmis:contentStreamFileName" propertyDefinitionId="cmis:contentStreamFileName"> <cmis:value>text.txt</cmis:value> </cmis:propertyString> <cmis:propertyInteger localName="rep-cmis:contentStreamLength" propertyDefinitionId="cmis:contentStreamLength"> <cmis:value>4234</cmis:value> </cmis:propertyInteger> <cmis:propertyString displayName="Keywords for Document" localName="keywords" propertyDefinitionId="keywords">

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 173 of 240

742074217422742374247425742674277428742974307431743274337434743574367437743874397440744174427443744474457446744774487449745074517452745374547455745674577458745974607461746274637464746574667467746874697470747174727473747474757476747774787479748074817482

517518519

Page 174: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<cmis:value>document</cmis:value> <cmis:value>example</cmis:value> <cmis:value>sample</cmis:value> <cmis:value>cmis</cmis:value> </cmis:propertyString> </cmis:properties> </cmisra:object></atom:entry>

Please also see the example documents included with the schema.

POSTing other document formats: (AtomPub)The behavior is repository specific when a non Atom entry or an atom document without the CMIS elements is posted to a folder collection. For example, the repository MAY auto-create a document with a specific type (document) the client could edit. If the repository does not support this scenario or another exception occurs, then the repository MUST return the appropriate HTTP status code.

Optional arguments: versioningState (for createDocument) sourceFolderId (for moveObject)

3.8.3 Policies CollectionThis is an atom feed of all the policy objects currently applied to a specific object. This is the only collection where the URI’s of the objects in the collection MUST be specific to that collection. A DELETE on the policy object in the collection is a removal of the policy from the object NOT a deletion of the policy object itself.

CMIS Services:GET: getAppliedPoliciesPOST: applyPolicy (to object representing this collection of policies)DELETE: removePolicy

Media Type: application/atom+xml;type=feedAccept:

MUST support Atom Entry Documents with CMIS extensions o application/atom+xml;type=entry or

o application/cmisatom+xml

MAY support other media type

Link Relations: service: Points to service document containing the CMIS repository. The service document

MUST contain only one workspace element.o Media Type: application/atomsvc+xml

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 174 of 240

74837484748574867487748874897490749174927493

74947495749674977498749975007501

75027503750475057506

75077508750975107511

75127513751475157516751775187519752075217522

75237524752575267527

520521522

Page 175: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

via: points to the atom entry of the resource generating this collection paging link relations as appropriate: first, next, previous, last

The policy entries displayed here are specific to the object generating this collection. A DELETE method on those URIs will invoke removePolicy().

The following CMIS Atom extension element MAY be included inside the atom feed: cmisra:numItems

The following CMIS Atom extension element MUST be included inside the atom entries: cmisra:object inside atom:entry

3.8.3.1 GETThe following arguments may be supplied. Please see the domain model for more information:

filter

3.8.3.2 POSTWhen an Atom Entry representing a Policy is posted to this collection, the policy will be applied to the object.

Example client request: POST /policies/f6fc3972-ed27-4b49-9412-b4ef2b0f715ef3670f66-62ee-487f-b733-999a69237024 HTTP/1.1Host: example.orgContent-Length: 1039Content-Type: application/atom+xml;type=entry

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><atom:entry xmlns:app="http://www.w3.org/2007/app" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <atom:author> <atom:name>Al Brown</atom:name> </atom:author> <atom:content src="http://cmisexample.oasis-open.org/rep1/f6fc3972-ed27-4b49-9412-b4ef2b0f715ef3670f66-62ee-487f-b733-999a69237024"/> <atom:id>urn:uuid:f6fc3972-ed27-4b49-9412-b4ef2b0f715ef3670f66-62ee-487f-b733-999a69237024</atom:id> <atom:title type="text">Security Policy for Invoices</atom:title> <atom:updated>2009-10-19T10:09:59.765-072010-01-25T10:20:58.849-08:00</atom:updated> <cmisra:object> <cmis:properties> <cmis:propertyId localName="rep-cmis:objectId" propertyDefinitionId="cmis:objectId"> <cmisra:object> <cmis:properties> <cmis:propertyId localName="rep-cmis:objectId" propertyDefinitionId="cmis:objectId">

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 175 of 240

75287529

753075317532

753375347535

753675377538

7539

754075417542

754375447545

754675477548754975507551755275537554755575567557755875597560756175627563756475657566756775687569757075717572757375747575757675777578

523524525

Page 176: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<cmis:value>f6fc3972-ed27-4b49-9412-b4ef2b0f715ef3670f66-62ee-487f-b733-999a69237024</cmis:value> </cmis:propertyId> </cmis:properties> </cmisra:object></atom:entry>

Example server response:HTTP/1.1 201 CreatedDate: Mon, 19 Oct 200925 Jan 2010 10:09:59 -070020:58 -0800Content-Length: 4043Content-Type: application/atom+xml;type=entryContent-Location: http://cmisexample.oasis-open.org/rep1/1ee01165-98cf-45bf-9bce-b6238caa561655cca51b-6cfa-4354-bdfe-690761576116Location: http://cmisexample.oasis-open.org/rep1/1ee01165-98cf-45bf-9bce-b6238caa561655cca51b-6cfa-4354-bdfe-690761576116

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><atom:entry xmlns:app="http://www.w3.org/2007/app" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:content src="http://cmisexample.oasis-open.org/rep1/<?xml version="1.0" encoding="UTF-8" standalone="yes"?><atom:entry xmlns:app="http://www.w3.org/2007/app" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:content src="http://cmisexample.oasis-open.org/rep1/1ee01165-98cf-45bf-9bce-b6238caa5616"/>55cca51b-6cfa-4354-bdfe-690761576116"/> <atom:id>urn:uuid:1ee01165-98cf-45bf-9bce-b6238caa561655cca51b-6cfa-4354-bdfe-690761576116</atom:id> <atom:title type="text">Security Policy for Invoices</atom:title> <atom:updated>2009-10-19T10:09:59.765-072010-01-25T10:20:58.849-08:00</atom:updated> <atom:link rel="self" href="http://cmisexample.oasis-open.org/rep1/1ee01165-98cf-45bf-9bce-b6238caa561655cca51b-6cfa-4354-bdfe-690761576116"/> <atom:link rel="edit" href="http://cmisexample.oasis-open.org/rep1/1ee01165-98cf-45bf-9bce-b6238caa561655cca51b-6cfa-4354-bdfe-690761576116"/> <atom:link type="application/cmis+xml;type=allowableActions" rel="http://docs.oasis-open.org/ns/cmis/link/200908/allowableactions" href="http://cmisexample.oasis-open.org/rep1/1ee01165-98cf-45bf-9bce-b6238caa561655cca51b-6cfa-4354-bdfe-690761576116/allowableactions"/>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 176 of 240

757975807581758275837584758575867587758875897590759175927593759475957596759775987599760076017602760376047605760676077608760976107611761276137614761576167617761876197620762176227623762476257626762776287629763076317632763376347635763676377638

526527528

Page 177: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<atom:link type="application/atom+xml;type=entry" rel="describedby" href="http://cmisexample.oasis-open.org/rep1/1ee01165-98cf-45bf-9bce-b6238caa561655cca51b-6cfa-4354-bdfe-690761576116/type"/> <atom:link type="application/atomsvc+xml" rel="service" href="http://cmisexample.oasis-open.org/rep1//service"/> <atom:published>2009-10-19T10:09:59.781-072010-01-25T10:20:58.849-08:00</atom:published> <atom:summary type="html">HTML summary of Entry 1ee01165-98cf-45bf-9bce-b6238caa561655cca51b-6cfa-4354-bdfe-690761576116</atom:summary> <atom:link type="application/atom+xml;type=feed" rel="up" href="http://cmisexample.oasis-open.org/rep1/1ee01165-98cf-45bf-9bce-b6238caa561655cca51b-6cfa-4354-bdfe-690761576116/parents"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/relationships" href="http://cmisexample.oasis-open.org/rep1/1ee01165-98cf-45bf-9bce-b6238caa561655cca51b-6cfa-4354-bdfe-690761576116/relationships"/> <atom:link type="application/cmisacl+xml" rel="http://docs.oasis-open.org/ns/cmis/link/200908/acl" href="http://cmisexample.oasis-open.org/rep1/1ee01165-98cf-45bf-9bce-b6238caa561655cca51b-6cfa-4354-bdfe-690761576116/acl"/> <cmisra:object> <cmis:properties> <cmis:propertyId localName="rep-cmis:objectId" propertyDefinitionId="cmis:objectId"> <cmisra:object> <cmis:properties> <cmis:propertyId localName="rep-cmis:objectId" propertyDefinitionId="cmis:objectId"> <cmis:value>1ee01165-98cf-45bf-9bce-b6238caa561655cca51b-6cfa-4354-bdfe-690761576116</cmis:value> </cmis:propertyId> <cmis:propertyId localName="rep-cmis:objectTypeId" propertyDefinitionId="cmis:objectTypeId"> <cmis:value>generalSecurityPolicy</cmis:value> </cmis:propertyId> <cmis:propertyString localName="rep-cmis:name" propertyDefinitionId="cmis:name"> <cmis:value>Security Policy for Invoices</cmis:value> </cmis:propertyString> <cmis:propertyDateTime localName="rep-cmis:creationDate" propertyDefinitionId="cmis:creationDate"> <cmis:value>2009-10-19T10:09:59.781-072010-01-25T10:20:58.849-08:00</cmis:value> </cmis:propertyDateTime> <cmis:propertyDateTime localName="rep-cmis:lastModificationDate" propertyDefinitionId="cmis:lastModificationDate"> <cmis:value>2009-10-19T10:09:59.781-072010-01-25T10:20:58.864-08:00</cmis:value> </cmis:propertyDateTime> <cmis:propertyId localName="rep-cmis:baseTypeId" propertyDefinitionId="cmis:baseTypeId"> <cmis:value>cmis:policy</cmis:value> </cmis:propertyId> <cmis:propertyString localName="rep-cmis:lastModifiedBy" propertyDefinitionId="cmis:lastModifiedBy"> <cmis:value>Al Brown</cmis:value> </cmis:propertyString> <cmis:propertyString localName="rep-cmis:createdBy" propertyDefinitionId="cmis:createdBy"> <cmis:value>Al Brown</cmis:value> </cmis:propertyString> </cmis:properties> </cmisra:object>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 177 of 240

763976407641764276437644764576467647764876497650765176527653765476557656765776587659766076617662766376647665766676677668766976707671767276737674767576767677767876797680768176827683768476857686768776887689769076917692769376947695769676977698769977007701

529530531

Page 178: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

</atom:entry>

Please also see the example documents included with the schema.

3.8.3.3 DELETEThis is the only collection where the URI’s of the objects in the collection MUST be specific to that collection. A DELETE on the policy object in the collection is a removal of the policy from the object NOT a deletion of the policy object itself.

3.9 FeedsFor any HTTP verb not specified on a resource,each implementation MAY chose to implement that HTTP verb in a repository-specific manner.

3.9.1 Object Parents FeedThis is the set of parents for a specific object.

CMIS Services:GET: getObjectParents

Media Type: application/atom+xml;type=feed

Link Relations: service: Points to service document containing the CMIS repository. The service document

MUST contain only one workspace element.o Media Type: application/atomsvc+xml

via: points to the atom entry of object who’s parents are represented by this collection

This feed contains a set of atom entries for each parent of the object that MUST contain: cmisra:object inside atom:entry cmisra:relativePathSegment inside atom:entry for the name of the object inside the folder

Example:<?xml version="1.0" encoding="UTF-8" standalone="yes"?><atom:feed xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:app="http://www.w3.org/2007/app" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <atom:title type="text">Parent Feed for 1b43e592-a780-4feb-a0dc-d25de6bf7ab4268d30b5-91a0-47f0-b985-6765e178f0bb</atom:title> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:updated>2009-10-19T10:10:00.562-072010-01-25T10:20:59.818-08:00</atom:updated> <atom:id>urn:uuid:a8fc16cb-d385-4172-b994-da119636d9546f541940-4abf-471b-99f0-8e6f66d53789</atom:id>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 178 of 240

7702770377047705

7706770777087709

7710

771177127713

77147715771677177718

771977207721772277237724

7725772677277728

7729773077317732773377347735773677377738773977407741774277437744774577467747

532533534

Page 179: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<atom:link type="application/atom+xml;type=feed" rel="self" href="http://cmisexample.oasis-open.org/rep1/1b43e592-a780-4feb-a0dc-d25de6bf7ab4268d30b5-91a0-47f0-b985-6765e178f0bb/3"/> <atom:link type="application/atomsvc+xml" rel="service" href="http://cmisexample.oasis-open.org/rep1//service"/> <atom:link type="application/atom+xml;type=entry" rel="via" href="http://cmisexample.oasis-open.org/rep1/1b43e592-a780-4feb-a0dc-d25de6bf7ab4268d30b5-91a0-47f0-b985-6765e178f0bb"/> <atom:link type="application/atom+xml;type=feed" rel="first" href="http://cmisexample.oasis-open.org/rep1/1b43e592-a780-4feb-a0dc-d25de6bf7ab4268d30b5-91a0-47f0-b985-6765e178f0bb/first"/> <atom:link type="application/atom+xml;type=feed" rel="next" href="http://cmisexample.oasis-open.org/rep1/1b43e592-a780-4feb-a0dc-d25de6bf7ab4268d30b5-91a0-47f0-b985-6765e178f0bb/4"/> <atom:link type="application/atom+xml;type=feed" rel="previous" href="http://cmisexample.oasis-open.org/rep1/1b43e592-a780-4feb-a0dc-d25de6bf7ab4268d30b5-91a0-47f0-b985-6765e178f0bb/2"/> <atom:link type="application/atom+xml;type=feed" rel="last" href="http://cmisexample.oasis-open.org/rep1/1b43e592-a780-4feb-a0dc-d25de6bf7ab4268d30b5-91a0-47f0-b985-6765e178f0bb/last"/> <cmisra:numItems>1</cmisra:numItems> <atom:entry> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:content src="http://cmisexample.oasis-open.org/rep1/adb70b59-db45-4da2-81c0-11062fb063bd661d6945-8f75-4dea-8799-7ba07b0e510e"/> <atom:id>urn:uuid:adb70b59-db45-4da2-81c0-11062fb063bd661d6945-8f75-4dea-8799-7ba07b0e510e</atom:id> <atom:title type="text">Customer Folder</atom:title> <atom:updated>2009-10-19T10:10:00.562-072010-01-25T10:20:59.833-08:00</atom:updated> <atom:link rel="self" href="http://cmisexample.oasis-open.org/rep1/adb70b59-db45-4da2-81c0-11062fb063bd661d6945-8f75-4dea-8799-7ba07b0e510e"/> <atom:link rel="edit" href="http://cmisexample.oasis-open.org/rep1/adb70b59-db45-4da2-81c0-11062fb063bd661d6945-8f75-4dea-8799-7ba07b0e510e"/> <atom:link type="application/cmis+xml;type=allowableActions" rel="http://docs.oasis-open.org/ns/cmis/link/200908/allowableactions" href="http://cmisexample.oasis-open.org/rep1/adb70b59-db45-4da2-81c0-11062fb063bd661d6945-8f75-4dea-8799-7ba07b0e510e/allowableactions"/> <atom:link type="application/atom+xml;type=entry" rel="describedby" href="http://cmisexample.oasis-open.org/rep1/adb70b59-db45-4da2-81c0-11062fb063bd661d6945-8f75-4dea-8799-7ba07b0e510e/type"/> <atom:link type="application/atomsvc+xml" rel="service" href="http://cmisexample.oasis-open.org/rep1//service"/> <atom:published>2009-10-19T10:10:00.562-072010-01-25T10:20:59.833-08:00</atom:published> <atom:summary type="html">HTML summary of Entry adb70b59-db45-4da2-81c0-11062fb063bd661d6945-8f75-4dea-8799-7ba07b0e510e</atom:summary> <atom:link type="application/atom+xml;type=entry" rel="up" href="http://cmisexample.oasis-open.org/rep1/adb70b59-db45-4da2-81c0-11062fb063bd661d6945-8f75-4dea-8799-7ba07b0e510e/up"/> <atom:link type="application/atom+xml;type=feed" rel="down" href="http://cmisexample.oasis-open.org/rep1/adb70b59-db45-4da2-81c0-11062fb063bd661d6945-8f75-4dea-8799-7ba07b0e510e/children"/> <atom:link type="application/cmistree+xml" rel="down" href="http://cmisexample.oasis-open.org/rep1/adb70b59-db45-4da2-81c0-11062fb063bd661d6945-8f75-4dea-8799-7ba07b0e510e/tree"/>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 179 of 240

77487749775077517752775377547755775677577758775977607761776277637764776577667767776877697770777177727773777477757776777777787779778077817782778377847785778677877788778977907791779277937794779577967797779877997800780178027803780478057806780778087809

535536537

Page 180: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/foldertree" href="http://cmisexample.oasis-open.org/rep1/adb70b59-db45-4da2-81c0-11062fb063bd661d6945-8f75-4dea-8799-7ba07b0e510e/foldertree"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/relationships" href="http://cmisexample.oasis-open.org/rep1/adb70b59-db45-4da2-81c0-11062fb063bd661d6945-8f75-4dea-8799-7ba07b0e510e/relationships"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/policies" href="http://cmisexample.oasis-open.org/rep1/adb70b59-db45-4da2-81c0-11062fb063bd661d6945-8f75-4dea-8799-7ba07b0e510e/policies"/> <atom:link type="application/cmisacl+xml" rel="http://docs.oasis-open.org/ns/cmis/link/200908/acl" href="http://cmisexample.oasis-open.org/rep1/adb70b59-db45-4da2-81c0-11062fb063bd661d6945-8f75-4dea-8799-7ba07b0e510e/acl"/> <cmisra:object> <cmis:properties> <cmis:propertyId localName="rep-cmis:objectId" propertyDefinitionId="cmis:objectId"> <cmis:value>adb70b59-db45-4da2-81c0-11062fb063bd661d6945-8f75-4dea-8799-7ba07b0e510e</cmis:value> </cmis:propertyId> <cmis:propertyId localName="rep-cmis:objectTypeId" propertyDefinitionId="cmis:objectTypeId"> <cmis:value>customer</cmis:value> </cmis:propertyId> <cmis:propertyString localName="rep-cmis:name" propertyDefinitionId="cmis:name"> <cmis:value>Customer Folder</cmis:value> </cmis:propertyString> <cmis:propertyDateTime localName="rep-cmis:creationDate" propertyDefinitionId="cmis:creationDate"> <cmis:value>2009-10-19T10:10:00.562-072010-01-25T10:20:59.833-08:00</cmis:value> </cmis:propertyDateTime> <cmis:propertyDateTime localName="rep-cmis:lastModificationDate" propertyDefinitionId="cmis:lastModificationDate"> <cmis:value>2009-10-19T10:10:00.562-072010-01-25T10:20:59.833-08:00</cmis:value> </cmis:propertyDateTime> <cmis:propertyId localName="rep-cmis:baseTypeId" propertyDefinitionId="cmis:baseTypeId"> <cmis:value>cmis:folder</cmis:value> </cmis:propertyId> <cmis:propertyString localName="rep-cmis:lastModifiedBy" propertyDefinitionId="cmis:lastModifiedBy"> <cmis:value>Al Brown</cmis:value> </cmis:propertyString> <cmis:propertyString localName="rep-cmis:createdBy" propertyDefinitionId="cmis:createdBy"> <cmis:value>Al Brown</cmis:value> </cmis:propertyString> <cmis:propertyId localName="rep-cmis:parentId" propertyDefinitionId="cmis:parentId"> <cmis:value>adb70b59-db45-4da2-81c0-11062fb063bdup661d6945-8f75-4dea-8799-7ba07b0e510eup</cmis:value> </cmis:propertyId> </cmis:properties> </cmisra:object> <cmisra:relativePathSegment>customer1</cmisra:relativePathSegment> </atom:entry></atom:feed>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 180 of 240

781078117812781378147815781678177818781978207821782278237824782578267827782878297830783178327833783478357836783778387839784078417842784378447845784678477848784978507851785278537854785578567857785878597860786178627863786478657866786778687869787078717872

538539540

Page 181: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Please also see the example documents included with the schema.

3.9.1.1 GETThe following arguments may be supplied. Please see the domain model for more information:

filter includeAllowableActions includeRelationships renditionFilter includeRelativePathSegment

o If true, then the cmisra:relativePathSegment element willMUST be included in the response.

3.9.2 ChangesThis is a link relationship described in the service document that contains the changes in the repository in the workspace element. The link relation pointing to this feed is http://docs.oasis-open.org/ns/cmis/link/200908/changes.

The ChangeLog Token is specified in the URI specified by the paging link notations. Through this binding it is not possible to retrieve the ChangeLog Token from the URIs.

CMIS Services:GET: getContentChanges()

Media Type: application/atom+xml;type=feedLink Relations:

service: Points to service document containing the CMIS repository. The service document MUST contain only one workspace element.

o Media Type: application/atomsvc+xml

paging link relations as appropriate: first, next, previous, lasto ChangeLogToken is incorporated into the URI specified by the next link relation

This feed MUST be ordered from oldest first to newest.

If the next changes does not exist yet, the link relation next MAY be available. If the next link relation is not available, the client should revisit the feed in the future and look for new items and the next link relation.

The following CMIS Atom extension element MAY be included inside the atom feed: cmisra:numItems

The following CMIS Atom extension element MUST be included inside the atom entries: cmisra:object inside atom:entry

Example:cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 181 of 240

78737874

787578767877787878797880788178827883

7884788578867887

788878897890

789178927893789478957896789778987899790079017902

7903790479057906

790779087909

791079117912

79137914541542543

Page 182: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><atom:feed xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:app="http://www.w3.org/2007/app" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <atom:title type="text">changelog feed</atom:title> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:updated>2009-10-19T10:092010-01-25T10:20:59.953-07255-08:00</atom:updated> <atom:id>urn:uuid:04393e94-6888-404e-b9de-765cf769b5de0bfc5306-fc76-4cd8-a0c0-7653dd43c0ff</atom:id> <atom:link type="application/atom+xml;type=feed" rel="self" href="http://cmisexample.oasis-open.org/rep1/oId/3"/> <atom:link type="application/atomsvc+xml" rel="service" href="http://cmisexample.oasis-open.org/rep1//service"/> <atom:link type="application/atom+xml;type=feed" rel="first" href="http://cmisexample.oasis-open.org/rep1/oId/first"/> <atom:link type="application/atom+xml;type=feed" rel="next" href="http://cmisexample.oasis-open.org/rep1/oId/4"/> <atom:link type="application/atom+xml;type=feed" rel="previous" href="http://cmisexample.oasis-open.org/rep1/oId/2"/> <atom:link type="application/atom+xml;type=feed" rel="last" href="http://cmisexample.oasis-open.org/rep1/oId/last"/> <cmisra:numItems>2</cmisra:numItems> <atom:entry> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:content src="http://cmisexample.oasis-open.org/rep1/2ff37143-0d0d-4c1a-948d-bd8311261c1f3f724c1d-12c8-43f2-919f-674df52b6ebd"/> <atom:id>urn:uuid:2ff37143-0d0d-4c1a-948d-bd8311261c1f3f724c1d-12c8-43f2-919f-674df52b6ebd</atom:id> <atom:title type="text">CMIS Example Folder as Customer Policy type</atom:title> <atom:updated>2009-10-19T10:092010-01-25T10:20:59.953-07255-08:00</atom:updated> <atom:link rel="self" href="http://cmisexample.oasis-open.org/rep1/2ff37143-0d0d-4c1a-948d-bd8311261c1f3f724c1d-12c8-43f2-919f-674df52b6ebd"/> <atom:link rel="edit" href="http://cmisexample.oasis-open.org/rep1/2ff37143-0d0d-4c1a-948d-bd8311261c1f3f724c1d-12c8-43f2-919f-674df52b6ebd"/> <atom:link type="application/cmis+xml;type=allowableActions" rel="http://docs.oasis-open.org/ns/cmis/link/200908/allowableactions" href="http://cmisexample.oasis-open.org/rep1/2ff37143-0d0d-4c1a-948d-bd8311261c1f3f724c1d-12c8-43f2-919f-674df52b6ebd/allowableactions"/> <atom:link type="application/atom+xml;type=entry" rel="describedby" href="http://cmisexample.oasis-open.org/rep1/2ff37143-0d0d-4c1a-948d-bd8311261c1f3f724c1d-12c8-43f2-919f-674df52b6ebd/type"/> <atom:link type="application/atomsvc+xml" rel="service" href="http://cmisexample.oasis-open.org/rep1//service"/> <atom:published>2009-10-19T10:092010-01-25T10:20:59.953-07255-08:00</atom:published> <atom:summary type="html">HTML summary of Entry 2ff37143-0d0d-4c1a-948d-bd8311261c1f3f724c1d-12c8-43f2-919f-674df52b6ebd</atom:summary>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 182 of 240

79157916791779187919792079217922792379247925792679277928792979307931793279337934793579367937793879397940794179427943794479457946794779487949795079517952795379547955795679577958795979607961796279637964796579667967796879697970797179727973797479757976

544545546

Page 183: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<atom:link type="application/atom+xml;type=entry" rel="up" href="http://cmisexample.oasis-open.org/rep1/2ff37143-0d0d-4c1a-948d-bd8311261c1f3f724c1d-12c8-43f2-919f-674df52b6ebd/up"/> <atom:link type="application/atom+xml;type=feed" rel="down" href="http://cmisexample.oasis-open.org/rep1/2ff37143-0d0d-4c1a-948d-bd8311261c1f3f724c1d-12c8-43f2-919f-674df52b6ebd/children"/> <atom:link type="application/cmistree+xml" rel="down" href="http://cmisexample.oasis-open.org/rep1/2ff37143-0d0d-4c1a-948d-bd8311261c1f3f724c1d-12c8-43f2-919f-674df52b6ebd/tree"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/foldertree" href="http://cmisexample.oasis-open.org/rep1/2ff37143-0d0d-4c1a-948d-bd8311261c1f3f724c1d-12c8-43f2-919f-674df52b6ebd/foldertree"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/relationships" href="http://cmisexample.oasis-open.org/rep1/2ff37143-0d0d-4c1a-948d-bd8311261c1f3f724c1d-12c8-43f2-919f-674df52b6ebd/relationships"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/policies" href="http://cmisexample.oasis-open.org/rep1/2ff37143-0d0d-4c1a-948d-bd8311261c1f3f724c1d-12c8-43f2-919f-674df52b6ebd/policies"/> <atom:link type="application/cmisacl+xml" rel="http://docs.oasis-open.org/ns/cmis/link/200908/acl" href="http://cmisexample.oasis-open.org/rep1/2ff37143-0d0d-4c1a-948d-bd8311261c1f3f724c1d-12c8-43f2-919f-674df52b6ebd/acl"/> <cmisra:object> <cmis:properties> <cmis:propertyId localName="rep-cmis:objectId" propertyDefinitionId="cmis:objectId"> <cmis:value>2ff37143-0d0d-4c1a-948d-bd8311261c1f3f724c1d-12c8-43f2-919f-674df52b6ebd</cmis:value> </cmis:propertyId> <cmis:propertyId localName="rep-cmis:objectTypeId" propertyDefinitionId="cmis:objectTypeId"> <cmis:value>customerpolicy</cmis:value> </cmis:propertyId> <cmis:propertyString localName="rep-cmis:name" propertyDefinitionId="cmis:name"> <cmis:value>CMIS Example Folder as Customer Policy type</cmis:value> </cmis:propertyString> <cmis:propertyDateTime localName="rep-cmis:creationDate" propertyDefinitionId="cmis:creationDate"> <cmis:value>2009-10-19T10:092010-01-25T10:20:59.953-07255-08:00</cmis:value> </cmis:propertyDateTime> <cmis:propertyDateTime localName="rep-cmis:lastModificationDate" propertyDefinitionId="cmis:lastModificationDate"> <cmis:value>2009-10-19T10:092010-01-25T10:20:59.953-07255-08:00</cmis:value> </cmis:propertyDateTime> <cmis:propertyId localName="rep-cmis:baseTypeId" propertyDefinitionId="cmis:baseTypeId"> <cmis:value>cmis:folder</cmis:value> </cmis:propertyId> <cmis:propertyString localName="rep-cmis:lastModifiedBy" propertyDefinitionId="cmis:lastModifiedBy"> <cmis:value>Al Brown</cmis:value> </cmis:propertyString> <cmis:propertyString localName="rep-cmis:createdBy" propertyDefinitionId="cmis:createdBy"> <cmis:value>Al Brown</cmis:value> </cmis:propertyString>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 183 of 240

797779787979798079817982798379847985798679877988798979907991799279937994799579967997799879998000800180028003800480058006800780088009801080118012801380148015801680178018801980208021802280238024802580268027802880298030803180328033803480358036803780388039

547548549

Page 184: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<cmis:propertyId localName="rep-cmis:parentId" propertyDefinitionId="cmis:parentId"> <cmis:value>2ff37143-0d0d-4c1a-948d-bd8311261c1fup3f724c1d-12c8-43f2-919f-674df52b6ebdup</cmis:value> </cmis:propertyId> </cmis:properties> <cmis:changeEventInfo> <cmis:changeType>updated</cmis:changeType> <cmis:changeTime>2009-10-19T10:092010-01-25T10:20:59.953-07255-08:00</cmis:changeTime> </cmis:changeEventInfo> </cmisra:object> <cmisra:pathSegment>policy</cmisra:pathSegment> </atom:entry> <atom:entry> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:content src="http://cmisexample.oasis-open.org/rep1/95715cc8-5f9c-45ce-8c54-4c2d8d7c44fc6e27bada-b5a2-4a39-be2c-269806eb0d42"/> <atom:id>urn:uuid:95715cc8-5f9c-45ce-8c54-4c2d8d7c44fc6e27bada-b5a2-4a39-be2c-269806eb0d42</atom:id> <atom:title type="text">CMIS Example Document</atom:title> <atom:updated>2009-10-19T10:092010-01-25T10:20:59.968-07255-08:00</atom:updated> <atom:link rel="self" href="http://cmisexample.oasis-open.org/rep1/95715cc8-5f9c-45ce-8c54-4c2d8d7c44fc6e27bada-b5a2-4a39-be2c-269806eb0d42"/> <atom:link rel="edit" href="http://cmisexample.oasis-open.org/rep1/95715cc8-5f9c-45ce-8c54-4c2d8d7c44fc6e27bada-b5a2-4a39-be2c-269806eb0d42"/> <atom:link type="application/cmis+xml;type=allowableActions" rel="http://docs.oasis-open.org/ns/cmis/link/200908/allowableactions" href="http://cmisexample.oasis-open.org/rep1/95715cc8-5f9c-45ce-8c54-4c2d8d7c44fc6e27bada-b5a2-4a39-be2c-269806eb0d42/allowableactions"/> <atom:link type="application/atom+xml;type=entry" rel="describedby" href="http://cmisexample.oasis-open.org/rep1/95715cc8-5f9c-45ce-8c54-4c2d8d7c44fc6e27bada-b5a2-4a39-be2c-269806eb0d42/type"/> <atom:link type="application/atomsvc+xml" rel="service" href="http://cmisexample.oasis-open.org/rep1//service"/> <atom:published>2009-10-19T10:092010-01-25T10:20:59.968-07255-08:00</atom:published> <atom:summary type="html">HTML summary of Entry 95715cc8-5f9c-45ce-8c54-4c2d8d7c44fc6e27bada-b5a2-4a39-be2c-269806eb0d42</atom:summary> <atom:link rel="edit-media" href="http://cmisexample.oasis-open.org/rep1/95715cc8-5f9c-45ce-8c54-4c2d8d7c44fc6e27bada-b5a2-4a39-be2c-269806eb0d42/edit-media"/> <atom:link rel="alternate" href="http://cmisexample.oasis-open.org/rep1/95715cc8-5f9c-45ce-8c54-4c2d8d7c44fc6e27bada-b5a2-4a39-be2c-269806eb0d42/alternate"/> <atom:link type="application/atom+xml;type=feed" rel="up" href="http://cmisexample.oasis-open.org/rep1/95715cc8-5f9c-45ce-8c54-4c2d8d7c44fc6e27bada-b5a2-4a39-be2c-269806eb0d42/parents"/> <atom:link type="application/atom+xml;type=feed" rel="version-history" href="http://cmisexample.oasis-open.org/rep1/95715cc8-5f9c-45ce-8c54-4c2d8d7c44fc6e27bada-b5a2-4a39-be2c-269806eb0d42/allversions"/> <atom:link type="application/atom+xml;type=entry" rel="current-version" href="http://cmisexample.oasis-open.org/rep1/95715cc8-5f9c-45ce-8c54-4c2d8d7c44fc6e27bada-b5a2-4a39-be2c-269806eb0d42/latest"/>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 184 of 240

8040804180428043804480458046804780488049805080518052805380548055805680578058805980608061806280638064806580668067806880698070807180728073807480758076807780788079808080818082808380848085808680878088808980908091809280938094809580968097809880998100

550551552

Page 185: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/relationships" href="http://cmisexample.oasis-open.org/rep1/95715cc8-5f9c-45ce-8c54-4c2d8d7c44fc6e27bada-b5a2-4a39-be2c-269806eb0d42/relationships"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/policies" href="http://cmisexample.oasis-open.org/rep1/95715cc8-5f9c-45ce-8c54-4c2d8d7c44fc6e27bada-b5a2-4a39-be2c-269806eb0d42/policies"/> <atom:link type="application/cmisacl+xml" rel="http://docs.oasis-open.org/ns/cmis/link/200908/acl" href="http://cmisexample.oasis-open.org/rep1/95715cc8-5f9c-45ce-8c54-4c2d8d7c44fc6e27bada-b5a2-4a39-be2c-269806eb0d42/acl"/> <cmisra:object> <cmis:properties> <cmis:propertyId localName="rep-cmis:objectId" propertyDefinitionId="cmis:objectId"> <cmis:value>95715cc8-5f9c-45ce-8c54-4c2d8d7c44fc6e27bada-b5a2-4a39-be2c-269806eb0d42</cmis:value> </cmis:propertyId> <cmis:propertyId localName="rep-cmis:objectTypeId" propertyDefinitionId="cmis:objectTypeId"> <cmis:value>document</cmis:value> </cmis:propertyId> <cmis:propertyString localName="rep-cmis:name" propertyDefinitionId="cmis:name"> <cmis:value>CMIS Example Document</cmis:value> </cmis:propertyString> <cmis:propertyDateTime localName="rep-cmis:creationDate" propertyDefinitionId="cmis:creationDate"> <cmis:value>2009-10-19T10:092010-01-25T10:20:59.968-07271-08:00</cmis:value> </cmis:propertyDateTime> <cmis:propertyDateTime localName="rep-cmis:lastModificationDate" propertyDefinitionId="cmis:lastModificationDate"> <cmis:value>2009-10-19T10:092010-01-25T10:20:59.968-07271-08:00</cmis:value> </cmis:propertyDateTime> <cmis:propertyId localName="rep-cmis:baseTypeId" propertyDefinitionId="cmis:baseTypeId"> <cmis:value>cmis:document</cmis:value> </cmis:propertyId> <cmis:propertyString localName="rep-cmis:lastModifiedBy" propertyDefinitionId="cmis:lastModifiedBy"> <cmis:value>Al Brown</cmis:value> </cmis:propertyString> <cmis:propertyString localName="rep-cmis:createdBy" propertyDefinitionId="cmis:createdBy"> <cmis:value>Al Brown</cmis:value> </cmis:propertyString> <cmis:propertyBoolean localName="rep-cmis:isLatestVersion" propertyDefinitionId="cmis:isLatestVersion"> <cmis:value>true</cmis:value> </cmis:propertyBoolean> <cmis:propertyBoolean localName="rep-cmis:isVersionSeriesCheckedOut" propertyDefinitionId="cmis:isVersionSeriesCheckedOut"> <cmis:value>false</cmis:value> </cmis:propertyBoolean> <cmis:propertyBoolean localName="rep-cmis:isMajorVersion" propertyDefinitionId="cmis:isMajorVersion"> <cmis:value>false</cmis:value> </cmis:propertyBoolean>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 185 of 240

81018102810381048105810681078108810981108111811281138114811581168117811881198120812181228123812481258126812781288129813081318132813381348135813681378138813981408141814281438144814581468147814881498150815181528153815481558156815781588159816081618162

553554555

Page 186: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<cmis:propertyBoolean localName="rep-cmis:isLatestMajorVersion" propertyDefinitionId="cmis:isLatestMajorVersion"> <cmis:value>false</cmis:value> </cmis:propertyBoolean> <cmis:propertyBoolean localName="rep-cmis:isImmutable" propertyDefinitionId="cmis:isImmutable"> <cmis:value>false</cmis:value> </cmis:propertyBoolean> <cmis:propertyString localName="rep-cmis:checkinComment" propertyDefinitionId="cmis:checkinComment"> <cmis:value>Checkin comment</cmis:value> </cmis:propertyString> <cmis:propertyString localName="rep-cmis:versionLabel" propertyDefinitionId="cmis:versionLabel"> <cmis:value>0.1</cmis:value> </cmis:propertyString> <cmis:propertyString localName="rep-cmis:contentStreamMimeType" propertyDefinitionId="cmis:contentStreamMimeType"> <cmis:value>text/plain</cmis:value> </cmis:propertyString> <cmis:propertyString localName="rep-cmis:contentStreamFileName" propertyDefinitionId="cmis:contentStreamFileName"> <cmis:value>text.txt</cmis:value> </cmis:propertyString> <cmis:propertyInteger localName="rep-cmis:contentStreamLength" propertyDefinitionId="cmis:contentStreamLength"> <cmis:value>4234</cmis:value> </cmis:propertyInteger> <cmis:propertyString displayName="Keywords for Document" localName="keywords" propertyDefinitionId="keywords"> <cmis:value>document</cmis:value> <cmis:value>example</cmis:value> <cmis:value>sample</cmis:value> <cmis:value>cmis</cmis:value> </cmis:propertyString> </cmis:properties> <cmis:changeEventInfo> <cmis:changeType>updated</cmis:changeType> <cmis:changeTime>2009-10-19T10:092010-01-25T10:20:59.968-07271-08:00</cmis:changeTime> </cmis:changeEventInfo> </cmisra:object> <cmisra:pathSegment>invoice.pdf</cmisra:pathSegment> </atom:entry></atom:feed>

Please also see the example documents included with the schema.

3.9.2.1 GETThe following optional parameters may be supplied:

filter maxItems includeACL includePolicyIds includeProperties filter

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 186 of 240

816381648165816681678168816981708171817281738174817581768177817881798180818181828183818481858186818781888189819081918192819381948195819681978198819982008201820282038204820582068207

82088209

82108211821282138214821582168217

556557558

Page 187: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

changeLogToken: If this parameter is specified, start the changes from the specified token. The changeLogToken is embedded in the paging link relations for normal iteration through the change list.

3.9.3 Folder DescendantsThis is a hierarchical feed comprising items under a specified folder to a specified depth. This is available via the link relation down with the application/cmistree+xml media type. Please see the Hierarchical Atom Entries for more information on format.

If a repository does not support capabilityGetDescendants, then these resources SHOULD NOT be exposed.

CMIS Services:GET: getDescendantsDELETE: deleteTree

Media Type: application/atom+xml;type=feed

Link Relations: service: Points to service document containing the CMIS repository. The service document

MUST contain only one workspace element.o Media Type: application/atomsvc+xml

via: points to the atom entry of the folder generating this collection up: points to the atom entry document for this folder’s parent

o Media Type: application/atom+xml;type=entry

o If the root folder, this link relation MUST not be included.

down: o points to the atom feed document representing the children feed for this same folder with

media type of application/atom+xml;type=entryo Since this is the descendants, the descendants link SHOULD NOT be included

paging link relations MAY be included as appropriate: first, next, previous, lasto Repositories may support these paging link relations on a particular cmisra:children

element. http://docs.oasis-open.org/ns/cmis/link/200908/foldertree: Points to the folder tree for this folder

The following CMIS Atom extension element MAY be included inside the atom feed: cmisra:numItems

The following CMIS Atom extension element MUST be included inside the atom entries: cmisra:object inside atom:entry cmisra:pathSegment inside atom:entry cmisra:children inside atom:entry

Example:<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 187 of 240

821882198220

8221822282238224

822582268227

82288229823082318232

82338234823582368237823882398240824182428243824482458246824782488249

825082518252

82538254825582568257

825882598260

559560561

Page 188: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<atom:feed xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:app="http://www.w3.org/2007/app" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <atom:title type="text">Feed for folder1</atom:title> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:updated>2009-10-19T10:10:00.203-072010-01-25T10:20:59.364-08:00</atom:updated> <atom:id>urn:uuid:83638fc5-90e7-4d03-bd04-1a4cc5c5c98ecb0a47d4-8d09-46f9-9b09-584acad684af</atom:id> <atom:link type="application/atom+xml;type=feed" rel="self" href="http://cmisexample.oasis-open.org/rep1/80dfb434-883b-4850-871d-6524c1ec2a64f083dd6f-1465-4516-97ce-040ec0c7c05a/3"/> <atom:link type="application/atomsvc+xml" rel="service" href="http://cmisexample.oasis-open.org/rep1//service"/> <atom:link type="application/atom+xml;type=entry" rel="via" href="http://cmisexample.oasis-open.org/rep1/80dfb434-883b-4850-871d-6524c1ec2a64f083dd6f-1465-4516-97ce-040ec0c7c05a"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/foldertree" href="http://cmisexample.oasis-open.org/rep1/80dfb434-883b-4850-871d-6524c1ec2a64f083dd6f-1465-4516-97ce-040ec0c7c05a/foldertree"/> <atom:link type="application/atom+xml;type=feed" rel="down" href="http://cmisexample.oasis-open.org/rep1/80dfb434-883b-4850-871d-6524c1ec2a64f083dd6f-1465-4516-97ce-040ec0c7c05a/children"/> <atom:link type="application/atom+xml;type=entry" rel="up" href="http://cmisexample.oasis-open.org/rep1/ba8910f0-0e99-4cda-a1f6-befce0fa20e703dcf5b8-5f82-45a1-b276-44d88069eec3"/> <cmisra:numItems>1</cmisra:numItems> <atom:entry> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:content src="http://cmisexample.oasis-open.org/rep1/c2e574a0-2d30-4834-b8a3-6333b33181c38e5a512c-8f2d-4387-a283-f3f30bbc312f"/> <atom:id>urn:uuid:c2e574a0-2d30-4834-b8a3-6333b33181c38e5a512c-8f2d-4387-a283-f3f30bbc312f</atom:id> <atom:title type="text">CMIS Example Folder as Customer type</atom:title> <atom:updated>2009-10-19T10:10:00.203-072010-01-25T10:20:59.364-08:00</atom:updated> <atom:link rel="self" href="http://cmisexample.oasis-open.org/rep1/c2e574a0-2d30-4834-b8a3-6333b33181c38e5a512c-8f2d-4387-a283-f3f30bbc312f"/> <atom:link rel="edit" href="http://cmisexample.oasis-open.org/rep1/c2e574a0-2d30-4834-b8a3-6333b33181c38e5a512c-8f2d-4387-a283-f3f30bbc312f"/> <atom:link type="application/cmis+xml;type=allowableActions" rel="http://docs.oasis-open.org/ns/cmis/link/200908/allowableactions" href="http://cmisexample.oasis-open.org/rep1/c2e574a0-2d30-4834-b8a3-6333b33181c38e5a512c-8f2d-4387-a283-f3f30bbc312f/allowableactions"/> <atom:link type="application/atom+xml;type=entry" rel="describedby" href="http://cmisexample.oasis-open.org/rep1/c2e574a0-2d30-4834-b8a3-6333b33181c38e5a512c-8f2d-4387-a283-f3f30bbc312f/type"/> <atom:link type="application/atomsvc+xml" rel="service" href="http://cmisexample.oasis-open.org/rep1//service"/>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 188 of 240

826182628263826482658266826782688269827082718272827382748275827682778278827982808281828282838284828582868287828882898290829182928293829482958296829782988299830083018302830383048305830683078308830983108311831283138314831583168317831883198320832183228323

562563564

Page 189: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<atom:published>2009-10-19T10:10:00.203-072010-01-25T10:20:59.380-08:00</atom:published> <atom:summary type="html">HTML summary of Entry c2e574a0-2d30-4834-b8a3-6333b33181c38e5a512c-8f2d-4387-a283-f3f30bbc312f</atom:summary> <atom:link type="application/atom+xml;type=entry" rel="up" href="http://cmisexample.oasis-open.org/rep1/c2e574a0-2d30-4834-b8a3-6333b33181c38e5a512c-8f2d-4387-a283-f3f30bbc312f/up"/> <atom:link type="application/atom+xml;type=feed" rel="down" href="http://cmisexample.oasis-open.org/rep1/c2e574a0-2d30-4834-b8a3-6333b33181c38e5a512c-8f2d-4387-a283-f3f30bbc312f/children"/> <atom:link type="application/cmistree+xml" rel="down" href="http://cmisexample.oasis-open.org/rep1/c2e574a0-2d30-4834-b8a3-6333b33181c38e5a512c-8f2d-4387-a283-f3f30bbc312f/tree"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/foldertree" href="http://cmisexample.oasis-open.org/rep1/c2e574a0-2d30-4834-b8a3-6333b33181c38e5a512c-8f2d-4387-a283-f3f30bbc312f/foldertree"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/relationships" href="http://cmisexample.oasis-open.org/rep1/c2e574a0-2d30-4834-b8a3-6333b33181c38e5a512c-8f2d-4387-a283-f3f30bbc312f/relationships"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/policies" href="http://cmisexample.oasis-open.org/rep1/c2e574a0-2d30-4834-b8a3-6333b33181c38e5a512c-8f2d-4387-a283-f3f30bbc312f/policies"/> <atom:link type="application/cmisacl+xml" rel="http://docs.oasis-open.org/ns/cmis/link/200908/acl" href="http://cmisexample.oasis-open.org/rep1/c2e574a0-2d30-4834-b8a3-6333b33181c38e5a512c-8f2d-4387-a283-f3f30bbc312f/acl"/> <cmisra:object> <cmis:properties> <cmis:propertyId localName="rep-cmis:objectId" propertyDefinitionId="cmis:objectId"> <cmis:value>c2e574a0-2d30-4834-b8a3-6333b33181c38e5a512c-8f2d-4387-a283-f3f30bbc312f</cmis:value> </cmis:propertyId> <cmis:propertyId localName="rep-cmis:objectTypeId" propertyDefinitionId="cmis:objectTypeId"> <cmis:value>customer</cmis:value> </cmis:propertyId> <cmis:propertyString localName="rep-cmis:name" propertyDefinitionId="cmis:name"> <cmis:value>CMIS Example Folder as Customer type</cmis:value> </cmis:propertyString> <cmis:propertyDateTime localName="rep-cmis:creationDate" propertyDefinitionId="cmis:creationDate"> <cmis:value>2009-10-19T10:10:00.203-072010-01-25T10:20:59.380-08:00</cmis:value> </cmis:propertyDateTime> <cmis:propertyDateTime localName="rep-cmis:lastModificationDate" propertyDefinitionId="cmis:lastModificationDate"> <cmis:value>2009-10-19T10:10:00.203-072010-01-25T10:20:59.380-08:00</cmis:value> </cmis:propertyDateTime> <cmis:propertyId localName="rep-cmis:baseTypeId" propertyDefinitionId="cmis:baseTypeId"> <cmis:value>cmis:folder</cmis:value> </cmis:propertyId> <cmis:propertyString localName="rep-cmis:lastModifiedBy" propertyDefinitionId="cmis:lastModifiedBy"> <cmis:value>Al Brown</cmis:value> </cmis:propertyString>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 189 of 240

832483258326832783288329833083318332833383348335833683378338833983408341834283438344834583468347834883498350835183528353835483558356835783588359836083618362836383648365836683678368836983708371837283738374837583768377837883798380838183828383838483858386

565566567

Page 190: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<cmis:propertyString localName="rep-cmis:createdBy" propertyDefinitionId="cmis:createdBy"> <cmis:value>Al Brown</cmis:value> </cmis:propertyString> <cmis:propertyId localName="rep-cmis:parentId" propertyDefinitionId="cmis:parentId"> <cmis:value>c2e574a0-2d30-4834-b8a3-6333b33181c3up8e5a512c-8f2d-4387-a283-f3f30bbc312fup</cmis:value> </cmis:propertyId> </cmis:properties> </cmisra:object> <cmisra:pathSegment>customer</cmisra:pathSegment> <cmisra:children> <atom:feed> <atom:title type="text">CMIS Example Folder as Customer type</atom:title> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:updated>2009-10-19T10:10:00.203-072010-01-25T10:20:59.380-08:00</atom:updated> <atom:id>urn:uuid:9550c57d-64cd-4f00-9ab4-5b44903717e867ee5e9f-d2e3-457d-9dec-be718e780452</atom:id> <atom:link type="application/atom+xml;type=feed" rel="self" href="http://cmisexample.oasis-open.org/rep1/c2e574a0-2d30-4834-b8a3-6333b33181c38e5a512c-8f2d-4387-a283-f3f30bbc312f/3"/> <atom:link type="application/atomsvc+xml" rel="service" href="http://cmisexample.oasis-open.org/rep1//service"/> <atom:link type="application/atom+xml;type=entry" rel="via" href="http://cmisexample.oasis-open.org/rep1/c2e574a0-2d30-4834-b8a3-6333b33181c38e5a512c-8f2d-4387-a283-f3f30bbc312f"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/foldertree" href="http://cmisexample.oasis-open.org/rep1/c2e574a0-2d30-4834-b8a3-6333b33181c38e5a512c-8f2d-4387-a283-f3f30bbc312f/foldertree"/> <atom:link type="application/atom+xml;type=feed" rel="down" href="http://cmisexample.oasis-open.org/rep1/c2e574a0-2d30-4834-b8a3-6333b33181c38e5a512c-8f2d-4387-a283-f3f30bbc312f/children"/> <atom:link type="application/atom+xml;type=entry" rel="up" href="http://cmisexample.oasis-open.org/rep1/80dfb434-883b-4850-871d-6524c1ec2a64f083dd6f-1465-4516-97ce-040ec0c7c05a"/> <cmisra:numItems>1</cmisra:numItems> <atom:entry> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:content src="http://cmisexample.oasis-open.org/rep1/d4bc9b02-f732-49ce-979a-da31175a4d508c2dbba5-ea33-469f-a052-9f01e636c72a"/> <atom:id>urn:uuid:d4bc9b02-f732-49ce-979a-da31175a4d508c2dbba5-ea33-469f-a052-9f01e636c72a</atom:id> <atom:title type="text">CMIS Example Doc as Invoice type</atom:title> <atom:updated>2009-10-19T10:10:00.203-072010-01-25T10:20:59.380-08:00</atom:updated> <atom:link rel="self" href="http://cmisexample.oasis-open.org/rep1/d4bc9b02-f732-49ce-979a-da31175a4d508c2dbba5-ea33-469f-a052-9f01e636c72a"/>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 190 of 240

83878388838983908391839283938394839583968397839883998400840184028403840484058406840784088409841084118412841384148415841684178418841984208421842284238424842584268427842884298430843184328433843484358436843784388439844084418442844384448445844684478448

568569570

Page 191: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<atom:link rel="edit" href="http://cmisexample.oasis-open.org/rep1/d4bc9b02-f732-49ce-979a-da31175a4d508c2dbba5-ea33-469f-a052-9f01e636c72a"/> <atom:link type="application/cmis+xml;type=allowableActions" rel="http://docs.oasis-open.org/ns/cmis/link/200908/allowableactions" href="http://cmisexample.oasis-open.org/rep1/d4bc9b02-f732-49ce-979a-da31175a4d508c2dbba5-ea33-469f-a052-9f01e636c72a/allowableactions"/> <atom:link type="application/atom+xml;type=entry" rel="describedby" href="http://cmisexample.oasis-open.org/rep1/d4bc9b02-f732-49ce-979a-da31175a4d508c2dbba5-ea33-469f-a052-9f01e636c72a/type"/> <atom:link type="application/atomsvc+xml" rel="service" href="http://cmisexample.oasis-open.org/rep1//service"/> <atom:published>2009-10-19T10:10:00.203-072010-01-25T10:20:59.380-08:00</atom:published> <atom:summary type="html">HTML summary of Entry d4bc9b02-f732-49ce-979a-da31175a4d508c2dbba5-ea33-469f-a052-9f01e636c72a</atom:summary> <atom:link rel="edit-media" href="http://cmisexample.oasis-open.org/rep1/d4bc9b02-f732-49ce-979a-da31175a4d508c2dbba5-ea33-469f-a052-9f01e636c72a/edit-media"/> <atom:link rel="alternate" href="http://cmisexample.oasis-open.org/rep1/d4bc9b02-f732-49ce-979a-da31175a4d508c2dbba5-ea33-469f-a052-9f01e636c72a/alternate"/> <atom:link type="application/atom+xml;type=feed" rel="up" href="http://cmisexample.oasis-open.org/rep1/d4bc9b02-f732-49ce-979a-da31175a4d508c2dbba5-ea33-469f-a052-9f01e636c72a/parents"/> <atom:link type="application/atom+xml;type=feed" rel="version-history" href="http://cmisexample.oasis-open.org/rep1/d4bc9b02-f732-49ce-979a-da31175a4d508c2dbba5-ea33-469f-a052-9f01e636c72a/allversions"/> <atom:link type="application/atom+xml;type=entry" rel="current-version" href="http://cmisexample.oasis-open.org/rep1/d4bc9b02-f732-49ce-979a-da31175a4d508c2dbba5-ea33-469f-a052-9f01e636c72a/latest"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/relationships" href="http://cmisexample.oasis-open.org/rep1/d4bc9b02-f732-49ce-979a-da31175a4d508c2dbba5-ea33-469f-a052-9f01e636c72a/relationships"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/policies" href="http://cmisexample.oasis-open.org/rep1/d4bc9b02-f732-49ce-979a-da31175a4d508c2dbba5-ea33-469f-a052-9f01e636c72a/policies"/> <atom:link type="application/cmisacl+xml" rel="http://docs.oasis-open.org/ns/cmis/link/200908/acl" href="http://cmisexample.oasis-open.org/rep1/d4bc9b02-f732-49ce-979a-da31175a4d508c2dbba5-ea33-469f-a052-9f01e636c72a/acl"/> <cmisra:object> <cmis:properties> <cmis:propertyId localName="rep-cmis:objectId" propertyDefinitionId="cmis:objectId"> <cmis:value>d4bc9b02-f732-49ce-979a-da31175a4d508c2dbba5-ea33-469f-a052-9f01e636c72a</cmis:value> </cmis:propertyId> <cmis:propertyId localName="rep-cmis:objectTypeId" propertyDefinitionId="cmis:objectTypeId"> <cmis:value>invoice</cmis:value> </cmis:propertyId> <cmis:propertyString localName="rep-cmis:name" propertyDefinitionId="cmis:name"> <cmis:value>CMIS Example Doc as Invoice type</cmis:value> </cmis:propertyString> <cmis:propertyDateTime localName="rep-cmis:creationDate" propertyDefinitionId="cmis:creationDate">

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 191 of 240

84498450845184528453845484558456845784588459846084618462846384648465846684678468846984708471847284738474847584768477847884798480848184828483848484858486848784888489849084918492849384948495849684978498849985008501850285038504850585068507850885098510

571572573

Page 192: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<cmis:value>2009-10-19T10:10:00.218-072010-01-25T10:20:59.380-08:00</cmis:value> </cmis:propertyDateTime> <cmis:propertyDateTime localName="rep-cmis:lastModificationDate" propertyDefinitionId="cmis:lastModificationDate"> <cmis:value>2009-10-19T10:10:00.218-072010-01-25T10:20:59.380-08:00</cmis:value> </cmis:propertyDateTime> <cmis:propertyId localName="rep-cmis:baseTypeId" propertyDefinitionId="cmis:baseTypeId"> <cmis:value>cmis:document</cmis:value> </cmis:propertyId> <cmis:propertyString localName="rep-cmis:lastModifiedBy" propertyDefinitionId="cmis:lastModifiedBy"> <cmis:value>Al Brown</cmis:value> </cmis:propertyString> <cmis:propertyString localName="rep-cmis:createdBy" propertyDefinitionId="cmis:createdBy"> <cmis:value>Al Brown</cmis:value> </cmis:propertyString> <cmis:propertyBoolean localName="rep-cmis:isLatestVersion" propertyDefinitionId="cmis:isLatestVersion"> <cmis:value>true</cmis:value> </cmis:propertyBoolean> <cmis:propertyBoolean localName="rep-cmis:isVersionSeriesCheckedOut" propertyDefinitionId="cmis:isVersionSeriesCheckedOut"> <cmis:value>false</cmis:value> </cmis:propertyBoolean> <cmis:propertyBoolean localName="rep-cmis:isMajorVersion" propertyDefinitionId="cmis:isMajorVersion"> <cmis:value>false</cmis:value> </cmis:propertyBoolean> <cmis:propertyBoolean localName="rep-cmis:isLatestMajorVersion" propertyDefinitionId="cmis:isLatestMajorVersion"> <cmis:value>false</cmis:value> </cmis:propertyBoolean> <cmis:propertyBoolean localName="rep-cmis:isImmutable" propertyDefinitionId="cmis:isImmutable"> <cmis:value>false</cmis:value> </cmis:propertyBoolean> <cmis:propertyString localName="rep-cmis:checkinComment" propertyDefinitionId="cmis:checkinComment"> <cmis:value>Checkin comment</cmis:value> </cmis:propertyString> <cmis:propertyString localName="rep-cmis:versionLabel" propertyDefinitionId="cmis:versionLabel"> <cmis:value>0.1</cmis:value> </cmis:propertyString> <cmis:propertyString localName="rep-cmis:contentStreamMimeType" propertyDefinitionId="cmis:contentStreamMimeType"> <cmis:value>text/plain</cmis:value> </cmis:propertyString> <cmis:propertyString localName="rep-cmis:contentStreamFileName" propertyDefinitionId="cmis:contentStreamFileName"> <cmis:value>text.txt</cmis:value> </cmis:propertyString> <cmis:propertyInteger localName="rep-cmis:contentStreamLength" propertyDefinitionId="cmis:contentStreamLength"> <cmis:value>4234</cmis:value> </cmis:propertyInteger> <cmis:propertyString displayName="Keywords for Document" localName="keywords" propertyDefinitionId="keywords">

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 192 of 240

851185128513851485158516851785188519852085218522852385248525852685278528852985308531853285338534853585368537853885398540854185428543854485458546854785488549855085518552855385548555855685578558855985608561856285638564856585668567856885698570857185728573

574575576

Page 193: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<cmis:value>document</cmis:value> <cmis:value>example</cmis:value> <cmis:value>sample</cmis:value> <cmis:value>cmis</cmis:value> </cmis:propertyString> </cmis:properties> </cmisra:object> <cmisra:pathSegment>invoice1.pdf</cmisra:pathSegment> </atom:entry> </atom:feed> </cmisra:children> </atom:entry></atom:feed>

Please also see the example documents included with the schema.

3.9.3.1 GETThe following arguments may be supplied. Please see the domain model for more information:

filter depth includeAllowableActions includeRelationships renditionFilter includePathSegment

3.9.3.2 DELETEThis deletes the folder and all sub-folders. The following arguments may be supplied. Please see the domain model for more information:

continueOnFailure unfileObjects

Status Code: 200 OK if successful. Body contains entity describing the status 202 Accepted, if accepted but deletion not yet taking place 204 No Content, if successful with no content 403 Forbidden, if permission is denied 401 Unauthorized, if not authenticated 500 Internal Server Error. The body SHOULD contain an entity describing the status

If the delete method does not delete all items, invoking GET with infinite depth on this URI will return the items not deleted. Subsequent DELETE methods can be invoked on this URI.Note: If the repository does not implement get on this resource, or the canGetDescendants is false, there is no mechanism to identify the resources that were not removed.

3.9.4 Folder TreeThis is a hierarchical feed comprising all the folders under a specified folder. This is available via the link relation foldertree with media type application/atom+xml;type=feed. Please see the Hierarchical Atom Entries for more information on format.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 193 of 240

8574857585768577857885798580858185828583858485858586

85878588

85898590859185928593859485958596

85978598859986008601

86028603860486058606860786088609

86108611861286138614

8615861686178618

577578579

Page 194: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

CMIS Services:GET: getFolderTreeDELETE: deleteTree

Media Type: application/atom +xml;type=feed

Link Relations: service: Points to service document containing the CMIS repository. The service document

MUST contain only one workspace element.o Media Type: application/atomsvc+xml

via: points to the atom entry of the folder generating this collection up: points to the atom entry document of this folder’s parent

o If the root folder, this link relation MUST not be included.

o Media Type: application/atom+xml;type=entry

down: o application/atom+xml : Points to the atom feed document representing the children feed

for this same foldero application/cmistree+xml: Points to the descendants feed of the same folder. If a

repository does not support capabilityGetDescendants, then this link SHOULD NOT be included.

paging link relations MAY be included as appropriate: first, next, previous, lasto Repositories may support these paging link relations on a particular cmisra:children

element.

This feed contains a set of atom entries for each sub-folder in the folder.

The following CMIS Atom extension element MAY be included inside the atom feed: cmisra:numItems

The following CMIS Atom extension element MUST be included inside the atom entries: cmisra:object inside atom:entry cmisra:pathSegment inside atom:entry cmisra:children inside atom:entry

Example:<?xml version="1.0" encoding="UTF-8" standalone="yes"?><atom:feed xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:app="http://www.w3.org/2007/app" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <atom:title type="text">FolderTree Feed of Folder1</atom:title> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 194 of 240

86198620862186228623

862486258626862786288629863086318632863386348635863686378638863986408641

86428643

864486458646

86478648864986508651

8652865386548655865686578658865986608661866286638664

580581582

Page 195: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

</atom:author> <atom:updated>2009-10-19T10:10:00.312-072010-01-25T10:20:59.521-08:00</atom:updated> <atom:id>urn:uuid:e8627e01-9b28-4e5b-b7b4-d88c05bae4e9f87e5678-dd24-4214-9e71-635f060beb7d</atom:id> <atom:link type="application/atom+xml;type=feed" rel="self" href="http://cmisexample.oasis-open.org/rep1/3bcbead0-ad9f-4e0c-a2e8-49d025e062c56e327a3c-a246-4cee-8176-b65edc3e1854/3"/> <atom:link type="application/atomsvc+xml" rel="service" href="http://cmisexample.oasis-open.org/rep1//service"/> <atom:link type="application/atom+xml;type=entry" rel="via" href="http://cmisexample.oasis-open.org/rep1/3bcbead0-ad9f-4e0c-a2e8-49d025e062c56e327a3c-a246-4cee-8176-b65edc3e1854"/> <atom:link type="application/cmistree+xml" rel="down" href="http://cmisexample.oasis-open.org/rep1/3bcbead0-ad9f-4e0c-a2e8-49d025e062c56e327a3c-a246-4cee-8176-b65edc3e1854/tree"/> <atom:link type="application/atom+xml;type=feed" rel="down" href="http://cmisexample.oasis-open.org/rep1/3bcbead0-ad9f-4e0c-a2e8-49d025e062c56e327a3c-a246-4cee-8176-b65edc3e1854/children"/> <atom:link type="application/atom+xml;type=entry" rel="up" href="http://cmisexample.oasis-open.org/rep1/cdaf0998-582a-445f-9179-113a12470b043056c4d7-4e16-49cb-a750-ad7a3844a1aa"/> <cmisra:numItems>1</cmisra:numItems> <atom:entry> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:content src="http://cmisexample.oasis-open.org/rep1/7d9c26a2-ad1e-43e5-b176-247b64e4f4bcc7b5a83e-37b6-4f5a-b646-50892252a180"/> <atom:id>urn:uuid:7d9c26a2-ad1e-43e5-b176-247b64e4f4bcc7b5a83e-37b6-4f5a-b646-50892252a180</atom:id> <atom:title type="text">Customer Folder</atom:title> <atom:updated>2009-10-19T10:10:00.312-072010-01-25T10:20:59.521-08:00</atom:updated> <atom:link rel="self" href="http://cmisexample.oasis-open.org/rep1/7d9c26a2-ad1e-43e5-b176-247b64e4f4bcc7b5a83e-37b6-4f5a-b646-50892252a180"/> <atom:link rel="edit" href="http://cmisexample.oasis-open.org/rep1/7d9c26a2-ad1e-43e5-b176-247b64e4f4bcc7b5a83e-37b6-4f5a-b646-50892252a180"/> <atom:link type="application/cmis+xml;type=allowableActions" rel="http://docs.oasis-open.org/ns/cmis/link/200908/allowableactions" href="http://cmisexample.oasis-open.org/rep1/7d9c26a2-ad1e-43e5-b176-247b64e4f4bcc7b5a83e-37b6-4f5a-b646-50892252a180/allowableactions"/> <atom:link type="application/atom+xml;type=entry" rel="describedby" href="http://cmisexample.oasis-open.org/rep1/7d9c26a2-ad1e-43e5-b176-247b64e4f4bcc7b5a83e-37b6-4f5a-b646-50892252a180/type"/> <atom:link type="application/atomsvc+xml" rel="service" href="http://cmisexample.oasis-open.org/rep1//service"/> <atom:published>2009-10-19T10:10:00.312-072010-01-25T10:20:59.521-08:00</atom:published> <atom:summary type="html">HTML summary of Entry 7d9c26a2-ad1e-43e5-b176-247b64e4f4bcc7b5a83e-37b6-4f5a-b646-50892252a180</atom:summary> <atom:link type="application/atom+xml;type=entry" rel="up" href="http://cmisexample.oasis-open.org/rep1/7d9c26a2-ad1e-43e5-b176-247b64e4f4bcc7b5a83e-37b6-4f5a-b646-50892252a180/up"/> <atom:link type="application/atom+xml;type=feed" rel="down" href="http://cmisexample.oasis-open.org/rep1/7d9c26a2-ad1e-43e5-b176-247b64e4f4bcc7b5a83e-37b6-4f5a-b646-50892252a180/children"/>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 195 of 240

8665866686678668866986708671867286738674867586768677867886798680868186828683868486858686868786888689869086918692869386948695869686978698869987008701870287038704870587068707870887098710871187128713871487158716871787188719872087218722872387248725

583584585

Page 196: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<atom:link type="application/cmistree+xml" rel="down" href="http://cmisexample.oasis-open.org/rep1/7d9c26a2-ad1e-43e5-b176-247b64e4f4bcc7b5a83e-37b6-4f5a-b646-50892252a180/tree"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/foldertree" href="http://cmisexample.oasis-open.org/rep1/7d9c26a2-ad1e-43e5-b176-247b64e4f4bcc7b5a83e-37b6-4f5a-b646-50892252a180/foldertree"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/relationships" href="http://cmisexample.oasis-open.org/rep1/7d9c26a2-ad1e-43e5-b176-247b64e4f4bcc7b5a83e-37b6-4f5a-b646-50892252a180/relationships"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/policies" href="http://cmisexample.oasis-open.org/rep1/7d9c26a2-ad1e-43e5-b176-247b64e4f4bcc7b5a83e-37b6-4f5a-b646-50892252a180/policies"/> <atom:link type="application/cmisacl+xml" rel="http://docs.oasis-open.org/ns/cmis/link/200908/acl" href="http://cmisexample.oasis-open.org/rep1/7d9c26a2-ad1e-43e5-b176-247b64e4f4bcc7b5a83e-37b6-4f5a-b646-50892252a180/acl"/> <cmisra:object> <cmis:properties> <cmis:propertyId localName="rep-cmis:objectId" propertyDefinitionId="cmis:objectId"> <cmis:value>7d9c26a2-ad1e-43e5-b176-247b64e4f4bcc7b5a83e-37b6-4f5a-b646-50892252a180</cmis:value> </cmis:propertyId> <cmis:propertyId localName="rep-cmis:objectTypeId" propertyDefinitionId="cmis:objectTypeId"> <cmis:value>customer</cmis:value> </cmis:propertyId> <cmis:propertyString localName="rep-cmis:name" propertyDefinitionId="cmis:name"> <cmis:value>Customer Folder</cmis:value> </cmis:propertyString> <cmis:propertyDateTime localName="rep-cmis:creationDate" propertyDefinitionId="cmis:creationDate"> <cmis:value>2009-10-19T10:10:00.328-072010-01-25T10:20:59.521-08:00</cmis:value> </cmis:propertyDateTime> <cmis:propertyDateTime localName="rep-cmis:lastModificationDate" propertyDefinitionId="cmis:lastModificationDate"> <cmis:value>2009-10-19T10:10:00.328-072010-01-25T10:20:59.521-08:00</cmis:value> </cmis:propertyDateTime> <cmis:propertyId localName="rep-cmis:baseTypeId" propertyDefinitionId="cmis:baseTypeId"> <cmis:value>cmis:folder</cmis:value> </cmis:propertyId> <cmis:propertyString localName="rep-cmis:lastModifiedBy" propertyDefinitionId="cmis:lastModifiedBy"> <cmis:value>Al Brown</cmis:value> </cmis:propertyString> <cmis:propertyString localName="rep-cmis:createdBy" propertyDefinitionId="cmis:createdBy"> <cmis:value>Al Brown</cmis:value> </cmis:propertyString> <cmis:propertyId localName="rep-cmis:parentId" propertyDefinitionId="cmis:parentId"> <cmis:value>7d9c26a2-ad1e-43e5-b176-247b64e4f4bcupc7b5a83e-37b6-4f5a-b646-50892252a180up</cmis:value> </cmis:propertyId> </cmis:properties> </cmisra:object>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 196 of 240

872687278728872987308731873287338734873587368737873887398740874187428743874487458746874787488749875087518752875387548755875687578758875987608761876287638764876587668767876887698770877187728773877487758776877787788779878087818782878387848785878687878788

586587588

Page 197: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<cmisra:pathSegment>customer</cmisra:pathSegment> </atom:entry></atom:feed>

Please also see the example documents included with the schema.

3.9.4.1 GETThe following arguments may be supplied. Please see the domain model for more information:

filter depth includeAllowableActions includeRelationships renditionFilter

3.9.4.2 DELETEThis is the same as DELETE on Folder Descendants. Please see that section.

3.9.5 AllVersions FeedThis is a feed comprised of all the versions of the given document.CMIS Services:

GET: getAllVersionsDELETE: deleteAllVersions

Media Type: application/atom+xml;type=feed

The feed SHOULD contain the newest versions at the beginning of the feed.

Link Relations: service: Points to service document containing the CMIS repository. The service document

MUST contain only one workspace element.o Media Type: application/atomsvc+xml

via: points to the atom entry of the resource generating this collection paging link relations as appropriate: first, next, previous, last

This feed contains a set of atom entries for each version in the version series cmisra:object inside atom:entry cmisra:children inside atom:entry if atom:entry represents a CMIS Folder

Example:<?xml version="1.0" encoding="UTF-8" standalone="yes"?><atom:feed xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:app="http://www.w3.org/2007/app" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <atom:title type="text">AllVersions for Document c3141e18-fb48-4742-a6f8-adef86dea79ae8abd7cd-b9ec-4dba-9eaa-1bce2ae9977f</atom:title>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 197 of 240

878987908791

87928793

8794879587968797879887998800

88018802

880388048805880688078808

88098810

8811881288138814881588168817

8818881988208821

8822882388248825882688278828882988308831

589590591

Page 198: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:updated>2009-10-19T10:09:59.828-072010-01-25T10:20:58.896-08:00</atom:updated> <atom:id>urn:uuid:309c322f-1e10-4306-85ba-98f1870c58825dc3d1c1-3e85-4720-acf8-cf98c96a5830</atom:id> <atom:link type="application/atom+xml;type=feed" rel="self" href="http://cmisexample.oasis-open.org/rep1/c3141e18-fb48-4742-a6f8-adef86dea79ae8abd7cd-b9ec-4dba-9eaa-1bce2ae9977f/3"/> <atom:link type="application/atomsvc+xml" rel="service" href="http://cmisexample.oasis-open.org/rep1//service"/> <atom:link type="application/atom+xml;type=entry" rel="via" href="http://cmisexample.oasis-open.org/rep1/c3141e18-fb48-4742-a6f8-adef86dea79ae8abd7cd-b9ec-4dba-9eaa-1bce2ae9977f"/> <cmisra:numItems>1</cmisra:numItems> <atom:entry> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:content src="http://cmisexample.oasis-open.org/rep1/9c7860a7-be25-439e-b473-8da032402a6d197033f2-ac11-4911-b5a3-60781fa5c281"/> <atom:id>urn:uuid:9c7860a7-be25-439e-b473-8da032402a6d197033f2-ac11-4911-b5a3-60781fa5c281</atom:id> <atom:title type="text">Invoice (Version1)</atom:title> <atom:updated>2009-10-19T10:09:59.828-072010-01-25T10:20:58.896-08:00</atom:updated> <atom:link rel="self" href="http://cmisexample.oasis-open.org/rep1/9c7860a7-be25-439e-b473-8da032402a6d197033f2-ac11-4911-b5a3-60781fa5c281"/> <atom:link rel="edit" href="http://cmisexample.oasis-open.org/rep1/9c7860a7-be25-439e-b473-8da032402a6d197033f2-ac11-4911-b5a3-60781fa5c281"/> <atom:link type="application/cmis+xml;type=allowableActions" rel="http://docs.oasis-open.org/ns/cmis/link/200908/allowableactions" href="http://cmisexample.oasis-open.org/rep1/9c7860a7-be25-439e-b473-8da032402a6d197033f2-ac11-4911-b5a3-60781fa5c281/allowableactions"/> <atom:link type="application/atom+xml;type=entry" rel="describedby" href="http://cmisexample.oasis-open.org/rep1/9c7860a7-be25-439e-b473-8da032402a6d197033f2-ac11-4911-b5a3-60781fa5c281/type"/> <atom:link type="application/atomsvc+xml" rel="service" href="http://cmisexample.oasis-open.org/rep1//service"/> <atom:published>2009-10-19T10:09:59.843-072010-01-25T10:20:58.896-08:00</atom:published> <atom:summary type="html">HTML summary of Entry 9c7860a7-be25-439e-b473-8da032402a6d197033f2-ac11-4911-b5a3-60781fa5c281</atom:summary> <atom:link rel="edit-media" href="http://cmisexample.oasis-open.org/rep1/9c7860a7-be25-439e-b473-8da032402a6d197033f2-ac11-4911-b5a3-60781fa5c281/edit-media"/> <atom:link rel="alternate" href="http://cmisexample.oasis-open.org/rep1/9c7860a7-be25-439e-b473-8da032402a6d197033f2-ac11-4911-b5a3-60781fa5c281/alternate"/> <atom:link type="application/atom+xml;type=feed" rel="up" href="http://cmisexample.oasis-open.org/rep1/9c7860a7-be25-439e-b473-8da032402a6d197033f2-ac11-4911-b5a3-60781fa5c281/parents"/> <atom:link type="application/atom+xml;type=feed" rel="version-history" href="http://cmisexample.oasis-open.org/rep1/9c7860a7-be25-439e-b473-8da032402a6d197033f2-ac11-4911-b5a3-60781fa5c281/allversions"/>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 198 of 240

88328833883488358836883788388839884088418842884388448845884688478848884988508851885288538854885588568857885888598860886188628863886488658866886788688869887088718872887388748875887688778878887988808881888288838884888588868887888888898890889188928893

592593594

Page 199: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<atom:link type="application/atom+xml;type=entry" rel="current-version" href="http://cmisexample.oasis-open.org/rep1/9c7860a7-be25-439e-b473-8da032402a6d197033f2-ac11-4911-b5a3-60781fa5c281/latest"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/relationships" href="http://cmisexample.oasis-open.org/rep1/9c7860a7-be25-439e-b473-8da032402a6d197033f2-ac11-4911-b5a3-60781fa5c281/relationships"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/policies" href="http://cmisexample.oasis-open.org/rep1/9c7860a7-be25-439e-b473-8da032402a6d197033f2-ac11-4911-b5a3-60781fa5c281/policies"/> <atom:link type="application/cmisacl+xml" rel="http://docs.oasis-open.org/ns/cmis/link/200908/acl" href="http://cmisexample.oasis-open.org/rep1/9c7860a7-be25-439e-b473-8da032402a6d197033f2-ac11-4911-b5a3-60781fa5c281/acl"/> <cmisra:object> <cmis:properties> <cmis:propertyId localName="rep-cmis:objectId" propertyDefinitionId="cmis:objectId"> <cmis:value>9c7860a7-be25-439e-b473-8da032402a6d197033f2-ac11-4911-b5a3-60781fa5c281</cmis:value> </cmis:propertyId> </cmis:properties> </cmisra:object> </atom:entry></atom:feed>

Please also see the example documents included with the schema.

3.9.5.1 GETThe following arguments may be supplied. Please see the domain model for more information:

filter includeAllowableActions

3.9.5.2 DELETEThis removes the entire version history of the document.

Success HTTP code: 204

3.9.6 Type Descendants FeedThis is a feed described in the service document that contains all the types under a specific type in the repository to a specific depth. If no parent type is specified, then the base types and their descendants are returned in the feed which is equivalent to all types in the repository if depth is infinite. The link relation is http://docs.oasis-open.org/ns/cmis/link/200908/typesdescendantstypedescendants.

Types are nested using the CMIS hierarchy extension. Please see section 3.4.3.2 Hierarchy Navigation Internet Draft Link Relations.

CMIS Services:GET: getTypeDescendants

Media Type: application/atom+xml;type=feed

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 199 of 240

88948895889688978898889989008901890289038904890589068907890889098910891189128913891489158916891789188919

89208921

8922892389248925

89268927

89288929

89308931893289338934

893589368937

893889398940

89418942

595596597

Page 200: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Link Relations: service: Points to service document containing the CMIS repository. The service document

MUST contain only one workspace element.o Media Type: application/atomsvc+xml

via: points to the type definition whose descendents represent this feed. This link is not present if no parent type is specified.

down: points to the children feed for the same type up: points to the parent type definition

o If this is a descendants feed for a base object type, this link is not present.

The following CMIS Atom extension element MAY be included inside the atom feed: cmisra:numItems

Example:<?xml version="1.0" encoding="UTF-8" standalone="yes"?><atom:feed xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:app="http://www.w3.org/2007/app" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <atom:title type="text">Base Types</atom:title> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:updated>2009-10-19T10:10:00.656-072010-01-25T10:20:59.911-08:00</atom:updated> <atom:id>urn:uuid:e1981abc-a130-4cf0-89f2-0fa26f2801fec5d3d357-33ec-47c1-8436-563e0d94d2e5</atom:id> <atom:link type="application/atom+xml;type=feed" rel="self" href="http://cmisexample.oasis-open.org/rep1//3"/> <atom:link type="application/atomsvc+xml" rel="service" href="http://cmisexample.oasis-open.org/rep1//service"/> <atom:link type="application/atom+xml;type=entry" rel="via" href="http://cmisexample.oasis-open.org/rep1/"/> <atom:link type="application/atom+xml;type=feed" rel="down" href="http://cmisexample.oasis-open.org/rep1//children"/> <cmisra:numItems>1</cmisra:numItems> <atom:entry> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:content>Type Definition for cmis:document</atom:content> <atom:id>http://cmisexample.oasis-open.org/rep1/type/cmis:document</atom:id> <atom:link type="application/atom+xml;type=entry" rel="self" href="http://cmisexample.oasis-open.org/rep1/type/cmis:document"/> <atom:link type="application/atomsvc+xml" rel="service" href="http://cmisexample.oasis-open.org/rep1/type/cmis:document"/> <atom:link type="application/atom+xml;type=entry" rel="describedby" href="http://cmisexample.oasis-open.org/rep1/type/cmis:document"/>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 200 of 240

8943894489458946894789488949895089518952895389548955

895689578958895989608961896289638964896589668967896889698970897189728973897489758976897789788979898089818982898389848985898689878988898989908991899289938994899589968997

598599600

Page 201: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<atom:link type="application/atom+xml;type=entry" rel="up" href="http://cmisexample.oasis-open.org/rep1/type/cmis:document/parent"/> <atom:link type="application/atom+xml;type=feed" rel="down" href="http://cmisexample.oasis-open.org/rep1/type/cmis:document/children/flat"/> <atom:link type="application/cmistree+xml" rel="down" href="http://cmisexample.oasis-open.org/rep1/type/cmis:document/children/tree"/> <atom:published>2009-10-19T10:10:00.656-072010-01-25T10:20:59.927-08:00</atom:published> <atom:summary type="html">HTML summary of Type Definition cmis:document</atom:summary> <atom:title type="text">Type Definition - cmis:document</atom:title> <atom:updated>2009-10-19T10:10:00.656-072010-01-25T10:20:59.927-08:00</atom:updated> <app:edited>2009-10-19T10:10:00.671-072010-01-25T10:20:59.927-08:00</app:edited> <cmisra:type xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="cmis:cmisTypeDocumentDefinitionType" cmisra:id="cmis:document"> <cmis:id>dtcmis:document</cmis:id> <cmis:localName>myrepname-cmis:document</cmis:localName> <cmis:localNamespace xsi:nil="true"/> <cmis:displayName>cmis:document</cmis:displayName> <cmis:queryName>cmis:document</cmis:queryName> <cmis:description>Description for type definition cmis:document</cmis:description> <cmis:baseId>cmis:document</cmis:baseId> <cmis:parentId>parent</cmis:parentId> <cmis:creatable>true</cmis:creatable> <cmis:fileable>true</cmis:fileable> <cmis:queryable>false</cmis:queryable> <cmis:fulltextIndexed>false</cmis:fulltextIndexed> <cmis:includedInSupertypeQuery>true</cmis:includedInSupertypeQuery> <cmis:controllablePolicy>true</cmis:controllablePolicy> <cmis:controllableACL>true</cmis:controllableACL> <cmis:versionable>true</cmis:versionable> <cmis:contentStreamAllowed>allowed</cmis:contentStreamAllowed> </cmisra:type> <cmisra:children> <atom:feed> <atom:title type="text">Children for Document</atom:title> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:updated>2009-10-19T10:10:00.671-072010-01-25T10:20:59.927-08:00</atom:updated> <atom:id>urn:uuid:5657c90b-b07f-4225-832d-28a5302f84246f1cdc44-bd89-41c0-8fad-89f3ad0f8f30</atom:id> <atom:link type="application/atom+xml;type=feed" rel="self" href="http://cmisexample.oasis-open.org/rep1/cmis:document/3"/> <atom:link type="application/atomsvc+xml" rel="service" href="http://cmisexample.oasis-open.org/rep1//service"/> <atom:link type="application/atom+xml;type=entry" rel="via" href="http://cmisexample.oasis-open.org/rep1/cmis:document"/> <atom:link type="application/atom+xml;type=feed" rel="down" href="http://cmisexample.oasis-open.org/rep1/cmis:document/children"/> <atom:link type="application/atom+xml;type=entry" rel="up" href="http://cmisexample.oasis-open.org/rep1/document"/> <cmisra:numItems>1</cmisra:numItems> <atom:entry>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 201 of 240

899889999000900190029003900490059006900790089009901090119012901390149015901690179018901990209021902290239024902590269027902890299030903190329033903490359036903790389039904090419042904390449045904690479048904990509051905290539054905590569057905890599060

601602603

Page 202: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:content>Type Definition for invoice-document</atom:content> <atom:id>http://cmisexample.oasis-open.org/rep1/type/invoice-document</atom:id> <atom:link type="application/atom+xml;type=entry" rel="self" href="http://cmisexample.oasis-open.org/rep1/type/invoice-document"/> <atom:link type="application/atomsvc+xml" rel="service" href="http://cmisexample.oasis-open.org/rep1/type/invoice-document"/> <atom:link type="application/atom+xml;type=entry" rel="describedby" href="http://cmisexample.oasis-open.org/rep1/type/cmis:document"/> <atom:link type="application/atom+xml;type=entry" rel="up" href="http://cmisexample.oasis-open.org/rep1/type/invoice-document/parent"/> <atom:link type="application/atom+xml;type=feed" rel="down" href="http://cmisexample.oasis-open.org/rep1/type/invoice-document/children/flat"/> <atom:link type="application/cmistree+xml" rel="down" href="http://cmisexample.oasis-open.org/rep1/type/invoice-document/children/tree"/> <atom:published>2009-10-19T10:10:00.671-072010-01-25T10:20:59.927-08:00</atom:published> <atom:summary type="html">HTML summary of Type Definition invoice-document</atom:summary> <atom:title type="text">Type Definition - invoice-document</atom:title> <atom:updated>2009-10-19T10:10:00.671-072010-01-25T10:20:59.927-08:00</atom:updated> <app:edited>2009-10-19T10:10:00.671-072010-01-25T10:20:59.927-08:00</app:edited> <cmisra:type xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="cmis:cmisTypeDocumentDefinitionType" cmisra:id="invoice-document"> <cmis:id>dtinvoice-document</cmis:id> <cmis:localName>myrepname-invoice-document</cmis:localName> <cmis:localNamespace xsi:nil="true"/> <cmis:displayName>invoice-document</cmis:displayName> <cmis:queryName>invoice-document</cmis:queryName> <cmis:description>Description for type definition invoice-document</cmis:description> <cmis:baseId>cmis:document</cmis:baseId> <cmis:parentId>parent</cmis:parentId> <cmis:creatable>true</cmis:creatable> <cmis:fileable>true</cmis:fileable> <cmis:queryable>false</cmis:queryable> <cmis:fulltextIndexed>false</cmis:fulltextIndexed> <cmis:includedInSupertypeQuery>true</cmis:includedInSupertypeQuery> <cmis:controllablePolicy>true</cmis:controllablePolicy> <cmis:controllableACL>true</cmis:controllableACL> <cmis:versionable>true</cmis:versionable> <cmis:contentStreamAllowed>allowed</cmis:contentStreamAllowed> </cmisra:type> </atom:entry>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 202 of 240

906190629063906490659066906790689069907090719072907390749075907690779078907990809081908290839084908590869087908890899090909190929093909490959096909790989099910091019102910391049105910691079108910991109111911291139114911591169117911891199120912191229123

604605606

Page 203: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

</atom:feed> </cmisra:children> </atom:entry> <atom:entry> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:content>Type Definition for cmis:folder</atom:content> <atom:id>http://cmisexample.oasis-open.org/rep1/type/cmis:folder</atom:id> <atom:link type="application/atom+xml;type=entry" rel="self" href="http://cmisexample.oasis-open.org/rep1/type/cmis:folder"/> <atom:link type="application/atomsvc+xml" rel="service" href="http://cmisexample.oasis-open.org/rep1/type/cmis:folder"/> <atom:link type="application/atom+xml;type=entry" rel="describedby" href="http://cmisexample.oasis-open.org/rep1/type/cmis:folder"/> <atom:link type="application/atom+xml;type=entry" rel="up" href="http://cmisexample.oasis-open.org/rep1/type/cmis:folder/parent"/> <atom:link type="application/atom+xml;type=feed" rel="down" href="http://cmisexample.oasis-open.org/rep1/type/cmis:folder/children/flat"/> <atom:link type="application/cmistree+xml" rel="down" href="http://cmisexample.oasis-open.org/rep1/type/cmis:folder/children/tree"/> <atom:published>2009-10-19T10:10:00.671-072010-01-25T10:20:59.927-08:00</atom:published> <atom:summary type="html">HTML summary of Type Definition cmis:folder</atom:summary> <atom:title type="text">Type Definition - cmis:folder</atom:title> <atom:updated>2009-10-19T10:10:00.671-072010-01-25T10:20:59.927-08:00</atom:updated> <app:edited>2009-10-19T10:10:00.671-072010-01-25T10:20:59.927-08:00</app:edited> <cmisra:type xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="cmis:cmisTypeFolderDefinitionType" cmisra:id="cmis:folder"> <cmis:id>dtcmis:folder</cmis:id> <cmis:localName>myrepname-cmis:folder</cmis:localName> <cmis:localNamespace xsi:nil="true"/> <cmis:displayName>cmis:folder</cmis:displayName> <cmis:queryName>cmis:folder</cmis:queryName> <cmis:description>Description for type definition cmis:folder</cmis:description> <cmis:baseId>cmis:folder</cmis:baseId> <cmis:parentId>parent</cmis:parentId> <cmis:creatable>true</cmis:creatable> <cmis:fileable>true</cmis:fileable> <cmis:queryable>false</cmis:queryable> <cmis:fulltextIndexed>false</cmis:fulltextIndexed> <cmis:includedInSupertypeQuery>true</cmis:includedInSupertypeQuery> <cmis:controllablePolicy>true</cmis:controllablePolicy> <cmis:controllableACL>true</cmis:controllableACL> </cmisra:type> <cmisra:children> <atom:feed> <atom:title type="text">Children for Folder</atom:title> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:updated>2009-10-19T10:10:00.671-072010-01-25T10:20:59.927-08:00</atom:updated>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 203 of 240

912491259126912791289129913091319132913391349135913691379138913991409141914291439144914591469147914891499150915191529153915491559156915791589159916091619162916391649165916691679168916991709171917291739174917591769177917891799180918191829183918491859186

607608609

Page 204: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<atom:id>urn:uuid:7b556496-2a09-40ca-b2a5-3e4e5596fb89361a3ac1-f7f7-47cb-b941-ae1200213fe0</atom:id> <atom:link type="application/atom+xml;type=feed" rel="self" href="http://cmisexample.oasis-open.org/rep1/cmis:folder/3"/> <atom:link type="application/atomsvc+xml" rel="service" href="http://cmisexample.oasis-open.org/rep1//service"/> <atom:link type="application/atom+xml;type=entry" rel="via" href="http://cmisexample.oasis-open.org/rep1/cmis:folder"/> <atom:link type="application/atom+xml;type=feed" rel="down" href="http://cmisexample.oasis-open.org/rep1/cmis:folder/children"/> <atom:link type="application/atom+xml;type=entry" rel="up" href="http://cmisexample.oasis-open.org/rep1/cmis:folder"/> <cmisra:numItems>1</cmisra:numItems> <atom:entry> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:content>Type Definition for customer-folder</atom:content> <atom:id>http://cmisexample.oasis-open.org/rep1/type/customer-folder</atom:id> <atom:link type="application/atom+xml;type=entry" rel="self" href="http://cmisexample.oasis-open.org/rep1/type/customer-folder"/> <atom:link type="application/atomsvc+xml" rel="service" href="http://cmisexample.oasis-open.org/rep1/type/customer-folder"/> <atom:link type="application/atom+xml;type=entry" rel="describedby" href="http://cmisexample.oasis-open.org/rep1/type/cmis:folder"/> <atom:link type="application/atom+xml;type=entry" rel="up" href="http://cmisexample.oasis-open.org/rep1/type/customer-folder/parent"/> <atom:link type="application/atom+xml;type=feed" rel="down" href="http://cmisexample.oasis-open.org/rep1/type/customer-folder/children/flat"/> <atom:link type="application/cmistree+xml" rel="down" href="http://cmisexample.oasis-open.org/rep1/type/customer-folder/children/tree"/> <atom:published>2009-10-19T10:10:00.671-072010-01-25T10:20:59.927-08:00</atom:published> <atom:summary type="html">HTML summary of Type Definition customer-folder</atom:summary> <atom:title type="text">Type Definition - customer-folder</atom:title> <atom:updated>2009-10-19T10:10:00.671-072010-01-25T10:20:59.927-08:00</atom:updated> <app:edited>2009-10-19T10:10:00.671-072010-01-25T10:20:59.927-08:00</app:edited> <cmisra:type xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="cmis:cmisTypeFolderDefinitionType" cmisra:id="customer-folder"> <cmis:id>dtcustomer-folder</cmis:id> <cmis:localName>myrepname-customer-folder</cmis:localName> <cmis:localNamespace xsi:nil="true"/> <cmis:displayName>customer-folder</cmis:displayName> <cmis:queryName>customer-folder</cmis:queryName> <cmis:description>Description for type definition customer-folder</cmis:description> <cmis:baseId>cmis:folder</cmis:baseId> <cmis:parentId>parent</cmis:parentId> <cmis:creatable>true</cmis:creatable>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 204 of 240

918791889189919091919192919391949195919691979198919992009201920292039204920592069207920892099210921192129213921492159216921792189219922092219222922392249225922692279228922992309231923292339234923592369237923892399240924192429243924492459246924792489249

610611612

Page 205: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<cmis:fileable>true</cmis:fileable> <cmis:queryable>false</cmis:queryable> <cmis:fulltextIndexed>false</cmis:fulltextIndexed> <cmis:includedInSupertypeQuery>true</cmis:includedInSupertypeQuery> <cmis:controllablePolicy>true</cmis:controllablePolicy> <cmis:controllableACL>true</cmis:controllableACL> </cmisra:type> </atom:entry> </atom:feed> </cmisra:children> </atom:entry> <atom:entry> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:content>Type Definition for cmis:relationship</atom:content> <atom:id>http://cmisexample.oasis-open.org/rep1/type/cmis:relationship</atom:id> <atom:link type="application/atom+xml;type=entry" rel="self" href="http://cmisexample.oasis-open.org/rep1/type/cmis:relationship"/> <atom:link type="application/atomsvc+xml" rel="service" href="http://cmisexample.oasis-open.org/rep1/type/cmis:relationship"/> <atom:link type="application/atom+xml;type=entry" rel="describedby" href="http://cmisexample.oasis-open.org/rep1/type/cmis:relationship"/> <atom:link type="application/atom+xml;type=entry" rel="up" href="http://cmisexample.oasis-open.org/rep1/type/cmis:relationship/parent"/> <atom:link type="application/atom+xml;type=feed" rel="down" href="http://cmisexample.oasis-open.org/rep1/type/cmis:relationship/children/flat"/> <atom:link type="application/cmistree+xml" rel="down" href="http://cmisexample.oasis-open.org/rep1/type/cmis:relationship/children/tree"/> <atom:published>2009-10-19T10:10:00.671-072010-01-25T10:20:59.943-08:00</atom:published> <atom:summary type="html">HTML summary of Type Definition cmis:relationship</atom:summary> <atom:title type="text">Type Definition - cmis:relationship</atom:title> <atom:updated>2009-10-19T10:10:00.687-072010-01-25T10:20:59.943-08:00</atom:updated> <app:edited>2009-10-19T10:10:00.687-072010-01-25T10:20:59.943-08:00</app:edited> <cmisra:type xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="cmis:cmisTypeRelationshipDefinitionType" cmisra:id="cmis:relationship"> <cmis:id>dtcmis:relationship</cmis:id> <cmis:localName>myrepname-cmis:relationship</cmis:localName> <cmis:localNamespace xsi:nil="true"/> <cmis:displayName>cmis:relationship</cmis:displayName> <cmis:queryName>cmis:relationship</cmis:queryName> <cmis:description>Description for type definition cmis:relationship</cmis:description> <cmis:baseId>cmis:relationship</cmis:baseId> <cmis:parentId>parent</cmis:parentId> <cmis:creatable>true</cmis:creatable> <cmis:fileable>false</cmis:fileable> <cmis:queryable>false</cmis:queryable> <cmis:fulltextIndexed>false</cmis:fulltextIndexed>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 205 of 240

925092519252925392549255925692579258925992609261926292639264926592669267926892699270927192729273927492759276927792789279928092819282928392849285928692879288928992909291929292939294929592969297929892999300930193029303930493059306930793089309931093119312

613614615

Page 206: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<cmis:includedInSupertypeQuery>true</cmis:includedInSupertypeQuery> <cmis:controllablePolicy>true</cmis:controllablePolicy> <cmis:controllableACL>true</cmis:controllableACL> <cmis:allowedSourceTypes>invoice</cmis:allowedSourceTypes> <cmis:allowedSourceTypes>capitalinvoice</cmis:allowedSourceTypes> <cmis:allowedTargetTypes>customer</cmis:allowedTargetTypes> </cmisra:type> <cmisra:children> <atom:feed> <atom:title type="text">Children for Relationship</atom:title> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:updated>2009-10-19T10:10:00.687-072010-01-25T10:20:59.943-08:00</atom:updated> <atom:id>urn:uuid:1bc33a0d-27ac-4976-9cab-58ea28e3ff6c9394ff3d-87c4-48c9-a951-ba725560faac</atom:id> <atom:link type="application/atom+xml;type=feed" rel="self" href="http://cmisexample.oasis-open.org/rep1/cmis:relationship/3"/> <atom:link type="application/atomsvc+xml" rel="service" href="http://cmisexample.oasis-open.org/rep1//service"/> <atom:link type="application/atom+xml;type=entry" rel="via" href="http://cmisexample.oasis-open.org/rep1/cmis:relationship"/> <atom:link type="application/atom+xml;type=feed" rel="down" href="http://cmisexample.oasis-open.org/rep1/cmis:relationship/children"/> <atom:link type="application/atom+xml;type=entry" rel="up" href="http://cmisexample.oasis-open.org/rep1/cmis:folder"/> <cmisra:numItems>1</cmisra:numItems> <atom:entry> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:content>Type Definition for customer-relationship</atom:content> <atom:id>http://cmisexample.oasis-open.org/rep1/type/customer-relationship</atom:id> <atom:link type="application/atom+xml;type=entry" rel="self" href="http://cmisexample.oasis-open.org/rep1/type/customer-relationship"/> <atom:link type="application/atomsvc+xml" rel="service" href="http://cmisexample.oasis-open.org/rep1/type/customer-relationship"/> <atom:link type="application/atom+xml;type=entry" rel="describedby" href="http://cmisexample.oasis-open.org/rep1/type/cmis:relationship"/> <atom:link type="application/atom+xml;type=entry" rel="up" href="http://cmisexample.oasis-open.org/rep1/type/customer-relationship/parent"/> <atom:link type="application/atom+xml;type=feed" rel="down" href="http://cmisexample.oasis-open.org/rep1/type/customer-relationship/children/flat"/> <atom:link type="application/cmistree+xml" rel="down" href="http://cmisexample.oasis-open.org/rep1/type/customer-relationship/children/tree"/> <atom:published>2009-10-19T10:10:00.687-072010-01-25T10:20:59.943-08:00</atom:published> <atom:summary type="html">HTML summary of Type Definition customer-relationship</atom:summary>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 206 of 240

931393149315931693179318931993209321932293239324932593269327932893299330933193329333933493359336933793389339934093419342934393449345934693479348934993509351935293539354935593569357935893599360936193629363936493659366936793689369937093719372937393749375

616617618

Page 207: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<atom:title type="text">Type Definition - customer-relationship</atom:title> <atom:updated>2009-10-19T10:10:00.687-072010-01-25T10:20:59.943-08:00</atom:updated> <app:edited>2009-10-19T10:10:00.687-072010-01-25T10:20:59.943-08:00</app:edited> <cmisra:type xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="cmis:cmisTypeRelationshipDefinitionType" cmisra:id="customer-relationship"> <cmis:id>dtcustomer-relationship</cmis:id> <cmis:localName>myrepname-customer-relationship</cmis:localName> <cmis:localNamespace xsi:nil="true"/> <cmis:displayName>customer-relationship</cmis:displayName> <cmis:queryName>customer-relationship</cmis:queryName> <cmis:description>Description for type definition customer-relationship</cmis:description> <cmis:baseId>cmis:relationship</cmis:baseId> <cmis:parentId>parent</cmis:parentId> <cmis:creatable>true</cmis:creatable> <cmis:fileable>false</cmis:fileable> <cmis:queryable>false</cmis:queryable> <cmis:fulltextIndexed>false</cmis:fulltextIndexed> <cmis:includedInSupertypeQuery>true</cmis:includedInSupertypeQuery> <cmis:controllablePolicy>true</cmis:controllablePolicy> <cmis:controllableACL>true</cmis:controllableACL> <cmis:allowedSourceTypes>invoice</cmis:allowedSourceTypes> <cmis:allowedSourceTypes>capitalinvoice</cmis:allowedSourceTypes> <cmis:allowedTargetTypes>customer</cmis:allowedTargetTypes> </cmisra:type> </atom:entry> </atom:feed> </cmisra:children> </atom:entry> <atom:entry> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:content>Type Definition for cmis:policy</atom:content> <atom:id>http://cmisexample.oasis-open.org/rep1/type/cmis:policy</atom:id> <atom:link type="application/atom+xml;type=entry" rel="self" href="http://cmisexample.oasis-open.org/rep1/type/cmis:policy"/> <atom:link type="application/atomsvc+xml" rel="service" href="http://cmisexample.oasis-open.org/rep1/type/cmis:policy"/> <atom:link type="application/atom+xml;type=entry" rel="describedby" href="http://cmisexample.oasis-open.org/rep1/type/cmis:policy"/> <atom:link type="application/atom+xml;type=entry" rel="up" href="http://cmisexample.oasis-open.org/rep1/type/cmis:policy/parent"/> <atom:link type="application/atom+xml;type=feed" rel="down" href="http://cmisexample.oasis-open.org/rep1/type/cmis:policy/children/flat"/> <atom:link type="application/cmistree+xml" rel="down" href="http://cmisexample.oasis-open.org/rep1/type/cmis:policy/children/tree"/> <atom:published>2009-10-19T10:10:00.687-072010-01-25T10:20:59.943-08:00</atom:published>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 207 of 240

937693779378937993809381938293839384938593869387938893899390939193929393939493959396939793989399940094019402940394049405940694079408940994109411941294139414941594169417941894199420942194229423942494259426942794289429943094319432943394349435943694379438

619620621

Page 208: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<atom:summary type="html">HTML summary of Type Definition cmis:policy</atom:summary> <atom:title type="text">Type Definition - cmis:policy</atom:title> <atom:updated>2009-10-19T10:10:00.687-072010-01-25T10:20:59.943-08:00</atom:updated> <app:edited>2009-10-19T10:10:00.687-072010-01-25T10:20:59.943-08:00</app:edited> <cmisra:type xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="cmis:cmisTypePolicyDefinitionType" cmisra:id="cmis:policy"> <cmis:id>dtcmis:policy</cmis:id> <cmis:localName>myrepname-cmis:policy</cmis:localName> <cmis:localNamespace xsi:nil="true"/> <cmis:displayName>cmis:policy</cmis:displayName> <cmis:queryName>cmis:policy</cmis:queryName> <cmis:description>Description for type definition cmis:policy</cmis:description> <cmis:baseId>cmis:policy</cmis:baseId> <cmis:parentId>parent</cmis:parentId> <cmis:creatable>true</cmis:creatable> <cmis:fileable>false</cmis:fileable> <cmis:queryable>false</cmis:queryable> <cmis:fulltextIndexed>false</cmis:fulltextIndexed> <cmis:includedInSupertypeQuery>true</cmis:includedInSupertypeQuery> <cmis:controllablePolicy>true</cmis:controllablePolicy> <cmis:controllableACL>true</cmis:controllableACL> </cmisra:type> </atom:entry></atom:feed>

Please also see the example documents included with the schema.

3.9.6.1 GETThe following arguments may be supplied. Please see the domain model for more information:

includePropertyDefinitions depth

3.10 ResourcesFor any HTTP verb not specified on a resource,each implementation MAY chose to implement that HTTP verb in a repository-specific manner.

3.10.1 Type EntryThis represents a type definition in the repository. This is enclosed as an atom entry

CMIS Services:GET: getTypeDefinition

Media Type: application/atom+xml;type=entry

Link Relations: service: Points to service document containing the CMIS repository. The service document

MUST contain only one workspace element.o Media Type: application/atomsvc+xml

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 208 of 240

94399440944194429443944494459446944794489449945094519452945394549455945694579458945994609461946294639464946594669467

94689469

9470947194729473

947494759476

94779478

9479948094819482

94839484948594869487

622623624

Page 209: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

up: Points to the parent type as atom entry if applicable down: Points to the children of this type as atom feed if applicable

o (Children) Media Type: application/atom +xml;type=feed points to the atom feed document representing the children feed for this same type

o (Descendants) Media Type: application/cmistree+xml points to the atom feed document representing the descendents feed for this same type

describedby: Points to the type definition atom entry of the base type of this type definition.

The following CMIS Atom extension element MUST be included inside the atom entry: cmisra:type

3.10.1.1 GETThere are no optional arguments for this resource.

Request:GET /obj/0010d88d-d006-4d50-aad0-c8f61f80f2735070f89a-6f00-4acf-84e9-d8836a6c7d23 HTTP/1.1Host: example.org

Response:HTTP/1.1 200 OkDate: Mon, 19 Oct 200925 Jan 2010 10:10:01 -070021:00 -0800Content-Length: 2995Content-Type: application/atom+xml;type=entryLocation: http://cmisexample.oasis-open.org/rep1/cmis:document

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><atom:entry xmlns:app="http://www.w3.org/2007/app" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:content>Type Definition for cmis:document</atom:content> <atom:id>http://cmisexample.oasis-open.org/rep1/type/cmis:document</atom:id> <atom:link type="application/atom+xml;type=entry" rel="self" href="http://cmisexample.oasis-open.org/rep1/type/cmis:document"/> <atom:link type="application/atomsvc+xml" rel="service" href="http://cmisexample.oasis-open.org/rep1/type/cmis:document"/> <atom:link type="application/atom+xml;type=entry" rel="describedby" href="http://cmisexample.oasis-open.org/rep1/type/cmis:document"/> <atom:link type="application/atom+xml;type=entry" rel="up" href="http://cmisexample.oasis-open.org/rep1/type/cmis:document/parent"/> <atom:link type="application/atom+xml;type=feed" rel="down" href="http://cmisexample.oasis-open.org/rep1/type/cmis:document/children/flat"/>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 209 of 240

9488948994909491949294939494

949594969497

94989499

9500950195029503950495059506950795089509951095119512951395149515951695179518951995209521952295239524952595269527952895299530953195329533953495359536953795389539

625626627

Page 210: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<atom:link type="application/cmistree+xml" rel="down" href="http://cmisexample.oasis-open.org/rep1/type/cmis:document/children/tree"/> <atom:published>2009-10-19T10:10:01.015-072010-01-25T10:21:00.380-08:00</atom:published> <atom:summary type="html">HTML summary of Type Definition cmis:document</atom:summary> <atom:title type="text">Type Definition - cmis:document</atom:title> <atom:updated>2009-10-19T10:10:2010-01.015-07-25T10:21:00.380-08:00</atom:updated> <app:edited>2009-10-19T10:10:2010-01.015-07-25T10:21:00.380-08:00</app:edited> <cmisra:type xsi:type="cmis:cmisTypeDocumentDefinitionType" cmisra:id="cmis:document" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <cmis:id>dtcmis:document</cmis:id> <cmis:localName>myrepname-cmis:document</cmis:localName> <cmis:localNamespace xsi:nil="true"/> <cmis:displayName>cmis:document</cmis:displayName> <cmis:queryName>cmis:document</cmis:queryName> <cmis:description>Description for type definition cmis:document</cmis:description> <cmis:baseId>cmis:document</cmis:baseId> <cmis:parentId>parent</cmis:parentId> <cmis:creatable>true</cmis:creatable> <cmis:fileable>true</cmis:fileable> <cmis:queryable>false</cmis:queryable> <cmis:fulltextIndexed>false</cmis:fulltextIndexed> <cmis:includedInSupertypeQuery>true</cmis:includedInSupertypeQuery> <cmis:controllablePolicy>true</cmis:controllablePolicy> <cmis:controllableACL>true</cmis:controllableACL> <cmis:versionable>true</cmis:versionable> <cmis:contentStreamAllowed>allowed</cmis:contentStreamAllowed> </cmisra:type></atom:entry>

Please also see the example documents included with the schema.

3.10.2 Document EntryThis is a CMIS Document instance.

CMIS Services:GET: getObject, getObjectOfLatestVersion (getObject)PUT: updatePropertiesDELETE: deleteObject

Media Type: application/atom+xml;type=entry

Link Relations: self: Points to an URI that returns the atom entry for this document. Please see Atom for more

information. edit: Points to an URI that accepts PUT of atom entry. Please see AtomPub for more information.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 210 of 240

95409541954295439544954595469547954895499550955195529553955495559556955795589559956095619562956395649565956695679568956995709571957295739574957595769577

9578

95799580

958195829583958495859586

95879588958995909591

628629630

Page 211: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

service: Points to service document containing the CMIS repository. The service document MUST contain only one workspace element.

o Media Type: application/atomsvc+xml

up: Points to the atom feed containing the set of parents. If there is only one parent, the repository MAY point this link relation directly to the atom entry of the parent.

version-history: Points to atom feed containing the versions of this documento If the document is not versionable, this link relation may not be on the resource

current-version: Points to the latest version of the documento Uses query parameter ‘returnVersion’ and enumReturnVersion

o If this version is the current-version, this link relation may not be on the resource

edit-media: o Same as setContentStream. Allows updating the content stream on this document

o Please see AtomPub for more information

working-copy: Points to the private working copy if it exists. describedby: Points to the type definition as an atom entry for the type of this document entry. alternate: this is used to identify the renditions available for the specified object. Please see the

Renditions section. http://docs.oasis-open.org/ns/cmis/link/200908/allowableactions: Points to the allowable actions

document for this object. http://docs.oasis-open.org/ns/cmis/link/200908/relationships: Points to the relationships feed for

this object http://docs.oasis-open.org/ns/cmis/link/200908/policies: Points to the policy feed for this object. http://docs.oasis-open.org/ns/cmis/link/200908/acl: Points to ACL document for this object

The following CMIS Atom extension element MUST be included inside the atom entry: cmisra:object

3.10.2.1 GETThe following arguments may be supplied. Please see the domain model for more information:

returnVersiono Used to differentiate between getObject() and getObjectOfLatestVersion().

o valid values are are described by the schema element cmisra:enumReturnVersion

o If not specified, return the version specified by the URI

includeAllowableActions includeRelationships includePolicyIds includeACL filter renditionFilter

o If not specified, renditions will not be included.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 211 of 240

95929593959495959596959795989599960096019602960396049605960696079608960996109611961296139614

961596169617

9618

961996209621962296239624962596269627962896299630963196329633631632633

Page 212: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Request:GET /obj/8a7b8f30-3e9f-49b9-acf7-94851ff7ad087c088887-5991-4b3a-9ad3-16379127e647?filter=cmis:objectId HTTP/1.1Host: example.org

Response:HTTP/1.1 200 OkDate: Mon, 19 Oct 200925 Jan 2010 10:1021:00 -07000800Content-Length: 3403Content-Type: application/atom+xml;type=entryLocation: /obj/8a7b8f30-3e9f-49b9-acf7-94851ff7ad087c088887-5991-4b3a-9ad3-16379127e647?filter=cmis:objectId

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><atom:entry xmlns:app="http://www.w3.org/2007/app" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:content src="http://cmisexample.oasis-open.org/rep1/8a7b8f30-3e9f-49b9-acf7-94851ff7ad087c088887-5991-4b3a-9ad3-16379127e647"/> <atom:id>urn:uuid:8a7b8f30-3e9f-49b9-acf7-94851ff7ad087c088887-5991-4b3a-9ad3-16379127e647</atom:id> <atom:title type="text">Invoice</atom:title> <atom:updated>2009-10-19T10:102010-01-25T10:21:00.843-07193-08:00</atom:updated> <atom:link rel="self" href="http://cmisexample.oasis-open.org/rep1/8a7b8f30-3e9f-49b9-acf7-94851ff7ad087c088887-5991-4b3a-9ad3-16379127e647"/> <atom:link rel="edit" href="http://cmisexample.oasis-open.org/rep1/8a7b8f30-3e9f-49b9-acf7-94851ff7ad087c088887-5991-4b3a-9ad3-16379127e647"/> <atom:link type="application/cmis+xml;type=allowableActions" rel="http://docs.oasis-open.org/ns/cmis/link/200908/allowableactions" href="http://cmisexample.oasis-open.org/rep1/8a7b8f30-3e9f-49b9-acf7-94851ff7ad087c088887-5991-4b3a-9ad3-16379127e647/allowableactions"/> <atom:link type="application/atom+xml;type=entry" rel="describedby" href="http://cmisexample.oasis-open.org/rep1/8a7b8f30-3e9f-49b9-acf7-94851ff7ad087c088887-5991-4b3a-9ad3-16379127e647/type"/> <atom:link type="application/atomsvc+xml" rel="service" href="http://cmisexample.oasis-open.org/rep1//service"/> <atom:published>2009-10-19T10:102010-01-25T10:21:00.843-07193-08:00</atom:published> <atom:summary type="html">HTML summary of Entry 8a7b8f30-3e9f-49b9-acf7-94851ff7ad087c088887-5991-4b3a-9ad3-16379127e647</atom:summary> <atom:link rel="edit-media" href="http://cmisexample.oasis-open.org/rep1/8a7b8f30-3e9f-49b9-acf7-94851ff7ad087c088887-5991-4b3a-9ad3-16379127e647/edit-media"/> <atom:link rel="alternate" href="http://cmisexample.oasis-open.org/rep1/8a7b8f30-3e9f-49b9-acf7-94851ff7ad087c088887-5991-4b3a-9ad3-16379127e647/alternate"/> <atom:link type="application/atom+xml;type=feed" rel="up" href="http://cmisexample.oasis-open.org/rep1/8a7b8f30-3e9f-49b9-acf7-94851ff7ad087c088887-5991-4b3a-9ad3-16379127e647/parents"/>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 212 of 240

9634963596369637963896399640964196429643964496459646964796489649965096519652965396549655965696579658965996609661966296639664966596669667966896699670967196729673967496759676967796789679968096819682968396849685968696879688968996909691969296939694

634635636

Page 213: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<atom:link type="application/atom+xml;type=feed" rel="version-history" href="http://cmisexample.oasis-open.org/rep1/8a7b8f30-3e9f-49b9-acf7-94851ff7ad087c088887-5991-4b3a-9ad3-16379127e647/allversions"/> <atom:link type="application/atom+xml;type=entry" rel="current-version" href="http://cmisexample.oasis-open.org/rep1/8a7b8f30-3e9f-49b9-acf7-94851ff7ad087c088887-5991-4b3a-9ad3-16379127e647/latest"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/relationships" href="http://cmisexample.oasis-open.org/rep1/8a7b8f30-3e9f-49b9-acf7-94851ff7ad087c088887-5991-4b3a-9ad3-16379127e647/relationships"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/policies" href="http://cmisexample.oasis-open.org/rep1/8a7b8f30-3e9f-49b9-acf7-94851ff7ad087c088887-5991-4b3a-9ad3-16379127e647/policies"/> <atom:link type="application/cmisacl+xml" rel="http://docs.oasis-open.org/ns/cmis/link/200908/acl" href="http://cmisexample.oasis-open.org/rep1/8a7b8f30-3e9f-49b9-acf7-94851ff7ad087c088887-5991-4b3a-9ad3-16379127e647/acl"/> <cmisra:object> <cmis:properties> <cmis:propertyId localName="rep-cmis:objectId" propertyDefinitionId="cmis:objectId"> <cmis:value>8a7b8f30-3e9f-49b9-acf7-94851ff7ad087c088887-5991-4b3a-9ad3-16379127e647</cmis:value> </cmis:propertyId> </cmis:properties> </cmisra:object></atom:entry>

Please also see the example documents included with the schema.

3.10.2.2 PUTThis does a replacement of the atom entry with the atom entry document specified. If readwrite properties are not included, the repository SHOULD NOT modify them.

The server SHOULD respond with: HTTP Status Code 200 Response Body containing the updated atom entry

3.10.2.3 DELETEThis removes the document.Success HTTP code: 204

3.10.3 Document Private Working Copy (PWC) EntryThis is the private working copy of the document (checkedout version of document)CMIS Services:

GET: getObjectPUT: updateProperties or checkInDELETE: cancelCheckOut

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 213 of 240

9695969696979698969997009701970297039704970597069707970897099710971197129713971497159716971797189719972097219722972397249725

9726

972797289729

9730973197329733

9734

973597369737

973897399740974197429743

637638639

Page 214: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Media Type: application/atom+xml;type=entry

Link relations: self: Points to the URI to retrieve this atom entry. Please see Atom for more information edit: Points to the URI to update this atom entry via POST. Please see AtomPub for more

information. service: Points to service document containing the CMIS repository. The service document

MUST contain only one workspace element.o Media Type: application/atomsvc+xml

up: Points to the atom feed containing the set of parents. If there is only one parent, the repository MAY point this link relation directly to the atom entry of the parent.

version-historyo Points to an URI that returns the feed associated with the version history

edit-mediao Same as setContentStream. Allows updating the content stream on this document

o Please see AtomPub for more information

via: atom entry that created this private working copy describedby: Points to the type definition as an atom entry for the type of this PWC entry. alternate: this is used to identify the renditions available for the specified object. Please see the

Renditions section. http://docs.oasis-open.org/ns/cmis/link/200908/allowableactions: Points to the allowable actions

document for this object. http://docs.oasis-open.org/ns/cmis/link/200908/relationships: Points to the relationships feed for

this object http://docs.oasis-open.org/ns/cmis/link/200908/policies: Points to the policy feed for this object. http://docs.oasis-open.org/ns/cmis/link/200908/acl: Points to ACL document for this object

The following element MUST be included inside the atom entry: cmisra:object

3.10.3.1 GETThe following arguments may be supplied. Please see the domain model for more information:

filter includeAllowableActions includeRelationships renditionFilter

o If not specified, renditions will not be included.

Request:GET /obj/3ca7d7d0-1c98-4c38-9141-604d287fb8813240a476-6de6-4ab2-978d-85ca2f4f3206?filter=cmis:objectId HTTP/1.1Host: example.org

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 214 of 240

9744

9745974697479748974997509751975297539754975597569757975897599760976197629763976497659766976797689769

977097719772

9773

9774977597769777977897799780978197829783978497859786

640641642

Page 215: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Response:HTTP/1.1 200 OkDate: Mon, 19 Oct 200925 Jan 2010 10:1021:00 -07000800Content-Length: 3564Content-Type: application/atom+xml;type=entryLocation: /obj/3ca7d7d0-1c98-4c38-9141-604d287fb8813240a476-6de6-4ab2-978d-85ca2f4f3206?filter=cmis:objectId

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><atom:entry xmlns:app="http://www.w3.org/2007/app" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:content src="http://cmisexample.oasis-open.org/rep1/3240a476-6de6-4ab2-978d-85ca2f4f3206"/><?xml version="1.0" encoding="UTF-8" standalone="yes"?><atom:entry xmlns:app="http://www.w3.org/2007/app" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:content src="http://cmisexample.oasis-open.org/rep1/3ca7d7d0-1c98-4c38-9141-604d287fb881"/> <atom:id>urn:uuid:3ca7d7d0-1c98-4c38-9141-604d287fb8813240a476-6de6-4ab2-978d-85ca2f4f3206</atom:id> <atom:title type="text">Invoice</atom:title> <atom:updated>2009-10-19T10:102010-01-25T10:21:00.968-07333-08:00</atom:updated> <atom:link rel="self" href="http://cmisexample.oasis-open.org/rep1/3ca7d7d0-1c98-4c38-9141-604d287fb8813240a476-6de6-4ab2-978d-85ca2f4f3206"/> <atom:link rel="edit" href="http://cmisexample.oasis-open.org/rep1/3ca7d7d0-1c98-4c38-9141-604d287fb8813240a476-6de6-4ab2-978d-85ca2f4f3206"/> <atom:link type="application/cmis+xml;type=allowableActions" rel="http://docs.oasis-open.org/ns/cmis/link/200908/allowableactions" href="http://cmisexample.oasis-open.org/rep1/3ca7d7d0-1c98-4c38-9141-604d287fb8813240a476-6de6-4ab2-978d-85ca2f4f3206/allowableactions"/> <atom:link type="application/atom+xml;type=entry" rel="describedby" href="http://cmisexample.oasis-open.org/rep1/3ca7d7d0-1c98-4c38-9141-604d287fb8813240a476-6de6-4ab2-978d-85ca2f4f3206/type"/> <atom:link type="application/atomsvc+xml" rel="service" href="http://cmisexample.oasis-open.org/rep1//service"/> <atom:published>2009-10-19T10:102010-01-25T10:21:00.968-07333-08:00</atom:published> <atom:summary type="html">HTML summary of Entry 3ca7d7d0-1c98-4c38-9141-604d287fb8813240a476-6de6-4ab2-978d-85ca2f4f3206</atom:summary>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 215 of 240

978797889789979097919792979397949795979697979798979998009801980298039804980598069807980898099810981198129813981498159816981798189819982098219822982398249825982698279828982998309831983298339834983598369837983898399840984198429843984498459846

643644645

Page 216: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<atom:link rel="edit-media" href="http://cmisexample.oasis-open.org/rep1/3ca7d7d0-1c98-4c38-9141-604d287fb8813240a476-6de6-4ab2-978d-85ca2f4f3206/edit-media"/> <atom:link rel="alternate" href="http://cmisexample.oasis-open.org/rep1/3ca7d7d0-1c98-4c38-9141-604d287fb8813240a476-6de6-4ab2-978d-85ca2f4f3206/alternate"/> <atom:link type="application/atom+xml;type=feed" rel="up" href="http://cmisexample.oasis-open.org/rep1/3ca7d7d0-1c98-4c38-9141-604d287fb8813240a476-6de6-4ab2-978d-85ca2f4f3206/parents"/> <atom:link type="application/atom+xml;type=feed" rel="version-history" href="http://cmisexample.oasis-open.org/rep1/3ca7d7d0-1c98-4c38-9141-604d287fb8813240a476-6de6-4ab2-978d-85ca2f4f3206/allversions"/> <atom:link type="application/atom+xml;type=entry" rel="current-version" href="http://cmisexample.oasis-open.org/rep1/3ca7d7d0-1c98-4c38-9141-604d287fb8813240a476-6de6-4ab2-978d-85ca2f4f3206/latest"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/relationships" href="http://cmisexample.oasis-open.org/rep1/3ca7d7d0-1c98-4c38-9141-604d287fb8813240a476-6de6-4ab2-978d-85ca2f4f3206/relationships"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/policies" href="http://cmisexample.oasis-open.org/rep1/3ca7d7d0-1c98-4c38-9141-604d287fb8813240a476-6de6-4ab2-978d-85ca2f4f3206/policies"/> <atom:link type="application/cmisacl+xml" rel="http://docs.oasis-open.org/ns/cmis/link/200908/acl" href="http://cmisexample.oasis-open.org/rep1/3ca7d7d0-1c98-4c38-9141-604d287fb8813240a476-6de6-4ab2-978d-85ca2f4f3206/acl"/> <atom:link type="application/atom+xml;type=feed" rel="working-copy" href="http://cmisexample.oasis-open.org/rep1/3ca7d7d0-1c98-4c38-9141-604d287fb8813240a476-6de6-4ab2-978d-85ca2f4f3206/pwc"/> <cmisra:object> <cmis:properties> <cmis:propertyId localName="rep-cmis:objectId" propertyDefinitionId="cmis:objectId"> <cmis:value>3ca7d7d0-1c98-4c38-9141-604d287fb8813240a476-6de6-4ab2-978d-85ca2f4f3206</cmis:value> </cmis:propertyId> </cmis:properties> </cmisra:object></atom:entry>

Please also see the example documents included with the schema.

3.10.3.2 PUTThis does a replacement of the atom entry with the atom entry document specified. If modifiable properties (whencheckedout or readwrite) are not included, the repository SHOULD NOT modify them.

The following arguments may be supplied. Please see the domain model for more information: checkinComment major checkin

o Used to differentiate between updateProperties() or checkin() services. If TRUE, execute checkin service.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 216 of 240

9847984898499850985198529853985498559856985798589859986098619862986398649865986698679868986998709871987298739874987598769877987898799880988198829883988498859886988798889889

9890

989198929893

9894989598969897989898999900

646647648

Page 217: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

o If this argument is specified as TRUE, then the body to PUT MAY be omitted if there are no modifications to be made during checkin

The server SHOULD respond with: HTTP Status Code 200 Location header of the resource (if changed via checkin) Response Body containing the updated atom entry

3.10.3.3 DELETEThis removes the document entry, in this case, cancels the check out. The PWC will be removed.

Success HTTP code: 204

3.10.4 Folder EntryThis is a CMIS Folder instance. The properties of a folder map onto the feed tag.CMIS Services:

GET: getObjectPUT: updatePropertiesDELETE: deleteObject (this is deletion of the folder only and not any contained objects)

Media Type: application/atom+xml;type=entry

Link Relations: self: Points to the URI to retrieve this atom entry. Please see Atom for more information editinformationedit: Points to the URI to update this atom entry via POST. Please see AtomPub

for more information. service: Points to service document containing the CMIS repository. The service document

MUST contain only one workspace element.o Media Type: application/atomsvc+xml

describedby: Points to the type definition as an atom entry for the type of this folder entry. down: Points to the children of this folder if they exist

o application/atom+xml : Points to the atom feed document representing the children feed for this same folder

o application/cmistree+xml: Points to the descendants feed of the same folder

up: Points to the atom entry for the parento If the root folder, this link will not be present

alternate: this is used to identify the renditions available for the specified object. Please see the Renditions section.

http://docs.oasis-open.org/ns/cmis/link/200908/allowableactions: Points to the allowable actions document for this object.

http://docs.oasis-open.org/ns/cmis/link/200908/relationships: Points to the relationships feed for this object

http://docs.oasis-open.org/ns/cmis/link/200908/policies: Points to the policy feed for this object. http://docs.oasis-open.org/ns/cmis/link/200908/acl: Points to ACL document for this object http://docs.oasis-open.org/ns/cmis/link/200908/foldertree: Points to the folder tree for this folder

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 217 of 240

99019902

99039904990599069907

99089909

99109911

9912991399149915991699179918

991999209921992299239924992599269927992899299930993199329933993499359936993799389939994099419942649650651

Page 218: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

The following CMIS Atom extension element MUST be included inside the atom entry: cmisra:object

3.10.4.1 GETThe following arguments may be supplied. Please see the domain model for more information:

filter includeAllowableActions includeRelationships renditionFilter

o If not specified, renditions will not be included.

Request:GET /obj/24cbe125-1ffc-4459-8089-0e6f0a500150cfc03a28-8240-471d-b4ba-6d8756cd5093?filter=cmis:objectId HTTP/1.1Host: example.org

Response:HTTP/1.1 200 OkDate: Mon, 19 Oct 200925 Jan 2010 10:1021:00 -07000800Content-Length: 3332Content-Type: application/atom+xml;type=entryLocation: /obj/24cbe125-1ffc-4459-8089-0e6f0a500150cfc03a28-8240-471d-b4ba-6d8756cd5093?filter=cmis:objectId

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><atom:entry xmlns:app="http://www.w3.org/2007/app" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:content src="http://cmisexample.oasis-open.org/rep1/<?xml version="1.0" encoding="UTF-8" standalone="yes"?><atom:entry xmlns:app="http://www.w3.org/2007/app" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:content src="http://cmisexample.oasis-open.org/rep1/24cbe125-1ffc-4459-8089-0e6f0a500150"/>cfc03a28-8240-471d-b4ba-6d8756cd5093"/>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 218 of 240

994399449945

9946

9947994899499950995199529953995499559956995799589959996099619962996399649965996699679968996999709971997299739974997599769977997899799980998199829983998499859986998799889989999099919992999399949995

652653654

Page 219: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<atom:id>urn:uuid:24cbe125-1ffc-4459-8089-0e6f0a500150cfc03a28-8240-471d-b4ba-6d8756cd5093</atom:id> <atom:title type="text">Customer Folder</atom:title> <atom:updated>2009-10-19T10:102010-01-25T10:21:00.875-07208-08:00</atom:updated> <atom:link rel="self" href="http://cmisexample.oasis-open.org/rep1/24cbe125-1ffc-4459-8089-0e6f0a500150cfc03a28-8240-471d-b4ba-6d8756cd5093"/> <atom:link rel="edit" href="http://cmisexample.oasis-open.org/rep1/24cbe125-1ffc-4459-8089-0e6f0a500150cfc03a28-8240-471d-b4ba-6d8756cd5093"/> <atom:link type="application/cmis+xml;type=allowableActions" rel="http://docs.oasis-open.org/ns/cmis/link/200908/allowableactions" href="http://cmisexample.oasis-open.org/rep1/24cbe125-1ffc-4459-8089-0e6f0a500150cfc03a28-8240-471d-b4ba-6d8756cd5093/allowableactions"/> <atom:link type="application/atom+xml;type=entry" rel="describedby" href="http://cmisexample.oasis-open.org/rep1/24cbe125-1ffc-4459-8089-0e6f0a500150cfc03a28-8240-471d-b4ba-6d8756cd5093/type"/> <atom:link type="application/atomsvc+xml" rel="service" href="http://cmisexample.oasis-open.org/rep1//service"/> <atom:published>2009-10-19T10:102010-01-25T10:21:00.875-07208-08:00</atom:published> <atom:summary type="html">HTML summary of Entry 24cbe125-1ffc-4459-8089-0e6f0a500150cfc03a28-8240-471d-b4ba-6d8756cd5093</atom:summary> <atom:link type="application/atom+xml;type=entry" rel="up" href="http://cmisexample.oasis-open.org/rep1/24cbe125-1ffc-4459-8089-0e6f0a500150cfc03a28-8240-471d-b4ba-6d8756cd5093/up"/> <atom:link type="application/atom+xml;type=feed" rel="down" href="http://cmisexample.oasis-open.org/rep1/24cbe125-1ffc-4459-8089-0e6f0a500150cfc03a28-8240-471d-b4ba-6d8756cd5093/children"/> <atom:link type="application/cmistree+xml" rel="down" href="http://cmisexample.oasis-open.org/rep1/24cbe125-1ffc-4459-8089-0e6f0a500150cfc03a28-8240-471d-b4ba-6d8756cd5093/tree"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/foldertree" href="http://cmisexample.oasis-open.org/rep1/24cbe125-1ffc-4459-8089-0e6f0a500150cfc03a28-8240-471d-b4ba-6d8756cd5093/foldertree"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/relationships" href="http://cmisexample.oasis-open.org/rep1/24cbe125-1ffc-4459-8089-0e6f0a500150cfc03a28-8240-471d-b4ba-6d8756cd5093/relationships"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/policies" href="http://cmisexample.oasis-open.org/rep1/24cbe125-1ffc-4459-8089-0e6f0a500150cfc03a28-8240-471d-b4ba-6d8756cd5093/policies"/> <atom:link type="application/cmisacl+xml" rel="http://docs.oasis-open.org/ns/cmis/link/200908/acl" href="http://cmisexample.oasis-open.org/rep1/24cbe125-1ffc-4459-8089-0e6f0a500150cfc03a28-8240-471d-b4ba-6d8756cd5093/acl"/> <cmisra:object> <cmis:properties> <cmis:propertyId localName="rep-cmis:objectId" propertyDefinitionId="cmis:objectId"> <cmis:value>24cbe125-1ffc-4459-8089-0e6f0a500150cfc03a28-8240-471d-b4ba-6d8756cd5093</cmis:value> </cmis:propertyId> </cmis:properties> </cmisra:object></atom:entry>

Please also see the example documents included with the schema.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 219 of 240

999699979998999910000100011000210003100041000510006100071000810009100101001110012100131001410015100161001710018100191002010021100221002310024100251002610027100281002910030100311003210033100341003510036100371003810039100401004110042100431004410045100461004710048100491005010051100521005310054100551005610057

655656657

Page 220: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

3.10.4.2 PUTThis does a replacement of the atom entry with the atom entry document specified. If readwrite properties are not included, the repository SHOULD NOT modify them.

The server SHOULD respond with: HTTP Status Code 200 Response Body containing the updated atom entry

3.10.4.3 DELETEThis removes the object (folder) from the repository.Success HTTP code: 204

3.10.5 Relationship EntryThis is a CMIS relationship instance. These objects are exposed via ‘relationships’ link type.CMIS Services:

GET: getObjectPUT: updatePropertiesDELETE: deleteObject

Media Type: application/atom+xml;type=entry

Link Relations: self: Points to the URI to retrieve this atom entry. Please see Atom for more information edit: Points to the URI to update this atom entry via POST. Please see AtomPub for more

information. service: Points to service document containing the CMIS repository. The service document

MUST contain only one workspace element.o Media Type: application/atomsvc+xml

describedby: Points to the type definition as an atom entry for the type of this relationship entry. http://docs.oasis-open.org/ns/cmis/link/200908/target http://docs.oasis-open.org/ns/cmis/link/200908/source http://docs.oasis-open.org/ns/cmis/link/200908/allowableactions: Points to the allowable actions

document for this object. http://docs.oasis-open.org/ns/cmis/link/200908/policies: Points to the policy feed for this object. http://docs.oasis-open.org/ns/cmis/link/200908/acl: Points to ACL document for this object

The following element MUST be included inside the atom entry: cmisra:object

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 220 of 240

10058

100591006010061

10062100631006410065

10066

100671006810069

10070100711007210073100741007510076

100771007810079100801008110082100831008410085100861008710088100891009010091

100921009310094

10095

658659660

Page 221: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

3.10.5.1 GETThe following arguments may be supplied. Please see the domain model for more information:

filter includeAllowableActions

Request:GET /obj/38af30f5-020d-4274-b25c-0821b6db899bad443afd-aa1a-4071-9735-1a49aac4e439?filter=cmis:objectId HTTP/1.1Host: example.org

Response:HTTP/1.1 200 OkDate: Mon, 19 Oct 200925 Jan 2010 10:10:01 -070021:00 -0800Content-Length: 2861Content-Type: application/atom+xml;type=entryLocation: /obj/38af30f5-020d-4274-b25c-0821b6db899bad443afd-aa1a-4071-9735-1a49aac4e439?filter=cmis:objectId

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><atom:entry xmlns:app="http://www.w3.org/2007/app" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <atom:author> <atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:content src="http://cmisexample.oasis-open.org/rep1/38af30f5-020d-4274-b25c-0821b6db899bad443afd-aa1a-4071-9735-1a49aac4e439"/> <atom:id>urn:uuid:38af30f5-020d-4274-b25c-0821b6db899bad443afd-aa1a-4071-9735-1a49aac4e439</atom:id> <atom:title type="text">Customer Relationship</atom:title> <atom:updated>2009-10-19T10:10:2010-01.000-07-25T10:21:00.349-08:00</atom:updated> <atom:link rel="self" href="http://cmisexample.oasis-open.org/rep1/38af30f5-020d-4274-b25c-0821b6db899bad443afd-aa1a-4071-9735-1a49aac4e439"/> <atom:link rel="edit" href="http://cmisexample.oasis-open.org/rep1/38af30f5-020d-4274-b25c-0821b6db899bad443afd-aa1a-4071-9735-1a49aac4e439"/> <atom:link type="application/cmis+xml;type=allowableActions" rel="http://docs.oasis-open.org/ns/cmis/link/200908/allowableactions" href="http://cmisexample.oasis-open.org/rep1/38af30f5-020d-4274-b25c-0821b6db899bad443afd-aa1a-4071-9735-1a49aac4e439/allowableactions"/> <atom:link type="application/atom+xml;type=entry" rel="describedby" href="http://cmisexample.oasis-open.org/rep1/38af30f5-020d-4274-b25c-0821b6db899bad443afd-aa1a-4071-9735-1a49aac4e439/type"/> <atom:link type="application/atomsvc+xml" rel="service" href="http://cmisexample.oasis-open.org/rep1//service"/> <atom:published>2009-10-19T10:10:01.000-072010-01-25T10:21:00.365-08:00</atom:published> <atom:summary type="html">HTML summary of Entry 38af30f5-020d-4274-b25c-0821b6db899bad443afd-aa1a-4071-9735-1a49aac4e439</atom:summary>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 221 of 240

10096100971009810099

1010010101101021010310104101051010610107101081010910110101111011210113101141011510116101171011810119101201012110122101231012410125101261012710128101291013010131101321013310134101351013610137101381013910140101411014210143101441014510146101471014810149101501015110152

661662663

Page 222: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<atom:link type="application/atom+xml;type=entry" rel="http://docs.oasis-open.org/ns/cmis/link/200908/source" href="http://cmisexample.oasis-open.org/rep1/38af30f5-020d-4274-b25c-0821b6db899bad443afd-aa1a-4071-9735-1a49aac4e439/source"/> <atom:link type="application/atom+xml;type=entry" rel="http://docs.oasis-open.org/ns/cmis/link/200908/target" href="http://cmisexample.oasis-open.org/rep1/38af30f5-020d-4274-b25c-0821b6db899bad443afd-aa1a-4071-9735-1a49aac4e439/target"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/policies" href="http://cmisexample.oasis-open.org/rep1/38af30f5-020d-4274-b25c-0821b6db899bad443afd-aa1a-4071-9735-1a49aac4e439/policies"/> <atom:link type="application/cmisacl+xml" rel="http://docs.oasis-open.org/ns/cmis/link/200908/acl" href="http://cmisexample.oasis-open.org/rep1/38af30f5-020d-4274-b25c-0821b6db899bad443afd-aa1a-4071-9735-1a49aac4e439/acl"/> <cmisra:object> <cmis:properties> <cmis:propertyId localName="rep-cmis:objectId" propertyDefinitionId="cmis:objectId"> <cmis:value>38af30f5-020d-4274-b25c-0821b6db899bad443afd-aa1a-4071-9735-1a49aac4e439</cmis:value> </cmis:propertyId> </cmis:properties> </cmisra:object></atom:entry>

Please also see the example documents included with the schema.

3.10.5.2 PUTThis does a replacement of the atom entry with the atom entry document specified. If readwrite properties are not included, the repository SHOULD NOT modify them.

The server SHOULD respond with: HTTP Status Code 200 Response Body containing the updated atom entry

3.10.5.3 DELETEThis removes the relationship entry.Successful HTTP code: 204

3.10.6 Policy EntryThis is a CMIS policy instance.CMIS Services:

GET: getObjectPUT: updatePropertiesDELETE: deleteObject or removePolicy

Media Type: application/atom+xml;type=entry

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 222 of 240

1015310154101551015610157101581015910160101611016210163101641016510166101671016810169101701017110172101731017410175101761017710178101791018010181

10182

101831018410185

10186101871018810189

10190

101911019210193

10194101951019610197101981019910200

664665666

Page 223: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Link Relations: self edit service: Points to service document containing the CMIS repository. The service document

MUST contain only one workspace element.o Media Type: application/atomsvc+xml

describedby: Points to the type definition as an atom entry for the type of this policy entry. alternate: this is used to identify the renditions available for the specified object. Please see the

Renditions section. http://docs.oasis-open.org/ns/cmis/link/200908/allowableactions: Points to the allowable actions

document for this object. http://docs.oasis-open.org/ns/cmis/link/200908/policies: Points to the policy feed for this object. http://docs.oasis-open.org/ns/cmis/link/200908/acl: Points to ACL document for this object

The following element MUST be included inside the atom entry: cmisra:object

3.10.6.1 GETThe following arguments may be supplied. Please see the domain model for more information:

filter includeAllowableActions includeRelationships renditionFilter

o If not specified, renditions will not be included.

Request:GET /obj/408fb453-4a18-4103-b495-e84a2a2761a0a09ed524-5f1b-4940-b2f0-4e4cd4631bf0?filter=cmis:objectId HTTP/1.1Host: example.org

Response:HTTP/1.1 200 OkDate: Mon, 19 Oct 200925 Jan 2010 10:1021:00 -07000800Content-Length: 2608Content-Type: application/atom+xml;type=entryLocation: /obj/408fb453-4a18-4103-b495-e84a2a2761a0a09ed524-5f1b-4940-b2f0-4e4cd4631bf0?filter=cmis:objectId

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><atom:entry xmlns:app="http://www.w3.org/2007/app" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <atom:author>

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 223 of 240

1020110202102031020410205102061020710208102091021010211102121021310214

102151021610217

10218

102191022010221102221022310224102251022610227102281022910230102311023210233102341023510236102371023810239102401024110242102431024410245102461024710248

667668669

Page 224: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

<atom:name>Al Brown</atom:name> <atom:uri>http://www.ibm.com/</atom:uri> <atom:email>[email protected]</atom:email> </atom:author> <atom:content src="http://cmisexample.oasis-open.org/rep1/408fb453-4a18-4103-b495-e84a2a2761a0a09ed524-5f1b-4940-b2f0-4e4cd4631bf0"/> <atom:id>urn:uuid:408fb453-4a18-4103-b495-e84a2a2761a0a09ed524-5f1b-4940-b2f0-4e4cd4631bf0</atom:id> <atom:title type="text">Security Policy</atom:title> <atom:updated>2009-10-19T10:102010-01-25T10:21:00.937-07318-08:00</atom:updated> <atom:link rel="self" href="http://cmisexample.oasis-open.org/rep1/408fb453-4a18-4103-b495-e84a2a2761a0a09ed524-5f1b-4940-b2f0-4e4cd4631bf0"/> <atom:link rel="edit" href="http://cmisexample.oasis-open.org/rep1/408fb453-4a18-4103-b495-e84a2a2761a0a09ed524-5f1b-4940-b2f0-4e4cd4631bf0"/> <atom:link type="application/cmis+xml;type=allowableActions" rel="http://docs.oasis-open.org/ns/cmis/link/200908/allowableactions" href="http://cmisexample.oasis-open.org/rep1/408fb453-4a18-4103-b495-e84a2a2761a0a09ed524-5f1b-4940-b2f0-4e4cd4631bf0/allowableactions"/> <atom:link type="application/atom+xml;type=entry" rel="describedby" href="http://cmisexample.oasis-open.org/rep1/408fb453-4a18-4103-b495-e84a2a2761a0a09ed524-5f1b-4940-b2f0-4e4cd4631bf0/type"/> <atom:link type="application/atomsvc+xml" rel="service" href="http://cmisexample.oasis-open.org/rep1//service"/> <atom:published>2009-10-19T10:102010-01-25T10:21:00.937-07318-08:00</atom:published> <atom:summary type="html">HTML summary of Entry 408fb453-4a18-4103-b495-e84a2a2761a0a09ed524-5f1b-4940-b2f0-4e4cd4631bf0</atom:summary> <atom:link type="application/atom+xml;type=feed" rel="up" href="http://cmisexample.oasis-open.org/rep1/408fb453-4a18-4103-b495-e84a2a2761a0a09ed524-5f1b-4940-b2f0-4e4cd4631bf0/parents"/> <atom:link type="application/atom+xml;type=feed" rel="http://docs.oasis-open.org/ns/cmis/link/200908/relationships" href="http://cmisexample.oasis-open.org/rep1/408fb453-4a18-4103-b495-e84a2a2761a0a09ed524-5f1b-4940-b2f0-4e4cd4631bf0/relationships"/> <atom:link type="application/cmisacl+xml" rel="http://docs.oasis-open.org/ns/cmis/link/200908/acl" href="http://cmisexample.oasis-open.org/rep1/408fb453-4a18-4103-b495-e84a2a2761a0a09ed524-5f1b-4940-b2f0-4e4cd4631bf0/acl"/> <cmisra:object> <cmis:properties> <cmis:propertyId localName="rep-cmis:objectId" propertyDefinitionId="cmis:objectId"> <cmis:value>408fb453-4a18-4103-b495-e84a2a2761a0a09ed524-5f1b-4940-b2f0-4e4cd4631bf0</cmis:value> </cmis:propertyId> </cmis:properties> </cmisra:object></atom:entry>

Please also see the example documents included with the schema.

3.10.6.2 PUTThis does a replacement of the atom entry with the atom entry document specified. If read/write properties are not included, the repository SHOULD NOT modify them.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 224 of 240

102491025010251102521025310254102551025610257102581025910260102611026210263102641026510266102671026810269102701027110272102731027410275102761027710278102791028010281102821028310284102851028610287102881028910290102911029210293102941029510296102971029810299103001030110302

10303

103041030510306

10307670671672

Page 225: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

The server SHOULD respond with: HTTP Status Code 200 Response Body containing the updated atom entry

3.10.6.3 DELETEThis removes the policy entry. If this policy entry was discovered through a policy collection on an object, then removePolicy() is performed rather than deleteObject() on the policy itself.

Success HTTP code: 204

3.10.7 Content StreamThis is the content stream portion of the document object. CMIS Services:

GET: getContentStreamPUT: setContentStreamDELETE: deleteContentStream

Media Type: Mime/Type of resource (mime type of content stream on document)

3.10.7.1 GETThis returns the content stream.

It is RECOMMENDED that HTTP Range requests are supported on this resource. It is RECOMMENDED that HTTP compression is also supported.

Please see RFC2616 for more information on HTTP Range requests.

3.10.7.2 PUTThis does a replacement of the content stream.

The following optional arguments may be supplied. Please see the domain model for more information: overwriteFlag.

o If not specified, this defaults to ‘true’ in this binding and behaves consistent with AtomPub.

Success HTTP code: 201

Success HTTP code: 200 (with content), 204 (without content) or 201 if a new resource is created. Please see the HTTP specification for more information.

Returns headers: Content-Location: URI for content stream Location: URI for content stream

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 225 of 240

103081030910310

10311

103121031310314

1031510316

10317103181031910320103211032210323

1032410325

103261032710328

1032910330

1033110332

1033310334103351033610337

1033810339

103401034110342

10343103441034510346

673674675

Page 226: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

3.10.7.3 DELETEThis removes the content stream.

3.10.8 ACL ResourceCMIS Services:

GET: getACLPUT: applyACL

Media Type: application/cmisacl+xml

3.10.8.1 GETThis returns the CMIS ACL for a specified object. The client will follow the link on the atom entry to get the CMIS ACL for that object.

Request:GET /objacl/59fe373b-0348-493e-baaf-21089b596f0afd79b7bd-2579-4ad1-aea2-eda89527fbef HTTP/1.1Host: example.org

Response:HTTP/1.1 200 OkDate: Mon, 19 Oct 200925 Jan 2010 10:1021:00 -07000800Content-Length: 758Content-Type: application/cmisacl+xmlLocation: /objacl/59fe373b-0348-493e-baaf-21089b596f0afd79b7bd-2579-4ad1-aea2-eda89527fbef

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><cmis:acl xmlns:app="http://www.w3.org/2007/app" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/" xmlns:cmism="http://docs.oasis-open.org/ns/cmis/messaging/200908/" xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"> <cmis:permission> <cmis:principal> <cmis:principalId>Al Brown</cmis:principalId> </cmis:principal> <cmis:permission>cmis:read</cmis:permission> <cmis:permission>cmis:write</cmis:permission> <cmis:permission>cmis:all</cmis:permission> <cmis:permission>publish</cmis:permission> <cmis:direct>true</cmis:direct> </cmis:permission></cmis:acl>

Please also see the example documents included with the schema.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 226 of 240

1034710348

10349103501035110352

1035310354

10355

103561035710358

103591036010361103621036310364103651036610367103681036910370103711037210373103741037510376103771037810379103801038110382103831038410385103861038710388103891039010391103921039310394

676677678

Page 227: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

4 Web Services Binding4.1 OverviewAll services and operations defined in the Domain Model are presented in the Web Services binding. The WSDL for these services reference two XSD documents. One defines elements for the primary data types of documents, folders, relationships and policies as well as collections of these types of objects. The second XSD defines the message formats for each of the CMIS services; the messages often refer to the data types defined in the first XSD schema. The WSDL presents exactly the abstract services defined in the Services section.The normative CMIS Web Services binding is defined by the WSDL and XSD as well as the details given here in this part of the CMIS specification except the examples.

4.1.1 WS-IA CMIS Web Services binding MUST comply with WS-I Basic Profile 1.1 and Basic Security Profile 1.0.

4.1.2 AuthenticationA CMIS Web Services binding SHOULD support WS-Security 1.1 for Username Token Profile 1.1 and MAY also support other authentication mechanisms. A CMIS repository MAY grant access to all or a subset of the CMIS services to unauthenticated clients.

4.1.3 Content TransferA CMISAll endpoints of the Web Services binding SHOULD supportMUST be MTOM content transfers. It MUST accept content that is base64 encoded.enabled.Reporting ErrorsServices MUST report errors via SOAP faults. The CMIS-Messaging.xsd defines a basic fault structure that includes an error code and an error message and the WSDL for each service defines specific messages that have the basic fault format.

4.2 Web Services Binding MappingThe Domain Model defines all services, operations, parameters and objects of CMIS. The Web Services binding is an exact one-to-one mapping of this definition with small exceptions that are explained in the next section. Operations and parameters are named exactly after their counterparts in the Services section. All rules and exceptions defined there apply to the Web Services binding. Optional parameters and optional return values are not set if they are missing or their value is NULL.

4.3 Additions to the Services section

4.3.1 updateProperties and checkIn SemanticsThis binding supports partial properties updates. All properties passed to updateProperties or checkIn will be updated to their new values. Properties that are passed without a value will be set to their default value or un-set if no default value is defined. All others property values remain untouched.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 227 of 240

10395

103961039710398103991040010401104021040310404

1040510406

10407104081040910410

10411104121041310414104151041610417

104181041910420104211042210423

10424

10425104261042710428

679680681

Page 228: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

4.3.2 Content RangesThis binding supports the retrieval of content ranges. The operation getContentStream accepts two optional parameters:

Integer offset: The first byte of the content to retrieve. Default value is 0. Integer length: The length of the range in bytes. Default value is the size of the content minus

the offset.

If the offset value is greater than the size of the content the repository SHOULD throw a constraint exception.If offset + length is greater than the size of the content the repository should deliver the content from the offset to the end of the content.

4.3.3 ExtensionsOn all input messages and some output messages exists an element called extension. This element is used to provide vendor or repository-specific information between client and server.All of the types referenced by the schema also support xs:any for vendor or repository-specific information.

4.3.4 Web Services Specific StructuresThis binding requires specific structures that are not part of the general CMIS schema.Please also see the example request and response documents included with the schema.

4.3.4.1 cmisFaultType and cmisFaultcmisFaultType and cmisFault SHOULD be used to generate SOAP faults. See Reporting Errors.

4.3.4.2 cmisRepositoryEntryTypecmisRepositoryEntryType is the return structure of getRepositories. It contains the id and the name of a repository.

4.3.4.3 cmisTypeContainercmisTypeContainer is the return structure of getTypeDescendants. It holds a type hierarchy.

4.3.4.4 cmisTypeDefinitionListTypecmisTypeDefinitionListType is the return structure of getTypeChildren. It contains a list of types, the hasMoreItems flag and the numItem element.

4.3.4.5 cmisObjectInFolderType, cmisObjectParentsType and cmisObjectInFolderContainerType

cmisObjectInFolderType holds, in addition to a cmisObjectType object, a path segment string. It is used in all operations that support the includePathSegments parameter. cmisObjectParentsType is similar but has a relative path segment string instead of a path segment. For details about path segments and relative path segments see Part I section 2.5.3 Paths.2.1.5.3 Paths.cmisObjectInFolderContainerType contains a folder hierarchy.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 228 of 240

104291043010431104321043310434

1043510436104371043810439

10440

1044110442104431044410445

104461044710448

1044910450

104511045210453

1045410455

104561045710458

10459104601046110462104631046410465

682683684

Page 229: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

4.3.4.6 cmisObjectListType and cmisObjectInFolderListTypecmisObjectListType and cmisObjectInFolderListType hold lists of cmisObjectType and cmisObjectInFolderType structures. They also contain the hasMoreItems flag and the numItems element that are returned by operations that return these lists.

4.3.4.7 cmisContentStreamTypecmisContentStreamType wraps a content stream and additional information about the stream.

Client to Repository Repository to Client

length Length of the content stream in bytes. If set it MUST be a positive number.If the length is unknown it MUST NOT be set.

SHOULD be set SHOULD be set

mimeType MIME Media Type of the content stream.For the primary content of a document it SHOULD match the value of the property cmis:contentStreamMimeType.

SHOULD be set MUST be set

filename Filename of the content stream.For the primary content of a document it SHOULD match the value of the property cmis:contentStreamFileName.

SHOULD be set SHOULD be set

stream The content stream.MUST be present even if the content stream has 0 bytes.

MUST be set MUST be set

4.3.4.8 cmisACLTypecmisACLType is the return structure of getACL and applyACL. It contains the current Access Control List (ACL) of the object and the exact flag that indeciates if the ACL fully describes the permission of this object.

4.3.4.9 cmisExtensionTypecmisExtensionType is a placeholder for extensions. See 4.3.3 Extensions.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 229 of 240

10466104671046810469

1047010471

10472

10473104741047510476

104771047810479

685686687

Page 230: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

5 IANA Considerations5.1 Content-Type Registration

5.1.1 CMIS Query A CMIS Query Document, when serialized as XML 1.0, can be identified with the following media type:

MIME media type name: application MIME subtype name: cmisquery +xml Mandatory parameters: None Optional parameters:

"charset": This parameter has semantics identical to the charset parameter of the "application/xml" media type as specified in [RFC3023].

Encoding considerations: Identical to those of "application/xml" as described in [RFC3023], Section 3.2.

Security considerations: As defined in this specification.In addition, as this media type uses the "+xml" convention, it shares the same security considerations as described in [RFC3023], Section 10.

Interoperability considerations: There are no known interoperability issues.

Published specification: This specification. Applications that use this media type:

No known applications currently use this media type. Additional information: Magic number(s):

As specified for "application/xml" in [RFC3023], Section 3.2. File extension: .cmisquery Fragment identifiers:

As specified for "application/xml" in [RFC3023], Section 5. Base URI:

As specified in [RFC3023], Section 6. Macintosh File Type code: TEXT Person and email address to contact for further information:

Al Brown <[email protected]>OASIS CMIS TC <[email protected]> Intended usage: COMMON Author/Change controller: IESG

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 230 of 240

10480

10481

1048210483

10484104851048610487104881048910490104911049210493104941049510496104971049810499105001050110502105031050410505105061050710508105091051010511105121051310514

688689690

Page 231: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

5.1.2 CMIS AllowableActions A CMIS Allowable Actions Document, when serialized as XML 1.0, can be identified with the following media type:

MIME media type name: application MIME subtype name: cmisallowableactions +xml Mandatory parameters: None. Optional parameters:

"charset": This parameter has semantics identical to the charset parameter of the "application/xml" media type as specified in [RFC3023].

Encoding considerations: Identical to those of "application/xml" as described in [RFC3023], Section 3.2.

Security considerations: As defined in this specification.In addition, as this media type uses the "+xml" convention, it shares the same security considerations as described in [RFC3023], Section 10.

Interoperability considerations: There are no known interoperability issues.

Published specification: This specification. Applications that use this media type:

No known applications currently use this media type. Additional information: Magic number(s):

As specified for "application/xml" in [RFC3023], Section 3.2. File extension: .cmisallowableactions Fragment identifiers:

As specified for "application/xml" in [RFC3023], Section 5. Base URI:

As specified in [RFC3023], Section 6. Macintosh File Type code: TEXT Person and email address to contact for further information:

Al Brown <[email protected]>OASIS CMIS TC <[email protected]> Intended usage: COMMON Author/Change controller: IESG

5.1.3 CMIS TreeA CMIS Tree Document, when serialized as XML 1.0, can be identified with the following media type:

MIME media type name: application MIME subtype name: cmistree +xml Mandatory parameters: None.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 231 of 240

105151051610517

10518105191052010521105221052310524105251052610527105281052910530105311053210533105341053510536105371053810539105401054110542105431054410545105461054710548

10549

1055010551

10552105531055410555

691692693

Page 232: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Optional parameters:"charset": This parameter has semantics identical to the charset parameter of the "application/xml" media type as specified in [RFC3023]. Encoding considerations: Identical to those of "application/xml" as described in [RFC3023], Section 3.2. Security considerations: As defined in this specification.In addition, as this media type uses the "+xml" convention, it shares the same security considerations as described in [RFC3023], Section 10. Interoperability considerations: There are no known interoperability issues. Published specification: This specification. Applications that use this media type: No known applications currently use this media type. Additional information: Magic number(s): As specified for "application/xml" in [RFC3023], Section 3.2. File extension: .cmistree Fragment identifiers: As specified for "application/xml" in [RFC3023], Section 5. Base URI: As specified in [RFC3023], Section 6. Macintosh File Type code: TEXT Person and email address to contact for further information: Al Brown <[email protected]>OASIS CMIS TC <[email protected]> Intended usage: COMMON Author/Change controller: IESG

5.1.4 CMIS AtomA CMIS Atom Document, when serialized as XML 1.0, can be identified with the following media type:

MIME media type name: application MIME subtype name: cmisatom +xml Mandatory parameters: None. Optional parameters:"charset": This parameter has semantics identical to the charset parameter of the "application/xml" media type as specified in [RFC3023].“type”: This parameter has semantics identical to the type parameter of the “application/atom+xml” as specified in [RFC4287] Encoding considerations: Identical to those of "application/xml" as described in [RFC3023], Section 3.2. Security considerations: As defined in this specification.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 232 of 240

105561055710558105591056010561105621056310564105651056610567105681056910570105711057210573105741057510576105771057810579105801058110582

10583

1058410585

105861058710588105891059010591105921059310594105951059610597

694695696

Page 233: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

In addition, as this media type uses the "+xml" convention, it shares the same security considerations as described in [RFC3023], Section 10. Interoperability considerations: There are no known interoperability issues. Published specification: This specification. Applications that use this media type: No known applications currently use this media type. Additional information: Magic number(s): As specified for "application/xml" in [RFC3023], Section 3.2. File extension: .cmisatom Fragment identifiers: As specified for "application/xml" in [RFC3023], Section 5. Base URI: As specified in [RFC3023], Section 6. Macintosh File Type code: TEXT Person and email address to contact for further information: Al Brown <[email protected]>OASIS CMIS TC <[email protected]> Intended usage: COMMON Author/Change controller: IESG

Please see section 3.1.1 on why this media type is needed above the Atom Media Type.

5.1.5 CMIS ACLA CMIS ACL Document, when serialized as XML 1.0, can be identified with the following media type:

MIME media type name: application MIME subtype name: cmisacl +xml Mandatory parameters: None. Optional parameters:"charset": This parameter has semantics identical to the charset parameter of the "application/xml" media type as specified in [RFC3023]. Encoding considerations: Identical to those of "application/xml" as described in [RFC3023], Section 3.2. Security considerations: As defined in this specification.In addition, as this media type uses the "+xml" convention, it shares the same security considerations as described in [RFC3023], Section 10. Interoperability considerations: There are no known interoperability issues. Published specification: This specification. Applications that use this media type: No known applications currently use this media type.cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 233 of 240

105981059910600106011060210603106041060510606106071060810609106101061110612106131061410615106161061710618

1061910620

1062110622

1062310624106251062610627106281062910630106311063210633106341063510636106371063810639

697698699

Page 234: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Additional information: Magic number(s): As specified for "application/xml" in [RFC3023], Section 3.2. File extension: .cmisacl Fragment identifiers: As specified for "application/xml" in [RFC3023], Section 5. Base URI: As specified in [RFC3023], Section 6. Macintosh File Type code: TEXT Person and email address to contact for further information: Al Brown <[email protected]>OASIS CMIS TC <[email protected]> Intended usage: COMMON Author/Change controller: IESG

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 234 of 240

1064010641106421064310644106451064610647106481064910650106511065210653

10654

700701702

Page 235: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

6 ConformanceAn implementation conforms to this specification if it satisfies all of the MUST or REQUIRED level requirements defined within this specification. Specification:

This specification references a number of other specifications (see the table above). In order to comply with this specification, an implementation MUST implement the portions of referenced specifications necessary to comply with the required provisions of this specification. Additionally, the implementation of the portions of the referenced specifications that are specifically cited in this specification MUST comply with the rules for those portions as established in the referenced specification.

An implementation conforms to this specification if it satisfies all of the MUST or REQUIRED level requirements defined within this specification.

Domain Model:Normative text within this specification takes precedence over the CMIS Core XML Schema. That is, the normative text in this specification further constrains the schemas and/or WSDL that are part of this specification; and this specification contains further constraints on the elements defined in referenced schemas.

Clients:Client implementations MAY implement either Restful AtomPub Binding or the Web Services Binding.

Repositories:Repositories MUST implement the following CMIS protocol bindings:

Restful AtomPub Binding Web Services Binding

Rest Binding:This specification references a number of other specifications. In order to comply with this specification, an implementation MUST implement the portions of referenced specifications necessary to comply with the required provisions of this specification. Additionally, the implementation of the portions of the referenced specifications that are specifically cited in this specification MUST comply with the rules for those portions as established in the referenced specification.Additionally normative text within this specification takes precedence over the CMIS RestAtom XML Schema. That is, the normative text in this specification further constrains the schemas and/or WSDL that are part of this specification; and this specification contains further constraints on the elements defined in referenced schemas.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 235 of 240

10655

106561065710658106591066010661106621066310664

106651066610667

10668106691067010671106721067310674

10675106761067710678

1067910680106811068210683

106841068510686106871068810689106901069110692106931069410695

703704705

Page 236: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

The CMIS RestAtom XML takes precedence over any examples or non-normative outlines included either in this document or as standalone examples.

Web Services Binding:Normative text within this specification takes precedence over the CMIS Messaging XML and CMIS WSDL. That is, the normative text in this specification further constrains the schemas and WSDL that are part of this specification; and this specification contains further constraints on the elements defined in referenced schemas.The CMIS Messaging XML and CMIS WSDL takes precedence over any examples or non-normative outlines included either in this document or as standalone examples.

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 236 of 240

10696106971069810699107001070110702107031070410705

706707708

Page 237: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

A. AcknowledgementsThe following individuals have participated in the creation of this specification and are gratefully acknowledged:

Participants:Philippe Allart, AdullactFlorian Bartels, fme AGFred Boiscuvier, Exalead, Inc.Al Brown, IBMJay Brown, IBMMark Carlson, Sun MicrosystemsDerek Carr, IBMDavid Caruana, Alfresco SoftwareEric Chan, Oracle CorporationSameer Charles, Magnolia International AGDavid Choy, EMC CorporationScott Conroy, IndividualCornelia Davis, EMC CorporationKevin Dorr, Flatirons Solutions CorporationJason Dubreuil, Fidelity InvestmentsBetsy Fanning, AIIMSteffen Frederiksen, Content Technologies ApSStephan Friedl, QuarkDustin Friesenhahn, Microsoft CorporationGary Gershon, IndividualPaul Goetz, SAP AGGregory Grefenstette, Exalead, Inc.Florent Guillaume, NuxeoEthan Gur-esh, Microsoft CorporationMartin Hermes, SAP AGJens Huebel, Open Text CorporationDavid Izatt, Structured Software Systems Limited (3SL)Gershon Janssen, IndividualVolker John, Saperion AGShane Johnson, Citytech, Inc.Christophe Kijewska, AdullactIjonas Kisselbach, VamosaMark Klamerus, IndividualStephan Klevenz, SAP AGBoris Kraft, Magnolia International AGAlison Macmillan, Oracle CorporationMichael Marth, Day SoftwareMary McRae, OASIS Ryan McVeigh, Oracle CorporationJuerg Meier, fme AGGregory Melahn, IBMPat Miller, Microsoft CorporationFlorian MuellerMüller, Open Text CorporationThomas Mueller, Day SoftwareJohn Newton, Alfresco SoftwareDavid Nuescheler, Day SoftwareConleth O'Connell, Vignette Corporation

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 237 of 240

10706

1070710708

10709107101071110712107131071410715107161071710718107191072010721107221072310724107251072610727107281072910730107311073210733107341073510736107371073810739107401074110742107431074410745107461074710748107491075010751107521075310754107551075610757

709710711

Page 238: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

Dominique Pfister, Day SoftwarePeeter Piegaze, Day SoftwareDavid Pitfield, Oracle CorporationNorrie Quinn, EMC CorporationCraig Randall, Adobe CorporationCelso Rodriguez, ASG Software SolutionsSteve Roth, Oracle CorporationPatrick Ryan, IBMAngela Schreiber, Day SoftwareSpencer Shearer, Exalead, Inc.Madi Solomon, Pearson PLCWojciech Specht, fme AGMaik Uhlenberg, fme AGOliver Walthard, Day SoftwarePatrick Ward, Booz Allen Hamilton

Original Authors of the initial contribution:Al Brown, IBMDavid Choy, EMCCornelia Davis, EMCEthan Gur-Esh, Microsoft

Original Acknowledgements of the initial contribution:Al Brown, IBMDavid Caruana, AlfrescoDerek Carr, IBMDavid Choy, EMCCornelia Davis, EMCPaul Goetz, SAPEthan Gur-Esh, MicrosoftMartin Hermes, SAPJens Hubel, OpenTextJay Brown, IBM Ryan McVeigh, OracleGregory Melahn, IBMFlorian MuellerMüller, OpenTextJohn Newton, AlfrescoNorrie Quinn, EMCSteve Roth, OracleCraig Randall, EMC

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 238 of 240

107581075910760107611076210763107641076510766107671076810769107701077110772

10773107741077510776107771077810779107801078110782107831078410785107861078710788107891079010791107921079310794107951079610797

712713714

Page 239: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

B. Non-Normative Text

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 239 of 240

10798

10799

715716717

Page 240: OASIS Specification Templatexml.coverpages.org/CMIS-spec-v10-CD6-PublicReview.doc  · Web viewIntroduction. The Content Management Interoperability Services (CMIS) standard defines

C. Revision History

Revision Date Editor Changes Made

1.0 01/11/2010 Al Brown

First specification

cmis-spec-v1.0 11 January 2010Copyright © OASIS® 2010. All Rights Reserved. Page 240 of 240

10800

10801

10802

718719720