Re: [bpel4people] Groups - New Action Item #0018 This is the sketch of the HT Arc...

[Yoichi Takayama <takayama.yoichi@gmail.com>]

Hi Alan,

Thanks for your assessment on the matter.

That was my understanding, too.

As you suggest, making the distinction between them would be cleaner.

Although the Task UI, its rendering information and the interface are all out of scope, it is essential to describe that we are well aware that they would be needed.

Best regards,

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 07/05/2009, at 6:32 AM, Rickayzen, Alan wrote:

Dear Yoichi, Frank,

My understanding of task UI is that which is used to perform the task (input
form, voting button, spreadsheet program, telephone, screwdriver...) and not
the meta-information associated with the task (description, priority...).
The latter *is* rendered by the task list client. But the task UI is not
necessarily rendered by the task list client.

So I believe Figure 7 is slightly misleading since the UI for the task can
be rendered by either the task list client, the task processor (engine?), or
the business application. It's a matter of deployment which of these is used
and how it is invoked. 

If that is the case, then I would prefer the statement in the last paragraph
"A task client in turn has to use this information to construct or
invoke..."

I'm also all in favour of including the architecture paper.

Best regards,

Alan Rickayzen
Alloy Product Manager
SAP AG
Hasso-Plattner-Ring 1
69190 Walldorf
T   +49 / 6227 / 7-45567
M   +49 / 160 90820152
E   alan.rickayzen@sap.com

smime.p7s