Irina Guseva writing at CMS Wire tells us that the CMSI draft has passed a critical milestone, getting 15% of votes, in the journey to become an officially ratified OASIS standard, read her article here:
CMIS Makes it as an official standard.
She has some quotes from Alfresco, Nuxeo, IBM and Day Software, and its an interesting little read.
This is very important for the ECM industry, but actually from my perspective even more important from an ECM / content management end user perspective. Official ratification of the standard, all out support from the industry, and baking the interoperability features into as many products as possible are a very good thing.
This will make it much more easy (and elegant ?) for SI's or internal IT departments to build systems which work exactly as the business requires, not as the vendor which meets 75% of the requirement wants them to. As you will know if you have read my blog before, the important part of ECM to me is the 'strategy' - not the vision of an ECMS as a monolithic, one size fits all solution to all your unstructured information management problems. Yet I have led procurements where ECM 'suites' from the big vendors have seemed a better solution than trying to fit together disparate pieces to build something from "best of breed" products.
CMIS promises to provide the best both worlds, a middle ground where "plug and play" comes to content management, so lets keep our fingers crossed for the continued development by OASIS and all those who have put in such a great amount of effort so far :-)
Showing posts with label CMIS. Show all posts
Showing posts with label CMIS. Show all posts
Tuesday, 27 April 2010
Tuesday, 8 December 2009
Content Management vendors, and CMIS
This posting is really just a link post, no thoughtful analysis here.......
My old mate Laurence has an excellent CMIS update posting on his Word of Pie blog. He has been involved in CMIS development on behalf of AIIM, and this summary piece is well worth reading: Looking at CMIS 1.0, thinking of 2.0
On the same subjectbut with a different twist Alan at CMS Watch posted "Three reasons to list CMIS in your Document Management RFP" having written some really big ECM / EDRM RFI's and RFP's I have to agree with his logic, including this nascent yet to be fully ratified standard can still help keep your selected vendors 'honest' !
On a different subject, but still with CMS Watch, they have updated their graphical representation of the information management / content management industry and the various vendors:
As I used to live just 40 mins north of London (England, not Ontario) I really like the 'tube' metaphor (yes, we call the London Underground the 'tube' not the Metro or the Subway - Subway is a sandwich shop!). If you want a higher resolution PDF copy for printing head on over to the CMS Watch site here: Technology Vendor Map.
Tuesday, 6 October 2009
Is Google Wave really targeted at SharePoint & Office Online ?
Come on people, show some imagination !
For all those who keep churning out the fact that Google Wave has no compelling improvement of email and IM, those who constantly suggest its a social networking platform aimed at taking on Twitter and FaceBook, or stating that its gonna flop because its unfinished crud;
Jeez, stop and breath and takd a minute to think about it !
Wave is a protocol (XMPP based), not just Google's current server platform and client app. There are already independent open source implementations of servers for the protocol. Yes the Google front end is unfinished - for all those who moan about how distracting it is to seen what the other person is typing; well even in the original Google I/O conference video they point out that that there will be a private 'draft' mode that will prevent this, so you can write in peace..........
Yes the released (and hyped it) early, because they want 'community' input - so no, its not finished or polished, but come on its just gone from private Alpha to invitation only Beta, its a long way from finished product(s) and no one is saying otherwise.
However all this "social networking / email killer" stuff is just distraction. The Wave protocol is about content centric collaboration - its a collaborative document creation / editing paradigm. So before pontificating on how it will never replace Twitter, think about how it might become competition for SharePoint 2010 and the online versions of the Office apps.
Think: Private cloud + Google Wave + Google Voice + Google Apps + = enterprise content collaboration platform. Is somebody going to write a CMIS API for this stack, I think they should !
Stephen Arnold has been saying for some time that people should be paying attentions to Googles moves in new database technology, so add that to all of the above.
Personally I would like to see appliances / software / VM's to more of this stuff inside the corporate firewall (you can build your own Wave servers, and buy Google Search Appliances).
I look at this from an enterprise viewpoint, and there are plenty of others who are doing so:
The only valid criticism I have heard of Wave so far is that is 're-inventing the wheel' a bit where it comes to the XML format it uses.
I am not on the invite list for the beta, and I doubt anyone at Google will read this, so I am not angling for one, in fact I think its going to be a couple of years before Google really builds up its 'wave front' - but thisl an open standards based protocol - stop thinking of Wave just as its seen in the flashy demo video or the sandbox developer account you managed to scrounge that you can't do much with.
Bottom line - stop thinking 'new fangled email crossed with IM and social networking' and think powerful content centric collaboration and document editing.
For all those who keep churning out the fact that Google Wave has no compelling improvement of email and IM, those who constantly suggest its a social networking platform aimed at taking on Twitter and FaceBook, or stating that its gonna flop because its unfinished crud;
Jeez, stop and breath and takd a minute to think about it !
Wave is a protocol (XMPP based), not just Google's current server platform and client app. There are already independent open source implementations of servers for the protocol. Yes the Google front end is unfinished - for all those who moan about how distracting it is to seen what the other person is typing; well even in the original Google I/O conference video they point out that that there will be a private 'draft' mode that will prevent this, so you can write in peace..........
Yes the released (and hyped it) early, because they want 'community' input - so no, its not finished or polished, but come on its just gone from private Alpha to invitation only Beta, its a long way from finished product(s) and no one is saying otherwise.
However all this "social networking / email killer" stuff is just distraction. The Wave protocol is about content centric collaboration - its a collaborative document creation / editing paradigm. So before pontificating on how it will never replace Twitter, think about how it might become competition for SharePoint 2010 and the online versions of the Office apps.
Think: Private cloud + Google Wave + Google Voice + Google Apps +
Stephen Arnold has been saying for some time that people should be paying attentions to Googles moves in new database technology, so add that to all of the above.
Personally I would like to see appliances / software / VM's to more of this stuff inside the corporate firewall (you can build your own Wave servers, and buy Google Search Appliances).
I look at this from an enterprise viewpoint, and there are plenty of others who are doing so:
- Ribbit tele-conferencing gadget
- 6rounds vidoe conferencing gadget
- SAP Gravity - collaborative business process modelling
- SalesForce.com
The only valid criticism I have heard of Wave so far is that is 're-inventing the wheel' a bit where it comes to the XML format it uses.
I am not on the invite list for the beta, and I doubt anyone at Google will read this, so I am not angling for one, in fact I think its going to be a couple of years before Google really builds up its 'wave front' - but thisl an open standards based protocol - stop thinking of Wave just as its seen in the flashy demo video or the sandbox developer account you managed to scrounge that you can't do much with.
Bottom line - stop thinking 'new fangled email crossed with IM and social networking' and think powerful content centric collaboration and document editing.
Tuesday, 18 November 2008
OASIS CMIS press release
Here is yesterdays OASIS press release on the formation of the CMIS technical committee:
http://www.marketwatch.com/news/story/OASIS-Members-Form-Committee-Advance/story.aspx?guid={A42B48F4-3BCB-4225-B91F-54299FB27096}
If you scroll down there are lots of interesting little endorsement snippets from various interested vendors.
http://www.marketwatch.com/news/story/OASIS-Members-Form-Committee-Advance/story.aspx?guid={A42B48F4-3BCB-4225-B91F-54299FB27096}
If you scroll down there are lots of interesting little endorsement snippets from various interested vendors.
Wednesday, 17 September 2008
Vendor support for different elements of CMIS - updated
Updated below - response to a question asked in the Webinar
So, I am currently listening to the AIIM webinar on Collaboration, and the intro from IBM, the sessions sponsors, noted something I had not picked up on elsewhere - different vendors have promised to support different elements of the CMIS standard, as in how they will implement the standards dual approaches of Web Services, or RESTful programming:
Vendors supporting both Web Services (SOAP etc) and REST:
As I have already said, it will be interesting to see which vendors back up the rhetoric with action.
Update: I asked the IBM representative (Cengiz Satir Sr. Offering Manager IBM Enterprise Content Management) if they would push CMIS forward to get the WCM, RM and DAM issues covered. He responded that CMIS does not / is not meant to cover these complex use cases as its meant for interoperability of 'Basic Content Services'. Now, he should know what he is talking about because as he mentioned IBM has 4 members on the CMIS committee, however its quite a surprising answer to me.
Jeetu Patel of Doculabs chipped in with a comment on how broadbased interoperabilty standards initiatives can only ever get more important.
So, I am currently listening to the AIIM webinar on Collaboration, and the intro from IBM, the sessions sponsors, noted something I had not picked up on elsewhere - different vendors have promised to support different elements of the CMIS standard, as in how they will implement the standards dual approaches of Web Services, or RESTful programming:
Vendors supporting both Web Services (SOAP etc) and REST:
- IBM
- Alfresco
- SAP
- EMC
- OpenText
- Microsoft
- BEA Oracle
As I have already said, it will be interesting to see which vendors back up the rhetoric with action.
Update: I asked the IBM representative (Cengiz Satir Sr. Offering Manager IBM Enterprise Content Management) if they would push CMIS forward to get the WCM, RM and DAM issues covered. He responded that CMIS does not / is not meant to cover these complex use cases as its meant for interoperability of 'Basic Content Services'. Now, he should know what he is talking about because as he mentioned IBM has 4 members on the CMIS committee, however its quite a surprising answer to me.
Jeetu Patel of Doculabs chipped in with a comment on how broadbased interoperabilty standards initiatives can only ever get more important.
Thursday, 11 September 2008
CMIS - will it be 'real' ?
One of the links in my previous post was to the CMS Watch take on the release of CMIS by their analyst Kas Thomas. His final paragraph is:
"Here's hoping IBM, EMC, Microsoft, and the others will follow Alfresco's early lead and actually implement CMIS rather than (as they did with JCR) just issue press releases about it."
Well a big 'amen' to that one !
When I was at the Open University we were using EMC Documentum as our heavy duty back end for the 'eProduction System' in other words digital asset management, collaborative team working and workflow for producing all the universities learning materials, be they destined for presentation in print, on the web, as an ebook or as multimedia.
One of the 'front ends' for presentation is the Moodle open source Virtual Learning Environment (VLE). However getting Documentum to talk to Moodle required some development work ("no, you don't say.....") . The developers decided to lever the architecture of JSR170, the Java Content Repository standard, which as Kas notes above, might have generated some press releases from EMC, but never actually made it as far as Documentum Content Server becoming JCR compliant. Moodle meanwhile is PHP, so there was a PHP to Documentum connector built, using JCR as a 'framework' (basically replicating calls etc). It was 'sort of' successful (?).
Now imagine if both Documentum Content Server and Moodle had been CMIS compliant or had CMIS comliant 'modules' - it would have been sooooo easy.
So this is my 'wide eyed enthusiam' posting, I truly hope all the vendors put their money where their standard is, so to speak, and actually follow Alfresco's lead by getting this into their product sets ASAP (or at least help OASIS to get a version 1.0 ratified as soon as it can).
"Here's hoping IBM, EMC, Microsoft, and the others will follow Alfresco's early lead and actually implement CMIS rather than (as they did with JCR) just issue press releases about it."
Well a big 'amen' to that one !
When I was at the Open University we were using EMC Documentum as our heavy duty back end for the 'eProduction System' in other words digital asset management, collaborative team working and workflow for producing all the universities learning materials, be they destined for presentation in print, on the web, as an ebook or as multimedia.
One of the 'front ends' for presentation is the Moodle open source Virtual Learning Environment (VLE). However getting Documentum to talk to Moodle required some development work ("no, you don't say.....") . The developers decided to lever the architecture of JSR170, the Java Content Repository standard, which as Kas notes above, might have generated some press releases from EMC, but never actually made it as far as Documentum Content Server becoming JCR compliant. Moodle meanwhile is PHP, so there was a PHP to Documentum connector built, using JCR as a 'framework' (basically replicating calls etc). It was 'sort of' successful (?).
Now imagine if both Documentum Content Server and Moodle had been CMIS compliant or had CMIS comliant 'modules' - it would have been sooooo easy.
So this is my 'wide eyed enthusiam' posting, I truly hope all the vendors put their money where their standard is, so to speak, and actually follow Alfresco's lead by getting this into their product sets ASAP (or at least help OASIS to get a version 1.0 ratified as soon as it can).
World Peace declared in ECM industry... CMIS is here ! Updated 12th Sept
Updated - I have added additional links to blog posts from Craig Randall and the Observing Content Management blog, that later notes something I had intially missed:
"The following use cases are out of scope for the initial set of deliverables:
________________________________________________________
OK, not quite 'world peace' (wishful thinking eh?) but we must welcome the birth of a new 'standard' the Content Management Interoperability Standard or CMIS to us..... :-)
What does it mean - well I am not sure, I kept of the 'puter at home last night and only picked this up this morning via a 'press release' email from EMC, and I am still digesting it all, but of course plenty of sharper people than I have hit the pressess already, so please check out the links below:
Enter CMIS a proposed ECM-SOA standard - Pie says he is 'almost too excited for words' !
CMIS - be careful what you ask for - MMm' the Big Men On Content seem less excited than Pie...
Announcing the CMIS specification - Microsoft Sharepoint Team blog
Announcing the CMIS specification - MS ECM Team blog
Alfresco releases first CMIS implementation - John Newton of Alfresco
CMIS the new lingua franca of EMC - CMS Watch
ECM standards war: bye bye JSR170 hello CMIS - Bex Huff
CMIS - Craid Randall
CMIS - Observing Content Management
The actual specification (version 0.5 full) is available from EMC developer network here:
http://community.emc.com/docs/DOC-1605
The official press releases are here:
SAP have been mentioned too, but I can't see a press release from them anywhere.
Although CMIS appears to have been an evolutionary off shoot of the stalled AIIM 'iECM' initiative, it is being handed to the OASIS standards body for ratification as a standard. (Hopefully the other vendors will exercise constraint on MS in this one, unlike the ISO fiasco with document standards).
So, enjoy reading that lot, plenty of opinion pieces to follow I expect !
"The following use cases are out of scope for the initial set of deliverables:
- Records Management and Compliance
- Digital Asset Management
- Web Content Management
- Subscription and Notification Services”
________________________________________________________
OK, not quite 'world peace' (wishful thinking eh?) but we must welcome the birth of a new 'standard' the Content Management Interoperability Standard or CMIS to us..... :-)
What does it mean - well I am not sure, I kept of the 'puter at home last night and only picked this up this morning via a 'press release' email from EMC, and I am still digesting it all, but of course plenty of sharper people than I have hit the pressess already, so please check out the links below:
Enter CMIS a proposed ECM-SOA standard - Pie says he is 'almost too excited for words' !
CMIS - be careful what you ask for - MMm' the Big Men On Content seem less excited than Pie...
Dogs and Cats: EMC, Microsoft, IBM, & Alfresco release CMIS - ECMArchitect
CMIS - its not JAS - Chuck Hollis of EMCAnnouncing the CMIS specification - Microsoft Sharepoint Team blog
Announcing the CMIS specification - MS ECM Team blog
Alfresco releases first CMIS implementation - John Newton of Alfresco
CMIS the new lingua franca of EMC - CMS Watch
ECM standards war: bye bye JSR170 hello CMIS - Bex Huff
CMIS - Craid Randall
CMIS - Observing Content Management
The actual specification (version 0.5 full) is available from EMC developer network here:
http://community.emc.com/docs/DOC-1605
The official press releases are here:
SAP have been mentioned too, but I can't see a press release from them anywhere.
Although CMIS appears to have been an evolutionary off shoot of the stalled AIIM 'iECM' initiative, it is being handed to the OASIS standards body for ratification as a standard. (Hopefully the other vendors will exercise constraint on MS in this one, unlike the ISO fiasco with document standards).
So, enjoy reading that lot, plenty of opinion pieces to follow I expect !
Subscribe to:
Posts (Atom)