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 SoftwareReceived on Friday, 18 November 2011 15:49:29 UTC
This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:16:18 UTC