[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [bpel4people] BP-118 Proposal - Task Type vs. Task Definition
+1 "Task Definition" is consistent with e.g. "Process Definition" in BPEL. 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: pic13091.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: "Phil Allen (SHAREPOINT DESIGNER)" <phillipa@exchange.microsoft.com> To: "bpel4people@lists.oasis-open.org" <bpel4people@lists.oasis-open.org> Date: 05.08.2009 08:33 Subject: [bpel4people] BP-118 Proposal - Task Type vs. Task Definition All, Since TaskType is the normative term for a value of the enumeration TASK|NOTIFICATION, we should use ‘task definition’ for the places in the spec that refer to different contents for a htd:task element. On review, I have found two locations that need updates in the WS-HumanTask specification. Proposal: Change the following two references in WS-HumanTask: Caption for figure 2, section 1.1: Task Types Deployed in Task Processor => Task Definitions Deployed in Task Processor Section 3.1: Business administrators play the same role as task stakeholders but at task type level => Business administrators play the same role as task stakeholders but at the task definition level. Thanks, Phil
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]