Fargo Systems have already written several XML data applications. As specialists in systems integration projects, we pride ourselves on our knowledge of interfaces, whether the solution is simple flat text files across two PC's or global communications using EDI across private networks. XML, as a new markup language standard, has benefits that are particularly well-adapted to the haulage and global shipping industries. The concept and the technologies to manipulate it easily are already well developed, (SQLserver2000, XSL, (eXtensible Style Language), DOM, (Document Object Model), SAX, (Simple API for XML), SOAP). These technologies may one day replace ADO, and some people are even talking about storing data in an XML format (back to flatfiles!) as a creative alternative to RDBMS. We don't believe this; We think we'll soon see XML "databases" but they will be quirky, low-key and "hobbyist". It will take something extra to remove RDBMS, (Relational Database Management Systems), from the top-spot for storing data. Where XML comes into its own, is in the ability to completely separate data from presentation, (in the web context), and in its flexibility with regards data transfer, (and indeed storage). Consider this: you have a database that you have to "release in the wild" that is focused on receiving data from customers and that that data(set) may well be extended. However that data is captured, it can easily be stored as an XMLstring in one database field and yet be totally searchable on whatever data element is required. To digress... Create a memo field called XMLData_tx. You know it will receive data from a customer feed containing some, little, or more data than you were expecting. Normally you would have a couple of choices. Either lose data, because you don't have a field in which to store the new, unexpected data, or redesign the data structure, (not practical if lots of installations), and still you're fire-fighting once you know about the changes. An alternative would be to create a single memo field and store the whole XML file within it, (known as a BLOB [Binary Large Object Block]). Because of its structure any <element> remains totally searchable and accessible, even if you don't even know that it exists. DOM/SAX allows you to traverse the tree structure of the XML document and access every <element> including its name but also the content it contains. That doesn't mean it will replace RDBMS. Accessing a low-level <element> in the hierarchy of an XML document stored in a single relational database field will not be fast. But it does have a place, either for archiving data or for when maximum data structure flexibility is required.
You may have gathered by now that we like XML. What we like more is using it to bring real benefits to real-life situations. Whether that means receiving transport orders electronically with automatic update of the Traffic Sheet without any intervention but complete with comprehensive email notifications, or subsequently updating yours, (or your customers), financial systems. The quicker the purchase hits their ledger, the quicker they'll pay it. And they don't need someone to input it. It may be your own in-house system or it may be a trusted business partner. Either way, here at Fargo Systems we believe firmly that all of our XML interface implementations have brought real benefits to our customers and we would love the opportunity to come into your business and assess potential and benefits likewise.