Subject: Re: [uddi-spec] Fw: [regrep] UDDI as the registry for ebXML components: Typo?
I will request the TC to submit a formal request. I think they'll be happy to oblige. Paul Macias noted to the team that he had tried repeatedly (to no avail) to get the team to review the document and help with some basic issues. I think now they are willing to get engaged. Anne ----- Original Message ----- From: "Tom Bellwood" <firstname.lastname@example.org> To: "Anne Thomas Manes" <email@example.com> Cc: "Uddi-Spec" <firstname.lastname@example.org> Sent: Wednesday, July 02, 2003 4:42 PM Subject: Re: [uddi-spec] Fw: [regrep] UDDI as the registry for ebXML components: Typo? > > > > > Hi Anne, > > Thank you for pursuing this discussion. While I don't object to the > proposed changes, I think we need an official statement from their TC > requesting us to make such changes. Can we get that? > > Luc is also trying to pursue getting acceptable Namespace and URI data from > them. Have your conversations touched on that topic? > > Please try to make the Tues. 7/8 meeting and I'll add this topic to the > agenda. > > Thanks, > Tom Bellwood Phone: (512) 838-9957 (external); TL: 678/9957 > (internal) > Co-Chair, OASIS UDDI Specification TC > > > "Anne Thomas Manes" <email@example.com> on 07/02/2003 11:34:45 AM > > To: "Uddi-Spec" <firstname.lastname@example.org> > cc: > Subject: [uddi-spec] Fw: [regrep] UDDI as the registry for ebXML > components: Typo? > > > > FYI: > > I've been having a lengthy discussion with the regrep TC regarding the > Registering ebXML in UDDI TN. They have some concern with the phrasing of > the problem statement -- particularly the implication that using ebXML > imposes significant increased cost and management. Here is some proposed > rewording. > > Anne > > ----- Original Message ----- > From: "Chiusano Joseph" <email@example.com> > To: "Anne Thomas Manes" <firstname.lastname@example.org> > Cc: <email@example.com>; <firstname.lastname@example.org> > Sent: Wednesday, July 02, 2003 12:20 PM > Subject: Re: [regrep] UDDI as the registry for ebXML components: Typo? > > > > <Quote> > > I'm still having trouble understanding what can be easily > > misinterpreted. Can you perhaps propose some alternate wording? Is it as > > simple as just saying "ebXML services and Web services" rather than > > "ebXML and Web services"? > > > > Just trying to understand the problem... > > </Quote> > > > > Thanks Anne. I appreciate your working with us, and I know you and the > > other UDDI folks have nothing but good intentions. I've already made a > > motion to have our TC chair vet this with the UDDI TC chairs (with no > > opposition from our TC so far), but for what it's worth here's how I > > would change the phrase - but I'll start with the current version of the > > first and second paragraphs on p.3 of the TN under "1.1 Problem > > Statement", so that the context is clear: > > > > <CurrentParagraphs> > > Multiple consortia have initiated pilot projects using the ebXML > > framework for business-to-business transactions, while corporations have > > also begun adopting ebXML technologies for internal use. At the same > > time Web service technologies, which have significant momentum due to > > unprecedented industry support, are also being rolled out. This > > introduces significant concerns of cost and manageability, because ebXML > > and Web services impose separate infrastructure requirements and > > platform components. > > > > As a universal technology for publication and discovery of service > > metadata, UDDI allows the bridging of the two infrastructures by > > accommodating metadata registrations for Web services as well as ebXML > > framework components, enabling interoperability among trading partners > > using ebXML or Web services. However, a prescribed methodology of > > modeling services and components which are conformant to ebXML > > specifications is required to make interoperable solutions possible. > > </CurrentParagraphs> > > > > <ProposedParagraphs> > > Multiple consortia have initiated pilot projects using the ebXML > > framework for business-to-business transactions, while corporations have > > also begun adopting ebXML technologies for internal use. At the same > > time Web service technologies, which have significant momentum due to > > unprecedented industry support, are also being rolled out. There may be > > situations in which a UDDI user may wish to access ebXML framework > > components that are registered in an ebXML registry. This Technical Note > > provides guidance on how to handle such scenarios. > > > > In addition to being a universal technology for publication and > > discovery of service metadata, the fact that UDDI also enables discovery > > ebXML framework components can help enable interoperability among > > trading partners that use UDDI and ebXML registry. However, a prescribed > > methodology of modeling services and components which are conformant to > > ebXML specifications is required to make interoperable solutions > > possible. > > </ProposedParagraphs> > > > > Thanks, > > Joe > > > <TAB>..... rest of the attachment deleted for brevity.... </TAB> >