Issue - R37 - Wrong namespace for ServiceRefType in example

[ws-bpel issues list editor<peter@furniss.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 - R37 - Wrong namespace for ServiceRefType in example

Status: received
Date added: 9 Nov 2006
Date submitted: 08 November 2006
Submitter: Thomas Schulze
Description: On page 184, section 15.4.1, line 37 and on page 185,
section 15.4.1, line 2 and line 16, the referenced type "ServiceRefType"
is prefixed with "bpel:" which is bound to namespace "
http://docs.oasis-open.org/wsbpel/2.0/process/executable" in this
example. But the type "ServiceRefType" is defined in the namespace "
http://docs.oasis-open.org/wsbpel/2.0/serviceref".
Submitter's proposal: Introduce for this example a new prefix "sref" and bind it to
namespace "http://docs.oasis-open.org/wsbpel/2.0/serviceref". Use this
new prefix for all three occurrences of the referenced type
"ServiceRefType".
Changes: 9 Nov 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 - R37 - [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 - R37 - Proposed resolution", without any Re: or similar.

To add a new issue, see the issues procedures document