← Prev in month
← Prev in thread
Next in thread →
Next in month →
Draft Minutes of 2008-07-08 are attached
Title: SCA-Assy - 2008-07-08
Hide IRC
- DRAFT -
SCA-Assembly TC
Teleconference
08 JUL 2008
Attendees
Present
fred carter, (AmberPoint)
Mark Combellack, (Avaya, Inc.)
Dale Moberg, (Axway Software*)
Tom Rutt, (Fujitsu Limited*)
Robert Freund, (Hitachi, Ltd.)
Eric Wells, (Hitachi, Ltd.)
Bryan Aupperle, (IBM)
David Booz, (IBM)
Mike Edwards, (IBM)
Simon Holdsworth, (IBM)
Dieter Koenig, (IBM)
Simon Moser, (IBM)
Simon Nash, (IBM)
Jim Marino, (Individual)
Peter Furniss, (Iris Financial Solutions Ltd.)
Jeff Estefan, (Jet Propulsion Laboratory:*)
Martin Chapman, (Oracle Corporation)
David DiFranco, (Oracle Corporation)
Khanderao Kand, (Oracle Corporation)
Anish Karmarkar, (Oracle Corporation)
Rich Levinson, (Oracle Corporation)
Ashok Malhotra, (Oracle Corporation)
Jeff Mischkinsky, (Oracle Corporation)
Gilbert Pilz, (Oracle Corporation)
Plamen Pavlov, (SAP AG*)
Chairs
Martin Chapman
Mike Edwards
Scribe
Bob Freund
Agenda:
1. Opening
Introductions
Roll call
Scribe confirmation
Agenda bashing
2. Approval of minutes of SCA-Assembly TC meeting of 1st July
http://www.oasis-open.org/apps/org/workgroup/sca-assembly/download.php/28712/SCA%20Assembly%20minutes%202008-07-01.html
3. Action Items:
2008-04-28-1: Editors to address the editorial comments contained in Combellack's comments at http://lists.oasis-open.org/archives/sca-assembly/200804/msg00089.html
2008-06-03-3: Simon Nash and Anish Karmarkar to develop a more concrete proposal for Issue 37 along the lines of the F2F discussion
so that profitable discussion may continue this meeting.
2008-06-03-4: Chapman to propose some non-normative clarification test to resolve Issue-26 due=2008-12-24
2008-06-03-6: Test sub cttee produce test assertions and test artifacts and test harness
2008-06-03-8: ref Assembly-16 Nash to look into how binding uris may be handled
2008-06-03-9: Mike Edwards to prepare a proposal for addressing Assembly-8 based on some of the discussions at the F2F
DONE (actually done by Dave Booz)
2008-06-03-11: Mike Edwards - Question of handling changes of property values (including multi-values) - should be part of
the discussion of Issue 41
DONE
3. Meeting Logistics
Due to F2F meetings for Bindings & Java next week, propose cancelling the Assembly TC call of July 15th
5. New Issues
ASSEMBLY-72 Do we need appendix A (pseudo-schema)?
http://www.osoa.org/jira/browse/ASSEMBLY-72
If we decide to Open this issue, there is a simple proposed resolution in this email:
http://lists.oasis-open.org/archives/sca-assembly/200807/msg00026.html
6. Existing Issues
Assembly-56 Need to clarify definition of Bidirectional Interfaces
http://www.osoa.org/jira/browse/ASSEMBLY-56
Previous emails:
http://lists.oasis-open.org/archives/sca-assembly/200807/msg00007.html
http://lists.oasis-open.org/archives/sca-assembly/200807/msg00009.html
ASSEMBLY-53 Contribution Extension Model
http://www.osoa.org/jira/browse/ASSEMBLY-53
Updated proposal is contained in this email
http://lists.oasis-open.org/archives/sca-assembly/200806/msg00043.html
http://lists.oasis-open.org/archives/sca-assembly/200807/msg00027.html
ASSEMBLY-8 SCDL artifact resolution underspecified
http://www.osoa.org/jira/browse/ASSEMBLY-8
Latest discussion and proposal:
http://lists.oasis-open.org/archives/sca-assembly/200807/msg00021.html
http://lists.oasis-open.org/archives/sca-assembly/200807/msg00027.html
ASSEMBLY-41 Conflicting domain-level deployments
http://www.osoa.org/jira/browse/ASSEMBLY-41
Proposed update to the Issue:
http://lists.oasis-open.org/archives/sca-assembly/200807/msg00029.html
Requires a writeup based on discussions at the F2F
ASSEMBLY-37 Need to clarify contents of an SCA Domain virtual composite
http://www.osoa.org/jira/browse/ASSEMBLY-37
Waiting for a write-up based on discussions at the F2F meeting
ASSEMBLY-16 Component URI is not well described
http://www.osoa.org/jira/browse/ASSEMBLY-16
Proposal requires write-up of 2 separate action items from the F2F
1)
http://lists.oasis-open.org/archives/sca-assembly/200807/msg00020.html
ASSEMBLY-33 Long-Running Request-Response Operations
http://www.osoa.org/jira/browse/ASSEMBLY-33
Waiting on a write up based on the discussions at the F2F
8. AOB
Contents
Topics
[1]
opening
[2]
Action Items
[3]
Meeting Logistics
[4]
New Issues
[5]
New Issue ASSEMBLY-72 Do we need appendix A (pseudo-schema)? http://www.osoa.org/jira/browse/ASSEMBLY-72
[6]
Existing Issues
[7]
Assembly-56 Need to clarify definition of Bidirectional Interfaces http://www.osoa.org/jira/browse/ASSEMBLY-56
[8]
AOB
Table of Resolutions
Table of Action Items
Action Items
Old:
2008-04-28-1: id=2008-04-28-1 status=pending Editors to address the editorial comments contained in Combellack's comments at http://lists.oasis-open.org/archives/sca-assembly/200804/msg00089.html
2008-06-03-3: id=2008-06-03-3 status=pending Simon Nash and Anish Karmarkar to develop a more concrete proposal for Issue 37 along the lines
of the F2F discussion so that profitable discussion may continue this meeting.
2008-06-03-4: id=2008-06-03-4 status=pending Chapman to propose some non-normative clarification test to resolve Issue-26 due=2008-12-24
2008-06-03-6: id=2008-06-03-6 status=pending owner=Edwards Test sub cttee produce test assertions and test artifacts and test harness
2008-06-03-8: id=2008-06-03-8 status=pending ref Assembly-16 Nash to look into how binding uris may be handled
2008-06-03-9: id=2008-06-03-9 status=done (by Dave Booz) Mike Edwards to prepare a proposal for addressing Assembly-8 based on some of the
discussions at the F2F
2008-06-03-11: id=2008-06-03-11 status=done Mike Edwards - Question of handling changes of property values (including multi-values) - should
be part of the discussion of Issue 41
New:
2008-07-08-1: owner=Nash Review spec for areas that might benefit from illustration by the addition of pseudo-schema
Resolutions
2008-07-08-1: Minutes of 2008-07-01 approved w/o
2008-07-08-2: m:Chapman s:Aupperle New Issue Assembly-72 opened w/o
2008-07-08-3: m:Freund s:Malhotra Resolve Assembly-72 by removing the pseudo-schema Appendix A w/o
2008-07-08-4: motion [56] passes 9-Aye 4-Nay 4-Present
Minutes
Scribe: Bob Freund
opening
Roll - quorate 18 of 25 voting members
Walker is on LOA
Agenda - agreed
Resolution: Minutes of 2008-07-01 approved w/o
Action Items
Action: id=2008-04-28-1 status=pending Editors to address the editorial comments contained in Combellack's comments at http://lists.oasis-open.org/archives/sca-assembly/200804/msg00089.html
Action: id=2008-06-03-3 status=pending Simon Nash and Anish Karmarkar to develop a more concrete proposal for Issue 37 along the lines
of the F2F discussion so that profitable discussion may continue this meeting.
Action: id=2008-06-03-4 status=pending Chapman to propose some non-normative clarification test to resolve Issue-26 due=2008-12-24
Action: id=2008-06-03-6 status=pending owner=Edwards Test sub cttee produce test assertions and test artifacts and test harness
Action: id=2008-06-03-8 status=pending ref Assembly-16 Nash to look into how binding uris may be handled
Action: id=2008-06-03-9 status=done (by Dave Booz) Mike Edwards to prepare a proposal for addressing Assembly-8 based on some of the
discussions at the F2F
Action: id=2008-06-03-11 status=done Mike Edwards - Question of handling changes of property values (including multi-values) - should
be part of the discussion of Issue 41
Meeting Logistics
Meeting of 2008-07-15 are canceled due to overlap with f2f meetings with Java and Bindings
New Issues
New Issue ASSEMBLY-72 Do we need appendix A (pseudo-schema)? http://www.osoa.org/jira/browse/ASSEMBLY-72
Chapman represents Karmarkar's new issue
Resolution: m:Chapman s:Aupperle New Issue Assembly-72 opened w/o
<Mike Edwards>
Can you post the motion into the chatroom please?
Motion: m:Freund s:Malhotra Resolve Assembly-72 by removing the pseudo-schema Appendix A
Action: owner=Nash Review spec for areas that might benefit from illustration by the addition of pseudo-schema
Resolution: m:Freund s:Malhotra Resolve Assembly-72 by removing the pseudo-schema Appendix A w/o
Existing Issues
Assembly-56 Need to clarify definition of Bidirectional Interfaces http://www.osoa.org/jira/browse/ASSEMBLY-56
<Mike Edwards>
http://lists.oasis-open.org/archives/sca-assembly/200807/msg00042.html
Motion: [56] m:Nash s: Aupperle Resolve Assembly-56 with the text "In a bidirectional interface, the service interface can have more
than one operation defined, and the callback interface can also have more than one operation defined. SCA runtimes MUST allow
an invocation of any operation on the service interface to be followed by zero, one or many invocations of any of the operations
on the callback interface. These callback operations can be invoked either before or after the operation on the service interface
has returned a response message, if there is one.
For a given invocation of a service operation, which operations are invoked on the callback interface, when these are invoked,
the number of operations invoked, and their sequence are not described by SCA. It is possible that this metadata about the
bidirectional interface can be supplied through mechanisms outside SCA. For example, it might be provided as a written
description attached to the callback interface."
<Gil>
the point is, from the application perspective, control has returned to the application code
<anish>
we have to be careful about saying 'return control'
<anish>
especially in a multithreaded env
<Dave Booz>
These callback operations can be invoked at any time during the exection of a service operation.
<anish>
i think when the runtime is providing support for this (wrt providing callback endpoints, correlation), then what dave says
makes sense. If the correlation and callack EPR is managed by the application then we should have nothing to say about it
<Dave Booz>
+1
<anish>
i think a bi-D interface should be allowed to be specified for both cases above
<Gil>
isn't "unsolicited callback" an oxymoron? what are you calling "back" from if there wasn't an original "call"?
<Martin C>
true but its just an iterface after all and can be invoked
<Dave Booz>
These callback operations can be invoked at any time during the exection of any service operation.
<Dave Booz>
unsolicited callback is a capabilty that used to exist in the specs. The idea was that callback was just a bad name for a
pair of ref/service pairs in opposite directions....we've since constrained this during discussion but there are no words
to reflect those discussions
<anish>
i sent a PO example from WSTF for the 2nd case that I talkd about where the application does the correleation and callback
endpoint mgmt
<Simon Nash>
dave, I think the constraint is that there is nothing in the assembly spec that requires this scenario to work. it isn't
explicitly prohibited.
<Martin C>
is there any amended text to discuss
Resolution: motion [56] passes 9-Aye 4-Nay 4-Present
AOB
Straggler roll
[End of Minutes]
Formatted on 2008-07-08 at 12:28:10 GMT-4
Minutes formatted by Schreiber, a collection of XSLT
stylesheets by Bob Freund modeled after David Booth's scribe
Schreiber diagnostics output[Delete this section before publishing the minutes]
statistics: Schreiber found 137 input lines
edits: Schreiber found the following text-edit commands:
edits: Line 173: bob: s/Makhotra/Malhotra
edits: Line 215: anish: s/send/sent/
command-scribe: Line 7: Bob Freund recognized
command-scribe: Schreiber detected that this section was scribed online
citation-detection-irc1: Line 18: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 20: Check for possible unrecognized nick '3. Action Items'
citation-detection-irc1: Line 22: Check for possible unrecognized nick '2008-04-28-1'
citation-detection-irc1: Line 24: Check for possible unrecognized nick '2008-06-03-3'
citation-detection-irc1: Line 26: Check for possible unrecognized nick '2008-06-03-4'
citation-detection-irc1: Line 28: Check for possible unrecognized nick '2008-06-03-6'
citation-detection-irc1: Line 30: Check for possible unrecognized nick '2008-06-03-8'
citation-detection-irc1: Line 32: Check for possible unrecognized nick '2008-06-03-9'
citation-detection-irc1: Line 35: Check for possible unrecognized nick '2008-06-03-11'
citation-detection-irc1: Line 45: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 48: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 54: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 56: Check for possible unrecognized nick 'Previous emails'
citation-detection-irc1: Line 57: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 58: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 61: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 64: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 65: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 68: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 71: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 72: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 75: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 78: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 82: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 87: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 91: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 95: Check for possible unrecognized nick 'http'
edit-substitute: command on line 173 succeeded, changed line 171 from 'Makhotra' to 'Malhotra'
edit-delete: Line 173 was deleted
edit-substitute: command on line 215 succeeded, changed line 213 from 'send' to 'sent'
edit-delete: Line 215 was deleted
system: Transformer: SAXON 8.9
[End of Schreiber diagnostic output]
← Prev in month
← Prev in thread
Next in thread →
Next in month →