Minutes
Introduction
Resolution: Minutes of 27-Jul-09 approved w/o
Action items
None - Mike E asks for volunteers to take on open issues
Test Assertions and TestCases
Public Review draft has been voted and sent to TC Administration for external posting.
TC Administration.require RDDL files for new namespaces
AnishK:
Will look at updating the RDDL files
MikeE:
There are some new issues against Test Suite but didn't make todays agenda
Existing Issues
<Mike Edwards>
Message with proposal:
ASSEMBLY 136: Promoting a reference with multiplicity 1..n and targets should default to 0..n
MikeE:
Describes latest proposal (linked above).
SimonN:
Propsal is quite different from previous proposal
...Questions on promotion of multiplicity
MikeE:
Covered in later sections
MikeE:
Continues reviewing changes
Tables describing the valid multiplicity combinations have been added
SimonN:
No details for defaults
...tables only seem to describe explicit values - nothing to say what happens if none specified
...we should explicitly describe defaults
MikeE:
Deliberately left these out as it makes the table too complex
<anish>
What we have and changes Mike/Simon are making are reasonable within the issue context, but taken overall this is getting
to be over-engineered: override, promotion, defaults, cardinality, changes in cardinality as things are promoted/wired, wired-by-impl
etc
SimonN:
Wording should be much more complex and at present rules for defaults and explicit are different
...these rules should be the same
AnishK:
This whole thing is getting to be too complicated
Additional issue(s) for wiredByImpl
Motion: Resolve ASSEMBLY-136 with proposal in E-mail m=MikeE s=NONE
Motion fails due to lack of second
SimonN:
Would like to add words to cover situations he's concerned with (defaults)
...Can't do this on-the-fly
Action: owner=SimonN Add wording to describe defaults for multiplicity promotion to ASSEMBLY-136 proposal
ASSEMBLY-80 Create an Event Processing Model for SCA
AnishK:
Should not block progress but appreciates concerns over delay etc.
...A parallel call would be a good place to address ASSEMBLY-80
ScottV:
Not sure that members will be able to find time for ANOTHER call
...would HAVE to be an official call so problems with quorum and/or voting status
JeffE:
Seems to be more EDA than SOA which is good but perhaps too big to do at present.
MartinC:
Charter isn't specific on this and would need official clarification if members dissagree.
MartinC:
Doesn't necessarily need to be full TC could be a subcommittee - Testing worked OK that way
<Martin C>
i think it shou8ld be treated like a sc
MarkC:
Fall-out that impacts other TC's - Java-TC already has two calls per week.
<Martin C>
sub-committees only make recoemmendations to the main tc, attendencs does not affect voting status
AnishK:
Issue is valid and we should address this - parallel calls seems best way.
Motion: The TC should hold parallel calls to address ASSEMBLY-80 (only) m=AnishK s=Khanderao
SimonN:
amends to make these parallel calls a Sub-committee call.
Motion: Additional calls should be Sub-Committee calls m=SimonN s=DannyvR
JeffM:
Sub-committee's have no authority - main TC could reject all work done by SC
MartinC:
Testing was done by SC and that worked OK
SimonN:
Doesn't address resource issues though
<Martin C>
why was SAP's name on the contribution?
Sanjay:
Agrees that this is getting into EDA and we should concentrate on SOA and get that published
<Martin C>
why was tibcos name on the contribution....
EricW:
We should have a few calls to determine EXACTLY how much work is required.
Danny:
Have looked at this and there's a lot we dissagree with and it will take a lot of work to resolve
<Scott Vorthmann>
I was a participant in the eventing calls for some time, but was not participating for the last year or more
GilbertP:
Questions on how SC would work - separate issues or a single issue/document
<Scott Vorthmann>
it did not occur to me to review the to-be-published document, with an eye to removing my name
Sanjay:
Seems that Charter is being used to force issue
JeffM:
Takes exception to that - submission was made in just same way as original OSOA spec.
AOB
Straggler role - Sanjay, Gil, Jeff
No issues opened or resolved
Schreiber diagnostics output
[Delete this section before publishing the minutes]
final validation: Date not specified, the date '2009-08-04' was assumed
final validation: Title not specified, default title 'OASIS SCA-Assembly TC...' was assumed
final validation: Chair not specified, default chair was assumed
statistics: Schreiber found 78 input lines
edits: Schreiber found no text-edit commands
command-scribe: Line 2: Since the line number is less than or equal to 20 we will interpret this as a scribename command,
note that the scribe command is deprecated
command-scribe: Line 2: Scribe 'Eric Wells' is recognized by use of the nick 'EricW'
command-scribe: Line 2: EricW's nick 'EricW' has been selected
command-autoroll/oasis: Line 115: Attempting to fetch roll from http://www.oasis-open.org/apps/org/workgroup/sca-assembly/event.php?event_id=16103
command-autoroll/oasis: Line 115: Successfully fetched roll from http://www.oasis-open.org/apps/org/workgroup/sca-assembly/event.php?event_id=16103
citation-detection-scribed: Line 116: Check for possible unrecognized nick 'COB 9'
system: Transformer: SAXON 9.1.0.7
[End of Schreiber diagnostic output]