Bindings TC Minutes - raw text, May 12

AGENDA

1. Opening 

Introductions 

Scribe assignment 

Top of the scribe list: 

Plamen Pavlov SAP AG 

David Booz IBM 

Martin Chapman Oracle Corporation 

Tom Rutt Fujitsu Limited 

Anish Karmarkar Oracle Corporation 

Ashok Malhotra Oracle Corporation 

Bryan Aupperle IBM 

Eric Johnson TIBCO Software Inc. 

Agenda bashing 

2. Approval of the minutes from 21 April:

http://www.oasis-open.org/committees/download.php/42005/SCA%20Bindings%20minutes%202011-04-21.

3. Actions 

20110310-03 [Editors] Make the change
to the JMS spec doc + Testcases doc described in http://lists.oasis-open.org/archives/sca-bindings/201103/msg00007.html

20110331-01 [Anish Karmarkar] Open issues
for the two test assertion comments (BWS-TA-50009, BWS-TA-50010) 

20110421-01 [Bryan Aupperle] Look up
what the Assembly TC did in the cases that Bryan referred to above [tests
deferred to other specs] 

4. New Issues 

BINDINGS-160:  BWS50013's target
is a WSDL 1.1. document, is that appropriate? 

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

BINDINGS-161: BWS50015's target is a
WSDL 1.1. document, is that appropriate? 

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

5. Open Issues 

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

BWS20027 is tested in the POJO tests

Status: Proposed resolution pending
AI 20110421-01 

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: Proposed resolution in JIRA

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

Clarify optionality of MAY statements
in JMS binding spec 

Status: Proposed resolution in JIRA

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

Clarify optionality of SHOULD statement
BJM30030 

Status: Proposed resolution in JIRA

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

Clarify optionality of SHOULD statement
BJM60009 

Status: Alternative proposed resolutions
in JIRA 

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

Clarify optionality of SHOULD statement
BJM60016 

Status: Proposed resolution in JIRA

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

Clarify optionality of SHOULD statement
BJM60001 

Status: No proposed resolution, needs
discussion 

6. AOB 

Eric moves to have Mike Edwards act
as pro-tem chair

Ashok seconds

Motion approved unanimously

Item 1 Agenda Bashing

No changes

Item 2 Meeting Minutes

Minutes of 21st April

Minutes accepted without change

Item 3 Actions

20110310-03 [Editors] Make the change
to the JMS spec doc + Testcases doc described in http://lists.oasis-open.org/archives/sca-bindings/201103/msg00007.html

20110331-01 [Anish Karmarkar] Open issues
for the two test assertion comments (BWS-TA-50009, BWS-TA-50010) 

20110421-01 [Bryan Aupperle] Look up
what the Assembly TC did in the cases that Bryan referred to above [tests
deferred to other specs]

Anish's item is DONE

Bryan's item is DONE

Item 4 New Issues

BINDINGS-160:  BWS50013's target
is a WSDL 1.1. document, is that appropriate? 

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

Anish describes the issue.  Derived
from what we found when reviewing the TAs for Web services.

Anish moves to open Issue 160

Ashok seconds

Motion accepted unanimously

Issue 160 is open.

anish: Reword BWS50013 to read:

"A WSDL 1.1 portType element associated
with an SCA service or reference MUST NOT have the

WSCallback policy assertion attached"

"associated with" is intended
to cover both the referencing of a concrete WSDL document from within

an SCA XML document (by any element)
and also cover the dynamic creation and advertising of a

WSDL by a runtime service.

<we can even add these explanatory
words if necessary>

anish: email that has the proposal:
http://lists.oasis-open.org/archives/sca-bindings/201105/msg00011.html

anish: The following is the list of
WSDL/1.1 elements whose scope contains the

Policy Subjects allowed for a WSCallback
policy assertion but which cannot

have WSCallback policy assertions attached:
wsdlPortType [BWS50013]

Anish proposed some modifications to
this proposal (email here:  http://lists.oasis-open.org/archives/sca-bindings/201105/msg00014.html)

anish: 1) replace BWS50013 with: The
following is the list of WSDL/1.1 elements whose scope contains the

Policy Subjects allowed for a WSCallback
policy assertion but which cannot

have WSCallback policy assertions attached:
wsdlPortType

anish: 2) In section 6.1 add: "A
WSDL 1.1 portType element associated with an SCA service or reference MUST
NOT have the

WSCallback policy assertion attached."

anish: 3) follow (2) with: "associated
with" is intended to cover both the referencing of a concrete WSDL
document from within

an SCA XML document (by any element)
and also cover the dynamic creation and advertising of a

WSDL by a runtime service.

Anish moves to resolve Issue 160 with
the proposal contained in the minutes above.

Ashok seconds

Motion accepted unanimously

Issue 160 is resolved

BINDINGS-161: BWS50015's target is a
WSDL 1.1. document, is that appropriate? 

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

Anish explains the issue.

Noted that Mike Edwards expanded the
scope to address BWS 50014 & BWS 50015

Anish moves to open Issue 161

Ashok seconds

Motion passes unanimously

Issue 161 is open

Proposal from Mike:  http://lists.oasis-open.org/archives/sca-bindings/201105/msg00015.html

Replace the normative statements [BWS50014]
and [BWS50015] with the following text: 

"It is good practice for Policies
and Assertions to be signed to prevent tampering.  It is acceptable
for 

an SCA runtime to reject a Policy that
is not signed or where there is no associated security token 

which indicates that the signer has
appropriate claims for the policy."

Ashok moves to resolve Issue 161 with
the proposal contained in the minutes above.

Martin seconds

Motion accepted unanimously

Issue 161 is resolved.

Item 5 Open Issues

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

BWS20027 is tested in the POJO tests

Status: Proposed resolution pending
AI 20110421-01

anish: Bryan's proposal: https://www.oasis-open.org/apps/org/workgroup/sca-bindings/download.php/41936/sca-wsbinding-1.1-testcases-csd01-rev1%20Issue152.odt

anish: https://www.oasis-open.org/apps/org/workgroup/sca-bindings/download.php/41938/sca-wsbinding-1.1-testcases-csd01-rev1%20Issue152.pdf

AI outcome is here: http://lists.oasis-open.org/archives/sca-bindings/201105/msg00013.html

Changes are in documentation of the
TA.

Anish moves to resolve Issue 152 with
the proposal contained in https://www.oasis-open.org/apps/org/workgroup/sca-bindings/download.php/41938/sca-wsbinding-1.1-testcases-csd01-rev1%20Issue152.pdf

Ashok seconds

Motion passes unanimously

Issue 152 is resolved

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: Proposed resolution in JIRA

Anish describes the proposal

MartinC : Should should be treated as
a must ala rfc2119

MartinC : its a must unless you have
very good reasons not to support

AOB

Bryan Aupperle request for LOA for May
19

- no objections, LOA granted

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