[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Raw chat log of 2008-07-10 telcon
anish: Agenda: http://lists.oasis-open.org/archives/sca-bpel/200807/msg00004.html 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 June 19, 2008 minutes http://lists.oasis-open.org/archives/sca-bpel/200806/msg00003.html 5. Approval of June 26, 2008 minutes http://lists.oasis-open.org/archives/sca-bpel/200806/msg00008.html 6. 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 #0042 Editors to incorporate all issue resolutions by 10 july 2008 7. SCA J TC's request to swap call times with us http://lists.oasis-open.org/archives/sca-bpel/200807/msg00000.html 8. New Issues a. Issues with BPEL extension schema: is reference NCName or QName and two conflicting definitions of reference. Is this a new issue or a typo? http://lists.oasis-open.org/archives/sca-bpel-editors/200807/msg00001.html 9. Status of spec Update from the editors 10. Issue 17 http://www.osoa.org/jira/browse/BPEL-17 TITLE - Allow Component Type side file to override defaults for service/reference This issue was waiting on Assembly-52, which was recently closed with no action. There is a proposal to resolve this issue in JIRA. 11. Issue 18 http://www.osoa.org/jira/browse/BPEL-18 TITLE- Need to rewrite the SCA-BPEL specifications with RFC-2119 keywords/statements See proposal (rev 5) from MikeR at http://lists.oasis-open.org/archives/sca-bpel/200806/msg00002.html 12. AOB anish: Scribe: Khanderao Kand anish: ScribeNick: khanderao khanderao: Updates on Action Items: anish: Topic: approval of june 19, 2008 minutes anish: ttp://lists.oasis-open.org/archives/sca-bpel/200806/msg00003.html anish: http://lists.oasis-open.org/archives/sca-bpel/200806/msg00003.html khanderao: Approval of Jun 19th Minutes: http://lists.oasis-open.org/archives/sca-bpel/200806/msg00003.html. Approved anish: june 26: http://lists.oasis-open.org/archives/sca-bpel/200806/msg00008.html khanderao: Approval of Jun 26th Minutes: http://lists.oasis-open.org/archives/sca-bpel/200806/msg00008.html. Approved khanderao: Updates on AIs: a) AI #0021 Chairs - to follow up with Mary to post the CD docs to OASIS repository. Mike Edwards: she has had the Assembly CD-01 for nearly 5 months khanderao: Mary's task list is full. No ETA from Mary. AI pending. khanderao: Updated on AI b) AI #0042 Editors to incorporate all issue resolutions by 10 july 2008: Pending khanderao: Agenda Items: khanderao: Agenda item: 7. SCA J TC's request to swap call times with us http://lists.oasis-open.org/archives/sca-bpel/200807/msg00000.html khanderao: Dieter won't be able regularly with the proposed time. khanderao: No supporter to change the time. khanderao: Action Item: To Anish/chair to get back SCA-J TC to inform our inability to swap the times anish can you hear me Dave Booz: no khanderao: NO anish going to swap phones. i'm giving up on this one anish give me a minute khanderao: Discussions on new issues: khanderao: a. Issues with BPEL extension schema: is reference NCName or QName and two conflicting definitions of reference. Is this a new issue or a typo? http://lists.oasis-open.org/archives/sca-bpel-editors/200807/msg00001.html khanderao: Dieter: It is a typo. Easily fixable and can be treated as an Action Item as against a new issue. anish: Action: Dieter to fix all the typos/errors in SCA BPEL XML schema khanderao: Other aspect is inconsistency of name space prefix . Dieter ready to volunteer to fix. khanderao: Agenda item 9. Status of spec: Update from the editors khanderao: Najib informed that he is done with his changes. khanderao: Dieter got the pen now. khanderao: Martin moved a motion to cancel the next call on Jul 17th 2008. Second: Danny khanderao: No discussion. No Objections. Motion passed unanimously khanderao: Action: Editors to updates specs(Agenda 9) by Jul 23rd 2008 call. khanderao: Discussions on LOAs in August. khanderao: Action: To all: Email your availabilities in the month of Aug. to Anish anish: Topic: issue 17 anish: http://www.osoa.org/jira/browse/BPEL-17 khanderao: Discussion on Agenda item 10. Issue 17 http://www.osoa.org/jira/browse/BPEL-17 TITLE - Allow Component Type side file to override defaults for service/reference This issue was waiting on Assembly-52, which was recently closed with no action. There is a proposal to resolve this issue in JIRA. Mike Edwards: helpful people, these Assembly folks khanderao: Assembly-52 was closed by the SCA Assembly TC with no action Mike Edwards: why wasn't the name constructed using the Scope name? Mike Edwards: ah - scratch that comment of mine khanderao: MikeR updates: On the SCA-BPEL TC call of 2008-02-28 we resolved that the following text will be used as the resolution of this issue, if the SCA Assembly specification adopts the @implementationRef attribute that has been proposed: The @implementationRef attribute MUST contain a valid XPath 1.0 expression, which when executed on a BPEL process returns exactly one <partnerLink> element. The partnerLink thus identified will be considered to correspond to the service or reference that contained the @implementationRef attribute. If a service or reference does not have an @implementationRef attribute, then it will act as if it had @implementationRef=//partnerLink[@name=$name], where $name is the value of the @name attribute of that service or reference. khanderao: MikeR: Open question : whether to use new prefix for this new implementationRef attribute? khanderao: Anish: This attribute meant to be sca-bpel extension or bpel extension. khanderao: MikeR: This is in componentType file and no extensions over there. khanderao: Dieter: Confirmed. khanderao: Anish: For scdl and component type file there is one name space. For BPEL, it is bpel extensions. khanderao: The idea of creating a separate schema for one attribute is not appropriate. khanderao: Najib: we can create a new schema file and import the existing namespace. khanderao: Anish: There is no one good way now. We should have a separate namespace for implementation.bpel khanderao: However, we do not need another discussion on single namespace for implementation.bpel khanderao: MikeR and Anish preferred to put in sca-bpel namespace. khanderao: Dieter: We should not be creating complicated dependencies. khanderao: Motion:by MikeR: anish: existing proposal: anish: The @implementationRef attribute MUST contain a valid XPath 1.0 expression, which when executed on a BPEL process returns exactly one <partnerLink> element. The partnerLink thus identified will be considered to correspond to the service or reference that contained the @implementationRef attribute. If a service or reference does not have an @implementationRef attribute, then it will act as if it had @implementationRef=//partnerLink[@name=$name], where $name is the value of the @name attribute of that service or reference. Michael Rowley: Proposed issue resolution: An @sca-bpel:implementationRef attribute on a component type's service or reference MUST contain a valid XPath 1.0 expression, which when executed on a BPEL process returns exactly one <partnerLink> element. The partnerLink thus identified will be considered to correspond to the service or reference that contained the @sca-bpel:implementationRef attribute. If a service or reference does not have an @sca-bpel:implementationRef attribute, then it will act as if it had @sca-bpel:implementationRef=//partnerLink[@name=$name], where $name is the value of the @name attribute of that service or reference. khanderao: Seconded by Danny khanderao: Motion passed unanimously khanderao: Meeting adjourned.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]