
Content management players who want to demonstrate conformance to Java will need to support this new API with their repositories. This will require time, effort and significant dollars. Predictions are that many content management systems (CMSs) manufacturers will dispense with developing their own repositories entirely and start obtaining them from suppliers who possess repositories that already conform to JSR 170. Future CM market development funds will no longer be directed toward the widest assortment of APIs or entirely new repositories but will be invested instead in content management application features. This should lead to the creation of a new IT sector by late 2004: the content infrastructure market.
Find out how Java Standards are developed and accepted
Why develop this new standard?
There is no current JSR that addresses the global problems with accessing data repositories. Large organizations have data in many different formats, platforms and locations. There are also many different producers and consumers of information and data. Data access problems occur because each interface, data conversion, version, access authorization, synchronization and storage is done by different applications and platforms. Maintaining access and upgrading infrastructure is difficult, expensive and time consuming. What is needed is a standard, uniform way to access and control all of this information.
Industry leaders take part in JSR 170
Scientific Research, Industry Support and News
Day's Leading Role
Day is leading the industry in developing a standard API ( JSR 170 ) to access content repositories in Java 2 independently of implementation. Day’s CTO, David Nuescheler, is the specification lead and over 20 companies have joined the group including Apache, ATG, BEA, HP, IBM, Oracle, Rational, Broadvision, Documentum, Interwoven, SAP, Venetica and Vignette.
CRX Content Repository Extreme
CRX is Day's content repository fully implementing the new Java Content Repository API (JCR) standard that makes your high value content easily accessible for any application.
Find out more about our native JSR 170 Content Repository...
