OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

sca-bpel message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Formated minutes of 2009-08-06 telcon


Attached.
Thanks to MikeR for scribing.

-Anish
--
Title: SCA-BPEL - 2009-08-06

OASIS Logo

- DRAFT -

OASIS SCA-BPEL TC

06 AUG 2009

Attendees

Present
Michael Rowley, (Active Endpoints, Inc.)
Mike Edwards, (IBM)
Dieter Koenig, (IBM)
Martin Chapman, (Oracle Corporation)
Khanderao Kand, (Oracle Corporation)
Anish Karmarkar, (Oracle Corporation)
Sanjay Patil, (SAP AG)
Najeeb Andrabi, (TIBCO Software Inc.)
Danny van der Rijn, (TIBCO Software Inc.)
Chair
Anish Karmarkar
Scribe
Michael Rowley

Contents

Topics
[1]  New Issue
[2]  submission of eventing extension to BPEL
[3]  Issue 49
[4]  Issue 52
Table of Resolutions
Table of Action Items

Action Items

New:
2009-08-06-1: MikeR will write an email with a proposal for issue 53

Resolutions


Minutes

<anish>
****** Note the new callin numbers *****
<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 Jul 23, 2009 minutes
http://lists.oasis-open.org/archives/sca-bpel/200907/msg00039.html
5. Action Items review
#0096 Anish - Create proposal for issue 41
PENDING
#0100 MikeR - Create a new proposal for issue 52
DONE
6. New Issues
NONE
7. BPEL Extensions for Eventing and Pub/Sub contribution
http://lists.oasis-open.org/archives/sca-bpel/200908/msg00002.html
8. Issue Discussion
5 open issues
a) Issue 49
BPEL process QName is assumed to be unique
http://www.osoa.org/jira/browse/BPEL-49
Proposal: http://lists.oasis-open.org/archives/sca-bpel/200907/msg00029.html
b) Issue 52
CT generation (section 2.1.1) does not take into consideration the multRefFrom attribute
http://osoa.org/jira/browse/BPEL-52
Proposal: http://lists.oasis-open.org/archives/sca-bpel/200907/msg00037.html
c) Issue 46
SBPEL3006 isn't deterministic
http://osoa.org/jira/browse/BPEL-46
d) Issue 41
SBPEL2022 has an incorrect 'MAY' and is not applied recursively
http://www.osoa.org/jira/browse/BPEL-41
Email discussion -
http://lists.oasis-open.org/archives/sca-bpel/200905/msg00035.html
http://lists.oasis-open.org/archives/sca-bpel/200905/msg00041.html
http://lists.oasis-open.org/archives/sca-bpel/200905/msg00044.html
9. AOB
<anish>

Scribe: Michael Rowley

 
Scribing
<Khanderao>
Hi
<Khanderao>
Did call detail change?
<Khanderao>
Not able to dial in.
<Sanjay>
US
18666824770
+14087744073
UK
+44(0)2081181001
+44(0)8444936817
08006948154
DE
+49(0)69222216106
08006648515
IE
+353(0)12475650
1800932479
Conference code: 6100473
Password: SCABPEL (7222735)
 
Agenda approved.
 
Minutes approved.
<Khanderao>
joined.
 
Both action items are done (96 & 100)

New Issue

<Mike Edwards>
 
 
MikeE moves MikeR seconds opening issue 53
 
unanimous approval
Resolution: Issue 53 is opened
Action: MikeR will write an email with a proposal for issue 53

submission of eventing extension to BPEL

Issue 49

<anish>
<anish>
the proposal says -- I'm inclined to not treat BPEL different from any other XML definition. Perhaps my proposed new sentence should be changed to remove the requirement that resolution results in a single process. So, it would be:
"SCA's artifact resolution mechanism, defined in section 11.2 of the SCA Assembly Specification, MUST be used to resolve the specified QName to a WS-BPEL process."
Then, whatever the assembly specification requires or allows with respect to uniqueness and/or implementation dependent mechanisms, we also use.
 
The proposal is to add it as the last sentence of section 1 (just prior to 1.1)
 
MikeR moves & Dieter seconds that we resolve 49 with the proposal above.
 
Motion passes without objection.
Resolution: issue 49 resolved with proposal in the chat

Issue 52

<anish>
 
The introspected component type also includes references for variables that are annotated with an sca-bpel:multiReference attribute. [SBPEL3006] The introspected component type MUST include a reference with a multiplicity of either "0..n" or "1..n" that corresponds to a variable with the sca-bpel:multiReference element. [SBPEL3007] The type of the reference MUST be determined by the partner link type and the partner role attributes of the sca-bpel:multiReferenceFrom extension element.
 
The introspected component type also includes references for variables that are annotated with an sca-bpel:multiReference attribute. [SBPEL3006] The introspected component type MUST include a reference with a multiplicity of either "0..n" or "1..n" that corresponds to a variable with the sca-bpel:multiReference element. [SBPEL3007] The type of the reference MUST be determined by the partner link type and the partner role attributes of the sca-bpel:multiReference extension element.
<Dieter Koenig>
Line 284: To assist a more effective SCA modeling ...
<Dieter Koenig>
Type compatibility of SCA sca:reference and BPEL plnkartnerLinkType/plnk:role ...
anish time check
Danny van der Rijn sorry - had to drop
 
Proposal amendment: Change 2.1.1 so that any partner link with MultiRefFrom attribute is not made into a service or reference and the partner link must not include a sca:reference or sca:service annotation.
Also the <multireference> element should also include a name attribute so that people can customize the reference name that is generated.

[End of Minutes]
Formatted on 2009-08-06 at 12:09:37 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

statistics: Schreiber found 104 input lines

edits: Schreiber found no text-edit commands

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

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

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

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

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

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

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

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

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

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

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

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

command-scribe: Line 59: Michael Rowley recognized

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

citation-detection-irc1: Line 87: Check for possible unrecognized nick 'Conference code'

citation-detection-irc1: Line 88: Check for possible unrecognized nick 'Password'

system: Transformer: SAXON 9.0.0.2

[End of Schreiber diagnostic output]



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]