{'fraction_non_alphanumeric': 0.019088016967126194, 'fraction_numerical': 0.0010604453870625664, 'mean_word_length': 5.378378378378378, '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}}
Solving two special dependency conflicts in real-time collaborative design systems

Dependency Graph (DG) is widely used in 3D design systems to represent the relationships among inner objects of the document. In order to transform the single-user application, which uses DG as the document model, into groupware system, OT is usually adapted to the new environment and five types of dependency conflicts are proposed and resolved in the literature. However, in some scenarios where loops are not allowed in the DG model, there are also two other conflicts named as cross-dependency conflict and transitive -dependency conflict, which may generate inconsistency document status or intention violation. This paper describes the definitions and detection rules of these two special conflicts and contributes a multi-version strategy to solve them. Conflict resolution strategies are detailed and examples are illustrated for their understanding.