This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
meta/@name=keywords should be specified in the HTML5 spec and made conforming; it has been in HTML4 and is widely used. See related discussion in http://www.w3.org/Bugs/Public/show_bug.cgi?id=6853 (which was about restoring its state to "Proposal" in http://wiki.whatwg.org/wiki/MetaExtensions).
It's presence in HTML4 is irrelevant. Why should it be in HTML5 proper and not an externally specified value registered with the registration mechanism?
There's simply no good reason to treat it different from other values defined in HTML 4, except for (I guess) ideology. So, on the other hand, why don't we move the three definitions that are part of HTML5 into separate specs as well?
It's not treated any differently than any other values in HTML4. I don't think I've ever even looked at the list of what values HTML4 defines since starting work on HTML5. This has nothing to do with ideology (what ideology?). HTML5 was written from scratch. We could move the three definitions in the HTML5 spec to another spec, but they are all significantly more useful than "keywords", so there are stronger reasons to keep them in the spec. For instance, "generator" affects the behaviour of validators, "application-name" has normative conformance criteria for UAs, and "description" is actually used by all manner of UAs. Since the only reason you have provided for defining this feature is that some other document once defined it, I haven't added it. Please reopen the bug if there are more compelling reasons.
(In reply to comment #3) > ... > This has nothing to do with ideology (what ideology?). HTML5 was written from > scratch. > ... The belief that doing so is the right thing to do is IMHO ideological. > We could move the three definitions in the HTML5 spec to another spec, but they > are all significantly more useful than "keywords", so there are stronger > reasons to keep them in the spec. For instance, "generator" affects the > behaviour of validators, "application-name" has normative conformance criteria > for UAs, and "description" is actually used by all manner of UAs. > > Since the only reason you have provided for defining this feature is that some > other document once defined it, I haven't added it. Please reopen the bug if > there are more compelling reasons. > ... That is incorrect; another reason I have provided is that it is widely used; and there's no good reason to make these documents non-conforming.
Actually, http://code.google.com/webstats/2005-12/metadata.html lists "keywords" as the most frequently used value for "name".
moved to HTML WG Tracker issue 79 http://www.w3.org/html/wg/tracker/issues/79
This bug predates the HTML Working Group Decision Policy. If you are satisfied with the resolution of this bug, 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 This bug is now being moved to VERIFIED. Please respond within two weeks. If this bug is not closed, reopened or escalated within two weeks, it may be marked as NoReply and will no longer be considered a pending comment.
The HTML WG decided by Call for Consensus to adopt the following Change Proposal to make <meta name="kewyords"> conforming and define its semantics. Please apply the appropriate edits to the spec. http://lists.w3.org/Archives/Public/public-html/2010Feb/0162.html
Requesting expedited processing on behalf of the WG.
Checked in as WHATWG revision r4860. Check-in comment: W3C HTML WG ISSUE-79 change proposal merge http://html5.org/tools/web-apps-tracker?from=4859&to=4860
Checked in as WHATWG revision r4861. Check-in comment: Fix the text added for ISSUE-79 to use appropriate terminology and to fit the style of the specification. http://html5.org/tools/web-apps-tracker?from=4860&to=4861
Please verify that the changes I made to the proposed text are acceptable.
The text changes were approved by Julian and acceptably implement the WG decision.
*** Bug 6853 has been marked as a duplicate of this bug. ***