...
* This could result in data loss if clients are attempting to provide the same membership predicates to the same resource in two separate ways. The alternative would be to pull all existing membership references and determine if any of the incoming membership relations are new. It is doable, but potentially costly.
...
- Containment triples (ldp:contains) would not be persisted to stored RDF files.
- Child resources would store and persist a reference to their containing parent.
- this could be fedora:hasParent, or some other predicate. LDP does not define this.
- Simple search index will be populated with ldp:contains triples
- When performing a GET operation, if prefer headers indicate that containment relations should be returned, then they will be pulled from the simple search index.
- These properties would be merged into the resultant RDF stream prior to returning to the client.
The intention of this approach is:
- to avoid triggering changes to the persisted state of a resource and its RDF when containment/membership changes.
- to avoid having extremely large persisted RDF files, which could impact system performance during read and write operations.
- to avoid unnecessary retrieval of containment/membership properties when they are not requested, as this would greatly reduce the value of the "Prefer: minimal" header.
...