W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > August 2011

[Bug 13921] meta-tag in HTML5 and validation

From: <bugzilla@jessica.w3.org>
Date: Sat, 27 Aug 2011 15:10:31 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1QxKWl-0005PF-Qw@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13921

Eirik <eim@brreg.no> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |eim@brreg.no

--- Comment #2 from Eirik <eim@brreg.no> 2011-08-27 15:10:29 UTC ---
(In reply to comment #1)
> Eirik,
> 
> * Which site (if it's possible to know)
> * Which meta-tags are used?
> * Which commercial products used?
> 
> The last two questions are important because concrete implementations are
> useful to understand in which ways the markup is used.

MondoSearch [1] is the product. Some of the meta-tags are related to page rank,
such as "RANK-DOCUMENT" and "RATING".

I don't have a complete list of all the meta-tags being used by this product,
and I'm really not very familiar with it, but it seems like it also supports
custom meta-tags specific for each site.

>From their brochure [2]
-----------------------
"Users can limit searches to deliver results solely from specific
categories. Categories can be easily created in several ways -
using meta-tags or manual assignments."

"Using custom ranking meta-tags, you can push pages up or
down in the search result list."
-----------------------


But this is just one of many ways that meta-tags have been used over the years
on various sites, especially on intranet sites but also on the Internet.

I don't see custom (meta)data attributes [3] needing such a whitelist ;)
I know data attributes are intended for private use, but meta-tags can also be
added for private use, and they *are* the current mechanism for specifying page
level metadata.

Karl, do you know the reason for wanting to add such a limitation in HTML5?
I've been trying to find a discussion, but without any luck.
Too me it seems like this important breaking of backwards-compatibility has
gone "under the radar" when creating the HTML5 spec.


[1] http://www.surfray.com/products/mondosearch-site-search.html
[2]
http://www.surfray.com/images/stories/files/mondosearch%205.4%20feature%20brochure.pdf
[3] http://dev.w3.org/html5/spec/Overview.html#custom-data-attribute

-- 
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 Saturday, 27 August 2011 15:10:36 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:17 UTC