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 2008-05-08 telcon


Attached.
Thanks to Najeeb for scribing.

-Anish
--
Title: SCA-BPEL - 2008-05-08

OASIS Logo

- DRAFT -

OASIS SCA-BPEL TC telcon

08 MAY 2008

Attendees

Present
Mike Edwards, (IBM)
Dieter Koenig, (IBM)
Simon Moser, (IBM)
Khanderao Kand, (Oralce Corporation)
Anish Karmarkar, (Oracle Corporation)
Ashok Malhotra, (Oracle Corporation)
Sanjay Patil, (SAP AG*)
Najeeb Andrabi, (TIBCO Software Inc.)
Danny van der Rijn, (TIBCO Software Inc.)
Chair
Anish Karmarkar
Scribe
Najeeb Andrabi
Agenda:
http://lists.oasis-open.org/archives/sca-bpel/200805/msg00005.html

Contents

Topics
[1]  agenda bashing
[2]  approval of 2008-05-01 minutes
[3]  Action item review
[4]  New issues discussion
[5]  Issue #21
[6]  Issue 20 discussion
Table of Resolutions
Table of Action Items

Action Items

New:
2008-05-08-1: Anish to amend Danny's proposal to resolve issue 20.

Resolutions


Minutes

Scribe: Najeeb Andrabi

<Sanjay>
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 may 1, 2008 minutes

http://lists.oasis-open.org/archives/sca-bpel/200805/msg00004.html

5. Action items review
http://www.oasis-open.org/apps/org/workgroup/sca-bpel/members/action_items.php

a) AI #0021
Chairs - to follow up with Mary to post the CD docs to OASIS repository
b) AI #0035 (Due date 5/
Dieter - Create a proposal for Issue 16 - Ambiguous Service Resolution
c) AI #0037
Anish - update the assembly RDDL file, file names and the references in the spec

6. New Issues

NONE

7. Status of JIRA
Update from issues editor

8. Issue Discussion

a) Issue 21 http://www.osoa.org/jira/browse/BPEL-21
Given the resolution of issue 14, can we close this?

b) Issue 20 http://www.osoa.org/jira/browse/BPEL-20
SCA-BPEL spec can not require bpel:mustUnderstand to be true
(proposal in JIRA)

c) Issue 15 http://www.osoa.org/jira/browse/BPEL-15
TITLE- Define Conformance Targets
SUBMITTED BY- Martin Chapman
http://lists.oasis-open.org/archives/sca-bpel/200803/msg00000.html
http://lists.oasis-open.org/archives/sca-bpel/200803/msg00014.html
http://lists.oasis-open.org/archives/sca-bpel/200803/msg00048.html
http://lists.oasis-open.org/archives/sca-bpel/200804/msg00001.html
http://lists.oasis-open.org/archives/sca-bpel/200804/msg00021.html
Review of section 2.1 from CD-01-rev3 at
http://lists.oasis-open.org/archives/sca-bpel/200804/msg00026.html

d) Issue 18 http://www.osoa.org/jira/browse/BPEL-18
TITLE- Need to rewrite the SCA-BPEL specifications with RFC-2119
keywords/statements
SUBMITTED BY- KHANDERAO KAND

e) Issue 16 http://osoa.org/jira/browse/BPEL-16
TITLE- Ambigous Service Resolution
SUBMITTED BY- Dieter Koenig


9. AOB

agenda bashing

 
Agenda approved

approval of 2008-05-01 minutes

<anish>
 
May 1st minutes approved.
Anish:
suggesting changing minutes in-order to strike word 'possible' in May 1st minutes
 
May 1st minutes approved with change above

Action item review

 
AI #0021
Chairs - to follow up with Mary to post the CD docs to OASIS repository
 
remains pending
Dieter:
If anyone else can volunteer for creating the proposal
Danny:
suggested to close the action item with no action
Dieter:
Can produce a proposal for AI# 0021 May 29th
 
AI #0037 remains pending - RDDL files needs to be uploaded.

New issues discussion

 
no new issues
 
Issue discussion

Issue #21

Anish:
We have decided that we would put all attributes in the same namespace
<anish>
Anish:
Opened Issue 21 to be separate from Issue 14.
<Sanjay>
m: close BPEL-21 with no action and add a comment to reference BPEL-20
Sanjay:
Moves to close issue 21 with no action with reference to Issue 20
 
Dieter seconds
 
Motion passes
Resolution: BPEL-21 closed with no action. Issue list to be updated to point 21 to issue 20.
 
Issue #21 resolved

Issue 20 discussion

<anish>
Danny:
Issue 20 proposal is not complete.
Danny:
mustUnderstand is reflection of actual BPEL process: whether BPEL process can run that construct
Danny:
two use cases
 
if mustUnderstand = true then process cannot run if the BPEL processor cannot understand the attribute
 
If mustUnderstand = false the process will run with potential of runing an invalid process
Danny:
we should not make mustUnderstand = true but make it flexible so that BPEL process does not have to understand.
Dieter:
if BPEL variables as sca properties are not understood they will not be intialized
Anish:
Agrees with Danny, the must understand attributes must be left to the authors of BPEL process
Anish:
update the proposal to reflect when to set mustUnderstand = true/false
Danny:
It is would nice to update the proposal but it is already well defined in BPEL specifications.
 
specification
<anish>
we have the following attributes: multiref, property, service, reference and intent in our NS
<Danny>
and there was silence...
<Sanjay>
sounds like we need a proposal
Anish:
go over each BPEL sca extension attributes so that we can figure out whether they are required or not
Anish:
reference can be required, but may not be attribute as it can define a value 0..1 implying that it needs to be wired
Sanjay:
Whether BPEL process understand is one way looking at it; other way looking at is to take into account the intent of the developer of the BPEL process.
Anish:
mustUnderstand= true/false is more of guidance issue.
Sanjay:
Introduce a short paragraph to explain that it depends on the context user is running BPEL process
Danny:
mustUnderstand= true also restricts portability as BPEL process running in SCA context cannot be ported to non SCA environment without editing the BPEL file and changing mustUnderstand = false.
Anish:
Providing some guidance for mustUnderstand attribute would be useful.
<Mike Edwards>
I think we are making far too much of this issue
Mike Edwards:
we should not require mustUnderstand = true.
Anish:
Danny to craft a proposal to resolve this issue
 
Danny moves to accept this proposal that is in JIRA
 
Sanjay seconds
Action: Anish to amend Danny's proposal to resolve issue 20.

[End of Minutes]
Formatted on 2008-05-08 at 17:33:56 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]

statistics: Schreiber found 134 input lines

edits: Schreiber found the following text-edit commands:

edits: Line 228: anish: s/multiref reference is required/reference can be required, but may not be/

command-scribe: Line 2: Najeeb Andrabi recognized

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

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

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

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

citation-detection-irc1: Line 82: Check for possible unrecognized nick 'a) Issue 21 http'

citation-detection-irc1: Line 88: Check for possible unrecognized nick 'b) Issue 20 http'

citation-detection-irc1: Line 96: Check for possible unrecognized nick 'c) Issue 15 http'

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

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

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

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

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

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

citation-detection-irc1: Line 118: Check for possible unrecognized nick 'd) Issue 18 http'

citation-detection-irc1: Line 128: Check for possible unrecognized nick 'e) Issue 16 http'

edit-substitute: command on line 228 succeeded, changed line 226 from 'multiref reference is required' to 'reference can be required, but may not be'

edit-delete: Line 228 was deleted

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]