1. Case Study on Redlining at the ISO Chandi Perera cperera@typefi.com

2. ISO International Organization for Standardization  World's largest developer and publisher of International Standards  164 national standard bodies  100000 experts into 3484 technical bodies  Collaboration with 649 international organizations  Total of 19977 International Standards

3. Single Source Publishing

4. Redline Publications Traditionally done manually Only for the most popular 50-60 standards documents Always for adjacent versions only High cost of production Delayed release

5. Automation Approach Identify the changes Render the changes

6. Track Changes Approach

7. Pros Changes can be seen by committee members as they author or update a standard. Side notes can be applied to the content to explain changes. Supported in Microsoft Word

8. Track Changes Approach Cons There is a requirement for editors and authors to keep track changes enabled. Any author or editor can “hide” changes by accepting tracked changes. There is a likelihood of lots of false changes being captured during intensive editing stages.

9. Track Changes Approach Cons The Word document becomes cluttered if there are lots of changes. The ability to redline across non-adjacent versions. Not everyone uses Microsoft Word, and copy and pasting from another application will mark the whole section as changed

10. XML Differencing Compare two versions of the same XML document and get an intelligent result

11. XML Differencing Pros Not dependent on author behavior or applications No need to retrain contributors Only comparing final documents Can compare non adjacent versions

12. XML Differencing Cons More complex to implement Requires additional software

13. XML Differencing How it works Output XML contains both versions

14. XML Differencing How it works MarkupMeaning deltaxml:deltaV2="A=B"the content of that element (and its children) has not changed deltaxml:deltaV2="A"content is unique to document A deltaxml:deltaV2="B"content is unique to document B deltaxml:deltaV2="A!=B" indicates that that element (or one or more of its descendants) has changed between documents

15. Creating the Redline

16. Redline Workflow

17. Rendering the Changes Text Images Tables Mathematics

18. Rendering Text Unchanged text old/deleted text new/added text

19. Rendering Images

20. Detecting Change Images Change in the figure filename/file path Change in the image file signature Change to figure XMP metadata

21. Rendering Tables Content change only: Render the same as text changes Structure changes: Render the same as figures

23. BUT!!!! Sometimes tables are used improperly

24. New edition

25. Change

26. Solution Address the editorial process and style Change table structure only when necessary

27. Rendering Mathematics Compare the MathML Render the images in changes Can lead to false positives between different versions of MathML or different ways of expressing the same equation

28. Rendering Reducing Clutter Do not render the changes that does not change the meaning

29. Rendering Rules addition or deletion of semi-colons change from hyphen to non-breaking hyphen change from hyphen to en rule and vice versa change from hyphen to em rule and vice versa addition or deletion of white space

30. Rendering Rules change from one type of white space to another (i.e. from space to non-breaking space) change from apostrophe to prime and vice versa change from hyphen to minus and vice versa change from flat text to hyperlinked text change from “equation” to “formula”

31. BUT!!! Be Careful Addition and removal of commas Capitalization changes Changes from italic to roman or back

32. Challenges Inconsistent Markup

33. Challenges Inconsistent Markup

34. Due to XML being generated from scratch each time there is no consistent id attributes Consistent @id would significant assist in the redline process Challenges Lack of @id

35. Automated creation of Redline Publications is possible If you cannot control the authoring process change tracking approach will not work ISO-STS (by extension JATS) provides reasonable support for XML Differencing/Redline Consistency of tagging between versions is critical Conclusions

36. QUESTIONS Chandi Perera cperera@typefi.com