STG LogoBrown University
Scholarly Technology Group
Home | Validate | Sample | What it Does | Why | HTML/OEB |  Identifying OEB Documents |  Conformance Rules

Identifying OEB Documents and Packages

OEB documents should begin as follows:

<?xml version='1.0' ?>
<!DOCTYPE html PUBLIC
    "+//ISBN 0-9673008-1-9//DTD OEB 1.0.1 Document//EN"
    "http://openebook.org/dtds/oeb-1.0.1/oebdoc1.dtd">
       

Conformant OEB 1.0.1 documents and packages must be encoded as either UTF-8 or UTF-16. Documents encoded as UTF-16 should begin in the same fashion, but with an encoding declaration added to the XML declaration:

<?xml version='1.0' encoding='UTF-16' ?>

OEB packages work similarly, but utilize different PUBLIC and SYSTEM identifiers:

<?xml version='1.0' ?>
<!DOCTYPE package PUBLIC
   "+//ISBN 0-9673008-1-9//DTD OEB 1.0.1 Package//EN"
   "http://openebook.org/dtds/oeb-1.0.1/oebpkg1.dtd">

Using Relative URIs in DOCTYPE Declarations

If your document or package uses a relative URI in its DOCTYPE declaration (e.g., oebpkg1.dtd in place of http://openebook.org/dtds/oeb-1.0.1/oebpkg1.dtd), this facility will abort with an error message because it is not always possible to verify that the URI you are using points to a DTD that is equivalent to the canonical OEB DTD. As long as your public identifier is given as above, you may bypass verification of the system identifier by checking the "bypass check of DOCTYPE system identifier" box on the validation forms.


 1999 Brown University and NuvoMedia, Inc.
Send comments to oebvalid@nuvomedia.com