Issue - 298 - Partner Relationships

[ws-bpel issues list editor <peter.furniss@erebor.co.uk>]

This issue has been added to the wsbpel issue list with a status of "received". The status will be changed to "open" if a motion to open the issue is proposed and that motion is approved by the TC. A motion could also be proposed to close it without further consideration. Otherwise it will remain as "received".

The issues list is posted as a Technical Committee document to the OASIS WSBPEL TC pages on a regular basis. The current edition, as a TC document, is the most recent version of the document entitled in the "Issues" folder of the WSBPEL TC document list - the next posting as a TC document will include this issue. The list editor's working copy, which will normally include an issue when it is announced, is available at this constant URL.

Issue - 298 - Partner Relationships

Status: received
Date added: 10 Jun 2006
Date submitted: 09 June 2006
Submitter: Monica J. Martin
Description: 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.
Submitter's proposal: 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 (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).

Changes: 10 Jun 2006 - new issue

---

To comment on this issue (including whether it should be accepted), please follow-up to this announcement on the wsbpel@lists.oasis-open.org list (replying to this message should automatically send your message to that list), or ensure the subject line as you send it starts "Issue - 298 - [anything]" or is a reply to such a message. If you want to formally propose a resolution to an open issue, please start the subject line "Issue - 298 - Proposed resolution", without any Re: or similar.

To add a new issue, see the issues procedures document (but the address for new issue submission is the sender of this announcement).