Developing RDF-based Web Services for supporting runtime matchmaking and invocation

Liu, Dong; Dietze, Stefan; Domingue, John

doi:10.1109/nwesp.2011.6088211

Cited by 3 publications

(4 citation statements)

References 18 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…However, when the additional services were provided by a third party, the addition of JSON-LD-based annotations was not the appropriate solution to adopt. Based on Yu et al [9], the development of the semantic description annotation used the RDF format, with the inclusion of several sections, namely (1) namespace construction, service and operation name, as well as endpoint invocation, (2) service categorization, (3) HTTP method declarations for service calls (GET, POST, PUT, DELETE, or PATCH), and (4) de nition of input and output parameters, as well as their reference models. Therefore, registered web services are exposed to several capabilities, using the RDF-based semantic description annotations.…”

Section: Related Workmentioning

confidence: 99%

“…Although a formal form for describing service semantics has not been found due to complexity [8], several approaches to create these descriptions have been carried out. This indicates the compilation of semantic description, by adding annotations through JSON-LD [1,4], SA-REST [5] or the Resource Description Framework (RDF) [9][10][11]. According to Guodong et al [12], a knowledge graph was created by extracting the entities, attributes, and several program relationships of different structural web pages and data sources.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

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%

Section: Introductionmentioning

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

“…However, when the additional services were provided by a third party, the addition of JSON-LD-based annotations was not the appropriate solution to adopt. Based on Yu et al [9], the development of the semantic description annotation used the RDF format, with the inclusion of several sections, namely (1) namespace construction, service and operation name, as well as endpoint invocation, (2) service categorization, (3) HTTP method declarations for service calls (GET, POST, PUT, DELETE, or PATCH), and (4) definition of input and output parameters, as well as their reference models. Therefore, registered web services are exposed to several capabilities, using the RDF-based semantic description annotations.…”

Section: Related Workmentioning

confidence: 99%

“…Although a formal form for describing service semantics has not been found due to complexity [8], several approaches to create these descriptions have been carried out. This indicates the compilation of semantic description, by adding annotations through JSON-LD [1][2][3][4], SA-REST [5] or the Resource Description Framework (RDF) [9][10][11]. A knowledge graph was created by extracting data from set of web pages and data sources then subsequently converted into structured data, such as triple RDF [12].…”

mentioning

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

Designing Semantic Web Service Based on OAS 3.0 through Relational Database

Muhamad

Suhardi

Bandung

2020

2020 International Conference on Information Technology Systems and Innovation (ICITSI)

View full text Add to dashboard Cite

Developing RDF-based Web Services for supporting runtime matchmaking and invocation

Cited by 3 publications

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

Designing Semantic Web Service Based on OAS 3.0 through Relational Database

Contact Info

Product

Resources

About