{'fraction_non_alphanumeric': 0.02025435704192181, 'fraction_numerical': 0.002826189354686764, 'mean_word_length': 5.495412844036697, '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}}
Semantic Web Services : A conceptual comparison of OWLS , WSMO and METEORS approaches

Today’s distributed computing is strongly connected with the idea of Web Services. These are parts of programs that can be accessed over a network using well defined protocols. Thus, building a software can be carried out using loosely coupled, reusable components. Moreover, the notion of Web services can facilitate the interoperability between systems to accomplish inside business tasks realizing the system integration and also inter-organizational operations. Current Web Services standards WSDL [19] and SOAP [11] introduced for describing, discovering and invoking Web Services, although they are well defined and accepted also by industry, they only describe the syntactic aspects of a Web Service. WSDL is less suitable for describing the semantics of a Web Service capability. This drawback affects not only the service discovery procedure but also service composition, invocation and interoperation [25]. Adding semantics to Web Services description standards can tackle these issues. The vision of Semantic Web Services is to describe the semantic aspects of a Web Service with a machine-interpretable and also understandable way enabling automatic interaction with services during their entire lifecycle. As far as publishing and discovery procedures are concerned, the provider can describe Web Service functionality and capability using terms derived form a semantic model. At the same time, requestors can use the same ”tools” for describing requesting service desired functionality. Thus, afterwards, reasoning techniques can be used to find the semantic similarity between the service description and the request. During composition, the functional aspect of the annotations can be used to aggregate the functionality of multiple services to create useful service compositions. During invocation, mappings between the semantic annotated concepts use to describe Web Service are mapped into XML-based SOAP messages to enable service execution. The description of Web Services in a machine-understandable fashion is ex-