[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [tag] updated agenda
Number for call-in ? -- Stephen D. Green Partner SystML, http://www.systml.co.uk Tel: +44 (0) 117 9541606 http://www.biblegateway.com/passage/?search=matthew+22:37 .. and voice Quoting "Durand, Jacques R." <JDurand@us.fujitsu.com>: > Minor updates to agenda: > - item #4 (added two new "guideline-related issues" i025, i026, see > http://wiki.oasis-open.org/tag/DocIssues) and giving it a bit more time > (+30mn) while assigning 1h to item #5. > - item #7 will be continuation of whatever is left from #4 and #5. > > Also reminder to Kevin and Paul to be prepared to talk for item #6. > > 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: (2:30h) > - i019 > - i020 (subprime predicates) > - i021 > - i022 (variables) > - i023 > - i024 (case of refs to external specifications) > - i025 (grouping / tags) > - i026 (classification) > ---------------------------------------------------------------------- > 5. K-TAG forum: proposals & analysis (1h) > - treatment of Optional, normative statements: potential best practice / > examples > - the notion of "capability" TAs, for assessing the use of some feature. > > ====================================================================== > 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 (# 4, # 5). > (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 others > 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. > ---------------------------------------------------------------------- > 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) > > > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]