Palimpsest: DocTrain: Dynamic Publishing

Palimpsest has moved. Please visit our blog in its new location for the most recent posts from Scriptorium.

Palimpsest

DocTrain: Dynamic Publishing

Thursday, May 08, 2008 — posted by Sarah

Once Content is in XML. Now what?
Learn How Dynamic Publishing Can Help You Improve the Re-use and Value of XML Content
Joshua Duhl
Quark

He begins with a lengthy explanation of why single-sourcing is a Good Thing, which I rather think might be unnecessary for this audience.

According to Mr. Duhl, most organizations are using print-based workflows or print-based workflows with an add-on for the web. Again, wrong audience.

The web mobile devices, and electronic communications have altered the fundamental principles of publishing: Content everywhere.

Pitfalls of traditional publishing

Processes are costsly
Updates are slow
Information is often out-of-date
Content is prone to errors
Customers are unhappy
Deadlines are missed

He appears to be describing the world before single-sourcing workflows. Think 1995. Other places in the organization, people are creating content you can use. He's defining the problem as sharing content between engineering and marketing. Lots of work and planning are required, but "staggering" benefits

Graphing complexity against volume

high complex/low volume: tech doc
high volume/low complex: statements, invoices
in the middle: correspondence

Tech pubs

need to work with content from multiple sources
publishing to multiple sources or for multiple sources
enable content for re-use beyond the tech doc

Wouldn't it be great

to use a single system that holds all information
to have an automated workflow that ensures approved content is automatically published for each edition and different devices

"automation and collaboration are two sides of the same coin"?

Core principles

content centric
single source
reuse strategy

Content is created regardless of format, layout, or media (content first)

single source

plan for reuse, support for variations and alternatives

leveraging XML

format versus structure

What is Quark Dynamic Publishing Solution
* QuarkXPress
* plus workflow
* dynamic publishing

OK, so I finally understand my issues with this...in a world where people are componentizing and picking and choosing their solutions, why would they go to a monolithic approach?

Create
* QXP
* Indesign
Word
XML
WEb

manage
workflow system/check-in/out etc

publish
QXP server
* Quark transformation engine
* XML transformation rules

delivery
rendered formats

Sorry the notes are so messy; this presentation went very fast due to some scheduling issues that were not the presenters fault.

But overall, Quark is proposing a "dynamic publishing solution" that enables single-sourcing workflows based on XML.

Labels: doctrainwest08, xml

1:34 PM Permalink |

|

<< Home

divider

Contributors

Palimpsest

DocTrain: Dynamic Publishing