National Instructional Materials Accessibility Standard, 37302-37306 [05-12853]

Download as PDF 37302 Federal Register / Vol. 70, No. 124 / Wednesday, June 29, 2005 / Proposed Rules Actions Accomplished Previously (i) Inspections and related investigative and corrective actions accomplished before the effective date of this AD, in accordance with any applicable Airbus service bulletin identified in Table 4 of this AD, are acceptable for compliance with the corresponding actions specified in this AD. TABLE 4.—SERVICE INFORMATION FOR ACTIONS ACCOMPLISHED PREVIOUSLY Airbus model A330 series airplanes. A340–200 and –300 series airplanes. Airbus service bulletin A330–28–3087, dated July 24, 2003. A330–28–3089, Revision 01, dated May 12, 2004. A340–28–4100, dated July 24, 2003. A340–28–5010, dated May 7, 2004. A340–28–5021, dated April 6, 2005. No Submission of Information/Parts (j) Where any Airbus service bulletin specifies to submit information to Airbus, or send removed float valves to either ArgoTech or Intertechnique, those actions are not required by this AD. Alternative Methods of Compliance (AMOCs) (k) The Manager, International Branch, ANM–116, Transport Airplane Directorate, FAA, has the authority to approve AMOCs for this AD, if requested in accordance with the procedures found in 14 CFR 39.19. Related Information (l) French airworthiness directives F– 2005–003, dated January 5, 2005, and F– 2005–004 R1 and F–2005–005 R1, both dated April 27, 2005, also address the subject of this AD. Issued in Renton, Washington, on June 22, 2005. Ali Bahrami, Manager, Transport Airplane Directorate, Aircraft Certification Service. [FR Doc. 05–12839 Filed 6–28–05; 8:45 am] BILLING CODE 4910–13–P required under sections 612(a)(23)(A) and 674(e)(4) of the Individuals with Disabilities Education Act, as amended by the Individuals with Disabilities Education Improvement Act of 2004 (Act). The purpose of the NIMAS is to help increase the availability and timely delivery of print instructional materials in accessible formats to blind or other persons with print disabilities in elementary schools and secondary schools. We must receive your comments on or before September 12, 2005. ADDRESSES: Address all comments about this proposed standard to Troy Justesen, Office of Special Education and Rehabilitative Services, U.S. Department of Education, 400 Maryland Avenue, SW., room 5126, Potomac Center Plaza, Washington, DC 20202–2641. If you prefer to send your comments through the Internet, you may address them to us at the U.S. Government Web site: http://www.regulations.gov. Or you may send your Internet comments to us at the following address: Osersnimascomments@ed.gov. You must include the term ‘‘NIMAS Comments’’ in the subject line of your electronic message. Please submit your comments only one time in order to ensure that we do not receive duplicate copies. FOR FURTHER INFORMATION CONTACT: Troy R. Justesen. Telephone: (202) 245–7468. If you use a telecommunications device for the deaf (TDD), you may call the Federal Relay Service (FRS) at 1– 800–877–8339. Individuals with disabilities may obtain this document in an alternative format (e.g., Braille, large print, audiotape, or computer diskette) on request to the contact person listed under FOR FURTHER INFORMATION CONTACT. DATES: SUPPLEMENTARY INFORMATION: Invitation to Comment DEPARTMENT OF EDUCATION 34 CFR Part 300 RIN 1820–AB56 National Instructional Materials Accessibility Standard Office of Special Education and Rehabilitative Services, Department of Education. ACTION: Notice of proposed rulemaking. AGENCY: SUMMARY: The Secretary of Education proposes to establish the National Instructional Materials Accessibility Standard (NIMAS or standard) as VerDate jul<14>2003 15:26 Jun 28, 2005 Jkt 205250 We invite you to submit comments regarding our proposal to adopt the NIMAS and to make your comments as specific as possible. Also, if appropriate, please identify the specific section or subsection of the NIMAS that each of your comments addresses and arrange your comments in the same order as the standard. We invite you to assist us in complying with the specific requirements of Executive Order 12866 and its overall requirement of reducing regulatory burden that might result from this proposed regulatory action. Please let us know of any further opportunities we should take to reduce potential costs PO 00000 Frm 00012 Fmt 4702 Sfmt 4702 or increase potential benefits in connection with this regulatory action. Please include the following with your comments: A description of the area of your involvement in special education or regular education, as well as your role, if any, in that area (e.g., parent, teacher, student, state or local administrator, or researcher) or other area (e.g., technology specialist, publisher, or software developer). During and after the comment period, you may inspect all public comments about the standard in room 5126, Potomac Center Plaza, 550 12th Street, SW., Washington, DC, between the hours of 8:30 a.m. and 4 p.m., Eastern time, Monday through Friday of each week except Federal holidays. Assistance to Individuals With Disabilities in Reviewing the Comments On request, we will supply an appropriate aid, such as a reader or print magnifier, to an individual with a disability who needs assistance to review the comments or other documents in the public rulemaking record for this standard. If you want to schedule an appointment for this type of aid, please contact the person listed under FOR FURTHER INFORMATION CONTACT. Background States use electronic files from publishers of educational materials to produce accessible versions (e.g., Braille or digital audio) of these materials or contract to have accessible versions produced from these files. Because States have different requirements for these electronic files, however, publishers often experience increased costs for production, and States experience delays and inconsistencies in the materials produced. To facilitate the provision of accessible, timely, and consistent versions of print textbooks in the United States, the Department of Education funded the National Center on Accessing the General Curriculum (NCAC) at the Center on Applied Special Technologies, Inc. (CAST) to establish technical specifications for a voluntary national instructional materials accessibility standard. Beginning in November 2002, NCAC convened a panel of 43 experts, composed of educators, publishers, technology specialists, and disability groups. The National Institute of Standards and Technology (NIST) also participated on the panel. The panel held three public meetings in January, March, and June 2003, and conducted extensive teleconference and online discussions. E:\FR\FM\29JNP1.SGM 29JNP1 Federal Register / Vol. 70, No. 124 / Wednesday, June 29, 2005 / Proposed Rules The panel developed, with consensus, a common standard for digital source files that can be used to accurately and reliably produce instructional materials in a variety of alternate formats using the same source file. This standard, known as the National Instructional Materials Accessibility Standard (NIMAS, version 1.0), provides a single, uniform format that can be used for the electronic files associated with instructional materials. The Department announced the establishment of the NIMAS as a voluntary standard on July 27, 2004. Additional information on the standard and the expert panel’s report is available at http://nimas.cast.org/about/ index.html. The purpose of the NIMAS is to help increase the availability and timely delivery of print instructional materials in accessible formats to blind or other persons with print disabilities in elementary schools and secondary schools. The term print instructional materials is defined in section 674(e)(3)(C) of the Act, and the term blind or other persons with print disabilities is defined in section 674(e)(3)(A) of the Act. Under section 674(e)(4) of the Act, the NIMAS applies to print instructional materials published after the date on which the final rule establishing the NIMAS is published in the Federal Register. This notice proposes to establish the NIMAS and would amend 34 CFR part 300 for purposes of complying with section 674(e)(4) of the Act. A separate rulemaking proceeding will be conducted to require States to adopt the standard. In this separate notice, the Secretary will propose other amendments to 34 CFR part 300, which will contain information and seek public comment on the requirement for States to adopt the NIMAS in a timely manner after it has been established by the Department, as set forth in section 612(a)(23)(A) of the Act. Significant Proposed Regulation We propose to establish the NIMAS in our regulations by adding an appendix to 34 CFR part 300 that will set forth the technical elements and specifications for the standard. The proposed appendix is included at the end of this notice. Executive Order 12866 Potential Costs and Benefits Under Executive Order 12866, we have assessed the potential costs and benefits of this regulatory action. The potential costs associated with the proposed standard are those resulting from statutory requirements VerDate jul<14>2003 15:26 Jun 28, 2005 Jkt 205250 and those we have determined to be necessary for administering this program effectively and efficiently. In assessing the potential costs and benefits—both quantitative and qualitative—of this regulatory action, we have determined that the benefits would justify the costs. We have also determined that this regulatory action would not unduly interfere with State, local, and tribal governments in the exercise of their governmental functions. Summary of Potential Costs and Benefits The National Instructional Materials Accessibility Standard (NIMAS) applies to print instructional materials required by State or local educational agencies (LEAs) for classroom use. Publishers, State and local educational agencies, authorized conversion entities, and students potentially will be affected by NIMAS. The adoption of the NIMAS is expected to provide long-term cost savings for publishers of educational materials. Currently, 26 States have laws requiring publishers to provide State or local educational agencies with electronic files suitable for converting print instructional materials into Braille versions. Depending on what requirements each State has enacted, publishers may be required to produce a conversion file in as many as 6 different file formats. This process wastes time and effort on the part of publishers and is unnecessarily costly. Adoption of the NIMAS means that publishers won’t have to convert their materials to several different file formats. The NIMAS will supersede the different standards for source files currently used by some State and local educational agencies to produce accessible versions of textbooks. However, unless States and LEAs currently use electronic source files to produce their own accessible versions of textbooks, this will not result in any additional cost to these agencies beyond that associated with publishing new State rules, as needed, to implement the NIMAS. In most cases, States and LEAs currently contract with third party providers to take the electronic source files and convert them into accessible formats such as Braille, digital text, and digital audio. These third party providers may encounter some cost in adapting to the use of the NIMAS files, but this will be more than offset by the savings realized from only having to work with one format instead of multiple formats. In addition, these entities will not need to spend PO 00000 Frm 00013 Fmt 4702 Sfmt 4702 37303 exorbitant amounts of time manipulating different types of files in order to convert them into accessible formats. Working with only one format is also a benefit for publishers of textbooks and will result in cost savings for these entities. Any cost to States and LEAs in moving to NIMAS should be offset by the increased speed in which they receive files and improved consistency and quality of the files received. The adoption of NIMAS is expected to be highly valuable to students who are blind or who have print disabilities because they will have access to accessible versions of textbooks in a timely manner. Current methods of converting print textbooks into Braille and other specialized formats are complex and time consuming, and the process can take months to complete. In many cases students who are blind or who have print disabilities now receive accessible textbooks and other instructional materials well after the beginning of the instructional period. The adoption of the NIMAS will improve both the speed of the process and the quality and consistency of books converted into specialized formats. The Act does not require existing textbooks to be converted to NIMAS. There also are no associated costs to prepare special education instructors to use or train others to use this new standard because teachers and other educational staff receive the books in their final accessible format. The method used to produce the book is not visible to the teachers or students, except that use of the universal standard is expected to speed the delivery of the books to the students and improve the quality and consistency of the texts. Regulatory Flexibility Act Certification The Secretary certifies that this proposed standard would not have a significant economic impact on a substantial number of small entities. This proposed standard would largely affect States and State agencies or individuals. States and State agencies are not defined as ‘‘small entities’’ in the Regulatory Flexibility Act. Paperwork Reduction Act of 1995 The proposed standard does not contain any information collection requirements. Intergovernmental Review This standard is not subject to Executive Order 12372 and the regulations in 34 CFR part 79. E:\FR\FM\29JNP1.SGM 29JNP1 37304 Federal Register / Vol. 70, No. 124 / Wednesday, June 29, 2005 / Proposed Rules Federalism Executive Order 13132 requires us to ensure meaningful and timely input by State and local elected officials in the development of regulatory policies that have federalism implications. ‘‘Federalism implications’’ means substantial direct effects on the States, on the relationship between the National Government and the States, or on the distribution of power and responsibilities among the various levels of government. The proposed standard may have federalism implications, as defined in Executive Order 13132. We encourage State and local elected officials to review and provide comments on this proposed standard. Electronic Access to This Document You may view this document, as well as all other Department of Education documents published in the Federal Register, in text or Adobe Portable Document Format (PDF) on the Internet at the following site: http://www.ed.gov/ news/fedregister. To use PDF you must have Adobe Acrobat Reader, which is available free at this site. If you have questions about using PDF, call the U.S. Government Printing Office (GPO), toll free, at 1– 888–293–6498; or in the Washington, DC, area at (202) 512–1530. accessible instructional materials, Technology. Note: The official version of this document is the document published in the Federal Register. Free Internet access to the official edition of the Federal Register and the Code of Federal Regulations is available on GPO Access at: http://www.gpoaccess.gov/nara/ index.html. PART 300—ASSISTANCE TO STATES FOR THE EDUCATION OF CHILDREN WITH DISABILITIES (Catalog of Federal Domestic Assistance Number does not apply) Authority: 20 U.S.C. 1411–1420, unless otherwise noted. List of Subjects in 34 CFR Part 300 National Instructional Materials Accessibility Standard (NIMAS), Special education, Grant programs— 2. Appendix D is added to part 300 as follows: Dated: June 24, 2005. John H. Hager, Assistant Secretary for Special Education and Rehabilitative Services. For the reasons discussed in the preamble, the Secretary proposes to amend part 300 of title 34 of the Code of Federal Regulations as follows: 1. The authority citation for part 300 continues to read as follows: Appendix D—National Instructional Materials Accessibility Standard TECHNICAL SPECIFICATIONS—THE BASELINE ELEMENT SET Element Description a. Document-level tags (required to be valid XML) dtbook ............... Head ................. book .................. meta .................. title .................... The root element in the Digital Talking Book DTD. <dtbook> contains metadata in <head> and the contents itself in <book>. Contains metainformation about the book but no actual content of the book itself, which is placed in <book>. This information is consonant with the <head> information in xhtml, see [XHTML11STRICT]. Other miscellaneous elements can occur before and after the required <title>. By convention <title> should occur first. Surrounds the actual content of the document, which is divided into <frontmatter>, <bodymatter>, and <rearmatter>. <head>, which contains metadata, precedes <book>. Indicates metadata about the book. It is an empty element that may appear repeatedly only in <head>. Contains the title of the book but is used only as metainformation in <head>. Use <doctitle> within <book> for the actual book title, which will usually be the same. Usage Guidelines: please refer to Document Level Tags and Required Tags in Appendix B, DAISY Consortium, 2002. http:// nimas.cast.org/about/report /index.html#appendixb. b. Structure and Hierarchy bodymatter ........ rearmatter ......... level1 ................ level2 ................ level3 ................ level4 ................ level5 ................ level6 ................ h1 h2 h3 h4 h5 h6 ...................... ...................... ...................... ...................... ...................... ...................... VerDate jul<14>2003 Consists of the text proper of a book, as contrasted with preliminary material <frontmatter> or supplementary information in <rearmatter>. Contains supplementary material such as appendices, glossaries, bibliographies, and indices. It follows the <bodymatter> of the book. The highest-level container of major divisions of a book. Used in <frontmatter>, <bodymatter>, and <rearmatter> to mark the largest divisions of the book (usually parts or chapters), inside which level2 subdivisions (often sections) may nest. The class attribute identifies the actual name (e.g., part, chapter) of the structure it marks. Contrast with <level>. Contains subdivisions that nest within <level1> divisions. The class attribute identifies the actual name (e.g., subpart, chapter, subsection) of the structure it marks. Contains sub-subdivisions that nest within <level2> subdivisions (e.g., sub-subsections within subsections). The class attribute identifies the actual name (e.g., section, subpart, subsubsection) of the subordinate structure it marks. Contains further subdivisions that nest within <level3> subdivisions. The class attribute identifies the actual name of the subordinate structure it marks. Contains further subdivisions that nest within <level4> subdivisions. The class attribute identifies the actual name of the subordinate structure it marks. Contains further subdivisions that nest within <level5> subdivisions. The class attribute identifies the actual name of the subordinate structure it marks. Contains the text of the heading for a <level1> structure. Contains the text of the heading for a <level2> structure. Contains the text of the heading for a <level3> structure. Contains the text of the heading for a <level4> structure. Contains the text of the heading for a <level5> structure. Contains the text of the heading for a <level6> structure. Usage Guidelines: please refer to the Information Object references in the Structure and Hierarchy section in Appendix B,  DAISY Consortium, 2002. 15:26 Jun 28, 2005 Jkt 205250 PO 00000 Frm 00014 Fmt 4702 Sfmt 4702 E:\FR\FM\29JNP1.SGM 29JNP1 Federal Register / Vol. 70, No. 124 / Wednesday, June 29, 2005 / Proposed Rules 37305 TECHNICAL SPECIFICATIONS—THE BASELINE ELEMENT SET—Continued Element Description c. Block Elements blockquote ........ list ..................... Li ....................... Hd ..................... note ................... P ....................... sidebar .............. cite .................... Dd ..................... Dl ...................... Dt ...................... Indicates a block of quoted content that is set off from the surrounding text by paragraph breaks. Compare with <q>, which marks short, inline quotations. Contains some form of list, ordered or unordered. The list may have intermixed heading <hd> (generally only one, possibly with <prodnote>) and an intermixture of list items <li> and <pagenum>. If bullets and outline enumerations are part of the print content, they are expected to prefix those list items in content, rather than be implicitly generated. Marks each list item in a <list>. <li> content may be either inline or block and may include other nested lists. Alternatively it may contain a sequence of list item components, <lic>, that identify regularly occurring content, such as the heading and page number of each entry in a table of contents. Marks the text of a heading in a <list> or <sidebar>. Marks a footnote, endnote, etc. Any local reference to <note id=’’yyy’’> is by <noteref idref=’’#yyy’’> [Attribute id]. Contains a paragraph, which may contain subsidiary <list> or <dl>. Contains information supplementary to the main text and/or narrative flow and is often boxed and printed apart from the main text block on a page. It may have a heading <hd>. Marks a reference (or citation) to another document. Marks a definition of the preceding term <dt> within a definition list <dl>. A definition without a preceding <dt> has no semantic interpretation, but is visually presented aligned with other <dd>. Contains a definition list, usually consisting of pairs of terms <dt> and definitions <dd>. Any definition can contain another definition list. Marks a term in a definition list <dl> for which a definition <dd> follows. Usage Guidelines: please refer to the Information Object references in the Block Elements section in Appendix B, DAISY Consortium, 2002. d. Inline Elements q ........................ strong ................ sub .................... sup .................... br ...................... line .................... linenum ............. pagenum ........... noteref .............. Contains a short, inline quotation. Compare with <blockquote>, which marks a longer quotation set off from the surrounding text. Marks stronger emphasis than <em>. Visually <strong> is usually rendered bold. Indicates a subscript character (printed below a character’s normal baseline). Can be used recursively and/or intermixed with <sup>. Marks a superscript character (printed above a character’s normal baseline). Can be used recursively and/or intermixed with <sub>. Marks a forced line break. Marks a single logical line of text. Often used in conjunction with <linenum> in documents with numbered lines. [Include in baseline element set. Use only when line breaks must be preserved to capture meaning (e.g., poems, legal texts).] Contains a line number, for example in legal text. [Include in baseline element set. Use only when <line> is used, and only for lines numbered in print book.] Contains one page number as it appears from the print document, usually inserted at the point within the file immediately preceding the first item of content on a new page. [NB: Only valid when includes id attribute]. Marks one or more characters that reference a footnote or endnote <note>. Contrast with <annoref>. <noteref> and <note> are independently skippable. Usage Guidelines: please refer to the Information Object references in the Inline Elements section in Appendix B, DAISYConsortium, 2002. e. Tables table .................. td ....................... tr ....................... Contains cells of tabular data arranged in rows and columns. A <table> may have a <caption>. It may have descriptions of the columns in <col>s or groupings of several <col> in <colgroup>. A simple <table> may be made up of just rows <tr>. A long table crossing several pages of the print book should have separate <pagenum> values for each of the pages containing that <table> indicated on the page where it starts. Note the logical order of optional <thead>, optional <tfoot>, then one or more of either <tbody> or just rows <tr>. This order accommodates simple or large, complex tables. The <thead> and <tfoot> information usually helps identify content of the <tbody> rows. For a multiple-page print <table> the <thead> and <tfoot> are repeated on each page, but not redundantly tagged. Indicates a table cell containing data. Marks one row of a <table> containing <th> or <td> cells. Usage Guidelines: please refer to the Information Object references in the Tables section in Appendix B, DAISY Consortium, 2002. f. Images imggroup ........... caption .............. VerDate jul<14>2003 Provides a container for one or more <img> and associated <caption>(s) and <prodnote>(s). A <prodnote> may contain a description of the image. The content model allows: 1) multiple <img> if they share a caption, with the ids of each <img> in the <caption imgref=’’id1 id2 ...’’>, 2) multiple <caption> if several captions refer to a single <img id=‘‘xxx’’> where each caption has the same <caption imgref=‘‘xxx’’>, 3) multiple <prodnote> if different versions are needed for different media (e.g., large print, Braille, or print). If several <prodnote> refer to a single <img id=‘‘xxx’’>, each prodnote has the same <prodnote imgref=‘‘xxx’’>. Describes a <table> or <img>. If used with <table> it must follow immediately after the <table> start tag. If used with <img> or <imggroup> it is not so constrained. Usage Guidelines: please refer to the Information Object references in the Images section in Appendix B, DAISY Consortium, 2002. 15:26 Jun 28, 2005 Jkt 205250 PO 00000 Frm 00015 Fmt 4702 Sfmt 4702 E:\FR\FM\29JNP1.SGM 29JNP1 37306 Federal Register / Vol. 70, No. 124 / Wednesday, June 29, 2005 / Proposed Rules 1. The Optional Elements and Guidelines for Use Publishers are encouraged to apply markup beyond the baseline (required) elements. The complete DTBook Element Set reflects the tags necessary to create the six types of Digital Talking Books referenced in Section II and Braille output. Because of the present necessity to subdivide the creation of alternate format materials into distinct phases, the Panel determined that baseline elements would be provided by publishers, and optional elements would be added to the NIMAScompliant files by third party conversion entities. In both circumstances the protocols for tagging the digital files should conform to the ANSI/NISO Z39.86 specification. For this reason, the optional elements beyond the baseline set are included as an Appendix C, and content converters are directed to the DAISY Structure Guidelines (http://www.daisy.org/ publications/guidelines/sg-daisy3/ structguide.htm) for guidance on their use. 2. Package File A package file describes a publication. It identifies all other files in the publication and provides descriptive and access information about them. A publication must include a package file conforming to the NIMAS. The package file is based on the Open eBook Publication Structure 1.2 package file specification (For most recent detail please see http://www.openebook.org/ oebps/oebps1.2/download/oeb12xhtml.htm#sec2). A NIMAS package file must be an XML-valid OeB PS 1.2 package file instance and must meet the following additional standards: The NIMAS Package File must include the following Dublin Core (dc:) metadata: • dc:Title. • dc:Creator (if applicable). • dc:Publisher. • dc:Date (Date of NIMAS-compliant file creation—yyyy-mm-dd). • dc:Format (=‘‘NIMAS 1.0’’). • dc:Identifier (a unique identifier for the NIMAS-compliant digital publication, e.g., print ISBN + ‘‘NIMAS’’—exact format to be determined). • dc:Language (one instance, or multiple in the case of a foreign language textbook, etc.). • dc:Rights (details to be determined). • dc:Source (ISBN of print version of textbook). And the following x-metadata items: • nimas-SourceEdition (the edition of the print textbook). VerDate jul<14>2003 15:26 Jun 28, 2005 Jkt 205250 • nimas-SourceDate (date of publication of the print textbook). The following metadata were proposed also as a means of facilitating recordkeeping, storage and file retrieval: • dc:Subject (Lang Arts, Soc Studies, etc.). • nimas-grade (specific grade level of the print textbook, e.g.; Grade 6). • nimas gradeRange (specific grade range of the print textbook, e.g.; Grades 4–5). And additional suggestion references the use of: • dc:audience:educationLevel (for the grade and gradeRange identifiers, noting that Dublin Core recommends using educationLevel with an appropriate controlled vocabulary for context, and recommends the U.S. Department of Education’s Level of Education vocabulary online at http://www.ed.gov/ admin/reference/index.jsp. Using educationLevel obviates the need for a separate field for gradeRange since dc elements can repeat more than once. A book used in more than one grade would therefore have two elements, one with value ‘‘Grade 4’’ and another with value ‘‘Grade 5.’’ A final determination as to which of these specific metadata elements to use needs to be clarified in practice. The package manifest must list all provided files (text, images, etc.). The package spine must reference all text content files in order. (Note: For purposes of continuity and to minimize errors in transformation and processing, the NIMAS-compliant digital text should be provided as a single document.) [FR Doc. 05–12853 Filed 6–28–05; 8:45 am] BILLING CODE 4000–01–P ENVIRONMENTAL PROTECTION AGENCY 40 CFR Parts 52 and 81 Approval and Promulgation of State Implementation Plans: Washington; Spokane Carbon Monoxide Nonattainment Area; Designation of Areas for Air Quality Planning Purposes Environmental Protection Agency (EPA). ACTION: Proposed rule. AGENCY: SUMMARY: On November 29, 2004, the State of Washington submitted a carbon monoxide (CO) maintenance plan for the Spokane CO nonattainment area to EPA for approval. The State Frm 00016 Fmt 4702 Sfmt 4702 In the rules section of this Federal Register, EPA is approving the State’s SIP submittal as a direct final rule without prior proposal because the Agency views this as a noncontroversial submittal and anticipates no adverse comments. A detailed rationale for the approval is set forth in the direct final rule. If EPA receives no adverse comments in response to this action, no further activity is contemplated. If EPA receives adverse comments, the Agency will withdraw the direct final rule and will address all public comments we receive in a subsequent final rule based on this proposed rule. EPA will not institute a second comment period. Any parties interested SUPPLEMENTARY INFORMATION: [Docket ID No. R10–OAR–2005–WA–0001; FRL–7929–6] PO 00000 concurrently requested that EPA redesignate the Spokane CO nonattainment area to attainment for the National Ambient Air Quality Standard (NAAQS) for CO. In this action, EPA is proposing approval of the maintenance plan and redesignation of the Spokane CO nonattainment area to attainment. DATES: Written comments must be received by July 29, 2005. ADDRESSES: Submit comments, identified by Docket ID No. R10–OAR– 2005–WA–0001, by one of the following methods: • Federal eRulemaking Portal: http:// www.regulations.gov. Follow the on-line instructions for submitting comments. • Agency Web site: http:// www.epa.gov/edocket. EDOCKET, EPA’s electronic public docket and comment system, is EPA’s preferred method for receiving comments. Follow the on-line instructions for submitting comments. • Mail: Connie Robinson, Office of Air, Waste, and Toxics, Environmental Protection Agency, Mail code: AWT– 107, 1200 Sixth Ave., Seattle, Washington 98101. • Hand Delivery: EPA, Region 10, Service Center, 14th Floor, 1200 Sixth Ave., Seattle, Washington 98101; Attention: Connie Robinson, Office of Air, Waste and Toxics, AWT–107. Such deliveries are only accepted during normal hours of operation, and special arrangements should be made for deliveries of boxed information. Please see the direct final rule which is located in the Final Rules and Regulations section of this Federal Register for detailed instructions on how to submit comments. FOR FURTHER INFORMATION CONTACT: Connie L. Robinson, EPA, Region 10, Office of Air, Waste, and Toxics (AWT– 107), Seattle, Washington, (206) 553– 1086, or by e-mail at robinson.connie@epa.gov. E:\FR\FM\29JNP1.SGM 29JNP1

Agencies

[Federal Register Volume 70, Number 124 (Wednesday, June 29, 2005)]
[Proposed Rules]
[Pages 37302-37306]
From the Federal Register Online via the Government Printing Office [www.gpo.gov]
[FR Doc No: 05-12853]


=======================================================================
-----------------------------------------------------------------------

DEPARTMENT OF EDUCATION

34 CFR Part 300

RIN 1820-AB56


National Instructional Materials Accessibility Standard

AGENCY: Office of Special Education and Rehabilitative Services, 
Department of Education.

ACTION: Notice of proposed rulemaking.

-----------------------------------------------------------------------

SUMMARY: The Secretary of Education proposes to establish the National 
Instructional Materials Accessibility Standard (NIMAS or standard) as 
required under sections 612(a)(23)(A) and 674(e)(4) of the Individuals 
with Disabilities Education Act, as amended by the Individuals with 
Disabilities Education Improvement Act of 2004 (Act). The purpose of 
the NIMAS is to help increase the availability and timely delivery of 
print instructional materials in accessible formats to blind or other 
persons with print disabilities in elementary schools and secondary 
schools.

DATES: We must receive your comments on or before September 12, 2005.

ADDRESSES: Address all comments about this proposed standard to Troy 
Justesen, Office of Special Education and Rehabilitative Services, U.S. 
Department of Education, 400 Maryland Avenue, SW., room 5126, Potomac 
Center Plaza, Washington, DC 20202-2641. If you prefer to send your 
comments through the Internet, you may address them to us at the U.S. 
Government Web site: http://www.regulations.gov.
    Or you may send your Internet comments to us at the following 
address: Osersnimascomments@ed.gov.
    You must include the term ``NIMAS Comments'' in the subject line of 
your electronic message.
    Please submit your comments only one time in order to ensure that 
we do not receive duplicate copies.

FOR FURTHER INFORMATION CONTACT: Troy R. Justesen. Telephone: (202) 
245-7468.
    If you use a telecommunications device for the deaf (TDD), you may 
call the Federal Relay Service (FRS) at 1-800-877-8339.
    Individuals with disabilities may obtain this document in an 
alternative format (e.g., Braille, large print, audiotape, or computer 
diskette) on request to the contact person listed under FOR FURTHER 
INFORMATION CONTACT.

SUPPLEMENTARY INFORMATION: 

Invitation to Comment

    We invite you to submit comments regarding our proposal to adopt 
the NIMAS and to make your comments as specific as possible. Also, if 
appropriate, please identify the specific section or subsection of the 
NIMAS that each of your comments addresses and arrange your comments in 
the same order as the standard.
    We invite you to assist us in complying with the specific 
requirements of Executive Order 12866 and its overall requirement of 
reducing regulatory burden that might result from this proposed 
regulatory action. Please let us know of any further opportunities we 
should take to reduce potential costs or increase potential benefits in 
connection with this regulatory action.
    Please include the following with your comments: A description of 
the area of your involvement in special education or regular education, 
as well as your role, if any, in that area (e.g., parent, teacher, 
student, state or local administrator, or researcher) or other area 
(e.g., technology specialist, publisher, or software developer).
    During and after the comment period, you may inspect all public 
comments about the standard in room 5126, Potomac Center Plaza, 550 
12th Street, SW., Washington, DC, between the hours of 8:30 a.m. and 4 
p.m., Eastern time, Monday through Friday of each week except Federal 
holidays.

Assistance to Individuals With Disabilities in Reviewing the Comments

    On request, we will supply an appropriate aid, such as a reader or 
print magnifier, to an individual with a disability who needs 
assistance to review the comments or other documents in the public 
rulemaking record for this standard. If you want to schedule an 
appointment for this type of aid, please contact the person listed 
under FOR FURTHER INFORMATION CONTACT.

Background

    States use electronic files from publishers of educational 
materials to produce accessible versions (e.g., Braille or digital 
audio) of these materials or contract to have accessible versions 
produced from these files. Because States have different requirements 
for these electronic files, however, publishers often experience 
increased costs for production, and States experience delays and 
inconsistencies in the materials produced.
    To facilitate the provision of accessible, timely, and consistent 
versions of print textbooks in the United States, the Department of 
Education funded the National Center on Accessing the General 
Curriculum (NCAC) at the Center on Applied Special Technologies, Inc. 
(CAST) to establish technical specifications for a voluntary national 
instructional materials accessibility standard. Beginning in November 
2002, NCAC convened a panel of 43 experts, composed of educators, 
publishers, technology specialists, and disability groups. The National 
Institute of Standards and Technology (NIST) also participated on the 
panel. The panel held three public meetings in January, March, and June 
2003, and conducted extensive teleconference and online discussions.

[[Page 37303]]

    The panel developed, with consensus, a common standard for digital 
source files that can be used to accurately and reliably produce 
instructional materials in a variety of alternate formats using the 
same source file. This standard, known as the National Instructional 
Materials Accessibility Standard (NIMAS, version 1.0), provides a 
single, uniform format that can be used for the electronic files 
associated with instructional materials. The Department announced the 
establishment of the NIMAS as a voluntary standard on July 27, 2004. 
Additional information on the standard and the expert panel's report is 
available at http://nimas.cast.org/about/index.html.
    The purpose of the NIMAS is to help increase the availability and 
timely delivery of print instructional materials in accessible formats 
to blind or other persons with print disabilities in elementary schools 
and secondary schools. The term print instructional materials is 
defined in section 674(e)(3)(C) of the Act, and the term blind or other 
persons with print disabilities is defined in section 674(e)(3)(A) of 
the Act.
    Under section 674(e)(4) of the Act, the NIMAS applies to print 
instructional materials published after the date on which the final 
rule establishing the NIMAS is published in the Federal Register. This 
notice proposes to establish the NIMAS and would amend 34 CFR part 300 
for purposes of complying with section 674(e)(4) of the Act. A separate 
rulemaking proceeding will be conducted to require States to adopt the 
standard. In this separate notice, the Secretary will propose other 
amendments to 34 CFR part 300, which will contain information and seek 
public comment on the requirement for States to adopt the NIMAS in a 
timely manner after it has been established by the Department, as set 
forth in section 612(a)(23)(A) of the Act.

Significant Proposed Regulation

    We propose to establish the NIMAS in our regulations by adding an 
appendix to 34 CFR part 300 that will set forth the technical elements 
and specifications for the standard. The proposed appendix is included 
at the end of this notice.

Executive Order 12866

Potential Costs and Benefits

    Under Executive Order 12866, we have assessed the potential costs 
and benefits of this regulatory action.
    The potential costs associated with the proposed standard are those 
resulting from statutory requirements and those we have determined to 
be necessary for administering this program effectively and 
efficiently.
    In assessing the potential costs and benefits--both quantitative 
and qualitative--of this regulatory action, we have determined that the 
benefits would justify the costs.
    We have also determined that this regulatory action would not 
unduly interfere with State, local, and tribal governments in the 
exercise of their governmental functions.

Summary of Potential Costs and Benefits

    The National Instructional Materials Accessibility Standard (NIMAS) 
applies to print instructional materials required by State or local 
educational agencies (LEAs) for classroom use. Publishers, State and 
local educational agencies, authorized conversion entities, and 
students potentially will be affected by NIMAS.
    The adoption of the NIMAS is expected to provide long-term cost 
savings for publishers of educational materials. Currently, 26 States 
have laws requiring publishers to provide State or local educational 
agencies with electronic files suitable for converting print 
instructional materials into Braille versions. Depending on what 
requirements each State has enacted, publishers may be required to 
produce a conversion file in as many as 6 different file formats. This 
process wastes time and effort on the part of publishers and is 
unnecessarily costly. Adoption of the NIMAS means that publishers won't 
have to convert their materials to several different file formats.
    The NIMAS will supersede the different standards for source files 
currently used by some State and local educational agencies to produce 
accessible versions of textbooks. However, unless States and LEAs 
currently use electronic source files to produce their own accessible 
versions of textbooks, this will not result in any additional cost to 
these agencies beyond that associated with publishing new State rules, 
as needed, to implement the NIMAS. In most cases, States and LEAs 
currently contract with third party providers to take the electronic 
source files and convert them into accessible formats such as Braille, 
digital text, and digital audio. These third party providers may 
encounter some cost in adapting to the use of the NIMAS files, but this 
will be more than offset by the savings realized from only having to 
work with one format instead of multiple formats. In addition, these 
entities will not need to spend exorbitant amounts of time manipulating 
different types of files in order to convert them into accessible 
formats. Working with only one format is also a benefit for publishers 
of textbooks and will result in cost savings for these entities. Any 
cost to States and LEAs in moving to NIMAS should be offset by the 
increased speed in which they receive files and improved consistency 
and quality of the files received.
    The adoption of NIMAS is expected to be highly valuable to students 
who are blind or who have print disabilities because they will have 
access to accessible versions of textbooks in a timely manner. Current 
methods of converting print textbooks into Braille and other 
specialized formats are complex and time consuming, and the process can 
take months to complete. In many cases students who are blind or who 
have print disabilities now receive accessible textbooks and other 
instructional materials well after the beginning of the instructional 
period. The adoption of the NIMAS will improve both the speed of the 
process and the quality and consistency of books converted into 
specialized formats.
    The Act does not require existing textbooks to be converted to 
NIMAS. There also are no associated costs to prepare special education 
instructors to use or train others to use this new standard because 
teachers and other educational staff receive the books in their final 
accessible format. The method used to produce the book is not visible 
to the teachers or students, except that use of the universal standard 
is expected to speed the delivery of the books to the students and 
improve the quality and consistency of the texts.

Regulatory Flexibility Act Certification

    The Secretary certifies that this proposed standard would not have 
a significant economic impact on a substantial number of small 
entities. This proposed standard would largely affect States and State 
agencies or individuals. States and State agencies are not defined as 
``small entities'' in the Regulatory Flexibility Act.

Paperwork Reduction Act of 1995

    The proposed standard does not contain any information collection 
requirements.

Intergovernmental Review

    This standard is not subject to Executive Order 12372 and the 
regulations in 34 CFR part 79.

[[Page 37304]]

Federalism

    Executive Order 13132 requires us to ensure meaningful and timely 
input by State and local elected officials in the development of 
regulatory policies that have federalism implications. ``Federalism 
implications'' means substantial direct effects on the States, on the 
relationship between the National Government and the States, or on the 
distribution of power and responsibilities among the various levels of 
government. The proposed standard may have federalism implications, as 
defined in Executive Order 13132. We encourage State and local elected 
officials to review and provide comments on this proposed standard.

Electronic Access to This Document

    You may view this document, as well as all other Department of 
Education documents published in the Federal Register, in text or Adobe 
Portable Document Format (PDF) on the Internet at the following site: 
http://www.ed.gov/news/fedregister.
    To use PDF you must have Adobe Acrobat Reader, which is available 
free at this site. If you have questions about using PDF, call the U.S. 
Government Printing Office (GPO), toll free, at 1-888-293-6498; or in 
the Washington, DC, area at (202) 512-1530.

    Note: The official version of this document is the document 
published in the Federal Register. Free Internet access to the 
official edition of the Federal Register and the Code of Federal 
Regulations is available on GPO Access at: http://www.gpoaccess.gov/nara/index.html.

(Catalog of Federal Domestic Assistance Number does not apply)

List of Subjects in 34 CFR Part 300

    National Instructional Materials Accessibility Standard (NIMAS), 
Special education, Grant programs--accessible instructional materials, 
Technology.

    Dated: June 24, 2005.
John H. Hager,
Assistant Secretary for Special Education and Rehabilitative Services.
    For the reasons discussed in the preamble, the Secretary proposes 
to amend part 300 of title 34 of the Code of Federal Regulations as 
follows:

PART 300--ASSISTANCE TO STATES FOR THE EDUCATION OF CHILDREN WITH 
DISABILITIES

    1. The authority citation for part 300 continues to read as 
follows:

    Authority: 20 U.S.C. 1411-1420, unless otherwise noted.
    2. Appendix D is added to part 300 as follows:

Appendix D--National Instructional Materials Accessibility Standard

           Technical Specifications--The Baseline Element Set
------------------------------------------------------------------------
         Element                            Description
------------------------------------------------------------------------
            a. Document-level tags (required to be valid XML)
------------------------------------------------------------------------
dtbook...................  The root element in the Digital Talking Book
                            DTD.  contains metadata in 
                            and the contents itself in .
Head.....................  Contains metainformation about the book but
                            no actual content of the book itself, which
                            is placed in . This information is
                            consonant with the  information in
                            xhtml, see [XHTML11STRICT]. Other
                            miscellaneous elements can occur before and
                            after the required . By convention
                            <title> should occur first.
book.....................  Surrounds the actual content of the document,
                            which is divided into <frontmatter>,
                            <bodymatter>, and <rearmatter>. <head>,
                            which contains metadata, precedes <book>.
meta.....................  Indicates metadata about the book. It is an
                            empty element that may appear repeatedly
                            only in <head>.
title....................  Contains the title of the book but is used
                            only as metainformation in <head>. Use
                            <doctitle> within <book> for the actual book
                            title, which will usually be the same.
                           Usage Guidelines: please refer to Document
                            Level Tags and Required Tags in Appendix B,
                            (copyright)DAISY Consortium, 2002. <a href="http://nimas.cast.org/about/report">http://nimas.cast.org/about/report</a> /
                            index.html#appendixb.
--------------------------
                       b. Structure and Hierarchy
------------------------------------------------------------------------
bodymatter...............  Consists of the text proper of a book, as
                            contrasted with preliminary material
                            <frontmatter> or supplementary information
                            in <rearmatter>.
rearmatter...............  Contains supplementary material such as
                            appendices, glossaries, bibliographies, and
                            indices. It follows the <bodymatter> of the
                            book.
level1...................  The highest-level container of major
                            divisions of a book. Used in <frontmatter>,
                            <bodymatter>, and <rearmatter> to mark the
                            largest divisions of the book (usually parts
                            or chapters), inside which level2
                            subdivisions (often sections) may nest. The
                            class attribute identifies the actual name
                            (e.g., part, chapter) of the structure it
                            marks. Contrast with <level>.
level2...................  Contains subdivisions that nest within
                            <level1> divisions. The class attribute
                            identifies the actual name (e.g., subpart,
                            chapter, subsection) of the structure it
                            marks.
level3...................  Contains sub-subdivisions that nest within
                            <level2> subdivisions (e.g., sub-subsections
                            within subsections). The class attribute
                            identifies the actual name (e.g., section,
                            subpart, subsubsection) of the subordinate
                            structure it marks.
level4...................  Contains further subdivisions that nest
                            within <level3> subdivisions. The class
                            attribute identifies the actual name of the
                            subordinate structure it marks.
level5...................  Contains further subdivisions that nest
                            within <level4> subdivisions. The class
                            attribute identifies the actual name of the
                            subordinate structure it marks.
level6...................  Contains further subdivisions that nest
                            within <level5> subdivisions. The class
                            attribute identifies the actual name of the
                            subordinate structure it marks.
h1.......................  Contains the text of the heading for a
                            <level1> structure.
h2.......................  Contains the text of the heading for a
                            <level2> structure.
h3.......................  Contains the text of the heading for a
                            <level3> structure.
h4.......................  Contains the text of the heading for a
                            <level4> structure.
h5.......................  Contains the text of the heading for a
                            <level5> structure.
h6.......................  Contains the text of the heading for a
                            <level6> structure.
                           Usage Guidelines: please refer to the
                            Information Object references in the
                            Structure and Hierarchy section in Appendix
                            B, (copyright) DAISY Consortium, 2002.
--------------------------

[[Page 37305]]

 
                            c. Block Elements
------------------------------------------------------------------------
blockquote...............  Indicates a block of quoted content that is
                            set off from the surrounding text by
                            paragraph breaks. Compare with <q>, which
                            marks short, inline quotations.
list.....................  Contains some form of list, ordered or
                            unordered. The list may have intermixed
                            heading <hd> (generally only one, possibly
                            with <prodnote>) and an intermixture of list
                            items <li> and <pagenum>. If bullets and
                            outline enumerations are part of the print
                            content, they are expected to prefix those
                            list items in content, rather than be
                            implicitly generated.
Li.......................  Marks each list item in a <list>. <li>
                            content may be either inline or block and
                            may include other nested lists.
                            Alternatively it may contain a sequence of
                            list item components, <lic>, that identify
                            regularly occurring content, such as the
                            heading and page number of each entry in a
                            table of contents.
Hd.......................  Marks the text of a heading in a <list> or
                            <sidebar>.
note.....................  Marks a footnote, endnote, etc. Any local
                            reference to <note id=''yyy''> is by
                            <noteref idref=''<greek-i>yyy''> [Attribute
                            id].
P........................  Contains a paragraph, which may contain
                            subsidiary <list> or <dl>.
sidebar..................  Contains information supplementary to the
                            main text and/or narrative flow and is often
                            boxed and printed apart from the main text
                            block on a page. It may have a heading <hd>.
cite.....................  Marks a reference (or citation) to another
                            document.
Dd.......................  Marks a definition of the preceding term <dt>
                            within a definition list <dl>. A definition
                            without a preceding <dt> has no semantic
                            interpretation, but is visually presented
                            aligned with other <dd>.
Dl.......................  Contains a definition list, usually
                            consisting of pairs of terms <dt> and
                            definitions <dd>. Any definition can contain
                            another definition list.
Dt.......................  Marks a term in a definition list <dl> for
                            which a definition <dd> follows.
                           Usage Guidelines: please refer to the
                            Information Object references in the Block
                            Elements section in Appendix B,
                            (copyright)DAISY Consortium, 2002.
--------------------------
                           d. Inline Elements
------------------------------------------------------------------------
q........................  Contains a short, inline quotation. Compare
                            with <blockquote>, which marks a longer
                            quotation set off from the surrounding text.
strong...................  Marks stronger emphasis than <em>. Visually
                            <strong> is usually rendered bold.
sub......................  Indicates a subscript character (printed
                            below a character's normal baseline). Can be
                            used recursively and/or intermixed with
                            <sup>.
sup......................  Marks a superscript character (printed above
                            a character's normal baseline). Can be used
                            recursively and/or intermixed with <sub>.
br.......................  Marks a forced line break.
line.....................  Marks a single logical line of text. Often
                            used in conjunction with <linenum> in
                            documents with numbered lines. [Include in
                            baseline element set. Use only when line
                            breaks must be preserved to capture meaning
                            (e.g., poems, legal texts).]
linenum..................  Contains a line number, for example in legal
                            text. [Include in baseline element set. Use
                            only when <line> is used, and only for lines
                            numbered in print book.]
pagenum..................  Contains one page number as it appears from
                            the print document, usually inserted at the
                            point within the file immediately preceding
                            the first item of content on a new page.
                            [NB: Only valid when includes id attribute].
noteref..................  Marks one or more characters that reference a
                            footnote or endnote <note>. Contrast with
                            <annoref>. <noteref> and <note> are
                            independently skippable.
                           Usage Guidelines: please refer to the
                            Information Object references in the Inline
                            Elements section in Appendix B,
                            (copyright)DAISYConsortium, 2002.
--------------------------
                                e. Tables
------------------------------------------------------------------------
table....................  Contains cells of tabular data arranged in
                            rows and columns. A <table> may have a
                            <caption>. It may have descriptions of the
                            columns in <col>s or groupings of several
                            <col> in <colgroup>. A simple <table> may be
                            made up of just rows <tr>. A long table
                            crossing several pages of the print book
                            should have separate <pagenum> values for
                            each of the pages containing that <table>
                            indicated on the page where it starts. Note
                            the logical order of optional <thead>,
                            optional <tfoot>, then one or more of either
                            <tbody> or just rows <tr>. This order
                            accommodates simple or large, complex
                            tables. The <thead> and <tfoot> information
                            usually helps identify content of the
                            <tbody> rows. For a multiple-page print
                            <table> the <thead> and <tfoot> are repeated
                            on each page, but not redundantly tagged.
td.......................  Indicates a table cell containing data.
tr.......................  Marks one row of a <table> containing <th> or
                            <td> cells.
                           Usage Guidelines: please refer to the
                            Information Object references in the Tables
                            section in Appendix B, (copyright)DAISY
                            Consortium, 2002.
--------------------------
                                f. Images
------------------------------------------------------------------------
imggroup.................  Provides a container for one or more <img>
                            and associated <caption>(s) and
                            <prodnote>(s). A <prodnote> may contain a
                            description of the image. The content model
                            allows: 1) multiple <img> if they share a
                            caption, with the ids of each <img> in the
                            <caption imgref=''id1 id2 ...''>, 2)
                            multiple <caption> if several captions refer
                            to a single <img id=``xxx''> where each
                            caption has the same <caption
                            imgref=``xxx''>, 3) multiple <prodnote> if
                            different versions are needed for different
                            media (e.g., large print, Braille, or
                            print). If several <prodnote> refer to a
                            single <img id=``xxx''>, each prodnote has
                            the same <prodnote imgref=``xxx''>.
caption..................  Describes a <table> or <img>. If used with
                            <table> it must follow immediately after the
                            <table> start tag. If used with <img> or
                            <imggroup> it is not so constrained.
                           Usage Guidelines: please refer to the
                            Information Object references in the Images
                            section in Appendix B, (copyright)DAISY
                            Consortium, 2002.
------------------------------------------------------------------------


[[Page 37306]]

1. The Optional Elements and Guidelines for Use

    Publishers are encouraged to apply markup beyond the baseline 
(required) elements. The complete DTBook Element Set reflects the tags 
necessary to create the six types of Digital Talking Books referenced 
in Section II and Braille output. Because of the present necessity to 
subdivide the creation of alternate format materials into distinct 
phases, the Panel determined that baseline elements would be provided 
by publishers, and optional elements would be added to the NIMAS-
compliant files by third party conversion entities. In both 
circumstances the protocols for tagging the digital files should 
conform to the ANSI/NISO Z39.86 specification. For this reason, the 
optional elements beyond the baseline set are included as an Appendix 
C, and content converters are directed to the DAISY Structure 
Guidelines (<a href="http://www.daisy.org/publications/guidelines/sg-daisy3/structguide.htm">http://www.daisy.org/publications/guidelines/sg-daisy3/structguide.htm</a>) for guidance on their use.

2. Package File

    A package file describes a publication. It identifies all other 
files in the publication and provides descriptive and access 
information about them. A publication must include a package file 
conforming to the NIMAS. The package file is based on the Open eBook 
Publication Structure 1.2 package file specification (For most recent 
detail please see <a href="http://www.openebook.org/oebps/oebps1.2/download/oeb12-xhtml.htm#sec2">http://www.openebook.org/oebps/oebps1.2/download/oeb12-xhtml.htm#sec2</a>). A NIMAS package file must be an XML-valid OeB PS 
1.2 package file instance and must meet the following additional 
standards:
    The NIMAS Package File must include the following Dublin Core (dc:) 
metadata:
    <bullet> dc:Title.
    <bullet> dc:Creator (if applicable).
    <bullet> dc:Publisher.
    <bullet> dc:Date (Date of NIMAS-compliant file creation--yyyy-mm-
dd).
    <bullet> dc:Format (=``NIMAS 1.0'').
    <bullet> dc:Identifier (a unique identifier for the NIMAS-compliant 
digital publication, e.g., print ISBN + ``-NIMAS''--exact format to be 
determined).
    <bullet> dc:Language (one instance, or multiple in the case of a 
foreign language textbook, etc.).
    <bullet> dc:Rights (details to be determined).
    <bullet> dc:Source (ISBN of print version of textbook).
    And the following x-metadata items:
    <bullet> nimas-SourceEdition (the edition of the print textbook).
    <bullet> nimas-SourceDate (date of publication of the print 
textbook).
    The following metadata were proposed also as a means of 
facilitating recordkeeping, storage and file retrieval:
    <bullet> dc:Subject (Lang Arts, Soc Studies, etc.).
    <bullet> nimas-grade (specific grade level of the print textbook, 
e.g.; Grade 6).
    <bullet> nimas gradeRange (specific grade range of the print 
textbook, e.g.; Grades 4-5).
    And additional suggestion references the use of:
    <bullet> dc:audience:educationLevel (for the grade and gradeRange 
identifiers, noting that Dublin Core recommends using educationLevel 
with an appropriate controlled vocabulary for context, and recommends 
the U.S. Department of Education's Level of Education vocabulary online 
at <a href="http://www.ed.gov/admin/reference/index.jsp">http://www.ed.gov/admin/reference/index.jsp</a>. Using educationLevel 
obviates the need for a separate field for gradeRange since dc elements 
can repeat more than once. A book used in more than one grade would 
therefore have two elements, one with value ``Grade 4'' and another 
with value ``Grade 5.''
    A final determination as to which of these specific metadata 
elements to use needs to be clarified in practice. The package manifest 
must list all provided files (text, images, etc.). The package spine 
must reference all text content files in order. (Note: For purposes of 
continuity and to minimize errors in transformation and processing, the 
NIMAS-compliant digital text should be provided as a single document.)

[FR Doc. 05-12853 Filed 6-28-05; 8:45 am]
BILLING CODE 4000-01-P</pre>				</div>
			</div>


			<div class="sidebar primary-sidebar">
				<aside data-directive="j-lead" data-type="cornell" data-impression="0">
				</aside>
								<aside class="leads-block -v10 -type1 jcard block">
					<div class="block-wrapper has-no-margin">
						<a data-gtm-type="click" data-gtm-category="Banners" data-gtm-label="Legal Jobs v1" href="https://j.st/4IH2?utm_medium=banner&utm_source=regulations&utm_campaign=legal-jobs-banner&utm_content=legal-jobs-v1"><span>Suscribe Now</span></a>
					</div>
				</aside>
				<aside id="ask-a-lawyer-widget" class="jcard has-padding-content-block-30 block" data-directive="j-ask-a-lawyer">
    <p class="heading-4">
        <a data-gtm-type="click" data-gtm-category="Navigation" data-gtm-action="Sidebar" data-gtm-label="All - Ask a Lawyer" href="https://answers.justia.com/">Ask a Lawyer</a>
    </p>
    <div class="block-wrapper small-font">
		<form data-gtm-type="submission" data-gtm-label="Ask a Lawyer" data-gtm-category="Widgets" name="ask-a-lawyer-form" method="post" action="https://answers.justia.com/ask" id="homepage-ask" accept-charset="utf-8">
			<div class="jfld-group">
				<strong>Question:</strong> <textarea name="question" class="jfld-block" id="ask-a-lawyer-textarea" rows="5" title="Please ask your question here and get free answers from lawyers." placeholder="Please ask your question here and get free answers from lawyers."></textarea> 
			</div>
			<span class="block"> <a id="answers-add-details">Add details</a> 
				<div class="pull-right" id="char-court">
					120
				</div>
			</span> 
			<div class="question-details clear-both hidden-content" id="question-details">
				<div class="jfld-group">
					<strong>Additional Details: </strong> <textarea name="details" id="ask-a-lawyer-details-textarea" rows="5" class="jfld-block" title="If you have additional details about your question fill them here" placeholder="If you have additional details about your question fill them here"></textarea> 
				</div>
				<span class="block"> 
					<div class="pull-right" id="char-court-details">
						1000 
					</div>
				</span> 
			</div>
			<button type="submit" name="submit" class="pull-right button button-primary uppercase"> Ask Question </button> 
		</form>
	</div>
</aside>
<!-- /ask_a_lawyer -->

<aside class="block summaries-banner marginb-20">
    <div class="content-wrapper">
        <p>
            Subscribe to Justia's 
            <strong class="nowrap">
                Free Newsletters
            </strong>
            featuring summaries of federal and state 
            <span class="nowrap">
                court opinions</span>. 
        </p>
        <a data-gtm-type="click" data-gtm-category="Banners" data-gtm-label="Summary Newsletters Banner"  class="button button-xlarge button-contrast has-no-border" href="https://daily.justia.com?utm_medium=banner&utm_source=regulations&utm_campaign=summary-newsletters-banner&utm_content=generic">
            Subscribe Now
        </a>
    </div>
</aside>

    <aside class="jcard has-padding-content-block-30 block">
        <p class="heading-4">
                      <a href="https://www.justia.com/lawyers" data-gtm-type="click" data-gtm-category="Navigation" data-gtm-action="Sidebar" data-gtm-label="Find a Lawyer"   id="findalawyerlawlink">
                Find a Lawyer
              </a>
                    </p>
        <div class="block-wrapper">
            <form data-gtm-type="submission" data-gtm-label="Find a Lawyer" data-gtm-category="Widgets" name="find-a-lawyer-form" class="jform small-font jform--find-lawyer" action="//lawyers.justia.com/search" method="get" accept-charset="utf-8">
                <div class="jfld-group">
                    <input type="text" name="query" value="" id="lawyer_practice_field" title="Legal Issue or Lawyer Name" placeholder="Legal Issue or Lawyer Name" class="jfld-block">
                </div>
                <div class="jfld-group -side-button clearfix">
                    <input type="text" name="location" value="" id="lawyer-location" title="City, State" placeholder="City, State">
                    <input type="submit" value="Search" class="button button-primary search uppercase">
                </div>
            </form>

            <div class="text-center clear-both">
                <strong class="heading-6 has-no-bottom-margin"><a data-gtm-type="click" data-gtm-category="Navigation" data-gtm-action="Sidebar" data-gtm-label="All - Lawyers - Get Listed Now!" href="https://lawyers.justia.com/lawyer-directory-listings" class="button button-red-ghost">Lawyers - Get Listed Now!</a></strong>
                <span class="tiny-font">Get a free directory profile listing</span> 
            </div>
        </div>
    </aside>

<aside data-directive="j-find-a-lawyer" data-practice=""  data-level="300"></aside>

 			</div><!-- /sidebar -->
		</div><!-- /main -->
		<footer class="footer">
			<div>
							</div><!-- /footer -->
		</footer>

	</div>

	<div id="footer" class="-v2 short bg-white color-black">
    <div class="wrapper has-no-padding">
        <div class="resources font-opensans has-padding-content-block-x2large clearfix">
            <div class="section-title">Justia Legal Resources</div>
            <div class="columns" data-gtm-children="Footer Resources">
                <div class="footer-block">
                    <div class="title">
                        <a title="Find a Lawyer" href="https://www.justia.com/lawyers">Find a Lawyer</a>
                        <span class="expand" data-directive="j-expand" data-section="footer-01">
                            <img src="https://justatic.com/v/20200929135607/shared/images/icons/svgfiles/blue/down.svg" alt="Arrow">
                        </span>
                    </div>
                    <ul id="footer-01" class="footer-list -collapsed">
                        <li><a title="Bankruptcy Lawyers" href="https://www.justia.com/lawyers/bankruptcy">Bankruptcy Lawyers</a></li>
                        <li><a title="Business Lawyers" href="https://www.justia.com/lawyers/business-law">Business Lawyers</a></li>
                        <li><a title="Criminal Lawyers" href="https://www.justia.com/lawyers/criminal-law">Criminal Lawyers</a></li>
                        <li><a title="Employment Lawyers" href="https://www.justia.com/lawyers/employment-law">Employment Lawyers</a></li>
                        <li><a title="Estate Planning Lawyers" href="https://www.justia.com/lawyers/estate-planning">Estate Planning Lawyers</a></li>
                        <li><a title="Family Lawyers" href="https://www.justia.com/lawyers/family-law">Family Lawyers</a></li>
                        <li><a title="Personal Injury Lawyers" href="https://www.justia.com/lawyers/personal-injury">Personal Injury Lawyers</a></li>
                        <li><a title="Find a Lawyer - More" href="https://www.justia.com/lawyers">More... </a></li>
                    </ul>
                </div>
                <div class="footer-block">
                    <div class="title">
                        <a title="Individuals" href="https://www.justia.com/individuals/">Individuals</a>
                        <span class="expand" data-directive="j-expand" data-section="footer-02">
                            <img src="https://justatic.com/v/20200929135607/shared/images/icons/svgfiles/blue/down.svg" alt="Arrow">
                        </span>
                    </div>
                    <ul id="footer-02" class="footer-list -collapsed">
                        <li><a title="Bankruptcy" href="https://www.justia.com/bankruptcy/">Bankruptcy</a></li>
                        <li><a title="Criminal" href="https://www.justia.com/criminal/">Criminal</a></li>
                        <li><a title="Divorce" href="https://www.justia.com/family/divorce/">Divorce</a></li>
                        <li><a title="DUI" href="https://www.justia.com/criminal/drunk-driving-dui-dwi/">DUI</a></li>
                        <li><a title="Estate Planning" href="https://www.justia.com/estate-planning/">Estate Planning</a></li>
                        <li><a title="Family Law" href="https://www.justia.com/family/">Family Law</a></li>
                        <li><a title="Personal Injury" href="https://www.justia.com/injury/">Personal Injury</a></li>
                        <li><a title="Individuals - More" href="https://www.justia.com/individuals/">More...</a></li>
                    </ul>
                </div>
                <div class="footer-block">
                    <div class="title">
                        <a title="Business" href="https://www.justia.com/business/">Business</a>
                        <span class="expand" data-directive="j-expand" data-section="footer-03">
                            <img src="https://justatic.com/v/20200929135607/shared/images/icons/svgfiles/blue/down.svg" alt="Arrow">
                        </span>
                    </div>
                    <ul id="footer-03" class="footer-list -collapsed">
                        <li><a title="Business Formation" href="https://www.justia.com/business-formation/">Business Formation</a></li>
                        <li><a title="Business Operations" href="https://www.justia.com/business-operations/">Business Operations</a></li>
                        <li><a title="Employment" href="https://www.justia.com/employment/">Employment</a></li>
                        <li><a title="Intellectual Property" href="https://www.justia.com/intellectual-property/">Intellectual Property</a></li>
                        <li><a title="International Trade" href="https://www.justia.com/international-trade/">International Trade</a></li>
                        <li><a title="Real Estate" href="https://www.justia.com/real-estate/">Real Estate</a></li>
                        <li><a title="Tax Law" href="https://www.justia.com/tax/">Tax Law</a></li>
                        <li><a title="Business - More" href="https://www.justia.com/business/">More... </a></li>
                    </ul>
                </div>
                <div class="footer-block">
                    <div class="title">
                        <a title="Law Students" href="https://www.justia.com/law-students/">Law Students</a>
                        <span class="expand" data-directive="j-expand" data-section="footer-04">
                            <img src="https://justatic.com/v/20200929135607/shared/images/icons/svgfiles/blue/down.svg" alt="Arrow">
                        </span>
                    </div>
                    <ul id="footer-04" class="footer-list -collapsed">
                        <li><a title="Law Schools" href="https://www.justia.com/law-schools/">Law Schools</a></li>
                        <li><a title="Admissions" href="https://www.justia.com/law-students/">Admissions</a></li>
                        <li><a title="Financial Aid" href="https://www.justia.com/law-students/">Financial Aid</a></li>
                        <li><a title="Course Outlines" href="https://www.justia.com/law-schools/outlines.html">Course Outlines</a></li>
                        <li><a title="Law Journals" href="https://www.justia.com/law-schools/">Law Journals</a></li>
                        <li><a title="Blogs" href="https://blawgsearch.justia.com/blogs/categories/law-student">Blogs</a></li>
                        <li><a title="Employment" href="https://www.justia.com/law-students/">Employment</a></li>
                        <li><a title="Law Students - More" href="https://www.justia.com/law-students/">More...</a></li>
                    </ul>
                </div>
                <div class="footer-block">
                    <div class="title">
                        <a title="US Federal Law" href="https://law.justia.com/federal/">US Federal Law</a>
                        <span class="expand" data-directive="j-expand" data-section="footer-05">
                            <img src="https://justatic.com/v/20200929135607/shared/images/icons/svgfiles/blue/down.svg" alt="Arrow">
                        </span>
                    </div>
                    <ul id="footer-05" class="footer-list -collapsed">
                        <li><a title="US Constitution" href="https://law.justia.com/constitution/us/">US Constitution</a></li>
                        <li><a title="US Code" href="https://law.justia.com/codes/us">US Code</a></li>
                        <li><a title="Regulations" href="https://regulations.justia.com/">Regulations</a></li>
                        <li><a title="Supreme Court" href="https://supreme.justia.com/">Supreme Court</a></li>
                        <li><a title="Circuit Courts" href="https://law.justia.com/cases/federal/appellate-courts/">Circuit Courts</a></li>
                        <li><a title="District Courts" href="https://law.justia.com/cases/federal/district-courts/">District Courts</a></li>
                        <li><a title="Dockets & Filings" href="https://dockets.justia.com/">Dockets & Filings</a></li>
                        <li><a title="US Federal Law - More" href="https://law.justia.com/federal/">More...</a></li>
                    </ul>
                </div>
                <div class="footer-block">
                    <div class="title">
                        <a title="US State Law" href="https://law.justia.com/us-states/">US State Law</a>
                        <span class="expand" data-directive="j-expand" data-section="footer-06">
                            <img src="https://justatic.com/v/20200929135607/shared/images/icons/svgfiles/blue/down.svg" alt="Arrow">
                        </span>
                    </div>
                    <ul id="footer-06" class="footer-list -collapsed">
                        <li><a title="State Constitutions" href="https://law.justia.com/us-states/">State Constitutions</a></li>
                        <li><a title="State Codes" href="https://law.justia.com/codes/">State Codes</a></li>
                        <li><a title="State Case Law" href="https://law.justia.com/cases/">State Case Law</a></li>
                        <li><a title="California" href="https://law.justia.com/california/">California</a></li>
                        <li><a title="Florida" href="https://law.justia.com/florida/">Florida</a></li>
                        <li><a title="New York" href="https://law.justia.com/new-york/">New York</a></li>
                        <li><a title="Texas" href="https://law.justia.com/texas/">Texas</a></li>
                        <li><a title="US State Law - More" href="https://law.justia.com/us-states/">More... </a></li>
                    </ul>
                </div>
                <div class="footer-block">
                    <div class="title">
                        <a title="Other Databases" href="https://www.justia.com/">Other Databases</a>
                        <span class="expand" data-directive="j-expand" data-section="footer-07">
                            <img src="https://justatic.com/v/20200929135607/shared/images/icons/svgfiles/blue/down.svg" alt="Arrow">
                        </span>
                    </div>
                    <ul id="footer-07" class="footer-list -collapsed">
                        <li><a title="Legal Blogs" href="https://blawgsearch.justia.com/">Legal Blogs</a></li>
                        <li><a title="Legal Forms" href="https://forms.justia.com/">Legal Forms</a></li>
                        <li><a title="GAO Reports" href="https://gao.justia.com/">GAO Reports</a></li>
                        <li><a title="Product Recalls" href="https://recalls.justia.com/">Product Recalls</a></li>
                        <li><a title="Patents" href="https://patents.justia.com/">Patents</a></li>
                        <li><a title="Trademarks" href="https://trademarks.justia.com/">Trademarks</a></li>
                        <li><a title="Countries" href="https://www.justia.com/countries/">Countries</a></li>
                        <li><a title="Other Databases - More" href="https://www.justia.com/">More...</a></li>
                    </ul>
                </div>
                <div class="footer-block">
                    <div class="title">
                        <a title="Legal Marketing" href="https://www.justia.com/marketing/">Legal Marketing</a>
                        <span class="expand" data-directive="j-expand" data-section="footer-08">
                            <img src="https://justatic.com/v/20200929135607/shared/images/icons/svgfiles/blue/down.svg" alt="Arrow">
                        </span>
                    </div>
                    <ul id="footer-08" class="footer-list -collapsed">
                        <li><a title="Law Firm Websites" href="https://www.justia.com/marketing/law-firm-websites/">Law Firm Websites</a></li>
                        <li><a title="Lawyer Blogs" href="https://www.justia.com/marketing/law-blogs/">Lawyer Blogs</a></li>
                        <li><a title="Content" href="https://www.justia.com/marketing/content/">Content</a></li>
                        <li><a title="Social Media" href="https://www.justia.com/marketing/social-media-networking/">Social Media</a></li>
                        <li><a title="Local Marketing" href="https://www.justia.com/marketing/local-marketing/">Local Marketing</a></li>
                        <li><a title="Paid Ads (CPC/PPC)" href="https://www.justia.com/marketing/cpc-ppc/">Paid Ads (CPC/PPC)</a></li>
                        <li><a title="Lawyer Directory" href="https://www.justia.com/marketing/lawyer-directory/">Lawyer Directory</a></li>
                        <li><a title="Legal Marketing - More" href="https://www.justia.com/marketing/">More...</a></li>
                    </ul>
                </div>
            </div>
        </div>
    </div>
    <div class="bg-justia-blue">
        <div class="wrapper">
            <div class="copyright">
                <span class="site"> 
                    <span class="social-media" data-gtm-children="Footer Social Media">
                        <a href="https://www.facebook.com/justia" title="Facebook" target="_blank" class="fb icon">
                            <img src="https://justatic.com/v/20200929135607/shared/images/icons/version2/social/facebook.svg" width="50" height="50" alt="Facebook">
                        </a>
                        <a href="https://twitter.com/justiacom" title="Twitter" target="_blank" class="twitter icon">
                            <img src="https://justatic.com/v/20200929135607/shared/images/icons/version2/social/twitter.svg" width="50" height="50" alt="Twitter">
                        </a>
                        <a href="https://www.linkedin.com/company/justia" title="LinkedIn" target="_blank" class="linkedin icon">
                            <img src="https://justatic.com/v/20200929135607/shared/images/icons/version2/social/linkedin.svg" width="50" height="50" alt="LinkedIn">
                        </a>
                        <a href="https://lawyers.justia.com/organization/justia-inc-16302" title="Justia Lawyer Directory" class="justia icon">
                            <img src="https://justatic.com/v/20200929135607/shared/images/icons/version2/social/justia.svg" width="50" height="50" alt="Justia">
                        </a>
                    </span>
                    <span class="credits" data-gtm-children="Footer Copyright">© 2020 <a href="https://www.justia.com/">Justia</a></span>
                </span>
                <span class="nav" data-gtm-children="Footer Navigation">
                    <a href="https://www.justia.com/">Legal Portal</a>
                    <a href="https://company.justia.com/">Company</a> 
                    <a href="https://support.justia.com/">Help</a>
                    <a href="https://www.justia.com/terms-of-service/">Terms of Service</a> 
                    <a href="https://www.justia.com/privacy-policy/">Privacy Policy</a> 
                    <a class="nowrap" href="https://www.justia.com/marketing/contact/">Marketing Solutions</a> 
                </span> 
            </div>
        </div>
    </div>
</div>
	<script>
var CodesTitles={hide_class:null,init:function(e,t){var n=this;n.hide_class=t;n.generateButtons(e);n.initButtons()},generateButtons:function(e){$(e).each(function(e,t){$(t).find("> a",0).before('<span class="us_codes_expand">+ </span>')})},initButtons:function(){var e=this;$(".us_codes_expand").click(function(){var t=$(this);if(t.parent().hasClass(e.hide_class)){t.parent().removeClass(e.hide_class);t.text("- ");return}t.parent().addClass(e.hide_class);t.text("+ ")})}};$(document).ready(function(){CodesTitles.init(".us_codes_has_children","us_codes_hide_children");$("#metadata").hide();$("a#metadata-link").click(function(e){e.preventDefault();$("#metadata").slideToggle(400);$(this).text($(this).text()=="View Metadata"?"Hide Metadata":"View Metadata");return false});$(".rsssubdrop").mouseover(function(){$("#TW-pop").show();return false}).mouseout(function(){$("#TW-pop").hide();return false});var e=$("div.citation").text().replace("What's This?","");var t=$("div.citation a").attr("href");var n='<b>Universal Citation: </b><a href="'+t+'">'+e+"</a>";$("div.citation").html(n)})
</script>
<script src="https://justatic.com/v/20200929135607/shared/js/core.js"></script>



	
</body>

</html>