{'fraction_non_alphanumeric': 0.02122820318423048, 'fraction_numerical': 0.0, 'mean_word_length': 5.346153846153846, '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}}
Bridging the MS/DSL Tools and the Eclipse Modeling Framework

Model Driven Engineering is based on a number of principles that may be applied in different contexts. Nowadays several environments employ the MDE principles: Model Driven Architecture (MDA™), Eclipse Modeling Framework (EMF), Microsoft Domain-Specific Language tools (MS/DSL), and many more. Focusing only on one context and ignoring other environments and platforms, based on different conventions, standards or protocols would be unwise because one of the desired properties of models is their ability to be exchanged between different contexts. Due to their abstraction expression level, models should ideally be more adaptable to various operational environments than conventional code. In other words, OMG models and Microsoft models among others should be able to be exchanged between the corresponding environments. In this paper we focus on exchange of models created in these two major industrial platforms: EMF and Microsoft DSL. The capability to exchange models between an EMF and a corresponding MS/DSL based system requires an abstract understanding of both architectures and a precise organization of the interoperability scheme. This paper describes the first results of a project in this area and presents the lessons learnt in this work.