- From: <bugzilla@jessica.w3.org>
- Date: Sun, 21 Aug 2011 18:45:29 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13469 --- Comment #6 from Manu Sporny <msporny@digitalbazaar.com> 2011-08-21 18:45:28 UTC --- > 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. I don't understand why you wrote the first and second sentence above - please elaborate on what you mean. The third sentence seems to be a layer violation - what a higher-level application does with Microdata and non-Microdata on the page has nothing to do with the Microdata processing rules. I don't remember reading anything that limited what a higher-level application does with the Microdata in a page in the Microdata spec. Do you have a link to that language? >> 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. Having a WYSIWYG editor that highlighted the exact text that is associated with the word "fourteen" and the data "14" retrieved from the page would be helpful. Having a spider understand that the on-page data doesn't deviate from the "hidden" data in the page would also be useful. The fact remains that <meta> does not allow you to do that. The resolution does not address my concerns, but I will not be pursuing the matter further as this shortcoming has been raised repeatedly and the answer has always been the same. -- 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 Sunday, 21 August 2011 18:45:33 UTC