From: Matthew H. <mat...@cs...> - 2008-03-20 07:04:43
|
Hi Tim, On 19 Mar 2008, at 23:17, Swanson, Tim wrote: >> -----Original Message----- >> From: owl...@li... [mailto:owlapi- >> dev...@li...] On Behalf Of Matthew >> Horridge >> Sent: Tuesday, March 18, 2008 7:38 AM >> >> The change listener just listens to OntologyChange events on the >> manager - basically add/remove axiom changes and SetOntologyURI >> changes. >> >> We will consider adding an OntologyManagerListener interface if you >> would find that helpful. This could be notified of changes when >> ontologies are added or removed from a manager. >> > > That would be great. > > I'm toying with the idea of an object that needs to be answerable to > all > the content of a set of ontologies. That is, when the object is > queried, > it needs to give an answer based on the content of those OWLOntology > objects. > > For performance reasons, it shouldn't go back and re-process the > ontologies every time it needs that information, so it stores what it > needs in memory, and then listens to change events on the ontologies. > > However, what I would like to do is to simply give the object an > OWLOntologyManager, and then say that the object is responsible for > any > ontology managed by that manager. For that approach to be feasible, > however, there would need to be something like an > OntologyManagerListener. o.k. I've noted the request and will see what I can do :) Cheers, Matthew |