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 for SCA Bindings TC for 2009-12-17



anonymous morphed into Laurent Domenech
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 
Eric Johnson TIBCO Software Inc. (LOA) 
David Booz IBM 
Anish Karmarkar Oracle Corporation 
Ashok Malhotra Oracle Corporation 

Agenda bashing 

2. Approval of the minutes from 19th November and 10th December: 

http://www.oasis-open.org/committees/download.php/35277/SCA%20Bindings%20minutes%202009-11-19.doc 
http://www.oasis-open.org/committees/download.php/35552/SCA%20Bindings%20minutes%202009-12-10.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) 

4. New Issues 

http://www.osoa.org/jira/browse/BINDINGS-110 
What is the purpose of definitions/binding element (for JMS binding)? 

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-107 
What is the purpose of definitions/binding element? 
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 

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 

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 

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: no proposed resolution 

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
Eric Johnson: Scribe: Eric
Eric Johnson: ten minutes in 55% of voting members present
Eric Johnson: Topic: Approval of the minutes
Eric Johnson: Minutes for 2009-11-19 approved without objection.
Eric Johnson: Minutes for 2009-12-10 approved without objection
Eric Johnson: Topic: Action items
Eric Johnson: All action items are still pending.
Eric Johnson: Topic: New issues
Eric Johnson: Subtopic: BINDINGS-110
Eric Johnson: Simon: Any comments on the issue?
Eric Johnson: Ashok: There is a bindingType in the definitions file.  Are we actually defining bindingType and binding?  Is it a typo?
Eric Johnson: Simon H: Definitely not a typo - in JCA and JMS, there is a specific use for the binding element.
Eric Johnson: ... we did open BINDINGS-107 against the JCA spec, this is the corresponding one for JMS.
Eric Johnson: Motion: open BINDINGS-110 - Eric moves, Ashok 2nds.
Eric Johnson: No objections to unanimous consent, motion passes, issue is opened.
Eric Johnson: Topic: Open Issue Discussion
Eric Johnson: Subtopic: BINDINGS-107
Eric Johnson: Simon H: Intent was to have something you could put in the definitions file, and then point to that from other bindings.  Really just a way to reuse a part of binding element from several places.
Eric Johnson: ... consensus was that this really isn't necessary for the binding to work, perhaps a usability question, but there are a variety of possible solutions besides the current one.
Eric Johnson: ... Proposal on the table is to remove the existing use of the binding element in the definitions file.
Eric Johnson: Eric: There's some concern that this issue affects the assembly specification.  How does the proposed resolution affect the assembly spec.
Eric Johnson: Simon: We would need to notify the Assembly-TC that we've removed the dependency on this.
Eric Johnson: Eric: And then the Assembly-TC might decide to remove the binding element from the definitions file altogether?
Eric Johnson: Simon: Yes.
Eric Johnson: Simon: Details for the JCA binding....
Eric Johnson: Eric: Has anyone else done a review of the proposal to see if they're happy with it?
Eric Johnson: Eric: Move to resolve BINDINGS-107 with the proposal in the email linked from the minutes.
Eric Johnson: Ashok: 2nd.
Eric Johnson: Simon: Any objections?
Eric Johnson: No objections - motion passes, BINDINGS-107 is resolved.
Eric Johnson: Subtopic: BINDINGS-110
Eric Johnson: Simon: Going through proposal for BINDINGS-110...
Eric Johnson: Simon: Anyone ready to propose to resolve...?
Eric Johnson: Eric: Has anyone looked over Simon's proposal to see if he missed anything?
Eric Johnson: Simon: Looks like the answer is the same.
Eric Johnson: Eric: Move that we adopt the direction to remove references to the binding elements in the definitions file.
Eric Johnson: Ashok: 2nd.
Eric Johnson: Simon: Any objections?
Eric Johnson: ... no objections, the motion has passed, the statement of direction has been accepted.
Eric Johnson: Subtopic: BINDINGS-96
Eric Johnson: Simon H: Going through the proposal
Eric Johnson: ...
Eric Johnson: Eric: One concern - it seems like a lot of work to go ahead and lay out all the special cases in the way we have.  Could we turn it around and state the one case where we do need scaCallbackDestination?
Eric Johnson: Simon H: How about I create a rev of the doc with the proposed changes?
Eric Johnson: Action: Simon to create revision of CD03 with proposed resolution to BINDINGS-96
Eric Johnson: Subtopic: BINDINGS-94
Eric Johnson: Simon: Some overlap with BINDINGS-96, in that it relates to the definition of scaCallbackDestination.
Eric Johnson: Simon: Detail of proposal - changes the definition to use the IETF proposal.
Eric Johnson: ... Actual proposal in resolution builds on proposed resolution from BINDINGS-96
Eric Johnson: Eric: What of the discussion I started?
Eric Johnson: Simon: Cannot see the point of additional flexibility....
Eric Johnson: Eric: For SOAP/JMS we're looking at the fact that existing vendors have URIs that they may want to preserve.
Eric Johnson: Eric: Perhaps not an important thing, because there's no legacy support required here.
Eric Johnson: Simon: Meeting is adjourned.  Next meeting is the first week in January.



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