|
On Thu, 4 Sep 2003 17:17:24 -0500 "Bartell, Aaron L. (TC)" <ALBartell@xxxxxxxxxxxxxx> wrote: > I think that would be worse than using XML, but that is > just my opinion. > Besides XML has so much more built into it like Schemas > and XSL (XSL used > for XML translations in this example). So much technology and work to do something that at one time was so simple. :) > > Are you going to tell your customer "Ok, first your going > to send me > Order=123, and when I respond with resp=success then you > send me item=11111, > and when I respond with resp=success you send me > item=2222, etc. . ."? XML > is so much more than just a buzzword and bulky. You're breaking it down to a point that is silly, Aaron. If you look at any XML document you can see it normally has a hierarchical structure that you can pull out into relational segments. Why? Because the data normally comes from a relational database to begin with. Order Header, Order Detail, Shipping Master, Shipping Detail, etc.. etc.. Hierarchical data is so 1980s. But I guess everything comes back into style. <snicker>
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.