Re: Collection / Container / List (+Pagination)

Yes indeed I did.

In the libraries, archives, museums, galleries and associated worlds collections & lists most often come into existence for a creative reason - A library collection, a reading list for educational / personal / entertainment reasons, a collection of museum artefacts for permanent or short period needs (traveling exhibitions, etc.) to name but a few.  Whereas containers seem not to need the creative aspect - they are more like a specialisation of Product.

In an archive you may have a folder of letters, in an box, on a shelf in the collection which is archived.   In this case, each letter would be a CreativeWork which a folder ‘contains’ and also ‘isPartOf’ the collection.

There a few aspects to this that I have been looking at recently, and was going to bring to the list in the near future - this is coming from the needs of describing archives, both physical and digital, suggesting the following in schema.org<http://schema.org>

New types:

     *   Container  - a subType of Product
     *   BoxContainer - subType of Container
     *   FolderContainer - subType of Container
     *   Shelf - subType of Container
     *   Collection - subType of CreativeWork

New/changed properties:

     *   contains - Domain: Container. Range: Thing
     *   containedIn - Add Product & CreativeWork to domain. Add Container to range
     *   hasPart - change range to Thing (from CreativeWork)

This may also be relevant to the recent ' Modeling question: folders (directories) and files’ thread.  A file/directory in a file system could be considered a container.

There is an argument for isPartOf, hasPart, contains, containedIn to be properties for Thing, which would make this even easier, but proposing new Thing level properties can be controversial.

The above all works with the aid of useful CreativeWork properties ‘hasPart' & ‘isPartOf', plus [new] Container properties ‘contains' & ‘containedIn’.  The problem then comes when the parts or the contained things need to be referenced in a particular order.  This is where I would look to multi-typing to solve the problem.  Proposing, if the above is accepted:


  *   CuratedList - a subtype of both Collection and ItemList
  *   OrderedContainer - Either:
     *   subtype of both Container and ItemList, or
     *   Assume that all containers could be ordered in which case make Container a subtype of Product and ItemList

~Richard

On 6 Mar 2015, at 14:30, Jarno van Driel <jarnovandriel@gmail.com<mailto:jarnovandriel@gmail.com>> wrote:

If I remember correctly during the discussions surrounding ItemList Richard Wallis mentioned 'curated' lists as well and what came out of that was that a collection could be expressed by using an multi-type entity like [ItemList, CreativeWork] as the having access to CreativeWork's properties is a 'must' to be able to express a curated list.

Unfortunately I couldn't find any reference to that part of the discussion nor whether an MTE like the one I mentioned is how Collections should be expressed. Maybe Richard could say something about this as well?

2015-03-06 14:58 GMT+01:00 Karen Coyle <kcoyle@kcoyle.net<mailto:kcoyle@kcoyle.net>>:
Add the Open Archives Initiative's Object Reuse and Exchange to your list:

http://www.openarchives.org/ore/1.0/datamodel


This is how collections are encoded in the Europeana Data Model

http://pro.europeana.eu/share-your-data/data-guidelines/edm-documentation


kc


On 3/6/15 12:40 AM, ☮ elf Pavlik ☮ wrote:
Hello,

I would like to ask for some feedback on how we design and use
collections. For now I will gather it on Social WG wiki but we can
easily move it to Web Schemas wiki!
https://www.w3.org/wiki/Socialwg/Collection_Comparison


What I already could find:

Linked Data Platform
* http://www.w3.org/TR/ldp/#ldpc (W3C TR)
* http://www.w3.org/TR/ldp-paging/ (W3C CR)

Activity Streams 2.0
* http://www.w3.org/TR/activitystreams-core/#collections (W3C FPWD)
* http://www.w3.org/TR/activitystreams-vocabulary/#dfn-collection (W3C FPWD)

Hydra
* http://www.hydra-cg.com/spec/latest/core/#collections (W3C CG Draft)
* https://www.w3.org/community/hydra/wiki/Collection_Design

* https://www.w3.org/community/hydra/wiki/Pagination

(intense discussions on pagination on mailing list)

Schema.org<http://Schema.org>
* http://schema.org/ItemList

* http://schema.org/collection


SIOC
* http://www.w3.org/Submission/sioc-spec/#term_Container (W3C Member
Submission)

Please consider it as invitation for discussion. I hope we can discuss
it also during upcoming Social WG Face 2 Face and share back some
conclusions.
https://www.w3.org/wiki/Socialwg/2015-03-17


Cheers!


--
Karen Coyle
kcoyle@kcoyle.net<mailto:kcoyle@kcoyle.net> http://kcoyle.net<http://kcoyle.net/>
m: 1-510-435-8234
skype: kcoylenet/+1-510-984-3600<tel:%2B1-510-984-3600>