Conformance
2017 R1 Update Rollup 1

ConformancePermanent link for this heading

The Fabasoft Integration for CMIS conforms to the CMIS specification and meets all of the MUST and REQUIRED level requirements defined within this specification. Supported requirements are listed in the next chapters.

Data ModelPermanent link for this heading

  • The repository identity must uniquely identify an available repository at the service endpoint.
  • A CMIS repository must have the base types:
    • cmis:document object-type
    • cmis:folder object-type
  • The root folder is a special folder such that it cannot be created, deleted, or moved using CMIS services.

ServicesPermanent link for this heading

Repository ServicesPermanent link for this heading

  • getRepositories
  • getRepositoryInfo
  • getTypeChildren
  • getTypeDescendants
  • getTypeDefinition

Navigation ServicesPermanent link for this heading

  • getChildren
  • getFolderParent
  • getObjectParents

Object ServicesPermanent link for this heading

  • createDocument
  • createDocumentFromSource
  • createFolder
  • getAllowableActions
  • getObject
  • getProperties
  • getObjectByPath
  • getContentStream
  • updateProperties
  • moveObject
  • deleteObject
  • deleteTree
  • deleteContentStream

Multi-Filing ServicesPermanent link for this heading

  • addObjectToFolder
  • removeObjectFromFolder

Restful AtomPub BindingPermanent link for this heading

  • Implementations of CMIS must be compliant with Atom (RFC4287) and Atom Publishing Protocol (RFC5023).
  • Exceptions must be mapped to the appropriate HTTP status code defined in CMIS domain model.
  • CMIS link relations must be included if the client can perform the operation.
  • Any feed must be a valid Atom Feed document.
  • Repositories must provide URI templates.

Web Service BindingPermanent link for this heading

  • A CMIS web services binding must comply with WS-I Basic Profile 1.1 and Basic Security Profile 1.0.