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: Tue, 09 Aug 2011 00:37:30 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1QqaK2-00053u-IQ@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13469

Manu Sporny <msporny@digitalbazaar.com> changed:

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

--- Comment #4 from Manu Sporny <msporny@digitalbazaar.com> 2011-08-09 00:37:29 UTC ---
The first part of your response misses the point of the use cases that I
described. The goal isn't to remove markup tags, the goal is to override one
set of text with another and be able to specify the DOM element whose contents
are overridden.

"<data itemprop=a value=foo>quux</data>"

Is that valid HTML5 markup? I couldn't find the data element nor could I find
the rules for processing the DATA element in the Microdata specification. If
links to those two things exist, that element and respective Microdata
processing rules address the use case I was concerned about.

"1. What is the use case for this? It doesn't seem necessary. There is nothing
in microdata like this currently (other than top-level microdata items being
associated with a particular element); why would adding this help?"

It would enable two use cases:

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.

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.

"2. This is already possible, just make sure the vocabulary defines the units.
(We learnt from scheme="" on <meta> that having this associated with the data
rather than the definition of the property is bad design.)"

There are issues with this approach, see:

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13465#c4

"3. The assertion in this reason seems false. It does not permit such checking
as far as I can tell. If it did, the whole feature wouldn't be necessary at
all."

I explain this a bit more above - do you understand the intent now?

-- 
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 Tuesday, 9 August 2011 00:37:32 UTC

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