Attachment J3 - Specification 1204.pdf

Background

The National Library Service for the Blind and Physically Handicapped (NLS), Library of Congress, administers a free library service to eligible residents of the United States and American citizens living abroad who cannot hold, handle, or read standard print media because of a temporary or permanent visual or physical limitation.

Using federal funds, NLS annually publishes approximately two thousand books and seventy magazines in audio and braille formats. Titles are selected to appeal to a wide variety of interests. Books and magazines are narrated and duplicated to a high professional standard. The number of copies produced of any title is dependent on anticipated reader demand.

Playback machines and their accessories are designed to facilitate convenient use by blind and physically handicapped people, provide maximum reliability under environmental conditions that are sometimes harsh, and survive handling that may be technically unsophisticated or inadvertently abusive. The equipment plays program materials in a special format compatible with NLS machines. All materials and equipment in the program can be sent to users and returned to libraries postage free.

A cooperating network of fifty-seven regional libraries and seventy-five subregional libraries circulates recorded and braille materials to a readership of some seven hundred thousand adults and children out of a potential eligible population of three million. Magazine subscriptions are provided on a direct-mail basis from the producers. Users must generally deal with service centers in distant cities and communicate by mail, e-mail, or phone with little or no personal contact. All materials come and go through a mail-order system. Fifty percent of the users are more than sixty-four years old and depend on the NLS program for their major source of entertainment and their connection with the print world; ninety-five percent read recorded materials, five per cent read braille.

Users are informed about new books, magazines, and services through two bimonthly publications, annual catalogs, web-based catalogs, and subject bibliographies produced by NLS, as well as various publications produced and circulated by the regional and subregional libraries.

User Materials

Contractors who consider submission of a bid to produce books, equipment, or other program products should be cognizant of the consumer-responsive nature of the program, and that the specifications for these products have been developed to meet the special need of readers in the program. Materials are produced with those needs foremost in mind and improved through constant monitoring and consumer input. Contractors are expected to familiarize themselves with the equipment-handling practices of blind and physically handicapped clientele and ensure that the equipment they produce will stand up under this type of use. A high degree of quality workmanship and product reliability is mandated by the product specification.

NLS

Specification #1204:2007

April 2007-i-

Table of Contents Page

Introduction

1. Scope

2. Reference Documents

3. Requirements

3.1 Delivery Medium

3.1.1 Conformance with Specification 1202

3.1.2 Multiple CD-Rs

3.1.2.1 Media Change Messages

3.2 Files

3.2.1 General

3.2.1.1 DTB-Specific Audio Files

3.2.1.2 File Names

3.2.1.3 Unique Identifier (UID)

3.2.2 Audio Files

3.2.2.1 Uncompressed Master WAV Files

3.2.2.2 Compression

3.2.2.3 Time Offset

3.2.2.4 Sound Quality

3.2.2.5 Source

3.2.3 SMIL Synchronization File

3.2.3.1 SMIL Validity

3.2.3.2 SMIL Audio Clips

3.2.3.3 SMIL Metadata

3.2.3.4 SMIL Granularity

3.2.3.5 Escapable Structures

3.2.3.6 Skippable Structures

3.2.3.7 Tables and Lists

3.2.3.8 Links

3.2.3.9 SMIL Structure

3.2.3.10 Segments

3.2.4 Navigation Control File (NCX)

3.2.4.1 NCX Validity

3.2.4.2 Audio Heading Clips

3.2.4.3 navLabel Content

3.2.4.4 docTitle

3.2.4.5 NCX Metadata

3.2.4.6 NavPoints

3.2.4.7 NavLists

April 2007-ii-

3.2.5 Package File (OPF)

3.2.5.1 OPF Validity

3.2.5.2 OPF Metadata

3.2.5.3 OPF Manifest

3.2.5.4 OPF Spine

3.2.5.5 Tours and Guides

3.2.6 distInfo File

3.2.6.1 distInfo Validity

3.2.7 Textual Content File

3.2.7.1 Textual Content File Validity

3.2.8 Resource File

3.2.8.1 Resource Validity

3.2.9 Checksum File

3.2.10 Complete DTB

3.2.10.1 Files to Include and Their Conformance

3.2.10.2 Files to Include on Each DTB CD-R

3.3 Production Tools

3.3.1 Audio Compression

3.3.1.1 Audio Encoder

3.3.1.2 Audio Encoder Parameters

3.3.1.3 Audio File Format

3.3.2 Parser

3.3.3 Other Validation Tools

Quality Assurance Provisions

4.1 Classification of Inspections

4.2 Responsibility for Inspections

4.2.1 Responsibility for Compliance

4.2.2 Test Records

4.3 Qualification Inspection

4.3.1 Qualification Samples

4.3.1.1 CD-R

4.3.1.2 Audio Encoder

4.3.1.3 Parser

4.3.1.4 Other Validation Tools

4.3.1.5 Complete DTB

4.3.2 Inspections

4.3.3 Quality Procedures

4.4 Incoming Inspection

4.4.1 Inspections

4.5 Acceptance Inspection

April 2007-iii-

4.5.1 Contractor's Acceptance Inspection

4.5.2 NLS Acceptance Inspection

4.6 Methods of Inspection

4.6.1 Delivery Medium

4.6.2 Multiple CD-Rs

4.6.3 File names

4.6.4 Unique Identifier (UID)

4.6.5 Audio Files

4.6.5.1 Compression

4.6.5.2 Time Offset

4.6.5.3 Sound Quality

4.6.5.4 Source

4.6.6 SMIL File

4.6.6.1 Validity

4.6.6.2 SMIL Pauses

4.6.6.3 SMIL Metadata

4.6.6.4 SMIL Granularity

4.6.6.5 Escapable Structures

4.6.6.6 Skippable Structures

4.6.6.7 Tables and Lists

4.6.6.8 Links

4.6.6.9 Announcements for DTB Magazine

4.6.6.10 SMIL Structure

4.6.6.11 Segments

4.6.7 NCX File

4.6.7.1 Validity

4.6.7.2 Audio Heading Clips

4.6.7.3 navLabel Content

4.6.7.4 docTitle

4.6.7.5 NCX Metadata

4.6.7.6 NCX Nesting

4.6.7.7 Class Attributes on NavPoints

4.6.7.8 pageRefs

4.6.7.9 NavLists

4.6.8 OPF File

4.6.8.1 Validity

4.6.8.2 OPF Metadata

4.6.8.3 OPF Manifest

4.6.8.4 OPF Spine

4.6.9 distInfo File

4.6.9.1 Validity

April 2007-iv-

4.6.10 Textual Content File

4.6.10.1 Validity

4.6.11 Resource File

4.6.11.1 Validity

4.6.12 Complete DTB

4.6.12.1 Conformance of Files

4.6.12.2 Included Files

4.6.13 Audio Encoder

4.6.14 Parser

4.6.15 Other Validation Tools

4.6.16 Checksum File

5. Labeling and Packaging

5.1 Labeling

5.1.1 Label on the Disc

5.1.2 Paper Label

5.1.3 Label Information

5.2 Packaging

5.2.1 Disc Storage Box

5.2.2 Label on Disc Storage Box

5.2.3 Packaging Disc Storage Boxes for Shipment

April 2007- -1

Introduction

This specification defines requirements for the set of files making up an audio magazine in digital talking book (DTB) format produced for the National Library Service for the Blind and Physically Handicapped (NLS), Library of Congress. These files consist of the compressed audio files, plus other files defined by ANSI/NISO Z39.86-2002.

1. Scope

This document describes the requirements for the set of files that comprise a complete audio magazine in the Digital Talking Book (DTB) format compliant with ANSI/NISO Z39.86-2002.

2. Reference Documents

The versions of the following documents in effect on the date a contract is awarded shall form a part of this specification. In the event of conflict between the publications referenced herein and the content of this specification, this specification shall be considered a superseding requirement.

2.1 American National Standards Institute (ANSI)

ANSI/NISO Z39.86-2002

Specifications for the Digital Talking Book

The document cited above is available from:

American National Standards Institute, Inc.

11 West 42nd Street New York, NY 10036

Or from:

http://www.niso.org/standards/resources/Z39-86-2002.html

2.2 National Library Service for the Blind and Physically Handicapped

NLS Specification 304 Requirements for narration and copies of cassette magazines

NLS Specification 1202 Requirements for Distribution Source Files, Review Copies, and Blank Recordable Compact Disc

April 2007- -2

The documents cited above are available from:

National Library Service for the Blind & Physically Handicapped Library of Congress 1291 Taylor Street., NW Washington, DC 20542

Or from:

http://www.loc.gov/nls/specs/

2.3 European Telecommunications Standards Institute

Extended Adaptive Multi-rate- Wideband (AMR-WB+) codec;

Transcoding functions ETSI TS 126 290 release 6 / 3GPP TS 26.290 release 6

The document cited above is available from:

http://www.3gpp.org/ftp/Specs/html-info/26290.htm

Transparent end-to-end packet switched streaming service; 3GPP file format (3GP) ETSI TS 126 244 release 7 / 3GPP TS 26.244 release 7

The document cited above is available from:

http://www.3gpp.org/ftp/Specs/html-info/26244.htm

2.4 Internet Engineering Task Force Network Working Group

The MD5 Message-Digest Algorithm (RFC 1321, April 1992)

The document cited above is available from:

http://www.ietf.org/rfc/rfc1321.txt

2.5 International Standards Organization

ISO 8601 Numeric Representation of Date and Time The document cited above is available from:

http://www.iso.org/iso/en/prods-services/popstds/datesandtime.html

April 2007- -3

3. Requirements

3.1 Delivery Medium

3.1.1 Conformance with Specification 1202

The CD-R(s) on which DTB magazines are delivered shall conform to all applicable requirements of NLS Specification 1202.

3.1.2 Multiple CD-Rs

A DTB magazine whose size exceeds 250 million bytes shall be delivered on multiple CD-Rs that conform to the requirements of sections 7.4.4, 8.4.2, and 11.2 of ANSI/NISO Z39.86-2002.

3.1.2.1 Media Change Messages

The contractor shall provide each required media change message in separate audio files. Each message shall be “insert cartridge n” where “n” is the number of the media unit to be inserted.

3.2 Files

3.2.1 General

The DTB files are defined by ANSI/NISO Z39.86-2002.

3.2.1.1 DTB-Specific Audio Files

3.2.1.1.1 File of Heading Clips

The file containing the audio clips of the NCX docTitle and audio navlabels for navPoints and navTargets shall be named name_datehdgs.xxx, where name_date is the name and issue date of the magazine (see 3.2.1.2, File Names) and xxx is the file extension (e.g., u-s-news_2006-08-08hdgs.3gp).

All alphabetic characters shall be in lower case.

April 2007- -4

3.2.1.1.2 DTB Magazine Announcement File Naming

The audio file containing the opening announcements for the DTB magazine shall be named name_dateann.xxx where name_date is the name and issue date of the magazine (see 3.3.1.2, File Names) and xxx is the file extension (e.g., u-s-news_2006-08-08ann.3gp). All alphabetic characters shall be in lower case.

3.2.1.1.3 Announcements

Only the announcements described in this section shall be presented during playback of the DTB.

3.2.1.1.3.1 DTB Beginning Announcements (Except

Children's Magazines)

The contractor shall record the following beginning announcements for use with the DTB, for all titles:

a. Title of the magazine as printed on the title page

b. Date of issue (include volume number and issue number in professional journals such as Foreign Affairs)

c. "Copyright (date and holder or holders)."

d. "Read by (name of narrator or narrators)" Give all names of narrators in order of appearance.

e. "This magazine contains (number) pages.”, “Approximate reading time: ____ hours, ____ minutes.” ( Rounded to the nearest five minutes, accurate to within +/-fifteen minutes of the value of “dtb:totalTime.” See 3.2.5.2.1, Metadata

April 2007- -5

Content.)

f. Announcements regarding navigation features: content to be determined by the producer in cooperation with NLS.

g. The appropriate announcements shall be used for the following situations:

When only advertising has been omitted:

"This recorded edition contains the entire text of the print edition, except for advertising."

When NLS provides special instructions to also omit other items: "This recorded edition contains the entire text of the print edition except for advertising and (name of item, or items) omitted by instruction of the National Library Service for the Blind and Physically Handicapped."

h. "This magazine was produced for the National Library Service for the Blind and Physically Handicapped, Library of Congress.”

i. Table of contents

The table of contents shall be recorded at this point in the sequence of announcements, regardless of its location in the print edition.

The spoken table of contents shall list articles in the order of their appearance in the body of the magazine, regardless of the order of their appearance in the written table of contents. The spoken table of contents shall give the name of each article, the number of the page on which that article appears, and its approximate reading time in minutes to the nearest minute, with

April 2007- -6 minimum duration of one minute (e.g., "Paris in the Fall, page 73, 15 minutes").

If no heading is found in the print magazine for the table of contents, the heading “Contents” shall be inserted.

3.2.1.1.3.2 Duration of Articles

At the beginning of each article or section (e.g., Letters to the Editor), following the title and author, if present, insert the approximate reading time in minutes to the nearest minute, with minimum duration of one minute as follows:

"Reading time minutes."

3.2.1.1.3.3 Ending Announcements (Except Children's

magazines)

The following announcements shall be recorded at the end of the text, in the order stated:

a. "End of (title of the magazine), for (date of issue)"

b. "Recorded in the studios of (name of studios), for the Library of Congress, (month and year)."

c. "Published by: (Publisher's name and address as it appears in the print edition).

Further reproduction or distribution in other than a specialized format is prohibited."

d. “If you experienced any difficulty with this magazine, please specify the problem on a postcard or letter addressed to: Materials Development Division, National Library

April 2007- -7

Service for the Blind and Physically Handicapped, Washington, DC 20542 or send an e-mail message to QAS@loc.gov.

3.2.1.1.3.4 DTB Beginning Announcements (Children's

magazines)

The following announcements shall be recorded at the beginning of the magazine in the order stated:

a. Title of the magazine as printed on the title page

b. Date of issue

c. "Copyright (date and holder or holders)"

d. "Read by (name of narrator or narrators)" Give all names of narrators in order of appearance.

e. "This magazine contains (number) pages."

“Approximate reading time: ____ minutes.”

(Rounded to the nearest minute, accurate to within +/- five minutes of the value of “dtb:totalTime.” See 3.2.5.2.1, Metadata Content.)

f. Announcements regarding navigation features: content to be determined by the producer in cooperation with NLS.

g. The appropriate announcements shall be used for the following situations:

When only advertising has been omitted:

"This recorded edition contains the entire text of the print edition, except for advertising."

April 2007- -8

When NLS provides special instructions to also omit other items: "This recorded edition contains the entire text of the print edition except for advertising and (name of item, or items) omitted by instruction of the National Library Service for the Blind and Physically Handicapped."

h. Table of contents

The table of contents shall be recorded at this point in the sequence of beginning announcements, regardless of its location in the print edition.

The spoken table of contents shall list articles in the order of their appearance in the body of the magazine, regardless of the order of their appearance in the written table of contents. The spoken table of contents shall give the name of each article, the number of the page on which that article appears, and its approximate reading time in minutes to the nearest minute, with minimum duration of one minute (e.g., "Paris in the Fall, page 73, 15 minutes").

If no heading is found in the print magazine for the table of contents, the heading “Contents” shall be inserted.

3.2.1.1.3.5 Duration of Articles

At the beginning of each article or section (e.g., Letters to the Editor), following the title and author, if present, insert the approximate reading time in minutes to the nearest minute, with minimum duration of one minute as follows:

"Reading time minutes."

April 2007- -9

3.2.1.1.3.6 Ending Announcements, Magazines

for Children

The following announcements shall be recorded at the end of the text, in the order stated:

a. "End of (title of magazine) for (date of issue)"

b. "Recorded in the studios of (name of studios), for the Library of Congress, (month and year)."

c. "Published by: (Publisher's name and address as it appears in the print edition).

Further reproduction or distribution in other than a specialized format is prohibited."

d. “If you experienced any difficulty with this magazine, please specify the problem on a postcard or letter addressed to: Materials Development Division, National Library Service for the Blind and Physically Handicapped, Washington, DC 20542 or send an e-mail message to QAS@loc.gov.

3.2.1.2 File Names

a. All alphabetic characters shall be in lower case.

b. The base filename of the magazine shall consist of the magazine name and the issue date in the following format: "name_YYYY- MM[-DD]". The name component shall be supplied by NLS.

When an issue date contains a span of dates (e.g. US News, August 8-15, 2003) only the first date in the span shall be included in the filename: (e.g., u-s-news_2003-08-08). Month and day figures shall include leading zeroes if needed to make up the two-character requirement.

April 2007- -10

c. SMIL files, where a DTB contains more than one, and all audio files with the exception of the media change message, announcement and headings files, shall have a sequence indicator consisting of a hyphen and four digits (including any leading zeroes needed to meet the four-digit requirement) appended to the magazine name in the file name. The range of sequence indicators shall begin with -0001 (e.g., smart-computing_2004-03-0001.3gp), and the sequence shall be continuous. For audio files holding the content of the DTB, the last two digits of the sequence indicator shall equal the two-digit side number for the corresponding WAV file. Any other audio files present in the DTB (other than the media change message, announcement and headings files, whose file names are prescribed) shall be assigned sequence indicators commencing after the number of the final audio content file.

d. Media change message files (see 3.1.2.1) shall be named “insertn.3gp” where “n” is the number of the cartridge to be inserted.

e. The name of the file containing MD5 checksums shall be the magazine name concatenated with the suffix “dtb.md5”, e.g., “smart-computing_2004-03dtb.md5”. For DTBs spanning multiple media units, section 3.2.1.2c notwithstanding, a sequence indicator consisting of a hyphen and two digits shall be inserted before the filename extension.(e.g., “smart-computing_2004-03dtb-01.md5”).

3.2.1.3 Unique Identifier (UID)

The UID shall consist of the lower-case character string "us-nls-dm-xxxx" where “xxxx”is the base filename (e.g. us-nls-dm-people_2004-03-29)

3.2.2 Audio Files

3.2.2.1 Uncompressed Master WAV Files

The following describes the requirements for the original audio source files from which the compressed 3gp files are created.

April 2007- -11

a. Each file shall be linear PCM data in WAV file format.

For the complete definition of the .WAV file format see:

Waveform - Audio File Format, "Multimedia Programming Interface and Data Specification v1.0" as issued by IBM and Microsoft, 1991. The Web address for this reference is:

http://www.cwi.nl/ftp/audio/RIFF-format

b. Each file shall be written at a sampling frequency of 44.1 ksps, and a bit depth of 16 bits per sample, with dither, and block alignment =2.

c. The average RMS signal level for the spoken text shall be not less than -24 dB FS, nor greater than -18 dB FS.

d. The background noise level shall not exceed -72 dB FS A-weighted. Background noise includes both acoustical and electrical noise. Noise gate processing is not permitted.

e. The master audio files shall be of good subjective sound quality.

f. Conversion of analog recordings to digital format is not permitted under this specification.

3.2.2.2 Compression

All DTB audio files shall be compressed with an audio encoder conforming with the requirements of section 3.3.1 and using NLS-approved settings for bitrate and other parameters. The compressed audio files shall be encoded monaurally at a constant bitrate.

3.2.2.3 Time Offset

The clipEnd time for each audio fragment shall be placed no closer than 200ms following the end of the narration of that fragment.

It is anticipated that there will be a time offset of 50 to 80 milliseconds between the uncompressed and compressed/ decompressed audio files. The timing references for all clipBegin

April 2007- -12 and clipEnd attributes on audio elements in the SMIL, NCX, Distinfo and resource files are to be relative to the original uncompressed WAV file. In determining the correct times for the start and end of audio clips, producers should assume that the time offset will be compensated for by the player, but these times can have an uncertainty of plus or minus 30 milliseconds when played.

3.2.2.4 Sound Quality

Compressed audio files shall be of acceptable subjective sound quality.

3.2.2.5 Source

The source for each compressed file shall be identical to the master WAV file or DTB-specific WAV file.

3.2.3 SMIL Synchronization File

The SMIL file(s) shall conform to the normative requirements of section 7 of ANSI/NISO Z39.86-2002.

3.2.3.1 SMIL Validity

The SMIL file(s) shall be well-formed and valid to the DTB-specific SMIL DTD of Appendix 2 of ANSI/NISO Z39.86- 2002.

3.2.3.2 SMIL Audio Clips

3.2.3.2.1 clipBegin and clipEnd Required

In all SMIL audio elements, both clipBegin and clipEnd must be present and valued.

3.2.3.2.2 SMIL Pauses

The clipBegin time for each audio fragment shall be placed not more than 100 milliseconds before the beginning of narration of that fragment. The clipEnd time shall be placed so as to preserve the

April 2007- -13 pause that follows the end of the narration of that fragment. (See also section 3.2.2.3.)

3.2.3.3 SMIL Metadata

SMIL metadata shall conform to the requirements of section 7.5 of ANSI/NISO Z39.86-2002, and the element “dtb:generator” shall be completed by the contractor.

3.2.3.4 SMIL Granularity

If a textual content file is required by NLS, SMIL file(s) shall have a level of granularity matching that of the textual content file as recommended by section 7.2 of ANSI/NISO Z39.86-2002.

3.2.3.5 Escapable Structures

If NLS requires any structures to be escapable, the SMIL file(s) shall conform to the normative requirements of section 7.4.1 of

ANSI/NISO Z39.86-2002.

3.2.3.6 Skippable Structures

If NLS requires any structures to be skippable, the SMIL file(s) shall conform to the normative requirements of section 7.4.3 of

ANSI/NISO Z39.86-2002.

3.2.3.6.1 defaultState Values

Unless otherwise specified by NLS, the value of defaultState shall be set to “true” for all skippable structures. The value of the defaultState for a given customTest element must be the same in all SMIL files for a DTB.

3.2.3.7 Tables and Lists

If NLS requires tables and/or lists to allow special navigation modes, the SMIL file(s) shall conform to the normative requirements of section 7.4.2 of ANSI/NISO Z39.86-2002.

April 2007- -14

3.2.3.8 Links

If NLS requires links, the SMIL file(s) shall conform to the normative requirements of section 7.4.5 of ANSI/NISO Z39.86- 2002.

3.2.3.9 SMIL Structure

At a minimum, one <par> (see ANSI/NISO Z39.86-2002, section

7.3 for definition) shall be included for each structural element in the magazine for which an NCX entry has been created.

3.2.3.10 Segments

A segment is a short section of text such as a paragraph, list item, table row, etc.; it has no heading and is not part of the hierarchical structure of the magazine. When required by NLS, specified segments shall be represented by <par>s or <seq>s in the SMIL file(s).

3.2.3.11 SMIL File Size

SMIL files exceeding 100 kilobytes must be divided into multiple SMIL files.

3.2.4 Navigation Control File (NCX)

The NCX file shall conform to the normative requirements of section 8 of

ANSI/NISO Z39.86-2002.

3.2.4.1 NCX Validity

The NCX file shall be well-formed and valid to the NCX DTD of Appendix 3 of ANSI/NISO Z39.86-2002.

Non-ASCII characters in all <text> elements shall be represented as numeric character references or as UTF-8 multi-byte sequences.

April 2007- -15

3.2.4.2 Audio Heading Clips

The set of audio clips of the docTitle and NCX headings shall be collected in a single, separate file that shall be compressed and shall be included on each CD-R.

3.2.4.2.1 clipBegin Timing

The clipBegin time for each audio clip shall be not more than 100 milliseconds before the beginning of narration in that clip. (See section 3.2.2.3).

3.2.4.2.2 clipBegin and clipEnd Required

In all audio elements, both clipBegin and clipEnd must be present and valued.

3.2.4.3 navLabel Content

3.2.4.3.1 navLabel Content for navPoints

Each navLabel within a navPoint shall contain both text and audio elements. The audio element shall contain a pointer to an audio clip of the heading of the navigable section of the magazine referenced by its parent navPoint. The audio clip shall be contained in the Audio Heading Clip file described in section 3.2.4.2. The audio and text content shall match the print headings found in the body of the magazine, rather than the table of contents. Line breaks and font information cannot appear in the text element. However their intent should be captured, if possible, using punctuation.

3.2.4.3.2 navLabel Content for navTargets

Each navLabel within a navTarget shall contain both text and audio elements. The audio element shall contain a pointer to an audio clip as follows:

April 2007- -16

a. For note references (noterefs), the audio clip shall contain the identifier (e.g. “note” or “footnote”) followed by the reference number. If the reference is a symbol, the audio clip shall contain only the identifier.

b. For page numbers (pagenums), the audio clip shall contain the identifier “page” followed by the page number. For special page numbers, the audio clip shall contain the identifier followed by the number as it appears in the print book, e.g., “page roman four” for iv, “page A one” for A-1.

c. For line numbers (linenums), the audio clip shall contain the identifier "line" followed by the line number.

The audio clip shall be contained in the Audio Heading Clip file described in section 3.2.4.2.

The text element shall contain only the appropriate number without the identifier “note”, “page” or “line,” except for noterefs indicated only by a symbol, for which it shall contain an asterisk. The text for special page numbers shall match the print book.

3.2.4.3.3 Title and Issue Date

The contractor shall include a navPoint for the beginning of the magazine. Its navLabel shall contain the title and issue date of the magazine. The class attribute shall be “title”.

3.2.4.3.4 Table of Contents

The contractor shall include a navPoint for the table of contents. If no heading is found in the print magazine for the table of contents, the navLabel “Contents” shall be inserted. The class attribute shall be “contents”.

April 2007- -17

3.2.4.3.5 Ending Announcements

The contractor shall include a navPoint for the ending announcements, with the navLabel content being "End of (magazine title and issue date)". The class attribute shall be “close”.

3.2.4.3.6 Absence of print headings

For segments of the magazine that are to be made navigable via the NCX but which lack a heading in the print edition, the contractor shall contact NLS for guidance on how to proceed.

3.2.4.4 docTitle

The docTitle element shall contain an audio element containing a pointer to an audio clip of the magazine’s title and date of issue, and a text element containing the magazine’s title and date of issue. The audio clip shall be contained in the Audio Heading Clip file described in section 3.2.4.2.

3.2.4.5 NCX Metadata

NCX metadata shall conform to the requirements of section 8.4.1 of ANSI/NISO Z39.86-2002, and the element “dtb:generator” shall be completed by the contractor.

3.2.4.6 NavPoints

3.2.4.6.1 NCX Nesting

When multiple levels of structures are included in the NCX, those levels must be reflected in properly nested navPoints.

3.2.4.6.2 Class Attribute on navPoints

Each navPoint shall have a class attribute drawn exactly from Table IV, corresponding as closely as possible to the type of magazine structure marked

April 2007- -18 by the navPoint. If no term listed in the table is appropriate, a descriptive UTF-8 compliant single-word term shall, with the concurrence of the NLS Quality Assurance Section, be used.

3.2.4.6.3 pageRefs

Each navPoint beginning on a page whose number is included in a navList of page numbers shall contain a pageRef attribute.

3.2.4.7 NavLists

If NLS requires that any of the magazine structures listed below be made separately navigable in the SMIL file(s), a navList is required for each, conforming to the normative requirements of

ANSI/NISO Z39.86-2002.

note reference (noteref) page number (pagenum) line number (linenum)

Each navList element shall have a class attribute describing the magazine structures it contains; the class attribute shall be the DTBook element name included in parentheses in the list above.

For each navTarget, the navLabel audio and text content shall be as specified in section 3.2.4.3; and the content element shall point to the SMIL time container that contains the footnote reference, page number or line number.

navLists are not required for other magazine structures, and are forbidden for segments.

3.2.4.7.1 Value Attribute

Each navTarget whose navLabel text element consists of an integer shall include a value attribute.

The value attribute shall contain an arabic integer

April 2007- -19 corresponding to the navTarget's text element value.

navTargets for frontmatter pages with roman numbers and for pages with compound numbers (e.g., A-15) shall not include a value attribute.

navTargets for page ranges (e.g., 25-26) shall have a value attribute equal to the first page number of the range. Note references and line numbers shall be repeated as necessary. Gaps in the sequence of values are acceptable, for example if only explanatory notes are read.

3.2.5 Package File (OPF)

The OPF file shall conform to the normative requirements of section 3 of

ANSI/NISO Z39.86-2002.

3.2.5.1 OPF Validity

The OPF file shall be well-formed and valid to the Open eBook Forum (OEBF) Publication Structure 1.0.1 package DTD referenced by section 3 of ANSI/NISO Z39.86-2002.

3.2.5.2 OPF Metadata

The OPF metadata shall be completed by the contractor. The element “nls:recordingAgency” shall be included in the OPF x-metadata.

3.2.5.2.1 Metadata Content

The contractor shall include the following metadata items:

dc:Title - Title and issue date as they appear on the cover of the print magazine, except that the date is to be placed within parentheses. i.e.-Smart Computing (December 2006).

The “dc:Date” element shall contain the year and month of “dtb:revisionDate” in the format “yyyy-mm”.

April 2007- -20 dc:Publisher – “National Library Service for the Blind and Physically Handicapped, Library of Congress”.

dc:Format – “ANSI/NISO Z39.86-2002" dc:Identifier – Magazine uid. See Section 3.2.1.3 for format.

dc:Source – The ISSN number of the print magazine (e.g.- 1093-4170). If the dtb magazine is a composite of several print magazines, dc:Source may be repeated to contain the ISSNs of all included magazines.

dc:Language – “en” for English, “es” for Spanish, “de” for German, and “fr” for French abbreviations.

dc:Rights – “Further reproduction or distribution in other than a specialized format is prohibited.”

dtb:sourceDate - Date of publication of the print magazine from which the DTB is derived. In the format of YYYY-MM-[DD] with a mandatory year and 2-digit month. The two digit day should be included, if applicable. For magazines where the cover date is not a specific date (e.g. - Summer, 2007), the producer shall, in consultation with the NLS Quality Assurance Section create a numeric date string consistent with the cover date and unique to that magazine.

dtb:sourcePublisher - Publisher of the print magazine (e.g.-Time, Inc.). If the DTB magazine is a composite of several print magazines, dtb:sourcePublisher may be repeated.

dtb:sourceRights- Copyright information for the print magazine (e.g.-2006 by Time, Inc.). If the DTB magazine is a composite of several print magazines, dtb:sourceRights may be repeated.

April 2007- -21 dtb:multimediaType - “audioNCX”

The “dtb:producedDate” element shall contain the date of the first build of the DTB in the format “yyyy-mm-dd” and shall not be changed.

The “dtb:revision” element shall contain a non-negative integer. For the first build, the revision shall be “0,” and the revision shall be incremented for each subsequent build.

The “dtb:revisionDate” element shall contain the date of the most recent revision of the DTB in the format “yyyy-mm-dd” and shall equal “dtb:producedDate” for revision “0.”

The “dtb:revisionDescription” element shall contain a text string describing the reason for the revision;

“dtb:revisionDescription” shall be present and valued for all revisions greater than “0,” and shall not be present for revision “0.”

The “dtb:narrator” element shall be entered last name first (e.g., Smith, John). The “dtb:narrator” element shall contain only one narrator; the element shall be repeated if there are multiple narrators.

dtb:producer - Full name of the organization that created the DTB.

dtb:audioFormat - “3gpp”

The “nls:recordingAgency” element shall contain the full name of the agency that made the original recording from which the DTB was created.

The “dtb:totalTime” element shall contain the total playing time of the DTB, i.e., the sum of the durations of all the audio elements of the SMIL files governing the playback of the magazine. For <seq>s and <par>s whose <customTest> elements

April 2007- -22 have been set to defaultState=“false,” audio referenced by these SMIL nodes shall be counted toward “dtb:totalTime” as if the defaultState had been set to “true.” This time value shall be accurate to within plus or minus 1 second.

Non-ASCII characters in all <metadata> element content shall be represented as numeric character references or as UTF-8 multi-byte sequences.

3.2.5.3 OPF Manifest

The manifest shall conform to the normative requirements of section 3.3 of ANSI/NISO Z39.86-2002.

3.2.5.4 OPF Spine

The spine shall conform to the normative requirements of section

3.4 of ANSI/NISO Z39.86-2002.

3.2.5.5 Tours and Guides

No tours or guides shall be included.

3.2.6 distInfo Files

If distInfo files are required, they shall conform to the normative requirements of section 11 of ANSI/NISO Z39.86-2002.

3.2.6.1 distInfo Validity

The distInfo file shall be well-formed and valid to the Distribution Information DTD of Appendix 6 of ANSI/NISO Z39.86-2002.

3.2.7 Textual Content File

If a textual content file is required by NLS, it shall conform to the normative requirements of section 4 of ANSI/NISO Z39.86-2002.

April 2007- -23

3.2.7.1 Textual Content File Validity

The textual content file shall be well-formed and valid to the DTBook DTD of Appendix 1 of ANSI/NISO Z39.86-2002.

3.2.8 Resource File

If a resource file is required by NLS, it shall conform to the normative requirements of section 10 of ANSI/NISO Z39.86-2002.

3.2.8.1 Resource Validity

The resource file shall be well-formed and valid to the Resource DTD of Appendix 5 of ANSI/NISO Z39.86-2002.

3.2.9 Checksum File

A checksum file shall be present on each CD-R submitted to NLS. This XML file shall contain a checksum for each file on the CD-R with the exception of the checksum file itself. All the files listed in the checksum file shall be present on the CD-R. The checksum shall be calculated using the MD5 algorithm as described in the reference cited in section 2.4 and shall be in the form of thirty-two hexadecimal digits. The checksums shall be generated from the source files prior to their transfer to the CD-R(s).

This checksum file does not form part of the DTB and thus shall not be listed in the book manifest. The checksums contained in the checksum file must be identical to the checksums calculated from the source files and to those calculated from the corresponding files stored on the CD-R.

April 2007- -24

The format of the XML file is described by the following DTD, which shall be placed at the beginning of each checksum file.

<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE diskcheck [ <!ELEMENT diskcheck (book, file+)> <!ATTLIST diskcheck version CDATA #FIXED "1.0" <!ELEMENT book (#PCDATA)> <!ELEMENT file (filename, checksum)> <!ATTLIST file type CDATA #IMPLIED content CDATA #IMPLIED <!ELEMENT filename (#PCDATA)> <!ELEMENT checksum (#PCDATA)> <!ATTLIST checksum type CDATA #REQUIRED

The <book> element shall contain the UID for the DTB, as defined in section 3.2.1.3.”

The <filename> element shall contain the name of the file for which the checksum is calculated.

The “type” attribute on the <checksum> element shall contain the value “MD5.”

3.2.10 Complete DTB

3.2.10.1 Files to Include and Their Conformance

The complete DTB, consisting of all required files, shall conform to the normative requirements of ANSI/NISO Z39.86-2002 and all applicable requirements of this specification.

April 2007- -25

3.2.10.2 Files to Include on Each DTB CD-R

All document type definitions (DTDs) and entity files referenced by any DTB files or by any DTDs shall be included on each CD-R of the DTB and shall be listed in the Package File manifest.

An XML checksum file is to be generated in accordance with section 3.2.9 and included on the DTB disk.

3.3 Production Tools

3.3.1 Audio Compression

3.3.1.1 Audio Encoder

The encoder used to compress the audio files for the DTB shall be fully compliant with the standard for Extended Adaptive Multi- Rate-Wideband (AMR-WB+), ETSI TS 126 290 release 6.

3.3.1.2 Audio Encoder Parameters

The encoder parameters shall generate AMR-WB+ with a frame type of 23 and an ISR index of 8, as described in section 8.1 of the above standard.

3.3.1.3 Audio File Format

The 3GP file format shall be used to store the compressed AMR- WB+ frames. The 3gp files will be fully compliant with ETSI TS 126 244 release 7 with the following restrictions:

3.3.1.3.1 Checksum Keyword

The 3GP file shall contain a User Data, “udta” box within the Movie, “moov” box. The “udta” box shall contain a Keyword sub-box that shall contain the keyword “md5sum.cccccccccccccccccccccccccccccccc,” where cccccccccccccccccccccccccccccccc is the ASCII hexadecimal representation of the 16 byte MD5 checksum of the entire source wav file.

April 2007- -26

3.3.1.3.2 Sample Size Box Format

The Sample Size box, “stsz” contained within the Sample Table, “stbl” box of the sound track’s Media Information, “minf” box shall contain only the elements “sample_size” and “sample_count.”

“sample_size” shall be the size of, and “sample_count” the number of AMR-WB+ superframes contained within the track.

3.3.2 Parser

The parser used to validate the OPF, NCX, SMIL, distInfo, resource, and textual content files shall be a validating XML parser compliant with the applicable standard referenced by ANSI/NISO Z39.86-2002.

3.3.3 Other Validation Tools

Any other software or other tools used to validate DTB content shall be capable of detecting deviations from the requirements of ANSI/NISO Z39.86-2002.

Quality Assurance Provisions

4.1 Classification of Inspections

The inspection requirements specified herein are classified as follows:

a. Qualification Inspection -- see section 4.3.

b. Incoming Inspection -- see section 4.4.

c. Contractor's Acceptance Inspection -- see section 4.5.1.

d. NLS Acceptance Inspection -- see section 4.5.2.

April 2007- -27

4.2 Responsibility for Inspections

The contractor is responsible for the performance of the inspection requirements defined by sections 4.3, 4.4, and 4.5.1. NLS reserves the right to perform any of the inspections set forth in this specification when deemed necessary to ensure that products conform to the prescribed requirements.

4.2.1 Responsibility for Compliance

All items must meet all requirements of sections 3 and 5. The inspections set forth in this specification shall become a part of the contractor's overall inspection system or quality program. The absence of any inspection requirements in this specification shall not relieve the contractor of the responsibility of assuring that all products or supplies submitted to NLS for acceptance comply with all requirements of the contract. Sampling in quality conformance does not authorize the submission of known defective material, either indicated or actual, nor does it commit NLS to acceptance of defective material. Should NLS determine that a fault or faults are found in production units within the warranty period, then correction of the fault or faults and production inspections or controls for prevention of future occurrences shall be instituted on request by NLS without additional charge to NLS.

4.2.2 Test Records

The contractor shall maintain complete records of all inspection results for the duration of the contract.

4.3 Qualification Inspection

Qualification inspection shall be performed by the contractor and by NLS on new products and on previously qualified products that have undergone any changes in materials, manufacturing process, or software version. All proposed changes shall be reported to the NLS contracting officer in writing, with a statement by the contractor describing the changes and the impact of the changes on the delivered product. NLS reserves the right to require six weeks for the evaluation of qualification samples prior to delivery of products incorporating the changes. The foregoing requirement does not relieve the contractor of any other requirements of this specification or the contract.

April 2007- -28

4.3.1 Qualification Samples

4.3.1.1 CD-R

Qualification samples are detailed in section 4.4.1 of NLS Specification 1202.

4.3.1.2 Audio Encoder

Samples shall consist of the set of compressed audio files submitted as part of the complete DTB required by section 4.3.1.5.

4.3.1.3 Parser

The XML parser to be used and its version shall be identified; if requested, a copy shall be submitted.

4.3.1.4 Other Validation Tools

Any other validation tools to be used and their versions shall be identified; if requested, copies shall be submitted.

4.3.1.5 Complete DTB

A complete DTB shall be submitted; the WAV files, metadata, and any other required source material will be provided by NLS.

4.3.2 Inspections

Qualification inspection shall consist of the inspections listed in Table I.

4.3.3 Quality Procedures

The contractor shall submit a document describing the quality assurance procedures used to achieve the requirements of this specification. Quality procedures shall contain provisions for configuration management of all software used in the production and validation of DTBs. NLS reserves the right to require the contractor to improve quality procedures.

April 2007- -29

Table I - Qualification Inspection

Requirement Section Test Method

CD-R 3.1.1 4.6.1

Audio Compression 3.2.2.2 4.6.5.1 Time Offset 3.2.2.3 4.6.5.2 Sound Quality 3.2.2.4 4.6.5.3 Source 3.2.2.5 4.6.5.4 Complete DTB files 3.2.10 4.6.12 Audio Encoder 3.3.1.1 4.6.13 Parser 3.3.2 4.6.14 Other Validation Tools 3.3.3 4.6.15 Labeling 5.1 NLS review Packaging 5.2 NLS review

4.4 Incoming Inspection

Incoming inspection shall be performed by the contractor on CD-Rs and on source materials provided by NLS.

4.4.1 Inspections

Incoming inspection shall consist of the inspections listed in Table II.

Table II - Incoming Inspection Requirement Section Test Method

CD-R 3.1.1 4.6.1

Uncompressed Master WAV Files 3.2.2.1 3.2.2.1 OPF Metadata 3.2.5.2 4.6.8.2 Textual Content File Validity 3.2.7.1 4.6.10.1

4.5 Acceptance Inspection

4.5.1 Contractor's Acceptance Inspection

Acceptance inspection shall be performed by the contractor on 100% of every DTB and shall consist of the inspections listed in Table III.

April 2007- -30

4.5.2 NLS Acceptance Inspection

Acceptance inspection will be performed by NLS on every DTB and will consist of the inspections listed in Table III. The checksums calculated from all files on the DTB CD-R(s) will be compared to the corresponding checksums in the checksum file of the disk.

April 2007- -31

Table III - Acceptance Inspection

Requirement Section Test Method

Multiple CD-R 3.1.2 4.6.2 DTB Magazine Announcement File Name 3.2.1.1.2 4.6.3 File Names 3.2.1.2 4.6.3 Unique Identifier (UID) 3.2.1.3 4.6.4 Uncompressed Master WAV Files 3.2.2.1 3.2.2.1 Audio Compression 3.2.2.2 4.6.5.1 Time Offset 3.2.2.3 4.6.5.2 Sound Quality 3.2.2.4 4.6.5.3 SMIL Validity 3.2.3.1 4.6.6.1 SMIL Pauses 3.2.3.2.2 4.6.6.2 SMIL Metadata 3.2.3.3 4.6.6.3 SMIL Granularity 3.2.3.4 4.6.6.4 Escapable Structures 3.2.3.5 4.6.6.5 Skippable Structures 3.2.3.6 4.6.6.6 defaultState Values 3.2.3.6.1 3.2.3.6.1 Tables and Lists 3.2.3.7 4.6.6.7 Links 3.2.3.8 4.6.6.8 Announcements for DTB Magazine 3.2.1.1.3 4.6.6.9 SMIL Structure 3.2.3.9 4.6.6.10 Segments 3.2.3.10 4.6.6.11 NCX Validity 3.2.4.1 4.6.7.1 Audio Heading Clips 3.2.4.2 4.6.7.2 clipBegin Timing 3.2.4.2.1 4.6.7.2.1 navLabel Content 3.2.4.3 4.6.7.3 docTitle 3.2.4.4 4.6.7.4 NCX Metadata 3.2.4.5 4.6.7.5 NCX Nesting 3.2.4.6.1 4.6.7.6 Class Attribute on navPoints 3.2.4.6.2 4.6.7.7 pageRefs 3.2.4.6.3 4.6.7.8 NavLists 3.2.4.7 4.6.7.9 OPF Validity 3.2.5.1 4.6.8.1 OPF Metadata 3.2.5.2 4.6.8.2 OPF Manifest 3.2.5.3 4.6.8.3 OPF Spine 3.2.5.4 4.6.8.4 distInfo Validity 3.2.6.1 4.6.9.1 Textual Content File Validity 3.2.7.1 4.6.10.1 Resource File Validity 3.2.8.1 4.6.11.1 Checksum File 3.2.9 4.6.16

April 2007- -32

Table III - Acceptance Inspection (continued)

Requirement Section Test Method

Complete DTB files 3.2.10 4.6.12 Files to Include on each DTB CD-R 3.2.10.2 4.6.12.2 Audio Encoder 3.3.1.1 4.6.13 Labeling 5.1 NLS review Label Information 5.1.3 NLS review Packaging 5.2 NLS review

4.6 Methods of Inspection

4.6.1 Delivery Medium

Each CD-R shall be tested for compliance with all applicable requirements of NLS Specification 1202.

4.6.2 Multiple CD-Rs

A DTB that requires multiple discs shall have a distInfo file compliant with the requirements of section 3.2.6, a set of media-change message files compliant with the requirements of section 3.1.2.1, and the complete DTB shall conform to the requirements of section 3.2.10.

4.6.3 File names

File names shall be examined for compliance with the requirements of section 3.2.1.1.2, and 3.2.1.2.

4.6.4 Unique Identifier (UID)

UIDs shall be examined for compliance with the requirements of section 3.2.1.3.

4.6.5 Audio Files

4.6.5.1 Compression

Each compressed audio file shall be examined for compliance with the

April 2007- -33 requirements of section 3.2.2.2.

4.6.5.2 Time Offset

Each compressed audio file shall be examined for compliance with the requirements of section 3.2.2.3.

4.6.5.3 Sound Quality

The sound quality of the compressed audio files shall conform to the requirements of section 3.2.2.4 as determined by a subjective listening comparison with the original uncompressed WAV file. Acceptable sound quality shall be determined by the NLS Quality Assurance Section.

4.6.5.4 Source

Each compressed audio file shall be examined for compliance with the requirements of section 3.2.2.5.

4.6.6 SMIL File

4.6.6.1 Validity

The SMIL file(s) shall be tested for compliance with the requirements of section 3.2.3.1 using a qualified XML validating parser.

4.6.6.2 SMIL Pauses

SMIL pauses shall be examined for compliance with the requirements of section 3.2.3.2.2.

4.6.6.3 SMIL Metadata

The SMIL metadata shall be examined for compliance with the requirements of section 3.2.3.3.

4.6.6.4 SMIL Granularity

The granularity of the SMIL files shall be examined for compliance with the requirements of section 3.2.3.4.

April 2007- -34

4.6.6.5 Escapable Structures

Escapable structures shall be examined for compliance with the requirements of section 3.2.3.5.

4.6.6.6 Skippable Structures

Skippable structures shall be examined for compliance with the requirements of section 3.2.3.6.

4.6.6.7 Tables and Lists

Tables and lists shall be examined for compliance with the requirements of section 3.2.3.7.

4.6.6.8 Links

Links shall be examined for compliance with the requirements of section 3.2.3.8.

4.6.6.9 Announcements for DTB Magazine

The DTB shall be examined for compliance with the requirements of section 3.2.1.1.3.

4.6.6.10 SMIL Structure

The DTB shall be examined for compliance with the requirements of section 3.2.3.9

4.6.6.11 Segments

The DTB shall be examined for compliance with the requirements of section 3.2.3.10.

4.6.7 NCX File

4.6.7.1 Validity

The NCX file shall be tested for compliance with the requirements of section

3.2.4.1 using a qualified XML validating parser.

April 2007- -35

4.6.7.2 Audio Heading Clips

The file containing the audio clips of the NCX headings shall be examined for compliance with the requirements of section 3.2.4.2.

4.6.7.2.1 clipBegin Timing

The file containing the audio clips of the NCX headings shall be examined for compliance with the requirements of section 3.2.4.2.1.

4.6.7.3 navLabel Content

The audio content, and text content if present, of each navLabel shall be examined for compliance with the requirements of section 3.2.4.3.

4.6.7.4 docTitle

The text and audio content of docTitle shall be examined for compliance with the requirements of section 3.2.4.4.

4.6.7.5 NCX Metadata

The NCX metadata shall be examined for compliance with the requirements of section 3.2.4.5.

4.6.7.6 NCX Nesting

The NCX file shall be examined for compliance with the requirements of section 3.2.4.6.1.

4.6.7.7 Class Attributes on NavPoints

Each Class Attribute shall be examined for compliance with the requirements of section 3.2.4.6.2.

4.6.7.8 pageRefs

Each pageRef shall be examined for compliance with the requirements of section 3.2.4.6.3.

April 2007- -36

4.6.7.9 NavLists

Each NavList shall be examined for compliance with the requirements of section 3.2.4.7.

4.6.8 OPF File

4.6.8.1 Validity

The OPF file shall be tested for compliance with the requirements of section

3.2.5.1 using a qualified XML validating parser.

4.6.8.2 OPF Metadata

The OPF metadata shall be examined for compliance with the requirements of section 3.2.5.2.

4.6.8.3 OPF Manifest

The OPF manifest shall be examined for compliance with the requirements of section 3.2.5.3.

4.6.8.