[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Raw Chat Transcript from June 9 Telcon
Mike Edwards: 1. Opening Introductions Scribe assignment Top of the scribe list: Plamen Pavlov SAP AG Tom Rutt Fujitsu Limited Ashok Malhotra Oracle Corporation Eric Johnson TIBCO Software Inc. Anish Karmarkar Oracle Corporation Martin Chapman Oracle Corporation Bryan Aupperle IBM Agenda bashing 2. Approval of the minutes from 2 June: http://www.oasis-open.org/committees/download.php/42445/SCA%20Bindings%20minutes%202011-06-02.doc 3. Actions 20110519-01 [Simon Holdsworth] Look into whether we need a testcase for the updated normative statement in BJM60009 [following resolution of BINDINGS-157]. 4. New Issues BINDINGS-162 WS binding support for use of EPRs to specify endpoint should be mandatory http://www.osoa.org/jira/browse/BINDINGS-162 BINDINGS-163 WS binding support for ?wsdl should be non-normative http://www.osoa.org/jira/browse/BINDINGS-163 BINDINGS-164 WS binding RPC literal support should require specific namespace http://www.osoa.org/jira/browse/BINDINGS-164 BINDINGS-165 BWS50014 & BWS50015 are optional normative statements http://www.osoa.org/jira/browse/BINDINGS-165 BINDINGS-166 Section 6.4 contains optional normative statements http://www.osoa.org/jira/browse/BINDINGS-166 BINDINGS-167 WSCB has separate conformance points in the Web services specification http://www.osoa.org/jira/browse/BINDINGS-167 BINDINGS-168 BWS20034 & BWS20036 are optional normative statements http://www.osoa.org/jira/browse/BINDINGS-168 5. Open Issues http://www.osoa.org/jira/browse/BINDINGS-153 write new tests for TA-20021 TA-20022 TA-20028 TA-20032TA-20034 TA-20035 TA-40007 TA-50008 TA-50009 Status: Proposed outline resolution in JIRA; partial direction agreed for some statements as per meeting minutes 6. Potential new JMS binding testcase Discuss potential new JMS binding testcase as described in: http://lists.oasis-open.org/archives/sca-bindings/201105/msg00036.html 7. AOB Ashok (Oracle): 5 members on the call: Mike, Anish, Ashok, Eric, Tom anish do we need 2/3rd for new issues? Ashok (Oracle): 5 out of 9 voting members -- quorate Ashok (Oracle): Agenda accepted Ashok (Oracle): Topic: Approval of the minutes from 2 June: http://www.oasis-open.org/committees/download.php/42445/SCA%20Bindings%20minutes%202011-06-02.doc Ashok (Oracle): Minutes approved Ashok (Oracle): Topic: Actions 20110519-01 [Simon Holdsworth] Look into whether we need a testcase for the updated normative statement in BJM60009 [following resolution of BINDINGS-157]. Ashok (Oracle): Pending Ashok (Oracle): Topic: New issues Ashok (Oracle): Eric: We do not require 2/3rd to open issues anish hopefully Plamen would join and we would have 2/3rd Ashok (Oracle): ... I recommend we try to open them all Ashok (Oracle): BINDINGS-162 WS binding support for use of EPRs to specify endpoint should be mandatory http://www.osoa.org/jira/browse/BINDINGS-162 Ashok (Oracle): ... not a SHOULD as the spec currently says Ashok (Oracle): Anish moves to open 162, Ashok seconds Ashok (Oracle): Motions passes w/o objection -- Issue 162 is open Ashok (Oracle): Anish: This comes from 153 where we had a agreed upon direction Ashok (Oracle): Anish discusses proposal anish: only thing required in an EPR is an address URI anish: ... so not a big deal other than parsing Ashok (Oracle): Present+: Plamen anish: Resolve issue 162 by s/SHOULD/MUST/ in 2022, and removing 2033 whereever it occurs in the main spec Ashok (Oracle): Anish moves to resolve 162 with above proposal. Ashok seconds Ashok (Oracle): 162 resolved w/o objection Ashok (Oracle): BINDINGS-163 WS binding support for ?wsdl should be non-normative http://www.osoa.org/jira/browse/BINDINGS-163 Ashok (Oracle): Anish moves open 163, Ashok seconds Ashok (Oracle): Motions passes w/o objection -- Issue 163 is open anish: "Any service hosted by an SCA runtime with one or more web service bindings with HTTP endpoints is strongly encouraged to return a WSDL description of the service in response to an HTTP GET request with the ?wsdl suffix added to that HTTP endpoint URL. Regardless of the protocol supported by an SCA service endpoint using the web services binding, the SCA runtime is strongly encouraged to provide some means of obtaining the WSDL description of the service. " Mike Edwards: This proposal went to list in http://lists.oasis-open.org/archives/sca-bindings/201106/msg00034.html Mike Edwards: Note this would replace both BWS20029 and BWS20030 Ashok (Oracle): Anish moves to resolve 163 with above proposal. Ashok seconds Ashok (Oracle): Motion passes w/o objection -- Issue 163 is resolved Ashok (Oracle): BINDINGS-164 WS binding RPC literal support should require specific namespace http://www.osoa.org/jira/browse/BINDINGS-164 Ashok (Oracle): Anish: This was also discussed under 153 there seemed to be consensus to replace MAY with MUST Ashok (Oracle): Anish moves to open 164, Ashok seconds Ashok (Oracle): Motion passes w/o objection -- Issue 164 is open Ashok (Oracle): Anish argues for a MUST Ashok (Oracle): Anish moves to resolve 164 by replacing SHOULD in 40007 with a MUST. Eric seconds Ashok (Oracle): Motion passes w/o objection -- Issue 164 is resolved Ashok (Oracle): BINDINGS-165 BWS50014 & BWS50015 are optional normative statements http://www.osoa.org/jira/browse/BINDINGS-165 Ashok (Oracle): Ashok moves to open 165, Tom Rutt seconds Ashok (Oracle): Motion passes w/o objection -- Issue 165 is open Ashok (Oracle): Mike: My proposal is to make these statements non-normative. Cannot have a MUST here. Mike Edwards: It is good practice for Policies and assertions to be signed to prevent tampering. The authors advise that an SCA runtime rejects Policies unless they are signed and have an associated security token to specify the signer has proper claims for the given policy Mike Edwards: It is good practice for Policies and assertions to be signed to prevent tampering. It is advised that an SCA runtime rejects Policies unless they are signed and have an associated security token to specify the signer has proper claims for the given policy. Mike Edwards: Ashok moves to resolve issue 165 by replacing BWS50014 & BWS50015 with: "It is good practice for Policies and assertions to be signed to prevent tampering. It is advised that an SCA runtime rejects Policies unless they are signed and have an associated security token to specify the signer has proper claims for the given policy." Ashok (Oracle): Ashok moves to resolve 165 with the above wording. Tom Rutt secon Ashok (Oracle): Motion passes w/o objection -- Issue 165 is resolved Ashok (Oracle): BINDINGS-166 Section 6.4 contains optional normative statements http://www.osoa.org/jira/browse/BINDINGS-166 Ashok (Oracle): Anish moves to open 166, Ashok seconds Ashok (Oracle): Motion passes w/o objection -- Issue 166 is open Ashok (Oracle): BINDINGS-167 WSCB has separate conformance points in the Web services specification http://www.osoa.org/jira/browse/BINDINGS-167 Ashok (Oracle): Anish moves to open 167, Tom Rutt seconds Ashok (Oracle): Motion passes w/o objection -- Issue 167 is open Ashok (Oracle): BINDINGS-168 BWS20034 & BWS20036 are optional normative statements http://www.osoa.org/jira/browse/BINDINGS-168 Ashok (Oracle): Anish moves to open 168, Eric seconds Ashok (Oracle): Motion passes w/o objection -- Issue 168 is open Ashok (Oracle): Mike: Please make proposals for the open issues Ashok (Oracle): AOB? Ashok (Oracle): ADJOURNED --
All the best, Ashok |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]