Today's minutes

[10:50] anish: Agenda --

[10:50] anish: 1. Roll call

2. Scribe appointment
Scribe list attached below

3. Agenda bashing

4. Meeting Minutes
Minutes of 2011-02-28 telcon raw chat log:
http://lists.oasis-open.org/archives/sca-j/201102/msg00070.html

5. TC Administrivia
a. Recording issue status - 9 open, 0 new

b. Filenames for POJO test case and test assertion docs

6. ACTION ITEMS

20110228-01: Mike E - send email to TAB list raising the issue of the proliferation of filenames in the new process.
PENDING

20110228-02: Anish to summarize the approach that we want to use for the new filenames - send an email to the TC list
DONE?

20110228-03: Anish - raise a new issue against the POJO C&I spec for conformance changes

DONE

7. New Issues (requires 2/3)
JAVA-231 POJO CI spec does have any reference to the testcases
http://osoa.org/jira/browse/JAVA-231

8. Issues with proposals

a. JAVA-227: TAB comments on POJO CI TCs
http://osoa.org/jira/browse/JAVA-227
http://lists.oasis-open.org/archives/sca-j/201101/msg00009.html
http://lists.oasis-open.org/archives/sca-j/201102/msg00038.html
http://lists.oasis-open.org/archives/sca-j/201102/msg00043.html
Resolution should include a decision on CN v. CS for POJO TAs

b. JAVA-230 implementation.spring @location attribute does not state the form which its URI value can take
Proposal in JIRA

9. Issues waiting for updated proposals (Spring/EJB/JEE)

a. JAVA-228 Interface of a service when no element is present
http://osoa.org/jira/browse/JAVA-228

b. JAVA-225 Ambiguity about the implicit reference interface in the introspected component type of a Spring app context
http://osoa.org/jira/browse/JAVA-225

c. JAVA-109: Property and reference names computed from SCA annotations in web modules not specified explicitly
http://www.osoa.org/jira/browse/JAVA-109
Proposal in Jira
Waiting for updated proposal (Vamsi)

d. JAVA-174: Consider portlets in the SCA JEE specification
http://www.osoa.org/jira/browse/JAVA-174

e. JAVA-91: Java EE Spec: Need to define the derivation of the name of a component contributed to the Domain by an application.composite file
http://www.osoa.org/jira/browse/JAVA-91
Waiting for updated proposal (Mike)

f. JAVA-93: JEE Integration spec needs to define how effective CT is calculated
http://www.osoa.org/jira/browse/JAVA-93
Waiting for updated proposal (Anish)

g. JAVA-108: RFC2119 Language is needed for the SCA-JEE Specification
http://www.osoa.org/jira/browse/JAVA-108
Waiting for updated proposal

h. JAVA-88: Java EE Spec: The @archive attribute of the implementation.jee element needs fixing
http://www.osoa.org/jira/browse/JAVA-88
No proposal
Plamen to check whether on his informal JEE issues list

10. AOB
a. straggler role

11. Spec status

CAA (part of 1st batch of 1.1 specs):
2 new issue, 2nd PR ended 2010-12-08, CSD05 expected to be final CSD
1st impl: Tuscany (compliant), 2nd impl: ??
http://lists.oasis-open.org/archives/sca-j/201012/msg00000.htmlhttp://lists.oasis-open.org/archives/sca-j/201012/msg00000.htmlTA: CD01 PR ended 2010-10-24, 0 open issue, CSD02 expected to be final CSD
TC: CD01 PR ended 2010-10-24, 0 open issue, CSD02 expected to be final CSD

POJO (part of 1st batch of 1.1 specs):
0 open issues, 2st PR ended 2010-12-08, CSD03 expected to be final CSD
1st impl: Tuscany (compliant), 2nd impl: ??
TA: CSD01 PR ended 2010-12-23
TC: CDS01 PR ended 2010-12-23

EJB Binding (not part of 1st batch of 1.1 specs):
0 open issues, 1st PR done, CSD03 expected to be final CSD
1st impl: ??, 2nd impl: ??
TA: WD stage, no CSD yet, 60 day PR needed
TC: WD stage, no CSD yet, 60 day PR needed

Spring C&I (not part of 1st batch of 1.1 specs):
1 open issues, WD stage, no CSD yet, 60 day PR needed
1st impl: ??, 2nd impl: ??
TA: no work done
TC: no work done

JEE (not part of 1st batch of 1.1 specs):
6 open issues, WD stage (not actively worked on), no CSD yet, 60 day PR needed
1st impl: ??, 2nd impl: ??
TA: no work done
TC: no work done

-----------------------------------------
Scribe list:
Plamen Pavlov: 3
Dave Booz: 3 (Last scribed: 2010-11-0
Anish Karmarkar: 19 (Last scribed: 2010-12-13)
Bryan Aupperle: 30 (Last scribed: 2011-02-07)
Martin Chapman: 22 (Last scribed: 2011-02-14)
Ashok Malhotra: 22 (Last scribed: 2011-02-21)
Mike Edwards: 26 (Last scribed: 2011-02-2

[10:52] anish I may be 5 mins late joining the call (hopefully no more than 5)

[11:04] Bryan Aupperle: Scribe: Bryan Aupperle

[11:04] anish dialing

[11:04] Bryan Aupperle: Topic: Agenda Bashing

[11:06] Bryan Aupperle: Correction to Issue count - actually 1 new.

[11:07] Dave Booz Ashok, after today you will have voting status back

[11:07] Bryan Aupperle: Mike: What are the Spring issues?

[11:07] Bryan Aupperle: Anish: 230, 228, 225.

[11:07] Bryan Aupperle: Agenda agreed.

[11:07] Bryan Aupperle: Topic: Approval of minutes

[11:07] Ashok (Oracle): Thanks, Dave!

[11:09] Bryan Aupperle: Dave: One action in minutes has a date of 29 Feb.

[11:09] Bryan Aupperle: Anish: Should be 28 Feb.

[11:09] Bryan Aupperle: Resolution: Minutes approved w/o

[11:09] Bryan Aupperle: Topic: File names for docs.

[11:10] Bryan Aupperle: Robin has not responded about what will happen with the latest links.

[11:10] Bryan Aupperle: Topic: Action Items:

[11:10] Bryan Aupperle: 20110228-01 - Still pending.

[11:11] Bryan Aupperle: 20110228-02 - Done

[11:11] Bryan Aupperle: 20110228-03 - Done

[11:11] Bryan Aupperle: Topic: JAVA-231 POJO CI spec does have any reference to the testcases
http://osoa.org/jira/browse/JAVA-231

[11:12] Bryan Aupperle: Anish: Summarizes Issue

[11:13] Bryan Aupperle: Motion: Mike, second Bryan - Open Issue 231

[11:13] Bryan Aupperle: Resolution: Motion passes w/o

[11:18] anish: This document defines the TestCases for the SCA Assembly specification.The TestCases represent a series of tests that an SCA runtime must pass in order to claim conformance to the requirements of the SCA Assembly specification.

[11:20] anish: This document defines the TestCases for the SCA-J POJO Component Implementation specification.The TestCases represent a series of tests that SCA runtimes are encouraged to pass in order to claim conformance to the requirements of the SCA-J Component Implementation specification.

[11:21] Mike Edwards: This document defines the TestCases for the SCA-J POJO Component Implementation specification.The TestCases represent a series of tests that SCA runtimes are expected to pass in order to claim conformance to the requirements of the SCA-J Component Implementation specification.

[11:21] Bryan Aupperle: Now discussing the text of the abstract for the testcases document.  Which may also be used in the spec itself.

[11:24] anish: The SCA-J POJO Component Implementation v1.1 TestCases Version 1.0 [ref] defines the TestCases for the SCA-J POJO Component Implementation specification.The TestCases represent a series of tests that SCA runtimes are expected to pass in order to claim conformance to the requirements of the SCA-J Component Implementation specification.

[11:24] Bryan Aupperle: Bryan: Actually text for spec would not be the same.

[11:24] anish: The SCA-J POJO Component Implementation TestCases Version 1.1 [ref] defines the TestCases for the SCA-J POJO Component Implementation specification.The TestCases represent a series of tests that SCA runtimes are expected to pass in order to claim conformance to the requirements of the SCA-J Component Implementation specification.

[11:26] anish: 1.3 Testcases

[11:26] Bryan Aupperle: Anish: Proposed spec text would be added as a new subsection 1.3.

[11:27] Bryan Aupperle: Subsection would be titled Testcases.

[11:28] Bryan Aupperle: Anish: So full proposal

[11:29] Bryan Aupperle: 1.3 Non-Normative References - with a reference to the testcases document

[11:29] Bryan Aupperle: Subsection 1.4 Testcases

[11:29] Bryan Aupperle: Subsection 1.4 Testcases

[11:29] Bryan Aupperle: Text of 1.4 is: The SCA-J POJO Component Implementation v1.1 TestCases Version 1.0 [ref] defines the TestCases for the SCA-J POJO Component Implementation specification.The TestCases represent a series of tests that SCA runtimes are expected to pass in order to claim conformance to the requirements of the SCA-J Component Implementation specification.

[11:30] Bryan Aupperle: Anish: Would expect this to be replicated in CAA.

[11:32] Bryan Aupperle: Motion: Mike, second Bryan - Resolve Issue 231 By adding subsection 1.3 Non-Normative References - with a reference to the testcases document and subsection 1.4 Testcases with text The SCA-J POJO Component Implementation v1.1 TestCases Version 1.0 [ref] defines the TestCases for the SCA-J POJO Component Implementation specification.The TestCases represent a series of tests that SCA runtimes are expected to pass in order to claim conformance to the requirements of the SCA-J Component Implementation specification.

[11:33] Bryan Aupperle: Resolution: Motion passes w/o

[11:34] Bryan Aupperle: AI (Anish): Raise new issue to link CAA spec to testcases.

[11:34] Bryan Aupperle: Topic: JAVA-227: TAB comments on POJO CI TCs
http://osoa.org/jira/browse/JAVA-227

[11:35] anish: "An implementation that claims to conform to this specification MUST be able to run all applicable Tests in
Section 2 TestCases, producing the Expected Output."

[11:41] Bryan Aupperle: Parts to resolution: 1) Add related works link to zip file. 2) Fix text in abstract/intro.  3) Updae conformance document.

[11:42] Bryan Aupperle: Should there be a statement in conformance about zip artifacts being authoritative over text in document?

[11:44] Bryan Aupperle: s/Updae/Update/

[11:44] anish: The XML schema pointed to by the RDDL document at the namespace URI, defined by this specification, are considered to be authoritative and take precedence over the XML schema defined in the appendix of this document.

[11:46] anish: The artifacts contained in the <URL-to-zip> are considered to be authoritative and take precedence over the artifacts described in this document.

[11:49] Bryan Aupperle: Motion: Bryan, second Mike - Resolve 227 by 1) Add related works link to zip file with a description, 2) Fix editorial errors in abstract/intro., 3) Update conformance with a) The artifacts contained in the <URL-to-zip> are considered to be authoritative and take precedence over the artifacts described in this document. and b) An implementation that claims to conform to this specification MUST be able to run all applicable Tests in
Section 2 TestCases, producing the Expected Output.

[11:50] Bryan Aupperle: Resolution: Motion passes w/o

[11:51] Bryan Aupperle: AI (Anish): Raise new issue to link CAA test case documet to to testcases.

[11:52] Bryan Aupperle: AI (Mike): Respond to PR comment re resolution of issue 227.

[11:53] anish: ttp://osoa.org/jira/browse/JAVA-230

[11:53] Bryan Aupperle: Topic: JAVA-230 implementation.spring @location attribute does not state the form which its URI value can take
http://osoa.org/jira/browse/JAVA-230

[11:53] anish: Add the following following line 613 (the description of the @location attribute, before any of the existing normative statements):

The location URI can either be an absolute URI or it can be a relative URI. In the case where the location URI is a relative URI,
the URI MUST be taken as being relative to the base of the contribution which contains the composite containing the
<implementation.spring/> element. [SPR40009]

[11:53] Bryan Aupperle: Mike reviews proposal

[11:54] Bryan Aupperle: Changes would be at line 613 of WD06.

[11:55] Bryan Aupperle: Anish: Shouldn't be a URL instead of a URI?

[11:55] Bryan Aupperle: Ashok: URI would be correct.

[11:56] Bryan Aupperle: Ashok, not worth changing.

[11:56] Bryan Aupperle: Motion: Mike, second Bryan - Resolve issue 230 with proposal in JIRA.

[11:56] Bryan Aupperle: Resolution: Motion passes w/o

[11:59] Bryan Aupperle: Topic: AVA-225 Ambiguity about the implicit reference interface in the introspected component type of a Spring app context
http://osoa.org/jira/browse/JAVA-225

[12:00] Bryan Aupperle: Review of what the state of deliberations is.

[12:03] Bryan Aupperle: AI (Bryan) Determine if CAA test assertions need any 2119 language clean up.

[12:03] Bryan Aupperle: Topic: AOB

sca-j message