Comparing and evaluating terminology services application programming interfaces: RxNav, UMLSKS and LexBIG

Application Programming Interfaces (APIs) are everyday tools for every software professional. When creating an API, a designer typically abstracts the tasks the API intends to perform. The API user, on the other hand, should use the API to perform specific-propose tasks. During the development of an API, the designer needs to write dialogues with which the user will interact with the API, performing a conversation between them. In this way, an API capable of offering effective dialogues to its users is called a conversational API. A conversational API is the one that is capable of communicating to its users its form of use and its internal logic of operation, making it clear the design decisions when abstracting concepts and tasks. In this paper, we present Colloquy, an evidence-based method to support the design of conversational APIs. Colloquy was conceived based on the lessons learned from an action research we conducted to identify effective strategies for designing conversational APIs. For six months, we followed the redesign of an existing API developed at an R&D laboratory of a large IT company. In this paper, we also present the first empirical evaluation of Colloquy. We conducted a case study in which the method was employed to design an API for refactoring source code in the Java programming language. Among other benefits, we found that Colloquy was effective in developing empathy with users and modeling conversations with them. Besides, Colloquy contributed to identifying new requirements and created models as API documentation.

Software reuse through Application Programming Interfaces (APIs) is an integral part of software development. The functionality offered by an API is not always accessed uniformly throughout the lifetime of a client program. We propose Temporal API Usage Pattern Mining to detect API usage patterns in terms of their time of introduction into client programs. We detect concepts as distinct groups of API functionality from the change history of a client program. We locate those concepts in the client change history and detect temporal usage patterns, where a pattern contains a set of concepts that were added into the client program in a specific temporal order. We investigated the properties of temporal API usage patterns through a multiple-case study of three APIs and their use in up to 19 client software projects. Our technique was able to detect a number of valuable patterns in two out of three of the APIs investigated. Further investigation showed some patterns to be relatively consistent between clients, produced by multiple developers, and not trivially derivable from program structure or API documentation.

Application Programming Interfaces (API) are exposed to developers in order to reuse software libraries. API directives are natural-language statements in API documentation that make developers aware of constraints and guidelines related to the usage of an API. This paper presents the design and the results of an empirical study on the directives of API documentation of object-oriented libraries. Its main contribution is to propose and extensively discuss a taxonomy of 23 kinds of API directives.

PurposeThis study aims to identify the developer’s objectives, current state-of-the-art techniques, challenges and performance evaluation metrics, and presents outlines of a knowledge-based application programming interfaces (API) recommendation system for the developers. Moreover, the current study intends to classify current state-of-the-art techniques supporting automated API recommendations.Design/methodology/approachIn this study, the authors have performed a systematic literature review of studies, which have been published between the years 2004–2021 to achieve the targeted research objective. Subsequently, the authors performed the analysis of 35 primary studies.FindingsThe outcomes of this study are: (1) devising a thematic taxonomy based on the identified developers’ challenges, where mashup-oriented APIs and time-consuming process are frequently encountered challenges by the developers; (2) categorizing current state-of-the-art API recommendation techniques (i.e. clustering techniques, data preprocessing techniques, similarity measurements techniques and ranking techniques); (3) designing a taxonomy based on the identified objectives, where accuracy is the most targeted objective in API recommendation context; (4) identifying a list of evaluation metrics employed to assess the performance of the proposed techniques; (5) performing a SWOT analysis on the selected studies; (6) based on the developer’s challenges, objectives and SWOT analysis, presenting outlines of a recommendation system for the developers and (7) delineating several future research dimensions in API recommendations context.Research limitations/implicationsThis study provides complete guidance to the new researcher in the context of API recommendations. Also, the researcher can target these objectives (accuracy, response time, method recommendation, compatibility, user requirement-based API, automatic service recommendation and API location) in the future. Moreover, the developers can overcome the identified challenges (including mashup-oriented API, Time-consuming process, learn how to use the API, integrated problem, API method usage location and limited usage of code) in the future by proposing a framework or recommendation system. Furthermore, the classification of current state-of-the-art API recommendation techniques also helps the researchers who wish to work in the future in the context of API recommendation.Practical implicationsThis study not only facilitates the researcher but also facilitates the practitioners in several ways. The current study guides the developer in minimizing the development time in terms of selecting relevant APIs rather than following traditional manual selection. Moreover, this study facilitates integrating APIs in a project. Thus, the recommendation system saves the time for developers, and increases their productivity.Originality/valueAPI recommendation remains an active area of research in web and mobile-based applications development. The authors believe that this study acts as a useful tool for the interested researchers and practitioners as it will contribute to the body of knowledge in API recommendations context.

External service integration and adherence to industry standards has become ever more important for collections data management platforms. External APIs (Application Programming Interfaces), allow for the development of bi-directional data flows critical to service integration. In contrast to service-oriented backend APIs, public APIs must have continually up-to-date, comprehensive documentation that covers common use cases, on-the-fly request validation, and meaningful error messages. OpenAPI (OpenAPI Initiative 2021), a machine-readable API documentation specification can help significantly with testing and maintenance, and libraries can be used to automate common maintenance tasks. Specify 7 is a biological collections data management platform developed by the Specify Collections Consortium (Specify Software Consortium 2021). This presentation summarizes the challenges and lessons learned with publishing the existing backend Specify 7 API to a public-facing external API. Each Specify 7 API is composed of 200 resources. A standard set of CRUD (Create, Read, Update, Delete) operations is provided for each resource for client interaction with a group of service-based endpoints for bulk operations such as file uploads, file-based data imports, and attachment manipulation. To support the migration, we developed a custom library to enhance request validation. Parameter validation is extended through a real-time comparison against the existing schema and data. The library is available to the community under a MIT license on GitHub (https://github.com/specify/open_api_tools/). In this presentation, we will close with an overview of the next steps for the Specify 7 public API. These include: An update to the latest OpenAPI specification, version 3.1. The latest version aims to increase compatibility with the Javascript Object Notation (JSON) Schema specification, and thus would allow us to use JSON Schema (IETF Trust 2021) validation frameworks. An in-depth evaluation of GraphQL for its ability to force all endpoints to be strongly typed and automatic validation of request parameters and response objects. An update to the latest OpenAPI specification, version 3.1. The latest version aims to increase compatibility with the Javascript Object Notation (JSON) Schema specification, and thus would allow us to use JSON Schema (IETF Trust 2021) validation frameworks. An in-depth evaluation of GraphQL for its ability to force all endpoints to be strongly typed and automatic validation of request parameters and response objects.

The integration of terminologies is still a challenging problem in medical informatics research and software applications, due to the high number of heterogeneous terminologies. In this paper, we present a generic API (Application Programming Interface) for a multi-terminology multilingual terminology service, and PyMedTermino, its open-source implementation in Python with 5 terminological resources (ICD10, SNOMED CT, MedDRA, CDF, VCM iconic language) and the UMLS compendium. This service has been designed for research and educational purpose. It offers various advanced functionalities rarely present in terminology services.

Recent industrial and academic research has focused on data-driven analytics with smartphones by collecting user interaction, context, and device systems data through Application Programming Interfaces (APIs) and sensors. The Android operating system provides various APIs to collect such mobile usage and sensor data for third-party developers. Usage Statistics API (US API) and Accessibility Service API (AS API) are representative Android APIs for collecting app usage data and are used for various research purposes, as they can collect fine-grained interaction data (e.g., app usage history and user interaction type). Furthermore, other sensor APIs help to collect a user’s context and device state data, along with AS/US APIs. This review investigates mobile usage and sensor data-driven research using AS/US APIs by categorizing the research purposes and the data types. In this article, the surveyed studies are classified as follows: five themes and 21 subthemes and a four-layer hierarchical data classification structure. This allows us to identify a data usage trend and derive insight into data collection according to research purposes. Several limitations and future research directions of mobile usage and sensor data-driven analytics research are discussed, including the impact of changes in the Android API versions on research, the privacy and data quality issues, and the mitigation of reproducibility risks with standardized data typology.

Despite their rapid growth, the utilisation of application programming interfaces (APIs) poses challenges for companies under pressure to yield productive systems integration. APIs of larger systems tend to be large, complex and have reduced modularity and quality, which makes them cumbersome to comprehend and use. These challenges can be addressed by static API analysis that focuses on studying API code itself and deriving business entities and dependencies from operational signatures. However, existing techniques for static analysis of APIs face the challenges in deriving a sufficient coverage of business entity relationship types from implementation-oriented API operational signatures carrying limited semantic insights. The paper aims to address such problems by supporting static analysis techniques for APIs that improve their modularity. Our approach adopts an object-oriented paradigm where the concept of “object” is exemplified by the notion of business entity. It systematically applies interface analysis methods and techniques for eliciting knowledge of business entities and their attributes, for deriving the temporal order of calling operations across multiple business entities, and for learning and extracting various ways of invoking a service via APIs. The approach is implemented as an open-source tool and applied to a group of widely-deployed services in practice for validation. The research contributes to identifying key aspects of both the structure and behaviour of APIs, which will lead to building a simplified but comprehensive interface (presentation) layer to assist service users in understanding complex and overloaded interfaces as well as to facilitate efficient and effective service integration.

We propose a method for examining and measuring the complexity of animal social networks that are characterized using association indices. The method focusses on the diversity of types of dyadic relationship within the social network. Binomial mixture models cluster dyadic relationships into relationship types, and variation in the preponderance and strength of these relationship types can be used to estimate association complexity using Shannon’s information index. We use simulated data to test the method and find that models chosen using integrated complete likelihood give estimates of complexity that closely reflect the true complexity of social systems, but these estimates can be downwardly biased by low-intensity sampling and upwardly biased by extreme overdispersion within components. We also illustrate the use of the method on two real datasets. The method could be extended for use on interaction rate data using Poisson mixture models or on multidimensional relationship data using multivariate mixture models.Significance statementAnimals from many species interact socially with multiple individuals, and these interactions form a social network. Pairs of individuals have social relationships that differ in their strength and type. This social complexity has long interested behavioural biologists, particularly in the context of social cognition. Measuring social complexity, however, presents challenges. We propose a new method for measuring the complexity of animal social networks. Our approach is based on quantifying variation in the strengths of social connections (measured using association indices) which we use to classify different types of pairwise relationships. We, then, use the number, strength and prevalence of these different types of relationships to measure association complexity. Our approach can be used to compare association complexity between populations and/or species. We provide code that researchers can use with their own datasets.

Although smuggling is commonly assumed to happen in remote and difficult-to-access borderlands, in reality, smuggling is most prevalent in areas that states tightly control, including at formal border crossings. To understand this puzzle, this article explores the relationship between states and smugglers at international borders. Based on extensive empirical research in various borderlands in North Africa and Southeast Asia, it argues that different kinds of smugglers prefer different types of relationships with the state. The article outlines six ideal types of such relationships. It contends that these types of relationships are the dominant factor in how different smuggling networks choose routes along a border. The findings have implications for our understanding of smuggling and policies that aim at addressing smuggling, especially regarding the effects of border fortifications and corruption prevention.

ObjectiveOur objective was to use multiple romantic relationship dimensions to identify a typology of emerging adult romantic relationships.BackgroundEmerging adult romantic relationships vary in terms of their relational dynamics, emotional and physical intimacy, and commitment. Understanding the diversity in emerging adult romantic relationships is crucial for developing effective relationship education for emerging adults as they make decisions about their romantic partnerships.MethodUsing data from 396 romantically involved but unmarried emerging adults, we used cluster analysis to identify a typology of romantic relationships based on relational dynamics (i.e., warmth and support and negative interactions), relationship duration, consolidation (i.e., number of nights and percentage of free time spent together), and commitment (i.e., likelihood of marrying partner).ResultsThe results indicated five types of relationships: (a) happily consolidated (30.8%), (b) happily independent (18.9%), (c) exploratory (17.9%), (d) stuck (23.0%), and (e) high intensity (9.3%). Demographic characteristics, depressive symptoms, life satisfaction, current cohabitation, and cycling within the current relationship varied between the relationship types.ConclusionsThere appear to be meaningful and important variations among the types of romantic relationships that emerging adults pursue. The associations between relationship type and well‐being depends on the interplay between relational dynamics, consolidation, and commitment.ImplicationsIndividuals in different types of relationships may require targeted interventions to help them move out of problematic relationships or to help them build skills for developing and maintaining relationship quality. Suggestions for each type of relationship are provided.

Image Processing and Computer Vision solutions have become commodities for software developers, thanks to the growing availability of Application Programming Interfaces (APIs) that encapsulate rich functionality, powered by advanced algorithms. Tech giants like Apple, Google, IBM, and Microsoft have made APIs and micro-services available in the cloud for the agile integration of machine learning and intelligent features onto everyday applications. As privacy and cyber welfare become prime concerns, special efforts have been devoted in the field of face processing and recognition. In this context, this paper provides a friendly, intuitive and fun to use mobile app that leverages the state-of-the-art APIs for face, age, gender and emotion recognition. The Face- It-Up app was implemented for the iOS platform and uses the Microsoft Cognitive Services APIs as a tool for human vision and face processing research. Experimental work on image compression, upside-down orientation, the Thatcher effect, negative inversion, high frequency, facial artifacts, caricatures and image degradation were performed to test the application. For this purpose, we used the Radboud and 10k US Adult Faces Databases. The app benefits from accessing high-resolution imagery and touch input from the smart-devices, allowing for a wide range of new experiments from the user perspective. Furthermore, our approach serves as a potential framework for new initiatives in image-based biometrics, the Internet of Things, and citizen science.

Information diffusion has been widely studied in networks, aiming to model the spread of information among objects when they are connected with each other. Most of the current research assumes the underlying network is homogeneous, i.e., objects are of the same type and they are connected by links with the same semantic meanings. However, in the real word, objects are connected via different types of relationships, forming multi-relational heterogeneous information networks. In this paper, we propose to model information diffusion in such multi-relational networks, by distinguishing the power in passing information around for different types of relationships. We propose two variations of the linear threshold model for multi-relational networks, by considering the aggregation of information at either the model level or the relation level. In addition, we use real diffusion action logs to learn the parameters in these models, which will benefit diffusion prediction in real networks. We apply our diffusion models in two real bibliographic information networks, DBLP network and APS network, and experimentally demonstrate the effectiveness of our models compared with single-relational diffusion models. Moreover, our models can determine the diffusion power of each relation type, which helps us understand the diffusion process better in the multi-relational bibliographic network scenario.

Web Application Programming Interfaces (APIs) allow systems to interact with each other over the network. Modern Web APIs often adhere to the REST architectural style, being referred to as RESTful Web APIs. RESTful Web APIs are decomposed into multiple resources (e.g., a video in the YouTube API) that clients can manipulate through HTTP interactions. Testing Web APIs is critical but challenging due to the difficulty to assess the correctness of API responses, i.e., the oracle problem. Metamorphic testing alleviates the oracle problem by exploiting relations (so-called metamorphic relations) among multiple executions of the program under test. In this paper, we present a metamorphic testing approach for the detection of faults in RESTful Web APIs. We first propose six abstract relations that capture the shape of many of the metamorphic relations found in RESTful Web APIs, we call these Metamorphic Relation Output Patterns (MROPs). Each MROP can then be instantiated into one or more concrete metamorphic relations. The approach was evaluated using both automatically seeded and real faults in six subject Web APIs. Among other results, we identified 60 metamorphic relations (instances of the proposed MROPs) in the Web APIs of Spotify and YouTube. Each metamorphic relation was implemented using both random and manual test data, running over 4.7K automated tests. As a result, 11 issues were detected (3 in Spotify and 8 in YouTube), 10 of them confirmed by the API developers or reproduced by other users, supporting the effectiveness of the approach.

The purpose of this study is to explore the antecedent of organization–public relationships that affects relationship outcomes. Organizations, realizing the interdependence with their publics, developed different types of relationships, such as communal and exchange relationships. Therefore, there should be other types of relationships influencing the quality of the relationships. In this study, 40 qualitative interviews with 36 multinational companies (from Fortune 500 and Taiwan's Commonwealth 1000) in 9 cities in China and Taiwan were conducted to explore more types of relationships. This study discovered mutual communal, covenantal, contractual, symbiotic, manipulative, and exploitive relationships multinational companies have developed with their Chinese publics. The findings also indicate that covenantal relationships help reach a win–win ground, and mutual communal relationships benefit multinational companies the most in achieving effectiveness. A continuum of types of relationships is provided in this study.