Re: ldp-ISSUE-72 (membershipObject): The object of a membership triple isn't always the address of the created informational resource [Linked Data Platform core]

Hi Roger,
could you please post an example that illustrates what the problem is? I 
have to admit not to understand.
Thanks.
--
Arnaud  Le Hors - Software Standards Architect - IBM Software Group




From:   "Linked Data Platform (LDP) Working Group Issue Tracker" 
<sysbot+tracker@w3.org>
To:     public-ldp-wg@w3.org, 
Date:   05/22/2013 02:13 AM
Subject:        ldp-ISSUE-72 (membershipObject): The object of a 
membership triple isn't always the address of the created informational 
resource [Linked Data Platform core]



ldp-ISSUE-72 (membershipObject): The object of a membership triple isn't 
always the address of the created informational resource [Linked Data 
Platform core]

http://www.w3.org/2012/ldp/track/issues/72

Raised by: Roger Menday
On product: Linked Data Platform core

When creating a new resource, the membershipPredicate and 
membershipSubject properties are used to construct a new triple expressing 
the relationship between the LDPR and the newly created resource. As 
pointed out by Henry, e.g. in [1], there is a current limitation because 
this new triple only references the document that contains the description 
(rather than the resource itself).

One solution might be :: when creating the membership triple, if the 
POSTed content includes a primaryTopic reference, the server should use 
that address as the object in the membership triple (and not that of the 
information resource itself). 

[1] http://lists.w3.org/Archives/Public/public-ldp-wg/2013May/0186.html