namedgraph

I use it in ETL whenever I have an XML source, then I use XSLT to lift it to RDF (either RDF/XML or TriX). I use it for the UI where I'm transforming RDF/XML to HTML. I'm also using for the interactive parts instead of Javascript (or React or Svelte etc.), but that's the interactive XSLT extension that goes beyond the standard.

XML to XML, XML to RDF, JSON to XML and XML to JSON, XML to text -- XSLT can be used for all kinds of transformations. 3.0 also supports streaming transforms, which is very useful for large input files.

XSLT is a declarative DSL made specifically for the XML data model. It does limited things such as navigating the XML tree but does them really well. It lifts the abstraction level so you can focus on the transformation. You can transform XML with bash or a general purpose language like Java, but it will never be so concise or effective.

https://atomgraph.com/cases/

Graph layout is just one of multiple layout modes. See here for more screenshots: https://atomgraph.github.io/LinkedDataHub/

It certainly has one of the largest interactive XSLT codebases that use Saxon-JS: https://www.saxonica.com/saxon-js/

No complaints about the Saxon processors here (we're using Saxon-HE server-side and Saxon-JS client-side). The XSLT standards are excellent, as is the quality of Saxon implementations.

That's just bullshit. Stop spreading FUD.

We participated in a huge RfP for a pharma company which planned RDF KG infrastructure for the next couple of years with 500 billion triple capabilities.

Biomedical, finance, defence, automotive -- all of those industries are using RDF/SPARQL. Just because your problems are not big or complex enough doesn't mean this tech is not used. It takes a certain organization size for Knowledge Graphs to make sense and pay off, that's why most industry users are Fortune 500-level companies.

Google started calling it Knowledge Graph 10 years ago: https://en.wikipedia.org/wiki/Google_Knowledge_Graph Then everyone else followed.

It doesn't have many ETL features, but it does support CSV import.

What kind of data are you looking to transform?

Just FYI, there are more screenshots on this GH page: https://atomgraph.github.io/LinkedDataHub/

At least in LinkedDataHub, the graph layout is only one of layout modes, together with lists, tables, charts, maps etc.

Check the GH page for more screenshots: https://atomgraph.github.io/LinkedDataHub/

The endpoint served by our partners went down.

Can you ping me at martynas@atomgraph.com? Would be appreciated.

Absolutely. XSLT is a data transformation technology, not a template language.

You do realize this is an open-source project? And you are comparing with a product by Neo4J who got $300M VC investment?

The enterprise Knowledge Graphs (yes, it's the same SemWeb tech stack in principle) in Fortune 500 sized companies have in-house platforms that present the graph to the end-users, with entity browsers, analytics, dashboards, structured content etc. LinkedDataHub is an attempt to bootstrap an open-source, standards-driven version of that.

LinkedDataHub was extracted from the common code from a number of Linked Data projects that we have done in different domains.

It can be used as a framework but it's a standalone application as well, because it provides the default built-in ontologies as well UI for Linked Data and SPARQL consumption.

Disclaimer: I'm the main developer.

It's special in the way that it is a standard. Pretty much the only standard NoSQL query language still.

You'd still need Linked Data/SPARQL to access datasources such as DBPedia, Wikidata etc.?

This video shows how RDF and SPARQL can be used to create interactive mash-ups from Linked Data sources. Try to do this with JSON :) Or even property graphs.

No Web Components, React, JSX, Svelte, Shadow DOM etc. etc. were used to implement the UI, only XSLT 3.0 and Saxon-JS.

Yes, let us see how you do data interchange without global identifiers. Such as URIs, which RDF has built-in natively and property graphs do not.

You're right about bioinformatics, but lets do a quick check on http://sparql.club/ on who else is looking for RDF/SPARQL specialists. Oh look: automotive industry, finance, publishing, medical, research etc.

Who knew that a global machine-readable knowledge base would involve some complexity?

Triples are already structured, machine-readable data. HTML is not.

Let us see your proposal of the superior model?

RDF was designed primarily for data interchange and there's nothing that beats it at that.

E.g. to get a job in FAANG, finance or pharma where SPARQL is used extensively on enterprise Knowledge Graphs? Check the jobs here: http://sparql.club/

This is one recent meta-study: https://www.nature.com/articles/s41597-021-00797-y

One of the main datasources is uniprot.org.

I know for a fact that AstraZeneca, Novo Nordisk, Novartis, Roche, Boehringer Ingelheim are all using RDF Knowledge Graphs, and there are probably many others. It would take some time to find the references though.

Check out our company page, maybe we can help ;) https://atomgraph.com/

Yes RDF is in its own niche -- data interchange. And that's where merge matters, when you for example need to merge protein data with genes and drugs etc. A bunch of pharma companies are using RDF Knowledge Graphs for that purpose. The need for data interchange comes with a certain company size, and that point RDF becomes the solution because there are no real alternatives.

I'm not talking about replacing JSON with RDF. Don't need data interchange -- don't use RDF. RDF is both at a different level of abstraction and solving problems of different scope.

Research projects? Research is something coming out of academia, as you know. These are open-source projects with active developer communities. Jena has long been under Apache, RDF4J is now under Eclipse Foundation.

Can you for once answer why large companies in the industry are using RDF/SPARQL as of today if it's so "dead"? Here's a list: http://sparql.club

Relational model, XML/JSON etc. simply do not have a generic merge operation defined the same way as RDF does. This can be proved with pen and paper.

And you still haven't addressed my second point about widespread industry use. It seems that SemWeb haters/sceptics always try to avoid this, why could that be?..

RDF is absolutely about triples and the converse graph form! The serialization formats are immaterial, orthogonal. The fact that you think it's about any particular format makes it obvious that you don't get it at all.

OWLAPI, Protege - that's it? RDF libraries broken? Dude what rock are you living under? What about Jena, RDF4J, rdflib, redland, dotNetRDF etc? Most of these libraries have been developed and tested for 20+ years and are active. See for yourself: https://github.com/semantalytics/awesome-semantic-web#progra...

Why are you spreading FUD?

We wasted 20 years by trying to replace one form of brackets with the other (XML vs. JSON). WHATWG and the browser vendors are responsible for this. Just like for the fact that we still don't have a machine-readable web. FAANG crawls the structured schema.org metadata like nobody else can and profits from it, and the rest of use are left with the HTML5 and Javascript crap.

Right... except that Uber, Boeing, JP Morgan Chase, Nike, Electronic Arts etc. etc. are looking for SPARQL developers right now: http://sparql.club/