OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

sca-bindings message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Raw notes from 11 March 09 call


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
Simon Holdsworth: Agenda:
Simon Holdsworth: 1. Opening 
 
Introductions 
Roll call 
Scribe assignment 
 
Top 10 on the scribe list: 
Nimish Hathalia TIBCO Software Inc. 
Plamen Pavlov SAP AG 
Martin Chapman Oracle Corporation 
Anish Karmarkar Oracle Corporation 
Tom Rutt Fujitsu Limited 
Piotr Przybylski IBM 
Eric Johnson TIBCO Software Inc. 
Simon Nash Individual 
David Booz IBM 
Ashok Malhotra Oracle Corporation 
 
Agenda bashing 
 
2. Approval of the minutes from 5th March 
 
http://www.oasis-open.org/committees/download.php/31622/SCA%20Bindings%20minutes%202009-03-05.doc 
 
3. Actions 
 
20090211-4 [General] Write up HTTP binding use cases 
20090226-1 [Simon Nash] Propose resolution for BINDINGS-23 
20090226-2 [Anish Karmarkar] Propose resolution for BINDINGS-25; depends on BINDINGS-54 
20090226-4 [Eric Johnson] Propose resolution for BINDINGS-43 
20090226-7 [Simon Holdsworth] Propose resolution for BINDINGS-60 
20090305-1 [Eric Johnson] Update proposal for BINDINGS-54 
 
4. SCA namespace change 
 
Latest email: http://lists.oasis-open.org/archives/sca-bindings/200903/msg00031.html 
 
5. 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) 
 
2 new issues on mailing list, not currently in JIRA, regarding JMS binding schema. 
 
6. Open Issue Summary/Schedule 
 
Discuss ownership/deferral of issues. 
 
Current schedule: 
Public review drafts to be completed by 5th March, with TC vote on 12th March 
Test assertions complete by end of March, test cases by end of April 
 
Issues with proposed resolutions: 4 
Issues with identified owner, no resolution: 4 
Issues with no identified owner: 0 
 
Survey outlook for issues with no proposed resolution (marked with * in this list) 
 
Simon Holdsworth: 39, 48, 60* 
Eric Johnson: 43*, 54 
Anish Karmarkar: 2, 25* 
Simon Nash: 23* 
 
7. Open Issue Discussion 
 
http://www.osoa.org/jira/browse/BINDINGS-54 
Endpoint URI algorithm is unclear 
Raiser: Eric Johnson, owner: Eric Johnson 
Status: Proposed resolution: http://lists.oasis-open.org/archives/sca-bindings/200902/msg00129.html 
Latest email: http://lists.oasis-open.org/archives/sca-bindings/200903/msg00016.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 
Status: Proposed resolution: http://lists.oasis-open.org/archives/sca-bindings/200902/msg00126.html 
Latest email: http://lists.oasis-open.org/archives/sca-bindings/200903/msg00015.html 
 
http://www.osoa.org/jira/browse/BINDINGS-25 
Is it required that every implementation of binding.ws support the soap intent? 
Raiser: Anish Karmarkar, owner: Anish Karmarkar 
Status: No current proposal. 
Latest email: http://lists.oasis-open.org/archives/sca-bindings/200903/msg00013.html 
 
http://www.osoa.org/jira/browse/BINDINGS-23 
@wsdlElement definition needs clarification on "equivalent" and use of WSDL 2.0 constructs 
Raiser: Eric Johnson, owner: Simon Nash 
Status: Specific resolution text required 
 
http://www.osoa.org/jira/browse/BINDINGS-39 
JMS callback specification does not cater for callbacks using other bindings 
Raiser: Simon Holdsworth, owner Simon Holdsworth 
Status: Proposed resolution: http://lists.oasis-open.org/archives/sca-bindings/200903/msg00004.html 
Latest email: http://lists.oasis-open.org/archives/sca-bindings/200903/msg00039.html 
 
http://www.osoa.org/jira/browse/BINDINGS-48 
How are mayProvide intents on bindings satisfied 
Raiser: Ashok Malhotra, owner: Simon Holdsworth 
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/msg00038.html 
 
http://www.osoa.org/jira/browse/BINDINGS-43 
Update binding.ws spec for wireFormat/operationSelection elements 
Raiser: Simon Holdsworth, owner: Anish Karmarkar 
Status: Specific resolution text required. 
 
http://www.osoa.org/jira/browse/BINDINGS-60 
JMS Default wire format insufficient to cover real world usage 
Raiser: Simon Holdsworth, owner: Simon Holdsworth 
Status: No proposal 
 
8. AOB 
 
------------------------------------------------------------------- 
 
*Revolving list of scribes* 
 
Nimish Hathalia TIBCO Software Inc. 
Plamen Pavlov SAP AG 
Martin Chapman Oracle Corporation 
Anish Karmarkar Oracle Corporation 
Tom Rutt Fujitsu Limited 
Piotr Przybylski IBM 
Eric Johnson TIBCO Software Inc. 
Simon Nash Individual 
David Booz IBM 
Ashok Malhotra Oracle Corporation 
Bryan Aupperle IBM
Simon Holdsworth: Apologies for delay in starting the call, looking for a room I can use to dial in from ...


 

anish i can't do arithmetic and figure out timezones, i can only attend the 1st part of the call and not the second, unlike what I said in my email. My plane leaves at 50 minutes after the hour, will be on the call as long as they let me.</B< pre>
anish did it just get better?</B< pre>
anish went on mute</B< pre>


 

Martin C: Scribe: Martin C
Martin C: Not quorate yet so cant approve minutes
Martin C: Topic: action items
Martin C: 20090226-2 [Anish Karmarkar] Propose resolution for BINDINGS-25; depends on BINDINGS-54
Martin C: Anish working on exact text, expect tomorrow
Martin C: no progress on other AI


 

anish was that any better or still a lot of noise when I talk?</B< pre>


 

Martin C: Topic: Namespace Change
Martin C: Namespace has been updated and has an impact on the Bindings specs.
Martin C: Some schemas needed correcting
Martin C: do we need to open an issue for these are does assmbly bind us?


 

anish i don't think we necessarily need an issue, but we should have a motion to accept, since each TC is independent</B< pre>


 

Martin C: two new issues have be logged as a result
Martin C: Mike E did may have made some changes based on changes in assembly filtering through
Martin C: AI: Simon Holdsworth to Diff the schemas to see what Mike E changed to see if issues need raising.
Martin C: AI: Editors to update the specs to update to the new namespace
Martin C: Topic: new issues
Martin C: not quorate so cant do today
Martin C: the issues dont have jira numbers yet
Martin C: Topic: schedule
Martin C: 5th March was target for PR draft
Martin C: We have passed this date, and we still have 8 open issues, and 10-12 issues needing to be applied
Martin C: Martin: are we priortizing any specs or all together
Martin C: Simon: no and might not have significant effect
Martin C: Simon: ws has most issues open, then jms, jca has none


 

Dave Booz so the most important binding has the most work left to do</B< pre>


 

Martin C: Anish: should focus on ws binding as this has significance wrt assembly
Martin C: Anish: but only useful if it effects people's editing priorities
Martin C: Simon: can think about reassigning priority off jms
Martin C: might help to reduce backlog of ws issues
Martin C: Topic: issues


 

Bryan Aupperle: FYI, 5 open issues against WS (2, 23, 25, 43, 54)  3 open issues agains JSM (39, 48, 60)  1 open issue against JCA (45)


 

Martin C: Most issues owners not on the call so cant really proceed
Martin C: Bindings-2
Martin C: Simon: a lot of issues in applied state but have been incorporated into CDs. So all applied issues in CD01 and CD02 need to be closed


 

Simon Holdsworth: Bindings-45 was resolved on last weeks call, state on JIRA not updated yet


 

Martin C: AI: Simon to talk to eric about closing applied issues


 

anish: can we talk about 39?


 

Martin C: Bindings-60: simon is writing a proposal so not worth talking until thet is ready
Martin C: Bindings-39: callbacks and jms


 

anish i have to go offline and walk towards my gate</B< pre>


 

Martin C: Simon H: assumes that callback might use a different binding than the forward request, so changes proposed based on that
Martin C: Anish: assumes only thing is needed is a callback address. This assumption may not be correct for all technologies
Martin C: Simon: wants to avoid direction that opens a can of worms
Martin C: Bryan: will have different biding elemenst in the scdl?
Martin C: Simon: to submit a new proposal
Martin C: Bindings-48
Martin C: Simon: proposal based on an email from Mike E on mayprovides
Martin C: Simon: not clear if conflicts between a binding and mayprovides is allowed
Martin C: Dave: if there are clear conflicts then its an error
Martin C: but other configuation errors may occur
Martin C: Simon: sounds like thats an instance thing
Martin C: Mayprovides applies to type no instance
Martin C: Might need to extend binding type to cover capabilites
Martin C: Simon requests people to look at his recent email on this
Martin C: AOB:
Martin C: none
Martin C: Meeting closed. Next meeting tomorrow

 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]