- From: Dan Scott <dan@coffeecode.net>
- Date: Wed, 21 May 2014 14:21:26 -0400
- To: Jarno van Driel <jarnovandriel@gmail.com>
- Cc: Jocelyn Fournier <jocelyn.fournier@gmail.com>, Dan Brickley <danbri@google.com>, W3C Web Schemas Task Force <public-vocabs@w3.org>
On Wed, May 21, 2014 at 02:04:20PM +0200, Jarno van Driel wrote: >I was wondering, can an entity also have multiple @about properties? > >I ask because when chaining multiple entities to a WebPageElement, to me it >seems the following is the logical thing to do: > ><body itemscope itemtype="http://schema.org/WebPage"> > ... > <div itemprop="hasPart" itemscope itemtype="http://schema.org/WPSideBar"> > <div itemprop="about" itemscope itemtype="http://schema.org/ContactPoint">...</div> > <div itemprop="about" itemscope itemtype="http://schema.org/ItemList">...</div> > </div> > ... ></body> > >Or would @hasPart or @mentions be prefered over @about? I'm not going to offer any advice about whether "hasPart" or "mentions" might be preferred here, but you can certainly have multiple "about" properties for a single entity. See the example for http://schema.org/MedicalScholarlyArticle - "about" is used twice, because the article is about a type of drug and about a type of medical condition. The cardinality of schema.org properties appears to be a FAQ dating back to at least 2011 (http://www.w3.org/2011/webschema/track/issues/5); we should probably add an explicit statement to http://schema.org/docs/gs.html or http://schema.org/docs/faq.html (or both) saying that you can, in general, repeat properties in schema.org entities as necessary.
Received on Wednesday, 21 May 2014 18:21:58 UTC