The Promise

The Promise; The Pain; The Payback

RICHARD PIPE

www.infogridpacific.com

The Pain

Nobody actually wants XML

We want lower production costs We want more formats - sometime We need more business options Intelligent content is nice We want to survive

The Promise

The Promised Benefits of XML

Lower cost of content ownership Content Reuse Content Objects (Chunking /

Segmenting) Format production Content markup

The Promise

The tangible Benefits of XML

Print output eBooks Content Objects Online strategies Mobile strategies Business Readiness

The Promise

Mobipocket

XML: A Quick History

60s60s 70s70s 80s80s 90s90s 00s00s

SGML conceived

HTML 1.0 XHTML 1.026 Jan 2000

The Proprietary Years The Open Years

1986 SGMLISO Standard

HTML 2.01995

XML 1.010 Feb 98

XHTML 1.131 May 2001

DocBookSGML

TE LiteDITA

NOW

ePub

TeXDonald Knuth

The Promise

The legacy luggage!

DocBook TEI – Text Encoding Initiative Custom “house” SGML to XML

The Pain

The Promise

XML can be enjoyable

The Promise

XML is a TOOL

The Promise

Use the newest tools

XHTML CSS 2.1 – CSS 3.0 XSLT/FO - carefully XSL Python Javascript

XHTML

CSS XSL Modules

The Promise

XML vs. XHTML

XHTML is XML – totally ePub is XHTML Online content is inevitably XHTML Why do things twice?

The Promise

XHTML Benefits

Standards Controlled Easy to work with Lots of tools Lowers the technology costs Lowers the “expert” costs Delivers the goods from Novel to

Textbook

The Pain

What is a bookGeneral Structural Perspective

Galley punctuated by... Titles & Headers Text blocks Lists Images & tables Special List structures Generated Content Links & references

The Pain

A quick comparisonContent Perspective

<recipe subject=“snacks”> <instructions> Do it this way.</instructions> <ingredients> <ingredient>Bread</ingredient> <ingredient>Butter</ingredient> <ingredient>Jam</ingredient> </ingredients> <cooking-time>5mins</cooking-time></recipe>

<div class= “block recipe snacks”> <p class= “instructions”> Do it this way.</p> <div class=“ingredients”> <p>Bread</p> <p>Butter</p> <p>Jam</p> </div> <p class=“cooking-time”>5mins</p></div>

XML Approach XHTML Approach

The Pain

Change Management Current Workflow & XML First

The Pain

Change ManagementRequired Workflow

The Payoff

The Payoff

SUMMARYWhich XML (XHTML)

The system that gives everything now Including things you don't want Including things you think you will never

need It must work out of the box It must be relatively painless

The Promise

The Questions

Is your solution based on open standards Will it do all I need today... and more What XML strategy do you recommend Show me the ROI calculations What are the ownership costs What is the cost of change

The Payoff

Thank You