The use of URIs and the URI pattern

The use of URI’s and the URI pattern: Finland Nordic URI Webinar 29. 5. 2019 Kai Koistinen National Land Survey of Finland

National URI recommendation • Public administration recommendation for spatial data URIs was accepted in September 2015 – Recommended URI structure – Process for implementing URIs – Examples on how to respond to URI requests (RDF based solution) – Life cycle rule principles – Use case examples – URIs in INSPIRE • http: //www. jhssuositukset. fi/web/guest/jhs/recommendations/193 – recommendation is available in Finnish, English and Swedish

Recommended URI pattern http: //{domain}/{type}/{dataset. Id}/{local. Id}[/{version. Id}] where: • domain = “paikkatiedot. fi” (“paikkatiedot” is “spatial data” in Finnish) – A centralized national URI redirection service maintained by NLSfi – Service has been implemented using CSIROs PID Service software: https: //www. seegrid. csiro. au/wiki/Siss/PIDService • type – “so” for spatial objects – “id” for real world objects • Inspire responsible organization creates “id” URIs for real world objects that are modelled as spatial objects in Inspire – “def” for concepts • concepts can be from any controlled vocabularies like thesauri, code lists, schemas etc. – “doc” documentation related to “so”, “id” or “def” • Includes different formats of the data (for example GML, JSON…) and references to other related data (real world objects, • spatial objects, concepts…) • the domain of a “doc” URI is decided by the data provider (paikkatiedot. fi is not used for as a domain for “doc” URIs) dataset. Id – the resource identifier that is mandatory for the Inspire datasets (can be given to non-Inspire datasets also) • we use a 7 digit integer – • • id register is maintained by NLSfi local. Id – a non limited string that is a local unique, persistent identifier for the object – data provider is responsible for the uniqueness and persistence of the local. Ids of his own datasets – Non-mandatory /{theme}/{class}/ parts can be included in the URI before local. Id for example for INSPIRE objects if needed version. Id – a max 25 digit string that is used to identify a version of a object – not mandatory

Linkings between real world objects, spatial objects and concepts A controlled spatial data vocabulary defines concepts: Standing waters: redirection http: //paikkatiedot. fi/def/234567/vesistot Lakes: redirection http: //paikkatiedot. fi/def/234567/jarvet Saimaa: redirection http: //paikkatiedot. fi/def/234567/saimaa http: //finto. fi/doc/234567/vesistot http: //finto. fi/doc/234567/jarvet http: //finto. fi/doc/234567/saimaa response • concept data in different formats (HTML, RDF etc. ) Modelled as a concept Real world object: Lake named saimaa http: //paikkatiedot. fi/id/123456/abc 123 The responsible organization for Inspire standing waters: Finnish environmental institute (SYKE) Other spatial data producer: City of Lappeenranta on cti ire red Modelled as a spatial object Inspire responsible organization creates a ”id” URI for the real world object and a ”so” for the spatial object: http: //paikkatiedot. fi/so/123456/abc 123 redirection City of Lappeenranta have their own spatial object for the real world lake Saimaa redirection http: //paikkatiedot. fi/so/345678/qwe 456 http: //www. syke. fi/doc/123456/abc 123 http: //www. lpr. fi/doc/345678/qwe 456 response • link to corresponding real world object • different formats of the spatial object (GML, JSON etc. ) • links to other relevant documentation like concepts and related spatial objects etc. • link to corresponding real world object • different formats of the spatial object(GML, JSON jne. ) • links to other relevant documentation like concepts and related spatial objects etc.

Implementation status • Paikkatiedot. fi redirection service is running and maintained by NLSfi – Redirections configured for a few datasets • Persistent http URIs have been implemented to some INSPIRE datasets – URI services missing from some datasets • NLSfi has piloted URI ”data cards” in many projects – First productional implementations will probably happen with WFS 3 • New national metadata recommendation guides to use http URI as resource identifier in metadata (dataset. Id) • Advanced life cycle management system developed in ”National Topographic Database” project • Real world object identifier (”id”) seems conceptually too complex to be implemented in first phase

7. 10. 2020 6