Issue - 298 - Proposal to Vote

["Monica J. Martin" <Monica.Martin@Sun.COM>]

Updated proposal as a result of offline discussions with Yiu, Koenig, 
vanderRijn, Ten-Hove and Martin.

Change from:
In Section 6.2 Change from:

   The partnerLink declarations specify the relationships that a
   WS-BPEL process will employ in its behavior. In order to utilize
   operations via a partnerLink, the binding and communication data,
   including endpoint references (EPR), for the partnerLink must be
   available (see also **Link**). The relevant information about a
   partnerLink can be set as part of business process deployment. This
   is outside the scope of the WS-BPEL specification.

Change to (add last four sentences):
   The partnerLink declarations specify the relationships that a
   WS-BPEL process will employ in its behavior. In order to utilize
   operations via a partnerLink, the binding and communication data,
   including endpoint references (EPR), for the partnerLink must be
   available (see also *Link*). The relevant information about a
   partnerLink can be set as part of business process deployment. This
   is outside the scope of the WS-BPEL specification.  Partner link
   types establish a relationship between WSDL port types of two Web
   services. The purpose of partner link types is to keep this
   relationship clear within the process, and make processes
   with more than one partner easier to understand. No other syntactic 
or semantic
   relationships are implied by partner link types in this specification.

Issue reference: 
http://www.oasis-open.org/apps/org/workgroup/wsbpel/email/archives/200606/msg00086.html