6.4.24 Extensions by countries or communities
From Geostandards
6 INSPIRE
6.1 Background and Motivation
- 6.1.1 Spatial Data Infrastructures
- 6.1.2 Requirements for a European SDI
- 6.1.3 Existing foundation for a European SDI
- 6.2.1 Background and history
- 6.2.2 The five components of the Directive
- 6.2.3 Implementation, status and schedule
- 6.2.4 Groups and responsibilities within INSPIRE
- 6.2.5 INSPIRE Implementing Rules and INSPIRE Guidance Documents
- 6.2.6 European and Global initiatives in the context of INSPIRE
6.3 Technical Architecture Overview
- 6.3.1 Relationship between the different components, in particular spatial data, metadata, registers, and network services
- 6.3.2 Terminology
6.4 Interoperabilty of spatial data sets / INSPIRE data specifications
- 6.4.1 Requirements of the INSPIRE Directive
- 6.4.2 Interoperability of spatial data
- 6.4.3 INSPIRE data scope
- 6.4.4 Modelling Framework
- 6.4.5 Generic Conceptual Model
- 6.4.6 ISO 19100 series of International Standards
- 6.4.7 Rules for application schemas and feature catalogues
- 6.4.8 Identifier Management
- 6.4.9 Object referencing modelling
- 6.4.10 Coordinate referencing
- 6.4.11 Multi-lingual text and cultural adaptability
- 6.4.12 Data quality
- 6.4.13 Metadata for evaluation and use
- 6.4.14 Multiple representations
- 6.4.15 Consistency between data
- 6.4.16 Portrayal model
- 6.4.17 Conformance
- 6.4.18 Generic Network Model
- 6.4.19 Gazetteers
- 6.4.20 Encoding and data formats
- 6.4.21 INSPIRE registers
- 6.4.22 Annex I data specifications
- 6.4.23 Outlook to Annex II/III data specifications
- 6.4.24 Extensions by countries or communities
he Generic Conceptual Model contains in Annex F a worked example for an extension to an INSPIRE application schema. The main focus of the Generic Conceptual Model are the INSPIRE data specifications. In addition, using INSPIRE data specifications as a basis for national or community extensions is strongly encouraged by the INSPIRE modelling framework as this will foster harmonisation and simplify the transformation of spatial data sets to the INSPIRE data specifications. It is the hope of INSPIRE that the INSPIRE data specifications will influence in many cases modelling activities for spatial data at the national level, because it adds value to the national spatial data infrastructure and simplifies transformation to the INSPIRE data specifications.
The example in Annex F of the Generic Conceptual Model explains how such extensions can be specified. The eContentplus proect ESDIN, for example, is currently extending Annex I data specification with addition requirements currently addressed in their specifications like EuroRegionalMap.
Extending an INSPIRE data specification would imply at a minimum that:
- the extension does not change anything in the INSPIRE data specification but normatively references it with all its requirements
- the extension does not add a requirement that breaks any requirement of the INSPIRE data specification
However, the extension may, for example, do any of the following:
- add new application schemas importing INSPIRE or other schemas as needed
- add new types and new constraints in your own application schemas
- extend INSPIRE code lists as long as the INSPIRE data specification does not identify the code list as a centrally managed code list
- add additional portrayal rules
In addition to these general rules that are mainly implied by the rules of UML, further harmonisation will be achieved, if the extensions conform to all requirements of the Generic Conceptual Model and the Guidelines for the encoding of spatial data, too.
An example illustrates en extension both on the conceptual level (UML) and the encoding level (XML Schema and XML).
| ← previous | Infrastructure for Spatial Information in the European Community (INSPIRE) | next → |
