Begin forwarded message:


<excerpt><bold><color><param>0000,0000,0000</param>From:
</color></bold>Steve Ross-Talbot <<steve@enigmatec.net>

<bold><color><param>0000,0000,0000</param>Date: </color></bold>26
November 2004 20:05:10 GMT

<bold><color><param>0000,0000,0000</param>To: </color></bold>"Luc
Clement" <<luc.clement@systinet.com>

<bold><color><param>0000,0000,0000</param>Cc:
</color></bold><<uddi-spec@lists.oasis-open.org>, "'James Bryce
Clark'" <<jamie.clark@oasis-open.org>, <<jevdemon@microsoft.com>,
<<wsbpel@lists.oasis-open.org>, <<drj@us.ibm.com>, "'Mary McRae'"
<<mary.mcrae@oasis-open.org>, "'Tony Rogers'" <<Tony.Rogers@ca.com>

<bold><color><param>0000,0000,0000</param>Subject: </color>Re:
[wsbpel] "Using BPEL4WS in a UDDI registry" OASIS UDDI Spec TC
Technical Note - Review Requested

</bold>

All:


Perhaps given the maturity of the Choreography working group it might
be a good idea to think about "Using CDL in a UDDI registry" I suspect
it will have a number of practical benefits and will certainly catch
the eye of many large users of this technology. Anyone out there
thought about this other than little ol' me?


Cheers


Steve T


On 26 Nov 2004, at 13:46, Luc Clement wrote:


<excerpt><fontfamily><param>Tahoma</param><color><param>0000,0000,807F</param><smaller>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.</smaller></color></fontfamily>


<fontfamily><param>Tahoma</param><color><param>0000,0000,807F</param><smaller>
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.</smaller></color></fontfamily>


 

<fontfamily><param>Arial</param><color><param>0000,0000,807F</param><smaller>Luc
Clément</smaller></color></fontfamily>

<color><param>0000,0000,807F</param><smaller><x-tad-smaller>Senior
Program Manager, Systinet</x-tad-smaller></smaller></color></excerpt></excerpt><excerpt><excerpt>


<color><param>0000,0000,807F</param><smaller><x-tad-smaller>Co-Chair
OASIS UDDI Spec TC</x-tad-smaller></smaller></color></excerpt></excerpt><excerpt><excerpt>


<color><param>0000,0000,807F</param><smaller><x-tad-smaller>Tel:
+1.617.768.4268 / Cell: +1.978.793.2162 / www.systinet.com</x-tad-smaller></smaller></color></excerpt></excerpt><excerpt><excerpt>




<bold><fontfamily><param>Tahoma</param><smaller>From:</smaller></fontfamily></bold><fontfamily><param>Tahoma</param><smaller>
Luc Clement [mailto:luc.clement@systinet.com]</smaller></fontfamily>

<fontfamily><param>Tahoma</param><smaller> <bold>Sent:</bold> Tuesday,
August 03, 2004 20:59</smaller></fontfamily>

<bold><fontfamily><param>Tahoma</param><smaller>To:</smaller></fontfamily></bold><fontfamily><param>Tahoma</param><smaller>
drj@us.ibm.com; jevdemon@microsoft.com</smaller></fontfamily>

<bold><fontfamily><param>Tahoma</param><smaller>Cc:</smaller></fontfamily></bold><fontfamily><param>Tahoma</param><smaller>
uddi-spec@lists.oasis-open.org; wsbpel@lists.oasis-open.org; Karl F.
Best; James Bryce Clark; Mary McRae; Tony Rogers</smaller></fontfamily>

<bold><fontfamily><param>Tahoma</param><smaller>Subject:</smaller></fontfamily></bold><fontfamily><param>Tahoma</param><smaller>
[wsbpel] "Using BPEL4WS in a UDDI registry" OASIS UDDI Spec TC
Technical Note - Review Requested</smaller></fontfamily>



<fontfamily><param>Georgia</param><smaller>Dear WSBPEL Chairs,</smaller></fontfamily>


<fontfamily><param>Georgia</param><smaller>The 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.</smaller></fontfamily>


<fontfamily><param>Georgia</param><smaller>The 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 to:</smaller></fontfamily>

	1.  	<fontfamily><param>Georgia</param><smaller>Enable the automatic
registration of BPEL4WS definitions in UDDI</smaller></fontfamily> 

	2.  	<fontfamily><param>Georgia</param><smaller>Enable optimized and
flexible UDDI queries based on specific BPEL4WS artifacts and
metadata</smaller></fontfamily> 

	3.  	<fontfamily><param>Georgia</param><smaller>Provide composability
with the mapping described in the <italic>"Using WSDL in a UDDI
Registry, Version 2.0.2"</italic> [1] Technical Note.</smaller></fontfamily>


<fontfamily><param>Georgia</param><smaller>We would like to invite the
BPEL TC to review and comment on the document and ask that you assign
two or more reviewers.</smaller></fontfamily>


<fontfamily><param>Georgia</param><smaller> The TN is posted at the
following locations by format:</smaller></fontfamily>

	• 	<fontfamily><param>Georgia</param><smaller>PDF:
<color><param>0000,0000,EEED</param>http://www.oasis-open.org/apps/org/workgroup/uddi-spec/download.php/8442/uddi-spec-tc-tn-bpel-20040725.pdf</color></smaller></fontfamily> 

	• 	<fontfamily><param>Georgia</param><smaller>MSWord:
<color><param>0000,0000,EEED</param>http://www.oasis-open.org/apps/org/workgroup/uddi-spec/download.php/8441/uddi-spec-tc-tn-bpel-20040725.doc</color> </smaller></fontfamily>


<fontfamily><param>Georgia</param><smaller>We would appreciate
comments as soon as possible but preferably before 31 Aug 04.
Please submit comments:</smaller></fontfamily>


<fontfamily><param>Georgia</param><smaller>To: Claus von Riegen, SAP
(<color><param>0000,0000,EEED</param>claus.von.riegen@sap.com</color>),</smaller></fontfamily>


<fontfamily><param>Georgia</param><smaller> cc: (UDDI Chairs):
<color><param>0000,0000,EEED</param>luc.clement@systinet.com</color>;
<color><param>0000,0000,EEED</param>tony.rogers@ca.com</color></smaller></fontfamily>


<fontfamily><param>Georgia</param><smaller>cc:
<color><param>0000,0000,EEED</param>uddi-spec@lists.oasis-open.org</color></smaller></fontfamily>


<fontfamily><param>Georgia</param><smaller>Thanks in advance</smaller></fontfamily>


<fontfamily><param>Georgia</param><smaller>Luc
Clément                       </smaller></fontfamily>

<fontfamily><param>Georgia</param><smaller>
</smaller></fontfamily><smaller><x-tad-smaller>Co-Chair OASIS UDDI
Spec TC</x-tad-smaller></smaller></excerpt></excerpt><excerpt><excerpt>


<smaller><x-tad-smaller>Systinet Corporation</x-tad-smaller></smaller></excerpt></excerpt><excerpt><excerpt>


<smaller><x-tad-smaller>Tel: +1.617.395.6798</x-tad-smaller></smaller></excerpt></excerpt><excerpt><excerpt>


<smaller> </smaller>


<smaller> </smaller>



<fontfamily><param>Georgia</param><smaller>[1]  OASIS UDDI Spec TC
Technical Note: “Using WSDL in a UDDI Registry, Version 2.0.2”,
<color><param>0000,0000,EEED</param>http://www.oasis-open.org/committees/uddi-spec/doc/tns.htm#WSDLTNV2</color> </smaller></fontfamily>

</excerpt></excerpt>