External Collection of value keys, status codes etc.: Unterschied zwischen den Versionen
Aus DRV STRING
| Zeile 10: | Zeile 10: | ||
=== Categories of STRING codes and messages === | === Categories of STRING codes and messages === | ||
| − | === Value Keys for Configuration Response ==== | + | ==== Value Keys for Configuration Response ==== |
* max_travellers | * max_travellers | ||
| Zeile 16: | Zeile 16: | ||
* [...] | * [...] | ||
| − | + | ==== Credit Card Codes ==== | |
* MA - Mastercard (we use only one code of the different ones in circulation) | * MA - Mastercard (we use only one code of the different ones in circulation) | ||
Version vom 25. Mai 2018, 10:02 Uhr
STRING will avoid to define possible values for elements in enumerations inside the schema files as this leads to validation violations when new values are added within the same version. We decided to collect these values in a central place on the project server alongside the schema definitions where they will be updated as needed.
The rules regarding these definitions are:
- You are supposed to use only values defined by STRING but you are not enforced to do so.
- You should detect unknown values and fail gracefully. Depending on the environment this could mean to just ignore it or to produce a meaningfull error message.
- If you need a new value (that is: you use a value in a communication between two partners already and think it should go into the common definition) please feel free to propose it to the STRING board (TODO: add link to documentation about this process).
Categories of STRING codes and messages
Value Keys for Configuration Response
- max_travellers
- max_services
- [...]
Credit Card Codes
- MA - Mastercard (we use only one code of the different ones in circulation)
- VI - Visa
- AM - American Express
- DI - Diner's Club
- [...]
[...]
