I think your model certainly makes sense for some use cases. It’s totally valid to create a local graph based on some local understanding and work off of that graph for some use cases.
But the mental model and value of having a global graph using entities with stable IDs is different.
Allowing humanity to grow its knowledge over time. The only way to truly grow knowledge is to have something stable that grows and accretes. You can’t do this if the underlying targets of description are constantly changing
Enabling communication at a global level. Think of things like language. How hard would it be to communicate if words meant different things in every conversation? You would have to constantly maintain a view of what each word meant in each sentence in order to understand anyone. This is a Tower of Babel situation and communication would break down.
This may provide some intuition for the value of having a global graph that is semantic so that we as a species can accrete knowledge over time and communicate across applications and communities.
Hey Yaniv and team, thanks for sharing and building this!
In the spec you say Solving the remaining composability challenges will enable an interoperable web3, I cant help but think this is much bigger than web3, it could enable interoperable knowledge across … well everything really. Super hyped about GRC-20.
I have a few questions/thoughts after reading the spec:
The specification seems quite simple and elegant and the problem of interoperability has been a theme in the web3 community for a while now. Do you know of any other initiatives/projects that attempted (and maybe failed?) to create something similar?
The document mentions Knowledge is published onto The Graph using onchain transactions. Maybe I’m misunderstanding this, but are there plans to have a cannonical blockchain where public knowledge is stored? What does that look, a set of smart contracts probably? And I assume that will be seeded with a bunch of “top level” entities like those described in the spec that already have an assigned ID, is that correct?
Any plans on building documentation or maybe tools for developers that want to use/integrate with the standard? For example, let’s say I’m looking to build a dapp that uses GRC-20 based knowledge graphs, where do I start?
Related to previous question, it would be nice to have a sandbox environment with a pre-populated (small) knowledge graph to play with, I know as I was reading I wanted something like that to exist to visualize and explore the ideas in the spec. A simple local first website would be nice.
How much of this is implemented on Geo?
Thanks again, excited for the future of The Graph!
BTW, I was already sold on the idea then I came across this post by @0xThierryx.com, brilliant stuff.
Driving AI agents’ behavior and governance with easily swappable knowledge graphs is a great way to empower people and take back some control, which is what web3 is about no? I wonder how far this can go, maybe there’s a future where knowledge graphs are incorporated into AI training as a way to reduce trainer bias or at least steer it toward individual preferences. Very interesting!