Sample: Bridging the Web and Digital Publishing


Click to go to the sample
Click to go to the sample

This post is part of the series – 2015_08_samples. Other posts:
  1. Introduction: Time to Move Forward
  2. Sample: Advancing Portable Documents for the Open Web Platform: Epub+Web
  3. Sample: Bridging the Web and Digital Publishing (Current)
  4. Sample of “5DOC Book ” – Art Book
  5. Sample: Looking Below the Surface

While it looks completely different than our EPUB+WEB specification sample, the first part of the series, it is still a 5DOC because the only technical requirement to be a 5DOC is a button to download the file. That and it has to be an HTML5 document of course.

In this way, a 5DOC takes after PDF – it represents a single abstraction. While PDF is a takeaway of the printed page, 5DOC is a takeaway of a web page or pages. Plus a 5DOC is also capable of delivering identifiable structured content.

Of course, it is highly desireable for the EPUB+WEB spec to deliver many more features as described in this and the previous sample, but why create unnecessary barriers and technical deconstructs when in reality it’s the download button and that’s it?


Sample: HTMLBook Documentation


Note (11 November 2015): this sample has been unpublished due to a change in approach by 5DOC for producing content with code syntax highlighting. Previously, 5DOC used a WordPress plugin and abstracted the relevant code for the 5DOC downloaded version.

Over time it has become obvious that in fact each sample has a different approach to code syntax highlighting and the goal should be flexibility not consistency. All links below initially to the 5DOC sample, now link to the original content.


HTMLBook–Unofficial Draft by O’Reilly Media, Inc proposes a standard for an HTML5 book based on XHTML5. This online sample is now available for download and offline use.

Arguments about HTML5 vs XHTML5 are about as clear as a discussion of the difference between General Motors and Opel. Once the “scout” in you indulges in learning, you then discover you have wasted your time. Gut instinct: go with HTML5. Here is one debate.

We have to ask ourselves what is the point? IMHO too much effort is made to make things complicated and less useful–to stay within known parameters. But why do we need e-readers when we have browsers and why do we need XHTML5 when we have JSON? is busy developing the capability to represent WordPress content with JSON Rest API. And there is already interest in extracting JSON from EPUB. So it is very realistic to project the capability to go from WordPress ⇔ HTML5 and from other forms of data structure ⇒ (WordPress || HTML5).