{'fraction_non_alphanumeric': 0.02051983584131327, 'fraction_numerical': 0.0, 'mean_word_length': 5.3652173913043475, '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}}
Ontology for OpenAPI REST Services Descriptions

OpenAPI Specification (OAS) defines a description format for REST APIs. In order for a machine to understand the meaning of REST services, OpenAPI service descriptions must be unambiguous. In a previous work we analysed the reasons that cause ambiguities in OpenAPI and showed that, in order to eliminate ambiguities, OpenAPI properties must be semantically annotated and mapped to a semantic model. Leveraging latest results for hypermedia-based construction of Web APIs (i.e. Hydra), the present work forwards this approach and proposes a reference ontology for REST services along with a formal procedure for converting OpenAPI service descriptions to instances of this ontology.