ZapThink » NeoCore

XML in the Content Lifecycle

Ronald Schmelzer — Mon, 27 Jan 2003 00:01:00 +0000

Key Findings:

The market for XML content lifecycle solutions is expected to grow from $1.8 Billion in 2003 to over $11.6 Billion by 2008.
Producers of content in the enterprise spend over 60% of their time locating, formatting, and structuring content and just 40% of their time actually creating it.
By 2008, about 60% of all content lifecycle products will be XML-enabled.
the primary challenge in the enterprise for producers of content — information that is intended for human consumption — is content reuse: the ability to integrate content from disparate sources.
Efforts to improve content processes have been slowed by efforts to extract and manipulate content from multiple, disparate data sources.

Table of Contents:

I. Report Scope
II. The Growth and Management of Content in the Enterprise
- 2.1. Sources and Growth of Content in the Enterprise
- 2.2. The Content Management Challenge
- 2.3. The Evolution of the Content Management System (CMS)
- 2.4. Markup Languages and Content
III. The Content Lifecycle
- 3.1. Content Creation
- 3.2. The Content Repository
- 3.3. Content Management
- 3.4. Content Publishing and Distribution
- 3.5. Content Syndication
- 3.6. Content Protection
IV. XML-Enabling the Content Lifecycle
- 4.1. Is XML Necessary for Improving the Content Lifecycle?
- 4.2. Content Creation: XML-based Authoring and Conversion
- 4.3. Content Repository: Native XML Storage and Search
- 4.4. Content Management: XML-based Content Componentization
- 4.5. Content Publishing and Distribution
- 4.6. Content Syndication: XML Standards and Products
- 4.7. Content Protection: XML-powered DRM
V. The ROI of XML-enabling the Content Lifecycle
- 5.1. Cost Savings: Content Reuse
- 5.2. Cost Savings: Efficient Content Search
- 5.3. Revenue Enhancing: Enabling Content Syndication
- 5.4. Cost Savings: Integrating Islands of Content
VI. Challenges in Implementing an XML-enabled Content Lifecycle
- 6.1. Metadata-encoding Content is Difficult
- 6.2. XML May Not be Suitable as a Long-term Archival Format
VII. The Service-Oriented Vision of Content
- 7.1. Shifting away from a Publish-oriented Mentality
- 7.2. Content as Services: Service-Oriented Content
- 7.3. Content Lifecycle Functionality as Services
VIII. Market for XML-enabled Content Lifecycle Products
- 8.1. Market Sizing and Growth
- 8.2. Vendor Market Segmentation and Positioning
- 8.3. The Future of Content Management Systems
IX. Conclusions
- 9.1. Key Notes
- 9.2. Decision Points
- 9.3. Figures
- 9.4. Tables
X. Profiled Vendors
- 10.1. Content Creation
- 10.2. Content Repository
- 10.3. Content Management
- 10.4. Content Publishing / Distribution
- 10.5. Content Syndication
- 10.6. Content Protection
Related Research
Trademark Notice and Statement of Opinion
About ZapThink, LLC

Download File

XML Data Store Multi-Client Study

Ronald Schmelzer — Fri, 13 Dec 2002 00:12:00 +0000

While much has been written about XML data storage, none of the research to date has focused on the key questions:

What are the different needs for XML data storage?
ow do those needs translate into different storage requirements?
How are various vendor solutions best suited to meet these different needs?

In attempting to understand the answers to the above questions, ZapThink realized that there was no single answer for any of these key questions. In fact, it seems that the various requirements for XML data storage pull end-user customers in different directions when they are deciding how to implement XML storage requirements. As such, this study seeks to do what no other study before it has done: show that XML data storage is not a distinct market segment, but instead a functionality requirement for applications that require XML storage in order to achieve their overall system objectives.

ZapThink: Native XML Data Storage Will Evolve

admin — Fri, 13 Dec 2002 00:12:00 +0000

nalysts at XML and Web services consultancy ZapThink Friday made the prediction that the native XML database (NXD) niche no longer exists as a separate market.

ZapThink Senior Analyst Ron Schmelzer told internetnews.com XML-enabled relational database (RDBMS), content management, and integration vendors are best suited to offer general-purpose XML data store solutions, while XML database pure-plays are offering more focused XML data storage solutions. Schmelzer believes XML database features will eventually become incorporated in an increasing number of major software packages, including those offered by Microsoft, Oracle and IBM.

NorthAmerican Logistics Cuts XML Translation Costs with Software AG’s Tamino

admin — Mon, 23 Sep 2002 00:09:00 +0000

Going forward, expect such native XML databases to become more common as the use of XML to represent all kinds of data spreads, says Ron Schmelzer, an analyst at Zapthink LLC, an XML consultancy in Waltham, Mass. XML databases are better than traditional ones at preserving XML hierarchies, says Schmelzer.

For example, a document can be stored as a document instead of being shoehorned into rows and columns, Schmelzer says.

Tamino was the first to market and remains on top. But a number of other vendors, including IxiaSoft Inc. and Neocore Inc., offer similar products.

In the future, expect to see vendors of traditional relational database management products, such as Oracle Corp., ship native XML databases as well, he says.

Overcoming XML’s Hidden Processing Costs

Ronald Schmelzer — Sun, 01 Sep 2002 00:09:00 +0000

XML is pervasive. In a matter of years, it will fuel every application, device, and document found in enterprise networks. However, as XML proliferates, it will stress existing systems and enterprise budgets to their breaking points. This is because existing n-tier software architectures and legacy infrastructures were not designed to process this verbose new data type efficiently. What enterprises need is a new way to process XML in the network, rather than in software at the database, application server, or presentation tiers. Yet today’s existing network infrastructure is limited to switching lower layer protocols and is unable to detect XML – much less parse and process it.

An emerging class of hardware-based XML-aware network devices addresses the performance, security and management issues that come with XML’s use in enterprise applications. These purpose-built network devices enable enterprises to process high volumes of XML in a way that offers high performance, optimal security, lowest total cost of ownership, and greatest centralization of XML processing capabilities.Download File

XML in the Content Lifecycle

Ronald Schmelzer — Fri, 23 Aug 2002 00:08:00 +0000

The process of creating content — information meant for human consumption — is almost always extremely effort-intensive. People must spend time organizing information prior to creation, constructing the content, and laying out the information so that it is easily read. With so much time, cost, and effort invested in content, it makes sense to reduce costs by reusing content as much as possible. Furthermore, content-oriented processes involve a complex set of interactions that progress in a “Content Lifecycle” consisting of five major stages: content creation, management, publishing, syndication, and protection. Each of these phases requires different technologies, processes, and resources.

By rearchitecting content representation technologies to treat content as another asset in the corporate IT infrastructure, businesses can realize the benefits long promised to us by reusable and agile content. But first, we need to move from ad-hoc content creation to content componentization, and then to content services. XML and Web Services are the key to this transition that can help organizations maximize the value of their content.Download File

NeoCore XMS 2.6 Delivers Performance for Mainstream Applications

admin — Fri, 23 Aug 2002 00:08:00 +0000

Ron Schmelzer, senior analyst with ZapThink, LLC, an XML and Web services-focused analyst group, said, “NeoCore XMS 2.6 allows users a potent way of storing, managing, and navigating through the rich hierarchy of XML in ways not possible with other types of solutions.”

NeoCore XMS 2.6 Delivers Performance for Mainstream Applications

admin — Mon, 19 Aug 2002 00:08:00 +0000

Ron Schmelzer, senior analyst with ZapThink, LLC, an XML and Web Services-focused analyst group, said that NeoCore’s release of XMS 2.6 illustrates the forward-thinking advancements the company is capable of producing for XML information management. “NeoCore XMS 2.6 allows users a potent way of storing, managing, and navigating through the rich hierarchy of XML in ways not possible with other types of solutions,” Schmelzer says. “These enhancements allow companies to save time and money, while working smarter and faster in order to thrive in today’s challenging economic environment.”

Structured vs. Unstructured Data

admin — Mon, 29 Jul 2002 00:07:00 +0000

As the challenge of data integration and information integration climb IT professionals’ agendas, it is important to know what kind of information is out there, anyway. One commonly bandied about statistic holds that 70 percent of all corporate information is contained in legacy systems. Our friends at Neocore, a vendor of an XML-base information management system based on a self-constructing XML database solution (www.neocore.com), passed on these figures to us from Zapthink Research (www.zapthink.com), which focuses on the XML marketplace. According to ZapThink, 80 percent of enterprise content is unstructured; 9 percent is contained in relational databases and 11 percent is in legacy systems. Who is right? Who knows? Enterprises themselves usually don’t. That is why most successful data integration projects start with companies taking an inventory of their data assets. For more insight, read the September issue of Database Trends and Applications magazine. Subscribe at www.dbta.com/subscribe.

Read more at: Database Trends and Applications

ZapNote: B-Bop

Ronald Schmelzer — Thu, 18 Apr 2002 00:04:00 +0000

The only true solutions for enterprise-wide XML data storage and retrieval are XML-enabled RDBMS and Native XML Data Store (NXD) approaches. The challenge with XML-enabled RDBMS is that they are not very well suited to highly extensible and flexible documents, while the challenge with NXDs is that they are unproven technologies with very small user bases. However, there is another option that is a sort of "middle ground": the use of an interpretive middle layer over standard RDBMS systems that offers schema-independent, "native" XML data storage. In this vein, B-Bop offers their Xfinity Server as a way of providing the features of Native XML storage while utilizing existing relational storage architectures. Download File