Option A — through an HVD-tagged distribution
<your-dataset-iri> dcat:distribution [
a dcat:Distribution ;
dcatap:applicableLegislation hvd-ir: ;
dcat:accessURL <https://your-api/service> ;
dct:license <.../licence/CC_BY_4_0> ;
dcat:accessService <your-service-iri>
] .
<your-service-iri> a dcat:DataService ;
dcatap:applicableLegislation hvd-ir: ;
dcat:endpointURL <https://your-api/service> ;
dcat:contactPoint <contact-iri> ;
foaf:page <https://your-api/documentation> ;
dcatap:hvdCategory <http://data.europa.eu/bna/c_4b74ea13> ;
dct:license <.../licence/CC_BY_4_0> .
Option B — linked directly with dcat:servesDataset
<your-service-iri> a dcat:DataService ;
dcat:servesDataset <your-dataset-iri> ;
dcatap:applicableLegislation hvd-ir: ;
dcat:endpointURL <https://your-api/service> ;
dcat:contactPoint <contact-iri> ;
foaf:page <https://your-api/documentation> ;
dcatap:hvdCategory <http://data.europa.eu/bna/c_4b74ea13> ;
dct:license <.../licence/CC_BY_4_0> .
The data service must be typed dcat:DataService and carry the applicable legislation itself. The endpoint URL, contact point, documentation page (foaf:page), HVD category and an open licence are mandatory checks: the API is still counted when they are missing, but each missing one is reported.