Raw text minutes for SCA BPEL TC of 21st Jan

Folks,

Here is the raw text:

Agenda -

1. Roll Call

http://www.oasis-open.org/apps/org/workgroup/sca-bpel/members/roster.php

2. Appointment of scribe

Scribe list attached below

3. Agenda bashing

4. Approval of 2010-01-14 minutes

5. Review of Action Items

#0109 Mike Edwards - Send instructions for running the Assembly tests

#0115 Mike Edwards - 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)

6. New Issues

None

7. Testing

Planned schedule:

Jan 21 - 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

a> Planning/volunteers for updating the test assertions document

b> MikeE to send instructions for running the tests

Here is a rough break up of work for creating the test cases. More volunteers
are appreciated.

Sanjay - SBL-TA-1001 to SBL-TA-2018

Anish - SBL-TA-3001 to SBL-TA-3026

8. Issue Discussion

a) Issue 61 - Need to deal with variable initialization not being idempotent

http://osoa.org/jira/browse/BPEL-61

RAISER: Danny van der Rijn

Anishs proposal: http://lists.oasis-open.org/archives/sca-bpel/201001/msg00006.html

Email discussion: http://lists.oasis-open.org/archives/sca-bpel/201001/msg00014.html

b) Issue 58 - Need to add Capability to indicate that a PartnerLink should
be ignored when introspecting the ComponentType of a BPEL process

http://www.osoa.org/jira/browse/BPEL-58

Email discussion: http://lists.oasis-open.org/archives/sca-bpel/200909/msg00016.html

Awaiting a new proposal from MikeE based on 2009-10-29 concall discussions

9. AOB

anish: Agenda: http://lists.oasis-open.org/archives/sca-bpel/201001/msg00019.html

anish: Date: 2010-01-21

anish: Chair: Anish Karmarkar

anish: scribe: Mike Edwards

anish: ScribeNick: Mike
Edwards

Mike Edwards: Item 3 Agenda
Bashing

Mike Edwards: No changes

Mike Edwards: Item 4 Approval
of Minutes from Previous Meeting

anish: http://lists.oasis-open.org/archives/sca-bpel/201001/msg00009.html

Mike Edwards: Minutes are
approved without objection

Mike Edwards: Item 5 Action
Items

Mike Edwards: #0109 Mike
Edwards - Send instructions for running the Assembly tests

#0115 Mike Edwards - 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)

Mike Edwards: Item #0109
is still outstanding - Mike debugging the Tuscany BPEL runtime at the moment

Mike Edwards: Item #115
now transferred to Anish, still outstanding

Dieter Koenig: SCA-BPEL
1.1 CD02 Revision 6: 

http://www.oasis-open.org/apps/org/workgroup/sca-bpel/download.php/35952/sca-bpel-1.1-spec-cd02-rev6.zip

Mike Edwards: Item #0117
still outstanding

Dieter Koenig: Affected
rules:

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]

Mike Edwards: Anish:  SBPEL3010.1
needs to be renamed to a "regular" numbering, just like the other
ones

Mike Edwards: - just use
a free number in the range

Dieter Koenig: rename [SBPEL2004.1]
and [SBPEL3010.1]

Mike Edwards: <discussion
of the approach to renumbering the conformance items with "."
notation>

Mike Edwards: Decision is
to renumber to use new numbers never used before.

anish: ACTION: dieter to
update the spec to remove "." from assertion lables

Mike Edwards: Test assertions
need to be updated

anish: ACTION: sanjay to
update the TA doc to sync up with the new CD rev

Mike Edwards: Item 7 Testing

Mike Edwards: Already have
the revised specification draft

Mike Edwards: Remaining
schedule:

Mike Edwards: Planned schedule:

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

Mike Edwards: Sanjay: Are
there new assertions needed as well as updates to existing ones?

Mike Edwards: Anish: Yes,
new ones are needed.

Mike Edwards: Sanjay: So
~5 assertions will be impacted

Mike Edwards: Item 8 Existing
Issues

Mike Edwards: Issue 61 -
Need to deal with variable initialization not being idempotent

http://osoa.org/jira/browse/BPEL-61

RAISER: Danny van der Rijn

Anishs proposal: http://lists.oasis-open.org/archives/sca-bpel/201001/msg00006.html

Email discussion: http://lists.oasis-open.org/archives/sca-bpel/201001/msg00014.html

anish: http://lists.oasis-open.org/archives/sca-bpel/201001/msg00014.html

anish: "The WS-BPEL
specification requires that the variable initialization logic in scopes
that contain (or whose children contain) a start

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 the

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 SCA
Domain"

(10.
and "Dynamic Behaviour of Component Property Values" (10.9) for
details. For such runtimes, the values of properties and of

muti-valued references can change with a change in the configuration of
the Domain-level composite."

Mike Edwards: Danny discusses
his concern, relating to statements in the BPEL specification.

Martin C damn pressed wrong
button and hung up instead of mute

Mike Edwards: Mike moves
to resolve Issue 61 with the wording in http://lists.oasis-open.org/archives/sca-bpel/201001/msg00014.html
added at the the end of Section 3.1

Mike Edwards: Dieter seconds

Mike Edwards: Motion passes
unanimously

Mike Edwards: Issue 61 is
resoved

Mike Edwards: s/resoved/resolved/

anish: 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

Mike Edwards: COB

Yours,  Mike.

Strategist - Emerging Technologies, SCA & SDO.

Co Chair OASIS SCA Assembly TC.

IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN, Great Britain.

Phone & FAX: +44-1962-818014    Mobile: +44-7802-467431  

Email:  

Unless stated otherwise above:

IBM United Kingdom Limited - Registered in England and Wales with number
741598. 

Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU