http://www.cnr.it/ontology/cnr/individuo/prodotto/ID115325

RESTful Implementation of Geospatial Services (Comunicazione a convegno)

Type

Comunicazione a convegno (Classe)
Prodotto della ricerca (Classe)

Label

RESTful Implementation of Geospatial Services (Comunicazione a convegno) (literal)

Anno

2008-01-01T00:00:00+01:00 (literal)

Alternative label

Mazzetti, P.; Nativi, S. (2008)
RESTful Implementation of Geospatial Services
in European Geosciences Union general meeting, 2008, Wien (Austria), 13 - 18 April 2008
(literal)

Http://www.cnr.it/ontology/cnr/pubblicazioni.owl#autori

Mazzetti, P.; Nativi, S. (literal)

Pagina inizio

05160 (literal)

Http://www.cnr.it/ontology/cnr/pubblicazioni.owl#url

http://www.cosis.net/abstracts/EGU2008/05160/EGU2008-A-05160-1.pdf (literal)

Http://www.cnr.it/ontology/cnr/pubblicazioni.owl#titoloVolume

5th EGU General Assembly (literal)

Http://www.cnr.it/ontology/cnr/pubblicazioni.owl#volumeInCollana

10 (literal)

Rivista

Geophysical research abstracts (Rivista)

Http://www.cnr.it/ontology/cnr/pubblicazioni.owl#pagineTotali

2 (literal)

Note

Google Scholar (literal)

Http://www.cnr.it/ontology/cnr/pubblicazioni.owl#affiliazioni

CNR (literal)

Titolo

RESTful Implementation of Geospatial Services (literal)

Http://www.cnr.it/ontology/cnr/pubblicazioni.owl#curatoriVolume

EGU (literal)

Abstract

In the last years REST (Representational State Transfer) has emerged as an alternative to existing approaches for Web applications development. Indeed, its characteristics of scalability and simplicity make it appealing for building complex Web services systems. Anyway an investigation is required to verify if and how it can be applied to specific domains. We analyzed the case of Geospatial services also building a prototype of a RESTful OGC WCS implementation. The WCSplus community discussions were considered as a starting point for our work. REST is an architectural style for distributed systems defined to describe the Web architecture and to guide its future evolution. It allows to describe a set of ResourceOriented architectures which share six constraints: client-server and stateless interaction, uniform interface, caching and code-on-demand (optional) support, multi-layer distribution. The fundamental characteristics of REST is the uniform interface which is defined by four interface constraints: identification of resources; manipulation of resources through representations; self-descriptive messages; and, hypermedia as the engine of application state. It is a generic (not resource-specific) interface, in the sense that it allows to perform the same set of actions on all the resources. Thus it exposes very basic operations for retrieving and sending representations of resources. Different application-level protocols can be used, but the most common implementation makes use of HTTP with GET/POST/PUT/DELETE verbs detailing the four basic operations mapping the CRUD (Create, Retrieve, Update, Delete) pattern. Since representations are generally encoded in XML, REST applications looks much like the traditional Web applications, usually referred to as POX-HTTP (Plain-Old-XML over HTTP), which implements Web Services using HTTP-GET and HTTP-POST operations. The uni- (literal)

Editore