OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   RE: [xml-dev] Categories of Web Service messages: data-oriented vs acti

[ Lists Home | Date Index | Thread Index ]

Again, we are cycling back to DOCTYPE over root over PI.

It works as long as a message has a detectable and reliable type 
and you send it to a source that does precisely what you expect. 
Otherwise, you are hardwiring two endpoints.  That isn't very 

It is straightforward to make the action an optional piece 
of information similar to Mike Kay's attribute, or a PI, 
or a wrapper value.  Someone has to bell the cat.  Who 
chooses?  Even if the consumer chooses, do they expect 
the itinerary from you and know to store it, print it, 
delete it, what?

XML separation of data from presentation is just another 
XML myth.  Properties is properties; nodes is nodes; tell 
me who gets to name the names and we can get on with business. 


-----Original Message-----
From: Roger L. Costello [mailto:costello@mitre.org]

XML is well known for its separation of data (XML) from presentation of
the data (XSLT), i.e., "one data but many views of the data".  

I would like to conjecture a similar design pattern for XML messages -
the separation of an XML message from the consumption of the message,
i.e., "one XML message but many consumers of the message". 

For example:
                             |        |
                    |------> | Logger |
                    |        |        |
|------------|      |        |--------|
|            |      |
| Intinerary | -----|        |--------------|
|            |      |        |              |
|------------|      |------> | Travel agent |
                             |              |

Here the Itinerary message is being consumed by 2 different applications
- a Travel agent (which responds with an XML message containing flights)
and a Logger application which logs all itineraries (and no response is
generated).  There are 2 important things to note: 

1. The same message (data) is usable by a variety of applications.  This
is possible because the Itinerary message is just data, it is not tied
to any application.  That is, there are no "action tags".

2. The application which consumes the data decides on the purpose of the

I like the clean separation of the XML message from the processing of
the message.  Isn't this exactly analogous to what we strive for with
XML and XSLT? To my mind it is, so I again assert that it is best to
leave out "action tags" in an XML message.  Comments?  /Roger

P.S. Great discussion!


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS