Content Management Interoperability Services (CMIS) Version 1.1
Content Management Interoperability Services (CMIS) Version 1.1
Content Management Interoperability Services (CMIS) Version 1.1
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
4 Web <strong>Services</strong> Binding<br />
4.1 Overview<br />
All services and operations defined in the domain model specification are presented in the Web <strong>Services</strong><br />
binding.<br />
The WSDL for these services reference two XSD documents. One defines elements for the primary data<br />
types of documents, folders, relationships, policies, items, and secondary types as well as collections of<br />
these types of objects. The second XSD defines the message formats for each of the <strong>CMIS</strong> services; the<br />
messages often refer to the data types defined in the first XSD schema. The WSDL presents exactly the<br />
abstract services defined in the <strong>Services</strong> section.<br />
The normative <strong>CMIS</strong> Web <strong>Services</strong> binding is defined by the WSDL and XSD as well as the details given<br />
here in this part of the <strong>CMIS</strong> specification.<br />
4.<strong>1.1</strong> WS-I<br />
A <strong>CMIS</strong> Web <strong>Services</strong> binding MUST comply with WS-I Basic Profile <strong>1.1</strong> and Basic Security Profile 1.0.<br />
4.1.2 Authentication<br />
A <strong>CMIS</strong> Web <strong>Services</strong> binding SHOULD support WS-Security <strong>1.1</strong> for Username Token Profile <strong>1.1</strong> and MAY<br />
also support other authentication mechanisms. A <strong>CMIS</strong> repository MAY grant access to all or a subset of<br />
the <strong>CMIS</strong> services to unauthenticated clients.<br />
4.1.3 <strong>Content</strong> Transfer<br />
All endpoints of the Web <strong>Services</strong> binding MUST be MTOM enabled.<br />
4.1.4 Reporting Errors<br />
<strong>Services</strong> MUST report errors via SOAP faults. The <strong>CMIS</strong>-Messaging.xsd defines a basic fault structure<br />
that includes an error code and an error message and the WSDL for each service defines specific messages<br />
that have the basic fault format.<br />
4.2 Web <strong>Services</strong> Binding Mapping<br />
The Domain Model defines all services, operations, parameters and objects of <strong>CMIS</strong>. The Web <strong>Services</strong><br />
binding is an exact one-to-one mapping of this definition with small exceptions that are explained in the next<br />
section. Operations and parameters are named exactly after their counterparts in the <strong>Services</strong> section. All<br />
rules and exceptions defined there apply to the Web <strong>Services</strong> binding. Optional parameters and optional<br />
return values are not set if they are missing or their value is NULL.<br />
<strong>CMIS</strong>-v<strong>1.1</strong>-csprd01<br />
Standards Track Work Product<br />
Copyright © OASIS Open 2012. All Rights Reserved.<br />
18 August 2012<br />
Page 256 of 331
Change language