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

Batch/multi-lingual requests #8

Open
achimr opened this issue Sep 19, 2014 · 1 comment
Open

Batch/multi-lingual requests #8

achimr opened this issue Sep 19, 2014 · 1 comment
Assignees

Comments

@achimr
Copy link
Contributor

achimr commented Sep 19, 2014

In each request, allow array of JSON structure instead of single substructure.

Easy for plain text requests, but not requests that involve files/URLs.

@achimr achimr self-assigned this Sep 19, 2014
@achimr achimr added this to the v2.0 Specification Issues milestone Sep 19, 2014
@achimr
Copy link
Contributor Author

achimr commented Sep 19, 2014

Comment from Yves Savourel:
I wonder about the scope of the resource ID. It is for a resource that is a source/target pair. But in many systems the model is to have an ID for a resource that has a source and zero or more targets. The target language code can easily be used to make the distinction between targets. One of the reasons for this is that potentially quite a few metadata redundant when using several pairs.Examples of such model are for instance the LingoTek API: http://devzone.lingotek.com/#/api-explorer, or the Transifex API: http://docs.transifex.com/developer/api/. I'm just curious about advantages the current model of the bilingual resource brings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant