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 #41 of i18nCore comments: http://www.w3.org/International/reviews/0606-its/ Sections 5.1, 5.3.2: We feel it is not acceptable that the markup proposed by ITS makes no mention of ways to define language for the content of ITS elements. At the very least, a proposed approach should be described in text, with xml:lang being held up as the most standard way to do things. Such text could say something like: "xml:lang should be available on the span element, unless the format into which ITS is being integrated has an attribute that fulfills the role of xml:lang, in which case that attribute should be available on the span element." And similar for other elements defined for ITS. ITS can point out that xml spec does define xml:lang in a global rules kind of way.
Proposal for a resolution made at http://www.w3.org/2006/07/21-i18nits-minutes.html#action03 . Action: working group to decide about the proposal.
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 with it.
Wait: response sent. See http://lists.w3.org/Archives/Public/public-i18n-its/2006JulSep/0332.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 that xml:lang is available in the non-normative ITS schemas at the desired elements.