This is the second article in a series of articles that relate to a new approach to using WSDL and UDDI, described in a new OASIS UDDI Technical Note. This article describes the types of UDDI query that can be issued against a UDDI model built according to the Technical Note.

Each binding element in the Web service's description file describes a supported protocol. Similar to the portType element, the binding element includes supported operations, as well as the input and output for each operation. The bindings provide concrete information on what protocol is being used, how the data is being transported, and where the service is located.

A WSDL binding style can be RPC or document. The use can be encoded or literal. How do you determine which combination of style/use to use? This article will help you decide.

When planning to use a new Web service, you need to learn its interface first. You can learn it from the Web service's WSDL (Web Services Description Language) document. It describes the messages that the Web service understands, the format of its responses to those messages, the protocols that the service support, and so on. The WSDL document is easy to browse. Just click the minus ("-") and plus ("+") signs along the left edge of the elements.

The World Wide Web Consortium (W3C) yesterday released the first public working drafts of the Web Services Description Language (WSDL) version 1.2.

Web Services Description Language (WSDL), originally developed by IBM, Microsoft, and others is an XML format for technical description of Web services. In this tutorial, Mike Olson and Uche Ogbuji introduce WSDL4Py, an open-source Python library for WSDL 1.1 hosted by IBM developerWork's open-source zone. Usage of the library is explained, as well as discussion of its development.

This article describes the Web Services Description Language (WSDL), an XML grammar for specifying properties of a Web service such as what it does, where it's located, and how to invoke it. It also introduces the IBM WSDL toolkit, which can generate stubs from WSDL and simplify the creation of Web services applications.

In this continuing series covering the basics of Web services, I've described Web services and explained how to format requests to them (as XML) and how to communicate with the services using SOAP. Yet, given that I know a Web service exists, how do I know where on the Web it might be available? How do I know just what sort of message to send? How do I know the format of a SOAP envelope's contents so that the remote server will understand what I want done?

A Web service's interface is covered in its WSDL format. A WSDL document always has a definitions element as its root. Any WSDL language element can contain the documentation element.

In a move to establish itself as a key provider of technology for creating and editing Web Services, Cape Clear Software Inc. Wednesday announced a free editor for the Web Services Definition Language (WSDL).

A WSDL binding style can be RPC or document. The use can be encoded or literal. How do you determine which combination of style/use to use? This article will help you decide.

In the document/literal style of Web services, the schemas of the interchange formats are often based on an existing document standard. This can cause problems synchronizing WSDL files with the standard schemata. This tip shows how to use XInclude to incorporate external schema fragments into a WSDL file.

In the document/literal style of Web services, the schemas of the interchange formats are often based on an existing document standard. This can cause problems synchronizing WSDL files with the standard schemata. This tip shows how to use XInclude to incorporate external schema fragments into a WSDL file.

In the first part of this article, I explained how to apply a stylesheet to a WSDL document. In this article I'll take a closer look at the simplifyWSDL stylesheet itself.

The message element describes the data being exchanged between the Web service providers and consumers. Each Web method has two messages: input and output. The input describes the parameters for the Web method; the output describes the return data from the Web method.

You've built your UDDI client, now find out how to use it. This article explains how to build a WSDL client. Your client will download WSDL files, parse them to read interface details, author service invocation requests, and collect information on any Web service you investigate.

Simple Object Access Protocol (SOAP) provides access to remote objects. Examples of such objects are simple or Enterprise JavaBeans components and COM/COM+ objects, etc. These objects reside inside different enterprises and may exist anywhere on the Internet. Therefore, SOAP communication works across the Internet and is a mechanism to exchange information between different enterprises.

This document builds upon Part I to show how to add type information to a WSDL document. Dave Winer proposed a second interface, one with multiple parameters and a structure to deal with. Just like cooking shows on TV, this essay starts with a document which has already been partially prepared, in this case by a member of the studio audience.

IBM's XML Evangelist, Mark Colan, emphasized the need for standards to exchange data between applications from different vendors. To this end, he discussed ebXML and Web Services. Colan presented a Gartner study that indicated that although XML had reached the so-called Peak of Disillusionment in 4Q99, Gartner predicted by 4Q01 it will reach the Plateau of Productivity. (And perhaps by then, we'll know who the next US president will be, too ;-)

In order for a person or company to run a Web service, basic information about that Web service needs to be provided - information such as where the service is located, how the service can be bound to, and similar information. All this information is provided by a Web Services Description Language (WSDL) document. In this column, we'll take a look at what WSDL is, how it works, and what the future may hold for WSDL.