Two New Issues: RE: WSHT CD-11 - RE: [bpel4people] 6/12 BPEL4People TC - Draft Minutes

[Luc Clément <luc.clement@activevos.com>]

In reviewing the spec further we identified two issues: (new Issue 11) error in maxOccurs for the rendering element, and (new Issue 12) the ws-humantask-api.wsdl does not validate because 'tBatchResponse' has no namespace

 

Issue 11 - Rendering element is erroneously bounded to a max of 1 any element

 

Type:         Defect

Resource:     Specification, syntax description in section 4.5

Description: 

'4.5 Elements for Rendering Tasks' states that the rendering element is bounded to a max of 1 any element, but in the schema the rendering element allows an unbounded collection of Any’s. This is corroborated by Line 1386: “One or more rendering methods can be provided in a task definition or a notification definition.”

Line 1399: Syntax:

<htd:renderings>

  <htd:rendering type="QName">+

    <xsd:any minOccurs="1" maxOccurs="1" />

  </htd:rendering>

</htd:renderings>

 

             

Proposal: change maxOccurs="1" to maxOccurs="unbounded" in the syntax section (line 1399) in the spec

 

 

 

Issue 12

 

Type:         Defect

Resource:     ws-humantask-api.wsdl

Description:  ws-humantask-api.wsdl does not validate because 'tBatchResponse' has no namespace declared

             

Proposal:     At line 17 of the ws-humantask-api.wsdl

 

<xsd:schema

      targetNamespace="http://docs.oasis-open.org/ns/bpel4people/ws-humantask/api/200803"

      xmlns:xsd="http://www.w3.org/2001/XMLSchema"

      xmlns:htt="http://docs.oasis-open.org/ns/bpel4people/ws-humantask/types/200803"

      elementFormDefault="qualified"

      blockDefault="#all">

 

..needs to change in one of the following ways:

 

1. Option 1 - declare a default namespace such as xmlns=http://docs.oasis-open.org/ns/bpel4people/ws-humantask/api/200803 as follows:

 

<xsd:schema

      targetNamespace="http://docs.oasis-open.org/ns/bpel4people/ws-humantask/api/200803"

      xmlns="http://docs.oasis-open.org/ns/bpel4people/ws-humantask/api/200803"

      xmlns:xsd="http://www.w3.org/2001/XMLSchema"

      xmlns:htt="http://docs.oasis-open.org/ns/bpel4people/ws-humantask/types/200803"

      elementFormDefault="qualified"

      blockDefault="#all">

 

2. Option 2 - preferably map a prefix to the "http://docs.oasis-open.org/ns/bpel4people/ws-humantask/api/200803" namespace and prefix all the tBatchResponse references:

 

<xsd:element name="batchResponse" type="ns:tBatchResponse" minOccurs="0" maxOccurs="unbounded"/>

 

instead of

 

<xsd:element name="batchResponse" type="tBatchResponse" minOccurs="0" maxOccurs="unbounded"/>

 

 

 

 

From: Luc Clément
Sent: Thursday, June 14, 2012 8:58 PM
To: 'Dave Ings'; bpel4people@lists.oasis-open.org
Subject: WSHT CD-11 - RE: [bpel4people] 6/12 BPEL4People TC - Draft Minutes

 

The changes we agreed to during the 20120616 meeting have been made. Issue 2 remained open at the end of the meeting.

 

I reviewed the initial proposal and realized that the introduction of two additional tTaskEventType enumerations, namely:

 

                                    <xsd:enumeration value="exited"/>

                                    <xsd:enumeration value="faulted"/>

 

… was not required or warranted. This enumeration is specifically meant for task *event* types. The additions of “exited” and “faulted” are states and not events. Thus, I removed these additions to the ws-humantask-types schema and document.

 

Find attached WSHT-CD11 for consideration.

 

Regards

Luc

 

Luc Clément

Active Endpoints

 

From: bpel4people@lists.oasis-open.org [mailto:bpel4people@lists.oasis-open.org] On Behalf Of Dave Ings
Sent: Tuesday, June 12, 2012 12:01 PM
To: bpel4people@lists.oasis-open.org
Subject: [bpel4people] 6/12 BPEL4People TC - Draft Minutes

 

(See attached file: BPEL4People TC Meeting Minutes 2012-06-12.pdf)

Regards, Dave Ings,
Emerging Software Standards
Email: ings@ca.ibm.com
Yahoo Messenger: dave_ings