[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Raw log of 2009-04-09 telcon
anish: Date: 2009-04-09 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 Apr 2, 2009 minutes http://lists.oasis-open.org/archives/sca-bpel/200904/msg00020.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 #0062 Sanjay - Reword SBL-TA-SP01 to reflect new tighter spec language 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. Status of PR 8. New issues a. Issue 34 http://osoa.org/jira/browse/BPEL-34 Incorrect uses of RFC 2119 'MAY' in SBPEL3017 Proposal in JIRA b. Issue 35 http://osoa.org/jira/browse/BPEL-35 Incorrect uses of RFC 2119 'MAY' in SBPEL3021 Proposal in JIRA 9. PR Issue Discussion a) Issue 33 http://osoa.org/jira/browse/BPEL-35 SBPEL3013 and SBPEL3014 use of RFC2119 'MAY' incorrectly Proposal -- http://lists.oasis-open.org/archives/sca-bpel/200904/msg00016.html 10. Test assertion doc and testing Latest Draft: http://lists.oasis-open.org/archives/sca-bpel/200904/msg00003.html OR http://lists.oasis-open.org/archives/sca-bpel/200904/pdf00000.pdf 11. AOB anish: Chair: Anish Karmarkar anish: Agenda: http://lists.oasis-open.org/archives/sca-bpel/200904/msg00021.html anish: Scribe: Najeeb Andrabi anish: ScribeNick: Najeeb Andrabi Najeeb Andrabi: Agenda bashing: 2 new issues Najeeb Andrabi: Agenda approved Najeeb Andrabi: Minutes approved. Najeeb Andrabi: Action Item review: Action 60 done Najeeb Andrabi: Action item 59 and 62 pending. Najeeb Andrabi: Anish: we should use same convention for listing namespaces and prefixes. Najeeb Andrabi: Two new issues filed by Sanjay: issues 34 and 35. Najeeb Andrabi: Issue 34 discussion. Najeeb Andrabi: http://osoa.org/jira/browse/BPEL-34 Najeeb Andrabi: Mike Edwards moves to open issue 34 Najeeb Andrabi: Dieter seconds. Najeeb Andrabi: Motion passed. Issue 34 is now open. Najeeb Andrabi: Dieter moves to resolve issue 34 with the current proposal in jira. Najeeb Andrabi: Mike Edwards: Moves resolve this issue Dieter Koenig: To explicitly map a partner link to a reference, the sca-bpel:reference attribute MUST specified for the partner link. Dieter Koenig: To explicitly map a partner link to a reference, the sca-bpel:reference attribute MUST be specified for the partner link. Najeeb Andrabi: Dieter seconds. Najeeb Andrabi: Issue 34 resolved. Najeeb Andrabi: Issue 35 discussion. Najeeb Andrabi: http://osoa.org/jira/browse/BPEL-35 Najeeb Andrabi: Dieter moves to open Issue 35 Najeeb Andrabi: Dave seconds Dieter Koenig: Issue 35 Proposal: Change SBPEL3021 to read as: An SCA extension attribute sca-bpel:requires MUST be used to declare required policy intents on a partner link. Najeeb Andrabi: Issue 35 is open. Mike Edwards: Change SBPEL3021 to read as: To declare policy intents on a partner link element, the SCA extension attribute sca-bpel:requires MUST be used . Mike Edwards: Mike E moves to resolve Issue 35 with the text above Najeeb Andrabi: Dieter seconds. Najeeb Andrabi: Issue 35 resolved. Najeeb Andrabi: Issue 33 discussion anish: [SBPEL3013] A WS-BPEL process definition MAY override the default mapping of partner links to services or references as described in section 2.1 by explicitly marking the partner link with an SCA attribute that describes the service or reference. anish: [SBPEL3014] To explicitly map a partner link to a service, the sca-bpel:service attribute MAY be specified for the partner link. Najeeb Andrabi: Anish: Proposal in jira for SBPEL3013/3014 is not quite right. anish: To explicitly map a partner link to a service, the sca-bpel:service attribute MUST be specified for the partner link ? anish: for 3014 ? anish: A WS-BPEL process definition can override the default mapping of partner links to services or references as described in section 2.1 by explicitly marking the partner link with an SCA attribute that describes the service or reference (replace 3013) anish: [SBPEL3014] To explicitly map a partner link to a service, the sca-bpel:service attribute MAY be specified for the partner link. anish: [SBPEL3014] To explicitly map a partner link to a service, the sca-bpel:service attribute MUST be specified for the partner link Mike Edwards: Mike E moves to resolve issue 33 by: Mike Edwards: 1) Replacing [SBPEL3013] with Mike Edwards: A WS-BPEL process definition can override the default mapping of partner links to services or references as described in section 2.1 by explicitly marking the partner link with an SCA attribute that describes the service or reference Mike Edwards: 2) Changing [SBPEL3014] to: Mike Edwards: To explicitly map a partner link to a service, the sca-bpel:service attribute MUST be specified for the partner link Najeeb Andrabi: Dieter seconds. Najeeb Andrabi: Issue 33 resolved with proposal in the chat. Najeeb Andrabi: Test Assertion document discussion. Najeeb Andrabi: Meeting is adjourned. anish: Present+ Dave Booz, (IBM) Present+ Mike Edwards, (IBM) Present+ Dieter Koenig, (IBM) Present+ Martin Chapman, (Oracle Corporation) Present+ Khanderao Kand, (Oracle Corporation) Present+ Anish Karmarkar, (Oracle Corporation) Present+ Ashok Malhotra, (Oracle Corporation) Present+ Najeeb Andrabi, (TIBCO Software Inc.)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]