RE: [soa-rm] SOA Definition - the graphic

["Duane Nickull" <dnickull@adobe.com>]

Frank:

Comments inline. 

-----Original Message-----
From: Francis McCabe [mailto:fgm@fla.fujitsu.com] 
Sent: Thursday, October 06, 2005 2:10 PM
To: Duane Nickull
Cc: soa-rm@lists.oasis-open.org
Subject: Re: [soa-rm] SOA Definition - the graphic

Well, here goes ....

1. There is something fundamentally unknowable about the acted upon  
resources. Certainly the user of a service never gets to see this.  
But even the service provider will often have a hard time pointing to  
this.

DN: Agree.  This would be consistent with a service being autonomous WRT
controlling its level of opacity.  Essentially, it suggests the same
pattern as a proxy server.

  If you are updating a database, but the database is replicated,  
then which is the resource that you are modifying in response to a  
service request? What happens if you swap one database out for  
another? There are more examples here; but the essence is that it can  
be extremely difficult to pinpoint the resource.

  On the other hand, its not necessary, so why bother?

DN: Agree - why bother trying to identify the resource unless required.
For the RM however, the question is whether or not we want to have the
"thing" represented as an abstract concept within the RM.  I remain
agnostic and am not strongly convinced either way.

Duane