namedgraph

Check our SPARQL-driven Knowledge Graph management system :) https://atomgraph.github.io/LinkedDataHub/

Explain this Knowledge Graph usage by Fortune 500 companies then: http://sparql.club/

It's not what you have to do, or how, it's that for the first time we have a common model for data interchange (RDF) with which you can model concepts and things in your domain, or more-importantly across domains, and simply merge the datasets. Try that with the relational model or JSON. Integration is the main value proposal of RDF today, nobody sane is trying to build a single global ontology of the world .

You can despise the fringe academic research, but how do you explain Knowledge Graph use by FAANG (including powering Alexa and Siri) as well as a number of Fortune 500 companies? Here are the companies looking for SPARQL (RDF query language) developers: http://sparql.club

Dude you're delusional. The web only succeeded because it was built on declarative tech, and JS is an the opposite of that.

Don't mix the WS-* trash with XPath/XSLT -- still the only standard data transformation technology. Last I check the JSON folks were still trying to reinvent XML schema? The JSON stack has nothing on XML in terms of maturity and features.

Exactly

Data-driven architecture is the future. Data has to be driving the software, not the way around.

They are what Joel Spolsky called "architecture astronauts".

Could a part of the reason that XPath stayed a niche technology that WHATWG and Google continuously chipped away at XML support and compatibility and shipped 20 year old implementations?

> SemWeb stack has almost zero adoption since its inception while graph databases are trendy

Where is my LOL GIF :D

RDF Knowledge Graphs used by: Elsevier, Bloomberg, Thomson Reuters/Refinitiv, Uber, Zalando, Microsoft, Apple, Amazon, HSBC... do I need to continue?

If you mean "mainstream developer" adoption, that is a poor and irrelevant indicator, because mainstream is not where the innovation happens.

Are you kidding? IRIs is what sets RDF above and beyond other data models. Global identifiers are crucial if you want to work with data interchange on a web scale.

Show me a definition of a "general graph model"? Nothing shows up on Wikipedia.

There is on the other hand a directed graph model: https://en.wikipedia.org/wiki/Directed_graph This is exactly what RDF is, with labeled vertices and edges.

Property graphs are mostly popular due to Neo4J marketing enabled by VC dollars. W3C has no such backing.

“Easier” is completely subjective, no way you can demonstrate that.

RDF solves a much larger problem than just graph data model and query. It addresses data interchange on the web scale, using URIs, zero-cost merge, Linked Data etc.

XQuery is for the XML data model, which is a tree and not a graph.

Tables as abstract and man-made, graphs and networks describe the real world much more naturally.

Also schema is optional in graph DBs, which gives them flexibility.

And in the case of RDF, global identifiers (URIs) and zero-cost dataset merge operation make it a unique fit for data interchange. It’s the only data model designed to be web-native.

RDF is a directed graph model. Nowhere does it say properties have to have properties in a graph model. You can always model them as intermediary nodes.

And every graph database conforms to Cypher or GQL? These are not even standards, ar least yet.

Not true at all. You can query an RDF dataset with SPARQL and not have any RDFS/OWL schema. A schema/ontology/vocabulary gives you a domain model, but it’s optional.

I don’t suppose either, because an equivalent example in SPARQL would not be more clunky.

Basically Neo4J thrives on vendor lock-in and standards lower the lock-in.

For some reason you neglect to mention RDF graph data model and its SPARQL query language, which have been W3C standards since 1997 and 2008, respectively.

They have a healthy ecosystem of both open-source and commercial software, and unlike property graphs were designed with data interchange in mind from the outset.

SPARQL was the first and still is the only standard NoSQL query language.

because it is an enterprise language? Jena originates from Hewlett-Packard labs.

That is exactly what is happening: people and companies marking up their pages with JSON-LD and RDFa metadata because it impacts SEO: https://developers.google.com/search/docs/guides/intro-struc...