Re: [soa-rm] FYI: BEA SOA Reference Diagram

[John Harby <jharby@gmail.com>]

I can live with the diagram but I definitely don't like this statement
for a deliverable:

"Instead, we are examining (!) the concepts and relationships that are
important in modeling SOAs."



On 5/18/05, Duane Nickull <dnickull@adobe.com> wrote:
> Frank is right.  We are not writing an SOA, we are building a reference
> model.  I would refer all back to my earlier posts on this subject.
> 
> Reference models generally avoid any concrete detail, such as showing
> two services.  In abstract, there are no multiple concrete  instances of
> services.
> 
> Case in point - look at the ISO reference model (7 layer stack).  It is
> a communication stack.  It's whole purpose is to act as a reference
> model for building networks yet it does not show two "things"
> communicating.
> 
> I am not saying the BEA bits are not useful.  We just need to keep
> vigilant in the concepts being abstract.
> 
> For those who wish to work on a SOA Reference Architecture, this is
> probably a logical next sub project once the RM is complete.
> 
> Duane
> 
> Frank McCabe wrote:
> 
> > The diagram does not help me very much ...:)
> >
> > I agree, however, that combining services seems to me to be an
> > integral part of service oriented architectures.
> >
> > However, we are *not* doing an SOA!!! At least, that is my
> > understanding.
> >
> > Instead, we are examining (!) the concepts and relationships that are
> > important in modeling SOAs.
> > <SNIP>
> 
>