Participation Reports help Crossref members drive research further

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.

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.

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.

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.

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

Open Researcher and Contributor ID (ORCID) is a community-driven non-profit organization that provides an open registry of persistent identifiers for researchers and scholars. The mission of ORCID is to address the name ambiguity problem in research and scholarly communication. ORCID works with the research community to embed identifiers in research workflows: grant applications, manuscript submissions, association membership renewal, meeting abstract submission, everywhere that a person can be connected with a research or scholarly contribution. This article describes ORCID, and its adoption by the research community, and provides examples of how ORCID identifiers are being integrated by organizations throughout the community and becoming part of the metadata on a diverse set of documents. Ultimately, the goal of ORCID is to improve discoverability, reduce repetitive data entry, and thereby allow researchers and organizations more time to focus on research and scholarly pursuits.

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.

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.

Improving the quality of publications will enhance teaching, support community service, and improve the campus reputation. One of the measurements of research quality can be observed by looking at the number of citations. The more research cited, the greater the effect it will have on other research. In addition, the publication of research results is used by most researchers in relation to the promotion of their academic positions. The position of the author in the research affects the weight value of his/her publication. At this time, no application can be used to classify the author’s position of each publication produced. This paper aims to create an application that acted as a search engine to retrieve and collect researcher data along with a list of their publications from the Scopus database. The application uses a REST API or Web Service of Scopus. Web Service allows the integration of various systems with different platforms or architectures for sharing data and services. This application was built using the PHP and JavaScript programming languages. The application’s development uses the Agile Software Development method. Users can also save the search results for the researcher data and researcher documents list in the MySQL database. Furthermore, this application also allows users to download the search result in their computer devices. The System Usability Scale (SUS) method was used to test the application’s usability and gained 80 as the final score.

<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>

REST4CEP: RESTful APIs for complex event processing

Organization Launched To Solve The Name Ambiguity Problem In Scholarly Research

The article is a review that in the initial part presents main data about the project named ORCID. Open Researcher and Contributor ID which is full name of the project aims to solve the name ambiguity problem in research and scholarly communications by creating a central registry of unique identifiers for individual researchers and an open and transparent linking mechanism between ORCID and other current researcher ID schemes. These identifiers, and the relationships among them, can be linked to the researcher’s output to enhance the scientific discovery process and to improve the efficiency of research funding and collaboration within the research community. ORCID project involved researchers, universities, national laboratories, commercial research organizations, publishers, national scientific agencies, scientometric databases, repositories, and international professional associations. ORCID accounting system provides researchers two main features: a unique identifier to obtain and monitor the results of research; using an application programming interface for transferring data between different accounting systems, and attribution of scientific papers in each of them. Author of the paper describes in details the process of registration in ORCID which consists in filling out serial forms. ORCID provides a persistent digital identifier that distinguishes one researcher from every other researcher and, through integration in key research workflows such as manuscript and grant submission, supports automated linkages between researcher and professional activities ensuring that researcher’s work is recognized. To ensure the connection between the name of the scientist and the results of his scientific activity ORCID ID information should be added while sending manuscript for publication, applying for grants and other research processes, introduce it to the various search browsers, scientometric databases and social networks. This will help to improve scientific international relationships, increase the representation of Ukrainian research work results in the global scholarly communication.

Persistent Identifiers and the Next Generation of Legal Scholarship