W3C home > Mailing lists > Public > public-ws-chor@w3.org > May 2003

Re: internal vs external

From: Jon Dart <jdart@tibco.com>
Date: Mon, 05 May 2003 12:45:20 -0700
Message-ID: <3EB6BF50.8030201@tibco.com>
To: Assaf Arkin <arkin@intalio.com>
CC: Champion Mike <Mike.Champion@SoftwareAG-USA.com>, public-ws-chor@w3.org

Assaf Arkin wrote:


> The rule I stand by is "what you don't need to expose should not be 
> exposed. period". 

This is a good general design principle, but there are cases where you 
need to limit information and cases where you don't. If the choreography 
involves only internal, non-sensitive systems, then each can have 
complete information about the other, at least complete at the level of 
what interfaces are used and how they interact (not message contents, 
necessarily).

> I would not be interested in supporting a language 
> that forces me to expose to any party how I happen to do things when I 
> service their requests. Except in those case where I do need to expose 
> that information for the benefit of these parties as agreed upon by all 
> parties involves (in this case customer, rental agency, credit agency). 
> My question is therefore how do I deal with those cases that do require 
> some specific steps to be exposed in a controlled manner as dictated by 
> the business scenario?
 >
 > arkin

This is related to the "central"  vs. "participant-focused" modelling 
issue that has periodically been discussed in this group (and which has 
recently re-surfaced in ws-arch).

If I have to employ a centralized model that includes all participants, 
then IMO it becomes more difficult to "hide" interactions from some 
subset of those participants. (I say more difficult rather than 
impossible, because you could imagine a technology that combined a 
central modelling facility with views into the model).

--Jon
Received on Monday, 5 May 2003 15:45:28 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 01:00:17 GMT