{'fraction_non_alphanumeric': 0.01566951566951567, 'fraction_numerical': 0.0, 'mean_word_length': 5.333333333333333, '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}}
Distributed Context Data Management

We argue that general context data distribution can be achieved by establishing a network of context managers. The context managers have a uniform core which is surrounded by the appropriate functionality to make it deployable in applications, user and organizational infrastructure, and on top of sensors. When access to the context manager is mediated and policed, we say that it is a context service, a publicly recognisable, addressable and tangible entity. Clients that wish to consult the context manager for updated context information, must turn to the service interface where they may face rejection for reasons of security, personal integrity or workload.