SAPERION Blog

Saturday saw the announcement on the OASIS members email list that Content Management Interoperability Services (CMIS) Version 1.0 was ready for public review. Review remains open until Dec. 22nd, and is open for non-OASIS members as well; thus we encourage everyone to participate and provide comments on this important ECM standard. Here is how to do that:

“Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility which can be located via [...], or directly at: http://www.oasis-open.org/committees/comments/index.php?wg_abbrev=cmis.”

Now, we are already at work to support CMIS (see CMIS, Chemistry and SAPERION Content Repository) but what about you? So far, CMIS is all the rave among the vendors, but the user community remains somewhat quiet ;-)

Last but not least, mapping names is not the only ordeal required to achieve an integration of CMIS with SCR.

Content Management Interoperability Services (CMIS) is an upcoming standard for exposing web services     (primarily REST) on top of various types of content repositories. Among them: SAPERION Content Repository (SCR).

While CMIS is in the making, Apache Chemistry is a readily available implementation that delivers most of what is needed to make CMIS work on top of SCR.

(more…)

We think: yes. There are several reasons to believe just that, among the least important of which is the fact that MS was among the group of companies who originally submitted the standards effort to OASIS. However, there are other things that make us believe that CMIS may be in for a treat by MS, particularly that MS folks have started to prove the point of CMIS by actively publishing an example about CMIS-based MOSS integration on MSDN.

(more…)

A (actually, the first) CMIS TC F2F in Redmond is coming to an end (ok, at the time of this writing, folks are still considering the issues that have been raised so far (see the CMIS Jira at http://tools.oasis-open.org/issues/browse/CMIS)). Many valuable contributions and discussions evolving around controversial aspects have taken place. Not surprising, one of the important results is the aggressive schedule set for the release of CMIS 1.0. The preliminary schedule leading to a first public draft can be found here: http://www.oasis-open.org/committees/download.php/30951/CMIS%20strawman%20schedule.xls. This schedule requires some functions to be restricted to a common denominator or to be dropped entirely. Thus, ACLs (particularly, the distinction between reading and writing ACLs), batch processing, and mix-ins (or aspects, think decorators when not familiar with AOP) will need to be further refined. (more…)

Im Wesentlichen reichen die CMIS-Funktionen, um auf Daten von typischen Dokumentenmanagementsystemen – siehe die Produkte der Initiatoren der Spezifikation, zugreifen zu können. Für eine Vereinheitlichung sämtlicher Content Repositories, wie dies die Intention des JCR ist, greift der CMIS-Funktionsumfang zu kurz. Demnach würden mit der intensiven Nutzung des CMIS zwar eine Reihe von Repositories von Anwendungen gemeinsam oder alternativ genutzt werden können, aber es blieben doch immer noch reichlich Informationsinseln übrig. Daher ist zu vermuten, dass sich langfristig eher der JCR-Standard durchsetzen wird.

Was mich befremdet ist, dass die gleichen treibenden Hersteller, die unter der AIIM-Flagge seit 5 Jahren scheinbar vergeblich um eine gemeinsame Spezifikation Namens iECM – Interoperable Enterprise Content Management – gerungen haben, parallel vor 2 Jahren die Spezifikation des CMIS begonnen haben. Bis diese Spezifikation jedoch durch die OASIS zum Standard erklärt wird, ist sicherlich noch mit eineinhalb Jahren zu rechnen. Ob dann auch der eingereichte Funktionsumfang so bleibt, ist noch abzuwarten. Day mit dem Vorsitzenden der JCR Expertengruppe, David Nuescheler, sowie einige weitere Firmen dieser Expertengruppe haben sich entschlossen, an der CMIS Standardisierung ebenfalls mitzuarbeiten. Ich bin mehr als gespannt, was dann endgültig den CMIS ausmachen wird.