Your SlideShare is downloading. ×
nextPub, A Specification of IDEAlliance
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.


Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

nextPub, A Specification of IDEAlliance


Published on

Published in: Technology

1 Comment
  • It's weird. Whether it is a format (use extension like .nextpub ), or an intermediary file ( just a xml file for transform) ? I support all digital publication using one format, means future Reading System only need to identify one, and I think it'll be EPUB (3, 4 or 5...). If nextPub is trying to build another format like .folio, PDF or any others. It will die. We should let it die.
    Are you sure you want to  Yes  No
    Your message goes here
  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. Getting into the weeds . . . . ..
  • 2. The Future of Publishing• In many ways, the iPad has made the vision for the future of publishing very real
  • 3. Just the Beginning . . .
  • 4. So What’s the Solution?• New digital delivery devices for magazines• New layouts and functionality• Our current workflows are not sustainable with multiple outputs requiring many cycles of design and editing per platform• How can we move toward? – an XML driven content creation process – Programmatic /dynamic display driven by emerging technologies
  • 5. Today’s Dilemma
  • 6. Standards for Scalability!• We cannot afford the level of effort to create the iPad edition for each new tablet that comes to market• So establishing standards for the future is critical
  • 7. Introducing nextPub™• nextPub™ is a new family of IDEAlliance specifications designed to simplify the production of multi-channel content• nextPub™ is defining best practices and recommendations that publishers can use to deliver magazines and other rich content across platforms and devices efficiently
  • 8. Those Involved• Condè Nast• Hearst Magazines• Meredith Corporation• Reader’s Digest• Rodale• Rogers• Time, Inc.• Wolters Kluwer• U.S. News & World Report
  • 9. Principle #1: Build on Today’s Standards
  • 10. Why Build on Standards?• Pool the experience of many companies and reflect best practices• Wide, ongoing industry oversight identifies weaknesses and anticipate trends• Off-the-shelf tools and technologies are built on standards
  • 11. Principle #2: Build on PRISM XML• The IDEAlliance PRISM Specification was launched in 1999 when XML had just become a W3C Recommendation• Even then we could imagine the future that the iPad has made a reality• Most Publishers have already invested in PRISM XML
  • 12. Principle #3: Employ Emerging Technologies
  • 13. Principle #4: Seek Broad Industry Collaboration
  • 14. ePub: Print Books to DigitalePub defines the delivery packaging and format for books on eReaders
  • 15. PRISM: Print Magazines to Digital XML PRISM XML is used to deliver magazine content to aggregator channels
  • 16. nextPub™ ties it all together XMLEmploying W3C standards, nextPub takes PRISM and ePub to the next level, making the best of both
  • 17. nextPub™ Defines• XML source content, based on PRISM, and capable of driving publishing on any platform – Robust data about each article • Content management • Usage Rights • Search • Aggregate / Monetize – Rich article content coding • Not just headings and paragraphs • Title, teasers, deck, sidebars, captions, credits and more!
  • 18. nextPub™ will Recommend:• Standards for encoding layout and formatting of content, rich media and ads – HTML5 – Java Script – CSS3 – RDFa – ePub3• Packaging for delivery of all components of a magazine to digital publishing platforms• Transformations from PRISM XML to nextPub for delivery
  • 19. What Expertise Do We Need?• eMedia Technologies including XML, PRISM, DAM and nextPub• Emerging Technologies including HTML5, CSS3, RDFa• Understanding techniques, tools and services to transform and deliver PRISM XML for display on digital devices
  • 20. Moving Forward• We are in the “early” days – Experimentation – Emerging standards• Participate with the nextPub community to: – Track emerging technologies and tools that support them – Train publishing technology staff – Develop new workflows based on an XML-driven content creation process – Develop best practices that efficiently drive programmatic /dynamic displays
  • 21. To Participate• Dianne Kennedy•• 630-941-8197