|dave...@bt.com||Feb 13, 2004 2:36 am|
|Paul M O'pella||Feb 13, 2004 5:41 am|
|dave...@bt.com||Feb 13, 2004 8:06 am|
|James Governor||Feb 13, 2004 8:20 am|
|dave...@bt.com||Feb 13, 2004 8:40 am|
|George Zagelow||Feb 13, 2004 8:53 am||.gif, .gif, .gif, 8 more|
|Young, Brian R||Feb 13, 2004 9:12 am|
|James Governor||Feb 13, 2004 9:30 am|
|George Zagelow||Feb 13, 2004 9:32 am|
|Bobbin Teegarden||Feb 13, 2004 10:56 am|
|Anne Thomas Manes||Feb 13, 2004 12:34 pm|
|Subject:||RE: [uddi-promo-discuss] Promotion of UDDI|
|From:||James Governor (jgov...@redmonk.com)|
|Date:||Feb 13, 2004 9:30:08 am|
I would recommend an excellent white paper about UDDI ebxml coexistence by Joe Chiusano of Booz Allen. He is an expert on the subject of registry coexistence and XML specification.
IBM and Microsoft have pushed the WS-I stack a little too hard. By that I mean IBM Web Services marketing which focuses on WSI, UDDI and BPEL as a remedy for every process management and integration issues, has been a little shortsighted, in my opinion. The fact is WS-I is still a lower order construct.
Ebxml is real (just look at Rosetta net and the excellent work by the Austalian public sector). But so is UDDI. As Brian says--if vendors want to see adoption its time to drive some reconciliation. This is not an either decision.
Its very interesting to me that some user organizations are in some cases doing both, without realizing it. Different teams in different contexts are using different approaches to integration.
-----Original Message----- From: Young, Brian R [mailto:bria...@BOEING.COM] Sent: Friday, February 13, 2004 5:23 PM To: uddi...@lists.oasis-open.org Subject: RE: [uddi-promo-discuss] Promotion of UDDI
ebXML Registry is an OASIS TC. This is one of the technologies that grew out of the joint OASIS / UN/CEFACT [United Nations Centre for Trade Facilitation and Electronic Business -- see http://en.wikipedia.org/wiki/UN/CEFACT and http://en.wikipedia.org/wiki/EbXML] effort several years ago.
An important issue for large international companies is seeking convergence or coexistence between UDDI and the ebXML Reg/Rep (Registry/Repository). Bottom line, we prefer to support one technology rather than two.
If you are going to promote UDDI, then it might be useful to develop a profile of current or potential users. Who is using UDDI? Who is using ebXML? Have you even heard of either technology? Are you using the technologies internally, externally or both? What product(s) are you using? Etc. I don't know how you might go about collecting this information, but it helps to "know the territory".
(Disclaimer: I am not entirely unbiased. My colleague Kathryn Breininger chairs the ebXML Registry TC).
Brian R. Young The Boeing Company (425) 865-5834 bria...@boeing.com DISCLAIMER: Any opinions expressed in this e-mail are my own and do not necessarily reflect the position of my company.
-----Original Message----- From: dave...@bt.com [mailto:dave...@bt.com] Sent: Friday, February 13, 2004 8:53 AM To: jgov...@redmonk.com; uddi...@lists.oasis-open.org Subject: RE: [uddi-promo-discuss] Promotion of UDDI
Sorry, I can't comment on that, as I know nothing about ebXML. I didn't even know such things as ebXML registries existed. We're in the
process of a large UDDI rollout, including an External one, initially targetted at ISPs as the first customers.
Dave Prout Web Services Integration Technical Architecture BT
-----Original Message----- From: James Governor [mailto:jgov...@redmonk.com] Sent: 13 February 2004 16:30 To: Prout,DA,Dave,XSJ67 PROUTDA R; uddi...@lists.oasis-open.org Subject: RE: [uddi-promo-discuss] Promotion of UDDI
Isn't a lot of the action "on the ground" happening around ebxml registries? At BT for example?
I think we need something on Vendor committment / support also.
UDDI V 3 Implementations seem very slow to appear. Vendors seem to have gone a little quiet on UDDI in the past year, which is probably why the take up by their customers is not really happening. As one of my colleagues just said, it is as if vendors have implemented it to get a 'tick in the box', but aren't really interested.
Dave Prout Web Services Integration Technical Architecture BT
-----Original Message----- From: Paul M O'pella [mailto:pope...@us.ibm.com] Sent: 13 February 2004 13:53 To: George Zagelow; uddi...@lists.oasis-open.org Subject: RE: [uddi-promo-discuss] Promotion of UDDI
I haven't seen any either, but thanks for the reminder to reply. If possible, I would like to see us try to cover the first three of George's suggestions at least initially, perhaps focusing on one or two depending on our success and the response:
* UDDI User Experiences * UDDI Best Practices * UDDI User Education
I believe publishing useful information about any or all of these three will automatically accomplish * UDDI promotion / evangelism
I think George's last item will be so much a part of these three as to preclude the need for it's being explicit * Usage of UDDI as a component of Web Services
I would add
* Usage of UDDI Internal Registries to facilitate reuse
"There is more to life than increasing its speed." -- Mahatma Gandhi
Paul M. O'Pella IBM Certified Consulting I/T Architect Global Services / EAI Certified MQSeries Specialist / Solutions Expert, MQSI Specialist, CrossWorlds Solutions Expert:, e-business Solutions Technologist pope...@us.ibm.com
To 02/13/2004 05:48 George Zagelow/Santa
Subject RE: [uddi-promo-discuss] Promotion of UDDI
I haven't seen any other messages since George's. Have I missed any ?
Dave Prout Web Services Integration Technical Architecture
+44 1442 296778
Greetings to the subscribers to our new discussion list. Let begin by welcoming you to the list, and by providing some background. When UDDI.org brought the early UDDI specifications to OASIS, we were looking for a flexible way to manage the further development of the spec. The OASIS Member Section structure was ideal, as it mapped very closely to the UDDI.org management structure we had in place, and gave us great flexibility in terms of managing as many different work efforts as we might need. The Member Section Steering Committee is now proposing that we do more to leverage the structure and to expand the family of those who have an interest in the success of UDDI. The Spec TC has done a superb job in progressing the spec. But, having a good spec isn't of much value if people don't know about it, or know how to use the technology. To that end, we are hopeful that this discussion list will allow us to zero in on at least one area of common interest, where we can start up a TC to work on some aspect of promoting UDDI. I gave some examples of areas we have discussed at the Steering Committee in the discussion list description:
* UDDI User Experiences * UDDI Best Practices * UDDI User Education * UDDI promotion / evangelism * Usage of UDDI as a component of Web Services
Some of this is pretty easy - pointers to exisiting customer references, or keeping current UDDI product descriptions out on UDDI.org. But, we could also go for a TC specifically focused on what users need. And, invite users to participate directly. We've purposely left the scope very broad, to see where we might get common interest. We'd be delighted to hear your thoughts, or answer any questions you might have. Thanks much.
Chair, OASIS UDDI Member Section Steering Committee Managing Director, UDDI Operators Council Web Services Strategy, IBM Software Group 1-408-463-4041 or 543-4041, FAX 3319 zage...@us.ibm.com