• To: "'Roger L. Costello'" <costello@m...>,<xml-dev@l...>
• Subject: RE: Categories of Web Service messages: data-oriented vs action-oriented
• From: "Michael Kay" <michael.h.kay@n...>
• Date: Tue, 5 Feb 2002 09:42:53 -0000
• Importance: Normal
• In-reply-to: <3C5EFBCE.AA5373EB@m...>
• Reply-to: <michael.h.kay@n...>

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

No problem with that, and you can abstract the "action" part so that the
detailed decisions are made by the recipient rather than the sender, but you
still need to say why you are sending the data. If I get a postcard that
just has an address on it, I bin it. If I get a postcard that says "please
note my new address", then I can do something with it. That doesn't stop
other recipients taking different action.

Michael Kay
Software AG
home: Michael.H.Kay@n...
work: Michael.Kay@s...

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

• Prev by Date: SV: Categories of Web Service messages: data-oriented v saction-oriented
• Next by Date: RE: Co-operating with Architectural Forms
• Previous by thread: Re: 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