in black and white
Main menu
Share a book About us Home
Biology Business Chemistry Computers Culture Economics Fiction Games Guide History Management Mathematical Medicine Mental Fitnes Physics Psychology Scince Sport Technics

the semantic web a gide to the future of XML, Web Services and Knowledge Management - Daconta M,C.

Daconta M,C. the semantic web a gide to the future of XML, Web Services and Knowledge Management - Wiley publishing , 2003. - 304 p.
ISBN 0-471-43257-1
Download (direct link): thesemanticwebguideto2003.pdf
Previous << 1 .. 28 29 30 31 32 33 < 34 > 35 36 37 38 39 40 .. 116 >> Next

Although UDDI has been embraced by major vendors, such as Microsoft and IBM, it is evolving and changing. It is not yet a standard, but it will be. Many business leaders have debated whether businesses would want to use a registry on the Internet; they might fear giving too much information by publishing descriptions of their assets on the Web. The question some critics ask is, "Do you want your technology to choose your business partners?" It remains to be seen whether or not UDDI will fully be embraced and implemented in a fully open B2B environment. Many market analysts believe that UDDI private registries, used in EAI, will provide much value.
Understanding Web Services
What Are ebXML Registries?
The ebXML standard was created by OASIS to link traditional data exchanges to business applications to enable intelligent business processes using XML. Because XML by itself does not provide semantics to solve interoperability problems, ebXML was developed as a mechanism for XML-based business vocabularies. In short, ebXML provides a common way for businesses to quickly and dynamically perform business transactions based on common business practices. Figure 4.7 shows an example of an ebXML architecture in use. In the diagram, company business process information and implementation details are found in the ebXML registry, and businesses can do business transactions after they agree on trading arrangements.
Information that can be described and discovered in an ebXML architecture includes the following:
■■ Business processes and components described in XML
■■ Capabilities of a trading partner
■■ Trading partner agreements between companies
Figure 4.7 An ebXML architecture in use.
Chapter 4
The heart of the ebXML architecture is the ebXML registry, which is the mechanism that is used to store and discover this information. Although it seems similar in purpose to UDDI, the ebXML registry contains domain-specific semantics for B2B. These domain-specific semantics are the product of agreement on many business technologies and protocols, such as EDI, SAP, and RosettaNet. Simply put, ebXML could be described as the start of a domain-specific Semantic Web.
The focus of ebXML was not initially on Web services, but it now uses SOAP as its message format. Therefore, many believe that ebXML will have a large role in the future of Web services. Unlike UDDI, ebXML is a standard. The ebXML standard does have support from many businesses, but the most influential companies in Web services, IBM and Microsoft, would like to see UDDI succeed as a registry for business information. Skeptics of ebXML suggest that its specifications have much content on business processes, but it will only be successful if businesses agree to those processes. However, it is possible that the two technologies can complement each other, and ebXML could succeed in the B2B market, while private UDDI registries succeed in the EAI market in the short term.
Although the technologies of UDDI and ebXML registries can complement each other, each will undoubtedly have its key successful areas. The following scenarios are indeed possible:
■■ Using the UDDI business registry to find ebXML registries and ebXML-enabled businesses for organizations that support ebXML
■■ Using UDDI to help businesses find other businesses to transact Web services
■■ Using ebXML registries for finding other ebXML-enabled businesses
It is unclear what the future holds for these technologies, because UDDI is continuing to evolve and ebXML has not yet seen widespread adoption.
Orchestrating Web Services
Orchestration is the process of combining simple Web services to create complex, sequence-driven tasks. This process, sometimes called flow composition or Web service choreography, involves creating business logic to maintain conversations between multiple Web services. Orchestration can occur between an application and multiple Web services, or multiple Web services can be chained into a workflow, so that they can communicate with one another. This section provides an example of a Web service orchestration solution and discusses the technologies available.
Understanding Web Services
A Simple Example
For our example, we'll list five separate Web services within a fictional organization: a hotel finder Web service, a driving directions finder, an airline ticket booker, a car rental service, and an expense report creator:
Hotel finder Web service. This Web service provides the ability to search for a hotel in a given city, list room rates, check room availability, list hotel amenities, and make room reservations.
Driving directions finder. This Web service gives driving directions and distance information between two addresses.
Airline ticket booker. This Web service searches for flights between two cities in a certain timeframe, lists all available flights and their prices, and provides the capability to make flight reservations.
Car rental Web service. This provides the capability to search for available cars on a certain date, lists rental rates, and allows an application to make a reservation for a car.
Previous << 1 .. 28 29 30 31 32 33 < 34 > 35 36 37 38 39 40 .. 116 >> Next