A Citation Data Collector Tool of Author’s Profiles in Scopus Based on Web and Application Programming Interface (API)

Web service-based application development has become a vital component of the modern in-formation technology ecosystem. The implementation of web services facilitates interoperability among diverse systems and platforms. REST API (REpresentational State Transfer Application Programming Interface) is one of the most popular architectures for creating efficient and scalable web services. This study examines the implementation of REST API in the development of web service-based applications. The case study focuses on the creation of a Web service-based Research Proposal Selection System. The REST API implementation method in this study adheres to the system development life cycle (SDLC) to ensure that the developed API meets business needs while being efficient, secure, and reliable. The analysis phase is conducted to gather both functional and non-functional REST API requirements. During the design phase, the REST API architecture is designed in detail, including how data will be transferred and processed, and how the API will interact with databases and other systems. Furthermore, in the implementation phase, the REST API is developed, ensuring that each endpoint operates correctly. In developing the Proposal Selection System, the implementation of web services integrates data from various existing sys-tems, including employee, academic, and research data. The system encompasses various features, such as proposal import, proposal mapping, proposal review, proposal assessment, proposal se-lection, and reporting. The research findings indicate that implementing the REST API simplifies the development of web service applications. The test results reveal that the average response time is relatively stable, measuring 31 ms without iterations and 29 ms with five iterations.

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.

Software Defined Networking (SDN) is a programmable network technology which aims to move an existing controller role in hardware equipment into an area of software. The control layer employs an application programming interface (API) to communicate with the application and infrastructure layers as it is centered between two layers. As the Southbound API used in communication with the infrastructure layer, the OpenFlow is defined as the current de factor standard in most SDN controllers. In contrast, the Northbound API used in communication with the application layer had no standard. Only REST API is used in Floodlight or OpenDaylight. Thus, the development in application area where SDN's true value lies to achieve network intelligence is not promoted well enough. In this paper, a gRPC protocol is proposed as useable Northbound API rather than REST API used in some controllers, and applicability of new standard as Northbound API is investigated.

The aim of this system is to use open source APIs to invoke and process the results of the Web services and to apply confidentiality and integration to the result of the Web services. In this system Web Services are requested using URL (Uniform Resource Locator) query to the WWW instead of SOAP message. When invoking the web services using JAX-RPC (Java Api for Xml-Based Remote Procedure Call) with SOAP request, the result returned may not be received properly due to de-serialization problem of complex XML data sets. Therefore it is required to invoke such services by submitting the query as URL query and received the results as XML data set. This XML data set may be hampered by man-in-middle attack during transfer. Hence this system uses open source APIs for providing XML signature and XML encryption. At the receiver after decryption and integrity check, the required node from XML data set is extracted and presented to the user. This article is focused on usage of open source APIs (Application program interface) for invoking web services as Restful Web services, applying XML signature and XML encryption, parsing the XML result after reverse process at receiver side and extracting the required nodes according to the user given condition. The problem of de-serialization in receiving huge XML result is resolved in the proposed system.

Hypermedia as the Engine of Application State (HATEOAS) is a principle that has been built upon the term hypermedia to refer to a constraint on the Representational State Transfer (REST) application architecture. This principle distinguishes REST from other application architectures, such as Simple Object Access Protocol in a way that client applications (e.g., a web app or a mobile app) need no prior knowledge for interacting with a REST-based Application Programming Interface (API) beyond a generic understanding of its hypermedia. Ion is an intuitive JavaScript Object Notation-based hypermedia type for REST, which can help software developers realize the principle of HATEOAS in their API design with ease. The goal of the work that is described in this paper has been to practically demonstrate the use of Ion in practice to have a self-documented REST API. For this purpose, a C# library has been implemented to demonstrate the use of Ion in having a REST API with self-documentation.

Web 2.0 has been happening on the fixed Internet side for several years already. This phenomenon has forced traditional Telco operators to consider new business models. One of the possible models is to utilize the IP Multimedia Subsystem (IMS) network architecture. Using the IMS, Telco operators have more control over the data instead of becoming just bit pipes. In addition, operators interest in providing open Application Programming Interfaces (APIs) exposing IMS and network assets has grown. In this paper, a RESTful IMS API implementation, is represented. The design and implementation of the API exposing IMS functionality is shown. In addition, the implementation of a REST application using the API is described.

Modern web services widely provide RESTful APIs for clients to access their functionality programmatically. Fuzzing is an emerging technique for ensuring the reliability of RESTful APIs. However, the existing RESTful API fuzzers repeatedly generate invalid requests due to unawareness of errors in the invalid tested requests and lack of effective strategy to generate legal value for the incorrect parameters. Such limitations severely hinder the fuzzing performance. In this paper, we propose DynER, a new test case generation method guided by dynamic error responses during fuzzing. DynER designs two strategies of parameter value generation for purposefully revising the incorrect parameters of invalid tested requests to generate new test requests. The strategies are, respectively, based on prompting Large Language Model (LLM) to understand the semantics information in error responses and actively accessing API-related resources. We apply DynER to the state-of-the-art fuzzer RESTler and implement DynER-RESTler. DynER-RESTler outperforms foREST on two real-world RESTful services, WordPress and GitLab with a 41.21% and 26.33% higher average pass rate for test requests and a 12.50% and 22.80% higher average number of unique request types successfully tested, respectively. The experimental results demonstrate that DynER significantly improves the effectiveness of test cases and fuzzing performance. Additionally, DynER-RESTler finds three new bugs.

BackgroundStability during early postnatal life in preterm infants is related to better outcomes. Although vital signs are monitored continuously in Neonatal Intensive Care Unites, this monitoring does not include all physiological parameters nor data such as movement patterns. Although there are scattered sources of data, there is no centralized data hub for neonates information.ResultsWe have created the first neonate data hub for easy and interactive access to upload or download postural, physiological, and medical data of neonates: NeoVault. NeoVault is a platform that provides access to information through two interfaces: 1) via a Web interface (designed for medical personnel, data scientists, researchers); and 2) via a RESTful API (Application Programming Interfaces) -designed for developers-, aiming to integrate access to information into third-party applications. The web access allows searching and filtering according to specific parameters, visualization of data through graphs and images, and generation of datasets in CSV format. Access through the RESTful API is described in OpenAPI, enabling access to information from any device, facilitating it in an interoperable format. Currently, it contains nearly 800,000 postural records and 3.000 physiological data entries. The physiological and postural data stored for each neonate in NeoVault are collected through the NRP (Neonates Recording Platform) tool, which allows for the automatic and reliable collection of data.ConclusionNeoVault is an open platform for simple access to postural, physiological, and medical data of neonates that can be utilized by researchers, data scientists, medical personnel, and programmers. It enables integration into third-party applications and the generation of customized datasets.

<span lang="EN-US">Mobile applications that have data transactions between users require a database relational database management system (RDBMS) and RESTful API operating on the hosting service so that all users can access the data. Renting a hosting service is not cheap and creating a RESTful API takes plenty of time. As an alternative to hosting, a free version of the Cloud Firestore service gives full access rights to the database and has an application programming interface (API) to manage data or access data. However, the free version of Cloud Firestore has limitations in terms of storage capacity, read, write, and delete processes. Therefore, redesigning process of the database was carried out into a low-cost version of the database model consisting of SQLite database and a low-cost version of the NoSQL database to overcome this problem. The goal is to reduce storage space usage and read, write, and delete processing on Cloud Firestore. The low-cost version of the database was tested with 6,030 data. The results obtained were savings of 47.27% storage usage, 83.08% write usage, 91.26% read process usage, and 83.19% delete process usage compared to the test results of the relational database model.</span>

Python Materials Genomics (pymatgen): A robust, open-source python library for materials analysis

REST4CEP: RESTful APIs for complex event processing

RESTful Web service composition with BPEL for REST

A Web-Based Perioperative Dashboard as a Platform for Anesthesia Informatics Innovation.

Background : Emergency incidents that occur in Indonesia are increasing day by day, both emergency incidents due to traffic accidents and incidents due to disease. The Indonesian government issued PERMENKES number 19 of 2016 concerning the Integrated Emergency Management System, in the creation of the SPGDT it is expected to be able to handle emergency cases in an integrated manner so as to minimize cases of disability and death. The Yogyakarta Special Region Health Service is currently running well in the implementation of SPGDT, but currently, the SPGDT application does not have the Mobile-Apps feature, especially on the Tracking Ambulance menu. With the ambulance tracking menu, people can easily make ambulance calls based on emergency cases that occur and also people don't need to worry if they find an emergency incident but the ambulance doesn't come, with ambulance tracking people can also see the movement of an ambulance that is on "standby" or in the process of “evacuating” an emergency event. Methods: the method in this research is the action research method. This action research method was chosen because the stages of action research start from diagnosis, planning, action and evaluation. Results: the results of this study, at the stage of identifying needs based on user actors. At the planning stage, what data flows are designed , created and the features needed . At the action stage, it produces a user interface design with Figma . At the evaluation stage, the final prototype score was assessed based on the System Usability Scale (SUS) questionnaire with the final score on the driver page prototype getting a final score of 62, while the prototype for paramedics got a final score of 71. And finally, the general public prototype got a final score of 69 Conclusions: The process of developing the design, planning and implementation of the mHealth application services requires the collaboration of various sectors, both from the user side from the health side. Feedback from various responses is the key to success to ensure the relevance and sustainability of the mHealth application services. Providing useful and easy-to-use and ensuring continuity of technical support can help smooth the process of using the mHealth application in day healthcare .

Detailed documentation and software tests are key factors for the success of a web application programming interface (API). When designing an API, especially in a design first approach, it is relevant to define a formal contract, known as API specification. This document must contain all necessary information regarding the API behavior. Thereby, the specification can be used to dynamically generate API components like documentation, client and server code, and software tests, reducing development and maintenance costs. This chapter presents a study of OpenAPI specification and its application on designing a new RESTful API for E-goi. It also presents a set of solutions for generating documentation, client code libraries, and test cases.