The WeWebU development team worked hard for the last three quarters in order to make it happen. “We are very proud to ship first deliveries of the latest version of WeWebU OpenWorkdesk to customers and partners”, says Dr. Rainer Pausch, Head of Products & Marketing at WeWebU. “Besides many incremental improvements we concentrated on four main areas which will open new markets to us and shall set us far ahead of the competition”, he adds.

WeWebU OpenWorkdesk 3.0 is compliant with section 508 of the US Rehabilitation Act and thus ensures accessibility for handicapped people. This is a prerequisite for entering the huge and very attractive market of governmental institutions especially in the United States of America and Canada. The support of CMIS (Content Management Interoperability Services) is another door opener for new markets since it allows WeWebU OpenWorkdesk to work with content form literally any modern ECM repository that supports this standard. Stefan Waldhauser, CEO of WeWebU is excited: “CMIS the SQL for content management is changing the ECM world – and we are part of it. Now applications build with WeWebU OpenWorkdesk can run on and combine content from such different sources like IBM ECM Systems, Alfresco and even Microsoft SharePoint. This is positive for our customers who now have a much greater choice for their backend system and WeWebU alike, since our potential customer base grows by magnitudes!” In order to bring the documents from all those different systems to the user WeWebU OpenWorkdesk now comes with an Advanced Viewing component that is capable to display literally all documents regardless of origin and format. “Advanced Document Viewing as well as other productivity enhancing features like improved bulk processing of documents, e-mail integration, and stored searches further improve the usability of OpenWorkdesk and thus the efficiency of its users”, concludes Dr. Pausch.

But not only the new features of OpenWorkdesk 3.0 are impressing. Stefan Waldhauser proudly explains: “Along with the development of this release we took two big and important steps that significantly boosted our product quality. First, we introduced the development method SCRUM that enables us every three weeks to create potentially shippable releases of our software that are tested and evaluated by our partners. Second, we went even further by making large parts of OpenWorkdesk open source. At www.openworkdesk.org everybody can download the Community Edition of OpenWorkdesk as well as the source code for tests, evaluation and even real projects. The feedback from both user groups immediately flows back into our development process and enables us to continually apply corrections and improvements.”

WeWebU OpenWorkdesk 3.0 is general available immediately.

About WeWebU Software AG

WeWebU Software AG is the specialist for Enterprise Information Management. With our standard products, enterprises can access their complete information infrastructure via a unified, process-oriented working environment. Thus, they reduce costs, increase their employees’ productivity, come to decisions faster and better, and make their whole enterprise more agile. WeWebU Software AG operates internationally. It cooperates with leading EIM manufacturers and consulting firms and is an IBM Advanced Business Partner as well as Alfresco Systems Integrator & Solutions Partner. The continually growing customer-base of WeWebU Software AG consists of e.g. Bayerischer Rundfunk, SAPERION AG, Siemens AG and DATEV e.G., financial institutions like Hamburger Sparkasse, Sparkasse Bremen, UniCredit Leasing, Visana Group, SUVA and NÜRNBERGER Versicherungsgruppe as well as several US federal and state agencies like the California Department of Public Health.

The Hippo Site Toolkit 1 is an open source toolkit for Java Web developers that are using Hippo CMS 6 and Hippo Repository 1. The tools can be used while developing websites, intranets and applications in combination with the Hippo Content Repository. The current version of the Hippo Site Toolkit is 1.02.02.

Click here to get further information.

So this means that the SharePoint Server 2010 now has the functionality to act as as CMIS client and as a CMIS server.

Click here to read the full article at TechNet.

The article deals with the following topics:

• About the CMIS standard and specification
• About the CMIS Producer and CMIS Consumer Web Part
• Installing and configuring CMIS connectors
• Bindings and permissions
• Mapping the CMIS data model to SharePoint concepts

Now I will write something about the developer of this explorer. Nicolas Raoul is 28, French and living in Tokyo.

He has been working at Aegif (Alfresco partner) for one year, the only foreigner in his company. Aegif was founded by ex-Documentum people when Alfresco appeared, and is the exclusive partner in Japan for Alfresco and Liferay. They contribute localizations and answer questions on the Alfresco Japanese forum, among other things.
They have been following the details of CMIS since June 2009. Their blog is actually one of the only Japanese websites talking about CMIS:
http://aegif.typepad.jp/blog (You need to be able to read Japanese )
Struts2CmisExplorer is their second CMIS-based project.

They realized a lot of companies needed a lighter alternative to the complex full-featured web clients that come with ECM products (for instance the “Alfresco Explorer”). Those juggernauts are great for power-users, but employees are usually provided with a lighter, simpler webapp. Clients sometimes also need a simple interface to check “their” documents (bills, reports, etc).

Those interfaces are basically showing the files of a particular directory, embedded into the company’s portal, and are usually developed for a particular ECM product.

So they wanted such a reusable browser, that they could easily integrate into any client’s portal, working with any ECM product. For the repository protocol, the choice was not hard. JCR could have worked, but CMIS is much more promising for document management. Even though most proprietary ECM products don’t support it yet.

For the UI library, they chose Struts2 because it is one of the most widespread enterprise web frameworks. Companies will not be afraid of using Struts2, and chances are they already use it. They brainstormed about the name, from monster names to totally abstract names, but finally settled for Struts2CmisExplorer, a plain and simple concatenation that leaves no ambiguity.

Struts2CmisExplorer was born to be forked. For instance some people will probably need to integrate it with Spring IoC, and Nicolas would love them to create a branch for this. He uses GitHub for source control, which makes branching/merging easy and visual.

About Nicloas: He released his first open source software in 1998, then studied maths and IT. He has worked in 14 countries and speaks 6 languages.
Projects: He worked on the French Air Force’s Document Management system, then on French National Library’s central document management system. He designed a part of the Schengen Information System (Europe polices database), and worked on HTML5 at W3C.

Struts2CmisExplorer is open source and available at http://code.google.com/p/struts2cmisexplorer/.

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

Late breaking news: It turns out that the current CMIS download on ECN Labs is already 1.0 compliant, so there won’t be another release in May. Also, the ECN Labs downloads are for preview purposes only.  As stated below, official product support for CMIS will be in the Documentum 6.7 release.

Read the full story at the EMC blog

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

The CMIS Connector for SharePoint provides a CMIS (Content Management Interoperability Services)interface over the top of SharePoint as well as a CMIS consumer Web Part that can be used to display content from other CMIS enabled repositories.

Click here to read the blog post.

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