Talk:Web Services Description Language

Pronunciation
For my part, I've never heard WSDL pronounced "weasel", which sounds somewhat pejorative to me. User 87.248.128.17 claims "I've heard this used as a reference to WSDL many times." This may well be true, but would probably fall foul of Wikipedia's policy on original research. --RichardVeryard 14:22, 2 August 2006 (UTC)

I have also never heard WSDL pronounced "weasel," nor have any of my co-workers, and we work with WSDLs on a regular basis (internally and with customers). While a very small group of people may pronounce it as "weasel," it is in no way a common pronunciation. --Etev 18:12, 10 August 2006 (UTC)

Definitely pronounced "wiz-dəl". 198.22.123.107 21:07, 29 August 2006 (UTC)

If it helps any, I have always heard it pronounced "wooz-dools" here in Chicago. 71.239.175.188 14:34, 24 May 2007 (UTC)

"WSDL" is an acronym and as such, is not pronounced (as a word). It's individual letters should be read/spoken. Pronouncing it as a word is pure and simple laziness. — Preceding unsigned comment added by 99.246.5.250 (talk) 18:55, 22 June 2011 (UTC)

Ah, but we pronounce many acronyms as words, for example NASA. Definitely wiz-dəl. I have never heard any other pronunciation, and I was immediately corrected when I first entered the protocol space and spelled it out. Ksnow (talk) 15:42, 28 March 2012 (UTC)Ksnow

The WSDL example is nothing like a real-world example, showing only how to do REST over SOAP, and not even a functional RESTful service. No web service of any kind would ever implement an interface like this. I move that it get replaced by the WSDL from an actual existing service. 67.98.226.13 16:50, 21 September 2007 (UTC)

Example
The WSDL Example is conceptual and explain the philosophy behind WSDL: to describe interfaces. Real World examples I've seen, tend to show only the practical aspects of configuring WS engines for SOAP...

By my opinion, WSDL is modeling language for interfaces, like UML is a modeling language for classes, data flow, state chart, etc. in OOP.

I really don't understand the meaning of the "adobe flex" example... maybe would be more intresting to show something from the JAX-WS...

The example needs an introductory sentence, at least, to tell us what it is. I was not even clear whether it was XSD or WSDL, at first. Ksnow (talk) 15:44, 28 March 2012 (UTC)Ksnow

BTW, I have 3 file that I'm using in my thesis for describing this technology.

Here they are, maybe you could think they are a better examples for WSDL.

WSDL 2.0 Sample, with HTTP and SOAP binding
ps. I'm unsure of the correctness of the lines containing whttp:location="{wt:id}"

bye, 'Cristiano, Italy' (i will register a day... )

Q & A
Ask a question about this topic and wait for answer —Preceding unsigned comment added by 213.178.224.165 (talk) 18:55, 23 February 2008 (UTC)

It would be good if this article would include an explanation of "why WSDL", and why a model for web services is a useful thing to have. The article has a heavy focus on the "what" of WSDL, but tells me little about "why" it matters. —Preceding unsigned comment added by 124.177.130.109 (talk) 22:42, 21 April 2009 (UTC)

Huh?
Hi there, I've been a developer and have been using computers for >20 years, but I don't usderstand the "Description", it reads way too exoteric. Could you kindly break it down? Thanks.

" The abstract definition of ports and messages are separated from their concrete use or instance, allowing the reuse of these definitions. A port is defined by associating a network address with a reusable binding, and a collection of ports define a service. Messages are abstract descriptions of the data being exchanged, and port types are abstract collections of supported operations. The concrete protocol and data format specifications for a particular port type constitutes a reusable binding, where the operations and messages are then bound to a concrete network protocol and message format. In this way, WSDL describes the public interface to the web service. ok? " 114.145.189.97 (talk) 11:23, 24 April 2009 (UTC)

Uninformative Introduction
I agree with Huh's comment above.

Always define a technical product, service or standard in terms of the functions it performs or the problems it solves.

The definition should then proceed to briefly discuss its operating environment including system requirements, then describe how it is structured or how it operates, and finally describe what it returns and under what circumstances. Somewhere along the way, a definition should mention the data it requires to operate. Present details for these narrative points later in the article.

Do not start your WSDL description by tracing WSDL versions, or by telling me that it is a W3C recommendation, not a standard. This means nothing to the new reader. At the most, this content should be a NOTE at the END of a functional description.

Examples are too long and too complex to be usable. No example on this page should be longer than twenty lines.

This page needs brief sections that describe how a developer creates a wsdl service; how a service initiates, how it operates and what it returns.

76.191.140.220 (talk) 23:03, 14 January 2011 (UTC)

Subset WSDL?
The entire paragraph on 'Subset WSDL' references two works by the same author, and does not describe the concept in any meaningful way. I'd suggest it is removed from this page as irrelevant information, or at least moved down to allow readers to focus more on the useful parts of this article.

The last sentence, "AWSCM is the pioneer tool to construct SWSDL's successfully" sounds like promotional talk to recommend a tool, not impartial information. It's been copied from the abstract of the article it links and adds no value to the page.

Calvenable (talk) 09:59, 12 January 2023 (UTC)
 * ✅. Jay  💬 10:44, 12 January 2023 (UTC)