From CMS Products to Open Content Repositories – A Paradigm Shift

Proprietary content management systems cause access, maintenance and management problems, resulting from the lack of a single source/standard for repository interactions. So what’s the solution? JSR170, a content repository API, provides a common programmatic interface that stops architecture, data source, and protocol from being obstacles to common versioning, transactions, and locks.

Though JSR170 doesn’t solve all enterprise content management problems, standardization and portable content
repositories reduce complexity and cost. Read the white paper (PDF) by Ram Sarma and Krishnanand Kuruppath to understand how.

Leave a Reply

This is a captcha-picture. It is used to prevent mass-access by robots. (see: www.captcha.net)

You must read and type the 5 chars within 0..9 and A..F, and submit the form.

  

Oh no, I cannot read this. Please, generate a

The Workplace Blog. Enterprise with an edge.

The Workplace offers engaging expert perspectives on trends, research, products, and other news about intranets, extranets, portals, information and knowledge management, enterprise 2.0, and emerging workplace solutions.

Join the workplace -secure your edge.