You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The API urls are multilingual. They have already been multilingual since last October, because the UvA users use the Dutch phonology.
Because the Wiki examples page was removed, it is not evident on Swagger that the urls are multilingual, because Swagger does not accommodate the Accept-Language header.
It is not feasible to add the Accept-Language code to Swagger, without hacking Swagger. (There are examples of this on the web, but those users are not using Django.)
The easiest, least amount of English and Json typing is to simply do it this way:
Issue: Document that the API also works with gloss fields and field choices in Dutch.
Propose to do it this way:
add an optional language code to the url itself as shown below:
This can be done simply with an illustration of one url:
In the first case, the exact same url is used. This defaults to English, unless the user is using the Accept-Language in their request.
This is what happens with Swagger, which uses English.
For the second case, the Swagger example is added:
get_gloss_data/{datasetid}/{glossid}/nl/
For this, the Dutch fields and example output with Dutch phonology can be shown. This can also be done for Chinese.
The text was updated successfully, but these errors were encountered:
The API urls are multilingual. They have already been multilingual since last October, because the UvA users use the Dutch phonology.
Because the Wiki examples page was removed, it is not evident on Swagger that the urls are multilingual, because Swagger does not accommodate the Accept-Language header.
It is not feasible to add the Accept-Language code to Swagger, without hacking Swagger. (There are examples of this on the web, but those users are not using Django.)
The easiest, least amount of English and Json typing is to simply do it this way:
Issue: Document that the API also works with gloss fields and field choices in Dutch.
Propose to do it this way:
This can be done simply with an illustration of one url:
get_gloss_data/{datasetid}/{glossid}/
get_gloss_data/{datasetid}/{glossid}/(en|nl|zh-hans)/
In the first case, the exact same url is used. This defaults to English, unless the user is using the Accept-Language in their request.
This is what happens with Swagger, which uses English.
For the second case, the Swagger example is added:
get_gloss_data/{datasetid}/{glossid}/nl/
For this, the Dutch fields and example output with Dutch phonology can be shown. This can also be done for Chinese.
The text was updated successfully, but these errors were encountered: