W3C home > Mailing lists > Public > www-validator@w3.org > August 2011

RE: HTML5 custom meta element name attribute values should be a warning

From: Ryan Foster <rrf5000@psu.edu>
Date: Mon, 8 Aug 2011 13:08:49 -0400
To: "'Michael[tm] Smith'" <mike@w3.org>
Cc: <www-validator@w3.org>
Message-ID: <006001cc55ed$d75d7c60$86187520$@edu>
Indeed, support-email is not a registered keyword, and is meant for an
intranet application, not a public consuming application.  I did not realize
that the HTML5 spec was so strict in this regard.  Even the HTML4 "reply-to"
keyword is not defined in the HTML5 spec, or I could have used that.

I read the part of the spec that stated:
Extensions to the predefined set of metadata names may be registered in the
WHATWG Wiki MetaExtensions page.

And I took that to mean that it was merely a suggestion and not a
requirement.  However, further down it does state:
Conformance checkers must use the information given on the WHATWG Wiki
MetaExtensions page to establish if a value is allowed or not: values
defined in this specification or marked as "proposed" or "ratified" must be
accepted, whereas values marked as "discontinued" or not listed in either
this specification or on the aforementioned page must be rejected as

So the Validator follows the spec.  I do realize that I can also choose to
ignore the error so long as it functions the way that I intended, but I
think that the spec is a bit harsh in this case.  I think that values not
explicitly defined in the spec should merely cast a warning instead of an
error.  I may try to file a bug report on the spec later.

Thanks for your reply!


-----Original Message-----
From: Michael[tm] Smith [mailto:mike@w3.org] 
Sent: Monday, August 08, 2011 11:48 AM
To: Ryan Foster
Cc: www-validator@w3.org
Subject: Re: HTML5 custom meta element name attribute values should be a

Ryan Foster <rrf5000@psu.edu>, 2011-08-08 10:37 -0400:

> While validating some HTML Doctyped as HTML5 with the W3C Markup Validator
> (http://validator.w3.org), I came across the following error:
> Line 6, Column 35: Bad value version for attribute name on element meta:
> Keyword version is not registered. 
> <meta name="version" content="1.0">
> Line 7, Column 52: Bad value support-email for attribute name on element
> meta: Keyword support-email is not registered. 
> <meta name="support-email" content="test@email.com">
> I believe this is the relevant section of the HTML5 spec:
> ther-metadata-names

Right. That section specifies that keywords are only valid if they are
registered. and "support-email" is not registered.

As the full error message emitted by the validator indicates, you can
register metadata names on the WHATWG wiki yourself.


> When I validate using the HTML 4.01 Strict Doctype, the errors aren't
> Is there a reason that this warrants an error instead of a warning?

The reason is that the HTML5 spec has more requirements on attribute values
than the HTML4 spec does, with the rationale generally being that alerting
users to bad and/or irrelevant attribute values is a good thing.

In the case of the "support-email" name value, if there is no spec that
defines what "support-email" means, then it's less likely that there are
any public consuming applications that actually process it and do anything
useful with it interoperably, and we want you to know that. It's then up to
you to do whatever you want with that knowledge.

> Is this an issue with the HTML specification(s) or with the W3C
> Validator?

It's a requirement in the HTML5 spec. If you disagree that it should be a
requirement, the way to let that be known would be to file a bug against
the HTML5 spec:



Michael[tm] Smith
Received on Monday, 8 August 2011 17:09:14 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 14:18:04 UTC