Topics under discussion include:

• Hierarchical/complex properties
• Mixin types
• WebDAV binding
• Batch
• Multiple content streams
• Internationalization
• More explicit exceptions
• Better exposure of renditions
• RepositoryInfo Property types support
• AtomPub expressibility and clean-up
• Type management
• Records Management
• Pessimistic locking
• Workflow (integration with standards, e.g. BPMN 2.0)
• Content Tagging
• Content Recommendations
• Commenting
• User definitions (Open Social)

The Committee has also started a special workgroup to produce a browser binding proposal for CMIS 1.1.

CMIS 1.0 passes with unanimous Yes (23% of the voting members), is now an official OASIS standard http://bit.ly/bmHVhs #ECM #CMIS

15% votes are needed to ratify a specification. Nobody voted against the ratification of CMIS 1.0.

Some more information about his ratification can be found at cmswire. They wrote an article about this ratification when 15% have been reached.

Congratulations to all CMIS contributors!
Now I’m looking for a real boost on CMIS topics.

OASIS members:

We are pleased to announce that Content Management Interoperability Services (CMIS) v1.0 has been approved as an OASIS Standard [1]. The submission of the approved standard can be found at [2].

Congratulations to the OASIS CMIS TC, and the community of implementers, developers and users who have brought the work successfully to culmination.

Mary

Source: http://lists.oasis-open.org/archives/tc-announce/201005/msg00000.html

Chief Marketing Officer Kevin Cochrane commented on the new release, “CRX 2.1 is an exciting new release because it provides the IT department with greater agility. Our new capabilities are designed for rapid development of new composite content applications, native support of the Cloud and expanded standards support with JSR-283 and CMIS, including for the Microsoft Sharepoint platform. We are looking forward to engaging with the community of JCR developers on our free developer edition of CRX 2.1 and growing our online catalog of ECM solutions through our PackageShare service.”

Nearly one year ago Day started to actively support the Apache Chemistry project. Day Software Holding AG is an enterprise software provider of Web 2.0 content management and content infrastructure software.

Check out the following link to read the full story:
http://www.day.com/day/en/company/news_events/press_releases/crx21launch.html

Microsoft doesn’t have SharePoint available within the demo yet but they support this demo.

You can upload and search for content within the repositories of the following companies:

• Alfresco
• EMC
• eXo
• IBM
• Nuxeo

I tested the upload of a test1.txt document to all repositories. It worked for all except EMC. There I got an error message. Than I tried to search for the content within the demo. But It didn’t find test1 or CMIS that entered into the document.

Also the search for www.cmis.biz leads to an error. There is still something to do within this demo but it really looks promising.

You can test it at http://aiim-iecm.org

This includes:

• CMIS Query
• Web Services Binding
• REST Binding
• Access Control Lists
• Change Logs
• Renditions
• CMIS Test Compatibility Kit
• Plus Alfresco extension for Aspect query and property get/set operations

Check the release notes for further details.

See how Documentum’s web services pulls together CMIS for standards based interoperability and integrations, DFS for building and extending your client applications, and RESTful services for Rich Internet Application mash-ups.

Based on the presentation there are four main Use Cases of CMIS:

• Multi-Repository
• Application + ECM Integration
• Build Once, Use Often
• Migration

The slides offer a general guideline of usage only, as there are no hard and fast rules on which technology should be used when. The PowerPoint presentation can be downloaded  here.

We’ve presented our new CMIS module for the Web Content Management System FirstSpirit.
This module is called “DMS connect” and is responsible for the connection to the repositories of Sharepoint and Alfresco using CMIS. The module helps to easily publish documents to websites.

I showed this module to several people. Almost all of them thought that this will bring a big benefit to their publication process.

Since the CeBIT I am really sure that CMIS will become a big success!

#Microsoft has now joined #EMC, #Alfresco, #Nuxeo, & #IBM in supporting the #AIIM #CMIS demo for #aiim10. #ECM

If you like to know more about the 22010 AIIM CMIS demo or if you like to participate check the following blog post for more details.

1. Repository to Repository: This is the direct communication between repositories. This most often occurs when content needs to be managed from a central, “master”, repository.
2. Application to Repository: This is when an application that uses content stores that content in an external repository. Through the use of CMIS, the application can focus on providing its core business solution without managing the content or integrating with different repositories that may each have their own API.
3. Federated Repository: This is the presentation of a collection of repositories to a user or application as a single repository. This model occurs frequently when users need to combine the services and information available from multiple systems to satisfy searches for content across a scope larger than any individual department.

Thomas Pole is the chair of the iECM committee and Laurence Hart is a member of the iECM committee

Source: The AIIM iECM CMIS Demo

Will unstructured content be the next frontier for BI? There’s hope that Content Management Integration Services (CMIS) will do for content what SQL did for databases.

After reading the whole article you can download an interesting report:
Silo to Gold Mine: What CMIS Can (and Can’t) Do for ECM Integration.

The full article can be read here.