Spatial Data Service sub-category

[PeterParslow]

TG Requirement 3.4 metadata/2.0/req/sds/sds-category states:

"At least one Spatial Data Service category or subcategory for the described service shall be given using the language-neutral keyword values as defined in Part D 4 “Classification of Spatial Data Services” of [Regulation 1205/2008]."

The current 'guidance' for service keywords is too similar to the guidance for dataset keywords. This requirement should be put there, not just in the encoding. And the 'guidance' and 'encoding guidance' sections should be de-duplicated.

The controlled vocabulary for these is at https://inspire.ec.europa.eu/metadata-codelist/SpatialDataServiceCategory

See #29, but this issue is to actually specify the requirement, rather than simply correct the example. I think this one is "breaking", but "just" correcting the example isn't?

[nmtoken]

What is the language-neutral keyword from Part D 4 “Classification of Spatial Data Services” of [Regulation 1205/2008] https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:32008R1205& for example:

101 Catalogue viewer (humanCatalogueViewer)
Client service that allows a user to interact with a catalogue to locate, browse, and manage metadata about
geographic data or geographic services.

Is it 101 or Catalogue viewer or humanCatalogueViewer

We'll assume it isn't the URI http://inspire.ec.europa.eu/metadata-codelist/SpatialDataServiceCategory/humanCatalogueViewer as it's not in D4.

[nmtoken]

OK, looking at example 4.2, it should be humanCatalogueViewer though example 4.2 misspells it.

So we need a new schematron rule that checks that we have either:

<gmd:keyword><gco:CharacterString>SDS D4 keyword</gco:CharacterString></gmd:keyword>

or

<gmd:keyword><gmx:Anchor>SDS D4 keyword</gmx:Anchor></gmd:keyword>

And possibly a local list of terms to check against

[PeterParslow]

https://inspire-mif.github.io/technical-guidelines/metadata/metadata-iso19139/metadata-iso19139.html Clause 4.3.3.2 has the SDS category as a Conformity statement, not "just" a keyword

[nmtoken]

Linking to the amending regulation for reference:

COMMISSION REGULATION (EU) No 1312/2014

31. “end point” means the internet address used to directly call an operation provided by a spatial data service,

32. “access point” means an internet address containing a detailed description of a spatial data service, including a
    list of end points to allow its execution,

33. “Invocable spatial data service” means all of the following:
    (a) a spatial data service with metadata which fulfils the requirements of Commission Regulation (EC) No
    1205/2008 (*),
    (b) a spatial data service with at least one resource locator that is an access point,
    (c) a spatial data service in conformity with a documented and publicly available set of technical specifications
    providing the information necessary for its execution,

34. “interoperable spatial data service” means an invocable spatial data service which fulfils the requirements of
    Annex VI,

35. “harmonised spatial data service” means an interoperable spatial data service which fulfils the requirements of
    Annex VII,

[nmtoken]

It's both a keyword (Example 4.2) of https://inspire-mif.github.io/technical-guidelines/metadata/metadata-iso19139/metadata-iso19139.html and also a conformity statement to one of (or at least one of, though one of makes more sense) Invocable|interoperable|harmonised SDS

So for validation I assume we could check for the keyword, and if it exists check for a conformity statement