XML Developers Get Slew of New Tools

Sarvega Inc., of Chicago, announced the availability of its Sarvega XRE 200, a blade system for XML Web services. Sarvega sells a suite of XML processing appliances that run the company’s XML EventStream Operating System (XESOS), which handles Web services processing and XML and Web services security. The XRE 200 is the latest in that series and supports a blade environment.

“By integrating the benefits of an XML appliance into a blade, Sarvega is giving enterprises a significant new option for deploying Web services infrastructures,” said Ronald Schmelzer, an analyst with ZapThink LLC, in Cambridge, Mass.

Read more at: eWeek

IBM Experiments with DB2 Search

Analyst Jason Bloomberg of XML-centric research organization ZapThink issues a reminder about the complexities of tagging. “What do you [do] about tons of existing content? It’s expensive to go back through libraries and provide metadata. And how do you get people to tag content as they produce it?” The latter problem is an issue of classic change management, but the technical problem of tagging old content is handled, to some extent, by a number of companies (e.g. CambridgeDocs) that claim to automate the process. That said, Bloomberg points out that, “To do metatagging well, you need human input.”

Read more at: Line56

ZapNote: CambridgeDocs

Download File

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.

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.