Redefining Multichannel Content Publishing
Throughout 2011, nextPub hosted numerous technology demonstrations where suppliers provided nextPub members early access to developing products. These brainstorming sessions provided a forum where publishers shared their visions for the next-generation technology solutions they'll need in order to make platform- and device-agnostic publishing workflows a reality.
During 2011, nextPub working groups developed Version 1.0 of the nextPub specifications that form the foundation for new, platform-agnostic workflows. At the heart of nextPub is the nextPub XML Source Content Encoding Specification. This specification defines semantically rich, platform-agnostic content vocabulary and a rich media encoding schema. It combines enhanced PRISM 3.0 (Publishing Requirements for Industry Standard Metadata) metadata along with the power of HTML5 to encode all the components that make up a publication─from the cover to the masthead to navigation devices to articles or chapters, and to advertising materials. nextPub Source was designed to support efficient aggregation and production of multichannel content while preserving the publisher's ability to distinctively brand the look and feel.
Defining Future Workflows
The nextPub publishing paradigm is based on establishing a nextPub content repository and employing nextPub "Rosetta Stone" transformations to drive a new generation of production technologies capable of automating branded layout and styling for published products. For some publications, an XML-first workflow is envisioned. For those publications where design is as critical as the text and rich media content, XML-early workflows are imagined. In either case, the concept is to store semantically rich, platform-agnostic source content in a nextPub repository so that content can be selected, transformed, formatted, packaged and served to any delivery channel in a highly automated fashion.
The nextPub XML Source Content Encoding Specification defines XML elements and attributes to encode source content. The metadata fields and values in this specification are drawn from the new IDEAlliance PRISM 3.0 Metadata and Controlled Vocabulary Specifications. A draft of this specification was released on Dec. 15, 2011, for public comment; it will be finalized in February by the nextPub Working Group.