Minutes
opening
Roll - quorate 18 of 25 voting members
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
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
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
<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
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]