[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Raw chat log of 2009-11-05 telcon
Simon Holdsworth: Agenda: Simon Holdsworth: 1. Opening Introductions Roll call Scribe assignment Top of the scribe list: Plamen Pavlov SAP AG Piotr Przybylski IBM Tom Rutt Fujitsu Limited Ashok Malhotra Oracle Corporation Martin Chapman Oracle Corporation Khanderao Kand Oracle Corporation Bryan Aupperle IBM Anish Karmarkar Oracle Corporation Eric Johnson TIBCO Software Inc. David Booz IBM Agenda bashing 2. Approval of the minutes from 15th October http://www.oasis-open.org/committees/download.php/34729/SCA%20Bindings%20minutes%202009-10-15.doc 3. Actions 20090211-4 [General] Write up HTTP binding use cases 20090709-2 [Editors] Update the schema appendix title to include 1.1 20090820-2 [Simon Holdsworth] Look at the templating mechanism with respect to policy. 20091001-2 [Bryan Aupperle] Get Piotr to respond to comments on proposals for issue BINDINGS-88 and BINDINGS-89 20091015-1 [Anish Karmarkar] Raise new issues found during TA creation for obvious bugs in WS binding spec 20091015-2 [Simon Holdsworth] Scan minutes for disposition of each point and generate a response to the comment and AIs as necessary 20091015-3 [Editors] Re: BINDINGS-99 point #1 - review and determine appropriate update to copyright dates (all specs) 20091015-4 [Editors] Re: BINDINGS-99 point #2 - clarify the text describing the JCA binding (JCA only) 20091015-5 [Editors] Re: BINDINGS-99 point #3 - revise text to reword or remove as appropriate (JCA only) 20091015-6 [Editors] Re: BINDINGS-99 point #5 - caption all examples, figures, snippets, etc., scrub text of use of former, latter, above, below, following. Replace with precise references (all specs) 20091015-7 [Editors] Re: BINDINGS-99 point #6 - clean up the text with regards to this item (JCA only) 20091015-8 [Editors] Re: BINDINGS-99 point #8 - look at whether the non-normative references section is relevant still, or needs to be populated (all specs) 20091015-9 [Editors] Re: BINDINGS-99 point #9 - clean up naming conventions section (all specs) 20091015-10 [Editors] Re: BINDINGS-99 point #10 - look for cleanup to clarify optionality (all specs) 20091015-11 [Editors] Re: BINDINGS-99 point #11 - do something to clarify the different uses for the @uri attribute (JCA only) 20091015-12 [Editors] Re: BINDINGS-99 point #16 - mark Annexes as normative or not as appropriate (all specs) 4. Holiday Meetings Discuss meetings of Nov 26, Dec 24, Dec 31 5. New Issues No new issues in JIRA; on mailing list: What is the purpose of definitions/binding element? http://lists.oasis-open.org/archives/sca-bindings/200911/msg00000.html No defined behaviour in JMS binding if resolved operation name not present in interface http://lists.oasis-open.org/archives/sca-bindings/200911/msg00003.html Incorrect closing element in JMS pseudo-schema http://lists.oasis-open.org/archives/sca-bindings/200911/msg00009.html 6. Test Assertions/Test cases Current status: Web Service binding TA document: http://www.oasis-open.org/committees/download.php/34571/sca-wsbinding-1.1-test-assertions-wd02.odt http://www.oasis-open.org/committees/download.php/34572/sca-wsbinding-1.1-test-assertions-wd02.pdf Status: Draft completed; needs review JMS TA document: http://www.oasis-open.org/committees/download.php/34706/sca-jmsbinding-1.1-test-assertions-wd03.doc http://www.oasis-open.org/committees/download.php/34707/sca-jmsbinding-1.1-test-assertions-wd03.pdf Status: Latest draft needs review. JCA TA document: http://www.oasis-open.org/committees/download.php/34114/sca-jcabinding-1.1-test-assertions-wd03.doc http://www.oasis-open.org/committees/download.php/34115/sca-jcabinding-1.1-test-assertions-wd03.pdf Comment: http://lists.oasis-open.org/archives/sca-bindings/200909/msg00011.html Status: reviewed and issues raised. 7. Open issue discussion Public review comment issues: http://www.osoa.org/jira/browse/BINDINGS-99 Patrick Durusau - 2009-10-07 - Comments on sca-jcabinding-1.1-spec.pdf Raiser: Public review comment, owner: unassigned Priority: 1 (PR comment needing disposition) Status: Proposed resolution: http://lists.oasis-open.org/archives/sca-bindings/200910/msg00054.html http://www.osoa.org/jira/browse/BINDINGS-100 Simon Holdsworth - 2009-10-07 - Comments on bindings specs Raiser: Simon Holdsworth, owner: Simon Holdsworth Priority: 1 (PR comment needing disposition) Status: Proposed resolution: http://lists.oasis-open.org/archives/sca-bindings/200910/msg00053.html http://www.osoa.org/jira/browse/BINDINGS-87 Web Service callback standard is best done by the appropriate Web Services working groups Raiser: PR comment, owner: Unassigned Priority: 1 (PR comment needing disposition) Status: latest email: http://lists.oasis-open.org/archives/sca-bindings/200911/msg00001.html http://www.osoa.org/jira/browse/BINDINGS-97 confusing statement on correlation ID in the context of callbacks with JMS binding Raiser: Public review comment, owner: Simon Holdsworth Priority: 1 (PR comment needing disposition) Status: Proposed resolution: http://lists.oasis-open.org/archives/sca-bindings/200911/msg00004.html Other open issues: http://www.osoa.org/jira/browse/BINDINGS-88 JCA Missing Normative statements re: connection/@name andactivationSpec/@name Raiser: Bryan Aupperle, owner: Unassigned Priority: Unassigned Status: proposed resolution in issue Latest email: http://lists.oasis-open.org/archives/sca-bindings/200910/msg00002.html http://www.osoa.org/jira/browse/BINDINGS-89 BJC20008 and BJC20014 are unclear Raiser: Bryan Aupperle, owner: Unassigned Priority: Unassigned Status: proposed resolution in issue Latest email: http://lists.oasis-open.org/archives/sca-bindings/200910/msg00003.html http://www.osoa.org/jira/browse/BINDINGS-93 BJM60006 too vague and conflicts with other statements Raiser: Simon Holdsworth, owner: Simon Holdsworth Priority: Unassigned Status: Proposed resolution in JIRA Latest email: http://lists.oasis-open.org/archives/sca-bindings/200910/msg00000.html http://www.osoa.org/jira/browse/BINDINGS-94 scaCallbackDestination destination name unclear Raiser: Simon Holdsworth, owner: Simon Holdsworth Priority: Unassigned Status: Proposed resolution in email: http://lists.oasis-open.org/archives/sca-bindings/200911/msg00008.html http://www.osoa.org/jira/browse/BINDINGS-95 BJM30032 and BJM30035 conflict Raiser: Simon Holdsworth, owner: Simon Holdsworth Priority: Unassigned Status: Proposed resolution in JIRA Latest email: http://lists.oasis-open.org/archives/sca-bindings/200911/msg00010.html http://www.osoa.org/jira/browse/BINDINGS-96 BJM60012 and BJM60013 conflict Raiser: Simon Holdsworth, owner: Simon Holdsworth Priority: Unassigned Status: Proposed resolution in JIRA http://www.osoa.org/jira/browse/BINDINGS-103 optional used in normative statement Raiser: Simon Holdsworth, owner: Simon Holdsworth Priority: Unassigned Status: Proposed resolution in JIRA http://www.osoa.org/jira/browse/BINDINGS-104 Expected @create attribute value not clear in some normative statements Raiser: Simon Holdsworth, owner: Simon Holdsworth Priority: Unassigned Status: Proposed resolution in JIRA http://www.osoa.org/jira/browse/BINDINGS-105 BJM30025 has no normative keyword Raiser: Simon Holdsworth, owner: Simon Holdsworth Priority: Unassigned Status: Proposed resolution in JIRA Latest email: http://lists.oasis-open.org/archives/sca-bindings/200911/msg00010.html http://www.osoa.org/jira/browse/BINDINGS-106 BJM30027 has no normative keyword Raiser: Simon Holdsworth, owner: Simon Holdsworth Priority: Unassigned Status: Proposed resolution in JIRA Latest email: http://lists.oasis-open.org/archives/sca-bindings/200911/msg00010.html http://www.osoa.org/jira/browse/BINDINGS-101 Opaque references - need for a terminology list? Raiser: PR comment, owner: Unassigned Priority: Unassigned Status: no proposed resolution http://www.osoa.org/jira/browse/BINDINGS-102 Need to specify all valid enumerations for @create attribute and others Raiser: PR comment, owner: Unassigned Priority: Unassigned Status: no proposed resolution http://www.osoa.org/jira/browse/BINDINGS-60 JMS Default wire format insufficient to cover real world usage Raiser: Mike Edwards, owner: Simon Holdsworth Priority: 3 (deferred) Status: outline proposal in issue 8. AOB anish: Scribe: Anish Karmarkar anish: Topic: Action anish: 20091015-2 is done anish: All others are still pending anish: Topic: Holiday meetings anish: Meetings on TG, Christmas and NY anish: (Nov 26, Dec 24, Dec 31) anish: The three calls on Nov 26, Dec 24, Dec 31 are canceled anish: Action: chair to cancel the three calls in KAVI anish: Plamen joins and the meeting is now quorate anish: Topic: Approval of the minutes from 15th October anish: http://www.oasis-open.org/committees/download.php/34729/SCA%20Bindings%20minutes%202009-10-15.doc anish: No objections to approving the minutes as posted anish: Resolution: minutes of 15th oct accepted anish: Topic: new issue 107 anish: What is the purpose of definitions/binding element? http://lists.oasis-open.org/archives/sca-bindings/200911/msg00000.html Eric Johnson: http://www.osoa.org/jira/browse/BINDINGS-107 anish: Motion: anish moves dave seconds to open issue 107 anish: motion passes w/o anish: ACTION: anish to open an issue against JMS which is similar to 107 anish: Topic: new issue 108 anish: No defined behaviour in JMS binding if resolved operation name not present in interface http://lists.oasis-open.org/archives/sca-bindings/200911/msg00003.html anish: http://www.osoa.org/jira/browse/BINDINGS-108 anish: SimonH explains the issue anish: motion: m:eric s:mikeE to open issue 108 anish: motion approved w/o anish: proposal fro 108 -- anish: Modify BJM40010 as follows: When a message is received at an SCA service with JMS binding, the SCA runtime MUST invoke the target component using the resolved operation name if that name is present in the target component's interface, otherwise the SCA runtime MUST raise an error [BJM40010]. anish: s/fro /for / Simon Holdsworth: When a message is received at an SCA service with JMS binding, the SCA runtime MUST invoke the target component using the resolved operation name Dave Booz: current words: When a message is received at an SCA service with JMS binding, the SCA runtime MUST invoke the target component using the resolved operation name [BJM40010]. anish: Dave: in the past we have broken up statements with two MUST anish: ... as it creates issues with TAs Simon Holdsworth: Alternatively add the following statmenet: "When a message is received at an SCA service with JMS binding, if the resolved operation name is not in the target component's interface the SCA runtime MUST raise an error [BJM400XX]." anish: simon: if we go with this, would we want to change the other stmt as well so that they match anish: Dave: yes Simon Holdsworth: Update to existing: When a message is received at an SCA service with JMS binding and the resolved operation name is in the target components interface, the SCA runtime MUST invoke the target component using the resolved operation name [BJM40010]. anish: motion: m: dave s:mikeE resolve 108 with the following: anish: Update to existing: When a message is received at an SCA service with JMS binding and the resolved operation name is in the target components interface, the SCA runtime MUST invoke the target component using the resolved operation name [BJM40010]. anish: and add a new: anish: "When a message is received at an SCA service with JMS binding, if the resolved operation name is not in the target component's interface the SCA runtime MUST raise an error [BJM400XX]." anish: motion approved w/o anish: Topic: new issue 109 anish: ncorrect closing element in JMS pseudo-schema http://lists.oasis-open.org/archives/sca-bindings/200911/msg00009.html anish: http://www.osoa.org/jira/browse/BINDINGS-109 anish: Simon: typo in closing tag anish: motion: m:eric s:mikeE to open issue 109 anish: motion approved w/o anish: motion: m:eric s:mikeE to resolve 109 with proposal in JIRA anish: motion approved w/o anish: Topic: issue 99 anish: http://www.osoa.org/jira/browse/BINDINGS-99 Patrick Durusau - 2009-10-07 - Comments on sca-jcabinding-1.1-spec.pdf Raiser: Public review comment, owner: unassigned Priority: 1 (PR comment needing disposition) Status: Proposed resolution: http://lists.oasis-open.org/archives/sca-bindings/200910/msg00054.html anish: Simon walks through his proposed resolution anish: anish: i think the ibm lawyers already checked this and it is ok anish: mike: yes we did anish: ... assembly spec does the same anish: ... it can predate existence of the TC anish: (the above refers to the copyright issue) anish: Eric: it would be beneficial if we summarized (like 3 no actions, 3 new issues etc) anish: ... we should also provide links to the issues that are raised anish: ... identifying the editorial AIs by our internal tracking numbers anish: s/identifying/and identify/ anish: motion: m:mikeE s:dave close issue 99 with no change to the spec, with an action to send a response in http://lists.oasis-open.org/archives/sca-bindings/200910/msg00054.html (modulo changes to item 1 related to copyright, and 3 comments from Eric) anish: motion approved w/o anish: Action: simon to send a response to the raiser of issue 99 as outlined in http://lists.oasis-open.org/archives/sca-bindings/200910/msg00054.html (modulo changes per the issue closing motion) anish: Topic: issue 100 anish: http://www.osoa.org/jira/browse/BINDINGS-100 Simon Holdsworth - 2009-10-07 - Comments on bindings specs Raiser: Simon Holdsworth, owner: Simon Holdsworth Priority: 1 (PR comment needing disposition) Status: Proposed resolution: http://lists.oasis-open.org/archives/sca-bindings/200910/msg00053.html anish: simon walks through his proposed resolution anish: anish: for the ws-spec how about: The relevant web service specifications have a way to figure out the operation. For example WS-Addressing wsa:Action SOAP header block anish: motion: m:anish s:mikeE resolve issue 100 with no change to the spec and an action to simon to send a response per http://lists.oasis-open.org/archives/sca-bindings/200910/msg00053.html (after cleaning it up) anish: motion approved w/o anish: meeting adjourned
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]