- From: <martin.hepp@ebusiness-unibw.org>
- Date: Tue, 13 May 2014 20:48:33 +0200
- To: Jason Douglas <jasondouglas@google.com>
- Cc: Markus Lanthaler <markus.lanthaler@gmx.net>, W3C Web Schemas Task Force <public-vocabs@w3.org>
If I remember correctly, the proposed modification would make ItemList more generally usable for any kind of ordered collection, so we would just have to remove the subtype relationship to CreativeWork. On 13 May 2014, at 20:20, Jason Douglas <jasondouglas@google.com> wrote: > ItemList inherits from CreativeWork and I believe is intended to be for "editorialized lists". Top 10 lists, etc. A list of Breadcrumbs or BlogPosts seem in scope, but that's not currently how the schema is connected. > > As mentioned in other threads, I think we need a different mechanism for collections more generally. Probably something more like the approach that was taken with Roles. > > On Tue May 13 2014 at 11:04:51 AM, Markus Lanthaler <markus.lanthaler@gmx.net> wrote: > On Tuesday, May 13, 2014 6:56 PM, Dan Brickley wrote: > > Yes, let's get ItemList back on track. We got this far previously: > > > > https://www.w3.org/wiki/WebSchemas/ItemList > > 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? > > -- > Markus Lanthaler > @markuslanthaler > > > >
Received on Tuesday, 13 May 2014 18:48:54 UTC