[WIKI-UPDATE] GetTogether2003Notes GT2003GianugoMatthewDavid Tue Oct 7 17:00:04 2003

[st...@outerthought.org]

Page: http://wiki.cocoondev.org/Wiki.jsp?page=GetTogether2003Notes , version: 12 on Tue Oct  7 14:25:12 2003 by BertrandDelacretaz

- * [GT2003GianugoAndMatthew]
?                 ---

+ * [GT2003GianugoMatthewDavid]
?                        +++++



Page: http://wiki.cocoondev.org/Wiki.jsp?page=GT2003GianugoMatthewDavid , version: 2 on Tue Oct  7 14:40:39 2003 by BertrandDelacretaz

- Raw notes taken collaboratively during the talk.
+ Raw notes taken collaboratively during the talk by Stefano Mazzocchi, Bertrand Delacrétaz, Rogier Peters, Steven Noels, Jeremy Quinn.
+ 
+ 
+ !!! JSR 170
+ [http://www.jcp.org/jsr/detail/170.jsp]
+ 
+ The specification lead of JSR 170, working at Day
+ 
+ Use case: the MyBank website. The bank uses a CMS for the website, another CMS for their intranet and they have to duplicate a bunch of stuff.
+ 
+ The problem with proprietary CMSes is that your stuff gets shielded behind one out of 200+ APIs related to CMS.
+ 
+ David shows some code snippets of different API that are used to connect to the various proprietary repositories.
+ 
+ Aim: One API for all content repositories - architecture, data source and protocol neutral.
+ 
+ Content is Data ++
+ Content is managed Data/Information
+ 
+ 
+ JSR has two levels of compliancy.
+ This is similar to yesterday's talk, see [GT2003HackathonJsr170]
+ 
+ Level 1 is simple to implement for vendors. Scope is:
+ * Access
+ * Read/Write
+ * Support hierarchy operations (copy/move/link)
+ * XML serialization 
+ * Search
+ * Content typing
+ 
+ Level 2 (extensive functionality)
+ * Versioning
+ * Locking
+ * Observation
+ * Transations
+ * Access control
+ 
+ Lots of overlap between webdav and JSR 170, a good parallel is HTTP and Servlet API: one is the protocol, another thing is the API.
+ 
+ He shows one of Gianugo's slides and adds JSR 170 (also based on yesterday's talk about how to build a CMS on top of cocoon)
+ 
+ {{{
+ backend <--> repository <--> frontend
+                 ^
+                 |
+                 V
+              sideend
+ }}}
+ 
+ !Current Situation
+ * going thru "community review"
+ * the open source reference implamentation is inside Jakarta Slide (inside the CVS as a proposal)
+ * the current RI is webdav-enabled already
+ 
+ !final thoughts
+ * webdav is an excellent transport layer for JSR 170 -> RI
+ * JSR 170 can be used as a generic client API to talk to a granular (property) level to a WEbdav server (and friends)
+ 
+ 
+ 
+