| Hi
I don't follow what the development on this issue is.
As I commented, the specification seems to have only TYPE=HUMANTASK and NOTIFICATION.
Does it preempt that there will be more task types expected, such as you seem to indicate along the line of SIMPLETASK and COMPLEXTASK (with sub categories?).
Since I cannot get the Complex Task and Subtask document, can someone clarify on this on this or point me to where the documents are?
Thanks, 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. On 05/03/2009, at 3:12 AM, Luc Clément wrote: All, Following up on the discussion from the F2F, we would like to open an issue tracking the proposal to add support for interoperable “simple tasks” to WS-HT, i.e. enabling task parents to register new simple tasks on a task processor remotely. This would allow task parents and task processors from different vendors to easily interoperate in task scenarios that involve simple tasks. Thanks, Alex Malek
|