CMSWire reports about one of the final session at the “Gilbane Conference San Francisco” that was about CMIS, JSR 170 and JSR 283.

The article  starts with the issue that we have a lot of content in a lot of different content repositories. According to a research, the amount of worldwide content was estimated at the following numbers:

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

This means that we really need to take care about how we can access those contents. The three standards CMIS, JSR 170 and JSR 283 can help in dealing with this problem. The article describes those standards.

JSR 170

• Lack of ease in implementing a contained 1-n parent-child relationship
• Inefficient reference model in certain cases
• Node types not useful for WCM object wrapper
• No multidimensional view of repositories
• Big ramp-up

JSR 283

• Not available yet
• Looks like a fine-tuned version of the older standard

CMIS

The speaker Naresh Devnani was excited when he first heard about this standard because of the vendor names associated with it. Big vendors are really needed in order to make it a standard. He said that CMIS should focus on collaboration between content authors, mashups and portals. Also CMIS is complimentary to search, as search alone has limited value.

The whole article can be read here.