Mike,
Thanks for recording this. In
turning this into the minutes document, I notice that the vote for opening
issue 124 is not mentioned. This may have been around the time that
we had issues with the chat room application. My recollection is
that the vote went 9 for, 2 against, please confirm this before I post
the final minutes in the doc repository.
Thanks, Simon
Simon Holdsworth
STSM, SCA Bindings Architect; Master Inventor; OASIS SCA Bindings TC Chair,
AT&T and Boeing Lab Advocate
MP 211, IBM UK Labs, Hursley Park, Winchester SO21 2JN, UK
Tel +44-1962-815059 (Internal 245059) Fax +44-1962-816898
Internet -
From:
Mike Edwards/UK/IBM@IBMGB
To:
"OASIS Bindings" <>
Date:
08/03/2010 07:24
Subject:
[sca-bindings] Minutes Raw Text for
TC Meeting of 4th March
Agenda
1. Opening
Introductions
Roll call
Scribe assignment
Top of the scribe list:
Plamen Pavlov SAP AG
Tom Rutt Fujitsu Limited
Ashok Malhotra Oracle Corporation
Martin Chapman Oracle Corporation
David Booz IBM
Eric Johnson TIBCO Software Inc.
Laurent Domenech TIBCO Software Inc.
Bryan Aupperle IBM
Anish Karmarkar Oracle Corporation
Agenda bashing
2. Approval of the minutes from 25th February:
http://www.oasis-open.org/committees/download.php/36574/SCA%20Bindings%20minutes%202010-02-25.doc
3. Actions
20090211-4 [General] Write up HTTP binding use cases
20090709-2 [Editors] Update the WS binding schema appendix title to include
1.1
20091015-8 [Editors] Re: BINDINGS-99 point #8 - look at whether the non-normative
references section is relevant still, or needs to be populated (WS binding)
20091015-9 [Editors] Re: BINDINGS-99 point #9 - clean up naming conventions
section (WS binding)
20091015-10 [Editors] Re: BINDINGS-99 point #10 - look for cleanup to clarify
optionality (WS binding)
20091015-12 [Editors] Re: BINDINGS-99 point #16 - mark Annexes as normative
or not as appropriate (all specs)
20100218-2 [Editors] Make corresponding changes in WS spec as per http://lists.oasis-open.org/archives/sca-bindings/200912/msg00013.html
4. New Issues
http://www.osoa.org/jira/browse/BINDINGS-124
No conformance target for non-SCA runtimes that want to implement SCA WS
Callback Protocol
5. Discuss proposed TC schedule
Updated following discussion on call of 25th Feb
Consider date by which open issues are to be closed or deferred; also consider
raising open vote to 2/3.
4th March: Focus on issues 87, 118
11th March: Focus on issues 111, 120, 121, 122, 123; bindings specs and
TA documents updated for all currently resolved issues and ready for review
for cd review.
18th March: cd vote on bindings specs and TA documents; discuss production
of test case documents/test cases
25th March: Submit cd04 of bindings specs for second public review; Initial
test case documents and test cases prepared for discussion/review
22nd April: Test cases complete
29th April: Submit cd01 of TA documents and test cases for public review
6. 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 and issues raised; needs to be updated for resolved
issues
JMS TA document:
http://www.oasis-open.org/committees/download.php/36374/sca-jmsbinding-1.1-test-assertions-wd05.doc
http://www.oasis-open.org/committees/download.php/36375/sca-jmsbinding-1.1-test-assertions-wd05.pdf
Status: Needs final tidy up for cd review
JCA TA document:
http://www.oasis-open.org/committees/download.php/36155/sca-jcabinding-1.1-test-assertions-wd04.doc
http://www.oasis-open.org/committees/download.php/36156/sca-jcabinding-1.1-test-assertions-wd04.pdf
Comment: http://lists.oasis-open.org/archives/sca-bindings/200909/msg00011.html
Status: Needs to be updated for resolved issues
7. 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-111
binding.jms uses JMS URI scheme even though it is not a valid IETF internet
draft
Raiser: Eric Johnson, owner: Unassigned
Priority: Unassigned
Status: Pending response from Oracle with respect to approval of the IETF
draft
http://www.osoa.org/jira/browse/BINDINGS-118
BWS40005 is ambiguous
Raiser: Anish Karmarkar, owner: Unassigned
Priority: Unassigned
Status: Proposal in email: http://lists.oasis-open.org/archives/sca-bindings/201002/msg00088.html
http://www.osoa.org/jira/browse/BINDINGS-120
Missing normative statements for JCA @uri
Raiser: Simon Holdsworth, owner: Simon Holdsworth
Priority: Unassigned
Status: Propsed resolution in JIRA
http://www.osoa.org/jira/browse/BINDINGS-121
Missing normative statements for binding.jca inboundOperation
Raiser: Simon Holdsworth, owner: Simon Holdsworth
Priority: Unassigned
Status: Propsed resolution in JIRA
http://www.osoa.org/jira/browse/BINDINGS-122
Missing normative statements for binding.jca outboundInteraction
Raiser: Simon Holdsworth, owner: Simon Holdsworth
Priority: Unassigned
Status: Propsed resolution in JIRA
http://www.osoa.org/jira/browse/BINDINGS-123
Missing normative statements for @type attributes
Raiser: Simon Holdsworth, owner: Simon Holdsworth
Priority: Unassigned
Status: Propsed resolution in JIRA
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
Scribe: Mike Edwards
90% of voting members present
Item 1 Agenda Bashing
no changes
Item 2 Minutes from Previous Meeting
Minutes from 25th February
Minutes are approved without change
Item 3 Action Items
20090211-4 [General] Write up HTTP binding use cases
20090709-2 [Editors] Update the WS binding schema appendix title to include
1.1
20091015-8 [Editors] Re: BINDINGS-99 point #8 - look at whether the non-normative
references section is relevant still, or needs to be populated (WS binding)
20091015-9 [Editors] Re: BINDINGS-99 point #9 - clean up naming conventions
section (WS binding)
20091015-10 [Editors] Re: BINDINGS-99 point #10 - look for cleanup to clarify
optionality (WS binding)
20091015-12 [Editors] Re: BINDINGS-99 point #16 - mark Annexes as normative
or not as appropriate (all specs)
20100218-2 [Editors] Make corresponding changes in WS spec as per http://lists.oasis-open.org/archives/sca-bindings/200912/msg00013.html
Anish is working on a new draft of the WS Binding spec that should complete
most of these
Item 4. New Issues
http://www.osoa.org/jira/browse/BINDINGS-124
No conformance target for non-SCA runtimes that want to implement SCA WS
Callback Protocol
Anish discusses the issue
Latest Proposal:
http://lists.oasis-open.org/archives/sca-bindings/201003/msg00000.html
Anish describes the outline of the proposal
- new conformance targets and related conformance requirements
Eric: Concern I have is that the way forward is to define targets not specific
to SCA - and that this might fall outside our charter. We would also
have to define test suite components that would not be SCA based - that
would be a lot of work.
Anish: I think that it is in scope. Defining what clients and services
have to do is within the scope of the charter.
- with respect to testing, I have not thought of that.
- perhaps all we need to do is to test between SCA runtimes.
- testing is a larger discussion
Martin: I think that this is in scope. There is no change in function
here - is just a relabelling - it means no change to the tests either.
Tom: If we write the conformance claims right, the tests will be the same
for any implmentation, SCA or non-SCA. So we don't
need to "test the world".
Anish: We should try to enable interoperability and bring clarity to this.
Anish moves to open Issue 124. Seconded by Martin.
Item 5. TC Schedule
Proposed schedule:
4th March: Focus on issues 87, 118
11th March: Focus on issues 111, 120, 121, 122, 123; bindings specs and
TA documents updated for all currently resolved issues and ready for review
for cd review.
18th March: cd vote on bindings specs and TA documents; discuss production
of test case documents/test cases
25th March: Submit cd04 of bindings specs for second public review; Initial
test case documents and test cases prepared for discussion/review
22nd April: Test cases complete
29th April: Submit cd01 of TA documents and test cases for public review
Item 7 Open Issues
Issue 118
http://www.osoa.org/jira/browse/BINDINGS-118
BWS40005 is ambiguous
Raiser: Anish Karmarkar, owner: Unassigned
Priority: Unassigned
Status: Proposal in email: http://lists.oasis-open.org/archives/sca-bindings/201002/msg00088.html
Simon discusses the issue and the proposal above.
anish: FWIW, simon, your proposal looks good to me
Simon: Makes the behaviour of the simple forms of <binding.ws/> will
be predictable
Anish: Question: not certain if we need to add policySets to the list.
Simon: Probably it was an oversight to leave them out.
- include policySets in that list
anish: In the event that the transport details are not determined by use
of the @wsdlElement attribute, policy intents, policy sets, or extensions
to the binding.ws element, an SCA runtime MUST enable the default transport
binding rules.
Mike moves to resolve Issue 118 by replacing the BWS40005 normative statement
with the following: In the event that the transport details are not determined
by use of the @wsdlElement attribute, policy intents, policySets, or extensions
to the binding.ws element, an SCA runtime MUST enable the default transport
binding rules.
Dave seconds
Anish: Should @uri be included in that list?
anish: In the event that the transport details are not determined by use
of the @wsdlElement attribute, @uri attribute, endpointReference element,
policy intents, policy sets or extensions to the binding.ws element, an
SCA runtime MUST enable the default transport binding rules.
Eric moves to amend the motion with the text proposed by Anish above
seconded by Anish
Amendment is approved
Amended motion is passed unanimoulsy
Issue 87:
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
Anish discusses the points in the email above
Simon: So the email has the response to the original comment: no changes
to the specs?
Anish: Yes
Simon: Is the TC happy for a response to be drafted along the lines of
the first 3 items in the email?
Tom: Moves to close Issue 87 with no change to the specification.
Eric seconds
Motion passes unanimously
Issue 87 is closed
ACTION: 20100304-01: (Anish) Draft a formal response to the original PR
comment, ready for TC review.
(for Issue 87)
COB
Yours, Mike.
Strategist - Emerging Technologies, SCA & SDO.
Co Chair OASIS SCA Assembly TC.
IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN, Great Britain.
Phone & FAX: +44-1962-818014 Mobile: +44-7802-467431
Email:
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU
