lavacon 2017 - who cares about change?
TRANSCRIPT
Revision log
Version control
Change tracking
Comparison
Native Markup(e.g. DITA)
Processing instructions
Identification
@rev attribute
@status attribute
Release management domain
Representation
Authors
Editors
SMEs
Reviewers
CustomersAuditors
Tracked changesTracked changesPublished changes
Change summaryPublished changes
Change summaryTracked changesPublished changes
Change summaryPublished changes
HEALTHCARE CASE STUDY• Word-based solution using change tracking
• Redline PDF ‘printed’ from Word
• Content moved to DITA-based system
• Conditional processing supports alternate requirements
• Change-tracking is no longer possible due to reuse
• Comparison used to create DITA source for redline publishing
SUMMARY• Content changes, constantly
• Think about who your change stakeholders are
• Build a mechanism for identifying and representing change
• Remember why you chose XML
• Provide changes in a way that meets stakeholder needs