{'fraction_non_alphanumeric': 0.01878453038674033, 'fraction_numerical': 0.0, 'mean_word_length': 6.133858267716535, '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}}
Abstraction Conflicts in Industrial Deployment of Model-Based Interoperability Standards

Model-based interoperability refers to a collaboration of independently developed systems based on heterogeneous semantic models in a common vocabulary and framework. Abstraction conflicts (differences in the choice and construction of abstractions of a real-world entity to fit a specified model vocabulary and framework) can significantly hamper interoperability when not taken into account during the design of interoperability standards. This paper studies the impact of abstraction conflicts on model-based interoperability in an Intelligent Transportation Systems (ITS) domain. We presents results from a case study, discuss causes for such abstraction conflicts, and illustrate, by means of a specific model-based interoperability solution, possible approaches to address and overcome such model differences.