Minutes BPEL TC meeting
Provided by Martin Chapman
Quorum: 15 members, 21 members so
meeting is quorate
FAQ:
Motion to approve FAQ:
http://www.oasis-open.org/apps/org/workgroup/wsbpel/document.php?document_id=23858
Motion by Ron,
2nd Monica.
Discussion: None
Objections: Danny objects
Counted Vote: Y 12, N 1, A 1
Motion Passes. FAQ Approved
Primer:
Motion to approve Primer:
http://www.oasis-open.org/apps/org/workgroup/wsbpel/document.php?document_id=23927
Motion by Deiter,
2nd Simon
Date needs to change to appropval date.
Incorporates
Monica's comments since last weeks meeting.
There are comments in the document
that should be reviewed. All comments deleted with the following changes to the
doc
Fix TOC to not include Title, Notices
and TOC.
Delete the sentence in section 1.5:
The seventh chapter answers to some key questions and provides references
In 6.1.11:
change:
In this case, invoice validation is repeatedly performed until the
defined invoice status condition is met.
to:
In this
case, invoice validation is repeatedly performed as long as the defined invoice
status condition is met.
change:
<receive name="receiveInvoiceValidation"
partnerLink="InvoiceValidation"
portType="tsv:TimesheetInvoiceValidationCallbackInterface"
operation="returnInvoiceValidation"
variable="invoiceValidated" />
to:
<receive name="receiveInvoiceValidation"
partnerLink="InvoiceValidation"
portType="tsv:TimesheetInvoiceValidationCallbackInterface"
operation="returnInvoiceValidation"
variable="InvoiceStatusResponse" />
Note: the variable name is changed.
also in 6.1.11 add at the end of the final sentence of this para:
"The variable must have been initialised or an error will occur".
In 6.1.12:
Change:
<repeatUntil>
<invoke name="timesheetValidation"
... />
<receive name="receiveValidation"
partnerLink="TimesheetValidation"
portType="tsv:TimesheetValidationCallbackInterface"
operation="returnTimesheetValidation"
variable="timesheetValidated" />
<condition>
bpel:getVariableProperty(
"TimesheetStatusResponse","timesheettst:completionStatus") < 5
</condition>
</repeatUntil>
to:
<repeatUntil>
<sequence>
<invoke name="timesheetValidation" ... />
<receive name="receiveValidation"
partnerLink="TimesheetValidation"
portType="tsv:TimesheetValidationCallbackInterface"
operation="returnTimesheetValidation"
variable="TimesheetStatusResponse" />
</sequence>
<condition>
bpel:getVariableProperty(
"TimesheetStatusResponse","tst:completionStatus") < 5
</condition>
</repeatUntil>
In Appendx
A update the link to BPEL4WS 1.1 to point to the OASIS submission.
Back to the
motion.
Danny doesn't believe it to be high
enough quality to be a committee draft.
Counted Vote: Y 6, N 1, A 4
Motion Passed. Primer is approved
Adoption TC:
Draft charter circulated.
Yes a TC can do adoption and erratta if members wanted to, depending on
how the charter is written.
Martin says its
silly to combine adoption with maintainance and
should be separate TCs.
This is because different types of members who would
contribute to each type of activity.
Diane notes that previous adoption TC's
have been very marketing oriented and suggests that for BPEL the adoption
activities of most value now would include technical education and guidance to
early implementers, and so might involve more technical people than other
previous adoption TC's have engaged.
Consensus that maybe Adoption is the wrong word.
Jamie will follow up with those who've expressed interest in
forming such a TC.
AOB:
Jamie thanked the prsenters
at the OASIS Symposium.
Jamie thanked the TC for all its
effort.
Motion to thank
the Chairs from Peter. 2nd Frank.
Unanimously approved!
Thanks to Peter for mianting the issues list throughout the life of this TC
Motion to
Adjourn. Passed.
Since there is no time to approve
these minutes please send any corrections to the list before