Commentary

Andrew Conry Murray
 

Proposed Standard Would Open Proprietary Content Management Systems

Microsoft, IBM, EMC, and others aim to make it easier for users and applications to pull content from competing repositories.

Microsoft, IBM, EMC, and others aim to make it easier for users and applications to pull content from competing repositories.Today a coalition of major vendors is submitting a proposed standard, Content Management Interoperability Services (CMIS), to Oasis. The goal of the specification is to make it easier for users and applications to pull content from multiple proprietary content management systems.

At present, much of the information generated in the workplace is locked into silos. Enterprises that want to integrate disparate content repositories, such as document management software and SharePoint, often have to build or buy one-off connections. Or they have to migrate content from one repository to another, which is time-consuming and expensive.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

CMIS will use the Web-based protocols SOAP and REST to serve as a common access mechanism. The specification also will create a common domain model to describe what the content looks like, its metadata, and what can be done with it, such as checking it in or out.

The spec's backers believe CMIS will enable users to get access to the right content quickly, and to use that content in new ways, such as in mashups and wikis. Software vendors also will be able to write applications that can run across any repositories that support CMIS.

They also hope the specification will help drive new sales of content management platforms by making it easier to extract value from them.

Work on CMIS was undertaken in 2006 by IBM, EMC, and Microsoft. They were later joined by Alfresco, Open Text, SAP, and Oracle. A final standard is expected to emerge from Oasis in late 2009.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links