> Taking the idea further, why aren't parts of the web, especially those which
> attempt to encode knowledge and the relationships between concepts (perhaps
> a future enhanced Wikipedia), accessible via an N-Dimensional graph?
dbPedia can give you such data from Wikipedia:
http://dbpedia.org/
and if you like you can follow links out into the cloud:
http://richard.cyganiak.de/2007/10/lod/
This piece argues that the graph view is (usually) a bad idea - it's
the "Pathetic Fallacy" of the somewhat misleading title. Interesting
read though.
http://swui.semanticweb.org/swui06/papers/Karger/Pathetic_Fallacy.html
I spent a while working on a graph-oriented tool (IdeaGraph) and came
to the conclusion that the view was only really useful in conjunction
with other UI elements, and it was best to avoid having more than a
little graph on screen at a time. I think I also did hook up the bits
to allow it to navigate the HTML Web through a graph, but never got to
anything I could call genuinely useful. Incidentally, the
ever-expanding tree is quite a nice alternative, you can traverse
graphs but it's more compact.
Cheers,
Danny.
http://webbeep.it - text to tones and back again
Hi,
In my experience, the key to charting this type of data is abstraction: not everything has to be displayed at the same time. Brushing, highlighting, and slicing are necessary operation unless you want an indecipherable--if pretty--mess of dots and lines.
An example: One could abridge a network path into only three nodes: beginning, grouped-middle and end nodes if the question is where did I start and where did I end? Or the nodes could be grouped by category: instead of specifically displaying every website, you could show something like [search engine]->[wiki]->[social network]->[search engine]->[retailer]->[email provider].
Irrelevant nodes could be collapsed.