ISSUE-88: Lost link to the resource created via POST

This issue was also described in detail as "Missing Function from Object to LDPR member"
http://www.w3.org/2012/ldp/wiki/MembershipInferencing#missing_function_from_object_to_LDPR_member

There is another solution to this problem is to have LDPCs list all the ldp:member's explicitly.

There are then two ways of recovering the "membership properties:

1. either as something one can deduce from a "ldp:member" => "membership triple" rule
such as is expressed in the spec, but could be quickly condensed by a SPARQL rule such as
CONSTRUCT {
?subject ?relation ?object . //<- the consequence
} WHERE {
?ldpc ldp:membershipSubject ?subject;
ldp:membershipPredicate ?relation;
ldp:membershipObject ?memberRelation;
ldp:member ?resource . // <- a membership relation

GRAPH ?resource {
?resource ?memberRelation ?object .
}

}
http://www.w3.org/2012/ldp/wiki/MembershipInferencing#ldp:member_.3D.3E_membership_triples
(in which case the "membership triples" are optional

2. or if the "membership triples" are considered as causal consequences of POSTing to an LDPC which would be expressed by a rule such as the one listed below, then BOTH the ldp:member and the "membership triples" MUST be published.

ON POSTING TO ?ldpc
CREATING ?member
CONSTRUCT {
?subject ?relation ?object .
} WHERE {
GRAPH ?ldpc {
?ldpc ldp:membershipSubject ?subject;
ldp:membershipPredicate ?relation;
ldp:membershipObject ?memberRelation .
}
GRAPH ?member {
?member ?memberRelation ?object
}
}

Detailed wiki discussion for this issue is at:
http://www.w3.org/2012/ldp/wiki/Issue-88