1 Keith Murray INSPIRE Data Specifications DT INSPIRE Conference, Edinburgh, June 2011 Short term...

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

TopicsTopics

• Why? & maintenance

• When? & maintenance

• What? & maintenance

• Who? & maintenance

• How? & maintenance

• Recommendations/Priorities----------------------------------------------------------------• References• Annex – draft flows

INSPIRE progress 2

3

WhyWhy

3

44

INSPIRE Regulation dates INSPIRE Regulation dates

2010 2012 2016

Annex I & II Compliant

Annex III Compliant

2014 2018

Develop Full Discovery & View Operational

2008

2010 2012 20162014 20182008

New data

Annex I themes Existing data

Annex II* & III themes

Annex II* & III themes

New data

Develop Download & Transformation Operational

Metadata, Discovery, View, Download & Transf & Annex I dates are all accurate – all other dates are best estimates

Metadata

Metadata

Legal adoption

V1.12 of 09 June 2011

Full

Invoke Invoke

Metadata

Data

Services

*Note: SDS will enter force via the ISDSS Regulation

Annex I themes

5

Why?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

6INSPIRE Data Specifications 66

Org

anis

ation

al B

usin

ess

Dat

aSp

atial

Obj

ects

Widely reused - widely referenced

Application specific - referenced

Report(PDF)

010010100010010100010101111101111110010010110100 23 March 2001

Timetable

Loose coupling – linkage

Standards

Data scope: spatial & non-spatialData scope: spatial & non-spatialIn

sco

pe n

ow o

r fut

ure

Not

in s

cope

7

Data Spec Scenario: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

WhenWhen

8

9

WhenWhen

• 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 needsie 2011 – 2012

10

WhatWhat

10

11

What?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

RegistersCodelists/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


UML model


Portrayal

Namespaces*

Vocabularies

Licenses


Data Specifications


UML model


Portrayal

Authentication

Namespaces*

Vocabularies

Licenses


Data Specifications


UML model


Portrayal

Authentication

Namespaces*

Vocabularies

Licenses

MS (only) sourceMS Candidate

European Commission: INSPIRE Member State: Any

Dat

a m

anag

emen

t b

ou

nd

ary

Data Publishers

Vocabs

Feature catalogues

Third Party eg WMO

13

WhoWho

13

14

Who?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

HowHow

15

16

HowHow

• Agree data configuration management principles:

– Registry data should be held once and reused (if required - echoed by 3rd 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

Limited Change ControlsLimited Change Controls

• Permitted Actions:– Add– Fix/Change– Depreciate

INSPIRE progress 17

European Commission

Member State Proviso

Add (Spatial Object) Yes Yes* *As candidate via MS register & liaison with the EC

Fix (Issue) Yes No MS cannot change INSPIRE Specifications – need to submit change request to EC

Depreciate (Spatial object or record)

Yes No MS cannot change INSPIRE Specifications – need to submit change request to EC

18

Process for “Fix_SO” Process for “Fix_SO” (may also be used for Depreciate)(may also be used for Depreciate)

INSPIREData Spec

Member States or TWG (LMO&SDIC via MS)

European Commission

Initiating MS

Upd & finalise INSPIRE data model & spec

Agree

UpdateWithdraw

Reject

ApproveChange

Reject

Prepare formal change plan

(scope/reason/time)

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

Recommendations - PrioritiesRecommendations - Priorities

19

20

Priorities for 2011-12Priorities 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

ReferencesReferences

INSPIRE progress 21

Ref Date Title

A INSPIRE DS DT2009-01-15

Drafting Team "Data Specifications"Maintenance of data specifications and associated documents

B INSPIRE Committee2010-12-16

Maintenance Paper to the INSPIRE Committee for Member State comment

C Austria Member State2011-05-16

Austrian Response on the “INSPIRE Maintenance & Implementation Discussion Paper.

D INSPIRE JRC2011-05-26

Discussion paper on INSPIRE Registers

E INSPIRE DS DT2011-06-09

Data maintenance priorities & mechanisms at Member State & EC levels

22

Annex AAnnex A– draft high level flows for Add & Fix SO– draft high level flows for Add & Fix SO

INSPIRE progress 22

23

Add_SOAdd_SO

24

Agree Process to be used for “Add_SO”Agree Process to be used for “Add_SO”

INSPIREData Spec

Organisati’nData Spec

MS Agree process with EC

SO found in Org’n dataset not supported

by INSPIRE

Where a member state organisation holds SO’s 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

Fast track for “Add_SO”Fast track for “Add_SO”

INSPIREData Spec

European Commisson

Initiating

All incl TWG


10 day review by MS & TWG

Defer

Agree

Reject


Agree

Update

Theme/SO/FCat


by INSPIRE

Organisat’nData Spec

Submit Candidate SO

description

Defer

Defer: transfer to Dual Running

ApproveChange

Member States (LMO&SDIC via MS)

Review proposal

Reject

Withdraw

26

Dual Running for “Add_SO”Dual Running for “Add_SO”

INSPIREData Spec

European Commission

Organisat’nData Spec


by INSPIRE

Submit outllineCandidate SO

description

Initiating MS


Theme/SO/FCat


Agree

Update

Reject

Reject

Withdraw

All to MS FCat/Codelist

RegisterMay 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

ApproveChange

27

Fix_SOFix_SO

28

Process for “Fix_SO” Process for “Fix_SO” (may also be used for Depreciate)(may also be used for Depreciate)

INSPIREData Spec

Member States or TWG (LMO&SDIC via MS)

European Commission

Initiating MS


Agree

UpdateWithdraw

Reject

ApproveChange

Reject

Prepare formal change plan

(scope/reason/time)

Notify MS/TWG

Error or change required in

INSPIRE Data Spec (Feature or attribute)

Request for Change to EC for INSPIRE

Agree


Comments

1 Keith Murray INSPIRE Data Specifications DT INSPIRE Conference, Edinburgh, June 2011 Short term...

Documents

Transcript of 1 Keith Murray INSPIRE Data Specifications DT INSPIRE Conference, Edinburgh, June 2011 Short term...