I’m a little confused right now WRT where exactly the RDFX core should be started – it’s either in the RDFXView class or in the plugin class – i’m assuming it’s in the plugin class… but… because everything’s event based there’s a risk of the core being ready before the view – and the view missing out on the initial broadcasts – what this means therefore is that there may need to be some kind of regular (i.e. once every n seconds) broadcast from the core to allow interested views to come and go whilst the core remains. This is very similar to the Jini lookup model – and so I’m immediately thinking that there is potential for a two way event with a View announcing it’s arrival and requesting the transmission of a “top node” from the model.

Time passes… Yes, it’s the plugin that should start the RDFX core and then when a view is started it will announce that it would like to know about “any node which can be a top node” or announce that it wants to know about node x” – where x is a URI – this then allows for multiple views and for the user to define the top node URI, should that prove useful – a kind of “start exploring from…” function.