Re: reworking welkin

From: Vineet Sinha <>
Date: Thu, 02 Feb 2006 19:18:50 -0500

And another project, Relo:

{disclaimer: I am the main developer behind Relo}

Relo does allow answering the question of the type in your example, i.e.
‘show me all authors who have published with penguin’. I'm seriously
considering adding a faceted refinement interface (similar to longwell /
magnet) and I'd be interested in helping build features to answer other
more complex questions, using visualization or more traditional techniques.

The fundamental differences between Welkin and Relo, is that Relo
focuses on:

]]] Usability: I have tried hard to hide the RDF, so that end users do
not need to worry about it. Also, to make sure that the tool is usable
we are answering the same questions that you have one domain at a time.
We have done the engineering for the software engineering domain, and
are currently working for expanding support other domains and general RDF.

]]] Size/Scale: Relo is designed to look at *parts* of *large* graphs of
information. Visualization techniques have shown to work poorly showing
large graphs, so we are spending time figuring out how to select
portions of the graphs to show to the user.

If you have chance, I'd be interested in hearing a citique of Relo.


Prokopp, Christian wrote:
> Have a look at
> too if you
> did not yet.
> ------------------------------------------------------------------------
> *From:* Arvind Venkataramani []
> *Sent:* Friday, 03 February 2006 5:44 AM
> *To:*
> *Subject:* reworking welkin
> So I’m taking an information visualization class, and I’ve been doing
> some research on classification in social bookmarking systems. And it
> struck me that the best thing to do is to put the two together.
> Here’s the idea: to combine RDF statement based navigation - ‘show me
> all authors [subject] who have published [predicate] with penguin
> [object]’ - with multi-dimensional info vis techniques to make welkin
> more powerful and adaptable to different contexts and purposes.
> I’d like to figure out how much interest there is in this, and what
> people want. (of course, since I’m studying HCI, I’ll do my gosh darned
> best to make sure it is usable). So:
> 1. What are you people using welkin for? What kind of data?
> 2. What kinds of questions do you want answered using an info-vis?
> 3. What problems do you have with welkin as it is now? What are the
> things you wish you could do, but can’t?
> Thanks a ton in advance, and I’m really open to suggestions:
> user-centred design and all that :)
> -- arvind
> ms/hci | gvu center | georgiatech
Received on Fri Feb 03 2006 - 00:17:57 EST

This archive was generated by hypermail 2.3.0 : Thu Aug 09 2012 - 16:39:18 EDT