Minutes
Opening
Roll - quorate with 22 of 33 voting members and four observers
Resolution: minutes of 2008-05-06 approved w/o
Action Items
Action: id=2008-04-01-1 status=pending Dave Booz to write up the OSGI approach to artifact resolution (Issue 8)
It was noted that Dave has an outstanding action item to write up something for issue 16
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-05-06-1 status=pending Booz/Karmarkar to write up a more detailed proposal for Assembly-37
Action: id=2008-05-06-2 status=done Nash to diddle some scdl wrt Assembly-37
Existing Issues
Assembly-16
Assembly-8 SCDL artifact resolution underspecified
Nash summarizes his proposal
<Mike Edwards>
Anish wrote a later response email here:
A frank exchange of contrasting views ensues
<anish>
i think we should allow them, but ignore them. Properties are a slightly different matter
<anish>
the difference between composite service/references and composite properties is that property values do flow downwards whereas
service/reference config flows only up
<Sanjay>
think a simpler model would be to provide visibility to service/references of deployed composites only.
<anish>
sanjay, visibility to whom?
<anish>
so if something is visible at the domain-level, is that for other components at the domain-level or outside the domain?
<anish>
i don't see a problem with what simon just read
<Sanjay>
I really don't understand why you need to create a wrapper composite for deploying a composite
anish simon, what is the line number again?
<Mike Edwards>
951 in WD03
<anish>
Composites may form component implementations in higher-level composites in other words the higher-level composites can have
components that are implemented by composites. For more detail on the use of composites as component implementations see the
section Using Composites as Component Implementations.
The content of a composite may be used within another composite through inclusion. When a composite is included by another
composite, all of its contents are made available for use within the including composite the contents are fully visible and
can be referenced by other elements within the including composite. For more detail on the inclusion of one composite into
another see the section Using Composites through Inclusion.
Martin C sometimes does make sense
<anish>
we made a decision some time back that things that go on at a higher-level (because of promotion) does not affect anything
at the lower-level (for services and references)
Action: Sanjay/Nash to prepare a counter proposal for assembly-37
reconfirming the action 2008-05-06-1 meaning that Booz/Karmarkar will develop some words on what he would change in the spec
relative to Assembly-37
<Mike Edwards>
There is a proposal in the JIRA
Rowley discusses his proposal contained in the JIRA
<anish>
i'm not sure what i'm agreeing with either, would like some time to digest this
<anish>
how do i figure out where (which contribution) a particular Qname is defined
<anish>
so that i can do an update
<anish>
do i have to go through all the contributions and go thru each definitions.xml of each contribution?
<Mike Edwards>
All of these artifacts within an SCA Domain are defined in SCA contributions in files called META-INF/definitions.xml (relative
to the contribution base URI). Although the definitions are specified within a single SCA contribution, the definitions are
visible throughout the domain. Because of this, all of the QNames for these definitions MUST be unique within the domain.
<Mike Edwards>
....those are the words in the JIRA
<anish>
i would like to think about the consequences of this a little more
Motion: m:Rowley s:Patil Assembly-44 resolved with the proposal contained in the JIRA entry
Amendment: m:Karmarkar s:Malhotra Accept the proposal in JIRA but leave the issue open in JIRA
Motion to call the question on the amendment
<Sanjay>
point of order - chair should have first taken a vote for 'calling the question'
Motion: Postpone consideration m:karmarkar s:Chapman
Resolution: Motion to postpone consideration Assembly-44 resolution w/o
Action: Rowley to develop refined text for the Assembly-44 proposal contained in the JIRA.
Conclusion of the AI by Rowley is that the offending sentence is described in the issue description in JIRA and that the proposal
contained in JIRA is intended to replace that sentence
Rowley describes his proposal which is contained in JIRA
<Bryan Aupperle>
This brings up some of the same audit related concerns we talked about on another issue last week.
Further consideration postponed due to press of time.
<Bryan Aupperle>
We may need to allow a given domain to prohibit overrides.
AOB
Schreiber diagnostics output
[Delete this section before publishing the minutes]
statistics: Schreiber found 140 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-01-1'
citation-detection-irc1: Line 23: Check for possible unrecognized nick '2008-04-28-1'
citation-detection-irc1: Line 25: Check for possible unrecognized nick '2008-05-06-1'
citation-detection-irc1: Line 27: Check for possible unrecognized nick '2008-05-06-2'
citation-detection-irc1: Line 37: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 40: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 41: Check for possible unrecognized nick 'http'
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 48: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 49: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 52: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 57: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 62: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 67: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 70: Check for possible unrecognized nick 'http'
system: Transformer: SAXON 8.9
[End of Schreiber diagnostic output]