blob: cf5ce4c94be8f285de68460c06f3ef9855f8ddcb [file] [log] [blame]
<html>
<head>
<title>WTP PMC Minutes for October 25, 2005 Conference Call</title>
</head>
<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
<table border="0" cellpadding="2" cellspacing="5" width="100%">
<tbody><tr>
<td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b>
<font color="#ffffff" face="Arial,Helvetica">PMC Conference Call - October 25, 2005</font></b></td>
</tr>
</tbody></table>
<table border="0" cellpadding="2" cellspacing="5" width="100%">
<tbody><tr>
<td>
Attending:
Tim Wagner [TW],
Arthur Ryman [AR],
Raghunathan Srinivasan [RS],
Carl Trieloff (Invited to speak on SOA / WTP overlap),
Karl Reti (also on the STP PMC),
Christophe Ney [CN],
Jochen Krause [JK]
<!--PMC MEMBERS NOT PRESENT ON THIS CALL:
Naci Dai [ND],
David Williams [DW],
Lawrence Mandel [LM],
-->
<h1>WTP PMC Minutes for October 25, 2005 Conference Call</h1>
<h2>WTP / SOA Discussion [Carl Trieloff] </h2>
<ul>
<li>Carl provided a brief overview of the SOA project, its status, and the proposal scope.
<li>Additional subprojects being added to incorporate more services, some of which are driven
by others joining the project. Expect to start working in mid-November.
<li>Some preliminary notes on surface area with WTP:
<ul>
<li>WSDL and XML Schema are used for contract design within STP; editing and validation would
be used directly. Validation extensions are needed, and would work within the existing
WTP validation framework (the extensions themselves would likely live in STP).
<li>WSDL code generation; framework belongs in WTP, extensions depend on the genericity
of their application.
<li>WS-Security is within the scope of WTP, but currently unresourced. Other WS-*
standards are similar. SOA network level security is not necessarily representative
of WS-Security, and that modeling/tooling would reside in STP.
<li>J2EE deployment is one deployment extension point for STP; this would exploit
existing WTP extension points.
<li>Extension to TCP/IP monitoring to provide SOAP message monitoring (WSDL-aware
viewing of the traffic.)
<li>Code generation framework - unclear on exactly how the breakdown would go, although
Iona has some code they may be contributing in this area.
</ul>
<li>Should cross pollinate at the architecture group level (will connect with David).
</ul>
<h2>Procedural </h2>
<ul>
<li>IP log begun; will need to spend time on this over the next two weeks to get ready for the 1.0
release view.
<li>Speaking of which...we need to schedule the WTP 1.0 release review.
<li>Need to follow up with John Graham on WTP/DTP migration plans for RDB APIs. Setting up call with
Arthur and John to discuss this further.
<li>WTP charter modifications accepted in last week's Board review; will post updated version
to website and notify EMO.
</ul>
<!--
<h2>Requirements Update </h2>
<ul>
<li>
</ul>
<h2>Architecture Update </h2>
<ul>
<li>
</ul>
<h2>1.0 Status </h2>
<ul>
<li>Plugin version numbers need to be bumped to 1.0?
<li>How did I-Build timing work out this week?
<li>New feature breakdown complete for WST?
</ul>
<h2>JSF Status </h2>
<ul>
<li>
</ul>
-->
<h2>Action Items</h2>
<ul>
<li>[TW, etc.] Continue work on IP log.
<li>[TW] Release review the week of 11/14 scheduled.
<li>[TW] Post new WTP Charter to Website and notify EMO.
<li>[TW] Need release train planning document - push Planning Council to produce this (email sent; tracking
status).
</ul>
<small>Minutes taken by Tim Wagner, October 25, 2005</small>
</tr>
</tbody></table>
</html>