Adapting SAWSDL for Semantic Annotations of RESTful Services

Improving semantic web services discovery using SPARQL-based repository filtering

“…Pedrinaci et al present a service repository called iServe that exposes service descriptions as linked data in terms of a Minimal Service Model (MSM) [32]. This model serves the purpose of an ontology of integration that simplifies SWS frameworks, integrating not only OWL-S, WSMO, SAWSDL and WSMO-Lite services, but also MicroWSMO [47] or SA-REST [48] descriptions of Web APIs. Our proposal can be also applied to MSM so that our filters can be applied to services registered in iServe, that provides a SPARQL endpoint that can be used to retrieve descriptions for a subsequent discovery.…”

Efficient runtime service discovery and consumption with hyperlinked RESTdesc

“…Later on, an adaptation specifically for RESTful services was proposed [20]. However, SAWSDL is only concerned with giving a semantic definition to the input and output parameters of services, rather than connecting them in a functional way.…”

Lightweight Semantic Annotation of Geospatial RESTful Services

“…The main proposed formalisms for describing these services are: the Web Application Description Language 1 (WADL), which describes syntactically RESTful services and the resources that they access; its semantic annotation extension [19]; MicroWSMO [3], which uses hREST (HTML for RESTful services) [3,5]; and SA-REST [2,8], which uses SAWSDL [1] and RDFa 2 to describe service properties. From a broader point of view, the work done in the state of the art on Semantic Web Services (SWS) has mainly focused on WS-*services.…”

“…Other approaches are more lightweight (e.g., [1,2]). The authors advocate an integrated lightweight approach for describing semantically RESTful services.…”

“…More recently, these (usually heavyweight) approaches have started to be adapted into a more lightweight manner for the semantic description of RESTful services [1,5,8]. However, most of the processes related to the annotation of RESTful services (e.g., [2,11]) still require a large amount of human intervention.…”