DAISY 2.02 Validator Introduction
What does the Validator do?
The Daisy 2.02 Validator is a tool for conformance testing of Daisy 2.02 DTBs. The Validator analyzes a Daisy 2.02 DTB and a generates a report containing a list of any errors and warnings found in the DTB.
The difference between
warning is significant, and is explained in more detail in the section Interpreting Results.
For additional information about interpreting the validator results, please read the section on result interpretation in the Validator User Manual. .
When performing the conformance test, the Validator applies a series of tests to the DTB. It compares data found in the DTB to data that is expected to be present. For example, the Validator will calculate the total playback time of the DTB and check whether this expected value correlates with the existing value. If the expectation is not met, the test has failed.
The tests performed have a wide and varying scope. Some tests will, if they fail, indicate that the DTB may not even be readable in a reading device. For example, one or several files may be missing, or damaged.
Not all tests that the Validator performs are aimed only at determining whether the DTB is readable. Conformance testing means that possible violations to specifications are checked, regardless of their impact on readability. In many cases, you will find that although the Validator reports that the DTB is not fully conformant, it will read fine in your reading device. For example, if information such as publishing date or file count is missing or erroneous, it will not have negative impact on readability. But the Validator will still report this as an error, since a normative statement in a specification has been violated.
A full list and explanation of the tests that the Validator performs is provided in the Validator Developer Manual, Appendix 1.
A list of tests that the Validator does not perform, is provided in Validator Scope in the Validator User Manual.
Why use the Validator?
You may use the Validator to:
- Check if the DTB is readable. This is a "good shape" measure that is required to assure that the end user will be able to read the DTB without experiencing problems.
- Check if the DTB is conformant. Many libraries and other information providers take great care to ensure that the information they archive and distribute is fully conformant to the specifications. As with all kinds of information, DTBs are also subject to the principles of longevity. Only if the DTB is conformant can its longevity be guaranteed.
Editing Within the Validator
The Validator tool also contains a document editor that may be used to correct existing errors. This is an additional feature and is not an integrated part of the Validators core functionality. Note that extensive technical knowledge is required to use this feature. See the Validator Document Editor in the Validator User Manual for additional information.
Who should use the Validator?
- Content producers. Organizations creating DTBs need a tool for quality control purposes.
- Distribution environments. Organizations that distribute DTBs need a tool to certify that the product being delivered is fully functional, and to effectively diagnose DTBs that are identified by users as defective.
- Production tool developers. Companies developing systems which create DTBs need a validation tool in order to verify that their systems function properly.
- Playback system developers. Companies developing playback systems for DTBs need a validation tool in order to verify the validity of content used during debugging and testing.
- Conformance testing. Conformance testing agencies need a validation tool to complete the work of conformance testing for production tools, as well as to validate test content used in conformance testing of playback systems.
Use and Licensing
The binary distribution of the Daisy 2.02 Validator is made available by the DAISY Consortium at no cost. The use of the application is entirely at one's own risk.
The library version of the Daisy 2.02 Validator is available under LGPL license and can be found on GNU Project Web site. See "Read More" on the final page of this document for the direct link (on-line access). .
Additional information is also available on the DAISY Software initiative (DSI). See "Read More".
In addition to the Daisy 2.02 Validator, the DAISY Consortium Is providing the following tools related to readability and conformance:
- The Regenerator
- The Regenerator is a software tool designed to enable organisations to repair and upgrade existing Daisy 2.0 and 2.02 DTBs. The tool takes a Daisy 2.0 or 2.02 DTB as input, and performs a series of operations on it in order to output a conformant Daisy 2.02 DTB.
- The Daisy 3 (ANSI/NISO Z39.86-2002) Validator
- DTBs made according to the Daisy 3 (ANSI/NISO Z39.86-2002) standard cannot be validated with the Daisy 2.02 Validator. For these purposes the Daisy 3 Validator should be used.
Detailed information on the DAISY 2.02 Regenerator the manual is available in the DAISY 2.02 Regenerator Manual.
Installation and Requirements
The Daisy 2.02 Validator will run under Windows™ 98, ME, 2000 and XP.
Before the Validator is installed both Microsoft XML Core Services (MSXML) 4.0 SP1 or higher, and Direct X 7 or higher must be installed. If these components are not already installed, go to the following web addresses for download:
The Daisy 2.02 Validator uses a large amount of computer memory when performing the conformance testing. If possible it is recommend that you use a computer with a minimum of 128 Mb RAM. Using a computer with even more RAM will increase performance further.
If you are running the validator in a networked environment, you should begin by checking that all directory paths that will be used are set up correctly. To do this, open the document paths dialog by selecting settings in the main menu and then clicking on document paths. Instructions on the how to modify these settings are given in the DAISY 2.02 Validator User Manual.
Text is available under the terms of the DAISY Consortium Intellectual Property Policy, Licensing, and Working Group Process.