FW: UDDI Change Request

["MACIAS, Paul" <PMACIAS@lmi.org>]

FYI, I've sent Joe's latest proposed text to the UDDI Spec listserve for consideration for tomorrow's UDDI discussion on the TN.

-Paul

-----Original Message-----
From: MACIAS, Paul 
Sent: Monday, July 07, 2003 3:45 PM
To: 'uddi-spec@lists.oasis-open.org'
Subject: UDDI Change Request


FYI.  Below is a revised proposal for a text change put forth for the AR discussion on the "UDDI as the registry for ebXML components" TN.

Regards,

Paul Macias

-----Original Message-----
From: Chiusano Joseph [mailto:chiusano_joseph@bah.com]
Sent: Monday, July 07, 2003 3:05 PM
To: regrep@lists.oasis-open.org
Subject: [regrep] UDDI Change Request


Anne or Paul,

Below is the text of our change request. Can you please forward this
request to the UDDI TC? Thanks so much.

CHANGE REQUEST:

On behalf of the OASIS/ebXML Registry TC, I would like to request the
following changes to the stated paragraphs in the UDDI Technical Note
titled "UDDI as the registry for ebXML components", Document Identifier
"uddi-spec-tc-tn-uddi-ebxml-20030508". The paragraphs occur under the
heading "1.1 Problem statement":

<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. UDDI
can play a major role in enabling trading partners and their Web
services and ebXML infrastructures to interact using UDDI as a common
registry. This is the focus of this Technical Note.

In addition to being a universal technology for publication and
discovery of service metadata, UDDI also enables discovery of ebXML
framework components such as Collaboration Protocol Profile and Business
Process Specification Schema. This capability can help enable
interoperability among trading partners that use UDDI and ebXML
framework components. However, a prescribed methodology of modeling
services and components which are conformant to ebXML specifications is
required to make interoperable solutions possible. 
</ProposedParagraphs>

Thank you for your consideration of this proposed change.

Kind Regards,
Joe Chiusano

winmail.dat