[Building Sakai] OASIS Content Management Interoperability Services (CMIS)

[Ian Boston]

Dont forget that when content management is mentioned in CMIS, its being mentioned by those deeply embedded in the Enterprise Content Management space which has been found to have 99.9% readers and 0.1% editors, lower density of access control (often managed at a workspace level), and structured hierarchies where the number of chid nodes at any one location rarely exceeds a few thousand.

Sakai is more application content management or collaborative content management where we have 99.9% editors, 0.1% readers. We have a high density of access control and often see millions (potentially) of child objects attached to one or more parents.

Those differences make many of the initiatives in the Enterprise Content Management space problematic to apply to Sakai. CMIS may be an exception, however from what I have seen so far it looks like its addressing interoperability between JCR like content stores.

Ian
On 6 Mar 2011, at 19:22, Nate Angell wrote:

> I read the following with interest:
> 
> <snip>
> Apache opens Chemistry content management tool kit
> In an effort to make content management systems work more harmoniously
> with one another, the Apache Software Foundation has promoted its
> Apache Chemistry interoperability toolkit to a top level project.
> 
> Chemistry is an open source implementation of the CMIS (Content
> Management Interoperability Services) standard, developed by OASIS
> (Organization for the Advancement of Structured Information
> Standards). CMIS provides a set of bindings for accessing data across
> multiple CMIS-compliant systems, without the need to understand the
> specific interface for each system.
> </snip>
> 
> According to CMIS supporters, it is designed to achieve content
> interoperability in ways that JCR didn't manage to achieve, and is
> meeting at least with some early success (at Adobe, Alfresco, IBM,
> Microsoft, Nuxeo, OpenText and SAP).
> 
> I bring CMIS and Apache Chemistry to the attention of the Sakai CLE
> and OAE communities in case they may provide fruitful pathways to
> further deepen Sakai's interoperability both as a producer and
> consumer of content.
> 
> Apache opens Chemistry content management tool kit
> http://www.computerworld.com/s/article/9210900/Apache_opens_Chemistry_content_management_tool_kit
> 
> For further reading:
> Vendors team on content-sharing spec
> http://www.infoworld.com/t/contentdocument-management/vendors-team-content-sharing-spec-043
> 
> --
> Nate Angell
> Client Evangelist
> http://www.rsmart.com
> http://twitter.com/xolotl
> http://xolotl.org
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> 
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"