Dashboard > JavaPolis 2004 > ... > JavaPolis Conference > JSR-170 Standardizing the Content Repository
JavaPolis 2004 Log In   View a printable version of the current page.
JSR-170 Standardizing the Content Repository
Added by Robin Mulkers, last edited by Stephan Janssen on Jul 14, 2005  (view change)

Abstract

Today, (web) applications have to adapt to every vendor's proprietary API to interact with various content repositories. This has the negative effect of locking a large percentage of information assets in vendor specific formats, limiting access to information, impacting system evolution/migration, and availability of third party content management tools.
JSR-170 proposes an API to solve these issues.

  • What is JSR-170? What is it not.
  • Why should i care?
  • What about webdav?
  • Colorful demos, and Usecases
  • Opensource and JSR-170?
  • A Content Repository: "The Super Store"?
  • Q&A: Ask your nasty JSR-170 question

Date and Time

Audience

Intermediate: developers that have worked with content repositories (CMS, DMS, ...)

Speaker(s)

Interesting Links

this is quite an interesting topic - where can i download the slides or the presentation itself? (the link isn't activated)

thx

Posted by Doris Wagner at Mar 07, 2005 04:26 | Permalink

You can find the presentations on the JavaPolis media pages

Posted by Sven Beauprez at Mar 07, 2005 06:16 | Permalink
Site powered by a free Open Source Project / Non-profit License (more) of Confluence - the Enterprise wiki.
Learn more or evaluate Confluence for your organisation.
Hosted by JavaLobby
Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 2.2.5 Build:#520 Jun 27, 2006) - Bug/feature request - Contact Administrators