INSPIRE-MIF/gp-data-service-linking-simplification

Figure in 7.2 Resources

Closed this issue · 11 comments

heidivanparys commented

I have a few questions / comments regarding the figure in 7.2 Resources:

annotated image

I tried to create an adapted version – for discussion – and of course the contents of a new figure would depend on the answers to some of my questions.

simplified

(as powerpoint)

MarieLambois commented

I am not really convinced that scenario 1 and 2 have still a meaning in the simplified approach. From what I understood, I also tried to improve @heidivanparys diagram a little bit. I re-introduce the (now optional) link to the Dataset MD from the service MD) and precised the the INSPIRE extension in the GetCapabilities is now optional.
image
To make really appear that it is a simplification I also drafted another diagram with only the mandatory elments:
image
INSPIRE.models_v1.2.pptx

  • 👍4
heidivanparys commented

Meeting 2022-06-21:

  • general agreement to use two figures
  • add note regarding the Spatial Data Set Identifier (see also #52)
  • change the colours so there is a difference between mandatory and optional (dark blue vs light blue)
jescriu commented

Dear @heidivanparys,

Regarding

I have a few questions / comments regarding the figure in 7.2 Resources:

and your 1st question/comment:

Is this figure supposed to illustrate scenario 2 only? Or is it supposed to give a general overview overview of this specification?

I think that the initial graphic was intended to provide a general overview of the scenarios (1 and 2) and possibilities, once introduced the new data-service linking simplification approach. But @dartasensi may confirm much better than me.

The rest of your comments and proposals makes totally sense to me.

Also the new "simplified" versions of the graphics provided by @MarieLambois - Just to comment two thing on them:

  • In the first simplified graphic, please correct the double 's' typo in '[O] Coupled Ressources'.
  • Note that the second simplified graphic is only representing the data-service linking simplification approach.

I will provide input on #52 as soon as possible, so there might be some implication to the final note on 'Spatial Data Set Identifier' to be added here.

Who will be finishing the editorial changes to the graphics above?

Jordi

idevisser commented

I will do the editoral changes, as part of the presentation in the MIG-T

  • 👍1
idevisser commented

Updated version;

image

image

INSPIRE.models_v1.3
INSPIRE.models_v1.3.pptx

jescriu commented

Dear @idevisser,
As I warned in my last post, the note regarding the Spatial Data Set Identifier for services will require some amendment.
I will provide input on #52 today.

heidivanparys commented

The legend should be updated to describe scenario 3 as well.

idevisser commented

I have update the legend as following;
Note:
• Regarding the INSPIRE compliant Service MD; In an INSPIRE Network Service – Scenario 1 implementation, this Service MD will not contain all INSPIRE metadata elements but contain a link to the Service MD in the Discovery Service. Scenario 2 and 3 have no separate Service MD in the Discovery Service, Scenario 2 makes use of extended capabilities, scenario 3 remaps the metadata elements to existing capability elements and the dataset metadata.
• Regarding the Spatial Data Set Identifier; The IR on metadata is not including the Unique resource identifier as a required metadata element to be applied to services. The TG for Download and View services specify a WxS/Atom metadata element that contains the Unique Resource Identifier of the Spatial Data Set. In the current INSPIRE Geoportal this is used, in some cases, to establish a link between data and service for quality control purposes. The Coupled resource would be enough for data-service linking purposes, as is used e.g. in case of a WMS in the current INSPIRE Geoportal.

  • 👍1
jescriu commented

Dear @idevisser, @heidivanparys, @MarieLambois, @AntoRot,
I prepared a new final version of the file with the graphics with minor aesthetic changes.
INSPIRE_models_v1.5.pptx
I will include this version in Section 7.2 of Part A consolidated proposal, and subsequently proceed to close this issue.