[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [bpel4people-editors] BP-44
Hi Mike, I looked at the BP-44 resolution (introduction of
getTaskOperations) and would like to propose modifications of this
resolution - hopefully this is acceptable as an editing task.
(0) ws-humantask-1.1-spec.doc
I noticed that all changes were accepted before applying BP-44 - this will
make it difficult to look at any changes made after CD 02, i.e., revisions
1 and 2. I think these changes should only be accepted after a vote by the
TC.
(1) ws-humantask-api.wsdl
All existing API operations have:
(a) input and output doc/lit wrapper element definitions (getTaskOperations
and getTaskOperationsResponse) in the WSDL <types> section
(b) input and output message definitions
(c) the operation definition itself
I noticed that (a) is missing - unfortunately XML schema validators do not
get this - add a definition like this:
<xsd:element name="getTaskOperations)">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="identifier" type="xsd:anyURI" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<:xsd:element name="getTaskOperationsResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="taskOperations" type="htt:tTaskOperations" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
Note that the complex type definitions used by API operations are all in
the ws-humantask-types.xsd - therefore the namespace prefix "htt:" (see
also (2) and (3) below).
(2) ws-humantask.xsd
The element taskOperations does not have to be added to the tTask complex
type here - tTask is an element of the WS-HT human task **definition
language** - no change of this artifact is required.
(3) ws-humantask-types.xsd
This is the right place for the new data type tTaskOperations.
The tTaskDetails element also contains a new taskOperations element of type
tTaskOperations. Note that tTaskDetails used to be called tTask as well -
in a different namespace, however, it lead to confusion (potentially here
as well) - this naming problem has been resolved by BP-61.
Also note the following **additional** modifications:
(a) in the tTaskOperations element, I added maxOccurs="unbounded" to the
<choice> - elements of this type contain the list of operations - it is
used in the API and in two more places - see also (d) below
(b) in the tTaskOperations element, I renamed getTaskInfo to getTaskDetails
(again, following BP-61)
(c) I modified the tTaskOperation type definition in order to let the
operation elements have empty content (instead of string content), e.g.
<claim/>
(d) finally, as this would be the first time where the Task Details
(tTaskDetails) contain a field which is not also available via the advanced
query (tTaskQueryResultSet) - therefore, I propose that the new
taskOperations element is also added to that superset of queryable task
properties
<!-- task operations -->
<xsd:complexType name="tTaskOperations">
<xsd:choice maxOccurs="unbounded">
<xsd:element name="claim" type="tTaskOperation" />
<xsd:element name="start" type="tTaskOperation" />
<xsd:element name="stop" type="tTaskOperation" />
<xsd:element name="release" type="tTaskOperation" />
<xsd:element name="suspend" type="tTaskOperation" />
<xsd:element name="suspendUntil" type="tTaskOperation" />
<xsd:element name="resume" type="tTaskOperation" />
<xsd:element name="complete" type="tTaskOperation" />
<xsd:element name="remove" type="tTaskOperation" />
<xsd:element name="fail" type="tTaskOperation" />
<xsd:element name="setPriority" type="tTaskOperation" />
<xsd:element name="addAttachment" type="tTaskOperation" />
<xsd:element name="getAttachmentInfos" type="tTaskOperation" />
<xsd:element name="getAttachments" type="tTaskOperation" />
<xsd:element name="deleteAttachments" type="tTaskOperation" />
<xsd:element name="addComment" type="tTaskOperation" />
<xsd:element name="getComments" type="tTaskOperation" />
<xsd:element name="skip" type="tTaskOperation" />
<xsd:element name="forward" type="tTaskOperation" />
<xsd:element name="delegate" type="tTaskOperation" />
<xsd:element name="getRendering" type="tTaskOperation" />
<xsd:element name="getRenderingTypes" type="tTaskOperation" />
<xsd:element name="getTaskDetails" type="tTaskOperation" />
<xsd:element name="getTaskDescription" type="tTaskOperation" />
<xsd:element name="setOutput" type="tTaskOperation" />
<xsd:element name="deleteOutput" type="tTaskOperation" />
<xsd:element name="setFault" type="tTaskOperation" />
<xsd:element name="deleteFault" type="tTaskOperation" />
<xsd:element name="getInput" type="tTaskOperation" />
<xsd:element name="getOutput" type="tTaskOperation" />
<xsd:element name="getFault" type="tTaskOperation" />
<xsd:element name="activate" type="tTaskOperation" />
<xsd:element name="nominate" type="tTaskOperation" />
<xsd:element name="setGenericHumanRole" type="tTaskOperation" />
<xsd:any namespace="##other" processContents="lax" />
</xsd:choice>
</xsd:complexType>
<xsd:complexType name="tTaskOperation">
<xsd:complexContent>
<xsd:restriction base="xsd:anyType"/>:
</xsd:complexContent>
</xsd:complexType>
and:
<xsd:element name="taskDetails" type="tTaskDetails" />
<xsd:complexType name="tTaskDetails">
<xsd:sequence>
...
<xsd:element name="taskOperations" type="tTaskOperations" minOccurs="
0" />
<xsd:any namespace="##other" processContents="lax" minOccurs="0"
maxOccurs="unbounded" />
</xsd:sequence>
</xsd:complexType>
and:
<xsd:complexType name="tTaskQueryResultRow">
<xsd:choice minOccurs="0" maxOccurs="unbounded">
...
<xsd:element name="taskOperations" type="tTaskOperations" />
<xsd:any namespace="##other" processContents="lax" />
</xsd:choice>
</xsd:complexType>
In order to simplify this change, please find attached the three XML Schema
artifacts with the above changes, based on SVN revision 96.
(See attached file: ws-humantask-api.wsdl)(See attached file:
ws-humantask.xsd)(See attached file: ws-humantask-types.xsd)
Kind Regards
Dieter König
Senior Technical Staff Member, WebSphere Process Server Architect
IBM Software Group, Application and Integration Middleware Software
WSS Business Process Solutions
Phone: +49-7031-16-3426 IBM Deutschland (Embedded
image moved
to file:
pic30517.gif)
E-Mail: dieterkoenig@de.ibm.com Schönaicher Str. 220
71032 Böblingen
Germany
IBM Deutschland
Research &
Development
GmbH /
Vorsitzender des
Aufsichtsrats:
Martin Jetter
Geschäftsführung:
Erich Baier
Sitz der
Gesellschaft:
Böblingen /
Registergericht:
Amtsgericht
Stuttgart, HRB
243294
From: Michael Rowley <michael.rowley@activevos.com>
To: Ralf Mueller <ralf.mueller@oracle.com>, Luc Clément <luc.clement@activevos.com>
Cc: Dieter Koenig1/Germany/IBM@IBMDE, "bpel4people-editors@lists.oasis-open.org"
<bpel4people-editors@lists.oasis-open.org>
Date: 27.02.2009 19:43
Subject: RE: [bpel4people-editors] Done with 20, 47-53, 55-62 - RETURNING THE PEN
I've taken care of BP-44, which affected the HT spec and ws-humantask.xsd
and ws-humantask-api.wsdl.
Ralf can have the pen now.
Michael
-----Original Message-----
From: Ralf Mueller [mailto:ralf.mueller@oracle.com]
Sent: Monday, February 23, 2009 3:02 AM
To: Luc Clément
Cc: Dieter Koenig1; bpel4people-editors@lists.oasis-open.org
Subject: Re: [bpel4people-editors] Done with 20, 47-53, 55-62 - RETURNING
THE PEN
I would prefer to take the pen from Wed (2/25) onwards, Michael its
all yours, let me know when you are done.
Best Regards,
Ralf
On Feb 22, 2009, at 8:47 PM, Luc Clément wrote:
> Thanks Dieter.
>
> I've also taken care of also of BP-28 - Issue 68, section 8.2 (XML
> Infoset) - removal of erroneous statement regarding the source of
> the value for the responseOperation.
>
> We won't be meeting this week. Nonetheless I'd like to ask editors
> to review Dieter's work. Once we have two thumbs up, I'll move these
> updates to "Applied".
>
> Who would like the pen next: Michael (
http://www.osoa.org/jira/browse/BP-44
> ) or Ralf (.http://www.osoa.org/jira/browse/BP-70).
>
> Luc
>
> -----Original Message-----
> From: Dieter Koenig1 [mailto:dieterkoenig@de.ibm.com]
> Sent: Friday, February 20, 2009 12:02
> To: Luc Clément
> Cc: bpel4people-editors@lists.oasis-open.org
> Subject: [bpel4people-editors] Done with 20, 47-53, 55-62 -
> RETURNING THE PEN
>
>
> I finished editing for the resolutions of issues 20, 47-53, 55-62, and
>>>>>>>>>> RETURN THE PEN <<<<<<<<<<?
>
> ====> Luc: I added the comments below to the Jira issue entries as
> well -- please mark all 16 issues as "Applied" in Jira.
>
> This is BPEL4People and WS-HumanTask CD 02 Revision 1 -- 20 February
> 2009
> -- in SVN, this is revision 94.
>
> Here is the list of individual changes:
>
> BP-20
> ws-humantask-types.xsd
> - changed simple type tStatus to xsd:string (lines 157-159)
> - added simple type tPredefinedStatus with enumeration (lines
> 161-174)
> ws-humantask-1.1-spec.doc
> - added pre-states and post-states to table in 6.1.1
> - added normative language about pre-states and post-states in
> 6.1.1
> - updated state diagram in 4.7 (activate->activation, revoke->
> release)
> - uploaded Visio diagram source "ws-humantask-state-
> diagram.vsd" into SVN
>
> BP-47
> bpel4people-1.1-spec.doc
> - added getState operation in section 5
> - DID NOT (!) update state diagram in 4.8 (remove transitions
> to closed state) - to be discussed
> - uploaded Visio diagram source "bpel4people-state-diagram.vsd"
> into SVN
>
> BP-48
> bpel4people-1.1-spec.doc
> - added abstract BPEL namespace on page 2
> - changed namespace prefix of opaque activity in 7.1.1
>
> BP-49
> ws-humantask.xsd
> - added maxOccurs="unbounded" to the "argument" element inside
> the "tFrom" definition (line 422-423)
>
> BP-50
> ws-humantask.xsd
> - removed elements orgaizationalEntity, user, users, group,
> groups, and their complex type definitions
> ws-humantask-types.xsd
> - added elements orgaizationalEntity, user, users, group,
> groups, and their complex type definitions
> - changed namespace prefix of associated element and type
> references (htd->(no prefix))
> - removed namespace definition
> xmlns:htd=">http://docs.oasis-open.org/ns/bpel4people/ws-humantask/200803
> "
> ws-humantask-context.xsd
> - changed namespace prefix of associated element and type
> references
> (htd->htt)
> - removed namespace definition
> xmlns:htd="http://docs.oasis-open.org/ns/bpel4people/ws-humantask/200803
> "
> ws-humantask-api.wsdl
> - changed namespace prefix of associated element and type
> references
> (htd->htt)
> - removed namespace definition
> xmlns:htd="http://docs.oasis-open.org/ns/bpel4people/ws-humantask/200803
> "
> ws-humantask-example-claim-approval.tel:
> - changed namespace prefix of associated element and type
> references
> (htd->htt)
> - added namespace definition
> xmlns:htt=">
http://docs.oasis-open.org/ns/bpel4people/ws-humantask/types/200803
> "
> - added htt namespace to xsi:schemaLocation attribute for
> example validation
> bpel4people-example-employee-of-the-month.bpel
> - changed namespace prefix of associated element and type
> references
> (htd->htt)
> - added namespace definition
> xmlns:htt="
http://docs.oasis-open.org/ns/bpel4people/ws-humantask/types/200803
> "
> - added htd and htt namespaces to xsi:schemaLocation attribute
> for example validation
> ws-humantask-1.1-spec.doc
> - changed namespace prefix of associated element and type
> references
> (htd->htt) (>100x)
> bpel4people-1.1-spec.doc
> - changed namespace prefix of associated element and type
> references
> (htd->htt) (>40x))
>
> BP-51
> ws-humantask-api.wsdl
> - removed tTime complex type definition
> - added namespace prefix htt to tTime reference (line 112)
> ws-humantask-types.xsd
> - added tTime complex type definition (lines 183-188)
>
> BP-52
> ws-humantask.xsd
> - renamed tPriority to tPriority-expr in ws-humantask.xsd
> (lines 172 and 469)
>
> BP-53
> ws-humantask-api.wsdl
> - added
> targetNamespace="
http://docs.oasis-open.org/ns/bpel4people/ws-humantask/api/200803
> "
> to schema element
> ws-humantask-protocol.wsdl
> - added
> targetNamespace="
http://docs.oasis-open.org/ns/bpel4people/ws-humantask/protocol/200803
> "
> to schema element
>
> BP-55
> ws-humantask-1.1-spec.doc
> - added import type xsd to properties in section 2.5.2 (line
> 404 and
> 411)
>
> BP-56
> ws-humantask-protocol.wsdl
> - renamed ProtocolMsgType to tProtocolMsgType (lines 14 and
> 22-24)
> ws-humantask-1.1-spec.doc
> - renamed ProtocolMsgType to tProtocolMsgType (lines 2081,
> 2093, 2100, 2109)
>
> BP-57
> ws-humantask.xsd
> - simplified tQuery and tExpression complex type definitions
> (lines
> 454-468)
>
> BP-58
> ws-humantask.xsd
> - changed attribute logicalPeopleGroup definition from QName to
> NCName (line 428)
>
> BP-59
> ws-humantask.xsd
> - dropped minOccurs="0" and (!) maxOccurs="unbounded" from
> tLiteral any particle (line 450)
>
> BP-60
> ws-humantask-api.wsdl
> - replaced faultName/faultData by complex typed element fault
> in setFault and fail operations (lines 186 and 500)
> ws-humantask-1.1-spec.doc
> - replaced faultName/faultData by complex typed element fault
> in setFault and fail operations in 6.1.1
> - minor formatting (3x lower case operation names) in 6.1.1
>
> BP-61
> ws-humantask-types.xsd
> - renamed the tTask type and the task element to tTaskDetails
> and taskDetails, respectively (lines 86-87)
> ws-humantask-api.wsdl
> - renamed getMyTasks to getMyTaskDetails (multiple occurences:
> elements, messages, operation)
> - renamed getTaskInfo to getTaskDetails (multiple occurences:
> elements, messages, operation))
> ws-humantask-1.1-spec.doc
> - renamed the tTask type and the task element to tTaskDetails
> and taskDetails, respectively, in 3.4.4, 6.1.1, 6.1.2, 6.1.5
> - renamed getMyTasks to getMyTaskDetails in 6.1.2 and 6.1.5
> - renamed getTaskInfo to getTaskDetails in 6.1.1 and 6.1.5
> - minor formatting (3x lower case operation names) in 6.2
>
> BP-62
> ws-humantask.xsd
> - added block="extension restriction" to abstract
> genericHumanRole element definition (line 119)
> bpel4people.xsd (!)
> - added block="extension restriction" to abstract
> genericHumanRole element definition (line 77))
>
>
> Kind Regards
>
> Dieter König
>
> Senior Technical Staff Member, WebSphere Process Server Architect
> IBM Software Group, Application and Integration Middleware Software
> WSS Business Process Solutions
>
>
>
>
>
> Phone: +49-7031-16-3426 IBM
> Deutschland (Embedded
>
image
> moved
>
to
> file:
>
pic17679
> .gif)
>
> E-Mail: dieterkoenig@de.ibm.com Schönaicher Str. 220
>
> 71032 Böblingen
>
> Germany
>
>
>
>
>
> IBM Deutschland
> Research &
> Development
> GmbH /
> Vorsitzender des
> Aufsichtsrats:
> Martin Jetter
> Geschäftsführung:
> Erich Baier
> Sitz der
> Gesellschaft:
> Böblingen /
> Registergericht:
> Amtsgericht
> Stuttgart, HRB
> 243294
>
>
>
>
>
>
> From: Luc Clément <luc.clement@activevos.com>
>
> To: "bpel4people-editors@lists.oasis-open.org"
<bpel4people-editors@lists.oasis-open.org
> >
>
> Date: 18.02.2009 18:37
>
> Subject: [bpel4people-editors] RE: Congratulations on CD-02:
> assignment of the next Editor
>
>
>
>
>
>
> Dieter now has the pen.
>
> From: Luc Clément [mailto:luc.clement@activevos.com]
> Sent:: Wednesday, February 18, 2009 11:44
> To: bpel4people-editors@lists.oasis-open.org
> Cc: Dieter Koenig1
> Subject: [bpel4people-editors] Congratulations on CD-02: assignment
> of the next Editor
>
> We have a bunch of updates that we can now make.
> Dieter: are you in a position to kickoff your edits or should
> Michael or I do so?
> Luc
> Luc Clément
> Active Endpoints, Inc
> +1.978.793.2162 | luc.clement@activevos.com
>
>
>
>
> Key Summary Assignee
> (Embed
> ded
> image
> moved
> to
> file:
> pic049
> 08.gif
> )
> http:/
> /www.o
> soa.or
> g/jira
> /image
> s/icon
> s/down
> .gif
>
> BP-68 htd:remoteTask - a possible error? Luc Clement
>
> BP-62 Blocked Substitution Elements in Human Task Dieter
> Koenig
> Definitions
>
> BP-61 Cleanup tTask Definitions Dieter
> Koenig
>
> BP-60 Use tFault in setFault and fail API Methods Dieter
> Koenig
>
> BP-59 MaxOccurs Constraint Wrong in tLiteral Dieter
> Koenig
>
> BP-58 Type of Attribute LogicalPeopleGroup within tFrom Dieter
> Koenig
> Element
>
> BP-57 Common Base Type for tQuery and tExpression Dieter
> Koenig
>
> BP-56 Rename ProtocolMsgType Dieter
> Koenig
>
> BP-55 Import of XML Schema Artifacts Dieter
> Koenig
>
> BP-53 XML Schema Element Name Resolution in WSDL Dieter
> Koenig
>
> BP-52 Rename Priority Expression Type Dieter
> Koenig
>
> BP-51 Move tTime to ws-humantask-types.xsd Dieter
> Koenig
>
> BP-50 Refactor User, Group, and OrganizationalEntity Dieter
> Koenig
>
> BP-49 MaxOccurs Constraint Missing in tFrom Dieter
> Koenig
>
> BP-48 Abstract BPEL Process Namespace Dieter
> Koenig
>
> BP-47 Determining that a people activity's task has been Dieter
> Koenig
> skipped
>
> BP-44 Discovering the operations available for the task Michael
> Rowley
>
>
> BP-20 Extensibility of BPEL4People and WS-HumanTask Dieter
> Koenig
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail. Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
