CMIS Round Table

3,142 views
2,976 views

Published on

Interoperability is key to open source success in the enterprise applications field. Aside from the JCR (Java Content Repository) and its successor, JCR2, new standards or proposed standards are emerging, such as CMIS (Content Management Interoperability Services), that promise true interoperability between proprietary (such as Documentum, Filenet or SharePoint) and open source (such as Nuxeo and Alfresco) ECM systems. Will this standards truly unlock information from their silos and enable ECM as the backbone for unstructured information in the enterprise? Participants of this roundtable, all of them involved in various standardization efforts, will present and discuss the pros and cons of the various approaches.

Published in: Technology, Education
7 Comments
0 Likes
Statistics
Notes
  • Hi David,

    I'm not saying that connectors cannot be written, or that semantic difference cannot be overcome. I'm just saying that it's harder to do for JCR than for CMIS :)
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Hi Florent,

    I completely disagree with the statement about the semantic mismatch
    with (pre-)existing legacy content repositories and JCR.

    I think that we have a lot of experience layering JCR on top of arbitrary legacy repositories since Day Software offers connectors for following 3rd
    party repositories:

    * Microsoft SharePoint 2003, 2007
    * EMC Documentum 5.2.5, 5.3
    * FileNet P8 Content Manager 3.5
    * OpenText Livelink 9.5, 9.6, 9.7
    * Vignette 7.3.0.5, 7.3.1
    * IBM Lotus Notes 6.5, 7.0
    * Interwoven TeamSite 6.5

    http://www.day.com/content/day/en/products/crx/jcr_connectors.html

    I feel like I will have to come up with a 'JCR loves CMIS' presentation
    similar to 'JCR loves Atom' or 'JCR loves WebDAV' in the past. ;)

    regards,
    david
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Nuxeo doesn't offer a JCR API on top of its existing Nuxeo Core API, no, there hasn't been customer demand for it yet -- but we've thought about it and it's feasible. If you choose a storage backend (we have several) that is based on Jackrabbit then you can access that directly of course.

    Future versions of Nuxeo will be CMIS compliant, we're working on it.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • 'so is Nuxeo JCR compliant? And you are also making it to ensure that the CMIS policy stands?'
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • @thaneshk
    If you want to expose through the JCR API an existing repository that wasn't designed with JCR in mind, unless you're lucky you'll find that there are a lot of semantic mismatches between your data model and the one that JCR requires. They can be overcome of course, with programming you can adapt anything to anything, but that doesn't mean the end result will be 'natural' for your existing repository. If you want to store arbitrary nodes with arbitrary properties (which is what JCR clients expect), in an efficient manner so that they can be queried fast, and map that to your native repository's model, then you may find yourself having lots of mapping issues.

    Nuxeo itself doesn't have this problem, our model is quite compatible with JCR, but a lot of other database and repository vendors will have models that simply don't match very well with what JCR expects, or for which the adaptation gets complex, with many intermediate nodes for each of the native repository's documents or records. JCR doesn't see this as a problem, having many nodes to represent data is the way JCR does things, but that's different enough that it may give pause to vendors.

    The JCR API manipulates nodes with simple properties on them. That's about as fine grained as you can get, in a hierarchical model. I contend that vendors aren't that interested in having clients or servers talking at such a low level, using such a rich API. And the richer the API to implement, the more complex it is to get the exact semantics required. This is what I mean by 'too fine grained for high interoperability'.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Be the first to like this

No Downloads
Views
Total views
3,142
On SlideShare
0
From Embeds
0
Number of Embeds
70
Actions
Shares
0
Downloads
89
Comments
7
Likes
0
Embeds 0
No embeds

No notes for slide

CMIS Round Table

  1. 1. Standards and interoperability for ECM <ul><li>JCR 2, CMIS, etc. </li></ul><ul><li>Round Table </li></ul><ul><li>Florent Guillaume – Nuxeo </li></ul><ul><li>John Newton – Alfresco </li></ul>Florent Guillaume | NUXEO DEV DAY 2008
  2. 2. JCR and CMIS NUXEO DEV DAY 2008
  3. 3. The state of JCR <ul><li>Content Repository for Java </li></ul><ul><li>JSR-170, released in June 2005 </li></ul><ul><li>Initiated by Day Software </li></ul><ul><ul><li>Also BEA, Documentum, FileNet, IBM, Oracle, Vignette and others </li></ul></ul><ul><li>Apache Jackrabbit is the RI </li></ul>NUXEO DEV DAY 2008
  4. 4. The state of JCR 2 <ul><li>JSR-283, first public review July 2007 </li></ul><ul><li>Final release expected early 2009 </li></ul><ul><li>Nuxeo and Alfresco also contributing </li></ul>NUXEO DEV DAY 2008
  5. 5. JCR – Basics <ul><li>CRUD </li></ul><ul><ul><li>Hierarchy of nodes </li></ul></ul><ul><ul><li>Simple properties, Lists, Binaries </li></ul></ul><ul><li>Queries </li></ul><ul><li>Versioning, Locking, References, ... </li></ul>NUXEO DEV DAY 2008
  6. 6. JCR – Goals <ul><li>Java API </li></ul><ul><li>Fine-grained storage model </li></ul><ul><li>Lots of functionality </li></ul><ul><li>Be the “SQL” of hierarchical storage </li></ul>NUXEO DEV DAY 2008
  7. 7. JCR – Problems for ECM <ul><li>Java API </li></ul><ul><li>Constrains the storage model a lot </li></ul><ul><li>Too fine grained for high interoperability </li></ul>NUXEO DEV DAY 2008
  8. 8. The state of CMIS <ul><li>Draft v 0.5 published in September 2008 by EMC, IBM, Microsoft </li></ul><ul><ul><li>Alfresco, Open Text, Oracle, SAP also on board from the start </li></ul></ul><ul><li>Oasis TC formed in November 2008 </li></ul><ul><ul><li>Adullact, Booz Allen Hamilton, Day, Ektron, Exalead, Fidelity, Flatirons, Magnolia, Mitre, Nuxeo , Saperion, Sun, Vamosa, Vignette (as of 2008-12-01) </li></ul></ul><ul><li>CMIS 1.0 expected mid-2009 </li></ul>NUXEO DEV DAY 2008
  9. 9. CMIS – Goals <ul><li>Simple document model </li></ul><ul><li>Independent of protocol </li></ul><ul><ul><li>SOAP, REST (AtomPub) bindings </li></ul></ul><ul><ul><li>Not tied to a programming language </li></ul></ul><ul><ul><li>Platform, vendor independent </li></ul></ul><ul><li>Basic set of ECM functions </li></ul><ul><ul><li>“Greatest common denominator” </li></ul></ul>NUXEO DEV DAY 2008
  10. 10. CMIS – Basics <ul><li>CRUD </li></ul><ul><ul><li>Hierarchy folders, Documents </li></ul></ul><ul><ul><li>Simple properties, Lists, One binary </li></ul></ul><ul><li>Policies </li></ul><ul><li>Versioning </li></ul><ul><li>Relationships </li></ul><ul><li>SQL Queries </li></ul>NUXEO DEV DAY 2008
  11. 11. CMIS – Advanced <ul><li>Multi-filing </li></ul><ul><li>Advanced queries </li></ul><ul><ul><li>Joins </li></ul></ul><ul><ul><li>Full text </li></ul></ul><ul><li>... maybe more? </li></ul>NUXEO DEV DAY 2008
  12. 12. Other related standards <ul><li>Network filesystems (NFS, SMB, etc.) </li></ul><ul><li>HTTP </li></ul><ul><li>WebDAV, DeltaV </li></ul><ul><li>RSS, AtomPub </li></ul><ul><li>RDF, Dublin Core </li></ul>NUXEO DEV DAY 2008
  13. 13. Round Table <ul><li>Florent Guillaume – Nuxeo </li></ul><ul><li>John Newton – Alfresco </li></ul>Presenter Name | NUXEO DEV DAY 2008
  14. 14. Proposed topics <ul><li>What features in an ECM standard? </li></ul><ul><li>Customer benefits </li></ul><ul><li>Vendor benefits </li></ul><ul><li>Proprietary vendors and standards </li></ul><ul><li>Open Source </li></ul>NUXEO DEV DAY 2008
  15. 15. What features in an ECM standard? <ul><li>Document model </li></ul><ul><li>Protocols </li></ul><ul><li>Language APIs </li></ul><ul><li>Services </li></ul>NUXEO DEV DAY 2008
  16. 16. Cutomer benefits <ul><li>Interoperability between vendors </li></ul><ul><li>Common model </li></ul><ul><li>“Desilofication” </li></ul><ul><li>“Commoditization” </li></ul>NUXEO DEV DAY 2008
  17. 17. Vendor benefits <ul><li>Repository vendors get more applications </li></ul><ul><li>Applications vendors get more repositories </li></ul><ul><li>PR </li></ul>NUXEO DEV DAY 2008
  18. 18. Proprietary vendors and standards <ul><li>Do vendors really want to interoperate? </li></ul><ul><li>When are they going to? </li></ul><ul><li>Less “bridging” vendors? </li></ul><ul><li>Are existing standards really being adopted? </li></ul><ul><li>Are new standards being sought? </li></ul>NUXEO DEV DAY 2008
  19. 19. Open Source <ul><li>More repositories </li></ul><ul><li>More clients </li></ul><ul><li>More applications </li></ul><ul><li>More competition as well! </li></ul>NUXEO DEV DAY 2008

×