{'fraction_non_alphanumeric': 0.016903313049357674, 'fraction_numerical': 0.0, 'mean_word_length': 5.271186440677966, '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}}
Service-Level Interoperability Issues of Platform as a Service

The numerous heterogeneities among different providers make platform as a service interoperability an interesting and complex research and practical problem. For example, each provider offers its own remote application programming interfaces (APIs). The main aim of this paper is to identify and address service-level interoperability issues when using APIs from different commercial providers of platform as a service. First, we define use case to add current user information from one platform as a service offer to the application hosted on another offer. To address interoperability problems, the ontology driven data mediation will be used and tested in this use case. Remote vendors' APIs are implemented as web services. Resulting web operations and their inputs/outputs are semantically annotated using cross-PaaS concepts from the developed platform as a service OWL ontology. Next, SAWSDL and XSLT are used to define service type mappings. Actual composition of platform as a service APIs is implemented by means of AI planner and developed Java web application. Testing and validation was performed on a case where current Sales force's user is added to data container in Vosao content management system deployed on Google App Engine. Novelty of the paper is a specific application domain (composition of operations defined in PaaS APIs) and new algorithm for identification of interoperability problems.