Re: [ANN] SView: a Web-based system for browsing Linked Data

Dear Hugh,

The developer team investigated the reason why "RDF description not found¡± 
occurs to the three URIs you pointed out.

1. For the first URI, the robots.txt of the website [1] does not allow 
agents to fetch the file.

User-agent: *
Disallow: /id/

2. For the other two URIs, SView can dereferences the HTTP URIs. However, 
the captured RDF data do not provide any triples about the particular two 

The SView system primarily aims to view entities instead of data files. So 
the input URI and the publication of related data should follow the rules of 
Linked Data [2], in particular the third rule:
When someone looks up a URI, provide useful information (about the URI), 
using the standards.

In this case, I think these two URIs denote RDF files instead of entities. 
Of course, there is a subtle issue, say HttpRange-14 [3].

In summary, the SView system keeps the principle of Linked Data in its 
design, and your feedback inspires us to cope with the situation that the 
input URI denotes an RDF file.


Yuzhong Qu


[2] Linked Data - Design Issues

[3] Dereferencing HTTP URIs

From: "Hugh Glaser" <>
> Hi there,
> This looks good.
> But it doesn¡¯t seem to be fetching quite a lot of Linked Data.
> I can get the ones on the home page, and I found
> worked.
> But
> all give "RDF description not found¡±.
> As far as I can verify, these three all do Conneg for
> Accept:application/rdf+xml
> Also, would you like to integrate with, or some other sameAs
> services?
> Best
> Hugh
> On 13 Nov 2013, at 05:50, Yuzhong Qu <> wrote:
>> Dear all,
>> A new system for browsing Linked Data, called SView, is now available
>> [1]. It enables end-users to conveniently browse entities described in
>> the Linked Data through views and navigators. Besides, it provides a
>> built-in service for users to resolve URI coreference collectively.
>> It has the following features:
>> 1. Home View
>> This particular view presents a personalized list of properties and their
>> values of the visited entity. Users can sort, remove and add properties
>> of the visited entity to form a better view of the concerned entity. Each
>> user's viewpoint on property sorting is collected and then turned into a
>> consensus sorting. The consensus sorting on involved properties is shared
>> among all users.
>> 2. Entity Identity Module
>> The "ID" component becomes available when browsing an entity (visible at
>> the left-upper corner). It enables users to interactively identify
>> coreference URIs of a visited entity. Each user's viewpoint on entity
>> coreference resolution is learned from the user's interaction, and all
>> users' viewpoints are aggregated and then shared among all users.
>> 3. Navigator Panel
>> This panel provides several navigators, such as navigation path, similar
>> entity and filtering facility, to help users locate or find semantically
>> related entities.
>> While a number of views and navigators have been built in the system,
>> more views and navigators are expected to be plugged in to make the
>> system better. It is under consideration that whether or not the SView
>> should become an open platform that receives ¡°plug-ins¡± (e.g. views,
>> navigators) from the developer community.
>> The WebSoft group at Nanjing University ( will
>> continue to improve the SView system. Any comments are welcome.
>> Have fun with SView :-)
>> Yuzhong Qu
>> [1]
> -- 
> Hugh Glaser
>   20 Portchester Rise
>   Eastleigh
>   SO50 4QS
> Mobile: +44 75 9533 4155, Home: +44 23 8061 5652

Received on Thursday, 14 November 2013 14:07:02 UTC