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: Today's minutes

Raw  minutes for today's call.

Bryan Aupperle, Ph.D.
STSM, WebSphere Enterprise Platform Software Solution Architect

Research Triangle Park,  NC
+1 919-254-7508 (T/L 444-7508)
Internet Address: aupperle@us.ibm.com
[11:57] Simon Holdsworth: Audio conference: 

Meeting Number: * 913929 * (press * before and after the digits) 

Phone numbers: 

Austria = Vienna 026822056419 
Belgium = Brussels 022901709 
China Toll Free = China North 108007121722, China South 108001201722 
Denmark = Copenhagen 32714982 
France = Paris 0170994364, Lyon 0426840196, Marseilles 0488915310 
Germany = Berlin 030726167296, Frankfurt 069710445413, Hamburg 040809020620, Munich 089244432767, Stuttgart 0711490813212, Dusseldorf 021154073845 
India Toll Free = 0008001006703 
Ireland = Dublin 014367612 
Italy = Milan 0230413007, Rome 06452108288, Turin 01121792100 
Japan = Tokyo 0357675037 
Netherlands = Amsterdam 0207965349 
Portugal = Lisbon 211200415 
Russia Toll Free = 81080022074011 
Spain = Barcelona: 934923140, Madrid: 917889793 
Sweden = Stockholm 0850520404 
Switzerland = Geneva 0225927186 
UK Toll Free = 08003581667 
UK Toll = London 02071542988, Manchester 01612500379, Birmingham 01212604587 
USA Toll Free = 18665289390 
USA Toll = 19543344789
[11:57] Simon Holdsworth: Agenda
[11:57] Simon Holdsworth: 1. Opening 

Roll call 
Scribe assignment 

Top 10 on the scribe list: 
Tom Rutt Fujitsu Limited 
Jeff Mischkinsky Oracle Corporation 
Plamen Pavlov SAP AG 
Bryan Aupperle IBM 
Martin Chapman Oracle Corporation 
Eric Johnson TIBCO Software Inc. 
Piotr Przybylski IBM 
Simon Nash Individual 
Anish Karmarkar Oracle Corporation 
Ashok Malhotra Oracle Corporation 

Agenda bashing 

2. Approval of the minutes from 9th April 


3. Actions 

20090211-4 [General] Write up HTTP binding use cases 
20090311-2 [Editors] Update specs for new assembly namespace 
20090312-1 [Editors] Update schemas in specs as per http://lists.oasis-open.org/archives/sca-bindings/200903/msg00057.html 
20090409-1 [Anish Karmarkar] Produce a revised proposal for BINDINGS-25 based on comments from April 9 telecon 

4. New Issues 

Please note, as per resolution on 9th October 2008, new issues received on the mailing list after Noon GMT 1st November can only be opened using the same voting rules as re-opening a closed issue (2/3 majority of a full TC vote) 

no new issues 

5. Open Issue Summary/Schedule 

Discuss ownership/deferral of issues. 

Current schedule: 

Must have issues resolved by April 16th 
Public review draft available for TC comments April 23rd 
Public review draft vote April 30th 
Test assertions complete one month beyond PRD, test cases one month after that. 

Issues with proposed resolutions: 5 
Issues with identified owner, no resolution: 0 
Issues with no identified owner: 0 

Survey outlook for issues with no proposed resolution (marked with * in this list) 

Simon Holdsworth: 48 (pri 3) 
Anish Karmarkar: 2 (pri 2), 25 (pri 1) 
Eric Johnson: 54 (pri 1) 
Simon Nash: 23 (pri 1) 

6. Conformance statement numbering 

Discuss/agree on the updates to the specs for issues 61, 62, 63. 




7. Open Issue Discussion 

@wsdlElement definition needs clarification on "equivalent" and use of WSDL 2.0 constructs 
Raiser: Eric Johnson, owner: Simon Nash 
Priority: 1 
Status: Proposed resolution: http://lists.oasis-open.org/archives/sca-bindings/200904/msg00000.html 

Is it required that every implementation of binding.ws support the soap intent? 
Raiser: Anish Karmarkar, owner: Anish Karmarkar 
Priority: 1 
Status: Proposed resolution in email http://lists.oasis-open.org/archives/sca-bindings/200904/msg00041.html 

Endpoint URI algorithm is unclear 
Raiser: Eric Johnson, owner: Eric Johnson 
Priority: 1 
Status: Proposed resolution: http://lists.oasis-open.org/archives/sca-bindings/200903/msg00104.html 
Latest email: http://lists.oasis-open.org/archives/sca-bindings/200903/msg00107.html 

How should SCA callback semantics be carried over Web Services? 
Raiser: Simon Nash, owner: Anish Karmarkar 
Priority: 2 
Status: Proposed resolution: http://lists.oasis-open.org/archives/sca-bindings/200904/msg00012.html 
Latest email: http://lists.oasis-open.org/archives/sca-bindings/200904/msg00038.html 

How are mayProvide intents on bindings satisfied 
Raiser: Ashok Malhotra, owner: Simon Holdsworth 
Priority: 3 
Status: Proposed resolution: http://lists.oasis-open.org/archives/sca-bindings/200903/msg00005.html 
Latest email: http://lists.oasis-open.org/archives/sca-bindings/200903/msg00059.html 

7. AOB
[11:59] anish simonH, I'll be about 5-10 mins late for the call
[12:03] Bryan Aupperle: Scribe: Bryan
[12:03] Martin C: phew
[12:03] Bryan Aupperle: Topic: Approval of 9 April minutes
[12:03] Bryan Aupperle: No objections, minutes approved
[12:03] Bryan Aupperle: Topic: Action Items
[12:04] Bryan Aupperle: 20090211-4: No Progress
[12:04] Bryan Aupperle: 20090311-2: No Progress
[12:04] Bryan Aupperle: 20090312-1: No Progress
[12:04] Bryan Aupperle: 20090409-1: Done
[12:05] Bryan Aupperle: Topic: New Issues
[12:05] Bryan Aupperle: No new issues
[12:06] Bryan Aupperle: Topic: Conformance Statement Numbering
[12:06] Bryan Aupperle: http://www.oasis-open.org/committees/download.php/31957/sca-binding-ws-1.1-spec-cd02-issue61.doc 


[12:08] Bryan Aupperle: Mike notes there seem to be relatively few normative statements.
[12:09] Bryan Aupperle: Simon H.  There are some sections with significant changes in progress that will add some normative statements.
[12:09] Bryan Aupperle: Simon N.  Some conformance statements are missing explicit conformance targets.
[12:15] Bryan Aupperle: Eric: My review has not compared the style etc. to what Assembly or Policy has done.  But this cross-linked style seems sufficient with respect to context for the statements in the appendix.
[12:17] Bryan Aupperle: Simon N. suggests that sections 4.2.1 and 4.2.2 have text that should be normative statements.
[12:20] Bryan Aupperle: Mike: Reviews approaches Assembly has done for situations like this.
[12:22] Bryan Aupperle: Mike: This is the time to fix text that is normative but missing RFC 2119 keywords.
[12:27] Bryan Aupperle: Conclusion is that an additional revision of these documents are needed to address concerns raised.
[12:28] Bryan Aupperle: Topic: Issue 25
[12:28] Bryan Aupperle: http://www.osoa.org/jira/browse/BINDINGS-25
[12:28] Bryan Aupperle: Proposed resolution in email http://lists.oasis-open.org/archives/sca-bindings/200904/msg00041.html
[12:34] Bryan Aupperle: Anish reviews proposal
[12:34] Bryan Aupperle: Simon N. Do we need document conformance clauses?
[12:36] Bryan Aupperle: Discussion about the style of these types of statements in Assembly.
[12:36] Mike Edwards: From the Assembly spec:
[12:36] Mike Edwards: SCA Composite Document: 
An SCA Composite Document is a file that MUST have an SCA <composite/> element as its root element and MUST conform to the sca-core-1.1.xsd schema and MUST comply with the additional constraints on the document contents as defined in Appendix C.
[12:40] anish: replace: The <binding.ws> element MUST be valid according to its XML Schema.
with: An SCA Composite Document (as defined by assembly section xxx) that has the <bidning.ws> element MUST be valid according to the XML Schema yyy.
with: An SCA Component Type Document (as defined by assembly section xxx) that has the <bidning.ws> element MUST be valid according to the XML Schema yyy.
[12:46] Bryan Aupperle: Mike: remove "optional" from line 114
[12:49] Bryan Aupperle: Eric: we need to be careful about not repeating information in lines 114-116 that is normatively stated elsewhere (either in this spec or in other specs.).
[12:49] Bryan Aupperle: Anish: this is somewhat intertwined with issue 54.
[12:50] Bryan Aupperle: Mike: We also do not need statements that duplicate what is defined in schemas.
[12:56] Bryan Aupperle: Simon N.  Assembly is not clear if @name, @requires, and @policySets must be supported by every binding.
[12:57] Bryan Aupperle: Simon N. So we should be explicit in this spec.
[12:58] Bryan Aupperle: Topic: AOB

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