Agenda
- Introduction of the participants
- Introduction of the Pipeline 2 project
- context (Pipeline 1 background, ZedNext)
- two-phase approach
- overarching principles and concrete objectives
- Presentation of the TTS WG
- context and scope
- objectives
- Presentation of the communication tools
- Google Group
- Google Code project (wiki, trackers)
- Next steps
- identify our availability
- schedule the next concall
Attendees
- Janine Wicke, TPB
- Kåre Sjölander, TPB
- Marisa DeMeglio, DAISY
- Mayu Hamada, ATDO
- Olaf Mittelstaedt, DAISY
- Romain Deltour, DAISY
- Ron Stewart, AHEAD
- Ted Van der Togt, Dedicon
Minutes
Introduction of the Pipeline 2 project
Pipeline 1:
- created for the DAISY 3 revision
- successful project, now in maintenance mode
- Java-centric framework, custom hand-written component system
- but some limitations:
- limited adoption by some organizations (e.g. .Net shops)
- significant learning curve (Java, proprietary XML grammars)
- technical limitations (workflow expressivity, lot of I/O, poor multithreading support)
Context:
- ANSI/NISO Z39.86 standard revision, to be published in 2011, aka "DAISY 4"
- two parts: "Authoring and Interchange" (single source master, DAISY XML) and "Distribution" (consumption format)
- Pipeline 2 intends to become a host framework for transformations of Z39.86-AI documents to various output formats
- e.g. ZedAI to ZedDist
- ZedAI public draft is available (since May 21st) - ZedDist will be available in late 2010
- also: ongoing EPUB revision (expected by the end of 2010)
Pipeline 2:
- high-level goals:
- support for ongoing standard revisions (DAISY, EPUB)
- better interoperability (platform neutral techs, communication layers)
- easier extensibility/maintenance (W3C standards, standard-based component system)
- general approach
- total redesign of the Pipeline 1: future-proof, but a real challenge
- 2-phase approach:
- phase 1: core framework redesign + limited set of conversion
- phase 2: advanced framework features + advanced conversions (Braille+TTS)
- + satellites WGs for Braille and TTS
- only phase 1 is approved by the DAISY Board. Phase 2 depends on its success, will require a new charter
- overarching principles and concrete objectives
- focus on platform neutral XML technologies
- heavily modular
- maximum test coverage
Presentation of the TTS WG
TTS-based production in the Pipeline 1:
- probably the most popular Pipeline 1 feature
- based on successive augmentation of the DTBook XML, with namespaced attributes
- then DAISY 3 fileset generation
- TTS is modular, based on the factory and adapters pattern
Pipeline 2 TTS WG
- why a dedicated working group
- strategical importance of TTS-based production
- test bed for advanced Pipeline 2 functionality
- overarching goals:
- support for DAISY 4 aka "ZedNext"
- native use/support of PLS and SSML standards
- better interoperability (e.g. web services)
- participation
- mostly through the mailing lists + wiki
- + concrete development/contributions welcome (if possible)
- open to developers, but also users/trainers/experts to gather requirements and early feedback
- strong coordination with the Pipeline 2 core developers
Communication tools
Next steps
- identify our availability
- schedule the next concall
- for the next concall: compile a list of requirements/expecations for the TTS-based system