Avoid XML Schema Wildcards For Web Service Interfaces

Authors:
James Pasley
Affiliations:
Cape Clear Software
Venue:
IEEE Internet Computing
Year:
2006

Citing 0
Cited 6

WSDL and UDDI extensions for version support in web services

Journal of Systems and Software
Improving Web Service descriptions for effective service discovery

Science of Computer Programming
Analysing complexity of XML schemas in geospatial web services

Proceedings of the 2nd International Conference on Computing for Geospatial Research & Applications
Predicting web service maintainability via object-oriented metrics: a statistics-based approach

ICCSA'12 Proceedings of the 12th international conference on Computational Science and Its Applications - Volume Part IV
An approach for web service discoverability anti-pattern detection for journal of web engineering

Journal of Web Engineering
Anti-pattern free code-first web services for state-of-the-art Java WSDL generation tools

International Journal of Web and Grid Services

Quantified Score

Hi-index	0.00

Visualization

Abstract

Developers risk negative side effects when they attempt to make Web services interfaces extensible without understanding the context in which various mechanisms are applied. Given the overuse and misapplication of the HTML example,developers often litter their interfaces with XML Schema wildcards. This increases complexity and results in ambiguous interface definitions. A more appropriate versioning strategy for Web services development can help developers avoid these problems.