LavaCon 2017 - Who Cares About Change?

Download LavaCon 2017 - Who Cares About Change?

Post on 23-Jan-2018

25 views

Category:

Technology

0 download

Embed Size (px)

TRANSCRIPT

<ul><li><p>Who CaresAbout Change?</p><p>Tristan Mitchell</p></li><li><p>Identification</p><p>Representation</p><p>Management</p><p>of XML Change</p></li><li><p>UNAVOIDABLE TRUTH #1</p><p>Content Changes</p></li><li><p>Everything changes and </p><p>nothing remains still</p><p>Change is the only constant</p></li><li><p>To improve is to change, so to be perfect is to have changed often. </p></li><li><p>UNAVOIDABLE TRUTH #2</p><p>Stakeholders want to see the changes</p></li><li><p>Authors</p><p>Editors</p><p>SMEs</p><p>Reviewers</p><p>CustomersAuditors</p></li><li><p>UNAVOIDABLE TRUTH #3</p><p>Change must first be identified before you </p><p>can show it</p></li><li><p>Revision log</p><p>Version control</p><p>Change tracking</p><p>Comparison</p><p>Native Markup(e.g. DITA)</p><p>Processing instructions </p><p>Identification</p><p>@rev attribute</p><p>@status attribute</p><p>Release management domain</p><p>Representation</p></li><li><p>OPPORTUNITY #1</p><p>Even change canbe reused</p><p>(if you represent it using structure)</p></li><li><p>OPPORTUNITY #2</p><p>Identified change can be published</p></li><li><p>MAKING IT WORK</p><p>Provide stakeholders with changes relevant to </p><p>their needs</p></li><li><p>Authors</p><p>Editors</p><p>SMEs</p><p>Reviewers</p><p>CustomersAuditors</p><p>Tracked changesTracked changesPublished changes</p><p>Change summaryPublished changes</p><p>Change summaryTracked changesPublished changes</p><p>Change summaryPublished changes</p></li><li><p>MAKING IT WORK</p><p>CustomerCase Study</p></li><li><p>HEALTHCARE CASE STUDY Word-based solution using change tracking</p><p> Redline PDF printed from Word</p><p> Content moved to DITA-based system</p><p> Conditional processing supports alternate requirements</p><p> Change-tracking is no longer possible due to reuse</p><p> Comparison used to create DITA source for redline publishing</p></li><li><p>CASE STUDY</p><p>Editor</p><p>CMSHTML</p><p>&amp;CSS</p><p>PDFDITAOT</p><p>PublishingTool</p><p>DITA workflow</p></li><li><p>SUMMARY Content changes, constantly</p><p> Think about who your change stakeholders are</p><p> Build a mechanism for identifying and representing change</p><p> Remember why you chose XML</p><p> Provide changes in a way that meets stakeholder needs</p><p>@TristanDeltaXMLtristan.mitchell@deltaxml.com</p></li></ul>