Proposed F2F agenda

["Durand, Jacques R." <JDurand@us.fujitsu.com>]

Proposed agenda for end of month F2F:

 

-Jacques

 

 

 

Test Assertions Guidelines (TAG) TC F2F meeting, Mar 27-28, 2008

================================================================

General objective:

a complete draft of the test assertions guideline document,

with at most a few non-critical unfinished points, and agreed-upon editorial work.

 

======================================================================

Day 1: Thursday 27th, AM:

======================================================================

----------------------------------------------------------------------

1. Kick-off (15mn):

- Review of the agenda and proposed updates.

- F2F logistics.

----------------------------------------------------------------------

2. Review of general structure and flow of the Guideline doc. (1h)

- discuss options for general layout, treatment of Best Practices,

glossary core vs. secondary, editorial aspects.

- overall size of document and of each section.

----------------------------------------------------------------------

3. Section-by-section "general review" (1h30)

- gathering comments on each sections (either candidate new issues,

or recommendations for editor's next update).

 

======================================================================

Day 1: Thursday 27th, PM:

======================================================================

----------------------------------------------------------------------

4. Discussion on current Open Issues: (2h)

- i019

- i020

- i021

- i022

- i023

----------------------------------------------------------------------

5. K-TAG forum: proposals & analysis (1:30h)

- treatment of Optional, normative statements: potential best practice / examples

- the notion of "capability" TAs, for assessing the use of some feature.

- treatment of external/secondary specs, and related TAs.

 

======================================================================

Day 2: Friday 28th, AM:

======================================================================

----------------------------------------------------------------------

6.Technical points: (1h30)

- "inheritance" aspects (Kevin)

- "identifying versions" (Paul)

- Pre-requisites details

- others?

----------------------------------------------------------------------

7. Follow-up on prior day unfinished business for Issues. (1h30)

(either old or newly filed issues), plus if time allows:

- Best practices

- review of examples.

 

======================================================================

Day 2: Friday 28th, PM:

======================================================================

----------------------------------------------------------------------

8. Review of References: both inline refs, and prior art / further reading (2h)

- candidate inline refs.

- Editorial treatment and coverage of external related work that is worth

commenting about.

Either from other SDOs, or from industry-specific groups).

o W3C QA framework

o the Schematron model

o ADL

o IEEE http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=147962

o the Voting standard group: "implementation statements".

http://www.eac.gov/vvsg/part1/chapter02.php/

o test-driven developt: http://en.wikipedia.org/wiki/Test-driven_development

o PosTECH: http://iisl.postech.ac.kr/publication/thesis/2007-wjy-ppt.pdf.

o others ?

----------------------------------------------------------------------

9. Discussion on how to approach the XML mark-up next step. (1h)

- objectives to achieve

(what tooling is expected to handle the mark-up: browser? test engine?)

- the case for TA executability, in some specific domain

(e.g. XPath predicates in schematron, in WS-I TAs)