![]() ![]() Luckily CMIS has a query service available to retrieve the possibilities of a repository, and it is clear, you should first investigate the repository's possibilities (to figure out how much of the spec is implemented) before integrating a CMS via CMIS. Especially if you have the idea to write an implementation which can handle multiple Content Management Systems at once, this could be a pitfall. It states clearly that a compliant CMS not necessarily will support the whole spec. A few CMIS capabilities are therefore “optional” for a repository to be compliant…” Thus, a repository implementation may not necessarily be able to support all CMIS capabilities. After reading the spec this is my major concern:Ģ.1.1.1 Optional Capabilities “. ![]() So does a new standard for integrating a CMS solves all your problems/needs? The answer -of course- is No. If you can freely choose between these two technologies I definitely would go for AtomPub because it’s the most complete one (the spec handles AtomPub in almost 100 pages, Web Services takes only 3 pages). The communication can be based on Webs Services or on Restful AtomPub. The specificationĬMIS allows you to communicate with a CMIS compliant CMS via a standard way. In this post I’ll try to give you a brief overview of the possibilities and focus points concerning a CMIS integration. This new standard is ideally suited for Repository-to-Repository (R2R) and Application-to-Repository (A2R) CMS integration. Since the first of may the first version of the CMIS spec is finalized.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |