Is RDF "hard"?

It is funny. Just now there’s a cool HN thread The Block Protocol | Hacker News where one of the comments says: “Oh look, someone reinvented semantic web again.” and further on it goes into “Why is RDF a bad thing?” with response:

  • Layers upon layers of complexity: Implementing CURIs alone is a non trivial task, although all that’s really needed to describe entities and attributes is 128bit UUIDs.

  • There is no good build-in way for authentication and trust.

  • Description Logic (the foundation of OWL) has a fundamentally prescriptive philosophy, which makes it inappropriate for most practical applications.

  • No good library and tool support in general, due to the complexity.

  • Blank Nodes

  • No good consistency mechanism for distributed data generation, and Quads (having multiple graphs) don’t properly solve this.

  • Using human readable entity and attr id’s leads to more bike-shedding and accidental collisions than it’s worth.

  • High barriers to entry.

  • After years of developer disappointment the earth is pretty much salted.

Some of these refer to what we discuss here.

Yes, I feel the same as you @dynamoRando and also want to stress there’s no criticism to my post, and mostly an encouragement to delve deeper into aspect that maybe deserve more attention.

1 Like