OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

uddi-spec message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Proposal for UDDI interoperability demonstration at XML 2003


Title: Proposal for UDDI interoperability demonstration at XML 2003

Dee,

On yesterday's TC meeting, the UDDI TC agreed to respond to your RFI for interoperability demonstrations at XML 2003 with the following proposal (see below, including the attached diagram).

We believe that the technical deployment model is already quite stable and represents the core of the interoperability demonstration. The business scenario is a draft version and might still change substantially, depending on what the participating vendors believe to be the most appropriate scenario for this kind of demonstration and conference.

Please note that so far, we have four companies that tentatively plan to participate in the demo (IBM, Microsoft, SAP, and UnitSpace). One reason for the tentative commitment is that several companies are concerned about the costs that may be necessary for participation and indicated that this influences their ability to actually participate.

Could you please keep us up to date with regard to your negotiations with IDEAlliance? We are especially interested in the kind of venue we can use for the demo and a notion of necessary expenses for participants.

Thanks a lot,
 Claus

-------------------
Technical deployment model
The scenario involves at least 3 UDDI registries and at least 2 UDDI client applications so that at least six interactions can be demoed. This demonstrates the need for the UDDI standard and demonstrates that all clients and servers conform to the UDDI specification.

UDDI Version 2 is demonstrated. Eventually, the "Using WSDL in a UDDI registry" TN, Version 2 is demonstrated.
Business scenario
A supply chain scenario is demonstrated (see attached diagram). The UDDI clients are part of purchasing applications (representing different companies from a certain industry, e.g. car manufacturers), the UDDI registries are part of private exchanges (representing communities from different industry verticals, e.g. tire industry, plastics industry, paintings industry). The basic assumption is that the car manufacturers have a business relationship (as a customer) with the private exchanges so that they can use their (UDDI) services.

The car manufacturers use the UDDI inquiry APIs that are provided by the private exchanges to
a) discover updated information about their known suppliers and the Web services they use and
b) dynamically discover new suppliers and their Web services.
The second use case is more appropriate in the early steps of the overall supply chain, such as for using Web services to request product catalogs, including terms and conditions for offered products. It can be used, for example, to demonstrate dynamic aggregation of product catalogs (provided that the catalogs are accessible over the same Web service type, a.k.a. tModel). The queries are parametrized by the product type, and/or Web service type in order to find suitable suppliers and Web services. The category systems and Web service types may be specific to the industry vertical of the different UDDI registries and may also indicate additional characteristics, such as whether the Web services are in test or production mode.

The scenario also covers the UDDI publication API in that the automotive suppliers each have a business relationship (as a supplier) with some of the private exchanges so that they can use their (UDDI) services to update information about themselves and the Web services they offer. In particular, updates are demonstrated that make the suppliers' UDDI registrations visible to the manufacturers' inquiries, e.g. by categorizing the businessEntity accordingly.

<<UDDI@XML2003Scenario.PNG>>

UDDI@XML2003Scenario.PNG



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]