- From: Dan Brickley <danbri@danbri.org>
- Date: Mon, 14 May 2012 11:03:46 +0200
- To: Егор Антонов <elderos@yandex-team.ru>, Adrian Giurca <giurca@tu-cottbus.de>, Guha <guha@google.com>, "public-vocabs@w3.org" <public-vocabs@w3.org>
On 14 May 2012 10:50, Егор Антонов <elderos@yandex-team.ru> wrote: > I don't see any sense to include full class hierarchy in path. > It proposed something like this: > > <div itemscope itemtype="http://schema.org/Sculpture/" > > <span itemprop="awards"> some award </span> > ... > </div> > > the short form is transformed into type + property name [...] This is one of those topics where there is no obvious right answer, only tradeoffs. Can we agree to disagree here, and accept that for the purpose of interchange and standards schema.org uses 'http://schema.org/' + propertyname, following the conventions of RDFa Lite and other W3C specs? Internally in various systems we are free to record all kinds of extra information, including one or more type(s) associated with the property occurrence. cheers, Dan
Received on Monday, 14 May 2012 09:04:19 UTC