It's similar to Freebase *but* rather than curating the organisation of data (as Freebase does) Fluidinfo is, er, "fluid" in that it expects conventions in tagging and organising data to emerge. Evolutionary pressure will make the best / most appropriate "schema" to survive (become conventions) in much the same way that hashtags is a bottom-up convention that emerged in Twitter.
The first thing I notice: It's incredibly slow. To be of practical use, it must speed up at least by the factor 100 (probably more; I've still no result for my first query, and that was one of the example queries shown by the help command!).
Yup, we're a start-up losing our Slashdot virginity...;-)
Slashdot Mirror
It's similar to Freebase *but* rather than curating the organisation of data (as Freebase does) Fluidinfo is, er, "fluid" in that it expects conventions in tagging and organising data to emerge. Evolutionary pressure will make the best / most appropriate "schema" to survive (become conventions) in much the same way that hashtags is a bottom-up convention that emerged in Twitter.
The first thing I notice: It's incredibly slow. To be of practical use, it must speed up at least by the factor 100 (probably more; I've still no result for my first query, and that was one of the example queries shown by the help command!).
Yup, we're a start-up losing our Slashdot virginity... ;-)
Fluidinfo in a nutshell: http://www.slideshare.net/fluidinfo/fluidinfo-in-a-nutshell Happy to answer any questions (n.b. yeah, I work for Fluidinfo and I authored the presentation that I'm linking to).