REGISTRY FOR RESTful WEB SERVICE: RESTRegistry

Rathod, Digvijaysinh

doi:10.29121/granthaalayah.v5.i7.2017.2114

Cited by 5 publications

(3 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The service registry holds a central position in helping service-oriented software developers determine candidates for several composed programs. This is generally public and open to all users and programmers [17], due to primarily facilitating the discovery of web services as a basic requirement element. Through the registry, the presence (location) and assembly of services and media, including languages, tools, and machines are often demonstrated, for the required provision of more complex functionality to be met [18].…”

Section: Related Workmentioning

confidence: 99%

Transforming OpenAPI Specification 3.0 Documents into RDF-based Semantic Web Services

Muhamad

Suhardi

Bandung

2022

Preprint

View full text Add to dashboard Cite

Service-Oriented Architecture (SOA) designs are translated into software units and meet principles such as discoverable, reusable, and compostable. Web services are becoming a technology adopted by service providers so that services can be discovered and reused by clients. To complete more complex business processes, a set of existing services can be composed following a certain flow. To support client needs, these services should be equipped with comprehensive user interfaces in the form of web descriptions, which outlines the service capabilities regarding specific standard or language. This should be considered through an understandable format for humans and/or machines. In the Representational State Transfer (REST) architectural style, the OpenAPI Specification (OAS) is used as a reference to create web service descriptions. However, it only supports syntactic interoperability, leading to the incapability of supporting the automated selection process. The main challenges in this automation process should be overcome by providing web service semantics to create "understandable" services that automatically interact with one other. This indicates that the OAS document is improved by adding semantics to each resource. Therefore, this study aims to develop a system capable of transforming resources in OAS documents into RDF-based semantic web services. The OAS structure was the main basis for creating a relational database schema. Furthermore, a database normalization technique was implemented to design a schema, which stored all objects in an OAS document. To map resources on the RDF data model, an ontology was developed, explaining the concepts and the relationships between them. This adopted the published linked-open vocabulary and corresponded to the characteristics of each identified OAS resource. To build RDF-based semantic web services, R2RML was used to generate the relational database model into triple RDF. The proposed system was also tested through prototyping and using a dataset of 106 OAS documents, which were downloaded from APIs.guru between 5–10 May 2021. The number of triple RDFs generated from each document varied according to the rate of resources. This was observed when an OAS document produced 36 to 16,505 triple RDF in a specific dataset. The final result showed the formation of a knowledge base in triple RDF format, which was managed using a graph management database. This led to the utilization of the repository semantic web services as a basis for service selection (using SPARQL) so that service operations can be found as well as input and output parameters that correspond to the service composition requirements. The use of relational databases to store OAS resources also increased the efficiency of reuse by approximately 48%, due to service developer designing interoperability between uniform parameter services, which were subsequently used as input and output.

show abstract

Section: Related Workmentioning

confidence: 99%

Transforming OpenAPI Specification 3.0 Documents into RDF-based Semantic Web Services

Muhamad

Suhardi

Bandung

2022

Preprint

View full text Add to dashboard Cite

show abstract

“…The service registry holds a central position in helping service-oriented software developers determine candidates for several composed programs. This is generally public and open to all users and programmers [13], due to primarily facilitating the discovery of web services as a basic requirement element. Through the registry, the presence (location) and assembly of services and media, including languages, tools, and machines are often demonstrated, for the required provision of more complex functionality to be met [14].…”

Section: Related Workmentioning

confidence: 99%

Transforming OpenAPI Specification 3.0 documents into RDF-based semantic web services

2022

View full text Add to dashboard Cite

Web services are provided with documents that at the very least specify the endpoint, input parameters, and output or response of each operation to expose their capabilities. This should be considered through an understandable format for humans and/or machines. In the Representational State Transfer (REST) architectural style, the OpenAPI Specification (OAS) is used as a reference to create web service descriptions. However, it only supports syntactic interoperability, leading to the incapability of supporting the automated selection process. To overcome this, OAS documents must be enhanced by including semantics to each resource to provide “understandable” services. Therefore, this study aims to develop a system capable of transforming resources in OAS documents into RDF-based semantic web services. To begin, a relational database schema based on the OAS structure is created to store all objects in the OAS document. The published open-linked vocabulary was then used to create the ontology, which maps resources and their relationships on the RDF data model. To build RDF-based semantic web services, R2RML was used to generate the relational database model into triple RDF. The proposed system was also tested through prototyping and using a dataset of 106 OAS documents, which were downloaded from APIs.guru between 5–10 May 2021. The number of triple RDFs generated per document varied with resource rate. An OAS document generates 36 to 16,505 triple RDF in a dataset. The end product was a triple RDF knowledge base maintained by a graph management database. It is now possible to find service operations, input and output parameters, and service composition requirements utilizing the repository semantic web services using SPARQL. On the other hand, the use of relational databases to store OAS resources increased reuse efficiency by approximately 48%, owing to service developers designing interoperability between uniform parameter services, which were then used as input and output.

show abstract

“…Service separation occurs in the background between the front-end and back-end which increases the intelligence and accuracy of distribution management. SOAP/WSDL has standard registry as described in research [9], where producer can register service specification and consumer can discover service endpoint using UDDI. Recently RESTful web service gained momentum in development of distributed application and research community already started discussion about RESTful based Service Oriented Architecture (SOA) but there is no standard central repository.…”

Section: Service Oriented Architecture Restfulmentioning

confidence: 99%

Integration Information Systems Design of Material Planning in the Manufacturing Industry using Service Oriented Architecture

Madefanny¹,

Suharjito²

2021

Adv. sci. technol. eng. syst. j.

View full text Add to dashboard Cite

PT XYZ has an Enterprise Resource Planning application that is used by the Planning Department to view stocks and plan production materials. Currently calculation of production materials takes more than 30 seconds just to export to Excel then a few minutes to adjust the data format to the planning form and the data used is not real-time. Each item needs to be calculated one by one per period, then the size of the Excel file used varies according to the time period and requires more storage. To support real-time integration and process efficiency planning and storage reduction, an integration between Enterprise Resource Planning application and web applications has been made using a Service Oriented Architecture approach. The Web service uses RESTful and has been tested using Quality of Service and the Vulnerability Test. Based on the test results using the Jmeter simulation with 10 users, it is obtained Latency 1.2 seconds and Load Time 1.2 seconds with an average amount of data sent 1280.73 bytes. The test results using OWASP ZAP show vulnerability to the web service header made from the web server version used by PHP version 5.6.40. With the results of these tests, the web service is able to replace the export and import process as well as create real-time data connectivity and replace storage media with databases, thereby reducing the time needed for planning activities.

show abstract

REGISTRY FOR RESTful WEB SERVICE: RESTRegistry

Cited by 5 publications

References 10 publications

Transforming OpenAPI Specification 3.0 Documents into RDF-based Semantic Web Services

Transforming OpenAPI Specification 3.0 Documents into RDF-based Semantic Web Services

Transforming OpenAPI Specification 3.0 documents into RDF-based semantic web services

Integration Information Systems Design of Material Planning in the Manufacturing Industry using Service Oriented Architecture

Contact Info

Product

Resources

About