Answers are grounded in this paper and cite their sources.
Web services for years as a software engineering technique. Programmers need a service description language so they can see what a software component written as a Web service does and how to use it. WSDL also facilitates the concept of software components, which could lead to the programming dream of reusable, maintainable software. Well, it could, were these components' functions better described. Unfortunately, programmers who use these functions within an enterprise typically treat them like a new version of subroutines. The next programmer hired to work on one of these components hasn't much more of a clue how to use it than he or she did with any other piece of software. Web services with semantic and enforceable descriptions that would enable dynamic interoperability over the Internet, would be more practical.
No takes yet. Share an insight, caveat, or question.
Charles Petrie (2009) studied this question.
Synapse has enriched 10 related papers. Consider them for comparative context: