>From the JSR: The Content Industry has defined a number of specifications on a protocol level to exchange content (ICE, WebDAV, etc.). However, there is no specification on an API level that addresses the unique requirements of a Content Repository. As well, there exists no Content Repository centric standard that appears to address issues such as version handling, full-text searching, and event-monitoring in a coherent manner
There is no standard that handles version handling, searching? I guess DELTAv and DASL don't cut it for these java folks. Why can't they implement a standard API for webDAV and make the protocol HTTP independent - in other words a DAV based API that can be webDAV, tcp-DAV, EJB-DAV (oh! please no!!!) or whatever communication channel DAV? Why reinvent the wheel? ----- Original Message ----- From: "Jason Novotny" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, August 13, 2004 10:57 AM Subject: JSR 170 support > > Hi, > > I read the mail postings of "JSR 170 available for Public Review" > and I'm interested in how important the Slide developer community feels > this API is for content management and how code integration is > progressing... like any ideas of timelines, for instance? > > Thanks, Jason > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
