Issue - 129 - Inconsistent Name Attribute Usage in PartnerLinkType

[ws-bpel issues list editor<peter.furniss@choreology.com>]

This issue has been added to the wsbpel issue list. 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 - 129 - Inconsistent Name Attribute Usage in PartnerLinkType

Status: open
Categories: Syntax and validation
Date added: 14 Jun 2004
Submitter: Yuzo Fujishima
Date submitted: 14 June 2004
Champion: Yuzo Fujishima
Document: WSBPEL Working Draft, April 23, 2004
Description: Currently, the "name" atttribute of a "portType" element is used within a "role" element within a "partnerLinkType" element to specify a port type associated with the role.

All other "name" attributes in the WSBPEL specificaiton are used to define the name of the object defined there, not the object referenced. Accordingly, all other "name"s are NCName where only the above portType name is QName.

<plnk:partnerLinkType name="ncname">
  <plnk:role name="ncname">+
    <plnk:portType name="qname"/>
  </plnk:role>
</plnk:partnerLinkType>

Submitter's proposal: Replace "portType" element with the newly introduced "responsibility" element that has "portType" attribute.
<plnk:partnerLinkType name="ncname">
  <plnk:role name="ncname">+
    <plnk:responsibility portType="qname"/>
  </plnk:role>
</plnk:partnerLinkType>

Changes: 14 Jun 2004 - new issue

---

To comment on this issue, 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 - 129 - [anything]" or is a reply to such a message. If you want to formally propose a resolution, please start the subject line "Issue - 129 - 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).