{'fraction_non_alphanumeric': 0.01201923076923077, 'fraction_numerical': 0.001201923076923077, 'mean_word_length': 5.717741935483871, '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 review of the widget landscape and incompatibilities between widget engines

A widget is a packaged interactive client-side application, commonly developed using Web standards and techniques to access data services both on theWeb and host devices. The purpose of this paper is to review the widget landscape and present key characteristics and concerns of widget technologies. Various incompatibilities exist between widgets and the proprietary engines hosting them on different platforms. Incompatibilities can be classified by how different implementations handle issues related to packaging, behaviour, security and presentation. These common concerns, together with economic drivers have given rise to numerous standardisation efforts such as those being carried out by the W3C in drafting the widget family of specifications.