This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 16520 - Don't indicate that XML MIME types *requires* xml:lang
Summary: Don't indicate that XML MIME types *requires* xml:lang
Status: CLOSED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML+RDFa (editor: Manu Sporny) (show other bugs)
Version: unspecified
Hardware: PC All
: P3 normal
Target Milestone: ---
Assignee: Manu Sporny
QA Contact: HTML WG Bugzilla archive list
URL: http://dev.w3.org/html5/rdfa/#specify...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-26 08:13 UTC by Leif Halvard Silli
Modified: 2012-08-19 21:21 UTC (History)
5 users (show)

See Also:


Attachments

Description Leif Halvard Silli 2012-03-26 08:13:46 UTC
The HTML+RDFa spec says:

]] If an author is editing an HTML fragment and is unsure of the final encapsulating MIME type for their markup, it is suggested that the author specify both lang and xml:lang [[

    NIT: "If an author is [snip] for their markup".
Correct: "If an author is [snip] for his/her markup".

ISSUE: The advice proliferate the belief that XML mime types *need* xml:lang. But it is only if they don't understand XHTML that they *need* xml:lang. They might very well not understand XHTML. But is that related to the MIME type?

The only use case I have heard for xml:lang is XML authoring tools - thus, not exactly "the final encapsulating MIME type". XML parsers of the Web browser kind (IE/Webkit/Opera/Gecko) do understand the @lang attribute. (Though there might be legacy versions which don't.) And e.g. the XHTML+RDFa DOCTYPE supports both @lang and @xml:lang.

Are there any *real* reasons for using both attributes - unrelated to authors' fears and feelings? Such as legacy RDFa parsers? Or specific XML authoring tools? Or specific consumers?
Comment 1 Manu Sporny 2012-08-19 21:16:42 UTC
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/Answered

Change Description: 

Fixed the nit you had (s/their/his\her/)

Rationale:

The nit submitted was correct.

> They might very well not understand XHTML. 
> But is that related to the MIME type?

No, it doesn't have to always be related to MIME type. RDFa processors often put themselves into XML or non-XML mode when processing, one of the ways that they can do this is based on MIME type. In non-XML mode, they shouldn't pay attention to xml:lang. So, if an author marks up their snippet using "xml:lang" and that snippet shows up in an HTML5 document processed in non-XML mode, then the "xml:lang" value would be ignored. This is why we tell authors to specify both.