- From: ☮ elf Pavlik ☮ <perpetual-tripper@wwelves.org>
- Date: Fri, 06 Mar 2015 16:00:17 +0100
- To: Jarno van Driel <jarnovandriel@gmail.com>
- CC: W3C Web Schemas Task Force <public-vocabs@w3.org>
- Message-ID: <54F9C101.5070501@wwelves.org>
On 03/06/2015 03:30 PM, Jarno van Driel 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. I may misunderstand some things abou current schema.org model, but in RDF you can use *any* property from *any* vocabulary on *any* entity. Unless a property has explicit constraint as disjoint with some other property(ies) http://www.w3.org/TR/owl2-syntax/#Disjoint_Object_Properties I thinks this makes one of the biggest differences to what people get used to in Object Oriented programming languages! If you use rdfs:domain and rdfs:range it can cause additional inferences e.g. adding more types to "@type" but schema org uses 'relaxed' / 'just a hint' version of them - schema:domainIncludes and schema:rangeIncludes which don't cause any inferences. { "@context": "http://schema.org", "name": "elf Pavlik", "knows": { "name": "Peter Pan" } } causes no inferences in RDFS reasoner, but running same reasoner on { "@context": [ "http://schema.org", {"foaf": "http://xmlns.com/foaf/0.1/ "} ], "name": "elf Pavlik", "foaf:knows": { "name": "Peter Pan" } } will use rdfs:domain and rdfs:range from foaf:knows definition and infer *two* triples "@type": "foaf:Person" http://xmlns.com/foaf/spec/#term_knows { "@context": [ "http://schema.org", {"foaf": "http://xmlns.com/foaf/0.1/ "} ], "@type": "foaf:Person", "name": "elf Pavlik", "foaf:knows": { "@type": "foaf:Person", "name": "Peter Pan" } } Still you can use "foaf:knows" on a Car or Book if you don't mind reasoner producing "@type": ["Book", "foaf"Person"]. When using "knows" from schema.org you can state that a Book knows a Car without any consequences. (Maybe validation tools would give some warnings, based on ... any documentation for that?) > > 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? Mail archives don't work very well as reference, i recommend capturing stuff on one of the wikis * https://www.w3.org/wiki/WebSchemas * https://github.com/schemaorg/schemaorg/wiki Cheers! > > 2015-03-06 14:58 GMT+01:00 Karen Coyle <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/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 http://kcoyle.net >> m: 1-510-435-8234 >> skype: kcoylenet/+1-510-984-3600 >> >> >
Received on Friday, 6 March 2015 15:00:37 UTC