-
assigned issue to
Messages 4.1.2.1.1 Default for Locale member
The Locale member of the userinfo structure is defined as {{{ locale OPTIONAL. (Locale): The default languages and scripts of the entire claim request, represented as a space-separated list of BCP47 [RFC5646] language tags. }}}
Does a default with a list of values make sense? Should it just be one value?
Comments (3)
-
reporter -
- changed status to open
This is in the request and is an acceptable list of locales. For example, a Japanese web service may want ja-JP if possible, but en may be acceptable. Then, one should list it as
"loacale":"ja-JP en"
On the other hand an US based service may not be able to accept Japanese because they cannot read it. Then, it should request
"locale":"en"
I agree that the current definition lacks the preference order, but when I wrote it, I just meant the list of acceptable locales and no preference.
Proposed change type (1)
locale OPTIONAL. (Locale): The list of acceptable languages and scripts of the entire claim request, represented as a space-separated list of BCP47 [RFC5646] language tags.
Proposed change type (2)
locale OPTIONAL. (Locale): The list of acceptable languages and scripts of the entire claim request, represented as a space-separated list of BCP47 [RFC5646] language tags in the order of the preference.
Change type (1) is just a clarification, (2) is a normative change. I think at this stage, we should just do (1).
-
- changed status to resolved
Fix
#292- Messages 4.1.2.1.1 Default for Locale member - Log in to comment