- From: elf Pavlik via GitHub <sysbot+gh@w3.org>
- Date: Mon, 02 Oct 2017 17:51:53 +0000
- To: public-hydra-logs@w3.org
As we see in Vimeo example, it does behave similar to having a dataset exposed by API.
> * in case of likes - `PUT /users/{user_id}/likes/{video_id}` server will update both
* `/users/{user_id}/likes`
* `/videos/{video_id}/likes`
> * in case of channels subscriptions - `PUT /users/{user_id}/channels/{channel_id}` server will update both
* `/users/{user_id}/channels`
* `/channels/{channel_id}/users`
Creating or Deleting a resource gets reflected in two different collection, where only one of them would have `ldp:contains` relationship (guessing by looking at IRI as not opaque identifiers)
--
GitHub Notification of comment by elf-pavlik
Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/137#issuecomment-333611794 using your GitHub account
Received on Monday, 2 October 2017 17:51:43 UTC