CMIS Round Table

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

more share options
Embed For WordPress.com

Without related presentations

7 comments

Comments 1 - 7 of 7 previous next Post a comment

+ Florent Guillaume 7 months ago
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 :)
+ David Nuescheler 7 months ago
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
+ Florent Guillaume 7 months ago
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.
+ thaneshk 7 months ago
'so is Nuxeo JCR compliant? And you are also making it to ensure that the CMIS policy stands?'
+ Florent Guillaume 7 months ago
@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'.
+ thaneshk 7 months ago
i have huge issues with Slide 7

Could you explain what you meant by 'Constrains the storage model alot' - Are you talking DB or just figuring out what your object model should be?

'too fine grained for high interoperability' - ???????
+ David Nuescheler 9 months ago
Of course i violently disagree with bullets 2 & 3 on slide 7 of this deck ;)

Notes on slide 1

Favorites, Groups & Events

CMIS Round Table - Presentation Transcript

Standards and interoperability for ECM
- JCR 2, CMIS, etc.
- Round Table
- Florent Guillaume – Nuxeo
- John Newton – Alfresco
Florent Guillaume | NUXEO DEV DAY 2008
JCR and CMIS NUXEO DEV DAY 2008
The state of JCR
- Content Repository for Java
- JSR-170, released in June 2005
- Initiated by Day Software
- Apache Jackrabbit is the RI
NUXEO DEV DAY 2008
The state of JCR 2
- JSR-283, first public review July 2007
- Final release expected early 2009
- Nuxeo and Alfresco also contributing
NUXEO DEV DAY 2008
JCR – Basics
- CRUD
- Queries
- Versioning, Locking, References, ...
NUXEO DEV DAY 2008
JCR – Goals
- Java API
- Fine-grained storage model
- Lots of functionality
- Be the “SQL” of hierarchical storage
NUXEO DEV DAY 2008
JCR – Problems for ECM
- Java API
- Constrains the storage model a lot
- Too fine grained for high interoperability
NUXEO DEV DAY 2008
The state of CMIS
- Draft v 0.5 published in September 2008 by EMC, IBM, Microsoft
- Oasis TC formed in November 2008
- CMIS 1.0 expected mid-2009
NUXEO DEV DAY 2008
CMIS – Goals
- Simple document model
- Independent of protocol
- Basic set of ECM functions
NUXEO DEV DAY 2008
CMIS – Basics
- CRUD
- Policies
- Versioning
- Relationships
- SQL Queries
NUXEO DEV DAY 2008
CMIS – Advanced
- Multi-filing
- Advanced queries
- ... maybe more?
NUXEO DEV DAY 2008
Other related standards
- Network filesystems (NFS, SMB, etc.)
- HTTP
- WebDAV, DeltaV
- RSS, AtomPub
- RDF, Dublin Core
NUXEO DEV DAY 2008
Round Table
- Florent Guillaume – Nuxeo
- John Newton – Alfresco
Presenter Name | NUXEO DEV DAY 2008
Proposed topics
- What features in an ECM standard?
- Customer benefits
- Vendor benefits
- Proprietary vendors and standards
- Open Source
NUXEO DEV DAY 2008
What features in an ECM standard?
- Document model
- Protocols
- Language APIs
- Services
NUXEO DEV DAY 2008
Cutomer benefits
- Interoperability between vendors
- Common model
- “Desilofication”
- “Commoditization”
NUXEO DEV DAY 2008
Vendor benefits
- Repository vendors get more applications
- Applications vendors get more repositories
- PR
NUXEO DEV DAY 2008
Proprietary vendors and standards
- Do vendors really want to interoperate?
- When are they going to?
- Less “bridging” vendors?
- Are existing standards really being adopted?
- Are new standards being sought?
NUXEO DEV DAY 2008
Open Source
- More repositories
- More clients
- More applications
- More competition as well!
NUXEO DEV DAY 2008