- From: Marat Tanalin | tanalin.com <mtanalin@yandex.ru>
- Date: Thu, 17 Nov 2011 23:02:51 +0400
- To: Tab Atkins Jr. <jackalmage@gmail.com>
- Cc: Tantek Celik <tantek@cs.stanford.edu>, Sam Ruby <rubys@intertwingly.net>, public-html@w3.org
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_.
Received on Thursday, 17 November 2011 19:03:28 UTC