New issue: Partner Relationships

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

========
new issue: Partner Relationships

Background: During the May 2006 F2F there was discussion surrounding 
partner links, EPR, etc.  A question was raised and later clarified that 
resulted in this editorial issue and proposed resolution to further 
specify that the semantic relationship or pairing of portTypes, EPR and 
partner links is outside of the specification.

reference: 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 (changes in UPPER CASE):

    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. WS-BPEL DOES NOT
    SPECIFY WHETHER THESE ROLES ARE RELATED, BY CALLBACK OR OTHERWISE
    (SUCH AS THE SEMANTIC RELEVANCE OF THEIR PAIRING).