1. 1 Keith Murray INSPIRE Data Specifications DT INSPIRE Conference, Edinburgh, June 2011 Short term priorities for maintenance and support to implementation at Member States and EC levels 1

2. 2 Topics Why? & maintenance When?& maintenance What? & maintenance Who? & maintenance How? & maintenance Recommendations/Priorities ---------------------------------------------------------------- References Annex – draft flows INSPIRE progress 2

3. 3 Why 3

4. 4 4 INSPIRE Regulation dates 201020122016 Annex I & II Compliant Annex III Compliant 20142018 Develop Full Discovery & View Operational 2008 201020122016201420182008 New data Annex I themes Existing data Annex II* & III themes New data DevelopDownload & Transformation Operational Metadata, Discovery, View, Download & Transf & Annex I dates are all accurate – all other dates are best estimates Metadata Legal adoption V1.12 of 09 June 2011 Full Invoke Metadata Data Services *Note: SDS will enter force via the ISDSS Regulation Annex I themes

5. 5 Why? Registry items that need to be established –Namespaces –Codelists Errors/change required to INSPIRE data specifications –Eg candidate spatial objects from Annex I not used Manage features in MS datasets are not in the INSPIRE data specification –TN, HY & others –Annex II & III more extensible approach INSPIRE progress 5

6. 6 INSPIRE Data Specifications6 6 Organisational Business Data Spatial Objects Widely reused - widely referenced Application specific - referenced Report (PDF) 01001010 00100101 000101011 111011111 10010010 110100 23 March 2001 Timetable Loose coupling – linkage Standards Data scope: spatial & non-spatial In scope now or future Not in scope

7. 7 Data Spec Scenario: Changes are found necessary eg a organisation in a Member State discovers an error or omission in an existing adopted INSPIRE data specification, or holds spatial objects not covered by the data specification A data provider has limited options: 1.Omit the feature from their INSPIRE compliant dataset? 2.Add in an additional feature using a local data specification? 3.Fix the issue or establish a model for the additional spatial object using the INSPIRE model and use that.? INSPIRE progress 7 Only option 3 will maintain interoperability

8. 8 When 8

9. 9 When Longer term arrangements[2013 onwards]: –post legislative phase –all aspects of INSPIRE management –powers & governance to decide Shorter term needs [2011-12]: –INSPIRE is now a living entity –change is continuous –the world moves on –existing teams manage change INSPIRE progress 9 The scope of this paper ONLY applies to the short term needs ie 2011 – 2012

10. 10 What

11. 11 What? Data Specifications [DS DT]: –Reference documents [D2.5, D2.7, D2.9 O&M] –Data Specifications [2.8.1-34] –Data model [UML, Feature Catalogue] Tools [DS DT]: –ShapeChange, –FC generation, –Model checking etc Registers [IOC TF] –need to be established –then kept up to date INSPIRE progress 11

12. 12 Registers Codelists/ Enumerations Data Specifications Feature Catalogue by theme UML model Coordinate Reference Systems &Grids Portrayal Namespaces* Vocabularies Licenses INSPIRE Adopted EC Candidate Codelists/ Enumerations Data Specifications Feature Catalogue by theme UML model Coordinate Reference Systems &Grids Portrayal Namespaces* Vocabularies Licenses Codelists/ Enumerations Data Specifications Feature Catalogue by theme UML model Coordinate Reference Systems &Grids Portrayal Authentication Namespaces* Vocabularies Licenses Codelists/ Enumerations Data Specifications Feature Catalogue by theme UML model Coordinate Reference Systems &Grids Portrayal Authentication Namespaces* Vocabularies Licenses MS (only) source MS Candidate European Commission: INSPIRE Member State: Any Data management boundary Data Publishers Vocabs Feature catalogues Third Party eg WMO

13. 13 Who

14. 14 Who? European Commission –overall ownership of the specifications –change control owners Member States –organisations who use the specifications –technical coordinating bodies at MS level –third parties Joint EC & MS –existing Structures in short term [DS DT, TWG, IOC TF] INSPIRE progress 14

15. 15 How

16. 16 How Agree data configuration management principles: –Registry data should be held once and reused (if required - echoed by 3 rd parties). –Registry data/data specifications should be managed and published by the authority responsible for its creation and maintenance –Member states will need to hold complementary registers for items that are in use but have not yet been adopted into the INSPIRE schema, or are purely of a local nature. –Extensions/corrections to theme data specifications ie feature or extension to type of feature, will always follow the INSPIRE Generic Conceptual Model and Encoding Guidance. –The maintenance process for registry/master data items will require lifecycle definition (eg design/candidate, currently in use, no longer in use) –Registries should be machine readable –Registry data will, by the adoption of the above principles, be distributed. INSPIRE progress 16

17. 17 Limited Change Controls Permitted Actions: –Add –Fix/Change –Depreciate INSPIRE progress 17 European Commission Member StateProviso Add (Spatial Object)YesYes**As candidate via MS register & liaison with the EC Fix (Issue)YesNoMS cannot change INSPIRE Specifications – need to submit change request to EC Depreciate (Spatial object or record) YesNoMS cannot change INSPIRE Specifications – need to submit change request to EC

18. 18 Process for Fix_SO (may also be used for Depreciate) INSPIRE Data Spec Member States or TWG (LMO&SDIC via MS) European Commission Initiating MS Upd & finalise INSPIRE data model & spec Agree Update Withdraw Reject Approve Change Reject Prepare formal change plan (scope/reason/ti me) Notify MS/TWG Error or change required in INSPIRE Data Spec (Feature or attribute) Request for Change to EC for INSPIRE Agree Consult DS DT - Agree Comments

19. 19 Recommendations - Priorities 19

20. 20 Priorities for 2011-12 INSPIRE progress 20 Recommendation 1: A change request process to Fix/Align and Depreciate items (data specification or register item) is required and this has to be controlled by the European Commission. Such a mechanism should be established in 2011 [Fasttrack & Dual Running]. Recommendation 2: The Add process will be required for such cases and may be initiated by Member States and the process supported by the European Commission to maintain interoperability. Recommendation 3: The three forms of change control on data specifications and registry items should be piloted starting in 2011 to evolve the most effective approach that balances change control with ease of deployment by data publishers. Recommendation 4: Stable URIs for registry items are required in 2011 – this includes URI for codelists, coordinate reference systems and portrayal schema as well as URI for spatial objects [for Member States who do not have an existing URI pattern] Recommendation 5: An INSPIRE namespace register is a 2011 requirement. Where Member States have established conforming URI patterns for spatial objects – the creation and maintenance of the namespace register may reside at Member State level.

21. 21 References INSPIRE progress 21 RefDateTitle AINSPIRE DS DT 2009-01-15 Drafting Team "Data Specifications" Maintenance of data specifications and associated documents BINSPIRE Committee 2010-12-16 Maintenance Paper to the INSPIRE Committee for Member State comment CAustria Member State 2011-05-16 Austrian Response on the INSPIRE Maintenance & Implementation Discussion Paper. DINSPIRE JRC 2011-05-26 Discussion paper on INSPIRE Registers EINSPIRE DS DT 2011-06-09 Data maintenance priorities & mechanisms at Member State & EC levels

22. 22 Annex A – draft high level flows for Add & Fix SO INSPIRE progress 22

23. 23 Add_SO

24. 24 Agree Process to be used for Add_SO INSPIRE Data Spec Organisatin Data Spec MS Agree process with EC SO found in Orgn dataset not supported by INSPIRE Where a member state organisation holds SOs not included in the INSPIRE Data Specification - if agreement exists - these features maybe added For universally recognised and well prepared cases a 3 month fast track process may be adopted (and is the preferred approach*) – otherwise a slower process may be adopted where a MS(s) support the SO until a unified agreement is reached -------------------------------------------------------------- *in all cases formal changes to the INSPIRE documents/registry will be necessary – some of which may take 12-24 months (eg if changes to the Regulation are necessary) Dual Running Fast Track

25. 25 Fast track for Add_SO INSPIRE Data Spec European Commisson Initiating All incl TWG Consult DS DT - Agree 10 day review by MS & TWG Defer Agree Reject Upd & finalise INSPIRE data model & spec Agree Update Theme/SO/FCat SO found in Orgn dataset not supported by INSPIRE Organisatn Data Spec Submit Candidate SO description Defer Defer: transfer to Dual Running Approve Change Member States (LMO&SDIC via MS) Review proposal Reject Withdraw

26. 26 Dual Running for Add_SO INSPIRE Data Spec European Commission Organisatn Data Spec SO found in Orgn dataset not supported by INSPIRE Submit outlline Candidate SO description Initiating MS Consult DS DT - Agree Theme/SO/ FCat Upd & finalise INSPIRE data model & spec Agree Update Reject Withdraw All to MS FCat/Codelist Register May be used by organisations within the MS Member States (LMO&SDIC via MS) Agree Add to candidate SO notice board for MS Review MS/TWG Approve Change

27. 27 Fix_SO

28. 28 Process for Fix_SO (may also be used for Depreciate) INSPIRE Data Spec Member States or TWG (LMO&SDIC via MS) European Commission Initiating MS Upd & finalise INSPIRE data model & spec Agree Update Withdraw Reject Approve Change Reject Prepare formal change plan (scope/reason/ti me) Notify MS/TWG Error or change required in INSPIRE Data Spec (Feature or attribute) Request for Change to EC for INSPIRE Agree Consult DS DT - Agree Comments