Actually, it finally is showing me some information. From the looks of the log 
file it was choking for ages on the dcterms vocabulary which was linked from 
the resource URI I was using. I don't think there is a large amount of value in 
the nodemap sizes, at least for my data, as the upper ontologies seem to take 
up most of the space, leaving the interesting information further down.

The following two URI's were the ones I was trying to use.

[1] http://bio2rdf.org/links/pubmed:10021349
[2] http://bio2rdf.org/pubmed:10021349

Is there anyway currently of starting the browser up with a given URI, ie, 
http://www.sheaflight.com/browser/SheaflightBrowser.aspx?uri=http://bio2rdf.org/pubmed:10021349

Cheers,

Peter

----- "Ian Hebden" <[EMAIL PROTECTED]> wrote:

> From: "Ian Hebden" <[EMAIL PROTECTED]>
> To: [email protected]
> Sent: Tuesday, 12 August, 2008 1:36:44 AM GMT +10:00 Brisbane
> Subject: Sheaflight Linked Data Browser
>
> Hi All,
> 
> 
> 
> I recently developed a new linked data browser as part of an MSc
> project, and I�m looking for people to give it a try and send me some
> feedback about the experience. The feedback consists of a simple
> questionnaire, (about 20 questions), which ask you to rate some of the
> browsers features on a scale of 1-5.
> 
> Sheaflight is an experimental Linked Data Browser which uses
> Microsoft's Silverlight technology and Joshua Tauberer's Semantic
> Web/RDF library to deliver a Treemap visualization of the underlying
> RDF/XML representation of resources (HTTP URIs).
> 
> In order to run the browser application, it is necessary to download
> and install the Microsoft Silverlight 2 Beta2 plug-in which is
> available from the Microsoft Silverlight site. Please refer to the
> Silverlight documentation for issues regarding supported platforms,
> etc. After the plug-in has been installed, you can simply point your
> browser to the Sheaflight Browser page.
> 
> Additional documentation may be obtained from the website
> www.sheaflight.com .
> 
> Many thanks in advance,
> 
> Ian Hebden ( [EMAIL PROTECTED] )

Reply via email to