[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: 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.
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.
I created a new .wsdl - ws-humantask-leantask-api.wsdl. The
name has been already proposed by Dieter (as part of issue
BP-128).
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.
Please let me know if you agree with these
changes.
Kind
regards,
Ivana Ivana
Trickovic Pflichtangaben/Mandatory
Disclosure Statements: http://www.sap.com/company/legal/impressum.epx 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
|
Luc
Luc
Clément
Active
Endpoints, Inc
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]