OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

sca-assembly message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Draft Minutes SCA-Assembly 2007-10-16 are attached


Title: SCA-Assy - 2007-10-16

WS-I Logo

- DRAFT -

SCA-Assembly TC Teleconference

16 OCT 2007

Attendees

Present
fred carter, (AmberPoint)
Dale Moberg, (Axway Software*)
David DiFranco, (BEA Systems, Inc.)
Jim Marino, (BEA Systems, Inc.)
Michael Rowley, (BEA Systems, Inc.)
Reza Shafii, (BEA Systems, Inc.)
Tom Rutt, (Fujitsu Limited*)
Robert Freund, (Hitachi, Ltd.)
Eisaku Nishiyama, (Hitachi, Ltd.)
Eric Wells, (Hitachi, Ltd.)
Michael Beisiegel, (IBM)
David Booz, (IBM)
Graham Charters, (IBM)
Mike Edwards, (IBM)
Dieter Koenig, (IBM)
Simon Nash, (IBM)
Peter Furniss, (Iris Financial Solutions Ltd.)
Martin Chapman, (Oracle Corporation)
Khanderao Kand, (Oracle Corporation)
Anish Karmarkar, (Oracle Corporation)
Jason Kinner, (Oracle Corporation)
Ashok Malhotra, (Oracle Corporation)
Jeff Mischkinsky, (Oracle Corporation)
David Haney, (Rogue Wave Software)
Ron Barack, (SAP AG*)
Henning Blohm, (SAP AG*)
Sanjay Patil, (SAP AG*)
Peter Peshev, (SAP AG*)
Prasad Yendluri, (Software AG, Inc.*)
Mark Hapner, (Sun Microsystems)
Peter Walker, (Sun Microsystems)
Scott Vorthmann, (TIBCO Software Inc.)
Chair
Martin Chapman and Mike Edwards
Scribe
Bob Freund
Agenda:

1. Opening
Introductions
Roll call
Scribe confirmation
Agenda bashing
2. Approval of minutes of SCA-Assembly TC meeting of 9nd October
http://lists.oasis-open.org/archives/sca-assembly/200710/msg00057.html
3. New Issues
Issue 9: wrong samples for implementation.composite
http://www.osoa.org/jira/browse/ASSEMBLY-9
Issue 10: URI attribute should not be mandatory for bindings
http://www.osoa.org/jira/browse/ASSEMBLY-10
4. Issue Proposals
Issue 6: http://www.osoa.org/jira/browse/ASSEMBLY-6
Proposal: http://lists.oasis-open.org/archives/sca-assembly/200710/msg00063.html
5. AOB

Contents

Topics
[1]  Opening
[2]  New Issue 9
[3]  New Issue 10
[4]  Issue 6
Table of Resolutions
Table of Action Items

Action Items

New:

Resolutions


Minutes

Scribe: Bob Freund

Opening

 
Roll - Quorate 24/38 63%
Resolution: M:Ashok S: Khanderao Minutes of 2007-10-09 approved w/o

New Issue 9

 
PeterP introduces his issue
MikeE:
OSOA has picked up all of these points and has prepared corrected examples
Resolution: M:PeterP S:missed new issue 9 accepted w/o

New Issue 10

 
PeterP introduces his new issue
Resolution: M: PeterP S:Sanjay New issue 10 accepted w/o

Issue 6

 
 
PeterP goes through his proposal
<anish>
looks good to me
<anish>
The offending sentence is: "An unpromoted reference that is operational MUST ..."
<anish>
so s/An unpromoted reference that is operational MUST/An unpromoted reference MUST/
<anish>
?
 
<anish>
Why not do a list: An unpromoted reference MUST have either (a) internal wire, or (b) cardinality > 0, or (c) a binding that has accessible ...
 
Amendment: M:Henning S: JeffM strike "that is operational"
<anish>
How about "An unpromoted reference whose cardinality is 1..1 or 1..n MUST have either an
internal wire within the scope of the current composite or a binding
that identifies correctly either the component/service for a wire to an
endpoint within the SCA domain or the accessible address of some
endpoint outside the SCA domain."
<Dave Booz>
I like Anish's proposal
 
motion to amend withdrawn
<Ashok Malhotra>
Looks good!
 
Amendment: M:Anish S:Khanderao "An unpromoted reference whose cardinality is 1..1 or 1..n MUST have either an
internal wire within the scope of the current composite or a binding
that identifies correctly either the component/service for a wire to an
endpoint within the SCA domain or the accessible address of some
endpoint outside the SCA domain."
<Sanjay>
What is the main purpose of zero cardinality? To allow for invalid wire configuration?
<Dieter Koenig>
"multiplicity" is also used in the sca-bpel spec
<anish>
sanjay, to allow the assembler to decide whether the reference should be wired or not
 
Amendment approved w/o
<jeffm>
fwiw, tom rutt is correct, the chairs can let some conversation go on, as long as it seems useful, before making a formal motion
 
Amendment: M:Simon S:Booz change cardinality to multiplicity
<Sanjay>
I would think that the assembler should still wire, because the component implementation MAY use that reference
 
Amendment accepted w/o
<Sanjay>
An optional use of a reference by an implementation should not mean that the assembler can keep the reference unwired/dangling?
MikeE:
Suggested wording for the 0.. case?
<Peter Peshev>
second sentence changes to : If the reference has a multiplicity of 0..1 or 0..n and the wiring conditions in the previous sentence are not met then the programming model MUST represent the reference as invalid (null, handle that throws exceptions when accessed, or some equivalent for the implementation type in question).
<anish>
dave, i think the assembly-level is already covered. if anything, we need to say something at the prog. model-level
 
Agendum+ Scott wrt Issue process
<Sanjay>
agree with tomR. we should let the discussion flow for a little longer before any motions are made
 
Amendment: M:Haney S:Booz Strike the last sentence of the proposal
 
amendment fails
<anish>
+1 to dave booz's proposal
<anish>
... to switch the order
<henning>
+1 from here as well
 
motion dies due to the hour
<Mike Edwards>
oh boy - and I thought that was one of the simpler proposals ...
 
Meeting Adjournes

[End of Minutes]
Formatted on 2007-10-16 at 10:34:15 GMT-7


Minutes formatted by Schreiber, a collection of XSLT stylesheets by Bob Freund modeled after David Booth's scribe

Schreiber diagnostics output

[Delete this section before publishing the minutes]

citation-detection-scribed: Line 104: Check for possible unrecognized nick 'Motion'

citation-detection-scribed: Line 110: Check for possible unrecognized nick 'Amendment'

citation-detection-scribed: Line 124: Check for possible unrecognized nick 'Amendment'

citation-detection-scribed: Line 140: Check for possible unrecognized nick 'Amendment'

citation-detection-scribed: Line 158: Check for possible unrecognized nick 'Amendment'

statistics: Schreiber found 109 input lines

edits: Schreiber found the following text-edit commands:

edits: Line 108: anish: s/> 1/> 0

command-scribe: Line 5: Bob Freund recognized

command-scribe: Schreiber detected that this section was scribed online

citation-detection-irc1: Line 16: Check for possible unrecognized nick 'http'

citation-detection-irc1: Line 20: Check for possible unrecognized nick 'Issue 9'

citation-detection-irc1: Line 21: Check for possible unrecognized nick 'http'

citation-detection-irc1: Line 23: Check for possible unrecognized nick 'Issue 10'

citation-detection-irc1: Line 24: Check for possible unrecognized nick 'http'

citation-detection-irc1: Line 29: Check for possible unrecognized nick 'Issue 6'

citation-detection-irc1: Line 30: Check for possible unrecognized nick 'Proposal'

edit-substitute: command on line 108 succeeded, changed line 106 from '> 1' to '> 0'

edit-delete: Line 108 was deleted

system: Transformer: SAXON SA 8.9

[End of Schreiber diagnostic output]



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]