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: Fri, 18 Nov 2011 19:48:53 +0400
To: Philip Jägenstedt <philipj@opera.com>
Cc: Tab Atkins Jr. <jackalmage@gmail.com>, Tantek Çelik <tantek@cs.stanford.edu>, Sam Ruby <rubys@intertwingly.net>, public-html@w3.org
Message-Id: <97001321631333@web60.yandex.ru>
The only point of @itempropvalue is to replace redundant DATA element. If we don't need DATA element, then the @itempropvalue is probably unneeded too.

So the question is: _either_ DATA element _or_ @itempropvalue attribute. If someone states that @itempropvalue is confusing, then he should provide an example where DATA element in the same situation is not confusing. Otherwise, appropriate discussion branch is pointless.


18.11.2011, 19:15, "Philip Jägenstedt" <philipj@opera.com>:
> On Fri, 18 Nov 2011 15:59:43 +0100, Marat Tanalin | tanalin.com
> <mtanalin@yandex.ru> wrote:
>
>>  Philip, thanks for your response, but this is incomplete and unclear
>>  without correlative examples using DATA elements instead of
>>  @itempropvalue.
>
> The main point is that it is not obvious at all what itempropvalue does in
> these two cases, thus the questions. The alternative might not involve
> <data> at all, but if you say what itemValue should be in both cases I can
> write out the itempropvalue-less solution.
>
> --
> Philip Jägenstedt
> Core Developer
> Opera Software
Received on Friday, 18 November 2011 15:49:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:41 GMT