On Thu, 17 Nov 2011 20:02:51 +0100, Marat Tanalin | tanalin.com <mtanalin@yandex.ru> wrote: > 17.11.2011, 22:45, "Tab Atkins Jr." <jackalmage@gmail.com>: >>>>> It would probably be useful if you provide a concrete descriptive >>>>> example showing how DATA element resolve this situation elegant and >>>>> nonconfusing way. Thanks. >>>> I... don't understand. What situation? >>> Situation that you describe as quite abstract example of why >>> @itemscope and @itempropvalue would be confusing. Then it's logical >>> for you to provide a _concrete_ markup (HTML code) example where DATA >>> element is nonconfusing for marking up same data ('geo', etc.). >> >> I still don't understand. The <data> element is irrelevant in the >> situation you're talking about. You would mark up such a thing as: > > Well, let's try to simplify and reformulate. > > There is DATA element proposal. > There is @itempropvalue proposal. > > You say that @itempropvalue could be confusing. > > Then it would be useful that you provide a _concrete_ example where > @itempropvalue _is_ confusing while DATA element is _not_. 1. <img src="pic.png" itemprop="img" itempropvalue="pic.jpg"> What is the value of the property "img"? Is it resolved as a URL or is it a plain text property? (src and href attributes are resolved as URLs in microdata, so itemValue would be something like "http://example.com/pic.png" if itempropvalue were not there.) 2. <div itemscope itemtype=review> ... <p itemprop=location itemscope itemtype=geo itempropvalue="37.3610,-122.0250"> Located at <span itemprop=lat>37.3610</span>, <span itemprop=long>-122.0250</span>. </p> </div> What is the value of the property "location"? Is it a plain text property "37.3610,-122.0250" or the subitem with type "geo" and two properties "lat" and "long"? None of these questions would arise with a <data> element, simply because you don't have the extra attribute to overload itemValue with. -- Philip Jägenstedt Core Developer Opera SoftwareReceived on Friday, 18 November 2011 09:30:48 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:41 GMT