12793 2011-05-26 01:30:44 +0000 @scheme attribute conflicts with Dublin Core encoding scheme declarations 2011-11-24 03:07:32 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified PC Windows XP RESOLVED NEEDSINFO P2 normal --- 1 eahostetter contributor hsivonen ian jfoliot julian.reschke mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 48833 0 eahostetter 2011-05-26 01:30:44 +0000 "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. 48839 1 julian.reschke 2011-05-26 06:23:52 +0000 (In reply to comment #0) > "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: > ... I think you're confusing meta/@schema with meta/@charset. Other than that, I agree that @scheme should be kept, along with profile and related constructs. 48847 2 hsivonen 2011-05-26 13:49:50 +0000 (In reply to comment #0) > "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" /> What consuming software are you writing this data for? What piece of software does something with the scheme attribute? > 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 Please see http://w3fools.com/ 48849 3 jfoliot 2011-05-26 16:49:55 +0000 (In reply to comment #2) > > What consuming software are you writing this data for? What piece of software > does something with the scheme attribute? > There are a large number of tools that interact with Dublin Core metadata: http://dublincore.org/tools/ Has this Working Group had any discussions with DCMI? Perhaps now that we are at Last Call we will hear from subject matter experts from that realm? 48850 4 julian.reschke 2011-05-26 17:08:10 +0000 (In reply to comment #3) > ... > Has this Working Group had any discussions with DCMI? Perhaps now that we are > at Last Call we will hear from subject matter experts from that realm? http://lists.w3.org/Archives/Public/public-html/2010May/0253.html 48852 5 hsivonen 2011-05-26 18:20:25 +0000 (In reply to comment #3) > (In reply to comment #2) > > > > What consuming software are you writing this data for? What piece of software > > does something with the scheme attribute? > > > > There are a large number of tools that interact with Dublin Core metadata: > http://dublincore.org/tools/ Does any of them fail if the input doesn't have the scheme attribute? If they do fail, what's the failure mode? 53487 6 mike 2011-08-04 05:14:20 +0000 mass-move component to LC1 60195 7 mike 2011-11-20 15:06:30 +0000 Elizabeth, John, see comment #5 from Henri: > (In reply to comment #3) > > There are a large number of tools that interact with Dublin Core metadata: > > http://dublincore.org/tools/ > > Does any of them fail if the input doesn't have the scheme attribute? If they > do fail, what's the failure mode? This bug is waiting on a response to that question. 60418 8 ian 2011-11-24 02:34:45 +0000 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: Did Not Understand Request Change Description: no spec change Rationale: see comment 7