Add endpoint for available languages

[cmutel]

No description provided.

[sami-m-g]

@cmutel should this be a separate endpoint get_languages given an iri or do you think we could return this in the perspective endpoints for ConceptScheme. Collection and Concept along with the other data?

[jsvgoncalves]

Probably much easier to implement at a global level. Not sure going to the individual resource group level adds much user value, @cmutel

[sami-m-g]

@jsvgoncalves it needs to be on iri level since every entity (ConceptSchem, Concept, ...etc.) have different available languages. Actually, maybe even the prefLabel and the altLabel of the same Concept can have different available languages.

[cmutel]

I had in mind an endpoint for all languages present regardless of specific endpoint. I don't think we need more than that, we will always allow for users to request a language, and then fall back to en.

[sami-m-g]

@cmutel given this:

every entity (ConceptScheme, Concept, ...etc.) have different available languages. Actually, maybe even the prefLabel and the altLabel of the same Concept can have different available languages.

It might be frustrating for users to find an available language returned by the endpoint that is not available for most labels. However, your call!

[sami-m-g]

@cmutel given this:

every entity (ConceptScheme, Concept, ...etc.) have different available languages. Actually, maybe even the prefLabel and the altLabel of the same Concept can have different available languages.

It might be frustrating for users to find an available language returned by the endpoint that is not available for most labels. However, your call!

@cmutel @jsvgoncalves I still suggest avoiding user frustration but kindly confirm your decision on a single endpoint so I can start working on this.