“If MathML is not present, then metadata must not be present that indicates that it is (for example, automated processes must not add MathML metadata by default).”
one or more of dc:Identifier (no format specified)
one or more of dc:Language
Special NIMAS consideration:
dc:Format =”NIMAS 1.1”
one or more of dc:Rights
one or more of dc:Source
nimas-SourceEdition (under x-metadata)
nimas-SourceDate (under x-metadata)
Verify that all PDFs linked to from the package document exist on disk
Verify that that the package document references at least one item of type application/pdf
This script CANNOT
Validate the contents of the PDF or image files
Check if the XML content file contains an updated DTD containing the MathML module
Caveats
We only verify the presence of PDF and image files; we do not verify that all linked files exist on disk.
dc:Date is validated as an ISO-8601 formatted date. This is more lenient than what NIMAS says (yyyy-mm-dd), as it would also allow yyyymmdd.
RelaxNG validation results sometimes give incorrect line and column numbers. This is a known issue with Jing.
Notes about NIMAS
NIMAS element markup is a subset of DTBook
Package file has more required metadata than in DAISY
DTBook requirements:
“The DTBook DTD must be updated to include the MathML module.”
“The actual math content itself is provided, encoded in MathML, within the XML source file.”
MathML in NIMAS points to version MathML v3 whereas MathML in DAISY points to version MathML v2. We support both.
Requires the use of @alttext, @altimg on the Math element (as does MathML in DAISY)
Says “the XSLT file must be present and must be listed in the package file” (mime type application/xslt+xml). Note that OPF schema allows application/xml as well. We follow the stricter NIMAS requirement but could consider relaxing it.
Fileset overview
XML content file
Package file (OPF)
PDF-format copy of title page and ISBN and copyright information pages
Full set of content images in SVG, JPG, or PNG format.