{'fraction_non_alphanumeric': 0.02033271719038817, 'fraction_numerical': 0.0, 'mean_word_length': 5.444444444444445, '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 service-oriented monitoring registry

Web services are software modules that expose their functionality over the Internet via well-defined interfaces. Although Web services are promising technologies in that they facilitate application-to-application communication over the Internet, they still rely on traditional distributed computing communication models such as the remote procedure call, in which a Web service requestor needs to have complete knowledge of a Web service provider interface. If a Web service requestor did not use the latest version of a Web service provider interface to generate a proxy service, then static binding to the Web service provider's services fails. In this paper, we provide functional requirements for a Service-Oriented Monitoring Registry (SOMR) that provides notification to service requestors when a version of an interface changes or a service becomes disabled. In order to present a more complete picture of SOMR we include four architectural views covering (i) the over-all system, (ii) its four tiers and their interconnection, (iii) details of the service tier and (iv) its deployment onto executable environments. SOMR provides public Web service registries that can be used by Web service providers, developers, and consumers to register their profiles so that whenever any change happens to Web service interfaces they are notified about these changes and can respond accordingly. In contrast with current static solutions, the proposed system provide a significant step toward achieving solutions that are consistent with the dynamic nature and evolution of Web services.