This property refers to a language supported by the Data Service. This property can be repeated if multiple languages are supported in the Data Service
The problem is that it is unclear what is meant by the reference to the Data Service class. The language of the data served by the Data Service is already covered by Dataset.language. Therefore, the Data Service language refers to the language of the parameters of the service and of the data structures (XML tags, CSV column headers, JSON key names, etc.) returned by that service.
Proposal
Clarify that DataService.language refers to the language of the parameters of the service and of the data structures (XML tags, CSV column headers, JSON key names, etc.) returned by that service by changing the usage note to:
The language of the structure that can be returned by querying the endpointURL.
Problem statement In the current GeoDCAT-AP 2.0.0, the language of a DataService has a usage note:
The problem is that it is unclear what is meant by the reference to the Data Service class. The language of the data served by the Data Service is already covered by Dataset.language. Therefore, the Data Service language refers to the language of the parameters of the service and of the data structures (XML tags, CSV column headers, JSON key names, etc.) returned by that service.
Proposal Clarify that DataService.language refers to the language of the parameters of the service and of the data structures (XML tags, CSV column headers, JSON key names, etc.) returned by that service by changing the usage note to:
consistently with how the DataService.format usage note looks like in DCAT-AP 3.0.