From: Adam Tauno Williams <firstname.lastname@example.org>
Sent: Friday, 15 February 2013, 13:49
Subject: Re: [libreoffice-users] Share-point?
On Fri, 2013-02-15 at 13:31 +0000, Tom Davies wrote:
Hmmm, what worries me is "MS" and "Standards" in the same sentence.
Haven't we already learned, many times over, that MS's idea of
open = closed
This is true for corporations, nothing specific to Microsoft. That is
why you need Open implementations and the ratification of a standards
body. CMIS has all these.
standards and interoperable = only works once on one system
or at least that seems to be the way it has always worked out historically.
Nope, that is already not true for CMIS.
So while it looks good i am fairly convinced there is a trap here
somewhere even if i can't see it and don't already know about it. An
OpenSource equivalent that uses the alleged 'standard' would be much
There *IS* Open Source implementations of CMIS. Alfresco is Open
Source. And there is even CMIS plugins for Drupal. There are several
other CMIS implementations, see the CMIS Wiki page - they even have a
column indicating if the implementation is Open Source or not.
Adam Tauno Williams GPG D95ED383
Systems Administrator, Python Developer, LPI / NCLA
For unsubscribe instructions e-mail to: email@example.com
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Impressum (Legal Info)
: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (MPLv2
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our trademark policy