Item 4 Approval of Minutes from Previous Meeting
Minutes are approved without objection
Resolution: minutes of of 2010-01-14 located at http://lists.oasis-open.org/archives/sca-bpel/201001/msg00009.html approved
#0109 MikeEdwards - Send instructions for running the Assembly tests
#0115 MikeEdwards - Prepare an updated version of the proposal for issue 58 (rewriting section 2.1.1 to remove the nested-if)
#0117 Danny - Create a new issue and a proposal for the 0..1 case (related to issue 53)
Item #0109 is still outstanding - Mike debugging the Tuscany BPEL runtime at the moment
Item #115 now transferred to Anish, still outstanding
Item #0117 still outstanding
For the subsequent work on test assertions etc., here is a summary of the affected conformance items:
-- BPEL-41 - Deleted [SBPEL2020], [SBPEL2021], [SBPEL2022] and introduced [SBPEL2023]
-- BPEL-42 - Deleted [SBPEL3004]
-- BPEL-45 - Modified [SBPEL3022] - wording only, no impact on test
-- BPEL-47 - New example only
-- BPEL-48 - Modified introduction text only
-- BPEL-49 - Extended [SBPEL1001]
-- BPEL-51 - Deleted [SBPEL3021]
-- BPEL-53 - Modified [SBPEL2012]
-- BPEL-55 - Introduced [SBPEL3024]
-- BPEL-59 - Introduced [SBPEL5001], [SBPEL5002]
-- BPEL-60 - Modified abstract text only
Moreover, spec revision 3+4 editing by Najeeb affected the following conformance items:
-- BPEL-52 - Deleted [SBPEL2004.2], [SBPEL3011], renamed [SBPEL3011.1] to [SBPEL3011]
-- BPEL-56 - Introduced [SBPEL3010.1]
SBPEL3010.1 needs to be renamed to a "regular" numbering, just like the other ones
- just use a free number in the range
rename [SBPEL2004.1] and [SBPEL3010.1]
<discussion of the approach to renumbering the conformance items with "." notation>
Decision is to renumber to use new numbers never used before.
Action: dieter to update the spec to remove "." from assertion lables
Test assertions need to be updated
Action: sanjay to update the TA doc to sync up with the new CD rev
Already have the revised specification draft
Feb 4 - Update Test Assertion Document
Mar 4 - Test Case Creation
Mar 25 - Review and finalization of Test Cases
Apr 1 - Go for 2nd PR
Are there new assertions needed as well as updates to existing ones?
Yes, new ones are needed.
So ~5 assertions will be impacted
"The WS-BPEL specification requires that the variable initialization logic in scopes that contain (or whose children contain)
activity use only idempotent functions in the from-spec. In SCA, WS-BPEL process variables which are associated with either
SCA properties or with SCA multi-valued references have their values set by the SCA runtime based on the configuration of
SCA domain composite for the component which uses the process as its implementation. Idempotency applies for a given
configuration of the SCA domain composite - but if the configuration of the SCA domain composite changes, then the values
of properties or of references can change. The SCA Assembly specification allows for a variety of SCA runtime designs,
including ones that permit the configuration of the SCA domain-level composite to change dynamically. See the SCA Assembly
specification [ASSEMBLY], specifically the sections on "Domain-Level Composite" (10.7), "Dynamic Behaviour of Wires in the
(10. and "Dynamic Behaviour of Component Property Values" (10.9) for details. For such runtimes, the values of properties
muti-valued references can change with a change in the configuration of the Domain-level composite."
Danny discusses his concern, relating to statements in the BPEL specification.
Martin C damn pressed wrong button and hung up instead of mute
Motion passes unanimously
Resolution: issue 61 resolved with wordings in http://lists.oasis-open.org/archives/sca-bpel/201001/msg00014.html added at the the end
of Section 3.1
Schreiber diagnostics output
[Delete this section before publishing the minutes]
final validation: Title not specified, default title 'OASIS SCA-BPEL TC...' was assumed
citation-detection-scribed: Line 144: Check for possible unrecognized nick 'Planned schedule'
statistics: Schreiber found 124 input lines
edits: Schreiber found the following text-edit commands:
edits: Line 189: MikeEdwards: s/resoved/resolved/
citation-detection-irc1: Line 13: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 34: Check for possible unrecognized nick 'Planned schedule'
citation-detection-irc1: Line 51: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 52: Check for possible unrecognized nick 'RAISER'
citation-detection-irc1: Line 53: Check for possible unrecognized nick 'Anishs proposal'
citation-detection-irc1: Line 54: Check for possible unrecognized nick 'Email discussion'
citation-detection-irc1: Line 57: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 58: Check for possible unrecognized nick 'Email discussion'
command-scribe: Line 70: Mike Edwards recognized
command-scribe: Schreiber detected that this section was scribed online
citation-detection-irc1: Line 99: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 159: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 160: Check for possible unrecognized nick 'RAISER'
citation-detection-irc1: Line 161: Check for possible unrecognized nick 'Anishs proposal'
citation-detection-irc1: Line 162: Check for possible unrecognized nick 'Email discussion'
edit-substitute: command on line 189 succeeded, changed line 187 from 'resoved' to 'resolved'
edit-delete: Line 189 was deleted
system: Transformer: SAXON 184.108.40.206
[End of Schreiber diagnostic output]