How does XAML relate to other Web Service standards?
In order to understand how XAML relates to many of the existing standards, it is first necessary to understand what function each of these standards performs. When a web service is built, described, discovered and used, there are many elements that will be required. The combination of these many different elements is called a web services architecture. Some categories of these elements are: registries, business process modeling, negotiation, service description and web service transport protocols. In order to use a web service, the existence of the service must be discovered. This discovery usually takes place in a “phone book” of web services known as a registry. Registries, such as UDDI and the ebXML registry/repository, contain human readable information that can be browsed and searched to find companies and their services. Once a desired service is located, the terms of use can be reviewed and/or negotiated. The e-speak framework provides an elaborate negotiation mechanism. ebXML a
Related Questions
- How does UDDI relate to other Web services-related standards projects at OASIS, W3C, and WS-I?
- How does UDDI relate to other Web services-related standards projects at OASIS, W3C, and WS-I?
- How does XAML relate to XML-based web service transport protocols (XP, SOAP, ebXML Transport)?
- How does XAML relate to XML-based web service transport protocols (XP, SOAP, ebXML Transport)?
- How does XAML relate to other Web Service standards?
- What standards define a web service?
