Putting Everything Back Together Again:

Copyright © Stilo International 2008

Delivering Information Products Joe GollnerVice President

e-Publishing Solutions Stilo International

Humpty Dumpty can be Put Back Together AgainWe have the TechnologyWe have the TechnologyHe will be

Better than he was beforeBetter, Stronger, Faster

Content Management Pop Quiz

In building a system to manage & publish contentIn building a system to manage & publish content…a. Meticulously capture the business requirements. b Rigorously document the rules that applyb. Rigorously document the rules that apply.c. Carefully define a detailed system architecture.d. Industriously build processing components to address the y g

requirements given the structural rules and the realities of the system architecture.All of the abovee. All of the above.

f. None of the above.E or F?E or F?

Sadly “F” may be the right answer…

Current Trends in the Content landscape

There are two relevant but apparently divergent trends:There are two relevant, but apparently divergent, trends:Simplicity wins, again.

Web 2.0 phenomenon is expanding & accelerating An era of interactive openness with users and communitiesHuge volumes of very simple, but still structured, contentDominant feature: Uncontrolled growthDominant feature: Uncontrolled growth.

Complexity endures, again.Enterprise applications are becoming content awareIntegration of content in all forms is acceleratingApplications are appearing that consume high-precision contentDominant feature: Uncontrolled growthDominant feature: Uncontrolled growth.

Prescriptive design methods cannot handle this growth

The Good News and Bad News about ContentThese trends bring changeThese trends bring changeThe Good News

The demand for content is expanding rapidlyexpanding rapidly

The Not So Good NewsThe complexity confronting

th & bli h &authors & publishers & technology providersis also growing rapidly

Challenges for PublishingStart from more complex sourcesMust respond on demandMust respond on-demandMust meet high quality levelsMust strive for perfect relevance

TopicsThe Curious Tale of the 13 StylesheetsThe Curious Tale of the 13 Stylesheets

The Rise of the Performance Support Portal

Expectations for Content

The Elements of a Scalable Publishing Process

Case Study:

The Curious Tale of the 13 StylesheetsThe Curious Tale of the 13 Stylesheets

The Curious Tale of the 13 Stylesheets

How advanced publishing processes

can savecan save money, time and sanity

Case Study: Ultimate TechDoc (Military)

Case Study: Bilingual Technical Documentation

Challenging outputrequirements ledto a proliferationof complexof complex stylesheets

Bilingual publishingBilingual publishingmade the requirementseven more e e o echallenging

Multiple layoutspecifications existed

Automated Content Publishing

Content Publishing Architecture

Case Study: Lessons Learned

ProcessingProcessingScripts

Processing

Simpler to MaintainRemoved Problems

StyleSheetsABC

gScriptsImproved Outputs

StyleSheetsABC

StyleSheetsABC

StyleSheetABC

StyleSheetABC

The Rise of the Performance Support Portalpp

The Rise of the Performance Support Portal

Performance Support Portals depend upon content resources that are intelligent and modular and that exhibit extremely high levels of quality

Observations on Performance Support PortalsPerformance Support Portals (PSPs)pp ( )

Becoming widespread in many industry sectorsPublic expectation is that products will be supported with a portalPortal services are differentiated by:Portal services are differentiated by:

PrecisionThe extent to which content is tailored for user contexts

PerformanceThe speed with which desired content is located

Navigabilityg yThe ability for users to move to supporting content

PortabilityThe ability for users to access content from anywhereThe ability for users to access content from anywhere

TimelinessThe tight integration of portal contents and product status

Project Scenario: Maintenance Information

Integrated MaintenanceMaintenanceInformation

Viewf C i lfor Commercial

Aircraft

All required sources are tightly integrated

in a single reference toolin a single reference tool

A dramatic improvement

yclo

pedi

a

xtbo

oks

Dem

and

Pub

lic

cade

mic

orta

ble

Ency Te

x

On P

Ac Po

Project Scenario

Russian Academic Knowledge PortalKnowledge Portal

Variable Output Documentand Knowledge Architectureg

(VODKA)

Project Scenario: Personalized Newspapers

Publishing

ModularContent

SpecializedComponents

MetadataResources

Real-TimePersonalizationResources Personalization

Processes

Modularized content

1996 – Present…Database storage & retrievalDynamic Assembly

Personalization Filtering

Project Scenario: Forest Information Mall

FIM Interface

Search Functionality

Process ContextNavigation through processes (areas) surfaces sets of relevant documents

Content ContextFinding content using a variety of familiar mechanisms and leading to applicable process areas

Web Web

documents applicable process areas

XML Metadata

Publish Process

Services

ToolsDatabases

Sites

ContactsContents

Lightweight deployment of XML & transformations to enable “process help”

Implications for ContentWhat then is expected of content?What then is expected of content?

1. Content must be available as valid XML2 C t t t b d l i d2. Content must be modularized3. Content must be meaningful in multiple contexts4 Content must be discretely addressable4. Content must be discretely addressable5. Content must be uniquely identifiable using metadata6. Content must be linked to related content7. Content must encourage modification & addition8. Content must be processable with almost perfect confidence

This also has implications for the publishing process...

Case Study: Hi h Effi i M lti di P bli hiHigh-Efficiency Multimedia Publishing

Case Study: Multimedia PublishingHigh Profile CustomergMajor enhancement of a successful CD ROM product

Issues with first release demanded a new approachFeature requests introduced challenging requirementsCost-effectiveness of production process needed improvementNew information sources identified for inclusion

New editionWould incorporate seven different publication sources

Mo ie details Mo ie re ie s film ind str biographiesMovie details, Movie reviews, film industry biographiesAwards information and glossary of film terminology

Estimated number of content objects: 3 million

Challenge: achieving high levels of quality and precision while reducing costs and accelerating editorial processes

Case Study: Optimization for Accelerated Editing<MOVIE COLOR=“c” RATING=“1.5” MPAA=“PG”>

MTTILE Li hti th Whit St lli /MTITLE<MTTILE>Lighting, the White Stallion</MTITLE> <RELEASE><LENGTH>95</LENGTH> <DATE>1986</DATE> <GENRE>Drama</DRAMA></RELEASE><D><NAME><ALTNAME><CALLED><NAMEPART>William</NAMEPART>

MultipleSources

C a /</CALLED><FAMILY>Levey</FAMILY></ALTNAME></NAME></D><A><NAME><ALTNAME><CALLED><NAMEPART>Mickey</NAMEPART></CALLED><FAMILY>Rooney</FAMILY></ALTNAME></NAME></A><NOTES><PARA>Extremely weak family fare with<PERSON> <CALLED><NOTES><PARA>Extremely weak family fare with<PERSON> <CALLED> <NAMEPART>Mickey</NAMEPART><FAMILY>Rooney</FAMILY> </CALLED></PERSON> a wealthy man whose racehorse is stolen.<PERSON><CALLED>The Mick</CALLED><ALSO>Mickey yRooney</ALSO></PERSON> can’t save it.</PARA></NOTES></MOVIE>

<movie c 1.5 PG>Lighting, the White Stallion (1986: Drama): 95<d>[William * Levey] <a>[Mickey * Rooney]

Optimized for Editing

<d>[William Levey] <a>[Mickey Rooney]Extremely weak family fare with [Mickey * Rooney] a wealthy man who racehorse is stolen. [The Mick = Mickey Rooney] can’t save it.

[ Warning:SGML

minimization! ]

Case Study: Innovative & Successful Solution

F t R ltFeatures:Automated conversion,markup enrichment,markup optimization,

Results:Solidification of market leadership,

Product functionality enhancement,Product content expansion,markup optimization,

metadata extraction, link identification & generation,and publishing.

Product content expansion,Editorial process streamlining,

reduced publishing costs,and improvement in profitability.

The Design of Scalable Publishing Solutionsg g

Deliver ContentACQUIRE ENRICH DELIVER

CONTEXT Import SelectMetadata

ContentProcessing Convert Collect Compile

ManageImport SelectCONTENT Publish

ContentProcessing Refactor Relate Resolve

CONNECTIONS Import SelectLinks

Delivering Content

Compile Publish

R l bl t t d i t ti t li bl l ti hi

Resolve

p

Resolve: assemble content and instantiate applicable relationshipsCompile: convert resolved content into a form suitable for renditionPublish: render the content in the forms required by the context

Delivery ConsiderationsAmounts to matching the delivery context to resourcesAmounts to matching the delivery context to resources

Identifying the right content artifacts based on the delivery contextResolving all relevant relationships to ensure content completenessCompiling the contents into the forms needed for efficient renditionRendering the compiled contents into usable products

Depends on processing precisionIn most cases, delivery should be completely automatedExceptions exist where delivery entails unique interventionsExceptions exist where delivery entails unique interventions

Sophistication drives the need for processing scalabilityReal-time delivery of tailored content modules from dynamic sourcesReal time delivery of tailored content modules from dynamic sources involves high standards for the content and high levels of performance, precision and reliability for the content processing technology

Scalable Publishing Solutions

ecia

lized

M

odel

s

ratio

n

ocum

ent

ourc

es

Spe M

Rul

esInte

gr

Dat

aur

ces

Do S

DSo

u

The Goal: High Fidelity AutomationPrint Publishing

(PDF)Content (PDF)

Deliver- Resolve- Compile- Publish

Web Publishing(Portal / Portable)

Publish

Output Print Products PDF

Rules

s

Delivery ProcessingAssembling the inputs

Content requested Content

Res

olve

TemplatesOutput Plan

(Map & View)

utpu

t Var

iant

s

Ren

der

ansf

orm

atio

ns

Content requestedSupporting assetsApplicable stylesheets & rules

Resolve into a processable whole

Content

Output Web XHTML

Assets

Ou

Tra

Compile

Resolve into a processable wholeCompile formattable content representationsPublish final formatted renditions

Products XHTML

The Publishing Pipeline

Resolution leverages CMS / Database services (selecting)g ( g)Compilation produces “simplest possible serialization”All stages generate activity logs that feed a “quality report”

Conclusions

Automation & careful design canDramatically improvepublishing processesAchieve the level of quality, precision & timelinessthat is neededReduce the cost & time neededto realize these goals

While there is no magic…d thi !we can do this!