- From: Linked Data Platform (LDP) Working Group Issue Tracker <sysbot+tracker@w3.org>
- Date: Tue, 23 Apr 2013 07:59:44 +0000
- To: public-ldp-wg@w3.org
ldp-ISSUE-61 (membershipSubject): remove membershipSubject [Linked Data Platform core] http://www.w3.org/2012/ldp/track/issues/61 Raised by: Henry Story On product: Linked Data Platform core the ldp:membershipSubject functionality was never really discussed in the Working group, but it was just taken on from the original IBM proposal. It complicates things and makes the LDPC model a lot harder to understand: - if the subject is another LDPC why not just POST to that other LDPC? In which case this feature is redundant. - if the subject is not an LDPC why not just PATCH the other LDPR with the new information? In which case this feature is redundant. What is the use case for this? Given that the aim of this first spec is to be very simple, why is this needed at all, when so many other features have been having trouble being developed?
Received on Tuesday, 23 April 2013 07:59:45 UTC