This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Issue #46 of i18nCore comments: http://www.w3.org/International/reviews/0606-its/ Section 5.6: Should this be identified by global rules as language information? If not, we should explain why in the language information data category section. FS: The current definition 6.7.1. says "The element langRule is used to express that a given piece of content (selected by the attribute langPointer) is used to express language information as defined by [RFC 3066bis]." I would add a note saying "Applying this data category to xml:lang attributes does not make sense since xml:lang is already defined in terms of RFC 3066 or its successor". If that would address your concern, please add it to your comment. I18n: We propose a slight alteration to the above: Applying the langRule data category to xml:lang attributes using global rules is not necessary, since ...
I'm not sure it's quite right: We don't use the langRule data cat on xml:lang because xml:lang is defined in terms of RFC30666. We don't use langRule on xml:lang because xml:lang is already the standard way to specify languages (regardless how it expresses that information). So I would add something like: "The element langRule is used to express that a given piece of content (selected by the attribute langPointer) is used to express language information as defined by [RFC 3066bis]. Note: Applying the langRule data category to xml:lang attributes using global rules is not necessary because xml:lang is the standard way to specify languages."
I18NCORE comment. Discussed at http://www.w3.org/2006/07/17-i18nits-minutes.html#item03 http://www.w3.org/2006/07/21-i18nits-minutes.html#item03 http://lists.w3.org/Archives/Public/public-i18n-its/2006JulSep/0162.html Action: working group to discuss http://lists.w3.org/Archives/Public/public-i18n-its/2006JulSep/0162.html .
Discussed at http://www.w3.org/2006/07/31-i18nits-minutes.html#item04 . Resolution: Agreed to go back to i18n core with the proposals at http://lists.w3.org/Archives/Public/public-i18n-its/2006JulSep/0121.html and http://lists.w3.org/Archives/Public/public-i18n-its/2006JulSep/0162.html . We say that processing of xml:lang is not a normative requirement for an ITS implementation. This resolution should resolve the bugs 3468, 3469, 3480 and 3515.
Action: editors to make the change and Felix to go back to i18n core.
Wait: response sent. See http://lists.w3.org/Archives/Public/public-i18n-its/2006JulSep/0333.html
Closed. Commenters satisfied see: http://lists.w3.org/Archives/Public/public-i18n-its/2006JulSep/0362.html
Summary: The Working Group decided to accept the proposal and to clarify the role of xml:lang for the "language information" data category.