zeginis

I agree. At OGI there are multi-lingual datasets. We may consider using JSON-LD (@language) to express the language used

I think a single requested or default language is enough. So something like "datasets(language:"fr"){..}; is ok. It is preferable to get the available languages for a specific dataset not for...

Some issues related to the language: - greek labels were not supported - language tag (e.g. @en) causes errors

It is ok to define the language at the top of the query and thus get results only in one language

> One other question @zeginis, would it be acceptable to not let you set this at the top of the query; but to supply it as a configuration option to...

Yes this is what I was thinking to implement. I realize that it is not as simple as I expected. Do you think there is a way to temporarily overcome...

@RickMoynihan any update on this? Are you going to fix this or we should go on with the "quick fix" option -> call the str on the language tagged string...

@lkitching I checked the PR. The queries are ok. I have tested them on some data created by Table2qb and they pass the tests. However I think we need some...

@lkitching I added 2 new SPARQL queries to support the CubiQL requirements I mentioned. When I run them independently at the SPARQL endpoint they return no results -> they succeed...

@lkitching what do you meant they are mapped to a `String` ? Can we use such dimensions without codelist to lock dimensions? e.g. ``` {cubiql{ dataset_earnings { title description observations(dimensions:{gender:ALL...