Not exact matches
eXeLearning can generate interactive contents in
XHTML or HTML5 format and it
allows you to create easily navigable web pages including text, images, interactive activities, image galleries or multimedia clips.
The use of [RDFa 1.1] attributes is
allowed in
XHTML Content Documents, but any usage must conform to the requirements defined in [HTML+RDF a11].
The initial sync of the EPUB book from iTunes takes care of this part,
allowing you to modify an individual
XHTML or CSS file using the technique described rather than having to rebundle EPUBs after edits and re-sync.
The switch element
allows an XML fragment to be conditionally inserted into the content model of an
XHTML Content Document.
The use of [Microdata] attributes is
allowed in
XHTML Content Documents, but any usage must conform to the requirements defined in that specification.
You can use them for EPUB 2 compliance (SVG with
XHTML fallbacks, as SVG wasn't
allowed in the spine previous), and even for script-less reading systems (fallback from an EPUB 3 - compliant
XHTML content document marked as scripted to another EPUB 3 - compliant
XHTML content document not marked as scripted).
What bindings do is
allow you to attach a scripted
XHTML document to another media type as a first fallback.
And once again, since only
XHTML and SVG content documents are
allowed in the spine without fallbacks, you either have to wrap the resource up as
XHTML or SVG or provide a fallback.
It
allows you to create your E-book in PDF and
XHTML formats, then encrypt it so that that you can manage who is able to receive and read your document.
EPUB 3.1 includes metadata that
allows the creation of fixed - layout
XHTML Content Documents [Packages 3.1], in addition to existing capabilities for fixed layouts in SVG.
The use of [EPUBCFI] expressions is strongly encouraged over other fragment identifier schemes (particularly in the context of reflowable
XHTML Content Documents), as they
allow Reading Systems to ingest Rendition Mappings without any prior pre-processing.
The lack of a rendering context means that the
XHTML content model for this document is very restrictive,
allowing only a single nav element in the body, to ease both authoring and processing.
This attribute
allows any element in an
XHTML Content Document to include additional information about its purpose and meaning within the work, using controlled vocabularies and terms.
Comment Guidelines: Basic
XHTML is
allowed (a href, strong, em, code).