I did not look very well at this example, but could you elaborate a it on why xml:lang on optionlist or option itself woudl not be possible/feasible? I'd say it are not prompts.
You cannot properly select from the options if you give a xml:lang field. Each option has an id, and only one may be 'selected'. This can get into conflict with the xml:lang attribute.
In this way:
- you make implementation easier (if not possible at all), without the need for all kinds of checks to get the selected option with the right 'language', or foltering the options when a language requetsed is not specified, or none are specified, or they are partially specified... etc. ad naseum. xml:lang in lists simply don't work well.
- you enforce that multiple gui values for the same value (id) are grouped together, and that there is always an option for taht id, for every language
As to it not being a prompt - I disagree. The value of 'prompt' is a gui value, which can be represnted in sereval ways: as a option value in a combobox, but also as a prompt for a radiobox, or a prompt for the enumdata field type.
-- Pierre van Rooden Mediapark, C 107 tel. +31 (0)35 6772815 "Never summon anything bigger than your head."
