Subject: Draft minutes from 2009-08-25 are attached (with improved spelling)

- DRAFT -

OASIS SCA-Assembly TC

25 AUG 2009

Attendees

Present

Mark Combellack	Avaya, Inc.	Group Member
Dale Moberg	Axway Software*	Group Member
Jacques Durand	Fujitsu Limited*	Group Member
Robert Freund	Hitachi, Ltd.	Group Member
Eric Wells	Hitachi, Ltd.	Group Member
Bryan Aupperle	IBM	Group Member
David Booz	IBM	Group Member
Graham Charters	IBM	Group Member
Mike Edwards	IBM	Group Member
Simon Holdsworth	IBM	Group Member
Mike Kaiser	IBM	Group Member
Simon Nash	Individual	Group Member
Jeff Estefan	Jet Propulsion Laboratory:*	Group Member
Martin Chapman	Oracle Corporation	Group Member
Tim Gleason	Oracle Corporation	Group Member
Khanderao Kand	Oracle Corporation	Group Member
Anish Karmarkar	Oracle Corporation	Group Member
Rich Levinson	Oracle Corporation	Group Member
Ashok Malhotra	Oracle Corporation	Group Member
Jonathan Maron	Oracle Corporation	Group Member
Jeff Mischkinsky	Oracle Corporation	Group Member
Gilbert Pilz	Oracle Corporation	Group Member
Aninda Sengupta	Oracle Corporation	Group Member
Clemens Utschig - Utschig	Oracle Corporation	Group Member
Sanjay Patil	SAP AG*	Group Member
Plamen Pavlov	SAP AG*	Group Member
Danny van der Rijn	TIBCO Software Inc.	Group Member
Scott Vorthmann	TIBCO Software Inc.	Group Member

Chair

Bob Freund (pro tem)

Scribe

Bob Freund

Agenda:

Introductions
Roll call
Scribe confirmation
Agenda bashing

2. Approval of minutes of previous SCA-Assembly TC meeting http://www.oasis-open.org/apps/org/workgroup/sca-assembly/download.php/33858/SCA%20Assembly%20minutes%202009-08-18.html

3. Action Items:

4. TC Administrivia

a) 1st Public Review of the Assembly Model spec ended June 23

Public comments list:
http://lists.oasis-open.org/archives/sca-assembly-comment/

b) Looking for Proposals for all open issues - see Item 8 of this agenda

5. Test Assertions and TestCases

Public Review draft has been voted and sent to TC Administration for external posting.

6. Existing Issues with Proposals

ASSEMBLY 147: Assembly Specification does not define the Component Type of a Composite used as an Implementation
http://www.osoa.org/jira/browse/ASSEMBLY-147

Proposal is in JIRA

ASSEMBLY-150: Some TestCases can only be implemented using specific implementation Languages http://www.osoa.org/jira/browse/ASSEMBLY-150

Proposal is in JIRA

ASSEMBLY-156: Spec is unclear if callback binding names need to be distinct from forward binding names
http://www.osoa.org/jira/browse/ASSEMBLY-156

Proposal is in JIRA

7. New Issues

ASSEMBLY 159: Align Test Assertion Document with latest Draft Assembly Spec
http://www.osoa.org/jira/browse/ASSEMBLY-159

ASSEMBLY 160: Section 12 does not require an SCA Runtime to raise an error in all error situations http://www.osoa.org/jira/browse/ASSEMBLY-160

ASSEMBLY 161: @callbackInterface attribute spelled incorrectly in TestComposite54. TestComposite55, TestComposite65
http://www.osoa.org/jira/browse/ASSEMBLY-161

ASSEMBLY 162: Remove Contribution ASM_8003 from the Test Suite
http://www.osoa.org/jira/browse/ASSEMBLY-162

ASSEMBLY 163: TestSuite - TestComposite63 has a wrong Service name
http://www.osoa.org/jira/browse/ASSEMBLY-163

ASSEMBLY 164: Test_ASM_8004 artifacts have errors relating to Java package names
http://www.osoa.org/jira/browse/ASSEMBLY-164

ASSEMBLY 165: Poor wording in descriptions of TestCases ASM_8009 & ASM_8018
http://www.osoa.org/jira/browse/ASSEMBLY-165

ASSEMBLY 166: Test_ASM_9003.composite contains an incorrect Web service URI
http://www.osoa.org/jira/browse/ASSEMBLY-166

ASSEMBLY 167: TestComposite63.composite contains an incorrect name
http://www.osoa.org/jira/browse/ASSEMBLY-167

ASSEMBLY 168: Errors in ASM_12013_TestCase artifacts
http://www.osoa.org/jira/browse/ASSEMBLY-168

ASSEMBLY 169: Errors in Artifacts for ASM_12005_TestCase
http://www.osoa.org/jira/browse/ASSEMBLY-169

ASSEMBLY 170: Errors in Artifacts for a set of testcases in ASM_120xx range http://www.osoa.org/jira/browse/ASSEMBLY-170

ASSEMBLY 171: Problems with artifacts for a set of the TestCases for SCA Assembly
http://www.osoa.org/jira/browse/ASSEMBLY-171

ASSEMBLY 172: ASM-TA-5031 is not adequately tested by any TestCase in the Test Suite
http://www.osoa.org/jira/browse/ASSEMBLY-172

ASSEMBLY 173: Errors in Test Artifacts for ASM_6022, ASM_5032, ASM_5016
http://www.osoa.org/jira/browse/ASSEMBLY-173

8. Existing Issues without proposals

ASSEMBLY-132: Microsoft technical comment about the SCA Assembly Model specification #1
http://www.osoa.org/jira/browse/ASSEMBLY-132

ASSEMBLY-149: Few comments from Siemens
http://www.osoa.org/jira/browse/ASSEMBLY-149

ASSEMBLY 138: Assembly specification unclear on Contribution vs Deployment - when can errors in artifacts be reported?
http://www.osoa.org/jira/browse/ASSEMBLY-138

ASSEMBLY 139: What is a constrainingType file supposed to look like?
http://www.osoa.org/jira/browse/ASSEMBLY-139

ASSEMBLY 140: Need TAs and testcases for property/@file and property/@many=true http://www.osoa.org/jira/browse/ASSEMBLY-140

ASSEMBLY 142: Need a normative statement for @autowire inheritance
http://www.osoa.org/jira/browse/ASSEMBLY-142

ASSEMBLY 143: There are no conformance statements in section 8.5 (CD03)
http://www.osoa.org/jira/browse/ASSEMBLY-143

ASSEMBLY 145: Unmarked MUST on line 1030 (CD03)
http://www.osoa.org/jira/browse/ASSEMBLY-145

ASSEMBLY-157: Make support for constrainingType an optional compliance point
http://www.osoa.org/jira/browse/ASSEMBLY-157

ASSEMBLY 158: Composite property example contradicts spec definition
http://www.osoa.org/jira/browse/ASSEMBLY-158

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

Directional proposal is in this email:
http://lists.oasis-open.org/archives/sca-assembly/200906/msg00129.html

AOB

Minutes

Scribe: Bob Freund

Opening

Roll - quorate with 19 of 24 voting members present

Pro-Tem chair election...

Resolution: no objection for Bob Freund to act as Pro-Tem Chair

agenda - approved

Resolution: Minutes of 2009-08-18 approved w/o

Open Issues

Assembly-147

Skipped due to Edwards' absence

boo hoo

Assembly-150

proposal - Proposal:

One approach to this problem is along these lines:

1. Mark all test assertions and testcases which are necessarily implementation language dependent.

2. Remove the requirement to run all such testcases from the Assembly test suite.

3. Make it a requirement for each language TC for which a valid version of these testcases can exist to add a version of each of these testcases
to the language-specific test suite for their implementation language.

This ensures that whereever possible, the testcase still exists and must still be run, without requiring testing the impossible on other
implementation languages.

Malhotra:

Proposes that the language-dependent test cases be moved to a separate section

hello

I'd like to squeak to register my presence

straggler roll - Mike Edwards

<anish>

is local the only assertion that is optional?

not sure about optional but I think @wiredByImpl falls into the bounds of this issue as well

<anish>

by optional, i mean, optional to conform to Assembly

Motion: m:Aupperle s:Booz Resolve Assembly-150 with the proposal in Jira

Resolution: m:Aupperle s:Booz Resolve Assembly-150 with the proposal in Jira w/o

ASSEMBLY-156: Spec is unclear if callback binding names need to be distinct from forward binding names http://www.osoa.org/jira/browse/ASSEMBLY-156

PROPOSAL:

Replace ASM90002 by the following:

When a service or reference has multiple bindings, all non-callback
bindings of the service or reference MUST have unique names, and all
callback bindings of the service or reference MUST have unique names.
[ASM90002] This uniqueness requirement implies that only one non-callback
binding of a service or reference can have the default @name value,
and only one callback binding of a service or reference can have the
default @name value.

Nash:

Where we were last on this issue was discussing policy attachments using structural uris

Booz:

Policy uses XPath so structural URLs do not apply

<anish>

i don't think bindings are QNames

<anish>

at least we don't say that

<anish>

+1 to jira proposal

Motion: m:Nash s:Karmarkar Resolve Assembly-156 with the proposal in Jira

Resolution: m:Nash s:Karmarkar Resolve Assembly-156 with the proposal in Jira w/o

New Issues

<anish>

+1 to batching

Resolution: Omnibus acceptance and opening of issues 159 and 161 through 173

ASSEMBLY 160: Section 12 does not require an SCA Runtime to raise an error in all error situations http://www.osoa.org/jira/browse/ASSEMBLY-160

Resolution: m:Booz s:Aupperle Open Issue 160 w/o

<anish>

wrt 160 there already are MUST/MUST NOT in section 12.1.2

<anish>

esp. see ASM14004, doesn't that fill in the gap that the issue is talking about

<anish>

perhaps that SHOULD NOT be turned into MUST NOT

Assembly-159

Motion: m:Wells The TC recommends to the test subcttee to begin the creation of a new version of the test assertion document

<Scott>

I am slow when not on the call, so I must make up for that

Resolution: m:Wells s:Aupperle The TC recommends to the test subcttee to begin the creation of a new version of the test assertion document w/o

Assembly-159 shall remain open until a new version of the test assertion document is available

straggler - roll - Gilbert Pilz

Scott, I believe that there are several issues that have been raised but not yet entered in JIRA (3 on the 11th - one by myself and 2 by Mike and on on the 17th by Mike)

<Scott>

ok, will look, Bryan

Schreiber diagnostics output

[Delete this section before publishing the minutes]

final validation: Title not specified, default title 'OASIS SCA-Assembly TC...' was assumed

statistics: Schreiber found 53 input lines

edits: Schreiber found the following text-edit commands:

edits: Line 22: s/cses/cases

edits: Line 84: s/roll/ roll - Gilbert Pilz

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

command-scribe: Line 3: Bob Freund is recognized

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

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

citation-detection-scribed: Line 17: Check for possible unrecognized nick 'proposal - Proposal'

edit-substitute: command on line 22 succeeded, changed line 18 from 'cses' to 'cases'

edit-delete: Line 22 was deleted

citation-detection-scribed: Line 47: Check for possible unrecognized nick 'PROPOSAL'

edit-substitute: command on line 84 succeeded, changed line 80 from 'roll' to ' roll - Gilbert Pilz'

edit-delete: Line 84 was deleted

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

command-autoroll/oasis: Line 93: Successfully fetched roll from http://www.oasis-open.org/apps/org/workgroup/sca-assembly/event.php?event_id=16106

system: Transformer: SAXON 9.1.0.7

[End of Schreiber diagnostic output]

sca-assembly message

- DRAFT -

OASIS SCA-Assembly TC

25 AUG 2009

Attendees

Present

Chair

Scribe

Agenda:

Contents

Action Items

Resolutions

Minutes

Opening

Open Issues

Assembly-147

Assembly-150

ASSEMBLY-156: Spec is unclear if callback binding names need to be distinct from forward binding names http://www.osoa.org/jira/browse/ASSEMBLY-156

New Issues

ASSEMBLY 160: Section 12 does not require an SCA Runtime to raise an error in all error situations http://www.osoa.org/jira/browse/ASSEMBLY-160

Assembly-159

Schreiber diagnostics output