Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
The underlying data has to be in graph-structured format (in RDF syntax); reasoning, most notably object consolidation, is supported via OWL. Once the data is indexed, users can search and browse right away. There's no configuration needed, because the ordering of data is done based on the calculated ranks. The UI can be configured via XSLT and CSS for adding a logo or changing the look and feel.
We've developed VisiNav as part of a research project, and the university owns (and manages) the IP. I guess they will make it available free of charge for educational and research organisations, but commercial applications would require a license.
The main obstacle to "this golden future" so far has been an insufficient amount of data published online. Many organisations sit on their data like hens sit on their eggs, and publishing data right requires some effort.
That's slowly changing, especially with more openness and transparency -- voluntarily or forced -- in all kinds of organisations and agencies (data.un.org, data.gov, data.gov.uk... ), more people getting the idea of open data, and the establishing of simplified best practices on how to publish data on the web following the Linked Data paradigm.
It's about time that Yahoo and Google finally start to take note and add open data to their systems (which don't exploit the full power of these technologies but hey you've got to start somewhere).
You misunderstand how that's supposed to work. You don't "free main memory" to SSD. The idea is to use SSD as a pre-buffer for RAM, so it's quicker to access than reading from disk.
But there's something wrong if the Linux kernel buffers SSD I/O in main memory and swaps code fragments to disk. At least that's what happened in my experiments.
I've been toying around with a Samsung 16GB SSD. Performance improvement over spinning disks in an I/O-heavy scenario was neglegible. Also, it seemed as if the Linux kernel was still using memory to buffer SSD disk I/O. Which somewhat negates the argument of using SSDs to free main memory for other stuff.
Any idea what type of OS/filesystem combination they were using?
I really hope they publish the stuff as Linked Data.