- From: elf Pavlik via GitHub <sysbot+gh@w3.org>
- Date: Wed, 16 Aug 2017 13:33:45 +0000
- To: public-hydra-logs@w3.org
> POSTing an schema:Person with the @id already set to a collection would be fine too I guess but opens a can of worms if the property values differ.
They payload of request to `/people/alice/events` collection could include just `{ "@id": "/events/42" }` since we only want to add reference, updating that event itself would require request directly to `/events/42`.
> Removing it from a collection is trickier though.
Good point, here HTTP verb like UNLINK would come very handy. I think may need PATCH to get this 'remove reference' functionality.
BTW if we DELETE `/events/42` do we rely on the server to remove it from `/events` collection members? Similar to https://www.w3.org/TR/ldp/#ldpc-HTTP_DELETE
I have impression that
* `/events` collection which **contains** its members works like `ldp:Container`
* `/people/alice/events` collection which only **references** its members works more like basic `ldp:Resource`
--
GitHub Notification of comment by elf-pavlik
Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/134#issuecomment-322772258 using your GitHub account
Received on Wednesday, 16 August 2017 13:33:47 UTC