3 ms·
The main benefit in my eyes is data integration. If you have multiple systems with data, and you want to merge the data together into a unified whole for some r
by jshen 8y ago
The main benefit in my eyes is data integration. If you have multiple systems with data, and you want to merge the data together into a unified whole for some reason then RDF/JSON-LD make it easy and mostly automatic.
For example:
1. How do you distinguish IDs from one system with those of another? RDF solves this.
2. How do you distinguish property names across systems? RDF solves this.
3. What if a entity originates in system A which you don’t control but you want to add a property to it in your system? RDF solves this.
JSON-LD is simply one way to serialize RDF data that makes look like what you would typically expect from an API that returns JSON. I.e. it’s developer friendly
In addition to the above, RDF is also an extraordinarily flexible/schemaless data model if you store your data as triples rather than as documents. There is definitely a steep learning curve to linked data, and I’ve had a hard time explaining it’s value over the years, but I think it’s worth the time to learn, understand, and leverage.
All of these benefits exist before you get into things like ontologies, which allows you to add additional value on top of what I outlined above.
- vfaronov 8y agoOutstanding explanation. I would like to emphasize one point: > If you have multiple systems with data, and you want to merge the data together into a unified whole for some reason This isn’t just about “big data” or “data warehousing” or such OLAPy concerns. It’s really about the bread and butter of modern information systems. “Get some ID from service A, use it to query service B.” Does that sound familiar? That’s data integration for you. That’s what RDF / Linked Data is about.