1. I.T. Core Location Vocabulary into practice Harmonised access to base address registries 2 April 2013 Stijn Goedertier

2. I.T. The European context and the need for Core Vocabularies 1

3. The ISA Programme undertakes a number of initiatives to promote interoperability

4. Political context European Interoperability Framework

5. 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

6. Core vocabularies Simplified, reusable, and extensible data models that capture the fundamental characteristics of a data entity in a context-neutral fashion. https://joinup.ec.europa.eu/node/43160

7. I.T. The Core Location Vocabulary 2

8. 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 GroupWorking Group

9. Core Location Vocabulary 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,...

10. Core Location Vocabulary RDF Schema Re-uses existing Linked Data vocabularies, notably Dublin Core and FOAF Builds on Universal Business Language, Re-uses information elements provided by Core Components Technical Specification (CCTS) of UN/CEFACT All specifications are released under the “ISA Open Metadata Licence v1.1” https://joinup.ec.europa.eu/category/licence/isa-open-metadata- licence-v11 Licence ? XML Schema

11. 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.W3C Location and Addresses Community Group It may produce specifications or use cases and requirements documents, which may be proposed for adoption by the W3C Government Linked Data (GLD) Working GroupW3C Government Linked Data

12. 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 address specification 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.

13. Core Location Vocabulary data model 13

14. INSPIRE Address Specification 14

15. I.T. Core Location Pilot - Interconnecting Belgian address data 3

16. 16 Today address data is fragmented across various registers 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 ?

17. 17 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 Repository SPARQL endpoint Address Identifier Address Notation Link Look up Disambiguate DATA CONSUMER ORIENTED USE CASES INSPIRE lookup, disambiguate, link The pilot demonstrates feasibility of Linked Data

18. 18 Address Identifier Address Notation Look up (de- reference) an address identifier Disambiguate (reconcile) an address notation Link datasets by means of address identifiers Example: Maria-Theresiastraat 1 1000 Brussel Example: http://data.gov.be/so/ad/ Address/00BR/9346-237 (fictitious) Three use cases for data consumers

19. 19 Prevent fragmentation of address data

20. 20 Technical architecture relational database SQL Processor SPARQL Processor Web Application Server Web BrowserRDF Client external database HTTP RDF Quad Store OpenLink Virtuso

21. 21 The pilot demonstrates that

22. Get involved Join the SEMIC community on JoinupSEMIC Visit our initiatives Semantic interoperability Vassilios.PERISTERAS@ec.europa.eu Joao.Frade@pwc.be Stijn.Goedertier@pwc.be Nikos.Loutas@pwc.be Programme Manager Team http://joinup.ec.europa.eu/