Minutes
Opening
Roll - quorate with 20 of 30 voting members
<Mike Edwards>
Agenda Bashing:
<Mike Edwards>
Add Discussion of Problems with Issues found by Editors
Agenda - addition of f2f logistics and problems with resolved issues found by editors
<Mike Edwards>
Add F2F Logistics Discussion
Resolution: minutes of 2008-06-24 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 Test sub cttee produce test assertions and test artifacts and test harness
Action: id=2008-06-03-7 status=done ref Assembly-16 Edwards to look into the question of aliases
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=pending 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=pending Mike Edwards - Question of handling changes of property values (including multi-values) -
should be part of the discussion of Issue 41
Action: id=2008-06-03-13 status=done Nash/Edwards prepare proposal text for Assembly-56
Action: id=2008-06-17-1 status=done Bryan Aupperle to develop a re-worked proposal for the resolution of Assembly-53 based on the
discussions of 2008-06-17
Problems that Editors found with resolved issues
Karmarkar:
Editors applied pending issues to CD-01 to create CD-01 rev 1
... Issues list and spec needs to be updated to reflect the incorporation of all issues including issue 69
... Some of the issues could not be resolved to the resolved state since some could not be applied and others were unclear
Issue 1 a incorporated, b dropped
Issue 14 changes seem to only apply to component properties. applied changes to component and not composite properties and
component type properties
Issue 17 JIRA says resolved but no minute is referenced
Issue 18 Has a dependency on Issue 12, 12 is closed but it never was applied to the spec
Issue 22 seems to be a duplicate of 35, 35 is closed but there is no resolution pointed to by JIRA
Issue 30 FYI - was not incorporated since we are waiting for the policy attachment resolution
Issue 45 FUI - Partially applied
Chairs thank Editors for their update
F2F Logistics - Sept 30-Oct 3 in Boston
<Mike Edwards>
Bob needs to know the number of attendees asap
<Mike Edwards>
We are also hoping to have a Wednesday night event such as a Boston Harbor dinner cruise
<Mike Edwards>
end of July for the end of the ballot
New Issues
Chapman takes the chair role
Edwards describes his new issue
Resolution: m:Edwards s:Combellack New Issue Assembly-70 opened w/o
Aupperle describes his new issue
Resolution: m:Aupperle s:Mischkinsky New Issue Assembly-71 opened w/o
Existing Issues
<Mike Edwards>
Proposed text for the Assembly specification (CD-01), to be added after line 2333
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. A single invocation of an operation on the service interface can cause
zero, one or many invocations of any of the operations on the callback interface. For a given invocation of a service operation,
which operations are invoked on the callback interface, 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.
<Simon Nash>
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.
A single invocation of an operation on the service interface can cause
zero, one or many invocations of any of the operations on the callback interface
<scn>, and a single invocation of an operation on the callback interface can result from
one or many invocations of any of the operations on the service interface</scn>.
For a given invocation of a service operation,
which operations are invoked on the callback interface, 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.
<Martin C>
For a given invocation of a service operation,
which operations are invoked on the callback interface, the number of operations invoked, how they are correlated, and their
sequence are not described
by SCA.
Motion: m:Nash s:Edwards 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.
A single invocation of an operation on the service interface can cause
zero, one or many invocations of any of the operations on the callback interface , and a single invocation of an operation
on the callback interface can result from
one or many invocations of any of the operations on the service interface.
For a given invocation of a service operation,
which operations are invoked on the callback interface, the number of operations invoked, how they are correlated, 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.
Consideration deferred due to press of time
AOB
Schreiber diagnostics output
[Delete this section before publishing the minutes]
statistics: Schreiber found 162 input lines
edits: Schreiber found no text-edit commands
command-scribe: Line 7: Bob Freund recognized
command-scribe: Schreiber detected that this section was scribed online
citation-detection-irc1: Line 17: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 19: Check for possible unrecognized nick '3. Action Items'
citation-detection-irc1: Line 21: Check for possible unrecognized nick '2008-04-28-1'
citation-detection-irc1: Line 23: Check for possible unrecognized nick '2008-06-03-3'
citation-detection-irc1: Line 25: Check for possible unrecognized nick '2008-06-03-4'
citation-detection-irc1: Line 27: Check for possible unrecognized nick '2008-06-03-6'
citation-detection-irc1: Line 29: Check for possible unrecognized nick '2008-06-03-7'
citation-detection-irc1: Line 31: Check for possible unrecognized nick '2008-06-03-8'
citation-detection-irc1: Line 33: 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 37: Check for possible unrecognized nick '2008-06-03-13'
citation-detection-irc1: Line 39: Check for possible unrecognized nick '2008-06-17-1'
citation-detection-irc1: Line 44: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 47: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 53: 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 67: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 72: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 77: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 83: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 88: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 213: Check for possible unrecognized nick 'http'
system: Transformer: SAXON 8.9
[End of Schreiber diagnostic output]