Interop and Unified Content

The Java Specification Request 170 [1], which defines a uniform application programming interface (API) for access to content repositories, might be a way to go for Open Source Content Management interoperability [2]?

Some analysts say that “June 2003 will see a reshuffling in the content management industry with final adoption of the Java Specification Request 170 (JSR 170) standard” because it addresses the main problem of CMS:

” Web applications such as Web sites, portals, shops or catalogues interact with content. These are held in content repositories, which are generally part of a content management system. The e-business sector has been faced with major challenges, because each CMS manufacturer uses its own repository API. It is not easy to exchange applications (for example, a database conforming to SQL), so integrators are forced to master various APIs, work with different application developers such as portal manufacturers, and adapt their products to a very wide range of APIs. This situation is not satisfactory for customers either – once you’ve decided on a content management system, it’s not easy to change your mind.” [3]

[1] http://www.jcp.org/en/jsr/detail?id=170&showPrint
[2] http://blog.bitflux.ch/p625.html
[3] http://www.serverworldmagazine.com/monthly/2003/01/java.shtml

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s