Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify meaning of DataService.language #106

Open
jakubklimek opened this issue Mar 8, 2024 · 1 comment
Open

Clarify meaning of DataService.language #106

jakubklimek opened this issue Mar 8, 2024 · 1 comment
Labels
release:3.0.0 Actively being worked on for GeoDCAT-AP 3.0.0 status:fixed Resolution applied in draft type:improvement Improvement of current handling of a problem webinar:2024-03-12 To be discussed in the 2024-03-12 webinar

Comments

@jakubklimek
Copy link
Contributor

Problem statement
In the current GeoDCAT-AP 2.0.0, the language of a DataService has a usage note:

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.

consistently with how the DataService.format usage note looks like in DCAT-AP 3.0.

@jakubklimek jakubklimek added type:improvement Improvement of current handling of a problem release:3.0.0 Actively being worked on for GeoDCAT-AP 3.0.0 webinar:2024-03-12 To be discussed in the 2024-03-12 webinar next-webinar To be discussed in the next webinar labels Mar 8, 2024
@jakubklimek jakubklimek added status:resolution-provided Resolution statement present, not yet applied in draft and removed next-webinar To be discussed in the next webinar labels Mar 21, 2024
@jakubklimek
Copy link
Contributor Author

Resolution approved during the webinar.

@jakubklimek jakubklimek added status:fixed Resolution applied in draft and removed status:resolution-provided Resolution statement present, not yet applied in draft labels Apr 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release:3.0.0 Actively being worked on for GeoDCAT-AP 3.0.0 status:fixed Resolution applied in draft type:improvement Improvement of current handling of a problem webinar:2024-03-12 To be discussed in the 2024-03-12 webinar
Projects
None yet
Development

No branches or pull requests

1 participant