[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [bpel4people] BPEL4People TC - 1Q09 F2F Final Agenda
Dear all, Here is my issue proposal. This is just formalizing the phone presentation I did in December. Title: A need for a "GetUI" or "StartTask" request/message for a Task Web Service Raised By: Yoichi Takayama Target: WS-BPEL Extension for People (BPEL4People) Specification V 1.1, CD 02 (proposal), 6 Jan 2009, Section 6 (and related sections) Also: Web-Services Human Task (WS-HumanTask) Specification Version 1.1, CD 02 (proposal), 6 Jan 2009, Section 7 (and related sections) http://www.oasis-open.org/apps/org/workgroup/bpel4people/document.php? document_id=30552 Description: In WS-HumanTask Section 7, Figure 1, the requestMessage presumably corresponds to createTask message of the Task Life Cycle management. Although this causes to "Register" the WS-C protocol handler EPRs between the Task Parent and the Task (implemented as a Web Service) as the (2) and (3) indicate, the "requestMessage is an asynchronous request and nothing follows after that. The (4a) is the asynchronous return for the (1) requestMessage, as I understand it. Presumably, following this step, there is the "start" message handled by the Task Life Cycle management (BPEL4People 4.8 or WS-HumanTask 4.7), which presumably would get UI from the Task Implementation to the Task Parent (and then to a Task Client and to its user agent that the end human user uses to do the Task) and let the end user do the human task. However, how this would be dealt with in an interoperable manner is not shown by the specification. Obviously, the (4a) or (4b) would not occur until the Task UI is presented to the end user and some outcome has been produced. So, the "start" step is a Task Service step that should be documented and defined before the termination of the Task such as (4a) or (4b). This is lacking in the specification. We cannot presume that the Task Parent or the Task Coordinator knows what operation or EPR to ask for to call it, since the specification does not have any place that states such an operation or how to specify such additional EPR for that operation, i.e. "StartTask". Proposal: 1. Add a "StartTask" request message to Section 6.1 of the WS- HumanTask and to the table of WS-C WS-HT messages (page 31). This corresponds to the "start" Task Life Cycle management command, but is distinct from it because it is one of the Task Web Service massages. This may return either a single page UI (such as HTML Form or XML) or an application UI (that could be a form of an EPR or URL or e.g. XUL- application XML launch point). The Task may be an multiple-page Web application or Desktop UI of an comprehensive application, for example. 2. For this reason, the interoperable format for the response message of the "StartTask" must be defined so that it can be interpreted by the Task Coordinator, Task Parent, and Task Client properly (so that they will know what the response contains and what to do with the information/data). Alternative We could provide an ability or a place to state the additional EPR for StartTask, but that is tedious. If a fixed WS-C WS-HT message can handle it, it is more consistent with the current CD and it may be simpler. Potential Problem If a Web Service implements multiple Tasks with different EPRs, each Task must implement different WS-C protocol handler and the "StartTask" message handler with it. In this case, there may be more efficient way to organize the whole WS-C WS-HT better. Yoichi ------------------------------------------------------------------------ -- Yoichi Takayama, PhD Senior Research Fellow RAMP Project MELCOE (Macquarie E-Learning Centre of Excellence) MACQUARIE UNIVERSITY Phone: +61 (0)2 9850 9073 Fax: +61 (0)2 9850 6527 www.mq.edu.au www.melcoe.mq.edu.au/projects/RAMP/ ------------------------------------------------------------------------ -- MACQUARIE UNIVERSITY: CRICOS Provider No 00002J This message is intended for the addressee named and may contain confidential information. If you are not the intended recipient, please delete it and notify the sender. Views expressed in this message are those of the individual sender, and are not necessarily the views of Macquarie E-Learning Centre Of Excellence (MELCOE) or Macquarie University. On 16/01/2009, at 10:05 AM, Dave Ings wrote: > Here's the agenda for next week's F2F. > > I will be offline Friday and Monday due to travel, so if we need to > adjust the agenda we will do so at the beginning of our meeting > Tuesday morning. In prior F2Fs minute takers each did 1/2 day - and > this seemed to work well - so I would expect we'll need 4 minute > takers over the course of the 2 working days. There will be at > least one break in the morning and one in the afternoon. > > Yoichi - when you submit your new issue to the mailing list, we'll > find an agenda slot that works for your time zone. > > Tuesday 1/20 20 9 AM - 12 noon > > 1. Welcome, roll call, assignment of initial minute taker, agenda > review - 15 minutes > > According to the chair's notes, the minute taker candidates are (in > order) Martin, Dieter, Frank, and Alex > > 2. Review and approval of the previous TC minutes - 5 minutes > > http://www.oasis-open.org/apps/org/workgroup/bpel4people/email/ > archives/200812/msg00044.html > > 3. Discuss New Issues - 30 minutes > > Issues 62 & 63 - Dieter > > http://www.osoa.org/jira/browse/BP-62 > http://www.osoa.org/jira/browse/BP-62 > > 4. Discuss Open Issues - 15 minutes > > Issue 20 - Phil et al > > This issue has been open but unassigned since 10/1. We should agree > upon what to do with it (or close it). > > http://www.osoa.org/jira/browse/BP-42 > > 5. Constellation 4 Interoperability - Alex & Phil - 60 minutes > > Tuesday Jan 20 1 PM - 5 PM > > 1. IBM/SAP Presentation on Task Routing Proposal - 2 hours > > http://www.oasis-open.org/apps/org/workgroup/bpel4people/email/ > archives/200901/msg00007.html > > 2. Committee Draft 2 Discussion & Potential Approval Vote - Luc > Clement - 1 hour > > To accommodate Luc dialing in from North America, will start at 9 > AM ET / 3 PM CET > > http://www.oasis-open.org/apps/org/workgroup/bpel4people/email/ > archives/200901/msg00002.html > > 3. Resume discussion on IBM/SAP presentation - 1 hour > > Wednesday 1/21 - 9 AM to 5 PM > > 1. Working session on task routing proposal(s) - - 5 hours > > 2. Michael to review proposals for issues 36, 44, 45 - 2 hours > > http://www.osoa.org/jira/browse/BP-36 > http://www.osoa.org/jira/browse/BP-44 > http://www.osoa.org/jira/browse/BP-45 > > Thursday 1/22 - 9 AM - 12 noon > > 1. To be scheduled depending on preceding two day's discussion. > > Logistics > > http://www.oasis-open.org/apps/org/workgroup/bpel4people/ > download.php/30565/BPEL4People%20TC%20F2F%20Meeting%20Stuttgart% > 202009-01-20.doc > > (On demand only) telecon Information: > > North American toll-free number: 866-245-5059 > European toll-free number: (00)-800-4444-1010 > International number: 416-343-2607 > Conference ID: 2388736 > > Informal chat room: http://webconf.soaphub.org/conf/room/ > bpel4people-TC > > Regards, Dave Ings, > Emerging Software Standards > Email: ings@ca.ibm.com > Yahoo Messenger: dave_ings > > > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]