[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [bpel4people-editors] Forward Progress on BP-16 - Revised Comments
Thanks Vinky. Reminder: please have your review of B4P BP-16 updates so we may
close on this before the Christmas break. Thanks Luc From: 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]