OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

bpel4people message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Proposed Errata - RE: [bpel4people] 4/24 BPEL4People TC - Draft Minutes


Find attached for the TC’s consideration a proposal based on Mark Ford’s recommendations [1]. Two files are attached:

 

1.     A text document describing the changes to the xsd, wsdl and specification

2.     A zip containing the modified xsd, wsdl and specification document

 

Luc Clément

Active Endpoints

 

[1] http://lists.oasis-open.org/archives/bpel4people/201203/msg00005.html

 

 

From: bpel4people@lists.oasis-open.org [mailto:bpel4people@lists.oasis-open.org] On Behalf Of Luc Clément
Sent: Monday, May 14, 2012 8:18 AM
To: Dave Ings; bpel4people@lists.oasis-open.org
Subject: RE: [bpel4people] 4/24 BPEL4People TC - Draft Minutes

 

Hello,

 

Mark Ford has asked me to take the lead on writing up proposals. I will aim to submit these to the TC within the next two weeks.

 

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, May 01, 2012 5:55 PM
To: bpel4people@lists.oasis-open.org
Subject: [bpel4people] 4/24 BPEL4People TC - Draft Minutes

 

(See attached file: BPEL4People TC Meeting Minutes 2012-04-24.pdf)

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

WS-HumanTask 1.1 Defects and Enhancements

Issue 1

Type:		Defect
Resource: 	ws-humantask-types.xsd
Description:	Missing enumerations in tTaskEventType:

			<xsd:enumeration value="deleteComment"/>
			<xsd:enumeration value="updateComment"/>
		
		Section ?4.11.1 Task Event Types and Data? lists task event types and data, but 
		the enumeration in the schema is missing deleteComment and updateComment.
		
Proposal:	Update ws-humantask-types.xsd (lines 376, 377) and doc (lines 2345, 2346, 4956, 4957)
		adding two enumeration elements


Issue 2
Type:		Enhancement
Resource:	ws-humantask-types.xsd
Description 	Suggest that two new tTaskEventType enumerations be added:

			<xsd:enumeration value="exited"/>
			<xsd:enumeration value="faulted"/>

		These two event types correspond to section ?8.1 Human Task Coordination
		Protocol Messages? and might be interesting event types to be part of the task
		history.
		

Proposal:		
		LC Notes - 
		- Added to xsd document (lines 389, 390) and the spec (2359, 2360, 4970, 4971)
		
			<xsd:enumeration value="exited"/>
			<xsd:enumeration value="failed"/>
			
		- ... but per tPredefinedStatus rather than use "faulted" I used "failed"
		- change "created" to "create" in the table at 4.11.1 (line 2295 - begining of table)
		- added exited and failed to 4.11.1  (line 2295 - end of table)
		- missing "cancel" (specified at 4.11.1) in the xsd; added in the xsd in file (line 391)
		  and spec (lines 2361, 4972)


Issue 3
Type: 		Defect
Resource:	ws-humantask-types.xsd
Description: 	Enumeration for deleteAttachment should be camel case. For example the

		schema currently defines:
			<xsd:enumeration value="deleteattachment"/>

		but should be
			<xsd:enumeration value="deleteAttachment"/>
			
Proposal:		

		LC Notes - done in xsd (line 373) and two places in the doc (lines 2343, 4954)
		
Issue 4

Type:		Defect
Resource:	ws-humantask-types.xsd
Description:	ComplexType tFaultData is a duplicate of tFault. I would prefer tFault over tFaultData 
		because tFault already defines child element faultData.
		
		Here is the definition of tFault:
		
		<xsd:complexType name="tFault">
			<xsd:sequence>
				<xsd:element name="faultName" type="xsd:NCName"/>
				<xsd:element name="faultData" type="xsd:anyType"/>
			</xsd:sequence>
		</xsd:complexType>
		
		And here is tFaultData:
		
		<xsd:complexType name="tFaultData">
			<xsd:sequence>
				<xsd:element name="faultName" type="xsd:NCName"/>
				<xsd:element name="faultData" type="xsd:anyType"/>
			</xsd:sequence>
		</xsd:complexType>
		
		
Proposal:		
		Removed tFaultData from xsd
		Replaced tFaultData reference in xsd (line 350) and spec (line 4929 ) to 
		tFault in tTaskInstanceData
		
		
Issue 5
		
Type:		Defect
Resource:	ws-humantask.xsd
Description:	Section ?4.4 Task Possible Outcomes? defines an element possibleOutcomes with
		child element of possibleOutcome, but neither complexType tPossibleOutcomes
		or child type tPossibleOutcome are defined in the schema. The following
		complexTypes need to be defined:
		
		<xsd:complexType name="tPossibleOutcomes">
			<xsd:complexContent>
				<xsd:extension base="tExtensibleElements">
					< xsd:sequence>
						<xsd:element name="possibleOutcome" type="tPossibleOutcome"
						maxOccurs="unbounded" />
					</xsd:sequence>
				</xsd:extension>
			</xsd:complexContent>
		</xsd:complexType>
		<xsd:complexType name="tPossibleOutcome">
			<xsd:complexContent>
				<xsd:extension base="tExtensibleElements">
					<xsd:sequence>
						<xsd:element name="outcomeName" type="tText"
						maxOccurs="unbounded" />
					</xsd:sequence>
				</xsd:extension>
			</xsd:complexContent>
		</xsd:complexType>	
		
Proposal:		
		Added to doc (lines 4073-4094) and schema (lines 368-398)
		
			  <!-- elements for task possible outcomes -->
			  <xsd:complexType name="tPossibleOutcomes">
			    <xsd:complexContent>
			      <xsd:extension base="tExtensibleElements">
				<xsd:sequence>
				  <xsd:element name="possibleOutcome" type="tPossibleOutcome" maxOccurs="unbounded" />
				</xsd:sequence>
			      </xsd:extension>
			    </xsd:complexContent>
			  </xsd:complexType>

			  <xsd:complexType name="tPossibleOutcome">
			    <xsd:complexContent>
			      <xsd:extension base="tExtensibleElements">
				<xsd:sequence>
				  <xsd:element name="outcomeName" type="tText" maxOccurs="unbounded" maxOccurs="unbounded" />
				</xsd:sequence>
			      </xsd:extension>
			    </xsd:complexContent>
			  </xsd:complexType>

Issue 6, 7, 8

Type:		Defect
Resource:	ws-humantask.xsd
Description:	Possible outcomes element missing from tTaskBase, tTask, tLeanTasks complexType.
		Need to add the following element to abstract complexType tTaskBase, tTask and tLeanTasks:
		
			<xsd:element name="possibleOutcomes" type="tPossibleOutcomes" minOccurs="0" />
			
Proposal:		
		Added to doc (lines 3971, 4007, 4318) and schema (lines 287, 314, 596)
			<xsd:element name="possibleOutcomes" type="tPossibleOutcomes" minOccurs="0" />	


Issue 9

Type:		Defect
Resource:	ws-humantask.xsd

Description:	Section ?4.6 Elements for Composite Tasks? illustrates an example of a subtask
		definition using toParts, e.g.
		
			<htd:subtask name="NCName">+
				( <htd:task>
					...
				</htd:task>
				| <htd:localTask reference="QName">
					standard-overriding-elements
					...
				</htd:localTask>
				)
				<htd:toParts>?
					<htd:toPart part="NCName" expressionLanguage="anyURI">+
						XPath expression
					</htd:toPart>
				</htd:toParts>
			</htd:subtask>

		but the schema as written does not support the toParts element.

		The current complexType definition:

			<xsd:complexType name="tSubtask">
				<xsd:complexContent>
					<xsd:extension base="tExtensibleElements">
						<xsd:choice>
							<xsd:element name="task" type="tTask" />
							<xsd:element name="localTask" type="tLocalTask" />
						</xsd:choice>
						<xsd:attribute name="name" type="xsd:NCName" use="required" />
					</xsd:extension>
				</xsd:complexContent>
			</xsd:complexType>
			
		should be changed to:
		
			<xsd:complexType name="tSubtask">
				<xsd:complexContent>
					<xsd:extension base="tExtensibleElements">
						<xsd:sequence>
							<xsd:choice>
								<xsd:element name="task" type="tTask"/>
								<xsd:element name="localTask" type="tLocalTask" />
							</xsd:choice>
							<xsd:element name="toParts" type="tToParts" minOccurs="0" />
						</xsd:sequence>
						<xsd:attribute name="name" type="xsd:NCName" use="required" />
					</xsd:extension>
				</xsd:complexContent>
			</xsd:complexType>

Proposal:
		updated xsd lines 561-567 and spec lines 4277-4283
		
Issue 10

Type:		Defect
Resource:	ws-humantask-api.wsdl

Description:	GetTaskHistoryResponse should be a collection of taskEvent and not
		tTaskEventType.

		Currently the schema defines complexType

		<xsd:element name="getTaskHistoryResponse">
			<xsd:complexType>
				<xsd:sequence>
					<xsd:element name="taskEvent" type="htt:tTaskEventType"
					minOccurs="0" maxOccurs="unbounded"/>
				</xsd:sequence>
			</xsd:complexType>
		</xsd:element>

		but it seems like it would be more correct to replace htt:tTaskEventType with a
		reference to element htt:taskEvent like so:

		<xsd:element name="getTaskHistoryResponse">
			<xsd:complexType>
				< xsd:sequence>
					<xsd:element ref=?taskEvent? minOccurs="0"
					maxOccurs="unbounded"/>
				</xsd:sequence>
			</xsd:complexType>
		</xsd:element>

		In addition, it might be more consistent to change the element definition
		taskEvent, which has an anonymous complexType, to a named complex type like
		tTaskEvent. This way the element in getTaskHistoryResponse can use a type
		rather than reference.	
		
Proposal:
		Updated wsdl lines 546 and spec lines xxx
		
		<xsd:element name="getTaskHistoryResponse">
		  <xsd:complexType>
		    < xsd:sequence>
		      <xsd:element name=?taskEvent? type="htt:tTaskEvent" 
		        minOccurs="0" maxOccurs="unbounded"/>
		    </xsd:sequence>
		  </xsd:complexType>
		</xsd:element>
		
		and made htt:tTaskEvent an explicit complex type in ws-humantask-types.xsd (line 394-423) 
		and spec (lines 2365-2403, 4983-5021)
		

Attachment: wsht-errata-1.zip
Description: wsht-errata-1.zip



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]