Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I feel like IKEA likely operates in a pretty restricted problem space compared to a general knowledge graph like wikidata or what have you. I don't know that you can separate the "all knowledge" graph into 3 layers like this.


I don’t think they claimed it would work for everyone. Or indeed for anyone else. Seems like it's just saying "this is what we do."

(Edit: removed needlessly snarky wording.)


My main interest in a knowledge graph is the universal application of it, and I suspect that's true for much of HN audience. So of course it's natural when reading this article to wonder if their methodology applies, and I was answering my own implicit question.

Good on IKEA for solving the problem they have efficiently, but I can be interested in a larger scope.


Yes, you’re correct and that’s a reasonable interest. I also realize that I worded my comment in a needlessly obnoxious way.


> I don't know that you can separate the "all knowledge" graph into 3 layers like this.

The 3 layers mentioned are just the basic structure of ontologies. Concepts eg “vehicle, person, desease, atom, bridge,…” then categories of the concepts, and finally data, ie instances.

Larger knowledge graphs don’t grow by adding more “layers” they add more content to all three layers.


I'm not an expert in this field, but I had never heard of this as a standard ontological structure. I can't find any solid description of it either, are there any references you can share?

I thought that it gets complicated because you can have concepts of concepts, and you can have both categories of concepts and concepts of categories etc etc. It ends up being more than 3 layers, and you get layer violations and loops etc.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: