Setting up an XML Backend

KMMag.com has an Article on the pros of setting up data centers using XML. I would imagine XML is going to be used more in OPACs, given the flexibility and robusness of the language. Has anyone started using XML in a library setting yet?

\"For example, XML-based systems can replace complex, expensive systems for electronic data interchange (EDI). Others can form a bridge for moving data between legacy applications and online systems, shielding users and developers from working with the actual code.\"

More from kmmag.com\"\"XML has been a content-oriented technology, but the real advances will come around XML messaging,\" says Nathaniel Palmer, an analyst with the Delphi Group in Boston. Content-oriented XML is used primarily for describing the different kinds of content in a document, such as author, date and text. In contrast, message-oriented XML describes data.

In spite of the multiplicity of applications and platforms within companies, line-of-business managers and users demand that these systems work together. Messaging-oriented middleware (MOM), which communicates between applications and operating systems, addresses this requirement, and XML can help to automate communications between them. MOM can translate data from various applications into XML, which in turn makes it easier to translate into other application formats. This requires much less work than doing one-to-one translations between every pair of application format types in an enterprise.

Syndicate content