1. Roll Call
Dave Booz, Bryan, Sanjay, Anish, MikeE
2. Scribe Assignment
Sanjay
3. Agenda Bashing
Approved
4. Approval of minutes of 9/18/2008 conf-call
http://lists.oasis-open.org/archives/opencsa-liaison/200809/msg00007.html
Approved unan
5. Issues
a. Issue 3 - http://osoa.org/jira/browse/LIAISON-3
Getting schema document associated with a particular version of the
Spec
Email discussion:
http://lists.oasis-open.org/archives/opencsa-liaison/200809/msg00008.html
Motion by Anish: to resolve Issue 3 with the proposal in http://lists.oasis-open.org/archives/opencsa-liaison/200809/msg00008.html
Seconded by Dave Booz
Motion carried unan
6. OpenCSA Project Management
Review of testing plans
Any other blocker issues?
Policy TC has about 10 open issues, most of them are backed with some proposal. It should be possible to begin on RFC 2119 and testing work.
Java TC has 50+ open issues and behind the curve in caching up with RFC2119/testing work
C-CPP TC has about 10 real issues (although the actual number is higher due to duplicates). Bryan fairly comfortable to wrap up the bulk of the technical issues by end of the year. Carryover of resolutions of conversation/scope related issues from Assembly TC may lead to additional work. One pass of RFC 2119 incorporation is already done. Further tidying up and testing work is due.
BPEL TC - has only 2 major issues, potentially 2 more new issues may get filed. Total of 4. The TC agreed on some wording using 2119 for one section - editors are now expected to apply 2119 to rest of the spec.
Assembly TC - has about 15 issues. 3 issues have agreed upon directions. One pass of 2119 work is done. Testing related work is started. Appendix of conformance statement has been added
Bindings TC - has 18 open issues. Editors have agreed to come up with a first pass of 2119 by next week. No work related to testing yet
Testing:
Assembly TC has produced some formats for test assertions and test documents. Resource issues for building a complete test suite. Need to decide the scope/coverage of testing by the test suite.
he testing effort may soon need a real versioning system e.g. sourceforge. The testing work of different TCs will benefit by sharing the same versioning system. We need versioning capabilities, which OASIS today does not have. We need to investigate what versioning system is used by other TCs and is okayed by OASIS staff.
ACTION: Sanjay to check with the OASIS staff for recommendation of versioning system e.g. Sourceforge
Suggestion to use the LSC calls for discussing administrative issues related to testing
7. Next conf-call?
10/23
8. AOB
None
Raw chat log:
Sanjay: Attendees: Dave Booz, Bryan, Sanjay, Anish
Sanjay: Policy TC has about 10 open issues, most of them are backed with some proposal. It should be possible to begin on RFC 2119 and testing work.
Sanjay: Java TC has 50+ open issues and behind the curve in caching up with RFC2119/testing work
Sanjay: C-CPP TC has about 10 real issues (although the actual number is higher due to duplicates)
Sanjay: Bryan fairly comfortable to wrap up the bulk of the technical issues by end of the year.
Sanjay: Carryover of resolutions of conversation/scope related issues from Assembly TC may lead to additional work
Sanjay: One pass of RFC 2119 incorporation is already done. Further tidying up and testing work is due.
Sanjay: +Anish
Sanjay: BPEL TC - has only 2 major issues, potentially 2 more new issues may get filed. Total of 4.
Sanjay: .. the TC agreed on some wording using 2119 for one section - editors are now expected to apply 2119 to rest of the spec.
Sanjay: +MikeE
Sanjay: Assembly TC - has about 15 issues
Sanjay: .. 3 issues have agreed upon directions
anish am i supposed to be the liaison for binding as well? no idea how many open issues it has. Will have to check
Sanjay: ... One pass of 2119 work is done. Testing related work is started. Appendix of conformance statement has been added
Sanjay: Bindings TC - has 18 open issues
Sanjay: ... Editors have agreed to come up with a first pass of 2119 by next week
Sanjay: ... No work related to testing yet
Sanjay: Agenda Item 5.a Issue 3
Sanjay: http://osoa.org/jira/browse/LIAISON-3
Getting schema document associated with a particular version of the
Spec
Email discussion:
http://lists.oasis-open.org/archives/opencsa-liaison/200809/msg00008.html
Sanjay: Anish posted a revised RDDL template which has pointers for previous versions of the schema documents of CS and higher statuses (and not to CDs).
Sanjay: Bryan: Will the RDDL for a OASIS version include links to CS versions?
Sanjay: answer was yes
Sanjay: Motion by Anish: to resolve Issue 3 with the proposal in http://lists.oasis-open.org/archives/opencsa-liaison/200809/msg00008.html
Sanjay: Seconded by Dave Booz
Sanjay: Motion carried unaimomously
Sanjay: Agenda item 6: OpenCSA Project Management
Review of testing plans
Any other blocker issues?
Sanjay: MikeE: Assembly TC has produced some formats for test assertions and test documnets
Sanjay: ... Resource issues for building a complete test suite
Sanjay: ... Resource issues for building a complete test suite
Sanjay: ... need to decide the scope/coverage of testing by the test suite
Sanjay: Anish: the testing effort may soon need a real versioning system e.g. sourceforge
Sanjay: ... the testing work of different TCs will benefit by sharing the same versioning system
Sanjay: DaveBooz: we should require use of the same versioning system across the OpenCSA TCs
Sanjay: ... consistency regarding style of usage, formats, etc across different TCs is important and sharing the same versioning system will make the efforts efficient
Sanjay: We need versioning capabilities, which OASIS today does not have. We need to investigate what vesioning system is used by other TCs and is okayed by OASIS staff.
Sanjay: Bryan: Do we anticipate TCs approving specific versions of test documents?
Sanjay: Sanjay: a> what statuses do test docs go through e.g. cd, cs, os?, b> maintenance plans for test documnets after TCs finish the spec work
Sanjay: ACTION: To check with the OASIS staff for recommendation of versioning system e.g. Sourceforge
Sanjay: Action assigned to Sanjay
Sanjay: Suggestion to use the LSC calls for discussing administrative issues related to testing
Sanjay: Next call: next week, same time
Sanjay: Mtg adjourned at 11 AM Pacific
|