Comments on: Three Fundamental CMIS Use Cases

By: Revisting the CMIS Use Cases « Word of Pie

Revisting the CMIS Use Cases « Word of Pie — Sun, 14 Mar 2010 15:35:23 +0000

[...] 14 March 2010 tags: CMIS, ECM, High Volume Server by Pie A while back, I discussed the Three Fundamental Use Cases for CMIS. Since then, there have been some additional thoughts on this topic. Since CMIS has [...]

By: The AIIM CMIS Demo: Looking Back at 2009 and Ahead to 2010 « Word of Pie

The AIIM CMIS Demo: Looking Back at 2009 and Ahead to 2010 « Word of Pie — Tue, 26 Jan 2010 14:01:54 +0000

[...] ups and downs of designing and building the demo. It classifies the demonstration using the three fundamental CMIS use cases that I crafted this past summer and talks about what the upcoming demonstration is going to [...]

By: Sascha Ohler

Sascha Ohler — Tue, 18 Aug 2009 14:50:31 +0000

Thanks. Very helpful.

By: Pie

Pie — Tue, 18 Aug 2009 13:20:21 +0000

Thanks. I’ll add your thoughts. I think some are slight variations of what has already been written, but others are new use cases. Thanks for your help.

-Pie

By: Stephane Croisier

Stephane Croisier — Tue, 18 Aug 2009 08:01:06 +0000

Good morning,

After some nightly thought, I think we perhaps could add:

I2R: Indexes-to-Repositories: this is where a content crawler or robots talk directly to the repository to ingest content
- Unified Search: Federated Search could be sometime a solution, but when dealing when large amounts of content a unified search could be better (cf: Automony comment on that). This could also be a way for crawlers to digest private or unpublished content. Semantic searches would also be able to access to metadata and associations (tripples) on systems which do not support RDF(a) or similar.

R2R: Migration
You mention it on the Federated Repositories Space. But it may also be a convenient way to rapidly migrate content items from one silo to the other. Companies are acquired or sometimes wants to change their systems (or unify their constellation of CM products under one single umbrella) and, even if they could manage some kind of federation of repositories, they might look at more easy and convenient ways to migrate their content from one repo to the other.

Federated Repo:
- CMIS bridges to access legacy or proprietary applications. It would be interesting to see if there is the development of CMIS bridges on top of applications or API which are (or do not want to be) compliant with CMIS. For example it would be nice to have a TwitterAPI-to-CMIS. But the same is true for some legacy applications which could not be modified anymore.
- Semantic ETL Aggregation: Dealing with several federated repositories immediately raise the concern of dealing with some kind of “unified common ontology”. There are little or no chance that all repositories are using the same sets of taxonomies to describe their content. There will be a multiplication of tags, categories, metadata,…. in a federated universe (notion of LinkedData in the semantic universe). A semantic CMIS could help find duplicates, generate dynamic cross-repositories associations, etc…

I will add others (if any) when I will get more inspiration
Cheers,
Stéphane

By: Kevin Cochrane

Kevin Cochrane — Mon, 17 Aug 2009 23:19:20 +0000

Completely agree with this use cases, as squares with what
we see people looking to do: build a front-end
web app tied to a specific biz purpose with a tailored
user experience that needs to source data from
different back end repos. This needs to be balanced
with IT budget constraints, and here is where
standards play a key role in lowering dev costs
to enable IT and biz agility and alignment on
key initiatives.

By: Pie

Pie — Mon, 17 Aug 2009 19:57:48 +0000

I wrote a post on this topic a while back: http://wordofpie.com/2009/04/28/content-enabled-applications-in-the-age-of-cmis/ I’m also embedding the link in the post now.

-Pie

By: Sascha Ohler

Sascha Ohler — Mon, 17 Aug 2009 19:31:37 +0000

Would you mind expanding on this use case? I think this is a very important one.
Thank you.

“Content Enabled Vertical Applications (CEVAs). Let the domain experts build a solution for the industry and let them plug it into any content system to manage the content. This frees the CEVA vendor from having to worry about the content or maintaining so many interfaces. That means more R&D money for real features.”