Redefining Multichannel Content Publishing
Following the release of the nextPub XML Source Content Specification, the nextPub Working Group will begin the task of developing transformation and packaging guidelines for delivering content across a wide variety of media channels, including enhanced e-readers using EPUB3, HTML5 browsers and even to print engines.
PRISM 3.0 Metadata to Organize Content
As the nextPub Working Groups began the design of the XML Source, it was clear that metadata and content encoding must both be defined. PRISM, the IDEAlliance metadata framework, was the obvious choice for metadata capture; it has been widely adopted across the magazine publishing community since its initial release in 2001. It is built in modules and, at this time, includes fields to describe magazine and serial publication content. In addition, PRISM includes new modules that provide detailed descriptions of usage rights, digital images and even recipes and advertising.
Because PRISM has a strong philosophy to not "reinvent the wheel," it includes subsets from other established metadata specifications including Dublin Core, International Press Telecommunications Council's (IPTC) Information Interchange Model (IIM), AdsML, Ghent PDF Workgroup (GWG) and even hRecipe. PRISM is constantly adding modules to meet the needs of the IDEAlliance membership. New metadata sets scheduled for development in 2012 include short-form video, projects such as crafts and home improvement, marketing and metadata specific to textbooks and educational materials.
HTML5 Content Encoding
Another challenge for the nextPub Working Group has been to develop a tagging scheme to encode semantically rich, platform-agnostic content. Initially, the thought was to extend the PRISM XML tag set known as PAM (PRISM Aggregator Message) for this purpose. As work progressed, and more use cases were developed, it became clear that the use case for the PAM XML tag set was quite different from the scenarios driving nextPub development.