Hide Notes 

Slide 1: Putting Everything Back Together Again: Delivering Information Products Copyright © Stilo International 2008 Joe Gollner Vice President e-Publishing Solutions Stilo International
Slide 2: Humpty Dumpty can be Put Back Together Again We have the Technology He will be Better than he was before Better, Stronger, Faster
Slide 3: Content Management Pop Quiz In building a system to manage & publish content content… Meticulously capture the business requirements. b. b Rigorously document the rules that apply 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. e. All of the above above. f. None of the above. E or F? a. Sadly “F” may be the right answer…
Slide 4: Current Trends in the Content landscape relevant, divergent, 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 communities Huge volumes of very simple, but still structured, content Dominant feature: Uncontrolled growth. growth Complexity endures, again. Enterprise applications are becoming content aware Integration of content in all forms is accelerating Applications are appearing that consume high-precision content Dominant feature: Uncontrolled growth. growth Prescriptive design methods cannot handle this growth
Slide 5: The Good News and Bad News about Content These trends bring change The Good News The demand for content is expanding rapidly The Not So Good News The complexity confronting authors & publishers & th bli h technology providers is also growing rapidly Challenges for Publishing Start from more complex sources Must respond on demand on-demand Must meet high quality levels Must strive for perfect relevance
Slide 6: Topics The Curious Tale of the 13 Stylesheets The Rise of the Performance Support Portal Expectations for Content The Elements of a Scalable Publishing Process
Slide 7: Case Study: The Curious Tale of the 13 Stylesheets
Slide 8: The Curious Tale of the 13 Stylesheets How advanced publishing processes can save money, time and sanity
Slide 9: Case Study: Ultimate TechDoc (Military)
Slide 10: Case Study: Bilingual Technical Documentation Challenging output requirements led to a proliferation of complex stylesheets Bilingual publishing made the requirements ee even more oe challenging Multiple layout specifications existed
Slide 11: Automated Content Publishing
Slide 12: Content Publishing Architecture
Slide 13: Case Study: Lessons Learned Processing Scripts Simpler to Maintain Removed Problems Improved Outputs ABC Processing g Scripts Style Sheets ABC Style Sheets ABC Style Sheets ABC Style Sheet ABC Style Sheet
Slide 14: The Rise of the Performance Support Portal pp
Slide 15: 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
Slide 16: Observations on Performance Support Portals Performance Support Portals ( pp (PSPs) ) Becoming widespread in many industry sectors Public expectation is that products will be supported with a portal Portal services are differentiated by: Precision The extent to which content is tailored for user contexts Performance The speed with which desired content is located Navigability g y The ability for users to move to supporting content Portability The ability for users to access content from anywhere Timeliness The tight integration of portal contents and product status
Slide 17: Project Scenario: Maintenance Information Integrated Maintenance Information View for C f Commercial il Aircraft All required sources are tightly integrated in a single reference tool A dramatic improvement
Slide 18: Ency yclopedia On Demand Tex xtbooks Ac cademic Project Scenario Russian Academic Knowledge Portal Variable Output Document g and Knowledge Architecture (VODKA) Po ortable P Public
Slide 19: Project Scenario: Personalized Newspapers Publishing Modular Content Specialized Components Metadata Resources Real-Time Personalization Processes Modularized content Database storage & retrieval Dynamic Assembly Personalization Filtering 1996 – Present…
Slide 20: Project Scenario: Forest Information Mall FIM Interface Search Functionality Content Context Finding content using a variety of familiar mechanisms and leading to applicable process areas Publish Process Process Context Navigation through processes (areas) surfaces sets of relevant documents Web Services XML Metadata Web Sites Databases Tools Contents Contacts Lightweight deployment of XML & transformations to enable “process help”
Slide 21: Implications for Content What then is expected of content? 1. 2. 2 3. 4. 4 5. 6. 7. 8. Content must be available as valid XML Content C t t must be modularized tb dl i d Content must be meaningful in multiple contexts Content must be discretely addressable Content must be uniquely identifiable using metadata Content must be linked to related content Content must encourage modification & addition Content must be processable with almost perfect confidence This also has implications for the publishing process...
Slide 22: Case Study: High-Efficiency M lti di P bli hi Hi h Effi i Multimedia Publishing
Slide 23: Case Study: Multimedia Publishing High Profile Customer g Major enhancement of a successful CD ROM product Issues with first release demanded a new approach Feature requests introduced challenging requirements Cost-effectiveness of production process needed improvement New information sources identified for inclusion New edition Would incorporate seven different publication sources Movie details Movie reviews, Mo ie details, Mo ie re ie s film ind str biographies industry Awards 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
Slide 24: Case Study: Optimization for Accelerated Editing <MOVIE COLOR=“c” RATING=“1.5” MPAA=“PG”> <MTTILE>Lighting, the White Stallion</MTITLE> MTTILE Li hti th Whit St lli /MTITLE Multiple <RELEASE><LENGTH>95</LENGTH> <DATE>1986</DATE> Sources <GENRE>Drama</DRAMA></RELEASE> <D><NAME><ALTNAME><CALLED><NAMEPART>William</NAMEPART> 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> <NAMEPART>Mickey</NAMEPART><FAMILY>Rooney</FAMILY> </CALLED></PERSON> a wealthy man whose racehorse is stolen. <PERSON><CALLED>The Mick</CALLED><ALSO>Mickey y Rooney</ALSO></PERSON> can’t save it.</PARA></NOTES></MOVIE> Optimized for Editing [ Warning: SGML minimization! ] <movie c 1.5 PG>Lighting, the White Stallion (1986: Drama): 95 <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.
Slide 25: Case Study: Innovative & Successful Solution Features: Ft Automated conversion, markup enrichment, markup optimization, metadata extraction, link identification & generation, and publishing. Results: R lt Solidification of market leadership, Product functionality enhancement, Product content expansion, Editorial process streamlining, reduced publishing costs, and improvement in profitability.
Slide 26: The Design of Scalable Publishing Solutions g g
Slide 27: Deliver Content ACQUIRE ENRICH DELIVER CONTEXT Import Select Metadata Content Processing Convert Collect Compile CONTENT Import Manage Select Publish Content Processing Refactor Relate Resolve CONNECTIONS Import Links Select
Slide 28: Delivering Content Compile p Resolve Publish Resolve: assemble content and i t ti t applicable relationships R l bl t t d instantiate li bl l ti hi Compile: convert resolved content into a form suitable for rendition Publish: render the content in the forms required by the context
Slide 29: Delivery Considerations Amounts to matching the delivery context to resources Identifying the right content artifacts based on the delivery context Resolving all relevant relationships to ensure content completeness Compiling the contents into the forms needed for efficient rendition Rendering the compiled contents into usable products Depends on processing precision In most cases, delivery should be completely automated Exceptions exist where delivery entails unique interventions Sophistication drives the need for processing scalability Real time Real-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
Slide 30: D Data Sou urces Do ocument Sources Integr ration Scalable Publishing Solutions Rules Spe ecialized M Models
Slide 31: The Goal: High Fidelity Automation Content Print Publishing (PDF) Deliver - Resolve - Compile - Publish Web Publishing (Portal / Portable) Rules Templates Output Plan (Map & View) Output Print Products Publish PDF Resolve Assembling the inputs Content Content requested Supporting assets Assets Applicable stylesheets & rules Resolve into a processable whole Compile formattable content representations Publish final formatted renditions Compile Output Web Products Render Delivery Processing Tra ansformations s Ou utput Variants XHTML
Slide 32: The Publishing Pipeline Resolution leverages CMS / Database services ( g (selecting) g) Compilation produces “simplest possible serialization” All stages generate activity logs that feed a “quality report”
Slide 33: Conclusions Automation & careful design can Dramatically improve publishing processes Achieve the level of quality, precision & timeliness that is needed Reduce the cost & time needed to realize these goals While there is no magic… we can d thi ! do this!