Re: Xquery might have some things right

From: Corey Brown <corey_at_spectrumsoftware.net>
Date: Fri, 5 Mar 2004 09:37:03 -0500
Message-ID: <Se02c.16672$JN2.13942@bignews4.bellsouth.net>

"Eric Kaun" <ekaun_at_yahoo.com> wrote in message news:dn%1c.55833$1O4.38437_at_newssvr33.news.prodigy.com...
> "Corey Brown" <corey_at_spectrumsoftware.net> wrote in message
> news:gZ_1c.46418$0l1.21653_at_bignews3.bellsouth.net...
> >
> > "Mikito Harakiri" <mikharakiri_at_iahu.com> wrote in message
> news:KkN1c.43$ia.170_at_news.oracle.com...
> > > "Eric Kaun" <ekaun_at_yahoo.com> wrote in message
> > > news:bvM1c.21037$va.6147_at_newssvr31.news.prodigy.com...
> > > > Yes, data exchange is a decent use of XML.
> > >
> > > I doubt it. You have System A which want to get some information from
> System
> > > B. How do you do that? Query it (what a surprise). The underlying
> transport
> > > beneath SQL connection doesn't really matter.

>

> Well, I was trying to be kind. Remember that "decent use of XML" is simply a
> comparison to "horrendous uses of XML," and wasn't comparing XML with other
> technologies and formats.

>


> >     No, you use simple publish and subscribe mechanisms. In which case

> exchaning

> >     data with XML works quite well.

>

> But it's just a format, whatever mechanism you use to exchange it. Publish
> and subscribe can be useful, but WHAT is published can be anything. XML is a
> wordy format, and doesn't get the parties involved out of the business of
> having to know the semantics of the data elements.

    Sure, that's why you need an AAIS (application to application interface specification),     otherwise how will you define the contract between one system and the other?

    XML does have "some" advantanges. Here's a short list:

• It's human readable. Developers can visually check on communications between systems simply by taping into the communications channel. Great for debugging too.
• Senders and receivers don't have to be in perfect sync. That is, information can be added at the transmitter that the receiver can simply ignore. This works especially well in a publish subscribe scenario where the subscribers use the published output in different ways.

    Sure it's wordy and shouldn't over extended to do things that it was never intended to do.     But that doesn't mean that it's not useful for certain classes of computing problems.

    Regards
    --Corey
>
> Received on Fri Mar 05 2004 - 08:37:03 CST