11.01.2013 Views

Global Drought Monitoring Service through the GEOSS Architecture ...

Global Drought Monitoring Service through the GEOSS Architecture ...

Global Drought Monitoring Service through the GEOSS Architecture ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Architectural Implementation Pilot, Phase 3 Version: 2.0<br />

<strong>Global</strong> <strong>Drought</strong> <strong>Monitoring</strong> and European <strong>Drought</strong><br />

Observatory-Water SBA Engineering Report<br />

Date: 11/Feb/2011<br />

different components, making <strong>the</strong> architecture flexible and scalable. Moreover, it does not affect<br />

existing geospatial service interfaces implementing a loosely-coupled solution in compliance<br />

with <strong>the</strong> <strong>GEOSS</strong> architectural principles.<br />

The system design for <strong>the</strong> DAC applies <strong>the</strong> well-known principle of Layered <strong>Architecture</strong><br />

(ISO, 1994), as depicted in Figure 11. Functionalities are grouped and layered according to <strong>the</strong>ir<br />

abstraction level. Figure 11 shows <strong>the</strong> three layers of <strong>the</strong> proposed architecture, implementing<br />

each layer on a different distribution tier:<br />

• in <strong>the</strong> Presentation Layer we find components implementing graphic user interfaces<br />

(GUIs);<br />

• <strong>the</strong> Integrated Semantic Layer is composed of components which implement <strong>the</strong> business<br />

logic necessary to integrate semantic and geospatial services;<br />

• The Single Semantic and Geospatial Query Layer provides query functionalities towards<br />

a set of different services (geospatial, semantic, etc.).<br />

Figure 17 – System <strong>Architecture</strong> for <strong>the</strong> DAC System<br />

The DAC clearly falls into <strong>the</strong> integrated semantic layer and makes use of <strong>the</strong> services in<br />

<strong>the</strong> single semantic and query layer in order to implement <strong>the</strong> query expansion strategy.<br />

The choice of service interfaces was mainly driven by <strong>the</strong> need of being as compliant as<br />

possible with widely adopted catalog service specifications to be interoperable with existing<br />

systems. Thus, for <strong>the</strong> interaction between <strong>the</strong> DAC and <strong>the</strong> catalog service, <strong>the</strong> OGC CSW/ISO<br />

AP (Application Profile) interface is used. Among <strong>the</strong> present application profiles of <strong>the</strong> OGC<br />

CSW core specification; this is presently one of <strong>the</strong> most widely implemented. Moreover, this is<br />

<strong>the</strong> INSPIRE compliant catalog service interface. The access to <strong>the</strong> semantic service takes place<br />

<strong>through</strong> SPARQL (<strong>the</strong> Query Language for Resource Description Format (RDF) semantic<br />

Page 57

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!