Thanks Michael.
I am taking the pen now.
Kind regards,
Ivana
Ivana
Trickovic Standards Architect SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf, Germany T +49 6227
7-63228 F
+49 6227 78-33160 M +49 151 57118422 mailto:ivana.trickovic@sap.com
www.sap.com
Sitz der
Gesellschaft/Registered Office: Walldorf, Germany Vorstand/SAP Executive Board:
Henning Kagermann (Sprecher/Co-CEO), Léo Apotheker (Sprecher/Co-CEO), Werner
Brandt, Erwin Gunst, Claus Heinrich, Bill McDermott,
Gerhard Oswald, John Schwarz, Jim Hagemann
Snabe
Vorsitzender des
Aufsichtsrats/Chairperson of the SAP Supervisory Board: Hasso
Plattner Registergericht/Commercial Register Mannheim No HRB 350269
Diese E-Mail kann
Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen
enthalten. Sollten Sie diese E-Mail irrtümlich erhalten haben, ist Ihnen eine
Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der E-Mail
ausdrücklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die
empfangene E-Mail. Vielen Dank.
This e-mail may
contain trade secrets or privileged, undisclosed, or otherwise confidential
information. If you have received this e-mail in error, you are hereby notified
that any review, copying, or distribution of it is strictly prohibited. Please
inform us immediately and destroy the original transmittal. Thank you for your
cooperation.
I’ve
checked in changes for 36, 41, 45.
I’m
giving up the pen.
Michael
From: Luc Clément
[mailto:luc.clement@activevos.com] Sent: Wednesday, April 29, 2009
11:33 AM To:
bpel4people-editors@lists.oasis-open.org Subject:
[bpel4people-editors] Resolution applied to B4P - BP-72 - FW: [bpel4people]
BP-72: Add the definition of the Human Task Process
term
I’ve
updated the B4P spec to cover: Issue 72: add WS-HumanTask and
WS-HumanTask Processor definitions to section 2.3
We’re
now at rev 114.
Michael
still has the pen on the HT spec.
From: Luc Clément
[mailto:luc.clement@activevos.com] Sent: Thursday, April 16, 2009
08:17 To: Dave Ings;
bpel4people@lists.oasis-open.org Subject: RE: [bpel4people] BP-72: Add
the definition of the Human Task Process term
I took
an action item yesterday to review BP-72. I propose the following
disposition:
1.
Add
conformance target definitions to section “2.3 Conformance Targets” of the B4P
spec as noted at: http://www.osoa.org/jira/browse/BP-72#action_13678:
Update
section 2.3 Conformance Targets by adding the following two
bullets:
•
WS-HumanTask Definition
A
WS-HumanTask Definition is any artifact that complies with the human interaction
schema and additional constraints as defined by the WS-HumanTask 1.1
specification.
•
WS-HumanTask Processor
A
WS-HumanTask Processor is any implementation that accepts a WS-HumanTask
definition and executes the semantics as defined by the WS-HumanTask 1.1
specification.
2.
As for
the need for a system component architecture diagram and supporting text to
address Yoichi’s concerns, I agree that this should be handled as part of
BP-65.
I
would therefore propose that BP-72 be constrained to an update of section 2.3 of
the B4P spec. If the TC approves this proposal, the editors (me) will be happy
to make the update once BP-72 is accepted as “Resolved”
Luc
Luc
Clément
Active
Endpoints, Inc
+1.978.793.2162
| luc.clement@activevos.com
From: Dave Ings
[mailto:ings@ca.ibm.com] Sent: Wednesday, February 18, 2009
10:28 To: bpel4people@lists.oasis-open.org Subject: Re:
[bpel4people] BP-72: Add the definition of the Human Task Process
term
My initial thought is that these suggestions
should be added to the system component architecture issue that Frank agreed to
handle
http://www.osoa.org/jira/browse/BP-65
rather
than being a standalone issue, but this is something we can discuss during the
TC.
Regards, Dave Ings, Emerging Software Standards Email:
ings@ca.ibm.com Yahoo Messenger: dave_ings
Luc Clément ---2009/02/18 09:54:54 AM---Assigned: http://www.osoa.org/jira/browse/BP-72
From: Yoichi Takayama [mailto:takayama.yoichi@gmail.
From:
|
Luc Clément
<luc.clement@activevos.com>
|
To:
|
Yoichi Takayama
<takayama.yoichi@gmail.com>
|
Cc:
|
"bpel4people@lists.oasis-open.org"
<bpel4people@lists.oasis-open.org>
|
Date:
|
2009/02/18 09:54 AM
|
Subject:
|
[bpel4people] 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]
Sent: Tuesday, February 17, 2009 23:48 To: Luc
Clément Cc: bpel4people@lists.oasis-open.org Subject: new
issue request
Target:
bpel4people-1.1-spec-CD-02-MARKEDUP.pdf
Description:
This document mentions HumanTask
Processor only 3 times in the Section 4.5.3.
920
A WS-HumanTask Processor MUST ...
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.
Proposal:
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 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.
|