- From: <bugzilla@jessica.w3.org>
- Date: Thu, 26 May 2011 01:30:45 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12793 Summary: @scheme attribute conflicts with Dublin Core encoding scheme declarations Product: HTML WG Version: unspecified Platform: PC OS/Version: Windows XP Status: NEW Severity: minor Priority: P2 Component: HTML5 spec (editor: Ian Hickson) AssignedTo: ian@hixie.ch ReportedBy: eahostetter@gmail.com QAContact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-wg-issue-tracking@w3.org, public-html@w3.org "The @scheme attribute of the meta element has been made obsolete and 'must not be used by authors'" (Source: http://efoundations.typepad.com/efoundations/2010/02/html5-metadata-and-dublin-core.html). The HTML5 specification states that @scheme must only be declared once per page, for character encoding. This poses a problem for those using the Dublin Core specification for metadata in HTML5, in which encoding schemes for syntax and vocabulary must be declared, per property as appropriate. Examples: <meta name="dcterms.modified" scheme="W3CDTF" content="2011-03-22" /> <meta name="dcterms.issued" scheme="W3CDTF" content="2010-03-15" /> <meta name="dcterms.language" scheme="ISO639-2" content="eng" /> >From what I can tell from the HTML5 spec, this has not changed. Nor has it changed in the W3Schools HTML5 online course: http://www.w3schools.com/html5/tag_meta.asp The Government of Canada has opted to use the "title" attribute in place of the scheme attribute to declare encoding schemes, on an interim basis, as part of the Web Experience Template. A more permanent way to declare encoding schemes is desirable. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Thursday, 26 May 2011 01:30:46 UTC