For the most part, I agree with you -- but SOA /= Web Services. SOA has been
with us a long time: ONC, DCE, CORBA, DCOM, RMI, Jini, JXTA, etc. SOA refers
to the service-oriented (or service-orinetated) style of design -- the
"guiding principles" for application design.

The protocols don't really matter, but the metadata does. As long as you
have standard metadata, you can negotiate the protocols. Hence WSDL, XML
Schema, WS-Policy, and other metadata formats are critical. Certainly they
will morph over time. For example, the differences between WSDL 1.1 and WSDL
2.0 are quite substantial. But these are simple tooling issues to migrate
from one to the other.

Anne

-----Original Message-----
From: Ernie Varitimos [mailto:erniev@...]
Sent: Tuesday, August 31, 2004 11:24 AM
To: service-orientated-architecture@yahoogroups.com
Subject: Re: [service-orientated-architecture] Are SOA's getting lost in
translation?

Web Services is only one of the myriad of components that might make up
an enterprise API, a.k.a. the Enterprise Service Bus (ESB). Web
Services will come and go, as did/will CORBA, DES, JXTA and others.
What remains is the need expose an organizations API through the
traversal of intelligent metadata. IMO the data itself is what's
important, not the transport mechanisms, nor the repositories. The real
challenge is agreement upon common semantics and ontologies.

-ernie

On Aug 30, 2004, at 1:42 PM, Gervas Douglas wrote:

> <<Gartner predicts that by 2008, more than 60 percent of enterprises
> will use SOA as the "guiding principle" when creating mission-
> critical applications and processes. That being said, it is
> important to realize that SOA isn't a new concept to the IT
> industry; it is just one that will be taking on a new life and a new
> direction. I attribute this to the popularity and gradual adoption
> of Web services - an industry standard for how the SOA repository
> should look, for how the reusable business processes should look and
> describe themselves and for how communication should happen. A major
> benefit is that there are no dependencies for how the services are
> implemented or what technology is being used. Plus after a service
> is deployed and becomes available for reuse, it is also tested,
> predictable and documented, driving down development costs.
>
> <You no longer have silos of architectures unique to an organization
> or department, but instead have made the architecture open yet
> secure.breaking down borders. The ability to build new applications
> that serve business processes and data across the organization and
> also extend their reach to a disparate array of customers, partners
> and suppliers provides for a tremendous advantage over competitors
> and is becoming more and more critical to the success of an
> organization.>>
>
> You can find this article at:
>
> http://zdnet.com.com/2100-1107_2-5325403.html
>
> Gervas
>
>
>
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>






Yahoo! Groups Links