Keep it simple! - a Nordic view on technical simplification issues 2018-11-16 Keep it simple! - a Nordic view on technical simplification issues
The INSPIRE data models 2018-11-16 The INSPIRE data models
2018-11-16 Unfolded
2018-11-16 …or as a flat tables…
2018-11-16 Flat vs. complex model
From a user perspective 2018-11-16 From a user perspective
2018-11-16 Voidables
Voidables 2018-11-16 http://data.gov.se/geodata/so/havsomraden/ 123e4567-e89b-12d3-a456-426655440000 http://data.gov.se/geodata/so/havsomraden/ unknown costalZoneManagementArea water
2018-11-16 Joins
Flattening of complex attributes 2018-11-16 Flattening of complex attributes An area got a name! 123e4567-e89b-12d3-a456-426655440000 http://data.gov.se/geodata/so/adress/ unknown costalZoneManagementArea water
2018-11-16 Geographical names
2018-11-16 Geographical names Name attributes
Geographical names Name attributes 2018-11-16 The combination of complex data types and voidables create this situation. Two rasters put on top of each other.
2018-11-16 Nordic viewpoints We acknowledge the complex data models as conceptual data models but propose that these should only be recommended encoding rules. i.e. flat data models are also valid for INSPIRE harmonisation. The content will be the same. We propose that voidable attributes are left out if they are not available. In the data models they should be considered “desirable” attributes. A modern software should be able to handle the merge of different attribute tables. We propose that the usage of complex data types, included from other application schemas (INSPIRE or ISO), are made simpler and that recommendations are made on alternative ways on how to fill the voidable elements of, for instance the data type GeographicalName.
A good example on simplification 2018-11-16 A good example on simplification Fit for purpose Prospecting areas for mining at the sea – from the The Danish Agency for Water and Nature Management The data is identified as in scope of INSPIRE AM Fit for purpose
After transformation Assumptions made: 2018-11-16 After transformation Assumptions made: attributes marked “voidable” are left out multiplicity changed from 1..* to exact 1 inheritances and data types are flattened