Hi Harald,
I saw the extractors that you have written and I think that it is a good
start, but I think that there is a case for adding methods to the API to
get the reifing topic of an object (and to get the object reified by a
topic). I think that methods are better than indexes in this case,
because there can only ever be a one-to-one relationship. These methods
could be implemented by simply making use of the existing methods of the
TopicMap interface so it shouldn't be a big deal to do it. I'll look
into adding these for the next release.
Cheers,
Kal
On Wed, 2004-08-18 at 16:57, Harald Kuhn wrote:
> Hi Kal,
>
> as the topic of how to handle reification of TopicMapObjects was mentioned on the mailinglist recently and i also had problems with this some time ago in one of my projects, i wrote two Extractors for Finding Reified Objects and Reifying Topics (RefiedObjectExtractor and ReifyingTopicExtractor). I also wrote an experimental index for the in Memory Backend which caches these information for a faster access. I am not quite sure which way would be the best.
>
> The question is wether extractors are the right point to add support for this. As i pointed out, it would also be possible to use and Index. I could also imagine adding methods to TopicMapObject and Topic (this would have by far the biggest impact on the API). What do you think ?
>
> As the Extractors have far less impact on the API, I added them to cvs (...utils.extractors). If anybody is interested in the code of the Index Prototype, just send me an email.
>
> Cheers,
> Harald
> ________________________________________________________________
> Verschicken Sie romantische, coole und witzige Bilder per SMS!
> Jetzt neu bei WEB.DE FreeMail: http://freemail.web.de/?mc=021193
--
Kal Ahmed <ka...@te...>
techquila
|
