W3C home > Mailing lists > Public > public-semweb-ui@w3.org > October 2007

Re: SVG Semantic Web graph browsing tool

From: Marcus Cobden <lists@marcuscobden.co.uk>
Date: Mon, 08 Oct 2007 13:43:13 +0100
Message-ID: <470A25E1.5070408@marcuscobden.co.uk>
To: public-semweb-ui@w3.org

anita@cs.uu.nl wrote:

I'm glad it's of use to you, but please reply to the list rather than me 
personally.

> This is of great use to me, but how does it work? I tried to add a uri to
> the box but it did not let me submit a web resource (I tried
> http://beta.uniprot.org/taxonomy/9606.rdf and
> http://www.w3.org/2000/07/hs78/algernon.rdf) - am I doing something wrong?

Ah sorry about that, that should really be documented or fixed.
The uri for the document is added to the graph and drop downs, but when 
you inspect it it shows only that it has 22 triples and nothing else.

This is because you are inspecting the URI of the document, and the 
document contains no triples describing itself, and thus nothing is 
displayed. What would be nice would be, when inspecting a document, for 
it to suggest a number of URI's it mentions within it, to allow you to 
start navigating around.

If you add http://purl.uniprot.org/taxonomy/9606 instead of 
http://beta.uniprot.org/taxonomy/9606.rdf the output will me much more 
useful.
The first url redirects to an intermediate page, which then redirects 
the request to an RDF version with the url you were using.
This will display information because the document mentions the url.

With the other url, either add one of the uri's from the document to the 
graph, or add one of the uri's referencing an entity within the document 
as a starting point.
eg. http://www.w3.org/2000/07/hs78/algernon#sets

> Also, how can I reference local files?

I'm afraid this is a regression here, it used to have the capability to 
open local files, but it suffered from the same cross domain permissions 
problem as the Tabulator (http://www.w3.org/2005/ajar/tab) in order to 
intercept 3XX redirections.

Packaging it as a Firefox extension is a way round this, but it's 
simpler to just go via a serverside script. Plus I have the spare 
bandwidth ;)
Received on Monday, 8 October 2007 12:43:44 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:16:47 GMT