Content management and other types of enterprise software providers including BEA Systems, Day Software, FileNet Corporation, IBM, Open Text, Oracle, Sun Microsystems, Vignette are working together under the Java Community Process JCP program to devise a Java Specification Request 170 Content Repository.
In a clear move to drive openness across enterprise content management, collaboration, enterprise resource planning and storage, this draft specification is expected to break the proprietary back of the content management industry and help move data from proprietary silos, to open, manageable repositories of data that can be leveraged across various platforms.
Designed to enable the development of content-based applications that can be deployed on top of a number of different underlying content repositories, these companies believe the technology will help better enable customers to deploy content applications faster and more cost-effectively using an open standards interface.
"We are aiming to provide customers the added value that common content services enable when tied to business applications," said David Nuescheler, CTO of Day Software and specification lead of JSR 170. "Standards-based integration for the content management market will also open opportunity for customers to leverage multiple applications and allow data to be tapped and used across different systems in their organization."
The JSR 170 draft specification is designed to make content management software easier to deploy, provide greater access to content-rich applications and enable businesses to more easily access and leverage both structured and unstructured data within their organization. In final ballot through the JCP and expected to be fully ratified in May, the JSR 170 specification will enable applications to standardize access to content repositories.
"JSR 170 will help foster the growth of the Enterprise Content Management market by lowering content-enabled and content-centric application development costs for ISV and customer IT departments as well as lowering the integration costs shouldered by ECM vendors," said Dan Whelan, CTO for FileNet. "FileNet has contributed to the development of this standard as a member of the JSR 170 Expert Group and has incorporated an early version of the specification in its FileNet P8 Content Manager suite."
http://jcp.org.

Comments
Post new comment