[Specifications] adding alredy existing resources as collection members

elf-pavlik has just created a new issue for https://github.com/HydraCG/Specifications:

== adding alredy existing resources as collection members ==
Currently in our Use Cases we only have situation where we [5. Create a new event](https://github.com/HydraCG/Specifications/blob/master/drafts/use-cases/5.creating-new-event.md) using operation advertised by the collection of events, which automatically adds it to that collection.

I would like to add use case of adding already existing resources to collections. For example if we have *People* in this API, each person could reference a 'personal collection of events' using `hydra:collection`. But we wouldn't want to create new events in that collection but instead just add already existing events. Possibly using [`schema:AddAction`](https://schema.org/AddAction) rather than [`schema:CreateAction`](https://schema.org/CreateAction).

What would such action reference with `hydra:expects`? It pretty much just needs an `@id` which should get added to `hydra:member` of that collection.

Once we roughly agree on approach to that I will make PR with this additional use case!

This issue somehow reminds me of https://tools.ietf.org/id/draft-snell-link-method-01.html

@RubenVerborgh do you know how currently Solid handles that? Probably it wouldn't use `ldp:Container` but just `ldp:Resource` to represent such collection and add statements with `hydra:member` using HTTP PATCH

Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/134 using your GitHub account

Received on Monday, 14 August 2017 22:22:10 UTC