[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: BP-72: Add the definition of the Human Task Process term
|
Assigned: http://www.osoa.org/jira/browse/BP-72
From: Yoichi Takayama
[mailto:takayama.yoichi@gmail.com] Target: bpel4people-1.1-spec-CD-02-MARKEDUP.pdf This document mentions HumanTask Processor only 3 times in
the Section 4.5.3.
928 HumanTask Processor hosting
... 948 ... WS-HumanTask 949 Processor ... While the
definition for a BPEL Processor is given in Section 2.3 as below, there
appears to be no clear definition or reference to what the HumanTask Processor
is at this point (although the reader would find it out in WS-HumanTask document
later). 251 BPEL4People Processor 252 A BPEL4People Processor is any
implementation that accepts a BPEL4People definition and 253 executes the semantics defined in
this document. Except that The HumanTask Processor must also return a
metadata, and the metadata operation is said to refer Section 8.2 of the
WS-HumanTask document. It seems that, before introducing a new term, it is better
to define it. Although the usage of the term is very limited in this case, the
term is neither common nor self-explanatory to someone who reads this
document (or works with this specification) for the first time.
Add the definition of the term at the beginning of
the block or immediately after the first usage. Also, clarify what it is. (1) It may be rather easy to say
that it is a Web Service which hosts a Human Task and implements WS-C to
interact with the BPEL4People Processor. (2) The Task Processor must be the
WS-C WS-HT Protocol Service in WS-C nomenclature and probably it needs to be
clarified. Notes: In my opinion it is better to define a Task List Manager
sub-system who receives a Task request from BPEL4People processing engine. A
Task Processor would rather interact with the Task List Manager, not the
BPEL4People processing engine. However, I understand that it could be said that it is an
implementation issue since this standard does not define anything about the
Task List Manager. However, this standard mentions (or the white paper did
mention) the way Task List client and Task client would work, and probably that
should be defined in the standard to have interpretability for
providers of these and a BPEL4people Processor. 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 -------------------------------------------------------------------------- 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. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]