- From: elf Pavlik via GitHub <sysbot+gh@w3.org>
- Date: Tue, 22 Aug 2017 13:04:43 +0000
- To: public-hydra-logs@w3.org
In https://www.w3.org/TR/ldp/#ldpc-HTTP_DELETE spec mandate that LDP server > 5.2.5.1 When a contained LDPR is deleted, the LDPC server MUST also remove the corresponding containment triple, which has the effect of removing the deleted LDPR from the containing LDPC. If hydra client can not rely on hydra server to remove 'containment triple', it may require client to always take that responsibility. Having operations like `AddMemberOperation` and `RemoveMemberOperation` would allow client to do it. Then we also may need to address a case where client issues `RemoveMemberOperation` but doesn't DELETE the resource (eg. `/events/42`), which would lead to collection `/events` not referencing any more `/events/42` as its member. -- GitHub Notification of comment by elf-pavlik Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/137#issuecomment-324019573 using your GitHub account
Received on Tuesday, 22 August 2017 13:04:45 UTC