Atom Binding documentation

[Former Member]

Hi everbody,

Is there a specific documentation about the HTTP API endpoints and how those URLs are being constructed for the cloud version of mobile docs?

We saw that URLs seem to be constructable with and without the cmisselector and we are wondering what the pattern is to call the different operations like getACL, applyACL, createDocumentFromSource etc. How can we determine the URL from the operation name? Or will all POST operations going against the /mcm/b/atom/repID/root URL with the cmisaction in the body?

Also we noticed that the Mobile Documents services enhance the standard CMIS datatypes. Therefore is there a documentation where the request and response messages for the single operations are being described?

Are the SAP XSD files available somewhere for ATOM-XML based calls? We have only found the standard CMIS XSDs which don't contain the SAP specific enhancements.

We were able to create some calls in postman using the JSON endpoints and form-urlencoded requests, but we would require to place calls in XML format. Unfortunately we are receiving back HTTP 405 errors whenever we are using XML based calls containing request structures which are taken from the standard CMIS XSDs.

Any pointers to helpful documents or blogs would be great.

[Former Member]

Hi Christian,

You are mixing up the CMIS Browser Binding and the CMIS AtomPub Binding. For example, a "cmisselector" parameter and a "/mcm/b/atom/repID/root " URL don't exist in the CMIS AtomPub Binding.

The URLs of the Browser Binding and the AtomPub Binding follow completely different rules.

The CMIS AtomPub Binding follows the AtomPub specification. That is, you start at the Service Document ("/mcm/b/atom") and follow the links. There are no simple URL patterns. (This is one of the reasons why the CMIS Browser Binding has been added in CMIS 1.1.)

The CMIS data types and extensions are binding independent. There are no schema extension and therefore no SAP specific XSD.

Here some CMIS and AtomPub documentation :

CMIS specification: http://docs.oasis-open.org/cmis/CMIS/v1.1/CMIS-v1.1.pdf (section 3 covers AtomPub)

AtomPub specification: https://tools.ietf.org/html/rfc5023#section-5.1

CMIS AtomPub examples: http://docs.oasis-open.org/cmis/CMIS/v1.1/os/examples/atompub/

Mobile Documents extensions: http://help.sap.com/saphelp_mdocs10/helpdata/en/8b/f151046a154d71b8cbdb4f08ef4492/content.htm?frames...

But I really would discourage you from using the CMIS AtomPub Binding. It's more complex, more verbose, and significantly slower for several operations.