ZedVal 2005 telcon 20050622
Participants: Markus, Piotr, James, Edmar

Toc of this file.
** general items **
** thinktank walkthrough **
** proposed agenda for f2f **
** links **

** general items **
  James; estimates participation 10 days (4f2f, + 6 additional)
  Edmar; [markus forgot to ask]
  Access to DTDs and spec; zed2005 not yet arrived from NLS.
  Generating DTBs for testing
    - only option right now is Bruno
    - testing framework (such as JUnit) may be considered;
    NLS is not going to do the testing this time.
  Sunday - evening dinner; eight oclock at the hotel

  Preparations: everyone to have a working IDE and CVS conn
  Markus suggested list on what to read in on:
   NLS map and diff [7] 
   StAX  [1]
   Schematron [2]
   JAXP1.3 [3]
   
  Markus suggested list of what to be brought along (installed)on machine:
    CVS dump from zedval and dmfc
    JDK1.5 
    JDK1.4.2
    Ideally the source code for jdk1.5, available at [4]
    JWSDP15, available at [5] (contains StAX reference implementation if you want that)
    All the jars and stuff provided by markus in zip at [6]
     (in the zip are also zed2002 and zed2005 specs)
    NLS map and diff [7] 
  
      
** thinktank walkthrough **
Implement 2005 test map 
  --> must have
Define and implement architectural changes for supporting multiple standards
  --> must have
  Method still unclear; share engine but distinctly separate processors is one approach

Fix Exception propagation
 --> must have

Cleanup of file-handling
 --> must have (the only open bug)

JavaLayer1.0
 --> must have

Migrate to SDK1.5 and JRE5
 --> must have, assuming that we can do it without breaking 142 users
 JP: what do we get? 
 JP: backwards compatibility? 
   MG, yes if we use JAXP1.3 syntax for all parser calls
   and dont use new syntactical constructs such as typed collections and asserts
 MG: we can only state conformance for one runtime
 JP: suggest java5 as the reference platform but nothing in the code would break
 if using previous platform: we can perhaps give warnings

Consider the use of Schematron
 --> may do
 MG: only real benefit is consolidation into same schema instance
 JP: does it support inparameters
 JP: does it support custom function calls
 @MG look at whether inparameters etc in iso schematron

Optimize interdoc link checking
 --> must do, move to custom java tests (looking at org.daisy.util.fileset)
  
Fulltext considerations
 --> groups doesnt think theres anything special to do here
 --> are we testing smilrefs? yep, image links resolve and are part of manifest? yep.

Use of some code from the Apache Jakarta project.
  --> may do
  command line interface:: good thing to do to simplify the code
  ECL: we are creating the output, bulding by hand, this package will do this for you
  MG: StAX is another alternative for writing output

DistVal
 --> may do; we are not chartered to do it.
 Distribution validator.
 Problem: ZedVal assumes that its a single volume.
 JP: possible to use the zedval engine for it
  
Consider porting of classes to/reuse of classes from org.daisy.util
  --> may do
  MG: does make economical sense (why maintain two solutions to generic problems)
  but is also a risk from a conformance validator perspective
  JP; if so need to replace current entityresolver etc
  JP; Inclusion of util.fileset packageinclusion for example, 
    relates/links to the architectural changes descided to support multiple standards
  
GUI
 - not gonna do that, not in charter, nope

**proposed agenda**
** DAY ONE **
1.1 Review and walkthrough of current design
1.2 Discuss and settle design re supporting multiple standards
 - determine what parts are shared and what are separate
 - determine cvs handling while implementing it (new branch? versioning?)
 - determine relation to more generic packages in org.daisy.util
 - reconsider the zedval2002 processortype usage rules 
1.3 consider implications of upcoming extensions (mathml-in-daisy)

** DAY TWO **
- joint review of NLS map and diff
- go through new map; determine test processor type for each test; design implications

** DAY THREE to FOUR **
Divide in one-person or several-person groups, focusing on particular
development items (complete list of what they are depends on outcome of day one and two) such as
 - engine and app redesign for multispecsupport
 - code cleanup as described in ** thinktank walkthrough **
 - implementation of 2005 test map  
  - develop relaxng test processors
  - develop schematron/xslt test processors
  - develop custom java class test processors
 - preparation of test suite (using Bruno or whatever we decide, JUnit may perhaps be a good investment) 

** links **
For reading:
[1] StAX  
 http://www.xml.com/pub/a/2003/09/17/stax.html
 http://www.jcp.org/en/jsr/detail?id=173 (also in [6])
[2] Schematron 
 http://www.dsdl.org/
 http://www.schematron.com/
 http://www.xml.com/pub/a/2003/11/12/schematron.html?page=1
 http://xml.ascc.net/resource/schematron/schematron.html
[3] JAXP1.3 
 https://jaxp.dev.java.net/
 http://www-128.ibm.com/developerworks/xml/library/x-jaxp13a.html

For downloading:
[4] the source code for jdk1.5 (really cool when debugging et al)
 http://java.sun.com/j2se/jrl_download.html
[5] JWSDP15
 http://java.sun.com/webservices/downloads/webservicespack.html
[6] 
jars and stuff provided by markus (note: 8 megs)
 http://www.daisy.org/projects/zedval/jarzip.zip

[7] NLS map and diff 
 http://www.daisy.org/projects/zedval/testmap.zip