1 / 36

Automated Redline Publishing for ISO Standards: A Case Study

Explore how the ISO implemented a new approach to automate redline publications, overcoming manual and costly production processes. Learn about the benefits and challenges of the XML Differencing approach, how to render changes in text, images, tables, and mathematics, and methods to reduce clutter. Discover the rules for rendering changes accurately and address challenges in inconsistent markup.

hcrowder
Download Presentation

Automated Redline Publishing for ISO Standards: A Case Study

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  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. Track Changes Approach 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 <someTagattributeA="ValueA"attributeB="ValueB"/><someTagattributeB="ValueB"attributeA="ValueA"></someTag>

  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

  15. Creating the Redline

  16. Redline Workflow

  17. Rendering the Changes Text Images Tables Mathematics

  18. Rendering Text <p>Unchanged text<deltaxml:textGroup deltaxml:deltaV2="A!=B"><deltaxml:text deltaxml:deltaV2="A">old/deleted text</deltaxml:text><deltaxml:text deltaxml:deltaV2="B">new/added text</deltaxml:text></deltaxml:textGroup></p>

  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

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

  23. New edition

  24. Change

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

  26. 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

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

  28. 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

  29. 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”

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

  31. Challenges Inconsistent Markup

  32. Challenges Inconsistent Markup

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

  34. Conclusions • 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

  35. QUESTIONSChandi Pereracperera@typefi.com

More Related