W3C home > Mailing lists > Public > public-vocabs@w3.org > December 2011

Re: using web-scale identifiers in microdata

From: Thad Guidry <thadguidry@gmail.com>
Date: Wed, 21 Dec 2011 12:15:33 -0600
Message-ID: <CAChbWaPbCZTY-isrGXEnCqPq-hfu5bA9dvTZVamU_f7ZQP=Phg@mail.gmail.com>
To: public-vocabs <public-vocabs@w3.org>

> Or could you just do something like the following to use @itemid? I
> don't know what value to give @itemtype below, since what I want to
> say is that this "Oregano" item is actually the same as a controlled
> term from an external vocabulary. This seems like more nesting and
> complication for consumers than you might want just to make this kind
> of link.
> <div itemscope itemtype="http://schema.org/Recipe">
>  <span itemprop="name">Oregano Bread</span>
>  <span itemprop="ingredients" itemscope
> itemtype="http://schema.org/Term"
> itemid="http://dbpedia.org/resource/Oregano"><span
> itemprop="name">Oregano</span></span>
> ...
> </div>
> I have a lot a terms (subject headings and the like) that I could link
> to, but since the main consumer of the microdata is the search
> engines, I want to make sure they understand what I'm providing them.
> It seems keeping something simple and extractable as text would be
> better in this case, but maybe, as Martin Hepp's example is, they
> would both understand how to handle a value of
> "http://dbpedia.org/resource/Oregano" and not penalize the page for
> this being hidden content?
> Jason
> [1] http://lists.w3.org/Archives/Public/public-vocabs/2011Nov/0004.html
> [2]
> http://foolip.org/microdatajs/live/?html=%3Cdiv%20itemscope%20itemtype%3D%22http%3A%2F%2Fschema.org%2FRecipe%22%3E%0A%20%3Cspan%20itemprop%3D%22name%22%3EOregano%20Bread%3C%2Fspan%3E%0A%20%3Clink%20itemprop%3D%22ingredients%22%20href%3D%22http%3A%2F%2Fdbpedia.org%2Fresource%2FOregano%22%2F%3EOregano%0A%3C%2Fdiv%3E
Identifiers (realist perspective identifiers) are really what you need.
 Oregano means different things to different folks in different parts of
the world.  A Thing With Many Names with 1 identifier is a good approach.
 I am not sure how a web developer from Puerto Rico designing a culinary
site would do this in microdata either.

Your example of Oregano, the ingredient from a realist perspective "The
dried leaves of the plant species Origanum vulgare" is not the same as
Oregano, the ingredient from a realist perspective "The dried leaves of the
plant species Plectranthus amboinicus, that is also commonly called
'Orégano' or 'Orégano Brujo' or 'Cuban Oregano' if you live in Cuba, Puerto
Rico, etc."  Microdata deals with generalist views very easily, but I have
yet to see Microdata deal with things specifically within a realist
perspective, which seems straightforward with RDFa.

Received on Wednesday, 21 December 2011 18:16:10 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:48:43 UTC