Re: ItemList

Your code example currently isn't correct according to schema.org's specs.
The expected value for @blogPost is @BlogPosting and the expected value for
@itemListElement is @text.

I guess for now your markup in Microdata of RDFa would require you to
declare multiple @blogPost properties (one on every @BlogPosting) or an
Array in JSON-LD.


2014-05-14 19:34 GMT+02:00 Markus Lanthaler <markus.lanthaler@gmx.net>:

> On Tuesday, May 13, 2014 8:19 PM, Jarno van Driel wrote
> > 2014-05-13 20:02 GMT+02:00 Markus Lanthaler:
> > > I asked this question already while ago but didn't get any answers, so
> > > I'll ask again. How is ItemList intended to be used? Can it be used as
> > > value for arbitrary properties that can be expected to take multiple
> > > values? For example, can I link a http://schema.org/Blog to an
> > > ItemList via the http://schema.org/blogPost property? Or isn't that
> > > how it is intended to be used?
> >
> > Personally I tried using it as for example:
> > - a list of Products on an eCommerce category (Collection)page
> > - a list of JobPostings on an a JobPosting site's CollectionPage
> > - a list of articles related to a NewsArticle
>
> Sorry, but this (and the rest of your email, and the replies from others)
> isn't really an answer to my question.
> Let's keep it concrete: If I have a schema.org/Blog, can I link to the
> blog posts via an ItemList or not? So, is the following snippet an example
> of how ItemList is intended to be used?
>
>    {
>       "@context": "http://schema.org/",
>       "@type": "Blog",
>       "blogPost": {
>         "@type": "ItemList",
>         "itemListElement": [
>           { "@type": "BlogPosting", ... },
>           ...
>         ]
>       }
>    }
>
> In other words, can I as a publisher expect such data to be interpreted
> correctly? Do I as a data consumer have to reasonable expect data of this
> shape?
>
>
> --
> Markus Lanthaler
> @markuslanthaler
>
>
>