Proposal to add hvdCategory as optional to GeoDCAT-AP 3.0

[hallinpihlatie]

In the High Value Datasets specification (DCAT-AP High Value Datasets) dcatap:hvdCategory and dcatap:legislationApplication are mandatory. (overview.jpg (2910×1102)

In GeoDCAT-AP 3.0 dcatap:applicableLegislation is optional. We'd suggest to also add dcatap:hvdCategory as optional to the GeoDCAT-AP 3.0.0. GeoDCAT-AP 3.0.0 (overview-annotated.jpg (3108×2475)).

[jescriu]

This issue is related to SEMICeu/GeoDCAT-AP#147

[H-a-g-L]

I would argue that while dcatap:applicableLegislation is included in the GeoDCAT-AP extension because it can be used to indicate any number of legal resources (e.g. the INSPIRE directive) and is not limited to the HVD implementing regulation, the dcatap:hvdCategory property is to be used for denoting the categories defined in the HVD implementing regulation (http://data.europa.eu/eli/reg_impl/2023/138/oj). Furthermore, the dcatap:hvdCategory property MUST be used with the High-value dataset categories taxonomy. The taxonomy is explicitly composed of “representations of the data categories as set out in Commission implementing Regulation (EU) 2023/138”.

To denote a thematic classification outside the context of the HVD regulation, I would argue that the DCAT properties dcat:theme and dcat:keyword (and optionally dct:subject) should be used. Adding the dcatap:hvdCategory property to thematically classify non-HV Datasets would, IMO, risk creating unnecessary confusion.

[hallinpihlatie]

I see what you mean. The confusion risk could perhaps be handled by adding an usage note on when to use it or do you consider the risk to prevail despite this.

I guess the main priority is that the SEMIC XSLT would 1) by default transform or 2) include an option to transform a HVD-keyword/URL in question to dcatap:hvdCategory if a relevant keyword/URL exists. The geoharvester of Conterra already does that.

In other mappings one might want to map it as dcat:theme or alike. For example in the more general mapping which is under development at the moment in an ISO211 project.

[jescriu]

This issue was long discussed in the Fourth Pilot meeting on 28 April, where it was highlighted the convenience of only using dcatap:hvdCategory for denoting High-value datasets, and the semantic implications on GeoDCAT-AP / DCAT-AP.

Based on this latter proposal

I see what you mean. The confusion risk could perhaps be handled by adding an usage note on when to use it or do you consider the risk to prevail despite this.

I guess the main priority is that the SEMIC XSLT would 1) by default transform or 2) include an option to transform a HVD-keyword/URL in question to dcatap:hvdCategory if a relevant keyword/URL exists. The geoharvester of Conterra already does that.

In other mappings one might want to map it as dcat:theme or alike. For example in the more general mapping which is under development at the moment in an ISO211 project.

I suggest to re-discuss this issue in the Fifth Pilot meeting focusing on the posibility to consider point 2.