I support the modification proposed by
It still does not support the modelling of
asynchronous long running B2B collaborations in UDDI but perhaps that should be
the subject of a separate note such as “Using BPSS in a UDDI registry”?
I have not kept track of the WS-BPEL working group recently so don’t know
if they plan to support B2B collaborations in abstract BPEL or not. In the
meantime I’d be very interested to know if anyone else is interested in
modelling B2B collaborations in UDDI using something like ebXML BPSS as the
Axel Martens [mailto:email@example.com]
Sent: Friday, 3 December 2004 8:23
To: Luc Clement
Cc: Diane Jordan; 'James Bryce
Clark'; firstname.lastname@example.org; 'Mary McRae'; 'Tony Rogers';
Subject: RE: [wsbpel] "Using
BPEL4WS in a UDDI registry" OASIS UDDI Spec TC Technical Note - Review
had an internal reviewing process within IBM, and a
comment should have been sent to the UDDI TC.
the transmission did not happen. Hence, I send you the
of my group on the proposed technical note, attached to
email. As the core idea, we consider the explicit
of the partner link concept necessary. The document
the introduction of a partner link tModel, the adjustment
the queries and relations, and two additional queries. The
describes our reasons and design decisions illustrated by
Post Doc Researcher
Component Systems Group
IBM TJ Watson Research
Hawthorne, NY (USA)
Phone: (914) 784-7480
11/26/2004 08:46 AM
Diane Jordan/Raleigh/IBM@IBMUS, <email@example.com>
<firstname.lastname@example.org>, "'James Bryce Clark'"
<email@example.com>, "'Mary McRae'"
<firstname.lastname@example.org>, "'Tony Rogers'"
RE: [wsbpel] "Using BPEL4WS in a UDDI
registry" OASIS UDDI Spec TC Technical Note - Review Requested
Having provided sufficient time to review the
"Using BPEL4WS in a UDDI Registry" Technical Note it is the UDDI Spec
TC’s opinion this Technical Note is ready to be published. It is our
intent to publish this TN by the end of this calendar year. That said, should
you have additional feedback please provide it no later than 3 Dec so it may be
considered prior to the expected ratification of the TN by this TC in mid-Dec.
We understand that there may be unresolved issues relating
to the relevance of abstract processes as it relates to the WSBPEL
specification. We would like to draw your attention to the fact that the TN
applies to the BPEL4WS 1.1 specification submitted to the WSBPEL TC and which
defines the concept of abstract processes. The decision to map BPEL4WS 1.1 was
deliberate – the TN aims at addressing current market needs.
Senior Program Manager, Systinet
Co-Chair OASIS UDDI Spec TC
Tel: +1.617.768.4268 / Cell: +1.978.793.2162 / www.systinet.com
From: Luc Clement
Sent: Tuesday, August 03, 2004 20:59
To: email@example.com; firstname.lastname@example.org
Cc: email@example.com; firstname.lastname@example.org;
Karl F. Best; James Bryce Clark; Mary McRae; Tony Rogers
Subject: [wsbpel] "Using BPEL4WS in a UDDI registry" OASIS
UDDI Spec TC Technical Note - Review Requested
UDDI Spec TC has been working on a “Using BPEL4WS in a UDDI
registry” Technical Note (TN) that it would like your input on before
proceeding to ratify this TN.
TN provides a mapping for publishing BPEL4WS abstract processes into a UDDI
registry. The primary goals of mapping BPEL4WS artifacts to the UDDI model are
Enable the automatic registration
of BPEL4WS definitions in UDDI
Enable optimized and flexible UDDI
queries based on specific BPEL4WS artifacts and metadata
Provide composability with the
mapping described in the "Using WSDL in
a UDDI Registry, Version 2.0.2"  Technical Note.
would like to invite the BPEL TC to review and comment on the document and ask
that you assign two or more reviewers.
TN is posted at the following locations by format:
We would appreciate comments as soon as possible but
preferably before 31 Aug 04. Please submit comments:
Claus von Riegen, SAP (email@example.com),
(UDDI Chairs): firstname.lastname@example.org; email@example.com
Co-Chair OASIS UDDI Spec TC
OASIS UDDI Spec TC Technical Note: “Using WSDL in a UDDI Registry, Version