Raw Text Minutes from SCA-J Conf Call, 24th Jan 2011

[Mike Edwards <mike_edwards@uk.ibm.com>]

1. Roll call

2. Scribe appointment
Scribe list attached below

3. Agenda bashing

4. Meeting Minutes
Minutes of 2011-01-10 telcon
http://www.oasis-open.org/committees/download.php/40710/SCA%20Java%20Minutes%202011-01-10.doc

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

6. ACTION ITEMS

2010-11-15-02: Mike to follow up with
Jacques on 217, 218, ,219, 220, and 221
PENDING

20101206-01: (Anish) Prepare an updated
proposal for Issue 182 with extra example material and further editorial
updates
PENDING

20101206-02: (Mike) Post a comment to
the list with a strawman proposal for Issue 224
PENDING

7. New Issues (requires 2/3)
NONE

8. Issues with proposals
NONE

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

a. JAVA-226: TAB comments on POJO CI
TAs
http://osoa.org/jira/browse/JAVA-226
http://lists.oasis-open.org/archives/sca-j/201101/msg00010.html

b. 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

c. JAVA-182: SCA Spring C & I specs
needs to refactor text under abstract and introduction
http://www.osoa.org/jira/browse/JAVA-182
Awaiting an action from Anish

d. JAVA-224
Support for JSR-330 - Dependency Injection
for Java
http://osoa.org/jira/browse/JAVA-224
Awaiting an action from Mike

e. JAVA-217 Weak design: Target is often
not well identified, in several TAs
http://osoa.org/jira/browse/JAVA-217

f. JAVA-220 Target should not be an
"event", but an identifiable entity
http://osoa.org/jira/browse/JAVA-220

g. JAVA-221 Stronger use of "tags"
might help classify TAs based on targets
http://osoa.org/jira/browse/JAVA-221

h. 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

i. 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)

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

k. 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)

l. 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)

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

n. 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: Mike Edwards
Agenda Bashing:
We can deal with Issues 224, 226, 227
Item 4 Meeting Minutes
Minutes from 10th Jan 2011
Minutes approved without change
Item 5 TC Administrivia
14 open, 0 new issues
2010-11-15-02: Mike to follow up with
Jacques on 217, 218, ,219, 220, and 221 
PENDING 

20101206-01: (Anish) Prepare an updated
proposal for Issue 182 with extra example material and further editorial
updates 
PENDING 

20101206-02: (Mike) Post a comment to
the list with a strawman proposal for Issue 224 
DONE
Item 6 Action Items
2010-11-15-02: Mike to follow up with
Jacques on 217, 218, ,219, 220, and 221 
PENDING 

20101206-01: (Anish) Prepare an updated
proposal for Issue 182 with extra example material and further editorial
updates 
PENDING 

20101206-02: (Mike) Post a comment to
the list with a strawman proposal for Issue 224 
SDONE
Item 9 Open Issues
JAVA-224 
Support for JSR-330 - Dependency Injection
for Java 
http://osoa.org/jira/browse/JAVA-224
Proposal from Mike Edwards:
http://lists.oasis-open.org/archives/sca-j/201101/msg00012.html
Mike dessribes the proposal, which is
to Close with No Action
Anish: Not sure that JSR-330 is really
tied to JEE - it can be used independent of JEE.
The material could be used independent
of JEE.
Anish: Even so, it is too late for this
release. (V1.1)
Mike moves to close Issue 224 with No
Action
Dave seconds
Motion passes unanimously
Issue 224 is resolved - Close with No
Action
Action: 20110124-01: (Mike) Respond
to the original comment in JAVA-224
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
Bryan describes the material contained
in his email (linked above)
Bryan: 1) Link to test artifacts
- addition formed after the one in Assembly
Bryan: Martin had posted a comment about
the use of "related work" for this reference
Mike: There is the argument that we're
permitted to change the front matter material without needing a new CSD/Public
Review
Bryan: 2) Point about the lack of formal
normative requirements in the spec
Anish: We can certainly add a normative
statement requiring runtimes to pass these tests
Bryan: 3) Also an error in the citation
format section in the front matter
anish lowered your hand
Mike: Normative statements are pointless
in a way in that the document is the spec for the test suite - but that
we the TC also produced the test suite artifacts and "guarantee"
that they conform to the document (it would be an error that the TC would
have to fix to be otherwise)
Anish: Is it OK to have a spec with
no normative statements?  Does OASIS require normative statements?
Ashok: Can have a standard that is purely
descriptive (in another standards body)
anish: A specification that is approved
by the TC at the Committee Specification Public Review Draft, Committee
Specification or OASIS Standard level must include a separate section,
listing a set of numbered conformance clauses, to which any implementation
of the specification must adhere in order to claim conformance to the specification
(or any optional portion thereof).
Martin: Are the test suites REALLY a
specification - or are they Committee Notes ?
Martin: These test documents should
be seen all as one package.
Anish: This needs to be taken up with
TC Admin?
Action: 20110124-02: (Anish) Take up
the Links question relating to JAVA-227 with TC-Admin - aim to get the
links updated without requiring a new CSD or public review
Hold further action on JAVA-227 until
feedback from TC Admin is received
JAVA-226: TAB comments on POJO CI TAs

http://osoa.org/jira/browse/JAVA-226

http://lists.oasis-open.org/archives/sca-j/201101/msg00010.html
Bryan - is about Test Assertions - comments
are in the linked email
Bryan: 1st item is about material added
by TC Admin
- comments must be addressed to TC Admin,
not this TC
Item 2: nice to have a summary to improve
readability
Item 3: nit
Item 4: The specification is clearly
defined as the SCA POJO spec..
Item 5: Is from the TA Guide
Item 6: There is a question about RFC2119
language here - there is 1 "may" & 1 "must" - which
should probably be changed
Item 7: Prerequisites must always be
true or the test would be not valid / unpredictable
Item 8: Nit - although there is a "should
here"
Item 9: Terminology from the TA Guide
Item 10: A terminology issue about the
description of Tags
Bryan: There is a reference JAXB spec
in one test assertion but it is not referenced in the normative references
section
AOB
Adjourned

Yours, Mike

Dr Mike Edwards		Mail Point 146, Hursley Park
STSM		Winchester, Hants SO21 2JN
SCA & Services Standards		United Kingdom
Co-Chair OASIS SCA Assembly TC
IBM Software Group
Phone:	+44-1962 818014
Mobile:	+44-7802-467431 (274097)
e-mail:	mike_edwards@uk.ibm.com

---

Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU