Übersicht:
Favoritenliste:
Favoritenseiten
Ihre Favoritenliste enthält derzeit keine Seiten. Sie fügen dieser Liste Seiten hinzu, indem Sie im Menü Extras der angezeigten Seite Favorit selektieren. |
> 3rd meeting
# round de table > new member (nomination from IT)
# proposal for the consolidated approach
# discussion
Did I understand you correctly, you still need the service metadata records to calculate the NSi4 indicators, right?
I thought there is created an option in the indicators to calculate them without service metadata see the description of NS4;
For this indicator only discovery, view, download and transformation network services will be taken into account. The identification of the type of network services will be done based on the "spatial data service type" metadata element when service metadata is provided, based on the definition of the service access points if these service access points are defined in data set metadata and based on the registered service endpoints for discovery network services. The conformity with Regulation (EU) No 976/2009 should be expressed in the "Conformity" metadata element. The Commission will provide a code list with possible conformity statements in the INSPIRE Register.
Having the service metadata only for the indicator is too much work for no benefit, there is no way I can explain that to the data producer. We need to find another option. Maybe the description field as an Anchor.
Can we not agree that all services added with the INSPIRE value of SpatialDataServiceType are conformant?
Could the conformity field eventually be in the dataset metadata in the getResource for each service ?
But there are still requirements on layernames and stored queries, isn't it ?
What is the value of the service = compatible flag in the service md, if there is no extendedCap anymore?
Would it be possible to add a conformance report on view service and download service within the dataset-metadata ?
= new issue and further discussion on GitHub
# next steps
= next meeting