RDF, Triples, and Semantic Web in everyday apps
rdf, semantic-web, triples
Solution
Triples can represent any other data structure. But this doesn't necessarily make them easier to work with. If your problem is table-shaped, then a table data structure will work better. With a graph data structure, you need to think about how to make up tables from triples, and that's extra work.
Solving most problems (especially simple problems where the shape of your data is predictable) doesn't require the flexibility of a graph data structure.
Problem
Vague, uninformed questions: 1: Why do nearly 100% of app developers, app development communities and literature (books, tutorials, etc) take for-granted that you want to express data using either a relational database or a key-value store? 2: Why isn't everybody using "Triple" data structures? 3: Aren't Triples applicable to every problem that relational databses and key-value stores, and aren't Triples at least as easy to work with in every case?