Welcome to our blog

books on a shelf icon

September 14, 2022 • 1 minute read
By: Mike Hale, Ph.D., Chief Learning and Content Officer

VitalSource has long been committed to increasing student success through easy access to affordable content. We also believe that if you can, you must improve learning for students and expand educational opportunities for all learners. Of course, we are not alone in this view and it is the reason many companies have built assessment-rich course materials. 

Insight-icon
VitalSource Insights
Whitepapers, infographics, case studies, and more
Browse
events
Events
VitalSource webinars and conferences
Connect
Blog > Goodbye Dash, Hello EPUB!

January 26, 2018 • 2 minute read

Goodbye Dash, Hello EPUB!

US_Blog_950_product updates

Share:

Outrider- Star Wars Recently, VitalSource retired our venerable, 18-year-old proprietary ebook format, known as Dash, DashML or VitalSource XML. As part of Dash’s retirement ceremony, we transitioned students using Dash books to EPUB versions, seamlessly maintaining all of their licenses, bookmarks, notes and highlights to make sure the big change, years in the making, was painless.

Engineering work on Dash began all the way back in 1997 with the (then quite risky!) decision to go with the new XML format for our product, rather than the “industry standard” at the time, SGML. Creating the format was what lead us to develop the flexible VitalBook format (for which we received a patent in the United States, Australia, Canada, The Peoples Republic of China, The European Union, Hong Kong, and India) in 2004. Dash survived for years – through the launch of our early apps VitalViewer and vitalsource KEY, and of course it was the first format built into our popular Bookshelf textbook apps still available today.

Dash was a hit with students – unlike PDFs, Dash supported a reflowable, responsive reading experience for different devices sizes, font sizes or layouts. It provided rich semantic markup, giving students an accessible eTextbook that could be read aloud using a screen reader more than a decade ahead of anyone else in the industry. Students could also explore figures and their captions, look up term definitions, and watch embedded videos. Surprisingly to many, we also had our own MathML renderer built into Dash, long before it was supported by any web browsers.

But Dash wasn’t easy. To build the custom XML needed to power Dash, the first books we released in those early years had to be physically shipped to India (2 copies…) and then manually marked up word by word, image by image. Rarely did most publishers have a full electronic copy in those days, and if it did exist, many did not even own the rights to that file. Keep in mind the Amazon Kindle wasn’t launched until late 2007!

Digital books have since been widely embraced. Along with more apps and more readers has come much better support for ebook standard formats, and better content publishing pipelines for our partners. We have championed EPUB as a quality open standard to anyone who will listen for years and it has been great to see publishers adopt the format at scale. In fact, EPUB was our most read format in 2017 – over 3 billion pages were read in Bookshelf last year, and 46% of them were read in an EPUB.

Better yet, with our industry-leading support for EPUB 3, an EPUB in Bookshelf can support everything Dash could support and more – rich media, interactives, quiz questions, activities, and anything under the sun that can help students learn can be added to an EPUB 3. So, sadly, it is time for Dash to retire – our last Dash page read was logged on December 9, 2017. But EPUB is here to stay!

Finally – as Dash heads out to pasture, I’m happy to reveal the biggest secret in VitalSource: why did we call it Dash? In typical VitalSource form, the name Dash is a pun. Trying to come up with a good code name for a rewrite of our rendering engine to make it faster, we landed on “Dash Render”, named after an obscure Star Wars character.

The combination of the pun on his last name, and “Dash” meaning fast (snappy performance was one of our primary goals) was irresistible. Plus, the shortness of “Dash" (four letters) made it a good prefix for class names and code files. Never expecting it to go beyond a private joke among the development team, it caught on companywide…and lasted almost two decades.

Subscribe to the blog

Subscribe