SCA Bindings Raw Minutes for 16 June 2011

1. Opening 

Introductions 

Scribe assignment 

Top of the scribe list: 

Plamen Pavlov SAP AG 

Tom Rutt Fujitsu Limited 

Eric Johnson TIBCO Software Inc. 

Anish Karmarkar Oracle Corporation 

Martin Chapman Oracle Corporation 

Bryan Aupperle IBM 

Ashok Malhotra Oracle Corporation 

Agenda bashing 

2. Approval of the minutes from 9 June:

http://www.oasis-open.org/committees/download.php/42491/SCA%20Bindings%20minutes%202011-06-09.doc

3. Actions 

20110519-01 [Simon Holdsworth] Look
into whether we need a testcase for the updated normative statement in
BJM60009 [following resolution of BINDINGS-157]. 

4. New Issues 

No new issues 

5. Open Issues 

http://www.osoa.org/jira/browse/BINDINGS-153

write new tests for TA-20021 TA-20022
TA-20028 TA-20032TA-20034 TA-20035 TA-40007 TA-50008 TA-50009 

Status: summary in email http://lists.oasis-open.org/archives/sca-bindings/201106/msg00041.html

http://www.osoa.org/jira/browse/BINDINGS-166

Section 6.4 contains optional normative
statements 

http://www.osoa.org/jira/browse/BINDINGS-167

WSCB has separate conformance points
in the Web services specification 

http://www.osoa.org/jira/browse/BINDINGS-168

BWS20034 & BWS20036 are optional
normative statements 

6. Potential new JMS binding testcase

Discuss potential new JMS binding testcase
as described in: 

http://lists.oasis-open.org/archives/sca-bindings/201105/msg00036.html

7. AOB

 

Scribe: Mike Edwards

anonymous morphed into anish1

Item 1 Agenda Bashing

no changes

Item 2 Approval of Minutes

Minutes of 9th June are approved

Item 3 Action Items

20110519-01 [Simon Holdsworth] Look
into whether we need a testcase for the updated normative statement in
BJM60009 [following resolution of BINDINGS-157].

DONE

Item 5 Open Issues

anish got to step away for a bit

http://www.osoa.org/jira/browse/BINDINGS-153

write new tests for TA-20021 TA-20022
TA-20028 TA-20032TA-20034 TA-20035 TA-40007 TA-50008 TA-50009 

Status: summary in email http://lists.oasis-open.org/archives/sca-bindings/201106/msg00041.html

anish back

Simon review the email above

Anish agrees that the summary is good

Simon: Only Bindings 168 affects this
issue

Simon proposes to move on to look at
Bindings 168

http://www.osoa.org/jira/browse/BINDINGS-168

BWS20034 & BWS20036 are optional
normative statements

Mike describes the issue and the proposal
in the JIRA

which is to make SOAP1_2 non-normative

Anish indicates that SOAP 1.2 support
is prevalent and widespread - so why not make it mandatory?

Bryan: The question is small device
situations?

Anish: Not much technical difference
between SOAP 1.2 and SOAP 1.1

Anish - we also require WS_Addressing
support, which is a bigger deal than SOAP 1.1

Bryan - I tend to agree with that argument

Anish moves to resolve Issue 168 by
replacing the SHOULD in both BWS20034 & BWS20036 with a MUST

Ashok seconds

Motion passes unanimoulsy

Issue 168 is resolved

Simon: The implication for Issue 153
is that we have 2 more mandatory statements that must be dealt with.

http://www.osoa.org/jira/browse/BINDINGS-166

Section 6.4 contains optional normative
statements

Mike reviews the issue and the proposal
in JIRA to remove both normative statements

Anish: I agree with removal of the second
statement

Anish: If we remove the first one, then
it would be good to add a non-normative statement elsewhere in the spec
indicating that implementations can support the Callback Protocol

- although we could leave that for the
other issue (167) and deal with that point when we resolve that one

Mike moves to resolve Issue 166 with
the proposal in JIRA

Anish seconds

Motion passes unanimously

Issue 166 is resolved

http://www.osoa.org/jira/browse/BINDINGS-167

WSCB has separate conformance points
in the Web services specification

Mike reviews the issue and the 2 alternative
proposals in the JIRA

- one to make WSCB mandatory

- one to remove WSCB entirely

Anish - I'm in favour of the second
option - a separate WSCB spec

Bryan - concern that our TC charter
may not allow a separate document

Anish - I don't see the difference

Mike - here is the section of the charter:

The following functions and mechanism
are considered as out-of-scope for the SCA Web Service Binding work:

Ensuring interoperability of SCA Web
Service Bindings that utilize existing WSDL documents and those that include
non standard WSDL extensions

Defining SCA binding metadata for non-WS-I
compliant Web services

Defining SCA binding metadata for non-SOAP
based Web services

Mapping of the WSDL type system with
other interface type systems such as Java interfaces

Metadata specific to implementation
of the services e.g. references to JAX-WS handlers to be invoked as part
of dispatching a service request

Support for SOAP intermediaries

Defining new wire-level protocols for
exchanging conversation identifiers and state. Conversation support may
be addressed by reference to existing web service standards.

Simon - I think the TC made a decision
not to have a separate spec and we'd need a special 2/3rds vote to overturn
that

<discussion of options for a way
forward>

Mike moves to close Issue 167 with no
action

Anish seconds

Mike: the notion here is that there
is, inside the Testcase Suite a full implementation of both the WSCB client
and the WSCB server, written as JAX-WS applications

Issue 167 is closed with no action

Simon: We as a TC need to decide our
Exit Criteria

Simon: Re Issue 153 we need to have
test artifacts for any new testcases that are required as part of any resolution
of the issue

COB

Yours, Mike

Dr Mike Edwards
 Mail Point 137, Hursley
Park

STSM
 Winchester, Hants SO21
2JN

SCA & Services
Standards
 United Kingdom

Co-Chair OASIS SCA
Assembly TC
 

IBM Software Group
  

Phone:
+44-1962 818014
  

Mobile:
+44-7802-467431 (274097)
  

e-mail:

  

 

 

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