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
fulfillment language #401
Comments
CIT defines train ticket language rules - in general "should be in language of the passenger".
|
For interface we want to use the accept-header This will be placed in the documentation |
I would note that |
Related to languages on tickets and communication to customer/retariles I´d follow CIT MIR directive as Joseph and Clemens mentioned. And as we´re currently doing. |
Accept language only where it is relevant |
So, to sum up the concrete impact on specifications:
|
…nt-language-#401 changes covered in issue #401 on languages
What the documentation currently states
What is defined in the swagger
Languages as they apply in the business (benerail view)
Usually in our business, we can distinguish the following use cases where language or localised information is relevant:
So, what is wrong ?
Benerail proposal
The text was updated successfully, but these errors were encountered: