I was going through the reference model os soa by OASIS and I found it lacking seriously in most of the abstractions it talks about
Lets start with soa definition itself-
SOA- (SOA) is a paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownership domains.
Till now my general understanding of soa was
SOA is an architectural approach that seeks to align business processes with service protocols and the underlying software components and legacy applications that implement them.
similarly abstraction of vocabulary execution context, visibility, real-world effect, interaction all seems to be too primitive, lacking in general high level abstraction.
At one point document says
A service is a mechanism to enable access to one or more capabilities?
Is service a mechanism or end?
In the topic "Dynamics of service" it has used so many closely related and confusing terms like visibility, awareness, real-world effect, willingness, reachability etc.?
What is the general opinion of people here?
---------------
regards,
shashank
__._,_.___
SPONSORED LINKS
| Computer software | Computer security software | Computer software program |
| Computer fax software | Computer virus software |
Your email settings: Individual Email|Traditional
Change settings via the Web (Yahoo! ID required)
Change settings via email: Switch delivery to Daily Digest | Switch to Fully Featured
Visit Your Group | Yahoo! Groups Terms of Use | Unsubscribe
Change settings via the Web (Yahoo! ID required)
Change settings via email: Switch delivery to Daily Digest | Switch to Fully Featured
Visit Your Group | Yahoo! Groups Terms of Use | Unsubscribe
__,_._,___
