The current implementation requires the origin to list all the triples to be removed when an entire resource is removed. This is a potential memory leak for long running applications, in addition to needlessly wasting resources to state that which is already known.
So it would be wise to either introduce an additional graph or to extend ll:remove to define some behaviour so that resources and their matches can be removed completely.
This might be especially relevant when working with properties that have blank nodes as object which can only exist once and are replaced often (e.g. a PartialCollectionView with its members being an ordered list).
The current implementation requires the origin to list all the triples to be removed when an entire resource is removed. This is a potential memory leak for long running applications, in addition to needlessly wasting resources to state that which is already known.
So it would be wise to either introduce an additional graph or to extend ll:remove to define some behaviour so that resources and their matches can be removed completely.
This might be especially relevant when working with properties that have blank nodes as object which can only exist once and are replaced often (e.g. a PartialCollectionView with its members being an ordered list).