Strategic Implications of XML for your Publishing Business

1,152 views

Published on

Nic's presentation from London Book Fair 2011 about what XML can do for and to publishers.

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,152
On SlideShare
0
From Embeds
0
Number of Embeds
157
Actions
Shares
0
Downloads
27
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Strategic Implications of XML for your Publishing Business

  1. 1. 1<br />Strategic Implications of XML for your Publishing Business<br />Nic Gibson<br />11th April 2011<br />(nicg@corbas.co.uk)<br />
  2. 2. 2<br />One-Slide Refresher<br />XML is a meta file format<br />Tagged text <br />Lots of angle brackets<br />A tiny little bit like HTML with stricter rules<br />You can write your own language by following the rules*<br />* Don’t to this at home<br />
  3. 3. 3<br />The Environment<br />Is XML important?<br />Why is it important now?<br />How does it affect your business?<br />
  4. 4. 4<br />Digital Markets Mature<br />More books will become digital only<br />The price of printing may only be a small part but it’s a part<br />Traditional publishing will be competing against a different cost base.<br />
  5. 5. 5<br />The business is changing<br />Publishing is paper centric<br />It needs to be content centric<br />The paper mindset needs to be replaced by a digital content mindset<br />Change Happens<br />
  6. 6. 6<br />The World has Changed<br />When did you <br />last use an encyclopaedia?<br />pick up a dictionary?<br />These are digital activities now<br />
  7. 7. 7<br />Traditional Models are Threatened<br />More writers will follow the Ian Fleming and Catherine Cookson estates<br />Amazon has 20% of the UK book market<br />In trade, more writers will be established indies before they even talk to a publisher<br />
  8. 8. 8<br />Change<br />Publishing is becoming more like software<br />No coincidence that new media folk are moving in<br />If publishing is becoming like software let’s learn the lessons of software development<br />project management<br />version control<br />separation of presentation and data<br />
  9. 9. 9<br />Content Driven Publishing<br />XML is a valuable tool<br />It’s not an answer in itself<br />An XML first workflow doesn’t necessarily get you anywhere<br />It’s the neutral format for your content<br />
  10. 10. 10<br />Challenges/Opportunities? <br />Process complexity<br />Licensing and custom publishing<br />Digital formats<br />Content reuse<br />Discoverability<br />Increase ROI<br />
  11. 11. 11<br />Processes<br />XML first/last/somewhere<br />Does it actually matter where the XML is?<br />We need digital content driven processes<br />
  12. 12. 12<br />How do you create your eBooks?<br />From edited manuscript?<br />From the application files?<br />From the print PDF?<br />From XML?<br />Where Are We Now?<br />
  13. 13. 13<br />How do you create your eBooks?<br />From edited manuscript?<br />From the application files?<br />From the print PDF?<br />From XML?<br />Where Are We Now?<br />
  14. 14. 14<br />The Continuum<br />Where’s the right place to be?<br />
  15. 15. 15<br />Traditional Workflows<br />
  16. 16. 16<br />Traditional Workflows<br />Traditional publishing workflows do not include digital content well<br />Well-known process<br />Developed over a long period<br />Efficient way to produce books<br />
  17. 17. 17<br />Traditional Workflows<br />Traditional publishing workflows do not include digital content well<br />Not suited to multi-format publishing<br />Not particularly suited to the outsourced world<br />Depends on valuable skill sets<br />
  18. 18. 18<br />Transitional Workflows<br />Transitional workflows are a first step<br />Simply adding digital outputs to your existing workflows<br />Convert the output into your new formats<br />Easy to do<br />You get XML<br />You get eBooks<br />
  19. 19. 19<br />Transitional Workflows<br />Transitional workflows are a first step<br />Simply adding XML to your existing workflows<br />Convert the output into your new formats<br />Some of the output benefits but none of the process benefits of content driven models<br />All of the costs of traditional publishing workflows<br />
  20. 20. 20<br />124<br />Content Driven Workflows<br />
  21. 21. 21<br />Content Driven Workflows<br />Get the content into XML as soon as you can<br />For suitable content types there are major benefits<br />Highly flexible<br />Multi format publishing is much easier<br />Repeatability <br />Lowered costs<br />
  22. 22. 22<br />Content Driven Workflows<br />Get the content into XML as soon as you can<br />For suitable content types there are major benefits<br />Very different - new skills required<br />Sometimes not applicable<br />
  23. 23. 23<br />Licensing<br />We want to license the content not the design<br />If it becomes easy, we will do it<br />Education<br />Reference<br />STM<br />Poetry<br />Cookery<br />
  24. 24. 24<br />Custom Publishing<br />Everything about licensing is true for custom publishing too<br />Educational publishing<br />sell by chapter<br />custom textbooks<br />
  25. 25. 25<br />Digital Formats<br />Digital formats breed<br />EPUB<br />Kindle<br />Web<br />What next?<br />
  26. 26. 26<br />What Does XML Get You?<br />Agile content<br />XML is an enabler for multi-format publishing<br />EPUB<br />Kindle<br />Web<br />multiple print formats<br />
  27. 27. 27<br />Agility<br />Content has to be agile<br />It has to be easy to <br />create the large format book<br />sell a single chapter <br />create the EPUB<br />change from EPUB to whatever comes next<br />XML enables agile content<br />
  28. 28. 28<br />The Way We Think<br />Design is integral<br />The words are fixed<br />
  29. 29. 29<br />Traditional Design<br />Traditionally, a book could be viewed as a tightly grouped trio of design, content and structure<br />
  30. 30. 30<br />Design and Digital Content<br />XML helps us to extract the design<br />Enables multiple designs for a single item of content<br />Enables a single design for multiple items of content<br />
  31. 31. 31<br />Design and Digital Content<br />XML helps us to extract the design<br />Enables multiple designs for a single item of content<br />Enables a single design for multiple items of content<br />
  32. 32. 32<br />Additional Revenue<br />
  33. 33. 33<br />Discoverability<br />Amazon recommendations<br />Finding eBooks<br />Metadata<br />Dublin Core<br />The semantic web<br />RDF<br />
  34. 34. 34<br />Content Reuse<br />Different types of content have different potentials for reuse<br />One of the ROI drivers for XML is reuse<br />
  35. 35. 35<br />Improved ROI<br />Simpler processes<br />Revenue opportunities<br />New formats<br />Reuse<br />
  36. 36. 36<br />Words<br />Digital only features<br />Print only features<br />Accessibility<br />
  37. 37. 37<br />What if?<br />XML may be superseded by something better<br />This happens in technology <br />XML could help you handle its own obsolescence<br />
  38. 38. 38<br />Summary<br />What challenges can XML help us with?<br />What does that change in the publishing process?<br />
  39. 39. 39<br />XML helps us become content focused<br />Licensing<br />Multi-format publishing<br />New revenue opportunities<br />
  40. 40. 40<br />We need to be more flexible<br />We have to change the way we think<br />The technology is here<br />Digital publishing is here<br />Let’s put them together and do something clever<br />
  41. 41. 41<br />Thank YouQuestions?<br />

×