Finnish Approach to Linked Data & Semantics

The Finnish approach to Linked Data and semantics focuses on URI design, ontology, and PID management for INSPIRE data. This initiative aims to streamline data search and product generation, enhancing spatial data management nationally. Through ontologies like PTO/SDO and Finto, Finland is developing a robust infrastructure for spatial data discovery and utilization. The integration of semantic annotations in OGC standards and spatially enabled data search demonstrates the practical implementation of this approach.

• Finnish
• Linked Data
• Semantics
• Ontology
• INSPIRE

gu_tel Follow

Uploaded on Feb 22, 2025 | 0 Views

Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

Presentation Transcript

1. Case Finland: URI design for Inspire with ontology approach Are3na PIDService webinar May 5th 2014 Esa Tiainen, Kai Koistinen NLS Finland 05052014

2. Contents Introduction of the Finnish approach Current status of work on PIDs Challenges for PID set-up and management Next steps

3. Introduction of the approach The initial goal was envisioned to successfully search data instances by concepts E.g. harmonised concepts in INSPIRE data specifications and beyond (controlled vocabularies) This would enable e.g. generating re-usable INSPIRE data products required by national law (instead of establishing numerous data products with several data providers updating many of them in parallel) To implement a framework for Linked Data; which is to address the INSPIRE requirement to fit I INSPIRE IDs to the national framework of identifiers . Conclusion: An ontology approach was a precondition Started with URI design for concepts We want to manage not only PIDs but semantics as well Further conclusion: URI management applicable as national solution Initialization of national recommendations to public administration on unique identifiers (HTTP URI) for spatial data

4. Related Ontologies Finnish spatial data ontology (PTO/SDO) 1. Application ontology generated from correspondent concepts of the INSPIRE schema; theme, spatial object types and attributes 2. A thesaurus of keywords in the national spatial data metadata The Finnish national ontology Finto (SKOS) Finnish Ontology and Thesaurus Service, www.finto.fi Based on the generic national thesaurus Further vision To enable the discovery of INSPIRE, as well as other spatial data, through the national ontology service besides national Geoportal and INSPIRE services Realization of full potential of INSPIRE and spatial data at large Operational Linked Data infrastructure

5. Semantic annotations in OGC standards, Best practise doc (2012) Fig 3 Reflected to Finnish national and spatial data Ontology (PTO) Application ontology corresponds i.e. to an ontology generated from a data product specification according to an INSPIRE data specification In practice, Domain ontology is the Finnish spatial data ontology (PTO) embedded in the national Finto-ontology SKOS (Finnish Ontology and Thesaurus Service, www.finto.fi)

6. Spatially enabled semantic data search In the following slide, Fig. 1, a detailed search method is presented If the performance of the automated search process presented is feasible, a spatially conscious semantic search is possible linking spatial data schemas and search terms with ontology and metadata through URIs and RDF The search is more simple with direct pre-annotation of controlled vocabulary concepts to the data object instances and using the same method but preprocessed to connect URI concepts to the (spatial) data instances Pre-processing may be feasiblle for faster performance or usability issues

7. Fig 1: Data entity discovery and retrieval annotations on metadata and schema level Cataloque service User (evacuation plan for a water polluting emission) Location based search application Data sources providing service interfaces Discovery service Ontology service Aika schemas) Task to warn /report bodies responsible of swimming places and harbours T1 Spatial Data Ontology SDO Data Product Schemas - Inspire-schemas - other schemas Service and dataset metadata Query results re search terms: Search terms Hydrology protection and emission with location description / boundaries T2 Hydrologiscal observations and sites Hydrology protection Dataset: Service: Spatial objects: Emission REST/SPARQL CSW REST/SPARQL Metadata entities referred to concept URI:s (RDF) T3 Schema entities referred to concept URI:s (RDF) Water resource areas T4 WFS-service provides the data by the schema W M S Dataset : Dataset : Service: Spatial objects T5 Retrieval of concepts for terms Hydrology protection and emission using SDO Provides URI:s of concepts related to search terms Hydrology protection and emission Ground water Dataset : Ground water areas Service : Spatial objcts: W F S Retrieval of metadata from Discovery service and schemas with object classes from Cataloque service using concept URI:s Provides datasets and services related to Hydrology protection and emission and with data within the location requested Provides schemas and their object classes related to hydrology protection and emission Swimming water Service : Spatial objcts: Dataset : Spatial objects : Harbours Dataset : Service : Swimming places Service : Kohteet: Spatial objects: Retrieval of spatial data instances related to Hydrology protection and emission within requested location area through the service interfaces Etc. Spatial data instances related to Hydrology protection and emission Harbours Etc.

8. Current stage Preparing national recommendation to public administration on unique identifiers (HTTP URI) for spatial data Use cases Re-use of data employing URIs Open data delivery and applications Semantic data discovery and linking (supported by ontology or schema service; INSPIRE schemas) Data update or synchronization with URIs Document linking Representation of download service interfaces (as standard URI responses) Piloting Proof of concept CSIRO PIDService as a resolution service Redirections: paikkatiedot.fi -pilot URL: http://paikkatiedot.fi/pidsvc/index2.html Pre-pilot URI-service: http://inspire-hy.fgi.fi/index_en.html Re-use of INSPIRE data NZ - Natural Risk Zones as minature of INSPIRE infrastructure Data discovery through ontology/catalogue service Re-use of INSPIRE and non-INSPIRE data

9. URI-pattern A. Generic for spatial data -/so/ 1) http://paikkatiedot.fi/so/{namespace}/{localId}[/{versionId}] centralized and common URI management and service, or 2) http://{register}.fi/so/{namespace}/{localId}[/{versionId}] - URI-service by the individual data provider {namespace} = data source, i.e. dataset identifier in national spatial data metadata {register} = URI management body i.e Helsinki for municipality or authority B. Specification for inspire data: http://{paikkatiedot}.fi/so/{namespace}/[{theme}/{class}/]{localId}[/{versionId} C. Linking URI-components /so/ for spatial objects /id/ for real world objects mandatory linked to /so/, or both ways as necessary for application use /doc/ for documents etc

10. Challenges for PID set-up and management (1) Issues on identification and INSPIRE ID Both the INSPIRE spatial object entity (instance) and the original spatial object (source object) correspondent to the INSPIRE instance have URIs of their own: The URI path of the INSPIRE instance has parts: /{ theme}/, /{class}/, but the spatial source object URI is opaque. Note that one or several INSPIRE spatial objects, e.g. in different INSPIRE themes, may be subsets of a single spatial source object. The URI of the spatial source object (instance) and the one of the INSPIRE /so/-instance(s) refer to the same and single /id/. The organization responsible of the source object shall create the /id/-URI. If the INSPIRE instance is created before the /id/-URI of the source object then it shall be created by the organization responsible of the INSPIRE spatial object and /so/-URI. Practically always the organization responsible of the spatial source object is responsible of the INSPIRE spatial object (this is the case in Finland).

11. Challenges for PID set-up and management (2) Consistent rules at the EU level At the EU level, we would expect that there would come a technical guidance or high-level recommendations to establish cornerstones for pan-European interoperability on issues such as standard URI response patterns (minimum for cross-border use) re-use or configuration of register services such as INSPIRE schemas or codelists etc. for reasoning in order to manage semantics standard representation of life-cycle rules (minimum for cross-border use) further definition/specification of operational roles of /so/- and /id/- components in URI-linking and response patterns linking method between /so/- and /id/ - one-way or both ways, which is our conclusion. representation of real-world object; whether /id/-component is feasible for that as common practice, similarly to ISA recommendation

12. Next steps To start shortly Generating reusable INSPIRE data products (required by nat. Law) Linking to generic national ontology service Completion of national recommendation on UIDs For INSPIRE implementation: March 2015 Expecting for INSPIRE MIG guidelines For final approval by the end of 2015 In the future Data discovery and retrieval Through national geo-portal Through spatial data services Extension of national thesaurus and ontology service Finto to spatial data discovery and retrieval

13. Thank you for attention Esa Tiainen Kai Koistinen esa.tiainen@nls.fi kai.koistinen@nls.fi

14. Further information Next slides with more details on the applied approach of OGC Best practise document (2012) The three different levels of semantic annotations Spatially enabled semantic data search

15. Management of Semantics using ontology Based on OGC:n best practise -document Semantic annotations in OGC standards (2012) The three different levels of (semantic) annotations possible for OGC Web Services 1. Metadata level ISO-metadata on dataset ISO-metadata on services OWS GetCapabilities Schema level metadata XML-schema in catalogue service (registry service) WFS DescribeFeatureType Entity level metadata GML-data 2. 3.

16. Technical realization of the individual levels On metadata level (1) a keyword in metadata or ontologized Inspire concept (theme or class - object type) is linked to the correspondent concept in spatial data ontology (PTO) On schema level (2) spatial object types and attributes of (Inspire) schema can be linked to an application ontology generated from correspondent concepts of the schema. This application ontology is further linked to the spatial data ontology (PTO) On entity level (3) the individual can be either annotated with domain concepts or with individuals of domain concepts

17. Granularity of spatial search The overall method comprises different levels of granularity Dataset discovery and retrieval annotations on metadata level Data entity discovery and retrieval annotations on schema level Data entity discovery and retrieval automated annotation process linking metadata and schema level (Fig. 1, most detailed) Data entity discovery and retrieval annotations on data entities (straightforward by pre-processing) (Four last slides show identification of different levels in FI, as a hint)

18. Principal steps in managing semantics 1. Data product schemas are annotated to all ontology or controlled vocabulary/thesaurus concepts that they imply, e.g. Inspire themes and (spatial) data object classes Use schemas, metadata, RDF, SKOS 2. Connect search terms to concepts of controlled vocabulary or ontology Use SPARQL, RDF

22. Dataset discovery and retrieval annotations on metadata level K ytt j (myrkkyp st n liittyv evakuointisuunnitelmaa tekev pelastuslaitoksen operaatiovastaava) Paikkatietokohteiden hakuun suunniteltu karttapohjainen sovellus Hakupalvelu Ontologiapalvelu Paikkatiedon tuottajat Aika Tarve myrkkyp st n raportoinnille mm. uimapaikkojen ja satamien vastuutahoille T1 Haku k site- ja spatiaalista rajausta k ytt en Aineistojen ja palvelujen metatiedot T2 Paikkatieto -ontologia Haetaan k sitteit paikkatieto-ontologiasta T3 T4 T5 Haetaan hakupalvelusta aineistojen ja palvelujen metatiedot, joiden annotoinnissa on k ytetty l ytyneit k sitteit ja jotka sis lt v t tietoa k ytt j n m rittelem lt alueelta uimapaikat Uimapaikat: Aineisto uimapaikat, saatavilla palvelun B kautta Satamat: Aineisto satamat, saatavilla palvelun C kautta satamat

23. Data entity discovery and retrieval annotations on schema level K ytt j (myrkkyp st n liittyv evakuointisuunnitelmaa tekev pelastuslaitoksen operaatiovastaava) Paikkatietokohteiden hakuun suunniteltu karttapohjainen sovellus Luettelopalvelu Ontologiapalvelu Paikkatiedon tuottajat Aika Tarve myrkkyp st n raportoinnille mm. uimapaikkojen ja satamien vastuutahoille T1 Haku k site- ja spatiaalista rajausta k ytt en Paikkati eto- ontologi a Tietotuoteskeemat - Inspire-skeemat - muut T2 Haetaan k sitteit paikkatieto-ontologiasta T3 T4 uimapaikat T5 Haetaan luettelopalvelusta kohdetyyppej ja attribuutteja, joiden annotoinnissa on k ytetty l ytyneit k sitteit satamat Haetaan infran palveluista l ytyneiden kohdetyyppien mukaisia tietokohteita k ytt j n rajaamalta alueelta Uimapaikat: Kohdetyyppi: bathingWater Kohteet: http://paikkatiedot.fi /so/uimapaikat/1234 Satamat: Kohdetyyppi: harbour Kohteet: http://paikkatiedot.fi /so/satamat/1234

24. Data entity discovery and retrieval annotations on metadata and schema level K ytt j (myrkkyp st n liittyv evakuointisuunnitelmaa tekev pelastuslaitoksen operaatiovastaava) Paikkatietokohteiden hakuun suunniteltu karttapohjainen sovellus Luettelopalvelu Ontologiapalvelu Paikkatiedon tuottajat Aika Tarve myrkkyp st n raportoinnille mm. uimapaikkojen ja satamien vastuutahoille Haku k site- ja spatiaalista rajausta k ytt en T1 Paikkati eto- ontologi a Tietotuoteskeemat - Inspire-skeemat - muut Aineistojen ja palvelujen metatiedot Haetaan k sitteit paikkatieto-ontologiasta T2 Haetaan hakupalvelusta aineistojen ja palvelujen metatiedot, joiden annotoinnissa on k ytetty l ytyneit k sitteit ja jotka sis lt v t tietoa k ytt j n m rittelem lt alueelta T3 T4 T5 uimapaikat Haetaan luettelopalvelusta kohdetyyppej ja attribuutteja, joiden annotoinnissa on k ytetty l ytyneit k sitteit Uimapaikat: Aineisto uimapaikat, saatavilla palvelun B kautta Kohdetyyppi: bathingWater Kohteet: http://paikkatiedot.fi /so/uimapaikat/1234 Satamat: Aineisto satamat, saatavilla palvelun C kautta Kohdetyyppi: harbour Kohteet: http://paikkatiedot.fi /so/satamat/1234 satamat Haetaan hakupalvelun kautta l ytyneist palveluista l ytyneiden kohdetyyppien mukaisia tietokohteita k ytt j n rajaamalta alueelta

25. Data entity discovery and retrieval annotations on data entities K ytt j (myrkkyp st n liittyv evakuointisuunnitelmaa tekev pelastuslaitoksen operaatiovastaava) Paikkatietokohteiden hakuun suunniteltu karttapohjainen sovellus Ontologiapalvelu Paikkatiedon tuottajat Aika Tarve myrkkyp st n raportoinnille mm. uimapaikkojen ja satamien vastuutahoille T1 Haku k site- ja spatiaalista rajausta k ytt en Paikkati eto- ontologi a T2 Haetaan k sitteit paikkatieto-ontologiasta T3 uimapaikat T4 T5 Haetaan l ytyneill k sitteill annotoituja tietokohteita infran palveluista satamat Uimapaikat: Kohteet: http://paikkatiedot.fi /so/uimapaikat/1234 Satamat: Kohteet: http://paikkatiedot.fi /so/satamat/1234