{'fraction_non_alphanumeric': 0.027695351137487636, 'fraction_numerical': 0.0, 'mean_word_length': 5.285714285714286, '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}}
Reuse in Hypermedia Applications

In the hypermedia communication process, authors are connected to readers through hypermedia applications. The underlying software is an important part of the “communication channel” between authors and readers: it is effective if it is “transparent.” This means that hypermedia software must be flexible and powerful, to support naïve users as well as “experienced navigators;” it must be developed and tested before contents, because contents, in real projects, are released very late; it must be robust and errorfree; and finally it must be inexpensive with respect to contents, because contents are the focus of the production effort. For all these reasons, the run-time software must be contents independent and application independent; in fact, it can be powerful enough only if its development costs can be shared over a large number of projects. Two applications, built around a reusable run-time engine based on the previous considerations, are presented in the paper.