29.06.2013 Views

NUI Galway – UL Alliance First Annual ENGINEERING AND - ARAN ...

NUI Galway – UL Alliance First Annual ENGINEERING AND - ARAN ...

NUI Galway – UL Alliance First Annual ENGINEERING AND - ARAN ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Enabling Federation of Government Metadata Repositories<br />

Gofran Shukair 1 , Nikos Loutas 1 , Fadi Maali 1 , Vassilios Peristeras 2<br />

1 Digital Enterprise Research Institute, <strong>NUI</strong> <strong>Galway</strong><br />

(firstname.lastname)@deri.org<br />

2 EC, DG for Informatics, Interoperability Solutions for European Public Administrations<br />

Abstract<br />

Data models, taxonomies, ontologies, code lists and<br />

semantic data exchange formats are the key resources<br />

for creating interoperable data exchange. These<br />

resources exists in several national repositories that<br />

differ in scope and in target group they are addressing<br />

and they are implemented using different technologies<br />

and expose different user interfaces to the end user.<br />

However the semantic content they include can often be<br />

reused even bypass the domain they were originally<br />

designed for. Seamless data exchange has been the<br />

motivation to enable interoperability of these different<br />

repositories in order to reach a federation of<br />

repositories where users can search for resources or<br />

assets in all the available repositories using a unified<br />

user interface.<br />

1. Introduction<br />

Resources, such as data models and schemata,<br />

taxonomies, ontologies, code lists are the means for<br />

seamless data exchange. In the context of this work, we<br />

use the term asset to refer to these types of resources.<br />

When it comes to government data, assets exist in<br />

isolated national e-government metadata repositories<br />

that differ (i) in scope, (ii) in target group they are<br />

addressing, (iii) are implemented using different<br />

technologies and (iv) expose different user interfaces to<br />

the end user. The semantic content they include can<br />

often be reused even bypass the domain they were<br />

originally designed for. But the physical isolation of<br />

these repositories and the heterogeneity of the assets<br />

hamper the reusability of common concepts.<br />

Hence, this research aims to (a) define a common<br />

data model to describe the assets of national egovernment<br />

metadata repositories and (b) to develop a<br />

proof-of-concept prototype showcasing the added-value<br />

of federation through cross-repository asset discovery<br />

and retrieval using a single point of access.<br />

2. Common Model Development<br />

This section introduces the Asset Description<br />

Metadata Schema (ADMS) and discusses its<br />

implementation using linked data and Semantic Web<br />

technologies. Thus, ADMS is implemented as an RDF<br />

Schema vocabulary which includes the core elements<br />

and the attributes needed to model an asset. We reuse<br />

properties from existing linked data vocabularies (e.g.<br />

DCAT 1 , DCMI 2 ) in the definition of an asset (Figure 1).<br />

1 F. Maali, R. Cyganiak, V. Peristeras. Enabling interoperability of<br />

government data catalogues. In Electronic Government, LNCS, 2010.<br />

2 http://dublincore.org/<br />

113<br />

An asset is a container dedicated to group artefact<br />

types that enable cross-repository interoperability and<br />

seamless data exchange. It is defined as a subclass<br />

dcat:Dataset with additional properties like dc:publisher<br />

and dc:spatial. The property adms:release is used for<br />

differentiating between the versions of each asset and<br />

the asset itself, Each asset will be related to its latest<br />

release using the property adms:release. Each release<br />

will be related to its previous one using. dc:hasVersion.<br />

Figure 1. ADMS Model in RDF<br />

3. Proof of concept Architecture<br />

Figure 2 shows the proposed architecture where<br />

assets from different national e-government metadata<br />

repositories can be queried and retrieved through a<br />

single point of access (SPARQL endpoint). Valueadded<br />

services, such as data mashups and faceted<br />

browsers, and third party applications can be built on<br />

top of this architecture. ADMS defines the<br />

administrative and descriptive metadata of the assets<br />

housed in the repositories. These assets can then<br />

queried and retrieved using querying API. Repositories<br />

can be connected to the federation and publish their<br />

assets’ metadata using the Publishing API and services.<br />

Figure 2. Proof of Concept prototype<br />

Acknowledgments. This work is a joint effort between<br />

]init[, EC ISA, <strong>NUI</strong> <strong>Galway</strong> and the University of<br />

Macedonia. It is funded in part by Science Foundation<br />

Ireland under Grant No. SFI/08/CE/I1380 (Lion-2).

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

Saved successfully!

Ooh no, something went wrong!