Draft minutes of 2008-10-14 are attached (sorry for lateness)

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

Title: SCA-Assy - 2008-10-14

Hide Chat

- DRAFT -

SCA Assembly TC
Teleconference

14 OCT 2008

Attendees

Present

fred carter
Mark Combellack
Robert Freund
Eric Wells
Bryan Aupperle
Michael Beisiegel
David Booz
Graham Charters
Mike Edwards
Simon Moser
Jim Marino
Simon Nash
Simon Nash
Jeff Estefan
Anish Karmarkar
Sanjay Patil
Plamen Pavlov
Peter Walker
Sabin Ielceanu
Scott Vorthmann

Chair

Mike Edwards

Scribe

Bob Freund

Agenda:

1. Opening

Introductions
Roll call
Scribe confirmation
Agenda bashing

2. Approval of minutes of SCA-Assembly TC F2F meeting of 30th September / 1st October

http://www.oasis-open.org/apps/org/workgroup/sca-assembly/download.php/29634/SCA%20Assembly%20minutes%202008-09-30.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-2 status=pending Edwards to write up some specific text consistent with the directional resolution to Assembly-16
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-7 status=pending Edwards to make a version of the spec and will label normative statements and will produce an example test case
id=2008-10-30-8 status=pending Freund to draft a conformance statement


4. Conformance, Test
http://lists.oasis-open.org/archives/sca-assembly/200810/msg00013.html


5. New Issues

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

6. Existing Issues

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/msg00011.html

Direction agreed at Oct F2F - waiting writeup

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

Direction agreed at Oct F2F - waiting writeup

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-61: Component type information directly in components
http://www.osoa.org/jira/browse/ASSEMBLY-61
http://lists.oasis-open.org/archives/sca-assembly/200810/msg00014.html

ASSEMBLY-64: Specification inconsistent on whether a default value for Property on a Constraining Type is allowed or not
http://www.osoa.org/jira/browse/ASSEMBLY-64
http://lists.oasis-open.org/archives/sca-assembly/200810/msg00015.html

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-47: Interface element needs an operation child element
http://www.osoa.org/jira/browse/ASSEMBLY-47

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

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-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
15 Open Issues
x opened
x resolved
8. AOB

---

Contents

Topics

[1]  Opening

[2]  Action Items

[3]  Conformance & Test

[4]  New Issues

[5]  New Issue ASSEMBLY-86: Abstract CRUD APIs for definitions infoset http://www.osoa.org/jira/browse/ASSEMBLY-86

[6]  New Issue ASSEMBLY-87: A single definitions infoset is not sufficient http://www.osoa.org/jira/browse/ASSEMBLY-87

[7]  Old Moldy Issues

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

[9]  AOB

Table of Resolutions

Table of Action Items

---

Action Items

Done:

id=2008-10-30-2 status=done Edwards to write up some specific text consistent with the directional resolution to Assembly-16

id=2008-10-30-7 status=done Edwards to make a version of the spec and will label normative statements and will produce an example test case

Pending:

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

---

Resolutions

• 2008-10-14-1: Minutes of 2008-09-30 approved w/o
• 2008-10-14-2: Assembly-86 opened w/o
• 2008-10-14-3: m:Karmarkar s:Booz New Issue Assembly-87 opened w/o

---

Minutes

Scribe: Bob Freund

Opening

Martin Chapman and Ashok Malhotra are on LOA

Mark Combellack has come off LOA

Roll - quorate with 13 of 24 voting members

Agenda - agreed

Resolution: Minutes of 2008-09-30 approved w/o

Action Items

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

Action: id=2008-08-26-2 status=pending Editors 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-2 status=done Edwards to write up some specific text consistent with the directional resolution to Assembly-16

Action: id=2008-10-30-3 status=pending 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-7 status=done Edwards to make a version of the spec and will label normative statements and will produce an example test case

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

Conformance & Test

see http://lists.oasis-open.org/archives/sca-assembly/200810/msg00013.html which contains an updated version of the spec as well as some conformance materials

Edwards reviews the materials

Nash suggests we in-line the text from the appendix so that it is absolutely the same text

<Bryan Aupperle>

is it just me or is there noise on the line?

<anish>

the contribution should not be thrown out

<anish>

only the deployment should fail

<anish>

we have a many-many

New Issues

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

Karmarkar discusses his new issue

Resolution: Assembly-86 opened w/o

<Jim Marino>

I am in on the call, just mute problem

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

Resolution: m:Karmarkar s:Booz New Issue Assembly-87 opened w/o

<Sanjay>

Anish, curious to know the scenarios that would benefit from standardization of the CRUD API for the definitions infoset.

Old Moldy Issues

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

see Edwards' proposal at http://lists.oasis-open.org/archives/sca-assembly/200810/msg00011.html

<Sanjay>

I guess any SCA runtime implementation will have to come up with some CRUD API for its own sake but is there a real reason for standardizing these API?

<anish>

gd Q sanjay, but this applies to all the abstract APIs that we define

<anish>

i still think that changing property using the property URI is very strange

<anish>

at runtime that is

<anish>

for example i configured composite A containing a component property. Composite A is now used at multiple places. The property value is guaranteed to be the same regardless of where and how composite A is used.

<anish>

if u use a URI to change a property inside a particular occurrence of the property, u'll be breaking the encapsulation

<anish>

how about 'relevant binding type'

<Sanjay>

I also don't see a convincing case for changing props of deployed components but I guess defining a URI for props is harmless. We may raise some Qs in the mind of the spec reader but I guess we are way beyond worrying about that :-)

Time ran out in discussion...

AOB

straggler roll

Adjourned

<Mike Edwards>

Thanks Bob

<Mike Edwards>

can you give me a few minutes to sort out the roll, Bob

<Mike Edwards>

I'd like to get Simon & Mark's status adjusted

no problem. just let me know when

<Mike Edwards>

OK, Bob - all done

thanks

[End of Minutes]
Formatted on 2008-10-21 at 15:33:49 GMT+2

---

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]

statistics: Schreiber found 83 input lines

edits: Schreiber found the following text-edit commands:

edits: Line 4: s/1. Opening/Agenda: 1. Opening

edit-substitute: command on line 4 succeeded, changed line 1 from '1. Opening' to 'Agenda: 1. Opening'

command-scribe: Line 2: Bob Freund is recognized

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

edit-delete: Line 4 was deleted

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

console: Line 114: kaviroll: http://www.oasis-open.org/apps/org/workgroup/sca-assembly/event.php?event_id=16061

system: Transformer: SAXON 9.0.0.6

[End of Schreiber diagnostic output]