[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [bpel4people-editors] AW: Ivana has the pen for BP-103 and BP-111
Hi Ivana, please see my responses inline (<dk>...</dk>).
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:
pic04498.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: "Trickovic, Ivana" <ivana.trickovic@sap.com>
To: Luc Cl�ment <luc.clement@activevos.com>, Dave Ings <[email protected]>, "'Phil Allen (SHAREPOINT DESIGNER)'"
<phillipa@exchange.microsoft.com>, Dieter Koenig1/Germany/IBM@IBMDE
Cc: "bpel4people-editors@lists.oasis-open.org" <bpel4people-editors@lists.oasis-open.org>
Date: 13.10.2009 15:36
Subject: [bpel4people-editors] AW: Ivana has the pen for BP-103 and BP-111
Hi all,
Resolutions for BP-103 and BP-111 are in the specification: revision 152 in
SVN..
Please note the following:
1. For BP-103 the following documents have been modified:
- ws-humantask document
- ws-humantask.xsd: definitions tTask, tTaskBase, and tCompletionBehavior
changed; new simple type "tCompletionAction" introduced:
<xsd:simpleType name="tCompletionAction">
<xsd:restriction base="xsd:string">
<xsd:enumeration value="manual" />
<xsd:enumeration value="automatic" />
</xsd:restriction>
</xsd:simpleType>
Please note that we already have simple type "tInstantiationPattern" which
could be reused (but it would be useful to change the name - make it more
generic).
<xsd:simpleType name="tInstantiationPattern">
<xsd:restriction base="xsd:string">
<xsd:enumeration value="manual" />
<xsd:enumeration value="automatic" />
</xsd:restriction>
</xsd:simpleType>
I can make this change if the editors team agrees.
<dk>You may use a common type, e.g. "tInteractionType" (for lack of a
better word).</dk>
2. For BP-111:
>Phil: Motion to resolve Issue 111 with the text, except 9.2.5 should have
the three references to the word 'protocol' removed and to remove the
>CreateLeanTaskResponse and all references to it.
>Matthias Kloppmann: Dieter seconds
The adopted proposal leads to not well-formed WSDL - the createLeanTask
operation has faults so the options were to:
(a) remove CreateLeanTaskResponse and *all faults* (and related
specification text) => but the specification text is needed in case of
two-way operation
(b) keep CreateLeanTaskReponse and make it empty and remove specification
text mentioning task identifier => this specification text is not needed
anymore
(c) keep CreateLeanTaskReponse and define it as output message
I selected option (2) as it required the least changes to the adopted
proposal and the remaining work will be done as part of issue
http://www.osoa.org/jira/browse/BP-128.
<dk>This is also by preference -- (b)=(2) :-) -- if the BP-128 proposal is
adopted then this is one of two createLeanTask variations anyway.</dk>
I created a new .wsdl - ws-humantask-leantask-api.wsdl. The name has been
already proposed by Dieter (as part of issue BP-128).
<dk>Please add "/api" to the namespace:
"http://docs.oasis-open.org/ns/bpel4people/ws-humantask/leantask/api/200803
" (in WSDL & spec).</dk>
The last point from my side: The BP-111 resolution introduced same faults
(illegalState...) in the new namespace - see new .wsdl. I believe we could
reuse existing faults defined in ws-humantask-api.wsdl. This change can be
made as part of issue BP-128.
<dk>I would keep them separate (as a copy) -- ws-humantask-api.wsdl has
additional faults that do not apply to lean tasks.</dk>
Please let me know if you agree with these changes.
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
Pflichtangaben/Mandatory Disclosure Statements:
http://www.sap.com/company/legal/impressum.epx.
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: Luc Cl�ment [mailto:luc.clement@activevos.com]
Gesendet:. Mittwoch, 7. Oktober 2009 17:57
An: bpel4people-editors@lists.oasis-open.org
Betreff: [bpel4people-editors] Ivana has the pen for BP-103 and BP-111
Ivana has volunteered and
has the pen for the
following two issues:
Ke
y
(Embedded image moved to
file: pic29992.gif)
http://www.osoa.org/jira/ima
ges/icons/down.gif
Summary
Assignee
BP-111 Addition Register, Unregister and Ivana
List to support interop of Task Tricko
Parent and Task Processor vic
BP-103 HT 4.7.1. Should we allow the Ivana
attachment of completion criteria to Tricko
a task element vic
Luc
Luc Cl�ment
Active Endpoints, Inc
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
