Draft Minutes from 2009-05-05 are attached

[Bob Freund <bob.freund@hitachisoftware.com>]

Title: SCA-Assy - 2009-05-05

Hide Chat

- DRAFT -

OASIS SCA-Assembly TC

05 MAY 2009

Attendees

Present

fred carter	AmberPoint	Group Member
Mark Combellack	Avaya, Inc.	Group Member
Dale Moberg	Axway Software*	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
Vamsavardhana Reddy Chillakuru	IBM	Group Member
Mike Edwards	IBM	Group Member
Dieter Koenig	IBM	Group Member
Simon Nash	Individual	Group Member
Jeff Estefan	Jet Propulsion Laboratory:*	Group Member
Martin Chapman	Oracle Corporation	Group Member
Anish Karmarkar	Oracle Corporation	Group Member
Ashok Malhotra	Oracle Corporation	Group Member
Gilbert Pilz	Oracle Corporation	Group Member
Sanjay Patil	SAP AG*	Group Member
Plamen Pavlov	SAP AG*	Group Member
Scott Vorthmann	TIBCO Software Inc.	Group Member

Chairs

Martin Chapman
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 28th April2009
http://www.oasis-open.org/apps/org/workgroup/sca-assembly/download.php/32307/SCA%20Assembly%20minutes%202009-04-28.html

3. Action Items:
id=2009-04-07-2 status=pending Editors to repair the form of the word portType
id=2009-04-28-1 status=doneWells to divide Issue 122 into more manageable chunks

4. TC Administrivia

Public Review started on April 24.
Public Review ends June 23.

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

5. New Issues

ASSEMBLY 133: Broken links in the Assembly spec
http://www.osoa.org/jira/browse/ASSEMBLY-133


6. Test Assertions and TestCases

Schedule
TestAssertions document is already complete.
TestCases document (and Test Cases) complete May 1
Subcommittee Review May 1 - May 12
Subcommittee Vote - May 13
Assembly TC review May 1 - May 26
Assembly TC vote - May 26

Latest documents:
http://www.oasis-open.org/apps/org/workgroup/sca-assembly-testing/download.php/31915/SCA_Assembly_Test_Assertions_16.odt
http://www.oasis-open.org/apps/org/workgroup/sca-assembly-testing/download.php/32368/SCA_Assembly_TestCases_19.odt

Artifacts:
http://tools.oasis-open.org/version-control/browse/wsvn/sca-assembly/TestCases/#_TestCases_

Start of Review for the Test Assertions document
- discussion

7. Existing (Deferred) Issues

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

Formal submission of a new document relating to this issue:
http://lists.oasis-open.org/archives/sca-assembly/200905/msg00011.html

ASSEMBLY 121: Conformance to OPTIONAL Normative Statements
http://www.osoa.org/jira/browse/ASSEMBLY-121

ASSEMBLY 122: Incorrect usage of MAY Keyword
http://www.osoa.org/jira/browse/ASSEMBLY-122

Latest proposals:
http://lists.oasis-open.org/archives/sca-assembly/200905/msg00001.html

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

ASSEMBLY 134: Promoted component reference changes multiplicity by default
http://www.osoa.org/jira/browse/ASSEMBLY-134

8. AOB

---

Contents

Topics

[1]  Opening

[2]  Action Items

[3]  Administriva

[4]  New Issues

[5]  ASSEMBLY 133: Broken links in the Assembly spec http://www.osoa.org/jira/browse/ASSEMBLY-133

[6]  Test Assertions and TestCases

[7]  Existing Issues

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

[9]  ASSEMBLY 122: Incorrect usage of MAY Keyword http://www.osoa.org/jira/browse/ASSEMBLY-122

[10]  AOB

Table of Resolutions

Table of Action Items

---

Action Items

Done:

id=2009-04-28-1 status=done Wells to divide Issue 122 into more manageable chunks

Pending:

id=2009-04-07-2 status=pending Editors to repair the form of the word portType

New:

id=2009-05-05-1 status=pending Editors to correct, on line 812 there appears an extra period before the word "by"

---

Resolutions

• 2009-05-05-1: Minutes of 2009-04-28 approved w/o
• 2009-05-05-2: m:Edwards s:Wells New Issue Assembly-133 Opened w/o

---

Minutes

<jeff.mischkinsky>

(Autoreply) sleeping -- zzzzzzzzz - dreaming of IM's

Scribe: Bob Freund

Opening

Roll - 17 of 22 voting members present

Agenda - Agreed

Resolution: Minutes of 2009-04-28 approved w/o

Action Items

Action: id=2009-04-07-2 status=pending Editors to repair the form of the word portType

Action: id=2009-04-28-1 status=done Wells to divide Issue 122 into more manageable chunks

Administriva

Public review ends June 23

New Issues

ASSEMBLY 133: Broken links in the Assembly spec http://www.osoa.org/jira/browse/ASSEMBLY-133

Chapman assumes chair

Edwards introduces his issue

<Mike Edwards>

Eric also found:

<Mike Edwards>

also a bad bookmark at line 3384 after the sentence following
[ASM12003].

Resolution: m:Edwards s:Wells New Issue Assembly-133 Opened w/o

Test Assertions and TestCases

Edwards:

Test assertion document is complete.

,,, members are urged to review and comment.

Existing Issues

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

There has been a formal submission of a new document at http://lists.oasis-open.org/archives/sca-assembly/200905/msg00011.html

Chapman says that it it not now actually a formal submision, but it was just a heads up

<jeff.mischkinsky>

u can expect the emails to make it "formal" shortly

<jeff.mischkinsky>

its already in kavi

ASSEMBLY 122: Incorrect usage of MAY Keyword http://www.osoa.org/jira/browse/ASSEMBLY-122

Eric discusses his email at http://lists.oasis-open.org/archives/sca-assembly/200905/msg00001.html

Action: Editors to correct, on line 812 there appears an extra period before the word "by"

<anish>

The reference MUST be nd able to invoke operations on any of its target service.

<anish>

The reference MUST be able to invoke operations on any of its target service.

<Dave Booz>

The new normative statement doesn't stand alone very well. I think it needs to retain the constrainingType context of the original statement. How about "An implementation that is constrained by a constrainingType MUST NOT..."

<anish>

suggestion - s/It is possible that an implementation contains additional/It is possible that an implementation constrained by the constrainingType can/

Wells:

please post additional comments

AOB

straggler roll

Adjourned

[End of Minutes]
Formatted on 2009-05-05 at 12:16:23 GMT-4

---

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]

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

final validation: Chair not specified, default chair was assumed

statistics: Schreiber found 42 input lines

edits: Schreiber found the following text-edit commands:

edits: Line 12: s/doneW/done W

command-scribe: Line 3: Bob Freund is recognized

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

edit-substitute: command on line 12 succeeded, changed line 11 from 'doneW' to 'done W'

edit-delete: Line 12 was deleted

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

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

system: Transformer: SAXON 9.1.0.6

[End of Schreiber diagnostic output]

smime.p7s