Work Plan 2016-17
Chartered project: Obi / Tobi

[Approved in November 2015 DAISY Consortium board meeting]

 

Submitted by: Avneesh Singh

Last updated on: November 30, 2015

††

Obi-Tobi project. 1

Brief introduction. 1

Outline of the plan for 2016-17. 2

Milestones or priorities. 2

Resources. 6

Dependencies & Risks. 6

 

Obi-Tobi project

Nature of activity: Chartered Project

Brief introduction

Project vision: Provide reference implementation of the latest specifications and, empower organizations & individuals across the globe to create accessible and feature-rich content for overcoming diversities like language, cost constraints & accessibility needs.

 

Both of the production tools, Tobi (full text full audio tool) & Obi (audio ncx/ncc tool) have established a landmark in the direction of the project vision.

Tobi pioneered in the implementation of the complete DIAGRAM content model & is among the early tools to produce EPUB 3 media overlays. This makes it a rare tool to produce publications compliant with main stream EPUB 3 specifications, &at the same time, produce access enhanced content.

Obi pioneered the implementation of Navigable Audio-Only EPUB 3 Guidelines. It has made a mark at the grass root level by expanding the reach of DAISY, thus enabling accessible publication production worldwide, and is being used by more than 60 DAISY production centres & numerous individuals, making it one of the preferred DAISY production tool chosen by diverse range of users, from large production houses to home users.

 

Outline of the plan for 2016-17

Obi has earned high reputation for audio-Only book production, which constitutes more than 80% of DAISY production worldwide. It is the driver of Audio-Only specifications & guidelines in the EPUB 3 standards, and is essential for facilitating and encouraging the migration from DAISY Audio-Only production of the members to the EPUB 3 ecosystem. Furthermore it is being used as a primary tool in outreach activities such as WIPO capacity building.

The plan for 2016-17 concentrates on advancing the essential implementation of Audio-Only EPUB 3 specifications, & serving the DAISY members by implementing their important feature requests.

 

Tobi: In strategy implementation, Tobi has the role of innovating production workflows for integrating access-enhanced content with the main stream publications, and creating a path for migration of members & friends to inclusive publishing.

 

Tobi has reached at a stable milestone,there is no immediate requirement of adding support of new specifications for access-enhanced publications, therefore in year 2016 Tobi will continue in the maintenance state. The development plan will be reviewed at the end of 2016, for possibility of implementing features requests from Diagrammar project, the requirements from hearing impaired community, & status of open annotations specifications for linking external descriptions to the publication, which are likely to mature in 2016-17.

Main Objectives of Obi-Tobi Project

         Implement EPUB 3 based specifications to facilitate the migration of DAISY membership to latest specifications for Audio-Only & Media Overlays production

         Support the production of advance accessibility features like Diagrammar image descriptions, open annotations, Math ML etc.) for access-enhanced publications

         Enhance the DAISY 3 & DAISY 2.02 based workflows as per members' requirements

         User interface improvements & maintenance

 

Milestones or priorities

Milestones are the concrete deliverables set forth on the basis of confirmed resources (either we have staff or we have confirmed funds and/or resource commitments).

Priorities are the deliverables based on external (membersí) contributions, our influence & dependency on others, available opportunities etc.

The milestones are defined only for the 1st year, on half yearly basis, for May 2016 and October 2016. While the priorities are defined on yearly basis, for 2016 & 2017.

 

The project plan for 2017 will be refined in September/October 2016.

There are two Obi releases scheduled in 2016, as well as in 2017. There is one Tobi release scheduled in 2016 as well in 2017. There is provision of additional Tobi releases depending on the demand.

Milestone May 2016

Implementation of EPUB 3 based specifications to facilitate the migration of DAISY membership to latest specifications for Audio-Only & Media Overlays production

         Obi: Implement elementary support for skippable structures in EPUB 3. (The full support will be implemented in 2nd phase, when the required specifications would be included in EPUB 3.1revision)

         Tobi: Listed in the priorities.

 

Support the production of advance accessibility features (image descriptions, open annotations, Math ML etc.) for access-enhanced publications

Listed in the priorities.

 

Enhance the DAISY 3 & DAISY 2.02 based workflows as per memberís requirements

         Obi: Improvements related to SBS network based deployment

         Obi: Incremental Workflow improvements based on the requests of members that deploy Obi in the standard desktop environment (Vision Australia, AVH etc.)

         Tobi: Workflow improvements of limited scope requested by the members.

         Tobi: Test release for automated sentence detection in the source document through Pipeline2 (Dependency lies on pipeline 2 project)

 

Remark: Other membersí features are listed in the priorities.

 

User interface improvements & maintenance

         Obi: Update localizations as per the translations provided by the members

         Obi: Improve the efficiency.

         Obi: and improvements to existing features & bug fixes

         Obi: Implement phase 1 of configurable fonts for user interface. Phase 1 includes support for a limited set of English language fonts.

 

Milestone September/October 2016

Implementation of EPUB 3 based specifications to facilitate the migration of DAISY membership to latest specifications for Audio-Only & Media Overlays production

         Obi: Implement the features of EPUB 3.1 revision, which are specific to Audio-Only publications. (Dependency is on the features included in EPUB 3.1 revision)

         Tobi: Listed in the priorities.

 

Support the advance accessibility features (image descriptions, open annotations, Math ML etc.) for access-enhanced publications

         Tobi: Update the Diagrammar image description export as per EPUB 3.1, which means replacing DescribedAt by the linking mechanism finalized by EPUB 3.1. (Dependency is on the EPUB 3.1 revision)

 

Enhance the DAISY 3 & DAISY 2.02 based workflows as per memberís requirements

         Obi: Improvements related to SBS network based deployment

         Obi: Incremental Workflow improvements based on the requests of the members that deploy Obi in the standard desktop environment (Vision Australia, AVH etc.)

         Tobi: Workflow improvements of limited scope requested by the members.

Remark: Other features are listed in priorities.

 

User interface improvements & maintenance

         Obi: Update localizations as per the translations provided by the members

         Obi: Improve the efficiency.

         Obi: Migrate to newer version of dotnet.

         Obi: and improvements to existing features & bug fixes

         Tobi: and improvements to existing features & bug fixes

 

Priorities based on external dependencies & availability of external contributions, 2016

Implementation of EPUB 3 based specifications to facilitate the migration of DAISY membership to latest specifications for Audio-Only & Media Overlays production

         Tobi: Support for EPUB 3.1 revision

         Tobi: Support for EDUPUB

         Tobi: Support for more input formats & validation/checking tools (with help of Pipeline2 backend)

         Both Obi & Tobi: Integrate the latest revision of EPUB Check validator

 

Support the advance accessibility features (image descriptions, open annotations, Math ML etc.) for access-enhanced publications

         Tobi: Implement new Diagrammar features if these are requested by Diagrammar project.

         Tobi: Update the Diagrammar image description export for keeping it sync. With Readiumís Diagrammar image descriptions implementation.

         Tobi: Improve the support for Math ML.

 

Enhance the DAISY 3 & DAISY 2.02 based workflows as per memberís requirements

         Both Obi & Tobi: integrate specific audio filters.

         Tobi: Integrated installer containing all the dependencies.

         Obi-Tobi promotion: Arrange face to face meetings with membersí to understand their requirements in a better way.

         Obi-Tobi promotion: Deploy the tools under the capacity building projects.

 

User interface improvements & maintenance

         Both Obi & Tobi: New localizations requested by the DAISY Community.

         Obi: Implement configurable fonts for user interface (wider set of fonts for wider set of languages.

         Tobi: Additional maintenance releases.

 

Priorities based on external dependencies & availability of external contributions, 2017

Implementation of EPUB 3 based specifications to facilitate the migration of DAISY membership to latest specifications for Audio-Only & Media Overlays production

         Tobi: Support for EPUB 3.1 revision

         Tobi: Support for EDUPUB

         Tobi: Support for more input formats & validation/checking tools

         Both Obi & Tobi: Integrate the latest version of EPUB Check validator

 

Support the advance accessibility features (image descriptions, open annotations, Math ML etc.) for access-enhanced publications

         Tobi: Implement new Diagrammar features if requested by Diagrammar project.

         Tobi: Implement W3C/EDUPUB open annotations specifications for linking the external descriptions to the publication.

         Tobi: Improvements to support for video as per the requirements of hearing impaired community

         Tobi: Improve the support for Math ML

 

Enhance the DAISY 3 & DAISY 2.02 based workflows as per memberís requirements

         Both Obi & Tobi: integrate specific audio filters

         Tobi: Integrated installer containing all the dependencies.

         Obi-Tobi promotion: Arrange face to face meetings with membersí to understand their requirements in a better way.

         Obi-Tobi promotion: Deploy the tools under the capacity building projects.

 

User interface improvements & maintenance

         Both Obi & Tobi: New localizations requested by the DAISY Community.

         Obi: Improve performance of user interface

 

Resources

The following tables lists the resources calculated for 2014 and, for 2015.

Table 1.1: % FTE for development team members

S. No.

Name

2016

2017

1.

Avneesh Singh (project manager)

35%

30%

2.

Daniel Weck (software architect)

20%

10%

3.

Rachana Singh (software tester & developer)

100%

75%

4.

Rohit Tandon (software developer)

100%

75%

 

Total (FTE)

2.55FTE

1.9FTE

 

Total (US$)

58k

42k

 

Table 2: Direct cost in US$.

S. No.

Item

2016

2017

1.

Travel(face to face meetings/promotion)

2k

2k

2.

Outsourcing (manuals, training & promotion videos etc.)

2k

2k

3.

Other costs (software/hardware/misc etc.)

0

0

 

Total

4k

4k

 

Dependencies & Risks

Dependencies

         The required pipeline 2 features should be delivered by the Pipeline 2 team at appropriate time.

         EPUB 3.x revisions should be delivered on time.

         Members collaborate with the project team, and provide feedback & detailed specifications for their requirements.

 

Risks

         Contributor withdrawal leads to discontinuation of certain functionality: If the functionality is aligned with future strategy of DAISY Consortium, the development team will intend to maintain it. Otherwise DCís development team holds no responsibility for taking that particular functionality forward.

         Non availability of a team member at time critical for project: As project resources are already lean, such a condition can lead to cut in feature list or lengthening of timeline. Damage control can be achieved to some extent if alternative for the team member is available at that time.

         The license of a desired dependency is incompatible with the project license: Either decide to change the project license or integrate some additional development effort in the budget and timeline.

---end of document--