SCA Bindings Telecon has been modified by Mr. Simon Holdsworth
Date: Thursday, 09 October 2008
Time: 12:00pm - 01:00pm ET
Event Description:
SCA Bindings TC weekly telecon
Chat room:
http://webconf.soaphub.org/conf/room/sca-bindings-TC
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
Agenda:
1. Opening
Introductions
Roll call
Scribe assignment
Top 10 on the scribe list (full list below, brackets indicate currently non-voting members):
Tom Rutt Fujitsu Limited
(Michael Beisiegel IBM)
(Sanjay Patil SAP AG)
Nimish Hathalia TIBCO Software Inc.
Plamen Pavlov SAP AG
Vladimir Savchenko SAP AG
Eric Johnson TIBCO Software Inc.
Simon Nash IBM
Ashok Malhotra Oracle Corporation
David Booz IBM
Agenda bashing
2. Approval of minutes of SCA-Binding TC meeting of 25th September
http://www.oasis-open.org/committees/download.php/29536/SCA%20Bindings%20minutes%202008-09-25.doc
3. Actions
20080304-9 [Editors] Update specs for outcome of ASSEMBLY-55 when it is resolved.
20080424-1 [Editors] Action: editors to incorporate editorial issue from Erics email into the specs. Original email: http://lists.oasis-open.org/archives/sca-bindings/200804/msg00008.html Latest email: http://lists.oasis-open.org/archives/sca-bindings/200806/msg00023.html (done for WS, still outstanding for JMS and JCA)
20080717-2 [Editors] Produce a revision of the forthcoming CDs to include RFC2119 re-writing by Sept 15th 2008
20080717-4 [Sanjay Patil] Provide examples for issue 24
20080717-6 [Vladimir Savchenko] Send out a proposal for how WSDL bindings and portTypes relate to each other. Target: 14th August
20080717-10 [Simon Holdsworth] Submit proposal for issue 7. Pending acceptance/resolution of Policy issue 60
20080904-1 [Editors] update SOAP intent as per email http://lists.oasis-open.org/archives/sca-bindings/200808/msg00072.html
4. New Issues
Please note, as per resolution on 17th July 2008, new issues received on the mailing list after Noon GMT 18th October can only be opened using the same voting rules as re-opening a closed issue (2/3 majority of a full TC vote)
BINDINGS-41: naming of binding specs/schema files
http://www.osoa.org/jira/browse/BINDINGS-41
BINDINGS-42: Clarify default data binding for JMS
http://www.osoa.org/jira/browse/BINDINGS-42
BINDINGS-43: Update binding.ws spec for wireFormat/operationSelection elements
http://www.osoa.org/jira/browse/BINDINGS-43
BINDINGS-44: Update binding.jms spec for wireFormat/operationSelection elements
http://www.osoa.org/jira/browse/BINDINGS-44
BINDINGS-45: Update binding.jca spec for wireFormat/operationSelection elements
http://www.osoa.org/jira/browse/BINDINGS-45
BINDINGS-46: The binding.jms/headers/@JMSCorrelationID attribute is inappropriate
http://www.osoa.org/jira/browse/BINDINGS-46
BINDINGS-47: How are mayProvide intents on bindings satisfied
http://www.osoa.org/jira/browse/BINDINGS-47
BINDINGS-48: Clarify default data binding for JMS when sending messages
http://www.osoa.org/jira/browse/BINDINGS-48
5. Open Issue Discussion
Open issues with proposed resolutions:
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/200808/msg00071.html Latest email: http://lists.oasis-open.org/archives/sca-bindings/200808/msg00073.html
http://www.osoa.org/jira/browse/BINDINGS-11
"Formal" WSDL generation is unclear, ambiguous, and incomplete
Raiser: Eric Johnson, owner: Eric Johnson, Anish Karmarkar
Status: Latest email: http://lists.oasis-open.org/archives/sca-bindings/200810/msg00012.html
http://www.osoa.org/jira/browse/BINDINGS-27
Identifying data binding and operation selection
Raiser: Mike Rowley, owner: Mike Edwards
Status: ASSEMBLY-79 resolution accepted, new issues opened for impact on each binding.
http://www.osoa.org/jira/browse/BINDINGS-31
What is a "plain name" for a connection factories or activation specs, and how is one distinguished from a JNDI name?
Raiser: Eric Johnson, owner: Simon Holdsworth
Status: Updated proposal in email http://lists.oasis-open.org/archives/sca-bindings/200810/msg00013.html
http://www.osoa.org/jira/browse/BINDINGS-40
Clarify rules around combination of destination, CF and AS elements
Raiser: Simon Holdsworth, owner: Simon Holdsworth
Status: Latest email: http://lists.oasis-open.org/archives/sca-bindings/200810/msg00004.html
Open issues with identified resolution owner:
http://www.osoa.org/jira/browse/BINDINGS-7
JMS bindingType and ordered intent - clarification needed
Raiser: Peter Peshev, owner Simon Holdsworth
Status: Awaiting decision on POLICY-60.
http://www.osoa.org/jira/browse/BINDINGS-21
Support for callback and conversation ID-s in bindings
Raiser: Peter Peshev, owner Peter Peshev
Status: Proposed resolution in issue
Notes: As for BINDINGS-2, this is waiting for clarification around conversations at the assembly level
Open issues with no identified resolution owner:
http://www.osoa.org/jira/browse/BINDINGS-22
Bindings specifications should provide exemplary Implementations for Callbacks and Conversations
Raiser: Mike Edwards
Status: No proposed resolution
Notes: As for BINDINGS-2, this is waiting for clarification around conversations at the assembly level
http://www.osoa.org/jira/browse/BINDINGS-23
@wsdlElement definition needs clarification on "equivalent" and use of WSDL 2.0 constructs
Raiser: Eric Johnson
Status: Specific resolution text required
http://www.osoa.org/jira/browse/BINDINGS-24
Which wire did a message arrive on?
Raiser: Sanjay Patil
Status: Waiting for examples from Sanjay as per 20080717-4
http://www.osoa.org/jira/browse/BINDINGS-25
Is it required that every implementation of binding.ws support the soap intent?
Raiser: Anish Karmarkar
Status: No current proposal. Latest email: http://lists.oasis-open.org/archives/sca-bindings/200807/msg00006.html
http://www.osoa.org/jira/browse/BINDINGS-29
Properties on Bindings
Raiser: Piotr Przybylski
Status: No current proposal; defer until Policy 15 (External Attachment) is resolved
10. AOB
-------------------------------------------------------------------
*Revolving list of scribes*
Tom Rutt Fujitsu Limited
(Michael Beisiegel IBM)
(Sanjay Patil SAP AG)
Nimish Hathalia TIBCO Software Inc.
Plamen Pavlov SAP AG
Vladimir Savchenko SAP AG
Eric Johnson TIBCO Software Inc.
Simon Nash IBM
Ashok Malhotra Oracle Corporation
David Booz IBM
Bryan Aupperle IBM
Khanderao Kand Oracle Corporation
Laurent Domenech TIBCO Software Inc.
Piotr Przybylski IBM
Anish Karmarkar Oracle Corporation
Martin Chapman Oracle Corporation
Minutes:
This event is one in a list of recurring events.
Other event dates in this series:
Thursday, 02 October 2008, 12:00pm to 01:00pm ET
Thursday, 16 October 2008, 12:00pm to 01:00pm ET
Thursday, 23 October 2008, 12:00pm to 01:00pm ET
Thursday, 30 October 2008, 12:00pm to 01:00pm ET
Thursday, 06 November 2008, 12:00pm to 01:00pm ET
Thursday, 13 November 2008, 12:00pm to 01:00pm ET
Thursday, 20 November 2008, 12:00pm to 01:00pm ET
Thursday, 27 November 2008, 12:00pm to 01:00pm ET
Thursday, 04 December 2008, 12:00pm to 01:00pm ET
Thursday, 11 December 2008, 12:00pm to 01:00pm ET
Thursday, 18 December 2008, 12:00pm to 01:00pm ET
Thursday, 25 December 2008, 12:00pm to 01:00pm ET
Thursday, 01 January 2009, 12:00pm to 01:00pm ET
Thursday, 08 January 2009, 12:00pm to 01:00pm ET
Thursday, 15 January 2009, 12:00pm to 01:00pm ET
Thursday, 22 January 2009, 12:00pm to 01:00pm ET
Thursday, 29 January 2009, 12:00pm to 01:00pm ET
Thursday, 05 February 2009, 12:00pm to 01:00pm ET
Thursday, 12 February 2009, 12:00pm to 01:00pm ET
Thursday, 19 February 2009, 12:00pm to 01:00pm ET
Thursday, 26 February 2009, 12:00pm to 01:00pm ET
Thursday, 05 March 2009, 12:00pm to 01:00pm ET
Thursday, 12 March 2009, 12:00pm to 01:00pm ET
Thursday, 19 March 2009, 12:00pm to 01:00pm ET
Thursday, 26 March 2009, 12:00pm to 01:00pm ET
Thursday, 02 April 2009, 12:00pm to 01:00pm ET
Thursday, 09 April 2009, 12:00pm to 01:00pm ET
Thursday, 16 April 2009, 12:00pm to 01:00pm ET
Thursday, 23 April 2009, 12:00pm to 01:00pm ET
Thursday, 30 April 2009, 12:00pm to 01:00pm ET
Thursday, 07 May 2009, 12:00pm to 01:00pm ET
Thursday, 14 May 2009, 12:00pm to 01:00pm ET
Thursday, 21 May 2009, 12:00pm to 01:00pm ET
Thursday, 28 May 2009, 12:00pm to 01:00pm ET
Thursday, 04 June 2009, 12:00pm to 01:00pm ET
Thursday, 11 June 2009, 12:00pm to 01:00pm ET
Thursday, 18 June 2009, 12:00pm to 01:00pm ET
Thursday, 25 June 2009, 12:00pm to 01:00pm ET
Thursday, 02 July 2009, 12:00pm to 01:00pm ET
Thursday, 09 July 2009, 12:00pm to 01:00pm ET
Thursday, 16 July 2009, 12:00pm to 01:00pm ET
Thursday, 23 July 2009, 12:00pm to 01:00pm ET
Thursday, 30 July 2009, 12:00pm to 01:00pm ET
Thursday, 06 August 2009, 12:00pm to 01:00pm ET
Thursday, 13 August 2009, 12:00pm to 01:00pm ET
Thursday, 20 August 2009, 12:00pm to 01:00pm ET
Thursday, 27 August 2009, 12:00pm to 01:00pm ET
Thursday, 03 September 2009, 12:00pm to 01:00pm ET
Thursday, 10 September 2009, 12:00pm to 01:00pm ET
Thursday, 17 September 2009, 12:00pm to 01:00pm ET
Thursday, 24 September 2009, 12:00pm to 01:00pm ET
View event details:
http://www.oasis-open.org/apps/org/workgroup/sca-bindings/event.php?event_id=19432
PLEASE NOTE: If the above link does not work for you, your email
application may be breaking the link into two pieces. You may be able to
copy and paste the entire link address into the address field of your web
browser.
