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

[Bug 13469] Enable Web page authors to override text/IRI content

From: <bugzilla@jessica.w3.org>
Date: Mon, 15 Aug 2011 04:44:56 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Qsp2m-0001dY-8w@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13469

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |WONTFIX

--- Comment #5 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-08-15 04:44:55 UTC ---
<data> is a proposal, see bug 13240.

> 1. Allow search engine companies to determine if the data from the text
> override on the page matches the text that was overridden, thus providing an
> additional tool to combat nasty SEO practices. Hidden data is bad, so at least
> allowing a spider to examine if the hidden data and the non-hidden data match
> up is a good thing. For example if the value "14" is the override and
> "fourteen" is the overridden text, then a spider can reason that a) the data
> matches the text and b) the text was shown on the page at some point so is less
> likely to be data spam.

This is false. If it was possible for spiders to do this kind of reasoning in
the first place, then spiders wouldn't need microdata. Indeed if tools were to
decide whether or not to trust the microdata in a page based on non-microdata
on the page, that tool would be in violation of the microdata processing rules.


> 2. It would allow debuggers, like the one built into Google Chrome, to
> highlight the sections of a page that particular pieces of data came from down
> to the exact span of text on the page.

The piece of data in the proposal would come from the attribute, not the
element's contents. It certainly would allow a development tool to highlight
the (possibly unrelated) contents of the element that happened to have the
attribute, but that's not especially more useful than highlighting a <meta>
element immediately before that same content, which is possible today.


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: Rejected
Change Description: no spec change
Rationale: Use cases are still not compelling.

-- 
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, 15 August 2011 04:45:01 UTC

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