- From: Owen Shepherd <owen.shepherd@e43.eu>
- Date: Sun, 09 Nov 2014 01:35:03 +0000
- To: ☮ elf Pavlik ☮ <perpetual-tripper@wwelves.org>
- CC: "public-socialweb@w3.org" <public-socialweb@w3.org>
- Message-ID: <545EC4C7.2020508@e43.eu>
I accidentally forgot to reply all, so I'll CC the list back in here. This problem doesn't apply to AS because we don't use "AS:follows" properties or similar > ☮ elf Pavlik ☮ <mailto:perpetual-tripper@wwelves.org> > 09 November 2014 01:23 > 1. Not sure if you wanted to send it just to or simply missed cc list > 2. If you put collection directly as values of follows you will get some > undesired consequences in RDF! > > * https://github.com/HydraCG/Specifications/issues/33 > * https://github.com/HydraCG/Specifications/issues/41 > > Owen Shepherd <mailto:owen.shepherd@e43.eu> > 08 November 2014 23:58 > Translating your Hydra sample to AS2 (as through the lens of > ActivityPump, and borrowing from AS1 where AS2 is currently missing): > { > "@id": "https://wwelves.org/perpetual-tripper", > "@type": "as:Person", > "follows": { > "@id": "https://wwelves.org/perpetual-tripper/follows", > "@type": "as:Collection", > "memberTypes": "as:Actor", > "totalItems": 23, > "items": [ > "http://owenshepherd.net", > "https://e14n.com/evan", > ... > ] > } > } > > with the provisio that it must remembered that ActivityStreams > collections are *paged* - there may be more items than conveyed in the > items member, in which case you must page your way through the > collection to find them all. (When I get around to exhaustively > documenting collections in ActivityPump I'll likely provide a > guaranteed mechanism for requesting a given number of items at once > and require impls to support at least ~200) > > - Owen > ☮ elf Pavlik ☮ <mailto:perpetual-tripper@wwelves.org> > 08 November 2014 23:49 > Howdy, > > In Owen's draft of ActivityPump we can find some use cases for > collections/containers: > http://oshepherd.github.io/activitypump/ActivityPump.html#collections > > While ago I started page for comparing existing designs: > https://www.w3.org/wiki/Socialwg/Collection_Comparison > > So far it only has examples in Hydra, I'll try to add AS and LDP > versions ASAP. Collection of people I follow, using hydra:Collection > would look something like: > > { > "@context": [ > "http://www.w3.org/ns/hydra/context.jsonld", > { "schema": "http://schema.org/" } > ] > "@id": "/perpetual-tripper", > "collection": { > "@id": "/pepetual-tripper/follows", > "@type": "Collection", > "manages": { > "property": "schema:follows", > "subject": "/perpetual-tripper" > } > "member: [ > "http://owenshepherd.net", > "https://e14n.com/evan", > ... > ] > } > } > > For followers one can simply use manages block with object instead of > subject > > "manages": { > "property": "schema:follows", > "object": "/perpetual-tripper" > } > > > Which provides clear way to reuse existing predicates while giving > collection separate URI and additionally enabling paging. > > It looks like some ActivityStreams/Pump features will require putting > constraint on members of collection. It currently uses "objectTypes" > documented in under 'collection' in > * > https://github.com/activitystreams/activity-schema/blob/master/activity-schema.md#object-types > > ActivityPump draft uses it in: > http://oshepherd.github.io/activitypump/ActivityPump.html#streams > > { > "id": "https://example.com/~alice/my-stream", > "objectType": "collection", > "objectTypes": ["activity"] > "items": [ ... ] > } > > Could we collect on our wiki page other requirements for > Collections/Containters which we currently stay aware of? > > Cheers! > > -- Sent using Postbox: http://www.getpostbox.com
Received on Sunday, 9 November 2014 01:35:34 UTC