You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by David Nuescheler <da...@day.com> on 2008/11/20 19:17:11 UTC

jcr-cmis sandbox

Hi all,

I am currently working in a technical committee on OASIS defining a
document management interoperability specification called CMIS [1].
CMIS shoots for a protocol level interoperability between applications
and various repository vendors.

The specification is in a very early stage and a lot of things
need to be addressed [2], but it has peeked the interest of a number
of people at Apache already.

Since functionally the CMIS specification is a subset of the
JCR specification it allows a very simple and straight-forward mapping to
a fully compliant JCR repository such as Jackrabbit.

Similar to the existing protocol layers (webdav etc) on top of
JCR that are already part of Jackrabbit, I would like to propose
that we initiate first tests with an implementation in a sandbox
project.

I think that there are going to be a lot of benefits from such
an implementation. First it will allow any JCR implementation
to be CMIS compliant automatically (once the specification
is released ;) ) and allow us to find the issues to be fixed
in the specification itself and drive it into a good direction.
But most importantly it will provide an platform for
interested parties to collaborate in the open on an
implementation.
Most of the organizations on the technical committee of CMIS
are already heavily involved at Apache either as contributors or as
sponsors and are also on the JCR expert group.

Let me know what you think.

regards,
david

[1] http://lists.oasis-open.org/archives/tc-announce/200810/msg00003.html
[2] http://roy.gbiv.com/untangled/2008/no-rest-in-cmis

Re: jcr-cmis sandbox

Posted by Julian Reschke <ju...@gmx.de>.
David Nuescheler wrote:
> ...
> absolutely. i think this would be particularly interesting given the fact that a
> lot of the functionality is already defined in webdav.
> 
> i wonder if it is possibly to steer the tc into that direction.
> ...

Yes. Indeed, it would be interesting to know how much steering the TC is 
going to accept :-).

>> Another thing the CMIS TC should look into are the various proposals for
>> including support for hierarchies into AtomPub (see, for example,
>> <http://www.oracle.com/technology/tech/feeds/spec/draft-divilly-atompub-hierarchy-00.html>).
>> It seems to me that this problem is generic enough, and the solution should
>> not be specific to CMIS.
> good point.
> do you want me to post this an issue for the tc? ...or do you want to
> post it yourself.

I currently can't post to the TC mailing list, nor use the issue 
tracker, so it would be great if you did that...

BR, Julian

Re: jcr-cmis sandbox

Posted by David Nuescheler <da...@day.com>.
hi julian,

thanks for your comments.

>> ...
>> Since functionally the CMIS specification is a subset of the
>> JCR specification it allows a very simple and straight-forward mapping to
>> a fully compliant JCR repository such as Jackrabbit.
>> ...
> Yes, the more challenging part is the mapping *from* a JCR repository (how
> to deal with the information loss).
yeah, that's true.

it seems that the ideal cmis client (in our case) would be an spi client
which then in term would expose jcr again.

> Defining a mapping will be useful, because it could be re-used to define
>  the relation of CMIS and WebDAV. I think the technically most interesting
> approach would be to enhance WebDAV to carry the information it currently
> doesn't have (such as node type information), and then to build CMIS as an
> extension *into* the Jackrabbit WebDAV layer.
absolutely. i think this would be particularly interesting given the fact that a
lot of the functionality is already defined in webdav.

i wonder if it is possibly to steer the tc into that direction.

> Another thing the CMIS TC should look into are the various proposals for
> including support for hierarchies into AtomPub (see, for example,
> <http://www.oracle.com/technology/tech/feeds/spec/draft-divilly-atompub-hierarchy-00.html>).
> It seems to me that this problem is generic enough, and the solution should
> not be specific to CMIS.
good point.
do you want me to post this an issue for the tc? ...or do you want to
post it yourself.

regards,
david

Re: jcr-cmis sandbox

Posted by Julian Reschke <ju...@gmx.de>.
David Nuescheler wrote:
> ...
> Since functionally the CMIS specification is a subset of the
> JCR specification it allows a very simple and straight-forward mapping to
> a fully compliant JCR repository such as Jackrabbit.
> ...

Yes, the more challenging part is the mapping *from* a JCR repository 
(how to deal with the information loss).

Defining a mapping will be useful, because it could be re-used to define 
  the relation of CMIS and WebDAV. I think the technically most 
interesting approach would be to enhance WebDAV to carry the information 
it currently doesn't have (such as node type information), and then to 
build CMIS as an extension *into* the Jackrabbit WebDAV layer.

 > ...

Another thing the CMIS TC should look into are the various proposals for 
including support for hierarchies into AtomPub (see, for example, 
<http://www.oracle.com/technology/tech/feeds/spec/draft-divilly-atompub-hierarchy-00.html>). 
It seems to me that this problem is generic enough, and the solution 
should not be specific to CMIS.


BR, Julian

Re: jcr-cmis sandbox

Posted by Gianugo Rabellino <g....@sourcesense.com>.
David,

thanks for this. From the peanut gallery (Troy McLure moment: hi
Jackrabbits, you might remember me for being an initial mentor of
Jackrabbit, and being dragged away since graduation, yet keeping a
place in my heart for the project) I have been both interested and
quite skeptical about CMIS: maybe it's just me being an old fart, but
I love protocols more than I fancy APIs, still I can see how CMIS has
a fair deal of shortcomings.

Having said that:

On Thu, Nov 20, 2008 at 7:17 PM, David Nuescheler <da...@day.com> wrote:
> I am currently working in a technical committee on OASIS defining a
> document management interoperability specification called CMIS [1].
> CMIS shoots for a protocol level interoperability between applications
> and various repository vendors.
>
> The specification is in a very early stage and a lot of things
> need to be addressed [2], but it has peeked the interest of a number
> of people at Apache already.

Yup, that would include myself - again as an optimist hoping that
major CMIS issues might get addressed. Also, you might count on a
number of engineers in my organization (disclosure: that'll be
www.sourcesense.com) who are very much interested in the proposed
standard: we have already been thinking about ways to get our hands
dirty, and this sounds like a great opportunity.

> Since functionally the CMIS specification is a subset of the
> JCR specification it allows a very simple and straight-forward mapping to
> a fully compliant JCR repository such as Jackrabbit.

Indeed. Not to mention that, as you righteously note, having a CMIS
implementation working against the JCR RI should be useful to all
those repositories exposing a JCR layer, so I can clearly smell useful
stuff.

> Similar to the existing protocol layers (webdav etc) on top of
> JCR that are already part of Jackrabbit, I would like to propose
> that we initiate first tests with an implementation in a sandbox
> project.
> I think that there are going to be a lot of benefits from such
> an implementation. First it will allow any JCR implementation
> to be CMIS compliant automatically (once the specification
> is released ;) ) and allow us to find the issues to be fixed
> in the specification itself and drive it into a good direction.

That alone is a noble and worthwhile goal. I do believe that a wire
protocol could be really useful to the CM world and, assuming that the
TC sees the light and doesn't come up with a white elephant, I can see
value in the ASF being the good steward of an implementation providing
guidance, critique, feedback and continuous reality check to the spec
writers.

> Let me know what you think.

FWIW, I would applaud at that effort and would be following it
closely. Happy to help, if help is needed!

Thanks,

-- 
Gianugo Rabellino
M: +44 779 5364 932 / +39 389 44 26 846
Sourcesense - making sense of Open Source: http://www.sourcesense.com

Re: jcr-cmis sandbox

Posted by Michael Wechner <mi...@wyona.com>.
David Nuescheler schrieb:
> Hi all,
>
> I am currently working in a technical committee on OASIS defining a
> document management interoperability specification called CMIS [1].
> CMIS shoots for a protocol level interoperability between applications
> and various repository vendors.
>
> The specification is in a very early stage and a lot of things
> need to be addressed [2], but it has peeked the interest of a number
> of people at Apache already.
>
> Since functionally the CMIS specification is a subset of the
> JCR specification it allows a very simple and straight-forward mapping to
> a fully compliant JCR repository such as Jackrabbit.
>
> Similar to the existing protocol layers (webdav etc) on top of
> JCR that are already part of Jackrabbit, I would like to propose
> that we initiate first tests with an implementation in a sandbox
> project.
>
> I think that there are going to be a lot of benefits from such
> an implementation. First it will allow any JCR implementation
> to be CMIS compliant automatically (once the specification
> is released ;) ) and allow us to find the issues to be fixed
> in the specification itself and drive it into a good direction.
> But most importantly it will provide an platform for
> interested parties to collaborate in the open on an
> implementation.
> Most of the organizations on the technical committee of CMIS
> are already heavily involved at Apache either as contributors or as
> sponsors and are also on the JCR expert group.
>
> Let me know what you think.
>   
At the moment I cannot help much except saying that I think it's great 
that you try to explore possibilities and make an effort to make ends meet

Cheers

Michael
> regards,
> david
>
> [1] http://lists.oasis-open.org/archives/tc-announce/200810/msg00003.html
> [2] http://roy.gbiv.com/untangled/2008/no-rest-in-cmis
>   


Re: jcr-cmis sandbox

Posted by David Nuescheler <da...@day.com>.
Hi Jukka,

>> Most of the organizations on the technical committee of CMIS
>> are already heavily involved at Apache either as contributors or as
>> sponsors and are also on the JCR expert group.
> If there are existing Apache committers from other projects who'd be
> interested in working on this, then we could simplify things by
> opening write access in the Jackrabbit sandbox to all Apache
> committers.

looking at this list I already see Paolo as an "outside" apache committer.
so i think this would be a great idea.

regards,
david

Re: jcr-cmis sandbox

Posted by Paolo Mottadelli <pa...@gmail.com>.
Hi all,

2 words about me. working for Sourcesense, committer of Apache POI
implementing the Open XML format support, very close to the CM world,
in particular to JCR; I have been also working on Alfresco for a
couple of years.

I am very excited by this thread, since I am one of those hoping that
CMIS could be, at least, a battering-ram towards better
interoperability among CM vendors.

>The specification is in a very early stage and a lot of things
>need to be addressed [2], but it has peeked the interest of a number
>of people at Apache already.

Yes, this is because there is already a missing brick for CMIS in
order to be successful, that is a Reference Implementation where to
build the Specs.

> Sounds good. We can get started fast in the sandbox and decide later
> whether the effort should be promoted to Jackrabbit trunk, turned into
> a subproject, or branched off somewhere else.
>
> If there are existing Apache committers from other projects who'd be
> interested in working on this, then we could simplify things by
> opening write access in the Jackrabbit sandbox to all Apache
> committers.

So, here is one!
I like the proposal to create a sandbox where we can put stuff that
could turn out very good stuff or just junk...
Yes: sandbox + committers r/w on it would be the simplest approach.

Cheers,


-- 
Paolo Mottadelli: http://www.paolomottadelli.com
Sourcesense - making sense of Open Source: http://www.sourcesense.com

Re: jcr-cmis sandbox

Posted by Jukka Zitting <ju...@gmail.com>.
Hi,

On Thu, Nov 20, 2008 at 7:17 PM, David Nuescheler <da...@day.com> wrote:
> Similar to the existing protocol layers (webdav etc) on top of
> JCR that are already part of Jackrabbit, I would like to propose
> that we initiate first tests with an implementation in a sandbox
> project.

Sounds good. We can get started fast in the sandbox and decide later
whether the effort should be promoted to Jackrabbit trunk, turned into
a subproject, or branched off somewhere else.

> But most importantly it will provide an platform for
> interested parties to collaborate in the open on an
> implementation.

Agreed. Especially if many of the interested people are already
familiar with Apache and Jackrabbit.

> Most of the organizations on the technical committee of CMIS
> are already heavily involved at Apache either as contributors or as
> sponsors and are also on the JCR expert group.

If there are existing Apache committers from other projects who'd be
interested in working on this, then we could simplify things by
opening write access in the Jackrabbit sandbox to all Apache
committers.

BR,

Jukka Zitting