On 08/07/11 20:55, Stephan Gambke wrote: > Hi Markus, > > Am 08.07.2011 20:20, schrieb Markus Krötzsch: >> On 08/07/11 14:30, Stephan Gambke wrote: >>> Hi James, >>> >>>> Semantic Glossary (Version 0.1 alpha) (r91693) + Lingo >>> well, r91449 implemented some changes that I do not really like. >>> Basically semantic objects not connected to a real wikipage are not >>> supported anymore.<snip> >> >> I do not know about the detailed implementation of this extension, but >> some clarification is needed here. The situation is actually the >> opposite of what is written above: the recent changes are in fact >> *introducing* the creation of non-page subobjects as a *new feature*. > >> On the other hand, I do not think that it is viable to have internal >> objects that belong to *no page at all*. This would imply that the data > > I was sure that internal objects survived data updating before so that > was why I was not too happy discovering that the data was just gone > after an update. I am not sure anymore though and I'm certainly not > downgrading to prove one of us wrong. Anyway, thanks for the clarification.
If internal object data survived before, then only because some special mechanism made sure that it was created again in each update. The old code certainly contained a feature to search and delete all subobject data together with the owning page. Maybe the old mechanism just needs to be updated to work with the new system; there should really not be a principal change in this. The only exception is if internal objects used the ID management of SWLStore directly to create internal objects that did not belong to any valid page (without an existing owner page, the update event that could delete the data would never occur). > > You are probably right that the glossary data should be stored on a wiki > page somehow. This is already possible, you can just use the properties > defined by the extension. It is just not advertised as the preferred > method to build the glossary. I will probably change the focus and keep > the internal objects mechanism as a simple alternative. I think it is actually easier with the new code to handle internal objects "without surprises." The current code will apparently need some adjustments, but after this it should work better than before (e.g. in the RDF store and not just in the SQL store). Regards, Markus ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
