Embed Size (px)
Citation preview
I.T.
Joining up INSPIRE XML and Core Location RDF schemas to interconnect Belgian address data
INSPIRE 2013, Florence
25 June 2013
Andrea Perego
Michael Lutz
Nikolaos Loutas
Vassilios Peristeras
ISA undertakes initiatives to foster interoperability of information exchanges by public administrations across sectors and borders
Action 1.1 – Semantic Interoperability Action 1.17 – Reusable INSPIRE reference components (ARE3NA) Action 2.13 – EU Location Framework
2
I.T.
Core Vocabularies for eGovernment
1
1. Core Vocabularies for eGovernment 2. Core Location Vocabulary 3. Designing URI sets for location 4. Core Location Pilot
Core vocabularies
Simplified, re-usable, and extensible data models that capture the fundamental characteristics of a data entity in a context-neutral fashion.
CORE
VOCABULARY
PUBLICSERVICE
https://joinup.ec.europa.eu/node/43160 5
Why relevant?
1. 1. Interoperability of base registers: common vocabularies for interconnecting authentic sources of Government data
2. “Basic data” a Minimal Viable Product.
3. 2. Interoperability of public services: greatest common denominator to which one can add context-specific extensions.
6
• Recommendation 12. Public administrations, when working to establish European public services, should develop interfaces to authentic sources and align them at semantic and technical level.
European Interoperability Framework
http://ec.europa.eu/isa/documents/isa_annex_ii_eif_en.pdf 7
Denmark: “Good basic data for everyone”
http://www.digst.dk/ 8
I.T.
The Core Location Vocabulary
2
1. Core Vocabularies for eGovernment 2. Core Location Vocabulary 3. Designing URI sets for location 4. Core Location Pilot
Core Location Vocabulary
• A simplified, reusable and extensible data model that captures the fundamental characteristics of a location, represented as an address, a geographic name, or a geometry.
• Developed in the period December 2011 – May 2012 by a multi disciplinary Working Group
Core Location – Task Force
• co-chairs: Michael Lutz, Paul Smits, Andrea Perego (DG JRC)
• editor: Phil Archer (W3C)
• task force: Segun Alayande, Adam Arndt, Joseph Azzopardi, Chirsina Bapst, Serena Coetzee, Andreas Gehlert, Giorgios Georgiannakis, Anja Hopfstock, Andreas
• Illert, Michaela Elisa Jackson, Morten Lind, Matthias Lüttgert, Andras Micsik, Piotr Piotrowski, Greg Potterton, Peter Schmitz, Raj Singh, Athina Trakas, Rob Walker, Stuart Williams, Peter Winstanley, ...
3 representation formats
RDF schema
Re-uses existing Linked Data vocabularies
ISA Open Metadata Licence v1.1
Re-uses Core Components Technical Specification (CCTS).
XML schema
Conceptual model
Re-use existing concepts in CCL, INSPIRE, etc.
Maintained by W3C (Government Linked Data Working Group)
12
W3C Location and Address Community
• The W3C Location and Addresses Community Group is to review the existing efforts such as the Core Location Vocabulary and assess whether any use cases would be served by harmonization and/or new standardization work.
• It may produce specifications or use cases and requirements documents, which may be proposed for adoption by the W3C Government Linked Data (GLD) Working Group
INSPIRE data specifications
• Core Location can be seen as a subset of the INSPIRE
address specification as it based on the INSPIRE
AddressRepresentation class.
• INSPIRE XML versus Location RDF representation.
• The Location CV and INSPIRE are complementary
• A linked data service can be implemented on top of an INSPIRE representation.
Core Location Vocabulary data model
15
INSPIRE Data Specification on Addresses
16
I.T.
Designing URI sets for location
3
1. Core Vocabularies for eGovernment 2. Core Location Vocabulary 3. Designing URI sets for location 4. Core Location Pilot
UK – Designing URI Sets for Location
Spatial objects and corresponding information resources Spatial object:
http://{domain.name}/so/{theme}/{class}/{namespace}/{localId}
Digital resource: http://{domain.name}/doc/{theme}/{class}/{namespace}/{localId}
INSPIRE generic conceptual model
Annex H (informative) Implementation of Identifiers using URIs in INSPIRE
Use persistent HTTP URI to identify spatial things and spatial objects
Resolving the URIs redirects (HTTP 303) to a download service that provides digital resources describing the spatial object or thing, e.g. in GML, JSON, HTML, RDF, etc.
Benefits of URIs
• Enables the deployment of federated governance procedures
• Provides access to individual objects, while it remains possible to download whole datasets
• URI dereferencing and access to alternate formats (e.g. GML, RDF, JSON, CSV,...)
• Enables efficient management of shared data within and into business systems
I.T.
Core Location Pilot - Interconnecting Belgian address data
4
1. Core Vocabularies for eGovernment 2. Core Location Vocabulary 3. Designing URI sets for location 4. Core Location Pilot
24
Data fragmentation
Heterogeneous data formats
Lack of common identifiers
Unlinked Low quality
Non-interoperable
UrBIS - Brussels
Capital Region
CRAB - Flanders PICC - Wallonia Civil register NGI – National
Geographic Institute
DATA CONSUMER
?
Interconnecting Belgian address registers
Core Location Pilot: https://joinup.ec.europa.eu/node/63242
LOGD INFRASTRUCTURE
UrBIS - Brussels
Capital Region
CRAB - Flanders PICC - Wallonia Civil register NGI – National
Geographic Institute
DATA CONSUMER
sample address data in native format
Linked address data
Common Data models
RDF view
SPARQL endpoint
INS
PIR
E
lookup, disambiguate, link
25
• XML and RDF views on relational data served over a Web interface
XML view
Xquery,
Xpath
Combining XML, RDF, and Linked Data
relational database
SQL Processor
XML
Processor
Web Application
Server
Web Browser RDF Client
external database
HTTP
RDF Quad Store
OpenLink Virtuso
XML Client
SPARQL
engine
27
Subject Predicate Object
NGI_Road.NATIONALREGISTRATION-NUMBER - URI
rdf:type tnro:Road
locn:geographicName
STREETNAME GERMAN @de
locn:geometry TGID
We used OpenlinkSW “Virtuoso” RDF Views
and XML Views
Alternatives: - D2RQ -SquirrelRDF - Revelytix Spyder
28
Address Identifier
Address Notation
UC2: Look up (de-
reference) an address identifier
UC1: Disambiguate (reconcile) an address notation
UC3: Link datasets
by means of address identifiers
Example: Chaussée de Bruxelles 135 1310 La Hulpe
Example: http://location.testproject.eu/so/ad/AddressRepresentation/SPW/248565
Three use cases for data consumers
29
UC1: Disambiguate (query) address notations
•SPARQL query on the triple store
•The query is converted into SQL and hits the relational tables of several data providers
30
UC2: Resolve Web identifiers
31
UC3: Link address data
32
UC3: Link address data
33
Conclusions
• Core Location ánd INSPIRE AD can be used to harmonise address data from disparate systems
• Core Location can be easily extended with (still experimental) INSPIRE RDF vocabularies
• URI sets for INSPIRE spatial objects and spatial things can accommodate both the XML (GML) and RDF world
Join SEMIC group on LinkedIn
Follow @SEMICeu on Twitter
Join SEMIC community on Joinup
Project Officer: [email protected]
Contractor: [email protected]
Get involved Visit our initiatives
SOFTWARE
FORGESCOMMUNITY
ADMS.
SW
CORE
VOCABULARY
PUBLICSERVICE
34
