Day Reacts to Enterprise CMS Interoperability Spec

By Irina Guseva (@irina_guseva) Sep 16, 2008

Following the initial introduction of the Content Management Interoperability Spec (CMIS) draft and reactions from Open Text and Alfresco, Day Software didn’t lag behind and responded to the proposed industry standard.

Day thinks that it’s good having a standard that functionally matches on a protocol level to what JCR (JSR170/283) specifies on an API level for Java.

CMSWire had a chance to chat with Day’s CTO David Nüscheler, and here’s what we found out.

Day’s Take on CMIS

According to Nüscheler, Day sees this new initiative as a good way to further fortify enterprise content management solutions. Day would be happy to contribute to the specification, because it validates its own standardization efforts and leadership in creation of Java standards over the past several years.

So far, Day’s involvement has been limited to reactions and readiness to implement, as heavy weight giants and originators of CMIS — EMC, Microsoft and IBM — rock the boat. “The three of the largest players in the ECM market… are well-qualified to initiate a protocol specification that is complementary to a programming API like JCR,” says Nüscheler.

Day’s Existing Standards

Day Software is not new to the standards creation business. In 2001, Day started the specification process of JCR — Java Content Repository — standards. Then, it was driven by the lack of an industry standard and high demand for non-proprietary content repositories for all content management applications, including Web Content Management, Digital Asset Management and Social Collaboration.

To keep Day’s customers happy, the company has created several content repository standards for Java technology API: JSR 170, JCR and JSR 283. Then, the CRX was born. Through involvement with JCR and open source standards around Apache Jackrabbit, Day started selling fully-compliant content repository called CRX.

This pre-existing history with standards explains why CMIS is of interest to Day: JSR 170, for example, is not supported by all Enterprise CMS vendors and is not programming language neutral. According to Day, CMIS is not competing with JSR 170, but merely mirrors it due to its platform- and language-agnostic nature.

As dutifully noted by CMS Watch, the programmers use APIs and not protocols, so it’s hard to compare HTTP, for example, with the Java Servlet spec.

Day’s Thoughts on Alfresco’s Involvement in CMIS

While we were happy to see at least one Open Source CMS vendor participate in the development of the upcoming industry standard, Nüscheler thinks that “As usual, Alfresco is making a lot of marketing noise about implementations despite that it has not even made it into a standards body yet.”