 | Up a level |
Group by: Item Type | No Grouping
Number of items: 4.
Conference or Workshop Item
Resource Oriented Modelling: Describing Restful Web Services Using Collaboration Diagrams
http://jb4-2.eprints-hosting.org/2229
The popularity of Resource Oriented and RESTful Web Services is increasing rapidly. In these, resources are key actors in the interfaces, in contrast to other approaches where services, messages or objects are. This distinctive feature necessitates a new approach for modelling RESTful interfaces providing a more intuitive mapping from model to implementation than could be achieved with non-resource methods. With this objective we propose an approach to describe Resource Oriented and RESTful Web Services based on UML collaboration diagrams. Then use it to model scenarios from several problem domains, arguing that Resource Oriented and RESTful Web Services can be used in systems which go beyond ad-hoc integration. Using the scenarios we demonstrate how the approach is useful for: eliciting domain ontologies; identifying recurring patterns; and capturing static and dynamic aspects of the interface.
Areeb Alowisheq
David Millard
Thanassis Tiropanis
http://jb4-2.eprints-hosting.org/2229
The popularity of Resource Oriented and RESTful Web Services is increasing rapidly. In these, resources are key actors in the interfaces, in contrast to other approaches where services, messages or objects are. This distinctive feature necessitates a new approach for modelling RESTful interfaces providing a more intuitive mapping from model to implementation than could be achieved with non-resource methods. With this objective we propose an approach to describe Resource Oriented and RESTful Web Services based on UML collaboration diagrams. Then use it to model scenarios from several problem domains, arguing that Resource Oriented and RESTful Web Services can be used in systems which go beyond ad-hoc integration. Using the scenarios we demonstrate how the approach is useful for: eliciting domain ontologies; identifying recurring patterns; and capturing static and dynamic aspects of the interface.
Areeb Alowisheq
David Millard
Thanassis Tiropanis
EXPRESS: EXPressing REstful Semantic Services
http://jb4-2.eprints-hosting.org/2227
We introduce a new approach for RESTful Semantic Web Services called EXPRESS. It aims to exploit the similarities between REST and the Semantic Web, such as realization of resources, self describing representations, and uniform interfaces. EXPRESS is straightforward and systematic. It works by identifying resources in ontologies and provides them with a uniform interface. We also discuss other RESTful and non-RESTful approaches to Semantic Web Services and show how they relate.
Areeb Alowisheq
David Millard
http://jb4-2.eprints-hosting.org/2227
We introduce a new approach for RESTful Semantic Web Services called EXPRESS. It aims to exploit the similarities between REST and the Semantic Web, such as realization of resources, self describing representations, and uniform interfaces. EXPRESS is straightforward and systematic. It works by identifying resources in ontologies and provides them with a uniform interface. We also discuss other RESTful and non-RESTful approaches to Semantic Web Services and show how they relate.
Areeb Alowisheq
David Millard
Monograph
Web Service Scenarios
http://jb4-2.eprints-hosting.org/2230
Areeb Alowisheq
David Millard
Thanassis Tiropanis
http://jb4-2.eprints-hosting.org/2230
Areeb Alowisheq
David Millard
Thanassis Tiropanis
Thesis
EXPRESS: Resource-oriented and RESTful Semantic Web services
http://jb4-2.eprints-hosting.org/2226
This thesis investigates an approach that simplifies the development of Semantic Web services (SWS) by removing the need for additional semantic descriptions.<br/><br/>The most actively researched approaches to Semantic Web services introduce explicit semantic descriptions of services that are in addition to the existing semantic descriptions of the service domains. This increases their complexity and design overhead. The need for semantically describing the services in such approaches stems from their foundations in service-oriented computing, i.e. the extension of already existing service descriptions. This thesis demonstrates that adopting a resource-oriented approach based on REST will, in contrast to service-oriented approaches, eliminate the need for explicit semantic service descriptions and service vocabularies. This reduces the development efforts while retaining the significant functional capabilities.<br/><br/>The approach proposed in this thesis, called EXPRESS (Expressing RESTful Semantic Services), utilises the similarities between REST and the Semantic Web, such as resource realisation, self-describing representations, and uniform interfaces. The semantics of a service is elicited from a resource’s semantic description in the domain ontology and the semantics of the uniform interface, hence eliminating the need for additional semantic descriptions. Moreover, stub-generation is a by-product of the mapping between entities in the domain ontology and resources.<br/><br/>EXPRESS was developed to test the feasibility of eliminating explicit service descriptions and service vocabularies or ontologies, to explore the restrictions placed on domain ontologies as a result, to investigate the impact on the semantic quality of the description, and explore the benefits and costs to developers. To achieve this, an online demonstrator that allows users to generate stubs has been developed. In addition, a matchmaking experiment was conducted to show that the descriptions of the services are comparable to OWL-S in terms of their ability to be discovered, while improving the efficiency of discovery. Finally, an expert review was undertaken which provided evidence of EXPRESS’s simplicity and practicality when developing SWS from scratch.
Areeb Alowisheq
http://jb4-2.eprints-hosting.org/2226
This thesis investigates an approach that simplifies the development of Semantic Web services (SWS) by removing the need for additional semantic descriptions.<br/><br/>The most actively researched approaches to Semantic Web services introduce explicit semantic descriptions of services that are in addition to the existing semantic descriptions of the service domains. This increases their complexity and design overhead. The need for semantically describing the services in such approaches stems from their foundations in service-oriented computing, i.e. the extension of already existing service descriptions. This thesis demonstrates that adopting a resource-oriented approach based on REST will, in contrast to service-oriented approaches, eliminate the need for explicit semantic service descriptions and service vocabularies. This reduces the development efforts while retaining the significant functional capabilities.<br/><br/>The approach proposed in this thesis, called EXPRESS (Expressing RESTful Semantic Services), utilises the similarities between REST and the Semantic Web, such as resource realisation, self-describing representations, and uniform interfaces. The semantics of a service is elicited from a resource’s semantic description in the domain ontology and the semantics of the uniform interface, hence eliminating the need for additional semantic descriptions. Moreover, stub-generation is a by-product of the mapping between entities in the domain ontology and resources.<br/><br/>EXPRESS was developed to test the feasibility of eliminating explicit service descriptions and service vocabularies or ontologies, to explore the restrictions placed on domain ontologies as a result, to investigate the impact on the semantic quality of the description, and explore the benefits and costs to developers. To achieve this, an online demonstrator that allows users to generate stubs has been developed. In addition, a matchmaking experiment was conducted to show that the descriptions of the services are comparable to OWL-S in terms of their ability to be discovered, while improving the efficiency of discovery. Finally, an expert review was undertaken which provided evidence of EXPRESS’s simplicity and practicality when developing SWS from scratch.
Areeb Alowisheq