Abstract
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.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
