I suppose the simplest solution would be a way to "mark" a thing as second-level thing, ie. a thing that cannot exist without grounding occurrence. We essentially have the same problem with sub-resources as discussed in this review request: https://git.reviewboard.kde.org/r/101994/
Cheers, Sebastian On 08/05/2011 12:18 AM, Christian Mollekopf wrote: > Hey, > > To bring an old topic up, does anyone have an idea how to get rid of > PIMO:Things if I don't have control over the grounding occurrence? > In my case that is a feeder generated resource (who would have > guessed..), so a combined InformationElement/DataObject. > For tagging purposes I generate a PIMO:Thing, and use only the Thing for > tags and alike (all manual user work). > > But since the grounding occurrence can vanish at any time, nepomuk is > left with a dangling Thing. > > I don't think we can make a cleanup service, since I might as well want > to keep the thing without a grounding occurrence (if valid at all). > But maybe I could mark the created thing as subresource of the IE, so it > gets deleted with it? > This would of course have to work over deleteDataByApplication, so if > another app uses the thing without setting it as subresource, the thing > remains > (otherwise we defeat the whole purpose of the thing). > > Ideas or plans? > > Cheers, > > Christian > _______________________________________________ > Nepomuk mailing list > [email protected] > https://mail.kde.org/mailman/listinfo/nepomuk > _______________________________________________ Nepomuk mailing list [email protected] https://mail.kde.org/mailman/listinfo/nepomuk
