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

36
Case Study on Redlining at the ISO Chandi Perera [email protected]

description

Case Study on Redlining at the ISO Chandi Perera [email protected]. ISO. International Organization for Standardization. World's largest developer and publisher of International Standards 164 national standard bodies 100000 experts into 3484 technical bodies - PowerPoint PPT Presentation

Transcript of Case Study on Redlining at the ISO Chandi Perera cperera@typefi

Page 1: Case Study on Redlining  at  the  ISO Chandi Perera cperera@typefi

Case Study on Redlining at the ISO

Chandi [email protected]

Page 2: Case Study on Redlining  at  the  ISO Chandi Perera cperera@typefi

ISOInternational 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

Page 3: Case Study on Redlining  at  the  ISO Chandi Perera cperera@typefi

Single Source Publishing

Page 4: Case Study on Redlining  at  the  ISO Chandi Perera cperera@typefi

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

Page 5: Case Study on Redlining  at  the  ISO Chandi Perera cperera@typefi

Automation Approach

• Identify the changes

• Render the changes

Page 6: Case Study on Redlining  at  the  ISO Chandi Perera cperera@typefi

Track Changes Approach

Page 7: Case Study on Redlining  at  the  ISO Chandi Perera cperera@typefi

Track Changes ApproachPros

• 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

Page 8: Case Study on Redlining  at  the  ISO Chandi Perera cperera@typefi

Track Changes ApproachCons

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

Page 9: Case Study on Redlining  at  the  ISO Chandi Perera cperera@typefi

Track Changes ApproachCons

• 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

Page 10: Case Study on Redlining  at  the  ISO Chandi Perera cperera@typefi

XML Differencing

• Compare two versions of the same XML document and get an intelligent result

<someTag attributeA="ValueA" attributeB="ValueB"/><someTag attributeB="ValueB"

attributeA="ValueA"></someTag>

Page 11: Case Study on Redlining  at  the  ISO Chandi Perera cperera@typefi

XML DifferencingPros

• Not dependent on author behavior or applications

• No need to retrain contributors

• Only comparing final documents

• Can compare non adjacent versions

Page 12: Case Study on Redlining  at  the  ISO Chandi Perera cperera@typefi

XML DifferencingCons

• More complex to implement

• Requires additional software

Page 13: Case Study on Redlining  at  the  ISO Chandi Perera cperera@typefi

XML DifferencingHow it works

• Output XML contains both versions

Page 14: Case Study on Redlining  at  the  ISO Chandi Perera cperera@typefi

XML DifferencingHow it works

Markup Meaning

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

Page 15: Case Study on Redlining  at  the  ISO Chandi Perera cperera@typefi

Creating the Redline

Page 16: Case Study on Redlining  at  the  ISO Chandi Perera cperera@typefi

Redline Workflow

Page 17: Case Study on Redlining  at  the  ISO Chandi Perera cperera@typefi

Rendering the Changes

• Text

• Images

• Tables

• Mathematics

Page 18: Case Study on Redlining  at  the  ISO Chandi Perera cperera@typefi

RenderingText

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

Page 19: Case Study on Redlining  at  the  ISO Chandi Perera cperera@typefi

RenderingImages

Page 20: Case Study on Redlining  at  the  ISO Chandi Perera cperera@typefi

Detecting ChangeImages

• Change in the figure filename/file path

• Change in the image file signature

• Change to figure XMP metadata

Page 21: Case Study on Redlining  at  the  ISO Chandi Perera cperera@typefi

RenderingTables

• Content change only: Render the same as text changes

• Structure changes: Render the same as figures

Page 22: Case Study on Redlining  at  the  ISO Chandi Perera cperera@typefi
Page 23: Case Study on Redlining  at  the  ISO Chandi Perera cperera@typefi

BUT!!!!

• Sometimes tables are used improperly

Page 24: Case Study on Redlining  at  the  ISO Chandi Perera cperera@typefi

New edition

Page 25: Case Study on Redlining  at  the  ISO Chandi Perera cperera@typefi

Change

Page 26: Case Study on Redlining  at  the  ISO Chandi Perera cperera@typefi

Solution

• Address the editorial process and style

• Change table structure only when necessary

Page 27: Case Study on Redlining  at  the  ISO Chandi Perera cperera@typefi

RenderingMathematics

• 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

Page 28: Case Study on Redlining  at  the  ISO Chandi Perera cperera@typefi

RenderingReducing Clutter

• Do not render the changes that does not change the meaning

Page 29: Case Study on Redlining  at  the  ISO Chandi Perera cperera@typefi

RenderingRules

• 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

Page 30: Case Study on Redlining  at  the  ISO Chandi Perera cperera@typefi

RenderingRules

• 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”

Page 31: Case Study on Redlining  at  the  ISO Chandi Perera cperera@typefi

BUT!!!Be Careful

• Addition and removal of commas

• Capitalization changes

• Changes from italic to roman or back

Page 32: Case Study on Redlining  at  the  ISO Chandi Perera cperera@typefi

ChallengesInconsistent Markup

Page 33: Case Study on Redlining  at  the  ISO Chandi Perera cperera@typefi

ChallengesInconsistent Markup

Page 34: Case Study on Redlining  at  the  ISO Chandi Perera cperera@typefi

• Due to XML being generated from scratch each time there is no consistent id attributes

• Consistent @id would significant assist in the redline process

ChallengesLack of @id

Page 35: Case Study on Redlining  at  the  ISO Chandi Perera cperera@typefi

• 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

Page 36: Case Study on Redlining  at  the  ISO Chandi Perera cperera@typefi

QUESTIONSChandi [email protected]