Avoid XML schema wildcards for Web service interfaces

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....

Full description

Saved in:
Bibliographic Details
Published in:IEEE internet computing Vol. 10; no. 3; pp. 72 - 79
Main Author: Pasley, J.
Format: Journal Article
Language:English
Published: New York, NY IEEE 01.05.2006
IEEE Computer Society
Subjects:
Applied sciences
Computer science; control theory; systems
Computer systems and distributed systems. User interface
Context-aware services
Contracts
Costs
Data structures
Exact sciences and technology
HTML
Software
Standards organizations
validation
Vocabulary
Web services
Web sites
XML
XML schema
XML language
Internet
Distributed computing
HTML language
Version management
Web service
ISSN:1089-7801, 1941-0131
Online Access:Get full text
Tags: Add Tag
No Tags, Be the first to tag this record!
Description
Summary: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
Bibliography:ObjectType-Article-1
SourceType-Scholarly Journals-1
content type line 14
ObjectType-Article-2
ObjectType-Feature-1
content type line 23
ObjectType-Feature-2
ISSN:1089-7801
1941-0131
DOI:10.1109/MIC.2006.45