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

Re: noted 3 issues re: time/data (was Re: minutes for HTML WG f2f, 2011-11-04, part 1)

From: Marat Tanalin | tanalin.com <mtanalin@yandex.ru>
Date: Mon, 14 Nov 2011 21:17:25 +0400
To: Tab Atkins Jr. <jackalmage@gmail.com>
Cc: (wrong string) Çelik <tantek@cs.stanford.edu>, Sam Ruby <rubys@intertwingly.net>, public-html@w3.org
Message-Id: <356121321291045@web65.yandex.ru>
14.11.2011, 19:38, "Tab Atkins Jr." <jackalmage@gmail.com>:

>> š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.
>
> That doesn't seem obvious to me.

What exactly is unobvious for you? (What exact of the two syntaxes, what exactly in each of them.)

>> š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).
>
> Do you understand what it means to have @itemprop and @itemscope on
> the same element?

Unfortunately, not quite. (If such their using is really needed and quite clear for you, then hopefully it would be not very hard for you to explain this briefly.)

Anyway, if the spec is too hard to understand (and it _is_ as for specifying 'itemscope' and 'itemprop' for the same element), then it should be simplified, isn't it? ;-)

Thanks.
Received on Monday, 14 November 2011 17:18:07 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:28 UTC