{'fraction_non_alphanumeric': 0.02191464821222607, 'fraction_numerical': 0.0, 'mean_word_length': 6.1735537190082646, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Tracked Changes: Navigating the Document-Format Anti-Pattern

Editing of word-processing documents at the presentation level, with visible tracking of changes, operates at a different level of abstraction and granularity than the recorded form in common document-file formats. The consequent mismatches along with other limitations of standards for document-file formats present an anti-pattern that impedes reliable inter-product exchange of change-tracked documents. Analysis of the situation for ODF change-tracking reveals simple extensions and definitions that supplement the current specification without introducing any conflicts. Patterns of systematic testing for conformant document files, compliant processing, and verifiable interoperability are identified as essential prerequisites to dependable improvement of change-tracking in collaborative settings.