4 ms·
Former Freebase, current Google engineer here: First of all, let me say that I'm glad more people are thinking/working in the space of triples. Even unstructur
by barakm 14y ago
Former Freebase, current Google engineer here:
First of all, let me say that I'm glad more people are thinking/working in the space of triples. Even unstructured ones like this.
But when there's no semi-strict schema, it gets really, really tricky. Free text is hard, and actual meaning is hard to separate. (I say semi-strict, as Freebase is schema-last -- feel free to create your own! -- but has some level of enforcement)
For specific domains you may be okay with tags. And for some limited applications it probably works great. Triples are cool!
But when you start talking about larger, broader, datasets, ones that no one person or small group can curate, you're going to start running into collision.
There's certainly an argument to be made for metaschema -- https://developers.google.com/freebase/v1/search-metaschema https://developers.google.com/freebase/v1/search-metaschema -- and crowdsourcing these sorts of things could be interesting.
I think there's a lot of interesting work to be done. But I doubt that this is "better" per se, or at the very least, is little more than a toy.
And hey, I built such a toy graph engine once upon a time (be gentle -- it was really a demo hack) https://github.com/barakmich/jgd https://github.com/barakmich/jgd -- you can even query it with Freebase's old MQL. (Which I have mixed feelings about, but is cool in its own way)
I guess my argument is, don't throw the baby out with the bathwater. And feel free to ping me for more!
- christophe971 14y agoFirst of all, I'm glad to be talking to a Freebase engineer :) Second: It is not intended to be a Freebase killer, but it is certainly better for me and what I needed it for: building denisthebot.com - which can answer questions about a whole lot of subjects while being completely agnostic about what "categories" these subjects fit in. Third: Since we all know no-one is going to change anyone's mind here, I won't discuss the merits of a DB structured the way I built it. But calling it a toy is quite flattering, I know some very powerful stuff that were called "toy" for some time :) Also, it would be a very easy toy to use, which will suit a lot of people, according to the emails I received. Also, you're right: "don't throw the baby out with the bathwater".