![](bg7.png)
Even the groups or companies that provides
specifications does not show how they can fit
together, the impression is that each specification
solve a particular problem.
Another point is that the companies and
development groups only talk about the
specifications and standards they proposed. Again,
someone that starts looking for the Web Services
standards and layers will become more confused
than before.
Another important contribution is that in this
work more than fifty Web Services specifications
and standards were analyzed. Thus the protocol on
each layer shows the superseded and competing
protocols in a very straight full view, making easy to
compare these specifications.
The Web Services stack presented and proposed
is an independent view of the Web Services
architecture and can contribute to merge different
efforts performed by the research community.
Although there are different views, some
standards are becoming de facto standards clearly at
lower layers.
Comparing to ISO OSI model the same
phenomenon happened: the protocols at the lower
layers are well defined and accepted while the
higher layers are basically a vision, and becomes
optional in most situations, such as the session layer.
Considering that a new network technology is
under development problems like this can be
avoided, and consistent and well done protocol
stacks can de constructed.
The Web Service protocol stack is a key
component that will guide the development and the
implementation of this technology.
This paper brings this important issue to the
discussion and proposes an independent view of the
Web Services stack, resulted from the comparison
and reasoning about a myriad of protocols and
personal protocol stacks actually available.
REFERENCES
Tanenbaum, Andrew S., 2003. Computer Networks,
Fourth Edition. Prentice Hall, New Jersey
Mitra, Nilo, 2003. SOAP Version 1.2 Part 0: Primer.
W3C Recommendation 24 June. Retrieved May 2,
2006, from <http://www.w3.org/TR/2003/REC-
soap12-part0-20030624/>.
W3C, 2004. Web Services Architecture Working Group.
Retrieved May 2, 2006, from
<http://www.w3.org/2002/ws/arch/>.
Vinoski, Steve, 2004. WS-Nonexistent Standards. IEEE
Internet Computing, vol. 8, no. 6, pp. 94-96. Retrieved
May 2, 2006, from
<http://dsonline.computer.org/0412/d/w6towp.htm>.
OASIS, 2005. OASIS SOA Reference Model TC. Retrieved
May 2, 2006, from <http://www.oasis-
open.org/committees/tc_home.php?wg_abbrev=soa-
rm>
MacKenzie,C. MatthewR et al, 2005. Reference Model for
Service Oriented Architectures. Working Draft 11, 15
December 2005. Retrieved May 2, 2006, from
<http://www.oasis-
open.org/committees/download.php/15966/wd-soa-
rm-11.pdf>
McGovern, James et al., 2003. Java Web Services
Architecture. Morgan Kaufmann, San Francisco.
Chinnici, Roberto et al., 2006. Web Services Description
Language (WSDL) Version 2.0 Part 1: Core
Language. W3C Candidate Recommendation 6
January 2006. Retrieved May 2, 2006, from
<http://www.w3.org/TR/wsdl20/>.
Clément, Luc et al., 2004. UDDI Version 3.0.2. UDDI
Spec Technical Committee Draft. Retrieved May 2,
2006, from <http://www.oasis-
open.org/committees/uddi-spec/doc/spec/v3/uddi-
v3.0.2-20041019.htm>.
Weerawarana, Sanjiva et al., 2005. Web Services Platform
Architecture : SOAP, WSDL, WS-Policy, WS-
Addressing, WS-BPEL, WS-Reliable Messaging, and
More. Prentice Hall PTR
Microsoft, 2006. Web Services Specifications. Retrieved
May 2, 2006, from
<http://msdn.microsoft.com/webservices/webservices/
understanding/specs/default.aspx?pull=>
Arora, Akhil et al., 2005. Web Services for Management
(WS-Management June 2005). Retrieved May 2, 2006,
from <http://msdn.microsoft.com/ws/2005/08/ws-
management/>
IBM, 2006. Standards and Web services. Retrieved May
2, 2006, from <http://www-
128.ibm.com/developerworks/webservices/standards/>
Cantor, Scott et al., 2004. Assertions and Protocols for the
OASIS Security Assertion Markup Language (SAML)
V2.0. Retrieved May 2, 2006, from
<http://www.oasis-
open.org/committees/download.php/9455/sstc-saml-
core-2.0-cd-02.pdf>.
Sun, 2006. Web Services Standards and Technologies.
Retrieved May 2, 2006, from
<http://developers.sun.com/techtopics/webservices/sta
ndards.html>
Turner, Mark; Budgen, David; Brereton, Pearl, 2003.
Turning Software into a Service. Computer,
vol. 36, no. 10, pp. 38-44, October.
Parastatidis; Savas; Webber, Jim, 2004. Assessing the Risk
and Value of Adopting Emerging and Unstable Web
Services Specifications. SCC, pp. 65-72, Services
Computing, 2004 IEEE International Conference on
(SCC'04), 2004.
THE QUEST FOR THE WEB SERVICES STACK
111