In past interfaces many values were added to transactions which almost never changed or at least were not updated on short notice. STRING moves them to a separate configuration query which is supposed to be executed by clients in a much lower frequency, for instance once per day and operator. In the meantime the values returned should be cached / stored locally.
One the one hand this query will return basic operator data like address, insolvency insurance and so on. On the other hand it provides a set of limitations and features of the operator system which are not by itself defined in the schema, for instance the maximum number of travellers in a request.
[...] (TODO: add image of ConfigurationResponse)
- ConfigurationRequest (a way to specifically ask for certain categories of information might be added later)
- ConfigurationResponse contains a list of key-value pairs as defined in the directory of external definitions