XML in the Content Lifecycle

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.

ZapThink: Big changes ahead in XML data storage

The beginning of 2003 marks ”the end of the Native XML Data [NXD] store market as we know it,” proclaimed Ronald Schmelzer, senior analyst at ZapThink, LLC, a Waltham, Mass.-based analyst firm specializing in XML.

This does not mean that NXD vendors will disappear, although larger software companies may acquire some of the smaller ones; but the way XML data storage products are marketed and deployed will change, he said.

Read more at: Application Development Trends

ZapNote: AGiLiENCE

Download File

XML Data Store Multi-Client Study

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

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.

Read more at: Internetnews.com

XML in the Content Lifecycle

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.