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: Formatted minutes of 2009-04-02 telcon


Attached.
Thanks to Danny for scribing.

-Anish
--
Title: SCA-BPEL - 2009-04-02

OASIS Logo

- DRAFT -

OASIS SCA-BPEL TC

02 APR 2009

Attendees

Present
Michael Rowley, (Active Endpoints, Inc.)
Dave Booz, (IBM)
Mike Edwards, (IBM)
Dieter Koenig, (IBM)
Martin Chapman, (Oracle Corporation)
Khanderao Kand, (Oracle 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
Sanjay Patil
Scribe
Danny van der Rijn
Agenda:
http://lists.oasis-open.org/archives/sca-bpel/200904/msg00002.html

Contents

Topics
[1]  approval of minutes
[2]  AI review
[3]  Testing Schedule
[4]  New Issues (PR Issues). Issue 30 http://www.osoa.org/jira/browse/BPEL-30
[5]  Test assertion doc and testing
Table of Resolutions
Table of Action Items

Action Items

New:
2009-04-02-1: Sanjay to open the issue
2009-04-02-2: Sanjay to reword SBL-TA-SP01 to reflect new tighter spec languageanish i think finishing review of TAs by next week is not going to happen

Resolutions


Minutes

<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 Mar 26, 2009 minutes
http://lists.oasis-open.org/archives/sca-bpel/200903/msg00060.html
5. Action Items review
#0059 Anish - Create Test Assertions for conformance items until SBPEL2020
#0060 Khanderao - Create Test Assertions for conformance items - SBPEL2021 to SBPEL3010
6. Testing schedule
We are past the previous schedule dates. We need a new schedule.
Proposal:
Review completed Test Assertions: 4/9/09 ?
TestCases complete : 4/30/09 ?
Public review draft ready : end of spec PR (5/31/09) ?
1st Public review complete : 60 days after start (7/31/09) ?
This would have to be synced with assembly schedule as it provides the necessary testing infrastructure.
7. New issues (PR Issues)
a. Issue 30 - Schema contains ##any for
http://www.osoa.org/jira/browse/BPEL-30
8. Test assertion doc and testing
3rd draft: http://lists.oasis-open.org/archives/sca-bpel/200903/msg00056.html
9. AOB

Scribe: Danny van der Rijn

approval of minutes

 
minutes approved
Resolution: Minutes of 2009-03-26 located at http://lists.oasis-open.org/archives/sca-bpel/200903/msg00060.html approved

AI review

 
Neither Anish nor Khaderao had time to get to theirs. Both actions remain open

Testing Schedule

 
Proposal -- Sanjay: target for first milestone (4/9) may still be achievable. Other dates would be used to trigger discussions with liason committee.

New Issues (PR Issues). Issue 30 http://www.osoa.org/jira/browse/BPEL-30

Anish:
Issue has been raised by Dave, and in other TCs.
MichaelR:
Isn't ##any used for forward compatibility
 
Motion: Open issue and close with proposal in email (m:Danny, s:Najeeb)
Anish:
Not for UPA, for scope extensibility. If we define our attribute, we define how it's used. WRT to future version allowing use of a new attribute, this would only come into play if the SBPEL namespace weren't changed.
 
Michael: Are we going to allow any possibility for a backward compatible change? Determination by SCA seems to be not. Who are we in BPEL to say ##otherwise?
 
Motion carries unanimously
Resolution: issue 30 resolved with proposal in JIRA

Test assertion doc and testing

<anish>
Sanjay:
Anish posted most current version last night, as above
<anish>
<Sanjay>
SBL-TA-SP01
<anish>
 
Mike: Where are the 2 attributes attached?
Sanjay:
Question originates in spec ambiguity.
<Sanjay>
The partnerLinkType and partnerRole attributes of the <partnerLink> and the child element <sca-bpel:multiReference> of the associated multi-valued reference variable MUST be matched.
 
Mike: An issue needs to be raised. Wording needs to be much more specific. Still don't like wording - isn't specific enough
<anish>
The @partnerLinkType and @partnerRole attributes of the <partnerLink> and the child element <sca-bpel:multiReference> of the associated multi-valued reference variable MUST be matched.
Sanjay:
Agree with Mike. Need to be more clear. Need an action to open the issue
Action: Sanjay to open the issue
<Michael Rowley>
The partnerLinkType and partnerRole attributes of the partner link MUST be the same as the partnerLinkType and partnerRole attributes of the <sca-bpel:multiReference> child element of the variable named by the @multiRefFrom attribute of the partner link.
<anish>
The partnerLinkType and partnerRole attributes of the <partnerLink> MUST be the same as the partnerLinkType and partnerRole attributes of the <sca-bpel:multiReference> child element of the variable named by the @multiRefFrom attribute of the partner link.
Anish:
Does the wording above seem right? Should we try to resolve this now?
<anish>
it would be issue #31
Sanjay:
Question about last clause: "named by ..." part - is it precise enough to be spec language?
<anish>
The partnerLinkType and partnerRole attributes of the <partnerLink> MUST be the same as the partnerLinkType and partnerRole attributes of the <sca-bpel:multiReference> child element of the variable named by the @multiRefFrom attribute of the <partnerLink>.
MichaelR:
Will get harder to read if we try to add variable reference semantics
anish added more angle bracket
<anish>
how about s/named/identified/
<anish>
The partnerLinkType and partnerRole attributes of the <partnerLink> MUST be the same as the partnerLinkType and partnerRole attributes of the <sca-bpel:multiReference> child element of the variable whose @name value is same as the value of the @multiRefFrom attribute of the <partnerLink>.
<Michael Rowley>
Title -- SBPEL3011 Assertion needs to be clarified
<Michael Rowley>
he assertion:
[SBPEL3011] The partnerLinkType and partnerRole attributes of the partner link and multi-valued reference variable MUST be matched.
is vague.
Proposal:
It should be changed to the following:
[SBPEL3011] The partnerLinkType and partnerRole attributes of the <partnerLink> MUST be the same as the partnerLinkType and partnerRole attributes of the <sca-bpel:multiReference> child element of the variable whose @name value is same as the value of the @multiRefFrom attribute of the <partnerLink>.
 
Motion: To open an issue with title and body as pasted into room above (m: Michael Rowley, s: Anish)
<anish>
This is issue 31
 
Motion carries unanimously
 
Motion: Resolve new issue according to proposal (m:Michael Rowley, s: Khanderao)
 
Motion carries unanimously
Resolution: issue 31 resolved with proposal in JIRA
Sanjay:
Back to test assertions...
Action: Sanjay to reword SBL-TA-SP01 to reflect new tighter spec languageanish i think finishing review of TAs by next week is not going to happen
 
On to SBL-TA-SP02
 
Mike: Not testing a runtime anymore - you have to make a test runtime.
 
+1
Sanjay:
SBL-TA-SP03
<Sanjay>
Title -- SBPEL3013 and SBPEL3014 use of RFC2119 'MAY' incorrectly
<Sanjay>
Proposal: Use alternative wording for RFC 2119 'MAY' e.g. 'can'.
 
Motion: Open a new issue, with title and proposal as typed above by Sanjay. (m: Sanjay, s: Danny)
 
Motion carries unanimously (Issue # will tentatively be 32)
Resolution: Issue 33 is opened
Anish:
AOB?
Anish:
Adjourned

[End of Minutes]
Formatted on 2009-04-08 at 21:42:55 GMT-8


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 66: Check for possible unrecognized nick 'Motion'

citation-detection-scribed: Line 70: Check for possible unrecognized nick 'Michael'

citation-detection-scribed: Line 88: Check for possible unrecognized nick 'Mike'

citation-detection-scribed: Line 94: Check for possible unrecognized nick 'Mike'

citation-detection-scribed: Line 137: Check for possible unrecognized nick 'Motion'

citation-detection-scribed: Line 143: Check for possible unrecognized nick 'Motion'

citation-detection-scribed: Line 156: Check for possible unrecognized nick 'Mike'

citation-detection-scribed: Line 166: Check for possible unrecognized nick 'Motion'

statistics: Schreiber found 108 input lines

edits: Schreiber found the following text-edit commands:

edits: Line 96: anish: s/partner link/<partnerLink>

edits: Line 168: Danny van der Rijn: s/description/proposal/

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

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

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

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

citation-detection-irc1: Line 32: Check for possible unrecognized nick '3rd draft'

command-scribe: Line 37: Danny van der Rijn recognized

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

edit-substitute: command on line 96 succeeded, changed line 92 from 'partner link' to '<partnerLink>'

edit-delete: Line 96 was deleted

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

edit-substitute: command on line 168 succeeded, changed line 166 from 'description' to 'proposal'

edit-delete: Line 168 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]