- From: Wallis,Richard <Richard.Wallis@oclc.org>
- Date: Tue, 7 May 2013 13:10:36 +0000
- To: Dan Brickley <danbri@danbri.org>
- CC: "public-vocabs@w3.org" <public-vocabs@w3.org>
> >Is this specifically library-like or cultural heritage notion of a >collection? Or is it a general purpose data structure for listing >bundles of things? My suspicion is that it's the latter, but it could >easily be mistaken for a very general purpose mechanism. You suspect correctly. The need/approach has come the library and associated worlds, but it is clearly applicable in a wider context. A library has a collection of books, a museum has a collection of artefacts, etc. However a farmer could have a collection of animals By making Collection a subclass of CreativeWork it does imply that the creation of a collection would be a conscious creative act by a creating person/organization. However the parts of a collection would not always be creative works themselves (fossils in a museum, toys and books in a children's library, etc.) hense the need for isPart to be added to Thing. > >If there's a bibliographic / cultural heritage problem we can solve >here, while avoiding getting into heavier 'theory of parts' territory >(e.g. http://ontology.buffalo.edu/smith/articles/Mereotopology.pdf) >I'd be happy... I have equal aversion to diving down such deep dark rabbit holes! Would we not avoid that by indicating that a Thing can be part of many collections or none, a Collection can contain zero or any parts that may or may not be in other Collections - or am I being naive? ;-) ~Richard. > >Dan > > >> Sub-classed to: Thing > CreativeWork > Collection >> Properties likely to be used from CreativeWork >> * about (e.g. for collection themes) >> * contentLocation (e.g. for museum/archive collections) >> * creator (e.g. for collection curators) >> >> New property for CreativeWork (or perhaps for Thing) >> As a matter of principle, anything imaginable can be thought of has >>having >> parts. Although we are primarily interested in this property for sake of >> modelling collections and multi-part works, a broader treatment as a >> property of schema:Thing would be appreciated. >> * Property: hasPart >> * Expected Type: Thing >> * Description: A thing that is part of this CreativeWork. For example >> things in a collection or parts in a multi-part work >> >> New property for Thing >> This is the same schema:isPartOf property as currently found in the >> http://schema.org/WebPage class with schema:CollectionPage as the range. >> We would like it promoted for broader use, particularly in this case, >>for >> use with a Collection Type. >> * Property: isPartOf >> * Expected Type: CreativeWork or Thing(dependant on choice for hasPart) >> * Description: Inverse of hasPart >> >> More information and some examples can be found on the SchemaBibExtend >> Wiki <http://www.w3.org/community/schemabibex/wiki/Collection>. >> >> ~Richard. >> >> >>
Received on Tuesday, 7 May 2013 13:12:02 UTC