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: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Thu, 17 Nov 2011 10:45:45 -0800
Message-ID: <CAAWBYDBoV8hP1VZpwGoyDvbsjU3HhNp6EmfBpJjdoOHUuRY_Jw@mail.gmail.com>
To: "Marat Tanalin | tanalin.com" <mtanalin@yandex.ru>
Cc: Tantek Çelik <tantek@cs.stanford.edu>, Sam Ruby <rubys@intertwingly.net>, public-html@w3.org
2011/11/17 Marat Tanalin | tanalin.com <mtanalin@yandex.ru>:
> 17.11.2011, 22:34, "Tab Atkins Jr." <jackalmage@gmail.com>:
>> 2011/11/17 Marat Tanalin | tanalin.com <mtanalin@yandex.ru>:
>>>  17.11.2011, 22:15, "Tab Atkins Jr." <jackalmage@gmail.com>:
>>>>  Hm, you don't seem to understand my response.  A Microdata property
>>>>  can have *another Microdata item* as its value.  For example, a
>>>>  "review" microdata vocab that uses a "geo" vocab for its location
>>>>  property.  That's indicated by putting @itemprop and @itemscope on the
>>>>  same element.
>>>  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:

<div itemscope itemtype=review>
  ...
  <p itemprop=location itemscope itemtype=geo>
    Located at <span itemprop=lat>37.3610</span>, <span
itemprop=long>-122.0250</span>.
  </p>
</div>

Since this has nothing to do with specifying a non-visible value for a
property, I'm still quite unsure as to what you're expecting of me.

~TJ
Received on Thursday, 17 November 2011 18:46:35 UTC

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