The XHTML document type defined by this specification is based on W3C [HTML5], and inherits all definitions of semantics, structure and processing behaviors from the HTML5 specification unless otherwise specified.
Not exact matches
Instead, for navigation, it uses an
xhtml document (toc.
xhtml), with an epub:
type of toc.
Here I defined a
document with an unsupported media -
type (text / html) and a fallback in a supported
type (application /
xhtml + xml).
Publication Resources referenced from
XHTML and SVG Content
Documents and CSS must now be Core Media
Types unless referenced in a context that provides native intrinsic fallback capabilities.
The switch mechanism encourages this
type of development and experimentation, but at the same time provides Authors who wish to take advantage of it the security of knowing that their content will still display on any compliant Reading System (i.e., it maintains the baseline requirement that all
XHTML Content
Documents be valid if none of the specialized markup is supported).
The [HTML5] object element should be used to embed custom (non-core) content
types in
XHTML Content
Documents.
This specification defines a method for semantic inflection using the attribute axis: instead of adding new XML elements to the
XHTML Content
Document vocabulary, the epub:
type attribute can be appended to existing elements to inflect the desired semantics.
PLS
Documents must be associated with the
XHTML Content
Document to which they apply using the [HTML] link element with its rel attribute set to «pronunciation» and its
type attribute set to the PLS media
type «application / pls + xml».
' PLS
Documents must be associated with the
XHTML Content
Document to which it applies using the [HTML5] link element with its rel attribute set to pronunciation and its
type attribute set to the PLS media
type (application / pls + xml).
Simple enough, I just create an
xhtml page containing the javascripted equivalent functionality and bind that to the slideshow media
type in the package
document:
What bindings do is allow you to attach a scripted
XHTML document to another media
type as a first fallback.
It's hard to guess without seeing the file, but if you're linking from one
xhtml document to another you probably don't have the right media
type on the manifest entry for the second.
Since the fallback is going to be an
XHTML or SVG
document containing the resource, there's almost no point in bothering to reference core media
types directly.
This indicated that the root element would be «'', and that the
Document Type Definition (DTD) was «
XHTML 1.0 Transitional».
This indicated that the root element would be «», and that the
Document Type Definition (DTD) was «
XHTML 1.0 Transitional».