{'fraction_non_alphanumeric': 0.013533834586466165, 'fraction_numerical': 0.0, 'mean_word_length': 4.6923076923076925, '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}}
XML to annotations mapping definition with patterns

Currently, the most commonly created formal languages are configuration 
 languages. So far source code annotations and XML are the leading notations 
 for configuration languages. In this paper, we analyse the correspondence 
 between these two formats. We show that there are typical XML to annotations 
 mapping solutions (mapping patterns) that indicate a correspondence between 
 embedded and external metadata formats in general. We argue that mapping 
 patterns facilitate creating configuration tools and we use a case study to 
 show how they can be used to devise a mapping between these two notations.