[Bug 12918] I found that you limited the keywords acceptable for the meta-name attribute and for the link-rel attribute. In the specs you use exhaustive lists of allowed keywords. In my opinion you should only suggest keywords. See also http://webhel.blogspot.com/20

http://www.w3.org/Bugs/Public/show_bug.cgi?id=12918

--- Comment #3 from Henri Sivonen <hsivonen@iki.fi> 2011-06-13 07:36:04 UTC ---
(In reply to comment #2)
> Sorry that I was not clear enough. It is okay that there is a wiki where you
> might find the meaning of a keyword.

The spec can be published on a wiki, sure.

> The problem with the suggested mechanism is that the content of a tag (i.e. the
> meta tag) is part of the HTML5 standard. That is curious in my opinion.

That HTML5 presumptively claims all meta keywords (and then relaxing that claim
a bit) is about as curious as HTML5 presumptively claiming all attribute names
(and then relaxing that claim a bit).

> When there is a company with a big name comes with a new keyword (=content) it
> will probably be accepted soon. However when a small company comes with a new
> keyword, all websites which use this content does not follow the HTML5
> standard. That's very strange in my opinion.

Do you have any evidence of big and small companies getting a different
treatment in the registries?

> I understand that it make sense for the meta tag to describe how the keywords
> should be interpreted. As time flows by the used keywords will change. I think
> it doesn´t make sense to change the HTML5 standard everytime a keyword changes.
> By making the wiki part of the standard this will be the case.

Why is that a problem? Is it a problem that the "HTML5 standard" "changes" if a
new language subtag for a natural language is added to the IANA language subtag
registry?

-- 
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 Monday, 13 June 2011 07:36:10 UTC