DCTM-CMIS RESTful URIs and AS format

where can we find information on all the standard supported URIs used by the DCTM-CMIS implementation? Is there a list of these URIs available publicly somehwere? Also, where can we find the application state exchange format ie the xml format used for requests and responses? Is there any standard publication?

Find more posts tagged with

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Accepted answers

abc123

EMC CMIS complies with OASIS CMIS spec and its referencing RFCs. CMIS spec also provides the schemas for data exchange and some sample messages for request/response.

You can call OPTIONS http://{hostname}:{port}/{emc-cmis-root-context}/resources/ to get the resource structure and available options on these resources.

EMC CMIS EA releases did not output mapping document.

Regards,

William

All comments

abc123

EMC CMIS complies with OASIS CMIS spec and its referencing RFCs. CMIS spec also provides the schemas for data exchange and some sample messages for request/response.

You can call OPTIONS http://{hostname}:{port}/{emc-cmis-root-context}/resources/ to get the resource structure and available options on these resources.

EMC CMIS EA releases did not output mapping document.

Regards,

William

ASamal

your suggestion was really helpful. So, when I did the OPTIONS stuff, it gave me an xml document. Is the schema of this document something that CMIS specifies? If yes, where can I find it? Sorry to bother you again?

NB: This xml document (as downloaded thru OPTIONS) looks to be some kind of wsdl. What is the conceptual approach behind this? Is it an attempt to explain the structure of a RESTful service?

abc123

WADL is out of CMIS spec. It gives the client a clear description of the system resource structure about where the resources are and what options you can do.

Note that different vendors may design different resource structure in their CMIS reference implementation. So to build a robust CMIS application, you need to follow CMIS spec to navigate resources, not the relative url path from the WADL. Take folder entry as an example, you should get folder's children feed by accessing folder entry's "Down" link, other than a hard-code URL "/{object_id}/children" in your application.

Regards,

William