Talk:Web Services Description Language

message: 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)
thread_title:  Pronunciation 

message: 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)
thread_title: Example

message: 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)
thread_title:  Q & A 

message: 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)
thread_title:  Huh? 

message: 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)
thread_title:  Uninformative Introduction 

message: 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)
replies: text: . Jay 💬 10:44, 12 January 2023 (UTC)
thread_title:  Subset WSDL?