Minutes
<Mike Edwards>
1. Roll call
2. Scribe appointment
Scribe list attached below
3. Agenda bashing
4. Meeting Minutes
a) Minutes of 2011-06-20 telcon:
http://lists.oasis-open.org/archives/sca-j/201106/msg00023.html 5. TC Administrivia
a. Recording issue status - 9 open, 0 new
b. Status of Spring C&I spec
6. ACTION ITEMS
2011-05-23-1: Anish to send a request to the SCA-Assembly TC wrt updating the RDDL and the XSD for spring CI
PENDING
2011-06-06-1: Mike - update the POJO work products with remaining resolved issues
PARTLY DONE, see
http://lists.oasis-open.org/archives/sca-j/201106/msg00019.html 7. Planning for PR of various specs
a) CAA spec: apply issue 233
b) CAA TA: apply issue 235, apply issue 232
c) CAA TC: apply issues 215? & 234
d) POJO spec: DONE
e) POJO TA: apply issue 236
f) POJO TC: apply issue 222, ref udpate(?)
g) Spring: DONE
h) Spring TC: WD ready, need tests
8. New Issues (requires 2/3)
NONE
9. Issues with proposals
a) Issue 240
Normative statements JCA90024 through JCA90039 are all based on optional function
http://osoa.org/jira/browse/JAVA-240 b) Issue 241
Normative statement JCA20009 is optional
http://osoa.org/jira/browse/JAVA-241 c) Issue 242
Normative statement JCA80052 is redundant
http://osoa.org/jira/browse/JAVA-242 10. Issues waiting for updated proposals
NONE
11. AOB
anish sorry i'm late, about to join in a minute
Meeting is quorate (3 of 5)
Agenda Bashing
Add discussion of next week's call to TC Administrivia
Add Exit Criteria before Item 9.
TC Administrivia
Anish:
Spring C&I has been published but with a note that the document is still in Quality Control. TC Admin also created a RDDL
file for the Spring namespace. Some items, like the versioning policy item are missing. These are being addressed but should
not hold up the PR.
Anish:
TC Admin has also commented that the diagrams do not work in Word 2010 and asked they be fixed in a future draft.
Next week's call is cancelled.
Currently no future calls on the calendar. New call to be scheduled starting on 11 July.
Approval of Minutes
No comments or corrections
Resolution: Minutes of 2011-06-20 telcon located at http://lists.oasis-open.org/archives/sca-j/201106/msg00023.html approved
Action Items
2011-06-06-1: Done (also CAA TA/TC and CAA spec)
Exit Criteria
Proposal - Folks,
In line with the other SCA TCs, the SCA-J TC needs to adopt concrete Exit Criteria.
I would be grateful if this could be added to today's TC meeting agenda.
Here is my proposal for the exit criteria, which is based closely on the SCA Assembly TC adopted exit criteria:
a)
The Concrete Exit Criteria for the SCA-J Common Annotations and APIs Specification Version 1.1 are that there shall be at
least 2 independent SCA runtimes each of which are compliant
with all normative portions of the specification as described in Section 12.3 of the SCA-J Common Annotations and APIs Specification
Version 1.1
b)
The Concrete Exit Criteria for the SCA POJO Component Implementation Specification Version 1.1 are that there shall be at
least 2 independent SCA runtimes each of which are compliant with
all normative portions of the specification as described in Section 11.3 of the SCA POJO Component Implementation Specification
Version 1.1
Yours, Mike
Mike reviews the proposal
<anish>
The TC shall define concrete exit criteria that include at least two independent offerings that implement and are compliant
with the all normative portions of specifications and demonstrate interoperability and portability as appropriate. Note that
these are minimums and that the TC is free to set more stringent criteria.
<Mike Edwards>
My proposal is basically a straightforward set of criteria, not requiring anything beyond the charter
Anish:
In the bindings TC there was a similar proposal and an amendment was proposed along the lines of each implementation needing
to provide evidence of interop/portability and that passing the test suite is sufficient evidence.
MikeE:
I do not think the same interop concerns exist here and so I would not be in favor of this amendment.
Anish:
Jeff is concerned that we need to ask every implementation we use for the exit criteria to provide evidence of conformance.
Bryan:
We will have to assess the conformance of any implementation that we use for passing the exit criteria. We will have to
examine any evidence provided so it is not necessary to bake this evaluation into the exit criteria.
<anish>
The Concrete Exit Criteria for the SCA-J Common Annotations and APIs Specification Version 1.1 are that :
1) there shall be at least 2 independent SCA runtimes each of which are compliant with all normative portions of the specification
as described in Section 12.3 of the SCA-J Common Annotations and APIs Specification Version 1.1.
2) those two implementation would provide evidence of interop/portability, as appropriate. Passing the testsuite is considered
sufficient to satisfy this criteron.
<anish>
The Concrete Exit Criteria for the SCA-J Common Annotations and APIs Specification Version 1.1 are that :
1) there shall be at least 2 independent SCA runtimes each of which are compliant with all normative portions of the specification
as described in Section 12.3 of the SCA-J Common Annotations and APIs Specification Version 1.1.
2) those two implementation would provide evidence of portability, as appropriate. Passing the testsuite is considered sufficient
to satisfy this criteron.
Bryan:
Not clear what the second point adds.
Anish:
Jeff thinks that the exit criteria adopted by the Assembly is not sufficient to meet what is required by the charter. He
is thinking of appealing the Assembly decision.
Anish:
This sets the position is that passing the test suite will automatically be accepted by the TC for use relative to the exit
criteria. It also allows the other test suites or evidence to be used for passing the exit criteria.
Dave:
I thought that we were going to use the market to judge compliance.
Anish:
Correct, but the exit criteria required by the TC charter creates a higher bar for the spec exiting the TC.
Dave:
I think point two mixes exit criteria and conformance.
Anish:
We have to have a demonstration of interop/portability (as per the charter)
Dave:
All we need is a claim of conformance. Since we believe that spec defines portability and interop.
Anish:
Jeff would like a higher bar for the demonstration relative to TC exit.
MikeE:
Adding the second point does not change the future actions the TC will have to take. The bindings TC has an additional consideration
about interop that does not apply here.
<anish>
The Concrete Exit Criteria for the SCA-J Common Annotations and APIs Specification Version 1.1 are that :
1) there shall be at least 2 independent SCA runtimes each of which are compliant with all normative portions of the specification
as described in Section 12.3 of the SCA-J Common Annotations and APIs Specification Version 1.1.
2) those two implementation would provide evidence of portability, as appropriate. Passing the testsuite is considered sufficient
to satisfy this criteron.
Motion to amend: Anish: Split criteria into two points first using text in motion second being 2) those two implementation
would provide evidence of portability, as appropriate. Passing the testsuite is considered sufficient to satisfy this criteron.
Motion fails to lack of second
Anish objects to the motion
Vote: 3 yes, 1 no - motion passes
Motion passes by role call
Resolution: Exit criteria for CAA and POJO spec accepted
Issue 241
Motion: Mike, second Dave: Resolve Java 241 with proposal in JIRA
motion passes w/o objection
Resolution: issue 241 is resolved with proposal in JIRA
AOB
Schreiber diagnostics output
[Delete this section before publishing the minutes]
final validation: Title not specified, default title 'OASIS SCA-J TC...' was assumed
final validation: Chair not specified, default chair 'Anish Karmarkar & Dave Booz' was assumed
citation-detection-scribed: Line 92: Check for possible unrecognized nick '2011-05-23-1'
citation-detection-scribed: Line 94: Check for possible unrecognized nick '2011-06-06-1'
citation-detection-scribed: Line 161: Check for possible unrecognized nick 'Motion'
citation-detection-scribed: Line 167: Check for possible unrecognized nick 'Motion to amend'
citation-detection-scribed: Line 173: Check for possible unrecognized nick 'Vote'
citation-detection-scribed: Line 186: Check for possible unrecognized nick 'Motion'
statistics: Schreiber found 118 input lines
edits: Schreiber found no text-edit commands
citation-detection-irc1: Line 10: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 18: Check for possible unrecognized nick '2011-05-23-1'
citation-detection-irc1: Line 21: Check for possible unrecognized nick '2011-06-06-1'
citation-detection-irc1: Line 25: Check for possible unrecognized nick 'a) CAA spec'
citation-detection-irc1: Line 26: Check for possible unrecognized nick 'b) CAA TA'
citation-detection-irc1: Line 27: Check for possible unrecognized nick 'c) CAA TC'
citation-detection-irc1: Line 28: Check for possible unrecognized nick 'd) POJO spec'
citation-detection-irc1: Line 29: Check for possible unrecognized nick 'e) POJO TA'
citation-detection-irc1: Line 30: Check for possible unrecognized nick 'f) POJO TC'
citation-detection-irc1: Line 31: Check for possible unrecognized nick 'g) Spring'
citation-detection-irc1: Line 32: Check for possible unrecognized nick 'h) Spring TC'
citation-detection-irc1: Line 40: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 44: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 48: Check for possible unrecognized nick 'http'
command-scribe: Line 57: Bryan Aupperle recognized
command-scribe: Schreiber detected that this section was scribed online
citation-detection-irc1: Line 182: Check for possible unrecognized nick 'http'
system: Transformer: SAXON 9.0.0.2
[End of Schreiber diagnostic output]