[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [bpel4people-editors] Forward Progress on BP-16 - RevisedComments
Thanks Ivana, I will incorporate these changes by end of this week. Regards, -Vinky Vinkesh O. Mehta , PMP Specialist
Leader, Deloitte Consulting LLP Mobile: + 1 512 750 2006 vmehta@deloitte.com
From: Trickovic, Ivana
[mailto:ivana.trickovic@sap.com] Hi
all, Finally,
I revisited my initial input (please see below) - I used revision 77. Commentx
on sections 4 and 5 did not change. I updated comments on sections 7 and
8. Kind
regards, Ivana Section 4 ========== Line 1075:
"The
name combined with the target namespace of a task element is used to uniquely
identify the task definition. " Change to "The
name combined with the target namespace MUST uniquely identify a task element
enclosed in the task definition." Line 1396:
"For
all deadlines if a status is not reached within a certain time then an
escalation action, specified using element <escalation>, can be
triggered. " Change to "For
all deadlines if a status is not reached within a certain time then an
escalation action, specified using element <escalation>, is triggered.
" Line 1411:
keep "MAY" Line 1432:
"In
the case where several reassignment escalations are triggered, the first
reassignment (lexical order) will be considered for execution. " change to "In
the case where several reassignment escalations are triggered, the first
reassignment (lexical order) MUST be considered for execution by the
WS-HumanTask Processor. " Line 1436:
keep "MAY" Line 1643:
"People
queries that cannot be executed successfully are treated as if they were
returning an empty set. " change to "People
queries that cannot be executed successfully MUST be treated as if they were
returning an empty set. " Line 1646:
keep "must" and change to "MUST" Line 1718:
keep "may" and change to "MAY" Line 1763:
"The
name combined with the target namespace of a notification element is used to
uniquely identify the notification definition. " change to "The
name combined with the target namespace MUST uniquely identify a notification
in the notification definition. " Section
7 ========== Line
1981: "The
calling application MAY set values of the following attributes of the task definition:" change
to "The
WS-HumanTask Parent MAY set values of the following attributes of the task
definition" Line
1998: "that
the parent application MUST use to send all protocol messages " change
to "that
the WS-HumanTask Parent MUST use to send all protocol messages" Line
2001: "The parent application reacts to that message by sending "
change to "The
WS-HumanTask Parent reacts to that message by sending " Line
2023: "Only priority and people assignments MUST be overridden for a
notification" change
to "Only
priority and people assignments MAY be overridden for a notification" Line
2029: "between the WS-HumaTask Processor and Application. " change
to "between
the WS-HumaTask Processor and WS-HumanTask Parent." Line
2039: "available to the WS-HumanTask processor" change to
"available to the WS-HumanTask Processor" Line
2040: "registration service MUST be passed by Applicaton" change to
"registration service MUST be passed by WS-HumanTask Parent" Line
2127: "the exit protocol message MUST be passed to the subprocess by" change
to "the
exit protocol message MUST be passed to the task by " Line
2193: "This policy assertion may be associated" change to "This
policy assertion can be associated " Line
2197: "the provider of a human task MAY signal whether or not the
corresponding task may communicate with an invoking component via the
WS-HumanTask coordination protocol. " change to "the provider of a
human task can signal whether or not the corresponding task can communicate
with an invoking component via the WS-HumanTask coordination protocol. " Line
2204: "This policy assertion specifies that the sender of an input message
MUST include context information for a human task coordination type passed with
the message." change to "This policy assertion specifies that the
WS-HumanTask Parent, in this case sender, MUST include context information for
a human task coordination type passed with the message." Line
2223: "In that case it means that the sender of an input message MAY pass
the human task context information with the message." change
to "In
that case it means that the WS-HumanTask Parent, in this case the sender, MAY
pass the human task context information with the message." Section
8 ========== Line
2230: "Passing this callback information from a caller (i.e. a requesting
application) to a human task may override static deployment information that
may have been set. " change
to "Passing
this callback information from a WS-HumanTask Parent (i.e. a requesting
application) to a human task MAY override static deployment information that
may have been set. " Line
2279: "This element of the EPR MUST be sent by the caller" change to
"This element of the EPR MUST be sent by the WS-HumanTask Parent, the
caller, " Line
2287: "message from the WS-HumanTask Processor back to the caller"
change to "message from the WS-HumanTask Processor back to the
WS-HumanTask Parent, the caller" Line
2294:""If this element is specified the <htcp:responseAction>
element MUST NOT be specified by the caller." change to "If
this element is specified the <htcp:responseAction> element MUST NOT be
specified by the WS-HumanTask Parent." Line
2385: "Note that the [fault endpoint] property is not used " change
to "Note that the [fault endpoint] property MUST NOT be used " Ivana Trickovic Sitz der Gesellschaft/Registered Office: Walldorf, Germany Vorsitzender des Aufsichtsrats/Chairperson of the SAP Supervisory
Board: Hasso Plattner 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. Von: Mehta,
Vinkesh (US - Austin) [mailto:vmehta@DELOITTE.com] I have
updated the WS-HT with Dieter’s comments (see response below). And I have
checked in the WS-HT into svn. Ivana,
will you be sending me additional/updated comments or does Dieter’s comments
includes your feedback? Thanks, -Vinky Vinkesh
O. Mehta , PMP Specialist
Leader, Deloitte Consulting LLP Mobile:
+ 1 512 750 2006 vmehta@deloitte.com
-----Original
Message----- Dear
BPEL4People Editing team, after discovering that section 2.3 already defines a
conformance target "WS-HumanTask Parent", I need to revise my
comments sent out earlier. Here is the new set: Section
3.2. line 516
- "they can be used" would be sufficient - no MAY needed <vinky>replaced ‘may’ with ‘can’</vinky> Section
4.+5. (edited
by DK) no comments Section
6. line
1811 (void response) - this is normatively addressed in
ws-humantask-api.wsdl - no issue required <vinky>Deleted Comment</vinky> line
1826 - broken reference <vinky>reference works</vinky> line
1845 - dup of line 1808 <vinky> Line deleted
</vinky> line
1935 - add "A WS-HT processor MUST support the XPath functions listed
below"? <vinky> Added line
</Vinky> Section
7. line
1993 - "WS-HumanTask Processor implementation" - drop
"implementation" <vinky>dropped</vinky> line
2001 - "The parent application MUST react ..." - not sure if we need
this - it is already mandated by WS-Coordination <vinky>
Removed MUST </vinky> line
2014 (same on line 2019 and line 2028) - "Response message SHOULD NOT
..." - revert to original sentence (this is a one-way operation - there is
never a response) <vinky>reverted to
Original</vinky> line
2017 - scenario 3 - replace "parent application" by
"WS-HumanTask Parent" <vinky>
replaced </vinky> line
2033 - replace "Human task aware requesting applications" by "A
WS-HumanTask Parent" <vinky> replaced
</vinky> line
2048 and line 2053 (attachments) - MAY seems ok as the attachment concept as a
whole is optional <vinky>Comment
deleted</vinky> line 2057
and line 2060 - change "No attachments MUST be returned." to
"Attachments MUST NOT be returned." <vinky>
Changed </vinky> line
2063 - drop "No attachments MUST be returned.." <vinky> Dropped, Comment deleted </vinky> line
2087 and line 2095 - again, the absence of a response is already covered by the
normative one-way interface of protocol operations, so these two sentences can
be reverted to their original wording <vinky>
Reverted </vinky> line
2114 - replace MAY by MUST, <vinky> replaced
</vinky> line
2143 - revert "WS-HumanTask Definition" to "WS-HumanTask" -
the context is completely independent of a task definition <vinky> reverted </vinky> line
2197 - (policy assertion) replace MAY by SHOULD <vinky>
replaced </vinky> Section
8. line
2301 - replace "the caller" (conformance target) by "the
WS-HumanTask Parent" <vinky> replaced
</vinky> line
2335 - replace ")will be used" by "is used" (always use
present tense) <vinky> replaced
</vinky> line
2408 - add normative language to the SOAP binding section <vinky>added normative language ‘MUST’ with regards
to WS-Addr-SOAP</vinky> line
2470 - replace "set by the caller in its response to the caller" by
"set by the WS-HumanTask Processor in its response to the WS-HumanTask
Parent" <vinky>replaced </vinky> 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:
pic07695.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 -----
Forwarded by Dieter Koenig1/Germany/IBM on 10.12.2008 18:40 -----.
From: Dieter Koenig1/Germany/IBM@IBMDE
To: "Luc Clement"
<luc.clement@activevos.com>
Cc:
bpel4people-editors@lists.oasis-open.org
Date: 08.12.2008 11:28
Subject: Re: [bpel4people-editors] Forward Progress on BP-16 Dear
BPEL4People Editing team, I collected a couple of review comments listed below
- we may walk through in one of the next editor's calls. Section
3.2. line 516
- "they can be used" would be sufficient - no MAY needed Section
4.+5. (edited
by DK) no comments Section
6. line
1811 (void response) - this is normatively addressed in ws-humantask-api.wsdl
- no issue required line 1826 - broken reference line 1845 - dup of line 1808
line 1935 - add "A WS-HT processor MUST support the XPath functions listed
below"? Section
7. line
1993 - "WS-HumanTask Processor implementation" - drop "implementation" line
2001 - "The parent application MUST react ..." - not sure if we need
this - it is alread mandated by WS-Coordination line 2014 (same on line 2019
and line 2028) - "Response message SHOULD NOT ..." - revert to
original sentence (this is a one-way operation - there is never a response)
line 2017 (same on line 2033) - >>>NEW ISSUE<<< - scenario 3
- the parent application must be a conformance target (!) as it has to send the
"exit" protocol
message - in line 2033, they are called "Human task aware requesting
applications" - in line 2301, "the caller" is used line 2048 and
line 2053 (attachments) - MAY seems ok as the attachment concept as a whole is
optional line 2057 and line 2060 - change "No attachments MUST be returned."
to " Attachments
MUST NOT be returned." line
2063 - drop "No attachments MUST be returned.." line
2087 and line 2095 - again, the absence of a response is already covered by the
normative one-way interface of protocol operations, so these two sentences can
be reverted to their original wording line 2114 - replace MAY by MUST, line
2143 - revert "WS-HumanTask Definition" to "WS-HumanTask" -
the context is completely independent of a task definition line 2197 - (policy
assertion) replace MAY by SHOULD Section
8. line
2301 - "the caller" (conformance target) - see issue above line 2335
- replace ")will be used" by "is used" (always use present
tense) line 2408 - add normative language to the SOAP binding section line 2470
- replace "caller" by "WS-HumanTask Processor" 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: pic09875.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:
"Luc Clement" <luc.clement@activevos.com>
To:
<bpel4people-editors@lists.oasis-open.org>
Date: 05.12.2008 02:15
Subject: [bpel4people-editors] Forward Progress on BP-16 Folks, Unfortunately,
we weren’t able to make progress on the HT review this week. Ivana,
Dieter and I discussed when we met briefly on Wednesday that we need to close
our review of HT by Wed 10 and the review of the B4P updates by Wed 17. This
would permit the TC to approve our BP-16 proposal, and subsequently release
CD-02 early in the new year. To this
end we ask that all editors provide input on the HT updates starting from 3.2
(to the end) no later than 10 Dec. Ralf has
not only completed his updates to B4P but mine also J. Sections 1 through 6
have been completed, and Ravi now has the pen. Given this progress and on the
assumption that Ravi will be completed shortly, I ask that all input on BP-16
updates to B4P be submitted by the 17th. If there
are any issues that need to be discussed, we can do so on the meetings of the
10th and 17th. Let’s
get this done before Xmas. I trust that everyone is on board with this. Luc’ Luc
Clément Active
Endpoints, Inc +1.978.793.2162
| luc.clement@activevos.com [attachment
"pic09875.gif" deleted by Dieter Koenig1/Germany/IBM] --------------------------------------------------------------------- To
unsubscribe from this mail list, you must leave the OASIS TC that generates
this mail. Follow this link to all your TCs in OASIS at:
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]