[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: AW: [uddi-ms] Gartner Application and WS Submit - Presentation by the OASIS UDDI Spec TC
Von: Luc Clement [mailto:Luc.Clement@systinet.com]
Gesendet: Mittwoch, 18. August 2004 21:50
An: Daniel Feygin; 'Andrew Hately'; Rob Kochman; firstname.lastname@example.org; Von Riegen, Claus; Zhe Wu
Cc: Ian Bruce; dee schur; email@example.com; firstname.lastname@example.org; 'James Bryce Clark'; 'Tony Rogers'
Betreff: [uddi-ms] Gartner Application and WS Submit - Presentation by the OASIS UDDI Spec TC
To: Daniel Feygin (UnitSpace), Andrew Hately (IBM); Rob Kochman (Microsoft); Jamie Orchard (IBM); Claus von Riegen (SAP); Zhe Wu (Oracle);
Cc: Ian Bruce (Systinet), Dee Schur (OASIS), Jamie Clark (OASIS), UDDI Spec TC, UDDI Member Section
Please find below a synopsis of the abstract that I propose we submitted to Gartner (via Dee Schur) to secure a spot on the agenda for Gartner's Application and Web Services Summit in
on 17 November. Orlando
Visibility, reusability, adaptability and manageability are the essential requirements for SOA provided by a registry, yet UDDI, the standard for a SOA Registry, is poorly understood.
This presentation by members of the OASIS UDDI Specification Technical Committee will provide you with an introduction to the UDDI standard in the form of a tutorial describing the standard and its features; and describe common use cases such as design time and runtime discovery in support of enterprise needs for visibility and reuse of SOA components.
You will hear from enterprise users who have deployed UDDI as part of their SOA and which will share with you their experience. And finally, you will see UDDI in action through a demonstration by members of the UDDI Technical Committee incorporating multiple product offerings interoperating in the context of addressing an enterprise business scenario.
Action for To: addressees:
1) Please review this abstract and provide comment ASAP. As I explained I'm going on a short vacation and in my absence, Ian Bruce (Systinet) will coordinate necessary updates to the abstract. Ian will submit this abstract NO LATER THAN EST to Dee Schur. Let's avoid getting caught up on details.
2) Please start the process of canvassing customers to present
As I said, I would be happy to represent the TC and give the UDDI session which will be followed by 1-2 customer presentations - then onto the demo.
Time is of the essence wrt the demo, so I ask that each of you start submit ideas on what we should present on the demo. The first to submit should start a separate mail thread will all To: addressees on the thread and cc: the TC mailing list.
I think that Claus and Daniel already have something that we can use as a starting point. Please make your submission before Sunday - I will use this input to setup one or more calls to firm up our plans and come to consensus on the demo.
If you need to contact me, please do so on my cell: 425.941.0150.
.... Let's make this a success - let's keep this simple.
Luc ClémentCo-Chair OASIS UDDI Spec TCSystinet
--- Begin Message ---
Title: Proposal for UDDI interoperability demonstration at XML 2003
- From: "Von Riegen, Claus" <email@example.com>
- To: "'firstname.lastname@example.org'" <email@example.com>
- Date: Wed, 3 Sep 2003 11:13:13 +0200
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,
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.
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--- End Message ---