Interpreting DAISY 2.02 Validator Results

Original Author(s): David Gordon

The following examples are validation errors reported by the DAISY 2.02 Validator with details as to how the identified errors can be corrected.

Note: The numbers shown in square brackets, refer to the position (line and character) in the text file where the error has been found. For example, [13:19] refers to line 13 character 19.

If the numbers [-1:-1] are displayed, the error can not be located to a particular point in the file.

Last updated: February 2005

Example 1

Error: file missing @ 12345.html [13:19]

: the smil file referenced by the content document does not exist, file doesn't exist

Diagnosis:

The Validator is pointing to the following line in the 'Content document'(html file):

<h1 id="bajw_0004"><a href="bajw0004.smil#bajw_0004"></a></h1>

This line is for a heading that is no longer being used - it has no text typed into it unlike the following example:

<h1 id="bajw_0002"><a href="bajw0002.smil#bajw_0002">Heading One</a></h1>

The line with the error is pointing to a SMIL link that no longer exists and is no longer a part of this particular DAISY project.

Cure:

Use the Validator's text editor to delete the complete line and then save the changes.

Example 2

Error: ncc.totalElapsedTime @ bajw0007.smil [10:55]

: the value of meta ncc:totalElapsedTime does not correspond to the total time elapsed to this point, suggested value: 00:08:51.442

Diagnosis:

The Validator is pointing to the following line in a SMIL file.

<meta name="ncc:totalElapsedTime" content="00:08:53" />

There is a discrepancy in the time that the production (authoring) tool has calculated (00:08:53) and the time that the Validator has calculated (00:08:51.442). This is a resulting of variations in rounding.

Cure:

This error can be corrected by using the Validator's text editor to change the line with the error from:

<meta name="ncc:totalElapsedTime" content="00:08:53" />

to:

<meta name="ncc:totalElapsedTime" content="00:08:51.442" />

Then save the edited file.

Note: The same process can be applied to any reported timing errors.

Example 3

Error: attribute pair error@ncc.html [-1:-1]

: one of the attributes in an attribute pair is missing or occurs more than once, meta name = ( 'dc:publisher' )

Diagnosis:

The Validator is pointing to the beginning of the ncc.html file. Check through the list of meta data elements to see if the meta name 'dc:publisher' is present (it may not have been entered when the project was created).

<meta name="dc:creator" content="RNIB Talking Book Service" />
<meta name="dc:date" content="2004-02-09" scheme="yyyy-mm-dd" />
<meta name="dc:format" content="DAISY 2.02" />
<meta name="dc:identifier" content="UK-RNIB-1667C0B5-360A-4BF3" />
<meta name="dc:language" content="en-GB" scheme="ISO 639" />
<meta name="ncc:charset" content="windows-1252" />
...
<meta name="ncc:kByteSize" content="14459" />
<meta http-equiv="Content-type" content="text/html; charset=windows-1252" />

Cure:

Using the Validator's text editor, manually add the following line into the list of meta data:

<meta name="dc:publisher" content="RNIB" />

Then save the edited file.

Note: The same process can be applied to any error that is reported from missing meta data elements.

Example 4

Error: ncc:files @ ncc.html [32:42]

meta element ncc:files does not match the number of files found in the DTB file set, suggested value: 19

Diagnosis:

The Validator is pointing to an incorrect value of meta data in the content for the "ncc:files" entry.

<meta name="ncc:narrator" content="DTG" />
<meta name="ncc:sourceDate" content="2003" scheme="yyyy" />
<meta name="ncc:sourceEdition" content="None" />
<meta name="ncc:sourcePublisher" content="RNIB" />
<meta name="ncc:files" content="17" />
<meta name="ncc:generator" content="LpStudioGen 1.6" />
<meta name="ncc:kByteSize" content="2083" />

 

The given value of 17 is incorrect.

Cure:

This error can be corrected by using the Validator's text editor to change the line with the error from:

<meta name="ncc:files" content="17" />

to:

<meta name="ncc:files" content="19" />

Then save the edited file.

Note:The same process can be used for other value errors.

Example 5

Error: attributes mismatch @ ncc.html [22:52]

: the content of one of the values in this attribute pair is invalid, name = 'ncc:totalTime' : attribute content doesn't follow rules.

Diagnosis:

The Validator is pointing to an incorrect content entry in the meta data entry 'ncc:totalTime'.

<meta name="ncc:sidebars" content="0" />
<meta name="ncc:setInfo" content="1 of 1" />
<meta name="ncc:tocItems" content="11" />
<meta name="ncc:totalTime" content="00:04-18" />
<meta name="dc:source" content="None" scheme="ISBN" />
<meta name="dc:subject" content="None" scheme="keyword" />
<meta name="ncc:depth" content="1" />

This error is not too obvious, but there is a hyphen between 04 and 18 in the reported total time. The format required is a colon.

Cure:

This error can be corrected by using the Validator's text editor to change the line with the error from:

<meta name="ncc:totalTime" content="00:04-18" />

to:

<meta name="ncc:totalTime" content="00:04:18" />

Then save the edited file.

Note:The same process can be used for other such character errors.

Example 6

Error: Clip-end time @ baiw007.smil [111:84]

The clip-end time value references a point in the audio file that does not exist, maximum possible value is: npt=89.260s

Diagnosis:

The Validator has calculated that an incorrect time entry has been made in the named SMIL file.

<par endsync="last">
<text src="sitevisits.html#xbai_0040" id="xbai_0040" />
<seq>
<audio src="7.mp3" clip-begin="npt=83.856s" clip-end="npt=91.185s" id="qwrt_0010" />
</seq>
</par>
</seq>
</body>
</smil>

As in other examples provided, the cursor will be positioned at the correct point in the relevant file.

Cure:

The timing error can be corrected by using the Validator's text editor to change the line with the error from:

<audio src="7.mp3" clip-begin="npt=83.856s" clip-end="npt=91.185s"

to:

<audio src="7.mp3" clip-begin="npt=83.856s" clip-end="npt=89.260s"

Then save the edited file.

Note:The same process can be used for all timing errors.

Example 7

This error was reported by the Validator following editing with one of the DAISY production tools:

bbcw00d2.smil
Automation Error. The object invoked has disconnected from its clients.

 

The file bbcw00d2.smil was then validated, with the following result:

Error: Document malformed @ bbcw00d2.smil [1:2]

: the document is not well-formed, Illegal qualified name character.

Diagnosis:

The Validator is pointing to the beginning of the file where there are 5 unnecessary and invalid closing tags.

</seq>
</par>
</seq>
</body>
</smil>
<?xml version="1.0" encoding="windows-1252"?>
<!DOCTYPE smil PUBLIC "-//W3C//DTD SMIL 1.0//EN" "http://www.w3.org/TR/REC-smil/SMIL10.dtd">
<smil>
<head>
<meta name="ncc:generator" content="LpStudioGen 1.6" />
<meta name="dc:format" content="DAISY 2.02" />
<meta name="title" content="2" />

Cure:

The 5 invalid closing tags at the top of the file have to be deleted. The very first line in the file must be the xml version statement, for example:

<?xml version="1.0" encoding="windows-1252"?>

or

<?xml version="1.0" encoding="iso-8859-1"?>

After editing, the file should, as in all instances where a file has been changed, be saved.

DAISYpedia Categories: 


This page was last edited by LLeith on Monday, August 9, 2010 14:53
Text is available under the terms of the DAISY Consortium Intellectual Property Policy, Licensing, and Working Group Process.