[XSLT30] collection lang processing should refer to BCP47 [I18N-ISSUE-400][I18N-ACTION-467]

Hello QT,

The Internationalization (I18N) WG has been cleaning up our Tracker recently and we found that we inadvertently did not forward you one of our comments during the Last Call period on your document [0]. Although that LC is long closed, I have been asked to forward the comment in case you find it useful and/or are able to address it anyway. The comment is tracked here: [1] and reads:
In Section 13.1.3 I find:

The lang attribute indicates that a collation suitable for a particular natural language should be used. The effective value of the attribute must either be a string in the value space of xs:language, or a zero-length string. Supplying the zero-length string has the same effect as omitting the attribute. If a language is requested that is not supported, the processor may use a fallback language identified by removing successive hyphen-separated suffixes from the supplied value until a supported language code is obtained; failing this, the processor behaves as if the lang attribute were omitted.

This describes a fallback that is identical to RFC4647 Basic Filtering [1] used in BCP47. However, no reference is provided to BCP47.

I'd suggest explicitly referencing BCP47 here and specifying fallback by reference.

Best regards (for I18N),


[0] http://www.w3.org/TR/xslt-30/#collating-sequences

[1] https://www.w3.org/International/track/issues/400

Addison Phillips
Principal SDE, I18N Architect (Amazon)
Chair (W3C I18N WG)

Internationalization is not a feature.
It is an architecture.

Received on Saturday, 10 October 2015 20:11:03 UTC