Gilbane SF: Content Integration Standards -- CMIS, JSR-170, JSR-283

One of the final sessions at Gilbane SF yesterday was around content standards: CMIS, JSR-170 and JSR-283.

Many realize there are several challenges with CMIS in particular and efficiently working with content from disparate content repositories in general.

The session aimed at shedding light on some of these challenges and possible solutions in the standards space.
 

Too Much Content in Too Many Content Repositories

Chances are, if you’re in the enterprise content management space and you have an ECM system, this still doesn’t solve all your ECM problems. There are also document management and digital asset management systems, for example, you need to be able to “talk to.” Users of one ECM system often need to access and store documents in an entirely different content repository.

Content standards existing right now are conceptually simple but challenging to implement. At the same time, many realize that content integration standards hold some promise for developing an enterprise-wide content infrastructure.

During the Gilbane SF session on content standards, we looked at challenges and prospects for existing and future standards like JSR-170, CMIS and JSR 283.

Moderated by Larry Hawes, the session featured two implementers who tried to address content integration problems.

CMIS, or Can Content Management Software Keep Pace?

Dick Weisinger, vice president and chief technologist at Formtek kicked off his presentation full of interesting statistical numbers. Weisinger’s pointed out a fact we’re all very well aware of: content in the digital universe is exploding.

According to a research, the amount of worldwide content was estimated at the following numbers:

• 2003 — 20 exabytes
• 2008 — 486 exabytes
• 2010 — 988 exabytes

At the same time, the hardware costs are shrinking. The question posed by Weisinger was whether software can keep pace in this ever-changing industry landscape.

From content management to other related areas, the speaker discussed how search algorithms have evolved, but the search is still really not very good. What makes search even more challenging is that it is hard to model enterprise usage patterns.

Nevertheless, enterprise search market is still growing with many companies doing different things with more or less success. However, today’s stats from AIIM say that 49% of business users consider finding data a difficult task to do.

Scattered data repositories only add to the challenge. The majority of companies have an assortment of repositories, be it ERP, PLM, PDM, BI, KM, WCM, or DM systems. The problems we run into with multiple repositories are compliance, eDiscovery and business intelligence.

Add to that the fact that 80% of data is unstructured, and the enterprise world looks very gloom. Search gets harder as data sets grow. It takes longer to index. Thus, it takes longer to search.

But the goal remains: extract knowledge and distill data.

How you do that?

1. Structure your data (using XML, for example)
2. Centralize multiple repositories and manage efficiencies of scale

Weisinger referred to CMIS as SQL for document management. Although, we also do need to point out that CMIS can be compared to more like HTTP for DM since it’s a protocol, as rightfully so noted by Eric Barroca, CEO of Nuxeo, who was in the audience.

comments

Useful article?

 Email It      

Follow @cmswire

Related Articles:

• Is There A Business Case For Using SharePoint as an Enterprise CMS?
• Out With IBM's Lotus Symphony, In With Apache OpenOffice IBM Edition
• More e-Discovery Announcements From LegalTech New York 2012 #ltny

Tags: cmis, enterprise cms, events, gilbane, gilbanesf, jsr-170, jsr-283, search, social media, web cms, web content management

One of the final sessions at Gilbane SF yesterday was around content standards: CMIS, JSR-170 and JSR-283.

Many realize there are several challenges with CMIS in particular and efficiently working with content from disparate content repositories in general.

The session aimed at shedding light on some of these challenges and possible solutions in the standards space.