Task #2306

MIWP-8 (J) Metadata for SDS Specification

Added by Ine de Visser over 5 years ago. Updated over 5 years ago.

Status:SubmittedStart date:17 Sep 2014
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Proposed change or action:

Description

Specification (TG SDS 4.5.3)

The Specification metadata element set out in Regulation (EU) No 1205/2008 shall also refer to or contain technical specifications (such as INSPIRE technical guidance but not only), to which the invocable spatial data service fully conforms, providing all the necessary technical elements (human and wherever relevant machine readable) to allow its invocation.

In order to make machine-readable the documentation of the service interface (e.g. WSDL) the element gmx:Anchor could be used instead of gco:CharacterString. The backward compatibility is still valid because the human readable text is kept.

The citation of the Spatial Data Service Regulation shall be provided.

Actions:

  1. Check defenitions of Specification in IR MD, TG MD and TG SDS, .. are they in line with each other?
  2. Update TG MD 2.8.2  Specification
  3. Update TG MD 2.8 Conformancy with Spatial Data Service Regulation  
  4. Give examples, explain  ...
  5. provide a codelist for all INSPIRE regulations, specifications etc

 


Related issues

Copied from MIWP-8: Metadata - Task #2305: MIWP-8 (J) Metadata for SDS Resource locator Submitted 17 Sep 2014
Copied to MIWP-8: Metadata - Task #2307: MIWP-8 (J) Metadata for SDS Coordinate reference system Submitted 17 Sep 2014
Copied to MIWP-8: Metadata - Task #2309: MIWP-8 (J) Metadata for SDS Point of contact Submitted 17 Sep 2014

History

#1 Updated by Ine de Visser over 5 years ago

COMMISSION REGULATION (EU) No 1312/2014 of 10 December 2014 amending Regulation (EU) No 1089/2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data services

The Specification metadata element set out in Regulation (EC) No 1205/2008 shall also refer to or contain technical specifications (such as INSPIRE technical guidance but not only), to which the invocable spatial data service fully conforms, providing all the necessary technical elements (human, and wherever relevant, machine readable) to allow its invocation.’

TG SDS;

Implementation Requirement 5 The citation of the Spatial Data Service Regulation shall be provided.

 

proposed change in TG MD;
 

Add to  2.8 Conformancy

TG Requirement XX In conformance to COMMISSION REGULATION (EU) No 1312/2014 of 10 December 2014 amending Regulation (EU) No 1089/2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data services, the metadata  shall also refer to or contain technical specifications (such as INSPIRE technical guidance but not only), to which the invocable spatial data service fully conforms, providing all the necessary technical elements (human, and wherever relevant, machine readable) to allow its invocation.’

 

#2 Updated by Ine de Visser over 5 years ago

and Also

TG Requirement XX

The citation of the COMMISSION REGULATION (EU) No 1312/2014 of 10 December 2014 amending Regulation (EU) No 1089/2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data services shall be provided.

Question; Should this replace the citation of COMMISSION REGULATION (EU) No 1089/2010 of 23 November 2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services in case of spatial data services and network services? Those services have their requirements to citate other regulations

#3 Updated by Peter Kochmann over 5 years ago

My state of knowledge is as follows:

For INSPIRE spatial dataset and series the conformity statement aims at least at IR 1089/2010. In addition a citation of data specifications (as TG) and/or maintenance of IR 1089/2010 (e.g. 1253/2013) can be given.

For INSPIRE network services always the IR 976/2009 has to be named. In addition a citation of TG View or Download can be given.

Following that (assumed) system I propose to give IR 1089/2010 for SDS as well and maybe have an additional one that gives 1312/2014, because 1312/2014 itself is just an amendment and not a complete regulation.

#4 Updated by Michael Östling over 5 years ago

I don't feel fully comfortable with this implementation. 
Maybe I need to get some clarifications on this.

We have in IR Metadata requirements to report conformance.
This is implemented as a DQ_ConformanceResult with mandatory elements
- Specification
- Explanation
- Pass

The suggested implementation for SDS Specification is to use to use ConformanceResult/Specification
But it's not a ConformanceResult we define the specification for. Its a Specification for the resource.

To use the above we need to add Explanation and Pass with nil-values.

As an alternative I could see possibility to use AccessURL with elements
- URL
- Name

- CI_OnlineFunctionCode (using value Information or a new value Specification)

The definition of AccessURL is

(link(s) to the resource access and/or endpoint and/or the link to additional information about the resource)

#5 Updated by Ine de Visser over 5 years ago

I can't follow your comment, please explain what you mean with

"The suggested implementation for SDS Specification is to use to use ConformanceResult/Specification
But it's not a ConformanceResult we define the specification for. Its a Specification for the resource."

In my opinion it's the same method of conformance declaration used in TG MD for network services. Or do i mis something?

#6 Updated by Peter Kochmann over 5 years ago

For my understanding there is no alternative than using DQ_ConformanceResult for SDS specification.

The description in 1312/2014 names no additional metadata element for documenting a SDS specification but clearly names the metadata element  for specification given in context of 1205/2008. So it focusses on the same element as INSPIRE network services and INSPIRE dataset/series do but with probably different content.

The example given in TG SDS of course is incomplete because explanation and pass are mandatory indeed.

#7 Updated by Michael Östling over 5 years ago

I see the scope for the Specification is actually   Additional Requirements on Metadata Set Out in Regulation (EC) No 1205/2008

So then I agree it should just be extended requirements on the already existing Specification.

Also available in: Atom PDF