OASIS Open

New Context Services, Inc.

No

I would really like to vote yes, but practically I cannot. Supporting an required but undef option is just the same as optional.

In most cases, optional and unspecified will effectively mean en, which is likely going to be the bottom of the stack choice for display anyways.

Implementors who care will populate it, and their content will be preferred over the specified cases.

I am nervous about other small locales leaving lang unspecified and not specifying their local language which will cause problems.

I'd like to see a SHOULD be specified if language is not en, but I do realize that is special casing en, but it is the world we live in (that english is the common denominator of languages now).