- From: Marat Tanalin | tanalin.com <mtanalin@yandex.ru>
- Date: Mon, 14 Nov 2011 12:49:33 +0400
- To: Tab Atkins Jr. <jackalmage@gmail.com>
- Cc: Tantek Celik <tantek@cs.stanford.edu>, Sam Ruby <rubys@intertwingly.net>, public-html@w3.org
14.11.2011, 12:23, "Tab Atkins Jr." <jackalmage@gmail.com>: > On Mon, Nov 14, 2011 at 12:09 AM, Marat Tanalin | tanalin.com > <mtanalin@yandex.ru> wrote: >> šLet's consider an example: >> š<data itemprop="foo" value="bar">ipsum</data> >> >> šIt's unclear why this is not sufficient instead: >> š<span itemprop="foo" value="bar">ipsum</span> > > Please tell me what the value of the "foo" property is on the following element: > > <span itemprop="foo" itemvalue="bar" itemscope> > > Is it the string "bar"? šOr is it the Microdata item started on the element? AFAIK, there is no 'itemvalue' html attribute in the current spec. Then what does it mean in your example? If to consider syntax with 'itempropvalue' attribute (as I've mentioned earlier and in the bug 14679 comment 3): <span itemprop="foo" itempropvalue="bar" itemscope> or CSS-like one I've proposed later: <span itemprop="foo: bar" itemscope> then 'bar' is obviously value of this span as property. > Microdata already has three places that a value can possible come from > - the textual content, the value of an attribute on certain elements, > and the Microdata item started on the element. šThere's a somewhat > intuitive ordering to these, but it's still right on the border of > being too complex for its own good. Then, microdata part of the spec probably should be simplified. In particular (but not limited to), it may make sense to disallow specifying 'itemscope' and 'itemprop' for the same element simultaneously (if it's currently really allowed).
Received on Monday, 14 November 2011 08:50:09 UTC