Tracktion Software Collective Content V1.0.5-R2R 'LINK'
DOWNLOAD ---> https://fancli.com/2sXJIi
The ultimate goal of CMIS is to dramatically reduce the IT burden around multivendor, multirepository content management environments. Currently, customers must spend valuable time and money to create and maintain custom integration code and one-off integrations to get different ECM systems within their organizations to "talk" to one another. The specification will also benefit independent software vendors (ISVs) by enabling them to create specialized applications that are capable of running over a variety of content management systems.
According to the press release issued today, "The ultimate goal of CMIS is to dramatically reduce the IT burden around multi-vendor, multi-repository content management environments. Currently, customers must spend valuable time and money to create and maintain custom integration code and one-off integrations to get different ECM systems within their organizations to 'talk' to one another. The specification will also benefit independent software vendors (ISVs) by enabling them to create specialized applications that are capable of running over a variety of content management systems."
From the Microsoft Content Management Interoperability Services (CMIS) document:CMIS is designed around a services architecture based on SOAP, REST and Atom to simplify application development. The process of developing content centric applications that are repository independent or that are capable of working with the content from various repositories becomes a viable option as a result of the CMIS specification. Examples of the types of applications we believe customers and independent software vendors will create include content mash-ups, document and records management applications, electronic discovery, multi channel publishing solutions and end-user collaborative workspaces and portals... CMIS demonstrates Microsoft's enhanced support for industry standards and will allow developers and independent software vendors to better interact with existing ECM systems and invent new solutions for customers...
[In part reflecting conversations within the OASIS CMIS Technical Committee about CMIS Candidate Discussion/Development Topics for Version 1.1/2.0 and related conversations]: "a list of business cases that we need support for in CMIS. Specific features may not be all listed, but I will be listing some to give an idea. The goal here is to stimulate everyone's collective mind and think about what we need in the next version. [Excerpted] as (1) Semantic Support: missing is the ability to query off of relationships; this will allow for more advanced relationship management (2) Records Management: now you can apply policies to a piece of content, but that policy could be a retention policy; (3) Support for Defined Data Models: satisfy the challenges of managing the same metadata model against different repository implementations of that model; (4) Create Content Types: create a new object type based upon a document or folder; (5) New Bindings: several ideas in the last year... WebDAV and JSON... (6) other examples: hierarchical metadata; tagging (set by combination of user and asset; Authority assigned to the tags; support for (queryable) aspects; ability to Query relationships in the 'Where' clause; with tagging, ability to query on tag strength... I'm sure that there are more, but I think those are the important ones. It helps the web-heads, the ECM types, and the solution providers..."
OASIS announced the approval of Content Management Interoperability Services (CMIS) version 1.0, a new open standard that enables information to be shared across Enterprise Content Management (ECM) repositories from different vendors. Advanced via a collaboration of major ECM solution providers worldwide, CMIS is now an official OASIS Standard, a status that signifies the highest level of ratification. Using Web services and Web 2.0 interfaces, CMIS dramatically reduces the IT burden around multi-vendor, multi-repository content management environments. Companies no longer need to maintain custom code and one-off integrations in order to share information across their various ECM systems. CMIS also enables independent software vendors (ISVs) to create specialized applications that are capable of running over a variety of content management systems. David Choy of EMC, chair of the OASIS CMIS Technical Committee: 'CMIS makes it possible for business units to deploy systems independently and focus on application needs rather than on infrastructure considerations. With CMIS, integrating content between two or more repositories is faster, simpler and more cost-effective. This is how it should be.' [...] Mary Laplante, vice president and senior analyst for the Gilbane Group: 'CMIS has the potential to be a game-changing standard, not only through its promise to facilitate affordable content management, but also as an enabler of whole new classes of high-value, information-rich applications that have not been feasible to date. At the end of the day, companies simply need better approaches to integrating systems. Business agility increasingly separates the winners from the losers, and agility is perhaps the biggest single benefit that CMIS offers'. CMIS is offered for implementation on a royalty-free basis..."
"I am an incurable optimist. I believe in the power of technology and that with software anything is possible. So it is understandable that on a panel on CMIS at AIIM the other week, Microsoft program manager Ethan Gur-esh described my vision of what might happen with CMIS as grandiose. If you are not familiar with CMIS, it is the Content Management Interoperability Services, which has just been ratified by the member companies of OASIS. It is in effect, an SQL for Content Management. In other words, a set of protocols, interfaces and query language definitions that allow a program to be written to any content management system. On the panel, I described how I believe CMIS can transform the ECM industry, allow for significant growth and spawn whole new companies and markets... The panel moderator, Mike Mahon, is from Zia Consulting who has created mobile applications for the iPhone and Android using CMIS. In short, all the major vendors are all behind CMIS and it will soon be possible for developers to build applications that can run on any repository. Also, the level of functionality in CMIS is quite rich even if it doesn't cover all the functionality of an ECM system. It's enough to build some seriously interesting applications. Are there any precedents for this level of standardization, interoperability and functionality? Many standards, such as various workflow, business process, web services and XML standards, have not been able to achieve these levels of compatibility... New solutions that integrate collaboration and social networking capabilities will also be content rich and need the functionality provided by CMIS. If you were to design an API for content applications in the Cloud, it would probably look a lot like the RESTful protocol of CMIS, so expect Cloud applications and content-oriented SaaS offerings to take advantage of CMIS. This could be the creation of companies the size of those client-server companies and the web-based companies that followed those. The standardization of platforms heralds the opening of markets that rely on those platforms. And platforms, once they are standardized tend to stick around for a long time and grow..."
"Day Software Holding AG, an enterprise software provider of Web 2.0 content management and content infrastructure software, has announced the release of CRX 2.1, Day's open, standards-based Enterprise Content Management (ECM) platform. Day's new CRX 2.1 release promotes rapid development, deployment and scalable hosting of composite content applications in either a public or private Cloud... CRX 2.1 adds support for both the JSR-283 and CMIS standards. JSR-283 support follows the December ratification of this successor standard to JSR-170, capping a multi-year effort led by CTO David Nuescheler in the Java Community Process (JCP) and Apache Jackrabbit project. Along with support for JCR 2.0, CRX 2.1 also adds support for the upcoming CMIS standard, which is scheduled for final voting and ratification 30-April-2010. CRX's support for CMIS follows nearly one year after Day's announcement of the Apache Chemistry project to provide a common, vendor-neutral reference implementation of the CMIS standard to promote development and adoption of the new standard. With major vendors like SAP and OpenText part of the Apache Chemistry project, CRX 2.1 provides standardized support for CMIS in addition to support for JCR. CRX 2.1 features also include: (1) Virtualization and IT Consolidation: Day extends CRX's virtual repository to extend a JSR-283 and CMIS interface to leading enterprise content management repositories, including Microsoft SharePoint. (2) Rapid Composite Content Application Development: CRX 2.1 introduces new tools for developer productivity. For web developers, CRX 2.1 introduces a new browser-based development environment, CRXDE Lite, that offers code-editing, packaging and deployment support for composite content applications, along with integration with leading source code management (SCM) systems... (3) Rapid Composite Content Application Development; (4) On-Demand Scalability with the Cloud: CRX 2.1 adds new support for elastic storage capability with native support for Amazon Web Services (AWS) S3; (5) Cloud-hosted PackageShare Service: In addition to its native Cloud support, with CRX 2.1 Day also introduces its first Cloud-hosted service, PackageShare. PackageShare is Day's online service for enabling CRX developers worldwide to package and share composite content applications, providing a global catalog of pre-built solutions and components..."
"A cadre of enterprise content management (ECM) software vendors is close to finalizing a standard for sharing data across their systems. Next week, OASIS is expected to ratify the Content Management Interoperability Services (CMIS), a set of bindings that would allow different content management systems to offer access to their content in a single, uniform fashion. CMIS is the effort of a number of ECM heavyweights, including IBM, Microsoft, EMC, and Alfresco... It is a standard much needed by both vendors and their enterprise customers, observers say... Ian Howells, the chief marketing officer at Alfresco: "Today, the hooks for fetching and changing data in systems such as EMC Documentum and Microsoft SharePoint are different for each system. Each application programming interface is completely unique... As a result, developers building applications that pull data from ECMs face a lot of work, especially if their creations need to access multiple content management systems. For each system, the content is in a proprietary format, the metadata is in a proprietary form, and the API is proprietary. It's a nightmare... CMIS could simplify matters insofar as it offers a single set of bindings that a developer could write to, and not worry about the underlying CMS. The bindings are based on either the REST (Representational State Transfer) protocol or the Web services-based SOAP (Simple Object Access Protocol)... What remains to be seen is to what extent the ECM vendors support the CMIS standard in their products... Thus far the vendors that have participated in CMIS seem enthusiastic. They have held a number of plug-fests to demonstrate that front-end querying software can draw data from a variety of back-end repositories..." 2b1af7f3a8