Formatted minutes of 2009-09-17 telcon

[Anish Karmarkar <Anish.Karmarkar@oracle.com>]

Attached.
Thanks to Dieter for scribing.

-Anish
--

Title: SCA-BPEL - 2009-09-17

Hide IRC

- DRAFT -

OASIS SCA-BPEL TC

17 SEP 2009

Attendees

Chair

Anish Karmarkar

Scribe

Dieter Koenig

Agenda:

http://lists.oasis-open.org/archives/sca-bpel/200909/msg00023.html

---

Contents

Topics

Table of Resolutions

Table of Action Items

---

Action Items

New:

2009-09-17-1: Najeeb to update XML Schema artifacts in spec appendix and SVN where necessary (according to the resolution of issue BPEL-52)

2009-09-17-2: Anish to ask MikeE for an updated proposal

---

Resolutions

• 2009-09-17-1: Minutes of 2009-09-10 located at http://lists.oasis-open.org/archives/sca-bpel/200909/msg00019.html approved w/o
• 2009-09-17-2: Issue 59 opened
• 2009-09-17-3: issue 53 resolved with the proposal at http://lists.oasis-open.org/archives/sca-bpel/200908/msg00021.html
• 2009-09-17-4: issue 54 closed with no action
• 2009-09-17-5: issue 55 resolved with proposal in the chat

---

Minutes

<anish>

agenda --

<anish>

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 Sep 10, 2009 minutes
http://lists.oasis-open.org/archives/sca-bpel/200909/msg00019.html
5. Action Items review
#106 AnishK file an issue about what a conformant runtime does when a non-conformant SCA BPEL doc is provided
DONE
6. New Issues
http://osoa.org/jira/browse/BPEL-59
7. Issue Discussion
a) Issue 53 - BPEL Process: References with Multiplicity 0..1 - how are they supposed to work?
http://osoa.org/jira/browse/BPEL-53
Proposal: http://lists.oasis-open.org/archives/sca-bpel/200908/msg00021.html
b) Issue 54 - sca-bpel:multiReference/@partnerLinkType and sca-bpel:multiReference/@partnerRole cardinality
http://osoa.org/jira/browse/BPEL-54
Proposal: in Jira
c) Issue 55 - Co-occurrence constraints on sca-bpelroperty attribute and sca-bpel:multiReference element
http://osoa.org/jira/browse/BPEL-55
Proposal: in Jira
d) Issue 46 - SBPEL3006 isn't deterministic
http://osoa.org/jira/browse/BPEL-46
no proposal
e) Issue 50 - Need more examples in the specification
http://osoa.org/jira/browse/BPEL-50
no proposal
f) 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
8. Testing
9. AOB

<anish>

7 out of 9 VM present -- quorate

Scribe: Dieter Koenig

 

3. Agenda bashing

 

Agenda approved without objection

 

4. Approval of Sep 10, 2009 minutes
http://lists.oasis-open.org/archives/sca-bpel/200909/msg00019.html

 

Minutes approved without objection

Resolution: Minutes of 2009-09-10 located at http://lists.oasis-open.org/archives/sca-bpel/200909/msg00019.html approved w/o

 

5. Action Items review
#106 AnishK file an issue about what a conformant runtime does when a non-conformant SCA BPEL doc is provided
DONE

 

6. New Issues
http://osoa.org/jira/browse/BPEL-59

 

How does a SCA Extended WS-BPEL Runtime deal with a non-conformant BPEL process?

 

This is about conformance w.r.t. SCA-BPEL (not WS-BPEL 2.0)

<Martin C>

i think we should open the issue, regardless of the solution

<Martin C>

anish you are achoing bad

 

Is this the switch we talk about:
<bpel:extension namespace="http://docs.oasis-open.org/ns/opencsa/sca-bpel/200801" mustUnderstand="yes|no" />

 

Motion (Martin), second (Danny): open issue BPEL-59

 

Motion passed without objection - issue BPEL-59 opened

Resolution: Issue 59 opened

 

7. Issue Discussion

 

7. a) Issue 53 - BPEL Process: References with Multiplicity 0..1 - how are they supposed to work?
http://osoa.org/jira/browse/BPEL-53
Proposal: http://lists.oasis-open.org/archives/sca-bpel/200908/msg00021.html

<anish>

new wordings: 3. Stub Reference. [SBPEL2012] If [SBPEL2010] does not apply and the partner link has initializePartnerRole="no", then the multiplicity MUST be "0..1" and the attribute wiredByImpl MUST be set to "true".

 

Motion (Danny), second (Dieter): resolve BPEL-53 as shown in http://lists.oasis-open.org/archives/sca-bpel/200908/msg00021.html

 

Motion passed without objection - issue BPEL-53 resolved

Resolution: issue 53 resolved with the proposal at http://lists.oasis-open.org/archives/sca-bpel/200908/msg00021.html

 

Kanderao asks for LOA from Oct 1 to Oct 10

 

Note that LOA requests need to be sent to the TC as well
Martin C had to drop for another call

 

Note to editors: always keep XML Schema artifacts in spec appendix and SVN in sync

 

New Action Item for Najeeb: update XML Schema artifacts in spec appendix and SVN where necessary (according to the resolution of issue BPEL-52)

Action: Najeeb to update XML Schema artifacts in spec appendix and SVN where necessary (according to the resolution of issue BPEL-52)

 

7. b) Issue 54 - sca-bpel:multiReference/@partnerLinkType and sca-bpel:multiReference/@partnerRole cardinality
http://osoa.org/jira/browse/BPEL-54
Proposal: in Jira

 

Issue seems obsolete as the attributes have been removed in a resolution of issue BPEL-52

 

Motion (Najeeb), second (Dieter): resolve BPEL-54 by closing with no action

 

Motion passed without objection - issue BPEL-54 closed with no action

Resolution: issue 54 closed with no action

 

7. c) Issue 55 - Co-occurrence constraints on sca-bpelroperty attribute and sca-bpel:multiReference element
http://osoa.org/jira/browse/BPEL-55
Proposal: in Jira

<anish>

In the introspected component type a variable cannot be both an SCA property and an SCA reference. [SBPELXXXX] A BPEL variable declaration MUST NOT have both the sca-bpelroperty extension attribute with a value of "yes" and the sca-bpel:multiReference extension child element.

 

Motion (Dieter), second (Danny): resolve BPEL-55 as shown above

 

Motion passed without objection - issue BPEL-55 resolved

Resolution: issue 55 resolved with proposal in the chat

 

7. d) Issue 46 - SBPEL3006 isn't deterministic
http://osoa.org/jira/browse/BPEL-46
no proposal

 

Discussion postponed

 

7. e) Issue 50 - Need more examples in the specification
http://osoa.org/jira/browse/BPEL-50
no proposal

 

Discussion postponed

 

7. f) 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

 

Idea: provide an attribute which signals that the partner link should be ignored

 

... that is, not considered by SCA as a reference or service

 

Mike R.: This can be useful if SCA is used in conjunction with other extensions

 

If inbound and outbound interactions are performed using non-SCA means then "skip" seems useful

 

General agreement that this capability is helpful

 

Anish to ask Mike E. for an updated proposal

Action: Anish to ask MikeE for an updated proposal

 

9. AOB

 

None

 

Meeting adjourned

[End of Minutes]
Formatted on 2009-09-22 at 11:39:10 GMT-7

---

Minutes formatted by Schreiber, a collection of XSLT stylesheets by Bob Freund modeled after David Booth's scribe

---

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 116: Check for possible unrecognized nick 'Note to editors'

citation-detection-scribed: Line 161: Check for possible unrecognized nick 'Idea'

citation-detection-scribed: Line 165: Check for possible unrecognized nick 'Mike R.'

statistics: Schreiber found 109 input lines

edits: Schreiber found no text-edit commands

citation-detection-irc1: Line 4: Check for possible unrecognized nick 'http'

citation-detection-irc1: Line 12: Check for possible unrecognized nick 'http'

citation-detection-irc1: Line 19: Check for possible unrecognized nick 'http'

citation-detection-irc1: Line 24: Check for possible unrecognized nick 'http'

citation-detection-irc1: Line 25: Check for possible unrecognized nick 'Proposal'

citation-detection-irc1: Line 28: Check for possible unrecognized nick 'http'

citation-detection-irc1: Line 29: Check for possible unrecognized nick 'Proposal'

citation-detection-irc1: Line 32: Check for possible unrecognized nick 'http'

citation-detection-irc1: Line 33: Check for possible unrecognized nick 'Proposal'

citation-detection-irc1: Line 36: Check for possible unrecognized nick 'http'

citation-detection-irc1: Line 40: Check for possible unrecognized nick 'http'

citation-detection-irc1: Line 44: Check for possible unrecognized nick 'http'

citation-detection-irc1: Line 45: Check for possible unrecognized nick 'Email discussion'

command-scribe: Line 61: Dieter Koenig recognized

command-scribe: Schreiber detected that this section was scribed online

citation-detection-irc1: Line 68: Check for possible unrecognized nick 'http'

citation-detection-irc1: Line 78: Check for possible unrecognized nick 'http'

citation-detection-irc1: Line 89: Check for possible unrecognized nick '<bpel'

citation-detection-irc1: Line 99: Check for possible unrecognized nick 'http'

citation-detection-irc1: Line 100: Check for possible unrecognized nick 'Proposal'

citation-detection-irc1: Line 122: Check for possible unrecognized nick 'http'

citation-detection-irc1: Line 123: Check for possible unrecognized nick 'Proposal'

citation-detection-irc1: Line 134: Check for possible unrecognized nick 'http'

citation-detection-irc1: Line 135: Check for possible unrecognized nick 'Proposal'

citation-detection-irc1: Line 146: Check for possible unrecognized nick 'http'

citation-detection-irc1: Line 152: Check for possible unrecognized nick 'http'

citation-detection-irc1: Line 158: Check for possible unrecognized nick 'http'

citation-detection-irc1: Line 159: Check for possible unrecognized nick 'Email discussion'

system: Transformer: SAXON 9.0.0.2

[End of Schreiber diagnostic output]