18.01.2015 Views

Content Management Interoperability Services (CMIS) Version 1.1

Content Management Interoperability Services (CMIS) Version 1.1

Content Management Interoperability Services (CMIS) Version 1.1

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

3 AtomPub Binding<br />

3.1 Overview<br />

This binding is based upon the Atom ([RFC4287]) and Atom Publishing Protocol ([RFC5023]). Implementations<br />

of <strong>CMIS</strong> MUST be compliant with [RFC4287] and [RFC5023].<br />

In this binding, the client interacts with the repository by acquiring the service document. The client will<br />

request the service document by the URI provided by the vendor. The client will then choose a <strong>CMIS</strong><br />

collection, and then start accessing the repository by following the references in the returned documents.<br />

This binding consists of a service document specifying at least <strong>CMIS</strong> service collections, Atom collections,<br />

feeds and entry documents. <strong>CMIS</strong> extends the Atom and AtomPub documents utilizing the Atom and Atom-<br />

Pub extension mechanism. <strong>CMIS</strong> also leverages link tags to specify additional resources related to the<br />

requested resource.<br />

When requesting a resource, optional parameters may be specified to change default behavior via query<br />

parameters.<br />

3.<strong>1.1</strong> Namespaces<br />

This specification uses the following namespaces and prefixes when referring to XML or XML schema elements<br />

in the text or examples:<br />

• <strong>CMIS</strong>-Core: http://docs.oasis-open.org/ns/cmis/core/200908/<br />

Prefix: cmis<br />

• <strong>CMIS</strong>-RestAtom: http://docs.oasis-open.org/ns/cmis/restatom/200908/<br />

Prefix: cmisra<br />

• Atom : http://www.w3.org/2005/Atom<br />

Prefix: atom<br />

• AtomPub: http://www.w3.org/2007/app<br />

Prefix: app<br />

3.1.2 Authentication<br />

Authentication SHOULD be handled by the transport protocol. Please see AtomPub [RFC5023] section 14.<br />

If the provided credentials are incorrect or unknown or entirely missing, a repository MAY return the HTTP<br />

status code 403 (Forbidden) instead of the HTTP status code 401 (Unauthorized). This may prevent attacks<br />

against the Browser Binding. See also section 5.2.9 Authentication.<br />

3.1.3 Response Formats<br />

The client can specify, in HTTP the Accept header, which formats are acceptable to the client. With this<br />

mechanism the client can choose which response format the <strong>CMIS</strong> implementation should respond with.<br />

The <strong>CMIS</strong> compliant implementation MUST support the appropriate Media Types specified in this document.<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 201 of 331

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!