Redefining Multichannel Content Publishing
Today, publishers that have implemented content management, based on PRISM metadata, are storing articles. For nextPub, the scope has changed from magazine article content to any standalone content unit, including the cover, navigation aids such as the contents, page or section views that are commonly found in tablet editions, recipes, puzzles, cartoons and advertisements.
The scope for nextPub also has changed from addressing magazine/serial content to all collection types where content may be aggregated and delivered. Altogether, nextPub addresses the creation of display books, textbooks and a wide variety of other publication types, as well as magazines.
The "where used" metadata block is specifically designed to track content usage across platforms, publications or aggregation types. Part of the nextPub specification effort was to not only define new metadata fields for the PRISM specifications, but develop many new controlled vocabularies that provide standardized industry field values.
When it comes to the model for coding nextPub content units, a valid HTML5 subset has been developed. While some forced restrictions to HTML5 exist, nextPub has not defined any extensions. The goal is to enable any HTML5 browser-based display mechanism to process raw nextPub content without plug-ins or customization. This is a major difference between the nextPub and the EPUB 3 strategy, which requires a conformant EPUB 3 reader technology to render content.
nextPub for Books and More
The nextPub Initiative builds on lessons learned in magazine publishing, but in no way is exclusive to this publishing vertical market. Moving away from the current PRISM XML model for encoding magazine articles further underlines the fact that this effort is inclusive of many more publication types than magazines.
Several metadata fields enable publishers to specify the type of source content and refine how the content is chunked and stored for use and reuse. The first of these metadata fields is the prism:aggregationType field that is used to specify the type of content in a repository. Types supported by nextPub include: blog; feed; newsletter; pamphlet; book; journal; newspaper; vook; bookazine; magazine; whitepaper; catalog; manual; report.