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?

Basically I’m combining your local music library with data from streaming services so you have unified playlists across them.

So basically I’m having to match a bunch of resources like songs together from different APIs.

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.

Can you describe a task that XSLT makes substantially easier to build/more correct/faster to execute? Saying “yep its good” gives an opinion but after looking at XSLT docs I am not “getting it”. Why do I want this? I transform data all the time with a bash script, is XSLT like bash?

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.