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

RE: Categories of Web Service messages: data-oriented vs actio

  • To: <xml-dev@l...>
  • Subject: RE: Categories of Web Service messages: data-oriented vs action-oriented
  • From: Bill de hOra <dehora@e...>
  • Date: Tue, 5 Feb 2002 11:56:17 -0000
  • Importance: Normal
  • In-reply-to: <3C5EE4D1.BE45A528@m...>

root element name in webservice

> From: Roger L. Costello [mailto:costello@m...] 
>
> 
> This XML message is identical to the earlier XML message 
> except for the root element.  The root element implies 
> action.  The root element is directly correlated to a method 
> name.  Its child elements are the parameters.  

The difference I can see is not that the root element has a different
name, that a human might reasonably interpret by default as a verb.  It
is that in the second case the _emitting_ software understands the root
element as a verb, not a noun. Changing tags doesn't make data
action-oriented, invoking code with that data does.


> 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.

The tightness in your examples are in any assumptions the *emitting*
software is making about what will be done to its data. i.e. how that
data will be acted on. Either way it's emitting data, passing a message,
uttering, or whatever. Tight coupling comes from faking a single thread
of execution on a network, not enough indirection, and hard coding
assumptions in software about what other software should be doing. 

The distinction I do see between action and data is this:

-data: the emitter doesn't assume how the message 
is to be processed.

-action: the emitter assumes the message will 
be processed according to its understanding of 
a verb.

(the latter sounds like hard-coding to me)

I'd rather see a classification of web services data based on speech act
theory. 

regards,
Bill de hOra



PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
 

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.


Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.