This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Section 4.1 says: "The lang attribute must be processed in the same manner as the xml:lang attribute is in the XHTML+RDFa specification, Section 5.5: Sequence, step #3. The rules for determining the language of a node are specified in the section titled The lang and xml:lang attributes in the HTML5 specification." It's unclear if this means lang and xml:lang must both be processed, only lang must be processed, or processors are always supposed to use the HTML5 definition of "the language of a node". Please clarify which is required. I assume the intent is that wherever XHTML+RDFa says to look at xml:lang, XHTML+RDFa processors must instead use the HTML5 definition of "the language of a node".
RDFA-SPEC-SECTIONS [specifying-the-language-for-a-literal]
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Fixed Change Description: Added text to clarify that the HTML5 definition of "the language of a node" should be used to specify the language of a literal: http://dev.w3.org/cvsweb/html5/rdfa/drafts/ED-rdfa-in-html-20100503/Overview.html.diff?r1=1.2&r2=1.3&f=h """ RDFa Core 1.1 allows for the current language to be specified by the Host Language. In order for RDFa Processors to conform to this specification, they must use the mechanism described in The lang and xml:lang attributes section of the [HTML5] specification to determine the language of a node. """ Rationale: The intent was always to use the same mechanism that HTML5 used to determine the language of a node. This re-wording hopefully clarifies that intent.
mass-move component to LC1