Minutes
Opening
Resolution: minutes of 2011-01-11 approved w/o
Action Items
Action: id=2010-09-22-8 status=pending owner="EricJ" produce new proposal for ASSEMBLY-227
Action: id=2011-01-04-1 status=pending Johnson in absentia to create a proposal for the resolution of Assembly-239
Action: id=2011-01-04-2 status=pending Edwards to write a new proposal for the resolution of Assembly-246 along the lines contained
in wsra
Action: id=2011-01-11-1 status=done Edwards to examine drafts in consideration of referencing specific versions in those cases where
the references are normative and propose modifications accordingly
<MartinC>
robin is temp tc-admin
<MartinC>
until they recruit a new one
Administrivia
Edwards:
We are looking for a new issues editor, shall we seek a new volunteer?
<beeps are heard as folks hang up>
everyone but Edwards and Chapman takes a step back
Vote to make new Working Draft of the Assembly V1.1 spec the next CSD (CSD07)
Edwards:
Are there any questions and are folks ready to vote?
Chapman:
Be sure that this is right as a change will require an another public review
Motion: m:Aupperle s:Jordan Approve WD 63 as CSD07 and put it out for a 15 day public review
Resolution: m:Aupperle s:Jordan Approve WD 63 as CSD07 and put it out for a 15 day public review w/o
Action: Edwards to take the appropriate steps with TC-Admin to accomplish the progression and review of CSD07
Issues against v1.2
<anish>
eric, wondering if what you are looking for is a default composite-level channel (similar to the one that exists at the global
level) -- such a default channel doesn't have to be configured by the assembler?
<Mike Edwards>
I don't understand the use of the term "scope" here
<MartinC>
to me its all about visibility of channels - if yiou can see it you can use it - thats the only scoping we have
<anish>
that was my point in the presentation too -- the implementation gets to decide how the mapping to JMS topics takes place.
The concept in SCA is abstract enuf to enable both cases
<Peter Niblett>
I think the idea of a default composite level channel is what they are asking for.. though there's then the question of whether
you can elect not to have a default for a particular composite and instead have the default propagate up to the next level
higher.. I have been wondering whether that would help with 227
<Mike Edwards>
Channels are *all* about connecting some group of producers to some group of consumers
<Mike Edwards>
if you have different groups then you need multiple channels
<anish>
peter, this make it complicated. such propagation/promotion was what we were trying to avoid.
<Mike Edwards>
if you want to limit the set of producers/consumers that can be connected, then don't put the channel at the Domain level
<Mike Edwards>
and you end up with a "subsystem" channel which would be entirely contained in some nested composite
<anish>
i think there may be a philosophical difference here -- I look at this as the assembler's job to figure out who is connected
to whom -- this is critical. I don't think Eric/Tibco has that view.
<Mike Edwards>
+1 Anish - that does seem to be the case
<Mike Edwards>
Assembly - composition - is all about deciding what pieces there are and how they are connected
<anish>
my view is that unlike an interface contract in the service-ref world, eventing part is not conducive to 'autowire' -- you
have to intentionally say who is connected to whom
next I suppose we will need to discuss channel credentials?
<Mike Edwards>
and while many systems may use Channels at the Domain level, there will be the need for Channels that belong to subsystems
and cannot be used by components outside the subsystem (ie Composite level Channels)
<MartinC>
i accept there is a bottom up design problem of not knowing about "local" channels in outer composites, i thought 227 and/or
the concept of a virtual channel that can be bound later might solve this
<anish>
i dont' see how a prosumer/label would change this issue
<Mike Edwards>
I believe that consumer promotion addresses Danny's composition question
<anish>
late binding requires promotion of producers/consumers/prosumers, me thinks
<Mike Edwards>
(& producer promotion)
<MartinC>
propotion of a virtual channel reference
<Mike Edwards>
- promotion is all about enabling the assembler of a composite to decide what can be done by the "user" of the composite
<anish>
or even promotion ;-)
<anish>
no motion on the table, so no filibuster
<Mike Edwards>
"NA Sales" vs "EMEA Sales" may be a good example of 2 channels that actually could handle the SAME event types and might require
STRUCTURAL organization to distinguish
<Mike Edwards>
Eric J: Global Channels seem to have a radically different role to that of Composite level channels
Action: Johnson to propose more concretely what the different roles of global vs local channels might be
AOB
Schreiber diagnostics output
[Delete this section before publishing the minutes]
final validation: Date not specified, the date '2011-01-18' 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 65 input lines
edits: Schreiber found the following text-edit commands:
edits: Line 3: s/1./agenda: 1.
edits: Line 27: s/take/takes
edits: Line 31: s/WG/WD
edits: Line 83: s/channels/channels might be
edits: Line 84: s/rolls/roles/
edit-substitute: command on line 3 succeeded, changed line 1 from '1.' to 'agenda: 1.'
command-scribe: Line 2: Bob Freund is recognized
command-scribe: Line 2: Bob Freund's nick Bob has been selected
edit-delete: Line 3 was deleted
edit-substitute: command on line 27 succeeded, changed line 25 from 'take' to 'takes'
edit-delete: Line 27 was deleted
edit-substitute: command on line 31 succeeded, changed line 30 from 'WG' to 'WD'
edit-delete: Line 31 was deleted
edit-substitute: command on line 83 succeeded, changed line 82 from 'channels' to 'channels might be'
edit-substitute: command on line 84 succeeded, changed line 82 from 'rolls' to 'roles'
edit-delete: Line 83 was deleted
edit-delete: Line 84 was deleted
command-autoroll/oasis: Line 89: Attempting to fetch roll from http://www.oasis-open.org/apps/org/workgroup/sca-assembly/event.php?event_id=28491
command-autoroll/oasis: Line 89: Successfully fetched roll from http://www.oasis-open.org/apps/org/workgroup/sca-assembly/event.php?event_id=28491
system: Transformer: SAXON 9.2.1.2
[End of Schreiber diagnostic output]