> >>
> >> I'm also in the progress of creating a SOA Reference Architecture.  
> >> It's not an easy task, but I have used the OASIS Reference Model as  
> >> a starting point. There is many issues I'm looking into, and some  
> >> of them are:
> >>
> >> A more detailed model of a service that makes it possible to use a  
> >> common langauge, i.e. relationships between messages, operations,  
> >> interface, ports, service and service provider. Seems like an easy  
> >> task, but I'm not able to construct a model that satisfies  
> >> everybody. E.g should there be a 1-1 relationship between a service  
> >> and a service interface (there could be many ports into the same  
> >> service, but they all use the same interface) or should a service  
> >> be able to implement many interfaces?
> >>     
> >
> > These are exactly the kind of questions I face in every single  
> > customer project. The first step is to define a model (or metamodel,  
> > if you prefer) of SOA concepts. For example, there is no right or  
> > wrong when it comes to questions such as whether a "service"
contains  
> > "operations" (or whether operations *are* services), whether
"service  
> > interface", "service", and "service implementations" are distinct  
> > concepts ... I have created several incompatible such models by now  
> > to incorporate specific customers' pre-existing terminology.
> >
> > This is also what I would hoped for the OASIS SOA reference model to  
> > provide, instead of high-level statements that are so consensus- 
> > driven that they are almost meaningless.
> >
> >   
I haven't completely read the latest version of the draft but I
thought the earlier versions (i.e. Working Draft 7), where they
defined a layered model (service, service description, policy,
contract, data model etc) was far more useful. As an architect I found
it provided a good foundation for discussing SOA. 

cheers
</jima>







------------------------ Yahoo! Groups Sponsor --------------------~--> 
Check out the new improvements in Yahoo! Groups email.
http://us.click.yahoo.com/6pRQfA/fOaOAA/yQLSAA/NhFolB/TM
--------------------------------------------------------------------~-> 

 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/service-orientated-architecture/

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 



Reply via email to