The WS-I Basic Profile
• To aid in the development of Interoperable web services, an industry consortium called the Web
Services Interoperability Organization (WS-I) was formed.
- The member list of WS-I reads like a who’s who of new technologies: Microsoft, Sun, Oracle, VeriSign
…
- The WS-I has created several specifications to codify how to create web services, including a popular
“Basic Profile”.
- They work with the existing SOAP and WSDL specs seeking to clear up inconsistencies and unclear
requirements without requiring changes to the fundamental specs (avoiding slow moving W3C spec rewriting).
• The Basic Profile works to define how to send messages with SOAP and define documents with WSDL.
- Many of the interoperability issues caused by multiple vendor implementations are directly defined in
the WS-I.
- Although WS-I helps to remove interoperability issues, interoperability issues will continue to happen.
- Currently the Basic Profile is at version 1.1.
- You can keep up with the Basic Profile at http://www.ws-i.org/deliverables/workinggroup.aspx?
wg=basicprofile.
• To aid in interoperability, WS-I places constraints on how you can use the tools provided. Some of the
limitations are listed below.
- Services must be described using a WSDL document.
- Limitations on what can be passed in a SOAP Fault are defined. A SOAP Fault is the standard SOAP
error message technique.
- Messages must not contain SOAP Encoding attributes.
- The SOAP message must have no DTD’s or processing instructions.
- Web services have to use the POST method when passed via HTTP.
• The specification itself contains many limitations, all aimed at solving the little errors that were
generated when integrating different SOAP toolkits.
• The WS-I is also working on recommending standards for evolving web services features.
• To aid in the development of Interoperable web services, an industry consortium called the Web
Services Interoperability Organization (WS-I) was formed.
- The member list of WS-I reads like a who’s who of new technologies: Microsoft, Sun, Oracle, VeriSign
…
- The WS-I has created several specifications to codify how to create web services, including a popular
“Basic Profile”.
- They work with the existing SOAP and WSDL specs seeking to clear up inconsistencies and unclear
requirements without requiring changes to the fundamental specs (avoiding slow moving W3C spec rewriting).
• The Basic Profile works to define how to send messages with SOAP and define documents with WSDL.
- Many of the interoperability issues caused by multiple vendor implementations are directly defined in
the WS-I.
- Although WS-I helps to remove interoperability issues, interoperability issues will continue to happen.
- Currently the Basic Profile is at version 1.1.
- You can keep up with the Basic Profile at http://www.ws-i.org/deliverables/workinggroup.aspx?
wg=basicprofile.
• To aid in interoperability, WS-I places constraints on how you can use the tools provided. Some of the
limitations are listed below.
- Services must be described using a WSDL document.
- Limitations on what can be passed in a SOAP Fault are defined. A SOAP Fault is the standard SOAP
error message technique.
- Messages must not contain SOAP Encoding attributes.
- The SOAP message must have no DTD’s or processing instructions.
- Web services have to use the POST method when passed via HTTP.
• The specification itself contains many limitations, all aimed at solving the little errors that were
generated when integrating different SOAP toolkits.
• The WS-I is also working on recommending standards for evolving web services features.
WS-I
Table of Contents
online learning aid. Any attempts to copy, reproduce, or use for training is strictly prohibited.
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
Courseware
Training Resources
Tutorials
Services