[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Minutes for today's call.
[11:57] Simon Holdsworth: Audio conference: Meeting Number: * 913929 * (press * before and after the digits) Phone numbers: Austria = Vienna 026822056419 Belgium = Brussels 022901709 China Toll Free = China North 108007121722, China South 108001201722 Denmark = Copenhagen 32714982 France = Paris 0170994364, Lyon 0426840196, Marseilles 0488915310 Germany = Berlin 030726167296, Frankfurt 069710445413, Hamburg 040809020620, Munich 089244432767, Stuttgart 0711490813212, Dusseldorf 021154073845 India Toll Free = 0008001006703 Ireland = Dublin 014367612 Italy = Milan 0230413007, Rome 06452108288, Turin 01121792100 Japan = Tokyo 0357675037 Netherlands = Amsterdam 0207965349 Portugal = Lisbon 211200415 Russia Toll Free = 81080022074011 Spain = Barcelona: 934923140, Madrid: 917889793 Sweden = Stockholm 0850520404 Switzerland = Geneva 0225927186 UK Toll Free = 08003581667 UK Toll = London 02071542988, Manchester 01612500379, Birmingham 01212604587 USA Toll Free = 18665289390 USA Toll = 19543344789
[11:58] Simon Holdsworth: Agenda
[11:58] Simon Holdsworth: . Opening Introductions Roll call Scribe assignment Top of the scribe list: Plamen Pavlov SAP AG Bryan Aupperle IBM Eric Johnson TIBCO Software Inc. Simon Nash Individual Anish Karmarkar Oracle Corporation Tom Rutt Fujitsu Limited Martin Chapman Oracle Corporation Ashok Malhotra Oracle Corporation David Booz IBM Agenda bashing 2a. Approval of the minutes from 20th May http://www.oasis-open.org/committees/download.php/32613/SCA%20Bindings%20minutes%202009-05-20.doc 2b. Approval of the minutes from 21st May http://www.oasis-open.org/committees/download.php/32633/SCA%20Bindings%20minutes%202009-05-21.doc 3. Actions 20090211-4 [General] Write up HTTP binding use cases 20090311-2 [Editors] Update specs for new assembly namespace 20090312-1 [Editors] Update schemas in specs as per http://lists.oasis-open.org/archives/sca-bindings/200903/msg00057.html 4. New Issues Please note, as per resolution on 9th October 2008, new issues received on the mailing list after Noon GMT 1st November can only be opened using the same voting rules as re-opening a closed issue (2/3 majority of a full TC vote) no new issues 5. Open Issue and PRD Schedule Down to one must-have issue, when can editors have a PRD ready? Is the best approach to produce CD03, accept that then vote to have that as PRD01? Current schedule: Must have issues resolved by April 16th Public review draft available for TC comments April 23rd Public review draft vote April 30th Test assertions complete one month beyond PRD, test cases one month after that. Issues with proposed resolutions: 3 Issues with identified owner, no resolution: 0 Issues with no identified owner: 0 Survey outlook for issues with no proposed resolution (marked with * in this list) David Booz: 73 (pri 1) Anish Karmarkar: 2 (pri 2) Simon Holdsworth: 48 (pri 3) 6. Open Issue Discussion http://www.osoa.org/jira/browse/BINDINGS-73 Default qualifier of 1_1 for SOAP intent contradicts WS Binding spec Raiser: Simon Nash, owner: David Booz Priority: 1 Status: Proposed resolution in JIRA Latest email: http://lists.oasis-open.org/archives/sca-bindings/200905/msg00093.html http://www.osoa.org/jira/browse/BINDINGS-2 How should SCA callback semantics be carried over Web Services? Raiser: Simon Nash, owner: Anish Karmarkar Priority: 2 Status: Latest proposal: http://lists.oasis-open.org/archives/sca-bindings/200905/msg00098.html http://www.osoa.org/jira/browse/BINDINGS-48 How are mayProvide intents on bindings satisfied Raiser: Ashok Malhotra, owner: Simon Holdsworth Priority: 3 Status: Proposed resolution: http://lists.oasis-open.org/archives/sca-bindings/200903/msg00005.html Latest email: http://lists.oasis-open.org/archives/sca-bindings/200903/msg00059.html 7. AOB ------------------------------------------------------------------- *Revolving list of scribes* Plamen Pavlov SAP AG Bryan Aupperle IBM Eric Johnson TIBCO Software Inc. Simon Nash Individual Anish Karmarkar Oracle Corporation Tom Rutt Fujitsu Limited Martin Chapman Oracle Corporation Ashok Malhotra Oracle Corporation David Booz IBM
[12:07] Bryan Aupperle: Scribe: Bryan Aupperle
[12:10] Bryan Aupperle: Topic: Approval of minutes of 20 May
[12:11] Bryan Aupperle: Minutes approved
[12:11] Bryan Aupperle: Topic: Approval of minutes of 21 May
[12:11] Bryan Aupperle: Minutes approved
[12:11] Bryan Aupperle: Topic: Action Items
[12:12] Bryan Aupperle: 20090311-2 Done for JCA and JMS, pending for WS 20090312-1 Done for JCA and JMS, pending for WS
[12:12] Bryan Aupperle: Topic New Issues.
[12:14] Bryan Aupperle: Issue raised on e-mail but not in JIRA yet - Update conformance section of JMS and JCA specs. Will discuss next call.
[12:14] Bryan Aupperle: Topic: PRD status
[12:15] Bryan Aupperle: All current issues have been applied to JMA and JCA specs. Please review in preparation for a CD/PRD vote.
[12:16] Bryan Aupperle: A number of issue resolutions need to be applied to the WS spec. but there are still two issues to resolve.
[12:17] Bryan Aupperle: Simon N: Can we work in parallel - prepare a draft with resolved issues while the remaining are being resolved?
[12:17] Bryan Aupperle: Anish: Yes, that is possible
[12:18] Bryan Aupperle: Topic: Issue Bindings 73
[12:18] Bryan Aupperle: http://www.osoa.org/jira/browse/BINDINGS-73
[12:18] Bryan Aupperle: Latest email: http://lists.oasis-open.org/archives/sca-bindings/200905/msg00093.html
[12:20] Bryan Aupperle: Dave reviews problems with original proposal
[12:20] Bryan Aupperle: Dave: Believes default is correct and CNA is appropriate
[12:22] Bryan Aupperle: Anish: Not clear we need to state default in spec as opposed to letting a runtime make a choice
[12:22] Bryan Aupperle: Dave: This can lead to interop problems.
[12:23] Bryan Aupperle: Simon N: Why is original proposal in conflict with Policy spec.?
[12:24] anish: simonN, what is the difference between any and no default?
[12:24] anish: that is if the policy spec allowed no default
[12:25] Bryan Aupperle: Dave clarifies the problem matching a reference with any and a service with 1_1.
[12:26] Bryan Aupperle: Simon N: We could write rules in WS spec to resolve the matching problem.
[12:28] Bryan Aupperle: Simon N: Cant multiple qualifies be provided?
[12:29] Bryan Aupperle: Dave: Not at the moment, they are currently mutually exclusive.
[12:29] Bryan Aupperle: Mike: The policy spec normative text in this area is very thin.
[12:30] Bryan Aupperle: Dave: Normative text is in algorithm part of policy spec. But we should be clearer.
[12:32] Bryan Aupperle: Mike: Should be possible for SOAP (unqualified) to match with SOAP.1_1 or SOAP.1_2 and specs should allow this.
[12:33] Bryan Aupperle: Mike: Policy seems to be broken wrt this.
[12:35] Mike Edwards: If we fix Policy, then we can close this issue with no action
[12:36] Bryan Aupperle: Anish: So default only applies to intent maps
[12:38] Bryan Aupperle: Ashok: There is clearly a use case that the policy spec does not address. But we should not fix Policy during PR. We should CNA this issue and open a Policy PR comment to address (since the solution in Policy is not clear at the moment.
[12:39] Bryan Aupperle: Motion: Mike, second Dave: close Bindings 73 - no action
[12:40] Bryan Aupperle: Action Item (Mike) Raise a PR issues against Policy to address this use case
[12:40] Bryan Aupperle: Motion passes w/o
[12:41] Bryan Aupperle: AI detail - Issues is against point 7 of the intent algorithm.
[12:41] Bryan Aupperle: Topic: Bindings 2
[12:41] Dave Booz: line 1451 of Policy CD02
[12:41] Bryan Aupperle: http://www.osoa.org/jira/browse/BINDINGS-2
[12:41] Bryan Aupperle: Latest proposal: http://lists.oasis-open.org/archives/sca-bindings/200905/msg00098.html
[12:43] Bryan Aupperle: Mike reviews latest changes
[12:48] Bryan Aupperle: Simon N: Should have an intro paragraph at start of 5.2.
[12:50] anish: Add in section 5.2:
[12:50] anish: For 357 examples of wire messages exchanged when using this protocol see the appendix SCA 358 Web Services Callback Protocol Message Examples.
[12:53] Bryan Aupperle: Discussion about the normative statements in assertion section
[12:54] Bryan Aupperle: Conclusion is that current text is not clear about assertions and the imposed requirements.
[12:59] Bryan Aupperle: Anish: This protocol should be composable with other protocols without the need for conformance points here.
[13:02] Bryan Aupperle: Lines 509, 512, 449 and 460 have must/MUST not covered (search on all keywords)
[13:03] Bryan Aupperle: Action Item (Anish): Produce updated draft to clean up protocol composition and make sure all keywords are part of conformance statements.
[13:03] Bryan Aupperle: COB
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]