Re: remote rdf data: template builder timing problem ...

conor325 wrote:
> anticipating support in XUL templates for SPARQL and other remote RDF
> query mechanisms, I broke a large RDF file into chunks, each
> corresponding to a precise query. Use a large file and it takes for
> ever for a template driven interface to load but break down the RDF
> data and only load it when needed and the interface behaves reasonably
> well.
> 
> It works like this: a data source file of "select_name_p1.rdf"
> corresponds to a SPARQL "select ?name where {".../p1" t3p:name ?name}".
> The current template mechanism let's you set the datasources attribute
> of a template: setting it to "select_name_p1.rdf" corresponds to
> issueing a "select ... etc" to a remote data source.
> 
> If the template builder handles such granular files then it should
> behave properly for a variety of remote query mechanisms. Conversely,
> problems with this approach will be shared by any query mechanism.
> 
> So the problem: it's one of timing and this test file isolates it:
> http://www.the325project.org/blogs/techBlogExamples/remoteRDFTest.xul.
> Basically, the template builder doesn't wait until a remote data source
> has loaded. I don't think this is correct behavior but perhaps there
> are reasons for the premature kick in. Anyone know?
> 

Known bug, the template builder doesn't observe the load and lacks a 
final rebuild or something like that.

Axel