- DRAFT -

SCA-Assembly TC
teleconference

28 OCT 2008

Attendees

Present

fred carter	AmberPoint	Group Member
Mark Combellack	Avaya, Inc.	Group Member
Dale Moberg	Axway Software*	Group Member
Jacques Durand	Fujitsu Limited*	Group Member
Tom Rutt	Fujitsu Limited*	Group Member
Robert Freund	Hitachi, Ltd.	Group Member
Eric Wells	Hitachi, Ltd.	Group Member
Bryan Aupperle	IBM	Group Member
Michael Beisiegel	IBM	Group Member
David Booz	IBM	Group Member
Graham Charters	IBM	Group Member
Mike Edwards	IBM	Group Member
Simon Holdsworth	IBM	Group Member
Dieter Koenig	IBM	Group Member
Simon Moser	IBM	Group Member
Jeff Estefan	Jet Propulsion Laboratory:*	Group Member
Martin Chapman	Oracle Corporation	Group Member
Khanderao Kand	Oracle Corporation	Group Member
Anish Karmarkar	Oracle Corporation	Group Member
Rich Levinson	Oracle Corporation	Group Member
Jeff Mischkinsky	Oracle Corporation	Group Member
Sanjay Patil	SAP AG*	Group Member
Plamen Pavlov	SAP AG*	Group Member
Peter Walker	Sun Microsystems	Group Member
Scott Vorthmann	TIBCO Software Inc.	Group Member

Chairs

Mike Edwards
Martin Chapman

Scribe

Bob Freund

Agenda:

1. Opening

Introductions
Roll call
Scribe confirmation
Agenda bashing

2. Approval of minutes of SCA-Assembly TC meeting of 21st October
http://www.oasis-open.org/apps/org/workgroup/sca-assembly/download.php/29736/SCA%20Assembly%20minutes%202008-10-21.html

3. Action Items:

id=2008-06-03-6 status=pending Test sub cttee produce test assertions and test artifacts and test harness
id=2008-08-26-2 status=pending Editors to re-consider the application of the resolution to assembly-57
id=2008-09-16-1 status=pending owner="Editors" Add text to justify no operator overloading as described in DaveB's E-mail

id=2008-10-30-1 status=pending Vorthmann to examine the specification and create text that implements the directional resolution to Assembly-37
id=2008-10-30-3 status=pending Karmaker to develop concrete text consistent with the directional resolution to Assembly-36
id=2008-10-30-4 status=pending Editors to fix pseudoschemas a/r to be consistent with the resolution that resolves Assembly-32
id=2008-10-30-5 status=pending Vorthman to create a proposal relative to potential solution for issue 5
id=2008-10-30-6 status=pending Koenig do the detailed work to implement the resolution to Assembly-60
id=2008-10-30-8 status=pending Freund to draft a conformance statement
id=2008-10-21-1 status=pending Edwards to produce an updated version of the Issue 16 proposal
DONE
id=2008-10-21-2 status=pending Edwards to refine the proposal for Assembly-51 and to post to the list
DONE
id=2008-10-21-3 status=pending Edwards to kick offdebate on Assembly-48 via the list
DONE

4. TC Administrivia

5. Conformance & Test

Consider the Conformance version of the specification.
http://www.oasis-open.org/apps/org/workgroup/sca-assembly/download.php/29791/sca-assembly-1.1-spec-cd01-rev2%20Conformance-05.pdf

6. Existing Issues

ASSEMBLY-73: What correlation support should SCA provide for callbacks?
http://www.osoa.org/jira/browse/ASSEMBLY-73
http://lists.oasis-open.org/archives/sca-assembly/200810/msg00016.html

ASSEMBLY-16 Component URI is not well described
http://www.osoa.org/jira/browse/ASSEMBLY-16
http://lists.oasis-open.org/archives/sca-assembly/200810/msg00049.html

ASSEMBLY-36 Compatability of component type side files
http://www.osoa.org/jira/browse/ASSEMBLY-36

http://lists.oasis-open.org/archives/sca-assembly/200810/msg00046.html
http://lists.oasis-open.org/archives/sca-assembly/200810/msg00047.html

ASSEMBLY-37 Need to clarify contents of an SCA Domain virtual composite
http://www.osoa.org/jira/browse/ASSEMBLY-37

Direction agreed at Oct F2F - waiting writeup

ASSEMBLY-51: Composite Completeness
http://www.osoa.org/jira/browse/ASSEMBLY-51

http://lists.oasis-open.org/archives/sca-assembly/200810/msg00039.html

ASSEMBLY-48: Defaulting composite reference targets to internal components
http://www.osoa.org/jira/browse/ASSEMBLY-48

http://lists.oasis-open.org/archives/sca-assembly/200810/msg00048.html

ASSEMBLY-33: Long-Running Request-Response Operations
http://www.osoa.org/jira/browse/ASSEMBLY-33

ASSEMBLY-34: Define error handling
http://www.osoa.org/jira/browse/ASSEMBLY-34

ASSEMBLY-46: Dynamic Aspects of the Domain not adequately described in the Assembly Specification
http://www.osoa.org/jira/browse/ASSEMBLY-46

ASSEMBLY-5: component type allows to specify wire targets on references
http://www.osoa.org/jira/browse/ASSEMBLY-5

ASSEMBLY-86: Abstract CRUD APIs for definitions infoset
http://www.osoa.org/jira/browse/ASSEMBLY-86

ASSEMBLY-87: A single definitions infoset is not sufficient
http://www.osoa.org/jira/browse/ASSEMBLY-87

ASSEMBLY-80: Create an Event Processing Model for SCA
http://www.osoa.org/jira/browse/ASSEMBLY-80

ASSEMBLY-2: use of UML 2.0
http://www.osoa.org/jira/browse/ASSEMBLY-2

7. Issue Status
14 Open Issues
x opened
x resolved
8. AOB

Minutes

Scribe: Bob Freund

Opening

Roll - quorate with 17 of 23 voting members

Agenda - agreed

Resolution: Minutes of 2008-10-21 approved w/o

Action Items

Action: id=2008-06-03-6 status=dropped Test sub cttee produce test assertions and test artifacts and test harness

Action: id=2008-08-26-2 status=pending Edwards to re-consider the application of the resolution to assembly-57

Action: id=2008-09-16-1 status=pending owner="Editors" Add text to justify no operator overloading as described in DaveB's E-mail

Action: id=2008-10-30-1 status=pending Vorthmann to examine the specification and create text that implements the directional resolution to Assembly-37

Action: id=2008-10-30-3 status=done Karmaker to develop concrete text consistent with the directional resolution to Assembly-36

Action: id=2008-10-30-4 status=pending Editors to fix pseudoschemas a/r to be consistent with the resolution that resolves Assembly-32

Action: id=2008-10-30-5 status=pending Vorthman to create a proposal relative to potential solution for issue 5

Action: id=2008-10-30-6 status=pending Koenig do the detailed work to implement the resolution to Assembly-60

Action: id=2008-10-30-8 status=pending Freund to draft a conformance statement

Action: id=2008-10-21-1 status=done Edwards to produce an updated version of the Issue 16 proposal

Action: id=2008-10-21-2 status=done Edwards to refine the proposal for Assembly-51 and to post to the list

Action: id=2008-10-21-3 status=done Edwards to kick offdebate on Assembly-48 via the list

Administrivia

-none-

Conformance and Test

Edwards:

A Complete spec version was posted with conformance statements included at http://www.oasis-open.org/apps/org/workgroup/sca-assembly/download.php/29791/sca-assembly-1.1-spec-cd01-rev2%20Conformance-05.pdf

...please look this over with the intent of having an approval vote at the next meeting

...adoption of this version is in the way of editors making further changes

Issues

ASSEMBLY-73: What correlation support should SCA provide for callbacks? http://www.osoa.org/jira/browse/ASSEMBLY-73

proposals are contained in http://lists.oasis-open.org/archives/sca-assembly/200810/msg00016.html

Chapman assumes chair

Edwards discusses the proposals

Motion: m:Edwards s:Booz resolve Assembly-73 with no action

Resolution: m:Edwards s:Booz resolve Assembly-73 with no action w/o

ASSEMBLY-16 Component URI is not well described http://www.osoa.org/jira/browse/ASSEMBLY-16

Proposal at http://lists.oasis-open.org/archives/sca-assembly/200810/msg00049.html

Edwards refers members to the spec document for the discussion (ref new section 6.8)

Edwards then refers members to section 9.2

Motion: m:Edwards s:Booz Resolve Assembly-16 with the text proposed in http://lists.oasis-open.org/archives/sca-assembly/200810/bin00012.bin

Resolution: m:Edwards s:Booz Resolve Assembly-16 with the test proposed in http://lists.oasis-open.org/archives/sca-assembly/200810/bin00012.bin w/o

ASSEMBLY-36 Compatability of component type side files http://www.osoa.org/jira/browse/ASSEMBLY-36

discussion in http://lists.oasis-open.org/archives/sca-assembly/200810/msg00046.html and http://lists.oasis-open.org/archives/sca-assembly/200810/msg00047.html

Karmarkar leads the discussion about his proposal to replace section 4.1

Complete adjusted text:

[1] Component type represents the configurable aspects of an implementation.
A component type consists of services that are offered, references to
other services that can be wired and properties that can be set. The
settable properties and the settable references to services are
configured by a component that uses the implementation.

An implementation type specification (for example, the WS-BPEL Client
and Implementation Specification Version 1.1 [ref]) specifies the
mechanism(s) by which the component type associated with an
implementation of that type is derived.

Since SCA allows a broad range of implementation technologies, it is
expected that some implementation technologies (for example, the Java
Client and Implementation Specification Version 1.1 [ref]) allow
for introspecting the implementation artifact(s) (for example, a Java
class) to derive the component type information. Other implementation
technologies might not allow for introspection of the implementation
artifact(s). In those cases where introspection is not allowed, SCA
encourages the use of a SCA component type side file. A component type
side file is an XML file whose document root element is
sca:componentType.

The implementation type specification defines
whether introspection is allowed, whether a side file is allowed, both are
allowed or some other mechanism specifies the CT.
The component type information derived through introspection is
called the 'introspected component type'. In any case, the implementation
type specification specifies how multiple sources of information
are combined to produce the 'effective component type'. The effective
component type is the component type metadata that is
presented to the using Component for configuration.

The extension of a componentType side file name MUST be
.componentType. The name and location of a componentType side file, if
allowed, is defined by the implementation type specification.

If a component type side file is not allowed for a particular
implementation type, the effective component type and introspected
component type are one and the same for that implementation type.

For the rest of this document, when the term 'component type' is used it refers to the 'effective component type'.

Motion: m:Karmarkar s:Aupperle Resolve Assembly-36 by replacing section 4.1 with the test at [1] above

Resolution: m:Karmarkar s:Aupperle Resolve Assembly-36 by replacing section 4.1 with the test at [1] above w/o

ASSEMBLY-51: Composite Completeness http://www.osoa.org/jira/browse/ASSEMBLY-51

Proposal contained in http://lists.oasis-open.org/archives/sca-assembly/200810/msg00039.html

Edwards reviews the proposal

Motion: m:Edwards s:Booz Resolve Assembly-51 with the proposal contained in http://lists.oasis-open.org/archives/sca-assembly/200810/msg00039.html

Resolution: m:Edwards s:Booz Resolve Assembly-51 with the proposal contained in http://lists.oasis-open.org/archives/sca-assembly/200810/msg00039.html w/o

ASSEMBLY-48: Defaulting composite reference targets to internal components http://www.osoa.org/jira/browse/ASSEMBLY-48

Proposal contained in http://lists.oasis-open.org/archives/sca-assembly/200810/msg00048.html

Edwards reviews his proposal

Motion: m:Edwards s:Karmarkar Resolve Assembly-48 by closing with no action

Resolution: m:Edwards s:Karmarkar Resolve Assembly-48 by closing with no action w/o

AOB

straggler roll

adjourned after resolving five issues

Schreiber diagnostics output

[Delete this section before publishing the minutes]

statistics: Schreiber found 68 input lines

edits: Schreiber found the following text-edit commands:

edits: Line 36: s/proposal at/proposals are contained in

edits: Line 44: s/n :/n:

edits: Line 54: s/Anish/Karmarkar

edits: Line 60: s/Component type represents/[1] Component type represents

command-scribe: Line 4: Bob Freund is recognized

command-scribe: Line 4: Bob Freund's nick bob has been selected

command-chair: Line 8: Since the line number is less than or equal to 20 we will interpret this as a chairname command, note that the chair command is deprecated

command-chair: Line 9: Since the line number is less than or equal to 20 we will interpret this as a chairname command, note that the chair command is deprecated

edit-substitute: command on line 36 succeeded, changed line 35 from 'proposal at' to 'proposals are contained in'

edit-delete: Line 36 was deleted

edit-substitute: command on line 44 succeeded, changed line 43 from 'n :' to 'n:'

edit-delete: Line 44 was deleted

edit-substitute: command on line 54 succeeded, changed line 53 from 'Anish' to 'Karmarkar'

edit-delete: Line 54 was deleted

edit-substitute: command on line 60 succeeded, changed line 56 from 'Component type represents' to '[1] Component type represents'

edit-delete: Line 60 was deleted

command-kaviroll: Line 75: Attempting to fetch roll from http://www.oasis-open.org/apps/org/workgroup/sca-assembly/event.php?event_id=16063

system: Transformer: SAXON 9.0.0.6

[End of Schreiber diagnostic output]

sca-assembly message

- DRAFT -

SCA-Assembly TC
teleconference

28 OCT 2008

Attendees

Present

Chairs

Scribe

Agenda:

Contents

Action Items

Resolutions

Minutes

Opening

Action Items

Administrivia

Conformance and Test

Issues

ASSEMBLY-73: What correlation support should SCA provide for callbacks? http://www.osoa.org/jira/browse/ASSEMBLY-73

ASSEMBLY-16 Component URI is not well described http://www.osoa.org/jira/browse/ASSEMBLY-16

ASSEMBLY-36 Compatability of component type side files http://www.osoa.org/jira/browse/ASSEMBLY-36

ASSEMBLY-51: Composite Completeness http://www.osoa.org/jira/browse/ASSEMBLY-51

ASSEMBLY-48: Defaulting composite reference targets to internal components http://www.osoa.org/jira/browse/ASSEMBLY-48

AOB

Schreiber diagnostics output

sca-assembly message

- DRAFT -

SCA-Assembly TCteleconference

28 OCT 2008

Attendees

Present

Chairs

Scribe

Agenda:

Contents

Action Items

Resolutions

Minutes

Opening

Action Items

Administrivia

Conformance and Test

Issues

ASSEMBLY-73: What correlation support should SCA provide for callbacks? http://www.osoa.org/jira/browse/ASSEMBLY-73

ASSEMBLY-16 Component URI is not well described http://www.osoa.org/jira/browse/ASSEMBLY-16

ASSEMBLY-36 Compatability of component type side files http://www.osoa.org/jira/browse/ASSEMBLY-36

ASSEMBLY-51: Composite Completeness http://www.osoa.org/jira/browse/ASSEMBLY-51

ASSEMBLY-48: Defaulting composite reference targets to internal components http://www.osoa.org/jira/browse/ASSEMBLY-48

AOB

Schreiber diagnostics output

SCA-Assembly TC
teleconference