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 chat log 14 Jan 2010


Simon Holdsworth: Audio conference: 
 
Meeting Number: * 913929 * (press * before and after the digits) 
 
Phone numbers: 
 
Austria = Vienna 026822056419 
Belgium = Brussels 022901709 
China = Beijing 01052237296 
Czech Republic = Prague 239014054 
Denmark = Copenhagen 32714982 
France = Lyon 0426840196 Marseille 0488915310 Paris 0170994364 
France TollFree = 0800944795 
Germany = Berlin 030726167296 Dusseldorf 021154073845 Frankfurt 069710445413 Hamburg 040809020620 Munich 089244432767 Stuttgart 0711490813212 
Germany TollFree = 08006646304 
India = Mumbai 02261501417 
Ireland = Dublin 014367612 
Italy = Milan 0230413007 Rome 06452108288 Turin 01121792100 
Japan = Tokyo 0357675037 
Netherlands = Amsterdam 0207965349 
Poland Toll-free = 008001213648 
Portugal Toll Free = 800782079 
Russia = Moscow 84999222481 
Russia Toll Free = 81080022074011 
South Africa Toll-free = 0800982617 
Spain = Barcelona 934923140 Madrid 917889793 
Sweden = Stockholm 0850520404 
Switzerland = Geneva 0225927186 
UAE Toll-free = 8000440387 
UK = Birmingham 01212604587 London 02071542988 Manchester 01612500379 
UK Toll Free = 08003581667 
USA = 19543344789 
USA & Canada Toll Free = 18665289390
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 
Martin Chapman Oracle Corporation 
Khanderao Kand Oracle Corporation 
Bryan Aupperle IBM 
David Booz IBM 
Anish Karmarkar Oracle Corporation 
Ashok Malhotra Oracle Corporation 
Eric Johnson TIBCO Software Inc. 
 
Agenda bashing 
 
2. Approval of the minutes from 17th December: 
 
http://www.oasis-open.org/committees/download.php/35681/SCA%20Bindings%20minutes%202009-12-17.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. 
20091015-1 [Anish Karmarkar] Raise new issues found during TA creation for obvious bugs in WS binding spec 
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) 
20091217-1 [Simon Holdsworth] Create revision of CD03 with proposed resolution to BINDINGS-96 
 
4. New Issues 
 
5. Test Assertions/Test cases 
 
Current status: 
 
Overall: Awaiting current set of issues to be resolved and applied, at which point editors will need to update TA docs and then we can review them with the aim of getting to CD. 
 
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. 
 
6. Open issue discussion 
 
Public review comment issues: 
 
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 
 
Other open issues: 
 
http://www.osoa.org/jira/browse/BINDINGS-110 
What is the purpose of definitions/binding element (for JMS binding)? 
Raiser: Anish Karmarkar, owner: Unassigned 
Priority: 1 (Impact on other specifications) 
Status: Proposed resolution in email http://lists.oasis-open.org/archives/sca-bindings/200911/msg00035.html 
Spec with proposed updates: http://lists.oasis-open.org/archives/sca-bindings/200912/msg00027.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 email http://lists.oasis-open.org/archives/sca-bindings/200912/msg00008.html 
Spec with proposed updates: http://lists.oasis-open.org/archives/sca-bindings/200912/msg00027.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/200912/msg00009.html 
Latest email: http://lists.oasis-open.org/archives/sca-bindings/200912/msg00025.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 email http://lists.oasis-open.org/archives/sca-bindings/200911/msg00010.html 
 
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 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 email http://lists.oasis-open.org/archives/sca-bindings/200911/msg00010.html 
 
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 email http://lists.oasis-open.org/archives/sca-bindings/200911/msg00037.html 
 
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 email http://lists.oasis-open.org/archives/sca-bindings/200912/msg00019.html 
 
http://www.osoa.org/jira/browse/BINDINGS-101 
Opaque references - need for a terminology list? 
Raiser: PR comment, owner: Unassigned 
Priority: Unassigned 
Status: Proposed resolution in email http://lists.oasis-open.org/archives/sca-bindings/200912/msg00013.html 
 
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: Draft proposal in email http://lists.oasis-open.org/archives/sca-bindings/201001/msg00002.html 
 
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


 

Martin C: Scribe: MartinC
Martin C: topic: agenda
Martin C: Approved as posted
Martin C: topic: Minutes
Martin C: Approval of the minutes from 17th December: 
 
http://www.oasis-open.org/committees/download.php/35681/SCA%20Bindings%20minutes%202009-12-17.doc
Martin C: No comments. Approved w/o
Martin C: topic: AI
Martin C: 20090820-2 [Simon Holdsworth] Look at the templating mechanism with respect to policy.
Martin C: Obselete
Martin C: 20091217-1 [Simon Holdsworth] Create revision of CD03 with proposed resolution to BINDINGS-96
Martin C: Done
Martin C: All others pending
Martin C: topic: Open issues
Martin C: http://www.osoa.org/jira/browse/BINDINGS-110
Martin C: Directional resolution made at last meeting.
Martin C: Proposed resolution in email http://lists.oasis-open.org/archives/sca-bindings/200911/msg00035.html 
Spec with proposed updates: http://lists.oasis-open.org/archives/sca-bindings/200912/msg00027.html
Martin C: Simon goes over the changes.
Martin C: changes in 3.0 (before 3.1)
Martin C: removal of attributes
Martin C: 7.6 example
Martin C: section 8, conformance changes
Martin C: Plus schema changes in appendix A
Martin C: Eric J: Moves to resolves 110 with proposal in attachement http://lists.oasis-open.org/archives/sca-bindings/200912/msg00027.html. 2nd Mike E
Martin C: s/ement/ment/
Martin C: Note: appendix b normative statements deleted as a result as well


 

Eric Johnson: (and note that Eric was aware of those deletions when I made my motion.)


 

Martin C: Passed w/o
Martin C: s/resolves/resolve/
Martin C: http://www.osoa.org/jira/browse/BINDINGS-96 
BJM60012 and BJM60013 conflict 
Raiser: Simon Holdsworth, owner: Simon Holdsworth 
Priority: Unassigned 
Status: Proposed resolution in email http://lists.oasis-open.org/archives/sca-bindings/200912/msg00008.html 
Spec with proposed updates: http://lists.oasis-open.org/archives/sca-bindings/200912/msg00027.html
Martin C: Changes in section 6 of msg0027.html
Martin C: s/0027/00027/
Martin C: First change to [BJM60002]
Martin C: Changes in 6.4 - Callbacks
Martin C: [BJM60011] modified
Martin C: changes in 6.4.1 (incl 60011)
Martin C: [BJM60012] changed
Martin C: descriptive text changed
Martin C: changes in 6.4.2
Martin C ping</B< pre>
Martin C: mostly editorial deletions
Martin C: section 6.4.3 deleted
Martin C: s/mostly //
Martin C: Mike E: struggling over use cases of 2 different wanys to do things, mostly to accomodate non-sca clients
Martin C: Mike E: this seems to complicate the SCA ones!
Martin C: Dave: bindings mostly are used to connect to non-sca, so don't see a problem with this proposal
Martin C: Mike E: shouldnt SCA aware use call back destination at all times?


 

anish: given that we have a wsdl extension for callback, why won't a "non-SCA" client not use callbacks?


 

Martin C: Mike E: was talking about clients that no nothing about callbacks


 

anish: why not use defaulting?
anish: i.e., if scaCallbackDestination  is not set and is required (because of bidirectional interfaces) the use JMSReplyTo


 

Martin C: Eric: seem to switch from proposal to use case
Martin C: Mike E: the resolution works but puts more work on the SCA client
Martin C: Eric: Do we have to support the use case
Martin C: Martin: repeats what Dave said
Martin C: Simon: an important goal to intact with non-sca
Martin C: s/intact/interact/
Martin C: Anish: would defaulting solve the problem
Martin C: If destination not present, use replyto, if none its an error
Martin C: Simon: the original text assumes the client has some optional behaviour, so being explicit might be better.
Martin C scribe got losthttp://webconf.soaphub.org/conf/wink.gif</B< pre>
Martin C: Simon: Bottom line is client has to do something with a response, and a call back needs to be handled differently, so more likely to use different addresses.
Martin C close to time</B< pre>
Martin C: The previous resolution to 110, did not include the changes in section 6 which are related to this issue, 96. Therefore section 6 changes must be ignored by the editors that apply resolution to 110.
Martin C: s/apply/apply to/
Martin C: AOB
Martin C: straggler roll
Martin C: Meeting closed

 



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