You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@chemistry.apache.org by Florian Müller <fm...@apache.org> on 2012/10/26 23:05:56 UTC
OpenCMIS and CMIS 1.1
Hi,
The CMIS 1.1 specification is now stable. The public review ended about
two weeks ago. That is, nothing material can be changed anymore.
OpenCMIS already supports the CMIS 1.1 Browser Binding. To complete the
CMIS 1.1 support, we would have to add a few new operations and
constants.
My vision is to support CMIS 1.0 and CMIS 1.1 with the same client
library and the same server framework. The client should automatically
adapt to the CMIS version of the repository. The server framework should
be able provide endpoints for both CMIS versions.
The alternative is to provide separate libraries for each CMIS version.
That would make the internal implementation simpler, but I think that
would be more cumbersome for OpenCMIS users.
Any thoughts?
Thanks,
Florian
Re: OpenCMIS and CMIS 1.1
Posted by Florian Müller <fm...@apache.org>.
Thanks for the feedback on this topic.
I will start adding CMIS 1.1 support to the current OpenCMIS code base
soon.
- Florian
> Hi,
>
> The CMIS 1.1 specification is now stable. The public review ended
> about two weeks ago. That is, nothing material can be changed
> anymore.
>
> OpenCMIS already supports the CMIS 1.1 Browser Binding. To complete
> the CMIS 1.1 support, we would have to add a few new operations and
> constants.
>
> My vision is to support CMIS 1.0 and CMIS 1.1 with the same client
> library and the same server framework. The client should
> automatically
> adapt to the CMIS version of the repository. The server framework
> should be able provide endpoints for both CMIS versions.
>
> The alternative is to provide separate libraries for each CMIS
> version. That would make the internal implementation simpler, but I
> think that would be more cumbersome for OpenCMIS users.
>
> Any thoughts?
>
>
> Thanks,
>
> Florian
Re: OpenCMIS and CMIS 1.1
Posted by Florent Guillaume <fg...@nuxeo.com>.
Agreed, the right path is to have a single library support both versions.
As Jay is saying, even at the cost of significant extra development.
Florent
On Fri, Oct 26, 2012 at 11:31 PM, Jay Brown <ja...@us.ibm.com> wrote:
> I would strongly recommend having the latest version of OpenCMIS always
> support current and back versions of the specification. Even at the cost
> of significant extra development.
>
> Since OpenCMIS is now effectively the standard client library, having to
> use a different version to take advantage of > 1.0 versions may have the
> effect of slowing adoption or worse creating a implied/perceived
> compatibility gap between providers who move up and those that take longer
> to adopt 1.1.
>
>
> Jay Brown
> Senior Engineer, ECM Development
> IBM Software Group
> jay.brown@us.ibm.com
>
> [image: Inactive hide details for Florian Müller ---10/26/2012 02:07:08
> PM--- Hi, The CMIS 1.1 specification is now stable. The public]Florian
> Müller ---10/26/2012 02:07:08 PM--- Hi, The CMIS 1.1 specification is now
> stable. The public review ended about
>
>
>
> From:
>
>
> Florian Müller <fm...@apache.org>
>
> To:
>
>
> <de...@chemistry.apache.org>,
>
> Date:
>
>
> 10/26/2012 02:07 PM
>
> Subject:
>
>
> OpenCMIS and CMIS 1.1
> ------------------------------
>
>
>
> Hi,
>
> The CMIS 1.1 specification is now stable. The public review ended about
> two weeks ago. That is, nothing material can be changed anymore.
>
> OpenCMIS already supports the CMIS 1.1 Browser Binding. To complete the
> CMIS 1.1 support, we would have to add a few new operations and
> constants.
>
> My vision is to support CMIS 1.0 and CMIS 1.1 with the same client
> library and the same server framework. The client should automatically
> adapt to the CMIS version of the repository. The server framework should
> be able provide endpoints for both CMIS versions.
>
> The alternative is to provide separate libraries for each CMIS version.
> That would make the internal implementation simpler, but I think that
> would be more cumbersome for OpenCMIS users.
>
> Any thoughts?
>
>
> Thanks,
>
> Florian
>
>
>
>
--
Florent Guillaume, Director of R&D, Nuxeo
Open Source, Java EE based, Enterprise Content Management (ECM)
http://www.nuxeo.com http://www.nuxeo.org +33 1 40 33 79 87
Re: OpenCMIS and CMIS 1.1
Posted by Craig McClanahan <cr...@gmail.com>.
On Fri, Oct 26, 2012 at 2:31 PM, Jay Brown <ja...@us.ibm.com> wrote:
> I would strongly recommend having the latest version of OpenCMIS always
> support current and back versions of the specification. Even at the cost
> of significant extra development.
>
> FWIW, this also maintains the ability for a single client app to talk to
two different servers running different versions of CMIS as well, unless
the package names are going to be changed every version.
Craig McClanahan
Re: OpenCMIS and CMIS 1.1
Posted by Jay Brown <ja...@us.ibm.com>.
I would strongly recommend having the latest version of OpenCMIS always
support current and back versions of the specification. Even at the cost
of significant extra development.
Since OpenCMIS is now effectively the standard client library, having to
use a different version to take advantage of > 1.0 versions may have the
effect of slowing adoption or worse creating a implied/perceived
compatibility gap between providers who move up and those that take longer
to adopt 1.1.
Jay Brown
Senior Engineer, ECM Development
IBM Software Group
jay.brown@us.ibm.com
|------------>
| From: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|Florian Müller <fm...@apache.org> |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| To: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|<de...@chemistry.apache.org>, |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Date: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|10/26/2012 02:07 PM |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Subject: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|OpenCMIS and CMIS 1.1 |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
Hi,
The CMIS 1.1 specification is now stable. The public review ended about
two weeks ago. That is, nothing material can be changed anymore.
OpenCMIS already supports the CMIS 1.1 Browser Binding. To complete the
CMIS 1.1 support, we would have to add a few new operations and
constants.
My vision is to support CMIS 1.0 and CMIS 1.1 with the same client
library and the same server framework. The client should automatically
adapt to the CMIS version of the repository. The server framework should
be able provide endpoints for both CMIS versions.
The alternative is to provide separate libraries for each CMIS version.
That would make the internal implementation simpler, but I think that
would be more cumbersome for OpenCMIS users.
Any thoughts?
Thanks,
Florian
Re: OpenCMIS and CMIS 1.1
Posted by "Huebel, Jens" <j....@sap.com>.
If we manage to make a single library I agree that this would be the
preferred choice.
Jens
On 26.10.12 23:05, "Florian Müller" <fm...@apache.org> wrote:
> Hi,
>
> The CMIS 1.1 specification is now stable. The public review ended about
> two weeks ago. That is, nothing material can be changed anymore.
>
> OpenCMIS already supports the CMIS 1.1 Browser Binding. To complete the
> CMIS 1.1 support, we would have to add a few new operations and
> constants.
>
> My vision is to support CMIS 1.0 and CMIS 1.1 with the same client
> library and the same server framework. The client should automatically
> adapt to the CMIS version of the repository. The server framework should
> be able provide endpoints for both CMIS versions.
>
> The alternative is to provide separate libraries for each CMIS version.
> That would make the internal implementation simpler, but I think that
> would be more cumbersome for OpenCMIS users.
>
> Any thoughts?
>
>
> Thanks,
>
> Florian