Should the API Framework include guidance on I18N, L10N?

[boshrin]

e.g., support multiple values for selected attributes (like name) for different language representations

[khazelton]

In general, if you are developing an API, you should expect to see any UTF-8 characters plus a language tag (e.g., for names)

Would it be good enough to stipulate that UTF-8-encoded characters must be allowable in attribute values?

We also need to add language tags. Use the locale ISO 639-1 (name of language in 2 letter format), ISO 3166-1 for country; two-letter language code plus two-letter country code.