{'fraction_non_alphanumeric': 0.016333938294010888, 'fraction_numerical': 0.0, 'mean_word_length': 5.202247191011236, '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}}
A taxonomy of issues in name systems design and implementation

In the last decade, name systems have grown from a single centrally-controlled server providing only host name to physical address mapping, to a complex system consisting of multiple and distributed servers, providing not only name mapping, but also general directory lookup services. These advances are due in part to the increase in size, complexity and heterogeneity of distributed systems. This paper presents a taxonomy of design and implementation issues in building a name system.