Draft minutes from 2009-10-27 are attached

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

Title: SCA-Assy - 2009-10-27

Hide Chat

- DRAFT -

OASIS SCA-Assembly TC

27 OCT 2009

Attendees

Present

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
Mike Edwards	IBM	Group Member
Simon Holdsworth	IBM	Group Member
Diane Jordan	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
Ashok Malhotra	Oracle Corporation	Group Member
Jonathan Maron	Oracle Corporation	Group Member
Jeff Mischkinsky	Oracle Corporation	Group Member
Gilbert Pilz	Oracle Corporation	Group Member
Sanjay Patil	SAP AG*	Group Member
Plamen Pavlov	SAP AG*	Group Member
Sabin Ielceanu	TIBCO Software Inc.	Group Member
Eric Johnson	TIBCO Software Inc.	Group Member
Danny van der Rijn	TIBCO Software Inc.	Group Member
Scott Vorthmann	TIBCO Software Inc.	Group Member

Chairs

Martin Chapman
Mike Edwards

Scribe

Bob Freund

Agenda:

1. 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/34862/SCA%20Assembly%20minutes%202009-10-20.html

3. Action Items

id=2009-10-20-1 status=done owner="SanjayP" Send E-mail describing alternative approach for ASSEMBLY-132
id=2009-10-20-2 status=done owner="ScottV" Create JIRA component for Event Handling Issues


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). 1st Public Review of Test Assertions and TestCases ended October 17

c) Confirmation of dates for Assembly F2F Meeting

December 1/2/3
Location: TIBCO, Bay Area, San Francisco.
0.5 day conclusion of SCA Assembly 1.1 specification
2.5 days Event Processing


5. Existing Issues with Proposals

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

Latest Proposal:
http://lists.oasis-open.org/archives/sca-assembly/200910/msg00056.html

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

Latest discussion:
http://lists.oasis-open.org/archives/sca-assembly/200910/msg00047.html
http://lists.oasis-open.org/archives/sca-assembly/200910/msg00034.html

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


6. New Issues

ASSEMBLY 183: Conformance statement for binding.sca
http://www.osoa.org/jira/browse/ASSEMBLY-183

ASSEMBLY 184: TestCase client - need to add capability for Test Bridge to check the actual error returned by the runtime.
http://www.osoa.org/jira/browse/ASSEMBLY-184

ASSEMBLY 185: Artfacts for Testcases that have statically checkable errors must be placed into separate Contributions
http://www.osoa.org/jira/browse/ASSEMBLY-185

ASSEMBLY 186: ASM_5023 - incorrect interfaces and referencename in TestComposite11.composite
http://www.osoa.org/jira/browse/ASSEMBLY-186


7. Test Suite Open Issues

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

Proposal is in JIRA

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

Proposal is in JIRA

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

Proposal is in JIRA

ASSEMBLY 175: Current Schema for Properties does not support value attribute- [ASM50027]
http://www.osoa.org/jira/browse/ASSEMBLY-175

Proposal is in JIRA

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


8. Existing Issues without proposals

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

---

Contents

Topics

[1]  Opening

[2]  Action Items

[3]  Administrivia

[4]  New Issue ASSEMBLY 183: Conformance statement for binding.sca http://www.osoa.org/jira/browse/ASSEMBLY-183

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

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

[7]  AOB

Table of Resolutions

Table of Action Items

---

Action Items

Done:

id=2009-10-20-1 status=done owner="SanjayP" Send E-mail describing alternative approach for ASSEMBLY-132

id=2009-10-20-2 status=done owner="ScottV" Create JIRA component for Event Handling Issues

---

Resolutions

• 2009-10-27-1: Minutes of 2009-10-20 approved w/o
• 2009-10-27-2: m:Malhotra s:Booz Assembly-183 opened w/o
• 2009-10-27-3: m:Edwards s:Karmarkar Resolve Assembly-143 with the text immediately above w/o

---

Minutes

Scribe: Bob Freund

Opening

<gilbert.pilz>

tree killer!

Roll - 19 of 24 voting members present

Agenda - agreed

Mike would like to do Assembly-183 first

no objections on the agenda amandment

Resolution: Minutes of 2009-10-20 approved w/o

Action Items

Action: id=2009-10-20-1 status=done owner="SanjayP" Send E-mail describing alternative approach for ASSEMBLY-132

Action: id=2009-10-20-2 status=done owner="ScottV" Create JIRA component for Event Handling Issues

Administrivia

Public review of both the Assembly Spec as well as the Test Cases have completed

Next F2F is proposed as December 1-3 at Tibco's location in the bay Area

New Issue ASSEMBLY 183: Conformance statement for binding.sca http://www.osoa.org/jira/browse/ASSEMBLY-183

<anish>

why can't you apply policies on binding.sca ?

Resolution: m:Malhotra s:Booz Assembly-183 opened w/o

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

Chapman assumes chair

Edwards dicusses his proposal at

<Mike Edwards>

Latest, latest proposal: http://lists.oasis-open.org/archives/sca-assembly/200910/msg00058.html

<Scott>

now linked in Jira as well

<anish>

so, i don't quite see why we need the stmt in ASM90006

<anish>

the general rules of intent satisfaction say that intents that are specified are either satisfied by the binding or policy set. These rules would still apply. Like they would for any other binding

<anish>

SHOULD with a MUST? It SHOULD satisfy an intent, if not it MUST raise an error. Why not just say it MUST satisfy an intent?

<anish>

IOW, the current wording says that it is never ok not to satisfy an intent as there would be an error

<Sanjay>

I think raising an error when an intent is not satisfied is required for any binding type. Why do we need a separate conformance statement for binding.sca?

<Sanjay>

If the only special casing for binding.sca is that - policy sets are not used for binding.sca, shouldn't we just say that!

<Ashok>

Sanjay, then we shd change the 'should' to a 'must'

<Ashok>

If it's a should then a warning needs to be raised if anything

<Sanjay>

Ashok, even with a 'must' I think it is redundant to the general requirement of 'intents must be satisfied', right?

<Ashok>

yes, that's correct

<anish>

how about: An SCA binding implementor is encouraged to support all the intents specified by the SCA Policy specification in their implementation.

<Mike Edwards>

Proposed text:

<Mike Edwards>

8.5 SCA Binding

The SCA binding element is defined by the following schema.

<binding.sca />

The SCA binding can be used for service interactions between references and services contained within the SCA Domain.
The way in which this binding type is implemented is not defined by the SCA specification and it can be implemented in different ways by different SCA runtimes.
The only requirement is that any specified qualities of service are implemented for the SCA binding type. Qualities of service for <binding.sca/> are expressed using intents.

The SCA binding type is not intended to be an interoperable binding type. For interoperability, an interoperable binding type such as the Web service binding is used.

An SCA runtime has to support the binding.sca binding type. See section 13.2.

A service definition with no binding element specified uses the SCA binding (see ASM50005 in section 4.2 on Component Service).
<binding.sca/> only has to be specified explicitly in override cases, or when a set of bindings is specified on a service definition and the SCA binding needs to be one of them.

If a reference does not have a binding subelement specified, then the binding used is one of the bindings specified by the service provider, as long as the intents attached to the reference and the service are all honoured, as described in Section 4.3 on Component Reference.

If the interface of the service or reference is local, then the local variant of the SCA binding will be used. If the interface of the service or reference is remotable, then either the local or remote variant of the SCA binding will be used depending on whether source and target are co-located or not.

If a <binding.sca/> element of a <component/> <reference/> specifies a URI via its @uri attribute, then this provides a wire to a target service provided by another component.
The form of the URI which points to the service of a component that is in the same composite as the source component is as follows:

<component-name>/<service-name>

<Scott>

works for me to first *shrink* the entire window, then drag the corner of this text box

Motion: m:Edwards s:Karmarkar Resolve Assembly-143 with the text immediately above

Resolution: m:Edwards s:Karmarkar Resolve Assembly-143 with the text immediately above w/o

Time: 5 minutes

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

proposal at http://lists.oasis-open.org/archives/sca-assembly/200910/msg00047.html

AOB

<jeff.mischkinsky>

-1

straggler roll

<Martin C>

roll is fixed

<Mike Edwards>

Thanks Bob

A pleasure

[End of Minutes]
Formatted on 2009-10-27 at 12:06:25 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 51 input lines

edits: Schreiber found the following text-edit commands:

edits: Line 9: s/mike/Mike

command-scribe: Line 1: Bob Freund is recognized

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

edit-substitute: command on line 9 succeeded, changed line 8 from 'mike' to 'Mike'

edit-delete: Line 9 was deleted

citation-detection-scribed: Line 67: Check for possible unrecognized nick 'Time'

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

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

system: Transformer: SAXON 9.1.0.7

[End of Schreiber diagnostic output]

smime.p7s