W3C home > Mailing lists > Public > public-vocabs@w3.org > August 2014

Re: ItemList examples

From: Gregg Kellogg <gregg@greggkellogg.net>
Date: Wed, 6 Aug 2014 20:42:31 -0700
Cc: vtardif@google.com, danbri@google.com, giurca@tu-cottbus.de, public-vocabs@w3.org
Message-Id: <85F101D4-9255-4083-8E97-BADD75F315C6@greggkellogg.net>
To: Jason Douglas <jasondouglas@google.com>
On Aug 6, 2014, at 7:49 PM, Jason Douglas <jasondouglas@google.com> wrote:

> I suppose the backward-compatible way to do it would be to:
> Create a new type (Collection?)
> Change the domain of the structural properties of ItemList to Collection
> Make ItemList inherit from Collection as well as CreativeWork
> That leaves ItemLiist as the editorial thing, so all existing markup would still be semantically unchanged.

I think Collection makes a lot of sense. To me, ItemList sounds like a curated list, whereas Collection sounds like a basic grouping.

I would still like to see some clarification on referenced Collections, and a means of paginating Collections. Hydra does this by adding first/last/next/prev properties in addition to totalItems.

Some Collections could contain thousands of items (UserLikes, Comments, Events, ...), so having a way to split these between different resources would be useful.

+1 to making ItemList a subclass of both Collection and CreativeWork.

Having Collection be a subtype of Role also makes sense (http://lists.w3.org/Archives/Public/public-vocabs/2014Jun/0279.html).

Gregg 

> -jason
> 
> On Wed Aug 06 2014 at 6:18:10 PM Vicki Tardif Holland <vtardif@google.com> wrote:
> On Wed, Aug 6, 2014 at 4:26 PM, Dan Brickley <danbri@google.com> wrote:
> I had a look into this last time you mentioned it. I agree that there
> is a need for something that's a pure data structure, and something
> else that carries the CreativeWork aspect. Are we OK with changing the
> meaning of ItemList out from under the feet of existing publishers? As
> far as I could see it was mostly used with Thing-properties, but there
> were some sites using 'about', 'author' properties.
> 
> I'm quite liking the Role-like idiom. If we're going to use it for
> Role, it probably makes sense here too.
> 
> I'm for creating two types:  a basic ItemList separate from CreativeWork and an EditedList that inherits from both CreativeWork and the basic ItemList. Otherwise, we are going to keep creating strange semantics to preserve the existing semantics.
> 
> - Vicki
> 
> 
> Vicki Tardif Holland | Ontologist | vtardif@google.com 
>  


Received on Thursday, 7 August 2014 03:43:04 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:49:34 UTC