Minutes
Agenda bashing
No additions - agenda accepted
Minutes
Approval of 18-Jul-08 minutes
Resolution: Minutes of 18-Jul-08 accepted 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-8 status=Completed ref Assembly-16 Nash to look into how binding uris may be handled
Action: id=2008-07-08-1 status=Pending Simon Nash - Review spec for areas that might benefit from illustration by the addition of
pseudo-schema
Roll Call
16/24 Members present - Quorate
New Issues
ASSEMBLY-73
Motion: Open Issue 73 m: Martin C s: Bryan A
Resolution: Issue ASSEMBLY-73 opened w/o
Open Issues
ASSEMBLY-53 Contribution Extension Model
Aupperle:
Reviews his proposal
... conflict between this and ASSEMBLY-28
... can Schema experts address this?
ASSEMBLY-28 already in CD document
Action: Aupperle to raise new issue(s) wrt ASSEMBLY-28
Discussion on proposal for ASSEMBLY-53 (in "Contribution.doc")
Resolution: Resolve ASSEMBLY-53 with propsal in E-mail issue=53
ASSEMBLY-8 SCDL artifact resolution underspecified
Proposal attached to above message
<Dave Booz>
navigate to section 6.6
Dave B: Reviews proposed changes
Martin C:
SCA-Runtime must raise an error - what sort of error?
<anish>
i think this error can be raised at deployment. But we should not force it. It must be raised at least before 'runtime'
... if not running how is error sent/received?
Discussion on whether entire contribution should be rejected or just the part that causes error
<anish>
so, there are two things we should say: 'when' and on 'what'
Also (subtle) distinction between deployment or runtime
Wording in final paragraph of section 6.6 needs changing to be more specific
Martin C:
Have talked in the past about abstract lifecycle definition
... if we had this it would make the "When" easier
Action: Edwards to raise an issue regarding definition of lifecycle model
Discussion of "What" and if entire contribution s/b rejected
Simon N: Would be good if we could only reject bad part of contribution
... but only if we can be sure there are no dependencies
<Martin C>
how about: As a result, the SCA runtime MUST reject a deployment composite if an included composite is not found within the
same SCA contribution as the including deployment composite
<Simon Nash>
The SCA runtime must prevent execution of any deployment composite that depends on a composite with any included composite
that is not found within the same SCA contribution
<Simon Nash>
the "depends on" part is needed
Next section of proposal - Section 11.2.1
Anish:
Wording is not clear where WSDL would be resolved
... Example IS clear but wording could be interpreted differently
<anish>
dave, what did you have in mind wrt recursive imports?
<anish>
never mind. u do have words about looking recursively
Long discussion on how these imports work
Overriding local by imports, etc.
(Sorry don't know what happend there)
Mike E: Any other comments on this section?
<Simon Nash>
a imports namespace foo from b / b imports namespace bar from c / a references something in bar / does something come from
a or c?
Anish:
Describes a use case where imports could be ambiguous
Simon N: Clarifies use case discussed earlier
Mike E: There seems to be too many concerns to resolve - continue discussion on E-mail list
Action: Karmarkar to send an E-mail with detials of use case
<anish>
Anish's usecase: three contributions X, Y and Z. Point out the case where a wsdl is imported in X from Y and the wsdl references
a schema that is also available in both Y and Z. In such a case the schema for the wsdl must come from Y and not Z.
Action: Booz to rewrite 11.2.1 to consider Simon N's use case
<bob>
/eric, new ais are auto numbered.
Action: Edwards to start discussion on E-mail regarding Section 6.6
<Simon Nash>
i thought what we wanted to enforce was that if a imports foo from b and b contains something that uses foo.qname, the search
for foo.qname must not go to a
the other case I am concerned about is that a imports foo from b and a contains something that uses foo.qnamei think the search
for foo.qname should go to a
Further discussion on imports - caching, OSGI model
AOB
Schreiber diagnostics output
[Delete this section before publishing the minutes]
final validation: Chair not specified, default chair was assumed
name-value: Line 127: Invalid status 'Completed'
citation-detection-scribed: Line 175: Check for possible unrecognized nick 'Dave B'
citation-detection-scribed: Line 199: Check for possible unrecognized nick 'Simon N'
citation-detection-scribed: Line 211: Check for possible unrecognized nick 'Dave B'
citation-detection-scribed: Line 227: Check for possible unrecognized nick 'Mike E'
citation-detection-scribed: Line 233: Check for possible unrecognized nick 'Simon N'
citation-detection-scribed: Line 235: Check for possible unrecognized nick 'Mike E'
citation-detection-scribed: Line 256: Check for possible unrecognized nick 'Adjourned 8'
statistics: Schreiber found 146 input lines
edits: Schreiber found the following text-edit commands:
edits: Line 173: Bryan Aupperle: s/Close ASSEMBLY-53/Resolve ASSEMBLY-53/
citation-detection-irc1: Line 12: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 14: Check for possible unrecognized nick '3. Action Items'
citation-detection-irc1: Line 16: Check for possible unrecognized nick '2008-04-28-1'
citation-detection-irc1: Line 18: Check for possible unrecognized nick '2008-06-03-3'
citation-detection-irc1: Line 20: Check for possible unrecognized nick '2008-06-03-4'
citation-detection-irc1: Line 22: Check for possible unrecognized nick '2008-06-03-6'
citation-detection-irc1: Line 24: Check for possible unrecognized nick '2008-06-03-8'
citation-detection-irc1: Line 26: Check for possible unrecognized nick '2008-07-08-1'
citation-detection-irc1: Line 32: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 39: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 42: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 43: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 46: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 49: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 50: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 53: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 56: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 60: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 65: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 69: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 73: Check for possible unrecognized nick 'http'
command-scribe: Line 104: Eric Wells recognized
command-scribe: Schreiber detected that this section was scribed online
edit-substitute: command on line 173 succeeded, changed line 161 from 'Close ASSEMBLY-53' to 'Resolve ASSEMBLY-53'
edit-delete: Line 173 was deleted
system: Transformer: SAXON 8.9
[End of Schreiber diagnostic output]