[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Categories of Web Service messages: data-orientedvs action

• To: <xml-dev@l...>
• Subject: Re: Categories of Web Service messages: data-orientedvs action-oriented
• From: Ramesh Gupta <ramesh@e...>
• Date: Mon, 04 Feb 2002 12:11:06 -0800
• In-reply-to: <3C5EE4D1.BE45A528@m...>
• User-agent: Microsoft-Outlook-Express-Macintosh-Edition/5.0.3

on 2/4/02 11:45 AM, Roger L. Costello at costello@m... wrote:

> I have convinced myself that there are two fundamentally different
> approaches to designing Web service XML messages.  They are:
> 
> 1. The data-oriented approach
> 
> 2. The action-oriented approach
>
> [snip]
>
> I contend that this action-oriented root element gives the message a
> very different feel.  I contend that it tightly couples the message to a
> particular kind of service - one that returns flight information.  The
> data-oriented approach, on the other hand, is not coupled to any
> service, so it could be used by a variety of services.

You would still have to identify what service you want your data to be used
with. Are you thinking of embedding a service "code" of some kind in the
data itself?

In other words, you would need both. Conceptually, you can combine the two
"approaches" as:

<getFlights>
    <itinerary>
        ...
    </itinerary>
</getFlights>

Regards,

Ramesh Gupta

• References:
  • Categories of Web Service messages: data-oriented vs action-oriented
    • From: "Roger L. Costello" <costello@m...>

• Prev by Date: Re: XPointer crisis
• Next by Date: RE: Categories of Web Service messages: data-oriented vs action-oriented
• Previous by thread: Categories of Web Service messages: data-oriented vs action-oriented
• Next by thread: RE: Categories of Web Service messages: data-oriented vs action-oriented
• Index(es):
  • Date
  • Thread