Notes from zedval telcon 20050926 Original agenda at bottom of document. Action items preceded by '@'. --begin notes-- AgendaItem: are we done with iteration 1? MG: javalayer problem check... remember to update the backlog @ES to check the prob MG: need to check the catalog UNC problems PK: we do want to JAR the dmfc utils; and zedval too PK: have done modifications to entityresolver to support JARness Re DTD validation at initial parse DONE, but James comment: shouldnt be testProcessor but a customTest @MG to fix this PK: added changes to installer class so xerces is not extracted to endorsed not committed yet JP: did we make the decision that we would only support 1.5 runtime? PK: No both. 142 as well; so users wont need to upgrade, JP: and mac support algo for handling input DTB version @ES: add this as a required inparam for now and add the heuristic (if inparam absent) later store the value in ZedContext @PK to lend ES a helping hand JP: problem w entityresolver if specs are wrong: DTD tests would pass need to add an extra test to be sure it uses the right DTDs for iteration 3: look at default assignment of maps how to handle multiple versions and multiple testmaps AgendaItem: workflow for iteration 2? steps to take: 1. develop testMap for one file PK MG 2. develop procMap for that file PK MG 3. review of procMap [telcon] 4. implement test for each entry in the testMap --> then move on to other file types PK and MG deliver 1+2 on mon 10th october mon 17th telcon for review of smil maps JP and ES report that they are available for work during second half october and november JP on vacation 18 november, back 29th pk on folder creation adding zedsuite2005/custom/org/daisy/zedsuite2005 zedsuite/custom/org/daisy/zedsuite PK wants to check out this more. @PK to write email explaning this. --end notes-- --begin agenda-- The backlog xls (describing iteration contents) is available at [1]. The f2f notes are available at [2]. 1. Are we done with iteration one? Walkthrough of items, note anything still waiting to be done. Items in the backlog for iteration 1 listed at [3] 2. What work, whom and and how for iteration 2? 2.1 Recap; current status. Items in the backlog for iteration 2 listed at [4]. 2.2 Work distribution and timelines. Note the need to focus on completing test- and procMaps. 3. CVS File system changes Piotr is ready to do the file system change to the cvs (adding folders). Piotr to describe the addition, to see if it is right. [1]http://www.daisy.org/projects/zedval/Zed2005backlog.xls [2]http://www.daisy.org/projects/zedval/zedval2005-f2f-notes.txt [3] These are the items in the backlog for iteration 1: Exception handling improved -- DONE Integrate JavaLayer 1.0 for audio files --> find corruption problem DONE Changes to support new jing DONE New entity resolver DONE Fixes to file-handling DONE Refactoring in custom test classes Remove DTD processor; validate at initial parse instead Use Jaxp 1.3 DONE Use 1.5 Java runtime DONE [4] These are the items in the backlog for iteration 2: Add properties to file classes to support new tests Add automatic id and reference collection for all XML files New DTD tests for 2005 [PUNT] New RNG tests for 2005 New XSLT tests for 2005 (?) New custom tests for 2005 New testMap/procMap for 2005 Integrate Schematron: new test processor + tests Remove reparse from textInternal etc customTests Remove XSLT develop algo for handling input DTB version determination --end agenda-- MG: javalayer problem check... remember to update the backlog @ES to check the prob MG: need to check the catalog UNC problems PK: we do want to JAR the dmfc utils; and zedval too PK: have done modifications to entityresolver to support JARness Re DTD validation at initial parse DONE, but James comment: shouldnt be testProcessor but a customTest @MG to fix this PK: added changes to installer class so xerces is not extracted to endorsed not committed yet JP: did we make the decision that we would only support 1.5 runtime? PK: No both. 142 as well; So users wont need to upgrade, JP: and mac support algo for handling input DTB version @ES: add this as a required inparam for now and add the heuristic (if inparam absent) later store the value in ZedContext @PK to lend ES a helping hand JP: problem w entityresolver if specs are wrong: DTD tests would pass need to add an extra test to be sure it uses the right DTDs for iteration 3: look at default assignment of maps how to handle multiple versions and multiple testmaps iteration 2 steps to take: 1. develop testMap for one file PK MG 2. develop procMap for that file PK MG 3. review of procMap [telcon] 4. implement test for each entry in the testMap --> then move on to other file types PK and MG deliver 1+2 on mon 10th october mon 17th telcon for review of smil maps JP and ES report that they are available for work during second half october and november JP on vacation 18 november, back 29th pk on folder creation adding zedsuite2005/custom/org/daisy/zedsuite2005 zedsuite/custom/org/daisy/zedsuite PK wants to check out this more. @PK to write email explaning this.