Ibm Archive

OpenCloud Manifesto = Skynet

The Terminator album cover Image via Wikipedia

Exciting to see folks pulling together some Cloud Computing standards to help us live seamlessly across the different cloud vendor offerings. I heard it first on the This Week in Tech podcast, it’s starting to sound a lot like the Terminator’s version of Skynet. Get it, clouds, skynet… Anyway, iIt seems like this should be a requirment for redundancy, not to mention the ability to move based on feature needs. Yes, sure, Cloud Computing is inherently redundant, but only across one vendor. It’ll also help us realize the best value and features quickly. I think the other thing it shows is that there is a lot of room for competition. It won’t just be the big players out there.

The manifesto itself was also interestingly absent of any of the big players. A quick glance at the manifesto and it’s refreshingly light, which is good. It seems to think more standards are on the way, which may or may not be a good thing. I think there are lots of lessons to be learned from standards like Corba or ws-deathstar. All in all good news and a recognition that the clouds are moving quickly.

Reblog this post [with Zemanta]

CMIS - will it revolutionize the CMS industry?

Last year three major CMS/ECM vendors IBM/Microsoft/ECM came together to propose new standards that will change the CMS landscape the same way SQL 92 did for the database industry.  Content Management Interoperability Services (CMIS) standards cover services that allow interoperability between content stores. These standards cover the three basic areas of Content Management Systems:

  • CMS basic operations - CRUD (Create, Retrieve, Update and delete) services, versioning and workflow

  • Content discovery - query services, search including a SQL like query

  • Domain model – object types, folder hierarchy, document, relationship and access rules

Previous interoperability proposals such as JSR 170283 have not gained traction because they were purely Java based and were too function rich, forcing the vendors to make substantial investments with little or no market driven need.    Another standard WEBDAV, was too simple and relied solely on HTTP protocol, it had no concepts of content types or content relationships.

CMIS supports both a SOAP based interface and REST based interface, the latter is much easier to implement.  Last month EMC, Microsoft, IBM and Alfresco were able to implement a draft CMIS and test it on Sharepoint/Documentum/Filenet and Alfresco.

The proposed CMIS query supports SQL like terms and clauses such as SELECT, FROM, WHERE and CONNECT by clause.  The query can include based terms and clauses based on content metadata and property such as size, date etc.  Example query:

_SELECT * FROM DOCUMENT WHERE ((CONTENT_STREAM_MIMETYPE = ‘MSWORD’) AND (CONTAINS ‘Razorfish’))

This new draft CMIS standard creates a clear firewall between applications and content stores.  It will cut application development and integrations costs, and eliminate time learning vendor specific content access APIs.  Imagine being able to design an application that can access and manipulate content from any content and change the underlying content store by merely changing an entry in some property file.   For the vendors the outlook may be murky initially, it is possible that the number of competing CMS/ECM products may shrink.  Nevertheless, the market penetration of CMS products will increase dramatically and CMS/ECM may be as ubiquitous as databases.  Microsoft’s involvement brings up the possibility that all MS Office products may support direct check in/check out from CMIS based repositories.

The CMIS draft was submitted in September ‘08 to the standards body OASIS for public comment.   It is expected to be approved by middle of 2009.  The draft is also being backed by Oracle and SAP.

Resources

CMIS charter

The draft may be accessed here as a zip.