Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

2013 06-25 goedertier-inspire-2013


Published on

Published in: Education, Technology
  • The pilot's Linked Data interface can be accessed here:

    The report is available here:

    For all administrative units, INSPIRE XML (GML) and RDF data can be obtained:
    Are you sure you want to  Yes  No
    Your message goes here
  • Be the first to like this

2013 06-25 goedertier-inspire-2013

  1. 1. I.T.Joining up INSPIRE XML and CoreLocation RDF schemas to interconnectBelgian address dataINSPIRE 2013, Florence25 June 2013Stijn.Goedertier@pwc.beAndrea PeregoMichael LutzNikolaos LoutasVassilios Peristeras
  2. 2. ISA undertakes initiativesto foster interoperability ofinformation exchanges bypublic administrationsacross sectors and bordersAction 1.1 – Semantic InteroperabilityAction 1.17 – Reusable INSPIRE referencecomponents (ARE3NA)Action 2.13 – EU Location Framework2
  3. 3. I.T.Core Vocabularies foreGovernment11. Core Vocabularies for eGovernment2. Core Location Vocabulary3. Designing URI sets for location4. Core Location Pilot
  4. 4. Core vocabulariesSimplified, re-usable, andextensible data models thatcapture the fundamentalcharacteristics of a data entityin a context-neutral fashion.COREVOCABULARYPUBLICSERVICE
  5. 5. Why relevant?1. 1. Interoperability of base registers:common vocabularies for interconnectingauthentic sources of Government data2. “Basic data” a Minimal Viable Product.3. 2. Interoperability of public services:greatest common denominator to which one canadd context-specific extensions.6
  6. 6. • Recommendation 12. Publicadministrations, when working toestablish European publicservices, should developinterfaces to authentic sourcesand align them at semantic andtechnical level.European Interoperability Framework
  7. 7. Denmark: “Good basic data foreveryone”
  8. 8. I.T.The Core Location Vocabulary21. Core Vocabularies for eGovernment2. Core Location Vocabulary3. Designing URI sets for location4. Core Location Pilot
  9. 9. Core Location Vocabulary• A simplified, reusable and extensible data modelthat captures the fundamental characteristics of alocation, represented as an address, a geographicname, or a geometry.• Developed in the period December 2011 – May2012 by a multi disciplinary Working Group
  10. 10. Core Location – Task Force• co-chairs: Michael Lutz, Paul Smits, Andrea Perego (DGJRC)• editor: Phil Archer (W3C)• task force: Segun Alayande, Adam Arndt, JosephAzzopardi, Chirsina Bapst, Serena Coetzee, AndreasGehlert, Giorgios Georgiannakis, Anja Hopfstock, Andreas• Illert, Michaela Elisa Jackson, Morten Lind,Matthias Lüttgert, Andras Micsik, Piotr Piotrowski, GregPotterton, Peter Schmitz, Raj Singh, Athina Trakas, RobWalker, Stuart Williams, Peter Winstanley, ...
  11. 11. 3 representation formatsRDFschemaRe-usesexistingLinked DatavocabulariesISA Open Metadata Licence v1.1Re-uses CoreComponentsTechnicalSpecification(CCTS).XMLschemaConceptualmodelRe-useexistingconcepts inCCL, INSPIRE,etc.Maintained by W3C (Government Linked Data Working Group)12
  12. 12. W3C Location and Address Community• The W3C Location and Addresses CommunityGroup is to review the existing efforts such as theCore Location Vocabulary and assess whetherany use cases would be served by harmonizationand/or new standardization work.• It may produce specifications or use cases andrequirements documents, which may be proposedfor adoption by the W3C Government Linked Data(GLD) Working Group
  13. 13. INSPIRE data specifications• Core Location can be seen as a subset of the INSPIREaddress specification as it based on the INSPIREAddressRepresentation class.• INSPIRE XML versus Location RDFrepresentation.• The Location CV and INSPIRE are complementary• A linked data service can be implemented on topof an INSPIRE representation.
  14. 14. Core Location Vocabulary data model15
  15. 15. INSPIRE Data Specification onAddresses16
  16. 16. I.T.Designing URI sets forlocation31. Core Vocabularies for eGovernment2. Core Location Vocabulary3. Designing URI sets for location4. Core Location Pilot
  17. 17. UK – Designing URI Sets forLocationSpatial objects and corresponding information resourcesSpatial object:http://{}/so/{theme}/{class}/{namespace}/{localId}Digital resource:http://{}/doc/{theme}/{class}/{namespace}/{localId}
  18. 18. INSPIRE generic conceptualmodelAnnex H (informative) Implementation ofIdentifiers using URIs in INSPIREUse persistent HTTP URI to identify spatial things andspatial objectsResolving the URIs redirects (HTTP 303) to a downloadservice that provides digital resources describing thespatial object or thing, e.g. in GML, JSON, HTML, RDF,etc.
  19. 19. Benefits of URIs• Enables the deployment of federatedgovernance procedures• Provides access to individual objects, while itremains possible to download whole datasets• URI dereferencing and access to alternateformats (e.g. GML, RDF, JSON, CSV,...)• Enables efficient management of shared datawithin and into business systems
  20. 20. I.T.Core Location Pilot -Interconnecting Belgianaddress data41. Core Vocabularies for eGovernment2. Core Location Vocabulary3. Designing URI sets for location4. Core Location Pilot
  21. 21. 24Data fragmentationHeterogeneous data formatsLack of common identifiersUnlinkedLow qualityNon-interoperableUrBIS - BrusselsCapital RegionCRAB - Flanders PICC - Wallonia Civil registerNGI – NationalGeographic InstituteDATA CONSUMER?
  22. 22. Interconnecting Belgianaddress registersCore Location Pilot: INFRASTRUCTUREUrBIS - BrusselsCapital RegionCRAB - Flanders PICC - Wallonia Civil registerNGI – NationalGeographic InstituteDATA CONSUMERsample address data in native formatLinked address dataCommon Data modelsRDF viewSPARQL endpointINSPIRElookup, disambiguate, link25• XML and RDFviews onrelational dataserved over aWeb interfaceXML viewXquery,Xpath
  23. 23. Combining XML, RDF, and LinkedDatarelationaldatabaseSQL ProcessorXMLProcessorWeb ApplicationServerWeb BrowserRDF ClientexternaldatabaseHTTPRDF QuadStoreOpenLink VirtusoXML ClientSPARQLengine
  24. 24. 27Subject Predicate ObjectNGI_Road.NATIONALREGISTRATION-NUMBER - URIrdf:type tnro:Roadlocn:geographicNameSTREETNAMEGERMAN@delocn:geometry TGIDWe used OpenlinkSW“Virtuoso” RDF Viewsand XML ViewsAlternatives:- D2RQ-SquirrelRDF- Revelytix Spyder
  25. 25. 28AddressIdentifierAddressNotationUC2: Look up (de-reference) anaddress identifierUC1: Disambiguate(reconcile) anaddress notationUC3: Link datasetsby means ofaddress identifiersExample:Chaussée de Bruxelles 1351310 La HulpeExample: use cases for data consumers
  26. 26. 29UC1: Disambiguate (query) addressnotations•SPARQL query onthe triple store•The query isconverted into SQLand hits therelational tables ofseveral dataproviders
  27. 27. 30UC2: Resolve Web identifiers
  28. 28. 31UC3: Link address data
  29. 29. 32UC3: Link address data
  30. 30. 33Conclusions• Core Location ánd INSPIRE AD can be used toharmonise address data from disparate systems• Core Location can be easily extended with (stillexperimental) INSPIRE RDF vocabularies• URI sets for INSPIRE spatial objects and spatialthings can accommodate both the XML (GML)and RDF world
  31. 31. Join SEMIC group on LinkedInFollow @SEMICeu on TwitterJoin SEMIC community on JoinupProject Officer:Vassilios.Peristeras@ec.europa.euContractor: Stijn.Goedertier@pwc.beGet involvedVisit our initiativesSOFTWAREFORGESCOMMUNITYADMS.SWCOREVOCABULARYPUBLICSERVICE34