{'fraction_non_alphanumeric': 0.019339242546333603, 'fraction_numerical': 0.0, 'mean_word_length': 4.8584905660377355, '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 DCI Execution Model

Computers provide three essential services: Data transformation, data storage, and data communication. Transformation and storage have long been well entrenched in algorithmic and data modelling languages. Unaccountably, communication is only seen as an I/O operation without explicit language support. At long last, this deficiency has now been remedied with the new Data - Context - Interaction (DCI) paradigm. Alan Kay introduced the notion of object orientation in the early seventies. He regarded an object as a virtual computer and an object system as thousands of computers hooked together by a very fast network. The locus of DCI is in the DCI Context where we find the specification of object system behavior. The Context declares a network of communicating objects where the nodes are called Roles and the edges Connectors. The system behavior algorithm is composed from RoleMethods; methods that are associated with the Roles. This study is about an execution model for DCI. An important aspect is the handling of DCI Contexts at runtime; where they are stored and how they are accessed. DCI in general and the DCI Context in particular make data communication a first class citizen of computer programming.